Communication for sidelink relays
By establishing a side link between the remote UE and the target relay UE or base station, the remote UE receives the local ID from the target relay UE or base station after path switching, the problem that the remote UE in 3GPP version 17 cannot obtain the local ID. Ensures the continuity of communication and the stability of data transmission.
Patent Information
- Application Number
- CN202280095293.9
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2022-04-25
- Publication Date
- 2024-12-03
AI Technical Summary
In 3GPP version 17, when the target relay user equipment (UE) is idle or inactive, side link relay supports direct to indirect path switching, but how the remote UE obtains its local ID is still unclear, resulting in communication interruption.
By establishing a side link between the remote UE and the target relay UE or base station, the remote UE receives the local ID from the target relay UE or base station and transmits data based on the ID to ensure the continuity of communication after path switching.
It is realized that the remote UE can obtain its local ID after path switching, thereby maintaining the continuity of communication and the stability of data transmission, and avoiding local ID conflicts and uncertainties.
Smart Images

Figure CN119072985A_ABST
Abstract
Description
Technical Field
[0001] Embodiments of the present disclosure relate generally to the field of telecommunications, and particularly to communications for sidelink relaying. Background Art
[0002] When the target relay user equipment (UE) is in idle or inactive state, the sidelink relay in the third generation partnership project (3GPP) release 17 supports direct to indirect path switching. It has been agreed that the target relay UE can send a sidelink UE information (SUI) message to the target base station (BS) and get the local ID of the remote UE from the target BS, which is the same as the radio resource control (RRC) establishment procedure. However, it is still unclear how the remote UE can get its local ID. Therefore, there is a need to further develop solutions for communication of sidelink relay. Summary of the invention
[0003] Generally speaking, example embodiments of the present disclosure provide a solution for communications for sidelink relaying.
[0004] In a first aspect, a first UE is provided. The first UE includes: a transceiver and a processor. The transceiver is configured to communicate with a network directly or via another UE. The processor is communicatively coupled to the transceiver and configured to perform operations including: receiving a first message from the network, the first message indicating that the first UE is switched to communicate with the network via a second UE in an idle state or an inactive state; obtaining a local ID of the first UE from the second UE or the network; and performing data transmission with the base station via the second UE based on the local ID of the first UE.
[0005] In a second aspect, a second UE is provided. The second UE includes a transceiver and a processor. The transceiver is configured to communicate with a network. The processor is communicatively coupled to the transceiver and configured to perform operations including: receiving a response to a first message from a first UE, the first message indicating that the first UE is switched to communicate with the network via the second UE in an idle state or an inactive state, the response indicating that the switching is completed; obtaining a local ID of the first UE from the first UE or the network; and sending the response to the network based on the local ID of the first UE.
[0006] In a third aspect, a BS is provided. The BS includes a transceiver and a processor. The transceiver is configured to communicate with a first UE directly or via another UE. The processor is communicatively coupled to the transceiver and configured to perform operations including: sending a first message to the first UE, the first message indicating that the first UE is switched to communicate with the base station via a second UE in an idle state or an inactive state; sending a local ID of the first UE to the first UE; and performing data transmission with the first UE via the second UE based on the local ID of the first UE.
[0007] In a fourth aspect, a method of communication is provided. The method includes: receiving a first message at a first UE and from a network, the first message indicating that the first UE is switched to communicate with the network via a second UE in an idle state or an inactive state; obtaining a local identity (ID) of the first UE from the second UE or the network; and performing data transmission with the network via the second UE based on the local ID of the first UE.
[0008] In a fifth aspect, a method of communication is provided. The method includes: receiving, at a second UE and from a first UE, a response to a first message indicating that the first UE is switched to communicate with the network via the second UE in an idle state or an inactive state, the response indicating that the switch is completed; obtaining an ID of the first UE from the first UE or the network; and sending the response to the network based on the local ID of the first UE.
[0009] In a sixth aspect, a communication method is provided. The method includes: sending a first message at a base station and to a first UE, the first message indicating that the first UE is switched to communicate with the base station via a second UE in an idle state or an inactive state; sending an ID of the first UE to the first UE; and performing data transmission with the first UE via the second UE based on the local ID of the first UE.
[0010] In a seventh aspect, a computer-readable medium is provided, the computer-readable medium comprising program instructions for causing an apparatus to execute the method according to the fourth aspect, the fifth aspect, or the sixth aspect of the present disclosure.
[0011] It should be understood that the invention summary is not intended to indicate the key or essential features of the embodiments of the present disclosure, nor is it intended to limit the scope of the present disclosure. Other features of the present disclosure will become readily understood through the following description. BRIEF DESCRIPTION OF THE DRAWINGS
[0012] The above and other objects, features and advantages of the present disclosure will become more apparent through a more detailed description of some embodiments of the present disclosure in the accompanying drawings, in which:
[0013] Figure 1A An example communication environment is shown in which example embodiments of the present disclosure may be implemented;
[0014] Figure 1B A schematic diagram illustrating a protocol stack in which some embodiments of the present disclosure may be implemented;
[0015] Figure 2 A schematic diagram illustrating a process for communication for a sidelink relay according to some embodiments of the present disclosure is illustrated;
[0016] Figure 3 A schematic diagram illustrating a process of exemplary communication according to some embodiments of the present disclosure, in which a remote UE obtains a local ID of the remote UE from a target BS after a path switch, and a target relay UE obtains a local ID of the remote UE from the target BS during a path switch;
[0017] Figure 4 A schematic diagram illustrating a process of exemplary communication according to some embodiments of the present disclosure, in which a remote UE obtains a local ID of the remote UE from a target relay UE after a path switch, and the target relay UE obtains a local ID of the remote UE from a target BS during a path switch;
[0018] Figure 5 A schematic diagram illustrating a process of exemplary communication according to some embodiments of the present disclosure, in which a remote UE and a target relay UE obtain a local ID of the remote UE from a target BS during a path switch;
[0019] Figure 6 A schematic diagram illustrating a process of exemplary communication according to some embodiments of the present disclosure, in which a remote UE obtains a local ID of the remote UE from a target BS during a path switch, and a target relay UE obtains a local ID of the remote UE from the remote UE during a path switch;
[0020] Figure 7 A flow chart illustrating a method of example communication implemented at a first UE as a remote UE according to some embodiments of the present disclosure;
[0021] Figure 8 A flow chart illustrating a method of example communication implemented at a second UE as a target relay UE according to some embodiments of the present disclosure;
[0022] Fig. 9 A flowchart illustrating an example method of communication implemented at a BS as a target BS according to some embodiments of the present disclosure; and
[0023] Fig.10 A simplified block diagram of an apparatus suitable for implementing embodiments of the present disclosure is illustrated.
[0024] Throughout the drawings, the same or similar reference numerals refer to the same or similar elements. DETAILED DESCRIPTION
[0025] The principle of the present disclosure will now be described with reference to some embodiments. It should be understood that these embodiments are described only for illustrative purposes, and are helpful for those skilled in the art to understand and implement the present disclosure, without indicating any limitation to the scope of the present disclosure. In addition to the methods described below, the disclosure described herein can be implemented in various ways.
[0026] In the following description and claims, unless defined otherwise, all technical and scientific terms used herein have the same meaning as commonly understood by one of ordinary skill in the art to which this disclosure belongs.
[0027] The terms used herein are only for describing specific embodiments and are not intended to limit the exemplary embodiments. For example, as used herein, the singular forms "a", "a kind of" and "the" are intended to include the plural forms as well, unless the context otherwise indicates. The terms "include", "have", "include" when used herein specify the presence of stated features, elements and / or components, etc., but do not exclude the presence or addition of one or more other features, elements, components and / or combinations thereof. In addition, when describing specific features, structures or characteristics in conjunction with some embodiments, it is considered that it is within the knowledge of those skilled in the art to implement such features, structures or characteristics in conjunction with other embodiments that are explicitly or not explicitly described.
[0028] It should also be understood that, although the terms "first", "second", etc. may be used to describe various elements in this article, these elements should not be limited by these terms. These terms are only used to distinguish one element from another element. For example, the first element can be named as the second element and similarly the second element can be named as the first element without departing from the scope of the exemplary embodiment. As used herein, the term "and / or" includes any combination and all combinations of one or more of the listed terms.
[0029] In the context of the present disclosure, the term "local ID" may be used interchangeably with the term "temporary ID", and the term "SRAP layer" may be used interchangeably with the term "adaptation layer".
[0030] As described above, although it is agreed that the target relay UE can send a SUI message to obtain the local ID of the remote UE, it is still unclear how the remote UE can obtain its local ID.
[0031] In view of this, an embodiment of the present disclosure proposes a solution for allocating a local ID of a remote UE, particularly during a path switch to a target relay UE in an idle or inactive state. In the solution, the remote UE obtains the local ID of the remote UE from the target relay UE or the base station. The target relay UE obtains the local ID of the remote UE from the remote UE or the base station. Then, the remote UE performs data transmission with the base station via the target relay UE.
[0032] According to an embodiment of the present disclosure, allocation of a local ID of a remote UE is clarified.
[0033] The following will refer to Figures 1A to 10 The principles and specific implementations of the present disclosure are described in detail.
[0034] Figure 1A An example communication environment 100A is shown in which embodiments of the present disclosure may be implemented. Figure 1A As shown, communication environment 100A may include UE 110, UE 120, UE 130, BS 140, and BS 150. BS 140 may provide cell 141 serving one or more UEs, and BS 150 may provide cell 151 serving one or more UEs. Figure 1A In the example of , UE 110 and UE 130 are located in cell 141, and UE 120 is located in cell 151. BS 140 and BS 150 may form a network, for example, an access network to a core network (not shown).
[0035] In some embodiments, when UE 110 is located within cell 141, UE 110 may communicate directly with BS 140. In some embodiments, when UE 110 is located outside or within cell 141, UE 110 may communicate with BS 140 via another UE (e.g., UE 130). In this case, UE 110 may be referred to as a remote UE, and UE 130 may be referred to as a relay UE. Similarly, when a second UE 120 is located within cell 151, UE 120 may communicate directly with BS 150.
[0036] In some embodiments, a UE (e.g., UE 110, 120, or 130) and a BS (e.g., BS 140 or 150) may communicate with each other via a channel such as a wireless communication channel. The wireless communication channel may include a physical uplink control channel (PUCCH), a physical uplink shared channel (PUSCH), a physical random access channel (PRACH), a physical downlink control channel (PDCCH), a physical downlink shared channel (PDSCH), and a physical broadcast channel (PBCH). Of course, any other suitable channel is also feasible.
[0037] In some embodiments, any two of the UEs (e.g., UEs 110, 120, and 130) may communicate with each other via sidelink channels such as a physical sidelink shared channel (PSSCH), a physical sidelink control channel (PSCCH), a physical sidelink feedback channel (PSFCH), a physical sidelink broadcast channel (PSBCH), and the like.
[0038] The communication in the communication environment 100A may conform to any suitable standard, including but not limited to Global System for Mobile Communications (GSM), Long Term Evolution (LTE), LTE-Evolution, LTE-Advanced (LTE-A), New Radio (NR), Wideband Code Division Multiple Access (WCDMA), Code Division Multiple Access (CDMA), GSM EDGE Radio Access Network (GERAN), Machine Type Communication (MTC), etc. In addition, the communication may be performed according to any generation of communication protocols currently known or to be developed in the future. The embodiments of the present disclosure may perform communication according to any generation of communication protocols currently known or to be developed in the future. Examples of communication protocols include but are not limited to first generation (1G) communication protocols, second generation (2G) communication protocols, 2.5G communication protocols, 2.75G communication protocols, third generation (3G) communication protocols, fourth generation (4G) communication protocols, 4.5G communication protocols, fifth generation (5G) communication protocols, 5.5G advanced networks, 5G advanced networks, or sixth generation (6G) networks.
[0039] It should be understood that Figure 1A The number of devices and cells in the communication environment 100A is for illustrative purposes only and does not imply any limitation to the present disclosure. The communication environment 100A may include any suitable number of UEs, BSs, and cells suitable for implementing the specific implementation of the present disclosure.
[0040] The communication between the UE and the BS or between the UEs in the communication environment 100A may be performed according to a protocol stack. Generally speaking, for a communication device (such as a UE or a BS), there are multiple entities in multiple network protocol layers in the protocol stack, and the multiple entities may be configured to implement corresponding processing for data or signaling sent from and received by the communication device. Figure 1B Schematic diagram 100B illustrates a protocol stack in which some embodiments of the present disclosure may be implemented.
[0041] like Figure 1BAs shown, the remote UE may include entities of the physical (PHY) layer, the medium access control (MAC) layer, the radio link control (RLC) layer, and the sidelink relay adaptation protocol (SRAP) layer for the sidelink (SL) interface, and entities of the packet data convergence protocol (PDCP) layer and the service data adaptation protocol (SDAP) layer for the Uu interface. The relay UE may include entities of the PHY layer, MAC layer, RLC layer, and SRAP layer for the SL interface, and entities of the PHY layer, MAC layer, RLC layer, and SRAP layer for the Uu interface. The BS may include entities of the PHY layer, MAC layer, RLC layer, SRAP layer, PDCP layer, and SDAP layer for the Uu interface.
[0042] refer to Figure 1B , a single Uu SRAP entity (also referred to as Uu adaptation layer in this article) is configured in the relay UE, while one PC5 SRAP entity (also referred to as PC5 adaptation layer in this article) is used to handle the remote UE. The PC5 adaptation layer can support adaptation layers on PC5 only for bearer mapping, with the following exceptions: for signaling radio bearer 0 (SRB0), there is no adaptation layer on the PC5 hop; for broadcast control channel (BCCH) and paging control channel (PCCH), there is no adaptation layer on the PC5 hop; and Uu radio link failure (RLF) is not indicated in the adaptation layer header (also referred to as SRAP header in this article for convenience). For the Uu adaptation layer, the serving BS of the relay UE assigns the local ID of the remote UE. Even for the first UL RRC message (SRB0), the relay UE is pre-configured with some default local IDs to be used. As Figure 1B As shown, the SRAP header 160 may include a remote UE ID 161 and a radio bearer ID 162. The remote UE ID 161 may include a local ID of the remote UE. The radio bearer ID 162 may include a Uu radio bearer ID of the remote UE.
[0043] return Figure 1AIn some scenarios, UE 110 may communicate directly with BS 140 at an earlier stage. When UE 110 moves, UE 110 may need to perform path switching in order to communicate with BS 150 via UE 120. This scenario is called direct to indirect path switching. In some scenarios, UE 110 may communicate with BS 140 via UE 130 at an earlier stage. When UE 110 moves, UE 110 may need to perform path switching in order to communicate with BS 150 via UE 120. This scenario is called indirect to indirect path switching. In these scenarios, UE 110 is called a remote UE, UE 120 is called a target relay UE, BS 140 serving the remote UE is called a source BS, and BS 150 serving the target relay UE is called a target BS.
[0044] It should be understood that although BS140 and BS150 Figure 1A 1 and 2. Although BS140 and BS150 are shown as different BSs in FIG. 1, BS140 and BS150 may also be the same BS. In this case, the source BS and the target BS may be the same BS.
[0045] For direct-to-indirect path switching and indirect-to-indirect path switching, the embodiments of the present disclosure provide a solution for allocating a local ID of a remote UE when the target relay UE is in an idle state or an inactive state. Figure 2 To describe the solution.
[0046] Figure 2 A schematic diagram illustrating a process 200 of communicating with an exemplary sidelink relay according to some embodiments of the present disclosure is shown. For the purpose of discussion, reference will be made to Figure 1A Process 200 is described. Process 200 may involve Figure 1A UE 110, UE 120, BS 140 and BS 150 are illustrated in FIG. Figure 2 The steps and the order of steps in are for illustration only and are not for limitation. It is assumed that UE 110 is used as a remote UE and UE 120 is used as a target relay UE in an idle state or an inactive state. Therefore, BS 140 is used as a source BS and BS 150 is used as a target BS. For convenience, hereinafter, UE 110 is also referred to as remote UE 110, UE 120 is also referred to as target relay UE 120, BS 140 is also referred to as source BS 140, and BS 150 is also referred to as target BS 150.
[0047] like Figure 2As shown, the target BS 150 sends 210 a message (also referred to herein as a first message for convenience) to the remote UE 110, which indicates that the remote UE 110 is switched to communicate with the target BS 150 via the target relay UE 120. The first message may include a configuration for the path switch. In some embodiments, the first message may be an RRC reconfiguration message. Of course, any other suitable message is also feasible.
[0048] In some embodiments, the target BS 150 may send 211 a measurement configuration to the remote UE 110 via the source BS 140. The remote UE 110 may perform 212 measurements based on the measurement configuration and report 213 the measurements to the target BS 150 via the source BS 140. Based on the report, the target BS 150 may decide to switch to the target relay UE 120 and then send 214 a path switch command (i.e., a first message) to the UE 110 via the source BS 140. In some embodiments where the source BS 140 and the target BS 150 are the same BS, the target BS 150 may send the path switch command directly to the remote UE 110.
[0049] After receiving the first message, the remote UE 110 obtains 220 a local ID of the remote UE 110. The local ID of the remote UE 110 is assigned by the target BS 150. In some embodiments, the remote UE 110 may obtain the local ID of the remote UE 110 from the target BS 150. In some embodiments, the remote UE 110 may obtain the local ID of the remote UE 110 from the target relay UE 120.
[0050] After receiving the first message, the remote UE 110 may apply 230 the configuration for the path switch and send 240 a response to the first message to the target relay UE 120. The response indicates that the path switch is complete. For example, the remote UE 110 may send an RRC reconfiguration complete message to the target relay UE 120 as a response to the first message.
[0051] After receiving the response to the first message, the target relay UE 120 obtains 250 the local ID of the remote UE 110. In some embodiments, the target relay UE 120 may obtain the local ID of the remote UE 110 from the target BS 150. In some embodiments, the target relay UE 120 may obtain the local ID of the remote UE 110 from the remote UE 110. After establishing a connection with the target BS 150, the target relay UE 120 may send 260 a message to the target BS 150 indicating that the path switch is complete.
[0052] After receiving the message indicating that the path switch is completed, the target BS 150 may perform 270 data transmission with the remote UE 110 via the target relay UE 120 .
[0053] In this way, the remote UE and the target relay UE can obtain the local ID of the remote UE, and the sidelink relay communication can be facilitated. Figures 3 to 6 Some example implementations of the solution are described.
[0054] Figure 3 A schematic diagram illustrating a process 300 of an example communication in which a remote UE obtains a local ID of the remote UE from a target BS after a path switch and a target relay UE obtains a local ID of the remote UE from a target BS during a path switch according to some embodiments of the present disclosure. For discussion purposes, reference will be made to Figure 1A Process 300 is described. Figure 3 The steps and step order in the description are for illustration only and are not intended to be limiting.
[0055] refer to Figure 3 , the target BS 150 may send 310 a first message to the remote UE 110, the first message indicating that the remote UE 110 is switched to communicate with the target BS 150 via the target relay UE 120. The target relay UE 120 is in an idle state or an inactive state. In this embodiment, the first message does not indicate the local ID of the remote UE 110. In other words, the target BS 150 does not provide the local ID to the remote UE 110 in the path switch command. For example, the target BS 150 may send an RRC reconfiguration message that does not include the local ID of the remote UE 110. Of course, any other suitable message is also feasible.
[0056] In some embodiments, target BS 150 may send 311 the first message to source BS 140, and source BS 140 may forward 312 the first message to remote UE 110. In some embodiments where target BS 150 and source BS 140 are the same BS, target BS 150 may send the first message to remote UE 110 directly.
[0057] After receiving the first message, the remote UE 110 may establish 320 a sidelink connection (e.g., a PC5 link) with the target relay UE 120. The remote UE 110 may then send 330 a response to the first message to the target BS 150 and via the target relay UE 120 indicating that the handover is complete. In this case, the response does not include the local ID in the SRAP header or does not include the SRAP header. For example, the remote UE 110 may send an RRC reconfiguration complete message in which the local ID field in the PC5 SRAP header is not present or the PC5 SRAP header is not present. Of course, any other suitable message is also possible.
[0058] In some embodiments, the remote UE 110 may send 331 a response to the first message to the target relay UE 120. After receiving the response to the first message, the target relay UE 120 may establish 332 a connection (e.g., a UuRRC connection) with the target BS 150. The target relay UE 120 may send 333 a request to the target BS 150 for obtaining the local ID of the remote UE 110. For example, the target relay UE 120 may send a SUI message or any other suitable message. In response to the request, the target BS 150 may send 334 a message (also referred to herein as the fourth message for convenience) to the target relay UE 120 indicating the local ID of the remote UE 110. For example, the target BS 150 may send an RRC reconfiguration message including the local ID of the remote UE 110 to the target relay UE 120. Of course, any other suitable message is also feasible.
[0059] The target relay UE 120 may add 335 the local ID of the remote UE 110 in the UuSRAP header of the response to the fourth message. The response to the fourth message indicates that the handover is complete. Then, the target relay UE 120 may send 336 a response to the fourth message to the target BS 150. For example, the target relay UE 120 may send an RRC reconfiguration complete message as a response to the fourth message to indicate that the handover is complete. Of course, any other suitable message is also feasible.
[0060] After receiving the response to the fourth message (e.g., the RRC reconfiguration complete message), the target BS 150 may send 340 a message (also referred to herein as a second message for convenience) to the remote UE 110 and via the target relay UE 120, the message indicating the local ID of the remote UE 110. In some embodiments, the second message may be an RRC reconfiguration message including the local ID of the remote UE 110. It should be understood that any other suitable message is also feasible.
[0061] After receiving the second message, the remote UE 110 may send 350 a response to the second message to the target BS 150 and via the target relay UE 120. In this case, there is a PC5 SRAP header in the response to the second message. For example, the remote UE 110 may send an RRC reconfiguration completion message to the target BS 150 via the target relay UE 120 as a response to the second message. It should be understood that any other suitable message is also feasible. In some embodiments where there is uplink data to be sent at the remote UE 110, the remote UE 110 may multiplex the uplink data with the response to the second message. In this case, the remote UE may have to delay its uplink data transmission by at least two RRC messages.
[0062] In other words, in process 300, if sl-PathSwitchConfig is included in the RRC reconfiguration message, the remote UE may obtain the local ID of the remote UE from the subsequent RRC reconfiguration message.
[0063] Utilizing process 300, after sending a local ID to a target relay UE, the target BS may send the same local ID to a remote UE (e.g., via a Uu RRC message). Thus, local ID conflict issues may be avoided. The target BS may not wish to assign a local ID to a remote UE until it is determined that the remote UE will be able to connect to the target BS via a target relay UE under coverage of the target BS. Given the uncertainty of direct-to-indirect path switching or indirect-to-indirect path switching, the target BS preferably waits for the target relay UE to connect first. Otherwise, the target BS requires additional implementations to assign or cycle unused local IDs.
[0064] Figure 4 A schematic diagram illustrating a process 400 of an example communication in which a remote UE obtains a local ID of the remote UE from a target relay UE after a path switch and a target relay UE obtains a local ID of the remote UE from a target BS during a path switch according to some embodiments of the present disclosure. For discussion purposes, reference will be made to Figure 1A Process 400 is described. Figure 4 The steps and step order in the description are for illustration only and are not intended to be limiting.
[0065] refer to Figure 4, the target BS 150 may send 410 a first message to the remote UE 110, the first message indicating that the remote UE 110 is switched to communicate with the target BS 150 via the target relay UE 120. The target relay UE 120 is in an idle state or an inactive state. In this embodiment, the first message does not indicate the local ID of the remote UE 110. In other words, the target BS 150 does not provide the local ID to the remote UE 110 in the path switch command. For example, the target BS 150 may send an RRC reconfiguration message that does not include the local ID of the remote UE 110. Of course, any other suitable message is also feasible.
[0066] In some embodiments, target BS 150 may send 411 a first message to source BS 140, and source BS 140 may forward 412 the first message to remote UE 110. In some embodiments where target BS 150 and source BS 140 are the same BS, target BS 150 may send the first message to remote UE 110 directly.
[0067] After receiving the first message, the remote UE 110 may establish 420 a sidelink connection (e.g., a PC5 link) with the target relay UE 120. The remote UE 110 may then send 430 a response to the first message to the target BS 150 and via the target relay UE 120 indicating that the handover is complete. In this case, the response does not include the local ID in the SRAP header or does not include the SRAP header. For example, the remote UE 110 may send an RRC reconfiguration complete message in which the local ID field in the PC5 SRAP header is not present or the PC5 SRAP header is not present. Of course, any other suitable message is also possible.
[0068] In some embodiments, the remote UE 110 may send 431 a response to the first message to the target relay UE 120. After receiving the response to the first message, the target relay UE 120 may establish 432 a connection (e.g., a UuRRC connection) with the target BS 150. The target relay UE 120 may send 433 a request to the target BS 150 for obtaining the local ID of the remote UE 110. For example, the target relay UE 120 may send a SUI message or any other suitable message. In response to the request, the target BS 150 may send 434 a message (also referred to herein as the fourth message for convenience) to the target relay UE 120 indicating the local ID of the remote UE 110. For example, the target BS 150 may send an RRC reconfiguration message including the local ID of the remote UE 110 to the target relay UE 120. Of course, any other suitable message is also feasible.
[0069] The target relay UE 120 may add 435 the local ID of the remote UE 110 in the UuSRAP header of the response to the fourth message. The response to the fourth message indicates that the handover is complete. Then, the target relay UE 120 may send 436 a response to the fourth message to the target BS 150. For example, the target relay UE 120 may send an RRC reconfiguration complete message as a response to the fourth message to indicate that the handover is complete. Of course, any other suitable message is also feasible.
[0070] After sending a response to the fourth message (e.g., RRC reconfiguration complete message), the target relay UE 120 may send 440 a message (also referred to herein as a third message for convenience) to the remote UE 110, which indicates the local ID of the remote UE 110. In some embodiments, the third message may be a PC5 RRC message. For example, the target relay UE 120 may reuse an existing PC5 RRC message such as a NotificationMessageSidelink message to send the local ID to the remote UE 110. It should be understood that any other existing or newly defined PC5 RRC message is also feasible.
[0071] After receiving the third message, the remote UE 110 may perform 450 data transmission with the target BS 150 via the target relay UE 120. In some embodiments where there is uplink data to be sent at the remote UE 110, the remote UE 110 may send the uplink data to the target BS 150 via the target relay UE 120. The PC5 SRAP header is present in the uplink data. In this case, the remote UE may also have to delay its uplink data transmission by at least two RRC messages.
[0072] In other words, in process 400, if sl-PathSwitchConfig is included in the RRC reconfiguration message, the remote UE may obtain the local ID of the remote UE from a subsequent PC5 RRC message.
[0073] Utilizing process 400, after receiving the local ID from the target BS, the target relay UE may send the same local ID to the remote UE (e.g., via a PC5 RRC message). Thus, local ID conflict issues may also be avoided. The target BS may not wish to assign a local ID to a remote UE until it is determined that the remote UE will be able to connect to the target BS via a target relay UE under the coverage of the target BS. Given the uncertainty of direct to indirect path switching or indirect to indirect path switching, the target BS preferably waits for the target relay UE to connect first. Otherwise, the target BS requires additional implementations to assign or cycle unused local IDs.
[0074] Figure 5 A schematic diagram illustrating a process 500 of an example communication in which a remote UE and a target relay UE obtain a local ID of the remote UE from a target BS during a path switch according to some embodiments of the present disclosure. For discussion purposes, reference will be made to Figure 1A Process 500 is described. Figure 5 The steps and step order in the description are for illustration only and are not intended to be limiting.
[0075] refer to Figure 5 , the target BS 150 may send 510 a first message to the remote UE 110, the first message indicating that the remote UE 110 is switched to communicate with the target BS 150 via the target relay UE 120. The target relay UE 120 is in an idle state or an inactive state. In this embodiment, the first message also indicates the local ID of the remote UE 110. In other words, the target BS 150 provides the local ID to the remote UE 110 in the path switch command. For example, the target BS 150 may send an RRC reconfiguration message including the local ID of the remote UE 110. Of course, any other suitable message is also feasible.
[0076] In some embodiments, target BS 150 may send 511 a first message to source BS 140, and source BS 140 may forward 512 the first message to remote UE 110. In some embodiments where target BS 150 and source BS 140 are the same BS, target BS 150 may send the first message to remote UE 110 directly.
[0077] After receiving the first message, the remote UE 110 may establish 520 a sidelink connection (e.g., a PC5 link) with the target relay UE 120. The remote UE 110 may then send 530 a response to the first message to the target BS 150 and via the target relay UE 120 indicating that the handover is complete. In this case, the response includes the local ID in the SRAP header. For example, the remote UE 110 may send an RRC reconfiguration complete message in which a PC5 SRAP header with a local ID field is present. Of course, any other suitable message is also possible.
[0078] In some embodiments where there is uplink data to be sent at the remote UE 110, the remote UE 110 may multiplex the uplink data with a response to the first message (e.g., an RRC reconfiguration complete message). In this way, the uplink data at the remote UE may be sent as early as the first RRC reconfiguration complete message. Therefore, no delay in uplink data transmission is incurred.
[0079] In some embodiments, the remote UE 110 may send 531 a response to the first message to the target relay UE 120. After receiving the response to the first message, the target relay UE 120 may establish 532 a connection (e.g., a UuRRC connection) with the target BS 150. The target relay UE 120 may send 533 a request to obtain the local ID of the remote UE 110 to the target BS 150. For example, the target relay UE 120 may send a SUI message or any other suitable message. In response to the request, the target BS 150 may send 534 a message (also referred to as the fourth message herein for convenience) to the target relay UE 120, which indicates the local ID of the remote UE 110. In this embodiment, the target BS 150 ensures that the local ID included in the fourth message is the same as the local ID included in the first message. For example, the target BS 150 may send an RRC reconfiguration message including the local ID of the remote UE 110 to the target relay UE 120. Of course, any other suitable message is also feasible.
[0080] The target relay UE 120 may send 535 a response to the fourth message to the target BS 150. For example, the target relay UE 120 may send an RRC reconfiguration complete message as a response to the fourth message to indicate that the handover is complete. Of course, any other suitable message is also feasible.
[0081] Then, the remote UE 110 may perform data transmission with the target BS 150 via the target relay UE 120. In some embodiments where there is uplink data multiplexed with the response to the first message, the target relay UE 120 may multiplex the uplink data with the response to the fourth message (e.g., RRC reconfiguration complete message). In this way, the uplink data from the remote UE is forwarded to the target BS by the target relay UE.
[0082] In some embodiments, the remote UE 110 may receive 540 downlink data from the target BS 150 via the target relay UE 120. The remote UE 110 may determine 550 whether the ID of the remote UE 110 in the SRAP header of the downlink data is different from the local ID obtained from the first message. If the ID of the remote UE 110 in the SRAP header of the downlink data is different from the local ID in the first message, the remote UE may trigger 560 an RRC re-establishment procedure.
[0083] In other words, in process 500, if sl-PathSwitchConfig is included in the RRC reconfiguration message, the remote UE can obtain the local ID of the remote UE from sl-PathSwitchConfig. The target BS is responsible for ensuring that the local ID provided in the path switch command is the same as the local ID obtained by the remote UE. If the remote UE identifies that the local ID in the PC5 SRAP header of the subsequent downlink transmission is different from the local ID received in the path switch command, the remote UE can declare an error and trigger the RRC reestablishment procedure.
[0084] With process 500, the target BS needs to ensure that the local ID provided in the path switch command is the same as the local ID obtained via the SUI message. Although the target BS may need additional implementations to allocate or recycle unused local IDs, it will not cause delays in uplink data transmission.
[0085] Figure 6 A schematic diagram illustrating a process 600 of an example communication in which a remote UE obtains a local ID of the remote UE from a target BS during a path switch and a target relay UE obtains a local ID of the remote UE from the remote UE during a path switch according to some embodiments of the present disclosure. For discussion purposes, reference will be made to Figure 1A Process 600 is described. Figure 6 The steps and step order in the description are for illustration only and are not intended to be limiting.
[0086] refer to Figure 6 , the target BS 150 may send 610 a first message to the remote UE 110, the first message indicating that the remote UE 110 is switched to communicate with the target BS 150 via the target relay UE 120. The target relay UE 120 is in an idle state or an inactive state. In this embodiment, the first message also indicates the local ID of the remote UE 110. In other words, the target BS 150 provides the local ID to the remote UE 110 in the path switch command. For example, the target BS 150 may send an RRC reconfiguration message including the local ID of the remote UE 110. Of course, any other suitable message is also feasible.
[0087] In some embodiments, target BS 150 may send 611 a first message to source BS 140, and source BS 140 may forward 612 the first message to remote UE 110. In some embodiments where target BS 150 and source BS 140 are the same BS, target BS 150 may send the first message to remote UE 110 directly.
[0088] After receiving the first message, the remote UE 110 may establish 620 a sidelink connection (e.g., a PC5 link) with the target relay UE 120. The remote UE 110 may then send 630 a response to the first message to the target BS 150 and via the target relay UE 120 indicating that the handover is complete. In this case, the response includes the local ID in the SRAP header. For example, the remote UE 110 may send an RRC reconfiguration complete message in which a PC5 SRAP header with a local ID field is present. Of course, any other suitable message is also possible.
[0089] In some embodiments where there is uplink data to be sent at the remote UE 110, the remote UE 110 may multiplex the uplink data with a response to the first message (e.g., an RRC reconfiguration complete message). In this way, the uplink data at the remote UE may be sent as early as the first RRC reconfiguration complete message. Therefore, no delay in uplink data transmission is incurred.
[0090] In some embodiments, the remote UE 110 may send 631 a response to the first message to the target relay UE 120. After receiving the response to the first message, the target relay UE 120 may obtain 632 a local ID from the PC5 SRAP header of the response to the first message. The target relay UE 120 may establish 633 a connection with the target BS 150 and send 634 a response to the first message to the target BS 150. In some embodiments where there is uplink data multiplexed with the response to the first message, the target relay UE 120 may send the response multiplexed with the uplink data to the target BS 150.
[0091] The remote UE 110 may then perform 640 data transmission with the target BS 150 via the target relay UE 120 .
[0092] In other words, in process 600, if sl-PathSwitchConfig is included in the RRC reconfiguration message, the remote UE may obtain the local ID of the remote UE from the sl-PathSwitchConfig.
[0093] Using process 600, the target relay UE does not request the local ID of the remote UE via the SUI. The target relay UE only reads the local ID of the remote UE from the PC5SRAP header of the response to the first message (e.g., the RRC reconfiguration complete message), and uses the local ID in all subsequent uplink messages and downlink messages. Therefore, the uplink data at the remote UE can be sent as early as the first RRC reconfiguration complete message, and no delay in the uplink data transmission is caused. In addition, there is no new requirement for the network.
[0094] Corresponding to the above process, the embodiments of the present disclosure also provide methods implemented at the remote UE, the target relay UE and the target BS. Figures 7 to 9 to describe these methods.
[0095] Figure 7 A flowchart of a method 700 of example communication implemented at a first UE as a remote UE according to some embodiments of the present disclosure is illustrated. The method 700 may be implemented at a device (e.g., Figure 1A It should be understood that the method 700 may include additional blocks not shown and / or some of the blocks shown may be omitted, and the scope of the present disclosure is not limited in this regard.
[0096] At block 710, a first UE (e.g., remote UE 110) receives a first message (i.e., a path switch command) from a network (e.g., target BS 150) indicating that remote UE 110 is switched to communicate with target BS 150 via a second UE (e.g., target relay UE 120). Target relay UE 120 is in an idle state or an inactive state. In some embodiments, remote UE 110 may receive the first message from target BS 150 via source BS 140. In some embodiments where target BS 150 and source BS 140 are the same BS, remote UE 110 may receive the first message directly from target BS 150.
[0097] At block 720 , the remote UE 110 obtains the local ID of the remote UE 110 from the target relay UE 120 or the target BS 150 .
[0098] At block 730 , the remote UE 110 performs data transmission with the target BS 150 via the target relay UE 120 based on the local ID of the remote UE 110 .
[0099] In some embodiments, the first message does not indicate the local ID of the remote UE 110. In these embodiments, the remote UE 110 may establish a side link connection with the target relay UE 120, and send a response to the first message indicating that the handover has been completed to the target BS 150 and via the target relay UE 120. The response does not include the local ID in the SRAP header or does not include the SRAP header. In these embodiments, the remote UE 110 may receive a second message from the target BS 150 and via the target relay UE 120, the second message indicating the local ID of the remote UE 110. In some alternative or additional embodiments, the remote UE 110 may send uplink data multiplexed with the response to the second message to the target BS 150 and via the target relay UE 120. In this way, the remote UE can obtain its local ID from the network after the path switch, and perform data transmission with the network based on the local ID.
[0100] Alternatively, the remote UE 110 may receive a third message from the target relay UE 120 and via the side link connection, the third message indicating the local ID of the remote UE 110. In some embodiments, the remote UE 110 may transmit uplink data to the target BS 150 and via the target relay UE 120, the uplink data including the local ID in the SRAP header. In this way, the remote UE may obtain its local ID from the target relay UE after the path switch, and perform data transmission with the network based on the local ID.
[0101] Alternatively, the first message may also indicate a local ID of the remote UE 110. In these embodiments, the remote UE 110 may obtain the local ID of the remote UE 110 from the first message. In some embodiments, the remote UE 110 may establish a side link connection with the target relay UE 120 and send a response to the first message indicating that the handover is complete to the target BS 150 and via the target relay UE 120. The response includes the local ID in the SRAP header. In some embodiments, the remote UE 110 may send uplink data multiplexed with the response to the first message to the target BS 150 and via the target relay UE 120.
[0102] In some implementations, remote UE 110 may also receive downlink data from target BS 150 via target relay UE 120. If the ID of remote UE 110 in the SRAP header associated with the downlink data is different from the local ID obtained from the first message, remote UE 110 may trigger an RRC re-establishment procedure.
[0103] Using the method 700, the remote UE can obtain its local ID and perform data transmission with the network based on the local ID.
[0104] Figure 8 A flow chart of a method 800 of example communication implemented at a second UE as a target relay UE according to some embodiments of the present disclosure is shown. The method 800 may be implemented at a device (e.g., the target relay UE 120 shown in FIG. 1 ). It should be understood that the method 800 may include additional blocks not shown and / or some of the blocks shown may be omitted, and the scope of the present disclosure is not limited in this regard.
[0105] At block 810, the second UE (e.g., target relay UE 120) receives a response to the first message from the first UE (e.g., remote UE 110). The first message indicates that the remote UE 110 is switched to communicate with the network (e.g., target BS 150) via the target relay UE 120 in an idle state or an inactive state. The response indicates that the switch is complete.
[0106] At block 820 , the target relay UE 120 obtains the local ID of the remote UE 110 from the remote UE 110 or the target BS 150 .
[0107] At block 830 , the target relay UE 120 sends a response to the first message to the target BS 150 based on the local ID of the remote UE 110 .
[0108] In some embodiments, the response does not include a local ID in the SRAP header or does not include a SRAP header. In these embodiments, the target relay UE 120 may establish a connection with the target BS 150 and send a request to the target BS 150 for obtaining the local ID of the remote UE 110. The target relay UE 120 may then receive a fourth message from the target BS 150 indicating the local ID of the remote UE 110. In this way, the target relay UE may obtain the local ID of the remote UE from the network.
[0109] In some embodiments, the target relay UE 120 may also send a third message to the remote UE, the third message indicating the local ID of the remote UE. In this way, the target relay UE may notify the remote UE of the same local ID. In some embodiments, the target relay UE 120 may also receive uplink data from the remote UE 110, the uplink data including the local ID in the SRAP header, and send the uplink data to the target BS 150. In this way, sidelink relay communication may be performed based on the local ID of the remote UE.
[0110] Alternatively, the response may include the local ID in the SRAP header. In some embodiments, the target relay UE 120 may establish a connection with the target BS 150 and send a request to the target BS 150 for obtaining the local ID of the remote UE 110. Then, the target relay UE 120 may receive a fourth message from the target BS 150, the fourth message indicating the local ID of the remote UE 110. In this way, the target relay UE may obtain the same local ID of the remote UE from the network.
[0111] In some embodiments, the target relay UE 120 may receive uplink data multiplexed with a response to the first message from the remote UE 110. In these embodiments, the target relay UE 120 may send uplink data multiplexed with a response to the fourth message to the target BS 150.
[0112] In some alternative embodiments where the response may include a local ID in the SRAP header, the target relay UE 120 may obtain the local ID from the SRAP header. That is, the target relay UE may obtain the same local ID of the remote UE from the remote UE. In this case, the target relay UE 120 may establish a connection with the target BS 150 and send a response to the first message to the target BS 150.
[0113] In some embodiments, the target relay UE 120 may receive uplink data multiplexed with the response to the first message from the remote UE 110. In these embodiments, the target relay UE 120 may send the uplink data multiplexed with the response to the first message to the target BS 150.
[0114] Using method 800, a target relay UE may obtain a local ID of a remote UE and forward data transmissions between the remote UE and a network based on the local ID.
[0115] Fig. 9 A flowchart of a method 900 of example communication implemented at a BS as a target BS according to some embodiments of the present disclosure is illustrated. The method 900 may be performed at a device (e.g., Figure 1A It should be understood that the method 900 may include additional blocks not shown and / or some of the blocks shown may be omitted, and the scope of the present disclosure is not limited in this regard.
[0116] At block 910, a BS (e.g., target BS 150) sends a first message to a first UE (e.g., remote UE 110), the first message indicating that remote UE 110 is switched to communicate with target BS 150 via a second UE (e.g., target relay UE 120) in an idle state or an inactive state. In some embodiments, target BS 150 may send the first message to remote UE 110 via source BS 140. In some embodiments where target BS 150 and source BS 140 are the same BS, target BS 150 may send the first message directly to remote UE 110.
[0117] At block 920 , the target BS 150 sends the local ID of the remote UE 110 to the remote UE 110 .
[0118] At block 930 , the target BS 150 performs data transmission with the remote UE 110 via the target relay UE 120 based on the local ID of the remote UE 110 .
[0119] In some embodiments, the first message does not indicate the local ID of the remote UE 110. In these embodiments, the target BS 150 may establish a connection with the target relay UE 120. The target BS 150 may receive a request for obtaining the local ID of the remote UE 110 from the target relay UE 120, and send a fourth message to the target relay UE 120, the fourth message indicating the local ID of the remote UE 110. In response to receiving a response to the fourth message from the target relay UE 120 indicating that the handover is complete, the target BS 150 may send a second message to the remote UE 110, the second message indicating the local ID of the remote UE 110. In some embodiments, the target BS 150 may receive uplink data multiplexed with the response to the second message from the remote UE 110 via the target relay UE 120.
[0120] Alternatively, the target BS 150 may send the local ID of the remote UE 110 in the first message. In some embodiments, the target BS 150 may establish a connection with the target relay UE 120. The target BS 150 may receive a request for obtaining the local ID of the remote UE from the target relay UE 120, and send a fourth message indicating the local ID of the remote UE to the target relay UE 120. The target BS 150 may ensure that the same local ID of the remote UE 110 is transmitted to the target relay UE 120.
[0121] In some embodiments, the target BS 150 may also receive a response to the fourth message indicating that the handover is complete from the target relay UE 120. In some embodiments, the target BS 150 may receive uplink data multiplexed with the response to the fourth message from the target relay UE.
[0122] Alternatively, the target BS 150 may not transmit the local ID of the remote UE 110 to the target relay UE 120. In these embodiments, the target BS 150 may establish a connection with the target relay UE 120 and receive a response to the first message indicating that the handover is complete from the target relay UE 120. In some embodiments, the target BS 150 may receive uplink data multiplexed with the response to the first message from the target relay UE 120.
[0123] Using the method 900, the target BS may allocate a local ID to the remote UE and perform data transmission with the remote UE via the target relay UE based on the local ID.
[0124] Fig.10 1 is a simplified block diagram of a device 1000 suitable for implementing embodiments of the present disclosure. For example, a remote UE 110, a target relay UE 120, and a target BS 150 may be implemented by the device 1000. As shown, the device 1000 includes: a processor 1010; a memory 1020, which is coupled to the processor 1010; and a transceiver 1040, which is coupled to the processor 1010.
[0125] The transceiver 1040 is used for bidirectional communication. The transceiver 1040 is coupled to at least one antenna to facilitate communication. The transceiver 1040 may include a transmitter circuit system (e.g., associated with one or more transmit chains) and / or a receiver circuit system (e.g., associated with one or more receive chains). The transmitter circuit system and the receiver circuit system may employ common circuit elements, different circuit elements, or a combination thereof.
[0126] Processor 1010 may be of any type suitable for the local technology network and may include one or more of the following: as non-limiting examples, a general purpose computer, a special purpose computer, a microprocessor, a digital signal processor (DSP), and a processor based on a multi-core processor architecture. Device 1000 may have multiple processors, such as application specific integrated circuit chips, which are time-constrained by a clock that synchronizes a main processor.
[0127] The memory 1020 may include one or more non-volatile memories and one or more volatile memories. Examples of non-volatile memories include, but are not limited to, read-only memory (ROM) 1024, electrically programmable read-only memory (EPROM), flash memory, hard disk, compact disk (CD), digital video disk (DVD), and other magnetic storage devices and / or optical storage devices. Examples of volatile memories include, but are not limited to, random access memory (RAM) 1022 and other volatile memories that do not persist during power-off time.
[0128] Computer program 1030 includes computer executable instructions that are executed by associated processor 1010. Program 1030 may be stored in ROM 1024. Processor 1010 may perform any suitable operations and processes by loading program 1030 into RAM 1022.
[0129] The embodiments of the present disclosure can be implemented with the aid of the program 1030, so that the device 1000 can execute the following steps: Figures 2 to 6 Any process of the present disclosure discussed. The embodiments of the present disclosure may also be implemented by hardware or by a combination of software and hardware.
[0130] The present disclosure also provides at least one computer program product tangibly stored on a non-transitory computer readable storage medium. The computer program product includes computer executable instructions, such as those included in a program module, which are executed in a device on a target real or virtual processor to perform the above-referenced Figures 7 to 9 Any of methods 700 to 900 described above.
[0131] Further, although the operations are depicted in a particular order, this should not be understood as requiring such operations to be performed in a sequential order or in the particular order shown, or requiring the execution of all illustrated operations to achieve the desired result. In some cases, multitasking and parallel processing may be advantageous. Although the above discussion includes several specific implementation details, these details should not be understood as limitations on the scope of the present disclosure, but should be considered as descriptions of features that may be peculiar to a particular embodiment. Certain features described in the context of different embodiments may also be implemented in combination in a single embodiment. On the contrary, the various features described in the context of a single embodiment may also be implemented in multiple embodiments individually or in the form of any suitable sub-combination.
[0132] Although the disclosure has been described in language specific to structural features and / or methodological acts, it should be understood that the disclosure defined in the appended claims is not necessarily limited to the specific features or acts described above. Rather, the specific features and acts described above are disclosed as example forms of implementing the claims.
[0133] In summary, the embodiments of the present disclosure may provide the following solutions.
[0134] Clause 1. A first user equipment (UE), the first user equipment (UE) comprising:
[0135] a transceiver configured to communicate with a network directly or via another UE; and
[0136] A processor communicatively coupled to the transceiver and configured to execute the packet
[0137] This includes operations for:
[0138] receiving a first message from the network, the first message indicating that the first UE is switched to communicate with the network via a second UE in an idle state or an inactive state;
[0139] obtaining a local identity (ID) of the first UE from the second UE or the network;
[0140] as well as
[0141] Data transmission with the network is performed via the second UE based on the local ID of the first UE.
[0142] Clause 2. The first UE of clause 1, wherein the first message does not indicate the local ID of the first UE, and wherein the operations further comprise:
[0143] establishing a sidelink connection with the second UE; and
[0144] A response to the first message is sent to the network and via the second UE indicating that the handover is complete, wherein the response does not include the local ID in a Sidelink Relay Adaptation Protocol (SRAP) header or does not include the SRAP header.
[0145] Clause 3. The first UE of clause 2, wherein obtaining the local ID of the first UE comprises:
[0146] A second message is received from the network and via the second UE, the second message indicating the local ID of the first UE.
[0147] Clause 4. The first UE of clause 3, wherein performing the data transmission comprises:
[0148] Uplink data multiplexed with a response to the second message is sent to the network and via the second UE.
[0149] Clause 5. The first UE of clause 2, wherein obtaining the local ID of the first UE comprises:
[0150] A third message is received from the second UE and via the sidelink connection, the third message indicating the local ID of the first UE.
[0151] Clause 6. The first UE of clause 5, wherein performing the data transmission comprises:
[0152] Uplink data is sent to the network and via the second UE, the uplink data including the local ID in a SRAP header.
[0153] Clause 7. The first UE of clause 1, wherein the first message further indicates the local ID of the first UE, and wherein obtaining the local ID of the first UE comprises:
[0154] The local ID of the first UE is obtained from the first message.
[0155] Clause 8. The first UE of clause 7, wherein the operations further comprise:
[0156] establishing a sidelink connection with the second UE; and
[0157] A response to the first message is sent to the network and via the second UE indicating that the handover is complete, the response including the local ID in a Sidelink Relay Adaptation Protocol (SRAP) header.
[0158] Clause 9. The first UE of clause 8, wherein performing the data transmission comprises:
[0159] Uplink data multiplexed with the response to the first message is sent to the network and via the second UE.
[0160] Clause 10. The first UE of clause 7, wherein the operations further comprise:
[0161] receiving downlink data from the network via the second UE; and
[0162] According to a Sidelink Relay Adaptation Protocol (SRAP) associated with the downlink data
[0163] A determination that the ID of the first UE in the header is different from the local ID obtained from the first message triggers a Radio Resource Control (RRC) re-establishment procedure.
[0164] Clause 11. A second user equipment (UE), the second user equipment (UE) comprising:
[0165] a transceiver configured to communicate with a network; and
[0166] A processor communicatively coupled to the transceiver and configured to execute the packet
[0167] This includes operations for:
[0168] receiving a response to a first message from a first UE, the first message indicating that the first UE is switched to communicate with the network via the second UE in an idle state or an inactive state, the response indicating that the switching is completed;
[0169] Obtaining a local identity (ID) of the first UE from the first UE or the network;
[0170] as well as
[0171] The response is sent to the network based on the local ID of the first UE.
[0172] Clause 12. The second UE of clause 11, wherein the response does not include the local ID in a Sidelink Relay Adaptation Protocol (SRAP) header or does not include the SRAP header, and wherein obtaining the local ID of the first UE comprises:
[0173] establishing a connection with the network;
[0174] sending a request to the network for obtaining the local ID of the first UE; and
[0175] A fourth message is received from the network, the fourth message indicating the local ID of the first UE.
[0176] Clause 13. The second UE of clause 12, wherein the operations further comprise:
[0177] Sending a third message to the first UE, where the third message indicates the local ID of the first UE;
[0178] receiving uplink data from the first UE, the uplink data including the local ID in a SRAP header; and
[0179] The uplink data is sent to the network.
[0180] Clause 14. The second UE of clause 11, wherein the response includes the local ID in a Sidelink Relay Adaptation Protocol (SRAP) header, and wherein obtaining the local ID of the first UE comprises:
[0181] establishing a connection with the network;
[0182] sending a request to the network for obtaining the local ID of the first UE; and
[0183] A fourth message is received from the network, the fourth message indicating the local ID of the first UE.
[0184] Clause 15. The second UE of clause 14, wherein the operations further comprise:
[0185] receiving, from the first UE, uplink data multiplexed with the response to the first message; and
[0186] Uplink data multiplexed with a response to the fourth message is sent to the network.
[0187] Clause 16. The second UE of clause 11, wherein the response includes the local ID in a Sidelink Relay Adaptation Protocol (SRAP) header, and wherein obtaining the local ID of the first UE comprises:
[0188] The local ID is obtained from the SRAP header.
[0189] Clause 17. The second UE of clause 16, wherein sending the response comprises:
[0190] establishing a connection with the network; and
[0191] The response is sent to the network.
[0192] Clause 18. The second UE of clause 17, wherein the operations further comprise:
[0193] receiving, from the first UE, uplink data multiplexed with the response to the first message; and
[0194] Uplink data multiplexed with the response to the first message is sent to the network.
[0195] Clause 19. A base station, the base station comprising:
[0196] a transceiver configured to communicate with a first user equipment (UE) directly or via another UE; and
[0197] A processor communicatively coupled to the transceiver and configured to execute the packet
[0198] This includes operations for:
[0199] Sending a first message to the first UE, where the first message indicates that the first UE is switched to communicate with the base station via a second UE in an idle state or an inactive state;
[0200] sending a local identity (ID) of the first UE to the first UE; and performing data transmission with the first UE via the second UE based on the local ID of the first UE.
[0201] Clause 20. The base station of clause 19, wherein the first message does not indicate the local ID of the first UE, and wherein sending the local ID of the first UE comprises:
[0202] establishing a connection with the second UE;
[0203] receiving, from the second UE, a request for obtaining the local ID of the first UE;
[0204] Sending a fourth message to the second UE, where the fourth message indicates the local ID of the first UE;
[0205] receiving a response to the fourth message from the second UE indicating that the handover is complete; and
[0206] A second message is sent to the first UE, where the second message indicates the local ID of the first UE.
[0207] Clause 21. The base station of clause 20, wherein performing the data transmission comprises:
[0208] Uplink data multiplexed with a response to the second message is received from the first UE.
[0209] Clause 22. The base station of clause 19, wherein transmitting the local ID of the first UE comprises:
[0210] The local ID of the first UE is sent in the first message.
[0211] Clause 23. The base station of clause 22, wherein the operations further comprise:
[0212] establishing a connection with the second UE;
[0213] receiving, from the second UE, a request for obtaining the local ID of the first UE;
[0214] sending a fourth message to the second UE, the fourth message indicating the local ID of the first UE; and
[0215] A response to the fourth message is received from the second UE indicating that the handover is complete.
[0216] Clause 24. The base station of clause 23, wherein performing the data transmission comprises:
[0217] Uplink data multiplexed with the response to the fourth message is received from the second UE.
[0218] Clause 25. The base station of clause 22, wherein the operations further comprise:
[0219] establishing a connection with the second UE; and
[0220] A response to the first message is received from the second UE indicating that the handover is complete.
[0221] Clause 26. The base station of clause 25, wherein performing the data transmission comprises:
[0222] Uplink data multiplexed with the response to the first message is received from the second UE.
[0223] Clause 27. A method of communication, the method comprising:
[0224] receiving, at a first user equipment (UE) and from a network, a first message indicating that the first UE is switched to communicate with the network via a second UE in an idle state or an inactive state;
[0225] obtaining a local identity (ID) of the first UE from the second UE or the network;
[0226] as well as
[0227] Data transmission with the network is performed via the second UE based on the local ID of the first UE.
[0228] Clause 28. A method as described in clause 27, wherein the first message does not indicate the local ID of the first UE, and wherein the method further comprises:
[0229] establishing a sidelink connection with the second UE; and
[0230] A response to the first message is sent to the network and via the second UE indicating that the handover is complete, wherein the response does not include the local ID in a Sidelink Relay Adaptation Protocol (SRAP) header or does not include the SRAP header.
[0231] Clause 29. The method of clause 28, wherein obtaining the local ID of the first UE comprises:
[0232] A second message is received from the network and via the second UE, the second message indicating the local ID of the first UE.
[0233] Clause 30. The method of clause 29, wherein performing the data transmission comprises:
[0234] Uplink data multiplexed with a response to the second message is sent to the network and via the second UE.
[0235] Clause 31. The method of clause 28, wherein obtaining the local ID of the first UE comprises:
[0236] A third message is received from the second UE and via the sidelink connection, the third message indicating the local ID of the first UE.
[0237] Clause 32. The method of clause 31, wherein performing the data transmission comprises:
[0238] Uplink data is sent to the network and via the second UE, the uplink data including the local ID in a SRAP header.
[0239] Clause 33. The method of clause 27, wherein the first message further indicates the local ID of the first UE, and wherein obtaining the local ID of the first UE comprises:
[0240] The local ID of the first UE is obtained from the first message.
[0241] Clause 34. The method according to clause 33, further comprising:
[0242] establishing a sidelink connection with the second UE; and
[0243] A response to the first message is sent to the network and via the second UE indicating that the handover is complete, the response including the local ID in a Sidelink Relay Adaptation Protocol (SRAP) header.
[0244] Clause 35. The method of clause 34, wherein performing the data transmission comprises:
[0245] Uplink data multiplexed with the response to the first message is sent to the network and via the second UE.
[0246] Clause 36. The method according to clause 33, further comprising:
[0247] receiving downlink data from the network via the second UE; and
[0248] According to a Sidelink Relay Adaptation Protocol (SRAP) associated with the downlink data
[0249] A determination that the ID of the first UE in the header is different from the local ID obtained from the first message triggers a Radio Resource Control (RRC) re-establishment procedure.
[0250] Clause 37. A method of communication, the method comprising:
[0251] receiving, at a second user equipment (UE) and from a first UE, a response to a first message indicating that the first UE is switched to communicate with a network via the second UE in an idle state or an inactive state, the response indicating that the switch is complete;
[0252] Obtaining a local identity (ID) of the first UE from the first UE or the network;
[0253] as well as
[0254] The response is sent to the network based on the local ID of the first UE.
[0255] Clause 38. A method as described in clause 37, wherein the response does not include the local ID in a Sidelink Relay Adaptation Protocol (SRAP) header or does not include the SRAP header, and wherein obtaining the local ID of the first UE comprises:
[0256] establishing a connection with the network;
[0257] sending a request to the network for obtaining the local ID of the first UE; and
[0258] A fourth message is received from the network, the fourth message indicating the local ID of the first UE.
[0259] Clause 39. The method according to clause 38, further comprising:
[0260] Sending a third message to the first UE, where the third message indicates the local ID of the first UE;
[0261] receiving uplink data from the first UE, the uplink data including the local ID in a SRAP header; and
[0262] The uplink data is sent to the network.
[0263] Clause 40. The method of clause 37, wherein the response includes the local ID in a Sidelink Relay Adaptation Protocol (SRAP) header, and wherein obtaining the local ID of the first UE comprises:
[0264] establishing a connection with the network;
[0265] sending a request to the network for obtaining the local ID of the first UE; and
[0266] A fourth message is received from the network, the fourth message indicating the local ID of the first UE.
[0267] Clause 41. The method according to clause 40, further comprising:
[0268] receiving, from the first UE, uplink data multiplexed with the response to the first message; and
[0269] Uplink data multiplexed with a response to the fourth message is sent to the network.
[0270] Clause 42. The method of clause 37, wherein the response includes the local ID in a Sidelink Relay Adaptation Protocol (SRAP) header, and wherein obtaining the local ID of the first UE comprises:
[0271] The local ID is obtained from the SRAP header.
[0272] Clause 43. The method of clause 42, wherein sending the response comprises:
[0273] establishing a connection with the network; and
[0274] The response is sent to the network.
[0275] Clause 44. The method according to clause 43, further comprising:
[0276] receiving, from the first UE, uplink data multiplexed with the response to the first message; and
[0277] Uplink data multiplexed with the response to the first message is sent to the network.
[0278] Clause 45. A method of communication, the method comprising:
[0279] Sending, at a base station and to a first user equipment (UE), a first message indicating that the first UE is switched to communicate with the base station via a second UE in an idle state or an inactive state;
[0280] sending a local identity (ID) of the first UE to the first UE; and
[0281] Data transmission with the first UE is performed via the second UE based on the local ID of the first UE.
[0282] Clause 46. The method of clause 45, wherein the first message does not indicate the local ID of the first UE, and wherein sending the local ID of the first UE comprises:
[0283] establishing a connection with the second UE;
[0284] receiving, from the second UE, a request for obtaining the local ID of the first UE;
[0285] Sending a fourth message to the second UE, where the fourth message indicates the local ID of the first UE;
[0286] receiving a response to the fourth message from the second UE indicating that the handover is complete; and
[0287] A second message is sent to the first UE, where the second message indicates the local ID of the first UE.
[0288] Clause 47. The method of clause 46, wherein performing the data transmission comprises:
[0289] Uplink data multiplexed with a response to the second message is received from the first UE.
[0290] Clause 48. The method of clause 45, wherein sending the local ID of the first UE comprises:
[0291] The local ID of the first UE is sent in the first message.
[0292] Clause 49. The method according to clause 48, further comprising:
[0293] establishing a connection with the second UE;
[0294] receiving, from the second UE, a request for obtaining the local ID of the first UE;
[0295] sending a fourth message to the second UE, the fourth message indicating the local ID of the first UE; and
[0296] A response to the fourth message is received from the second UE indicating that the handover is complete.
[0297] Clause 50. The method of clause 49, wherein performing the data transmission comprises:
[0298] Uplink data multiplexed with the response to the fourth message is received from the second UE.
[0299] Clause 51. The method according to clause 48, further comprising:
[0300] establishing a connection with the second UE; and
[0301] A response to the first message is received from the second UE indicating that the handover is complete.
[0302] Clause 52. The method of clause 51, wherein performing the data transmission comprises:
[0303] Uplink data multiplexed with the response to the first message is received from the second UE.
[0304] Clause 53. A computer-readable medium comprising program instructions for causing an apparatus to perform a method according to any of clauses 27 to 36 or any of clauses 37 to 44 or any of clauses 45 to 52.
Claims
1. A first user equipment (UE), the first user equipment (UE) comprising: a transceiver configured to communicate with a network directly or via another UE; and a processor communicatively coupled to the transceiver and configured to perform operations including: receiving a first message from the network, the first message indicating that the first UE is switched to communicate with the network via a second UE in an idle state or an inactive state; obtaining a local identity (ID) of the first UE from the second UE or the network; and Data transmission with the network is performed via the second UE based on the local ID of the first UE.
2. The first UE of claim 1, wherein the first message does not indicate the local ID of the first UE, and wherein the operations further comprise: establishing a sidelink connection with the second UE; as well as A response to the first message is sent to the network and via the second UE indicating that the handover is complete, wherein the response does not include the local ID in a Sidelink Relay Adaptation Protocol (SRAP) header or does not include the SRAP header.
3. The first UE according to claim 2, wherein obtaining the local ID of the first UE comprises: A second message is received from the network and via the second UE, the second message indicating the local ID of the first UE.
4. The first UE according to claim 3, wherein performing the data transmission comprises: Uplink data multiplexed with a response to the second message is sent to the network and via the second UE.
5. The first UE according to claim 2, wherein obtaining the local ID of the first UE comprises: A third message is received from the second UE and via the sidelink connection, the third message indicating the local ID of the first UE.
6. The first UE according to claim 5, wherein performing the data transmission comprises: Uplink data is sent to the network and via the second UE, the uplink data including the local ID in a SRAP header.
7. The first UE of claim 1, wherein the first message further indicates the local ID of the first UE, and wherein obtaining the local ID of the first UE comprises: The local ID of the first UE is obtained from the first message.
8. The first UE according to claim 7, wherein the operations further comprise: establishing a sidelink connection with the second UE; as well as A response to the first message is sent to the network and via the second UE indicating that the handover is complete, the response including the local ID in a Sidelink Relay Adaptation Protocol (SRAP) header.
9. The first UE according to claim 8, wherein performing the data transmission comprises: Uplink data multiplexed with the response to the first message is sent to the network and via the second UE.
10. The first UE according to claim 7, wherein the operations further comprise: receiving downlink data from the network via the second UE; as well as A Radio Resource Control (RRC) re-establishment procedure is triggered based on a determination that an ID of the first UE in a Sidelink Relay Adaptation Protocol (SRAP) header associated with the downlink data is different from the local ID obtained from the first message.
11. A second user equipment (UE), the second user equipment (UE) comprising: a transceiver configured to communicate with a network; as well as a processor communicatively coupled to the transceiver and configured to perform operations including: receiving a response to a first message from a first UE, the first message indicating that the first UE is switched to communicate with the network via the second UE in an idle state or an inactive state, the response indicating that the switching is completed; obtaining a local identity (ID) of the first UE from the first UE or the network; and The response is sent to the network based on the local ID of the first UE.
12. The second UE of claim 11, wherein the response does not include the local ID in a Sidelink Relay Adaptation Protocol (SRAP) header or does not include the SRAP header, and wherein obtaining the local ID of the first UE comprises: establishing a connection with the network; Sending a request to the network for obtaining the local ID of the first UE; as well as A fourth message is received from the network, the fourth message indicating the local ID of the first UE.
13. The second UE according to claim 12, wherein the operations further comprise: Sending a third message to the first UE, where the third message indicates the local ID of the first UE; receiving uplink data from the first UE, the uplink data including the local ID in a SRAP header; as well as The uplink data is sent to the network.
14. The second UE of claim 11, wherein the response includes the local ID in a Sidelink Relay Adaptation Protocol (SRAP) header, and wherein obtaining the local ID of the first UE comprises: establishing a connection with the network; Sending a request to the network for obtaining the local ID of the first UE; as well as A fourth message is received from the network, the fourth message indicating the local ID of the first UE.
15. The second UE according to claim 14, wherein the operations further comprise: receiving, from the first UE, uplink data multiplexed with the response to the first message; as well as Uplink data multiplexed with a response to the fourth message is sent to the network.
16. The second UE of claim 11, wherein the response includes the local ID in a Sidelink Relay Adaptation Protocol (SRAP) header, and obtaining the local ID of the first UE comprises: The local ID is obtained from the SRAP header.
17. A base station, comprising: a transceiver configured to communicate with a first user equipment (UE) directly or via another UE; and a processor communicatively coupled to the transceiver and configured to perform operations including: Sending a first message to the first UE, where the first message indicates that the first UE is switched to communicate with the base station via a second UE in an idle state or an inactive state; sending a local identity (ID) of the first UE to the first UE; and Data transmission with the first UE is performed via the second UE based on the local ID of the first UE.
18. The base station of claim 17, wherein the first message does not indicate the local ID of the first UE, and wherein sending the local ID of the first UE comprises: establishing a connection with the second UE; receiving, from the second UE, a request for obtaining the local ID of the first UE; Sending a fourth message to the second UE, where the fourth message indicates the local ID of the first UE; receiving, from the second UE, a response to the fourth message indicating that the handover is complete; as well as A second message is sent to the first UE, where the second message indicates the local ID of the first UE.
19. The base station of claim 18, wherein performing the data transmission comprises: Uplink data multiplexed with a response to the second message is received from the first UE.
20. The base station of claim 17, wherein sending the local ID of the first UE comprises: The local ID of the first UE is sent in the first message.
Citation Information
Cited By
Communication method, communication apparatus, and storage medium
WO2026124002A1
