Method for radio station, method for core network node and core network node

Abstract

An aspect of this disclosure includes a method of a ration satiation. The method includes receiving, from a User Equipment (UE), at least one of information for identification related to UE capability, information for indirect network sharing support indicator, and information for identification of a Public Land Mobile Network (PLMN) that assigns the information for identification related to UE capability. The method includes sending, to a core network node, at least one of the information for the identification related to UE capability, the information for indirect network sharing support, and the information for identification of a Public Land Mobile Network (PLMN) that assigns the information for identification related to UE The method includes receiving, from the core network node, at least one of information for the identification related to UE capability, information for 5G Globally Unique Temporary Identifier (5G-GUTI), and the information for identification of a Public Land Mobile Network (PLMN) that assigns the information for identification related to UE capability. The method includes sending, to the UE, at least one of the information for 5G-GUTI information for identification related to UE capability, and the information for identification of a Public Land Mobile Network (PLMN) that assigns the information for identification related to UE capability.

Description

METHOD FOR RADIO STATION, METHOD FOR CORE NETWORK NODE AND CORE NETWORK NODE

[0001] The present disclosure related to a method for a radio station, a method for a core network node, a method for a first radio station, a method for a second radio station, a method for a master radio station, a method for a first core network node, a method for a second core network node, a method for a third core network node, and a method for a user equipment.

[0002] When developing network sharing (e.g. MOCN), one of the challenges for the partners' network operators is related with the maintenance generated by the interconnection (e.g., number of network interfaces) between the shared RAN and two or more core networks, especially for a very large number of shared base station. 　　An indirect network sharing is developed in 3GPP to configure network sharing easily and dynamically with less maintenance efforts.

[0003] In this disclosure, an operator that has operational control of a Shared RAN is called a hosting operator. An operator that are authorized to use shared RAN resources provided by the hosting operator is called a participating operator.

[0004] NPL 1: [1] 3GPP TR 21.905: "Vocabulary for 3GPP Specifications". V18.0.0 (2024-03) NPL 2: [2] 3GPP TS 23.501: "System architecture for the 5G System (5GS)". V19.2.1 (2025-01) NPL 3: [3] 3GPP TS 23.502: "Procedures for the 5G System (5GS)". V19.2.0 (2024-12) NPL 4: [4] 3GPP TS 23.503: "Policy and charging control framework for the 5G System (5GS) Stage 2". V19.2.0 (2024-12) NPL 5: [5] 3GPP TS 23.003: "Numbering, addressing and identification". V19.1.0 (2024-12) NPL 6: [6] 3GPP TS 37.340: "Multi-connectivity; Overall Description; Stage 2". V18.4.0 (2024-12) NPL 7: [7] 3GPP TS 38.413: "NG-RAN; NG Application Protocol (NGAP)". V18.4.0 (2024-12) NPL 8: [8] 3GPP TS 38.423: "NG-RAN; Xn application protocol (XnAP)". V18.4.0 (2024-12) NPL 9: [9] 3GPP TS 38.331: "NR Radio Resource Control (RRC) protocol specification". V18.4.0 (2024-12) NPL 10:

[0010] 3GPP TS 36.331: "Evolved Universal Terrestrial Radio Access (E-UTRA) Radio Resource Control (RRC) Protocol specification". V18.4.0 (2024-12)

[0005] It is unclear what configuration or structure is required for the Radio Capabilities Signaling optimization (RACS) to operate in the indirect network sharing environment.

[0006] The disclosure has a method for a radio station in a hosting operator network comprising receiving, from a User Equipment (UE), at least one of information for identification related to UE capability, information for indirect network sharing support indicator, and information for identification of a Public Land Mobile Network (PLMN) that assigns the information for identification related to UE capability, sending, to a core network node, at least one of the information for the identification related to UE capability, the information for indirect network sharing support, and the information for identification of a Public Land Mobile Network (PLMN) that assigns the information for identification related to UE, receiving, from the core network node, at least one of information for the identification related to UE capability, information for 5G Globally Unique Temporary Identifier (5G-GUTI), and the information for identification of a Public Land Mobile Network (PLMN) that assigns the information for identification related to UE capability; and sending, to the UE, at least one of the information for 5G-GUTI information for identification related to UE capability, and the information for identification of a Public Land Mobile Network (PLMN) that assigns the information for identification related to UE capability.

[0007] The disclosure has a method for a core network node in a hosting operator network comparing receiving, from a radio station, at least one of information for identification related to UE capability, information for indirect network sharing support indicator, and information for identification of a Public Land Mobile Network (PLMN) that assigns the information for identification related to UE capability, sending, to a Unified Data Management Function (UDM) in a participating operator network, a message related to a registration procedure, receiving, from the UDM, a response message to the message relate to the registration procedure; and sending, to the radio station, at least one of the information for the identification related to UE capability, information for 5G Globally Unique Temporary Identifier (5G-GUTI), and the information for identification of a Public Land Mobile Network (PLMN) that assigns the information for identification related to UE capability.

[0008] The disclosure has a method for a radio station in a hosting operator network comprising receiving from a core network node in the hosting operator network, at least one of information for User Equipment (UE) capability inquiry and information for identification related to a Public Land Mobile Network (PLMN) of a host operator, deciding to perform a UE capability inquiry procedure, sending, to the User Equipment (UE), a message related to the UE capability inquiry, receiving, from the UE, at least one of information for identification related to UE capability and the information for identification related to a Public Land Mobile Network (PLMN) of a host operator; and sending, to the core network node, the information for identification related to UE capability and the information for identification related to a Public Land Mobile Network (PLMN) of a host operator.

[0009] The disclosure has a method for a core network node in a hosting operator network comprising sending, to a radio station in the hosting operator network, at least one of information for User Equipment (UE) capability inquiry and information for identification related to a Public Land Mobile Network (PLMN) of a host operator; and receiving, from the radio station, at least one of information for identification related to UE capability and the information for identification related to a Public Land Mobile Network (PLMN)of a host operator.

[0010] The disclosure has a method for a first radio station in a hosting operator network comprising deciding to initiate a handover procedure, sending, to a second radio station in the hosting operator network, a handover request message including at least one of information for 5G Globally Unique Temporary Identifier (5G-GUTI) and information for identification of a Public Land Mobile Network (PLMN) that assigns information for identification related to UE capability; and receiving, from the second radio station, an acknowledgement message in response to the handover request message.

[0011] The disclosure has a method for a second radio station in a hosting operator network comprising receiving, from a first radio station, a handover request message including at least one of information for 5G Globally Unique Temporary Identifier (5G-GUTI) and information for identification of a Public Land Mobile Network (PLMN) that assigns information for identification related to UE capability, sending, to the first radio station, an acknowledgement message in response to the handover request message, sending, to a core network node in a hosting operator network, a request message related to a path switch: and receiving, from the core network node, an acknowledgement message in response to the request message related to the path switch, wherein the acknowledgement message in response to the request message related to the path switch includes at least one of information for 5G Globally Unique Temporary Identifier (5G-GUTI) and information for identification of a Public Land Mobile Network (PLMN) that assigns nformation for identification related to UE capability.

[0012] The disclosure has a method for a core network node in a hosting operator network comprising receiving, from a second radio station in the hosting operator network, a request message related to a path switch: and sending, to the second radio station, an acknowledgement message in response to the request message related to the path switch, wherein the acknowledgement message in response to the request message related to the path switch includes at least one of information for 5G Globally Unique Temporary Identifier (5G-GUTI) and information for identification of a Public Land Mobile Network (PLMN) that assigns information for identification related to UE capability.

[0013] The disclosure has a method for a radio station in a hosting operator network comprising sending, to a core network node in the hosting operator network, a request message related to a User Equipment (UE) capability identification mapping; and receiving, from the core network node, a response message relate to the UE capability identification mapping, wherein the request message includes information for identification of a Public Land Mobile Network (PLMN) that assigns information for identification related to UE capability, wherein the response message includes information for UE capability for paging.

[0014] The disclosure has a method for a core network node in a hosting operator network comprising receiving, from a radio station in the hosting operator network, a request message related to a User Equipment (UE) capability identification mapping, sending, to a Network Repository Function (NRF) in the hosting operator network, a request message related to a Network Function (NF) discovery including information for identification related to a Public Land Mobile Network (PLMN), receiving, from the NRF, a response message in response to the request message related to the NF discovery, sending, to a UE radio Capability management Function (UCMF) in the hosting operator network, a message related to UE capability management including information for identification related to UE capability, receiving, from the UCMF, a response message in response to the message relate to UE capability management; and sending, to the radio station, a response message relate to the UE capability identification mapping, wherein the request message related to a User Equipment (UE) capability identification mapping including information for identification of a Public Land Mobile Network (PLMN) that assigns information for identification related to UE capability, wherein the response message relate to the UE capability identification mapping including information for UE capability for paging.

[0015] The disclosure has a method for a master radio station in a hosting operator network comprising deciding to perform a secondary radio station addition procedure, sending, to the secondary radio station, a request message related to the secondary radio station addition procedure; and receiving, from the secondary radio station, an acknowledgement request in response to the request message, wherein the request message includes at least one of information for Globally Unique AMF Identifier (GUAMI), information for 5G Globally Unique Temporary Identifier (5G-GUTI), and information for identification of a Public Land Mobile Network (PLMN) that assigns information for identification related to UE capability.

[0016] The disclosure has a method for a radio station in a participating operator network comprising receiving, from a User Equipment (UE), a Radio Resource Control (RRC) message including at least one of information for identification related to UE capability, information for indirect network sharing support indicator, and information for identification of a Public Land Mobile Network (PLMN) that assigns the information for identification related to UE capability; and sending, to a core network node in a participating operator network, at least one of the information for indirect network sharing support indicator, and the information for identification of a Public Land Mobile Network (PLMN) that assigns the information for identification related to UE capability based on the RRC message.

[0017] The disclosure has a method for a first core network node in a participating operator network comprising deciding whether information for identification related to UE capabilityneeds to be updated, sending, to a second core network node in the participating operator network, a request message related to Network Function (NF) discovery including information for identification related to a Public Land Mobile Network (PLMN) of a host operator; and receiving, from the second core network node, a response message in response to the request message, sending, to a third core network node in the participating operator network, a message related to a User Equipment (UE) capability management, receiving, from the third core network node, a response message related to the UE capability management; and sending, to a radio station in the participating operator network, at least one of information for 5G-GUTI and the information for identification of a Public Land Mobile Network (PLMN) that assigns the information for identification related to UE capability.

[0018] The disclosure has a method for a second core network node in a participating operator network comprising receiving, from a first core network node in the participating operator network, a request message related to Network Function (NF) discovery including information for identification related to a Public Land Mobile Network (PLMN) of a host operator; and sending, to the first core network node, a response message in response to the request message.

[0019] The disclosure has a method for a core network node in a hosting operator network comprising setting information for identification related to a Public Land Mobile Network (PLMN) of a participating network, sending, to a Network Repository Function (NRF) in a participating operator network, a request message related to a Network Function (NF) discovery including the information for identification related to a Public Land Mobile Network (PLMN) of the participating network, receiving, from the NRF, a response message in response to the request message relate to the NF discovery, sending, to a UE radio Capability Management Function (UCMF) in the participating operator network, a message related to a User Equipment (UE) capability management, receiving, from the UCMF, a response message related to the UE capability management; and sending, to a radio station in a hosting operator network, at least one of information for 5G-GUTI and the information for identification of a Public Land Mobile Network (PLMN) that assigns information for identification related to UE capability.

[0020] The disclosure has a method for a core network node in a hosting operator network comprising receiving, from a radio station in the hosting operator network, a request message related to a User Equipment (UE) capability identification mapping, sending, to a Network Repository Function (NRF) in a participating operator network, a request message related to a Network Function (NF) discovery including information for identification related to a Public Land Mobile Network (PLMN), receiving, from the NRF, a response message in response to the request message related to the NF discovery, sending, to a UE radio Capability Management Function (UCMF) in the participating operator network, a message related to UE capability management including information for identification related to UE capability, receiving, from the UCMF, a response message in response to the message relate to the UE capability management; and sending, to the radio station, a response message relate to the UE capability identification mapping, wherein the request message related to a User Equipment (UE) capability identification mapping including information for identification of a Public Land Mobile Network (PLMN) that assigns the information for identification related to UE capability, wherein the response message relate to the UE capability identification mapping including information for UE capability for paging.

[0021] The disclosure has a method for a first radio station comprising receiving, from a second radio station, a request message related to User Equipment (UE) context retrieve, sending, to the second radio station, a response message in response to the request message, wherein the response message includes at least one of information for identification of a Public Land Mobile Network (PLMN) that assigns information for identification related to UE capability.

[0022] The disclosure has a method for a first core network node in a first network comprisingcommunicating with a User Equipment (UE); and updating a UE Radio Capability Identity during mobility of the UE from the second core network node in a second network to the first core network node, wherein the first network operates as a participating operator network, wherein the second network operates as a hosting operator network.

[0023] The disclosure has a first core network node in a first network comprising means for communicating with a User Equipment (UE); and means for updating a UE Radio Capability Identity during mobility of the UE from the second core network node in a second network to the first core network node, wherein the first network operates as a participating operator network, wherein the second network operates as a hosting operator network.

[0024] Fig. 1 is a diagram illustrating an example architecture of this disclosure.Fig. 2 is an example signaling diagram of this disclosure.Fig. 3 is an example signaling diagram of this disclosure.Fig. 4 is an example signaling diagram of this disclosure.Fig. 5 is an example signaling diagram of this disclosure.Fig. 6 is an example signaling diagram of this disclosure.Fig. 7 is an example signaling diagram of this disclosure.Fig. 8 is an example signaling diagram of this disclosure.Fig. 9 is an example signaling diagram of this disclosure.Fig. 10 is an example signaling diagram of this disclosure.Fig. 11 is a diagram illustrating a system overview.Fig. 12 is a block diagram illustrating a UE.Fig. 13 is a block diagram illustrating an N3IWF.Fig. 14 is a block diagram illustrating a non-3GPP access.Fig. 15 is a block diagram illustrating an (R)AN node.Fig. 16 is a diagram illustrating System overview of (R)AN node based on O-RAN architecture.Fig. 17 is a block diagram illustrating an RU.Fig. 18 is a block diagram illustrating a DU.Fig. 19 is a block diagram illustrating a CU.Fig. 20 is a block diagram illustrating an AMF.Fig. 21 is a block diagram illustrating an SMF.Fig. 22 is a block diagram illustrating a UPF.Fig. 23 is a block diagram illustrating a PCF.Fig. 24 is a block diagram illustrating an NWDAF.Fig. 25 is a block diagram illustrating a UDM.Fig. 26 is a block diagram illustrating an AUSF.Fig. 27 is a block diagram illustrating an UCMF.Fig. 28 is a block diagram illustrating an NRF.Fig. 29 is a block diagram illustrating an NEF.Fig. 30 is a block diagram illustrating a UDR.Fig. 31 is a block diagram illustrating an OAM.Fig. 32 is a block diagram illustrating an AF.

[0025] <Abbreviations> 　　For the purposes of the present document, the abbreviations given in 3GPP TR 21.905 [1] and the following apply. An abbreviation defined in the present document takes precedence over the definition of the same abbreviation, if any, in 3GPP TR 21.905 [1]. 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 AAnF　　AKMA Anchor Function ABBA　　Anti-Bidding down Between Architectures AF　　Application Function A-KID　　AKMA Key Identifier AKMA　　Authentication and Key Management for Applications AMBR　　Aggregated Maximum Bit Rate 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 AP　　Authentication Proxy AR　　Augmented Reality ARFCN　　Absolute radio-frequency channel number AS　　Access Stratum ASN　　Abstract Syntax Notation A-TID　　AKMA Temporary UE Identifier 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 CDR　　Charging Data Record CHF　　Charging Function CN PDB　　Core Network Packet Delay Budget CP　　Control Plane CSG　　Closed Subscriber Group DAPS　　Dual Active Protocol Stacks DL　　Downlink DN　　Data Network DNAI　　DN Access Identifier DNN　　Data Network Name DRX　　Discontinuous Reception DSATSSS　　Dual Steer Access Traffic Steering, Switching, Splitting DSATSSS-LL　　Dual Steer Access Traffic Steering, Switching, Splitting- Low-Layer DSMA　　Dual Steer Multi Access DS-TT　　Device-side TSN translator ePDG　　evolved Packet Data Gateway EBI　　EPS Bearer Identity ECGI　　E-UTRAN Cell Global Identifier 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 GCI　　Global Cable Identifier GEO　　Geostationary Earth Orbit GFBR　　Guaranteed Flow Bit Rate GMLC　　Gateway Mobile Location Centre GNSS　　Global Navigation Satellite System G-PDU　　GTP encapsulated user Plane Data Unit GPS　　Global Positioning System GPSI　　Generic Public Subscription Identifier GSO　　Geosynchronous Orbit GUAMI　　Globally Unique AMF Identifier GUTI　　Globally Unique Temporary UE Identity HAPS　　High Altitude Platform Station HPLMN　　Home Public Land Mobile Network HR　　Home Routed (roaming) HSS　　Home Subscriber Server IAB　　Integrated access and backhaul IEC　　International Electrotechnical Commission IMEI / TAC　　IMEI Type Allocation Code IMSI　　International Mobile Subscriber Identity IPsec　　Internet Protocol Security IPUPS　　Inter PLMN UP Security I-RNTI　　Inactive-Radio Network Temporary Identifier I-SMF　　Intermediate SMF ISO　　International Organization for Standardization I-UPF　　Intermediate UPF KAF　　AKMA Application Key KAKMA　　AKMA Anchor Key LADN　　Local Area Data Network LBO　　Local Break Out (roaming) LCS　　Location Service LEO　　Low Earth Orbit LMF　　Location Management Function LoA　　Level of Automation LPP　　LTE Positioning Protocol LRF　　Location Retrieval Function LSB　　Least Significant Bit MA　　Multi Access MCC　　Mobile country code MCX　　Mission Critical Service MDBV　　Maximum Data Burst Volume ME　　Mobile Equipment MFBR　　Maximum Flow Bit Rate MIB　　Master Information Block 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 MNO　　Mobile Network Operator MO　　Mobile Originated MOCN　　Multiple Operator Core Network MPS　　Multimedia Priority Service MPTCP　　Multi-Path TCP Protocol MR　　Mixed Reality MSB　　Most Significant Bit MT　　Mobile Termination, Mobile Terminating, Mobile terminated N3IWF　　Non-3GPP InterWorking Function N3GPP　　Non-3GPP access N5CW　　Non-5G-Capable over WLAN NAI　　Network Access Identifier NAS　　Non-Access-Stratum NCGI　　NR Cell Global Identity NCI　　NR Cell Identity NEF　　Network Exposure Function NF　　Network Function NGAP　　Next Generation Application Protocol NGSO　　Non-Geosynchronous Orbit 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 NTN　　Non-Terrestrial Networks NW-TT　　Network-side TSN translator NWDAF　　Network Data Analytics Function OAM　　Operations, Administration, and Maintenance 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 QoS　　Quality of Service RACS　　Radio Capabilities Signaling optimization (R)AN　　(Radio) Access Network RAT　　Radio Access Technology RFID　　Radio Frequency Identification RG　　Residential Gateway RID　　Routing Indicator 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 RTT　　Round-Trip Time RVAS　　Roaming Value Added Service SA NR　　Standalone New Radio SBA　　Service Based Architecture SBI　　Service Based Interface SCP　　Service Communication Proxy S-CSCF　　Server - Call Session Control Function 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 SLA　　Service Level Agreement SMF　　Session Management Function SMS　　Short Message Service 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 TAC　　Tracking Area Code TAI　　Tracking Area Identity TAU　　Tracking Area Update TEID　　Tunnel Endpoint Identifier TMGI　　Temporary Mobile Group Identity 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 UCU　　UE Configuration Update 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 VR　　Virtual Reality 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 WPT　　Wireless Power Transfer

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

[0027] <General> 　　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.

[0028] 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. 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.

[0029] 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.

[0030] 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.

[0031] 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.

[0032] 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.

[0033] Each of Aspects 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.

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

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

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

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

[0038] 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."

[0039] In this disclosure, the expression "A and / or B" may mean "A or B", "A and B", "at least one of A and B" etc.

[0040] Although this disclosure discloses a mechanism for the 5G, all mechanisms in this disclosure can equally apply to the 6G, EPS and / or any other system as well. In case all mechanisms in this disclosure are to apply to the EPS, the following terminology conversions apply: - gNB a eNodeB - AMF a MME - SMF a SGW or PGW or combined SGW and PGW - UPF a SGW-U or PGW-U or combined SGW-U and PGW-U - UDM a HSS - NGAP a S1AP - N2 reference point a S1-MME reference point - N3 reference point a S1-U reference point - N9 reference point a S5 or S8 reference point - N14 reference point a S10 reference point - RRC Setup Request a RRC Connection Setup Request - RRC Setup a RRC Connection Setup - RRC Setup Complete a RRC Connection Setup Complete - NG SETUP REQUET message a S1 SETUP REQUEST message - NG SETUP RESPONSE message a S1 SETUP RESPONSE message - XN SETUP REQUET message a S2 SETUP REQUEST message - XN SETUP RESPONSE message a S2 SETUP RESPONSE message - AMF CONFIGURATION UPDATE message a MME CONFIGURATION UPDATE message - AMF CONFIGURATION UPDATE ACKNOWLEDGE a MME CONFIGURATION UPDATE ACKNOWLEDGE message - RAN CONFIGURATION UPDATE message a ENB CONFIGURATION UPDATE message - RAN CONFIGURATION UPDATE ACKNOWLEDGE a ENB CONFIGURATION UPDATE ACKNOWLEDGE message - S-NODE ADDITION REQUEST message a SENB ADDITION REQUEST message - Any NGAP messages a Respective S1AP messages - Registration Request message a Attach Request message or TAU Request message - Registration Accept message a Attach Accept message or TAU Accept message - Any AMF service-related messages (ex. Namf_Communication_NonUeN2InfoNotify) a GTP-C messages - Any UDM service-related messages (for example, Nudm_SDM_Notification) a DIAMETER messages - 5G-GUTI a GUTI - 5G-S-TMSI a S-TMSI - PDU Session ID a TEID or TEID and IP address

[0041] A user equipment (UE) according to example aspect of this disclosure includes at least one memory, and at least one hardware processor coupled to the at least one memory. The at least one hardware processor is configured to send a registration request message in a case where the UE is registered over 3GPP access through a hosting operator network using an Indirect network sharing in the hosting operator network and a participating operator network and the UE moves out an area of the Indirect network sharing. The registration request message is sent to an Access and Mobility Management Function (AMF) in the hosting operator network. The at least one hardware processor is configured to receive a registration reject message from the AMF. The registration reject message includes at least one of information indicating that an area where the UE is located is not a subject for the Indirect network sharing and information indicating that the UE is requested to perform Public Land Mobile Network (PLMN) selection. The at least one hardware processor is configured to perform the PLMN selection. The at least one hardware processor is configured to perform a registration procedure in the participating operator network.

[0042] A communication apparatus according to example aspect of this disclosure includes at least one memory, and at least one hardware processor coupled to the at least one memory. The at least one hardware processor is configured to receive a registration request message from a user equipment (UE) which is registered over 3GPP access through a hosting operator network using an Indirect network sharing in the hosting operator network and a participating operator network and which moves out an area of the Indirect network sharing. The communication apparatus is in the hosting operator network. The at least one hardware processor is configured to check that an area where the UE is located is not a subject for the Indirect network sharing. The at least one hardware processor is configured to send a registration reject message to the UE. The registration reject message includes at least one of information indicating that the area where the UE is located is not the subject for the Indirect network sharing and information indicating that the UE is requested to perform Public Land Mobile Network (PLMN) selection.

[0043] A user equipment (UE) according to example aspect of this disclosure includes at least one memory, and at least one hardware processor coupled to the at least one memory. The at least one hardware processor is configured to send a message in a case where the UE is registered over 3GPP access through a hosting operator network using an Indirect network sharing in the hosting operator network and a participating operator network and the UE moves out an area of the Indirect network sharing. The message includes information related to the participating operator network. The at least one hardware processor is configured to receive another message. Another message includes information indicating that the UE is requested to perform Public Land Mobile Network (PLMN) selection. The at least one hardware processor is configured to perform the PLMN selection. The at least one hardware processor is configured to perform a registration procedure in the participating operator network.

[0044] A communication apparatus according to example aspect of this disclosure includes at least one memory, and at least one hardware processor coupled to the at least one memory. The at least one hardware processor is configured to receive a message from a user equipment (UE) which is registered over 3GPP access through a hosting operator network using an Indirect network sharing in the hosting operator network and a participating operator network and which moves out an area of the Indirect network sharing. The message includes information related to the participating operator network. The at least one hardware processor is configured to send another message. Another message includes information indicating that the UE is requested to perform Public Land Mobile Network (PLMN) selection.

[0045] A user equipment (UE) according to example aspect of this disclosure includes at least one memory, and at least one hardware processor coupled to the at least one memory. The at least one hardware processor is configured to treat the UE as the UE is registered to a participating operator network in a case where the UE determines that the UE is registered over 3GPP access through a hosting operator network using an Indirect network sharing in the hosting operator network and the participating operator network. The at least one hardware processor is configured to perform a registration procedure in the participating operator network in a case where the UE moves out an area of the Indirect network sharing.

[0046] A user equipment (UE) according to example aspect of this disclosure includes at least one memory, and at least one hardware processor coupled to the at least one memory. The at least one hardware processor is configured to treat the UE as the UE is registered to a participating operator network in a case where the UE determines that the UE is registered over 3GPP access through a hosting operator network using an Indirect network sharing in the hosting operator network and the participating operator network. 5G Globally Unique Temporary Identifier (5G-GUTI) related to the participating operator network is assigned to the UE. The at least one hardware processor is configured to perform a registration procedure in the participating operator network based on Subscription Concealed Identifier (SUCI) instead of the 5G-GUTI in a case where the UE moves out an area of the Indirect network sharing.

[0047] A communication apparatus in a hosting operator network according to example aspect of this disclosure includes at least one memory, and at least one hardware processor coupled to the at least one memory. The at least one hardware processor is configured to communicate with a user equipment (UE). The at least one hardware processor is configured to assign 5G Globally Unique Temporary Identifier (5G-GUTI) related to a participating operator network to the UE during a registration procedure over 3GPP access through the hosting operator network using an Indirect network sharing in the hosting operator network and the participating operator network.

[0048] Example aspect of this disclosure includes a method of a Radio Access Network (RAN), Core Network (CN) and User Equipment (UE). The method includes mobility management in an indirect network sharing for cellular communication in 3GPP system.

[0049] Fig. 1 illustrates an example of target architecture that this disclosure applies to.

[0050] The UE 3 may be a subscriber or a user of the participating operator.

[0051] The UE 3 may be an inbound roamer to the participating operator where the participating operator has a roaming agreement with the UE 3's home network operator.

[0052] The hosting operator and the participating operator have an agreement to use the Indirect network sharing in certain area to provide cellular communication services to subscribers belonging to the participating operator network where the hosting operator has a coverage and can provide cellular communication services while the participating operator does not have a coverage and cannot provide cellular communication services directly.

[0053] In one another example, the hosting operator and the participating operator have an agreement to use the Indirect network sharing to provide cellular communication services to subscribers belonging to the participating operator network in case the participating operator network experiences failure situations.

[0054] The UE 3 belonging to the participating operator registers to the AMF 7001 in the hosting operator network to have cellular communication services that is provided through the participating operator network.

[0055] The hosting operator network may constitute of a network of the hosting operator or a network managed or operated by the hosting operator.

[0056] The participating operator network may constitute of a network of the participating operator or a network managed or operated by the participating operator.

[0057] The hosting operator may be expressed as a hosting RAN operator, a hosting NG-RAN operator, a hosting network operator or etc.

[0058] The participating operator may be expressed as a participating NG-RAN operator, a participating network operator or etc.

[0059] The hosting operator network may include RAN 504, S-RAN 502(e.g., Secondary-RAN 502) and M-RAN 503 (e.g., Master-RAN 503) and a hosting operator's core network. The hosting operator's core network may include at least one of the AMF 7001, UCMF 7701, NRF 7801 etc. participating operator's core network may include at least one of the AMF 7002, UDM 75, UCMF 7702, NRF 7802 etc.

[0060] The UCMF 7701 and the UCMF 7002 may have a reference interface between the hosting operator network and the participating operator network.

[0061] Alternatively, any NFs in the hosting network can access the UCMF 7002 in the participating operator network directly using the service-based interface as defined in 3GPP TS 23.502 [3].

[0062] In one example, The RAN 504 may be a standalone RAN without S-RAN 502.

[0063] The RAN 504 and the S-RAN 502 may configure a multi-connectivity as defined in 3GPP TS 37.340 [6].

[0064] The M-RAN 503 is illustrated in Fig. 1 to cover a scenario where the UE 3 performs handover. In this case, the RAN 504 is referred to as a source RAN and the M-RAN 503 is referred to as a target RAN.

[0065] The RAN 504 and the AMF 7002 are illustrated in Fig. 1 to cover scenarios where the UE 3 moves from the hosting operator network to the participating operator network or from the participating operator network to the hosting operator network due to UE mobility.

[0066] The AMF 7001 may communicate with the NRF 7802 via the NRF 7801. In this case, the NRF 7801 may be referred to as an NRF in VPLMN and the NRF 7802 may be referred to as a NRF in HPLMN.

[0067] In another example, although there is no connecting line illustrated between the AMF 7001 and NRF 7802 in Fig. 1, the AMF 7001 may directly communicate with the NRF 7802.

[0068] A method for a radio station in a hosting operator network according to example aspect of this disclosure includes receiving, from a User Equipment (UE), at least one of information for identification related to UE capability, information for indirect network sharing support indicator, and information for identification of a Public Land Mobile Network (PLMN) that assigns the information for identification related to UE capability. The method includes sending, to a core network node, at least one of the information for the identification related to UE capability, the information for indirect network sharing support, and the information for identification of a Public Land Mobile Network (PLMN) that assigns the information for identification related to UE The method includes receiving, from the core network node, at least one of information for the identification related to UE capability, information for 5G Globally Unique Temporary Identifier (5G-GUTI), and the information for identification of a Public Land Mobile Network (PLMN) that assigns the information for identification related to UE capability. The method includes sending, to the UE, at least one of the information for 5G-GUTI information for identification related to UE capability, and the information for identification of a Public Land Mobile Network (PLMN) that assigns the information for identification related to UE capability.

[0069] A method for a core network node in a hosting operator network according to example aspect of this disclosure includes receiving, from a radio station, at least one of information for identification related to UE capability, information for indirect network sharing support indicator, and information for identification of a Public Land Mobile Network (PLMN) that assigns the information for identification related to UE capability. The method includes sending, to a Unified Data Management Function (UDM) in a participating operator network, a message related to a registration procedure receiving, from the UDM, a response message to the message relate to the registration procedure. The method includes sending, to the radio station, at least one of the information for the identification related to UE capability, information for 5G Globally Unique Temporary Identifier (5G-GUTI), and the information for identification of a Public Land Mobile Network (PLMN) that assigns the information for identification related to UE capability.

[0070] A method for a core network node according to example aspect of this disclosure includes sending, to the radio station, a message related to a User Equipment (UE) capability check including at least one of information for User Equipment (UE) capability inquiry and information for identification related to a Public Land Mobile Network (PLMN))receiving, from the radio station, a message related to a UE capability identification including at least one of the. The method includes setting the information for identification related to a Public Land Mobile Network (PLMN) of a host operator. The method includes sending, to a Network Repository Function (NRF) in the hosting operator network, a message related to Network Function (NF) discovery including the information for identification related to the PLMN of the host operator of the host operator. The method includes receiving, from the NRF, a response message to the message related to the NF discovery including a NF profile. The method includes sending, to a UE radio Capability Management Function (UCMF) in the hosting operator network, a message related to a UE capability management. The method includes receiving, from the UCMF, a response message related to the UE capability management including the information for identification related to UE capability.

[0071] A method for a radio station in a hosting operator network according to example aspect of this disclosure includes receiving from a core network node in the hosting operator network, at least one of information for User Equipment (UE) capability inquiry and information for identification related to a Public Land Mobile Network (PLMN) of a host operator. The method includesdeciding to perform a UE capability inquiry procedure. The method includes sending, to the User Equipment (UE), a message related to the UE capability inquiry. The method includes receiving, from the UE, at least one of information for identification related to UE capability and the information for identification related to a Public Land Mobile Network (PLMN) of a host operator. The method includes sending, to the core network node, the information for identification related to UE capability and the information for identification related to a Public Land Mobile Network (PLMN) of a host operator.

[0072] A method for a core network node in a hosting operator network according to example aspect of this disclosure includes sending, to a radio station in the hosting operator network, at least one of information for User Equipment (UE) capability inquiry and information for identification related to a Public Land Mobile Network (PLMN) of a host operator. The method includes receiving, from the radio station, at least one of information for identification related to UE capability and the information for identification related to a Public Land Mobile Network (PLMN)of a host operator.

[0073] A method for a first radio station in a hosting operator network according to example aspect of this disclosure includes deciding to initiate a handover procedure. The method includes sending, to a second radio station in the hosting operator network, a handover request message including at least one of information for 5G Globally Unique Temporary Identifier (5G-GUTI) and information for identification of a Public Land Mobile Network (PLMN) that assigns information for identification related to UE capability. The method includes receiving, from the second radio station, an acknowledgement message in response to the handover request message.

[0074] A method for a second radio station in a hosting operator network according to example aspect of this disclosure includes receiving, from a first radio station, a handover request message including at least one of information for 5G Globally Unique Temporary Identifier (5G-GUTI) and information for identification of a Public Land Mobile Network (PLMN) that assigns information for identification related to UE capability. The method includes sending, to the first radio station, an acknowledgement message in response to the handover request message. The method includes sending, to a core network node in a hosting operator network, a request message related to a path switch. The method includes receiving, from the core network node, an acknowledgement message in response to the request message related to the path switch, wherein the acknowledgement message in response to the request message related to the path switch includes at least one of information for 5G Globally Unique Temporary Identifier (5G-GUTI) and information for identification of a Public Land Mobile Network (PLMN) that assigns the information for identification related to UE capability.

[0075] A method for a core network node in a hosting operator network according to example aspect of this disclosure includes receiving, from a second radio station in the hosting operator network, a request message related to a path switch. The method includes sending, to the second radio station, an acknowledgement message in response to the request message related to the path switch, wherein the acknowledgement message in response to the request message related to the path switch includes at least one of information for 5G Globally Unique Temporary Identifier (5G-GUTI) and information for identification of a Public Land Mobile Network (PLMN) that assigns information for identification related to UE capability.

[0076] A method for a radio station in a hosting operator network according to example aspect of this disclosure includes sending, to a core network node in the hosting operator network, a request message related to a User Equipment (UE) capability identification mapping. The method includes receiving, from the core network node, a response message related to the UE capability identification mapping, wherein the request message includes information for identification of a Public Land Mobile Network (PLMN) that assigns information for identification related to UE capability, wherein the response message includes information for UE capability for paging.

[0077] A method for a core network node in a hosting operator network according to example aspect of this disclosure includes receiving, from a radio station in the hosting operator network, a request message related to a User Equipment (UE) capability identification mapping. The method includes sending, to a Network Repository Function (NRF) in the hosting operator network, a request message related to a Network Function (NF) discovery including information for identification related to a Public Land Mobile Network (PLMN). The method includes receiving, from the NRF, a response message in response to the request message related to the NF discovery. The method includes sending, to a UE radio Capability management Function (UCMF) in the hosting operator network, a message related to UE capability management including information for identification related to UE capability. The method includes receiving, from the UCMF, a response message in response to the message relate to UE capability management. The method includes sending, to the radio station, a response message relate to the UE capability identification mapping, wherein the request message related to a User Equipment (UE) capability identification mapping including information for identification of a Public Land Mobile Network (PLMN) that assigns information for identification related to UE capability, wherein the response message relate to the UE capability identification mapping including information for UE capability for paging.

[0078] A method for a master radio station in a hosting operator network according to example aspect of this disclosure includes deciding to perform a secondary radio station addition procedure. The method includes sending, to the secondary radio station, a request message related to the secondary radio station addition procedure. The method includes receiving, from the secondary radio station, an acknowledgement request in response to the request message, wherein the request message includes at least one of information for Globally Unique AMF Identifier (GUAMI), information for 5G Globally Unique Temporary Identifier (5G-GUTI), and information for identification of a Public Land Mobile Network (PLMN) that assigns information for identification related to UE capability.

[0079] A method for a radio station in a participating operator network according to example aspect of this disclosure includes receiving, from a User Equipment (UE), a Radio Resource Control (RRC) message including at least one of information for identification related to UE capability, information for indirect network sharing support indicator, and information for identification of a Public Land Mobile Network (PLMN) that assigns the information for identification related to UE capability. The method includes sending, to a core network node in a participating operator network, at least one of the information for indirect network sharing support indicator, and the information for identification of a Public Land Mobile Network (PLMN) that assigns the information for identification related to UE capability based on the RRC message.

[0080] A method for a first core network node in a participating operator network according to example aspect of this disclosure includes deciding whether information for identification related to UE capability needs to be updated. The method includes sending, to a second core network node in the participating operator network, a request message related to Network Function (NF) discovery including information for identification related to a Public Land Mobile Network (PLMN) of a host operator. The method includes receiving, from the second core network node, a response message in response to the request message. The method includes sending, to a third core network node in the participating operator network, a message related to a User Equipment (UE) capability management. The method includes receiving, from the third core network node, a response message related to the UE capability management. The method includes sending, to a radio station in the participating operator network, at least one of information for 5G-GUTI and the information for identification of a Public Land Mobile Network (PLMN) that assigns the information for identification related to UE capability.

[0081] A method for a second core network node in a participating operator network according to example aspect of this disclosure includes receiving, from a first core network node in the participating operator network, a request message related to Network Function (NF) discovery including information for identification related to a Public Land Mobile Network (PLMN) of a host operator. The method includes sending, to the first core network node, a response message in response to the request message.

[0082] A method for a core network node in a hosting operator network according to example aspect of this disclosure includes setting information for identification related to a Public Land Mobile Network (PLMN) of a participating network. The method includes sending, to a Network Repository Function (NRF) in a participating operator network, a request message related to a Network Function (NF) discovery including the information for identification related to a Public Land Mobile Network (PLMN) of the participating network. The method includes receiving, from the NRF, a response message in response to the request message relate to the NF discovery. The method includes sending, to a UE radio Capability Management Function (UCMF) in the participating operator network, a message related to a User Equipment (UE) capability management. The method includes receiving, from the UCMF, a response message related to the UE capability management. The method includes sending, to a radio station in a hosting operator network, at least one of information for 5G-GUTI and the information for identification of a Public Land Mobile Network (PLMN) that assigns information for identification related to UE capability.

[0083] A method for a core network node in a hosting operator network according to example aspect of this disclosure includes receiving, from a radio station in the hosting operator network, a request message related to a User Equipment (UE) capability identification mapping. The method includes sending, to a Network Repository Function (NRF) in a participating operator network, a request message related to a Network Function (NF) discovery including information for identification related to a Public Land Mobile Network (PLMN). The method includes receiving, from the NRF, a response message in response to the request message related to the NF discovery. The method includes sending, to a UE radio Capability Management Function (UCMF) in the participating operator network, a message related to UE capability management including information for identification related to UE capability. The method includes receiving, from the UCMF, a response message in response to the message relate to the UE capability management. The method includes sending, to the radio station, a response message relate to the UE capability identification mapping, wherein the request message related to a User Equipment (UE) capability identification mapping including information for identification of a Public Land Mobile Network (PLMN) that assigns the information for identification related to UE capability, wherein the response message relate to the UE capability identification mapping including information for UE capability for paging.

[0084] A method for a first radio station according to example aspect of this disclosure includes receiving, from a second radio station, a request message related to User Equipment (UE) context retrieve.

[0085] The method includes sending, to the second radio station, a response message in response to the request message, wherein the response message includes at least one of information for identification of a Public Land Mobile Network (PLMN) that assigns information for identification related to UE capability.

[0086] <First Aspect> 　　In case that the RACS function is deployed in the indirect network sharing environment, it is not clear which operator, the hosting operator or the participating operator assigns a UE Radio Capability ID for those of UEs which belong to the participating operator.

[0087] In addition, it is also not clear how the RAN manages an operator ID (I.E. PLMN ID) that assigns the UE Radio Capability ID to the UE 3 since the RAN 5 does not interwork directly with the 5GC nodes in the participating network in an indirect network sharing environment.

[0088] This Aspect discloses a few embodiments that make RACS function work in an indirect network sharing environment.

[0089] The indirect network sharing is useful comparing to the network sharing (e.g. MOCN) as interfaces between operators are less and thus less configuration efforts necessary.

[0090] On the other hand, the UE radio capability signaling optimization (RACS) function is widely deployed by PLMN operators. As the UE radio capability and configuration are becoming high functionality and sophisticated, the UE Radio Capability information is accordingly increasing in size. The RACS function helps to mitigate data volume over the air to convey a UE Radio Capability information from the UE to a RAN.

[0091] Author of this disclosure investigates how the RACS function works with the indirect network sharing environment and found some potential issues.

[0092] For example, - It is not clear which operator, either a hosting operator or a participating operator, assigns a UE Radio Capability ID for those of UEs who belonging to the participating operator. - It is also not clear how the RAN manages an operator ID (I.E. PLMN ID) that assigned the UE Radio Capability ID for the UE since the RAN does not interwork with the 5GC nodes that belong to the participating network in the indirect network sharing environment.

[0093] <First example of the First Aspect> 　　This example includes mechanisms where the UE Radio Capability ID is assigned by the hosting network and both, the assigned UE Radio Capability ID and operator ID (e.g., PLMN ID) which assigns the UE Radio Capability ID to the UE 3 (i.e. a PLMN ID of the hosting network), are managed in core network 7 and RAN 5.

[0094] In addition, this example also includes a mechanism for the UE 3 to re-assign the UE Radio Capability ID when the UE 3 moves out from an area covered by the hosting network to an area covered by the participating network.

[0095] <First scenario in the First example of the First Aspect> 　　The First scenario in the First example of the First Aspect includes an example mechanism for assigning the UE Radio Capability ID by the hosting network during the Registration procedure.

[0096] Fig. 2 illustrates an example of mechanism for assigning the UE Radio Capability ID by the hosting network during the Registration procedure.

[0097] The detailed processes of this example are described below with reference to Fig. 2.

[0098] Step 1. The UE 3 sends the RRC Setup Request message to the M-RAN 501 (e.g., Master-RAN 501).

[0099] Step 2. Upon the reception of the RRC Setup Request message in Step 1, the M-RAN 501 sends the RRC Setup message to the UE 3.

[0100] Step 3. The UE 3 sends the RRC Setup Complete message to the M-RAN 501 including Dedicated NAS, UE Radio Capability ID, Indirect Network Sharing support indicator and PLMN ID of the UE Radio Capability. The Dedicated NAS includes the Registration Request message. The Registration Request message includes at least one of User ID, UE Radio Capability ID, Indirect Network Sharing support indicator and PLMN ID of the UE Radio Capability.

[0101] The following bullets explain each parameter in detail. - User ID: User ID (e.g., the User ID may be expressed as User Identity) may be a 5G-GUTI, SUCI or SUPI. - UE Radio Capability ID: the UE Radio Capability ID is an identifier used to represent a set of UE radio capabilities with format defined in 3GPP TS 23.003 [5] that is used to uniquely identify a set of UE Radio Capabilities (excluding UTRAN and NB-IoT capabilities). - Indirect Network Sharing support indicator: The Indirect Network Sharing support indicator indicates that the UE 3 has the capability to support the Indirect Network Sharing. - The Indirect Network Sharing support indicator may be referred by the AMF 7001. The AMF 7001 may send the PLMN ID of the UE Radio Capability to the UE 3 only if the UE 3 includes the Indirect Network Sharing support indicator. - In one example, the Indirect Network Sharing support indicator may indicate that the UE 3 supports handling of the PLMN ID of the UE Radio Capability. - PLMN ID of the UE Radio Capability: The PLMN ID of the UE Radio Capability is an identity which indicates the PLMN that assigns the UE Radio Capability ID to the UE 3. - The PLMN ID of the UE Radio Capability may be expressed in another way. For example, UE Radio Capability ID assigning PLMN ID, UE Radio Capability ID assigned PLMN ID, PLMN ID of PLMN-assigned UE Radio Capability ID, PLMN assigning RAC ID or etc. - The PLMN ID of the UE Radio Capability may be composed of a PLMN Identifier as defined in 3GPP TS 23.003 [5] (composing of MCC and MNC). - The PLMN ID of the UE Radio Capability may be composed of a Globally Unique AMF Identifier (GUAMI) as defined in 3GPP TS 23.003 [5] (composing of MCC, MNC and AMF Identifier (AMFI)). - The PLMN ID of the UE Radio Capability may be expressed as the PLMN ID assigning UE Radio Capability ID or the PLMN ID assigned UE Radio Capability ID.

[0102] The M-RAN 501 stores the Indirect Network Sharing support indicator and the PLMN ID of the UE Radio Capability if received from the UE 3.

[0103] Step 4. Upon reception of the RRC Setup Complete message from the UE 3, the M-RAN 501 sends the Initial UE message to the AMF 7001 including NAS-PDU. The NAS-PDU includes the Registration Request message that is received in the Dedicated NAS message in Step 3.

[0104] Step 5. Upon reception of the Registration Request message in Step 4, the AMF 7001 performs the Nudm_UECM_Registration procedure with the UDM 75 to register the AMF 7001 in the subscriber data record of the UE 3 in the UDM 75.

[0105] Step 6. The AMF 7001 performs the Nudm_SDM_Get procedure with the UDM 75 to download a subscriber of the UE 3.

[0106] Step 7. The AMF 7001 may interrogate the RAN 501 if the AMF 7001 does not hold the UE Radio Capability information and / or UE Radio Capability for Paging for the UE 3. For example, this interrogation is disclosed in the Third Variant of the First scenario in the First example of the First Aspect.

[0107] In case that the UE Radio Capability ID and / or PLMN ID of the UE Radio Capability are received in the Registration Request message from the UE 3 in Step 3, Steps 8 to 12 may be skipped and the process continues from Step 13.

[0108] Note that UE Radio Access Capability information implies a UE radio capabilities formats specified in 3GPP TS 38.331 [9] or / and a UE radio capabilities formats specified in 3GPP TS 36.331

[0010] or / and UE radio capabilities formats specified in a RRC protocol specification in 6G.

[0109] Step 8. The AMF 7001 sets the PLMN ID of the host operator in the Nnrf_NFDiscovery_Request message in Step 9.

[0110] Step 9. The AMF 7001 sends the Nnrf_NFDiscovery_Request message to the NRF 7801 including NF service Name and PLMN ID. The PLMN ID may be the ID of the hosting operator PLMN.

[0111] The following bullets explain each parameter in detail. - NF service Name: The NF service Name indicates a target of the Network Function for the discovery. In this example, the NF service Name is set as the UCMF. - PLMN ID: The PLMN ID indicates a target PLMN where the target Network Function is located.

[0112] Step 10. Upon reception of the Nnrf_NFDiscovery_Request message in Step 9, the NRF 7801 discovers a UCMF (i.e. UCMF 7701) in the PLMN indicated by the PLMN ID, example based on an internal data record within the NRF 7801 and finds the NF profile of the discovered UCMF 7701, example the NF profile is stored in the internal data record within the NRF 7801 and sends an Nnrf_NFDiscovery_Response message to the AMF 7001 including NF profile. The NF profile includes the profile of the discovered UCMF 7701. The NF profile may include NF instance ID, NF type, PLMN ID, FQDN or IP address of NF other profile information as described in section 6.2.6.2 in 3GPP TS 23.501 [2].

[0113] Step 11. The AMF 7001 sends Nucmf_UECapabilityManagement_Assign message to the UCMF 7701 including UE Radio Access Capability and UE Radio Capability for Paging.

[0114] The UE Radio Access Capability and the UE Radio Capability for Paging may be obtained in Step 7 as capabilities of the UE 3.

[0115] Step 12. Upon reception of the Nucmf_UECapabilityManagement_Assign message from the AMF 7001 in Step 11, the UCMF 7701 finds a UE Radio Capability ID that corresponds to the received UE Radio Access Capability and the received UE Radio Capability for Paging and sends the UE Radio Capability ID.

[0116] The UCMF 7701 sends the Nucmf_UECapabilityManagement_Assign response message to the AMF 7001 including the UE Radio Capability ID.

[0117] Step 13. The AMF 7001 sends the Initial Context Setup Request message to the RAN 501 including UE Radio Capability ID, 5G-GUTI, PLMN ID of the UE Radio Capability and NAS-PDU. The NAS-PDU includes the Registration Accept message that includes 5G-GUTI, UE Radio Capability ID and PLMN ID of the UE Radio Capability.

[0118] The AMF 7001 may include either the 5G-GUTI or the PLMN ID of the UE Radio Capability or both in the Initial Context Setup Request message.

[0119] Both the 5G-GUTI and the PLMN ID of the UE Radio Capability identify the participating network of the UE 3.

[0120] The AMF 7001 may include the PLMN ID of the UE Radio Capability only if the AMF 7001 receives the Indirect Network Sharing support indicator from the UE 3 in Step 3.

[0121] The following bullets explain each parameter in detail. - GUAMI: The GUAMI indicates a Globally Unique AMF Identifier as defined in 3GPP TS 23.003 [5] (composing of MCC, MNC and AMF Identifier (AMFI)) - UE Radio Capability ID: Refer to Step 3. - 5G-GUTI: The 5G-GUTI is a temporary user identifier for the UE 3, Refer to 3GPP TS 23.003 [5] for details. - PLMN ID of the UE Radio Capability: Refer to Step 3. - NAS-PDU: The NAS-PDU in the Initial Context Setup Request message includes a NAS message that is relayed to the UE 3 by the RAN 501. In this example, the NAS-PDU includes the Registration Accept message.

[0122] Step 14. Upon reception of the Initial Context Setup Request message from the AMF 7001 in Step 13, the RAN 501 (e.g., the Master-RAN 501) stores the received GUAMI, UE Radio Capability ID, 5G-GUTI and PLMN ID of the UE Radio Capability.

[0123] The RAN 501 may identify that UE 3 is a user equipment from the participating network if the MCC and the MNC parts of the GUAMI are different from the MCC and the MNC parts of the PLMN ID of the UE Radio Capability.

[0124] The RAN 501 may identify that UE 3 is a user equipment from the participating network if the MCC and the MNC parts of the GUAMI are different from the MCC and the MNC parts of the 5G-GUTI.

[0125] The RAN 501 sends the RRC Reconfiguration message to the UE 3 including nas-Container. The nas-Container includes the Registration Accept message that is received in Step 13 from the AMF 7001.

[0126] Step 15. The UE 3 sends the RRC UL Information Transfer message to the RAN 501 including Dedicated NAS. The Dedicated NAS includes the Registration Complete message.

[0127] Step 16. Upon reception of the RRC UL Information Transfer message from the UE 3, the RAN 501 sends the Uplink NAS Transport message to the AMF 7001 including NAS-PDU. The NAS-PDU includes the Registration Complete that is received in Step 15 from the UE 3.

[0128] Step 17. The UE 3 stores the received UE Radio Capability ID and the received PLMN ID of the UE Radio Capability.

[0129] The UE 3 may include the received UE Radio Capability ID and the received PLMN ID of the UE Radio Capability in the Registration Request message when the UE 3 performs the Registration procedure later. The Registration Request message including the UE Radio Capability ID and the PLMN ID of the UE Radio Capability helps an AMF and a RAN to find the UE Radio Capability of the UE 3.

[0130] <First Variant of the First scenario in the First example of the First Aspect> 　　Like the Initial Context Setup Request message in Step 13, the following NGAP messages may carry the UE Radio Capability ID together with the PLMN ID of the UE Radio Capability from the AMF 7001 to the RAN 501: - UE Context Modification Request message; - Connection Establishment Indication message; - Handover Request message; - Path Switch Request Acknowledge message; - Downlink NAS Transfer message; - UE Information Transfer message.

[0131] <Second Variant of the First scenario in the First example of the First Aspect> 　　In one example, in Step 8 the AMF 7001 determines to use the UCMF of the participating operator network UCMF 7702 to which the UE 3 belongs to get the UE radio capability ID corresponding to the radio capabilities of the UE 3. In this case the AMF 7001 sets the PLMN ID of the participating operator in the Nnrf_NFDiscovery_Request message in Step 9. Step 9 and Step 10 are executed. The NRF 7801 may contact NRF of participating PLMN to get the address of UCMF 7702. After getting the address of UCMF 7702, the Steps 11 and 12 are executed between the AMF 7001 in the hosting operator network and the UCMF 7702 in the participating operator network to get the UE radio capability Identity of the UE 3.

[0132] <Third Variant of the First scenario in the First example of the First Aspect> 　　In the Step 7 of Fig. 2, the AMF 7001 may interrogate the RAN 501 if the AMF 7001 does not recognize the UE Radio Capability ID received from the UE 3 or the AMF 7001 does not hold the UE Radio Capability information and / or UE Radio Capability for Paging for the UE 3.

[0133] Fig. 3 illustrates an example of mechanism on enquiring the UE Radio Capability ID.

[0134] <Fourth Variant of the First scenario in the First example of the First Aspect> 　　In one example, the FQDN or IP Address of UCMF 7701 is locally configured in the AMF 7001. In this case, the AMF 7001 skips Steps 9 and 10 and continues the process with Step 11.

[0135] The detailed processes of this example are described below with reference to Fig. 3.

[0136] Step 0. The AMF 7001 may send the UE Capability Check Request message, or newly defined NGAP signalling message e.g. UE Capability Enquiry message, including the UE Capability Enquiry indicator and / or PLMN ID of the hosting network to the M-RAN 501.

[0137] Step 1. The M-RAN 501 decides to perform UE radio capability Enquiry procedure in order to fetch the UE Radio Access Capability information from the UE 3, e.g. upon receiving the signalling message in Step 0, or the RAN internally decides to do so even without receiving the signalling message in Step 0.

[0138] Step 2. The M-RAN 501 sends the UECapabilityEnquiry message to the UE 3 including the UE-CapabilityRAT-Request indicator and the PLMN-ID that the M-RAN 501 is connecting to, in this case the PLMN-ID is the id of hosting network.

[0139] Step 3. The UE 3 replies the UECapabilityInformation message to the M-RAN 501 including the UE Radio Access Capability Information, UE Radio Capability for Paging, UE Radio Capability ID and the PLMN-ID that the UE intends to provide.

[0140] Step 4. Upon reception of the Step 3, the M-RAN 501 sends the UE Radio Capability Info Indication to the AMF 7001 including the UE Radio Access Capability Information, UE Radio Capability for Paging, UE Radio Capability ID and PLMN ID.

[0141] <Fifth Variant of the First scenario in the First example of the First Aspect> 　　At Step 4 of Fig. 2 the AMF 7001 may store the Indirect Network Sharing Indication, PLMN ID of the UE Radio Capability and the UE Radio Capability ID received in the Registration Request message from UE 3 in the UE Context within the AMF 7001. Then the AMF 7001 may provide the Indirect Network Sharing Indication, the PLMN ID of the UE Radio Capability and the UE Radio Capability ID stored in the UE context for UE 3 to the target AMF via Namf_Communication_UEContexTransfer Response message during the UE context retrieval by the target AMF in inter AMF mobility.

[0142] Similarly, in Step 12 of Fig. 2 the AMF 7001 may store or update the UE Radio Capability ID received in the Nucmf_UECapabilityManagement_Assign response message from the UCMF 7701 in the UE Context within the AMF 7001. Then the AMF 7001 may provide the new UE Radio Capability ID together with the Indirect Network Sharing Indication and the PLMN ID of the UE Radio Capability stored in the UE context for UE 3 to the target AMF via Namf_Communication_UEContexTransfer Response message during the UE context retrieval by the target AMF in inter AMF mobility.

[0143] <Sixth Variant of the First scenario in the First example of the First Aspect> 　　In one example, when a UE 3 is handed over to a target RAN of the participating operator network, the M-RAN 501 includes UE Radio Capability information in the Handover Required message in an existing IE or a new IE. When the AMF 7001 sends the UE context to the target AMF of the participating operator during handover cases and inter PLMN mobility case then it sends UE 3 UE Radio capability information to the target AMF in an existing message between the AMF 7001 and the target AMF of the participating network operator.

[0144] In one example, the AMF 7001 sends an Indirect Network sharing Indicator in Registration Accept message to the UE in step 14. When the UE selects a cell of the participating operator network and performing Registration to the participating operator network then the UE determines that it is moving from host operator network to the participating network operator based on Indirect Network sharing Indicator and the UE shall not include UE radio capability ID in the registration request message to the participating operator network

[0145] <Second scenario in the First example of the First Aspect> 　　The Second scenario of the First example of the First Aspect includes an example mechanism for handover within the hosting network.

[0146] Fig. 4 illustrates an example of mechanism on handling of the UE Radio Capability in the hosting network during the Handover procedure.

[0147] The detailed processes of this example are described below with reference to Fig. 4.

[0148] Step 0. The UE 3 is in CM-CONNECTED state.

[0149] Step 1. The M-RAN 501 (e.g., Master-RAN 501) decides to perform handover with the M-RAN 503 (e.g., Master-RAN 503) as the target RAN for the handover procedure.

[0150] Step 2. The M-RAN 501 sends the Handover Request message to the M-RAN 503 including GUAMI, UE Radio Capability ID, 5G-GUTI and PLMN ID of the UE Radio Capability.

[0151] The M-RAN 501 may include either the 5G-GUTI or the PLMN ID of the UE Radio Capability or both in the Handover Request message.

[0152] Both the 5G-GUTI and the PLMN ID of the UE Radio Capability identify a participating network of the UE 3.

[0153] The following bullets explain each parameter in detail. - GUAMI: Refer to Step 13 in Fig. 2. - UE Radio Capability ID: Refer to Step 3 in Fig. 2. - 5G-GUTI: Refer to Step 13 in Fig. 2. - PLMN ID of the UE Radio Capability: Refer to Step 3 in Fig. 2.

[0154] Step 3. Upon reception of the Handover Request message from the M-RAN 501 in Step 2, the M-RAN 503 may perform an admission control and stores the received GUAMI, UE Radio Capability ID, 5G-GUTI and PLMN ID of the UE Radio Capability.

[0155] The RAN 503 may identify that UE 3 is a user equipment from the participating network if the MCC and the MNC parts of the GUAMI are different from the MCC and the MNC parts of the PLMN ID of the UE Radio Capability.

[0156] The RAN 503 may identify that UE 3 is a user equipment from the participating network if the MCC and the MNC parts of the GUAMI are different from the MCC and the MNC parts of the 5G-GUTI.

[0157] Once the admission control is successful, the M-RAN 503 sends the Handover Request acknowledge message to the RAN 501.

[0158] Step 4. Upon reception of the Handover Request acknowledge message from the M-RAN 503 in Step 3, the M-RAN 501 sends the RRC Reconfiguration message to the UE 3 to order the UE 3 to handover to a cell from the M-RAN 503.

[0159] Step 5. Upon reception of the RRC Reconfiguration message from the M-RAN 501 in Step 4, the UE 3 tunes to the cell from the M-RAN 503 and synchronizes with the cell.

[0160] Step 6. Once the synchronization is successful in Step 5, the UE 3 sends the RRC Reconfiguration Complete message to the M-RAN 503.

[0161] Step 7. Upon reception of the RRC Reconfiguration Complete message from the UE 3 in Step 6, the M-RAN 503 sends the Handover success message to the M-RAN 501.

[0162] Step 8. The M-RAN 503 sends the Path Switch Request message to the AMF 7001. The M-RAN 503 finds the AMF 7001 based on the GUAMI received from the M-RAN 501 in Step 2.

[0163] Step 9. Upon reception of the Path Switch Request message from the M-RAN 503 in Step 8, the AMF 7001 sends the Path Switch Request acknowledge message including UE Radio Capability ID, 5G-GUTI and PLMN ID of the UE Radio Capability .

[0164] The AMF 7001 may include either the 5G-GUTI or the PLMN ID of the UE Radio Capability or both in the Path Switch Request acknowledge message.

[0165] Both the 5G-GUTI and the PLMN ID of the UE Radio Capability identify a participating network of the UE 3.

[0166] The following bullets explain each parameter in detail. - UE Radio Capability ID: Refer to Step 3 in Fig. 2. - 5G-GUTI: Refer to Step 13 in Fig. 2. - PLMN ID of the UE Radio Capability: Refer to Step 3 in Fig. 2.

[0167] Step 10. The M-RAN 503 sends the UE Context Release message to the M-RAN 501.

[0168] <Third scenario in the First example of the First Aspect> 　　The Third scenario in the First example of the First Aspect includes an example mechanism for UE Radio Capability ID Mapping procedure in the hosting network.

[0169] For example, this procedure may be used by the M-RAN 501 in case that the M-RAN 501 has a UE Radio Capability ID but does not have a corresponding UE Radio Access Capability and UE Radio Capability for Paging.

[0170] For example, this procedure may be used by the M-RAN 501 in case that the M-RAN 501 has a UE Radio Capability ID and needs to confirms the corresponding UE Radio Access Capability and UE Radio Capability for Paging by interrogating with the AMF 7001.

[0171] Fig. 5 illustrates an example of mechanism on handling of the UE Radio Capability ID Mapping procedure in the hosting network.

[0172] Note that this procedure uses non-UE-associated signaling.

[0173] The detailed processes of this example are described below with reference to Fig. 5.

[0174] Step 0. The M-RAN 501 (e.g., Master-RAN 501) decides to perform UE radio capability ID mapping procedure. For example, if the M-RAN 501 needs to check the compatibility between the UE radio capabilities and network configuration on IMS voice service.

[0175] Step 1. The M-RAN 501 sends the UE radio capability ID mapping request to the AMF 7001 including UE Radio Capability ID and PLMN ID of the UE Radio Capability.

[0176] The following bullets explain each parameter in detail. - UE Radio Capability ID: Refer to Step 3 in Fig. 2. - PLMN ID of the UE Radio Capability: Refer to Step 3 in Fig. 2.

[0177] Note that Steps 2 to 5 are optional steps and executed if the AMF 7001 does not have a mapping information for the received UE Radio Capability ID in Step 1.

[0178] Step 2. The AMF 7001 sends the Nnrf_NFDiscovery_Request message to the NRF 7801 including NF service Name and PLMN ID.

[0179] The AMF 7001 sets the PLMN ID of the host operator in the Nnrf_NFDiscovery_Request message.

[0180] The following bullets explain each parameter in detail. - NF service Name: Refer to Step 9 in Fig. 2. - PLMN ID: Refer to Step 9 in Fig. 2.

[0181] Step 3. Upon reception of the Nnrf_NFDiscovery_Request message in Step 2, the NRF 7801 discovers a UCMF (i.e. UCMF 7701) in a PLMN indicated by the PLMN ID, example based on an internal data record within the NRF 7801 and finds a NF profile of the discovered UCMF 7701, example the NF profile is stored in the internal data record within the NRF 7801 and sends an Nnrf_NFDiscovery_Response message to the AMF 7001 including NF profile. The NF profile includes a profile of the discovered UCMF 7701. The NF profile may include NF instance ID, NF type, PLMN ID, FQDN or IP address of NF other profile information as described in section 6.2.6.2 in 3GPP TS 23.501 [2].

[0182] Step 4. The AMF 7001 sends Nucmf_UECapabilityManagement_Resolve message to the UCMF 7701 including UE Radio Capability ID.

[0183] The following bullets explain each parameter in detail. - UE Radio Capability ID: Refer to Step 3 in Fig. 2.

[0184] Step 5. Upon reception of the Nucmf_UECapabilityManagement_Resolve message from the AMF 7001 in Step 4, the UCMF 7701 finds a UE Radio Access Capability and UE Radio Capability for Paging that corresponds to the received UE Radio Capability ID.

[0185] For example, the UE Radio Access Capability and the UE Radio Capability for Paging that corresponds to the received UE Radio Capability ID are stored in the internal data record within the UCMF 7701.

[0186] The UCMF 7701 sends the Nucmf_UECapabilityManagement_Resolve response message to the AMF 7001 including the UE Radio Access Capability and UE Radio Capability for Paging.

[0187] Steo 6. Upon reception of the Nucmf_UECapabilityManagement_Resolve response message from the UCMF 7701 in Step 5, the AMF 7001 sends the UE radio capability ID mapping response message to the M-RAN 501 including UE Radio Capability ID, UE Radio Access Capability and UE Radio Capability for Paging.

[0188] The M-RAN 501 maintains the mapping between UE Radio Capability ID and UE Radio Access Capability and between UE Radio Capability ID and UE Radio Capability for Paging.

[0189] <First variant of Third scenario in the First example of the First Aspect> 　　The principle of the Third scenario in the First example of the First aspect is also applicable in EPS. In this case the eNodeB includes PLMN ID of the UE Radio capability to the UE RADIO CAPABILITY ID MAPPING REQUEST message to the MME. PLMN ID of the UE Radio capability is set to the PLMN ID for which the eNodeB is asking for radio capability information mapping corresponding to the UE Radio Capability ID. For example, MME is shared by PLMN 1 and PLMN 2 and MME has established the S1 interface with the eNodeB for these two PLMNs and eNodeB wants to know the radio capability information or a UE radio capability ID for PLMN 1, then the eNodeB includes PLMN ID of PLMN 1 in the UE RADIO CAPABILITY ID MAPPING REQUEST message. When the MME receives UE RADIO CAPABILITY ID MAPPING REQUEST message containing the PLMN ID and UE radio capability identity, the MME selects a UCMF corresponding to the PLMN ID received in the UE RADIO CAPABILITY ID MAPPING REQUEST message. The MME sends an existing message to the selected UCMF containing the UE radio capability identity requesting the UCMF to provide the radio capability information corresponding to the UE radio capability identity. The UCMF upon receiving the message sends the radio capability information corresponding to the UE radio capability identity to the MME in an existing message from. When the MME receives the response message from the UCMF, the MME sends radio capability information along with the UE radio capability ID the MME has sent to the UCMF received from UCMF to the eNodeB in the UE RADIO CAPABILITY ID MAPPING RESPONSE message. In addition, the MME and eNodeB will make an entry to the dictionary of UE Radio capability identity, PLMN ID and radio capability information. The eNodeB and MME use this entry to covert between the UE radio capabilities information and UE radio capability IE for the PLMN ID until it is updated by the UCMF.

[0190] In one example, if the UCMF is shared by multiple PLMNs then the MME sends received PLMN ID from the eNodeB in UE RADIO CAPABILITY ID MAPPING REQUEST message to UCMF the handling radio capability IE and radio capability information mapping. The UCMF uses the PLMN ID received in the message from the MME to map the UE Radio capability ID to the UE Radio capability information and sends back to the MME as described above.

[0191] <Fourth scenario in the First example of the First Aspect> 　　The Fourth scenario in the First example of the First Aspect includes an example mechanism for the Secondary Node Addition procedure in the hosting network. This scenario applies for the case when the M-RAN and S-RAN belongs to two different PLMNs, these PLMNs can be equivalent PLMNs or Hosting operator and the participating operator in case of Indirect Network sharing.

[0192] Fig. 6 illustrates an example of mechanism on handling of the Secondary Node Addition procedure in the hosting network.

[0193] The detailed processes of this example are described below with reference to Fig. 6.

[0194] Step 0. The UE 3 is in CM-CONNECTED state.

[0195] Step 1. The M-RAN 501 (e.g., Master-RAN 501) decides to perform the Secondary Node Addition procedure as described in 3GPP TS 37.340 [6].

[0196] Step 2. The M-RAN 501 sends the S-Node Addition Request message (e.g., Secondary Node Addition Request message) to the S-RAN 502 (e.g., Secondary-RAN 502) including UE Radio Capability ID, GUAMI, 5G-GUTI and PLMN ID of the UE Radio Capability.

[0197] The M-RAN 501 may include either the 5G-GUTI or the PLMN ID of the UE Radio Capability or both in the S-Node Addition Request message.

[0198] Both the 5G-GUTI and the PLMN ID of the UE Radio Capability identify a participating network of the UE 3.

[0199] The following bullets explain each parameter in detail. - UE Radio Capability ID: Refer to Step 3 in Fig. 2. - GUAMI: Refer to Step 13 in Fig. 2. - 5G-GUTI: Refer to Step 13 in Fig. 2. - PLMN ID of the UE Radio Capability: Refer to Step 3 in Fig. 2.

[0200] Step 3. Upon reception of the S-Node Addition Request message from the M-RAN 501 in Step 2, the S-RAN 502 allocates radio resources for user plane.

[0201] The S-RAN 502 may identify that UE 3 is a user equipment from the participating network if the MCC and the MNC parts of the GUAMI are different from the MCC and the MNC parts of the PLMN ID of the UE Radio Capability.

[0202] The S-RAN 502 may identify that UE 3 is a user equipment from the participating network if the MCC and the MNC parts of the GUAMI are different from the MCC and the MNC parts of the 5G-GUTI.

[0203] After successful resource allocation, the S-RAN 502 sends the S-Node Addition Request Acknowledge to the M-RAN 501.

[0204] Step 4. The Secondary Node Addition procedure continues from Step 2a in Section 10.2.2 in 3GPP TS 37.340 [6].

[0205] <First Variant of Fourth scenario in the First example of the First Aspect> 　　In one example, the principle of the above embodiment also applies to the EPS system. In EPS system, for Evolved Non-standalone Dual Connectivity (EN-DC) the MeNB sends in SGNB ADDITION REQUEST message including at least one of the GUMI (Globally Unique MME ID) and PLMN ID of the UE Radio Capability.

[0206] The GUMMEI is taking from the GUMMEI part of the GUTI assigned to the UE 3. The PLMN ID of the UE Radio Capability is the PLMN ID which is associated with Radio capability identity.

[0207] When the en-gNB receives SGNB ADDITION REQUEST message then the en-gNB derives or finds the radio capability information related to the radio capability ID from the UE radio capability ID and radio capability mapping database related to the received PLMN ID. The en-gNB uses this radio capability information for the UE 3 related procedures in en-gNB.

[0208] In one example, the en-gNB receives SGNB ADDITION REQUEST message then the en-gNB looks into the mapping database of UE radio capability information and UE radio capability ID related to the selected PLMN ID to find radio capability information corresponding to the received UE radio capability ID. The en-gNB will then use this radio capability information for the UE 3 in the existing procedures in en-gNB.

[0209] <Second variant of Fourth scenario in the First example of the First Aspect> 　　In one example, in Step 2 when the S-RAN 502 receives S-Node Addition Request message then the S-RAN 502 looks into the mapping database of UE radio access capability information and UE radio capability ID related to the selected PLMN ID to find radio access capability information corresponding to the received UE radio capability ID. The S-RAN 502 will then use this radio access capability information for the UE 3 in the existing procedures in S-RAN 502.

[0210] <Third variant of Fourth scenario in the First example of the First Aspect> 　　In one example, if the M-RAN 501 determines that the S-RAN 502 belongs to the different PLMN, then the M-RAN 501 sends the UE Radio capability information in an existing information element or in a new information element to the S-RAN 502 in the S-Node Addition Request message. When the S-RAN 502 receives the UE radio capability information, the S-RAN 502 will use the information for the UE 3 in the procedure related to the S-RAN 502.

[0211] If the S-RAN 502 receives both UE radio capability ID and UE radio capability information, then the S-RAN 502 may map the UE radio capability ID to the UE radio capability information based on a data base (ex. the dictionary) stored at the S-RAN 502. In case the S-RAN 502 cannot map the UE radio capability ID to the UE radio capability information, then the S-RAN 502 will use the received UE radio capability information.

[0212] <Fifth scenario in the First example of the First Aspect> 　　The Fifth scenario in the First example of the First Aspect includes an example mechanism of the Registration procedure in a participating network when the UE 3 moves from the hosting network.

[0213] Fig. 7 illustrates an example of mechanism on assigning the UE Radio Capability ID by the participating network during the Registration procedure.

[0214] The detailed processes of this example are described below with reference to Fig. 7.

[0215] Step 0. The UE 3 has registered with AMF 7001 in the hosting network and a 5G-GUTI that includes a PLMN ID of the participating network is assigned.

[0216] Step 1. The UE 3 sends the RRC Setup Request message to the RAN 504. For example, the UE 3 may send the RRC Setup Request message to the RAN 504 in a participating operator network. Example, The UE 3 moves to an area where the participating network operator covers.

[0217] Step 2. Upon the reception of the RRC Setup Request message in Step 1, the RAN 504 sends the RRC Setup message to the UE 3.

[0218] Step 3. The UE 3 sends the RRC Setup Complete message to the RAN 504 including Dedicated NAS, UE Radio Capability ID, Indirect Network Sharing support indicator and PLMN ID of the UE Radio Capability. The Dedicated NAS includes the Registration Request message. The Registration Request message includes at least one of User ID, UE Radio Capability ID, Indirect Network Sharing support indicator and PLMN ID of the UE Radio Capability.

[0219] Refer to Step 3 in Fig. 2 for parameter details.

[0220] The RAN 504 stores the Indirect Network Sharing support indicator and PLMN ID of the UE Radio Capability if received from the UE 3.

[0221] Step 4. Upon reception of the RRC Setup Complete message from the UE 3, the RAN 504 sends the Initial UE message to the AMF 7002 including NAS-PDU. The NAS-PDU includes the Registration Request message that is received in the Dedicated NAS in Step 3.

[0222] Step 5. Upon reception of the Registration Request message in Step 4, the AMF 7002 performs the Nudm_UECM_Registration procedure with the UDM 75 to register the AMF 7002 to a subscriber data record of the UE 3 in the UDM 75.

[0223] Step 6. The AMF 7002 performs the Nudm_SDM_Get procedure with the UDM 75 to download a subscriber of the UE 3.

[0224] Step 7. The AMF 7002 may interrogate the RAN 501 if the AMF 7002 does not hold the UE Radio Capability information and / or UE Radio Capability for Paging for the UE 3. 　　For example, this interrogation is disclosed in the Third Variant of the First scenario in the First example of the First Aspect with replacing the AMF 7001 for the AMF 7002 and replacing the M-RAN 501 for the RAN 501.

[0225] Step 8. The AMF 7002 decides whether UE Radio Capability ID needs to update based on the following checking criteria: - If the received PLMN ID of the UE Radio Capability in the Registration Request message in Step 4 is different from a PLMN ID of the AMF 7002, the AMF 7002 decides to update the UE Radio Capability ID for the UE 3. - If the received 5G-GUTI in the User ID that is received in the Registration Request message in Step 4 can be referred as a 5G-GUTI assigned by any AMF 7001 in the hosting network based on local configuration, the AMF 7002 decides to update the UE Radio Capability ID for the UE 3. - If the AMF Identifier part of the received 5G-GUTI in the User ID that is received in the Registration Request message in Step 3 can be referred as a 5G-GUTI assigned by any AMF in the hosting network based on local configuration, the AMF 7002 decides to update the UE Radio Capability ID for the UE 3.

[0226] Unless any of the above criteria matches, Steps 9 to 12 are skipped, and the process continues from Step 13.

[0227] Step 9. The AMF 7002 sends the Nnrf_NFDiscovery_Request message to the NRF 7802 including NF service Name and PLMN ID. The PLMN ID may be the ID of hosting operator PLMN. 　　Refer to Step 9 in Fig. 2 for parameter details.

[0228] Step 10. Upon reception of the Nnrf_NFDiscovery_Request message in Step 9, the NRF 7802 discovers a UCMF (i.e. UCMF 7702) in a PLMN indicated by the PLMN ID, example based on an internal data record within the NRF 7802 and finds a NF profile of the discovered UCMF 7702, example the NF profile is stored in the internal data record within the NRF 7802 and sends an Nnrf_NFDiscovery_Response message to the AMF 7002 including NF profile. The NF profile includes a profile of the discovered UCMF 7702. The NF profile may include NF instance ID, NF type, PLMN ID, FQDN or IP address of NF other profile information as described in section 6.2.6.2 in 3GPP TS 23.501 [2].

[0229] Step 11. The AMF 7002 sends Nucmf_UECapabilityManagement_Assign message to the UCMF 7702 including UE Radio Access Capability and UE Radio Capability for Paging. 　　The UE Radio Access Capability and the UE Radio Capability for Paging may be obtained in Step 7 as capabilities of the UE 3.

[0230] Step 12. Upon reception of the Nucmf_UECapabilityManagement_Assign message from the AMF 7002 in Step 11, the UCMF 7702 finds a UE Radio Capability ID that corresponds to the received UE Radio Access Capability and the received UE Radio Capability for Paging and sends the UE Radio Capability ID.

[0231] The UCMF 7702 sends the Nucmf_UECapabilityManagement_Assign response message to the AMF 7002 including the UE Radio Capability ID.

[0232] Step 13. The AMF 7002 sends the Initial Context Setup Request message to the RAN 501 including UE Radio Capability ID, 5G-GUTI, PLMN ID of the UE Radio Capability and NAS-PDU. The NAS-PDU includes the Registration Accept message that includes 5G-GUTI, UE Radio Capability ID and PLMN ID of the UE Radio Capability.

[0233] The AMF 7002 may include either the 5G-GUTI or the PLMN ID of the UE Radio Capability or both in the Initial Context Setup Request message.

[0234] Both the 5G-GUTI and the PLMN ID of the UE Radio Capability identify a participating network of the UE 3.

[0235] The AMF 7002 may include the PLMN ID of the UE Radio Capability only if the AMF 7002 receives the Indirect Network Sharing support indicator from the UE 3 in Step 3.

[0236] Refer to Step 13 in Fig. 2 for parameter details.

[0237] Step 14. Upon reception of the Initial Context Setup Request message from the AMF 7002 in Step 13, the RAN 501 stores the received GUAMI, UE Radio Capability ID, 5G-GUTI and PLMN ID of the UE Radio Capability.

[0238] The RAN 501 may identify that UE 3 is a UE 3 of a user from the participating network if the MCC and the MNC parts of the GUAMI are different from the MCC and the MNC parts of the PLMN ID of the UE Radio Capability.

[0239] The RAN 501 may identify that UE 3 is a UE 3 of a user from the participating network if the MCC and the MNC parts of the GUAMI are different from the MCC and the MNC parts of the 5G-GUTI.

[0240] The RAN 501 sends the RRC Reconfiguration message to the UE 3 including nas-Container. The nas-Container includes the Registration Accept message that is received in Step 13 from the AMF 7002.

[0241] Step 15. The UE 3 sends the RRC UL Information Transfer message to the RAN 504 including Dedicated NAS. The Dedicated NAS includes the Registration Complete message.

[0242] Step 16. Upon reception of the RRC UL Information Transfer message from the UE 3, the RAN 504 sends the Uplink NAS Transport message to the AMF 7002 including NAS-PDU. The NAS-PDU includes the Registration Complete that is received in Step 15 from the UE 3.

[0243] Step 17. The UE 3 stores the received UE Radio Capability ID and the received PLMN ID of the UE Radio Capability.

[0244] The UE 3 may include the received UE Radio Capability ID and the received PLMN ID of the UE Radio Capability into the Registration Request message when the UE 3 performs the Registration procedure later.

[0245] The Registration Request message including the UE Radio Capability ID and the PLMN ID of the UE Radio Capability helps an AMF and a RAN to find the UE Radio Capability of the UE 3.

[0246] <First Variant of the Fifth scenario in the First example of the First Aspect> 　　At Step 4 of Fig. 7 the AMF 7002 may store the Indirect Network Sharing Indication, PLMN ID of the UE Radio Capability and the UE Radio Capability ID received in the Registration Request message from UE 3 in the UE Context within the AMF 7002. Then the AMF 7002 may provide the Indirect Network Sharing Indication, the PLMN ID of the UE Radio Capability and the UE Radio Capability ID stored in the UE context for UE 3 to the target AMF via Namf_Communication_UEContexTransfer Response message during the UE context retrieval by the target AMF in inter AMF mobility.

[0247] Similarly, in Step 12 of Fig. 7 the AMF 7002 may store or update the UE Radio Capability ID received in the Nucmf_UECapabilityManagement_Assign response message from the UCMF 7702 in the UE Context within the AMF 7002. Then the AMF 7002 may provide the new UE Radio Capability ID together with the Indirect Network Sharing Indication and the PLMN ID of the UE Radio Capability stored in the UE context for UE 3 to the target AMF via Namf_Communication_UEContexTransfer Response message during the UE context retrieval by the target AMF in inter AMF mobility.

[0248] <Sixth scenario in the First example of the First Aspect> 　　This example includes the mechanism to handle the UE radio capabilities ID or UE radio capabilities when the UE 3 transit from the RRC Inactive state to RRC connected state. This example also covers the case when the UE context is transferred between different NG-RANs served by different PLMNs.

[0249] In this scenario, the Last serving RAN 502 may be interpreted as the old serving RAN, the old RAN or the Source RAN.

[0250] In this scenario, the Last serving RAN 502 may be interpreted as the Last serving gNB.

[0251] Fig. 8 illustrates the UE radio capabilities transfer procedure during the UE context retrieval procedure between the new NG RAN and last serving RAN.

[0252] The detailed processes of this example are described below with reference to Fig. 8.

[0253] Step 0. The UE 3 is in RRC_INACTIVE state. 　　The UE 3, the Last serving RAN 502 and the AMF 7001 have assigned UE radio capability ID corresponding to the UE radio capability information.

[0254] Step 1.　　When the UE 3 decides to perform the resume procedure, the UE 3 sends the RRC Resume Request message to the RAN 501 including the I-RNTI that are allocated by the Last serving RAN 502.

[0255] Step 2.　　The RAN 501, if the RAN 501 is able to resolve the gNB identity contained in the I-RNTI, sends the RETRIEVE UE CONTEXT REQUEST message to the Last serving RAN 502 to obtains the UE Context data for the UE 3.

[0256] Steps 3-4. Upon reception of the RETRIEVE UE CONTEXT REQUEST message from the RAN 501, the Last serving RAN 502 finds the UE Radio Capability ID for the UE 3, based on the UE context for the UE 3 stored in the Last serving RAN 502, if the Last serving RAN 502 knows that the RAN 501 supports the RACS function as defined in 3GPP TS 23.501 [2].

[0257] The Last serving RAN 502 sends the RETRIEVE UE CONTEXT RESPONSE message including the UE Radio Capability ID, PLMN ID of the UE Radio Capability, UE Radio capability to the RAN 501.

[0258] The following bullets explain each parameter in detail. - UE Radio Capability ID: Refer to Step 3 in Fig. 2. - PLMN ID of the UE Radio Capability: Refer to Step 3 in Fig. 2. - UE Radio capability: The UE Radio capability includes either the UE Radio Access Capability Information message as defined in 3GPP TS 38.331 [9], or the UE Radio Access Capability Information-NB message as defined in 3GPP TS 36.331

[0010] .

[0259] If the Last serving RAN 502 has knowledge that the RAN 501 might not have a local copy of the UE Radio Capability corresponding to the UE Radio Capability ID (example, in case the Last serving RAN 502 has retrieved the UE Radio Capability for the UE 3 from the AMF 7001) then the Last serving RAN 502 may also include some or all of the UE Radio Capability for the UE 3 in the RETRIEVE UE CONTEXT RESPONSE message.

[0260] For example, the Last serving RAN 502 may include some part of the UE Radio Capability for the UE 3 in the RETRIEVE UE CONTEXT RESPONSE message due to the size limit based on local configuration.

[0261] In the case of inter-PLMN retrieval, i.e. the RAN 501 and Last serving RAN 502 belongs to two different PLMNs, when the Last serving RAN 502 (example, Source NG-RAN) and RAN 501 (Example, Target NG-RAN) support RACS as defined in 3GPP TS 23.501 [2] and the Last serving RAN 502 determines based on local configuration that the PLMN associated with the RAN 501 does not support the UE Radio Capability ID assigned by the PLMN associated with the Last serving RAN 502, then the Last serving RAN 502 shall provide the UE Radio capability to the RAN 501 in RETRIEVE UE CONTEXT RESPONSE message and shall not send the UE Radio Capability ID in RETRIEVE UE CONTEXT RESPONSE message.

[0262] If the RAN 501 received the UE Radio capability but did not receive the UE Radio Capability ID in the RETRIEVE UE CONTEXT RESPONSE message from the Last serving RAN 502, the RAN 501 shall proceed with RRC_INACTIVE to RRC_CONNECTED procedure using the received UE radio access capabilities.

[0263] If the RAN 501 received both the UE radio access capabilities and the UE Radio Capability ID in the RETRIEVE UE CONTEXT RESPONSE message from the Last serving RAN 502, then the RAN 501 shall use any locally stored UE Radio capability corresponding to the UE Radio Capability ID. If none of them are stored locally, the RAN 501 may request the full UE Radio capability from the core network 7 (e.g. AMF 7001).

[0264] If the full UE Radio capability is not promptly received from the core network 7 or the RAN 501 decides not to request them, then the RAN 501 shall proceed with the UE Radio capability sent by the Last serving RAN 502.

[0265] The RAN 501 may use the UE Radio capability that corresponds to the received UE Radio Capability ID and received the PLMN ID of the UE Radio Capability from the source NG-RAN for any other UE with the same the UE Radio Capability ID and the same PLMN ID of the UE Radio Capability.

[0266] The RAN 501 may not use the UE Radio capability that corresponds to the received UE Radio Capability ID and received the PLMN ID of the UE Radio Capability from the source NG-RAN for any other UE with the same the UE Radio Capability ID and the same PLMN ID of the UE Radio Capability.

[0267] The RAN 501 shall not use the UE Radio capability that corresponds to the received UE Radio Capability ID from the source NG-RAN for any other UE with the same the UE Radio Capability ID but the received PLMN ID of the UE Radio Capability is different from the ones for any other UE.

[0268] Steps 5-7. The RAN 501 and UE 3 complete the resumption of the RRC connection. The UE 3 moves to the RRC_CONNECTED state.

[0269] Steps 8-9. The RAN 501 performs the path switch procedure with core network 7 including the AMF 7001.

[0270] <First variant of sixth scenario in the First example of the First Aspect> 　　In one example, if the Last serving RAN 502 is shared by multiple PLMN, the Last serving RAN 502 sends the UE Radio Capability ID and the PLMN ID of the UE Radio Capability in the RETRIEVE UE CONTEXT RESPONSE message in Step 4. When the RAN 501 receives the RETRIEVE UE CONTEXT RESPONSE message, then the RAN 501 uses the mapping of UE Radio Capability ID and UE Radio capability associated with the received PLMN to convert the received UE Radio Capability ID to the UE Radio capability.

[0271] <Second variant of sixth scenario in the First example of the First Aspect> 　　In one example, in Steps 2-4, if the RAN 501 is shared by multiple PLMNs, the RAN 501 sends the RETRIEVE UE CONTEXT REQUEST message to the Last serving RAN 502 including a PLMN ID of the current cell where the UE 3 camps. When the Last serving RAN 502 receives the RETRIEVE UE CONTEXT REQUEST message and last serving cell belongs to a different PLMN from the received PLMN in the RETRIEVE UE CONTEXT REQUEST message, then the Last serving RAN 502 may take one of the following steps: - The Last serving RAN 502 sends UE radio capability information in the RETRIEVE UE CONTEXT RESPONSE message either in the existing information element or in the new information element. The Last serving 502 may not send the UE radio capability information ID to the RAN 501 in the RETRIEVE UE CONTEXT RESPONSE message. - The Last serving RAN 502 sends the UE Radio capability ID related to the PLMN of the new cell and the PLMN ID of the new cell in the RETRIEVE UE CONTEXT RESPONSE message if the Last serving RAN 502 has a data base of the UE Radio capability ID for the PLMN ID received in RETRIEVE UE CONTEXT REQUEST message corresponding to the UE Radio Capability information. - The Last serving RAN 502 sends UE radio capability information in the RETRIEVE UE CONTEXT RESPONSE message either in the existing information element or in the new information element. The Last serving 502 may also send the UE Radio capability ID for the PLMN ID received in RETRIEVE UE CONTEXT REQUEST message corresponding to the UE Radio Capability information to the RAN 501 in the RETRIEVE UE CONTEXT RESPONSE message. - In the above cases the RETRIEVE UE CONTEXT RESPONSE may also contain the PLMN ID with the value of the PLMN ID received in the RETRIEVE UE CONTEXT REQUEST message.

[0272] On reception of the RETRIEVE UE CONTEXT RESPONSE message, the RAN 501 takes one of the following actions: - If the RAN 501 receives the UE radio capability ID, then the RAN 501 maps the received UE radio capability ID to the UE radio capability information using a data base (ex. the dictionary) of the UE radio capabilities and corresponding UE Radio capability IEs for the PLMN ID sent in the RETRIEVE UE CONTEXT REQUEST message. The mapped UE radio capability information is for the UE 3 in the RAN 501. - If the RAN 501 receives the UE radio capability information, then the RAN 501 uses the received UE radio capability information for the UE 3 in RAN 501. The RAN 501 may also get the corresponding UE radio capability ID for the PLMN sent in the RETRIEVE UE CONTEXT REQUEST message. - In the above cases, if the PLMN ID is present in RETRIEVE UE CONTEXT RESPONSE message then the RAN 501 uses a data base (ex, the dictionary) of the received PLMN ID to map UE radio capability ID to corresponding UE radio capability information or vice versa.

[0273] <Second example of the First Aspect> 　　This example includes mechanisms that the UE Radio Capability ID is assigned by the participating network and both the assigned UE Radio Capability ID and PLMN ID who assigns the UE Radio Capability ID to the UE 3 (i.e. a PLMN ID of the participating network) are managed in core network 7 and RAN 5.

[0274] <First scenario in the Second example of the First Aspect> 　　The First scenario in the Second example of the First Aspect includes an example mechanism for assigning the UE Radio Capability ID by the participating network during the Registration procedure.

[0275] Fig. 9 illustrates an example of mechanism on assigning the UE Radio Capability ID by the participating network during the Registration procedure.

[0276] The detailed processes of this example are described below with reference to Fig. 9.

[0277] Step 1. Steps 1 to 7 in Fig. 2 take place.

[0278] Step 2. The AMF 7001 sets the PLMN ID of the participating operator in the Nnrf_NFDiscovery_Request message in Step 3. For example, the AMF 7001 is included in a hosting operator network.

[0279] Step 3. The AMF 7001 sends the Nnrf_NFDiscovery_Request message to the NRF 7802 including NF service Name and PLMN ID. The PLMN ID may be the ID of participating operator PLMN. For example, the NRF 7802 is included in a participating operator network.

[0280] The following bullets explain each parameter in detail. - NF service Name: Refer to Step 9 in Fig. 2. - PLMN ID: Refer to Step 9 in Fig. 2.

[0281] Step 4. Upon reception of the Nnrf_NFDiscovery_Request message in Step 3, the NRF 7802 discovers a UCMF (i.e. UCMF 7702) in a PLMN indicated by the PLMN ID, example based on an internal data record within the NRF 7802 and finds a NF profile of the discovered UCMF 7702, example the NF profile is stored in the internal data record within the NRF 7802 and sends an Nnrf_NFDiscovery_Response message to the AMF 7001 including NF profile. The NF profile includes a profile of the discovered UCMF 7702. The NF profile may include NF instance ID, NF type, PLMN ID, FQDN or IP address of NF other profile information as described in section 6.2.6.2 in 3GPP TS 23.501 [2].

[0282] Step 5. The AMF 7001 sends Nucmf_UECapabilityManagement_Assign message to the UCMF 7702 including UE Radio Access Capability and UE Radio Capability for Paging.

[0283] The UE Radio Access Capability and the UE Radio Capability for Paging may be obtained in Step 7 in Fig. 2 as capabilities of the UE 3.

[0284] Step 6. Upon reception of the Nucmf_UECapabilityManagement_Assign message from the AMF 7001 in Step 5, the UCMF 7702 finds a UE Radio Capability ID that corresponds to the received UE Radio Access Capability and the received UE Radio Capability for Paging and sends the UE Radio Capability ID.

[0285] The UCMF 7702 sends the Nucmf_UECapabilityManagement_Assign response message to the AMF 7001 including the UE Radio Capability ID.

[0286] Step 7. Steps 13 to 17 in Fig. 2 take place.

[0287] <First Variant of the First scenario in the Second example of the First Aspect> 　　The Nnrf_NFDiscovery_Request message in Step 3 may be sent from the AMF 7001 to the NRF 7802 via the NRF 7801 in the hosting network.

[0288] Similarly, The Nnrf_NFDiscovery_Response message in Step 4 may be sent from the NRF 7802 to the AMF 7001 via the NRF 7801 in the hosting network.

[0289] <Second Variant of the First scenario in the Second example of the First Aspect> 　　The Nucmf_UECapabilityManagement_Assign message in Step 5 may be sent from the AMF 7001 to the UCMF 7702 via the UCMF 7701 in the hosting network.

[0290] Similarly, The Nucmf_UECapabilityManagement_Assign response message in Step 6 may be sent from the UCMF 7702 to the AMF 7001 via the UCMF 7701 in the hosting network.

[0291] <Second scenario in the Second example of the First Aspect> 　　The Second scenario in the Second example of the First Aspect includes an example mechanism for UE Radio Capability ID Mapping procedure in the hosting network.

[0292] Fig. 10 illustrates an example of mechanism on handling of the UE Radio Capability ID Mapping procedure in the hosting network. 　　Note that this procedure uses non-UE-associated signaling.

[0293] The detailed processes of this example are described below with reference to Fig. 10.

[0294] Step 1. Steps 0 to 1 in Fig. 5 take place.

[0295] Step 2. The AMF 7001 sends the Nnrf_NFDiscovery_Request message to the NRF 7802 including NF service Name and PLMN ID. The AMF 7001 sets the PLMN ID of the host operator in the Nnrf_NFDiscovery_Request message.

[0296] The following bullets explain each parameter in detail. - NF service Name: Refer to Step 9 in Fig. 2. - PLMN ID: Refer to Step 9 in Fig. 2.

[0297] Step 3. Upon reception of the Nnrf_NFDiscovery_Request message in Step 2, the NRF 7802 discovers a UCMF (i.e. UCMF 7702) in a PLMN indicated by the PLMN ID, example based on an internal data record within the NRF 7802 and finds a NF profile of the discovered UCMF 7702, example the NF profile is stored in the internal data record within the NRF 7802 and sends an Nnrf_NFDiscovery_Response message to the AMF 7001 including NF profile. The NF profile includes a profile of the discovered UCMF 7702. The NF profile may include NF instance ID, NF type, PLMN ID, FQDN or IP address of NF other profile information as described in section 6.2.6.2 in 3GPP TS 23.501 [2].

[0298] Step 4. The AMF 7001 sends Nucmf_UECapabilityManagement_Resolve message to the UCMF 7702 including UE Radio Capability ID.

[0299] The following bullets explain each parameter in detail. - UE Radio Capability ID: Refer to Step 3 in Fig. 2.

[0300] Step 5. Upon reception of the Nucmf_UECapabilityManagement_Resolve message from the AMF 7001 in Step 4, the UCMF 7702 finds a UE Radio Access Capability and UE Radio Capability for Paging that corresponds to the received UE Radio Capability ID.

[0301] The UCMF 7702 sends the Nucmf_UECapabilityManagement_Resolve response message to the AMF 7001 including the UE Radio Access Capability and UE Radio Capability for Paging.

[0302] Step 6. Step 6 in Fig. 5 take place.

[0303] <First Variant of the Second scenario in the Second example of the First Aspect> 　　The Nnrf_NFDiscovery_Request message in Step 2 may be sent from the AMF 7001 to the NRF 7802 via the NRF 7801 in the hosting network.

[0304] Likewise, The Nnrf_NFDiscovery_Response message in Step 3 may be sent from the NRF 7802 to the AMF 7001 via the NRF 7801 in the hosting network.

[0305] <Second Variant of the Second scenario in the Second example of the First Aspect> 　　The Nucmf_UECapabilityManagement_ Resolve message in Step 4 may be sent from the AMF 7001 to the UCMF 7702 via the UCMF 7701 in the hosting network.

[0306] Likewise, The Nucmf_UECapabilityManagement_ Resolve response message in Step 5 may be sent from the UCMF 7702 to the AMF 7001 via the UCMF 7701 in the hosting network.

[0307] <Third Variant of the Second scenario in the Second example of the First Aspect> 　　The Nnrf_NFDiscovery_Request message containing PLMN ID in Step 2 may be sent from the AMF 7001 to the NRF 7801 in the hosting network. The NRF 7801 determines the address of NRF 7802 corresponding the received PLMN ID and sends Nnrf_NFDiscovery_Request message containing NF Service name = UCMF and optionally PLMN ID to the NRF 7802. The NRF 7802 returns the IP Address or FQDN of UCMF 7702 to NRF 7801 which in turns return the IP address or FQDN to the AMF 7001 in an existing message between the NRF and AMF. The AMF 7001 access the UCMF 7702 as per Steps 4 and 5.

[0308] <Fourth Variant of the Second scenario in the Second example of the First Aspect> 　　In one example, the FQDN or IP Address of UCMF 7702 is locally configured in the AMF 7001, In this case the AMF 7001 skips Steps 2 and 3 and continues the process with Step 4.

[0309] <System overview> 　　Fig. 11 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, or via non-3GPP access 41, N3IWF 40 and core network 7.

[0310] The N3IWF 40 and non-3GPP access 41 support any non-3GPP RAT including wireless local area network (WLAN) technology as defined by the Institute of Electrical and Electronics Engineers (IEEE)s. The non-3GPP access may be an Untrusted Non-3GPP access or a Trusted Non-3GPP access.

[0311] 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 and a 6G RAT.

[0312] 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.

[0313] 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'.

[0314] 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.

[0315] 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).

[0316] 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).

[0317] 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).

[0318] 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).

[0319] 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.

[0320] 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 Authentication Server Function (AUSF) 76, a AKMA Anchor Function (AAnF) 77, a Network Repository Function (NRF) 78, a Network Exposure Function (NEF) 79 and a Unified Data Repository (UDR) 7A. 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, AAnF 77, NRF 78, NEF 79 and UDR 7A for the roaming-out UE 3.

[0321] The OAM 8 includes, amongst others, Operational functions, Administrational functions and Maintenance related functions. The OAM 8 has interfaces with RAN 5, logical nodes in the core network 7 in a PLMN. In addition, the OAM 8 has interfaces to the AF 201 and other entities that are located in the data network 20.

[0322] 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, AAnF 77, NRF 78, NEF 79 and UDR 7A for the roaming-out UE 3.

[0323] 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.

[0324] The "Uu" interface may include a Control plane of Uu interface and User plane of Uu interface.

[0325] 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 (i.e. PHY sublayer).

[0326] 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.

[0327] For example, the following messages are communicated over the RRC layer to support AS signaling. - 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. - 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 - 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, ue-MeasurementsAvailable, mobilityState, ng-5G-S-TMSI-Part2, registeredAMF, selectedPLMN-Identity, s-NSSAI-List , onboardingRequest

[0328] 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. - 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. - 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. - 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. - 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.

[0329] <User equipment (UE)> 　　Fig. 12 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.

[0330] 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).

[0331] 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.).

[0332] The UE 3 may, for example, be an item of transport equipment (for example transport equipment such as: rolling stocks; motor vehicles; motorcycles; bicycles; trains; buses; carts; rickshaws; ships and other watercraft; aircraft; rockets; satellites; drones; balloons etc.).

[0333] 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.).

[0334] 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.).

[0335] 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.).

[0336] 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.

[0337] 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)).

[0338] 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.

[0339] 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.

[0340] 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.

[0341] 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.

[0342] 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). For a wearable device, the UE 3 may be a reduced capability device (RedCap).

[0343] 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).

[0344] The UE in this disclosure may have same or similar component(s) to the UE 3.

[0345] <N3IWF> 　　Fig. 13 is a block diagram illustrating the main components of an exemplary N3IWF 40. As shown, the apparatus includes a transceiver circuit 401 which is operable to transmit signals to and to receive signals from other nodes or units (including the non-3GPP access 41) via a network interface 402. A controller 403 controls the operation of the N3IWF 40 in accordance with software stored in a memory 404. Software may be pre-installed in the memory 404 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 4041 and a communications control module 4042 having at least a transceiver control module 40421. The communications control module 4042 (using its transceiver control module 40421 is responsible for handling (generating / sending / receiving) signalling between the N3IWF 40 and other nodes or units, such as the non-3GPP access 41 and other nodes and units.

[0346] The N3IWF 40 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).

[0347] The N3IWF in this disclosure may have same or similar component(s) to the N3IWF 40.

[0348] <non-3GPP access> 　　Fig. 14 is a block diagram illustrating the main components of an exemplary non-3GPP access 41. As shown, the non-3GPP access 41 includes a transceiver circuit 411 which is operable to transmit signals to and to receive signals from connected UE(s) 3 via one or more antennas 412 and to transmit signals to and to receive signals from other network nodes or network unit (either directly or indirectly) via a network interface 413. A controller 414 controls the operation of the non-3GPP access 41 in accordance with software stored in a memory 415. 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 4151 and a communications control module 4152 having at least a transceiver control module 41521.

[0349] The communications control module 4152 (using its transceiver control sub-module) is responsible for handling (generating / sending / receiving) signalling between the non-3GPP access 41 and other nodes or units, such as the UE 3 and the N3IWF 40 (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 non-3GPP access 41 for a particular UE 3, and in particular, relating to MAC layer and LLC layer.

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

[0351] The non-3GPP access 41 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).

[0352] The non-3GPP access 41 may be a node, communication apparatus etc. The non-3GPP access 41 may be expressed as a non-3GPP access node.

[0353] The non-3GPP access in this disclosure may have same or similar component(s) to the non-3GPP access 41.

[0354] <(R)AN node> 　　Fig. 15 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.

[0355] 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.

[0356] 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.

[0357] 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).

[0358] The (R)AN node 5 may be expressed as a RAN node, RAN, (R)AN etc.

[0359] The (R)AN in this disclosure may have same or similar component(s) to the (R)AN node 5.

[0360] <System overview of (R)AN node 5 based on O-RAN architecture> 　　Fig. 16 schematically illustrates a (R)AN node 5 based on O-RAN architecture to which the (R)AN node 5 aspects are applicable.

[0361] 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).

[0362] 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).

[0363] 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.

[0364] <Radio Unit (RU)> 　　Fig. 17 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.

[0365] 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.

[0366] 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.

[0367] 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).

[0368] 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.

[0369] The RU in this disclosure may have same or similar component(s) to the RU 60.

[0370] <Distributed Unit (DU)> 　　Fig. 18 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.

[0371] 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).

[0372] 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. 　　The DU in this disclosure may have same or similar component(s) to the DU 61.

[0373] <Centralized Unit (CU)> 　　Fig. 19 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.

[0374] 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).

[0375] 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.

[0376] The CU in this disclosure may have same or similar component(s) to the CU 62.

[0377] <AMF> 　　Fig. 20 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) 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).

[0378] 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).

[0379] The AMF in this disclosure may have same or similar component(s) to the AMF 70.

[0380] <SMF> 　　Fig. 21 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).

[0381] 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).

[0382] The SMF in this disclosure may have same or similar component(s) to the SMF 71.

[0383] <UPF> 　　Fig. 22 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).

[0384] 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).

[0385] The UPF in this disclosure may have same or similar component(s) to the UPF 72.

[0386] <PCF> 　　Fig. 23 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).

[0387] 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).

[0388] The PCF in this disclosure may have same or similar component(s) to the PCF 73.

[0389] <NWDAF> 　　Fig. 24 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).

[0390] 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).

[0391] The NWDAF in this disclosure may have same or similar component(s) to the NWDAF 74.

[0392] <UDM> 　　Fig. 25 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).

[0393] 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).

[0394] The UDM in this disclosure may have same or similar component(s) to the UDM 75.

[0395] <AUSF> 　　Fig. 26 is a block diagram illustrating the main components of the AUSF 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 AUSF 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 AUSF 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).

[0396] The AUSF 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).

[0397] The AUSF in this disclosure may have same or similar component(s) to the AUSF 76.

[0398] <UCMF> 　　Fig. 27 is a block diagram illustrating the main components of the UCMF 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 UCMF 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 UCMF 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).

[0399] The UCMF 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).

[0400] The UCMF in this disclosure may have same or similar component(s) to the UCMF 77.

[0401] <NRF> 　　Fig. 28 is a block diagram illustrating the main components of the NRF 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 NRF 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 NRF 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).

[0402] The NRF 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).

[0403] The NRF in this disclosure may have same or similar component(s) to the NRF 78.

[0404] <NEF> 　　Fig. 29 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).

[0405] 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).

[0406] The NEF in this disclosure may have same or similar component(s) to the NEF 79.

[0407] <UDR> 　　Fig. 40 is a block diagram illustrating the main components of the UDR 7A. As shown, the apparatus includes a transceiver circuit 7A01 which is operable to transmit signals to and to receive signals from other nodes (including the AMF 70) via a network interface 7A02. A controller 7A03 controls the operation of the UDR 7A in accordance with the software stored in a memory 7A04. The Software may be pre-installed in the memory 7A04 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 7A041 and a communications control module 7A042 having at least a transceiver control module 7A0421. The communications control module 7A042 (using its transceiver control module 7A0421 is responsible for handling (generating / sending / receiving) signalling between the UDR 7A 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).

[0408] The UDR 7A 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).

[0409] The UDR in this disclosure may have same or similar component(s) to the UDR 7A.

[0410] <OAM> 　　Fig. 41 is a block diagram illustrating the main components of the OAM 8. As shown, the apparatus includes a transceiver circuit 811 which is operable to transmit signals to and to receive signals from other nodes via a network interface 8012. A controller 813 controls the operation of the OAM 8 in accordance with software stored in a memory 814. Software may be pre-installed in the memory 814 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 8141 and a communications control module 8142 having at least a transceiver control module 81421. The communications control module 8142 (using its transceiver control module 81421 is responsible for handling (generating / sending / receiving) signalling between the OAM 8 and other nodes. 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).

[0411] The OAM 8 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).

[0412] The OAM in this disclosure may have same or similar component(s) to the OAM 8.

[0413] <AF> 　　Fig. 42 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).

[0414] 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).

[0415] The AF in this disclosure may have same or similar component(s) to the AF 201.

[0416] The whole or part of the example Aspects disclosed above can be described as, but not limited to, the following.

[0417] <TS 23.501> <6.3.15　　UCMF Discovery and Selection> 　　The AMF, MME, NEF, AF, SCEF, SCS / AS may utilize the NRF to discover UCMF instance(s) unless UCMF information is available by other means, e.g. locally configured in UCMF services consumers.

[0418] In the case of delegated discovery and selection in SCP, the NF consumer shall forward the request towards SCP.

[0419] The UCMF selection function in UCMF NF consumers or in SCP should consider the following factor when it is available: - 1. The PLMN ID (MCC and MNC) of the selected PLMN in case of INS. This is MCC and MNC of the operator network or the MCC and MNC of the GUAMI of the 5G-GUTI assigned to the UE when the UE has registered to the operator PLMN in case of INS case. 　　In case of Indirect Network Sharing (INS) deployment scenario when a UE registers to the participating network the consumer NF (e.g AMF) sends a Nnrf_NFDiscovery Request message containing home PLMN ID set to the PLMN ID of the selected PLMN of the UE and serving PLMN ID set to host PLMN ID to the NRF of the host PLMN. The NRF of the host PLMN selects participating PLMN NRF corresponding to the PLMN ID received in the Nnrf_NFDiscovery Request message and sends the Nnrf_NFDiscovery Request to participating PLMN NRF. The participating PLMN NRF sends the IP address or FQDN of the UCMF of the participating PLMN to the AMF via NRF of the host PLMN. The NF consumer and the NRF follows the procedure as described in sub clause 4.17.5 of TS 23.02 TheAMF uses this UCMF to get the UE radio capability ID corresponding to the UE radio access capability information and vice versa.

[0420] <TS 23.502> <5.2.7.3　　Nnrf_NFDiscovery service> <5.2.7.3.1　　General> 　　Service description: This service enables one NF or SCP to discover a set of NF instances with specific NF service or a target NF type or one or more SCPs. The service also enables one NF service or SCP to discover a specific NF service. The service operations defined below allow the NF / NF services or SCP to communicate with NRF.

[0421] This service also enables an SCP to discover SCPs.

[0422] NOTE:　　For the purpose of the Nnrf_NFDiscovery service, the SCP is treated in the same way as NFs. It is designated with a specific NF type. However, the SCP does not support services.

[0423] <5.2.7.3.2　　Nnrf_NFDiscovery_Request service operation> 　　Service operation name: Nnrf_NFDiscovery_Request 　　Description: provides the IP address or FQDN of the expected NF instance(s) and if present in NF profile, the Endpoint Address(es) of NF service instance(s) to the NF service consumer or SCP. 　　Inputs, Required: one or more target NF service Name(s), NF type of the target NF, NF type of the NF service consumer.

[0424] If the NF service consumer intends to discover an NF service producer providing all the standardized services, it provides a wildcard NF service name.

[0425] <Inputs, Optional:> -　　S-NSSAI and the associated NSI ID (if available), DNN, target NF / NF service PLMN ID (or realm in the case of network specific identifier type SUCI / SUPI, see clause 4.17.5a), NRF to be used to select NFs / services within HPLMN or Credentials Holder, Serving PLMN ID (or PLMN ID and NID in the case of SNPN, see clause 4.17.5a), the NF service consumer ID, preferred target NF location, TAI.

[0426] NOTE 1:　　For network slicing the NF service consumer ID is a required input.

[0427] -　　FQDN for the S5 / S8 interface of the SMF+PGW-C, to discover the N11 / N16 interface of the SMF+PGW-C in the case of EPS to 5GS mobility.

[0428] -　　If the target NF stores Data Set(s) (e.g. UDR, BSF): SUPI, GPSI, IMPI, IMPU, Data Set Identifier(s). (UE) IPv4 address, IP domain or (UE) IPv6 Prefix.

[0429] NOTE 2:　　GPSI is relevant for BSF.

[0430] NOTE 3:　　If the request includes a subscriber identifier the NRF may need to use the association between the supplied subscriber identifier and the appropriate NF Group ID as described in clause 6.3.1 of TS 23.501 [2] to determine the applicable set of NF instances for the response.

[0431] NOTE 4:　　The (UE) IPv4 address or (UE) IPv6 Prefix is provided for BSF discovery: in that case the NRF looks up for a match within one of the Range(s) of (UE) IPv4 addresses or Range(s) of (UE) IPv6 prefixes provided by BSF(s) as part of the invocation of Nnrf_NFManagement_NFRegister operation. The NRF is not meant to store individual (UE) IPv4 addresses or (UE) IPv6 prefixes.

[0432] -　　If the target NF is UDM or AUSF, the request may include the UE's Routing Indicator, or the UE's Routing Indicator and Home Network Public Key identifier.

[0433] -　　If the target UDM or NF is AUSF, the request may include the UE's HNI: PLMN ID in the case of PLMN, PLMN ID + NID in the case of SNPN. Optionally, some NFs may additionally include a Home Network Identifier in the form of a realm e.g. in the case of access to an SNPN using credentials owned by CH with AAA Server or in the case of SNPN Onboarding using a DCS with AAA Server.

[0434] -　　If the target NF is NSSAAF, the request may include Home Network Identifier in the form of a realm e.g. in the case of access to an SNPN using credentials owned by CH with AAA Server or in the case of SNPN Onboarding using credentials from a DCS with AAA Server.

[0435] -　　If the target NF is AMF and the consumer NF is MB-SMF for broadcast service, the request includes TAI(s) (see clause 7.3 of TS 23.247

[0078] ).

[0436] -　　If the target NF is AMF and the consumer NF is other than MB-SMF, the request may include:

[0437] -　　AMF region, AMF Set, GUAMI and Target TAI(s).

[0438] -　　If the target NF is UDR or UDM or AUSF or PCF or BSF, the request may include UDR Group ID or UDM Group ID or AUSF Group ID or PCF Group ID or BSF Group ID respectively.

[0439] NOTE 5:　　It is assumed that the corresponding NF service consumer is either configured with the corresponding Group ID or it received it via earlier Discovery output.

[0440] -　　If the target NF is UDM, the request may include SUPI, GPSI, Internal Group ID and External Group ID.

[0441] -　　If the target NF is UPF, the request may include SMF Area Identity, UE IPv4 Address / IPv6 Prefix, supported ATSSS steering functionality, the supported UPF event exposure service, the supported Event IDs that can be subscribed, supported operator configurable UPF capabilities, support of NAT information exposure functionality and support of IP or MAC filter-based packet detection functionality. And if UPF can expose NAT information, the UE IPv4 address / IPv6 Prefix seen by the DN (e.g. a Public IP address).

[0442] NOTE 6:　　If UE's IPv4 address or IPv6 Prefix is provided for UPF discovery, then the NRF looks up for a match within one of the Range(s) of IPv4 addresses or IPv6 prefixes provided by UPF in the NF profile at the invocation of Nnrf_NFManagement_NFRegister operation. The NRF is not meant to store the UE's individual IPv4 addresses or IPv6 prefixes.

[0443] NOTE 7:　　Discovering UPF at PDU Session Establishment time and creating the N4 association assumes full connectivity between SMF and UPFs.

[0444] -　　If the target NF is CHF, the request may include SUPI or GPSI as specified in TS 32.290

[0042] .

[0445] -　　If the target NF is PCF or SMF, the request may include the MA PDU Session capability to indicate that a NF instance supporting MA PDU session capability is requested.

[0446] -　　If the target NF is PCF, the request may include the DNN replacement capability to indicate that a NF instance supporting DNN replacement capability is preferred.

[0447] -　　If the target NF is PCF or SMF, the request may include the slice replacement capability to indicate that a NF instance supporting slice replacement capability is preferred.

[0448] -　　If the target NF is PCF, the request may include the 5G ProSe Capability as specified in TS 23.304

[0077] .

[0449] -　　If the target NF is PCF, the request may include the V2X capability as specified in TS 23.287

[0073] .

[0450] -　　If the target NF is PCF, the request may include the A2X capability as specified in TS 23.256

[0080] .

[0451] -　　If the target NF is PCF, the request may include the URSP delivery in EPS capability.

[0452] -　　If the target NF is PCF, the request may include the Ranging / SL Positioning Capability as specified in TS 23.586

[0088] .

[0453] -　　If the target NF is NWDAF, the request may include:

[0454] -　　Analytics ID(s) (possibly per service).

[0455] -　　TAI(s).

[0456] -　　Analytics aggregation capability and / or Analytics metadata provisioning capability.

[0457] -　　A Real-Time Communication Indication per Analytics ID, NF Set ID and NF Type of the NF data sources.

[0458] -　　Roaming exchange capability if data / analytics exchange between PLMNs is needed.

[0459] -　　The S-NSSAI(s), Area(s) of Interest of the Trained ML Model required and NF consumer information when the target is an NWDAF containing MTLF.

[0460] -　　For HFL, required FL capability type (i.e. FL server, FL client, if available) and Time period of interest when the target is an NWDAF containing MTLF with HFL capability. When the target is an NWDAF containing MTLF with HFL client capability, NF Set ID(s) of data source and NF type(s) where data can be collected as input for local model training may be included.

[0461] -　　Required VFL capability type (i.e. VFL server, VFL client, if available) and optional Time period of interest when the target is an NWDAF containing MTLF with VFL capability. When the VFL capability type indicates VFL client, the NWDAF also includes the VFL interoperability indicator, per Analytics ID and optionally supported Feature IDs.

[0462] -　　If the target NF is NWDAF containing MTLF with ML Model Accuracy checking capability, it includes ML Model Accuracy checking capability for ML model Accuracy Monitoring (see clause 5.2 of TS 23.288

[0050] ).

[0463] -　　If the target NF is NWDAF containing AnLF with Analytics Accuracy checking capability, it includes Analytics Accuracy checking capability for Analytics Accuracy Monitoring (see clause 5.2 of TS 23.288

[0050] ).

[0464] Details about NWDAF discovery and selection are described in clause 6.3.13 of TS 23.501 [2].

[0465] NOTE 8:　　Analytics metadata provisioning capability is only applicable when NF service consumer is NWDAF.

[0466] NOTE 9:　　NF consumer information such as vendor ID is defined in stage 3.

[0467] -　　If target NF is ADRF, the request may include:

[0468] -　　Data and analytics storage and retrieval capability.

[0469] -　　ML model storage and retrieval capability.

[0470] Details about ADRF discovery and selection are described in clause 6.3.20 of TS 23.501 [2].

[0471] -　　If the target NF is HSS, the request may include IMPI and / or IMPU and / or HSS Group ID.

[0472] -　　If the NF service consumer needs to discover NF service producer instance(s) within an NF instance, the request includes the target NF Instance ID and NF Service Set ID of the producer.

[0473] -　　If the NF service consumer needs to discover NF service producer instance(s) in an equivalent NF Service Set within an NF Set, the request includes the identification of the equivalent NF service Set and NF Set ID of producer.

[0474] NOTE 10:　　TS 29.510

[0037] specifies the mechanism to identify equivalent NF Service Sets.

[0475] -　　If the NF service consumer needs to discover NF service producer instance(s) in the NF Set, the request includes the target NF Set ID of the producer.

[0476] -　　If the target NF is SMF, the request may include:

[0477] -　　the UE location (TAI); or

[0478] -　　information about the location or serving scope of SMF (operator specific information, e.g. geographical location, data centre) considering UE location; or

[0479] -　　TAI list.

[0480] -　　If the target NF is P-CSCF, the request may include UE location information, UE IP address / IP prefix, Access Type.

[0481] -　　If the target NF is NEF, the request may include Event ID(s) provided by AF and optional AF identification as described in clause 6.2.2.3 of TS 23.288

[0050] . The request may also include required AF's VFL capability type (i.e. VFL client, if available), optional Time Period of Interest, per Analytics ID, VFL interoperability indicator, per Analytics ID, optionally supported Feature IDs and Service Area. When the consumer is an AF, the request may include an External Identifier, External Group Identifier, or a domain name. If the target NF is local NEF, the request may include the parameters of list of supported TAI or list of supported DNAI additionally.

[0482] -　　If the target NF is SMF, the request may include the Control Plane CIoT 5GS Optimisation Indication or User Plane CIoT 5GS Optimisation Indication.

[0483] -　　If the target NF is a NSACF, the request may include the S-NSSAI(s) of the PLMN or SNPN where the NSACF is located , the NSAC Service Area Identifier and NSACF service capability. Details about NSACF discovery and selection are described in clause 6.3.22 of TS 23.501 [2].

[0484] -　　If the target NF is SCP, the request may include information about:

[0485] -　　SCP domain(s).

[0486] -　　Remote PLMN reachable through SCP.

[0487] -　　Endpoint addresses or Address Domain(s) (e.g. IP Address or FQDN ranges) accessible via the SCP.

[0488] -　　NF sets of NFs served by the SCP.

[0489] -　　If the target NF is MB-SMF, the request may include UE location (i.e. TAI), MBS Session ID and Area Session ID. Details about MB-SMF discovery and selection are described in TS 23.247

[0078] .

[0490] -　　If the target NF is 5G DDNMF, the request may include SUPI, IP Address or FQDN of 5G DDNMF.

[0491] -　　If the target NF is DCCF, the request may include TAI(s), NF type of the NF data sources, NF Set ID of the NF data sources, support for relocation of data subscription. Details about DCCF discovery and selection are described in clause 6.3.19 of TS 23.501 [2].

[0492] -　　If the target NF is EASDF, the request may include S-NSSAI, DNN, N6 IP address of the PSA UPF, Supported DNS security protocols, location as per NF profile and DNAI(if exist). Details about EASDF discovery and selection are described in clause 6.3.23 of TS 23.501 [2].

[0493] -　　If the target NF is AMF, the request may include the support of SNPN Onboarding to indicate whether the target NF instance supports SNPN Onboarding or not.

[0494] -　　If the target NF is SMF, the request may include the support of User Plane Remote Provisioning to indicate whether the target NF instance supports User Plane Remote Provisioning or not as described in clause 5.30.2.10.4.3 of TS 23.501 [2].

[0495] -　　If the target NF is NEF, the request may include the support of UAS NF functionality, the capability to support Multi-member AF session with required QoS and the capability to support member UE selection assistance functionality.

[0496] -　　If the target NF is NSSAAF, the request may include SUPI or Internal Group ID.

[0497] -　　If the target NF is DCSF, the request may include IMPU of calling party, SIP URI or Tel URI of called party.

[0498] -　　If the target NF is MF, the request may include the list of required data channel media capabilities or MF location information as specified in TS 23.228

[0055] .

[0499] -　　If the target NF is IMS AS, the request may include the list of supported IMS DC events.

[0500] -　　If the target NF is MRF or MRFP, it includes the list of required IMS media services (as defined in TS 23.228

[0055] ).

[0501] -　　If the target NF is in another PLMN or domain, the request may include an indication of "support of the indirect communication with delegated discovery with NF selection at target domain feature" and / or an indication of "support of indirect communication without delegated discovery with NF selection at target domain feature".

[0502] -　　if the target NF is UCMF and in case of INS deployment scenario the request may include home PLMN ID set to the PLMN ID of the selected PLMN of the UE and serving PLMN ID set to host PLMN ID.

[0503] <Outputs, Required> -　　One of the following:

[0504] -　　A set of NF instance profiles; or

[0505] -　　an indication that "indirect communication with delegated discovery with NF selection at target domain is requested"; or

[0506] -　　an indication that "indirect communication without delegated discovery with NF selection at target domain is requested" together with a set of NF instance profiles;

[0507] -　　a validity period for the discovery result.

[0508] The set of NF instance profiles shall contain per NF Instance: NF type, NF instance ID, FQDN or IP address(es) of the NF instance and if applicable, a list of services instances, where each service instance has a service name, a NF service instance ID and optionally Endpoint Address(es)

[0509] Endpoint Address(es) may be a list of IP addresses or an FQDN for the NF service instance.

[0510] NOTE 11:　　SCPs does not have any service instances. 　　Outputs, Optional: Per NF instance, other information in the NF profile listed in clause 6.2.6 of TS 23.501 [2] related to the NF instance, such as:

[0511] -　　NF load information.

[0512] -　　NF capacity information.

[0513] -　　NF priority information.

[0514] -　　If the target NF stores Data Set(s) (e.g. UDR): Range(s) of SUPIs, range(s) of GPSIs, range(s) of external group identifiers, Data Set Identifier(s). If the target NF is BSF or P-CSCF: Range(s) of (UE) IPv4 addresses or Range(s) of (UE) IPv6 prefixes, Range(s) of SUPIs, range(s) of GPSIs.

[0515] NOTE 12:　　Range of SUPI(s) is limited in this release to a SUPI type of IMSI as defined in TS 23.003

[0033] .

[0516] -　　If the target NF is UDM, UDR, PCF, BSF or AUSF, they can include UDM Group ID, UDR Group ID, PCF Group ID, BSF Group ID, AUSF Group ID respectively.

[0517] -　　If the target NF is HSS, it can include HSS Group ID.

[0518] -　　For UDM and AUSF, Routing Indicator, or Routing Indicator and Home Network Public Key identifier.

[0519] -　　If the target NF is AMF, it includes list of GUAMI(s). In addition, it may include list of GUAMI(s) for which it can serve as backup for failure / maintenance.

[0520] -　　If the target NF is CHF, it includes primary CHF instance and the secondary CHF instance pair(s), if configured in CHF instance profile.

[0521] -　　For the UPF Management: UPF Provisioning Information as defined in clause 4.17.6.

[0522] -　　S-NSSAI(s) and the associated NSI ID(s) (if available).

[0523] -　　Information about the location or serving scope of the target NF (operator specific information, e.g. geographical location, data centre).

[0524] -　　TAI(s).

[0525] -　　PLMN ID.

[0526] -　　If the target is PCF or SMF, it includes the MA PDU Session capability to indicate if the NF instance supports MA PDU session or not.

[0527] -　　If the target is PCF, it includes the DNN replacement capability to indicate if the NF instance supports DNN replacement or not.

[0528] -　　If the target NF is NWDAF, it may include:

[0529] -　　Analytics ID(s) (possibly per service).

[0530] -　　NF Set ID and NF Type of the NF data sources, if available, NWDAF Serving Area information.

[0531] -　　Analytics aggregation capability and / or Analytics metadata provisioning capability, if such capability is provided by the NWDAF.

[0532] -　　Supported Analytics Delay per Analytics ID.

[0533] -　　If the target NF is NWDAF, it may also include the ML model Filter information parameters S-NSSAI(s) and Area(s) of Interest for the trained ML model(s) per Analytics ID(s) and ML Model Interoperability indicator per Analytics ID(s), if available (see clause 5.2 of TS 23.288

[0050] ).

[0534] -　　If the target NF is NWDAF with FL capability, it may also include FL capability information per analytics ID containing FL capability type (i.e. FL server and / or FL client, if available) and Time interval supporting FL, if available (see clause 5.2 of TS 23.288

[0050] ).

[0535] -　　If the target NF is NWDAF with the VFL capability, it may include VFL capability information per Analytics ID containing VFL capability type (i.e. VFL server, VFL client, or both, if available) and optional Time interval supporting VFL, if available. When the VFL capability type indicates VFL client, the NWDAF also includes the VFL interoperability indicator, per Analytics ID and optionally supported Feature IDs (see clause 5.2 of TS 23.288

[0050] ).

[0536] Details about NWDAF specific information are described in clause 6.3.13 of TS 23.501 [2].

[0537] NOTE 13:　　The Supported Analytics Delay is provided for an Analytics ID only when the NRF had received Real-Time Communication Indication for this Analytics ID in the NWDAF discovery request.

[0538] -　　If the target is a trusted AF, it includes one or multiple combination(s) of the S-NSSAI and DNN corresponding to the AF. In addition, it may include supported Application Id(s), Event ID(s) supported by the AF and Internal-Group Identifier.

[0539] -　　NF Set ID.

[0540] -　　NF Service Set ID.

[0541] -　　If the target NF is SMF, it may include the SMF(s) Service Area.

[0542] NOTE 14:　　If neither SMF Service Area nor serving scope of SMF is provided, the AMF assumes that the SMF can serve the whole PLMN.

[0543] -　　If the target NF is P-CSCF, it includes P-CSCF FQDN(s) or IP address(es) and optional Access Type(s) associated with each P-CSCF.

[0544] -　　If the target NF is NEF, it may include Event ID(s) provided by AF and / or it may include AF's VFL capability type (i.e. VFL client, if available) and optional Time Period of Interest, per Analytics ID, VFL interoperability indicator, per Analytics ID, optionally supported Feature IDs, Service Area and / or it includes one or multiple combination(s) of the S-NSSAI and DNN corresponding to the untrusted AF served by the NEF.

[0545] -　　SCP domain the NF belongs to.

[0546] NOTE 15:　　Only one SCP domain is registered in NF profile for an NF.

[0547] -　　If the target is SCP:

[0548] -　　SCP domain(s).

[0549] -　　Remote PLMNs reachable through SCP.

[0550] -　　Endpoint addresses or Address Domain(s) (e.g. IP Address or FQDN ranges) accessible via the SCP.

[0551] -　　NF sets of NFs served by the SCP.

[0552] -　　If the target NF is 5G DDNMF, it may include IP Address or FQDN of 5G DDNMF.

[0553] -　　If the target NF is MB-SMF, it may include the MBS Session ID(s), Area Session ID(s), corresponding MBS service area(s) as described in TS 23.247

[0078] .

[0554] -　　If the target NF is DCCF, it includes DCCF serving area information, NF type of the NF data sources, NF Set ID of the NF data sources, support for relocation of data subscription. Details about DCCF specific information are described in clause 6.3.19 of TS 23.501 [2].

[0555] -　　If an indication that "indirect communication with delegated discovery with NF selection at target domain is requested" or an "indication that "indirect communication without delegated discovery with NF selection at target domain is requested" is provided, optionally:

[0556] -　　an indication that the reply applies to all NF types; and / or

[0557] -　　the address of an SCP where to send the request.

[0558] See clause 4.17.4 and 4.17.5 for details on the usage of this service operation.

[0559] <TS 38.413> <8.3.1.2　　Successful Operation> 　　The M-NG-RAN node initiates the procedure by sending the S-NODE ADDITION REQUEST message to the S-NG-RAN node.

[0560] When the M-NG-RAN node sends the S-NODE ADDITION REQUEST message, it shall start the timer TXnDCprep.

[0561] The allocation of resources according to the values of the Allocation and Retention Priority IE included in the QoS Flow Level QoS Parameters IE for each QoS flow shall follow the principles specified for the PDU Session Resource Setup procedure in TS 38.413 [5].

[0562] The S-NG-RAN node shall choose the ciphering algorithm based on the information in the UE Security Capabilities IE and locally configured priority list of AS encryption algorithms and apply the key indicated in the S-NG-RAN node Security Key IE as specified in TS 33.501

[0028] .

[0563] If the TSC Traffic Characteristics IE is included for a QoS flow in the S-NODE ADDITION REQUEST message, the S-NG-RAN node shall behave the same as the NG-RAN node in the PDU Session Resource Setup procedure, specified in TS 38.413 [5].

[0564] If the Additional QoS Flow Information IE is included for a QoS flow in the S-NODE ADDITION REQUEST message, the S-NG-RAN node shall behave the same as the NG-RAN node in the PDU Session Resource Setup procedure, specified in TS 38.413 [5].

[0565] For each GBR QoS flow, if the Alternative QoS Parameters Set List IE is included in the GBR QoS Flow Information IE, the S-NG-RAN node shall, if supported, behave the same as the NG-RAN node in the PDU Session Resource Setup procedure specified in TS 38.413 [5].

[0566] For each PDU session, if the Network Instance IE is included in the PDU Session Resource Setup Info - SN terminated IE contained in the PDU Session Resources To Be Added List IE and the Common Network Instance IE is not present, the S-NG-RAN node shall, if supported, use it when selecting transport network resource as specified in TS 23.501 [7].

[0567] For each GBR QoS flow, if the Offered GBR QoS Flow Information IE is included in the QoS Flows To Be Setup List IE contained in the PDU Session Resource Setup Info - SN terminated IE, the S-NG-RAN node may request the M-NG-RAN node to configure the DRB to which that QoS flow is mapped with MCG resources.

[0568] For each PDU session, if the Non-GBR Resources Offered IE is included in the PDU Session Resource Setup Info - SN terminated IE contained in the PDU Session Resources To Be Added List IE and set to "true", the S-NG-RAN node may request the M-NG-RAN node to configure DRBs to which non-GBR QoS flows of the PDU session are mapped with MCG resources.

[0569] For each PDU session, if the Common Network Instance IE is included in the PDU Session Resource Setup Info - SN terminated IE contained in the PDU Session Resources To Be Added List IE, the S-NG-RAN node shall, if supported, use it when selecting transport network resource as specified in TS 23.501 [7].

[0570] <Redundant transmission> -　　For each PDU session, if the Redundant UL NG-U UP TNL Information at UPF IE is included in the PDU Session Resource Setup Info - SN terminated IE, the S-NG-RAN node shall, if supported, use it as the uplink termination point for the user plane data for this PDU session for the redundant transmission and it shall include the Redundant DL NG-U UP TNL Information at NG-RAN IE in the PDU Session Resource Setup Response Info - SN terminated IE as described in TS 23.501 [7].

[0571] -　　For each PDU session, if the Redundant Common Network Instance IE is included in the PDU Session Resource Setup Info - SN terminated IE the S-NG-RAN node shall, if supported, use it when selecting transport network resource for the redundant transmission as specified in TS 23.501 [7].

[0572] -　　For each PDU session for which the Redundant QoS Flow Indicator IE is include in QoS Flows To Be Setup List IE contained in the S-NODE ADDITION REQUEST message, the S-NG-RAN node shall, if supported, store and use it as specified in TS 23.501 [7].

[0573] -　　For each PDU session, if the Redundant PDU Session Information IE is included in the PDU Session Resource Setup Info - SN terminated IE in the S-NODE ADDITION REQUEST message, the S-NODE-RAN node shall, if supported, store the received information in the UE context and setup the redundant user plane resources for the concerned PDU session, as specified in TS 23.501 [7].

[0574] -　　For each PDU session resource successfully setup for which the Redundant PDU Session Information IE is included in the S-NODE ADDITION REQUEST message, the S-NG-RAN node shall, if supported, include the Used RSN Information IE in the PDU Session Resource Setup Response Info - SN terminated IE in the S-NODE ADDITION REQUEST ACKNOWLEDGE message. If the PDU Session Pair ID IE is included in the Redundant PDU Session Information IE, the S-NG-RAN node may store and use it to identify the paired PDU sessions.

[0575] If the S-NODE ADDITION REQUEST message contains the Selected PLMN IE, the S-NG-RAN node may use it for RRM purposes. If the S-NODE ADDITION REQUEST message also contains the Selected NID IE, the S-NG-RAN node may decide to use the SNPN identified by the Selected PLMN IE and Selected NID IE for its own usage.

[0576] If the S-NODE ADDITION REQUEST message contains the Expected UE Behaviour IE, the S-NG-RAN node shall, if supported, store this information and may use it to optimize resource allocation.

[0577] If the S-NODE ADDITION REQUEST message contains the Mobility Restriction List IE, the S-NG-RAN node, if supported, shall store this information and use it to select an appropriate SCG.

[0578] If the S-NODE ADDITION REQUEST message contains the Index to RAT / Frequency Selection Priority IE, the S-NG-RAN node may use it for RRM purposes.

[0579] If the S-NG-RAN node is a gNB and the S-NODE ADDITION REQUEST message contains the PCell ID IE, the S-NG-RAN node shall search for the target NR cell among the NR neighbour cells of the PCell indicated, as specified in the TS 37.340 [8].

[0580] If the S-NODE ADDITION REQUEST message contains the S-NG-RAN node PDU Session Aggregate Maximum Bit Rate IE, the S-NG-RAN node may use it for RRM purposes.

[0581] If the S-NODE ADDITION REQUEST message contains the MR-DC Resource Coordination Information IE, the S-NG-RAN node should forward it to lower layers and it may use it for the purpose of resource coordination with the M-NG-RAN node, or to coordinate with sidelink resources used in the M-NG-RAN node. The S-NG-RAN node shall consider the value of the received UL Coordination Information IE valid until reception of a new update of the IE for the same UE. The S-NG-RAN node shall consider the value of the received DL Coordination Information IE valid until reception of a new update of the IE for the same UE. If the E-UTRA Coordination Assistance Information IE or the NR Coordination Assistance Information IE is contained in the MR-DC Resource Coordination Information IE, the S-NG-RAN node shall, if supported, use the information to determine further coordination of resource utilisation between the S-NG-RAN node and the M-NG-RAN node.

[0582] If the S-NODE ADDITION REQUEST message contains the NE-DC TDM Pattern IE, the S-NG-RAN node should forward it to lower layers and use it for the purpose of single uplink transmission. The S-NG-RAN node shall consider the value of the received NE-DC TDM Pattern IE valid until reception of a new update of the IE for the same UE.

[0583] If the S-NODE ADDITION REQUEST message contains the QoS Flow Mapping Indication IE, the S-NG-RAN node may take it into account that only the uplink or downlink QoS flow is mapped to the DRB.

[0584] For each bearer for which allocation of the PDCP entity is requested at the S-NG-RAN node:

[0585] -　　the M-NG-RAN node may propose to apply forwarding of downlink data by including the DL Forwarding IE within PDU Session Resource Setup Info - SN terminated IE of the S-NODE ADDITION REQUEST message. For each bearer that it has decided to admit, the S-NG-RAN node may include the DL Forwarding GTP Tunnel Endpoint IE within the PDU Session Resource Setup Response Info - SN terminated IE of the S-NODE ADDITION REQUEST ACKNOWLEDGE message to indicate that it accepts the proposed forwarding of downlink data for this bearer.

[0586] -　　the S-NG-RAN node may include for each bearer in the PDU Session Resource Setup Response Info - SN terminated IE the UL Forwarding GTP Tunnel Endpoint IE to indicates it request data forwarding of uplink packets to be performed for that bearer.

[0587] -　　the M-NG-RAN node shall include RLC Mode IE for each bearer offloaded from M-NG-RAN node to S-NG-RAN node in the DRBs to QoS Flow Mapping List IE within the PDU Session Resource Setup Info - SN terminated IE of the S-NODE ADDTION REQUEST message, and the RLC Mode IE indicates the mode that the M-NG-RAN used for the DRB when it was hosted at the M-NG-RAN node.

[0588] For each bearer for which the PDCP entity is at the M-NG-RAN node:

[0589] -　　the M-NG-RAN node shall include the RLC mode IE for each bearer in the DRBs To Be Setup List IE within the PDU Session Resource Setup Info - MN terminated IE of the S-NODE ADDTION REQUEST message to indicate the RLC mode has been configured at the M-NG-RAN node, so that the S-NG-RAN node shall configure the same RLC mode for this MN terminated split bearer.

[0590] The M-NG-RAN node may also propose to apply forwarding of UL data when offloading QoS flows for which in-order delivery is requested by including the UL Forwarding Proposal IE in the Data Forwarding and Offloading Info from source NG-RAN node IE within the PDU Session Resource Setup Info - SN terminated IE of the S-NODE ADDITION REQUEST message. The S-NG-RAN node may include the PDU Session level UL data Forwarding UP TNL Information IE in the Data Forwarding Info from target NG-RAN node IE within the PDU Session Resource Setup Response Info - SN terminated IE of the S-NODE ADDITION REQUEST ACKNOWLEDGE message to indicate that it accepts the proposed forwarding.

[0591] If the Masked IMEISV IE is contained in the S-NODE ADDITION REQUEST message the S-NG-RAN node shall, if supported, use it to determine the characteristics of the UE for subsequent handling.

[0592] If the UE Radio Capability ID IE is contained in the S-NODE ADDITION REQUEST message, the S-NG-RAN node shall, if supported, store this information in the UE context and use it as defined in TS 23.501 [7] and TS 23.502

[0013] . If the PLMN ID assigning the UE Radio Capability ID is included, the S-NG-RAN node derives the UE radio capability information mapped to UE Radio Capability ID for the PLMN sent in PLMN ID assigning the UE Radio Capability ID.

[0593] The S-NG-RAN node shall report to the M-NG-RAN node, in the S-NODE ADDITION REQUEST ACKNOWLEDGE message, the result for all the requested PDU session resources in the following way:

[0594] -　　A list of PDU session resources which are successfully established shall be included in the PDU Session Resources Admitted To Be Added List IE.

[0595] -　　A list of PDU session resources which failed to be established shall be included in the PDU Session Resources Not Admitted List IE.

[0596] Upon reception of the S-NODE ADDITION REQUEST ACKNOWLEDGE message the M-NG-RAN node shall stop the timer TXnDCprep.

[0597] If the S-NODE ADDITION REQUEST ACKNOWLEDGE message contains the MR-DC Resource Coordination Information IE, the M-NG-RAN node may use it for the purpose of resource coordination with the S-NG-RAN node. The M-NG-RAN node shall consider the value of the received UL Coordination Information IE valid until reception of a new update of the IE for the same UE. The M-NG-RAN node shall consider the value of the received DL Coordination Information IE valid until reception of a new update of the IE for the same UE. If the E-UTRA Coordination Assistance Information IE or the NR Coordination Assistance Information IE is contained in the MR-DC Resource Coordination Information IE, the M-NG-RAN node shall, if supported, use the information to determine further coordination of resource utilisation between the M-NG-RAN node and the S-NG-RAN node.

[0598] The S-NG-RAN node may include for each bearer in the DRBs To Be Setup List IE in the S-NODE ADDITION REQUEST ACKNOWLEDGE message the PDCP SN Length IE to indicate the PDCP SN length for that DRB.

[0599] If the S-NG-RAN node UE XnAP ID IE is contained in the S-NODE ADDITION REQUEST message, the S-NG-RAN node shall, if supported, store this information and use it as defined in TS 37.340 [8].

[0600] If the S-NODE ADDITION REQUEST message contains the PDCP SN Length IE, the S-NG-RAN node shall, if supported, store this information and use it for lower layer configuration of the concerned MN terminated bearer.

[0601] If the S-NODE ADDITION REQUEST message contains the SN Addition Trigger Indication IE, the S-NG-RAN node shall include the RRC config indication IE in the S-NODE ADDITION REQUEST ACKNOWLEDGE message to inform the M-NG-RAN node if the S-NG-RAN node applied full or delta configuration, as specified in TS 37.340 [8].

[0602] If the S-NODE ADDITION REQUEST message contains the S-NG-RAN node Maximum Integrity Protected Data Rate Uplink IE or the S-NG-RAN node Maximum Integrity Protected Data Rate Downlink IE, the S-NG-RAN node shall use the received information when enforcing the maximum integrity protected data rate for the UE.

[0603] If the Security Indication IE is included in the PDU Session Resource Setup Info - SN terminated IE of the S-NODE ADDITION REQUEST message, the behaviour of the S-NG-RAN node shall be the same as specified for the same IE in the PDU Session Resources To Be Setup List IE in the Handover Preparation procedure, for the concerned PDU session, and the S-NG-RAN node shall include the Security Result IE in the PDU Session Resource Setup Response Info - SN terminated IE. If either the S-NG-RAN node or the M-NG-RAN node is an ng-eNB, the S-NG-RAN node shall behave as specified in TS 33.501

[0028] .

[0604] If the Security Result IE is included in the PDU Session Resource Setup Info - SN terminated IE of the S-NODE ADDITION REQUEST message, the S-NG-RAN node may take the information into account when deciding whether to perform user plane integrity protection or ciphering for the DRBs that it establishes for the concerned PDU session, except if the Split Session Indicator IE is included in the PDU Session Resource Setup Info - SN terminated IE and set to "split", in which case it shall perform user plane integrity protection or ciphering according to the information in the Security Result IE.

[0605] The S-NG-RAN node may include the Location Information at S-NODE IE in the S-NODE ADDITION REQUEST ACKNOWLEDGE message, if respective information is available at the S-NG-RAN node.

[0606] If the Location Information at S-NODE reporting IE set to "pscell" is included in the S-NODE ADDITION REQUEST, the S-NG-RAN node shall, start providing information about the current location of the UE. If the Location Information at S-NODE IE is included in the S-NODE ADDITION REQUEST ACKNOWLEDGE, the M-NG-RAN node shall store the included information so that it may be transferred towards the AMF.

[0607] If the Default DRB Allowed IE is included in the PDU Session Resource Setup Info - SN terminated IE of the S-NODE ADDITION REQUEST message and set to "true", the S-NG-RAN node may configure the default DRB for the PDU session.

[0608] If the S-NODE ADDITION REQUEST ACKNOWLEDGE message includes the DRB IDs taken into use IE, the M-NG-RAN node, if applicable, shall act as specified in TS 37.340 [8].

[0609] If Trace Activation IE has previously been received for this UE, it shall be included in the S-NODE ADDITION REQUEST message. If the Trace Activation IE is included in the S-NODE ADDITION REQUEST message, the S-NG-RAN node shall, if supported, initiate the requested trace function as described in TS 32.422

[0023] .

[0610] If the Trace Activation IE is included in the S-NODE ADDITION REQUEST message which includes:

[0611] -　　the MDT Activation IE set to "Immediate MDT and Trace", then the S-NG-RAN node shall if supported, initiate the requested trace session and MDT session as described in TS 32.422

[0023] .

[0612] -　　the MDT Activation IE set to "Immediate MDT Only", the S-NG-RAN node shall, if supported, initiate the requested MDT session as described in TS 32.422

[0023] and the S-NG-RAN node shall ignore the Interfaces To Trace IE, and the Trace Depth IE.

[0613] -　　the MDT Location Information IE, within the MDT Configuration IE, the S-NG-RAN node shall, if supported, store this information and take it into account in the requested MDT session.

[0614] -　　the MDT Activation IE set to "Immediate MDT Only", and if the Signalling based MDT PLMN List IE is included in the MDT Configuration IE, the S-NG-RAN node may use it to propagate the MDT Configuration as described in TS 37.320

[0043] .

[0615] -　　the Bluetooth Measurement Configuration IE, within the MDT Configuration IE, the S-NG-RAN node shall, if supported, take it into account for MDT Configuration as described in TS 37.320

[0043] .

[0616] -　　the WLAN Measurement Configuration IE, within the MDT Configuration IE, the S-NG-RAN node shall, if supported, take it into account for MDT Configuration as described in TS 37.320

[0043] .

[0617] -　　the Sensor Measurement Configuration IE, within the MDT Configuration IE, the S-NG-RAN node shall take it into account for MDT Configuration as described in TS 37.320

[0043] .

[0618] -　　the MDT Configuration IE and if the S-NG-RAN node is a gNB at least the MDT Configuration-NR IE shall be present, while if the S-NG-RAN Node is an ng-eNB at least the MDT Configuration-EUTRA IE shall be present.

[0619] If the Area Scope IE is not present in the MDT Configuration IE, the S-NG-RAN node shall consider that the MDT Configuration is applied to all PLMNs indicated in the MDT PLMN List, as described in TS 32.422

[0023] .

[0620] If the Requested Fast MCG recovery via SRB3 IE set to "true" is included in the S-NODE ADDITION REQUEST message and the S-NG-RAN node decides to configure fast MCG link recovery via SRB3 as specified in TS 37.340 [8], the S-NG-RAN node shall, if supported, include the Available fast MCG recovery via SRB3 IE set to "true" in the S-NODE ADDITION REQUEST ACKNOWLEDGE message.

[0621] If the QoS Monitoring Request IE is included in the QoS Flow Level QoS Parameters IE for a QoS flow contained in the DRBs To Be Setup List IE of the PDU Session Resource Setup Info - MN terminated IE, the S-NG-RAN node shall, if supported, use it to configure lower layers for the purpose of delay measurement and QoS monitoring as specified in TS 23.501 [7]. If the QoS Monitoring Reporting Frequency IE is included in the QoS Flow Level QoS Parameters IE for a QoS flow contained in the DRBs To Be Setup List IE of the PDU Session Resource Setup Info - MN terminated IE, the S-NG-RAN node shall, if supported, use it for RAN part delay reporting.

[0622] For each QoS flow which has been successfully established in the S-NG-RAN node, if the QoS Monitoring Request IE was included in the QoS Flow Level QoS Parameters IE contained in the PDU Session Resource Setup Info - SN terminated IE, the S-NG-RAN node shall store this information, and shall, if supported, perform delay measurement and QoS monitoring as specified in TS 23.501 [7]. If the QoS Monitoring Reporting Frequency IE was included in the QoS Flow Level QoS Parameters IE contained in the PDU Session Resource Setup Info - SN terminated IE, the S-NG-RAN node shall store this information, and shall, if supported, use it for RAN part delay reporting. In case such a QoS flow is included in the DRBs To Be Setup List IE of the PDU Session Resource Setup Response Info - SN terminated IE, the M-NG-RAN node shall, if supported, use it to configure lower layers for the purpose of delay measurement and QoS monitoring. If the QoS Monitoring Reporting Frequency IE is included in the DRBs To Be Setup List IE of the PDU Session Resource Setup Response Info - SN terminated IE, the M-NG-RAN node shall, if supported, use it for RAN part delay reporting.

[0623] For each DRB configured as MN-terminated split bearer / SCG bearer, if the QoS Mapping Information IE is included in the DRBs Admitted List IE in the PDU Session Resource Setup Response Info - MN terminated IE of the S-NODE ADDITION REQUEST ACKNOWLEDGE message, the M-NG-RAN node shall, if supported, use it to set DSCP and / or IPv6 flow label fields for the downlink IP packets which are transmitted from M-NG-RAN node to S-NG-RAN node through the GTP tunnels indicated by the UP Transport Layer Information IE.

[0624] If the Source NG-RAN Node ID IE is included in the S-NODE ADDITION REQUEST message, the S-NG-RAN node shall, if supported, use it to decide the direct data path availability with the indicated source NG-RAN node, and if the direct data forwarding path is available, include the Direct Forwarding Path Availability IE set to "direct path available" in the S-NODE ADDITION REQUEST ACKNOWLEDGE message.

[0625] If for a given QoS Flow the Source DL Forwarding IP Address IE or both, the Source DL Forwarding IP Address IE and the Source Node DL Forwarding IP Address IE are included within the Data Forwarding and Offloading Info from source NG-RAN node IE in the PDU Session Resource Setup Info - SN terminated IE contained in the S-NODE ADDITION REQUEST message, the S-NG-RAN node shall, if supported, store this information and use it as part of its ACL functionality configuration actions, if such ACL functionality is deployed.

[0626] If for a given QoS Flow the Source DL Forwarding IP Address IE is included within the QoS Flows Mapped To DRB List IE in the PDU Session Resource Setup Response Info - SN terminated IE contained in the S-NODE ADDITION REQUEST ACKNOWLEDGE message, the M-NG-RAN node shall, if supported, store this information and use it as part of its ACL functionality to identify source TNL address for data forwarding in case of subsequent handover preparation, if such ACL functionality is deployed.

[0627] If the Management Based MDT PLMN List IE is contained in the S-NODE ADDITION REQUEST message, the S-NG-RAN node shall, if supported, store the received information in the UE context, and use this information to allow subsequent selection of the UE for management based MDT defined in TS 32.422

[0023] .

[0628] Upon reception of the S-NODE ADDITION REQUEST message, the S-NG-RAN node shall, if supported, start collecting SCG information and continue for as long as the UE stays in one of its cells.

[0629] If the UE History Information IE is included in the S-NODE ADDITION REQUEST message, the S-NG-RAN node shall, if supported, store this information.

[0630] If the UE History Information from the UE IE is included in the S-NODE ADDITION REQUEST message, the S-NG-RAN node shall, if supported, store this information.

[0631] If the PSCell Change History IE set to "reporting full history" is included in the S-NODE ADDITION REQUEST message, the S-NG-RAN node shall, if supported, signal the latest SCG UE History Information upon each PSCell change, to the M-NG-RAN node, using the S-NG-RAN node initiated S-NG-RAN node Modification procedure.

[0632] If the IAB Node Indication IE set to "true" is contained in the S-NODE ADDITION REQUEST message, the S-NG-RAN node shall, if supported, consider that dual connectivity operation is requested for an IAB-node. In addition:

[0633] -　　If the No PDU Session Indication IE is contained in the S-NODE ADDITION REQUEST message, the S-NG-RAN node shall, if supported, consider the UE as an IAB-node which does not have any PDU sessions activated, and ignore the PDU Session Resources To Be Added List IE, and shall not take any action with respect to PDU session setup. Subsequently, the M-NG-RAN node shall, if supported, ignore the PDU Session Resources Admitted To Be Added List IE in the S-NODE ADDITION REQUEST ACKNOWLEDGE message.

[0634] -　　If the F1-terminating IAB-donor Indicator IE set to "true" is contained in the S-NODE ADDITION REQUEST message, the S-NG-RAN node shall, if supported, assume that it will become the F1-terminating IAB-donor of the IAB-node, and act as described in TS 38.401 [2].

[0635] If the CHO Information SN Addition IE is included in the S-NODE ADDITION REQUEST message, the S-NG-RAN node shall consider that the S-NG-RAN node Addition Preparation procedure has been triggered as part of a conditional handover. It may use the Source M-NG-RAN node ID IE and the Source M-NG-RAN node UE XnAP ID IE to identify other active S-NG-RAN node Addition Preparations related to this UE. If the PCell ID IE is also included in the S-NODE ADDITION REQUEST message, then the S-NG-RAN node shall, if supported, include the PCell ID IE within the CHO Information SN Addition Acknowledge IE of the S-NODE ADDITION REQUEST ACKNOWLEDGE message. If the Estimated Arrival Probability IE is contained in the CHO Information SN Addition IE included in the S-NODE ADDITION REQUEST message, then the S-NG-RAN node may use the information to allocate necessary resources for the UE. If the Direct Forwarding Path Availability with source M-NG-RAN node IE set to "direct path available" is included in the S-NODE ADDITION REQUEST ACKNOWLEDGE message, the M-NG-RAN node shall, if supported, consider that the direct forwarding path is available between the target S-NG-RAN node and the source M-NG-RAN node.

[0636] If the SCG Activation Request IE is included in the S-NODE ADDITION REQUEST message, the S-NG-RAN node may use it to configure SCG resources as specified in TS 37.340 [8], and shall, if supported, include the SCG Activation Status IE in the S-NODE ADDITION REQUEST ACKNOWLEDGE message. If the SCG Activation Request IE in the S-NODE ADDITION REQUEST message is set to "Activate SCG", the S-NG-RAN node shall, if supported, activate the SCG resources and set the SCG Activation Status IE in the S-NODE ADDITION REQUEST ACKNOWLEDGE message to "SCG activated".

[0637] If the Conditional PSCell Addition Information Request IE is included in the S-NODE ADDITION REQUEST message, the S-NG-RAN node shall, if supported, consider that the request concerns CPAC, as described in TS 37.340 [8]. Accordingly, the S-NG-RAN node shall, if supported, include the Conditional PSCell Addition Information Acknowledge IE in the S-NODE ADDITION REQUEST ACKNOWLEDGE message.

[0638] If the S-CPAC Request Information IE is contained in the Conditional PSCell Addition Information Request IE included in the S-NODE ADDITION REQUEST message, the S-NG-RAN node shall, if supported, consider that the procedure is triggered for S-CPAC preparation. If the S-NG-RAN node accepts the request as a S-CPAC preparation, it shall include the Candidate PSCell with Other Information List IE in the Conditional PSCell Addition Information Acknowledge IE.

[0639] If the S-CPAC Reference Configuration Request IE set to "request" is contained in the Conditional PSCell Addition Information Request IE included in the S-NODE ADDITION REQUEST message, the S-NG-RAN node shall, if supported, provide the SCG reference configuration for S-CPAC.

[0640] If the S-CPAC Multiple Target S-NG-RAN Node List IE is contained within the S-CPAC Request Information IE in the Conditional PSCell Addition Information Request IE included in the S-NODE ADDITION REQUEST message, the S-NG-RAN node shall, if supported, consider that the information pertains to a list of PSCells suggested for other candidate SN(s) may also be prepared for S-CPAC, and act as described in TS 37.340 [8].

[0641] If the Conditional PSCell Addition Information Acknowledge IE is included in the S-NODE ADDITION REQUEST ACKNOWLEDGE message, the M-NG-RAN node shall, if supported, consider the indicated PSCells are selected by the target SN as candidate PSCells for CPAC or S-CPAC.

[0642] If the S-NG-RAN node applied a complete candidate configuration for a specific PSCell, e.g., as part of preparation of S-CPAC, the S-NG-RAN node shall inform the M-NG-RAN node by including the S-CPAC Complete Candidate Configuration Indicator IE in the Candidate PSCell with Other Information Item IE in the Conditional PSCell Addition Information Acknowledge IE in the S-NODE ADDITION REQUEST ACKNOWLEDGE message.

[0643] If the CG-CandidateList is included in the S-NG-RAN node to M-NG-RAN node Container IE in the S-NODE ADDITION REQUEST ACKNOWLEDGE message, the M-NG-RAN node shall, if supported, use it for the purpose of CPAC or S-CPAC.

[0644] If the Estimated Arrival Probability IE is contained in the Conditional PSCell Addition Information Request IE included in the S-NODE ADDITION REQUEST message, then the candidate target S-NG-RAN node may use the information to allocate necessary resources for the incoming CPAC or S-CPAC procedure.

[0645] If the S-NG-RAN node UE Slice Maximum Bit Rate IE for a specific S-NSSAI is included in the S-NODE ADDITION REQUEST message, the S-NG-RAN node shall, if supported, store and use the received S-NG-RAN node UE Slice Maximum Bit Rate for all PDU sessions associated with the S-NSSAI for the concerned UE as defined in TS 23.501 [7].

[0646] If the S-NODE ADDITION REQUEST ACKNOWLEDGE message includes the SN Mobility Information IE, the M-NG-RAN node shall, if supported, store this information and use it as defined in TS 37.340 [8].

[0647] If the QMC Coordination Request IE is contained in the S-NODE ADDITION REQUEST message, the S-NG-RAN node may use it as specified in TS 37.340 [8], and shall, if supported, include the QMC Coordination Response IE in the S-NODE ADDITION REQUEST ACKNOWLEDGE message.

[0648] If the Source SN to Target SN QMC Information IE is contained in the S-NODE ADDITION REQUEST message, the S-NG-RAN node shall, if supported, use it for QoE measurements handling, as specified in TS 37.340 [8].

[0649] If the Source M-NG-RAN node ID IE is included in the S-NODE ADDITION REQUEST message, the S-NG-RAN node may use it to deduce direct data path availability with the source M-NG-RAN node, and if the direct data forwarding path is available, may include the Direct Forwarding Path Availability with source M-NG-RAN node IE in the S-NODE ADDITION REQUEST ACKNOWLEDGE message.

[0650] If the S-NODE ADDITION REQUEST message contains the IAB Authorization status IE, the S-NG-RAN node shall, if supported, store it and use it as defined in TS 38.401[2].

[0651] <Interactions with the S-NG-RAN node Reconfiguration Completion procedure> 　　If the S-NG-RAN node admits at least one PDU session resource, the S-NG-RAN node shall start the timer TXnDCoverallwhen sending the S-NODE ADDITION REQUEST ACKNOWLEDGE message to the M-NG-RAN node except for a request for conditional configuration. The reception of the S-NODE RECONFIGURATION COMPLETE message shall stop the timer TXnDCoverallif TXnDCoverallis running.

[0652] <Interaction with the Activity Notification procedure> 　　Upon receiving an S-NODE ADDITION REQUEST message containing the Desired Activity Notification Level IE, the S-NG-RAN node shall, if supported, use this information to decide whether to trigger subsequent Activation Notification procedures according to the requested notification level.

[0653] <9.1.2.1　　S-NODE ADDITION REQUEST> 　　This message is sent by the M-NG-RAN node to the S-NG-RAN node to request the preparation of resources for dual connectivity operation for a specific UE.

[0654] Direction: M-NG-RAN node => S-NG-RAN node.

[0655]

[0656]

[0657] <9.2.1.13　　UE Context Information - Retrieve UE Context Response> 　　This IE contains the UE context information within the RETRIEVE UE CONTEXT RESPONSE message.

[0658] <TS 38.413> <8.14.3.2　　Successful Operation>

[0659] The NG-RAN node initiates the procedure by sending a UE RADIO CAPABILITY ID MAPPING REQUEST message. The NG-RAN includes the PLMN ID related to UE radio capability ID if the NG-RAN is shared by multiple PLMN (e.g. in case of MOCN and INS).

[0660] Upon receipt of the UE RADIO CAPABILITY ID MAPPING REQUEST message, the AMF shall provide within the UE RADIO CAPABILITY ID MAPPING RESPONSE message the UE Radio Capability information mapped to the UE Capability ID indicated in the UE RADIO CAPABILITY ID MAPPING REQUEST message for the PLMN ID indicated in the UE RADIO CAPABILITY ID MAPPING REQUEST

[0661] <9.2.13.4　　UE RADIO CAPABILITY ID MAPPING REQUEST> 　　This message is sent by the NG-RAN node to request the AMF to provide mapping information for the indicated UE Radio Capability ID.

[0662] Direction: NG-RAN node => AMF

[0663] <9.2.13.5　　UE RADIO CAPABILITY ID MAPPING RESPONSE> 　　This message is sent by the AMF to provide UE Radio Capability information which is mapped to the UE Radio Capability ID indicated by the NG-RAN node in the UE RADIO CAPABILITY ID MAPPING REQUEST message.

[0664] Direction: AMF => NG-RAN node

[0665] <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.

[0666] 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.

[0667] 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.

[0668] 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.

[0669] 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.

[0670] 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.

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

[0672] 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.

[0673] 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.

[0674] 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.

[0675] 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. 　　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).

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

[0677] (Supplementary note 1) 　　A method for a radio station in a hosting operator network comprising: 　　receiving, from a User Equipment (UE), at least one of information for identification related to UE capability, information for indirect network sharing support indicator, and information for identification of a Public Land Mobile Network (PLMN) that assigns the information for identification related to UE capability, 　　sending, to a core network node, at least one of the information for the identification related to UE capability, the information for indirect network sharing support, and the information for identification of a Public Land Mobile Network (PLMN) that assigns the information for identification related to UE, 　　receiving, from the core network node, at least one of information for the identification related to UE capability, information for 5G Globally Unique Temporary Identifier (5G-GUTI), and the information for identification of a Public Land Mobile Network (PLMN) that assigns the information for identification related to UE capability; and 　　sending, to the UE, at least one of the information for 5G-GUTI information for identification related to UE capability, and the information for identification of a Public Land Mobile Network (PLMN) that assigns the information for identification related to UE capability. 　　(Supplementary note 2) 　　A method for a core network node in a hosting operator network comparing: 　　receiving, from a radio station, at least one of information for identification related to UE capability, information for indirect network sharing support indicator, and information for identification of a Public Land Mobile Network (PLMN) that assigns the information for identification related to UE capability, 　　sending, to a Unified Data Management Function (UDM) in a participating operator network, a message related to a registration procedure, 　　receiving, from the UDM, a response message to the message relate to the registration procedure; and 　　sending, to the radio station, at least one of the information for the identification related to UE capability, information for 5G Globally Unique Temporary Identifier (5G-GUTI), and the information for identification of a Public Land Mobile Network (PLMN) that assigns the information for identification related to UE capability. 　　(Supplementary note 3) 　　The method for a core network node according to supplementary note 2 comprising: 　　sending, to the radio station, a message related to a User Equipment (UE) capability check including at least one of information for User Equipment (UE) capability inquiry and information for identification related to a Public Land Mobile Network (PLMN)) 　　receiving, from the radio station, a message related to a UE capability identification including at least one of the, 　　setting the information for identification related to a Public Land Mobile Network (PLMN) of a host operator, 　　sending, to a Network Repository Function (NRF) in the hosting operator network, a message related to Network Function (NF) discovery including the information for identification related to the PLMN of the host operator of the host operator, 　　receiving, from the NRF, a response message to the message related to the NF discovery including a NF profile, 　　sending, to a UE radio Capability Management Function (UCMF) in the hosting operator network, a message related to a UE capability management; and 　　receiving, from the UCMF, a response message related to the UE capability management including the information for identification related to UE capability. 　　(Supplementary note 4) 　　A method for a radio station in a hosting operator network comprising: 　　receiving from a core network node in the hosting operator network, at least one of information for User Equipment (UE) capability inquiry and information for identification related to a Public Land Mobile Network (PLMN) of a host operator, 　　deciding to perform a UE capability inquiry procedure, 　　sending, to the User Equipment (UE), a message related to the UE capability inquiry, 　　receiving, from the UE, at least one of information for identification related to UE capability and the information for identification related to a Public Land Mobile Network (PLMN) of a host operator; and 　　sending, to the core network node, the information for identification related to UE capability and the information for identification related to a Public Land Mobile Network (PLMN) of a host operator. 　　(Supplementary note 5) 　　A method for a core network node in a hosting operator network comprising: 　　sending, to a radio station in the hosting operator network, at least one of information for User Equipment (UE) capability inquiry and information for identification related to a Public Land Mobile Network (PLMN) of a host operator; and 　　 receiving, from the radio station, at least one of information for identification related to UE capability and the information for identification related to a Public Land Mobile Network (PLMN)of a host operator. 　　(Supplementary note 6) 　　A method for a first radio station in a hosting operator network comprising: 　　deciding to initiate a handover procedure, 　　sending, to a second radio station in the hosting operator network, a handover request message including at least one of information for 5G Globally Unique Temporary Identifier (5G-GUTI) and information for identification of a Public Land Mobile Network (PLMN) that assigns information for identification related to UE capability; and 　　receiving, from the second radio station, an acknowledgement message in response to the handover request message. 　　(Supplementary note 7) 　　A method for a second radio station in a hosting operator network comprising: 　　receiving, from a first radio station, a handover request message including at least one of information for 5G Globally Unique Temporary Identifier (5G-GUTI) and information for identification of a Public Land Mobile Network (PLMN) that assigns information for identification related to UE capability, 　　sending, to the first radio station, an acknowledgement message in response to the handover request message, 　　sending, to a core network node in a hosting operator network, a request message related to a path switch: and 　　receiving, from the core network node, an acknowledgement message in response to the request message related to the path switch, wherein the acknowledgement message in response to the request message related to the path switch includes at least one of information for 5G Globally Unique Temporary Identifier (5G-GUTI) and information for identification of a Public Land Mobile Network (PLMN) that assigns nformation for identification related to UE capability. 　　(Supplementary note 8) 　　A method for a core network node in a hosting operator network comprising: 　　receiving, from a second radio station in the hosting operator network, a request message related to a path switch: and 　　sending, to the second radio station, an acknowledgement message in response to the request message related to the path switch, wherein the acknowledgement message in response to the request message related to the path switch includes at least one of information for 5G Globally Unique Temporary Identifier (5G-GUTI) and information for identification of a Public Land Mobile Network (PLMN) that assigns information for identification related to UE capability. 　　(Supplementary note 9) 　　A method for a radio station in a hosting operator network comprising: 　　sending, to a core network node in the hosting operator network, a request message related to a User Equipment (UE) capability identification mapping; and 　　receiving, from the core network node, a response message relate to the UE capability identification mapping, wherein the request message includes information for identification of a Public Land Mobile Network (PLMN) that assigns information for identification related to UE capability, wherein the response message includes information for UE capability for paging. 　　(Supplementary note 10) 　　A method for a core network node in a hosting operator network comprising: 　　receiving, from a radio station in the hosting operator network, a request message related to a User Equipment (UE) capability identification mapping, 　　sending, to a Network Repository Function (NRF) in the hosting operator network, a request message related to a Network Function (NF) discovery including information for identification related to a Public Land Mobile Network (PLMN), 　　 receiving, from the NRF, a response message in response to the request message related to the NF discovery, 　　 sending, to a UE radio Capability management Function (UCMF) in the hosting operator network, a message related to UE capability management including information for identification related to UE capability, 　　 receiving, from the UCMF, a response message in response to the message relate to UE capability management; and 　　sending, to the radio station, a response message relate to the UE capability identification mapping, wherein the request message related to a User Equipment (UE) capability identification mapping including information for identification of a Public Land Mobile Network (PLMN) that assigns information for identification related to UE capability, wherein the response message relate to the UE capability identification mapping including information for UE capability for paging. 　　(Supplementary note 11) 　　A method for a master radio station in a hosting operator network comprising: 　　deciding to perform a secondary radio station addition procedure, 　　sending, to the secondary radio station, a request message related to the secondary radio station addition procedure; and 　　receiving, from the secondary radio station, an acknowledgement request in response to the request message, wherein the request message includes at least one of information for Globally Unique AMF Identifier (GUAMI), information for 5G Globally Unique Temporary Identifier (5G-GUTI), and information for identification of a Public Land Mobile Network (PLMN) that assigns information for identification related to UE capability. 　　(Supplementary note 12) 　　A method for a radio station in a participating operator network comprising: 　　receiving, from a User Equipment (UE), a Radio Resource Control (RRC) message including at least one of information for identification related to UE capability, information for indirect network sharing support indicator, and information for identification of a Public Land Mobile Network (PLMN) that assigns the information for identification related to UE capability; and 　　sending, to a core network node in a participating operator network, at least one of the information for indirect network sharing support indicator, and the information for identification of a Public Land Mobile Network (PLMN) that assigns the information for identification related to UE capability based on the RRC message. 　　(Supplementary note 13) 　　A method for a first core network node in a participating operator network comprising: 　　deciding whether information for identification related to UE capabilityneeds to be updated, 　　sending, to a second core network node in the participating operator network, a request message related to Network Function (NF) discovery including information for identification related to a Public Land Mobile Network (PLMN) of a host operator; and 　　receiving, from the second core network node, a response message in response to the request message, 　　sending, to a third core network node in the participating operator network, a message related to a User Equipment (UE) capability management, 　　receiving, from the third core network node, a response message related to the UE capability management; and 　　sending, to a radio station in the participating operator network, at least one of information for 5G-GUTI and the information for identification of a Public Land Mobile Network (PLMN) that assigns the information for identification related to UE capability. 　　(Supplementary note 14) 　　A method for a second core network node in a participating operator network comprising: 　　receiving, from a first core network node in the participating operator network, a request message related to Network Function (NF) discovery including information for identification related to a Public Land Mobile Network (PLMN) of a host operator; and 　　sending, to the first core network node, a response message in response to the request message. 　　(Supplementary note 15) 　　A method for a core network node in a hosting operator network comprising: 　　setting information for identification related to a Public Land Mobile Network (PLMN) of a participating network, 　　sending, to a Network Repository Function (NRF) in a participating operator network, a request message related to a Network Function (NF) discovery including the information for identification related to a Public Land Mobile Network (PLMN) of the participating network, 　　receiving, from the NRF, a response message in response to the request message relate to the NF discovery, 　　sending, to a UE radio Capability Management Function (UCMF) in the participating operator network, a message related to a User Equipment (UE) capability management, 　　receiving, from the UCMF, a response message related to the UE capability management; and 　　sending, to a radio station in a hosting operator network, at least one of information for 5G-GUTI and the information for identification of a Public Land Mobile Network (PLMN) that assigns information for identification related to UE capability. 　　(Supplementary note 16) 　　A method for a core network node in a hosting operator network comprising: 　　receiving, from a radio station in the hosting operator network, a request message related to a User Equipment (UE) capability identification mapping, 　　sending, to a Network Repository Function (NRF) in a participating operator network, a request message related to a Network Function (NF) discovery including information for identification related to a Public Land Mobile Network (PLMN), 　　receiving, from the NRF, a response message in response to the request message related to the NF discovery, 　　sending, to a UE radio Capability Management Function (UCMF) in the participating operator network, a message related to UE capability management including information for identification related to UE capability, 　　receiving, from the UCMF, a response message in response to the message relate to the UE capability management; and 　　sending, to the radio station, a response message relate to the UE capability identification mapping, wherein the request message related to a User Equipment (UE) capability identification mapping including information for identification of a Public Land Mobile Network (PLMN) that assigns the information for identification related to UE capability, wherein the response message relate to the UE capability identification mapping including information for UE capability for paging. 　　(Supplementary note 17) 　　A method for a first radio station comprising: 　　receiving, from a second radio station, a request message related to User Equipment (UE) context retrieve, 　　sending, to the second radio station, a response message in response to the request message, wherein the response message includes at least one of information for identification of a Public Land Mobile Network (PLMN) that assigns information for identification related to UE capability. 　　(Supplementary note 18) 　　A method for a first core network node in a first network comprising: 　　communicating with a User Equipment (UE); and 　　updating a UE Radio Capability Identity during mobility of the UE from the second core network node in a second network to the first core network node, wherein the first network operates as a participating operator network, wherein the second network operates as a hosting operator network. 　　(Supplementary note 19) 　　A first core network node in a first network comprising: 　　means for communicating with a User Equipment (UE); and 　　means for updating a UE Radio Capability Identity during mobility of the UE from the second core network node in a second network to the first core network node, wherein the first network operates as a participating operator network, wherein the second network operates as a hosting operator network.

[0678] This application is based upon and claims the benefit of priority from Indian Patent Application No. 202511009816, filed on February 6, 2025, the disclosure of which is incorporated herein in its entirety by reference.

[0679] 3　　USER EQUIPMENT(UE) 31　　TRANSCEIVER CIRCUIT 32　　ANTENNA 33　　CONTROLLER 34　　USER INTERFACE 35　　USIM 36　　MEMORY 361　　OPERATING SYSTEM 362　　COMMUNICATIONS CONTROL MODULE 3621　　TRANSCEIVER CONTROL MODULE 40　　N3IWF 401　　TRANSCEIVER CIRCUIT 402　　NETWORK INTERFACE 403　　CONTROLLER 404　　MEMORY 4041　　OPERATING SYSTEM 4042　　COMMUNICATIONS CONTROL MODULE 40421　　TRANSCEIVER CONTROL MODULE 41　　NON-3GPP ACCESS 411　　TRANSCEIVER CIRCUIT 412　　ANNTENA 413　　NETWORK INTERFACE 414　　CONTROLLER 415　　MEMORY 4151　　OPERATING SYSTEM 4152　　COMMUNICATIONS CONTROL MODULE 41521　　TRANSCEIVER CONTROL MODULE 5　　RADIO ACCESS NETWORK (RAN) 501　　RAN 502　　RAN 503　　RAN 504　　RAN 51　　TRANSCEIVER CIRCUIT 52　　ANTENNA 53　　NETWORK INTERFACE 54　　CONTROLLER 55　　MEMORY 551　　OPERATING SYSTEM 552　　COMMUNICATIONS CONTROL MODULE 5521　　TRANSCEIVER CONTROL MODULE 60　　RU 601　　TRANSCEIVER CIRCUIT 602　　ANTENNA 603　　NETWORK INTERFACE 604　　CONTROLLER 605　　MEMORY 6051　　OPERATING SYSTEM 6052　　COMMUNICATIONS CONTROL MODULE 60521　　TRANSCEIVER CONTROL MODULE 61　　DU 611　　TRANSCEIVER CIRCUIT 612　　NETWORK INTERFACE 613　　CONTROLLER 614　　MEMORY 6141　　OPERATING SYSTEM 6142　　COMMUNICATIONS CONTROL MODULE 61421　　TRANSCEIVER CONTROL MODULE 62　　CU 621　　TRANSCEIVER CIRCUIT 622　　NETWORK INTERFACE 623　　CONTROLLER 624　　MEMORY 6241　　OPERATING SYSTEM 6242　　COMMUNICATIONS CONTROL MODULE 62421　　TRANSCEIVER CONTROL MODULE 7　　CORE NETWORK 70　　AMF 7001　　AMF 7002　　AMF 7003　　MME 701　　TRANSCEIVER CIRCUIT 702　　NETWORK INTERFACE 703　　CONTROLLER 704　　MEMORY 7041　　OPERATING SYSTEM 7042　　COMMUNICATIONS CONTROL MODULE 70421　　TRANSCEIVER CONTROL MODULE 71　　SMF 711　　TRANSCEIVER CIRCUIT 712　　NETWORK INTERFACE 713　　CONTROLLER 714　　MEMORY 7141　　OPERATING SYSTEM 7142　　COMMUNICATIONS CONTROL MODULE 71421　　TRANSCEIVER CONTROL MODULE 72　　UPF 721　　TRANSCEIVER CIRCUIT 722　　NETWORK INTERFACE 723　　CONTROLLER 724　　MEMORY 7241　　OPERATING SYSTEM 7242　　COMMUNICATIONS CONTROL MODULE 72421　　TRANSCEIVER CONTROL MODULE 73　　PCF 731　　TRANSCEIVER CIRCUIT 732　　NETWORK INTERFACE 733　　CONTROLLER 734　　MEMORY 7341　　OPERATING SYSTEM 7342　　COMMUNICATIONS CONTROL MODULE 73421　　TRANSCEIVER CONTROL MODULE 74　　NWDAF 741　　TRANSCEIVER CIRCUIT 742　　NETWORK INTERFACE 743　　CONTROLLER 744　　MEMORY 7441　　OPERATING SYSTEM 7442　　COMMUNICATIONS CONTROL MODULE 74421　　TRANSCEIVER CONTROL MODULE 75　　UDM 751　　TRANSCEIVER CIRCUIT 752　　NETWORK INTERFACE 753　　CONTROLLER 754　　MEMORY 7541　　OPERATING SYSTEM 7542　　COMMUNICATIONS CONTROL MODULE 75421　　TRANSCEIVER CONTROL MODULE 76　　AUSF 761　　TRANSCEIVER CIRCUIT 762　　NETWORK INTERFACE 763　　CONTROLLER 764　　MEMORY 7641　　OPERATING SYSTEM 7642　　COMMUNICATIONS CONTROL MODULE 76421　　TRANSCEIVER CONTROL MODULE 77　　UCMF 7701　　UCMF 7702　　UCMF 771　　TRANSCEIVER CIRCUIT 772　　NETWORK INTERFACE 773　　CONTROLLER 774　　MEMORY 7741　　OPERATING SYSTEM 7742　　COMMUNICATIONS CONTROL MODULE 77421　　TRANSCEIVER CONTROL MODULE 78　　NRF 7801　　NRF 7802　　NRF 781　　TRANSCEIVER CIRCUIT 782　　NETWORK INTERFACE 783　　CONTROLLER 784　　MEMORY 7841　　OPERATING SYSTEM 7842　　COMMUNICATIONS CONTROL MODULE 78421　　TRANSCEIVER CONTROL MODULE 79　　NEF 791　　TRANSCEIVER CIRCUIT 792　　NETWORK INTERFACE 793　　CONTROLLER 794　　MEMORY 7941　　OPERATING SYSTEM 7942　　COMMUNICATIONS CONTROL MODULE 79421　　TRANSCEIVER CONTROL MODULE 7A　　UDR 7A1　　TRANSCEIVER CIRCUIT 7A2　　NETWORK INTERFACE 7A3　　CONTROLLER 7A4　　MEMORY 7A41　　OPERATING SYSTEM 7A42　　COMMUNICATIONS CONTROL MODULE 7A421　　TRANSCEIVER CONTROL MODULE 8　　OPERATIONS, ADMINISTRATION, AND MAINTENANCE (OAM) 811　　TRANSCEIVER CIRCUIT 812　　NETWORK INTERFACE 813　　CONTROLLER 814　　MEMORY 8141　　OPERATING SYSTEM 8142　　COMMUNICATIONS CONTROL MODULE 81421　　TRANSCEIVER CONTROL MODULE 20　　DATA NETWORK 201　　APPLICATION FUNCTION (AF) 2011　　TRANSCEIVER CIRCUIT 2012　　NETWORK INTERFACE 2013　　CONTROLLER 2014　　MEMORY 20141　　OPERATING SYSTEM 20142　　COMMUNICATIONS CONTROL MODULE 201421　　TRANSCEIVER CONTROL MODULE

Claims

A method for a radio station in a hosting operator network comprising:　　receiving, from a User Equipment (UE), at least one of information for identification related to UE capability, information for indirect network sharing support indicator, and information for identification of a Public Land Mobile Network (PLMN) that assigns the information for identification related to UE capability,　　sending, to a core network node, at least one of the information for the identification related to UE capability, the information for indirect network sharing support, and the information for identification of a Public Land Mobile Network (PLMN) that assigns the information for identification related to UE,　　receiving, from the core network node, at least one of information for the identification related to UE capability, information for 5G Globally Unique Temporary Identifier (5G-GUTI), and the information for identification of a Public Land Mobile Network (PLMN) that assigns the information for identification related to UE capability; and　　sending, to the UE, at least one of the information for 5G-GUTI information for identification related to UE capability, and the information for identification of a Public Land Mobile Network (PLMN) that assigns the information for identification related to UE capability.　　A method for a core network node in a hosting operator network comparing:　　receiving, from a radio station, at least one of information for identification related to UE capability, information for indirect network sharing support indicator, and information for identification of a Public Land Mobile Network (PLMN) that assigns the information for identification related to UE capability,　　sending, to a Unified Data Management Function (UDM) in a participating operator network, a message related to a registration procedure,　　receiving, from the UDM, a response message to the message relate to the registration procedure; and　　sending, to the radio station, at least one of the information for the identification related to UE capability, information for 5G Globally Unique Temporary Identifier (5G-GUTI), and the information for identification of a Public Land Mobile Network (PLMN) that assigns the information for identification related to UE capability.　　The method for a core network node according to claim 2 comprising:　　sending, to the radio station, a message related to a User Equipment (UE) capability check including at least one of information for User Equipment (UE) capability inquiry and information for identification related to a Public Land Mobile Network (PLMN))　　receiving, from the radio station, a message related to a UE capability identification including at least one of the,　　setting the information for identification related to a Public Land Mobile Network (PLMN) of a host operator,　　sending, to a Network Repository Function (NRF) in the hosting operator network, a message related to Network Function (NF) discovery including the information for identification related to the PLMN of the host operator of the host operator,　　receiving, from the NRF, a response message to the message related to the NF discovery including a NF profile,　　sending, to a UE radio Capability Management Function (UCMF) in the hosting operator network, a message related to a UE capability management; and　　receiving, from the UCMF, a response message related to the UE capability management including the information for identification related to UE capability.　　A method for a radio station in a hosting operator network comprising:　　receiving from a core network node in the hosting operator network, at least one of information for User Equipment (UE) capability inquiry and information for identification related to a Public Land Mobile Network (PLMN) of a host operator,　　deciding to perform a UE capability inquiry procedure,　　sending, to the User Equipment (UE), a message related to the UE capability inquiry,　　receiving, from the UE, at least one of information for identification related to UE capability and the information for identification related to a Public Land Mobile Network (PLMN) of a host operator; and　　 sending, to the core network node, the information for identification related to UE capability and the information for identification related to a Public Land Mobile Network (PLMN) of a host operator.　　A method for a core network node in a hosting operator network comprising:　　sending, to a radio station in the hosting operator network, at least one of information for User Equipment (UE) capability inquiry and information for identification related to a Public Land Mobile Network (PLMN) of a host operator; and　　 receiving, from the radio station, at least one of information for identification related to UE capability and the information for identification related to a Public Land Mobile Network (PLMN)of a host operator.　　A method for a first radio station in a hosting operator network comprising:　　deciding to initiate a handover procedure,　　sending, to a second radio station in the hosting operator network, a handover request message including at least one of information for 5G Globally Unique Temporary Identifier (5G-GUTI) and information for identification of a Public Land Mobile Network (PLMN) that assigns information for identification related to UE capability; and　　receiving, from the second radio station, an acknowledgement message in response to the handover request message.　　A method for a second radio station in a hosting operator network comprising:　　receiving, from a first radio station, a handover request message including at least one of information for 5G Globally Unique Temporary Identifier (5G-GUTI) and information for identification of a Public Land Mobile Network (PLMN) that assigns information for identification related to UE capability,　　sending, to the first radio station, an acknowledgement message in response to the handover request message,　　sending, to a core network node in a hosting operator network, a request message related to a path switch: and　　receiving, from the core network node, an acknowledgement message in response to the request message related to the path switch, wherein the acknowledgement message in response to the request message related to the path switch includes at least one of information for 5G Globally Unique Temporary Identifier (5G-GUTI) and information for identification of a Public Land Mobile Network (PLMN) that assigns nformation for identification related to UE capability.　　A method for a core network node in a hosting operator network comprising:　　receiving, from a second radio station in the hosting operator network, a request message related to a path switch: and　　sending, to the second radio station, an acknowledgement message in response to the request message related to the path switch, wherein the acknowledgement message in response to the request message related to the path switch includes at least one of information for 5G Globally Unique Temporary Identifier (5G-GUTI) and information for identification of a Public Land Mobile Network (PLMN) that assigns information for identification related to UE capability.　　A method for a radio station in a hosting operator network comprising:　　sending, to a core network node in the hosting operator network, a request message related to a User Equipment (UE) capability identification mapping; and　　receiving, from the core network node, a response message relate to the UE capability identification mapping, wherein the request message includes information for identification of a Public Land Mobile Network (PLMN) that assigns information for identification related to UE capability, wherein the response message includes information for UE capability for paging.　　A method for a core network node in a hosting operator network comprising:　　receiving, from a radio station in the hosting operator network, a request message related to a User Equipment (UE) capability identification mapping,　　sending, to a Network Repository Function (NRF) in the hosting operator network, a request message related to a Network Function (NF) discovery including information for identification related to a Public Land Mobile Network (PLMN),　　 receiving, from the NRF, a response message in response to the request message related to the NF discovery,　　 sending, to a UE radio Capability management Function (UCMF) in the hosting operator network, a message related to UE capability management including information for identification related to UE capability,　　 receiving, from the UCMF, a response message in response to the message relate to UE capability management; and　　sending, to the radio station, a response message relate to the UE capability identification mapping, wherein the request message related to a User Equipment (UE) capability identification mapping including information for identification of a Public Land Mobile Network (PLMN) that assigns information for identification related to UE capability, wherein the response message relate to the UE capability identification mapping including information for UE capability for paging.　　A method for a master radio station in a hosting operator network comprising:　　deciding to perform a secondary radio station addition procedure,　　sending, to the secondary radio station, a request message related to the secondary radio station addition procedure; and　　receiving, from the secondary radio station, an acknowledgement request in response to the request message, wherein the request message includes at least one of information for Globally Unique AMF Identifier (GUAMI), information for 5G Globally Unique Temporary Identifier (5G-GUTI), and information for identification of a Public Land Mobile Network (PLMN) that assigns information for identification related to UE capability.　　A method for a radio station in a participating operator network comprising:　　receiving, from a User Equipment (UE), a Radio Resource Control (RRC) message including at least one of information for identification related to UE capability, information for indirect network sharing support indicator, and information for identification of a Public Land Mobile Network (PLMN) that assigns the information for identification related to UE capability; and　　 sending, to a core network node in a participating operator network, at least one of the information for indirect network sharing support indicator, and the information for identification of a Public Land Mobile Network (PLMN) that assigns the information for identification related to UE capability based on the RRC message.　　A method for a first core network node in a participating operator network comprising:　　deciding whether information for identification related to UE capabilityneeds to be updated,　　sending, to a second core network node in the participating operator network, a request message related to Network Function (NF) discovery including information for identification related to a Public Land Mobile Network (PLMN) of a host operator; and　　receiving, from the second core network node, a response message in response to the request message,　　sending, to a third core network node in the participating operator network, a message related to a User Equipment (UE) capability management,　　receiving, from the third core network node, a response message related to the UE capability management; and　　sending, to a radio station in the participating operator network, at least one of information for 5G-GUTI and the information for identification of a Public Land Mobile Network (PLMN) that assigns the information for identification related to UE capability.　　A method for a second core network node in a participating operator network comprising:　　receiving, from a first core network node in the participating operator network, a request message related to Network Function (NF) discovery including information for identification related to a Public Land Mobile Network (PLMN) of a host operator; and　　sending, to the first core network node, a response message in response to the request message.　　A method for a core network node in a hosting operator network comprising:　　setting information for identification related to a Public Land Mobile Network (PLMN) of a participating network,　　sending, to a Network Repository Function (NRF) in a participating operator network, a request message related to a Network Function (NF) discovery including the information for identification related to a Public Land Mobile Network (PLMN) of the participating network,　　receiving, from the NRF, a response message in response to the request message relate to the NF discovery,　　sending, to a UE radio Capability Management Function (UCMF) in the participating operator network, a message related to a User Equipment (UE) capability management,　　receiving, from the UCMF, a response message related to the UE capability management; and　　sending, to a radio station in a hosting operator network, at least one of information for 5G-GUTI and the information for identification of a Public Land Mobile Network (PLMN) that assigns information for identification related to UE capability.　　A method for a core network node in a hosting operator network comprising:　　receiving, from a radio station in the hosting operator network, a request message related to a User Equipment (UE) capability identification mapping,　　sending, to a Network Repository Function (NRF) in a participating operator network, a request message related to a Network Function (NF) discovery including information for identification related to a Public Land Mobile Network (PLMN),　　receiving, from the NRF, a response message in response to the request message related to the NF discovery,　　sending, to a UE radio Capability Management Function (UCMF) in the participating operator network, a message related to UE capability management including information for identification related to UE capability,　　receiving, from the UCMF, a response message in response to the message relate to the UE capability management; and　　sending, to the radio station, a response message relate to the UE capability identification mapping, wherein the request message related to a User Equipment (UE) capability identification mapping including information for identification of a Public Land Mobile Network (PLMN) that assigns the information for identification related to UE capability, wherein the response message relate to the UE capability identification mapping including information for UE capability for paging.　　A method for a first radio station comprising:　　receiving, from a second radio station, a request message related to User Equipment (UE) context retrieve,　　sending, to the second radio station, a response message in response to the request message, wherein the response message includes at least one of information for identification of a Public Land Mobile Network (PLMN) that assigns information for identification related to UE capability.　　A method for a first core network node in a first network comprising:　　communicating with a User Equipment (UE); and　　updating a UE Radio Capability Identity during mobility of the UE from the second core network node in a second network to the first core network node, wherein the first network operates as a participating operator network, wherein the second network operates as a hosting operator network.　　A first core network node in a first network comprising:　　　　means for communicating with a User Equipment (UE); and　　　　means for updating a UE Radio Capability Identity during mobility of the UE from the second core network node in a second network to the first core network node, wherein the first network operates as a participating operator network, wherein the second network operates as a hosting operator network.

Images