user equipment

Abstract

According to one aspect of the present application, in connection of a mobile terminal device to a non-public network (NPN) of a 5GS, the mobile terminal device and the device within the core network do not make congestion management effective. Alternatively, in connection of a mobile terminal device to a non-public network (NPN) of a 5GS, the mobile terminal device and the device within the core network provide a NAS-level congestion management method to the mobile terminal device and the device within the core network in connection to the NPN (Non-public Network) of the 5GS by making congestion management effective only in a specific PLMN (Public land mobile network) of the congestion management.

Description

Technical Field

[0001] This application claims the benefit of priority from Japanese Patent Application No. 2019-147897, filed on August 9, 2019, the entire contents of which are incorporated herein by reference. Background Art

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

[0003] Furthermore, in recent years, 3GPP has also been conducting research on the next-generation communication technology and system architecture of the 5G (5th Generation) mobile communication system, specifically the 5GS (5G System) standardization as a system for implementing the 5G mobile communication system (see Non-Patent Documents 1 and 2). 5GS identifies the technical issues involved in connecting various terminals to cellular networks and specifies solutions.

[0004] Prior art literature

[0005] Non-patent literature

[0006] Non-patent document 1: 3GPP TS 23.501 V16.1.0 (2019-06); 3rd Generation Partnership Project; Technical Specification Group Services and SystemAspects; System Architecture for the 5G System; Stage 2 (Release 16)

[0007] Non-patent document 2: 3GPP TS 23.502 V16.1.1(2019-06); 3rd GenerationPartnership Project; Technical Specification Group Services and SystemAspects; Procedures for the 5G System; Stage 2 (Release 16)

[0008] Non-patent document 3: 3GPP TS 24.501 V16.1.0 (2019-06); 3rd Generation Partnership Project; Technical Specification Group Core Network and Terminals; Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3 (Release 16) Summary of the Invention

[0009] Problems to be solved by the invention

[0010] In 5GS, in addition to providing a mechanism that provides a function equivalent to congestion management, control signal management based on reasons other than congestion management is also being studied (see Non-Patent Documents 1, 2, and 3).

[0011] On the other hand, in 5GS, non-public networks (NPNs) are also being studied. NPNs are networks that only specific users or UEs are allowed to access or connect to.

[0012] However, it is not clear whether the UE and the network apply congestion management in 5GS when connected to the NPN.

[0013] Furthermore, it is unclear whether congestion management will continue in the destination PLMN if the UE changes its PLMN while connected to the NPN and congestion management is applied, and the PLMN before the change is the home PLMN.

[0014] The present invention has been made in view of the above circumstances, and an object of the present invention is to provide a mechanism and a communication control method for realizing a control signal management process for the purpose of congestion management during system modification.

[0015] Technical Solution

[0016] The UE (User Equipment) of one embodiment of the present application is a UE provided with a control section and a transceiving section, characterized in that, in a case where the transceiving section receives a reason value and an avoidance timer value for starting a timer for congestion management based on a DNN (Data Network Name), the control section starts the timer using the avoidance timer value, the reason value indicates a shortage of resources, and the timer is started per DNN and SNPN (Stand-alone Non-Public Network).

[0017] The communication control method of one embodiment of the present application is a communication control method of a UE (User Equipment), characterized in that, in a case where a reason value and an avoidance timer value for starting a timer for congestion management based on a DNN (Data Network Name) are received, the timer is started using the avoidance timer value, the reason value indicates a shortage of resources, and the timer is started per DNN and SNPN (Stand-alone Non-Public Network).

[0018] Advantageous Effects

[0019] According to one aspect of the present application, a terminal device constituting a 5GS, a device in a core network is characterized in that processing for supporting mobile management, session management related to a non-public network is implemented. BRIEF DESCRIPTION OF DRAWINGS

[0020] Figure 1 is a diagram explaining an outline of a mobile communication system (EPS / 5GS).

[0021] Figure 2 is a diagram explaining a detailed configuration of a mobile communication system (EPS / 5GS).

[0022] Figure 3 is a diagram explaining a device configuration of a UE.

[0023] Figure 4 is a diagram explaining a configuration of an access network device (gNB) in a 5GS.

[0024] Figure 5 is a diagram explaining a configuration of a core network device (AMF / SMF / UPF) in a 5GS.

[0025] Figure 6 is a diagram explaining a login procedure.

[0026] Figure 7 is a diagram explaining a PDU session establishment procedure.

[0027] Figure 8 is a diagram illustrating a network-led PDU session management procedure.

[0028] Figure 9 is a diagram illustrating a UE-led PDU session management procedure. DETAILED DESCRIPTION

[0029] Hereinafter, a best mode for carrying out the present application will be described with reference to the accompanying drawings. Note that, in the present embodiment, an embodiment of a mobile communication system in which the present application is applied will be described as an example.

[0030] [1. Outline of System]

[0031] First, Figure 1 is a diagram for illustrating an outline of a mobile communication system 1 used in each embodiment, Figure 2 is a diagram for illustrating a detailed configuration of the mobile communication system 1.

[0032] In Figure 1 , it is described that the mobile communication system 1 is configured of a UE_A 10, an access network_A 80, a core network_A 90, a PDN (Packet Data Network) _A 5, an access network_B 120, a core network_B 190, and a DN (Data Network) _A 6.

[0033] Hereinafter, these devices, functions will be described while sometimes omitting the symbols, for example, UE, access network_A, core network_A, PDN, access network_B, core network_B, DN, and the like.

[0034] Further, in Figure 2 , it is described that the UE_A 10, the E-UTRAN 80, the MME 40, the SGW 35, the PGW-U 30, the PGW-C 32, the PCRF 60, the HSS 50, the 5G AN 120, the AMF 140, the UPF 130, the SMF 132, the PCF 160, the UDM 150, the N3IWF 170, and the like devices, functions, and interfaces connecting these devices, functions to each other.

[0035] Hereinafter, these devices, functions will be described while sometimes omitting the symbols, for example, UE, E-UTRAN, MME, SGW, PGW-U, PGW-C, PCRF, HSS, 5G AN, AMF, UPF, SMF, PCF, UDM, N3IWF, and the like.

[0036] Note that, as the EPS (Evolved Packet System) of the 4G system, the configuration includes the access network_A and the core network_A, but can further include the UE and / or the PDN. Further, as the 5GS (5G System) of the 5G system, the configuration includes the UE, the access network_B, and the core network_B, but can further include the DN.

[0037] The UE is a device that can connect to a network service via a 3GPP access (also referred to as a 3GPP access network, 3GPP AN) and / or a non-3GPP access (also referred to as a non-3GPP access network, non-3GPP AN). The UE can be a terminal device such as a portable telephone, a smartphone, or the like that can perform wireless communication, and can be a terminal device that can connect to the EPS, the 5GS. The UE can have a UICC (Universal Integrated Circuit Card), an eUICC (Embedded UICC). Note that the UE can be expressed as a user device, and can be expressed as a terminal device.

[0038] Further, the access network_A corresponds to an E-UTRAN (Evolved Universal Terrestrial Radio Access Network) and / or a wireless LAN access network. In the E-UTRAN, one or more eNBs (evolved Node Bs) 45 are disposed. Note that, hereinafter, the eNB 45 is sometimes described with the symbol omitted, for example, eNB. Further, in the case where a plurality of eNBs are present, the eNBs are connected to each other, for example, through an X2 interface. Further, in the wireless LAN access network, one or more access points are disposed.

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

[0040] In addition, the non-3GPP access network can be an untrusted non-3GPP access network or a trusted non-3GPP access network. Here, the untrusted non-3GPP access network can be, for example, a non-3GPP access network such as a public wireless LAN that is not securely managed within the access network. On the other hand, the trusted non-3GPP access network can be an access network specified by 3GPP, and can also have a TNAP (trusted non-3GPP access point) and a TNGF (trusted non-3GPP Gateway function).

[0041] In the following, E-UTRAN and NG-RAN are referred to as 3GPP access. Wireless LAN access networks and non-3GPP ANs are also referred to as non-3GPP access. Nodes deployed in access network_B are also collectively referred to as NG-RAN nodes.

[0042] In addition, below, access network_A and / or access network_B and / or the device included in access network_A and / or the device included in access network_B are sometimes referred to as access network or access network device.

[0043] Furthermore, Core Network_A corresponds to the Evolved Packet Core (EPC). The EPC includes, for example, the Mobility Management Entity (MME), Serving Gateway (SGW), Packet Data Network Gateway (PGW)-U, PGW-C, Policy and Charging Rules Function (PCRF), and Home Subscriber Server (HSS).

[0044] Furthermore, Core Network_B corresponds to 5GCN (5G Core Network). 5GCN includes, for example, AMF (Access and Mobility Management Function), UPF (User Plane Function), SMF (Session Management Function), PCF (Policy Control Function), and UDM (Unified Data Management). Here, 5GCN can be represented as 5GC.

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

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

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

[0048] In addition, below, at least a portion of the access network_A, core network_A, PDN, access network_B, core network_B, and DN, and / or one or more devices included therein, may be referred to as a network or network device. In other words, the network and / or network device transmitting and receiving messages and / or executing a process refers to at least a portion of the access network_A, core network_A, PDN, access network_B, core network_B, and DN, and / or one or more devices included therein, transmitting and receiving messages and / or executing a process.

[0049] Furthermore, the UE can connect to an access network. Furthermore, the UE can connect to a core network via the access network. Furthermore, the UE can connect to a PDN or DN via the access network and the core network. In other words, the UE can send and receive (communicate) user data with the PDN or DN. This can be done using not only Internet Protocol (IP) communication but also non-IP communication.

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

[0051] In addition, access network_A, core network_A, access network_B, core network_B, PDN_A, DN_A can be composed of Figure 2For example, Core Network_A and / or Core Network_B may include AUSF (Authentication Server Function) and AAA (Authentication, authorization, and accounting) server (AAA-S).

[0052] Here, the AUSF is a core network device that has an authentication function for 3GPP access and non-3GPP access. Specifically, it is a network function unit that receives a request for authentication for 3GPP access and / or non-3GPP access from a UE and performs an authentication process.

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

[0054] It should be noted that in Figure 2 In the figure, for simplicity, each device and function is described one by one, but multiple devices and functions of the same type may be configured in the mobile communication system 1. Specifically, the mobile communication system 1 may include multiple devices and functions such as UE_A 10, E-UTRAN 80, MME 40, SGW 35, PGW-U 30, PGW-C 32, PCRF 60, HSS 50, 5G AN 120, AMF 140, UPF 130, SMF 132, PCF 160, and / or UDM 150.

[0055] [2. Configuration of Each Device]

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

[0057] It should be noted that the storage units (storage_A340, storage_A440, storage_B540, storage_A640, storage_B740) within each device and function described below are composed of, for example, semiconductor memories, SSDs (Solid State Drives), HDDs (Hard Disk Drives), etc. In addition, each storage unit can store not only the information originally set at the factory stage, but also various information sent and received between the device itself and devices and functions other than the function (such as UEs and / or access network devices and / or core network devices and / or PDNs and / or DNs). In addition, each storage unit can store identification information, control information, flags, parameters, etc. included in control messages sent and received within the various communication processes described below. In addition, each storage unit can store this information in each UE. In addition, when intercommunication between 5GS and EPS is performed, each storage unit can store control messages and user data sent and received between the devices and functions included in the 5GS and / or EPS. At this time, not only data sent and received via the N26 interface can be stored, but also data not sent and received via the N26 interface can be stored.

[0058] [2.1. UE Device Configuration]

[0059] First, use Figure 3 An example of the configuration of a UE (User Equipment) is described. The UE is composed of a control unit A300, an antenna 310, a transceiver A320, and a storage unit A340. The control unit A300, the transceiver A320, and the storage unit A340 are connected via a bus. The transceiver A320 is connected to the antenna 310.

[0060] The control unit A300 is a functional unit that controls the overall operation and functions of the UE. The control unit A300 reads and executes various programs stored in the storage unit A340 as needed to implement various processes in the UE.

[0061] The transceiver_A320 is a functional unit for wireless communication with a base station (eNB or gNB) within the access network via an antenna. Specifically, the UE uses the transceiver_A320 to transmit and receive user data and / or control information with the access network, core network, PDN, and / or DN.

[0062] Reference Figure 2To explain in detail, the UE can communicate with the base station device (eNB) within the E-UTRAN via the LTE-Uu interface using the transceiver_A320. Furthermore, the UE can communicate with the base station device (gNB) within the 5G AN using the transceiver_A320. Furthermore, the UE can send and receive NAS (Non-Access-Stratum) messages with the AMF via the N1 interface using the transceiver_A320. However, the N1 interface is a logical interface, so in practice, communication between the UE and the AMF is carried out via the 5G AN.

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

[0064] [2.2. gNB Device Configuration]

[0065] Next, use Figure 4 An example of a gNB configuration is described below. The gNB consists of a control unit B500, an antenna 510, a network connection unit B520, a transceiver B530, and a storage unit B540. The control unit B500, the network connection unit B520, the transceiver B530, and the storage unit B540 are connected via a bus. The transceiver B530 is connected to the antenna 510.

[0066] The control unit B500 controls the overall operation and functions of the gNB. It implements various processes within the gNB by reading and executing various programs stored in the storage unit B540 as needed.

[0067] The Network Connection Unit_B520 is a functional unit for communication between the gNB and the AMF and / or UPF. Specifically, the gNB can use the Network Connection Unit_B520 to send and receive user data and / or control information with the AMF and / or UPF.

[0068] The transceiver_B 530 is a functional unit for wirelessly communicating with the UE via the antenna 510. Specifically, the gNB can use the transceiver_B 530 to transmit and receive user data and / or control information to and from the UE.

[0069] Reference Figure 2 To elaborate, the gNB within the 5G AN can communicate with the AMF via the N2 interface using the network connection unit_B520 and with the UPF via the N3 interface. Furthermore, the gNB can communicate with the UE using the transceiver unit_B530.

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

[0071] [2.3.AMF's device configuration]

[0072] Next, the use of the AMF will be described. Figure 5 An example of the device configuration of the AMF will be described. The AMF is configured by a control section_B700, a network connection section_B720, and a storage section_B740. The control section_B700, the network connection section_B720, and the storage section_B740 are connected via a bus. The AMF can be a node that handles the control plane.

[0073] The control section_B700 is a functional section that controls the operation and the function of the AMF as a whole. The control section_B700 realizes various processes in the AMF by reading out various programs stored in the storage section_B740 as necessary and executing them.

[0074] The network connection section_B720 is a functional section for connecting the AMF with a base station device (gNB) and / or an SMF and / or a PCF and / or a UDM and / or a SCEF within a 5G AN. That is, the AMF can transmit and receive user data and / or control information between the base station device (gNB) and / or the SMF and / or the PCF and / or the UDM and / or the SCEF within the 5G AN using the network connection section_B720.

[0075] Reference will be made to Figure 2 In detail, the AMF within the 5GCN can communicate with the gNB via the N2 interface, can communicate with the UDM via the N8 interface, can communicate with the SMF via the N11 interface, and can communicate with the PCF via the N15 interface by using the network connection section_A620. In addition, the AMF can transmit and receive NAS messages with the UE via the N1 interface by using the network connection section_A620. However, the N1 interface is a logical interface, and thus, in reality, the communication between the UE and the AMF is performed via the 5G AN. In addition, the AMF can communicate with the MME via the N26 interface by using the network connection section_A620 in the case where the N26 interface is supported.

[0076] The storage section_B740 is a functional section for storing programs, user data, control information, and the like required for each operation of the AMF.

[0077] Note that the AMF has a function of exchanging control messages with the RAN using an N2 interface, a function of exchanging NAS messages with the UE using an N1 interface, a function of performing encryption and integrity protection of NAS messages, a Registration management (RM) function, a Connection management (CM) function, a Reachability management function, a Mobility management function of the UE or the like, a function of transferring Session Management (SM) messages between the UE and the SMF, an Access Authentication function, a Security Anchor function (SEA), a Security Context management (SCM) function, a function of supporting an N2 interface for the N3IWF (Non-3GPP Interworking Function), a function of supporting transmission and reception of NAS signals with the UE via the N3IWF, a function of authenticating the UE connected via the N3IWF, and the like.

[0078] Further, in the Registration management, an RM state of each UE is managed. The RM state can be synchronized between the UE and the AMF. As the RM state, there are a non-registered state (RM-DEREGISTERED state) and a registered state (RM-REGISTERED state). In the non-registered state, the UE is not registered to the network, and therefore, the UE context in the AMF does not have location information, routing information valid for the UE, so the AMF is in a state where the UE cannot be reached. Further, in the registered state, the UE is registered to the network, and therefore, the UE can receive a service that needs to be registered to the network. Note that the RM state can also be expressed as a 5GMM state (5GMM state). In this case, the non-registered state can also be expressed as a 5GMM-DEREGISTERED state, and the registered state can also be expressed as a 5GMM-REGISTERED state.

[0079] In other words, 5GMM-REGISTERED can be a state in which each apparatus has established a 5GMM context, and can be a state in which a PDU session context has been established. Note that, in a case where each apparatus is in 5GMM-REGISTERED, UE_A 10 can start transmission and reception of user data, control messages, and can respond to paging. Further, note that, in a case where each apparatus is in 5GMM-REGISTERED, UE_A 10 can perform a login procedure other than a login procedure for initial login and / or a service request procedure.

[0080] Further, 5GMM-DEREGISTERED can be a state in which each apparatus has not established a 5GMM context, can be a state in which the network does not have location information of UE_A 10, and can be a state in which the network cannot reach UE_A 10. Note that, in a case where each apparatus is in 5GMM-DEREGISTERED, UE_A 10 can start a login procedure, and can establish a 5GMM context by performing the login procedure.

[0081] Further, in connection management, a CM state of each UE is managed. The CM state can be synchronized between the UE and the AMF. As the CM state, there are a non-connected state (CM-IDLE state) and a connected state (CM-CONNECTED state). In the non-connected state, the UE is in a logged state, but does not have a NAS signaling connection established between the UE and the AMF via an N1 interface. Further, in the non-connected state, the UE does not have a connection of an N2 interface (N2 connection) and a connection of an N3 interface (N3 connection). On the other hand, in the connected state, there is a NAS signaling connection established between the UE and the AMF via the N1 interface. Further, in the connected state, the UE can also have a connection of the N2 interface (N2 connection) and / or a connection of the N3 interface (N3 connection).

[0082] Also, in the connection management, it is possible to manage the CM state over 3GPP access and the CM state over non-3GPP access separately. In this case, as the CM state over 3GPP access, there can be a non-connected state over 3GPP access (CM-IDLE state over 3GPP access) and a connected state over 3GPP access (CM-CONNECTED state over 3GPP access). Also, as the CM state over non-3GPP access, there can be a non-connected state over non-3GPP access (CM-IDLE state over non-3GPP access) and a connected state over non-3GPP access (CM-CONNECTED state over non-3GPP access). Note that the non-connected state can represent an idle mode, and the connected state mode can represent a connected mode.

[0083] Note that the CM state can also represent a 5GMM mode. In this case, the non-connected state can also represent a 5GMM-IDLE mode, and the connected state can also represent a 5GMM-CONNECTED mode. Also, the non-connected state over 3GPP access can also represent a 5GMM-IDLE mode over 3GPP access, and the connected state over 3GPP access can also represent a 5GMM-CONNECTED mode over 3GPP access. Also, the non-connected state over non-3GPP access can also represent a 5GMM-IDLE mode over non-3GPP access, and the connected state over non-3GPP access can also represent a 5GMM-CONNECTED mode over non-3GPP access. Note that the 5GMM-IDLE mode can represent an idle mode, and the 5GMM-CONNECTED mode can represent a connected mode.

[0084] Further, the AMF can be configured more than one within the core network_B. Further, the AMF can be an NF that manages more than one NSI (Network Slice Instance). Further, the AMF can also be a shared CP function (CCNF; Common CPNF (Control Plane Network Function)) that is shared among a plurality of NSIs.

[0085] Note that the N3IWF is an apparatus and / or function configured between the non-3GPP access and the 5GCN in a case where the UE is connected with the 5GS via the non-3GPP access.

[0086] [2.4. Apparatus Configuration of SMF]

[0087] Next, the use of the SMF will be described. Figure 5 An example of the apparatus configuration of the SMF will be described. The SMF is configured by a control unit_B 700, a network connection unit_B 720, and a storage unit_B 740. The control unit_B 700, the network connection unit_B 720, and the storage unit_B 740 are connected via a bus. The SMF can be a node that handles the control plane.

[0088] The control unit_B 700 is a functional unit that controls the actions and functions of the entire SMF. The control unit_B 700 realizes various processes in the SMF by reading out and executing various programs stored in the storage unit_B 740 as necessary.

[0089] The network connection unit_B 720 is a functional unit for connecting the SMF with the AMF and / or the UPF and / or the PCF and / or the UDM. That is, the SMF can transmit and receive user data and / or control information between the AMF and / or the UPF and / or the PCF and / or the UDM using the network connection unit_B 720.

[0090] Referring to Figure 2 In detail, the SMF in the 5GCN can communicate with the AMF via the N11 interface, can communicate with the UPF via the N4 interface, can communicate with the PCF via the N7 interface, and can communicate with the UDM via the N10 interface by using the network connection unit_A 620.

[0091] The storage unit_B 740 is a functional unit for storing programs, user data, control information, and the like required for each action of the SMF.

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

[0093] [2.5. UPF device configuration]

[0094] Next, use Figure 5 The following describes an example of a UPF configuration. The UPF consists of a control unit B700, a network connection unit B720, and a storage unit B740. The control unit B700, the network connection unit B720, and the storage unit B740 are connected via a bus. The UPF can be a node that processes the control plane.

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

[0096] The Network Connection Unit_B720 is a functional unit for connecting the UPF to a base station (gNB) and / or SMF and / or DN within the 5G AN. Specifically, the UPF can use the Network Connection Unit_B720 to transmit and receive user data and / or control information with a base station (gNB) and / or SMF and / or DN within the 5G AN.

[0097] Reference Figure 2 To provide a detailed explanation, the UPF in the 5GCN can communicate with the gNB via the N3 interface by using the network connection part _A620, can communicate with the SMF via the N4 interface, can communicate with the DN via the N6 interface, and can communicate with other UPFs via the N9 interface.

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

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

[0100] Furthermore, the UPF can be a gateway for IP and / or non-IP communications. Furthermore, the UPF can function as both a transport for IP communications and a converter for non-IP and IP communications. Furthermore, the multiple gateways configured can be gateways connecting the core network B and a single DN. It should be noted that the UPF can have connectivity with other NFs and can also connect to various devices via other NFs.

[0101] It should be noted that the user plane is user data sent and received between the UE and the network. The user plane can be sent and received using a PDN connection or a PDU session. In the case of EPS, the user plane can also be sent and received using the LTE-Uu interface and / or the S1-U interface and / or the S5 interface and / or the S8 interface and / or the SGi interface. In the case of 5GS, the user plane can also be sent and received via the interface between the UE and the NG RAN and / or the N3 interface and / or the N9 interface and / or the N6 interface. Hereinafter, the user plane may also be represented as U-Plane.

[0102] The control plane is responsible for sending and receiving control messages for purposes such as UE communication control. This control plane can use the NAS (Non-Access-Stratum) signaling connection between the UE and the MME for transmission and reception. Furthermore, in the case of EPS, the control plane can also use the LTE-Uu interface and the S1-MME interface for transmission and reception. Furthermore, in the case of 5GS, the control plane can also use the interface between the UE and the NG RAN and the N2 interface for transmission and reception. Hereinafter, the control plane may also be referred to as the Control Plane or the C-Plane.

[0103] Furthermore, the user plane (U-Plane, User Plane; UP) can be a communication path for sending and receiving user data and can be composed of multiple bearers. Furthermore, the control plane (C-Plane, Control Plane; CP) can be a communication path for sending and receiving control messages and can be composed of multiple bearers. [2.6. Description of Other Devices and / or Functions]

[0104] Next, other devices and / or functions will be described.

[0105] The term "network" refers to at least a portion of the access network B, core network B, and DN. Furthermore, one or more devices included in at least a portion of the access network B, core network B, and DN may also be referred to as a network or network device. Specifically, "the network performs message transmission, reception, and / or processing" may mean that a device within the network (a network device and / or a control device) performs message transmission, reception, and / or processing. Conversely, "a device within the network performs message transmission, reception, and / or processing" may mean that the network performs message transmission, reception, and / or processing.

[0106] In addition, SM (Session Management) messages (also known as NAS (Non-Access-Stratum) SM messages) can be NAS messages used in the SM process, or can be control messages sent and received between UE_A10 and SMF132 via AMF140. SM messages can include PDU session establishment request messages, PDU session establishment accept messages, PDU session complete messages, PDU session reject messages, PDU session change request messages, PDU session change accept messages, and PDU session change response messages. In addition, the SM process can include the PDU session establishment process.

[0107] Furthermore, 5GS (5G System) services may be connection services provided using the core network B190. Furthermore, 5GS services may be different from EPS services or the same as EPS services.

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

[0109] Furthermore, the S1 mode allows UE_A10 to access the EPC via the E-UTRAN. In other words, the S1 mode allows for the transmission and reception of messages using the S1 interface. It should be noted that the S1 interface may be composed of the S1-MME interface and the S1-U interface.

[0110] Furthermore, the N1 mode is a mode in which UE_A10 is allowed to access the 5GC via the 5G access network. In other words, the N1 mode may also be a mode in which messages are sent and received using the N1 interface.

[0111] In addition, the APN (Access Point Name) can be identification information for identifying the core network and / or external networks such as PDN. In addition, the APN can also be used as information for selecting a gateway such as PGW_A30 / UPF130 connected to the core network A_90.

[0112] In addition, TFT (Traffic Flow Template) means that 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, TFT can establish a correspondence between user data such as application data being sent and received and an appropriate transmission path, and can be identification information that identifies application data. In addition, UE_A10 can use the default bearer to send and receive user data that cannot be identified by TFT. In addition, UE_A10 can pre-store the TFT associated with the default bearer.

[0113] The PDN (Packet Data Network) type indicates the type of PDN connection, including IPv4, IPv6, IPv4v6, and non-IP. If IPv4 is specified, data is sent and received using IPv4. If IPv6 is specified, data is sent and received using IPv6. If IPv4v6 is specified, data is sent and received using either IPv4 or IPv6. If non-IP is specified, communication is performed not only using IP but also using methods other than IP.

[0114] In addition, the EPS bearer is a logical communication path established between the UE and the PGW, and is the communication path that constitutes the PDN connection. EPS bearers include default bearers (also called default EPS bearers) and dedicated bearers (also called dedicated EPS bearers).

[0115] The default bearer is the EPS bearer initially established for a PDN connection. Only one default bearer can be established in a PDN connection. The default bearer is an EPS bearer that can be used for user data communications that are not associated with a TFT (Traffic Flow Template).

[0116] A dedicated bearer is an EPS bearer established after the default bearer is established in a PDN connection. More than one dedicated bearer can be established in one PDN connection. A dedicated bearer is an EPS bearer that can be used for communication of user data corresponding to a TFT.

[0117] A PDU (Protocol Data Unit / Packet Data Unit) session can be defined as an association between a DN providing PDU connectivity services and a UE, but can also be connectivity established between a UE and an external gateway. The UE can use a PDU session to send and receive user data with the DN by establishing a PDU session in the 5GS via the access network B and the core network B. Here, the external gateway can be a UPF, SCEF, or similar device. The UE can use a PDU session to send and receive user data with devices such as application servers deployed in the DN.

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

[0119] Furthermore, the DNN (Data Network Name) can be used to identify external networks such as the core network and / or DN. Furthermore, the DNN can be used to select gateways such as PGW_A30 / UPF130 that connect to the core network B190. Furthermore, the DNN can be equivalent to the APN (Access Point Name).

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

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

[0122] In addition, a network slice instance (NSI) refers to a network slice formed and configured by a collection of instances (entities) of network functions (NFs) and required resources. Here, NF refers to a processing function in a network, which is adopted or defined in 3GPP. NSI is an entity that constitutes one or more NSs within the core network_B. In addition, NSI can be composed of a virtual NF (Network Function) generated using NST (Network Slice Template). Here, NST refers to a logical expression of one or more NFs associated with a resource request for providing the requested communication service or capability. That is, NSI can refer to an aggregate within the core network_B190 composed of multiple NFs. In addition, NSI can be a logical network configured to divide the user data sent according to services, etc. There can be more than one NF in the NS. The NF constituted in the NS may be a device shared with other NSs, or may not be a device shared with other NSs. The UE and / or devices within the network can be assigned to one or more NSs based on registration information such as NSSAI and / or S-NSSAI and / or UE usage type and / or one or more NSI IDs and / or APN. It should be noted that the UE usage type is a parameter value included in the UE's registration information for identifying the NSI. The UE usage type can be stored in the HSS. The AMF can select the SMF and UPF based on the UE usage type.

[0123] In addition, S-NSSAI (Single Network Slice Selection Assistance information) is information used to identify NS. S-NSSAI can be composed of only SST (Slice / Servicetype: Slice / Service type), or it can be composed of both SST and SD (Slice Differentiator: Slice Differentiator). Here, SST refers to information indicating the expected actions of NS in terms of functions and services. In addition, SD can be information that interpolates SST when selecting an NSI from multiple NSIs shown in SST. S-NSSAI can be information specific to each PLMN, or it can be standard information common between PLMNs. In addition, the network can store more than one S-NSSAI in the UE's login information as the default S-NSSAI. It should be noted that when the S-NSSAI is the default S-NSSAI, the network can provide the NS related to the UE when the UE does not send a valid S-NSSAI to the network in the login request message.

[0124] In addition, NSSAI (Network Slice Selection Assistance Information) is a collection of S-NSSAI. Each S-NSSAI included in NSSAI is information that assists the access network or core network in selecting NSI. The UE can store the NSSAI allowed by the network for each PLMN. In addition, NSSAI can be information used to select the AMF.

[0125] A tracking area is a single or multiple areas managed by the core network that can be represented by the location information of the UE_A10. A tracking area can be composed of multiple cells. Furthermore, a tracking area can be a range within which control messages such as paging are broadcast, or a range within which the UE_A10 can move without undergoing a handover process. Furthermore, a tracking area can be a routing area or a location area, as long as it is the same area as these areas. Hereinafter, a tracking area may also be referred to as a TA (Tracking Area).

[0126] The TA list 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 login process and / or a tracking area update process 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 login process and / or a tracking area update process. It should be noted that the TA list can also be expressed as a TAI list consisting of one or more TAIs (Tracking area identities). hereinafter, the TAI list may also refer to the TA list. The TA list may also be expressed as a registration area.

[0127] The UE ID is information for identifying the UE. Specifically, for example, the UE ID can be a SUCI (SUbscription Concealed Identifier), a SUPI (Subscription Permanent Identifier), a GUTI (Globally Unique Temporary Identifier), an IMEI (International Mobile Subscriber Identity), an IMEISV (IMEI Software Version), or a TMSI (Temporary Mobile Subscriber Identity). Alternatively, the UE ID can also be other information set within an application or a network. Also, the UE ID can be information for identifying a user.

[0128] The PLMN ID (Public land mobile network Identity) is information for identifying an operator. For example, the PLMN ID can be composed of an MCC (Mobile Country Code) and an MNC (Mobile Network Code). The PLMN in which the UE is logged in can be set as a logged-in PLMN or a RPLMN (Registered PLMN), and a PLMN that the UE considers to be equivalent to the logged-in PLMN at the time of cell selection or handover can be set as an equivalent PLMN or an EPLMN (equivalent PLMN). Note that a list composed of one or more EPLMNs can be set as an EPLMN list or an equivalent PLMN list. The equivalent PLMN list can be transmitted from the network to the UE at the time of a log-in procedure.

[0129] The first timer of this embodiment is a timer for managing the start of a process for session management such as a PDU session establishment process and / or the sending of an SM (Session Management) message such as a PDU session establishment request message, and may also be information indicating the value of a backoff timer for managing the behavior of session management. Hereinafter, the first timer and / or the backoff timer are sometimes referred to as a timer. During the execution of the first timer, each device may be prohibited from starting a process for session management and / or sending and receiving SM messages. It should be noted that the first timer may be set to establish an association with at least one of the congestion management units applied by the NW and / or the congestion management units identified by the UE. For example, it may be set by an APN / DNN unit and / or an identification information unit representing one or more NW slices and / or a rejection reason value unit in the session management process and / or a session unit indicating rejection in the session management process and / or a PTI unit of the session management process.

[0130] It should be noted that SM messages can be NAS messages used in the session management process, or control messages sent and received between UE_A10 and SM132 via AMF140. Furthermore, SM messages include PDU Session Establishment Request messages, PDU Session Establishment Accept messages, PDU Session Complete messages, PDU Session Reject messages, PDU Session Change Request messages, PDU Session Change Accept messages, and PDU Session Change Reject messages. Furthermore, the session management process can include the PDU Session Establishment process, the PDU Session Change process, and the like. Furthermore, during these processes, each message received by UE_A10 may include a backoff timer value. The UE can set the backoff timer received from the NW as the first timer, set the timer value using other methods, or set a random value. Furthermore, if multiple backoff timers are received from the NW, the UE can manage multiple "first timers" corresponding to the multiple backoff timers, or select a timer value from the multiple backoff timer values ​​received from the NW based on a policy maintained by the UE, set it as the first timer, and manage it accordingly. For example, if two backoff timer values ​​are received, the UE sets the backoff timer values ​​received from the NW as "first timer #1" and "first timer #2," respectively, and manages these backoff timers. Alternatively, based on a policy maintained by the UE, the UE may select one backoff timer value from among the multiple backoff timer values ​​received from the NW and set it as the first timer for management.

[0131] When UE_A10 receives multiple backoff timer values ​​from the NW, it can manage multiple "first timers" corresponding to the multiple backoff timers. To distinguish the multiple "first timers" received by UE_A10, they may sometimes be referred to as "first timer #1" or "first timer #2" below. It should be noted that multiple backoff timers can be obtained during a single session management process or during separate, separate session management processes.

[0132] Here, the first timer can be a back-off timer set for multiple associated NW slices based on the information used to identify an NW slice as described above, and used to suppress reconnection, or set in units of a combination of APN / DNN and an NW slice, and used to prevent reconnection, but is not limited to this. It can also be a back-off timer set in units of a combination of APN / DNN and multiple NW slices associated based on the information used to identify an NW slice, and used to suppress reconnection.

[0133] The second timer of this embodiment may be a timer used for the first congestion management. Specifically, the second timer may be a backoff timer associated with the DNN. The second timer may also be T3396 in 3GPP. The second timer may also be the first timer. The UE may enable the first congestion management while the second timer is counting.

[0134] The third timer in this embodiment may be a timer for the third congestion management and / or the fourth congestion management. Specifically, the third timer may be a backoff timer associated with the DNN and / or S-NSSAI. The second timer may also be T3584 in 3GPP. The third timer may also be the first timer. The UE may enable the third congestion management and / or the fourth congestion management while the third timer is counting.

[0135] The fourth timer in this embodiment may be a timer for the second congestion management. Specifically, the fourth timer may be a backoff timer associated with the S-NSSAI. The second timer may also be T3585 in 3GPP. The fourth timer may also be the first timer. The UE may enable the second congestion management while the fourth timer is counting.

[0136] The congestion management of this embodiment is composed of one or more congestion managements from the first congestion management to the fourth congestion management. It should be noted that the control of the UE by the NW can be achieved through the first timer and the congestion management identified by the UE, and the UE can store the association of this information.

[0137] The first congestion management of this embodiment means control signal congestion management with the parameters of DNN as the object. For example, in the NW, when congestion is sensed for DNN#A, the NW can apply the first congestion management when the NW identifies it as a UE-led session management request with only the parameters of DNN#A as the object. It should be noted that even if the UE-led session management request does not include DNN information, the NW can still select the default DNN as the congestion management object under the NW's leadership. Alternatively, even in the case of a UE-led session management request identified by the NW as including DNN#A and S-NSSAI#A, the NW can also apply the first congestion management. When the first congestion management is applied, the UE can suppress the UE-led session management request with only DNN#A as the object.

[0138] In other words, the first congestion management of this embodiment is control signal congestion management targeting DNN, and may be congestion management caused by the congestion state of connectivity to DNN. For example, the first congestion management may be congestion management for limiting connections to DNN#A in all connectivity. Here, the connection to DNN#A in all connectivity may be a connection to DNN#A in connectivity using any S-NSSAI that the UE can utilize, or a connection to DNN#A via a network slice that the UE can connect to. Furthermore, connectivity to DNN#A that does not pass through a network slice may be included. In this embodiment, the first congestion management may be referred to as DNN-based congestion management.

[0139] The second congestion management in this embodiment refers to control signal congestion management targeting S-NSSAI parameters. For example, if the NW detects control signal congestion for S-NSSAI#A and identifies a UE-initiated session management request targeting only S-NSSAI#A parameters, the NW may apply the second congestion management. When the second congestion management is applied, the UE may suppress UE-initiated session management requests targeting only S-NSSAI#A.

[0140] In other words, the second congestion management in this embodiment is control signal congestion management targeting S-NSSAI, and can be congestion management caused by the congestion of the network slice selected based on S-NSSAI. For example, the second congestion management can also be congestion management for limiting all connections based on S-NSSAI#A. In other words, it can also be congestion management for limiting all connections to the DNN via the network slice selected based on S-NSSAI#A. In this embodiment, the second congestion management can also be referred to as S-NSSAI-based congestion management.

[0141] The third congestion management of the present embodiment indicates control signal congestion management targeting parameters of a DNN and an S-NSSAI. For example, in the NW, in a case where control signal congestion to DNN #A and control signal congestion to S-NSSAI #A are sensed at the same time, when the NW identifies that a UE-initiated session management request targeting parameters of DNN #A and S-NSSAI #A, the NW can apply the third congestion management. Note that the NW can select a default DNN as a congestion management object by NW-initiation even in a case where information indicating the DNN is not included in the UE-initiated session management request. In a case where the third congestion management is applied, the UE can suppress the UE-initiated session management request targeting parameters of DNN #A and S-NSSAI #A.

[0142] In other words, the third congestion management of the present embodiment is control signal congestion management targeting parameters of a DNN and an S-NSSAI, and can be congestion management caused by connectivity to the DNN via a network slice selected based on the S-NSSAI being in a congested state. For example, the third congestion management can be congestion management for limiting connections to DNN #A in connectivity based on S-NSSAI #A. In the present embodiment, the third congestion management can also be referred to as congestion management by a combination of an S-NSSAI and a DNN, congestion management targeting a combination of an S-NSSAI and a DNN.

[0143] The fourth congestion management of the present embodiment indicates control signal congestion management targeting at least one parameter of a DNN and / or an S-NSSAI. For example, in the NW, in a case where control signal congestion to DNN #A and control signal congestion to S-NSSAI #A are sensed at the same time, when the NW identifies that a UE-initiated session management request targeting at least one parameter of DNN #A and / or S-NSSAI #A, the NW can apply the fourth congestion management. Note that the NW can select a default DNN as a congestion management object by NW-initiation even in a case where information indicating the DNN is not included in the UE-initiated session management request. In a case where the fourth congestion management is applied, the UE can suppress the UE-initiated session management request targeting at least one parameter of DNN #A and / or S-NSSAI #A. In the present embodiment, the fourth congestion management can also be referred to as congestion management by a combination of an S-NSSAI and a DNN, congestion management targeting a combination of an S-NSSAI and a DNN.

[0144] In other words, the fourth congestion management of the present embodiment is a control signal congestion management that targets parameters of a DNN and an S-NSSAI, and can be a congestion management caused by a congestion state of a network slice selected based on an S-NSSAI and connectivity to a DNN. For example, the fourth congestion management can be a congestion management for limiting all connections based on an S-NSSAI #A, and can be a congestion management for limiting connections to a DNN #A among all connectivity. That is, it can be a congestion management for limiting all connections to a DNN via a network slice selected according to an S-NSSAI #A, and can be a congestion management for limiting connections to a DNN #A among all connectivity. Here, the connections to a DNN #A among all connectivity can be connections of a DNN #A among connectivity using any S-NSSAI available to a UE, or can be connections of a DNN #A via a network slice to which a UE can connect. Also, it can include connectivity to a DNN #A not via a network slice.

[0145] Therefore, the fourth congestion management that targets a DNN #A and an S-NSSAI #A as parameters can be a congestion management that simultaneously performs the first congestion management that targets a DNN #A as a parameter and the second congestion management that targets an S-NSSAI #A as a parameter.

[0146] In addition, a non-public network (NPN) is a non-public network used by a specific user such as a private use by a company or the like for a specific purpose, and is not intended for general use. There are two types of a stand-alone non-public network (SNPN) and a public network integrated NPN in the NPN. Note that the following description as the NPN can mean both the SNPN and the public network integrated NPN.

[0147] The SNPN is operated by an NPN operator, and is not affected by a function unit provided by a PLMN. That is, in other words, the SNPN is an NPN dedicated network independent of a generally public PLMN. The SNPN can be identified by a combination of a PLMN ID and an NID, and the combination of the PLMN ID and the NID can be set as an SNPN identity (SNPN ID). The PLMN ID for the SNPN can be information secured for a private network, and for example, an MCC included in the PLMN ID can be 999. Note that in a case where a UE has logged in to an SNPN, the logged-in SNPN can also be referred to as a logged-in SNPN or an RNPN (registred SNPN).

[0148] The NID (Network identifier) is information that identifies a network. An SNPN can be identified by a combination of a PLMN ID and a NID. The NID can be information that is unique within an SNPN, or information that is unique in the world.

[0149] Further, the public network integrated NPN is implemented using a function section of the PLMN. That is, in other words, the public network integrated NPN is an NPN that is virtually implemented within the PLMN. Moreover, the public network integrated NPN is an NPN that can be generated via the PLMN. The public network integrated NPN can be implemented using, for example, the function of a network slice. Specifically, it can be implemented by using a network slice assigned to the NPN. The public network integrated NPN can be identified by an S-NSSAI, or can be identified by a combination of an S-NSSAI and a CAG ID. Further, the public network integrated NPN can be implemented using, for example, a DN. Specifically, the public network integrated NPN is implemented by using a DN for the NPN.

[0150] Further, the CAG (Closed Access Groups) ID is information that identifies a group of subscribers who are allowed to connect to one or more cells with which the CAG is associated, and the CAG is a group identified by the CAG ID. The CAG is a group that is utilized when the public network integrated NPN is implemented in a network slice. The CAG is used not to attempt access to a network slice assigned to the NPN from a UE that does not allow the NPN. The CAG ID is information that is unique within the PLMN.

[0151] The SNPN enable UE refers to a UE whose setting information includes information indicating that the UE can utilize an SNPN. In other words, the SNPN enable UE can include information indicating that the UE can utilize an SNPN in the setting information of the UE, or the UE can store at least one piece of information related to the SNPN. The SNPN enable UE can support an SNPN access mode. In other words, the SNPN enable UE can operate in the SNPN access mode, or can not operate in the SNPN access mode.

[0152] The UE that operates in the SNPN access mode is a UE that selects only an SNPN at the time of network selection. The UE that operates in the SNPN access mode can also be referred to as an SNPN access mode UE. The SNPN access mode UE is an SNPN enable UE.

[0153] Next, the identification information of the present embodiment will be described.

[0154] The first identification information is a reason value. When the first identification information is included in the PDU session reject message, the first identification information may be information indicating the reason why the network rejected the UE's request or the reason why the network was unable to establish the PDU session. The first identification information may also be the second to fourth identification information.

[0155] The second identification information is information indicating that the network cannot establish a PDU session due to insufficient resources. The second identification information may also be information indicating that DNN-based congestion management is detected and / or that DNN-based congestion management is being performed. Moreover, the second identification information may also be information requesting DNN-based congestion management and / or the start of processing based on the detection of DNN-based congestion management. The second identification information may also be 5G session management reason value #26 (5GSM cause #26 "Insufficient resources: insufficient resources"). The second identification information may also be the first identification information.

[0156] The third identification information is information indicating that the network cannot establish a PDU session due to insufficient resources for a specific network slice and DN. The third identification information may also be information indicating that congestion management performed by a combination of S-NSSAI and DNN is detected and that congestion management performed by a combination of S-NSSAI and DNN is being performed. Moreover, the third identification information may also be information requesting congestion management performed by a combination of S-NSSAI and DNN and / or the start of processing based on the detection of congestion management performed by a combination of S-NSSAI and DNN. The third identification information may also be 5G session management reason value #67 (5GSM cause #67 "Insufficient resources for specific slice and DNN: Insufficient resources for specific slice and DNN"). The third identification information may also be the first identification information.

[0157] The fourth identification information is information indicating that the network cannot establish a PDU session due to insufficient resources for the network slice requested by the UE. The fourth identification information may also be information indicating that S-NSSAI-based congestion management is detected and / or S-NSSAI-based congestion management is being performed. Moreover, the fourth identification information may also be information requesting S-NSSAI-based congestion management and / or the start of processing based on detecting S-NSSAI-based congestion management. The fourth identification information may also be 5GS session management reason #69 (5GSM cause #69 "Insufficient resources for specific slice: Insufficient resources for specific slice"). The fourth identification information may also be the first identification information.

[0158] The fifth identification information may be the value of a backoff timer. Alternatively, the fifth identification information may be information requesting and indicating the minimum duration (interval) until retrying the session management procedure. If the UE is logged into an NPN, the fifth identification information may be the PLMN for the logged-in NPN or a value valid for the logged-in NPN and an equivalent PLMN. The fifth identification information may be associated with at least one of the first to fourth identification information.

[0159] The eleventh identification information is a reason value. When the eleventh identification information is included in the PDU session reject message, the eleventh identification information may be information indicating the reason why the network rejected the UE's request or the reason why the network initiated a network-led PDU session management process. The eleventh identification information may also be the twelfth to fourteenth identification information. The eleventh identification information may be the same as the first identification information.

[0160] The twelfth identification information is information indicating that the network has started a network-led PDU session management process due to insufficient resources. The twelfth identification information may also be information indicating that DNN-based congestion management has been detected and / or that DNN-based congestion management is being performed. Moreover, the twelfth identification information may also be information requesting DNN-based congestion management and / or the start of a process based on detecting DNN-based congestion management. The twelfth identification information may also be 5G session management reason value #26 (5GSM cause #26 "Insufficient resources"). The twelfth identification information may also be the eleventh identification information. The twelfth identification information may be the same as the second identification information.

[0161] The thirteenth identification information is information indicating that the network has started a network-led PDU session management process due to insufficient resources for a specific network slice and DN. The thirteenth identification information may also be information indicating that congestion management performed by a combination of S-NSSAI and DNN has been detected and that congestion management performed by a combination of S-NSSAI and DNN is being performed. Moreover, the thirteenth identification information may also be information requesting congestion management performed by a combination of S-NSSAI and DNN and / or the start of processing based on the detection of congestion management performed by a combination of S-NSSAI and DNN. The thirteenth identification information may also be the 5G session management reason value #67 (5GSM cause #67 "Insufficient resources for specificslice and DNN"). The thirteenth identification information may also be the eleventh identification information. The thirteenth identification information may be the same as the third identification information.

[0162] The fourteenth identification information is information indicating that the network starts a network-initiated PDU session management procedure due to insufficient resources for a network slice requested by the UE. The fourteenth identification information can also be information indicating that congestion management based on S-NSSAI is detected and / or is being performed. Also, the fourteenth identification information can also be information requesting congestion management based on S-NSSAI and / or the start of a process based on detecting congestion management based on S-NSSAI. The fourteenth identification information can be 5GSM cause #69 “Insufficient resources for specific slice”. The fourteenth identification information can also be the eleventh identification information. The fourteenth identification information can be the same as the fourth identification information.

[0163] The fifteenth identification information can be a value of a back-off timer. The fifth identification information can also be information requesting and indicating a minimum period (interval) until the execution of a retry of a session management procedure. In the case where the UE is logged into an NPN, the fifteenth identification information can be a PLMN for the logged-in NPN or a value valid in an equivalent PLMN. The fifteenth identification information can be associated with at least one of the eleventh to fourteenth identification information. The fifteenth identification information can be the same as the fifth identification information.

[0164] The twenty-first identification information is a reason value. In the case where the twenty-first identification information is included in the PDU session change reject message, the twenty-first identification information can be information indicating a reason for the network to reject the UE’s request or a reason for the network to be unable to change the PDU session. The twenty-first identification information can also be the twenty-second to twenty-fourth identification information.

[0165] The twenty-second identification information is information indicating that the network is unable to establish a PDU session and / or is unable to change a PDU session due to insufficient resources. The twenty-second identification information can also be information indicating that congestion management based on DNN is detected and / or is being performed. Also, the twenty-second identification information can also be information requesting congestion management based on DNN and / or the start of a process based on detecting congestion management based on DNN. The twenty-second identification information can be 5GSM cause #26 “Insufficient resources”. The second identification information can also be the twenty-first identification information. The twenty-second identification information can be the same as the second identification information.

[0166] The twenty-third identification information is information indicating that the network cannot establish a PDU session and / or cannot change the PDU session due to insufficient resources for a specific network slice and DN. The twenty-third identification information may also be information indicating that congestion management performed by a combination of S-NSSAI and DNN is detected and that congestion management performed by a combination of S-NSSAI and DNN is being performed. Moreover, the twenty-third identification information may also be information requesting congestion management performed by a combination of S-NSSAI and DNN and / or the start of processing based on the detection of congestion management performed by a combination of S-NSSAI and DNN. The twenty-third identification information may also be 5G session management reason value #67 (5GSM cause #67 "Insufficient resources for specific slice and DNN"). The twenty-third identification information may also be the twenty-first identification information. The twenty-third identification information may be the same as the third identification information.

[0167] The twenty-fourth identification information is information indicating that the network cannot establish a PDU session and / or cannot change the PDU session due to insufficient resources for the network slice requested by the UE. The twenty-fourth identification information may also be information indicating that S-NSSAI-based congestion management is detected and / or that S-NSSAI-based congestion management is being performed. Moreover, the twenty-fourth identification information may also be information requesting S-NSSAI-based congestion management and / or the start of processing based on detecting S-NSSAI-based congestion management. The twenty-fourth identification information may also be 5GS session management reason #69 (5GSM cause #69 "Insufficient resources for specific slice"). The twenty-fourth identification information may also be the twenty-first identification information. The twenty-fourth identification information may be the same as the fourth identification information.

[0168] The twenty-fifth identification information may be the value of the backoff timer. The twenty-fifth identification information may also be information requesting and indicating the minimum period (interval) until the execution of the session management process is retried. When the UE is logged into the NPN, the twenty-fifth identification information may be the PLMN for the logged-in NPN or a value valid in the logged-in NPN and an equivalent PLMN. The twenty-fifth identification information may be associated with at least one of the twenty-first to twenty-fourth identification information. [3. Description of the Process Used in Each Embodiment]

[0169] First, the processes used in each embodiment are described. It should be noted that the processes used in each embodiment include a registration procedure, a network slice-specific authentication and authorization procedure, and a UE configuration update procedure. Each process is described below.

[0170] It should be noted that, in each embodiment, Figure 2 As described in

[15] , the following description takes as an example the case where the HSS and UDM, the PCF and PCRF, the SMF and PGW-C, and the UPF and PGW-U are configured as the same device (that is, the same physical hardware, the same logical hardware, or the same software). However, the contents described in this embodiment can also be applied to the case where they are configured as different devices (that is, different physical hardware, different logical hardware, or different software). For example, data can be sent and received directly between them, data can be sent and received via the N26 interface between the AMF and MME, or data can be sent and received via the UE.

[0171] [3.1. Login process]

[0172] First, use Figure 6 The registration procedure is described. Hereinafter, this process refers to the registration procedure. The registration procedure is a process led by the UE to log in to the access network_B and / or core network_B and / or DN. If it is not logged in to the network, the UE can perform this procedure at any time, such as when the power is turned on. In other words, if it is in a non-registered state (RM-DEREGISTERED state), the UE can start this procedure at any time. In addition, each device (especially the UE and AMF) can transition to the registered state (RM-REGISTERED) based on the completion of the registration procedure.

[0173] It should be noted that this process may be a login process for an NPN, and each device can change the login state (logged-in state or non-logged-in state) of each NPN based on the completion of this process.

[0174] Also, the registration procedure may be a procedure for updating location registration information of the UE in the network and / or periodically notifying the network of the UE's status and / or updating specific parameters related to the UE in the network.

[0175] The UE can start the login process when moving across TAs. In other words, the UE can start the login process when it moves to a TA that is different from the TA shown in the maintained TA list (or registration area). Moreover, the UE can also start this process when the executing timer expires. Moreover, the UE can also start the login process when the context of each device needs to be updated because the PDU session is disconnected or disabled. Moreover, the UE can also start the login process when the capability information and / or preference selection related to the UE's PDU session establishment changes. Moreover, the UE can also start the login process periodically. Moreover, the UE can start the login process based on the completion of the UE setting update process or based on the completion of the login process or based on the completion of the PDU session establishment process or based on the completion of the PDU session management process or based on the information received from the network in each process. It should be noted that the UE can perform the login process at any timing and is not limited to this.

[0176] It should be noted that the above-mentioned process for the UE to transition from a state that has not logged into the network to a state that has logged into the network can be set as an initial registration procedure, and the registration procedure performed by the UE when it is logged into the network can be set as a registration procedure for mobility and periodic registration update.

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

[0178] Here, the UE can include information indicating a request for connection to the NPN in a login request message and / or an RRC message and send the information. Here, the information indicating a request for connection to the NPN can be an SNPN ID, an S-NSSAI for the NPN, a DNN for the NPN, a CAG ID, or a combination thereof.

[0179] It should be noted that the UE can select, determine whether to send the information indicating the request for connection to the NPN to the network based on the capability information of the UE and / or the UE policy and / or the state of the UE and / or the login information of the user and / or the context maintained by the UE, etc.

[0180] Specifically, the UE can send the information indicating the request for connection to the NPN to the network in the case of supporting the function of connecting to the NPN and / or in the case of being a valid UE for the SNPN and / or in the case of being a UE in the SNPN access mode.

[0181] The UE can also include information other than the information indicating the request for connection to the NPN in the login request message and / or the RRC message including the login request message, for example, the UE ID can be sent. It should be noted that in the case where the UE sends the information indicating the request for connection to the NPN to the network, the UE ID can be the UE ID for the NPN.

[0182] In addition, the UE can send the PDU session establishment process in the login process by including the SM message (such as the PDU session establishment request message) in the login request message, or sending the SM message (such as the PDU session establishment request message) together with the login request message.

[0183] The 5G AN (or gNB) selects the AMF that transmits the login request message when receiving the RRC message including the login request message (S602). It should be noted that the 5G AN (or gNB) can select the AMF based on one or more identification information included in the login request message and / or the RRC message including the login request message. Specifically, the 5G AN (or gNB) can select the AMF of the transmission destination of the login request message based on at least one identification information in the information indicating the request for connection to the NPN.

[0184] For example, the 5G AN (or gNB) can select the AMF based on the PLMN ID included in the SNPN ID, can select the AMF based on the SNPN ID, can select the AMF based on the S-NSSAI, and can select the AMF based on the DNN.

[0185] Note that the selection method of the AMF is not limited to this, and the 5G AN (or gNB) can select the AMF based on a condition other than this. The 5G AN (or gNB) extracts the log-in request message from the received RRC message and transmits the log-in request message to the selected AMF (S604). Note that, in a case where the information indicating the request for connection to the NPN is not included in the log-in request message but is included in the RRC message, the identification information included in the RRC message is transmitted to the selected AMF together with the log-in request message (S604).

[0186] The AMF performs processing #1 within the core network upon receiving the log-in request message (S606). The processing #1 within the core network can be, for example, execution of first condition determination, generation of a UE context, an authentication procedure, or a combination of these.

[0187] The first condition determination is used to determine whether the network (or the AMF) accepts the request of the UE. Each device performs the (A) procedure in a case where the first condition determination is true. On the other hand, each device can skip the (A) procedure and perform the (B) procedure in a case where the first condition determination is false.

[0188] Note that the first condition determination can be performed based on reception of the log-in request message and / or each identification information and / or subscriber information and / or capability information of the network and / or operator policy and / or state of the network and / or user's log-in information and / or context held by the AMF, and the like included in the log-in request message.

[0189] For example, the first condition determination can be true in a case where the network allows the request of the UE, and the first condition determination can be false in a case where the network does not allow the request of the UE. In addition, the first condition determination can be true in a case where the network and / or device within the network of the login destination of the UE supports the function requested by the UE, and the first condition determination can be false in a case where the function requested by the UE is not supported. Also, the first condition determination can be true in a case where the identification information of the transceiver is allowed, and the first condition determination can be false in a case where the identification information of the transceiver is not allowed.

[0190] First, the (A) procedure of the present procedure is described. In a case where the AMF determines acceptance of the log-in request of the UE, the AMF transmits a log-in acceptance message to the UE based on the determination (S610).

[0191] The AMF can include information indicating that connection to the NPN has been allowed to the UE in the login acceptance message and / or an RRC message including the login acceptance message. The information indicating that connection to the NPN has been allowed can be an SNPN ID, can be an S-NSSAI for the NPN, can be a DNN for the NPN, can be a CAG ID, or can be a combination of these.

[0192] Note that the AMF can select and determine the identification information included in the login acceptance message based on the received respective identification information and / or subscriber information and / or network capability information and / or operator policy and / or network status and / or user login information and / or context maintained by the AMF, and the like.

[0193] Further, the AMF can include an SM message (e.g., a PDU session establishment acceptance message) in the login acceptance message and transmit the same, or transmit the SM message (e.g., a PDU session establishment acceptance message) together with the login acceptance message. However, this transmission method can also be performed in a case where the SM message (e.g., a PDU session establishment request message) is included in the login request message. Further, in this transmission method, it can also be performed in a case where the SM message (e.g., a PDU session establishment request message) is included together with the login request message. The AMF can indicate that the procedure for the SM is accepted in the login procedure by performing such a transmission method.

[0194] Further, the AMF can indicate that the UE's request is accepted by transmitting the login acceptance message based on the received respective identification information and / or subscriber information and / or network capability information and / or operator policy and / or network status and / or user login information and / or context maintained by the AMF, and the like.

[0195] The UE receives the login acceptance message via the 5G AN (gNB) (S610). The UE can identify that the UE's request based on the login request message is accepted and the contents of the respective identification information included in the login acceptance message by receiving the login acceptance message.

[0196] The UE can further transmit a login completion message to the AMF as a response message to the login acceptance message via the 5G AN (gNB) (S612). Note that the UE can transmit a PDU session establishment completion message or the like as an SM message included in the login completion message in a case where a PDU session establishment acceptance message or the like is received as an SM message, or can indicate completion of the procedure for the SM by including the SM message. Here, the login completion message is a NAS message exchanged on the N1 interface, but is exchanged in an RRC message between the UE and the 5G AN (gNB).

[0197] The AMF receives the login completion message (S612) via the 5G AN (gNB). In addition, each device completes the (A) process and the login process in this process based on the transmission and reception of the login acceptance message and / or the login completion message.

[0198] Next, the case where the first condition is false is described. The AMF sends a Registration Reject message to the UE via the 5G AN (gNB) as a response to the Registration Request message (S614). Here, the Registration Reject message is a NAS message sent and received over the N1 interface, but is included in RRC messages sent and received between the UE and the 5G AN (gNB).

[0199] It should be noted that the AMF can also indicate that the UE's request based on the login request message is rejected by sending a login reject message.

[0200] It should be noted that the various processes performed by the UE based on the reception of each identification information as described above can be performed during this process or after the completion of this process, or can be performed based on the completion of this process after the completion of this process. The UE receives a login rejection message via the 5G AN (gNB). By receiving the login rejection message, the UE can identify that the UE's request based on the login request message has been rejected and the contents of the various identification information included in the login rejection message. In addition, the UE can also identify that the UE's request has been rejected if it has not received a login acceptance message or a login rejection message within a specified period after sending the login request message. Each device can complete the login process based on the sending and receiving of the login rejection message.

[0201] It should be noted that each device can transition to or maintain a state in which the UE is logged into the network (RM_REGISTERED state or 5GMM-REGISTERED state) based on the transmission and reception of a login acceptance message and / or a login completion message, and can also transition to or maintain a state in which the UE is not logged into the network (RM_DEREGISTERED state or 5GMM-DEREGISTERED state) based on the transmission and reception of a login rejection message. In addition, the transition of each device to each state can be based on the completion of the login process.

[0202] Furthermore, upon completion of the login process, each device may perform processing based on the information sent and received during the login process. For example, when information indicating that a portion of the UE's request was rejected is sent or received, the reason for the UE's request rejection can be identified. Furthermore, each device may re-implement this process based on the reason for the UE's request rejection, or may perform the login process for Core Network_A or other cells.

[0203] Further, the UE can store the identification information received with the login accept message and / or the login reject message based on completion of the login procedure, and can identify the determination of the network.

[0204] Further, each apparatus can also start a PDU session establishment procedure to the NPN based on completion of the login procedure. Note that details of the PDU session establishment procedure are described later.

[0205] [3.2. PDU Session Establishment Procedure]

[0206] Next, a summary of the PDU session establishment procedure performed for establishing a PDU session is described. Hereinafter, the PDU session establishment procedure is also referred to as the present procedure. The present procedure is a procedure performed by each apparatus for establishing a PDU session. Note that each apparatus can execute the present procedure in a state where the login procedure is completed, or can execute the present procedure in the login procedure. In addition, each apparatus can start the present procedure in a login state, or can start the present procedure at an arbitrary timing after the login procedure. Further, the UE can start the present procedure when counting of at least one of the first to fourth timers in execution is expired. In addition, each apparatus can establish a PDU session based on completion of the PDU session establishment procedure. Further, each apparatus can establish a plurality of PDU sessions by executing the present procedure a plurality of times.

[0207] Note that the present procedure can be a PDU session establishment procedure to the NPN, and each apparatus can establish a PDU session to the NPN based on completion of the present procedure.

[0208] Using Figure 7 An example of steps of executing the PDU session establishment procedure is described. Hereinafter, each step of the present procedure is described. First, the UE_A 10 starts the PDU session establishment procedure by transmitting a PDU session establishment request message (S700) to the core network_B via the access network_B.

[0209] Specifically, the UE_A 10 transmits the PDU session establishment request message (S700) to the AMF 140 in the core network_B 190 via the NR node_A 122 using the N1 interface.

[0210] Here, the UE_A 10 can include information indicating the NPN in the PDU session establishment request message, and can indicate that the UE_A 10 requests to connect to the NPN by including information indicating the NPN. Note that the information indicating the NPN can be an SNPN ID, can be an S-NSSAI for the NPN, can be a DNN for the NPN, can be a CAG ID, or can be a combination of these. Note that two or more of these identification information can be constituted as one or more identification information, or one identification information can be constituted by two or more identification information.

[0211] The AMF receives the PDU session establishment request message and performs third condition determination. The third condition determination is for determining whether the AMF accepts the request of the UE_A 10. The core network_B starts processing #2 within the core network in the case where the third condition determination is true (S702), and starts the process (B) in the process in the case where the third condition determination is false. Note that the steps in the case where the third condition determination is false are described later. Here, the processing #2 within the core network can be an SMF selection by the AMF within the core network_B 190 and / or transmission and reception of the PDU session establishment request message between the AMF and the SMF.

[0212] The core network_B 190 starts the processing #2 within the core network. In the processing #2 within the core network, the AMF 140 can select the SMF 132 as the NF of the routing destination of the PDU session establishment request message, and transmit or transfer the PDU session establishment request message to the selected SMF 132 using the N11 interface. Here, the AMF 140 can select the SMF 132 of the routing destination based on the information included in the PDU session establishment request message. In more detail, the AMF 140 can select the SMF 132 of the routing destination in accordance with each identification information and / or subscriber information and / or capability information of the network and / or operator policy and / or network state and / or context held by the AMF 140, which are acquired based on the reception of the PDU session establishment request message.

[0213] Note that the PDU session establishment request message can be a NAS message. In addition, the PDU session establishment request message can be a message requesting establishment of a PDU session, and is not limited thereto.

[0214] The SMF 132 in the core network_B 190 receives the PDU session establishment request message and performs third condition discrimination. The third condition discrimination is for determining whether the SMF 132 accepts the request of the UE_A 10. In the third condition discrimination, the SMF 132 determines whether the third condition discrimination is true or false. The SMF 132 starts the process of (A) in the present process in a case where the third condition discrimination is true, and starts the process of (B) in the present process in a case where the third condition discrimination is false. Note that the steps in the case where the third condition discrimination is false are described later.

[0215] Hereinafter, the steps in the case where the third condition discrimination is true, that is, the process of (A) in the present process, are described. The SMF 132 selects the UPF 130 of the establishment destination of the PDU session to perform eleventh condition discrimination.

[0216] Here, the eleventh condition discrimination is for determining whether each device performs processing #3 in the core network. Here, the processing #3 in the core network can include the start and / or execution of the PDU session establishment authentication process by each device and / or the transmission and / or reception of a Session Establishment request message between the SMF and the UPF in the core network_B 190, and / or the transmission and / or reception of a Session Establishment response message, and the like (S704). In the eleventh condition discrimination, the SMF 132 determines whether the eleventh condition discrimination is true or false. The SMF 132 starts the PDU session establishment authentication authorization process in a case where the eleventh condition discrimination is true, and omits the PDU session establishment authentication authorization process in a case where the eleventh condition discrimination is false. Note that the details of the PDU session establishment authentication authorization process of the processing #2 in the core network are described later.

[0217] Next, the SMF 132 transmits a Session Establishment request message to the selected UPF 130 and starts the process of (A) in the present process on the basis of the eleventh condition discrimination and / or the completion of the PDU session establishment authentication authorization process. Note that the SMF 132 can start the process of (B) in the present process on the basis of the completion of the PDU session establishment authentication authorization process, without starting the process of (A) in the present process.

[0218] Here, the SMF 132 can select one or more UPFs 130 on the basis of each identification information and / or the capability information of the network and / or the subscriber information and / or the operator policy and / or the network state and / or the context that the SMF 132 has held, which are acquired on the basis of the reception of the PDU session establishment request message. Note that in a case where a plurality of UPFs 130 are selected, the SMF 132 can transmit a Session Establishment request message to each UPF 130.

[0219] UPF 130 receives the session establishment request message and generates a context for the PDU session. Furthermore, based on receiving the session establishment request message and / or generating the context for the PDU session, UPF 130 sends a session establishment response message to SMF 132. Furthermore, SMF 132 receives the session establishment response message. It should be noted that the session establishment request message and the session establishment response message may be control messages sent and received over the N4 interface. Furthermore, the session establishment response message may be a response message to the session establishment request message.

[0220] Furthermore, SMF132 may allocate the address allocated to UE_A10 based on the receipt of the PDU session establishment request message and / or the selection of UPF130 and / or the receipt of the session establishment response message. It should be noted that SMF132 may allocate the address allocated to UE_A10 during the PDU session establishment process or after the PDU session establishment process is completed.

[0221] Specifically, SMF132 can perform address allocation during the PDU session establishment process without using DHCPv4 to allocate IPv4 addresses, and can also send the allocated addresses to UE_A10. Furthermore, SMF132 can perform address allocation after the PDU session establishment process when using DHCPv4 or DHCPv6 or SLAAC (Stateless Address Autoconfiguration) to allocate IPv4 addresses and / or IPv6 addresses and / or IPv6 prefixes, and can also send the allocated addresses to UE_A10. It should be noted that the address allocation implemented by SMF132 is not limited to this.

[0222] Moreover, SMF132 can also include the allocated address in the PDU session establishment acceptance message and send it to UE_A10 based on the completion of the address allocation of the address allocated to UE_A10, or it can send it to UE_A10 after completing the PDU session establishment process.

[0223] Based on the reception of the PDU session establishment request message and / or the selection of UPF130 and / or the reception of the session establishment response message and / or the completion of the address allocation of the address allocated to UE_A10, SMF132 sends a PDU session establishment accept message (S706) to UE_A10 via AMF140.

[0224] Specifically, the SMF 132 transmits the PDU session establishment accept message to the AMF 140 using the N11 interface, and the AMF 140 that has received the PDU session establishment accept message transmits the PDU session establishment accept message to the UE_A 10 using the N1 interface.

[0225] Note that, in a case where the PDU session is a PDN connection, the PDU session establishment accept message can be a PDN connectivity accept message. Also, the PDU session establishment accept message can be a NAS message that is transmitted and received on the N11 interface and the N1 interface. Further, the PDU session establishment accept message is not limited to this, and can be a message indicating that the establishment of the PDU session is accepted.

[0226] The UE_A 10 receives the PDU session establishment accept message from the SMF 132. The UE_A 10 identifies the contents of various pieces of identification information included in the PDU session establishment accept message by receiving the PDU session establishment accept message.

[0227] Next, the UE_A 10 transmits a PDU session establishment complete message to the SMF 132 via the AMF 140 based on the completion of the reception of the PDU session establishment accept message (S708). Also, the SMF 132 receives the PDU session establishment complete message and performs second condition discrimination.

[0228] Specifically, the UE_A 10 transmits the PDU session establishment complete message to the AMF 140 using the N1 interface, and the AMF 140 that has received the PDU session establishment complete message transmits the PDU session establishment complete message to the SMF 132 using the N11 interface.

[0229] Note that, in a case where the PDU session is a PDN connection, the PDU session establishment complete message can be a PDN connectivity complete message, or an Activate default EPS bearer context accept message. Also, the PDU session establishment complete message can be a NAS message that is transmitted and received on the N1 interface and the N11 interface. Further, the PDU session establishment complete message can be a response message to the PDU session establishment accept message, but is not limited to this, and can be a message indicating the completion of the PDU session establishment procedure.

[0230] The second conditional judgment allows SMF 132 to determine the type of message being sent or received on the N4 interface. If the second conditional judgment is true, process #4 within the core network can be initiated (S710). Process #4 within the core network may include, for example, sending and receiving a Session Modification Request message and / or a Session Modification Response message. SMF 132 sends a Session Modification Request message to UPF 130 and then receives a Session Modification Accept message from UPF 130 upon receiving the Session Modification Request message. Furthermore, if the second conditional judgment is false, SMF 132 executes process #2 within the core network. Specifically, the SMF sends a Session Establishment Request message to UPF 130 and then receives a Session Establishment Accept message from UPF 130 upon receiving the Session Establishment Request message.

[0231] Each device completes process (A) in this process by sending and receiving a PDU session establishment completion message and / or a session change response message and / or a session establishment response message and / or a RA (Router Advertisement).

[0232] Next, the steps for the case where the third condition is judged to be false, that is, the steps of process (B) in this process are described. SMF 132 sends a PDU session establishment reject message to UE_A 10 via AMF 140 (S712), starting process (B) in this process.

[0233] Specifically, SMF132 uses the N11 interface to send a PDU session establishment rejection message to AMF140, and AMF140, which receives the PDU session establishment request message, uses the N1 interface to send a PDU session establishment rejection message to UE_A10.

[0234] It should be noted that, when the PDU session is a PDN connection, the PDU session establishment reject message may be a PDN connectivity reject message. Furthermore, the PDU session establishment reject message may be a NAS message sent and received on the N11 interface and the N1 interface. In addition, the PDU session establishment reject message is not limited thereto and may also be a message indicating that the establishment of the PDU session is rejected.

[0235] Here, the SMF 132 can include one or more of the first to fifth identification information in the PDU session establishment rejection message, and can indicate that the request of the UE_A 10 is rejected by including the identification information. Note that two or more of the identification information can be constituted as one or more identification information.

[0236] Further, the SMF 132 can indicate that the establishment of the PDU session for the NPN is rejected by transmitting the PDU session establishment rejection message including the first identification information and / or the second identification information and / or the third identification information and / or the fourth identification information and / or the fifth identification information, and can indicate that the establishment of the PDU session to the NPN is not allowed.

[0237] More specifically, the SMF 132 can indicate that the establishment of the PDU session for the NPN is rejected due to the fact that the core network is performing congestion management based on the DNN by transmitting the first identification information and / or the second identification information and / or the fifth identification information, can request the start of the congestion management based on the DNN, and can request the start of the timer using the value indicated by the fifth identification information.

[0238] Alternatively, the SMF 132 can indicate that the establishment of the PDU session for the NPN is rejected due to the fact that the core network is performing congestion management by the combination of the S-NSSAI and the DNN by transmitting the first identification information and / or the third identification information and / or the fifth identification information, can request the start of the congestion management by the combination of the S-NSSAI and the DNN, and can request the start of the timer using the value indicated by the fifth identification information.

[0239] Further, the SMF 132 can indicate that the establishment of the PDU session for the NPN is rejected due to the fact that the core network is performing congestion management based on the S-NSSAI by transmitting the first identification information and / or the fourth identification information and / or the fifth identification information, can request the start of the congestion management based on the S-NSSAI, and can request the start of the timer using the value indicated by the fifth identification information.

[0240] Further, the SMF 132 can transmit two or more of the first to fifth identification information in combination, and can make a request in combination of the above matters. Note that the matters indicated by the SMF 132 by transmitting each identification information can not be limited to these.

[0241] Moreover, SMF132 may also include identification information other than the first to fifth identification information in the PDU session establishment rejection message. For example, SMF132 may include information indicating the NPN in the PDU session establishment rejection message. It should be noted that, here, the information indicating the NPN may be the SNPN ID, the S-NSSAI for the NPN, the DNN for the NPN, the CAG ID, or a combination of these. It should be noted that the information indicating the NPN included in the PDU session establishment rejection message may also be the information indicating the NPN received from the UE.

[0242] As described above, the core network_B190 may notify UE_A10 of the congestion management applied by sending a PDU session establishment reject message. It should be noted that, thereby, the core network_B190 may notify UE_A10 of the application of congestion management and / or instruct UE_A10 to perform congestion management and / or information identifying the type of congestion management applied and / or information identifying the object of congestion management, such as the DNN and / or S-NSSAI, corresponding to the applied congestion management and / or the value of a timer corresponding to the applied congestion management.

[0243] It should be noted that core network_B can determine the identification information included in the PDU session establishment rejection message based on the received identification information and / or network capability information and / or operator policy and / or network status.

[0244] For example, the core network_B190 may not perform at least one of the first to fourth congestion management processes for the UE and / or the combination of the UE and the NPN when the UE is logged in to the NPN and / or the UE requests to be connected to the NPN and / or the UE is in a state of being connected to the NPN, and may also manage the UE and / or the combination of the UE and the NPN as excluded objects from the first to fourth congestion management.

[0245] Moreover, in the case where the core network_B190 does not perform at least one of the first to fourth congestion management processes for the UE and / or the combination of the UE and the NPN and / or manages the UE and / or the combination of the UE and the NPN as excluded objects from the first to fourth congestion management, the SMF132 may not include at least one of the first to fifth identification information in the PDU session establishment reject message.

[0246] Specifically, for example, in a case where the core network_B 190 is in a state where the first congestion management is not performed for the UE and / or the combination of the UE and the NPN and / or manages the UE and / or the combination of the UE and the NPN as an exclusion target of the first congestion management, the SMF 132 can not include the first identification information and / or the second identification information and / or the fifth identification information in the PDU session establishment reject message.

[0247] Likewise, for example, in a case where the core network_B 190 is in a state where the second congestion management is not performed for the UE and / or the combination of the UE and the NPN and / or manages the UE and / or the combination of the UE and the NPN as an exclusion target of the second congestion management, the SMF 132 can not include the first identification information and / or the fourth identification information and / or the fifth identification information in the PDU session establishment reject message.

[0248] Likewise, for example, in a case where the core network_B 190 is in a state where the third congestion management is not performed for the UE and / or the combination of the UE and the NPN and / or manages the UE and / or the combination of the UE and the NPN as an exclusion target of the third congestion management, the SMF 132 can not include the first identification information and / or the third identification information and / or the fifth identification information in the PDU session establishment reject message.

[0249] Likewise, for example, in a case where the core network_B 190 is in a state where the fourth congestion management is not performed for the UE and / or the combination of the UE and the NPN and / or manages the UE and / or the combination of the UE and the NPN as an exclusion target of the fourth congestion management, the SMF 132 can not include the first identification information and / or the second identification information and / or the third identification information and / or the fourth identification information and / or the fifth identification information in the PDU session establishment reject message.

[0250] In other words, in a case where the UE is in a state where the login to the NPN is performed and / or information indicating the NPN is received from the UE and / or the UE is in a state where the connection to the NPN is made, the SMF 132 can not include at least one of the first to fourth identification information in the PDU session establishment reject message.

[0251] One or more of the first to fifth identification information can be included in the PDU session establishment reject message received by the UE_A 10 from the SMF 132.

[0252] Next, the UE_A 10 implements the fifth processing based on the reception of the PDU session establishment reject message (S714). Further, the UE_A 10 can also implement the fifth processing based on the completion of the present process.

[0253] Next, a first example of the fifth processing will be described.

[0254] Here, the fifth processing can be processing in which the UE_A 10 disregards the matter indicated by the SMF 132. Also, the fifth processing can be processing in which the UE_A 10 recognizes that the request of the present procedure is rejected.

[0255] Specifically, in the fifth processing, it can be that, in a case where the UE_A 10 receives the first identification information and / or the second identification information and / or the fifth identification information from the core network_B 190, the UE_A 10, based on a state in which the UE_A 10 is logged into the NPN and / or a state in which the UE_A 10 is connected to the NPN and / or a state in which the UE_A 10 transmits information indicating the NPN to the network, disregards the information and the request indicated by the first identification information and / or the second identification information and / or the fifth identification information, and does not perform the first congestion management.

[0256] Also, in the fifth processing, it can be that, in a case where the UE_A 10 receives the first identification information and / or the third identification information and / or the fifth identification information from the core network_B 190, the UE_A 10, based on a state in which the UE_A 10 is logged into the NPN and / or a state in which the UE_A 10 is connected to the NPN and / or a state in which the UE_A 10 transmits information indicating the NPN to the network, disregards the information and the request indicated by the first identification information and / or the third identification information and / or the fifth identification information, and does not perform the third congestion management and / or the fourth congestion management.

[0257] Also, in the fifth processing, it can be that, in a case where the UE_A 10 receives the first identification information and / or the fourth identification information and / or the fifth identification information from the core network_B 190, the UE_A 10, based on a state in which the UE_A 10 is logged into the NPN and / or a state in which the UE_A 10 is connected to the NPN and / or a state in which the UE_A 10 transmits information indicating the NPN to the network, disregards the information and the request indicated by the first identification information and / or the fourth identification information and / or the fifth identification information, and does not perform the second congestion management.

[0258] Here, the fifth processing can be processing in which the UE_A 10 recognizes the matter indicated by the SMF 132. Also, the fifth processing can be processing in which the UE_A 10 stores the received identification information as a context, and can be processing in which the UE_A 10 transfers the received identification information to an upper layer and / or a lower layer. Also, the fifth processing can be processing in which the UE_A 10 recognizes that the request of the present procedure is rejected.

[0259] Note that the UE_A 10 can retransmit the rejected request and retry the PDU session establishment procedure based on completion of the fifth processing.

[0260] Next, a second example of the fifth processing will be described.

[0261] Here, the fifth processing can be processing in which the UE_A 10 identifies the matter indicated by the SMF 132. Also, the fifth processing can be processing in which the UE_A 10 stores the received identification information as context, and can be processing in which the UE_A 10 transmits the received identification information to an upper layer and / or a lower layer.

[0262] Also, in the fifth processing, the processing of identifying the congestion management to be applied can be performed on the basis of one or more of the first to fifth identification information.

[0263] Also, in the fifth processing, the processing of identifying which one of the first to fourth congestion management categories is applied and the processing of identifying the DNN and / or the S-NSSAI corresponding to the applied congestion management can be performed on the basis of one or more of the first to fifth identification information.

[0264] Also, in the fifth processing, the value of the setting of at least one of the first to fourth timers shown in the fifth identification information corresponding to the applied congestion management can be identified and set on the basis of one or more of the first to fifth identification information, and the counting of the set timer can be started.

[0265] Specifically, in the fifth processing, in a case where the UE_A 10 receives the first identification information and / or the second identification information and / or the fifth identification information from the core network_B 190, the UE_A 10 can set the value shown in the fifth identification information to the second timer on the basis of the state of the UE_A 10 logged into the NPN and / or the state of the UE_A 10 connected to the NPN, and start the second timer. At this time, in the fifth processing, the UE_A 10 can also manage the second timer as a timer valid for the RPLMN and the EPLMN. In other words, the UE_A 10 logged into the NPN and / or connected to the NPN can transition to a state in which the transmission of the allow SM message is allowed in a case where the counting of the second timer is performed in a state in which the UE_A 10 is logged into a PLMN different from the RPLMN or the EPLMN, and can transition to a state in which the start of the PDU session establishment procedure and / or the start of the PDU session management procedure is allowed.

[0266] Moreover, in the fifth process, when UE_A10 receives the first identification information and / or the second identification information and / or the fifth identification information from the core network_B190, and when UE_A10 is not logged in to the NPN, UE_A10 also sets the value indicated by the fifth identification information to the second timer and starts the second timer. At this time, in the fifth process, UE_A10 can also manage the second timer as a timer valid for all PLMNs. In other words, UE_A10 that is not logged in to the NPN and / or is not connected to the NPN can maintain the second timer even if a change occurs in the PLMN of the login destination during the execution of the second timer counting, can maintain a state in which the sending of SM messages is not allowed, and can maintain a state in which the start of the PDU session establishment process and / or the start of the PDU session management process is not allowed.

[0267] Furthermore, in the fifth process, when UE_A10 receives the first identification information, the third identification information, and / or the fifth identification information from core network_B190, UE_A10 may set the value indicated by the fifth identification information to the third timer based on the state of UE_A10 being logged into and / or connected to the NPN, and start the third timer. In this case, in the fifth process, UE_A10 may also manage the third timer as a timer valid for the RPLMN. In other words, UE_A10 logged into and / or connected to the NPN may transition to a state that allows the sending of SM messages when logged into a PLMN different from the RPLMN and / or an NPN different from the RNPN, or may transition to a state that allows the initiation of the PDU session establishment procedure and / or the initiation of the PDU session management procedure when logged into a PLMN different from the RPLMN and / or logged into an NPN different from the RNPN.

[0268] Furthermore, in the fifth process, when UE_A10 receives the first identification information and / or the fourth identification information and / or the fifth identification information from core network_B190, UE_A10 may set the value indicated by the fifth identification information to the fourth timer based on the state of UE_A10 being logged into and / or connected to the NPN, and start the fourth timer. In this case, in the fifth process, UE_A10 may also manage the fourth timer as a timer valid for the RPLMN. In other words, UE_A10 logged into and / or connected to the NPN may transition to a state that allows the sending of SM messages when logged into a PLMN different from the RPLMN and / or an NPN different from the RNPN, and may also transition to a state that allows the initiation of the PDU session establishment process and / or the initiation of the PDU session management process.

[0269] Further, the fifth processing can also be processing in which the UE_A 10 starts the process again after a certain period, or processing in which a request for a state transition of the UE_A 10 is limited or restricted.

[0270] Further, the fifth processing can also be processing in which the UE_A 10 starts the process again after a certain period, or processing in which a request for a state transition of the UE_A 10 is limited or restricted.

[0271] Further, the UE_A 10 can recognize that the request of the UE_A 10 is rejected by receiving the PDU session establishment reject message, or by not receiving the PDU session establishment reject message. Each device completes the process (B) in the process based on the reception and transmission of the PDU session establishment reject message.

[0272] Each device completes the process based on the completion of the process (A) or (B) in the process. Note that each device can transition to a state in which the PDU session is established based on the completion of the process (A) in the process, can recognize that the process is rejected based on the completion of the process (B) in the process, and can also transition to a state in which the PDU session is not established.

[0273] Further, each device can implement processing based on the identification information exchanged in the process based on the completion of the process. In other words, the UE_A 10 can implement the fifth processing based on the completion of the process.

[0274] Further, the third condition discrimination can be performed based on the identification information and / or the subscriber information and / or the operator policy included in the PDU session establishment request message. For example, the third condition discrimination can be true in a case where the network allows the request of the UE_A 10. Further, the third condition discrimination can be false in a case where the network does not allow the request of the UE_A 10. Further, the third condition discrimination can be true in a case where the network and / or the device within the network of the connection destination of the UE_A 10 supports the function requested by the UE_A 10, and can be false in a case where it does not support the function. Further, the third condition discrimination can be true in a case where it is determined that the network is in a congested state, and can be false in a case where it is determined that the network is in a non-congested state. Note that the conditions that determine the true or false of the third condition discrimination are not limited to the above conditions.

[0275] Further, the second condition discrimination can be performed based on whether a session on an N4 interface for the PDU session is established. For example, the second condition discrimination can be true in a case where a session on an N4 interface for the PDU session is established, and can be false in a case where it is not established. Note that the conditions that determine the true or false of the second condition discrimination are not limited to the above conditions.

[0276] Further, the eleventh condition determination can be based on the identification information and / or the subscriber information and / or the operator policy included in the PDU session establishment request message. For example, the eleventh condition determination can be true in a case where the network allows implementation of the DN_A6-based authentication and / or authorization in the present procedure. Further, the eleventh condition determination can be false in a case where the network does not allow implementation of the DN_A6-based authentication and / or authorization in the present procedure. Also, the eleventh condition determination can be true in a case where the network and / or the device within the network of the connection destination of the UE_A10 supports implementation of the DN_A6-based authentication and / or authorization in the present procedure, and can be false in a case where the network and / or the device within the network of the connection destination of the UE_A10 does not support implementation of the DN_A6-based authentication and / or authorization in the present procedure. Also, the eleventh condition determination can be true in a case where the sixty-first identification information is received, and can be false in a case where the sixty-first identification information is not received. In other words, the eleventh condition determination can be true in a case where a container including the SM PDU DN Request Container and / or a plurality of information and / or the like is received, and can be false in a case where the container is not received. Note that the conditions for determining the true or false of the eleventh condition determination are not limited to the above conditions.

[0277] Through the reception and transmission of the PDU session establishment reject message in the above procedure, the core network_B 190 notifies the UE_A 10 of the applied congestion management, and the UE_A 10 can apply the congestion management indicated by the core network_B 190 or can ignore the congestion management indicated by the core network_B 190. Note that the core network_B 190 and the UE_A 10 can apply a plurality of congestion managements by performing the procedure and the processing explained in the present procedure a plurality of times. Note that the applied congestion managements can be different congestion management categories and / or congestion managements corresponding to different DNNs and / or congestion managements corresponding to different S-NSSAIs and / or congestion managements different in a combination of DNNs and S-NSSAIs.

[0278] [3.3. Network-Dominated PDU Session Management Procedure]

[0279] Next, a summary of the network-dominated session management procedure is explained. Hereinafter, the network-dominated session management procedure is also referred to as the present procedure. The present procedure is a procedure for session management performed by the network with respect to an already established PDU session. Note that the present procedure can be performed at any timing after the above-described registration procedure and / or the PDU session establishment procedure are completed and each device transitions to a state in which at least one PDU session is established. Further, each device can transmit and receive a message including identification information for stopping or changing the congestion management in the present procedure, or can start a behavior based on a new congestion management indicated by the network based on completion of the present procedure.

[0280] Note that the present procedure can be a network-initiated PDU session modification procedure and / or a network-initiated PDU session release procedure, and the like, and can also perform a network-initiated session management procedure not limited to these. Note that each device can transmit and receive a PDU session modification message in the network-initiated PDU session modification procedure, and can transmit and receive a PDU session release message in the network-initiated PDU session release procedure.

[0281] Using Figure 8 Examples of the network-initiated session management procedure are described. In this chapter, the present procedure refers to the network-initiated session management procedure. Hereinafter, each step of the present procedure is described.

[0282] As described above, each device in the UE_A 10 and the core network_B 190 in which at least one PDU session is established based on the completion of the login procedure and / or the PDU session establishment procedure starts the network-initiated session management procedure at any timing. Here, the device in the core network_B 190 that starts the present procedure can be the SMF and / or the AMF, and the UE_A can transmit and receive a message in the present procedure via the AMF and / or the access network_B.

[0283] Specifically, the device in the core network_B 190 transmits a network-initiated session management request message to the UE_A (S802). Here, the device in the core network_B 190 can include one or more of the eleventh to fifteenth identification information in the network-initiated session management request message, and can indicate a request of the core network_B 190 by including the identification information. Note that two or more of the identification information can be constituted as one or more identification information.

[0284] Further, the SMF 132 can indicate a request for a change of a PDU session for an NPN, a release of a PDU session establishment for an NPN, a request for a release of a PDU session establishment for an NPN, or a disallowal of a PDU session establishment to an NPN by transmitting the eleventh identification information and / or the twelfth identification information and / or the thirteenth identification information and / or the fourteenth identification information and / or the fifteenth identification information in the network-initiated session management request message.

[0285] In more detail, the SMF 132 can indicate that a management procedure of a PDU session for an NPN is started because the core network is performing DNN-based congestion management by transmitting the eleventh identification information and / or the twelfth identification information and / or the fifteenth identification information, can request a start of DNN-based congestion management, and can request a start of a timer using a value indicated by the fifth identification information.

[0286] Alternatively, the SMF 132 can also indicate that the management procedure of the PDU session for the NPN is started due to the fact that the core network is performing the congestion management by the combination of the S-NSSAI and the DNN by transmitting the eleventh identification information and / or the thirteenth identification information and / or the fifteenth identification information, can request the start of the congestion management by the combination of the S-NSSAI and the DNN, and can request the start of the timer using the value indicated by the fifteenth identification information.

[0287] Alternatively, the SMF 132 can also indicate that the management procedure of the PDU session for the NPN is started due to the fact that the core network is performing the congestion management based on the S-NSSAI by transmitting the eleventh identification information and / or the fourteenth identification information and / or the fifteenth identification information, can request the start of the congestion management based on the S-NSSAI, and can request the start of the timer using the value indicated by the fifteenth identification information.

[0288] Further, the SMF 132 can also make a request in which the above matters are combined by transmitting two or more of the eleventh to fifteenth identification information. Note that the matters indicated by the SMF 132 by transmitting each identification information are not limited to these.

[0289] Further, the SMF 132 can also include identification information other than the eleventh to fifteenth identification information in the network-initiated PDU session management request message. For example, the SMF 132 can include information indicating the NPN in the network-initiated PDU session management request message. Note that the information indicating the NPN here can be the SNPN ID, can be the S-NSSAI for the NPN, can be the DNN for the NPN, can be the CAG ID, or can be a combination of these. Note that the information indicating the NPN included in the network-initiated PDU session management request message can also be the information indicating the NPN received from the UE.

[0290] As described above, the core network_B 190 can notify the congestion management applied to the UE_A 10 by transmitting the network-initiated PDU session management request message. Note that, as a result, the core network_B 190 can notify that the congestion management is applied to the UE_A 10 and / or instruct the UE_A 10 to perform the congestion management and / or identify the information of the applied congestion management category and / or identify the information of the object of the congestion management such as the DNN and / or the S-NSSAI corresponding to the applied congestion management and / or establish the value of the timer corresponding to the applied congestion management.

[0291] It should be noted that core network_B can determine the identification information included in the network-led PDU session management request message based on the received identification information and / or network capability information and / or operator policies and / or network status.

[0292] For example, the core network_B190 may not perform at least one of the first to fourth congestion management processes for the UE and / or the combination of the UE and the NPN when the UE is logged in to the NPN and / or the UE requests to be connected to the NPN and / or the UE is in a state of being connected to the NPN, and may also manage the UE and / or the combination of the UE and the NPN as excluded objects from the first to fourth congestion management.

[0293] Moreover, in the case where the core network_B190 does not perform at least one of the first to fourth congestion management processes for the UE and / or the combination of the UE and the NPN and / or manages the UE and / or the combination of the UE and the NPN as excluded objects from the first to fourth congestion management, the SMF132 may not include at least one of the eleventh to fourteenth identification information in the network-led PDU session management request message.

[0294] Specifically, for example, in a case where the core network_B190 is in a state where the first congestion management is not performed for the UE and / or the combination of the UE and the NPN and / or the UE and / or the combination of the UE and the NPN is managed as an excluded object of the first congestion management, the SMF132 may not include the eleventh identification information and / or the twelfth identification information and / or the fifteenth identification information in the network-led PDU session management request message.

[0295] Similarly, for example, in a case where the core network_B190 is in a state where the second congestion management is not performed for the UE and / or the combination of the UE and the NPN and / or the UE and / or the combination of the UE and the NPN is managed as an excluded object of the second congestion management, the SMF132 may not include the eleventh identification information and / or the fourteenth identification information and / or the fifteenth identification information in the network-led PDU session management request message.

[0296] Similarly, for example, in a case where the core network_B190 is in a state where the third congestion management is not performed for the UE and / or the combination of the UE and the NPN and / or the UE and / or the combination of the UE and the NPN is managed as an excluded object of the third congestion management, the SMF132 may not include the eleventh identification information and / or the thirteenth identification information and / or the fifteenth identification information in the network-led PDU session management request message.

[0297] Similarly, for example, in a case where the core network_B190 is in a state where the fourth congestion management is not performed for the UE and / or the combination of the UE and the NPN and / or the UE and / or the combination of the UE and the NPN is managed as an excluded object of the fourth congestion management, the SMF132 may not include the eleventh identification information and / or the twelfth identification information and / or the thirteenth identification information and / or the fourteenth identification information and / or the fifteenth identification information in the network-led PDU session management request message.

[0298] In other words, in a case where the UE is in a state of logging in to the NPN and / or in a case where information indicating the NPN is received from the UE and / or in a state of being connected to the NPN, SMF 132 may not include at least one of the eleventh to fifteenth identification information in the network-led PDU session management request message.

[0299] The network-led PDU session management request message received by UE_A10 from SMF132 may include one or more identification information from the eleventh identification information to the fifteenth identification information.

[0300] UE_A, having received the network-initiated session management request message, then sends a network-initiated session management complete message ( S804 ). Furthermore, UE_A may also perform the sixth process ( S806 ) based on one or more of the eleventh to fifteenth identification information received from Core Network_B 190, completing this process. Furthermore, UE_A 10 may perform the sixth process upon completion of this process.

[0301] Hereinafter, a first example of the sixth process will be described.

[0302] Here, the sixth process may be a process in which UE_A 10 disregards the matter instructed by SMF 132. Furthermore, the sixth process may be a process in which UE_A 10 recognizes that management of the PDU session has been requested.

[0303] Specifically, in the sixth processing, it may be that when UE_A10 receives the eleventh identification information and / or the twelfth identification information and / or the fifteenth identification information from the core network_B190, UE_A10 ignores the information and request represented by the eleventh identification information and / or the twelfth identification information and / or the fifteenth identification information based on the state of UE_A10 logging into the NPN and / or connected to the NPN, and does not perform the first congestion management.

[0304] Also, in the sixth processing, it can be that, in a case where the UE_A 10 receives the eleventh identification information and / or the thirteenth identification information and / or the fifteenth identification information from the core network_B 190, the UE_A 10, based on a state in which the UE_A 10 is logged into the NPN and / or a state in which the UE_A 10 is connected to the NPN, disregards information and a request indicated by the eleventh identification information and / or the thirteenth identification information and / or the fifteenth identification information, and does not perform the third congestion management and / or the fourth congestion management.

[0305] Also, in the sixth processing, it can be that, in a case where the UE_A 10 receives the eleventh identification information and / or the thirteenth identification information and / or the fifteenth identification information from the core network_B 190, the UE_A 10, based on a state in which the UE_A 10 is logged into the NPN and / or a state in which the UE_A 10 is connected to the NPN, disregards information and a request indicated by the eleventh identification information and / or the thirteenth identification information and / or the fifteenth identification information, and does not perform the second congestion management.

[0306] Here, the sixth processing can be processing in which the UE_A 10 identifies the matter indicated by the SMF 132. Also, the sixth processing can be processing in which the UE_A 10 stores the received identification information as a context, and can be processing in which the UE_A 10 transmits the received identification information to an upper layer and / or a lower layer.

[0307] Note that the UE_A 10 can retransmit the rejected request and retry the PDU session establishment procedure based on completion of the sixth processing.

[0308] Next, a second example of the sixth processing will be described.

[0309] Here, the sixth processing can be processing in which the UE_A 10 identifies the matter indicated by the SMF 132. Also, the sixth processing can be processing in which the UE_A 10 stores the received identification information as a context, and can be processing in which the UE_A 10 transmits the received identification information to an upper layer and / or a lower layer.

[0310] Also, in the sixth processing, the processing of identifying the applied congestion management can be performed based on one or more of the eleventh identification information to the fifteenth identification information.

[0311] Also, in the sixth processing, the processing of identifying which one of the first to fourth congestion management categories is applied and the processing of identifying the DNN and / or the S-NSSAI corresponding to the applied congestion management can be performed based on one or more of the eleventh identification information to the fifteenth identification information.

[0312] Moreover, in the sixth processing, the value set for at least one of the first to fourth timers as shown in the fifteenth identification information corresponding to the applied congestion management can also be identified and set based on one or more identification information from the eleventh to fifteenth identification information, and the counting of the set timer can be started.

[0313] Specifically, in the sixth process, when UE_A10 receives the eleventh identification information, the twelfth identification information, and / or the fifteenth identification information from the core network_B190, UE_A10 may set the value indicated by the fifteenth identification information to the second timer based on the state of UE_A10 logged into and / or connected to the NPN, and start the second timer. At this time, in the sixth process, UE_A10 may also manage the second timer as a timer valid for both the RPLMN and the EPLMN. In other words, if UE_A10 logged into and / or connected to the NPN logs into a PLMN different from the RPLMN or EPLMN while the second timer is counting, the state may transition to a state where the sending of SM messages is permitted, or may transition to a state where the initiation of the PDU session establishment procedure and / or the initiation of the PDU session management procedure is permitted.

[0314] Furthermore, in the sixth process, when UE_A10 receives the eleventh identification information and / or the twelfth identification information and / or the fifteenth identification information from the core network_B190, and when UE_A10 is not logged into the NPN, UE_A10 also sets the value indicated by the fifteenth identification information to the second timer and starts the second timer. In this case, in the sixth process, UE_A10 may also manage the second timer as a timer valid for all PLMNs. In other words, UE_A10 that is not logged into the NPN and / or is not connected to the NPN may maintain the second timer even if a change in PLMN occurs during the counting execution of the second timer, may maintain a state in which the sending of SM messages is not allowed, and may maintain a state in which the start of the PDU session establishment process and / or the start of the PDU session management process is not allowed.

[0315] Also, in the sixth processing, it can be that, in a case where the UE_A 10 receives the eleventh identification information and / or the thirteenth identification information and / or the fifteenth identification information from the core network_B 190, the UE_A 10 sets the value indicated by the fifteenth identification information to the third timer on the basis of a state in which the UE_A 10 is logged in to the NPN and / or a state in which the UE_A 10 is connected to the NPN, and starts the third timer. At this time, in the sixth processing, the UE_A 10 can also manage the third timer as a timer valid for the RPLMN. In other words, the UE_A 10 logged in to the NPN and / or connected to the NPN can maintain a state in which the transmission of the SM message is not allowed in a case where the UE_A 10 is logged in to a PLMN different from the RPLMN in the counting of the third timer, and can maintain a state in which the start of the PDU session establishment procedure and / or the start of the PDU session management procedure is not allowed.

[0316] Also, in the sixth processing, it can be that, in a case where the UE_A 10 receives the eleventh identification information and / or the thirteenth identification information and / or the fifteenth identification information from the core network_B 190, the UE_A 10 sets the value indicated by the fifteenth identification information to the fourth timer on the basis of a state in which the UE_A 10 is logged in to the NPN and / or a state in which the UE_A 10 is connected to the NPN, and starts the fourth timer. At this time, in the sixth processing, the UE_A 10 can also manage the fourth timer as a timer valid for the RPLMN. In other words, the UE_A 10 logged in to the NPN and / or connected to the NPN can maintain a state in which the transmission of the SM message is not allowed in a case where the UE_A 10 is logged in to a PLMN different from the RPLMN in the counting of the fourth timer, and can maintain a state in which the start of the PDU session establishment procedure and / or the start of the PDU session management procedure is not allowed.

[0317] Also, the sixth processing can be processing in which the UE_A 10 starts the present procedure again after a certain period elapses, and can be processing in which the state of the request to limit or restrict the UE_A 10 is transitioned.

[0318] Hitherto, for the sixth processing, the processing contents have been described using the first example and the second example, but the present processing is not limited to these processes of the sixth processing. For example, the sixth processing can be processing in which the processing described in the first example and the processing described in the second example are combined.

[0319] Further, the message of the network-led session management request and response can be a PDU session modification command (PDU SESSION MODIFICATION COMMAND), can be a PDU session release command (PDU SESSION RELEASE COMMAND), and is not limited to these.

[0320] Note that the UE_A 10 can perform the congestion management identification process applied by the UE_A 10 based on the received eleventh to fifteenth identification information in the sixth process.

[0321] Also, each device can implement a process based on the identification information exchanged in the present process based on completion of the present process. In other words, the UE_A 10 can implement the sixth process based on completion of the present process, and can complete the present process after completion of the sixth process.

[0322] In the above process, by the exchange of the network-initiated session management request message, the core network_B 190 can instruct the UE_A 10 to stop or change the congestion management that the UE_A 10 has applied. Further, the UE_A 10 can implement the stop or change of the congestion management applied by the UE_A 10 based on the network-initiated session management request message from the core network_B 190. Here, in a case where the UE_A 10 has applied one or more congestion managements, the congestion management to be stopped or changed can be identified based on reception of the identification information included in the network-initiated session management request message from the core network_B 190. Note that each of the applied congestion managements can be different congestion management categories and / or congestion management corresponding to different DNNs and / or congestion management corresponding to different S-NSSAIs and / or congestion management that differs in a combination of DNN and S-NSSAI.

[0323] [3.4. UE-initiated PDU session management]

[0324] Next, a summary of the UE-initiated session management procedure is described. Hereinafter, the UE-initiated session management procedure is also referred to as the present procedure. The present procedure is a procedure for session management performed by the UE for an established PDU session. Note that the present procedure can be performed at any timing after the above-described registration procedure and / or PDU session establishment procedure are completed and each device transitions to a state in which at least one PDU session is established. Also, the UE can start the present procedure when the count of at least one of the first to fourth timers in execution expires. In addition, each device can exchange messages including identification information for stopping or changing congestion management in the present procedure, and can start behavior based on new congestion management instructed by the network based on completion of the present procedure.

[0325] Note that the present procedure can be a UE-initiated PDU session modification procedure, and a network-initiated session management procedure not limited to these can be performed. Note that each device can exchange a PDU session modification request message and / or a PDU session modification reject message in the UE-initiated PDU session modification procedure.

[0326] Use Figure 9An example of the UE-initiated session management procedure is described. In this chapter, the procedure refers to the UE-initiated session management procedure. Hereinafter, each step of the procedure is described. As described above, each device within UE_A 10 and core network_B 190 that has established at least one PDU session based on completion of the registration procedure and / or the PDU session establishment procedure starts the UE-initiated session management procedure at any timing. Here, the procedure can be started by UE_A 10, which can transmit and receive messages in the procedure via AMF and / or access network_B.

[0327] Specifically, UE_A 10 transmits a UE-initiated PDU session management request message to AMF 140 within core network_B 190 via NR node_A 122 using the N1 interface (S902). In the case where the procedure is a UE-initiated PDU session modification procedure, the UE-initiated PDU session management request message can be a PDU session modification request (PDU SESSION MODIFICATION REQUEST) message.

[0328] Here, UE_A 10 can include information indicating an NPN in the PDU session management request message, and can indicate that UE_A 10 requests connection to the NPN by including information indicating the NPN. Note that the information indicating the NPN can be an SNPN ID, can be an S-NSSAI for the NPN, can be a DNN for the NPN, can be a CAG ID, or can be a combination of these. Note that two or more of these identification information can constitute one or more identification information, or one identification information can be constituted by two or more identification information.

[0329] AMF receives the PDU session management request message and performs third condition determination. The third condition determination is used to determine whether the AMF accepts the request of UE_A 10. Core network_B starts (A) the network-initiated session management procedure (S906) in the case where the third condition determination is true, and starts (B) the procedure in the case where the third condition determination is false. Note that the (A) network-initiated session management procedure in the case where the third condition determination is true can be the network-initiated PDU session management procedure described above.

[0330] Next, the steps of the case where the third condition is determined to be false, that is, the steps of the process (B) in the present procedure, will be described. The SMF 132 transmits a UE-Initiated PDU Session Management Reject message to the UE_A 10 via the AMF 140 (S908), starting the process (B) in the present procedure. In the case where the present procedure is the UE-Initiated PDU Session Modification procedure, the UE-Initiated PDU Session Management Reject message can be a PDU Session Modification Reject message.

[0331] Specifically, the SMF 132 transmits the UE-Initiated PDU Session Management Reject message to the AMF 140 using the N11 interface, and the AMF 140 that has received the UE-Initiated PDU Session Management Request message transmits the UE-Initiated PDU Session Management Reject message to the UE_A 10 using the N1 interface.

[0332] Here, the SMF 132 can include one or more of the twenty-first to twenty-fifth identification information in the PDU Session Management Reject message, and can indicate that the request of the UE_A 10 is rejected by including these identification information. Note that two or more of these identification information can constitute one or more identification information.

[0333] Further, the SMF 132 can also indicate that the establishment of the PDU session for the NPN is rejected, can indicate that the establishment of the PDU session to the NPN is not allowed, can indicate that the modification of the PDU session for the NPN is rejected, and can indicate that the modification of the PDU session for the NPN is not allowed, by transmitting 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-fifth identification information in the PDU Session Management Reject message.

[0334] More specifically, the SMF 132 can indicate that the establishment and / or the modification of the PDU session for the NPN is rejected due to the fact that the core network is performing the DNN-based congestion management, can request the start of the DNN-based congestion management, and can request the start of the timer using the value indicated by the twenty-fifth identification information, by transmitting the twenty-first identification information and / or the twenty-second identification information and / or the twenty-fifth identification information.

[0335] Alternatively, the SMF 132 can also indicate that the establishment and / or the change of the PDU session for the NPN is rejected due to the fact that the core network is performing congestion management by the combination of the S-NSSAI and the DNN by transmitting the twenty-first identification information and / or the twenty-third identification information and / or the twenty-fifth identification information, can request the start of the congestion management by the combination of the S-NSSAI and the DNN, and / or can request the start of the timer using the value indicated by the twenty-fifth identification information.

[0336] Further, the SMF 132 can also indicate that the establishment and / or the change of the PDU session for the NPN is rejected due to the fact that the core network is performing congestion management based on the S-NSSAI by transmitting the twenty-first identification information and / or the twenty-fourth identification information and / or the twenty-fifth identification information, can request the start of the congestion management based on the S-NSSAI, and / or can request the start of the timer using the value indicated by the twenty-fifth identification information.

[0337] Moreover, the SMF 132 can also make a request in which the above matters are combined by transmitting two or more of the twenty-first to twenty-fifth identification information. Note that the matters indicated by the SMF 132 by transmitting each identification information are not limited to these.

[0338] Further, the SMF 132 can also include identification information other than the twenty-first to twenty-fifth identification information in the PDU session management reject message. For example, the SMF 132 can include information indicating the NPN in the PDU session management reject message. Note that the information indicating the NPN here can be the SNPN ID, can be the S-NSSAI for the NPN, can be the DNN for the NPN, can be the CAG ID, or can be a combination of these. Note that the information indicating the NPN included in the PDU session management reject message can be the information indicating the NPN received from the UE.

[0339] As described above, the core network_B 190 can notify the congestion management applied to the UE_A 10 by transmitting the PDU session management reject message. Note that, as a result, the core network_B 190 can notify that the congestion management is applied to the UE_A 10 and / or instruct the UE_A 10 to perform the congestion management and / or information identifying the applied congestion management category and / or information identifying the object of the congestion management such as the DNN and / or the S-NSSAI corresponding to the applied congestion management and / or the value of the timer established in correspondence with the applied congestion management.

[0340] It should be noted that the core network_B can determine the identification information included in the PDU session management reject message based on the received identification information and / or the capability information of the network and / or the policy such as the operator policy and / or the state of the network.

[0341] For example, the core network_B 190 can not perform at least one of the first to fourth congestion management procedures for the UE and / or the combination of the UE and the NPN, or can manage the UE and / or the combination of the UE and the NPN as an exclusion object of the first to fourth congestion management, in a case where the UE is in a state of being logged in for the NPN and / or a case where the UE requests to connect to the NPN and / or a case where the UE is in a state of being connected to the NPN.

[0342] Also, in a case where the core network_B 190 does not perform at least one of the first to fourth congestion management procedures for the UE and / or the combination of the UE and the NPN, or manages the UE and / or the combination of the UE and the NPN as an exclusion object of the first to fourth congestion management, the SMF 132 can not include at least one of the twenty-first to twenty-fifth identification information in the PDU session management reject message.

[0343] Specifically, for example, in a case where the core network_B 190 is in a state of not performing the first congestion management for the UE and / or the combination of the UE and the NPN and / or manages the UE and / or the combination of the UE and the NPN as an exclusion object of the first congestion management, the SMF 132 can not include the twenty-first identification information and / or the twenty-second identification information and / or the twenty-fifth identification information in the PDU session management reject message.

[0344] Also, for example, in a case where the core network_B 190 is in a state of not performing the second congestion management for the UE and / or the combination of the UE and the NPN and / or manages the UE and / or the combination of the UE and the NPN as an exclusion object of the second congestion management, the SMF 132 can not include the twenty-first identification information and / or the twenty-fourth identification information and / or the twenty-fifth identification information in the PDU session management reject message.

[0345] Also, for example, in a case where the core network_B 190 is in a state of not performing the third congestion management and / or the fourth congestion management for the UE and / or the combination of the UE and the NPN and / or manages the UE and / or the combination of the UE and the NPN as an exclusion object of the third congestion management and / or the fourth congestion management, the SMF 132 can not include the twenty-first identification information and / or the twenty-third identification information and / or the twenty-fifth identification information in the PDU session management reject message.

[0346] In other words, in a case where the UE is in a state logged in for the NPN and / or a case where information indicating the NPN is received from the UE and / or a case where the UE is in a state connected to the NPN, the SMF 132 can not include at least one of the twenty-first to twenty-fourth identification information in the PDU session management reject message even in a case where the first to fourth congestion management is detected.

[0347] One or more of the twenty-first identification information to the twenty-fifth identification information can be included in the PDU session management reject message received by the UE_A 10 from the SMF 132.

[0348] Next, the UE_A 10 implements the seventh process based on the reception of the PDU session management reject message (S910). Further, the UE_A 10 can also implement the seventh process based on the completion of the present procedure.

[0349] Hereinafter, a first example of the seventh process will be described.

[0350] Here, the seventh process can be a process in which the UE_A 10 disregards the matter indicated by the SMF 132. Also, the seventh process can be a process in which the UE_A 10 recognizes that the request of the present procedure is rejected.

[0351] Specifically, in the seventh process, in a case where the UE_A 10 receives the twenty-first identification information and / or the twenty-second identification information and / or the twenty-fifth identification information from the core network_B 190, the UE_A 10, based on the UE_A 10 being in a state logged in for the NPN and / or a state connected to the NPN and / or the UE_A 10 transmitting information indicating the NPN to the network, disregards the information and the request indicated by the twenty-first identification information and / or the twenty-second identification information and / or the twenty-fifth identification information, and does not perform the first congestion management.

[0352] Also, in the seventh process, in a case where the UE_A 10 receives the twenty-first identification information and / or the twenty-third identification information and / or the twenty-fifth identification information from the core network_B 190, the UE_A 10, based on the UE_A 10 being in a state logged in for the NPN and / or a state connected to the NPN and / or the UE_A 10 transmitting information indicating the NPN to the network, disregards the information and the request indicated by the twenty-first identification information and / or the twenty-third identification information and / or the twenty-fifth identification information, and does not perform the third congestion management and / or the fourth congestion management.

[0353] Also, in the seventh processing, in a case where the UE_A 10 receives the twenty-first identification information and / or the twenty-fourth identification information and / or the twenty-fifth identification information from the core network_B 190, the UE_A 10 can ignore the information and the request indicated by the twenty-first identification information and / or the twenty-fourth identification information and / or the twenty-fifth identification information, and not perform the second congestion management, based on a state in which the UE_A 10 is logged in to the NPN and / or a state in which the UE_A 10 is connected to the NPN and / or a state in which the UE_A 10 transmits information indicating the NPN to the network.

[0354] Here, the seventh processing can be processing in which the UE_A 10 identifies the matter indicated by the SMF 132. Also, the seventh processing can be processing in which the UE_A 10 stores the received identification information as a context, and processing in which the UE_A 10 transfers the received identification information to an upper layer and / or a lower layer. Also, the seventh processing can be processing in which the UE_A 10 identifies that the request of the present procedure is rejected.

[0355] Note that the UE_A 10 can retransmit the rejected request and retry the PDU session management procedure based on completion of the seventh processing.

[0356] Next, a second example of the seventh processing will be described.

[0357] Here, the seventh processing can be processing in which the UE_A 10 identifies the matter indicated by the SMF 132. Also, the seventh processing can be processing in which the UE_A 10 stores the received identification information as a context, and processing in which the UE_A 10 transfers the received identification information to an upper layer and / or a lower layer.

[0358] Also, in the seventh processing, the processing of identifying the application of the congestion management can be performed based on one or more of the twenty-first identification information to the twenty-fifth identification information.

[0359] Also, in the seventh processing, the processing of identifying which one of the first to fourth congestion management categories to apply and the processing of identifying the DNN and / or the S-NSSAI corresponding to the applied congestion management can be performed based on one or more of the twenty-first identification information to the twenty-fifth identification information.

[0360] Also, in the seventh processing, the value of the setting of at least one of the first to fourth timers indicated by the twenty-fifth identification information corresponding to the applied congestion management can be identified and set based on one or more of the twenty-first identification information to the twenty-fifth identification information, and the counted timer can be started.

[0361] Specifically, in the seventh processing, it can be that, in a case where the UE_A 10 receives the twenty-first identification information and / or the twenty-second identification information and / or the twenty-fifth identification information from the core network_B 190, the UE_A 10 sets the value indicated by the twenty-fifth identification information to the second timer based on a state of the UE_A 10 logged into the NPN and / or a state of the UE_A 10 connected to the NPN, and starts the second timer. At this time, in the seventh processing, the UE_A 10 can also manage the second timer as a timer valid for the RPLMN and the EPLMN. In other words, the UE_A 10 logged into the NPN and / or connected to the NPN can transition to a state where the transmission of the SM message is allowed in the execution of the counting of the second timer in a case where the UE_A 10 is logged into a PLMN different from the RPLMN or the EPLMN, can transition to a state where the start of the PDU session establishment procedure and / or the start of the PDU session management procedure is allowed.

[0362] Further, in the seventh processing, it can be that, in a case where the UE_A 10 receives the twenty-first identification information and / or the twenty-second identification information and / or the twenty-fifth identification information from the core network_B 190, in a case where the UE_A 10 is not logged into the NPN, the UE_A 10 also sets the value indicated by the twenty-fifth identification information to the second timer, and starts the second timer. At this time, in the seventh processing, the UE_A 10 can also manage the second timer as a timer valid for all PLMNs. In other words, the UE_A 10 not logged into the NPN and / or not connected to the NPN can maintain the second timer even if a change in the PLMN occurs in the execution of the counting of the second timer, can maintain a state where the transmission of the SM message is not allowed, and can also maintain a state where the start of the PDU session establishment procedure and / or the start of the PDU session management procedure is not allowed.

[0363] Further, in the seventh processing, it can be that, in a case where the UE_A 10 receives the twenty-first identification information and / or the twenty-third identification information and / or the twenty-fifth identification information from the core network_B 190, the UE_A 10 sets the value indicated by the twenty-fifth identification information to the third timer based on a state of the UE_A 10 logged into the NPN and / or a state of the UE_A 10 connected to the NPN, and starts the third timer. At this time, in the seventh processing, the UE_A 10 can also manage the third timer as a timer valid for the RPLMN. In other words, the UE_A 10 logged into the NPN and / or connected to the NPN can transition to a state where the transmission of the SM message is allowed in a case where the UE_A 10 is logged into a PLMN different from the RPLMN, can transition to a state where the start of the PDU session establishment procedure and / or the start of the PDU session management procedure is allowed.

[0364] Furthermore, in the seventh process, when UE_A10 receives the 21st, 24th, and / or 25th identification information from core network_B190, UE_A10 may set the value indicated by the 25th identification information to the fourth timer based on the UE_A10's login status to the NPN and / or its connection status to the NPN, and start the fourth timer. In this case, in the seventh process, UE_A10 may also manage the fourth timer as a timer valid for the RPLMN. In other words, when UE_A10 is logged in to the NPN and / or connected to the NPN, it may transition to a state that allows the sending of SM messages, or it may transition to a state that allows the initiation of the PDU session establishment procedure and / or the initiation of the PDU session management procedure, if it is logged in to a PLMN different from the RPLMN.

[0365] Moreover, the seventh processing may be a processing in which UE_A10 restarts the present process after a certain period of time, or a processing in which the state transitions to a state that limits or restricts the request of UE_A10.

[0366] The seventh process has been described above using the first and second examples, but is not limited to these. For example, the seventh process may be a combination of the process described in the first and second examples.

[0367] Furthermore, UE_A10 can recognize that its request has been rejected by receiving a PDU Session Management Reject message or by not receiving a UE-led PDU Session Management Request message. Each device completes process (B) of this process based on the transmission and reception of the PDU Session Management Reject message.

[0368] 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 to a state where a PDU session is established based on the completion of process (A) in this process, or can recognize that this process is rejected based on the completion of process (B) in this process, and can also transition to a state where a PDU session is not established.

[0369] Furthermore, each device can perform processing based on the identification information sent and received in this process upon completion of this process. In other words, UE_A10 can perform the seventh process upon completion of this process.

[0370] Further, the third condition determination can be performed based on identification information and / or subscriber information and / or operator policy included in the PDU session management request message. For example, the third condition determination can be true in a case where the network allows the request of the UE_A 10. Further, the third condition determination can be false in a case where the network does not allow the request of the UE_A 10. Also, the third condition determination can be true in a case where the network and / or the device within the network of the connection destination of the UE_A 10 supports the function requested by the UE_A 10, and can be false in a case where the network and / or the device within the network does not support the function. Also, the third condition determination can be true in a case where it is determined that the network is in a congested state, and can be false in a case where it is determined that the network is in a non-congested state. Note that the conditions that determine the true or false of the third condition can not be limited to the above conditions.

[0371] Through the reception and transmission of the PDU session management reject message in the above procedure, the core network_B 190 notifies the UE_A 10 of the applied congestion management, and the UE_A 10 can apply the congestion management indicated by the core network_B 190 or can ignore the congestion management indicated by the core network_B 190. Note that the core network_B 190 and the UE_A 10 can apply a plurality of congestion managements by performing the procedure and the processing explained in the present procedure a plurality of times. Note that the applied congestion managements can be different congestion management categories and / or congestion managements corresponding to different DNNs and / or congestion managements corresponding to different S-NSSAIs and / or congestion managements that differ in a combination of DNNs and S-NSSAIs.

[0372] [4. Explanation of Embodiments]

[0373] Hereinafter, the first to second embodiments will be explained. Note that the first to second embodiments are one example of the present application. That is, the embodiments that represent the present application are not limited to the first to second embodiments, and can be a combination of one or more of the procedures explained in the third chapter.[4.1. Explanation of the First Embodiment]

[0374] First, the first embodiment will be explained. The first embodiment is constituted of a login procedure and a PDU session establishment procedure. Note that the detailed contents of the login procedure and the PDU session establishment procedure of the present embodiment refer to the contents explained above.

[0375] In the first embodiment, first, the UE_A 10 starts the login procedure. The UE_A 10 and the devices transition to a state of being logged in to the NPN and / or a state of being allowed to connect to the NPN and / or a state of being connected to the NPN based on completion of the login procedure. Specifically, the state of being logged in to the NPN or the state of being allowed to connect to the NPN and / or the state of being connected to the NPN is transitioned to by receiving the login accept message from the AMF 140.

[0376] Furthermore, UE_A10 starts a PDU session establishment process based on the completion of the login process. UE_A10 may request a PDU session establishment for the NPN by sending information indicating the NPN to the core network_B190.

[0377] UE_A10 receives a PDU session establishment rejection message from core network_B190 as a response to the PDU session establishment request message. It should be noted that the PDU session establishment rejection message may include at least one of the first to fifth identification information.

[0378] Based on the fact that UE_A10 is logged in to the NPN and / or connected to the NPN and / or that UE_A10 has requested a PDU session management procedure for the NPN, UE_A10 ignores the request from Core Network_B190 and does not start congestion management indicated by the identification information received from Core Network_B190. In other words, UE_A10 ignores the request to start congestion management indicated by Core Network_B190 and does not start the corresponding congestion management.

[0379] UE_A10 that does not start congestion management can perform the PDU session establishment process by continuing to send the PDU session establishment request message again.

[0380] Through the above, UE_A10 and each device do not enable the congestion management process for UEs connected to the NPN. In other words, through this process, UE_A10 and each device can treat UEs connected to the NPN as being excluded from the congestion management process.

[0381] [4.2. Description of the Second Embodiment]

[0382] Next, the second embodiment is described. The second embodiment consists of a first login process, a PDU session establishment process, and a second login process. It should be noted that the details of the first login process and the second login process of this embodiment refer to the login process described above, and the details of the PDU session establishment process of this embodiment refer to the PDU session establishment process described above.

[0383] In the second embodiment, UE_A 10 initiates a first login procedure. Upon completion of the first login procedure, UE_A 10 and each device transition to the Connected to NPN state. Transitions to the Logged-in to NPN state or the Allowed to NPN state are made by receiving a PDU Session Accept message from the AMF 140.

[0384] Furthermore, upon completion of the login process, UE_A10 starts a PDU session establishment process, and requests PDU session establishment for the NPN by sending information indicating the NPN to the core network_B190.

[0385] The UE_A 10 receives the PDU session establishment reject message from the core network_B 190 as a response to the PDU session establishment request message. Note that at least one of the first to fifth identification information can be included in the PDU session establishment reject message.

[0386] The UE_A 10 starts the congestion management procedure based on the request from the core network_B 190. Specifically, for example, the UE_A 10 can perform the second congestion management based on the reception of the first identification information and / or the second identification information and / or the fifth identification information.

[0387] The UE_A 10 exits from the RPLMN and / or the RSNPN in the congestion management execution, and starts the second login procedure for other PLMN. The UE_A 10 can stop the congestion management in the second login procedure based on the fact that the UE-selected PLMN is not the RPLMN, the RSNPN, and the EPLMN.

[0388] With the above, the UE_A 10 and each device can make the congestion management and / or the corresponding timer established with the congestion management effective for the logged-in PLMN and / or the logged-in SNPN and / or the equivalent PLMN, can also transition to a state that allows the transmission of the SM message, and can also transition to a state that allows the start of the PDU session establishment procedure and / or the start of the PDU session management procedure, in the case where the UE is connected to the NPN.

[0389] In other words, in the case where the UE is connected to the NPN, in the case where the UE is connected to a PLMN different from the logged-in PLMN and the equivalent PLMN or in the case where the UE is connected to an NPN different from the logged-in NPN, the UE_A 10 and each device can make the congestion management and / or the corresponding timer established with the congestion management ineffective or stop for the logged-in PLMN and / or the logged-in SNPN and / or the equivalent PLMN, can also maintain a state that does not allow the transmission of the SM message, and can also maintain a state that does not allow the start of the PDU session establishment procedure and / or the start of the PDU session management procedure.

[0390] [Main point of the embodiment]

[0391] The UE (User Equipment; terminal device) of one embodiment of the present application is characterized by including a transceiver that, in the case where the UE is connected to an NPN (Non-Public Network), disregards a twenty-sixth 5G SM (5G Session Management) reason value in the case where the twenty-sixth 5G SM reason value is received.

[0392] The UE (User Equipment) of one embodiment of the present application is characterized by including a transceiver that, in a case where the UE is connected to a NPN (Non-Public Network), disregards a sixty-seventh 5GSM (5G Session Management) cause value in a case where the sixty-seventh 5GSM cause value is received.

[0393] The UE (User Equipment) of one embodiment of the present application is characterized by including a transceiver that, in a case where the UE is connected to a NPN (Non-Public Network), disregards a sixty-ninth 5GSM (5G Session Management) cause value in a case where the sixty-ninth 5GSM cause value is received.

[0394] The UE (User Equipment) of one embodiment of the present application is characterized by including a control unit and a transceiver, the UE is connected to a NPN (Non-Public Network), the control unit starts a back-off timer corresponding to a DNN (Data Network Name), the back-off timer is applied to a first PLMN (Public Land Mobile Network) and a second PLMN, the first PLMN is a PLMN in which the UE is logged in, and the second PLMN is an equivalent PLMN.

[0395] [5. Improvement Example]

[0396] The program that works in the apparatus according to the present application can be a program that controls a CPU (Central Processing Unit) or the like to cause a computer to function in order to realize the functions of the embodiments according to the present application. The program or information processed by the program is temporarily stored in a volatile memory such as a RAM (Random Access Memory) or a nonvolatile memory such as a flash memory, a hard disk drive (HDD), or another storage device system.

[0397] Note that the program for realizing the functions of the embodiments according to the present application can be recorded in a computer-readable recording medium. The program recorded in the recording medium can be read into a computer system and executed to realize the functions. The "computer system" here refers to a computer system built into the apparatus and includes a computer system including an operating system, hardware, and the like. Furthermore, the "computer-readable recording medium" can be a semiconductor recording medium, an optical recording medium, a magnetic recording medium, a medium that dynamically stores a program for a short time, or another computer-readable recording medium.

[0398] In addition, each functional block or each feature of the device used in the above-mentioned embodiment can be installed or executed by an electronic circuit such as an integrated circuit or multiple integrated circuits. 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 (ASIC) for a specific purpose, a field programmable gate array (FPGA) or other programmable logic elements, discrete gates or transistor logic, discrete hardware parts or a combination thereof. The general-purpose processor 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 solutions of the present invention may also use new integrated circuits based on this technology.

[0399] It should be noted that the present invention is not limited to the aforementioned embodiments. While the embodiments describe an example of a device, 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 appliances, cleaning / washing equipment, air conditioners, office equipment, vending machines, and other lifestyle appliances, as well as terminal devices or communication devices.

[0400] The embodiments of the present invention have been described in detail above with reference to the accompanying drawings. However, the specific configuration is not limited to this embodiment and also includes design changes within the scope of the present invention. In addition, the present invention can be modified in various ways within the scope of the technical solutions shown in the technical solutions, 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, the configuration obtained by replacing the elements described in the above embodiments with the elements that have the same effect with each other is also included.

[0401] Description of Reference Numerals

[0402] 1 Mobile Communication System

[0403] 10 UE_A

[0404] 30 PGW-U

[0405] 32 PGW-C

[0406] 35 SGW

[0407] 40 MME

[0408] 45 eNB

[0409] 50 HSS

[0410] 60 PCRF

[0411] 80 Access Network_A (E-UTRAN)

[0412] 90 Core Network_A

[0413] 120 Access Network_B (5G AN)

[0414] 122 gNB

[0415] 130 UPF

[0416] 132 SMF

[0417] 140 AMF

[0418] 150 UDM

[0419] 160 PCF

[0420] 190 Core Network_B

Claims

1. A user equipment (UE), characterized in that: The UE includes a control unit and a transceiver unit. When the transceiver receives the 5G session management 5GSM reason value #26 and the backoff timer value for starting the timer T3396 for congestion management based on the data network name DNN, The control unit starts the timer T3396 using the backoff timer value. The 5GSM reason value #26 indicates insufficient resources. In the case of an independent non-public network SNPN, the timer T3396 is started for each DNN and SNPN.

2. A communication method for a user equipment (UE), characterized in that: Upon receiving the 5G Session Management 5GSM Reason value #26 and the backoff timer value for starting the timer T3396 for congestion management based on the data network name DNN, Using the backoff timer value to start the timer T3396, The 5GSM reason value #26 indicates insufficient resources. In the case of an independent non-public network SNPN, the timer T3396 is started for each DNN and SNPN.

Images