A communication method and device

By configuring SRAP entities in advance or by receiving headless data packets at the remote terminal equipment, the failure problem of remote user equipment during RRC reconstruction or recovery is solved, and the success rate is improved.

CN116997032BActive Publication Date: 2026-11-10HUAWEI TECH CO LTD
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202210578450.3
Authority / Receiving Office
CN · China
Patent Type
Patents(China)
Current Assignee / Owner
Priority Date
2022-04-25
Filing Date
2022-05-25
Publication Date
2026-11-10
Estimated Expiration
2042-05-25

AI Technical Summary

Technical Problem

In relay communication scenarios, when remote user equipment (UE) rebuilds or recovers RRC, the release of the SRAP entity makes it impossible to recognize the RRC rebuild message with the SRAP header, resulting in rebuild failure and a low success rate.

Method used

The remote terminal device predetermines the SRAP entity, and after receiving a data packet with an SRAP header, removes the header information and obtains configuration information to configure the SRAP entity, or receives a headerless data packet and configures the SRAP entity according to the configuration information, or the relay terminal device processes the SRAP header to send a headerless data packet to the remote terminal device.

Benefits of technology

It improves the success rate of RRC reconstruction or RRC recovery on remote terminal devices, ensuring that messages with SRAP headers can be correctly identified during subsequent communication.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN116997032B_ABST
    Figure CN116997032B_ABST
Patent Text Reader

Abstract

This application relates to a communication method and apparatus. A remote terminal device receives a first data packet from a relay terminal device via SRB1. The first data packet includes a first message and an SRAP header. The first message is either an RRC connection restoration message or an RRC reconstruction message. The remote terminal device removes the SRAP header through an SRAP entity to obtain configuration information. The SRAP entity is determined before removing the SRAP header. The remote terminal device configures the SRAP entity according to the configuration information. The remote terminal device can predetermine the SRAP entity, so that after receiving the first data packet with the SRAP header, the remote terminal device can remove the SRAP header through the SRAP entity, thereby obtaining the RRC reconstruction message or the RRC connection restoration message, thus improving the success rate of RRC reconstruction or RRC restoration for the remote terminal device.
Need to check novelty before this filing date? Find Prior Art

Description

[0001] Cross-reference to related applications

[0002] This application claims priority to Chinese Patent Application No. 202210444170.3, filed on April 25, 2022, entitled "A Communication Method", the entire contents of which are incorporated herein by reference. Technical Field

[0003] This application relates to the field of communication technology, and in particular to a communication method and device. Background Technology

[0004] In Uu interface communication, when a user equipment (UE) fails to connect in Radio Resource Control (RRC), it can resume RRC; or after being released to the inactive RRC state, it can re-establish RRC. In relay communication scenarios, remote UEs can also resume or re-establish RRC through relay UEs.

[0005] Taking the RRC reconstruction process as an example. Currently, when a remote UE initiates an RRC reconstruction, it can send an RRC reconstruction request to the base station through the relay UE. After receiving the RRC reconstruction request, the base station will send an RRC reconstruction message to the remote UE through the relay UE. This RRC reconstruction message can carry information used to configure the sidelink relay adaptation protocol (SRAP) entity of the remote UE. The RRC reconstruction message sent by the relay UE to the remote UE carries an SRAP header. However, when the remote UE fails in the RRC connection state or is released to the RRC inactive state, it may release the SRAP entity. This causes the remote UE to be unable to recognize the RRC reconstruction message with the SRAP header, and thus discard the RRC reconstruction message. This will cause the remote UE reconstruction to fail, and because the remote UE cannot obtain the information carried in the RRC reconstruction message for configuring the SRAP entity, it cannot configure the SRAP entity. The same applies to the RRC recovery process.

[0006] It is evident that the success rate of RRC reconstruction or recovery for remote UEs is currently low. Summary of the Invention

[0007] This application provides a communication method and device to improve the success rate of RRC reconstruction or RRC recovery for remote UEs.

[0008] In a first aspect, a first communication method is provided, which can be executed by a terminal device, or by another device including the functions of a terminal device, or by a chip system (or chip) or other functional module capable of implementing the functions of the terminal device, such as being disposed within the terminal device. The terminal device is, for example, a remote terminal device. The method includes: receiving a first data packet from a relay terminal device via an SRB1 of the remote terminal device, the first data packet including a first message and an SRAP header, the first message being an RRC connection restoration message or an RRC reconstruction message; removing the SRAP header via an SRAP entity to obtain configuration information, the SRAP entity being determined before removing the SRAP header; and configuring the SRAP entity according to the configuration information.

[0009] In this embodiment, the remote terminal device can pre-determine the SRAP entity. After receiving a first data packet with an SRAP header, the remote terminal device can remove the SRAP header through this SRAP entity, thereby obtaining an RRC reconstruction message or an RRC connection recovery message, thus improving the success rate of RRC reconstruction or recovery. Furthermore, the remote terminal device can configure the SRAP entity based on the configuration information included in the RRC reconstruction message or RRC connection recovery message, ensuring that messages with SRAP headers can be correctly identified during subsequent communication.

[0010] In an optional implementation, the method further includes: establishing the SRAP entity before removing the SRAP header. For example, when the remote terminal device fails in RRC connection state, or when it is released to RRC inactive state, the SRAP entity can be released, and therefore, the remote terminal device can re-establish the SRAP entity. For example, the SRAP entity can be established after the remote UE sends an RRC recovery request or an RRC reconstruction request, or when the remote UE is preparing to send an RRC recovery request or an RRC reconstruction request, or when the remote UE is preparing to initiate RRC connection recovery or RRC connection reconstruction, or when or after timer T301 or timer T311 starts, or when or after timer T319 or timer T319a starts, or also when the remote UE initiates RRC connection recovery or RRC connection reconstruction.

[0011] In one optional implementation, establishing the SRAP entity before removing the SRAP header includes: establishing the SRAP entity according to a default configuration before removing the SRAP header. If the remote terminal device has not yet obtained the configuration information of the SRAP entity, then the remote terminal device can establish the SRAP entity according to the default configuration.

[0012] In one optional implementation, the SRAP entity is one that was not released when the remote terminal device was released to the RRC inactive state. For example, if the remote terminal device did not release the SRAP entity when released to the RRC inactive state, or when the remote terminal device failed in the RRC connected state, the remote terminal device can utilize the unreleased SRAP entity without having to create a new SRAP entity. Furthermore, the remote terminal device does not need to perform any additional configuration on the unreleased SRAP entity, making the implementation relatively simple.

[0013] In an optional implementation, the method further includes reconfiguring the unreleased SRAP entity before removing the SRAP header. For example, if the remote terminal device does not release the SRAP entity when it is released to an RRC inactive state, or when the remote terminal device fails in an RRC connected state, the remote terminal device can utilize the unreleased SRAP entity. The remote terminal device can reconfigure the unreleased SRAP entity to process the SRAP header of the first data packet according to the reconfigured SRAP entity. For example, the remote terminal device can reconfigure the SRAP entity according to the default configuration, without specific limitations.

[0014] In one optional implementation, the SRAP entity does not include the first field (or, in other words, the SRAP entity does not include configuration information for the first field); or, the SRAP entity includes the first field (or, in other words, the SRAP entity includes configuration information for the first field), and the first field is an undefined field, or the first field carries a default value. The first field is used to carry the identifier of the remote terminal device. A normal SRAP entity typically includes configuration information for the first field to carry the identifier of the remote terminal device. After receiving a data packet, the SRAP entity can compare the identifier of the remote terminal device carried in the data packet with the identifier of the remote terminal device carried by the SRAP entity. If they match, the SRAP entity can remove the SRAP header of the data packet and deliver the data packet to the upper layer of the SRAP entity; if they do not match, the SRAP entity can discard the data packet. In this embodiment, the remote terminal device has not yet obtained its identifier, therefore the SRAP entity may not include the configuration information for the first field, or although the SRAP entity includes configuration information for the first field, the first field may be undefined, or the first field may carry a default value. That is, the SRAP entity does not currently carry the identifier of the remote terminal device.

[0015] In one optional implementation, the SRAP header includes a first identifier, which is the identifier of the remote terminal device; or, the SRAP header does not include the identifier of the remote terminal device. If the message sent by the access network device to the relay terminal device includes the first identifier, the relay terminal device may not process it, and the SRAP header of the first data packet may continue to include the first identifier. Alternatively, the relay terminal device may remove the first identifier from the SRAP header before sending the first data packet to the remote terminal device, in which case the SRAP header received by the remote terminal device will not include the first identifier. The SRAP entity determined by the remote terminal device may not recognize the identifier of the remote terminal device; regardless of whether the SRAP header includes the first identifier, the SRAP entity can remove the SRAP header. Therefore, through this SRAP entity, the remote terminal device will not discard the first data packet.

[0016] In one optional implementation, configuring the SRAP entity according to the configuration information includes: configuring the SRAP entity according to a second identifier included in the configuration information, where the second identifier is the identifier of the remote terminal device. After removing the SRAP header of the first data packet from the SRAP entity of the remote terminal device, the configuration information included in the first data packet can be obtained. The remote terminal device can configure the SRAP entity according to this configuration information. For example, if the configuration information includes a second identifier, the remote terminal device can add the second identifier to the SRAP entity. Therefore, if the SRAP entity subsequently receives another data packet, it can remove the SRAP header of the data packet according to the second identifier, or discard the data packet. The second identifier and the first identifier can be, for example, the same identifier, or they can be different identifiers.

[0017] Secondly, a second communication method is provided, which can be executed by a terminal device, or by another device including the functions of a terminal device, or by a chip system or other functional module capable of implementing the functions of the terminal device, such as being disposed within the terminal device. Optionally, the terminal device is, for example, a remote terminal device. The method includes: receiving a first data packet from a relay terminal device via the SRB1 of the remote terminal device, the first data packet including a first message, and the first data packet not including an SRAP header, the first message being an RRC connection restoration message or an RRC reconstruction message; configuring the SRAP entity according to the configuration information included in the first message.

[0018] For example, the relay terminal device can remove the SRAP header from the first data packet and then send the first data packet with the SRAP header removed to the remote terminal device. The first data packet received by the remote terminal device will then not include the SRAP header. The remote terminal device can then process the first data packet normally. For instance, the remote terminal device can obtain the configuration information included in the first data packet and configure the SRAP entity based on this configuration information, enabling the SRAP entity to filter data packets normally. In this embodiment, the remote terminal device does not need to pre-determine the SRAP entity, resulting in minimal changes to the remote terminal device's operating logic and a relatively simple implementation.

[0019] Thirdly, a third communication method is provided, which can be executed by a terminal device, or by another device including the functions of a terminal device, or by a chip system or other functional module capable of implementing the functions of the terminal device, such as being disposed within the terminal device. Optionally, the terminal device may be, for example, a relay terminal device. The method includes: obtaining a second data packet through an SRAP entity, the second data packet including an SRAP header and a first message, the SRAP header including a first identifier of a remote terminal device, the first message being an RRC connection recovery message or an RRC reconstruction message; processing the SRAP header through the SRAP entity to obtain a first data packet, the first data packet not including the first identifier; and sending the first data packet to the remote terminal device through the SRB1 of the remote terminal device.

[0020] The second data packet, for example, originates from an access network device. The relay terminal device can process the SRAP header so that the first data packet does not include the first identifier. After receiving the first data packet, the remote terminal device can process it without discarding it, thus enabling it to obtain RRC reconstruction or RRC connection restoration messages, thereby improving the success rate of RRC reconstruction or restoration. Furthermore, the remote terminal device can configure the SRAP entity based on the configuration information included in the RRC reconstruction or RRC connection restoration message, ensuring proper recognition of messages with SRAP headers in subsequent communications.

[0021] In one optional implementation, the SRAP entity processes the SRAP header to obtain the first data packet, including: removing the SRAP header from the SRAP entity to obtain the first data packet; or, processing the first identifier in the SRAP header from the SRAP entity to obtain the first data packet. The relay terminal device can remove the SRAP header, thus eliminating the need for the remote terminal device to pre-establish an SRAP entity, simplifying the operation process of the remote terminal device. Alternatively, the relay terminal device can process the first identifier in the SRAP header, so the SRAP entity of the remote terminal device does not need to identify the remote terminal device's identifier in the SRAP header, but can simply remove the SRAP header. Through the technical solutions of this application embodiment, the probability of the remote terminal device discarding the first data packet can be reduced, improving the success rate of RRC reconstruction or RRC recovery for the remote terminal device.

[0022] In one optional implementation, processing the first identifier in the SRAP header through the SRAP entity includes: updating the first identifier through the SRAP entity; or removing the first identifier through the SRAP entity. For example, the relay terminal device may update the first identifier in the SRAP header to a first value, such as a default value. Alternatively, the relay terminal device may remove the first identifier from the SRAP header. Alternatively, the relay terminal device may also process the first identifier in other ways, as long as the SRAP header no longer includes the first identifier.

[0023] In an optional implementation, the method further includes: determining that the first message is a first downlink message sent to the remote terminal device on the SRB1; or determining that the second data packet includes indication information, the indication information being used to indicate processing of the SRAP header. If the relay terminal device determines that the first message is a first downlink message sent to the remote terminal device on the SRB1, or the second data packet includes the indication information, then the relay terminal device processes the SRAP header in the manner described above.

[0024] Fourthly, a fourth communication method is provided, which can be executed by a terminal device, or by another device including the functions of a terminal device, or by a chip system or other functional module capable of implementing the functions of the terminal device, such as being disposed within the terminal device. Optionally, the terminal device is, for example, a remote terminal device. The method includes: storing a first identifier of the remote terminal device, the first identifier being acquired by the remote terminal device when it is in an RRC connection state, and the first identifier being an identifier of the SRAP entity application of the remote terminal device.

[0025] In this embodiment, the remote terminal device can store the first identifier, or in other words, the remote terminal device does not release the first identifier, thereby enabling it to obtain the SRAP entity. The access network device can also preferentially allocate the first identifier to the remote terminal device, so that the SRAP entity of the remote terminal device can recognize the first message from the access network device, improving the success rate of RRC reconstruction or RRC recovery of the remote terminal device.

[0026] In an optional implementation, the method further includes: sending a second message to the relay terminal device, wherein the second message includes the first identifier, and the second message is an RRC connection restoration request message or an RRC reconstruction request message. Since the remote terminal device stores the first identifier, it can carry the first identifier when sending the second message to the relay terminal device.

[0027] In an optional implementation, the method further includes: establishing the SRAP entity when initiating an RRC connection recovery process or an RRC reconstruction process.

[0028] In one alternative implementation, establishing the SRAP entity includes: establishing the SRAP entity according to a default configuration.

[0029] In one alternative implementation, the SRAP entity is one that was not released when the remote terminal device was released to the RRC inactive state.

[0030] In an alternative implementation, the method further includes: reconfiguring the unreleased SRAP entity in the event of initiating an RRC connection recovery process or an RRC reconstruction process.

[0031] In an optional implementation, the method further includes: receiving a first data packet from the relay terminal device via the SRB1 of the remote terminal device, the first data packet including a first message and an SRAP header, the SRAP header including the first identifier, and the first message being an RRC connection recovery message or an RRC reconstruction message; identifying the first identifier through the SRAP entity and removing the SRAP header to obtain configuration information; and configuring the SRAP entity according to the configuration information. In this embodiment, regardless of how the remote terminal device determines the SRAP entity, the SRAP entity can carry the first identifier. Therefore, the SRAP entity can normally filter data packets. When the access network device assigns an identifier to the remote terminal device, it can preferentially assign the first identifier. If the access network device continues to assign the first identifier to the remote terminal device, the SRAP header carried by the data packets sent by the access network device will also include the first identifier, and the remote terminal device can identify the first data packet, thereby obtaining the configuration information included in the first data packet.

[0032] In an optional implementation, the method further includes: receiving a first data packet from the relay terminal device via the SRB0 of the remote terminal device, the first data packet including an RRC establishment message and excluding an SRAP header; and configuring the SRAP entity according to the configuration information included in the RRC establishment message. If the access network device does not assign a first identifier to the remote terminal device but assigns another identifier, the access network device can execute the RRC establishment procedure. In the RRC establishment procedure, the access network device sends a message via SRB0, and correspondingly, the relay terminal device also sends a first data packet to the remote terminal device via SRB0. Since the message carried by SRB0 does not include an SRAP header, the remote terminal device can obtain the configuration information included in the RRC establishment message to configure the SRAP entity.

[0033] Regarding the technical effects of the optional implementation methods in the fourth aspect, please refer to the description of the technical effects of the relevant implementation methods in any of the foregoing aspects.

[0034] Fifthly, a fifth communication method is provided, which can be executed by an access network device, or by other devices including the functions of an access network device, or by a chip system or other functional module capable of implementing the functions of the access network device, such as being disposed within the access network device. Optionally, the access network device is, for example, a base station. The method includes: receiving a second identifier of a remote terminal device from a relay terminal device; determining a first identifier of the remote terminal device based on the second identifier; and sending a first message to the relay terminal device, the first message including a third identifier, wherein the first identifier may be the same as or different from the third identifier, wherein the first message is an RRC connection recovery message, an RRC reconstruction message, or an RRC establishment message.

[0035] In one optional implementation, the method further includes: the access network device preferentially assigning a first identifier to the remote terminal device.

[0036] In one optional implementation, the access network device preferentially assigns a first identifier to the remote terminal device, including: if the first identifier does not conflict with the identifiers of other remote terminal devices connected to the relay terminal device, then the first identifier is the same as the third identifier, and the first message is the RRC connection restoration message or the RRC reconstruction message; or, if the first identifier conflicts with the identifiers of other remote terminal devices connected to the relay terminal device, then the first identifier is different from the third identifier, and the first message is the RRC establishment message.

[0037] In one optional implementation, if the first message is the RRC connection recovery message or the RRC reconstruction message, the first message is sent via SRB1; or, if the first message is the RRC establishment message, the first message is sent via SRB0.

[0038] For the technical effects of the fifth aspect or its alternative implementations, please refer to the description of the technical effects of the relevant implementations of the fourth aspect.

[0039] Sixthly, a communication device is provided. The communication device can be a remote terminal device as described in any one of the first to fifth aspects above. The communication device possesses the functions of the aforementioned remote terminal device. The communication device is, for example, a remote terminal device, or a larger device including a remote terminal device, or a functional module within a remote terminal device, such as a baseband device or a chip system. In one optional implementation, the communication device includes a baseband device and a radio frequency device. In another optional implementation, the communication device includes a processing unit (sometimes also called a processing module) and a transceiver unit (sometimes also called a transceiver module). The transceiver unit can implement both transmitting and receiving functions. When the transceiver unit implements the transmitting function, it can be called a transmitting unit (sometimes also called a transmitting module), and when the transceiver unit implements the receiving function, it can be called a receiving unit (sometimes also called a receiving module). The transmitting unit and the receiving unit can be the same functional module, which is called the transceiver unit and can implement both transmitting and receiving functions; or, the transmitting unit and the receiving unit can be different functional modules, and the transceiver unit is a collective term for these functional modules.

[0040] In one optional implementation, the transceiver unit is configured to receive a first data packet from a relay terminal device via the SRB1 of the communication device, the first data packet including a first message and an SRAP header, wherein the first message is an RRC connection recovery message or an RRC reconstruction message; the processing unit is configured to remove the SRAP header through an SRAP entity and obtain configuration information, wherein the SRAP entity is determined before removing the SRAP header; the processing unit is further configured to configure the SRAP entity according to the configuration information.

[0041] In one optional implementation, the transceiver unit is configured to receive a first data packet from a relay terminal device via the SRB1 of the communication device, the first data packet including a first message and excluding an SRAP header, the first message being an RRC connection recovery message or an RRC reconstruction message; the processing unit is configured to configure the SRAP entity according to the configuration information included in the first message.

[0042] In one optional implementation, the processing unit is configured to store a first identifier of the remote terminal device, the first identifier being acquired by the remote terminal device when it is in an RRC connection state, and the first identifier being an identifier of the SRAP entity application of the remote terminal device.

[0043] In an alternative embodiment, the communication device further includes a storage unit (sometimes also called a storage module), and the processing unit is configured to couple with the storage unit and execute programs or instructions in the storage unit to enable the communication device to perform the functions of the remote terminal device described in any of the first to fifth aspects above.

[0044] In a seventh aspect, a communication device is provided. The communication device may be a relay terminal device as described in any of the first to fifth aspects above. The communication device possesses the functions of the aforementioned relay terminal device. The communication device may be, for example, a relay terminal device, or a larger device including a relay terminal device, or a functional module within a relay terminal device, such as a baseband device or a chip system. In one optional implementation, the communication device includes a baseband device and a radio frequency device. In another optional implementation, the communication device includes a processing unit (sometimes also called a processing module) and a transceiver unit (sometimes also called a transceiver module). For details on the implementation of the transceiver unit, please refer to the description in the sixth aspect.

[0045] In one optional implementation, the processing unit is configured to obtain a second data packet through an SRAP entity, the second data packet including an SRAP header and a first message, the SRAP header including a first identifier of the remote terminal device, and the first message being an RRC connection recovery message or an RRC reconstruction message; the processing unit is further configured to process the SRAP header through the SRAP entity to obtain a first data packet, the first data packet not including the first identifier; the transceiver unit is further configured to send the first data packet to the remote terminal device through the SRB1 of the remote terminal device.

[0046] In one alternative implementation, the communication device further includes a storage unit (sometimes also called a storage module), and the processing unit is configured to couple with the storage unit and execute programs or instructions in the storage unit to enable the communication device to perform the functions of the relay terminal device described in any of the first to fifth aspects above.

[0047] Eighthly, a communication device is provided. The communication device may be an access network device as described in any of the first to fifth aspects above. The communication device possesses the functions of the aforementioned access network device. The communication device may be, for example, an access network device, a larger device including an access network device, or a functional module within an access network device, such as a baseband device or a chip system. In one optional implementation, the communication device includes a baseband device and a radio frequency device. In another optional implementation, the communication device includes a processing unit (sometimes also called a processing module) and a transceiver unit (sometimes also called a transceiver module). For details on the implementation of the transceiver unit, please refer to the description in the sixth aspect.

[0048] In one optional implementation, the transceiver unit is configured to receive a second identifier of the remote terminal device from the relay terminal device; the processing unit is configured to determine a first identifier of the remote terminal device based on the second identifier; the transceiver unit is further configured to send a first message to the relay terminal device, the first message including a third identifier, the first identifier being the same as or different from the third identifier, wherein the first message is an RRC connection recovery message, an RRC reconstruction message, or an RRC establishment message.

[0049] In one alternative implementation, the communication device further includes a storage unit (sometimes also called a storage module), the processing unit being coupled to the storage unit and executing programs or instructions in the storage unit to enable the communication device to perform the functions of the access network device described in any of the first to fifth aspects above.

[0050] Ninth aspect, a communication system is provided, comprising the communication apparatus described in the sixth aspect and the communication apparatus described in the seventh aspect.

[0051] In one alternative implementation, the communication system further includes the communication device described in the eighth aspect.

[0052] In a tenth aspect, a computer-readable storage medium is provided for storing a computer program or instructions that, when executed, cause the methods performed by the access network device, remote terminal device, or relay terminal device in the foregoing aspects to be implemented.

[0053] In the eleventh aspect, a computer program product containing instructions is provided, which, when run on a computer, enables the methods described in the above aspects to be implemented.

[0054] In a twelfth aspect, a chip system is provided, including a processor and an interface, the processor being configured to call and execute instructions from the interface to enable the chip system to implement the methods of the above aspects. Attached Figure Description

[0055] Figure 1A This is a schematic diagram of the protocol stacks of various devices in a relay scenario;

[0056] Figure 1B and Figure 1C These are schematic diagrams illustrating two application scenarios of embodiments of this application;

[0057] Figures 2-5 Flowcharts of several communication methods provided in the embodiments of this application;

[0058] Figure 6 A schematic diagram of an apparatus provided in an embodiment of this application;

[0059] Figure 7 This is a schematic diagram of another device provided in an embodiment of this application. Detailed Implementation

[0060] To make the objectives, technical solutions, and advantages of the embodiments of this application clearer, the embodiments of this application will be further described in detail below with reference to the accompanying drawings.

[0061] The following explanations of some terms or concepts used in the embodiments of this application are provided to facilitate understanding by those skilled in the art.

[0062] In this embodiment, the terminal device is a device with wireless transceiver capabilities, which can be a fixed device, a mobile device, a handheld device (e.g., a mobile phone), a wearable device, an in-vehicle device, or a wireless device (e.g., a communication module, a modem, or a chip system, etc.) built into the aforementioned devices. The terminal device is used to connect people, objects, machines, etc., and can be widely used in various scenarios, including but not limited to the following: cellular communication, device-to-device (D2D) communication, vehicle-to-everything (V2X) communication, machine-to-machine / machine-type communications (M2M / MTC) communication, Internet of Things (IoT), virtual reality (VR), augmented reality (AR), industrial control, self-driving, remote medical care, smart grid, smart furniture, smart office, smart wearables, smart transportation, smart city, drones, robots, and other scenarios. The terminal device may sometimes be referred to as user equipment (UE), terminal, access station, UE station, remote station, wireless communication equipment, or user device, etc. For ease of description, the terminal device in this application embodiment will be described using UE as an example.

[0063] The network devices in this application embodiment may include, for example, access network devices and / or core network devices. The access network devices are devices with wireless transceiver capabilities, used to communicate with the terminal devices. The access network devices include, but are not limited to, base stations (base transceiver stations, BTS, Node B, eNodeB / eNB, or gNodeB / gNB), transmission reception points (TRPs), base stations evolved from the 3rd generation partnership project (3GPP), access nodes in Wi-Fi systems, wireless relay nodes, wireless backhaul nodes, etc. The base stations may be: macro base stations, micro base stations, pico base stations, small cells, relay stations, etc. Multiple base stations can support networks using the same access technology or networks using different access technologies. A base station may contain one or more co-located or non-co-located transmission and reception points. The access network equipment can also be a radio controller, centralized unit (CU), and / or distributed unit (DU) in a cloud radio access network (CRAN) scenario. The access network equipment can also be a server, etc. For example, in vehicle-to-everything (V2X) technology, the access network equipment can be a roadside unit (RSU). The following description uses a base station as an example. A base station can communicate with a terminal device, or it can communicate with a terminal device through a relay station. A terminal device can communicate with multiple base stations in different access technologies. The core network equipment is used to implement functions such as mobility management, data processing, session management, policy and billing. The names of the equipment implementing core network functions may differ in systems using different access technologies; this application does not limit this. Taking a 5G system as an example, the core network equipment includes: access and mobility management function (AMF), session management function (SMF), policy control function (PCF), or user plane function (UPF), etc.

[0064] In this application embodiment, the communication device used to implement the network device function can be a network device itself, or it can be a device capable of supporting the network device in implementing that function, such as a chip system. This device can be installed within the network device. In the technical solutions provided in this application embodiment, the example of a network device being used to implement the network device function is used to describe the technical solutions provided in this application embodiment.

[0065] The PC5 reference point (or PC5 interface) serves as the reference point (or interface) between UEs.

[0066] The Uu reference point (or Uu interface) is the reference point (or interface) between the UE and the radio access network (e.g., next generation (NG) radio access network (RAN), or evolved UMTS terrestrial radio access network (E-UTRAN)).

[0067] In this application embodiment, the number of nouns, unless otherwise specified, refers to "singular nouns or plural nouns," that is, "one or more." "At least one" means one or more, and "more than one" means two or more. "And / or" describes the relationship between related objects, indicating that three relationships can exist. For example, A and / or B can mean: A exists alone, A and B exist simultaneously, or B exists alone, where A and B can be singular or plural. The character " / " generally indicates that the related objects before and after are in an "or" relationship. For example, A / B means: A or B. "At least one of the following" or similar expressions refer to any combination of these items, including any combination of single or plural items. For example, at least one of a, b, or c means: a, b, c, a and b, a and c, b and c, or a and b and c, where a, b, and c can be single or multiple.

[0068] The ordinal numbers such as "first" and "second" mentioned in the embodiments of this application are used to distinguish multiple objects and are not used to limit the size, content, order, timing, priority, or importance of the multiple objects. For example, the first data packet and the second data packet can be the same data packet or different data packets, and such names do not indicate differences in the content, size, corresponding sending and receiving ends, sending order, priority, or importance of the two data packets. In addition, the numbering of steps in the various embodiments described in this application is only to distinguish different steps and is not used to limit the order between steps. For example, S201 may occur before S202, or may occur after S202, or may occur simultaneously with S202.

[0069] Please refer to Figure 1AThis diagram illustrates the protocol stack of the remote UE, relay UE, and access network equipment in a relay scenario. The remote UE includes a protocol stack corresponding to the PC5 interface, such as the Packet Data Convergence Protocol (PDCP) entity, SRAP entity, Radio Link Control (RLC) entity, Media Access Control (MAC) entity, and Physical Layer (PHY) entity. There are two PDCP entities, corresponding to the signal radio bearer (SRB) 0 and SRB1 of the remote UE on the Uu interface. If there are more SRBs, there can be more PDCP entities. The SRAP entity corresponds to SRBs other than SRB0 (e.g., SRB1) (or the SRAP entity for the PC5 interface can also correspond to SRB0, but SRB0 messages are not processed), and can also correspond to data radio bearers (DRBs), etc. There are two RLC entities, corresponding to SRB0 and SRB1. If there are more SRBs, there can be more RLC entities. The relay UE includes both a protocol stack corresponding to the PC5 interface and a protocol stack corresponding to the Uu interface. The protocol stack corresponding to the PC5 interface includes SRAP entities corresponding to all SRBs except SRB0 (and possibly DRBs) (or the SRAP entity for the PC5 interface may also correspond to SRB0, but SRB0 messages are not processed), and RLC, MAC, and PHY entities corresponding to SRB0 and SRB1 respectively. The protocol stack corresponding to the Uu interface includes SRAP entities corresponding to each SRB (and possibly DRB), two RLC entities corresponding to SRB0 and SRB1 respectively, a MAC entity, and a PHY entity. The access network equipment includes a protocol stack corresponding to the Uu interface, for example, including two PDCP entities corresponding to SRB0 and SRB1 respectively, SRAP entities corresponding to each SRB (and possibly DRB), and two RLC, MAC, and PHY entities corresponding to SRB0 and SRB1 respectively.

[0070] Taking a remote UE performing RRC reconstruction as an example. When a remote UE performs RRC reconstruction, it sends an RRC reconstruction request to the relay UE via SRB0. According to... Figure 1AIt is known that the remote UE's SRB0 does not correspond to an SRAP entity, or the remote UE's SRAP entity does not process messages on SRB0 (i.e., messages transmitted on SRB0). Therefore, the RRC reconstruction request does not need to add an SRAP header. After receiving the RRC reconstruction request, the relay UE sends the remote UE's Layer 2 (L2) identity number (ID) to the access network device. The access network device can assign a local ID to the remote UE based on this L2 ID, and the access network device will send this local ID to the relay UE. The relay UE receives the access network device's configuration information for the SRAP entity, which includes the remote UE's local ID. According to the configuration information, the relay UE's Uu SRAP entity adds an SRAP header to the RRC reconstruction request from the remote UE, adds the local ID to the SRAP header, and then sends the RRC reconstruction request with the added SRAP header to the access network device through the RLC bearer / channel of the Uu interface. After receiving an RRC reconstruction request from a remote UE, the access network device sends an RRC reconstruction message for the remote UE to the relay UE. This RRC reconstruction message includes an SRAP header. The relay UE can determine that the packet was forwarded to the corresponding remote UE by using the local ID in the header of the received SRAP packet. The relay UE can send this RRC reconstruction message to the remote UE through the PC5 RLCbearer / channel carrying the remote UE's SRB1.

[0071] However, when a remote UE experiences an RRC connection failure, it may have already released the SRAP entity. This causes the remote UE to discard the RRC reconstruction message after receiving it because it cannot recognize the SRAP header, resulting in a reconstruction failure. Furthermore, the RRC reconstruction message also carries information for configuring the remote UE's SRAP entity. Since the remote UE discarded the RRC reconstruction message, it cannot obtain this information and therefore cannot configure the SRAP entity. A similar situation applies to the RRC recovery process.

[0072] Therefore, the technical solution of this application embodiment is provided. In this application embodiment, the remote UE can pre-determine the SRAP entity. After receiving the first data packet with the SRAP header, the remote UE can remove the SRAP header through the SRAP entity, thereby obtaining the RRC reconstruction message or RRC connection recovery message, thus improving the success rate of RRC reconstruction or RRC recovery for the remote UE. Furthermore, the remote UE can also configure the SRAP entity according to the configuration information included in the RRC reconstruction message or RRC connection recovery message, thereby correctly recognizing messages with the SRAP header during subsequent communication.

[0073] The technical solutions provided in this application can be applied to fourth-generation (4G) mobile communication technology systems, such as long-term evolution (LTE) systems, or to 5G systems, such as new radio (NR) systems, or to next-generation mobile communication systems or other similar communication systems, without any specific limitations.

[0074] This application relates to a UE-to-network relay mechanism, which can be used to improve cellular network coverage. Please refer to... Figure 1B and Figure 1C The diagram illustrates two application scenarios according to embodiments of this application. In one scenario, the relay UE is within the coverage area of ​​the access network device in the cellular network; that is, the relay UE can communicate directly with the access network device via the Uu interface. The remote UE can communicate with the relay UE via the PC5 interface, sending data from the remote UE to the relay UE, which then forwards the data to the access network device via the Uu interface. Alternatively, data from the core network destined for the remote UE arrives at the access network device, which sends the data to the relay UE via the Uu interface, and the relay UE then forwards the data to the remote UE via the PC5 interface. Figure 1B In the middle, the remote UE is also within the coverage area of ​​the access network equipment; Figure 1C In this case, the remote terminal equipment is not within the coverage area of ​​the access network equipment.

[0075] To better illustrate the embodiments of this application, the methods provided in the embodiments of this application are described below with reference to the accompanying drawings. For ease of description, the remote terminal device is exemplified as a remote UE, and the relay terminal device is exemplified as a relay UE in the various embodiments of this application. The methods provided in the various embodiments of this application can be applied to... Figure 1B or Figure 1C The network architecture shown, for example, the remote UE involved in the various embodiments of this application, is... Figure 1B or Figure 1C The remote UE in this application refers to the access network device involved in the various embodiments of this application. Figure 1B or Figure 1C The access network equipment in this application, specifically the relay UE involved in the various embodiments, is... Figure 1B or Figure 1C The relay UE in the middle.

[0076] In various embodiments of this application, "entity" may also be replaced with "layer". For example, "SRAP entity" may also be called "SRAP layer", "PDCP entity" may also be called "PDCP layer", etc.

[0077] To address the technical problems addressed in this application, various embodiments of this application provide multiple methods. Please refer to the following for details. Figure 2 This is a flowchart of the first communication method provided in the embodiments of this application.

[0078] S201. The remote UE sends a second message to the relay UE. Correspondingly, the relay UE receives the second message from the remote UE. This second message is a message sent by the remote UE to the access network device through the relay UE. In this embodiment, taking the remote UE performing RRC reconstruction or RRC connection restoration (or simply RRC restoration) as an example, for example, if the remote UE performs RRC reconstruction, the second message is an RRC reconstruction request (or RRC connection reconstruction request); or if the remote UE performs RRC restoration, the second message is an RRC restoration request (or RRC connection restoration request).

[0079] For example, the second message includes information such as the physical cell identifier (PCI) and cell radio network temporary identity (C-RNTI) of the remote UE.

[0080] The second message is sent through the remote UE's SRB0. When the relay UE receives it, there is no SRAP header by default. Therefore, when the remote UE sends the second message, it does not need to add an SRAP header.

[0081] S202. The remote UE determines the SRAP entity. Alternatively, the remote UE obtains the SRAP entity.

[0082] If the remote UE has released the SRAP entity before performing RRC reconstruction or RRC recovery, the remote UE can establish the SRAP entity. For example, the remote UE can release the SRAP entity when it fails in RRC connected state or when it is released to RRC inactive state. Optionally, the remote UE can establish the SRAP entity according to the default configuration, or the remote UE can establish the SRAP entity without any configuration, for example, the remote UE can establish an SRAP entity with SRAP functionality (remove header function).

[0083] Regardless of how the remote UE establishes the SRAP entity, the SRAP entity may not include a first field, or in other words, the SRAP entity may not include the configuration information of the first field (or the configuration information of the SRAP entity may not include the configuration information of the first field). The first field is used to carry the identifier of the remote UE, which may be, for example, a local ID, or other types of identifiers. If the remote UE establishes the SRAP entity normally, the SRAP entity will include the configuration information of the first field, and the first field will carry the identifier of the remote UE. However, in this embodiment, the remote UE establishes the SRAP entity according to a default configuration or without any configuration. Even with a default configuration, it may not include the identifier of the remote UE. Therefore, the SRAP entity may not include the configuration information of the first field, and thus the SRAP entity will not have the configuration of the remote UE's identifier.

[0084] Alternatively, regardless of how the remote UE establishes the SRAP entity, the SRAP may include configuration information for the first field, but the first field may be undefined; for example, the first field may not carry the identifier of the remote UE. Alternatively, the first field may carry a default value, such as "0" or another value, but this default value is not the identifier of the remote UE. Therefore, the SRAP entity established by the remote UE does not have the configuration of the remote UE's identifier.

[0085] It is also possible that the remote UE did not release the SRAP entity before performing RRC reconstruction or RRC recovery. For example, when the remote UE fails in RRC connected state or is released to RRC inactive state, it does not release the SRAP entity. Optionally, the remote UE can reconfigure the SRAP entity. For example, the remote UE can reconfigure the SRAP entity according to the default configuration. The reconfigured SRAP entity may not include the configuration information of the first field, or it may include the configuration information of the first field, but the first field is not defined or carries a default value. Please refer to the above introduction.

[0086] Alternatively, when the remote UE fails in RRC connected state, or is released to RRC inactive state, although the SRAP entity is not released, its configuration is released. This means that the SRAP entity may not include the configuration information of the first field, or it may include the configuration information of the first field, but the first field is undefined or carries a default value. Therefore, the remote UE may not process the SRAP entity, that is, it does not need to execute S202, so S202 is an optional step.

[0087] Specifically, if S202 is executed, it can be executed before, after, or simultaneously with S201, without any specific restrictions. For example, the SRAP entity can be established after the remote UE sends an RRC recovery request or an RRC reconstruction request, or when the remote UE is preparing to send an RRC recovery request or an RRC reconstruction request, or when the remote UE is preparing to initiate an RRC connection recovery or RRC connection reconstruction, or when or after timer T301 or timer T311 starts, or when or after timer T319 or timer T319a starts, or when the remote UE initiates an RRC connection recovery or RRC connection reconstruction.

[0088] S203. The relay UE sends information about the remote UE to the access network device. Correspondingly, the access network device receives the information about the remote UE from the relay UE. The information about the remote UE may include the L2 ID of the remote UE, which indicates that the remote UE accesses the network through the relay UE.

[0089] For example, a relay UE sends sidelink UE information (SUI) to the access network device, which includes information about the remote UE.

[0090] S204. The access network device sends the first identifier of the remote UE to the relay UE. Correspondingly, the relay UE receives the first identifier from the access network device. The first identifier is, for example, the local ID of the remote UE.

[0091] For example, the access network device can assign a first identifier to the remote UE and send SRAP configuration information to the relay UE. This SRAP configuration information may include the first identifier of the remote UE. When the relay UE relays (including sending or receiving) data between the remote UE and the access network device, the SRAP entity can determine the destination device based on the SRAP configuration information and the source of the data packet. For example, for uplink data transmission, the SRAP entity can determine to add a local ID and / or RB information to the SRAP header based on the PC5RLC bearer or channel from the remote UE, and determine the RLC bearer information on the Uu interface based on the local ID in the SRAP header from the remote UE. Similarly, for downlink data transmission, the SRAP entity can determine which remote UE the data packet should be transmitted to based on the local ID in the header of the data packet received from the access network device.

[0092] S205, The relay UE adds an SRAP header to the second message.

[0093] The relay UE can add an SRAP header to the second message based on the received SRAP configuration information. The SRAP header includes a first identifier. Optionally, the SRAP header also includes information about the SRB used by the remote UE to send the second message, such as the identifier of the remote UE's SRB0, or information that the remote UE's RB ID is 0.

[0094] S206. The relay UE sends a second message with an added SRAP header to the access network device. Correspondingly, the access network device receives the second message with the added SRAP header from the relay UE. For example, the relay UE sends this second message with the added SRAP header to the access network device via the RLC bearer corresponding to the SRB0 of the remote UE, where the second message is an SRB0 message, such as an RRC recovery request or an RRC reconstruction request.

[0095] S207. The access network device sends a first message to the relay UE. Correspondingly, the relay UE receives the first message from the access network device. This first message is sent by the access network device to the remote UE via the relay UE in response to a second message sent by the remote UE via the relay UE. The first message is an SRB1 message of the remote UE. If the second message is an RRC reconstruction request, then the first message is an RRC reconstruction message; or, if the second message is an RRC recovery request, then the first message is an RRC recovery message (or RRC connection recovery message). The first message may include configuration information that can be used to configure the SRAP entity of the remote UE. For example, the configuration information may include a second identifier, which is the identifier of the remote UE, such as a local ID assigned to the remote UE by the access network device. Optionally, the first identifier and the second identifier may be the same identifier or different identifiers. This configuration information is, for example, a sideline layer 2 remote configuration (sl-L2RemoteConfig).

[0096] For example, when an access network device sends a second data packet to a relay UE, the second data packet may include a first message and an SRAP header, which may include a first identifier. Optionally, the SRAP header may also include information about the SRB of the remote UE receiving the second data packet, such as the identifier of the remote UE's SRB1, or the RB ID information of the remote UE.

[0097] S208. The relay UE sends a first data packet to the remote UE. Correspondingly, the remote UE receives the first data packet from the relay UE. For example, the relay UE receives an SRB1 message (such as an RRC recovery message or RRC reconstruction message) sent from the access network device to the remote UE. This SRB1 message is carried and sent between the access network device and the relay UE through the first data packet.

[0098] The first data packet and the second data packet can be the same data packet. For example, if the Uu SRAP entity of a relay UE receives a second data packet from an access network device, it can deliver the second data packet to the PC5 SRAP entity of the relay UE. The PC5 SRAP entity of the relay UE may choose not to process the second data packet, but instead send it to the remote UE via the PC5RLC bearer or channel of the remote UE's SRB1. The Uu SRAP entity and the PC5 SRAP entity of the relay UE can be the same entity or different entities.

[0099] Alternatively, the first data packet and the second data packet can be different data packets, but both the first data packet and the second data packet include the first message. For example, the Uu SRAP entity of the relay UE receives a second data packet from the access network device and can deliver the second data packet to the PC5 SRAP entity of the relay UE. The PC5 SRAP entity of the relay UE can remove the SRAP header included in the second data packet, and then re-add the SRAP header to the second data packet with the SRAP header removed to obtain the first data packet, and then send the first data packet to the remote UE through the PC5 RLC bearer or channel of the remote UE SRB1. The SRAP header added by the PC5 SRAP entity of the relay UE to the second data packet with the SRAP header removed may include a first identifier. Optionally, the SRAP header may also include information about the SRB of the remote UE that receives the first data packet, such as the identifier of the remote UE's SRB1 or the RB ID of the remote UE.

[0100] S209. The remote UE removes the SRAP header of the first data packet through the SRAP entity and obtains configuration information.

[0101] The remote UE has identified the SRAP entity. This SRAP entity may not include the first field, or may not include configuration information for the first field, or may include an undefined first field or a first field carrying a default value. Therefore, the SRAP entity may not recognize (or ignore) the remote UE's identifier included in the SRAP header, or the SRAP entity may only have the function of removing the SRAP header and not the function of error packet detection (for example, the SRAP entity will not compare whether the remote UE's identifier included in the SRAP header is the same as the identifier included in the SRAP entity or the configured identifier, and will not directly drop the data packet because the identifier included in the SRAP header of the received data packet is not the identifier configured by the SRAP entity). In this case, the SRAP entity will remove the SRAP header, and the remote UE will obtain the first data packet with the SRAP header removed. The SRAP entity can deliver the first data packet with the SRAP header removed to the PDCP entity of the remote UE. The PDCP entity can parse the first data packet with the SRAP header removed and obtain the first message, so that the remote UE's RRC reconstruction or RRC recovery can be successful, thereby improving the success rate of the remote UE's RRC reconstruction or RRC recovery.

[0102] S210. The remote UE configures the SRAP entity according to the configuration information.

[0103] As mentioned earlier, the first message (e.g., RRC recovery message or RRC reconstruction message) may include configuration information. Therefore, the remote UE can also configure (or reconfigure) the SRAP entity according to the configuration information. For example, the remote UE can configure the SRAP entity according to the second identifier included in the configuration information, so that the SRAP entity applies the second identifier. In subsequent communications, the SRAP entity can identify whether the destination device of the received data packet is the remote UE according to the second identifier. When the relay UE sends data packets later, the second identifier can be added to the SRAP header of the data packet for the relay UE to determine the source of the data packet.

[0104] In this embodiment, the remote UE can pre-determine the SRAP entity. After receiving the first data packet with the SRAP header, the remote UE can remove the SRAP header through this entity, thereby obtaining the RRC reconstruction message or RRC recovery message, improving the success rate of RRC reconstruction or recovery for the remote UE. Furthermore, the remote UE can configure the SRAP entity based on the configuration information included in the RRC reconstruction message or RRC recovery message, ensuring proper recognition of messages with SRAP headers during subsequent communication. Moreover, the solution in this embodiment is relatively simple and easy to implement.

[0105] Please refer to the following. Figure 3 This is a flowchart of a second communication method provided in an embodiment of this application.

[0106] S301. The remote UE sends a second message to the relay UE. Correspondingly, the relay UE receives the second message from the remote UE.

[0107] For more information about S301, please refer to [link / reference]. Figure 2 Description of S201 in the illustrated embodiment.

[0108] S302. The relay UE sends information about the remote UE to the access network device. Correspondingly, the access network device receives the information about the remote UE from the relay UE. The information about the remote UE may include the L2 ID of the remote UE, which indicates that the remote UE accesses the network through the relay UE.

[0109] For more information about S302, please refer to [link / reference]. Figure 2 Description of S203 in the illustrated embodiment.

[0110] S303. The access network device sends the first identifier of the remote UE to the relay UE. Correspondingly, the relay UE receives the first identifier from the access network device. The first identifier is, for example, the local ID of the remote UE.

[0111] For more information about S303, please refer to [link / reference]. Figure 2 Description of S204 in the illustrated embodiment.

[0112] S304, The relay UE adds an SRAP header to the second message.

[0113] For more information about S303, please refer to [link / reference]. Figure 2 Description of S205 in the illustrated embodiment.

[0114] S305. The relay UE sends a second message with an added SRAP header to the access network device. Correspondingly, the access network device receives the second message with the added SRAP header from the relay UE. For example, the relay UE sends this second message with the added SRAP header to the access network device through the RLC bearer corresponding to the SRB0 message of the remote UE, where the second message is an SRB0 message, such as an RRC recovery request or RRC reconstruction request.

[0115] For more information about S305, please refer to [link / reference]. Figure 2 Description of S206 in the illustrated embodiment.

[0116] S306. The access network device sends a first message to the relay UE. Correspondingly, the relay UE receives the first message from the access network device.

[0117] For example, when an access network device sends a second data packet to a relay UE, the second data packet may include a first message and an SRAP header, which may include a first identifier. Optionally, the SRAP header may also include information about the SRB of the remote UE receiving the second data packet, such as the identifier of the remote UE's SRB1, or the RB ID information of the remote UE.

[0118] For more information about S306, please refer to [link / reference]. Figure 2 Description of S207 in the illustrated embodiment.

[0119] S307. The relay UE processes the SRAP header to obtain the first data packet. The first data packet does not include the first identifier.

[0120] Optionally, if the first condition is met, the relay UE can process the SRAP header; otherwise, the relay UE can choose not to process the SRAP header. For example, one implementation of the first condition is that the first message is the first downlink message sent by the access network device to the remote UE on SRB1. The relay UE can determine whether the first message is the first downlink message sent to the remote UE on SRB1 in the following way: if the relay UE receives an uplink message (e.g., the second message) from the remote UE on the PC5 RLC bearer or channel corresponding to SRB0, and after receiving the uplink message, the relay UE has not sent any downlink message to the remote UE on the RLC bearer corresponding to SRB1, then the relay UE can determine that the first message is the first downlink message sent by the access network device to the remote UE on SRB1.

[0121] For example, another implementation of the first condition is that the second data packet includes indication information. This indication information can indicate whether the SRAP header is being processed, or whether the first message is the first downlink message sent to the remote UE on SRB1. For instance, this indication information can be included in the SRAP header of the second data packet, or it can be included in the payload of the second data packet. This indication information can occupy one or more bits. In other words, the access network device can add this indication information to the second data packet, allowing the relay UE to process the SRAP header based on this indication information without needing to perform other judgments, thus simplifying the implementation for the relay UE.

[0122] In addition to the above, there may be other ways to implement the first condition, and this application embodiment does not limit them.

[0123] In this embodiment of the application, one way for the relay UE to process the SRAP header is that the relay UE removes the SRAP header through its SRAP entity (e.g., PC5 SRAP entity or Uu SRAP entity). Figure 3 Taking this as an example, one implementation where the first data packet does not include the first identifier is that the first data packet does not include the SRAP header.

[0124] S308. The relay UE sends a first data packet to the remote UE. Correspondingly, the remote UE receives the first data packet from the relay UE. For example, the relay UE receives an SRB1 message (such as an RRC recovery message or RRC reconstruction message) sent from the access network device to the remote UE. This SRB1 message is carried and sent between the access network device and the relay UE through this first data packet.

[0125] S309. The remote UE configures (or reconfigures) the SRAP entity according to the configuration information included in the first message.

[0126] For example, if the first data packet does not include an SRAP header, the RLC entity of the remote UE can deliver the first data packet to the PDCP entity of the remote UE after receiving it. The PDCP entity can parse the first data packet to obtain the first message, thus enabling the remote UE to successfully rebuild or restore RRC, thereby improving the success rate of remote UE's RRC rebuild or restoration.

[0127] In this embodiment, the remote UE does not need to predetermine the SRAP entity. For example, when the remote UE is released to the RRC inactive state, or when the remote UE fails in the RRC connected state, the SRAP entity can be released, and it is not necessary to pre-establish the SRAP entity after release. The first message may include configuration information. After receiving the first message, the remote UE can configure its SRAP entity according to the configuration information. Alternatively, the remote UE can establish its SRAP entity according to the configuration information. For example, the remote UE can configure the SRAP entity according to the second identifier included in the configuration information, so that the SRAP entity applies the second identifier. In subsequent communications, the SRAP entity can identify whether the destination device of the received data packet is the remote UE according to the second identifier.

[0128] In this embodiment, the relay UE can send a data packet with the SRAP header removed to the remote UE. This allows the remote UE to parse the data packet without pre-establishing an SRAP entity, improving the success rate of RRC reconstruction or RRC recovery for the remote UE and simplifying the implementation for the remote UE. Furthermore, the remote UE can configure the SRAP entity based on the configuration information included in the RRC reconstruction or RRC recovery message, thus enabling it to correctly recognize messages with the SRAP header during subsequent communication.

[0129] Please refer to the following. Figure 4 This is a flowchart of a third communication method provided in the embodiments of this application.

[0130] S401. The remote UE sends a second message to the relay UE. Correspondingly, the relay UE receives the second message from the remote UE.

[0131] For more information about S401, please refer to [link / reference]. Figure 2 S201 in the illustrated embodiment.

[0132] S402. The remote UE determines the SRAP entity. Alternatively, the remote UE obtains the SRAP entity.

[0133] For more information about the S402, please refer to [link / reference]. Figure 2 S202 in the illustrated embodiment.

[0134] S403. The relay UE sends information about the remote UE to the access network device. Correspondingly, the access network device receives the information about the remote UE from the relay UE. The information about the remote UE may include the L2 ID of the remote UE, which indicates that the remote UE accesses the network through the relay UE.

[0135] For more information about S403, please refer to [link / reference]. Figure 2 S203 in the illustrated embodiment.

[0136] S404. The access network device sends the first identifier of the remote UE to the relay UE. Correspondingly, the relay UE receives the first identifier from the access network device. The first identifier is, for example, the local ID of the remote UE.

[0137] For more information about S404, please refer to [link / reference]. Figure 2 S204 in the illustrated embodiment.

[0138] S405, the relay UE adds an SRAP header to the second message.

[0139] For more information about S405, please refer to [link / reference]. Figure 2 S205 in the illustrated embodiment.

[0140] S406. The relay UE sends a second message with an added SRAP header to the access network device. Correspondingly, the access network device receives the second message with the added SRAP header from the relay UE. For example, the relay UE sends this second message with the added SRAP header to the access network device through its SRB0.

[0141] S407. The access network device sends a first message to the relay UE. Correspondingly, the relay UE receives the first message from the access network device.

[0142] For example, when an access network device sends a second data packet to a relay UE, the second data packet may include a first message and an SRAP header, which may include a first identifier. Optionally, the SRAP header may also include information about the SRB of the remote UE receiving the second data packet, such as the identifier of the remote UE's SRB1, or the RB ID information of the remote UE.

[0143] For more information about the S407, please refer to [link / reference]. Figure 2 S207 in the illustrated embodiment.

[0144] S408, The relay UE processes the SRAP header to obtain the first data packet. The first data packet does not include the first identifier.

[0145] Optionally, the relay UE may process the SRAP header if the first condition is met. For details on the first condition, please refer to [link / reference needed]. Figure 3 S307 in the illustrated embodiment.

[0146] In this embodiment, one way for the relay UE to process the SRAP header is to process the first identifier included in the SRAP header. For example, one way for the relay UE to process the first identifier included in the SRAP header is to remove the first identifier from the SRAP header, then the SRAP header no longer includes the first identifier. Wherein, after the relay UE removes the first identifier from the SRAP header, the SRAP header may no longer include the configuration information of the first field (for an introduction to the first field, please refer to...). Figure 2 (as shown in the embodiment) Alternatively, the SRAP header may continue to include configuration information for the first field, but the first field is undefined or does not carry any information (or the first field is empty).

[0147] For example, another way for a relay UE to process the first identifier included in the SRAP header is to update (or replace) the first identifier in the SRAP header. Figure 4 For example, a relay UE can update the first identifier in the SRAP header to a third identifier, which is, for example, the default value.

[0148] In addition, the relay UE may process the first identifier included in the SRAP header in other ways, and this application embodiment does not impose any restrictions. After processing by the relay UE, a first data packet can be obtained (the first data packet is, for example, the data packet obtained by the relay UE after processing the SRAP header of the second data packet). The first data packet still includes the SRAP header, but the SRAP header no longer includes the first identifier.

[0149] S409. The relay UE sends a first data packet to the remote UE. Correspondingly, the remote UE receives the first data packet from the relay UE. For example, the relay UE receives an SRB1 message (such as an RRC recovery message or RRC reconstruction message) sent from the access network device to the remote UE. This SRB1 message is carried and sent between the access network device and the relay UE through the first data packet.

[0150] S410. The remote UE removes the SRAP header of the first data packet through the SRAP entity and obtains configuration information.

[0151] If the SRAP header of the first data packet does not include the identifier of the remote UE (first identifier), then the SRAP entity of the remote UE can remove the SRAP header and deliver the first data packet with the SRAP header removed to the PDCP entity of the remote UE. The PDCP entity can parse the first data packet with the SRAP header removed to obtain the first message, thereby enabling the remote UE to successfully rebuild or restore RRC, thus improving the success rate of RRC rebuilding or RRC restoration of the remote UE.

[0152] S411. The remote UE configures (or reconfigures) the SRAP entity according to the configuration information.

[0153] For more information about the S411, please refer to [link / reference]. Figure 2 S210 in the illustrated embodiment.

[0154] In this embodiment, the remote UE can predetermine the SRAP entity, and the relay UE can process the SRAP header of the data packet to be sent to the remote UE, so that the data packet no longer includes the first identifier. This allows the remote UE's SRAP entity to remove the SRAP header of the data packet and obtain an RRC reconstruction message or RRC recovery message, improving the success rate of RRC reconstruction or RRC recovery for the remote UE. Furthermore, the remote UE can configure the SRAP entity based on the configuration information included in the RRC reconstruction message or RRC recovery message, thus enabling it to correctly identify messages with SRAP headers during subsequent communication.

[0155] Please refer to the following. Figure 5 This is a flowchart of the fourth communication method provided in the embodiments of this application.

[0156] S501. The remote UE stores its first identifier. The first identifier is, for example, an identifier applied by the remote UE's SRAP entity, such as the remote UE's local ID. The first identifier may be obtained when the remote UE is in RRC connected state, or it may not be released when the remote UE fails in RRC connected state, or it may not be released when the remote UE is released to RRC inactive state.

[0157] Optionally, the remote UE may also store a second identifier of the remote UE, such as the L2ID of the remote UE. For example, if the remote UE maintains its context information, the remote UE may store the first and second identifiers in the context information.

[0158] S502, The access network device stores the first identifier of the remote UE.

[0159] For example, when the remote UE is in RRC connected state, the access network device can store the first identifier of the remote UE. Alternatively, after the access network device assigns a first identifier to the remote UE, it can store the first identifier of the remote UE.

[0160] Optionally, the access network device may also store a second identifier of the remote UE. For example, if the access network device also maintains context information of the remote UE, the access network device may also store the first and second identifiers in the context information.

[0161] S501 may be executed before S502, after S502, or simultaneously with S502.

[0162] S503. The remote UE sends a second message to the relay UE. Correspondingly, the relay UE receives the second message from the remote UE.

[0163] Optionally, the second message may include the first identifier.

[0164] For more information about S503, please refer to [link / reference]. Figure 2 S201 of the illustrated embodiment.

[0165] S504. The remote UE determines the SRAP entity. Alternatively, the remote UE obtains the SRAP entity.

[0166] If the remote UE has released the SRAP entity before performing RRC reconstruction or RRC recovery, the remote UE can establish an SRAP entity. For example, the remote UE can release the SRAP entity when it fails in RRC connected mode or when it is released to RRC inactive mode. Optionally, the remote UE can establish the SRAP entity according to the default configuration, or it can establish the SRAP entity without any configuration; for example, the remote UE can establish an SRAP entity with SRAP functionality. The SRAP entity established by the remote UE can apply a first identifier; for example, the SRAP entity includes configuration information in a first field, and the first field carries the first identifier. That is, the SRAP entity can identify erroneous packets based on the first identifier. If the SRAP entity of a data packet received by the remote UE does not include the first identifier, the remote UE can discard the data packet.

[0167] Alternatively, if the remote UE does not release the SRAP entity before performing RRC reconstruction or RRC recovery—for example, when the remote UE fails in RRC connected state or when released to RRC inactive state without releasing the SRAP entity—then, if the configuration of the unreleased SRAP entity has been released (e.g., the unreleased SRAP entity does not apply the first identifier), the remote UE can reconfigure the SRAP entity to apply the first identifier. Alternatively, if the unreleased SRAP entity already applies the first identifier, the remote UE does not need to process the SRAP entity; that is, it does not need to execute S504. Therefore, S504 is an optional step.

[0168] Specifically, if S504 is executed, it can be executed before, after, or simultaneously with S503, without any specific restrictions. For example, the SRAP entity can be established after the remote UE sends an RRC recovery request or an RRC reconstruction request, or when the remote UE is preparing to send an RRC recovery request or an RRC reconstruction request, or when the remote UE is preparing to initiate an RRC connection recovery or RRC connection reconstruction, or when or after timer T301 or timer T311 starts, or when or after timer T319 or timer T319a starts, or when the remote UE initiates an RRC connection recovery or RRC connection reconstruction.

[0169] S505, the relay UE sends information about the remote UE to the access network device. Correspondingly, the access network device receives the information about the remote UE from the relay UE. The information about the remote UE may include a second identifier of the remote UE, such as the remote UE's L2ID, which indicates that the remote UE accesses the network through the relay UE.

[0170] For more information about the S505, please refer to [link / reference]. Figure 2 S203 of the illustrated embodiment.

[0171] S506. The access network device sends the third identifier of the remote UE to the relay UE. Correspondingly, the relay UE receives the third identifier from the access network device. The third identifier is, for example, the local ID of the remote UE.

[0172] For example, the access network device can assign a third identifier to the remote UE and send the remote UE's SRAP configuration information to the relay UE. The SRAP configuration information may include the third identifier.

[0173] Optionally, after receiving the second identifier, the access network device can determine the first identifier of the remote UE based on the second identifier. For example, if the access network device stores the first and second identifiers in the context information of the remote UE, the first identifier can be retrieved using the second identifier as an index. If the access network device obtains the first identifier, it can prioritize allocating the first identifier when assigning an identifier to the remote UE. For example, if the second condition is met, the access network device can assign the first identifier to the remote UE, in which case the first identifier is the same as the third identifier; or, if the second condition is not met, the access network device can choose not to assign the first identifier to the remote UE, but instead assign a new identifier, in which case the first identifier is different from the third identifier.

[0174] One second condition is, for example, that the first identifier does not conflict with the identifiers of other remote UEs connected to (or served by) the relay UE. A relay UE may serve one or more remote UEs, and therefore, different remote UEs can be distinguished by their identifiers (e.g., local IDs). If the first identifier has already been assigned to other remote UEs served by the relay UE, it indicates a conflict between the first identifier and the identifiers of those other remote UEs. In this case, if the access network device continues to assign the first identifier to the remote UE, it will cause confusion among the different remote UEs served by the relay UE. Therefore, the access network device can assign a new identifier to the remote UE instead of reassigning the first identifier. Conversely, if the first identifier has not been assigned to other remote UEs served by the relay UE, it indicates that the first identifier does not conflict with the identifiers of those other remote UEs, and the access network device can continue to assign the first identifier to the remote UE.

[0175] In addition to the above, the second condition may have other implementation methods, which are not limited in the embodiments of this application.

[0176] S507, the relay UE adds an SRAP header to the second message.

[0177] The relay UE can add an SRAP header to the second message based on the received SRAP configuration information. This SRAP header includes a third identifier. Optionally, the SRAP header may also include information about the SRB used by the remote UE to send the second message, such as the identifier of the remote UE's SRB0 or ​​the remote UE's RB ID information.

[0178] S508. The relay UE sends a second message with an added SRAP header to the access network device. Correspondingly, the access network device receives the second message with the added SRAP header from the relay UE. For example, the relay UE sends this second message with the added SRAP header to the access network device through the RLC bearer corresponding to the SRB0 of the remote UE, where the second message is an SRB0 message, such as an RRC recovery request or an RRC reconstruction request.

[0179] Since the third identifier assigned by the access network device may be the same as or different from the first identifier, subsequent steps may include two branches. S509–S511 constitute branch 1; if the first identifier and the third identifier are the same, branch 1 can be executed. S512–S513 constitute branch 2; if the first identifier and the third identifier are different, or if the access network device has not obtained the first identifier of the remote UE (e.g., has not obtained the context information of the remote UE), branch 2 can be executed. Branch 1 and branch 2 are two parallel schemes, and either one can be selected for execution.

[0180] Optionally, if the access network device obtains the first identifier, before executing branch 1 or branch 2, the access network device can also determine whether the first identifier and the third identifier are the same. If the first identifier and the third identifier are the same, then branch 1 is executed; if the first identifier and the third identifier are different, then branch 2 is executed.

[0181] S509. The access network device sends a first message to the relay UE. Correspondingly, the relay UE receives the first message from the access network device. This first message is sent by the access network device to the remote UE via the relay UE in response to a second message sent by the remote UE via the relay UE. If the second message is an RRC reconstruction request, then the first message is an RRC reconstruction message; or, if the second message is an RRC recovery request, then the first message is an RRC recovery message. The first message may include configuration information that can be used to configure the SRAP entity of the remote UE, for example, the configuration information may include a first identifier. This configuration information is, for example, sl-L2RemoteConfig.

[0182] For example, when an access network device sends a second data packet to a relay UE, the second data packet may include a first message and an SRAP header, which may include a first identifier. Optionally, the SRAP header may also include information about the SRB of the remote UE receiving the second data packet, such as the identifier of the remote UE's SRB1, or the RB ID information of the remote UE.

[0183] S510, the relay UE sends a first data packet to the remote UE. Correspondingly, the remote UE receives the first data packet from the relay UE. For example, the relay UE receives an SRB1 message (such as an RRC recovery message or RRC reconstruction message) sent from the access network device to the remote UE. This SRB1 message is carried and sent between the access network device and the relay UE through the first data packet.

[0184] For more information about the S510, please refer to [link / reference]. Figure 2 S208 in the illustrated embodiment.

[0185] S511. The remote UE identifies the first identifier through the SRAP entity and removes the SRAP header of the first data packet to obtain configuration information.

[0186] The remote UE's SRAP entity applies the first identifier, and the SRAP header of the first data packet also includes the first identifier. Therefore, the SRAP entity verifies the first data packet and considers it a correct data packet. The SRAP entity can then remove the SRAP header, obtaining the first data packet with the SRAP header removed. This SRAP entity can then deliver the first data packet with the SRAP header removed to the remote UE's PDCP entity. The PDCP entity can parse the first data packet with the SRAP header removed to obtain the first message, thus enabling the remote UE's RRC reconstruction or recovery to succeed, thereby improving the success rate of remote UE's RRC reconstruction or recovery.

[0187] S512, The access network device sends a first message to the relay UE. Correspondingly, the relay UE receives the first message from the access network device.

[0188] The access network device can store the first identifier in the context information of the remote UE. Therefore, if the first identifier is different from the third identifier, or if the access network device fails to obtain the first identifier, the access network device can assume that the context information of the remote UE has changed. In this case, the access network device may no longer perform the RRC reconstruction or RRC recovery process, but instead will perform the RRC establishment process. Optionally, the first message is an RRC establishment message. This RRC establishment message may include configuration information, which can be used to configure the SRAP entity of the remote UE. For example, this configuration information may include the third identifier. This configuration information is, for example, sl-L2RemoteConfig.

[0189] For example, an access network device sends a second data packet to a relay UE via SRB0. The second data packet may include a first message and an SRAP header, which may include a third identifier. Optionally, the SRAP header may also include information about the SRB of the remote UE receiving the second data packet, such as the identifier of the remote UE's SRB0.

[0190] S513, the relay UE sends the first data packet to the remote UE. Correspondingly, the remote UE receives the first data packet from the relay UE.

[0191] After receiving the second data packet, the relay UE determines that the SRB used to receive the second data packet is SRB0. Since the relay UE and the remote UE do not add an SRAP header when transmitting on SRB0, the relay UE can remove the SRAP header of the second data packet to obtain the first data packet. The relay UE then sends the first data packet to the remote UE through the PC5 RLC bearer or channel corresponding to the remote UE's SRB0.

[0192] The first data packet does not include an SRAP header. After receiving the first data packet, the RLC entity corresponding to the remote UE's SRB0 can deliver it to the remote UE's PDCP entity. The PDCP entity can then parse the first data packet to obtain the first message, enabling the remote UE to establish an RRC connection, thereby improving the success rate of the remote UE connecting to the network.

[0193] S514. The remote UE configures (or reconfigures) the SRAP entity according to the configuration information.

[0194] S514 can be applied to both branch 1 and branch 2. For example, in branch 1, the remote UE can obtain the configuration information included in the first message after receiving the first message, and thus configure the SRAP entity. For example, the remote UE can configure the SRAP entity according to the first identifier included in the configuration information, so that the SRAP entity applies the first identifier. In subsequent communications, the SRAP entity can identify whether the destination device of the received data packet is the remote UE based on the first identifier.

[0195] Alternatively, for branch 2, after receiving the first message, the remote UE can configure its SRAP entity based on the configuration information included in the first message. For example, the remote UE can configure the SRAP entity based on the third identifier included in the configuration information, so that the SRAP entity applies the third identifier. In subsequent communications, the SRAP entity can identify whether the destination device of the received data packet is the remote UE based on the third identifier.

[0196] In this embodiment, the remote UE can obtain an SRAP entity using the unreleased first identifier, and the access network device can also preferentially allocate a first identifier to the remote UE, enabling the remote UE's SRAP entity to recognize the first message from the access network device, thus improving the success rate of RRC reconstruction or RRC recovery for the remote UE. If the access network device allocates other identifiers to the remote UE, it can also perform the RRC establishment process and transmit messages through SRB0. Messages transmitted through SRB0 do not need to have an SRAP header added, and the remote UE can also recognize the message. Therefore, the solution provided in this embodiment improves the success rate of the remote UE connecting to the network. Moreover, this embodiment enhances the configuration logic of the access network device with minimal modifications to the UE (remote UE and / or relay UE).

[0197] Figure 6 A schematic diagram of a communication device according to an embodiment of this application is provided. The communication device 600 may be... Figures 2 to 5 The access network device or its circuitry in any of the embodiments shown is used to implement the method corresponding to the access network device in the above method embodiments. Alternatively, the communication device 600 may be... Figure 2 The embodiments shown to Figure 5 The circuitry system of the remote UE in any of the embodiments shown is used to implement the method corresponding to the remote UE in the above method embodiments. Alternatively, the communication device 600 may be... Figure 2 The embodiments shown to Figure 5 The circuit system of the relay UE described in any of the embodiments shown is used to implement the method corresponding to the relay UE in the above method embodiments. Specific functions can be found in the descriptions of the above method embodiments. For example, one type of circuit system is a chip system.

[0198] The communication device 600 includes at least one processor 601. The processor 601 can be used for internal processing within the device to implement certain control processing functions. Optionally, the processor 601 includes instructions. Optionally, the processor 601 can store data. Optionally, different processors can be independent devices, located in different physical locations, or located on different integrated circuits. Optionally, different processors can be integrated into one or more processors, for example, integrated on one or more integrated circuits.

[0199] Optionally, the communication device 600 includes one or more memories 603 for storing instructions. Optionally, the memories 603 may also store data. The processor and the memories may be separate or integrated together.

[0200] Optionally, the communication device 600 includes a communication line 602 and at least one communication interface 604. Since the memory 603, communication line 602, and communication interface 604 are all optional, therefore... Figure 6 All are represented by dashed lines.

[0201] Optionally, the communication device 600 may further include a transceiver and / or an antenna. The transceiver can be used to send information to or receive information from other devices. The transceiver may be referred to as a transceiver unit, transceiver circuit, input / output interface, etc., and is used to realize the transmission and reception functions of the communication device 600 via the antenna. Optionally, the transceiver includes a transmitter and a receiver. For example, the transmitter can be used to generate a radio frequency (RF) signal from a baseband signal, and the receiver can be used to convert the RF signal back into a baseband signal.

[0202] Processor 601 may include a general-purpose central processing unit (CPU), a microprocessor, an application-specific integrated circuit (ASIC), or one or more integrated circuits for controlling the execution of programs according to the present application.

[0203] Communication line 602 may include a path for transmitting information between the aforementioned components.

[0204] Communication interface 604 uses any transceiver-like device for communicating with other devices or communication networks, such as Ethernet, radio access network (RAN), wireless local area network (WLAN), wired access network, etc.

[0205] The memory 603 may be a read-only memory (ROM) or other type of static storage device capable of storing static information and instructions, random access memory (RAM) or other type of dynamic storage device capable of storing information and instructions, or electrically erasable programmable read-only memory (EEPROM), compact disc read-only memory (CD-ROM) or other optical disc storage, optical disc storage (including compressed optical discs, laser discs, optical discs, digital universal optical discs, Blu-ray discs, etc.), magnetic disk storage media or other magnetic storage devices, or any other medium capable of carrying or storing desired program code in the form of instructions or data structures and accessible by a computer, but not limited thereto. The memory 603 may exist independently and be connected to the processor 601 via communication line 602. Alternatively, the memory 603 may be integrated with the processor 601.

[0206] The memory 603 stores computer execution instructions for implementing the scheme of this application, and its execution is controlled by the processor 601. The processor 601 executes the computer execution instructions stored in the memory 603, thereby implementing the communication method provided in the above embodiments of this application.

[0207] Optionally, the computer execution instructions in the embodiments of this application may also be referred to as application code, and the embodiments of this application do not specifically limit this.

[0208] In a specific implementation, as one example, processor 601 may include one or more CPUs, for example... Figure 6 CPU0 and CPU1 in the CPU.

[0209] In a specific implementation, as one example, the communication device 600 may include multiple processors, such as... Figure 6 Processors 601 and 608 are mentioned. Each of these processors can be a single-core (single-CPU) processor or a multi-core (multi-CPU) processor. A processor here can refer to one or more devices, circuits, and / or processing cores used to process data (e.g., computer program instructions).

[0210] when Figure 6 When the device shown is a chip, such as a chip for an access network device, a chip for a remote UE, or a chip for a relay UE, the chip includes a processor 601 (which may also include a processor 608), a communication line 602, a memory 603, and a communication interface 604. Specifically, the communication interface 604 may be an input interface, pins, or circuits, etc. The memory 603 may be a register, a cache, etc. The processor 601 and the processor 608 may be a general-purpose CPU, a microprocessor, an ASIC, or one or more integrated circuits for controlling the execution of a program that controls the communication method of any of the above embodiments.

[0211] This application embodiment can divide the device into functional modules according to the above method example. For example, each function can be divided into its own functional modules, or two or more functions can be integrated into one processing module. The integrated modules can be implemented in hardware or as software functional modules. It should be noted that the module division in this application embodiment is illustrative and only represents one logical functional division. In actual implementation, there may be other division methods. For example, when dividing the device into functional modules according to each function, Figure 7 A schematic diagram of an apparatus 700 is shown. This apparatus 700 can be an access network device, a remote UE, or a relay UE involved in the various method embodiments described above, or it can be a chip in an access network device, a chip in a remote UE, or a chip in a relay UE. The apparatus 700 includes a transmitting unit 701, a processing unit 702, and a receiving unit 703.

[0212] It should be understood that the device 700 can be used to implement the steps performed by the access network device, the remote UE, or the relay UE in the method of the embodiments of this application. The relevant features can be referred to the various embodiments above, and will not be repeated here.

[0213] Optional, Figure 7The functions / implementation processes of the transmitting unit 701, receiving unit 703, and processing unit 702 can be understood through... Figure 6 The processor 601 in the memory calls computer execution instructions stored in memory 603 to implement the function. Alternatively, Figure 7 The function / implementation process of the processing unit 702 can be achieved through... Figure 6 The processor 601 in the memory calls computer execution instructions stored in the memory 603 to implement this. Figure 7 The functions / implementation of the transmitting unit 701 and the receiving unit 703 can be understood through... Figure 6 It is implemented using the communication interface 604.

[0214] Optionally, when the device 700 is a chip or circuit, the functions / implementation of the transmitting unit 701 and the receiving unit 703 can also be implemented through pins or circuits, etc.

[0215] This application also provides a computer-readable storage medium storing a computer program or instructions that, when executed, implement the methods performed by the access network device, remote UE, or relay UE in the aforementioned method embodiments. Thus, the functions described in the above embodiments can be implemented as software functional units and sold or used as independent products. Based on this understanding, the technical solution of this application, in essence, or the part that contributes to it, or a part of the technical solution, can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) to execute all or part of the steps of the methods described in the various embodiments of this application. The storage medium includes various media capable of storing program code, such as USB flash drives, portable hard drives, ROM, RAM, magnetic disks, or optical disks.

[0216] This application also provides a computer program product comprising: computer program code, which, when run on a computer, causes the computer to perform the method executed by the access network device, remote UE, or relay UE in any of the foregoing method embodiments.

[0217] This application also provides a processing apparatus, including a processor and an interface; the processor is used to execute the methods performed by the access network device, remote UE, or relay UE involved in any of the above method embodiments.

[0218] In the above embodiments, implementation can be achieved entirely or partially through software, hardware, firmware, or any combination thereof. When implemented using software, it can be implemented entirely or partially in the form of a computer program product. The computer program product includes one or more computer instructions. When the computer program instructions are loaded and executed on a computer, all or part of the processes or functions described in the embodiments of this application are generated. The computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable device. The computer instructions can be stored in a computer-readable storage medium or transmitted from one computer-readable storage medium to another. For example, the computer instructions can be transmitted from one website, computer, server, or data center to another website, computer, server, or data center via wired (e.g., coaxial cable, fiber optic, digital subscriber line (DSL)) or wireless (e.g., infrared, wireless, microwave, etc.) means. The computer-readable storage medium can be any available medium that a computer can access or a data storage device such as a server or data center that integrates one or more available media. The available medium can be a magnetic medium (e.g., floppy disk, hard disk, magnetic tape), an optical medium (e.g., DVD), or a semiconductor medium (e.g., solid-state disk (SSD)).

[0219] The various illustrative logic units and circuits described in the embodiments of this application can be implemented or operate the described functions using a general-purpose processor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA), or other programmable logic devices, discrete gate or transistor logic, discrete hardware components, or any combination thereof. The general-purpose processor can be a microprocessor; alternatively, it can be any conventional processor, controller, microcontroller, or state machine. The processor can also be implemented using a combination of computing devices, such as a digital signal processor and a microprocessor, multiple microprocessors, one or more microprocessors combined with a digital signal processor core, or any other similar configuration.

[0220] The steps of the methods or algorithms described in the embodiments of this application can be directly embedded in hardware, software units executed by a processor, or a combination of both. The software units can be stored in RAM, flash memory, ROM, erasable programmable read-only memory (EPROM), EEPROM, registers, hard disks, removable disks, CD-ROMs, or any other form of storage medium in the art. Exemplarily, the storage medium can be connected to the processor so that the processor can read information from the storage medium and write information to the storage medium. Optionally, the storage medium can also be integrated into the processor. The processor and storage medium can be disposed in an ASIC, which can be disposed in the terminal device. Optionally, the processor and storage medium can also be disposed in different components of the terminal device.

[0221] These computer program instructions may also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer-implemented process, such that the instructions, which execute on the computer or other programmable apparatus, provide steps for implementing the functions specified in one or more flowcharts and / or one or more block diagrams.

[0222] Although embodiments of this application have been described in conjunction with specific features and examples, it is obvious that various modifications and combinations can be made thereto without departing from the scope of the embodiments of this application. Accordingly, the embodiments and drawings of this application are merely exemplary illustrations of the embodiments of this application as defined by the appended claims, and are considered to cover any and all modifications, variations, combinations, or equivalents within the scope of the embodiments of this application. Obviously, those skilled in the art can make various modifications and variations to the embodiments of this application without departing from the scope of the embodiments of this application. Thus, if these modifications and variations of the embodiments of this application fall within the scope of the claims of the embodiments of this application and their equivalents, then the embodiments of this application are also intended to include these modifications and variations.

Claims

1. A communication method, characterized in that, Applied to remote terminal devices, the method includes: The remote terminal device receives a first data packet from the relay terminal device via its SRB1. The first data packet includes a first message and an SRAP header. The first message is either an RRC connection recovery message or an RRC reconstruction message. The SRAP header is removed through the SRAP entity to obtain configuration information. The SRAP entity is determined before the SRAP header is removed. Configure the SRAP entity according to the configuration information.

2. The method according to claim 1, characterized in that, The method further includes: The SRAP entity is established before the SRAP header is removed.

3. The method according to claim 2, characterized in that, Establishing the SRAP entity before removing the SRAP header includes: Before removing the SRAP header, the SRAP entity is created according to the default configuration.

4. The method according to claim 1, characterized in that, The SRAP entity is the one that was not released when the remote terminal device was released to the RRC inactive state.

5. The method according to claim 4, characterized in that, The method further includes: Before removing the SRAP header, reconfigure the SRAP entity that has not been released.

6. The method according to any one of claims 1 to 5, characterized in that, The SRAP entity does not include the configuration information for the first domain; or, The SRAP entity includes the configuration information of the first domain, and the first domain is either an undefined domain or carries a default value. The first field is used to carry the identifier of the remote terminal device.

7. The method according to any one of claims 1 to 5, characterized in that, The SRAP header includes a first identifier, which is the identifier of the remote terminal device; or... The SRAP header does not include the identifier of the remote terminal device.

8. The method according to any one of claims 1 to 5, characterized in that, The method further includes: Configure the SRAP entity according to the configuration information, including: Configure the SRAP entity according to the second identifier included in the configuration information, wherein the second identifier is the identifier of the remote terminal device.

9. A communication device, characterized in that, include: One or more processors; One or more memory units; And one or more computer programs, wherein the one or more computer programs are stored in the one or more memories, the one or more computer programs including instructions that, when executed by one or more processors of the communication device, cause the communication device to perform the method as described in any one of claims 1 to 8.

10. A computer-readable storage medium, characterized in that, The computer-readable storage medium is used to store a computer program that, when run on a computer, causes the computer to perform the method as described in any one of claims 1 to 8.

11. A chip, characterized in that, It includes one or more processors and a communication interface, wherein the one or more processors are used to read instructions to execute the method as described in any one of claims 1 to 8.