RU2773240C1 - User equipment - Google Patents

Abstract

FIELD: communication.

SUBSTANCE: invention relates to the field of communication control, namely, control of control signals based on reasons other than overload control. To realise the technical result, a request information included in a first message with an initial session creation request is transmitted, based on the protocol data unit (PDU), to the network node in order to create a first PDU session with the data network name (DNN) and single network slice selection assistance information (S-NSSAI), a message denying the creation of a PDU session is received (S1122) and the request information included in a second message with an initial PDU session creation request is transmitted (S1100) to the network node in order to create a second PDU session when the reason value of the message denying the creation of a PDU session indicating that the first PDU session does not exist is received for the initial request to create a second PDU session.

EFFECT: improved overload control initiated by the terminal apparatus.

15 cl, 12 dwg

Description

CROSS-REFERENCE TO RELATED APPLICATION

[0001] This application claims priority based on Japanese Patent Application No. 2018-189949 filed October 5, 2018, the contents of which are incorporated herein by reference.

FIELD OF THE INVENTION

[0002] The present invention relates to user equipment (UE).

BACKGROUND OF THE INVENTION

[0003] 3GPP (3rd Generation Systems Partnership Project), carrying out the activities of standardizing the latest mobile communication systems, has studied the system architecture of LTE (Long Term Evolution of Communication Networks), i.e. SAE (System Architecture Evolution). 3GPP has standardized EPS (Evolved Packet System) as a communication system for implementing all IP (Internet protocols). In addition, the core network constituting the EPS is called EPC (Evolved Packet Core).

[0004] In addition, recently, 3GPP specialists have been studying next generation communication technology and system architecture for 5G (5th generation) mobile communication systems, i.e., next generation mobile communication systems, and in particular, 3GPP specialists have been engaged in the standardization of 5GS (5G systems ) as a system for implementing 5G mobile communication systems (see NPL 1 and NPL 2). In order to standardize solutions in 5GS, the technical problems associated with connecting various terminals to the cellular network were identified.

[0005] Solution requirements include, for example, optimizing and diversifying communication procedures to provide continuous support of a mobile communication service for a terminal supporting various access networks, optimizing a system architecture in accordance with optimizing and diversifying communication procedures, and the like.

[0006] Documents of the prior art

[0007] Non-Patent Literature

[0008] Non-Patent Document 1: 3GPP TS 23.501 v15.0.0; 3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; System Architecture for the 5G System; Stage 2 (Release 15)

[0009] Non-Patent Document 2: 3GPP TS 23.502 v15.0.0; 3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Procedures for the 5G System; Stage 2 (Release 15)

SUMMARY OF THE INVENTION

[0010] Technical problem

[0011] In 5GS, in addition to the configuration performing a function equivalent to congestion control, control of a control signal based on causes other than congestion control is learned (see NPL 1 and NPL 2).

[0012] However, workflows remain unexplained related to session control of a terminal receiving a reason that the network informs the terminal to apply control signal control based on a reason other than congestion control. In addition, as with congestion control, the backoff timer control process when reporting the backoff timer to the terminal is not explained.

[0013] In view of the above, one aspect of the present invention can be obtained, and an object of the present invention is to provide a configuration and a communication control method for realizing a control signal control process based on a cause other than congestion control.

[0014] Problem Solving

[0015] The user equipment of the present invention comprises a transmission unit, where, according to the received 5GSM cause value, a session PDU does not exist, the transmission unit transmits a request message to create an initial session PDU.

[0016] The user equipment of the present invention comprises a receiving unit and a control unit, wherein when the receiving unit receives a 5GSM cause value according to which the request is denied or not specified and the timer data, the control unit activates a backoff timer for the common land mobile network information combination usage (PLMN), a data network name (DNN), and one ancillary information for network slice selection (S-NSSAI) based on a 5GSM cause value in case the 5GSM cause value is a cause value different from another cause value related to overload management.

[0017] The user equipment of the present invention comprises a receiving unit and a control unit, wherein when the receiving unit receives a 5GSM cause value and timer data, the control unit activates a backoff timer for a combination of PLMN, DNN, and S-NSSAI based on the 5GSM cause value in the case, if the 5GSM cause value is a cause value different from another congestion control related cause value.

[0018] The user equipment of the present invention comprises a control unit, wherein when the received 5GSM cause value is a cause value other than congestion control, the control unit ignores the received backoff timer.

[0019] Effect of invention

[0020] According to the configuration described above, the 5GS terminal device and the device in the core network can perform control processes such as congestion control initiated by the terminal device and the network for each network slice and/or DNN or access point name (APN ).

BRIEF DESCRIPTION OF GRAPHICS

[0021] FIG. 1 is a diagram illustrating a circuit diagram of a mobile communication system.

[0022] FIG. 2 is a diagram illustrating an example of an access network configuration in a mobile communication system.

[0023] FIG. 3 is a diagram illustrating a configuration example and the like of a core network_A in a mobile communication system.

[0024] FIG. 4 is a diagram illustrating an example of a core network configuration in a mobile communication system.

[0025] FIG. 5 is a diagram illustrating a hardware configuration of a UE.

[0026] FIG. 6 is a diagram illustrating the hardware configuration of an Evolved Node B (eNB)/New Radio Access Technology (NR) station node.

[0027] FIG. 7 is a diagram illustrating the hardware configuration of a Mobility Management Entity (MME)/Access and Mobility Management Function (AMF).

[0028] FIG. 8 is a diagram illustrating the hardware configuration of the Session Management Function (SMF)/Packet Data Network Gateway (PGW)/User Plane Function (UPF).

[0029] FIG. 9 is a diagram illustrating the initial procedure.

[0030] FIG. 10 is a diagram illustrating the registration procedure.

[0031] FIG. 11 is a diagram illustrating a procedure for creating a PDU session.

[0032] FIG. 12 is a diagram illustrating a network-initiated session management procedure.

DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0033] Next, with reference to the drawings, the best embodiment of the present invention will be described. In this embodiment, one embodiment of the mobile communication system according to the present invention will be described as an example.

[0034] [1. System Overview]

[0035] An overview of the mobile communication system according to the present embodiment will be described with reference to FIG. 1, FIG. 2, FIG. 3 and FIG. 4. In FIG. 2 is a diagram illustrating the details of an access network in the mobile communication system shown in FIG. 1. In FIG. 3 is a diagram mainly illustrating details of the core network_A90 in the mobile communication system shown in FIG. 1. In FIG. 4 is a diagram mainly illustrating the details of the core network_B190 in the mobile communication system shown in FIG. 1. As shown in FIG. 1, the mobile communication system 1 according to the present embodiment includes a terminal device (which is also referred to as a user equipment or a mobile terminal device) UE_A10, an access network (AN)_A, an access network_B, a core network (CN)_A90, a core network_B190, packet data network (PDN)_A6 and data network (DN)_A5. It should be noted that the combination of access network_A and core network_A90 may be referred to as EPS (Evolved Packet System; 4G mobile communication system), and the combination of access network_B, core network_B190 and UE_A10 may be referred to as 5GS (5G system; 5G mobile communication system). 5GS and EPS configurations may not be limited to the above. For simplicity, reference network_A90, reference network_B, or a combination thereof may also be referred to as reference network; access network_A, access network_B, or a combination thereof may also be referred to as an access network or a radio access network; and DN_A5, PDN_A6, or a combination thereof may also be referred to as a DN.

[0036] Here, UE_A10 may be a device capable of connecting to a network service via 3GPP access (also referred to as 3GPP access network) and/or non-3GPP access (also referred to as non-3GPP access network). The UE may also be equipped with a UICC (Universal Integrated Circuit Card) or eUICC (Embedded UICC). UE_A10 may be a wireless connection capable terminal device and may be an ME (Mobile Equipment), MS (Mobile Station), a CIoT (Cellular Internet of Physical Entities) terminal (CIoT UE), or the like.

[0037] In addition, UE_A10 may be connected to an access network and/or to a core network. Moreover, UE_A10 may connect to DN_A and/or PDN_A via access network and/or core network. UE_A10 transmits and/or receives (communicates) user data to and/or from (via) DN_A and/or PDN_A using a protocol data unit or packet data unit (PDU) session and/or connecting to a PDN (packet data network ) (also known as connecting to a PDN). In addition, the exchange of user data is not limited to Internet Protocol (IP: IPv4 or IPv6) communication, and may be, for example, non-IP EPS communication, or may be Ethernet communication (registered trademark) or 5GS unstructured communication.

[0038] In this case, IP communication means communication using IP and is communication carried out by sending and/or receiving an IP packet with an assigned IP header. The payload portion contained in the IP packet may include user data transmitted and/or received by the UE_A10. In addition, non-IP communication means non-IP communication, and is communication implemented by sending and/or receiving data without a given IP header. For example, non-IP communication may also be a data exchange implemented by sending and/or receiving application data without a given IP address, or may be sending and/or receiving user data sent and/or received by UE_A10 with a different header such as a media access control (MAC) header, an Ethernet frame header (registered trademark), or the like.

[0039] In addition, a PDU session refers to a connection established between UE_A10 and DN_A5 to provide a PDU connection service. In particular, the session PDU may also be a connection created between UE_A10 and an external gateway. In this case, the external gateway may be a UPF, PGW (packet data network gateway), or the like. In addition, the session PDU may be a communication path established for transmitting and receiving user data between the UE_A10 and the core network and/or DN, or may be a communication path for transmitting and receiving PDUs. The session PDU may further be a session created between the UE_A10 and the core network and/or DN, or may be a logical communication path including a transmission path, such as one or more channels, etc., between devices in the mobile system 1 connections. More specifically, the session PDU may be a connection established between the UE_A10 and the core_B190 and/or an external gateway, or may be a connection established between the UE_A10 and the UPF. In addition, the session PDU may be a connectivity and/or connection between UE_A10 and UPF_A235 via NR-node_A122. Moreover, a PDU session may be identified by a PDU session identifier (ID) and/or an EPS channel identifier.

[0040] Moreover, UE_A10 can transmit and/or receive user data to and/or from a device such as an application server deployed in DN_A5 using a session PDU. In other words, during a PDU session, user data transmitted and/or received between UE_A10 and a device such as an application server deployed in DN_A5 can be transmitted. In addition, each device (UE_A10, device in the access network, device in the core network and/or device in the data network) can manage one or more pieces of identification information associated with the PDU session. It should be noted that these identity information pieces may include at least one of APN (Access Point Name), TFT (Traffic Flow Pattern), Session Type, Application Identity, DN_A5 Identity, NSI Identity (Network Slice Instance) , DCN (dedicated core network) identification information, and access network identification information, and may further include other information. Furthermore, when multiple PDU sessions are created, the respective pieces of identification information associated with the PDU sessions may have the same content or different content. The NSI identification information is further information for identifying the NSI, and hereinafter may be an NSI identifier or a slice instance identifier.

[0041] In addition, as shown in FIG. 2, Access Network_A and/or Access Network B can be any of UTRAN (Universal Terrestrial Radio Access Network)_A20, E-UTRAN (Evolved Universal Terrestrial Radio Access Network)_A80, and NG-RAN (5G-RAN)_A120. Hereinafter, UTRAN_A20, E-UTRAN_A80 and/or NG-RAN_A120 may be referred to as a 3GPP access or a 3GPP access network, and a non-3GPP wireless LAN or AN may be referred to as a non-3GPP access or a non-3GPP access network. Each radio access network includes the device to which the UE_A10 is actually connected (for example, a base station device or an access point), and the like.

[0042] For example, E-UTRAN_A80 is an LTE access network and is configured to include one or more eNBs_A45. eNB_A45 is a radio base station to which UE_A10 connects via E-UTRA (Enhanced Universal Terrestrial Access). In addition, in the case where a plurality of eNBs are present in the E-UTRAN_A80, the eNBs can be connected to each other.

[0043] In addition, NG-RAN_A120 is a 5G access network, or may be the (R)AN illustrated in FIG. 4 and is configured to include one or more NR nodes (new radio access technology nodes)_A122 and/or ng-eNBs. In addition, NR-node_A122 is a radio base station to which UE_A10 is connected via 5G radio access, and may also be referred to as gNB. In addition, the ng-eNB may be an eNB (E-UTRA) which is a 5G access network, may be connected to the core network_B190 via an NR node_A, or may be directly connected to the core network_B190. In addition, in the case where there are multiple NR-nodes_A122 and/or ng-eNBs in NG-RAN_A120, NR-nodes_A122 and/or ng-eNBs may be connected to each other.

[0044] NG-RAN_A120 may further be an access network configured with E-UTRA access and/or 5G radio access. In other words, NG-RAN_A120 may include eNB_A45, or NR-node_A122, or both. In this case, eNB_A45 and NR-node_A122 may be similar devices. Thus, NR-node_A122 can be replaced by eNB_A45.

[0045] UTRAN_A20 is an access network of a 3G mobile communication system and is configured to include RNC (Radio Network Controller)_A24 and NB (Node B)_A22. NB_A22 is a radio base station to which UE_A10 connects via UTRA (Universal Terrestrial Radio Access), and UTRAN_A20 may include one or more radio base stations. In addition, RNC_A24 is a controller for connecting core network_A90 to NB_A22, and UTRAN_A20 may be configured to include one or more RNCs. In addition, RNC_A24 may be connected to one or more NB_A22.

[0046] It should be noted that in this document, the expression "UE_A10 is connected to each radio access network" means that "UE_A10 is connected to a base station device, access point, or the like included in each radio access network" and that "data, signals etc. are also transmitted and/or received via the base station device and the access point.” It should be noted that the control messages transmitted and/or received between UE_A10 and core network_B190 may be the same control message, regardless of the type of access network. Therefore, the expression "UE_A10 and the core network_B190 transmit a message to each other and/or receive it from each other through the NR node_A122" may be equivalent to the expression "UE_A10 and the core network_B190 transmit a message to each other via the eNB_A45".

[0047] The access network is further a radio network attached to the UE_A10 and/or the core network. The access network may be a 3GPP access network or an access network not supported by 3GPP. In addition, the 3GPP access network may be UTRAN_A20, E-UTRAN_A80 and NG-RAN (radio access network)_A120, and the non-3GPP access network may be a wireless LAN access point (WLAN AN). In addition, UE_A10 may be connected to an access network to connect to a core network, or may be connected to a core network via an access network.

[0048] In addition, DN_A5 and PDN_A6 are data networks that provide communication services to UE_A10, may be configured as packet data networks, or may be configured for each service. Moreover, DN_A5 may include a connected communication terminal. Thus, a connection to DN_A5 may involve a connection to a communication terminal or server device deployed in DN_A5. In addition, the transmission and/or reception of user data to and/or from DN_A5 may refer to the transmission and/or reception of user data to and/or from the communication terminal or server device deployed in DN_A5. In addition, although DN_A5 is outside the core networks shown in FIG. 1, it may be within the core network.

[0049] In addition, core network_A90 and/or core network_B190 may be configured as a device in one or more core networks. In this case, the device in the core network may be a device that performs part of the processing or functions, or all of the processing or functions of the devices included in the core network_A90 and/or core network_B190. It should be noted that a device in the core network may be referred to as a core network device.

[0050] In addition, the core network is a mobile IP network operated by a mobile operator (MNO) and connected to an access network and/or DN. The core network may be a core network for a mobile operator operating and managing the mobile communications system 1, or may be a core network for a mobile virtual network operator or mobile virtual network service provider such as a mobile virtual network operator (MVNO). ) or a mobile virtual network (MVNE) implementation tool. Core Network_A90 may be EPC (Evolved Packet Core) constituting EPS (Evolved Packet System), and Core Network_B190 may be 5GC (5G Core Network) constituting 5GS. The core network_B190 may further be a core network for a system that provides 5G communication services. Conversely, the EPC may represent the core network_A90 and the 5GC may represent the core network_B190. It should be noted that the core network_A90 and/or the core network_B190 may not be limited to the above and may be a network for providing mobile communication services.

[0051] Next, reference network_A90 will be described. The core network_A90 may include at least one of HSS (Home Subscriber Server)_A50, AAA (Authentication, Authorization, Accounting), PCRF (Billing Policies and Rules Function), PGW_A30, ePDG, Signaling Gateway (SGW_A35), MME (Entity Mobility Management)_A40, SGSN (Serving GPRS Support Node) and Service Environment Creation Function (SCEF). In addition, they can be configured as NF (network functions). NF may be a processing function included in the network. In addition, the core network_A90 may be connected to a plurality of radio access networks (eg, UTRAN_A20 and E-UTRAN_A80).

[0052] Although among the network functions in FIG. 3 only HSS (HSS_A50), PGW (PGW_A30), SGW (SGW_A35) and MME (MME_A40) are shown for simplicity, this does not mean that they do not include other NF devices and/or functions. For simplicity, UE_A10 is also called UE, HSS_A50 is also called HSS, PGW_A30 is also called PGW, SGW_A35 is also called SGW, MME_A40 is also called MME, and DN_A5 and/or PDN_A6 are also called DN or PDN.

[0053] Each device included in the core network_A90 will be briefly described below.

[0054] PGW_A30 is a relay device connected to DN, SGW_A35, ePDG, WLAN ANa70, PCRF and AAA and transmitting user data as a gateway between DN (DN_A5 and/or PDN_A6) and core network_A90. In addition, the PGW_A30 can act as a gateway for IP and/or non-IP communications. In addition, the PGW_A30 may be provided with a function for performing IP communication, or may be provided with a function for converting between non-IP communication and IP communication. Moreover, many such gateways can be deployed in the core network_A90. In addition, multiple deployed gateways can act as gateways to connect the core network_A90 to a single PDN.

[0055] It should be noted that a user plane (U or UP plane) may be a communication path for transmitting and/or receiving user data and may include a plurality of channels. The control plane (C-plane or CP) may further be a communication path for transmitting and/or receiving a control message and may include a plurality of channels.

[0056] In addition, PGW_A30 may be connected to SGW, DN, UPF (User Plane Function) and/or SMF (Session Management Function), and may also be connected to UE_A10 via U plane. Moreover, PGW_A30 may be configured as integral with UPF_A235 and/or SMF_A230.

[0057] SGW_A35 is a relay device that is connected to PGW_A30, MME_A40, E-UTRAN_A80, SGSN and UTRAN_A20 and transmits user data as a gateway between core network_A90 and 3GPP access network (UTRAN_A20, GERAN or E-UTRAN_A80).

[0058] The MME_A40 is a control device that is connected to the SGW_A35, the access network, the HSS_A50, and the SCEF, and performs location information management, including UE_A10 mobility management via the access network, and access control. The MME_A40 may further include a session management device function for managing a session created by the UE_A10. In addition, a plurality of such control devices may be deployed in the core network A90, and, for example, a location control device other than MME_A40 may also be configured. Like MME_A40, a location management device other than MME_A40 can be connected to SGW_A35, access network, SCEF and HSS_A50. Moreover, MME_A40 can be connected to an Access and Mobility Management (AMF) unit.

[0059] In addition, when a plurality of MMEs are included in the core network_A90, the MMEs can be connected to each other. As a result, the UE_A10 context can be transmitted and/or received between MMEs. Thus, MME_A40 is a control device for transmitting and/or receiving control information related to mobility management and session management to and/or from UE_A10. In other words, MME_A40 may be a control device for the control plane (plane C; CP).

[0060] Although an example is described in which the MME_A40 is configured to be included in the core network_A90, the MME_A40 may further be a control device configured in one or more core networks, DCN or NSI, or may be a control device connected to one or more core networks, DCN or NSI. In this case, multiple DCNs or NSIs may be managed by one network operator or different network operators, respectively.

[0061] In addition, the MME_A40 may be a relay device that transmits user data as a gateway between the core network_A90 and the access network. In addition, the amount of user data transmitted and/or received by the MME_A40 acting as a gateway may be small.

[0062] The MME_A40 may further be an NF whose function is to manage the mobility of the UE_A10 or the like, or an NF managing one or more NSIs. In addition, MME_A40 may be an NF with a function to perform one or more of the above functions. It should be noted that the NF block may be one or more devices deployed in the core network_A90, may be a CP functional block (hereinafter also referred to as a control plane functional block (CPF) or a control plane network functional block) for processing control information and/ or a control message, or may be a common CP functional block shared by multiple network slices.

[0063] Here, NF is a processing function configured on the network. In other words, the NF may be a functional entity such as MME, SGW, PGW, CPF, AMF, SMF, or UPF, or may be a function such as mobility management (MM) and session management (SM), or capability information. . In addition, the NF may be a functional device that performs a single function, or may be a functional device that implements multiple functions. For example, a separate NF block may be present to implement the MM function and a separate NF block to implement the SM function, or an NF may be present to implement both the MM function and the SM function.

[0064] HSS_A50 is a control node that is connected to MME_A40, AAA and SCEF and manages subscriber information. The subscriber information HSS_A50 is used, for example, during access control to the MME_A40. The HSS_A50 can optionally be connected to a location control device other than the MME_A40. For example, HSS_A50 can be connected to CPF_A140.

[0065] In addition, HSS_A50 and UDM (Unified Data Management)_A245 may be configured as different devices and/or NFs, or may be configured as the same device and/or NFs.

[0066] AAA connects to PGW30, HSS_A50, PCRF and WLAN ANa70 and performs access control on UE_A10 connected via WLAN ANa70.

[0067] The PCRF connects to PGW_A30, WLAN ANa75, AAA, DN_A5 and/or PDN_A6 and performs QoS control for data delivery. For example, the PCRF performs QoS control for the communication path between UE_A10 and DN_A5 and/or PDN_A6. The PCRF may further be a device configured to create and/or manage a Policy and Charging Control (PCC) rule and/or a routing rule used by each of the devices to transmit and/or receive user data.

[0068] In addition, the PCRF may be a policy control function (PCF) with the ability to create and/or manage a policy. More specifically, PCRF can be connected to UPF_A235.

[0069] The ePDG is connected to the PGW30 and the WLAN ANb75 and delivers user data as a gateway between the core network_A90 and the WLAN ANb75.

[0070] The SGSN is a control device that is connected to UTRAN_A20, GERAN and SGW_A35 and performs location control between a 3G/2G access network (UTRAN/GERAN) and an LTE (4G) access network (E-UTRAN). In addition, the SGSN performs the functions of PGW and SGW selection, UE_A10 time zone management, and MME_A40 selection during E-UTRAN handover.

[0071] SCEF is a relay device that connects to DN_A5 and/or PDN_A6, MME_A40 and HSS_A50 and acts as a gateway connecting DN_A5 and/or PDN_A6 to core network_A90 and transmitting user data. Moreover, SCEF can act as a gateway for non-IP communication. The SCEF may further perform the function of converting between non-IP communication and IP communication. In addition, a plurality of such gateways may be deployed in the core network_A90. In addition, multiple gateways may also be deployed connecting core network_A90 to one DN_A5, PDN_A6 and/or DN. In addition, SCEF may be configured outside or within the core network.

[0072] Next, reference network_B190 will be described. The backbone network_B190 may include at least one of an authentication server function (AUSF), an access and mobility management function (AMF)_A240, a network unstructured storage function (UDSF), a network exposure function (NEF), a network repository function (NRF) , Policy Management Functions (PCF), Session Management Functions (SMF)_A230, Unified Data Management (UDM), User Plane Functions (UPF)_A235, Application Functions (AF), and Non-3GPP Network Interworking Functions (N3IWF). In addition, they can be configured as NF (network functions). NF may refer to a processing function configured on the network.

[0073] For simplicity, FIG. 4 of the above items only show AMF (AMF_A240), SMF (SMF_A230) and UPF (UPF_A235), but this does not mean that items (devices and/or network functions (NF)) other than the above are not included in them. Note that for simplicity, UE_A10 is also called UE, AMF_A240 is also called AMF, SMF_A230 is also called SMF, UPF_A235 is also called UPF, and DN_A5 is also called DN.

[0074] In addition, in FIG. 4 shows the N1 interface (hereinafter referred to as the reference point), the N2 interface, the N3 interface, the N4 interface, the N6 interface, the N9 interface, and the N11 interface. In this case, the N1 interface is the interface between UE and AMF, the N2 interface is the interface between (R)AN (Access Network) and AMF, and the N3 interface is the interface between (R)AN (Access Network) and UPF, the N4 interface is the interface between SMF and UPF, interface N6 is the interface between UPF and DN, interface N9 is the interface between UPF and UPF, and interface N11 is the interface between AMF and SMF. These interfaces can be used to perform communication between devices. In this case, (R)AN will also be referred to as NG RAN.

[0075] Each device included in the core network_B190 will be briefly described below.

[0076] First, AMF_A240 is connected to another AMF, SMF (SMF_A230), access network (ie UTRAN_A20, E-UTRAN_A80 or NG-RAN_A120), UDM, AUSF and PCF. The AMF_A240 may perform the function of registration management, connection management, reachability management, UE_A10 mobility management or the like, session management (SM) message transmission between UE and SMF, access authentication (or access authorization), security anchor function (SEA), management security context (SCM), N2 interface support for the N3IWF, support for transmitting and/or receiving signals from and/or from the NAS UE by the N3IWF, authentication of the UE connected by the N3IWF, registration management (RM) state management, connection management (CM ), etc. In addition, one or more AMFs_A240 functions may be deployed within the core network_B190. In addition, AMF_A240 may be an NF managing one or more network slice instances (NSIs). In addition, AMF_A240 may also be a Common Control Plane Network Function (CCNF; Common CPNF) shared by multiple NSIs.

[0077] In addition, the RM state includes an unregistered state (RM-DEREGISTERED state) and a registered state (RM-REGISTERED state). In the RM-DEREGISTERED state, the UE does not register with the network, so there is no valid location or routing information for the UE in the UE context in the AMF, hence the AMF cannot reach the UE. In the RM-REGISTERED state, the UE registers with the network so that the UE can receive services that require registration with the network.

[0078] In addition, the CM state includes an unconnected state (CM-IDLE state) and an established connected state (CM-CONNECTED state). In the CM-IDLE state, the UE is in the RM-REGISTERED state, but does not have a NAS signaling connection established with the AMF via the N1 interface. In addition, in the CM-IDLE state, the UE does not have an N2 interface connection (N2 connection) or an N3 interface connection (N3 connection). On the other hand, in the CM-CONNECTED state, the UE has a NAS signaling connection established with the AMF on the N1 interface. In addition, in the CM-CONNECTED state, the UE may have an N2 interface connection (N2 connection) and/or an N3 interface connection (N3 connection).

[0079] In addition, the SMF_A230 may have the following functions: a session management function (SM) for PDU sessions or the like, an IP address assignment and management function for a UE, a UPF selection and management function, a UPF configuration function for routing of traffic to the corresponding destination, a downlink data arrival reporting function (downlink data notification), a function for providing SM information unique to the AN (each AN) to be transmitted to the AN via the N2 interface by AMF, a continuity mode detection function session and service (SSC) for a session, a roaming function, and the like. In addition, SMF_A230 can be connected to AMF_A240, UPF_A235, UDM, and PCF.

[0080] In addition, UPF_A235 is connected to DN_A5, SMF_A230, another UPF, and an access network (i.e., UTRAN_A20, E-UTRAN_A80, or NG-RAN_A120). The UPF_A235 may have the following functions: anchor for intra-RAT or inter-RAT mobility, packet routing and forwarding, uplink classifier (CL UL) function to support routing of multiple traffic flows for one DN, point function branches for multihoming PDU session support, user plane QoS processing, uplink traffic inspection, downlink packet buffering and downlink data notification triggering function, etc. In addition, the UPF_A235 may be a relay device, which transmits user data, acting as a gateway between DN_A5 and backbone_B190. The UPF_A235 may further act as a gateway for IP and/or non-IP communication. In addition, the UPF_A235 may be provided with a function for performing IP communication, or may be provided with a function for converting between non-IP communication and IP communication. In addition, multiple deployed gateways can act as gateways to connect the core_B190 to the same DN. In addition, the UPF_A235 may be connected to other NFs, or may be connected to each device via other NFs.

[0081] It should be noted that a UPF_C239 (also referred to as a branch point or uplink classifier), which is a UPF other than UPF_A235, may be present as a device or NF between UPF_A235 and the access network. If UPF_C239 is present, a PDU session between UE_A10 and DN_A5 is established by the access network, UPF_C239 and UPF_A235.

[0082] In addition, AUSF is connected to UDM and AMF_A240. AUSF functions as an authentication server.

[0083] Thanks to UDSF, all NFs are provided with the function of storing or restoring information in the form of unstructured data.

[0084] The NEF provides the means to securely deliver services and capabilities obtained over the 3GPP network. The information received from the other NF is stored as structured data.

[0085] When the NRF receives an NF discovery request from an NF instance, the NRF provides the NF with information about the discovered NF instances or holds information about the available NF instances or services supported by the instances.

[0086] The PCF is connected to the SMF (SMF_A230), AF and AMF_A240. The PCF provides a policy rule, and so on.

[0087] UDM is connected to AMF_A240, SMF (SMF_A230), AUSF and PCF. The UDM includes the UDM FE (Application Front End) and the User Data Repository (UDR). The UDM FE handles authentication information (credentials), location management, subscriber management (subscription management), etc. The UDR stores the data required to be provided by the UDM FE and the policy profiles required by the PCF.

[0088] AF is connected to the PCF. AF influences traffic routing or participates in policy management.

[0089] The N3IWF performs the functions of establishing an IPsec tunnel with the UE, relaying NAS (N1) signaling between the UE and the AMF, processing the N2 signaling transmitted from the SMF and relayed by the AMF, establishing an IPsec security association (IPsec SA), relaying the user plane packet between the UE and UPF, AMF selection, etc.

[0090] In addition, the S1 mode is a UE mode in which messages can be transmitted and received via the S1 interface. The S1 interface may further include an S1-MME interface, an S1-U interface, and an X2 interface that connects the radio base stations.

[0091] A UE in S1 mode may access, for example, EPC via an eNB performing an E-UTRA function or EPC via an en-gNB performing a NR function.

[0092] Although the EPC access via the eNB performing the E-UTRA function and the EPC access via the en-gNB performing the NR function are set to S1 mode, they can be set to different modes, respectively.

[0093] In addition, the N1 mode is a UE mode in which the UE can access the 5GC via the 5G access network. In addition, the N1 mode may also be a UE mode in which messages can be sent and received over the N1 interface. The N1 interface may further include an N1 interface and an Xn interface connecting the radio base stations.

[0094] A UE in N1 mode may access, for example, 5GC via an ng-eNB performing an E-UTRA function or 5GC via a gNB performing an NR function.

[0095] In addition, 5GC access via ng-eNB performing E-UTRA function and 5GC access via gNB performing NR function are set to N1 mode, but may be set to different modes, respectively.

[0096] [1.2. Configuration of each device]

[0097] Hereinafter, the configuration of each device will be described. It should be noted that some or all of the functions of each device and each device block described below may function on physical hardware, or may function on logical hardware that is actually configured on general purpose hardware.

[0098] [1.2.1. UE Configuration]

[0099] First of all, in FIG. 5 shows an example hardware configuration of UE_A10. As shown in FIG. 5, UE_A10 includes a control unit_A500, a transmit and/or receive unit_A520, and a storage unit_A540. Transmitting and/or receiving unit_A520 and storage unit_A540 are connected to control unit_A500 via a bus. In addition, an external antenna 410 is connected to the transmitting and/or receiving unit_A520.

[00100] The control unit_A500 is a functional unit for managing the entire UE_A10 and realizes various processing of the entire UE_A10 by reading and executing various types of information and programs stored in the storage unit_A540.

[00101] The transmitting and/or receiving unit_A520 is a functional block for connecting the UE_A10 to a base station (UTRAN_A20, E-UTRAN_A80 or NG-RAN_A120) and/or to a wireless LAN (WLAN AN) access point in an access network and to connect to the network access. In other words, UE_A10 may connect to a base station and/or access point in an access network via an external antenna 410 connected to transmit and/or receive unit_A520. In particular, UE_A10 may transmit and/or receive user data and/or control information to and/or from a base station and/or access point in an access network via an external antenna 410 connected to and/or from transmit and/or receive unit_A520.

[00102] The storage unit_A540 is a functional unit that stores programs, data, and the like for each operation of the UE_A10, and includes, for example, a hard disk drive (HDD), a solid state drive (SSD), etc. The storage unit_A540 stores the identification information, control information, flag, parameter, rule, policy, etc. included in the control message transmitted and/or received in the communication procedure described below.

[00103] [1.2.2. eNB/NR node]

[00104] Next in FIG. 6 shows an example configuration of the device eNB_A45 and NR-node_A122. As shown in FIG. 6, the eNB_A45 and the NR node _A122 include a control_B600, a network connection_B620, a transmission and/or reception_B630, and a storage_B640. The network connection_B620, the transmission and/or reception_B630 and the storage_B640 are connected to the control_B600 via a bus. In addition, an external antenna 510 is connected to the transmitting and/or receiving unit_B630.

[00105] The control unit_B600 is a functional unit for managing the entire eNB_A45 and the entire NR node_A122, and realizes various processing of the entire eNB_A45 and the entire NR node_A122 by reading and executing various types of information and programs stored in the storage unit_B640.

[00106] Network connection block_B620 is a functional block for connecting eNB_A45 and NR node_A122 to AMF_A240 and UPF_A235 within the core network. In other words, eNB_A45 and NR-node_A122 can be connected to AMF_A240 and UPF_A235 within the core network via network connection block_B620. In particular, eNB_A45 and NR-node_A122 can transmit and/or receive user data and/or control information to and/or from AMF_A240 and/or UPF_A235 via network connection unit_B620.

[00107] Transmitting and/or receiving block_B630 is a functional block for connecting eNB_A45 and NR node_A122 to UE_A10. In other words, eNB_A45 and NR-node_A122 can transmit and/or receive user data and/or control information to and/or from UE_A10 via transmit and/or receive unit_B630.

[00108] Storage_B640 is a functional block for storing programs, data, and the like required for each operation of eNB_A45 and NR-node_A122. For example, the storage unit_B640 includes a semiconductor memory, an HDD, an SSD, and the like. The storage unit_B640 stores identification information, control information, a flag, a parameter, and the like included in a control message transmitted and/or received in the communication procedure described below. The storage unit_B640 may store context information for each UE_A10.

[00109] [1.2.3. MME/AMF configuration]

[00110] Next, in FIG. 7 shows an example configuration for an MME_A40 and/or AMF_A240 device. As shown in FIG. 7, MME_A40 and/or AMF_A240 include a control_C700, a network connection_C720, and a storage_C740. The network connection_C720 and the storage unit_C740 are connected to the control unit_C700 via a bus. In addition, the context 642 is stored in storage_C740.

[00111] The control_C700 is a functional block for managing the entire MME_A40 or AMF_A240, and realizes various processing of the entire AMF_A240 by reading and executing various types of information and programs stored in the storage unit_C740.

[00112] Network connection block_C720 is a functional block for connecting MME_A40 and/or AMF_A240 to other MME_A40, AMF_240, SMF_A230, base station (UTRAN_A20, E-UTRAN_A80 or NG-RAN_A120) within an access network and/or to a wireless access point LAN (WLAN AN), UDM, AUSF and PCF. In other words, the MME_A40 or AMF_A240 can transmit data/or control information to the base station and/or access point within the access network, UDM, AUSF and PCF and/or receive from them via the network connection unit_C720.

[00113] The storage block_C740 is a functional block for storing programs, data, and the like required for each operation of the MME_A40 or AMF_A240. For example, the storage unit_B740 includes a semiconductor memory, an HDD, an SSD, and the like. The storage unit_B740 stores identification information, control information, a flag, a parameter, and the like included in a control message transmitted and/or received in the communication procedure described below. The context 642 stored in the storage unit_C740 may include a context stored per UE, a context stored per session PDU, and a context stored per channel. The context stored for each UE may include International Mobile Subscriber Identity (IMSI), Integrated Services Digital Network Mobile Subscriber Number (MSISDN), MM State, Global Temporary Unique Identifier (GUTI), ME ID, UE radio access capabilities , UE network capability, MS network capability, access restriction, tunnel endpoint identifier (F-TEID) MME, SGW F-TEID, eNB address, UE MME identifier S1AP, eNB UE identifier S1AP, NR node address, NR-identifier host, WAG address, and WAG ID. In addition, the context stored for each session PDU may include the APN used, session type assigned, IP address(es), PGW F-TEID, SCEF identifier, and default channel. In addition, the context stored for each channel may include EPS channel identifier, transaction identifier (TI), TFT, SGW F-TEID, PGW F-TEID, MME F-TEID, eNB address, NR node address, WAG, eNB ID, NR node ID, and WAG ID.

[00114] [1.2.4. SMF Configuration]

[00115] Next, in FIG. 8 shows an example hardware configuration of the SMF_A230. As shown in FIG. 8, SMF_A230 includes a control unit_D800, a network connection_unit_D820, and a storage unit_D840. The network connection_D820 and the data storage_unit_D840 are connected to the controller_D800 via a bus. In addition, context 742 is stored in storage_D840.

[00116] The SMF_A230 control_D800 is a functional block for managing the entire SMF_A230, and realizes various processing of the entire SMF_A230 by reading and executing various types of information and programs stored in the storage unit_D840.

[00117] In addition, SMF_A230 network connection block_D820 is a functional block for connecting SMF_A230 to AMF_A240, UPF_A235, UDM and PCF. In other words, SMF_A230 can transmit data and/or control information to and/or receive data and/or control information from AMF_A240, UPF_A235, UDM, and PCF via network connection unit_D820.

[00118] In addition, the SMF_A230 storage unit_D840 is a functional unit for storing programs, data, and the like required for each operation of the SMF_A230. The SMF_A230 storage unit_D840 includes, for example, a semiconductor memory, an HDD, an SSD, or the like. The SMF_A230 data storage unit_D840 stores identification information, control information, a flag, a parameter, etc. received in the communication procedure described below. In addition, the context 742 stored in the SMF_A230 data storage unit_D840 may include a context stored per UE, a context stored per APN, a context stored per session PDU, and a context stored per channel. The context stored for each UE may include IMSI, ME identifier, MSISDN, and RAT type. The context stored for each APN may include the APN in use. It should be noted that the context stored for each APN may be stored for each data network ID. The context stored for each PDU session may include the assigned session type, IP address(es), F-TEID SGW, F-TEID PGW, and default channel. The context stored for each channel may include an EPS, TFT, SGW F-TEID, and PGW F-TEID channel identifier.

[00119] [1.2.5. PGW/UPF Configuration]

[00120] Next, in FIG. 8 shows an example configuration for a PGW_A30 and/or UPF_A235 device. As shown in FIG. 8, each of PGW_A30 and/or UPF_A235 includes a control_D800, a network connection_D820, and a storage_D840. The network connection_D820 and the data storage_unit_D840 are connected to the controller_D800 via a bus. In addition, context 742 is stored in storage_D840.

[00121] The PGW_A30 or UPF_A235 control unit_D800 is a functional unit for controlling the entire PGW_A30 or UPF_A235 and realizes various processing of the entire PGW_A30 or UPF_A235 by reading and executing various types of information and programs stored in the storage unit_D840.

[00122] In addition, the PGW_A30 or UPF_A235 network connection block_D820 is a functional block for connecting the PGW_A30 or UPF_A235 to a DN (i.e., DN_A5), SMF_A230, another UPF_A235, and an access network (i.e., UTRAN_A20, E-UTRAN_A80 and NG-RAN_A120). In other words, the UPF_A235 may transmit user data and/or control information to a DN (i.e., DN_A5), SMF_A230, another UPF_A235, and an access network (i.e., UTRAN_A20, E-UTRAN _A80, or NG-RAN_A120) and/or receive from them through block_D820 connecting to the network.

[00123] In addition, the UPF_A235 storage unit_D840 is a functional unit for storing programs, data, and the like required for each operation performed by the UPF_A235. The storage unit_D840 UPF_A235 includes, for example, a semiconductor memory, an HDD, an SSD or the like. The storage unit_D840 UPF_A235 stores identification information, control information, a flag, a parameter, etc. received in the communication procedure described below. In addition, the context 742 stored in the UPF_A235 storage unit_D840 may include a context stored per UE, a context stored per APN, a context stored per session PDU, and a context stored per channel. The context stored for each UE may include IMSI, ME identifier, MSISDN, and RAT type. The context stored for each APN may include the APN in use. It should be noted that the context stored for each APN may be stored for each data network ID. The context stored for each PDU session may include the assigned session type, IP address(es), F-TEID SGW, F-TEID PGW, and default channel. The context stored for each channel may include an EPS, TFT, SGW F-TEID, and PGW F-TEID channel identifier.

[00124] [1.2.6. Information stored in the data storage unit of each device described above]

[00125] Next, each piece of information stored in the data storage unit of each of the devices described above will be described.

[00126] IMSI (International Mobile Subscriber Identity) is a permanent identification information of a subscriber (user), and is an identification information assigned to a user using a UE. The IMSI stored in UE_A10, MME_A40/CPF_A140/AMF_A2400 and SGW_A35 may be the same as the IMSI stored in the HSS_A50 server.

[00127] The EMM state/MM state is the mobility management state of UE_A10 or MME_A40/CPF_A140/AMF_A240. For example, the EMM state/MM state may be an EMM-REGISTERED (registered state) state in which the UE_A10 is registered with the network and/or an EMM-DEREGISTERD (unregistered state) state in which the UE_A10 is not registered with the network. In addition, the EMM state/MM state may be an ECM-CONNECTED state, in which a connection is maintained between the UE_A10 and the core network, and/or an ECM-IDLE state, in which the connection is dropped. It should be noted that the EMM state/MM state may be information for distinguishing the state in which the UE_A10 is registered with the EPC from the state in which the UE_A10 is registered with the NGC or 5GC.

[00128] The Global Temporary Unique Identifier (GUTI) is the temporary identification information of the UE_A10. The GUTI includes the identification information (Globally Unique MME Identifier (GUMMEI)) MME_A40/CPF_A140/AMF_A240 and the identification information (M-Temporary Mobile Subscriber Identity (M-TMSI)) UE_A10 in a specific MME_A40/CPF_A140/AMF_A240. The ME identifier is a UE_A10 or ME identifier and may be, for example, an international mobile equipment identifier (IMEI) or an IMEI software version (IMEISV). MSISDN is the base telephone number of UE_A10. The MSISDN stored in the MME_A40/CPF_A140/AMF_A240 may be information included in the storage unit HSS_A50. In addition, the GUTI may include information to identify CPF_140.

[00129] MME F-TEID is information for identifying MME_A40/CPF_A140/AMF_A240. The MME F-TEID may include an IP address MME_A40/CPF_A140/AMF_A240, a tunnel endpoint identifier (TEID) MME_A40/CPF_A140/AMF_A240, or both. In addition, the IP address of MME_A40/CPF_A140/AMF_A240 and TEID of MME_A40/CPF_A140/AMF_A240 can be stored separately. In addition, the MME F-TEID may be identification information for user data or identification information for control information.

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

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

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

[00133] In addition, the APN may be identification information for identifying the core network and an external network such as a DN. The APN may also be additionally used as information to select a gateway such as PGW_A30/UPGW_A130/UPF_A235 to connect to the A_90 core network. It should be noted that the APN may be a data network name (DNN). Thus, an APN may be represented by a DNN and a DNN may be represented by an APN.

[00134] In addition, the APN may be an identity for identifying such a gateway or an identity for identifying an external network, such as a DN. When a plurality of gateways is deployed connecting the core network and the DN, there may additionally be a plurality of gateways that may be selected according to the APN. In addition, from such a plurality of gateways, one gateway may be selected in a different manner in which identification information other than the APN is used.

[00135] The UE radio access capability information is the radio access capability identification information for the UE_A10. The network capabilities of the UE include a security algorithm and a key derivation function supported by UE_A10. MS network capabilities are information that, for a UE_A10 having the function(s) of GERAN_A25 and/or UTRAN _A20, includes one or more pieces of information required for SGSN_A42. The access restriction is registration information for access restriction. The eNB address is the IP address of eNB_A45. The MME ID of the UE S1AP is information for identifying the UE_A10 in the MME_A40/CPF_A140/AMF_A240. The UE S1AP eNB ID is information for identifying the UE_A10 in the eNB_A45.

[00136] The used APN is the recently used APN. The APN used may be a data network identifier. The APN may include a network identity and a default carrier identity. The APN used may further be information for identifying the DN with which the session PDU is created.

[00137] The assigned session type is the session type information of the PDU. The assigned session type may be the assigned PDN type. The possible session types of the PDU are "IP" or "non-IP". In addition, when the session type of the PDU is IP, information about the PDN type allocated by the network may be further included. Note that the assigned session type can be IPv4, IPv6, or IPv4v6.

[00138] In addition, if the IP address is not specified, it refers to the IP address allocated to the UE. An IP address can be an Ipv4 address, an IPv6 address, an Ipv6 prefix, or an interface identifier. It should be noted that when the assigned session type is non-IP, the IP address element may not be included.

[00139] The DN identifier is identification information for identifying the core network_B190 and an external network such as a DN. The DN may also optionally be used as information to select a gateway such as UPGW_A130 or PF_A235 connected to the core_B190.

[00140] In addition, the DN identifier may be identification information for identifying such a gateway or identification information for identifying an external network such as a DN. When a plurality of gateways is deployed connecting the backbone_B190 and the DN, a plurality of gateways may additionally be present, which may be selected according to the DN identifier. In addition, from such a plurality of gateways, one gateway may be selected in a different manner, in which identification information other than the DN is used.

[00141] In addition, the DN may be information that is equivalent to or different from an APN. If the DN ID is information other than APN, each device can manage information about the corresponding relationship between the DN ID and the APN, perform the APN request procedure using the DN ID, or perform the DN request procedure using the APN.

[00142] The SCEF identifier is the SCEF_A46 IP address used in the PDU session. The default channel is information obtained and/or generated during the creation of a PDU session, and is an EPS channel identification information for identifying a default channel associated with a PDU session.

[00143] The EPS channel ID is the EPS channel identification information. In addition, the EPS channel identifier may be identification information for identifying a signaling radio bearer (SRB) and/or a control plane radio bearer (CRB), or identification information for identifying a data radio bearer (DRB). A transaction identifier (TI) is identification information for identifying a bidirectional message flow (transaction). It should be noted that the EPS channel identifier may be an EPS channel identification information for identifying a dedicated channel. Thus, the EPS channel identifier may be identification information for identifying an EPS channel other than the default channel. The TFT represents all the packet filters associated with the EPS link. The TFT is information for identifying a portion of the transmitted and/or received pieces of user data, and the UE_A10 uses the EPS channel associated with the TFT to transmit and/or receive the user data identified by the TFT. In other words, UE_A10 uses a radio bearer (RB) associated with the TFT to transmit and/or receive user data identified by the TFT. Further, with the TFT, user data such as application data transmitted and/or received via the corresponding transmission channel may be associated, and may be identification information for identifying application data. In addition, UE_A10 may use the default channel to transmit and/or receive user data that cannot be identified by the TFT. In addition, UE_A10 may store in advance the TFT associated with the default channel.

[00144] The default channel is an EPS channel identification information for identifying a default channel associated with a PDU session. It should be noted that the EPS channel may be a logical communication path established between UE_A10 and PGW_A30/UPGW_A130/UPF_A235, or a communication path representing a PDN connection/PDU session. The EPS channel may further be a default channel or a dedicated channel. In addition, the EPS channel may include a RB created between UE_A10 and a base station and/or access point within an access network. In addition, the RB and the EPS channel may be associated on a one-to-one basis. Therefore, the RB identification information and the EPS channel identification information may be related to each other on a one-to-one basis, or may be the same identification information. It should be noted that RB may be SRB and/or CRB or DRB. In addition, the default channel may be information that the UE_A10 and/or SGW_A35 and/or PGW_A30/UPGW_A130/SMF_A230/UPF_A235 receive from the core network at the time the PDU session was created. It should be noted that the default channel is an EPS channel originally created when connecting a PDN/in a PDU session, and is an EPS channel that can only be created once when connecting to a PDN/in a PDU session. The default channel may also be an EPS channel, which may be used to transmit user data that is not associated with the TFT. In addition, a dedicated channel is an EPS channel created after creating a default channel when connecting to a PDN/in a PDU session, and is an EPS channel that can be created repeatedly when connecting to a PDN/in a PDU session. The dedicated channel is an EPS channel that can be used to transmit user data associated with the TFT.

[00145] The user ID is information for identifying a subscriber. The user identifier may be an IMSI or an MSISDN. The user identifier may also optionally be identification information other than IMSI or MSISDN. The serving node information is information for identifying the MME_A40/CPF_A140/AMF_A240 used in the PDU session and may be an IP address for the MME_A40/CPF_A140/AMF_A240.

[00146] The eNB address is the IP address of the eNB_A45. The eNB ID is information for identifying the UE in the eNB_A45. The MME address is the IP address of MME_A40/CPF_A140/AMF_A240. The MME ID is information for identifying the MME_A40/CPF_A140/AMF_A240. The NR node address is the IP address of NR node_A122. The NR node ID is information for identifying the NR node_A122. The WAG address is the IP address of the WAG. The WAG ID is information for identifying the WAG.

[00147] An anchor or anchor point is a UFP that functions as a gateway for DNs and PDU sessions. The UPF used as the anchor point may also be a PDU session anchor or anchor.

[00148] The SSC mode is a session and service continuity mode supported by the system and/or each device in the 5GC. More specifically, the SSC mode may be a mode providing for the type of session and service continuity supported by the PDU session created between UE_A10 and the anchor point. In this case, the anchor point can be either UPGW or UPF_A235. In addition, the SSC mode may be a mode providing the type of session continuity and service configured for each PDU session. The SSC mode may further include three modes, such as SSC mode 1, SSC mode 2, and SSC mode 3. The SSC mode is associated with the anchor point and cannot be changed during the creation of a PDU session.

[00149] In addition, SSC mode 1 of the present embodiment is a session and service continuity mode in which, when UE_A10 connects to a network, the same UPF is continuously maintained as an anchor point regardless of access technologies such as Radio Access Technology (RAT) , and from the used cell. More specifically, SSC Mode 1 may be a mode that ensures session and service continuity without changing the anchor point used by the created session PDU, even under UE_A10 mobility conditions.

[00150] SSC Mode 2 of the present invention is further a session and service continuity mode in which, when an anchor point associated with one SSC Mode 2 is included in a PDU session, the PDU session is first released and then another PDU session is created. More specifically, SSC mode 2 is a mode in which, in the case of an anchor point movement, a PDU session is first deleted and then a new PDU session is created.

[00151] In addition, SSC mode 2 is a session and service continuity mode in which the same UPF is continuously maintained as an anchor point only within the service area of the UPF. More specifically, SSC Mode 2 may be a mode that allows session and service continuity without changing the UPF used by the created session PDU as long as UE_A10 is within the UPF service area. In addition, SSC mode 2 may be a mode in which session and service continuity is ensured by changing the UPF used by the created session PDU under the mobility of a UE_A10, such as a UE_A10 leaving the UPF service area.

[00152] In this case, the TUPF service area may be an area in which one UPF can perform a session and service continuity function, or a subset of the access network, such as a RAT or a cell, used when connecting UE_A 10 to the network. The access network subset may further be a network including one or more RATs and/or cells, or may be a tracking area (TA).

[00153] In addition, SSC Mode 3 of the present embodiment is a session and service continuity mode in which another PDU session can be created between a new anchor point and a UE for the same DN, and the PDU session does not need to be released between UE and anchor point.

[00154] In addition, SSC mode 3 is a session and service continuity mode in which a new session PDU and/or communication path can be created using a new UPF for the same DN before the session PDU and/or communication path is disconnected, created between UE_A10 and UPF. In addition, SSC mode 3 may be a session and service continuity mode allowing UE_A10 multihoming.

[00155] Additionally or alternatively, SSC mode 3 may be a session and service continuity mode in which multiple PDU sessions and/or UPFs associated with PDU sessions may be allowed. In other words, in SSC Mode 3, each device can maintain session and service continuity by using multiple PDU sessions, or can maintain session and service continuity by using multiple TUPFs.

[00156] In this case, when each device creates a new PDU session and/or communication path, the network may choose a new UPF, or the new UPF may be the optimal UPF for the location where UE_A10 connects to the network. When the plurality of PDU and/or UPF sessions used by PDU sessions are valid, UE_A 10 may immediately further correlate application and/or flow data exchanges with newly created PDU sessions, or may do so based on the execution of data exchanges.

[00157] [1.3. Description of initial procedure]

[00158] Next, in order to avoid duplication of descriptions, before describing the detailed procedure for performing the initial procedure in the present embodiment, terminology specific to the present embodiment and basic identification information used in each procedure will be described in advance.

[00159] In the present embodiment, the network refers to at least some of Access Network_A20/80, Access Network_B80/120, Core Network_A90, Core Network_B190, DN_A5, and PDN_A6. In addition, one or more devices included in at least some of the access network_A20/80, access network_B80/120, core network_A90, core network_B190, DN_A5, and PDN_A6 may also be referred to as a network or a network device. In other words, the expression "a network performs transmission and/or reception of a message and/or performs a procedure" means that a device (network device) in the network transmits and/or receives a message and/or performs a procedure.

[00160] In the present embodiment, the session management (SM) message (also referred to as non-access layer (NAS) SM message or SM message) may be a NAS message used in a procedure for SM (also referred to as session management procedure or SM procedure), or may be a control message sent and/or received between UE_A10 and SMF_A230 by AMF_A240. The SM message may further include a PDU session creation request message, a PDU session creation approval message, a PDU session end message, a PDU session rejection message, a PDU session change request message, a PDU session change approval message, a rejecting a PDU session change, and the like. In addition, the procedure for the SM may include a procedure for creating a PDU session, a procedure for changing a PDU session, and the like.

[00161] In the present embodiment, the tracking area (also referred to as TA) is a range that may be designated by the location information of UE_A10 controlled by the core network, and may include, for example, one or more cells. In addition, the TA may be a range in which a control message such as a paging message is broadcast, or a range in which the UE_A10 can move without performing a handover procedure.

[00162] In the present embodiment, the TA list is a list including one or more TAs allocated to UE_A10 by the network. In addition, when UE_A10 moves within one or more TAs included in the TA list, UE_A10 may move without performing a registration procedure. In other words, the TA list may be an infogroup related to an area in which the UE_A10 can move without performing a registration procedure.

[00163] In the present embodiment, a network slice (NS) is a logical network with specific network capabilities and network characteristics. Hereinafter, the network slice will also be referred to as the NW slice.

[00164] A Network Slice Instance (NSI) in the present embodiment is an object of each of one or more network slices configured in the core network_B190. In addition, the NSI in the present embodiment may include a virtual network function (NF) generated using a network slice pattern (NST). In this case, an NST is associated with a resource request to provide a required communication service or capability, and is a logical expression of one or more NFs (network functions). In other words, the NSI may be a union consisting of a plurality of NFs in the reference network_B190. Further, the NSI may be a logical network capable of classifying user data transmitted using a service or the like. A network slice may include at least one or more NFs. An NF included in a network slice may or may not be a device shared by another network slice. A UE_A10 and/or a device within a network may be allocated to one or more network slices based on NSSAI and/or S-NSSAI, and/or UE usage type, and/or one or more slice type identifiers, and/or one or more IDs NS registration information and/or APN.

[00165] In the present embodiment, S-NSSAI is an abbreviation for assistance information for selecting an individual network slice, and is information for identifying a network slice. The S-NSSAI may include SST (Slice/Service Type) and SD (Slice Differentiator). The S-NSSAI may include only SST or both SST and SD. In this case, the SST is information about the operation of the network slices expected in terms of functions and services. In addition, the SD may be information supplementing the SST at the time of selecting one NSI from a plurality of NSIs determined by the SST. The S-NSSAI may be information unique to each public land mobile network (PLMN), or may be standard information common to PLMNs, or may be information unique to each carrier, different for each PLMN.

[00166] More specifically, SST and/or SD may be standard information (standard value) common to PLMNs, or may be information (non-standard value) unique to each network operator, different for each PLMN. In addition, the network may store one or more S-NSSAI fragments in the UE_A10 registration information as the default S-NSSAI.

[00167] The Supplementary Information for Network Slice Selection (NSSAI) in the present embodiment is a group of Supplemental Information for Selecting a Single Network Slice (S-NSSAI). Each S-NSSAI fragment included in the NSSAI is information to help the access or core network select an NSI. UE_A10 may store the NSSAI allowed by the network for each PLMN. In addition, the NSSAI may be information used to select the AMF_A240.

[00168] Operator A's network according to the present embodiment is a network operated by network operator A (operator A). In this case, for example, operator A may deploy an NW slice shared by operator B, which will be described below.

[00169] Operator B's network according to the present embodiment is a network operated by network operator B (operator B). In this case, for example, operator B may deploy an NW slice shared by operator A.

[00170] The first NW slice in the present embodiment is the NW slice to which the generated session PDU belongs when the UE connects to a specific DN. It should be noted that, for example, the first NW slice may be an NW slice that is managed within Operator A's network, or it may be an NW slice that is typically managed within Operator B's network.

[00171] The second NW slice in the present embodiment is an NW slice having a different session PDU and configured to connect to a DN serving as a connection destination of the PDU session belonging to the first NW slice. It should be noted that the first NW slice and the second NW slice may be controlled by the same operator or they may be controlled by different operators.

[00172] In the present embodiment, an equivalent PLMN refers to a PLMN that is considered the same PLMN as any PLMN in the network.

[00173] A dedicated core network (DCN) in the present embodiment is one or more subscriber-specific dedicated core networks configured in core network_A90. More specifically, a DCN for a UE registered as a machine-to-machine (M2M) communication function user may be configured in Core Network_A90, for example. In addition, for a UE without a proper DCN within the core network_A90, a default DCN may be configured. At least one or more MME_40 or SGSN_A42 may be further deployed in the DCN, and at least one or more SGW_A35, PGW_A30 or PCRF_A60 may be further deployed in the DCN. It should be noted that a DCN may be identified with a DCN ID, and further, a UE may be assigned to one DCN based on information such as the UE's usage type and/or the DCN ID.

[00174] The first timer in the present embodiment is a timer for initiating a session management procedure, such as a PDU session creation procedure, and/or for controlling the transmission of a session management (SM) message, such as a PDU session request message, and may be information containing a backoff timer value for controlling session control operating modes. Hereinafter, the first timer and/or backoff timer may be referred to as a timer. During the operation of the first timer, any device may be prohibited from initiating a session management procedure and/or sending and receiving an SM message. It should be noted that the first timer may be configured to be associated with at least one congestion control unit applied by the NW and/or with an overload control unit identified by the UE. For example, the first timer may be configured for at least one of an APN/DNN block, and/or an identification information block about one or more NW slices, and/or a rejection reason value block in a session control procedure, and/or a session block, rejected in the session management procedure, and/or the PTI block of the session management procedure.

[00175] It should be noted that the SM message may be a NAS message used in the procedure for session management, and may be a control message transmitted and/or received between UE_A10 and SMF_A230 by AMF_A240. The SM message may further include a PDU session creation request message, a PDU session creation approval message, a PDU session end message, a PDU session rejection message, a PDU session change request message, a PDU session change approval message, a rejecting a PDU session change; received by UE_A10. The UE may set the backoff timer received from the NW as the first timer, may set the first timer to a timer value in another method, or may set the first timer to a random value. In addition, when receiving a plurality of backoff timers from the NW, the UE may manage a plurality of “first timers” according to a plurality of backoff timers, or may select one timer value from a plurality of backoff timer values received from the NW based on a policy stored by the UE, to set the first timer to one time value and control the first timer. For example, when two backoff timer values are received, the UE sets "first timer #1" and "first timer #2" respectively to the backoff timer values received from the NW, and controls "first timer #1" and "first timer #2 ". In addition, from the plurality of backoff timer values received from the NW, one value can be selected based on the policy stored by the UE, and the first timer can be set to and controlled by this one value.

[00176] When UE_A10 receives a plurality of backoff timer values from NW, UE_A10 may manage a plurality of "first timers" in accordance with the plurality of backoff timers. Here, in order to distinguish between the plurality of "first timers" received by the UE_A10, they may be described as "first timer #1" or "first timer #2", for example. It should be noted that multiple backoff timers may be obtained in a single session control procedure or may be obtained in different session control procedures.

[00177] In this case, the first timer may be a backoff timer to suppress reconnection and be configured for a plurality of associated NW slices based on information to identify a single NW slice as described previously, or may be a backoff timer to prevent reconnection. connection and be configured without limitation for the APN/DNN combination block and one NW slice, and the first backoff timer may be a backoff timer to suppress reconnection and be configured for the APN/DNN combination block and a plurality of associated NW slices based on information to identify one NW slice.

[00178] The retry information included in the 11th identification information in the present embodiment is information by which the network (NW) informs the UE_A10 whether to allow reconnection using the same DNN information and/or S information -NSAI to request (S1100) to create a rejected session PDU.

[00179] Meanwhile, when the UE performs (S1100) a PDU session creation request not including the DNN, the information in the PDU session creation request (1100) not including the DNN is considered the same information. In addition, when the UE performs (S1100) a request to create a session of a PDU not including the S-NSSAI, the information in the request (1100) to create a session of the PDU not including the S-NSSAI is considered the same information.

[00180] It should be noted that retry information may be configured in a UTRAN access block and/or an E-UTRAN access block and/or an NR access block and/or a slice information block fragment and/or an equivalent PLMN block, and/or an S1 mode block and/or an NW mode block.

[00181] The retry information indicated in the access block (UTRAN access, E-UTRAN access, or NR access) may further be reconnect information using the same information for the network in the proposed access change. The retry information indicated in the slice block may be further defined as slice information other than the rejected slice information, and reconnection using the specified slice information may be allowed.

[00182] The retry information indicated in the equivalent PLMN block may further be information that when the PLMN changes, reconnection using the same information is allowed when the changed PLMN is equivalent to the PLMN. In addition, if the modified PLMN is not equivalent to the PLMN, the retry information may be information that reconnection using the present procedure is not allowed.

[00183] The retry information indicated in the mode block (S1 mode or N1 mode) may further be information that when the mode is changed, reconnection using the same information is allowed when the changed mode is S1 mode. In addition, as long as the changed mode is S1 mode, the retry information may also be information that reconnection using the same information is not allowed.

[00184] A network slice association rule in the present embodiment is a rule for link information identifying a plurality of network slices. It should be noted that the network slice association rule may be received in the Session Reject PDU message, or may be preconfigured in UE_A10. In addition, the last of the network slice association rules may be applied in UE_A10. Conversely, the UE_A10 mode may be based on the last network slice association rule. For example, when UE_A10 receives a new network slice association rule in a PDU session reject message, with the network slice association rule previously configured in UE_A10, UE_A10 may update the network slice association rule stored in UE_A10.

[00185] A backoff timer priority control rule according to the present embodiment is a rule configured for UE_A10 to jointly control a plurality of backoff timers that have occurred in multiple PDU sessions on a single backoff timer. For example, when conflicting or overlapping congestion control is applied and the UE contains a plurality of backoff timers, UE_A10 may simultaneously control multiple backoff timers based on the backoff timer priority control rules. It should be noted that the situation in which conflicting or overlapping congestion control occurs occurs when congestion control based on DNN only and congestion control based on both DNN and slice information are applied simultaneously, in which case congestion control is given priority. based only on DNN. It should be noted that the backoff timer priority control rule may not be limited to the above. It should be noted that the backoff timer may be the first timer included in the Session Reject PDU message.

[00186] The first state according to the present embodiment is a state in which each device has completed the registration procedure and the PDU session creation procedure, and the UE_A10 and/or each device is in a state in which one or more congestion controls from the first overload control to the fourth overload control. In this case, the UE_A10 and/or each device may be in the state in which the UE_A10 has been registered with the network (the RM-REGISTERED state) upon completion of the registration procedure, and the state in which the PDU session creation procedure has been completed may be the state in which at which UE_A10 received the PDU Session Creation Reject message from the network.

[00187] The overload control according to the present embodiment includes one or more overload controls from the first overload control to the fourth overload control. It should be noted that the control of the UE by the NW is carried out by the congestion control recognized by the UE and the first timer, and the UE can communicate with this information.

[00188] The first congestion control in the present embodiment provides for control signal overload control related to the DNN parameter. For example, when the NW detects an overload on DNN #A and the NW recognizes it as a UE-initiated session control request related to the DNN #A parameter only, the NW may apply the first congestion control. It should be noted that even when the UE-initiated session control request does not include DNN information, the NW may select the default DNN initiated by the NW and configure it as a target for congestion control. Alternatively, even when the NW recognizes it as a UE-initiated session control request including DNN #A and S-NSSAI #A, the NW may apply the first congestion control. In the case of applying the first congestion control, the UE may suppress the UE-initiated session control request related to DNN #A only.

[00189] In other words, the first congestion control according to the present embodiment is the control signal overload control related to the DNN, and may be the congestion control caused by connecting to the DNN in an overload state. For example, the first congestion control may be congestion control to restrict connection to DNN #A on all types of connections. In this case, the connection to DNN #A on all types of connections may be a connection to DNN #A when connected using S-NSSAI of all types available to the UE, and may be a connection to DNN #A via a network slice to which the UE can connect. In addition, a connection to DNN #A can be enabled without going through the network slice.

[00190] The second congestion control in the present embodiment provides for control signal overload control related to the S-NSSI parameter. For example, when the NW detects control signal congestion with respect to S-NSSAI #A and the NW recognizes it as a UE-initiated session control request related to the S-NSSAI #A parameter only, the NW may apply the second congestion control. In the case of applying the second congestion control, the UE may suppress the UE-initiated session control request related to S-NSSAI No. A only.

[00191] In other words, the second congestion control according to the present embodiment is control signal congestion control related to S-NSSAI, and may be congestion control initiated by a network slice selected based on the S-NSSAI in an overload state. For example, the second congestion control may be congestion control to restrict all connections based on S-NSSAI #A. A.

[00192] The third congestion control in the present embodiment provides for control signal overload control related to DNN and S-NSSAI parameters. For example, when the NW simultaneously detects control signal overload on DNN #A and control signal overload on S-NSSAI #A, and when the NW recognizes it as a UE initiated session control request related to DNN parameters #A and S-NSSAI # A, NW can apply the third overload control. It should be noted that even when the UE-initiated session control request does not include DNN information, the NW can select the default DNN initiated by the NW and configure its congestion target control. In the case of applying the third congestion control, the UE may suppress the UE-initiated session control request related to DNN #A and S-NSSAI #A parameters.

[00193] In other words, the third congestion control according to the present embodiment is control signal congestion control related to DNN parameters No. A and S-NSSAI, and may be congestion control initiated by connecting to a DNN via a network slice selected based on S-NSSAI in congestion state. For example, the third congestion control may be congestion control to restrict all connections to DNN #A when connecting based on S-NSSAI #A.

[00194] The fourth congestion control in the present embodiment provides for control signal overload control relating to at least one of the DNN and/or S-NSSAI parameters. For example, when the NW simultaneously detects control signal overload on DNN #A and control signal overload on S-NSSAI #A, and when the NW recognizes it as a UE-initiated session control request related to at least one of the parameters of DNN #A and /or S-NSSAI No. A, NW may apply fourth congestion control. It should be noted that even when the UE-initiated session control request does not include DNN information, the NW can select the default DNN initiated by the NW and configure its congestion target control. In the case of applying the fourth congestion control, the UE suppresses the UE-initiated session control request related to at least one of the DNN #A and/or S-NSSAI #A parameters.

[00195] In other words, the fourth congestion control according to the present embodiment is control signal congestion control related to DNN and S-NSSAI parameters, and may be congestion control initiated by a network slice selected based on S-NSSAI and connection to a DNN in an overload state. For example, the fourth congestion control may be congestion control to restrict all connections based on S-NSSAI #A, and may be congestion control to restrict connection to DNN #A on all types of connections. In other words, the fourth congestion control may be congestion control to restrict all connections to the DNN via the network slice selected based on S-NSSAI #A, and may be congestion control to restrict the connection to DNN #A on all types of connections. In this case, the connection to DNN #A on all types of connections may be a connection to DNN #A when connected using S-NSSAI of all types available to the UE, and may be a connection to DNN #A via a network slice to which the UE can connect. In addition, a connection to DNN #A can be enabled without going through the network slice.

[00196] Therefore, the fourth congestion control having DNN #A and S-NSSAI #A as parameters may be congestion control in which the first congestion control with DNN #A as a parameter and the second congestion control with S-NSSAI # A as a parameter, execute simultaneously.

[00197] The first mode in the present embodiment is a mode in which the UE stores slice information transmitted in the first session PDU creation request message together with the transmitted PDU session identification information. In the first mode of operation, the UE may store slice information transmitted in the first session PDU creation request message, or may store slice information received upon rejecting the first PDU session creation request.

[00198] The second mode in the present embodiment is a mode in which the UE sends a request to create a session PDU to connect to the same APN/DNNs as in the request to create the first session PDU using a different piece of slice information, different from the slice information specified when the first PDU session was created. In particular, the second mode may be a mode in which, when the backoff timer value received from the network is zero or invalid, the UE sends a request to create a session PDU to connect to an APN/DNN matching the APN/DNN for which the request is sent. to create the first PDU session by using a different piece of information than the slice information specified when the first PDU session was created. Alternatively, the second mode may be a mode in which when the first PDU session is rejected because the radio access of the particular PLMN to which the specified APN/DNN is connected is not supported, or when the PDU session is rejected for a temporary reason, the UE sends a creation request. session PDU to connect to an APN/DNN matching the APN/DNN included in the request to create the first session PDU by using a different piece of information than the slice information specified when creating the first session PDU.

[00199] The third mode in the present embodiment is a mode in which the UE does not send a request to create a new PDU session using the same identification information until the first timer expires when rejecting the request to create a PDU session. In particular, the third mode may also be a mode in which the UE does not send a request to create a new PDU session using the same identification information until the first timer expires, when the backoff timer value received from the network is neither zero, nor invalid. In this case, the same identity may mean that the first identity and/or the second identity included in the request to create a new session PDU are identical, or may mean that the first identity and/or the second identity transmitted in the rejected PDU session creation request are identical.

[00200] In addition, the third mode may also be a mode in which the UE does not send a request to create a new PDU session using the same identification information until the first timer expires when a different PLMN is selected or a different NW slice is selected. , upon receiving the reason for rejecting the network configuration failure, and activating the received backoff timer upon rejecting the first request to create a PDU session.

[00201] Specifically, a PDU session in which a request to create a new PDU session in the third mode is not transmitted may be a PDU session to which congestion control associated with the first timer is applied. More specifically, the third mode may be a no request to create a new session PDU for a PDU session with a connection depending on the type of congestion control associated with the first timer that uses the DNN and/or S-NSSAI associated with congestion control. It should be noted that the UE processing blocked by the current mode of operation may be the initiation of a session management procedure, including a request to create a session PDU, and/or transmission and/or reception of an SM message.

[00202] The fourth mode in the present embodiment is a mode in which the UE does not transmit a request to create a new PDU session that does not contain slice information and DNN/APN information until the first timer expires when rejecting the request to create a PDU session. In particular, the fourth mode may be a mode in which the UE does not transmit a request to create a new session PDU that does not contain slice information and DNN/APN information until the first timer expires, when the backoff timer received from the network is not neither null nor invalid.

[00203] The fifth mode in the present embodiment is a mode in which the UE does not transmit a request to create a new session PDU that uses the same identification information when declining the request to create a session PDU. In particular, the fifth mode may be a mode in which the UE does not send a request to create a new PDU session using the same identity in case the UE is in an equivalent PLMN when the PDP types supported by the UE and the network are different.

[00204] The sixth mode in the present embodiment is a mode in which the UE transmits a request to create a new PDU session as an initial procedure using the same identity when rejecting the request to create a PDU session. Specifically, the sixth mode may be a mode in which the UE transmits a request to create a new PDU session as an initial procedure using the same identity when rejecting the request to create a first PDU session due to lack of context in the PDN session of the destination in transmission. service from non-3GPP access.

[00205] The seventh mode in the present embodiment is a mode in which the UE continues the backoff timer received at the time of rejecting the previous request to create a PDU session when another NW slice is selected in the PLMN selection procedure. Specifically, the seventh mode is a mode in which the UE continues the backoff timer received upon rejecting the request to create the first session PDU, in the case of selecting a PLMN while rejecting the request to create the first session PDU, and an NW slice, common for the NW slice specified in the request to create the first PDU session in the selected PLMN.

[00206] The eighth mode in the present embodiment is a mode in which the UE configures a network reported value or a value previously configured in the UE as the first timer value. Specifically, the eighth mode may be a mode in which the UE configures the backoff timer value received in the first session PDU creation request rejection notification as the first timer value, or may be a configuration mode of a value previously configured or stored in UE as the first timer value. In addition, the eighth mode, which is the configuration of a timer configured or stored in advance in the UE as the first timer value, can be limited when the UE is in the HPLMN or equivalent PLMN.

[00207] The ninth mode in the present embodiment is a mode in which the UE does not send a request to create a new PDU session until the terminal is powered on/off or the USIM (Universal Subscriber Identity Module) is inserted/removed, upon rejection request to create a PDU session. Specifically, in the ninth mode of operation, the UE does not transmit a request to create a new PDU session until the terminal is powered on/off or the USIM is inserted/removed in case the backoff timer received from the network is invalid, or in the case where the reason for rejecting the first session PDU is the difference in PDP types between the UE and the network. Alternatively, the ninth mode may be a mode in which a request to create a new PDU session is not transmitted until the terminal is powered on/off or the USIM is inserted/removed in the connected PLMN when the first PDU session is rejected due to lack of wireless support for the specified APN. /DNN from the connected PLMN side and no backoff timer information element received from the network, and no information about retries, or when PDU session reconnection to the equivalent PLMN is allowed. Alternatively, the ninth mode may be a mode in which a request to create a new PDU session is not transmitted until the terminal is powered on/off or the USIM is inserted/removed in the connected PLMN when the PDU session is rejected due to lack of wireless support for the specified APN/ DNN from the attached PLMN side, no backoff timer information element received from the network, and no retry information, or when PDU session reconnection to the equivalent PLMN is not allowed. Alternatively, the ninth mode may be a mode in which a request to create a new PDU session is not transmitted until the terminal is powered on/off or the USIM is inserted/removed when the first PDU session is rejected due to lack of wireless support from the specified APN/ DNN of the connected PLMN, and in case the backoff timer received from the network is neither zero nor invalid. Alternatively, the ninth mode may be a mode in which a request to create a new PDU session is not transmitted until the terminal is powered on/off or the USIM is inserted/removed when the first PDU session is rejected due to lack of wireless support from the connected PLMN of the specified APN/DNN, and in case the backoff timer received from the network is invalid.

[00208] The tenth mode in the present embodiment is a mode in which the UE sends a request to create a new session PDU when rejecting the request to create a session PDU. In particular, the tenth mode may be a mode in which the UE transmits a request to create a new PDU session in the case where the backoff timer received from the network is zero, or when the request to create the first PDU session is rejected for temporary reasons and in the absence of messages about the backoff timer IE itself from the network. Alternatively, the tenth mode may be a mode in which a request to create a new PDU session is transmitted when another PLMN is selected or another NW slice is selected, when the request to create the first PDU session is rejected for temporary reasons if the backoff timer is not activated for the target APN/ The DNN in the selected PLMN or the backoff timer received from the network is invalid. Alternatively, the tenth mode may be a mode in which a request to create a new PDU session is transmitted when the request to create the first PDU session is rejected due to a difference in PDP types of the UE and the network, and in the case that retry information is not received when another PLMN is selected. or when a different PLMN is selected that is not in the equivalent PLMN list, or when the PDP type is changed, or when the terminal is powered on/off, or when a USIM is inserted/removed. Alternatively, the tenth mode may be a mode in which a request to create a new PDU session is transmitted when the first PDU session is rejected due to lack of wireless support for the specified APN/DNN by the connected PLMN, and in case the backoff timer specified and received from the network is null.

[00209] The 11th mode in the present embodiment is a mode in which the UE ignores the first timer and retry information. In particular, the 11th mode may be a mode in which the UE ignores the first timer and retry information when denying a request to create the first session PDU because the destination PDN session context is not present in a non-3GPP handover. access, or when the creation of the first PDU session is rejected due to the creation of the maximum number of channels when connecting to the PDN.

[00210] The 12th mode in the present embodiment is a mode in which the UE determines information for identifying a plurality of associated NW slices based on information for identifying a single NW slice received in a rejection notification for a request to create a first session PDU, and is a mode in which the UE prohibits reconnection with a plurality of associated NW slices based on information for identifying one NW slice. Specifically, the 12th mode may be a mode in which the UE retrieves information for identifying another NW slice associated with information for identifying the NW slice reported along with rejecting the request to create the first session PDU based on the rule associated with network cut. It should be noted that the rule associated with the network slice may be pre-configured in the UE or may be signaled by the network in a session PDU request rejection notification.

[00211] The 13th mode in the present embodiment may be a mode in which the UE controls the timer based on the backoff timer priority control rule in the case where a plurality of different congestion controls are activated by the same UE to create one or more PDU sessions , and there are many timers in the network. For example, a request from the UE to create a first session PDU for the combination of DNN_1 and slice_1 is subject to congestion control based on both DNN and slice information, and the UE receives the first timer #1. In addition, for the combination of DNN_1 and slice_2, the UE issues a request to create a second PDU session that is subject to congestion control based only on the DNN and receives the first timer #2. backoff timer priority control. In particular, the timer value held by the UE may be overwritten by the timer value generated by prioritized congestion control.

[00212] The 14th mode in the present embodiment may be a timer control mode for each session control instance (per session PDU) in the case where a plurality of different congestion controls apply the same UE to create one or more PDU sessions , and when there are many timers in the network. For example, when the creation of the first PDU session performed by the UE for the combination of DNN #1 and slice #1 encounters congestion based on both the DNN and slice information, the UE manages the backoff timer target value as the first timer #1. Accordingly, when the UE attempts to further create a PDU session for the combination of DNN #1 and slice #2 as the second PDU session encountered congestion based on DNN only, the UE manages the backoff timer target value as the first timer #2. At this time, the UE controls multiple timers (in this case the first timer #1 and the first timer #2) at the same time. Specifically, the UE manages the timers based on the session control/session PDU instance. In addition, when the UE simultaneously receives a plurality of timers during a single session control procedure, the UE simultaneously manages the target backoff timer based on the congestion control unit identified by the UE.

[00213] The 15th mode in the present embodiment may be a mode in which the UE performs the first identification process to determine which type of congestion control to apply from the first congestion control to the fourth congestion control, and performs the second identification process to identification of the DNN and/or S-NSSAI associated with the applied congestion control. It should be noted that the first identification process can be performed based on at least one part of the identification information from the first identification information to the fourth identification information and/or at least one part of the identification information from the 11th identification information to the 18th identification information. Similarly, the second identification process may be performed based on at least one part of the identification information from the first identification information to the fourth identification information and/or at least one part of the identification information from the 11th identification information to the 18th identification information.

[00214] An example of the first identification process will be described below. In the first identification process, the type of congestion control applied may be determined as the first congestion control when one of two or more combinations of the following cases is performed.

・The case in which at least the 15th identification information is the value corresponding to the first overload control.

・The case in which at least the 16th identification information is the value corresponding to the first overload control.

・A case in which at least the 14th identification information includes first congestion control information.

・The case in which at least the 17th identity information includes only DNN and does not include S-NSSAI.

・The case in which the 16th identification information is information for identifying the identification information in any of the first overload control and the second overload control, and is information in which only the value corresponding to the second overload control can be configured for the 16th identification information , and a case in which at least the 16th identification information is not received.

・The case in which the 16th identification information is information for identifying the identification information in any of the first overload control and the fourth overload control, and is information in which only the value corresponding to the fourth overload control can be configured for the 16th identification information , and a case in which at least the 16th identification information is not received.

・The case in which the 16th identification information is information for identifying the identification information in any of the first overload control, the second overload control, and the fourth overload control, and is information in which only the value corresponding to the second overload control and the value corresponding to the fourth congestion control can be configured for the 16th identity information, and the case in which at least the 16th identity information is not received.

[00215] However, the present embodiment is not limited to the example described above, and UE_A10 may perform the identification process based on at least one part of the identification information from the first identification information to the fourth identification information, and/or based on at least one part of the identification information or combinations of two or more pieces of identification information from the 11th identification information to the 18th identification information.

[00216] In the first identification process, the type of congestion control applied can be identified as the second congestion control by performing one of two or more combinations of the following cases.

・A case in which at least the 15th identification information is a value corresponding to the second overload control.

・A case in which at least the 16th identification information is a value corresponding to the second overload control.

・A case in which at least the 14th identification information includes second congestion control information.

・The case in which at least the 17th identity information includes only S-NSSAI and does not include DNN.

・The case in which the 16th identification information is information for identifying the identification information in any of the first overload control and the second overload control, and is information in which only the value corresponding to the first overload control can be configured for the 16th identification information , and a case in which at least the 16th identification information is not received.

・The case in which the 16th identification information is information for identifying the identification information in any of the second overload control and the third overload control, and is information in which only the value corresponding to the third overload control can be configured for the 16th identification information, and a case in which at least the 16th identification information is not received.

・The case in which the 16th identification information is information for identifying identification information in any of the second overload control, third overload control, and fourth overload control, and is information in which only the value corresponding to the third overload control and the value corresponding to the fourth congestion control can be configured for the 16th identity information, and the case in which at least the 16th identity information is not received.

[00217] However, the present embodiment is not limited to the example described above, and UE_A10 may perform the identification process based on at least one part of the identification information from the first identification information to the fourth identification information, and/or based on at least one part of the identification information or combinations of two or more pieces of identification information from the 11th identification information to the 18th identification information.

[00218] In the first identification process, the type of congestion control applied can be identified as the third congestion control by performing one of two or more combinations of the following cases.

・A case in which at least the 15th identification information is a value corresponding to the third overload control.

・The case in which at least the 16th identification information is the value corresponding to the third overload control.

・A case in which at least the 14th identification information includes third congestion control information.

・A case in which at least the 15th identity is a value corresponding to a plurality of congestion controls including the third congestion control and not including the fourth congestion control, and in which the 17th identity includes S-NSSAI and DNN.

・The case in which the 16th identification information is information for identifying the identification information in any of the third overload control and the fourth overload control, and is information in which only the value corresponding to the fourth overload control can be configured for the 16th identification information , and a case in which at least the 16th identification information is not received.

・The case in which the 16th identification information is information for identifying the identification information in any of the second overload control and the third overload control, and is information in which only the value corresponding to the second overload control can be configured for the 16th identification information, and a case in which at least the 16th identification information is not received.

・The case in which the 16th identification information is information for identifying identification information in any of the second overload control, third overload control, and fourth overload control, and is information in which only the value corresponding to the second overload control and the value corresponding to the fourth congestion control can be configured for the 16th identity information, and the case in which at least the 16th identity information is not received.

[00219] However, the present embodiment is not limited to the example described above, and UE_A10 may perform the identification process based on at least one part of the identification information from the first identification information to the fourth identification information, and/or based on at least one part of the identification information or combinations of two or more pieces of identification information from the 11th identification information to the 18th identification information.

[00220] In the first identification process, the type of congestion control applied can be identified as the fourth congestion control by performing one of two or more combinations of the following cases.

・The case in which at least the 15th identification information is the value corresponding to the fourth overload control.

・A case in which at least the 16th identification information is a value corresponding to the fourth overload control.

・A case in which at least the 14th identification information includes fourth congestion control information.

・A case in which at least the 15th identity is a value corresponding to a plurality of congestion controls including the fourth congestion control and not including the third congestion control, and in which the 17th identity includes S-NSSAI and DNN.

・The case in which the 16th identification information is information for identifying the identification information in any of the third overload control and the fourth overload control, and is information in which only the value corresponding to the third overload control can be configured for the 16th identification information , and a case in which at least the 16th identification information is not received.

・The case in which the 16th identification information is information for identifying the identification information in any of the second overload control and the fourth overload control, and is information in which only the value corresponding to the second overload control can be configured for the 16th identification information , and a case in which at least the 16th identification information is not received.

・The case in which the 16th identification information is information for identifying the identification information in any of the first overload control and the fourth overload control, and is information in which only the value corresponding to the first overload control can be configured for the 16th identification information , and a case in which at least the 16th identification information is not received.

・The case in which the 16th identification information is information for identifying identification information in any of the second overload control, third overload control, and fourth overload control, and is information in which only the value corresponding to the second overload control and the value corresponding to the third congestion control can be configured for the 16th identity information, and the case in which at least the 16th identity information is not received.

・The case in which the 16th identification information is information for identifying the identification information in any of the first overload control, the second overload control, and the fourth overload control, and is information in which only the value corresponding to the first overload control and the value corresponding to the second congestion control can be configured for the 16th identity information, and the case in which at least the 16th identity information is not received.

[00221] However, the present embodiment is not limited to the example described above, and UE_A10 may perform the identification process based on at least one part of the identification information from the first identification information to the fourth identification information, and/or based on at least one part of the identification information or combinations of two or more pieces of identification information from the 11th identification information to the 18th identification information, or may perform the identification process using other means.

[00222] As described above, the type of congestion control can be identified through the first identification process.

[00223] Next, an example of the second identification process will be described. In addition, the second identification process may be a process of identifying the corresponding DNN and/or S-NSSAI for the type of congestion control identified by the first identification process.

[00224] In particular, the DNN corresponding to the first congestion control, the third congestion control, and the fourth congestion control can be determined based on the 12th identification information. Additionally/alternatively, the DNN corresponding to the first congestion control, the third congestion control, and the fourth congestion control may be determined based on the 17th identification information. Additionally/alternatively, the DNN corresponding to the first congestion control, the third congestion control, and the fourth congestion control may be determined based on the 2nd identification information.

[00225] Therefore, the DNN corresponding to the first congestion control, the third congestion control, and the fourth congestion control may be the DNN of the 12th identification information. Additionally/alternatively, the DNN corresponding to the first congestion control, the third congestion control, and the fourth congestion control may be a DNN included in the 17th identification information. Additionally/alternatively, the DNN corresponding to the first congestion control, the third congestion control, and the fourth congestion control may be the DNN of the 2nd identification information.

[00226] In addition, the S-NSSAI corresponding to the second congestion control, the third congestion control, and the fourth congestion control can be determined based on the 17th identification information. Additionally/alternatively, the DNN corresponding to the first congestion control, the third congestion control, and the fourth congestion control may be determined based on the 1st identification information.

[00227] Therefore, the DNN corresponding to the first congestion control, the third congestion control, and the fourth congestion control may be an S-NSSAI of the 17th identification information. Additionally/alternatively, the DNN corresponding to the first congestion control, the third congestion control, and the fourth congestion control may be an S-NSSAI included in the 1st identification information.

[00228] However, the present embodiment is not limited to the example described above, and UE_A10 may also perform the identification process based on at least one part of the identification information from the first identification information to the fourth identification information, and/or based on at least one part of the identification information or a combination of two or more pieces of identification information from the 11th identification information to the 18th identification information, or may perform the identification process using other means.

[00229] Based on the above 15th mode of operation, UE_A10 can identify the congestion control that the core network_B190 applies to UE_A10. In other words, UE_A10 may identify the corresponding type of congestion control and the corresponding S-NSSAI and/or DNN as the applicable congestion control based on the 15th operating mode. In addition, UE_A10 may store and manage one or more pieces of identity from the first identity to the fourth identity and from the 11th identity to the 18th identity in connection with the applied congestion control. In this case, the 3rd identification information, the 4th identification information, and/or the 13th identification information may be stored and managed as information for identifying the applied congestion control.

[00230] The 16th mode in the present embodiment is a mode in which the UE stops the first timer when executing the NW-initiated session control procedure with the first timer activated.

[00231] In this case, for example, the 16th mode may be a mode of determining the first timer to be stopped among the plurality of first timers activated based on the 21st identification information, and then stopping the determined timer when the plurality of first timers are activated. . Additionally/alternatively, the 16th mode may be a stop mode of the first timer associated with the overload control identified by the 17th mode of operation. It should be noted that when there are a plurality of overload controls identified by the 17th operating mode, it is possible to stop the timer associated with each overload control.

[00232] The 17th mode in the present embodiment is a mode in which the UE identifies the congestion control whose application is to be stopped among one or more congestion controls applied by the UE based on the receipt of a control message transmitted by the core network. For example, the UE may determine the congestion control whose application should be stopped or changed based on the 21st identification information.

[00233] Specifically, as described above, the UE may store the third identification information, the fourth identification information, and/or the 13th identification information as information for identifying the congestion control in the fourth process, and may identify the congestion control in which the information for identifying this the congestion control matches the 13th identification information included in the 21st identification information as the congestion control whose application is to be stopped.

[00234] Additionally/alternatively, the UE may identify the congestion control whose application is to be stopped based on one part or combination of a plurality of parts of the 11th identity to the 18th identity included in the 21st identity. Here, the details of the identification method may be the same as the identification process in the 15th operation mode described in the fourth process in the example PDU session creation procedure described below. In other words, the UE may identify the congestion control to be stopped in a manner that is the same as the method for identifying the applied congestion control.

[00235] It should be noted that the UE may identify a set of congestion controls whose application should be stopped. Hereinafter, the overload control identified by the above method is considered the first overload control, and a method for identifying the second overload control different from the first overload control will be described.

[00236] For example, the UE may identify the congestion control associated with the DNN matching the DNN associated with the first congestion control as the second congestion control. Additionally/alternatively, the UE may identify the congestion control associated with the S-NSSAI matching the S-NSSAI associated with the first congestion control as the second congestion control. It should be noted that the identification of a plurality of congestion controls whose application is to be stopped can only be configured to be performed when the first congestion control and/or the second congestion control is a particular type of congestion control.

[00237] Specifically, the UE may identify the second congestion control when the first congestion control is any of the first to fourth congestion control. Additionally/alternatively, when indicating the second congestion control, the UE may identify the second congestion control when the congestion control to be searched is any of the first to fourth congestion control. It should be noted that the core network and/or the UE may be pre-configured in a type in which the first congestion control and/or the second identification information may identify a plurality of congestion controls. In addition, the number of specific types of congestion control allowed for identification is not necessarily configured to be one, but may be configured as a plurality.

[00238] The first identification information in the present embodiment is information for identifying whether a session belongs to the first NW slice. In other words, the first identification information may be information that the UE is waiting to create a PDU session belonging to the first NW slice. Specifically, for example, the first identification information may be information for identifying the first NW slice. It should be noted that the slice information may be identification information about a particular S-NSSAI. It should be noted that the first identification information may be information for identifying a specific NW slice in Operator A's network, or may be information for generic identification of the same NW slice at Operator B (other than Operator A). The first identification information may further be information for identifying the first NW slice configured based on the HPLMN, may be information for identifying the first NW slice received from the AMF during the registration procedure, or may be information for identifying the first NW slice provided by the network. In addition, the first identification information may be information for identifying the first NW slice stored for each PLMN.

[00239] The second identification information in the present embodiment may be a DNN (Data Network Name) and information used to identify a DN (Data Network).

[00240] The third identification information in the present embodiment may be a PDU session ID and information used to identify the PDU session.

[00241] The fourth identification information in the present embodiment may be a PTI (procedure transaction identifier), which is information for identifying the transmission and/or reception of a series of messages of a specific session management procedure as one group, and may also be information used to identify and/or distinguish between the transmission and/or reception of another series of messages related to session management.

[00242] The 11th identification information in the present embodiment may be information about rejecting a request to create a session PDU or a request to change a session PDU. It should be noted that a PDU session creation request or a PDU session change request is a request made by the UE and may include a DNN and/or S-NSSAI. In other words, the 11th identification information may be information that the NW rejects a request to create or a request to change a session PDU corresponding to the DNN and/or S-NSSA.

[00243] In addition, the 11th identification information may be information containing information about retries.

[00244] Further, the NW may transmit at least one of the 12th to 18th identities along with the 11th identities to the UE to inform the UE of congestion control. In other words, the NW may notify the UE of the congestion control corresponding to one fragment or combination of the plurality of identification information fragments 12 to 18. On the other hand, the UE may identify the congestion control corresponding to one piece or combination of the plurality of 12th to 18th identification information pieces, and perform processing based on the identified congestion control. In particular, the UE may start timing the first timer associated with the identified congestion control. The value of the first timer may be further determined using the 14th identification information, the value of the timer may be configured in another way, such as using a value previously stored by the UE, or a random value may be configured.

[00245] The 12th identity information in the present embodiment may be a DNN, which may be a DNN not allowed by the network, or may be unallowed information for the DNN identified by the second identity information. The 12th identity may further be the same DNN as the second identity.

[00246] The 13th identification information in the present embodiment may be the session ID of the PDU and/or PTI not allowed by the network, or may be information that the session ID of the PDU and/or PTI identified by the third identification information is not allowed. In addition, the session ID of the PDU of the 13th identification information may be the same as the session ID of the PDU for the third identification information. In addition, the PTI of the 13th identity information may be the same as the PTI of the fourth identity information.

[00247] In this case, the 13th identification information can be used as information for identifying the congestion control reported by the NW to the UE based on the PDU session creation rejection. In other words, the UE may store and manage the 13th identity information in connection with the congestion control performed based on the 15th operation mode, and use the 13th identity information as information for identifying the congestion control being performed. In addition, the information for identification of the congestion control may be composed of a combination of one or more parts of the identification information from the 14th to the 18th identification information in addition to the 13th identification information.

[00248] The 14th identification information in the present embodiment may be backoff timer value information. In other words, the backoff timer may be a value indicating a valid congestion control period that the NW notifies the UE based on the PDU session creation rejection. In other words, the UE may use the 14th identity information as a timer value in the 15th mode of operation executed in response to receiving the 14th identity information. In addition to the timer value, the 14th identification information may further include information for identifying the type of congestion control. In particular, the 14th identification information may include information for determining which of the first to fourth overload controls is applied. For example, the information for identifying the type of congestion control may be a timer name identifying each congestion control, or may be a flag identifying each congestion control. However, the present embodiment is not limited to the example described above, and congestion control may be identified using other means, such as using a location stored in a control message, and the like.

[00249] The 15th identification information in the present embodiment is information about one or more reason values that determine the reason for rejecting the procedure. In other words, the cause value may be information about the congestion control applied by the NW to the given procedure, or may be information with a reason value for rejecting the given procedure applied by the NW other than the congestion control.

[00250] It should be noted that the cause value may be information for identifying, based on the PDU session creation rejection, which of the congestion controls among the first to fourth congestion controls matches the congestion control that the NW notifies the UE. In this case, the NW may transmit a different value to the UE as a cause value according to each first to fourth congestion control. The UE may interpret each value transmitted as a cause value in advance, and identify, in the 15th operating mode, based on at least the 15th identification information, the congestion control among the first to fourth congestion controls.

[00251] Alternatively, the cause value may be information for identifying, based on the PDU session creation rejection, whether the congestion control that the NW notifies the UE is the first congestion control or any congestion control from the second, third, and fourth congestion controls. In this case, the NW may send a different value to the UE as the cause value depending on whether the congestion control is the first congestion control or any congestion control from the second, third, and fourth congestion controls. The UE may interpret each value transmitted as a cause value in advance and identify, in the 15th mode of operation, based on at least the 15th identification information, whether the congestion control is the first congestion control or any of the second, third, and fourth congestion controls.

[00252] Alternatively, the cause value may be information for identifying, based on the PDU session creation rejection, whether the congestion control that the NW notifies the UE is the first congestion control, the second congestion control, or any congestion control of the third and fourth congestion controls. In this case, the NW may send a different value to the UE as the cause value depending on whether the congestion control is the first congestion control, the second congestion control, or any of the third and fourth congestion controls. The UE may interpret each value transmitted as a cause value in advance and identify in the 15th operating mode based on at least the 15th identification information whether the congestion control is the first congestion control, the second congestion control, or any of the third and fourth congestion control. overload control.

[00253] Alternatively, the cause value may be information for identifying, based on PDU session creation rejection, whether the congestion control that the NW notifies the UE is the first congestion control or the second congestion control, or the third congestion control or the fourth congestion control. In this case, the NW may send a different value to the UE as the cause value depending on whether the congestion control is the first congestion control or the second congestion control or the third congestion control or the fourth congestion control. The UE further interprets each value transmitted as a cause value in advance, and identifies, in the 15th operation mode, based on at least the 15th identification information, whether the congestion control is the first congestion control or the second congestion control, or the third congestion control or the fourth congestion control. .

[00254] Alternatively, the cause value may be information for identifying, based on the PDU session creation rejection, whether the congestion control that the NW notifies the UE is the second congestion control or the third congestion control, or the first congestion control or the fourth congestion control. In this case, the NW may send a different value to the UE as the cause value depending on whether the congestion control is the second congestion control or the third congestion control or the first congestion control or the fourth congestion control. The UE further interprets each value transmitted as a cause value in advance, and identifies, in the 15th operating mode, based on at least the 15th identification information, whether the congestion control is the second congestion control or the third congestion control, or the first congestion control or the fourth congestion control. .

[00255] Alternatively, the cause value may be information for identifying, based on the PDU session creation rejection, whether the congestion control that the NW notifies the UE is the second congestion control or the fourth congestion control, or the first congestion control or the third congestion control. In this case, the NW may send a different value to the UE as the cause value depending on whether the congestion control is the second congestion control or the fourth congestion control, or the first congestion control or the third congestion control. The UE further interprets each value transmitted as a cause value in advance, and identifies in the 15th operation mode, based on at least the 15th identification information, whether the congestion control is the second congestion control or the fourth congestion control, or the first congestion control or the third congestion control. .

[00256] Alternatively, the cause value may be information that the NW performs congestion control for the UE based on the PDU session creation rejection. In other words, the cause value may be information by which the UE starts to perform any congestion control of the first to fourth congestion controls. In this case, the cause value need not be information that can identify a particular congestion control.

[00257] A more detailed example of a reason value for rejecting a given procedure applied by the NW, other than the congestion control described above, may further be a cause value (missing or unknown DNN) transmitted by the UE from the NW indicating that the external DN is rejecting the given procedure. because the procedure is missing DNN information or includes an unknown DNN. In addition, a more detailed example of a cause value could be a cause value (unknown PDU session type) sent by the UE from the NW indicating that the external DN rejects the procedure because the procedure cannot recognize or does not allow the session PDU type of the procedure. In addition, a more detailed example of a cause value can be a cause value (user authentication or authorization error) which the NW reports to the UE, and which indicates that the external DN rejects the given procedure due to failed authentication and authorization of the user in this procedure, deauthentication and authorization based on the external DN or deauthentication and authorization based on the NW. In addition, a more detailed example of the reason value may be a cause value (request denied, not specified) for the NW to notify the UE to reject the requested service, operation, or resource reservation request based on an unspecified reason. In addition, a more detailed example of the cause value may be a cause value (service option temporarily out of order) for the NW to notify the UE that the NW is temporarily unable to receive a service request from the UE. In addition, a more detailed example of the cause value may be the reason value (PTI already in use) for NW to notify the UE that the PTI inserted by the UE is already in use. In addition, a more detailed example of the cause value may be a cause value (out of LADN service area) for the NW to notify the UE that the UE is outside the LADN service area. In addition, a more detailed example of the cause value may be a reason value (IPv4 session PDU type allowed) for the NW to notify the UE that only the IPv4 session PDU type is allowed. In addition, a more detailed example of the cause value may be a cause value (only IPv6 session PDU type allowed) for the NW to notify the UE that only IPv6 session PDU type is allowed. In addition, a more detailed example of a cause value could be a cause value (session PDU does not exist) for the NW to notify the UE that the NW does not support the target session PDU when the session PDU is transitioned from non-3GPP access to 3GPP access or the session PDU is transferred from EPS to 5GS by UE. In addition, a more detailed example of the cause value may be a cause value (unsupported SSC mode) for the NW to notify the UE that the NW does not support the SSC mode requested by the UE. In addition, a more detailed example of a cause value could be a cause value (missing or unknown DNN in slice) sent by the UE from the NW indicating that the outer DN rejects the procedure because DNN information is missing or included in the procedure through a particular slice. unknown DNN. In addition, a more detailed example of a cause value can be a cause value (the maximum data rate per UE for user plane integrity protection is too low) transmitted by the UE from the NW, indicating that the UE does not meet the requirements for the maximum data rate for protecting user plane integrity, pushed for the service requested by the UE from the NW.

[00258] Note that, in the present embodiment, when the third congestion control is not performed, the implication corresponding to the third congestion control is not required in the cause value in the 15th identification information described above, and the cause value in the 15th identification information may be a value that may omit the processing, description, and implication associated with the third overload control as described above. In addition, in the present embodiment, when the fourth congestion control is not performed, the implication corresponding to the fourth congestion control is not required in the cause value in the 15th identification information described above, and the cause value in the 15th identification information may be a value that may omit the processing, description, and implication associated with the fourth overload control as described above.

[00259] As a more detailed example, the 15th identification information for identifying the first congestion control may be a cause value indicating insufficient resources. In addition, the 15th identification information identifying the second congestion control may be a cause value indicating insufficient resources for a certain slice. The 15th identification information identifying the third congestion control may further be a cause value indicating insufficient resources for a certain slice and DNN.

[00260] Thus, the 15th identification information may also be information by which the type of congestion control can be identified, and may be information on the type of congestion control corresponding to the backoff timer and/or the backoff timer value in 14- and identification information.

[00261] Therefore, UE_A10 can also identify the type of congestion control based on the 15th identification information. Based on the 15th identification information, it can be further determined which type of congestion control corresponds to the backoff timer and/or the backoff timer value in the 14th identification information.

[00262] The 16th identification information in the present embodiment is one or more pieces of information about the indication with information about the rejection of this procedure. In other words, the indication information may be congestion control information applied by the NW to the procedure. The NW may provide for congestion control applied by the NW based on the 16th identification information.

[00263] For example, the indication information may be information about the type of congestion control determined by the NW for the UE as two or more congestion controls from the first to fourth congestion controls. Therefore, the NW may transmit a value associated with the determined control applied to the UE as indication information. The UE may further interpret each transmitted value as indication information in advance and identify, in the 15th operation mode, based on at least the 16th identification information, the congestion control among the first to fourth congestion controls. In this case, two or more overload controls of the first to fourth overload controls are overload controls, which can be identified using indication information, and the identified overload controls can be all four overload controls, can be the first overload control and the second overload control. , may be the third overload control and the fourth overload control, may be the second to fourth overload controls, or may be any other combination thereof.

[00264] It should be noted that the indication information does not necessarily require that values corresponding to all overload controls be identified. For example, if indication information values are respectively associated with congestion controls and allocated to congestion controls except for congestion control A, the indication information value need not be configured for congestion control A. In this case, the NW and UE may identify congestion control as the first congestion control while not transmitting and/or receiving indication information. It should be noted that the overload control A may be any of the first to fourth overload control.

[00265] In addition, when notifying the UE of congestion control based on the transmission of the PDU session creation rejection message, there may or may not be cases where identification may or may not be included, depending on the first to fourth congestion control type. In other words, the NW may use the identification information as congestion control information, depending on the type of congestion control, or may use other identification information as the overload control information, depending on the type of congestion control, without using the identification information.

[00266] Note that, in the present embodiment, when the third congestion control is not performed, the implication corresponding to the third congestion control is not required in the 16th identification information indication information described above and the 16th identification information indication information may be information that may lack processing, description, and implication associated with the third congestion control as described above. Further, in the present embodiment, when the fourth overload control is not performed, the implication corresponding to the fourth overload control is not required in the 16th identification information designation information described above, and the 16th identification information designation information may be information , which may omit the processing, description, and implication associated with the fourth overload control as described above.

[00267] The 17th identification information in the present embodiment is one or more value fragments of the procedure rejection information. In other words, the value of the information may also be information about the congestion control applied by the NW to the procedure. It should be noted that the 17th identification information may be information including at least one piece of identification information for identifying one or more NW slices included in the 18th identification information and/or the 12th identification information.

[00268] The NW may provide for congestion control applied by the NW based on the 17th identification information. In other words, the NW may report which congestion control among the first to fourth congestion controls is applied based on the 17th identification information. The NW may further determine the DNN and/or S-NSSAI that is the subject of the congestion control applied to the UE based on the transmission of the PDU session reject message based on the 17th identity information. For example, when the 17th identity is simply DNN #1, then the first congestion control related to DNN #1 is applied. When the 17th identity is simply S-NSSAI #1, the second congestion control related to S- is applied. NSSAI No. 1. When the 17th information is configured with DNN No. 1 and S-NSSAI No. 1, then a third congestion control or a fourth congestion control related to at least one of DNN No. 1 and/or S-NSSAI may be applied. No. 1.

[00269] It should be noted that the 17th identification information need not be information that can identify which congestion control of the first to fourth congestion controls apply, and the 17th identification information may be information about the DNN and/or S-NSSAI that are subject to congestion control identified by other means, eg based on other identification information.

[00270] The 18th identification information in the present embodiment may be information about denying a request to create a session of a PDU belonging to the first NW slice, or may be information about not allowing a request to create a session of a PDU belonging to the first NW slice. , or a request to change the PDU session (Change Session PDU). In this case, the first NW slice may be the NW slice defined by the first identification information, or may be another NW slice. In addition, the 18th identification information may be information about the lack of permission to create a session of the PDU belonging to the first NW slice identified by the 12th identification information, or may be information about the lack of permission to create a session of the PDU belonging to the first NW-slice. slice, in the PDU session identified by the 13th identification information. In addition, the 11th identification information may be information about the lack of permission to create a PDU session belonging to the first slice in the registration area and/or tracking area to which UE_A10 currently belongs, or may be information about creating a PDU session. belonging to the first NW slice in the access network to which UE_A10 is connected. The 11th identification information may further be identification information for determining the NW slice to which the rejected session request PDU belongs, or for identifying one or more NW slices. Moreover, the 18th identity may be an identity containing assistance information for the radio access system to select an appropriate MME when the connection destination UE switches to EPS. It should be noted that the side information may be DCN ID information. The 18th identification information may further be a network slice association rule, which is a rule for linking a plurality of slice information pieces.

[00271] The 21st identification information in the present embodiment may be information for stopping one or more first timers activated by the UE, or may be information about the first timer to be stopped of the first timers activated by the UE. In particular, the 21st identification information may be information containing the 13th identification information stored in the UE in connection with the first timer. Moreover, the 21st identification information may be information about at least one piece of identification information from the 12th to 18th identification information stored (stored) in the UE in connection with the first timer.

[00272] In addition, the 21st identification information may be information changing the association of the first timer stored in the UE using information about at least one piece of identification information from the 13th to 17th identification information. For example, when the first timer is activated to suppress the UE-initiated session control of the combination of DNN #A and S-NSSAI #A, the UE may change the association target of the activated timer to S-NSSAI #A only and recognize that the UE-initiated session control request addressed to the DNN No. A is allowed upon receipt of an NW-initiated session control request including the 21st identification information allowing connection to DNN No. A. In other words, the 21st identification information may be information about changing the congestion control applied during receiving the 21st identification information, to another congestion control of the first to fourth congestion controls.

[00273] Next, the initial procedure according to the present embodiment will be described with reference to FIG. 9. Hereinafter, the initial procedure is also referred to as this procedure, and this procedure includes a registration procedure, a UE-initiated PDU session creation procedure, and a network-initiated session management procedure. Details of the registration procedure, the UE-initiated PDU session establishment procedure, and the network-initiated session management procedure will be described below.

[00274] Specifically, each device performs the registration procedure (S900), and the UE_A10 enters the network registration state (RM-REGISTERED state). Then, each device performs a PDU session creation procedure (S902), and the UE_A10 creates a PDU session with DN_A5 that provides a PDU connection service via the core network_B190, and each device enters the first state (S904). It should be noted that although the session PDU is considered to be created by the access network and UPF_A235, the procedure is not limited to this. That is, a UPF (UPF_C239) other than UPF_A235 may be present between UPF_A235 and the access network. At this time, a PDU session is created by the access network, UPF_C239 and UPF_A235. Then, each device in the first state can perform the network-initiated session management procedure at any time (S906).

[00275] It should be noted that each device may exchange different capability information and/or different request information from each of the devices in a registration procedure, a PDU session creation procedure, and/or a network-initiated session control procedure. In addition, when each device exchanges various types of information and/or negotiates various requests in the registration procedure, each device may or may not exchange various types of information and/or negotiate various requests within the PDU session creation procedure and/or network initiated session management procedures. In addition, when each device does not exchange different kinds of information and/or negotiate different requests in the registration procedure, each device can exchange different kinds of information and/or negotiate different requests within the PDU session creation procedure and/or the network-initiated session control procedure. . In addition, even when each device exchanges different kinds of information and/or negotiates different requests in the registration procedure, each device can exchange different kinds of information and/or negotiate different requests within the PDU session creation procedure and/or the network-initiated session control procedure. .

[00276] In addition, each device may perform the PDU session creation procedure as part of the registration procedure or after the registration procedure is completed. In addition, when performing the PDU session creation procedure within the registration procedure, a PDU session creation request message may be included in the registration request message and transmitted and/or received, and a PDU session creation approval message may be included in the registration approval message. and transmitted and/or received, a PDU Session Creation Complete message may be included in the Registration Completion message and transmitted and/or received, and a PDU Session Creation Reject message may be included in the Registration Reject message and transmitted and/or received. Further, when executing the PDU session creation procedure within the registration procedure, each device may create a PDU session based on the completion of the registration procedure, or may enter a state in which a PDU session is created between devices.

[00277] In addition, each device involved in this procedure may transmit and/or receive each control message described in this procedure, to transmit and/or receive one or more pieces of identification information included in each control message, and store each piece of identification information transmitted and/or received as a context.

[00278] [1.3.1. Overview of registration procedure]

[00279] First, an overview of the registration procedure will be given. The registration procedure is a procedure initiated by the UE_A10 to perform registration with the network (access network and/or core network_B190 and/or DN_A5). In the state in which the UE_A10 is not registered with the network, the UE_A10 can perform this procedure at any time, such as when the power is turned on. In other words, if the UE_A10 is in the de-registration state (RM-DEREGISTERED state), the UE may initiate this procedure at any time. In addition, each device may enter a registered state (RM-REGISTERED state) based on the completion of the registration procedure.

[00280] Moreover, this procedure may be a procedure for updating the UE_A10 network location registration information and/or periodically notifying the network of the UE_A10 state by the UE_A10 equipment and/or updating a certain parameter related to the UE_A10 in the network.

[00281] UE_A10 may initiate this procedure at a time when UE_A10 is performing mobility in a TA. In other words, UE_A10 may initiate this procedure at a time when UE_A10 transitions to a TA other than the TA specified in the TA list stored in UE_A10. UE_A10 may optionally initiate this procedure at the time the timer expires. In addition, UE_A10 may initiate this procedure when it is necessary to update the context of each device due to a disconnection or revocation of validation (also referred to as deactivation) of the session PDU. In addition, the UE_A10 may initiate this procedure at the time when there is a change in the capability and/or preference information related to creating a PDU session for the UE_A10. In addition, UE_A10 may regularly initiate this procedure. It should be noted that UE_A10 is not limited to the above and may perform this procedure at any point in time, provided that a session PDU is created.

[00282] [1.3.1.1. Registration Procedure Example]

[00283] An example of the method for performing the registration procedure will be described with reference to FIG. 10. In this section, "this procedure" means the registration procedure. Each step of this procedure will be described below.

[00284] First, UE_A10 sends a registration request message to AMF_A240 via NR-node_A122 (also referred to as gNB) and/or ng-eNB (S1000) (S1002) (S1004) to initiate the registration procedure. In addition, during the registration procedure, the UE_A10 may transmit a session management (SM) message (eg, create session PDU request message) included in the registration request message, or transmit an SM message (eg, create session PDU request message) along with a registration request message to initiate a session management (SM) procedure, such as a PDU session creation procedure.

[00285] Specifically, UE_A10 transmits an RRC (Radio Resource Control) message including a registration request message to NR-node_A122 and/or ng-eNB (S1000). In case of receiving an RRC message including a registration request message, NR-node_A122 and/or ng-eNB extracts the registration request message from the RRC message and selects AMF_A240 as the NF or common CP to which the registration request message is directed ( S1002). In this case, NR-node_A122 and/or ng-eNB selects AMF_A240 based on the information included in the RRC message. NR-node_A122 and/or ng-eNB transmits or forwards a registration request message to the selected AMF_A240 (S1004).

[00286] It should be noted that the registration request message is a NAS (Non-Access Layer) message transmitted and/or received on the N1 interface. In addition, the RRC message is a control message sent and/or received between UE_A10 and NR-node_A122 and/or ng-eNB. The NAS message is further processed at the NAS layer, the RRC message is processed at the RRC layer, and the NAS layer is a higher layer than the RRC layer.

[00287] In addition, when a plurality of NSIs request registration, the UE_A10 may transmit a registration request message for each NSI, or may transmit a plurality of registration request messages included in one or more RRC messages. In addition, the plurality of Registration Request messages described above may be included in one or more RRC messages and transmitted as a single Registration Request message.

[00288] In case of receiving a registration request message and/or a control message other than the registration request message, AMF_A240 performs the determination of the first condition. The determination of the first condition is used to determine whether the AMF_A240 receives a request from the UE_A10. When determining the first condition, AMF_A240 determines whether the definition of the first condition is true or false. AMF_A240 initiates procedure (A) in this procedure when the definition of the first condition is true (i.e., the network receives the UE_A10 request), and initiates procedure (B) in this procedure when the definition of the first condition is false (i.e., the network does not accept equipment request UE_A10).

[00289] Next, the steps will be described in the case where the determination of the first condition is true, that is, each step of the procedure (A) within this procedure will be described. AMF_A240 executes the determination of the fourth condition and initiates procedure (A) within this procedure. The determination of the fourth condition is to determine whether the AMF_A240 is transmitting and/or receiving an SM message to/from the SMF_A230. In other words, determining the fourth condition may include determining whether the AMF_A240 performs a PDU session creation procedure within the procedure. When the fourth condition definition is true (i.e., AMF_A240 transmits and/or receives an SM message to and/or from SMF_A230), AMF_A240 selects SMF_A230 and sends an SM message to and/or receives from the selected SMF_A230, and when the fourth condition definition is false ( i.e., AMF_A240 does not transmit an SM message to and/or receive from SMF_A230), AMF_A240 skips the process (S1006). It should be noted that when the AMF_A240 receives the SM message about the deviation from the SMF_A230, the AMF_A240 may stop the procedure (A) in this procedure and initiate the procedure (B) in this procedure.

[00290] Moreover, AMF_A240 transmits a registration approval message to UE_A10 by NR node_A122 based on receiving a registration request message from UE_A10 and/or completing transmission and/or reception of an SM message to and/or from SMF_A230 (S1008). For example, when the determination of the fourth condition is true, AMF_A240 may transmit a registration approval message based on receiving a registration request message from UE_A10. In addition, if the fourth condition is false, AMF_A240 may transmit a registration approval message based on completion of transmission and/or reception of an SM message to and/or from SMF_A230. In this case, the registration approval message may be transmitted as a response message to the registration request message. In addition, the registration approval message is a NAS message transmitted and/or received on the N1 interface, and for example, AMF_A240 may send it as an N2 interface control message to NR-node_A122, and NR-node_A122 receiving the message may include the message in RRC message and send it to UE_A10.

[00291] When the determination of the fourth condition is true, the AMF_A240 may further include an SM message (e.g., PDU session creation approval message) in the registration approval message, and transmit a registration approval message or send an SM message (e.g., PDU session creation approval message) along with a registration approval message. In addition, this transmission method can be performed when the registration request message includes an SM message (eg, PDU session request messages) and when the fourth condition is true. In addition, the transmission method can be performed by including an SM message (eg, a create PDU session request message) in a registration request message and the fourth condition is true. AMF_A240 may report approval of the procedure to the SM by performing such a transmission method.

[00292] UE_A10 receives a registration approval message via NR node_A122 (S1008). UE_A10 receives the registration approval message and recognizes the contents of various types of identification information included in the registration approval message.

[00293] Then, UE_A10 sends a registration complete message to AMF_A240 based on the received registration approval message (S1010). It should be noted that when the UE_A10 receives an SM message such as a PDU session creation approval message, the UE_A10 may send an SM message such as a PDU session creation complete message included in the registration complete message, or may include an SM message in it for the message about the completion of the procedure for SM. In this case, the registration completion message may be transmitted as a response message to the registration approval message. In addition, the registration complete message is a NAS message transmitted and/or received on the N1 interface, and for example, UE_A10 may include it in the RRC message and transmit it to NR-node_A122 and NR-node_A122, which receives the message, may send message AMF_A240 as a control message to interface N2.

[00294] AMF_A240 receives a registration complete message (S1010). In addition, each device completes procedure (A) within the present procedure based on the transmission and/or reception of a registration approval message and/or a registration completion message.

[00295] Next, the steps will be described in the case of a false determination of the first condition, i.e., each step of the procedure (B) within this procedure will be described. AMF_A240 sends a registration rejection message to UE_A10 via NR node_A122 (S1012) to initiate procedure (B) within this procedure. In this case, the registration rejection message may be transmitted as a response message to the registration request message. In addition, the registration rejection message is a NAS message transmitted and/or received on the N1 interface, and for example, AMF_A240 may send it as an N2 interface control message to NR-node_A122, and NR-node_A122 receiving the message may include the message in RRC message and send it to UE_A10. The registration rejection message transmitted by AMF_A240 is not further limited to this as long as it is a message rejecting the request of the UE_A10.

[00296] It should be noted that the procedure (B) of this procedure can sometimes be initiated when the procedure (A) of the procedure is terminated. When the determination of the fourth condition is true in procedure (A), the AMF_A240 may include an SM rejection message, such as a PDU session creation rejection message or the like, in the registration rejection message, and transmit the SM message, or report the procedure rejection to the SM by including rejection SM messages. In this case, UE_A10 may further receive a rejection message SM, such as a PDU session creation rejection message, or may recognize a procedure rejection for the SM.

[00297] In addition, UE_A10 may receive a registration rejection message or may not receive a registration approval message to recognize UE_A10's request rejection. Each device completes procedure (B) within the present procedure based on the transmission and/or reception of a registration rejection message.

[00298] Each device completes the present procedure (registration procedure) based on the completion of procedure (A) or (B) within the present procedure. It should be noted that each device may transition to a state in which UE_A10 is registered with the network (RM_REGISTERED state) based on completion of procedure (A) within this procedure, or may maintain a state in which UE_A10 is not registered with the network (RM_DEREGISTERED state), based on the completion of the procedure (B) within the framework of this procedure. In addition, the transition of each device to each state may be performed based on the present registration procedure, or may be performed based on the creation of a PDU session.

[00299] Each device may, based on the completion of this procedure, further perform processing based on the identification information transmitted and/or received in this procedure.

[00300] Further, determination of the first condition may be made based on the identification information and/or subscriber information and/or operator policy included in the registration request message. For example, the definition of the first condition may be true when the UE_A10 request is allowed by the network. In addition, the determination of the first condition may be false when the UE_A10 request is not allowed by the network. In addition, the determination of the first condition may be true when the network in which UE_A10 is registered and/or the device in the network supports the function requested by UE_A10 and may be false when the network and/or device does not support the function. The first condition definition may further be true when it is determined that the network is congested and may be false when it is determined that the network is not congested. It should be noted that the conditions for determining whether the determination of the first condition is true or false may not be limited to the conditions described above.

[00301] In addition, the determination of the fourth condition may also be performed based on whether the AMF_A240 receives the SM message, and may be performed based on whether the SM message is included in the registration request message. For example, the determination of the fourth condition may be true when the AMF_A240 receives the SM and/or the SM message is included in the registration request message, and may be false when the AMF_A240 does not receive the SM and/or the SM message is not included in the registration request message. It should be noted that the conditions for determining whether the determination of the fourth condition is true or false may not be limited to the conditions described above.

[00302] [1.3.2. Overview of PDU Session Creation Procedure]

[00303] Next, an overview of the PDU session creation procedure performed to create a PDU session with DN_A5 will be given. Hereinafter, the procedure for creating a PDU session is also referred to as this procedure. This procedure is the procedure for creating a PDU session for each device. It should be noted that each device can perform this procedure in a state in which the registration procedure is completed, or during the execution of the registration procedure. In addition, each device may initiate the present procedure in the registered state, or may initiate the present procedure at any time after the registration procedure. In addition, each device may create a PDU session based on completion of the PDU session creation procedure. Each device may further perform this procedure multiple times to create multiple PDU sessions.

[00304] [1.3.2.1. Example PDU Session Creation Procedure]

[00305] An example of a procedure for performing a PDU session creation procedure will be described with reference to FIG. 11. Each step of this procedure will be described below. First, UE_A10 transmits a PDU session creation request message to the core network_B via access network_B (S1100), and initiates a PDU session creation procedure.

[00306] Specifically, UE_A10 transmits a PDU session creation request message to AMF_A240 in core network_B190 via NR node_A122 using N1 interface (S1100). AMF_A receives a PDU session creation request message and performs a third condition determination. The determination of the third condition is used to determine whether AMF_A approves the request of UE_A10. When determining the third condition, AMF_A determines whether the definition of the fifth condition is true or false. When the determination of the third condition is true, the reference network_B initiates process No. 1 in the reference network (S1101), and when the determination of the third condition is false, the reference network_B initiates procedure (B) within this procedure. It should be noted that the steps to be performed in the case where the determination of the third condition is false will be described below. In this case, process #1 in the core network may be the SMF selection performed by the AMF_A in the core network_B190 and/or the transmission and/or reception of a PDU session request message between AMF_A and SMF_A.

[00307] Reference network_B190 initiates process #1 in the reference network. During process #1 in the core network, AMF_A240 may select SMF_A230 as NF as the routing destination of the create session PDU request message, and may transmit or carry the create session PDU request message to the selected SMF_A230 using the N11 interface. In this case, AMF_A240 may select SMF_A230 as the routing destination based on information included in the Create Session PDU Request message. More specifically, AMF_A240 may select SMF_A230 as the routing destination based on each piece of identification information retrieved upon receipt of the PDU session request message and/or subscriber information and/or network capability information and/or based on operator policy, and/or network state, and/or context, which is already contained in AMF_A240.

[00308] It should be noted that the PDU session request message may be a NAS message. In addition, it is possible that the PDU session creation request message can only be a PDU session request message, and is not limited thereto.

[00309] In this case, UE_A10 may include one or more first to fourth identity information fragments in a session creation request PDU message, or may report a device request to UE_A10 by including these identification information fragments. It should be noted that two or more pieces of identification information for the identification information can be configured as one or more pieces of identification information.

[00310] The UE_A10 may further include the first identification information and/or the second identification information and/or the third identification information and/or the fourth identification information in the PDU session creation request message and transmit them to request the creation of a PDU session belonging to network slice to report the network slice to which the PDU session belongs and which the UE_A10 is requesting, or to report the network slice to which the PDU session will belong.

[00311] More specifically, UE_A10 may transmit the first identification information and the second identification information in conjunction with each other to request the creation of a session PDU belonging to the network slice in the session PDU created for the DN identified by the second identification information to report the network slice to which the PDU session belongs and which the UE_A10 is requesting, or to report the network slice to which the PDU session will belong.

[00312] UE_A10 may further combine and transmit two or more pieces of identification information from the first to the fourth to create a request that takes into account all of the above situations. It should be noted that the complexities related to the UE_A10 transmitting each piece of identification information may not be limited to this.

[00313] It should be noted that the UE_A10 may determine which piece of identification information among the first to fourth identification information is included in the create session PDU request message based on the capability information of the UE_A10 and/or a policy such as a UE policy and/or UE_A10 preferences, and/or applications (higher level). It should be noted that the determination made by UE_A10 as to which piece of identification information should be included in the create session PDU request message is not limited to the determination described above.

[00314] SMF_A230 at core_B190 receives a PDU session creation request message and performs a third condition determination. The determination of the third condition is used to determine whether the SMF_A230 approves the request of the UE_A10. When determining the third condition, SMF_A230 determines whether the definition of the third condition is true or false. When the definition of the third condition is true, SMF_A230 initiates the procedure (A) of this procedure, and when the definition of the third condition is false, SMF_A230 initiates the procedure (B) of this procedure. It should be noted that the steps to be performed in the case where the determination of the third condition is false will be described below.

[00315] Next, steps will be described when the determination of the third condition is true, that is, each step of the procedure (A) within the procedure will be described. SMF_A230 selects the UPF_A235 for which a session PDU is to be created, and performs the determination of the 11th condition.

[00316] In this case, the definition of the 11th condition is used to determine whether each device performs process No. 2 in the core network. In this case, process #2 in the core network may include initiating and/or performing an authentication procedure when creating a PDU session by each device, and/or sending and/or receiving a session creation request message between SMF_A and UPF_A in the core network_B190, and /or transmitting and/or receiving a session creation response message (S1103), etc. When determining the 11th condition, SMF_A230 determines whether the determination of the 11th condition is true or false. SMF_A230 initiates the authentication and/or authorization procedure when creating a session PDU in the case when the definition of the 11th condition is true, and skips the authentication and/or authorization procedure when creating a session PDU in the case when the definition of the 11th condition is false. It should be noted that the details of the authentication and/or authorization procedure for creating a session PDU for process #2 in the core network will be described below.

[00317] The SMF_A230 then sends a session creation request message to the selected UPF_A235 based on the determination of the 11th condition and/or completion of the session creation authentication and/or authorization procedure of the PDU, and initiates procedure (A) within this procedure. It should be noted that SMF_A230 may initiate procedure (B) within this procedure without initiating procedure (A) within this procedure based on the completion of the authentication and/or authorization procedure when creating the PDU session.

[00318] In this case, the SMF_A230 may select one or more UPFs_A235 functions based on each piece of identification information obtained based on the receipt of the PDU session request message and/or network capability information and/or subscriber information, and/ or operator policy, and/or network status, and/or context, which is already contained in SMF_A230. Note that when multiple UPF_A235s are selected, SMF_A230 may send a session creation request message to each UPF_A235.

[00319] UPF_A235 receives a session request message and creates a context for the session PDU. In addition, the UPF_A235 sends a session creation response message to the SMF_A230 based on the reception of the session creation request message and/or the creation of the context for the session PDU. SMF_A230 additionally receives a session creation response message. It should be noted that the session creation request message and the session creation response message may be control messages sent and/or received on the N4 interface. The create session response message may further be a response message to the create session request message.

[00320] The SMF_A230 may further perform address assignment to assign an address to UE_A10 based on receiving a session creation request message PDU and/or selection of UPF_A235 and/or receiving a session creation response message. It should be noted that SMF_A230 may perform address assignment to assign an address to UE_A10 during the PDU session creation procedure, or may perform address assignment to assign the address of UE_A10 after the PDU session creation procedure is completed.

[00321] In particular, when SMF_A230 assigns an IPv4 address without using DHCPv4, SMF_A230 may perform address assignment during a PDU session creation procedure or may transmit the assigned address to UE_A10. In addition, when the SMF_A230 assigns an IPv4 address and/or an IPv6 address and/or an IPv6 prefix using DHCPv4, DHCPv6, or SLAAC (stateless address autoconfiguration), the SMF_A230 may perform address assignment after the PDU session creation procedure, or may transmit the assigned address equipment UE_A10. It should be noted that the address assignment performed by SMF_A230 is not limited to the above.

[00322] The SMF_A230 may further include the assigned address in the PDU session creation approval message and may transmit it to the UE_A10 based on the completion of the address assignment for the address assigned to the UE_A10, or may transmit the assigned address to the UE_A10 upon completion of the session PDU creation procedure.

[00323] SMF_A230 transmits to UE_A10 a PDU session creation approval message by AMF_A240 based on receiving a PDU session creation request message and/or selecting UPF_A235 and/or receiving a session creation response message and/or completing an address assignment to an address assigned to the equipment UE_A10 (S1110).

[00324] Specifically, the SMF_A230 transmits the PDU session creation approval message to the AMF_A240 using the N11 interface, and the AMF_A240 receiving the PDU session creation approval message transmits the PDU session creation approval message to the UE_A10 using the N1 interface.

[00325] It should be noted that when the PDU session is a PDN connection, the PDU session creation approval message may be a PDN connection approval message. The PDU Session Creation Accept message may further be a NAS message transmitted and/or received on the N11 interface and the N1 interface. In addition, the PDU session creation approval message is not limited to the above, and may be any message informing the PDU session creation approval.

[00326] UE_A10 receives a PDU session creation approval message from SMF_A230. UE_A10 receives the PDU Session Creation Acceptance message to recognize the content of various types of identification information included in the PDU Session Creation Acceptance message.

[00327] Next, UE_A10 transmits a PDU Session Creation Completion message to SMF_A230 via AMF_A240 based on completion of receipt of PDU Session Creation Acceptance Message (S1114). In addition, the SMF_A230 receives the PDU Session Creation Completion message and performs the determination of the second condition.

[00328] Specifically, UE_A10 sends a PDU session completion message to AMF_A240 using the N1 interface, and the AMF_A240 receiving the PDU session creation complete message sends a PDU session creation complete message to SMF_A230 using the N11 interface.

[00329] It should be noted that when the PDU session is a PDN connection, the PDU session creation complete message may be a PDN connection complete message, or may be a default EPS channel context activation approval message. In addition, the PDU session creation completion message may be a NAS message transmitted and/or received on the N1 interface and the N11 interface. In addition, the PDU session creation completion message should only be a response message to the PDU session creation approval message, but is not limited to, and may be a PDU session creation procedure completion message.

[00330] The definition of the second condition is used in SMF_A230 to determine the type of message to be transmitted and/or received on the N4 interface. When the determination of the second condition is true, process No. 3 in the reference network can be initiated (S1115). In this case, process #3 in the core network may include sending and/or receiving a session change request message and/or sending and/or receiving a session change response message, etc. SMF_A230 sends a session change request message UPF_A235 and further receives a session change approval message transmitted from the UPF_A235 receiving the session change request message. In addition, when the determination of the second condition is false, SMF_A230 executes process No. 2 in the core network. In other words, the SMF_A sends a create session request message to UPF_A235 and further receives a session change approval message sent from UPF_A235 receiving the session create request message.

[00331] Each device completes procedure (A) within the present procedure based on the transmission and/or reception of a session creation completed PDU message, and/or the transmission and/or reception of a session change response message, and/or the transmission and/or reception session creation response message, and/or sending and/or receiving RA (router advertisement).

[00332] Next, the steps will be described in the case of a false determination of the third condition, i.e., each step of the procedure (B) within this procedure will be described. SMF_A230 sends a PDU session creation rejection message to UE_A10 by AMF_A240 (S1122) and initiates a procedure (B) within the procedure.

[00333] Specifically, SMF_A230 transmits a PDU session creation rejection message to AMF_A240 using the N11 interface, and AMF_A240 receives a PDU session creation request message and sends a PDU session creation rejection message to UE_A10 using the N1 interface.

[00334] It should be noted that when the PDU session is a PDN connection, the PDU session creation reject message may be a PDN connection reject message. The PDU session creation rejection message may further be a NAS message transmitted and/or received on the N11 interface and the N1 interface. In addition, the PDU session creation rejection message is not limited to the above, and may be any PDU session creation rejection message.

[00335] In this case, SMF_A230 may include one or more identity information fragments 11 to 18 in the PDU session creation rejection message, or may report rejection of the UE_A10 request by including these identity information fragments. It should be noted that two or more pieces of identification information for the identification information can be configured as one or more pieces of identification information.

[00336] In addition, SMF_A230 may include an 11th identity and/or a 12th identity and/or a 13th identity and/or a 14th identity and/or a 15th identity , and/or the 16th identification information, and/or the 17th identification information, and/or the 18th identification information into the PDU session creation rejection message and transmit them to report the rejection of the PDU session creation request belonging to network slice, or report a network slice that does not have permission to belong to a session PDU.

[00337] More specifically, the SMF_A230 may send the 18th identity information and the 12th identity information in association with each other to report the rejection of a request to create a session PDU belonging to a network slice is rejected in a session PDU created for a DN , identified using the 12th identification information, or to report a network slice that does not have permission to belong to the session PDU.

[00338] In addition, the SMF A230 may include the 18th identification information in the PDU session creation rejection message and transmit it to report the rejection of the session creation request of the PDU belonging to the network slice in the registration area and/or the tracking area, to which UE_A10 currently belongs, or to report a network slice that does not have permission to belong to a session PDU.

[00339] In addition, the SMF_A230 may include the 18th identification information in the session creation rejection PDU message and transmit it to report the rejection of the session creation request of the PDU belonging to the network slice in the access network to which it is currently connected. UE_A10, or to report a network slice that does not have permission to belong to a session PDU.

[00340] In addition, the SMF_A230 may include the 11th identification information and/or the 14th identification information in the session creation rejection PDU message and transmit them to report the value of the first timer and indicate whether a procedure similar to this procedure needs to be performed again. after completing this procedure.

[00341] In addition, SMF_A230 may combine and transmit two or more pieces of identification information from the 11th to the 18th to create a request that takes into account all of the above situations. It should be noted that the complexities related to the SMF_A230 transmitting each piece of identification information may not be limited to this.

[00342] It should be noted that the SMF_A230 can determine which piece of identification information among the 11th to 18th identities should be included in the PDU session creation rejection message based on the received identity and/or network capability information, and/or policies, such as carrier policy, and/or network status.

[00343] In addition, the 12th identification information may be information about the same DNN as the DNN of the second identification information. Moreover, the 13th identification information may be information about the same PDU session ID as the PDU session ID of the third identification information. The 18th identity information may further be information transmitted when the first identity information is received and/or when the network slice from the first identity information is not allowed by the network. It should be noted that the determination made by the SMF_A230 as to which piece of identification information should be included in the session creation rejection PDU message is not limited to the determination described above.

[00344] As described above, the core_B190 notifies the UE_A10 of the congestion control applied by transmitting a PDU session reject message. As a result, the core network_B190 may report the congestion control application to the UE_A10 and/or inform the UE_A10 to perform congestion control and/or information to identify the type of congestion control applied and/or information to identify the congestion control target such as DNN and/ or an S-NSSAI corresponding to the applied congestion control and/or a timer value associated with the applied congestion control.

[00345] In this case, each piece of the above-described information may be information identified by one or more pieces of identification information from the 11th to 18th identification information.

[00346] UE_A10 may include one or more of the identity information pieces from identity information 11 to 18 in the PDU session creation rejection message received from SMF_A230.

[00347] Next, UE_A10 executes the fourth process based on the receipt of the PDU session creation rejection message (S1124). In addition, UE_A10 may perform a fourth process based on the completion of this procedure.

[00348] Next, a first example of the fourth process will be described.

[00349] Here, the fourth process may be a process in which UE_A10 recognizes the condition reported by SMF_A230. Moreover, the fourth process may be a process in which the UE_A10 stores the received identity as a context, or may be a process in which the UE transmits the received identity to a higher layer and/or a lower layer. In addition, the fourth process may be a process in which the UE_A10 recognizes the rejection of the request to apply this procedure.

[00350] Moreover, when UE_A10 receives the 14th identity information and the 11th identity information, the fourth process may be a process in which UE_A10 sets a value from the 14th identity information as the value of the first timer, or may be a process to start the first timer with the timer value set. Moreover, when UE_A10 receives the 11th identification information, the fourth process may be a process of realizing one or more of the first to 11th operating modes.

[00351] When UE_A10 receives the 18th identification information and the 11th identification information, the fourth process may further be a process in which the UE_A10 performs the 12th operation mode based on the NW slice identification information included in the 18th identification information, and association rules of the network slice included in the 18th identification information, or association rules of the network slice stored and preconfigured in UE_A10.

[00352] In addition, when UE_A10 receives a plurality of pieces of the 14th identification information and the 11th identification information, the fourth process may be a process in which the UE_A10 performs the 13th mode of operation based on the plurality of first timers included in each piece 14 th identification information, and the backoff timer priority control rules stored by UE_A10.

[00353] In addition, when UE_A10 receives a plurality of pieces of the 14th identification information and the 11th identification information, the fourth process may be a process in which the UE_A10 performs the 14th operation mode based on the plurality of first timers included in each piece 14 th identification information.

[00354] Meanwhile, modes of operation 12 to 15 may be congestion control initiated and executed by UE_A10 based on rules and/or policies in UE_A10. In particular, for example, the UE_A10 may be configured to include the following elements in the storage unit and/or the controller in the UE_A10: a policy (UE policy) and/or a rule, a policy and/or rule management function, a policy enforcement means by which UE_A10 operates based on policy and/or rule, one or more applications and session management instances (session manager) to manage one or more PDU sessions to be created or attempted to be created based on a request from each application, and can implement management overload initiated by the UE_A10 by executing any of the 12th to 15th operating modes as a fourth process based on the above items. In this case, the policy and/or rule may include one or more of a network slice associated rule and/or a backoff timer priority control rule and/or a network slice selection policy (NSSP), which may be further preconfigured. in UE_A10 or received from the network. In addition, the policy enforcement engine may be an NSSP enforcement engine. In addition, the application may be an application layer protocol, and the creation or attempt to create a PDU session may be made based on a request from the application layer protocol. In addition, the session management instance may be a software element that is dynamically generated for each session PDU. In addition, the S-NSSAI may be grouped as UE_A10 internal processing, or processing may be performed based on the S-NSSAI grouping. It should be noted that the internal configuration and processing of UE_A10 is not limited to this, and each element may be implemented by software or may be performed as software processing in UE_A10.

[00355] In addition, UE_A10 may switch to EPS in the fourth process or based on the completion of the fourth process, and may initiate position registration in the EPS based on the DCN ID included in the 18th identification information. It should be noted that the UE_A10 switch to EPS may be based on a handover procedure or may be a UE_A10 initiated RAT switch. In addition, when UE_A10 receives the 18th identity information including the DCN ID, UE_A10 may perform switching to EPS during the fourth process or after completion of the fourth process.

[00356] In addition, the fourth process may be a process in which the UE_A10 re-initiates the present procedure after a certain period of time has elapsed, or may be a process of transitioning to a state in which the request of the UE_A10 is limited or restricted.

[00357] In addition, UE_A10 may transition to the first state in accordance with the completion of the fourth process.

[00358] Next, a second example of the fourth process will be described.

[00359] Here, the fourth process may be a process in which UE_A10 recognizes the condition reported by SMF_A230. In addition, the fourth process may also be a process in which the UE_A10 stores the received identity as a context, or may be a process in which the UE transmits the received identity to a higher layer and/or a lower layer.

[00360] Further, in the fourth process, processing may be performed to identify the congestion control application based on one or more of the identification information pieces from the 11th to 18th identification information.

[00361] In addition, in the fourth process, processing may be performed to identify the applicable type of congestion controls from the first to fourth congestion controls, and to identify the applicable DNNs and/or S-NSSAIs associated with congestion control based on one or more fragments. identification information from identification information 11 to 18. In particular, the present process may be the process described in the 15th mode of operation.

[00362] In addition, in the fourth process, based on one or more pieces of identification information from the 11th to 18th identification information, an applicable value for the first timer from the 14th identification information associated with congestion control can be identified and configured, and the first timer can be started. In particular, the present process may be the process described in the 8th mode of operation.

[00363] In addition, in the fourth process, one or more of the first mode of operation through the seventh mode of operation may be performed in accordance with the initiation or termination of any of the processes described above.

[00364] In addition, in the fourth process, one or more of the ninth mode of operation through the 15th mode of operation may be performed in accordance with the initiation or termination of any of the processes described above.

[00365] In addition, UE_A10 may transition to the first state in accordance with the completion of the fourth process.

[00366] Although the detailed processes for the fourth process have been described using the first example and the second example, the fourth process need not be limited to these examples. For example, the fourth process may be a combined process consisting of a portion of the plurality of detailed processes described in the first example and a portion of the plurality of detailed processes described in the second example.

[00367] In addition, UE_A10 may receive a PDU session creation rejection message or not receive a PDU session creation approval message to recognize the rejection of the UE_A10 request. Each device terminates procedure (B) within the present procedure based on the transmission and/or reception of a PDU session creation rejection message.

[00368] Each device completes the present procedure based on completion of procedure (A) or (B) of the present procedure. It should be noted that each device may transition to the state in which the PDU session is created based on the completion of the procedure (A) of the present procedure, may recognize that the present procedure has been rejected, or each device may recognize that the present procedure has been rejected, enter the state in which the session PDU is not created, or transition to the first state based on the completion of the procedure (B) of the present procedure.

[00369] In addition, each device may, based on the completion of the present procedure, perform processing based on the identification information transmitted and/or received in the present procedure. In other words, UE_A10 may execute the fourth process based on the completion of the present procedure, or may transition to the first state upon completion of the fourth process.

[00370] In addition, the third condition determination may be made based on the identification information included in the PDU session request message and/or subscriber information and/or operator policy. For example, the third condition definition may be true when the network allows the UE_A10 request. In addition, the third condition determination may be false when the network does not allow the UE_A10 request. In addition, the third condition determination may be true when the network to which UE_A10 is connected and/or a device in the network supports the function requested by UE_A10 and may be false when the network and/or device does not support the function. The third condition definition may further be true when it is determined that the network is congested and may be false when it is determined that the network is not congested. It should be noted that the conditions for determining the truth or falsity of the third condition definition may not be limited to the above conditions.

[00371] In addition, a second condition determination may be made based on whether a session has been created on the N4 interface for the PDU session. For example, the second condition definition may be true when a session on the N4 interface for the session PDU has been created, and may be false when a session on the N4 interface for the session PDU has not been created. It should be noted that the conditions for determining the truth or falsity of the second condition definition may not be limited to the above conditions.

[00372] In addition, the 11th condition determination may be made based on the identification information included in the session creation request message PDU and/or subscriber information and/or operator policy. For example, the 11th condition definition may be true when the network allows authentication and/or authorization to be performed with DN_A5 during the present procedure. In addition, the 11th condition definition may be false when the network does not allow authentication and/or authorization with DN_A5 to be performed during the present procedure. In addition, the 11th condition definition may be true when the network serving as the connection destination of UE_A10 and/or a device in the network supports performing authentication and/or authorization with DN_A5 during the present procedure, or may be false when the network and/or the device does not support performing authentication and/or authorization with DN_A5 during this procedure. In addition, the 11th condition determination may be true when the 61st identification information is received, or may be false when the 61st identification information is not received. In other words, the 11th condition definition may be true when the container including information such as the SM PDU DN request container and/or the plurality of pieces of information is received, or may be false when the container is not received. It should be noted that the conditions for determining the truth or falsity of the 11th condition definition may not be limited to the above conditions.

[00373] By transmitting and/or receiving a PDU session reject message in the above procedure, core_B190 notifies UE_A10 of the applied congestion control, and UE_A10 can apply the congestion control provided by core_B190. The core network_B190 and UE_A10 may further apply a plurality of congestion controls by repeatedly executing the procedures and processes described in this procedure. It should be noted that the congestion controls used may be different types of congestion controls and/or congestion controls corresponding to different DNNs and/or congestion controls corresponding to different S-NNSAIs and/or congestion controls with different combinations of DNNs and S-NSSAIs.

[00374] [1.3.3. Overview of network-initiated session management procedure]

[00375] Next, an overview of the network-initiated session management procedure will be described. Hereinafter, the network-initiated session management procedure will also be referred to as the present procedure. The present procedure is a procedure for session management initiated and executed by the network for the created session PDU. It should be noted that the present procedure can be performed at any time after the completion of the registration procedure and/or the PDU session creation procedure described above and the transition of each device to the first state. In addition, each device may send and/or receive a message including identification information to stop or change congestion control during the present procedure, or may initiate a mode of operation based on the new congestion control provided by the network based on completion of the present procedure.

[00376] In addition, UE_A10 may stop applying the congestion control identified based on the control information transmitted and/or received through the present procedure. In other words, the core network_B190 may initiate the present procedure and transmit the control message and control information of the present procedure to the UE_A10 to notify the UE_A10 to stop applying the identified congestion control by using this control information.

[00377] It should be noted that the present procedure may be a network-initiated PDU session change procedure and/or a network-initiated PDU session release procedure or the like, or may perform a network-initiated session management procedure that is not limited to the above. It should be noted that each device may send and/or receive a PDU session change message in a network initiated PDU session change procedure, or may send and/or receive a PDU session release message in a network initiated PDU session release procedure.

[00378] [1.3.3.1. Example of first network-initiated session management procedure]

[00379] An example of a network-initiated session management procedure will be described with reference to FIG. 12. In this section, "the present procedure" refers to a network-initiated session management procedure. Each step of this procedure will be described below.

[00380] As described above, based on the completion of the registration procedure and/or the PDU session creation procedure, each device in UE_A10 and core_B190 that transitions (S1200) to the first state starts a network-initiated session control procedure at any point in time. In this case, the device in the core network_B190 that initiates the present procedure may be an SMF_A and/or AMF_A, and the UE_A may send and/or receive a message within the present procedure via the AMF_A and/or access network_B.

[00381] Specifically, the device in the core network_B190 sends a message (S1202) requesting network-initiated session control to the UE_A. In this case, the device in the core network_B190 may include the 21st identification information in the network-initiated session control request message, or may report the request to the core network_B190 by including this identification information.

[00382] Then, the UE_A receiving the network-initiated session control request message transmits a network-initiated session control end message (S1204). In addition, UE_A may perform the fifth process based on the 21st identification information received from the core network_B190 (S1206) and end the present procedure. In addition, UE_A10 may perform the fifth process based on the completion of the present procedure.

[00383] An example of the fifth process will be described below.

[00384] In this case, the fifth process may be a process in which the UE_A10 recognizes the theme defined by the core_B190, or may be a process in which the UE_A10 recognizes the request of the core_B190. In addition, the fifth process may be a process in which the UE_A10 stores the received identity as a context, or may be a process in which the UE transmits the received identity to a higher layer and/or a lower layer.

[00385] In addition, the message sent and/or received in the network-initiated session control request may be a PDU SESSION CHANGE COMMAND, may be a PDU SESSION RELEASE COMMAND, but not limited.

[00386] It should be noted that UE_A10 may execute the UE_A10's congestion control identification process based on the received 21st identification information in the fifth process. In this case, the overload control identification process may be the 17th operation mode.

[00387] When UE_A10 receives the 21st identification information, the fifth process may further be the 16th mode of operation. In particular, it may be, for example, the process of stopping one or more timers operating on the basis of the fourth process described above.

[00388] In other words, the UE_A10 receiving the 21st identification information performs the 17th mode of operation to identify the congestion control that the network informs should be stopped or changed, and then performs the 16th mode of operation to stop or change identified overload control.

[00389] In addition, each device may, based on the completion of the present procedure, perform processing based on the identification information transmitted and/or received in the present procedure. In other words, UE_A10 may execute the fifth process upon completion of the present procedure, or may terminate the present procedure upon completion of the fifth process.

[00390] In the above procedure, the core network_B190 may inform the UE_A10 to stop or change the congestion control applied by the UE_A10 by sending and/or receiving a network initiated session control request message. In addition, UE_A10 may stop or change the congestion control applied by UE_A10 based on the network initiated session control request message. In this case, when UE_A10 applies one or more congestion controls, UE_A10 may identify congestion control to be stopped or changed based on receiving the identification information included in the network-initiated session control request message from core network_B190. It should be noted that the congestion controls applied may also be different types of congestion controls and/or congestion controls corresponding to different DNNs and/or congestion controls corresponding to different S-NNSAIs and/or congestion controls with different combinations of DNNs and S-NSSAIs.

[00391] [1.3.3.2. Example of Second Network Initiated Session Control Procedure]

[00392] According to the example of the first network-initiated session control procedure described in Section 1.3.3.1, the congestion control procedure is stopped in the procedure regardless of whether the congestion control procedure applied by UE_A10 is one of the congestion control procedures from the first congestion control procedure to the fourth congestion control procedure .

[00393] Without being limited to the foregoing, the procedure described in the example of the first network-initiated session control procedure described in Section 1.3.3.1 may also be a procedure performed in accordance with congestion control. For example, the procedure may be performed for congestion control classified as first congestion control, third congestion control, or fourth congestion control among one or more congestion controls applied to UE_A10.

[00394] In other words, UE_A10 may stop the congestion control corresponding to the first congestion control, the third congestion control, and/or the fourth congestion control by the fifth process.

[00395] During the timing of the backoff timer corresponding to the second congestion control, UE_A10 may respond with respect to the core network_B190 without stopping the backoff timer corresponding to the second congestion control if UE_A10 receives a network-initiated session control request message with respect to the second control overload.

[00396] In other words, while the backoff timer corresponding to S-NSSAI #A is timing, UE_A10 can respond to the backbone_B190 without stopping the backoff timer corresponding to S-NSSAI #A when UE_A10 receives a triggered request message. network session management for S-NSSAI No. A and any overloaded DNN.

[00397] Thus, with respect to the second congestion control, upon receiving the network-initiated session control request message, UE_A10 may transmit a backbone_B190 message in response to the network-initiated session control request message, but may continue congestion control. Therefore, it is possible to suppress transmission of the UE-initiated session control request message governed by the second congestion control.

[00398] Here, as described above, the network-initiated session control request message in the present embodiment may be a CHANGE PDU SESSION COMMAND message in a network-initiated PDU session control procedure, or may be a PDU SESSION RELEASE COMMAND message in network-initiated session PDU release procedure.

[00399] As described above, the Network-Initiated Session Control Completion message for the response to the PDU CHANGE SESSION COMMAND message according to the present embodiment may further be a PDU CHANGE SESSION COMPLETE message, and the Network-Initiated Session Control Completion message for The response to the PDU SESSION RELEASE COMMAND message according to the present embodiment may be a PDU RELEASE COMPLETE message. In addition, when the network-initiated session control request message is a PDU change session command and/or PDU session release message, UE_A10 and core_B190 may further perform the detailed processes described below in addition to the processes described above.

[00400] For example, when the core network_B190 transmits a network-initiated session control request message including reactivation need information, the processing may be performed as follows. The reactivation need information is further 5G activation request information, a specific example of which can be the value of 5G Session Control Cause No. 39 (5GSM Cause No. 39).

[00401] Hereinafter, a first example of a process and procedure at the time of receiving information about the need for reactivation will be described.

[00402] When UE_A10 receives a network-initiated session control request message including reactivation need information, UE_A10 does not initiate a UE-initiated session creation procedure PDU again immediately after the network-initiated session control procedure is completed, but waits for control release. overload and then re-initiates the UE-initiated PDU session creation procedure. In this case, the UE-initiated PDU session creation procedure may be a UE-initiated PDU session creation procedure for the PDU session type, SSC mode, and DNN and S-NSSAI provided in the UE-initiated PDU session creation procedure when a changeable or release PDU session is created. .

[00403] Waiting for the release of the overload control may be further performed after the expiration of the timer corresponding to the second overload control. In other words, it may be executed after the timer corresponding to the second overload control has expired and/or after the timer corresponding to the second overload control has been reset.

[00404] In addition, UE_A10 may include the following additional message in the network-initiated session control termination message.

[00405] The additional information may be timer expiration wait information and/or timer remaining time value information. In this case, the timer may be a timer corresponding to the second overload control. In addition, waiting for the timer to expire may be performed after the timer has expired. In other words, it may be executed after the timer corresponding to the second overload control has expired and/or after the timer corresponding to the second overload control has been reset.

[00406] In addition, the core network_B190 may receive a network-initiated session control termination message including an additional message and identify the value of the remaining timer countdown time. The UE-initiated PDU session creation procedure may be further identified after a time equal to the remaining timer countdown value has elapsed.

[00407] In this case, the remaining value of the timer countdown time identified by the core network_B190 may be a value that takes into account the offset compared to the value from the received side information, between the time of transmission by the equipment UE_A10 of the message about the end of the network-initiated session control and the time of receipt of the message backbone_B190.

[00408] In addition, the present invention is not limited to the first example of the process and procedure at the time of receiving the reactivation request information, and the second example of the process and procedure at the time of receiving the reactivation request information can be performed as follows.

[00409] As described above with respect to the second congestion control, upon receiving the network-initiated session control request message, UE_A10 may send a backbone_B190 message in response to the network-initiated session control request message, but may continue congestion control. Therefore, suppression of transmission of the UE-initiated session control request message controlled by the second control continues, but UE_A10 and/or core_B190 can be configured to allow transmission during the re-initiation of the UE-initiated PDU session creation procedure.

[00410] In other words, when UE_A10 receives a network-initiated session control request message including reactivation need information, UE_A10 initiates a UE-initiated session creation procedure PDU again after the network-initiated session control procedure is completed. In this case, the UE-initiated PDU session creation procedure may be a UE-initiated PDU session creation procedure for the PDU session type, SSC mode, and DNN and S-NSSAI provided in the UE-initiated PDU session creation procedure when a changeable or release PDU session is created. .

[00411] UE_A10 and core_B190 may further execute and terminate the exception-allowed procedure, while UE_A10 continues to apply congestion control, but UE_A10 may suppress the initiation of another UE-initiated session control procedure suppressed by the second congestion control.

[00412] In addition, the present invention is not limited to the first and second examples of the process and procedure at the time of receiving the reactivation request information, and the third example of the process and procedure at the time of receiving the reactivation request information can be performed as follows.

[00413] As described above with respect to the second congestion control, upon receiving the network initiated session control request message, the UE_A10 may send a core network_B190 message in response to the network initiated session control request message. When UE_A10 receives a network-initiated session control request message including reactivation need information, UE_A10 further stops applying the second congestion control.

[00414] In other words, UE_A10 may continue to manage congestion when the network-initiated session management request message does not include reactivation need information. In this case, transmission of the UE-initiated session control request message governed by the second congestion control is suppressed.

[00415] Therefore, when the UE_A10 receives the network-initiated session control request message including the need for reactivation information, the UE_A10 initiates the UE-initiated session creation procedure PDU again after the network-initiated session control procedure is completed. Meanwhile, the UE-initiated PDU session creation procedure may be a UE-initiated PDU session creation procedure for the PDU session type, SSC mode, and DNN and S-NSSAI provided in the UE-initiated PDU session creation procedure when the modified or released PDU session is created.

[00416] In addition, the present invention is not limited to the first, second, and third examples of the process and procedure at the time of receiving the reactivation request information, and the reactivation need information can be configured to prevent it from being transmitted by the core network_B190, as follows.

[00417] More specifically, the core network_B190 can be configured to suppress the inclusion of information about the need for reactivation when transmitting a network-initiated session control request message to the UE_A10 to which congestion control is applied.

[00418] Alternatively, the core network_B190 may be configured to suppress the inclusion of the need for reactivation information when the core network_B190 sends a network initiated session control request message to the UE_A10 to which the second congestion control is applied.

[00419] The processes and procedures for the UE_A10 equipment and the core network_B190 have been described above, but the processes of the core network_B190 described in this section may in particular be a process performed by a control device such as SMF_A230 and/or AMF_A240 in the core network_B190. Therefore, the phrase "reference network_B190 transmits and receives a control message" may mean that a control device such as SMF_A230 and/or AMF_A240 in core network_B190 transmits and receives a control message.

[00420] In addition, the present invention is not limited to this section. In the phrases used in the description of the present embodiment, the process of releasing the applied congestion control or the process of stopping the congestion control may include the process of stopping the backoff timer corresponding to the congestion control, and the process of continuing to apply the congestion control or the process of continuing the congestion control may include continuing backoff timer corresponding to congestion control.

[00421] In the first, second, and third examples of the process and procedure described in this section, at the time of receiving the reactivation request information, a network-initiated session control request message and/or a network-initiated session control procedure were further described to the UE with respect to to S-NSSAI No. A and any overloaded DNN.

[00422] In other words, S-NSSAI #A and any overloaded DNN may be S-NSSAI #A and any DNN associated with a session PDU subject to a network-initiated session control request message and/or a network-initiated control procedure. session from this section.

[00423] In addition, UE_A10 and core_B190 may perform the SSC Mode 2 anchor move procedure, including the procedure of this section, and switch to a PDU session anchor or a PDU session with a different anchor to continue communication. In this case, the SSC Mode 2 anchor move procedure is the procedure initiated and started by the core_B190 and the procedure associated with the transmission of the PDU session release command performed within this procedure in one of the procedures described in this section.

[00424] In addition, UE_A10 and core_B190 may perform the SSC Mode 3 anchor move procedure, including the procedure of this section, and switch to a PDU session anchor or a PDU session with a different anchor to continue communication. In this case, the SSC Mode 3 anchor move procedure is the procedure initiated and started by the core_B190 and the procedure associated with the transmission of the command to change the PDU session performed within this procedure in one of the procedures described in this section.

[00425] Next, the process at the time of moving the UE with PLMN change in a state in which congestion control is applied will be described.

[00426] Here, specifically, the process at the time of changing the PLMN by the UE_A10 in the state in which the first congestion control is applied will be described. Meanwhile, the first overload control and the process controlled at the time of applying the first overload control may be as described above.

[00427] Repeating the description, the first congestion control may be a DNN based congestion control. For example, the first congestion control may be the congestion control applied by the NW to UE_A10 based on the UE-initiated session control request rejection message in case the NW receives a UE-initiated session control request using DNN #A from UE_A10, and the NW detects congestion with respect to a particular DNN, such as DNN #A. In this case, when applying the first congestion control, the UE_A10 may start the backoff timer corresponding to the first congestion control received from the NW and may not transmit a request for UE-initiated session control using DNN #A before this backoff timer expires. In addition, "using the DNN" may mean including information about the DNN in a UE-initiated session control request, such as a session creation request PDU message.

[00428] Here, for explanation, "first congestion control" is formulated as "first congestion control for a particular DNN".

[00429] In addition, in the first congestion control, even when the UE-initiated session control request does not include DNN information, the NW can select a default DNN initiated by the NW and configure it as a target for congestion control. In other words, the first congestion control may be the congestion control applied by the NW to the UE_A10 based on the UE-initiated session control request reject message when the NW receives a UE-initiated session control request from the UE_A10 that does not use a DNN, and NW detects an overload on the default DNN. In this case, when applying the first congestion control, UE_A10 may start the backoff timer corresponding to the first congestion control received from the NW, and may not transmit a request for a UE-initiated session control that does not use a DNN until this backoff timer expires. . Also, not using a DNN may mean that the DNN information is not included in a UE-initiated session control request, such as a session creation request PDU message.

[00430] Here, for clarification, the first congestion control for the default DNN is applied based on a request for UE-initiated session control that does not use DNN information, and therefore the phrase is formulated as "congestion control without using DNN" to distinguish from the phrase "congestion control for a specific DNN". In addition, a request for UE-initiated session control, such as a PDU session request message that does not use a DNN, is formulated as a request for UE-initiated session control without using a DNN. For example, a session request message to create a PDU session without using a DNN is a session request message to create a PDU session that does not use a DNN.

[00431] The UE_A10 may be further configured to transmit a PDU session creation request message using a particular DNN in the new PLMN when the backoff timer corresponding to the first congestion control for the particular DNN is counted down by the UE_A10 upon PLMN change, or when the backoff timer is deactivated transfer corresponding to the first congestion control for a particular DNN. Therefore, UE_A10 may send a PDU session creation request message using a particular DNN based on the configuration.

[00432] In this case, UE_A10 may continue to count until the timer expires and not stop the backoff timer. Alternatively, UE_A10 may continue to hold the deactivated backoff timer in the deactivated state.

[00433] Thus, the first congestion control for a particular DNN may also correspond to a PLMN.

[00434] For example, when the first congestion control for a specific DNN is applied, the UE associates a backoff timer with the PLMN and the specific DNN to start counting, and when the backoff timer is reset or deactivated, the session PDU using the specific DNN associated with the backoff timer, may not be created in the PLMN associated with the backoff timer. In addition, when the backoff timer is deactivated, a PDU session using a particular DNN associated with the backoff timer may not be created in the PLMN associated with that backoff timer until the terminal is powered down or the USIM is removed. In addition, by resetting the backoff timer in the PLMN associated with the backoff timer, a PDU session can be created using the particular DNN associated with the backoff timer.

[00435] In other words, the UE_A10 may be configured to send a PDU session creation request message using a particular DNN in a new PLMN when the UE_A10 counts down the backoff timer corresponding to the first congestion control for the particular DNN and the PLMN until it is replaced on change. PLMN, or when the backoff timer corresponding to the first congestion control for a particular DNN and PLMN is deactivated prior to its change, and when the backoff timer corresponding to the first congestion control for a particular DNN and PLMN is not counted down after the change, and when the backoff timer is not deactivated transmission corresponding to the first congestion control for a particular DNN and PLMN after it has changed. UE_A10 may optionally send a PDU session creation request message using a specific DNN based on the configuration.

[00436] The UE_A10 may be further configured to send a PDU session creation request message that does not use a DNN in the new PLMN when the UE_A10 counts down the backoff timer corresponding to the first congestion control without using a DNN when the PLMN is changed, or when deactivated a backoff timer corresponding to the first congestion control without using a DNN. Therefore, UE_A10 may send a PDU session creation request message using a particular DNN based on the configuration.

[00437] In this case, UE_A10 may continue to count until the timer expires and not stop the backoff timer. Alternatively, UE_A10 may continue to hold the deactivated backoff timer in the deactivated state.

[00438] Thus, the first congestion control without using a DNN may also correspond to a PLMN. In other words, the UE_A10 may be configured to send a PDU session creation request message without using a DNN in the new PLMN when the UE_A10 counts down the first congestion control backoff timer without using the DNN corresponding to the PLMN until it is replaced on a PLMN change, or when deactivated. congestion control first control backoff timer without using the DNN corresponding to the PLMN before it is changed, and when the first congestion control backoff timer without using the DNN corresponding to the PLMN is not counted after the change, and when the first congestion control backoff timer is not deactivated without using the DNN corresponding to the PLMN. UE_A10 may further send a session creation request message PDU that does not use a DNN based on the configuration.

[00439] As described above, UE_A10 can perform the same process regardless of whether the first congestion control is for a particular DNN or without using a DNN.

[00440] In other words, the UE_A10 may be configured to send a PDU session creation request message that does not use DNNs and/or a PDU session creation request message that does not use DNNs, which are adjusted by congestion control corresponding to the PLMN to of its change, in a new PLMN, when UE_A10 counts down the first congestion control corresponding PLMN backoff timer until it is replaced at a PLMN change, or when the first congestion control backoff timer corresponding to a PLMN is deactivated before its change, and when the backoff timer is not counted down transmission of the first congestion control corresponding to the PLMN after its change, and when the delay timer of transmission of the first congestion control corresponding to the PLMN is not deactivated.

[00441] Alternatively, UE_A10 may perform a different process depending on whether the first congestion control is for a particular DNN or not using a DNN.

[00442] UE_A10 may be further configured not to transmit a PDU session creation request message using a particular DNN in a new PLMN when UE_A10 counts down the backoff timer corresponding to the first congestion control for a particular DNN on PLMN change, or when deactivated a backoff timer corresponding to the first congestion control for the specific DNN. Therefore, UE_A10 can adjust the transmission of the PDU session creation request message using a particular DNN based on the configuration.

[00443] In this case, UE_A10 may continue to count until the timer expires and not stop the backoff timer. Alternatively, UE_A10 may continue to hold the deactivated backoff timer in the deactivated state.

[00444] Thus, the first congestion control for a particular DNN can be applied to different PLMNs.

[00445] On the other hand, the UE_A10 may be configured to send a PDU session creation request message that does not use a specific DNN in the new PLMN when the UE_A10 counts down the backoff timer corresponding to the first congestion control without using the DNN when the PLMN is changed , or when the backoff timer corresponding to the first congestion control without using a DNN is deactivated. Therefore, UE_A10 may send a PDU session creation request message using a particular DNN based on the configuration.

[00446] In this case, UE_A10 may continue to count until the timer expires and not stop the backoff timer. Alternatively, UE_A10 may continue to hold the deactivated backoff timer in the deactivated state.

[00447] Thus, the first congestion control without using a DNN may also correspond to a PLMN.

[00448] For example, when first congestion control is applied without using a DNN, the UE associates a backoff timer with a PLMN and no DNN to start counting, and when the timer is reset or deactivated, a PDU session without using a DNN associated with the backoff timer may not be created in the PLMN associated with the backoff timer. In addition, when the backoff timer is deactivated, a PDU session without using the DNN associated with the backoff timer may not be created in the PLMN associated with the backoff timer until the terminal is powered down or the USIM is removed. In addition, when the backoff timer is reset, creation of a PDU session without using the DNN associated with the backoff timer can be performed in the PLMN associated with the backoff timer.

[00449] In other words, the UE_A10 may be configured to send a PDU session creation request message without using a DNN in a new PLMN when the UE_A10 counts down the first congestion control backoff timer without using the DNN corresponding to the PLMN until it is replaced on a PLMN change, or when the first congestion control backoff timer is deactivated without using the DNN corresponding to the PLMN before it is changed, and when the first congestion control backoff timer is not running without using the DNN corresponding to the PLMN after it is changed, and when the first congestion control backoff timer is not deactivated without using the DNN corresponding to the PLMN. UE_A10 may further send a session creation request message PDU that does not use a DNN based on the configuration.

[00450] In this case, the first congestion control either performs the same process for a particular DNN or does not use a DNN, or performs a different process because the process associated with the PLMN change can be configured based on the information preconfigured in UE_A10, but can be determined based on whether the second PLMN after replacing the PLMN with it is equivalent to the first PLMN before it is replaced. For example, when the second PLMN after being replaced is not equivalent to the PLMN of the first PLMN before it was replaced, the same process can be applied. When the second PLMN after being replaced is equivalent to the PLMN of the first PLMN before it is replaced, another process can be performed.

[00451] In addition, in the present embodiment, deactivation of the backoff timer may mean that the congestion control associated with the backoff timer and/or the backoff timer has transitioned to the deactivated state. When UE_A10 receives a timer value related to deactivation, UE_A10 may deactivate the backoff timer and/or congestion control corresponding to the backoff timer.

[00452] In this case, the deactivated backoff timer and/or congestion control corresponding to the backoff timer may correspond to one or more of the first to fourth congestion control types. The type of congestion control corresponding to the deactivated backoff timer and/or the deactivated congestion control corresponding to the backoff timer can be similarly determined and identified upon receipt of the value of the backoff timer.

[00453] More specifically, UE_A10 may receive from the NW the 14th identification information and the 15th identification information about deactivating the backoff timer and/or congestion control corresponding to the backoff timer, and deactivate the backoff timer for the congestion control type of 15- and identification information.

[00454] In addition, in a state in which the backoff timer and/or congestion control is deactivated, application of congestion control can be continued until the terminal is powered down or the USIM is removed. The process adjusted at this time may further be the same process adjusted when the backoff timer counts down according to the congestion control type.

[00455] The UE_A10 and NW process associated with changing the PLMN described above is described for the first congestion control and/or backoff timer for the first congestion control, but the same process may also be performed for the second congestion control, the third congestion control, and the fourth overload control. However, a session creation request message of a PDU whose transmission is being throttled or allowed may be a message corresponding to each type. In other words, the congestion control and/or the backoff timer corresponding to the congestion control may also correspond to the PLMN regardless of the type of congestion control. Alternatively, congestion control and/or backoff timer corresponding to congestion control may also correspond to the PLMN regardless of the type of congestion control. Therefore, for the first congestion control, the second congestion control, and the third congestion control, the congestion control and/or backoff timer corresponding to the congestion control can be configured to conform to the PLMN. Therefore, for the first congestion control without using a DNN, the second congestion control without using a DNN, and the third congestion control without using a DNN, the congestion control and/or backoff timer corresponding to the congestion control can be configured to match the PLMN, and the first congestion control for a specific The DNN may not match the PLMN. In addition, the process when each congestion control corresponds to the PLMN and/or the process related to the backoff timer corresponding to each congestion control may be a process for the first congestion control associated with the PLMN as described above and/or the first control the overload in the process description relating to the backoff timer corresponding to the first congestion control corresponding to the PLMN as described above can be replaced by congestion control of each second to fourth type. In addition, the process when each congestion control does not match the PLMN and/or the process related to the backoff timer corresponding to each congestion control may be a process for the first congestion control that does not match the PLMN as described above, and/ or the first congestion control in the process description relating to the backoff timer corresponding to the first congestion control that does not correspond to the PLMN as described above may be replaced by congestion control of each second to fourth type. However, as described above, the session creation request message of the PDU whose transmission is being throttled or allowed may be a message corresponding to each type.

[00456] In addition, in the description of the present embodiment, a statement that NW is transmitting to UE_A10 may mean that AMF or SMF is transmitting to UE_A10, and a statement that UE_A10 is transmitting to NW may mean that UE_A10 is transmitting to AMF or SMF. The statement that the NW is receiving from the UE_A10 may further mean that the AMF or SMF is receiving from the UE_A10, and the statement that the UE_A10 is receiving from the NW may mean that the UE_A10 is receiving from the AMF or SMF.

[00457] [1.4 Modified Fourth Process Example]

[00458] Although the fourth process has been described in the present embodiment, it is not limited to the previous description, and the following process may be performed in the fourth process.

[00459] This modified example mainly refers to the mode of operation of the registration procedure shown in FIG. 10 and/or the PDU session registration procedure shown in FIG. 11. The present embodiment further relates to a case in which the PDU session creation rejection message (S1122) received by the UE_A includes a 15th identification information, and/or a 14th identification information, and/or an 11th identification information in the PDU session creation procedure shown in FIG. eleven.

[00460] It should be noted that in the present modified example, the 15th identification information is information about one or more values of the present procedure rejection reason reported by the NW to the UE for a case other than applying congestion control. The 14th identification information is information containing the backoff timer value. The 11th identification information is information containing retry information. The backoff timer may be the first timer used in the third congestion control described above in the present embodiment, and is not limited thereto as long as it is a communication system timer that can be recognized by the UE. It should be noted that the phrase "backoff timer SM" is used to distinguish the backoff timer from the first timer described above. In addition, when the PDU session creation procedure does not include DNN information, the phrase "without using DNN" is used to distinguish from control of a control signal including DNN information. In addition, similarly, when the PDU session creation procedure does not include S-NSSAI information, the phrase "without using S-NSSAI" is used to distinguish from control of a control signal including S-NSSAI information.

[00461] The fourth process (S1124) can be performed according to the contents of the 11th identity and/or the 14th identity and/or the 15th identity included in the PDU session creation rejection message received by the UE_A .

[00462] The SMF_A230 or AMF_A240 may load the backoff timer SM from the 14th identity information and send a PDU session creation rejection message (S1122) to the UE_A10 when the failure reason value from the 15th identity information is not due to insufficient resources, and/ or insufficient resources for a certain slice and DNN, and/or insufficient resources for a certain slice.

[00463] In this case, UE_A10 may perform the fourth process based on the received backoff timer value SM when the reject reason value of the 15th identity is not due to insufficient resources, and/or insufficient resources for specific slices and DNNs, and/or insufficient resources for certain slices, and/or failed user authentication or authorization, and/or is outside the LADN service area, and/or only IPv4 is allowed as a PDU session type, and/or only IPv6 is allowed as a PDU session type, and /or session PDU does not exist.

[00464] Specifically, UE_A10 may execute the first process example, described below as the fourth process example of this modified example, when the backoff timer SM value is non-zero or invalid.

[00465] UE_A10 may start an SM backoff timer for a PLMN and/or a DNN and/or an S-NSSAI, may also start an SM backoff timer for a PLMN and/or a non-DNN and/or an S-NSSAI, may also start the SM backoff timer for the PLMN and/or DNN and/or non-S-NSSAI, and may also start the SM backoff timer for the PLMN and/or non-DNN and/or non-S-NSSAI.

[00466] In addition, UE_A10 may suppress the transmission of a message (1011) with a request to create a session PDU based on the value of the backoff timer SM.

[00467] Specifically, the UE_A10 may suppress reconnection using another DNN-related PDU session request message and the S-NSSAI parameters transmitted in the PDU session request message (1011) until the backoff timer SM for the PLMN and/or DNN and/or S-NSSAI will expire and/or until the terminal is powered on/off or the USIM (Universal Subscriber Identity Module) is inserted/removed.

[00468] In addition, UE_A10 may suppress reconnection using another non-DNN related PDU session request message and the S-NSSAI parameters transmitted in the PDU session request message (1011) until until the PLMN and/or non-DNN and/or S-NSSAI backoff timer SM expires, and/or until the terminal is powered on/off or the USIM (universal module) is inserted/removed subscriber identification).

[00469] In addition, UE_A10 may suppress reconnection using another DNN-related PDU session request message and the non-S-NSSAI parameters transmitted in the PDU session request message (1011) until the backoff timer SM for PLMN and/or DNN and/or non-S-NSSAI and/or until terminal power is turned on/off or USIM (Universal Identification Module) is inserted/removed subscriber).

[00470] In addition, UE_A10 may suppress reconnection using another non-DNN related PDU session request message and the non-S-NSSAI parameters sent in the PDU session request message (1011) while backoff timer SM for PLMN and/or non-DNN and/or non-S-NSSAI expires and/or terminal power is turned on/off or USIM (Universal Identification Module) is inserted/removed subscriber).

[00471] UE_A10 may further execute a second process example different from the first process example as a fourth process example of this modified example when the backoff timer SM is invalid.

[00472] The UE_A10 may suppress reconnection using another DNN-related PDU session request message and the S-NSSAI parameters transmitted in the PDU session request message (1011) until the terminal is powered on/off , or until USIM (Universal Subscriber Identity Module) is inserted/removed.

[00473] In addition, UE_A10 may suppress reconnection using another non-DNN related PDU session request message and the S-NSSAI parameters transmitted in the PDU session request message (1011) while the terminal is powered will not be enabled/disabled, or until USIM (Universal Subscriber Identity Module) is inserted/removed.

[00474] In addition, the UE_A10 may suppress reconnection using another DNN-related PDU session request message and the non-S-NSSAI parameters transmitted in the PDU session request message (1011) while the terminal is powered will not be enabled/disabled, or until USIM (Universal Subscriber Identity Module) is inserted/removed.

[00475] In addition, UE_A10 may suppress reconnection using another non-DNN related PDU session request message and the non-S-NSSAI parameters sent in the PDU session request message (1011) until the terminal will not be powered on/off, or until the USIM (Universal Subscriber Identity Module) is inserted/removed.

[00476] UE_A10 may further execute a third process example, different from the first and second process examples, as the fourth process example of this modified example, with backoff timer SM set to zero.

[00477] UE_A10 may stop operation with the backoff timer SM activated corresponding to the DNN and S-NSSAI sent in the PDU session request message (1011) and send another PDU session request message using DNN and S- NSSAI transmitted in the message (1011) with a request to create a session PDU.

[00478] In addition, UE_A10 may stop operation if the backoff timer SM corresponding to the non-DNN and S-NSSAI transmitted in the PDU session request message (1011) has started operation, and send another create request message. session PDU using non-DNN and S-NSSAI transmitted in the message (1011) with a request to create a session PDU.

[00479] In addition, UE_A10 may stop operation if the backoff timer SM corresponding to the DNN and non-S-NSSAI transmitted in the PDU session request message (1011) has started operation, and send another create request message. session PDU using the DNN and non-S-NSSAI sent in the Create Session PDU Request message (1011).

[00480] In addition, UE_A10 may stop operation with the backoff timer of the SM corresponding to the non-DNN and non-S-NSSAI sent in the create session request message (1011) PDU activated, and send another session request message PDU using non-DNN and non-S-NSSAI transmitted in the message (1011) with a request to create a session PDU.

[00481] It should be noted that UE_A10 does not stop the activated backoff timer SM when the PLMN changes or when changing from N1 mode to S1 mode. This is because, for example, when the PLMN change returns to the original PLMN again from the PLMN destination change, the backoff timer activated by the original PLMN is still active and the control signaling applied to the original PLMN is still applied.

[00482] UE_A10 may further perform a fourth procedure example as a fourth example process of this modified example when performing a PLMN change while the backoff timer SM is running before the PLMN change starts. In this case, the PLMN before the change is called the original PLMN.

[00483] The UE_A10 may send a PDU session creation request message using the same S-NSSAI and DNN as the S-NSSAI and DNN corresponding to the SM backoff timer activated by the source PLMN when the SM backoff timer activated by the source PLMN for S-NSSAI and DNN, not activated at PLMN change destination.

[00484] In addition, UE_A10 may send a PDU session creation request message using the same S-NSSAI and non-DNNs as S-NSSAI and non-DNNs corresponding to the SM backoff timer activated by the source PLMN when the timer backoff SM activated by source PLMN for S-NSSAI and non-DNN is not activated at PLMN change destination.

[00485] In addition, UE_A10 may send a PDU session creation request message using the same non-S-NSSAI and DNNs as non-S-NSSAI and DNNs corresponding to the SM backoff timer activated by the source PLMN when the timer backoff SM activated by originating PLMN for non-S-NSSAI and DNN not activated at PLMN change destination.

[00486] In addition, UE_A10 may send a PDU session request message using the same non-S-NSSAI and non-DNNs as non-S-NSSAI and non-DNNs corresponding to the SM backoff timer activated by the original PLMN when the backoff timer SM activated by the source PLMN for non-S-NSSAI and non-DNN is not activated at the PLMN change destination.

[00487] The UE_A10 may further execute a fifth procedure example different from the first, second, and third procedure examples as the fourth process example of this modified example when the cause value of the 15th identity means "user authentication or authentication failed" , or "only IPv4 PDU session type allowed", or "only IPv6 PDU session type allowed".

[00488] In particular, the fifth example of the procedure may be a procedure in which the UE_A10 may not automatically transmit a reconnection using a different DNN-related PDU session request message and the S-NSSAI parameters transmitted in the (1011) message with a request to create a session PDU, until the session PDU type used in the message (1011) with a request to create a session PDU changes, or until the power of the terminal is turned on/off, or until a USIM (Universal Subscriber Identity Module) is inserted /deleted

[00489] In addition, it may be a procedure in which the UE_A10 may not automatically transmit a reconnect using a different non-DNN related PDU session request message and the S-NSSAI parameters transmitted in the (1011) message with a request to create a session PDU, until the session PDU type used in the message (1011) with a request to create a session PDU changes, or until the power of the terminal is turned on/off, or until a USIM (Universal Subscriber Identity Module) is inserted /deleted

[00490] In addition, it may be a procedure in which the UE_A10 may not automatically transmit a reconnect using another DNN-related PDU session request message and the non-S-NSSAI parameters transmitted in the (1011) message with a request to create a session PDU, until the session PDU type used in the message (1011) with a request to create a session PDU changes, or until the power of the terminal is turned on/off, or until a USIM (Universal Subscriber Identity Module) is inserted /deleted

[00491] In addition, it may be a procedure in which the UE_A10 may not automatically transmit a reconnect using a different non-DNN related PDU session request message and the non-S-NSSAI parameters conveyed in the message ( 1011) with a request to create a session PDU, until the session PDU type used in the message (1011) with a request to create a session PDU changes, or until the power of the terminal is turned on/off, or until the USIM (Universal Subscriber Identity Module) will be inserted/removed.

[00492] The UE_A10 may further execute a sixth procedure example other than the first, second, third, and fifth procedure examples as the fourth process example of the present modified example when the cause value of the 15th identification information means "session PDU does not exist" .

[00493] In particular, UE_A10 may send an initial session creation request message (initial request) PDU related to the DNN and the S-NSSAI parameters transmitted in the PDU session request message (1011).

[00494] In addition, UE_A10 may send a non-DNN related PDU creation request message (initial request) and the S-NSSAI parameters transmitted in the PDU creation request message (1011).

[00495] In addition, UE_A10 may send an initial session creation request message (initial request) PDU related to the DNN and the non-S-NSSAI parameters transmitted in the PDU session request message (1011).

[00496] In addition, UE_A10 may send a non-DNN related PDU creation request message (initial request) and non-S-NSSAI parameters transmitted in the PDU creation request message (1011).

[00497] The UE_A10 may further perform a seventh procedure example other than the first, second, third, fifth, and sixth procedure examples as the fourth process example of this modified example when the cause value of the 15th identification information means "user authentication or authentication failed" and/or "only session type IPv4 PDU allowed" and/or "only session type IPv6 PDU allowed" and/or "session PDU does not exist".

[00498] In particular, UE_A10 may also ignore the received backoff timer SM.

[00499] UE_A10 may further transmit another PDU session creation request message based on the retries information of the 11th identity information. In particular, when the connection in the equivalent PLMN is allowed in the retry information, the UE_A10 may send another DNN-related PDU session request message and the S-NSSAI parameters transmitted in the PDU session request message (1011) in equivalent PLMN.

[00500] In addition, when the connection in the equivalent PLMN is allowed in the retry information, the UE_A10 may send another non-DNN PDU session request message and the S-NSSAI parameters transmitted in the request message (1011). to create a PDU session in the equivalent PLMN.

[00501] In addition, when the connection in the equivalent PLMN is allowed in the retry information, the UE_A10 may send another DNN-related PDU session request message and the non-S-NSSAI parameters sent in the request message (1011). to create a PDU session in the equivalent PLMN.

[00502] In addition, when the connection in the equivalent PLMN is allowed in the retry information, the UE_A10 may send another non-DNN related PDU session request message and the non-S-NSSAI parameters sent in the (1011) message with a request to create a PDU session in the equivalent PLMN. As described above, the UE_A10 may also perform the process based on the receipt of the PDU session creation rejection message.

[00503] In other words, a process based on receiving a PDU session creation rejection message may be an example of the process described below. In addition, the exemplary process may be a process executed when the session creation rejection PDU message includes a timer value.

[00504] When the 5GSM cause value included in the PDU session creation reject message is a cause value different from another congestion control-related cause value, the UE_A10 may start a backoff timer for the combination of PLMN, DNN, and S-NSSAI using the received timer value, based on the received 5GSM cause value.

[00505] In this case, DNN and S-NSSAI may be reported by UE_A10. In particular, as described above, UE_A10 may also include the DNN and S-NSSAI in the session creation request PDU message. Further, the PDU session creation rejection message in the present process may be a response message to the PDU session creation request message.

[00506] The cause value related to congestion control may further be a cause value indicating insufficient resources and/or insufficient resources for a particular slice and/or insufficient resources for a particular slice and DNN.

[00507] In other words, for the above example process, when the 5GSM cause value included in the PDU session creation reject message is different from the cause value included in the following group of cause values, UE_A10 may start a backoff timer for the combination of PLMN, DNN, and S-NSSAI using the received timer value.

[00508] In this case, the group of cause values may be the aforementioned cause related to congestion control and/or "user authentication or authorization failed" and/or "out of LADN service area" and/or "only PDU session type allowed IPv4" and/or "only session type IPv6 PDU allowed" and/or "session PDU does not exist".

[00509] Specifically, when the 5GSM Cause value included in the PDU session creation reject message indicates that the request was denied without indication, the UE_A10 may start a backoff timer for the combination of PLMN, DNN, and S-NSSAI using the received timer value.

[00510] The process performed by UE_A10 during the backoff timer described above may further be the process already described in this section.

[00511] [2. Modified example]

[00512] A program executable in devices according to the present invention may be a program that controls a central processing unit (CPU) capable of controlling a computer to implement the functions of an embodiment according to the present invention. Programs or information processed by programs is temporarily stored on a volatile storage device such as random access memory (RAM), a non-volatile storage device such as a flash ROM or hard disk drive (HDD), or other data storage device.

[00513] In addition, a program for implementing such functions according to an embodiment of the present invention may be recorded on a computer-readable storage medium. This can be done by loading the program recorded on the storage medium into a computer system and executing the program. The term "computer system" as used herein refers to a computer system embedded in devices and including an operating system and hardware components such as peripherals. In addition, a "machine-readable storage medium" may be any of a semiconductor storage medium, an optical storage medium, a magnetic storage medium, a storage medium in which a program is dynamically stored for a short time, or any other computer-readable storage medium.

[00514] In addition, various functional blocks or various device features used in the above-described embodiments may be set or implemented by an electrical circuit, such as an integrated circuit or a plurality of integrated circuits. Circuitry capable of performing the functions described herein may include general purpose processors, digital signal processors (DSPs), application specific integrated circuits (ASICs), field programmable gate arrays (FPGAs), or other programmable logic devices, circuits on discrete components or transistorized logic circuits, discrete hardware components, or any combination of the above. A general purpose processor may be a microprocessor, or may be any conventional processor, controller, microcontroller, or state machine. The above circuit may include a digital circuit or may include an analog circuit. In addition, if due to advances in semiconductor technology, a new circuit integration technology emerges to replace the technologies used in current integrated circuits, a new integrated circuit based on the new circuit integration technology may also be used in one or more aspects of the present invention.

[00515] The present invention is not limited to the embodiments described above. In the embodiments, the devices are described by way of example, but the invention according to the present patent application is not limited to these devices, and is applicable to a terminal device or communication device, in particular to a fixed type or fixed type electronic device installed indoors or outdoors, for example audio-video device, kitchen device, washer or washing machine, air-conditioning device, office equipment, vending machine and other home appliances.

[00516] Embodiments of the present invention have been described in detail with reference to the accompanying drawings, but the specific configuration is not limited to the present embodiments and includes structural modifications and the like without going beyond the scope of the present invention. In addition, various modifications may be made to the present invention within the scope of the claims, and embodiments obtained by suitably combining the techniques described in various embodiments may also be included within the technical scope of the present invention. In addition, the configuration in which the constituent elements described in the respective embodiments and having mutually the same effects are interchangeable can also be included within the technical scope of the present invention.

Claims (25)

1. A method for performing user equipment (UE) control of a control signal, comprising the steps of: transmitting (S1100) the request information included in the first protocol data unit (PDU)-based initial session creation request message to the network node to create the first session PDU with the data network name (DNN) and the common network segment selection assistance information ( S-NSSAI); receiving (S1122) a PDU session creation rejection message; and transmitting (S1100) the request information included in the second PDU session creation request message to the network node to create the second PDU session, upon receiving the PDU session creation rejection message reason value indicating that the first PDU session does not exist, for the initial request for creating a second PDU session. 2. The method of claim 1, wherein the second session PDU is associated with a DNN and an S-NSSAI when the DNN and S-NSSAI are indicated in the second initial session creation request message PDU. 3. The method of claim 1, wherein the second session PDU is associated with the S-NSSAI and not with the DNN when the DNN is not indicated in the second create initial session PDU request message. 4. The method of claim 1, wherein the second session PDU is associated with a DNN and not with an S-NSSAI when the S-NSSAI is not indicated in the second initial session creation request message PDU. 5. The method of claim 1, wherein the second session PDU is associated with neither the DNN nor the S-NSSAI when neither the DNN nor the S-NSSAI is specified in the second Create Initial PDU Session Request message. 6. The method of claim 1, wherein the cause value is a cause value corresponding to 5G session management (5GSM). 7. User equipment (UE) for performing control signal management, comprising: one or non-volatile machine-readable media having computer executable programs; and at least one processor connected to said one or non-volatile machine-readable media and configured to execute computer executable programs for performing the method according to any one of paragraphs. 1-6. 8. A method for executing a control signal by a network node, comprising the steps of: receive (S1100) from the user equipment (UE) the request information included in the first message with the request to create an initial session based on the protocol data unit (PDU), to create the first session PDU with a data network name (DNN) and a single selection assistance information network segment (S-NSSAI); determining (S1101) whether a first session PDU exists based on at least one of the DNN and the S-NSSAI; and transmitting (S1122) to the UE a PDU session creation rejection message with a reason value indicating that the first session PDU does not exist when it is determined that the first session PDU does not exist. 9. The method of claim. 8, further comprising receiving (S1101) from the UE a second message with a request to create an initial session PDU to create a second session PDU; wherein the request information included in the second create initial session PDU request message is for the initial request to create the second session PDU. 10. The method of claim 9, wherein the second session PDU is associated with the DNN and S-NSSAI when the DNN and S-NSSAI are indicated in the second initial PDU session creation request message. 11. The method of claim 9, wherein the second session PDU is associated with the S-NSSAI and not with the DNN when the DNN is not indicated in the second create initial session PDU request message. 12. The method of claim 9, wherein the second session PDU is associated with the DNN and not with the S-NSSAI when the S-NSSAI is not indicated in the second create initial session PDU request message. 13. The method of claim 9, wherein the second session PDU is associated with neither the DNN nor the S-NSSAI when neither the DNN nor the S-NSSAI is specified in the second create initial session PDU request message. 14. The method of claim 8, wherein the cause value is a 5G Session Management (5GSM) cause value. 15. A network node for performing control of a control signal, comprising: one or non-volatile machine-readable media having computer executable programs; and at least one processor connected to said one or non-volatile machine-readable media and configured to execute computer executable programs for performing the method according to any one of paragraphs. 8-14.

Images