Terminal device, core network device and communication control method

By using the registration request and prohibition list mechanism of NSSAI in the 5G system, the generalization problem of login management between terminal devices and network devices is solved, the effective management and update of login information is realized, and the efficiency of mobile communication services is improved.

CN115426701BActive Publication Date: 2024-12-03SHARP KK
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202211065166.2
Authority / Receiving Office
CN · China
Patent Type
Patents(China)
Current Assignee / Owner
Priority Date
2017-03-17
Filing Date
2018-03-14
Publication Date
2024-12-03
Estimated Expiration
2038-03-14

AI Technical Summary

Technical Problem

In 5G systems, there is a lack of a clear post-login behavior determination mechanism in the login management process between the terminal device and the network device, especially the initial management, update management and regular update management of login information are difficult to achieve generalization.

Method used

By sending a registration request message containing NSSAI during the registration process, and receiving and processing information prohibiting the use of NSSAI in the core network, the prohibited NSSAI is included in the prohibited list to determine the behavior after login.

Benefits of technology

The login management and information update of terminal device information are realized in the communication system, ensuring that the information of terminal device can be correctly logged in and updated in various states, and improving the management efficiency of mobile communication services.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN115426701B_ABST
    Figure CN115426701B_ABST
Patent Text Reader

Abstract

The present invention provides a terminal device, a core network and a communication control method, wherein the terminal device comprises: a transceiver unit and a control unit, wherein the transceiver unit is configured to send a registration request message including single network slice selection auxiliary information S‑NSSAI to an access and mobility management function AMF during a registration process, and receive a response message to the registration request message, wherein the response message includes first identification information or second identification information from the AMF, and the control unit is configured to add the S‑NSSAI to a prohibited list when the first identification information or the second identification information is received, wherein the first identification information indicates that the S‑NSSAI is prohibited in a current public land mobile network PLMN, and the second identification information indicates that the S‑NSSAI is prohibited in a current registration area.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] The present invention relates to a terminal device, a core network device, and a communication control method. This application claims priority based on Japanese Patent Application No. 2017-52492 filed in Japan on March 17, 2017, the entire contents of which are hereby incorporated by reference into this application. Background Art

[0002] In the 3GPP (3rd Generation Partnership Project), which has been conducting standardization activities for mobile communication systems in recent years, the system framework of LTE (Long Term Evolution), namely SAE (System Architecture Evolution), has been studied. As a communication system that realizes full IP (Internet Protocol), 3GPP has standardized EPS (Evolved Packet System). It should be noted that the core network that constitutes EPS is called EPC (Evolved Packet Core).

[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 terms of next-generation communication technology, NextGen (Architecture and Security for Next Generation System: Next-generation system architecture and security) has been studied. Moreover, in 3GPP, as a system for realizing the 5G mobile communication system, 5GS (5G System: 5G system) has been standardized. In 5GS, technical issues for connecting various terminals to cellular networks are extracted and solutions are standardized.

[0004] As request conditions, for example, there can be cited: optimization and diversification of the communication process for information logging into the terminal when connecting various terminals to the cellular network, optimization and optimization of the communication process for information management of the terminal, optimization of the system architecture that matches the optimization and diversification of the communication process, etc.

[0005] Prior art literature

[0006] Non-patent literature

[0007] Non-patent document 1: 3GPP TR 23.799; Technical Specification Group Services and System Aspects; Study on Architecture for Next Generation System; (Release 14)

[0008] Non-patent document 2: 3GPP TS 23.501; Technical Specification Group Services and System Aspects; System Architecture for the 5G System; Stage 2; (Release 15)

[0009] Non-patent document 3: 3GPP TS 23.502; Technical Specification Group Services and System Aspects; Procedures for the 5G System; Stage 2; (Release 15) Summary of the invention

[0010] Problem that the invention aims to solve

[0011] In 5GS, the generalization of registration management in mobile communication services between terminal devices and network devices is being studied. More specifically, the generalization of protocols for managing login information of devices included in the core network facing the terminal devices is being studied to simplify login management, including: initial login of terminal device information to the core network as the login target of the terminal device, update of login information with the mobility of the terminal device, and regular update of login information.

[0012] However, a means for managing login based on the status of the terminal device and the network device, a means for determining the behavior after login, and the like are not yet clear.

[0013] The present invention has been made in view of the above-mentioned problems, and an object of the present invention is to provide a means for managing login based on the status of a terminal device or a network device, a means for determining a behavior after login, and the like.

[0014] Technical Solution

[0015] The terminal device of the present invention is characterized in that it comprises: a transceiver unit, which, during a registration procedure, sends a registration request message including NSSAI (Single Network Slice Selection Assistance information) to a device included in a core network, and receives a registration rejection message including information A indicating that the use of the NSSAI is prohibited from the device included in the core network; and a control unit, which includes the NSSAI in a prohibited list based on the information A, wherein the prohibited list is a list storing one or more prohibited NSSAIs.

[0016] The device included in the core network of the present invention is characterized in that it comprises: a transceiver unit, which, during a registration process, receives a registration request message including NSSAI (Single Network Slice Selection Assistance information) from a terminal device, and sends a registration rejection message including information A indicating that the use of the NSSAI is prohibited to the terminal device; and a control unit.

[0017] The communication control method of the terminal device of the present invention is characterized in that it has the following steps: during the registration process, a registration request message including NSSAI (Single Network Slice Selection Assistance information) is sent to a device included in a core network; a registration rejection message including information A indicating that the use of the NSSAI is prohibited is received from the device included in the core network; and based on the information A, the NSSAI is included in a prohibited list, wherein the prohibited list is a list storing one or more prohibited NSSAIs.

[0018] The communication control method of the device included in the core network of the present invention is characterized in that it also has the following steps: during the registration process, receiving a registration request message including NSSAI (Single Network Slice SelectionAssistance information) from the terminal device; and sending a registration rejection message including information A indicating that the use of the NSSAI is prohibited to the terminal device.

[0019] Beneficial Effects

[0020] According to the present invention, in a communication system in which the protocols used for login management and login information management in mobile communication services are standardized, terminal devices and various devices within the core network can log the information of the terminal devices into various devices based on the states of various devices including control devices and terminal devices included in the communication system, and can update the information of the terminal devices that have logged into various devices. BRIEF DESCRIPTION OF THE DRAWINGS

[0021] Figure 1 This is a diagram for explaining the outline of a mobile communication system.

[0022] Figure 2 is a diagram used to illustrate deployment options for 5G systems.

[0023] Figure 3 This is a diagram for explaining an example of the configuration of a core network and an access network in a mobile communication system.

[0024] Figure 4 This is a diagram used to illustrate the device structure of UE.

[0025] Figure 5 This is a diagram for explaining the storage unit of UE.

[0026] Figure 6 This is a diagram used to illustrate the device structure of eNB / NR node / WAG.

[0027] Figure 7 This is a diagram used to illustrate the device structure of MME / CPF / AMF.

[0028] Figure 8 This is a diagram used to illustrate the storage unit of MME / CPF / AMF.

[0029] Fig. 9 This is a diagram used to illustrate the storage unit of MME / CPF / AMF.

[0030] Fig.10 This is a diagram used to illustrate the device structure of SGW / PGW / UPGW / SCEF / SMF / UPF.

[0031] Fig.11 This is a diagram for explaining the storage unit of SGW.

[0032] Fig.12 This is a diagram used to illustrate the storage unit of PGW / UPGW / SMF / UPF.

[0033] Fig.13 This is a diagram for explaining the storage unit of SCEF.

[0034] Fig.14 It is a diagram used to explain the initial process and / or the update process.

[0035] Fig.15 is a diagram for explaining the registration process. DETAILED DESCRIPTION

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

[0037] [1. Implementation Method]

[0038] [1.1. System Overview]

[0039] Figure 1 FIG. 1 is a diagram for explaining the outline of the mobile communication system according to the present embodiment. Figure 1 As shown, the mobile communication system 1 is composed of a mobile terminal device UE_A10, an access network_B, a core network_B190, and a PDN (Packet Data Network)_A5. Here, UE_A10 can be any terminal device that can perform wireless connection, and can be UE (User Equipment), ME (Mobile Equipment), MS (Mobile Station), or CIoT (Cellular Internet of Things) terminal (CIoT UE), etc. Moreover, the core network can be the core network_B190, and the access network can be the access network_B. Moreover, the core network can also be a core network device. Alternatively, in this embodiment, the core network device can refer to each device included in the core network_B190 and / or a device that performs part or all of the processing or functions of each device. Access network_B can be an access network in a 5G mobile communication system, and can be NextGenRAN_A120 and / or E-UTRAN_A80 and / or WLAN ANc125. Moreover, access network_A can be an access network in a 4G mobile communication system or E-UTRAN_A80.

[0040] In addition, UE_A10 can be connected to the access network and / or the core network. Moreover, UE_A10 can be connected to PDN_A5 via the access network and / or the core network, and then send and receive user data between it and PDN_A5. It should be noted that the user data can be data sent and received between UE_A10 and PDN_A5. Moreover, the sending and receiving (communication) of user data can be implemented using a PDU (Protocol Data Unit or Packet Data Unit: protocol data unit or packet data unit) session, and can also be implemented using a PDN connection (Packet Data Network Connection: packet data network connection). Moreover, the communication of user data is not limited to IP (Internet Protocol: network protocol) communication, but can also be non-IP communication.

[0041] Here, the PDU session or PDN connection (hereinafter, also referred to as PDN connection) is the connectivity established between UE_A10 and PDN_A5 in order to provide PDU connection services such as sending and receiving user data between UE_A10 and PDN_A5. More specifically, the PDU session or PDN connection can be the connectivity established between UE_A10 and an external gateway. Here, the external gateway can be a device that connects the core network and PDN_A5, such as PGW (Packet Data Network Gateway)_A30, UPGW (User PlaneGateway)_A130, and SCEF (Service Capability Exposure Function)_A46.

[0042] In addition, a PDU session or a PDN connection can be a communication path established for sending and receiving user data between UE_A10 and the core network and / or PDN_A5, or a communication path for sending and receiving PDU. Moreover, a PDU session or a PDN connection can be a session established between UE_A10 and the core network and / or PDN_A5, or a logical communication path composed of one or more bearer and other transmission paths between devices within the mobile communication system 1. More specifically, a PDU session can be a connection established between UE_A10 and the core network_B190 and / or an external gateway, or a connection established between UE_A10 and UPGW_A130 or UPF_A235, or a connection such as a PDN connection (Packet Data Network Connection).

[0043] It should be noted that the PDN connection can be the connectivity and / or connection between UE_A10 and PGW_A30 via eNB (evolved Node B)_A45 and / or SGW (Serving Gateway)_A35, or the connectivity and / or connection between UE_A10 and SCEF_A46 via eNB_A45 and / or MME (Mobility Management Entity)_A40. Moreover, the PDU session can be the connectivity and / or connection between UE_A10 and UPGW_A130 or UPF_A235 via NR node_A122. Moreover, the PDN connection can be identified by the PDN connection ID, and the PDU session can also be identified by the PDU session ID. Moreover, the PDN connection and the PDU session can be identified by the EPS bearer ID.

[0044] It should be noted that UE_A10 can use PDU sessions or PDN connections to send and receive user data with devices such as application servers configured to PDN_A5. In other words, PDU sessions or PDN connections can transmit user data sent and received between UE_A10 and devices such as application servers configured to PDN_A5. Moreover, each device (UE_A10, devices in the access network and / or devices in the core network) can establish a correspondence between one or more identification information and the PDU session or PDN connection for management. It should be noted that these identification information may include at least one of APN (Access Point Name), TFT (Traffic Flow Template), session type, application identification information, PDN_A5 identification information, NSI (Network Slice Instance) identification information, DCN (Dedicated Core Network) identification information and access network identification information, and may further include other information. Moreover, in the case of establishing multiple PDU sessions or PDN connections, the content of each identification information corresponding to the PDU session or PDN connection may be the same or different. Furthermore, the NSI identification information is information for identifying the NSI, and may be the following NSI ID or Slice Instance ID.

[0045] In addition, IP communication refers to data communication using IP, which is data communication achieved by sending and receiving IP packets to which IP headers are assigned. It should be noted that the payload constituting the IP packet may include user data sent and received by UE_A10. In addition, non-IP communication refers to data communication that does not use IP, which is data communication achieved by sending and receiving data that is not assigned an IP header. For example, non-IP communication can be data communication achieved by sending and receiving application data that is not assigned an IP packet, or it can be assigned a MAC header, Ethernet (registered trademark) frame header, or other headers to send and receive user data sent and received by UE_A10.

[0046] Moreover, PDN_A5 may be a DN (Data Network) that provides communication services for UE_A10. It should be noted that DN may be constructed as a packet data service network, or may be constructed for each service. Moreover, PDN_A5 may include connected communication terminals. Therefore, connecting to PDN_A5 may refer to connecting to a communication terminal or a server device configured for PDN_A5. Moreover, sending and receiving user data with PDN_A5 may refer to sending and receiving user data with a communication terminal or a server device configured for PDN_A5. It should be noted that PDN_A5 may be expressed as a DN, or DN may be expressed as PDN_A5.

[0047] Moreover, the access network is a wireless network connected to UE_A10 and / or the core network. The access network can be a 3GPP access network or a non-3GPP access network. It should be noted that the 3GPP access network can be E-UTRAN (Evolved Universal Terrestrial Radio Access Network)_A80, NextGen RAN (NextGeneration Radio Access Network)_A120, and the non-3GPP access network can be WLAN ANc125. It should be noted that in order to connect to the core network, UE_A10 can be connected to the access network, or it can be connected to the core network via the access network.

[0048] Moreover, the core network is an IP mobile communication network operated by a mobile communication operator (Mobile Network Operator) connected to the access network and / or PDN_A5. The core network can be a core network for a mobile communication operator that operates and manages the mobile communication system 1, or a core network for virtual mobile communication operators such as MVNO (Mobile Virtual Network Operator) and MVNE (Mobile Virtual Network Enabler), and virtual mobile communication service providers. It should be noted that the core network_B190 can be an EPC (Evolved Packet Core) constituting EPS (Evolved Packet System), or an NGC (Next Generation (Next Gen) Core) constituting NGS (Next Gen System (Next Generation System)), or a 5GC (5G Core Network) constituting 5GS (5G System: 5G System). Moreover, the core network_B190 can be a core network of a system that provides 5G communication services. It should be noted that the core network_B190 is not limited thereto, and may also be a network that provides mobile communication services. It should be noted that the EPS may be a system that implements a 4G mobile communication system. Moreover, the 5GS and / or NGS may be a system that implements a 5G mobile communication system.

[0049] Next, an example of the configuration of the core network_B190 is described. An example of the configuration of the core network_B190 is described. Figure 3 An example of the configuration of the core network_B190 is shown in FIG. Figure 3 The core network (a)_B190 is composed of HSS_A50, PCRF_A60, SMF (Session Management Function)_A230, UPF (User Plane Function)_A235, AMF (Access and Mobility Management Function)_A240, and SCEF_A46.

[0050] It should be noted that SMF_A230 and / or AMF_A240 can be CPF (Control Plane Function)_A140, and UPF_A235 can be PGW (User Plane Gateway)_A130. Therefore, SMF_A230 and / or AMF_A240 can be expressed as CPF_A140, and CPF_A140 can be expressed as SMF_A230 and / or AMF_A240. Moreover, UPF_A235 can be expressed as UPGW_A130, and UPGW_A130 can be expressed as UPF_A235. In addition, the core network_B190 can be connected to multiple radio access networks (E-UTRAN_A80, NextGen RAN_A120, WLAN ANc125). The radio access network can be configured to be connected to multiple different access networks, or it can be configured to be connected to any one access network. Moreover, UE_A10 can wirelessly connect to the wireless access network.

[0051] Furthermore, the access network that can be connected through the 3GPP access system can be composed of E-UTRAN_A80 and NextGenRAN_A120. Furthermore, the access network that can be connected through the WLAN access system can be composed of a WLAN access network c (WLAN ANc125) connected to CPF_A140 or AMF_A240 and UPGW_A130 or UPF_A235. Below, each device is briefly described.

[0052] UPGW_A130 or UPF_A235 is a device connected to PDN_A5, CPF_A140 or SMF_A230, E-UTRAN80, NextGenRAN_A120 and WLAN ANc125, and is a relay device that transmits user data as a gateway between PDN_A5 and / or DN and core network_B190. It should be noted that UPGW_A130 or UPF_A235 can be a gateway for IP communication and / or non-IP communication. Moreover, UPGW_A130 or UPF_A235 can have the function of transmitting IP communication, and can also have the function of converting non-IP communication and IP communication. It should be noted that multiple such gateways can be configured in core network_B190. And the configured multiple gateways can be gateways connecting core network_B190 and a single DN. It should be noted that UPGW_A130 or UPF_A235 can have connectivity with other NFs and can be connected to each device via other NFs. It should be noted that UPGW_A130 or UPF_A235 can be SGW_A35 and / or PGW_A30.

[0053] PGW_A30 is a relay device connected to PDN_A5, SGW_A35 and PCRF_A60, and serves as a gateway between PDN_A5 and / or DN and core network_B190 to transmit user data. It should be noted that PGW_A30 can be a gateway for IP communication and / or non-IP communication.

[0054] Moreover, PGW_A30 may have the function of transmitting IP communication and the function of converting non-IP communication and IP communication. It should be noted that multiple such gateways may be configured in the core network_B190. Moreover, the multiple configured gateways may be gateways connecting the core network_B190 and a single DN.

[0055] It should be noted that U-Plane (User Plane) may be a communication path for sending and receiving user data and may be composed of multiple bearers. Also, C-Plane (Control Plane) may be a communication path for sending and receiving control messages and may be composed of multiple bearers.

[0056] Furthermore, PGW_A30 can be connected to the UP function and the Policy function, and can also be connected to UE_A10 via U-Plane. Furthermore, PGW_A30 can be configured together with UPGW_A130 or UPF_A235.

[0057] SGW_A35 is connected to PGW_A30, MME_A40 and E-UTRAN_A80, and serves as a relay device for transmitting user data as a gateway between the core network_B190 and the 3GPP access network (E-UTRAN_A80, NextGen RAN_A120).

[0058] Moreover, SGW_A35 can be a UP function for transmitting user data having a connection with the access network, or it can be a UPGW (User Plane Gateway)_A130 which serves as a gateway for transmitting user data between the access network and the core network.

[0059] Moreover, CPF_A140 is a device connected to UPGW_A130 or UPF_A235, E-UTRAN_A80, NextGen RAN_A120, WLAN ANc125, HSS_A50 and SCEF_A46. CPF_A140 can be an NF that plays the role of mobility management of UE_A10, etc., or an NF that plays the role of session management of PDU sessions, etc., or an NF that manages one or more NSIs. In addition, CPF_140 can also be an NF that plays one or more of the above roles. It should be noted that NF can be one or more devices configured in the core network_B190, or a CP function (Control Plane Function or Control Plane Network Function: control plane network function) for control information and / or control messages, or a shared CP function (CCNF, Common CPNF (Control Plane Network Function): common control plane network function) shared among multiple NSIs. It should be noted that CPF_A140 may have connectivity with other NFs and may be connected to various devices via other NFs. It should be noted that CPF_A140 may be MME_A40 or an NF having the functions of AMF_A240 and SMF_A230.

[0060] Moreover, AMF_A240 is a device connected to SMF_A230, E-UTRAN_A80, NextGen RAN_A120, WLAN ANc125, HSS_A50 and SCEF_A46. AMF_A240 can be an NF that plays the role of mobility management of UE_A10, etc., or it can be an NF that manages one or more NSIs. In addition, AMF_A240 can be an NF that plays one or more of the above roles. It should be noted that NF can be one or more devices configured in the core network_B190, or it can be a CP function (Control Plane Function or Control Plane Network Function: control plane network function) for control information and / or control messages, or it can be a shared CP function (CCNF, CommonCPNF (Control Plane Network Function): common control plane network function) shared among multiple NSIs. It should be noted that AMF_A240 can have connectivity with other NFs and can be connected to each device via other NFs. It should be noted that AMF_A240 may be a NF having some of the functions of CPF_A140.

[0061] Moreover, SMF_A230 is a device connected to AMF_A240, UPF_A235, HSS_A50 and PCRF_A60. SMF_A230 can be an NF that plays a role in session management such as PDU sessions. It should be noted that NF can be one or more devices configured in the core network_B190, or it can be a CP function (ControlPlane Function or Control Plane Network Function: control plane network function) for control information and / or control messages, or it can be a shared CP function (CCNF, Common CPNF (Control Plane Network Function): common control plane network function) shared among multiple NSIs. It should be noted that SMF_A230 can have connectivity with other NFs and can be connected to each device via other NFs. It should be noted that SMF_A230 can be an NF with some of the functions of CPF_A140.

[0062] MME_A40 is a control device that is connected to SGW_A35, access network, HSS_A50, and SCEF_A46, and performs location information management and access control including mobility management of UE_A10 via the access network. In addition, MME_A40 may function as a session management device that manages sessions established by UE_A10.

[0063] In addition, a plurality of such control devices may be configured in the core network_B190, for example, it may be composed of a location management device different from the MME_A40. The location management device different from the MME_A40 may be connected to the SGW_A35, the access network, the SCEF_A46, and the HSS_A50 in the same manner as the MME_A40.

[0064] In addition, when multiple MMEs are included in the core network_B190, the MMEs can be connected to each other. As a result, the context of UE_A10 can be sent and received between MMEs. In this way, MME_A40 only needs to be a management device for sending and receiving control information related to mobility management and session management with UE_A10, in other words, it only needs to be a control device of the control plane (Control Plane; C-Plane; CP).

[0065] Furthermore, although MME_A40 is described as being included in the core network_B190, MME_A40 may be a management device formed in one or more core networks or DCNs or NSIs, or may be a management device connected to one or more core networks or DCNs or NSIs. Here, multiple DCNs or NSIs may be used by a single communication operator or by different communication operators.

[0066] In addition, MME_A40 may be a relay device that transmits user data as a gateway between the core network_B190 and the access network. It should be noted that the user data sent and received using MME_A40 as a gateway may be small data.

[0067] Moreover, MME_A40 can be an NF that plays a role of mobility management for UE_A10, etc., or an NF that plays a role of session management for PDU sessions, etc., or an NF that manages one or more NSIs. In addition, MME_A40 can be an NF that plays one or more of the above roles. It should be noted that the NF can be one or more devices configured in the core network_B190, or a CP function for control information and / or control messages (hereinafter also referred to as CPF (Control Plane Function) or Control Plane Network Function: Control Plane Network Function), or a shared CP function shared among multiple NSIs.

[0068] Here, NF refers to a processing function constructed within the network. That is, NF can be a functional device such as MME, SGW, PGW, CPF, UPGW, or a function or capability information such as MM (Mobility Management) and SM (Session Management). In addition, NF can be a functional device for implementing a single function or a functional device for implementing multiple functions. For example, there can be a NF for implementing an MM function and a NF for implementing an SM function, or there can be a NF for implementing both the MM function and the SM function.

[0069] SCEF_A46 is connected to PDN_A5, CPF_A140 or AMF_A240 or MME_A40 and HSS_A50, and serves as a relay device that connects PDN_A5 and / or DN with the gateway of core network_B190 to transmit user data. It should be noted that SCEF_A46 can be a gateway for non-IP communication. Moreover, SCEF_A46 can have the function of converting non-IP communication and IP communication. In addition, multiple such gateways can be configured in core network_B190. Moreover, multiple gateways that connect core network_B190 with a single PDN_A5 and / or DN can also be configured. It should be noted that SCEF_A46 can be constructed on the outside of the core network or on the inside.

[0070] HSS_A50 is a management node that is connected to MME_A40, AMF_A240, SMF_A230, and SCEF_A46 to manage subscriber information. The subscriber information of HSS_A50 is referenced, for example, during access control by MME_A40. Moreover, HSS_A50 can be connected to a location management device different from MME_A40. For example, HSS_A50 can be connected to CPF_A140, AMF_A240, or SMF_A230. HSS_A50 can be UDM (Unified Data Management).

[0071] PCRF_A60 is connected to UPGW_A130 or SMF_A230 or PGW_A30 and PDN_A5 to perform QoS management for data transmission. For example, it manages the QoS of the communication path between UE_A10 and PDN_A5. In addition, PCRF_A60 can be a device that formulates and / or manages PCC (Policy and Charging Control) rules and / or routing rules used by each device when sending and receiving user data.

[0072] In addition, PCRF_A60 may also be a policy function that formulates and / or manages policies. In more detail, PCRF_A60 may be connected to a UP function. PCRF_A60 may also be a PCF (Policy function).

[0073] In addition, if Figure 3 As shown in (b), each wireless access network includes a device (eg, a base station device, an access point device) to which UE_A10 is actually connected. The device used for connection can be a device suitable for the wireless access network.

[0074] In this embodiment, E-UTRAN_A80 is an access network of LTE (Long Term Evolution), and is configured to include eNB_A45. eNB_A45 is a wireless base station for UE_A10 to connect via E-UTRA (Evolved Universal Terrestrial Radio Access), and can be configured to include one or more eNB_A45 in E-UTRAN_A80. In addition, multiple eNBs can be connected to each other.

[0075] Moreover, NextGen RAN_A120 is a 5G access network, which is configured to include NR node (New Radio Access Technology node: new radio access technology node) _A122. NR node_A122 is a wireless base station for UE_A10 to connect through NextGen RA (Next Generation Radio Access), and can be configured to include one or more NR node_A122 in NextGen RAN_A120. It should be noted that when a plurality of NR node_A122 are included in NextGen RAN_A120, it can be configured to include NR node_A122 and NR node_B123 in NextGen RAN_A120. In this case, NR node_B123 can be the same as NR node_A122.

[0076] Furthermore, NextGen RAN_A120 may be an access network composed of E-UTRA and / or NextGen RA. In other words, NextGen RAN_A120 may include eNB_A45, NR node_A122, or both. In this case, eNB_A45 and NR node_A122 may also be the same device. Therefore, NR node_A122 can be replaced with eNB_A45.

[0077] It should be noted that NextGen RAN_A120 can be 5G-RAN (5G Radio Access Network) or 5G-AN (5G Access Network). In other words, NextGenRAN_A120 can be expressed as 5G-RAN and / or 5G-AN, and 5G-RAN and / or 5GN-AN can be expressed as NextGen RAN_A120.

[0078] In addition, NR node_A122 can be a gNB. In other words, NR node_A122 can be expressed as a gNB, or a gNB can be expressed as NR node_A122.

[0079] WLAN ANc125 is a wireless LAN access network, and is configured to include WAG_A126. WAG (WLAN Access Gateway: Wireless LAN Access Gateway)_A126 is a wireless base station for UE_A10 to connect via wireless LAN access, and can be configured to include one or more WAG_A126 in WLAN ANc125. Moreover, WAG_A126 can be a gateway between the core network_B190 and WLAN ANc125. In addition, in WAG_A126, the functional part of the wireless base station and the functional part of the gateway can be composed of different devices.

[0080] It should be noted that, in this specification, UE_A10 is connected to each radio access network, which means that it is connected to the base station device, access point, etc. included in each radio access network, and the data and signals received and sent are also transmitted through the base station device and access point. It should be noted that regardless of the type of access network, the control messages sent and received between UE_A10 and core network_B190 can be the same control messages. Therefore, the UE_A10 and core network_B190 sending and receiving messages via NR node_A122 can be the same as the UE_A10 and core network_B190 sending messages via eNB_A45 and / or WAG_A126.

[0081] [1.2. Device configuration]

[0082] First, the identification information stored in each device is explained. IMSI (International Mobile Subscriber Identity) is permanent identification information of a subscriber (user), and is identification information assigned to a user using a UE. The IMSI stored in UE_A10, MME_A40 / CPF_A140 / AMF_A2400, and SGW_A35 can be equivalent to the IMSI stored in HSS_A50.

[0083] EMM State / MM State indicates the mobility management state of UE_A10 or MME_A40 / CPF_A140 / AMF_A240. For example, EMM State / MM State can be the EMM-REGISTERED state (login state) in which UE_A10 logs in to the network and / or the EMM-DEREGISTERD state (non-login state) in which UE_A10 is not logged in to the network. In addition, EMM State / MM State can be the ECM-CONNECTED state that maintains the connection between UE_A10 and the core network and / or the ECM-IDLE state that releases the connection. It should be noted that EMM State / MM State can be information that can distinguish between the state of UE_A10 logging in to EPC and the state of logging in to NGC or 5GC.

[0084] GUTI (Globally Unique Temporary Identity) is the temporary identification information of UE_A10. GUTI is composed of the identification information of MME_A40 / CPF_A140 / AMF_A240 (GUMMEI (Globally Unique MME Identifier)) and the identification information of UE_A10 within a specific MME_A40 / CPF_A140 / AMF_A240 (M-TMSI (M-Temporary Mobile Subscriber Identity)). ME Identity is the ID of UE_A10 or ME, for example, it can be IMEI (International Mobile Equipment Identity) or IMEISV (IMEI Software Version). MSISDN represents the basic telephone number of UE_A10. The MSISDN stored in MME_A40 / CPF_A140 / AMF_A240 can be information indicated by the storage unit of HSS_A50. It should be noted that the GUTI may include information for identifying the CPF_140.

[0085] MME F-TEID is information for identifying MME_A40 / CPF_A140 / AMF_A240. MME F-TEID may include the IP address of MME_A40 / CPF_A140 / AMF_A240, may include the TEID (Tunnel Endpoint Identifier) ​​of MME_A40 / CPF_A140 / AMF_A240, or may include both. In addition, the IP address of MME_A40 / CPF_A140 / AMF_A240 and the TEID of MME_A40 / CPF_A140 / AMF_A240 may be stored independently. In addition, MME F-TEID may be identification information for user data or identification information for control information.

[0086] SGW F-TEID is information for identifying SGW_A35. SGW F-TEID may include the IP address of SGW_A35, the TEID of SGW_A35, or both. In addition, the IP address of SGW_A35 and the TEID of SGW_A35 may be stored independently. In addition, SGW F-TEID may be identification information for user data or identification information for control information.

[0087] PGW F-TEID is information for identifying PGW_A30 / UPGW_A130 / SMF_A230 / UPF_A235. PGW F-TEID may include the IP address of PGW_A30 / UPGW_A130 / SMF_A230 / UPF_A235, may include the TEID of PGW_A30 / UPGW_A130 / SMF_A230 / UPF_A235, or may include both. In addition, the IP address of PGW_A30 / UPGW_A130 / SMF_A230 / UPF_A235 and the TEID of PGW_A30 / UPGW_A130 / SMF_A230 / UPF_A235 may be stored independently. In addition, PGW F-TEID may be identification information for user data or identification information for control information.

[0088] The eNB F-TEID is information for identifying the eNB_A45. The eNB F-TEID may include the IP address of the eNB_A45, the TEID of the eNB_A45, or both. In addition, the IP address of the eNB_A45 and the TEID of the SGW_A35 may be stored independently. In addition, the eNB F-TEID may be identification information for user data or identification information for control information.

[0089] In addition, APN can be identification information for identifying the core network and external networks such as DN. Moreover, APN can also be used as information for selecting gateways such as PGW_A30 / UPGW_A130 / UPF_A235 connected to the core network A_90. It should be noted that APN can be DNN (Data Network Name). Therefore, APN can be expressed as DNN, and DNN can also be expressed as APN.

[0090] It should be noted that APN can be identification information for identifying such a gateway, or identification information for identifying an external network such as a DN. It should be noted that in the case where multiple gateways connected to the core network and the DN are configured, there may be multiple gateways that can be selected by the APN. Moreover, a gateway may be selected from such multiple gateways by other methods using identification information other than the APN.

[0091] UE Radio Access Capability is identification information indicating the radio access capability of UE_A10. UE Network Capability includes security algorithms and key derivation functions supported by UE_A10. MS Network Capability is information including one or more information required by SGSN_A42 for UE_A10 with GERAN_A25 and / or UTRAN_A20 functions. Access Restriction is login information for access restriction. eNB Address is the IP address of eNB_A45. MME UE S1APID is information for identifying UE_A10 within MME_A40 / CPF_A140 / AMF_A240. eNB UE S1AP ID is information for identifying UE_A10 within eNB_A45.

[0092] APN in Use is the most recently used APN. APN in Use may be a Data Network Identifier. The APN may be composed of network identification information and default operator identification information. Furthermore, APN in Use may be information identifying the DN of the establishment destination of the PDU session.

[0093] Assigned Session Type is information indicating the type of PDU session. AssignedSession Type can also be Assigned PDN Type. The type of PDU session can be IP or non-IP. Moreover, when the type of PDU session is IP, it can further include information indicating the type of PDN assigned by the network. It should be noted that Assigned Session Type can be IPv4, IPv6 or IPv4v6.

[0094] In addition, if there is no special record, IP Address is the IP address assigned to the UE. The IP address can be an IPv4 address, an IPv6 address, or an IPv6 prefix. It should be noted that when AssignedSession Type indicates non-IP, the IP Address element may not be included.

[0095] DN ID is identification information for identifying the core network_B190 and external networks such as DN. In addition, DN ID can also be used as information for selecting a gateway such as UPGW_A130 or PF_A235 connected to the core network_B190.

[0096] It should be noted that DN ID can be identification information for identifying such a gateway, or identification information for identifying an external network such as DN. It should be noted that, in the case where multiple gateways connecting the core network_B190 and the DN are configured, there may be multiple gateways that can be selected by DNID. Moreover, a gateway may be selected from such multiple gateways by other methods using identification information other than DN ID.

[0097] Moreover, DN ID can be information equivalent to APN or different from APN. It should be noted that when DN ID and APN are different information, each device can manage information indicating the correspondence between DN ID and APN, and can also implement the process of using DN ID to query APN, and can also implement the process of using APN to query DN ID.

[0098] SCEF ID is the IP address of SCEF_A46 used in the PDU session. Default Bearer is information acquired and / or generated when establishing a PDU session, and is EPS bearer identification information used to identify the default bearer corresponding to the PDU session.

[0099] EPS Bearer ID (EPS bearer ID) is the identification information of the EPS bearer. In addition, EPS Bearer ID can be identification information for identifying SRB (Signalling Radio Bearer) and / or CRB (Control-plane Radiobearer), or identification information for identifying DRB (Data Radio Bearer). TI (Transaction Identifier) ​​is identification information for identifying a bidirectional message flow (Transaction). It should be noted that EPS Bearer ID can be EPS bearer identification information for identifying a dedicated bearer. Therefore, it can be identification information for identifying an EPS bearer different from the default bearer. TFT represents all packet filters associated with the EPS bearer. TFT is information that identifies a part of the user data being sent and received, and UE_A10 uses the EPS bearer associated with TFT to send and receive user data identified by TFT. In other words, UE_A10 uses the RB (Radio Bearer) associated with TFT to send and receive user data identified by TFT. In addition, the TFT may establish a correspondence between the received and sent user data such as application data and an appropriate transmission path, which may be identification information for identifying the application data. In addition, the UE_A10 may use the default bearer to send and receive user data that cannot be identified by the TFT. In addition, the UE_A10 may pre-store the TFT associated with the default bearer.

[0100] Default Bearer is the EPS bearer identification information that identifies the default bearer corresponding to the PDN session. It should be noted that the EPS bearer can be either a logical communication path established between UE_A10 and UPGW_A130, or a communication path that constitutes a PDU connection / PDU session. Moreover, the EPS bearer can be either a default bearer or a dedicated bearer. Moreover, the EPS bearer can be constituted to include RBs established between UE_A10 and base stations and / or access points in the access network. Moreover, the RB can be mapped one-to-one to the EPS bearer. Therefore, the identification information of the RB can correspond one-to-one to the identification information of the EPS bearer, or it can be the same identification information. It should be noted that the RB can be an SRB and / or a CRB, or it can be a DRB. In addition, the Default Bearer can be the information obtained by UE_A10 and / or SGW_A35 and / or PGW_A30 / UPGW_A130 / SMF_A230 / UPF_A235 from the core network when establishing a PDU session. It should be noted that the default bearer is the EPS bearer initially established in the PDN connection / PDU session, and is an EPS bearer that can only be established in one PDN connection / PDU session. The default bearer can be an EPS bearer that can be used in communications of user data that have not established a corresponding TFT. In addition, a dedicated bearer is an EPS bearer that is established after the default bearer is established in the PDN connection / PDU session, and is an EPS bearer that can be established in multiple PDN connection / PDU sessions. A dedicated bearer is an EPS bearer that can be used in communications of user data that have established a corresponding TFT.

[0101] User Identity is information that identifies the subscriber. User Identity can be IMSI or MSISDN. Moreover, User Identity can also be identification information other than IMSI and MSISDN. Serving Node Information is information that identifies the MME_A40 / CPF_A140 / AMF_A240 used in the PDU session, and can be the IP address of MME_A40 / CPF_A140 / AMF_A240.

[0102] eNB Address is the IP address of eNB_A45. eNB ID is information that identifies the UE within eNB_A45. MME Address is the IP address of MME_A40 / CPF_A140 / AMF_A240. MME ID is information that identifies MME_A40 / CPF_A140 / AMF_A240. NR node Address is the IP address of NR node_A122. NR node ID is information that identifies NR node_A122. WAG Address is the IP address of WAG_A126. WAG ID is information that identifies WAG_A126.

[0103] The configuration of each device is described below. It should be noted that part or all of the functions of each device and each part of each device described below may be executed on physical hardware or on logical hardware virtually configured on general-purpose hardware.

[0104] [1.2.1. UE configuration]

[0105] exist Figure 4 The device structure of UE_A10 is shown in FIG. Figure 4 As shown, UE_A10 is composed of a transceiver_A420, a control unit_A400, and a storage unit_A440. The transceiver_A420 and the storage unit_A440 are connected to the control unit_A400 via a bus. The control unit_A400 is a functional unit for controlling UE_A10. The control unit_A400 implements various processes by reading and executing various programs stored in the storage unit_A440.

[0106] The transceiver_A420 is a functional unit for connecting the UE_A10 to a base station and / or an access point in the access network and to the access network. In addition, the transceiver_A420 is connected to an external antenna_A410. In other words, the transceiver_A420 is a functional unit for connecting the UE_A10 to a base station and / or an access point in the access network. Moreover, the transceiver_A420 is a transceiver functional unit for the UE_A10 to send and receive user data and / or control information from a base station and / or an access point in the access network.

[0107] The storage unit_A440 is a functional unit for storing programs and data required for various actions of the UE_A10. The storage unit_A440 is composed of, for example, a semiconductor memory, a HDD (Hard Disk Drive), etc. The storage unit_A440 can at least store identification information and / or control information and / or flags and / or parameters included in the control messages sent and received in the communication process described later. Figure 4As shown, UE context 442 is stored. The following describes the information elements stored in storage unit_A440. It should be noted that UE context 442 may include a UE context used when connected to core network_B190 and a UE context used when connected to core network_B190. Moreover, the UE context used when connected to core network_B190 and the UE context used when connected to core network_B190 may be stored together or separately.

[0108] First, in Figure 5 (b) of FIG. 1 shows the information elements included in the UE context stored for each UE. Figure 5 As shown in (b), the UE context stored for each UE includes MSI, EMM State, GUTI, and ME Identity. Figure 5 (c) shows the UE context for each PDU session or PDN connection stored for each PDU session or PDN connection. Figure 5 As shown in (c), the UE context of each PDU session includes APN in Use, Assigned SessionType, IP Address(es), and Default Bearer.

[0109] exist Figure 5 (d) shows the UE context for each bearer stored in the storage unit of the UE. Figure 5 As shown in (d), the UE context of each bearer includes EPS Bearer ID, TI, and TFT.

[0110] [1.2.2. eNB / NR node / WAG configuration]

[0111] The following describes the configuration of eNB_A45, NR node_A122, and WAG_A126. Figure 6 The device configuration of eNB_A45, NR node_A122 and WAG_A126 is shown in FIG. Figure 6 As shown, eNB_A45, NR node_A122 and WAG_A126 are composed of a network connection unit_B620, a transceiver unit_B630, a control unit_B600 and a storage unit_B640. The network connection unit_B620, the transceiver unit_B630 and the storage unit_B640 are connected to the control unit_B600 via a bus.

[0112] The control unit_B600 is a functional unit for controlling the eNB_A45. The control unit_B600 implements various processes by reading and executing various programs stored in the storage unit_B640.

[0113] The network connection unit_B620 is a functional unit for connecting the eNB_A45, NR node_A122 and WAG_A126 to the MME_A40 and / or SGW_A35. In addition, the network connection unit_B620 is a transceiver for the eNB_A45, NR node_A122 and WAG_A126 to send and receive user data and / or control information from the MME_A40 and / or SGW_A35.

[0114] The transceiver_B630 is a functional unit for connecting the eNB_A45, NR node_A122, and WAG_A126 to the UE_A10. The transceiver_B630 is a transceiver functional unit for transmitting and receiving user data and / or control information from the UE_A10. In addition, the transceiver_B630 is connected to the external antenna_B610.

[0115] The storage unit_B640 is a functional unit that stores programs, data, etc. required for each action of the eNB_A45, NR node_A122, and WAG_A126. The storage unit_B640 is composed of, for example, a semiconductor memory, an HDD, etc. The storage unit_B640 can at least store identification information and / or control information and / or flags and / or parameters included in the control message sent and received in the communication process described later. The storage unit_B640 can store this information as a context for each UE_A10.

[0116] [1.2.3.MME / CPF / AMF composition]

[0117] The following describes the configuration of MME_A40, CPF_140, and AMF_A240. Figure 7 The device configuration of MME_A40, CPF_140 and AMF_A240 is shown in FIG. Figure 7 As shown, MME_A40, CPF_140 and AMF_A240 are composed of a network connection unit_C720, a control unit_C700 and a storage unit_C740. The network connection unit_C720 and the storage unit_C740 are connected to the control unit_C700 via a bus. It should be noted that the functions of these units can be run on physical hardware or on logical hardware that is virtually constructed on general hardware.

[0118] The control unit_C700 is a functional unit for controlling the MME_A40, CPF_140, and AMF_A240. The control unit_C700 reads and executes various programs stored in the storage unit_C740 to implement various processes.

[0119] The network connection unit_C720 is a functional unit for connecting the MME_A40 with a base station in the access network and / or an access point in the access network and / or SCEF_A46 and / or HSS_A50 and / or SGW_A35. In addition, the network connection unit_C720 is a transceiver for MME_A40 to send and receive user data and / or control information with a base station in the access network and / or an access point in the access network and / or SCEF_A46 and / or HSS_A50 and / or SGW_A35.

[0120] Furthermore, the network connection unit_C720 is a functional unit for connecting CPF_140 with a base station in the access network and / or an access point in the access network and / or SCEF_A46 and / or HSS_A50 and / or UPGW_A130 and / or UPF_A235 and / or SMF_A230. Furthermore, the network connection unit_C720 is a transceiver unit for MME_A40 to send and receive user data and / or control information with a base station in the access network and / or an access point in the access network and / or SCEF_A46 and / or HSS_A50 and / or UPGW_A130 and / or UPF_A235.

[0121] The storage unit_C740 is a functional unit that stores programs, data, etc. required for each operation of the MME_A40, CPF_140, and AMF_A240. The storage unit_C740 is composed of, for example, a semiconductor memory, an HDD, etc. The storage unit_C740 can at least store identification information and / or control information and / or flags and / or parameters included in the control messages sent and received in the communication process described later.

[0122] Storage Unit_C740 Figure 7 The MME context 742 is shown as being stored. The information elements stored in the storage unit _C740 are described below. It should be noted that in the MME context, CPF_140 can be a storage context. First, in Figure 8 (b) of FIG. 1 shows the information elements included in the UE context stored for each UE. Figure 8As shown in (b), the MME context stored for each UE includes one or more of IMSI, MSISDN, MM State, GUTI, ME Identity, UE Radio AccessCapability (UE radio access capability), UE Network Capability, MS Network Capability, AccessRestriction (access restriction), MME F-TEID, SGW F-TEID, eNB Address, MME UE S1AP ID, eNB UES1AP ID, NR node Address, NR node ID, WAG Address, and WAG ID.

[0123] Next, in Fig. 9 (c) shows the MME context for each PDU session or PDN connection stored for each PDU session or PDN connection. Fig. 9 As shown in (c), the MME context of each PDU session includes APN in Use, Assigned Session Type, IP Address(es), PGW F-TEID, SCEF ID, and Default bearer.

[0124] exist Fig. 9 (d) shows the MME context of each bearer stored for each bearer. Fig. 9 As shown in (d), the MME context stored for each bearer includes one or more of EPS Bearer ID, TI, TFT, SGW F-TEID, PGW F-TEID, MME F-TEID, eNB Address, NR node Address, WAG Address, eNB ID, NR node ID, and WAG ID. Here, Figure 8 and Fig. 9 The information elements included in the MME context shown may be stored in either the MM context or the EPS bearer context.

[0125] [1.2.4. Configuration of SGW]

[0126] exist Fig.10 The device structure of SGW_A35 is shown in FIG. Fig.10 As shown, SGW_A35 is composed of a network connection unit_D1020, a control unit_D1000, and a storage unit_D1040. The network connection unit_D1020 and the storage unit_D1040 are connected to the control unit_D1000 via a bus.

[0127] The control unit D1000 is a functional unit for controlling the SGW_A35. The control unit D1000 reads and executes various programs stored in the storage unit D1040 to implement various processes.

[0128] The network connection unit_D1020 is a functional unit for connecting the SGW_A35 with a base station and / or access point and / or MME_A40 and / or PGW_A30 and / or SGSN_A42 in the access network. In addition, the network connection unit_D1020 is a transceiver for the SGW_A35 to send and receive user data and / or control information from a base station and / or access point and / or MME_A40 and / or PGW_A30 and / or SGSN_A42 in the access network.

[0129] The storage unit_D1040 is a functional unit that stores programs, data, etc. required for each action of the SGW_A35. The storage unit_D1040 is composed of, for example, a semiconductor memory, an HDD, etc. The storage unit_D1040 can at least store identification information and / or control information and / or flags and / or parameters included in the control message sent and received in the communication process described later.

[0130] Storage unit_D1040 Fig.10 The EPS bearer context 1042 is shown as being stored. It should be noted that the EPS bearer context 1042 includes a context stored for each UE, a context stored for each PDU session, and a context stored for each bearer.

[0131] First, in Fig.11 (b) of FIG. 4 shows the information elements of the EPS bearer context stored for each UE. Fig.11 As shown in (b), the EPS bearer context stored for each UE includes: IMSI, ME Identity, MSISDN, MMEF-TEID, and SGW F-TEID.

[0132] Furthermore, the EPS bearer context includes the EPS bearer context for each PDU session stored for each PDU session. Fig.11 The EPS bearer context for each PDU session is shown in (c). Fig.11 As shown in (c), the EPS bearer context of each PDU session includes: APN in Use, Assigned Session Type, SGW F-TEID, PGW F-TEID, Default Bearer, IP Address(es).

[0133] Furthermore, the EPS bearer context includes the EPS bearer context of each bearer. Fig.11 (d) shows the EPS bearer context of each bearer. Fig.11 As shown in (d), the EPS bearer context of each bearer includes one or more of EPS Bearer ID, TFT, PGW F-TEID, SGW F-TEID, eNB F-TEID, MME Address, NR node Address, WAG Address, MME ID, NR node ID, and WAG ID.

[0134] [1.2.5. Configuration of PGW / UPGW / SMF / UPF]

[0135] exist Fig.10 The device configuration of PGW_A30, UPGW_A130, SMF_A230 and UPF_A235 is shown in FIG. Fig.10 As shown, PGW_A30, UPGW_A130, SMF_A230 and UPF_A235 are composed of a network connection unit_D1020, a control unit_D1000 and a storage unit_D1040. The network connection unit_D1020 and the storage unit_D1040 are connected to the control unit_D1000 via a bus. It should be noted that the functions of these units can be run on physical hardware or on logical hardware that is virtually constructed on general hardware.

[0136] The control unit D1000 is a functional unit for controlling the PGW_A30. The control unit D1000 reads and executes various programs stored in the storage unit D1040 to implement various processes.

[0137] The network connection unit_D1020 is a functional unit for connecting PGW_A30 with SGW_A35 and / or PCRF_A60 and / or ePDG_A65 and / or AAA_A55 and / or TWAG_A74 and / or PDN_A5. In addition, the network connection unit_D1020 is a transceiver for PGW_A30 to send and receive user data and / or control information from SGW_A35 and / or PCRF_A60 and / or ePDG_A65 and / or AAA_A55 and / or TWAG_A74 and / or PDN_A5.

[0138] Furthermore, the network connection unit_D1020 is a functional unit for connecting UPGW_A130 with PCRF_A60 and / or NR node_A122 and / or PDN_A5. Furthermore, the network connection unit_D1020 is a transceiver for PGW_A30 to send and receive user data and / or control information from SGW_A35 and / or PCRF_A60 and / or ePDG_A65 and / or AAA_A55 and / or TWAG_A74 and / or PDN_A5.

[0139] In addition, the network connection unit_D1020 is a functional unit for connecting SMF_A230 with AMF_A240 and / or UPF_A235 and / or HSS_A50 and / or PCRF_A60. In addition, the network connection unit_D1020 is a transceiver for SMF_A230 to send and receive control information with AMF_A240 and / or UPF_A235 and / or HSS_A50.

[0140] In addition, the network connection unit_D1020 is a functional unit for connecting UPF_A235 with NR node_A122 and / or SMF_A230 and / or PDN_A5 and / or DN_B105. In addition, the network connection unit_D1020 is a transceiver for UPF_A235 to send and receive user data and / or control information with NR node_A122 and / or SMF_A230 and / or PDN_A5 and / or DN_B105.

[0141] The storage unit_D1040 is a functional unit that stores programs, data, etc. required for each action of PGW_A30. The storage unit_D1040 is composed of, for example, a semiconductor memory, an HDD, etc. The storage unit_D1040 can at least store identification information and / or control information and / or flags and / or parameters included in the control message sent and received in the communication process described later.

[0142] Storage unit_D1040 Fig.10 The EPS bearer context 1042 is shown as being stored. It should be noted that, in the EPS bearer context 1042, the context stored per UE, the context stored per APN, the context stored per PDU session or PDN connection, and the context stored per bearer may also be stored separately. Moreover, the EPS bearer context may be a context stored in UPGW_A130 and / or SMF_A230 and / or UPF_A235.

[0143] exist Fig.12 (b) shows the information elements included in the EPS bearer context stored for each UE. Fig.12As shown in (b), the EPS bearer context stored for each UE includes IMSI, ME Identity, MSISDN, and RATtype.

[0144] Next, in Fig.12 (c) shows the EPS bearer context stored for each APN. Fig.12 As shown in (c), the EPS bearer context stored for each APN in the PGW storage unit includes APN in use. It should be noted that the EPS bearer context stored for each APN may also be stored for each Data Network Identifier.

[0145] In addition, Fig.12 (d) shows the EPS bearer context for each PDU session or PDN connection stored for each PDU session or PDN connection. Fig.12 As shown in (d), the EPS bearer context of each PDU session or PDN connection includes: Assigned Session Type, IP Address(es), SGW F-TEID, PGW F-TEID, and Default Bearer.

[0146] Further in Fig.12 (e) of FIG. 1 shows the EPS bearer context stored for each EPS bearer. Fig.12 As shown in (e), the EPS bearer context includes: EPS Bearer ID, TFT, SGW F-TEID, and PGW F-TEID.

[0147] [1.2.6. Composition of SCEF]

[0148] exist Fig.10 The device structure of SCEF_A46 is shown in FIG. Fig.10 As shown, SCEF_A46 is composed of a network connection unit_D1020, a control unit_D1000, and a storage unit_D1040. The network connection unit_D1020 and the storage unit_D1040 are connected to the control unit_D1000 via a bus.

[0149] The control unit_D1000 is a functional unit for controlling the SCEF_A46. The control unit_D1000 implements various processes by reading and executing various programs stored in the storage unit_D1040. The network connection unit_D1020 is a functional unit for connecting the SCEF_A46 with the core network_B190. In other words, the network connection unit_D1020 is a functional unit for connecting the SCEF_A46 with the MME_A40. Moreover, the network connection unit_D1020 is a transceiver for the SCEF_A46 to send and receive user data and / or control information from the MME_A40.

[0150] The storage unit_D1040 is a functional unit that stores programs, data, etc. required for each action of the SCEF_A46. The storage unit_D1040 is composed of, for example, a semiconductor memory, an HDD, etc. The storage unit_D1040 can at least store identification information and / or control information and / or flags and / or parameters included in the control message sent and received in the communication process described later.

[0151] Storage unit_D1040 Fig.10 The EPS bearer context 1042 is shown as being stored. The following describes the information elements stored in the storage unit_D1040. Fig.13 (b) of FIG. 4 shows the information elements included in the EPS bearer context. Fig.13 As shown in (b), the EPS bearer context includes: User Identity, APN in Use, EPS Bearer ID, and Serving NodeInformation.

[0152] [1.3. Description of the initial process and / or update process]

[0153] Next, before describing the detailed steps of the initial process and / or update process of the present embodiment, in order to avoid duplication of description, terminology unique to the present embodiment and main identification information used in each process are described in advance.

[0154] In this embodiment, the network is the access network and / or the core network_B190 and / or the PDN_A5. In addition, the network may also represent any device included in the access network and / or the core network_B190 and / or the PDN_A5. That is, the network executing the sending and receiving of messages and / or the process means that the devices in the network execute the sending and receiving of messages and / or the process.

[0155] The first DN of this embodiment is a common DN. It can be a DN that is not a MEC (Mobile Edge Computing) DN. Moreover, the first DN can be a DN that is not a local DN, or it can be a DN that uses a third-party service located in a place far away from the place where UE_A10 accesses. It should be noted that the first DN can be expressed as PDN_A5 or DN, and PDN_A5 can also be expressed as the first DN or DN.

[0156] The second timer of this embodiment is a back-off timer indicating prohibition of starting a registration process and / or sending a registration request message. Each device may be prohibited from starting a registration process and / or sending and receiving a registration request message during the execution of the second timer. It should be noted that the time for executing the second timer may be the time indicated by the value of the timer for sending and receiving a registration acceptance message and / or a registration rejection message, or may be a preconfigured time.

[0157] The first state of this embodiment refers to the state in which UE_A10 has not logged in to the network. In addition, the first state may also refer to a state that does not include location information and routing information that are valid for the UE context in AMF_A240. In the first state, UE_A10 and the devices in the core network may or may not have a UE context. It should be noted that the UE context may be a context for UE_A10 and / or the devices in the core network to generate and / or maintain a context. Moreover, the device in the core network may be AMF_A240 or SMF_A230. In addition, the first state may refer to a state in which UE_A10 can perform the initial registration process.

[0158] The second state of this embodiment refers to the state in which UE_A10 logs in to the network. In addition, the second state may also refer to the state in which UE_A10 can receive a service request for login from the network. Moreover, the second state may refer to the state in which UE_A10 can execute a process for updating mobility registration. Moreover, the second state may refer to the state in which the registration process can be started again after the UE has logged in to the network once. Moreover, the second state may refer to the state in which the context within UE_A10 and / or the core network has been established and / or generated, and may be the state in which the UE_A10 and / or the device within the core network maintains the context.

[0159] Here, starting the registration process again when UE_A10 has logged in to the network once can specifically mean that UE_A10 performs the registration process regularly, or performs the registration process due to the movement (mobility) of UE_A10 or for updating capability information (capability) or for renegotiating protocol parameters (protocol parameter).

[0160] The third state of this embodiment refers to after UE_A10 starts the initial registration process. Moreover, the third state may also be a state in which UE_A10 waits for a response from the network and / or AMF_A240. Moreover, the third state may also be a state indicating that the initial process has been started. In other words, the third state may be the state to which UE_A10 and / or a device within the core network transitions when starting the registration process in the first state, or it may be a state indicating that the initial registration has been started.

[0161] The fourth state of this embodiment refers to the state after UE_A10 restarts the registration process after logging into the network once. Moreover, the fourth state may also be a state in which UE_A10 waits for a response from the network and / or AMF_A240. Moreover, the fourth state may also be a state after indicating the start of a process other than the initial process. In other words, the fourth state may be the state to which UE_A10 and / or a device within the core network transitions when the registration process restarts in the second state, or it may be a state indicating the restart of registration.

[0162] The mobility restriction in this embodiment refers to information that limits the movement (mobility) of UE_A10 or limits access to services. The mobility restriction may include at least one of RAT restriction, forbidden area, and service area restriction. Alternatively, it may include all of this information.

[0163] Here, RAT restriction refers to information indicating one or more RATs (Radio Access Technology) to which UE_A10 cannot connect. It should be noted that in the RAT indicated by the RAT restriction, UE_A10 may be in a state where any communication with the network is prohibited, or in a state where communication other than specific communication is restricted. Here, specific communication may refer to emergency-related communication, or the sending and receiving of control information included in the initial registration process.

[0164] In addition, a prohibited area refers to information indicating a range in which UE_A10 cannot communicate with the network in a specific RAT. A prohibited area may be information indicating a range in which communications other than UE_A10 or specific communications are restricted in a specific RAT. Here, specific communications may refer to emergency-related communications, or the sending and receiving of control information included in the initial registration process, for example.

[0165] In addition, the service area restriction is information composed of an allowed area and a non-allowed area. It should be noted that the allowed area may be information indicating a range in which UE_A10 and the network can communicate in a specific RAT. Moreover, the non-allowed area may be information indicating a range in which a process for enabling communication of user data between UE_A10 and the network has been prohibited. Specifically, in the non-allowed area, UE_A10 may be prohibited from starting a service request process.

[0166] The registration area / cell of this embodiment is information indicating one or more tracking areas or cells assigned to UE_A10. The registration area / cell may be information assigned by AMF_A240. The registration area / cell may be information assigned in consideration of the mobility pattern and service area restriction of the UE. Moreover, the registration area / cell may be information indicating the cell to which UE_A10 is currently connected, or information indicating the tracking area to which UE_A10 currently belongs. Moreover, the registration area may be stored for each access type, for example, the registration area for 3GPP connection and the registration area for non-3GPP connection may be different information. Moreover, the registration area / cell may also be a tracking area.

[0167] The tracking area of ​​this embodiment is a single or multiple ranges managed by the core network that can be represented by the location information of UE_A10. The tracking area can be composed of multiple cells. Moreover, the tracking area can be the range of control messages such as broadcast paging, or the range in which UE_A10 can move without performing a switching process. Moreover, the tracking area can be a routing area or a location area, as long as it is the same area as these areas. Below, the tracking area can also be TA (Tracking Area).

[0168] The TA list of this embodiment is a list of one or more TAs assigned to UE_A10 by the network. It should be noted that UE_A10 can move without performing a tracking area update procedure during movement within one or more TAs included in the TA list. In other words, in UE_A10, the TA list can be an information group indicating an area in which UE_A10 can move without performing a tracking area update procedure.

[0169] The NSI (Network Slice Instance) of this embodiment refers to an entity that constitutes one or more network slices (Network Slice) within the core network_B190. In addition, the NSI of this embodiment can be composed of a virtual NF (Network Function) generated using an NST (Network Slice Template). Here, NST refers to a logical expression of one or more NFs (Network Functions) associated with a resource request for providing the requested communication service and capability.

[0170] 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 formed to divide the distributed user data according to services, etc. At least one NF may be formed in a network slice. The NF formed in a network slice may be a device shared with other network slices, or may not be a device shared with other network slices.

[0171] UE_A10 and / or devices within the network can be assigned to one or more network slices based on login information and / or APN such as NSSAI and / or S-NSSAI and / or UE usage type (UE usage type) and / or one or more network slice type IDs and / or one or more NS IDs.

[0172] The S-NSSAI of this embodiment is the abbreviation of Single Network Slice Selection Assistance information, which is information used to identify network slices. S-NSSAI can be composed of SST (Slice / Service type) and SD (Slice Differentiator). S-NSSAI can be composed of SST only or both SST and SD.

[0173] Here, SST refers to information indicating the actions of the network slice expected in terms of functions and services. In addition, SD can be information that supplements SST when selecting an NSI from multiple NSIs shown in SST.

[0174] The S-NSSAI may be information specific to each PLMN or may be standard information common among PLMNs. In addition, the network may store one or more S-NSSAIs in the login information of UE_A10 as default S-NSSAIs.

[0175] The NSSAI (Single Network Slice Selection Assistance information) of this embodiment is a collection of S-NSSAI. Each S-NSSAI included in the NSSAI is information for assisting the access network or core network to select NSI. UE_A10 can store the NSSAI allowed by the network for each PLMN. In addition, NSSAI can be information for selecting AMF_A240.

[0176] The forbidden S-NSSAI list of this embodiment refers to a forbidden list that stores S-NSSAIs that are prohibited from use by the network. The forbidden S-NSSAI list can be composed of one or more S-NSSAIs. Moreover, UE_A10 can manage the forbidden S-NSSAI list for each PLMN or for registration areas / cells. In other words, the forbidden S-NSSAI list can correspond to a PLMN or to a registration area / cell.

[0177] The forbidden NSSAI list of this embodiment refers to a forbidden list that stores NSSAIs that are prohibited from being used by the network. The forbidden NSSAI list can be composed of one or more NSSAIs. Moreover, UE_A10 can manage the forbidden NSSAI list for each PLMN or for each registration area / cell. In other words, the forbidden NSSAI list can correspond to a PLMN or to a registration area / cell.

[0178] The registration attempt count (registration attempt counter) of this embodiment refers to information indicating the number of times UE_A10 attempts the registration process. The registration attempt count may also be information indicating the number of times UE_A10 attempts the registration process and fails. It should be noted that the registration attempt count can be managed for each PLMN. Moreover, the registration attempt count may also be managed separately by the registration attempt count (update) (registration attempt counter(update)) and the registration attempt count (initial) (registration attempt counter(initial)), or may be managed as a common value. It should be noted that the registration attempt count can be managed by UE_A10.

[0179] The registration attempt count (initial) of this embodiment refers to information indicating the number of times UE_A10 attempts the initial registration process. The registration attempt count (initial) may also be information indicating the number of times UE_A10 attempts the initial registration process and fails. In other words, the registration attempt count (initial) may be information indicating the number of times UE_A10 in the first state attempts the registration process, or may be information indicating the number of times the registration process is attempted and fails.

[0180] The registration attempt count (update) of this embodiment refers to information indicating the number of times the registration process is attempted again when UE_A10 logs in to the network once. The registration attempt count (update) may also be information indicating the number of times UE_A10 attempts the registration process again and fails. In other words, the registration attempt count (update) may be information indicating the number of times UE_A10 in the second state attempts the registration process, or may be information indicating the number of times the registration process is attempted and fails.

[0181] exist Figure 2 (a) shows the configuration of Deployment Option 2 of this embodiment. Deployment Option 2 of this embodiment is a deployment option of NGS (NextGen System) as an independent configuration, and is a deployment option performed by Access Network _B using NR (New Rat)-based wireless access.

[0182] In other words, deployment option 2 may be a deployment option of NGS using access network_B190 composed of NR node_A122. Here, in the case of deployment option 2, the RAT used in access network_B190 may be NR.

[0183] It should be noted that NR (New Rat) can be used in 5G (5 thThe NR can be either NextGen RA or 5G RA (5th Generation Radio Access).

[0184] exist Figure 2 (b) shows the structure of Deployment Option 3 of this embodiment. Deployment Option 3 of this embodiment is a deployment option of EPS with a non-independent structure, and is a deployment option performed by using a dual-connected access network _A90 including E-UTRA as an anchor RAT and NR as a secondary RAT.

[0185] In other words, deployment option 3 may be a deployment option using EPS of access network_A90 including eNB_A45 as an anchor node and NRnode_A122 as a secondary node. Here, in the case of deployment option 3, the RAT used in access network_A90 may be E-UTRA.

[0186] exist Figure 2 (c) shows the structure of deployment option 4 of the present embodiment. Deployment option 4 of the present embodiment is a deployment option of a non-independent NGS, and is a deployment option performed by access network _B190 using dual connectivity including NR as an anchor RAT and E-UTRA as a secondary RAT.

[0187] In other words, deployment option 4 may be a deployment option of NGS using access network_B190 including NR node_A122 as an anchor node and eNB_A45 as a secondary node. Here, in the case of deployment option 4, the RAT used in access network_B190 may be E-UTRA and NR. Also, in the case of deployment option 4, E-UTRA may be Evolved E-UTRA, and eNB_A45 may be Evolved eNB.

[0188] exist Figure 2 (d) shows the configuration of Deployment Option 5 of this embodiment. Deployment Option 5 of this embodiment is a deployment option of NGS as an independent configuration, and is a deployment option performed by Access Network _B190 using E-UTRA-based wireless access.

[0189] In other words, deployment option 5 may be a deployment option of NGS using access network_B190 composed of eNB_A45. Here, in the case of deployment option 5, the RAT used in access network_B190 may be E-UTRA. Also, in the case of deployment option 5, E-UTRA may be Evolved E-UTRA, and eNB_A45 may be Evolved eNB.

[0190] exist Figure 2 (e) shows the structure of deployment option 7 of the present embodiment. Deployment option 7 of the present embodiment is a deployment option of NGS that is not independently structured, and is a deployment option performed by access network _B190 using dual connectivity including E-UTRA as the anchor RAT and NR as the secondary RAT.

[0191] In other words, deployment option 7 may be a deployment option of NGS using access network_B190 including eNB_A45 as an anchor node and NRnode_A122 as a secondary node. Here, in the case of deployment option 7, RAT used in access network_B190 may be E-UTRA and NR. Also, in the case of deployment option 7, E-UTRA may be Evolved E-UTRA, and eNB_A45 may be Evolved eNB.

[0192] The first behavior of this embodiment refers to the behavior of UE_A10 sending a registration request message that does not include the NSSAI sent in the previous registration process. Specifically, UE_A10 can send a registration request message including an NSSAI different from the NSSAI sent in the previous registration process, or can send a registration request message that does not include NSSAI, or can send a registration request message including an empty NSSAI. At this time, UE_A10 can send a registration request message after the expiration of the second timer and the pre-configured backoff timer, if these timers have already started.

[0193] The second behavior of this embodiment refers to the behavior that UE_A10 does not send the registration request message sent in the previous registration process to the same PLMN (Public Land Mobile Network). Specifically, UE_A10 can send a registration request message including the same NSSAI as the NSSAI sent in the previous registration process to different PLMNs, and can also send a registration request message including an NSSAI different from the NSSAI sent in the previous registration process to the same PLMN. Moreover, UE_A10 can also send a registration request message that does not include NSSAI or includes an empty NSSAI to the same PLMN. At this time, UE_A10 can send a registration request message after the expiration of the second timer and the pre-configured backoff timer, if these timers have already started.

[0194] The third behavior of this embodiment refers to the behavior that UE_A10 does not send the registration request message sent in the previous registration process in the same registration area / cell. Specifically, UE_A10 can send a registration request message including the same NSSAI as the NSSAI sent in the previous registration process to a different registration area / cell, or send a registration request message including a different NSSAI in the same registration area / cell. Moreover, UE_A10 can also send a registration request message that does not include NSSAI or includes an empty NSSAI in the same registration area / cell. It should be noted that in the case where mobility restrictions are stored, UE_A10 can further consider mobility restrictions to send a registration request message. At this time, UE_A10 can send a registration request message after the expiration of these timers when the second timer and the pre-configured backoff timer have been started.

[0195] The fourth behavior of this embodiment refers to the behavior that UE_A10 sends the registration request message sent in the previous registration process to the same PLMN and / or the same registration area / cell after a certain period of time. Specifically, UE_A10 may send a registration request message including the same NSSAI as the NSSAI sent in the previous registration process to the same PLMN and / or the same registration area / cell after a certain period of time. At this time, UE_A10 may send a registration request message after the expiration of the second timer and the pre-configured backoff timer when these timers have already started. It should be noted that after a certain period of time may refer to the time until the execution of the second timer expires. It should be noted that after a certain period of time is not limited to this.

[0196] The fifth behavior of this embodiment refers to the behavior of UE_A10 and / or the device in the core network transitioning to the first state. Specifically, it can be that UE_A10 and / or the device in the core network transitions from any of the second to fourth states to the first state. The UE_A10 and / or the device in the core network that has transitioned to the first state can delete the UE context immediately, or temporarily maintain it, or delete it after a certain period of time.

[0197] The sixth behavior of this embodiment refers to the behavior of UE_A10 and / or the device in the core network transitioning to the second state. Specifically, it can be that UE_A10 and / or the device in the core network transitions from any of the third and fourth states to the second state. The UE_A10 and / or the device in the core network that has transitioned to the second state can generate or update the UE context, or continue to maintain the generated or updated UE context.

[0198] For example, UE_A10 and / or a device within the core network that has transitioned from the third state to the second state can generate a UE context, and UE_A10 and / or a device within the core network that has transitioned from the fourth state to the second state can update the UE context.

[0199] The seventh behavior of this embodiment refers to the behavior of updating the prohibited NSSAI list or prohibited S-NSSAI list stored by UE_A10. Specifically, UE_A10 and / or the device in the core network can add the NSSAI sent by UE_A10 to the network or the S-NSSAI included in the NSSAI to the prohibited NSSAI list or prohibited S-NSSAI list.

[0200] The eighth behavior of this embodiment refers to the behavior of resetting the prohibited NSSAI list or prohibited S-NSSAI list stored by the device in UE_A10 and / or the core network. In addition, the eighth behavior can be the behavior of the device in UE_A10 and / or the core network deleting the maintained UE context. It should be noted that the timing of deleting the UE context by the device in UE_A10 and / or the core network can be immediate deletion after executing the eighth behavior, or it can be deletion after a certain period of time.

[0201] The ninth behavior of this embodiment refers to the behavior of UE_A10 and / or the device in the core network starting the second timer. It should be noted that the value of the timer used when UE_A10 and / or the device in the core network starts the second timer can be the value of the second timer that has been sent and received, or it can be the value of the preconfigured second timer.

[0202] The tenth behavior of this embodiment refers to the behavior of UE_A10 increasing or resetting the stored registration attempt count. Specifically, UE_A10 can update by increasing the registration attempt count, and can reset the registration attempt count when the registration attempt count reaches a certain value.

[0203] Here, UE_A10 can manage the registration attempt count (update) and the registration attempt count (initial) separately. Specifically, UE_A10 that has sent the initial registration request message can increment or reset the registration attempt count (initial). Alternatively, UE_A10 that has sent the registration request message again after UE_A10 has logged in to the network once can increment or reset the registration attempt count (update).

[0204] In other words, the UE_A10 in the third state may increment or reset the registration attempt count (initial). Alternatively, the UE_A10 in the fourth state may increment or reset the registration attempt count (update).

[0205] The eleventh behavior of this embodiment refers to the behavior of UE_A10 sending a deregistration request message to the network. UE_A10 can perform the fifth behavior by sending a deregistration request message. It should be noted that the deregistration request made by UE_A10 can be a message sent by UE_A10 in order to transition to the first state and / or UE_A10 in order to transition to a state where it is not logged in to the network.

[0206] The twelfth behavior of this embodiment refers to the behavior of UE_A10 updating the stored forbidden RAT list (forbidden RATlist). Specifically, when executing the twelfth behavior, UE_A10 can add the currently connected RAT to the forbidden RAT list. Moreover, the twelfth behavior can also be the behavior of UE_A10 disabling the capability information (RATcapability) related to the maintained RAT. Specifically, when executing the twelfth behavior, UE_A10 can disable the capability information (E-UTRA Capability) related to E-UTRA, and can also disable the capability (NRCapability) related to NR.

[0207] The 30th behavior of this embodiment refers to the behavior of UE_A10 and / or the device in the core network transitioning to the third state. Specifically, UE_A10 and / or the device in the core network in the first state can transition to the third state. UE_A10 that has transitioned to the third state can wait for a certain period of time for a response from the network. The certain period of time can be managed by a timer. It should be noted that if no response from the network is received after a certain period of time, UE_A10 can perform the first behavior.

[0208] The thirty-first behavior of this embodiment refers to the behavior of UE_A10 and / or the device in the core network transitioning to the fourth state. Specifically, UE_A10 and / or the device in the core network in the first state can transition to the fourth state. UE_A10 that has transitioned to the fourth state can wait for a response from the network for a certain period of time. The certain time can be managed by a timer. It should be noted that if no response from the network is received after a certain period of time, UE_A10 can perform the first behavior or the second behavior.

[0209] Next, the identification information of this embodiment is described. The third identification information of this embodiment is information indicating the NSSAI requested by UE_A10. The third information can be the NSSAI set by the HPLMN, or the NSSAI obtained from the AMF_A240 during the registration process, or the NSSAI allowed by the network. Moreover, the third identification information can be the NSSAI stored for each PLMN.

[0210] The fifth identification information of this embodiment is information indicating whether the network is allowed to allocate NSSAI other than the NSSAI requested by UE_A10. The fifth identification information may be information indicating whether the network is allowed to allocate NSSAI composed of S-NSSAI other than one or more S-NSSAIs constituting the NSSAI requested by UE_A10. Moreover, the fifth identification information may be information indicating whether the network is allowed to allocate NSSAI composed of a part of one or more S-NSSAIs constituting the NSSAI requested by UE_A10.

[0211] The sixth identification information of this embodiment is information indicating the registration type (Registration type). The registration type (Registration type) may be information indicating whether the registration process requested by UE_A10 is an initial process or a process other than the initial process. In more detail, the registration type may be information indicating whether the registration process requested by UE_A10 is an initial registration (Initial Registration) process, a periodic registration (Periodic Registration update: periodic registration update) process, or a registration (Mobility Registration update) process due to the movement of UE_A10, or a registration process that occurs for updating capability information (capability) and / or for renegotiating protocol parameters (protocol parameter). It should be noted that a registration process other than the initial registration may also be expressed as a registration update process. Conversely, the registration update process may also refer to a registration process other than the initial registration process.

[0212] It should be noted that, when the sixth identification information indicates an initial registration process and / or UE_A10 in the first state has sent a registration request message and / or a device in the core network in the first state has received a registration request message, UE_A10 and / or a device in the core network can perform the 30th behavior based on the sending and receiving of the registration request message. On the other hand, when the sixth identification information indicates a registration process other than the initial registration process and / or UE_A10 in the second state has sent a registration request message and / or a device in the core network in the second state has received a registration request message, UE_A10 can perform the 31st behavior based on the sending and receiving of the registration request message.

[0213] The thirteenth identification information of this embodiment is the NSSAI allowed by the network for UE_A10. The thirteenth identification information may be the same information as the third identification information, or may be different information. In the case where the fifth identification information is included in the registration request message, the thirteenth identification information may be the same as the third identification information. In more detail, in the case where the network is allowed to allocate NSSAI other than the NSSAI requested by UE_A10 based on the fifth identification information included in the registration request message, the thirteenth identification information may be an NSSAI different from the third identification information. On the other hand, in the case where the network is not allowed to allocate NSSAI other than the NSSAI requested by UE_A10 based on the fifth identification information included in the registration request message, the thirteenth identification information may be an NSSAI different from the third identification information.

[0214] It should be noted that UE_A10 and / or the device within the core network can perform the sixth behavior and / or the tenth behavior based on the sending and receiving of the thirteenth identification information and / or the registration acceptance message, and can also reset the registration attempt count, and can also perform the behaviors of both parties. In addition, when executing the tenth behavior, when UE_A10 is in the third state, UE_A10 can reset the registration attempt count (initial) instead of the registration attempt count. Alternatively, when UE_A10 is in the fourth state, the registration attempt count (update) can be reset instead of the registration attempt count.

[0215] The fourteenth identification information of this embodiment is the mobility restriction assigned to the UE by the core network. The fourteenth identification information is information considered when UE_A10 performs communication with the network.

[0216] UE_A10 and / or the device in the core network can perform the sixth behavior and / or the tenth behavior based on the reception of the fourteenth identification information and / or the registration acceptance message, and can also reset the registration attempt count, and can also perform the behaviors of both parties. In addition, when UE_A10 is in the third state, the registration attempt count (initial) can be reset to replace the registration attempt count. Alternatively, when UE_A10 is in the fourth state, the registration attempt count (update) can be reset to replace the registration attempt count.

[0217] Moreover, UE_A10 may store the received fourteenth identification information as the mobility restriction based on the reception of the fourteenth identification information. In addition, in the case where UE_A10 has already stored the mobility restriction, UE_A10 may update the mobility restriction to the information indicated by the received fourteenth information based on the reception of the fourteenth identification information. It should be noted that the mobility restriction may be stored in the UE context, in which case the mobility restriction may be stored or updated as the sixth behavior.

[0218] The fifteenth identification information of this embodiment is a reason value (cause) indicating the reason why some requests made by UE_A10 are not allowed and / or some requests made by UE_A10 are rejected. Specifically, the fifteenth identification information may be information indicating that an NSSAI different from the NSSAI requested by the UE is allocated to the UE and / or indicating the reason.

[0219] The fifteenth identification information may be transmitted including the meaning of the sixteenth to seventeenth identification information. UE_A10 may perform one or more actions among the actions performed with the reception of the sixteenth to seventeenth identification information based on the reception of the fifteenth identification information.

[0220] The sixteenth identification information of this embodiment is information indicating that an NSSAI different from the NSSAI requested by UE_A10 is allocated to the UE. The sixteenth identification information may also be information for determining whether UE_A10 performs the registration process again.

[0221] UE_A10 may determine to start the registration process again based on the reception of the sixteenth identification information and send a registration request message. At this time, if the second timer and the preconfigured second timer have already started, the registration request message may be sent after these timers expire. Alternatively, if a regular registration process is scheduled, UE_A10 may send a registration request message as a regular registration request message after the timer for managing the regular registration process expires.

[0222] UE_A10 may also perform one or more of the seventh behavior, the ninth behavior, the tenth behavior, and the eleventh behavior based on the reception of the sixteenth identification information. It should be noted that UE_A10 and / or the device in the core network may use the eighteenth identification information that has been sent and received, or may use a preconfigured value as the value of the second timer started in the ninth behavior.

[0223] The seventeenth identification information of this embodiment is information indicating whether retransmission of a registration request message including the same NSSAI as the third identification information sent or received in the registration request message is allowed. The seventeenth identification information may be information (allowed) indicating that retransmission of a registration request message including the same NSSAI as the third identification information sent or received in the registration request message is allowed, or may be information (not allowed) indicating that retransmission is not allowed. The network may determine the seventeenth identification information according to a network policy.

[0224] UE_A10 may determine to start the registration process again based on the reception of the seventeenth identification information and send a registration request message. At this time, if the second timer and the preconfigured second timer have already started, the registration request message may be sent after these timers expire. Alternatively, if a regular registration process is scheduled, UE_A10 may send a registration request message as a regular registration request message after the timer for managing the regular registration process expires.

[0225] When UE_A10 sends a registration request message to start the registration process, if the seventeenth identification information is allowed, the NSSAI sent previously can be included to send a registration request message to the same PLMN. In addition, at this time, the registration area / cell can also be the same as the previous process.

[0226] Alternatively, when UE_A10 sends a registration request message in order to start the registration process, if the seventeenth identification information is not allowed, the registration request message can be sent through any of the first to fourth behaviors.

[0227] UE_A10 may also perform one or more of the seventh behavior, the ninth behavior, the tenth behavior, the eleventh behavior, and the twelfth behavior based on the reception of the seventeenth identification information. It should be noted that UE_A10 and / or the device in the core network may use the eighteenth identification information that has been sent and received, or may use a preconfigured value as the value of the second timer started in the ninth behavior.

[0228] The eighteenth identification information of this embodiment is information indicating the time until UE_A10 can start the next registration process. The eighteenth information may be the value of the second timer. UE_A10 may perform the ninth behavior and / or the tenth behavior based on the reception of the eighteenth identification information. Moreover, the device within the core network may perform the ninth behavior based on the sending of the eighteenth identification information. It should be noted that UE_A10 and / or the device within the core network may use the eighteenth identification information that has been sent and received, or may use a preconfigured value as the value of the second timer started in the ninth behavior.

[0229] The twenty-first identification information of this embodiment is information indicating a reason value (cause) indicating that the request is rejected. The twenty-first identification information may also be information indicating that part of the request is rejected.

[0230] The twenty-first information may be sent including the meaning indicated by one or more identification information among the twenty-second to twenty-eighth identification information. UE_A10 may perform one or more of the behaviors performed with the reception of the twenty-second to twenty-eighth identification information based on the reception of the twenty-first identification information.

[0231] The twenty-second identification information of this embodiment is information indicating that the requested NSSAI is not allowed. The twenty-second identification information may also be information indicating that the use of the requested NSSAI is prohibited. Moreover, the twenty-second information may be information indicating that the requested NSSAI cannot be found from a list managed by the network. The twenty-second identification information may be information indicating that the service provided by the requested NSSAI is not allowed to be used. Here, the requested NSSAI may refer to the NSSAI indicated by the third identification information. It should be noted that the twenty-second identification information may also be sent including the meaning of the twenty-seventh identification information.

[0232] UE_A10 can perform one or more of the first behavior, the fifth behavior, the seventh behavior, the eighth behavior, the ninth behavior, and the tenth behavior based on the reception of the twenty-second identification information. Moreover, the device in the core network can perform one or more of the fifth behavior, the eighth behavior, and the ninth behavior based on the sending of the twenty-second identification information. It should be noted that UE_A10 and / or the device in the core network can use the twenty-ninth identification information that has been sent and received, and can also use a preconfigured value as the value of the second timer started in the ninth behavior.

[0233] The twenty-third identification information of this embodiment indicates that the requested NSSAI is not allowed in the PLMN to which UE_A10 is connected. The twenty-third identification information may also be information indicating that the use of the requested NSSAI is prohibited in the PLMN to which UE_A10 is connected. Moreover, the twenty-third information may be information indicating that the requested NSSAI cannot be found from a list of each PLMN managed by the network. Moreover, the twenty-third identification information may be information indicating that the service provided by the requested NSSAI is not allowed in the PLMN to which UE_A10 is connected.

[0234] UE_A10 can perform one or more of the second behavior, the fifth behavior, the seventh behavior, the eighth behavior, the ninth behavior, and the tenth behavior based on the reception of the twenty-third identification information. Moreover, the device within the core network can perform one or more of the fifth behavior, the eighth behavior, and the ninth behavior based on the sending of the twenty-third identification information. It should be noted that UE_A10 and / or the device within the core network can use the received and sent twenty-ninth identification information, or can use a preconfigured value as the value of the second timer started in the ninth behavior. Moreover, when the prohibited S-NSSAI list or the prohibited NSSAI list is managed for each PLMN, UE_A10 can perform the seventh behavior.

[0235] The twenty-fourth identification information of this embodiment is information indicating that the requested NSSAI is not allowed in the registration area / cell to which UE_A10 is connected. The twenty-fourth identification information may also be information indicating that the use of the requested NSSAI is prohibited in the registration area / cell to which UE_A10 is connected. Moreover, the twenty-fourth information may be information indicating that the requested NSSAI cannot be found from a list of each registration area / cell managed by the network. Moreover, the twenty-fourth identification information may be information indicating that the service provided by the requested NSSAI is not allowed in the registration area / cell to which UE_A10 is connected.

[0236] UE_A10 can perform one or more of the third behavior, the fifth behavior, the seventh behavior, the eighth behavior, the ninth behavior, and the tenth behavior based on the reception of the twenty-fourth identification information. Moreover, the device within the core network can perform one or more of the fifth behavior, the eighth behavior, and the ninth behavior based on the sending of the twenty-fourth identification information. It should be noted that UE_A10 and / or the device within the core network can use the received and sent twenty-ninth identification information, or can use a preconfigured value as the value of the second timer started in the ninth behavior. Moreover, when the prohibited S-NSSAI list or the prohibited NSSAI list is managed according to each registration area / cell, UE_A10 can perform the seventh behavior.

[0237] The twenty-fifth identification information of this embodiment is information indicating that the requested NSSAI is temporarily not allowed. The twenty-fifth identification information may also be information indicating that the use of the requested NSSAI is temporarily prohibited. Moreover, the twenty-fifth identification information may be information indicating that the service provided by the requested NSSAI is temporarily not allowed. In the case where the twenty-fifth identification information is included in the registration rejection message, the twenty-ninth identification information may also be included in the registration rejection message.

[0238] UE_A10 can perform one or more of the first behavior, the fourth behavior, the fifth behavior, the sixth behavior, the eighth behavior, the ninth behavior, the tenth behavior, and the eleventh behavior based on the reception of the twenty-fifth identification information. Moreover, the device in the core network can perform one or more of the fifth behavior, the sixth behavior, the eighth behavior, and the ninth behavior based on the sending of the twenty-fifth identification information. It should be noted that UE_A10 and / or the device in the core network can use the twenty-ninth identification information that has been sent and received, and can also use a preconfigured value as the value of the second timer started in the ninth behavior.

[0239] Specifically, when UE_A10 and / or the device within the core network is in the third state, UE_A10 and / or the device within the core network can perform the fifth behavior based on the reception and transmission of the twenty-fifth identification information. On the other hand, when UE_A10 and / or the device within the core network is in the fourth state, UE_A10 and / or the device within the core network can perform the sixth behavior based on the reception and transmission of the twenty-fifth identification information. Moreover, when UE_A10 and / or the device within the core network has performed the sixth behavior, UE_A10 can determine to perform the eleventh behavior based on the reception of the twenty-fifth identification information. UE_A10 can determine to perform the eleventh behavior based on the UE policy.

[0240] The twenty-sixth identification information of this embodiment may be congestion information (Congestion) indicating network congestion.

[0241] UE_A10 can perform one or more of the first behavior, the fourth behavior, the fifth behavior, the sixth behavior, the eighth behavior, the ninth behavior, the tenth behavior, and the eleventh behavior based on the reception of the twenty-sixth identification information. Moreover, the device in the core network can perform one or more of the fifth behavior, the sixth behavior, the eighth behavior, and the ninth behavior based on the sending of the twenty-sixth identification information. It should be noted that UE_A10 and / or the device in the core network can use the twenty-ninth identification information that has been sent and received, and can also use a preconfigured value as the value of the second timer started in the ninth behavior.

[0242] When UE_A10 and / or the device within the core network is in the third state, UE_A10 and / or the device within the core network can perform the fifth behavior based on the sending and receiving of the twenty-sixth identification information. On the other hand, when UE_A10 and / or the device within the core network is in the fourth state, UE_A10 and / or the device within the core network can perform the sixth behavior based on the sending and receiving of the twenty-sixth identification information. Moreover, when UE_A10 and / or the device within the core network has performed the sixth behavior, UE_A10 can determine to perform the eleventh behavior based on the reception of the twenty-sixth identification information. UE_A10 can determine to perform the eleventh behavior based on the UE policy. Moreover, UE_A10 can perform the fifth behavior based on the eleventh behavior, and can also transition to a state of waiting for a response from the network based on the eleventh behavior.

[0243] The twenty-seventh identification information of this embodiment is information indicating a non-recognition request. The twenty-seventh information may be information indicating that the requested NSSAI or DNN, etc., is not recognized.

[0244] UE_A10 can perform one or more of the first behavior, the second behavior, the third behavior, the fifth behavior, the seventh behavior, the ninth behavior, and the tenth behavior based on the reception of the twenty-seventh identification information. Moreover, the device in the core network can perform one or more of the fifth behavior, the eighth behavior, and the ninth behavior based on the sending of the twenty-seventh identification information. It should be noted that UE_A10 and / or the device in the core network can use the twenty-ninth identification information that has been sent and received, and can also use a preconfigured value as the value of the second timer started in the ninth behavior.

[0245] The twenty-eighth identification information of this embodiment is information indicating that the request is rejected based on mobility restriction. The twenty-eighth identification information may also be information indicating that the request is rejected based on RAT restriction.

[0246] Furthermore, the twenty-eighth identification information may also be information indicating that control messages of UE_A10 are prohibited from being sent and received in the RAT to which the current UE_A10 is connected. Furthermore, the twenty-eighth identification information may also be information indicating that control messages of UE_A10 and user data are prohibited from being sent and received in the RAT to which the current UE_A10 is connected.

[0247] In other words, the twenty-eighth identification information may be information indicating that sending and receiving C-Plane and / or U-Plane messages of UE_A10 and / or core network_A10 is prohibited in the RAT to which the current UE_A10 is connected, or it may indicate that the RAT to which the current UE_A10 is connected is a RAT in which sending and receiving C-Plane and / or U-Plane messages is prohibited.

[0248] Moreover, the twenty-eighth identification information may be information indicating the type of deployment option of the system to which the current UE_A10 is connected. Moreover, the twenty-eighth identification information may also be information indicating that, due to the type of deployment option, the sending and receiving of C-Plane and / or U-Plane messages of the UE_A10 and / or the core network_A10 is prohibited in the RAT to which the current UE_A10 is connected. Moreover, the twenty-eighth identification information may also indicate that the RAT to which the current UE_A10 is connected does not conform to the type of deployment option of the system.

[0249] Here, the types of deployment options may include deployment option 2, deployment option 3, deployment option 4, deployment option 5, and deployment option 7. It should be noted that the types of deployment options are not limited to these.

[0250] UE_A10 can perform one or more of the fifth behavior, the eighth behavior, the ninth behavior, the tenth behavior, and the twelfth behavior based on the reception of the twenty-eighth identification information. Moreover, the device in the core network can perform one or more of the fifth behavior, the eighth behavior, and the ninth behavior based on the sending of the twenty-eighth identification information. It should be noted that UE_A10 and / or the device in the core network can use the twenty-ninth identification information that has been sent and received, and can also use a preconfigured value as the value of the second timer started in the ninth behavior.

[0251] The twenty-ninth identification information of this embodiment may be the same as the eighteenth identification information. UE_A10 may perform the ninth behavior and / or the tenth behavior based on the reception of the twenty-ninth identification information. Moreover, the device within the core network may perform the ninth behavior based on the sending of the twenty-ninth identification information. It should be noted that UE_A10 and / or the device within the core network may use the received and sent twenty-ninth identification information, or may use a preconfigured value as the value of the second timer started in the ninth behavior.

[0252] Next, use Fig.14The initial process and / or update process of the present embodiment are described. In the present embodiment, each device can transition to any state of the first or second state by executing the initial process and / or update process. Moreover, when each device has been transformed into the second state, UE_A10 can establish a session via the core network_B190. Hereinafter, this process refers to the initial process and / or update process, and each process includes a registration process and a PDU session establishment process. Here, the registration process may also include an initial registration process (S1400) and / or a registration update process (S1408). It should be noted that the initial registration process may also be expressed as an initial registration process. Similarly, the registration update process may also be expressed as a re-registration process. In other words, when each device is in the first state, the initial registration process may be a registration process started by UE_A10. Moreover, when each device is in the second state, it may be a registration process started by UE_A10, and the registration update process may also be a registration process other than the initial registration process. The details of each process are described later.

[0253] In this process, each device in the first state (S1412) first executes the initial registration process (S1400) and transitions to a state in which UE_A10 has logged in to the network, i.e., the second state, or a state in which UE_A10 has not logged in to the network, i.e., the first state. Next, each device that has transitioned to the second state executes the PDU session establishment process (S1402) as a process for establishing a PDU session, and transitions to either the first or second state (S1404). Next, each device in the second state implements the registration update process, and transitions to either the first or second state based on the completion of the registration update process. It should be noted that each device can exchange various capability information and / or various request information of each device during the registration process and / or the PDU session establishment process, and can also transition to the third or fourth state based on the start of the registration process.

[0254] It should be noted that, each device may not implement the exchange of various information and / or negotiation of various requests during the PDU session establishment process, if the exchange of various information and / or negotiation of various requests have been implemented during the registration process. Conversely, each device may implement the exchange of various information and / or negotiation of various requests during the PDU session establishment process, if the exchange of various information and / or negotiation of various requests have not been implemented during the registration process. However, it is not limited to this, and each device may implement the exchange of various information and / or negotiation of various requests during the PDU session establishment process, if the exchange of various information and / or negotiation of various requests have been implemented during the registration process.

[0255] In addition, each device may perform the PDU session establishment process during the registration process, or may perform the PDU session establishment process after the registration process is completed. In the case where the PDU session establishment process is performed during the registration process, the PDU session establishment request message may be sent and received in the registration request message, the PDU session establishment acceptance message may be sent and received in the registration acceptance message, the PDU session establishment completion message may be sent and received in the registration completion message, and the PDU session establishment rejection message may be sent and received in the registration rejection message. Moreover, in the case where the PDU session establishment process is performed during the registration process, each device may establish a PDU session based on the completion of the registration process, or may transition to either the first state or the second state.

[0256] Each device completes this process through the above process. It should be noted that each device involved in this process can send and receive one or more identification information included in each control message by sending and receiving each control message described in this process, and store the sent and received identification information as a context. Moreover, each device can transition to either the first state or the second state based on the completion of each process.

[0257] [1.3.1. Overview of the registration process]

[0258] First, an overview of the registration process is described. The registration process is a process led by UE_A10 to connect to the network (access network and / or core network_B190 and / or PDN_A5). In addition, this process may include an initial registration (InitialRegistration) process and / or a registration update (Registration update) process. Moreover, the registration update process may include periodic registration updates (Periodic Registration update) and / or registration updates based on the mobility of UE_A10 (Mobility Registration update), registration updates for updating various capability information or for renegotiating protocol-related parameters (protocol parameter).

[0259] If UE_A10 is not connected to the network, the initial registration process can be performed at any time, such as when the terminal power is turned on. In other words, if UE_A10 is not logged in to the network (RM-DEREGISTERED), that is, the first state, this process can be started at any time. In addition, each device can transition to the third state based on the start of the initial registration process, and can also transition to the first or second state based on the completion of the initial registration process.

[0260] Moreover, when UE_A10 is connected to the network, in other words, logged in to the network (RM-REGISTERED), that is, in the second state, the registration update process can be a process for updating the location login information of UE_A10 in the network and / or for UE_A10 to periodically notify the network of the status of UE_A10 and / or for updating capability information related to UE_A10 in the network and / or specific parameters related to the protocol.

[0261] In addition, UE_A10 can start this process with mobility across TAs while being connected to the network. In other words, UE_A10 can start this process when entering a TA that is different from the TA shown in the maintained TA list. Moreover, UE_A10 can start this process when the executed timer expires. Moreover, UE_A10 can start this process when the context of each device needs to be updated because the PDU session and / or EPS bearer is cut off or disabled. Moreover, UE_A10 can start this process when the capability information and / or preference selection related to the PDU session establishment of UE_A10 changes. Moreover, UE_A10 can start this process periodically. It should be noted that UE_A10 is not limited to these, and as long as it is in the second state, the registration update process can be performed at any timing. In addition, each device can transition to the fourth state based on the start of the registration update process, and can also transition to the first or second state based on the completion of the registration update process.

[0262] Moreover, this process may also be started and / or performed in a 3GPP access network and / or a non-3GPP access network.

[0263] [1.3.1.1. Registration process example]

[0264] use Fig.15 An example of the steps of executing the registration process is described. Hereinafter, this process refers to the registration process. In addition, this process may also include an initial registration process and / or a registration update process, which may also be the same as this process. In other words, the initial registration process and / or the registration update process may be executed as the registration process, and the initial registration process and / or the registration update process may also be expressed as the registration process.

[0265] The following describes each step of this process. First, UE_A10 sends a registration request message (S1500)(S1502)(S1504) to AMF_A240 via NR node_A122 to start the registration process. UE_A10 can include an SM (Session Management) message in the registration request message and send it, or it can include an SM message to request the implementation of a PDU session establishment process and other processes for implementing session management during the registration process.

[0266] In addition, UE_A10 and / or each device can transition to the third state based on the sending of a request message during the initial registration process, and can also transition to the fourth state based on the sending of a request message during the registration update process.

[0267] Specifically, UE_A10 sends an RRC message including a registration request message to NR node_A122 (S1500). NR node_A122, which has received the RRC message including the registration request message, selects AMF_A240 as the NF or shared CP function of the routing destination of the registration request message (S1502), and sends the registration request message to the selected AMF_A240 (S1504). Here, NR node_A122 can select the AMF_A240 of the routing destination based on the information included in the RRC message. In addition, the registration request message can be a NAS (Non-Access-Stratum) message sent and received on the N1 interface. Moreover, the RRC message can be a control message sent and received between UE_A10 and NR node_A122.

[0268] Here, UE_A10 may include at least one or more of the third, fifth, and sixth identification information in the registration request message and / or the RRC message, and the request of UE_A10 may be indicated by including these identification information.

[0269] Moreover, UE_A10 can indicate the NSSAI requested by UE_A10 by sending the third identification information. That is, UE_A10 can also indicate that the network is allowed to select or allocate NSSAI regardless of the request of UE_A10 by not sending the third identification information. The NSSAI allocated to UE_A10 by the network can be the default NSSAI.

[0270] Moreover, UE_A10 can indicate whether UE_A10 allows NSSAI other than the NSSAI requested in the third identification information by sending the fifth identification information, and can also indicate whether to allow allocation of different NSSAI including S-NSSAI constituting the NSSAI requested in the third identification information. UE_A10 can send the fifth identification information when the third identification information has been sent.

[0271] Moreover, UE_A10 can indicate the type of registration process to be performed by sending the sixth identification information. For example, UE_A10 can also indicate the execution of the initial registration by sending the sixth identification information, and can also indicate the execution of the registration update process. In addition, UE_A10 can determine and indicate the execution of the initial registration process when UE_A10 and / or each device is in the first state by sending the sixth identification information, and can also determine and indicate the execution of the registration update process when UE_A10 and / or each device is in the second state.

[0272] It should be noted that UE_A10 can determine whether to add the third and / or fifth and / or sixth identification information to the registration request message based on the capability information of UE_A10 and / or UE policy and / or UE_A10's priority selection. It should be noted that it is not limited to UE_A10 to determine whether to add the third and / or fifth and / or sixth identification information to the registration request message.

[0273] In addition, UE_A10 may include these identification information in a control message different from the registration request message and send it. For example, UE_A10 may include these identification information in an ESM information response message (S1506) which is a response message to an ESM (EPS Session Management) information request message and send it.

[0274] AMF_A240 receives a registration request message and / or a control message different from the registration request message, and performs a first condition determination. The first condition determination is used to determine whether the network accepts the request of UE_A10. AMF_A240 starts process (A) in this process when the first condition determination is true, and starts process (B) in this process when the first condition determination is false.

[0275] The following describes each step of the (A) process in this process. AMF_A240 performs the fourth condition determination and starts the (A) process in this process. The fourth condition determination is used to determine whether AMF_A240 implements the sending and receiving of SM messages between it and SMF_A230. When the fourth condition determination is true, AMF_A240 performs the selection of SMF_A230 and the sending and receiving of SM messages between it and the selected SMF_A230, and omits (S1508) when the fourth condition determination is false. Moreover, AMF_A240 sends a registration accept message (S1510) to UE_A10 via NR node_A122 based on the reception of the registration request message and / or the completion of the sending and receiving of SM messages between it and SMF_A230. Here, when this process is executed as a registration update process, the registration accept message may also be a registration update accept message. It should be noted that AMF_A240 may not continue with process (A) in this process but start process (B) in this process when receiving an SM message indicating rejection. Here, the registration acceptance message may be sent and received in a control message of the N2 interface and an RRC message. Moreover, the registration acceptance message may be a NAS message sent and received on the N1 interface. In addition, the registration acceptance message may be a response message to the registration request message.

[0276] Moreover, UE_A10 may determine the state to be transformed after the completion of this process based on the identification information included in the registration acceptance message, and may also determine the behavior after the completion of this process. Moreover, UE_A10 may also perform the sixth and / or tenth behavior based on the reception of the registration acceptance message and / or one or more identification information included in the registration acceptance message.

[0277] Moreover, when the fourth condition is judged to be true, AMF_A240 can include SM messages such as PDU session establishment acceptance message in the registration acceptance message and send it, and can indicate the acceptance of the process for implementing session management by including the SM message.

[0278] Here, AMF_A240 may include at least one of the thirteenth to eighteenth identification information in the registration acceptance message, or may indicate that the request of UE_A10 has been accepted by including these identification information.

[0279] Moreover, AMF_A240 indicates the NSSAI allowed and / or allocated to UE_A10 by the network by sending the thirteenth identification information. Moreover, AMF_A240 can also indicate that the network supports and / or allows the connection to NSSAI requested by UE_A10 by sending the thirteenth identification information.

[0280] Moreover, AMF_A240 may also indicate the mobility restriction assigned by the network to UE_A10 by sending the fourteenth identification information. Moreover, AMF_A240 may also indicate the type of service area restriction assigned by the network to UE_A10 by sending the fourteenth identification information. For example, AMF_A240 may indicate whether the registration area to which UE_A10 is currently connected is an allowed area (Allowed area) or a non-allowed area (Non-allowed area) by sending the fourteenth identification information, and may also indicate UE_A10 to perform service connection restrictions based on the fourteenth identification information, and may also indicate the storage or update of mobility restrictions, and may also indicate the execution of the twelfth behavior.

[0281] Moreover, AMF_A240 may also indicate the reason for rejecting or not allowing part of the request of UE_A10 by sending the fifteenth identification information. For example, AMF_A240 may indicate that an NSSAI different from the NSSAI requested by UE_A10 is allocated to UE_A10 by sending the fifteenth identification information, and may also indicate the reason.

[0282] Moreover, AMF_A240 may also indicate that the NSSAI requested by UE_A10 is not allowed, and an NSSAI different from the NSSAI requested by UE_A10 is allocated to UE_A10 by sending the sixteenth identification information. Moreover, AMF_A240 may also indicate whether to allow retransmission of the registration request message including the NSSAI requested by UE_A10 by sending the seventeenth identification information. For example, AMF_A240 may also indicate that retransmission of the registration request message including the NSSAI requested by UE_A10 is allowed, or may indicate that retransmission of the registration request message including the NSSAI requested by UE_A10 is not allowed, by sending the seventeenth identification information.

[0283] Moreover, AMF_A240 may also indicate the timer value as the time until UE_A10 can start the next registration process by sending the eighteenth identification information, and may also instruct UE_A10 to perform the ninth behavior. Moreover, AMF_A240 may also indicate that the NSSAI requested by UE_A10 is not allowed by sending the thirteenth identification information and / or the fifteenth identification information and / or the sixteenth identification information and / or the seventeenth identification information and / or the eighteenth identification information, and may also indicate that the NSSAI shown in the thirteenth identification information is different from the NSSAI requested by UE_A10. In addition, in the case of including information indicating that the seventeenth identification information is not allowed, UE_A10 may instruct the execution of the first and / or eleventh behavior. In addition, in the case of including information indicating that the seventeenth identification information is allowed, UE_A10 may instruct the execution of the fourth behavior.

[0284] It should be noted that AMF_A240 can determine which identification information from the thirteenth to eighteenth identification information to add to the registration acceptance message based on the received identification information and / or network capability information and / or operator policy and / or network status. It should be noted that it is not limited to AMF_A240 to determine which identification information to add to the registration acceptance message.

[0285] UE_A10 receives the registration acceptance message, and then sends a registration complete message to AMF_A240 (S1512). It should be noted that, when UE_A10 receives an SM message such as a PDU session establishment acceptance message, it can include an SM message such as a PDU session establishment completion message in the registration completion message for sending, and can also indicate that the process for implementing session management is completed by including an SM message. Here, the registration completion message may be a NAS message sent and received on the N1 interface. In addition, the registration completion message may be a response message to the registration acceptance message. Moreover, the registration completion message may be included in the RRC message and the control message of the N2 interface for sending and receiving.

[0286] AMF_A240 receives the registration completion message. Each device completes the process (A) in this process based on the transmission and reception of the registration acceptance message and / or the registration completion message.

[0287] Moreover, UE_A10 and / or each device can transition to the second state based on the completion of process (A) in this process.

[0288] Next, each step of the process (B) in this process is explained. AMF_A240 sends a registration reject message (S1514) to UE_A10 via NR node_A122 to start the process (B) in this process. Here, when this process is executed as a registration update process, the registration reject message may also be a registration update reject message. Moreover, UE_A10 receives the registration reject message and recognizes that the request of UE_A10 is rejected. Each device completes the process (B) in this process based on the sending and receiving of the registration reject message.

[0289] Moreover, UE_A10 and / or each device can transition to the first or second state based on the completion of process (B) in this process. Moreover, UE_A10 can determine the state to which the process is transitioned after completion based on the identification information included in the registration rejection message, and can also determine the behavior after completion of the process. Moreover, UE_A10 can also perform the sixth and / or tenth behavior based on the registration rejection message and / or the reception of one or more identification information included in the registration rejection message. Moreover, in the case that UE_A10 receives a registration rejection message in the third state, UE_A10 receiving one or more identification information included in the registration rejection message can perform the fifth behavior.

[0290] It should be noted that, when the fourth condition is judged to be true, AMF_A240 may include a SM message indicating rejection, such as a PDU session establishment rejection message, in the registration rejection message for sending, or may indicate that the process for implementing session management is rejected by including an SM message indicating rejection. In this case, UE_A10 may further receive a SM message indicating rejection, such as a PDU session establishment rejection message, and authenticate that the process for implementing session management is rejected.

[0291] Moreover, the registration rejection message may be a NAS message sent and received on the N1 interface. In addition, the registration rejection message may be a response message to the registration request message, but is not limited thereto, and may also be a message rejecting the request of UE_A10. Moreover, the registration rejection message may be sent and received in a control message and an RRC message of the N2 interface.

[0292] In addition, AMF_A240 may include at least one of the twenty-first to twenty-ninth identification information in the registration rejection message, and may indicate that the request of UE_A10 is rejected by including these identification information.

[0293] Moreover, AMF_A240 can indicate the reason for rejecting this process by sending the twenty-first identification information, and can also indicate the rejection of part of the request of UE_A10.

[0294] Moreover, AMF_A240 may also indicate that the NSSAI requested by UE_A10 is not allowed by sending the twenty-second identification information, or may indicate that the NSSAI requested by UE_A10 cannot be found in the list managed by the network, or may indicate that the service provided by the NSSAI requested by UE_A10 is not allowed.

[0295] Moreover, AMF_A240 may also indicate that the NSSAI requested by UE_A10 is not allowed within the PLMN by sending the twenty-third identification information, or may indicate that the NSSAI requested by UE_A10 cannot be found in the list of each PLMN managed by the network, or may indicate that the services provided by the NSSAI requested by UE_A10 are not allowed within the PLMN.

[0296] Moreover, AMF_A240 may also indicate that the NSSAI requested by UE_A10 is not allowed in the registration area / cell by sending the twenty-fourth identification information, or may indicate that the NSSAI requested by UE_A10 cannot be found in the list managed by the network, or may indicate that the services provided by the NSSAI requested by UE_A10 are not allowed in the registration area / cell.

[0297] Moreover, AMF_A240 may also indicate that the NSSAI requested by UE_A10 is temporarily not allowed by sending the twenty-fifth identification information, and may also indicate that the service provided by the NSSAI requested by UE_A10 is temporarily not allowed. Moreover, AMF_A240 may also indicate network congestion by sending the twenty-sixth identification information. Moreover, AMF_A240 may also indicate that the request of UE_A10 is not recognized by sending the twenty-seventh identification information, and may also indicate that the NSSAI and / or DNN requested by UE_A10 is not recognized.

[0298] Moreover, AMF_A240 may also indicate that UE_A10 has rejected this process based on mobility restriction and / or RAT restriction by sending the twenty-eighth identification information, and may also indicate that it is prohibited to send and receive control messages and / or user data in the RAT to which UE_A10 is currently connected. Moreover, the type of deployment option of the system to which UE_A10 is currently connected may also be indicated. Specifically, it may indicate whether the type of deployment option of the system to which UE_A10 is currently connected is deployment option 2, deployment option 3, deployment option 4, deployment option 5, or deployment option 7.

[0299] Moreover, AMF_A240 can also indicate the timer value as the time until UE_A10 can start the next registration process by sending the twenty-ninth identification information, and can also instruct UE_A10 to perform the ninth behavior.

[0300] Moreover, AMF_A240 may also indicate that the NSSAI requested by UE_A10 is not allowed by sending one or more of the identification information from the twenty-first to twenty-seventh identification information, and may also indicate the reason why the NSSAI requested by UE_A10 is not allowed.

[0301] Moreover, AMF_A240 may also instruct UE_A10 to perform the first behavior by sending the twenty-first and / or twenty-second identification information. Moreover, AMF_A240 may also instruct UE_A10 to perform the second behavior by sending the twenty-first and / or twenty-third and / or twenty-seventh identification information. Moreover, AMF_A240 may also instruct UE_A10 to perform the third behavior by sending the twenty-first and / or twenty-fourth identification information. Moreover, AMF_A240 may also instruct UE_A10 to perform the fourth behavior by sending the twenty-first and / or twenty-fifth identification information.

[0302] Moreover, AMF_A240 may also instruct UE_A10 to perform the fourth behavior by sending the twenty-seventh and / or twenty-ninth identification information. Moreover, AMF_A240 may also instruct UE_A10 to perform the fifth behavior by sending the twenty-first and / or twenty-second and / or twenty-third and / or twenty-fourth and / or twenty-seventh and / or twenty-eighth identification information to UE_A10 in the fourth state. Moreover, AMF_A240 may also instruct UE_A10 to perform the sixth behavior by sending the twenty-first and / or twenty-fifth and / or twenty-sixth identification information to UE_A10 in the fourth state. Moreover, AMF_A240 may also instruct UE_A10 to perform the seventh and / or eighth behavior by sending the twenty-first and / or twenty-second and / or twenty-third and / or twenty-fourth and / or twenty-seventh and / or twenty-eighth identification information. Moreover, AMF_A240 may also instruct UE_A10 to perform the twelfth behavior by sending the twenty-first and / or twenty-eighth identification information.

[0303] It should be noted that AMF_A240 may determine which identification information among the twenty-first to twenty-ninth identification information to add to the registration rejection message based on the received identification information and / or network capability information and / or operator policy and / or network status. It should be noted that it is not limited to AMF_A240 to determine which identification information to add to the registration rejection message.

[0304] Each device completes this process based on the completion of process (A) or (B) in this process. It should be noted that each device can transition UE_A10 to the second state based on the completion of process (A) in this process, or can recognize the rejection of this process based on the completion of process (B) in this process, and can transition to the first state in the case of the initial registration process, and can transition to the first or second state in the case of the registration update process. In addition, the transition to each state of each device can be based on the completion of this process, can be based on the start of this process, or can be based on the establishment of a PDU session.

[0305] Furthermore, each device may implement processing based on the identification information sent and received in this process based on the completion of this process. For example, UE_A10 may recognize that the NSSAI requested by UE_A10 is allowed based on the thirteenth identification information, or may recognize that the NSSAI indicated by the thirteenth identification information is the same as the NSSAI requested by UE_A10.

[0306] Alternatively, UE_A10 may identify that the NSSAI requested by UE_A10 is not allowed based on the thirteenth identification information and / or the fifteenth identification information and / or the sixteenth identification information and / or the seventeenth identification information, and may also identify that the NSSAI indicated by the thirteenth identification information is different from the NSSAI requested by UE_A10. Moreover, UE_A10 may also perform the first behavior based on the reception of the thirteenth identification information and / or the fifteenth identification information and / or the sixteenth identification information and / or the seventeenth identification information indicating that it is not allowed, and may also perform the eleventh behavior. Alternatively, UE_A10 may perform the fourth behavior based on the reception of the thirteenth identification information and / or the fifteenth identification information and / or the sixteenth identification information and / or the seventeenth identification information and / or the eighteenth identification information indicating that it is allowed.

[0307] Moreover, UE_A10 can identify the type of service area restrictions of the registration area to which UE_A10 is currently connected based on the reception of the fourteenth identification information. Specifically, UE_A10 can identify whether the registration area to which UE_A10 is currently connected is an allowed area or a non-allowed area based on the reception of the fourteenth identification information.

[0308] Moreover, UE_A10 may also perform the first action based on the reception of the thirteenth identification information and / or the fifteenth identification information and / or the sixteenth identification information and / or the seventeenth identification information indicating that it is not allowed.

[0309] Moreover, UE_A10 can perform the fourth action based on the reception of the thirteenth identification information and / or the fifteenth identification information and / or the sixteenth identification information and / or the seventeenth identification information indicating permission and / or the eighteenth identification information.

[0310] Furthermore, UE_A10 may perform the sixth behavior based on the reception of the registration acceptance message. Furthermore, UE_A10 may perform the ninth behavior based on the reception of the eighteenth identification information. Furthermore, UE_A10 may perform the tenth behavior based on the reception of the registration acceptance message.

[0311] Furthermore, UE_A10 may also perform the eleventh behavior based on the thirteenth identification information and / or the fifteenth identification information and / or the sixteenth identification information and / or the seventeenth identification information indicating that it is not allowed. Furthermore, UE_A10 may perform the twelfth behavior based on the reception of the fourteenth identification information.

[0312] Moreover, UE_A10 can also identify that the NSSAI requested by UE_A10 is not allowed based on the reception of one or more of the identification information from the twenty-first to twenty-seventh identification information, and can also identify the reason why the NSSAI requested by UE_A10 is not allowed.

[0313] Moreover, UE_A10 can also identify that the sending and receiving of control messages and / or user data in the RAT to which UE_A10 is currently connected is prohibited based on the reception of the twenty-eighth identification information, and can also identify the type of deployment option of the system to which UE_A10 is currently connected. Specifically, UE_A10 can identify whether the type of deployment option of the system to which UE_A10 is currently connected is deployment option 2, deployment option 3, deployment option 4, deployment option 5, or deployment option 7 based on the reception of the twenty-eighth identification information.

[0314] Moreover, UE_A10 may perform the first behavior based on the reception of the twenty-first identification information and / or the twenty-second identification information. Moreover, UE_A10 may perform the second behavior based on the reception of the twenty-first identification information and / or the twenty-third identification information and / or the twenty-seventh identification information.

[0315] Moreover, UE_A10 may perform the third behavior based on the reception of the 21st identification information and / or the 24th identification information. UE_A10 may perform the fourth behavior based on the reception of the 21st identification information and / or the 25th identification information and / or the 27th identification information and / or the 29th identification information.

[0316] Furthermore, UE_A10 may perform the fifth behavior based on the reception of the registration rejection message when each device is in the third state. Furthermore, UE_A10 may perform the fifth behavior based on the reception of the twenty-first identification information and / or the twenty-second identification information and / or the twenty-third identification information and / or the twenty-fourth identification information and / or the twenty-seventh identification information and / or the twenty-eighth identification information when each device is in the fourth state.

[0317] Furthermore, UE_A10 may also perform the sixth behavior based on the reception of the 21st identification information and / or the 25th identification information and / or the 26th identification information when each device is in the fourth state. Furthermore, UE_A10 may perform the seventh behavior based on the reception of the 21st identification information and / or the 22nd identification information and / or the 23rd identification information and / or the 24th identification information and / or the 27th identification information and / or the 28th identification information.

[0318] Moreover, UE_A10 may perform the eighth behavior based on the reception of the twenty-first identification information and / or the twenty-second identification information and / or the twenty-third identification information and / or the twenty-fourth identification information and / or the twenty-seventh identification information and / or the twenty-eighth identification information. Moreover, UE_A10 may perform the ninth behavior based on the reception of the twenty-ninth identification information.

[0319] Moreover, UE_A10 may perform the tenth behavior based on the reception of the registration rejection message. Moreover, UE_A10 may perform the twelfth behavior based on the reception of the twenty-first identification information and / or the twenty-eighth identification information.

[0320] Moreover, in the case where each device has been transformed into the second state, each device can perform a PDU session establishment process. Specifically, for example, UE_A10 can perform a PDU session establishment process based on the NSSAI assigned by the network. Alternatively, in the case where each device has been transformed into the second state, each device can perform a deregistration process. Alternatively, in the case where each device has been transformed into the second state, a registration update process can be performed.

[0321] In addition, the first condition determination may be performed based on the identification information and / or subscriber information and / or operator policy included in the registration request message. For example, the first condition determination may be true when the network allows the request of UE_A10. In addition, the first condition determination may be false when the network does not allow the request of UE_A10. Moreover, the first condition determination may be true when the network of the connection object of UE_A10 and / or the device within the network supports the function requested by UE_A10, and may be false when it is not supported. It should be noted that the conditions that determine the truth or falsity of the first condition determination may not be limited to the above-mentioned conditions.

[0322] In addition, the fourth condition determination can be performed based on whether AMF_A240 receives an SM message, or based on whether the registration request includes an SM message. For example, the fourth condition determination can be true when AMF_A240 receives an SM message and / or the registration request includes an SM message, and can be false when AMF_A240 does not receive an SM message and / or the registration request does not include an SM message. It should be noted that the conditions for determining the truth or falsity of the fourth condition may not be limited to the above conditions.

[0323] [2. Improvement example]

[0324] The program operating in the device involved in the present invention may be a program that controls the Central Processing Unit (CPU) and the like to realize the functions of the embodiments involved in the present invention and enables the computer to function. 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.

[0325] 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 the device and including hardware such as an operating system and peripherals. In addition, the "computer-readable recording medium" may be 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.

[0326] In addition, each functional block or each feature of the device used in the above-mentioned embodiments can be installed or executed by an electronic circuit, such as an integrated circuit or multiple integrated circuits. Circuits designed in a manner to perform the functions described in this specification may include: a general-purpose processor, a digital signal processor (DSP), an integrated circuit for a specific purpose (ASIC), a field programmable gate array (FPGA) or other programmable logic elements, discrete gates or transistor logic, discrete hardware components, or a combination thereof. The general-purpose processor may be a microprocessor, or it may be a processor, controller, microcontroller or state machine of the previous type. The above-mentioned electronic circuit may be composed of digital circuits or analog circuits. In addition, in the case where integrated circuit technology that replaces current integrated circuits appears due to advances in semiconductor technology, one or more schemes of the present invention may also use new integrated circuits based on this technology.

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

[0328] Above, 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 embodiments, 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 shown in the technical solution, 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.

[0329] Explanation of symbols

[0330] 1 Mobile Communication System

[0331] 5 PDN_A

[0332] 10UE_A

[0333] 30 PGW_A

[0334] 35 SGW_A

[0335] 40 MME_A

[0336] 42 SGSN_A

[0337] 45 eNB_A

[0338] 46 SCEF_A

[0339] 50 HSS_A

[0340] 60 PCRF_A

[0341] 80 E-UTRAN_A

[0342] 105 DN_B

[0343] 120 NextGen RAN_A

[0344] 122 NR node_A

[0345] 123 NR node_B

[0346] 125 WLAN ANc

[0347] 126 WAG_A

[0348] 130 UPGW_A

[0349] 140 CPF_A

[0350] 190 Core Network_B

[0351] 230 SMF_A

[0352] 235 UPF_A

[0353] 240 AMF_A

Claims

1. A user equipment UE, It is characterized in that The UE has: The transceiver unit and the control unit, wherein: The transceiver unit is configured as follows: During the registration process, a registration request message including single network slice selection assistance information S-NSSAI is sent to the access and mobility management function AMF, and receiving a response message to the registration request message from the AMF, the response message including first identification information or second identification information, the first identification information indicating that the S-NSSAI is not allowed in the current public land mobile network PLMN; and the second identification information indicating that the S-NSSAI is not allowed in the current registration area, During the registration process after receiving the response message including the first identification information, The control unit is configured as follows: determining not to include the S-NSSAI in a registration request message in the current PLMN, and The transceiver unit is configured as follows: sending the Registration Request message without including the S-NSSAI, and During the registration process after receiving the response message including the second identification information, The control unit is configured as follows: determining not to include the S-NSSAI in a registration request message in the current registration area, and The transceiver unit is configured as follows: Sending the registration request message without including the S-NSSAI.

2. The UE according to claim 1, wherein The first identification information indicates a rejection reason for the current PLMN, and The second identification information indicates a rejection reason in the current registration area.

3. A communication control method for a user equipment UE, the communication control method The following steps are involved: During the registration process, a registration request message including single network slice selection assistance information S-NSSAI is sent to the access and mobility management function AMF, and receiving a response message to the registration request message from the AMF, the response message including first identification information or second identification information, the first identification information indicating that the S-NSSAI is not allowed in the current public land mobile network PLMN; and the second identification information indicating that the S-NSSAI is not allowed in the current registration area, During the registration process after receiving the response message including the first identification information, determining not to include the S-NSSAI in a registration request message in the current PLMN, and sending the Registration Request message without including the S-NSSAI, and During the registration process after receiving the response message including the second identification information, determining not to include the S-NSSAI in a registration request message in the current registration area, and Sending the registration request message without including the S-NSSAI.

4. The communication control method according to claim 3, wherein The first identification information indicates a rejection reason for the current PLMN, and The second identification information indicates a rejection reason in the current registration area.