Communication method and device

By detecting and releasing side link disconnects, the problem that the local identity allocated by the relay UE cannot be recovered is solved, the reuse of the identity and the forwarding service from the terminal to the network is ensured, and the system's identity management efficiency is improved.

CN113873580BActive Publication Date: 2024-11-22HUAWEI TECH CO LTD
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202010612136.3
Authority / Receiving Office
CN · China
Patent Type
Patents(China)
Current Assignee / Owner
Filing Date
2020-06-30
Publication Date
2024-11-22
Estimated Expiration
2040-06-30

AI Technical Summary

Technical Problem

In the relay scenario of the LTE user equipment to the network, the local identity allocated by the relay UE cannot be effectively retracted, resulting in the identity being exhausted and the terminal to the network cannot be provided for forwarding services.

Method used

By detecting the disconnection of the side link, the second terminal device or the first network device deletes the association relationship with the first terminal device, releases the local identity and corresponding routing information, ensuring that the identity can be reused by other terminal devices.

Benefits of technology

It effectively avoids the situation of exhaustion of the logo, ensures that the new remote UE can provide terminal-to-network forwarding services when accessing the relay UE, and improves the system's identification management efficiency.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN113873580B_ABST
    Figure CN113873580B_ABST
Patent Text Reader

Abstract

The present application provides a communication method and apparatus, which can effectively reclaim a local identifier localid. A second terminal device forwards data of a first terminal device to communicate with a first network device, the second terminal device communicates with the first terminal device via a side link, and the second terminal device communicates with the first network device via a wireless network. The method includes: the second terminal device determines that the side link is disconnected; the second terminal device deletes the association between the first identifier and the first terminal device, the first identifier is used to identify the first terminal device, and the first identifier is allocated by the second terminal device or the first network device to the first terminal device.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] The present application relates to the field of communications, and more specifically, to a communication method and device. Background Art

[0002] In the long term evolution (LTE) user equipment (UE) to network relay (UE-network relay) application scenario, the remote user equipment (remote UE) and the relay user equipment (relay UE) communicate through the sidelink (SL), and the relay UE and the network equipment communicate through the wireless network.

[0003] After the relay UE receives data sent by a remote UE, it determines that it needs to continue forwarding to the network device. However, in order to let the network device know which remote UE sent the data, it needs to carry the identifier of the remote UE. If the cell-radio network temporary identifier (C-RNTI) or layer 2 identifier of the remote UE is used, the air interface overhead is large because the lengths of these two identifiers are long. Therefore, the relay UE or the network device assigns a shorter local identifier (local identifier, local id) to the remote UE, and uses the local id to identify the remote UE when the relay UE forwards the remote UE's data to the network device.

[0004] Currently, only how to allocate local IDs is considered, but no mechanism for revoking or deleting local IDs is considered. If the local IDs allocated by the relay UE cannot be revoked, the local IDs will be used up, and when a new remote UE accesses the relay UE, the terminal to network (U2N) forwarding service cannot be provided. Summary of the invention

[0005] The present application provides a communication method and apparatus that can effectively retrieve a local ID and / or delete corresponding routing information.

[0006] In a first aspect, a communication method is provided, which can be executed by a second terminal device or by a component of the second terminal device, such as a processor, a chip, or a chip system. The method is introduced by taking the execution of the second terminal device as an example. The second terminal device forwards data of the first terminal device to communicate with the first network device, the second terminal device communicates with the first terminal device via a side link, and the second terminal device communicates with the first network device via a wireless network. The method includes: the second terminal device determines that the side link is disconnected; the second terminal device deletes the association between a first identifier and the first terminal device, the first identifier is used to identify the first terminal device, and the first identifier is allocated by the second terminal device or the first network device to the first terminal device.

[0007] Based on the above technical solution, after the second terminal device determines that the side link between it and the first terminal device is disconnected, the second terminal device deletes the association between the first identifier and the first terminal device. Therefore, the first identifier can be used to identify other terminal devices, thereby avoiding the situation where other terminal devices are unable to establish a connection with the second terminal device when the identifier is exhausted.

[0008] In a possible implementation, the second terminal device deletes the association between the first identifier and the first terminal device, including one or more of the following: the second terminal device releases the first identifier and / or corresponding routing information, and the second terminal device releases the context of the first terminal device.

[0009] In one possible implementation, the second terminal device determines that the side link is disconnected, including: the second terminal device starts a first timer after receiving data sent by the first terminal device to the network device, and / or the second terminal device receives data sent by the first network device to the first terminal device; if the second terminal device does not receive the data sent by the first terminal device before the first timer expires, and / or the second terminal device does not receive the data sent by the first network device to the first terminal device before the first timer expires, then it is determined that the side link is disconnected.

[0010] In a possible implementation, the method further includes: the second terminal device sends first indication information to the first network device, wherein the first indication information indicates that the side link is disconnected.

[0011] In a possible implementation, the method further includes: the first indication information is side link terminal information, the side link terminal information does not carry a first target identifier, and the first target identifier corresponds to the first identifier of the first terminal device.

[0012] In a possible implementation, the second terminal device determines that the sidelink is disconnected, including: the second terminal device receives second indication information sent by the first terminal device, and the second indication information indicates that the sidelink is disconnected.

[0013] In a possible implementation, the second terminal device determines that the side link is disconnected, including: the second terminal device receives third indication information sent by the first network device, and the third indication information indicates that the side link is disconnected.

[0014] In a possible implementation, the method further includes: the second terminal device determines that the sidelink is disconnected according to a logical channel configuration, and the logical channel configuration is related to the first terminal device.

[0015] In a possible implementation manner, the first identifier is a local identifier (local id).

[0016] In a second aspect, a communication method is provided, in which a first terminal device communicates with a first network device by forwarding data through a second terminal device, the first terminal device and the second terminal device communicate through a side link, and the first network device and the second terminal device communicate through a wireless network. The method can be executed by the first network device, and can also be executed by a component of the first network device, such as a processor, a chip, or a chip system. The method is introduced by taking the execution of the first network device as an example, and the method includes: the first network device determines that the side link is disconnected; the first network device deletes the association between a first identifier and the first terminal device, the first identifier is associated with the identifier of the second terminal device, the first identifier is used to identify the first terminal device, and the first identifier is allocated to the first terminal device by the second terminal device or by the first network device.

[0017] In a possible implementation, the first network device deletes the association between the first identifier and the first terminal device, including one or more of the following: the first network device releases the first identifier, and the first network device releases the context of the first terminal device.

[0018] In one possible implementation, the first network device determines that the side link is disconnected, including: the first network device starts a second timer after receiving the data of the first terminal device sent by the second terminal device, and / or after the first network device sends the data of the first terminal device to the second terminal device; if the first network device does not receive the data of the first terminal device before the second timer expires, and / or the first network device does not send the data of the first terminal device to the second terminal device before the second timer expires, then it is determined that the side link is disconnected.

[0019] In one possible implementation, the first network device determines that the side link is disconnected, including: the first network device receives fourth indication information sent by the second network device, and the fourth indication information includes at least one of the following information: requesting to obtain the context of the first terminal device, releasing the context of the first terminal device, and switching permission.

[0020] In a possible implementation, the method further includes: the first network device sending third indication information to the second terminal device, wherein the third indication information indicates that the side link is disconnected.

[0021] In a possible implementation, the method further includes: the second terminal device determines that the sidelink is disconnected according to a logical channel configuration, and the logical channel configuration is related to the first terminal device.

[0022] In a possible implementation, the first network device determines that the side link is disconnected, including: the first network device receives first indication information sent by the second terminal device, and the first indication information indicates that the side link is disconnected.

[0023] In a possible implementation, the first indication information is side link terminal information, the side link terminal information does not carry a first target identifier, and the first target identifier corresponds to the first identifier of the first terminal device.

[0024] In a possible implementation, the first network device determines that the side link is disconnected, including: the first network device receives second indication information sent by the first terminal device, and the second indication information indicates that the side link is disconnected.

[0025] According to a third aspect, a communication method is provided, in which a first terminal device communicates with a first network device by forwarding data through a second terminal device, the first terminal device and the second terminal device communicate via a side link, and the second terminal device and the first network device communicate via a wireless network. The method can be executed by the first terminal device, or by a component of the first terminal device, such as a processor, a chip, or a chip system. The method is introduced by taking the execution of the first terminal device as an example, and the method includes: the first terminal device determines to disconnect the side link connection; the first terminal device sends a second indication message, and the second indication message is used to indicate that the side link is disconnected.

[0026] In one possible implementation, the first terminal device determines to disconnect the side link connection, including: the first terminal device determines to disconnect the side link connection according to one or more of the following: wireless connection failure, switching failure, and a third timer.

[0027] In a possible implementation, the first terminal device determines to disconnect the sidelink connection, including: the first terminal device receives fifth indication information, and the fifth indication information is used to indicate to disconnect the sidelink connection.

[0028] In a possible implementation manner, the fifth indication information includes at least one of the following information sent by the first network device: radio resource control RRC release, radio resource control RRC rejection, and switching command.

[0029] In a possible implementation manner, the fifth indication information includes a radio resource control RRC re-establishment notification sent by the second network device.

[0030] In a possible implementation manner, the first terminal device sending the second indication information includes: the first terminal device sending the second indication information to the second terminal device.

[0031] In a possible implementation manner, the first terminal device sending the second indication information includes: the first terminal device sending the second indication information to the first network device.

[0032] In a fourth aspect, a communication method is provided, in which a second terminal device forwards data of at least one first terminal device to communicate with a first network device, the second terminal device communicates with the at least one first terminal device via a side link, and the second terminal device communicates with the first network device via a wireless network. The method may be executed by the second terminal device, or by a component of the second terminal device, such as a processor, a chip, or a chip system. The method is described by taking the execution of the second terminal device as an example, and the method includes:

[0033] The second terminal device sends a radio resource control RRC reconstruction request or an RRC recovery request message to the second network device, and the RRC reconstruction request message or the RRC recovery request message includes sixth indication information, and the sixth indication information is used to instruct the second network device to obtain the context of the first terminal device from the first network device.

[0034] In a possible implementation manner, the sixth indication information includes an identifier of the at least one first terminal device.

[0035] In a possible implementation, before the second terminal device sends a radio resource control (RRC) reestablishment request message to the second network device, the method further includes: the second terminal device disconnecting the wireless network communication connection with the first network device.

[0036] In a fifth aspect, a communication method is provided, including: a first terminal device sends a radio resource control RRC establishment request message to a second terminal device using a first logical channel, wherein the first logical channel is used to send the RRC establishment request message, the radio resource control RRC establishment message, and a handover permission;

[0037] The second terminal device forwards the RRC establishment request message to the first network device by using a second logical channel, where the second logical channel is allocated by the first network device to the second terminal device;

[0038] The first network device receives the RRC establishment request message;

[0039] The first network device sends the RRC establishment message to the second terminal device by using the second logical channel according to the RRC establishment request message;

[0040] The second terminal device sends the RRC establishment message to the first terminal device using the first logical channel.

[0041] In a sixth aspect, a communication method is provided, in which a first terminal device communicates with a first network device by forwarding data through a second terminal device, the first terminal device communicates with the second terminal device through a side link, and the second terminal device communicates with the first network device through a wireless network. The method can be executed by the first terminal device, or by a component of the first terminal device, such as a processor, a chip, or a chip system. The method is described by taking the execution of the first terminal device as an example. The method includes:

[0042] The first terminal device obtains the radio access network area code RANAC and all wireless network temporary identification indication information of the serving cell where the second terminal device is located;

[0043] The first terminal device sends a radio resource control RRC establishment request message to the first network device according to the RANAC and the indication information of all radio network temporary identities.

[0044] In a possible implementation, the first terminal device obtains the radio access network area code RANAC and all wireless network temporary identification indication information of the service cell where the second terminal device is located, including: the first terminal device sends a request message for obtaining the RANAC to the second terminal device; the first terminal device receives the RANAC sent by the second terminal device.

[0045] In a possible implementation, the first terminal device obtains the radio access network area code RANAC and all wireless network temporary identification indication information of the service cell where the second terminal device is located, including: the first terminal device receives a system broadcast message periodically sent by the second terminal device; the first terminal device obtains the RANAC and all wireless network temporary identification indication information according to the system broadcast message.

[0046] In a seventh aspect, a communication method is provided, in which a first terminal device communicates with a first network device by forwarding data through a second terminal device, the first terminal device communicates with the second terminal device through a side link, and the second terminal device communicates with the first network device through a wireless network. The method can be executed by the first terminal device, or by a component of the first terminal device, such as a processor, a chip, or a chip system. The method is described by taking the execution of the first terminal device as an example, and the method includes:

[0047] The first terminal device obtains a physical cell identifier PCI of a serving cell where the second terminal device is located;

[0048] The first terminal device sends the PCI to the second network device, so that the second network device obtains the context of the first terminal device from the first network device.

[0049] In a possible implementation, the first terminal device obtains the physical cell identifier PCI of the second terminal device, including: the first terminal device sends a request message for obtaining the PCI to the second terminal device; and the first terminal device receives the PCI sent by the second terminal device.

[0050] In a possible implementation, the first terminal device obtains the physical cell identifier PCI of the second terminal device, including: the first terminal device receives a system broadcast message periodically sent by the second terminal device; and the first terminal device obtains the PCI according to the system broadcast message.

[0051] In an eighth aspect, a communication device is provided, comprising a unit for implementing the functions of the method in the first aspect or any possible implementation manner of the first aspect.

[0052] In a ninth aspect, a communication device is provided, comprising a unit for implementing the functions of the method in the second aspect or any possible implementation manner of the second aspect.

[0053] In a tenth aspect, a communication device is provided, comprising a unit for implementing the functions of the method in the third aspect or any possible implementation manner of the third aspect.

[0054] In the eleventh aspect, a communication device is provided, comprising: a processor and a transceiver, wherein the transceiver is used to receive computer code or instructions and transmit them to the processor, and the processor executes the computer code or instructions, such as the method in the first aspect or any possible implementation of the first aspect.

[0055] In the twelfth aspect, a communication device is provided, comprising: a processor and a transceiver, wherein the transceiver is used to receive computer code or instructions and transmit them to the processor, and the processor executes the computer code or instructions, such as the method in the second aspect or any possible implementation of the second aspect.

[0056] In the thirteenth aspect, a communication device is provided, comprising: a processor and a transceiver, wherein the transceiver is used to receive computer code or instructions and transmit them to the processor, and the processor executes the computer code or instructions, such as the method in the third aspect or any possible implementation of the third aspect.

[0057] In a fourteenth aspect, a communication system is provided, comprising the first terminal device and the second terminal device in the method described in the first aspect, the second aspect or the third aspect.

[0058] In a possible implementation manner, the communication system further includes: the first network device in the method described in the first aspect, the second aspect, or the third aspect.

[0059] In a fifteenth aspect, a computer-readable storage medium is provided, wherein the computer-readable medium stores a computer program; when the computer program runs on a computer, the computer executes the method in the first aspect or any possible implementation of the first aspect.

[0060] In the sixteenth aspect, a computer-readable storage medium is provided, wherein the computer-readable medium stores a computer program; when the computer program runs on a computer, the computer executes the method in the second aspect or any possible implementation of the second aspect.

[0061] In the seventeenth aspect, a computer-readable storage medium is provided, wherein the computer-readable medium stores a computer program; when the computer program runs on a computer, the computer executes the method in the third aspect or any possible implementation of the third aspect. BRIEF DESCRIPTION OF THE DRAWINGS

[0062] Figure 1 This is a schematic diagram of UE and UE communicating through the PC5 interface according to an embodiment of the present application.

[0063] Figure 2 A schematic flowchart of a communication method according to an embodiment of the present application.

[0064] Figure 3 This is a schematic diagram of the process interaction of the relay UE sending the first indication information to the base station after determining that the side link is disconnected in an embodiment of the present application.

[0065] Figure 4 This is a schematic diagram of the 1:1 mapping relationship between SL LCH and Uu LCH in an embodiment of the present application.

[0066] Figure 5 This is a schematic diagram of the N:1 mapping relationship between SL LCH and Uu LCH in an embodiment of the present application.

[0067] Figure 6 A schematic flowchart of another communication method according to an embodiment of the present application.

[0068] Figure 7 This is a schematic diagram of the interaction process of a source base station receiving a handover permission sent by a target base station during the HO process of an embodiment of the present application.

[0069] Figure 8A schematic diagram of a process interaction in which a first network device sends third indication information to a relay UE after receiving a handover permission message sent by a target base station in an embodiment of the present application.

[0070] Fig. 9 This is a schematic diagram of the process interaction of a source base station receiving, during the RRC reconstruction process, obtaining the context of a first terminal device and releasing the context of the first terminal device in an embodiment of the present application.

[0071] Fig.10 This is a schematic diagram of the process interaction of sending third indication information to the relay UE after the first network device of an embodiment of the present application receives a context message for obtaining the first terminal device / releasing the context message for the first terminal device sent by the target base station.

[0072] Fig.11 A schematic flowchart of another communication method according to an embodiment of the present application.

[0073] Fig.12 A schematic diagram of the process interaction of a remote UE receiving a handover command sent by a source base station during the HO process of an embodiment of the present application.

[0074] Fig.13 This is a schematic diagram of a process interaction in which a remote UE sends second indication information to a relay UE after receiving a HO CMD according to an embodiment of the present application.

[0075] Fig.14 This is a schematic diagram of the process interaction of sending second indication information to the relay UE after the remote UE receives the RRC release / RRC rejection message sent by the base station in an embodiment of the present application.

[0076] Fig.15 A schematic flowchart of another communication method according to an embodiment of the present application.

[0077] Fig.16 A schematic diagram of the process interaction of a target base station acquiring the context of a relay UE and its remote UE according to an RRC reconstruction request message sent by a relay UE during an RRC reconstruction process in an embodiment of the present application.

[0078] Fig.17 This is an internal implementation block diagram when multiple SL LCHs of the remote UE of an embodiment of the present application are multiplexed on one Uu LCH.

[0079] Fig.18 A schematic block diagram of a communication device according to an embodiment of the present application.

[0080] Fig.19 A schematic block diagram of another communication device according to an embodiment of the present application.

[0081] Fig. 20 A schematic block diagram of another communication device according to an embodiment of the present application.

[0082] Fig.21 A schematic block diagram of another communication device according to an embodiment of the present application.

[0083] Fig. 22 A schematic block diagram of a communication system according to an embodiment of the present application. DETAILED DESCRIPTION

[0084] The technical solution in this application will be described below in conjunction with the accompanying drawings.

[0085] The embodiments of the present application can be applied to various communication systems, such as wireless local area network (WLAN), narrowband Internet of Things (NB-IoT), global system for mobile communications (GSM), enhanced data rate for GSM evolution (EDGE), wideband code division multiple access (WCDMA), code division multiple access 2000 (CDMA2000), time division-synchronization code division multiple access (TD-SCDMA), long term evolution (LTE), satellite communication, fifth generation (5G) system or new communication systems that will appear in the future.

[0086] The terminal devices involved in the embodiments of the present application may include various handheld devices, vehicle-mounted devices, wearable devices, computing devices or other processing devices connected to a wireless modem with wireless communication functions. The terminal may be a mobile station (MS), a subscriber unit (subscriber unit), a user equipment (UE), a cellular phone (cellular phone), a smart phone (smart phone), a wireless data card, a personal digital assistant (PDA) computer, a tablet computer, a wireless modem (modem), a handheld device (handset), a laptop computer (laptop computer), a machine type communication (MTC) terminal, etc.

[0087] In a wireless communication system, UEs can communicate with each other through a network, or they can communicate with each other directly without the help of network equipment, such as Figure 1 As shown in the figure, the direct communication interface between UE1 and UE2 is called PC5 interface, which is similar to the Uu interface between UE and the network. The link between UE and UE is called sidelink (SL). Currently, PC5 interface has been used for device to device (D2D) communication and vehicle to everything (V2X). In the Internet of Vehicles, each vehicle is a UE, and data can be directly transmitted between UE and UE through Sidelink without going through the network, which can effectively reduce communication delay.

[0088] Broadcast, unicast and multicast are supported on Sidelink.

[0089] Broadcast communication is similar to base station broadcasting system information, that is, the UE sends broadcast service data to the outside without encryption, and any other UE within the effective range can receive the broadcast service data if it is interested in the broadcast service.

[0090] Unicast communication is similar to data communication after a radio resource control (RRC) connection is established between a UE and a base station. It requires a unicast connection to be established between two UEs. After the unicast connection is established, the two UEs can communicate data based on the negotiated identifier. The data can be encrypted or unencrypted. Compared with broadcast communication, in unicast communication, unicast communication can only be performed between two UEs after a unicast connection is established.

[0091] Multicast communication refers to the communication between all UEs in a communication group. Any UE in the group can send and receive data of the multicast service.

[0092] In order to expand network coverage and reduce UE power consumption, a relay UE is introduced between the UE and the network. If the remote UE is at the edge of the network coverage or has no network coverage, it can communicate with the network through the forwarding data of the relay UE. The remote UE and the relay UE communicate through the PC5 interface, and the relay UE and the network communicate through the Uu interface.

[0093] In the long term evolution (LTE) SL UE-Network relay, for the layer 2 (L2) relay mode, a relay UE can be connected to multiple remote UEs, so an adaptation layer (AL) is added to the protocol stack between the relay UE and the gNB. Taking uplink data transmission as an example, after receiving SL data from a remote UE, the relayUE knows that it will eventually continue to send it upward to the network. However, in order for the network to know which remote UE sent the data, it is necessary to carry a remote UE identifier in the AL layer. The identifier can directly use the cell radio network temporary identifier (C-RNTI) or SL L2 id of the remote UE, but the lengths of these two identifiers are relatively long. For example, C-RNTI is 16 bits (bit) in the prior art, and SL L2 id is 24 bits. If they are used directly, the overhead on the air interface is large. Therefore, it is necessary to carry a shorter local identifier (local identifier, local id), such as 1 byte, which can support up to 256 remote UEs, for identifying different remote UEs under the relay UE, and for informing the network which remote UE sent the data. The remote UE identifier only works between the relay UE and the network device, and does not work between the remote UE and the relay UE. On the SL, the different SL L2 IDs between the remote UE and the relay UE can be used to distinguish which remote UE's data belongs to.

[0094] In the current technical solution, only how to allocate local ID is considered, but the mechanism of reclaiming or deleting local ID is not considered. If the local ID allocated by relay UE cannot be reclaimed, the local ID will be exhausted, and when a new remote UE accesses the relay UE, the terminal to network (UE to network, U2N) forwarding service cannot be provided. Therefore, the embodiment of the present application proposes a communication method that can effectively reclaim the local ID.

[0095] In order to facilitate the understanding of the technical solution of the present application, a handover (HO) process, a radio resource control (RRC) re-establishment process, and an RRC release / RRC rejection involved in the technical solution of the present application are briefly described.

[0096] 1. The HO process includes:

[0097] 1) UE reports measurement report to source base station;

[0098] 2) The source base station makes a handover decision;

[0099] 3) The source base station sends a handover request (ho request) message to the target base station;

[0100] 4) The target base station performs admission control to see whether to allow the UE to enter the cell;

[0101] 5) If allowed, the target base station replies to the source base station with a handover permission message, ie, an acknowledgement (ACK) message.

[0102] 6) The source base station sends a handover command (HO CMD) to the UE;

[0103] 7) The source base station sends a sequence number (SN) state transfer message to the target base station, telling it which packet data convergence protocol (PDCP) service data unit (SDU) data packets are received and which are not received;

[0104] 8) After receiving the HO CMD, the UE immediately disconnects from the source base station and attempts to access the target base station. If the access is successful, it sends a HO complete message to the target base station;

[0105] 9) After the UE successfully accesses the target base station, the target base station sends a path switching request message to the access and mobility management function (AMF), requesting to change the forwarding address of the downlink data, so that the AMF will subsequently send the UE's downlink data packet to the target base station instead of the source base station;

[0106] 10) After receiving the path switching request message, the AMF notifies the user plane function (UPF) to perform path switching;

[0107] 11) If the path switching is successful, the AMF replies with a path switching confirmation message to the target base station;

[0108] 12) After the UE successfully accesses the target base station, the target base station sends a notification message to release the context of the UE to the source base station, so that the source base station releases the context of the UE.

[0109] 2. The RRC reconstruction process includes:

[0110] 1) After a radio link failure (RLF) or handover failure (HOF) occurs in the UE, the RRC reestablishment process is performed. The UE first selects a cell that meets the connection conditions and then sends an RRC reestablishment request message on the cell;

[0111] 2) After receiving the RRC reestablishment request message, the target base station searches for the original serving cell of the UE according to the information carried in the message, and sends a context request message for obtaining the UE;

[0112] 3) After receiving the request message in the UE context, the source base station replies with a response message for obtaining the UE context, where the response message includes the UE context;

[0113] 4) If the target base station successfully obtains the context of the UE, an RRC re-establishment notification message is sent to the UE; it should be understood that if the target base station fails to obtain the context of the UE, an RRC reconfiguration message may be sent to the UE;

[0114] 5) If the UE receives the RRC reestablishment notification message, it considers that the RRC reestablishment is successful and sends an RRC reestablishment completion message to the target base station; if the UE receives the RRC reconfiguration message, it sends an RRC reconfiguration completion message to the target base station;

[0115] 6) After the UE is successfully reestablished, the target base station provides the source base station with an XN-U address;

[0116] 7) After the source base station obtains the XN-U address, it forwards the UE's cached data packets in the source base station to the target base station; and sends an SN status transfer message to the target base station to notify which data packets are received and which are not received;

[0117] 8) The target base station sends a path switching request message to the AMF, requesting to change the downlink data packet forwarding address, so that the AMF subsequently sends the UE's downlink data packet to the target base station instead of the source base station;

[0118] 9) After receiving the path switching request message, the AMF notifies the user plane function (UPF) to perform path switching;

[0119] 10) If the path switching is successful, the AMF replies with a path switching confirmation message to the target base station;

[0120] 11) After receiving the path switch positive confirmation message, the target base station sends a context notification message of releasing the UE to the source base station, so that the source base station releases the context of the UE.

[0121] 3. The UE receives the RRC release / RRC rejection message sent by the network device and enters the idle state / inactive state.

[0122] When the UE supports the inactive state, the base station still maintains the UE context, instead of not maintaining the UE context on the network side like the UE in the idle state; the advantage of maintaining the UE context is that when the UE enters the connected state next time, since the network already has the UE context, some processes can be omitted, such as security negotiation, bearer configuration, UE capability negotiation, etc., so that it can quickly enter the connected state and then quickly transmit data.

[0123] The RRC release message sent by the base station to the UE carries a suspend configuration, such as full-RNTI, short-RNTI, ran-paging cycle, and timer t380.

[0124] 1. Enter the inactive state process 1

[0125] 1) UE initiates RRC re-establishment request;

[0126] 2) The target base station successfully requests the UE context from the source base station;

[0127] 3) The target base station decides to keep the UE in the inactive state;

[0128] 4) The target base station notifies the AMF to perform path switching;

[0129] 5) The target base station generates and sends an RRC release message to the UE;

[0130] 6) The target base station informs the source base station to release the UE context.

[0131] 2. Enter the inactive state process 2

[0132] 1) UE initiates RRC re-establishment request;

[0133] 2) The target base station fails to request the UE context from the source base station. In this case, the source base station has the UE context but does not want to provide it to the target base station;

[0134] 3) The source base station generates an RRC release message and sends it to the UE through the target base station;

[0135] 4) The UE remains in the inactive state.

[0136] It should be understood that in process 1, the context of the UE is migrated from the source base station to the target base station, while in process 2, the context of the UE is not migrated.

[0137] 3. Enter the idle state process

[0138] 1) UE initiates RRC re-establishment request;

[0139] 2) The target base station fails to request the UE context from the source base station. In this case, the source base station has the UE context but does not want to provide it to the target base station;

[0140] 3) The source base station generates an RRC release message and sends it to the UE through the target base station;

[0141] 4) After receiving the RRC release message, the UE enters the idle state. It should be understood that when the UE changes from the inactive state to the idle state, the AMF must be notified.

[0142] 5) The source base station releases the UE context.

[0143] The present application embodiment proposes a communication method, which is applicable to UE-Network relay application scenarios, such as Figure 2 As shown, a schematic flow chart of a communication method 200 according to an embodiment of the present application is shown.

[0144] The second terminal device forwards the data of the first terminal device to communicate with the first network device, the second terminal device communicates with the first terminal device via a side link, and the second terminal device communicates with the first network device via a wireless network. The first terminal device is called a remote UE, the second terminal device is called a relay UE, and the first network device can be a base station. The method can be executed by the second terminal device, or by a component of the second terminal device, such as a processor, a chip, or a chip system, and the method is described by taking the execution of the second terminal device as an example.

[0145] 210. The second terminal device determines that the sidelink between the first terminal device and the second terminal device is disconnected.

[0146] 220. The second terminal device deletes the association between the first identifier and the first terminal device, where the first identifier is allocated by the second terminal device or the first network device to the first terminal device and is used to identify the first terminal device. Specifically, the second terminal device deletes the association between the first identifier and the first terminal device, including one or more of the following: the second terminal device releases the first identifier, and the second terminal device releases the context of the first terminal device.

[0147] Specifically, optionally, the second terminal device may determine through detection by itself that the sidelink is disconnected.

[0148] In the new radio (NR) R16 protocol, for the scenario of direct communication between two UEs via the sidelink, a keep-alive message is defined in the PC5 signaling (PC5-S) layer. The transmitting (transmission, Tx) UE or the receiving (reception, Rx) UE can initiate the keep-alive message by itself or periodically. If no response message is received from the other UE within the specified time, it is considered that the sidelink connection is abnormally released, and the access stratum (access stratum, AS) is notified to release the corresponding SL connection (sl link). For the application scenario of UE-Network relay, this mechanism can be reused for relay UE, so that the relay UE periodically sends a keep-alive message to the remote UE to detect whether the remote UE has left the relay UE. If the PC5-S layer of the relay UE detects and notifies the AS layer to release the SL link, the relay UE determines that the SL connection between it and the remote UE is disconnected.

[0149] The NR R16 protocol supports hybrid automatic repeat request (HARQ) based on RLF to find that the PC5 link has RLF, that is, the Tx UE sends data to the Rx UE. If it receives continuous negative acknowledgement (NACK) or discontinuous transmission (DTX), or does not receive any ACK / NACK feedback, it is considered that the SL has RLF, and the SLlink can be released automatically at the AS layer. For the application scenario of UE-Network relay, this mechanism can be reused for the relay UE, allowing the relay UE to send data to the remote UE as the sender. If continuous NACK or DTX is detected, or no ACK / NACK feedback is received, the relay UE determines that the SL between it and the remote UE is disconnected.

[0150] In addition to the above, optionally, after receiving data sent by the remote UE to the first network device, the relay UE starts the first timer. If the relay UE does not receive the data sent by the remote UE to the first network device before the first timer expires, the relay UE determines that the SL between it and the remote UE is disconnected. Alternatively, after receiving data sent by the first network device to the remote UE, the relay UE starts or restarts the first timer. If the relay UE does not receive the data sent by the first network device to the remote UE before the first timer expires, the relay UE determines that the SL between it and the remote UE is disconnected. It should be understood that the duration of the first timer is adjustable and can be configured by the network side, preset, or configured by other terminal devices. The relay UE starts or restarts the first timer each time it receives or sends new and / or retransmitted data.

[0151] After the second terminal device determines that the side link is disconnected through detection, it can optionally send a first indication message to the first network device indicating that the side link between it and the first terminal device is disconnected. The first indication message is used by the first network device to delete the association between the first identifier and the first terminal device and / or the routing information corresponding to the first terminal device. The first identifier is allocated by the second terminal device or the first network device to the first terminal device and is used to identify the first terminal device. Optionally, the first identifier is a local identifier, which is a local id.

[0152] like Figure 3As shown, a schematic diagram of the process interaction of the relay UE sending the first indication information to the base station after determining that the side link is disconnected is shown. The specific process is as follows:

[0153] 301, the relay UE determines that the sidelink between it and the remote UE is disconnected;

[0154] 302. The relay UE sends first indication information to the source base station.

[0155] The first indication information may be side link terminal information, which does not carry the first target identifier and the local id corresponding to the first target identifier, and the first target identifier corresponds to the first identifier of the first terminal device. The correspondence may be pre-configured or told by the second terminal device to the first network device. The side link terminal information may include the identifiers of all remote UEs connected to the relay UE (e.g., dest l2 id) and the local ids of all remote UEs connected to the relay UE.

[0156] Optionally, the first indication information sent by the second terminal device to the first network device may be sent only after all uplink / downlink data of the remote UE has been forwarded, so as to inform the first network device that the data of the first terminal device has been transmitted, thereby further triggering the first network device to release the local ID of the first terminal device. Alternatively, the first indication information may be sent first, and then after all the remote data has been forwarded, another indication is sent to indicate that the data has been sent, thereby further triggering the first network device to release the local ID of the first terminal device. Specifically, optionally, the second terminal device receives the second indication information sent by the first terminal device, and the second indication information indicates that the side link between the second terminal device and the first terminal device is disconnected. It should be understood that in many scenarios, the remote UE first perceives the side link disconnection, for example: during the RRC reconstruction process, the remote UE receives the RRC release and RRC rejection sent by the network device; during the HO process, the remote UE receives the switching command sent by the first network device. Both the RRC release / reject message and the HO CMD message are encrypted and transparently transmitted to the relay UE, and the relay UE cannot be informed. Therefore, sending the second indication information to the relay UE before the remote UE leaves the relay UE can enable the relay UE to determine that the sidelink between it and the remote UE is disconnected.

[0157] Specifically, optionally, the second terminal device receives a third indication message sent by the first network device, and the third indication message indicates that the side link between the second terminal device and the first terminal device is disconnected. In some application scenarios, the first network device first senses that the side link is disconnected. For example, during the RRC reconstruction process, the first network device receives at least one of a request sent by the second network device to obtain the context of the first terminal device and release the context of the first terminal device; it should be understood that the second network device is the target base station and the first network device is the source base station. For another example, during the HO process, the first network device receives a switching permission sent by the second network device. The first network device first senses that the side link between the relay UE and the remote UE is to be disconnected or has been disconnected, and can send a third indication message to the relay UE. The relay UE determines that the side link between it and the remote UE is disconnected based on the third indication message.

[0158] Optionally, the second terminal device can determine that the side link between it and the first terminal device is disconnected based on the logical channel configuration information, and the logical channel configuration information is related to the first terminal device. If the SL logical channel (logical channel, LCH) between the remote UE and the relay UE has been deleted, or the Uu LCH corresponding to the remote UE is deleted, it is considered that the side link between the remote UE and the relay UE is disconnected.

[0159] Logical channel configuration is generally configured by the network side. The mapping relationship between SL LCH and Uu LCH can be 1:1 mapping or N:1 mapping.

[0160] The 1:1 mapping relationship includes: a SL LCH between a remote UE and a relay UE is uniquely mapped to a Uu LCH between the relay UE and the base station, and the SL LCHs corresponding to different remote UEs will not be multiplexed on the same Uu LCH, such as Figure 4 Therefore, the relay UE knows which Uu LCHs are associated with the local id, and the relay UE can determine which remote UE has its sidelink disconnected according to the deletion of the SL LCH or the deletion of the Uu LCH.

[0161] The N:1 mapping relationship includes: SL LCHs between multiple remote UEs and relay UEs can be mapped to one Uu LCH between the relay UE and the base station, and the SL LCHs corresponding to different remote UEs are multiplexed on the same Uu LCH, such as Figure 5At this time, the relay UE cannot determine which remote UE has its sidelink disconnected according to the deletion of the Uu LCH, because the relay UE does not know which Uu LCH is configured for the remote UE.

[0162] Therefore, no matter which mapping relationship is adopted, the relay UE can determine which remote UE has its side link disconnected only by deleting the configuration of the SL LCH. For example, if all SL LCHs corresponding to a remote UE have been deleted, it is considered that the side link between the remote UE and it is disconnected. If a 1:1 mapping relationship is adopted, the relay UE can also determine which remote UE has its side link disconnected based on the deletion of the Uu LCH.

[0163] In the technical solution provided in the embodiment of the present application, the relay UE can promptly determine that the side link between it and the remote UE is disconnected, and delete the association between the first identifier and the remote UE. Therefore, the first identifier can be used to identify other terminal devices, thereby avoiding the situation where other terminal devices are unable to establish a connection with the second terminal device when the identifier is exhausted.

[0164] The present application embodiment proposes a communication method, which is applicable to UE-Network relay application scenarios, such as Figure 6 As shown, a schematic flow chart of a communication method 600 according to an embodiment of the present application is shown.

[0165] The first terminal device communicates with the first network device by forwarding data through the second terminal device, the first terminal device communicates with the second terminal device through a side link, and the first network device communicates with the second terminal device through a wireless network, wherein the first terminal device is called a remote UE, the second terminal device is called a relay UE, and the first network device may be a base station. The method may be executed by the first network device, or by a component of the first network device, such as a processor, a chip, or a chip system, and the method is described by taking the execution of the first network device as an example.

[0166] 610. The first network device determines that the side link between the first terminal device and the second terminal device is disconnected.

[0167] 620. The first network device deletes the association between the first identifier and the first terminal device, the first identifier is associated with the identifier of the second terminal device, the first identifier is used to identify the first terminal device, and the first identifier is allocated by the second terminal device or the first network device to the first terminal device. Specifically, optionally, the first network device deletes the association between the first identifier and the first terminal device, including one or more of the following: the first network device releases the first identifier, and the first network device releases the context of the first terminal device.

[0168] Specifically, optionally, the first network device can determine that the side link is disconnected through detection by itself. After the first network device receives the data of the first terminal device sent by the second terminal device, it starts the second timer. If the first network device does not receive the data of the first terminal device before the second timer expires, it determines that the side link is disconnected. Alternatively, after the first network device sends the data of the first terminal device to the second terminal device, it starts or restarts the second timer. If the first network device does not send the data of the first terminal device to the second terminal device before the second timer expires, it determines that the side link is disconnected. Optionally, the second timer can be configured by the network side (such as CN / RAN / gNB / gNB-CU / gNB-DU, etc.) to the UE, or configured by the opposite UE.

[0169] Specifically, optionally, the first network device can determine that the side link is disconnected based on the fourth indication information received from the second network device. The fourth indication information includes at least one of the following information: request to obtain the context of the first terminal device, release the context of the first terminal device, switching permission, etc. During the HO process, the first network device receives a switching permission, acquisition of the context of the first terminal device, or release of the context of the first terminal device sent by the second network device, and then determines that the side link is disconnected. When a SL RLF occurs in the remote UE, and the RRC is successfully reestablished to other cells, the first network device receives at least one of a request to obtain the context of the first terminal device and release the context of the first terminal device sent by the second network device, and then determines that the side link is disconnected; it should be understood that the second network device is the target base station and the first network device is the source base station.

[0170] like Figure 7 As shown, a schematic diagram of the process interaction of the source base station receiving the handover permission sent by the target base station during the HO process is shown. The specific process is as follows:

[0171] 701, the remote UE reports a measurement report to the source base station;

[0172] 702, the source base station makes a handover decision;

[0173] 703, the source base station sends a handover request message to the target base station;

[0174] 704, the target base station performs admission control to see whether the remote UE is allowed to switch to the current cell. If allowed, a switching permission message, such as an ACK message, is sent to the source base station.

[0175] 705. After receiving the handover permission message sent by the target base station, the source base station sends a handover command to the remote UE.

[0176] During the HO process, after the source base station receives the switching permission message sent by the target base station, it determines that the side link between the remote UE and the relay UE is disconnected; or, after the source base station sends a switching command to the remote UE, the source base station (first network device) determines that the side link between the remote UE and the relay UE is disconnected.

[0177] 706. After the first network device determines that the side link between the remote UE and the relay UE is disconnected and releases the local id, routing information and UE context of the corresponding remote UE maintained by the first network device, it can send a third indication message to the relayUE to indicate that the side link is disconnected, so that the relay UE deletes the association between the first identifier and the first terminal device and releases the first identifier.

[0178] like Figure 8 As shown, a schematic diagram of the process interaction of the first network device sending the third indication information to the relayUE after receiving the handover permission message sent by the target base station is shown. The specific process is as follows:

[0179] 801, the source base station receives a handover permission message sent by the target base station;

[0180] 802, the source base station sends a handover command to the remote UE;

[0181] 803. The source base station sends third indication information to the relay UE.

[0182] like Fig. 9 As shown, a schematic diagram of the process interaction of the source base station receiving a request sent by the target base station to obtain the context of the first terminal device and releasing the context of the first terminal device during the RRC reconstruction process is shown. The specific process is as follows:

[0183] 901, the remote UE sends an RRC reestablishment request message to the target base station;

[0184] 902. After receiving the reconstruction request message, the target base station searches for the source base station of the remote UE according to the information carried in the reconstruction request message, and sends a request message to the source base station requesting to obtain the context of the remote UE; if the source base station receives the request message, it determines that the side link between the remote UE and the relay UE is disconnected, and releases the local id, routing information and UE context of the corresponding remote UE maintained by the first network device.

[0185] 903. After the RRC reconstruction is successful, the target base station receives the path switch request response message sent by the AMF, and can send a notification message to the source base station to release the context of the remote UE. If the source base station receives the notification message to release the context of the remote UE, it is determined that the side link between the remote UE and the relay UE is disconnected. During the RRC reconstruction process, if the source base station receives a message sent by the target base station to obtain the context of the first terminal device or release the context of the first terminal device, it is determined that the side link is disconnected. Optionally, the source base station can send a third indication message to the relay UE to indicate that the side link is disconnected, so that the relay UE deletes the association between the first identifier and the first terminal device and releases the first identifier.

[0186] like Fig.10 As shown, a schematic diagram of the process interaction of the first network device sending the third indication information to the relay UE after receiving the context message of obtaining the first terminal device / releasing the context message of the first terminal device sent by the target base station is shown. The specific process is as follows:

[0187] 1001. The source base station receives a context message for acquiring a first terminal device / a context message for releasing a first terminal device sent by a target base station;

[0188] 1002. The source base station sends third indication information to the relay UE.

[0189] The first network device first senses that the side link between the relay UE and the remote UE is to be disconnected or has been disconnected, and can send third indication information to the relay UE to enable the relay UE to delete the association between the first identifier and the first terminal device and release the first identifier.

[0190] Optionally, the first network device may perform logical channel configuration, and if the mapping relationship between SL LCH and Uu LCH is a 1:1 mapping, the first network device may determine that the side link between the remote UE and the relay UE is disconnected based on the deletion of the Uu LCH corresponding to the remote UE.

[0191] Specifically, optionally, when the second terminal device determines through detection that the side link is disconnected, it can send a first indication message to the first network device. The first network device receives the first indication message and determines that the side link is disconnected based on the first indication message.

[0192] Optionally, the first indication information may be side link terminal information, which does not carry the first target identifier and the local id corresponding to the first target identifier, and the first target identifier corresponds to the first identifier of the first terminal device. The correspondence may be pre-configured or told by the second terminal device to the first network device. The side link terminal information may be the identifiers of all remote UEs connected to the relay UE (such as dest l2 Id) and the local ids of all remote UEs connected to the relay UE.

[0193] Specifically, optionally, the first network device may receive the second indication information sent by the first terminal device, and determine the sidelink disconnection according to the second indication information. For example, the remote UE switches from relay UE1 to relay UE2, but the remote UE still communicates with the first network device. After the remote UE establishes a communication connection with relay UE2, it may send an indication to the first network device that the sidelink between it and relay UE1 is disconnected.

[0194] The second indication information may also be a switching success message. When the remote UE is successfully switched from relay UE1 to relay UE2, the switching success message may be sent to the first network device, so that the first network device determines that the sidelink between the remote UE and the sidelink relay UE1 is disconnected.

[0195] In the UE-Network relay application scenario, when the remote UE first senses that the sidelink between it and the relay UE is disconnected, before the sidelink is disconnected, the remote UE can send a notification message to the relay UE, such as a Remote release message, to inform the relay UE that the sidelink is disconnected. Because in many cases, the message received by the remote UE through the relay UE is encrypted and transparent to the relay UE, such as radio resource control RRC release, radio resource control RRC rejection, switching command, etc. After receiving the notification message sent by the remote UE, the relay UE releases the local id of the remote UE. When a new remote UE wants to access the relay UE, the relay UE can assign the local id to the new remote UE, thereby avoiding the local id being exhausted and the inability to provide terminal to network (UE to network, U2N) forwarding service when the new remote UE accesses the relay UE.

[0196] The present application embodiment proposes a communication method, which is applicable to UE-Network relay application scenarios, such as Fig.11 As shown, a schematic flow chart of a communication method 1100 according to an embodiment of the present application is shown.

[0197] The first terminal device communicates with the first network device by forwarding data through the second terminal device, the first terminal device communicates with the second terminal device through a side link, and the second terminal device communicates with the first network device through a wireless network. The first terminal device is called a remote UE, the second terminal device is called a relay UE, and the first network device can be a base station. The method can be executed by the first terminal device, or by a component of the first terminal device, such as a processor, a chip, or a chip system, and the method is described by taking the execution of the first terminal device as an example.

[0198] 1110. The first terminal device determines to disconnect the sidelink connection between it and the second terminal device. Optionally, the first terminal device may sense the disconnection of the sidelink between it and the second terminal device through its own detection, or may determine the disconnection of the sidelink between it and the second terminal device according to the received indication information.

[0199] 1120. Before the first terminal device senses and determines to disconnect the side link, it can send second indication information to the second terminal device, or send second indication information to the first network device to indicate that the side link is disconnected.

[0200] Specifically, optionally, the first terminal device determines to disconnect the side link with the second terminal device according to one or more of the following: wireless connection failure, switching failure.

[0201] Specifically, optionally, after the first terminal device sends data to the first network device through the second terminal device, the third timer is started. If the first terminal device does not send data to the first network device through the second terminal device before the third timer times out, it is determined that the side link is disconnected; or, after receiving data sent by the first network device through the second terminal device, the first terminal device starts or restarts the third timer. If the first terminal device does not receive data sent by the first network device before the third timer times out, it is determined that the side link is disconnected. Optionally, the third timer can be configured by the network side (such as CN / RAN / gNB / gNB-CU / gNB-DU, etc.) for the UE, or configured by the opposite UE.

[0202] Specifically, optionally, the first terminal device receives fifth indication information, which indicates that the side link is disconnected. The fifth indication information includes at least one of the following information sent by the first network device: radio resource control RRC release, radio resource control RRC rejection, and switching command. During the HO process, if the first terminal device receives a switching command sent by the first network device, it is determined to disconnect the side link between it and the second terminal device. During the RRC reestablishment process, the first terminal device receives a radio resource control RRC reestablishment (RRC Reestablishment) notification sent by the second network device, and the radio resource control RRC reestablishment notification is sent to the first terminal device after the second network device successfully obtains the context of the first terminal device from the first network device, then it is determined that the side link between it and the second terminal device is disconnected. Alternatively, the first terminal device receives an RRC release / RRC rejection message sent by the first network device, then it is determined that the side link between it and the second terminal device is disconnected; for example, when the load of the first network device is high, to disconnect the RRC connection of the first terminal device, it will send an RRC release / RRC rejection message to the first terminal device.

[0203] In addition, if a connection is successfully established between the remote UE and the first network device via the Uu interface, it is determined that the side link between the remote UE and the second terminal device is disconnected.

[0204] like Fig.12 As shown, a schematic diagram of the process interaction of the remote UE receiving the handover command sent by the source base station during the HO process is shown. The specific process is as follows:

[0205] 1201, the remote UE reports a measurement report to the source base station;

[0206] 1202, the source base station makes a handover decision;

[0207] 1203, the source base station sends a handover request message to the target base station;

[0208] 1204, the target base station performs admission control to see whether the remote UE is allowed to switch to the cell. If allowed, a switching permission message, such as an ACK message, is sent to the source base station.

[0209] 1205. After receiving the handover permission message sent by the target base station, the source base station sends a handover command (HO CMD) message to the remote UE, and releases the local id, routing information and UE context of the corresponding remote UE maintained by the first network device. During the HO process, if the remote UE receives the HO CMD, it determines to disconnect the sidelink with the relay UE.

[0210] like Fig.13 As shown, a schematic diagram of the process interaction of the remote UE sending the second indication information to the relay UE after receiving the HO CMD is shown. The specific process is as follows:

[0211] 1301, the source base station sends a handover request message to the target base station;

[0212] 1302, after receiving the handover permission message sent by the target base station, the source base station sends a handover command to the remote UE;

[0213] 1303, after receiving the handover command, the remote UE determines to disconnect the sidelink with the relay UE, and can send second indication information to the relay UE to instruct the sidelink to be disconnected so that the relay UE releases the local ID of the remote UE. Optionally, the second indication information can be "Remote release".

[0214] like Fig.14 As shown, a schematic diagram of the process interaction of the remote UE sending the second indication information to the relay UE after receiving the RRC release / RRC rejection message sent by the base station is shown. The specific process is as follows:

[0215] 1401, the remote UE receives an RRC release / RRC rejection message sent by the base station, and the remote UE determines to disconnect the side link between it and the relay UE;

[0216] 1402, before disconnecting the sidelink between the remote UE and the relay UE, the remote UE sends second indication information to the relay UE, which is used to indicate that the sidelink is disconnected, so that the relay UE releases the local ID of the remote UE. Optionally, the second indication information may also be "Remote release".

[0217] The embodiment of the present application proposes a communication method 1500, which is applied to the scenario where a relay UE has an RLF and then performs RRC reconstruction. In this scenario, when the relay UE has an RLF and reestablishes to another cell, the remote UE under it still assumes that it can access the network through the relay UE, that is, the remote UE does not change the relay UE. It should be understood that there can be multiple remote UEs that establish a communication connection with a relay UE, that is, a relay UE can forward data of multiple remote UEs.

[0218] At present, when the relay UE has RLF, reselects a new cell, and initiates an RRC reestablishment request message, the reestablished cell will request the context of the relay UE from the original serving cell. If the request is successful, the relay UE will receive an RRC reestablishment notification message from the network side, which means that the network side can allow the relay UE to reestablish. However, in the existing technical solution, the second network device of the reestablished cell cannot obtain the context of the remote UE under the relay UE from the first network device of the original serving cell. Therefore, the embodiment of the present application proposes a communication method 700, which can simultaneously obtain the context of the relayUE and the remote UE under it.

[0219] like Fig.15 As shown, a schematic flow chart of a communication method 1500 according to an embodiment of the present application is shown.

[0220] The second terminal device forwards data of at least one first terminal device to communicate with the first network device, the second terminal device communicates with at least one first terminal device via a side link, and the second terminal device communicates with the first network device via a wireless network. The first terminal device is called a remote UE, the second terminal device is called a relay UE, and the first network device can be a base station. The method can be executed by the second terminal device, or by a component of the second terminal device, such as a processor, a chip, or a chip system, and the method is described by taking the execution of the second terminal device as an example. The communication method 1500 includes:

[0221] 1510. The second terminal device sends a radio resource control RRC reconstruction request message or an RRC recovery request message to the second network device. The RRC reconstruction request message or the RRC recovery request message includes sixth indication information. The sixth indication information is used to instruct the second network device to obtain the context of the first terminal device from the first network device. The sixth indication information can also instruct the second network device to obtain the context of the second terminal device. The sixth indication information may include some information indicating that the second terminal device is a relay UE.

[0222] Before the second terminal device sends a radio resource control RRC reestablishment request message to the second terminal device, the method also includes: RLF occurs in the second terminal device, and the wireless network communication connection between the second terminal device and the first network device is disconnected.

[0223] Optionally, the sixth indication information can be used to instruct the second network device to obtain the context of all first terminal devices under the second terminal device from the first network device, and can also be used to instruct the second network device to obtain the context of some first terminal devices under the second terminal device from the first network device. Specifically, the sixth indication information includes the identifier of at least one first terminal device, and may also include the identifier of the second terminal device. The identifier of the first terminal device may be the C-RNTI of the first terminal device, an inactive network temporary identifier (I-RNTI), etc. It should be understood that the sixth indication information may be explicit indication information or implicit indication information.

[0224] For example, the remote UEs connected to the relay UE via the sidelink include remote UE1, remote UE2, and remote UE3 or all remote UEs, and the sixth indication information may include the identifiers of remote UE1, remote UE2, and remote UE3, and the second network device may obtain the contexts of remote UE1, remote UE2, and remote UE3 from the first network device according to the sixth indication information. The sixth indication information may also include only the identifier of remote UE1, and the second network device may obtain only the context of remote UE1 from the first network device according to the sixth indication information. In this case, only remote UE1 may need to access the rebuilt cell or the relay UE may not be changed.

[0225] Optionally, the sixth indication information may be included in the RRC reconstruction request message or may be sent independently, which is not limited in the embodiments of the present application.

[0226] like Fig.16 As shown, a schematic diagram of the process interaction of the target base station obtaining the context of the relay UE and its remote UE according to the RRC reconstruction request message sent by the relay UE during the RRC reconstruction process is shown. The specific process is as follows:

[0227] 1601: RLF occurs in the relay UE.

[0228] 1602, the relay UE sends an RRC re-establishment request message or an RRC recovery request message to the target base station of the re-established cell, where the RRC re-establishment request message or the RRC recovery request message includes sixth indication information, which is used to instruct the target base station to obtain the context of the remote UE under the relay UE from the source base station, and the sixth indication information may include an identifier of the remote UE under the relay UE;

[0229] 1603. The target base station obtains the context of the remote UE under the relay UE from the source base station according to the sixth indication information.

[0230] In some possible implementations, the second terminal device does not need to send the sixth indication information indicating the acquisition of the context of the first terminal device to the second network device. After receiving the radio resource control RRC reconstruction request message sent by the second terminal device, the second network device sends a context fetch message to the first network device and only carries the identifier of the second terminal device. If the first network device finds that there are many first terminal devices under the second terminal device, the first network device will send the context of all first terminal devices and the context of the second terminal device under the second terminal device to the second network device.

[0231] The second network device obtains the context of the second terminal device and the first terminal device under it, so that the second terminal device and the first terminal device under it can access the network together.

[0232] In addition, the second network device can obtain the local ID corresponding to the first terminal device from the first network device according to the sixth indication information in the RRC reconstruction request message sent by the second terminal device, thereby facilitating U2N data transmission.

[0233] In order to facilitate the understanding of the technical solution, the allocation of local IDs is briefly described.

[0234] The local id can be allocated by the relay UE and notified to the network, or it can be allocated by the network and notified to the relay UE. Both solutions are feasible.

[0235] Take the assignment of local id to relay UE as an example. The remote UE sends a message. After receiving the message, the relay UE confirms that the message is the first message based on the SL L2id and that the message needs to be forwarded to the base station. At the same time, it receives the SL L2 id corresponding to the remote UE. The relay UE assigns a local id by itself, associates its own C-RNTI and local id with the SL L2 id, generates corresponding routing information for subsequent data forwarding, and forwards it to the network side. After the network side receives the first message forwarded by the relay UE, it associates the C-RNTI and local id of the relay UE with the C-RNTI / S-TMSI of the remote UE or the context of the remote UE.

[0236] The following takes the example of the remote UE entering the connected state from the idle state as an example for explanation.

[0237] After the remote UE discovers the relay UE, the remote UE establishes a SL unicast connection with the relay UE, and the remote UE sends an RRC establishment request message, which can be carried on one or more dedicated SL LCHs, or multiplexed on the existing shared SL LCH for RRC establishment. It should be understood that the shared SL LCH is already in the R16 standard and is allocated after the PC5-S connection is established between the two UEs. For example, for the Uu SRB0 / 1 / 2 messages, the protocol predefines that SL LCH4, 5, and 6 are used to carry the corresponding SRB messages respectively (because R16 has defined 4 LCHs for SL SRB, corresponding to unencrypted PC5-S signaling transmission, fully secured but not encrypted PC5-S signaling transmission, fully secured and encrypted PC5-S signaling transmission, and SLRRC signaling transmission); or after the UE establishes the RRC connection (the mapping of Uu SRB0 and SL LCH is still predefined by the protocol), the base station configures the mapping relationship between Uu SRB1 / 2 and SL LCH or SL LCH id of a remote UE or all remote UEs.

[0238] If the RRC establishment request message is carried on one or more specific SL LCHs, for example, SL LCH=5 is a SL LCH specifically used to forward Uu RRC messages, the relay UE considers all messages received from the specific SL LCH as not being sent to itself and forwards them to the base station.

[0239] If the RRC setup request message is carried on the shared SL LCH, an additional indication is required to inform the relay UE that the message needs to be further forwarded to the base station, rather than the remote UE sending it to the relay UE and the relay UE parsing it. For example, through a 1-bit indication, "0" indicates that it needs to be forwarded, and "1" indicates that it does not need to be forwarded.

[0240] If the relay UE receives a message from the SL LCH and determines that the message needs to be further forwarded to the base station, and the relay UE determines that the remote UE has not been assigned a local id before through the remote UE layer 2 identifier carried in the media access control (MAC) header in the received SL data packet, the relay UE assigns an unused local id to the remote UE, and configures a default / default backhaul logical channel (default BH LCH) for the relay UE through the base station, and forwards the message through the default BH LCH.

[0241] The default BH LCH may be one or more configured by the base station for the relay UE.

[0242] If the default BH LCH is one, all Uu RRC messages of all remote UEs that are ultimately sent to the base station or RRC messages sent by the base station to all remote UEs are multiplexed on this shared default BH LCH for transmission; in this process, there needs to be an AL between the relay UE and the base station that carries the localid assigned by the relay UE to the remote UE. It should be understood that the relay UE maintains the association between the SL L2 Id (remote UE identifier) ​​and the local id, and the gNB maintains the association between the remote UE identifier and the C-RNTI and local id of the relay UE.

[0243] If there are multiple default BH LCHs, the relay UE can select an unoccupied default BH LCH from the pre-configured default BH LCHs for the first message to be forwarded by the remote UE, and use the default BH LCH to transmit only the RRC message corresponding to the remote UE; the downlink RRC message sent by the base station to the remote UE also always uses the SL default LCH dedicated to the remote UE; at this time, there is no need for AL between the relay UE and the base station, nor is it necessary to carry the local id.

[0244] Still taking the shared default BH LCH as an example, the base station replies to the remote UE with an RRC establishment message, which is also sent on the default BH LCH pre-configured for the relay UE and carries the local id corresponding to the remote UE.

[0245] The relay UE considers any message received from the shared default BH LCH as not sent to itself and needs to forward it to the remote UE. The remote UE to which it is forwarded needs to find the L2 ID of the corresponding remote UE based on the localid carried by the base station in the AL; and forward it on the dedicated SL LCH.

[0246] After receiving the RRC establishment message sent by the base station, the remote UE replies with an RRC reestablishment completion message to the base station and sends it to the relay UE on the dedicated SL LCH or shared SL RRC.

[0247] The relay UE receives the message from the dedicated SL LCH. At this time, it determines that the localid has been assigned to the remote UE before, so there is no need to divide it again. Instead, it uses the previously assigned local id to encapsulate the message and forward it to the base station; at the same time, the local id previously assigned to the remote UE is carried in the AL layer, and of course it is also sent to the base station on the dedicated default BH LCH.

[0248] If the base station receives a message from the dedicated default BH LCH, it believes that it must be sent by the remote UE and has an AL layer. Therefore, it parses it according to the solution with AL and reads out the local ID. According to the association between the remote UE identifier maintained by the base station and the C-RNTI and local ID of the relay UE, it knows that the subsequent RRC message is actually sent to itself by a remote UE, and then operates on the corresponding remote UE.

[0249] It should be understood that, for the same remote UE, the RRC establishment request message sent by the remote UE to the base station, the RRC establishment message replied by the base station, and the switching permission sent by the base station to the remote UE during the HO switching process all use the SL LCH and default BH LCH corresponding to the remote UE.

[0250] Multiple SL LCHs of a remote UE can be multiplexed on one Uu LCH, or the LCHs of multiple remote UEs can be multiplexed on one Uu LCH.

[0251] Taking the uplink transmission of multiple SL LCHs of a remote UE multiplexed on one Uu LCH as an example, after receiving the data packet, the base station side needs to obtain the local ID at the AL layer to know which remote UE sent it, and through the Uu / SLLCH / DRB identifier, know which SL LCH corresponding to the Uu PDCP / SDAP entity sent it.

[0252] Take the uplink signaling radio bearer (SRB) as an example. Fig.17As shown in the figure, if the three SRBs (such as SRB0 / 1 / 2) of remoteUE1 are all mapped to the same Uu LCH, then two PDCP entities of remote UE1, such as PDCP1 and PDCP2, and three RRC entities, such as RRC0, RRC1 and RRC2, are associated on an RLC entity on the base station side. The RRC0 entity has no corresponding PDCP entity; the base station sends the local id and SL LCH identifier carried in the AL layer to the corresponding PDCP / RRC entity of remote UE1; the local id in the AL received by the base station is filled by the relay UE itself according to the association between the remote UE identifier and the maintained local id, and the LCH identifier is filled with the SL LCH identifier information explicitly carried in the data packet received on the SL LCH, or when RRC0 / 1 / 2 are multiplexed on one SL LCH, the SL LCH identifier explicitly carried in the MAC header of the data packet cannot be distinguished; therefore, it is necessary to fill in the SL The RLC layer adds an indication of RRC0 / 1 / 2, so that after the relay UE receives the uplink data packet and parses it into the SL RLC, it knows which SL LCH identifies the data and then fills it in the Uu AL.

[0253] Similar to the downlink SRB, after receiving the data packet sent by the base station on a Uu LCH, the relay UE further parses the AL layer to obtain the local id and SL LCH identifier. The relay UE uses these two identifiers to identify which SL LCH of which remote UE the packet is sent to and hands it over to the corresponding remote UE and the RLC entity corresponding to the SL LCH, and finally sends it to the corresponding remote UE. After receiving the data packet forwarded by the relay UE, the remote UE parses the MAC header. If it is its own data packet, it further hands it over to the RLC entity corresponding to the corresponding SL LCH and further submits it to the upper layer (PDCP / RRC or SDAP, etc.).

[0254] In addition, there is another problem when sending uplink data to the remote UE: when the SL MAC of the remote UE sends SL data, it needs to fill in the destination L2 Id in the SL MAC header, and the destination L2 Id is also the L2 Id of the relay UE. In NR V2X R16, the L2 Id is provided to the AS layer by the upper layer (for example, APP layer or V2X layer), but because the upper layer of the SL AS layer of the remote UE is the Uu upper layer, there is no V2X layer, and the UuAPP layer will not provide the destination L2 Id to the SL AS layer according to the prior art, the remote UE can only obtain the destination L2 Id at the AS layer itself.

[0255] The possible solutions include: binding the RRC / PDCP / SDAP / RLC entity with the destination L2 Id, and when delivering data packets to the SL MAC, telling the remote UE about the destination L2 Id of the relay UE packet by packet through inter-layer primitives. Alternatively, the MAC obtains the binding relationship between the RLC entity and the destination L2 Id in advance, and when the SL RLC subsequently loses packets to the SL MAC, it does not need to indicate the destination L2 Id packet by packet; the MAC will find the destination L2 Id by looking up the binding relationship between the RLC entity and the destination L2 Id obtained in advance based on which RLC entity the data packet comes from, without having to fill in the destination L2 Id in the SL MAC header and send it out.

[0256] How MAC obtains the binding relationship of the RLC entity in advance can be that the network side (such as the base station) configures the remote UE through messages such as Uu RRC / SDAP / PDCP / NAS. After receiving the configuration, the corresponding configuration receiving layer further forwards it to the SL MAC entity of the remote UE. It can also be that the relay UE configures the remote UE, such as through SLPC5-S / RRC / SDAP / PDCP / RLC / MAC signaling, etc., and the remote UE's configuration receiving layer also receives it, parses it, and forwards it to the SL MAC entity of the remote UE. The remote UE can also generate the binding relationship itself. For example, after receiving the binding relationship between Uu PDCP and SL LCH from the base station, it knows that the target L2 Id associated with the Uu SDAP / RRC / PDCP entity corresponding to this bearer is the L2 Id of the relay UE. In this case, the L2 id of the relay UE has been obtained before. Alternatively, after the remote UE establishes the SL link / connection for relay with the relay UE, the corresponding SL RLC / MAC entity is bound to the L2 Id of the relay UE. In this way, no matter whether the remote UE sends Uu RRC or UuPDCP data in the future, it will send it to the corresponding SL RLC entity. The RLC entity will record the binding relationship between itself and the target L2 Id, and can carry the L2 Id of the relay UE when submitting it to the SL MAC entity. The SL MAC entity can then continue to encapsulate and send it out, and the target L2 Id it carries is also the correct L2 Id of the relay UE.

[0257] In the U2N scenario, assuming that the remote UE can support the inactive state and perform RRC reestablishment after RLF or HOF occurs, after selecting or residing under a new relay UE, the remote UE needs to determine whether to initiate an event-based radio access network notification area update (RNAU). If the RAN where the remote UE is located is the same as the radio access network area code (RAN area code, RANAC) of the cell where the new relay UE is located, RNAU does not need to be triggered. If the RANAC where the remote UE is located is different from the RAN of the cell where the new relay UE is located, RNAU needs to be triggered. Therefore, the remote UE needs to obtain the source of the relevant system broadcast information of the cell where the relay UE is located, such as the RAN area identifier, cell identifier or RANAC of the cell where the relay UE is located.

[0258] In addition, the remote UE also needs to decide which type of RRC reestablishment request message to send, and whether to carry the full-RNTI or the short-RNTI in the RRC reestablishment request message, based on the full-RNTI indication information provided in the system broadcast information of the cell where the relay UE is located. Therefore, the remote UE also needs to obtain the full-RNTI indication information provided in the system broadcast information of the cell where the relay UE is located.

[0259] Therefore, after the remote UE resides under a new relay UE, the remote UE can send indication information for obtaining RANAC to the relay UE. After receiving the indication information, the relay UE replies RANAC to the remote UE. After receiving the RANAC, the remote UE can decide whether to initiate RNAU.

[0260] Optionally, the remote UE may also receive a system broadcast message periodically sent by the relay UE, and obtain the RANAC and the full-RNTI according to the received system broadcast message.

[0261] In the U2N scenario, if the remote UE has an RLF and performs RRC reconstruction, it needs to carry the physical cell identification (PCI) of the original service cell, so that the reconstructed base station can find the original service base station corresponding to the remote UE according to the PCI to further obtain the context of the remote UE; or, when the remote UE is switched, such as before switching to a target relay UE, it needs to report the PCI of the service cell where the target relay UE is located, and report it to the original service base station through a measurement report message or other message, so that the original service base station can find the target service base station corresponding to the remote UE according to the PCI, so as to prepare for switching in advance. However, the acquisition of PCI in the above two scenarios is not supported in the current protocol. Therefore, in order to support RRC reconstruction, the remote UE needs to obtain the PCI information of the service cell of the original relay UE, and in order to support HO, the remote UE needs to obtain the PCI information of the service cell of the target relay UE.

[0262] Optionally, the remote UE may send a request message for obtaining PCI to the relay UE of the original service cell, and the relay UE replies with PCI. Then the remote UE may send the obtained PCI to the target base station, and the target base station finds the original service base station of the remote UE according to the PCI, and obtains the context of the relay UE. The remote UE may also send a request message for obtaining PCI to the relay UE of the target service cell, and the relay UE replies with PCI. Then the remote UE may report the obtained PCI to the original service base station, so that the original service base station can find the target service base station corresponding to the remote UE according to the PCI, and prepare for switching in advance.

[0263] Optionally, the remote UE may receive a system broadcast message periodically sent by a relay UE of the original serving cell / target serving cell, and obtain the PCI information of the original serving cell / target serving cell according to the received system broadcast message.

[0264] The embodiment of the present application is also applicable to the CU-DU architecture and the CP-UP separation architecture. For example, for the CU-DU architecture, the gNB notifies the relay UE to release the local id and remote UE context, which may be:

[0265] CU directly notifies the relay UE, or,

[0266] The CU notifies the relay UE via the DU, or

[0267] DU directly notifies relay UE, or,

[0268] DU notifies relay UE through CU.

[0269] Similarly, the relay UE notifies the gNB to release the local ID and the context of the remote UE, which can also be similarly subdivided: after the CU receives the message from the relay UE, the CU releases or notifies the DU to release the local ID; or after the DU receives the message, the DU releases or notifies the CU to release the local ID;

[0270] Remote UE local id is released, and optionally remote UE context is released.

[0271] The release message can be sent through SL / Uu RRC / SIB / SDAP / PDCP / RLC / MAC CE / PHY (DCI / UCI / SCI) and the like; it can also be sent through SL PC5-S or Uu NAS.

[0272] The present application embodiment provides a communication device 1800, such as Fig.18 As shown, a schematic block diagram of a communication device 1800 according to an embodiment of the present application is shown. The device can be applied to a second terminal device.

[0273] The device 1800 includes: a judgment unit 1810 and a processing unit 1820, the judgment unit 1810 is used to determine whether the side link is disconnected; the processing unit 1820 is used to delete the association between the first identifier and the first terminal device, the first identifier is used to identify the first terminal device, and the first identifier is allocated by the second terminal device or the first network device to the first terminal device.

[0274] Optionally, the processing unit 1820 is specifically configured to release the first identifier and / or release the context of the first terminal device.

[0275] Optionally, the apparatus 1800 further includes a transceiver unit 1830, the transceiver unit 1830 being configured to start a first timer after receiving data sent by the first terminal device to the network device and / or after receiving data sent by the first network device to the first terminal device;

[0276] The judgment unit 1810 is specifically used to determine that the side link is disconnected if the transceiver unit 1830 does not receive data sent by the first terminal device before the first timer expires, and / or does not receive data sent by the first network device to the first terminal device before the first timer expires.

[0277] Optionally, the transceiver unit 1830 is further used to send first indication information to the first network device, where the first indication information indicates that the side link is disconnected.

[0278] Specifically, optionally, the first indication information may be side link terminal information, the side link terminal information does not carry the first target identifier, and the first target identifier corresponds to the first identifier of the first terminal device.

[0279] Optionally, the judgment unit 1810 is specifically used to determine that the side link is disconnected if the transceiver unit 1830 receives second indication information sent by the first terminal device, and the second indication information indicates that the side link is disconnected.

[0280] Optionally, the judgment unit 1810 is specifically used to determine that the side link is disconnected if the transceiver unit 1830 receives third indication information sent by the first network device, and the third indication information indicates that the side link is disconnected.

[0281] Optionally, the judgment unit 1810 is further used to determine the side link disconnection according to a logical channel configuration, where the logical channel configuration is related to the first terminal device.

[0282] The present application embodiment provides a communication device 1900, such as Fig.19 As shown, a schematic block diagram of a communication device 1900 according to an embodiment of the present application is shown. The device can be applied to a first network device.

[0283] The device 1900 includes: a judgment unit 1910 and a processing unit 1920, the judgment unit 1910 is used to determine whether the side link is disconnected; the processing unit 1920 is used to delete the association between the first identifier and the first terminal device, the first identifier is associated with the identifier of the second terminal device, the first identifier is used to identify the first terminal device, and the first identifier is allocated by the second terminal device or the first network device to the first terminal device.

[0284] Optionally, the processing unit 1920 is specifically used to release the first identifier and / or release the context of the first terminal device.

[0285] Optionally, the device 1900 further includes a transceiver unit 1930, and the transceiver unit 1930 is used to start a second timer after receiving the data of the first terminal device sent by the second terminal device and / or after sending the data of the first terminal device to the second terminal device;

[0286] The judgment unit 1910 is specifically used to determine that the side link is disconnected if the transceiver unit 1930 does not receive the data of the first terminal device before the second timer expires, and / or does not send the data of the first terminal device to the second terminal device before the second timer expires.

[0287] Optionally, the judgment unit 1910 is specifically used to determine that the side link is disconnected if the transceiver unit 1930 receives fourth indication information sent by the second network device, and the fourth indication information includes at least one of the following information: requesting to obtain the context of the first terminal device, releasing the context of the first terminal device, and switching allowed.

[0288] Optionally, the transceiver unit 1930 is further used to send a third indication message to the second terminal device, where the third indication message indicates that the side link is disconnected.

[0289] Optionally, the judgment unit 1910 is specifically used to determine that the side link is disconnected if the transceiver unit 1930 receives first indication information sent by the second terminal device, and the first indication information indicates that the side link is disconnected.

[0290] Optionally, the judgment unit 1910 is specifically used to determine that the side link is disconnected if the transceiver unit 1930 receives second indication information sent by the first terminal device, and the second indication information indicates that the side link is disconnected.

[0291] The present application embodiment provides a communication device 2000, such as Fig. 20 As shown, a schematic block diagram of a communication device 2000 according to an embodiment of the present application is shown. The device can be applied to a first terminal device.

[0292] The device 2000 includes: a judgment unit 2010 and a transceiver unit 2020, the judgment unit 2010 is used to determine whether the side link is disconnected; the transceiver unit 2020 is used to send second indication information, and the second indication information is used to indicate that the side link is disconnected.

[0293] Optionally, the judgment unit 2010 is specifically used to determine to disconnect the side link connection according to one or more of the following: wireless connection failure, switching failure, and a third timer.

[0294] Optionally, the judgment unit 2010 is specifically used to determine that the side link is disconnected if the transceiver unit 2020 receives fifth indication information, and the fifth indication information is used to indicate the disconnection of the side link.

[0295] Specifically, optionally, the fifth indication information includes at least one of the following information sent by the first network device: radio resource control RRC release, radio resource control RRC rejection, and switching command.

[0296] Specifically, optionally, the fifth indication information includes a radio resource control RRC reestablishment notification sent by the second network device.

[0297] Optionally, the transceiver unit 2020 is specifically used to send the second indication information to the second terminal device.

[0298] Optionally, the transceiver unit 2020 is specifically configured to send the second indication information to the first network device. Fig.21 As shown, a schematic block diagram of a communication device 2100 according to an embodiment of the present application is shown.

[0299] The device 2100 includes: a processor 2110 and a transceiver 2120, wherein the transceiver 2120 is used to receive computer codes or instructions and transmit them to the processor 2110, and the processor 2110 executes the computer codes or instructions, such as the method in any possible implementation method in the embodiments of the present application.

[0300] The embodiment of the present application provides a communication system 2200, including the first terminal device 2210 and the second terminal device 2220 described in the communication method of the embodiment of the present application.

[0301] Optionally, the communication system 2200 may further include: the first network device 2230 described in the communication method of the embodiment of the present application.

[0302] The present application also provides a computer-readable storage medium on which a computer program for implementing the method in the above method embodiment is stored. When the computer program is run on a computer, the computer can implement the method in the above method embodiment.

[0303] In the various embodiments of the present application, unless otherwise specified or provided for in any logical conflict, the terms and / or descriptions between the different embodiments are consistent and may be referenced to each other, and the technical features in the different embodiments may be combined to form new embodiments according to their inherent logical relationships.

[0304] In addition, the term "and / or" in this application is only a description of the association relationship of associated objects, indicating that there may be three relationships. For example, A and / or B can represent three situations: A exists alone, A and B exist at the same time, and B exists alone. In addition, the character " / " in this article generally indicates that the objects associated before and after are in an "or" relationship; the term "at least one" in this application can mean "one" and "two or more". For example, at least one of A, B and C can represent seven situations: A exists alone, B exists alone, C exists alone, A and B exist at the same time, A and C exist at the same time, C and B exist at the same time, and A, B and C exist at the same time.

[0305] Those of ordinary skill in the art will appreciate that the units and algorithm steps of each example described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are performed in hardware or software depends on the specific application and design constraints of the technical solution. Those skilled in the art may use different methods to implement the described functions for each specific application, but such implementation should not be considered to be beyond the scope of this application.

[0306] Those skilled in the art can clearly understand that, for the convenience and brevity of description, the specific working processes of the systems, devices and units described above can refer to the corresponding processes in the aforementioned method embodiments and will not be repeated here.

[0307] In the several embodiments provided in the present application, it should be understood that the disclosed systems, devices and methods can be implemented in other ways. For example, the device embodiments described above are only schematic. For example, the division of the units is only a logical function division. There may be other division methods in actual implementation, such as multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. Another point is that the mutual coupling or direct coupling or communication connection shown or discussed can be through some interfaces, indirect coupling or communication connection of devices or units, which can be electrical, mechanical or other forms.

[0308] The units described as separate components may or may not be physically separated, and the components shown as units may or may not be physical units, that is, they may be located in one place or distributed on multiple network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution of this embodiment.

[0309] In addition, each functional unit in each embodiment of the present application may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit.

[0310] If the functions are implemented in the form of software functional units and sold or used as independent products, they can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the present application can be essentially or partly embodied in the form of a software product that contributes to the prior art. The computer software product is stored in a storage medium and includes several instructions for a computer device (which can be a personal computer, a server, or a network device, etc.) to perform all or part of the steps of the methods described in the various embodiments of the present application. The aforementioned storage media include: various media that can store program codes, such as USB flash drives, mobile hard disks, read-only memories (ROM), random access memories (RAM), magnetic disks or optical disks.

[0311] The above is only a specific implementation of the present application, but the protection scope of the present application is not limited thereto. Any person skilled in the art who is familiar with the present technical field can easily think of changes or substitutions within the technical scope disclosed in the present application, which should be included in the protection scope of the present application. Therefore, the protection scope of the present application should be based on the protection scope of the claims.

Claims

1. A communication method, characterized in that: The second terminal device forwards data of the first terminal device to communicate with the first network device, the second terminal device communicates with the first terminal device via a side link, and the second terminal device communicates with the first network device via a wireless network, and the method includes: Determining that the sidelink is disconnected; Delete the association between the first identifier and the first terminal device, the first identifier is used to identify the first terminal device, and after deleting the association between the first identifier and the first terminal device, the first identifier is also used to identify other terminal devices, and the first identifier is allocated to the second terminal device or the first network device.

2. The method according to claim 1, characterized in that The deleting the association between the first identifier and the first terminal device includes: Release the first identifier and / or release the context of the first terminal device.

3. The method according to claim 1 or 2, characterized in that: The determining that the sidelink is disconnected comprises: After receiving data sent by the first terminal device to the network device, and / or after receiving data sent by the first network device to the first terminal device, starting a first timer; If the data sent by the first terminal device is not received before the first timer expires, and / or the data sent by the first network device to the first terminal device is not received before the first timer expires, it is determined that the side link is disconnected.

4. The method according to claim 3, characterized in that The method further comprises: First indication information is sent to the first network device, where the first indication information indicates that the sidelink is disconnected.

5. The method according to claim 4, characterized in that The method further comprises: The first indication information is side link terminal information, the side link terminal information does not carry a first target identifier, and the first target identifier corresponds to the first identifier of the first terminal device.

6. The method according to claim 1 or 2, characterized in that: The determining that the sidelink is disconnected comprises: A second indication message sent by the first terminal device is received, and the second indication message indicates that the side link is disconnected.

7. The method according to claim 1 or 2, characterized in that: The determining that the sidelink is disconnected comprises: A third indication message sent by the first network device is received, wherein the third indication message indicates that the side link is disconnected.

8. The method according to claim 7, characterized in that The method further comprises: The sidelink disconnection is determined based on a logical channel configuration, and the logical channel configuration is related to the first terminal device.

9. The method according to any one of claims 1 to 8, characterized in that The first identifier is a local identifier local id.

10. A communication method, characterized in that: The first terminal device communicates with the first network device by forwarding data through the second terminal device, the first terminal device and the second terminal device communicate via a side link, and the first network device and the second terminal device communicate via a wireless network, the method comprising: Determining that the sidelink is disconnected; Delete the association between the first identifier and the first terminal device, the first identifier is associated with the identifier of the second terminal device, the first identifier is used to identify the first terminal device, and after deleting the association between the first identifier and the first terminal device, the first identifier is also used to identify other terminal devices, and the first identifier is allocated to the second terminal device or the first network device.

11. The method according to claim 10, characterized in that The deleting the association between the first identifier and the first terminal device includes: Release the first identifier and / or release the context of the first terminal device.

12. The method according to claim 10 or 11, characterized in that: The determining that the sidelink is disconnected comprises: After receiving the data of the first terminal device sent by the second terminal device, and / or after sending the data of the first terminal device to the second terminal device, starting a second timer; If no data of the first terminal device is received before the second timer expires, and / or if no data of the first terminal device is sent to the second terminal device before the second timer expires, it is determined that the sidelink is disconnected.

13. The method according to claim 10 or 11, characterized in that: The determining that the sidelink is disconnected comprises: Receive fourth indication information sent by the second network device, where the fourth indication information includes at least one of the following information: Request to obtain the context of the first terminal device, release the context of the first terminal device, and allow switching.

14. The method according to claim 12 or 13, characterized in that The method further comprises: A third indication message is sent to the second terminal device, wherein the third indication message indicates that the side link is disconnected.

15. The method according to claim 10 or 11, characterized in that: The determining that the sidelink is disconnected comprises: A first indication message sent by the second terminal device is received, and the first indication message indicates that the side link is disconnected.

16. The method according to claim 10 or 11, characterized in that The determining that the sidelink is disconnected comprises: A second indication message sent by the first terminal device is received, and the second indication message indicates that the side link is disconnected.

17. A method of communication, characterized in that: The first terminal device communicates with the first network device by forwarding data through the second terminal device, the first terminal device communicates with the second terminal device through a side link, and the second terminal device communicates with the first network device through a wireless network, the method comprising: Determining to disconnect the sidelink connection; Send a second indication message, wherein the second indication message is used to indicate that the side link is disconnected, and the second indication message is used to delete an association between a first identifier and the first terminal device, wherein the first identifier is used to identify the first terminal device, and after deleting the association between the first identifier and the first terminal device, the first identifier is also used to identify other terminal devices, and the first identifier is allocated to the second terminal device or the first network device.

18. The method according to claim 17, characterized in that The determining to disconnect the sidelink connection comprises: The sidelink connection is disconnected according to one or more of the following: Wireless connection failure, handover failure, third timer.

19. The method according to claim 17, characterized in that The determining to disconnect the sidelink connection comprises: A fifth indication message is received, where the fifth indication message is used to indicate disconnection of the sidelink.

20. The method according to claim 19, characterized in that The fifth indication information includes at least one of the following information sent by the first network device: Radio Resource Control RRC Release, Radio Resource Control RRC Reject, Handover Command.

21. The method according to claim 19, characterized in that The fifth indication information includes a radio resource control RRC reestablishment notification sent by the second network device.

22. The method according to any one of claims 17 to 21, characterized in that The sending of the second indication information includes: Send the second indication information to the second terminal device.

23. The method according to any one of claims 17 to 21, characterized in that The sending of the second indication information includes: Send the second indication information to the first network device.

24. A communication device, characterized in that: The method comprises means for implementing the functions of the method according to any one of claims 1 to 9.

25. A communication device, characterized in that: The method comprises means for implementing the functions of the method according to any one of claims 10 to 16.

26. A communication device, characterized in that: The method comprises means for implementing the functions of the method according to any one of claims 17 to 23.

27. A communication device, characterized in that: include: A processor and a transceiver, wherein the transceiver is used to receive computer codes or instructions and transmit them to the processor, and the processor executes the computer codes or instructions, according to the method according to any one of claims 1 to 9.

28. A communication device, characterized in that: include: A processor and a transceiver, wherein the transceiver is used to receive computer codes or instructions and transmit them to the processor, and the processor executes the computer codes or instructions, according to the method of any one of claims 10 to 16.

29. A communication device, characterized in that: include: A processor and a transceiver, wherein the transceiver is used to receive computer codes or instructions and transmit them to the processor, and the processor executes the computer codes or instructions, according to the method of any one of claims 17 to 23.

30. A communication system, characterized in that: include: The first terminal device and the second terminal device in the method according to any one of claims 1 to 23.

31. The communication system according to claim 30, characterized in that The communication system further comprises: The first network device in the method of any one of claims 1 to 23.

32. A computer-readable storage medium, characterized in that: include: The computer readable medium stores a computer program; When the computer program is executed on a computer, the computer is caused to execute the method according to any one of claims 1 to 23.