Method of first communication apparatus, method of user equipment (UE), first communication apparatus and ue

Abstract

An aspect of this disclosure includes a method of a first communication apparatus. The method includes receiving a Registration Request message from a User Equipment (UE). The Registration Request message includes Requested Network Slice Selection Assistance Information (NSSAI). The method includes sending the Requested NSSAI to a second communication apparatus. The method includes receiving Allowed NSSAI from the second communication apparatus. The Allowed NSSAI includes Single Network Slice Selection Assistance Information (S-NSSAI). The method includes sending a Registration Accept message to the UE. The Registration Accept message includes Partially Allowed NSSAI. The Partially Allowed NSSAI includes the S-NSSAI.

Description

METHOD OF FIRST COMMUNICATION APPARATUS, METHOD OF USER EQUIPMENT (UE), FIRST COMMUNICATION APPARATUS AND UE　　The present disclosure relates to a method of a first communication apparatus, a method of a user equipment (UE), a first communication apparatus and UE and so on.　　According to the 3GPP SA2 contribution S2-2303160 (NPL 2), 3GPP SA2 group concludes that an AMF selects the Partially Allowed NSSAI and S-NSSAIs rejected partially in the RA for the UE based on a local policy in the AMF.NPL 1: 3GPP TR 21.905: "Vocabulary for 3GPP Specifications". V17.1.0 (2021-12)NPL 2: S2-2303160: https: / / www.3gpp.org / ftp / tsg_sa / WG2_Arch / TSGS2_155_Athens_2023-02 / Docs / S2-2303160.zipNPL 3: 3GPP TS 23.501: "System architecture for the 5G System (5GS)". V18.0.0 (2022-12)NPL 4: 3GPP TS 23.032: "Universal Geographical Area Description (GAD)". V17.2.0 (2021-12)NPL 5: RFC 5139: https: / / www.rfc-editor.org / rfc / rfc5139　　According to the network slice management mechanism in 5GC as defined in 3GPP TS 23.501 (NPL 3), the 5GC has a dedicated functional entity, Network Slice Selection Function (NSSF), for assigning S-NSSAI(s) to the UE based on the network slice(s) within the Requested NSSAI from the UE, a subscriber data of the UE, a location of the UE and other configuration data in the 5GC and an associated Operation and Maintenance (O&M) system. Based on this mechanism, mobile operators configure the network slice related data base in the NSSF.　　On the other hand, NPL 2 defines that newly introduced network slice related data, Partially Allowed NSSAI and S-NSSAIs rejected partially in the RA, which are selected based on the sole decision by the AMF based on the AMF local policy.　　However, regarding the decision by the AMF based on the AMF local policy, there are some problems.　　This disclosure includes mechanism(s) for solving at least partially the above problems.　　A method of a first communication apparatus according to a first aspect of the present disclosure includes:　　receiving a Registration Request message from a User Equipment (UE),　　wherein the Registration Request message includes Requested Network Slice Selection Assistance Information (NSSAI);　　sending the Requested NSSAI to a second communication apparatus;　　receiving Allowed NSSAI from the second communication apparatus,　　wherein the Allowed NSSAI includes Single Network Slice Selection Assistance Information (S-NSSAI); and　　sending a Registration Accept message to the UE,　　wherein the Registration Accept message includes Partially Allowed NSSAI, and　　wherein the Partially Allowed NSSAI includes the S-NSSAI.　　A method of a User Equipment (UE) according to a second aspect of the present disclosure includes:　　sending a Registration Request message to a first communication apparatus,　　wherein the Registration Request message includes Requested Network Slice Selection Assistance Information (NSSAI); and　　receiving a Registration Accept message,　　wherein the Registration Accept message includes Partially Allowed NSSAI, and　　wherein the Partially Allowed NSSAI includes Single Network Slice Selection Assistance Information (S-NSSAI),　　wherein the S-NSSAI in the Partially Allowed NSSAI is based on Allowed NSSAI sent from a second communication apparatus to the first communication apparatus, and　　wherein the Allowed NSSAI includes the S-NSSAI.　　A first communication apparatus according to a third aspect of the present disclosure includes:　　means for receiving a Registration Request message from a User Equipment (UE),　　wherein the Registration Request message includes Requested Network Slice Selection Assistance Information (NSSAI);　　means for sending the Requested NSSAI to a second communication apparatus;　　means for receiving Allowed NSSAI from the second communication apparatus,　　wherein the Allowed NSSAI includes Single Network Slice Selection Assistance Information (S-NSSAI); and　　means for sending a Registration Accept message to the UE,　　wherein the Registration Accept message includes Partially Allowed NSSAI, and　　wherein the Partially Allowed NSSAI includes the S-NSSAI.　　A User Equipment (UE) according to a fourth aspect of the present disclosure includes comprising:　　means for sending a Registration Request message to a first communication apparatus,　　wherein the Registration Request message includes Requested Network Slice Selection Assistance Information (NSSAI); and　　means for receiving a Registration Accept message,　　wherein the Registration Accept message includes Partially Allowed NSSAI, and　　wherein the Partially Allowed NSSAI includes Single Network Slice Selection Assistance Information (S-NSSAI),　　wherein the S-NSSAI in the Partially Allowed NSSAI is based on Allowed NSSAI sent from a second communication apparatus to the first communication apparatus, and　　wherein the Allowed NSSAI includes the S-NSSAI.Fig. 1 is a signaling diagram of a First example of the First Aspect.Fig. 2 is a signaling diagram of a Second example of the First Aspect.Fig. 3 is a signaling diagram of a Third example of the First Aspect.Fig. 4 is a diagram illustrating a system overview.Fig. 5 is a block diagram illustrating a UE.Fig. 6 is a block diagram illustrating an (R)AN node.Fig. 7 is a diagram illustrating System overview of (R)AN node based on O-RAN architecture.Fig. 8 is a block diagram illustrating an RU.Fig. 9 is a block diagram illustrating a DU.Fig. 10 is a block diagram illustrating a CU.Fig. 11 is a block diagram illustrating an AMF.Fig. 12 is a block diagram illustrating a PCF.Fig. 13 is a block diagram illustrating an NWDAF.Fig. 14 is a block diagram illustrating a UDM.Fig. 15 is a block diagram illustrating an NSSF.Fig. 16 is a signaling diagram of Registration with AMF re-allocation procedure.　　For the purposes of the present document, the abbreviations given in 3GPP TR 21.905 (NPL 1) and the following apply. An abbreviation defined in the present document takes precedence over the definition of the same abbreviation, if any, in NPL 1.4G-GUTI　　4G Globally Unique Temporary UE Identity5GC　　5G Core Network5GLAN　　5G Local Area Network5GS　　5G System5G-AN　　5G Access Network5G-AN PDB　　5G Access Network Packet Delay Budget5G-EIR　　5G-Equipment Identity Register5G-GUTI　　5G Globally Unique Temporary Identifier5G-BRG　　5G Broadband Residential Gateway5G-CRG　　5G Cable Residential Gateway5G GM　　5G Grand Master5G-RG　　5G Residential Gateway5G-S-TMSI　　5G S-Temporary Mobile Subscription Identifier5G VN　　5G Virtual Network5QI　　5G QoS IdentifierAF　　Application FunctionAMF　　Access and Mobility Management FunctionAMF-G　　Geographically selected Access and Mobility Management FunctionAMF-NG　　Non-Geographically selected Access and Mobility Management FunctionANDSF　　Access Network Discovery and Selection FunctionARFCN　　Absolute radio-frequency channel numberAS　　Access StratumASN　　Abstract Syntax NotationATSSS　　Access Traffic Steering, Switching, SplittingATSSS-LL　　ATSSS Low-LayerAuC　　Authentication CentreAUSF　　Authentication Server FunctionAUTN　　Authentication tokenBCCH　　Broadcast Control ChannelBMCA　　Best Master Clock AlgorithmBSF　　Binding Support FunctionCAG　　Closed Access GroupCAPIF　　Common API Framework for 3GPP northbound APIsCHF　　Charging FunctionCN PDB　　Core Network Packet Delay BudgetCP　　Control PlaneDAPS　　Dual Active Protocol StacksDL　　DownlinkDN　　Data NetworkDNAI　　DN Access IdentifierDNN　　Data Network NameDRX　　Discontinuous ReceptionDS-TT　　Device-side TSN translatorePDG　　evolved Packet Data GatewayEBI　　EPS Bearer IdentityEPS　　Evolved Packet SystemEUI　　Extended Unique IdentifierFAR　　Forwarding Action RuleFN-BRG　　Fixed Network Broadband RGFN-CRG　　Fixed Network Cable RGFN-RG　　Fixed Network RGFQDN　　Fully Qualified Domain NameGFBR　　Guaranteed Flow Bit RateGMLC　　Gateway Mobile Location CentreG-PDU　　GTP encapsulated user Plane Data UnitGPS　　Global Positioning SystemGPSI　　Generic Public Subscription IdentifierGUAMI　　Globally Unique AMF IdentifierGUTI　　Globally Unique Temporary UE IdentityHPLMN　　Home Public Land Mobile NetworkHR　　Home Routed (roaming)HSS　　Home Subscriber ServerIAB　　Integrated access and backhaulIPsec　　Internet Protocol SecurityIMEI / TAC　　IMEI Type Allocation CodeIMSI　　International Mobile Subscriber IdentityIPUPS　　Inter PLMN UP SecurityI-SMF　　Intermediate SMFI-UPF　　Intermediate UPFLADN　　Local Area Data NetworkLBO　　Local Break Out (roaming)LMF　　Location Management FunctionLoA　　Level of AutomationLPP　　LTE Positioning ProtocolLRF　　Location Retrieval FunctionMCC　　Mobile country codeMCX　　Mission Critical ServiceMDBV　　Maximum Data Burst VolumeME　　Mobile EquipmentMFBR　　Maximum Flow Bit RateMICO　　Mobile Initiated Connection OnlyMINT　　Minimization of service interruptionMITM　　Man In the MiddleMME　　Mobility Management EntityMNC　　Mobile Network CodeMOCN　　Multiple Operator Core NetworkMPS　　Multimedia Priority ServiceMPTCP　　Multi-Path TCP ProtocolMT　　Mobile TerminationN3IWF　　Non-3GPP InterWorking FunctionN3GPP　　Non-3GPP accessN5CW　　Non-5G-Capable over WLANNAI　　Network Access IdentifierNAS　　Non-Access-StratumNEF　　Network Exposure FunctionNF　　Network FunctionNGAP　　Next Generation Application ProtocolNID　　Network identifierNMEA　　National Marine Electronics AssociationNPN　　Non-Public NetworkNR　　New RadioNSAG　　Network Slice Access Stratum GroupNRF　　Network Repository FunctionNSAC　　Network Slice Admission ControlNSACF　　Network Slice Admission Control FunctionNSI ID　　Network Slice Instance IdentifierNSSAA　　Network Slice-Specific Authentication and AuthorizationNSSAAF　　Network Slice-Specific Authentication and Authorization FunctionNSSAI　　Network Slice Selection Assistance InformationNSSF　　Network Slice Selection FunctionNSSP　　Network Slice Selection PolicyNSSRG　　Network Slice Simultaneous Registration GroupNW-TT　　Network-side TSN translatorNWDAF　　Network Data Analytics FunctionPCF　　Policy Control FunctionPCO　　Protocol Configuration OptionsPCRF　　Policy and Charging Rules FunctionPDB　　Packet Delay BudgetPDR　　Packet Detection RulePDU　　Protocol Data UnitPEI　　Permanent Equipment IdentifierPER　　Packet Error RatePFD　　Packet Flow DescriptionPLMN　　Public Land Mobile NetworkPNI-NPN　　Public Network Integrated Non-Public NetworkPPD　　Paging Policy DifferentiationPPF　　Paging Proceed FlagPPI　　Paging Policy IndicatorPSA　　PDU Session AnchorPTP　　Precision Time ProtocolQFI　　QoS Flow IdentifierQoE　　Quality of ExperienceRACS　　Radio Capabilities Signalling optimisation(R)AN　　(Radio) Access NetworkRAT　　Radio Access TechnologyRG　　Residential GatewayRIM　　Remote Interference ManagementRQA　　Reflective QoS AttributeRQI　　Reflective QoS IndicationRRC　　Radio Resource ControlRSN　　Redundancy Sequence NumberRSRP　　Reference Signal Received PowerRSRQ　　Reference Signal Received QualityRVAS　　Roaming Value Added ServiceSA NR　　Standalone New RadioSBA　　Service Based ArchitectureSBI　　Service Based InterfaceSCP　　Service Communication ProxySD　　Slice DifferentiatorSEAF　　Security Anchor FunctionalitySENSE　　Signal Level Enhanced Network SelectionSEPP　　Security Edge Protection ProxySGW　　Serving GatewaySIB　　System Information BlockSINR　　Signal to Interference plus Noise RatioSMF　　Session Management FunctionSMSF　　Short Message Service FunctionSN　　Sequence NumberSN name　　Serving Network Name.SNPN　　Stand-alone Non-Public NetworkS-NSSAI　　Single Network Slice Selection Assistance InformationSOR　　Steering of RoamingSSC　　Session and Service ContinuitySSCMSP　　Session and Service Continuity Mode Selection PolicySST　　Slice / Service TypeSUCI　　Subscription Concealed IdentifierSUPI　　Subscription Permanent IdentifierSV　　Software VersionTAU　　Tracking Area UpdateTEID　　Tunnel Endpoint IdentifierTMSI　　Temporary Mobile Subscriber IdentityTNAN　　Trusted Non-3GPP Access NetworkTNAP　　Trusted Non-3GPP Access PointTNGF　　Trusted Non-3GPP Gateway FunctionTNL　　Transport Network LayerTNLA　　Transport Network Layer AssociationTSC　　Time Sensitive CommunicationTSCAI　　TSC Assistance InformationTSN　　Time Sensitive NetworkingTSN GM　　TSN Grand MasterTSP　　Traffic Steering PolicyTT　　TSN TranslatorTWIF　　Trusted WLAN Interworking FunctionUCMF　　UE radio Capability Management FunctionUDM　　Unified Data ManagementUDR　　Unified Data RepositoryUDSF　　Unstructured Data Storage FunctionUE　　User EquipmentUL　　UplinkUL CL　　Uplink ClassifierUPF　　User Plane FunctionUPSI　　UE Policy Section IdentifierURLLC　　Ultra Reliable Low Latency CommunicationURRP-AMF　　UE Reachability Request Parameter for AMFURSP　　UE Route Selection PolicyUSIM　　User Services Identity ModuleVID　　VLAN IdentifierVLAN　　Virtual Local Area NetworkVPLMN　　Visited Public Land Mobile NetworkW-5GAN　　Wireline 5G Access NetworkW-5GBAN　　Wireline BBF Access NetworkW-5GCAN　　Wireline 5G Cable Access NetworkW-AGF　　Wireline Access Gateway FunctionDefinitions　　For the purposes of the present document, the terms and definitions given in NPL 1 and the following apply. A term defined in the present document takes precedence over the definition of the same term, if any, in NPL 1.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.　　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.　　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.　　In the following specification and the claims, reference will be made to a number of terms, which may be defined to have the following meanings. The singular forms "a", "an", and "the" include plural references unless the context clearly dictates otherwise.　　As used herein, information is associated with data and knowledge, as data is meaningful information and represents the values attributed to parameters. Further knowledge signifies understanding of an abstract or concrete concept. Note that this example system is simplified to facilitate description of the disclosed subject matter and is not intended to limit the scope of this disclosure. Other devices, systems, and configurations may be used to implement the Aspects disclosed herein in addition to, or instead of, a system, and all such Aspects are contemplated as within the scope of the present disclosure.　　Each of Aspects (i.e. First Aspect, Second Aspect, Third Aspect, First example of the First Aspect, Second example of the First Aspect, Third example of the First Aspect, First example of the Second Aspect, Second example of the Second Aspect, Third example of the Second Aspect, Variant of each Aspects) and elements included in the each 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.　　Any lists described in following aspects include at least one parameter or multiple parameters.　　The Partially Allowed NSSAI may be expressed as Partially allowed NSSAI, partially allowed NSSAI, partially Allowed NSSAI, partially allowed S-NSSAI, Partially Allowed network slice, Partially Allowed S-NSSAI and so on.　　The S-NSSAIs rejected partially in the RA may be expressed as S-NSSAI rejected partially in the RA, S-NSSAIs rejected partially, S-NSSAI rejected partially, Partially rejected NSSAI, partially Rejected NSSAI, partially rejected NSSAI, Partially Rejected S-NSSAI, Rejected S-NSSAIs partially, Rejected S-NSSAI partially, Partially Rejected NSSAI, Partially Rejected network slice and so on.　　In this disclosure, network slice(s) may mean S-NSSAI(s).　　In this disclosure, S-NSSAI(s) may mean network slice(s). In this disclosure, S-NSSAI(s) may mean network slice(s) identified by the S-NSSAI(s).　　In this disclosure, network slice(s) may be identified by corresponding S-NSSAI(s).　　An example object of this disclosure is to provide a method and apparatus that can solve the above problem.　　A method of a first communication apparatus according to example aspect of this disclosure includes receiving at least one of Partially Allowed Network Slice Selection Assistance Information (NSSAI) and Rejected Single Network Slice Selection Assistance Information (S-NSSAI) partially from a second communication apparatus. The method includes sending the at least one of the Partially Allowed NSSAI and the Rejected S-NSSAI partially to a user equipment (UE).　　A method of a first communication apparatus according to example aspect of this disclosure includes receiving, from a second communication apparatus, information for determining at least one of Partially Allowed Network Slice Selection Assistance Information (NSSAI) and Rejected Single Network Slice Selection Assistance Information (S-NSSAI) partially. The method includes determining the at least one of the Partially Allowed NSSAI and the Rejected S-NSSAI partially. The method includes sending the at least one of the Partially Allowed NSSAI and the Rejected S-NSSAI partially to a user equipment (UE).　　A method of a user equipment (UE) according to example aspect of this disclosure includes sending, to a communication apparatus, information indicating that the UE is able to understand at least one of Partially Allowed Network Slice Selection Assistance Information (NSSAI) and Rejected Single Network Slice Selection Assistance Information (S-NSSAI) partially. The method includes receiving the at least one of the Partially Allowed NSSAI and the Rejected S-NSSAI partially from the communication apparatus in a case of sending the information.　　A method of a first communication apparatus according to example aspect of this disclosure includes receiving, from a second communication apparatus, information for determining at least one of Partially Allowed Network Slice Selection Assistance Information (NSSAI) and Rejected Single Network Slice Selection Assistance Information (S-NSSAI) partially. The method includes determining the at least one of the Partially Allowed NSSAI and the Rejected S-NSSAI partially. The method includes sending the at least one of the Partially Allowed NSSAI and the Rejected S-NSSAI partially to the second communication apparatus.　　A first 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 at least one of Partially Allowed Network Slice Selection Assistance Information (NSSAI) and Rejected Single Network Slice Selection Assistance Information (S-NSSAI) partially from a second communication apparatus. The at least one hardware processor is configured to send the at least one of the Partially Allowed NSSAI and the Rejected S-NSSAI partially to a user equipment (UE).　　A first 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, from a second communication apparatus, information for determining at least one of Partially Allowed Network Slice Selection Assistance Information (NSSAI) and Rejected Single Network Slice Selection Assistance Information (S-NSSAI) partially. The at least one hardware processor is configured to determine the at least one of the Partially Allowed NSSAI and the Rejected S-NSSAI partially. The at least one hardware processor is configured to send the at least one of the Partially Allowed NSSAI and the Rejected S-NSSAI partially to a user equipment (UE).　　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, to a communication apparatus, information indicating that the UE is able to understand at least one of Partially Allowed Network Slice Selection Assistance Information (NSSAI) and Rejected Single Network Slice Selection Assistance Information (S-NSSAI) partially. The at least one hardware processor is configured to receive the at least one of the Partially Allowed NSSAI and the Rejected S-NSSAI partially from the communication apparatus in a case of sending the information.　　A first 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, from a second communication apparatus, information for determining at least one of Partially Allowed Network Slice Selection Assistance Information (NSSAI) and Rejected Single Network Slice Selection Assistance Information (S-NSSAI) partially. The at least one hardware processor is configured to determine the at least one of the Partially Allowed NSSAI and the Rejected S-NSSAI partially. The at least one hardware processor is configured to send the at least one of the Partially Allowed NSSAI and the Rejected S-NSSAI partially to the second communication apparatus.　　An example aspect of this disclosure includes a method of a core network communication apparatus. The method includes communicating between core network apparatuses that controls a partial Network Slice availability in a Registration Area in a case where a network slice is available in one or more TAs of the RA in a PLMN or an SNPN. The method includes sending from a first core network apparatus to a second core network apparatus, first information indicating a Requested NSSAI that is received from a user equipment (UE) and the second core network apparatus selects second information indicating a Partially Allowed NSSAI and third information indicating S-NSSAIs rejected partially in the RA during the registration procedure.　　For example, the present disclosure relates to a core network apparatus. The core network apparatus may select the Partially Allowed NSSAI and S-NSSAIs rejected partially in the RA based on a systematic mechanism using system wide data base in the PLMN or the SNPN.　　Definition of at least one of the Partially Allowed NSSAI and the Rejected S-NSSAIs partially in the RA in NPL 2 may be applied to at least one of the Partially Allowed NSSAI and the Rejected S-NSSAIs partially in the RA in this disclosure.First Aspect　　This aspect includes mechanisms to select newly introduced network slice related data, for example Partially Allowed NSSAI and S-NSSAIs rejected partially in the RA, based on a systematic mechanism using system wide data base in the PLMN or the SNPN.First example of the First Aspect:　　According to the network slice management mechanism in 5GC as defined in NPL 3, the 5GC has a dedicated functional entity, Network Slice Selection Function (NSSF), for assigning S-NSSAI(s) to the UE based on the network slice(s) within the Requested NSSAI from the UE, a subscriber data of the UE, a location of the UE and other configuration data in the 5GC and an associated Operation and Maintenance (O&M) system. Based on this mechanism, mobile operators configure the network slice related data base in the NSSF.　　On the other hand, NPL 2 defines that newly introduced network slice related data, Partially Allowed NSSAI and S-NSSAIs rejected partially in the RA, which are selected based on the sole decision by the AMF based on the AMF local policy.　　With this condition, mobile operators, who manage network slice related data base in the NSSF, must have another data base for the Partially Allowed NSSAI and reject the S-NSSAIs partially in the RA in the AMF.　　As the result, mobile operators need to manage network slice related data, one in the NSSF and another one in the AMF.　　This makes mobile operators difficult to manage network slice related data in their network and causes additional cost for management.　　For example, this First example of the First Aspect includes flexible mechanism for managing newly introduced network slice related data, for example Partially Allowed NSSAI and S-NSSAIs rejected partially in the RA in mobile operator's network.　　Fig. 1 includes an example of selecting newly introduced network slice related data by the NSSF 76.　　The detailed processes of the First example of the First Aspect are described below with reference to Fig. 1.　　Step 1. A UE 3 sends a Registration Request message to an AMF 70 including at least one of User ID, Requested NSSAI, and Partial Network Slice Availability support indication.　　The following bullets explain each parameter in detail.　　・User ID may be a 5G-GUTI, SUCI or SUPI. For example, the User ID may be a 5G-GUTI, SUCI or SUPI for the UE 3. The User ID may be expressed as User Identity.　　・Requested NSSAI is a list of S-NSSAI(s) that the UE 3 requests to use. The definition of the Requested NSSAI in the current 3GPP standard(s) may be applied to the Requested NSSAI in this disclosure.　　・Partial Network Slice Availability support indication indicates that the UE 3 supports handling of at least one of the Partially Allowed NSSAI and the Rejected S-NSSAIs partially in the RA. For example, the Partial Network Slice Availability support indication may indicate that the UE 3 is able to know or understand at least one of the Partially Allowed NSSAI and the Rejected S-NSSAIs partially. For example, the Partial Network Slice Availability support indication may indicate that the UE 3 is able to perform process(es) related to at least one of the Partially Allowed NSSAI and the Rejected S-NSSAIs partially. The Partial Network Slice Availability support indication may indicate that the UE 3 supports at least one of the Partially Allowed NSSAI and the Rejected S-NSSAIs partially.　　Step 2. Upon reception of the Registration Request message in step 1, the AMF 70 invokes an Nudm_UECM_Registration service to a UDM 75 to register AMF 70 as the roaming node for the UE 3. The UDM 75 may be included in HPLMN.　　Step 3. After the completion of the Nudm_UECM_Registration service in step 2, the AMF 70 sends an Nudm_SDM_Get Request message to the UDM 75 including at least one of User ID and Partial Network Slice Availability support indication. See step 1 for definition of the Partial Network Slice Availability support indication and the User ID. For example, the Partial Network Slice Availability support indication and the User ID in the step 3 may be same one in the step 1.　　Step 4. Upon reception the Nudm_SDM_Get Request message, the UDM 75 finds the subscriber data for the UE 3 and sends an Nudm_SDM_Get Response message including Subscriber data for the UE 3. The Subscriber data may include the following data.　　・Service area for the S-NSSAI. It can be a geographical area in the visited PLMN or the NSPN. This information may be represented with at least one from the followings:　　　　>Universal Geographical Area Description (GAD) as defined in 3GPP TS 23.032 (NPL 4).　　　　>NMEA format as used by the GPS system.　　　　>Revised Civic Location Format for Presence Information Data Format Location Object as defined in RFC 5139 (NPL 5)　　　　>A list of TAIs in current VPLMN.　　・Restricted service area for the S-NSSAI. It can be a geographical area in the visited PLMN or the NSPN. This information may be represented as shown in the Service area for the S-NSSAI.　　In one example, the UDM 75 may include the data shown in above bullets only if the UDM 75 receives the Partial Network Slice Availability support indication from the AMF 70 in step 3.　　Step 5. After the AMF 70 obtains the Subscriber data, including a Subscribed NSSAI that is used by the AMF 70 to determine Allowed NSSAI and / or Rejected NSSAI, for the UE 3 from the UDM 75 in step 4, the AMF 70 sends an Nnssf_NSSelection_Get message to an NSSF 76 including at least one of Requested NSSAI, Partial Network Slice Availability support indication and other existing information. See step 1 for definition of the Partial Network Slice Availability support indication and the Requested NSSAI. For example, the Partial Network Slice Availability support indication and the Requested NSSAI in the step 4 may be same one in the step 1. The Nnssf_NSSelection_Get message may include TAI.　　Step 6. Upon reception of the Nnssf_NSSelection_Get message, the NSSF 76 generates at least one of the Partially Allowed NSSAI and the Rejected S-NSSAIs partially in the RA based on the input parameters, for example at least one of Requested NSSAI and TAI in the Nnssf_NSSelection_Get message. For example, the NSSF 76 may determine at least one of the Partially Allowed NSSAI and the Rejected S-NSSAI partially based on the input parameters.　　The input parameters may be expressed as information for determining at least one of the Partially Allowed NSSAI and the Rejected S-NSSAIs partially.　　The NSSF 76 may generate at least one of the Partially Allowed NSSAI and the Rejected S-NSSAIs partially in the RA only if the Nnssf_NSSelection_Get message includes the Partial Network Slice Availability support indication. The Partial Network Slice Availability support indication may indicate to the NSSF 76 that the UE 3 supports the Partially Allowed NSSAI or the Rejected S-NSSAIs partially. The NSSF 76 may generate at least one of Allowed NSSAI and Rejected NSSAI based on the input parameters, for example Requested NSSAI, TAI in Nnssf_NSSelection_Get message.　　The NSSF 76 sends an Nnssf_NSSelection_Get Response message to the AMF 70 including at least one of Allowed NSSAI, Rejected NSSAI, Partially Allowed NSSAI, and Rejected S-NSSAIs partially in the RA. For example, in a case where the NSSF 76 generates at least one of the Allowed NSSAI, the Rejected NSSAI, the Partially Allowed NSSAI, and the Rejected S-NSSAIs partially in the RA, the NSSF 76 may send the Nnssf_NSSelection_Get Response message to the AMF 70.　　The NSSF 76 may include Partially Allowed NSSAI and Rejected S-NSSAIs partially in the RA only if the Nnssf_NSSelection_Get message includes the Partial Network Slice Availability support indication.　　The Partially Allowed NSSAI may include a list of Allowed S-NSSAI(s) and each S-NSSAI in the list has associated list of TAI(s). The S-NSSAI in the Partially Allowed NSSAI may be only allowed to use in the TAI(s) associated to the S-NSSAI.　　For example, S-NSSAI(s) in the Partially Allowed NSSAI may be associated with TAI(s) or TA.　　For example, S-NSSAI(s) in the Partially Allowed NSSAI may indicate S-NSSAI(s) which is allowed or available in associated or specific TAI(s) or TA(s). For example, the Partially Allowed NSSAI includes S-NSSAI 1 which is allowed or available in TAI 1 (or TA 1).For example, the Partially Allowed NSSAI includes S-NSSAI(s) which is allowed or available in associated or specific TAI(s) or TA(s).　　For example, the Partially Allowed NSSAI may be associated with TAI(s) or TA(s). For example, in a case where the Partially Allowed NSSAI is associated with TAI 1 (or TA 1) and the Partially Allowed NSSAI includes S-NSSAI 1, S-NSSAI 1 may be allowed or available in TAI 1 (or TA 1).　　For example, the Partially Allowed NSSAI may indicate S-NSSAI(s) which is allowed or available in associated or specific TA or TAI. For example, the Partially Allowed NSSAI may include S-NSSAI(s) associated with TA(s) or TAI(s). For example, in case where the Partially Allowed NSSAI includes S-NSSAI 1 associated with TAI 1 or TA 1 identified by TAI 1, it may mean that S-NSSAI 1 is allowed or available in TAI 1 or TA 1 identified by TAI 1. For example, in a case where the UE 3 receives the Partially Allowed NSSAI which includes S-NSSAI 1 associated with TAI 1 or TA 1 identified by TAI 1 and the UE 3 wants to use S-NSSAI 1, the UE 3 may consider that S-NSSAI 1 is allowed or available in TA 1. In a case where the UE 3 wants to use S-NSSAI 1 (e.g., the UE 3 wants to establish PDU session(s) on S-NSSAI 1) and the UE 3 considers that the UE 3 is in TA 1, the UE 3 may use S-NSSAI 1 (e.g., the UE 3 may use S-NSSAI 1 for establishing the PDU session(s) or the UE 3 may establish the PDU session(s) on S-NSSAI 1 or associated with S-NSSAI 1). In a case where the UE 3 is not in TA 1, the UE 3 may move to TA 1 and use S-NSSAI 1 in TA 1. For example, the Partially Allowed NSSAI or S-NSSAI(s) in the Partially Allowed NSSAI may indicate S-NSSAI(s) which is allowed or is available in specific TAI(s) or TA(s) identified by the specific TAI(s). The Partially Allowed NSSAI or S-NSSAI(s) in the Partially Allowed NSSAI may be associated with specific TAI(s) or TA(s) identified by the specific TAI(s).　　The Rejected S-NSSAIs partially in the RA may include a list of S-NSSAI(s) and each S-NSSAI in the list has associated list of TAI(s). The S-NSSAI in the Rejected S-NSSAIs partially in the RA may be only allowed to use in the TAI(s) associated to the S-NSSAI. To use that S-NSSAI in the TAI(s) or TA(s) identified by the TAI(s), the UE has to perform the Registration procedure with the S-NSSAI set to the Requested NSSAI at the associated TAI(s).　　For example, S-NSSAI(s) in the Rejected S-NSSAIs partially in the RA may be associated with TAI(s) or TA. For example, the Rejected S-NSSAIs partially in the RA may include S-NSSAI(s) associated with TA(s) or TAI(s). For example, in case where the Rejected S-NSSAIs partially in the RA include S-NSSAI 1 associated with TAI 1 or TA 1 identified by TAI 1, it may mean that S-NSSAI 1 is only allowed or only available in TAI 1 or TA 1 identified by TAI 1. For example, in a case where the UE 3 receives the Rejected S-NSSAIs partially in the RA which includes S-NSSAI 1 associated with TAI 1 or TA 1 identified by TAI 1 and the UE 3 wants to use S-NSSAI 1, the UE 3 may move to TA 1 and may perform the Registration procedure for S-NSSAI 1 in TA 1. In a case where the UE 3 has been already in TA 1, the UE 3 may perform the Registration procedure for S-NSSAI 1 in TA 1.　　For example, the Rejected S-NSSAIs partially in the RA or S-NSSAI(s) in the Rejected S-NSSAIs partially in the RA may indicate S-NSSAI(s) which is allowed to use or available if the UE 3 performs, in specific TAI(s) or TA(s) identified by the specific TAI(s), a new Registration procedure for the S-NSSAI(s) or performs, in the specific TAI(s) or the TA(s) identified by the specific TAI(s), a Registration procedure for the S-NSSAI(s) again.　　For example, the Rejected S-NSSAIs partially in the RA or S-NSSAI(s) in the Rejected S-NSSAIs partially in the RA may indicate S-NSSAI(s) which is allowed or is available in specific TAI(s) or TA(s) identified by the specific TAI(s) and which is allowed to use or available if the UE 3 performs, in the specific TAI(s) or the TA(s) identified by the specific TAI(s), a new Registration procedure for the S-NSSAI(s) or performs, in the specific TAI(s) or the TA(s) identified by the specific TAI(s), a Registration procedure for the S-NSSAI(s) again. The Rejected S-NSSAIs partially in the RA or S-NSSAI(s) in the Rejected S-NSSAIs partially in the RA may be associated with specific TAI(s) or TA(s) identified by the specific TAI(s).　　For example, S-NSSAI(s) in the Rejected S-NSSAIs partially in the RA may indicate S-NSSAI(s) which is only allowed or only available in associated or specific TAI(s) or TA(s). For example, the Rejected S-NSSAIs partially in the RA includes S-NSSAI 1 which is only allowed or only available in TAI 1 (or TA 1).　　For example, the Rejected S-NSSAIs partially in the RA includes S-NSSAI(s) which is only allowed or only available in associated or specific TAI(s) or TA(s).　　For example, the Rejected S-NSSAIs partially in the RA may be associated with TAI(s) or TA(s). For example, in a case where the Rejected S-NSSAIs partially in the RA is associated with TAI 1 (or TA 1) and the Rejected S-NSSAIs partially in the RA includes S-NSSAI 1, S-NSSAI 1 may be only allowed or only available in TAI 1 (or TA 1). For example, in a case where the Rejected S-NSSAIs partially in the RA is associated with TAI 1 (or TA 1) and the Rejected S-NSSAIs partially in the RA includes S-NSSAI 1, S-NSSAI 1 may be rejected in TAI(s) (or TA(s)) except for TAI 1 (or TA 1).　　For example, the Rejected S-NSSAIs partially in the RA may indicate S-NSSAI(s) which is only allowed or only available in associated or specific TA or TAI.　　The NSSF 76 may include, in the Nnssf_NSSelection_Get Response message, at least one of a first target AMF set, a first list of candidate AMF(s), a second target AMF set, the second list of candidate AMF(s), a third AMF set and a third list of candidate AMF(s). AMF(s) in the first target AMF set or the first list may support the Allowed NSSAI only. AMF(s) in the second target AMF set or the second list may support both the Allowed NSSAI and the Partially Allowed NSSAI. AMF(s) in the third target AMF set or the third list may support the Partially Allowed NSSAI only.　　For example, in a case where the NSSF 76 receives the Requested NSSAI which includes S-NSSAI 1, the NSSF 76 may generate, based on operator's policy or local configuration in the NSSF 76, the Partially Allowed NSSAI which includes S-NSSAI 1 by setting S-NSSAI 1 to the Partially Allowed NSSAI.　　For example, in a case where the NSSF 76 receives the Requested NSSAI which includes S-NSSAI 1, the NSSF 76 may generate, based on operator's policy or local configuration in the NSSF 76, the Rejected S-NSSAIs partially in the RA which includes S-NSSAI 1 by setting S-NSSAI 1 to the Rejected S-NSSAIs partially in the RA.　　For example, in a case where the NSSF 76 receives the Requested NSSAI which includes S-NSSAI 1 and TAI 1, the NSSF 76 may generate, based on operator's policy or local configuration in the NSSF 76, the Partially Allowed NSSAI regarding TAI 1 which includes S-NSSAI 1 by setting S-NSSAI 1 to the Partially Allowed NSSAI.　　For example, in a case where the NSSF 76 receives the Requested NSSAI which includes S-NSSAI 1 and TAI 1, the NSSF 76 may generate, based on operator's policy or local configuration in the NSSF 76, the Partially Allowed NSSAI which includes S-NSSAI 1 associated with TAI 1 by setting S-NSSAI 1 to the Partially Allowed NSSAI and by associating TAI 1 with S-NSSAI 1. S-NSSAI 1 associated with TAI 1 may indicate that S-NSSAI 1 is only allowed or available in TAI 1 (e.g., in TA 1 indicated by TAI 1).　　For example, in a case where the NSSF 76 receives the Requested NSSAI which includes S-NSSAI 1 and TAI 1, the NSSF 76 may generate, based on operator's policy or local configuration in the NSSF 76, the Rejected S-NSSAIs partially in the RA regarding TAI 1 which includes S-NSSAI 1 by setting S-NSSAI 1 to the Rejected S-NSSAIs partially in the RA.　　For example, in a case where the NSSF 76 receives the Requested NSSAI which includes S-NSSAI 1 and TAI 1, the NSSF 76 may generate, based on operator's policy or local configuration in the NSSF 76, the Rejected S-NSSAIs partially in the RA which includes S-NSSAI 1 associated with TAI 1 by setting S-NSSAI 1 to the Rejected S-NSSAIs partially in the RA and by associating TAI 1 with S-NSSAI 1. S-NSSAI 1 associated with TAI 1 may indicate that S-NSSAI 1 is only allowed or available in TAI 1 (e.g., in TA 1 indicated by TAI 1).　　For example, in this disclosure, the NSSF 76 may set, based on at least one of the input parameters, an operator's policy and a local configuration in the NSSF 76, S-NSSAI(s) that the NSSF 76 allows to use for the UE 3 in specific TA(s) to the Partially Allowed NSSAI.For example, in this disclosure, the NSSF 76 may set, based on at least one of the input parameters, an operator's policy and a local configuration in the NSSF 76, S-NSSAI(s) which is allowed to use or available if the UE 3 performs, in specific TA(s), a new Registration procedure for the S-NSSAI(s) or performs, in specific TA(s), a Registration procedure for the S-NSSAI(s) again to the Rejected S-NSSAIs partially in the RA.　　For example, the NSSF 76 may determine at least one of the Partially Allowed NSSAI and the Rejected S-NSSAI partially based on information indicating which network slice(s) or S-NSSAI(s) is allowed or available for the UE 3. The at least one of the input parameters, an operator's policy and a local configuration in the NSSF 76 may include information indicating which network slice(s) or S-NSSAI(s) is allowed or available for the UE 3 or any other information for determining the at least one of the Partially Allowed NSSAI and the Rejected S-NSSAI partially.　　Step 7. Upon reception of the Nnssf_NSSelection_Get Response message in step 6, the AMF 70 decides at least one of RA (e.g., TAI list), Allowed NSSAI, Rejected NSSAI, Partially Allowed NSSAI, and Rejected S-NSSAIs partially in the RA based on input from the NSSF 76 in step 6. For example, the AMF 70 may determine at least one of RA (e.g., TAI list), Allowed NSSAI, Rejected NSSAI, Partially Allowed NSSAI, and Rejected S-NSSAIs partially in the RA based on input from the NSSF 76 in step 6.　　For example, in a case where the AMF 70 receives the Nnssf_NSSelection_Get Response message, the AMF 70 may decide relationship between the RA (e.g., TAI list) and at least one of the Partially Allowed NSSAI, the Rejected S-NSSAIs partially, the Allowed NSSAI and Rejected NSSAI.　　For example, it assumes a case where the Allowed NSSAI includes S-NSSAI 1, the Partially Allowed NSSAI includes S-NSSAI 2, the Rejected S-NSSAIs partially includes S-NSSAI 3 (e.g., the AMF 70 receives the Nnssf_NSSelection_Get Response message including the Allowed NSSAI which includes S-NSSAI 1, the Partially Allowed NSSAI which includes S-NSSAI 2 and the Rejected S-NSSAIs partially which includes S-NSSAI 3), and the RA includes TA 1 to TA 4. In this case, the AMF 70 may decide that S-NSSAI 1 is allowed to use in the RA (i.e., in TA 1 to TA 4), S-NSSAI 2 is allowed to use in TA 1 and TA 2, S-NSSAI 3 is allowed to use in TA 4. In other words, the AMF 70 may decide that the Allowed NSSAI is for the RA (i.e., TA 1 to TA 4), the Partially Allowed NSSAI is for the TA 1 and TA 2, the Rejected S-NSSAIs partially is for TA 4.　　For example, in a case where the AMF 70 receives the Nnssf_NSSelection_Get Response message, the AMF 70 may decide to send, to the UE 3, at least one of the received Partially Allowed NSSAI, the received Rejected S-NSSAIs partially, the received Allowed NSSAI and received Rejected NSSAI as it is.　　For example, in a case where the AMF 70 receives the Nnssf_NSSelection_Get Response message including the Partially Allowed NSSAI which includes S-NSSAI 1, the AMF 70 may decide to send, to the UE 3, at least the received Partially Allowed NSSAI which includes S-NSSAI 1.　　For example, in a case where the AMF 70 receives the Nnssf_NSSelection_Get Response message including the Rejected S-NSSAIs partially in the RA which includes S-NSSAI 1, the AMF 70 may decide to send, to the UE 3, at least the received Rejected S-NSSAIs partially in the RA which includes S-NSSAI 1.　　For example, in a case where the AMF 70 receives the Nnssf_NSSelection_Get Response message including the Partially Allowed NSSAI regarding TAI 1 which includes S-NSSAI 1, the AMF 70 may decide to send, to the UE 3, at least the received Partially Allowed NSSAI regarding TAI 1 which includes S-NSSAI 1.　　For example, in a case where the AMF 70 receives the Nnssf_NSSelection_Get Response message including the Rejected S-NSSAIs partially in the RA regarding TAI 1 which includes S-NSSAI 1, the AMF 70 may decide to send, to the UE 3, at least the received Rejected S-NSSAIs partially in the RA regarding TAI 1 which includes S-NSSAI 1.　　For example, in a case where the AMF 70 receives the Nnssf_NSSelection_Get Response message including the Partially Allowed NSSAI which includes S-NSSAI 1 associated with TAI 1, the AMF 70 may decide to send, to the UE 3, at least the received Partially Allowed NSSAI which includes S-NSSAI 1 associated with TAI 1.　　For example, in a case where the AMF 70 receives the Nnssf_NSSelection_Get Response message including the Rejected S-NSSAIs partially in the RA which includes S-NSSAI 1 associated with TAI 1, the AMF 70 may decide to send, to the UE 3, at least the received Rejected S-NSSAIs partially in the RA which includes S-NSSAI 1 associated with TAI 1.　　If the AMF 70 decides to send the Partially Allowed NSSAI along with the Allowed NSSAI, the AMF 70 may choose an AMF from the second target AMF set or the second list of candidate AMF(s) which supports both the Allowed NSSAI and the Partially Allowed NSSAI.　　For example, in this disclosure, the AMF 70 may set, based on at least one of the input from the NSSF 76 in step 6, an operator's policy and a local configuration in the AMF 70, S-NSSAI(s) that the AMF 70 allows to use for the UE 3 in specific TA(s) to the Partially Allowed NSSAI.　　For example, in this disclosure, the AMF 70 may set, based on at least one of the input from the NSSF 76 in step 6, an operator's policy and a local configuration in the AMF 70, S-NSSAI(s) which is allowed to use or available if the UE 3 performs, in specific TA(s), a new Registration procedure for the S-NSSAI(s) or performs, in specific TA(s), a Registration procedure for the S-NSSAI(s) again to the Rejected S-NSSAIs partially in the RA.　　Step 8. The AMF 70 sends a Registration Accept message to the UE 3 including at least one of the RA (i.e., TAI list), the Allowed NSSAI, the Rejected NSSAI, the Partially Allowed NSSAI, the Rejected S-NSSAIs partially in the RA and other existing information.　　For example, the AMF 70 may send the Registration Accept message including the information (e.g., at least one of the Allowed NSSAI, the Rejected NSSAI, the Partially Allowed NSSAI and the Rejected S-NSSAIs partially) decided in step 7.　　For example, the AMF 70 may send a UE Configuration Update message or any other messages including the information (e.g., at least one of the Allowed NSSAI, the Rejected NSSAI, the Partially Allowed NSSAI and the Rejected S-NSSAIs partially) decided in step 7.　　Step 9. Upon reception of the Registration Accept message from the AMF 70, the UE 3 stores at least one of the TAI list, the Allowed NSSAI, the Rejected NSSAI, the Partially Allowed NSSAI, the Rejected S-NSSAIs partially in the RA and other received information in step 8. For example, the UE 3 may store at least one of the TAI list, the Allowed NSSAI, the Rejected NSSAI, the Partially Allowed NSSAI, the Rejected S-NSSAIs partially in the RA and other received information to non-volatile memories in the UE 3.　　Step 10. The UE 3 sends a Registration Complete message to the AMF 70.Variant 1 of First example of the First Aspect:　　In a case where the UE 3 receives the Allowed NSSAI including S-NSSAI (e.g., S-NSSAI 1) and the Partially Allowed NSSAI including the same S-NSSAI (e.g., S-NSSAI 1) from the AMF 70 in the Registration Accept message in step 8, the UE 3 may accept the received S-NSSAI (e.g., S-NSSAI 1) as the Allowed NSSAI (e.g., the UE 3 may accept the Allowed NSSAI which includes S-NSSAI 1, and use the Allowed NSSAI for subsequent process(es)) and remove the S-NSSAI (e.g., S-NSSAI 1) from the Partially Allowed NSSAI if the UE 3 has stored or maintained the Partially Allowed NSSAI including the S-NSSAI (e.g., S-NSSAI 1).　　Alternatively, in a case where the UE 3 receives the Allowed NSSAI including S-NSSAI (e.g., S-NSSAI 1) and the Partially Allowed NSSAI including the same S-NSSAI (e.g., S-NSSAI 1) from the AMF 70 in the Registration Accept message in step 8, the UE 3 may accept the received S-NSSAI (e.g., S-NSSAI 1) as the Partially Allowed NSSAI (e.g., the UE 3 may accept the Partially Allowed NSSAI which includes S-NSSAI 1, and use the Partially Allowed NSSAI for subsequent process(es)) and remove the S-NSSAI (e.g., S-NSSAI 1) from the Allowed NSSAI if the UE 3 has already stored or maintained the Allowed NSSAI including the S-NSSAI (e.g., S-NSSAI 1).Variant 2 of First example of the First Aspect:　　In a case where the UE 3 receives the Rejected NSSAI including S-NSSAI (e.g., S-NSSAI 1) and the Rejected S-NSSAIs partially in the RA including the same S-NSSAI (e.g., S-NSSAI 1) from the AMF 70 in the Registration Accept message in step 8, the UE 3 may accept the received S-NSSAI (e.g., S-NSSAI 1) as the Rejected NSSAI and remove the S-NSSAI (e.g., S-NSSAI 1) from the Rejected S-NSSAIs partially in the RA if the UE 3 has already stored or maintained the Rejected S-NSSAIs partially in the RA including the S-NSSAI (e.g., S-NSSAI 1).　　Alternatively, in a case where the UE 3 receives the Rejected NSSAI including S-NSSAI (e.g., S-NSSAI 1) and the Rejected S-NSSAIs partially in the RA including the same S-NSSAI (e.g., S-NSSAI 1) from the AMF 70 in the Registration Accept message in step 8, the UE 3 may accept the received S-NSSAI (e.g., S-NSSAI 1) as the Rejected S-NSSAIs partially in the RA and remove the S-NSSAI (e.g., S-NSSAI 1) from the Rejected NSSAI if the UE 3 has already stored or maintained the Rejected NSSAI including the S-NSSAI (e.g., S-NSSAI 1).Variant 3 of First example of the First Aspect:　　In one example, the Partially Allowed NSSAI in steps 6, 7, 8 and 9 may include a list of Allowed S-NSSAI(s) and each S-NSSAI in the list has associated with a list of cell(s).　　For example, S-NSSAI(s) in the Partially Allowed NSSAI may be associated with a list of cell(s).　　For example, S-NSSAI(s) in the Partially Allowed NSSAI may be associated with cell(s).　　For example, S-NSSAI(s) in the Partially Allowed NSSAI may be associated with or available in specific cell(s).　　For example, S-NSSAI 1 associated with cell 1 is included in the Partially Allowed NSSAI. S-NSSAI 1 associated with cell 1 may be allowed or available in cell 1.　　For example, S-NSSAI 1 associated with TA 1 and cell 1 is included in the Partially Allowed NSSAI. S-NSSAI 1 associated with TA 1 and cell 1 may be allowed or available in cell 1 of TA 1.Variant 4 of First example of the First Aspect:　　In one example, in step 6, the NSSF 76 may not provide the Partially Allowed NSSAI or the Rejected S-NSSAIs partially in the RA but provide the Allowed NSSAI, and a list of S-NSSAI(s) which is present in the Requested NSSAI and not homogenously supported in the RA which includes TA(s) supported by the AMF 70, and the TA(s) (e.g., TAI(s) of the TA(s)) supporting the S-NSSAI in the list. The NSSF 76 may send a Target AMF set(s) which includes AMF(s) supporting the Allowed NSSAI or a list(s) of candidate AMF(s) supporting the Allowed NSSAI. In step 7, upon reception of the Nnssf_NSSelection_Get Response message, the AMF 70 may construct the Partially Allowed NSSAI. The AMF 70 may send the Allowed NSSAI and the Partially Allowed NSSAI to the NSSF 76 in an existing message or in a new message to get Target AMF set(s) including AMF(s) which supports both the Allowed NSSAI and the Partially Allowed NSSAI or list of candidate AMF(s) including AMF(s) which supports both the Allowed NSSAI and the Partially Allowed NSSAI. Upon reception of the message from the AMF 70, the NSSF 76 may provide the Target AMF set(s) or the list of candidate AMF(s) in an existing message or a new message to the AMF 70. Upon reception of the message from the NSSF 76, the AMF 70 may select an AMF from the Target AMF set(s) or the list of candidate AMF(s). The steps 8 and 9 may be executed afterwards.Variant 5 of First example of the First Aspect:　　In one example, the AMF 70 may subscribe with the NSSF 76 to be notified, regularly or on event bases, about the network slice support within the PLMN. For example, the AMF 70 may subscribe with the NSSF 76 or may send a subscription request to the NSSF 76 for receiving notification about the network slice support within the PLMN from the NSSF 76. The notification may be periodic or regular. The notification may be sent to the AMF 70 periodically or regularly. The notification may be sent to the AMF 70 in a case where specific event(s) occurs.　　During the subscription request to the NSSF 76, the AMF 70 may provide a list of network slice(s) (e.g., a list of S-NSSAI(s)) which is supported by the AMF 70. The AMF 70 may also provide a type of the required notification from the NSSF 76. For example, the type may indicate that regular or periodic notification is required. For example, the type may indicate that notification is required in a case where specific event(s) occurs. For example, the event(s) may include a change in one or more network slices (e.g., one or more S-NSSAI(s)) supported by the AMF 70. The change may be related to whether the network slice(s) (e.g., S-NSSAI(s)) is fully supported or partially supported within the PLMN. If the network slice is changed from fully supported in the PLMN to partially supported in the PLMN (e.g., the supported TA of the network slice is changed from RA including TA 1 and TA 2 to TA 1 only), the NSSF 76 may provide, to the AMF 70, the notification including an updated list of TA(s) in which each network slice is supported (e.g., the NSSF 76 may provide, to the AMF 70, TA 1 where the network slice is supported). If a certain network slice is temporary supported, the NSSF 76 may also provide the time window at which the temporary slice is supported. The AMF 70 may store the received network slice support information from the NSSF 76 for each network slice supported by AMF 70. For example, the network slice support information may include at least one of the updated list and the time window. Then, during the UE 3's registration with the AMF 70, if the UE 3 sends the Partial Network Slice Availability support indication, the AMF 70 may check, by using the stored network slice support information within the AMF 70, whether the network slice(s) (e.g., S-NSSAI(s)) within the Requested NSSAI provided by UE 3 in step 1 of Fig. 1 are fully supported or partially supported in the PLMN. If one or more network slices in the Requested NSSAI are partially supported in the PLMN, the AMF 70 may consider the TA(s) in which these network slices are supported when deciding what RA to assign to the UE 3 so that the number of the Partially supported network slice in the RA of the UE 3 is minimal. Then the AMF 70 may provide the Allowed network slice (e.g., Allowed NSSAI) and the Partially Allowed network slice (e.g., Partially Allowed NSSAI) and the Partially Rejected network slice (e.g., the Rejected S-NSSAIs partially in the RA) to the UE 3 by using the Registration Accept message in step 8 of Fig. 1. Alternatively, the AMF 70 may provide the Partially Allowed network slice and the Partially Rejected network slice to the UE 3 by using a UE Configuration Update message.Variant 6 of First example of the First Aspect:　　The AMF 70 may not include the Partial Network Slice Availability support indication in the Nudm_SDM_Get Request message. The UDM 75 may send the Nudm_SDM_Get Response message even if the Partial Network Slice Availability support indication is not included in the Nudm_SDM_Get Request message.　　The Partial Network Slice Availability support indication may not be included in the messages mentioned in Fig. 1. Each node in Fig. 1 may perform process(es) in Fig. 1 without the Partial Network Slice Availability support indication.　　These above variants may be applied to other examples of the First Aspect.　　According to at least one of First example of the First Aspect and the variants in the First example, it can solve the above-mentioned problem.　　For example, at least one of First example of the First Aspect and the variants in the First example can solve the problem that regarding the decision by the AMF based on the AMF local policy, there are some problems.　　For example, at least one of First example of the First Aspect and the variants in the First example can solve the problem that mobile operators need to manage network slice related data, one in the NSSF and another one in the AMF and this makes mobile operators difficult to manage network slice related data in their network and causes additional cost for management.　　For example, according to at least one of First example of the First Aspect and the variants in the First example, the NSSF 76 can configure at least one of the Partially Allowed NSSAI and the Rejected S-NSSAIs partially in the RA. For example, that is, there is no need to manage the network slice related data separately. For example, that is, the network slice related data is stored in the NSSF 76. Therefore, it can solve the above-mentioned problem.Second example of the First Aspect:　　According to the network slice management mechanism in 5GC as defined in NPL 3, the 5GC has a dedicated functional entity, Network Slice Selection Function (NSSF), for assigning S-NSSAI(s) to the UE based on the network slice(s) within the Requested NSSAI from the UE, a subscriber data of the UE, a location of the UE and other configuration data in the 5GC and an associated Operation and Maintenance (O&M) system. Based on this mechanism, mobile operators configure the network slice related data base in the NSSF.　　On the other hand, NPL 2 defines that newly introduced network slice related data, Partially Allowed NSSAI and S-NSSAIs rejected partially in the RA, which are selected based on the sole decision by the AMF based on the AMF local policy.　　In the 5G system there are some nodes except for the AMF, hence that only the AMF is able to perform the above decision based on the AMF local policy may make unnecessary limitation for the 5G system.　　For example, this Second example of the First Aspect includes flexible mechanism for managing newly introduced network slice related data, for example Partially Allowed NSSAI and S-NSSAIs rejected partially in the RA in mobile operator's network.　　Fig. 2 includes an example that allows a PCF 73 to provide the Partially Allowed NSSAI and Rejected S-NSSAIs partially in the RA to an AMF 70 based on one or more operator policies or configuration in the PCF 73. This example allows for a network slice to be classed as partially allowed or partially rejected not only because these network slices are not supported in certain TAs of the RA of the UE but also based on the operator policies in the PCF 73 which may consider the slice congestion (e.g., a network slice is made not allowed in TAs with high congestion) or any other issues with the network slice(s). For example, one or more network slices may be supported in the whole RA of the UE 3 however, because in some TAs of the RA the congestion may be very high, based on the operator policy or configuration in PCF 73 the network slices in these TAs with high congestion (e.g., with congestion higher than a threshold level set in the one or more operator's policies) may be considered as not supported in these high congestion TAs. In this case these network slices, although supported in all the TAs of the RA would be treated and provided to the UE 3 as Partially Allowed network slices, i.e., not allowed in the TAs with a congestion higher than the threshold set in the operator's policies or configuration in the PCF 73. The PCF 73 can make the granularity of this feature per UE, per location or only at specific times while the NSSF 76 is with system wide granularity.　　The detailed processes of the Second example of the First Aspect are described below with reference to Fig. 2.　　Step 1. The steps 1 to 4 in Fig. 1 take place.　　Step 2. After the AMF 70 obtained the subscriber data for the UE 3 from the UDM 75, the AMF 70 sends an Npcf_AMPolicyControl_Create message to the PCF 73 including at least one of Requested NSSAI, Partial Network Slice Availability support indication and other existing information. See step 1 in Fig. 1 for definition of the Requested NSSAI and the Partial Network Slice Availability support indication. For example, the Partial Network Slice Availability support indication and the Requested NSSAI in the step 2 may be same one in the step 1.　　Step 3. Upon reception of the Npcf_AMPolicyControl_Create message, based on at least one of the received Requested NSSAI, operator configuration and operator policy in the PCF 73, the PCF 73 may decide to configure one or more requested S-NSSAIs (e.g., S-NSSAI(s) in the Requested NSSAI) as partially allowed or partially rejected in the RA. For example, the PCF 73 may determine at least one of the Partially Allowed NSSAI and the Rejected S-NSSAIs partially in the RA based on at least one of the received Requested NSSAI, operator configuration and operator policy in the PCF 73. For example, the PCF 73 may determine at least one of the Partially Allowed NSSAI and the Rejected S-NSSAIs partially in the RA even if the PCF 73 does not receive the Partial Network Slice Availability support indication.　　The at least one of the received Requested NSSAI, operator configuration and operator policy may be expressed as information for determining at least one of the Partially Allowed NSSAI and the Rejected S-NSSAIs partially.　　For example, one or more network slices may be supported in the whole RA of the UE 3 however, because in some TAs of the RA the congestion may be very high or for any other consideration, based on operator policy or configuration in PCF 73 the network slices in these TAs with high congestion (e.g. with congestion higher than a threshold level set in the operator's policies) or for any other reason may be considered as not supported in these TAs. In this case these network slices, although supported in all the TAs of the RA, would be treated and provided to the UE 3 as Partially Allowed network slices (e.g., the Partially Allowed NSSAI), i.e., not allowed in the TAs with a congestion higher than the threshold set in the operator's policies or configuration in the PCF 73. The PCF 73 can decide whether the network slice is Partially Allowed network slice (e.g., the Partially Allowed NSSAI) or Partially Rejected network slice (e.g., S-NSSAIs rejected partially) per all UEs bases or per a group of UEs bases or per a single UE bases granularity depending on the instructions in the operator's policies or configurations within the PCF 73.　　The PCF 73 generates Partially Allowed NSSAI, Rejected S-NSSAIs partially in the RA based on the input parameters, for example Requested NSSAI, in the Npcf_AMPolicyControl_Create message. The PCF 73 may generate at least one of Partially Allowed NSSAI and Rejected S-NSSAIs partially in the RA only if the Npcf_AMPolicyControl_Create message includes the Partial Network Slice Availability support indication.　　For example, the PCF 73 may configure S-NSSAI(s) in the Requested NSSAI as the Partially Allowed NSSAI or Rejected S-NSSAIs partially in the RA based on the operator's policy or local configuration in the PCF 73.　　For example, the PCF 73 may set S-NSSAI(s) in the Requested NSSAI to the Partially Allowed NSSAI or Rejected S-NSSAIs partially in the RA based on the operator's policy or local configuration in the PCF 73.　　For example, it assumes a case where S-NSSAI 1 is supported in the RA which includes TA 1 and TA 2, and the PCF 73 knows, based on the operator's policy or local configuration in the PCF 73, that TA 1 is in high congestion (e.g., the congestion level in TA1 is higher than a threshold congestion level set by the operator's configuration or policies). In this case, the PCF 73 may set S-NSSAI 1 to the Partially Allowed NSSAI regarding TA 2 (e.g., the UE 3 is allowed to trigger request for PDU Session when the UE is in TA 2 however, the UE 3 is not allowed to trigger request for PDU Session when the UE 3 is in TA 1 due to the high congestion level in TA1, although the S-NSSAI 1 is supported in TA 1 as well) or the PCF 73 may set S-NSSAI 1 associated with TA 2 to the Partially Allowed NSSAI.　　For example, it assumes a case where S-NSSAI 1 is supported in the RA which includes TA 1 and TA 2, and the PCF 73 knows, based on the operator's policy or local configuration in the PCF 73, that TA 1 is in high congestion. In this case, the PCF 73 may set S-NSSAI 1 to the Rejected S-NSSAIs partially regarding TA 1 or the PCF 73 may set S-NSSAI 1 associated with TA 1 to the Rejected S-NSSAIs partially.　　Please note that whether the S-NSSAI(s) in the Requested NSSAI is set to the Partially Allowed NSSAI or the Rejected S-NSSAIs partially in the RA may be determined based on other factors. For example, the PCF 73 may determine whether the S-NSSAI(s) in the Requested NSSAI is set to the Partially Allowed NSSAI or the Rejected S-NSSAIs partially in the RA based on subscriber data for the UE 3 (e.g., S-NSSAI which normally is fully supported in the PLMN and the UE's RA may transit from allowed S-NSSAI (e.g., Allowed NSSAI) to partially allowed S-NSSAI (e.g., Partially Allowed NSSAI) for the UE 3 in certain times of the day or week or year by subscription in the UDM. In this way the operator may balance the quality of service between UEs of different level of subscription, e.g., allowing to UEs with higher priority subscription to maintain the quality of service even when the system is congested.) or information indicating which network slice(s) (e.g., S-NSSAI) is supported in TA(s) (or TAI(s)) and so on.　　The subscriber data may indicate which network slice(s) (e.g., S-NSSAI) is allowed or available for UE(s).　　For example, it assumes a case where S-NSSAI 1 is supported in the RA which includes TA 1 and TA 2, and the PCF 73 knows, based on the operator's policy or local configuration in the PCF 73, that S-NSSAI 1 is allowed or available for the UE 3 in TA 1. In this case, the PCF 73 may set S-NSSAI 1 to the Partially Allowed NSSAI regarding TA 1 or the PCF 73 may set S-NSSAI 1 associated with TA 1 to the Partially Allowed NSSAI.　　For example, it assumes a case where S-NSSAI 1 is supported in the RA which includes TA 1 and TA 2, and the PCF 73 knows, based on the operator's policy or local configuration in the PCF 73, that S-NSSAI 1 is allowed or available for the UE 3 when the UE 3 performs a Registration procedure in TA 1. In this case, the PCF 73 may set S-NSSAI 1 to the Rejected S-NSSAIs partially regarding TA 1 or the PCF 73 may set S-NSSAI 1 associated with TA 1 to the Rejected S-NSSAIs partially.　　For example, in this disclosure, the PCF 73 may set, based on at least one of the received Requested NSSAI, operator configuration and operator policy in the PCF 73, S-NSSAI(s) that the PCF 73 allows to use for the UE 3 in specific TA(s) to the Partially Allowed NSSAI.　　For example, in this disclosure, the PCF 73 may set, based on at least one of the received Requested NSSAI, operator configuration and operator policy in the PCF 73, S-NSSAI(s) which is allowed to use or available if the UE 3 performs, in specific TA(s), a new Registration procedure for the S-NSSAI(s) or performs, in specific TA(s), a Registration procedure for the S-NSSAI(s) again to the Rejected S-NSSAIs partially in the RA.　　For example, the PCF 73 may determine at least one of the Partially Allowed NSSAI and the Rejected S-NSSAIs partially in the same manner as the NSSF 76 in step 6 of Fig. 1 or the AMF 70 in step 7 of Fig. 1.　　For example, the AMF 70 in Fig. 1 or the NSSF 76 may determine at least one of the Partially Allowed NSSAI and the Rejected S-NSSAIs partially in the same manner as the PCF 73 in Fig. 2.　　Step 4. The PCF 73 sends an Npcf_AMPolicyControl_Create Response message to the AMF 70 including at least one of the Partially Allowed NSSAI, and the Rejected S-NSSAIs partially in the RA.　　For example, the PCF 73 may send the Npcf_AMPolicyControl_Create Response message including the information (e.g., at least one of the Partially Allowed NSSAI and the Rejected S-NSSAIs partially) decided in step 3.　　The PCF 73 may include the Partially Allowed NSSAI and the Rejected S-NSSAIs partially in the RA only if the Npcf_AMPolicyControl_Create message includes the Partial Network Slice Availability support indication.　　See step 6 in Fig. 1 for details of the Partially Allowed NSSAI and the Rejected S-NSSAIs partially in the RA.　　Step 5. Upon reception of the Npcf_AMPolicyControl_Create Response message in step 4, the AMF 70 decides RA (e.g., TAI list), Allowed NSSAI, Rejected NSSAI, Partially Allowed NSSAI, Rejected S-NSSAIs partially in the RA based on input from the PCF 73 in step 4. The AMF 70 may perform the same process(es) as in step 7 in Fig. 1.　　Step 6. The steps 8 to 10 in Fig. 1 take place.Variant 1 of Second example of the First Aspect:　　In one example, the operator policy or configuration related to the network slice availability (e.g., the operator policy or the configuration mentioned in step 3) may be provided to the AMF 70 by the PCF 73 in step 4 of Fig. 2 within the Npcf_AMPolicyControl_Create Response message or within any other existing or a new message between the PCF 73 and the AMF 70. In this case the AMF 70 may decide which network slice(s) (e.g., S-NSSAI(s)) from the Requested NSSAI provided by UE 3 in step 1 of Fig. 2 will be treated as Partially Allowed network slice (e.g., Partially Allowed NSSAI) or as Partially Rejected network slice (e.g., S-NSSAIs rejected partially) in the Registration Area of the UE 3 based on the operator policies and configuration related the network slice availability provided by the PCF 73 to AMF 70 in step 4 of Fig. 2. For example, one or more network slices may be supported in the whole RA of the UE 3 however, because in some TAs of the RA the congestion may be very high or for any other consideration, based on the operator policies and configuration related the network slice availability provided by the PCF 73 to AMF 70 the network slices in these TAs with high congestion (e.g., with congestion higher than a threshold level set in the operator's policies) or for any other reason may be considered as not supported in these TAs. In this case these network slices, although supported in all the TAs of the RA for the UE 3, would be treated and provided to the UE 3 as Partially Allowed network slices, i.e., not allowed in the TAs with a congestion higher than the threshold set in the the operator policies and configuration related the network slice availability provided by the PCF 73 to AMF 70. The AMF 70 can decide whether the network slice is Partially Allowed network slice or Partially Rejected network slice per all UEs bases or per a group of UEs bases or per a single UE bases granularity depending on the instructions in the operator's policies or configurations received from the PCF 73. For example, the AMF 70 may configure S-NSSAI(s) in the Requested NSSAI as the Partially Allowed NSSAI or Rejected S-NSSAIs partially in the RA based on the operator's policy or the configuration received from the PCF 73 in the same manner as the PCF 73 in step 3 of Fig. 2.　　According to at least one of Second example of the First Aspect and the variant in the Second example, it can solve the above-mentioned problem.　　For example, at least one of Second example of the First Aspect and the variant in the Second example can solve the problem that regarding the decision by the AMF based on the AMF local policy, there are some problems.　　For example, at least one of Second example of the First Aspect and the variant in the Second example can solve the problem that, that only the AMF is able to perform the above decision based on the AMF local policy may make unnecessary limitation for the 5G system.　　For example, according to at least one of Second example of the First Aspect and the variant in the Second example, the PCF 73 can configure at least one of the Partially Allowed NSSAI and the Rejected S-NSSAIs partially in the RA. Therefore, it can solve the above-mentioned problem.Third example of the First Aspect:　　According to the network slice management mechanism in 5GC as defined in NPL 3, the 5GC has a dedicated functional entity, Network Slice Selection Function (NSSF), for assigning S-NSSAI(s) to the UE based on the network slice(s) within the Requested NSSAI from the UE, a subscriber data of the UE, a location of the UE and other configuration data in the 5GC and an associated Operation and Maintenance (O&M) system. Based on this mechanism, mobile operators configure the network slice related data base in the NSSF.　　On the other hand, NPL 2 defines that newly introduced network slice related data, Partially Allowed NSSAI and S-NSSAIs rejected partially in the RA, which are selected based on the sole decision by the AMF based on the AMF local policy.　　In the 5G system there are some nodes except for the AMF, hence that only the AMF is able to perform the above decision based on the AMF local policy may make unnecessary limitation for the 5G system.　　For example, this Third example of the First Aspect includes flexible mechanism for managing newly introduced network slice related data, for example Partially Allowed NSSAI and S-NSSAIs rejected partially in the RA in mobile operator's network.　　Fig. 3 includes an example that relies on the network slice information provided by an NWDAF 74. This allows for a network slice to be classed as Partially Allowed network slice or Partially Rejected network slice not only because these slices are not supported in certain TAs of the RA but also based on the latest network slice status information provided by the NWDAF 74 which may be related to the slice congestion (e.g., a slice is made not allowed in TAs with high congestion) or any other issues with the network slices. For example, one or more network slices may be supported in the whole RA of the UE 3 however, because in some TAs of the RA the congestion may be very high, based on the network slice status information provided by the NWDAF 74 the network slices in these TAs with high congestion (e.g., with congestion higher than a threshold level set in the operator's policies) may be considered as not supported in these high congestion TAs. In this case these network slices, although supported in all the TAs of the RA would be treated and provided to the UE 3 as Partially Allowed network slices or Partially Rejected network slices, i.e., not allowed in the TAs with a congestion higher than the threshold set in the network slice status information provided by the NWDAF 74.　　The detailed processes of the Third example of the First Aspect are described below with reference to Fig. 3.　　Step 1. The AMF 70 subscribes to the Network Slice information notification service that is provided by the NWDAF 74.　　The Network Slice information notification service provides to Service customers the latest network slice information including at least one of congestion level, restricted area, allowed area and available time period information.　　For example, the NWDAF 74 may provide the network slice information to the AMF 70.　　In a case where the AMF 70 subscribes to the Network Slice information notification service that is provided by the NWDAF 74, the AMF 70 may provide a list of network slice(s) (e.g., S-NSSAI(s)) supported by the AMF 70 to the NWDAF 74. The NWDAF 74 may provide, to the AMF 70, the network slice information regarding network slice(s) (e.g., S-NSSAI(s)) indicated by the list.　　For example, the congestion level may indicate whether the network slice(s) (S-NSSAI(s)) is congested in TA(s).　　For example, the congestion level may indicate level of congestion in the network slice(s) in TA(s).　　For example, the congestion level may indicate whether S-NSSAI 1 or a network slice identified by S-NSSAI 1 is congested in TA(s).　　For example, the congestion level may indicate level of congestion for S-NSSAI 1 or a network slice identified by S-NSSAI 1 in TA(s).　　For example, the congestion level may indicate level of congestion, for S-NSSAI 1 or a network slice identified by S-NSSAI 1 in TA(s), higher than a threshold level of congestion defined by the operator's configuration or policies.　　For example, the restricted area may indicate an area restricted.　　For example, the restricted area may indicate an area restricted due to congestion in the network slice(s).　　For example, the restricted area may indicate a restricted TA.　　For example, the restricted area may indicate a restricted TA due to congestion in the network slice(s).　　For example, the restricted area may indicate area(s) or TA(s) where S-NSSAI(s) or network slice(s) identified by the S-NSSAI(s) is restricted or is not available.　　For example, the restricted area may indicate that S-NSSAI(s) or network slice(s) identified by the S-NSSAI(s) is restricted or is not available in TA(s).　　For example, the restricted area may indicate an area or a TA where S-NSSAI 1 or a network slice identified by S-NSSAI 1 is restricted or is not available.　　For example, the restricted area may indicate that S-NSSAI 1 or a network slice identified by S-NSSAI 1 is restricted or is not available in a TA.　　For example, the restricted area may indicate that S-NSSAI 1 or a network slice identified by S-NSSAI 1 is restricted or is not available in certain times of the day, week or year defined by operator's policy or configuration.　　For example, the allowed area may indicate an area allowed.　　For example, the allowed area may indicate an area allowed due to congestion in the network slice(s).　　For example, the allowed area may indicate an allowed TA.For example, the allowed area may indicate an allowed TA considering congestion in the network slice(s).　　For example, the allowed area may indicate area(s) or TA(s) where S-NSSAI(s) or network slice(s) identified by the S-NSSAI(s) is allowed or is available.　　For example, the allowed area may indicate an area or a TA where S-NSSAI 1 or a network slice identified by S-NSSAI 1 is allowed or is available.　　For example, the allowed area may indicate that S-NSSAI 1 or a network slice identified by S-NSSAI 1is allowed or is available in a TA.　　For example, the allowed area may indicate that S-NSSAI 1 or a network slice identified by S-NSSAI 1 is allowed or is available in certain times of the day, week or year defined by operator's policy or configuration.　　The available time period information may indicate term or period of validity for at least one of the congestion level, the restricted area, the allowed area.　　The available time period information may indicate term or period of validity for network slice(s) (or S-NSSAI(s)).　　Step 2. Once a condition for notification is met, the NWDAF 74 sends an Nnwdaf_SliceInformation Notification message to the AMF 70 including the network slice information regarding the network slice(s) supported by the AMF 70. For example, the NWDAF 74 may send the Nnwdaf_SliceInformation Notification message to the AMF 70 periodically.For example, the NWDAF 74 may send the Nnwdaf_SliceInformation Notification message to the AMF 70 including the network slice information regarding the network slice(s) indicated by the list in step 1.　　The network slice information may be expressed as information for determining at least one of the Partially Allowed NSSAI and the Rejected S-NSSAI partially.　　Step 3. Based on the received information in the Nnwdaf_SliceInformation Notification message from the NWDAF 74, the AMF 70 decides whether updating UE configuration is needed or not. For example, based on the network slice support information received from the NWDAF 74, like network slice congestion and any other issues with the network slices, the AMF 70 may decide that one or more network slices from the Allowed NSSAI for the UE 3 is treated as Partially Allowed network slices as these network slice(s) are with hight level of congestion in certain TAs of the RA for the UE 3 or there are any other problems with these network slice in some of the TAs of the RA for the UE 3. In such cases, the AMF 70 may update the Allowed NSSAI for the UE 3 by removing such problematic network slice from the Allowed NSSAI for the UE 3 and by adding these network slices in the Partially Allowed NSSAI or the Rejected S-NSSAIs partially in the RA for the UE 3.　　For example, it assumes a case where the RA includes TAs 1 to 4 and the AMF 70 has sent the Allowed NSSAI including S-NSSAIs 1, 2 and 3 to the UE 3 and the AMF 70 stores the Allowed NSSAI. And it assumes a case where the received congestion level indicates that a network slice identified by S-NSSAI 2 is congested in TAs 3 and 4 and a network slice identified by S-NSSAI 3 is congested in TAs 1 to 3. In this case the AMF 70 may remove S-NSSAIs 2 and 3 from the Allowed NSSAI. And the AMF 70 may set S-NSSAI 2 associated with at least one of TA 1 and TA 2 to the Partially Allowed NSSAI. And the AMF 70 may set S-NSSAI 3 associated with at least TA 4 to the Rejected S-NSSAIs partially in the RA. For example, in a case where TAI 1 identifies TA 1 and TAI 2 identifies TA 2, S-NSSAI 2 may be associated with at least one of TAI 1 and TAI 2. For example, in a case where TAI 4 identifies TA 4, S-NSSAI 3 may be associated with at least TAI 4.　　For example, in this disclosure, the AMF 70 may set, based on at least one of the received network slice information, an operator's policy and a local configuration in the AMF 70, S-NSSAI(s) that the AMF 70 allows to keep using for the UE 3 in specific TA(s) to the Partially Allowed NSSAI.　　For example, in this disclosure, the AMF 70 may set, based on at least one of the received network slice information, an operator's policy and a local configuration in the AMF 70, S-NSSAI(s) which is allowed to use or available if the UE 3 performs, in specific TA(s), a new Registration procedure for the S-NSSAI(s) or performs, in specific TA(s), a Registration procedure for the S-NSSAI(s) again to the Rejected S-NSSAIs partially in the RA.　　For example, it assumes a case where the RA includes TAs 1 to 4 and the AMF 70 has sent the Allowed NSSAI including S-NSSAIs 1, 2 and 3 to the UE 3 and the AMF 70 stores the Allowed NSSAI. And it assumes a case where the received restricted area indicates that a network slice identified by S-NSSAI 2 is restricted or not available in TAs 3 and 4 and a network slice identified by S-NSSAI 3 is restricted or not available in TAs 1 to 3. In this case the AMF 70 may remove S-NSSAIs 2 and 3 from the Allowed NSSAI. And the AMF 70 may set S-NSSAI 2 associated with at least one of TA 1 and TA 2 to the Partially Allowed NSSAI. And the AMF 70 may set S-NSSAI 3 associated with at least TA 4 to the Rejected S-NSSAIs partially in the RA. For example, in a case where TAI 1 identifies TA 1 and TAI 2 identifies TA 2, S-NSSAI 2 may be associated with at least one of TAI 1 and TAI 2. For example, in a case where TAI 4 identifies TA 4, S-NSSAI 3 may be associated with at least TAI 4.　　The received restricted area indicating a network slice identified by S-NSSAI(s) is restricted or is not available in specific TA(s) may indicate the network slice identified by the S-NSSAI(s) is allowed or is available except for the specific TA(s).　　The received restricted area indicating a network slice identified by S-NSSAI 2 is restricted or is not available in TAs 1 and 2 may indicate a network slice identified by S-NSSAI 2 is allowed or is available in TAs 3 and 4.　　For example, it assumes a case where the RA includes TAs 1 to 4 and the AMF 70 has sent the Allowed NSSAI including S-NSSAIs 1, 2 and 3 to the UE 3 and the AMF 70 stores the Allowed NSSAI. And it assumes a case where the received allowed area indicates that a network slice identified by S-NSSAI 1 is allowed or is available in TAs 1 to 4, a network slice identified by S-NSSAI 2 is allowed or is available in TAs 1 and 2 and a network slice identified by S-NSSAI 3 is allowed or is available in TA 4. In this case the AMF 70 may remove S-NSSAIs 2 and 3 from the Allowed NSSAI. And the AMF 70 may set S-NSSAI 2 associated with at least one of TA 1 and TA 2 to the Partially Allowed NSSAI. And the AMF 70 may set S-NSSAI 3 associated with at least TA 4 to the Rejected S-NSSAIs partially in the RA. For example, in a case where TAI 1 identifies TA 1 and TAI 2 identifies TA 2, S-NSSAI 2 may be associated with at least one of TAI 1 and TAI 2. For example, in a case where TAI 4 identifies TA 4, S-NSSAI 3 may be associated with at least TAI 4.　　The received allowed area indicating a network slice identified by S-NSSAI(s) is allowed or is available in specific TA(s) may indicate the network slice identified by the S-NSSAI(s) is not allowed or is restricted or is not available except for the specific TA(s).　　The received allowed area indicating a network slice identified by S-NSSAI 2 is allowed or is available in TAs 1 and 2 may indicate a network slice identified by S-NSSAI 2 is not allowed or is restricted or is not available in TAs 3 and 4.　　For example, in a case where the received available time period information indicates from 9 AM to 5 PM and the current time is in 9 AM to 5 PM, the AMF 70 may consider at least one of the received congestion level, the restricted area and the allowed area. For example, in a case where the current time is in 9 AM to 5 PM, the AMF 70 may perform the above process(es) for deciding to update the Allowed NSSAI and to set S-NSSAI(s) to at least one of the Partially Allowed NSSAI and the Rejected S-NSSAIs partially.　　For example, it assumes a case where the RA includes TAs 1 to 4 and the AMF 70 has sent the Allowed NSSAI including S-NSSAIs 1, 2 and 3 to the UE 3 and the AMF 70 stores the Allowed NSSAI. And it assumes a case where the received available time period information indicates that a network slice identified by S-NSSAI 1 is allowed or is available in TAs 1 to 4 from 9 AM to 5 PM, a network slice identified by S-NSSAI 2 is allowed or is available in TAs 1 and 2 from 9 AM to 5 PM and a network slice identified by S-NSSAI 3 is allowed or is available in TA 4 from 9 AM to 5 PM. In this case, as long as the current time is in from 9 AM to 5 PM, the AMF 70 may remove S-NSSAIs 2 and 3 from the Allowed NSSAI. And the AMF 70 may set S-NSSAI 2 associated with at least one of TA 1 and TA 2 to the Partially Allowed NSSAI. And the AMF 70 may set S-NSSAI 3 associated with at least TA 4 to the Rejected S-NSSAIs partially in the RA. For example, in a case where TAI 1 identifies TA 1 and TAI 2 identifies TA 2, S-NSSAI 2 may be associated with at least one of TAI 1 and TAI 2. For example, in a case where TAI 4 identifies TA 4, S-NSSAI 3 may be associated with at least TAI 4.　　For example, in a case where the Allowed NSSAI which is sent by the AMF 70 to the UE 3 includes S-NSSAIs 1 to 4 and the above-mentioned network slice information indicates that S-NSSAI 4 is not available in the RA (i.e., S-NSSAI 4 is not available in all TA(s) of the RA), the AMF 70 may remove S-NSSAI 4 from the Allowed NSSAI and set S-NSSAI 4 to the Rejected NSSAI.　　For example, the AMF 70 may determine at least one of the Partially Allowed NSSAI and the Rejected S-NSSAI partially based on the information received from the NWDAF 74.　　Step 4. Once the AMF 70 decides updating UE configuration is needed at the decision in step 3, the AMF 70 sends a UE Configuration Update Command message to the UE 3 including at least one of the updated Allowed NSSAI, the updated Rejected NSSAI, the updated Partially Allowed NSSAI, the updated Rejected S-NSSAIs partially in the RA and other existing information.　　For example, in a case where the AMF 70 decides to update the Allowed NSSAI and the Rejected NSSAI, and decides to set S-NSSAI(s) to at least one of the Partially Allowed NSSAI and the Rejected S-NSSAIs partially in step 3, the AMF 70 may send, to the UE 3, the UE Configuration Update Command message including at least one of the updated Allowed NSSAI, the updated Rejected NSSAI, the Partially Allowed NSSAI and the Rejected S-NSSAIs partially.　　For example, the AMF 70 may send, to the UE 3, the UE Configuration Update Command message including at least one of the Allowed NSSAI, the Rejected NSSAI, the Partially Allowed NSSAI and the Rejected S-NSSAIs partially which are updated or generated or set or configured in step 3.　　For example, the AMF 70 may send the UE Configuration Update Command message to the UE 3 in a case where the AMF 70 receives the Partial Network Slice Availability support from the UE 3. See step 1 in Fig. 1 for definition of the Partial Network Slice Availability support indication.　　Step 5. Upon reception of the UE Configuration Update Command message from the AMF 70, the UE 3 stores at least one of the Allowed NSSAI, the Rejected NSSAI, the Partially Allowed NSSAI, the Rejected S-NSSAIs partially in the RA and other received information in step 4. The UE 3 may store the received information to non-volatile memories in the UE 3.　　Step 6. The UE 3 sends the UE Configuration Update Complete message to the AMF 70.Variant 1 of Third example of the First Aspect:　　In step 3, the AMF 70 may decide to update the UE configuration in the UE 3 when next Registration procedure (for example, mobility registration procedure) takes place. In this case, Partially Allowed NSSAI, Rejected S-NSSAIs partially in the RA and other information needed to be updated in the UE 3 decided by the AMF 70 based on input from the NWDAF 74 is reflected at the step 7 in Fig. 1.　　For example, in step 7 of Fig. 1, the AMF 70 may decide the RA, the Allowed NSSAI, Rejected NSSAI, the Partially Allowed NSSAI, the Rejected S-NSSAIs partially in the RA based on the network slice information from the NWDAF 74 mentioned in step 2 of Fig. 3.　　For example, in step 7 of Fig. 1, the AMF 70 may decide the RA, the Allowed NSSAI, Rejected NSSAI, the Partially Allowed NSSAI, the Rejected S-NSSAIs partially in the RA based on at least one of the information from the NSSF 76 mentioned in step 6 of Fig. 1, the information from the PCF 73 mentioned in step 4 of Fig. 2 and the network slice information from the NWDAF 74 mentioned in step 2 of Fig. 3.　　For example, the AMF 70 may consider the information received from the NWDAF 74 during the Registration procedure. For example, in a case where the AMF 70 receives the Registration Request message from the UE 3 and the network slice information from the NWDAF 74 is available, the AMF 70 may perform the same procedure in step 3 of Fig. 3. Then the AMF 70 may send the Registration Accept message including at least one of the Allowed NSSAI, the Rejected NSSAI, the Partially Allowed NSSAI and the Rejected S-NSSAIs partially which are updated or generated or set or configured in step 3 of Fig. 3.　　According to at least one of Third example of the First Aspect and the variant in the Third example, it can solve the above-mentioned problem.　　For example, at least one of Third example of the First Aspect and the variant in the Third example can solve the problem that regarding the decision by the AMF based on the AMF local policy, there are some problems.　　For example, at least one of Third example of the First Aspect and the variant in the Third example can solve the problem that, that only the AMF is able to perform the above decision based on the AMF local policy may make unnecessary limitation for the 5G system.　　For example, according to at least one of Third example of the First Aspect and the variant in the Third example, the NWDAF 74 can send information for determining at least one of the Partially Allowed NSSAI and the Rejected S-NSSAIs partially in the RA. Therefore, it can solve the above-mentioned problem.　　For example, the disclosure includes process(es) for determining at least one of the Partially Allowed NSSAI and the Rejected S-NSSAIs partially in the RA. For example, in a case where one node in this disclosure determines at least one of the Partially Allowed NSSAI and the Rejected S-NSSAIs partially in the RA, the one node may use the process(es) performed by another node for determining at least one of the Partially Allowed NSSAI and the Rejected S-NSSAIs partially in the RA. For example, the one node may store information which is used by the another node and for determining at least one of the Partially Allowed NSSAI and the Rejected S-NSSAIs partially in the RA. For example, the NSSF 76 in Fig. 1 may store the information which is used by the PCF 73 in Fig. 2 and for determining at least one of the Partially Allowed NSSAI and the Rejected S-NSSAIs partially in the RA and may determine, based on the information, at least one of the Partially Allowed NSSAI and the Rejected S-NSSAIs partially in the RA in the same manner as the PCF 73 in Fig. 2. For example, the information may be provided to the NSSF 76 in advance (e.g., the NSSF 76 may store the information in advance). For example, the NSSF 76 may receive the information from other communication apparatus (including e.g., the PCF 73) in advance.System overview　　Fig. 4 schematically illustrates a telecommunication system 1 for a mobile (cellular or wireless) to which the above aspects are applicable.　　The telecommunication system 1 represents a system overview in which an end to end communication is possible. For example, UE 3 (or user equipment, 'mobile device' 3) communicates with other UEs 3 or service servers in the data network 20 via respective (R)AN nodes 5 and a core network 7.　　The (R)AN node 5 supports any radio accesses including a 5G radio access technology (RAT), an E-UTRA radio access technology, a beyond 5G RAT, a 6G RAT and non-3GPP RAT including wireless local area network (WLAN) technology as defined by the Institute of Electrical and Electronics Engineers (IEEE).　　The (R)AN node 5 may split into a Radio Unit (RU), Distributed Unit (DU) and Centralized Unit (CU). In some aspects, each of the units may be connected to each other and structure the (R)AN node 5 by adopting an architecture as defined by the Open RAN (O-RAN) Alliance, where the units above are referred to as O-RU, O-DU and O-CU respectively.　　The (R)AN node 5 may be split into control plane function and user plane function. Further, multiple user plane functions can be allocated to support a communication. In some aspects, user traffic may be distributed to multiple user plane functions and user traffic over each user plane functions are aggregated in both the UE 3 and the (R)AN node 5. This split architecture may be called as 'dual connectivity' or 'Multi connectivity'.　　The (R)AN node 5 can also support a communication using the satellite access. In some aspects, the (R)AN node 5 may support a satellite access and a terrestrial access.　　In addition, the (R)AN node 5 can also be referred as an access node for a non-wireless access. The non-wireless access includes a fixed line access as defined by the Broadband Forum (BBF) and an optical access as defined by the Innovative Optical and Wireless Network (IOWN).　　The core network 7 may include logical nodes (or 'functions') for supporting a communication in the telecommunication system 1. For example, the core network 7 may be 5G Core Network (5GC) that includes, amongst other functions, control plane functions and user plane functions. Each function in logical nodes can be considered as a network function. The network function may be provided to another node by adapting the Service Based Architecture (SBA).　　A Network Function can be deployed as distributed, redundant, stateless, and scalable that provides the services from several locations and several execution instances in each location by adapting the network virtualization technology as defined by the European Telecommunications Standards Institute, Network Functions Virtualization (ETSI NFV).The core network 7 may support the Non-Public Network (NPN). The NPN may be a Stand-alone Non-Public Network (SNPN) or a Public Network Integrated NPN (PNI-NPN).　　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.　　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, and a Network Slice Selection Function (NSSF) 76. 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, and PCF 73 for the roaming-out UE 3.　　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.　　The "Uu" interface may include a Control plane of Uu interface and User plane of Uu interface.　　The User plane of Uu interface is responsible to convey user traffic between the UE 3 and a serving (R)AN node 5. The User plane of Uu interface may have a layered structure with SDAP, PDCP, RLC and MAC sublayer over the physical connection.　　The Control plane of Uu interface is responsible to establish, modify and release a connection between the UE 3 and a serving (R)AN node 5. The Control plane of Uu interface may have a layered structure with RRC, PDCP, RLC and MAC sublayers over the physical connection.　　For example, the following messages are communicated over the RRC layer to support AS signaling.　　・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, mobilityState, ng-5G-S-TMSI-Part2, registeredAMF, selectedPLMN-Identity　　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.User equipment (UE)　　Fig. 5 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.　　The UE 3 may, for example, support the Non-Public Network (NPN), The NPN may be a Stand-alone Non-Public Network (SNPN) or a Public Network Integrated NPN (PNI-NPN).　　The UE 3 may, for example, be an item of equipment for production or manufacture and / or an item of energy related machinery (for example equipment or machinery such as: boilers; engines; turbines; solar panels; wind turbines; hydroelectric generators; thermal power generators; nuclear electricity generators; batteries; nuclear systems and / or associated equipment; heavy electrical machinery; pumps including vacuum pumps; compressors; fans; blowers; oil hydraulic equipment; pneumatic equipment; metal working machinery; manipulators; robots and / or their application systems; tools; molds or dies; rolls; conveying equipment; elevating equipment; materials handling equipment; textile machinery; sewing machines; printing and / or related machinery; paper converting machinery; chemical machinery; mining and / or construction machinery and / or related equipment; machinery and / or implements for agriculture, forestry and / or fisheries; safety and / or environment preservation equipment; tractors; precision bearings; chains; gears; power transmission equipment; lubricating equipment; valves; pipe fittings; and / or application systems for any of the previously mentioned equipment or machinery etc.).　　The UE 3 may, for example, be an item of transport equipment (for example transport equipment such as: rolling stocks; motor vehicles; motor cycles; bicycles; trains; buses; carts; rickshaws; ships and other watercraft; aircraft; rockets; satellites; drones; balloons etc.).The UE 3 may, for example, be an item of information and communication equipment (for example information and communication equipment such as: electronic computer and related equipment; communication and related equipment; electronic components etc.).　　The UE 3 may, for example, be a refrigerating machine, a refrigerating machine applied product, an item of trade and / or service industry equipment, a vending machine, an automatic service machine, an office machine or equipment, a consumer electronic and electronic appliance (for example a consumer electronic appliance such as: audio equipment; video equipment; a loud speaker; a radio; a television; a microwave oven; a rice cooker; a coffee machine; a dishwasher; a washing machine; a dryer; an electronic fan or related appliance; a cleaner etc.).　　The UE 3 may, for example, be an electrical application system or equipment (for example an electrical application system or equipment such as: an x-ray system; a particle accelerator; radio isotope equipment; sonic equipment; electromagnetic application equipment; electronic power application equipment etc.).　　The UE 3 may, for example, be an electronic lamp, a luminaire, a measuring instrument, an analyzer, a tester, or a surveying or sensing instrument (for example a surveying or sensing instrument such as: a smoke alarm; a human alarm sensor; a motion sensor; a wireless tag etc.), a watch or clock, a laboratory instrument, optical apparatus, medical equipment and / or system, a weapon, an item of cutlery, a hand tool, or the like.　　The UE 3 may, for example, be a wireless-equipped personal digital assistant or related equipment (such as a wireless card or module designed for attachment to or for insertion into another electronic device (for example a personal computer, electrical measuring machine)).The UE 3 may be a device or a part of a system that provides applications, services, and solutions described below, as to "internet of things (IoT)", using a variety of wired and / or wireless communication technologies.　　Internet of Things devices (or "things") may be equipped with appropriate electronics, software, sensors, network connectivity, and / or the like, which enable these devices to collect and exchange data with each other and with other communication devices. IoT devices may comprise automated equipment that follow software instructions stored in an internal memory. IoT devices may operate without requiring human supervision or interaction. IoT devices might also remain stationary and / or inactive for a long period of time. IoT devices may be implemented as a part of a (generally) stationary apparatus. IoT devices may also be embedded in non-stationary apparatus (e.g. vehicles) or attached to animals or persons to be monitored / tracked.It will be appreciated that IoT technology can be implemented on any communication devices that can connect to a communications network for sending / receiving data, regardless of whether such communication devices are controlled by human input or software instructions stored in memory.　　It will be appreciated that IoT devices are sometimes also referred to as Machine-Type Communication (MTC) devices or Machine-to-Machine (M2M) communication devices or Narrow Band-IoT UE (NB-IoT UE). It will be appreciated that a UE 3 may support one or more IoT or MTC applications.　　The UE 3 may be a smart phone or a wearable device (e.g. smart glasses, a smart watch, a smart ring, or a hearable device).　　The UE 3 may be a car, or a connected car, or an autonomous car, or a vehicle device, or a motorcycle or V2X (Vehicle to Everything) communication module (e.g. Vehicle to Vehicle communication module, Vehicle to Infrastructure communication module, Vehicle to People communication module and Vehicle to Network communication module).(R)AN node　　Fig. 6 is a block diagram illustrating the main components of an exemplary (R)AN node 5, for example a base station ('eNB' in LTE, 'gNB' in 5G, a base station for 5G beyond, a base station for 6G). As shown, the (R)AN node 5 includes a transceiver circuit 51 which is operable to transmit signals to and to receive signals from connected UE(s) 3 via one or more antennas 52 and to transmit signals to and to receive signals from other network nodes (either directly or indirectly) via a network interface 53. A controller 54 controls the operation of the (R)AN node 5 in accordance with software stored in a memory 55. Software may be pre-installed in the memory and / or may be downloaded via the telecommunication network or from a removable data storage device (RMD), for example. The software includes, among other things, an operating system 551 and a communications control module 552 having at least a transceiver control module 5521.　　The communications control module 552 (using its transceiver control sub-module) is responsible for handling (generating / sending / receiving) signalling between the (R)AN node 5 and other nodes, such as the UE 3, another (R)AN node 5, the AMF 70 and the UPF 72 (e.g. directly or indirectly). The signalling may include, for example, appropriately formatted signalling messages relating to a radio connection and a connection with the core network 7 (for a particular UE 3), and in particular, relating to connection establishment and maintenance (e.g. RRC connection establishment and other RRC messages), NG Application Protocol (NGAP) messages (i.e. messages by N2 reference point) and Xn application protocol (XnAP) messages (i.e. messages by Xn reference point), etc. Such signalling may also include, for example, broadcast information (e.g. Master Information and System information) in a sending case.The controller 54 is also configured (by software or hardware) to handle related tasks such as, when implemented, UE mobility estimate and / or moving trajectory estimation.　　The (R)AN node 5 may support the Non-Public Network (NPN). The NPN may be a Stand-alone Non-Public Network (SNPN) or a Public Network Integrated NPN (PNI-NPN).The (R)AN node 5 may be expressed as a RAN node, RAN, (R)AN etc.System overview of (R)AN node 5 based on O-RAN architecture　　Fig. 7 schematically illustrates a (R)AN node 5 based on O-RAN architecture to which the (R)AN node 5 aspects are applicable.　　The (R)AN node 5 based on O-RAN architecture represents a system overview in which the (R)AN node is split into a Radio Unit (RU) 60, Distributed Unit (DU) 61 and Centralized Unit (CU) 62. In some aspects, each unit may be combined. For example, the RU 60 can be integrated / combined with the DU 61 as an integrated / combined unit, the DU 61 can be integrated / combined with the CU 62 as another integrated / combined unit. Any functionality in the description for a unit (e.g. one of RU 60, DU 61 and CU 62) can be implemented in the integrated / combined unit above. Further, CU 62 can separate into two functional units such as CU Control plane (CP) and CU User plane (UP). The CU CP has a control plane functionality in the (R)AN node 5. The CU UP has a user plane functionality in the (R)AN node 5. Each CU CP is connected to the CU UP via an appropriate interface (such as the so-called "E1" interface and / or the like).　　The UE 3 and a respective serving RU 60 are connected via an appropriate air interface (for example the so-called "Uu" interface and / or the like). Each RU 60 is connected to the DU 61 via an appropriate interface (such as the so-called "Front haul", "Open Front haul", "F1" interface and / or the like). Each DU 61 is connected to the CU 62 via an appropriate interface (such as the so-called "Mid haul", "Open Mid haul", "E2" interface and / or the like). Each CU 62 is also connected to nodes in the core network 7 (such as the so-called core network nodes) via an appropriate interface (such as the so-called "Back haul", "Open Back haul", "N2" / "N3" interface(s) and / or the like). In addition, a user plane part of the DU 61 can also be connected to the core network nodes 7 via an appropriate interface (such as the so-called "N3" interface(s) and / or the like).　　Depending on functionality split among the RU 60, DU 61 and CU 62, each unit provides some of the functionality that is provided by the (R)AN node 5. For example, the RU 60 may provide 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.Radio Unit (RU)　　Fig. 8 is a block diagram illustrating the main components of an exemplary RU 60, for example a RU part of base station ('eNB' in LTE, 'gNB' in 5G, a base station for 5G beyond, a base station for 6G). As shown, the RU 60 includes a transceiver circuit 601 which is operable to transmit signals to and to receive signals from connected UE(s) 3 via one or more antennas 602 and to transmit signals to and to receive signals from other network nodes or network unit (either directly or indirectly) via a network interface 603. A controller 604 controls the operation of the RU 60 in accordance with software stored in a memory 605. Software may be pre-installed in the memory and / or may be downloaded via the telecommunication network or from a removable data storage device (RMD), for example. The software includes, among other things, an operating system 6051 and a communications control module 6052 having at least a transceiver control module 60521.　　The communications control module 6052 (using its transceiver control sub-module) is responsible for handling (generating / sending / receiving) signalling between the RU 60 and other nodes or units, such as the UE 3, another RU 60 and DU 61 (e.g. directly or indirectly). The signalling may include, for example, appropriately formatted signalling messages relating to a radio connection and a connection with the RU 60 (for a particular UE 3), and in particular, relating to MAC layer and RLC layer.　　The controller 604 is also configured (by software or hardware) to handle related tasks such as, when implemented, UE mobility estimate and / or moving trajectory estimation.　　The RU 60 may support the Non-Public Network (NPN). The NPN may be a Stand-alone Non-Public Network (SNPN) or a Public Network Integrated NPN (PNI-NPN).　　As described above, the RU 60 can be integrated / combined with the DU 61 as an integrated / combined unit. Any functionality in the description for the RU 60 can be implemented in the integrated / combined unit above.Distributed Unit (DU)　　Fig. 9 is a block diagram illustrating the main components of an exemplary DU 61, for example a DU part of a base station ('eNB' in LTE, 'gNB' in 5G, a base station for 5G beyond, a base station for 6G). As shown, the apparatus includes a transceiver circuit 611 which is operable to transmit signals to and to receive signals from other nodes or units (including the RU 60) via a network interface 612. A controller 613 controls the operation of the DU 61 in accordance with software stored in a memory 614. Software may be pre-installed in the memory 614 and / or may be downloaded via the telecommunication network or from a removable data storage device (RMD), for example. The software includes, among other things, an operating system 6141 and a communications control module 6142 having at least a transceiver control module 61421. The communications control module 6142 (using its transceiver control module 61421 is responsible for handling (generating / sending / receiving) signalling between the DU 61 and other nodes or units, such as the RU 60 and other nodes and units.　　The DU 61 may support the Non-Public Network (NPN). The NPN may be a Stand-alone Non-Public Network (SNPN) or a Public Network Integrated NPN (PNI-NPN).　　As described above, the RU 60 can be integrated / combined with the DU 61 or CU 62 as an integrated / combined unit. Any functionality in the description for DU 61 can be implemented in one of the integrated / combined unit above.Centralized Unit (CU)　　Fig. 10 is a block diagram illustrating the main components of an exemplary CU 62, for example a CU part of base station ('eNB' in LTE, 'gNB' in 5G, a base station for 5G beyond, a base station for 6G). As shown, the apparatus includes a transceiver circuit 621 which is operable to transmit signals to and to receive signals from other nodes or units (including the DU 61) via a network interface 622. A controller 623 controls the operation of the CU 62 in accordance with software stored in a memory 624. Software may be pre-installed in the memory 624 and / or may be downloaded via the telecommunication network or from a removable data storage device (RMD), for example. The software includes, among other things, an operating system 6241 and a communications control module 6242 having at least a transceiver control module 62421. The communications control module 6242 (using its transceiver control module 62421 is responsible for handling (generating / sending / receiving) signalling between the CU 62 and other nodes or units, such as the DU 61 and other nodes and units.　　The CU 62 may support the Non-Public Network (NPN). The NPN may be a Stand-alone Non-Public Network (SNPN) or a Public Network Integrated NPN (PNI-NPN).　　As described above, the CU 62 can be integrated / combined with the DU 61 as an integrated / combined unit. Any functionality in the description for the CU 62 can be implemented in the integrated / combined unit above.AMF　　Fig. 11 is a block diagram illustrating the main components of the AMF 70. As shown, the apparatus includes a transceiver circuit 701 which is operable to transmit signals to and to receive signals from other nodes (including the UE 3, the NSSF 76) via a network interface 702. A controller 703 controls the operation of the AMF 70 in accordance with software stored in a memory 704. Software may be pre-installed in the memory 704 and / or may be downloaded via the telecommunication network or from a removable data storage device (RMD), for example. The software includes, among other things, an operating system 7041 and a communications control module 7042 having at least a transceiver control module 70421. The communications control module 7042 (using its transceiver control module 70421 is responsible for handling (generating / sending / receiving) signalling between the AMF 70 and other nodes, such as the UE 3 (e.g. via the (R)AN node 5) and other core network nodes (including core network nodes in the HPLMN of the UE 3 when the UE 3 is roaming-in. Such signalling may include, for example, appropriately formatted signalling messages (e.g. a registration request message and associated response messages) relating to access and mobility management procedures (for the UE 3).　　The AMF 70 may support the Non-Public Network (NPN). The NPN may be a Stand-alone Non-Public Network (SNPN) or a Public Network Integrated NPN (PNI-NPN).PCF　　Fig. 12 is a block diagram illustrating the main components of the PCF 73. As shown, the apparatus includes a transceiver circuit 731 which is operable to transmit signals to and to receive signals from other nodes (including the AMF 70) via a network interface 732. A controller 733 controls the operation of the PCF 73 in accordance with software stored in a memory 734. Software may be pre-installed in the memory 734 and / or may be downloaded via the telecommunication network or from a removable data storage device (e.g. a removable memory device (RMD)), for example. The software includes, among other things, an operating system 7341 and a communications control module 7342 having at least a transceiver control module 73421. The communications control module 7342 (using its transceiver control module 73421 is responsible for handling (generating / sending / receiving) signalling between the PCF 73 and other nodes, such as the AMF 70 and other core network nodes (including core network nodes in the HPLMN of the UE 3 when the UE 3 is roaming-in. Such signalling may include, for example, appropriately formatted signalling messages (e.g. a HTTP restful methods based on the service based interfaces) relating to policy management procedures (for the UE 3).　　The PCF 73 may support the Non-Public Network (NPN). The NPN may be a Stand-alone Non-Public Network (SNPN) or a Public Network Integrated NPN (PNI-NPN).NWDAF　　Fig. 13 is a block diagram illustrating the main components of the NWDAF 74. As shown, the apparatus includes a transceiver circuit 741 which is operable to transmit signals to and to receive signals from other nodes (including the AMF 70 and the UDM 75) via a network interface 742. A controller 743 controls the operation of the NWDAF 74 in accordance with software stored in a memory 744. Software may be pre-installed in the memory 744 and / or may be downloaded via the telecommunication network or from a removable data storage device (e.g. a removable memory device (RMD)), for example. The software includes, among other things, an operating system 7441 and a communications control module 7442 having at least a transceiver control module 74421. The communications control module 7442 (using its transceiver control module 74421 is responsible for handling (generating / sending / receiving) signalling between the NWDAF 74 and other nodes, such as the AMF 70 and other core network nodes (including core network nodes in the HPLMN of the UE 3 when the UE 3 is roaming-in. Such signalling may include, for example, appropriately formatted signalling messages (e.g. a HTTP restful methods based on the service based interfaces) relating to policy management procedures (for the UE 3).　　The NWDAF 74 may support the Non-Public Network (NPN). The NPN may be a Stand-alone Non-Public Network (SNPN) or a Public Network Integrated NPN (PNI-NPN).UDM　　Fig. 14 is a block diagram illustrating the main components of the UDM 75. As shown, the apparatus includes a transceiver circuit 751 which is operable to transmit signals to and to receive signals from other nodes (including the AMF 70) via a network interface 752. A controller 753 controls the operation of the UDM 75 in accordance with software stored in a memory 754. Software may be pre-installed in the memory 754 and / or may be downloaded via the telecommunication network or from a removable data storage device (RMD), for example. The software includes, among other things, an operating system 7541 and a communications control module 7542 having at least a transceiver control module 75421. The communications control module 7542 (using its transceiver control module 75421 is responsible for handling (generating / sending / receiving) signalling between the UDM 75 and other nodes, such as the AMF 70 and other core network nodes (including core network nodes in the VPLMN of the UE 3 when the UE 3 is roaming-out. Such signalling may include, for example, appropriately formatted signalling messages (e.g. a HTTP restful methods based on the service based interfaces) relating to mobility management procedures (for the UE 3).　　The UDM 75 may support the Non-Public Network (NPN). The NPN may be a Stand-alone Non-Public Network (SNPN) or a Public Network Integrated NPN (PNI-NPN).NSSF　　Fig. 15 is a block diagram illustrating the main components of the NSSF 76. As shown, the apparatus includes a transceiver circuit 761 which is operable to transmit signals to and to receive signals from other nodes (including the AMF 70) via a network interface 762. A controller 763 controls the operation of the NSSF 76 in accordance with software stored in a memory 764. Software may be pre-installed in the memory 764 and / or may be downloaded via the telecommunication network or from a removable data storage device (RMD), for example. The software includes, among other things, an operating system 7641 and a communications control module 7642 having at least a transceiver control module 76421. The communications control module 7642 (using its transceiver control module 76421 is responsible for handling (generating / sending / receiving) signalling between the NSSF 76 and other nodes, such as the AMF 70 and other core network nodes (including core network nodes in the VPLMN of the UE 3 when the UE 3 is roaming-out. Such signalling may include, for example, appropriately formatted signalling messages (e.g. a HTTP restful methods based on the service based interfaces) relating to mobility management procedures (for the UE 3).　　The NSSF 76 may support the Non-Public Network (NPN). The NPN may be a Stand-alone Non-Public Network (SNPN) or a Public Network Integrated NPN (PNI-NPN).　　Fig. 16 illustrates Registration with AMF re-allocation procedure. The whole or part of the example Aspects disclosed above can be described as, but not limited to, the following.4.2.2.2.3　　Registration with AMF re-allocation　　When an AMF receives a Registration request, the AMF may need to reroute the Registration request to another AMF, e.g. when the initial AMF is not the appropriate AMF to serve the UE. The Registration with AMF re-allocation procedure, described in figure 4.2.2.2.3-1, is used to reroute the NAS message of the UE to the target AMF during a Registration procedure.　　The initial AMF and the target AMF register their capability at the NRF.　　1. If the UE is in CM-IDLE State, steps 1 and 2 of figure 4.2.2.2.2-1 have occurred and the (R)AN sends the Registration request message within an Initial UE message to the initial AMF. If the UE is in CM-CONNECTED state and triggers registration procedure, the NG-RAN sends Registration request message in the Uplink NAS Transport message to the serving AMF which is initial AMF. The AMF may skip step 2-3.　　2. If the AMF needs the SUPI and / or UE's subscription information to decide whether to reroute the Registration Request or if the Registration Request was not sent integrity protected or integrity protection is indicated as failed, then AMF performs steps 4 to 9a or to 9b of figure 4.2.2.2.2-1.　　3a. [Conditional] If the initial AMF needs UE's subscription information to decide whether to reroute the Registration Request and UE's slice selection subscription information was not provided by old AMF, the AMF selects a UDM as described in clause 6.3.8 3TS 23.501 [2].　　3b. Initial AMF to UDM: Nudm_SDM_Get (SUPI, Slice Selection Subscription data).　　The initial AMF request UE's Slice Selection Subscription data from UDM by invoking the Nudm_SDM_Get (see clause 5.2.3.3.1) service operation. UDM may get this information from UDR by Nudr_DM_Query(SUPI, Slice Selection Subscription data).　　For a Disaster Roaming Registration, the AMF may provide the indication of Disaster Roaming service to the UDM.　　3c. UDM to initial AMF: Response to Nudm_SDM_Get. The AMF gets the Slice Selection Subscription data including Subscribed S-NSSAIs.　　UDM responds with slice selection subscription data to initial AMF.　　For a Disaster Roaming Registration, the UDM responds with the slice selection subscription data for a Disaster Roaming service to initial AMF based on the local policy and / or the local configuration as specified in clause 5.40.4 of 3TS 23.501 [2].　　4a. [Conditional] Initial AMF to NSSF: Nnssf_NSSelection_Get (Requested NSSAI, [Mapping Of Requested NSSAI], Subscribed S-NSSAI(s) with the default S-NSSAI indication, [NSSRG Information], TAI, Allowed NSSAI for the other access type (if any), [Mapping of Allowed NSSAI], PLMN ID of the SUPI, Partial Network Slice Availability support indication).　　If there is a need for slice selection, (see clause 5.15.5.2.1 of 3TS 23.501 [2]), e.g. the initial AMF cannot serve all the S-NSSAI(s) from the Requested NSSAI permitted by the subscription information, the initial AMF invokes the Nnssf_NSSelection_Get service operation from the NSSF by including Requested NSSAI, optionally Mapping Of Requested NSSAI, Subscribed S-NSSAIs with the default S-NSSAI indication, [NSSRG Information], Allowed NSSAI for the other access type (if any), Mapping of Allowed NSSAI, PLMN ID of the SUPI and the TAI of the UE. Partial Network Slice Availability support indication indicates to the NSSF that the UE supports handling of partially allowed NSSAI or partially rejected NSSAI.　　The AMF includes, if available, the NSSRG Information for the S-NSSAIs of the HPLMN, defined in clause 5.15.12 of 3TS 23.501 [2], including information whether the UE has indicated support of the subscription-based restrictions to simultaneous registration of network slices and whether the UDM has indicated to provide all subscribed S-NSSAIs for non-supporting UEs.　　4b. [Conditional] NSSF to Initial AMF: Response to Nnssf_NSSelection_Get (AMF Set or list of AMF addresses, Allowed NSSAI for the first access type, [Mapping Of Allowed NSSAI], [Allowed NSSAI for the second access type], [Mapping of Allowed NSSAI], [NSI ID(s)], [NRF(s)], [List of rejected (S-NSSAI(s), cause value(s))], [Configured NSSAI for the Serving PLMN], [Mapping Of Configured NSSAI], partially allowed NSSAI of the first access type and associated TAs of each S-NSSAI present in the partially allowed NSSAI or partially rejected NSSAI and for each S-NSSAI in the partially rejected NSSAI the list of TA supporting the S-NSSAI).　　The NSSF performs the steps specified in point (B) in clause 5.15.5.2.1 of 3TS 23.501 [2]. The NSSF returns to initial AMF the Allowed NSSAI for the first access type, optionally the Mapping Of Allowed NSSAI, the Allowed NSSAI for the second access type (if any), optionally the Mapping of Allowed NSSAI and the target AMF Set or, based on configuration, the list of candidate AMF(s). The NSSF may return NSI ID(s) associated to the Network Slice instance(s) corresponding to certain S-NSSAI(s). The NSSF may return the NRF(s) to be used to select NFs / services within the selected Network Slice instance(s). It may return also information regarding rejection causes for S-NSSAI(s) not included in the Allowed NSSAI. The NSSF may return Configured NSSAI for the Serving PLMN and possibly the associated mapping of the Configured NSSAI. If the NSSRG information was included in the request, the NSSF provides the Configured NSSAI as described in clause 5.15.12 of 3TS 23.501 [2].　　When the AMF receives Partial Network Slice Availability support indication and the one of the S-NSSAI in the requested NSSAI is not supported in the registration area, then the AMF sends the S-NSSAI in the partially allowed NSSAI and sends the associated TAs of the S-NSSAI to the AMF.　　NOTE: For each S-NSSAI in the partially allowed NSSAI, the NSSF gets list of supported TAIs from the UDM in an existing message or in a new message, or the AMF in an existing message or a new message.　　NOTE 1: The NRF(s) returned by the NSSF, if any, belong to any level of NRF (see clause 6.2.6 of 3TS 23.501 [2]) according to the deployment decision of the operator.　　5. [Conditional] Initial AMF to old AMF: Namf_Communication_RegistrationStatusUpdate (failure cause ).　　If the UE was in CM-IDLE and another AMF is selected, the initial AMF sends a reject indication to the old AMF telling that the UE Registration procedure did not fully complete at the initial AMF. The old AMF continues as if the Namf_Communication_UEContextTransfer had never been received.　　6a. [Conditional] Initial AMF to NRF: Nnrf_NFDiscovery_Request (NF type, AMF Set).　　If the initial AMF does not locally store the target AMF address and if the initial AMF intends to use direct reroute to target AMF or the reroute via (NG-R)AN message needs to include AMF address, then the initial AMF invokes the Nnrf_NFDiscovery_Request service operation from the NRF to find a proper target AMF which has required NF capabilities to serve the UE. The NF type is set to AMF. The AMF Set is included in the Nnrf_NFDiscovery_Request.　　6b. [Conditional] NRF to AMF: Response to Nnrf_NFDiscovery_Request (list of (AMF pointer, AMF address, plus additional selection rules and NF capabilities)).　　The NRF replies with the list of potential target AMF(s). The NRF may also provide the details of the services offered by the candidate AMF(s) along with the notification end-point for each type of notification service that the selected AMF had registered with the NRF, if available. As an alternative, it provides a list of potential target AMFs and their capabilities and optionally, additional selection rules. Based on the information about registered NFs and required capabilities, a target AMF is selected by the initial AMF.　　If the security association has been established between the UE and initial AMF, to avoid a registration failure, the initial AMF shall forward the NAS message to the target AMF by executing step 7(A).　　NOTE 2: The security context in the initial AMF is not transferred to the target AMF if initial AMF forward the NAS message to the target AMF via (R)AN. In this case the UE rejects the NAS message sent from target AMF as the security context in the UE and target AMF are not synchronized.　　NOTE 3: Network slice isolation cannot be completely maintained in case the AMF reallocation is executed by step 7(A).　　If the initial AMF is not part of the target AMF Set and is not able to get a list of candidate AMF(s) by querying the NRF with the target AMF Set (e.g. the NRF locally pre-configured on AMF does not provide the requested information, the query to the appropriate NRF provided by the NSSF is not successful, or the initial AMF has knowledge that the initial AMF is not authorized as serving AMF etc.) then the initial AMF shall forward the NAS message to the target AMF via (R)AN executing step 7(B) unless the security association has been established between the UE and initial AMF; the Allowed NSSAI and the AMF Set are included to enable the (R)AN to select the target AMF as described in clause 6.3.5 of 3TS 23.501 [2].　　7(A). If the initial AMF, based on local policy and subscription information, decides to forward the NAS message to the target AMF directly, the initial AMF invokes the Namf_Communication_N1MessageNotify to the target AMF, carrying the rerouted NAS message. The Namf_Communication_N1MessageNotify service operation includes AN access information (e.g. the information enabling (R)AN to identify the N2 terminating point, CAG Identifier(s) of the CAG cell) and the complete Registration Request message in clear text as specified in TS 33.501

[0015] and the UE's SUPI and MM Context if available. If the initial AMF has obtained the information from the NSSF as described at step 4b, that information except the AMF Set or list of AMF addresses is included. The target AMF then updates the (R)AN with a new updated N2 termination point for the UE in the first message from target AMF to RAN in step 8.　　7(B). [Conditional] if the UE was in CM-IDLE, if the initial AMF, based on local policy and subscription information, decides to forward the NAS message to the target AMF via (R)AN unless the target AMF(s) are returned from the NSSF and identified by a list of candidate AMF(s), the initial AMF sends a NGAP Reroute NAS Request message to the (R)AN (step 7a). The NGAP Reroute Request NAS message includes the information about the target AMF and the complete Registration Request message. If the initial AMF has obtained the information as described at step 4b, that information is included. The (R)AN sends the Initial UE message to the target AMF (step 7b) indicating reroute due to slicing including the information from step 4b that the NSSF provided.　　NOTE 4: Step 7B is not supported if the UE was in CM-CONNECTED i.e. the NGAP Uplink NAS Transport message was received at step 1.　　8. After receiving the Registration Request message transmitted at step 7(A)a or step 7(B)b, the target AMF continues with the Registration procedure from step 4 until 22 of figure 4.2.2.2.2-1 (with the target AMF corresponding to the new AMF), which includes the UE context retrieved from old AMF. If the 5G security context is received from the initial AMF, the target AMF continue using that one instead of the 5G security context the target AMF may have retrieved from the old AMF. If the initial AMF decides to forward the NAS message to the target AMF (step 7(A), the first message from the target AMF to (R)AN (either Initial Context Setup Request, or Downlink NAS Transport) contain the AMF name of the initial AMF and target AMF UE NGAP ID.5.2.16.2.1 Nnssf_NSSelection_Get service operation　　Service operation name: Nnssf_NSSelection_Get　　Description: This service operation enables Network Slice selection in both the Serving PLMN and HPLMN. It also enables the NSSF to provide to the AMF the Allowed NSSAI and the Configured NSSAI for the Serving PLMN. It allows also to provide the NSAG information which is applicable (clause 5.15.14 of 3TS 23.501 [2]).　　It may be invoked during Registration procedure, during inter-PLMN mobility procedure, during PDU Session Establishment procedure or during UE Configuration Update procedure. When invoked during Registration procedure it may possibly trigger AMF re-allocation. When invoked during PDU Session Establishment procedure it may be invoked in the VPLMN or in the HPLMN; if invoked in the VPLMN it returns the hNRF selected by the hNSSF and, if applicable, the value of the HPLMN NSI ID. When invoked during UE Configuration Update procedure or inter-PLMN mobility procedure it may be invoked in the Serving PLMN.　　NOTE 1: The list of events, which trigger invoking of the Nnssf_NSSelection_Get service operation, is not exhaustive.　　NOTE 2: The NSSF can determine the serving network and Access Type from the TAI, as described in TS 29.571

[0070] .　　Inputs, Required: None.　　Inputs, Conditional Required:　　If this service operation is invoked during Registration procedure for Network Slice selection or UE Configuration Update procedure, then the following inputs are required:　　　　- Subscribed S-NSSAI(s) with the indication if marked as default S-NSSAI, PLMN ID of the SUPI, TAI, NF type of the NF service consumer, Requester ID.　　If this service operation is invoked to derive the S-NSSAI for the serving PLMN (as described in clause 4.11.1.3.3), the following inputs are required:　　　　- S-NSSAIs for the HPLMN associated with established PDN connection, PLMN ID of the SUPI, NF type of the NF service consumer, Requester ID.　　If this service operation is invoked by target AMF during inter-PLMN mobility procedure, the following inputs are required:　　　　- S-NSSAIs for the HPLMN, PLMN ID of the SUPI, TAI.　　If this service operation is invoked during PDN Connection Establishment in the Serving PLMN in EPS by a SMF+PGW-C, the following inputs are required:　　　　- Subscribed S-NSSAIs for the UE, PLMN ID of the SUPI, NF type of the NF service consumer, Requester ID.　　If this service operation is invoked during PDU Session Establishment procedure in the Serving PLMN then the following inputs are required:　　　　- S-NSSAI, non-roaming / LBO roaming / HR roaming indication, PLMN ID of the SUPI, TAI, NF type of the NF service consumer, Requester ID.　　Inputs, Optional:　　If this service operation is invoked during Registration procedure for Network Slice selection or UE Configuration Update procedure, then the following inputs are provided if available:　　　　- Requested NSSAI, Mapping Of Requested NSSAI, Default Configured NSSAI Indication, NSSRG Information, UE support of subscription-based restrictions to simultaneous registration of network slice feature Indication, UDM indication to provide all subscribed S-NSSAIs for UEs not indicating support of subscription-based restrictions to simultaneous registration of network slices, Allowed NSSAI for current Access Type, Allowed NSSAI for the other Access Type and the corresponding Mapping Of Allowed NSSAIs for current Access Type and other Access Type, Rejected S-NSSAI(s) for RA, UE support of NSAG Information.　　If this service operation is invoked during PDU Session Establishment procedure, then the following input is optional:　　　　- HPLMN S-NSSAI that maps to the S-NSSAI from the Allowed NSSAI of the Serving PLMN.　　If the AMF gets Partial Network Slice Availability support indication from the UE, the AMF sends this information to the NSSF.　　Outputs, Conditional Required:　　If this service operation is invoked during Registration procedure for Network Slice selection or UE Configuration Update procedure, then one or more of the following outputs are required:　　　　- Allowed NSSAI, Configured NSSAI; Target AMF Set or, based on configuration, the list of candidate AMF(s).　　If this service operation is invoked during inter-PLMN mobility procedure, then one or more of the following outputs are required:　　　　- Allowed NSSAI.　　If this service operation is invoked to derive the S-NSSAI for the serving PLMN (as described in clause 4.11.1.3.3), the following output is required:　　　　- S-NSSAIs for the HPLMN associated with established PDN connection, Mapping of S-NSSAIs associated with established PDN connection in the Serving PLMN.　　If this service operation is invoked during PDN Connection Establishment in the Serving PLMN in EPS by a SMF+PGW-C, the following outputs are required:　　　　- Subscribed S-NSSAIs for the UE, Mapping of S-NSSAIs associated with the subscribed S-NSSAIs for the UE in the Serving PLMN.　　If this service operation is invoked during PDU Session Establishment procedure, then the following outputs are required:　　　　- The NRF to be used to select NFs / services within the selected Network Slice instance.　　Outputs, conditional Optional:　　If this service operation is invoked during UE Registration procedure or UE Configuration Update procedure, then one or more of the following outputs are optional:　　　　- Mapping Of Allowed NSSAI, Mapping Of Configured NSSAI, NSI ID(s) associated with the Network Slice instances of the Allowed NSSAI, NRF(s) to be used to select NFs / services within the selected Network Slice instance(s) and NRF to be used to determine the list of candidate AMF(s) from the AMF Set, rejected S-NSSAI with cause of rejection, Target NSSAI, the NSAG information (defined in clause 5.15.14 of 3TS 23.501 [2]).　　If this service operation is invoked during inter-PLMN mobility procedure, then the following output is optional:　　　　- Mapping Of Allowed NSSAI.　　If this service operation is invoked during PDU Session Establishment procedure, then the following output is optional:　　　　- NSI ID associated with the S-NSSAI provided in the input.　　If the service operation is invoked during the initial registration, mobility registration, inter PLMN mobility, or EPS to 5GS mobility, then the following output is optional　　　　- Partially allowed NSSAI or partially rejected NSSAI;　　　　- Associated TAIs for each S-NSSAI present in the partially allowed NSSAI or partially rejected NSSAI.Modifications and Alternatives　　Detailed aspects have been described above. As those skilled in the art will appreciate, a number of modifications and alternatives can be made to the above aspects whilst still benefiting from the disclosures embodied therein. By way of illustration only a number of these alternatives and modifications will now be described.　　In the above description, the UE 3 and the network apparatus are described for ease of understanding as having a number of discrete modules (such as the communication control modules). Whilst these modules may be provided in this way for certain applications, for example where an existing system has been modified to implement the disclosure, in other applications, for example in systems designed with the inventive features in mind from the outset, these modules may be built into the overall operating system or code and so these modules may not be discernible as discrete entities. These modules may also be implemented in software, hardware, firmware or a mix of these.　　Each controller may comprise any suitable form of processing circuitry including (but not limited to), for example: one or more hardware implemented computer processors; microprocessors; central processing units (CPUs); arithmetic logic units (ALUs); input / output (IO) circuits; internal memories / caches (program and / or data); processing registers; communication buses (e.g. control, data and / or address buses); direct memory access (DMA) functions; hardware or software implemented counters, pointers and / or timers; and / or the like.In the above aspects, a number of software modules were described. As those skilled in the art will appreciate, the software modules may be provided in compiled or un-compiled form and may be supplied to the UE 3 and the network apparatus as a signal over a computer network, or on a recording medium. Further, the functionality performed by part or all of this software may be performed using one or more dedicated hardware circuits. However, the use of software modules is preferred as it facilitates the updating of the UE 3 and the network apparatus in order to update their functionalities.　　In the above aspects, a 3GPP radio communications (radio access) technology is used. However, any other radio communications technology (e.g. WLAN, Wi-Fi, WiMAX, Bluetooth, etc.) and other fix line communications technology (e.g. BBF Access, Cable Access, optical access, etc.) may also be used in accordance with the above aspects.　　Items of user equipment might include, for example, communication devices such as mobile telephones, smartphones, user equipment, personal digital assistants, laptop / tablet computers, web browsers, e-book readers and / or the like. Such mobile (or even generally stationary) devices are typically operated by a user, although it is also possible to connect so-called 'Internet of Things' (IoT) devices and similar machine-type communication (MTC) devices to the network. For simplicity, the present application refers to mobile devices (or UEs) in the description but it will be appreciated that the technology described can be implemented on any communication devices (mobile and / or generally stationary) that can connect to a communications network for sending / receiving data, regardless of whether such communication devices are controlled by human input or software instructions stored in memory.Various other modifications will be apparent to those skilled in the art and will not be described in further detail here.　　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.　　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.　　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, registers, 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.　　The previous description of the disclosed examples is provided to enable any person skilled in the art to make or use the present disclosure. Various modifications to these examples will be readily apparent to those skilled in the art, and the generic principles defined herein may be applied to other examples without departing from the spirit or scope of the disclosure. Thus, the present disclosure is not intended to be limited to the examples shown herein but is to be accorded the widest scope consistent with the principles and novel features disclosed herein.　　While the disclosure has been particularly shown and described with reference to exemplary Aspects thereof, the disclosure is not limited to these Aspects. It will be understood by those of ordinary skill in the art that various changes in form and details may be made therein without departing from the spirit and scope of the present disclosure as defined by this document. For example, the Aspects above are not limited to 5GS, and the Aspects are also applicable to communication system other than 5GS (e.g., 6G system, 5G beyond system).Supplementary notes　　The whole or part of the example Aspects disclosed above can be described as, but not limited to, the following supplementary notes.　　(Supplementary note 1)　　A method of a first communication apparatus comprising:　　receiving at least one of Partially Allowed Network Slice Selection Assistance Information (NSSAI) and Rejected Single Network Slice Selection Assistance Information (S-NSSAI) partially from a second communication apparatus; and　　sending the at least one of the Partially Allowed NSSAI and the Rejected S-NSSAI partially to a user equipment (UE).　　(Supplementary note 2)　　The method according to supplementary note 1,　　wherein the sending the at least one of the Partially Allowed NSSAI and the Rejected S-NSSAI partially includes sending a Registration Accept message including the at least one of the Partially Allowed NSSAI and the Rejected S-NSSAI partially.　　(Supplementary note 3)　　The method according to supplementary note 1 or 2, further comprising:　　receiving information indicating that the UE is able to understand the at least one of the Partially Allowed NSSAI and the Rejected S-NSSAI partially; and　　sending the information to the second communication apparatus.　　(Supplementary note 4)　　The method according to supplementary note 3,　　wherein the receiving the at least one of the Partially Allowed NSSAI and the Rejected S-NSSAI partially includes receiving the at least one of the Partially Allowed NSSAI and the Rejected S-NSSAI partially in a case of the sending the information to the second communication apparatus.　　(Supplementary note 5)　　The method according to supplementary note 3 or 4,　　wherein the receiving the information includes receiving a Registration Request message including the information, and　　wherein the sending the information includes sending an Nnssf_NSSelection_Get message including the information.　　(Supplementary note 6)　　The method according to any one of supplementary notes 1 to 5,　　wherein the receiving the at least one of the Partially Allowed NSSAI and the Rejected S-NSSAI partially includes receiving an Nnssf_NSSelection_Get Response message including the at least one of the Partially Allowed NSSAI and the Rejected S-NSSAI partially.　　(Supplementary note 7)　　The method according to any one of supplementary notes 1 to 6,　　wherein the first communication apparatus is an Access and Mobility Management Function (AMF), and　　wherein the second communication apparatus is a Network Slice Selection Function (NSSF).　　(Supplementary note 8)　　The method according to supplementary note 3 or 4,　　wherein the receiving the information includes receiving a Registration Request message including the information, and　　wherein the sending the information includes sending an Npcf_AMPolicyControl_Create message including the information.　　(Supplementary note 9)　　The method according to any one of supplementary notes 1 to 4 and 8,　　wherein the receiving the at least one of the Partially Allowed NSSAI and the Rejected S-NSSAI partially includes receiving an Npcf_AMPolicyControl_Create Response message including the at least one of the Partially Allowed NSSAI and the Rejected S-NSSAI partially.　　(Supplementary note 10)　　The method according to any one of supplementary notes 1 to 4, 8 and 9,　　wherein the first communication apparatus is an Access and Mobility Management Function (AMF), and　　wherein the second communication apparatus is a Policy Control Function (PCF).　　(Supplementary note 11)　　A method of a first communication apparatus comprising:　　receiving, from a second communication apparatus, information for determining at least one of Partially Allowed Network Slice Selection Assistance Information (NSSAI) and Rejected Single Network Slice Selection Assistance Information (S-NSSAI) partially;　　determining the at least one of the Partially Allowed NSSAI and the Rejected S-NSSAI partially; and　　sending the at least one of the Partially Allowed NSSAI and the Rejected S-NSSAI partially to a user equipment (UE).　　(Supplementary note 12)　　The method according to supplementary note 11,　　wherein the receiving the information includes receiving an Nnwdaf_SliceInformation Notification message including the information, and　　wherein the sending the at least one of the Partially Allowed NSSAI and the Rejected S-NSSAI partially includes sending a UE Configuration Update Command message including the at least one of the Partially Allowed NSSAI and the Rejected S-NSSAI partially.　　(Supplementary note 13)　　The method according to supplementary note 11 or 12,　　wherein the first communication apparatus is an Access and Mobility Management Function (AMF), and　　wherein the second communication apparatus is a Network Data Analytics Function (NWDAF).　　(Supplementary note 14)　　A method of a user equipment (UE) comprising:　　sending, to a communication apparatus, information indicating that the UE is able to understand at least one of Partially Allowed Network Slice Selection Assistance Information (NSSAI) and Rejected Single Network Slice Selection Assistance Information (S-NSSAI) partially; and　　receiving the at least one of the Partially Allowed NSSAI and the Rejected S-NSSAI partially from the communication apparatus in a case of sending the information.　　(Supplementary note 15)　　The method according to supplementary note 14,　　wherein the sending the information includes sending a Registration Request message including the information, and　　wherein the receiving the at least one of the Partially Allowed NSSAI and the Rejected S-NSSAI partially includes receiving a Registration Accept message including the at least one of the Partially Allowed NSSAI and the Rejected S-NSSAI partially.　　(Supplementary note 16)　　The method according to supplementary note 14 or 15,　　wherein the communication apparatus is an Access and Mobility Management Function (AMF).　　(Supplementary note 17)　　A method of a first communication apparatus comprising:　　receiving, from a second communication apparatus, information for determining at least one of Partially Allowed Network Slice Selection Assistance Information (NSSAI) and Rejected Single Network Slice Selection Assistance Information (S-NSSAI) partially;　　determining the at least one of the Partially Allowed NSSAI and the Rejected S-NSSAI partially; and　　sending the at least one of the Partially Allowed NSSAI and the Rejected S-NSSAI partially to the second communication apparatus.　　(Supplementary note 18)　　The method according to supplementary note 17,　　wherein the receiving the information includes receiving an Nnssf_NSSelection_Get message including the information,　　wherein the sending the at least one of the Partially Allowed NSSAI and the Rejected S-NSSAI partially includes sending an Nnssf_NSSelection_Get Response message including the at least one of the Partially Allowed NSSAI and the Rejected S-NSSAI partially.　　(Supplementary note 19)　　The method according to supplementary note 17 or 18,　　wherein the first communication apparatus is a Network Slice Selection Function (NSSF), and　　wherein the second communication apparatus is an Access and Mobility Management Function (AMF).　　(Supplementary note 20)　　The method according to supplementary note 17,　　wherein the receiving the information includes receiving an Npcf_AMPolicyControl_Create message including the information,　　wherein the sending the at least one of the Partially Allowed NSSAI and the Rejected S-NSSAI partially includes sending an Npcf_AMPolicyControl_Create Response message including the at least one of the Partially Allowed NSSAI and the Rejected S-NSSAI partially.　　(Supplementary note 21)　　The method according to supplementary note 17 or 20,　　wherein the first communication apparatus is a Policy Control Function (PCF), and　　wherein the second communication apparatus is an Access and Mobility Management Function (AMF).　　(Supplementary note 22)　　A first communication apparatus comprising:　　means for receiving at least one of Partially Allowed Network Slice Selection Assistance Information (NSSAI) and Rejected Single Network Slice Selection Assistance Information (S-NSSAI) partially from a second communication apparatus; and　　means for sending the at least one of the Partially Allowed NSSAI and the Rejected S-NSSAI partially to a user equipment (UE).　　(Supplementary note 23)　　The first communication apparatus according to supplementary note 22,　　wherein the sending the at least one of the Partially Allowed NSSAI and the Rejected S-NSSAI partially includes sending a Registration Accept message including the at least one of the Partially Allowed NSSAI and the Rejected S-NSSAI partially.　　(Supplementary note 24)　　The first communication apparatus according to supplementary note 22 or 23, further comprising:　　means for receiving information indicating that the UE is able to understand the at least one of the Partially Allowed NSSAI and the Rejected S-NSSAI partially; and　　means for sending the information to the second communication apparatus.　　(Supplementary note 25)　　The first communication apparatus according to supplementary note 24,　　wherein the receiving the at least one of the Partially Allowed NSSAI and the Rejected S-NSSAI partially includes receiving the at least one of the Partially Allowed NSSAI and the Rejected S-NSSAI partially in a case of the sending the information to the second communication apparatus.　　(Supplementary note 26)　　The first communication apparatus according to supplementary note 24 or 25,　　wherein the receiving the information includes receiving a Registration Request message including the information, and　　wherein the sending the information includes sending an Nnssf_NSSelection_Get message including the information.　　(Supplementary note 27)　　The first communication apparatus according to any one of supplementary notes 22 to 26,　　wherein the receiving the at least one of the Partially Allowed NSSAI and the Rejected S-NSSAI partially includes receiving an Nnssf_NSSelection_Get Response message including the at least one of the Partially Allowed NSSAI and the Rejected S-NSSAI partially.　　(Supplementary note 28)　　The first communication apparatus according to any one of supplementary notes 22 to 27,　　wherein the first communication apparatus is an Access and Mobility Management Function (AMF), and　　wherein the second communication apparatus is a Network Slice Selection Function (NSSF).　　(Supplementary note 29)　　The first communication apparatus according to supplementary note 24 or 25,　　wherein the receiving the information includes receiving a Registration Request message including the information, and　　wherein the sending the information includes sending an Npcf_AMPolicyControl_Create message including the information.　　(Supplementary note 30)　　The first communication apparatus according to any one of supplementary notes 22 to 25 and 29,　　wherein the receiving the at least one of the Partially Allowed NSSAI and the Rejected S-NSSAI partially includes receiving an Npcf_AMPolicyControl_Create Response message including the at least one of the Partially Allowed NSSAI and the Rejected S-NSSAI partially.　　(Supplementary note 31)　　The first communication apparatus according to any one of supplementary notes 22 to 25, 29 and 30,　　wherein the first communication apparatus is an Access and Mobility Management Function (AMF), and　　wherein the second communication apparatus is a Policy Control Function (PCF).　　(Supplementary note 32)　　A first communication apparatus comprising:　　means for receiving, from a second communication apparatus, information for determining at least one of Partially Allowed Network Slice Selection Assistance Information (NSSAI) and Rejected Single Network Slice Selection Assistance Information (S-NSSAI) partially;　　means for determining the at least one of the Partially Allowed NSSAI and the Rejected S-NSSAI partially; and　　means for sending the at least one of the Partially Allowed NSSAI and the Rejected S-NSSAI partially to a user equipment (UE).　　(Supplementary note 33)　　The first communication apparatus according to supplementary note 32,　　wherein the receiving the information includes receiving an Nnwdaf_SliceInformation Notification message including the information, and　　wherein the sending the at least one of the Partially Allowed NSSAI and the Rejected S-NSSAI partially includes sending a UE Configuration Update Command message including the at least one of the Partially Allowed NSSAI and the Rejected S-NSSAI partially.　　(Supplementary note 34)　　The first communication apparatus according to supplementary note 32 or 33,　　wherein the first communication apparatus is an Access and Mobility Management Function (AMF), and　　wherein the second communication apparatus is a Network Data Analytics Function (NWDAF).　　(Supplementary note 35)　　A user equipment (UE) comprising:　　means for sending, to a communication apparatus, information indicating that the UE is able to understand at least one of Partially Allowed Network Slice Selection Assistance Information (NSSAI) and Rejected Single Network Slice Selection Assistance Information (S-NSSAI) partially; and　　means for receiving the at least one of the Partially Allowed NSSAI and the Rejected S-NSSAI partially from the communication apparatus in a case of sending the information.　　(Supplementary note 36)　　The UE apparatus according to supplementary note 35,　　wherein the sending the information includes sending a Registration Request message including the information, and　　wherein the receiving the at least one of the Partially Allowed NSSAI and the Rejected S-NSSAI partially includes receiving a Registration Accept message including the at least one of the Partially Allowed NSSAI and the Rejected S-NSSAI partially.　　(Supplementary note 37)　　The UE according to supplementary note 35 or 36,　　wherein the communication apparatus is an Access and Mobility Management Function (AMF).　　(Supplementary note 38)　　A first communication apparatus comprising:　　means for receiving, from a second communication apparatus, information for determining at least one of Partially Allowed Network Slice Selection Assistance Information (NSSAI) and Rejected Single Network Slice Selection Assistance Information (S-NSSAI) partially;　　means for determining the at least one of the Partially Allowed NSSAI and the Rejected S-NSSAI partially; and　　means for sending the at least one of the Partially Allowed NSSAI and the Rejected S-NSSAI partially to the second communication apparatus.　　(Supplementary note 39)　　The first communication apparatus according to supplementary note 38,　　wherein the receiving the information includes receiving an Nnssf_NSSelection_Get message including the information,　　wherein the sending the at least one of the Partially Allowed NSSAI and the Rejected S-NSSAI partially includes sending an Nnssf_NSSelection_Get Response message including the at least one of the Partially Allowed NSSAI and the Rejected S-NSSAI partially.　　(Supplementary note 40)　　The first communication apparatus according to supplementary note 38 or 39,　　wherein the first communication apparatus is a Network Slice Selection Function (NSSF), and　　wherein the second communication apparatus is an Access and Mobility Management Function (AMF).　　(Supplementary note 41)　　The first communication apparatus according to supplementary note 38,　　wherein the receiving the information includes receiving an Npcf_AMPolicyControl_Create message including the information,　　wherein the sending the at least one of the Partially Allowed NSSAI and the Rejected S-NSSAI partially includes sending an Npcf_AMPolicyControl_Create Response message including the at least one of the Partially Allowed NSSAI and the Rejected S-NSSAI partially.　　(Supplementary note 42)　　The first communication apparatus according to supplementary note 38 or 41,　　wherein the first communication apparatus is a Policy Control Function (PCF), and　　wherein the second communication apparatus is an Access and Mobility Management Function (AMF).　　(Supplementary note 43)　　A method of a first communication apparatus comprising:　　receiving a Registration Request message from a User Equipment (UE),　　wherein the Registration Request message includes Requested Network Slice Selection Assistance Information (NSSAI);　　sending the Requested NSSAI to a second communication apparatus;　　receiving Allowed NSSAI from the second communication apparatus,　　wherein the Allowed NSSAI includes Single Network Slice Selection Assistance Information (S-NSSAI); and　　sending a Registration Accept message to the UE,　　wherein the Registration Accept message includes Partially Allowed NSSAI, and　　wherein the Partially Allowed NSSAI includes the S-NSSAI.　　(Supplementary note 44)　　The method according to supplementary note 43,　　wherein the S-NSSAI in the Partially Allowed NSSAI is decided by the first communication apparatus based on the Allowed NSSAI.　　(Supplementary note 45)　　The method according to supplementary note 43,　　wherein the S-NSSAI in the Partially Allowed NSSAI is decided by the first communication apparatus based on the Allowed NSSAI and a policy in the first communication apparatus.　　(Supplementary note 46)　　The method according to any one of supplementary notes 43 to 45,　　wherein the Allowed NSSAI is decided based on the Requested NSSAI.　　(Supplementary note 47)　　The method according to any one of supplementary notes 43 to 46,　　wherein the first communication apparatus is an Access and Mobility Management Function (AMF), and　　wherein the second communication apparatus is a Network Slice Selection Function (NSSF).　　(Supplementary note 48)　　A method of a User Equipment (UE) comprising:　　sending a Registration Request message to a first communication apparatus,　　wherein the Registration Request message includes Requested Network Slice Selection Assistance Information (NSSAI); and　　receiving a Registration Accept message,　　wherein the Registration Accept message includes Partially Allowed NSSAI, and　　wherein the Partially Allowed NSSAI includes Single Network Slice Selection Assistance Information (S-NSSAI),　　wherein the S-NSSAI in the Partially Allowed NSSAI is based on Allowed NSSAI sent from a second communication apparatus to the first communication apparatus, and　　wherein the Allowed NSSAI includes the S-NSSAI.　　(Supplementary note 49)　　The method according to supplementary note 48,　　wherein the S-NSSAI in the Partially Allowed NSSAI is decided based on the Allowed NSSAI.　　(Supplementary note 50)　　The method according to supplementary note 48,　　wherein the S-NSSAI in the Partially Allowed NSSAI is decided based on the Allowed NSSAI and a policy in the first communication apparatus.　　(Supplementary note 51)　　The method according to any one of supplementary notes 48 to 50,　　wherein the Allowed NSSAI is decided based on the Requested NSSAI.　　(Supplementary note 52)　　The method according to any one of supplementary notes 48 to 51,　　wherein the first communication apparatus is an Access and Mobility Management Function (AMF), and　　wherein the second communication apparatus is a Network Slice Selection Function (NSSF).　　(Supplementary note 53)　　A first communication apparatus comprising:　　means for receiving a Registration Request message from a User Equipment (UE),　　wherein the Registration Request message includes Requested Network Slice Selection Assistance Information (NSSAI);　　means for sending the Requested NSSAI to a second communication apparatus;　　means for receiving Allowed NSSAI from the second communication apparatus,　　wherein the Allowed NSSAI includes Single Network Slice Selection Assistance Information (S-NSSAI); and　　means for sending a Registration Accept message to the UE,　　wherein the Registration Accept message includes Partially Allowed NSSAI, and　　wherein the Partially Allowed NSSAI includes the S-NSSAI.　　(Supplementary note 54)　　The first communication apparatus according to supplementary note 53,　　wherein the S-NSSAI in the Partially Allowed NSSAI is decided by the first communication apparatus based on the Allowed NSSAI.　　(Supplementary note 55)　　The first communication apparatus according to supplementary note 53,　　wherein the S-NSSAI in the Partially Allowed NSSAI is decided by the first communication apparatus based on the Allowed NSSAI and a policy in the first communication apparatus.　　(Supplementary note 56)　　The first communication apparatus according to any one of supplementary notes 53 to 55,　　wherein the Allowed NSSAI is decided based on the Requested NSSAI.　　(Supplementary note 57)　　The first communication apparatus according to any one of supplementary notes 53 to 56,　　wherein the first communication apparatus is an Access and Mobility Management Function (AMF), and　　wherein the second communication apparatus is a Network Slice Selection Function (NSSF).　　(Supplementary note 58)　　A User Equipment (UE) comprising:　　means for sending a Registration Request message to a first communication apparatus,　　wherein the Registration Request message includes Requested Network Slice Selection Assistance Information (NSSAI); and　　means for receiving a Registration Accept message,　　wherein the Registration Accept message includes Partially Allowed NSSAI, and　　wherein the Partially Allowed NSSAI includes Single Network Slice Selection Assistance Information (S-NSSAI),　　wherein the S-NSSAI in the Partially Allowed NSSAI is based on Allowed NSSAI sent from a second communication apparatus to the first communication apparatus, and　　wherein the Allowed NSSAI includes the S-NSSAI.　　(Supplementary note 59)　　The UE according to supplementary note 58,　　wherein the S-NSSAI in the Partially Allowed NSSAI is decided based on the Allowed NSSAI.　　(Supplementary note 60)　　The UE according to supplementary note 58,　　wherein the S-NSSAI in the Partially Allowed NSSAI is decided based on the Allowed NSSAI and a policy in the first communication apparatus.　　(Supplementary note 61)　　The UE according to any one of supplementary notes 58 to 60,　　wherein the Allowed NSSAI is decided based on the Requested NSSAI.　　(Supplementary note 62)　　The UE according to any one of supplementary notes 58 to 61,　　wherein the first communication apparatus is an Access and Mobility Management Function (AMF), and　　wherein the second communication apparatus is a Network Slice Selection Function (NSSF).　　This application is based upon and claims the benefit of priority from Indian patent applications No. 202311025745, filed on April 5, 2023, the disclosure of which is incorporated herein in its entirety by reference.1 TELECOMMUNICATION3 UE5 (R)AN NODE7 CORE NETWORK20 DATA NETWORK60 RU61 DU62 CU70 AMF71 SMF72 UPF73 PCF74 NWDAF75 UDM76 NSSF201 AF

Claims

1. A method of a first communication apparatus comprising: 　　receiving a Registration Request message from a User Equipment (UE), 　　wherein the Registration Request message includes Requested Network Slice Selection Assistance Information (NSSAI); 　　sending the Requested NSSAI to a second communication apparatus; 　　receiving Allowed NSSAI from the second communication apparatus, 　　wherein the Allowed NSSAI includes Single Network Slice Selection Assistance Information (S-NSSAI); and 　　sending a Registration Accept message to the UE, 　　wherein the Registration Accept message includes Partially Allowed NSSAI, and 　　wherein the Partially Allowed NSSAI includes the S-NSSAI.

2. The method according to claim 1, 　　wherein the S-NSSAI in the Partially Allowed NSSAI is decided by the first communication apparatus based on the Allowed NSSAI.

3. The method according to claim 1, 　　wherein the S-NSSAI in the Partially Allowed NSSAI is decided by the first communication apparatus based on the Allowed NSSAI and a policy in the first communication apparatus.

4. The method according to any one of claims 1 to 3, 　　wherein the Allowed NSSAI is decided based on the Requested NSSAI.

5. The method according to any one of claims 1 to 4, 　　wherein the first communication apparatus is an Access and Mobility Management Function (AMF), and 　　wherein the second communication apparatus is a Network Slice Selection Function (NSSF).

6. A method of a User Equipment (UE) comprising: 　　sending a Registration Request message to a first communication apparatus, 　　wherein the Registration Request message includes Requested Network Slice Selection Assistance Information (NSSAI); and 　　receiving a Registration Accept message, 　　wherein the Registration Accept message includes Partially Allowed NSSAI, and 　　wherein the Partially Allowed NSSAI includes Single Network Slice Selection Assistance Information (S-NSSAI), 　　wherein the S-NSSAI in the Partially Allowed NSSAI is based on Allowed NSSAI sent from a second communication apparatus to the first communication apparatus, and 　　wherein the Allowed NSSAI includes the S-NSSAI.

7. The method according to claim 6, 　　wherein the S-NSSAI in the Partially Allowed NSSAI is decided based on the Allowed NSSAI.

8. The method according to claim 6, 　　wherein the S-NSSAI in the Partially Allowed NSSAI is decided based on the Allowed NSSAI and a policy in the first communication apparatus.

9. The method according to any one of claims 6 to 8, 　　wherein the Allowed NSSAI is decided based on the Requested NSSAI.

10. The method according to any one of claims 6 to 9, 　　wherein the first communication apparatus is an Access and Mobility Management Function (AMF), and 　　wherein the second communication apparatus is a Network Slice Selection Function (NSSF).

11. A first communication apparatus comprising: 　　means for receiving a Registration Request message from a User Equipment (UE), 　　wherein the Registration Request message includes Requested Network Slice Selection Assistance Information (NSSAI); 　　means for sending the Requested NSSAI to a second communication apparatus; 　　means for receiving Allowed NSSAI from the second communication apparatus, 　　wherein the Allowed NSSAI includes Single Network Slice Selection Assistance Information (S-NSSAI); and 　　means for sending a Registration Accept message to the UE, 　　wherein the Registration Accept message includes Partially Allowed NSSAI, and 　　wherein the Partially Allowed NSSAI includes the S-NSSAI.

12. The first communication apparatus according to claim 11, 　　wherein the S-NSSAI in the Partially Allowed NSSAI is decided by the first communication apparatus based on the Allowed NSSAI.

13. The first communication apparatus according to claim 11, 　　wherein the S-NSSAI in the Partially Allowed NSSAI is decided by the first communication apparatus based on the Allowed NSSAI and a policy in the first communication apparatus.

14. The first communication apparatus according to any one of claims 11 to 13, 　　wherein the Allowed NSSAI is decided based on the Requested NSSAI.

15. The first communication apparatus according to any one of claims 11 to 14, 　　wherein the first communication apparatus is an Access and Mobility Management Function (AMF), and 　　wherein the second communication apparatus is a Network Slice Selection Function (NSSF).

16. A User Equipment (UE) comprising: 　　means for sending a Registration Request message to a first communication apparatus, 　　wherein the Registration Request message includes Requested Network Slice Selection Assistance Information (NSSAI); and 　　means for receiving a Registration Accept message, 　　wherein the Registration Accept message includes Partially Allowed NSSAI, and 　　wherein the Partially Allowed NSSAI includes Single Network Slice Selection Assistance Information (S-NSSAI), 　　wherein the S-NSSAI in the Partially Allowed NSSAI is based on Allowed NSSAI sent from a second communication apparatus to the first communication apparatus, and 　　wherein the Allowed NSSAI includes the S-NSSAI.

17. The UE according to claim 16, 　　wherein the S-NSSAI in the Partially Allowed NSSAI is decided based on the Allowed NSSAI.

18. The UE according to claim 16, 　　wherein the S-NSSAI in the Partially Allowed NSSAI is decided based on the Allowed NSSAI and a policy in the first communication apparatus.

19. The UE according to any one of claims 16 to 18, 　　wherein the Allowed NSSAI is decided based on the Requested NSSAI.

20. The UE according to any one of claims 16 to 19, 　　wherein the first communication apparatus is an Access and Mobility Management Function (AMF), and 　　wherein the second communication apparatus is a Network Slice Selection Function (NSSF).

Images