Method of user equipment (UE), method of communication apparatus, method of communication apparatus in hosting operator network, UE, communication apparatus, and communication apparatus in hosting operator network

Abstract

An aspect of this disclosure includes method of a user equipment (UE). The method includes sending 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 method includes receiving 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 method includes performing the PLMN selection. The method includes performing a registration procedure in the Participating operator network.

Description

METHOD OF USER EQUIPMENT (UE), METHOD OF COMMUNICATION APPARATUS, METHOD OF COMMUNICATION APPARATUS IN HOSTING OPERATOR NETWORK, UE, COMMUNICATION APPARATUS, AND COMMUNICATION APPARATUS IN HOSTING OPERATOR NETWORK

[0001] The present disclosure relates to a method of a user equipment (UE), a method of a communication apparatus, a method of a communication apparatus in a Hosting operator network, a UE, a communication apparatus, and a communication apparatus in a Hosting operator network and etc.

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

[0003] An indirect network sharing is developed in 3GPP in order to configure network sharing easily and dynamically with less maintenance efforts.

[0004] In this disclosure, an operator that has operational control of a Shared RAN is called as a Hosting operator. An operator that are authorized to use shared RAN resources provided by the Hosting Operator is called as a Participating operator.

[0005] 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.1.0 (2024-09) NPL 3: [3] 3GPP TS 23.502: "Procedures for the 5G System (5GS)". V19.1.0 (2024-09) NPL 4: [4] 3GPP TS 23.122: "Non-Access-Stratum (NAS) functions related to Mobile Station (MS) in idle mode". V19.0.0 (2024-09) NPL 5: [5] 3GPP TS 22.261: "Service requirements for the 5G system Stage 1". V20.0.0 (2024-09) NPL 6: [6] 3GPP TS 23.003: "Numbering, addressing and identification". V19.0.0 (2024-09) NPL 7: [7] 3GPP TS 23.503: "Policy and charging control framework for the 5G System (5GS) Stage 2". V19.1.0 (2024-09) NPL 8: [8] 3GPP TS 24.501: "Non-Access-Stratum (NAS) protocol for 5G System (5GS) Stage 3". V19.0.0 (2024-09)

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

[0007] However, an architecture for the indirect network sharing has some inconsistencies with an architecture without the indirect network sharing. The inconsistencies might causes serious operational failure and cellular communication services provided by the Participating operator might be discontinued due to the operational failure.

[0008] For example, after the UE moves out from an area for the indirect network sharing and there are cells provided by an operator which the UE has a contract with (i.e., Participating operator, this may be equal to an HPLMN), the UE needs to select a cell provided by the Participating operator.

[0009] On the other hand, there may be cells provided by the Hosting operator without RAN sharing (or indirect network sharing) with the Participating operator.

[0010] In this case, it is unclear in 3GPP standards whether the UE keeps on staying with Cells of the Hosting operator network because the UE holds a Hosting operator as the Registered PLMN (i.e., the UE holds a 5G-GUTI provided by the Hosting operator.)

[0011] If the UE keeps on staying with Cells of the Hosting operator network, the stickiness to the Hosting operator network even outside of the area for the indirect network sharing is considered as miss operation and most likely against a network sharing contract between the Hosting operator and the Participating operator.

[0012] The disclosure has a method of a user equipment (UE) comprising sending 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, wherein the registration request message is sent to an Access and Mobility Management Function (AMF) in the Hosting operator network receiving a registration reject message from the AMF, wherein 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 performing the PLMN selection and performing a registration procedure in the Participating operator network.

[0013] The disclosure has a method of a communication apparatus comprising receiving 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, wherein the communication apparatus is in the Hosting operator network checking that an area where the UE is located is not a subject for the Indirect network sharing and sending a registration reject message to the UE, wherein 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.

[0014] The disclosure has a method of a user equipment (UE) comprising sending 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, wherein the message includes information related to the Participating operator network receiving another message, wherein the another message includes information indicating that the UE is requested to perform Public Land Mobile Network (PLMN) selection performing the PLMN selection and performing a registration procedure in the Participating operator network.

[0015] The disclosure has a method of a communication apparatus comprising receiving 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, and wherein the message includes information related to the Participating operator network and sending another message, wherein the another message includes information indicating that the UE is requested to perform Public Land Mobile Network (PLMN) selection.

[0016] The disclosure has a method of a user equipment (UE) comprising treating 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 and performing a registration procedure in the Participating operator network in a case where the UE moves out an area of the Indirect network sharing.

[0017] The disclosure has a method of a user equipment (UE) comprising treating 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, wherein 5G Globally Unique Temporary Identifier (5G-GUTI) related to the Participating operator network is assigned to the UE and performing 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.

[0018] The disclosure has a method of a communication apparatus in a Hosting operator network comprising communicating with a user equipment (UE); and assigning 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.

[0019] The disclosure has a user equipment (UE) comprising means for sending 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, wherein the registration request message is sent to an Access and Mobility Management Function (AMF) in the Hosting operator network means for receiving a registration reject message from the AMF, wherein 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 means for performing the PLMN selection and means for performing a registration procedure in the Participating operator network.

[0020] The disclosure has a communication apparatus comprising means for receiving 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, wherein the communication apparatus is in the Hosting operator network means for checking that an area where the UE is located is not a subject for the Indirect network sharing; and means for sending a registration reject message to the UE, wherein 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.

[0021] The disclosure has a user equipment (UE) comprising means for sending 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, wherein the message includes information related to the Participating operator network means for receiving another message, wherein the another message includes information indicating that the UE is requested to perform Public Land Mobile Network (PLMN) selection means for performing the PLMN selection; and means for performing a registration procedure in the Participating operator network.

[0022] The disclosure has a communication apparatus comprising means for receiving 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, and wherein the message includes information related to the Participating operator network; and means for sending another message, wherein the another message includes information indicating that the UE is requested to perform Public Land Mobile Network (PLMN) selection.

[0023] The disclosure has a user equipment (UE) comprising means for treating 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; and means for performing a registration procedure in the Participating operator network in a case where the UE moves out an area of the Indirect network sharing.

[0024] The disclosure has a user equipment (UE) comprising means for treating 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, wherein 5G Globally Unique Temporary Identifier (5G-GUTI) related to the Participating operator network is assigned to the UE; and means for performing 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.

[0025] The disclosure has a communication apparatus in a Hosting operator network comprising means for communicating with a user equipment (UE); and means for assigning 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.

[0026] Fig. 1 is a diagram illustrating an example architecture of this disclosure.Fig. 2 is a diagram illustrating an example zone concept 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 an example signaling diagram of this disclosure.Fig. 12 is an example data format of 5G-GUTI of this disclosure.Fig. 13 is an example data format of 5G-GUTI of this disclosure.Fig. 14 is an example signaling diagram of this disclosure.Fig. 15 is an example signaling diagram of this disclosure.Fig. 16 is a diagram illustrating a system overview.Fig. 17 is a block diagram illustrating a UE.Fig. 18 is a block diagram illustrating an N3IWF.Fig. 19 is a block diagram illustrating a non-3GPP access.Fig. 20 is a block diagram illustrating an (R)AN node.Fig. 21 is a diagram illustrating System overview of (R)AN node based on O-RAN architecture.Fig. 22 is a block diagram illustrating an RU.Fig. 23 is a block diagram illustrating a DU.Fig. 24 is a block diagram illustrating a CU.Fig. 25 is a block diagram illustrating an AMF.Fig. 26 is a block diagram illustrating an SMF.Fig. 27 is a block diagram illustrating a UPF.Fig. 28 is a block diagram illustrating a PCF.Fig. 29 is a block diagram illustrating an NWDAF.Fig. 30 is a block diagram illustrating a UDM.Fig. 31 is a block diagram illustrating an AUSF.Fig. 32 is a block diagram illustrating an AAnF.Fig. 33 is a block diagram illustrating an NRF.Fig. 34 is a block diagram illustrating an NEF.Fig. 35 is a block diagram illustrating a UDR.Fig. 36 is a block diagram illustrating an OAM.Fig. 37 is a block diagram illustrating an AF.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0041] 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 => eNodeB - AMF => MME - SMF => SGW or PGW or combined SGW and PGW - UPF => SGW-U or PGW-U or combined SGW-U and PGW-U - UDM => HSS - NGAP => S1AP - N2 reference point => S1-MME reference point - N3 reference point => S1-U reference point - N9 reference point => S5 or S8 reference point - N14 reference point => S10 reference point - RRC Setup Request => RRC Connection Setup Request - RRC Setup => RRC Connection Setup - RRC Setup Complete => RRC Connection Setup Complete - NG SETUP REQUET message => S1 SETUP REQUEST message - NG SETUP RESPONSE message => S1 SETUP RESPONSE message - XN SETUP REQUET message => S2 SETUP REQUEST message - XN SETUP RESPONSE message => S2 SETUP RESPONSE message - AMF CONFIGURATION UPDATE message => MME CONFIGURATION UPDATE message - AMF CONFIGURATION UPDATE ACKNOWLEDGE => MME CONFIGURATION UPDATE ACKNOWLEDGE message - RAN CONFIGURATION UPDATE message => ENB CONFIGURATION UPDATE message - RAN CONFIGURATION UPDATE ACKNOWLEDGE => ENB CONFIGURATION UPDATE ACKNOWLEDGE message - Any NGAP messages => Respective S1AP messages - Registration Request message => Attach Request message or TAU Request message - Registration Accept message => Attach Accept message or TAU Accept message - Any AMF service-related messages (ex. Namf_Communication_NonUeN2InfoNotify) => GTP-C messages - Any UDM service-related messages (for example, Nudm_SDM_Notification) => DIAMETER messages - 5G-GUTI => GUTI - 5G-S-TMSI => S-TMSI - PDU Session ID => TEID or TEID and IP address

[0042] A method of a user equipment (UE) according to example aspect of this disclosure includes sending 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 method includes receiving 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 method includes performing the PLMN selection. The method includes performing a registration procedure in the Participating operator network.

[0043] A method of a communication apparatus according to example aspect of this disclosure includes receiving 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 method includes checking that an area where the UE is located is not a subject for the Indirect network sharing. The method includes sending 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.

[0044] A method of a user equipment (UE) according to example aspect of this disclosure includes sending 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 method includes receiving another message. The another message includes information indicating that the UE is requested to perform Public Land Mobile Network (PLMN) selection. The method includes performing the PLMN selection. The method includes performing a registration procedure in the Participating operator network.

[0045] A method of a communication apparatus according to example aspect of this disclosure includes receiving 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 method includes sending another message. The another message includes information indicating that the UE is requested to perform Public Land Mobile Network (PLMN) selection.

[0046] A method of a user equipment (UE) according to example aspect of this disclosure includes treating 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 method includes performing a registration procedure in the Participating operator network in a case where the UE moves out an area of the Indirect network sharing.

[0047] A method of a user equipment (UE) according to example aspect of this disclosure includes treating 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 method includes performing 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.

[0048] A method of a communication apparatus in a Hosting operator network according to example aspect of this disclosure includes communicating with a user equipment (UE). The method includes assigning 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.

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

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

[0051] 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. The 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.

[0052] 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. The another message includes information indicating that the UE is requested to perform Public Land Mobile Network (PLMN) selection.

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

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

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

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

[0057] Example aspect of this disclosure includes a method of a core network. The method includes communicating with a User Equipment (UE). The method includes receiving, from the UE, a first message using non-3GPP access while the UE has registered with 3GPP access in the indirect network sharing environment. The method includes sending, to the UE, a second message rejecting the first message since assigning the same AMF with 3GPP access is not possible. The method includes assigning one AMF for both 3GPP access and non-3GPP access as far as the UE registers to the same PLMN.

[0058] Fig. 1 illustrates an example of target architecture that this disclosure applies to. 　　The UE 3 may be a subscriber or a user of the Participating operator. 　　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.

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

[0060] 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 becomes a failure situation.

[0061] 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 by the AF 201 through the Participating operator network.

[0062] Hosting operator network may indicate a network of the Hosting operator or a network managed or operated by the Hosting operator.

[0063] Participating operator network may indicate a network of the Participating operator or a network managed or operated by the Participating operator.

[0064] The Hosting operator may be expressed as a Hosting RAN operator or a Hosting NG-RAN operator etc.

[0065] The Participating operator may be expressed as a Participating NG-RAN operator etc.

[0066] The Hosting operator network may include RAN 5 and a Hosting operator's core network. The Hosting operator's core network may include at least one of the AMF 7001, V-PCF 7301, SMF 7101, and UPF 7201 etc.

[0067] Participating operator's core network may include at least one of the UDM 75, H-PCF 7302, SMF 7102, and UPF 7202 etc.

[0068] Indirect Network Sharing may be a type of NG-RAN Sharing (or RAN Sharing) in which the communication between the Shared NG-RAN (or Shared RAN) and the Participating operator's core network is routed through the Hosting NG-RAN operator's core network (or Hosting operator's network).

[0069] In case that the Indirect network sharing applies to a certain area, the Fig. 2 illustrates an example of an area concept between Hosting operator (e.g. Operator A in Fig. 2) and the Participating operator (e.g. Operator B in Fig. 2).

[0070] In this example, the Hosting operator and the Participating operator have an agreement to apply the Indirect network sharing in Zone 1 to subscribers belonging to the Participating operator as the Participating operator does not have coverage for the Zone 1 for providing cellular communication services. For example, the Zone 1 may be an area where the Hosting operator has coverage.

[0071] On the other hand, the Indirect network sharing does not apply to a Zone 2 as both the Hosting operator and the Participating operator have coverages to provide cellular communication services to their subscribers or inbound roamers. For example, the Zone 2 may be an area where the coverage by the Hosting operator and the coverage by the Participating operator are overlapped.

[0072] In addition, the Indirect network sharing does not apply to a Zone 3 neither as there is no coverage by the Hosting operator.

[0073] For example, the Zone 3 may be an area where the Participating operator has coverage. In the Zone 3, operator(s) other than Hosting operator may have coverage.

[0074] For example, the Indirect network sharing in this disclosure may be expressed as an Indirect network sharing using at least one of the 3GPP access and the non-3GPP access or an Indirect network sharing based on at least one of the 3GPP access and the non-3GPP access.

[0075] For example, the Indirect network sharing in this disclosure may be expressed as an Indirect network sharing using at least one of the 3GPP access and the non-3GPP access in the Hosting operator network and the Participating operator network or an Indirect network sharing based on at least one of the 3GPP access and the non-3GPP access in the Hosting operator network and the Participating operator network.

[0076] For example, the Indirect network sharing in this disclosure may be expressed as an Indirect network sharing using at least one of the 3GPP access and the non-3GPP access for the Hosting operator network and the Participating operator network or an Indirect network sharing based on at least one of the 3GPP access and the non-3GPP access for the Hosting operator network and the Participating operator network.

[0077] For example, the Indirect network sharing in this disclosure may be expressed as an Indirect network sharing using at least one of the 3GPP access and the non-3GPP access in the Hosting operator network or an Indirect network sharing based on at least one of the 3GPP access and the non-3GPP access in the Hosting operator network.

[0078] For example, the Indirect network sharing in this disclosure may be a type of NG-RAN Sharing (or RAN Sharing) using at least one of 3GPP access and the non-3GPP access in which the communication between the Shared NG-RAN (or Shared RAN) and the Participating operator's core network is routed through the Hosting NG-RAN operator's core network (or Hosting operator's network).

[0079] Note that the Indirect Network Sharing shall be transparent to the user according to 3GPP TS 22.261 [5] in current 3GPP definition.

[0080] <First Aspect> 　　For example, according to 3GPP TS 23.501 [2], a 5G Globally Unique Temporary Identifier (5G-GUTI) for a UE accessing with the indirect network sharing is provided by the Hosting Operator while cellular communication services are provided to the UE by the Participating operator. I.e., the UE is registered to the Participating operator in NAS level.

[0081] On the other hand, if the UE connects to both 3GPP access and non-3GPP access, one 5G-GUTI is assigned for both accesses according to 3GPP TS 23.501 [2].

[0082] Taking two mechanisms into account, for example, the UE may need to have a common 5G-GUTI from the Hosting operator network (or a 5G-GUTI from the Hosting operator network) or a 5G-GUTI from the Participating operator network in case where the UE registers to both 3GPP access and non-3GPP access in the indirect network sharing environment.

[0083] However, in the 3GPP standards, it is unclear how the 5G-GUTI would be managed (e.g., assigned) for 3GPP access and non-3GPP access in the context of indirect network sharing.

[0084] For example, there is no 3GPP standards for the UE to register to the Hosting operator network for non-3GPP access.

[0085] As the result, for example, the UE may not be able to use non-3GPP access as far as the UE is in the indirect network sharing environment. This is a serious service level restriction for UEs.

[0086] This aspect includes example mechanisms for handling of non-3GPP access in an area where the indirect network sharing is deployed.

[0087] In this Aspect, there are two examples disclosed.

[0088] The First example discloses example mechanisms for the UE 3 to recognize that the UE 3 has registered with 3GPP access through the Hosting operator network using the Indirect network sharing architecture.

[0089] The Second example discloses example mechanisms for the UE 3 for registering with non-3GPP access in case where the UE 3 establishes an association with the non-3GPP access 41 while the UE 3 is registered to an AMF 7001 in the Hosting operator network.

[0090] There are a few example mechanisms disclosed in both the First example and the Second example.

[0091] The UE 3 may take any mechanism in the Second example once the UE 3 recognizes that the UE 3 is registered with 3GPP access through the Hosting operator network using the Indirect network sharing architecture by any of mechanism in the First example.

[0092] I.e., any combination between an example mechanism in the First example and an example mechanism in the Second example is possible.

[0093] The above problem or the contents of this Aspect also applies for the case when the UE is registered to a PLMN in home country for a disaster roaming case to support Minimization of Service Interruption (MINT) as described in section 4.24 of 3GPP TS 24.501 and section 3.10 of 3GPP TS 23.122 and other parts of the 3GPP TS 24.501 and 3GPP TS 23.122. When the UE is registered over 3GPP access to a PLMN other than HPLMN in home country in case of disaster roaming case to support the minimization of service interruption and then UE gets trigger to register over non-3GPP access in home country than it is not sure how the UE will choose the N3IWF and same AMF is chosen for both 3GPP access and non-3GPP access.

[0094] The same scenarios apply for the case when the UE registered for the emergency services to a VPLMN which is in forbidden list and the UE gets trigger to register over non-3GPP access.

[0095] All the Aspects or at least one of the Aspects of this disclosure e.g. all or at least one of the examples of first aspects and the second aspects and their variants applies for the case when the UE is registered for disaster roaming to support minimisation of the service interruption as per section 3.10 of 3GPP TS 23.122 and other parts of the 3GPP TS 24.501 ad 3GPP TS 23.122. In the first aspect, the UE determined that it is registered to a VPLMN when the UE registration is successful with 5GS registration type disaster roaming initial registration or disaster roaming mobility registration updating in the registration request message as described in TS 24.501. All or at least one of examples of the second aspect also apply for the case when the UE is registered for the VPLMN in home country for disaster roaming services and the get triggers to register for non-3GPP access. The second aspect describes how the UE and the network behaves when the UE is registered for the disaster roaming services and the UE gets trigger to the register for the non-3GPP access in the home country. In the first aspect and the second aspect, the indirect network sharing capability is replaced by the capability to support Minimization of service interruption (MINT), the indirect network sharing capability for the network in broadcast message or NAS message sent to the UE is replaced with network MINT support indicator. In this case, the Hosting operator network is the VPLMN where the UE is registered for the disaster roaming services and the Participating operator network is the HPLMN or EHPLMN. In the current scenario the participating operator (VPLMN) has its own NG-RAN and may not have RAN sharing with host PLMN (HPLMN). The Participating network (HPLMN or EHPLMN) also has its own the NG-RAN. The AMF 7001 tells the UDM 75 the UE 3 is registered for disaster roaming services, and optionally the PLMN ID of the Participating operator where the UE is registered for the disaster roaming services or disaster roaming capability of the host PLMN.

[0096] The below Aspect(s) is also applied for the case when the UE is registered to a VPLMN in the home country and the UE gets trigger to register over non-3GPP access. In this case the Hosting operator network acts as the VPLMN where the UE is registered for the emergency services and the UE participating PLMN (e.g. the Participating operator network is the HPLMN or EHPLMN. In this case the Participating operator network and Hosting operating network have their own NG-RAN and don't share the RAN between them.

[0097] All the Aspect(s) below is also applied to select the ePDG, in this case the N3IWF is replaced with ePDG and non-3GPP access node selection information with ePDG access node selection information to select the ePDG.

[0098] <First example of the First Aspect> 　　This example includes example mechanisms for the UE 3 to detect that the UE 3 is registered with 3GPP access through the Hosting operator network using the Indirect network sharing architecture.

[0099] <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 detecting that the UE 3 is registered with 3GPP access through the Hosting operator network using the Indirect network sharing architecture by reading existing system information.

[0100] Fig. 3 illustrates an example of mechanism on detecting that the UE 3 is registered with 3GPP access through the Hosting operator network using the Indirect network sharing architecture by reading existing system information.

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

[0102] Step 0. The UE 3 registers to the AMF 7001 in the Hosting operator network over 3GPP access. A 5G-GUTI is assigned by the AMF 7001 as a temporary identifier for the UE 3.

[0103] Step 1. The UE 3 reads system information for checking whether UE 3 is in home country or not.

[0104] For example, the UE 3 may read an mcc part of PLMN ID in the IdentityInfoList that is broadcasted in system information (e.g. SIB 1). For example. The UE 3 may receive the system information and read the mcc part of PLMN ID in the IdentityInfoList that is broadcasted in system information. Then the UE 3 may check the mcc part in system information matches with the mcc part of SUPI in the USIM (e.g. the USIM for the UE 3 or for the user or subscriber of the UE 3).

[0105] If the mcc part in system information matches with the mcc part of SUPI in the USIM, the UE 3 recognizes that the UE 3 is in home country and this process continues. Otherwise (e.g. in a case where the mcc part in system information does not match with the mcc part of SUPI in the USIM), the UE 3 is out of home country and this process stops at this point.

[0106] Step 2. The UE 3 checks whether MCC and MNC of 5G-GUTI (e.g. mcc part and mnc part of 5G-GUTI (e.g. the 5G-GUTI assigned by the AMF 7001)) is the same as the MCC and MNC of SUPI in the USIM. (e.g. mcc part and mnc part of SUPI in the USIM). If it matches (e.g. in a case where MCC of the 5G-GUTI and MCC of the SUPI match and MNC of the 5G-GUTI and MNC of the SUPI match), it means that the UE 3 is registered to UE 3's HPLMN and this process stops at this point. Otherwise (e.g. in a case where MCC of the 5G-GUTI and MCC of the SUPI does not match and MNC of the 5G-GUTI and MNC of the SUPI match, or in a case where MCC of the 5G-GUTI and MCC of the SUPI match and MNC of the 5G-GUTI and MNC of the SUPI does not match, or in a case where MCC of the 5G-GUTI and MCC of the SUPI does not match and MNC of the 5G-GUTI and MNC of the SUPI does not match), this process continues.

[0107] Step 3. The UE 3 reads system information whether MCC and MNC of SUPI is broadcasted in the system information.

[0108] For example, the UE 3 reads an mcc part of PLMN ID in the IdentityInfoList that is broadcasted in system information (e.g. SIB 1).

[0109] For example, the UE 3 reads an mnc part of PLMN ID in the IdentityInfoList that is broadcasted in system information (e.g. SIB 1).

[0110] If MCC and MNC of SUPI is broadcasted in system information (e.g. in a case where MCC or mcc part of the system information and MCC or mcc part of the SUPI match and MNC or mnc part of the system information and MNC or mnc part of the SUPI match), it means that the UE 3 is registered with the Hosting operator network. Otherwise (e.g. in a case where MCC or mcc part of the system information and MCC or mcc part of the SUPI does not match and MNC or mnc part of the system information and MNC or mnc part of the SUPI match, or in a case where MCC or mcc part of the system information and MCC or mcc part of the SUPI match and MNC or mnc part of the system information and MNC or mnc part of the SUPI does not match, or in a case where MCC or mcc part of the system information and MCC or mcc part of the SUPI does not match and MNC or mnc part of the system information and MNC or mnc part of the SUPI does not match), the UE 3 is an outbound roamer of national roaming.

[0111] For example, as the UE 3 checks mcc part of PLMN ID in the IdentityInfoList that is broadcasted in system information (e.g. SIB 1) in Step 1, the UE 3 may check only whether MNC of SUPI is broadcasted in the system information (e.g. the UE 3 may check only whether MNC or mnc part of the system information and MNC or mnc part of the SUPI match).

[0112] At this point (e.g. in a case where MCC and MNC of SUPI is broadcasted in system information), the UE 3 recognizes that the UE 3 is registered with or over 3GPP access through the Hosting operator network using the Indirect network sharing architecture. As described above, the UE 3 detects the Indirect network sharing. In this disclosure, recognizing may mean determining or detecting.

[0113] For example, Steps 1 to 3 may be carried out in any order.

[0114] <Second scenario in the First example of the First Aspect> 　　The Second scenario in the First example of the First Aspect includes an example mechanism for detecting that the UE 3 is registered with 3GPP access through the Hosting operator network using the Indirect network sharing architecture by reading new system information.

[0115] Fig. 4 illustrates an example of mechanism on detecting that the UE 3 is registered with 3GPP access through the Hosting operator network using the Indirect network sharing architecture by reading new system information.

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

[0117] Two new system information, one in Step 1-1 and another one in Step 1-2, are disclosed in this scenario.

[0118] Step 1-1 may be solely broadcasted. For example, system information in Step 1-1 may be broadcasted solely.

[0119] Step 1-2 may be solely broadcasted. For example, system information in Step 1-2 may be broadcasted solely.

[0120] Step 1-1 and Step 1-2 may be broadcasted together. For example, system information in Step 1-1 and system information in Step 1-2 may be broadcasted together. For example, information (e.g. information element(s)) in system information in Step 1-1 and information (e.g. information element(s)) in system information in Step 1-2 may be broadcasted in one system information.

[0121] Step 1-1. Cells with RAN 5 broadcast new system information including Hosting operator network PLMN Identity. The Hosting operator network PLMN Identity includes a PLMN Identity (e.g. MCC and MNC) of the Hosting operator.

[0122] For example, RAN 5 or cell(s) of the RAN 5 or cell(s) controlled or managed by the RAN 5 may broadcast system information including Hosting operator network PLMN Identity.

[0123] The Hosting operator network PLMN Identity may include or indicate a PLMN Identity of the Hosting operator (e.g. MCC and MNC of the Hosting operator, MCC and MNC related to the Hosting operator etc).

[0124] Step 1-2. Cells with RAN 5 broadcast new system information including Participating operator network PLMN Identity list. The Participating operator network PLMN Identity list includes a list of PLMN Identities (MCC(s) and MNC(s)) of Participating operator networks which have a service contract of the indirect network sharing with the Hosting operator.

[0125] For example, RAN 5 or cell(s) of the RAN 5 or cell(s) controlled or managed by the RAN 5 may broadcast system information including Participating operator network PLMN Identity list.

[0126] The Participating operator network PLMN Identity list may include or indicate a PLMN Identity of the Participating operator (or PLMN Identities of the Participating operators) or a list of PLMN Identity of the Participating operator (e.g. MCC(s) and MNC(s) of the Participating operator(s), MCC(s) and MNC(s) related to the Participating operator(s) etc).

[0127] Step 2. The UE 3 registers to the AMF 7001 in the Hosting operator network over 3GPP access. A 5G-GUTI is assigned by the AMF 7001 for a temporary identifier for the UE 3.

[0128] If the MCC and MNC of the assigned 5G-GUTI is the same as the Hosting operator network PLMN Identity in system information in Step 1-1, the UE 3 recognizes that the UE 3 is registered with 3GPP access through the Hosting operator network using the Indirect network sharing architecture. As described above, the UE 3 detects the Indirect network sharing.

[0129] In one another example, if the MCC and MNC of the SUPI is broadcasted in the Participating operator network PLMN Identity list in Step 1-2, the UE 3 also recognizes that the UE 3 is registered with 3GPP access through the Hosting operator network using the Indirect network sharing architecture.

[0130] Note that the Participating operator network PLMN Identity list may be referred by the UE 3 before the Registration procedure in Step 2 for decision making whether the UE 3 should register with the Hosting operator network or not.

[0131] If the MCC and MNC of the assigned 5G-GUTI is the same as the Hosting operator network PLMN Identity in system information in Step 1-1 and / or if the MCC and MNC of the SUPI is broadcasted in the Participating operator network PLMN Identity list in Step 1-2, the UE 3 may recognize that the UE 3 is registered with 3GPP access through the Hosting operator network using the Indirect network sharing architecture.

[0132] For example, the UE 3 may recognize that the UE 3 is in the Hosting operator network using the Indirect network sharing architecture in a case where the UE 3 receives the system information in Step 1-1 and the system information in Step 1-2. Then the UE 3 may register to the AMF 7001 in the Hosting operator network over 3GPP access, and the UE 3 may recognize that the UE 3 is registered with 3GPP access through the Hosting operator network using the Indirect network sharing architecture, after the registration to the AMF 7001.

[0133] For example, the UE 3 may register to the AMF 7001 in the Hosting operator network over 3GPP access in a case where the UE 3 receives the system information in Step 1-2, and the UE 3 may recognize that the UE 3 is registered with 3GPP access through the Hosting operator network using the Indirect network sharing architecture, after the registration to the AMF 7001.

[0134] For example, the UE 3 may register to the AMF 7001 in the Hosting operator network over 3GPP access. Then the UE 3 may check whether the UE 3 receives the system information in Step 1-1 and the system information in Step 1-2. In a case where the UE 3 receives the system information in Step 1-1 and the system information in Step 1-2, the UE 3 may recognize that the UE 3 is registered with 3GPP access through the Hosting operator network using the Indirect network sharing architecture.

[0135] For example, the system information may include information indicating the Hosting operator network using the Indirect network sharing architecture. For example, the RAN 5 may send system information including information indicating the Hosting operator network using the Indirect network sharing architecture, instead of the system information in Step 1-1 and / or the system information in Step 1-2. In a case where the UE 3 receives information indicating the Hosting operator network using the Indirect network sharing architecture and the UE 3 registers to the AMF 7001 in the Hosting operator network over 3GPP access, the UE 3 may recognize that the UE 3 is registered with 3GPP access through the Hosting operator network using the Indirect network sharing.

[0136] The UE 3 may perform the Registration procedure within cell(s) or towards the RAN 5 which broadcasts the system information in Step 1-1 and / or the system information Step 1-2. Then in a case where the UE 3 is registered (e.g. to the AMF 7001 in Hosting operator network), the UE 3 may recognize that the UE 3 is registered with 3GPP access through the Hosting operator network using the Indirect network sharing.

[0137] <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 detecting that the UE 3 is registered with 3GPP access through the Hosting operator network using the Indirect network sharing architecture by an NAS level communication between the UE 3 and the AMF 7001.

[0138] Fig. 5 illustrates an example of mechanism on detecting that the UE 3 is registered with 3GPP access through the Hosting operator network using the Indirect network sharing architecture by the NAS level communication between the UE 3 and the AMF 7001.

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

[0140] Step 1. The UE 3 sends the Registration Request message to the AMF 7001 includes at least one of User ID and Indirect network sharing capability.

[0141] 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. - Indirect network sharing capability: The Indirect network sharing capability indicates that the UE 3 supports all functionalities or at least one of functionalities disclosed in this disclosure to support non-3GPP access and mobility management with the Indirect network sharing architecture. - For example, the Indirect network sharing capability may indicates that the UE 3 supports all functionalities or at least one of functionalities disclosed in this disclosure and performed by the UE 3. - For example, the Indirect network sharing capability may indicate that the UE 3 supports the Indirect network sharing architecture. - For example, the Indirect network sharing capability may indicate that the UE 3 supports the Indirect network sharing. - For example, the Indirect network sharing capability may indicate that the UE 3 supports the Indirect network sharing architecture using at least one of 3GPP access and non-3GPP access. - For example, the Indirect network sharing capability may indicate that the UE 3 supports the Indirect network sharing using at least one of 3GPP access and non-3GPP access. - For example, the Indirect network sharing capability may indicate that the UE 3 supports for process(es) (e.g., signal transmission, reception, processing) carried out by the UE 3 in this disclosure. - For example, the Indirect network sharing capability may indicate that the UE 3 supports to use at least one of 3GPP access and non-3GPP access for the Indirect network sharing.

[0142] Step 2. Upon reception of the Registration Request message in Step 1, the AMF 7001 sends an Nudm_UECM_Registration Request message to a UDM 75 including at least one of the SUPI, Indirect network sharing indication and Indirect network sharing capability.

[0143] The following bullets explain each parameter in detail. - SUPI: Subscription Permanent Identifier, Refer to 3GPP TS 23.003 [6] for details. - Indirect network sharing indication: The Indirect network sharing indication indicates that the UE 3 is accessing from the Hosting operator network using the Indirect network sharing function or Indirect network sharing architecture or Indirect network sharing. - The Indirect network sharing indication may indicate that the UE 3 is accessing from the Hosting operator network using the Indirect network sharing function which uses the 3GPP access or Indirect network sharing architecture which uses the 3GPP access or Indirect network sharing which uses the 3GPP access. - The Indirect network sharing indication may indicate that the UE 3 is accessing from the Hosting operator network using the Indirect network sharing function which uses at least one of the 3GPP access and the non-3GPP access or using Indirect network sharing architecture which uses at least one of the 3GPP access and the non-3GPP access or using Indirect network sharing which uses at least one of the 3GPP access and the non-3GPP access. - For example, the AMF 7001 may know or understand that the UE 3 is accessing from the Hosting operator network using the Indirect network sharing function based on UE context for the UE 3. The AMF 7001 may send the Indirect network sharing indication after the AMF 7001 knows or understands that the UE 3 is accessing from the Hosting operator network. - For example, the AMF 7001 may know or understand that the UE 3 is accessing from the Hosting operator network using the Indirect network sharing function based the received User ID (e,g. SUCI, the MCC and MNC part of the SUCI can tell whether the UE 3 belongs to a participating operator network or hosting operator network). In one example, when the UE 3 sends 5G-GUTI in the Registration Request message then the AMF 7001 fetches the UE context from the source AMF and after that the based on the SUPI of the UE context fetched, the host operator can know the participating PLMN of the UE 3 and indicate that this UE 3 is accessing using indirect network sharing. - For example, the AMF 7001 may store information indicating that the UE 3 is UE or a subscriber or a user from the Participating operator, and using this information the AMF 7001 may know or understand that the UE 3 is accessing from the Hosting operator network using the Indirect network sharing function. - For example, the AMF 7001 may store information indicating correspondence between that User ID of the UE 3 and UE(s) from the Hosting operator network using the Indirect network sharing function, and using the received User ID and this information, the AMF 7001 may know or understand that the UE 3 is accessing from the Hosting operator network using the Indirect network sharing function. - For example, in a case where the AMF 7001 receives the Indirect network sharing capability from the UE 3, the AMF 7001 may know or understand that the UE 3 is accessing from the Hosting operator network using the Indirect network sharing function. - For example, the AMF 7001 may know that the AMF 7001 itself is an AMF in the Hosting operator network using the Indirect network sharing function. If the AMF 7001 receives the Registration Request message from the UE 3, the AMF 7001 may know or understand that the UE 3 is accessing from the Hosting operator network using the Indirect network sharing function. - The AMF 7001 may store or receive (e.g. from other network node(s)) information indicating which UEs are accessing from the Hosting operator network and, based on that information, may determine that UE 3 is accessing from the Hosting operator network. - The Indirect network sharing function may include function for the Indirect network sharing, the Indirect network sharing etc. The Indirect network sharing function may mean function for the Indirect network sharing, the Indirect network sharing itself etc. - For example, the Indirect network sharing indication may indicate that the UE 3 registers or is registered with or over 3GPP access through the Hosting operator network using the Indirect network sharing architecture. - For example, the Indirect network sharing indication may indicate that the UE 3 registers or is registered through or to the Hosting operator network using the Indirect network sharing architecture which uses the 3GPP access or Indirect network sharing which uses the 3GPP access. - Indirect network sharing capability: The indirect network sharing capability indicates a UE capability for a support of the indirect network sharing.

[0144] The AMF 7001 sends the indirect network sharing capability of the UE 3 as received in the Registration Request message.

[0145] Step 3. Upon reception of the Nudm_UECM_Registration Request message in Step 2, the UDM 75 sends an Nudm_UECM_Registration Response message to the AMF 7001.

[0146] Step 4. After the completion of the Nudm_UECM_Registration service in Steps 2 and 3, the AMF 7001 sends an Nudm_SDM_Get Request message to the UDM 75 including at least one of the SUPI, Indirect network sharing indication and Indirect network sharing capability. Refer to Step 2 for parameter details.

[0147] Step 5. The UDM 75 finds Subscriber data for the UE 3 and sends an Nudm_SDM_Get Response message to the AMF 70 including at least one of the Subscriber data for the UE 3, Non-3GPP access node selection parameter and list of indirect network sharing PLMNs.

[0148] The following bullets explain each parameter in detail. - Subscriber data: The Subscriber data is subscriber data for the UE 3. - Non-3GPP access node selection parameter: The Non-3GPP access node selection parameter includes parameter(s) that the UE 3 may use if the UE 3 initiates the Registration procedure for non-3GPP access in the Hosting operator network where the UE 3 is registering. The Non-3GPP access node selection parameter may be specific to the Hosting operator that the UE 3 is registering. The Non-3GPP access node selection parameter may include at least one of the following parameters. - N3IWF location preference: The N3IWF location preference indicates a preference of N3IWF location, either in the Hosting operator network or in the Participating operator network. - FQDN for the N3IWF in the Hosting operator network. An N3IWF in the Hosting operator network may be found by the UE 3 by the DNS query. For example, the UE 3 may find or select N3IWF in the Hosting operator network using the FQDN for the N3IWF in the Hosting operator network. For example, the FQDN for the N3IWF in the Hosting operator network may be included in the Non-3GPP access node selection parameter in a case where the N3IWF location preference indicates N3IWF location in the Hosting operator network or N3IWF in the Hosting operator network. - FQDN for the N3IWF in the Participating operator network. This FQDN may be the same as the one the UE 3 configures for the FQDN for the N3IWF that is located in HPLMN. This FQDN may be the same as the one the UE 3 configures for the FQDN for the N3IWF that is located in a roaming partner of the HPLMN operator. For example, the UE 3 may find N3IWF in the Participating operator network using the FQDN for the N3IWF in the Participating operator network. For example, the FQDN for the N3IWF in the Participating operator network may be included in the Non-3GPP access node selection parameter in a case where the N3IWF location preference indicates N3IWF location in the Participating operator network or N3IWF in the Participating operator network. - list of indirect network sharing PLMNs: The list of indirect network sharing PLMNs indicates a list of PLMN(s) that the UE 3 is allowed to access as the Hosting operator network in the indirect network sharing. The list of indirect network sharing PLMNs may be in the Subscriber data. An indirect network sharing PLMN in this list may be expressed by PLMN ID (for example, MCC and MNC). The PLMNs are listed in order of decreasing priority, with the first PLMN being the highest priority PLMN as the Hosting operator network for the UE 3. For example, the list of indirect network sharing PLMNs includes PLMN ID(s) for PLMN(s) that the UE 3 is allowed to access as the Hosting operator network in the indirect network sharing. For example, the list of indirect network sharing PLMNs includes information indicating PLMN(s) that the UE 3 is allowed to access as the Hosting operator network in the indirect network sharing.

[0149] For example, the AMF 7001 may send the Indirect network sharing capability of the UE 3 to the UDM 75. In one example, whenever the UDM 75 receives the Indirect network sharing capability of the UE 3, the UDM 75 may send at least one of the Indirect network sharing capability and an indication that the UE 3 is registered in the Hosting operator network (or the Indirect network sharing indication) to an NF in an existing message of a service operation between the UDM 75 and the NF. The NF will take necessary action based on at least one of the received the indirect network sharing capability and the indication.

[0150] Step 6. The AMF 7001 sends the Registration Accept message to the UE 3 including at least one of 5G-GUTI, Indirect network sharing indication and Non-3GPP access node selection parameter. 　　The following bullets explain each parameter in detail. - 5G-GUTI: The 5G-GUTI is a temporary user identifier for the UE 3. Refer to 3GPP TS 23.003 [6] for details. - Indirect network sharing indication: Refer to Step 2. - Non-3GPP access node selection parameter: Refer to Step 5.

[0151] Step 7. Upon reception of the Registration Accept message, the UE 3 stores the received data in the Registration Accept message in step 6 for example into non-volatile memory in the UE 3 or USIM.

[0152] The UE 3 sends the Registration Complete message to the AMF 7001.

[0153] The UE 3 recognizes that the UE 3 is registered with 3GPP access through the Hosting operator network using the Indirect network sharing architecture if the UE 3 receives the Indirect network sharing indication in the Registration Accept message in Step 6. As described above, the UE 3 detects the Indirect network sharing.

[0154] The UE 3 may recognize that the UE 3 is registered through or to the Hosting operator network using the Indirect network sharing architecture which uses the 3GPP access or using the Indirect network sharing which uses the 3GPP access if the UE 3 receives the Indirect network sharing indication in the Registration Accept message in Step 6.

[0155] For example, the Indirect network sharing indication in Step 6 may indicate that the UE 3 is registered with 3GPP access through the Hosting operator network using the Indirect network sharing architecture or using Indirect network sharing.

[0156] For example, the Indirect network sharing indication in Step 6 may indicate that the UE 3 is registered through the Hosting operator network using the Indirect network sharing which uses the 3GPP access.

[0157] For example, the Non-3GPP access node selection parameter may be expressed as information for a registration procedure for non-3GPP access in the Hosting operator network using an Indirect network sharing which uses non-3GPP access.

[0158] For example, the Non-3GPP access node selection parameter may be expressed as information for a registration procedure for non-3GPP access in the Participating operator network using an Indirect network sharing which uses non-3GPP access.

[0159] For example, the Non-3GPP access node selection parameter may be expressed as information for a registration procedure for non-3GPP access in the Hosting operator network using the Indirect network sharing.

[0160] For example, the Non-3GPP access node selection parameter may be expressed as information for a registration procedure for non-3GPP access in the Participating operator network using the Indirect network sharing.

[0161] <First Variant of the third scenario in the First example of the First Aspect> 　　In one example, after the initial registration procedure to the AMF 7001, the PCF 73 (e.g. V-PCF 7301 or H-PCF 7302) sends the Non-3GPP access node selection parameter in the URSP information element using the procedure as defined in 3GPP TS 23.503 [7] and 3GPP TS 24.501 [8] to the UE 3 supporting the indirect network sharing when the PCF 73 determines that the UE 3 supports indirect network sharing and the UE 3 is registered over 3GPP access in the Hosting operator network of indirect network sharing case based on an existing message or a new message received from either AMF 7001 or UDM 75. For example, the AMF 7001 may send the parameter(s) in at least one of Steps 2, 4, 5 and 6 to the PCF 73. For example, the UDM 75 may send the parameter(s) in at least one of Steps 2, 4 and 5 to the PCF 73. The PCF 73 may determine that the UE 3 supports indirect network sharing and the UE 3 is registered over 3GPP access in the Hosting operator network using indirect network sharing.

[0162] <Second Variant of the third scenario in the First example of the First Aspect> 　　In one example the AMF 7001 sends its capability that the AMF 7001 supports the indirect network sharing procedure as defined in at least one of the Aspects of this disclosure to the RAN 5 in an existing message. The AMF 7001 also sends the capability that the AMF 7001 supports the indirect network sharing procedure to NF(s) in an existing or in a new message. The RAN 5 also sends its capability to the AMF 7001 that the RAN 5 supports indirect network sharing procedure defined in the at least one of Aspects of the disclosure.

[0163] For example, the capability from the AMF 7001 may indicate that the AMF 7001 supports for process(es) (e.g., signal transmission, reception, processing) carried out by the AMF 7001 in this disclosure.

[0164] For example, the capability from the RAN 5 may indicate that the RAN 5 supports for process(es) (e.g., signal transmission, reception, processing) carried out by the RAN 5 in this disclosure.

[0165] <Third Variant of the third scenario in the First example of the First Aspect> 　　In Step 6, if the AMF 7001 receives the list of indirect network sharing PLMNs from the UDM 75 in Step 5 and the Hosting operator network of the AMF 7001 is not listed in the list of indirect network sharing PLMNs, the AMF 7001 sends the Registration Reject message in Step 6 instead of the Registration Accept message including a cause code or a cause value indicating that the Hosting operator network being accessing is not allowed to access. The cause code or the cause value may be an existing cause (for example, roaming not allowed) or new cause code (or new cause value) indicating that the Hosting operator network being accessing is not allowed to access.

[0166] <Fourth Variant of the third scenario in the First example of the First Aspect> 　　In Step 6, if the AMF 7001 receives the list of indirect network sharing PLMNs from the UDM 75 in Step 5, the AMF 7001 may forward this parameter to the UE 3 in the Registration Accept message or Registration Reject message.

[0167] <Second example of the First Aspect> 　　The Second example of the First Aspect includes example mechanisms how the 3GPP access and non-3GPP access work together in the Indirect network sharing architecture.

[0168] Scenarios in this example apply to the UE 3 where the UE 3 is located in the Zone A in Fig. 2 where the Indirect network sharing applies.

[0169] <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 that the UE 3 registers to the AMF 7001 in the Hosting operator network.

[0170] Fig. 6 illustrates an example of mechanism that the UE 3 registers to the AMF 7001 in the Hosting operator network.

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

[0172] Step 0-1. The UE 3 registers to the AMF 7001 in the Hosting operator network over 3GPP access. A 5G-GUTI is assigned by the AMF 7001 for a temporary identifier for the UE 3. For example, the UDM 75 in the Participating operator network may know or understand that the UE 3 registers to the AMF 7001 in the Hosting operator network over 3GPP access.

[0173] In one example, the UE 3 is configured, in a UE memory using OMA DM, or in a USIM e.g. in an existing Elementary File (EF) or a new EF, or through an existing information element (IE) or a new IE in an existing NAS message (e.g. Registration accept message or Configuration Update command message or downlink UE NAS transport message ) or a new NAS message during an existing NAS procedure (e.g. Registration procedure or UE policy transmission procedure from Home or VPLMN PCF to the UE as defined in 3GPP TS 24.501 [8]) or a new NAS procedure, whether the UE 3 is allowed to selects an N3IWF (e.g. N3IWF 4001) of the host PLMN (e.g. Hosting operator network) or not in an indirect networking scenario). The Host PCF may provide the FQDN of N3IWF or IP address of N3IWF.

[0174] Step 0-2. The UE 3 recognizes that the UE 3 is registered to the AMF 7001 in the Hosting operator network based on the Indirect network sharing over 3GPP access.

[0175] In one example, the UE 3 recognizes that the UE 3 is registered to the AMF 7001 in the Hosting operator network based on the Indirect network sharing over 3GPP access based on any mechanisms as disclosed in the First example of the First Aspect.

[0176] Step 1. The UE 3 establishes a Radio association or connection with a non-3GPP access 41.

[0177] The non-3GPP access 41 may be located in the Zone A where the indirect network sharing is effective to the UE 3. The non-3GPP access 41 may include node(s) for the non-3GPP access. The non-3GPP access 41 may be substituted with node(s) for the non-3GPP access or non-3GPP access node(s).

[0178] Step 2. The UE 3 obtains an IP address from the non-3GPP access 41 by performing the DNS procedure to find the N3IWF 4001 in the Hosting operator network by constructing the Prefixed N3IWF OI FQDN with the MCC and MNC of the 5G-GUTI that assigned to the UE 3 in Step 0-1. 　　In one example, the UE may execute Step 2 to 4 if the UE 3 is configured to use N3IWF of the host PLMN (e.g. the N3IWF 4001) as defined in step 0-1.

[0179] Step 3. Steps 2 to 18 in the Registration procedure in section 4.12.2.2 in 3GPP TS 23.502 [3] take place. For example, the UE 3 may perform the Registration procedure over non-3GPP access via the N3IWF 4001. For example, the UE 3 may perform the Registration procedure over non-3GPP access via the N3IWF 4001, by using the 5G-GUTI assigned in Step 0-1.

[0180] Step 4. The UE 3 registered to both 3GPP access and non-3GPP access with single 5G-GUTI assigned by the AMF 7001.

[0181] After Step 4, the cellular communication services are available to the UE 3 in both 3GPP access and non-3GPP access. For example, the cellular communication services are available to the UE 3 in both 3GPP access and non-3GPP access under the Indirect network sharing environment.

[0182] <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 that the UE 3 registers to the AMF 7001 in the Hosting operator network with assistance by the Participating operator network during the Registration procedure for 3GPP access.

[0183] This scenario may be only available in case where the UE 3 recognizes that the UE 3 is registered to the AMF 7001 in the Hosting operator network based on the disclosure in Fig. 5 and the UE 3 holds the Non-3GPP access node selection parameter.

[0184] Fig. 7 illustrates an example of mechanism that the UE 3 registers to the AMF 7001 in the Hosting operator network assisted by the Participating operator network during the Registration procedure for 3GPP access.

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

[0186] Step 1. Steps 0-1 to 1 in Fig. 6 take place. During the Registration procedure, the AMF 7001 may indicate to the UDM 75 that the UE 3 is registering to the Indirect network sharing, UE capability to support indirect network sharing (e.g. the Indirect network sharing capability) and host network ID (e.g. MCC and / or MNC of the host PLMN (Hosting operator network) to which the UE 3 is registered). The UDM 75 may send the UE indirect network capability (e.g. the Indirect network sharing capability), host network ID, location of the UE 3 to the Home PCF 73 or visited PCF 73 in an existing message or a new message between the UDM 75 and the PCF 73 during an existing service operation (e.g. during AM policy association or UE policy association as defined in 3GPP TS 23.502 [3] and 3GPP TS 23.503 [7]) or a new service operation. The Home PCF or the visited PCF may send the non-3GPP access node selection information (e.g. Non-3GPP access node selection parameter) or a new information element containing N3IWF FQDN of the host PLMN or IP Address of N3IWF of the host PLMN and it may optionally send an indication instructing the UE 3 to use N3IWF FQDN of the host PLMN or IP address of the N3IWF of the host PLMN if the UE 3 is registered to the host PLMN in an existing message between the UE 3 and PCF 73 or a new message between the UE 3 and the PCF 73. The UE 3 receives the non-3GPP access node selection information. In one example, the non-3GPP access node selection information and the above-mentioned indication may be stored in an existing EF or a new EF in the USIM.

[0187] Step 2. The UE 3 obtains an IP address from the N3IWF 4001, where the N3IWF 4001 is selected based on Non-3GPP access node selection parameter that is received from the Participating operator network (i.e. UDM 75) when the UE 3 performs the Registration procedure for 3GPP access.

[0188] In one example, if the UE 3 is configured to select N3IWF of the host PLMN as described in step 1,then the UE 3 may select the N3IWF node (e.g. the N3IWF 4001) as per the FQDN or IP Address received in step 1 or apply the received information in step 1 and treat as the UE 3 in a visited country and apply procedure defined to select N3IWF in visited country as defined in the section 6.3.6 of 3GPP TS 23.501 [2] for the visited PLMN.

[0189] Step 3. The UE 3 performs the Registration procedure with the N3IWF 4001 and AMF 7001 for non-3GPP access by performing Steps 2 to 18 in section 4.12.2.2 in 3GPP TS 23.502 [3]. For example, the UE 3 may perform the Registration procedure over non-3GPP access via the N3IWF 4001. For example, the UE 3 may perform the Registration procedure over non-3GPP access via the N3IWF 4001, by using the 5G-GUTI assigned in Step 1.

[0190] After Step 3, cellular communication services are available to the UE 3 via 3GPP access and non-3GPP access. For example, the cellular communication services are available to the UE 3 in both 3GPP access and non-3GPP access under the Indirect network sharing environment.

[0191] <Third scenario in the Second example of the First Aspect> 　　The third scenario in the Second example of the First Aspect includes an example mechanism that the UE 3 registers to the AMF 7002 in the Participating operator network for non-3GPP access and deregisters from 3GPP access.

[0192] Fig. 8 illustrates an example of mechanism that the UE 3 registers to the AMF 7002 in the Participating operator network for non-3GPP access and deregisters from 3GPP access.

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

[0194] Step 1. Steps 0-1 to 1 in Fig. 6 take place.

[0195] Step 2. The UE 3 obtains an IP address from the N3IWF 4002 that is selected according to the N3IWF selection in section 6.3.6 in 3GPP TS 23.501 [2].

[0196] For example, the UE 3 may obtain an IP address from the N3IWF 4002, where the N3IWF 4002 is selected based on Non-3GPP access node selection parameter that is received from the Participating operator network (i.e. UDM 75) when the UE 3 performs the Registration procedure for 3GPP access.

[0197] Step 3. After successful an IPsec Security Association (SA) establishment with the N3IWF 4002, the UE 3 sends the Registration Request message to the AMF 7002 includes at least one of User ID and Indirect network sharing capability.

[0198] The following bullets explain each parameter in detail. - User ID: Refer to Step 1 in Fig. 5. - Indirect network sharing capability: Refer to Step 1 in Fig. 5.

[0199] For example, the UE 3 may send the Registration Request message to the AMF 7002 via the N3IWF 4002.

[0200] For example, the UE 3 may perform the Registration procedure over non-3GPP access to the AMF 7002 by sending the Registration Request message.

[0201] Step 4. Upon reception of the Registration Request message in Step 3, the AMF 7002 sends an Nudm_UECM_Registration Request message to a UDM 75 including at least one of the SUPI, Indirect network sharing capability and Indirect network sharing indication.

[0202] The following bullets explain each parameter in detail. - SUPI: Refer to Step 2 in Fig. 5. - Indirect network sharing capability of the UE as received in the registration request message. Refer to Step 1 in Fig. 5. - Indirect network sharing indication: Refer to Step 2 in Fig. 5.

[0203] The Indirect network sharing indication in Step 4 may indicate that the UE 3 is accessing by using the Indirect network sharing function or Indirect network sharing architecture or Indirect network sharing.

[0204] The Indirect network sharing indication in Step 4 may indicate that the UE 3 is accessing by using the Indirect network sharing function which uses at least one of the 3GPP access and the non-3GPP access, or Indirect network sharing architecture which uses at least one of the 3GPP access and the non-3GPP access, or Indirect network sharing which uses at least one of the 3GPP access and the non-3GPP access.

[0205] The Indirect network sharing indication in Step 4 may indicate that the UE 3 is accessing to the Participating operator network using the Indirect network sharing function which uses at least one of the 3GPP access and the non-3GPP access, or Indirect network sharing architecture which uses at least one of the 3GPP access and the non-3GPP access, or Indirect network sharing which uses at least one of the 3GPP access and the non-3GPP access.

[0206] The Indirect network sharing indication in Step 4 may indicate that the UE 3 is registered over 3GPP access in the Hosting network and the UE 3 is accessing to the Participating operator network using the Indirect network sharing function which uses at least one of the 3GPP access and the non-3GPP access, or Indirect network sharing architecture which uses at least one of the 3GPP access and the non-3GPP access, or Indirect network sharing which uses at least one of the 3GPP access and the non-3GPP access. The AMF 7002 may know or understand that the UE 3 is registered over 3GPP access in the Hosting network based on information received from the UDM 75.

[0207] Step 5. Upon reception of the Nudm_UECM_Registration Request message in Step 4, the UDM 75 sends an Nudm_UECM_Registration Response message to the AMF 7002.

[0208] Step 6. After the completion of the Nudm_UECM_Registration service in Steps 4 and 5, the AMF 7002 sends an Nudm_SDM_Get Request message to the UDM 75 including at least one of the SUPI and Indirect network sharing indication. Refer to Step 4 for parameter details.

[0209] Step 7. Upon reception of the Nudm_SDM_Get Request message in Step 6, the UDM 75 finds Subscriber data for the UE 3 and sends an Nudm_SDM_Get Response message to the AMF 70 including at least one of the Subscriber data for the UE 3 and Deregistration request from 3GPP access.

[0210] The following bullets explain each parameter in detail. - Subscriber data: Refer to Step 5 in Fig. 5. - Deregistration request from 3GPP access: The Deregistration request from 3GPP access indicates to the UE 3 that the UE 3 is requested to perform the UE initiated Deregistration procedure for 3GPP access as described in section 4.2.2.3.2 in 3GPP TS 23.502 [3]. - Deregistration request from 3GPP access may be expressed other ways, for example, Deregistration request from other access type, Detach request from 3GPP access or Single registration required etc.

[0211] For example, the UDM 75 may know or understand that the UE 3 registers to the AMF 7001 in the Hosting operator network over 3GPP access. 　　For example, the UDM 75 may know or understand that the UE 3 registers to the AMF 7001 in the Hosting operator network over 3GPP access during the Registration procedure for the 3GPP access (e.g. the Step 0-1 in Fig. 6).

[0212] In a case where the UDM 75 knows or understands that the UE 3 registers to the AMF 7001 in the Hosting operator network over 3GPP access and the UDM 75 receives the Indirect network sharing indication, the UDM 75 may determine that the UE 3 needs to be deregistered, then the UDM 75 may send at least one of the Subscriber data for the UE 3 and the Deregistration request from 3GPP access.

[0213] Step 8. The AMF 7002 sends the Registration Accept message to the UE 3 including 5G-GUTI and Deregistration request from 3GPP access.

[0214] The following bullets explain each parameter in detail. - 5G-GUTI: Refer to Step 6 in Fig. 5. - Deregistration request from 3GPP access: Refer to Step 7.

[0215] Step 9. Upon reception of the Registration Accept message, the UE 3 stores the received data in the Registration Accept message in step 8 into non-volatile memory in the UE 3 or USIM. 　　The UE 3 sends the Registration Complete message to the AMF 7002.

[0216] Step 10. The UE 3 initiates the Deregistration procedure to 3GPP access according to section 4.2.2.3.2 in TS 3GPP 23.502 [3] if the UE 3 receives the Deregistration request from 3GPP access in the Registration Accept message in Step 9.

[0217] After Step 10, Cellular communication services are available to the UE 3 via non-3GPP access.

[0218] At least one of Step 3, Step 8 and Step 9 may be expressed the Registration procedure over non-3GPP access via the N3IWF 4002 in Participating operator network.

[0219] <First Variant of the third scenario in the Second example of the First Aspect> 　　In Step 7, instead of sending the Deregistration request from 3GPP access in the Nudm_SDM_Get Response message, the UDM 75 sends the Nudm_UECM_DeregistrationNotification message to the AMF 7002 after the Step 7 to initiate the Network-initiated Deregistration procedure for 3GPP access.

[0220] <Second Variant of the third scenario in the Second example of the First Aspect> 　　In Step 7, the UDM 75 does not include the Deregistration request from 3GPP access in the Nudm_SDM_Get Response message.

[0221] In this case, the UE 3 holds or keeps two 5G-GUTIs, one for 3GPP access assigned by the AMF 7001 in the Hosting operator network and the other one for non-3GPP access assigned by the AMF 7002 in the Participating operator network.

[0222] In Step 8, the UE 3 does not replace 5G-GUTI for 3GPP access with the received 5G-GUTI in the Registration Accept message in Step 8 even the UE 3 recognizes that the UE 3 is registered to the same PLMN (i.e. the Participating operator network). For example, in a case where the UE 3 receives the message in step 8, the UE 3 may recognize that the UE 3 is registered to the same PLMN (i.e. the Participating operator network).

[0223] <Third Variant of the third scenario in the Second example of the First Aspect> 　　In Nudm_UECM_Registration Response message in Step 5 or Nudm_SDM_Get Response message in Step 7, the UDM 75 sends a reject cause to the AMF 7002. The reject cause indicates that the Registration to the non-3GPP access is not acceptable as the AMF for 3GPP access is assigned in the Hosting operator network.

[0224] Upon reception the reject cause by the AMF 7002, the AMF 7002 sends the Registration Reject message to the UE 3 instead of the Registration Accept message in Step 8 including existing reject cause or new cause indicating that the Registration to the non-3GPP access is not acceptable as the AMF for 3GPP access is assigned in the Hosting operator network. The reject cause may be expressed as rejection cause.

[0225] In one example, if the UE 3 receives the rejection cause, the UE 3 may accept the Registration Reject message and abandon to register to the non-3GPP access.

[0226] In one another example, if the UE 3 receives the rejection cause, the UE 3 initiates the Deregistration procedure with 3GPP access and initiates the Registration procedure with non-3GPP access after successful Deregistration procedure with 3GPP access.

[0227] In one example, the Registration Reject message may contains information element which contains the N3IWF FQDN or IP address of N3IWF of host PLMN (e.g. N3IWF 4001). When the UE 3 receives the N3IWF FQDN or N3IWF IP address of the host PLMN in Registration Reject message the UE 3 may select the N3IWF corresponding to the N3IWF FQDN or N3IWF IP address. The UE 3 may initiate the Registration procedure over the selected N3IWF by sending the Registration Request message containing the 5G-GUTI received in step 1 from the AMF7001 and may also include the 5G-GUTI to the N3IWF. The N3IWF may select the AMF corresponding to the GUAMI of the 5G-GUTI i.e. AMF 7001. Upon reception of the Registration Request message from the UE 3, the AMF 7001 may complete the Registration procedure for non-3GPP access as per the procedure defined in section 4.12.2.2 of 3GPP TS 23.502 [3].

[0228] <Fourth Variant of the third scenario in the Second example of the First Aspect> 　　In one example, when a UE 3 gets trigger to register over non-3GPP access, the UE 3 determines whether the UE 3 is registered over 3GPP access to the Hosting operator network. On determining based on the procedure defined in the Aspects of this disclosure that the UE 3 is registered over 3GPP access to the Hosting operator network, the UE 3 initiates deregistration procedure over 3GPP access to the Hosting operator network. After successful deregistration procedure, the UE 3 initiates registration procedure over non-3GPP access as defined in section 4.12.2.2 of TS 23.502 [3]. In case the UE 3 finds a suitable cell of HPLMN only then the UE 3 may initiate registration procedure to the 3GPP access to the HPLMN by sending Registration Request message containing the 5G-GUTI received over non-3GPP access and also sending this 5G-GUTI in the RRC connection Request message and / or RRC setup complete message. The UE 3 and the HPLMN complete the registration procedure as define in the section 4.2.2.2.2 of TS 23.502 [3].

[0229] <Fifth Variant of the third scenario in the Second example of the First Aspect> 　　In one example, when a UE 3 is registered over non-3GPP access to the HPLMN in the home country and the UE 3 selects a cell of indirect network sharing case (e.g. the cell in the Zone 1), the UE 3 first deregisters for the non-3GPP access and then performs registration procedure for 3GPP access as defined in the step 1.

[0230] In another example, when the UE 3 determines that the UE 3 is registered over non-3GPP access over HPLMN then the UE 3 finds a cell of the HPLMN in the indirect network sharing case, and the UE 3 doesn't initiate registration procedure over 3GPP access until the UE 3 is deregisters over the non-3GPP access.

[0231] In one example, the contents of the above Aspect apply when the UE 3 is registered over non-3GPP access first and the UE 3 finds the cell of HPLMN in case of indirect network sharing deployments.

[0232] <Fourth scenario in the Second example of the First Aspect> 　　The Fourth scenario in the Second example of the First Aspect includes an example mechanism that the UE 3 registers to the AMF 7001 in the Hosting operator network for non-3GPP access through the N3IWF 4002 in the Participating operator network.

[0233] Fig. 9 illustrates an example of mechanism that the UE 3 registers to the AMF 7001 in the Hosting operator network for non-3GPP access through the N3IWF 4002 in the Participating operator network.

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

[0235] Step 1. Steps 0-1 to 1 in Fig. 6 take place.

[0236] Step 2. The UE 3 obtains an IP address from the N3IWF 4002 that is selected according to the N3IWF selection in section 6.3.6 in 3GPP TS 23.501 [2].

[0237] Step 2 may be same to Step 2 in Fig. 8.

[0238] Step 3. After successful an Ipsec Security Association (SA) establishment with the N3IWF 4002, the UE 3 sends the Registration Request message to the AMF 7002 including at least one of User ID and Indirect network sharing capability.

[0239] The following bullets explain each parameter in detail. - User ID: Refer to Step 1 in Fig. 5. - Indirect network sharing capability: Refer to Step 1 in Fig. 5.

[0240] Step 3 may be same to Step 3 in Fig. 8.

[0241] Step 4. Upon reception of the Registration Request message in Step 3, the AMF 7002 sends an Nudm_UECM_Registration Request message to a UDM 75 including at least one of the SUPI and Indirect network sharing indication.

[0242] The following bullets explain each parameter in detail. - SUPI: Refer to Step 2 in Fig. 5. - Indirect network sharing indication: Refer to Step 2 in Fig. 5.

[0243] Step 4 may be same to Step 4 in Fig. 8.

[0244] Step 5. Upon reception of the Nudm_UECM_Registration Request message in Step 4, the UDM 75 sends an Nudm_UECM_Registration Response message to the AMF 7002. 　　Step 5 may be same to Step 5 in Fig. 8.

[0245] Step 6. After the completion of the Nudm_UECM_Registration service in Steps 4 and 5, the AMF 7002 sends an Nudm_SDM_Get Request message to the UDM 75 including at least one of the SUPI and Indirect network sharing indication. Refer to Step 4 for parameter details.

[0246] Step 6 may be same to Step 6 in Fig. 8.

[0247] Step 7. The UDM 75 finds Subscriber data for the UE 3 and sends an Nudm_SDM_Get Response message to the AMF 7002 including the Subscriber data for the UE 3 and Registered AMF name in 3GPP access.

[0248] The following bullets explain each parameter in detail. - Subscriber data: Refer to Step 5 in Fig. 5. - Registered AMF name in 3GPP access: The Registered AMF name in 3GPP access indicates the AMF that is assigned to the UE 3 for 3GPP access. The AMF name may be an AMF that is located in the Hosting operator network based on the Indirect network sharing. - The AMF name may be expressed by the FQDN format or Ipv4 address or Ipv6 address. - For example, the Registered AMF name in 3GPP access may indicate the AMF 7001. - For example, the Registered AMF name in 3GPP access may indicate an AMF (e.g. the AMF 7001) that the UE 3 is registered in the Hosting operator network using the Indirect network sharing.

[0249] After Step 7, the AMF 7002 may take either Step 8-1 or Step 8-2 (e.g. both Step 8-2a and Step 8-2b) depending on operator policy and / or a bilateral agreement between the Hosting operator and the Participating operator in order to re-allocate AMF to the AMF 7001 that assigned the 5G-GUTI to the UE 3 for 3GPP access.

[0250] Optional Step for AMF direct re-allocation

[0251] Step 8-1. The AMF 7002 sends the Namf_Communication_N1MessageNotify message to the AMF 7001 including NAS message. The NAS message is the one that the AMF 7002 receives from the UE 3 in Step 3.

[0252] For example, the AMF 7002 may send the Namf_Communication_N1MessageNotify message to the AMF 7001 which is indicated by the Registered AMF name in 3GPP access.

[0253] For example, the AMF 7002 may send directly the Namf_Communication_N1MessageNotify message to the AMF 7001 which is indicated by the Registered AMF name in 3GPP access.

[0254] <Optional Steps for AMF re-allocation via N3IWF> 　　Step 8-2a. The AMF 7002 sends the Reroute NAS Request message to the N3IWF 4002 including NAS message. The NAS message is the one that the AMF 7002 receives from the UE 3 in Step 3.

[0255] Step 8-2b. The N3IWF 4002 sends the Initial NAS message to the AMF 7001 including NAS message. The NAS message is the one the N3IWF 4002 receives from the AMF 7002 in Step 8-2a.

[0256] For example, the AMF 7002 may send the NAS message to the AMF 7001 which is indicated by the Registered AMF name in 3GPP access, via the N3IWF 4002.

[0257] For example, the AMF 7002 may send the NAS message to the AMF 7001 which is indicated by the Registered AMF name in 3GPP access, indirectly via the N3IWF 4002.

[0258] For example, the AMF 7002 may notify the destination of the NAS message (e.g. the AMF 7001) to the N3IWF 4002, then the N3IWF 4002 may send the NAS message to the AMF 7001.

[0259] Step 9. The UE 3 and core network 7 (e.g. the AMF 7001) in the Hosting operator network continues the Registration procedure from Step 8 in section 4.2.2.2.3 in 3GPP TS 23.502 [3] for non-3GPP access or defined in section 4.12.2.2 of 3GPP TS 23.502 [3].

[0260] For example, the UE 3 and the core network 7 (e.g. the AMF 7001) in the Hosting operator network continues the Registration procedure for the non-3GPP access in the Hosting operator network.

[0261] After successful registration procedure for non-3GPP access, the UE 3 is registered to the AMF 7001 in the Hosting operator network for non-3GPP access with the N3IWF 4002 in the Participating operator network.

[0262] Upon reception of the Registration Accept message, the UE 3 stores the received data in the Registration Accept message in step 8 into non-volatile memory in the UE 3 or USIM.

[0263] The UE 3 sends the Registration Complete message to the AMF 7002.

[0264] After Step 9, the cellular communication services are available to the UE 3 in both 3GPP access and non-3GPP access. For example, the cellular communication services are available to the UE 3 in both 3GPP access and non-3GPP access under the Indirect network sharing environment.

[0265] <First variant of Fourth scenario in the Second example of the First Aspect> 　　In this scenario the UE 3 is configured by the HPLMN (e.g. Participating operator network) whether the UE 3 can select N3IWF of the HPLMN according to the section of 6.3.6 in 3GPP TS 23.501 [2] while the UE 3 is already registered to the hosting network operator. The UE 3 receives this configuration information element in one of the following ways:

[0266] i) It is configured in the USIM in an existing EF or a new EF.

[0267] ii) The UE 3 receives this configuration information from the home PCF (e.g. H-PCF 7302) or visited PCF (e.g. V-PCF 7301) in an existing message defined between the UE 3 and the PCF or a in a new message between the UE 3 and the PCF.

[0268] iii) In an existing NAS message (e.g. Registration accept message or UE configuration update message) or in a new NAS message between the UE 3 and the AMF 7001 when the UE 3 registers to the Hosting operator network or between the UE 3 and the AMF 7002 when the UE 3 was registered before to the HPLMN e.g. AMF 7001. If the UE 3 is configured to select the N3IWF of the HPLMN while the UE 3 is registered to the Hosting network operator i.e. in indirect network sharing case, the UE 3 finds the N3IWF 4002 according to section of 6.3.6 in 3GPP TS 23.501 [2]. The UE 3 initiates registration procedure to the HPLMN which is the Participating network operator over selected N3IWF 4002. The UE 3 may include current 5G-GUTI received over 3GPP access from the Hosting operator network in the registration request message. In one example the UE 3 may include SUCI in the registration request message.

[0269] In one example, when the AMF 7002 receives the registration request message in step 3, the AMF 7002 proceeds with Registration procedure over non-3GPP access in the HPLMN i.e., on the participating PLMN as per the procedure defined in section 4.12.2 of 3GPP TS 23.502 [3]. After successful registration procedure the UE 3 maintains two independent UE contexts (e.g. 5GMM context, security context, 5G-GUTI), one over the Hosting operator network and another over the HPLMN i.e., on the Participating operator network. When the UE 3 moves out and the UE 3 selects a non-sharing cell of the HPLMN (e.g. the UE 3 moves out from the area for the Indirect network sharing and selects the cell of the HPLMN (e.g. the Participating operator)) then the UE 3 performs registration procedure to the HPLMN and the UE 3 may include 5G-GUTI of the Hosting operator network. The registration procedure is executed as defined in section 4.2.2.2 or 4.12.8 of 3GPP TS 23.503 [3]. In one example the AMF 7002 receives information element in an existing message or in a new message between the UDM 75 and the AMF 7002 from the UDM 75 indicating whether to continue the Registration procedure in the Participating operator network or in the Hosting operator network. If the information element indicates that the Registration procedure is allowed to register to HPLMN while the UE 3 is registered to the Hosting operator network over 3GPP access, then the AMF 7002 proceeds with the Registration procedure in the Hosting operator network, otherwise the AMF 7002 executes steps 8-9 defined in the Fig. 9.

[0270] <Second variant of Fourth scenario in the Second example of the First Aspect> 　　In one example, the UE 3 is registered over non-3GPP access to the participating operator network (HPLMN) and the UE 3 finds the cell of the HPLMN in indirect network sharing case, then the UE 3 initiates registration over 3GPP access includes current 5G-GUTI received over non-3GPP access. The AMF 7001 may fetch the UE context for the non-3GPP access from AMF 7002 using an existing message or a new message defined between AMF 7001 and AMF 7002 using an existing service operation or procedure or new service operation or procedure defined between AMF 7001 and AMF 7002. After the non-3GPP access context is fetched successfully in AMF 7001, then the AMF 7001 may send an indicator to the UE 3 that the UE 3 is registered for both 3GPP access and non-3GPP access in the Participating operator network in the registration accept message or in an existing NAS message or in a new NAS message. The AMF 7001 may also include a 5G-GUTI in the NAS the message. When the UE 3 receives the NAS message the UE 3 considers itself registered for both 3GPP access and non-3GPP access to the Participating operator network which provided the 5G-GUTI. The UE 3 uses the received 5G-GUTI for the both 3GPP access and non-3GPP access AS and NAS procedure until a new 5G-GUTI is received.

[0271] <Fifth scenario in the Second example of the First Aspect> 　　The Fifth scenario in the Second example of the First Aspect includes an example mechanism that the UE 3 does not initiate the Registration procedure for non-3GPP access as the UE 3 recognizes that the UE 3 is registered to the AMF 7001 in the Hosting operator.

[0272] In one example, the UE 3 does not initiate the Registration procedure over non-3GPP access as the UE 3 recognizes that having a common AMF for both 3GPP access and non-3GPP access is not possible.

[0273] In one example, the common AMF may be the AMF 7001.

[0274] For example, before initiating the Registration procedure for non-3GPP access in the Participating operator network, the UE 3 may determine whether the UE 3 is registered to the AMF 7001 in the Hosting operator. In a case where the UE 3 determines that the UE 3 is registered to the AMF 7001 in the Hosting operator, the UE 3 may not initiate the Registration procedure for non-3GPP access in the Participating operator network or may retain to initiate the Registration procedure for non-3GPP access in the Participating operator network or stop initiating the Registration procedure for non-3GPP access in the Participating operator network. When the UE 3 goes out of coverage of Indirect network sharing and finds non-sharing cell of the HPLMN (e.g. the cell of the HPLMN (e.g. the Participating operator)), the UE 3 registers to the HPLMN over 3GPP access. After the successful Registration procedure over the 3GPP access and receiving a new 5G-GUTI, the UE 3 selects an N3IWF in the HPLMN as defined in section 6.3.6 in 3GPP TS 23.501 [2] and initiates registration to the non-3GPP access to the HPLMN using the new 5G-GUTI.

[0275] In one example, the UE 3 selects a N3IWF in the HPLMN as soon as the UE 3 deregisters over 3GPP access i.e. the UE 3 goes to 5GMM.DEREGISTERED state for 3GPP access.

[0276] <Second Aspect> 　　This aspect includes example mechanisms for mobility management when the indirect network is deployed in the PLMN.

[0277] In case that the UE 3 moves out from an area for indirect network sharing and there are cells provided by an operator which the UE 3 has a contract with (i.e., participating operator, which may be equal to an HPLMN), the UE 3 needs to select a cell provided by the participating operator.

[0278] On the other hand, there may be cells provided by the Hosting operator without RAN sharing with the Participating operator.

[0279] In this case, the UE 3 may keep on staying with Cells of the Hosting operator because the UE holds a Hosting operator as the Registered PLMN. (i.e., the UE holds a 5G-GUTI provided by the Hosting operator.)

[0280] At least one of example mechanisms that are disclosed in this Aspect aim to let the UE 3 select a cell provided by the Participating operator when the UE 3 moves out from an area for the indirect network sharing.

[0281] In this Aspect, the Zone 1 in Fig. 2 is referred as the area for the indirect network sharing.

[0282] The Zone 2 and the Zone 3 in Fig. 2 are referred as the area where the indirect network sharing does not apply.

[0283] <First example of the Second Aspect> 　　This example includes example mechanisms for the UE 3 to register from a Cell provided by the Participating operator after the UE 3 moves out from an area for Indirect network sharing (i.e. the Zone 1 in Fig. 2) and moves into an area where both the Hosting operator and the Participating operator have separate coverages (i.e. the Zone 2 in Fig. 2) for cellular communication services.

[0284] Fig. 10 illustrates an example of mechanism that the UE 3 registers from a Cell provided by the Participating operator, with assistance by the NAS level signalling, after the UE 3 moves out from an area for Indirect network sharing (i.e. the Zone 1 in Fig. 2) and moves into an area where both the Hosting operator and the Participating operator have separate coverages (i.e. the Zone 2 in Fig. 2) for cellular communication services.

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

[0286] Step 0. The UE 3 registers to the AMF 7001 in the Hosting operator network over 3GPP access (or non-3GPP access) in an area for Indirect network sharing (e.g. Zone 1 in Fig. 2). A 5G-GUTI is assigned by the AMF 7001 as a temporary identifier for the UE 3.

[0287] Step 1. The UE 3 moves out from the area for Indirect network sharing (e.g. Zone 1 in Fig. 2). Then the UE 3 moves into an area where both the Hosting operator and the Participating operator have separate coverages (i.e. the Zone 2 in Fig. 2).

[0288] Step 2-1. The UE 3 receives and reads the System Information from a Cell with RAN 502 in the Hosting operator Network.

[0289] Step 2-2. The UE 3 also receives and reads the System Information from a Cell with RAN 503 in the Participating operator Network. Step 2-2 may be performed before Step 2-1.

[0290] Steps 3. As the UE 3 holds the 5G-GUTI assigned by the Hosting operator and considers the Hosting operator as the Registered PLMN, the UE 3 sends the Registration Request message to the AMF 7002 in the Hosting operator network including User ID. User ID may have the 5G-GUTI assigned in Step 0 by the AMF 7001.

[0291] Step 4. Upon reception of the Registration Request message from the UE 3 in Step 3, the AMF 7002 examines a Tracking Area (TA) and / or cell ID where the UE is located, and checks whether the area where the UE 3 is located is an area for the Indirect network sharing.

[0292] The Tracking Area (TA) and cell ID (for example, E-UTRA CGI or NR CGI) may be obtained by the AMF 7002 from the User Location Information parameter in the Initial UE message from the RAN 502 that carries the Registration request message in Step 3.

[0293] For example, the AMF 7002 may know or understand, based on local configuration in the AMF 7002, the area for the Indirect network sharing.

[0294] For example, the AMF 7002 may store or receive (e.g. from other network node(s)) information for checking whether the area where the UE 3 is located is an area for the Indirect network sharing.

[0295] For example, the information for checking whether the area where the UE 3 is located is an area for the Indirect network sharing may indicate correspondence between the area for the Indirect network sharing and TA and / or cell ID. For example, the AMF 7002 may know or understand, based on TA and / or cell ID, the area for the Indirect network sharing. For example, the AMF 7002 may know or understand, based on the above information and TA and / or cell ID, the area for the Indirect network sharing. The above information may be included in local configuration in the AMF 7002.

[0296] In one example, the AMF 7002 may fetch the UE context from old AMF 7001 using the step(s) described in section 4.2.2.2 of 3GPP TS 23.501 [2].

[0297] Step 5. If the AMF 7002 concludes that the area where the UE 3 is located is not a subject for the Indirect network sharing based on location configuration in the AMF 7002, the AMF 7002 sends the Registration reject message to the UE 3 including at least one of Cause=no Indirect network sharing (or cause value or cause code which is set to no Indirect network sharing) and Re-registration after PLMN selection required. The expression "Cause=no Indirect network sharing" may mean "Cause (or cause value or cause code) is set to no Indirect network sharing".

[0298] The following bullets explain each parameter in detail. - Cause=no Indirect network sharing: The Cause=no Indirect network sharing indicates that the area where the UE 3 is located is not a subject for the Indirect network sharing. This may be a reason for rejecting the Registration request message. - The Cause=no Indirect network sharing may indicate that the area where the UE 3 is located is not the area for the Indirect network sharing. - The Cause=no Indirect network sharing may indicate that the area where the UE 3 is located is outside of the area for the Indirect network sharing. - The Cause=no Indirect network sharing may indicate that the area where the UE 3 is located is not the area where the Indirect network sharing is available. - The Cause=no Indirect network sharing may indicate that the area where the UE 3 is located is outside of the area where the Indirect network sharing is available. - In one example, the Cause may be an existing cause, for example, Roaming not allowed. For example, the Cause which is set to Roaming not allowed may indicate that the area where the UE 3 is located is not a subject for the Indirect network sharing. - Re-registration after PLMN selection required: The Re-registration after PLMN selection required indicates that the UE 3 is requested to perform the PLMN selection and / or to perform the Registration procedure with a PLMN selected by the PLMN selection procedure (or the PLMN selection).

[0299] The UE 3 may perform the integrity protection and optionally cypher the Registration Reject message using the security context fetched from the AMF 7001.

[0300] Step 6. Upon reception of the Registration reject message from the AMF 7002, the UE 3 preforms the PLMN selection procedure as the UE 3 receives the Re-registration after PLMN selection required in the Registration reject message in Step 5. The UE 3 may find a Cell provided by the Participating operator as the Participating operator network may be set as the highest operator network to select in the USIM or non-volatile memory in the UE 3. For example, the UE 3 belonging to the Participating operator may find a Cell provided by the Participating operator as the Participating operator network may be set as the highest operator network to select in the USIM or non-volatile memory in the UE 3.

[0301] Step 7. The UE 3 initiates the Registration procedure with AMF 7003 through RAN 503 according to section 4.2.2.2.2 in 3GPP TS 23.502 [3] as the UE 3 receives the Re-registration after PLMN selection required in the Registration reject message in Step 5.

[0302] After successful Registration procedure in Step 7, the UE 3 registers to the AMF 7003 in the Participating operator network.

[0303] <First Variant of the First example of the Second Aspect> 　　In Step 1, if the UE 3 moves to an area where only the Participating operator network has a coverage (for example, Zone 3 in Fig. 2), the UE 3 performs Steps 6 and 7 as there is no other choices.

[0304] <Second example of the Second Aspect> 　　This example includes example mechanisms for the UE 3 to register from a Cell provided by the Participating operator, with assistance by the AS level signalling, after the UE 3 moves out from an area for Indirect network sharing (i.e. the Zone 1 in Fig. 2) and moves into an area where both the Hosting operator and the Participating operator have coverages (i.e. the Zone 2 in Fig. 2) for cellular communication services.

[0305] Fig. 11 illustrates an example of mechanism that the UE 3 registers from a Cell provided by the Participating operator, with assistance by the AS level signalling, after the UE 3 moves out from an area for Indirect network sharing (i.e. the Zone 1 in Fig. 2) and moves into an area where both the Hosting operator and the Participating operator have coverages (i.e. the Zone 2 in Fig. 2) for cellular communication services.

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

[0307] Step 0. The UE 3 registers to the AMF 7001 in the Hosting operator network over 3GPP access (or non-3GPP access) in an area for Indirect network sharing (e.g. Zone 1 in Fig. 2). A specific 5G-GUTI for a subscriber from the Participating operator network is assigned by the AMF 7001 as a temporary identifier for the UE 3.

[0308] For example, the UE 3 may perform a Registration procedure to the AMF 7001 in the Hosting operator network over 3GPP access in an area for Indirect network sharing, and the specific 5G-GUTI is assigned by the AMF 7001 to the UE 3 during the Registration procedure.

[0309] Based on local configuration of the AMF 7001, the AMF 7001 may assign the specific 5G-GUTI (e.g. the 5G-GUTI including the field "I" or the field "Participating operator ID" as shown below) to the UE 3.

[0310] For example, the AMF 7001 may store or receive (e.g. from other network node(s)) information indicating the UE 3 (or a subscriber of the UE 3 or user of the UE 3) is a subscriber from the Participating operator network. Based on the information, the AMF 7001 may assign the specific 5G-GUTI to the UE 3.

[0311] The AMF 7001 may store or receives (e.g. from other network node(s)) information indicating which UEs (or subscribers of the UEs or users of the UEs) are subscribers from the Participating operator network. Based on the information, the AMF 7001 may determine that the UE 3 is a subscriber from the Participating operator network, and assign the specific 5G-GUTI to the UE 3.

[0312] The above stored or received information may indicate correspondence between User ID and the subscriber from the Participating operator network. Based on the information and the User ID (e.g. the User ID received by the Registration request message in step 0), the AMF 7001 may determine that the UE 3 is a subscriber from the Participating operator network, and assign the specific 5G-GUTI to the UE 3.

[0313] The AMF 7001 may have a specific range of 5G-TMSI for 5G-GUTI to be assigned to a subscriber from the Participating operator network.

[0314] Fig. 12 illustrates an example of the 5G-GUTI format specific to a subscriber from the Participating operator network.

[0315] The 5G-GUTI includes GUAMI and 5G-TMSI where the GUAMI has MCC, MNC and AMF Identifier.

[0316] 5G-TMSI identifies the UE 3 uniquely within the AMF 7001.

[0317] In the specific 5G-GUTI for a subscriber from the Participating operator network in Fig. 12, the 5G-TMSI field is separated into a field "I" and a field for Temporary identifier. I.e. the 5G-TMSI includes the field "I" and the field for Temporary identifier.

[0318] The field "I" may be a one-bit data.

[0319] The field "I" is a discriminator whether the UE 3 is coming from any Participating operator networks or not.

[0320] The field " I" may be located at MSB in the 5G-TMSI filed or at the LSB in the 5G-TMSI field.

[0321] Value 1 in the field "I" may indicate that the 5G-GUTI is for a subscriber (or the UE 3) coming from the Participating operator network or may indicate that the 5G-GUTI is for the Participating operator network. Value 1 in the field "I" may indicate that the subscriber or the UE 3 is a subscriber or the UE 3 in the Participating operator network. Value 1 in the field "I" may indicate that the subscriber or the UE 3 that this 5G-GUTI is assigned is a subscriber or the UE 3 in the Participating operator network.

[0322] Value 0 in the field "I" may indicate that the 5G-GUTI is for a subscriber coming from the Non Participating operator network or may indicate that the 5G-GUTI is for the Non Participating operator network. Value 0 in the field "I" may indicate that the subscriber or the UE 3 is a subscriber or the UE 3 in the Non Participating operator network. Value 0 in the field "I" may indicate that the subscriber or the UE 3 that this 5G-GUTI is assigned is a subscriber or the UE 3 in the Non Participating operator network.

[0323] The field for Temporary identifier identifies the UE 3 uniquely within the AMF 7001 which came from any Participating operator network.

[0324] In another example, the AMF 7001 may have a specific range of 5G-TMSI for 5G-GUTI to be assigned to a subscriber per a Participating operator that has a contract for the Indirect network sharing.

[0325] Fig. 13 illustrates an example of the 5G-GUTI format specific to a subscriber from the Participating operator network.

[0326] The 5G-GUTI includes GUAMI and 5G-TMSI where the GUAMI has MCC, MNC and AMF Identifier.

[0327] 5G-TMSI identifies the UE 3 uniquely within the AMF 7001.

[0328] In the specific 5G-GUTI for a subscriber from the Participating operator network in Fig. 13, the 5G-TMSI filed is separated into a field "Participating operator ID" and a field for Temporary identifier. I.e. the 5G-TMSI includes the field "Participating operator ID" and the field for Temporary identifier.

[0329] The field for Temporary identifier uniquely identifies 5G-TMSI.

[0330] The field "Participating operator ID" may have at least one bit length that identifies a Participating operator or a Participating operator network. The field "Participating operator ID" may be a PLMN ID of the Participating operator.

[0331] The field "Participating operator ID" may be a normalized value for the Participating operator that is valid only in the Hosting operator network.

[0332] The field for Temporary identifier identifies the UE 3 uniquely within the AMF 7001 which came from a specific Participating operator network that is identified by the field "Participating operator ID".

[0333] The 5G-GUTI assigned in Step 0 may include the field "I" which is set to 1 or the field "Participating operator ID" which indicates a Participating operator.

[0334] Return to the explanation of Fig. 11.

[0335] For example, the UE 3 may generate 5G S-TMSI based on the 5G-GUTI assigned in Step 0. For example, the UE 3 may generate 5G S-TMSI based on 5G-TMSI of the 5G-GUTI assigned in Step 0.

[0336] As 5G-TMSI includes the specific value (e.g. the field "I" or the field "Participating operator ID"), the 5G S-TMSI generated based on the 5G-TMSI may also include the specific value (e.g. the field "I" or the field "Participating operator ID").

[0337] Step 1. Steps 1 to 2-2 in Fig. 10 take place.

[0338] Step 2. As the UE 3 holds the 5G-GUTI assigned by the Hosting operator and considers the Hosting operator as the Registered PLMN, the UE 3 sends the RRC Setup Request message to the RAN 502 including 5G S-TMSI. The 5G S-TMSI is a User identifier of the UE 3.

[0339] For example, the 5G S-TMSI in Step 2 may include 5G-TMSI of the 5G-GUTI assigned in Step 0.

[0340] Step 3. Upon reception of the RRC Setup Request message in Step 2 from the UE 3, the RAN 502 sends the RRC Setup message to the UE 3.

[0341] Step 4. The UE 3 sends the RRC Setup Complete message to the RAN 502 including 5G-GUTI and Dedicated NAS.

[0342] The following bullets explain each parameter in detail. - 5G-GUTI: The 5G-GUTI is a temporary user identifier for the UE 3. For example, the 5G-GUTI in Step 4 may be the 5G-GUTI assigned in Step 0. - Dedicated NAS: The Dedicated NAS includes the NAS message. The NAS message may be the Registration request message.

[0343] Step 5. Upon reception of the RRC Setup Complete message from the UE 3 in Step 4, the RAN 502 examines the 5G S-TMSI received in step 2 and / or the 5G-GUTI received in step 4 and finds that the UE 3 belongs to a Participating operator.

[0344] In one example, the RAN 502 finds that the UE 3 belongs to a Participating operator based on a value of the specific 5G S-TMSI for the UE 3 as explained in the Step 0.

[0345] In one example, the RAN 502 may find or determine that the UE 3 belongs to a Participating operator in a case where the received 5G S-TMSI includes the field "I" which indicates that the 5G-GUTI is for a subscriber coming from the Participating operator network (e.g. the field "I" which is set to 1) as explained in the Step 0.

[0346] In one example, the RAN 502 may find or determine that the UE 3 belongs to a Participating operator in a case where the received 5G S-TMSI includes the field "Participating operator ID" (e.g. the field "Participating operator ID" which indicates the Participating operator, the field "Participating operator ID" which indicates PLMN ID of the Participating operator etc.) as explained in the Step 0.

[0347] In another example, the RAN 502 finds that the UE 3 belongs to a Participating operator based on a value of the MCC part and MNC part of GUAMI in the 5G-GUTI. For example, in a case where the Participating operator is indicated by at least one of the MCC part and the MNC part, the RAN 502 may find or determine that the UE 3 belongs to a Participating operator.

[0348] If the MCC part and MNC part indicate a PLMN operator that the Hosting operator does not have roaming agreements, the RAN 502 finds that the UE 3 belongs to a Participating operator.

[0349] For example, the RAN 502 may find or determine that the UE 3 belongs to a Participating operator in a case where the received 5G S-TMSI includes the field "Participating operator ID" (e.g. the field "Participating operator ID" which indicates the Participating operator, the field "Participating operator ID" which indicates PLMN ID of the Participating operator etc.) and / or in a case where the Participating operator is indicated by at least one of the MCC part and the MNC part.

[0350] For example, the RAN 502 may find or determine that the UE 3 belongs to a Participating operator in a case where the received 5G S-TMSI includes the field "I" which indicates that the 5G-GUTI is for a subscriber coming from the Participating operator network (e.g. the field "I" which is set to 1) and / or in a case where the Participating operator is indicated by at least one of the MCC part and the MNC part.

[0351] Step 6. The RAN 502 sends the RRC Release message to the UE 3 including PLMN Selection required. The PLMN Selection required indicates to the UE 3 that the UE 3 is requested to perform the PLMN selection and to perform the Registration procedure with a PLMN selected by the PLMN selection procedure. For example, the RAN 502 may send the RRC Release message in a case where the RAN 502 finds or determines that the UE 3 belongs to a Participating operator in Step 5.

[0352] Step 7. Steps 6 and 7 in Fig. 10 take place.

[0353] After successful Registration procedure in Step 7, the UE 3 registers to the AMF 7003 in the Participating operator network.

[0354] <Third example of the Second Aspect> 　　This example includes example mechanisms for the UE 3 to register from a Cell provided by the Participating operator after the UE 3 moves out from an area for Indirect network sharing (i.e. the Zone 1 in Fig. 2) and moves into an area where both the Hosting operator and the Participating operator have coverages (i.e. the Zone 2 in Fig. 2) for cellular communication services.

[0355] Fig. 14 illustrates an example of mechanism that the UE 3 registers to a Cell provided by the Participating operator, by referring to system information, after the UE 3 moves out from an area for Indirect network sharing (i.e. the Zone 1 in Fig. 2) and moves into an area where both the Hosting operator and the Participating operator have coverages (i.e. the Zone 2 in Fig. 2) for cellular communication services.

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

[0357] Step 1. The UE 3 registers to the AMF 7001 in the Hosting operator network over 3GPP access (or non-3GPP access) in an area for the Indirect network sharing (for example, Zone 1 in Fig. 2). A 5G-GUTI is assigned by the AMF 7001 as a temporary identifier for the UE 3. The MCC and MNC part of the 5G-GUTI may be set to MCC and MNC of the Hosting operator network to which the AMF 7001 belongs.

[0358] Step 2. The UE 3 recognizes that the UE 3 is registered with AMF 7001 in the Hosting operator network.

[0359] In one example, the UE 3 recognizes that the UE 3 is registered in the Hosting operator network based on the disclosed mechanisms in the First example of the First Aspect.

[0360] Step 3. The UE 3 stores at least one of the 5G-GUTI received in Step 1 and "host plmn" in UE memory or USIM.

[0361] The UE 3 behaves or performs extra actions in the following bullets if the UE recognizes that UE 3 is in a Hosting operator network. - The UE 3 treats itself as the UE 3 is registered to the Participating operator network. For example, the AS layer and / or NAS layer of the UE 3 reports a registration status to upper layer of the UE 3 and the UE 3 shows or does not show an icon for roaming status as the same way when the UE 3 is registered to the Participating operator network. For example, the UE 3 does not show the icon for roaming status even if the UE 3 is in the Hosting operator network (or even if the UE 3 is registered to the Hosting operator network). For example, the UE 3 may show the icon indicating that the UE 3 is in the Participating operator network even if the UE 3 is in the Hosting operator network (or even if the UE 3 is registered to the Hosting operator network). These icons may be displayed on the display of the UE 3.The UE 3 may show the Participating operator name even if the UE 3 is registered to the host PLMN (e.g. the Hosting operator). - The UE 3 does not start the Preferred PLMN timer or background scanning timer T or Timer T as defined in 3GPP TS 23.122 [4] while the UE 3 is in the Participating operator network.

[0362] Step 4. The UE 3 moves out from the area for Indirect network sharing (for example, Zone 1 in Fig. 2).

[0363] In one example, the UE 3 recognizes that the UE 3 is not in the area for Indirect network sharing by reading or receiving the SIB1 and checking whether the SIB1 broadcasts a PLMN ID of the Participating operator network or not.

[0364] In another example, the UE 3 recognizes that the UE 3 is not in the area for Indirect network sharing by reading or receiving the SIB1 of a cell belonging to an PLMN ID indicated by the stored "host plmn" and checking whether the SIB1 broadcasts a PLMN ID of the Participating operator network or not.

[0365] In another example, the UE 3 recognizes that the UE 3 is not in the area for Indirect network sharing by reading or receiving the system information as disclosed in Step 1-1 of Fig. 4 and checking whether the system information SIB1 broadcasts the Hosting operator network PLMN Identity or not.

[0366] In another example, the UE 3 recognizes that the UE 3 is not in the area for Indirect network sharing by reading or receiving the system information as disclosed in Step 1-2 of Fig. 4 and checking whether the system information SIB1 broadcasts a PLMD ID for the home network of the UE3 in the Participating operator network PLMN Identity list or not.

[0367] If not for any examples in above (e.g. if the received SIB 1 includes the PLMN ID of the Participating operator network only, if the received SIB 1 does not include the PLMN ID of the Hosting operator network, if the UE 3 does not receive the SIB 1 including both the PLMN ID of the Hosting operator network and the PLMN ID of the Participating operator network but the UE 3 receives the SIB 1 including the PLMN ID of the Participating operator network only, if the UE 3 does not receive the SIB 1 including both the PLMN ID of the Hosting operator network and the PLMN ID of the Participating operator network but the UE 3 receives separately one SIB 1 including the PLMN ID of the Hosting operator network only and another SIB 1 including the PLMN ID of the Participating operator network only, if the UE 3 receives separately one SIB 1 including the PLMN ID of the Hosting operator network only and another SIB 1 including the PLMN ID of the Participating operator network only etc.), the UE 3 recognizes that the UE 3 is outside of the area for Indirect network sharing.

[0368] For example, in an area for the Indirect network sharing (for example, Zone 1 in Fig. 2), the RAN (e.g. RAN 501) may broadcast the system information (e.g. SIB 1) including both the PLMN ID of the Hosting operator network and the PLMN ID of the Participating operator network.

[0369] For example, in an area where both the Hosting operator and the Participating operator have coverages (i.e. the Zone 2 in Fig. 2), the RAN (e.g. RAN 502) may broadcast the system information (e.g. SIB 1) including the PLMN ID of the Hosting operator network, and the RAN (e.g. RAN 503) may broadcast the system information (e.g. SIB 1) including the PLMN ID of the Participating operator network.

[0370] In one example, the PLMN ID of the Participating operator network may be the same as the MCC and MNC part of the SUPI in the USIM of the UE 3.

[0371] After the UE 3 recognizes that the UE 3 is not in the area for Indirect network sharing, the UE 3 performs the PLMN selection.

[0372] The Participating operator network may be selected based on the PLMN selection priority list in the USIM of the UE 3.

[0373] For example, in a case where the UE 3 recognizes that the UE 3 is not in the area for Indirect network sharing, the UE 3 may perform the PLMN selection and select the Participating operator network based on the PLMN selection priority list in the USIM of the UE 3.

[0374] For example, in a case where the UE 3 recognizes that the UE 3 is not in the area for Indirect network sharing, the UE 3 which belonging to the Participating operator may perform the PLMN selection and select the Participating operator network based on the PLMN selection priority list in the USIM of the UE 3.

[0375] Step 5. The UE 3 initiates the Registration procedure with AMF 7003 through RAN 503 in the Participating operator network according to section 4.2.2.2.2 in 3GPP TS 23.502 [3].

[0376] For example, the UE 3 may perform process(es) in the Second Aspect (for example, the process(es) in First example of the Second Aspect, the process(es) in Second example of the Second Aspect) to register to the Participating network instead of the Hosting operator network.

[0377] For example, as the UE 3 treats itself as the UE 3 is registered to the Participating operator network, the UE 3 may perform the Registration procedure with AMF 7003 through RAN 503 in the Participating operator network according to section 4.2.2.2.2 in 3GPP TS 23.502 [3]. The UE 3 may send the Registration Request message containing the 5G-GUTI in step 1.

[0378] In one example, the UE 3 may discard the 5G-GUTI received in the step 1 and includes SUCI in the registration request message.

[0379] After successful Registration procedure in Step 5, the UE 3 registers to the AMF 7003 in the Participating operator network.

[0380] <Fourth example of the Second Aspect> 　　This example includes example mechanisms for the UE 3 to register from a Cell provided by the Participating operator after the UE 3 moves out from an area for Indirect network sharing (i.e. the Zone 1 in Fig. 2) and moves into an area where both the Hosting operator and the Participating operator have coverages (i.e. the Zone 2 in Fig. 2) for cellular communication services.

[0381] Fig. 15 illustrates an example of mechanism that the UE 3 registers from a Cell provided by the Participating operator, by referring to system information, after the UE 3 moves out from an area for Indirect network sharing (i.e. the Zone 1 in Fig. 2) and moves into an area where both the Hosting operator and the Participating operator have coverages (i.e. the Zone 2 in Fig. 2) for cellular communication services.

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

[0383] Step 1. The UE 3 registers to the AMF 7001 in the Hosting operator network over 3GPP access in an area for the Indirect network sharing (for example, Zone 1 in Fig. 2). A 5G-GUTI is assigned by the AMF 7001 as a temporary identifier for the UE 3.

[0384] The 5G-GUTI assigned by the AMF 7001 has a PLMN ID (e.g. MCC and MNC) of the Participating operator network.

[0385] For example, the AMF 7001 may assign the 5G-GUTI to the UE 3 during the Registration procedure for the Hosting operator network over 3GPP access in an area for the Indirect network sharing.

[0386] For example, the AMF 7001 generates the 5G-GUTI based on one of the following Steps. - The AMF 7001 generates the 5G-GUTI in general. I.e., a PLMN ID (e.g. MCC and MNC) part of the 5G-GUTI is the one for the Participating operator network. The Participating operator is the one which is selected by the UE 3 to register to. The AMF 7001 determines participating PLMN (or the Participating operator network) which is sent as selected PLMN from RAN 501 to the AMF 7001 in an existing NGAP message when the UE 3 is transitioning from the Idle mode to the connected mode. For example, this MCC and MNC of the TAI or CGI present in the UE location information of the Initial UE message. For example, the AMF 7001 may generate the 5G-GUTI including the PLMN ID (e.g. MCC and MNC) of the Participating operator network. For example, the AMF 7001 may receive, from the RAN 501, PLMN ID (e.g. MCC and MNC) of the Participating operator network which is in the user location information in the Initial UE message, and the AMF 7001 may generate the 5G-GUTI including the PLMN ID (e.g. MCC and MNC) of the Participating operator network. For example, the AMF 7001 may store PLMN ID (e.g. MCC and MNC) of the Participating operator network, and the AMF 7001 may generate the 5G-GUTI including the PLMN ID (e.g. MCC and MNC) of the Participating operator network. - The AMF 7001 replaces the PLMN ID (MCC and MNC) part of the 5G-GUTI with the PLMN ID (MCC and MNC) for the Participating operator network. For example, first, the AMF 7001 may generate the 5G-GUTI including the PLMN ID (e.g. MCC and MNC) of the Hosting operator network, then the AMF 7001 may generate the 5G-GUTI including the PLMN ID (e.g. MCC and MNC) of the Participating operator network by replacing the PLMN ID of the Hosting operator network with the PLMN ID of the Participating operator network. For example, the AMF 7001 may store or receive (from other network node(s), e.g. the RAN 501) the PLMN ID of the Participating operator network.

[0387] With this 5G-GUTI assignment, uniqueness of the 5G-GUTI for the UE 3 is guaranteed in the AMF 7001.

[0388] As the AMF 7001 assigns a 5G-GUTI with a PLMN ID (MCC and MNC) of the Participating operator network, the following example mechanisms may be needed in the RAN 501 and other RAN in the Hosting operator network.

[0389] <Additions to the Routing table> 　　In order to make the AMF selection for the AMF 7001 possible with the assigned 5G-GUTI by the AMF 7001, new entry for the Routing table may be needed. New entry for the Routing table includes a PLMN ID (e.g. MCC and MNC) of the Participating operator network that makes the selection of the AMF 7001 and routing to the AMF 7001 possible.

[0390] <New AMF selection logic in the RANs in the Hosting operator network> 　　When the RAN 501 needs to perform the AMF selection based on the 5G-GUTI that has a different MCC and MNC of the Hosting operator network, the RAN 501 replaces the PLMN ID (e.g. MCC and MNC) part of the 5G-GUTI with the PLMN ID (e.g. MCC and MNC) for the Hosting operator network and the RAN 501 performs the AMF selection with the converted 5G-GUTI.

[0391] For example, this conversion is only needed in the RAN 501 if the RAN 501 recognizes that PLMN ID (e.g. MCC and MNC) before the conversion is a PLMN ID of a Participating operator network based on a configuration in the RAN 501.

[0392] For example, in a case where the RAN 501 needs to perform the AMF selection based on the 5G-GUTI, the RAN 501 may replace the PLMN ID (e.g. MCC and MNC) of the 5G-GUTI including the PLMN ID of the Participating operator network with the PLMN ID (e.g. MCC and MNC) of the Hosting operator network, then the RAN 501 performs the AMF selection based on the 5G-GUTI including the PLMN ID (e.g. MCC and MNC) of the Hosting operator network. For example, the RAN 501 may store the PLMN ID (e.g. MCC and MNC) of the Hosting operator network.

[0393] Step 2. The UE 3 recognizes that the UE 3 is registered with AMF 7001 in the Hosting operator network.

[0394] In one example, the UE 3 recognizes that the UE 3 is registered in the Hosting operator network based on the disclosed mechanisms in the First example of the First Aspect.

[0395] Step 3. The UE 3 stores at least one of the 5G-GUTI received in Step 1 and "host plmn" in UE memory or USIM.

[0396] The UE 3 behaves or performs extra actions in the following bullets if the UE recognizes that UE 3 is in a Hosting operator network. - The UE 3 treats itself as the UE 3 is registered to the Participating operator network. For example, the UE 3 shows or does not show an icon for roaming status as the same case when the UE 3 is registered to the Participating operator network.

[0397] The Step 3 may be same to the Step 3 in Third example of the Second Aspect.

[0398] Step 4. The UE 3 moves out from the area for Indirect network sharing (e.g. Zone 1 in Fig. 2).

[0399] In one example, the UE 3 recognizes that the UE 3 is not in the area for Indirect network sharing by reading or receiving the SIB1 and checking whether the SIB1 broadcasts a PLMN ID of the Participating operator network or not. If not, the UE 3 is outside of the area for Indirect network sharing.

[0400] In one example, the PLMN ID of the Participating operator network may be the same as the MCC and MNC part of the SUPI in the USIM of the UE 3.

[0401] After the UE 3 recognizes that the UE 3 is not in the area for Indirect network sharing, the UE 3 performs the PLMN selection.

[0402] The Participating operator network may be selected based on the PLMN selection priority list in the USIM of the UE 3.

[0403] The Step 4 may be same to the Step 4 in Third example of the Second Aspect.

[0404] Step 5. The UE 3 initiates the Registration procedure, with the User Identity set to the SUCI of the UE 3 in the Registration request message, with AMF 7003 through RAN 503 according to section 4.2.2.2.2 in 3GPP TS 23.502 [3].

[0405] For example, the UE 3 may initiate the Registration procedure by sending the Registration request message which includes the User Identity set to the SUCI of the UE 3.

[0406] For example, the UE 3 may initiate the Registration procedure by sending the Registration request message which includes the User Identity set to the SUCI of the UE 3, instead of the 5G-GUTI assigned by the AMF 7001 in Step 1.

[0407] For example, the UE 3 may use the SUCI of the UE 3, instead of the 5G-GUTI assigned by the AMF 7001 in Step 1, for initiating the Registration procedure.

[0408] Note that the 5G-GUTI assigned by the AMF 7001 in Step 1 is not sent outside of the Hosting operator network as the assigned 5G-GUTI by the AMF 7001 is valid only within the Hosting operator network.

[0409] After successful Registration procedure in Step 5, the UE 3 registers to the AMF 7003 in the Participating operator network.

[0410] <System overview> 　　Fig. 16 schematically illustrates a telecommunication system 1 for a mobile (cellular or wireless) to which the above aspects are applicable.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0447] <N3IWF> 　　Fig. 18 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.

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

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

[0450] <non-3GPP access> 　　Fig. 19 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.

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

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

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

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

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

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

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

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

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

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

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

[0462] <System overview of (R)AN node 5 based on O-RAN architecture> 　　Fig. 21 schematically illustrates a (R)AN node 5 based on O-RAN architecture to which the (R)AN node 5 aspects are applicable. 　　The (R)AN node 5 based on O-RAN architecture represents a system overview in which the (R)AN node is split into a Radio Unit (RU) 60, Distributed Unit (DU) 61 and Centralized Unit (CU) 62. In some aspects, each unit may be combined. For example, the RU 60 can be integrated / combined with the DU 61 as an integrated / combined unit, the DU 61 can be integrated / combined with the CU 62 as another integrated / combined unit. Any functionality in the description for a unit (e.g. one of RU 60, DU 61 and CU 62) can be implemented in the integrated / combined unit above. Further, CU 62 can separate into two functional units such as CU Control plane (CP) and CU User plane (UP). The CU CP has a control plane functionality in the (R)AN node 5. The CU UP has a user plane functionality in the (R)AN node 5. Each CU CP is connected to the CU UP via an appropriate interface (such as the so-called "E1" interface and / or the like).

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

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

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

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

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

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

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

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

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

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

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

[0474] The DU in this disclosure may have same or similar component(s) to the DU 61.

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

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

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

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

[0479] <AMF> 　　Fig. 25 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).

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

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

[0482] <SMF> 　　Fig. 26 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).

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

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

[0485] <UPF> 　　Fig. 27 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).

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

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

[0488] <PCF> 　　Fig. 28 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).

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

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

[0491] <NWDAF> 　　Fig. 29 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).

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

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

[0494] <UDM> 　　Fig. 30 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).

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

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

[0497] <AUSF> 　　Fig. 31 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).

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

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

[0500] <AAnF> 　　Fig. 32 is a block diagram illustrating the main components of the AAnF 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 AAnF 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 AAnF 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).

[0501] The AAnF 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).

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

[0503] <NRF> 　　Fig. 33 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).

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

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

[0506] <NEF> 　　Fig. 34 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).

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

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

[0509] <UDR> 　　Fig. 35 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).

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

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

[0512] <OAM> 　　Fig. 36 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).

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

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

[0515] <AF> 　　Fig. 37 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).

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

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

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

[0519] <6.3.6　　N3IWF selection> <6.3.6.1　　General> 　　When the UE supports connectivity with N3IWF but does not support connectivity with ePDG, as specified in TS 23.402

[0043] , the UE shall perform the procedure in clause 6.3.6.2 for selecting an N3IWF.

[0520] When the UE supports connectivity with N3IWF, as well as with ePDG, as specified in TS 23.402

[0043] , the UE shall perform the procedure in clause 6.3.6.3 for selecting either an N3IWF or an ePDG, i.e. for selecting a non-3GPP access node.

[0521] In both cases above the UE can be configured by the HPLMN with the same information that includes: 1)　　ePDG identifier configuration: It contains the FQDN or IP address of the ePDG in the HPLMN, as specified in clause 4.5.4.3 of TS 23.402

[0043] . This is used only when the UE supports connectivity with ePDG and attempts to select an ePDG. It is ignored in all other cases. 2)　　N3IWF identifier configuration: It contains the FQDN or IP address of the N3IWF in the HPLMN. 3)　　Extended Home N3IWF identifier configuration: It contains one or multiple tuples of FQDN / IP address of the N3IWF in the HPLMN and the S-NSSAIs supported by this N3IWF. 4)　　Non-3GPP access node selection information: It contains a prioritized list of PLMNs and for each PLMN it includes (i) a "Preference" parameter which indicates if ePDG or N3IWF is preferred in this PLMN and (ii) an FQDN parameter which indicates if the Tracking / Location Area Identity FQDN or the Operator Identifier FQDN (as specified in clause 4.5.4.4 of TS 23.402

[0043] ) should be used when discovering the address of an ePDG or N3IWF in this PLMN. The list of PLMNs shall include the HPLMN and shall include an "any PLMN" entry, which matches any PLMN the UE is connected to except the HPLMN. 5)　　Slice-specific N3IWF prefix configuration: It contains one or multiple tuples consisting of: -　　List of supported S-NSSAIs; -　　Prefix for the Prefixed N3IWF OI or TA FQDNs. NOTE 1:　　Extended Home N3IWF identifier configuration and Slice-specific N3IWF prefix configuration are assumed to be provided to the UE as part of ANDSP. 6)　　the indirect network sharing information: It contains a parameter which indicates what action the UE supporting indirect network sharing procedure shall perform when the UE is registered over 3GPP access in a indirect network sharing case and the UE gets trigger to register over non-3GPP access. The UE supporting indirect network sharing performs one of the actions below depending on the value of the indirect network sharing information: -　　the parameter indicates the UE to not register to non-3GPP access while the UE is registered over the 3GPP access in an indirect network sharing case. -　　the parameter indicates the UE to first performs deregiter over 3GPP access and then performs registration over non-3GPP access. -　　the parameter indicates the UE to select the N3IWF of the HPLMN as defined in sub clause 6.3.6.2 and keep registering over 3GPP access. -　　the parameter indicates the UE to select the N3IWF of the PLMN ID corresponding to the MCC and MNC of the current 5G-GUTI received over 3GPP access. The UE will set the OI of N3IWF OI FQDN as MCC and MNC of the 5G-GUTI in order to select the N3IWF. 　　- the parameter indicates the IP address of the N3IWF of the the PLMN ID corresponding to the MCC and MNC of the current 5G-GUTI received over 3GPP access.

[0522] The ePDG identifier configuration, the N3IWF identifier configuration, the Extended Home N3IWF identifier configuration and the Slice-specific N3IWF Prefix Configuration are optional parameters, while the Non-3GPP access node selection information is required and shall include at least the HPLMN and the "any PLMN" entry.

[0523] If the ePDG identifier configuration is configured in the UE, then, when the UE decides to select an ePDG in the HPLMN (according to the procedure in clause 6.3.6.3), the UE shall use the ePDG identifier configuration to find the IP address of the ePDG in the HPLMN and shall ignore the FQDN parameter of the HPLMN in the Non-3GPP access node selection information.

[0524] If the N3IWF identifier configuration or the Extended Home N3IWF identifier configuration is configured in the UE, then, when the UE decides to select an N3IWF in the HPLMN (according to the procedure in clause 6.3.6.3 for combined N3IWF / ePDG selection and the procedure in clause 6.3.6.2 for Stand-alone N3IWF selection), the UE shall use the Extended Home N3IWF identifier configuration, if available, and otherwise the N3IWF identifier configuration to find the IP address of the N3IWF in the HPLMN and shall ignore the FQDN parameter of the HPLMN in the Non-3GPP access node selection information.

[0525] The HPLMN's PCF takes the UE's subscribed S-NSSAIs into account when providing Extended Home N3IWF identifier configuration and / or Slice-specific N3IWF Prefix Configuration to the UE.

[0526] If a UE does not support the Extended Home N3IWF identifier configuration and the Slice-specific N3IWF Prefix Configuration, then the HPLMN provides to the UE the Non-3GPP access node selection information and the N3IWF identifier configuration by taking into account the UE's subscribed S-NSSAIs. NOTE 2:　　If the HPLMN deploys multiple N3IWFs with different TAs which support different S-NSSAIs, then the HPLMN can configure a UE with N3IWF identifier configuration so that the UE selects an N3IWF that supports the UE's subscribed S-NSSAIs.

[0527] The UE can be configured by the VPLMN with the following information applicable for the V-PLMN:

[0528] Slice-specific N3IWF prefix configuration: It contains one or multiple tuples consisting of: -　　List of supported S-NSSAIs; -　　Prefix for the Prefixed N3IWF OI or TA FQDNs.

[0529] To enable the V-PCF to provide the UE with Slice-specific N3IWF prefix configuration, the AMF provides the V-PCF with the Configured NSSAI for the serving PLMN during the UE Policy Association Establishment / Modification procedure. NOTE 3:　　In non-roaming cases, the UE PCF already receives the subscribed NSSAI from the UDR. Therefore, there is no need for the AMF to provide the Configured NSSAI to the PCF in the non-roaming case. NOTE 4:　　PCF (V-PCF in the roaming case) is assumed to be locally configured with information about the slices supported by the different N3IWFs in the serving PLMN.

[0530] During the registration procedure the AMF may determine if the N3IWF selected by the UE is suitable for the S-NSSAI(s) requested by the UE considering the UE subscription. If the AMF determines that a different N3IWF should be selected as described in clause 4.12.2.2 of TS 23.502 [3], the AMF: -　　may, if the UE supports slice-based N3IWF selection, triggers the UE Policy Association Establishment or UE Policy Association Update procedure to provide the UE with updated N3IWF selection information; when the AMF is informed by the PCF that the update of UE policy information on the UE is completed as described in clause 4.12.2.2.2 of TS 23.502 [3], the AMF releases UE Policy Association if the UE is not registered over 3GPP access before proceeding to the Registration Reject over untrusted non-3GPP access; -　　shall send a Registration Reject message to the UE. The AMF may include target N3IWF information (FQDN and / or IP address) in the Registration Reject so that the UE can, if supported by the UE, use the target N3IWF information to select the N3IWF to register to 5GC if the UE wishes to send the same Requested NSSAI as during the previous Registration Request. The target N3IWF information only applies to the one N3IWF selection performed by the UE just after receiving the Registration Reject.

[0531] The AMF may determine the N3IWF based on the list of supported TAs and the corresponding list of supported slices for each TA obtained as defined in clause 5.15.8. NOTE 5:　　The operator is assumed to ensure that UEs that do not support slice-based N3IWF selection always select an N3IWF that supports at least one slice requested by the UE. This is to avoid unnecessary and potentially repetitive rejections of those UEs. To ensure this, the operator is assumed to provide identifiers of N3IWFs that only support a subset of the slices configured in the network only to UEs that support slice-based N3IWF selection.

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

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

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

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

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

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

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

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

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

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

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

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

[0544] <Supplementary notes> 　　The whole or part of the example Aspects disclosed above can be described as, but not limited to, the following supplementary notes. (1st supplementary notes) 　　(Supplementary note 1) 　　A method of a user equipment (UE) comprising: 　　communicating with a communication apparatus; and 　　determining that the UE is registered over 3GPP access through a Hosting operator network using an Indirect network sharing which uses at least one of the 3GPP access and non-3GPP access in the Hosting operator network and a Participating operator network. 　　(Supplementary note 2) 　　The method according to supplementary note 1, further comprising: 　　performing a registration procedure to the Hosting operator network; 　　wherein the determining that the UE is registered over the 3GPP access through the Hosting operator network using the Indirect network sharing includes: 　　receiving system information; 　　performing first checking that Mobile Country Code (MCC) in the system information matches with MCC of Subscription Permanent Identifier (SUPI) in Universal Subscriber Identity Module (USIM) for the UE; 　　performing second checking that MCC of 5G Globally Unique Temporary Identifier (5G-GUTI) and Mobile Network Code (MNC) of the 5G-GUTI matches with the MCC of the SUPI and MNC of the SUPI, 　　wherein the 5G-GUTI is assigned in the registration procedure; 　　performing third checking that the MCC of the SUPI and MNC of the SUPI are broadcasted in the system information; and 　　determining that the UE is registered over the 3GPP access through the Hosting operator network using the Indirect network sharing in a case where the UE performs the first checking, the second checking and the third checking. 　　(Supplementary note 3) 　　The method according to supplementary note 1, further comprising: 　　wherein the determining that the UE is registered over the 3GPP access through the Hosting operator network using the Indirect network sharing includes: 　　receiving an identity related to the Hosting operator network and an identity related to the Participating operator network; 　　performing a registration procedure to the Hosting operator network after receiving the identity related to the Hosting operator network and the identity related to the Participating operator network, 　　wherein 5G Globally Unique Temporary Identifier (5G-GUTI) is assigned in the registration procedure; and 　　determining that the UE is registered over the 3GPP access through the Hosting operator network using the Indirect network sharing after performing the registration procedure. 　　(Supplementary note 4) The method according to any one of supplementary notes 1 to 3, further comprising: 　　establishing a connection for non-3GPP access in a case where the UE determines that the UE is registered over the 3GPP access through the Hosting operator network using the Indirect network sharing; 　　finding Non-3GPP InterWorking Function (N3IWF) in the Hosting operator network; and 　　performing a registration procedure over the non-3GPP access via the N3IWF. 　　(Supplementary note 5) 　　The method according to any one of supplementary notes 1 to 3, further comprising: 　　establishing a connection for non-3GPP access in a case where the UE determines that the UE is registered over the 3GPP access through the Hosting operator network using the Indirect network sharing; 　　finding Non-3GPP InterWorking Function (N3IWF) in the Participating operator network; 　　performing a registration procedure over the non-3GPP access via the N3IWF; and 　　performing a deregistration procedure for the 3GPP access. 　　(Supplementary note 6) 　　The method according to supplementary note 5, further comprising: 　　wherein the performing the registration procedure over the non-3GPP access via the N3IWF includes: 　　sending a registration request message via the N3IWF to an Access and Mobility Management Function (AMF) in the Participating operator network, 　　wherein the registration request message includes information indicating that the UE supports Indirect network sharing using non-3GPP access; 　　receiving a registration accept message, 　　wherein the registration accept message includes information indicating that the UE is requested to perform the deregistration procedure, 　　wherein the performing the deregistration procedure for the 3GPP access includes performing the deregistration procedure based on the information indicating that the UE is requested to perform the deregistration procedure. 　　(Supplementary note 7) 　　The method according to supplementary note 2 or 3, further comprising: 　　establishing a connection for non-3GPP access in a case where the UE determines that the UE is registered over the 3GPP access through the Hosting operator network using the Indirect network sharing; 　　finding Non-3GPP InterWorking Function (N3IWF) in the Participating operator network; 　　performing a registration procedure over the non-3GPP access via the N3IWF; and 　　keeping the 5G-GUTI which is assigned in the registration procedure to the Hosting operator network over the 3GPP access and a 5G-GUTI which is assigned in the registration procedure over the non-3GPP access via the N3IWF. 　　(Supplementary note 8) 　　The method according to any one of supplementary notes 1 to 3, further comprising: 　　establishing a connection for non-3GPP access in a case where the UE determines that the UE is registered over the 3GPP access through the Hosting operator network using the Indirect network sharing; 　　finding Non-3GPP InterWorking Function (N3IWF) in the Participating operator network; 　　performing a registration procedure over the non-3GPP access via the N3IWF; and 　　receiving a registration reject message, 　　wherein the registration reject message including information indicating the registration procedure over the non-3GPP access via the N3IWF in not acceptable; and 　　performing one of: 　　　　accepting the registration reject message; and 　　　　performing a deregistration procedure for the 3GPP access and performing another registration procedure over the non-3GPP access via the N3IWF after the deregistration procedure for the 3GPP access is successful. 　　(Supplementary note 9) 　　The method according to any one of supplementary notes 1 to 3, further comprising: 　　establishing a connection for non-3GPP access in a case where the UE determines that the UE is registered over the 3GPP access through the Hosting operator network using the Indirect network sharing; 　　finding Non-3GPP InterWorking Function (N3IWF) in a Participating operator network; 　　performing a registration procedure over the non-3GPP access via the N3IWF; and 　　performing a registration procedure over the non-3GPP access in the Hosting operator network. 　　(Supplementary note 10) 　　The method according to any one of supplementary notes 1 to 3, further comprising: 　　not performing a registration procedure over the non-3GPP access via Non-3GPP InterWorking Function (N3IWF) in the Participating operator network in a case where the UE determines that the UE is registered over the 3GPP access through the Hosting operator network using the Indirect network sharing. 　　(Supplementary note 11) 　　A method of a user equipment (UE) comprising: 　　sending a registration request message, 　　wherein the registration request message includes information indicating that the UE supports Indirect network sharing using non-3GPP access; 　　receiving a registration accept message, 　　wherein the registration accept message includes information indicating that the UE is registered through a Hosting operator network using an Indirect network sharing which uses 3GPP access; and 　　determining that the UE is registered over the 3GPP access through the Hosting operator network using the Indirect network sharing which uses the 3GPP access in a case where the UE receives the registration accept message. 　　(Supplementary note 12) 　　The method according to supplementary note 11, 　　wherein the registration accept message includes information for a registration procedure for the non-3GPP access in the Hosting operator network using the Indirect network sharing. 　　(Supplementary note 13) 　　The method according to supplementary note 12, further comprising: 　　selecting Non-3GPP InterWorking Function (N3IWF) in the Hosting operator network based on the information for the registration procedure for the non-3GPP access in the Hosting operator network using the Indirect network sharing; and 　　performing a registration procedure over the non-3GPP access via the N3IWF. 　　(Supplementary note 14) 　　The method according to any one of supplementary notes 1 to 3, 11 or 12, further comprising: 　　establishing a connection for the non-3GPP access in a case where the UE determines that the UE is registered over the 3GPP access through the Hosting operator network using the Indirect network sharing; 　　finding Non-3GPP InterWorking Function (N3IWF) in the Hosting operator network; and 　　performing a registration procedure over the non-3GPP access via the N3IWF. 　　(Supplementary note 15) 　　A method of a communication apparatus in a Hosting operator network comprising: 　　receiving a registration request message from a user equipment (UE), 　　wherein the registration request message includes information indicating that the UE supports an Indirect network sharing using at least one of 3GPP access and non-3GPP access; 　　sending information indicating that a user equipment (UE) is accessing from the Hosting operator network using an Indirect network sharing which uses 3GPP access; 　　receiving at least one of information for a registration procedure for the non-3GPP access in the Hosting operator network using the Indirect network sharing using the non-3GPP access and information indicating Public Land Mobile Network (PLMN) that the UE is allowed to access as the Hosting operator network; and 　　sending a registration accept message, 　　wherein the registration accept message includes information indicating that the UE is registered through the Hosting operator network using the Indirect network sharing which uses 3GPP access and the information for a registration procedure for the non-3GPP access in the Hosting operator network using the Indirect network sharing using the non-3GPP access. 　　(Supplementary note 16) 　　The method according to supplementary note 15, 　　wherein the communication apparatus is an Access and Mobility Management Function (AMF). 　　(Supplementary note 17) 　　A method of a communication apparatus in a Participating operator network comprising: 　　receiving a registration request message from a user equipment (UE), 　　wherein the UE is registered over 3GPP access through a Hosting operator network using an Indirect network sharing using at least one of the 3GPP access and non-3GPP access, and 　　wherein the registration request message includes information indicating that the UE supports the Indirect network sharing; 　　sending information indicating that the UE is accessing using the Indirect network sharing; 　　receiving information indicating that the UE is requested to perform a deregistration procedure for the 3GPP access; and 　　sending a registration accept message, 　　wherein the registration accept message includes the information indicating that the UE is requested to perform the deregistration procedure for the 3GPP access. 　　(Supplementary note 18) 　　The method according to supplementary note 17, 　　wherein the communication apparatus is an Access and Mobility Management Function (AMF). 　　(Supplementary note 19) 　　A method of a communication apparatus in a Participating operator network comprising: 　　receiving a registration request message from a user equipment (UE), 　　wherein the UE is registered over 3GPP access through a Hosting operator network using an Indirect network sharing using at least one of the 3GPP access and non-3GPP access, and 　　wherein the registration request message includes information indicating that the UE supports the Indirect network sharing; 　　sending information indicating that the UE is accessing using the Indirect network sharing; 　　receiving information to perform a deregistration procedure for the 3GPP access; and 　　performing the deregistration procedure. 　　(Supplementary note 20) 　　The method according to supplementary note 19, 　　wherein the communication apparatus is an Access and Mobility Management Function (AMF). 　　(Supplementary note 21) 　　A method of a communication apparatus in a Participating operator network comprising: 　　receiving a registration request message from a user equipment (UE), 　　wherein the UE is registered over 3GPP access through a Hosting operator network using an Indirect network sharing using at least one of 3GPP access and non-3GPP access, and 　　wherein the registration request message includes information indicating that the UE supports the Indirect network sharing; 　　sending information indicating that the UE is accessing using the Indirect network sharing; 　　receiving information indicating that an Access and Mobility Management Function (AMF) that the UE is registered in the Hosting operator network using the Indirect network sharing; and 　　sending the registration request message to the AMF to perform a registration procedure between the UE and the AMF, 　　wherein the registration request message is sent to the AMF directly or via Non-3GPP InterWorking Function (N3IWF) in the Participating operator network. 　　(Supplementary note 22) 　　The method according to supplementary note 21, 　　wherein the communication apparatus is another Access and Mobility Management Function (AMF). 　　(Supplementary note 23) 　　A method of a communication apparatus in a Participating operator network comprising: 　　receiving information indicating that a user equipment (UE) is accessing from a Hosting operator network using an Indirect network sharing which uses 3GPP access; and 　　sending at least one of information for a registration procedure for non-3GPP access in the Hosting operator network using an Indirect network sharing which uses the non-3GPP access and information indicating Public Land Mobile Network (PLMN) that the UE is allowed to access as the Hosting operator network. 　　(Supplementary note 24) 　　The method according to supplementary note 23, 　　wherein the communication apparatus is a Unified Data Management (UDM). 　　(Supplementary note 25) 　　A method of a communication apparatus in a Participating operator network comprising: 　　receiving information indicating that a user equipment (UE) is accessing using an Indirect network sharing using at least one of 3GPP access and non-3GPP access, 　　wherein the UE is registered over 3GPP access through a Hosting operator network using the Indirect network sharing; and 　　sending information indicating that the UE is requested to perform a deregistration procedure for the 3GPP access. 　　(Supplementary note 26) 　　The method according to supplementary note 25, 　　wherein the communication apparatus is a Unified Data Management (UDM). 　　(Supplementary note 27) 　　A method of a communication apparatus in a Participating operator network comprising: 　　receiving information indicating that a user equipment (UE) is accessing using an Indirect network sharing using at least one of 3GPP access and non-3GPP access, 　　wherein the UE is registered over 3GPP access through a Hosting operator network using the Indirect network sharing; and 　　sending information indicating that an Access and Mobility Management Function (AMF) that the UE is registered in the Hosting operator network using the Indirect network sharing. 　　(Supplementary note 28) 　　The method according to Supplementary note 27, 　　wherein the communication apparatus is a Unified Data Management (UDM). 　　(Supplementary note 29) 　　A user equipment (UE) comprising: 　　means for communicating with a communication apparatus; and 　　means for determining that the UE is registered over 3GPP access through a Hosting operator network using an Indirect network sharing which uses at least one of the 3GPP access and non-3GPP access in the Hosting operator network and a Participating operator network. 　　(Supplementary note 30) 　　The UE according to supplementary note 29, further comprising: 　　means for performing a registration procedure to the Hosting operator network; 　　means for receiving system information; 　　means for performing first checking that Mobile Country Code (MCC) in the system information matches with MCC of Subscription Permanent Identifier (SUPI) in Universal Subscriber Identity Module (USIM) for the UE; 　　means for performing second checking that MCC of 5G Globally Unique Temporary Identifier (5G-GUTI) and Mobile Network Code (MNC) of the 5G-GUTI matches with the MCC of the SUPI and MNC of the SUPI, 　　wherein the 5G-GUTI is assigned in the registration procedure; 　　means for performing third checking that the MCC of the SUPI and MNC of the SUPI are broadcasted in the system information; and 　　wherein the means for determining determines that the UE is registered over the 3GPP access through the Hosting operator network using the Indirect network sharing in a case where the UE performs the first checking, the second checking and the third checking. 　　(Supplementary note 31) 　　The UE according to supplementary note 29, further comprising: 　　means for receiving an identity related to the Hosting operator network and an identity related to the Participating operator network; 　　means for performing a registration procedure to the Hosting operator network after receiving the identity related to the Hosting operator network and the identity related to the Participating operator network, 　　wherein 5G Globally Unique Temporary Identifier (5G-GUTI) is assigned in the registration procedure; and 　　wherein the means for determining determines that the UE is registered over the 3GPP access through the Hosting operator network using the Indirect network sharing after performing the registration procedure. 　　(Supplementary note 32) 　　The UE according to any one of supplementary notes 29 to 31, further comprising: 　　means for establishing a connection for non-3GPP access in a case where the UE determines that the UE is registered over the 3GPP access through the Hosting operator network using the Indirect network sharing; 　　means for finding Non-3GPP InterWorking Function (N3IWF) in the Hosting operator network; and 　　means for performing a registration procedure over the non-3GPP access via the N3IWF. 　　(Supplementary note 33) 　　The UE according to any one of supplementary notes 29 to 31, further comprising: 　　means for establishing a connection for non-3GPP access in a case where the UE determines that the UE is registered over the 3GPP access through the Hosting operator network using the Indirect network sharing; 　　means for finding Non-3GPP InterWorking Function (N3IWF) in the Participating operator network; 　　means for performing a registration procedure over the non-3GPP access via the N3IWF; and 　　means for performing a deregistration procedure for the 3GPP access. 　　(Supplementary note 34) 　　The UE according to supplementary note 33, further comprising: 　　wherein the means for performing the registration procedure over the non-3GPP access via the N3IWF: 　　sends a registration request message via the N3IWF to an Access and Mobility Management Function (AMF) in the Participating operator network, 　　wherein the registration request message includes information indicating that the UE supports Indirect network sharing using non-3GPP access; 　　receives a registration accept message, 　　wherein the registration accept message includes information indicating that the UE is requested to perform the deregistration procedure, 　　wherein the means for performing the deregistration procedure for the 3GPP access performs the deregistration procedure based on the information indicating that the UE is requested to perform the deregistration procedure. 　　(Supplementary note 35) 　　The UE according to supplementary note 30 or 31, further comprising: 　　means for establishing a connection for non-3GPP access in a case where the UE determines that the UE is registered over the 3GPP access through the Hosting operator network using the Indirect network sharing; 　　means for finding Non-3GPP InterWorking Function (N3IWF) in the Participating operator network; 　　means for performing a registration procedure over the non-3GPP access via the N3IWF; and 　　means for keeping the 5G-GUTI which is assigned in the registration procedure to the Hosting operator network over the 3GPP access and a 5G-GUTI which is assigned in the registration procedure over the non-3GPP access via the N3IWF. 　　(Supplementary note 36) 　　The UE according to any one of supplementary notes 29 to 31, further comprising: 　　means for establishing a connection for non-3GPP access in a case where the UE determines that the UE is registered over the 3GPP access through the Hosting operator network using the Indirect network sharing; 　　means for finding Non-3GPP InterWorking Function (N3IWF) in the Participating operator network; 　　means for performing a registration procedure over the non-3GPP access via the N3IWF; and 　　means for receiving a registration reject message, 　　wherein the registration reject message including information indicating the registration procedure over the non-3GPP access via the N3IWF in not acceptable; and 　　means for performing one of: 　　　　accepting the registration reject message; and 　　　　performing a deregistration procedure for the 3GPP access and performing another registration procedure over the non-3GPP access via the N3IWF after the deregistration procedure for the 3GPP access is successful. 　　(Supplementary note 37) 　　The UE according to any one of supplementary notes 29 to 31, further comprising: 　　means for establishing a connection for non-3GPP access in a case where the UE determines that the UE is registered over the 3GPP access through the Hosting operator network using the Indirect network sharing; 　　means for finding Non-3GPP InterWorking Function (N3IWF) in a Participating operator network; 　　means for performing a registration procedure over the non-3GPP access via the N3IWF; and 　　means for performing a registration procedure over the non-3GPP access in the Hosting operator network. 　　(Supplementary note 38) 　　The UE according to any one of supplementary notes 29 to 31, further comprising: 　　means for not performing a registration procedure over the non-3GPP access via Non-3GPP InterWorking Function (N3IWF) in the Participating operator network in a case where the UE determines that the UE is registered over the 3GPP access through the Hosting operator network using the Indirect network sharing. 　　(Supplementary note 39) 　　A user equipment (UE) comprising: 　　means for sending a registration request message, 　　wherein the registration request message includes information indicating that the UE supports Indirect network sharing using non-3GPP access; 　　means for receiving a registration accept message, 　　wherein the registration accept message includes information indicating that the UE is registered through a Hosting operator network using an Indirect network sharing which uses 3GPP access; and 　　means for determining that the UE is registered over the 3GPP access through the Hosting operator network using the Indirect network sharing which uses the 3GPP access in a case where the UE receives the registration accept message. 　　(Supplementary note 40) 　　The UE according to supplementary note 39, 　　wherein the registration accept message includes information for a registration procedure for the non-3GPP access in the Hosting operator network using the Indirect network sharing. 　　(Supplementary note 41) 　　The UE according to supplementary note 40, further comprising: 　　means for selecting Non-3GPP InterWorking Function (N3IWF) in the Hosting operator network based on the information for the registration procedure for the non-3GPP access in the Hosting operator network using the Indirect network sharing; and 　　means for performing a registration procedure over the non-3GPP access via the N3IWF. 　　(Supplementary note 42) 　　The UE according to any one of supplementary notes 29 to 31, 39 or 40, further comprising: 　　means for establishing a connection for the non-3GPP access in a case where the UE determines that the UE is registered over the 3GPP access through the Hosting operator network using the Indirect network sharing; 　　means for finding Non-3GPP InterWorking Function (N3IWF) in the Hosting operator network; and 　　means for performing a registration procedure over the non-3GPP access via the N3IWF. 　　(Supplementary note 43) 　　A communication apparatus in a Hosting operator network comprising: 　　means for receiving a registration request message from a user equipment (UE), 　　wherein the registration request message includes information indicating that the UE supports an Indirect network sharing using at least one of 3GPP access and non-3GPP access; 　　means for sending information indicating that a user equipment (UE) is accessing from the Hosting operator network using an Indirect network sharing which uses 3GPP access; 　　means for receiving at least one of information for a registration procedure for the non-3GPP access in the Hosting operator network using the Indirect network sharing using the non-3GPP access and information indicating Public Land Mobile Network (PLMN) that the UE is allowed to access as the Hosting operator network; and 　　means for sending a registration accept message, 　　wherein the registration accept message includes information indicating that the UE is registered through the Hosting operator network using the Indirect network sharing which uses 3GPP access and the information for a registration procedure for the non-3GPP access in the Hosting operator network using the Indirect network sharing using the non-3GPP access. 　　(Supplementary note 44) 　　The communication apparatus according to supplementary note 43, 　　wherein the communication apparatus is an Access and Mobility Management Function (AMF). 　　(Supplementary note 45) 　　A communication apparatus in a Participating operator network comprising: 　　means for receiving a registration request message from a user equipment (UE), 　　wherein the UE is registered over 3GPP access through a Hosting operator network using an Indirect network sharing using at least one of the 3GPP access and non-3GPP access, and 　　wherein the registration request message includes information indicating that the UE supports the Indirect network sharing; 　　means for sending information indicating that the UE is accessing using the Indirect network sharing; 　　means for receiving information indicating that the UE is requested to perform a deregistration procedure for the 3GPP access; and 　　means for sending a registration accept message, 　　wherein the registration accept message includes the information indicating that the UE is requested to perform the deregistration procedure for the 3GPP access. 　　(Supplementary note 46) 　　The communication apparatus according to supplementary note 45, 　　wherein the communication apparatus is an Access and Mobility Management Function (AMF). 　　(Supplementary note 47) 　　A communication apparatus in a Participating operator network comprising: 　　means for receiving a registration request message from a user equipment (UE), 　　wherein the UE is registered over 3GPP access through a Hosting operator network using an Indirect network sharing using at least one of the 3GPP access and non-3GPP access, and 　　wherein the registration request message includes information indicating that the UE supports the Indirect network sharing; 　　means for sending information indicating that the UE is accessing using the Indirect network sharing; 　　means for receiving information to perform a deregistration procedure for the 3GPP access; and 　　means for performing the deregistration procedure. 　　(Supplementary note 48) 　　The communication apparatus according to supplementary note 47, 　　wherein the communication apparatus is an Access and Mobility Management Function (AMF). 　　(Supplementary note 49) 　　A communication apparatus in a Participating operator network comprising: 　　means for receiving a registration request message from a user equipment (UE), 　　wherein the UE is registered over 3GPP access through a Hosting operator network using an Indirect network sharing using at least one of 3GPP access and non-3GPP access, and 　　wherein the registration request message includes information indicating that the UE supports the Indirect network sharing; 　　means for sending information indicating that the UE is accessing using the Indirect network sharing; 　　means for receiving information indicating that an Access and Mobility Management Function (AMF) that the UE is registered in the Hosting operator network using the Indirect network sharing; and 　　means for sending the registration request message to the AMF to perform a registration procedure between the UE and the AMF, 　　wherein the registration request message is sent to the AMF directly or via Non-3GPP InterWorking Function (N3IWF) in the Participating operator network. 　　(Supplementary note 50) 　　The communication apparatus according to supplementary note 49, 　　wherein the communication apparatus is another Access and Mobility Management Function (AMF). 　　(Supplementary note 51) 　　A communication apparatus in a Participating operator network comprising: 　　means for receiving information indicating that a user equipment (UE) is accessing from a Hosting operator network using an Indirect network sharing which uses 3GPP access; and 　　means for sending at least one of information for a registration procedure for non-3GPP access in the Hosting operator network using an Indirect network sharing which uses the non-3GPP access and information indicating Public Land Mobile Network (PLMN) that the UE is allowed to access as the Hosting operator network. 　　(Supplementary note 52) 　　The communication apparatus according to supplementary note 51, 　　wherein the communication apparatus is a Unified Data Management (UDM). 　　(Supplementary note 53) 　　A communication apparatus in a Participating operator network comprising: 　　means for receiving information indicating that a user equipment (UE) is accessing using an Indirect network sharing using at least one of 3GPP access and non-3GPP access, 　　wherein the UE is registered over 3GPP access through a Hosting operator network using the Indirect network sharing; and 　　means for sending information indicating that the UE is requested to perform a deregistration procedure for the 3GPP access. 　　(Supplementary note 54) 　　The communication apparatus according to supplementary note 53, 　　wherein the communication apparatus is a Unified Data Management (UDM). 　　(Supplementary note 55) 　　A communication apparatus in a Participating operator network comprising: 　　means for receiving information indicating that a user equipment (UE) is accessing using an Indirect network sharing using at least one of 3GPP access and non-3GPP access, 　　wherein the UE is registered over 3GPP access through a Hosting operator network using the Indirect network sharing; and 　　means for sending information indicating that an Access and Mobility Management Function (AMF) that the UE is registered in the Hosting operator network using the Indirect network sharing. 　　(Supplementary note 56) 　　The communication apparatus according to supplementary note 55, 　　wherein the communication apparatus is a Unified Data Management (UDM). (2nd supplementary notes) 　　(Supplementary note 1) 　　A method of a user equipment (UE) comprising: 　　sending 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, 　　wherein the registration request message is sent to an Access and Mobility Management Function (AMF) in the Hosting operator network; 　　receiving a registration reject message from the AMF, 　　wherein 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; 　　performing the PLMN selection; and 　　performing a registration procedure in the Participating operator network. 　　(Supplementary note 2) 　　A method of a communication apparatus comprising: 　　receiving 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, 　　wherein the communication apparatus is in the Hosting operator network; 　　checking that an area where the UE is located is not a subject for the Indirect network sharing; and 　　sending a registration reject message to the UE, 　　wherein 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. 　　(Supplementary note 3) 　　The method according to supplementary note 2, 　　wherein the communication apparatus is an Access and Mobility Management Function (AMF). 　　(Supplementary note 4) 　　A method of a user equipment (UE) comprising: 　　sending 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, 　　wherein the message includes information related to the Participating operator network; 　　receiving another message, 　　wherein the another message includes information indicating that the UE is requested to perform Public Land Mobile Network (PLMN) selection; 　　performing the PLMN selection; and 　　performing a registration procedure in the Participating operator network. 　　(Supplementary note 5) 　　A method of a communication apparatus comprising: 　　receiving 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, and 　　wherein the message includes information related to the Participating operator network; and 　　sending another message, 　　wherein the another message includes information indicating that the UE is requested to perform Public Land Mobile Network (PLMN) selection. 　　(Supplementary note 6) 　　The method according to supplementary note 5, 　　wherein the communication apparatus is a Radio Access Network (RAN) node. 　　(Supplementary note 7) 　　A method of a user equipment (UE) comprising: 　　treating 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; and 　　performing a registration procedure in the Participating operator network in a case where the UE moves out an area of the Indirect network sharing. 　　(Supplementary note 8) 　　A method of a user equipment (UE) comprising: 　　treating 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, 　　wherein 5G Globally Unique Temporary Identifier (5G-GUTI) related to the Participating operator network is assigned to the UE; and 　　performing 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. 　　(Supplementary note 9) 　　A method of a communication apparatus in a Hosting operator network comprising: 　　communicating with a user equipment (UE); and 　　assigning 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. 　　(Supplementary note 10) 　　The method according to supplementary note 9, 　　wherein the communication apparatus is an Access and Mobility Management Function (AMF). 　　(Supplementary note 11) 　　A user equipment (UE) comprising: 　　means for sending 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, 　　wherein the registration request message is sent to an Access and Mobility Management Function (AMF) in the Hosting operator network; 　　means for receiving a registration reject message from the AMF, 　　wherein 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; 　　means for performing the PLMN selection; and 　　means for performing a registration procedure in the Participating operator network. 　　(Supplementary note 12) 　　A communication apparatus comprising: 　　means for receiving 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, 　　wherein the communication apparatus is in the Hosting operator network; 　　means for checking that an area where the UE is located is not a subject for the Indirect network sharing; and 　　means for sending a registration reject message to the UE, 　　wherein 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. 　　(Supplementary note 13) 　　The communication apparatus according to supplementary note 12, 　　wherein the communication apparatus is an Access and Mobility Management Function (AMF). 　　(Supplementary note 14) 　　A user equipment (UE) comprising: 　　means for sending 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, 　　wherein the message includes information related to the Participating operator network; 　　means for receiving another message, 　　wherein the another message includes information indicating that the UE is requested to perform Public Land Mobile Network (PLMN) selection; 　　means for performing the PLMN selection; and 　　means for performing a registration procedure in the Participating operator network. 　　(Supplementary note 15) 　　A communication apparatus comprising: 　　means for receiving 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, and 　　wherein the message includes information related to the Participating operator network; and 　　means for sending another message, 　　wherein the another message includes information indicating that the UE is requested to perform Public Land Mobile Network (PLMN) selection. 　　(Supplementary note 16) 　　The communication apparatus according to supplementary note 15, 　　wherein the communication apparatus is a Radio Access Network (RAN) node. 　　(Supplementary note 17) 　　A user equipment (UE) comprising: 　　means for treating 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; and 　　means for performing a registration procedure in the Participating operator network in a case where the UE moves out an area of the Indirect network sharing. 　　(Supplementary note 18) 　　A user equipment (UE) comprising: 　　means for treating 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, 　　wherein 5G Globally Unique Temporary Identifier (5G-GUTI) related to the Participating operator network is assigned to the UE; and 　　means for performing 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. 　　(Supplementary note 19) 　　A communication apparatus in a Hosting operator network comprising: 　　means for communicating with a user equipment (UE); and 　　means for assigning 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. 　　(Supplementary note 20) 　　The communication apparatus according to supplementary note 19, 　　wherein the communication apparatus is an Access and Mobility Management Function (AMF).

[0545] This application is based upon and claims the benefit of priority from Indian Patent Application No. 202411081591, filed on October 25, 2024, the disclosure of which is incorporated herein in its entirety by reference.

[0546] 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 4001　　N3IWF 4002　　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　　ANTENNA 413　　NETWORK INTERFACE 414　　CONTROLLER 4154　　MEMORY 4151　　OPERATING SYSTEM 4152　　COMMUNICATIONS CONTROL MODULE 41521　　TRANSCEIVER CONTROL MODULE 5　　RADIO ACCESS NETWORK (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　　ACCESS AND MOBILITY MANAGEMENT FUNCTION (AMF) 701　　TRANSCEIVER CIRCUIT 702　　NETWORK INTERFACE 703　　CONTROLLER 704　　MEMORY 7041　　OPERATING SYSTEM 7042　　COMMUNICATIONS CONTROL MODULE 70421　　TRANSCEIVER CONTROL MODULE 71　　SESSION MANAGEMENT FUNCTION (SMF) 7101　　SMF 7102　　SMF 711　　TRANSCEIVER CIRCUIT 712　　NETWORK INTERFACE 713　　CONTROLLER 714　　MEMORY 7141　　OPERATING SYSTEM 7142　　COMMUNICATIONS CONTROL MODULE 71421　　TRANSCEIVER CONTROL MODULE 72　　USER PLANE FUNCTION (UPF) 7201　　UPF 7202　　UPF 721　　TRANSCEIVER CIRCUIT 722　　NETWORK INTERFACE 723　　CONTROLLER 724　　MEMORY 7241　　OPERATING SYSTEM 7242　　COMMUNICATIONS CONTROL MODULE 72421　　TRANSCEIVER CONTROL MODULE 73　　POLICY CONTROL FUNCTION (PCF) 7301　　V-PCF 7302　　H-PCF 731　　TRANSCEIVER CIRCUIT 732　　NETWORK INTERFACE 733　　CONTROLLER 734　　MEMORY 7341　　OPERATING SYSTEM 7342　　COMMUNICATIONS CONTROL MODULE 73421　　TRANSCEIVER CONTROL MODULE 74　　NETWORK DATA ANALYTICS FUNCTION (NWDAF) 741　　TRANSCEIVER CIRCUIT 742　　NETWORK INTERFACE 743　　CONTROLLER 744　　MEMORY 7441　　OPERATING SYSTEM 7442　　COMMUNICATIONS CONTROL MODULE 74421　　TRANSCEIVER CONTROL MODULE 75　　UNIFIED DATA MANAGEMENT (UDM) 751　　TRANSCEIVER CIRCUIT 752　　NETWORK INTERFACE 753　　CONTROLLER 754　　MEMORY 7541　　OPERATING SYSTEM 7542　　COMMUNICATIONS CONTROL MODULE 75421　　TRANSCEIVER CONTROL MODULE 76　　AUTHENTICATION SERVER FUNCTION (AUSF) 761　　TRANSCEIVER CIRCUIT 762　　NETWORK INTERFACE 763　　CONTROLLER 764　　MEMORY 7641　　OPERATING SYSTEM 7642　　COMMUNICATIONS CONTROL MODULE 76421　　TRANSCEIVER CONTROL MODULE 77　　AKMA ANCHOR FUNCTION (AAnF) 771　　TRANSCEIVER CIRCUIT 772　　NETWORK INTERFACE 773　　CONTROLLER 774　　MEMORY 7741　　OPERATING SYSTEM 7742　　COMMUNICATIONS CONTROL MODULE 77421　　TRANSCEIVER CONTROL MODULE 78　　NETWORK REPOSITORY FUNCTION (NRF) 781　　TRANSCEIVER CIRCUIT 782　　NETWORK INTERFACE 783　　CONTROLLER 784　　MEMORY 7841　　OPERATING SYSTEM 7842　　COMMUNICATIONS CONTROL MODULE 78421　　TRANSCEIVER CONTROL MODULE 79　　NETWORK EXPOSURE FUNCTION (NEF) 791　　TRANSCEIVER CIRCUIT 792　　NETWORK INTERFACE 793　　CONTROLLER 794　　MEMORY 7941　　OPERATING SYSTEM 7942　　COMMUNICATIONS CONTROL MODULE 79421　　TRANSCEIVER CONTROL MODULE 7A　　UNIFIED DATA REPOSITORY (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

1. A method of a user equipment (UE) comprising: 　　sending 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, 　　wherein the registration request message is sent to an Access and Mobility Management Function (AMF) in the Hosting operator network; 　　receiving a registration reject message from the AMF, 　　wherein 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; 　　performing the PLMN selection; and 　　performing a registration procedure in the Participating operator network.

2. A method of a communication apparatus comprising: 　　receiving 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, 　　wherein the communication apparatus is in the Hosting operator network; 　　checking that an area where the UE is located is not a subject for the Indirect network sharing; and 　　sending a registration reject message to the UE, 　　wherein 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.

3. The method according to claim 2, 　　wherein the communication apparatus is an Access and Mobility Management Function (AMF).

4. A method of a user equipment (UE) comprising: 　　sending 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, 　　wherein the message includes information related to the Participating operator network; 　　receiving another message, 　　wherein the another message includes information indicating that the UE is requested to perform Public Land Mobile Network (PLMN) selection; 　　performing the PLMN selection; and 　　performing a registration procedure in the Participating operator network.

5. A method of a communication apparatus comprising: 　　receiving 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, and 　　wherein the message includes information related to the Participating operator network; and 　　sending another message, 　　wherein the another message includes information indicating that the UE is requested to perform Public Land Mobile Network (PLMN) selection.

6. The method according to claim 5, 　　wherein the communication apparatus is a Radio Access Network (RAN) node.

7. A method of a user equipment (UE) comprising: 　　treating 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; and 　　performing a registration procedure in the Participating operator network in a case where the UE moves out an area of the Indirect network sharing.

8. A method of a user equipment (UE) comprising: 　　treating 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, 　　wherein 5G Globally Unique Temporary Identifier (5G-GUTI) related to the Participating operator network is assigned to the UE; and 　　performing 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.

9. A method of a communication apparatus in a Hosting operator network comprising: 　　communicating with a user equipment (UE); and 　　assigning 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.

10. The method according to claim 9, 　　wherein the communication apparatus is an Access and Mobility Management Function (AMF).

11. A user equipment (UE) comprising: 　　means for sending 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, 　　wherein the registration request message is sent to an Access and Mobility Management Function (AMF) in the Hosting operator network; 　　means for receiving a registration reject message from the AMF, 　　wherein 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; 　　means for performing the PLMN selection; and 　　means for performing a registration procedure in the Participating operator network.

12. A communication apparatus comprising: 　　means for receiving 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, 　　wherein the communication apparatus is in the Hosting operator network; 　　means for checking that an area where the UE is located is not a subject for the Indirect network sharing; and 　　means for sending a registration reject message to the UE, 　　wherein 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.

13. The communication apparatus according to claim 12, 　　wherein the communication apparatus is an Access and Mobility Management Function (AMF).

14. A user equipment (UE) comprising: 　　means for sending 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, 　　wherein the message includes information related to the Participating operator network; 　　means for receiving another message, 　　wherein the another message includes information indicating that the UE is requested to perform Public Land Mobile Network (PLMN) selection; 　　means for performing the PLMN selection; and 　　means for performing a registration procedure in the Participating operator network.

15. A communication apparatus comprising: 　　means for receiving 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, and 　　wherein the message includes information related to the Participating operator network; and 　　means for sending another message, 　　wherein the another message includes information indicating that the UE is requested to perform Public Land Mobile Network (PLMN) selection.

16. The communication apparatus according to claim 15, 　　wherein the communication apparatus is a Radio Access Network (RAN) node.

17. A user equipment (UE) comprising: 　　means for treating 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; and 　　means for performing a registration procedure in the Participating operator network in a case where the UE moves out an area of the Indirect network sharing.

18. A user equipment (UE) comprising: 　　means for treating 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, 　　wherein 5G Globally Unique Temporary Identifier (5G-GUTI) related to the Participating operator network is assigned to the UE; and 　　means for performing 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.

19. A communication apparatus in a Hosting operator network comprising: 　　means for communicating with a user equipment (UE); and 　　means for assigning 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.

20. The communication apparatus according to claim 19, 　　wherein the communication apparatus is an Access and Mobility Management Function (AMF).

Images