Method and apparatus for handling sidelink radio bearer (SLRB) mapping configuration release in a wireless communication system
Patent Information
- Application Number
- HK42026118095
- Authority / Receiving Office
- HK · HK
- Patent Type
- Patents
- Current Assignee / Owner
- Priority Date
- 2024-02-19
- Filing Date
- 2026-01-22
- Publication Date
- 2026-09-11
AI Technical Summary
Existing wireless communication systems suffer from inefficiency and inadequate resource management when handling sidelink radio bearer mapping configuration release, especially in 5G New Radio technology, where there is a lack of effective mechanisms for QoS flow mapping and RLC channel management between relay user equipment and remote user equipment.
The relay UE establishes a first PC5 RRC connection with the source remote UE and a second PC5 RRC connection with the target remote UE. It receives the PC5 QoS flow to SLRB mapping configuration index and identifier, transmits the PC5 relay RLC channel configuration, releases unrelated E2E SLRBs in a timely manner, and optimizes the management of SLRB and RLC channels.
It improves the efficiency and flexibility of sidelink radio bearer mapping configuration, optimizes resource utilization, and enhances the communication quality and coverage between relay UEs and remote UEs in 5G New Radio technology.
Smart Images

Figure 00000000_0000_ABST
Abstract
Description
[0001] Cross-references to related applications
[0002] This application claims the benefit of U.S. Provisional Patent Application Serial No. 63 / 555,275, filed February 19, 2024, the entire disclosure of which is incorporated herein by reference in its entirety. Technical Field
[0003] This disclosure generally relates to wireless communication networks, and more specifically, to a method and apparatus for processing the release of sidelink radio bearer (SLRB) mapping configurations in a wireless communication system. Background Technology
[0004] With the rapid growth in demand for transmitting large amounts of data to and from mobile communication devices, traditional mobile voice communication networks have evolved into networks that communicate using Internet Protocol (IP) data packets. This IP data packet communication can provide users of mobile communication devices with IP-bearing voice, multimedia, multicast, and video-on-demand communication services.
[0005] An exemplary network architecture is the Evolved Universal Terrestrial Radio Access Network (E-UTRAN). E-UTRAN systems can provide high data throughput to enable the aforementioned IP-based voice and multimedia services. Currently, the 3GPP standards organization is discussing next-generation (e.g., 5G) New Radio technologies. Therefore, changes to the current core of the 3GPP standards are currently being submitted and considered to facilitate their evolution and completion. Summary of the Invention
[0006] A method and apparatus for a source relay user equipment (UE) are disclosed. In one embodiment, the relay UE establishes a first PC5 Radio Resource Control (RRC) connection with a source remote UE and a second PC5 RRC connection with a target remote UE. The relay UE further receives a PC5 Quality of Service (QoS) flow-to-Sidelink Radio Bearer (SLRB) mapping from the source remote UE, wherein the PC5 QoS flow-to-SLRB mapping includes an end-to-end (E2E) SLRB configuration index and at least one sidelink QoS flow identity (ID). The relay UE also transmits the configuration of a PC5 Relay Radio Link Control (RLC) channel to the target remote UE, wherein the E2E SLRB is associated with the PC5 Relay RLC channel. Furthermore, the relay UE receives first information from the source remote UE indicating the release of the PC5 QoS flow-to-SLRB mapping. Additionally, if no other E2E SLRB is associated with the PC5 relay RLC channel, the relay UE transmits a second message to the target remote UE indicating the release of the PC5 relay RLC channel. Attached Figure Description
[0007] Figure 1 A diagram of a wireless communication system according to an exemplary embodiment is shown.
[0008] Figure 2 This is a block diagram of a transmitter system (also called an access network) and a receiver system (also called a user equipment or UE) according to an exemplary embodiment.
[0009] Figure 3 This is a functional block diagram of a communication system according to an exemplary embodiment.
[0010] Figure 4 This is based on an exemplary embodiment. Figure 3 Functional block diagram of the program code.
[0011] Figure 5 It is a reproduction of Figure 16.12.2.2-1 of 3GPP TS 38.300V18.0.0.
[0012] Figure 6 It is a reproduction of Figure 16.12.2.2-2 from 3GPP TS 38.300V18.0.0.
[0013] Figure 7It is a reproduction of Figure 16.12.7-1 of 3GPP TS 38.300V18.0.0.
[0014] Figure 8 It is 3GPP TS 38.331V18.0.0. Figure 5 Reproduction of .8.9.1.1-1.
[0015] Figure 9 It is 3GPP TS 38.331V18.0.0. Figure 5 Reproduction of .8.9.1.1-2.
[0016] Figure 10 A PC5 RRC connection for inter-UE relay is shown according to an exemplary embodiment.
[0017] Figure 11 An example of processing SLRB mapping configuration release according to an exemplary embodiment is shown.
[0018] Figure 12 This is a flowchart based on an exemplary embodiment. Detailed Implementation
[0019] The exemplary wireless communication systems and apparatus described below employ wireless communication systems that support broadcast services. Wireless communication systems are widely deployed to provide various types of communication, such as voice and data. These systems may be based on code division multiple access (CDMA), time division multiple access (TDMA), orthogonal frequency division multiple access (OFDMA), 3GPP Long Term Evolution (LTE) radio access, 3GPP Long Term Evolution Advanced (LTE-A or LTE-Advanced), 3GPP2 Ultra Mobile Broadband (UMB), WiMax, 3GPP New Radio (NR), or some other modulation techniques.
[0020] Specifically, the exemplary wireless communication systems and apparatus described below can be designed to support one or more standards, such as those provided by the association known as the "Third Generation Partnership Project" (referred to herein as 3GPP), including: TS 38.300V18.0.0, "NR; General Description of NR and NG-RAN; Phase 2 (Revision 18)"; TS 38.331V18.0.0, "NR; Radio Resource Control (RRC) Protocol Specification (Revision 18)"; and RIL H693. The standards and documents listed above are hereby expressly incorporated in their entirety by reference.
[0021] Figure 1 A multiple access wireless communication system according to an embodiment of the present invention is illustrated. Access network 100 (AN) includes multiple antenna groups, one group containing antennas 104 and 106, another group containing antennas 108 and 110, and additional groups containing antennas 112 and 114. Figure 1 In this diagram, only two antennas are shown in each antenna group; however, each antenna group can utilize more or fewer antennas. Access terminal 116 (AT) communicates with antennas 112 and 114, where antennas 112 and 114 transmit information to access terminal 116 via forward link 120 and receive information from access terminal 116 via reverse link 118. Access terminal (AT) 122 communicates with antennas 106 and 108, where antennas 106 and 108 transmit information to access terminal (AT) 122 via forward link 126 and receive information from access terminal (AT) 122 via reverse link 124. In an FDD system, communication links 118, 120, 124, and 126 can communicate using different frequencies. For example, forward link 120 can use a frequency different from that used by reverse link 118.
[0022] Each group of antennas and / or the area in which they are designed to communicate is often referred to as a sector of the access network. In an embodiment, each antenna group is designed to communicate with an access terminal in a sector of the area covered by access network 100.
[0023] In communications via forward links 120 and 126, the transmit antennas of access network 100 can utilize beamforming to improve the signal-to-noise ratio of the forward links for different access terminals 116 and 122. Furthermore, compared to an access network that transmits to all its access terminals via a single antenna, the access network using beamforming to transmit to access terminals randomly distributed throughout its coverage area causes less interference to access terminals in neighboring cells.
[0024] An access network (AN) can be a fixed station or base station used for communication with terminals, and may also be referred to as an access point, Node B, base station, enhanced base station, evolved Node B (eNB), network node, network, or any other term. An access terminal (AT) may also be referred to as user equipment (UE), wireless communication device, terminal, access terminal, or any other term.
[0025] Figure 2 This is a simplified block diagram of an embodiment of the transmitter system 210 (also referred to as the access network) and receiver system 250 (also referred to as the access terminal (AT) or user equipment (UE)) in the MIMO system 200. At the transmitter system 210, service data for multiple data streams is provided from the data source 212 to the transport (TX) data processor 214.
[0026] In one embodiment, each data stream is transmitted via a corresponding transmit antenna. The TX data processor 214 formats, decodes, and interleaves the service data of the data streams based on a specific decoding scheme selected for each data stream to provide decoded data.
[0027] OFDM technology can be used to multiplex the decoded data and pilot data of each data stream. The pilot data is typically a known data pattern processed in a known manner and can be used at the receiver system to estimate the channel response. The multiplexed pilot and decoded data for said data streams are then modulated (i.e., symbol mapped) based on a specific modulation scheme (e.g., BPSK, QPSK, M-PSK, or M-QAM) selected for each data stream to provide modulated symbols. The data rate, decoding, and modulation for each data stream can be determined by instructions executed by processor 230.
[0028] The modulation symbols of all data streams are then provided to the TX MIMO processor 220, which can further process the modulation symbols (e.g., for OFDM). The TX MIMO processor 220 then... T A modulation symbol stream is provided to N T Transmitters (TMTRs) 222a to 222t. In some embodiments, the TX MIMO processor 220 applies beamforming weights to symbols of the data stream and the antennas transmitting said symbols therefrom.
[0029] Each transmitter 222 receives and processes a corresponding symbol stream to provide one or more analog signals, and further modulates (e.g., amplifies, filters, and up-converts) the analog signals to provide modulated signals suitable for transmission via the MIMO channel. Then, from N... T Antennas 224a to 224t transmit N from transmitters 222a to 222t. TA modulated signal.
[0030] At receiver system 250, by N R Each antenna 252a to 252r receives the transmitted modulated signal and provides the signal received from each antenna 252 to a corresponding receiver (RCVR) 254a to 254r. Each receiver 254 modulates (e.g., filters, amplifies, and downconverts) the corresponding received signal, digitizes the modulated signal to provide a sample, and further processes the sample to provide a corresponding "received" symbol stream.
[0031] The RX data processor 260 then uses specific receiver processing technology from N R 254 receivers receive and process N R Each received symbol stream provides N T Each detected symbol stream is then demodulated, deinterleaved, and decoded by the RX data processor 260 to recover the service data used for the data stream. The processing performed by the RX data processor 260 is complementary to the processing performed by the TX MIMO processor 220 and TX data processor 214 at the transmitter system 210.
[0032] Processor 270 periodically determines which pre-decoding matrix to use (discussed below). Processor 270 formulates a reverse link message including the matrix index part and the rank part.
[0033] The reverse link message may include various types of information relating to the communication link and / or the received data stream. The reverse link message is then processed by the TX data processor 238, modulated by the modulator 280, regulated by the transmitters 254a to 254r, and transmitted back to the transmitter system 210, which also receives service data from multiple data streams from the data source 236.
[0034] At transmitter system 210, the modulated signal from receiver system 250 is received by antenna 224, conditioned by receiver 222, demodulated by demodulator 240, and processed by RX data processor 242 to extract the reverse link message transmitted by receiver system 250. Processor 230 then determines which pre-decoding matrix to use to determine beamforming weights and then processes the extracted message.
[0035] Turning Figure 3 This figure illustrates an alternative simplified functional block diagram of a communication device according to an embodiment of the present invention. Figure 3 As shown, this can be achieved using the communication device 300 in a wireless communication system. Figure 1 UE (or AT) 116 and 122 or Figure 1The communication device 300 is a base station (or AN) 100, and the wireless communication system is preferably an NR system. The communication device 300 may include an input device 302, an output device 304, a control circuit 306, a central processing unit (CPU) 308, a memory 310, program code 312, and a transceiver 314. The control circuit 306 executes the program code 312 in the memory 310 via the CPU 308, thereby controlling the operation of the communication device 300. The communication device 300 can receive signals input by a user via the input device 302 (e.g., a keyboard or keypad) and can output images and sounds via the output device 304 (e.g., a monitor or speaker). The transceiver 314 is used to receive and transmit wireless signals, pass the received signals to the control circuit 306, and wirelessly output signals generated by the control circuit 306. Alternatively, the communication device 300 in a wireless communication system can also be used. Figure 1 AN 100 in the middle.
[0036] Figure 4 This is according to an embodiment of the present invention. Figure 3 The diagram shows a simplified block diagram of program code 312. In this embodiment, program code 312 includes an application layer 400, a layer 3 portion 402, and a layer 2 portion 404, and is coupled to a layer 1 portion 406. Layer 3 portion 402 generally performs radio resource control. Layer 2 portion 404 typically performs link control. Layer 1 portion 406 typically performs physical connections.
[0037] Version 18 of the 3GPP Phase 2 specification (TS 38.300) specifies Layer 2 U2U relay as follows:
[0038] 16.12 Side Link Relay
[0039] 16.12.1 Overview
[0040] Sidelink relay is introduced to support 5G ProSe UE-to-Network Relay (U2N Relay) functionality (specified in TS23.304
[48] ) to provide network connectivity for U2N remote UEs. Both L2 and L3 U2N relay architectures are supported. The L3 U2N relay architecture is transparent to the NG-RAN serving U2N relay UEs, the difference being the control of sidelink resources. Detailed architecture and procedures for L3 U2N relay can be found in TS23.304
[48] .
[0041] U2N relay UEs will be in RRC_CONNECTED state to perform relay of unicast data.
[0042] For L2 U2N trunk operations, the following RRC state combinations are supported:
[0043] Both the L2 U2N relay UE and the L2 U2N remote UE should be in RRC_CONNECTED state to perform the transmission / reception of unicast data via relay; and
[0044] - An L2 U2N relay UE can be in RRC_IDLE, RRC_INACTIVE, or RRC_CONNECTED state, as long as all L2 U2N remote UEs connected to the L2 U2N relay UE are in RRC_INACTIVE or RRC_IDLE state.
[0045] A single unicast link is established between an L2 U2N relay UE and an L2 U2N remote UE. NG-RAN services from a given L2U2N relay UE to an L2 U2N remote UE and services of the L2U2N relay UE should be separated in different Uu RLC channels.
[0046] For L2 U2N relay, L2 U2N remote UEs can be configured to use resource allocation mode 2 (as specified in 5.7.2 and 16.9.3.1) only for relay data.
[0047] Sidelink relay is introduced to support 5G ProSe UE-to-UE (U2U) relay functionality (specified in TS 23.304
[48] ), thereby providing connectivity between U2U remote UEs. Both L2 and L3 U2U relay architectures are supported. The L3 U2U relay architecture is transparent to the AS layer of the U2U relay UE. Detailed architecture and procedures for L3 U2U relay can be found in TS23.304
[48] .
[0048] U2U relay UEs will support U2U relay functionality as specified in TS23.304
[48] to provide coverage extension for sidelink transmission between two U2U remote UEs. With coverage extension, a U2U remote UE can communicate with a peer U2U remote UE that is not reachable within the sidelink coverage area.
[0049] U2U relay UEs and U2U remote UEs can be in any RRC state. U2U relay UEs and U2U remote UEs can be within or outside the coverage area of different cells. U2U relay UEs and U2U remote UEs support two sidelink resource allocation modes (i.e., Mode 1 and Mode 2). For U2U relay, NR sidelinks are supported between the U2U relay UE and the U2U remote UE. After the NR sidelink is established between the U2U relay UE and the U2U remote UE, an end-to-end PC5 unicast link connection is established between the U2U remote UEs. Only unicast is supported between the U2U relay UE and the U2U remote UE.
[0050] [...]
[0051] 16.12.2.2L2 UE Inter-Relay
[0052] The protocol stacks for the user plane and control plane of the L2 U2U trunk architecture are shown in Figures 16.12.2.2-1 and 16.12.2.2-2. The SRAP sublayer is disposed on the two PC5 interfaces above the RLC sublayer used for both CP and UP. Sidelink SDAP, PDCP, and RRC terminate between the two L2 U2U remote UEs (i.e., end-to-end), while SRAP, RLC, MAC, and PHY terminate at each hop of the PC5 link.
[0053] 3GPP TS 38.300, titled "User Plane Protocol Stack for L2 Inter-UE Relay"
[0054] Figure 16.12.2.2-1 of V18.0.0 is reproduced as follows Figure 5 ]
[0055] [3GPP TS 38.300, titled "Control Plane Protocol Stack for L2 Inter-UE Relay"]
[0056] Figure 16.12.2.2-2 of V18.0.0 is reproduced as follows Figure 6 ]
[0057] For L2 UE-to-UE relay, the SRAP sublayer at the L2 U2U remote UE:
[0058] - The SRAP sublayer at the L2 U2U remote UE performs bearer mapping between the end-to-end PC5 radio bearers (SL-SRB or SL-DRB) of the L2 U2U remote UE at each hop of the PC5 relay RLC channel between the L2 U2U remote UE and the L2 U2U relay UE.
[0059] - For services transmitted from an L2 U2U remote UE to an L2 U2U relay UE, different end-to-end PC5 radio bearers (SL-SRB or SL-DRB) destined for the same peer L2 U2U remote UE and / or different peer L2 U2U remote UEs can be multiplexed into the same PC5 relay RLC channel, which is located between the L2 U2U remote UE and the L2 U2U relay UE.
[0060] - For services received at an L2 U2U remote UE, the same PC5 trunk RLC channel from an L2 U2U trunk UE can be demultiplexed to different end-to-end PC5 radio bearers (SL-SRB or SL-DRB) of the same peer L2 U2U remote UE and / or different peer L2 U2U remote UEs.
[0061] The SRAP sublayer at the L2 U2U remote UE supports identification of both the peer L2 U2U remote UE and itself. A local ID is assigned by the L2U2U relay UE to both L2 U2U remote UEs for identification. Of the two local IDs, one identifies the L2 U2U remote UE and the other identifies the peer L2 U2U remote UE. The peer L2 U2U remote UE's local ID and the L2U2U remote UE's local ID, along with the corresponding L2 ID of the peer L2 U2U remote UE, are delivered by the L2 U2U relay UE to the L2 U2U remote UE. Identification information for the end-to-end PC5 radio bearer and the two local IDs are included in the SRAP header so that received packets used by the peer L2U2U remote UE for a specific PDCP entity are associated with the correct end-to-end PC5 radio bearer of the L2 U2U remote UE.
[0062] For L2 UE-to-UE relay, the SRAP sublayer at the L2 U2U relay UE:
[0063] - The SRAP sublayer at the L2 U2U relay UE determines the egress PC5 relay RLC channel based on the mapping of the end-to-end PC5 radio bearers and egress PC5 relay RLC channels of a specific pair between the L2 U2U remote UE and its peer L2U2U remote UE.
[0064] - For inbound traffic received from one or more L2 U2U remote UEs at an L2 U2U relay UE, different end-to-end PC5 radio bearers (SL-SRB or SL-DRB) of the same L2 U2U remote UE and / or the same / different end-to-end PC5 radio bearers (SL-SRB or SL-DRB) of the L2 U2U remote UE can be multiplexed to the same outgoing PC5 relay RLC channel, which is located between the L2 U2U relay UE and the peer L2 U2U remote UE.
[0065] [...]
[0066] 16.12.7 Control plane program for L2 U2U relay
[0067] L2 U2U remote UEs need to establish an end-to-end SL-SRB / DRB with their peer L2 U2U remote UEs before transmitting user plane data.
[0068] The following advanced connection establishment procedure in Figure 16.12.7-1 applies to L2 U2U relay UEs and L2U2U remote UEs:
[0069] [3GPP TS 38.300, titled "Procedure for L2 U2U Remote UE Connection Establishment"]
[0070] Figure 16.12.7-1 of V18.0.0 is reproduced as follows Figure 7 ]
[0071] 1. L2 U2U remote UEs, L2 U2U relay UEs and peer L2 U2U remote UEs execute discovery procedures or integrated discovery procedures.
[0072] 2a. L2 U2U remote UE establishes / modifies PC5-RRC connection with the selected L2 U2U relay UE (i.e., as specified in TS23.304
[48] ).
[0073] 2b. L2 U2U relay UE establishes / modifies PC5-RRC connection with peer L2 U2U remote UE (i.e., as specified in TS23.304
[48] ).
[0074] 3. The L2 U2U relay UE is assigned two local IDs, which are delivered to each of the L2 U2U remote UEs via an RRCReconfigurationSidelink message: one local ID is used to identify the L2 U2U remote UE, and the other local ID is used to identify the peer L2U2U remote UE. When delivering the local IDs, the L2 ID of the peer L2U2U remote UE is also delivered to the U2U remote UE for association between the local IDs and the L2 IDs of the peer U2U remote UEs.
[0075] 4. An L2 U2U remote UE establishes an end-to-end PC5-RRC connection with its peer L2 U2U remote UE via an L2 U2U relay UE. For end-to-end connection establishment, fixed indices (i.e., 0 / 1 / 2 / 3) are defined for end-to-end SL-SRB 0 / 1 / 2 / 3, and a specified PC5 relay RLC channel is configured on each hop. Sidelink UE capabilities are exchanged between L2 U2U remote UEs via PC5-RRC (e.g., SL-SRB3) messages.
[0076] 5. The L2 U2U remote UE sends the set of all QoS attributes for the end-to-end QoS flow to the L2 U2U relay UE via PC5-RRC.
[0077] 6. L2 U2U relay UEs only perform QoS splitting for PDBs.
[0078] Note: The method of splitting the PDB depends on the L2 U2U relay UE implementation plan.
[0079] 7. The L2 U2U relay UE sends the split QoS value (i.e., PDB) to the L2 U2U remote UE via PC5-RRC message.
[0080] 8. The serving gNB of an L2 U2U remote UE exports the PDCP and SDAP configurations for the end-to-end SL-DRB, and uses the end-to-end RRCReconfigurationSidelink message to provide the peer L2 U2U remote UE with a portion of the reception-related configuration. The end-to-end bearer ID for SL-SRB and SL-DRB is used as input for L2 U2U relay encryption and decryption at PDCP.
[0081] 9a. The serving gNB of the L2 U2U remote UE or the L2 U2U remote UE exports the first-hop configuration for the SL-DRB (e.g., PC5 trunk RLC channel configuration) and provides the configuration related to the Rx received on the first hop (i.e., by the trunk UE) to the L2 U2U trunk UE using the per-hop RRCReconfigurationSidelink message.
[0082] 9b. The serving gNB of the L2 U2U relay UE or the L2 U2U relay UE exports the second-hop configuration (e.g., PC5 relay RLC channel configuration) for each SL-DRB, and provides the configuration related to the reception on the second hop (i.e., RX performed by the peer remote UE) to the peer L2 U2U remote UE using the per-hop RRCReconfigurationSidelink message.
[0083] 10. L2 U2U remote UEs and peer L2 U2U remote UEs transmit or receive data via L2 U2U relay UEs.
[0084] The 3GPP Radio Resource Control (RRC) specification (TS 38.331) for version 18 specifies the following for sidelink RRC reconfiguration procedures, sidelink radio bearer management, and PC5 relay radio link control (RLC) channel management:
[0085] 5.8.9.1 Sidelink RRC Reconfiguration
[0086] 5.8.9.1.1 Overview
[0087] [Image from 3GPP TS 38.331V18.0.0 with the title "Side link RRC reconfiguration successful"]
[0088] 5.8.9.1.1-1 reproduced as Figure 8 ]
[0089] [Image from 3GPP TS 38.331V18.0.0 titled "Side link RRC reconfiguration failed"]
[0090] 5.8.9.1.1-2 reproduced as Figure 9 ]
[0091] The purpose of this procedure is to modify PC5-RRC connections, such as establishing / modifying / releasing sidelink DRBs or additional sidelink RLC bearers or PC5 relay RLC channels, adding / modifying / releasing sidelink carriers, (re)configuring NR sidelink measurements and reports, (re)configuring sidelink CSI reference signal resources, (re)configuring CSI report delay limits, (re)configuring sidelink DRX, (re)configuring SL inter-UE coordination report delay limits, and indicating SFN-DFN offset.
[0092] In the following situations, the UE may initiate a sidelink RRC reconfiguration procedure and perform the operations in clause 5.8.9.1.2 on the corresponding PC5-RRC connection:
[0093] - In the case of L2 U2U relay operation, release of the sidelink DRB associated with the peer UE or L2 U2U relay UE and peer L2 U2U remote UE, as specified in Clause 5.8.9.1a.1;
[0094] - In the case of L2 U2U relay operation, the establishment of the sidelink DRB associated with the peer UE or L2 U2U relay UE and peer L2 U2U remote UE, as specified in Clause 5.8.9.1a.2;
[0095] - Modify the parameters included in the SLRB-Config of the sidelink DRB associated with the peer UE, as specified in Clause 5.8.9.1a.2;
[0096] - Release of additional sidelink RLC bearers associated with the peer UE, as specified in Clause 5.8.9.1a.5;
[0097] - The establishment of additional sidelink RLC bearers associated with the peer UE, as specified in Clause 5.8.9.1a.6;
[0098] - Modify the parameters included in the SL-RLC-BearerConfig of the additional sidelink RLC bearer associated with the peer UE, as specified in Clause 5.8.9.1a.6;
[0099] - Release of PC5 trunk RLC channels for L2 U2N / U2U trunk UEs and remote UEs, as specified in Clause 5.8.9.7.1;
[0100] - Establishment of PC5 trunk RLC channels for L2 U2N / U2U trunk UEs and remote UEs, as specified in Clause 5.8.9.7.2;
[0101] - Modifications to the parameters included in SL-RLC-ChannelConfigPC5 for PC5 trunk RLC channels used for L2 U2N / U2U trunk UEs and remote UEs, as specified in Clause 5.8.9.7.2;
[0102] - Release of sidelink carriers associated with the peer UE, as specified in Clause 5.8.9.1b.1;
[0103] - The addition of sidelink carriers associated with the peer UE, as specified in Clause 5.8.9.1b.2;
[0104] - Modifications to the sidelink carriers associated with the peer UE, as specified in Clause 5.8.9.1b.2;
[0105] - (Reconfiguration of peer UEs used to perform NR sidelink measurements and reporting)
[0106] - Reconfiguration of side-link CSI reference signal resources and CSI report delay limits;
[0107] - Used for (re)configuration of peer UEs to perform sidelink DRX;
[0108] - SL (Inter-UE Coordination Reporting) Delay Limits (Re)configuration;
[0109] - Reconfiguration of the local UE ID of an L2 U2U remote UE performed by an L2 U2U relay UE.
[0110] - A response to a request for an SFN-DFN offset from an L2 U2N remote UE in a RemoteUEInformationSidelink message;
[0111] - The change in the SFN-DFN offset value at the L2 U2N relay UE.
[0112] Note: The determination of when the SFN-DFN offset value has changed to the point where an update needs to be sent to the L2 U2N remote UE depends on the L2 U2N relay UE implementation scheme.
[0113] In RRC_CONNECTED, the UE applies the NR sidelink communication parameters provided in RRCReconfiguration (if present). In RRC_IDLE or RRC_INACTIVE, the UE applies the NR sidelink communication parameters provided in the system information (if present). For other cases, the UE applies the NR sidelink communication parameters provided in SidelinkPreconfigNR (if present). When the UE performs a state transition between these three cases, after obtaining the new configuration, the UE applies the NR sidelink communication parameters provided in the new state. Before obtaining the new configuration, the UE continues to apply the NR sidelink communication parameters provided in the old state.
[0114] 5.8.9.1.2 Actions related to the transmission of SidelinkUEInformation messages
[0115] The UE should configure the contents of the RRCReconfigurationSidelink message as follows:
[0116] 1> For each side link DRB to be released, according to clause 5.8.9.1a.1.1, due to the configuration of sl-ConfigDedicated NR, SIB12, SidelinkPreconfigNR, or the upper layer:
[0117] 2> Configure the entries included in slrb-ConfigToReleaseList corresponding to the sidelink DRB;
[0118] 1> For each side link DRB to be established or modified, according to clause 5.8.9.1a.2.1, due to the receipt of sl-ConfigDedicatedNR, SIB12, or SidelinkPreconfigNR:
[0119] 2> If the sidelink DRB is a per-hop sidelink DRB (i.e., the UE does not act as an L2 U2U remote UE):
[0120] 3> To establish a sidelink DRB:
[0121] 4> Assign the new logical channel identifier to the logical channel associated with the side link DRB and set sl-MAC-LogicalChannelConfigPC5 in SLRB-Config to include the new logical channel identifier;
[0122] 3> Based on the received sl-RadioBearerConfig and the sl-RLC-BearerConfig corresponding to the side link DRB, set the SLRB-Config contained in slrb-ConfigToAddModList;
[0123] 2> Otherwise, if the sidelink DRB is an end-to-end sidelink DRB (i.e., the UE acts as an L2U2U remote UE and configures the peering L2 U2U remote UE with end-to-end SDAP and PDCP, or provides QoS flows and end-to-end DRB mappings to L2 relay UEs):
[0124] 3> If the UE is in RRC_CONNECTED:
[0125] 4> Based on the received sl- in sl-ConfigDedicatedNR
[0126] RadioBearerConfig sets the SLRB-Config contained in slrb-ConfigToAddModList;
[0127] 3> Otherwise, if the UE is in RRC_IDLE / RRC_INACTIVE:
[0128] 4> Based on sl-RadioBearerConfig in SIB12, configure the SLRB- (as defined in slrb-ConfigToAddModList) exported via the end-to-end QoS attribute set.
[0129] Config;
[0130] 3> If the UE is outside the coverage area:
[0131] 4> Based on sl-RadioBearerConfig in SidelinkPreconfigNR, configure the QoS attribute set exported from the end-to-end QoS attribute set and included in slrb-
[0132] SLRB-Config in ConfigToAddModList;
[0133] 1> For each additional sidelink RLC bearer to be released, in accordance with clause 5.8.9.1a.5.1, due to the configuration of sl-ConfigDedicatedNR, SIB12, SidelinkPreconfigNR, or the upper layer:
[0134] 2> Configure the entries included in the sl-RLC-BearerToReleaseList corresponding to the additional sidelink RLC bearers;
[0135] 1> For each additional sidelink RLC bearer to be established or modified, in accordance with clause 5.8.9.1a.6.1, due to the receipt of sl-ConfigDedicatedNR, SIB12, or SidelinkPreconfigNR:
[0136] 2> If an additional sidelink RLC bearer will be established:
[0137] 3> Assign the new logical channel identifier of the logical channel to be associated with the sidelink DRB and set the sl-MAC- in SL-RLC-BearerConfig.
[0138] LogicalChannelConfigPC5 is set to include the new logical channel identifier;
[0139] 2> Based on the received sl-RadioBearerConfig and the sl-RLC-BearerConfig corresponding to the additional side link RLC bearer, set the SL-RLC-Bearer Config contained in sl-RLC-BearerToAddModList;
[0140] 1> Set the entries contained in sl-CarrierToReleaseList corresponding to the sidelink carrier, where the MAC entity indicates that the maximum number of consecutive HARQ DTX for a specific destination has been reached;
[0141] 1> At least consider the carriers mapped to the sidelink QoS flow configured by the upper layer, the carriers configured in sl-ConfigDedicatedNR, SIB12 or SidelinkPreconfigNR, and the carriers supported by the two UEs, and set the entries contained in sl-CarrierToAddModList corresponding to the sidelink carriers.
[0142] 1> Configure sl-MeasConfig as follows:
[0143] 2> If the frequency used for NR side link communication is included in sl-ConfigDedicatedNR within the RRCReconfiguration message, then sl-FreqInfoToAddModList / sl-
[0144] In FreqInfoToAddModListExt or in sl-ConfigCommonNR contained in SIB12:
[0145] 3> If the UE is in RRC_CONNECTED:
[0146] 4> Configure sl-MeasConfig based on the NR sidelink measurement configuration information stored for this destination;
[0147] 3> If the UE is in RRC_IDLE or RRC_INACTIVE:
[0148] 4> Based on the stored NR-side link measurement configuration received from SIB12, set sl-MeasConfig;
[0149] 2> Otherwise:
[0150] 3> Configure sl- according to sl-MeasPreconfig in SidelinkPreconfigNR.
[0151] MeasConfig;
[0152] 1> Configure sl-LatencyBoundIUC-Report;
[0153] 1> Start timer T400 for the destination;
[0154] 1> Configure sl-CSI-RS-Config;
[0155] 1> Configure sl-LatencyBoundCSI-Report;
[0156] 1> Configure sl-ResetConfig;
[0157] Note 1: Whether / how to set the parameters included in sl-LatencyBoundIUC-Report, sl-CSI-RS-Config, sl-LatencyBoundCSI-Report, and sl-ResetConfig depends on the UE implementation scheme.
[0158] 1> Configure sl-DRX-ConfigUC-PC5 as follows:
[0159] 2> If the frequency used for NR side link communication is included in sl-ConfigDedicatedNR within the RRCReconfiguration message, then sl-FreqInfoToAddModList / sl-
[0160] In FreqInfoToAddModListExt or in sl-ConfigCommonNR contained in SIB12:
[0161] 3> If the UE is in RRC_CONNECTED, and if sl-
[0162] ScheduledConfig is included in RRCReconfiguration's sl-
[0163] In ConfigDedicatedNR, then:
[0164] 4> Set sl-DRX-ConfigUC-PC5 according to the NR sidelink DRX configuration information stored for this destination;
[0165] Note 2: If the UE is in RRC_IDLE, RRC_INACTIVE, or out of coverage, or in RRC_CONNECTED, and sl-UE-SelectedConfig is included in sl-ConfigDedicatedNR within RRCReconfiguration, then sl-DRX-ConfigUC-PC5 is set depending on the UE implementation scheme.
[0166] 1> For each PC5 trunk RLC channel that will be released due to the configuration of sl-ConfigDedicatedNR:
[0167] 2> Set the SL-RLC-ChannelID corresponding to the PC5 relay RLC channel in sl-RLC-ChannelToReleaseListPC5;
[0168] 1> For each PC5 trunk RLC channel that will be established or modified due to the receipt of sl-ConfigDedicatedNR:
[0169] 2> To establish a PC5 relay RLC channel, then:
[0170] 3> Assign the new logical channel identifier of the logical channel to be associated with the PC5 relay RLC channel and set the sl-MAC- in SL-RLC-ChannelConfigPC5 to be...
[0171] LogicalChannelConfigPC5 is set to include the new logical channel identifier;
[0172] 2> Based on the received SL-RLC- corresponding to the PC5 relay RLC channel
[0173] ChannelConfig is used to set SL-RLC-ChannelConfigPC5 contained in sl-RLC-ChannelToAddModListPC5, which includes setting sl-RLC-ChannelID-PC5 to the same value of sl-RLC-ChannelID received in SL-RLC-ChannelConfig;
[0174] 1> If the UE acts as an L2 U2N relay UE:
[0175] 2> If the destination UE is an L2 U2N remote UE that requested the SFN-DFN offset in a previous RemoteUEInformationSidelink message:
[0176] 3> If the SFN-DFN offset has changed since the previous transmission of the RRCReconfigurationSidelink message, or if no previous transmission of the RRCReconfigurationSidelink message has occurred since the RemoteUEInformationSidelink message was received:
[0177] 4> Set sl-SFN-DFN-Offset according to the relationship between the SFN and DFN timelines in PCell;
[0178] 1> If the UE acts as an L2 U2U relay UE, and if the initiator configures the local ID as the connected L2 U2U remote UE:
[0179] 2> If you assign or modify local ID pairs for end-to-end PC5 connections, and if you successfully establish a PC5-RRC connection with an L2U2U remote UE and a PC5-RRC connection with a peer L2 U2U remote UE:
[0180] 3> Include the entry in sl-LocalID-PairToAddModList and set the fields as follows:
[0181] 4> As needed, based on the association between user information and L2 ID specified in TS23.304
[65] , set sl-RemoteUE-LocalIdentity to include the new local UE ID, and set sl-RemoteUE-L2Identity to include the source L2 ID of the L2 U2U remote UE in SL-SRAP-ConfigPC5;
[0182] 4> As needed, based on the association between user information and L2 ID specified in TS23.304
[65] , set sl-PeerRemoteUE-LocalIdentity to include the new local UE ID, and set sl-PeerRemoteUE-L2Identity to include the peer L2 ID.
[0183] The destination L2 ID of the U2U remote UE is included in SL-SRAP-ConfigPC5;
[0184] 2> Otherwise, if you want to release the local ID pair for end-to-end PC5 connections:
[0185] 3> Include the entry in sl-LocalID-PairToReleaseList, where SL-
[0186] The Destination Identity value is set to the destination L2 of the peer-to-peer U2U remote UE.
[0187] ID;
[0188] 1> If the UE acts as an L2 U2U remote UE (i.e., Tx UE), and if the initiating procedure configures the first hop PC5 trunk RLC channel of the end-to-end side link DRB as a connected L2 U2N trunk UE (i.e., Rx UE) based on the configuration in SIB12 or SidelinkPreconfigNR; or
[0189] 1> If the UE is acting as an L2 U2U relay UE (i.e., Tx UE) and is in RRC_IDLE, RRC_INACTIVE, or OoC, and if the initiator configures the second-hop PC5 relay RLC channel as a connected L2 U2N remote UE (i.e., Rx UE) based on the configuration in SIB12 or SidelinkPreconfigNR:
[0190] 2> To establish a PC5 relay RLC channel, then:
[0191] 3> Assign a new RLC channel ID, and set sl-RLC-ChannelID-PC5 in SL-RLC-ChannelConfigPC5 to include the new RLC channel ID;
[0192] 3> Assign the new logical channel identifier of the logical channel to be associated with the PC5 relay RLC channel and set the sl-MAC- in SL-RLC-ChannelConfigPC5 to be...
[0193] LogicalChannelConfigPC5 is set to include the new logical channel identifier;
[0194] 3> If the UE is in RRC_IDLE or RRC_INACTIVE:
[0195] 4> Configure the SL-RLC-BearerConfig based on the per-hop QoS derived from the end-to-end SLRB according to SIB12.
[0196] SL-RLC-ChannelConfigPC5 in ChannelToAddModListPC5;
[0197] 3> Otherwise, if the UE is outside the coverage area:
[0198] 4> Configure the SL-RLC-BearerConfig included in SL-RLC- based on the per-hop QoS exported from SLRB according to SidelinkPreconfigNR.
[0199] SL-RLC-ChannelConfigPC5 in ChannelToAddModListPC5;
[0200] Note 3: If the UE is in RRC_IDLE or RRC_INACTIVE or outside coverage, how the per-flow QoS split on the first / second hop is incorporated into the per-SLRB tier QoS derived for RLC channel configuration depends on the UE implementation.
[0201] The UE will submit an RRCReconfigurationSidelink message to the lower layer for transmission.
[0202] 5.8.9.1.3 UE reception of RRCReconfigurationSidelink
[0203] The UE will perform the following actions after receiving the RRCReconfigurationSidelink:
[0204] 1> If RRCReconfigurationSidelink contains sl-ResetConfig:
[0205] 2> Execute the sidelink reset configuration procedure as specified in 5.8.9.1.10;
[0206] 1> If RRCReconfigurationSidelink contains slrb-ConfigToReleaseList:
[0207] 2> For slrb- which is part of the current UE sidelink configuration
[0208] The value of each entry contained in ConfigToReleaseList;
[0209] 3> Perform the sidelink DRB release procedure in accordance with clause 5.8.9.1a.1;
[0210] 1> If RRCReconfigurationSidelink contains slrb-ConfigToAddModList:
[0211] 2> For SLRB- which is not part of the current UE sidelink configuration
[0212] Each slrb-PC5-ConfigIndex value contained in ConfigToAddModList:
[0213] 3> If sl-MappedQoS-FlowsToAddList is included, then:
[0214] 4> Apply the SL-MappedQoS-FlowsToAddList included in the application.
[0215] PQFI;
[0216] 3> Perform the sidelink DRB addition procedure according to clause 5.8.9.1a.2;
[0217] 2> For slrb- which is part of the current UE sidelink configuration
[0218] Each slrb-PC5-ConfigIndex value contained in ConfigToReleaseList:
[0219] 3> If sl-MappedQoS-FlowsToAddList is included, then:
[0220] 4> Add the SL-PQFI included in the sl-MappedQoS-FlowsToAddList to the corresponding sidelink DRB;
[0221] 3> If it contains sl-MappedQoS-FlowsToReleaseList:
[0222] 4> Remove items included in sl-MappedQoS from the corresponding sidelink DRB.
[0223] SL-PQFI in the FlowsToRelease List;
[0224] 3> If the sidelink DRB release condition as described in Clause 5.8.9.1a.1.1 is met:
[0225] 4> Perform the sidelink DRB release procedure in accordance with clause 5.8.9.1a.1.2;
[0226] 3> Otherwise, if the sidelink DRB modification conditions described in Clause 5.8.9.1a.2.1 are met, then:
[0227] 4> Perform the sidelink DRB modification procedure according to clause 5.8.9.1a.2.2;
[0228] 1> If RRCReconfigurationSidelink contains sl-RLC-BearerToReleaseList:
[0229] 2> For sl-RLC- which is part of the current UE sidelink configuration
[0230] The value of each entry contained in BearerToReleaseList;
[0231] 3> Perform the additional sidelink RLC bearer release procedure in accordance with clause 5.8.9.1a.5;
[0232] 1> If RRCReconfigurationSidelink contains sl-RLC-BearerToAddModList:
[0233] 2> For sl-RLC that is not part of the current UE sidelink configuration
[0234] Each SL-RLC-BearerConfigIndex value contained in BearerToAddModList:
[0235] 3> Perform the additional sidelink RLC bearer addition procedure in accordance with Clause 5.8.9.1a.6;
[0236] 2> For sl-RLC as part of the current UE sidelink configuration
[0237] Each SL-RLC-BearerConfigIndex value contained in BearerToAddModList:
[0238] 3> Perform the additional sidelink RLC bearer modification procedure in accordance with clause 5.8.9.1a.6;
[0239] 1> If RRCReconfigurationSidelink contains sl-CarrierToReleaseList:
[0240] 2> For sl- which is part of the current UE sidelink configuration
[0241] The value of each entry contained in CarrierToReleaseList;
[0242] 3> Perform the sidelink carrier release procedure in accordance with Clause 5.8.9.1b.1;
[0243] 1> If RRCReconfigurationSidelink contains sl-CarrierToAddModList:
[0244] 2> For SL- which is not part of the current UE side link configuration
[0245] Each sl-Carrier-Id value contained in CarrierToAddModList:
[0246] 3> Perform the sidelink carrier addition procedure according to clause 5.8.9.1b.2;
[0247] 2> For sl- which is part of the current UE sidelink configuration
[0248] Each sl-Carrier-Id value contained in CarrierToAddModList:
[0249] 3> Perform the carrier modification procedure in accordance with Clause 5.8.9.1b.2;
[0250] 1> If RRCReconfigurationSidelink contains sl-MeasConfig:
[0251] 2> Execute the sidelink measurement configuration procedure as specified in 5.8.10;
[0252] 1> If the RRCReconfigurationSidelink message contains sl-CSI-RS-Config:
[0253] 2> Application-side link CSI-RS configuration;
[0254] 1> If the RRCReconfigurationSidelink message contains sl-LatencyBoundCSI-Report:
[0255] 2> Application configured with sidelink CSI report latency limits;
[0256] 1> If RRCReconfigurationSidelink contains sl-RLC-ChannelToReleaseListPC5:
[0257] 2> For sl-RLC- which is part of the current UE sidelink configuration
[0258] Each SL-RLC-ChannelID value contained in ChannelToReleaseListPC5;
[0259] 3> Perform the PC5 relay RLC channel release procedure in accordance with clause 5.8.9.7.1;
[0260] 1> If RRCReconfigurationSidelink contains sl-RLC-ChannelToAddModListPC5:
[0261] 2> For sl-RLC that is not part of the current UE sidelink configuration
[0262] Each sl-RLC-ChannelID-PC5 value contained in ChannelToAdd ModListPC5:
[0263] 3> Perform the PC5 trunk RLC channel addition procedure according to clause 5.8.9.7.2;
[0264] 2> For sl-RLC- which is part of the current UE sidelink configuration
[0265] Each sl-RLC-ChannelID-PC5 value contained in ChannelToAddModList PC5:
[0266] 3> Perform the PC5 relay RLC channel modification procedure according to clause 5.8.9.7.2;
[0267] 1> If the RRCReconfigurationSidelink message contains sl-DRX-ConfigUC-PC5; and
[0268] 1> If the UE accepts sl-DRX-ConfigUC-PC5:
[0269] 2> Configure the lower layer to perform sidelink DRX operations according to sl-DRX-ConfigUC-PC5 for the associated destination as defined in TS 38.321[3];
[0270] 1> If the RRCReconfigurationSidelink message contains sl-LatencyBoundIUC-Report:
[0271] 2> Application configured sidelink IUC reporting latency limits;
[0272] 1> If the RRCReconfigurationSidelink message contains sl-LocalID-PairToReleaseList or sl-LocalID-PairToAddModList:
[0273] 2> Configure the SRAP entity to perform NR sidelink L2 U2U relay operations accordingly for end-to-end PC5 connection of peer L2 U2U remote UEs, such as TS 38.351
[65]
[0274] Defined in the document;
[0275] 1> If the RRCReconfigurationSidelink message contains sl-MappingToAddModListPC5 or sl-MappingToReleaseListPC5:
[0276] 2> Configure the lower layer to perform NR side link L2 U2U relay operation according to the mapping between the end-to-end side link bearer of the L2 U2U remote UE and the egress PC5 relay RLC channel as defined in TS 38.351
[65] ;
[0277] 1> If the UE cannot comply with the (partial) configuration contained in RRCReconfigurationSidelink (i.e., sidelink RRC reconfiguration fails):
[0278] 2> Continue using the configuration used before receiving the RRCReconfigurationSidelink message;
[0279] 2> Set the content of the RRCReconfigurationFailureSidelink message;
[0280] 3> Submit the RRCReconfigurationFailureSidelink message to the lower layer for transmission;
[0281] 1> If the RRCReconfigurationSidelink message contains sl-SFN-DFN-Offset:
[0282] 2> If sl-SFN-DFN-Offset is set to setup:
[0283] 3> Apply the configured SFN-DFN time offset;
[0284] 2> If sl-SFN-DFN-Offset is set to release:
[0285] 3> Release the received sl-SFN-DFN-Offset;
[0286] 1> Otherwise:
[0287] 2> Set the content of the RRCReconfigurationCompleteSidelink message;
[0288] 3> If the UE refuses to receive the sidelink DRX configuration sl-DRX- from the peer UE
[0289] ConfigUC-PC5, then:
[0290] 4> Include sl-DRX-ConfigReject in the RRCReconfigurationCompleteSidelink message;
[0291] 4> Sidelink DRX is not considered for application to the corresponding sidelink unicast communication;
[0292] 3> Submit the RRCReconfigurationCompleteSidelink message to the lower layer for transmission;
[0293] Note 1: When the same logical channel is configured with a different RLC mode by another UE, the UE will treat the situation as a side link RRC reconfiguration failure.
[0294] Note 2: Whether to indicate rejection of the received sidelink DRX configuration to the peer UE depends on the UE implementation scheme.
[0295] [...]
[0296] 5.8.9.1.9 UE receiving RRCReconfigurationCompleteSidelink
[0297] The UE will perform the following actions after receiving RRCReconfigurationCompleteSidelink:
[0298] 1> Stop timer T400 at the destination (if it is running);
[0299] 1> Consider applying the configuration in the corresponding RRCReconfigurationSidelink message.
[0300] 2> If the RRCReconfigurationSidelink message contains sl-DRX-ConfigReject:
[0301] 3> Sidelink DRX is not considered for application to the corresponding sidelink unicast communication;
[0302] [...]
[0303] 5.8.9.1a Sidelink Radio Bearer Management
[0304] 5.8.9.1a.1 Sidelink DRB Release
[0305] 5.8.9.1a.1.1 Sidelink DRB Release Condition
[0306] For NR sidelink communication, initiate sidelink DRB release under the following conditions:
[0307] 1> For multicast, broadcast, and unicast, if the slrb-Uu-ConfigIndex of the sidelink DRB (if it exists) is included in sl-RadioBearerToReleaseList in sl-ConfigDedicatedNR; or
[0308] 1> For multicast and broadcast, if there is no sidelink QoS stream mapped to a sidelink DRB for transmission with data indicated by the upper layer, the sidelink QoS stream is (re)configured by receiving SIB12 or SidelinkPreconfigNR; or
[0309] 1> For multicast, broadcast, and unicast, if the SL-RLC-BearerConfigIndex (if present) of the associated RLC entity used for the sidelink DRB (i.e., containing additional sidelink RLC bearers, if applicable) is included in sl-RLC-BearerToReleaseList / sl-RLC-BearerToReleaseListSizeExt in sl-ConfigDedicatedNR; or
[0310] 1> For unicast, if there is no sidelink QoS stream mapped to a sidelink DRB for transmission with data indicated by the upper layer, the sidelink QoS stream is reconfigured by receiving SIB12 or SidelinkPreconfigNR; and if there is no sidelink QoS stream mapped to a sidelink DRB, the sidelink QoS stream is reconfigured by receiving RRCReconfigurationSidelink with data; or
[0311] 1> For unicast, if the SLRB-PC5-ConfigIndex of the sidelink DRB (if it exists) is included in slrb-ConfigToReleaseList in RRCReconfigurationSidelink, or if sl-ResetConfig is included in RRCReconfigurationSidelink; or
[0312] 1> For unicast, when the corresponding PC5-RRC connection is released due to the detection of a sidelink RLF in accordance with Clause 5.8.9.3; or
[0313] 1> For unicast, when the corresponding PC5-RRC connection is released due to an upper-layer request in accordance with Clause 5.8.9.5.
[0314] 5.8.9.1a.1.2 Sidelink DRB Release Operation
[0315] For each sidelink DRB that meets its sidelink DRB release condition as specified in Clause 5.8.9.1a.1.1, the UE configured by the upper layer to perform NR sidelink communication and capable of NR sidelink communication shall:
[0316] 1> For multicast and broadcast; or
[0317] 1> For unicast, if the sidelink DRB is released after receiving the RRCReconfigurationSidelink message; or
[0318] 1> For unicast, after receiving the RRCReconfigurationCompleteSidelink message, if the sidelink DRB release is triggered by a configuration received in sl-ConfigDedicatedNR, SIB12, or SidelinkPreconfigNR, or indicated by the upper layer, then:
[0319] 2> Release the PDCP entity used for NR sidelink communication associated with the sidelink DRB;
[0320] 2> If the SDAP entity used for NR sidelink communication associated with this sidelink DRB is configured as follows:
[0321] 3> Indicate the release of the sidelink DRB to the SDAP entity associated with this sidelink DRB (TS 37.324
[24] , Clause 5.3.3);
[0322] 2> Release SDAP entities (if present) that do not have an associated sidelink DRB as specified in Clause 5.1.2 of TS 37.324
[24] for NR sidelink communication;
[0323] 1> For multicast and broadcast; or
[0324] 1> For unicast, after receiving the RRCReconfigurationCompleteSidelink message, if the sidelink DRB release is triggered due to the configuration received in sl-ConfigDedicatedNR:
[0325] 2> For the sl-RLC received as part of the current UE sidelink configuration -
[0326] Each sl-RLC-BearerConfigIndex contained in BearerToReleaseList / sl-RLC-BearerToReleaseListSizeExt:
[0327] 3> Release the RLC entity and corresponding logical channel used for NR sidelink communication, which is associated with sl-RLC-BearerConfigIndex.
[0328] 1> For unicast, if the sidelink DRB is released due to receiving an RRCReconfigurationSidelink message; or
[0329] 1> For unicast, after receiving the RRCReconfigurationCompleteSidelink message, if the sidelink DRB release is triggered due to a configuration received in SIB12 or SidelinkPreconfigNR, or indicated by the upper layer, then:
[0330] 2> Release the RLC entity and corresponding logical channel used for NR sidelink communication associated with the sidelink DRB;
[0331] 2> Execute the sidelink UE information procedure for unicast in Clause 5.8.3 when necessary.
[0332] 1> If a sidelink radio link failure is detected for a specific destination, then:
[0333] 2> Release the PDCP entity, RLC entity, and logical channel of the sidelink SRB for a specific destination.
[0334] Editor's Note: Further research is needed on how to release the SL DRB on E2E and the hop configuration for U2U relays.
[0335] 5.8.9.1a.2 Adding / Modifying Side Link DRBs
[0336] 5.8.9.1a.2.1 Adding / Modifying Conditions for Side-Link DRB
[0337] For NR sidelink communication, sidelink DRB addition is initiated only under the following conditions:
[0338] 1> If any sidelink QoS flow is (re)configured by sl-ConfigDedicatedNR, SIB12, SidelinkPreconfigNR and will be mapped to a sidelink DRB that has not been established; or
[0339] 1> If any sidelink QoS flow is (re)configured by RRCReconfigurationSidelink and will be mapped to an unestablished sidelink DRB;
[0340] For NR sidelink communication, sidelink DRB modification is initiated only under the following conditions:
[0341] 1> For a sidelink DRB that is established, any of the parameters related to the sidelink DRB can be changed through sl-ConfigDedicatedNR, SIB12, SidelinkPreconfigNR, or RRCReconfigurationSidelink;
[0342] 5.8.9.1a.2.2 Side Link DRB Addition / Modification Operations
[0343] For a sidelink DRB that meets the conditions for adding a sidelink DRB as specified in Clause 5.8.9.1a.2.1, the UE configured by the upper layer to perform NR sidelink communication and capable of NR sidelink communication should:
[0344] 1> For multicast and broadcast; or
[0345] 1> For unicast, if a sidelink DRB is added due to receiving an RRCReconfigurationSidelink message; or
[0346] 1> For unicast, after receiving the RRCReconfigurationCompleteSidelink message, if the sidelink DRB addition is triggered due to configuration received in sl-ConfigDedicatedNR, SIB12, or SidelinkPreconfigNR, or indicated by the upper layer, then:
[0347] 2> If no SDAP entity for NR sidelink communication is associated with the destination and broadcast type of the sidelink DRB:
[0348] 3> Establish an SDAP entity for NR side link communication as specified in Clause 5.1.1 of TS 37.324
[24] ;
[0349] 2> Based on the sl-SDAP received in RRCReconfigurationSidelink
[0350] ConfigPC5 or the sl-SDAP-Config (re)configuration SDAP entity received in sl-ConfigDedicatedNR, SIB12, or SidelinkPreconfigNR associated with the sidelink DRB;
[0351] 2> Establish a PDCP entity for NR sidelink communication and configure the PDCP entity according to sl-PDCP-ConfigPC5 received in RRCReconfiguration Sidelink or sl-PDCP-Config received in sl-Config DedicatedNR, SIB12, or SidelinkPreconfigNR associated with the sidelink DRB;
[0352] 2> For each hop sidelink DRB (i.e., the UE does not act as an L2 U2U remote UE):
[0353] 3> Establish an RLC entity for NR sidelink communication and configure the RLC entity according to sl-RLC-ConfigPC5 received in RRCReconfiguration Sidelink or sl-RLC-Config received in sl-Config DedicatedNR, SIB12, or SidelinkPreconfigNR associated with the sidelink DRB;
[0354] 3> If this procedure is due to receiving an RRCReconfigurationSidelink message:
[0355] 4> Based on the sl-MAC received in the RRCReconfigurationSidelink associated with the sidelink DRB
[0356] LogicalChannelConfigPC5 configures the MAC entity using the logical channel and executes the sidelink UE information procedure in Clause 5.8.3 for unicast when necessary;
[0357] 3> Otherwise, if this procedure is due to receiving the RRCReconfigurationCompleteSidelink message, then:
[0358] 4> Configure the MAC entity with the logical channel associated with the sidelink DRB based on the sl-MAC-LogicalChannelConfig received in sl-ConfigDedicatedNR, SIB12, and SidelinkPreconfigNR;
[0359] 3> Otherwise (i.e., for multicast / broadcast):
[0360] 4> Based on the sl-MAC-LogicalChannelConfig received in sl-ConfigDedicatedNR, SIB12, and SidelinkPreconfigNR, configure the MAC entity with the logical channel associated with the sidelink DRB and assign the new LCID to this logical channel.
[0361] 2> For end-to-end link DRB (i.e., the UE acts as an L2 U2U remote UE):
[0362] 3> If the UE is in RRC_CONNECTED:
[0363] 4> Associate this end-to-end link DRB with the PC5 RLC channel indicated by sl-EgressRLC-ChannelPC5, which is included in sl-ConfigDedicatedNR, received from RRCReconfiguration;
[0364] 3> Otherwise, if the UE is in RRC_IDLE or RRC_INACTIVE:
[0365] 4> Based on the configuration in SIB12, associate this end-to-end link DRB with the PC5 RLC channel derived from the QoS attribute set of each SLRB through this end-to-end link DRB.
[0366] 3> Otherwise, if the UE is outside the coverage area:
[0367] 4> Based on the configuration in SidelinkPreconfigNR, associate this end-to-end link DRB with the PC5 RLC channel derived from the QoS attribute set of each SLRB through this end-to-end link DRB.
[0368] Note 1: When a sidelink DRB is added due to the configuration of RRCReconfigurationSidelink, the sidelink DRB configuration depends on the UE implementation scheme, which selects the parameters to be transmitted for the sidelink DRB from the received sl-ConfigDedicatedNR (if in RRC_CONNECTED), SIB12 (if in RRC_IDLE / INACTIVE), and SidelinkPreconfigNR (if not in coverage) of the RLC mode with the same mode configured in RRCReconfigurationSidelink.
[0369] For a sidelink DRB that meets the sidelink DRB modification conditions as specified in Clause 5.8.9.1a.2.1, the UE configured by the upper layer to perform NR sidelink communication and capable of NR sidelink communication should:
[0370] 1> For multicast and broadcast; or
[0371] 1> For unicast, if the sidelink DRB modification is triggered by receiving an RRCReconfigurationSidelink message; or
[0372] 1> For unicast, after receiving the RRCReconfigurationCompleteSidelink message, if the sidelink DRB modification is triggered due to a configuration received within sl-ConfigDedicatedNR, SIB12, or SidelinkPreconfigNR, then:
[0373] 2> Based on the sl-SDAP received in RRCReconfigurationSidelink
[0374] The SDAP entity that configures the sidelink DRB in sl-SDAP-Config received in ConfigPC5 or sl-ConfigDedicatedNR, SIB12, SidelinkPreconfigNR (if included);
[0375] 2> Based on the sl-PDCP received in RRCReconfigurationSidelink
[0376] The PDCP entity that reconfigures the sidelink DRB in ConfigPC5 or sl-PDCP-Config received in sl-ConfigDedicatedNR, SIB12, SidelinkPreconfigNR (if included);
[0377] 2> Based on the sl-RLC received in RRCReconfigurationSidelink
[0378] The RLC entity that reconfigures the sidelink DRB, either ConfigPC5 or sl-RLC-Config received in sl-ConfigDedicatedNR, SIB12, or SidelinkPreconfigNR (if included);
[0379] 2> Based on the sl-MAC received in RRCReconfigurationSidelink
[0380] LogicalChannelConfig PC5 or sl-MAC received in sl-ConfigDedicatedNR, SIB12, SidelinkPreconfigNR (if included)
[0381] LogicalChannelConfig reconfigures the logical channel of the sidelink DRB.
[0382] [...]
[0383] 5.8.9.7 PC5 Trunk RLC Channel Management for L2 U2N or U2U Trunks
[0384] 5.8.9.7.1 PC5 Relay RLC Channel Release
[0385] UE should:
[0386] 1> If the PC5 relay RLC channel is released after receiving the RRCReconfigurationSidelink message; or
[0387] 1> After receiving the RRCReconfigurationCompleteSidelink message, if the PC5 relay RLC channel release is triggered due to the configuration received in sl-ConfigDedicatedNR; or
[0388] 1> For unicast in L2 U2U relay operations, if there is no end-to-end link DRB associated with this RLC channel:
[0389] 2> For each SL-RLC-ChannelID received in sl-ConfigDedicatedNR within RRCReconfiguration in sl-ConfigDedicatedNR, or for each SL-RLC-ChannelID received as part of the current UE sidelink configuration...
[0390] For each SL-RLC-ChannelID contained in ChannelToReleaseListPC5, or for the RLC channel to be released:
[0391] 3> Release the RLC entity and the corresponding logical channel associated with the SL-RLC-ChannelID;
[0392] 1> If the PC5 relay RLC channel release is triggered by an upper layer as specified in 5.8.9.5 for a specific destination, or by an upper layer as specified in 5.8.9.10.4 for a specific destination corresponding to the received sl-DestinationIdentityRemoteUE, or is triggered due to a sidelink RLF as specified in 5.8.9.3:
[0393] 2> Release the RLC entity and the corresponding logical channel associated with the SL-RLC-ChannelID for the specific destination;
[0394] 5.8.9.7.2 Adding / Modifying RLC Channels in PC5 Relay
[0395] After establishing a PC5-RRC connection between the L2 U2N trunk UE and the L2 U2N remote UE, the L2U2N trunk UE should:
[0396] 1> If an SRAP entity has not yet been created, then create an SRAP entity as specified in TS 38.351
[66] ;
[0397] 1> Apply the RLC-specified configuration for SL-RLC0 as specified in Clause 9.1.1.4:
[0398] 1> If the L2 U2N relay UE is in the RRC_IDLE / INACTIVE state, then the RLC preset configuration of SL-RLC1 as defined in Clause 9.2.4 shall be applied;
[0399] After establishing a PC5-RRC connection between an L2 U2U remote UE and an L2 U2U relay UE, and after establishing a PC5-RRC connection between an L2 U2U relay UE and its peer L2 U2U remote UE, the L2U2U remote UE or L2 U2U relay UE should:
[0400] 1> If an SRAP entity has not yet been created, then create an SRAP entity as specified in TS 38.351
[66] ;
[0401] 1> Apply the RLC-specified configuration of the SL-U2U-RLC as specified in Clause 9.1.1.4;
[0402] UE should:
[0403] 1> If the addition / modification of a PC5 relay RLC channel is triggered by receiving an RRCReconfigurationSidelink message; or
[0404] 1> After receiving the RRCReconfigurationCompleteSidelink message, if the PC5 relay RLC channel addition / modification is triggered due to the configuration received in sl-ConfigDedicatedNR; or
[0405] 1> After receiving the RRCReconfigurationCompleteSidelink message, if PC5 relay RLC channel addition / modification is triggered for the end-to-end side link DRB based on the configuration in SIB12 or SidelinkPreconfigNR:
[0406] 2> If the current configuration contains a received sl-RLC-ChannelID or sl-RLC-
[0407] The PC5 trunk RLC channel of ChannelID-PC5; or
[0408] 2> If the configuration in SIB12 or SidelinkPreconfigNR has been updated, export the PC5 trunk RLC channel based on the configuration:
[0409] 3> Reconfigure the sidelink RLC entity based on the received sl-RLC-Config or sl-RLC-ConfigPC5;
[0410] 3> Based on the received sl-MAC-LogicalChannelConfig or sl-MAC-
[0411] LogicalChannel ConfigPC5 reconfigures the sidelink MAC entity using a logical channel;
[0412] 2> Otherwise (previously not configured with the received sl-RLC-ChannelID or sl-RLC-
[0413] ChannelID-PC5 PC5 Relay RLC Channel):
[0414] 3> Establish a sidelink RLC entity based on the received sl-RLC-Config (in sl-ConfigDedicatedNR, SIB12, or SidelinkPreconfigNR) or sl-RLC-ConfigPC5;
[0415] 3> Based on the received sl-MAC-LogicalChannelConfig or sl-MAC-
[0416] LogicalChannel ConfigPC5 configures the sidelink MAC entity using logical channels.
[0417] [...]
[0418] The following issue, RIL H693, was raised during the R18 ASN1 review to address the E2E SLRB to QoS mapping problem:
[0419] [RIL]: H693 [Entrusted]: Huawei (Rui Wang) [WI]: SLrelay [Type]: 2 [Status]: ToDo [TDoc]: R2-24xxxxx [Conclusion]: v032
[0420] [Description]: In L2 U2U, the source UEE needs to send an E2E SLRB to a QoS mapping to the relay UE for per-SLRB derivation. The original intention was to reuse the existing SDAP configuration to include the mapping. However, PQFI cannot distinguish between different destination UEs / E2E connections in U2U. Therefore, we propose a solution that introduces a new field / IE for U2U.
[0421] [Proposed changes]:
[0422] The proposed solution: To introduce the new field / type, use the QoS Flow ID to indicate links to different destination IDs. If further discussion is needed, we can include a discussion document with the TP to cover procedural text and changes to ASN.1.
[0423] The changes are as follows:
[0424]
[0425] [Comment]:
[0426] U2U (User-to-User) relaying was introduced in 3GPP Release 18, where a relay UE is used to support communication between two remote UEs that cannot communicate directly with each other due to being outside radio coverage. The relay UE needs to establish a PC5RRC connection (or PC5 unicast link) with each of the source remote UE (e.g., the first PC5 hop) and the target remote UE (e.g., the second PC5 hop), such as... Figure 10 The diagram illustrates a PC5 RRC connection for inter-UE relay according to an exemplary embodiment. Additionally, an end-to-end PC5 RRC connection can be established between these two remote UEs for Layer 2 (L2) U2U relay. The source remote UE can communicate with multiple target remote UEs via the same relay UE.
[0427] For an L2 remote UE connected to another L2 remote UE via an L2 relay UE, the end-to-end Quality of Service (QoS) requirements for relay services between peer L2 remote UEs can be met by the corresponding QoS control for the PC5 RRC connection between the L2 source remote UE and the L2 relay UE (i.e., the first-hop PC5 QoS control) and the QoS control for the PC5 RRC connection between the L2 relay UE and the L2 target remote UE (i.e., the second-hop PC5 QoS control).
[0428] To achieve this, the source remote UE and the target remote UE can first negotiate the end-to-end QoS requirements for the new PC5 QoS flow. Then, the source remote UE can provide the relay UE with the end-to-end QoS requirements (e.g., a set of QoS attributes) so that the relay UE can split the Packet Delay Budget (PDB) into one PDB value for the first hop and another PDB value for the second hop. The relay UE can then provide the source remote UE with the split PDB value for the first hop, allowing the source remote UE to determine the end-to-end (E2E) SL DRB configuration and the PC5 relay RLC channel configuration (for transmitting packets for the PC5 QoS flow to the target remote UE via the first hop) at least based on the split PDB value received from the relay UE. The source remote UE then provides the relay UE with the receive (Rx) RLC parameters of the PC5 relay RLC channel configuration (e.g., via an RRC reconfiguration sidelink message) so that the relay UE can receive packets for the PC5 QoS flow from the source remote UE on the PC5 relay RLC channel.
[0429] Additionally, the relay UE can determine another PC5 relay RLC channel configuration for the second hop based on another split PDB value (e.g., per SLRB QoS attribute set) and then provide the Rx RLC parameters of the PC5 relay RLC channel configuration to the target remote UE (e.g., via another RRC reconfiguration sidelink message) so that packets of the PC5 QoS stream can be forwarded to the target remote UE on the PC5 relay RLC channel via the second hop.
[0430] Essentially, different E2E SL-DRBs destined for the same or different remote UEs can be multiplexed by the source remote UE onto the same PC5 relay RLC channel for transmission. Therefore, the end-to-end PC5 radio bearer ID (E2E SL DRB ID), the source remote UE's local UE ID, and the target remote UE's local UE ID are included in the header of the SRAP PDU (for transmitting data packets) so that the relay UE can determine the egress PC5 relay RLC channel for forwarding data packets, and also so that the received data packets used by the target remote UE for a specific PDCP entity can be associated with the correct E2E SL DRB of the target remote UE. To support this, for each target remote UE, the source remote UE needs to maintain the mapping between the E2E SL DRB and the egress PC5 relay RLC channel via the first hop between the source remote UE and the relay UE. Furthermore, for each source-target remote UE pair, the relay UE needs to maintain the mapping between the E2E SL DRB and the egress PC5 relay RLC channel via the second hop between the relay UE and the target remote UE. The local UE ID of the remote UE can be assigned by the relay UE. Figure 16.12.7-1 of 3GPP TS 38.300V18.0.0 (reproduced as) Figure 7 The above concepts are illustrated in the diagram.
[0431] RIL H693 further proposes adding a new information element (IE) slrb-MappingConfigToAddMod List to allow the source remote UE to send a list of PC5 QoS flows mapped to SLRBs to the relay UE. This allows the relay UE to derive the per-SLRB QoS attribute set for each SLRB in the list to determine the PC5 relay RLC channel configuration for the SLRB. Another IE, slrb-MappingConfigToReleaseList, is also introduced to allow the source remote UE to release PC5 QoS flows to SLRB mappings. Each entry in the list contains an SLRB-PC5-ConfigIndex indicating the E2E SLRB. It is unclear how the relay will respond to receiving the slrb-MappingConfigToReleaseList. When releasing an E2E SLRB, the source remote UE needs to send the slrb-MappingConfigToReleaseList to the relay UE to release the associated PC5 QoS flows to the SLRB mapping. In this case, if there are no other E2E SL DRBs associated with the PC5 trunk RLC channel, the trunk UE should notify the target remote UE to release the PC5 trunk RLC channel associated with the E2E SLRB indicated in slrb-MappingConfigToReleaseList on the second hop. Figure 11 An example of the solution described above is shown. Specifically, Figure 11 An example of processing SLRB mapping configuration release according to an exemplary embodiment is shown.
[0432] Figure 12This is flowchart 1200 for a relay user equipment (UE). In step 1205, the relay UE establishes a first PC5 Radio Resource Control (RRC) connection with the source remote UE and a second PC5 RRC connection with the target remote UE. In step 1210, the relay UE receives a PC5 Quality of Service (QoS) flow-to-sidelink radio bearer (SLRB) mapping from the source remote UE, wherein the PC5 QoS flow-to-SLRB mapping includes an end-to-end (E2E) SLRB configuration index and at least one sidelink QoS flow identifier (ID). In step 1215, the relay UE transmits the configuration of a PC5 relay radio link control (RLC) channel to the target remote UE, wherein the E2E SLRB is associated with the PC5 relay RLC channel. In step 1220, the relay UE receives first information from the source remote UE indicating the release of the PC5 QoS flow-to-SLRB mapping. In step 1225, if there are no other E2E SLRBs associated with the PC5 relay RLC channel, the relay UE transmits second information indicating the release of the PC5 relay RLC channel to the target remote UE.
[0433] In one embodiment, the release of the PC5 QoS flow mapping to the SLRB can signify the release of the E2E SLRB. The relay UE can establish a PC5 relay RLC channel in response to receiving an RRC reconfiguration message from the network node for configuring the PC5 relay RLC channel. The relay UE can derive the per-SLRB QoS attribute set of the E2E SLRB based on the QoS information of the PC5 QoS flow identified by at least one sidelink QoS flow identifier (ID). The relay UE can determine the configuration of the PC5 relay RLC channel for the E2E SLRB based on the per-SLRB QoS attribute set of the E2E SLRB.
[0434] In one embodiment, the configuration of the PC5 relay RLC channel may be included in the first RRC reconfiguration sidelink message. The second information may be included in the second RRC reconfiguration sidelink message.
[0435] In one embodiment, after receiving an RRC reconfiguration complete sidelink message from the target remote UE, the relay UE can release the PC5 relay RLC channel.
[0436] Return to reference Figure 3 and 4In an exemplary embodiment from the perspective of the relay UE, the relay UE 300 includes program code 312 stored in memory 310. CPU 308 can execute program code 312 to enable the relay UE to (i) establish a first PC5 Radio Resource Control (RRC) connection with the source remote UE and a second PC5 RRC connection with the target remote UE, (ii) receive a PC5 Quality of Service (QoS) flow-to-sidelink radio bearer (SLRB) mapping from the source remote UE, wherein the PC5 QoS flow-to-SLRB mapping includes an end-to-end (E2E) SLRB configuration index and at least one sidelink QoS flow identifier (ID), (iii) transmit the configuration of a PC5 relay radio link control (RLC) channel to the target remote UE, wherein the E2E SLRB is associated with the PC5 relay RLC channel, (iv) receive first information from the source remote UE indicating the release of the PC5 QoS flow-to-SLRB mapping, and (v) transmit second information to the target remote UE indicating the release of the PC5 relay RLC channel if no other E2ESLRB is associated with the PC5 relay RLC channel. In addition, CPU 308 can execute program code 312 to perform all the above actions and steps or other actions and steps described herein.
[0437] Various aspects of this disclosure have been described above. It should be understood that the teachings herein can be implemented in a wide variety of forms, and any specific structure, function, or both disclosed herein are merely representative. Based on the teachings herein, those skilled in the art will understand that the aspects disclosed herein can be implemented independently of any other aspects, and two or more of these aspects can be combined in various ways. For example, any number of aspects set forth herein can be used to implement an apparatus or practice. Furthermore, such apparatuses or practices can be implemented using structures, functions, or structures and functions other than or different from those set forth herein. As examples of some of the foregoing concepts, in some aspects, a parallel channel can be established based on the pulse repetition frequency. In some aspects, a parallel channel can be established based on the pulse position or offset. In some aspects, a parallel channel can be established based on a jump sequence. In some aspects, a parallel channel can be established based on the pulse repetition frequency, the pulse position or offset, and a time jump sequence.
[0438] Those skilled in the art will understand that information and signals can be represented using any of a variety of different techniques and skills. For example, data, instructions, commands, information, signals, bits, symbols, and chips that may be referenced throughout the above description can be represented by voltage, current, electromagnetic waves, magnetic fields or magnetic particles, light fields or light particles, or any combination thereof.
[0439] Those skilled in the art will further appreciate that the various illustrative logic blocks, modules, processors, components, circuits, and algorithm steps described in conjunction with the aspects disclosed herein can be implemented as electronic hardware (e.g., a digital implementation designed using source decoding or some other technique, an analog implementation, or a combination of both), incorporating various forms of program or design code with instructions (which, for convenience, may be referred to herein as "software" or "software module"), or a combination of both. To clearly illustrate this interchangeability between hardware and software, the various illustrative components, blocks, modules, circuits, and steps have been described above generally in terms of their functionality. Whether this functionality is implemented as hardware or software depends on the specific application and the design constraints imposed on the system as a whole. Those skilled in the art can implement the described functionality in different ways for each specific application, but such implementation decisions should not be construed as a departure from the scope of this disclosure.
[0440] Furthermore, the various illustrative logic blocks, modules, and circuits described in connection with the aspects disclosed herein may be implemented within or executed by an integrated circuit (“IC”), access terminal, or access point. An IC may include a general-purpose processor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA) or other programmable logic device, discrete gate or transistor logic, discrete hardware components, electrical components, optical components, mechanical components, or any combination thereof designed to perform the functions described herein, and may execute code or instructions residing within the IC, outside the IC, or both. A general-purpose processor may be a microprocessor, but alternatively, the processor may be any conventional processor, controller, microcontroller, or state machine. The processor may also be implemented as a combination of computing devices, such as a combination of a DSP and a microprocessor, multiple microprocessors, one or more microprocessors combined with a DSP core, or any other such configuration.
[0441] It should be understood that any particular order or hierarchy of steps in any disclosed process is an instance of an example method. It should be understood that a particular order or hierarchy of steps in the process may be rearranged based on design preferences while remaining within the scope of this disclosure. The appended method claims present the elements of the various steps in a sample order and are not intended to be limited to any particular order or hierarchy presented.
[0442] The steps of the methods or algorithms described in conjunction with the aspects disclosed herein can be implemented directly in hardware, with software modules executed by a processor, or a combination of both. Software modules (e.g., containing executable instructions and associated data) and other data can reside in data memory, such as RAM memory, flash memory, ROM memory, EPROM memory, EEPROM memory, registers, hard disk, removable disk, CD-ROM, or any other form of computer-readable storage medium known in the art. Example storage media can be coupled to a machine such as a computer / processor (for convenience, the machine may be referred to herein as a "processor"), such that the processor can read information (e.g., code) from the storage medium and write information to the storage medium. Example storage media can be integrated with the processor. The processor and storage medium can reside in an ASIC. The ASIC can reside in a user equipment. Alternatively, the processor and storage medium can reside in a user equipment as discrete components. Furthermore, in some aspects, any suitable computer program product may include a computer-readable medium comprising code associated with one or more aspects of this disclosure. In some respects, computer program products may include packaging materials.
[0443] While the invention has been described in conjunction with various aspects, it should be understood that further modifications can be made to the invention. This application is intended to cover any changes, uses, or adaptations to the invention that generally follow the principles of the invention and include such deviations from this disclosure, which fall within the scope of known and customary practice in the art to which this invention pertains.
Claims
1. A method for relay user equipment, characterized in that, include: The relay user equipment establishes a first PC5 radio resource control connection with the source remote user equipment and a second PC5 radio resource control connection with the target remote user equipment. After the first PC5 radio resource control connection between the relay user equipment and the source remote user equipment is established, the relay user equipment receives a PC5 quality of service flow to sidelink radio bearer mapping from the source remote user equipment, wherein the PC5 quality of service flow to sidelink radio bearer mapping includes an end-to-end sidelink radio bearer configuration index and at least one sidelink quality of service flow identifier. After the second PC5 radio resource control connection between the relay user equipment and the target remote user equipment is established, the relay user equipment transmits the configuration of the PC5 relay radio link control channel to the target remote user equipment, wherein the end-to-end side link radio bearer is associated with the PC5 relay radio link control channel. The relay user equipment receives from the source remote user equipment a first message indicating the release of the PC5 quality of service flow to the sidelink radio bearer mapping; as well as When there are no other end-to-end side link radio bearers associated with the PC5 relay radio link control channel, the relay user equipment transmits a second message to the target remote user equipment indicating the release of the PC5 relay radio link control channel.
2. The method according to claim 1, characterized in that, The release of the PC5 Quality of Service flow to the sidelink radio bearer mapping means that the end-to-end sidelink radio bearer is released.
3. The method according to claim 1, characterized in that, The method further includes: The relay user equipment establishes the PC5 relay radio link control channel in response to receiving a radio resource control reconfiguration message from a network node for configuring the PC5 relay radio link control channel.
4. The method according to claim 1, characterized in that, The method further includes: The relay user equipment derives the set of service quality attributes for each sidelink radio bearer of the end-to-end sidelink radio bearer based on the service quality information of the PC5 service quality flow identified by the at least one sidelink service quality flow identifier.
5. The method according to claim 4, characterized in that, The method further includes: The relay user equipment determines the configuration of the PC5 relay radio link control channel for the end-to-end side link radio bearer based on the quality of service attribute set of each side link radio bearer of the end-to-end side link radio bearer.
6. The method according to claim 1, characterized in that, The configuration of the PC5 relay radio link control channel is included in the first radio resource control reconfiguration sidelink message.
7. The method according to claim 1, characterized in that, The second information is contained in the second radio resource control message reconfiguration sidelink message.
8. The method according to claim 1, characterized in that, The method further includes: After receiving a radio resource control reconfiguration complete sidelink message from the target remote user equipment, the relay user equipment releases the PC5 relay radio link control channel.
9. A relay user equipment, characterized in that, include: Control circuit; A processor, which is installed in the control circuit; as well as A memory, which is mounted in the control circuit and operatively coupled to the processor; The processor is configured to execute program code stored in the memory to: Establish a first PC5 radio resource control connection with the source remote user equipment and a second PC5 radio resource control connection with the target remote user equipment; After the first PC5 radio resource control connection between the relay user equipment and the source remote user equipment is established, a PC5 quality of service flow to sidelink radio bearer mapping is received from the source remote user equipment, wherein the PC5 quality of service flow to sidelink radio bearer mapping includes an end-to-end sidelink radio bearer configuration index and at least one sidelink quality of service flow identifier. After the second PC5 radio resource control connection between the relay user equipment and the target remote user equipment is established, the configuration of the PC5 relay radio link control channel is transmitted to the target remote user equipment, wherein the end-to-end side link radio bearer is associated with the PC5 relay radio link control channel. Receive first information from the source remote user equipment indicating the release of the PC5 quality of service flow to the sidelink radio bearer mapping; as well as If no other end-to-end side link radio bearer is associated with the PC5 relay radio link control channel, a second message indicating the release of the PC5 relay radio link control channel is transmitted to the target remote user equipment.
10. The relay user equipment according to claim 9, characterized in that, The release of the PC5 Quality of Service flow to the sidelink radio bearer mapping means that the end-to-end sidelink radio bearer is released.
11. The relay user equipment according to claim 9, characterized in that, The processor is further configured to execute program code stored in the memory to: The PC5 relay radio link control channel is established in response to receiving a radio resource control reconfiguration message from a network node for configuring the PC5 relay radio link control channel.
12. The relay user equipment according to claim 9, characterized in that, The processor is further configured to execute program code stored in the memory to: The service quality information of the PC5 service quality flow identified by the at least one sidelink service quality flow identifier is used to derive the service quality attribute set of each sidelink radio bearer of the end-to-end sidelink radio bearer.
13. The relay user equipment according to claim 12, characterized in that, The processor is further configured to execute program code stored in the memory to: The configuration of the PC5 relay radio link control channel for the end-to-end side link radio bearer is determined based on the quality of service attribute set of each side link radio bearer of the end-to-end side link radio bearer.
14. The relay user equipment according to claim 9, characterized in that, The configuration of the PC5 relay radio link control channel is included in the first radio resource control reconfiguration sidelink message.
15. The relay user equipment according to claim 9, characterized in that, The second information is contained in the second radio resource control reconfiguration sidelink message.
16. The relay user equipment according to claim 9, characterized in that, The processor is further configured to execute program code stored in the memory to: After receiving the radio resource control reconfiguration complete sidelink message from the target remote user equipment, the PC5 relay radio link control channel is released.
