Core network and user equipment (UE)

Abstract

In a 5GS, a communication method for continuing a service of a PDU session in a network slice is provided in a case where the network slice is congested, a case where the network performance of the network slice does not satisfy an SLA, or the like. The UE transmits, in a login process, a login request message including UE capability information indicating that the UE supports anchor relocation with an S-NSSAI or a change of a network slice, establishes a first PDU session, receives the first S-NSSAI and a PDU session release command message including a first PDU session ID, releases the first PDU session, transmits the first S-NSSAI and a PDU session establishment request message including a second PDU session ID, and transmits the first S-NSSAI and the PDU session establishment request message to the second PDU session ID. And establishing a second PDU session.

Description

Technical Field

[0001] The present invention relates to a core network and UE (User Equipment). Background Art

[0002] In 3GPP (3rd Generation Partnership Project) which is carrying out standardization activities of mobile communication systems in recent years, SAE (System Architecture Evolution) which is a system framework of LTE (Long Term Evolution) is being studied.

[0003] In addition, in recent years, 3GPP has also conducted research on the next-generation communication technology and system architecture of the 5G (5th Generation) mobile communication system, which is the next-generation mobile communication system. In particular, 5GS (5G System) has been standardized as a system to implement the 5G mobile communication system (see non-patent documents 1 to 3). In 5GS, technical issues for connecting various terminals to cellular networks are extracted and solutions are standardized. Prior art literature Non-patent literature

[0004] Non-patent document 1: 3GPP TS23.501V17.4.0 (2022-03); 3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Systemarchitecture for the 5G System (5GS); Stage 2 (Release 17) Non-patent document 2: 3GPP TS23.502V17.4.0 (2022-03); 3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Procedures for the 5G System (5GS); Stage 2 (Release 17) Non-patent document 3: 3GPP TS24.501V17.6.1 (2022-03); 3rd Generation Partnership Project; Technical Specification Group Core Network and Terminals; Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3 (Release 17) Non-patent document 4: 3GPP TR 23.700-41V0.2.0 (2022-04); 3rd Generation Partnership Project; Technical Specification Group Services and SystemAspects; Study on enhancement of network slicing; Phase 3 (Release 18) Summary of the invention Problem that the invention aims to solve

[0005] In 5GS (5G System), in order to provide various services, research is being conducted on 5GCN (5G Core Network) as a new core network.

[0006] Moreover, in 5G, network slices are defined as logical networks that provide specific network functions and specific network characteristics for specific service types and specific groups. For example, a network slice can be a logical network provided to a terminal with a low-latency function or a logical network provided to a sensor terminal for IoT (Internet of Things).

[0007] In addition, in order to study further functions associated with network slicing, 3GPP has studied eNS (Enhancement of Network Slicing). In 3GPP, as a phase 3 study of eNS, a technology for continuing the service of a PDU session in a network slice in the case of network slice congestion without mobility, the case where the network performance of a network slice without mobility does not meet the service level agreement (also called SLA), and the case of network slice congestion with mobility has been studied (see non-patent document 4).

[0008] However, practical methods for meeting the above requirements are still unclear.

[0009] The present invention is completed in view of the above situation and provides a method for implementing the functions used for NS and / or SNPN in 5GS. Technical Solution

[0010] A UE according to one embodiment of the present invention is a UE (User Equipment) having a transceiver and a control unit, characterized in that the transceiver sends a login request message during a login process, the login request message including UE capability information indicating that the UE supports anchor relocation with S-NSSAI (Single Network Slice Selection Assistance Information) or a change in network slice, the control unit establishes a first PDU session identified by a first PDU session ID by starting a PDU session establishment process, the control unit sets SSC mode 2 for the first PDU session, the transceiver receives a first S-NSSAI and a PDU session release command message including the first PDU session ID during a PDU session release process, the control unit releases the first PDU session corresponding to the first PDU session ID, the transceiver sends the first S-NSSAI and a PDU session establishment request message including a second PDU session ID, and the control unit establishes a second PDU session corresponding to the second PDU session ID using the first S-NSSAI.

[0011] In addition, a UE of one embodiment of the present invention is a UE (User Equipment) having a transceiver unit and a control unit, characterized in that the transceiver unit sends a login request message during a login process, the login request message including information indicating that the UE supports anchor relocation with S-NSSAI (Single Network Slice Selection Assistance Information) or a change in network slice, the control unit establishes a first PDU session identified by a first PDU session ID by starting a PDU session establishment process, the control unit sets SSC mode 3 for the first PDU session, the transceiver unit receives a first S-NSSAI and a PDU session change command message including the first PDU session ID during a PDU session change process, the transceiver unit sends the first S-NSSAI and a PDU session establishment request message including a second PDU session ID, the control unit establishes a second PDU session corresponding to the second PDU session ID using the first S-NSSAI, and after establishing the second PDU session, the control unit releases the first PDU session corresponding to the first PDU session ID. Beneficial Effects

[0012] According to the present invention, a method for continuing the service of a PDU session in a network slice can be provided in situations where the network slice is congested without mobility, where the network performance of the network slice does not meet the service level agreement (also known as SLA) without mobility, where the network slice is congested with mobility, etc. BRIEF DESCRIPTION OF THE DRAWINGS

[0013] Figure 1 This is a diagram illustrating the outline of a mobile communication system (EPS / 5GS). Figure 2 This is a diagram illustrating the detailed structure of the mobile communication system (EPS / 5GS). Figure 3 This is a diagram illustrating the device structure of UE. Figure 4 This is a diagram illustrating the structure of the access network device (gNB) in 5GS. Figure 5 This is a diagram that illustrates the structure of the core network device (AMF / SMF / UPF) in 5GS. Figure 6 This is a diagram illustrating the PDU session change process. Figure 7 This is a diagram illustrating the PDU session release process. Figure 8 This is a diagram that explains the PDU session establishment process. Fig. 9 This is a diagram for explaining a part of the first embodiment. Fig.10 This is a diagram for explaining a part of the second embodiment. Fig.11 This is a diagram for explaining the login process. DETAILED DESCRIPTION

[0014] Hereinafter, the best mode for carrying out the present invention will be described with reference to the accompanying drawings. It should be noted that in this embodiment, an embodiment of a mobile communication system in which the present invention is applied will be described as an example. [1. System Overview]

[0015] first, Figure 1 is a diagram for explaining an outline of a mobile communication system 1 used in each embodiment. Figure 2 It is a diagram for explaining the detailed structure of the mobile communication system 1.

[0016] exist Figure 1It is recorded that the mobile communication system 1 is composed of UE_A10, access network_A80, core network_A90, PDN (Packet Data Network: packet data network)_A5, access network_B120, core network_B190, and DN (Data Network: data network)_A6.

[0017] In the following, these devices / functions may be recorded with omitted symbols, such as UE, access network_A, core network_A, PDN, access network_B, core network_B, DN, etc.

[0018] In addition, Figure 2 The following devices / functions are recorded: UE_A10, E-UTRAN80, MME40, SGW35, PGW-U30, PGW-C32, PCRF60, HSS50, 5G AN120, AMF140, UPF130, SMF132, PCF160, UDM150, N3IWF170 and other devices / functions as well as interfaces connecting these devices / functions to each other.

[0019] In the following, for these devices / functions, symbols are sometimes omitted, such as UE, E-UTRAN, MME, SGW, PGW-U, PGW-C, PCRF, HSS, 5G AN, AMF, UPF, SMF, PCF, UDM, N3IWF, etc.

[0020] It should be noted that the EPS (Evolved Packet System) as a 4G system is composed of an access network_A and a core network_A, but may further include UE and / or PDN. In addition, the 5GS (5G System) as a 5G system is composed of a UE, an access network_B and a core network_B, but may further include a DN.

[0021] UE is a device that can connect to network services via 3GPP access (also known as 3GPP access network, 3GPP AN) and / or non-3GPP access (non-3GPP access, also known as non-3GPP access network, non-3GPP AN). UE can be a terminal device that can perform wireless communication, such as a portable phone or a smart phone, or a terminal device that can connect to EPS or 5GS. UE can have UICC (Universal Integrated Circuit Card) or eUICC (Embedded UICC). It should be noted that UE can be expressed as a user device or as a terminal device.

[0022] In addition, access network_A corresponds to E-UTRAN (Evolved Universal Terrestrial Radio Access Network) and / or wireless LAN access network. One or more eNBs (evolved Node Bs) 45 are configured in E-UTRAN. It should be noted that, in the following, eNB45 is sometimes recorded by omitting the symbol like eNB. In addition, when there are multiple eNBs, each eNB is connected to each other, for example, via an X2 interface. In addition, one or more access points are configured in the wireless LAN access network.

[0023] In addition, access network_B corresponds to the 5G access network (5G AN). 5G AN is composed of NG-RAN (NG Radio Access Network: NG wireless access network) and / or non-3GPP access network. One or more gNB (NRNodeB: NR Node B) 122 are configured in NG-RAN. It should be noted that, below, the gNB122 is sometimes recorded with omitted symbols, such as eNB. The gNB is a node that provides the NR (New Radio: New Radio) user plane and control plane to the UE, and is a node connected to the 5GCN via the NG interface (including the N2 interface or the N3 interface). That is, the gNB is a base station device redesigned for 5GS, and has different functions from the base station device (eNB) used in the EPS as a 4G system. In addition, when there are multiple gNBs, the gNBs are connected to each other, for example, via an Xn interface.

[0024] In addition, the non-3GPP access network can be an untrusted non-3GPP access network or a trusted non-3GPP access network. Here, the untrusted non-3GPP access network can be a non-3GPP access network such as a public wireless LAN that does not perform security management within the access network. On the other hand, the trusted non-3GPP access network can be an access network specified by 3GPP and can have TNAP (trusted non-3GPP access point) and TNGF (trusted non-3GPP Gateway function).

[0025] NG-RAN refers to the radio access network connected to 5GCN, which can also use NR or E-UTRA or both. In other words, NG-RAN can also be E-UTRAN.

[0026] In addition, below, E-UTRAN and NG-RAN are sometimes referred to as 3GPP access. In addition, wireless LAN access network and non-3GPP AN are sometimes referred to as non-3GPP access. In addition, nodes configured in access network_B are sometimes collectively referred to as NG-RAN nodes.

[0027] In addition, in the following, access network_A and / or access network_B and / or the device included in access network_A and / or the device included in access network_B are sometimes referred to as access networks or access network devices.

[0028] In addition, the core network_A corresponds to EPC (Evolved Packet Core). In EPC, for example, MME (Mobility Management Entity), SGW (Serving Gateway), PGW (Packet Data Network Gateway)-U, PGW-C, PCRF (Policy and Charging Rules Function), HSS (Home Subscriber Server), etc. are configured.

[0029] In addition, core network_B corresponds to 5GCN (5G Core Network). In 5GCN, for example, AMF (Access and Mobility Management Function), UPF (User Plane Function), SMF (Session Management Function), PCF (Policy Control Function), UDM (Unified Data Management), etc. are configured. Here, 5GCN can be expressed as 5GC.

[0030] In addition, below, core network_A and / or core network_B, devices included in core network_A and / or devices included in core network_B are sometimes referred to as core networks or core network devices or devices within the core network.

[0031] The core network (core network_A and / or core network_B) can be an IP mobile communication network operated by a mobile communication operator (Mobile Network Operator; MNO) that connects the access network (Access Network_A and / or Access Network_B) and PDN and / or DN, or it can be a core network used by a mobile communication operator that operates and manages the mobile communication system 1, or it can be a core network used by virtual mobile communication operators and virtual mobile communication service providers such as MVNO (Mobile Virtual Network Operator) and MVNE (Mobile Virtual Network Enabler).

[0032] The core network (core network_A and / or core network_B) and the access network (access network_A and / or access network_B) may be different for each mobile communication operator.

[0033] In addition, Figure 1 The case where PDN and DN are the same is recorded in the specification, but they can also be different. PDN can be a DN (Data Network) that provides communication services to UE. It should be noted that DN can be constructed as a packet data service network or can be constructed for each service. Moreover, PDN can include connected communication terminals. Therefore, connection with PDN can be connection with communication terminals and server devices configured for PDN. Moreover, sending and receiving user data with PDN can be sending and receiving user data with communication terminals and server devices configured for PDN. It should be noted that PDN can be expressed as DN, and DN can be expressed as PDN.

[0034] In addition, hereinafter, at least a part of access network_A, core network_A, PDN, access network_B, core network_B, DN and / or one or more devices included therein are sometimes referred to as a network or a network device. That is, the network and / or network device sending and receiving messages and / or executing a process means that at least a part of access network_A, core network_A, PDN, access network_B, core network_B, DN and / or one or more devices included therein send and receive messages and / or execute a process.

[0035] In addition, the UE can be connected to the access network. In addition, the UE can be connected to the core network via the access network. Moreover, the UE can be connected to the PDN or DN via the access network and the core network. That is, the UE can send and receive (communicate) user data between the PDN or DN. When sending and receiving user data, not only IP (Internet Protocol) communication can be used, but also non-IP communication can be used.

[0036] Here, IP communication refers to data communication using IP, in which data is sent and received through IP packets. An IP packet consists of an IP header and a payload portion. The payload portion may include data sent and received by devices / functions included in EPS and devices / functions included in 5GS. In addition, non-IP communication refers to data communication that does not use IP, in which data is sent and received in a form different from the structure of IP packets. For example, non-IP communication may be data communication achieved by sending and receiving application data that is not assigned an IP header, or may be assigned other headers such as a MAC header, Ethernet (registered trademark) frame header, etc. to send and receive user data sent and received by the UE.

[0037] In addition, the access network_A, core network_A, access network_B, core network_B, PDN_A, and DN_A may have configurations not recorded in Figure 2 For example, the core network_A and / or the core network_B and / or the PDN_A and / or the DN_A may include an AUSF (Authentication Server Function), an AAA (Authentication, authorization, and accounting) server (AAA-S). The AAA server may be configured outside the core network.

[0038] Here, AUSF is a core network device having an authentication function for 3GPP access and non-3GPP access, and more specifically, is a network function unit that receives a request for authentication for 3GPP access and / or non-3GPP access from a UE and executes an authentication process.

[0039] In addition, the AAA server is a device that is directly connected to the AUSF or indirectly via other network devices and has authentication, authorization and billing functions. The AAA server can be a network device within the core network. It should be noted that the AAA server can be included in the PLMN and / or SNPN but not included in the core network_A and / or core network_B. That is, the AAA server can be either a core network device or a device outside the core network. For example, the AAA server can be a server device within the PLMN and / or SNPN managed by a third party (3rdParty).

[0040] In this document, when referred to as NW, it can mean a core network, an access network, or both.

[0041] It should be noted that in Figure 2In the figure, for the sake of simplicity, each device / function is described as one, but multiple similar devices / functions may be configured in the mobile communication system 1. Specifically, multiple devices / functions such as UE_A10, E-UTRAN80, MME40, SGW35, PGW-U30, PGW-C32, PCRF60, HSS50, 5G AN120, AMF140, UPF130, SMF132, PCF160 and / or UDM150 may be configured in the mobile communication system 1.

[0042] Furthermore, the mobile communication system 1 may include devices and / or functions other than those described above, for example, it may include NSSF (Network Slice Selection Function). [2. Configuration of each device]

[0043] Next, the configuration of each device (UE and / or access network device and / or core network device) used in each embodiment is described using the accompanying drawings. It should be noted that each device can be configured as physical hardware, as logical (virtual) hardware configured on general hardware, or as software. In addition, at least part (including all) of the functions of each device can also be configured as physical hardware, logical hardware, or software.

[0044] It should be noted that each storage unit (storage unit_A340, storage unit_A440, storage unit_B540, storage unit_A640, storage unit_B740) in each device and each function that appears below is composed of, for example, semiconductor memory, SSD (Solid State Drive), HDD (Hard Disk Drive), etc. In addition, each storage unit can not only store the information originally set at the factory stage, but also store various information sent and received between the device itself and devices / functions other than the function (such as UE and / or access network device and / or core network device and / or PDN and / or DN). In addition, each storage unit can store identification information, control information, flags, parameters, etc. included in the control messages sent and received in various communication processes described later. In addition, each storage unit can also store this information for each UE. In addition, each storage unit can store control messages and user data sent and received between the devices / functions included in 5GS and / or EPS when intercommunication between 5GS and EPS is performed. At this time, not only the data sent and received via the N26 interface can be stored, but also the data not sent and received via the N26 interface can be stored. [2.1. UE device configuration]

[0045] First, use Figure 3An example of the configuration of a UE (User Equipment) is described. The UE is composed of a control unit_A300, an antenna 310, a transceiver_A320, and a storage unit_A340. The control unit_A300, the transceiver_A320, and the storage unit_A340 are connected via a bus. The transceiver_A320 is connected to the antenna 310.

[0046] The control unit_A300 is a functional unit that controls the overall actions and functions of the UE. The control unit_A300 reads and executes various programs stored in the storage unit_A340 as needed, thereby realizing various processes in the UE.

[0047] The transceiver_A320 is a functional unit for wirelessly communicating with a base station device (eNB or gNB) in the access network via an antenna. That is, the UE can use the transceiver_A320 to send and receive user data and / or control information between the access network device and / or the core network device and / or the PDN and / or the DN.

[0048] Reference Figure 2 To explain in detail, the UE can communicate with the base station device (eNB) in the E-UTRAN via the LTE-Uu interface by using the transceiver_A320. In addition, the UE can communicate with the base station device (gNB) in the 5G AN by using the transceiver_A320. In addition, the UE can send and receive NAS (Non-Access-Stratum: non-access layer) messages with the AMF via the N1 interface by using the transceiver_A320. However, since the N1 interface is a logical interface, the communication between the UE and the AMF is actually carried out via the 5G AN.

[0049] The storage unit_A340 is a functional unit for storing programs, user data, control information, etc. required for various actions of the UE. [2.2.gNB device configuration]

[0050] Next, use Figure 4 The following describes an example of the gNB device configuration. The gNB is composed of a control unit_B500, an antenna 510, a network connection unit_B520, a transceiver unit_B530, and a storage unit_B540. The control unit_B500, the network connection unit_B520, the transceiver unit_B530, and the storage unit_B540 are connected via a bus. The transceiver unit_B530 is connected to the antenna 510.

[0051] The control unit_B500 is a functional unit that controls the overall actions and functions of the gNB. The control unit_B500 reads and executes various programs stored in the storage unit_B540 as needed, thereby realizing various processes in the gNB.

[0052] The network connection unit_B520 is a functional unit for gNB to communicate with AMF and / or UPF. That is, the gNB can use the network connection unit_B520 to send and receive user data and / or control information between the AMF and / or UPF.

[0053] The transceiver_B530 is a functional unit for wirelessly communicating with the UE via the antenna 510. That is, the gNB can use the transceiver_B530 to send and receive user data and / or control information between the UE.

[0054] Reference Figure 2 To explain in detail, the gNB in ​​the 5G AN can communicate with the AMF via the N2 interface by using the network connection unit_B520, and can communicate with the UPF via the N3 interface. In addition, the gNB can communicate with the UE by using the transceiver unit_B530.

[0055] Storage unit_B540 is a functional unit used to store programs, user data, control information, etc. required for various actions of gNB. [2.3.AMF device configuration]

[0056] Next, use Figure 5 The following describes an example of the device configuration of AMF. AMF is composed of a control unit_B700, a network connection unit_B720, and a storage unit_B740. The control unit_B700, the network connection unit_B720, and the storage unit_B740 are connected via a bus. AMF can be a node that operates a control plane.

[0057] The control unit_B700 is a functional unit that controls the overall operation and functions of the AMF. The control unit_B700 reads and executes various programs stored in the storage unit_B740 as needed, thereby realizing various processes in the AMF.

[0058] The network connection unit_B720 is a functional unit for connecting the AMF with the base station device (gNB) and / or SMF and / or PCF and / or UDM and / or SCEF in the 5G AN. That is, the AMF can use the network connection unit_B720 to send and receive user data and / or control information between the base station device (gNB) and / or SMF and / or PCF and / or UDM and / or SCEF in the 5G AN.

[0059] Reference Figure 2To explain in detail, the AMF in 5GCN can communicate with gNB via the N2 interface, can communicate with UDM via the N8 interface, can communicate with SMF via the N11 interface, and can communicate with PCF via the N15 interface by using the network connection unit_A620. In addition, the AMF can send and receive NAS messages with the UE via the N1 interface by using the network connection unit_A620. However, since the N1 interface is a logical interface, the communication between the UE and the AMF is actually carried out via the 5G AN. In addition, when the N26 interface is supported, the AMF can communicate with the MME via the N26 interface by using the network connection unit_A620.

[0060] Storage unit_B740 is a functional unit for storing programs, user data, control information, etc. required for various actions of AMF.

[0061] It should be noted that AMF has the following functions: the function of exchanging control messages with RAN using N2 interface, the function of exchanging NAS messages with UE using N1 interface, the function of encrypting and integrity protecting NAS messages, the registration management (RM) function, the connection management (CM) function, the reachability management function, the mobility management (Mobility management) function of UE, etc., the function of transmitting SM (Session Management) messages between UE and SMF, the access authentication (Access Authentication, Access Authorization) function, the security anchor function (SEA; Security Anchor Functionality), the security context management (SCM; Security Context Management) function, the function of supporting the N2 interface for N3IWF (Non-3GPP Interworking Function: non-3GPP interworking function), the function of supporting the sending and receiving of NAS signals with UE via N3IWF, the function of authenticating UE connected via N3IWF, etc.

[0062] In addition, the RM state of each UE is managed in the login management. The RM state can be synchronized between the UE and the AMF. As the RM state, there are a non-logged-in state (RM-DEREGISTERED state) and a logged-in state (RM-REGISTERED state). In the RM-DEREGISTERED state, since the UE has not logged in to the network, the UE context in the AMF does not have valid location information and routing information for the UE, so the AMF is in a state where the UE cannot be reached. In addition, in the RM-REGISTERED state, the UE has logged in to the network, so the UE can receive services that require login to the network. It should be noted that the RM state can be expressed as a 5GMM state (5GMM state). In this case, the RM-DEREGISTERED state can be expressed as a 5GMM-DEREGISTERED state, and the RM-REGISTERED state can be expressed as a 5GMM-REGISTERED state.

[0063] In other words, 5GMM-REGISTERED can be a state where each device has established a 5GMM context, or a state where each device has established a PDU session context. It should be noted that when each device is 5GMM-REGISTERED, UE_A10 can start sending and receiving user data and control messages, and can also respond to paging. Moreover, it should be noted that when each device is 5GMM-REGISTERED, UE_A10 can perform login procedures and / or service request procedures other than the login procedure for initial login.

[0064] Moreover, 5GMM-DEREGISTERED can be a state where each device has not established a 5GMM context, a state where the location information of UE_A10 is not grasped by the network, or a state where the network cannot reach UE_A10. It should be noted that when each device is 5GMM-DEREGISTERED, UE_A10 can start the login process or establish a 5GMM context by executing the login process.

[0065] In addition, the CM state of each UE is managed in the connection management. The CM state can be synchronized between the UE and the AMF. As CM states, there are a non-connected state (CM-IDLE state) and a connected state (CM-CONNECTED state). In the CM-IDLE state, the UE is in the RM-REGISTERED state, but does not have a NAS signaling connection (NAS signaling connection) established with the AMF via the N1 interface. In addition, in the CM-IDLE state, the UE does not have a connection (N2connection) of the N2 interface and a connection (N3connection) of the N3 interface. On the other hand, in the CM-CONNECTED state, it has a NAS signaling connection (NAS signaling connection) established with the AMF via the N1 interface. In addition, in the CM-CONNECTED state, the UE may also have a connection (N2connection) of the N2 interface and / or a connection (N3connection) of the N3 interface.

[0066] Moreover, in connection management, it can also be divided into CM state in 3GPP access and CM state in non-3GPP access for management. In this case, as the CM state in 3GPP access, there can be a non-connected state in 3GPP access (CM-IDLE state over 3GPP access) and a connected state in 3GPP access (CM-CONNECTED state over3GPP access). Moreover, as the CM state in non-3GPP access, there can be a non-connected state in non-3GPP access (CM-IDLE state over non-3GPP access) and a connected state in non-3GPP access (CM-CONNECTEDstate over non-3GPP access). It should be noted that the non-connected state can be expressed as an idle mode, and the connected state mode can be expressed as a connected mode.

[0067] It should be noted that the CM state can also be expressed as 5GMM mode. In this case, the non-connected state can also be expressed as 5GMM non-connected mode (5GMM-IDLE mode), and the connected state can also be expressed as 5GMM connected mode (5GMM-CONNECTED mode). Moreover, the non-connected state in 3GPP access can also be expressed as 5GMM non-connected mode in 3GPP access (5GMM-IDLE mode over 3GPP access), and the connected state in 3GPP access can also be expressed as 5GMM connected mode in 3GPP access (5GMM-CONNECTED mode over 3GPP access). Moreover, the non-connected state in non-3GPP access can also be expressed as 5GMM non-connected mode in non-3GPP access (5GMM-IDLE modeover non-3GPP access), and the connected state in non-3GPP access can also be expressed as 5GMM connected mode in non-3GPP access (5GMM-CONNECTED mode over non-3GPP access). It should be noted that the 5GMM non-connected mode can be expressed as an idle mode, and the 5GMM connected mode can be expressed as a connected mode.

[0068] In addition, more than one AMF can be configured in the core network_B. In addition, AMF can be an NF that manages more than one NSI (Network Slice Instance). In addition, AMF can also be a shared CP function (CCNF; Common CPNF (Control Plane Network Function)) shared among multiple NSIs.

[0069] It should be noted that N3IWF is a device and / or function configured between non-3GPP access and 5GCN when the UE is connected to 5GS via non-3GPP access. [2.4.SMF device configuration]

[0070] Next, use Figure 5 An example of the device configuration of SMF is described. SMF is composed of a control unit_B700, a network connection unit_B720, and a storage unit_B740. The control unit_B700, the network connection unit_B720, and the storage unit_B740 are connected via a bus. SMF can be a node that operates a control plane.

[0071] The control unit_B700 is a functional unit that controls the entire operation and function of the SMF. The control unit_B700 reads and executes various programs stored in the storage unit_B740 as needed, thereby realizing various processes in the SMF.

[0072] The network connection unit_B720 is a functional unit for connecting the SMF with the AMF and / or UPF and / or PCF and / or UDM. That is, the SMF can use the network connection unit_B720 to send and receive user data and / or control information between the AMF and / or UPF and / or PCF and / or UDM.

[0073] Reference Figure 2 To explain in detail, the SMF in 5GCN can communicate with AMF via the N11 interface, communicate with UPF via the N4 interface, communicate with PCF via the N7 interface, and communicate with UDM via the N10 interface by using the network connection unit _A620.

[0074] Storage unit_B740 is a functional unit for storing programs, user data, control information, etc. required for various actions of SMF.

[0075] SMF has the following functions: session management functions such as establishment, modification, and release of PDU sessions, IP address allocation and management functions for UE, UPF selection and control functions, UPF setting functions for routing services to the appropriate destination (sending destination), functions for sending and receiving the SM part of NAS messages, functions for notifying that downlink data has arrived (Downlink Data Notification), functions for providing AN-specific (each AN's) SM information sent to AN via AMF and through the N2 interface, functions for determining the SSC mode (Session and Service Continuity mode) for the session, roaming functions, etc. [2.5. UPF device configuration]

[0076] Next, use Figure 5 The following describes an example of the device configuration of the UPF. The UPF is composed of a control unit_B700, a network connection unit_B720, and a storage unit_B740. The control unit_B700, the network connection unit_B720, and the storage unit_B740 are connected via a bus. The UPF may be a node that operates the control plane.

[0077] The control unit_B700 is a functional unit that controls the overall operation and functions of the UPF. The control unit_B700 reads and executes various programs stored in the storage unit_B740 as needed, thereby realizing various processes in the UPF.

[0078] The network connection unit_B720 is a functional unit for connecting the UPF to the base station device (gNB) and / or SMF and / or DN in the 5G AN. That is, the UPF can use the network connection unit_B720 to send and receive user data and / or control information between the base station device (gNB) and / or SMF and / or DN in the 5G AN.

[0079] Reference Figure 2 To explain in detail, the UPF in 5GCN can communicate with gNB via the N3 interface, communicate with SMF via the N4 interface, communicate with DN via the N6 interface, and communicate with other UPFs via the N9 interface by using the network connection unit _A620.

[0080] Storage unit_B740 is a functional unit for storing programs, user data, control information, etc. required for various actions of UPF.

[0081] UPF has the following functions: function as an anchor point (hereinafter also referred to as anchor) for intra-RAT mobility or inter-RAT mobility, function as an external PDU session point for interconnecting with DN (that is, function as a gateway between DN and core network_B to transmit user data), function of routing and transmitting packets, UL CL (Uplink Classifier) ​​function supporting routing of multiple service flows for one DN, branching point function supporting multi-homed PDU sessions, QoS (Quality of Service) processing function for user plane, verification function of uplink services, triggering buffering of downlink packets, downlink data notification function, etc. UPF is sometimes also called anchor or PDU session anchor or endpoint.

[0082] In addition, UPF can be a gateway for IP communication and / or non-IP communication. In addition, UPF can have the function of transmitting IP communication, and can also have the function of converting non-IP communication and IP communication. Moreover, the configured multiple gateways can be gateways connecting the core network_B with a single DN. It should be noted that UPF can have connectivity with other NFs, and can also be connected to each device via other NFs.

[0083] It should be noted that the user plane is user data sent and received between the UE and the network. The user plane can use a PDN connection or a PDU session for transmission and reception. Moreover, in the case of EPS, the user plane can also use the LTE-Uu interface and / or the S1-U interface and / or the S5 interface and / or the S8 interface and / or the SGi interface for transmission and reception. Moreover, in the case of 5GS, the user plane can also be transmitted and received via the interface between the UE and the NG RAN and / or the N3 interface and / or the N9 interface and / or the N6 interface. In the following, the user plane can also be expressed as U-Plane.

[0084] Moreover, the control plane is a control message sent and received for communication control of UE, etc. The control plane can use the NAS (Non-Access-Stratum) signaling connection between UE and MME for transmission and reception. Moreover, in the case of EPS, the control plane can also use the LTE-Uu interface and the S1-MME interface for transmission and reception. Moreover, in the case of 5GS, the control plane can also use the interface between UE and NG RAN and the N2 interface for transmission and reception. In the following, the control plane can be expressed as Control Plane or C-Plane.

[0085] Furthermore, the user plane (U-Plane, User Plane; UP) may be a communication path for sending and receiving user data, and may be composed of multiple bearers. Furthermore, the control plane (C-Plane, Control Plane; CP) may be a communication path for sending and receiving control messages, and may be composed of multiple bearers. [2.6. Other devices and / or functions and / or terms in this embodiment]

[0086] Next, other devices and / or functions and / or terms and / or identification information and / or messages sent, received, stored and managed by each device are described.

[0087] The network refers to at least a part of the access network_B, the core network_B, and the DN. In addition, one or more devices included in at least a part of the access network_B, the core network_B, and the DN may also be referred to as a network or a network device. That is, the network executing the sending, receiving, and / or processing of messages may mean that a device (network device and / or control device) in the network executes the sending, receiving, and / or processing of messages. Conversely, the device in the network executing the sending, receiving, and / or processing of messages may mean that the network executes the sending, receiving, and / or processing of messages.

[0088] In addition, the SM (session management) message (also called NAS (Non-Access-Stratum) SM message) can be a NAS message used in the process of SM use, or a control message sent and received between UE_A10 and SMF_A230 via AMF_A240. Moreover, the SM message can include: PDU session establishment request message, PDU session establishment accept message, PDU session rejection message, PDU session change request message, PDU session change command message, PDU session change complete message, PDU session change command rejection message, PDU session change rejection message, PDU session release request message, PDU session release rejection message, PDU session release command message, PDU session release complete message, etc.

[0089] In addition, the process used for SM or the SM process may include: PDU session establishment procedure, PDU session modification procedure, and PDU session release procedure. It should be noted that each process may be a process initiated by the UE or a process initiated by the NW (network).

[0090] In addition, the MM (Mobility management) message (or also called NAS MM message) can be a NAS message used for the MM process, or a control message sent and received between UE_A10 and AMF_A240. Moreover, the MM message may include: a registration request message, a registration accept message, a registration reject message, a de-registration request message, a de-registration accept message, a configuration update command message, a configuration update complete message, a service request message, a service accept message, a service reject message, a notification message, a notification response message, etc.

[0091] In addition, the procedures used for MM or MM procedures may include: registration procedure, de-registration procedure, generic UE configuration update procedure, authentication / authorization procedure, service request procedure, paging procedure, and notification procedure.

[0092] In addition, 5GS (5G System) services may be connection services provided using the core network B190. Furthermore, 5GS services may be services different from EPS services or services similar to EPS services.

[0093] In addition, non-5GS services may be services other than 5GS services, and may also include EPS services and / or non-EPS services.

[0094] In addition, the PDN (Packet Data Network) type indicates the type of PDN connection, which includes IPv4, IPv6, IPv4v6, and non-IP. When IPv4 is specified, it indicates that data is sent and received using IPv4. When IPv6 is specified, it indicates that data is sent and received using IPv6. When IPv4v6 is specified, it indicates that data is sent and received using IPv4 or IPv6. When non-IP is specified, it indicates that communication is performed not only by communication using IP, but also by communication methods other than IP.

[0095] In addition, a PDU (Protocol Data Unit) session can be defined as an association between a DN and a UE that provides a PDU connectivity service, but can also be a connectivity established between a UE and an external gateway. The UE establishes a PDU session via the access network_B and the core network_B in the 5GS, thereby enabling the use of the PDU session to send and receive user data with the DN. Here, the external gateway may refer to a UPF, a SCEF, etc. The UE can use the PDU session to send and receive user data with a device such as an application server configured in the DN.

[0096] It should be noted that each device (UE and / or access network device and / or core network device) can also establish a correspondence between one or more identification information and the PDU session for management. It should be noted that these identification information may include one or more of DNN, QoS rules, PDU session type, application identification information, NSI identification information, access network identification information, and SSC mode (also called SSC mode), and may further include other information. Moreover, in the case of establishing multiple PDU sessions, the identification information corresponding to the PDU session establishment may be the same content or different content.

[0097] In addition, DNN (Data Network Name) can be identification information for identifying external networks such as the core network and / or DN. Furthermore, DNN can also be used as information for selecting a gateway such as PGW_A30 / UPF_A235 connected to the core network_B190. Furthermore, DNN can also be equivalent to APN (Access Point Name).

[0098] In addition, the PDU (Protocol Data Unit / Packet Data Unit) session type indicates the type of PDU session, which includes IPv4, IPv6, Ethernet, and Unstructured. When IPv4 is specified, it means that IPv4 is used to send and receive data. When IPv6 is specified, it means that IPv6 is used to send and receive data. When Ethernet is specified, it means that Ethernet frames are sent and received. In addition, Ethernet can indicate that communication without using IP is performed. When Unstructured is specified, it means that Point-to-Point (P2P) tunnel technology is used to send and receive data to an application server in the DN. As a P2P tunnel technology, for example, UDP / IP encapsulation technology can also be used. It should be noted that in addition to the above, IP can also be included in the PDU session type. IP can be specified when the UE can use both IPv4 and IPv6.

[0099] In addition, PLMN (Public land mobile network) is a communication network that provides mobile wireless communication services. PLMN is a network managed by an operator as a (mobile) communication operator, and the operator can be identified by PLMNID. In this article, PLMN can also mean PLMN ID. The PLMN that is consistent with the MCC (Mobile Country Code) and MNC (Mobile Network Code) of the UE's IMSI (International Mobile Subscriber Identity) can be the Home PLMN (Home PLMN: HPLMN). PLMN can also mean the core network.

[0100] Furthermore, the UE may maintain an equivalent HPLMN list (Equivalent HPLMN list) for identifying one or more EHPLMNs (Equivalent HPLMN) in the USIM. A PLMN different from the HPLMN and / or the EHPLMN may be a VPLMN (Visited PLMN).

[0101] The PLMN to which the UE successfully logs in may be an RPLMN (Registered PLMN). Each device may receive and / or maintain and / or store from the RPLMN an equivalent HPLMN list (Equivalent HPLMN list) for identifying one or more EPLMNs (Equivalent PLMNs) that can be used equivalently to the RPLMN in the PLMN selection of the UE.

[0102] The current PLMN may be a PLMN requested by the UE, and / or a PLMN selected by the UE, and / or an RPLMN, and / or a PLMN allowed by the network, and / or a PLMN to which a core network device that sends and receives messages belongs.

[0103] The requested PLMN means the destination network of the message when the UE sends a message. Specifically, it can be the PLMN selected by the UE when the UE sends a message. The requested PLMN is the PLMN requested by the UE, which can be the current PLMN. In addition, the PLMN requested by the UE in the logged-in state can also be the logged-in PLMN.

[0104] NPN (Non-public network) refers to a network with non-public specifications as its purpose. There are two types of NPN: SNPN (Stand-alone non-public network) and PNI-NPN (Public network integrated non-public network). SNPN and PNI-NPN can be deployed to 5GS. In this article, the case shown as NPN may refer to SNPN or PNI-NPN or both.

[0105] SNPN (Stand-alone non-public network) is a network operated by an NPN operator and does not rely on the network functions provided by the PLMN. In other words, SNPN is a network independent of the PLMN and can only be accessed by specific UEs. SNPN can be identified by PLMN ID and NID (Network identifier).

[0106] Here, the PLMN ID identifying the SNPN does not need to be unique. For example, more than one PLMN ID reserved for use in a private network may also be used for the NPN.

[0107] In addition, SNPN (Stand-alone Non-Public Network) is a network identified by a SNPN ID composed of a combination of a PLMN ID and a NID (Network identifier), and only allows specific UEs to connect. SNPN can also mean a core network. Here, the UE allowed to connect to the SNPN can be a SNPN-enabled UE.

[0108] Furthermore, the UE may maintain an equivalent SNPN list (Equivalent SNPN list) for identifying one or more ESNPNs (Equivalent SNPNs) in the USIM. A SNPN different from the HSNPN and / or the ESNPN may be a VPLMN (Visited PLMN).

[0109] The SNPN to which the UE successfully logs in may be an RSNPN (Registered SNPN). Each device may receive and / or maintain and / or store from the RSNPN an equivalent SNPN list (Equivalent SNPNlist) that can be used equivalently to the RSNPN in the UE's PLMN selection or SNPN selection and is used to identify one or more ESNPNs (Equivalent PLMN).

[0110] PNI-NPN (Public network integrated non-public network) refers to an NPN deployed with the support of PLMN. In other words, it is a network that uses the functions of PLMN to implement non-public specifications.

[0111] The MS (UE) can access the onboarded SNPN using the default UE credentials through the onboarding services in SNPN.

[0112] The registration process for the onboarding service of SNPN may be an initial registration for onboarding services in SNPN. Moreover, or alternatively, the registration process for the onboarding service of SNPN may also be a registration process for mobile-based registration update when the UE logs in for the onboarding service of SNPN. The registration process for the onboarding service of SNPN may also be expressed as SNPN onboarding registration.

[0113] During the login process of the loading service for SNPN, MM-based slice admission control can be performed on the S-NSSAI for the loading service for SNPN without going through the AMF or NF in the core network.

[0114] In addition, a network slice (NS) refers to a logical network that provides specific network capabilities and network characteristics. UE and / or network can support network slicing (NW slicing; NS) in 5GS. Sometimes network slicing is also referred to as slicing.

[0115] In addition, a network slice instance (NSI) refers to a network slice formed and configured by a collection of instances (entities) of network functions (NFs) and required resources. Here, NF refers to a processing function in a network, which is adopted or defined in 3GPP. NSI is an entity that constitutes one or more NSs within the core network_B. In addition, NSI can be composed of a virtual NF (Network Function) generated using NST (Network Slice Template).

[0116] Here, NST refers to a logical expression of one or more NFs associated with a resource request for providing the requested communication service or capability. That is, NSI may refer to a collection within the core network B190 composed of multiple NFs. In addition, NSI may be a logical network configured to divide the user data sent according to services, etc. More than one NF may be configured in NS. The NF configured in NS may be a device shared with other NSs, or may not be a device shared with other NSs.

[0117] The UE and / or the device in the network can be assigned to one or more NSs based on the login information such as NSSAI and / or S-NSSAI and / or UE usage type (UE usage type) and / or one or more NSI IDs and / or APN. It should be noted that the UE usage type is a parameter value included in the login information of the UE for identifying the NSI. The UE usage type can be stored in the HSS. The AMF can select the SMF and UPF based on the UE usage type.

[0118] In addition, S-NSSAI (Single Network Slice Selection Assistance information) is information for identifying NS. S-NSSAI can be composed of only SST (Slice / Servicetype: Slice / Service type), or it can be composed of both SST and SD (Slice Differentiator: Slice Differentiator). Here, SST refers to information indicating the expected actions of NS in terms of functions and services. In addition, SD may be information that interpolates SST when selecting an NSI from multiple NSIs shown in SST. S-NSSAI may be information specific to each PLMN or SNPN, or it may be standard information common between PLMNs or SNPNs.

[0119] In addition, S-NSSAI can be sent and received between devices using the S-NSSAI IE of 5GS. In this case, the S-NSSAI can be composed of S-NSSAI (SST and / or SD) associated with the current PLMN or SNPN and / or S-NSSAI (SST and / or SD) of the HPLMN (if any. For example, when the UE is roaming or the current PLMN or SNPN is a VPLMN or SNPN).

[0120] In addition, the network may store more than one S-NSSAI in the UE's login information as the default S-NSSAI. It should be noted that when the S-NSSAI is the default S-NSSAI, when the UE does not send a valid S-NSSAI to the network in the login request message, the network may provide the NS related to the UE.

[0121] In addition, the S-NSSAI sent and received between the UE and the NW can also be expressed as an S-NSSAI IE (Information element). Moreover, the S-NSSAI IE sent and received between the UE and the NW can be composed of an S-NSSAI composed of an SST and / or SD of a logged-in PLMN or SNPN and / or an SST and / or SD representing an S-NSSAI of an HPLMN or SNPN mapped with the S-NSSAI. One or more S-NSSAIs stored by the UE and / or NW can be composed of an SST and / or SD, or can be composed of an S-NSSAI composed of an SST and / or SD and / or an SST and / or SD representing an S-NSSAI of an HPLMN mapped with the S-NSSAI.

[0122] In addition, NSSAI (Network Slice Selection Assistance Information) is a collection of S-NSSAI. Each S-NSSAI included in NSSAI is information for assisting the access network or core network to select NSI. The UE can store the NSSAI allowed by the network for each PLMN or SNPN. In addition, NSSAI can be information for selecting AMF. The UE can also apply each NSSAI (allowed NSSAI and / or configured NSSAI and / or rejected NSSAI and / or pendingNSSAI) to PLMN and EPLMN or SNPN and ESNPN.

[0123] The mapped S-NSSAI is the S-NSSAI of the HPLMN mapped to the S-NSSAI of the logged-in PLMN in the roaming scenario. The UE may store one or more set NSSAIs and mapped S-NSSAIs mapped to the S-NSSAI included in the allowed NSSAI of each access type. Moreover, the UE may also store one or more mapped S-NSSAIs of the S-NSSAI included in the rejected NSSAI and / or pending NSSAI.

[0124] In the case of a roaming scenario supporting SNPN, the mapped S-NSSAI may be the S-NSSAI of the HSNPN mapped to the S-NSSAI of the logged-in SNPN.

[0125] The Network Slice-Specific Authentication and Authorization (NSSAA) function refers to the function used to implement network slice-specific authentication and authorization. In the network slice-specific authentication and authorization, the UE can be authenticated and authorized outside the core network such as a third party. The PLMN or SNPN and the network device with the NSSAA function can perform the NSSAA process on a certain S-NSSAI based on the UE's login information. Moreover, the UE with the NSSAA function can manage, store, and send and receive pending NSSAI and third rejected NSSAI. In this article, NSSAA is sometimes referred to as the network slice-specific authentication and authorization process, the authentication and authorization process.

[0126] The S-NSSAI requiring NSSAA is an S-NSSAI requiring NSSAA managed by the core network and / or the core network device. Moreover, during roaming, the S-NSSAI requiring NSSAA may also be an S-NSSAI other than the HPLMN or HSNPN to which the S-NSSAI is mapped, which is an S-NSSAI of the HPLMN or HSNPN requiring NSSAA managed by the core network and / or the core network device.

[0127] The core network and / or the core network device may store the S-NSSAI that requires NSSAA by establishing a correspondence between information indicating whether S-NSSAI and NSSAA are required. The core network and / or the core network device may also establish a correspondence between the S-NSSAI that requires NSSAA and information indicating whether NSSAA has been completed or information indicating the status of allowing or successfully completing NSSAA for storage. The core network and / or the core network device may manage the S-NSSAI that requires NSSAA as information that is not related to the access network.

[0128] In addition, the configured NSSAI is the NSSAI provided to and stored in the UE. The UE may store the configured NSSAI for each PLMN or SNPN. The UE may also store the configured NSSAI in association with the PLMN or SNPN.

[0129] It should be noted that, in this article, the setting NSSAI corresponding to the PLMN can be expressed as the setting NSSAI for the PLMN or the setting NSSAI for the PLMN or the setting NSSAI for the PLMN, and the setting NSSAI associated with the PLMN. Similarly, the setting NSSAI corresponding to the SNPN can be expressed as the setting NSSAI for the SNPN or the setting NSSAI for the SNPN or the setting NSSAI for the SNPN, and the setting NSSAI associated with the SNPN.

[0130] In addition, the UE may not establish an association with the PLMN, but store the settings NSSAI that are valid for all PLMNs, and may set such settings NSSAI as the "default settings NSSAI". Similarly, the UE may not establish an association with the SNPN, but store the settings NSSAI that are valid for all SNPNs, and may set such settings NSSAI as the "default settings NSSAI". The UE may not establish an association with either the PLMN or the SNPN, but store all valid settings NSSAI for PLMNs and SNPNs, and may set such settings NSSAI as the "default settings NSSAI".

[0131] NSSAI can be set up to associate with multiple PLMNs or SNPNs. These multiple PLMNs can be EPLMNs, and multiple SNPNs can also be ESNPNs.

[0132] The configured NSSAI may be information set by the network (or PLMN or SNPN). The S-NSSAI included in the configured NSSAI may be expressed as configured S-NSSAI (configured S-NSSAI). The configured S-NSSAI may be sent and received using the S-NSSAI IE, in which case the configured S-NSSAI may be constructed to include S-NSSAI (SST and / or SD) and mapped S-NSSAI (SST of the mapped HPLMN or SNPN and / or SD of the mapped HPLMN or SNPN) (if any. For example, when the UE is roaming or the associated PLMN or SNPN is a VPLMN or VSNPN).

[0133] Alternatively, the S-NSSAI (SST and / or SD) of the PLMN or SNPN and the S-NSSAI (SST and / or SD) of the HPLMN or SNPN may be handled independently. Specifically, the setting S-NSSAI of the PLMN or SNPN may be expressed as "setting S-NSSAI for PLMN or SNPN" or "setting S-NSSAI of PLMN or SNPN" or "setting S-NSSAI for PLMN or SNPN".

[0134] Moreover, one or more S-NSSAIs of the HPLMN or HSNPN mapped with the setting S-NSSAI can also be expressed as "one or more mapping S-NSSAIs of the setting NSSAI for the PLMN or SNPN" or "one or more mapping S-NSSAIs of the setting NSSAI of the PLMN or SNPN".

[0135] In other words, the UE may store the "configured NSSAI of the current PLMN or SNPN" that constitutes the S-NSSAI of the current PLMN or SNPN, and when roaming, may also store "one or more mapped S-NSSAIs for the configured NSSAI of the current PLMN or SNPN". The one or more mapped S-NSSAIs for the configured NSSAI may be a mapped S-NSSAI (mapped S-NSSAI(s) for the configured NSSAI) of 3GPP.

[0136] The NSSAI setting may be updated by the NW at any time, and based on the update, the updated NSSAI setting may be sent from the NW to the UE.

[0137] In addition, the requested NSSAI is the NSSAI provided by the UE to the network during the login process. During the login process, the S-NSSAI included in the requested NSSAI sent by the UE may be the S-NSSAI included in the allowed NSSAI or the set NSSAI stored by the UE.

[0138] The requested NSSAI may be information indicating the network slice requested by the UE. The S-NSSAI included in the requested NSSAI may be expressed as a requested S-NSSAI. For example, the requested NSSAI may be included in an RRC (Radio Resource Control) message for transmission and reception, and the RRC message includes a NAS message or a NAS (Non-Access-Stratum) message sent from the UE to the network, such as a login request message or a PDU session establishment request message. Here, in the case of roaming, the requested NSSAI may include the S-NSSAI of the VPLMN and the S-NSSAI of the mapped HPLMN. In other words, the S-NSSAI included in the requested NSSAI (requested S-NSSAI) may be composed of an S-NSSAI and a mapped S-NSSAI.

[0139] The requested NSSAI may be information including one or more S-NSSAIs corresponding to the network slices requested by the UE. It should be noted that, here, the network slice requested by the UE may refer to the network slice that the UE wants to use, or it may be the network slice that the UE requests to be allowed to use by the network. The S-NSSAI included in the requested NSSAI may be the S-NSSAI included in the set NSSAI corresponding to the current PLMN, or it may be the S-NSSAI included in the allowed NSSAI corresponding to the current PLMN.

[0140] In other words, the request NSSAI may include one or more S-NSSAIs included in the set NSSAI corresponding to the current PLMN or one or more S-NSSAIs included in the allowed NSSAI corresponding to the current PLMN, or a combination of the two. More specifically, the allowed NSSAI corresponding to the current PLMN may refer to the allowed NSSAI corresponding to the current PLMN and the current access type. Moreover, the request NSSAI may also be the request NSSAI of 5GS.

[0141] It should be noted that the S-NSSAI included in the requested NSSAI may be an S-NSSAI not included in the rejected NSSAI stored by the UE and associated with the current PLMN or SNPN and / or an S-NSSAI not included in the pending NSSAI stored by the UE and associated with the current PLMN or SNPN, or an S-NSSAI not included in the fourth rejected NSSAI stored by the UE and associated with the current PLMN or SNPN.

[0142] Furthermore, the S-NSSAI included in the request NSSAI may be an S-NSSAI for which a backoff timer associated with the S-NSSAI and / or a mapped S-NSSAI of the S-NSSAI in the UE is not executed.

[0143] In addition, allowed NSSAI is information indicating one or more network slices that the UE is allowed to connect to. In other words, allowed NSSAI is information identifying the network slices that the network is allowed to connect to the UE. Allowed NSSAI can be allowed NSSAI stored by the UE and / or NW, or it can be allowed NSSAI sent from the NW to the UE. In this case, allowed NSSAI can refer to the allowed NSSAI IE of 3GPP.

[0144] The Allowed NSSAI IE sent from the NW to the UE may include a list of S-NSSAIs of the current PLMN or SNPN that are valid for the current PLMN or SNPN when not roaming.

[0145] When roaming, the Allowed NSSAI IE sent from the NW to the UE may include a list of S-NSSAIs of the current PLMN or SNPN that are valid for the current PLMN or SNPN and a list of mapped S-NSSAIs of the HPLMN or HSNPN that are further mapped with the S-NSSAI of the current PLMN or SNPN.

[0146] It should be noted that the list of S-NSSAIs of the current PLMN or SNPN that are valid for the current PLMN or SNPN and included in the allowed NSSAI IE may also be referred to as allowed NSSAIs, and the list of mapped S-NSSAIs of the S-NSSAIs of the HPLMN or HSNPN that are mapped with the S-NSSAIs of the current PLMN or SNPN may be referred to as the list of mapped S-NSSAIs of allowed NSSAIs. Here, the list of mapped S-NSSAIs of allowed NSSAIs may be the mapped S-NSSAI(s) for the allowed NSSAI for a PLMN of 3GPP. Similarly, allowed NSSAI may also refer to the allowed NSSAI for a PLMN or an SNPN of 3GPP.

[0147] The UE and / or NW may store and manage the allowed NSSAI as UE information for each access (3GPP access or non-3GPP access). The UE and / or NW may also manage the allowed NSSAI in association with the login area.

[0148] Moreover, the UE and / or NW may establish an association with the PLMN or SNPN to store and manage the allowed NSSAI as UE information. The allowed NSSAI may also be associated with multiple PLMNs, which may be EPLMNs, and the multiple SNPNs may also be ESNPNs.

[0149] It should be noted that, in this article, the allowed NSSAI that corresponds to the PLMN or SNPN and the access type can be expressed as "the allowed NSSAI for the PLMN or SNPN and the access type" or "the allowed NSSAI for the access type of the PLMN or SNPN".

[0150] The S-NSSAI included in the allowed NSSAI can be expressed as allowed S-NSSAI (allowed S-NSSAI). Allowed S-NSSAI can be transmitted and received using the S-NSSAI IE. In this case, allowed S-NSSAI (SST and / or SD) can be constructed to include S-NSSAI and mapped S-NSSAI (SST of the mapped HPLMN or SNPN and / or SD of the mapped HPLMN or SNPN) (if any. For example, when the UE is roaming or the associated PLMN or SNPN is a VPLMN or VSNPN).

[0151] Alternatively, the S-NSSAI (SST and / or SD) of the PLMN or SNPN and the S-NSSAI (SST of the mapped HPLMN or SNPN and / or SD of the mapped HPLMN or SNPN) of the HPLMN or SNPN may be processed independently. Specifically, the allowed S-NSSAI of the PLMN or SNPN may be expressed as "allowed S-NSSAI for PLMN or SNPN" or "allowed S-NSSAI of PLMN or SNPN" or "allowed S-NSSAI for PLMN or SNPN".

[0152] Moreover, one or more S-NSSAIs of the HPLMN or HSNPN mapped with the allowed S-NSSAI can also be expressed as "one or more mapped S-NSSAIs for the allowed NSSAIs of the PLMN or SNPN" or "one or more mapped S-NSSAIs for the allowed NSSAIs of the PLMN or SNPN".

[0153] In addition, the rejected NSSAI is information indicating one or more network slices that the UE is not allowed to use or request. In other words, the rejected NSSAI is information identifying the network slices that the network is not allowed to connect to the UE. The rejected NSSAI sent from the NW to the UE may be included in the rejected NSSAI IE or the extended rejected NSSAI IE.

[0154] The rejected NSSAI sent and received using the rejected NSSAI IE may be information including a combination of one or more S-NSSAI (SST and / or SD) and a rejection reason value (rejected S-NSSAI). The rejected NSSAI sent and received using the extended rejected NSSAI IE (Extendedrejected NSSAI IE) may be information including a combination of one or more S-NSSAI (SST and / or SD), a mapped S-NSSAI (SST of the mapped HPLMN or SNPN and / or SD of the mapped HPLMN or SNPN) (if any. For example, when the UE is roaming or the associated PLMN or SNPN is a VPLMN or VSNPN) and a rejection reason value (Rejected S-NSSAI).

[0155] The extended rejected NSSAI IE may include one or more sets of rejected SS-NSSA and / or NSSAI (Partial extended Rejected NSSAI list of 5GS: partial extended rejected NSSAI list of 5GS), and the set of rejected S-NSSAI may include information indicating the type of the set.

[0156] The information indicating the type of a set may be, for example, information indicating that the set includes one or more reject S-NSSAI (SST and / or SD) together with an associated backoff timer value, or information indicating that the set does not include an associated backoff timer value but includes one or more reject S-NSSAI (SST and / or SD).

[0157] When the information indicating the type of the set is information indicating that the set includes one or more reject S-NSSAIs together with the associated backoff timer value, the set of reject S-NSSAIs may also include the backoff timer value.

[0158] Here, the S-NSSAI included in the rejected NSSAI may be associated with a PLMN ID or a SNPN ID. It should be noted that the PLMN or SNPN represented by the PLMN ID or SNPN ID associated with the S-NSSAI included in the rejected NSSAI may be the current PLMN or the current SNPN. Alternatively, the PLMNID or SNPN ID associated with the S-NSSAI included in the rejected NSSAI may be information representing the HPLMN or HSNPN regardless of the current PLMN or SNPN.

[0159] Here, the rejection reason value is information indicating the reason why the network rejects the corresponding S-NSSAI or the combination of the corresponding S-NSSAI and the mapped S-NSSAI (if any). The UE and / or the network may establish a corresponding rejection reason value with each S-NSSA or the combination of the corresponding S-NSSAI and the mapped S-NSSAI, and store and manage each S-NSSAI and / or the mapped S-NSSAI (if any) as an appropriate rejected NSSAI and / or a mapped S-NSSAI of the rejected NSSAI.

[0160] Moreover, the rejection of NSSAI may also be included in a NAS message sent from the network to the UE, such as a login acceptance message, a setting update command, a login rejection message, or an RRC message including a NAS message. The S-NSSAI included in the rejection of NSSAI may be expressed as a rejection of S-NSSAI.

[0161] The UE may use the Reject NSSAI IE to send a Reject NSSAI when roaming, or may use the Extended Reject NSSAI IE to send a Reject NSSAI. The Extended Reject NSSAI IE may include one or more Reject S-NSSAI (IE) consisting of the S-NSSAI (SST and / or SD) of the current PLMN or SNPN, the mapped S-NSSAI (SST of the mapped HPLMN or SNPN and / or the SD of the mapped HPLMN or SNPN), and the Reject Reason value, which may be understood as the UE requesting the NW to request the received S-NSSAI of the current PLMN or SNPN and the received mapped S-NSSAI together and being rejected. On the other hand, the Reject NSSAI IE may also include a Reject S-NSSAI IE based on the S-NSSAI of the current PLMN or SNPN and the Reject Reason value, which may also be understood as the UE requesting the NW to receive the S-NSSAI of the current PLMN or SNPN or the S-NSSAI associated with the S-NSSAI of the HPLMN or HSNPN and being rejected.

[0162] The reject NSSAI may be any one of the first to fourth reject NSSAIs, one or more mapped S-NSSAIs for the first reject NSSAI, one or more mapped S-NSSAIs for the second reject NSSAI, and one or more mapped S-NSSAIs for the fourth reject NSSAI, or a combination of these. The S-NSSAI included in the reject NSSAI may be expressed as the reject S-NSSAI. The reject S-NSSAI may be sent and received between devices using the S-NSSAI IE, and the S-NSSAI IE indicating the reject NSSAI may be constructed to include the S-NSSAI and the mapped S-NSSAI.

[0163] The UE and / or NW may associate the PLMN or SNPN to store and manage the rejected NSSAI as UE information. The rejected NSSAI may also be associated with one or more other PLMNs or SNPNs, where the one or more other PLMNs may be EPLMNs, and the one or more other SNPNs may be ESNPNs.

[0164] It should be noted that, in this article, the rejection NSSAI associated with the PLMN or SNPN may also be expressed as a rejection NSSAI for the PLMN or SNPN or a rejection NSSAI for the PLMN or SNPN or a rejection NSSAI for the PLMN or SNPN. The UE and / or NW may also store the second rejection NSSAI and / or the second rejection S-NSSAI in association with the login area. The UE and / or NW may also store the second rejection NSSAI and / or the second rejection S-NSSAI in association with the access type and / or login area.

[0165] Here, the first rejected NSSAI is a set of one or more S-NSSAIs that are not available in the current PLMN or the current SNPN. The first rejected NSSAI may be a rejected NSSAI for the current PLMN or SNPN of 5GS, or a rejected S-NSSAI for the current PLMN or SNPN, or an S-NSSAI included in the rejected NSSAI for the current PLMN or SNPN, or a mapped S-NSSAI (s) for rejected S-NSSAI for the current PLMN or SNPN, or an S-NSSAI included in the mapped S-NSSAI for rejected S-NSSAI for the current PLMN or SNPN. The list (set) of mapped S-NSSAIs for the first rejected NSSAI may be one or more mapped S-NSSAIs for the first rejected NSSAI, or may be a mapped S-NSSAI (mapped S-NSSAI(s) for the rejected NSSAI for the current PLMN or SNPN) of 5GS. The first rejected NSSAI may be a rejected NSSAI stored by the UE or NW, or may be a rejected NSSAI sent from the NW to the UE.

[0166] In the case where the first rejection NSSAI is a rejection NSSAI sent from the NW to the UE, the S-NSSAI included in the request NSSAI sent by the UE to the NW includes one or more S-NSSAIs that are rejected due to unavailability in the current PLMN or the current SNPN. In this case, the first rejection NSSAI may be information including a combination of one or more S-NSSAIs and a rejection reason value. The rejection reason value at this time may be "S-NSSAI not available in the current PLMN or SNPN", or it may be information indicating that the S-NSSAI corresponding to the rejection reason value is unavailable in the current PLMN or SNPN. The S-NSSAI included in the first rejection NSSAI may be expressed as the first rejection S-NSSAI.

[0167] In the case where the first rejection NSSAI is a rejection NSSAI sent from the NW to the UE, the first rejection NSSAI may be included in a rejection NSSAI IE or an extended rejection NSSAI IE for transmission and reception. The rejection NSSAI IE or the extended rejection NSSAI IE may include a combination of the S-NSSAI of at least one current PLMN or SNPN and a rejection reason value. In the case where the UE is roaming, the above combination may also include a mapped S-NSSAI as the S-NSSAI of the HPLMN.

[0168] In other words, in the roaming case, the first rejection NSSAI sent from the NW to the UE may include a combination of the S-NSSAI of at least one current PLMN or SNPN, the mapped S-NSSAI, and the rejection reason value.

[0169] The first rejection NSSAI can be applied to the entire PLMN or SNPN. The UE and / or NW can regard the first rejection NSSAI and the S-NSSAI included in the first rejection NSSAI as information that does not depend on the access type. That is, the first rejection NSSAI can be information that is valid for 3GPP access (3GPP access) and non-3GPP access (non-3GPP access).

[0170] The UE may delete the first rejection NSSAI from the storage when the UE switches to the non-logged-in state for the current PLMN in both the 3GPP access and the non-3GPP access. In other words, when the UE switches to the non-logged-in state for the current PLMN via a certain access, or successfully logs in to a new PLMN via a certain access, or fails to log in to the new PLMN via a certain access and switches to the non-logged-in state, and when the UE is in a state (non-logged-in state) without logging in through the access of the other party, the UE deletes the first rejection NSSAI. That is, when the UE switches to the non-logged-in state for the current PLMN via a certain access, and when the UE is in a state (logged-in state) in which the UE has logged in to the current PLMN via the access of the other party, the UE may not delete the first rejection NSSAI.

[0171] The S-NSSAI or the first rejected NSSAI included in the first rejected NSSAI may be the S-NSSAI of the current PLMN. In other words, the S-NSSAI or the first rejected NSSAI included in the first rejected NSSAI may be stored and / or managed and / or transmitted and received only in association with the current PLMNID or SNPN ID. Moreover / or, the S-NSSAI included in the first rejected NSSAI may be the S-NSSAI of the HPLMN or the S-NSSAI of the current PLMN.

[0172] The second rejected NSSAI is a set of one or more S-NSSAIs that are not available in the current registration area. The second rejected NSSAI can be a rejected NSSAI for the current registration area of ​​5GS, or a mapped S-NSSAI (mapped S-NSSAI(s)for rejected NSSAI for the current registration area) for the rejected NSSAI for the current registration area, or an S-NSSAI included in the mapped S-NSSAI for the rejected NSSAI for the current registration area. The list (set) of mapped S-NSSAIs for the second rejected NSSAI can be one or more mapped S-NSSAIs for the second rejected NSSAI, or a mapped S-NSSAI (mapped S-NSSAI(s)for therejected NSSAI for the current registration area) for the rejected NSSAI of 5GS for the current registration area. The second rejected NSSAI can be a rejected NSSAI stored by the UE or NW, or a rejected NSSAI sent from the NW to the UE. In the case where the second rejection NSSAI is a rejection NSSAI sent from the NW to the UE, the second rejection NSSAI may be information including a combination of one or more S-NSSAIs and a reason value. The rejection reason value at this time may be "S-NSSAI not available in the current registration area", or it may be information indicating that the S-NSSAI corresponding to the reason value is not available in the current registration area. The S-NSSAI included in the second rejection NSSAI may be expressed as a second rejection S-NSSAI.

[0173] In the case where the second rejection NSSAI is a rejection NSSAI sent from the NW to the UE, the S-NSSAI included in the request NSSAI by the UE includes one or more S-NSSAIs that are rejected because they are not available in the current registration area. In this case, the second rejection NSSAI may be included in the rejection NSSAI IE or the extended rejection NSSAI IE for transmission and reception. The rejection NSSAI IE or the extended rejection NSSAI IE may include a combination of the S-NSSAI of at least one current PLMN or SNPN and a rejection reason value. In the case where the UE is roaming, the above combination may also include a mapped S-NSSAI as the S-NSSAI of the HPLMN.

[0174] In other words, in the roaming case, the second rejection NSSAI sent from the NW to the UE may include a combination of the S-NSSAI of at least one current PLMN or SNPN, the mapped S-NSSAI, and the rejection reason value.

[0175] The second rejection NSSAI may be valid within the current registration area or may be applied to the current registration area. The UE and / or NW may regard the second rejection NSSAI and the S-NSSAI included in the second rejection NSSAI as information for each access type. That is, the second rejection NSSAI may be information valid for 3GPP access or non-3GPP access, respectively. That is, the UE may delete the second rejection NSSAI associated with a certain access from the storage once it switches to the non-logged-in state for the access.

[0176] The S-NSSAI or the second rejected NSSAI included in the second rejected NSSAI may be the S-NSSAI of the current PLMN. In other words, the S-NSSAI or the second rejected NSSAI included in the second rejected NSSAI may be stored and / or managed and / or transmitted and received only in association with the current PLMNID or SNPN ID. Alternatively, the S-NSSAI included in the second rejected NSSAI may be the S-NSSAI of the HPLMN or the S-NSSAI of the current PLMN.

[0177] The third rejected NSSAI is an S-NSSAI that requires NSSAA, and is a set of one or more S-NSSAIs for which the NSSAA fails or is canceled for the S-NSSAI. The third rejected NSSAI may be an NSSAI stored by the UE and / or NW, or it may be an NSSAI sent and received between the NW and the UE. In the case where the third rejected NSSAI is sent from the NW to the UE, the third rejected NSSAI may be information including a combination of one or more S-NSSAIs and a rejection reason value. The rejection reason value at this time may be "S-NSSAI not available due to the failed or revoked NSSAI", or it may be information indicating the failure or cancellation of the NSSAI for the S-NSSAI corresponding to the rejection reason value. The S-NSSAI included in the third rejected NSSAI may be expressed as a third rejected S-NSSAI.

[0178] In the case where the third Reject NSSAI is the NSSAI sent from the NW to the UE, the third Reject NSSAI may be transmitted and received using the Reject NSSAI IE or the Extended Reject NSSAI IE.

[0179] The third rejection NSSAI can be applied to logging into a PLMN or logging into a SNPN, or can be applied to logging into a PLMN and / or an EPLMN, or can be applied to logging into a SNPN and / or an ESNPN, or can be applied to all PLMNs or SNPNs. The third rejection NSSAI being applied to all PLMNs can mean that the third rejection NSSAI is not associated with a PLMN, or can mean that the third rejection NSSAI is associated with an HPLMN or an HSNPN.

[0180] Moreover, the UE and / or NW may regard the third rejected NSSAI and the third rejected S-NSSAI as information that is independent of the access type. That is, the third rejected NSSAI may be information that is valid for 3GPP access and non-3GPP access. The third rejected NSSAI may be an NSSAI different from the rejected NSSAI. The third rejected NSSAI may also be the first rejected NSSAI. The third rejected NSSAI may be a rejected NSSAI for the failed or revoked NSSAA of the 5GS, or a rejected S-NSSAI for the failed or revoked NSSAA, or an S-NSSAI included in the rejected NSSAI for the failed or revoked NSSAA.

[0181] The third rejection NSSAI is a rejection NSSAI for the UE to identify the slices rejected by the core network due to NSSAA failure or cancellation. Specifically, while storing the third rejection NSSAI, the UE does not start the login request process for the S-NSSAI included in the third rejection NSSAI. The third rejection NSSAI may be identification information including one or more S-NSSAIs received from the core network in correspondence with the rejection reason value indicating the failure of NSSAA.

[0182] The third rejection NSSAI is information that is independent of the access type. Specifically, when the UE stores the third rejection NSSAI, the UE may not attempt to send a login request message including the S-NSSAI included in the third rejection NSSAI to both 3GPP access and non-3GPP access. Alternatively, the UE can send a login request message including the S-NSSAI included in the third rejection NSSAI based on the UE policy.

[0183] Alternatively, the UE may delete the third reject NSSAI based on the UE policy and transition to a state where a login request message including the S-NSSAI included in the third reject NSSAI can be sent. In other words, in the case where the UE sends a login request message including the S-NSSAI included in the third reject NSSAI based on the UE policy, the UE may delete the S-NSSAI from the third reject NSSAI.

[0184] When roaming, the S-NSSAI included in the third rejecting NSSAI may be the S-NSSAI of the HPLMN. In other words, the third rejecting NSSAI received by the UE from the VPLMN or VSNPN may include the S-NSSAI of the HPLMN or HSNPN.

[0185] In other words, the UE and / or each device may store the "third rejected NSSAI" constituting the S-NSSAI of the HPLMN or HSNPN. That is, even when roaming, the "third rejected NSSAI" may be stored without being associated with the mapped S-NSSAI.

[0186] The fourth rejected NSSAI is information including one or more S-NSSAIs reaching the maximum number of UEs per network slice. The fourth rejected NSSAI can be the NSSAI stored by the UE and / or NW, or it can be the NSSAI sent from the NW to the UE.

[0187] The fourth rejected NSSAI may be a rejected NSSAI for the maximum number of UEs reached of 5GS, a rejected S-NSSAI for the maximum number of UEs reached, an S-NSSAI included in the rejected NSSAI for the maximum number of UEs reached, a mapped S-NSSAI (mapped S-NSSAI(s) for the maximum number of UEs reached), or an S-NSSAI included in the mapped S-NSSAI for the maximum number of UEs reached. The list (set) of mapped S-NSSAIs for the fourth rejected NSSAI may be one or more mapped S-NSSAIs for the fourth rejected NSSAI, or a mapped S-NSSAI for the maximum number of UEs reached of 5GS.

[0188] In the case where the fourth rejection NSSAI is sent from the NW to the UE, the fourth rejection NSSAI may be information including one or more information including at least one S-NSSAI (SST and / or SD), a mapped S-NSSAI (SST and / or SD) (if present), a rejection reason value, and a backoff timer value. The rejection reason value at this time may be "S-NSSAI not available due to maximum number of UEs reached for each network slice", or it may be information indicating that the maximum number of UEs that can be notified of the S-NSSAI corresponding to the rejection reason value or allowed as the allowed NSSAI has been reached.

[0189] Here, the rejection reason value may be the rejection reason value included in the rejection NSSAI. Moreover, at this time, the value of the backoff timer may also be information indicating the period during which the UE is prohibited from sending an MM message using one or more S-NSSAIs associated with the value of the backoff timer and / or one or more mapped S-NSSAIs associated with the current PLMN or SNPN.

[0190] The fourth rejection NSSAI can be applied to the registered PLMN and / or EPLMN, and can also be applied to the registered SNPN and / or ESNPN, and can also be applied to one or more PLMNs or SNPNs described in the TAI included in the TA list (TAI list or registration area).

[0191] The UE and / or the NW may regard the fourth rejected NSSAI and the S-NSSAI included in the fourth rejected NSSAI as information for each access type.

[0192] In the case where the fourth Reject NSSAI is the NSSAI sent from the NW to the UE, the fourth Reject NSSAI may be sent and received using the extended Reject NSSAI IE.

[0193] In case the first to fourth Reject NSSAIs are transmitted and received using the Reject NSSAI IE or the Extended Reject NSSAI IE, a list of rejected S-NSSAIs may be included in the Reject NSSAI IE and the Extended Reject NSSAI IE.

[0194] When the first to fourth reject NSSAIs are sent and received using the reject NSSAI IE, the list of rejected S-NSSAIs included in the reject NSSAI IE may be one or more reject S-NSSAIs of 5GS. The reject S-NSSAI may be composed of the S-NSSAI (SST and / or SD) of the current PLMN or SNPN and the corresponding rejection reason value.

[0195] In the case where the first to fourth Reject NSSAIs are transmitted and received using the Extended Reject NSSAI IE, the list of rejected S-NSSAIs included in the Extended Reject NSSAI IE may be a partial Extended Reject NSSAI list of 5GS.

[0196] The list of rejected S-NSSAIs includes a first type of list that does not include a backoff timer value, and a second type of list that includes a backoff timer value applied to all S-NSSAIs included in the list of rejected S-NSSAIs. The extended reject NSSAI IE may be composed of one or more first type of lists and / or one or more second lists.

[0197] The first type of list may contain one or more information indicating that the list is of the first type and one or more 5GS rejection S-NSSAI. The rejection S-NSSAI may contain the S-NSSAI (SST and / or SD) of the current PLMN or SNPN and the corresponding rejection reason value. Moreover, the rejection S-NSSAI may contain a mapping S-NSSAI (SST and / or SD).

[0198] The information indicating that the list is of the first type may mean that the list does not include one or more S-NSSAIs together with the corresponding backoff timer values. In other words, it may also mean that the list does not include backoff timer values ​​corresponding to one or more S-NSSAIs included in the list.

[0199] The second type of list may include information indicating that the list is of the second type, a backoff timer value, and one or more 5GS rejection S-NSSAIs. The rejection S-NSSAI may include the S-NSSAI (SST and / or SD) of the current PLMN or SNPN and the corresponding rejection reason value. Moreover, the rejection S-NSSAI may include a mapping S-NSSAI (SST and / or SD).

[0200] The information indicating that the list is of the second type may be information indicating that the list includes more than one S-NSSAI and the values ​​of the backoff timer corresponding thereto, and that the value of the backoff timer is applied to all S-NSSAIs.

[0201] It should be noted that the value of the backoff timer included in the second type of list may be the value included in the same second type of list and applied to all S-NSSAIs.

[0202] The pending NSSAI may be the pending NSSAI of the 5GS. The pending NSSAI may be the NSSAI stored in the UE and / or NW, or the NSSAI sent and received between the NW and the UE.

[0203] In the case where the pending NSSAI is the NSSAI sent from the NW to the UE, the pending NSSAI can be sent and received using a pending NSSAI IE that constitutes more than one S-NSSAI IE, which may include S-NSSAI (SST and / or SD) and mapped S-NSSAI (SST of the mapped HPLMN or HSNPN and / or SD of the mapped HPLMN or HSNPN) (if any. For example, when the UE is roaming or the associated PLMN or SNPN is a VPLMN or VSNPN).

[0204] The pending NSSAI may be applied to the registered PLMN or the registered SNPN as a whole, may be applied in the registered PLMN and one or more EPLMNs of the registered PLMN, or may be applied in the registered SNPN and one or more ESNPNs of the registered SNPN.

[0205] The UE and / or NW may regard the S-NSSAI included in the pending NSSAI as information that does not depend on the access type. That is, the pending NSSAI may be information common to both 3GPP access and non-3GPP access.

[0206] The pending NSSAI is an NSSAI composed of one or more S-NSSAIs identifying the slice for which the UE is pending a process. Specifically, the UE does not start a login request process for the S-NSSAI included in the pending NSSAI or the mapped S-NSSAI of the pending NSSAI during storage of the pending NSSAI.

[0207] In other words, the UE does not use the S-NSSAI included in the pending NSSAI during the login process until the NSSAA for the S-NSSAI included in the stored pending NSSAI is completed. The pending NSSAI is information that does not depend on the access type. Specifically, in the case where the UE stores the pending NSSAI, the UE does not attempt to send a login request message including the S-NSSAI included in the pending NSSAI to both the 3GPP access and the non-3GPP access.

[0208] When roaming (roaming scenario), the S-NSSAI included in the pending NSSAI stored by the UE may be the S-NSSAI of the HPLMN or HSNPN. In other words, the pending NSSAI IE received by the UE from the VPLMN or VSNPN may include the S-NSSAI of the HPLMN or SNPN. Such a pending NSSAI may also be referred to as the first pending NSSAI.

[0209] In other words, for the UE storing the first pending NSSAI, the mapped S-NSSAI for the first pending NSSAI means not storing it, and the S-NSSAI constructed in the first pending NSSAI stored in the UE is the S-NSSAI of the HPLMN or HSNPN whether in roaming or non-roaming.

[0210] However, when the first pending NSSAI is sent from the NW to the UE, in other words, when the UE receives the pending NSSAI from the NW, the pending NSSAI IE including the pending NSSAI may include the mapped S-NSSAI of the current S-NSSAI, or may only include the mapped S-NSSAI.

[0211] On the other hand, when roaming (roaming scenario), the S-NSSAI included in the pending NSSAI stored by the UE may be the S-NSSAI of the current PLMN (VPLMN) or SNPN (VSNPN). In other words, the pending NSSAI received by the UE from the VPLMN or VSNPN may include the S-NSSAI of the VPLMN or VSNPN. Such a pending NSSAI may also be referred to as a second pending NSSAI.

[0212] In other words, when roaming, there may be more than one mapped S-NSSAI for the second pending NSSAI. Whether roaming or non-roaming, the S-NSSAI constructed in the second pending NSSAI may be the S-NSSAI of the current PLMN or SNPN.

[0213] In this document, when referring to the pending NSSAI, it may mean the first pending NSSAI, the second pending NSSAI, both pending NSSAIs, or another pending NSSAI.

[0214] The tracking area is one or more ranges managed by the core network that can be represented as the location information of UE_A10. The tracking area can be composed of multiple cells. Moreover, the tracking area can be either a range for broadcasting control messages such as paging, or a range where UE_A10 can move without performing a switching process. Moreover, the tracking area can be either a routing area or a positioning area, as long as it is the same area as these areas. Hereinafter, the tracking area may also be referred to as TA (Tracking Area). The tracking area can be identified by TAI (Tracking Area Identity) composed of TAC (Tracking area code) and PLMN.

[0215] The registration area (Registration area or login area) is a set of one or more TAs assigned to the UE by the AMF. It should be noted that it is better for UE_A10 to move without sending or receiving signals for tracking area update while moving within one or more TAs included in the registration area. In other words, the registration area can be an information group indicating the area where UE_A10 can move without performing the tracking area update process. The registration area can be identified by a TAI list (TAIlist) composed of one or more TAIs.

[0216] The TAIs included in the TAI list may belong to one PLMN or multiple PLMNs. In the case where multiple TAIs included in the TAI list belong to different PLMNs, these PLMNs may be EPLMNs.

[0217] UE ID refers to information used to identify UE. Specifically, for example, UE ID can be SUCI (SUbscription Concealed Identifier) ​​or SUPI (Subscription Permanent Identifier) ​​or GUTI (Globally Unique Temporary Identifier) ​​or IMEI (International Mobile Subscriber Identity) or IMEISV (IMEI Software Version) or TMSI (Temporary Mobile Subscriber Identity). Alternatively, UE ID can be other information set in an application or network. Moreover, UE ID can also be information used to identify a user.

[0218] The management of the maximum number of UEs connected to a slice refers to the management and / or control of the maximum number of UEs that can log in to a network slice or S-NSSAI at the same time, or the management and / or control of the maximum number of UEs that can establish a PDU session that uses a network slice or S-NSSAI at the same time. The management of the maximum number of UEs connected to a slice can be 5GS's NSAC (network slice admission control). NSAC can also be expressed as slice admission control.

[0219] The management and / or control of the maximum number of UEs that can log in to a network slice or S-NSSAI at the same time can be expressed as MM-based slice admission control (Mobility management based slice admission control). The management and / or control of the maximum number of UEs that can establish PDU sessions that use network slices or S-NSSAI at the same time can be expressed as SM-based slice admission control (Session management based slice admission control). Slice admission control (slice admission control) can mean NSAC (Network Slice Admission Control).

[0220] Here, the UE logging into the network slice or S-NSSAI may refer to the UE including the S-NSSAI representing the network slice in the storage of the allowed NSSAI. A device in a network supporting the function of managing the maximum number of UEs connected to a slice or the function of managing and / or controlling the maximum number of UEs that can simultaneously log into a network slice or S-NSSAI can store the maximum number of UEs that need to be connected to the slice for each S-NSSAI, and can confirm whether the number of logged-in UEs has reached a constant as the maximum number during the login process.

[0221] Moreover, each device that supports the function of managing the maximum number of UEs connected to a slice or the function of managing and / or controlling the maximum number of UEs that can simultaneously log in to a network slice or S-NSSAI can store the fourth rejected NSSAI. In this document, the maximum number of UEs connected to a slice is sometimes expressed as the maximum number of UEs connected to each slice or the maximum number of UEs that can log in to a network slice or S-NSSAI or the maximum number of UEs or a constant.

[0222] SSC (Session and Service Continuity) refers to a technology for maintaining a session and / or service. Here, a session may be a PDU session established between a UE and a NW, and a service may refer to a service provided to a UE through a PDU session established between the UE and the NW. Various modes may exist.

[0223] In other words, the SSC (Session and Service Continuity) mode indicates the mode of service session continuity (Session and Service Continuity) supported by the system and / or each device in 5GC. More specifically, it can be a mode indicating the type of service session continuity supported by the PDU session established between UE_A10 and the anchor point.

[0224] Here, the anchor point can be UPGW or UPF. UPF can also be TUPF (terminating user-plane function). TUPF is the UPF of the terminal of each interface and has the PDU session anchor function. In other words, the anchor point can be a PDU Session Anchor.

[0225] For SSC, the switching anchor point may also be referred to as anchor relocation and / or change of PDU session anchor. It should be noted that these may also be referred to as anchor relocation process, PDU session anchor change process. In addition, anchor relocation may be the concept of change of PDU session anchor without change of network slice and / or S-NSSAI, or the concept of change of PDU session anchor with change of network slice and / or S-NSSAI.

[0226] In anchor relocation, the PDU session established in the initial state may be referred to as a first PDU session, and the PDU session established after the process is completed may be referred to as a second PDU session.

[0227] It should be noted that the SSC mode may also be a mode indicating a type of service session continuity set for each PDU session. That is, the SSC mode may be associated with the PDU session.

[0228] And / or, the SSC mode is associated with the anchor point and can be controlled to be unable to change between the states in which the PDU session is established. During the life of the PDU session, it is also possible to change the SSC mode associated with the PDU session. The following describes each SSC mode.

[0229] SSC Mode 1 is a mode for maintaining service session continuity with the same UPF as an anchor point regardless of the access technology such as RAT (Radio Access Technology) and cell used when UE_A10 is connected to the network. More specifically, SSC Mode 1 may be a mode for achieving service session continuity by not changing the anchor point used for the established PDU session even if UE_A10 moves.

[0230] SSC mode 2 is a mode in which, when an anchor point is included in a PDU session, the PDU session is released first and then the service session of the PDU session is established. In more detail, SSC mode 2 is a mode in which, when an anchor point is relocated, a PDU session is deleted once and then a new PDU session is established.

[0231] SSC mode 2 is a mode for maintaining service session continuity with the same UPF as an anchor point only within the service area of ​​the UPF. In more detail, as long as UE_A10 is within the service area of ​​the UPF, SSC mode 2 can be a mode for achieving service session continuity without changing the UPF used by the established PDU session. Moreover, when UE_A10 moves, such as leaving the service area of ​​the UPF, SSC mode 2 can be a mode for achieving service session continuity by changing the UPF used by the established PDU session.

[0232] Here, the service area of ​​the UPF can be an area where the UPF can provide a service session continuity function, or it can be a subset of the access network such as RAT, cell, etc. used when the UE_A10 is connected to the network. Moreover, the subset of the access network can be a network including one or more cells, or it can be a TA.

[0233] In the session continuity under SSC mode 2, when the change of S-NSSAI is not allowed, it can also be referred to as the first SSC mode 2. On the other hand, in the session continuity under SSC mode 2, when the change of S-NSSAI is allowed, it can also be referred to as the second SSC mode 2. In other words, the case where the S-NSSAI or network slice is changed and the session continuity is performed in SSC mode 2 can also be referred to as the second SSC mode 2. In further other words, the case where the S-NSSAI or network slice is changed and the PDU session of SSC mode 2 is continued can also be referred to as the second SSC mode 2. When it is simply referred to as SSC mode 2, it can also mean the first SSC mode 2 and / or the second SSC mode 2.

[0234] SSC mode 3 is a service session continuation mode that can establish a PDU session between a new anchor point and the UE for the same DN without releasing the PDU session between the UE and the anchor point.

[0235] SSC mode 3 is a mode that allows service session continuity of a new PDU session and / or communication path established via a new UPF for the same DN before disconnecting the PDU session and / or communication path established between UE_A10 and UPF. Moreover, SSC mode 3 can be a mode that allows UE_A10 to become multi-homed service session continuity.

[0236] And / or SSC mode 3 may also be a mode that allows continuity of service sessions using multiple PDU sessions and / or establishing corresponding UPFs with PDU sessions. In other words, in the case of SSC mode 3, each device may use multiple PDU sessions to achieve service session continuity, and may also use multiple UPFs to achieve service session continuity.

[0237] In the session continuity of SSC mode 3, when the change of S-NSSAI is not allowed, it can also be referred to as the first SSC mode 3. On the other hand, in the session continuity under SSC mode 3, when the change of S-NSSAI is allowed, it can also be referred to as the second SSC mode 3. In other words, the case where the S-NSSAI or network slice is changed and the session continuity is performed in SSC mode 3 can also be referred to as the second SSC mode 3. In further other words, the case where the S-NSSAI or network slice is changed and the PDU session of SSC mode 3 is continued can also be referred to as the second SSC mode 3. When it is simply referred to as SSC mode 3, it can also mean the first SSC mode 3 and / or the second SSC mode 3.

[0238] SSC mode 4 may be the second SSC mode 2.

[0239] In other words, SSC mode 4 is a mode in which the S-NSSAI or network slice is changed when an anchor point is included in the PDU session, and the PDU session is released first and then the service session of the PDU session is established continuously. In more detail, SSC mode 4 is a mode in which the S-NSSAI or network slice is changed when the anchor point is relocated, and the PDU session is reestablished after deleting the PDU session once.

[0240] SSC mode 4 is a mode for service session continuity that changes S-NSSAI or network slice only within the service area of ​​UPF, and continuously maintains the same UPF as an anchor point. In more detail, as long as UE_A10 is within the service area of ​​UPF, SSC mode 4 can be a mode for achieving service session continuity by changing S-NSSAI or network slice without changing the UPF used for the established PDU session. Moreover, in the event of mobility of UE_A10 such as leaving the service area of ​​UPF, SSC mode 4 can be a mode for achieving service session continuity by changing S-NSSAI or network slice, and changing the UPF used for the established PDU session.

[0241] Here, the service area of ​​the UPF can be an area where the UPF can provide a service session continuity function, or it can be a subset of the access network such as RAT, cell, etc. used when the UE_A10 is connected to the network. Moreover, the subset of the access network can be a network including one or more cells, or it can be a TA.

[0242] SSC mode 5 may be the second SSC mode 3.

[0243] In other words, SSC mode 5 is a service session continuity mode that can change the S-NSSAI or network slice and establish a PDU session between the new anchor point and the UE for the same DN without releasing the PDU session between the UE and the anchor point.

[0244] SSC mode 5 is a mode that allows service session continuity by establishing a new PDU session and / or communication path via a new UPF for the same DN before changing the S-NSSAI or network slice and cutting off the PDU session and / or communication path established between UE_A10 and UPF. Moreover, SSC mode 5 may be a mode that allows service session continuity for UE_A10 to become multi-homed.

[0245] In addition, SSC mode 5 may also be a mode that allows the continuity of service sessions that use multiple PDU sessions and / or establish corresponding UPFs with PDU sessions. In other words, in the case of SSC mode 5, each device may use multiple PDU sessions to achieve service session continuity, and may also use multiple UPFs to achieve service session continuity.

[0246] In addition, the subscription information may include restrictions on simultaneous logins to the network slice. The subscription information is provided to the serving AMF (serving AMF, AMF that serves the UE, AMF to which the UE is connected) as a UE subscription in the form of NSSRG (Network Slice Simultaneous Registration Group) information. The subscription information may include a list of subscribed DNNs and a default DNN (defaultDNN) for each S-NSSAI and / or information indicating whether the S-NSSAI is marked as the default subscribed S-NSSAI (default subscribed S-NSSAI) and / or information indicating whether the S-NSSAI is associated with NSSAA and / or NSSRG information. The subscription information may be information sent by the UDM to the AMF. In other words, the UDM may be information for managing subscription information.

[0247] In addition, the subscription information for the UE may include NSSRG information for each S-NSSAI. The NSSRG information may be information that limits which S-NSSAIs can be provided to the UE at the same time in the allowed NSSAI. In the case of NSSRG information associated with multiple S-NSSAIs, more than one S-NSSAI included in the allowed NSSAI may share at least one (common) NSSRG. In addition, in the case where NSSRG information exists in the subscription information, each S-NSSAI included in the subscription information may be associated with at least one NSSRG. When the AMF receives subscription information for the UE including NSSRG information, only one or more S-NSSAIs such as those with a common NSSRG may be included in the allowed NSSAI for the UE. In addition, the subscription information including NSSRG information may include at least one default S-NSSAI. In addition, in the case of receiving a request NSSAI from the UE, the AMF that supports NSSRG and / or processing functions related to NSSRG information can determine whether the S-NSSAI of the HPLMN can be provided together with the allowed NSSAI based on the NSSRG information of the S-NSSAI of the HPLMN.

[0248] In addition, the UE may include information indicating whether these functions (subscription-based restrictions to simultaneous registration of network slices feature) are supported in the 5GMM capability IE included in the login request message for sending. In other words, information indicating whether the UE supports the function of limiting simultaneous registration of network slices based on subscriptions may be included as the forty-first identification information. In addition, the NW may include information indicating whether these functions (subscription-based restrictions to simultaneous registration of network slices feature) are supported in the 5GS network feature support IE included in the login acceptance message or the login rejection message for sending. In other words, information indicating whether the NW supports the function of limiting simultaneous registration of network slices based on subscriptions may also be included as the fifty-first identification information.

[0249] In addition, when the serving AMF provides the UE with the setting of NSSAI, that is, when the UE supports the function of limiting simultaneous logins to network slices based on subscription, the AMF may provide the UE with the NSSRG information related to the S-NSSAI of the HPLMN present in the mapping information of the setting of NSSAI. The UE that receives the NSSRG information may include the S-NSSAI with the common NSSRG in the request NSSAI.

[0250] In addition, the first identification information is information indicating a new S-NSSAI. The first identification information may be information indicating an updated or changed S-NSSAI. The first identification information may be information indicating an S-NSSAI associated with a newly established PDU session (e.g., a second PDU session). The first identification information may be an S-NSSAI assigned by the network to the second PDU session and / or the UE.

[0251] In addition, the S-NSSAI indicated by the first identification information may be the same S-NSSAI as the S-NSSAI associated with the established PDU session (e.g., the first PDU session), or a different S-NSSAI. The SST of the S-NSSAI indicated by the first identification information may be the same as the SST of the S-NSSAI associated with the first PDU session, or may be different.

[0252] In addition, the first identification information may be information indicating updated or changed preference information. The first identification information may be information notified by the network of update or change of preference information of a path or anchor point included in a PDU session.

[0253] In addition, the second identification information is information indicating a reason. The second identification information may be a reason value or a 5GSM cause IE. In addition, the second identification information may be information indicating an update or change of preference information. In other words, the second identification information may be information indicating that the network has updated or changed the preference information. Moreover, the second identification information may be information indicating an update or change of a PDU session caused by the movement of the UE. In other words, the second identification information may be information indicating that the network has updated or changed information related to the PDU session along with an update of the UE location information. For example, the second identification information may be information indicating that the S-NSSAI associated with the PDU session cannot be used, and information indicating a change in the S-NSSAI.

[0254] In addition, the second identification information can be 5GSM reason #39 "Reactivation requested", or it can be information represented by 5GSM reason #39 "Reactivation requested".

[0255] In addition, the eleventh identification information is information indicating a new S-NSSAI. The eleventh identification information may be associated with a PDU session ID sent and received together. The eleventh identification information may be the same as the first identification information.

[0256] In addition, the twelfth identification information may be a reason value. In addition, the twelfth identification information may also be a 5GSM reason IE. The twelfth identification information may be information indicating the start of a PDU session establishment process for re-establishing a PDU session for the same DN request. Moreover, the twelfth identification information may also be information indicating the start of a PDU session establishment process for re-establishing a PDU session for the same S-NSSAI request, or may be information indicating the start of a PDU session establishment process for re-establishing a PDU session for different S-NSSAI requests. In addition, the twelfth identification information may also be information indicating the start of a PDU session establishment process for re-establishing a PDU session for different DN requests. In addition, the twelfth identification information may also be information indicating the start of a PDU session establishment process for re-establishing a PDU session for the same or different DNs and the same or different S-NSSAI requests.

[0257] In addition, the twelfth identification information can be 5GSM reason #39 "Reactivation Request" or information represented by 5GSM reason #39 "Reactivation Request".

[0258] In addition, the twenty-first identification information may be requested S-NSSAI information. The twenty-first identification information may also be empty information. The twenty-first identification information may be the S-NSSAI notified from the NW. Specifically, the S-NSSAI included in the twenty-first identification information may be the S-NSSAI represented by the first identification information and / or the eleventh identification information. In addition, the twenty-first identification information may also be the S-NSSAI selected by the UE from one or more S-NSSAIs notified by the fifty-second or fifty-third identification information.

[0259] In addition, the twenty-second identification information may be information indicating a requested SSC mode. The twenty-second identification information may indicate at least one of SSC mode 1 to SSC mode 5.

[0260] In addition, the twenty-third identification information may be information indicating the capability of the UE. In addition, the twenty-third identification information may also be capability information of the UE shown as a 5GSM capability IE. In addition, the twenty-third identification information may be information included in the 5GSM capability IE and / or the 5GSM capability IE. In addition, the twenty-third identification information may also be information indicating whether the UE supports changes in S-NSSAI or network slices based on anchor relocation. In addition, the twenty-third identification information may also be information indicating whether the UE supports changes in S-NSSAI or network slices based on anchor relocation. In addition, the twenty-third identification information may also be information indicating whether the UE supports anchor relocation and changes in S-NSSAI or network slices. In addition, the twenty-third identification information may also be information indicating whether the UE supports anchor relocation and changes in S-NSSAI or network slices. In addition, the twenty-third identification information may also be information indicating whether the UE supports anchor relocation with changes in S-NSSAI or network slices. In addition, the twenty-third identification information may also be information indicating whether the UE supports anchor relocation with changes in S-NSSAI or network slices. In addition, the twenty-third identification information may also be information indicating whether the UE supports anchor relocation with changes in S-NSSAI or network slices. In addition, the twenty-third identification information may also be information indicating whether the UE supports anchor relocation with changes in S-NSSAI or network slices. Fig. 9 or Fig.10 In the process shown, the UE supports anchor relocation with S-NSSAI or network slice change. In addition, the twenty-third identification information may also be information indicating whether the UE supports anchor relocation with S-NSSAI or network slice change in the process shown. Fig. 9 or Fig.10 The process shown herein supports anchor relocation information with accompanying S-NSSAI or network slice change.

[0261] In addition, the thirty-first identification information may be information indicating the capabilities of the network. In addition, the thirty-first identification information may also be capability information of the network shown as a 5GSM network feature support IE. In addition, the thirty-first identification information may also be information included in the 5GSM network feature support IE and / or the 5GSM network feature support IE. In addition, the thirty-first identification information may also be information indicating whether the NW and / or the established PDU session supports changes in S-NSSAI or network slices based on anchor relocation. In addition, the thirty-first identification information may also be information indicating that the NW and / or the established PDU session supports changes in S-NSSAI or network slices based on anchor relocation. In addition, the thirty-first identification information may also be information indicating whether the NW and / or the established PDU session supports anchor relocation and changes in S-NSSAI or network slices. In addition, the thirty-first identification information may also be information indicating that the NW and / or the established PDU session supports anchor relocation and changes in S-NSSAI or network slices. In addition, the thirty-first identification information may also be information indicating whether the NW and / or the established PDU session supports anchor relocation with S-NSSAI or network slice change. In addition, the thirty-first identification information may also be information indicating whether the NW and / or the established PDU session supports anchor relocation with S-NSSAI or network slice change. In addition, the thirty-first identification information may also be information indicating whether the NW and / or the established PDU session supports anchor relocation with S-NSSAI or network slice change. Fig. 9 or Fig.10 The process shown indicates whether the NW and / or established PDU session supports anchor relocation information accompanying S-NSSAI or network slice change.

[0262] In addition, the thirty-first identification information can be associated with the SSC mode and / or PDU session ID and / or anchor point that are sent and received together.

[0263] In addition, the thirty-second identification information may indicate that the NW has changed the S-NSSAI by anchor relocation. The thirty-second identification information may be the changed S-NSSAI. The thirty-second identification information may be the S-NSSAI IE.

[0264] In addition, the thirty-fifth identification information may be information indicating that the PDU session cannot be established because the NW and / or the established PDU session does not support the change of S-NSSAI or network slice based on anchor relocation and / or the NW and / or the established PDU session does not support anchor relocation with change of S-NSSAI or network slice and / or the NW does not support change of S-NSSAI based on anchor relocation. The thirty-fifth identification information may be a reason value, for example, it may be a 5GSM reason IE.

[0265] In addition, the thirty-fifth identification information can be 5GSM reason #39 "Reactivation Request" or information represented by 5GSM reason #39 "Reactivation Request".

[0266] In addition, the forty-first identification information may be information indicating the capability of the UE. In addition, the forty-first identification information may also be capability information of the UE shown as a 5GMM capability IE. In addition, the forty-first identification information may also be information included in the 5GMM capability IE and / or the 5GMM capability IE. In addition, the forty-first identification information may also be information indicating whether the UE supports changes in S-NSSAI or network slices based on anchor relocation. In addition, the forty-first identification information may also be information indicating whether the UE supports changes in S-NSSAI or network slices based on anchor relocation. In addition, the forty-first identification information may also be information indicating whether the UE supports anchor relocation and changes in S-NSSAI or network slices. In addition, the forty-first identification information may also be information indicating whether the UE supports anchor relocation and changes in S-NSSAI or network slices. In addition, the forty-first identification information may also be information indicating whether the UE supports anchor relocation with changes in S-NSSAI or network slices. In addition, the forty-first identification information may also be information indicating whether the UE supports anchor relocation with changes in S-NSSAI or network slices. In addition, the forty-first identification information may also be information indicating whether the UE supports anchor relocation with changes in S-NSSAI or network slices. In addition, the forty-first identification information may also be information indicating whether the UE supports anchor relocation with changes in S-NSSAI or network slices. In addition, the forty-first identification information may also be information indicating whether the UE supports anchor relocation with changes in S-NSSAI or network slices. Fig. 9 or Fig.10 In the process shown, the UE supports anchor relocation with S-NSSAI or network slice change. In addition, the forty-first identification information may also be information indicating whether the UE supports anchor relocation with S-NSSAI or network slice change during the process shown. Fig. 9 or Fig.10 The process shown herein supports anchor relocation information with accompanying S-NSSAI or network slice change.

[0267] In addition, the UE may include information indicating whether it supports the function of limiting simultaneous registration of network slices based on subscriptions (subscription-based restrictions to simultaneous registration of networkslices feature) in the 5GMM capability IE included in the login request message for sending. In other words, information indicating whether the UE supports the function of limiting simultaneous registration of network slices based on subscriptions may be included as the forty-first identification information.

[0268] In addition, the forty-first identification information may also be information including one or more of the above-mentioned UE capability information.

[0269] In addition, the forty-second identification information may be a request NSSAI.

[0270] In addition, the fifty-first identification information may be information indicating the capabilities of the network. In addition, the fifty-first identification information may also be 5GS network feature support IE (5GS network feature support IE). In addition, the fifty-first identification information may also be information included in 5GS network feature support and / or 5GS network feature support. In addition, the fifty-first identification information may also be information indicating whether the NW and / or an established PDU session supports changes in S-NSSAI or network slices based on anchor relocation. In addition, the fifty-first identification information may also be information indicating that the NW and / or an established PDU session supports changes in S-NSSAI or network slices based on anchor relocation. In addition, the fifty-first identification information may also be information indicating whether the NW and / or an established PDU session supports anchor relocation and changes in S-NSSAI or network slices. In addition, the fifty-first identification information may also be information indicating that the NW and / or an established PDU session supports anchor relocation and changes in S-NSSAI or network slices. In addition, the fifty-first identification information may also be information indicating whether the NW and / or the established PDU session supports anchor relocation with S-NSSAI or network slice change. In addition, the fifty-first identification information may also be information indicating whether the NW and / or the established PDU session supports anchor relocation with S-NSSAI or network slice change. In addition, the fifty-first identification information may also be information indicating whether the NW and / or the established PDU session supports anchor relocation with S-NSSAI or network slice change. Fig. 9 or Fig.10 The information of whether the NW and / or the established PDU session supports anchor relocation with S-NSSAI or network slice change in the process shown. In addition, the fifty-first identification information may also be information indicating whether the NW and / or the established PDU session supports anchor relocation with S-NSSAI or network slice change in the process shown. Fig. 9 or Fig.10 The process shown is that the NW and / or an established PDU session supports anchor relocation information accompanying S-NSSAI or network slice change.

[0271] In addition, the NW may include information indicating whether the function of limiting simultaneous registration of network slices based on subscriptions (subscription-based restrictions to simultaneous registration of networkslices feature) in the 5GS network feature support IE included in the login acceptance message or the login rejection message for sending. In other words, information indicating whether the NW supports the function of limiting simultaneous registration of network slices based on subscriptions may also be included as the fifty-first identification information.

[0272] In addition, the fifty-first identification information may be information including one or more of the above-mentioned NW capability information.

[0273] The fifty-first identification information can be associated with the SSC mode and / or PDU session ID and / or anchor point that are sent and received together.

[0274] In addition, the fifty-second identification information may be NSSAI allowed.

[0275] In addition, the fifty-third identification information may be the set NSSAI. [3. Description of Processes Used in Each Embodiment]

[0276] Next, the processes used in each embodiment are described. It should be noted that the processes used in each embodiment include a PDU session change process and / or a PDU session release process and / or a PDU session establishment process and / or a login process. Each process is described below.

[0277] It should be noted that, in each embodiment, Figure 2 As described above, the case where HSS and UDM, PCF and PCRF, SMF and PGW-C, UPF and PGW-U are respectively configured as the same device (that is, the same physical hardware or the same logical hardware or the same software) is used as an example for explanation. However, the content described in this embodiment can also be applied to the case where they are configured as different devices (that is, different physical hardware, or different logical hardware or different software). For example, data can be sent and received directly between them, data can be sent and received via the N26 interface between AMF and MME, and data can be sent and received via UE. [3.1.PDU session change process]

[0278] Next, use Figure 6 , the behavior of each device when the NW executes the PDU session change process is described. Hereinafter, the PDU session change process is sometimes referred to as this process. In addition, the PDU session change process can be an SM process.

[0279] This process is a process performed by each device to update the status of the PDU session. It should be noted that each device can execute this process in the state where the PDU session establishment process has been completed, and can also execute this process during the PDU session establishment process. In addition, each device can start this process in the logged-in state, and can also start this process at any time after the PDU session establishment process. In addition, each device can update the status of the PDU session based on the completion of the PDU session change process. Moreover, when multiple PDU sessions are established, each device can update the status of each PDU session by executing this process multiple times.

[0280] The following describes each step of this process. SMF sends a PDU session modification command message (PDU session modification command) (S802) (S804) to the UE via the AMF. Specifically, SMF_A230 uses the N11 interface to send a PDU session modification command message (S802) to the AMF, and the AMF that receives the PDU session modification command message sends a PDU session modification command message (S804) to the UE using the N1 interface.

[0281] It should be noted that the trigger for SMF to send a PDU session change command message may be the receipt of a status change notification message sent from AMF, the receipt of a request message from AF, or the detection of a status change of SMF itself.

[0282] It should be noted that the trigger for SMF to send a PDU session change command message may also be that SMF and / or AMF sense that the S-NSSAI associated with the PDU session is not allowed to be used. In the case where AMF senses that the S-NSSAI is not allowed to be used, SMF may receive a status change notification message from AMF.

[0283] Furthermore, the PDU session change command message may be a NAS message sent and received on the N11 interface and the N1 interface, or may be included in a NAS message for sending and receiving. In addition, the PDU session change command message is not limited thereto, and any message indicating that the change of the PDU session has been determined may be used.

[0284] Furthermore, the state change notification message may be a message sent by the AMF to the SMF using the N11 interface, or may be information indicating that the state of the UE has changed according to the mobility of the UE, etc. Furthermore, the state change notification message may also be information indicating that the state of the UE and / or the network device has changed due to changes in subscriber information and / or operator policy and / or UE policy. Furthermore, the request message from the AF may be either a request message sent from the AF or a request message sent by another network device agent.

[0285] Here, the SMF may include at least one or more identification information from the first to second identification messages in the PDU session change command message, and the SMF's request may be represented by including these identification information.

[0286] Furthermore, the SMF can request a connection target of the PDU session or a change in information about the PDU session by sending one or more of the identification information 71 to 72. In more detail, the SMF can request an update of the preference information by sending the second identification information and / or sending the second identification information in association with the first identification information, and can also request a change in the default route, and can also notify a change in mobility.

[0287] The SMF may notify the change of the S-NSSAI and / or the new S-NSSAI by sending the second identification information and / or sending the first identification information.

[0288] It should be noted that the SMF can determine which identification information from the first to second identification information to add to the PDU session change request message based on network capability information and / or operator policies and / or network status. It should be noted that the determination made by the SMF as to which identification information to add to the PDU session change request message is not limited to this.

[0289] The UE can identify the NW request by receiving one or more of the first to second identification information. Specifically, based on the reception of the second identification information, the UE can identify the connection destination of the PDU session, the change of information related to the PDU session, and the change of the S-NSSAI.

[0290] The UE may identify the S-NSSAI associated with the second PDU session and / or the S-NSSAI requested by the UE in a PDU session establishment procedure performed subsequently based on the first identification information.

[0291] It should be noted that, when the S-NSSAI indicated in the first identification information is not included in the allowed NSSAI (Allowed NSSAI) stored by the UE, a login request message can be sent before the PDU session establishment process is performed, and the login request message may include a requested NSSAI IE (requested NSSAIIE) containing the S-NSSAI indicated in the eleventh identification information.

[0292] The UE that receives the PDU session change command message sends a PDU session change accept (PDU session establishment accept) message (S806) to the SMF via the AMF (S808).

[0293] Specifically, UE_A10 uses the N1 interface to send a PDU session change acceptance message (S806) to AMF_A240, and the AMF that receives the PDU session change request message uses the N11 interface to send a PDU session change acceptance message (S808) to SMF.

[0294] It should be noted that the PDU session change accept message may be a NAS message sent and received on the N1 interface and the N11 interface, or may be included in a NAS message. In addition, the PDU session change accept message is not limited thereto, and may also be a message indicating that the establishment of the PDU session is accepted.

[0295] The SMF receives the PDU session change accept message and sends a session change request message (SessionModification request) to the UPF (S810), and then receives the session change accept (SessionModification response) message sent by the UPF that received the session change request message (S812). Each device completes this process based on the sending and receiving of the PDU session change accept message and / or the sending and receiving of the session change accept message.

[0296] It should be noted that in this process, when the address allocated to the UE is not notified to the UE, the SM can send the RA via the UPF that becomes the anchor point.

[0297] Through the above, each device can update the status of the PDU session. [3.2.PDU session release process]

[0298] First, the PDU session release procedure is briefly described. Hereinafter, this procedure refers to the PDU session release procedure. It should be noted that a PDU session may include one or more routes. In other words, one or more anchor points may be assigned to a PDU session.

[0299] This process is used for each device to release the PDU session. It should be noted that each device can execute this process after completing the PDU session establishment process. In addition, each device can start this process in the logged-in state, or at any time after the PDU session establishment process.

[0300] Below, use Figure 7 , an example of the steps for executing the PDU session establishment process is described. Below, each step of this process is described. First, the SMF determines to start the PDU session release process. The condition for the SMF to determine to start the PDU session release process may be that the SMF determines to start anchor (UPF) relocation. Moreover, the condition for the SMF to determine to perform anchor relocation may be receiving a status change notification message sent from the AMF, or receiving a request message from the AF, or sensing the status change of the SMF itself.

[0301] It should be noted that the trigger for SMF to determine to start the PDU session release process may be that SMF and / or AMF sense that the S-NSSAI associated with the PDU session is not allowed to be used. In the case where AMF and / or NSSF sense that the use of S-NSSAI is not allowed, SMF may receive a state change notification message from AMF and / or NSSF. It should be noted that the main factors for determining the relocation of the anchor are not limited to this.

[0302] Next, the SMF sends a session release request message (S910) to the UPF of the relocation source to start the release process of the session between the SMF and the UPF. Here, the SMF can select one or more UPFs based on the determination of the UPF relocation and / or based on the context that the SMF has maintained. It should be noted that, in the case of selecting multiple UPFs, the SMF can send a session release request message to each UPF.

[0303] UPF receives the session release request message and deletes the context for the PDU session. Moreover, based on receiving the session release request message and / or deleting the context for the PDU session, UPF sends a session release response (Session release response) message to SMF (S912). Moreover, SMF receives the session release response message. It should be noted that the session release request message and the session release response message can be control messages sent and received on the N4 interface. Moreover, the session release response message can be a response message to the session release request message.

[0304] Next, the SMF sends a PDU session release command (PDU session release command) message (S902) to the UE via the AMF based on the reception of the PDU session release response message and / or the determination of the relocation of the PDU session anchor (S904).

[0305] Specifically, SMF sends a PDU session release command message to AMF (S902), and the AMF that receives the PDU session release command message sends a PDU session release command message to the UE (S904).

[0306] It should be noted that the PDU session release command message can be a NAS message sent and received on the N11 interface and the N1 interface, and can also be included in a NAS message for sending. In addition, the PDU session release command message is not limited to this, as long as it is a message indicating that the release of the PDU session is requested by the network and / or the release of the PDU session is determined by the network.

[0307] Here, the SMF and / or AMF may include at least one of the eleventh to twelfth identification information in the PDU session release command message and / or the NAS message, and may also indicate a request for release of the PDU session by including these identification information.

[0308] Moreover, SMF and / or AMF can indicate that the network has accepted the request to establish a PDU session connected to the DN, or can indicate that the network has allowed the establishment of a PDU session connected to the DN by sending one or more of the identification information from the eleventh to the twelfth identification information.

[0309] In more detail, the SMF and / or AMF can indicate that the information about the PDU session released for a certain period of time after the PDU session is released is maintained by sending one or more of the identification information from the eleventh to the twelfth identification information.

[0310] Moreover, the SMF and / or AMF can indicate the release of the PDU session for the purpose of PDU session anchor relocation by sending one or more identification information among the eleventh to twelfth identification information.

[0311] It should be noted that the SMF and / or AMF can determine which identification information from the eleventh to twelfth identification information to add to the PDU session release command message and / or NAS message based on the received identification information and / or network capability information and / or operator policies and / or network status. It should be noted that the determination made by the SMF and / or AMF as to which identification information to add to the PDU session release command message and / or NAS message is not limited to this.

[0312] The UE can identify the request of the NW by receiving one or more of the identification information from the eleventh to twelfth identification information. Specifically, based on the reception of the twelfth identification information, the UE can identify the connection destination of the PDU session, the change of information related to the PDU session, and the change of the S-NSSAI.

[0313] The UE may identify the S-NSSAI associated with the second PDU session and / or the S-NSSAI requested by the UE in a PDU session establishment procedure performed subsequently based on the eleventh identification information.

[0314] It should be noted that, when the S-NSSAI indicated in the eleventh identification information is not included in the allowed NSSAI (Allowed NSSAI) stored by the UE, a login request message can be sent before the PDU session establishment process is performed, and the login request message may include a requested NSSAI IE (requested NSSAIIE) containing the S-NSSAI indicated in the eleventh identification information.

[0315] The UE receives the PDU session release command message, and then sends a PDU session release accept message (PDU session release accept) to the SMF via the AMF (S906)(S908).

[0316] Specifically, the UE uses the N1 interface to send a PDU session release accept message (S906) to the AMF, and the AMF that receives the PDU session release accept message uses the N11 interface to send a PDU session release accept message (S908) to the SMF.

[0317] It should be noted that the PDU session release accept message can be a NAS message sent and received on the N1 interface and the N11 interface, and can also be included in a NAS message for sending and receiving. In addition, the PDU session release accept message can be any message as long as it is a response message to the PDU session release command message, but is not limited thereto, as long as it is a message indicating that the PDU session release process is completed.

[0318] Next, the SM sends a PDU session release notification message to the AMF (S912). SMF_A230 can notify the completion of the release of the PDU session by sending the PDU session release notification message, or it can notify that although the PDU session is released, it is in a state of maintaining the storage of part of the information for relocation. It should be noted that the PDU session release notification message is not limited to this, as long as it is a message that notifies the release of the PDU session.

[0319] It should be noted that the AMF may start timing the timer using the timer for managing the storage of information about the PDU session based on the reception of the PDU session release accept message and / or the reception of the PDU session release notification message and / or the sending of the PDU session release command message. The AMF may identify and store the information indicated by each message and / or the identification information included in each message based on the reception of the PDU session release accept message and / or the reception of the PDU session release notification message and / or the sending of the PDU session release command message.

[0320] Moreover, in the event of expiration of a timer used to manage the storage of information about the PDU session, the AMF may release the information and / or context about the PDU session.

[0321] The SMF may start timing a timer that manages the storage of information about the PDU session based on the reception of a PDU session release accept message and / or the sending of a PDU session release notification message and / or the reception of a PDU session release command message.

[0322] Moreover, in the event of expiration of a timer used to manage storage of information about a PDU session, the SMF may release information and / or context about the PDU session.

[0323] Each device completes this process based on the transmission and reception of S906 and / or S908 and / or S912. It should be noted that each device can be transformed into a state where the PDU session is released based on the completion of this process. Moreover, each device can implement processing based on the identification information transmitted and received in this process based on the completion of this process.

[0324] For example, when the UE receives one or more of the eleventh to twelfth identification information, the PDU session establishment process using the eleventh identification information can be immediately started.

[0325] Moreover, when the UE receives one or more of the identification information from the eleventh to the twelfth identification information, it may temporarily not release the information about the PDU session, or it may immediately release the information about the PDU session.

[0326] The UE may send a PDU session release request message to the AMF based on the fact that the restriction time (lifetime) of the S-NSSAI associated with the current PDU session is approaching expiration, and based on the fact that the current PDU session has established an association with SSC mode 2 or SSC mode 4. Moreover, the AMF may send the received PDU session release request message to the SMF. Here, UE_A10 may include in the PDU session release request message identification information indicating a request for anchor relocation of the S-NSSAI and / or SSC associated with the above-mentioned current PDU session. It should be noted that the process after the SMF receives the PDU session release request message may be to use Figure 7 The process after S910 is described. [3.3. PDU session establishment process]

[0327] Next, use Figure 8 , the behavior of each device when the UE executes the PDU session establishment process is described. Hereinafter, the PDU session establishment process is sometimes referred to as this process. In addition, the PDU session establishment process can also be an SM process.

[0328] It should be noted that this process can also be executed after executing the login process more than once.

[0329] First, the UE sends a PDU session establishment request message to the SMF (S1400)(S1402)(S1404) to start the PDU session establishment process. Then, the SMF receives the PDU session establishment request message from the UE.

[0330] Specifically, the UE starts the PDU session establishment process by sending a NAS message (S1400) including an N1 SM container containing a PDU session establishment request message to the AMF via the access network. The NAS message is, for example, a message sent via the N1 interface, and may be an uplink NAS transport (UL NAS TRANSPORT) message.

[0331] Moreover, the AMF may determine the SMF based on the NAS message received from the UE and / or the state of the network (S1402). Moreover, the AMF may transmit the identification information included in the received PDU session establishment request message and / or NAS message to the selected SMF (S1404).

[0332] The UE may send a PDU session establishment request message based on reception of at least one of the first to second identification information and / or the eleventh to twelfth identification information.

[0333] Here, the UE may include at least one of the twenty-first to twenty-third identification information in a PDU session establishment request message or a NAS message for transmission. It should be noted that the UE may include other identification information in a PDU session establishment request message or a NAS message. Specifically, the UE may include the requested DNN and PDU session ID in a PDU session establishment request message or a NAS message.

[0334] It should be noted that the UE can indicate that the UE supports each function by sending these identification information, and can also indicate the UE's request. Moreover, in the case of sending and receiving multiple identification information, two or more of these identification information can constitute more than one identification information. It should be noted that the information indicating support for each function and the information indicating a request for use of each function can be sent and received as the same identification information, or can be sent and received as different identification information.

[0335] Here, the UE indicates the content of the above identification information to the network by sending a PDU session establishment request message or a NAS message.

[0336] The UE may send empty twenty-first identification information based on the reception of at least one of the first to second identification information and / or the eleventh to twelfth identification information, or may determine not to send the twenty-first identification information. In other words, the UE may send a PDU session establishment request message using no S-NSSAI based on the reception of at least one of the first to second identification information and / or the eleventh to twelfth identification information.

[0337] Then, when receiving a NAS message, the AMF can identify the content of the request made by the UE and / or the information included in the NAS message (message, container, information).

[0338] Next, the AMF selects the SMF as the transmission destination of at least a part of the information (message, container, information) included in the NAS message received from the UE (S1402). It should be noted that the AMF can select the SMF of the transmission destination based on the information (message, container, information) included in the NAS message and / or subscriber information and / or network capability information and / or UE policy and / or operator policy and / or network status and / or user login information and / or context maintained by the AMF.

[0339] Specifically, the AMF may select an SMF for establishing a PDU session for the same DNN as the DNN associated with the first PDU session. Similarly, the AMF may also select an SMF for establishing a PDU session for the same S-NSSAI as the S-NSSAI associated with the first PDU session.

[0340] In addition, the AMF may select an SMF for establishing a PDU session for an S-NSSAI consisting of the same SST as the SST of the S-NSSAI associated with the first PDU session. Alternatively, the AMF may also select an SMF for establishing a PDU session for an S-NSSAI different from the S-NSSAI associated with the first PDU session.

[0341] Next, the AMF sends at least a portion of the information (message, container, information) included in the NAS message received from the UE to the selected SMF via the N11 interface, for example (S1404).

[0342] Then, when receiving information (messages, containers, information) sent from AMF, SMF can identify the content of information (messages, containers, information) requested by UE and / or received from AMF.

[0343] Here, the SMF can perform a second condition determination. In addition, the second condition determination can be used to determine whether the network accepts the UE's request. The SMF can start the second condition determination if it is true. Figure 8 (A) process, when the second condition is judged to be false, starts Figure 8 (B) process.

[0344] It should be noted that the second condition determination can also be performed by a NF other than the SMF. The NF may be, for example, NSSF, NWDAF, PCF, or NRF. In the case where a NF other than the SMF performs the second condition determination, the SMF may provide the NF with the information required for the second condition determination, specifically, at least a portion of the information received from the UE (S1406). Moreover, in the case where the NF determines the truth or falsity of the second condition determination based on the information received from the SMF, information including the result of the second condition determination (that is, whether it is true or false) may be transmitted to the SMF. The SMF may determine the identification information and / or control message that should be sent to the UE based on the result of the second condition determination received from the NF.

[0345] It should be noted that the second condition judgment can be performed based on information received from AMF (messages, containers, information) and / or subscriber information (subscription information) and / or network capability information and / or UE policy and / or operator policy and / or network status and / or user login information and / or context maintained by SMF.

[0346] For example, the second condition may be determined to be true when the network allows the UE's request, and false when the network does not allow the UE's request. In addition, the second condition may be determined to be true when the network of the UE's connection destination and / or the device within the network supports the function requested by the UE, and false when the function requested by the UE is not supported. In addition, the second condition may be determined to be true when the identification information sent and received is allowed, and false when the identification information sent and received is not allowed.

[0347] It should be noted that the conditions for determining the truth or falsity of the second conditional determination may not be limited to the above conditions.

[0348] Next, Figure 8 Each step of the process (A) is described.

[0349] The SMF may select a UPF for the established PDU session, for example, by sending an N4 session establishment request message to the selected UPF via an N4 interface (S1408). The N4 session establishment request message may include at least a portion of the PCC rules received from the PCF.

[0350] SMF can determine whether to perform authorization for C2 communication in this process based on information (messages, containers, information) received from AMF and / or information such as PCC rules received from PCF and / or subscriber information and / or network capability information and / or UE policy and / or operator policy and / or network status and / or user login information and / or context maintained by SMF.

[0351] In the case of performing authorization of C2 communication in this process, the SMF can determine the authorization for establishment of the PDU session requested by the UE based on at least one of the twenty-first to twenty-third identification information.

[0352] Here, the SMF may select one or more UPFs based on information (messages, containers, information) received from the AMF and / or information such as PCC rules received from the PCF and / or subscriber information and / or network capability information and / or UE policy and / or operator policy and / or network status and / or user login information and / or contexts maintained by the SMF. In addition, when multiple UPFs are selected, the SMF may send an N4 session establishment request message to each UPF. Here, it is assumed that the UPF is selected.

[0353] Then, when receiving the N4 session establishment request message (S1408), the UPF can identify the content of the information received from the SMF. In addition, the UPF can send an N4 session establishment response message (S1410) to the SMF via the N4 interface based on the reception of the N4 session establishment request message.

[0354] Then, the SMF can identify the content of the information received from the UPF when receiving the N4 session establishment response message as a response message to the N4 session establishment request message.

[0355] Next, the SMF sends a PDU session establishment accept message to the UE based on the reception of the PDU session establishment request message and / or the selection of the UPF and / or the reception of the N4 session establishment response message, etc. Then, the UE receives the PDU session establishment accept message and / or identification information from the SMF (S1412)(S1414)(S1416).

[0356] Specifically, the SMF sends the N1 SM container and / or the N2 SM information and / or the PDU session ID to the AMF (S1412) based on the reception of the PDU session establishment request message and / or the selection of the UPF and / or the reception of the N4 session establishment response message, for example, via the N11 interface. Here, the N1 SM container may include the PDU session establishment acceptance message. Moreover, the PDU session ID may be included in the PDU session establishment acceptance message.

[0357] Next, the AMF that receives the N1 SM container and / or the N2 SM information and / or the PDU session ID sends a NAS message (S1414) to the UE via the first base station device included in the access network (S1416). Here, the NAS message is sent, for example, via the N1 interface. In addition, the NAS message may be a downlink NAS transport (DL NAS TRANSPORT) message.

[0358] Specifically, when the AMF sends an N2 PDU session request message to the base station device included in the access network (S1414), the base station device that receives the N2 PDU session request message sends a NAS message to the UE (S1416). Here, the N2 PDU session request message may include a NAS message and / or N2 SM information. In addition, the NAS message may include a PDU session ID and / or an N1 SM container.

[0359] In addition, the PDU session establishment accept message may be a response message to the PDU session establishment request. In addition, the PDU session establishment accept message may indicate that the establishment of the PDU session is accepted.

[0360] Here, the SMF and / or AMF may indicate that at least part of the UE's request based on the PDU session establishment request message is accepted by sending a PDU session establishment accept message and / or an N1 SM container and / or a PDU session ID and / or a NAS message and / or an N2 SM information and / or an N2PDU session request message.

[0361] Here, the SMF and / or AMF may include at least one of the thirty-first to thirty-second identification information in the PDU session establishment accept message and / or the N1 SM container and / or the NAS message and / or the N2 SM information and / or the N2 PDU session request message for sending.

[0362] The SMF may send the thirty-first identification information to the UE when the NW supports the change of the S-NSSAI based on the anchor relocation. The SMF may send the thirty-second identification information when the change of the S-NSSAI based on the anchor relocation occurs.

[0363] It should be noted that, by sending these identification information and / or PDU session establishment acceptance messages, the SMF can indicate that the network supports each function, that the UE's request is accepted, that the request from the UE is not allowed, or a combination of these information. Moreover, in the case of sending and receiving multiple identification information, two or more of these identification information can constitute more than one identification information. And / or, in the case where one identification information includes multiple meanings, it can be divided into multiple identification information for sending and receiving. For example, information indicating support for each function and information indicating a request to use each function can be sent and received as the same identification information, or as different identification information.

[0364] Specifically, SMF can instruct NW to change S-NSSAI through anchor repositioning by sending the thirty-first identification information, and can also send information indicating whether NW supports the function of changing S-NSSAI through anchor repositioning, and can also indicate that NW supports the function of changing S-NSSAI according to anchor repositioning.

[0365] When the NW and / or the established PDU session supports the change of S-NSSAI based on anchor relocation, the SMF may send the thirty-first identification information, which indicates that the NW and / or the established PDU session supports the change of S-NSSAI based on anchor relocation.

[0366] The SMF may send at least one of the thirty-first to thirty-second identification information based on the reception of at least one of the twenty-first to twenty-third identification information.

[0367] Here, the network can indicate the content of the above identification information to the UE by sending a PDU session establishment accept message.

[0368] It should be noted that the network may also include identification information other than the thirty-first and thirty-second identification information in the PDU session establishment acceptance message for transmission. Specifically, the network may include information indicating the SSC mode corresponding to the established PDU session and / or anchor point in the Selected SSC mode IE for transmission. The network may also include information indicating the SSC mode corresponding to the established PDU session and / or anchor point in the Selected SSC mode IE for transmission.

[0369] The network may also include the S-NSSAI and / or DNN corresponding to the established PDU session in the PDU session establishment accept message and send it.

[0370] It should be noted that, in the case where this process is a PDU session establishment process for the second PDU session in the anchor relocation of the PDU session of SSC modes 2 to 5, the S-NSSAI sent by the SMF is the S-NSSAI associated with the second PDU session, which may be different from the S-NSSAI associated with the first PDU session. And / or, the SST included in the S-NSSAI sent by the SMF may be controlled to be the same as the SST of the S-NSSAI associated with the first PDU session.

[0371] It should be noted that SMF and / or AMF can determine which identification information to include in the PDU session establishment acceptance message and / or N1 SM container and / or NAS message and / or N2 SM information and / or N2 PDU session request message based on the received identification information and / or subscriber information and / or network capability information and / or UE policy and / or operator policy and / or network status and / or user login information and / or context maintained by SMF and / or AMF.

[0372] Next, when the UE receives the NAS message via the N1 interface (S1416), for example, it can recognize that the UE's request based on the PDU session establishment request message is accepted and / or the content of information (message, container, information) included in the NAS message.

[0373] Next, Figure 8 Each step of the process of (B) is described.

[0374] First, based on the reception of the PDU session establishment request message, the SMF sends the N1 SM container and / or the PDU session ID to the AMF via the N11 interface (S1418). Here, the N1 SM container may include a PDU session establishment rejection message. Moreover, the PDU session ID may be included in the PDU session establishment rejection message.

[0375] Next, the AMF that receives the N1 SM container and / or the PDU session ID sends a NAS message (S1420) to the UE via a base station device included in the access network (S1422). Here, the NAS message is sent, for example, via the N1 interface. In addition, the NAS message may be a downlink NAS transport (DL NAS TRANSPORT) message. In addition, the NAS message may include the PDU session ID and / or the N1 SM container.

[0376] In addition, the PDU session establishment rejection message may be a response message to the PDU session establishment request. In addition, the PDU session establishment rejection message may indicate that the establishment of the PDU session is rejected.

[0377] Here, the SMF and / or AMF may indicate that the UE's request based on the PDU session establishment request message is rejected by sending a PDU session establishment reject message and / or an N1 SM container and / or a PDU session ID and / or a NAS message.

[0378] It should be noted that, by sending a PDU session establishment reject message, the SMF can indicate that the UE's request is rejected, that the request from the UE is not allowed, or a combination of these information.

[0379] Here, the SMF and / or AMF may include the thirty-fifth identification information in the PDU session establishment reject message and / or the N1 SM container and / or the NAS message and / or the N2 SM information and / or the N2 PDU session request message for sending.

[0380] It should be noted that SMF and / or AMF can determine which identification information to include in the PDU session establishment reject message and / or N1 SM container and / or NAS message and / or N2 SM information and / or N2 PDU session request message based on the received identification information and / or subscriber information and / or network capability information and / or UE policy and / or operator policy and / or network status and / or user login information and / or context maintained by SMF and / or AMF.

[0381] Next, when the UE receives a NAS message via the N1 interface (S1422), for example, it can identify that the UE's request based on the PDU session establishment request message is rejected and / or the content of information (message, container, information) included in the NAS message.

[0382] Moreover, the UE can identify the content indicated by the received identification information when receiving the thirty-fifth identification information. The UE can identify the content of the above identification information by receiving a NAS message or a PDU session establishment accept message or a PDU session establishment reject message.

[0383] Specifically, the UE may recognize that the NW does not support the change of the S-NSSAI based on anchor relocation based on the reception of the thirty-fifth identification information. And / or, the UE may also recognize that the PDU session establishment request is requested from the NW again based on the reception of the thirty-fifth identification information.

[0384] The UE may start the login request process again based on the receipt of the thirty-fifth identification information, and at this time, may request the NW for the same S-NSSAI as the S-NSSAI associated with the first PDU session.

[0385] Each device can complete this process based on sending and receiving PDU session establishment acceptance messages. At this point, each device can be transformed into a state where it can communicate with the DN using the established PDU session.

[0386] Each device can also complete this process based on the sending and receiving of the PDU session establishment acceptance message or the PDU session establishment rejection message. At this time, each device cannot establish a PDU session, and therefore, cannot communicate with the DN in the absence of a PDU session that has been established.

[0387] It should be noted that the various processes performed by the UE based on the reception of various identification information as described above can also be performed during this process or after this process is completed. [3.4. Login process]

[0388] Next, use Fig.11 The registration procedure is explained below. In this chapter, the registration procedure is sometimes referred to as this procedure. The registration procedure is a process for the UE to take the lead in logging in to the access network_B and / or the core network_B and / or the DN. If the UE is not logged in to the network, this procedure can be performed at any time, such as when the power is turned on. In other words, if the UE is in a non-logged-in state (5GMM-DEREGISTERED state), this procedure can be started at any time. In addition, each device (especially the UE and AMF) can be transformed into a registered state (5GMM-REGISTEDED state) based on the completion of the registration procedure. It should be noted that each registration state can be managed by each device for each access. Specifically, each device can independently manage the registration state for 3GPP access (registered state or non-registered state) and the registration state for non-3GPP access.

[0389] Moreover, the registration process may be a process for updating the location registration information of the UE in the network and / or periodically notifying the network of the status of the UE from the UE and / or updating specific parameters related to the UE in the network.

[0390] The UE can start the login process when it moves to a TA that is outside the current login area. In other words, the UE can start the login process when it moves to a TA different from the TA shown in the maintained TA list. Furthermore, the UE can also start the login process when the context of each device needs to be updated due to the disconnection or failure of the PDU session. Furthermore, the UE can also start the login process when the capability information and / or preferences related to the PDU session establishment of the UE change. Moreover, the UE can also start the login process periodically. Further, the UE can also start the login process based on the completion of the login process or the completion of the PDU session establishment process or the information received from the network in each process. In addition, the UE can also start this process after executing the processes of Chapters 3.1 to 3.4 more than once. It should be noted that the UE can perform the login process at any timing, and is not limited to this.

[0391] In addition, this process can also be performed in a PLMN (HPLMN or VPLMN) or an equivalent PLMN or a SNPN or an equivalent SNPN.

[0392] It should be noted that the above-mentioned process for transitioning from a state where the UE is not logged in to the network (non-logged in state) to a logged in state (logged in state) may be an initial registration procedure or a registration procedure for initial registration. In addition, the registration procedure performed in a state where the UE is logged in to the network (logged in state) may also be a registration procedure for mobility and periodic registration update or a mobility and periodic registration procedure.

[0393] It should be noted that the UE may store or not store each S-NSSAI and / or S-NSSAI recorded in Chapter 2.6 at the time of starting this process. The UE may start this process while storing each S-NSSAI and / or S-NSSAI recorded in Chapter 2.6 at the time of starting this process.

[0394] The details of the login process described below can be applied to any of these.

[0395] First, the UE starts the login process by sending a NAS message (S600)(S602)(S604) including a login request message to the AMF. Specifically, the UE sends an RRC message including a login request message to a base station device (also called 5G AN, gNB) (S600). It should be noted that the login request message may be a NAS message sent and received on the N1 interface. In addition, the RRC message may be a control message sent and received between the UE and the base station device. In addition, the NAS message is processed in the NAS layer, and the RRC message is processed in the RRC layer. It should be noted that the NAS layer is a layer higher than the RRC layer.

[0396] Here, the UE can include at least one of the 41st to 42nd identification information in a login request message and / or an RRC message for sending. Here, the 41st to 42nd identification information can be as described in Chapter 2.6. Moreover, the UE can include identification information indicating the type of this process in the login request message and / or the RRC message for sending. Here, the identification information indicating the type of this process can be a 5GS registration type IE (5GS registration type IE (Information Element)). The 5GS registration type IE is information used to indicate the type of login requested, and can also indicate initial registration, updating of login information accompanied by mobility (mobility registration updating), updating of periodic login information (periodic registration updating), and emergency registration (emergency registration).

[0397] The UE may include the identification information in a control message different from the information, for example, in a control message of a layer lower than the RRC layer (for example, a MAC (Medium Access Control) layer, an RLC (Radio Link Control) layer, a PDCP (Packet Data Convergence Protocol) layer, a SDAP (Service Data Adaptation Protocol) layer, etc.). It should be noted that by sending the identification information, the UE may indicate that the UE supports various functions, may indicate the UE's request, or may indicate both.

[0398] It should be noted that the UE can select and determine whether to send at least one of the 41st to 42nd identification information to the network based on the UE's capability information and / or UE policy and / or UE status and / or user login information and / or context maintained by the UE and / or identification information sent and received in a process executed before this process.

[0399] In addition, when the UE includes the forty-second identification information in the login request message and / or the RRC message, that is, when more than one S-NSSAI is included as the forty-second identification information, it is ideal to include S-NSSAIs belonging to the same NSSRG.

[0400] The UE can store allowed NSSAI, set NSSAI, rejected NSSAI, and mapped S-NSSAI.

[0401] The UE may include information other than the forty-first to forty-second identification information in the login request message and / or the RRC message, for example, may include UE ID and / or PLMN ID and / or AMF identification information for transmission. Here, the AMF identification information may refer to information identifying the AMF or a set of AMFs, for example, may refer to 5G-S-TMSI (5G S-TemporaryMobileSubscriptionIdentifier: 5G S-TemporaryMobileSubscriptionIdentifier), GUAMI (Globally UniqueAMF Identifier: Globally UniqueAMF Identifier).

[0402] In addition, when the 5GS registration type indicates a mobile registration update, and the purpose of starting the login process is not to change the network slice to which the UE is currently logged in, and the UE is in the current login area or the current tracking area, the UE may not include a request for NSSAI in the login process.

[0403] When receiving an RRC message including a login request message, the base station device selects an AMF (S602) to forward the login request message. It should be noted that the base station device can select an AMF based on the identification information included in the login request message and / or the RRC message. Specifically, when the base station device receives at least one of the 41st to 42nd identification information, it can select the AMF to which the login request message is sent based on the received identification information. For example, the base station device can select an AMF included in the network slice identified by the 42nd identification information or an AMF having connectivity to the network slice identified by the 42nd identification information. In addition, the base station device may also select an AMF having an NW function corresponding to the UE capability information indicated by the 41st identification information.

[0404] It should be noted that the AMF selection method is not limited to this, and the base station device can also select AMF based on conditions other than this.

[0405] The base station device extracts the login request message from the received RRC message, and forwards the login request message to the selected AMF (S604). It should be noted that, when at least one of the 41st to 42nd identification information is not included in the login request message but is included in the RRC message, the identification information included in the RRC message can be transmitted to the selected AMF together with the login request message (S604).

[0406] The AMF can perform the first condition determination when receiving the login request message. The first condition determination is used to determine whether the network accepts the UE's request. The AMF can perform the processes of S610 to S612 when the first condition determination is determined to be true. In addition, the AMF can also perform the process of S610 when the first condition determination is determined to be false.

[0407] In addition, the first condition determination may also be performed by a network function (also referred to as NF) other than the AMF. In the case where the NF other than the AMF performs the first condition determination, the AMF may provide the NF with the information required for the first condition determination, specifically, at least a portion of the information received from the UE (S606). Further, in the case where the NF determines the truth or falsity of the first condition determination based on the information received from the AMF, information including the result of the first condition determination (in short, true or false) may be transmitted to the AMF. The AMF may determine the identification information and / or control message to be sent to the UE based on the result of the first condition determination received from the NF.

[0408] It should be noted that, when the first condition is judged to be true, the control message sent and received in S610 may be a registration accept message, and when the first condition is judged to be false, the control message sent and received in S610 may be a registration accept message or a registration reject message.

[0409] It should be noted that the first condition judgment can be performed based on the reception of the login request message and / or the identification information and / or subscriber information and / or network capability information and / or operator policy and / or network status and / or user login information and / or context maintained by the AMF included in the login request message.

[0410] For example, when the network allows or does not reject the UE's request, the first conditional judgment can be determined to be true, and when the network does not allow or reject the UE's request, the first conditional judgment can be determined to be false. In addition, when the network allows or does not reject part of the UE's request, the first conditional judgment can be determined to be true even in the presence of unauthorized UE requests. In addition, when the network does not allow or reject all UE requests, the first conditional judgment can be determined to be false. In addition, when the network of the UE's login destination and / or the device within the network supports the function requested by the UE, the first conditional judgment can be determined to be true, and when the function requested by the UE is not supported, the first conditional judgment can be determined to be false. Further, when the identification information sent and received is allowed, the first conditional judgment can be determined to be true, and when the identification information sent and received is not allowed, the first conditional judgment can be determined to be false.

[0411] The AMF may include one or more of the fifty-first to fifty-third identification information in the control message and send it. Here, the fifty-first to fifty-third identification information may be as described in Chapter 2.6. It should be noted that the AMF may indicate that the network supports each function by sending these identification information and / or control messages, or may indicate that the UE's request is accepted, or may indicate that the request from the UE is not allowed, or may indicate a combination of these information. Moreover, in the case of sending and receiving multiple identification information, two or more of these identification information may constitute one or more identification information. It should be noted that the information indicating support for each function and the information indicating a request to use each function may be sent and received as the same identification information, or may be sent and received as different identification information.

[0412] Upon receiving a login request message including at least one of the 41st to 42nd identification information from the UE, the AMF may include at least one of the 51st to 53rd identification information in a control message for transmission.

[0413] In addition, even in the case of receiving a login request message from the UE that does not include at least one of the 41st to 42nd identification information, the AMF may include at least one of the 51st to 53rd identification information in the control message for transmission.

[0414] The AMF may also include setting NSSAI and / or allowing NSSAI and / or rejecting NSSAI and / or pending NSSAI in a control message for transmission. It should be noted that the fifty-first to fifty-third identification information may be included in allowing NSSAI and / or rejecting NSSAI and / or pending NSSAI for transmission, or may be sent as information different from these.

[0415] The AMF may not have allowed S-NSSAI (Allowed NSSAI) for the UE when sending the control message, but may include a null value in the Allowed NSSAI when there is a reservation to perform the NSSAA procedure after the completion of this procedure or in parallel with this procedure, or when the NSSAA procedure is being performed between the UE and the network, or when the pending NSSAI is included in the control message for sending.

[0416] It should be noted that AMF can determine whether to include at least one of the fifty-first to fifty-third identification information in the control message based on the received identification information and / or subscriber information and / or network capability information and / or operator policy and / or network status and / or user login information and / or context maintained by AMF and / or identification information sent and received in the process executed before this process.

[0417] In addition, the AMF may indicate that the UE's request is accepted by sending a login acceptance message based on the received identification information and / or subscriber information and / or network capability information and / or operator policy and / or network status and / or user login information and / or context maintained by the AMF, or may indicate that the UE's request is rejected by sending a login rejection message.

[0418] The UE receives a control message (a login acceptance message or a login rejection message) and / or the transmitted identification information (at least one of the fifty-first to fifty-third identification information) via the base station device (S610). In the case where the control message is a login acceptance message, the UE can recognize that the request of the UE according to the login request message is accepted and the contents of various identification information included in the login acceptance message by receiving the login acceptance message. In addition, in the case where the control message is a login rejection message, the UE can recognize that the request of the UE according to the login request message is rejected and the contents of various identification information included in the login rejection message by receiving the login rejection message.

[0419] In addition, when the UE receives at least one of the fifty-first to fifty-third identification information from the core network, it can store the information indicated by the received identification information.

[0420] Further, in the case where the control message is a login acceptance message, the UE can send a login completion message to the AMF via the base station device as a response message to the login acceptance message (S612). Here, the login completion message is a NAS message sent and received on the N1 interface, but can also be sent and received between the UE and the base station device in an RRC message.

[0421] The AMF receives the login completion message via the base station device (S612). In addition, each device completes this process based on the transmission and reception of the login acceptance message and / or the login completion message.

[0422] In addition, each device may also complete the login process based on the sending and receiving of the login rejection message.

[0423] It should be noted that each device can also transition or maintain the state in which the UE is logged in to the network (RM_REGISTERED state or 5GMM-REGISTERED state) based on the sending and receiving of the login acceptance message and / or the login completion message, and transition or maintain the state in which the UE is not logged in to the network (RM_DEREGISTERED state or 5GMM-DEREGISTERED state) based on the sending and receiving of the login rejection message when the UE receives the login rejection message for the current PLMN during access. In addition, the transition of each device to each state can also be based on the sending and receiving of the login completion message or the completion of the login process.

[0424] Moreover, each device may implement processing based on information sent and received during the login process based on the completion of the login process. For example, the reason why the UE's request was rejected may be identified when information indicating that a part of the UE's request was rejected is sent and received. Furthermore, each device may implement this process again based on the reason why the UE's request was rejected, and may also implement the login process for the core network_A and other cells.

[0425] Furthermore, the UE may store the identification information received together with the registration accept message and / or the registration reject message based on the completion of the registration procedure, and may also identify the determination of the network.

[0426] In addition, each device can establish corresponding storage for the information sent and received in this process. [4. Embodiments of the present invention]

[0427] The implementation of the present invention may be a combination of the processes described in more than one of the three chapters. For example, in this implementation, a logged-in UE may perform one or more PDU session establishment processes described in Chapter 3.3 to establish a PDU session. Moreover, between the UE and the NW, in a state where at least one first PDU session is established, the PDU session release process of Chapter 3.1 and / or the PDU session release process of Chapter 3.2 and / or the PDU session establishment process of Chapter 3.3 may be performed one or more times.

[0428] Hereinafter, an example of a specific embodiment of the present invention will be described. [4.1. First embodiment]

[0429] Below, use Fig.11 , Figure 8 as well as Fig. 9 A first embodiment (hereinafter referred to as the present embodiment) will be described.

[0430] First, the UE starts by Fig.11 The login process shown. Here, it is assumed that the UE sends a login request message and receives a control message (login acceptance message or login rejection message) from the NW side. Here, it is assumed that at the time point when the login process is completed, the UE is in a state of being logged in to the network (also called a logged-in state, 5GMM-REGISTEDED state).

[0431] Then, the UE starts Figure 8 The PDU session establishment process shown is used to establish a first PDU session. It should be noted that the PDU session establishment request message or NAS message sent by the UE includes not only at least one of the twenty-first to twenty-third identification information, but also the first PDU session ID for identifying the first PDU session, the DNN for identifying the DN of the connection destination, etc. In addition, the twenty-first identification information included in the PDU session establishment request message and / or NAS message sent from the UE can be selected by the UE from the NSSAI shown by the fifty-second or fifty-third identification information received during the login process. In addition, the thirty-second identification information included in the PDU session establishment acceptance message and / or NAS message sent from the NW can be the same as the twenty-first identification information. In addition, the SSC mode (SSC mode 3 or SSC mode 5) can be included in the PDU session establishment acceptance message and / or NAS message sent from the NW. Here, it is assumed that the first PDU session is established at the time point when the PDU session establishment process is completed, and it is assumed that SSC mode 3 or SSC mode 5 is applied to the first PDU session.

[0432] Next, use Fig. 9 The following describes the process of changing the anchor point in SSC mode 3 or SSC mode 5. In other words, the following describes the process of changing the PDU session anchor of the first PDU session associated with SSC mode 3 and / or SSC mode 5 and continuing the session and service.

[0433] It should be noted that, here, SSC mode 3 may mean the second SSC mode 3. Hereinafter, unless otherwise specified, a PDU session and / or anchor point associated with SSC mode 3 may also mean an association with support for changes in S-NSSAI based on anchor relocation.

[0434] also, Fig. 9The SMF#1 and SMF#2 can be devices in the same PLMN or devices in different PLMNs. SMF#1 and SMF#2 can be SMF132. Similarly, Fig. 9 UPF#1 and UPF#2 may be devices in the same PLMN or devices in different PLMNs. UPF#1 and UPF#2 may be UPF130.

[0435] First, as an initial state, the UE may be in a state of establishing a first PDU session via UPF#1. It should be noted that the first PDU session may be managed by SMF#1 and associated with SSC mode 3 and / or SSC mode 5.

[0436] Each device changes to the initial state, so each device can perform the PDU session establishment process in Chapter 3.3 to establish a first PDU session via UPF#1 associated with SSC mode 3 and / or SSC mode 5. The first PDU session can be associated with S-NSSAI#1 and / or DNN#1.

[0437] Next, SMF#1 determines the relocation of the UPF and / or SMF of the first PDU session (S1500). That is, SMF#1 determines the anchor relocation. The determination of the anchor relocation of SMF#1 may be the same as the triggering of the SMF sending the PDU session change command message in the PDU session change process of Chapter 3.1. In addition, the determination may also be made in the case where the UE supports the change of S-NSSAI or network slice based on anchor relocation, and / or the UE supports anchor relocation and the change of S-NSSAI or network slice, and / or the UE supports anchor relocation with the change of S-NSSAI or network slice, and / or the NW and / or the established PDU session supports the change of S-NSSAI or network slice based on anchor relocation, and / or the NW and / or the established PDU session supports the anchor relocation and the change of S-NSSAI or network slice, and / or the NW and / or the established PDU session supports the anchor relocation with the change of S-NSSAI or network slice.

[0438] Specifically, for example, the SMF may determine the relocation of the UPF and / or SMF and / or S-NSSAI based on the reception of a state change notification message sent from the AMF and / or NSSF. For example, the AMF and / or NSSF may send a message notifying the change of the S-NSSAI to SMF#1 based on the expiration of the life time of S-NSSAI#1.

[0439] In addition, for example, AMF and / or NSSF may send a message notifying the change of S-NSSAI to SMF#1 based on the overload of S-NSSAI#1 and / or the NS or NSI indicated by S-NSSAI#1 within the core network.

[0440] Next, SMF#1 starts the PDU session change process and executes the PDU session change process for the first PDU session (S1502). It should be noted that S1502 can be performed by Figure 6 The process of S802 to S812 is implemented. It should be noted that the PDU session change process can be performed when the UE supports changes in S-NSSAI or network slices based on anchor relocation, and / or the UE supports anchor relocation and changes in S-NSSAI or network slices, and / or the UE supports anchor relocation with changes in S-NSSAI or network slices, and / or the NW and / or an established PDU session supports changes in S-NSSAI or network slices based on anchor relocation, and / or the NW and / or an established PDU session supports anchor relocation and changes in S-NSSAI or network slices, and / or the NW and / or an established PDU session supports anchor relocation and changes in S-NSSAI or network slices, and / or the NW and / or an established PDU session supports anchor relocation with changes in S-NSSAI or network slices.

[0441] Specifically, SMF#1 sends a PDU session change command message to the UE via the AMF. The PDU session change command may include at least one of the first to second identification information. The UE receives information and / or messages sent from the SMF and / or AMF.

[0442] For example, SMF#1 may include S-NSSAI#2 in the first identification information for transmission, or may indicate anchor relocation accompanying the change of S-NSSAI through the second identification information. In addition, SMF#1 may also include S-NSSAI (set to S-NSSAI#2) belonging to the same NSSRG as the S-NSSAI (set to S-NSSAI#1) used in the first PDU session in the first identification information for transmission.

[0443] The UE may identify the start of anchor relocation of a PDU session anchor associated with SSC mode 3 and / or SSC mode 5 based on reception of one or more of the first to second identification information and / or a PDU session change command message.

[0444] Specifically, the UE identifies the anchor relocation of the first PDU session based on the reception of the first identification information and / or the second identification information. Here, the first identification information may be S-NSSAI#2 which is different from S-NSSAI#1. Alternatively, the first identification information may be empty, in which case no S-NSSAI may be requested.

[0445] When the UE accepts the request from the NW, it sends a PDU session change accept message to SMF#1. SMF#1 can exchange session change request and / or session change response messages with UPF#1.

[0446] Next, the UE starts the PDU session establishment process via UPF#2, and each device executes the PDU session establishment process via UPF#2 (S1504). S1504 can be performed by Figure 8 The process of S1400 to S1416 is implemented. It should be noted that the PDU session establishment process can be performed when the UE supports changes in S-NSSAI or network slices based on anchor relocation, and / or the UE supports anchor relocation and changes in S-NSSAI or network slices, and / or the UE supports anchor relocation with changes in S-NSSAI or network slices, and / or the NW and / or an established PDU session supports changes in S-NSSAI or network slices based on anchor relocation, and / or the NW and / or an established PDU session supports anchor relocation and changes in S-NSSAI or network slices, and / or the NW and / or an established PDU session supports anchor relocation and changes in S-NSSAI or network slices, and / or the NW and / or an established PDU session supports anchor relocation with changes in S-NSSAI or network slices.

[0447] Specifically, the UE sends a PDU session establishment request message and / or at least one of the twenty-first to twenty-third identification information to SMF#2 via the AMF. The UE may include at least one of the twenty-first to twenty-third identification information in the PDU session establishment request message or the NAS message for transmission.

[0448] When the UE receives the first identification information from the NW and the first identification information is not empty, the S-NSSAI included in the first identification information may be included in the 21st identification information for transmission. When the UE receives empty first identification information from the NW, the 21st identification information may not be transmitted to the NW.

[0449] In other words, when the UE receives information indicating an empty S-NSSAI from the NW, it may send empty twenty-first identification information or may not send the twenty-first identification information.

[0450] SMF#2 selects UPF#2 based on the received information, and each device establishes a second PDU session via UPF#2. The second PDU session may be associated with S-NSSAI#2 and / or DNN#1.

[0451] Furthermore, each device releases the first PDU session via UPF#1 (S1506). The PDU session release process for releasing the first PDU session may be initiated by the UE or by the SMF. For example, S1506 may be Figure 7 The PDU session release process shown. However, in this case, the reason value is different from 5GSM reason #39 "Reactivation request". It should be noted that the PDU session release process can be performed when the UE supports changes in S-NSSAI or network slices based on anchor relocation, and / or the UE supports anchor relocation and changes in S-NSSAI or network slices, and / or the UE supports anchor relocation with changes in S-NSSAI or network slices, and / or the NW and / or established PDU sessions support changes in S-NSSAI or network slices based on anchor relocation, and / or the NW and / or established PDU sessions support anchor relocation and changes in S-NSSAI or network slices, and / or the NW and / or established PDU sessions support anchor relocation and changes in S-NSSAI or network slices, and / or the NW and / or established PDU sessions support anchor relocation with changes in S-NSSAI or network slices.

[0452] As described above, during the login process initiated by the UE, the UE sends a login request message and / or a NAS message including information (the forty-first identification information) indicating that the UE supports anchor relocation with S-NSSAI (Single Network Slice Selection Assistance Information) or a change in network slice, and receives a login acceptance message and / or a NAS message from the NW side.

[0453] Afterwards, the UE establishes a PDU session for a certain S-NSSAI, that is, a first PDU session identified by a first PDU session ID, through a PDU session establishment process initiated by the UE. Here, SSC mode 3 and / or SSC mode 5 are set for the first PDU session.

[0454] Afterwards, the UE receives a PDU session change command message and / or a NAS message including a first S-NSSAI (first identification information) and a first PDU session ID in a PDU session change process initiated by the network. Here, the first S-NSSAI (first identification information) may be an S-NSSAI different from the S-NSSAI used in the first PDU session.

[0455] Afterwards, the UE establishes a PDU session for the first S-NSSAI (S-NSSAI indicated by the first identification information), that is, a second PDU session identified by the second PDU session ID, through the PDU session establishment process initiated by the UE. At this time, the UE sends a PDU session establishment request message and / or a NAS message including the first S-NSSAI (the twenty-first identification information) and the second PDU session ID.

[0456] Afterwards, after establishing the second PDU session, the UE releases the first PDU session corresponding to the first PDU session ID through a PDU session release process initiated by the UE or the NW.

[0457] As described above, each device can change the PDU session anchor of the PDU session associated with SSC mode 3 and / or SSC mode 5 to achieve the continuation of the session and / or service. In other words, each device can change the network slice and change the PDU session anchor to achieve the continuation of the session and / or service. [4.2. Second embodiment]

[0458] Below, use Fig.11 , Figure 8 as well as Fig.10 A second embodiment (hereinafter referred to as the present embodiment) will be described.

[0459] First, the UE starts by Fig.11 The login process shown. Here, it is assumed that the UE sends a login request message and receives a control message (login acceptance message or login rejection message) from the NW side. Here, it is assumed that at the time point when the login process is completed, the UE is in a state of being logged in to the network (also called a logged-in state, 5GMM-REGISTEDED state).

[0460] Then, the UE starts Figure 8The PDU session establishment process shown is used to establish a first PDU session. It should be noted that the PDU session establishment request message or NAS message sent by the UE includes not only at least one of the twenty-first to twenty-third identification information, but also the first PDU session ID for identifying the first PDU session, the DNN for identifying the DN of the connection destination, etc. In addition, the twenty-first identification information included in the PDU session establishment request message and / or NAS message sent from the UE can be selected by the UE from the NSSAI shown by the fifty-second or fifty-third identification information received during the login process. In addition, the thirty-second identification information included in the PDU session establishment acceptance message and / or NAS message sent from the NW can be the same as the twenty-first identification information. In addition, the PDU session establishment acceptance message and / or NAS message sent from the NW may include an SSC mode (SSC mode 2 or SSC mode 4). Here, it is assumed that the first PDU session is established at the time point when the PDU session establishment process is completed, and it is assumed that SSC mode 3 or SSC mode 5 is applied to the first PDU session.

[0461] Next, use Fig.10 The following describes the process of changing the anchor point in SSC mode 2 or SSC mode 4. In other words, the following describes the process of changing the PDU session anchor of the first PDU session associated with SSC mode 2 and / or SSC mode 4 and continuing the session and service.

[0462] It should be noted that, here, SSC mode 2 may mean the second SSC mode. In the following, unless otherwise specified, a PDU session and / or anchor point associated with SSC mode 2 may also mean an association with support for changes in S-NSSAI based on anchor relocation.

[0463] also, Fig.10 The SMF#1 and SMF#2 can be devices in the same PLMN or devices in different PLMNs. SMF#1 and SMF#2 can be SMF132. Similarly, Fig.10 UPF#1 and UPF#2 may be devices in the same PLMN or devices in different PLMNs. UPF#1 and UPF#2 may be UPF130.

[0464] First, as an initial state, the UE may be in a state of establishing a first PDU session via UPF#1. It should be noted that the first PDU session may be managed by SMF#1 and associated with SSC mode 2 and / or SSC mode 4.

[0465] Each device changes to the initial state, so each device can perform the PDU session establishment process in Chapter 3.3 to establish a first PDU session via UPF#1 associated with SSC mode 2 and / or SSC mode 4. The first PDU session can be associated with S-NSSAI#1 and / or DNN#1.

[0466] Next, SMF#1 determines the relocation of the UPF and / or SMF of the first PDU session (S1600). That is, SMF#1 determines the anchor relocation. The determination of the anchor relocation of SMF#1 may be the same as the triggering of the SMF sending the PDU session release command message and / or release request message in the PDU session change process of Chapter 3.2. In addition, the determination may also be made in the case where the UE supports changes in S-NSSAI or network slices based on anchor relocation, and / or the UE supports anchor relocation and changes in S-NSSAI or network slices, and / or the UE supports anchor relocation accompanied by changes in S-NSSAI or network slices, and / or the NW and / or an established PDU session supports changes in S-NSSAI or network slices based on anchor relocation, and / or the NW and / or an established PDU session supports anchor relocation and changes in S-NSSAI or network slices, and / or the NW and / or an established PDU session supports anchor relocation and changes in S-NSSAI or network slices, and / or the NW and / or an established PDU session supports anchor relocation and changes in S-NSSAI or network slices.

[0467] Specifically, for example, the SMF may determine the relocation of the UPF and / or S-NSSAI based on the reception of a state change notification message sent from the AMF and / or NSSF. For example, the AMF and / or NSSF may send a message to SMF#1 notifying the change of the S-NSSAI based on the approaching expiration of the life time of the S-NSSAI#1.

[0468] In addition, for example, AMF and / or NSSF may send a message notifying a change of S-NSSAI to SMF#1 based on S-NSSAI#1 and / or the NSI indicated by S-NSSAI#1 being overloaded within the core network.

[0469] Next, SMF#1 sends DNAI information (S1602) as information for selecting SMF (SMF#2) for establishing the second PDU session to AMF, and AMF receiving the DNAI (DNAI information) sends a response message (S1604) to SMF#1. Here, the DNAI information may constitute information indicating DNN#1 and / or S-NSSAI#2. It should be noted that these processes can be performed when the UE supports changes in S-NSSAI or network slices based on anchor relocation, and / or the UE supports anchor relocation and changes in S-NSSAI or network slices, and / or the UE supports anchor relocation accompanied by changes in S-NSSAI or network slices, and / or the NW and / or established PDU sessions support changes in S-NSSAI or network slices based on anchor relocation, and / or the NW and / or established PDU sessions support anchor relocation and changes in S-NSSAI or network slices, and / or the NW and / or established PDU sessions support anchor relocation and changes in S-NSSAI or network slices, and / or the NW and / or established PDU sessions support anchor relocation accompanied by changes in S-NSSAI or network slices.

[0470] Next, SMF#1 executes a PDU session release process (S1608) for releasing the first PDU session via UPF#1. It should be noted that S1608 may be performed by Figure 7 The process of S902 to S912 is implemented. It should be noted that the PDU session release process can be performed when the UE supports changes in S-NSSAI or network slices based on anchor relocation, and / or the UE supports anchor relocation and changes in S-NSSAI or network slices, and / or the UE supports anchor relocation with changes in S-NSSAI or network slices, and / or the NW and / or an established PDU session supports changes in S-NSSAI or network slices based on anchor relocation, and / or the NW and / or an established PDU session supports anchor relocation and changes in S-NSSAI or network slices, and / or the NW and / or an established PDU session supports anchor relocation and changes in S-NSSAI or network slices, and / or the NW and / or an established PDU session supports anchor relocation with changes in S-NSSAI or network slices.

[0471] Specifically, SMF#1 sends a PDU session release command message to the UE via AMF.

[0472] Here, the SMF and / or AMF may include at least one of the eleventh to twelfth identification information in the PDU session release command message and / or the NAS message, and may also indicate a request for release of the PDU session by including these identification information.

[0473] For example, SMF#1 may include S-NSSAI#2 in the eleventh identification information for transmission, or may indicate anchor relocation accompanying the change of S-NSSAI through the twelfth identification information. In addition, SMF#1 may also include S-NSSAI (set to S-NSSAI#2) belonging to the same NSSRG as the S-NSSAI (set to S-NSSAI#1) used in the first PDU session in the eleventh identification information for transmission.

[0474] The UE receives one or more identification information among the eleventh and twelfth identification information and / or the PDU session change command message. The UE may recognize the start of anchor relocation of the PDU session anchor associated with SSC mode 2 and / or SSC mode 4 based on the reception of one or more identification information among the eleventh and twelfth identification information and / or the PDU session change command message.

[0475] Specifically, the UE identifies the anchor relocation of the first PDU session based on the reception of one or more of the identification information in the eleventh to twelfth identification information. Here, the eleventh identification information may be S-NSSAI#2 which is different from S-NSSAI#1. Alternatively, the eleventh identification information may be empty, in which case no S-NSSAI may be requested.

[0476] When the UE accepts the request from the NW, it sends a PDU session release accept message to SMF#1. SMF#1 can exchange session change request and / or session change response messages with UPF#1. Thus, each device releases the first PDU session.

[0477] Next, the UE starts the PDU session establishment process via UPF#2, and each device executes the PDU session establishment process via UPF#2 (S1610). S1610 can be performed by Figure 8 The process of S1400 to S1416 is implemented. It should be noted that the PDU session establishment process can be performed when the UE supports changes in S-NSSAI or network slices based on anchor relocation, and / or the UE supports anchor relocation and changes in S-NSSAI or network slices, and / or the UE supports anchor relocation with changes in S-NSSAI or network slices, and / or the NW and / or an established PDU session supports changes in S-NSSAI or network slices based on anchor relocation, and / or the NW and / or an established PDU session supports anchor relocation and changes in S-NSSAI or network slices, and / or the NW and / or an established PDU session supports anchor relocation and changes in S-NSSAI or network slices, and / or the NW and / or an established PDU session supports anchor relocation with changes in S-NSSAI or network slices.

[0478] Specifically, the UE sends a PDU session establishment request message and / or at least one of the twenty-first to twenty-third identification information to SMF#2 via the AMF. The UE may include at least one of the twenty-first to twenty-third identification information in the PDU session establishment request message or the NAS message for transmission.

[0479] When the UE receives the eleventh identification information from the NW and the eleventh identification information is not empty, the S-NSSAI included in the eleventh identification information may be included in the twenty-first identification information and sent. When the UE receives empty first identification information from the NW, the twenty-first identification information may not be sent to the NW.

[0480] In other words, when the UE receives information indicating an empty S-NSSAI from the NW, it may send empty twenty-first identification information or may not send the twenty-first identification information.

[0481] SMF#2 selects UPF#2 based on the received information, and each device establishes a second PDU session via UPF#2. The second PDU session may be associated with S-NSSAI#2 and / or DNN#1.

[0482] As described above, during the login process initiated by the UE, the UE sends a login request message and / or a NAS message including the UE capability information (the forty-first identification information) indicating that the UE supports anchor relocation with S-NSSAI (Single Network Slice Selection Assistance Information) or a change of the network slice, and receives a login acceptance message and / or a NAS message from the NW side.

[0483] Afterwards, the UE establishes a PDU session for a certain S-NSSAI, that is, a first PDU session identified by a first PDU session ID, through a PDU session establishment process initiated by the UE. Here, SSC mode 2 and / or SSC mode 4 are set for the first PDU session.

[0484] Afterwards, the UE releases the first PDU session corresponding to the first PDU session ID by receiving a PDU session release command message and / or a NAS message including the first S-NSSAI (the eleventh identification information) and the first PDU session ID during the PDU session release process initiated by the network. Here, the first S-NSSAI (the eleventh identification information) may be an S-NSSAI different from the S-NSSAI used in the first PDU session.

[0485] Afterwards, the UE establishes a PDU session for the first S-NSSAI, i.e., a second PDU session identified by the second PDU session ID, through the PDU session establishment process initiated by the UE. At this time, the UE sends a PDU session establishment request message and / or a NAS message including the first S-NSSAI (the twenty-first identification information) and the second PDU session ID.

[0486] Thus, each device can change the PDU session anchor of the PDU session associated with SSC mode 2 and / or SSC mode 4 to achieve the continuation of the session and / or service. In other words, each device can change the network slice and change the PDU session anchor to achieve the continuation of the session and / or service. [5. Modifications]

[0487] The program running in the device of the present invention may be a program that controls a central processing unit (CPU) or the like to make the computer function in a manner that realizes the functions of the embodiments of the present invention. The program or the information processed by the program is temporarily stored in a volatile memory such as a random access memory (RAM) or a non-volatile memory such as a flash memory, a hard disk drive (HDD) or other storage device system.

[0488] It should be noted that the program for realizing the functions of the embodiments involved in the present invention may also be recorded in a computer-readable recording medium. This can be realized by reading the program recorded in the recording medium into a computer system and executing it. The "computer system" mentioned here refers to a computer system built into a device, and includes a computer system of hardware such as an operating system and peripherals. In addition, the "computer-readable recording medium" may refer to a semiconductor recording medium, an optical recording medium, a magnetic recording medium, a medium that dynamically stores a program for a short period of time, or other computer-readable recording media.

[0489] In addition, each functional block or each feature of the device used in the above-mentioned embodiment can be installed or executed by an electronic circuit, such as an integrated circuit or multiple integrated circuits. The circuit designed to perform the functions described in this specification may include: a general-purpose processor, a digital signal processor (DSP), an integrated circuit (ASIC) for a specific purpose, a field programmable gate array (FPGA), or other programmable logic elements, discrete gates or transistor logic, discrete hardware parts, or a combination thereof. The general-purpose processor can be a microprocessor, or it can be a processor, controller, microcontroller or state machine of the previous type. The aforementioned circuit can be composed of digital circuits or analog circuits. In addition, with the emergence of integrated circuit technology to replace existing integrated circuits through the advancement of semiconductor technology, one or more schemes of the present invention can also use new integrated circuits based on this technology.

[0490] It should be noted that the present invention is not limited to the above-mentioned embodiments. In the embodiments, an example of a device is described, but the present invention is not limited thereto and can be applied to fixed or non-movable electronic devices installed indoors or outdoors, such as AV equipment, kitchen equipment, cleaning / washing equipment, air conditioning equipment, office equipment, vending machines, other life equipment, and other terminal devices or communication devices.

[0491] The embodiments of the present invention are described in detail with reference to the accompanying drawings, but the specific configuration is not limited to the present embodiment, and also includes design changes within the scope of the gist of the present invention. In addition, the present invention can be variously modified within the scope indicated by the claims, and the embodiments obtained by appropriately combining the technical solutions disclosed in different embodiments are also included in the technical scope of the present invention. In addition, it also includes a configuration obtained by replacing the elements that have the same effect as the elements recorded in the above-mentioned embodiments with each other. (Cross-reference of related applications) This application claims the benefit of priority to Japanese patent application No. 2022-072934 filed on April 27, 2022, the entire contents of which are incorporated herein by reference. Description of Reference Numerals 1: Mobile communication system 10: UE_A 30: PGW-U 32: PGW-C 35: SGW 40: MME 45: eNB 50:HSS 60: PCRF 80: Access network_A (E-UTRAN) 90: Core Network_A 120: Access network_B (5G AN) 122: gNB 130: UPF 132: SMF 140:AMF 150: UDM 160: PCF 190: Core Network_B

Claims

1. A core network, comprising a control unit, wherein: The control unit receives the UE capability information from the user equipment UE in the login request message, When session and service continuity SSC mode 3 is set for an established protocol data unit PDU session, determining, for the UE, whether the PDU session change command message includes S-NSSAI different from single network slice selection assistance information S-NSSAI for the PDU session, When SSC mode 2 is set for an established PDU session, it is determined for the UE whether a PDU session release command message includes an S-NSSAI different from the S-NSSAI used for the PDU session.

2. The core network according to claim 1, characterized in that: The UE capability information is UE capability information sent by the UE when anchor relocation is performed with a change in network slice.

3. A user equipment UE, characterized in that: The UE includes a transceiver unit and a control unit. The transceiver sends a login request message during the login process. The registration request message includes UE capability information indicating that the UE supports anchor relocation with single network slice selection assistance information S-NSSAI or a change of network slice, The control unit establishes a first PDU session identified by a first PDU session ID by starting a protocol data unit PDU session establishment process, The control unit sets SSC mode 2 for the first PDU session, The transceiver receives a first S-NSSAI and a PDU session release command message including the first PDU session ID during a PDU session release process, The control unit releases the first PDU session corresponding to the first PDU session ID, The transceiver sends the first S-NSSAI and a PDU session establishment request message including a second PDU session ID, The control unit establishes a second PDU session corresponding to the second PDU session ID using the first S-NSSAI.

4. A user equipment UE, characterized in that: The UE includes a transceiver unit and a control unit. The transceiver sends a login request message during the login process. The registration request message includes information indicating that the UE supports anchor relocation with single network slice selection assistance information S-NSSAI or a change of network slice, The control unit establishes a first PDU session identified by a first PDU session ID by starting a protocol data unit PDU session establishment process, The control unit sets SSC mode 3 for the first PDU session, The transceiver receives a first S-NSSAI and a PDU session change command message including the first PDU session ID during the PDU session change process, The transceiver sends the first S-NSSAI and a PDU session establishment request message including a second PDU session ID, The control unit establishes a second PDU session corresponding to the second PDU session ID using the first S-NSSAI, After establishing the second PDU session, the control unit releases the first PDU session corresponding to the first PDU session ID.

Images