User device, communication device, method for user device, and method for communication device

Abstract

One aspect of this disclosure includes a Remote User Equipment (UE) method. The method includes performing a registration procedure. The method includes performing a Protocol Data Unit (PDU) session establishment procedure via a first ProSe UE-to-Network Relay and a PDU session establishment procedure via a second ProSe UE-to-Network Relay.

Description

Technical Field

[0001] This disclosure relates to a method for a Remote User Equipment (UE), a method for a first communication device, a Remote UE, a first communication device, and the like.

Background Art

[0002] In 3GPP (registered trademark) TS22.261 (Non-Patent Document 2), the following service requirements are described. The coverage provided by each Network Relay UE is relatively narrow compared to that of a normal radio station. Therefore, when the Remote UE moves, this requirement is important for the Remote UE in order to maintain a stable indirect network connection by expanding the coverage. - It is assumed that the 5G system can manage communication between a Remote UE and a 5G network via multi-path indirect network connections.

Prior Art Documents

Non-Patent Documents

[0003]

Non-Patent Document 1

Non-Patent Document 2

Non-Patent Document 3

Non-Patent Document 4

[0004] However, the following service requirements are not yet addressed in 5GS. For example, the 3GPP specification does not include a mechanism to achieve the following service requirements. - The 5G system shall be able to manage communication between the Remote UE and the 5G network via multipath indirect network connectivity.

[0005] If 5GS does not support multipathing in indirect network connections, the instability of communication in the single connection between the Remote UE and the Network Relay UE will prevent the Remote UE (or Remote UE) from avoiding sudden interruptions or disconnections in connection services over the indirect network connection. The unstable connection in the single connection between the Remote UE and the Network Relay UE will impair the user experience in indirect network connections.

[0006] To mitigate or avoid sudden interruptions or disconnections in indirect network connections, multipathing for indirect network connections using multiple Network Relay UEs is necessary. [Means for solving the problem]

[0007] In the first exemplary embodiment, the Remote User Equipment (UE) method is: Follow the registration procedure, This includes performing a first ProSe UE-to-Network Relay procedure for establishing a Protocol Data Unit (PDU) session, and a second ProSe UE-to-Network Relay procedure for establishing a PDU session.

[0008] In a second exemplary embodiment, the method of the first communication device is: The Remote User Equipment (UE) receives information indicating that it supports connections via the first ProSe UE-to-Network Relay and the second ProSe UE-to-Network Relay. This includes sending information indicating that the Remote UE is authorized to perform communication via the first ProSe UE-to-Network Relay and the second ProSe UE-to-Network Relay.

[0009] In a third exemplary embodiment, the method of the first communication device is: To communicate with the second communication device, The Remote User Equipment (UE) includes transmitting information to the second communication device indicating that it is authorized to perform communication via the first ProSe UE-to-Network Relay and the second ProSe UE-to-Network Relay.

[0010] In a fourth exemplary embodiment, the method of the first communication device is: The Remote User Equipment (UE) receives information from the second communication device indicating that it is requesting communication via the first ProSe UE-to-Network Relay and the second ProSe UE-to-Network Relay, This includes transmitting information for controlling communication with a second communication device.

[0011] In a fifth exemplary embodiment, the method of the first communication device is: Receiving information for controlling communication via the first ProSe UE-to-Network Relay and the second ProSe UE-to-Network Relay, This includes performing communications based on that information.

[0012] In a sixth exemplary embodiment, the method of the first communication device is: Information is received from the second communication device indicating that the Remote User Equipment (UE) is requesting communication via the first ProSe UE-to-Network Relay and the second ProSe UE-to-Network Relay, This includes the Remote UE transmitting information to the second communication device indicating that it is authorized to establish communication.

[0013] In a seventh exemplary embodiment, the method of the first communication device is: Receive, from a second communication device, information indicating that a Remote User Equipment (UE) requests communication via a first ProSe UE-to-Network Relay and a second ProSe UE-to-Network Relay, and information indicating that the second communication device supports such communication. Include transmitting, to the second communication device, a policy including information indicating that the Remote UE is permitted to establish communication.

[0014] In an eighth exemplary aspect, a Remote User Equipment (UE) includes means for performing a registration procedure, and means for performing a Protocol Data Unit (PDU) Session establishment procedure via a first ProSe UE-to-Network Relay and a PDU Session establishment procedure via a second ProSe UE-to-Network Relay.

[0015] In a ninth exemplary aspect, a first communication device includes means for receiving information indicating that a Remote User Equipment (UE) supports communication via a first ProSe UE-to-Network Relay and a second ProSe UE-to-Network Relay, and means for transmitting information indicating that the Remote UE is permitted to perform communication via the first ProSe UE-to-Network Relay and the second ProSe UE-to-Network Relay.

[0016] In a tenth exemplary aspect, a first communication device includes means for communicating with a second communication device, and The system includes means for transmitting to a second communication device information indicating that the Remote User Equipment (UE) is authorized to perform communication via a first ProSe UE-to-Network Relay and a second ProSe UE-to-Network Relay.

[0017] In the eleventh exemplary embodiment, the first communication device is A means for receiving from a second communication device information indicating that Remote User Equipment (UE) is requesting communication via a first ProSe UE-to-Network Relay and a second ProSe UE-to-Network Relay, It includes means for transmitting information for controlling communication with a second communication device.

[0018] In a twelfth exemplary embodiment, the first communication device is: Means for receiving information for controlling communication via the first ProSe UE-to-Network Relay and the second ProSe UE-to-Network Relay, This includes means for carrying out communication based on that information.

[0019] In the 13th exemplary embodiment, the first communication device is A means for receiving from a second communication device information indicating that Remote User Equipment (UE) is requesting communication via a first ProSe UE-to-Network Relay and a second ProSe UE-to-Network Relay, The system includes means for transmitting information to a second communication device indicating that the Remote UE is authorized to establish its communication.

[0020] In the fourteenth exemplary embodiment, the first communication device is: Means for receiving from a second communication device information indicating that a Remote User Equipment (UE) is requesting communication via a first ProSe UE-to-Network Relay and a second ProSe UE-to-Network Relay, and information indicating that the second communication device is compatible with that communication, The system includes means for transmitting a policy to a second communication device that contains information indicating that the Remote UE is authorized to establish its communication. [Effects of the Invention]

[0021] An exemplary object of this disclosure is to provide a method and apparatus that can solve the problems described above. [Brief explanation of the drawing]

[0022] [Figure 1] Figure 1 shows a network connection model of the first embodiment of the first aspect. [Figure 2] Figure 2 is a signaling diagram of a second embodiment of the first aspect. [Figure 3] Figure 3 is a signaling diagram of a third embodiment of the first aspect. [Figure 4] Figure 4 shows the movement of Remote UE as an embodiment of the first and second embodiments. [Figure 5] Figure 5 is a signaling diagram of the fourth embodiment of the first aspect. [Figure 6] Figure 6 shows a network connection model of the first embodiment of the second aspect. [Figure 7] Figure 7 is a signaling diagram of a third embodiment of the second aspect. [Figure 8] Figure 8 is a signaling diagram of the fourth embodiment of the second aspect. [Figure 9] Figure 9 shows an overview of the Proximity Based Services system. [Figure 10] Figure 10 is a block diagram of the UE. [Figure 11] Figure 11 is a block diagram of the (R)AN node. [Figure 12] Figure 12 shows a system overview of a (R)AN node based on the O-RAN architecture. [Figure 13] Figure 13 is a block of RU. [Figure 14] Figure 14 is a block diagram of the DU. [Figure 15] Figure 15 is a block of CU. [Figure 16] Figure 16 is a block diagram of the AMF. [Figure 17] Figure 17 is a block diagram of the SMF. [Figure 18] Figure 18 is a block diagram of the UPF. [Figure 19] Figure 19 is a block diagram of the PCF. [Figure 20] Figure 20 is a block of AF. [Figure 21] Figure 21 is a block diagram of the UDM. [Modes for carrying out the invention]

[0023] (abbreviation) For the purposes of this document, 3GPP TR21.905 (Non-Patent Literature 1) and the abbreviations given below apply. If the same abbreviation exists in 3GPP TR21.905 (Non-Patent Literature 1), the abbreviation defined in this document shall take precedence. 4G-GUTI 4G Globally Unique Temporary UE Identity 5GC 5G Core Network 5G LAN 5G Local Area Network 5GS 5G System 5G-AN 5G Access Network 5G-AN PDB 5G Access Network Packet Delay Budget 5G-EIR 5G-Equipment Identity Register 5G-GUTI 5G Globally Unique Temporary Identifier 5G-BRG 5G Broadband Residential Gateway 5G-CRG 5G Cable Residential Gateway 5G GM 5G Grand Master 5G-RG 5G Residential Gateway 5G-S-TMSI 5G S-Temporary Mobile Subscription Identifier 5G VN 5G Virtual Network 5QI 5G QoS Identifier AF Application Function AMF Access and Mobility Management Function AMF-G Geographically selected Access and Mobility Management Function AMF-NG Non-Geographically selected Access and Mobility Management Function ANDSF Access Network Discovery and Selection Function ARFCN Absolute radio-frequency channel number AS Access Stratum ASN Abstract Syntax Notation ATSSS Access Traffic Steering, Switching, Splitting ATSSS-LL ATSSS Low-Layer AuC Authentication Centre AUSF Authentication Server Function AUTN Authentication token BCCH Broadcast Control Channel BMCA Best Master Clock Algorithm BSF Binding Support Function CAG Closed Access Group CAPIF Common API Framework for 3GPP northbound APIs CHF Charging Function CN PDB Core Network Packet Delay Budget CP Control Plane DAPS Dual Active Protocol Stacks DL Downlink DN Data Network DNAI DN Access Identifier DNN Data Network Name DRX Discontinuous Reception DS-TT Device-side TSN translator ePDG evolved Packet Data Gateway EBI EPS Bearer Identity EPS Evolved Packet System EUI Extended Unique Identifier FAR Forwarding Action Rule FN-BRG Fixed Network Broadband RG FN-CRG Fixed Network Cable RG FN-RG Fixed Network RG FQDN Fully Qualified Domain Name GFBR Guaranteed Flow Bit Rate GMLC Gateway Mobile Location Centre G-PDU GTP encapsulated user Plane Data Unit GPS Global Positioning System GPSI Generic Public Subscription Identifier GUAMI Globally Unique AMF Identifier GUTI Globally Unique Temporary UE Identity HPLMN Home Public Land Mobile Network HR Home Routed(ローミング) HSS Home Subscriber Server IAB Integrated access and backhaul IPsec Internet Protocol Security IMEI / TAC IMEI Type Allocation Code IMSI International Mobile Subscriber Identity IPUPS Inter PLMN UP Security I-SMF Intermediate SMF I-UPF Intermediate UPF LADN Local Area Data Network LBO Local Break Out(ローミング) LMF Location Management Function LoA Level of Automation LPP LTE Positioning Protocol LRF Location Retrieval Function MCC Mobile country code MCX Mission Critical Service MDBV Maximum Data Burst Volume ME Mobile Equipment MFBR Maximum Flow Bit Rate MICO Mobile Initiated Connection Only MINT Minimization of service interruption MITM Man In the Middle MME Mobility Management Entity MN Master Node MNC Mobile Network Code MOCN Multiple Operator Core Network MPS Multimedia Priority Service MPTCP Multi-Path TCP Protocol MT Mobile Termination N3IWF Non-3GPP InterWorking Function N3GPP Non-3GPP access N5CW Non-5G-Capable over WLAN NAI Network Access Identifier NAS Non-Access-Stratum NEF Network Exposure Function NF Network Function NGAP Next Generation Application Protocol NID Network identifier NMEA National Marine Electronics Association NPN Non-Public Network NR New Radio NSAG Network Slice Access Stratum Group NRF Network Repository Function NSAC Network Slice Admission Control NSACF Network Slice Admission Control Function NSI ID Network Slice Instance Identifier NSSAA Network Slice-Specific Authentication and Authorization NSSAAF Network Slice-Specific Authentication and Authorization Function NSSAI Network Slice Selection Assistance Information NSSF Network Slice Selection Function NSSP Network Slice Selection Policy NSSRG Network Slice Simultaneous Registration Group NW-TT Network-side TSN translator NWDAF Network Data Analytics Function PCF Policy Control Function PCO Protocol Configuration Options PCRF Policy and Charging Rules Function PDB Packet Delay Budget PDR Packet Detection Rule PDU Protocol Data Unit PEI Permanent Equipment Identifier PER Packet Error Rate PFD Packet Flow Description PLMN Public Land Mobile Network PNI-NPN Public Network Integrated Non-Public Network PPD Paging Policy Differentiation PPF Paging Proceed Flag PPI Paging Policy Indicator ProSe Proximity based Services PSA PDU Session Anchor PTP Precision Time Protocol QFI QoS Flow Identifier QoE Quality of Experience RACS Radio Capabilities Signalling optimisation (R)AN (Radio)Access Network RAT Radio Access Technology RG Residential Gateway RIM Remote Interference Management RQA Reflective QoS Attribute RQI Reflective QoS Indication RRC Radio Resource Control RSC Relay Service Code RSD Route Selection Descriptor RSN Redundancy Sequence Number RSRP Reference Signal Received Power RSRQ Reference Signal Received Quality RVAS Roaming Value Added Service SA NR Standalone New Radio SBA Service Based Architecture SBI Service Based Interface SCP Service Communication Proxy SD Slice Differentiator SEAF Security Anchor Functionality SENSE Signal Level Enhanced Network Selection SEPP Security Edge Protection Proxy SGW Serving Gateway SIB System Information Block SINR Signal to Interference plus Noise Ratio SMF Session Management Function SMSF Short Message Service Function SN Sequence Number SN Secondary Node SN name Serving Network Name SNPN Stand-alone Non-Public Network S-NSSAI Single Network Slice Selection Assistance Information SOR Steering Of Roaming SSC Session and Service Continuity SSCMSP Session and Service Continuity Mode Selection Policy SST Slice / Service Type SUCI Subscription Concealed Identifier SUPI Subscription Permanent Identifier SV Software Version TAU Tracking Area Update TEID Tunnel Endpoint Identifier TMSI Temporary Mobile Subscriber Identity TNAN Trusted Non-3GPP Access Network TNAP Trusted Non-3GPP Access Point TNGF Trusted Non-3GPP Gateway Function TNL Transport Network Layer TNLA Transport Network Layer Association TSC Time Sensitive Communication TSCAI TSC Assistance Information TSN Time Sensitive Networking TSN GM TSN Grand Master TSP Traffic Steering Policy TT TSN Translator TWIF Trusted WLAN Interworking Function UCMF UE radio Capability Management Function UDM Unified Data Management UDR Unified Data Repository UDSF Unstructured Data Storage Function UE User Equipment UL Uplink UL CL Uplink Classifier UPF User Plane Function UPSI UE Policy Section Identifier URLLC Ultra Reliable Low Latency Communication URRP-AMF UE Reachability Request Parameter for AMF URSP UE Route Selection Policy USIM User Services Identity Module VID VLAN Identifier VLAN Virtual Local Area Network VPLMN Visited Public Land Mobile Network W-5GAN Wireline 5G Access Network W-5GBAN Wireline BBF Access Network W-5GCAN Wireline 5G Cable Access Network W-AGF Wireline Access Gateway Function

[0024] (definition) For the purposes of this document, the terms and definitions given in 3GPP TR21.905 (Non-Patent Literature 1) and below shall apply. If the same term is defined in 3GPP TR21.905 (Non-Patent Literature 1), the terms defined in this document shall take precedence.

[0025] (Summary) Those skilled in the art will understand that elements in the drawings are shown for simplification and may not necessarily be drawn to scale. Furthermore, with respect to the structure of a device, one or more components of the device may be represented in the drawings by conventional symbols, and the drawings may show only certain details relevant to understanding aspects of this disclosure so as not to obscure the drawings with details that would be readily apparent to those skilled in the art who benefit from the description herein.

[0026] For the purpose of facilitating understanding of the principles of this disclosure, the embodiments shown in the figures will be referenced and specific language will be used to describe them. Nevertheless, it will be understood that this is not intended to limit the scope of this disclosure. Such modifications and further alterations to the exemplary systems, as well as such further applications of the principles of this disclosure, as would ordinarily conceivable to those skilled in the art, should be construed as being within the scope of this disclosure.

[0027] The terms “comprises,” “comprising,” or any other variation thereof are intended to encompass non-exclusive inclusions such that a process or method containing a list of steps may include steps not explicitly enumerated, or other steps specific to such process or method, rather than only those steps. Similarly, one or more devices, entities, subsystems, elements, components, or constituents following “comprises ~ a” do not, without further constraint, exclude the existence of other devices, subsystems, elements, components, constituents, additional devices, additional subsystems, additional elements, additional components, or additional constituents. Throughout this specification, occurrences of the phrases “in one aspect,” “in another aspect,” and similar wording may, but not necessarily, all refer to the same aspect.

[0028] Unless otherwise defined, all technical and scientific terms used herein have the same meaning as those generally understood by those skilled in the art to which this disclosure pertains. The systems, methods, and examples provided herein are illustrative and not intended to limit the scope of this disclosure.

[0029] In the following specification and claims, certain terms may be defined as having the following meanings: The singular forms “a,” “an,” and “the” include plural references unless the context clearly indicates otherwise.

[0030] Where used herein, data is meaningful information and represents values ​​resulting from parameters; therefore, information is related to data and knowledge. Further knowledge means an understanding of abstract or concrete concepts. This exemplary system is simplified for the sake of facilitating the explanation of the subject matter of this disclosure and is not intended to limit the scope of this disclosure. The embodiments disclosed herein can be implemented using other devices, systems, and configurations in addition to, or instead of, the system, and all such embodiments are considered to be within the scope of this disclosure.

[0031] Each embodiment (i.e., the first embodiment, the second embodiment, the first embodiment relating to the first embodiment, the second embodiment relating to the first embodiment, the third embodiment relating to the first embodiment, the fourth embodiment relating to the first embodiment, the first embodiment relating to the second embodiment, the second embodiment relating to the second embodiment, the third embodiment relating to the second embodiment, the fourth embodiment relating to the second embodiment, and variations of each embodiment) and the elements contained in each of the embodiments described below can be implemented independently or in combination with any other. These embodiments contain novel features that differ from each other. Therefore, these embodiments contribute to achieving different objectives or solving different problems and contribute to obtaining different advantages.

[0032] Any list described in the following aspects includes at least one or more parameters.

[0033] An exemplary object of this disclosure is to provide a method and apparatus that can solve the problems described above.

[0034] A Remote User Equipment (UE) method in an exemplary aspect of this disclosure includes performing a registration procedure. This method includes performing a Protocol Data Unit (PDU) session establishment procedure via a first ProSe UE-to-Network Relay, and a PDU session establishment procedure via a second ProSe UE-to-Network Relay.

[0035] A first communication device method in an exemplary aspect of the present disclosure includes receiving information indicating that Remote User Equipment (UE) is compatible with connections via a first ProSe UE-to-Network Relay and a second ProSe UE-to-Network Relay. The method also includes transmitting information indicating that the Remote UE is authorized to perform communications via the first ProSe UE-to-Network Relay and the second ProSe UE-to-Network Relay.

[0036] A method of a first communication device in an exemplary aspect of the present disclosure includes communicating with a second communication device. The method includes transmitting information to the second communication device indicating that the Remote User Equipment (UE) is authorized to perform communication via the first ProSe UE-to-Network Relay and the second ProSe UE-to-Network Relay.

[0037] A method of a first communication device in an exemplary aspect of the present disclosure includes receiving from a second communication device information indicating that Remote User Equipment (UE) is requesting communication via a first ProSe UE-to-Network Relay and a second ProSe UE-to-Network Relay. The method includes transmitting information for controlling communication with the second communication device.

[0038] A method of a first communication device in an exemplary aspect of the present disclosure includes receiving information for controlling communications via a first ProSe UE-to-Network Relay and a second ProSe UE-to-Network Relay. The method includes performing communications based on such information.

[0039] A first communication device method in an exemplary embodiment of the present disclosure includes receiving from a second communication device information indicating that Remote User Equipment (UE) is requesting communication via a first ProSe UE-to-Network Relay and a second ProSe UE-to-Network Relay. The method also includes transmitting to the second communication device information indicating that the Remote UE is authorized to establish its communication.

[0040] The method of the first communication device in an exemplary aspect of the present disclosure includes receiving from the second communication device information indicating that Remote User Equipment (UE) is requesting communication via the first ProSe UE-to-Network Relay and the second ProSe UE-to-Network Relay, and information indicating that the second communication device is responding to that communication. The method also includes transmitting to the second communication device a policy that includes information indicating that the Remote UE is authorized to establish that communication.

[0041] An exemplary Remote User Equipment (UE) in this disclosure includes at least one memory and at least one hardware processor connected to the at least one memory. The at least one hardware processor is configured to perform a registration procedure. The at least one hardware processor is configured to perform a Protocol Data Unit (PDU) session establishment procedure via a first ProSe UE-to-Network Relay and a PDU session establishment procedure via a second ProSe UE-to-Network Relay.

[0042] A first communication device according to an exemplary aspect of the present disclosure includes at least one memory and at least one hardware processor connected to the at least one memory. The at least one hardware processor is configured to receive information indicating that Remote User Equipment (UE) is compatible with connections via a first ProSe UE-to-Network Relay and a second ProSe UE-to-Network Relay. The at least one hardware processor is configured to transmit information indicating that the Remote UE is authorized to perform communications via the first ProSe UE-to-Network Relay and the second ProSe UE-to-Network Relay.

[0043] An exemplary embodiment of the present disclosure includes a first communication device comprising at least one memory and at least one hardware processor connected to the at least one memory. The at least one hardware processor is configured to communicate with a second communication device. The at least one hardware processor is configured to transmit to the second communication device information indicating that Remote User Equipment (UE) is authorized to perform communication via the first ProSe UE-to-Network Relay and the second ProSe UE-to-Network Relay.

[0044] An exemplary embodiment of the present disclosure includes a first communication device comprising at least one memory and at least one hardware processor connected to the at least one memory. The at least one hardware processor is configured to receive from a second communication device information indicating that Remote User Equipment (UE) is requesting communication via a first ProSe UE-to-Network Relay and a second ProSe UE-to-Network Relay. The at least one hardware processor is configured to transmit information for controlling communication with the second communication device.

[0045] A first communication device according to an exemplary aspect of the present disclosure includes at least one memory and at least one hardware processor connected to the at least one memory. The at least one hardware processor is configured to receive information for controlling communications via a first ProSe UE-to-Network Relay and a second ProSe UE-to-Network Relay. The at least one hardware processor is configured to perform communications based on that information.

[0046] An exemplary embodiment of the present disclosure includes a first communication device comprising at least one memory and at least one hardware processor connected to the at least one memory. The at least one hardware processor is configured to receive from a second communication device information indicating that Remote User Equipment (UE) is requesting communication via a first ProSe UE-to-Network Relay and a second ProSe UE-to-Network Relay. The at least one hardware processor is configured to transmit to the second communication device information indicating that the Remote UE is authorized to establish its communication.

[0047] A first communication device according to an exemplary aspect of the present disclosure includes at least one memory and at least one hardware processor connected to the at least one memory. The at least one hardware processor is configured to receive from the second communication device information indicating that Remote User Equipment (UE) is requesting communication via a first ProSe UE-to-Network Relay and a second ProSe UE-to-Network Relay, and information indicating that the second communication device is responding to that communication. The at least one hardware processor is configured to transmit to the second communication device a policy including information indicating that the Remote UE is authorized to establish that communication.

[0048] This disclosure uses the system overview of Proximity Based Services (ProSe) shown in Figure 9 to disclose the following aspects, where the service server that Remote UE310 communicates with is AF201 in the data network 20. However, the service server that Remote UE310 targets is not limited to AF201. For example, the target service server could be any server, such as an Internet, IMS, IoT service, or V2X service. For example, if this disclosure is applied to a UE-to-Network Relay of 5G ProSe Layer-3 corresponding to N3IWF as described in 3GPP TS23.304 (Non-Patent Literature 7), the target service server may be located in the Home PLMN of Remote UE310, or it may be connected via N3IWF while Remote UE310 is in the Visited PLMN.

[0049] Remote UE may be represented as, for example, ProSe Remote UE, 5G ProSe Remote UE, etc.

[0050] Network Relay UE may also be represented as, for example, ProSe UE-to-Network Relay, 5GProSe UE-to-Network Relay, etc.

[0051] A Remote UE may use multiple Network Relay UEs to establish an indirect network connection with the Network Relay UEs.

[0052] (First aspect) This embodiment discloses a mechanism for configuring multipath for indirect network connections using multiple Network Relay UEs by adapting enhanced Access Traffic Steering, Switching, Splitting (ATSSS) functionality. Multipath for indirect network connections may also be expressed as multipath indirect network connections, multipath indirect communication connections, multiple indirect network communication paths, etc. Communication in the multipath for indirect network connections, or communication performed in the multipath for indirect network connections, may also be expressed as multipath indirect network communication.

[0053] Multipath indirect communication connectivity provides high resilience to data connectivity (for example, even if a Remote UE falls out of coverage of the single Network Relay UE it is connected to, the Remote UE's data connectivity can still be maintained).

[0054] (First embodiment relating to the first aspect) Figure 1 includes a network connectivity model that supports multipath indirect network connectivity by adapting the Advanced Access Traffic Steering, Switching, Splitting (ATSSS) function to 5GS, which supports Proximity-based Services. The ATSSS function is defined in 3GPP TS23.501 (Non-Patent Literature 3). The Advanced Access Traffic Steering, Switching, Splitting (eATSSS) function may be an evolution of the ATSSS function.

[0055] Figure 1 includes a network connectivity model that supports multipath indirect network connectivity by adapting advanced Access Traffic Steering, Switching, Splitting (ATSSS) functionality.

[0056] Remote UE310 connects to Network Relay UE30001, Network Relay UE30002, and Network Relay UE30003 for a single enhanced Multi Access-PDU (MA PDU) session. MA PDU sessions are defined in 3GPP TS23.501 (Non-Patent Literature 2) and 3GPP TS23.502 (Non-Patent Literature 3). For example, Remote UE310 may connect to at least two Network Relay UEs.

[0057] A Multi Access-PDU (MA PDU) Session is a PDU Session associated with two independent N3 / N9 tunnels between UPF72 and RAN5, and with multiple access methods connected to 5GC according to 3GPP TS23.502 (Non-Patent Document 3), i.e., associated with both 3GPP access and non-3GPP access. On the other hand, an evolved Multi Access-PDU (MA PDU) Session may include two or more independent Uu connections between Network Relay UE30 and RAN5, as well as N3 / N9 tunnels between UPF72 and RAN5, with a single access type, i.e., between 3GPP accesses, or multiple access types, i.e., one or more 3GPP accesses and one or more non-3GPP accesses.

[0058] An evolved Multi Access-PDU (MA PDU) Session may be a PDU Session having two or more independent Uu connections between Network Relay UE30 and RAN5, or associated therewith; or a PDU Session having an N3 / N9 tunnel between UPF72 and RAN5, or associated therewith, with a single access type, some 3GPP access (or some non-3GPP access); or multiple access types, i.e., one or more 3GPP accesses, one or more non-3GPP accesses.

[0059] Figure 1 shows that each Network Relay UE30 has its own associated RAN5 (for example, Network Relay UE30001 has or is associated with RAN501), but Network Relay UE30 can connect to the same RAN5 as other Network Relay UE30s. For example, both Network Relay UE30001 and Network Relay UE30002 can connect to RAN501.

[0060] In one embodiment, the Remote UE310 may connect directly to the RAN5 via the Uu interface to configure an Evolutionary Multi Access-PDU (MA PDU) Session while establishing other connections via the Network Relay UE30 and RAN5.

[0061] Remote UE310 and UPF72 may support enhanced ATSSS-LL functionality. ATSSS-LL functionality is defined in 3GPP TS23.501 (Non-Patent Document 2) and 3GPP TS23.502 (Non-Patent Document 3). In addition to ATSSS-LL functionality, enhanced ATSSS-LL functionality provides at least one of the following features: The evolved ATSSS-LL functionality in Remote UE310 and UPF72 does not require the application of a specific protocol. It is a data switching function that determines how to steer, switch, and split uplink traffic between 3GPP and non-3GPP accesses based on the supplied eATSSS Rule and local conditions (e.g., signal loss conditions). The ATSSS-LL functionality in Remote UE310 and UPF72 may be applied to steer, switch, and split all types of traffic, including TCP traffic, UDP traffic, and Ethernet traffic. If Remote UE310 provides "Multi-path relay capability" during the registration procedure, the advanced ATSSS-LL functionality may be enabled in Remote UE310. If Remote UE310 provides "Advanced ATSSS-LL capability" during the PDU Session Establishment procedure, the Advanced ATSSS-LL functionality may be enabled in Remote UE310.

[0062] Remote UE310 and UPF72 may maintain an enhanced ATSSS Rule for multipath indirect network connectivity. The ATSSS Rule is defined in 3GPP TS23.501 (Non-Patent Document 2) and 3GPP TS23.502 (Non-Patent Document 3). The enhanced ATSSS Rule is generated by SMF71 by contacting PCF73 and transmitted to Remote UE310 and UPF72.

[0063] For example, SMF71 may contact PCF73 to receive information from PCF73 for generating an evolved ATSSS Rule, and may generate an evolved ATSSS Rule based on the received information. SMF71 may also generate an evolved ATSSS Rule based on local policies or local settings within SMF71. SMF71 may send the generated evolved ATSSS Rule to Remote UE310 and UPF72. The evolved ATSSS Rule for UPF72 can be included in the N4 rule or it can be independent of the N4 rule. In addition to the ATSSS Rule, the evolved ATSSS Rule may include at least one of the following pieces of information: • Multi-Active-Standby: This is used when multiple accesses are available to direct the service data flow (SDF) to multiple accesses (e.g., active accesses), and when an active access becomes unavailable, the SDF switches to another available active access. When an active access becomes available again, the SDF returns to that access. • Smallest Delay: Used to direct SDF to the access determined to have the minimum Round-Trip Time (RTT). To determine the RTT across multiple 3GPP accesses, measurements may be obtained by Remote UE310 and UPF72. In addition, if an access becomes unavailable, all SDF traffic (all traffic on the SDF, or the SDF itself) is switched to another available access. This can only be used with Non-GBR SDF. • Load-Balancing: Used to divide the SDF across multiple 3GPP accesses when multiple 3GPP accesses are available. This includes the proportion of SDF traffic sent through each 3GPP access. Load-Balancing may only be applied to non-GBR SDF. In addition, if one access becomes unavailable, all SDF traffic (all traffic in the SDF) is switched to another available access. • Priority-based: Used to direct all SDF traffic (or SDF) to higher priority access until it is determined that the access is congested. In this case, all SDF traffic (or SDF) is also sent to lower priority access, i.e., SDF traffic (or SDF) is split across multiple 3GPP accesses. In addition, if higher priority access becomes unavailable, all SDF traffic (or SDF) is switched to lower priority access. This can only be used with Non-GBR SDF. For example, Remote UE310 may determine that congestion has occurred based on local policies or local settings on Remote UE310. For example, if Remote UE310 receives information indicating that congestion has occurred on other network nodes, Remote UE310 may determine that congestion has occurred. UPF72 may determine that congestion has occurred in a similar manner to Remote UE310.

[0064] The evolved ATSSS Rule may also be applied to non-3GPP access.

[0065] Advanced Access Traffic Steering, Switching, Splitting (ATSSS) functionality is also sometimes referred to as ATSSS for multi-path indirect network connections, Multi Path ATSSS (MPATSSS), enhanced ATSSS (eATSSS), or enhanced ATSSS (eATSSS) functionality.

[0066] The capability of the evolved ATSSS function in SMF71 and UPF72 can be expressed as evolved ATSSS capability. Evolved ATSSS capability can also be called, for example, eATSS capability.

[0067] The capability of the advanced ATSSS function may be indicated by the fact that the SMF71 or UPF72 supports the advanced ATSSS function.

[0068] The capabilities of the evolved ATSSS function may demonstrate that SMF71 or UPF72 can perform appropriate processes using the evolved ATSSS Rule.

[0069] The capabilities of the evolved ATSSS function may indicate that SMF71 or UPF72 can use the evolved ATSSS Rule to perform at least one of the above-described steering of the SDF and the above-described partitioning of the SDF.

[0070] The capabilities of the advanced ATSSS function may also demonstrate that the SMF71 or UPF72 can perform communication over multipath indirect network connections.

[0071] The capabilities of the evolved ATSSS function may indicate that the SMF71 or UPF72 can perform communication over a multipath indirect network connection using at least one of the evolved ATSSS Rule and the evolved ATSSS function.

[0072] For example, at least one of Remote UE310, SMF71, and UPF72 may use an evolved ATSSS Rule to process or perform eATSSS functions (including, for example, at least one of the SDF steering and SDF splitting described above).

[0073] For example, at least one of the Remote UE310, SMF71, and UPF72 may use an evolved ATSSS Rule to perform at least one of the SDF steering and SDF splitting described above.

[0074] For example, at least one of the Remote UE310, SMF71, and UPF72 may perform at least one of the above-mentioned SDF steering and SDF splitting by executing the evolved ATSSS-LL function using the evolved ATSSS Rule.

[0075] For example, at least one of the Remote UE310, SMF71, and UPF72 may use an evolved ATSSS Rule to perform communication over a multipath indirect network connection.

[0076] At least one of the Remote UE310, SMF71, and UPF72 may store an evolved ATSSS rule.

[0077] At least one of the Remote UE310, SMF71, and UPF72 may pre-store an evolutionary ATSSS rule. At least one of the Remote UE310, SMF71, and UPF72 may pre-receive an evolutionary ATSSS rule from another network node.

[0078] For example, at least one of the Remote UE310, SMF71, and UPF72 may determine which path is used for communication based on an evolved ATSSS rule.

[0079] For example, if there are three multipath indirect network connections (e.g., a first connection or path via Network Relay UE30001, a second connection or path via Network Relay UE30002, and a third connection or path via Network Relay UE30003), at least one of Remote UE310, SMF71, and UPF72 may determine which connection or path is used for communication based on the evolved ATSSS Rule.

[0080] The policy for the evolved ATSSS function in PCF73 may be expressed as the evolved ATSSS policy. The evolved ATSSS policy may also be called, for example, the eATSS policy.

[0081] The advanced ATSSS-LL functionality may also be called, for example, eATSSS-LL functionality, ATSSS-LL for multi-path indirect network connections, Multi Path ATSSS-LL (MPATSSS-LL), or Enhanced ATSSS-LL (eATSSS-LL).

[0082] The evolved ATSSS Rule may also be called, for example, the ATSSS Rule for multi-path indirect network connections, eATSSS Rule, Multi Path ATSSS Rule (MPATSSS Rule), enhanced ATSSS Rule (eATSSS Rule), or eATSSS Rule.

[0083] The evolved Multi Access-PDU (MA PDU) Session may also be called, for example, MA PDU Session for multi-path indirect network connections, or enhanced MA PDU Session (eMA PDU Session).

[0084] Communication in a multipath indirect network connection or communication performed in a multipath indirect network connection may include communication in, via, through, or using an eMA PDU Session.

[0085] Advanced Access Traffic Steering, Switching, Splitting (ATSSS) functionality may include advanced ATSSS-LL functionality.

[0086] The advanced ATSSS-LL functionality may include advanced Access Traffic Steering, Switching, and Splitting (ATSSS) functionality.

[0087] An evolved ATSSS Rule may be used in at least one of the following functions: evolved Access Traffic Steering, Switching, Splitting (ATSSS) functionality and evolved ATSSS-LL functionality.

[0088] An evolved ATSSS Rule may be a rule used for at least one of the following functions: evolved Access Traffic Steering, Switching, Splitting (ATSSS) functionality and evolved ATSSS-LL functionality.

[0089] (Second embodiment relating to the first aspect) Figure 2 shows an example of the registration procedure for Remote UE310. Referring to Figure 2, a detailed process of a second embodiment relating to the first aspect is described below.

[0090] Step 0: A communication path is established between the Remote UE310 and the Network Relay UE300 via the PC5 interface, in accordance with 3GPP TS23.304 (Non-Patent Document 7).

[0091] Step 1: The Remote UE310 sends a Registration Request message to the AMF70 that includes at least one of the following: User ID, Requested NSSAI, and Multi-path relay capability. The Remote UE310 may also send the Registration Request message to the AMF70 via the Network Relay UE300. For example, the Network Relay UE300 may be Network Relay UE30001, Network Relay UE30002, or Network Relay UE30003, as shown in Figure 1.

[0092] The following sections provide a detailed explanation of each parameter. The User ID (which may be represented as User Identity, for example) may be a 5G-GUTI, SUCI, or SUPI. For example, User Identity may be a 5G-GUTI, SUCI, or SUPI for Remote UE310. Multi-path relay capability indicates that the Remote UE310 supports the processing of multipath indirect network connections as disclosed herein. In one embodiment, multi-path relay capability may indicate that the Remote UE310 supports the processing or execution of an Advanced Access Traffic Steering, Switching, Splitting (ATSSS) function or process, as disclosed in the first aspect of this disclosure. Multi-path relay capability may be defined in 5GMM capability. Multi-path relay capability may indicate that the Remote UE310 supports multipath indirect network connections. Multi-path relay capability may indicate that the Remote UE310 supports connections via Network Relay UE30001, connections via Network Relay UE30002, and connections via Network Relay UE30003, as shown in Figure 1.

[0093] Step 2: Upon receiving the Registration Request message in Step 1, AMF70 calls the Nudm_UECM_Registration service to UDM75 in HPLMN to register AMF70 as the current AMF node for Remote UE310.

[0094] Step 3: After the completion of the Nudm_UECM_Registration service in Step 2, AMF70 sends a Nudm_SDM_Get Request message containing the User ID and Multi-path relay capability to UDM75 in HPLMN. For details on the User ID and Multi-path relay capability, please refer to Step 1.

[0095] Step 4 UDM75 finds the Subscriber data for Remote UE310 and sends a Nudm_SDM_Get Response message containing the Subscriber data for Remote UE310 to AMF70. The Subscriber data includes the subscribed eMA PDU (eMA PDU subscribed). UDM75 may provide the subscribed eMA PDU to AMF70 as part of the 5G ProSe subscription data. UDM75 may provide the subscribed eMA PDU to AMF70 only if UDM75 received Multi-path relay capability from AMF70 in Step 3.

[0096] A subscribed eMA PDU indicates that the Remote UE310 is authorized to establish an eMA PDU Session as subscriber data. A subscribed eMA PDU may exist for each S-NSSAI within a Subscribed NSSAI. A subscribed eMA PDU may indicate that the Remote UE310 is authorized to communicate in, by, through, or using an eMA PDU Session. A subscribed eMA PDU may indicate that the Remote UE310 is authorized to communicate using a multipath indirect network connection.

[0097] The subscribed eMA PDU may also indicate the maximum number of PC5 connections that the Remote UE310 can establish in a single eMA PDU Session. If the AMF70 receives a request from the Remote UE310 to add another PDU Session to an established eMA PDU Session, the maximum number of PC5 connections is referenced by the AMF70. If the request attempts to add more PC5 connections than the maximum number, the AMF70 rejects the request and sends an MM rejection message to the Remote UE310.

[0098] For example, if the request attempts to establish more PC5 connections than the maximum number, the AMF70 rejects the request and sends an MM rejection message to the Remote UE310 along with the cause. The cause may indicate that the request attempts to establish more PC5 connections than the maximum number. The cause may indicate that the request was rejected because it attempts to establish more PC5 connections than the maximum number.

[0099] For example, if AMF70 determines that the request would reach the maximum number of PC5 connections for Remote UE310, AMF70 may reject the request and send an MM rejection message to Remote UE310.

[0100] For example, if the AMF70 determines that establishing a PC5 connection as a result of that request would cause the current number of PC5 connections on the Remote UE310 to exceed the maximum number of PC5 connections, the AMF70 may reject the request and send an MM rejection message to the Remote UE310.

[0101] Step 5: After obtaining the Subscriber data for Remote UE310 from UDM75 in Step 4, AMF70 sends a Registration Accept message to Remote UE310, including the 5G-GUTI and the subscribed eMA PDU.

[0102] When Remote UE310 receives an eMA PDU subscribed from AMF70 in a Registration Accept message, Remote UE310 recognizes that it can establish a multipath indirect network connection or an eMA PDU session. If the subscribed eMA PDU indicates the maximum number of PC5 connections that Remote UE310 can establish for a single eMA PDU session, the maximum number of PC5 connections is remembered by Remote UE310 and referenced when Remote UE310 adds further PDU sessions to an established eMA PDU session. Remote UE310 may request to add further PDU sessions to an established eMA PDU session up to the maximum number of PC5 connections received. In one embodiment, the subscribed eMA PDU may also be represented as, for example, a supported eMA PDU, a multiple supported PDU, etc.

[0103] (Modification 1 of the second embodiment relating to the first aspect) In step 5, if the AMF70 does not support multipath indirect network connectivity or MA PDU Session, the AMF70 does not include the eMA PDU subscribed in step 5 in the Registration Accept message. That is, if the AMF70 does not support multipath indirect network connectivity or MA PDU Session, the AMF70 cannot read the Multipath relay capability parameters in step 1, as added in this disclosure. However, the AMF70 can still perform the Registration Procedure without supporting multipath indirect network connectivity or MA PDU Session.

[0104] In step 1, if Remote UE310 sends a Registration Request message to AMF70 indicating its Multipath relay capability, but receives a Registration Accept message without a subscribed eMA PDU, Remote UE310 recognizes that it cannot establish a multipath indirect network connection or eMA PDU session because AMF70 does not support it, or that Remote UE310 has not subscribed to a multipath indirect network connection. For example, in step 1, if AMF70 does not support multipath indirect network connections or MA PDU sessions and AMF70 receives a Registration Request message, AMF70 may send a message indicating that AMF70 does not support multipath indirect network connections or MA PDU sessions, or AMF70 may send a Registration Reject message to reject the Registration Request message.

[0105] (Third embodiment relating to the first aspect) Figure 3 includes an example of a PDU session establishment procedure for a multipath indirect network connection with advanced ATSSS functionality.

[0106] To configure an eMA PDU Session using multiple Network Relay UE300s, the Remote UE310 must repeat the PDU Session establishment procedure in Figure 3 as many times as the Remote UE310 replicates the PC5 connection for the eMA PDU Session. This procedure configures eATSSS rules on both the Remote UE310 and UPF72, so that user data between the Remote UE310 and AF201 in the data network 20 is processed according to the eATSSS rules on both the Remote UE310 and UPF72, resulting in reliable user data transmission via the PC5 interface. The procedure for establishing a multipath indirect network connection is shown in the fourth embodiment relating to the first aspect.

[0107] Referring to Figure 3, the detailed process of the third embodiment relating to the first aspect will be described below.

[0108] Step 0: A communication path is established between the Remote UE310 and the Network Relay UE300 via the PC5 interface, in accordance with 3GPP TS23.304 (Non-Patent Document 7). The registration procedure is successfully performed by the Network Relay UE300, and the Remote UE310 is authorized to establish a multipath indirect network connection. For example, in Step 0, the Remote UE310 may be registered by performing the process shown in Figure 2. For example, the Network Relay UE300 may be Network Relay UE30001, Network Relay UE30002, or Network Relay UE30003, as shown in Figure 1.

[0109] Step 1: The Remote UE310 sends a UL NAS Transport message to the AMF70 that includes at least one of the following: PDU Session ID, Request Type set for the eMA PDU request, DNN, S-NSSAI, and NAS container. The NAS container may include a PDU Session Establishment Request message, a Service Request message, or any other NAS message for the purpose of establishing an eMA PDU Session, reusing an already established eMA PDU Session, or modifying an already established eMA PDU Session. For example, if the Remote UE310 receives a subscribed eMA PDU, the Remote UE310 may send a UL NAS Transport message.

[0110] The following sections provide a detailed explanation of each parameter. The PDU Session ID is an association between the Remote UE310 and the data network 20 that provides the PDU connection service. For example, the PDU Session ID may be an identifier or identity (ID) that indicates or identifies the association between the Remote UE310 and the data network 20 that provides the PDU connection service. The Request Type set for an eMA PDU request indicates that the Remote UE310 is requesting the establishment of an eMA PDU session. The Request Type set for an eMA PDU may also be expressed as "Request Type=eMA request". The Request Type set for an eMA PDU request may indicate that the Remote UE310 is requesting to communicate via, by, through, or using an eMA PDU session. The Request Type set for an eMA PDU request may indicate that the Remote UE310 is requesting to communicate using a multipath indirect network connection. The Request Type set for an eMA PDU request may indicate that the Remote UE310 is requesting the establishment of a multipath indirect network connection. For example, the Remote UE310 may set the Request Type to eMA PDU request only if the Remote UE310 has eATSSS capability. • DNN is a Data Network Name, equivalent to APN in EPS. A DNN is a reference to a data network. S-NSSAI is a single NSSAI (Single NSSAI) that represents a network slice.

[0111] In one embodiment, any other NAS message embedded in a PDU Session Establishment message, Service Request message, or UL NAS transport message may include the Request Type set in the eMA PDU request.

[0112] The Remote UE310 may send a UL NAS Transport message during the PDU Session Establishment procedure.

[0113] Step 2: Upon receiving a UL NAS Transport message from the Remote UE310, the AMF70 performs SMF selection. For example, the AMF70 may perform SMF selection based on at least one of the received Request Type, S-NSSAI, or DNN configured in the eMA PDU request from the Remote UE310. The AMF70 selects an SMF71 that supports eATSSS functionality, and furthermore, the selected SMF71 must have an associated UPF72 that also supports eATSSS functionality. The selected SMF71 and the UPF72 associated with the SMF71 must have eATSSS capability.

[0114] For example, AMF70 may store information indicating which SMFs have eATSSS capability and which UPFs are associated with those SMFs. For example, based on the stored information, AMF70 may select SMF71 and UPF72, which have eATSSS capability. For example, if AMF70 receives a Request Type set for an eMA PDU request, AMF70 may select SMF71 and UPF72, which have eATSSS capability, based on the stored information. For example, AMF70 may receive information from other network nodes indicating which SMFs have eATSSS capability and which UPFs are associated with those SMFs. For example, AMF70 may know in advance which SMFs and UPFs have eATSSS capability.

[0115] For example, in step 1, the Remote UE310 may provide the AMF70 with evolved ATSSS-LL capability by UL NAS Transport message. The evolved ATSSS-LL capability may indicate that the Remote UE310 is capable of processing multipath indirect network connections, as disclosed herein. The evolved ATSSS-LL capability may indicate that the Remote UE310 is capable of processing or executing evolved Access Traffic Steering, Switching, Splitting (ATSSS) functionality, or processing or executing evolved ATSSS-LL functionality.

[0116] If the AMF70 receives the evolved ATSSS-LL capability, the AMF70 may perform SMF selection in step 2.

[0117] Step 3: If SMF71 is selected, AMF70 sends an Nsmf_PDUSession_CreateSMContext Request message to SMF71, which includes at least one of the following: PDU Session ID, Request Type set for the eMA PDU request, and a NAS message containing a PDU Session Establishment Request message.

[0118] The NAS message may include a Service Request message or any other NAS message as described in step 1, instead of or in addition to the PDU Session Establishment Request message.

[0119] The Nsmf_PDU Session_CreateSMContext Request message may include at least one of the following: User ID (which may be set in the SUPI of Remote UE310), DNN, and S-NSSAI.

[0120] In step 3, the PDU Session ID, DNN, S-NSSAI, Request Type set for the eMA PDU request, and the PDU Session Establishment Request message may be the same as those in step 1.

[0121] Step 4 If SMF71 does not have Session Management Subscriber data, SMF71 may send a Nudm_SDM_Get message to UDM75 that includes at least one of the following: User ID, DNN, S-NSSAI, and Request Type set for the eMA PDU request. The User ID may be set in the SUPI. The User ID may be set in the SUPI of the Remote UE310. For details on the Request Type set for the DNN, S-NSSAI, and eMA PDU request, see Step 1. The Request Type set for the DNN, S-NSSAI, and eMA PDU request in Step 4 may be the same as in Step 1.

[0122] Step 5 Upon receiving a Nudm_SDM_Get message from SMF71, UDM75 may send a Nudm_SDM_Get Response message to SMF71 containing Session Management Subscriber data. The Session Management Subscriber data may include authorized eMA PDUs (eMA PDU allowed). Authorized eMA PDUs indicate that Remote UE310 is authorized to establish an eMA PDU session with at least one of the DNN and S-NSSAI shown in the Nudm_SDM_Get message in Step 4.

[0123] An authorized eMA PDU may indicate that the Remote UE310 is authorized to establish an eMA PDU session. An authorized eMA PDU may indicate that the Remote UE310 is authorized to establish communication via, by, through, or using an eMA PDU session. An authorized eMA PDU may indicate that the Remote UE310 is authorized to establish communication using a multipath indirect network connection.

[0124] The authorized eMA PDU may also indicate the maximum number of PC5 connections that the Remote UE310 can establish with at least one of the DNN and S-NSSAI. The maximum number of PC5 connections is referenced by the SMF71 when it receives a request from the Remote UE310 to add an additional PDU session to an established eMA PDU session. If the request attempts to establish more than the maximum number of PC5 connections, the SMF71 rejects the request and sends an SM rejection message to the Remote UE310. For example, if the request attempts to establish more than the maximum number of PC5 connections, the SMF71 rejects the request and sends an SM rejection message to the Remote UE310 with the cause. The cause may indicate that the request attempts to establish more than the maximum number of PC5 connections. The cause may indicate that the request was rejected because it attempts to establish more than the maximum number of PC5 connections.

[0125] For example, if SMF71 determines that the request would reach the maximum number of PC5 connections for Remote UE310, SMF71 may reject the request and send an SM rejection message to Remote UE310.

[0126] For example, if the SMF71 determines that establishing a PC5 connection as a result of that request would cause the current number of PC5 connections on the Remote UE310 to exceed the maximum number of PC5 connections, the SMF71 may reject the request and send an SM rejection message to the Remote UE310.

[0127] Step 6: SMF71 sends the Nsmf_PDUSession_CreateSMContext Response message to AMF70.

[0128] For example, if SMF71 receives an Nsmf_PDUSession_CreateSMContext Request message and already has Session Management Subscriber data, SMF71 does not need to send a Nudm_SDM_Get message. In this case, SMF71 may send an Nsmf_PDUSession_CreateSMContext Response after receiving the Nsmf_PDUSession_CreateSMContext Request message.

[0129] For example, if SMF71 receives a Nudm_SDM_Get Response message, SMF71 will send an Nsmf_PDU Session_CreateSMContext Response.

[0130] Step 7 If SMF71 does not have a PCF association, SMF71 may send an Npcf_SMPolicyControl_Create message to PCF73 that includes at least one of the following: User ID, DNN, S-NSSAI, Request Type set for the eMA PDU request, and eATSSS capability. The User ID may be set in the SUPI. The User ID may be set in the SUPI of the Remote UE310. The eATSSS capability indicates the capability of at least one of SMF71 and associated UPF72 to handle eATSSS functionality.

[0131] For example, eATSSS capability may indicate that at least one of SMF71 and UPF72 supports advanced ATSSS functionality.

[0132] For example, eATSSS capability may indicate that at least one of SMF71 and UPF72 supports the advanced ATSSS-LL function.

[0133] For example, eATSSS capability may indicate that at least one of SMF71 and UPF72 supports multipath indirect network connectivity.

[0134] For details on the Request Type set for DNN, S-NSSAI, and eMA PDU requests, please refer to Step 1.

[0135] The Request Type set for the DNN, S-NSSAI, and eMA PDU requests in Step 7 may be the same as that in Step 1.

[0136] In step 7, the User ID, DNN, S-NSSAI, and Request Type set for the eMA PDU request may be the same as those sent in step 4.

[0137] For example, if SMF71 has an association with PCF or has an eATSSS policy (e.g., the eATSSS policy for Remote UE310), SMF71 does not need to perform step 7.

[0138] Step 8 When PCF73 receives the Npcf_SMPolicyControl_Create message from SMF71, it may inspect the request and provide an eATSSS policy. The eATSSS policy may be included in the PCC Rule. PCF73 may create the eATSSS policy. The eATSSS policy is created based on the eATSSS capability and Subscription data. The Subscription data may be for the Remote UE310. PCF73 may create the eATSSS policy based on a local policy or local configuration in PCF73. PCF73 may pre-download the Subscription data for the Remote UE310 from UDM75. The eATSSS policy may be a policy for at least one of the following: eATSSS, eATSSS functionality, and eATSSS-LL functionality.

[0139] The eATSSS policy may include permitted eMA PDUs. The PCC Rule may also include permitted eMA PDUs. See Step 5 for details on permitted eMA PDUs.

[0140] For example, if the Subscription data includes information indicating that the Remote UE310 is permitted to establish an eMA PDU session to at least one of the DNN and S-NSSAI, as shown in the Npcf_SMPolicyControl_Create message in step 7, and the PCF73 receives the eATSSS capability, the PCF73 may create or generate an eATSSS policy containing the permitted eMA PDU.

[0141] For example, if the Subscription data includes information indicating that the Remote UE310 is permitted to establish an eMA PDU Session, and the PCF73 receives the eATSSS capability, the PCF73 may create or generate an eATSSS policy that includes the permitted eMA PDU.

[0142] For example, PCF73 may create or generate an eATSSS policy that includes an eMA PDU when it receives eATSSS capability, which includes multi-path relay capability for Remote UE310 in the Subscription data.

[0143] For example, an eATSSS policy may include information for generating an eATSSS Rule.

[0144] For example, an eATSSS policy may include information to determine the proportion of SDF traffic transmitted through each 3GPP access. This information may be used to determine the "Load-Balancing" rule in the eATSSS rule.

[0145] For example, an eATSSS policy may include information for determining priority for each 3GPP access. This information may be used for the "Priority-based" rule in the eATSSS rule.

[0146] SMF71 generates eATSSS rules and N4 rules for UPF72 based on the eATSSS policy received from PCF73. The eATSSS rule may be included in the N4 rule. Alternatively, the N4 rule may be included in the eATSSS rule.

[0147] For example, SMF71 may generate eATSSS Rules based on local policies or local configurations within SMF71.

[0148] For example, SMF71 may generate an eATSSS Rule based on the received eATSSS policy, as well as at least one of the local policies and local configurations within SMF71.

[0149] For example, SMF71 may generate an eATSSS Rule based on the information described above in the eATSSS policy. The information described above in the eATSSS policy may be pre-stored in SMF71.

[0150] For example, an eATSSS Rule may include an eATSSS policy. For example, SMF71 may generate an eATSSS Rule by including an eATSSS policy in the eATSSS Rule.

[0151] Step 9: SMF71 sends an N4 Session Establishment message to UPF72, which includes the PDU Session ID, the Request Type set for the eMA PDU request, and at least one of the eATSSS Rules, in order to reserve a user plane resource for the eMA PDU Session and install the eATSSS Rule.

[0152] Step 10: After successfully reserving the eMA PDU Session resource and installing the eATSSS Rule, UPF72 sends an N4 Session Establishment Response message to SMF71.

[0153] Step 11 SMF71 sends a Namf_Communication_N1N2MessageTransfer message to AMF70, which contains an N1 SM container. The N1 SM container contains a PDU Session Establishment Accept message, a Service Accept message, or any other NAS message. The PDU Session Establishment Accept message, or any other SM message (e.g., a Service Accept message or any other NAS message), contains the eMA PDU status and the eATSSS Rule. The eMA PDU status indicates the status of the eMA PDU session, indicating whether 5GS (e.g., the network) accepts the request to establish an eMA PDU session.

[0154] The eMA PDU status may indicate whether 5GS accepts the request to establish an eMA PDU session.

[0155] The eMA PDU status may indicate that 5GS accepts the request to establish an eMA PDU session.

[0156] For example, SMF71 may configure an eMA PDU status that indicates whether 5GS will accept a request to establish an eMA PDU Session, based on a local policy or local configuration within SMF71.

[0157] For example, SMF71 may configure an eMA PDU status that indicates 5GS will accept the request to establish an eMA PDU Session if steps 4 through 10 are completed successfully.

[0158] For example, if a PC5 connection is established by request, and the current number of PC5 connections on the Remote UE310 does not exceed the maximum number of PC5 connections (which may be as described in step 5), the SMF71 may configure an eMA PDU status indicating that 5GS accepts the request to establish an eMA PDU Session.

[0159] The eMA PDU status may also indicate the maximum number of PC5 connections that the Remote UE310 can establish with at least one of the DNN and S-NSSAI. If the Remote UE310 adds further PDU sessions to an established eMA PDU Session, the maximum number of PC5 connections is remembered and referenced by the Remote UE310. The Remote UE310 may request to add further PDU sessions to the established eMA PDU Session up to the maximum number of PC5 connections received. The SMF71 may send the eMA PDU status to the UPF72. The SMF71 may generate the eMA PDU status in step 9 and send it to the UPF72.

[0160] The eMA PDU status may indicate that 5GS does not accept the request to establish an eMA PDU session. The eMA PDU status indicating that 5GS does not accept the request to establish an eMA PDU session may be included in the SM rejection message sent to the Remote UE310, as described in step 5. The eMA PDU status indicating that 5GS does not accept the request to establish an eMA PDU session may be included in the rejection message (e.g., a PDU Session Establishment Reject message) sent to the Remote UE310. For example, the PDU Session Establishment Reject message may be included in the N1 SM container.

[0161] For example, if steps 4 through 10 do not complete successfully, SMF71 may configure an eMA PDU status that indicates 5GS will not accept the request to establish an eMA PDU Session.

[0162] For example, if a PC5 connection is established by request and the current number of PC5 connections on the Remote UE310 exceeds the maximum number of PC5 connections (which may be as described in step 5), the SMF71 may configure an eMA PDU status indicating that 5GS will not accept the request to establish an eMA PDU Session.

[0163] Step 12: The AMF70 sends a DL NAS Transport message to the Remote UE310 that includes a PDU Session Establishment Accept message, a Service Accept message, or any other NAS message. The PDU Session Establishment Accept message, or any other SM message (e.g., a Service Accept message or any other NAS message), includes the eMA PDU status and eATSSS Rule. For details on the eMA PDU status and eATSSS Rule, see Step 11.

[0164] The order of Step 4 and Step 7 can be reversed.

[0165] (Modification 1 of the third embodiment relating to the first aspect) If the Remote UE310 sends a PDU Session Establishment Request message in step 1 to add an additional PC5 connection to an existing eMA PDU Session, and receives an SM rejection message or a PDU Session Establishment Reject message, the Remote UE310 will not add the new PC5 connection due to the rejection, but will maintain the PC5 connections already established for the eMA PDU Session. This rejection does not affect the existing PC5 connections for the eMA PDU Session.

[0166] (Fourth embodiment relating to the first aspect) A fourth embodiment relating to the first aspect includes how multipath indirect network connectivity can be established and updated based on the movement of the Remote UE310 using Figures 4 and 5.

[0167] Figure 4 shows an example of Remote UE movement. In Figure 4, Remote UE310 moves from left to right.

[0168] At point 0, the Remote UE310 is in the RM-DEREGISTERED state. For example, the Remote UE310 switches on at point 0 after successfully completing the deregistration procedure.

[0169] At point 1: By moving, the Remote UE310 is within the coverage of the Network Relay UE30001, so the Remote UE310 can recognize signals from the Network Relay UE30001.

[0170] Regarding point 2: Since the Remote UE310 has coverage for both Network Relay UE30001 and Network Relay UE30002, it can recognize signals from both Network Relay UE30001 and Network Relay UE30002.

[0171] In point 3: Since Remote UE310 is outside the coverage of Network Relay UE30001 but within the coverage of Network Relay UE30002, Remote UE310 can only recognize signals from Network Relay UE30002.

[0172] Figure 5 illustrates how a multipath indirect network connection is configured and how it reverts back to a single-path indirect network connection, using the Remote UE310's behavior as an example.

[0173] Figure 5 shows an example of a multipath indirect network connection using the advanced ATSSS function. Referring to both Figures 4 and 5, the detailed procedure of the fourth embodiment relating to the first aspect is described below.

[0174] The steps in Figure 5 will be explained below.

[0175] Step 0-1: The Network Relay UE30001 performs the registration procedure with the AMF70, establishing at least one PDU session with the SMF71 and UPF72.

[0176] Step 0-2: Network Relay UE30002 performs a registration procedure with AMF70, establishing at least one PDU session with SMF71 and UPF72. In one embodiment, SMF71 and UPF72 may be the same as or different from those for Network Relay UE30001. *Point 1: Remote UE only recognizes Network Relay UE30001.

[0177] Step 1: When the Remote UE310 recognizes a signal from the Network Relay UE30001, the Remote UE310 performs UE-to-NW Relay Discovery and Selection with the Network Relay UE30001 in accordance with 3GPP TS23.304 (Non-Patent Document 7).

[0178] Step 2 After successfully performing UE-to-NW Relay Discovery and Selection with Network Relay UE30001 in Step 1, Remote UE310 initiates the Registration procedure disclosed in the second embodiment relating to the first aspect.

[0179] Step 3 After the registration procedure is successful, Remote UE310 initiates the MA PDU Session Establishment procedure via, for, or against Network Relay UE30001, as disclosed in the third embodiment relating to the first aspect. The procedure included in the third embodiment relating to the first aspect may be referred to as the MA PDU Session Establishment procedure, or the eMA PDU Session Establishment procedure, the PDU Session Establishment procedure for MA PDU Session, the PDU Session Establishment procedure for eMA PDU Session, and so on.

[0180] After the MA PDU Session Establishment procedure is successful, the Remote UE310 communicates with AF201 in the data network 20 using a single connection path between the Remote UE310 and UPF72.

[0181] At this point, at least one of the Remote UE310, AMF70, SMF71, and UPF72 stores the eMA PDU status and the eATSSS Rule for managing the multi-path indirect network connection.

[0182] At this point, the eATSSS-LL function is installed in both the Remote UE310 and the UPF72.

[0183] For example, the Remote UE310 may be regarded as having the eATSSS-LL function installed if the Remote UE310 receives at least one of the eMA PDU status and the eATSSS Rule. For example, if the UPF72 receives at least one of the eMA PDU status and the eATSSS Rule, the UPF72 may be regarded as having the eATSSS-LL function installed.

[0184] For example, the Remote UE310 may communicate via the Network Relay UE30001 based on the eATSSS Rule received in step 3.

[0185] For example, the Remote UE310 may execute the eATSSS function or the eATSSS-LL function based on the eATSSS Rule received in step 3. *Point 2: The Remote UE recognizes both the Network Relay UE30001 and the Network Relay UE30002.

[0186] Step 4 When Remote UE310 recognizes the signal from Network Relay UE30002, Remote UE310 performs UE-to-NW Relay Discovery and Selection with Network Relay UE30002 according to 3GPP TS23.304 (Non-Patent Document 7). For example, Remote UE310 may perform UE-to-NW Relay Discovery and Selection with Network Relay UE30002 while maintaining the PDU session established in Step 3.

[0187] Step 5 After successfully performing UE-to-NW Relay Discovery and Selection with Network Relay UE30002 in Step 4, Remote UE310 starts the MA PDU Session Establishment procedure in, for, or with Network Relay UE30002, as disclosed in the third embodiment regarding the first aspect.

[0188] For example, Remote UE310 may start the MA PDU Session Establishment procedure via Network Relay UE30002 while maintaining the PDU session established in Step 3.

[0189] For example, when Remote UE310 starts the MA PDU Session Establishment procedure in Step 5, Remote UE310 may use the same PDU Session ID as that used in Step 3.

[0190] After successfully completing the MA PDU Session Establishment procedure, Remote UE310 communicates with AF201 in data network 20 using two connection paths between Remote UE310 and UPF72.

[0191] At this point, at least one of the Remote UE310, AMF70, SMF71, and UPF72 updates the eMA PDU status and eATSSS Rule to manage multipath indirect network connectivity.

[0192] For example, at least one of the Remote UE310, AMF70, SMF71, and UPF72 may store at least one of the eMA status and eATSSS Rule generated or received in step 5.

[0193] For example, at least one of the Remote UE310, AMF70, SMF71, and UPF72 may store at least one of the eMA statuses and eATSSS rules generated or received in step 5, independently of those stored in step 3.

[0194] At this point, two connection paths are established between the Remote UE310 and the UPF72, enabling high resilience for data connectivity.

[0195] For example, at this point, Remote UE310 may communicate via Network Relay UE30001 and Network Relay UE30002.

[0196] For example, at this point, Remote UE310 may communicate simultaneously via Network Relay UE30001 and Network Relay UE30002.

[0197] For example, Remote UE310 may communicate via Network Relay UE30001 based on at least one of the eATSSS Rules received in step 3 and the eATSSS Rule received in step 5.

[0198] For example, Remote UE310 may communicate via Network Relay UE30002 based on at least one of the eATSSS Rules received in step 3 and the eATSSS Rule received in step 5.

[0199] For example, the Remote UE310 may perform the eATSSS function or the eATSSS-LL function based on at least one of the eATSSS Rules received in step 3 and the eATSSS Rule received in step 5.

[0200] In one embodiment, if the Remote UE310 recognizes a signal from RAN5, the Remote UE310 may initiate an MA PDU Session Establishment procedure (e.g., a PDU Session Establishment procedure for an MA PDU Session, or a PDU Session Establishment procedure for an eMA PDU Session) using the Uu interface to RAN5. In this case, the UE-to-NW Relay Discovery and Selection in step 4 are not performed. *Point 3: Remote UE only recognizes Network Relay UE30002.

[0201] Step 6 If, due to the distance between Remote UE310 and Network Relay UE30001, for example, weak signal strength, Remote UE310 is unable to maintain a communication path with Network Relay UE30001 via the PC5 interface, Network Relay UE30001 may initiate a PDU Session Release procedure, triggered, for example, by a lower-layer Radio Link Failure (RLF), as described in 3GPP TS23.502 (Non-Patent Literature 4), Section 4.3.4.2.

[0202] After the PDU Session Release procedure is successful, the Remote UE310 communicates with AF201 in data network 20 using a single connection path between the Remote UE310 and UPF72.

[0203] For example, Remote UE310 may communicate via Network Relay UE30002 based on the eATSSS Rule received in step 5.

[0204] For example, the Remote UE310 may execute the eATSSS function or the eATSSS-LL function based on the eATSSS Rule received in step 5.

[0205] At this point, at least one of the Remote UE310, AMF70, SMF71, and UPF72 updates the eMA PDU status and eATSSS Rule to manage multipath indirect network connectivity.

[0206] For example, during or after the PDU Session Release procedure, at least one of Remote UE310, AMF70, SMF71, and UPF72 may delete the eMA PDU status and eATSSS Rule stored in step 3, or replace the eMA PDU status and eATSSS Rule stored in step 3 with the eMA PDU status and eATSSS Rule generated or received in step 5.

[0207] For example, if the Remote UE310 is initially located at point 2 (e.g., if the Remote UE310 is switched on at point 2), the Remote UE310 may execute steps 1 to 5. In this case, the Remote UE310 may first execute steps 1 to 3 and then execute steps 4 and 5, or the Remote UE310 may first execute steps 4, 2, and 5 and then execute steps 1 and 3.

[0208] For example, the Remote UE310 may execute an evolved Access Traffic Steering, Switching, Splitting (ATSSS) function or an evolved ATSSS-LL function based on the received eATSSS Rule.

[0209] For example, at point 1 or 2, the Remote UE310 may perform communication via the Network Relay UE30001 based on the received eATSSS Rule (e.g., this communication includes transmitting uplink data). If 3GPP access and non-3GPP access are available for communication via the Network Relay UE30001, the Remote UE310 may perform communication via the Network Relay UE30001 using 3GPP access or non-3GPP access. The Remote UE310 may determine which access is used for communication based on the eATSSS Rule.

[0210] For example, at point 2 or 3, Remote UE310 may perform communication via Network Relay UE30002 based on the received eATSSS Rule (for example, this communication may include sending uplink data). If both 3GPP access and non-3GPP access are available for communication via Network Relay UE30002, Remote UE310 may perform communication via Network Relay UE30002 using either 3GPP access or non-3GPP access. Remote UE310 may determine which access to use for communication based on the eATSSS Rule.

[0211] For example, UPF72 may perform an evolved Access Traffic Steering, Switching, Splitting (ATSSS) function or an evolved ATSSS-LL function based on the received eATSSS Rule.

[0212] For example, at point 1 or 2, UPF72 may perform communication via Network Relay UE30001 based on the received eATSSS Rule (for example, this communication may include sending downlink data). If both 3GPP and non-3GPP access are available for communication via Network Relay UE30001, UPF72 may perform communication via Network Relay UE30001 using either 3GPP or non-3GPP access. UPF72 may determine which access to use for communication based on the eATSSS Rule.

[0213] For example, at point 2 or 3, UPF72 may perform communication via Network Relay UE30002 based on the received eATSSS Rule (for example, this communication may include sending downlink data). If both 3GPP and non-3GPP access are available for communication via Network Relay UE30002, UPF72 may perform communication via Network Relay UE30002 using either 3GPP or non-3GPP access. UPF72 may determine which access to use for communication based on the eATSSS Rule.

[0214] Executing the Advanced Access Traffic Steering, Switching, Splitting (ATSSS) function or the Advanced ATSSS-LL function based on the received eATSSS Rule may include the aforementioned communication via Remote UE310 or UPF72.

[0215] The eATSSS Rule may be used to perform the Advanced Access Traffic Steering, Switching, Splitting (ATSSS) function or the Advanced ATSSS-LL function.

[0216] The eATSSS Rule may also be information for performing the Advanced Access Traffic Steering, Switching, Splitting (ATSSS) function or the Advanced ATSSS-LL function.

[0217] The eATSSS Rule may include information for controlling the aforementioned communication via Remote UE310 or UPF72.

[0218] The eATSSS Rule may be represented as information for controlling or executing the aforementioned communication by Remote UE310 or UPF72.

[0219] The eATSSS Rule may be represented as information for controlling or executing communication in a multipath indirect network connection.

[0220] For example, multipath indirect network connectivity may include connectivity via or through Network Relay UE30001, and connectivity via or through Network Relay UE30002.

[0221] The above-described problems can be solved according to the first embodiment and at least one of the variations thereof.

[0222] For example, the first embodiment and at least one of its modifications can solve the problem that the above-mentioned service requirements are not yet supported by 5GS.

[0223] For example, the first embodiment and at least one of its modifications can solve the problem that the 3GPP specification lacks a mechanism for achieving the aforementioned service requirements.

[0224] For example, the first embodiment and at least one variation thereof can solve the problem that, when 5GS does not support multipathing for indirect network connectivity, the Remote UE (or Remote UE) cannot avoid sudden interruptions or disconnections of connectivity services via indirect network connectivity due to unstable communication over a single connection between the Remote UE and the Network Relay UE.

[0225] For example, the first embodiment and at least one of its modifications can solve the problem that the user experience in indirect network connections is impaired due to unstable connections via a single connection between the Remote UE and the Network Relay UE.

[0226] For example, according to the first embodiment and at least one of its modifications, a procedure for achieving multipath indirect network connections (e.g., an evolved Multi Access-PDU (MA PDU) session) is disclosed, and a Remote UE can establish multipath indirect network connections. Thus, the aforementioned problems can be solved.

[0227] (Second aspect) This embodiment discloses a mechanism for configuring multipath for indirect network connectivity using multiple Network Relay UEs by establishing multiple PDU sessions between a Remote UE and its anchor UPF. This functionality may also be called an evolved PDU Session for multipath indirect network communication.

[0228] The 5G ProSe UE-to-Network Relay UE300 enables multi-path indirect communication connections between the 5G core network (5GC) and the Remote UE310. These multi-path indirect connections provide high resilience to data connectivity (for example, they can maintain data connectivity for a UE even if it loses coverage of the single Network Relay UE it is connected to).

[0229] (First embodiment relating to the second aspect) Figure 6 includes a reference architecture that supports multipath indirect network connectivity between Remote UE310 and 5GC in both PLMN-to-PLMN and non-roaming / roaming scenarios. Figure 6 shows a network connectivity model that supports multipath indirect network connectivity using multiple PDU Sessions. The multipath indirect network connectivity provides a data communication path between Remote UE310 and AF201 in data network 20.

[0230] Multipath indirect network communication is a mode of network communication that has multiple connection paths, such as between Remote UE310 and UPF(PSA)72004 via Network Relay UE30001, RAN501, and Relay UE UPF72001; between Remote UE310 and UPF(PSA)72004 via Network Relay UE30002, RAN502, and Relay UE UPF72002; and between Remote UE310 and UPF(PSA)72004 via Network Relay UE30003, RAN503, and Relay UE UPF72003.

[0231] UPF(PSA)72004 is an anchor UPF for multipath indirect network communication, and UPF(PAS)72004 includes an evolved ATSSS for multiple PDU session rules to perform or maintain multipath indirect network communication. The evolved ATSSS for multiple PDU session rules may also be called an mATSSS Rule.

[0232] In one embodiment, the Remote UE310 may connect directly to the RAN5 via the Uu interface to configure a multipath indirect network connection while establishing other connections via the Network Relay UE300 and RAN5.

[0233] The mATSSS Rule is used to structure and maintain multipath indirect network communications, similar to the disclosure in the first embodiment. For example, the mATSSS Rule may be used in the same manner as the eATSSS Rule.

[0234] The main difference between the first and second embodiments is that the first embodiment uses only one PDU Session ID and one end-user IP address of an MA PDU Session (or eMA PDU Session) to configure multipath indirect network communication, whereas the second embodiment uses multiple independent PDU Sessions, i.e., multiple PDU Session IDs and multiple associated end-user IP addresses to configure multipath indirect network communication.

[0235] The mATSSS Rule is installed on both the Remote UE310 and the UPF(PSA)72004.

[0236] In addition to the eATSSS Rule, the mATSSS Rule addresses multiple independent PDU Sessions used for multipath indirect network communication by the evolved ATSSS-LL for multiple PDU Session functionality. The mATSSS Rule may include other mATSSS Rules. For example, the mATSSS Rule may be used to achieve the evolved ATSSS-LL for multiple PDU Session functionality. For example, the mATSSS Rule may be associated with the evolved ATSSS-LL for multiple PDU Session functionality. The evolved ATSSS-LL for multiple PDU Session functionality includes at least one of the following features: • Functionality similar to the eATSSS-LL function in Remote UE310. Based on the mATSSS Rule, Remote UE310 performs at least one of the following to handle uplink user packets between multiple established PDU sessions: Multi-Active-Standby, Smallest Delay, Load-Balancing, and Priority-based. In other words, the eATSSS-LL function may be applied to multiple PDU sessions. • Network Address Translation (NAT) functionality in Remote UE310. Remote UE310 maintains a representative end-user IP address for multipath indirect network connectivity. This representative end-user IP address represents a unique end-user IP address for applications within Remote UE310 for multipath indirect network communication. When Remote UE310 receives a downlink packet from one of the associated PDU sessions, it performs the NAT function to exchange the received end-user IP address with the representative end-user IP address and forwards the downlink data (e.g., downlink packets) to the application within Remote UE310. By using this NAT function, applications within Remote UE310 can recognize a single instance of IP connectivity with AF201 within the data network 20. • Functionality similar to the ATSSS-LL function of UPF(PSA)72004. Based on the mATSSS Rule, UPF(PSA)72004 performs at least one of the following to process downlink user packets between multiple established PDU sessions: Multi-Active-Standby, Smallest Delay, Load-Balancing, and Priority-based. This function may also be called the Downlink Classifier for downlink data processing, meaning that the eATSSS-LL function may be applied to multiple PDU sessions. By using the Downlink Classifier function, downlink data arriving from AF201 in the data network 20 can be distributed to multiple established PDU sessions. • NAT function of UPF(PSA)72004. The UPF(PSA)72004 maintains a representative end-user IP address for multipath indirect network connectivity. The representative end-user IP address represents a unique end-user IP address for AF201 in data network 20 for multipath indirect network communication. When the UPF(PSA)72004 receives an uplink packet from one of the associated PDU sessions, the UPF(PSA)72004 performs the NAT function to exchange the received end-user IP address with the representative end-user IP address and forwards the uplink data (e.g., uplink packets) to AF201 in data network 20. By using this NAT function, AF201 in data network 20 can recognize a single instance of IP connectivity with Remote UE310.

[0237] In one embodiment, RAN501 can be directly connected to UPF(PSA)72004 without Relay UE UPF72001. In one embodiment, RAN502 can be directly connected to UPF(PSA)72004 without Relay UE UPF72002. In one embodiment, RAN503 can be directly connected to UPF(PSA)72004 without Relay UE UPF72003. In another embodiment, RAN501, RAN502, and RAN503 can be directly connected to UPF(PSA)72004 without Relay UE UPF72001, Relay UE UPF72002, and Relay UE UPF72003.

[0238] As shown in Figure 6, Remote UE310 establishes multiple indirect network communication paths to 5GC. Remote UE310 and Network Relay UE30001, 30002, and 30003 may belong to the same PLMN or different PLMNs, and furthermore, two or more Network Relay UE30001, 30002, and 30003 may belong to different PLMNs. Remote UE310 may also be in a roaming location, and if Remote UE310 is in a VPLMN, N3IWF can be used to connect Remote UE310 to its HPLMN.

[0239] The Remote UE310 may be simultaneously connected to two or more RAN5s using multi-connectivity as defined in 3GPP TS37.340 (Non-Patent Document 8). For example, RAN501 can be a Master Node (MN) for multipath indirect network communication, while RAN502 can be a Secondary Node (SN). In this case, UPF72001 and UPF72002 can be the same UPF72.

[0240] Core Network entities that provide services to Remote UE310 (e.g., including AMF70, SMF71, UPF72, etc.) may be the same as the Core Network entities of Network Relay UE300. Core Network entities that provide services to Remote UE310 (e.g., including AMF70, SMF71, UPF72, etc.) may be different from the Core Network entities of Network Relay UE300. RAN5 can be used by multiple different Layer3 UE-to-Network Relays to the network. RAN5 can be shared by 5GC via Multi-Operator Core Network. UPF72 may include UPF72001, UPF72002, UPF72003, UPF72004, etc.

[0241] The reference architecture supports creating multiple PDU sessions between Remote UE310 and UPF(PAS)72004 using Relay UE UPF72001, Relay UE UPF72002, and Relay UE UPF72003. The mATSSS function allows routing of user traffic through multiple indirect network communication paths between Remote UE310 and UPF(PSA)72004.

[0242] Relay UE UPF72001, Relay UE UPF72002, and Relay UE UPF72003 may be connected to one or more UPF(PSA)72004 for each UE-to-Network Relay connection. A UE-to-Network Relay connection may be established for each Relay Service Code (RSC). A UE-to-Network Relay connection may be established for each DNN and / or S-NSSAI. The expression "A and / or B" may mean "at least one of A and B" in this disclosure.

[0243] The Advanced Access Traffic Steering, Switching, Splitting (ATSSS) functionality for Multiple PDU Sessions may also be called, for example, ATSSS for Multipath Indirect Network Connectivity for Multiple PDU Sessions, Multi Path ATSSS (mMPATSSS), Advanced ATSSS for Multiple PDU Sessions (mATSSS), or mATSSS functionality.

[0244] The capabilities of the Advanced ATSSS function for Multiple PDU Sessions in SMF71 and UPF72 (e.g., UPF72001, UPF72002, UPF72003, UPF72004, etc.) can be expressed as Advanced ATSSS capability for Multiple PDU Sessions. This Advanced ATSSS capability for Multiple PDU Sessions may also be called, for example, mATSSS capability.

[0245] The capability of the advanced ATSSS functionality for multiple PDU sessions may indicate that the SMF71 or UPF72 (e.g., UPF72001, UPF72002, UPF72003, UPF72004, etc.) supports the advanced ATSSS functionality for multiple PDU sessions.

[0246] The capabilities of the advanced ATSSS functionality for multiple PDU sessions may demonstrate that SMF71 or UPF72 (e.g., UPF72001, UPF72002, UPF72003, UPF72004, etc.) can perform the appropriate process using the mATSSS Rule.

[0247] The capability of the evolved ATSSS function for Multiple PDU Sessions may demonstrate that SMF71 or UPF72 (e.g., UPF72001, UPF72002, UPF72003, UPF72004, etc.) can perform at least the evolved ATSSS-LL described above for Multiple PDU Session functionality using the mATSSS Rule.

[0248] The capabilities of the advanced ATSSS feature for multiple PDU sessions may indicate that the SMF71 or UPF72 (e.g., UPF72001, UPF72002, UPF72003, UPF72004, etc.) can perform communication over multipath indirect network connections.

[0249] The capability of the evolved ATSSS function for Multiple PDU Sessions may indicate that the SMF71 or UPF72 (e.g., UPF72001, UPF72002, UPF72003, UPF72004, etc.) can perform communication in a multipath indirect network connection using the mATSSS Rule for Multiple PDU Session functionality, and at least one of the mATSSS function and the evolved ATSSS-LL.

[0250] For example, at least one of the Remote UE310, SMF71, and UPF72 (e.g., UPF72001, UPF72002, UPF72003, UPF72004, etc.) may use the mATSSS Rule to process or execute at least the evolved ATSSS-LL described above for the Multiple PDU Session function.

[0251] For example, at least one of the Remote UE310, SMF71, and UPF72 (e.g., UPF72001, UPF72002, UPF72003, UPF72004, etc.) may perform communication in a multipath indirect network connection using at least one of the mATSSS Rule and evolved ATSSS-LL for multiple PDU session functions.

[0252] Remote UE310, and at least one of SMF71 and UPF72 (e.g., UPF72001, UPF72002, UPF72003, UPF72004, etc.) may store the mATSSS Rule.

[0253] At least one of the following: Remote UE310, SMF71, and UPF72 (e.g., UPF72001, UPF72002, UPF72003, UPF72004, etc.) may have the mATSSS Rule pre-stored.

[0254] Remote UE310, and at least one of SMF71 and UPF72 may have previously received mATSSS rules from other network nodes.

[0255] For example, at least one of the Remote UE310, SMF71, and UPF72 may determine which path is used for communication based on the mATSSS Rule.

[0256] For example, if there are three multipath indirect network connections (e.g., a first connection or path via Network Relay UE30001, a second connection or path via Network Relay UE30002, and a third connection or path via Network Relay UE30003), at least one of Remote UE310, SMF71, and UPF72 may determine, based on the mATSSS Rule, which of the connections or paths is used for communication.

[0257] The policy for the Advanced ATSSS feature for Multiple PDU Sessions in PCF73 can be expressed as the Advanced ATSSS policy for Multiple PDU Sessions. This Advanced ATSSS policy for Multiple PDU Sessions may also be called, for example, the mATSSS policy.

[0258] The advanced ATSSS-LL for Multiple PDU Session functionality may also be called, for example, ATSSS-LL for multipath indirect network connectivity for Multiple PDU Session, Multi Path ATSSS-LL (mMPATSSS-LL), Advanced ATSSS-LL for Multiple PDU Session (mATSSS-LL), Advanced ATSSS-LL functionality for Multiple PDU Session, or mATSSS-LL functionality.

[0259] The advanced ATSSS Rule for Multiple PDU Session functionality may also be called, for example, the ATSSS Rule for Multipath Indirect Network Connections for Multiple PDU Session functionality, meATSSS Rule, Multi Path ATSSS Rule (mMPATSSS Rule) for Multiple PDU Session functionality, the advanced STSSS Rule for Multiple PDU Session functionality (mATSSS Rule), or mATSSS Rule.

[0260] An evolved PDU Session for multipath indirect network communication may also be called, for example, a PDU Session for multipath indirect network communication (mPDU Session).

[0261] Communication in a multipath indirect network connection, or communication performed in a multipath indirect network connection, may include communication in, by, via, or using an mPDU Session.

[0262] Advanced Access Traffic Steering, Switching, Splitting (ATSSS) functionality for Multiple PDU Sessions may include Advanced ATSSS-LL for Multiple PDU Session functionality.

[0263] Advanced ATSSS-LL functionality for multiple PDU sessions may include advanced Access Traffic Steering, Switching, Splitting (ATSSS) functionality for multiple PDU sessions.

[0264] The mATSSS Rule may be used for at least one of the following: the Advanced Access Traffic Steering, Switching, Splitting (ATSSS) functionality for Multiple PDU Sessions, and the Advanced ATSSS-LL functionality for Multiple PDU Sessions.

[0265] An evolved ATSSS Rule may be a rule used for at least one of the following: the evolved Access Traffic Steering, Switching, Splitting (ATSSS) function for Multiple PDU Sessions, and the evolved ATSSS-LL function for Multiple PDU Sessions.

[0266] (Second embodiment relating to the second aspect) A second embodiment relating to the second aspect discloses a Registration Procedure for Remote UE310 corresponding to an mPDU Session.

[0267] Figure 2 in the second embodiment relating to the first aspect is used for the Remote UE310 Registration Procedure corresponding to an mPDU Session with the following modifications. • The Multi-path relay capability in Step 1 of Figure 2 indicates that the Remote UE310 supports processing mPDU Sessions. The Multi-path relay capability may be replaced with mATSSS capability. mATSSS capability may be used instead of Multi-path relay capability. mATSSS capability may indicate that the Remote UE310 supports multipath indirect network connectivity. mATSSS capability may indicate that the Remote UE310 supports connectivity via Network Relay UE30001, Network Relay UE30002, and Network Relay UE30003, as shown in Figure 6. • The eMA PDU subscribed in steps 4 and 5 of Figure 2 can be replaced with a subscribed mPDU Session. A subscribed mPDU Session may be used instead of a subscribed eMA PDU. A subscribed mPDU Session indicates that the Remote UE310 is permitted to establish an mPDU Session as subscriber data. A subscribed mPDU Session indicates that the Remote UE310 is permitted to establish an mPDU Session. There may be a subscribed mPDU Session for each S-NSSAI in the subscribed NSSAI. A subscribed mPDU Session may indicate that the Remote UE310 is permitted to communicate in, by, through, or using the mPDU Session. A subscribed mPDU Session may indicate that the Remote UE310 is permitted to communicate using a multipath indirect network connection.

[0268] (Third embodiment relating to the second aspect) Figure 7 includes an example of a PDU session establishment procedure for a multipath indirect network connection using multiple PDU sessions.

[0269] To configure an mPDU session using multiple Network Relay UE300s, the Remote UE310 needs to repeat the PDU Session establishment procedure in Figure 5 as many times as the Remote UE310 replicates the PC5 connection for the mPDU session.

[0270] This procedure configures the mATSSS Rule on both the Remote UE310 and UPF72, so that user data between the Remote UE310 and AF201 in the data network 20 is processed according to the mATSSS Rule on both the Remote UE310 and UPF72, resulting in reliable user data transmission via the PC5 interface. The procedure for establishing a multipath indirect network connection is shown in the fourth embodiment relating to the second aspect.

[0271] The detailed process of the third embodiment relating to the second aspect will be described below with reference to Figure 7.

[0272] In Figure 7, UPF72 represents UPF(PSA)72004 in Figure 6, and Relay UE UPF72001, Relay UE UPF72002, and Relay UE UPF72003 are not shown because they are coupled to UPF(PSA)72004, or Relay UE UPF72001, Relay UE UPF72002, and Relay UE UPF72003 are unnecessary because RAN501, RAN502, and RAN503 are directly connected to UPF(PSA)72004. For example, as in Figure 6, Relay UE UPF72001, Relay UE UPF72002, Relay UE UPF72003, and UPF(PSA)72004 may be arranged separately. In this case, communication with UPF(PSA)72004 may be performed via at least one of Relay UE UPF72001, Relay UE UPF72002, and Relay UE UPF72003.

[0273] Step 0: A communication path is established between the Remote UE310 and the Network Relay UE300 via the PC5 interface, in accordance with 3GPP TS23.304 (Non-Patent Literature 7). The Registration procedure is successfully performed by the Network Relay UE300, and the Remote UE310 is authorized to establish a multipath indirect network connection. For example, in Step 0, the Remote UE310 may be registered by performing the process of the second embodiment relating to the second aspect. For example, the Network Relay UE300 may be Network Relay UE30001, Network Relay UE30002, or Network Relay UE30003, as shown in Figure 6.

[0274] Step 1: The Remote UE310 sends a UL NAS Transport message to the AMF70 that includes at least one of the following: PDU Session ID, Request Type set in the mPDU request, Linked PDU Session ID, Representative IP address, DNN, S-NSSAI, and NAS container. The NAS container may include a PDU Session Establishment Request message, a Service Request message, or any other NAS message for the purpose of establishing an mPDU Session or adding a new PDU Session to an already established mPDU Session. For example, if the Remote UE310 receives a subscribed mPDU Session, the Remote UE310 may send a UL NAS Transport message.

[0275] The following sections provide a detailed explanation of each parameter. • PDU Session ID: See step 1 of the third embodiment relating to the first aspect. The Request Type set for an mPDU request indicates that the Remote UE310 is requesting the establishment of an mPDU session. The Request Type set for an mPDU request may also be expressed as "Request Type=mPDU request (request)". The Request Type set for an mPDU request may indicate that the Remote UE310 is requesting to communicate via, by, through, or using an mPDU session. The Request Type set for an mPDU request may indicate that the Remote UE310 is requesting to communicate using a multipath indirect network connection. The Request Type set for an mPDU request may indicate that the Remote UE310 is requesting the establishment of a multipath indirect network connection. The Linked PDU Session ID indicates the PDU Session ID representing the mPDU Session. The Linked PDU Session ID is most likely the PDU Session ID of the first PDU Session ID of the mPDU Session. The Linked PDU Session ID may also be the PDU Session ID of the first PDU Session ID of the mPDU Session. The Linked PDU Session ID may also be the PDU Session ID of the mPDU Session. The Linked PDU Session ID may also be the PDU Session ID for communication in a multipath indirect network connection. If the mPDU Session does not have an existing PDU Session ID (for example, the very first PDU Session to constitute the mPDU Session), then the Linked PDU Session ID is not included. The Representative IP address represents the end-user IP address assigned to the Remote UE310 for the mPDU Session. The end-user IP address may be assigned in step 0. The Representative IP address represents the Remote UE310 when it communicates with AF201 in data network 20. The Representative IP address also represents the Remote UE310 when it communicates with applications within the Remote UE310. The Representative IP address may also be the end-user IP address for the mPDU Session. The Representative IP address may also be the end-user IP address for communication in multipath indirect network connections. • DNN: See step 1 of the third embodiment relating to the first aspect. ·S-NSSAI: Refer to step 1 of the third embodiment relating to the first aspect.

[0276] In one embodiment, any other NAS message embedded in a PDU Session Establishment Request message, Service Request message, or UL NAS Transport message may include the Request Type set in the mPDU request.

[0277] The Remote UE310 may send a UL NAS Transport message during the PDU Session Establishment procedure.

[0278] Step 2: Upon receiving a UL NAS Transport message from the Remote UE310, the AMF70 performs SMF selection. For example, the AMF70 may perform SMF selection based on at least one of the received Request Type, Linked PDU Session ID, Representative IP address, S-NSSAI, and DNN configured in the mPDU request from the Remote UE310. The selected SMF71, and the UPF72 associated with the SMF71, must have mATSSS capability.

[0279] For example, AMF70 may store information indicating at least one of the SMFs and UPFs associated with the SMFs that have mATSSS capability. For example, based on the stored information, AMF70 may select at least one of the SMF71 and UPF72 that have mATSSS capability. For example, if AMF70 receives a Request Type set for an mPDU request, AMF70 may select at least one of the SMF71 and UPF72 that have mATSSS capability based on the stored information. For example, AMF70 may receive information from other network nodes indicating at least one of the SMFs and UPFs associated with the SMFs that have mATSSS capability. For example, AMF70 may know in advance which SMFs and UPFs have mATSSS capability.

[0280] When a Linked PDU Session ID is received, the AMF70 selects the SMF71 associated with the PDU Session in the Linked PDU Session ID that the Remote UE310 is connected to. For example, when a Linked PDU Session ID is received, the AMF70 may select the SMF71 associated with the PDU Session identified by the Linked PDU Session ID. In this way, the same SMF71 managing the mPDU Session is correctly selected by the AMF70.

[0281] The AMF70 may store information indicating the relationship between the SMF and the PDU Session (or PDU Session ID), and based on the stored information, the AMF70 may select an SMF71 associated with the PDU Session identified by the Linked PDU Session ID.

[0282] Step 3: If SMF71 is selected, AMF70 sends an Nsmf_PDUSession_CreateSMContext Request message to SMF71, which includes at least one of the following: PDU Session ID, Request Type set in the mPDU request, Linked PDU Session ID, Representative IP address, and a NAS message containing a PDU Session Establishment Request message.

[0283] The NAS message may include a Service Request message or any other NAS message as described in step 1, instead of or in addition to the PDU Session Establishment Request message.

[0284] The Nsmf_PDUSession_CreateSMContext Request message may include at least one of the following: User ID, DNN, and S-NSSAI (the User ID may be set in the SUPI of the Remote UE310).

[0285] The PDU Session ID, DNN, S-NSSAI, Request Type set for the mPDU request, and PDU Session Establishment Request message in Step 3 may be the same as those in Step 1.

[0286] Step 4 If SMF71 does not have Session Management Subscriber data, SMF71 may send a Nudm_SDM_Get message to UDM75 that includes at least one of the following: User ID, DNN, S-NSSAI, and Request Type set for the mPDU request. The User ID may be set in the SUPI. The User ID may be set in the SUPI of the Remote UE310. For details on the Request Type set for the DNN, S-NSSAI, and mPDU request, see Step 1. The Request Type set for the DNN, S-NSSAI, and mPDU request in Step 4 may be the same as those in Step 1.

[0287] Step 5 Upon receiving a Nudm_SDM_Get message from SMF71, UDM75 may send a Nudm_SDM_Get Response message to SMF71 containing Session Management Subscriber data. The Session Management Subscriber data may include permitted mPDUs (mPDU allowed). The permitted mPDUs indicate that Remote UE310 is permitted to establish an mPDU session with at least one of the DNN and S-NSSAI shown in the Nudm_SDM_Get message in Step 4.

[0288] An authorized mPDU may indicate that the Remote UE310 is authorized to establish an mPDU session. An authorized mPDU may indicate that the Remote UE310 is authorized to establish communication in, by, through, or using an mPDU session. An authorized mPDU may indicate that the Remote UE310 is authorized to establish communication using a multipath indirect network connection.

[0289] The permitted mPDU may also indicate the maximum number of PC5 connections that the Remote UE310 can establish with at least one of the DNN and S-NSSAI. The maximum number of PC5 connections is referenced by the SMF71 when it receives a request from the Remote UE310 to add additional PDU sessions to an established mPDU session. If the request attempts to establish more than the maximum number of PC5 connections, the SMF71 rejects the request and sends an SM rejection message to the Remote UE310. For example, if the request attempts to establish more than the maximum number of PC5 connections, the SMF71 rejects the request and sends an SM rejection message to the Remote UE310 with the cause. The cause may indicate that the request attempts to establish more than the maximum number of PC5 connections. The cause may indicate that the request was rejected because it attempts to establish more than the maximum number of PC5 connections.

[0290] For example, if SMF71 determines that the request would reach the maximum number of PC5 connections for Remote UE310, SMF71 may reject the request and send an SM rejection message to Remote UE310.

[0291] For example, if the SMF71 determines that establishing a PC5 connection as a result of that request would cause the current number of PC5 connections on the Remote UE310 to exceed the maximum number of PC5 connections, the SMF71 may reject the request and send an SM rejection message to the Remote UE310.

[0292] Step 6: SMF71 sends the Nsmf_PDUSession_CreateSMContext Response message to AMF70.

[0293] For example, if SMF71 receives an Nsmf_PDUSession_CreateSMContext Request message and already has Session Management Subscriber data, SMF71 does not need to send a Nudm_SDM_Get message. In this case, SMF71 may send an Nsmf_PDUSession_CreateSMContext Response after receiving the Nsmf_PDUSession_CreateSMContext Request message.

[0294] Step 7 If SMF71 is not associated with PCF, SMF71 may send an Npcf_SMPolicyControl_Create message to PCF73 that includes at least one of the following: User ID, DNN, S-NSSAI, Request Type set for the mPDU request, and mATSSS capability. The User ID may be set in the SUPI. The User ID may be set in the SUPI of the Remote UE310. The mATSSS capability indicates the capability of at least one of SMF71 and associated UPF72 to handle mATSSS functionality.

[0295] For example, mATSSS capability may indicate that at least one of SMF71 and UPF72 supports the advanced ATSSS function for Multiple PDU Sessions.

[0296] For details on the Request Type set for DNN, S-NSSAI, and mPDU requests, please refer to Step 1.

[0297] The Request Type set for the DNN, S-NSSAI, and mPDU requests in Step 7 may be the same as that in Step 1.

[0298] The User ID, DNN, S-NSSAI, and Request Type set for the mPDU request in Step 7 may be the same as those sent in Step 4.

[0299] For example, if SMF71 has an association with PCF or has an mATSSS policy (e.g., the mATSSS policy for Remote UE310), SMF71 does not need to perform step 7.

[0300] Step 8 When PCF73 receives the Npcf_SMPolicyControl_Create message from SMF71, it may inspect the request and provide an mATSSS policy. The mATSSS policy may be included in the PCC Rule. PCF73 may create the mATSSS policy. The mATSSS policy is created based on the mATSSS function and Subscription data. The Subscription data may be for the Remote UE310. PCF73 may create the mATSSS policy based on a local policy or local configuration within PCF73. PCF73 may pre-download the Subscription data for the Remote UE310 from UDM75. The mATSSS policy may be a policy for at least one of the following: mATSSS, mATSSS function, and mATSSS-LL function.

[0301] The mATSSS policy may include permitted mPDUs. The PCC Rule may also include permitted mPDUs. See Step 5 for details on permitted mPDUs.

[0302] For example, if the Subscription data includes information indicating that the Remote UE310 is permitted to establish an mPDU session with at least one of the DNN and S-NSSAI shown in the Npcf_SMPolicyControl_Create message in step 7, and the PCF73 receives the mATSSS capability, the PCF73 may create or generate an mATSSS policy containing the permitted mPDU.

[0303] For example, if the Subscription data includes information indicating that the Remote UE310 is permitted to establish an mPDU session, and the PCF73 receives the mATSSS capability, the PCF73 may create or generate an mATSSS policy that includes the permitted mPDU.

[0304] For example, if the Subscription data includes Multi-path relay capability or mATSSS capability for Remote UE310, and PCF73 receives the mATSSS capability, PCF73 may create or generate an mATSSS policy that includes the permitted mPDU.

[0305] For example, an mATSSS policy may include information for generating an mATSSS Rule. For example, an mATSSS policy may include information for determining the ratio of SDF traffic transmitted through each 3GPP access. This information may be used to determine the "Load-Balancing" Rule in an mATSSS Rule. For example, an mATSSS policy may include information for determining the priority of each 3GPP access. This information may be used for the "Priority-based" Rule in an mATSSS Rule. For example, an mATSSS policy may include information for sharing / transmitting the same Remote UE SDF traffic transmitted across different independent PDU Sessions over multiple 3GPP / non-3GPP accesses.

[0306] SMF71 generates at least one of the following for UPF72 based on the mATSSS policy received from PCF73: an mATSSS Rule and an N4 Rule. The mATSSS Rule may be included in the N4 Rule, or the N4 Rule may be included in the mATSSS Rule.

[0307] For example, SMF71 may generate mATSSS rules based on local policies or local configurations within SMF71.

[0308] For example, SMF71 may generate an mATSSS Rule based on at least one of the received mATSSS policy, local policies within SMF71, and local configurations.

[0309] For example, SMF71 may generate an mATSSS Rule based on the information described above in the mATSSS policy. The information described above in the mATSSS policy may be pre-stored in SMF71.

[0310] For example, an mATSSS Rule may include an mATSSS policy. For example, SMF71 may generate an mATSSS Rule by including an mATSSS policy in the mATSSS Rule.

[0311] Step 9: SMF71 sends an N4 Session Establishment message to UPF72 containing at least one of the following: PDU Session ID, Request Type set in the mPDU request, Linked PDU Session ID, Representative IP address, and mATSSS Rule, in order to reserve a user plane resource for the mPDU Session and install the mATSSS Rule.

[0312] When UPF72 receives a Linked PDU Session ID, it means that there may be one or more PDU Sessions that constitute the mPDU Session. In this case, UPF72 finds all associated PDU Sessions and performs the mATSSS-LL function within the associated PDU Sessions.

[0313] When UPF72 receives a Representative IP address, it performs NAT functionality on uplink user data sent from Remote UE310. Since uplink user data (e.g., user IP packets) have a source IP address configured to the unique IP address assigned to this PDU Session, UPF72 replaces the source IP address of the user IP packets with the Representative IP address. By using this NAT functionality within UPF72, AF201 in data network 20 always receives uplink user data from Remote UE310 with the same source IP address (e.g., Representative IP address).

[0314] Step 10: After successfully reserving the mPDU Session resources and installing the mATSSS Rule, UPF72 sends an N4 Session Establishment Response message to SMF71.

[0315] Step 11 SMF71 sends a Namf_Communication_N1N2MessageTransfer message to AMF70, which contains an N1 SM container. The N1 SM container contains a PDU Session Establishment Accept message, a Service Accept message, or any other NAS message. The PDU Session Establishment Accept message, or any other SM message (e.g., a Service Accept message or any other NAS message), contains the mPDU status and mATSSS Rule. The mPDU status indicates the status of the mPDU session, showing whether 5GS (e.g., the network) accepts the request to establish the mPDU session.

[0316] The mPDU status may indicate whether 5GS accepts the request to establish an mPDU session.

[0317] For example, SMF71 may configure an mPDU status that indicates whether 5GS will accept the request to establish an mPDU session, based on local policies within SMF71. For example, SMF71 may configure an mPDU status that indicates 5GS will accept the request to establish an mPDU session if steps 4 through 10 are completed successfully. For example, if the request establishes a PC5 connection and the current number of PC5 connections on the Remote UE310 does not exceed the maximum number of PC5 connections (which may be as described in step 5), SMF71 may configure an mPDU status that indicates 5GS will accept the request to establish an mPDU session.

[0318] The mPDU status can also indicate the maximum number of PC5 connections that the Remote UE310 can establish to at least one of the DNN and S-NSSAI. The maximum number of PC5 connections is stored and referenced by the Remote UE310 when the Remote UE310 adds further PDU sessions to an established mPDU session. The Remote UE310 may request that further PDU sessions be added to an established mPDU session up to the maximum number of PC5 connections received. The SMF71 may send the mPDU status to the UPF72. The SMF71 may generate the mPDU status in step 9 and send it to the UPF72.

[0319] The mPDU status may indicate that 5GS will not accept the request to establish an mPDU session. The mPDU status indicating that 5GS will not accept the request to establish an mPDU session may be included in the SM rejection message sent to the Remote UE310, as described in step 5. The mPDU status indicating that 5GS will not accept the request to establish an mPDU session may be included in the rejection message sent to the Remote UE310 (for example, a PDU Session Establishment Reject message). For example, a PDU Session Establishment Reject message may be included in the N1 SM container.

[0320] For example, SMF71 may configure an mPDU status indicating that 5GS will not accept the request to establish an mPDU Session if steps 4 through 10 do not complete successfully. For example, if a PC5 connection is established by the request and the current number of PC5 connections on the Remote UE310 exceeds the maximum number of PC5 connections (which may be as described in step 5), SMF71 may configure an mPDU status indicating that 5GS will not accept the request to establish an mPDU Session.

[0321] Step 12 The AMF70 sends a DL NAS Transport message to the Remote UE310 that includes a PDU Session Establishment Accept message, a Service Accept message, or any other NAS message. The PDU Session Establishment Accept message or any other SM message (e.g., a Service Accept message or any other NAS message) includes the mPDU status and mATSSS rule. For details on the mPDU status and mATSSS rule, see Step 11.

[0322] After the PDU Session Establishment procedure is successful, the Remote UE310 obtains the end-user IP address of the PDU Session (for example, for an mPDU Session). For example, the end-user IP address can be notified by a NAS message in step 12 or after performing a DNS query on UPF72.

[0323] If the Remote UE310 holds a Representative IP address other than the IP address assigned by this PDU Session Establishment procedure for the PDU Session, the Remote UE310 performs NAT functionality for downlink user data sent from UPF72. Since downlink user data may have a destination IP address configured with the unique IP address assigned to this PDU Session, the Remote UE310 replaces the destination IP address of the user IP packet with the Representative IP address. By using this NAT functionality within the Remote UE310, applications within the Remote UE310 will always receive downlink user data from the Remote UE310 with the same destination IP address (Representative IP address).

[0324] The order of Step 4 and Step 7 can be reversed.

[0325] (Modification 1 of the third embodiment relating to the second aspect) If the Remote UE310 sends a PDU Session Establishment Request message in step 1 to add an additional PC5 connection to an existing mPDU Session, and receives an SM rejection message or a PDU Session Establishment Reject message, the Remote UE310 will not add the new PC5 connection due to the rejection, but will maintain the PC5 connections already established for the mPDU Session. This rejection does not affect the existing PC5 connections of the mPDU Session.

[0326] (Modification 2 of the third embodiment relating to the second aspect) If UPF72 receives a Representative IP address in step 9, it may assign this Representative IP address to the PDU Session, if its configuration allows. As a result, each PDU Session that makes up the mPDU Session will be assigned the same IP address. By using this approach, the Remote UE310 and UPF72 do not enable NAT functionality, thus reducing processing on both the Remote UE310 and UPF72. For example, this approach may be used instead of using NAT functionality.

[0327] (Modification 3 of the third embodiment relating to the second aspect) The UE Route Selection Policy (URSP) rules in section 6.6.2.1 of TS23.503 (Non-Patent Literature 5) may be applied to the 5G ProSe Remote UE. The Route Selection Descriptor (RSD) of the URSP rule can be evolved to include a new information element, "ProSe Multi-PDU Sessions Preference" or "ProSe Layer-3 UE-to-Network Relay Offload by Multi-PDU Sessions," to accommodate multiple independent PDU sessions through different indirect connections via the UE-to-Network Relay UE300. If an application in the Remote UE310 or application traffic in the Remote UE310 matches a URSP rule, the corresponding RSD can be used to evaluate an existing PDU session or establish a new PDU session.

[0328] (Fourth embodiment relating to the second aspect) A fourth embodiment relating to the second embodiment includes how multipath indirect network connectivity can be established and updated based on the movement of the Remote UE310 using Figures 4 and 8 in the fourth embodiment relating to the second embodiment.

[0329] For the procedure of the fourth embodiment relating to the second aspect shown in Figure 8, please refer to Figure 4 and the related explanatory text.

[0330] Using the Remote UE310's behavior as an example, Figure 8 illustrates how a multipath indirect network connection is configured and how it reverts to a single-path indirect network connection. Figure 8 shows an example of a multipath indirect network connection using multiple PDU sessions.

[0331] The detailed procedure of the fourth embodiment relating to the second aspect will be described below with reference to both Figure 4 and Figure 8.

[0332] The steps shown in Figure 8 are explained below.

[0333] Step 0-1: The Network Relay UE30001 performs the registration procedure with the AMF70, establishing at least one PDU session with the SMF71 and UPF72.

[0334] Step 0-2: Network Relay UE30002 performs a registration procedure with AMF70, establishing at least one PDU session with SMF71 and UPF72. In one embodiment, SMF71 and UPF72 may be the same as or different from those for Network Relay UE30001. *Point 1: Remote UE only recognizes Network Relay UE30001.

[0335] Step 1: When the Remote UE310 recognizes a signal from the Network Relay UE30001, the Remote UE310 performs UE-to-NW Relay Discovery and Selection with the Network Relay UE30001 in accordance with 3GPP TS23.304 (Non-Patent Document 7).

[0336] Step 2 After successfully performing UE-to-NW Relay Discovery and Selection with Network Relay UE30001 in Step 1, Remote UE310 initiates the Registration procedure as disclosed in the second embodiment relating to the second aspect.

[0337] Step 3 After the registration procedure is successful, the Remote UE310 initiates a PDU Session Establishment procedure to generate an mPDU Session via, for, or against the Network Relay UE30001, as disclosed in the third embodiment relating to the second aspect. For example, the Linked PDU Session ID in the PDU Session Establishment procedure in Step 3 does not need to be included in the UL NAS Transport message in Step 3.

[0338] After the PDU Session Establishment procedure is successful, the Remote UE310 communicates with AF201 in the data network 20 using a single connection path between the Remote UE310 and UPF72.

[0339] At this point, at least one of the Remote UE310, AMF70, SMF71, and UPF72 stores the mPDU status and mATSSS Rule for managing multipath indirect network connections.

[0340] At this point, the mATSSS-LL function is installed on both the Remote UE310 and UPF72.

[0341] For example, if Remote UE310 receives at least one of the mPDU status and mATSSS Rule, Remote UE310 may consider the mATSSS-LL function to be installed. For example, if UPF72 receives at least one of the mPDU status and mATSSS Rule, UPF72 may consider the mATSSS-LL function to be installed.

[0342] For example, the Remote UE310 may communicate via the Network Relay UE30001 based on the mATSSS Rule received in step 3.

[0343] For example, the Remote UE310 may perform a mATSSS function or a mATSSS-LL function based on the mATSSS Rule received in step 3. *Point 2: Remote UE recognizes both Network Relay UE30001 and Network Relay UE30002.

[0344] Step 4 When the Remote UE310 recognizes a signal from the Network Relay UE30002, the Remote UE310 performs UE-to-NW Relay Discovery and Selection with the Network Relay UE30002 in accordance with 3GPP TS23.304 (Non-Patent Literature 7). For example, the Remote UE310 may perform UE-to-NW Relay Discovery and Selection with the Network Relay UE30002 while maintaining the PDU session (e.g., mPDU Session) established in Step 3.

[0345] Step 5 After successfully performing UE-to-NW Relay Discovery and Selection with Network Relay UE30002 in Step 4, Remote UE310 initiates a PDU Session Establishment procedure via, for, or against Network Relay UE30002, as disclosed in the third embodiment relating to a second aspect for adding another PDU Session to an mPDU Session.

[0346] For example, the Linked PDU Session ID in the UL NAS Transport message in the PDU Session Establishment procedure in step 5 may be the same PDU Session ID used in the PDU Session Establishment procedure in step 3.

[0347] For example, the Representative IP address in the UL NAS Transport message during the PDU Session Establishment procedure in step 5 may be the IP address assigned in step 2.

[0348] For example, Remote UE310 may initiate the PDU Session Establishment procedure via, for, or against Network Relay UE30002, while maintaining the PDU session (e.g., mPDU Session) established in step 3.

[0349] After the Session Establishment procedure is successful, the Remote UE310 communicates with AF201 in the data network 20 using two connection paths between the Remote UE310 and UPF72.

[0350] At this point, at least one of the Remote UE310, AMF70, SMF71, and UPF72 updates the mPDU status and mATSSS Rule to manage multipath indirect network connectivity.

[0351] For example, at least one of the Remote UE310, AMF70, SMF71, and UPF72 may store at least one of the mPDU status and mATSSS Rule generated or received in step 5.

[0352] At this point, two connection paths are established between the Remote UE310 and the UPF72, enabling high resilience for data connectivity.

[0353] For example, at this point, Remote UE310 may communicate via Network Relay UE30001 and Network Relay UE30002.

[0354] For example, at this point, Remote UE310 may communicate simultaneously via Network Relay UE30001 and Network Relay UE30002.

[0355] For example, Remote UE310 may communicate via Network Relay UE30001 based on at least one of the mATSSS Rules received in step 3 and the mATSSS Rule received in step 5.

[0356] For example, Remote UE310 may communicate via Network Relay UE30002 based on at least one of the mATSSS Rules received in step 3 and the mATSSS Rule received in step 5.

[0357] For example, the Remote UE310 may perform a mATSSS function or a mATSSS-LL function based on at least one of the mATSSS Rules received in step 3 and the mATSSS Rule received in step 5.

[0358] In one embodiment, if the Remote UE310 recognizes a signal from RAN5, the Remote UE310 may use the Uu interface to RAN5 to initiate a PDU Session Establishment procedure (e.g., a PDU Session Establishment procedure to generate an mPDU Session, or a PDU Session Establishment procedure). In this case, the UE-to-NW Relay Discovery and Selection in step 4 are not performed. *Point 3: Remote UE only recognizes Network Relay UE30002.

[0359] Step 6 If, due to the distance between Remote UE310 and Network Relay UE30001, for example, weak signal strength, Remote UE310 is unable to maintain a communication path with Network Relay UE30001 via the PC5 interface, Network Relay UE30001 may initiate a PDU Session Release procedure, triggered, for example, by a lower-layer Radio Link Failure (RLF), as described in 3GPP TS23.502 (Non-Patent Literature 4), Section 4.3.4.2.

[0360] After the PDU Session Release procedure is successful, the Remote UE310 communicates with AF201 in data network 20 using a single connection path between the Remote UE310 and UPF72.

[0361] For example, the Remote UE310 may communicate via the Network Relay UE30002 based on the mATSSS Rule received in step 5.

[0362] For example, the Remote UE310 may perform a mATSSS function or a mATSSS-LL function based on the mATSSS Rule received in step 5.

[0363] At this point, at least one of the Remote UE310, AMF70, SMF71, and UPF72 updates the mPDU status and mATSSS Rule to manage multipath indirect network connectivity.

[0364] For example, during or after the PDU Session Release procedure, at least one of the Remote UE310, AMF70, SMF71, and UPF72 may delete the mPDU status and mATSSS Rule stored in step 3, or replace the mPDU status and mATSSS Rule stored in step 3 with the mPDU status and mATSSS Rule generated or received in step 6.

[0365] For example, if the Remote UE310 is initially located at point 2 (for example, if the Remote UE310 is switched on at point 2), the Remote UE310 may perform steps 1 through 5. In this case, the Remote UE310 may first perform steps 1 through 3, then steps 4 and 5, or the Remote UE310 may first perform steps 4, 2 and 5, then steps 1 and 3.

[0366] For example, the Remote UE310 may perform an evolved Access Traffic Steering, Switching, Splitting (ATSSS) function for multiple PDU sessions, or an mATSSS-LL function, based on the received mATSSS Rule.

[0367] For example, at point 1 or 2, Remote UE310 may perform communication via Network Relay UE30001 based on the received mATSSS Rule (for example, this communication may include sending uplink data). If both 3GPP access and non-3GPP access are available for communication via Network Relay UE30001, Remote UE310 may perform communication via Network Relay UE30001 using either 3GPP access or non-3GPP access. Remote UE310 may determine which access to use for communication based on the mATSSS Rule.

[0368] For example, at point 2 or 3, Remote UE310 may perform communication via Network Relay UE30002 based on the received mATSSS Rule (for example, this communication may include sending uplink data). If both 3GPP access and non-3GPP access are available for communication via Network Relay UE30002, Remote UE310 may perform communication via Network Relay UE30002 using either 3GPP access or non-3GPP access. Remote UE310 may determine which access to use for communication based on the mATSSS Rule.

[0369] For example, UPF72 (e.g., UPF(PSA)72004, Relay UE UPF72001, Relay UE UPF72002, Relay UE UPF72003, etc.) may perform an evolved Access Traffic Steering, Switching, Splitting (ATSSS) function or an mATSSS-LL function for multiple PDU sessions based on the received mATSSS Rule.

[0370] For example, at point 1 or 2, UPF72 (e.g., UPF(PSA)72004, Relay UE UPF72001, Relay UE UPF72002, Relay UE UPF72003, etc.) may perform communication via Network Relay UE30001 based on the received mATSSS Rule (for example, this communication may include sending downlink data). If both 3GPP and non-3GPP access are available for communication via Network Relay UE30001, UPF72 (e.g., UPF(PSA)72004, Relay UE UPF72001, Relay UE UPF72002, Relay UE UPF72003, etc.) may perform communication via Network Relay UE30001 using either 3GPP access or non-3GPP access. Remote UE310 may determine which access is used for communication based on the mATSSS Rule.

[0371] For example, at point 2 or 3, UPF72 (e.g., UPF(PSA)72004, Relay UE UPF72001, Relay UE UPF72002, Relay UE UPF72003, etc.) may perform communication via Network Relay UE30002 based on the received mATSSS Rule (for example, this communication may include sending downlink data). If both 3GPP access and non-3GPP access are available for communication via Network Relay UE30002, Remote UE310 may perform communication via Network Relay UE30002 using either 3GPP access or non-3GPP access. Remote UE310 may determine which access to use for communication based on the mATSSS Rule.

[0372] Executing the Advanced Access Traffic Steering, Switching, Splitting (ATSSS) function or the mATSSS-LL function for a Multiple PDU Session based on the received mATSSS Rule includes the aforementioned communication via Remote UE310 or UPF72 (e.g., UPF(PSA)72004, Relay UE UPF72001, Relay UE UPF72002, Relay UE UPF72003, etc.).

[0373] The mATSSS Rule may be used to perform Advanced Access Traffic Steering, Switching, Splitting (ATSSS) functionality for Multiple PDU Sessions, or mATSSS-LL functionality.

[0374] The mATSSS Rule may also be information for performing the Advanced Access Traffic Steering, Switching, Splitting (ATSSS) function for Multiple PDU Sessions, or the mATSSS-LL function.

[0375] The mATSSS Rule may include information for controlling the aforementioned communication via Remote UE310 or UPF72 (e.g., UPF(PSA)72004, Relay UE UPF72001, Relay UE UPF72002, Relay UE UPF72003, etc.).

[0376] The mATSSS Rule may be represented as information for controlling or executing the above-mentioned communication via Remote UE310 or UPF72 (e.g., UPF(PSA)72004, Relay UE UPF72001, Relay UE UPF72002, Relay UE UPF72003, etc.).

[0377] The mATSSS Rule may be represented as information for controlling or executing communication in a multipath indirect network connection.

[0378] For example, multipath indirect network connectivity may include connectivity via or through Network Relay UE30001, and connectivity via or through Network Relay UE30002.

[0379] (Modification 1 of the fourth embodiment relating to the second aspect) The UE Route Selection Policy (URSP) rules in section 6.6.2.1 of TS23.503 (Non-Patent Literature 5) may be applied to the 5G ProSe Remote UE. The Route Selection Descriptor (RSD) within the URSP rule can be evolved to include a new information element, "ProSe Multi-path Indirect Connection Preference" or "ProSe Layer-3 UE-to-Network Relay Offload with Multi-indirect Connection," to support multiple indirect connections via the UE-to-Network Relay UE300. If an application within the Remote UE310, or application traffic within the Remote UE310, matches a URSP rule, a new indirect connection can be established via the UE-to-Network Relay UE300 and a new PDU Session using the corresponding RSD.

[0380] The above-described problems can be solved according to the second embodiment and at least one of the modifications of the second embodiment.

[0381] For example, the second embodiment and at least one of its variations can solve the problem that the above-mentioned service requirements are not yet addressed by 5GS.

[0382] For example, the second embodiment and at least one of its variations can solve the problem that the 3GPP specification does not have a mechanism for achieving the above-mentioned service requirements.

[0383] For example, the second embodiment, and at least one of its modifications, can solve the problem that, if 5GS does not support multipathing for indirect network connectivity, the Remote UE (or Remote UE) cannot avoid sudden interruptions or disconnections of connectivity services via indirect network connectivity due to unstable communication via a single connection between the Remote UE and the Network Relay UE.

[0384] For example, the second embodiment, and at least one of its variations, can solve the problem of the user experience being impaired in indirect network connections due to unstable connections via a single connection between the Remote UE and the Network Relay UE.

[0385] For example, a procedure for achieving a multipath indirect network connection (e.g., an mPDU Session) is disclosed according to at least one of the second embodiment and variations thereof, so that a Remote UE can establish a multipath indirect network connection. Thus, the above-mentioned problems can be solved.

[0386] (System Overview) Figure 9 schematically shows a telecommunications system 1 for mobile (cellular or wireless) to which the above embodiments can be applied.

[0387] Telecommunication system 1 represents a system overview that enables end-to-end communication. For example, UE3 (or user equipment, "mobile device" 3) communicates with other UE3 or service servers in the data network 20 via their respective (R)AN nodes 5 and core network 7.

[0388] (R)AN Node 5 supports any radio access, including non-3GPP RATs, such as 5G radio access technology (RAT), E-UTRA radio access technology, beyond 5G RAT, 6G RAT, and wireless local area network (WLAN) technology as defined by the Institute of Electrical and Electronics Engineers (IEEE).

[0389] (R)AN node 5 can be divided into Radio Unit (RU), Distributed Unit (DU), and Centralized Unit (CU). In some embodiments, each unit can be connected to one another, and (R)AN node 5 can be constructed by adopting an architecture defined by the Open RAN (O-RAN) Alliance, where the above units are referred to as O-RU, O-DU, and O-CU, respectively.

[0390] (R)AN node 5 can be divided into control plane functions and user plane functions. Furthermore, multiple user plane functions can be allocated to handle communications. In some embodiments, user traffic can be distributed across multiple user plane functions, and the user traffic on each user plane function is aggregated at both UE3 and (R)AN node 5. This divided architecture can be called "dual connectivity" or "multi-connectivity".

[0391] (R)AN node 5 can also support communications using satellite access. In some embodiments, (R)AN node 5 can support both satellite and ground access.

[0392] Furthermore, (R)AN node 5 can also be called an access node for non-wireless access. Non-wireless access includes fixed-line access as defined by the Broadband Forum (BBF), as well as optical access as defined by the Innovative Optical and Wireless Network (IOWN).

[0393] The core network 7 may include logical nodes (or "functions") to support communications in the telecommunications system 1. For example, the core network 7 may be a 5G Core Network (5GC) that includes control plane functions and user plane functions, among other functions. Each function within a logical node can be considered a network function. Network functions can be provided to other nodes by adapting a Service Based Architecture (SBA).

[0394] Network functions can be deployed as distributed, redundant, stateless, and scalable services delivered from several locations and several execution instances at each location, by adapting network virtualization technology as defined by the European Telecommunications Standards Institute, Network Functions Virtualization (ETSI NFV).

[0395] Core Network 7 can support Non-Public Networks (NPNs). An NPN can be a Stand-alone Non-Public Network (SNPN) or a Public Network Integrated NPN (PNI-NPN).

[0396] As is well known, UE3 can enter and exit the area (i.e., radio cell) served by (R)AN node 5 when UE3 is moving within the geographic area covered by telecommunications system 1. To track UE3 and facilitate movement between different (R)AN node 5, the core network 7 includes at least one access and mobility management function (AMF) 70. The AMF 70 communicates with the (R)AN node 5 coupled to the core network 7. In some core networks, a mobility management entity (MME), a mobility management node for Beyond 5G, or a mobility management node for 6G may be used instead of the AMF 70.

[0397] In the case of telecommunications system 1 that supports Proximity-based Services, UE3 can be separated into two different logical nodes, for example, Network Relay UE300 and Remote UE310. While Network Relay UE300 is connected to the core network 7 via (R)AN node 5, Remote UE310 is connected to the core network 7 via Network Relay UE300 and (R)AN node 5. In one embodiment, Remote UE310 is connected to the core network 7 only via (R)AN node 5. The block diagram of UE3 in Figure 10 can be applied to Network Relay UE300, Network Relay UE30001, Network Relay UE30002, Network Relay UE30003, and Remote UE310.

[0398] The core network 7 also includes, among other things, a Session Management Function (SMF) 71, a User Plane Function (UPF) 72, a Policy Control Function (PCF) 73, a Network Data Analytics Function (NWDAF) 74, a Unified Data Management (UDM) 75, and a Network Slice Selection Function (NSSF) 76. When UE3 is roaming to the visited Public Land Mobile Network (VPLMN), UE3's home Public Land Mobile Network (HPLMN) provides the roaming UE3 with the UDM 75, as well as at least some of the functions of SMF 71, UPF 72, and PCF 73.

[0399] UE3 and each Serving(R)AN node 5 are connected via appropriate air interfaces (e.g., so-called "Uu" interfaces). Adjacent (R)AN nodes 5 are connected to each other via appropriate (R)AN nodes 5 to (R)AN node interfaces (e.g., so-called "Xn" interfaces). Each (R)AN node 5 is also connected to nodes in the core network 7 (so-called core network nodes, etc.) via appropriate interfaces (e.g., so-called "N2" / "N3" interfaces). The core network 7 also provides connectivity to the data network 20. The data network 20 can be the internet, a public network, an external network, a private network, or an internal network of the PLMN. If the data network 20 is provided by a PLMN operator or Mobile Virtual Network Operator (MVNO), the data network 20 can provide IP Multimedia Subsystem (IMS) services. UE3 can connect to the data network 20 using IPv4, IPv6, IPv4v6, Ethernet, or unstructured data types. The data network may contain Application Function (AF) 201.

[0400] The "Uu" interface may include the Control plane of the Uu interface and the User plane of the Uu interface.

[0401] The User plane of the Uu interface is responsible for transmitting user traffic between UE3 and Serving(R)AN node 5. The User plane of the Uu interface can have a hierarchical structure with SDAP, PDCP, RLC, and MAC sublayers via physical connections.

[0402] The Uu interface's control plane is responsible for establishing, modifying, and releasing connections between UE3 and Serving(R)AN node 5. The Uu interface's control plane can have a hierarchical structure with RRC, PDCP, RLC, and MAC sublayers via physical connections.

[0403] For example, to support AS signaling, the following message is communicated via the RRC layer. • RRC Setup Request message: This message is sent from UE3 to (R)AN node 5. In addition to the parameters disclosed in this disclosure, the following parameters may be included in the RRC Setup Request message. #establishmentCause and ue-Identity. ue-Identity can have the value ng-5G-S-TMSI-Part1 or randomValue. • RRC Setup message: This message is sent from (R)AN node 5 to UE3. In addition to the parameters disclosed in this aspect of disclosure, the following parameters may be included together in the RRC Setup message. #masterCellGroup and radioBearerConfig. • RRC setup complete message: This message is sent from UE3 to (R)AN node 5. In addition to the parameters disclosed in this embodiment, the following parameters may be included in the RRC setup complete message. #guami-Type, iab-NodeIndication, idleMeasAvailable, mobilityState, ng-5G-S-TMSI-Part2, registeredAMF, selectedPLMN-Identity.

[0404] The UE3 and AMF70 are connected via an appropriate interface (e.g., the so-called N1 interface). The N1 interface is responsible for providing communication between the UE3 and AMF70 in order to support NAS signaling. The N1 interface can be established via 3GPP access and non-3GPP access. For example, the following messages are communicated via the N1 interface. • Registration request message: This message is sent from UE3 to AMF70. In addition to the parameters disclosed in this disclosure, the following parameters may be included in the registration request message: #5GS registration type, ngKSI, 5GS mobile identity, Non-current native NAS key set identifier, 5GMM capability, UE security capability, Requested NSSAI, Last visited registered TAI, S1 UE network capability, Uplink data status, PDU session status, MICO indication, UE status, Additional GUTI, Allowed PDU session status, UE's usage setting, Requested DRX parameters, EPS NAS message container, LADN indication, Payload container type, Payload container, Network slicing indication, 5GS update type, Mobile station classmark2, Supported codecs, NAS message container, EPS bearer context status, Requested extended DRX parameters, T3324 value, UE radio capability ID, Requested mapped NSSAI, Additional information requested, Requested WUS assistance information, N5GC indication, and Requested NB-N1 mode DRX parameters. • Registration Acceptance Message: This message is sent from AMF70 to UE3. In addition to the parameters disclosed in this form, the following parameters may be included in the registration acceptance message. #5GS registration result, 5G-GUTI, Equivalent PLMNs, TAI list, Allowed NSSAI, Rejected NSSAI, Configured NSSAI, 5GS network feature support, PDU session status, PDU session reactivation result, PDU session reactivation result error cause, LADN information, MICO indication, Network slicing indication, Service area list, T3512 value, Non-3GPP de-registration timer value, T3502 value, Emergency number list, Extended emergency number list, SOR transparent container, EAP message, NSSAI inclusion mode, Operator-defined access category definitions, Negotiated DRX parameters, Non-3GPP NW policies, EPS bearer context status, Negotiated extended DRX parameters, T3447 value, T3448 value, T3324 value, UE radio capability ID, UE radio capability ID deletion indication, Pending NSSAI, Ciphering key data, CAG information list, Truncated 5G-S-TMSI configuration, Negotiated WUS assistance information, Negotiated NB-N1 mode DRX parameters, and Extended rejected NSSAI. • Registration Complete message: This message is sent from UE3 to AMF70. In addition to the parameters disclosed in this disclosure, the following parameters may be included in the Registration Complete message. #SOR transparent container. • Authentication Request message: This message is sent from AMF70 to UE3. In addition to the parameters disclosed in this disclosure, the following parameters may be included in the Authentication Request message. #ngKSI, ABBA, Authentication parameter RAND(5G authentication challenge), Authentication parameter AUTN(5G authentication challenge), and EAP message. • Authentication Response message: This message is sent from UE3 to AMF70. In addition to the parameters disclosed in this disclosure, the following parameters may be included in the Authentication Response message. #Authentication response message identity, Authentication response parameter and EAP message. • Authentication Result message: This message is sent from AMF70 to UE3. In addition to the parameters disclosed in this disclosure, the following parameters may be included in the Authentication Result message. #ngKSI, EAP messages, and ABBA. • Authentication Failure message: This message is sent from UE3 to AMF70. In addition to the parameters disclosed in this disclosure, the following parameters may be included in the Authentication Failure message. #Authentication failure message identifier, 5GMM cause, and Authentication failure parameters. • Authentication Reject message: This message is sent from AMF70 to UE3. In addition to the parameters disclosed in this disclosure, the following parameters may be included in the Authentication Reject message. #EAP message. • Service Request message: This message is sent from UE3 to AMF70. In addition to the parameters disclosed in this disclosure, the following parameters may be included in the Service Request message. #ngKSI, Service type, 5G-S-TMSI, Uplink data status, PDU session status, Allowed PDU session status, NAS message container. • Service Accept message: This message is sent from AMF70 to UE3. In addition to the parameters disclosed in this disclosure, the following parameters may be included in the Service Accept message: #PDU session status, PDU session reactivation result, PDU session reactivation result error cause, EAP message, and T3448 value. • Service Reject message: This message is sent from AMF70 to UE3. In addition to the parameters disclosed in this disclosure, the following parameters may be included in the Service Reject message. #5GMM cause, PDU session status, T3346 value, EAP message, T3448 value, and CAG information list. • Configuration Update Command message: This message is sent from AMF70 to UE3. In addition to the parameters disclosed in this disclosure, the following parameters may be included in the Configuration Update Command message. #Configuration update indication, 5G-GUTI, TAI list, Allowed NSSAI, Service area list, Full name for network, Short name for network, Local time zone, Universal time and local time zone, Network daylight saving time, LADN information, MICO indication, Network slicing indication, Configured NSSAI, Rejected NSSAI, Operator-defined access category definitions, SMS indication, T3447 value, CAG information list, UE radio capability ID deletion indication, 5GS registration result, Truncated 5G-S-TMSI configuration, Additional configuration indication, and Extended rejected NSSAI. • Configuration Update Complete message: This message is sent from UE3 to AMF70. In addition to the parameters disclosed in this disclosure, the following parameters may be included in the Configuration Update Complete message. #Configuration update complete message identity.

[0405] (User Equipment (UE)) Figure 10 is a block diagram showing the main components of UE3 (Mobile Device 3). As shown, UE3 includes a transceiver circuit 31 that can operate to send and receive signals with nodes connected via one or more antennas 32. UE3 may also include a user interface 34 for inputting and outputting information to and from the outside. Although not necessarily shown in Figure 10, UE3 can have all the usual functions of a conventional mobile device, which can be provided by any one or any combination of hardware, software, and firmware, as needed. The software can be pre-installed in memory and / or downloaded, for example, via a telecommunications network or from a removable data storage device (RMD). The controller 33 controls the operation of UE3 according to the software stored in memory 36. The software includes, among other things, an operating system 361, as well as a communication control module 362 having at least one transceiver control module 3621. The communication control module 362 (using its transceiver control module 3621) is responsible for signaling between the UE3 and other nodes, such as (R)AN node 5 and AMF70, and for processing (generating / transmitting / receiving) uplink / downlink data packets. Such signaling may include, for example, appropriately formatted signaling messages relating to access and mobility management procedures (for the UE3) (e.g., registration request messages and associated response messages). The controller 33 interacts with one or more Universal Subscriber Identity Modules (USIMs) 35. If multiple USIMs 35 are installed, the controller 33 may enable only one USIM 35 or multiple USIMs 35 simultaneously.

[0406] UE3 can support, for example, Non-Public Networks (NPNs). An NPN can be a Stand-alone Non-Public Network (SNPN) or a Public Network Integrated NPN (PNI-NPN).

[0407] UE3 can be, for example, items of equipment for production or manufacturing, and / or items of energy-related machinery (e.g., boilers, engines, turbines, solar panels, wind turbines, hydroelectric generators, thermal power generators, nuclear power generators, batteries, nuclear systems and / or related equipment, heavy electrical equipment, pumps including vacuum pumps, compressors, fans, blowers, hydraulic equipment, pneumatic equipment, metalworking machinery, manipulators, robots and / or their application systems, tools, molds or dies, rolls, conveying equipment, lifting equipment, material handling equipment, textile machinery, sewing machines, printing and / or related machinery, paperwork machinery, chemical machinery, mining and / or construction machinery and / or related equipment, machinery and / or equipment for agriculture, forestry and / or fisheries, safety and / or environmental protection equipment, tractors, precision bearings, chains, gears, power transmission equipment, lubrication equipment, valves, pipe fittings, and / or application systems for any of the aforementioned equipment or machinery).

[0408] UE3 can be, for example, a transport equipment item (e.g., transport equipment such as railway cars, automobiles, motorcycles, bicycles, trains, buses, carts, rickshaws, ships and other vessels, aircraft, rockets, satellites, drones, balloons, etc.).

[0409] UE3 can be, for example, an item of information and communication equipment (e.g., electronic computers and related equipment, communication and related equipment, electronic components and other information and communication equipment).

[0410] UE3 can be, for example, refrigerators, refrigerator applications, merchandise and / or service industry equipment items, vending machines, automated service machines, office equipment, consumer electronics and electronic devices (e.g., audio equipment, video equipment, speakers, radios, televisions, microwave ovens, rice cookers, coffee machines, dishwashers, washing machines, dryers, electronic fans or related appliances, vacuum cleaners and other consumer electronic devices).

[0411] UE3 can be, for example, an electrical application system or device (such as an X-ray system, particle accelerator, radioisotope device, sound wave device, electromagnetic application device, power application device, etc.).

[0412] UE3 can include, for example, electronic lamps, lighting fixtures, measuring instruments, analyzers, testers, or surveying or sensing equipment (e.g., smoke detectors, motion sensors, wireless tags, etc.), wristwatches or clocks, inspection equipment, optical devices, medical equipment and / or systems, weapons, cutlery products, hand tools, etc.

[0413] UE3 can be, for example, a wireless-equipped personal digital assistant, or related equipment (such as a wireless card or module designed to be attached to or inserted into another electronic device, such as a personal computer or electrical measuring instrument).

[0414] UE3 can be part of a device or system that provides applications, services, and solutions related to the Internet of Things (IoT), as described below, using various wired and / or wireless communication technologies.

[0415] Internet of Things devices (or "things") can be equipped with appropriate electronics, software, sensors, network connectivity, etc., which enable them to collect and exchange data with each other and with other communication devices. IoT devices can comprise automated equipment that follows software instructions stored in internal memory. IoT devices can operate without requiring human monitoring or interaction with humans. IoT devices can also remain stationary and / or inactive for extended periods. IoT devices can be implemented as part of (generally) stationary equipment. IoT devices can also be incorporated into non-stationary equipment (e.g., vehicles) or attached to animals or people to be monitored / tracked.

[0416] IoT technology can be understood as being implemented on any communication device that can connect to a communication network to send / receive data, regardless of whether such communication device is controlled by human input or by software instructions stored in memory.

[0417] IoT devices are sometimes referred to as Machine-Type Communication (MTC) devices, Machine-to-Machine (M2M) communication devices, or Narrow Band-IoT UEs (NB-IoT UEs). UE3 is understood to support one or more IoT or MTC applications.

[0418] UE3 can be a smartphone or a wearable device (e.g., smart glasses, smartwatch, smart ring, or hearable device).

[0419] UE3 can be an automobile, connected car, autonomous vehicle, vehicle device, motorcycle, or Vehicle to Everything (V2X) communication module (e.g., vehicle-to-vehicle communication module, vehicle-to-infrastructure communication module, vehicle-to-pedestrian communication module, and vehicle-to-network communication module).

[0420] ((R)AN node) Figure 11 is a block diagram showing the main components of an exemplary (R)AN node 5, for example, a base station (an "eNB" in LTE, a "gNB" in 5G, a 5G Beyond base station, or a 6G base station). As shown in the diagram, the (R)AN node 5 includes a transceiver circuit 51 that can operate to send and receive signals with a connected UE3 via one or more antennas 52, and to send and receive signals with other network nodes (directly or indirectly) via a network interface 53. A controller 54 controls the operation of the (R)AN node 5 according to software stored in memory 55. The software can be pre-installed in memory and / or downloaded, for example, via a telecommunications network or from a removable data storage device (RMD). The software includes, among other things, an operating system 551, and a communication control module 552 having at least a transceiver control module 5521.

[0421] The communication control module 552 (using its transceiver control submodule) is responsible for processing (generating / transmitting / receiving) signaling between (R)AN node 5 and other nodes, e.g., UE3, another (R)AN node 5, AMF70, UPF72, (for example, directly or indirectly). The signaling may include, for example, appropriately formatted signaling messages related to radio connectivity and connectivity with the core network 7 (for a particular UE3), particularly connectivity establishment and maintenance (e.g., RRC connectivity establishment and other RRC messages), NG Application Protocol (NGAP) messages (i.e., messages from the N2 reference point), and Xn application protocol (XnAP) messages (i.e., messages from the Xn reference point). Such signaling may also include, for example, broadcast information in the transmission case (e.g., master information and system information).

[0422] The controller 54, when implemented, is also configured (by software or hardware) to handle related tasks such as UE mobility estimation and / or movement trajectory estimation.

[0423] (R) AN node 5 can support Non-Public Network (NPN). The NPN can be a Stand-alone Non-Public Network (SNPN) or a Public Network Integrated NPN (PNI-NPN).

[0424] RAN501, RAN502, and RAN503 may have the same components as (R)AN node 5. (R)AN node 5 can be represented as RAN node, RAN, (R)AN, etc.

[0425] (System overview of (R)AN node 5 based on O-RAN architecture) Figure 12 schematically shows an (R)AN node 5 based on an O-RAN architecture to which an embodiment of (R)AN node 5 can be applied.

[0426] The (R)AN node 5, based on the O-RAN architecture, represents a system overview in which the (R)AN node is divided into a Radio Unit (RU) 60, a Distributed Unit (DU) 61, and a Centralized Unit (CU) 62. In some embodiments, each unit can be combined. For example, RU 60 can be combined with DU 61 as an integration / combination unit, and DU 61 can be combined with CU 62 as another integration / combination unit. Any function described in the unit description (e.g., one of RU 60, DU 61, and CU 62) can be implemented in the above integration / combination units. Furthermore, CU 62 can be separated into two functional units, such as a CU Control plane (CP) and a CU User plane (UP). The CU CP has control plane functionality in the (R)AN node 5. The CU UP has user plane functionality in the (R)AN node 5. Each CU CP is connected to the CU UP via an appropriate interface (such as the so-called "E1" interface).

[0427] UE3 and each serving RU60 are connected via the appropriate air interface (e.g., the so-called "Uu" interface). Each RU60 is connected to a DU61 via the appropriate interface (e.g., the so-called "Front haul", "Open Front haul", "F1" interface). Each DU61 is connected to a CU62 via the appropriate interface (e.g., the so-called "Mid haul", "Open Mid haul", "E2" interface). Each CU62 is also connected to a node in the core network 7 (e.g., the so-called core network node) via the appropriate interface (e.g., the so-called "Back haul", "Open Back haul", "N2" / "N3" interface). Furthermore, the user plane portion of the DU61 can also be connected to a core network node via the appropriate interface "N3".

[0428] Depending on the functions divided among RU60, DU61, and CU62, each unit provides a portion of the functions provided by (R)AN node 5. For example, RU60 can provide the function to communicate with UE3 (e.g., Network Relay UE300) via the air interface, DU61 can provide the function to support the MAC and RLC layers, and CU62 can provide the function to support the PDCP, SDAP, and RRC layers.

[0429] (Radio Unit (RU)) Figure 13 is a block diagram showing the main components of the RU portion of an exemplary RU60, for example, a base station (eNB in ​​LTE, gNB in ​​5G, 5G Beyond base station, 6G base station). As shown in the figure, the RU60 includes a transceiver circuit 601 that can operate to send and receive signals with a connected UE3 via one or more antennas 602, and to send and receive signals with other network nodes or network units (directly or indirectly) via a network interface 603. The controller 604 controls the operation of the RU60 according to software stored in memory 605. The software can be pre-installed in memory and / or downloaded, for example, via a telecommunications network or from a removable data storage device (RMD). The software includes, among other things, an operating system 6051, and a communication control module 6052 having at least a transceiver control module 60521.

[0430] The communication control module 6052 (using its transceiver control submodule) is responsible for processing (generating / transmitting / receiving) signaling between RU60 and other nodes or units, such as UE3, another RU60, and DU61, (for example, directly or indirectly). This signaling may include appropriately formatted signaling messages, for example, regarding wireless connectivity and connectivity with RU60 (for a specific UE3, e.g., Network Relay UE300), particularly concerning the MAC and RLC layers.

[0431] The controller 604, when implemented, is also configured (by software or hardware) to handle related tasks such as UE mobility estimation and / or movement trajectory estimation. The RU60 can support Non-Public Networks (NPNs). An NPN can be a Stand-alone Non-Public Network (SNPN) or a Public Network Integrated NPN (PNI-NPN).

[0432] As described above, RU60 can be integrated / coupled with DU61 as an integration / coupling unit. Any of the functions described in the RU60 description can be implemented in the above integration / coupling unit.

[0433] (Distributed Unit (DU)) Figure 14 is a block diagram showing the main components of the DU portion of an exemplary DU61, for example, a base station (eNB in ​​LTE, gNB in ​​5G, 5G Beyond base station, 6G base station). As shown in the figure, the device includes a transceiver circuit 611 that can operate to send and receive signals with other nodes or units (including RU60) via a network interface 612. A controller 613 controls the operation of the DU61 according to software stored in memory 614. The software can be pre-installed in memory 614 and / or downloaded, for example, via a telecommunications network or from a removable data storage device (RMD). The software includes, among other things, an operating system 6141 and a communication control module 6142 having at least a transceiver control module 61421. The communication control module 6142 (using its transceiver control module 61421) is responsible for processing (generating / transmitting / receiving) signaling between the DU61 and other nodes or units, such as RU60, other nodes and units.

[0434] The DU61 can support Non-Public Networks (NPNs). An NPN can be a Stand-alone Non-Public Network (SNPN) or a Public Network Integrated NPN (PNI-NPN).

[0435] As described above, RU60 can be integrated / coupled with DU61 or CU62 as an integration / coupling unit. Any function described in the DU61 description can be implemented in one of the above integration / coupling units.

[0436] (Centralized Unit (CU)) Figure 15 is a block diagram showing the main components of the CU portion of an exemplary CU62, for example, a base station (eNB in ​​LTE, gNB in ​​5G, 5G Beyond base station, 6G base station). As shown in the figure, the device includes a transceiver circuit 621 that can operate to send and receive signals with other nodes or units (including DU61) via a network interface 622. A controller 623 controls the operation of the CU62 according to software stored in memory 624. The software can be pre-installed in memory 624 and / or downloaded, for example, via a telecommunications network or from a removable data storage device (RMD). The software includes, among other things, an operating system 6241, and a communication control module 6242 having at least a transceiver control module 62421. The communication control module 6242 (using its transceiver control module 62421) is responsible for processing (generating / transmitting / receiving) signaling between the CU62 and other nodes or units, such as DU61, other nodes and units.

[0437] CU62 can support Non-Public Networks (NPNs). An NPN can be a Stand-alone Non-Public Network (SNPN) or a Public Network Integrated NPN (PNI-NPN).

[0438] As described above, CU62 can be integrated / coupled with DU61 as an integration / coupling unit. Any of the functions described in the CU62 description can be implemented in the above integration / coupling unit.

[0439] (AMF) Figure 16 is a block diagram illustrating the main components of the AMF70. As shown, the device includes a transceiver circuit 701 that can operate to send and receive signals with other nodes (including UE3 (e.g., Network Relay UE300 and Remote UE310), NSSF76) via a network interface 702. The controller 703 controls the operation of the AMF70 according to software stored in memory 704. The software can be pre-installed in memory 704 and / or downloaded, for example, via a telecommunications network or from a removable data storage device (RMD). The software includes, among other things, an operating system 7041, and a communication control module 7042 having at least a transceiver control module 70421. The communication control module 7042 (using its transceiver control module 70421) is responsible for processing (generating / transmitting / receiving) signaling between the AMF 70 and other nodes, such as UE3 (via (R)AN node 5) and other core network nodes (including the core network node in UE3's HPLMN when UE3 is roaming in). Such signaling may include, for example, appropriately formatted signaling messages relating to access and mobility management procedures (for UE3), such as registration request messages and associated response messages.

[0440] The AMF70 can support Non-Public Networks (NPNs). An NPN can be a Stand-alone Non-Public Network (SNPN) or a Public Network Integrated NPN (PNI-NPN).

[0441] (SMF) Figure 17 is a block diagram showing the main components of the SMF71. As shown, the device includes a transceiver circuit 711 that can operate to send and receive signals with other nodes (including the AMF70) via a network interface 712. A controller 713 controls the operation of the SMF71 according to software stored in memory 714. The software can be pre-installed in memory 714 and / or downloaded, for example, via a telecommunications network or from a removable storage device (e.g., a removable memory device (RMD)). This software includes, among other things, an operating system 7141, as well as a communication control module 7142 having at least one transceiver control module 71421. The communication control module 7142 (using its transceiver control module 71421) is responsible for handling (generating / sending / receiving) signaling between the SMF71 and other nodes, such as the AMF70, and other core network nodes (including the core network nodes in the HPLMN of the UE3 when the UE3 (e.g., Network Relay UE300 and Remote UE310)) is roaming in. Such signaling may include, for example, appropriately formatted signaling messages regarding policy management procedures (for the UE3), such as HTTP restful methods based on service-based interfaces.

[0442] The SMF71 can support Non-Public Networks (NPNs). An NPN can be a Stand-alone Non-Public Network (SNPN) or a Public Network Integrated NPN (PNI-NPN).

[0443] (UPF) Figure 18 is a block diagram showing the main components of the UPF72. As shown, the device includes a transceiver circuit 721 that can operate to send and receive signals with other nodes (including the SMF71) via a network interface 722. A controller 723 controls the operation of the UPF72 according to software stored in memory 724. The software can, for example, be pre-installed in memory 724 and / or downloaded via a telecommunications network or from a removable storage device (e.g., a removable memory device (RMD)). This software includes, among other things, an operating system 7241, and a communication control module 7242 having at least one transceiver control module 72421. The communication control module 7242 (using its transceiver control module 72421) is responsible for processing (generating / transmitting / receiving) signaling between UPF72 and other nodes, such as SMF71, and other core networks (including core network nodes in the HPLMN of UE3 when UE3 (e.g., Network Relay UE300 and Remote UE310)) is roaming. Such signaling may include, for example, appropriately formatted signaling messages (e.g., HTTP restful methods based on service-based interfaces) relating to policy management procedures (for UE3).

[0444] UPF72 can support Non-Public Networks (NPNs). An NPN can be a Stand-alone Non-Public Network (SNPN) or a Public Network Integrated NPN (PNI-NPN). UPF72001, UPF72002, UPF72003, and UPF72004 can have the same components as UPF72.

[0445] (PCF) Figure 19 is a block diagram showing the main components of the PCF73. As shown, the device includes a transceiver circuit 731 that can operate to send and receive signals with other nodes (including the AMF70) via a network interface 732. The controller 733 controls the operation of the PCF73 according to software stored in memory 734. The software can be pre-installed in memory 734 and / or downloaded, for example, via a telecommunications network or from a removable storage device (e.g., a removable memory device (RMD)). The software includes, among other things, an operating system 7341, and a communication control module 7342 having at least a transceiver control module 73421. The communication control module 7342 (using its transceiver control module 73421) is responsible for processing (generating / transmitting / receiving) signaling between PCF73 and other nodes, such as AMF70, and other core network nodes (including the core network within the HPLMN of UE3 when UE3 (e.g., Network Relay UE300 and Remote UE310)) is roaming. Such signaling may include, for example, appropriately formatted signaling messages regarding policy management procedures (for UE3) (e.g., HTTP restful methods based on service-based interfaces).

[0446] PCF73 can support Non-Public Networks (NPNs). An NPN can be a Stand-alone Non-Public Network (SNPN) or a Public Network Integrated NPN (PNI-NPN).

[0447] (AF) Figure 20 is a block diagram showing the main components of AF201. As shown, the device includes a transceiver circuit 2011 that can operate to send and receive signals with other nodes (including UE3 (e.g., Network Relay UE300 and Remote UE310)) via a network interface 2012. A controller 2013 controls the operation of AF201 according to software stored in memory 2014. The software can be pre-installed in memory 2014 and / or downloaded, for example, via a telecommunications network or from a removable storage device (e.g., removable memory device (RMD)). The software includes, among other things, an operating system 20141, and a communication control module 20142 having at least a transceiver control module 201421. The communication control module 20142 (using its transceiver control module 201421) is responsible for processing (generating / sending / receiving) signaling between AF201 and other nodes, such as UE3, and other core network nodes (including the core network node in UE3's HPLMN when UE3 is roaming). Such signaling may include, for example, appropriately formatted signaling messages regarding policy management procedures (for UE3), such as HTTP restful methods based on service-based interfaces.

[0448] The AF201 can support Non-Public Networks (NPNs). An NPN can be a Stand-alone Non-Public Network (SNPN) or a Public Network Integrated NPN (PNI-NPN).

[0449] (UDM) Figure 21 is a block diagram showing the main components of the UDM 75. As shown, the device includes a transceiver circuit 751 that can operate to send and receive signals with other nodes (including the AMF 70) via a network interface 752. A controller 753 controls the operation of the UDM 75 according to software stored in memory 754. The software can be pre-installed in memory 754 and / or downloaded, for example, via a telecommunications network or from a removable data storage device (RMD). The software includes, among other things, an operating system 7541, and a communication control module 7542 having at least a transceiver control module 75421. The communication control module 7542 (using its transceiver control module 75421) is responsible for handling (generating / transmitting / receiving) signaling between the UDM 75 and other nodes, such as the AMF 70 and other core network nodes (including the core network nodes in the VPLMN of the UE3 when the UE3 (e.g., Network Relay UE300 and Remote UE310)) is roaming. Such signaling may include, for example, appropriately formatted signaling messages (e.g., HTTP restful methods based on service-based interfaces) relating to mobility management procedures (for the UE3).

[0450] The UDM75 can support Non-Public Networks (NPNs). An NPN can be a Stand-alone Non-Public Network (SNPN) or a Public Network Integrated NPN (PNI-NPN).

[0451] The exemplary embodiments disclosed above, in whole or in part, can be described as follows, without limitation:

[0452] (Variations and alternative examples) Detailed embodiments have been described above. As those skilled in the art will understand, several modifications and substitutions can be made to the embodiments described above while still benefiting from the disclosure as embodied therein. Some of these substitutions and modifications are described here only as examples.

[0453] For the sake of clarity, the above description assumes that the UE3 and network device have several separate modules (such as a communications control module). These modules may be provided in this way in certain applications, for example, where an existing system is modified to implement the present disclosure. However, in other applications, such as systems designed from the outset with the features of the present invention in mind, these modules may be incorporated into the overall operating system or code, and therefore may not be identified as separate entities. These modules may also be implemented as software, hardware, firmware, or a combination thereof.

[0454] Each controller may include, but is not limited to, one or more hardware-implemented computer processors, microprocessors, central processing units (CPUs), arithmetic logic units (ALUs), input / output (IO) circuits, internal memory / cache (program and / or data), processing registers, communication buses (such as control buses, data buses, and / or address buses), direct memory access (DMA) functions, hardware or software-implemented counters, pointers, and / or timers, and any other suitable form of processing circuitry.

[0455] In the above embodiments, several software modules have been described. As those skilled in the art will understand, software modules can be provided in compiled or uncompiled form and supplied to the UE3 and network devices as signals over a computer network or on a recording medium. Furthermore, some or all of the functions performed by this software can be performed using one or more dedicated hardware circuits. However, it is preferable to use software modules because it facilitates updating the UE3 and network devices to update those functions.

[0456] In the above embodiments, 3GPP wireless communication (wireless access) technology is used. However, any other wireless communication technology (e.g., WLAN, Wi-Fi, WiMAX, Bluetooth, etc.) and other fixed-line communication technologies (e.g., BBF access, cable access, optical access, etc.) can also be used in accordance with the above embodiments.

[0457] The category of user devices may include, for example, mobile phones, smartphones, user devices, personal digital assistants, laptop / tablet computers, web browsers, e-readers, and other communication devices. Such mobile (or even more broadly, fixed) devices are typically operated by a user, but it is also possible to connect so-called "Internet of Things" (IoT) devices and similar machine-type communication (MTC) devices to a network. For brevity, this application refers to mobile devices (or UEs) in the description, but it will be understood that the described technology can be implemented in any communication device (mobile and / or generally fixed) that can connect to a communication network to send and receive data, whether such communication devices are controlled by human input or by software instructions stored in memory.

[0458] Various other modifications are obvious to those skilled in the art and will not be described in further detail here.

[0459] As those skilled in the art will understand, this disclosure can be embodied as a method and a system. Accordingly, this disclosure can take the form of entirely hardware embodiments, software embodiments, or embodiments combining software and hardware embodiments.

[0460] Each block in the block diagram can be understood as being implemented by computer program instructions. These computer program instructions can be provided to a processor in a general-purpose computer, a dedicated computer, or other programmable data processing device to manufacture a machine, thereby generating means for implementing the functions / operations specified in the flowchart and / or block diagram, through which the instructions executed via the computer or other programmable data processing device processor. The general-purpose processor may be a microprocessor, but instead, the processor may be any conventional processor, controller, microcontroller, or state machine. The processor may also be implemented as a combination of computing devices, for example, multiple microprocessors, one or more microprocessors, or any other such configuration.

[0461] The methods or algorithms described in relation to the embodiments disclosed herein can be directly embodied in hardware, in software modules executed by a processor, or in a combination of the two. The software module may be RAM memory, flash memory, ROM memory, EPROM memory, EEPROM memory, hard disk, removable disk, CD-ROM, or any other form of storage medium known in the art. The storage medium can be coupled to the processor so that the processor can read information from and write information to the storage medium. Alternatively, the storage medium can be integrated with the processor. The processor and storage medium may be located within an ASIC.

[0462] The preceding description of the disclosed embodiments is provided to enable those skilled in the art to implement or use the disclosure. Various modifications to these embodiments will be readily apparent to those skilled in the art, and the general principles defined herein can be applied to other embodiments without departing from the spirit or scope of the disclosure. Thus, the disclosure is not intended to be limited to the embodiments shown herein, but rather to be given the broadest scope consistent with the principles and novel features disclosed herein.

[0463] This disclosure is illustrated and described in detail with reference to its exemplary embodiments, but is not limited to these embodiments. Those skilled in the art will understand that various modifications can be made to the form and details without departing from the spirit and scope of this disclosure as defined herein. For example, the embodiments described above are not limited to 5GS, and these embodiments can also be applied to communication systems other than 5GS (e.g., 6G systems, 5G Beyond systems).

[0464] (Note) The exemplary embodiments disclosed above, in whole or in part, may be described as follows, but are not limited to these: (Note 1) A method for Remote User Equipment (UE), Follow the registration procedure, A method comprising performing a Protocol Data Unit (PDU) session establishment procedure via a first ProSe UE-to-Network Relay, and a PDU session establishment procedure via a second ProSe UE-to-Network Relay. (Note 2) Receiving information for controlling communication via the first ProSe UE-to-Network Relay and the second ProSe UE-to-Network Relay, Based on that information, including controlling communications, The method described in Appendix 1. (Note 3) That information includes information for swapping Internet Protocol (IP) addresses for communication. The method described in Appendix 2. (Note 4) This further includes transmitting the PDU Session Identity (ID) for communication and the IP address for communication. The method described in Appendix 2. (Note 5) This further includes receiving information indicating that the Remote UE is authorized to perform communication, The method described in any one of the appendices 2 to 4. (Note 6) This further includes sending information indicating that the Remote UE is requesting communication. The method described in any one of the appendices 2 to 5. (Note 7) This further includes receiving information indicating that the network accepts the communication requested by the Remote UE. The method described in Appendix 6. (Note 8) The Remote UE further includes sending information indicating that it supports connections via a first ProSe UE-to-Network Relay and a second ProSe UE-to-Network Relay. The method described in any one of the appendices 1 through 7. (Note 9) A method for a first communication device, The Remote User Equipment (UE) receives information indicating that it supports connections via the first ProSe UE-to-Network Relay and connections via the second ProSe UE-to-Network Relay, A method comprising sending information indicating that the Remote UE is authorized to perform communication via a first ProSe UE-to-Network Relay and a second ProSe UE-to-Network Relay. (Note 10) Receiving information indicating that the Remote UE is requesting communication, Selecting a second communication device, Transmitting information to a second communication device, Receiving information to control the communication, and information indicating that the network accepts the communication requested by the Remote UE, The further includes transmitting information for controlling communications, and information indicating that the network accepts communications requested by the Remote UE, The method described in Appendix 9. (Note 11) Receiving a Protocol Data Unit (PDU), Session Identity (ID), and Internet Protocol (IP) address for communication, Further includes transmitting the PDU Session ID and IP address to a second communication device. The method described in Appendix 10. (Note 12) A method for a first communication device, To communicate with the second communication device, A method comprising sending information to a second communication device indicating that the Remote User Equipment (UE) is authorized to perform communication via a first ProSe UE-to-Network Relay and a second ProSe UE-to-Network Relay. (Note 13) A method for a first communication device, Information is received from the second communication device indicating that the Remote User Equipment (UE) is requesting communication via the first ProSe UE-to-Network Relay and the second ProSe UE-to-Network Relay, A method comprising transmitting information for controlling communication to a second communication device. (Note 14) The Remote UE sends information to the third communication device indicating that it is requesting communication via the first ProSe UE-to-Network Relay and the second ProSe UE-to-Network Relay, The Remote UE further includes receiving information from a third communication device indicating that it is authorized to establish communication, The method described in Appendix 13. (Note 15) Information indicating that the Remote UE is requesting communication via the first ProSe UE-to-Network Relay and the second ProSe UE-to-Network Relay, and information indicating that the first communication device is responding to that communication, are transmitted to the fourth communication device. The Remote UE further includes receiving a policy from a fourth communication device that contains information indicating that it is permitted to establish communication, The method described in Appendix 13 or 14. (Note 16) The further includes transmitting to a fifth communication device information indicating that the Remote UE is requesting communication via a first ProSe UE-to-Network Relay and a second ProSe UE-to-Network Relay, as well as information for controlling such communication. The method described in any one of the appendices 13 to 15. (Note 17) A method for a first communication device, Receiving information for controlling communication via the first ProSe UE-to-Network Relay and the second ProSe UE-to-Network Relay, A method that includes performing communication based on that information. (Note 18) A method for a first communication device, Information is received from the second communication device indicating that the Remote User Equipment (UE) is requesting communication via the first ProSe UE-to-Network Relay and the second ProSe UE-to-Network Relay, A method comprising sending information to a second communication device indicating that the Remote UE is authorized to establish communication. (Note 19) A method for a first communication device, The Remote User Equipment (UE) receives from the second communication device information indicating that it is requesting communication via the first ProSe UE-to-Network Relay and the second ProSe UE-to-Network Relay, as well as information indicating that the second communication device is compatible with that communication. A method comprising sending a policy to a second communication device that includes information indicating that the Remote UE is permitted to establish communication. (Note 20) Remote User Equipment (UE), The means of performing the registration procedure, Remote User Equipment (UE) comprising means for performing a Protocol Data Unit (PDU) session establishment procedure via a first ProSe UE-to-Network Relay, and a PDU session establishment procedure via a second ProSe UE-to-Network Relay. (Note 21) Means for receiving information for controlling communication via the first ProSe UE-to-Network Relay and the second ProSe UE-to-Network Relay, It is equipped with means for controlling communications based on that information. Remote UE as described in Appendix 20. (Note 22) That information includes information for swapping Internet Protocol (IP) addresses for communication. Remote UE as described in Appendix 21. (Note 23) It further comprises a PDU Session Identity (ID) for communication and means for transmitting an IP address for communication. Remote UE as described in Appendix 21. (Note 24) The Remote UE further provides means for receiving information indicating that it is authorized to perform communication. Remote UE as described in any one of the appendices 21 to 23. (Note 25) It further includes means for sending information indicating that the Remote UE is requesting communication. The Remote UE described in any one of the appendices 21 to 24. (Note 26) The network further includes means for receiving information indicating that it accepts communication requested by the Remote UE. Remote UE as described in Appendix 25. (Note 27) The Remote UE further includes means for transmitting information indicating that it supports connections via a first ProSe UE-to-Network Relay and a second ProSe UE-to-Network Relay. Remote UE as described in any one of the appendices 20 to 26. (Note 28) A first communication device, A means for receiving information indicating that the Remote User Equipment (UE) supports connections via the first ProSe UE-to-Network Relay and the second ProSe UE-to-Network Relay, A first communication device comprising means for transmitting information indicating that a Remote UE is authorized to perform communication via a first ProSe UE-to-Network Relay and a second ProSe UE-to-Network Relay. (Note 29) A means of receiving information indicating that the Remote UE is requesting communication, Means for selecting a second communication device, Means for transmitting information to a second communication device, Means for receiving information for controlling communications, and information indicating that the network accepts communications requested by the Remote UE, The system further comprises means for transmitting information for controlling communications and information indicating that the network accepts communications requested by the Remote UE. The first communication device described in Appendix 28. (Note 30) Means for receiving a Protocol Data Unit (PDU) Session Identity (ID) for communication, and an Internet Protocol (IP) address for communication, The system further includes means for transmitting the PDU Session ID and IP address to a second communication device. The first communication device described in Appendix 29. (Note 31) A first communication device, A means for communicating with a second communication device, A first communication device comprising means for transmitting information to a second communication device indicating that Remote User Equipment (UE) is authorized to perform communication via a first ProSe UE-to-Network Relay and a second ProSe UE-to-Network Relay. (Note 32) A first communication device, A means for receiving information from a second communication device indicating that Remote User Equipment (UE) is requesting communication via a first ProSe UE-to-Network Relay and a second ProSe UE-to-Network Relay, A first communication device equipped with means for transmitting information for controlling that communication to a second communication device. (Note 33) Means for transmitting information to a third communication device indicating that the Remote UE is requesting communication via a first ProSe UE-to-Network Relay and a second ProSe UE-to-Network Relay, The Remote UE further comprises means for receiving information from a third communication device indicating that it is authorized to establish its communication. The first communication device described in Appendix 32. (Note 34) Means for transmitting to a fourth communication device information indicating that the Remote UE is requesting communication via the first ProSe UE-to-Network Relay and the second ProSe UE-to-Network Relay, and information indicating that the first communication device is responding to that communication, The Remote UE further comprises means for receiving a policy from a fourth communication device that includes information indicating that it is authorized to establish its communication. The first communication device as described in Appendix 32 or 33. (Note 35) The system further includes means for transmitting to a fifth communication device information indicating that the Remote UE is requesting communication via a first ProSe UE-to-Network Relay and a second ProSe UE-to-Network Relay, as well as information for controlling such communication. The first communication device described in any one of the appendices 32 to 34. (Note 36) A first communication device, Means for receiving information for controlling communication via the first ProSe UE-to-Network Relay and the second ProSe UE-to-Network Relay, A first communication device equipped with means for performing communication based on that information. (Note 37) A first communication device, A means for receiving information from a second communication device indicating that Remote User Equipment (UE) is requesting communication via a first ProSe UE-to-Network Relay and a second ProSe UE-to-Network Relay, A first communication device comprising means for transmitting information to a second communication device indicating that the Remote UE is authorized to establish its communication. (Note 38) A first communication device, Means for receiving from a second communication device information indicating that a Remote User Equipment (UE) is requesting communication via a first ProSe UE-to-Network Relay and a second ProSe UE-to-Network Relay, and information indicating that the second communication device is compatible with communication, A first communication device, including means for transmitting a policy to a second communication device that contains information indicating that the Remote UE is authorized to establish its communication.

[0465] This application claims priority under Indian Patent Application No. 202311030373, filed on 27 April 2023, the disclosure of which is incorporated herein by reference in its entirety. [Explanation of symbols]

[0466] 20 Data Networks 201 AF 2011 Transceiver Circuit 2012 Network Interface 2013 Controller 2014 Memory 20141 Operating Systems 20142 Communication Control Module 201421 Transceiver Control Module 3 UE 300 NETWORK RELAY UE 310 REMOTE UE 31 Transceiver Circuit 32 Antennas 33 Controllers 34 User Interface 35 USIM 36 memory 361 Operating Systems 362 Communication control module 3621 Transceiver Control Module 5 (R)AN Node 51 Transceiver Circuit 52 Antennas 53 Network Interfaces 54 Controllers 55 memory 551 Operating Systems 552 Communication control module 5521 Transceiver Control Module 60 RU 601 Transceiver Circuit 602 Antenna 603 Network Interface 604 Controller 605 memory 6051 Operating System 6052 Communication Control Module 60521 Transceiver Control Module 61 DU 611 Transceiver Circuit 612 Network Interfaces 613 Controller 614 memory 6141 Operating Systems 6142 Communication control module 61421 Transceiver Control Module 62 CU 621 Transceiver Circuit 622 Network Interfaces 623 Controller 624 memory 6241 Operating Systems 6242 Communication control module 62421 Transceiver Control Module 7 Core Network 70 AMF 701 Transceiver Circuit 702 Network Interface 703 Controller 704 memory 7041 Operating System 7042 Communication control module 70421 Transceiver Control Module 71 SMF 711 Transceiver Circuit 712 Network Interfaces 713 Controller 714 memory 7141 Operating Systems 7142 Communication control module 71421 Transceiver Control Module 72 UPF 721 Transceiver Circuit 722 Network Interfaces 723 Controller 724 memory 7241 Operating Systems 7242 Communication control module 72421 Transceiver Control Module 73 PCF 731 Transceiver Circuit 732 Network Interfaces 733 Controller 734 memory 7341 Operating Systems 7342 Communication control module 73421 Transceiver Control Module 74 NWDAF 75 UDM 751 Transceiver Circuit 752 Network Interfaces 753 Controller 754 memory 7541 Operating Systems 7542 Communication control module 75421 Transceiver Control Module 76 NSSF

Claims

1. Follow the registration procedure, This includes performing a Protocol Data Unit (PDU) Session establishment procedure via a first ProSe UE-to-Network Relay, and a PDU Session establishment procedure via a second ProSe UE-to-Network Relay. Remote User Equipment (UE) method.

2. Receiving information for controlling communication via the first ProSe UE-to-Network Relay and the second ProSe UE-to-Network Relay, Includes controlling the communication based on the aforementioned information, The method according to claim 1.

3. The information includes information for swapping Internet Protocol (IP) addresses for the communication. The method according to claim 2.

4. Further includes transmitting a PDU Session Identity (ID) for the aforementioned communication and an IP address for the aforementioned communication. The method according to claim 2.

5. The Remote UE further includes receiving information indicating that it is authorized to perform the communication, The method according to any one of claims 2 to 4.

6. The further includes transmitting information indicating that the Remote UE is requesting the communication, The method according to any one of claims 2 to 5.

7. The further includes receiving information indicating that the network accepts the communication requested by the Remote UE, The method according to claim 6.

8. The Remote UE further includes transmitting information indicating that it supports connections via the first ProSe UE-to-Network Relay and connections via the second ProSe UE-to-Network Relay. The method according to any one of claims 1 to 7.

9. Receiving information indicating that the Remote User Equipment (UE) supports connections via the first ProSe UE-to-Network Relay and connections via the second ProSe UE-to-Network Relay, The Remote UE includes transmitting information indicating that it is authorized to perform communication via the first ProSe UE-to-Network Relay and the second ProSe UE-to-Network Relay. A method for a first communication device.

10. Receiving information indicating that the Remote UE is requesting the communication, Selecting a second communication device, Transmitting the information to the second communication device, Receiving information for controlling the aforementioned communication, and information indicating that the network accepts the aforementioned communication requested by the Remote UE, The further includes transmitting information for controlling the communication and information indicating that the network accepts the communication requested by the Remote UE, The method according to claim 9.

11. The receiving of a Protocol Data Unit (PDU) Session Identity (ID) for the aforementioned communication, and an Internet Protocol (IP) address for the aforementioned communication, The further includes transmitting the PDU Session ID and the IP address to the second communication device. The method according to claim 10.

12. To communicate with the second communication device, This includes transmitting information to the second communication device indicating that the Remote User Equipment (UE) is authorized to perform communication via the first ProSe UE-to-Network Relay and the second ProSe UE-to-Network Relay, A method for a first communication device.

13. Receiving information from the second communication device indicating that the Remote User Equipment (UE) is requesting communication via the first ProSe UE-to-Network Relay and the second ProSe UE-to-Network Relay, This includes transmitting information for controlling the aforementioned communication to the second communication device. A method for a first communication device.

14. Transmitting to the third communication device the information indicating that the Remote UE is requesting the communication via the first ProSe UE-to-Network Relay and the second ProSe UE-to-Network Relay, The Remote UE further includes receiving information from the third communication device indicating that it is authorized to establish the communication, The method according to claim 13.

15. The Remote UE is requesting the communication via the first ProSe UE-to-Network Relay and the second ProSe UE-to-Network Relay, and the information indicating that the first communication device is compatible with the communication is transmitted to the fourth communication device. The Remote UE further includes receiving a policy from the fourth communication device that includes the information indicating that it is authorized to establish the communication, The method according to claim 13 or 14.

16. The further includes transmitting to a fifth communication device the information indicating that the Remote UE is requesting the communication via the first ProSe UE-to-Network Relay and the second ProSe UE-to-Network Relay, and the information for controlling the communication. The method according to any one of claims 13 to 15.

17. Receiving information for controlling communication via the first ProSe UE-to-Network Relay and the second ProSe UE-to-Network Relay, This includes performing the communication based on the aforementioned information, A method for a first communication device.

18. Receiving information from the second communication device indicating that the Remote User Equipment (UE) is requesting communication via the first ProSe UE-to-Network Relay and the second ProSe UE-to-Network Relay, This includes transmitting information to the second communication device indicating that the Remote UE is authorized to establish the communication, A method for a first communication device.

19. Receiving from the second communication device information indicating that the Remote User Equipment (UE) is requesting communication via the first ProSe UE-to-Network Relay and the second ProSe UE-to-Network Relay, and information indicating that the second communication device is compatible with said communication, This includes transmitting to the second communication device a policy that includes information indicating that the Remote UE is authorized to establish the communication, A method for a first communication device.

20. Means for performing the registration procedure, The system comprises means for performing a first ProSe UE-to-Network Relay procedure for establishing a Protocol Data Unit (PDU) session, and a second ProSe UE-to-Network Relay procedure for establishing a PDU session. Remote User Equipment (UE).

21. Means for receiving information for controlling communication via the first ProSe UE-to-Network Relay and the second ProSe UE-to-Network Relay, The system includes means for controlling the communication based on the aforementioned information. Remote UE as described in claim 20.

22. The information includes information for swapping Internet Protocol (IP) addresses for the communication. Remote UE as described in claim 21.

23. The system further comprises means for transmitting a PDU Session Identity (ID) for the aforementioned communication and an IP address for the aforementioned communication. Remote UE as described in claim 21.

24. The Remote UE further comprises means for receiving information indicating that it is authorized to perform the communication. Remote UE according to any one of claims 21 to 23.

25. The system further comprises means for transmitting information indicating that the Remote UE is requesting the communication. Remote UE according to any one of claims 21 to 24.

26. The network further comprises means for receiving information indicating that it accepts the communication requested by the Remote UE. Remote UE as described in claim 25.

27. The Remote UE further comprises means for transmitting information indicating that it supports a connection via the first ProSe UE-to-Network Relay and a connection via the second ProSe UE-to-Network Relay. Remote UE according to any one of claims 20 to 26.

28. A means for receiving information indicating that Remote User Equipment (UE) supports connections via a first ProSe UE-to-Network Relay and a second ProSe UE-to-Network Relay, The Remote UE includes means for transmitting information indicating that it is authorized to perform communication via the first ProSe UE-to-Network Relay and the second ProSe UE-to-Network Relay. The first communication device.

29. Means for receiving information indicating that the Remote UE is requesting the communication, Means for selecting a second communication device, Means for transmitting the information to the second communication device, Means for receiving information for controlling the aforementioned communication, and information indicating that the network accepts the aforementioned communication requested by the Remote UE, The system further comprises means for transmitting information for controlling the communication and information indicating that the network accepts the communication requested by the Remote UE. The first communication device according to claim 28.

30. Means for receiving a Protocol Data Unit (PDU) Session Identity (ID) for the aforementioned communication, and an Internet Protocol (IP) address for the aforementioned communication, The system further includes means for transmitting the PDU Session ID and the IP address to the second communication device. The first communication device according to claim 29.

31. A means for communicating with a second communication device, The Remote User Equipment (UE) includes means for transmitting information to the second communication device indicating that it is authorized to perform communication via the first ProSe UE-to-Network Relay and the second ProSe UE-to-Network Relay. The first communication device.

32. Means for receiving information from a second communication device indicating that Remote User Equipment (UE) is requesting communication via a first ProSe UE-to-Network Relay and a second ProSe UE-to-Network Relay, The device includes means for transmitting information for controlling the aforementioned communication to the second communication device. The first communication device.

33. Means for transmitting to a third communication device the information indicating that the Remote UE is requesting the communication via the first ProSe UE-to-Network Relay and the second ProSe UE-to-Network Relay, The Remote UE further comprises means for receiving information from the third communication device indicating that it is authorized to establish the communication. The first communication device according to claim 32.

34. Means for transmitting to a fourth communication device the information indicating that the Remote UE is requesting the communication via the first ProSe UE-to-Network Relay and the second ProSe UE-to-Network Relay, and the information indicating that the first communication device is responding to the communication, The system further comprises means for receiving from the fourth communication device a policy containing the information indicating that the Remote UE is authorized to establish the communication. The first communication device according to claim 32 or 33.

35. The system further comprises means for transmitting to a fifth communication device the information indicating that the Remote UE is requesting the communication via the first ProSe UE-to-Network Relay and the second ProSe UE-to-Network Relay, and the information for controlling the communication. The first communication device according to any one of claims 32 to 34.

36. Means for receiving information for controlling communication via the first ProSe UE-to-Network Relay and the second ProSe UE-to-Network Relay, The system includes means for performing the communication based on the aforementioned information. The first communication device.

37. Means for receiving information from a second communication device indicating that Remote User Equipment (UE) is requesting communication via a first ProSe UE-to-Network Relay and a second ProSe UE-to-Network Relay, The Remote UE includes means for transmitting information to the second communication device indicating that it is authorized to establish the communication. The first communication device.

38. Means for receiving from the second communication device information indicating that Remote User Equipment (UE) is requesting communication via the first ProSe UE-to-Network Relay and the second ProSe UE-to-Network Relay, and information indicating that the second communication device is compatible with said communication, The means includes transmitting to the second communication device a policy containing information indicating that the Remote UE is authorized to establish the communication, The first communication device.

Images