Method and apparatus for user equipment-to-network relay discovery in wireless communication system

Abstract

A method and apparatus for user equipment to network relay discovery in a wireless communication system are disclosed. The second relay user equipment receives a first user equipment-to-network relay discovery message from the first relay user equipment, wherein the first user equipment-to-network relay discovery message includes a user information identifier of the first relay user equipment, a layer-2 identifier of the third relay user equipment, and an identifier of a serving cell of the third relay user equipment. Further, the second relay user equipment transmits a second user equipment-to-network relay discovery message to the remote user equipment, where the second user equipment-to-network relay discovery message includes a user information identification of the second relay user equipment and a Layer 2 identification of the third relay user equipment and an identification of the serving cell.

Description

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS

[0002] This application claims the benefit of U.S. Provisional Patent Application No. 63 / 529,312, filed on July 27, 2023, the entire disclosure of which is incorporated herein by reference in its entirety. Technical Field

[0003] The present disclosure relates generally to wireless communication networks, and more particularly, to a method and apparatus for multi-hop UE-to-network relay discovery in a wireless communication system. Background Art

[0004] As the demand for transmitting large amounts of data to and from mobile communication devices grows rapidly, traditional mobile voice communication networks have evolved into networks with Internet Protocol (IP) packet communications, which can provide IP-based voice, multimedia, multicast, and on-demand communication services to users of mobile communication devices.

[0005] An exemplary network structure is an Evolved Universal Terrestrial Radio Access Network (E-UTRAN). The E-UTRAN system can provide high data throughput to enable the above-mentioned IP-bearing voice and multimedia services. Currently, the 3rd Generation Partnership Project (3GPP) standards organization is discussing new next-generation (e.g., 5G) radio technologies. Therefore, changes to the current body of 3GPP standards are currently being submitted and considered to evolve and finalize the 3GPP standards. Summary of the invention

[0006] The present invention discloses a method and apparatus for UE to network (U2N) relay discovery. In one embodiment, a second relay UE receives a first U2N relay discovery message from a first relay UE, wherein the first U2N relay discovery message includes a user information identification (ID) of the first relay UE, a layer 2 ID of a third relay UE, and an ID of a serving cell of the third relay UE. In addition, the second relay UE transmits a second U2N relay discovery message to a remote UE, wherein the second U2N relay discovery message includes the user information ID of the second relay UE, the layer 2 ID, and the ID of the serving cell. BRIEF DESCRIPTION OF THE DRAWINGS

[0007] Figure 1 A diagram illustrating a wireless communication system according to an exemplary embodiment;

[0008] Figure 2 is a block diagram of a transmitter system (also referred to as an access network) and a receiver system (also referred to as a user equipment or UE) according to an exemplary embodiment;

[0009] Figure 3 is a functional block diagram of a communication system according to an exemplary embodiment;

[0010] Figure 4 According to an exemplary embodiment Figure 3 Functional block diagram of the program code;

[0011] Figure 5 For 3GPP TS23.304V18.2.0 Figure 4 .2.7.1-1 reappearance;

[0012] Figure 6 For 3GPP TS23.304V18.2.0 Figure 4 .2.7.2-1 reappearance;

[0013] Figure 7 For 3GPP TS23.304V18.2.0 Figure 6 .3.2.1-1 reappearance;

[0014] Figure 8 For 3GPP TS23.304V18.2.0 Figure 6 .3.2.1-2 reappearance;

[0015] Fig. 9 For 3GPP TS23.304V18.2.0 Figure 6 .3.2.3.2-1 reappearance;

[0016] Fig.10 For 3GPP TS23.304V18.2.0 Figure 6 .3.2.3.3-1 reappearance;

[0017] Fig.11 For 3GPP TS23.304V18.2.0 Figure 6 .4.3.1-1 reappearance;

[0018] Fig.12 For 3GPP TS23.304V18.2.0 Figure 6 .5.1.1-1 reappearance;

[0019] Fig.13 For 3GPP TS23.304V18.2.0 Figure 6 .5.2.2-1 reappearance;

[0020] Fig.14 For 3GPP TS 38.300 V17.5.0 Fig.16 .12.5.1-1 reappearance;

[0021] Fig.15 For 3GPP TS 38.300 V17.5.0 Fig.16 .12.6.1-1 reappearance;

[0022] Fig.16 For 3GPP TS 38.300 V17.5.0 Fig.16 .12.6.2-1 reappearance;

[0023] Fig.17 An exemplary 3-hop UE to network relay is shown according to an exemplary embodiment;

[0024] Fig.18 illustrates a multi-route UE-to-network relay according to an exemplary embodiment;

[0025] Fig.19 illustrates multi-hop UE-to-network relay discovery according to an exemplary embodiment;

[0026] Fig. 20 shows remote UE measurement reporting with Model A according to an exemplary embodiment;

[0027] Fig.21 is a flow chart according to an exemplary embodiment. DETAILED DESCRIPTION

[0028] The exemplary wireless communication systems and devices described below adopt wireless communication systems that support broadcast services. Wireless communication systems are widely deployed to provide various types of communications such as voice, data, etc. These systems can be based on code division multiple access (CDMA), time division multiple access (TDMA), orthogonal frequency division multiple access (OFDMA), 3GPP Long Term Evolution (LTE) wireless access, 3GPP Long Term Evolution Advanced (LTE-A or Advanced LTE), 3GPP2 Ultra Mobile Broadband (UMB), WiMax, 3GPP New Radio (NR) or some other modulation technology.

[0029] Specifically, the exemplary wireless communication systems and devices described below may be designed to support one or more standards, such as those provided by an alliance named “3rd Generation Partnership Project” referred to herein as 3GPP, including: TS 23.304 V18.2.0, “Proximity based Service (ProSe) in 5G System (5GS) (Release 18)”; TS 38.300 V17.5.0, “NR; NR and NG-RAN Overall Description; Stage 2 (Release 17)”; and TS 22.261 V19.3.0, “Service Requirements for 5G System; Stage 1 (Release 19)”. The standards and documents listed above are expressly incorporated herein by reference in their entirety.

[0030] Figure 1 A multiple access wireless communication system according to an embodiment of the present invention is shown. An access network 100 (AN) includes multiple antenna groups, one group includes 104 and 106, another group includes 108 and 110, and an additional group includes 112 and 114. Figure 1 , only two antennas are shown for each antenna group, however, each antenna group may 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 a frequency division duplex (FDD) system, communication links 118, 120, 124, and 126 may use different frequencies for communication. For example, forward link 120 may use a different frequency than reverse link 118.

[0031] Each antenna group and / or the area in which the antenna group is designed to communicate is often referred to as a sector of the access network. In an embodiment, the antenna groups are each designed to communicate with access terminals in a sector of the area covered by the access network 100.

[0032] In communicating via forward links 120 and 126, the transmit antennas of access network 100 may utilize beamforming in order to improve the signal-to-noise ratio of the forward links for the different access terminals 116 and 122. Also, an access network using beamforming to transmit to access terminals randomly dispersed throughout its coverage area may cause less interference to access terminals in neighboring cells than if the access network transmitted to all of its access terminals via a single antenna.

[0033] An access network (AN) may be a fixed station or base station for communicating with a terminal, and may also be referred to as an access point, a Node B, a base station, an enhanced base station, an evolved Node B (eNB), a network node, a network, or some other terminology. An access terminal (AT) may also be referred to as a user equipment (UE), a wireless communication device, a terminal, an access terminal, or some other terminology.

[0034] Figure 2 A simplified block diagram of an embodiment of a transmitter system 210 (also referred to as an access network) and a receiver system 250 (also referred to as an access terminal (AT) or user equipment (UE)) in a multiple input multiple output (MIMO) system 200. At the transmitter system 210, traffic data for a number of data streams is provided from a data source 212 to a transmit (TX) data processor 214.

[0035] In one embodiment, each data stream is transmitted via a respective transmit antenna.TX data processor 214 formats, codes, and interleaves the traffic data for each data stream based on a particular coding scheme selected for that data stream to provide coded data.

[0036] The coded data for each data stream may be multiplexed with pilot data using OFDM techniques. The pilot data is typically a known data pattern that is processed in a known manner and may be used at the receiver system to estimate the channel response. The multiplexed pilot and coded data for each data stream are then modulated (i.e., symbol mapped) based on a specific modulation scheme selected for the data stream (e.g., Binary Phase Shift Keying (BPSK), Quadrature Phase Shift Keying (QPSK), Multiple Phase Shift Keying (M-PSK), or Quadrature Amplitude Modulation (M-QAM)) to provide modulation symbols. The data rate, coding, and modulation for each data stream may be determined by instructions executed by the processor 230.

[0037] The modulation symbols for all data streams are then provided to a TX MIMO processor 220, which may further process the modulation symbols (e.g., for OFDM). T The modulation symbol stream is provided to N Ttransmitters (TMTR) 222a through 222t. In certain embodiments, TX MIMO processor 220 applies beamforming weights to the symbols of the data streams and to the antenna from which the symbol is being transmitted.

[0038] Each transmitter 222 receives and processes a respective symbol stream to provide one or more analog signals, and further conditions (eg, amplifies, filters, and upconverts) the analog signals to provide a modulated signal suitable for transmission over the MIMO channel. T The antennas 224a to 224t transmit the N signals from the transmitters 222a to 222t. T a modulated signal.

[0039] At the receiver system 250, N R The transmitted modulated signals are received by each antenna 252a through 252r and the received signal from each antenna 252 is provided to a respective receiver (RCVR) 254a through 254r. Each receiver 254 conditions (e.g., filters, amplifies, and downconverts) a respective received signal, digitizes the conditioned signal to obtain samples, and further processes the samples to provide a corresponding “received” symbol stream.

[0040] The RX data processor 260 then receives and processes the N R The N received by the receiver 254 R symbol streams to provide N T The RX data processor 260 then demodulates, deinterleaves, and decodes each detected symbol stream to recover the traffic data for the data stream. The processing by the RX data processor 260 is complementary to the processing performed by the TX MIMO processor 220 and the TX data processor 214 at the transmitter system 210.

[0041] Processor 270 periodically determines which pre-coding matrix to use (discussed below). Processor 270 formulates a reverse link message comprising a matrix index portion and a rank value portion.

[0042] The reverse link message may include various types of information about the communication link and / or the received data stream. The reverse link message is then processed by the TX data processor 238, which also receives traffic data for a number of data streams from the data source 236, modulated by the modulator 280, conditioned by the transmitters 254a to 254r, and transmitted back to the transmitter system 210.

[0043] At the transmitter system 210, the modulated signals from the receiver system 250 are received by the antenna 224, conditioned by the receiver 222, demodulated by the demodulator 240, and processed by the RX data processor 242 to extract the reverse link message transmitted by the receiver system 250. The processor 230 then determines which precoding matrix to use to determine the beamforming weights and then processes the extracted message.

[0044] Steering Figure 3 , this figure shows an alternative simplified functional block diagram of a communication device according to one embodiment of the present invention. Figure 3 As shown, the communication device 300 in the wireless communication system can be used to implement Figure 1 UE (or AT) 116 and 122 in or Figure 1 The base station (or AN) 100 in 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, a program code 312 and a transceiver 314. The control circuit 306 executes the program code 312 in the memory 310 through the CPU 308, thereby controlling the operation of the communication device 300. The communication device 300 can receive signals input by the user through the input device 302 (such as a keyboard or a keypad), and can output images and sounds through the output device 304 (such as a display or a speaker). The transceiver 314 is used to receive and transmit wireless signals, pass the received signals to the control circuit 306, and wirelessly output the signals generated by the control circuit 306. The communication device 300 in the wireless communication system can also be used to implement Figure 1 AN 100 in.

[0045] Figure 4 According to one embodiment of the present invention, Figure 3 4. In this embodiment, program code 312 includes application layer 400, layer 3 portion 402, and layer 2 portion 404, and is coupled to layer 1 portion 406. Layer 3 portion 402 typically performs radio resource control. Layer 2 portion 404 typically performs link control. Layer 1 portion 406 typically performs physical connectivity.

[0046] 3GPP TS 23.304 specifies the procedures related to UE to network relay as follows:

[0047] 4.2.7 5G ProSe UE to Network Relay Reference Architecture

[0048] 4.2.7.1 5G ProSe layer 3 UE to network relay reference architecture

[0049] Down Figure 4.2.7.1-1 shows a high-level reference architecture for 5G ProSe layer 3 UE to network relay. In this figure, the 5G ProSe layer 3 UE to network relay can be in the HPLMN or VPLMN.

[0050] [3GPP TS 23.304 V18.2.0 titled "Reference architecture for 5G ProSe layer 3 UE to network relay" Figure 4 .2.7.1-1 Reproduced as Figure 5 ]

[0051] […]

[0052] 4.2.7.2 5G ProSe layer 2 UE to network relay reference architecture

[0053] Figure 4 .2.7.2-1 shows the 5G ProSe Layer 2 UE to Network Relay reference architecture. The 5G ProSe Layer 2 Remote UE and the 5G ProSe Layer 2 UE to Network Relay may be served by the same or different PLMNs. If the serving PLMNs of the 5G ProSe Layer 2 Remote UE and the 5G ProSe Layer 2 UE to Network Relay are different, the NG-RAN is shared by the serving PLMN, see 5G MOCN architecture in Section 5.18 of TS 23.501 [4].

[0054] [3GPP TS23.304 V18.2.0 titled "5G ProSe layer 2 UE to network relay reference architecture" Figure 4 .2.7.2-1 Reproduced as Figure 6 ]

[0055] NOTE 1: Uu between 5G ProSe Layer 2 Remote UE and NG-RAN consists of RRC, SDAP and PDCP.

[0056] Note 2: 5G ProSe Layer 2 Remote UE and 5G ProSe Layer 2 UE to Network Relay are served by the same NG-RAN. The core network entities (e.g., AMF, SMF, UPF) serving 5G ProSe Layer 2 Remote UE and 5G ProSe Layer 2 UE to Network Relay may be the same or different.

[0057] […]

[0058] 6.3.2 5G ProSe direct discovery procedure over PC5 reference point

[0059] 6.3.2.1 Overview

[0060] The PC5 communication channel is used to carry discovery messages on the PC5, and the discovery messages on the PC5 are distinguished from other PC5 messages by the AS layer.

[0061] Supports both Model A and Model B discovery as defined in TS 23.303 [3]:

[0062] - Model A uses a single discovery protocol message (Notify).

[0063] - Model B uses two discovery protocol messages (solicit and response).

[0064] Figure 6 The procedure for 5G ProSe direct discovery with Model A is described in .3.2.1-1.

[0065] [3GPP TS 23.304 V18.2.0 titled "5G ProSe direct discovery with Model A" Figure 6 .3.2.1-1 Reproduced as Figure 7 ]

[0066] 1. Notify the UE to send a notification message. The notification message may include the type of discovery message, ProSe application code or ProSe restricted code, relay_Indication, security protection element, and [metadata information]. The application layer metadata information may be included in the notification message as metadata.

[0067] The destination Layer 2 ID and source Layer 2 ID used to send the notification message are specified in clauses 5.8.1.2 and 5.8.1.3.

[0068] If the 5G ProSe inter-UE relay can broadcast its user information ID during 5G ProSe inter-UE discovery, the notification UE includes relay_Indication.

[0069] The listening UE determines the destination Layer 2 ID for signaling reception. The destination Layer 2 ID is configured with the UE as specified in clause 5.8.2.1.

[0070] Figure 6 The procedure for 5G ProSe direct discovery with Model B is described in .3.2.1-2.

[0071] [3GPP TS TS23.304 V18.2.0 titled "5G ProSe Direct Discovery with Model B" Figure 6 .3.2.1-2 is reproduced as Figure 8 ]

[0072] 1. The discoverer UE sends a request message. The request message may include the type of discovery message, ProSe query code, relay_Indication, and security protection element.

[0073] The destination Layer 2 ID and source Layer 2 ID used to send the solicitation message are specified in clauses 5.8.1.2 and 5.8.1.3.

[0074] How the discoverer UE determines the destination Layer 2 ID for signalling reception is specified in clause 5.8.1.2.

[0075] If the 5G ProSe inter-UE relay can broadcast its user information ID during 5G ProSe inter-UE discovery, the discoverer UE includes relay_Indication.

[0076] 2. The discoverer UE that matches the solicitation message responds to the discoverer UE using a response message. The response message may include the type of discovery message, ProSe response code, relay_Indication, security protection element, and [metadata information]. The application layer metadata information may be included in the response message as metadata.

[0077] If the 5G ProSe inter-UE relay can broadcast its user information ID during 5G ProSe inter-UE discovery, the discovered UE includes relay_Indication.

[0078] The source Layer 2ID used to send the response message is specified in clause 5.8.1.3. The destination Layer 2ID is set to the source Layer 2ID of the received solicitation message.

[0079] NOTE: Details of security protection elements are specified in TS 33.503

[29] .

[0080] […]

[0081] 6.3.2.3 5G ProSe UE to Network Relay Discovery

[0082] 6.3.2.3.1 Overview

[0083] 5G ProSe UE to Network Relay Discovery is applicable to both 5G ProSe Layer 3 and Layer 2 UE to Network Relay Discovery for public safety purposes and commercial services. To perform 5G ProSe UE to Network Relay Discovery, the 5G ProSe Remote UE and the 5G ProSe UE to Network Relay are pre-configured or provisioned with relevant information as described in clause 5.1.

[0084] In 5G ProSe UE to network relay discovery, the UE uses pre-configured or provisioned information for the relay discovery procedure as defined in clause 5.1.4.1.

[0085] The Relay Service Code (RSC) is used for 5G ProSe UE to Network Relay discovery to indicate the connectivity service provided by the 5G ProSe UE to Network Relay to the 5G ProSe Remote UE. The RSC (including one RSC dedicated to emergency services) is configured on the 5G ProSe UE to Network Relay and the 5G ProSe Remote UE as defined in clause 5.1.4. Based on the policy specified in clause 5.1.4, the 5G ProSe UE to Network Relay and the 5G ProSe Remote UE know whether the RSC is providing 5G ProSe Layer 2 or Layer 3 UE to Network Relay service and whether the RSC is used for emergency services. A 5G ProSe UE to Network Relay supporting multiple RSCs may use multiple discovery messages to advertise the RSCs with one RSC per discovery message.

[0086] NOTE: Clause 5.4.4 specifies when the 5G ProSe UE to network relay can broadcast an emergency RSC.

[0087] Additional information not used directly for discovery may also be announced using the PC5-D protocol stack in a single or separate discovery messages of type "Relay Discovery Additional Information" as defined in section 5.8.3.1.

[0088] 6.3.2.3.2 Procedure for 5G ProSe UE to Network Relay Discovery with Model A

[0089] Figure 6 .Described in 3.2.3.2-1 is the procedure for 5G ProSe UE to network relay discovery with Model A.

[0090] [3GPP TS 23.304 V18.2.0 titled "5G ProSe UE to Network Relay Discovery with Model A" Figure 6 .3.2.3.2-1 Reproduced as Fig. 9 ]

[0091] 1.5G ProSe UE to Network Relay sends a UE to Network Relay Discovery Notification message. The UE to Network Relay Discovery Notification message contains the type of discovery message, notifier information and RSC, and is sent using source layer 2 ID and destination layer 2 ID as described in clause 5.8.3.

[0092] For 5G ProSe Layer 3 UE-to-network relay, the 5G ProSe Layer 3 UE-to-network relay shall only include the RSC in the UE-to-network relay discovery notification when the S-NSSAI associated with the RSC belongs to the allowed NSSAI of the UE-to-network relay.

[0093] The 5G ProSe Remote UE (1 to 3) determines the destination Layer 2 ID for signaling reception. As specified in clause 5.1.4.1, the destination Layer 2 ID is configured with the UE.

[0094] The 5G ProSe remote UEs (1 to 3) listen to the notification message and the 5G ProSe UE to network RSC corresponding to the service to be served.

[0095] Optionally, the 5G ProSe UE to Network Relay may also send a Relay Discovery Additional Information message as defined in clause 6.5.1.3. The parameters contained in this message as well as the source layer 2 ID and destination layer 2 ID used to send and receive messages are described in clause 5.8.3.

[0096] The 5G ProSe remote UE selects a 5G ProSe UE to network relay based on the information received in step 1.

[0097] NOTE: The access stratum information used for 5G ProSe UE to network relay selection is specified in the RAN specification.

[0098] 6.3.2.3.3 Procedure for 5G ProSe UE to Network Relay Discovery with Model B

[0099] Figure 6 .Described in 3.2.3.3-1 is the procedure for 5G ProSe UE to network relay discovery with Model B.

[0100] [3GPP TS 23.304 V18.2.0 titled "5G ProSe UE to Network Relay Discovery with Model B" Figure 6 .3.2.3.3-1 Reproduced as Fig.10 ]

[0101] 1. The 5G ProSe Remote UE sends a 5G ProSe UE to Network Relay Discovery Solicitation message. The 5G ProSe UE to Network Discovery Solicitation message contains the type of discovery message, discoverer information, RSC and optional target message, and is sent using source layer 2 ID and destination layer 2 ID as described in clause 5.8.3. The 5G ProSe Remote UE discovering the 5G ProSe UE to Network Relay sends the solicitation message with the RSC associated with the desired connectivity service. The RSC is based on the policy / parameters specified in clause 5.1.4.1.

[0102] The way in which the 5G ProSe UE to Network Relay (1 to 3) determines the destination Layer 2 ID for signaling reception is specified in clause 5.8.3. As specified in clause 5.1.4.1, the destination Layer 2 ID is configured with the UE.

[0103] 2. The 5G ProSe UE to Network Relay (1 and 2) matching the value of the RSC and target information (if present) contained in the solicitation message responds to the 5G ProSe Remote UE with a UE to Network Relay Discovery Response message. The 5G ProSe UE to Network Relay Discovery Response message contains the type of discovery message, discoverer information and RSC, and is sent using the source Layer 2 ID and destination Layer 2 ID as described in clause 5.8.3.

[0104] For the 5G ProSe Layer 3 UE-to-network Relay, the 5G ProSe UE-to-network Relay shall only respond to a matching RSC in the UE-to-network Relay Discovery Solicitation message when the S-NSSAI associated with the RSC belongs to the allowed NSSAIs of the 5G ProSe UE-to-network Relay.

[0105] The 5G ProSe remote UE selects a 5G ProSe UE to network relay based on the information received in step 2.

[0106] […]

[0107] 6.5.1 5G ProSe Communication via 5G ProSe Layer 3 UE to Network Relay

[0108] 6.5.1.0 Overview

[0109] 5G ProSe communications via 5G ProSe Layer 3 UE to Network Relay may be performed with or without involvement of N3 IWF for non-emergency services and for emergency services as specified in clause 5.4.4.

[0110] 6.5.1.1 5G ProSe communication via 5G ProSe layer 3 UE to network relay without N3IWF

[0111] 5G ProSe Layer 3 UE to Network Relay registers with the network (if not already registered). 5G ProSe Layer 3 UE to Network Relay establishes a PDU Session or modifies an existing PDU Session in order to provide relay services towards 5G ProSe Layer 3 Remote UEs. PDU Sessions supporting 5G ProSe Layer 3 UE to Network Relay shall only be used for 5G ProSe Layer 3 Remote UE relay services.

[0112] The PLMN serving the 5G ProSe Layer 3 UE to the network relay and the PLMN where the 5G ProSe Layer 3 remote UE is registered can be the same PLMN or two different PLMNs.

[0113] [3GPP TS 23.304 V18.2.0 entitled "5G ProSe communication via 5G ProSe layer 3 UE to network relay without N3 IWF" Figure 6 .5.1.1-1 is reproduced as Fig.11 ]

[0114] 1. Service authorization and provisioning are performed as described in clause 6.2 for 5G ProSe Layer 3 UE to Network Relay (step 1a) and 5G ProSe Layer 3 Remote UE (step 1b).

[0115] 2.5G ProSe Layer 3 UE to Network Relay can establish a PDU session for relaying. In the case of IPv6, the 5G ProSe Layer 3 UE to Network Relay obtains the IPv6 prefix from the network via the prefix delegation function as defined in TS 23.501 [4].

[0116] NOTE 1: The 5G ProSe Layer 3 UE to Network Relay may establish a PDU Session for any Relay Service Code it supports before establishing a connection with the 5G ProSe Layer 3 Remote UE.

[0117] 3. The 5G ProSe Layer 3 Remote UE performs discovery of the 5G ProSe Layer 3 UE to the Network Relay as described in clause 6.3.2.3. As part of the discovery procedure, the 5G ProSe Layer 3 Remote UE learns about the connectivity services provided by the 5G ProSe Layer 3 UE to the Network Relay.

[0118] 4. The 5G ProSe Layer 3 Remote UE selects the 5G ProSe Layer 3 UE to Network Relay and establishes a connection for unicast mode communication as described in clause 6.4.3.6. If there is no PDU session associated with the relay service code or a new PDU session for relay is required, the 5G ProSe Layer 3 UE to Network Relay initiates a new PDU session establishment procedure for relay before completing the PC5 connection establishment.

[0119] When the 5G ProSe Layer 3 remote UE sends a direct communication request message containing a dedicated emergency RSC, the 5G ProSe Layer 3 UE to network relay sets up an emergency PDU session for relaying emergency services without establishing an emergency PDU session in step 2.

[0120] NOTE 2: If emergency services of the 5G ProSe layer 3 UE to network relay itself are in progress, how to handle the conflict situation is specified in clause 5.4.4.3.

[0121] The network decides that the PDU session to be established is for relayed traffic, and then generates 5G ProSe Layer 3 UE to Network Relay QoS rules and QoS flow level QoS parameters with relay considerations, and may initiate the setup of the QoS flow, as specified in clause 5.6.2.1. The remote UE may also initiate the setup of the QoS flow by providing PC5 QoS information and (optionally) PC5 QoS rules to the 5G ProSe Layer 3 UE to Network Relay during the connection setup, according to the procedure specified in clause 5.6.2.1.

[0122] 5G ProSe Layer 3 UE to Network Relay determines the PDU Session Type for relay as specified in clause 5.4.1.1.

[0123] Depending on the PDU session type used for relaying, the 5G ProSe layer 3 UE to network relay performs the relay function at the corresponding layer as follows:

[0124] -When IP type PDU session is used for IP traffic over PC5 reference point, the 5G ProSe Layer 3 UE to Network Relay acts as an IP router. For IPv4, the 5G ProSe Layer 3 UE to Network Relay performs IPv4 NAT between the IPv4 address assigned to the 5G ProSe Layer 3 remote UE and the IPv4 address assigned to the PDU session for relayed traffic.

[0125] -When Ethernet type PDU session is used for Ethernet traffic over PC5 reference point, the 5G ProSe Layer 3 UE-to-network relay acts as an Ethernet switch.

[0126] - When an unstructured type PDU session is used for unstructured traffic over the PC5 reference point, the 5G ProSe Layer 3 UE to network relay performs traffic relay based on the mapping between the PC5 link identifier and the PDU session ID and the mapping between the PFI for the PC5 layer 2 link and the QFI for the PDU session. These mappings are created when the unstructured type PDU session is established for the 5G ProSe layer 3 remote UE.

[0127] - When IP type PDU session is used for Ethernet or unstructured traffic over PC5 reference point, 5G ProSe layer 3 UE to network relay uses IP tunneling. For this IP tunneling, 5G ProSe layer 3 UE to network relay locally allocates IP address / prefix for 5G ProSe layer 3 remote UE and is used over Uu reference point to encapsulate and decapsulate uplink and downlink traffic for 5G ProSe layer 3 remote UE. Tunneled traffic over Uu reference point is transported over PC5 reference point as Ethernet or unstructured traffic.

[0128] 5. For IP PDU session type and IP traffic over PC5 reference point, the 5G ProSe Layer 3 remote UE is allocated an IPv6 prefix or IPv4 address (including NAT case) as defined in clause 5.5.1.3.

[0129] 6.5G ProSe Layer 3 Remote UE may provide PC5 QoS information and PC5 QoS rules to the 5G ProSe Layer 3 UE to Network Relay using Layer 2 Link Modification procedures as specified in clause 6.4.3.4. The 5G ProSe Layer 3 UE to Network Relay generates packet filters for use on the Uu interface based on the received PC5 QoS information and QoS rules as described in clause 5.6.2.1 and may perform UE requested PDU session modification as defined in clause 4.3.3 of TS23.502 [5] to set up a new QoS flow or bind a service to an existing QoS flow.

[0130] Uplink and downlink relaying can start from this point. For downlink traffic forwarding, PC5 QoS rules are used to map downlink packets to PC5 QoS flows. For uplink traffic forwarding, 5G QoS rules are used to map uplink packets to Uu QoS flows.

[0131] 7.5G ProSe Layer 3 UE to Network Relay shall send a Remote UE Report (Remote User ID, Remote UE Information) message to the SMF for the PDU Session associated with the relay. The Remote User ID as defined in TS 33.503

[29] is the identification of the 5G ProSe Layer 3 Remote UE user that was successfully connected in step 4. The Remote UE Information is used to assist in identifying the 5G ProSe Layer 3 Remote UE in the 5GC. For IP PDU Session Type, the Remote UE Information is the Remote UE IP Information. For Ethernet PDU Session Type, the Remote UE Information is the Remote UE MAC address detected by the 5G ProSe Layer 3 UE to Network Relay. For Unstructured PDU Session Type, the Remote UE Information is not included. For this PDU Session associated with the relay, the SMF stores the Remote User ID and related Remote UE Information in the SM context of the 5G ProSe Layer 3 UE to Network Relay.

[0132] Remote UE reporting is an N1 SM NAS message sent to the AMF along with the PDU Session ID and then delivered to the SMF.

[0133] NOTE 3: Privacy protection of remote user IDs is specified in TS 33.503

[29] .

[0134] For IP information, the following principles apply:

[0135] - For IPv4, the 5G ProSe Layer 3 UE to Network Relay shall report the TCP / UDP port range assigned to each 5G ProSe Layer 3 remote UE (along with the remote user ID);

[0136] -For IPv6, the 5G ProSe Layer 3 UE to Network Relay shall report the IPv6 prefix assigned to the individual 5G ProSe Layer 3 Remote UE (along with the Remote User ID).

[0137] If a PDU Session for relaying is released by the UE-to-network relay or the network as described in clause 4.3.4 of TS 23.502 [5], the UE-to-network relay shall initiate the release of the Layer 2 link associated with the released PDU Session using the procedure defined in clause 6.4.3.3.

[0138] If the service authorization for acting as a 5G ProSe Layer 3 UE to Network Relay in the serving PLMN is revoked, the PDU session for the relay shall be released as described in section 4.3.4 of TS 23.502 [5] (e.g., by 5G ProSe Layer 3 UE to Network Relay).

[0139] When the 5G ProSe Layer 3 Remote UE is disconnected from the 5G ProSe Layer 3 UE to Network Relay (e.g. after an explicit Layer 2 link release or based on the absence of keep-alive messages on PC5), the 5G ProSe Layer 3 UE to Network Relay shall send a Remote UE Report message to inform the SMF that the 5G ProSe Layer 3 Remote UE has left.

[0140] NOTE 4: In order for the SMF to have 5G ProSe Layer 3 remote UE information, the 5G ProSe Layer 3 UE to the HPLMN and VPLMN where the network relay is authorized to operate needs to support the transmission of 5G ProSe Layer 3 remote UE related parameters when the SMF is in the HPLMN.

[0141] How the 5G ProSe Layer 3 UE to Network Relay releases the PDU session for the relay or removes the QoS flow for the relay when the 5G ProSe Layer 3 remote UE is disconnected from the 5G ProSe Layer 3 UE to Network Relay depends on the 5G ProSe Layer 3 UE to Network Relay implementation.

[0142] […]

[0143] 6.5.1.3 Additional parameter notification procedure

[0144] Figure 6The additional parameter notification procedure outlined in .5.1.3-1 is used by the 5G ProSe Remote UE to request the 5G ProSe UE to relay notification of additional parameters as defined in clause 5.8.3 (for Model A).

[0145] [3GPP TS 23.304 V18.2.0 entitled "Additional parameter notification procedure" Figure 6 .5.1.3-1 Reproduced as Fig.12 ]

[0146] 1.5G ProSe remote UE has discovered 5G ProSe UE to network relay and requires additional parameters.

[0147] The 2.5G ProSe remote UE sends an additional parameter notification request to the 5G ProSe UE to the network relay to obtain additional parameters.

[0148] 3. The 5G ProSe UE to Network Relay acknowledges receipt of the request in step 2 and the Additional Parameters Notification Response (Additional_Parameters_Announcement_Request_Refresh timer). An Additional_Parameters_Announcement_Request_Refresh timer (configurable in the 5G ProSe UE to Network Relay) is provided to the 5G ProSe Remote UE so that when this timer expires, if it still needs to obtain additional parameters, the 5G ProSe Remote UE repeats the Additional Parameters Notification Request procedure. If the 5G ProSe Remote UE does not initiate a new Additional Parameters Notification Request procedure when this Additional_Parameters_Announcement_Request_Refresh timer expires, and no other UE requests additional parameters notification before the Additional_Parameters_Announcement_Request_Refresh timer in the 5G ProSe UE to Network Relay expires, then the relay will stop notifying additional parameters.

[0149] 4.5G ProSe UE to Network Relay notifies the additional parameters by sending a Relay Discovery Additional Information message, as defined in clause 5.8.3. This is repeated periodically with a configurable frequency (usually higher than the frequency related to the Additional_Parameters_Announcement_Request_Refresh timer) until there are no UEs requesting notification of the additional parameters as determined by the Additional_Parameters_Announcement_Request_Refresh timer running in the 5G ProSe UE to Network Relay.

[0150] NOTE: Based on UE implementation, if there are other 5G ProSe Remote UEs that are connected to the 5G ProSe UE to Network Relay but have not requested any additional parameters, the 5G ProSe UE to Network Relay may send the Relay Discovery Additional Information message several times consecutively in step 4. This ensures that other 5G ProSe Remote UEs obtain such additional parameters without invoking any new requests.

[0151] 5.5G ProSe UE to network relay detects new or updated additional parameters.

[0152] 6. The detection of new or updated additional parameters in step 5 triggers the 5G ProSe UE to Network Relay to notify the additional parameters by immediately sending a Relay Discovery Additional Information message, and repeating periodically with a configurable frequency as in step 4 until there is no request to notify the additional parameters, i.e. until the Additional_Parameters_Announcement_Request_Refresh timer in the 5G ProSe UE to Network Relay expires.

[0153] 6.5.2 5G ProSe Communication via 5G ProSe Layer 2 UE to Network Relay

[0154] […]

[0155] 6.5.2.2 Connection Establishment

[0156] [3GPP TS 23.304 V18.2.0 titled "Connection establishment for 5G ProSe layer 2 UE to network relay" Figure 6 .5.2.2-1 is reproduced as Fig.13 ]

[0157] 0. If within coverage, the 5G ProSe Layer 2 Remote UE and the 5G ProSe Layer 2 UE to Network Relay may independently perform initial registration with the network according to the registration procedure in TS 23.502 [5].

[0158] 1. If in coverage, the 5G ProSe Layer 2 Remote UE and the 5G ProSe Layer 2 UE to Network Relay independently obtain service authorization for 5G ProSe Layer 2 UE to Network Relay operation from the network. Service authorization and parameter provisioning for 5G ProSe Layer 2 UE to Network Relay operation are performed for the 5G ProSe Layer 2 UE to Network Relay and the 5G ProSe Layer 2 Remote UE as specified in clause 5.1.4.

[0159] If the 5G ProSe Layer 2 Remote UE is “not served by NG-RAN”, the preconfigured parameters are used and the serving authorization and parameters may be updated after step 6.

[0160] If the 5G ProSe Layer 2 Remote UE has not performed initial registration, the 5G ProSe Layer 2 Remote UE may perform initial registration in step 6.

[0161] 2.5G ProSe Layer 2 Remote UE and 5G ProSe Layer 2 UE to Network Relay perform 5G ProSe UE to Network Relay discovery and selection as specified in clause 6.3.2.3.

[0162] The 3.5G ProSe Layer 2 Remote UE initiates a one-to-one communication connection with the selected 5G ProSe Layer 2 UE to the Network Relay through PC5 using the procedure as described in clause 6.4.3.

[0163] 4. The 5G ProSe Layer 2 Remote UE establishes an RRC connection with the same NG-RAN serving the selected 5G ProSe Layer 2 UE to Network Relay specified in TS 38.300

[12] . The 5G ProSe Layer 2 Remote UE sets the RRC establishment cause as defined in TS 38.331

[16] .

[0164] 5. During step 4, if the 5G ProSe Layer 2 UE to Network Relay is in CM_IDLE state and receives a trigger from the AS layer to enter the CM-CONNECTED state due to the AS layer connection of the remote UE set up with NG-RAN, the 5G ProSe Layer 2 UE to Network Relay performs the service request procedure in clause 4.2.3.2 of TS 23.502 [5].

[0165] 6. The 5G ProSe Layer 2 Remote UE sends a NAS message to the serving AMF. The NAS message is encapsulated in a Uu RRC message sent to the 5G ProSe Layer 2 UE to Network Relay via PC5, and the 5G ProSe Layer 2 UE to Network Relay forwards the Uu RRC message to the NG-RAN specified in TS 38.300

[12] . The NG-RAN selects the serving AMF of the 5G ProSe Layer 2 Remote UE and forwards the NAS message to this AMF.

[0166] If the 5G ProSe Layer 2 Remote UE has not performed an initial registration, the NAS message is an Initial Registration message. Otherwise, the NAS message is either a Service Request message or a Mobility or Periodic Registration message, as specified in TS 38.300

[12] , taking into account the TAI or PC5-RRC message in the RRC container received from the 5G ProSe Layer 2 UE to the Network Relay during Relay Discovery (see clause 5.8.3.3).

[0167] 7.5G ProSe Layer 2 Remote UE may trigger the PDU Session Establishment procedure as defined in clause 4.3.2.2 of TS 23.502 [5].

[0168] 8. Data is transferred between the 5G ProSe Layer 2 Remote UE and the UPF via the 5G ProSe Layer 2 UE to Network Relay and NG-RAN. The 5G ProSe Layer 2 UE to Network Relay forwards all data messages between the 5G ProSe Layer 2 Remote UE and the NG-RAN as specified in TS 38.300

[12] .

[0169] 3GPP TS 38.300 specifies the procedures related to UE to network relay as follows:

[0170] 16.12 Sidelink Relay

[0171] 16.12.1 Overview

[0172] Sidelink relay is introduced to support 5G ProSe UE to Network Relay (U2N Relay) functionality (specified in TS23.304

[48] ) to provide connectivity to the network for U2N remote UEs. Both L2 and L3 U2N relay architectures are supported. The L3 U2N relay architecture is transparent to the serving NG-RAN of the U2N relay UE, except for controlling the sidelink resources. The detailed architecture and procedures for L3 U2N relay can be found in TS23.304

[48] .

[0173] A U2N relay UE should be in RRC_CONNECTED to perform relay of unicast data.

[0174] For L2 U2N relay operation, the following RRC state combinations are supported:

[0175] - Both the L2 U2N relay UE and the L2 U2N remote UE should be in RRC_CONNECTED to perform transmission / reception of relayed unicast data; and

[0176] - The L2 U2N relay UE may be in RRC_IDLE, RRC_INACTIVE or RRC_CONNECTED as long as all L2 U2N remote UEs connected to the L2 U2N relay UE are in RRC_INACTIVE or RRC_IDLE.

[0177] A single unicast link is established between one L2 U2N relay UE and one L2 U2N remote UE. Traffic from the NG-RAN to the L2 U2N remote UE via a given L2 U2N relay UE and traffic from the L2 U2N relay UE should be separated in different Uu RLC channels.

[0178] For L2 U2N relay, the L2 U2N remote UE may only be configured to use resource allocation mode 2 (as specified in 5.7.2 and 16.9.3.1) for relaying data.

[0179] […]

[0180] 16.12.3 Relay Discovery

[0181] Model A and Model B discovery models as defined in TS 23.304

[48] are supported for U2N relay discovery. The protocol stack for discovery is shown in Fig.16 .12.3-1.

[0182] […]

[0183] The U2N remote UE may perform relay discovery message transmission (i.e., as specified in TS 23.304

[48] ) and may listen to the sidelink of relay discovery messages while in RRC_IDLE, RRC_INACTIVE, or RRC_CONNECTED. The network may broadcast or configure, via dedicated RRC signaling, a Uu RSRP threshold that the U2N remote UE uses to determine whether it may transmit a relay discovery message to the U2N relay UE.

[0184] A U2N relay UE may perform relay discovery message transmission (i.e., as specified in TS 23.304

[48] ) and may listen to the sidelink for relay discovery messages while in RRC_IDLE, RRC_INACTIVE, or RRC_CONNECTED. The network may broadcast or configure, via dedicated RRC signaling, a maximum Uu RSRP threshold, a minimum Uu RSRP threshold, or both, which the U2N relay UE uses to determine whether it may transmit a relay discovery message to a U2N remote UE.

[0185] The network may provide relay discovery configuration using broadcast or dedicated signaling. In addition, U2N remote UEs and L3 U2N relay UEs may use pre-configuration for relay discovery.

[0186] Resource pools for NR side link communications can be used for relay discovery or the network can configure resource pools dedicated to relay discovery. Resource pools dedicated to relay discovery can be configured simultaneously with resource pools used for NR side link communications in system information, dedicated signaling, and / or pre-configuration. Whether dedicated resource pools for relay discovery are configured is based on the network implementation plan. If resource pools dedicated to relay discovery are configured, only those resource pools dedicated to relay discovery are applied to relay discovery. If only resource pools for NR side link communications are configured, all configured resource pools can be used for relay discovery and NR side link communications.

[0187] For a U2N remote UE that has been connected to the network by a U2N relay UE (including both in-coverage and out-of-coverage situations), only resource allocation mode 2 is used for relay discovery message transmission.

[0188] For in-coverage U2N relay UEs, and for both in-coverage and out-of-coverage U2N remote UEs, the NR sidelink resource allocation principle is applied for relay discovery messaging.

[0189] The sidelink power control for transmission of relay discovery messages is the same as the sidelink power control used for NR sidelink communication.

[0190] Ciphering or integrity protection in the PDCP layer shall not be used for the Relay Discovery Message.

[0191] U2N remote UE and U2N relay UE can determine whether the gNB supports relay discovery, non-relay discovery, or both based on SIB12.

[0192] 16.12.4 Relay Selection / Reselection

[0193] The U2N remote UE performs radio measurements at the PC5 interface and uses them together with the higher layer criteria as specified in TS 23.304

[48] for U2N relay selection and reselection. When there is no unicast PC5 connection between the U2N relay UE and the U2N remote UE, the U2N remote UE uses SD-RSRP measurements to evaluate whether the PC5 link quality for the U2N relay UE meets the relay selection criteria.

[0194] For relay reselection, when there is data transmission from the U2N relay UE to the U2N remote UE, the U2N remote UE uses SL-RSRP measurement for the serving U2N relay UE for relay reselection trigger evaluation, and in the absence of data transmission from the U2N relay UE to the U2N remote UE, it will depend on the UE implementation to decide whether to use SL-RSRP or SD-RSRP for relay reselection trigger evaluation.

[0195] If the PC5 link quality measured by the U2N Remote UE for the U2N Relay UE exceeds a configured threshold (pre-configured or provided by the gNB), the U2N Remote UE considers the U2N Relay UE to be suitable for radio measurement. The U2N Remote UE retrieves suitable U2N Relay UE candidates that meet all AS layer and higher layer criteria (see TS 23.304

[48] ). If there are multiple such candidate U2N Relay UEs, it is up to the U2N Remote UE implementation to select one of them. For L2 U2N Relay selection (reselection), PLMN ID and Cell ID can be used as additional AS criteria.

[0196] The U2N remote UE triggers the U2N relay selection in the following cases:

[0197] -The direct Uu signal strength of the current serving cell of the U2N remote UE is below the configured signal strength threshold;

[0198] - Indicated by upper layers of the U2N remote UE.

[0199] U2N remote UE can trigger U2N relay reselection in the following cases:

[0200] -The current PC5 signal strength of the U2N relay UE is lower than the (pre-)configured signal strength threshold;

[0201] - Cell reselection, handover, Uu RLF or Uu RRC connection establishment / recovery failure has been indicated by the U2N relay UE via PC5-RRC signaling;

[0202] -When the U2N remote UE receives a PC5-S link release message from the U2N relay UE;

[0203] -When the U2N remote UE detects PC5 RLF;

[0204] -Instructed by upper layer.

[0205] For L2 U2N Remote UE and L3 U2N Remote UE in RRC_IDLE or RRC_INACTIVE, the cell selection (reselection) procedure and the relay selection (reselection) procedure run independently. If both a suitable cell and a suitable U2N Relay UE are available, it depends on the U2N Remote UE implementation to select the cell or the U2N Relay UE. The L3 U2N Remote UE may select both the cell and the L3 U2N Relay UE at the same time, and this depends on the implementation of the L3 U2N Remote UE.

[0206] For both L2 and L3 U2N relay UEs in RRC_IDLE or RRC_INACTIVE, PC5-RRC message is used to notify its connected U2N remote UEs when the U2N relay UE selects a new cell. PC5-RRC message is also used to notify its connected L2 or L3 U2N remote UEs when the L2 or L3 U2N relay UE performs handover, detects Uu RLF or its Uu RRC connection establishment / recovery fails. After receiving the PC5 RRC message for notification, it is up to the U2N remote UE implementation to decide whether to release or maintain the unicast PC5 link. If the U2N remote UE decides to release the unicast PC5 link, it triggers the PC5 release procedure and may perform cell or relay reselection.

[0207] 16.12.5 Control Plane Procedures for L2 U2N Relay

[0208] 16.12.5.1RRC Connection Management

[0209] L2 U2N remote UE needs to establish its own PDU session / DRB with the network before user plane data transfer.

[0210] The NR sidelink PC5 unicast link establishment procedure may be used to set up a secure unicast link between the L2 U2N remote UE and the L2 U2N relay UE before the L2 U2N remote UE establishes a Uu RRC connection with the network via the L2 U2N relay UE.

[0211] The establishment of Uu SRB1 / SRB2 and DRB for L2 U2N remote UE is subject to Uu configuration procedure for L2 UE to network relay.

[0212] Fig.16 The following high-level connection establishment procedure in .12.5.1-1 applies to L2 U2N Relay and L2 U2N Remote UE:

[0213] [3GPP TS 38.300 V17.5.0 entitled "Procedures for L2 U2N Remote UE Connection Establishment" Fig.16 .12.5.1-1 reproduced as Fig.14 ]

[0214] 1. The L2 U2N Remote and L2 U2N Relay UEs perform a discovery procedure and establish a PC5-RRC connection using the NR sidelink PC5 unicast link establishment procedure.

[0215] 2. The L2 U2N Remote UE sends a first RRC message (i.e., RRCSetupRequest) for its connection establishment with the gNB via the L2 U2N Relay UE using the designated PC5 Relay RLC channel configuration. If the L2 U2N Relay UE is not in RRC_CONNECTED, it needs to perform its own Uu RRC connection establishment upon receiving the message on the designated PC5 Relay RLC channel. After the RRC connection establishment procedure of the L2 U2N Relay UE, the gNB configures the SRB0 Relay Uu Relay RLC channel to the U2N Relay UE. The gNB responds to the L2 U2N Remote UE with an RRCSetup message. The RRCSetup message is sent to the L2 U2N Remote UE using the SRB0 Relay Uu Relay channel on Uu and the designated PC5 Relay RLC channel on PC5.

[0216] Note 1: Empty.

[0217] 3. The gNB and L2 U2N relay UE perform the relay channel establishment procedure over Uu. Based on the configuration from the gNB, the L2U2N relay / remote UE establishes the PC5 relay RLC channel for relaying of SRB1 over PC5 towards the L2 U2N remote / relay UE.

[0218] 4. An RRCSetupComplete message is sent by the L2 U2N Remote UE to the gNB via the L2 U2N Relay UE using the SRB1 Relay channel on PC5 and the SRB1 Relay channel on Uu configured to the L2 U2N Relay UE. The L2 U2N Remote UE is then in RRC_CONNECTED as if the gNB were.

[0219] 5. The L2 U2N Remote UE and gNB follow the Uu Security Mode procedures to establish security and the security messages are forwarded via the L2 U2N Relay UE.

[0220] 6. The gNB sends an RRCReconfiguration message to the L2 U2N Remote UE via the L2 U2N Relay UE to set up the end-to-end SRB2 / DRB of the L2 U2N Remote UE. The L2 U2N Remote UE sends an RRCReconfigurationComplete message to the gNB via the L2 U2N Relay UE as a response. In addition, the gNB may configure an additional Uu relay RLC channel between the gNB and the L2 U2N Relay UE, and a PC5 relay RLC channel between the L2 U2N Relay UE and the L2 U2N Remote UE for relay services.

[0221] […]

[0222] 16.12.6 Service Continuity for L2 U2N Relay

[0223] 16.12.6.0 Overview

[0224] The service continuity procedure is applicable only for the mobility cases of path switching from indirect to direct path and from direct to indirect path when the L2 U2N Remote UE and the L2 U2N Relay UE belong to the same gNB.

[0225] 16.12.6.1 Switching from Indirect to Direct Path

[0226] For service continuity over L2 U2N relay, the following procedure is used in case the L2 U2N remote UE switches to direct path:

[0227] [3GPP TS 38.300 V17.5.0 entitled "Procedure for L2 U2N remote UE handover to direct Uu cell" Fig.16 .12.6.1-1 Reproduced as Fig.15 ]

[0228] 1. Perform Uu measurement configuration and measurement report signaling procedures to evaluate both relay link measurements and Uu link measurements. Report measurement results from L2 U2N remote UEs when configured reporting criteria are met. The sidelink relay measurement report will contain at least the source L2 ID of the L2 U2N relay UE, the serving cell ID (i.e., NCGI / NCI) and the sidelink measurement quantity results. The sidelink measurement quantity may be the SL-RSRP of the serving L2 U2N relay UE, and if SL-RSRP is not available, SD-RSRP is used.

[0229] 2. The gNB decides to switch the L2 U2N remote UE to the direct Uu path.

[0230] 3. The gNB sends an RRCReconfiguration message to the L2 U2N remote UE. The L2 U2N remote UE stops the user plane and control plane transmission via the L2 U2N relay UE after receiving the RRCReconfiguration message with the path switch configuration.

[0231] 4. The L2 U2N remote UE synchronizes with the gNB and performs random access.

[0232] 5. The UE (i.e., the L2 U2N remote UE in the previous step) sends an RRCReconfigurationComplete message to the gNB via a direct path using the configuration provided in the RRCReconfiguration message. According to this step, the UE (i.e., the L2 U2N remote UE in the previous step) uses an RRC connection to the gNB via a direct path.

[0233] 6. The gNB sends an RRCReconfiguration message to the L2 U2N relay UE to reconfigure the connection between the L2 U2N relay UE and the gNB. The RRCReconfiguration message may be sent to the L2 U2N relay UE at any time after step 3 based on the gNB implementation (e.g., to release the Uu relay RLC channel and PC5 relay RLC channel configuration for relaying, and the bearer mapping configuration associated with the L2 U2N remote UE).

[0234] 7. The AS layer of the L2 U2N relay UE or L2 U2N remote UE instructs the upper layer to release the PC5 unicast link after receiving the RRCReconfiguration message from the gNB. The timing of performing the link release depends on the UE implementation.

[0235] 8. The data path is switched from an indirect path to a direct path between the UE (i.e., the previous L2 U2N Remote UE) and the gNB. If configured by the gNB, PDCP re-establishment or PDCP data recovery in uplink is performed by the UE (i.e., the previous L2 U2N Remote UE) for lossless delivery during the path switch.

[0236] Note: Step 8 can be performed at any time after Step 4. Step 8 is independent of Step 6 and Step 7.

[0237] 16.12.6.2 Switching from direct to indirect paths

[0238] The gNB may select a L2U2N relay UE in any RRC state, i.e., RRC_IDLE, RRC_INACTIVE, or RRC_CONNECTED, as the target L2 U2N relay UE for direct to indirect path handover.

[0239] For service continuity of L2 U2N remote UE, in case the L2 U2N remote UE switches to an indirect path via a L2U2N relay UE in RRC_CONNECTED, the following procedure is used:

[0240] [3GPP TS 38.300 V17.5.0 entitled "Procedure for L2 U2N Remote UE to switch to indirect path via L2 U2N Relay UE in RRC_CONNECTED" Fig.16 .12.6.2-1 Reproduced as Fig.16 ]

[0241] 1. The L2 U2N remote UE reports one or more candidate L2 U2N relay UEs and Uu measurement values ​​after it measures / discovers the candidate L2 U2N relay UEs:

[0242] - The L2 U2N remote UE filters appropriate L2 U2N relay UEs according to the relay selection criteria before reporting. The L2 U2N remote UE shall only report L2 U2N relay UE candidates that meet the higher layer criteria;

[0243] -The report contains at least the L2 U2N relay UE ID, the serving cell ID of the L2 U2N relay UE and the sidelink measurement quantity information. SD-RSRP is used as the sidelink measurement quantity.

[0244] 2. The gNB decides to handover the L2 U2N remote UE to the target L2 U2N relay UE. The gNB then sends an RRCReconfiguration message to the target L2 U2N relay UE, which contains at least the local ID and L2 ID of the L2 U2N remote UE, the Uu relay RLC channel and PC5 relay RLC channel configuration for relaying, and the bearer mapping configuration.

[0245] 3. The gNB sends an RRCReconfiguration message to the L2 U2N remote UE. The RRCReconfiguration message contains at least the L2 U2N relay UE ID, the local ID of the remote UE, the PC5 relay RLC channel configuration for the relay service, and the associated end-to-end Uu radio bearers. The L2 U2N remote UE stops the user plane and control plane transmission via the direct path after receiving the RRCReconfiguration message from the gNB.

[0246] 4. The L2 U2N remote UE establishes a PC5 RRC connection with the target L2 U2N relay UE.

[0247] 5. The L2 U2N remote UE completes the path switching procedure by sending an RRCReconfigurationComplete message to the gNB via the L2 U2N relay UE.

[0248] 6. The data path is switched from a direct path to an indirect path between the L2 U2N remote UE and the gNB.

[0249] In the case that the selected L2 U2N relay UE for direct to indirect path switching is in RRC_IDLE or RRC_INACTIVE, after receiving the path switch command, the L2 U2N remote UE establishes a PC5 link with the L2 U2N relay UE and sends an RRCReconfigurationComplete message via the L2 U2N relay UE, which triggers the L2 U2N relay UE to enter the RRC_CONNECTED state. Fig.16 The procedure in .12.6.2-1 for L2 U2N remote UE switching to indirect path may also be applied when the selected L2 U2N relay UE for direct to indirect path switching is in RRC_IDLE or RRC_INACTIVE, except that the RRCReconfiguration message is sent from the gNB to the L2 U2N relay UE after the L2 U2N relay UE enters the RRC_CONNECTED state, which occurs during step 5.

[0250] 3GPP TS22.261 specifies the connectivity model and KPIs for UE to network relay in 5G systems as follows:

[0251] 6.9 Connectivity Model

[0252] 6.9.1 Description

[0253] A UE (remote UE) can be connected directly to the network (direct network connection), connected using another UE as a relay UE (indirect network connection), or connected using both direct and indirect connections. Relay UEs can be used in many different scenarios and verticals (inHome, SmartFarming, SmartFactories, public safety, etc.). In these cases, the use of relay UEs can be used to improve the energy efficiency and coverage of the system.

[0254] The remote UE can be anything from a simple wearable, such as a sensor embedded in clothing, to a more complex wearable UE listening to biometrics. It can also be a non-wearable UE communicating in a personal area network, such as a group of home appliances (e.g., a smart thermostat and input keys), or an electronic UE in an office environment (e.g., a smart printer), or a smart flower pot that can be remotely activated to water a plant.

[0255] When a remote UE attempts to establish an indirect network connection, there may be several available relay UEs in the vicinity, and a procedure for selecting a suitable relay UE among the available relay UEs needs to be supported.

[0256] Indirect network connection covers the use of relay UEs for connecting remote UEs to the 3GPP network. There may be one or more relay UEs (more than one hop) between the network and the remote UE.

[0257] The ProSe Inter-UE Relay may also be used to connect two remote Public Safety UEs using a direct device connection.There may be one or more ProSe Inter-UE Relays (more than one hop) between two remote Public Safety UEs.

[0258] 6.9.2 Requirements

[0259] The following set of requirements supplements the requirements listed in 3GPP TS 22.278 [5], clauses 7B and 7C.

[0260] 6.9.2.1 Overview

[0261] The 5G system will support the use of one or more relay UEs to relay services between remote UEs and gNBs.

[0262] The 5G system will support the same traffic flow of remote UEs to be relayed via different indirect network connection paths.

[0263] The 5G system will support different service flows of remote UEs to be relayed via different indirect network connection paths.

[0264] The connection between the remote UE and the relay UE will be able to use 3GPP RAT or non-3GPP RAT and use licensed or unlicensed frequency bands.

[0265] The connection between the remote UE and the relay UE will be able to use fixed broadband technology.

[0266] When the remote UE and the relay UE subscribe to different PLMNs and both PLMNs have roaming agreements with the VPLMN, the 5G system will support the indirect network connection mode in the VPLMN.

[0267] The 5G system will be able to support UEs using simultaneous indirect and direct network connection modes.

[0268] When using relay UEs, network operators will be able to define the maximum number of hops supported in their network.

[0269] The 5G system will be able to manage communications between remote UEs and the 5G network across multi-path indirect network connections.

[0270] 6.9.2.2 Services and service continuity

[0271] The 5G system will be able to support all types of services for indirect network connection modes, such as voice, data, IoT small data, multimedia, and MCX.

[0272] The 5G system will be able to support QoS for user service sessions between remote UEs and the network using 3GPP access technologies.

[0273] 5G systems will be able to provide an indication to a remote UE (alternatively, an authorized user) about the quality of the currently available indirect network connection paths.

[0274] The 5G system will be able to maintain service continuity for the remote UE's indirect network connection when the communication path to the network changes (i.e., change of one or more of the relay UEs, change of gNB).

[0275] Note: This does not apply to traffic flows of remote UEs using different indirect network connection paths.

[0276] 6.9.2.3 Permission and Authorization

[0277] The 5G system will enable network operators to authorize UEs to use indirect network connections. Authorization will be able to be restricted to only use relay UEs belonging to the same network operator. Authorization should be able to be restricted to only relay UEs belonging to the same application layer group.

[0278] The 5G system will enable network operators to authorize a UE to relay services as a relay UE. Authorization will be able to allow relaying only for remote UEs belonging to the same network operator. Authorization will be able to allow relaying only for remote UEs belonging to the same application layer group.

[0279] The 5G system will support a mechanism for the end user to provide / revoke permission for an authorized UE to act as a relay UE.

[0280] The 5G system will support a mechanism for an authorized third party to provide / revoke permission for an authorized UE to act as a relay UE.

[0281] The 5G system will provide suitable APIs through which an authorized third party will be able to authorize (multiple) UEs to act as relay UEs or remote UEs under the control of the third party.

[0282] The 5G system will provide suitable APIs through which an authorized third party will be able to enable / deactivate (multiple) UEs to act as relay UEs or remote UEs under the control of the third party.

[0283] 6.9.2.4 Relay UE Selection

[0284] The 3GPP system will support the selection and reselection of relay UEs based on a combination of different criteria, e.g.

[0285] - the characteristics of the traffic intended to be relayed (e.g. expected message frequency and required QoS),

[0286] - Subscriptions of the relay UE and the remote UE,

[0287] - Capabilities / capacity / coverage when using relay UEs,

[0288] - the QoS achievable by selecting the relay UE,

[0289] - the power consumption required by the relay UE and the remote UE,

[0290] - Pre-paired relay UE,

[0291] - 3GPP or non-3GPP access relay UE uses to connect to the network,

[0292] - the 3GPP network to which the relay UE is connected (directly or indirectly),

[0293] - Overall optimization of power consumption / performance of 3GPP systems, or

[0294] -Battery capacity and battery life of the relay UE and remote UE.

[0295] NOTE: Reselection may be triggered by any dynamic change in the selection criteria, e.g. by battery exhaustion of the relay UE, a new relay available UE coming within range, a remote UE requesting additional resources or higher QoS, etc.

[0296] 3GPP TS23.304 introduces UE-to-network relay (U2N) in Release 18. For single-hop U2N relay, U2N relay can be used to support data communication between the remote UE and the network when the remote UE cannot communicate directly with the network. U2N relay needs to establish a PC5 unicast link (or PC5 radio resource control (RRC) connection) with the remote UE and establish an RRC connection with a network node (e.g., gNB) to support data communication between the remote UE and the network. According to 3GPP TS22.261, multi-hop U2N relay can be supported in Release 19. Fig.17 An exemplary 3-hop U2N relay is shown. Also, when using relay UEs, network operators will be able to define the maximum number of hops supported in their network.

[0297] Considering that the more hops are used, the more delay is incurred, it is not appropriate for the network to configure one value of the maximum number of hops for services with different QoS requirements. Therefore, it is advantageous for the network to configure the maximum number of hops on a service basis. For example, the network may provide the maximum number of hops for each (ProSe) Relay Service Code (RSC) to the relay UE in order to limit the maximum number of hops for a multi-hop U2N relay, where the RSC indicates the connectivity service provided by the U2N relay to the remote UE. Alternatively, the network may provide a mapping of the maximum number of hops to the (ProSe) RSC to the relay UE. In one embodiment, each RSC may be associated with one or more PDU sessions.

[0298] As described in 3GPP TS23.304, the remote UE may perform a discovery procedure to find a U2N relay and then establish a PC5 unicast link with the U2N relay in order to access the network via the U2N relay. According to 3GPP TS 38.300, the U2N relay UE may perform relay discovery messaging and may listen to the side link for relay discovery messaging when in RRC_IDLE, RRC_INACTIVE, or RRC_CONNECTED. In other words, the U2N relay UE should be within the coverage (IC) of the network in order to perform relay discovery messaging, and the U2N relay UE out of coverage (OOC) is not allowed to perform relay discovery messaging because the remote UE cannot access the network via the OOC U2N relay UE.

[0299] To support multi-hop U2N relaying, it is not necessary for all relays involved in the multi-hop U2N relaying to be within the coverage area (IC) of the network. Fig.17For example, it is sufficient that Relay 3 is in coverage (IC), and the other relays (i.e., Relay 1 and Relay 2) may be out of coverage (OOC). In order to allow the remote UE to find Relay 3 (which is an IC relay), Relay 3 may initiate UE-to-network relay discovery with model A by transmitting or broadcasting a U2N Relay Discovery Notification message including a cumulative hop count of 1. Upon receiving the U2N Relay Discovery Notification message from Relay 3, Relay 2 may transmit or broadcast a new U2N Relay Discovery Notification message including a cumulative hop count of 2. Similarly, Relay 1 may transmit or broadcast another U2N Relay Discovery Notification message including a cumulative hop count of 3 in response to receiving the U2N Relay Discovery Notification message from Relay 2. After receiving the U2N Relay Discovery Notification message from Relay 1, the remote UE may then establish a PC5 unicast link (or PC5 RRC connection) with Relay 1. A PC5 unicast link may also be established between Relay 1 and Relay 2 and between Relay 2 and Relay 3, so that remote UEs can access the network via Relay 1, Relay 2, and Relay 3. In this example, it is assumed that the maximum number of hops is greater than three.

[0300] Fig.18 An exemplary multi-route UE to network relay is shown. Fig.18 As shown in , for a remote UE, there may be multiple routes to reach the network via different relay UEs. Respectively, route A has 3 hops, and route B has 2 hops. In this case, it is beneficial to consider the cumulative number of hops for relay UE (or route) selection in terms of the transmission delay of the remote UE. For example, the remote UE may select relay 4 (i.e., route B) for communication with the network. In other words, the remote UE may select a relay UE indicating fewer (or smaller) cumulative hops, and the remote UE may be connected to the network via the relay UE. The remote UE may then transmit a direct communication request message to the selected relay UE for establishing a PC5 unicast link (or PC5RRC connection) with the selected relay UE. For relay UE selection, other factors such as the signal strength (e.g., RSRP) of the relay UE may also be considered. After a PC5 unicast link (or PC5 RRC connection) has been established between the remote UE and relay 4 and between relay 4 and relay 5, the remote UE may then establish an RRC connection with the network via relay 4 and relay 5. This applies to the case where the remote UE is initially out of network coverage (OOC) and attempts to discover a relay UE for connection with the network.

[0301] When a remote UE initiates UE-to-network relay discovery with model B to find a relay within coverage, the remote UE may transmit or broadcast a U2N relay discovery solicitation message. When a U2N relay discovery solicitation message is received from a remote UE, the relay UE may transmit or broadcast a new U2N relay discovery solicitation message including a cumulative hop count of 1, so as to implement the maximum hop count limit configured by the network. The following relay UE may also transmit or broadcast other U2N relay discovery solicitation messages including an increased cumulative hop count until the maximum hop count has been reached or the relay UE is within coverage (IC) of the network. For example, when a U2N relay discovery solicitation message is received from other relay UEs, if the relay UE is within coverage (IC) of the network, the relay UE may reply with a new U2N relay discovery response message. Otherwise, if the relay UE is out of coverage (OOC) of the network and the maximum hop count has not been reached (i.e., the cumulative hop count plus 1 included in the received U2N Relay Discovery Solicitation message is less than or equal to the maximum hop count), the relay UE may transmit or broadcast another U2N Relay Discovery Solicitation message.

[0302] As discussed above, the remote UE may select a relay route / path for accessing the network based on the cumulative hop count associated with each relay route / path. To support this, the relay UEs within coverage (IC) need to include the final cumulative hop count in the U2N relay discovery response message. When receiving the U2N relay discovery response message from the relay UE, those intermediate relay UEs may also include the final cumulative hop count in the new U2N relay discovery response message. As a result, the remote UE may receive the final cumulative hop count in the U2N relay discovery response message sent from the neighboring relay UE. Fig.19 An example of multi-hop UE to network relay discovery with Model B is shown. Fig.19 In the example shown in , the final cumulative hop count is 3.

[0303] Alternatively, the IC relay UE may (re)initialize the cumulative hop count with 1 and include it in the U2N relay discovery response message. Each subsequent relay UE may increase the received cumulative hop count by 1. As a result, the remote UE will also receive a final cumulative hop count of 3 from the neighboring relay UE.

[0304] In the case that there may be multiple ongoing UE-to-network relay discovery procedures during the same time period, the above-mentioned U2N relay discovery solicitation message or U2N relay discovery response message may include the user information ID of the remote UE.

[0305] To support switching between direct and indirect paths, the remote UE needs to report the measurement results of the candidate relay UEs to the gNB so that the gNB can select the target relay UE for path switching. The measurement report message may include at least the L2 U2N relay UE ID, the serving cell ID of the L2 U2N relay UE (e.g., NCGI / NCI), and the sidelink measurement quantity information (e.g., RSRP).

[0306] Fig. 20 An exemplary remote UE measurement report with Model A is shown. Fig. 20 In the case of a multi-hop U2N relay as shown in , it is presumed that measurements may be performed on a relay UE (e.g., Relay 1) adjacent to a remote UE, and the L2 ID and the serving cell ID may belong to the relay UE connected to the gNB (e.g., Relay 3). Therefore, Relay 3 needs to send its L2 ID and the serving cell ID to the remote UE via intermediate relay UEs (e.g., Relay 1 and Relay 2) during the discovery procedure. Relay 3 may send its L2 ID and the serving cell ID in a U2N Relay Discovery message (e.g., a U2N Relay Discovery Notification message for Model A or a U2N Relay Discovery Response message for Model B). For Relay 3, it is also feasible to send these two pieces of information to the remote UE using other PC5-S messages or PC5-RRC messages after the discovery procedure. Alternatively, the L2 ID and the serving cell ID may be transmitted in two different messages. For example, the serving cell ID may be transmitted in a U2N Relay Discovery Notification message or a U2N Relay Discovery Response message, and the L2 ID may be transmitted in a Relay Discovery Additional Information message or a PC5-RRC message. And, the L2 ID may be forwarded to the remote UE in another relay discovery additional information message or another PC5-RRC message by the intermediate relay UE. In addition, another identifier of relay 3 (e.g., user information ID or C-RNTI) may be used to replace the L2 ID. Preferably, the remote UE may send an additional parameter notification request to relay 3 via the intermediate relays (i.e., relay 1 and relay 2) to request the L2 ID of relay 3.

[0307] In general, measurement results of multiple candidate relay UEs may be reported by the remote UE, and thus there may be multiple entries of candidate relay UE information. Each entry may include a measurement result, a layer 2 ID of the candidate relay UE, and an ID of a serving cell of the candidate relay UE. After receiving the measurement report from the remote UE, the gNB may then determine the target relay UE for path switching and send an RRC reconfiguration message indicating the target relay UE to the remote UE. In one embodiment, the RRC reconfiguration message may include information indicating the target relay UE (e.g., an entry index or L2 ID of the target relay UE), a local ID of the remote UE, a PC5 relay RLC channel configuration for relay services, and / or associated end-to-end Uu radio bearers. The remote UE may then connect to the target relay UE and the intermediate relay UE in the relay path involved for switching to an indirect path. Furthermore, the gNB needs to send another RRC reconfiguration message to inform the target relay UE of the path switch. In one embodiment, the RRC reconfiguration message may include the L2 ID of the remote UE, the local ID of the remote UE, the Uu relay RLC channel and PC5 relay RLC channel configuration for relaying, and / or bearer mapping configuration.

[0308] On the other hand, it is beneficial to take into account the (cumulative) number of hops involved in the multi-hop U2N relay in terms of the QoS requirements of the gNB when selecting a target relay UE for the remote UE. To achieve this, the remote UE is required to include the (cumulative) number of hops involved in the multi-hop U2N relay and associated with each candidate relay UE in the measurement report message sent to the gNB.

[0309] Fig.21 Flowchart 2100 of a method for UE-to-network relay discovery. In step 2105, the second relay UE receives a first U2N relay discovery message from the first relay UE, wherein the first U2N relay discovery message includes a user information identifier (ID) of the first relay UE, a layer 2 ID of a third relay UE, and an ID of a serving cell of the third relay UE. In step 2110, the second relay UE transmits a second U2N relay discovery message to a remote UE, wherein the second U2N relay discovery message includes the user information ID of the second relay UE, the layer 2 ID of the third relay UE, and an ID of a serving cell.

[0310] In one embodiment, the third relay UE may be the same as or different from the first relay UE. In the case where the third relay UE is the same as the first relay UE, this means that there are two U2N relays between the remote UE and the network (in the relay path).

[0311] In one embodiment, the first U2N relay discovery message may include a first cumulative hop count. The second U2N relay discovery message may include a second cumulative hop count. The second cumulative hop count may be equal to the first cumulative hop count plus 1.

[0312] In one embodiment, the first U2N relay discovery message may include a user information ID and / or a relay service code (RSC) of the remote UE. The second U2N relay discovery message may include a user information ID and / or an RSC of the remote UE.

[0313] In one embodiment, the first U2N relay discovery message or the second U2N relay discovery message may be a U2N relay discovery notification message. The first U2N relay discovery message or the second U2N relay discovery message may be a U2N relay discovery response message.

[0314] Return to reference Figure 3 and Figure 4 , in an exemplary embodiment from the perspective of the second relay UE. The second relay UE 300 includes a program code 312 stored in the memory 310. The CPU 308 can execute the program code 312 to enable the second relay UE to: (i) receive a first U2N relay discovery message from the first relay UE, wherein the first U2N relay discovery message includes the user information ID of the first relay UE, the layer 2 ID of the third relay UE, and the ID of the serving cell of the third relay UE; and (ii) transmit a second U2N relay discovery message to the remote UE, wherein the second U2N relay discovery message includes the user information ID of the second relay UE and the layer 2 ID of the third relay UE and the ID of the serving cell. In addition, the CPU 308 can execute the program code 312 to perform all of the above actions and steps or other actions and steps described herein.

[0315] Various aspects of the present disclosure have been described above. It should be understood that the teachings herein can be embodied in a wide variety of forms, and any specific structure, function, or both disclosed herein are only representative. Based on the teachings herein, it should be understood by those skilled in the art 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 described herein can be used to implement a device or practice a method. In addition, other structures, functions, or structures and functions different from the aspects described in addition to one or more aspects described herein can be used to implement such devices or practice such methods. As an example of some of the above concepts, in some aspects, parallel channels can be established based on pulse repetition frequencies. In some aspects, parallel channels can be established based on pulse positions or offsets. In some aspects, parallel channels can be established based on time hopping sequences. In some aspects, parallel channels can be established based on pulse repetition frequencies, pulse positions or offsets, and time hopping sequences.

[0316] Those skilled in the art will understand that information and signals may be represented using any of a variety of different technologies and techniques. For example, data, instructions, commands, information, signals, bits, symbols, and chips that may be referenced throughout the above description may be represented by voltage, current, electromagnetic waves, magnetic fields or particles, optical fields or particles, or any combination thereof.

[0317] Those skilled in the art will further appreciate that the various illustrative logical blocks, modules, processors, components, circuits, and algorithm steps described in conjunction with the aspects disclosed herein may be implemented as electronic hardware (e.g., digital implementations, analog implementations, or a combination of both, which may be designed using source decoding or some other techniques), and various forms of programs or design codes with instructions (for convenience, which may be referred to herein as "software" or "software modules"), or a combination of both. To clearly illustrate this interchangeability of hardware and software, various illustrative components, blocks, modules, circuits, and steps have been described above generally in terms of their functions. Whether such functions are implemented as hardware or software depends on the specific application and the design constraints imposed on the overall system. Those skilled in the art may implement the described functions in different ways for each specific application, but such implementation decisions should not be interpreted as causing a departure from the scope of the present disclosure.

[0318] In addition, the various illustrative logical blocks, modules, and circuits described in conjunction with the aspects disclosed herein may be implemented within or performed by an integrated circuit ("IC"), an access terminal, or an 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 in the alternative, the processor may be any conventional processor, controller, microcontroller, or state machine. A processor may also be implemented as a combination of computing devices, for example, a combination of a DSP and a microprocessor, a plurality of microprocessors, one or more microprocessors in conjunction with a DSP core, or any other such configuration.

[0319] It should be understood that any specific order or hierarchy of steps in any disclosed process is an example of an exemplary method. It should be understood that based on design preferences, the specific order or hierarchy of steps in a process can be rearranged while remaining within the scope of the present disclosure. The accompanying method claims present elements of the various steps in an exemplary order and are not meant to be limited to the specific order or hierarchy presented.

[0320] The steps of the method or algorithm described in conjunction with the various aspects disclosed herein may be implemented directly in hardware, software modules executed by a processor, or a combination of the two. Software modules (e.g., including executable instructions and related data) and other data may reside in a data memory, such as a RAM memory, a flash memory, a ROM memory, an EPROM memory, an EEPROM memory, a register, a hard disk, a removable disk, a CD-ROM, or any other form of computer-readable storage medium known in the art. An example storage medium may be coupled to a machine such as a computer / processor (which may be referred to herein as a "processor" for convenience), such a processor may read information (e.g., code) from a storage medium and write the information to the storage medium. An example storage medium may be integrated with a processor. The processor and storage medium may reside in an ASIC. The ASIC may reside in a user device. In an alternative, the processor and storage medium may reside in a user device as discrete components. In addition, in some aspects, any suitable computer program product may include a computer-readable medium, which includes code related to one or more aspects of the present disclosure. In some aspects, a computer program product may include packaging materials.

[0321] Although the present invention has been described in conjunction with various aspects, it will be appreciated that the present invention is capable of further modifications. This application is intended to cover any changes, uses or adaptations of the present invention that generally follow the principles of the present invention and include such deviations from the present disclosure that are within the scope of known and customary practice in the field to which the present invention relates.

Claims

1. A method for user equipment to network relay discovery, characterized in that: include: The second relay user equipment receives a first user equipment to network relay discovery message from the first relay user equipment, wherein the first user equipment to network relay discovery message includes a user information identifier of the first relay user equipment, a layer 2 identifier of the third relay user equipment, and an identifier of a serving cell of the third relay user equipment; as well as The second relay user equipment transmits a second user equipment to network relay discovery message to the remote user equipment, wherein the second user equipment to network relay discovery message includes a user information identifier of the second relay user equipment, the layer 2 identifier and the identifier of the serving cell.

2. The method according to claim 1, characterized in that The third relay user equipment is the same as the first relay user equipment.

3. The method according to claim 1, characterized in that The third relay user equipment is different from the first relay user equipment.

4. The method according to claim 1, characterized in that: The first user equipment to network relay discovery message includes a first cumulative hop count.

5. The method according to claim 4, characterized in that The second user equipment to network relay discovery message includes a second accumulated hop count.

6. The method according to claim 5, characterized in that The second accumulated hop count is equal to the first accumulated hop count plus 1.

7. The method according to claim 1, characterized in that The first user equipment to network relay discovery message includes a user information identifier or a relay service code of the remote user equipment.

8. The method according to claim 7, characterized in that The second user equipment to network relay discovery message includes the user information identifier of the remote user equipment or the relay service code.

9. The method according to claim 1, characterized in that: The first user equipment to network relay discovery message or the second user equipment to network relay discovery message is a user equipment to network relay discovery notification message.

10. The method according to claim 1, characterized in that The first user equipment to network relay discovery message or the second user equipment to network relay discovery message is a user equipment to network relay discovery response message.

11. A second relay user equipment for user equipment to network relay discovery, characterized in that: include: Control circuit; a processor installed in the control circuit; as well as a memory installed in the control circuit and operatively coupled to the processor; wherein the processor is configured to execute program code stored in the memory to: Receiving a first user equipment to network relay discovery message from the first relay user equipment, wherein the first user equipment to network relay discovery message includes a user information identifier of the first relay user equipment, a layer 2 identifier of a third relay user equipment, and an identifier of a serving cell of the third relay user equipment; as well as A second user equipment to network relay discovery message is transmitted to a remote user equipment, wherein the second user equipment to network relay discovery message includes a user information identifier of the second relay user equipment, the layer 2 identifier and the identifier of the serving cell.

12. The second relay user equipment according to claim 11, characterized in that: The third relay user equipment is the same as the first relay user equipment.

13. The second relay user equipment according to claim 11, characterized in that: The third relay user equipment is different from the first relay user equipment.

14. The second relay user equipment according to claim 11, characterized in that: The first user equipment to network relay discovery message includes a first cumulative hop count.

15. The second relay user equipment according to claim 14, characterized in that: The second user equipment to network relay discovery message includes a second accumulated hop count.

16. The second relay user equipment according to claim 15, characterized in that: The second accumulated hop count is equal to the first accumulated hop count plus 1.

17. The second relay user equipment according to claim 11, characterized in that: The first user equipment to network relay discovery message includes a user information identifier or a relay service code of the remote user equipment.

18. The second relay user equipment according to claim 17, characterized in that: The second user equipment to network relay discovery message includes the user information identifier of the remote user equipment or the relay service code.

19. The second relay user equipment according to claim 11, characterized in that: The first user equipment to network relay discovery message or the second user equipment to network relay discovery message is a user equipment to network relay discovery notification message.

20. The second relay user equipment according to claim 11, characterized in that: The first user equipment to network relay discovery message or the second user equipment to network relay discovery message is a user equipment to network relay discovery response message.

Images