Method of UE, method of UPF, method of AMF, UE, UPF, and amf

Abstract

An aspect of this disclosure includes a method of a UE. The method includes establishing two 3GPP accesses. The method includes determining whether to reduce amount of traffic sent over one access among the two 3GPP accesses or to duplicate the traffic or to switch the traffic, based on a maximum measured value of a first parameter and a threshold value of the first parameter.

Description

METHOD OF UE, METHOD OF UPF, METHOD OF AMF, UE, UPF, AND AMF

[0001] The present disclosure relates to a method of a UE, a method of a UPF, a method of an AMF, a UE, a UPF and an AMF, etc.

[0002] Access Traffic Steering, Switching and Splitting (ATSSS) considers multi-access scenario where UE is connected via one 3GPP access and one non-3GPP access, whereas Dual Steer (DS) considers a scenario where UE is connected via dual 3GPP accesses.

[0003] In the NPL 2, different use cases and potential new requirements are captured based on DS. In this disclosure, the following problem statements are addressed.

[0004] NPL 1: 3GPP TR 21.905: "Vocabulary for 3GPP Specifications". V17.1.0 (2021-12) NPL 2: 3GPP TS 22.841: " Study on Upper layer traffic steer, switch and split over dual 3GPP access". V2.0.0 (2023-09) NPL 3: 3GPP TS 23.501: "System architecture for the 5G System (5GS)". V18.3.0 (2023-09) NPL 4: 3GPP TS 23.502: "Procedures for the 5G System (5GS)". V18.3.0 (2023-09) NPL 5: 3GPP TS 23.503: "Policy and charging control framework for the 5G System (5GS) Stage 2". V18.3.0 (2023-09) NPL 6: RFC 5481: "Packet Delay Variation Applicability Statement" https: / / datatracker.ietf.org / doc / html / rfc5481 NPL 7: 3GPP TS 37.340: "Multi-connectivity Stage 2". V17.6.0 (2023-09)

[0005] For example, the problem to solve is that there is no disclosure in the above 3GPP specification mentioned in Background how to realize Dual Steer (DS) that considers a scenario where UE is connected via dual 3GPP accesses.

[0006] For example, the objective of this invention is to solve the above problem.

[0007] In one aspect there is provided a method of a UE comprising: 　　establishing two 3GPP accesses; and 　　determining whether to reduce amount of traffic sent over one access among the two 3GPP accesses or to duplicate the traffic or to switch the traffic, based on a maximum measured value of a first parameter and a threshold value of the first parameter.

[0008] In one aspect there is provided a method of a UPF comprising: 　　communicating with a UE establishing two 3GPP accesses; and 　　determining whether to reduce amount of traffic sent over one access among the two 3GPP accesses or to duplicate the traffic or to switch the traffic, based on a maximum measured value of a first parameter and a threshold value of the first parameter.

[0009] In one aspect there is provided a method of an AMF comprising: 　　sending, to a PCF, Dual 3GPP access support information indicating that a UE supports dual 3GPP access and ID of a UE, in a case where the AMF receives the Dual 3GPP access support information and first support information indicating that the UE supports for PNI-NPN as a network slice and dual 3GPP access; 　　receiving, from the PCF, an eURSP (enhanced URSP) rule for establishing Multi-Access / Dual-Steer PDU session; and 　　sending, to the UE, the eURSP rule.

[0010] In one aspect there is provided a method of a UE comprising: 　　sending, to an AMF, Dual 3GPP access support information indicating that the UE supports dual 3GPP access and first support information indicating that the UE supports for PNI-NPN as a network slice and dual 3GPP access; and 　　receiving, from the AMF, an eURSP rule for establishing Multi-Access / Dual Steer PDU session.

[0011] In one aspect there is provided a method of an AMF comprising: 　　receiving, from a UE, first support information indicating that the UE supports for PNI-NPN S-NSSAIs and requesting S-NSSAI in a case where PDU session establishment based on an eURSP rule is triggered; 　　selecting a SMF which supports for PNI-NPN S-NSSAIs, in a case where support of the UE for the S-NSSAI is verified; 　　receiving, from the SMF, a Dual Steer rule used for controlling traffic steering, switching and splitting of dual 3GPP access; and 　　sending, to the UE, the Dual Steer rule.

[0012] In one aspect there is provided a method of a UE comprising: 　　sending, to an AMF, first support information indicating that the UE supports for PNI-NPN S-NSSAIs and requesting S-NSSAI in a case where the UE triggers PDU session establishment based on an eURSP rule; and 　　receiving, from the AMF, a Dual Steer rule used for controlling traffic steering, switching and splitting of dual 3GPP access, in a case where support of the UE for the S-NSSAI is verified.

[0013] In one aspect there is provided a method of an AMF comprising: 　　receiving, from a UE, first support information indicating that the UE supports for PNI-NPN S-NSSAIs and requesting S-NSSAI and SAG information indicating a condition or a rule related to the use of the S-NSSAI by the UE, in a case where PDU session establishment based on an eURSP rule is triggered; 　　selecting a SMF which supports for PNI-NPN S-NSSAIs, in a case where support of the UE for the S-NSSAI and the SAG information are verified; 　　receiving, from the SMF, a Dual Steer rule used for controlling traffic steering, switching and splitting of dual 3GPP access; and 　　sending, to the UE, the Dual Steer rule.

[0014] In one aspect there is provided a method of a UE comprising: 　　sending, to an AMF, first support information indicating that the UE supports for PNI-NPN S-NSSAIs and requesting S-NSSAI and SAG information indicating a condition or a rule related to the use of the S-NSSAI by the UE, in a case where the UE triggers PDU session establishment based on an eURSP rule; and 　　receiving, from the AMF, a Dual Steer rule used for controlling traffic steering, switching and splitting of dual 3GPP access, in a case where support of the UE for the S-NSSAI and the SAG information are verified.

[0015] In one aspect there is provided a method of an AMF comprising: 　　receiving, from a PCF, a dual steer rule of dual 3GPP access for a UE that is updated based on a request from an AF; and 　　sending, to the UE, the dual steer rule, 　　wherein the dual steer rule is included in an eURSP rule.

[0016] In one aspect there is provided a method of a UE comprising: 　　performing a registration procedure with an AMF; and 　　receiving, from the AMF, a dual steer rule of dual 3GPP access for the UE, in a case where the dual steer rule is updated based on a request from an AF, 　　wherein the dual steer rule is included in an eURSP rule.

[0017] In one aspect there is provided a method of an AMF comprising: 　　receiving, from a SMF, an updated dual steer rule of dual 3GPP access derived based on a request from an AF; and 　　sending, to a UE, the updated dual steer rule.

[0018] In one aspect there is provided a method of a UE comprising: 　　performing a PDU session establishment procedure with an AMF; and 　　receiving, from the AMF, an updated dual steer rule of dual 3GPP access derived in a case where the updated dual steer rule is derived based on a request from an AF.

[0019] In one aspect there is provided a UE comprising: 　　means for establishing two 3GPP accesses; and 　　means for determining whether to reduce amount of traffic sent over one access among the two 3GPP accesses or to duplicate the traffic or to switch the traffic, based on a maximum measured value of a first parameter and a threshold value of the first parameter.

[0020] In one aspect there is provided a UPF comprising: 　　means for communicating with a UE establishing two 3GPP accesses; and 　　means for determining whether to reduce amount of traffic sent over one access among the two 3GPP accesses or to duplicate the traffic or to switch the traffic, based on a maximum measured value of a first parameter and a threshold value of the first parameter.

[0021] In one aspect there is provided an AMF comprising: 　　means for sending, to a PCF, Dual 3GPP access support information indicating that a UE supports dual 3GPP access and ID of a UE, in a case where the AMF receives the Dual 3GPP access support information and first support information indicating that the UE supports for PNI-NPN as a network slice and dual 3GPP access; 　　means for receiving, from the PCF, an eURSP (enhanced URSP) rule for establishing Multi-Access / Dual-Steer PDU session; and 　　means for sending, to the UE, the eURSP rule.

[0022] In one aspect there is provided a UE comprising: 　　means for sending, to an AMF, Dual 3GPP access support information indicating that the UE supports dual 3GPP access and first support information indicating that the UE supports for PNI-NPN as a network slice and dual 3GPP access; and 　　means for receiving, from the AMF, an eURSP rule for establishing Multi-Access / Dual-Steer PDU session.

[0023] In one aspect there is provided an AMF comprising: 　　means for receiving, from a UE, first support information indicating that the UE supports for PNI-NPN S-NSSAIs and requesting S-NSSAI in a case where PDU session establishment based on an eURSP rule is triggered; 　　means for selecting a SMF which supports for PNI-NPN S-NSSAIs, in a case where support of the UE for the S-NSSAI is verified; 　　means for receiving, from the SMF, a Dual Steer rule used for controlling traffic steering, switching and splitting of dual 3GPP access; and 　　means for sending, to the UE, the Dual Steer rule.

[0024] In one aspect there is provided a UE comprising: 　　means for sending, to an AMF, first support information indicating that the UE supports for PNI-NPN S-NSSAIs and requesting S-NSSAI in a case where the UE triggers PDU session establishment based on an eURSP rule; and 　　means for receiving, from the AMF, a Dual Steer rule used for controlling traffic steering, switching and splitting of dual 3GPP access, in a case where support of the UE for the S-NSSAI is verified.

[0025] In one aspect there is provided an AMF comprising: 　　means for receiving, from a UE, first support information indicating that the UE supports for PNI-NPN S-NSSAIs and requesting S-NSSAI and SAG information indicating a condition or a rule related to the use of the S-NSSAI by the UE, in a case where PDU session establishment based on an eURSP rule is triggered; 　　means for selecting a SMF which supports for PNI-NPN S-NSSAIs, in a case where support of the UE for the S-NSSAI and the SAG information are verified; 　　means for receiving, from the SMF, a Dual Steer rule used for controlling traffic steering, switching and splitting of dual 3GPP access; and 　　means for sending, to the UE, the Dual Steer rule.

[0026] In one aspect there is provided a UE comprising: 　　means for sending, to an AMF, first support information indicating that the UE supports for PNI-NPN S-NSSAIs and requesting S-NSSAI and SAG information indicating a condition or a rule related to the use of the S-NSSAI by the UE, in a case where the UE triggers PDU session establishment based on an eURSP rule; and 　　means for receiving, from the AMF, a Dual Steer rule used for controlling traffic steering, switching and splitting of dual 3GPP access, in a case where support of the UE for the S-NSSAI and the SAG information are verified.

[0027] In one aspect there is provided an AMF comprising: 　　means for receiving, from a PCF, a dual steer rule of dual 3GPP access for a UE that is updated based on a request from an AF; and 　　means for sending, to the UE, the dual steer rule, 　　wherein the dual steer rule is included in an eURSP rule.

[0028] In one aspect there is provided a UE comprising: 　　means for performing a registration procedure with an AMF; and 　　means for receiving, from the AMF, a dual steer rule of dual 3GPP access for the UE, in a case where the dual steer rule is updated based on a request from an AF, 　　wherein the dual steer rule is included in an eURSP rule.

[0029] In one aspect there is provided an AMF comprising: 　　means for receiving, from a SMF, an updated dual steer rule of dual 3GPP access derived based on a request from an AF; and 　　means for sending, to a UE, the updated dual steer rule.

[0030] In one aspect there is provided a UE comprising: 　　means for performing a PDU session establishment procedure with an AMF; and 　　means for receiving, from the AMF, an updated dual steer rule of dual 3GPP access derived in a case where the updated dual steer rule is derived based on a request from an AF.

[0031] According to the present disclosure, it is possible to provide a method of a UE, a method of a UPF, a method of an AMF, a UE, a UPF and an AMF.

[0032] Examples of the disclosure will now be described, by way of example, with reference to the tables and the accompanying drawings in which:

[0033] (Table 1) 　　Table 1 is a Dual Steer PDU Session Control information in the PCC rule in First example of the First Aspect; (Table 2) 　　Table 2 is Dual Steer PDU Session Control information in the PCC rule when steering modes is divided into different types in Second example of the First Aspect; (Table 3) 　　Table 3 is a Dual Steer rule for UE in the Second example of the First Aspect; (Table 4) 　　Table 4 is Dual Steer (DS) information element(s) in the Fourth example of the First Aspect; (Table 5) 　　Table 5 is a DS route selection related information element(s) in the Fourth example of the First Aspect;Fig. 1 is an example of RTT variation calculation by UE reuses PMFP Echo Request / Response messages in the Third example of the First Aspect;Fig. 2 is an example of PMFP ECHO REQUEST WITH TIMESTAMP message content in the Third example of the First Aspect;Fig. 3 is an example PMFP ECHO RESPONSE WITH TIMESTAMP message content in the Third example of the First Aspect;Fig. 4 is an example of PMFP Message Types message content in the Third example of the First Aspect;Fig. 5 is an Example of how Load-Balancing mode is applied for RTT and RTT_PDV in the Third example of the First Aspect;Fig. 6 is an Example of how Load-Balancing mode is applied for UL delay and UL_PDV in the Third example of the First Aspect;Fig. 7 is an Example of evaluation of RTT delay and RTT PDV and the resulting UE and UPF behaviour in redundant steering mode in the Third example of the First Aspect;Fig. 8 is an Example of evaluation of UL delay and UL PDV and the resulting UE behaviour in redundant steering mode in the Third example of the First Aspect;Fig. 9 is a eURSP rule in the Fourth example of the First Aspect;Fig. 10 is a Route selection descriptor list (legacy) in the Fourth example of the First Aspect;Fig. 11 is a Route selection descriptor (legacy) in the Fourth example of the First Aspect;Fig. 12 is a Dual Steer rule in the Fourth example of the First Aspect;Fig. 13 is a DS route selection rules in the Fourth example of the First Aspect;Fig. 14 is a UE Policy part information element(s) in the Fourth example of the First Aspect;Fig. 15 is a eURSP in UE Policy part information element(s) in the Fourth example of the First Aspect;Fig. 16 is a 3PDASP in the UE Policy part IE in the Fifth example of the First Aspect;Fig. 17 is a 3PDASP contents in the Fifth example of the First Aspect;Fig. 18 is a 3PDASP rule in the Fifth example of the First Aspect;Fig. 19 is a Selection criteria entries in 3PDASP rule in Fifth example of the First Aspect;Fig. 20 is a Selection criteria set entries in 3PDASP rule in Fifth example of the First Aspect;Fig. 21 is a MCC and MNC as the Selection criteria sub entry in 3PDASP rule in the Fifth example of the First Aspect;Fig. 22 is a MCC and MNC as the Selection criteria sub entry in 3PDASP rule for preferred PLMN roaming partner in the Fifth example of the First Aspect in the Fifth example of the First Aspect;Fig. 23 is a MCC, MNC and NID as the Selection criteria sub entry in 3PDASP rule for preferred SNPN network in the Fifth example of the First Aspect;Fig. 24 is a Priority information in the Selection criteria sub entry in 3PDASP rule for preferred access technology in the Fifth example of the First Aspect;Fig. 25 is encoding for Validity area in 3PDASP rule in 3PDASP rule in the Fifth example of the First Aspect;Fig. 26 is encoding for Location entry in 3PDASP rule in 3PDASP rule in the Fifth example of the First Aspect;Fig. 27 is encoding for Location entry {entry type =3GPP location} in 3PDASP rule in the Fifth example of the First Aspect;Fig 28 is encoding for 3GPP location field {field type = TAC} in 3PDASP rule in the Fifth example of the First Aspect;Fig. 29 is encoding for 3GPP location field {field type = EUTRA CI} in 3PDASP rule in the Fifth example of the First Aspect;Fig. 30 is encoding for 3GPP location field {field type = NR CI} in 3PDASP rule in the Fifth example of the First Aspect;Fig. 31 is encoding for Time of day in 3PDASP rule in the Fifth example of the First Aspect;Fig. 32 is encoding for Time of day sub field in 3PDASP rule in the Fifth example of the First Aspect;Fig. 33 is encoding for ToD sub field in 3PDASP rule in the Fifth example of the First Aspect;Fig. 34 is encoding for ToD sub field {field type = "time start" or "time stop" in 3PDASP rule in the Fifth example of the First Aspect;Fig. 35: ToD sub field {field type = "date start" or "date stop"} in 3PDASP rule in the Fifth example of the First Aspect;Fig. 36: ToD sub field {field type = "day of the week"} in 3PDASP rule in the Fifth example of the First Aspect;Fig. 37 is a Dual Steer rule provisioning in Second Aspect;Fig. 38 is a signaling diagram of the First example of the Second aspect;Fig. 39 is a signaling diagram of the Second example of the Second aspect;Fig. 40 is a signaling diagram of the Third example of the Second aspect;Fig. 41 is a signaling diagram of the Fourth example of the Second aspect;Fig. 42 is a signaling diagram of First example of the Third aspect;Fig. 43 is a signaling diagram of Second example of the Third aspect;Fig. 44 is a diagram illustrating a system overview;Fig. 45 is a block diagram illustrating a UE;Fig. 46 is a block diagram illustrating an (R)AN node;Fig. 47 is a diagram illustrating System overview of (R)AN node based on O-RAN architecture;Fig. 48 is a block diagram illustrating an RU;Fig. 49 is a block diagram illustrating a DU;Fig. 50 is a block diagram illustrating a CU;Fig. 51 is a block diagram illustrating an AMF;Fig. 52 is a block diagram illustrating an SMF;Fig. 53 is a block diagram illustrating a UPF;Fig. 54 is a block diagram illustrating a PCF;Fig. 55 is a block diagram illustrating an NWDAF;Fig. 56 is a block diagram illustrating a UDM;Fig. 57 is a block diagram illustrating an NSSF;Fig. 58 is a block diagram illustrating an NSACF;Fig. 59 is a block diagram illustrating an AUSF;Fig. 60 is a block diagram illustrating an NEF; andFig. 61 is a block diagram illustrating an AF.

[0034] For the purposes of the present document, the abbreviations given in NPL 1 and the following apply. An abbreviation defined in the present document takes precedence over the definition of the same abbreviation, if any, in NPL 1.

[0035] < Abbreviations > 3PDASP　　3GPP Dual Access discovery and Selection Policy 4G-GUTI　　4G Globally Unique Temporary UE Identity 5GC　　5G Core Network 5GLAN　　5G Local Area Network 5G HE AV　　5G Home Environment Authentication Vector 5G SE AV　　5G Serving Environment Authentication Vector 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 ABBA　　Anti-Bidding down Between Architectures 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 DS-LL　　Dual Steer Lower Layer 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 (roaming) 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 (roaming) LMF　　Location Management Function LoA　　Level of Automation LPP　　LTE Positioning Protocol LRF　　Location Retrieval Function MC 　　Multi-Connectivity 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 MP-DCCP　　Multi-Path - Datagram Congestion Control Protocol MPTCP　　Multi-Path TCP Protocol MP-QUIC　　Multi-Path-Quick UDP Internet Connections 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

[0036] < Definitions > 　　For the purposes of the present document, the terms and definitions given in NPL 1 and the following apply. A term defined in the present document takes precedence over the definition of the same term, if any, in NPL 1.

[0037] < General > 　　For example, the objective of this application is to disclose at least one of the solutions of at least one of the following problems to realize Dual Steer (DS) that considers a scenario where UE is connected via dual 3GPP accesses: 1.　　How do the UE & network determine steering functionalities and steering modes for routing the traffic across dual 3GPP accesses? If the problem is not addressed, the UE and the network cannot route the traffic across two 3GPP accesses. 2.　　How does the UE select the second PLMN / NPN in case of different 3GPP networks after an initial PLMN / NPN was selected for the UE? If the problem is not addressed, the UE and the network cannot route the traffic across two 3GPP accesses. 3.　　How to signal the additional dual 3GPP access-related configuration rules or changes to the rules between the network and UE? If problem is not addressed, the UE and the NW have no defined procedure for signaling the rules and cannot steer the traffic across two 3GPP accesses. 4.　　How to enable an NPN operator to: 　　4.1.　　configure / provision specific parameters related to traffic routing across two 3GPP accesses; and 　　4.2.　　Influence traffic routing across two 3GPP accesses based on (new / updated) user-plane requirements. 5.　　How the UE have two 3GPP accesses to configure Dual Steer (DS) in case where two 3GPP accesses are provided by the different USIM. For example, one 3GPP access is provided by an Operator A with a terrestrial network with USIM-A while the other 3GPP access is provided by an Operator B over NTN (Non-Terrestrial Network) with USIM-B.

[0038] If the problem is not addressed, the NPN operator has no means to provision specific parameters related to routing across dual 3GPP access and cannot influence traffic routing according to new user plane requirements.

[0039] Those skilled in the art will appreciate that elements in the figures are illustrated for simplicity and may not have necessarily been drawn to scale. Furthermore, in terms of the construction of the device, one or more components of the device may have been represented in the figures by conventional symbols, and the figures may show only those specific details that are pertinent to understanding the Aspects of the present disclosure so as not to obscure the figures with details that will be readily apparent to those skilled in the art having the benefit of the description herein. For the purpose of promoting an understanding of the principles of the disclosure, reference will now be made to the Aspect illustrated in the figures and specific language will be used to describe them.

[0040] It will nevertheless be understood that no limitation of the scope of the disclosure is thereby intended. Such alterations and further modifications in the illustrated system, and such further applications of the principles of the disclosure as would normally occur to those skilled in the art are to be construed as being within the scope of the present disclosure.

[0041] The terms "comprises", "comprising", or any other variations thereof, are intended to cover a non-exclusive inclusion, such that a process or method that comprises a list of steps does not include only those steps but may include other steps not expressly listed or inherent to such a process or method. Similarly, one or more devices or entities or sub-systems or elements or structures or components preceded by "comprises... a" does not, without more constraints, preclude the existence of other devices, sub-systems, elements, structures, components, additional devices, additional sub-systems, additional elements, additional structures or additional components. Appearances of the phrase "in an Aspect", "in another Aspect" and similar language throughout this specification may, but not necessarily do, all refer to the same Aspect.

[0042] Unless otherwise defined, all technical and scientific terms used herein have the same meaning as commonly understood by those skilled in the art to which this disclosure belongs. The system, methods, and examples provided herein are only illustrative and not intended to be limiting.

[0043] In the following specification and the claims, reference will be made to a number of terms, which may be defined to have the following meanings. The singular forms "a", "an", and "the" include plural references unless the context clearly dictates otherwise. As used herein, information is associated with data and knowledge, as data is meaningful information and represents the values attributed to parameters. Further knowledge signifies understanding of an abstract or concrete concept. Note that this example system is simplified to facilitate description of the disclosed subject matter and is not intended to limit the scope of this disclosure. Other devices, systems, and configurations may be used to implement the Aspects disclosed herein in addition to, or instead of, a system, and all such Aspects are contemplated as within the scope of the present disclosure.

[0044] Each of Aspects (i.e., the First Aspect, the Second Aspect, and the Third Aspect) and elements included in the each of Aspects described below may be implemented independently or in combination with any other. These Aspects include novel characteristics different from one another. Accordingly, these Aspects contribute to achieving objects or solving problems different from one another and contribute to obtaining advantages different from one another.

[0045] Any lists described in following aspects include at least one parameter or multiple parameters.

[0046] An example object of this disclosure is to provide a method and apparatus that can solve the above-mentioned problem.

[0047] Definition of one parameter in one aspect or one example may be applied to another parameter which has same name of the one parameter in another aspect or another example. For example, definition of parameter A in one aspect or one example may be applied to parameter A in another aspect or another example.

[0048] In this disclosure, regarding listed parameters in the certain message, at least one of the listed parameters may be included in the certain message. For example, "the message including parameter A and parameter B" may mean "the message including at least one of parameter A and parameter B". In addition, for example, "A including (or containing, or similar wording etc.) B and C" may mean "A including at least one of B and C".

[0049] < First Aspect > 　　The first aspect addresses the definition of the appropriate rules for the UE 3 and the network to support routing of the user-plane traffic across two 3GPP access networks. 5GC may provide appropriate rules to the UE 3 as a part of session management, that is when the UE 3 is either in the process of establishing the PDU session or already has a PDU session established. In addition or alternatively, the rules can be provided as a part of non-session session management policy control.

[0050] Such rules include the Dual Steer rules in PCF 73. For non-session related management policy control, the 5GC may be able to provide policy information from the PCF 73 to the UE 3 using 3GPP Dual Access Network Discovery & Selection Policy (3PDSP) enhanced UE 3 Route Selection Policy (eURSP). For example, PCF 73 may provide, to the UE3, policy information. For example, PCF 73 may provide, to the UE3, policy information using 3GPP Dual Access Network Discovery & Selection Policy (3PDSP) enhanced UE 3 Route Selection Policy (eURSP). For session related management policy control, the 5GC may be able to provide appropriate rules, including Dual Steer rules, to the UE 3 during the session management procedure. The PCF control of Dual Steer for a detected service data flow (SDF) is enabled by including Dual Steer Session Control information in the PCC (Policy and Charging Control) rule. For example, 5GC node (for example PCF 73) may provide, to the UE3, Dual Steer rules. For example, 5GC node (for example PCF 73) may provide, to the UE3, Dual Steer rules during the session management procedure.

[0051] < First example of the First Aspect > 　　The first example of the First Aspect addresses the rules as a part of session management, i.e. the enablement of Dual 3GPP Access aka Dual Steer in PCF 73. The PCF control of Dual Steer for a detected service data flow (SDF) may be enabled by including Dual Steer PDU Session Control information in the PCC rule, as per the table below. The PCC rule may include all the information necessary for controlling the Dual Steer capabilities for a specific SDF. The information in the PCC rule may apply to the SDF regardless of the type of access network used for the packet. Regardless of "Category" in the Table 1, the at least one information in Table 1 may be included in the Dual Steer PDU Session Control information or the PCC rule.

[0052] Table 1: Dual Steer PDU Session Control information in the PCC rule

[0053] In Table 1, the IEs that apply to Multi Access Dual Steer policy and charging control rule (PCC rule) are disclosed. The information may be required to enable the user plane detection of the traffic and corresponding policy control and charging for a service data flow. The description for the disclosed information elements (IEs) may be provided in the Table 1. Further details to some of the IEs in the PCC rule may be given below: 　　Application descriptor(s) may relate to the application traffic, which can be identified using, e.g. Application ID and OS (OSId and an OSAppId). 　　Steering mode may include, e.g. at least one of active-standby, smallest-delay, priority-based, load-balancing, redundant steering mode, and others. Please note that steering modes can be further divided into sub-categories, depending on which modes require, e.g. active transmission on two 3GPP accesses simultaneously. For example, there could be a steering modes Type I and Steering modes Type II, where Steering mode Type II refers to all steering modes, including the ones that require simultaneous transmission on two 3GPP accesses, and hence can support modes such as load-balancing and redundant steering mode. Such categorization may require additional fields to indicate different steering modes. Table 2 gives an example. 　　Steering functionality may include at least one of MP-TCP functionality, MP-QUIC functionality, DualSteer-LL functionality, and MP-DCCP. Steering functionality may include other transport layer functionality. 　　Transport mode(s) may depend on the steering functionality. For example, if steering functionality is MP-QUIC, then the transport mode may be indicated. In other cases, such as Dual Steer-LL or MP-TCP, transport mode may not be used. 　　Threshold value(s) may refer to KPIs, namely delay (one-way and round-trip), packet delay variation with respect to one-way and round-trip delay, and packet loss rate. The threshold value(s) of these KPIs may determine the behaviour of a UE 3 and the network if they are exceeded. The threshold value(s) fields may include at least one of followings: 　　　　Maximum Round Trip Time; 　　　　Maximum Packet Loss Rate; 　　　　Maximum RTT PDV or a combination of RTT and RTT PDV; and 　　　　Maximum one-way delay or a combination of one-way delay and one-way PDV; 　　Preferred 3GPP Access combination may include the preferred combination of 3GP Accesses to configure Dual Steer. For example, it can be NR and NR, NR and eUTRA, eUTRA and eUTRA.

[0054] As Dual Steer functionality may apply to UEs with different TX / RX capabilities, which limits the support for certain steering rules, another variation of the PDU Session Control information in the PCC rule when steering mode is divided into different types is given in Table 2. Furthermore, a Dual-Steer capable UE may be a single UE with different TX / RX capabilities or may comprise two UEs (e.g. to support simultaneous transmission).

[0055] Regardless of "Category" in the Table 2, the at least one information in Table 2 may be included in the Dual Steer PDU Session Control information or the PCC rule.

[0056] Table 2: Dual Steer PDU Session Control information in the PCC rule when steering mode is divided into different types

[0057] < Second example of the First Aspect > 　　The second example of the First Aspect addresses the Dual Steer rules during the session management, i.e. the Dual Steer rules created or generated in SMF 71 that are sent both to the UE 3 and the UPF 72. Regardless of "Category" in the Table 3, the at least one information in Table 3 may be included in the Dual Steer rules.

[0058] Table 3: Dual Steer rules for UE

[0059] In Tables 1 to 3, the IEs that apply to the Dual Steer rules may be disclosed. For example, further details to some of the IEs in the Dual Steer rules are given below: 　　Threshold values with regard to the Round-Trip Time. The threshold values fields may include at least one of the followings: 　　　　Maximum Round Trip Time; 　　　　Maximum Packet Loss Rate; 　　　　Maximum RTT PDV or a combination of RTT and RTT PDV; and 　　　　Maximum one-way delay or a combination of one-way delay and one-way PDV, 　　Steering Functionality may identify whether the MPTCP functionality, the MPQUIC functionality, Dual Steer -LL or MP-DCCP functionality should be applied for the matching traffic. 　　Preferred 3GPP Access combination may indicate if only NR-NR accesses may be used or NR and eUTRA, eUTRA and eUTRA combination can also be used.

[0060] Please note that in this example also, there could be steering modes Type I and Steering modes Type II, where Steering mode Type II refers to all steering modes, including the ones that may require simultaneous transmission on two 3GPP accesses, and hence can support modes such as load-balancing and redundant steering mode.

[0061] < Third example of the First Aspect > 　　In the third example of the First Aspect, the method for calculation of round-trip delay variation by a UE 3 over 3GPP access network may be depicted. In general, Packet Delay Variation (PDV) threshold values can also be provided as a parameter by AF or can be defined for different services based on an agreement between, e.g. NPN and PLMN operators.

[0062] The calculation of RTT (Round Trip Time) delay variation can reuse some of the mechanisms for calculating RTT, already in prior art. The UE 3 may send PMFP ECHO REQUEST messages over one of the 3GPP accesses of the Dual Steer PDU session and receive PMFP ECHO RESPONSE messages from UPF 72 on the same access. For the RTT variation calculation, TPDV may represent the time over which the RTT variation is calculated. The timer TPDV may coincide with the timer T101, which may be used for calculating RTT. For each PMFP transaction i (a pair of request / response) messages, RTT variation can be calculated as RTT_var(i) = RTT(i)-RTT(min), RTT(min) is the delay with the lowest value for RTT (minimum) for the duration of timer TPDV. In NPL 6, formula for PDV(i) = D(i)-D(min) is given, where D(min) is the delay of the packet with the lowest value for delay (minimum) over the current test interval. Normally, PDV is calculated for a one-way delay. Round-trip measurements may give a cumulative indication of the delay variation present on both directions of the path.

[0063] Although Fig. 1 shows the UPF 72 as the network entity in the 5GC, network entity that communicates the PMFP Echo Request / Response messages with the UE 3 is not limited to the UPF 72 but also any 5GC entities. For example, AMF 70, SMF 71, PCF 73 and NEF 79 may be the network entity in the 5GC communicating with UE 3, instead of UPF 72 in Fig. 1.

[0064] For calculation of one-way delay (UL or DL) and corresponding PDV measurement, the existing 3GPP mechanisms, i.e. PMF and the ECHO REQUEST / ECHO RESPONSE messages can be reused, but using the modified messages. The new proposed messages are referred to as PMFP ECHO REQUEST WITH TIMESTAMP and PMFP ECHO RESPONSE WITH TIMESTAMP, they are shown in Figs. 2 and 3. Fig. 4 defines the value part of the message type Information Elements used in the PMF Protocol. The new proposed messages, that is PMFP ECHO REQUEST WITH TIMESTAMP and PMFP ECHO RESPONSE WITH TIMESTAMP are also depicted in Fig. 4. For example, the calculation of the UL delay follows these steps: 1) UE 3 and UPF 72 may be assumed to be time-synchronized; 2) UE 3 sends a PMFP ECHO REQUEST WITH TIMESTAMP message to UPF 72; 3) UPF 72 sends back PMFP ECHO RESPONSE WITH TIMESTAMP; 4) UE 3, based on the time difference between ECHO REQUEST and ECHO RESPONSE WITH TIMESTAMP messages, calculates estimated UL delay. For DL one-way delay estimation, UPF 72 can apply the same mechanism. One way PDV can be calculated, according to Fig. 1, except that in this case PMFP ECHO REQUEST WITH TIMESTAMP and PMFP ECHO RESPONSE WITH TIMESTAMP messages are used.

[0065] Behaviour of a UE 3 and UPF 72 in a load-balancing mode is given by Fig. 5, where RTT and RTT_PDV are used as KPIs. In that case, the load balancing will apply to both UE 3 and UPF 72. The UE, establishing two 3GPP accesses, may determine whether to stop (or reduce) or not the amount of traffic sent over one access among the two 3GPP accesses, based on a maximum measured value of a first parameter (for example, RTT, PLR, RTT_PDV, UL_delay, UL_PDV) and a (predetermined) threshold value of the first parameter. The UPF, establishing two 3GPP accesses, may determine whether to stop (or reduce) or not the amount of traffic sent over one access among the two 3GPP accesses, based on a maximum measured value of a first parameter and a (predetermined) threshold value of the first parameter.

[0066] In case the threshold values are provided for e.g. a one-way delay and one-way PDV, the evaluation is done separately for UL or DL and effects behaviour of UE 3 (see Fig. 6 for Load-Balancing mode) or UPF 72, respectively. The UE, establishing two 3GPP accesses, may determine whether to stop (or reduce) or not the amount of traffic sent over one access among the two 3GPP accesses, based on a maximum measured value of a first parameter (for example, RTT, PLR, RTT_PDV, UL_delay, UL_PDV) and a (predetermined) threshold value of the first parameter. The UE and the UPF may determine whether the maximum measured value of the first parameter may exceed the threshold value of the first parameter on both two 3GPP accesses.

[0067] In a case where the maximum measured value of the first parameter exceeds the threshold value of the first parameter on both accesses, the UE and the UPF may duplicate or switch the traffic of the SDF on both accesses. In a case where the maximum measured value of the first parameter does not exceed the threshold value of the first parameter on both accesses, the UE and the UPF may determine whether the maximum measured value of the first parameter may exceed the threshold value of the first parameter on one access among the two 3GPP access. In a case where the maximum measured value of the first parameter exceeds the threshold value of the first parameter on one access, the UE and the UPF may send the traffic of the SDF on the other access. In a case where the maximum measured value of the first parameter does not exceed the threshold value of the first parameter on one access, the UE and the UPF may send the traffic of the SDF only over the primary access indicated in the steering mode information field. In a case where the steering mode information is set to "Primary access is not provided", the UE and the UPF may select a primary access based on their implementation.

[0068] Fig. 7 depicts an example of redundant steering mode for RTT and RTT PDV while Fig. 8 depicts an example of redundant steering mode, when UL delay threshold and UL PDV are provided and used as determining KPI for traffic duplication or for traffic switching.

[0069] In all of the above examples, delay and PDV are considered together, but the evaluation can also use these parameters individually or combined with other parameters such as PLR (Packet Loss Rate). Some combinations may be restricted to particular steering modes.

[0070] < Fourth example of the First Aspect > 　　The fourth example of the First Aspect addresses enhanced URSP (eURSP) rules. The eURSP rules have new information that pertain to Dual Steer, i.e., they include the Dual Steer rules' information elements. Hence, one or more Dual Steer rules are added to be a part of an eURSP rule.

[0071] One possibility is to use eURSP rules in a way to indicate support for Dual Steer, in which case decoding on all Dual Steer information elements would depend if this field is set to yes or no. If the UE 3 does not support Dual Steer, all the Dual Steer information elements (for example, in Table 4) that follow are ignored.

[0072] Table 4, linked to Fig. 12, indicates DS information elements referring to the indication of dual steer, the precedence value of the indicated rule and traffic descriptor, e.g., description of applications to which the rule applies, data network indicated by the application and others. DS traffic descriptor field is of variable size and contains a variable number (at least one) of traffic descriptor components. Dual Steer rules may refer to how the traffic is distributed across two 3GPP accesses. There may be two ways these rules can be provided to the UE. For example, (1)When the UE is connected state, Dual Steer rule(s) are provided on its own, (2) Also, Dual Steer rules may be a part of eURSP rules, when the UE is registered, but in idle mode. The Fourth example of the first aspect may refer to the case when a Dual Steer rule or rules are added to a URSP rule. The URSP rule may become enhanced URSP (eURSP).

[0073] Table 4: Dual Steer (DS) information element(s)

[0074] Table 5, linked to Figs. 12 and 13, indicates DS route selection related information elements. The route selection descriptor indicates how the traffic should be routed, and is applicable for the indicated PDU session. DS route selection contents field is of variable size and contains a variable number (at least one) of route selection descriptor components. DS route selection related information element(s) may be added to the URSP rules.

[0075] Table 5: DS route selection related information element(s)

[0076] Please note that some of the fields in Table 4 and Table 5 can be inherited from a non-Dual Steer rule in the eURSP rule, for example, IP or non-IP descriptors, FQDN, PDU Session Type etc.

[0077] The eURSP rules may be also provided separately, for example, as a part of UE policy section management list information element, where UE policy part type is defined.

[0078] Fig. 11 and Fig. 12 depict an example of information elements(s) for the eURSP rules as a part of the UE policy. Table 5 indicates DS route selection related information elements.

[0079] eURSP rules would be, in this case, applicable only to UE 3(s) that support Dual Steer while legacy UE 3(s) would continue to use URSP rules.

[0080] < Fifth example of the First Aspect > 　　Fifth example of the First Aspect addresses the rules related to a discover and selection of a second network - PLMN / SNPN for Dual Steer. These rules are provided as a part of 3GPP Dual Access discovery and Selection Policy rules, here referred to as 3PDASP.

[0081] 3PDASP rule may consist of or include at least one of the following fields: 　　rule identifier, a unique number that identifies the 3PDASP rule; 　　one or more groups of criteria for applying a particular 3PDASP rule ; 　　indication on validity area where the second access network discovery and selection rule applies, such as 3GPP location, geo-location, zero or more time of day indication; 　　rule priority - a unique number indicating the priority of a particular 3PDASP rule; and 　　roaming - indicates if the rule is valid only when roaming.

[0082] Each set of selection criteria may contain at least one of the following fields: 　　criteria priority; 　　preferred roaming partner list PLMNs -indicating the preferred PLMNs for the second network selection when roaming; 　　preferred list of SNPNs - -indicating the preferred SNPNs for the second network selection; 　　PLMN exclusion list - list containing PLMNs that will not be attempted to register on as a second network; 　　SNPN exclusion list - list containing SNPNs that will not be attempted to register on as a second network; 　　preferred access technology - indicates if NR or any RAT may be considered when selecting a second access network; and 　　slice-based list of 3GPP networks and gNBs - the list containing a combination of PLMN-IDs, gNBs and S-NSSAIs, which should be considered for the second network selection. The S-NSSAI list indicates the list of S-NSSAI(s) that are supported by the indicated PLMNs and gNBs.

[0083] Fig. 16 to Fig. 36 depict possible encoding for the 3PDASP related information element(s).

[0084] < Second Aspect > 　　The second aspect addresses how to signal / provision the additional dual 3GPP access-related configuration rules or changes to the rules between the network and UE 3. Fig. 37 depicts the Dual Steer rule provisioning to the UE 3 either SM (Session Management) procedures or the MM (Mobility Management) procedures.

[0085] The Second aspect, in addition, addresses support for a network slice that acts as PNI-NPN NSSAI (i.e. PNI-NPN as a network slice), and can be combined with Dual Steer and other slice access conditions. The following examples refer to procedures for rule provisioning for PNI-NPN UEs 3, Dual Steer PDU Session establishment on S-NSSAI-1 acting as PNI-NPN and a case with a single AMF 70.

[0086] < First Example of the Second Aspect > 　　The First Example of the Second Aspect addresses network slice configuration as PNI-NPN and its provision to the UE 3 at registration within the Registration Accept message or at any time with the UE Configuration Update message. Specifically, this example refers to a case where there may be a Slice Access Group (SAG) information (SAG info) attached to such a network slice. The SAG info attached to the network slice may contain certain attributes which may define the conditions or the rules related to the use of such network slice by the UE.

[0087] For example, the SAG information may include at least one of the following attributes: 　　a PNI-NPN access attribute may define whether the network slice can be used as a NPI-NPN or not; 　　a service type attribute may define for what type of service this network slice may be used by the UE 3; 　　a time attribute may define the time window when the UE may ask for a service on the network slice; 　　a location attribute may define the location expressed in one or more Cell ID(s) or TA(s) where the UE 3 can use the network slice for a service; and 　　a device category attribute may define the type of devices that can use the network slice. The device category attribute may define the UE category that is allowed to use the network slice, 　　a multi-access / dual steer PDU attribute may define whether the UE can use the network slice for a multi-access / dual steer PDU Session.

[0088] The SAG info may be configured with a network slice granularity i.e. applicable per network slice or the SAG info can be per network slice and UE granularity, i.e. applicable per a network slice and per a UE at the same time when the SAG info is part of the UE subscription information.

[0089] In addition, the First Example of the Second Aspect addresses a mechanism how two USIMs are corelated in case where the UE 3 configures the DS using two USIMs. These two USIMs can have single subscription i.e. in the UDM the IMSIs of both USIM corresponds to same subscription of a user GPSI or ned to both USIMs.

[0090] The Fig. 38 describes the process in detail, where UE3 also requires subscription to access this slice.

[0091] Step 1. The operator may designate one or more S-NSSAIs (e.g. S-NSSAI-1) in the role of PNI-NPN with Slice Access Group (SAG) info so that a restricted set of users have access to this network slice acting as PNI-NPN and also a restricted set of services are allowed for the UEs on such network slices. The network slice can be a special type of PNI-NPN slice, for example, only available in certain area, time of day and / or catering for particular devices / applications / QoS profiles. In one example the SAG info and its attributes may be configured in the AMF or in the UDM by the network operator per network slice granularity (i.e. the AMF or the UDM may receive or obtain or store the SAG info or be configured by the SAG info.). In this case, the SAG info of the network slice is applicable for each UE to which this network slice is provided within the Allowed NSSAI. Alternatively, the operator may provide the SAG info with its attributes per UE granularity in which case the SAG info related to a network slice is part of the UE subscription information in the UDM and based on the attributes of the SAG there could be different rules of access to the network slice for different UEs.

[0092] In addition, the UDM 75 may have a subscriber data that indicates an associated another subscriber ID (identifier). The associated another subscriber ID may be called as other notations or expressions. The following bullets list examples for another notations: 　　Linked user ID; 　　Linked user identifier; 　　Linked USIM; 　　Linked Permanent Equipment Identifier (PEI); 　　Linked IMEI; 　　Linked IMEISV; 　　Linked Generic Public Subscription Identifier (GPSI); 　　Linked MSISDN; 　　Associated another subscriber data; 　　Another subscriber data; 　　Associated Another user ID; and 　　Associated another user identifier.

[0093] The associated another subscriber ID may be maintained in the UDM 75 per subscriber basis, per S-NSSAI basis, per DNN basis or per S-NSSAI and DNN basis with associated PDU session information and UE capability information for DS with two USIM.

[0094] In case the UE 3 establishes the PDU session, the UDM 75 receives a SUPI, an associated SMF information, an associated UPF information, S-NSSAI, DNN and PDU Session ID. The associated SMF information may be an SMF name (FQDN) or IP address (IPv4, IPv6 or IPv4V6 address) of the PSA (PDU Session Anchor) SMF. The associated UPF information may be an UPF name (FQDN) or IP address (IPv4, IPv6 or IPv4V6 address) of the PSA (PDU Session Anchor) UPF. The UDM 75 obtains the PDU Session related data by subscribing to the SMF service. With this subscribing, the SMF 71 notifies the SMF information, the associated UPF information, S-NSSAI, DNN, PDU Session ID to the UDM 75. The UE capability information for DS with two USIM is received from the AMF 70 when the UE 3 performs the registration procedure. In one example the USIM may be configured in an Elementary File (EF) whether the USIM is primary USIM or secondary USIM (e.g., in the EF, there may be information indicating whether the USIM is primary USIM or secondary USIM. The EF in the USIM may include information indicating whether the USIM is primary USIM or secondary USIM. The EF in the USIM may indicate whether the USIM is primary USIM or secondary USIM). If the USIM is primary USIM then the UE will perform registration procedure first (e.g., the UE may perform registration procedure first over the primary USIM) then the UE performs registration procedure over secondary USIM if both primary and secondary USIMs are inserted in the device. In one example, the USIM may also contains an EF indicating whether the USIM is Dual Steer with Dual USIM capable (DSDS). If the USIM is DSDS configured and the service is enabled then the UE will perform registration procedure over primary and secondary USIMs at the same time. In one example the EF is USIM SST and one byte is reserved for whether DSDS capable is enabled or not. If the service is enabled then the UE performs dual registration procedure.

[0095] Step 2. The UE 3 sends a Registration Request message to an AMF 70 including at least one of User ID, Requested NSSAI, Dual 3GPP access / Dual steer support information and support information for PNI-NPN as an S-NSSAI (support for PNI-NPN as an S-NSSAI). The following bullets explain each parameter in detail. 　　UE ID: UE ID (e.g., the UE ID may be expressed as User ID, User Identity etc.) may be a 5G-GUTI, SUCI or SUPI or other identity supported by 3GPP specification. 　　Requested NSSAI may indicate one or more S-NSSAI(s) that the UE 3 request to use. For example, S-NSSAI-1 is included in the Requested NSSAI. 　　Dual 3GPP access support information may indicate whether the UE 3 is Dual 3GPP access / DS capable or not. (Dual 3GPP access support information may indicate whether the UE 3 supports Dual 3GPP access or not). The Dual 3GPP access(es) may be expressed as Dual Steer. 　　support information for PNI-NPN as an S-NSSAI (in other words, first support information) may indicate whether the UE 3 supports the configuration for a network slice configured as PNI-NPN or not. The support information for PNI-NPN as an S-NSSAI may indicate that the UE 3 supports the configuration for a network slice configured as PNI-NPN. The support information for PNI-NPN as an S-NSSAI may be expressed as Support for PNI-NPN as an S-NSSAI. 　　UE capability information for DS with two USIM (comprising two UEs). This capability information indicates that UE 3 is capable to establish two PDU Sessions with two USIMs and configures the IP connectivity service using two PDU Sessions that span to two USIMs. In one example, the UE capability information for DS with two USIMs may be indicated in the 5GMM capability. The two PDU sessions are established for the same DNN or same S-NSSAI and DNN. 　　UE capability information for DS (single USIM) that supports simultaneous transmission, i.e., has dual radio capability. This capability information indicates that UE 3 with a single USIM is capable to establish a single DS PDU session or two PDU Sessions. In one example, the UE capability information for DS with single USIM may be indicated in the 5GMM capability. In case of two PDU sessions, they are established for the same DNN or same S-NSSAI and DNN.

[0096] Step 3. When the AMF 70 retrieves or receives the UE subscription information from the UDM 75, the AMF 70 may also include in a first message (for example, Nudm_SDM_Get_Request message) to the UDM 75 the indication(s) for PNI-NPN as a S-NSSAI and the indication for Dual 3GPP access support received from the UE 3 and the UE capability information for DS with two USIM received from the UE 3. For example, AMF 70 may send, to the core network node (for example UDM 75), the first information and the Dual 3GPP access support information. For example, AMF 70 may send, to the core network node (for example UDM 75), the UE ID and the Requested NSSAI which includes S-NSSAI(s) (e.g., S-NSSAI-1). The above parameter(s) which is sent from the AMF 70 to the UDM 75 may be included in the Nudm_SDM_Get_Request message.

[0097] Step 4. The UDM 75 may check or determine whether the UE 3 has a subscription for PNI-NPN and whether the UE 3 indicated support for PNI-NPN as an S-NSSAI. If yes (e.g., in a case where the UE 3 has the subscription for PNI-NPN and the UE 3 indicated the support for PNI-NPN), the UE 3 may be assigned to the PNI-NPN slice (e.g. S-NSSAI-1) and a related SAG info. For example, if the UE 3 supports PNI-NPN as S-NSSAI then UE 3 may be registered to the PNI-NPN slice (e.g. S-NSSAI-1) and receive SAG information. The SAG (Slice Access Group) info may define at least one the condition(s) and the at least one rule(s) for use of the network slice by the UE. The SAG info of the network slice may contain at least one attribute(s) which define the at least one conditions or the at least one rules related to the use of such network slice by the UE. For example, a PNI-NPN access attribute may define whether the network slice can be used as a NPI-NPN or not. A service type attribute may define for what type of service this network slice may be used by the UE. A time attribute may define the time window when the UE may ask for a service on the network slice. A location attribute may define the location expressed in one or more Cell ID(s) or TA(s) where the UE can use the network slice for a service. A device category attribute may define the type of devices that can use the network slice, a device category attribute may define the UE category that is allowed to use the network slice, a multi-access / dual-steer PDU attribute may define whether the UE can use the network slice for a multi-access / dual-steer PDU Session. For example, in a case where the UE 3 has the subscription for PNI-NPN and the UE 3 indicated the support for PNI-NPN, the PNI-NPN slice (e.g. S-NSSAI-1) and the SAG info related to the PNI-NPN slice may be assigned to the UE 3. For example, in a case where the UE 3 has the subscription for PNI-NPN and the UE 3 indicated the support for PNI-NPN, the UDM 75 may assign the PNI-NPN slice (e.g. S-NSSAI-1) and the SAG info related to the PNI-NPN slice to the UE 3.

[0098] Step 5. If the UDM 75 concludes that the UE 3 is entitled to access the PNI-NPN which is configured as a S-NSSAI, the UDM 75 may return back to the AMF 70 a second message (e.g. Nudm_SDM_Get Response message) in which the UDM 75 includes the network slice in the role of PNI-NPN (for example S-NSSAI-1) and the SAG info. For example, if the UDM 75 determines that the UE 3 is capable of access to the PNI-NPN which is configured as a S-NSSAI, then UDM 75 may send, to the AMF 70, the network slice in the role of PNI-NPN (for example S-NSSAI-1) and the SAG info. The UDM 75 may conclude that the UE 3 is entitled to access the PNI-NPN based on the information for the UE 3 stored in the UDM 75. The UDM 75 may conclude that the UE 3 is entitled to access the PNI-NPN based on subscription information for the UE 3 stored in the UDM 75. The UDM 75 may conclude that the UE 3 is entitled to access the PNI-NPN in a case where the UDM 75 receives information indicating that the UE 3 is entitled to access the PNI-NPN. For example, the UDM 75 may send, to the AMF 70, the UE ID, S-NSSAI-1 in the role of PNI-NPN (e.g., S-NSSAI-1 which identifies a network slice in the role of PNI-NPN), the SAG info (e.g., the SAG info related to S-NSSAI-1).

[0099] In addition, if the UDM 75 has received the UE capability information for DS with two USIM in Step 3 (for example, Nudm_SDM_Get_Request message), the UDM 75 may provide at least one of the following DS with two USIM related information to the AMF 70. 　　DS with two USIM allowed - This indication indicates that the UE 3 is allowed to configure DS using two USIMs. 　　Associated another subscriber ID - This indication indicates that an associated subscriber ID that may be used to configure the DS using two USIMs. 　　Associated SMF information - The associated SMF information indicates that an SMF information that is used for the established PDU Session where the DS using two USIMs possible. 　　Associated UPF information - The associated UPF information indicates that a UPF information that is used for the established PDU Session where the DS using two USIMs possible. 　　Associated S-NSSAI - The associated S-NSSAI indicates that an S-NSSAI that is used for the established PDU Session where the DS using two USIMs possible. 　　Associated DNN - The associated DNN indicates that a DNN that is used for the established PDU Session where the DS using two USIMs possible. 　　Associated PDU Session ID - The associated PDU Session ID indicates that an PDU Session ID that is used for the established PDU Session where the DS using two USIMs possible. 　　Associated Connection ID - The associated Connection ID is a unique identifier of an IP connectivity among PLMNs where the DS using two USIMs possible. The associated Connection ID may consist of or include PLMN ID and unique value of connection identifier within the PLMN. The associated Connection ID is assigned to a PDU Session that is subject for the DS using two USIMs. If two PDU Session are established to provide a DS using two USIMs, the same associated Connection ID is assigned to two PDU Session. The associated Connection ID may be used to issue single charging ticket for the DS using two USIMs by the CHF and charging system. The associated Connection ID is provided by the UDM 75 together with the Associated PDU Session ID. 　　Primary USIM (e.g. primary SUPI) and secondary USIM (e.g. secondary SUPI) - The Primary USIM and secondary USIM indicate a priority in two SUPIs.

[0100] Step 6. The AMF 70 triggers Policy association establishment request as part of the registration procedure. If the UE 3 indicates support for Dual 3GPP access (e.g., in a case where the UE 3 sends the Dual 3GPP access support information, or in a case where the UE 3 sends the Dual 3GPP access support information which indicates that the UE 3 supports the Dual 3GPP access), the AMF 70 may include in the UE Policy association establishment request to the PCF 73 an indication for Dual 3GPP access support (e.g., the Dual 3GPP access support information). For example, if the AMF 70 receives, from the UE 3, the Dual 3GPP access support information, the AMF 70 may send, to the PCF 73, the Dual 3GPP access support information and the UE ID.

[0101] Step 7. If the AMF 70 indicates the Dual 3GPP access support of the UE 3, the PCF 73 may provide to the AMF 70 the eURSP rules (the enhanced URSP(UE Route Selection. Policy) rules) during the UE Policy establishment procedure or with the Namf_Communication_N1N2MessageTransfer message as part of the UE Policy update procedure if the UE capability for Dual 3GPP access is retrieved by the PCF 73 from the UDM 75. For example, if the AMF 70 receives, from the UE 3, the Dual 3GPP access support information and the AMF 70 sends, to the PCF 73, the Dual 3GPP access support information, the PCF 73 may send, to the AMF 70, at least eURSP rule(s). For example, PCF 73 may generate the eURSP rule(s). The PCF 73 may send the UE ID and the eURSP rule(s) related to the UE ID (e.g., the eURSP rule(s) for the UE 3) to the AMF 70. The eURSP rules may be expressed as eURSP rule(s), eURSP rule etc.

[0102] Step 8. The AMF 70 may trigger the UE Configuration Update Command to the UE 3 and the AMF 70 may include the eURSP rules as part of the UE policy update in the UE 3. If the AMF 70 provides a network slice in addition to the Allowed NSSAI within the UE Configuration Update Command message, the AMF 70 may also provide the related SAG info, if available. For example, AMF 70 may send, to the UE 3, the at least eURSP rule. For example, AMF 70 may send, to the UE 3, a network slice in addition to the Allowed NSSAI. For example, AMF 70 may send, to the UE 3, SAG info. The SAG info, sent to the UE 3, may be related to the at least one eURSP rule or the network slice. For example, the AMF 70 may send, to the UE 3, the eURSP rules, Allowed NSSAI, SAG info related to the Allowed NSSAI (e.g., SAG info related to network slice(s) or S-NSSAI(s) in the Allowed NSSAI). The above parameter(s) which is sent from the AMF 70 to the UE 3 may be included in the UE Configuration Update Command message.

[0103] Step 9. If the UE 3 indicates support for PNI-NPN as S-NSSAI, the AMF 70 may provide the S-NSSAI-1 as PNI-NPN to the UE 3. For example, if the UE 3 supports for PNI-NPN as S-NSSAI, the AMF 70 may determine that the AMF 70 sends the S-NSSAI-1 as PNI-NPN to the UE 3.

[0104] Step 10. The AMF 70 may send the Registration Accept message to the UE 3 including at least one of UE ID, Allowed NSSAI, PNI-NPN, SAG info and the DS with two USIM . For example, the AMF 70 may send at least the S-NSSAI-1 as PNI-NPN to the UE 3. The DS with two USIM related information may be sent from the AMF 70 to the UE 3 only if the UE 3 sends the UE capability information for DS with two USIM to the AMF 70 in Step 2.

[0105] The following bullets may explain each parameter in detail. 　　UE ID: UE ID (e.g., the UE ID may be expressed as User ID or User Identity) may be a 5G-GUTI. 　　Allowed NSSAI indicates one or more S-NSSAI(s) that the UE 3 is allowed to use. For example, S-NSSAI-1 is included in the Allowed NSSAI. 　　PNI-NPN - a network slice which is configured as PNI-NPN. This network slice can be provided to the UE 3 as a separate parameter within the Registration Accept message for which the network may also provide a SAG info. The UE 3 may consider such PNI-NPN network slice as allowed network slice within the conditions and rules set by the SAG info. Alternatively, this PNI-NPN network slice may be provided as part of the Allowed NSSAI and again with a potential SAG info to set the conditions and the rules for it usage by the UE 3. The PNI-NPN which is set to S-NSSAI-1 may indicate that the network slice identified by S-NSSAI-1 is configured as PNI-NPN. 　　SAG info - The SAG (Slice Access Group) info defines the conditions and the rules for use of the network slice by the UE. The SAG info of the network slice may contain certain attributes which define the conditions or the rules related to the use of such network slice by the UE. For example, a PNI-NPN access attribute may define whether the network slice can be used as a NPI-NPN or not (e.g., in a case where the above "PNI-NPN" parameter is set to S-NSSAI-1, the PNI-NPN access attribute may define that the network slice identified by S-NSSAI-1 can be used as the PNI-NPN); a service type attribute may define for what type of service this network slice may be used by the UE; a time attribute may define the time window when the UE may ask for a service on the network slice; a location attribute may define the location expressed in one or more Cell ID(s) or TA(s) where the UE can use the network slice for a service; a device category attribute may define the type of devices that can use the network slice, a device category attribute may define the UE category that is allowed to use the network slice, a multi-access / dual-steer PDU attribute may define whether the UE can use the network slice for a multi-access / dual-steer PDU Session. 　　The DS with two USIM related information - The DS with two USIM related information may be sent to the UE 3 per UE basis, per S-NSSAI basis for S-NSSAIs in the Allowed NSSAI, per S-NSSAI basis for S-NSSAIs in the Configured NSSAI, per DNN basis or per DNN / S-NSSAI combination basis. The DS with two USIM related information may consist of the following information. 　　DS with two USIM allowed. 　　Associated another subscriber ID. 　　Associated SGW information. 　　Associated UPF information. 　　Associated S-NSSAI. 　　Associated DNN. 　　Associated PDU Session ID. 　　Associated Connection ID. 　　Primary USIM (e.g. Primary SUPI) and Secondary USIM (e.g. secondary SUPI).

[0106] Step 11. The UE 3 may receive the Registration Accept message from the AMF 70. When the UE 3 is assigned by a network slice (e.g. S-NSSAI-1) in the role of PNI-NPN and the SAG info is also included, the UE 3 may request a service on that network slice (e.g. S-NSSAI-1) according to the conditions and the rules set by the attributes in the SAG info as per the SAG attribute description in step 10. For example, the UE 3 may request single PDU session establishment or Multi-Access / Dual-Steer (MA / Dual Steer) PDU session establishment relating to the network slice (e.g. S-NSSAI-1) based on at least one of the eURSP rules or the SAG information. For example, in a case where the service that the UE 3 wants to trigger matches the service defined by the service type attribute in the SAG info for S-NSSAI-1, the UE 3 may request the service on S-NSSAI-1 (or the network slice identified by S-NSSAI-1) based on the eURSP rules or may request single PDU session establishment or MA / Dual Steer PDU session establishment for S-NSSAI-1 (or the network slice identified by S-NSSAI-1) based on the eURSP rules. For example, in a case where the current time matches the time defined by the time attribute in the SAG info for S-NSSAI-1, the UE 3 may request the service on S-NSSAI-1 (or the network slice identified by S-NSSAI-1) based on the eURSP rules or may request single PDU session establishment or MA / Dual Steer PDU session establishment for S-NSSAI-1 (or the network slice identified by S-NSSAI-1) based on the eURSP rules. For example, in a case where the UE 3's location matches the location defined by the location attribute in the SAG info for S-NSSAI-1, the UE 3 may request the service on S-NSSAI-1 (or the network slice identified by S-NSSAI-1) based on the eURSP rules or may request single PDU session establishment or MA / Dual Steer PDU session establishment for S-NSSAI-1 (or the network slice identified by S-NSSAI-1) based on the eURSP rules. For example, in a case where the UE 3's device category (e.g., the UE category for the UE 3) matches the type of device or the UE category defined by the device category attribute in the SAG info for S-NSSAI-1, the UE 3 may request the service on S-NSSAI-1 (or the network slice identified by S-NSSAI-1) based on the eURSP rules or may request single PDU session establishment or MA / Dual Steer PDU session establishment for S-NSSAI-1 (or the network slice identified by S-NSSAI-1) based on the eURSP rules. The MA PDU session may be expressed as Dual Steer PDU session. The MA PDU session establishment may be expressed as Dual Steer PDU session establishment. For example, in a case where the multi-access / dual-steer PDU attribute indicates that the UE 3 can use the network slice identified by S-NSSAI-1 or can use S-NSSAI-1, the UE 3 may request the service on S-NSSAI-1 (or the network slice identified by S-NSSAI-1) based on the eURSP rules or may request single PDU session establishment or MA / Dual Steer PDU session establishment for S-NSSAI-1 (or the network slice identified by S-NSSAI-1) based on the eURSP rules.

[0107] In case the UE 3 receives the DS with two USIM related information, the UE 3 recognizes that the DS with two USIM is available. The UE 3 refers to the PDU Session activities (Established PDU Session) with another USIM and establishes another PDU Session with the current USIM to configure the Dual Steer with two USIMs. A eURSP rule maps application to a primary USIM or a secondary USIM or both. In case the application is map to both and the AMF indicates that the UE is enabled for dual USIM Dual steer (DSDS) then the UE establishes one PDU session on each USIM for a S-NSSAI and S-NSSAI + DNN.

[0108] < Variant 1 of First example of the Second Aspect > 　　When the UE 3 is multi-SIM capable and the UE 3 has received the DS with two USIM related information and a PDU Session is newly established or released in another USIM, the UDM 75 sends the notification to the AMF 70 for notifying a new the DS with two USIM related information. Then, the AMF sends the UE Configuration Update (UCU) message to the UE 3 for updating the DS with two USIM related information in the UE 3. In one example, the primary USIM and secondary USIM configuration may also be sent from in the UCU message.

[0109] < Second Example of the Second Aspect > 　　The detailed processes of the Second example of the Second Aspect are described below with the reference to Fig. 39.

[0110] Step 1. The UE 3 may be registered with HPLMN, and configured for S-NSSAI-11 that acts as PNI-NPN. The eURSP rules may be provided to the UE 3. For example, a network slice identified by S-NSSAI-11 may be included in or may be operated in PNI-NPN.

[0111] Step 2. An application in the UE 3 may trigger the PDU Session establishment. Based on the eURSP rules, the UE 3 may generate Dual Steer PDU session establishment request on S-NSSAI-11.

[0112] Step 3. The UE 3 may send PDU session establishment request to the AMF 70, indicating support for PNI-NPN S-NSSAIs, requesting S-NSSAI-11, UE capability information for DS with two USIM, DS with two USIM requested and Associated Connection ID. The Associated Connection ID may be sent by the UE 3 in case where the UE 3 has another PDU Session established with another USIM and the DS with two USIM requested. As another PDU Session with another USIM has the same value for the Associated Connection ID, the 5GC and charging system can corelate two PDU Sessions, one that has been established with another USIM and the PDU Session being established with this procedure, so that single charging ticket can be issued for two PDU Sessions. For example, single charging ticket can be issued by combining two CDRs for each PDU Sessions. For example, UE 3 may perform PDU Session establishment. For example, UE 3 may perform PDU Session establishment based on the eURSP rule(s). For example, UE 3 may send, to the AMF 70, first support information indicating that the UE 3 may support for PNI-NPN S-NSSAIs and requesting S-NSSAI-11. Dual Steer_PDU Session type may be included in the PDU session establishment request. Dual Steer_PDU Session type may define IP or Ethernet PDU session type. Dual Steer PDU session may be a PDU connectivity service, which can use one 3GPP access network at a time, or simultaneously two 3GPP access networks.

[0113] For example, the UE 3 may send, to the AMF 70, UE ID, support information for PNI-NPN as an S-NSSAI, PNI-NPN which is set to S-NSSAI-11. The support information for PNI-NPN as an S-NSSAI may be expressed as support for PNI-NPN S-NSSAIs or S-NSSAI as PNI-NPN support. The PNI-NPN which is set to S-NSSAI-11 may indicate that the network slice identified by S-NSSAI-11 is configured as PNI-NPN.

[0114] Step 4. In this step, additional, slice specific authentication may be invoked by AMF 70. For example, the AMF 70 may authenticate the network slice requested by the UE 3.

[0115] Step 5. AMF 70 may pass the UE 3's request details to UDM 75 by sending Nudm_SDM_Get_Request, which may include UE ID (e.g., SUPI), support for PNI-NPN S-NSSAIs, requested S-NSSAI-11 that acts as PNI-NPN, UE capability information for DS with two USIM and Associated Connection ID. For example, the AMF 70 send, to the UDM 75, the UE ID (e.g., SUPI), first support information indicating that the UE 3 may support for PNI-NPN S-NSSAIs, and the requested S-NSSAI-11 that acts as PNI-NPN. For example, the AMF 70 send, to the UDM 75, the UE ID (e.g., SUPI), support for PNI-NPN S-NSSAIs, and PNI-NPN which is set to S-NSSAI-11. The PNI-NPN which is set to S-NSSAI-11 may be expressed as the requested S-NSSAI-11 that acts as PNI-NPN, PNI_NPN which is set to S-NSSAI-11 etc.

[0116] Step 6. UDM 75 may check the UE subscription and may verify the UE 3's subscription for S-NSSAI-11 as PNI-NPN slice. For example, the UDM 75 may verify that the UE 3 may support for the S-NSSAI-11 as PNI-NPN slice. If the UDM 75 does not receives the Associated Connection ID in Nudm_SDM_Get_Request message in Step 5, the UDM 75 may assign new Associated Connection ID.

[0117] Step 7. UDM 75 may send the response to AMF 70, e.g. using Nudm_SDM_Get_Response, indicating S-NSSAI-11 to be used for access to PNI-NPN services. For example, the UDM 75 may send the response, to the AMF 70, indicating that S-NSSAI-11 may be used for access to PNI-NPN services. For example, the UDM 75 may send, to the AMF 70, the UE ID and PNI-NPN which is set to S-NSSAI-11.

[0118] In addition, the UDM 75 may send the response to AMF 70, e.g. using Nudm_SDM_Get_Response, including the DS with two USIM related information. Refer to the Step 5 in the First Example of the Second Aspect for details of the DS with two USIM related information.

[0119] Step 8. In this step, AMF 70 may perform SMF selection. SMF 71 may support S-NSSAI(s) acting as PNI-NPN as well as Dual Steer. For example, the AMF 70 may select the SMF 71 which supports S-NSSAI(s) acting as PNI-NPN as well as Dual Steer. For example, the AMF 70 may select the SMF 71 which supports S-NSSAI-11 as well as Dual Steer. For example, the AMF 70 may store information for selecting the SMF 71 (e.g., information indicating which SMF(s) supports S-NSSAI(s) which acts as PNI-NPN, information indicating which SMF(s) supports network slice(s) which acts as PNI-NPN, information indicating which SMF(s) supports DS).

[0120] In case that the AMF 70 receives the DS with two USIM related information from the UDM 75 in Step 7, the AMF 70 takes the DS with two USIM related information into account for the SMF selection. For example, the AMF 70 receives the requesting S-NSSAI-11 from the UE 3 in Step 3 and the AMF 70 receives the DS with two USIM related information from the UDM 75 including the DS with two USIM related information for the S-NSSAI-11 in Step 7, the AMF 70 may select an SMF in the Associated SMF information for the S-NSSAI-11 in the DS with two USIM related information.

[0121] Step 9. AMF 70 may send NsmfPDU_Session_CreateSMContextRequest to the selected SMF (e.g., SMF 71), indicating support for S-NSSAI(s) acting as PNI-NPN, indicating S-NSSAI-11 and Dual Steer PDU Request indication as well as indication of two access networks. For example, the AMF 70 may send, to the SMF 71, the S-NSSAI as PNI-NPN support, PNI-NPN which is set to S-NSSAI-11, Dual-steer PDU Request indication and indication of two 3GPP access network RATs, e.g., NR-NR, NR-LTE. The Dual 3GPP PDU Request indication may indicate that MA / Dual Steer PDU Session is requested, although the session may be initially established using only one 3GPP access network, as depicted in this figure.

[0122] In addition, the AMF 70 may send NsmfPDU_Session_CreateSMContextRequest to the selected SMF (e.g., SMF 71), including the DS with two USIM requested that is received from the UE 3 in Step 3, the DS with two USIM related information maintained in the AMF 70 and the Associated Connection ID.

[0123] Step 10. SMF 71 may send NsmfPDU_Session_CreateSMContextResponse for confirming S-NSSAI support for PNI-NPN, S-NSSAI-11 and the Associated Connection ID. For example, the SMF 71 may send to the AMF 70, the S-NSSAI as PNI-NPN support, and PNI-NPN which is set to S-NSSAI-11. The SMF 71 may send the Associated Connection ID in a case where the SMF 71 is in charge of issuing the Associated Connection ID.

[0124] Step 11. SMF 71 may initiate PCF selection and policy association to retrieve Dual Steer control information, according to the parameters from PCF 73. The example of policy control parameters related to the Dual Steer rule is given in Table 1. The Dual Steer control information may be or may be based on at least one of parameters in Table 1.

[0125] In addition, if the SMF 71 receives the DS with two USIM related information from the AMF 70 in Step 9, The SMF 71 performs the Home-routed Roaming - UE registered to different PLMNs procedure as described in section 4.22.2.2.2 in NPL 4 with the following replacements if the DS with two USIM requested is included in Step 9. 　　Non-3GPP access is replaced with another 3GPP access. 　　Non-3GPP path is replaced with another 3GPP path. 　　MA PDU Request is replaced with the DS with two USIM requested.

[0126] Step 12. The SMF 71 may perform UPF selection to select a UPF 72 as the anchor of this PDU Session, supporting PNI-NPN S-NSSAI and Dual Steer. For example, the SMF 71 may select the UPF 72 which supports S-NSSAI(s) acting as PNI-NPN as well as Dual Steer. For example, the SMF 71 may select the UPF 72 which supports S-NSSAI-11 as well as Dual Steer. For example, the SMF 71 may store information for selecting the UPF 72 (e.g., information indicating which UPF(s) supports S-NSSAI(s) which acts as PNI-NPN, information indicating which UPF(s) supports network slice(s) which acts as PNI-NPN, information indicating which UPF(s) supports DS).

[0127] Step 13. SMF 71 may derive the Dual Steer rule(s) based on PCF Dual Steer policy control. The Dual Steer rule(s) may be used for controlling traffic steering, switching and splitting in the uplink direction and N4 Dual Steer rules (e.g., the above Dual Steer rule(s)) may be sent to UPF 72 for controlling the traffic steering, switching and splitting in the downlink direction. The SMF 71 may send the Dual Steer rule(s) to the UPF 72.

[0128] Step 14. The Dual Steer rule(s) may be sent to AMF 70 in a container, using NamfN1N2_MessageTransfer. The message to AMF 70 may include UE ID, Dual Steer PDU session accept indication, which may indicate to AMF 70 that this is a Dual Steer PDU session and the Associated Connection ID. AMF 70 may mark this PDU session as Dual Steer PDU session based on the received indication. Also, for example, the SMF 71 may send the Dual Steer rule(s) to the AMF 70.

[0129] Step 15. AMF 70 may send the PDU session establishment accept message to the UE 3, which may include container with the Dual Steer rule(s), indication of granted S-NSSAI-11 and Associated Connection ID. For example, the AMF 70 may send, to the UE 3, the Dual Steer rule(s) and the PNI-NPN which is set to S-NSSAI-11. N4 Dual Steer Rules may be provided to UPF 72. The UE 3 may use the Dual Steer rules for MA / Dual Steer PDU Session. The UE 3 may use the Dual Steer rules for steering traffic on MA PDU Session. The UE 3 may use the Dual Steer rules for controlling traffic steering, switching and splitting. In one example, the UE first establishes a PDU session over the first primary USIM. If a NF (e.g. SMF or UDM) indicates either by an explicit IE to the UE in any existing NAS message or in a new NAS message or in URSP rules (or eURSP rules) to establish the second PDU session over the second USIM then the UE establishes a second PDU session for the DNN or the S-NSSAI and DNN of the first PDU session. The application can transfer data on both PDU session. In one example, a static or dynamic IP address is assigned to the DNN or S-NSSAI and DNN in the network and the UE. The UE starts transmitting data over DRB of the two PDU sessions simultaneously or sequentially as indicated to the UE in during the two PDU session establishment procedure in one of the NAS messages involved in the PDU session establishment or through a URSP rule (or eURSP rules).

[0130] < Variant 1 of Second example of the Second Aspect > 　　In case the SMF 71 in charge of issuing the Associated Connection ID for the PDU Session in Step 10, the SMF 71 invokes the Nudm_UECM_Registration service to the UDM 75 including the Associated Connection ID. With this service invocation, the UDM 75 can maintain the PDU Session with the assigned Associated Connection ID.

[0131] < Third Example of the Second Aspect > 　　The Third Example of the Second Aspect addresses the process of Dual Steer PDU Session Establishment by PNI-NPN UE 3(s) using S-NSSAIs acting as PNI-NPN. The Fig. 40 describes the process in details.

[0132] Step 1. The UE 3 may be registered with HPLMN, and configured for S-NSSAI-1 that acts as PNI-NPN. The eURSP rules and the SAG info related to the PNI-NPN network slice access may be provided to the UE 3 during the registration procedure. For example, a network slice identified by S-NSSAI-1 may be included in or may be operated in PNI-NPN.

[0133] Step 2. An application in the UE 3 may trigger the PDU Session establishment. Based on the eURSP rules, the UE 3 may create or generate Dual Steer PDU session establishment request on S-NSSAI-1.

[0134] Step 3. The UE 3 may send PDU session establishment request to the AMF 70, indicating support for support for PNI-NPN as S-NSSAI and requesting S-NSSAI-1. The UE 3 also includes the SAG info if available in the UE 3. For example, UE 3 may perform PDU Session establishment. For example, UE 3 may perform PDU Session establishment based on the eURSP rule(s). For example, UE 3 may send, to the AMF 70, first support information indicating that the UE 3 may support for PNI-NPN S-NSSAIs and requesting S-NSSAI-1 and the SAG information indicating a condition or a rule related to the use of the S-NSSAI by the UE. The step 3 in Fig. 40 may be same to step 3 in Fig. 39 with replacement S-NSSAI-11 with S-NSSAI-1 and inclusion of the SAG info.

[0135] Step 4. As the PDU Session request by the UE 3 may be for a network slice, e.g SNSSAI-1, designated as PNI-NPN, the AMF 70 may trigger additional slice specific authentication. The additional slice specific authentication can be with an entity within the 3GPP system or with an entity external to the 3GPP system, as per NPL 4.

[0136] Step 5. The AMF 70 may trigger the UE subscription information retrieval from the UDM 75. The AMF 70 may send Nudm_SDM_Get_Request message to the UDM 75 in which the AMF 70 may include the UE ID (e.g. SUPI), support for PNI-NPN as S-NSSAI (e.g. first information indicating that the UE 3 may support for PNI-NPN as S-NSSAI), the requested S-NSSAI-1 that acts as PNI-NPN and the related SAG info if available.

[0137] Step 6. The UDM 75 may check the UE subscription and may verify the UE 3's subscription for S-NSSAI-1 as PNI-NPN slice and also verify the SAG info if provided. For example, the UDM 75 may verify that the UE 3 may support for the S-NSSAI-11 as PNI-NPN slice and verify the SAG info.

[0138] Step 7. If the UE 3 is entitled for access to the S-NSSAI-1 which is designated as PNI-NPN, the UDM 75 may send the response to AMF 70, using Nudm_SDM_Get_Response, for confirming S-NSSAI-1 to be used for access to PNI-NPN services. For example, if UDM 75 determines that the UE 3 may be capable of access to the PNI-NPN which is configured as a S-NSSAI, then UDM 75 may send, to the AMF 70, the response indicating S-NSSAI-1 to be used for access to PNI-NPN services. For example, in a case where the UDM 75 determines that the service that the UE 3 wants to trigger matches the service defined by the service type attribute in the SAG info for S-NSSAI-1, the UDM 75 may perform the process(es) in step 7. For example, in a case where the UDM 75 determines that the current time matches the time defined by the time attribute in the SAG info for S-NSSAI-1, the UDM 75 may perform the process(es) in step 7. For example, in a case where the UDM 75 determines that the UE 3's location matches the location defined by the location attribute in the SAG info for S-NSSAI-1, the UDM 75 may perform the process(es) in step 7. For example, in a case where the UDM 75 determines that the UE 3's device category (e.g., the UE category for the UE 3) matches the type of device or the UE category defined by the device category attribute in the SAG info for S-NSSAI-1, the UDM 75 may perform the process(es) in step 7. For example, in a case where the UDM 75 determines that the multi-access / dual-steer PDU attribute indicates that the UE 3 can use the network slice identified by S-NSSAI-1 or can use S-NSSAI-1, the UDM 75 may perform the process(es) in step 7.

[0139] Step 8. If the UE 3 indicates support for PNI-NPN as S-NSSAI, the AMF 70 may select a SMF 71 supporting the PNI-NPN as S-NSSAI and also supporting the Dual Steer functionality. For example, the AMF 70 may select the SMF 71 which supports S-NSSAI(s) acting as PNI-NPN as well as Dual Steer. For example, the AMF 70 may select the SMF 71 which supports S-NSSAI-1 as well as Dual Steer. For example, the AMF 70 may store information for selecting the SMF 71 (e.g., information indicating which SMF(s) supports S-NSSAI(s) which acts as PNI-NPN, information indicating which SMF(s) supports network slice(s) which acts as PNI-NPN, information indicating which SMF(s) supports DS).

[0140] Step 9. The AMF 70 may send NsmfPDU_Session_CreateSMContextRequest to the selected SMF (e.g., the SMF 71), indicating support for PNI-NPN as S-NSSAI, indicating S-NSSAI-1 and Dual Steer PDU Request indication. For example, the AMF 70 may send information or ID indicating the selected SMF 71.

[0141] Step 10. SMF 71 may return NsmfPDU_Session_CreateSMContextResponse.

[0142] Step 11. SMF 71 may initiate PCF selection and policy association to retrieve Dual Steer control information from PCF 73 and the SMF 71 may indicate the support for PNI-NPN as an S-NSSAI to the PCF 73.

[0143] Step 12. The SMF 71 may perform UPF selection to select a UPF 72 as the anchor of this PDU Session, supporting PNI-NPN S-NSSAI and Dual Steer. For example, the SMF 71 may select the UPF 72 which supports S-NSSAI(s) acting as PNI-NPN as well as Dual Steer. For example, the SMF 71 may select the UPF 72 which supports S-NSSAI-1 as well as Dual Steer. For example, the SMF 71 may store information for selecting the UPF 72 (e.g., information indicating which UPF(s) supports S-NSSAI(s) which acts as PNI-NPN, information indicating which UPF(s) supports network slice(s) which acts as PNI-NPN, information indicating which UPF(s) supports DS).

[0144] Step 13. The SMF 71 may derive the Dual Steer rule(s) based on PCF Dual Steer policy control. The Dual Steer rules may be used for controlling traffic steering, switching and splitting in the uplink direction and N4 Dual Steer rule(s) (e.g., the above Dual Steer rule(s)) may be sent to UPF 72 for controlling the traffic steering, switching and splitting in the downlink direction. The SMF 71 may send the Dual Steer rules to AMF 70 in a container, using NamfN1N2_MessageTransfer. The message to AMF 70 may include UE ID and Dual Steer session accept indication. The SMF 71 may send the Dual Steer rule(s) to the UPF 72.

[0145] Step 14. The AMF 70 may send the PDU session establishment accept message to the UE 3, which may include container with the Dual Steer rules as well as indication of granted S-NSSAI-1. The N4 Dual Steer Rules may be also provided to UPF 72. For example, the AMF 70 may send, to the UE 3, the Dual Steer rule(s). N4 Dual Steer Rules may be provided to UPF 72. The UE 3 may use the Dual Steer rules for MA PDU Session. The UE 3 may use the Dual Steer rules for steering traffic on MA PDU Session. The UE 3 may use the Dual Steer rules for controlling traffic steering, switching and splitting.

[0146] < Fourth example of the Second Aspect > 　　This example considers the case of a single AMF and a single RRC connection between UE 3 and RAN MN 501. The Fig. 41 describes the process in details.

[0147] In this example, a single AMF scenario with Dual Steer, and the case when the additional radio resources on the second 3GPP access are invoked using the multi-connectivity procedures as defined in NPL 7.

[0148] Step 1. UE 3 may already have an established PDU session on S-NSSAI-1. For example, the UE 3 indicates support for Dual 3GPP access and Dual 3GPP Access PDU session with MC allowed in the Registration Request message when the UE 3 performs the Registration procedure with the AMF 70 before the PDU session has been established. One example, the support for Dual 3GPP access and the Dual 3GPP Access PDU session upgrade with MC (or DC) allowed may be indicated by the UE 3 in the UE MM capability. The MC may include DC. The MC may be expressed as DC. The DC may include MC. The DC may be expressed as MC. The support for Dual 3GPP access indicates that the UE 3 supports the Dual 3GPP access function (or Dual 3GPP access or DS or DS function). The Dual 3GPP Access PDU session with MC allowed indicates that the UE 3 supports to configure the multi-connectivity as defined in NPL 7 in order to establish the Dual Steer.

[0149] Step 2. QoS update based on locally configured policy or a dynamic policy association from PCF 73 or signalling from another network function or UE 3 may initiate PDU session modification, which also includes triggering Dual 3GPP access with MC. The PCF 73 may indicate the RFSP Index value that corresponding to the PDU Session that may be used to configure the multi-connectivity.

[0150] Step 3. The SMF 71 may optionally check with UDM 75 if UE 3 is authorized to use Dual 3GPP access with MC for the associated with the PDU session. One example, the UDM 75 may provide the RFSP Index value that corresponding to the PDU Session that may be used to configure the multi-connectivity.

[0151] Step 4. Based on the PDU session modification, N4 session modification may be invoked towards UPF 72. For example, SMF 71 may request UPF 72 to assign additional N3 tunnel end point address for new QoS flows or some existing QoS Flow(s), which will use a second 3GPP access. Also, (updated) N4 dual steer rules may be transferred from SMF 71 to UPF 72.

[0152] Step 5. The SMF 71 may start the PDU Session Modification procedure to the AMF 70 by sending Namf_Communication_N1N2MessageTransfer message. The Namf_Communication_N1N2MessageTransfer message may include N2 SM information towards RAN MN 501, such as PDU Session ID, (updated) QoS and information indicating how flows may be distributed between access nodes, Dual Steer with MC and slice information S-NSSAI-1. The Dual Steer with MC indicates that the multi-connectivity is requested to establish the Dual Steer. The Dual Steer with MC may include some associated parameters such as QoS flows as a target QoS flow as subject to be handled by the secondary node (RAN SN 502), RFSP index value that may be used to select a secondary cell by the RAN MN 501.

[0153] Step 6. The AMF 70 sends the N2 request message to RAN MN 501 including the N1 SM container and the trigger indication, i.e., Dual Steer with MC, for a second 3GPP access, which may be used to trigger the multi-connectivity procedure. Refer to Step 5 for detail of the Dual Steer with MC.

[0154] Step 7. The N1 SM container for UE 3 may be forwarded by RAN MN 501 to the UE 3. N1 SM container may include PDU Session Modification Command with parameters such as PDU Session ID, QoS, as well as indication of Dual Steer with MC and (updated) Dual Steer rules. Refer to Step 5 for detail of the Dual Steer with MC. For example, the RAN MN 501 may send the N1 SM container to the UE 3.

[0155] Step 8. The RAN 501 (e.g., the RAN MN 501) may initiate a secondary cell addition procedure as defined in NPL 7. A secondary cell belongs to another RAN SN 502 (or RAN 502) may be selected based on the received Dual Steer with MC from the AMF 70, the UE measurement reports to RAN MN 501, its support of S-NSSAI-1, while taking into account the requested QoS. The procedure also uses information about the second N3 UPF tunnel endpoint for establishment of user-plane resources between the RAN SN 502 and UPF 72. The procedure may also establish data radio bearers between UE and cell on the RAN SN 502.

[0156] Step 9. The RAN MN 501 may initiate acknowledgement of N2 request to AMF 70, indicating tunnel information for the RAN SN 502, support for S-NSSAI-1, a result of Dual Steer with MC in the Dual Steer with MC accepted. The Dual Steer with MC accepted may be per QoS flows basis. The Dual Steer with MC accepted may indicate that the multi-connectivity with the Dual Steer is accepted. The Dual Steer with MC accepted may indicate that the multi-connectivity using the Dual Steer is accepted. The Dual Steer with MC accepted may indicate that the DS with the multi-connectivity is accepted. The Dual Steer with MC accepted may indicate that the DS using the multi-connectivity is accepted.

[0157] Step 10. AMF 70 may initiate PDU Session Update Request to SMF 71, providing the N2 information received in the acknowledgment from RAN MN 501. SMF 71 may reply to AMF 70, acknowledging the provided information.

[0158] Step 11. The UE 3 may send PDU Session Modification complete, acknowledging the PDU session modification request, Dual Steer with MC and the use of provided Dual Steer rules for the UL routing.

[0159] Step 12. The RAN MN 501 may send the UL NAS Transfer message to AMF 70 to transfer the message from the UE 3 in Step 11.

[0160] Step 13. AMF 70 may trigger PDU session modification to SMF 71, providing it with the N1 SM container (PDU Session Modification Command Ack). The SMF 71 replies with a Nsmf_PDUSession_UpdateSMContext Response to AMF 70.

[0161] Step 14. SMF 71 may initiate N4 session modification procedure towards UPF 72 to provide the N3 tunnel end point address in the RAN SN 502 for the second 3GPP access for user plane connection.

[0162] < Third Aspect > 　　The third aspect addresses how to enable provision of the additional dual 3GPP access-related configuration rules or changes to the rules between the network and UE 3. Fig. 42 depicts the Dual Steer rule provisioning to the UE 3 either SM (Session Management) procedures or the MM (Mobility Management) procedures.

[0163] < First example of the third aspect > 　　Fig. 42 depicts an example of the AF 201 guidance for the determination of the eURSP rules for the UE 3, pertaining specifically to Dual Steer policy. The example illustrates a case when a UE 3 is PNI-NPN user, and AF 201 belongs to the PNI-NPN operator.

[0164] The detailed processes of the First example of the Third Aspect are described below with the reference to Fig. 42.

[0165] Step 0. A hosting PLMN operator may designate one or more slices for PNI-NPN and the allowed CAG list may be provisioned for this subscriber. In this step, the operator may add support for Dual Steer, in UDM 75 as a part of Session Management Subscription data for the indicated subscriber. Dual Steer information may indicate whether multi-access / dual-steer Dual Steer-PDU session is allowed.

[0166] Step 1. UE 3 may be registered to the network (PNI-NPN) using (pre-configured) CAG information and with the configured NSSAI.

[0167] Step 2. In this step, the AF 201 may create or generate a request, invoking Nnef_ServiceParameter_Create service operation. For example, the request may be a request for update dual steer rules or a policy update request, as a part of eURSP rules.

[0168] Step 3. AF 201 may send to NEF 79 an HTTP POST request to the "Service Parameter Subscriptions" resource using Nnef_ServiceParameter_Create service.

[0169] The request may include at least one of the following parameters: 　　AF identifier - an identifier of the AF making a request; and 　　AF service identifier identifies the target traffic to be influenced, represented by the combination of DNN and optionally S-NSSAI, and application identifier or traffic filtering information. 　　UE identifier or identifier of a group of UEs - identifies UEs, e.g., Generic Public Subscription Identifier (GPSI) or for a group of UEs that belong to PNI-NPN, a group identifier can be used; and 　　DualSteer_PDU Session Type (Ethernet or IP). DualSteer_PDU Session Type may indicate Ethernet or IP.

[0170] Route selection parameters related to Dual Steer routing, which may include parameters that need to be created or updated in the eURSP rules, e.g.: 　　　　DualSteer_S-NSSAIs - either a single or a list of S-NSSAI(s); 　　　　Preferred 3GPP Access combination - indicates whether NR only is the preferred radio access technology or both RAN and LTE technologies can be used; 　　　　Non-Seamless WiFi Offload indication (DualSteer_Non-Seamless Wifi Offload indication) - indicates if the traffic of the matching application is to be offloaded to non-3GPP access outside of a Dual Steer PDU Session; 　　　　DualSteer_LocationCriteria - indicates location criteria to which the request applies, which can be given in a form of e.g., geographical area (such as radius from given coordinates); and 　　　　DualSteer_Time Window - time validity to which this service request refers.

[0171] The definition of the parameters in the request may refer to table 4 or 5.

[0172] Step 3a. NEF 79 may perform mapping, e.g. from AF service identifier to S-NSSAI and DNN.

[0173] Step 4a. The NEF 79 may invoke Nudm_SDM_Get service operation to map, e.g. the GPSI in Target UE Identifier into SUPI, according to information received from UDM 75. The NEF 79 also may assign a Transaction Reference ID to the Nnef_ServiceParameter_Create request.

[0174] Step 4b. The NEF 79 may need to authorize the service specific parameter provisioning request by the AF 201 with the UDM 75 by sending a Nudm_ServiceSpecificAuthorisation_Create service operation. If the AF 201 provides a geographical area as spatial validity condition, NEF 79 can forward to UDM 75 / UDR location information. The transformation into 3GPP identifiers (e.g. TAI(s)) may be preconfigured. Additional mapping can be done, as stated in Step 5.

[0175] Step 5. In this step, there may be an exchange with UDM 75 / UDR for performing the additional mapping, e.g. mapping of application traffic descriptors to the matching eURSP rules as well as mapping of Dual Steer route selection parameters to the corresponding Dual Steer Route Selection descriptors in the appropriate eURSP rules. UDM 75 / UDR may also store Dual Steer eURSP specific parameters (SUPI, DualSteer_S-NSSAI, DualSteer_Preferred 3GPP Access combination , etc.) and CAG cells (Allowed) and time validity in UDR. Note that CAG cells may be derived from Tracking Area.

[0176] Step 6. NEF 79 responds to the AF and a response, sent from the NEF to the AF, may include the assigned Transaction Reference ID.

[0177] Step 7. UDR may update the PCF 73 for data change using Nudr_DM_notify including one of DualSteer_S-NSSAI, CAG cells and time validity or etc.

[0178] Step 8. The PCF 73 may initiate UE Policy delivery via AMF 70 using Namf_Communication_N1N2MessageTransfer service. The message may include SUPI UE Policy Container with the dual steer rules. PCF 73 may derive the dual steer rules based on at least one of DualSteer_S-NSSAI, CAG cells and time validity, etc. PCF 73 may derive or update the dual steer rules based on at least one of DualSteer_S-NSSAI, CAG cells and time validity, etc. In a case where the PCF 73 determines that the dual steer rules or eURSP rules which has been sent to the UE 3 already is needed to be updated by information indicated by the AF 201 in step 2 or information which has been mapped in step 5, the PCF 73 may derive the dual steer rules or eURSP rules based on information indicated by the AF 201 in step 2 or information which has been mapped in step 5. For example, in a case where it indicates that S-NSSAI for PNI-NPN has been changed by information indicated by the AF 201 in step 2 or information which has been mapped in step 5, the PCF 73 may derive the dual steer rules or eURSP rules for the changed S-NSSAI.

[0179] Step 9. The AMF 70 transparently may pass or send the UE Policy with the UE dual steer rules (in other words, dual steer rules for the UE) to the UE, The UE dual steer rules may be provided to the UE 3 as part of the UE Policy information element or as an independent information element. The UE dual steer rules and the UE Policy information element may be provided separately. Alternatively, the AMF 70 may deliver the UE dual steer rules via any other NAS signalling message between the AMF 70 and the UE 3 like the Registration Accept message for example. For example, the AMF 70 may send, to the UE 3, the dual steer rules or eURSP rules. The UE 3 may use the dual steer rules or eURSP rules for MA / Dual Steer PDU Session. The UE 3 may use the dual steer rules or eURSP rules for steering traffic on MA / Dual Steer PDU Session. The UE 3 may use the dual steer rules or eURSP rules for controlling traffic steering, switching and splitting. The dual steer rule may be included in an eURSP rule.

[0180] < Second example of the third aspect > 　　Fig. 43 depicts an example of AF influencing traffic routing / steering by providing new or updated user-plane requirements, related to Dual Steer. The example refers to a case when a UE 3 or a group of UE 3s are PNI-NPN users, and the AF 201 belongs to a PNI-NPN operator.

[0181] The detailed processes of the Second example of the Second Aspect are described below with the reference to Fig. 43.

[0182] Step 0: A UE 3 or a group of UE 3s each may have an ongoing PDU session.

[0183] Step 1: In this step, the AF 201 may create or generate a request. To create or generate a new request, the AF 201 may invoke a Nnef_TrafficInfluence_Create service operation. For example, the request may be a request for update / influence dual steer rules for ongoing traffic routing.

[0184] Step 2. AF 201 may invoke Nnef_TrafficInfluence_Create service operation towards NEF 79. The input may include at least one of the following parameters: 　　AF Identifier - the identifier of the AF; 　　Transaction ID - The AF Transaction Id refers to the request; and 　　the address (IP or Ethernet) of one or more UE 3(s), 　　User Plane Latency Requirements for dual steer, which may include at least one of the following parameters: 　　　　maximum UL delay between UE 3 and UPF 72; 　　　　maximum UL PDV, as explained in the First Aspect; 　　　　Maximum DL delay between UE 3 and UPF 72; 　　　　maximum RTT between UE 3 and UPF 72; and 　　　　maximum RTT PDV, as explained in the First Aspect.

[0185] Step 3a. The NEF 79 may store the AF 201 request information in the UDR (the AF 201 request information may include AF Identifier, AF Transaction Id, the address of one or more UEs), and mapping / storing of User Plane Latency Requirements for Dual 3GPP access in UDR is performed in this step. The AF 201 may use the existing services for parameters update in the 3GPP system if any update to the User Plane latency Requirements for Dual access in the UDR is needed.

[0186] Step 3b. The NEF 79 may respond to the AF 201.

[0187] Step 4. The PCF 73(s) that may subscribe to modifications of AF 201 requests may receive a Nudr_DM_Notify notification of data change from the UDR. The Data Subset may identify that the information relates to AF update / influence user plane requirements request for Dual 3GPP Access.

[0188] Step 5. The PCF 73 determines if existing PDU Sessions are potentially impacted by the AF request. For each of these PDU Sessions, the PCF 73 may update the SMF 71 by using corresponding new policy information about the PDU Session (e.g., information in the AF request in Step 2 or mapping information in step 3a) by invoking Npcf_SMPolicyControl_UpdateNotify service operation. The PCF 73 may include the Dual Steer Policy ID(s) in control information of the relevant PCC rule. The PCF 73 also may include Metadata in the control information of the PCC rule when Metadata was provided by the AF 201. The Metadata may refer to additional data about service, in terms of e.g. access permission, QoS, location or time information, or a combination of these, which are not provided as direct attributes, but as additional, contextual information by AF. If the AF request may include a notification reporting request, the PCF 73 may include in the PCC rule(s) the information required for reporting the event, including the Notification Target Address pointing to the NEF 79 or AF 201 and the Notification Correlation ID containing the AF Transaction Internal ID. In a case where the PCF 73 determines that the dual steer rules which has been sent to the UE 3 already is needed to be updated by information in the AF request in Step 2 or mapping information in step 3a, the PCF 73 may send, to the SMF 71, information for updating the Dual Steer Rules (e.g., information in the AF request in Step 2 or mapping information in step 3a). For example, in a case where it indicates that maximum UL delay has been changed by information in the AF request in Step 2 or mapping information in step 3a, the PCF 73 may send, to the SMF 71, the maximum UL delay indicated by information in the AF request in Step 2 or mapping information in step 3a.

[0189] Step 6. When the updated policy information about the PDU Session is received from the PCF 73, the SMF 71 may derive the updated Dual Steer Rules. In a case where the SMF 71 receives the information for updating the Dual Steer Rules from the PCF 73, the SMF 71 may derive or update the Dual Steer Rules based on the information for updating the Dual Steer Rules. For example, in a case where the SMF 71 receives the maximum UL delay from the PCF 73, the SMF 71 may derive or update the Dual Steer Rules based on the received maximum UL delay. For example, in a case where the SMF 71 receives the maximum UL delay from the PCF 73, the SMF 71 may update the maximum UL delay in the previous Dual Steer Rules to the received maximum UL delay to derive or update the Dual Steer Rules.

[0190] Step 7. SMF 71 may send the updated Dual Steer Rules to UE 3(s) using N1 SM container and Namf_Communication_N1N2MessageTransfer to AMF 70. The update N4 Dual Steer rules may be provided to UPF 72 using N4 Session Modification Procedure. For example, the SMF 71 may send, to the UE 3, the updated Dual Steer rule(s). N4 Dual Steer Rules or the updated Dual Steer rule(s) may be provided to UPF 72. The UE 3 may use the updated Dual Steer rules for MA / Dual Steer PDU Session. The UE 3 may use the updated Dual Steer rules for steering traffic on MA / Dual Steer PDU Session. The UE 3 may use the updated Dual Steer rules for controlling traffic steering, switching and splitting.

[0191] < System overview > 　　Fig. 44 schematically illustrates a telecommunication system 1 for a mobile (cellular or wireless) to which the above aspects are applicable. The telecommunication system 1 represents a system overview in which an end to end communication is possible. For example, UE 3 (or user equipment, 'mobile device' 3) communicates with other UEs 3 or service servers in the data network 20 via respective (R)AN nodes 5 and a core network 7.

[0192] The (R)AN node 5 supports any radio accesses including a 5G radio access technology (RAT), an E-UTRA radio access technology, a beyond 5G RAT, a 6G RAT and non-3GPP RAT including wireless local area network (WLAN) technology as defined by the Institute of Electrical and Electronics Engineers (IEEE). The (R)AN node 5 may split into a Radio Unit (RU), Distributed Unit (DU) and Centralized Unit (CU). In some aspects, each of the units may be connected to each other and structure the (R)AN node 5 by adopting an architecture as defined by the Open RAN (O-RAN) Alliance, where the units above are referred to as O-RU, O-DU and O-CU respectively. The (R)AN node 5 may be split into control plane function and user plane function. Further, multiple user plane functions can be allocated to support a communication. In some aspects, user traffic may be distributed to multiple user plane functions and user traffic over each user plane functions are aggregated in both the UE 3 and the (R)AN node 5. This split architecture may be called as 'dual connectivity' or 'Multi connectivity'. The (R)AN node 5 can also support a communication using the satellite access. In some aspects, the (R)AN node 5 may support a satellite access and a terrestrial access. In addition, the (R)AN node 5 can also be referred as an access node for a non-wireless access. The non-wireless access includes a fixed line access as defined by the Broadband Forum (BBF) and an optical access as defined by the Innovative Optical and Wireless Network (IOWN).

[0193] The core network 7 may include logical nodes (or 'functions') for supporting a communication in the telecommunication system 1. For example, the core network 7 may be 5G Core Network (5GC) that includes, amongst other functions, control plane functions and user plane functions. Each function in logical nodes can be considered as a network function. The network function may be provided to another node by adapting the Service Based Architecture (SBA). A Network Function can be deployed as distributed, redundant, stateless, and scalable that provides the services from several locations and several execution instances in each location by adapting the network virtualization technology as defined by the European Telecommunications Standards Institute, Network Functions Virtualization (ETSI NFV). The core network 7 may support the Non-Public Network (NPN). The NPN may be a Stand-alone Non-Public Network (SNPN) or a Public Network Integrated NPN (PNI-NPN).

[0194] As is well known, a UE 3 may enter and leave the areas (i.e. radio cells) served by the (R)AN node 5 as the UE 3 is moving around in the geographical area covered by the telecommunication system 1. In order to keep track of the UE 3 and to facilitate movement between the different (R)AN nodes 5, the core network 7 comprises at least one access and mobility management function (AMF) 70. The AMF 70 is in communication with the (R)AN node 5 coupled to the core network 7. In some core networks, a mobility management entity (MME) or a mobility management node for beyond 5G or a mobility management node for 6G may be used instead of the AMF 70.

[0195] The core network 7 also includes, amongst others, 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, a Network Slice Selection Function (NSSF) 76 and a Network Slice Admission Control Function (NSACF) 77. When the UE 3 is roaming to a visited Public Land Mobile Network (VPLMN), a home Public Land Mobile Network (HPLMN) of the UE 3 provides the UDM 75 and at least some of the functionalities of the SMF 71, UPF 72, PCF 73 and NSACF 77 for the roaming-out UE 3.

[0196] The UE 3 and a respective serving (R)AN node 5 are connected via an appropriate air interface (for example the so-called "Uu" interface and / or the like). Neighboring (R)AN node 5 are connected to each other via an appropriate (R)AN node 5 to (R)AN node interface (such as the so-called "Xn" interface and / or the like). Each (R)AN node 5 is also connected to nodes in the core network 7 (such as the so-called core network nodes) via an appropriate interface (such as the so-called "N2" / "N3" interface(s) and / or the like). From the core network 7, connection to a data network 20 is also provided. The data network 20 can be an internet, a public network, an external network, a private network or an internal network of the PLMN. In case that the data network 20 is provided by a PLMN operator or Mobile Virtual Network Operator (MVNO), the IP Multimedia Subsystem (IMS) service may be provided by that data network 20. The UE 3 can be connected to the data network 20 using IPv4, IPv6, IPv4v6, Ethernet or unstructured data type. The data network may include an Application Function (AF) 201.

[0197] The "Uu" interface may include a Control plane of Uu interface and User plane of Uu interface. The User plane of Uu interface is responsible to convey user traffic between the UE 3 and a serving (R)AN node 5. The User plane of Uu interface may have a layered structure with SDAP, PDCP, RLC and MAC sublayer over the physical connection. The Control plane of Uu interface is responsible to establish, modify and release a connection between the UE 3 and a serving (R)AN node 5. The Control plane of Uu interface may have a layered structure with RRC, PDCP, RLC and MAC sublayers over the physical connection. For example, the following messages are communicated over the RRC layer to support AS signaling.

[0198] RRC Setup Request message: This message is sent from the UE 3 to the (R)AN node 5. In addition to the parameters that are disclosed by Aspects in this disclosure, following parameters may be included together in the RRC Setup Request message. 　　　　establishmentCause and ue-Identity. The ue-Identity may have a value of ng-5G-S-TMSI-Part1 or randomValue.

[0199] RRC Setup message: This message is sent from the (R)AN node 5 to the UE 3. In addition to the parameters that are disclosed by Aspects in this disclosure, following parameters may be included together in the RRC Setup message. 　　　　masterCellGroup and radioBearerConfig.

[0200] RRC setup complete message: This message is sent from the UE 3 to the (R)AN node 5. In addition to the parameters that are disclosed by Aspects in this disclosure, following parameters may be included together in the RRC setup complete message. 　　　　guami-Type, iab-NodeIndication, idleMeasAvailable, mobilityState, ng-5G-S-TMSI-Part2, registeredAMF, selectedPLMN-Identity.

[0201] The UE 3 and the AMF 70 are connected via an appropriate interface (for example the so-called N1 interface and / or the like). The N1 interface is responsible to provide a communication between the UE 3 and the AMF 70 to support NAS signaling. The N1 interface may be established over a 3GPP access and over a non-3GPP access. For example, the following messages are communicated over the N1 interface.

[0202] registration request message: This message is sent from the UE 3 to the AMF 70. In addition to the parameters that are disclosed by Aspects in this disclosure, following parameters may be included together 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 classmark 2, 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 accept message: This message is sent from the AMF 70 to the UE 3. In addition to the parameters that are disclosed by Aspects in this disclosure, following parameters may be included together in the registration accept 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 the UE 3 to the AMF 70. In addition to the parameters that are disclosed by Aspects in this disclosure, following parameters may be included together in the Registration Complete message. 　　　　SOR transparent container.

[0203] Authentication Request message: This message is sent from the AMF 70 to the UE 3. In addition to the parameters that are disclosed by Aspects in this disclosure, following parameters may be included together 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 the UE 3 to the AMF 70. In addition to the parameters that are disclosed by Aspects in this disclosure, following parameters may be populated together in the Authentication Response message. 　　　　Authentication response message identity, Authentication response parameter and EAP message. 　　Authentication Result message: This message is sent from the AMF 70 to the UE 3. In addition to the parameters that are disclosed by Aspects in this disclosure, following parameters may be populated together in the Authentication Result message. 　　　　ngKSI, EAP message and ABBA. 　　Authentication Failure message: This message is sent from the UE 3 to the AMF 70. In addition to the parameters that are disclosed by Aspects in this disclosure, following parameters may be populated together in the Authentication Failure message. 　　　　Authentication failure message identity, 5GMM cause and Authentication failure parameter. 　　Authentication Reject message: This message is sent from the AMF 70 to the UE 3. In addition to the parameters that are disclosed by Aspects in this disclosure, following parameters may be populated together in the Authentication Reject message. 　　　　EAP message.

[0204] Service Request message: This message is sent from the UE 3 to the AMF 70. In addition to the parameters that are disclosed by Aspects in this disclosure, following parameters may be populated together 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 the AMF 70 to the UE 3. In addition to the parameters that are disclosed by Aspects in this disclosure, following parameters may be populated together 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 the AMF 70 to the UE 3. In addition to the parameters that are disclosed by Aspects in this disclosure, following parameters may be populated together in the Service Reject message. 　　　　5GMM cause, PDU session status, T3346 value, EAP message, T3448 value and CAG information list.

[0205] Configuration Update Command message: This message is sent from the AMF 70 to the UE 3. In addition to the parameters that are disclosed by Aspects in this disclosure, following parameters may be populated together 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, 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 the UE 3 to the AMF 70. In addition to the parameters that are disclosed by Aspects in this disclosure, following parameters may be populated together in the Configuration Update Complete message. 　　　　Configuration update complete message identity.

[0206] < User equipment (UE) > 　　Fig. 45 is a block diagram illustrating the main components of the UE 3 (mobile device 3). As shown, the UE 3 includes a transceiver circuit 31 which is operable to transmit signals to and to receive signals from the connected node(s) via one or more antennas 32. Further, the UE 3 may include a user interface 34 for inputting information from outside or outputting information to outside. Although not necessarily shown in the Figure, the UE 3 may have all the usual functionality of a conventional mobile device and this may be provided by any one or any combination of hardware, software and firmware, as appropriate. Software may be pre-installed in the memory and / or may be downloaded via the telecommunication network or from a removable data storage device (RMD), for example. A controller 33 controls the operation of the UE 3 in accordance with software stored in a memory 36. The software includes, among other things, an operating system 361 and a communications control module 362 having at least a transceiver control module 3621. The communications control module 362 (using its transceiver control module 3621) is responsible for handling (generating / sending / receiving) signalling and uplink / downlink data packets between the UE 3 and other nodes, such as the (R)AN node 5 and the AMF 70. Such signalling may include, for example, appropriately formatted signalling messages (e.g. a registration request message and associated response messages) relating to access and mobility management procedures (for the UE 3). The controller 33 interworks with one or more Universal Subscriber Identity Module (USIM) 35. If there are multiple USIMs 35 equipped, the controller 33 may activate only one USIM 35 or may activate multiple USIMs 35 at the same time.

[0207] The UE 3 may, for example, support the Non-Public Network (NPN), The NPN may be a Stand-alone Non-Public Network (SNPN) or a Public Network Integrated NPN (PNI-NPN). The UE 3 may, for example, be an item of equipment for production or manufacture and / or an item of energy related machinery (for example equipment or machinery such as: boilers; engines; turbines; solar panels; wind turbines; hydroelectric generators; thermal power generators; nuclear electricity generators; batteries; nuclear systems and / or associated equipment; heavy electrical machinery; pumps including vacuum pumps; compressors; fans; blowers; oil hydraulic equipment; pneumatic equipment; metal working machinery; manipulators; robots and / or their application systems; tools; molds or dies; rolls; conveying equipment; elevating equipment; materials handling equipment; textile machinery; sewing machines; printing and / or related machinery; paper converting machinery; chemical machinery; mining and / or construction machinery and / or related equipment; machinery and / or implements for agriculture, forestry and / or fisheries; safety and / or environment preservation equipment; tractors; precision bearings; chains; gears; power transmission equipment; lubricating equipment; valves; pipe fittings; and / or application systems for any of the previously mentioned equipment or machinery etc.). The UE 3 may, for example, be an item of transport equipment (for example transport equipment such as: rolling stocks; motor vehicles; motor cycles; bicycles; trains; buses; carts; rickshaws; ships and other watercraft; aircraft; rockets; satellites; drones; balloons etc.). The UE 3 may, for example, be an item of information and communication equipment (for example information and communication equipment such as: electronic computer and related equipment; communication and related equipment; electronic components etc.). The UE 3 may, for example, be a refrigerating machine, a refrigerating machine applied product, an item of trade and / or service industry equipment, a vending machine, an automatic service machine, an office machine or equipment, a consumer electronic and electronic appliance (for example a consumer electronic appliance such as: audio equipment; video equipment; a loud speaker; a radio; a television; a microwave oven; a rice cooker; a coffee machine; a dishwasher; a washing machine; a dryer; an electronic fan or related appliance; a cleaner etc.).

[0208] The UE 3 may, for example, be an electrical application system or equipment (for example an electrical application system or equipment such as: an x-ray system; a particle accelerator; radio isotope equipment; sonic equipment; electromagnetic application equipment; electronic power application equipment etc.). The UE 3 may, for example, be an electronic lamp, a luminaire, a measuring instrument, an analyzer, a tester, or a surveying or sensing instrument (for example a surveying or sensing instrument such as: a smoke alarm; a human alarm sensor; a motion sensor; a wireless tag etc.), a watch or clock, a laboratory instrument, optical apparatus, medical equipment and / or system, a weapon, an item of cutlery, a hand tool, or the like. The UE 3 may, for example, be a wireless-equipped personal digital assistant or related equipment (such as a wireless card or module designed for attachment to or for insertion into another electronic device (for example a personal computer, electrical measuring machine)). The UE 3 may be a device or a part of a system that provides applications, services, and solutions described below, as to "internet of things (IoT)", using a variety of wired and / or wireless communication technologies.

[0209] Internet of Things devices (or "things") may be equipped with appropriate electronics, software, sensors, network connectivity, and / or the like, which enable these devices to collect and exchange data with each other and with other communication devices. IoT devices may comprise automated equipment that follow software instructions stored in an internal memory. IoT devices may operate without requiring human supervision or interaction. IoT devices might also remain stationary and / or inactive for a long period of time. IoT devices may be implemented as a part of a (generally) stationary apparatus. IoT devices may also be embedded in non-stationary apparatus (e.g. vehicles) or attached to animals or persons to be monitored / tracked. It will be appreciated that IoT technology can be implemented on any communication devices that can connect to a communications network for sending / receiving data, regardless of whether such communication devices are controlled by human input or software instructions stored in memory. It will be appreciated that IoT devices are sometimes also referred to as Machine-Type Communication (MTC) devices or Machine-to-Machine (M2M) communication devices or Narrow Band-IoT UE (NB-IoT UE). It will be appreciated that a UE 3 may support one or more IoT or MTC applications. The UE 3 may be a smart phone or a wearable device (e.g. smart glasses, a smart watch, a smart ring, or a hearable device). The UE 3 may be a car, or a connected car, or an autonomous car, or a vehicle device, or a motorcycle or V2X (Vehicle to Everything) communication module (e.g. Vehicle to Vehicle communication module, Vehicle to Infrastructure communication module, Vehicle to People communication module and Vehicle to Network communication module).

[0210] < (R)AN node > 　　Fig. 46 is a block diagram illustrating the main components of an exemplary (R)AN node 5, for example a base station ('eNB' in LTE, 'gNB' in 5G, a base station for 5G beyond, a base station for 6G). As shown, the (R)AN node 5 includes a transceiver circuit 51 which is operable to transmit signals to and to receive signals from connected UE(s) 3 via one or more antennas 52 and to transmit signals to and to receive signals from other network nodes (either directly or indirectly) via a network interface 53. A controller 54 controls the operation of the (R)AN node 5 in accordance with software stored in a memory 55. Software may be pre-installed in the memory and / or may be downloaded via the telecommunication network or from a removable data storage device (RMD), for example. The software includes, among other things, an operating system 551 and a communications control module 552 having at least a transceiver control module 5521. The communications control module 552 (using its transceiver control sub-module) is responsible for handling (generating / sending / receiving) signalling between the (R)AN node 5 and other nodes, such as the UE 3, another (R)AN node 5, the AMF 70 and the UPF 72 (e.g. directly or indirectly). The signalling may include, for example, appropriately formatted signalling messages relating to a radio connection and a connection with the core network 7 (for a particular UE 3), and in particular, relating to connection establishment and maintenance (e.g. RRC connection establishment and other RRC messages), NG Application Protocol (NGAP) messages (i.e. messages by N2 reference point) and Xn application protocol (XnAP) messages (i.e. messages by Xn reference point), etc. Such signalling may also include, for example, broadcast information (e.g. Master Information and System information) in a sending case. The controller 54 is also configured (by software or hardware) to handle related tasks such as, when implemented, UE mobility estimate and / or moving trajectory estimation. The (R)AN node 5 may support the Non-Public Network (NPN), The NPN may be a Stand-alone Non-Public Network (SNPN) or a Public Network Integrated NPN (PNI-NPN). The RAN in this disclosure may have same components to the (R)AN node 5. The MN or SN in this disclosure may have same components to the (R)AN node 5. The (R)AN node 5 may be expressed as a RAN node, RAN, (R)AN etc.

[0211] < System overview of (R)AN node 5 based on O-RAN architecture > 　　Fig. 47 schematically illustrates a (R)AN node 5 based on O-RAN architecture to which the (R)AN node 5 aspects are applicable. The (R)AN node 5 based on O-RAN architecture represents a system overview in which the (R)AN node is split into a Radio Unit (RU) 60, Distributed Unit (DU) 61 and Centralized Unit (CU) 62. In some aspects, each unit may be combined. For example, the RU 60 can be integrated / combined with the DU 61 as an integrated / combined unit, the DU 61 can be integrated / combined with the CU 62 as another integrated / combined unit. Any functionality in the description for a unit (e.g. one of RU 60, DU 61 and CU 62) can be implemented in the integrated / combined unit above. Further, CU 62 can separate into two functional units such as CU Control plane (CP) and CU User plane (UP). The CU CP has a control plane functionality in the (R)AN node 5. The CU UP has a 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 and / or the like). The UE 3 and a respective serving RU 60 are connected via an appropriate air interface (for example the so-called "Uu" interface and / or the like). Each RU 60 is connected to the DU 61 via an appropriate interface (such as the so-called "Front haul", "Open Front haul", "F1" interface and / or the like). Each DU 61 is connected to the CU 62 via an appropriate interface (such as the so-called "Mid haul", "Open Mid haul", "E2" interface and / or the like). Each CU 62 is also connected to nodes in the core network 7 (such as the so-called core network nodes) via an appropriate interface (such as the so-called "Back haul", "Open Back haul", "N2" / "N3" interface(s) and / or the like). In addition, a user plane part of the DU 61 can also be connected to the core network nodes via an appropriate interface (such as the so-called "N3" interface(s) and / or the like). Depending on functionality split among the RU 60, DU 61 and CU 62, each unit provides some of the functionality that is provided by the (R)AN node 5. For example, the RU 60 may provide a functionalities to communicate with a UE 3 over air interface, the DU 61 may provide functionalities to support MAC layer and RLC layer, the CU 62 may provide functionalities to support PDCP layer, SDAP layer and RRC layer.

[0212] < Radio Unit (RU) > 　　Fig. 48 is a block diagram illustrating the main components of an exemplary RU 60, for example a RU part of base station ('eNB' in LTE, 'gNB' in 5G, a base station for 5G beyond, a base station for 6G). As shown, the RU 60 includes a transceiver circuit 601 which is operable to transmit signals to and to receive signals from connected UE(s) 3 via one or more antennas 602 and to transmit signals to and to receive signals from other network nodes or network unit (either directly or indirectly) via a network interface 603. A controller 604 controls the operation of the RU 60 in accordance with software stored in a memory 605. Software may be pre-installed in the memory and / or may be downloaded via the telecommunication network or from a removable data storage device (RMD), for example. The software includes, among other things, an operating system 6051 and a communications control module 6052 having at least a transceiver control module 60521. The communications control module 6052 (using its transceiver control sub-module) is responsible for handling (generating / sending / receiving) signalling between the RU 60 and other nodes or units, such as the UE 3, another RU 60 and DU 61 (e.g. directly or indirectly). The signalling may include, for example, appropriately formatted signalling messages relating to a radio connection and a connection with the RU 60 (for a particular UE 3), and in particular, relating to MAC layer and RLC layer. The controller 604 is also configured (by software or hardware) to handle related tasks such as, when implemented, UE mobility estimate and / or moving trajectory estimation. The RU 60 may support the Non-Public Network (NPN), The NPN may be a Stand-alone Non-Public Network (SNPN) or a Public Network Integrated NPN (PNI-NPN). As described above, the RU 60 can be integrated / combined with the DU 61 as an integrated / combined unit. Any functionality in the description for the RU 60 can be implemented in the integrated / combined unit above.

[0213] < Distributed Unit (DU) > 　　Fig. 49 is a block diagram illustrating the main components of an exemplary DU 61, for example a DU part of a base station ('eNB' in LTE, 'gNB' in 5G, a base station for 5G beyond, a base station for 6G). As shown, the apparatus includes a transceiver circuit 611 which is operable to transmit signals to and to receive signals from other nodes or units (including the RU 60) via a network interface 612. A controller 613 controls the operation of the DU 61 in accordance with software stored in a memory 614. Software may be pre-installed in the memory 614 and / or may be downloaded via the telecommunication network or from a removable data storage device (RMD), for example. The software includes, among other things, an operating system 6141 and a communications control module 6142 having at least a transceiver control module 61421. The communications control module 6142 (using its transceiver control module 61421 is responsible for handling (generating / sending / receiving) signalling between the DU 61 and other nodes or units, such as the RU 60 and other nodes and units. The DU 61 may support the Non-Public Network (NPN), The NPN may be a Stand-alone Non-Public Network (SNPN) or a Public Network Integrated NPN (PNI-NPN). As described above, the RU 60 can be integrated / combined with the DU 61 or CU 62 as an integrated / combined unit. Any functionality in the description for DU 61 can be implemented in one of the integrated / combined unit above.

[0214] < Centralized Unit (CU) > 　　Fig. 50 is a block diagram illustrating the main components of an exemplary CU 62, for example a CU part of base station ('eNB' in LTE, 'gNB' in 5G, a base station for 5G beyond, a base station for 6G). As shown, the apparatus includes a transceiver circuit 621 which is operable to transmit signals to and to receive signals from other nodes or units (including the DU 61) via a network interface 622. A controller 623 controls the operation of the CU 62 in accordance with software stored in a memory 624. Software may be pre-installed in the memory 624 and / or may be downloaded via the telecommunication network or from a removable data storage device (RMD), for example. The software includes, among other things, an operating system 6241 and a communications control module 6242 having at least a transceiver control module 62421. The communications control module 6242 (using its transceiver control module 62421 is responsible for handling (generating / sending / receiving) signalling between the CU 62 and other nodes or units, such as the DU 61 and other nodes and units. The CU 62 may support the Non-Public Network (NPN), The NPN may be a Stand-alone Non-Public Network (SNPN) or a Public Network Integrated NPN (PNI-NPN). As described above, the CU 62 can be integrated / combined with the DU 61 as an integrated / combined unit. Any functionality in the description for the CU 62 can be implemented in the integrated / combined unit above.

[0215] < AMF > 　　Fig. 51 is a block diagram illustrating the main components of the AMF 70. As shown, the apparatus includes a transceiver circuit 701 which is operable to transmit signals to and to receive signals from other nodes (including the UE 3, the NSSF 76) via a network interface 702. A controller 703 controls the operation of the AMF 70 in accordance with software stored in a memory 704. Software may be pre-installed in the memory 704 and / or may be downloaded via the telecommunication network or from a removable data storage device (RMD), for example. The software includes, among other things, an operating system 7041 and a communications control module 7042 having at least a transceiver control module 70421. The communications control module 7042 (using its transceiver control module 70421 is responsible for handling (generating / sending / receiving) signalling between the AMF 70 and other nodes, such as the UE 3 (e.g. via the (R)AN node 5) and other core network nodes (including core network nodes in the HPLMN of the UE 3 when the UE 3 is roaming-in. Such signalling may include, for example, appropriately formatted signalling messages (e.g. a registration request message and associated response messages) relating to access and mobility management procedures (for the UE 3). The AMF 70 may support the Non-Public Network (NPN), The NPN may be a Stand-alone Non-Public Network (SNPN) or a Public Network Integrated NPN (PNI-NPN). The AMF in this disclosure may have same components to the AMF 70.

[0216] < SMF > 　　Fig. 52 is a block diagram illustrating the main components of the SMF 71. As shown, the apparatus includes a transceiver circuit 711 which is operable to transmit signals to and to receive signals from other nodes (including the AMF 70) via a network interface 712. A controller 713 controls the operation of the SMF 71 in accordance with software stored in a memory 714. Software may be pre-installed in the memory 714 and / or may be downloaded via the telecommunication network or from a removable data storage device (e.g. a removable memory device (RMD)), for example. The software includes, among other things, an operating system 7141 and a communications control module 7142 having at least a transceiver control module 71421. The communications control module 7142 (using its transceiver control module 71421 is responsible for handling (generating / sending / receiving) signalling between the SMF 71 and other nodes, such as the AMF 70 and other core network nodes (including core network nodes in the HPLMN of the UE 3 when the UE 3 is roaming-in. Such signalling may include, for example, appropriately formatted signalling messages (e.g. a HTTP restful methods based on the service based interfaces) relating to policy management procedures (for the UE 3). The SMF 71 may support the Non-Public Network (NPN), The NPN may be a Stand-alone Non-Public Network (SNPN) or a Public Network Integrated NPN (PNI-NPN). The SMF in this disclosure may have same components to the SMF 71.

[0217] < UPF > 　　Fig. 53 is a block diagram illustrating the main components of the UPF 72. As shown, the apparatus includes a transceiver circuit 721 which is operable to transmit signals to and to receive signals from other nodes (including the SMF 71) via a network interface 722. A controller 723 controls the operation of the UPF 72 in accordance with software stored in a memory 724. Software may be pre-installed in the memory 724 and / or may be downloaded via the telecommunication network or from a removable data storage device (e.g. a removable memory device (RMD)), for example. The software includes, among other things, an operating system 7241 and a communications control module 7242 having at least a transceiver control module 72421. The communications control module 7242 (using its transceiver control module 72421 is responsible for handling (generating / sending / receiving) signalling between the UPF 72 and other nodes, such as the SMF 71 and other core network nodes (including core network nodes in the HPLMN of the UE 3 when the UE 3 is roaming-in. Such signalling may include, for example, appropriately formatted signalling messages (e.g. a HTTP restful methods based on the service based interfaces) relating to policy management procedures (for the UE 3). The UPF 72 may support the Non-Public Network (NPN), The NPN may be a Stand-alone Non-Public Network (SNPN) or a Public Network Integrated NPN (PNI-NPN). The UPF in this disclosure may have same components to the UPF 72.

[0218] < PCF > 　　Fig. 54 is a block diagram illustrating the main components of the PCF 73. As shown, the apparatus includes a transceiver circuit 731 which is operable to transmit signals to and to receive signals from other nodes (including the AMF 70) via a network interface 732. A controller 733 controls the operation of the PCF 73 in accordance with software stored in a memory 734. Software may be pre-installed in the memory 734 and / or may be downloaded via the telecommunication network or from a removable data storage device (e.g. a removable memory device (RMD)), for example. The software includes, among other things, an operating system 7341 and a communications control module 7342 having at least a transceiver control module 73421. The communications control module 7342 (using its transceiver control module 73421 is responsible for handling (generating / sending / receiving) signalling between the PCF 73 and other nodes, such as the AMF 70 and other core network nodes (including core network nodes in the HPLMN of the UE 3 when the UE 3 is roaming-in. Such signalling may include, for example, appropriately formatted signalling messages (e.g. a HTTP restful methods based on the service based interfaces) relating to policy management procedures (for the UE 3). The PCF 73 may support the Non-Public Network (NPN), The NPN may be a Stand-alone Non-Public Network (SNPN) or a Public Network Integrated NPN (PNI-NPN). The PCF in this disclosure may have same components to the PCF 73.

[0219] < NWDAF > 　　Fig. 55 is a block diagram illustrating the main components of the NWDAF 74. As shown, the apparatus includes a transceiver circuit 741 which is operable to transmit signals to and to receive signals from other nodes (including the AMF 70 and the UDM 75) via a network interface 742. A controller 743 controls the operation of the NWDAF 74 in accordance with software stored in a memory 744. Software may be pre-installed in the memory 744 and / or may be downloaded via the telecommunication network or from a removable data storage device (e.g. a removable memory device (RMD)), for example. The software includes, among other things, an operating system 7441 and a communications control module 7442 having at least a transceiver control module 74421. The communications control module 7442 (using its transceiver control module 74421 is responsible for handling (generating / sending / receiving) signalling between the NWDAF 74 and other nodes, such as the AMF 70 and other core network nodes (including core network nodes in the HPLMN of the UE 3 when the UE 3 is roaming-in. Such signalling may include, for example, appropriately formatted signalling messages (e.g. a HTTP restful methods based on the service based interfaces) relating to policy management procedures (for the UE 3). The NWDAF 74 may support the Non-Public Network (NPN), The NPN may be a Stand-alone Non-Public Network (SNPN) or a Public Network Integrated NPN (PNI-NPN). The NWDAF in this disclosure may have same components to the NWDAF 74.

[0220] < UDM > 　　Fig. 56 is a block diagram illustrating the main components of the UDM 75. As shown, the apparatus includes a transceiver circuit 751 which is operable to transmit signals to and to receive signals from other nodes (including the AMF 70) via a network interface 752. A controller 753 controls the operation of the UDM 75 in accordance with software stored in a memory 754. Software may be pre-installed in the memory 754 and / or may be downloaded via the telecommunication network or from a removable data storage device (RMD), for example. The software includes, among other things, an operating system 7541 and a communications control module 7542 having at least a transceiver control module 75421. The communications control module 7542 (using its transceiver control module 75421 is responsible for handling (generating / sending / receiving) signalling between the UDM 75 and other nodes, such as the AMF 70 and other core network nodes (including core network nodes in the VPLMN of the UE 3 when the UE 3 is roaming-out. Such signalling may include, for example, appropriately formatted signalling messages (e.g. a HTTP restful methods based on the service based interfaces) relating to mobility management procedures (for the UE 3). The UDM 75 may support the Non-Public Network (NPN), The NPN may be a Stand-alone Non-Public Network (SNPN) or a Public Network Integrated NPN (PNI-NPN). The UDM in this disclosure may have same components to the UDM 75.

[0221] < NSSF > 　　Fig. 57 is a block diagram illustrating the main components of the NSSF 76. As shown, the apparatus includes a transceiver circuit 761 which is operable to transmit signals to and to receive signals from other nodes (including the AMF 70) via a network interface 762. A controller 763 controls the operation of the NSSF 76 in accordance with software stored in a memory 764. Software may be pre-installed in the memory 764 and / or may be downloaded via the telecommunication network or from a removable data storage device (RMD), for example. The software includes, among other things, an operating system 7641 and a communications control module 7642 having at least a transceiver control module 76421. The communications control module 7642 (using its transceiver control module 76421 is responsible for handling (generating / sending / receiving) signalling between the NSSF 76 and other nodes, such as the AMF 70 and other core network nodes (including core network nodes in the VPLMN of the UE 3 when the UE 3 is roaming-out. Such signalling may include, for example, appropriately formatted signalling messages (e.g. a HTTP restful methods based on the service based interfaces) relating to mobility management procedures (for the UE 3). The NSSF 76 may support the Non-Public Network (NPN), The NPN may be a Stand-alone Non-Public Network (SNPN) or a Public Network Integrated NPN (PNI-NPN). The NSSF in this disclosure may have same components to the NSSF 76.

[0222] < NSACF > 　　Fig. 58 is a block diagram illustrating the main components of the NSACF 77. As shown, the apparatus includes a transceiver circuit 771 which is operable to transmit signals to and to receive signals from other nodes (including the AMF 70) via a network interface 772. A controller 773 controls the operation of the NSACF 77 in accordance with the software stored in a memory 774. The Software may be pre-installed in the memory 774 and / or may be downloaded via the telecommunication network or from a removable data storage device (e.g. a removable memory device (RMD)), for example. The software includes, among other things, an operating system 7741 and a communications control module 7742 having at least a transceiver control module 77421. The communications control module 7742 (using its transceiver control module 77421 is responsible for handling (generating / sending / receiving) signalling between the NSACF 77 and other nodes, such as the AMF 70 and other core network nodes (including core network nodes in the HPLMN of the UE 3 when the UE 3 is roaming-in. Such signalling may include, for example, appropriately formatted signalling messages (e.g. a HTTP restful methods based on the service based interfaces) relating to network data analytics function procedures (for the UE 3). The NSACF 77 may support the Non-Public Network (NPN), The NPN may be a Stand-alone Non-Public Network (SNPN) or a Public Network Integrated NPN (PNI-NPN). The NSACF in this disclosure may have same components to the NSACF 77.

[0223] < AUSF > 　　Fig. 59 is a block diagram illustrating the main components of the AUSF 78. As shown, the apparatus includes a transceiver circuit 781 which is operable to transmit signals to and to receive signals from other nodes (including the AMF 70) via a network interface 782. A controller 783 controls the operation of the AUSF 78 in accordance with the software stored in a memory 784. The Software may be pre-installed in the memory 784 and / or may be downloaded via the telecommunication network or from a removable data storage device (e.g. a removable memory device (RMD)), for example. The software includes, among other things, an operating system 7841 and a communications control module 7842 having at least a transceiver control module 78421. The communications control module 7842 (using its transceiver control module 78421 is responsible for handling (generating / sending / receiving) signalling between the AUSF 78 and other nodes, such as the AMF 70 and other core network nodes (including core network nodes in the HPLMN of the UE 3 when the UE 3 is roaming-in. Such signalling may include, for example, appropriately formatted signalling messages (e.g. a HTTP restful methods based on the service based interfaces) relating to network data analytics function procedures (for the UE 3). The AUSF 78 may support the Non-Public Network (NPN), The NPN may be a Stand-alone Non-Public Network (SNPN) or a Public Network Integrated NPN (PNI-NPN). The AUSF in this disclosure may have same components to the AUSF 78.

[0224] < NEF > 　　Fig. 60 is a block diagram illustrating the main components of the NEF 79. As shown, the apparatus includes a transceiver circuit 791 which is operable to transmit signals to and to receive signals from other nodes (including the AMF 70) via a network interface 792. A controller 793 controls the operation of the NEF 79 in accordance with the software stored in a memory 794. The Software may be pre-installed in the memory 794 and / or may be downloaded via the telecommunication network or from a removable data storage device (e.g. a removable memory device (RMD)), for example. The software includes, among other things, an operating system 7941 and a communications control module 7942 having at least a transceiver control module 79421. The communications control module 7942 (using its transceiver control module 79421 is responsible for handling (generating / sending / receiving) signalling between the NEF 79 and other nodes, such as the AMF 70 and other core network nodes (including core network nodes in the HPLMN of the UE 3 when the UE 3 is roaming-in. Such signalling may include, for example, appropriately formatted signalling messages (e.g. a HTTP restful methods based on the service based interfaces) relating to network data analytics function procedures (for the UE 3). The NEF 79 may support the Non-Public Network (NPN), The NPN may be a Stand-alone Non-Public Network (SNPN) or a Public Network Integrated NPN (PNI-NPN). The NEF in this disclosure may have same components to the NEF 79.

[0225] < AF > 　　Fig. 61 is a block diagram illustrating the main components of the AF 201. As shown, the apparatus includes a transceiver circuit 2011 which is operable to transmit signals to and to receive signals from other nodes (including the UE 3) via a network interface 2012. A controller 2013 controls the operation of the AF 201 in accordance with software stored in a memory 2014. Software may be pre-installed in the memory 2014 and / or may be downloaded via the telecommunication network or from a removable data storage device (e.g. a removable memory device (RMD)), for example. The software includes, among other things, an operating system 20141 and a communications control module 20142 having at least a transceiver control module 201421. The communications control module 20142 (using its transceiver control module 201421 is responsible for handling (generating / sending / receiving) signalling between the AF 201 and other nodes, such as the UE 3 and other core network nodes (including core network nodes in the HPLMN of the UE 3 when the UE 3 is roaming-in. Such signalling may include, for example, appropriately formatted signalling messages (e.g. a HTTP restful methods based on the service based interfaces) relating to policy management procedures (for the UE 3). The AF 201 may support the Non-Public Network (NPN), The NPN may be a Stand-alone Non-Public Network (SNPN) or a Public Network Integrated NPN (PNI-NPN). The AF in this disclosure may have same components to the AF 201.

[0226] < Modifications and Alternatives > 　　Detailed aspects have been described above. As those skilled in the art will appreciate, a number of modifications and alternatives can be made to the above aspects whilst still benefiting from the disclosures embodied therein. By way of illustration only a number of these alternatives and modifications will now be described. In the above description, the UE 3 and the network apparatus are described for ease of understanding as having a number of discrete modules (such as the communication control modules). Whilst these modules may be provided in this way for certain applications, for example where an existing system has been modified to implement the disclosure, in other applications, for example in systems designed with the inventive features in mind from the outset, these modules may be built into the overall operating system or code and so these modules may not be discernible as discrete entities. These modules may also be implemented in software, hardware, firmware or a mix of these. Each controller may comprise any suitable form of processing circuitry including (but not limited to), for example: one or more hardware implemented computer processors; microprocessors; central processing units (CPUs); arithmetic logic units (ALUs); input / output (IO) circuits; internal memories / caches (program and / or data); processing registers; communication buses (e.g. control, data and / or address buses); direct memory access (DMA) functions, hardware or software implemented counters, pointers and / or timers; and / or the like.

[0227] In the above aspects, a number of software modules were described. As those skilled in the art will appreciate, the software modules may be provided in compiled or un-compiled form and may be supplied to the UE 3 and the network apparatus as a signal over a computer network, or on a recording medium. Further, the functionality performed by part or all of this software may be performed using one or more dedicated hardware circuits. However, the use of software modules is preferred as it facilitates the updating of the UE 3 and the network apparatus in order to update their functionalities. In the above aspects, a 3GPP radio communications (radio access) technology is used. However, any other radio communications technology (e.g. WLAN, Wi-Fi, WiMAX, Bluetooth, etc.) and other fix line communications technology (e.g. BBF Access, Cable Access, optical access, etc.) may also be used in accordance with the above aspects. Items of user equipment might include, for example, communication devices such as mobile telephones, smartphones, user equipment, personal digital assistants, laptop / tablet computers, web browsers, e-book readers and / or the like. Such mobile (or even generally stationary) devices are typically operated by a user, although it is also possible to connect so-called 'Internet of Things' (IoT) devices and similar machine-type communication (MTC) devices to the network. For simplicity, the present application refers to mobile devices (or UEs) in the description but it will be appreciated that the technology described can be implemented on any communication devices (mobile and / or generally stationary) that can connect to a communications network for sending / receiving data, regardless of whether such communication devices are controlled by human input or software instructions stored in memory. Various other modifications will be apparent to those skilled in the art and will not be described in further detail here.

[0228] As will be appreciated by one of skill in the art, the present disclosure may be embodied as a method, and system. Accordingly, the present disclosure may take the form of an entirely hardware embodiment, a software embodiment or an embodiment combining software and hardware aspects.

[0229] It will be understood that each block of the block diagrams, can be implemented by computer program instructions. These computer program instructions may be provided to a processor of a general-purpose computer, special purpose computer, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions / acts specified in the flowchart and / or block diagram block or blocks. A general-purpose processor may be a microprocessor, but in the alternative, the processor may be any conventional processor, controller, microcontroller, or state machine. A processor may also be implemented as a combination of computing devices, e.g., a plurality of microprocessors, one or more microprocessors, or any other such configuration.

[0230] The methods or algorithms described in connection with the examples disclosed herein may be embodied directly in hardware, in a software module executed by a processor, or in a combination of the two. A software module may reside in RAM memory, flash memory, ROM memory, EPROM memory, EEPROM memory, hard disk, a removable disk, a CD-ROM, or any other form of storage medium known in the art. A storage medium may be coupled to the processor such that the processor can read information from, and write information to, the storage medium. In the alternative, the storage medium may be integral to the processor. The processor and the storage medium may reside in an ASIC.

[0231] The previous description of the disclosed examples is provided to enable any person skilled in the art to make or use the present disclosure. Various modifications to these examples will be readily apparent to those skilled in the art, and the generic principles defined herein may be applied to other examples without departing from the spirit or scope of the disclosure. Thus, the present disclosure is not intended to be limited to the examples shown herein but is to be accorded the widest scope consistent with the principles and novel features disclosed herein.

[0232] While the disclosure has been particularly shown and described with reference to exemplary Aspects thereof, the disclosure is not limited to these Aspects. It will be understood by those of ordinary skill in the art that various changes in form and details may be made therein without departing from the spirit and scope of the present disclosure as defined by this document. For example, the Aspects above are not limited to 5GS, and the Aspects are also applicable to communication system other than 5GS (e.g., 6G system, 5G beyond system).

[0233] Although the present disclosure has been described with reference to the example embodiments, the present disclosure is not limited to the above. Various changes that can be understood by those skilled in the art can be made to the configuration and details of the present disclosure within the scope of the disclosure.

[0234] This application is based upon and claims the benefit of priority from Indian patent application No. 202311083215, filed on December 6, 2023, the disclosure of which is incorporated herein in its entirety by reference.

[0235] < Supplementary notes > 　　The whole or part of the example Aspects disclosed above can be described as, but not limited to, the following supplementary notes.

[0236] (Supplementary note 1) 　　A method of a UE comprising: 　　establishing two 3GPP accesses; and 　　determining whether to reduce amount of traffic sent over one access among the two 3GPP accesses or to duplicate the traffic or to switch the traffic, based on a maximum measured value of a first parameter and a threshold value of the first parameter. (Supplementary note 2) 　　A method of a UPF comprising: 　　communicating with a UE establishing two 3GPP accesses; and 　　determining whether to reduce amount of traffic sent over one access among the two 3GPP accesses or to duplicate the traffic or to switch the traffic, based on a maximum measured value of a first parameter and a threshold value of the first parameter. (Supplementary note 3) 　　A method of an AMF comprising: 　　sending, to a PCF, Dual 3GPP access support information indicating that a UE supports dual 3GPP access and ID of a UE, in a case where the AMF receives the Dual 3GPP access support information and first support information indicating that the UE supports for PNI-NPN as a network slice and dual 3GPP access; 　　receiving, from the PCF, an eURSP (enhanced URSP) rule for establishing Multi-Access / Dual-Steer PDU session; and 　　sending, to the UE, the eURSP rule. (Supplementary note 4) 　　A method of a UE comprising: 　　sending, to an AMF, Dual 3GPP access support information indicating that the UE supports dual 3GPP access and first support information indicating that the UE supports for PNI-NPN as a network slice and dual 3GPP access; and 　　receiving, from the AMF, an eURSP rule for establishing Multi-Access / Dual Steer PDU session. (Supplementary note 5) 　　A method of an AMF comprising: 　　receiving, from a UE, first support information indicating that the UE supports for PNI-NPN S-NSSAIs and requesting S-NSSAI in a case where PDU session establishment based on an eURSP rule is triggered; 　　selecting a SMF which supports for PNI-NPN S-NSSAIs, in a case where support of the UE for the S-NSSAI is verified; 　　receiving, from the SMF, a Dual Steer rule used for controlling traffic steering, switching and splitting of dual 3GPP access; and 　　sending, to the UE, the Dual Steer rule. (Supplementary note 6) 　　A method of a UE comprising: 　　sending, to an AMF, first support information indicating that the UE supports for PNI-NPN S-NSSAIs and requesting S-NSSAI in a case where the UE triggers PDU session establishment based on an eURSP rule; and 　　receiving, from the AMF, a Dual Steer rule used for controlling traffic steering, switching and splitting of dual 3GPP access, in a case where support of the UE for the S-NSSAI is verified. (Supplementary note 7) 　　A method of an AMF comprising: 　　receiving, from a UE, first support information indicating that the UE supports for PNI-NPN S-NSSAIs and requesting S-NSSAI and SAG information indicating a condition or a rule related to the use of the S-NSSAI by the UE, in a case where PDU session establishment based on an eURSP rule is triggered; 　　selecting a SMF which supports for PNI-NPN S-NSSAIs, in a case where support of the UE for the S-NSSAI and the SAG information are verified; 　　receiving, from the SMF, a Dual Steer rule used for controlling traffic steering, switching and splitting of dual 3GPP access; and 　　sending, to the UE, the Dual Steer rule. (Supplementary note 8) 　　A method of a UE comprising: 　　sending, to an AMF, first support information indicating that the UE supports for PNI-NPN S-NSSAIs and requesting S-NSSAI and SAG information indicating a condition or a rule related to the use of the S-NSSAI by the UE, in a case where the UE triggers PDU session establishment based on an eURSP rule; and 　　receiving, from the AMF, a Dual Steer rule used for controlling traffic steering, switching and splitting of dual 3GPP access, in a case where support of the UE for the S-NSSAI and the SAG information are verified. (Supplementary note 9) 　　A method of an AMF comprising: 　　receiving, from a PCF, a dual steer rule of dual 3GPP access for a UE that is updated based on a request from an AF; and 　　sending, to the UE, the dual steer rule, 　　wherein the dual steer rule is included in an eURSP rule. (Supplementary note 10) 　　A method of a UE comprising: 　　performing a registration procedure with an AMF; and 　　receiving, from the AMF, a dual steer rule of dual 3GPP access for the UE, in a case where the dual steer rule is updated based on a request from an AF, 　　wherein the dual steer rule is included in an eURSP rule. (Supplementary note 11) 　　A method of an AMF comprising: 　　receiving, from a SMF, an updated dual steer rule of dual 3GPP access derived based on a request from an AF; and 　　sending, to a UE, the updated dual steer rule. (Supplementary note 12) 　　A method of a UE comprising: 　　performing a PDU session establishment procedure with an AMF; and 　　receiving, from the AMF, an updated dual steer rule of dual 3GPP access derived in a case where the updated dual steer rule is derived based on a request from an AF. (Supplementary note 13) 　　A UE comprising: 　　means for establishing two 3GPP accesses; and 　　means for determining whether to reduce amount of traffic sent over one access among the two 3GPP accesses or to duplicate the traffic or to switch the traffic, based on a maximum measured value of a first parameter and a threshold value of the first parameter. (Supplementary note 14) 　　A UPF comprising: 　　means for communicating with a UE establishing two 3GPP accesses; and 　　means for determining whether to reduce amount of traffic sent over one access among the two 3GPP accesses or to duplicate the traffic or to switch the traffic, based on a maximum measured value of a first parameter and a threshold value of the first parameter. (Supplementary note 15) 　　An AMF comprising: 　　means for sending, to a PCF, Dual 3GPP access support information indicating that a UE supports dual 3GPP access and ID of a UE, in a case where the AMF receives the Dual 3GPP access support information and first support information indicating that the UE supports for PNI-NPN as a network slice and dual 3GPP access; 　　means for receiving, from the PCF, an eURSP (enhanced URSP) rule for establishing Multi-Access / Dual-Steer PDU session; and 　　means for sending, to the UE, the eURSP rule. (Supplementary note 16) 　　A UE comprising: 　　means for sending, to an AMF, Dual 3GPP access support information indicating that the UE supports dual 3GPP access and first support information indicating that the UE supports for PNI-NPN as a network slice and dual 3GPP access; and 　　means for receiving, from the AMF, an eURSP rule for establishing Multi-Access / Dual-Steer PDU session. (Supplementary note 17) 　　An AMF comprising: 　　means for receiving, from a UE, first support information indicating that the UE supports for PNI-NPN S-NSSAIs and requesting S-NSSAI in a case where PDU session establishment based on an eURSP rule is triggered; 　　means for selecting a SMF which supports for PNI-NPN S-NSSAIs, in a case where support of the UE for the S-NSSAI is verified; 　　means for receiving, from the SMF, a Dual Steer rule used for controlling traffic steering, switching and splitting of dual 3GPP access; and 　　means for sending, to the UE, the Dual Steer rule. (Supplementary note 18) 　　A UE comprising: 　　means for sending, to an AMF, first support information indicating that the UE supports for PNI-NPN S-NSSAIs and requesting S-NSSAI in a case where the UE triggers PDU session establishment based on an eURSP rule; and 　　means for receiving, from the AMF, a Dual Steer rule used for controlling traffic steering, switching and splitting of dual 3GPP access, in a case where support of the UE for the S-NSSAI is verified. (Supplementary note 19) 　　An AMF comprising: 　　means for receiving, from a UE, first support information indicating that the UE supports for PNI-NPN S-NSSAIs and requesting S-NSSAI and SAG information indicating a condition or a rule related to the use of the S-NSSAI by the UE, in a case where PDU session establishment based on an eURSP rule is triggered; 　　means for selecting a SMF which supports for PNI-NPN S-NSSAIs, in a case where support of the UE for the S-NSSAI and the SAG information are verified; 　　means for receiving, from the SMF, a Dual Steer rule used for controlling traffic steering, switching and splitting of dual 3GPP access; and 　　means for sending, to the UE, the Dual Steer rule. (Supplementary note 20) 　　A UE comprising: 　　means for sending, to an AMF, first support information indicating that the UE supports for PNI-NPN S-NSSAIs and requesting S-NSSAI and SAG information indicating a condition or a rule related to the use of the S-NSSAI by the UE, in a case where the UE triggers PDU session establishment based on an eURSP rule; and 　　means for receiving, from the AMF, a Dual Steer rule used for controlling traffic steering, switching and splitting of dual 3GPP access, in a case where support of the UE for the S-NSSAI and the SAG information are verified. (Supplementary note 21) 　　An AMF comprising: 　　means for receiving, from a PCF, a dual steer rule of dual 3GPP access for a UE that is updated based on a request from an AF; and 　　means for sending, to the UE, the dual steer rule, 　　wherein the dual steer rule is included in an eURSP rule. (Supplementary note 22) 　　A UE comprising: 　　means for performing a registration procedure with an AMF; and 　　means for receiving, from the AMF, a dual steer rule of dual 3GPP access for the UE, in a case where the dual steer rule is updated based on a request from an AF, 　　wherein the dual steer rule is included in an eURSP rule. (Supplementary note 23) 　　An AMF comprising: 　　means for receiving, from a SMF, an updated dual steer rule of dual 3GPP access derived based on a request from an AF; and 　　means for sending, to a UE, the updated dual steer rule. (Supplementary note 24) 　　A UE comprising: 　　means for performing a PDU session establishment procedure with an AMF; and 　　means for receiving, from the AMF, an updated dual steer rule of dual 3GPP access derived in a case where the updated dual steer rule is derived based on a request from an AF.

[0237] 1　　system 20　　data network 201　　AF 3　　UE 31, 51, 601, 611, 621, 701, 711, 721, 731, 741, 751, 761, 771, 781, 791, 2011　　transceiver circuit 32, 52, 602　　antenna 53, 603, 612, 622, 702, 712, 722, 732, 742, 752, 762, 772, 782, 792, 2012　　network interface 33, 54, 604, 613, 623, 703, 713, 723, 733, 743, 753, 763, 773, 783, 793, 2013　　controller 34　　user interface 35　　USIM 36, 55, 605, 614, 624, 704, 714, 724, 734, 744, 754, 764, 774, 784, 794, 2014　　memory 361, 551, 6051, 6141, 6241, 7041, 7141, 7341, 7441, 7541, 7641, 7741, 7841, 7941, 20141　　operating system 362, 552, 6052, 6142, 6242, 7042, 7142, 7242, 7342, 7442, 7542, 7642, 7742, 7842,7942,20142　　communication control module 3621, 5521, 60521, 61421, 62421, 70421, 71421, 72421, 73421, 74421, 75421, 76421, 77421, 78421, 79421, 201421　　transceiver control module 5　　(R)AN node 501　　RAN MN 502　　RAN SN 60　　RU 61　　DU 62　　CU 7　　core network 70　　AMF 71　　SMF 72　　UPF 73　　PCF 74　　NWDAF 75　　UDM 76　　NSSF 77　　NSACF 78　　AUSF 79　　NEF

Claims

1. A method of a UE comprising: 　　establishing two 3GPP accesses; and 　　determining whether to reduce amount of traffic sent over one access among the two 3GPP accesses or to duplicate the traffic or to switch the traffic, based on a maximum measured value of a first parameter and a threshold value of the first parameter.

2. A method of a UPF comprising: 　　communicating with a UE establishing two 3GPP accesses; and 　　determining whether to reduce amount of traffic sent over one access among the two 3GPP accesses or to duplicate the traffic or to switch the traffic, based on a maximum measured value of a first parameter and a threshold value of the first parameter.

3. A method of an AMF comprising: 　　sending, to a PCF, Dual 3GPP access support information indicating that a UE supports dual 3GPP access and ID of a UE, in a case where the AMF receives the Dual 3GPP access support information and first support information indicating that the UE supports for PNI-NPN as a network slice and dual 3GPP access; 　　receiving, from the PCF, an eURSP (enhanced URSP) rule for establishing Multi-Access / Dual-Steer PDU session; and 　　sending, to the UE, the eURSP rule.

4. A method of a UE comprising: 　　sending, to an AMF, Dual 3GPP access support information indicating that the UE supports dual 3GPP access and first support information indicating that the UE supports for PNI-NPN as a network slice and dual 3GPP access; and 　　receiving, from the AMF, an eURSP rule for establishing Multi-Access / Dual Steer PDU session.

5. A method of an AMF comprising: 　　receiving, from a UE, first support information indicating that the UE supports for PNI-NPN S-NSSAIs and requesting S-NSSAI in a case where PDU session establishment based on an eURSP rule is triggered; 　　selecting a SMF which supports for PNI-NPN S-NSSAIs, in a case where support of the UE for the S-NSSAI is verified; 　　receiving, from the SMF, a Dual Steer rule used for controlling traffic steering, switching and splitting of dual 3GPP access; and 　　sending, to the UE, the Dual Steer rule.

6. A method of a UE comprising: 　　sending, to an AMF, first support information indicating that the UE supports for PNI-NPN S-NSSAIs and requesting S-NSSAI in a case where the UE triggers PDU session establishment based on an eURSP rule; and 　　receiving, from the AMF, a Dual Steer rule used for controlling traffic steering, switching and splitting of dual 3GPP access, in a case where support of the UE for the S-NSSAI is verified.

7. A method of an AMF comprising: 　　receiving, from a UE, first support information indicating that the UE supports for PNI-NPN S-NSSAIs and requesting S-NSSAI and SAG information indicating a condition or a rule related to the use of the S-NSSAI by the UE, in a case where PDU session establishment based on an eURSP rule is triggered; 　　selecting a SMF which supports for PNI-NPN S-NSSAIs, in a case where support of the UE for the S-NSSAI and the SAG information are verified; 　　receiving, from the SMF, a Dual Steer rule used for controlling traffic steering, switching and splitting of dual 3GPP access; and 　　sending, to the UE, the Dual Steer rule.

8. A method of a UE comprising: 　　sending, to an AMF, first support information indicating that the UE supports for PNI-NPN S-NSSAIs and requesting S-NSSAI and SAG information indicating a condition or a rule related to the use of the S-NSSAI by the UE, in a case where the UE triggers PDU session establishment based on an eURSP rule; and 　　receiving, from the AMF, a Dual Steer rule used for controlling traffic steering, switching and splitting of dual 3GPP access, in a case where support of the UE for the S-NSSAI and the SAG information are verified.

9. A method of an AMF comprising: 　　receiving, from a PCF, a dual steer rule of dual 3GPP access for a UE that is updated based on a request from an AF; and 　　sending, to the UE, the dual steer rule, 　　wherein the dual steer rule is included in an eURSP rule.

10. A method of a UE comprising: 　　performing a registration procedure with an AMF; and 　　receiving, from the AMF, a dual steer rule of dual 3GPP access for the UE, in a case where the dual steer rule is updated based on a request from an AF, 　　wherein the dual steer rule is included in an eURSP rule.

11. A method of an AMF comprising: 　　receiving, from a SMF, an updated dual steer rule of dual 3GPP access derived based on a request from an AF; and 　　sending, to a UE, the updated dual steer rule.

12. A method of a UE comprising: 　　performing a PDU session establishment procedure with an AMF; and 　　receiving, from the AMF, an updated dual steer rule of dual 3GPP access derived in a case where the updated dual steer rule is derived based on a request from an AF.

13. A UE comprising: 　　means for establishing two 3GPP accesses; and 　　means for determining whether to reduce amount of traffic sent over one access among the two 3GPP accesses or to duplicate the traffic or to switch the traffic, based on a maximum measured value of a first parameter and a threshold value of the first parameter.

14. A UPF comprising: 　　means for communicating with a UE establishing two 3GPP accesses; and 　　means for determining whether to reduce amount of traffic sent over one access among the two 3GPP accesses or to duplicate the traffic or to switch the traffic, based on a maximum measured value of a first parameter and a threshold value of the first parameter.

15. An AMF comprising: 　　means for sending, to a PCF, Dual 3GPP access support information indicating that a UE supports dual 3GPP access and ID of a UE, in a case where the AMF receives the Dual 3GPP access support information and first support information indicating that the UE supports for PNI-NPN as a network slice and dual 3GPP access; 　　means for receiving, from the PCF, an eURSP (enhanced URSP) rule for establishing Multi-Access / Dual-Steer PDU session; and 　　means for sending, to the UE, the eURSP rule.

16. A UE comprising: 　　means for sending, to an AMF, Dual 3GPP access support information indicating that the UE supports dual 3GPP access and first support information indicating that the UE supports for PNI-NPN as a network slice and dual 3GPP access; and 　　means for receiving, from the AMF, an eURSP rule for establishing Multi-Access / Dual-Steer PDU session.

17. An AMF comprising: 　　means for receiving, from a UE, first support information indicating that the UE supports for PNI-NPN S-NSSAIs and requesting S-NSSAI in a case where PDU session establishment based on an eURSP rule is triggered; 　　means for selecting a SMF which supports for PNI-NPN S-NSSAIs, in a case where support of the UE for the S-NSSAI is verified; 　　means for receiving, from the SMF, a Dual Steer rule used for controlling traffic steering, switching and splitting of dual 3GPP access; and 　　means for sending, to the UE, the Dual Steer rule.

18. A UE comprising: 　　means for sending, to an AMF, first support information indicating that the UE supports for PNI-NPN S-NSSAIs and requesting S-NSSAI in a case where the UE triggers PDU session establishment based on an eURSP rule; and 　　means for receiving, from the AMF, a Dual Steer rule used for controlling traffic steering, switching and splitting of dual 3GPP access, in a case where support of the UE for the S-NSSAI is verified.

19. An AMF comprising: 　　means for receiving, from a UE, first support information indicating that the UE supports for PNI-NPN S-NSSAIs and requesting S-NSSAI and SAG information indicating a condition or a rule related to the use of the S-NSSAI by the UE, in a case where PDU session establishment based on an eURSP rule is triggered; 　　means for selecting a SMF which supports for PNI-NPN S-NSSAIs, in a case where support of the UE for the S-NSSAI and the SAG information are verified; 　　means for receiving, from the SMF, a Dual Steer rule used for controlling traffic steering, switching and splitting of dual 3GPP access; and 　　means for sending, to the UE, the Dual Steer rule.

20. A UE comprising: 　　means for sending, to an AMF, first support information indicating that the UE supports for PNI-NPN S-NSSAIs and requesting S-NSSAI and SAG information indicating a condition or a rule related to the use of the S-NSSAI by the UE, in a case where the UE triggers PDU session establishment based on an eURSP rule; and 　　means for receiving, from the AMF, a Dual Steer rule used for controlling traffic steering, switching and splitting of dual 3GPP access, in a case where support of the UE for the S-NSSAI and the SAG information are verified.

21. An AMF comprising: 　　means for receiving, from a PCF, a dual steer rule of dual 3GPP access for a UE that is updated based on a request from an AF; and 　　means for sending, to the UE, the dual steer rule, 　　wherein the dual steer rule is included in an eURSP rule.

22. A UE comprising: 　　means for performing a registration procedure with an AMF; and 　　means for receiving, from the AMF, a dual steer rule of dual 3GPP access for the UE, in a case where the dual steer rule is updated based on a request from an AF, 　　wherein the dual steer rule is included in an eURSP rule.

23. An AMF comprising: 　　means for receiving, from a SMF, an updated dual steer rule of dual 3GPP access derived based on a request from an AF; and 　　means for sending, to a UE, the updated dual steer rule.

24. A UE comprising: 　　means for performing a PDU session establishment procedure with an AMF; and 　　means for receiving, from the AMF, an updated dual steer rule of dual 3GPP access derived in a case where the updated dual steer rule is derived based on a request from an AF.

Images