User equipment (UE)

Abstract

The UE transmits a registration request message including a first S-NSSAI and UE capability information indicating that an energy efficiency function is supported, receives a registration accept message including the first S-NSSAI, a reason value indicating that the first S-NSSAI has reached the upper-limit value of an energy consumption amount per network slice, and a second S-NSSAI, stores the first S-NSSAI and / or the second S-NSSAI and / or the fact that the first S-NSSAI has reached the upper-limit value of an energy consumption amount per network slice in association with each other, and transmits a PDU session establishment request message together with the second S-NSSAI.

Description

UE (User Equipment)

[0001] This embodiment relates to a UE (User Equipment). This application claims priority to Japanese Patent Application No. 2023-188296, filed on November 2, 2023, the contents of which are incorporated herein by reference.

[0002] The 3GPP (3rd Generation Partnership Project) is studying system architecture for a fifth-generation (5G) mobile communication system (also referred to as the 5G System or 5GS) (see Non-Patent Documents 1 to 3). 3GPP is currently discussing the standardization of Release 18 (also referred to as Rel-18) (see Non-Patent Documents 1 to 3).

[0003] 3GPP TS 23.501 V18.3.0 (2023-09); 3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; System architecture for the 5G System (5GS); Stage 2 (Release 18)3GPP TS 23.502 V18.3.0 (2023-09); 3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Procedures for the 5G System (5GS); Stage 2 (Release 18)3GPP TS 24.501 V18.4.0 (2023-09); 3rd Generation Partnership Project; Technical Specification Group Core Network and Terminals; Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3; (Release 18)3GPP TR 23.700-66 V0.1.0 (2023-10); 3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Study on Energy Efficiency and Energy Saving (Release 19)

[0004] Furthermore, 3GPP is currently discussing energy efficiency and energy saving as a technical item for Release 19 (also known as Rel-19) (see Non-Patent Document 4). Non-Patent Document 4 lists the key issue of network energy-related information exposure, but no specific solution has yet been discussed.

[0005] One aspect of this embodiment has been made in consideration of the above circumstances, and aims to provide a method for efficiently disclosing information related to network energy, particularly clarifying UE behavior and NW (network) behavior.

[0006] A UE of one embodiment of this embodiment is a UE (User Equipment) having a transceiver unit, a control unit, and a memory unit, wherein the transceiver unit transmits a registration request message including a first S-NSSAI and UE capability information indicating that the UE supports energy efficiency functions, receives a registration accept message including the first S-NSSAI, a reason value indicating that the first S-NSSAI has reached an upper limit of energy consumption per network slice, and a second S-NSSAI, the control unit associates and stores in the memory unit the first S-NSSAI, and / or the second S-NSSAI, and / or the fact that the first S-NSSAI has reached an upper limit of energy consumption per network slice, and the transceiver unit transmits a PDU session establishment request message together with the second S-NSSAI.

[0007] According to one aspect of this embodiment, a method for efficiently disclosing information related to network energy, in particular, clarification of UE behavior and NW behavior, is provided.

[0008] FIG. 1 is a diagram illustrating an overview of a mobile communication system (EPS / 5GS). FIG. 2 is a diagram illustrating a detailed configuration of a mobile communication system (EPS / 5GS). FIG. 3 is a diagram illustrating the device configuration of a UE. FIG. 4 is a diagram illustrating the configuration of an access network device (gNB) in 5GS. FIG. 5 is a diagram illustrating the configuration of a core network device (AMF / SMF) in 5GS. FIG. 6 is a diagram illustrating a registration procedure. FIG. 7 is a diagram illustrating a PDU session establishment procedure.

[0009] Hereinafter, a best mode for carrying out one aspect of this embodiment will be described with reference to the drawings. In this embodiment, as an example, an embodiment of a mobile communication system to which one aspect of this embodiment is applied will be described.

[0010] [1. System Overview] First, FIG. 1 is a diagram for explaining an overview of a mobile communication system 1 used in each embodiment, and FIG. 2 is a diagram for explaining a detailed configuration of the mobile communication system 1.

[0011] FIG. 1 shows that the mobile communication system 1 is composed of UE_A10, access network _A80, core network _A90, PDN (Packet Data Network) _A5, access network _B120, core network _B190, and DN (Data Network) _A6.

[0012] In the following, these devices and functions may be referred to by abbreviating the symbols, such as UE, access network_A, core network_A, PDN, access network_B, core network_B, DN, etc.

[0013] Figure 2 also shows devices and functions such as UE_A10, E-UTRAN80, MME40, SGW35, PGW-U30, PGW-C32, PCRF60, HSS50, 5G AN120, AMF140, UPF130, SMF132, PCF160, UDM150, and N3IWF170, as well as interfaces that connect these devices and functions to each other.

[0014] In the following, these devices and functions may be referred to by abbreviated symbols such as UE, E-UTRAN, MME, SGW, PGW-U, PGW-C, PCRF, HSS, 5G AN, AMF, UPF, SMF, PCF, UDM, N3IWF, etc.

[0015] The 4G system EPS (Evolved Packet System) includes an access network _A and a core network _A, but may further include a UE and / or a PDN. The 5G system 5GS (5G System) includes a UE, an access network _B, and a core network _B, but may further include a DN.

[0016] A UE is a device that can connect to a network service via 3GPP access (also referred to as a 3GPP access network, or 3GPP AN) and / or non-3GPP access (also referred to as a non-3GPP access network, or non-3GPP AN). A UE may be a terminal device capable of wireless communication, such as a mobile phone or a smartphone, and may be a terminal device that can connect to both EPS and 5GS. A UE may include a UICC (Universal Integrated Circuit Card) or an eUICC (Embedded UICC). Note that a UE may be referred to as a user device or a terminal device.

[0017] Furthermore, access network_A corresponds to an E-UTRAN (Evolved Universal Terrestrial Radio Access Network) and / or a wireless LAN access network. One or more eNBs (evolved Node Bs) 45 are deployed in the E-UTRAN. Note that, hereinafter, the eNB 45 may be referred to by abbreviating the symbol eNB. If there are multiple eNBs, the eNBs are connected to each other, for example, via an X2 interface. Furthermore, one or more access points are deployed in the wireless LAN access network.

[0018] Furthermore, access network_B corresponds to a 5G access network (5G AN). The 5G AN is composed of an NG-RAN (NG Radio Access Network) and / or a non-3GPP access network. One or more gNBs (NR NodeBs) 122 are deployed in the NG-RAN. Note that, hereinafter, the symbol for gNB 122 may be abbreviated, such as gNB. The gNB is a node that provides the NR (New Radio) user plane and control plane to UEs, and is a node that connects to the 5GCN via an NG interface (including an N2 interface or an N3 interface). In other words, the gNB is a base station device newly designed for 5GS, and has different functions from the base station device (eNB) used in the 4G system EPS. Furthermore, when there are multiple gNBs, the gNBs are connected to each other, for example, via an Xn interface.

[0019] Furthermore, the non-3GPP access network may be an untrusted non-3GPP access network or a trusted non-3GPP access network. Here, the untrusted non-3GPP access network may be a non-3GPP access network that does not perform security management within the access network, such as a public wireless LAN. On the other hand, the trusted non-3GPP access network may be an access network specified by 3GPP, and may include a trusted non-3GPP access point (TNAP) and a trusted non-3GPP gateway function (TNGF).

[0020] In the following, E-UTRAN and NG-RAN may be referred to as 3GPP access. Also, wireless LAN access networks and non-3GPP AN may be referred to as non-3GPP access. Also, nodes located in access network_B may be collectively referred to as NG-RAN nodes.

[0021] Furthermore, in the following, access network _A, and / or access network _B, and / or devices included in access network _A, and / or devices included in access network _B may be referred to as access networks or access network devices.

[0022] The core network_A corresponds to an EPC (Evolved Packet Core), which includes, for example, an MME (Mobility Management Entity), an SGW (Serving Gateway), a PGW (Packet Data Network Gateway)-U, a PGW-C, a PCRF (Policy and Charging Rules Function), and an HSS (Home Subscriber Server).

[0023] Furthermore, the core network_B corresponds to a 5G Core Network (5GCN). In the 5GCN, for example, an Access and Mobility Management Function (AMF), a User Plane Function (UPF), a Session Management Function (SMF), a Policy Control Function (PCF), a Unified Data Management (UDM), etc. are arranged. Here, the 5GCN may be expressed as a 5GC.

[0024] In addition, in the following, core network _A and / or core network _B, devices included in core network _A, and / or devices included in core network _B may be referred to as core networks, core network devices, or devices within the core network.

[0025] The core network (core network _A and / or core network _B) may be an IP mobile communication network operated by a mobile network operator (MNO) that connects the access network (access network _A and / or access network _B) to the PDN and / or DN, or it may be a core network for a mobile network operator that operates and manages the mobile communication system 1, or it may be a core network for a virtual mobile communication operator or virtual mobile communication service provider such as an MVNO (Mobile Virtual Network Operator) or MVNE (Mobile Virtual Network Enabler).

[0026] Also, while FIG. 1 illustrates a case where the PDN and the DN are the same, they may be different. The PDN may be a DN (Data Network) that provides communication services to the UE. The DN may be configured as a packet data service network, or may be configured for each service. Furthermore, the PDN may include a connected communication terminal. Therefore, connecting to the PDN may mean connecting to a communication terminal or a server device located in the PDN. Furthermore, transmitting and receiving user data to and from the PDN may mean transmitting and receiving user data to and from a communication terminal or a server device located in the PDN. The PDN may be expressed as the DN, and the DN may be expressed as the PDN.

[0027] In addition, hereinafter, at least a portion of the access network _A, the core network _A, the PDN, the access network _B, the core network _B, and the DN, and / or one or more devices included therein may be referred to as a network or a network device. In other words, when a network and / or a network device sends or receives a message and / or performs a procedure, it means that at least a portion of the access network _A, the core network _A, the PDN, the access network _B, the core network _B, and the DN, and / or one or more devices included therein send or receive a message and / or perform a procedure.

[0028] The UE can also be connected to an access network. The UE can also be connected to a core network via the access network. The UE can also be connected to a PDN or DN via the access network and the core network. That is, the UE can transmit and receive (communicate) user data with the PDN or DN. When transmitting and receiving user data, not only IP (Internet Protocol) communication but also non-IP communication may be used.

[0029] Here, IP communication refers to data communication using IP, and data is transmitted and received using IP packets. An IP packet is composed of an IP header and a payload portion. The payload portion may include data transmitted and received by devices and functions included in EPS or devices and functions included in 5GS. Non-IP communication refers to data communication that does not use IP, and data is transmitted and received in a format different from the IP packet structure. For example, non-IP communication may be data communication achieved by transmitting and receiving application data without an IP header, or may be user data transmitted and received by a UE with a different header such as a MAC header or an Ethernet (registered trademark) frame header.

[0030] In addition, devices not shown in Figure 2 may be configured in access network _A, core network _A, access network _B, core network _B, PDN_A, and DN_A.

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

[0032] Furthermore, the term "network" refers to at least a portion of the access network _B, core network _B, and DN. One or more devices included in at least a portion of the access network _B, core network _B, and DN may also be referred to as a network or a network device. In other words, when a network transmits, receives, and / or processes messages, it may mean that devices within the network (network devices and / or control devices) transmit, receive, and / or process messages. Conversely, when a device within the network transmits, receives, receives, and / or processes messages, it may mean that the network transmits, receives, receives, and / or processes messages.

[0033] [2. Configuration of Each Device] Next, the configuration of each device (UE, and / or access network device, and / or core network device) used in each embodiment will be described with reference to the drawings. Each device may be configured as physical hardware, as logical (virtual) hardware configured on general-purpose hardware, or as software. Furthermore, at least a part (including all) of the functions of each device may be configured as physical hardware, logical hardware, or software.

[0034] Note that each memory unit (memory unit_A340, memory unit_B540, memory unit_B740) in each device / function mentioned below is configured with, for example, a semiconductor memory, a solid state drive (SSD), a hard disk drive (HDD), etc. Each memory unit can store not only information originally set at the time of shipment, but also various information transmitted and received between the device / function other than the device / function itself (e.g., UE, and / or access network device, and / or core network device, and / or PDN, and / or DN). Each memory unit can also store identification information, control information, flags, parameters, etc. included in control messages transmitted and received in various communication procedures described below. Each memory unit may also store this information for each UE. Furthermore, when interworking between 5GS and EPS is performed, each memory unit can store control messages and user data transmitted and received between the device / function included in 5GS and / or EPS. In this case, not only those transmitted and received via the N26 interface but also those transmitted and received without via the N26 interface can be stored.

[0035] [2.1. Device configuration of UE] First, an example of the device configuration of UE (User Equipment) will be explained using Figure 3. The UE is composed of a control unit _A300, an antenna 310, a transceiver unit _A320, and a memory unit _A340. The control unit _A300, the transceiver unit _A320, and the memory unit _A340 are connected via a bus. The transceiver unit _A320 is connected to the antenna 310.

[0036] The control unit _A300 is a functional unit that controls the operation and functions of the entire UE. The control unit _A300 realizes various processing in the UE by reading and executing various programs stored in the memory unit _A340 as needed.

[0037] The transceiver unit _A320 is a functional unit for wireless communication with a base station device (eNB or gNB) in the access network via an antenna. That is, the UE can use the transceiver unit _A320 to transmit and receive user data and / or control information between an access network device, and / or a core network device, and / or a PDN, and / or a DN.

[0038] Explaining in detail with reference to Figure 2, the UE can communicate with a base station device (eNB) in the E-UTRAN via the LTE-Uu interface by using the transceiver unit _A320. The UE can also communicate with a base station device (gNB) in the 5G AN by using the transceiver unit _A320. The UE can also transmit and receive AMF and NAS (Non-Access-Stratum) messages via the N1 interface by using the transceiver unit _A320. However, since the N1 interface is logical, in reality, communication between the UE and the AMF is performed via the 5G AN.

[0039] The memory unit _A340 is a functional unit for storing programs, user data, control information, etc. necessary for each operation of the UE. The memory unit _340 may also have the function of storing control information transmitted and received between an access network device, a core network device, and a DN.

[0040] [2.2. Device configuration of gNB] Next, an example of the device configuration of a gNB will be described using Figure 4. The gNB is composed of a control unit _B500, an antenna 510, a network connection unit _B520, a transceiver unit _B530, and a memory unit _B540. The control unit _B500, the network connection unit _B520, the transceiver unit _B530, and the memory unit _B540 are connected via a bus. The transceiver unit _B530 is connected to the antenna 510.

[0041] The control unit _B500 is a functional unit that controls the operation and functions of the entire gNB. The control unit _B500 realizes various processes in the gNB by reading and executing various programs stored in the memory unit _B540 as necessary.

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

[0043] The transceiver unit _B530 is a functional unit for wireless communication with the UE via the antenna 510. That is, the gNB can transmit and receive user data and / or control information to and from the UE using the transceiver unit _B530.

[0044] 2, a gNB in ​​a 5G AN can communicate with an AMF via an N2 interface by using a network connection unit _B 520, and can communicate with a UPF via an N3 interface, and can communicate with a UE by using a transceiver unit _B 530.

[0045] The memory unit _B540 is a functional unit for storing programs, user data, control information, etc. necessary for each operation of the gNB. The memory unit _540 may also have the function of storing control information transmitted and received between the UE, other access network devices (base station devices), core network devices, and DNs.

[0046] [2.3. AMF Device Configuration] Next, an example of the AMF device configuration will be explained using Figure 5. The AMF is composed of a control unit _B700, a network connection unit _B720, and a memory unit _B740. The control unit _B700, the network connection unit _B720, and the memory unit _B740 are connected via a bus. The AMF may be a node that handles the control plane.

[0047] The control unit _B700 is a functional unit that controls the operation and functions of the entire AMF. The control unit _B700 realizes various processing in the AMF by reading and executing various programs stored in the memory unit _B740 as needed.

[0048] The network connection unit _B720 is a functional unit for the AMF to connect to a base station device (gNB), and / or SMF, and / or PCF, and / or UDM, and / or SCEF, and / or NSACF in a 5G AN. In other words, the AMF can use the network connection unit _B720 to send and receive user data and / or control information between a base station device (gNB), and / or SMF, and / or PCF, and / or UDM, and / or SCEF in a 5G AN.

[0049] Explaining in detail with reference to FIG. 2, the AMF in the 5GCN can communicate with a gNB via the N2 interface by using the network connection unit _A620, can communicate with a UDM via the N8 interface, can communicate with an SMF via the N11 interface, and can communicate with a PCF via the N15 interface. The AMF can also send and receive NAS messages with a UE via the N1 interface by using the network connection unit _A620. However, since the N1 interface is logical, communication between the UE and the AMF is actually performed via a 5G AN. Furthermore, if the AMF supports the N26 interface, it can communicate with an MME via the N26 interface by using the network connection unit _A620.

[0050] The memory unit _B740 is a functional unit for storing programs, user data, control information, etc. required for each operation of the AMF. The memory unit _740 may also have the function of storing control information transmitted and received between the UE, access network devices, other core network devices, and DN.

[0051] The AMF has functions such as exchanging control messages with the RAN using the N2 interface, exchanging NAS messages with the UE using the N1 interface, encrypting and protecting the integrity of NAS messages, registration management (RM) functions, connection management (CM) functions, reachability management functions, mobility management functions for UEs, etc., transferring SM (Session Management) messages between the UE and the SMF, access authentication (Access Authorization) functions, security anchor functionality (SEA), security context management (SCM), a function to support the N2 interface for the N3IWF (Non-3GPP Interworking Function), a function to support sending and receiving NAS signals with the UE via the N3IWF, and a function to authenticate UEs connected via the N3IWF.

[0052] In addition, registration management manages the RM state for each UE. The RM state may be synchronized between the UE and the AMF. The RM state includes an unregistered state (RM-DEREGISTERED state) and a registered state (RM-REGISTERED state). In the RM-DEREGISTERED state, the UE is not registered with the network, and therefore the UE context in the AMF does not have valid location information or routing information for the UE, and therefore the AMF cannot reach the UE. In the RM-REGISTERED state, the UE is registered with the network, and therefore the UE can receive services that require registration with the network. Note that the RM state may also be expressed as a 5GMM state. In this case, the RM-DEREGISTERED state may be expressed as a 5GMM-DEREGISTERED state, and the RM-REGISTERED state may be expressed as a 5GMM-REGISTERED state.

[0053] In other words, 5GMM-REGISTERED may be a state in which each device has established a 5GMM context or a PDU session context. When each device is 5GMM-REGISTERED, UE_A10 may start transmitting and receiving user data and control messages, or may respond to paging. Furthermore, when each device is 5GMM-REGISTERED, UE_A10 may perform registration procedures other than the registration procedure for initial registration, and / or service request procedures.

[0054] Furthermore, 5GMM-DEREGISTERED may be a state in which each device has not established a 5GMM context, a state in which UE_A10's location information is not known to the network, or a state in which UE_A10 is unreachable from the network. Note that when each device is 5GMM-DEREGISTERED, UE_A10 may initiate a registration procedure or may establish a 5GMM context by performing the registration procedure.

[0055] In addition, connection management manages the CM state for each UE. The CM state may be synchronized between the UE and the AMF. The CM state includes a non-connected state (CM-IDLE state) and a connected state (CM-CONNECTED state). In the CM-IDLE state, the UE is in the RM-REGISTERED state but does not have a NAS signaling connection established with the AMF via the N1 interface. In the CM-IDLE state, the UE does not have an N2 interface connection or an N3 interface connection. On the other hand, in the CM-CONNECTED state, the UE has a NAS signaling connection established with the AMF via the N1 interface. In the CM-CONNECTED state, the UE may have an N2 interface connection and / or an N3 interface connection.

[0056] Furthermore, in connection management, the CM state in 3GPP access and the CM state in non-3GPP access may be managed separately. In this case, the CM state in 3GPP access may include a non-connected state in 3GPP access (CM-IDLE state over 3GPP access) and a connected state in 3GPP access (CM-CONNECTED state over 3GPP access). Furthermore, the CM state in non-3GPP access may include a non-connected state in non-3GPP access (CM-IDLE state over non-3GPP access) and a connected state in non-3GPP access (CM-CONNECTED state over non-3GPP access). Note that the non-connected state may be expressed as an idle mode, and the connected state mode may be expressed as a connected mode.

[0057] The CM state may be expressed as a 5GMM mode. In this case, the unconnected state may be expressed as a 5GMM unconnected mode (5GMM-IDLE mode), and the connected state may be expressed as a 5GMM connected mode (5GMM-CONNECTED mode). Furthermore, the unconnected state in 3GPP access may be expressed as a 5GMM unconnected mode in 3GPP access (5GMM-IDLE mode over 3GPP access), and the connected state in 3GPP access may be expressed as a 5GMM connected mode in 3GPP access (5GMM-CONNECTED mode over 3GPP access). Furthermore, the unconnected state in non-3GPP access may be expressed as a 5GMM unconnected mode in non-3GPP access (5GMM-IDLE mode over non-3GPP access), and the connected state in non-3GPP access may be expressed as a 5GMM connected mode in non-3GPP access (5GMM-CONNECTED mode over non-3GPP access). In addition, the 5GMM non-connected mode may be expressed as idle mode, and the 5GMM connected mode may be expressed as connected mode.

[0058] In addition, one or more AMFs may be placed in the core network _B. In addition, the AMF may be a Network Function (NF) that manages one or more Network Slice Instances (NSIs). In addition, the AMF may be a Common Control Plane Network Function (CCNF) shared among multiple NSIs.

[0059] In addition, the N3IWF is a device and / or function located between the non-3GPP access and the 5GCN when the UE connects to the 5GS via the non-3GPP access.

[0060] [2.4. SMF Device Configuration] Next, an example of the SMF device configuration will be explained using Figure 5. The SMF is composed of a control unit _B700, a network connection unit _B720, and a memory unit _B740. The control unit _B700, the network connection unit _B720, and the memory unit _B740 are connected via a bus. The SMF may be a node that handles the control plane.

[0061] The control unit _B700 is a functional unit that controls the operation and functions of the entire SMF. The control unit _B700 realizes various processing in the SMF by reading and executing various programs stored in the memory unit _B740 as needed.

[0062] The network connection unit _B720 is a functional unit for the SMF to connect with the AMF, and / or UPF, and / or PCF, and / or UDM. In other words, the SMF can use the network connection unit _B720 to send and receive user data and / or control information between the AMF, and / or UPF, and / or PCF, and / or UDM, and / or NSACF.

[0063] Explaining in more detail with reference to Figure 2, the SMF in the 5GCN can communicate with the AMF via the N11 interface, with the UPF via the N4 interface, with the PCF via the N7 interface, and with the UDM via the N10 interface by using the network connection unit _A620.

[0064] The memory unit _B740 is a functional unit for storing programs, user data, control information, etc. required for each operation of the SMF.

[0065] The SMF has session management functions such as establishing, modifying, and releasing PDU sessions, IP address allocation for UEs and its management, UPF selection and control, UPF configuration for routing traffic to the appropriate destination, sending and receiving the SM portion of NAS messages, Downlink Data Notification, providing AN-specific (for each AN) SM information to be sent to the AN via the N2 interface via the AMF, determining the SSC mode (Session and Service Continuity mode) for the session, and roaming functions.

[0066] In addition, the memory unit _740 may have the function of storing control information transmitted and received between the UE, access network devices, other core network devices, and DN.

[0067] [2.5. UPF Device Configuration] Next, an example of the UPF device configuration will be explained using Figure 5. The UPF is composed of a control unit _B700, a network connection unit _B720, and a memory unit _B740. The control unit _B700, the network connection unit _B720, and the memory unit _B740 are connected via a bus. The UPF may be a node that handles the control plane.

[0068] The control unit _B700 is a functional unit that controls the operation and functions of the entire UPF. The control unit _B700 realizes various processing in the UPF by reading and executing various programs stored in the memory unit _B740 as needed.

[0069] The network connection unit _B720 is a functional unit for the UPF to connect to a base station device (gNB), and / or SMF, and / or DN within the 5G AN. In other words, the UPF can use the network connection unit _B720 to transmit and receive user data and / or control information between the base station device (gNB), and / or SMF, and / or DN within the 5G AN.

[0070] Explaining in more detail with reference to Figure 2, a UPF in a 5GCN can communicate with a gNB via the N3 interface, with an SMF via the N4 interface, with a DN via the N6 interface, and with other UPFs via the N9 interface by using the network connection unit _A620.

[0071] The memory unit _B740 is a functional unit for storing programs, user data, control information, etc. required for each operation of the UPF.

[0072] The UPF has functions such as an anchor point for intra-RAT mobility or inter-RAT mobility, an external PDU session point for interconnecting to DNs (i.e., a gateway between DNs and core network_B that forwards user data), packet routing and forwarding, an UL CL (Uplink Classifier) ​​function that supports routing of multiple traffic flows to one DN, a branching point function that supports multi-homed PDU sessions, a QoS (Quality of Service) processing function for the user plane, an uplink traffic verification function, downlink packet buffering, and a function to trigger downlink data notifications.

[0073] The UPF may also be a gateway for IP communication and / or non-IP communication. The UPF may also have a function for forwarding IP communication and a function for converting non-IP communication and IP communication. Furthermore, multiple gateways may be gateways that connect the core network_B to a single DN. The UPF may also have connectivity with other NFs and may be connected to each device via other NFs.

[0074] In addition, the memory unit _740 may have the function of storing control information transmitted and received between the UE, access network devices, other core network devices, and DN.

[0075] [2.6. Description of Other Devices and / or Functions and Control Information in the Present Embodiment] Next, other devices or functions, technical terms, control information and control messages transmitted, received, stored and managed by each device or function, etc. will be described.

[0076] Furthermore, these control information and control messages may be information that is pre-stored by the UE, and / or base station, and / or AMF, and / or SMF, and / or core network devices / functions other than AMF and SMF (e.g., NSSF, PCF, etc.), or some of these may be pre-stored and stored in conjunction with the transmission and reception of this control information.

[0077] In addition, the NSSF (Network Slice Selection Function) may be a network function (also referred to as NF) that has functions such as selecting an NSI (Network Slice Instance) to serve a UE, determining the mapping between an allowed NSSAI and a subscribed S-NSSAI, determining the mapping between a configured NSSAI and a subscribed S-NSSAI, and determining whether an S-NSSAI must be replaced and providing information indicating that the S-NSSAI is unavailable and a corresponding alternative S-NSSAI.

[0078] Furthermore, a PCF (Policy Control Function) may be an NF having a function of determining a unified policy for controlling network (NW) behavior, a function of providing policy rules to a CP function, and the like.

[0079] In addition, an NSACF (Network Slice Admission Control Function) may be an NF that has the function of monitoring and controlling the number of registered UEs per network slice (NS), and / or, in the case of interworking with an EPC, the function of monitoring and controlling the number of UEs having at least one PDU session and / or PDN connection per NS, and / or the function of monitoring and controlling the number of PDU sessions established per NS.

[0080] In addition, in this embodiment, some or all of the functions of disclosing information related to network energy (also referred to as Network energy related information exposure) may be performed by a base station device (including a gNB), and / or an AMF, and / or an SMF, and / or an UPF, and / or an NSSF, and / or a PCF, and / or an NSACF, or may be performed by an NF other than these. The NF may be an NF called, for example, an Energy Efficiency Function (EEF, also referred to as an energy efficiency function), an Energy Efficiency Management Function (EEMF, also referred to as an energy efficiency management function), an Energy Consumption Function (ECF, also referred to as an energy consumption function), an Energy Consumption Management Function (ECMF, also referred to as an energy consumption management function), an Energy Saving Function (ESF, also referred to as an energy saving function), an Energy Saving Management Function (ESMF, also referred to as an energy saving management function), an Energy Efficiency and Energy Saving Function (EEESF, also referred to as an energy efficiency and energy saving function), an Energy Efficiency and Energy Saving Management Function (EEESMF, also referred to as an energy efficiency and energy saving management function), etc.

[0081] Energy Consumption (EC) may be the amount of energy used to achieve a particular system, for example, expressed in joules or watt-hours.

[0082] Energy Efficiency (EE) may be the relationship between energy consumption and useful output.

[0083] Energy Saving (ES) may mean saving energy or reducing EC.

[0084] Furthermore, Energy Efficiency and Energy Saving (EEES) may be a concept that includes EC, and / or EE, and / or ES.

[0085] It should be noted that EC, EE, ES, and EEES may be interchangeable. In other words, for example, EC used in this specification may be interchangeable with EE, ES, and EEES.

[0086] In addition, the functions of Network energy related information exposure, and / or EE, and / or EC, and / or ES, and / or EEES, and / or CE, and / or RE may not be applied to V2X (Vehicle-to-Everything), and / or V2X services, and / or A2X (Aircraft-to-Everything), and / or A2X services, and / or emergency services, but these functions may be applied to other services.

[0087] The user plane (also referred to as UP) refers to user data transmitted and received between a UE and a network. The UP may be a communication path for transmitting and receiving user data and may be composed of multiple bearers. The UP may be transmitted and received using a PDN connection in the case of 4G, or a PDU session in the case of 5G. In the case of EPS, the UP may be transmitted and received using the LTE-Uu interface, and / or the S1-U interface, and / or the S5 interface, and / or the S8 interface, and / or the SGi interface. In the case of 5GS, the UP may be transmitted and received via the interface between the UE and the NG RAN, and / or the N3 interface, and / or the N9 interface, and / or the N6 interface. The UP may also be expressed as the U-Plane.

[0088] Furthermore, a control plane (also referred to as CP) refers to a control message transmitted and received to control communication of a UE, etc. The CP may be a communication path for transmitting and receiving control messages, and may be composed of multiple bearers. The CP may be transmitted and received using a NAS (Non-Access-Stratum) signaling connection between the UE and the MME. The CP may be transmitted and received using a NAS (Non-Access-Stratum) signaling connection between the UE and the AMF. In the case of EPS, the CP may be transmitted and received using the LTE-Uu interface and the S1-MME interface. In the case of 5GS, the CP may be transmitted and received using the interface between the UE and the NG RAN and the N2 interface. The CP may be expressed as a control plane or a C-Plane.

[0089] In addition, the SM procedure (also referred to as the procedure for SM) may include a PDU session establishment procedure initiated by the UE, a PDU session modification procedure initiated by the UE or SMF (or network), and a UE-requested PDU session release procedure initiated by the UE or SMF (or network).

[0090] In the PDU session establishment procedure, the UE sends a PDU session establishment request message to the SMF, and upon receiving the PDU session establishment request message, the SMF may send a PDU session establishment accept message or a PDU session establishment reject message to the UE. If the SMF accepts the PDU session establishment request from the UE, it may send a PDU session establishment accept message, or if it rejects the PDU session establishment request, it may send a PDU session establishment reject message.

[0091] In addition, in the UE-initiated PDU session modification procedure, the UE sends a PDU session modification request message to the SMF, and upon receiving the PDU session modification request message, the SMF may either execute the SMF-initiated PDU session modification procedure or send a PDU session modification reject message to the UE. Here, if the SMF accepts the PDU session modification request from the UE, it may execute the SMF-initiated PDU session modification procedure, or if it rejects the request, it may send a PDU session modification reject message.

[0092] In addition, in a PDU session modification procedure initiated by the SMF (or the network), the SMF sends a PDU session modification command message to the UE, and the UE, upon receiving the PDU session modification command message, may send a PDU session modification complete message or a PDU session modification command reject message to the SMF. Here, the UE may send a PDU session modification complete message if it accepts the PDU session modification instruction from the SMF, or may send a PDU session modification command reject message if it does not accept the instruction.

[0093] In addition, in the UE-initiated PDU session release procedure, the UE transmits a PDU session release request message to the SMF, and upon receiving the PDU session release request message, the SMF may either execute the SMF-initiated PDU session release procedure or send a PDU session release reject message to the UE. Here, if the SMF accepts the PDU session release request from the UE, it may execute the SMF-initiated PDU session release procedure, or if it rejects the request, it may send a PDU session release reject message.

[0094] In addition, in a PDU session release procedure initiated by the SMF (or the network), the SMF sends a PDU session release command message to the UE, and the UE that receives this may send a PDU session release complete message to the SMF.

[0095] In addition, the MM (Mobility Management) message may be a control message transmitted and received between the UE and the AMF in the MM procedure, or may be an NAS message (also referred to as an NAS MM message).

[0096] In addition, an SM (Session Management) message (also referred to as a NAS (Non-Access-Stratum) SM message) may be a control message transmitted and received between a UE and an SMF via an AMF during an SM procedure, or may be an NAS message (also referred to as a NAS SM message).

[0097] In addition, the MM procedure (also referred to as a procedure for MM) may include a registration procedure initiated by the UE, a de-registration procedure initiated by the UE or the AMF (or the network), a generic UE configuration update procedure initiated by the AMF (or the network), a service request procedure initiated by the UE, a paging procedure initiated by the AMF (or the network), and a notification procedure initiated by the AMF (or the network).

[0098] In this case, in the registration procedure, the UE sends a registration request message to the AMF, and the AMF that receives the message may send a registration accept message or a registration reject message to the UE. Here, the AMF may send a registration accept message if it accepts the registration request from the UE, or may send a registration reject message if it does not accept it.

[0099] In addition, in a deregistration procedure initiated by the UE, the UE may send a deregistration request message to the AMF, and the AMF may then send a deregistration accept message to the UE.

[0100] In addition, in a deregistration procedure initiated by the AMF (or network), the AMF may send a deregistration request message to the UE, and the UE that receives this may send a deregistration acceptance message to the AMF.

[0101] In addition, in the generic UE configuration update procedure, the AMF may send a configuration update command message to the UE, and the UE that receives this may send a configuration update complete message to the AMF.

[0102] In addition, in the service request procedure, the UE sends a service request message to the AMF, and the AMF that receives the service request may send a service accept message or a service reject message to the UE. Here, the AMF may send a service accept message when accepting the service request from the UE, or may send a service reject message when not accepting the service request.

[0103] In addition, in the paging procedure, the AMF sends a paging request (Request Paging) to the base station, and the base station that receives this sends a paging message to the UE, and the UE that receives this may send a service request message or a registration request message to the AMF.

[0104] In addition, in the notification procedure, the AMF sends a notification message to the UE, and the UE that receives this may send a notification response message to the AMF, or may send a service request message or a registration request message to the AMF.

[0105] In addition, the MM (Mobility Management) message may be a control message transmitted and received between the UE and the AMF in the MM procedure, or may be an NAS message (also referred to as an NAS MM message).

[0106] In addition, the 5GS (5G System) service may be a connection service provided using the core network_B190. Furthermore, the 5GS service may be a service different from the EPS service or may be a service similar to the EPS service.

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

[0108] Furthermore, a PDU (Protocol Data Unit) session can be defined as an association between a DN that provides a PDU connectivity service and a UE, but may also be connectivity established between a UE and an external gateway. In 5GS, a UE can transmit and receive user data to and from a DN by establishing a PDU session via an access network _B and a core network _B. Here, this external gateway may be a UPF, SCEF, or the like. The UE can transmit and receive user data to and from a device such as an application server located in the DN using the PDU session.

[0109] Each device (UE, and / or access network device, and / or core network device) may associate one or more pieces of identification information with a PDU session and manage them. These pieces of identification information may include one or more of the DNN, QoS rule, PDU session type, application identification information, NSI identification information, and access network identification information, or may further include other information. Furthermore, when multiple PDU sessions are established, the identification information associated with the PDU sessions may be the same or different.

[0110] Furthermore, the DNN (Data Network Name) may be identification information that identifies the core network and / or an external network such as a DN. Furthermore, the DNN can also be used as information for selecting a gateway such as PGW_A30 / UPF_A235 that connects the core network _B190. Furthermore, the DNN may be equivalent to an APN (Access Point Name).

[0111] Furthermore, the PDU (Protocol Data Unit / Packet Data Unit) session type indicates the type of PDU session, and can be IPv4, IPv6, Ethernet, or Unstructured. If IPv4 is specified, it indicates that data will be transmitted and received using IPv4. If IPv6 is specified, it indicates that data will be transmitted and received using IPv6. If Ethernet is specified, it indicates that Ethernet frames will be transmitted and received. Furthermore, Ethernet may indicate that communication using IP is not performed. If Unstructured is specified, it indicates that data will be transmitted and received to an application server or the like in the DN using Point-to-Point (P2P) tunneling technology. As the P2P tunneling technology, for example, UDP / IP encapsulation technology may be used. In addition to the above, the PDU session type may also include IP. IP can be specified if the UE is capable of using both IPv4 and IPv6.

[0112] A PLMN (Public Land Mobile Network) is a communication network that provides mobile radio communication services. A PLMN is a network managed by an operator, which is a communications carrier, and the operator can be identified by a PLMN ID. A PLMN that matches the MCC (Mobile Country Code) and MNC (Mobile Network Code) of a UE's IMSI (International Mobile Subscriber Identity) may be a Home PLMN (HPLMN). Furthermore, a UE may store an Equivalent HPLMN list in its USIM to identify one or more Equivalent HPLMNs (EPLMNs). A PLMN different from the HPLMN and / or EPLMN may be a Visited PLMN (VPLMN). A PLMN to which a UE has successfully registered may be a Registered PLMN (RPLMN). Note that a service provided by a PLMN may be referred to as a PLMN service, and a service provided by an SNPN may be referred to as an SNPN service.

[0113] A network slice (NS) is a logical network that provides specific network capabilities and network characteristics. UEs and / or networks can support network slices (NW slices; NS) in 5GS. A network slice may also be simply referred to as a slice.

[0114] A network slice instance (NSI) is composed of an instance (entity) of a network function (NF) and a set of required resources, forming a deployed network slice. Here, an NF is a processing function in a network, adopted or defined by 3GPP. An NSI is an entity of one or more NSs configured within a core network _B. An NSI may also be composed of virtual network functions (NFs) generated using a network slice template (NST). Here, an NST is associated with resource requirements for providing required communication services and capabilities, and is a logical representation of one or more NFs. In other words, an NSI may be a collection of multiple NFs within the core network _B 190. An NSI may also be a logical network configured to separate user data delivered by services, etc. One or more NFs may be configured within an NS. The NFs configured in an NS may or may not be devices shared with other NSs. A UE and / or a device in the network can be assigned to one or more NSs based on registration information such as an NSSAI, an S-NSSAI, an UE usage type, an NSI ID, or one or more APNs. The UE usage type is a parameter value included in the UE registration information and used to identify the NSI. The UE usage type may be stored in the HSS. The AMF may select an SMF and a UPF based on the UE usage type.

[0115] Furthermore, S-NSSAI (Single Network Slice Selection Assistance Information) is information for identifying an NS. The S-NSSAI may consist of only an SST (Slice / Service type), or may consist of an SST and an SD (Slice Differentiator). Here, the SST is information indicating the expected behavior of the NS in terms of functions and services. The SD may be information that interpolates the SST when selecting one NSI from multiple NSIs indicated by the SST. The S-NSSAI may be information specific to each PLMN, or may be standard information common among PLMNs. The network may store one or more S-NSSAIs in the registration information of the UE as default S-NSSAIs. Note that when the S-NSSAI is the default S-NSSAI, if the UE does not send a valid S-NSSAI to the network in a registration request message, the network may provide an NS related to the UE.

[0116] Also, NSSAI (Network Slice Selection Assistance Information) is a collection of S-NSSAIs. Each S-NSSAI included in the NSSAI is information that assists the access network or core network in selecting an NSI. The UE may store the NSSAI authorized by the network for each PLMN. Also, the NSSAI may be information used to select an AMF.

[0117] Furthermore, the configured NSSAI (also referred to as configured NSSAI) is an NSSAI that is provided and stored in the UE. The UE may store the configured NSSAI for each PLMN. The configured NSSAI may be information configured by the network (or PLMN). The S-NSSAI included in the configured NSSAI may be expressed as configured S-NSSAI. The configured S-NSSAI may be configured to include an S-NSSAI and a mapped S-NSSAI.

[0118] The requested NSSAI (also referred to as the Requested NSSAI) is an NSSAI provided from the UE to the network during the registration procedure. The requested NSSAI may be an allowed NSSAI or a configured NSSAI stored by the UE. Specifically, the requested NSSAI may be information indicating a network slice that the UE wishes to access. The S-NSSAI included in the requested NSSAI may be expressed as a requested S-NSSAI. For example, the requested NSSAI is transmitted in a Radio Resource Control (RRC) message including an NAS message or a Non-Access-Stratum (NAS) message, such as a registration request message or a PDU session establishment request message, transmitted from the UE to the network.

[0119] Furthermore, the allowed NSSAI (also referred to as the permitted NSSAI or Allowed NSSAI) is information indicating one or more network slices to which the UE is permitted. In other words, the allowed NSSAI is information that identifies the network slice to which the network permits the UE to connect. The UE and the network each store and manage the allowed NSSAI for each access (3GPP access or non-3GPP access) as UE information. The S-NSSAI included in the allowed NSSAI may be expressed as the allowed S-NSSAI. The allowed S-NSSAI may be configured to include the S-NSSAI and the mapped S-NSSAI.

[0120] Furthermore, the mapped S-NSSAI (also referred to as a mapped S-NSSAI) may be the S-NSSAI of the HPLMN mapped to the S-NSSAI of the registered PLMN in a roaming scenario (i.e., during roaming). The mapped S-NSSAI may basically be the S-NSSAI used when the UE is roaming, or may be an S-NSSAI that is not used when the UE is not roaming (also referred to as during non-roaming). The UE may store one or more mapped S-NSSAIs mapped to the configured NSSAI and the S-NSSAI included in the Allowed NSSAI for each access type. The UE may also store one or more mapped S-NSSAIs included in the rejected NSSAI or mapped S-NSSAIs corresponding to the S-NSSAI included in the rejected NSSAI.

[0121] Furthermore, a rejected NSSAI (also referred to as a Rejected NSSAI) is information indicating one or more network slices to which a UE is not permitted to connect. In other words, a rejected NSSAI is information identifying a network slice to which a network does not permit a UE to connect. A rejected NSSAI may be information including one or more combinations of an S-NSSAI and a rejection reason value (hereinafter also referred to as a reason value or rejection reason). Here, a rejection reason value is information indicating a reason why a network rejects a corresponding S-NSSAI. The UE and the network may store and manage the rejected NSSAI appropriately based on the rejection reason value associated with each S-NSSAI. Furthermore, the rejected NSSAI may be included in an NAS message transmitted from the network to a UE, such as a registration accept message, a configuration update command, or a registration reject message, or in an RRC message including an NAS message. An S-NSSAI included in a rejected NSSAI may be expressed as a rejected S-NSSAI. Here, the rejected NSSAI may mean any of the first to fifth rejected NSSAIs. Furthermore, the rejected S-NSSAI may mean a rejected S-NSSAI included in any of the first to fifth rejected NSSAIs, and these may be referred to as the first to fifth rejected S-NSSAIs. Furthermore, an S-NSSAI included in a rejected NSSAI may be expressed as a rejected S-NSSAI. The rejected S-NSSAI may be configured to include an S-NSSAI and a mapped S-NSSAI.

[0122] Here, the first rejected NSSAI may be a rejected NSSAI for the current PLMN or SNPN (also referred to as rejected NSSAI for the current PLMN or SNPN). In other words, the first rejected NSSAI may be an NSSAI that is unavailable in the current PLMN or SNPN. Furthermore, the first rejected NSSAI may be a set of one or more S-NSSAIs that are unavailable in the current PLMN or SNPN among the S-NSSAIs included in the requested NSSAI sent by the UE. Furthermore, the first rejected NSSAI may be a set of S-NSSAIs that are included in the requested NSSAI sent from the UE and are sent from the AMF together with a rejection reason value (also referred to as a reason value) indicating that the S-NSSAI is unavailable in the current PLMN or SNPN.

[0123] The second rejected NSSAI may be a rejected NSSAI for the current RA (also referred to as a rejected NSSAI for the current registration area). In other words, the second rejected NSSAI may be an NSSAI that cannot be used in the current RA. The second rejected NSSAI may be a set of one or more S-NSSAIs that the UE included in the requested NSSAI and that are not available in the current RA. The second rejected NSSAI may be a set of S-NSSAIs included in the requested NSSAI sent from the UE and sent from the AMF with a reason value that the S-NSSAI is not available in the current RA.

[0124] The third rejected NSSAI may also be a rejected NSSAI for the failed or revoked NSSAA. The third rejected NSSAI may also be a set of S-NSSAIs sent from the AMF with a reason value indicating that the S-NSSAI is unavailable due to a failed or revoked NSSAA. The third rejected NSSAI may also be a set of one or more S-NSSAIs that require an NSSAA and for which the NSSAA for that S-NSSAI has failed or been revoked.

[0125] Furthermore, the fourth rejected NSSAI may be a rejected NSSAI for the maximum number of UEs reached (also referred to as "Rejected NSSAI for the maximum number of UEs reached"). Furthermore, the fourth rejected NSSAI may be a set of S-NSSAIs that are included in the requested NSSAI transmitted from the UE and transmitted from the AMF together with a reason value indicating that the S-NSSAI is not available because the maximum number of UEs has been reached. Furthermore, the fourth rejected NSSAI may be information including one or more S-NSSAIs for which the maximum number of UEs per network slice has been reached.

[0126] Furthermore, the fifth rejected NSSAI may be a rejected NSSAI including an S-NSSAI related to the functionality of network energy related information exposure, and / or EE, and / or EC, and / or ES, and / or EEES, and / or CE, and / or RE. Furthermore, the fifth rejected NSSAI may be a set of S-NSSAIs included in the requested NSSAI sent from the UE and sent from the AMF with a reason value indicating that the S-NSSAI cannot be used in the current RA because the network energy related information exposure, and / or EE, and / or EC, and / or ES, and / or EEES, and / or CE, and / or RE have reached an upper limit value or a predetermined threshold. The fifth rejected NSSAI may also be a set of S-NSSAIs sent from the AMF along with a reason value that the S-NSSAI cannot be used in the current RA because the network energy related information exposure, and / or EE, and / or EC, and / or ES, and / or EEES, and / or CE, and / or RE has reached an upper limit value or a predetermined threshold.

[0127] Furthermore, the first to fifth rejected NSSAIs may be stored as separate rejected NSSAIs in the UE and / or NF (AMF and / or NSACF and / or NSSF and / or PCF and / or OAM and / or new NF), or may be stored as a common rejected NSSAI.

[0128] Furthermore, a pending NSSAI (also referred to as a Pending NSSAI) is an S-NSSAI that requires network slice specific authentication by the network, and is a collection of one or more S-NSSAIs that are not usable in the current PLMN because the network slice specific authentication has not been completed. The pending NSSAI may be a 5GS Rejected NSSAI due to NSSAA or a pending NSSAI. The pending NSSAI may be an NSSAI stored by the UE or the NW, or an NSSAI transmitted from the NW to the UE. Note that the pending NSSAI is not limited to the rejected NSSAI, and may be an NSSAI independent of the rejected NSSAI. When the pending NSSAI is an NSSAI transmitted from the NW to the UE, the pending NSSAI may be information including one or more combinations of an S-NSSAI and a rejection reason value. The rejection reason value at this time may be "NSSAA is pending for the S-NSSAI" and may be information indicating that the S-NSSAI associated with the rejection reason value is prohibited or pending use by the UE until the NSSAA for that S-NSSAI is completed.

[0129] Furthermore, the pending NSSAI is valid for the entire registered PLMN. In other words, the UE and / or NW may treat the S-NSSAI included in the third rejected NSSAI and the pending NSSAI as information independent of the access type. In other words, the pending NSSAI may be information valid for 3GPP access and non-3GPP access. The pending NSSAI may be an NSSAI different from the rejected NSSAI. The pending NSSAI may be the second or fourth rejected NSSAI.

[0130] Furthermore, the pending NSSAI is an NSSAI consisting of one or more S-NSSAIs that identify slices for which the UE has pending procedures. Specifically, while the UE stores the pending NSSAI, it does not initiate a registration request procedure for the S-NSSAI included in the pending NSSAI. In other words, the UE does not use the S-NSSAI included in the pending NSSAI during the registration procedure until the NSSAA for the S-NSSAI included in the pending NSSAI is completed. The pending NSSAI is identification information that includes one or more S-NSSAIs received from the core network in association with a rejection reason value indicating a pending NSSAA. The pending NSSAI is information that is independent of the access type. Specifically, when the UE stores the pending NSSAI, the UE does not attempt to send a registration request message including the S-NSSAI included in the pending NSSAI to both 3GPP access and non-3GPP access.

[0131] A tracking area (also referred to as TA) is a single or multiple ranges managed by the core network that can be represented by the location information of UE_A10. A TA may be composed of multiple cells. Furthermore, a TA may be an area in which control messages such as paging are broadcast, or an area in which UE_A10 can move without performing a handover procedure. Furthermore, a TA may be a routing area, a location area, or anything similar. A TA may be identified by a Tracking Area Identity (TAI), which is composed of a PLMN ID (PLMN Identifier) ​​and a Tracking Area Code (TAC). Here, the PLMN ID is an identifier used to identify a PLMN and may be composed of a Mobile Country Code (MCC) and a Mobile Network Code (MNC). The MCC is an identifier used to identify the country in which the UE is located, and the MNC is an identifier used to identify the Home Location Network (HPLMN) in the country in which the UE is located. The TAC is an identifier used to identify a TA in a PLMN.

[0132] A registration area (also referred to as a registration area, RA) is a collection of one or more TAs assigned to a UE by the AMF. Note that UE_A10 may be able to move without sending or receiving signals for TA update while moving within one or more TAs included in the RA. In other words, RA may be a group of information indicating areas in which UE_A10 can move without performing a TA update procedure. An RA may be identified by a TAI list consisting of one or more TAIs.

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

[0134] Network Slice-Specific Authentication and Authorization (NSSAA) is a function for realizing network slice-specific authentication and authorization. Network slice-specific authentication and authorization allows UE authentication and authorization to be performed outside the core network, such as by a third party. PLMNs and network devices with NSSAA functionality can perform NSSAA procedures for a certain S-NSSAI based on the UE's registration information. Furthermore, UEs with NSSAA functionality can manage and store rejected NSSAIs for pending NSSAA and / or rejected NSSAIs for failed NSSAA. In this document, NSSAA may be referred to as the network slice-specific authentication and authorization procedure or the authentication and authorization procedure.

[0135] An S-NSSAI requiring an NSSAA is an S-NSSAI requiring an NSSAA that is managed by a core network and / or a core network device. The core network and / or core network device may store an S-NSSAI requiring an NSSAA by associating the S-NSSAI with information indicating whether an NSSAA is required. The core network and / or core network device may further store an S-NSSAI requiring an NSSAA with information indicating whether an NSSAA has been completed, or information indicating that the NSSAA has been completed and is permitted or successful. The core network and / or core network device may manage an S-NSSAI requiring an NSSAA as information unrelated to the access network.

[0136] Also, a UE in single registration mode has only one active MM state. That is, a UE in single registration mode can only be active in either the RM state (5GMM state) in 5GC or the EMM state in EPC. Also, a UE in single registration mode is in 5GC NAS mode when connecting to 5GC, and is in EPC NAS mode when connecting to EPC. Also, since a UE in single registration mode can only be registered to either 5GC or EPC, when moving between EPC and 5GC, it is necessary to map EPS-GUTI (also referred to as 4G-GUTI) and 5G-GUTI.

[0137] In addition, a UE in dual registration mode may be able to independently register with 5GC and EPC. A UE in dual registration mode can independently maintain 5G-GUTI and EPS-GUTI (also referred to as 4G-GUTI).

[0138] Next, the identification information used in this specification will be explained.

[0139] Furthermore, the first identification information may be a requested NSSAI (also referred to as a requested NSSAI IE (Information Element)). Furthermore, the first identification information may include one or more S-NSSAIs indicating network slices requested by the UE. Furthermore, the first identification information may include an S-NSSAI included in the 11th identification information, the 15th identification information, the 31st identification information, or the 35th identification information.

[0140] The second identification information may be information indicating UE capability. The second identification information may be information included in 5GMM capability (also referred to as 5GMM capability IE). The second identification information may be information indicating whether the UE supports some or all of the following functions: network energy related information exposure, and / or energy efficiency (EE), and / or energy consumption (EC), and / or energy saving (ES), and / or energy efficiency and energy saving (EEES), and / or carbon emission (CE), and / or renewable energy (RE).

[0141] The third identification information may be information indicating a type of registration to be requested. The third identification information may be information included in a 5GS registration type (also referred to as a 5GS registration type IE). The third identification information may indicate network energy related information exposure, and / or EE, and / or EC, and / or ES, and / or EEES, and / or CE, and / or RE.

[0142] Furthermore, the fourth identification information may be information that includes at least one of the first to third identification information.

[0143] Note that transmitting and receiving at least one of the first to third identification information may be equivalent to transmitting and receiving the fourth identification information. In other words, transmitting and receiving at least one of the first to third identification information may mean transmitting and receiving the fourth identification information, and transmitting and receiving the fourth identification information may mean transmitting and receiving at least one of the first to third identification information.

[0144] Furthermore, the eleventh identification information may be an NSSAI. Furthermore, the eleventh identification information may be an allowed NSSAI (also referred to as an allowed NSSAI IE), and / or a configured NSSAI (also referred to as a configured NSSAI IE), and / or a rejected NSSAI (also referred to as a rejected NSSAI IE), and / or an extended rejected NSSAI (also referred to as an extended rejected NSSAI IE), and / or a pending NSSAI (also referred to as a pending NSSAI IE). Furthermore, the eleventh identification information may include one or more S-NSSAIs indicating network slices transmitted from the NW. Furthermore, the eleventh identification information may include an S-NSSAI included in the first identification information, or may include an S-NSSAI not included in the first identification information. Furthermore, the eleventh identification information may include an S-NSSAI not included in the fifteenth identification information.

[0145] Furthermore, the eleventh identification information may include an S-NSSAI indicating a network slice that supports some or all of the functions of network energy related information exposure, and / or EE, and / or EC, and / or ES, and / or EEES, and / or CE, and / or RE and is unavailable. The eleventh identification information may also include an S-NSSAI indicating a network slice that supports some or all of the functions of network energy related information exposure, and / or EE, and / or EC, and / or ES, and / or EEES, and / or CE, and / or RE and is unavailable because the values ​​of these functions exceed an upper limit or a predetermined threshold. The eleventh identification information may also include an S-NSSAI indicating a network slice that does not support some or all of the functions of network energy related information exposure, and / or EE, and / or EC, and / or ES, and / or EEES, and / or CE, and / or RE. The eleventh identification information may also be the fifth rejected NSSAI. The eleventh identification information may be an NSSAI that includes the fifth rejected S-NSSAI. The eleventh identification information may include the thirteenth identification information, the fourteenth identification information, and / or the fifteenth identification information.

[0146] Furthermore, the twelfth identification information may be information indicating network capability (NW capability). Furthermore, the twelfth identification information may be information included in 5G System (5GS) network feature support (also referred to as 5GS network feature support IE). Furthermore, the twelfth identification information may be information indicating whether the NW supports some or all of the functions of Network energy related information exposure, and / or EE, and / or EC, and / or ES, and / or EEES, and / or CE, and / or RE.

[0147] Furthermore, the 13th identification information may be a timer (also referred to as a backoff timer) value. Furthermore, the 13th identification information may be a timer value corresponding to the 11th identification information. Furthermore, the 13th identification information may be a timer value common to all S-NSSAIs included in the 11th identification information. Specifically, when there are two or more S-NSSAIs included in the 11th identification information, there may be only one 13th identification information, and one timer value indicated by the 13th identification information may be applied to all S-NSSAIs included in the 11th identification information. Furthermore, the 13th identification information may be a timer value corresponding to the S-NSSAIs included in the 11th identification information. Specifically, when there are two or more S-NSSAIs included in the 11th identification information, there may be as many 13th identification information as there are S-NSSAIs, and the corresponding timer value indicated by the 13th identification information may be applied to each S-NSSAI included in the 11th identification information.

[0148] The fourteenth identification information may also be a reason value indicating that the UE request is rejected. For example, the fourteenth identification information may indicate that the S-NSSAI has reached an upper limit or threshold of energy consumption per NS, or that the NS identified by the S-NSSAI has reached an upper limit or threshold of energy consumption. Here, this S-NSSAI may be the S-NSSAI included in the first identification information or the eleventh identification information. The fourteenth identification information may also indicate that the PDU session has reached an upper limit or threshold of energy consumption. The fourteenth identification information may also indicate that the PDU session in the S-NSSAI indicated by the first identification information or the eleventh identification information has reached an upper limit or threshold of energy consumption. The fourteenth identification information may also indicate that the UE has reached an upper limit or threshold of energy consumption. The 14th identification information may also indicate that an upper limit or threshold for network energy related information exposure, and / or EE, and / or EC, and / or ES, and / or EEES, and / or CE, and / or RE has been reached.

[0149] The fourteenth identification information may also indicate information indicating amounts related to network energy related information exposure, and / or EE, and / or EC, and / or ES, and / or EEES, and / or CE, and / or RE. For example, the fourteenth identification information may indicate information indicating current energy consumption and / or future energy consumption.

[0150] Furthermore, the fifteenth identification information may be one or more S-NSSAIs. Furthermore, the fifteenth identification information may be an S-NSSAI indicating a network slice supporting some or all of the functions of network energy related information exposure, and / or EE, and / or EC, and / or ES, and / or EEES, and / or CE, and / or RE. Furthermore, the fifteenth identification information may include one or more S-NSSAIs indicating a network slice transmitted from the NW. Furthermore, the fifteenth identification information may include an S-NSSAI included in the first identification information, or may include an S-NSSAI not included in the first identification information. Furthermore, the fifteenth identification information may include an S-NSSAI not included in the eleventh identification information. Furthermore, the fifteenth identification information may be referred to as an alternative S-NSSAI.

[0151] The sixteenth identification information may be information that includes at least one of the eleventh to fifteenth identification information.

[0152] Note that transmitting and receiving at least one of the 11th to 15th identification information may be equivalent to transmitting and receiving the 16th identification information. In other words, transmitting and receiving at least one of the 11th to 15th identification information may mean transmitting and receiving the 16th identification information, and transmitting and receiving the 16th identification information may mean transmitting and receiving at least one of the 11th to 15th identification information.

[0153] Furthermore, the 21st identification information may be an S-NSSAI. Furthermore, the 21st identification information may include one or more S-NSSAIs indicating a network slice for which the UE requests establishment of a PDU session. For example, the 21st identification information may include an S-NSSAI included in the 11th identification information, the 15th identification information, the 31st identification information, or the 35th identification information.

[0154] Furthermore, the 22nd identification information may be information indicating UE capability. Furthermore, the second identification information may be information included in 5GSM capability (also referred to as 5GSM capability IE). Furthermore, the second identification information may be information indicating whether the UE supports some or all of the functions of network energy related information exposure, and / or EE, and / or EC, and / or ES, and / or EEES, and / or CE, and / or RE.

[0155] Furthermore, the 23rd identification information may be S-NSSAI. Furthermore, the 23rd identification information may be the same as the 11th identification information or the 15th identification information.

[0156] Furthermore, the 24th identification information may be information that includes at least one of the 21st to 23rd identification information.

[0157] Note that transmitting and receiving at least one of the 21st to 23rd identification information may be equivalent to transmitting and receiving the 24th identification information. In other words, transmitting and receiving at least one of the 21st to 23rd identification information may mean transmitting and receiving the 24th identification information, and transmitting and receiving the 24th identification information may mean transmitting and receiving at least one of the 21st to 23rd identification information.

[0158] Furthermore, the 31st identification information may be an S-NSSAI. Furthermore, the 31st identification information may include one or more S-NSSAIs indicating network slices to which the NW allows or rejects the establishment of a PDU session. For example, the 31st identification information may include at least one of one or more S-NSSAIs included in the 21st identification information and / or the 23rd identification information. Furthermore, the 31st identification information may be an S-NSSAI that is not included in the 35th identification information.

[0159] Furthermore, the 31st identification information may be an S-NSSAI indicating a network slice that supports some or all of the functions of network energy related information exposure, and / or EE, and / or EC, and / or ES, and / or EEES, and / or CE, and / or RE, but is unavailable. The 31st identification information may be an S-NSSAI indicating a network slice that supports some or all of the functions of network energy related information exposure, and / or EE, and / or EC, and / or ES, and / or EEES, and / or CE, and / or RE, but is unavailable because the values ​​of these functions exceed their upper limits or predetermined thresholds. The 31st identification information may be an S-NSSAI indicating a network slice that does not support some or all of the functions of network energy related information exposure, and / or EE, and / or EC, and / or ES, and / or EEES, and / or CE, and / or RE. The 31st identification information may include the 33rd identification information, the 34th identification information, and / or the 35th identification information.

[0160] Furthermore, the 32nd identification information may be information indicating network capability (NW capability). Furthermore, the 32nd identification information may be information included in 5G Session Management (5GSM) network feature support (also referred to as 5GSM network feature support IE). Furthermore, the 32nd identification information may be information indicating whether the NW supports some or all of the functions of Network energy related information exposure, and / or EE, and / or EC, and / or ES, and / or EEES, and / or CE, and / or RE.

[0161] Furthermore, the 33rd identification information may be a timer (also referred to as a backoff timer) value. Furthermore, the 33rd identification information may be a timer value corresponding to the 31st identification information. Furthermore, the 33rd identification information may be a timer value common to all S-NSSAIs included in the 31st identification information. Specifically, when there are two or more S-NSSAIs included in the 31st identification information, only one 33rd identification information may exist, and one timer value indicated by the 33rd identification information may be applied to all S-NSSAIs included in the 31st identification information. Furthermore, the 33rd identification information may be a timer value corresponding to the S-NSSAIs included in the 31st identification information. Specifically, when there are two or more S-NSSAIs included in the 31st identification information, there may be as many 33rd identification information as there are S-NSSAIs, and the corresponding timer value indicated by the 33rd identification information may be applied to each S-NSSAI included in the 31st identification information.

[0162] Furthermore, the 34th identification information may be a reason value indicating that the UE request is rejected. For example, the 34th identification information may indicate that the S-NSSAI has reached an upper limit or threshold of energy consumption per NS, or that the NS identified by the S-NSSAI has reached an upper limit or threshold of energy consumption. Here, this S-NSSAI may be the S-NSSAI included in the 21st identification information or the 31st identification information. The 34th identification information may also indicate that a PDU session has reached an upper limit or threshold of energy consumption. The 34th identification information may also indicate that a PDU session in the S-NSSAI indicated by the 21st identification information or the 31st identification information has reached an upper limit or threshold of energy consumption. The 34th identification information may also indicate that the UE has reached an upper limit or threshold of energy consumption. The 34th identification information may also indicate that an upper limit or threshold for network energy related information exposure, and / or EE, and / or EC, and / or ES, and / or EEES, and / or CE, and / or RE has been reached.

[0163] The 34th identification information may also indicate information indicating amounts related to network energy related information exposure, and / or EE, and / or EC, and / or ES, and / or EEES, and / or CE, and / or RE. For example, the 34th identification information may indicate information indicating current energy consumption and / or future energy consumption.

[0164] Furthermore, the 35th identification information may be one or more S-NSSAIs. Furthermore, the 35th identification information may be an S-NSSAI indicating a network slice supporting some or all of the functions of network energy related information exposure, and / or EE, and / or EC, and / or ES, and / or EEES, and / or CE, and / or RE. Furthermore, the 35th identification information may include one or more S-NSSAIs indicating a network slice transmitted from the NW. Furthermore, the 35th identification information may include at least one of the one or more S-NSSAIs included in the 21st identification information and / or the 23rd identification information, or may include an S-NSSAI not included in the 21st identification information and / or the 23rd identification information. Furthermore, the 35th identification information may include an S-NSSAI not included in the 31st identification information. Furthermore, the 35th identification information may be referred to as an alternative S-NSSAI.

[0165] Furthermore, the 36th identification information may be information that includes at least one of the 31st to 35th identification information.

[0166] Note that transmitting and receiving at least one of the identification information Nos. 31 to 35 may be equivalent to transmitting and receiving the identification information No. 36. In other words, transmitting and receiving at least one of the identification information Nos. 31 to 35 may mean transmitting and receiving the identification information No. 36, and transmitting and receiving the identification information No. 36 may mean transmitting and receiving at least one of the identification information Nos. 31 to 35.

[0167] 3. First Embodiment First, a first embodiment will be described. In this embodiment, control information transmitted, received, stored, and / or managed by each device / function will be described.

[0168] In the first embodiment, as shown in FIG. 2, an example will be described in which the HSS and UDM, the PCF and PCRF, the SMF and PGW-C, and the UPF and PGW-U are configured as the same device / function (i.e., the same physical hardware, the same logical hardware, or the same software). However, the contents described in this embodiment are also applicable to cases in which these are configured as different devices / functions (i.e., different physical hardware, different logical hardware, or different software). For example, data may be transmitted and received directly between these, or may be transmitted and received via the N26 interface between the AMF and MME, or may be transmitted and received via the UE.

[0169] [3.1. Registration Procedure] Next, the registration procedure will be described with reference to FIG. 6. In this chapter, this registration procedure may be simply referred to as this procedure. The registration procedure is a procedure initiated by the UE to register with the access network _B and / or the core network _B and / or the DN. If the UE is not registered with a network, it can execute this procedure at any time, for example, when powered on. In other words, if the UE is in a deregistered state (5GMM-DEREGISTERED state), it can start this procedure at any time. Furthermore, each device (especially the UE and the AMF) can transition to a registered state (5GMM-REGISTED state) based on the completion of the registration procedure. Note that each registration state may be managed by each device for each access. Specifically, each device may independently manage the registration state (registered state or unregistered state) for 3GPP access and the registration state for non-3GPP access.

[0170] Furthermore, the registration procedure may be a procedure for updating the location registration information of the UE in the network, and / or for the UE to periodically notify the network of the status of the UE, and / or for updating certain parameters related to the UE in the network.

[0171] A UE may initiate a registration procedure when it moves to a TA outside its current registration area. In other words, a UE may initiate a registration procedure when it moves to a TA different from the TAs indicated in its TA list. Furthermore, a UE may initiate a registration procedure when a PDU session is disconnected or invalidated, requiring a context update for each device. Furthermore, a UE may initiate a registration procedure when a change occurs in the UE's capability information and / or preferences regarding PDU session establishment. Furthermore, a UE may initiate a registration procedure periodically. Furthermore, a UE may initiate a registration procedure based on the completion of a registration procedure, the completion of a PDU session establishment procedure, or information received from the network during each procedure. Furthermore, a UE may initiate this procedure after performing the procedures described in Chapter 3 one or more times. However, the UE may also perform the registration procedure at any timing.

[0172] This procedure may also be performed in a PLMN (HPLMN or VPLMN), or an equivalent PLMN, or an SNPN, or an equivalent SNPN, or an ON-SNPN, or an SO-SNPN.

[0173] The procedure for the UE to transition from a state where it is not registered in the network (unregistered state) to a state where it is registered (registered state) may be an initial registration procedure or a registration procedure for initial registration. Furthermore, the registration procedure executed when the UE is registered in the network (registered state) may be a registration procedure for mobility and periodic registration update or a mobility and periodic registration procedure.

[0174] Note that the UE may or may not store each NSSAI and / or S-NSSAI included in each NSSAI described in Chapter 2.6 at the time of initiating this procedure. Furthermore, the UE may initiate this procedure if it has stored each NSSAI and / or S-NSSAI described in Chapter 2.6 at the time of initiating this procedure. Furthermore, the UE may execute this procedure one or more times after storing each NSSAI and / or S-NSSAI included in each NSSAI acquired from the network by executing this procedure.

[0175] The details of the registration process described below are applicable to both.

[0176] First, the UE initiates the registration procedure by transmitting an NAS message including a registration request message to the AMF via 3GPP access or non-3GPP access (S600) (S602) (S604). Specifically, the UE transmits an RRC message including an NAS message including the registration request message to a base station device (also referred to as a 5G AN or gNB) (S600). Note that the registration request message is an NAS message transmitted and received on the N1 interface. Also, the RRC message may be a control message transmitted and received between the UE and the base station device. Also, the NAS message is processed in the NAS layer, and the RRC message is processed in the RRC layer. Note that the NAS layer is a layer higher than the RRC layer.

[0177] Here, the UE may transmit at least one of the first to fourth identification information in the registration request message, the NAS message, and / or the RRC message, where the first to fourth identification information may be as described in Chapter 2.6.

[0178] In addition, by transmitting these identification information, the UE may indicate that the UE supports each function, may indicate the UE's request, or may indicate the information indicated by each identification information to the network.

[0179] In addition, the UE may select and decide whether to send at least one of the first to fourth identification information to the network based on the UE's capability information, and / or UE policy, and / or UE status, and / or user registration information, and / or context held by the UE, and / or identification information sent and received in procedures performed prior to this procedure, etc.

[0180] For example, if the UE supports some or all of the functions of network energy related information exposure, and / or EE, and / or EC, and / or ES, and / or EEES, and / or CE, and / or RE, the UE may include second identification information indicating that it supports the functions of network energy related information exposure, and / or EE, and / or EC, and / or ES, and / or EEES, and / or CE, and / or RE in the registration request message and / or NAS message.

[0181] In addition, the UE may include third identification information indicating the network energy related information exposure, and / or EE, and / or EC, and / or ES, and / or EEES, and / or CE, and / or RE, for example, when the UE wishes to perform registration or registration procedures regarding network energy related information exposure, and / or EE, and / or EC, and / or ES, and / or EEES, and / or CE, and / or RE.

[0182] Also, when the UE has already received the identification information, it may recognize the meaning indicated by the identification information.

[0183] Furthermore, when the UE has already received the eleventh identification information, the UE may include the S-NSSAI included in the eleventh identification information in the first identification information. For example, when the eleventh identification information is an allowed NSSAI and / or a configured NSSAI including one or more S-NSSAIs, the UE may include one or more S-NSSAIs among them in the first identification information. Furthermore, when the eleventh identification information is a rejected NSSAI and / or an extended rejected NSSAI and / or a pending NSSAI including one or more S-NSSAIs, the UE may not include one or more S-NSSAIs among them in the first identification information.

[0184] Furthermore, when the UE has already received the 15th identification information, the UE may include the S-NSSAI indicated by the 15th identification information in the first identification information. Furthermore, when the UE has already received the 15th identification information, the UE may include the S-NSSAI indicated by the 15th identification information in the first identification information, regardless of whether the 11th identification information has been received.

[0185] Furthermore, when the UE has already received the 11th identification information and the 14th identification information, the UE does not need to include the S-NSSAI included in the 11th identification information in the first identification information.

[0186] In addition, when the UE has already received the 11th identification information and / or the 14th identification information and / or the 15th identification information, it may include the S-NSSAI included in the 15th identification information in the first identification information.

[0187] Furthermore, when the UE has already received the 11th identification information and / or the 13th identification information and / or the 14th identification information, if the timer using the timer value indicated by the 13th identification information has not expired, the UE does not need to include the S-NSSAI included in the 11th identification information in the first identification information.

[0188] In addition, when the UE has already received the 11th identification information and / or the 13th identification information and / or the 14th identification information, when the timer using the timer value indicated by the 13th identification information has expired, or when the timer has been stopped based on an instruction from the NW side (e.g., a control message such as a setting update command), the UE may include the S-NSSAI contained in the 11th identification information in the first identification information.

[0189] In addition, when the UE has already received the 31st identification information, the UE may include the S-NSSAI indicated by the 31st identification information in the first identification information.

[0190] Furthermore, when the UE has already received the 35th identification information, the UE may include the S-NSSAI indicated by the 35th identification information in the first identification information. Furthermore, when the UE has already received the 35th identification information, the UE may include the S-NSSAI indicated by the 35th identification information in the first identification information, regardless of whether the 31st identification information has been received.

[0191] Furthermore, when the UE has already received the 31st identification information and the 34th identification information, the UE does not need to include the S-NSSAI included in the 31st identification information in the first identification information.

[0192] In addition, when the UE has already received the 31st identification information and / or the 34th identification information and / or the 35th identification information, it may include the S-NSSAI included in the 35th identification information in the first identification information.

[0193] Furthermore, when the UE has already received the 31st identification information and / or the 33rd identification information and / or the 34th identification information, if the timer using the timer value indicated by the 33rd identification information has not expired, the UE does not need to include the S-NSSAI included in the 31st identification information in the first identification information.

[0194] In addition, when the UE has already received the 31st identification information and / or the 33rd identification information and / or the 34th identification information, when the timer using the timer value indicated by the 33rd identification information has expired, or when the timer has been stopped based on an instruction from the NW side (e.g., a control message such as a PDU session change command or a setting update command), the UE may include the S-NSSAI included in the 31st identification information in the first identification information.

[0195] Furthermore, when the UE has already received the eleventh identification information and / or the fourteenth identification information, the UE may determine whether to include the S-NSSAI included in the eleventh identification information in the first identification information based on the current energy consumption or future energy consumption indicated by the fourteenth identification information for the S-NSSAI included in the eleventh identification information. For example, when the current energy consumption or future energy consumption indicated by the fourteenth identification information exceeds a predetermined value, the UE may not include the S-NSSAI included in the eleventh identification information in the first identification information. Furthermore, when the current energy consumption or future energy consumption indicated by the fourteenth identification information does not exceed a predetermined value, the UE may include the S-NSSAI included in the eleventh identification information in the first identification information.

[0196] Furthermore, when the UE has already received the 31st identification information and / or the 34th identification information, the UE may determine whether to include the S-NSSAI included in the 31st identification information in the first identification information based on the current energy consumption or future energy consumption indicated by the 34th identification information for the S-NSSAI included in the 31st identification information. For example, when the current energy consumption or future energy consumption indicated by the 34th identification information exceeds a predetermined value, the UE may not include the S-NSSAI included in the 31st identification information in the first identification information. Furthermore, when the current energy consumption or future energy consumption indicated by the 34th identification information does not exceed a predetermined value, the UE may include the S-NSSAI included in the 31st identification information in the first identification information.

[0197] Furthermore, when multiple pieces of identification information are transmitted and received, two or more of these pieces of identification information may be configured as one or more pieces of identification information. Note that the information indicating support for each function and the information indicating a request for use of each function may be transmitted and received as the same identification information, or may be transmitted and received as different identification information.

[0198] Next, when the base station device receives an RRC message including a NAS message including a registration request message, the base station device selects an AMF to which to forward the received RRC message, and / or the registration request message, and / or the NAS message (S602), and forwards them to the selected AMF (S604). The base station device may select an AMF based on identification information included in the registration request message, the NAS message, and / or the RRC message. Specifically, when the base station device receives at least one of the first to fourth identification information, the base station device may select an AMF based on the received identification information. For example, the base station device may select an AMF included in the network slice identified by the first identification information, or may select an AMF having connectivity to the network slice identified by the first identification information. The base station device may also select an AMF having NW functions corresponding to the UE capability information indicated by the second identification information. The base station device may also select an AMF that supports NW functions corresponding to the 5GS registration type (also referred to as registration type) indicated by the third identification information. The AMF selection method is not limited to this, and the base station device may select an AMF based on other conditions.

[0199] Next, when the AMF receives a registration request message or the like from the base station device, the AMF can execute a first condition determination. The first condition determination is for determining whether the network accepts the UE's request. When the AMF determines that the first condition determination is true, the AMF may execute the procedures from S610 to S612. Also, when the AMF determines that the first condition determination is false, the AMF may execute the procedure of S610.

[0200] If the first condition determination is true, the control message transmitted and received at S610 may be a Registration accept message, and if the first condition determination is false, the control message transmitted and received at S610 may be a Registration accept message or a Registration reject message. The control message may be transmitted in a NAS message. Furthermore, the NAS message may be transmitted in an RRC message.

[0201] Furthermore, the first condition determination may be performed based on the reception of a registration request message, etc. received from a base station device, and / or each identification information contained in the registration request message, etc., and / or subscriber information, and / or network capability information, and / or operator policy, and / or network status, and / or user registration information, and / or context held by the AMF, etc.

[0202] For example, if the network does not permit or reject the UE's request, the first condition determination may be determined as true, and if the network does not permit or reject the UE's request, the first condition determination may be determined as false. Furthermore, if the network does not permit or reject part of the UE's request, the first condition determination may be determined as true. Furthermore, if the network does not permit or reject all of the UE's request, the first condition determination may be determined as false. Furthermore, if the network to which the UE is registered and / or a device within the network supports the function requested by the UE, the first condition determination may be determined as true. Furthermore, if the received identification information is permitted, the first condition determination may be determined as true, and if the received identification information is not permitted, the first condition determination may be determined as false.

[0203] In addition, the first condition determination may be performed by a network function (also referred to as NF) other than the AMF. When an NF other than the AMF performs the first condition determination, the AMF may provide the NF with information necessary to perform the first condition determination, specifically, at least a portion of the information received from the UE (S606). Then, when the NF determines whether the first condition determination is true or false based on the information received from the AMF, it may convey information including the result of the first condition determination (i.e., true or false) to the AMF. The AMF may determine identification information and / or a control message to be transmitted to the UE based on the result of the first condition determination received from the NF.

[0204] In addition, step S606 may be executed regardless of whether the first condition determination is performed by the AMF or by an NF other than the AMF.

[0205] The AMF may also use the UE ID, and / or the access type (corresponding to the access that sent the registration request message), and / or one or more S-NSSAIs included in the first identity information, and / or the Network energy related information, to check with the NSACF and / or NSSF and / or PCF and / or OAM and / or new NF whether an upper limit or threshold for Network energy related information exposure and / or EE and / or EC and / or ES and / or EEES and / or CE and / or RE has been reached, or whether an upper limit or threshold for Network energy related information exposure and / or EE and / or EC and / or ES and / or EEES and / or CE and / or RE per NS has been reached, or whether an upper limit or threshold for Network energy related information exposure and / or EE and / or EC and / or ES and / or EEES and / or CE and / or RE per UE has been reached. It may also transmit control information indicating an increase in exposure and / or EE and / or EC and / or ES and / or EEES and / or CE and / or RE, and / or control information indicating an increase in network energy related information exposure and / or EE and / or EC and / or ES and / or EEES and / or CE and / or RE per NS, and / or control information indicating an increase in network energy related information exposure and / or EE and / or EC and / or ES and / or EEES and / or CE and / or RE per UE.

[0206] Furthermore, when one or more S-NSSAIs included in the first identification information received from the UE correspond to V2X (Vehicle-to-Everything), and / or V2X service, and / or A2X (Aircraft-to-Everything), and / or A2X service, and / or emergency service, the AMF may not need to transmit these control information to the NSACF and / or NSSF and / or PCF and / or OAM and / or new NF.

[0207] In addition, when the 5GS registration type indicated in the third identification information received from the UE indicates emergency registration, the AMF may not need to send this control information to the NSACF and / or NSSF and / or PCF and / or OAM and / or new NF.

[0208] Furthermore, the NSACF and / or NSSF and / or PCF and / or OAM and / or new NF that receives these control information from the AMF may check or determine whether an upper limit or threshold of network energy related information exposure and / or EE and / or EC and / or ES and / or EEES and / or CE and / or RE has been reached, or whether an upper limit or threshold of network energy related information exposure and / or EE and / or EC and / or ES and / or EEES and / or CE and / or RE per NS has been reached, or whether an upper limit or threshold of network energy related information exposure and / or EE and / or EC and / or ES and / or EEES and / or CE and / or RE per UE has been reached. Note that this checking or determination may or may not be performed for each access type. In addition, the NSACF and / or NSSF and / or PCF and / or OAM and / or new NF may not need to check or determine whether these upper limits or thresholds have been reached when one or more S-NSSAIs included in the first identification information received from the AMF correspond to V2X (Vehicle-to-Everything), and / or V2X services, and / or A2X (Aircraft-to-Everything), and / or A2X services, and / or emergency services.

[0209] Furthermore, when the NSACF and / or NSSF and / or PCF and / or OAM and / or new NF confirms or determines that these upper limits or thresholds have been reached, it may send to the AMF the UE ID, and / or the access type (corresponding to the access that sent the registration request message), and / or one or more S-NSSAIs included in the first identification information, and / or control information indicating that the network energy related information exposure and / or EE and / or EC and / or ES and / or EEES and / or CE and / or RE have reached their upper limits or thresholds, and / or control information indicating that the network energy related information exposure and / or EE and / or EC and / or ES and / or EEES and / or CE and / or RE per NS have reached their upper limits or thresholds, and / or control information indicating that the network energy related information exposure and / or EE and / or EC and / or ES and / or EEES and / or CE and / or RE per UE have reached their upper limits or thresholds. Note that this control information may be transmitted by being included in the 14th identification information. Furthermore, the NSACF and / or NSSF and / or PCF and / or OAM and / or new NF may transmit the S-NSSAI that has reached these upper limit values ​​or thresholds to the AMF. This S-NSSAI may be transmitted by being included in the 11th identification information. Furthermore, the NSACF and / or NSSF and / or PCF and / or OAM and / or new NF may transmit an S-NSSAI (alternative S-NSSAI) that replaces the S-NSSAI that has reached these upper limit values ​​or thresholds to the AMF. This S-NSSAI may be transmitted by being included in the 15th identification information. Furthermore, the NSACF and / or NSSF and / or PCF and / or OAM and / or new NF may transmit the timer (back-off timer) value for the S-NSSAI that has reached these upper limit values ​​or thresholds to the AMF. This timer value may be transmitted in the 13th identification information.Also, when not making a judgment for each access type, the NSACF and / or NSSF and / or PCF and / or OAM and / or new NF may not send the access type (corresponding to the access that sent the registration request message).

[0210] Furthermore, when the NSACF and / or NSSF and / or PCF and / or OAM and / or new NF confirms or determines that these upper limits or thresholds have not been reached, it may send to the AMF the UE ID, and / or the access type (corresponding to the access that sent the registration request message), and / or one or more S-NSSAIs included in the first identification information, and / or control information indicating that the upper limits or thresholds have not been reached for the network energy related information exposure and / or EE and / or EC and / or ES and / or EEES and / or CE and / or RE, and / or control information indicating that the upper limits or thresholds have not been reached for the network energy related information exposure and / or EE and / or EC and / or ES and / or EEES and / or CE and / or RE per NS, and / or control information indicating that the upper limits or thresholds have not been reached for the network energy related information exposure and / or EE and / or EC and / or ES and / or EEES and / or CE and / or RE per UE. Also, when not making a judgment for each access type, the NSACF and / or NSSF and / or PCF and / or OAM and / or new NF may not send the access type (corresponding to the access that sent the registration request message).

[0211] Also, when making a judgment for each access type, the NSACF and / or NSSF and / or PCF and / or OAM and / or new NF may, for example, reach an upper limit or threshold for one access type (e.g., 3GPP access) but not reach the upper limit or threshold for another access type (e.g., non-3GPP access).

[0212] Note that these exchanges of control information between the AMF and the NSACF and / or NSSF and / or PCF and / or OAM and / or new NF may be performed by one or more procedures. For example, some of the exchanges may be performed between the AMF and the NSACF and / or NSSF and / or PCF and / or OAM and / or new NF, and the rest of the exchanges may be performed between the AMF and the NSACF and / or NSSF and / or PCF and / or OAM and / or new NF, thereby performing all of the exchanges.

[0213] Furthermore, the AMF may include at least one of the identification information items 11 to 16 in a control message and transmit the control message to the UE via the base station device. Here, the identification information items 11 to 16 may be as described in Chapter 2.6. By transmitting the identification information items and / or the control message, the AMF may indicate whether the network supports each function, whether the UE request has been accepted, or a combination of these. Furthermore, when multiple pieces of identification information are transmitted and received, two or more pieces of identification information may be configured as one or more pieces of identification information. Note that the information indicating support for each function and the information indicating permission to use each function may be transmitted and received as the same identification information, or may be transmitted and received as different identification information.

[0214] In addition, the AMF may send a control message including at least one of the 11th to 16th identification information when it receives at least one of the 1st to 4th identification information from the UE.

[0215] Furthermore, the AMF may determine whether to include at least one of the identification information items 11 to 16 in the control message based on each received identification information, and / or subscriber information, and / or network capability information, and / or operator policy, and / or network status, and / or user registration information, and / or context held by the AMF, and / or identification information sent and received in procedures performed prior to this procedure, etc.

[0216] The AMF may also indicate to the UE that the UE's request has been accepted by sending a registration acceptance message, or may indicate to the UE that the UE's request has been rejected by sending a registration rejection message.

[0217] In addition, if the NW supports some or all of the functions of Network energy related information exposure, and / or EE, and / or EC, and / or ES, and / or EEES, and / or CE, and / or RE, the AMF may include 12th identification information indicating that the NW supports the functions of Network energy related information exposure, and / or EE, and / or EC, and / or ES, and / or EEES, and / or CE, and / or RE in the control message and / or NAS message.

[0218] In addition, if the NW does not support some or all of the functions of network energy related information exposure, and / or EE, and / or EC, and / or ES, and / or EEES, and / or CE, and / or RE, the AMF may include 12th identification information indicating that the functions of network energy related information exposure, and / or EE, and / or EC, and / or ES, and / or EEES, and / or CE, and / or RE are not supported in the control message and / or NAS message. Furthermore, in this case, the AMF may not include 13th identification information, and / or 14th identification information, and / or 15th identification information in the control message and / or NAS message.

[0219] The AMF may also send the eleventh identification information and / or the twelfth identification information when it receives, from the NSACF and / or the NSSF and / or the PCF and / or the OAM and / or the new NF, control information indicating a UE ID, and / or an access type (corresponding to the access that sent the registration request message), and / or one or more S-NSSAIs included in the first identification information, and / or network energy related information exposure and / or EE and / or EC and / or ES and / or EEES and / or CE and / or RE that have not reached an upper limit or threshold, and / or control information indicating that network energy related information exposure per NS and / or EE and / or EC and / or ES and / or EEES and / or CE and / or RE that have not reached an upper limit or threshold, and / or control information indicating that network energy related information exposure per UE and / or EE and / or EC and / or ES and / or EEES and / or CE and / or RE that have not reached an upper limit or threshold.

[0220] The AMF also receives from the NSACF and / or NSSF and / or PCF and / or OAM and / or new NF the UE ID, and / or the access type (corresponding to the access that sent the registration request message), and / or one or more S-NSSAIs included in the first identification information, and / or control information indicating that Network energy related information exposure and / or EE and / or EC and / or ES and / or EEES and / or CE and / or RE have reached an upper limit or threshold, and / or control information indicating that Network energy related information exposure and / or EE and / or EC and / or ES and / or EEES and / or CE and / or RE have reached an upper limit or threshold, and / or Network energy related information per UE. When control information is received indicating that exposure and / or EE and / or EC and / or ES and / or EEES and / or CE and / or RE has reached an upper limit or threshold, 11th identification information and / or 12th identification information and / or 13th identification information and / or 14th identification information and / or 15th identification information may be transmitted.

[0221] Next, the UE receives a control message (a registration accept message or a registration reject message) and / or the transmitted identification information (at least one of the eleventh to sixteenth identification information) via the base station device (S610). If the control message is a registration accept message, the UE may recognize, by receiving the registration accept message, that the UE's request in the registration request message has been accepted and / or the contents of the various identification information included in the registration accept message. Also, if the control message is a registration reject message, the UE may recognize, by receiving the registration reject message, that the UE's request in the registration request message has been rejected and / or the contents of the various identification information included in the registration reject message.

[0222] Furthermore, when the UE receives at least one of the 11th to 16th identification information from the core network, the UE may store the information indicated by the received identification information, or may behave based on the information indicated by the received identification information.

[0223] For example, when the UE receives at least one of the eleventh to sixteenth identification information, the UE may recognize and store the content of the received identification information.

[0224] Furthermore, based on receiving the 14th identification information, the UE may recognize and store whether the network energy related information exposure and / or EE and / or EC and / or ES and / or EEES and / or CE and / or RE has reached an upper limit or threshold, and / or whether the network energy related information exposure and / or EE and / or EC and / or ES and / or EEES and / or CE and / or RE per NS has reached an upper limit or threshold, and / or whether the network energy related information exposure and / or EE and / or EC and / or ES and / or EEES and / or CE and / or RE per UE has reached an upper limit or threshold.

[0225] Furthermore, based on receiving the 11th identification information and the 14th identification information, the UE may recognize and store that the S-NSSAI indicated by the 11th identification information is unavailable based on the reason value indicated by the 14th identification information.

[0226] Furthermore, based on receiving the 11th identification information, the 14th identification information, and the 15th identification information, the UE may recognize that the S-NSSAI indicated by the 11th identification information is unavailable based on the reason value indicated by the 14th identification information, and may also recognize and store that the S-NSSAI indicated by the 15th identification information is available, and / or that registration is possible using that S-NSSAI, and / or that a registration procedure is possible using that S-NSSAI, and / or that a PDU session establishment procedure is possible using that S-NSSAI, and / or that a PDU session establishment is possible using that S-NSSAI.

[0227] Furthermore, based on receiving the 11th identification information, the 13th identification information, and the 14th identification information, the UE may recognize and store that the S-NSSAI indicated by the 11th identification information is unavailable based on the cause value indicated by the 14th identification information, and may start a timer using the timer value indicated by the 13th identification information. In this case, if the timer has not expired, the UE may recognize and store that the S-NSSAI included in the 11th identification information is unavailable, and / or that registration using that S-NSSAI is unavailable, and / or that a registration procedure using that S-NSSAI is unavailable, and / or that a PDU session establishment procedure using that S-NSSAI is unavailable, and / or that a PDU session establishment using that S-NSSAI is unavailable. Furthermore, when the timer expires or when the timer is stopped based on an instruction from the network side (for example, a control message such as a configuration update command sent from the AMF to the UE), the UE may recognize and memorize that the S-NSSAI included in the 11th identification information is available, and / or that registration is possible using that S-NSSAI, and / or that a registration procedure is possible using that S-NSSAI, and / or that a PDU session establishment procedure is possible using that S-NSSAI, and / or that a PDU session is possible to establish using that S-NSSAI.

[0228] Furthermore, if the control message is a registration accept message, the UE may further transmit a registration complete message to the AMF via the base station device as a response message to the registration accept message (S612). Here, the registration complete message is an NAS message transmitted and received on the N1 interface, but may be transmitted and received between the UE and the base station device by being included in an RRC message.

[0229] Next, the AMF receives a registration completion message via the base station device (S612).

[0230] Each device completes this procedure based on the transmission and reception of a registration acceptance message and / or a registration completion message. Each device may also recognize that this procedure has been successfully completed based on the transmission and reception of a registration acceptance message and / or a registration completion message.

[0231] Each device may complete the registration procedure based on the transmission or reception of a registration rejection message, or may recognize that the procedure was not completed normally or that the procedure was completed abnormally based on the transmission or reception of a registration rejection message.

[0232] Each device may transition to or maintain a state in which the UE is registered with the network (RM_REGISTERED state or 5GMM-REGISTERED state) based on the transmission and reception of a registration accept message and / or a registration complete message. Also, each device may transition to or maintain a state in which the UE is not registered with the network on the access from which the registration reject message was received for the current PLMN (RM_DEREGISTERED state or 5GMM-DEREGISTERED state) based on the transmission and reception of a registration reject message. Also, the transition to each state of each device may be based on the transmission and reception of a registration complete message or the completion of the registration procedure.

[0233] Furthermore, each device may perform processing based on the information transmitted and received during the registration procedure based on the completion of the registration procedure. For example, if the device transmits or receives information indicating that some of the UE's requests have been rejected, the device may recognize the reason why the UE's requests have been rejected. Furthermore, each device may perform this procedure again based on the reason why the UE's requests have been rejected, or may perform the registration procedure for core network_A or another cell.

[0234] Furthermore, the UE may store the identification information received with the registration accept message and / or the registration reject message and may recognize the network's decision based on the completion of the registration procedure.

[0235] Furthermore, each device may store the information transmitted and received in this procedure in association with each other.

[0236] In addition, the UE may send a registration request message including a first S-NSSAI and UE capability information indicating that it supports energy efficiency functions, receive a registration accept message including the first S-NSSAI, a reason value indicating that the first S-NSSAI has reached an upper limit of energy consumption per network slice, and a second S-NSSAI, associate and store the first S-NSSAI and / or the second S-NSSAI and / or the first S-NSSAI have reached an upper limit of energy consumption per network slice, and send a PDU session establishment request message together with the second S-NSSAI.

[0237] Furthermore, the UE and / or NW may use what they have recognized and / or stored based on the identification information and / or control information exchanged through this procedure as a criterion for determining whether or not to initiate an MM procedure or SM procedure that will be executed separately after the completion of this procedure.

[0238] [3.2. PDU Session Establishment Procedure] Next, the behavior of each device when a UE executes a PDU session establishment procedure will be explained using Figure 7. Hereinafter, the PDU session establishment procedure may be referred to as this procedure. The PDU session establishment procedure may also be an SM procedure.

[0239] Furthermore, this procedure may be performed after the registration procedure and / or PDU session establishment procedure have been performed one or more times.

[0240] First, the UE sends a PDU session establishment request message to the SMF via 3GPP access or non-3GPP access (S1400, S1402, S1404) to start the PDU session establishment procedure. Then, the SMF receives the PDU session establishment request message from the UE.

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

[0242] Furthermore, the AMF may determine an SMF based on a NAS message received from the UE and / or a network state (S1402). Further, the AMF may forward identification information included in the received PDU session establishment request message and / or NAS message to the selected SMF (S1404).

[0243] The UE may send a PDU session establishment request message based on receiving at least one of the eleventh to sixteenth identification information.

[0244] Here, the UE may include at least one of the identification information items 21 to 24 in the PDU session establishment request message or the NAS message and transmit it. Note that the UE may also include other identification information in the PDU session establishment request message or the NAS message. Specifically, the UE may include the requested DNN or PDU session ID in the PDU session establishment request message or the NAS message.

[0245] By transmitting these pieces of identification information, the UE may indicate that it supports each function, indicate a request from the UE, or indicate to the network the information indicated by each piece of identification information.

[0246] In addition, the UE may select and decide whether to send at least one of the identification information items 21 to 24 to the network based on the UE's capability information, and / or UE policy, and / or UE status, and / or user registration information, and / or context held by the UE, and / or identification information sent and received in procedures performed prior to this procedure, etc.

[0247] For example, if the UE supports some or all of the functions of network energy related information exposure, and / or EE, and / or EC, and / or ES, and / or EEES, and / or CE, and / or RE, the UE may include 22nd identification information indicating that it supports the functions of network energy related information exposure, and / or EE, and / or EC, and / or ES, and / or EEES, and / or CE, and / or RE in the PDU session establishment request message and / or NAS message.

[0248] Furthermore, when the UE wishes to perform a PDU session establishment or PDU session establishment request procedure regarding, for example, network energy related information exposure, and / or EE, and / or EC, and / or ES, and / or EEES, and / or CE, and / or RE, the UE may include control information indicating the network energy related information exposure, and / or EE, and / or EC, and / or ES, and / or EEES, and / or CE, and / or RE in the PDU session establishment request message and / or NAS message.

[0249] Also, when the UE has already received the identification information, it may recognize the meaning indicated by the identification information.

[0250] Furthermore, when the UE has already received the eleventh identification information, the UE may include the S-NSSAI included in the eleventh identification information in the 21st identification information. For example, when the eleventh identification information is an allowed NSSAI and / or a configured NSSAI including one or more S-NSSAIs, the UE may include one or more S-NSSAIs among them in the 21st identification information. Furthermore, when the eleventh identification information is a rejected NSSAI and / or an extended rejected NSSAI and / or a pending NSSAI including one or more S-NSSAIs, the UE may not include one or more S-NSSAIs among them in the 21st identification information.

[0251] Furthermore, when the UE has already received the 15th identification information, the UE may include the S-NSSAI indicated by the 15th identification information in the 21st identification information. Furthermore, when the UE has already received the 15th identification information, the UE may include the S-NSSAI indicated by the 15th identification information in the 21st identification information, regardless of whether the 11th identification information has been received.

[0252] Furthermore, when the UE has already received the 11th identification information and the 14th identification information, the UE does not need to include the S-NSSAI contained in the 11th identification information in the 21st identification information.

[0253] In addition, when the UE has already received the 11th identification information and / or the 14th identification information and / or the 15th identification information, it may include the S-NSSAI included in the 15th identification information in the 21st identification information.

[0254] Furthermore, when the UE has already received the 11th identification information and / or the 13th identification information and / or the 14th identification information, if the timer using the timer value indicated in the 13th identification information has not expired, the UE does not need to include the S-NSSAI included in the 11th identification information in the 21st identification information.

[0255] In addition, when the UE has already received the 11th identification information and / or the 13th identification information and / or the 14th identification information, when the timer using the timer value indicated by the 13th identification information has expired, or when the timer has been stopped based on an instruction from the NW side (e.g., a control message such as a setting update command), the UE may include the S-NSSAI contained in the 11th identification information in the 21st identification information.

[0256] In addition, when the UE has already received the 31st identification information, the UE may include the S-NSSAI indicated by the 31st identification information in the 21st identification information.

[0257] Furthermore, when the UE has already received the 35th identification information, the UE may include the S-NSSAI indicated by the 35th identification information in the 21st identification information. Furthermore, when the UE has already received the 35th identification information, the UE may include the S-NSSAI indicated by the 35th identification information in the 21st identification information, regardless of whether the 31st identification information has been received or not.

[0258] Furthermore, when the UE has already received the 31st identification information and the 34th identification information, the UE does not need to include the S-NSSAI included in the 31st identification information in the first identification information.

[0259] Furthermore, when the UE has already received the 31st identification information and the 34th identification information, the UE does not need to include the S-NSSAI contained in the 31st identification information in the 21st identification information.

[0260] In addition, when the UE has already received the 31st identification information and / or the 34th identification information and / or the 35th identification information, it may include the S-NSSAI included in the 35th identification information in the 21st identification information.

[0261] Furthermore, when the UE has already received the 31st identification information and / or the 33rd identification information and / or the 34th identification information, if the timer using the timer value indicated in the 33rd identification information has not expired, the UE does not need to include the S-NSSAI contained in the 31st identification information in the 31st identification information.

[0262] In addition, when the UE has already received the 31st identification information and / or the 33rd identification information and / or the 34th identification information, when the timer using the timer value indicated by the 33rd identification information has expired, or when the timer has been stopped based on an instruction from the network side (e.g., a control message such as a PDU session change command or a setting update command), the UE may include the S-NSSAI contained in the 31st identification information in the 21st identification information.

[0263] Furthermore, when the UE has already received the 11th identification information and / or the 14th identification information, the UE may determine whether to include the S-NSSAI included in the 11th identification information in the 21st identification information based on the current energy consumption or future energy consumption indicated by the 14th identification information for the S-NSSAI included in the 11th identification information. For example, when the current energy consumption or future energy consumption indicated by the 14th identification information exceeds a predetermined value, the UE may not include the S-NSSAI included in the 11th identification information in the 21st identification information. Furthermore, when the current energy consumption or future energy consumption indicated by the 14th identification information does not exceed a predetermined value, the UE may include the S-NSSAI included in the 11th identification information in the 21st identification information.

[0264] Furthermore, when the UE has already received the 31st identification information and / or the 34th identification information, the UE may determine whether to include the S-NSSAI included in the 31st identification information in the 21st identification information based on the current energy consumption or future energy consumption indicated by the 34th identification information for the S-NSSAI included in the 31st identification information. For example, when the current energy consumption or future energy consumption indicated by the 34th identification information exceeds a predetermined value, the UE may not include the S-NSSAI included in the 31st identification information in the 21st identification information. Furthermore, when the current energy consumption or future energy consumption indicated by the 34th identification information does not exceed a predetermined value, the UE may include the S-NSSAI included in the 31st identification information in the 21st identification information.

[0265] Next, when the AMF receives the NAS message, it can recognize what the UE is requesting and / or the contents of the information contained in the NAS message (message, container, information, etc.).

[0266] Next, the AMF selects an SMF as a transfer destination for at least part of the information (message, container, information) included in the NAS message received from the UE (S1402). The AMF may select the transfer destination SMF based on the information (message, container, information) included in the NAS message, and / or subscriber information, and / or network capability information, and / or UE policy, and / or operator policy, and / or network status, and / or user registration information, and / or context held by the AMF, etc.

[0267] Specifically, the AMF may select an SMF for establishing a PDU session for a DNN similar to the DNN with which the first PDU session is associated. Similarly, the AMF may select an SMF for establishing a PDU session for an S-NSSAI similar to the S-NSSAI with which the first PDU session is associated.

[0268] The AMF may also select an SMF for establishing a PDU session for an S-NSSAI for which an SST similar to the SST of the S-NSSAI to which the first PDU session is associated is configured, or the AMF may select an SMF for establishing a PDU session for an S-NSSAI different from the S-NSSAI to which the first PDU session is associated.

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

[0270] Next, when the SMF receives information (messages, containers, information) sent from the AMF, it can recognize what the UE is requesting and / or the content of the information (messages, containers, information) received from the AMF.

[0271] Here, the SMF may perform a second condition determination. The second condition determination may be for determining whether the network accepts the UE request. If the SMF determines that the second condition determination is true, it may start the procedure of (A) in Figure 8, and if the SMF determines that the second condition determination is false, it may start the procedure of (B) in Figure 8.

[0272] Furthermore, the second condition determination may be performed based on information received from the AMF (message, container, information), and / or subscription information, and / or network capability information, and / or UE policy, and / or operator policy, and / or network status, and / or user registration information, and / or context held by the SMF, etc.

[0273] For example, if the network permits the UE's request, the second condition determination may be determined as true, and if the network does not permit the UE's request, the second condition determination may be determined as false. Furthermore, if the network to which the UE is connected and / or a device within the network supports the function requested by the UE, the second condition determination may be determined as true, and if the function requested by the UE is not supported, the second condition determination may be determined as false. Furthermore, if the transmitted and received identification information is permitted, the second condition determination may be determined as true, and if the transmitted and received identification information is not permitted, the second condition determination may be determined as false.

[0274] The conditions for determining whether the second condition is true or false are not limited to the above-mentioned conditions.

[0275] Note that the second condition determination may be performed by an NF other than the SMF. The NF may be, for example, an NSSF, an NWDAF, a PCF, or an NRF. When an NF other than the SMF performs the second condition determination, the SMF may provide the NF with information necessary for performing the second condition determination, specifically, at least a portion of the information received from the UE (S1406). Then, when the NF determines whether the second condition determination is true or false based on the information received from the SMF, it may convey information including the result of the second condition determination (i.e., whether it is true or false) to the SMF. The SMF may determine identification information and / or a control message to be transmitted to the UE based on the result of the second condition determination received from the NF.

[0276] Furthermore, step S1406 may be executed regardless of whether the second condition determination is performed by the SMF or by an NF other than the SMF.

[0277] The SMF may also use the UE ID, and / or the access type (corresponding to the access that sent the PDU session establishment request message), and / or the PDU session ID, and / or one or more S-NSSAIs included in the 21st identity and / or the 23rd identity, and / or the Network energy related information to check with the NSACF and / or NSSF and / or PCF and / or OAM and / or new NF whether the upper limit or threshold of Network energy related information exposure and / or EE and / or EC and / or ES and / or EEES and / or CE and / or RE has been reached, or whether the upper limit or threshold of Network energy related information exposure and / or EE and / or EC and / or ES and / or EEES and / or CE and / or RE per NS has been reached, or whether the upper limit or threshold of Network energy related information exposure and / or EE and / or EC and / or ES and / or EEES and / or CE and / or RE per UE and / or PDU session and / or QoS flow has been reached. The SMF may transmit control information indicating an increase in exposure and / or EE and / or EC and / or ES and / or EEES and / or CE and / or RE, and / or control information indicating an increase in network energy related information exposure and / or EE and / or EC and / or ES and / or EEES and / or CE and / or RE per NS, and / or control information indicating an increase in network energy related information exposure and / or EE and / or EC and / or ES and / or EEES and / or CE and / or RE per UE and / or PDU session and / or QoS flow, which may be transmitted by the SMF to the NSACF and / or NSSF and / or PCF and / or OAM and / or new NF via the AMF.

[0278] Furthermore, when one or more S-NSSAIs included in the 21st identification information and / or the 23rd identification information received from the UE correspond to V2X (Vehicle-to-Everything), and / or V2X service, and / or A2X (Aircraft-to-Everything), and / or A2X service, and / or emergency service, the SMF may not need to transmit this control information to the NSACF and / or NSSF and / or PCF and / or OAM and / or new NF.

[0279] Furthermore, the NSACF and / or NSSF and / or PCF and / or OAM and / or new NF receiving the control information from the SMF may check or determine whether an upper limit or threshold for network energy related information exposure and / or EE and / or EC and / or ES and / or EEES and / or CE and / or RE has been reached, or whether an upper limit or threshold for network energy related information exposure and / or EE and / or EC and / or ES and / or EEES and / or CE and / or RE per NS has been reached, or whether an upper limit or threshold for network energy related information exposure and / or EE and / or EC and / or ES and / or EEES and / or CE and / or RE per UE and / or PDU session and / or QoS flow has been reached, whereby this checking or determination may or may not be performed per access type. In addition, the NSACF and / or NSSF and / or PCF and / or OAM and / or new NF may not need to check or determine whether these upper limits or thresholds have been reached when one or more S-NSSAIs included in the 21st identification information and / or 23rd identification information received from the SMF correspond to V2X (Vehicle-to-Everything), and / or V2X services, and / or A2X (Aircraft-to-Everything), and / or A2X services, and / or emergency services.

[0280] Furthermore, when the NSACF and / or NSSF and / or PCF and / or OAM and / or new NF confirms or determines that these upper limits or thresholds have been reached, it may transmit the UE ID, and / or the access type (corresponding to the access that sent the PDU session establishment request message), and / or the PDU session ID, and / or one or more S-NSSAIs included in the 21st identification information and / or the 23rd identification information, and / or control information indicating that the upper limits or thresholds of the EE and / or EC and / or ES and / or EEES and / or CE and / or RE have been reached, and / or control information indicating that the upper limits or thresholds of the EE and / or EC and / or ES and / or EEES and / or CE and / or RE have been reached, and / or Network energy related information per UE and / or PDU session and / or QoS flow. The SMF may transmit control information indicating that the exposure and / or EE and / or EC and / or ES and / or EEES and / or CE and / or RE have reached their upper limits or thresholds. This control information may be transmitted in the form of 34th identity information. Furthermore, the NSACF and / or NSSF and / or PCF and / or OAM and / or new NF may transmit an S-NSSAI that has reached these upper limits or thresholds to the SMF. This S-NSSAI may be transmitted in the form of 31st identity information. Furthermore, the NSACF and / or NSSF and / or PCF and / or OAM and / or new NF may transmit an S-NSSAI (alternative S-NSSAI) that replaces the S-NSSAI that has reached these upper limits or thresholds to the SMF. This S-NSSAI may be transmitted in the form of 35th identity information.Furthermore, the NSACF and / or NSSF and / or PCF and / or OAM and / or new NF may transmit to the SMF the timer (back-off timer) value for the S-NSSAI that has reached these upper limit values ​​or thresholds. This timer value may be transmitted in the 33rd identification information. Furthermore, when not making a determination for each access type, the NSACF and / or NSSF and / or PCF and / or OAM and / or new NF may not transmit the access type (corresponding to the access that transmitted the PDU session establishment request message).

[0281] Furthermore, when the NSACF and / or NSSF and / or PCF and / or OAM and / or new NF confirms or determines that these upper limits or thresholds have not been reached, it may transmit the UE ID, and / or the access type (corresponding to the access that sent the PDU session establishment request message), and / or the PDU session ID, and / or one or more S-NSSAIs included in the 21st identification information and / or the 23rd identification information, and / or control information indicating that the upper limits or thresholds have not been reached for the UE ID, and / or the access type (corresponding to the access that sent the PDU session establishment request message), and / or the PDU session ID, and / or one or more S-NSSAIs included in the 21st identification information and / or the 23rd identification information, and / or Network energy related information exposure and / or the EE and / or the EC and / or the ES and / or the EEES and / or the CE and / or the RE, and / or control information indicating that the upper limits or thresholds have not been reached for the UE ID, and / or the network energy related information exposure per NS and / or the EE and / or the EC and / or the ES and / or the EEES and / or the CE and / or the RE, and / or the network energy related information per UE and / or PDU session and / or QoS flow. The NSACF and / or NSSF and / or PCF and / or OAM and / or new NF may transmit control information indicating that the exposure and / or EE and / or EC and / or ES and / or EEES and / or CE and / or RE have not reached the upper limit or threshold to the SMF. Furthermore, if the determination is not made for each access type, the NSACF and / or NSSF and / or PCF and / or OAM and / or new NF may not transmit the access type (corresponding to the access that transmitted the PDU session establishment request message). Furthermore, the NSACF and / or NSSF and / or PCF and / or OAM and / or new NF may transmit this to the SMF via the AMF.

[0282] Also, when making a judgment for each access type, the NSACF and / or NSSF and / or PCF and / or OAM and / or new NF may, for example, reach an upper limit or threshold for one access type (e.g., 3GPP access) but not reach the upper limit or threshold for another access type (e.g., non-3GPP access).

[0283] Note that the exchange of control information between these SMFs (via AMFs as needed) and the NSACF and / or NSSF and / or PCF and / or OAM and / or new NF may be performed by one or more procedures. For example, some of the exchanges may be performed between the SMF and the NSACF and / or NSSF and / or PCF and / or OAM and / or new NF, and the remaining exchanges may be performed between the SMF and the NSACF and / or NSSF and / or PCF and / or OAM and / or new NF, thereby performing all of the exchanges.

[0284] Next, each step of the procedure in FIG. 8(A) will be explained.

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

[0286] The SMF may decide whether to approve C2 communication during this procedure based on information received from the AMF (message, container, information), and / or information such as PCC rules received from the PCF, and / or subscriber information, and / or network capability information, and / or UE policy, and / or operator policy, and / or network status, and / or user registration information, and / or context held by the SMF, etc.

[0287] If approval of C2 communication is performed during this procedure, the SMF may determine approval of the establishment of the PDU session requested by the UE based on at least one of the identification information items 21 to 23.

[0288] Here, the SMF may select one or more UPFs based on information received from the AMF (message, container, information), and / or information such as PCC rules received from the PCF, and / or subscriber information, and / or network capability information, and / or UE policy, and / or operator policy, and / or network status, and / or user registration information, and / or context held by the SMF, etc. If multiple UPFs are selected, the SMF may send an N4 session establishment request message to each UPF. Here, it is assumed that a UPF is selected.

[0289] Next, when the UPF receives the N4 session establishment request message (S1408), it can recognize the content of the information received from the SMF. Furthermore, based on the reception of the N4 session establishment request message, the UPF may send an N4 session establishment response message to the SMF, for example, via the N4 interface (S1410).

[0290] Next, when the SMF receives an N4 session establishment response message as a response message to the N4 session establishment request message, it can recognize the contents of the information received from the UPF.

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

[0292] Specifically, the SMF sends an N1 SM container, N2 SM information, and / or a PDU session ID to the AMF, for example, via the N11 interface, based on receiving the PDU session establishment request message, selecting the UPF, and / or receiving the N4 session establishment response message (S1412). Here, the N1 SM container may include a PDU session establishment accept message. Furthermore, the PDU session ID may be included in the PDU session establishment accept message.

[0293] Next, the AMF that has received the N1 SM container, and / or the N2 SM information, and / or the PDU session ID, transmits a NAS message to the UE via a first base station device included in the access network (S1414) (S1416). Here, the NAS message is transmitted, for example, via the N1 interface. The NAS message may also be a downlink NAS transport (DL NAS TRANSPORT) message.

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

[0295] The PDU session establishment acceptance message may be a response message to a PDU session establishment request, and may indicate that the establishment of the PDU session has been accepted.

[0296] Here, the SMF and / or AMF may indicate that at least part of the UE's request in the PDU session establishment request message has been accepted by sending a PDU session establishment acceptance message, and / or an N1 SM container, and / or a PDU session ID, and / or an NAS message, and / or N2 SM information, and / or an N2 PDU session request message.

[0297] Here, the SMF and / or AMF may include at least one of the identification information 31 to 36 in the PDU session establishment acceptance message, and / or the N1 SM container, and / or the NAS message, and / or the N2 SM information, and / or the N2 PDU session request message and send it.

[0298] By transmitting these identification information and / or the PDU session establishment acceptance message, the SMF may indicate that the network supports each function, that the UE request has been accepted, that the UE request has not been permitted, or a combination of these. Furthermore, when multiple identification information is transmitted and received, two or more of these identification information may be configured as one or more identification information. And / or, when one identification information has multiple meanings, it may be divided into multiple identification information and transmitted and received. For example, the information indicating support of each function and the information indicating a request to use each function may be transmitted and received as the same identification information or as different identification information.

[0299] Furthermore, the SMF and / or AMF may determine which identification information to include in the PDU session establishment acceptance message, and / or the N1 SM container, and / or the NAS message, and / or the N2 SM information, and / or the N2 PDU session request message based on each received identification information, and / or subscriber information, and / or network capability information, and / or UE policy, and / or operator policy, and / or network status, and / or user registration information, and / or context held by the SMF and / or AMF, etc.

[0300] Furthermore, the SMF may transmit at least one of the identification information items 31 to 36 based on the reception of at least one of the identification information items 21 to 24. In addition to these identification information items, the SMF may also transmit a PDU session ID. This PDU session ID may be associated with the identification information items 31 to 36. This PDU session ID may be the same as the PDU session ID transmitted in the PDU session establishment request message, or may be a new PDU session ID newly assigned on the network side.

[0301] In addition, if the NW supports some or all of the functions of Network energy related information exposure, and / or EE, and / or EC, and / or ES, and / or EEES, and / or CE, and / or RE, the SMF may include 32nd identification information indicating that the NW supports the functions of Network energy related information exposure, and / or EE, and / or EC, and / or ES, and / or EEES, and / or CE, and / or RE in the PDU session establishment acceptance message and / or NAS message.

[0302] Furthermore, if the NW does not support some or all of the functions of network energy related information exposure, and / or EE, and / or EC, and / or ES, and / or EEES, and / or CE, and / or RE, the SMF may include in the PDU session establishment accept message and / or NAS message a 32nd identification indicating that the functions of network energy related information exposure, and / or EE, and / or EC, and / or ES, and / or EEES, and / or CE, and / or RE are not supported. Furthermore, in this case, the SMF may not include the 33rd identification, and / or the 34th identification, and / or the 35th identification in the PDU session establishment accept message and / or NAS message.

[0303] The SMF also receives from the NSACF and / or NSSF and / or PCF and / or OAM and / or new NF the UE ID, and / or the access type (corresponding to the access that sent the PDU session establishment request message), and / or the PDU session ID, and / or one or more S-NSSAIs included in the 21st identity and / or the 23rd identity, and / or control information indicating that the network energy related information exposure and / or the EE and / or the EC and / or the ES and / or the EEES and / or the CE and / or the RE have not reached the upper limit or threshold, and / or control information indicating that the network energy related information exposure and / or the EE and / or the EC and / or the ES and / or the EEES and / or the CE and / or the RE have not reached the upper limit or threshold, and / or network energy related information per UE and / or PDU session and / or QoS flow. When control information is received indicating that exposure and / or EE and / or EC and / or ES and / or EEES and / or CE and / or RE has not reached an upper limit value or threshold, the 31st identification information and / or the 32nd identification information may be transmitted.

[0304] The SMF also receives from the NSACF and / or NSSF and / or PCF and / or OAM and / or new NF the UE ID, and / or the access type (corresponding to the access that sent the PDU session establishment request message), and / or the PDU session ID, and / or one or more S-NSSAIs included in the 21st identity and / or the 23rd identity, and / or control information indicating that the network energy related information exposure and / or the EE and / or the EC and / or the ES and / or the EEES and / or the CE and / or the RE has reached an upper limit or threshold, and / or control information indicating that the network energy related information exposure and / or the EE and / or the EC and / or the ES and / or the EEES and / or the CE and / or the RE has reached an upper limit or threshold, and / or network energy related information per UE and / or PDU session and / or QoS flow. When control information is received indicating that exposure and / or EE and / or EC and / or ES and / or EEES and / or CE and / or RE has reached an upper limit or threshold, the 31st identification information and / or the 32nd identification information and / or the 33rd identification information and / or the 34th identification information and / or the 35th identification information may be transmitted.

[0305] Here, the network may indicate the content of the above identification information to the UE by sending a PDU session establishment acceptance message.

[0306] In addition, the network may also transmit identification information other than the identification information 31 to 36 in the PDU session establishment accept message. Specifically, the network may transmit information indicating the SSC mode associated with the established PDU session and / or anchor point in the Selected SSC mode IE. The network may transmit information indicating the SSC mode associated with the established PDU session and / or anchor point in the Selected SSC mode IE.

[0307] The network may send the S-NSSAI and / or DNN associated with the established PDU session in a PDU session establishment accept message.

[0308] Next, when the UE receives the NAS message, for example via the N1 interface (S1416), it can recognize that the UE's request via the PDU session establishment request message has been accepted and / or the contents of the information (message, container, information) contained in the NAS message.

[0309] Furthermore, when the UE receives at least one of the identification information 31 to 36 and / or the PDU session ID from the core network, the UE may store the information indicated by the received identification information or may behave based on the information indicated by the received identification information.

[0310] For example, when the UE receives at least one of the 31st to 36th identification information, it may recognize and store the content of the received identification information.

[0311] Furthermore, based on receiving the 34th identification information, the UE may recognize and store whether the network energy related information exposure and / or EE and / or EC and / or ES and / or EEES and / or CE and / or RE has reached an upper limit or threshold, and / or whether the network energy related information exposure and / or EE and / or EC and / or ES and / or EEES and / or CE and / or RE per NS has reached an upper limit or threshold, and / or whether the network energy related information exposure and / or EE and / or EC and / or ES and / or EEES and / or CE and / or RE per UE and / or PDU session and / or QoS flow has reached an upper limit or threshold.

[0312] Furthermore, based on receiving the 31st identification information and the 34th identification information, the UE may recognize and store that the S-NSSAI indicated by the 31st identification information is unavailable based on the reason value indicated by the 34th identification information.

[0313] Furthermore, based on receiving the 31st identification information, the 34th identification information, and the 35th identification information, the UE may recognize that the S-NSSAI indicated by the 31st identification information is unavailable based on the reason value indicated by the 34th identification information, and may also recognize and store that the S-NSSAI indicated by the 35th identification information is available, and / or that registration is possible using that S-NSSAI, and / or that a registration procedure is possible using that S-NSSAI, and / or that a PDU session establishment procedure is possible using that S-NSSAI, and / or that a PDU session establishment is possible using that S-NSSAI.

[0314] Furthermore, based on receiving the 31st identification information, the 33rd identification information, and the 34th identification information, the UE may recognize and store that the S-NSSAI indicated by the 31st identification information is unavailable based on the cause value indicated by the 34th identification information, and may start a timer using the timer value indicated by the 33rd identification information. In this case, if the timer has not expired, the UE may recognize and store that the S-NSSAI included in the 31st identification information is unavailable, and / or that registration using that S-NSSAI is unavailable, and / or that a registration procedure using that S-NSSAI is unavailable, and / or that a PDU session establishment procedure using that S-NSSAI is unavailable, and / or that a PDU session establishment using that S-NSSAI is unavailable. Furthermore, when the timer expires or when the timer is stopped based on an instruction from the network side (for example, a control message such as a PDU session change command sent from the SMF to the UE), the UE may recognize and memorize that the S-NSSAI included in the 31st identification information is available, and / or that registration is possible using that S-NSSAI, and / or that a registration procedure is possible using that S-NSSAI, and / or that a PDU session establishment procedure is possible using that S-NSSAI, and / or that a PDU session is possible to establish using that S-NSSAI.

[0315] Next, each step of the procedure in FIG. 8(B) will be explained.

[0316] First, based on receiving the PDU session establishment request message, the SMF sends an N1 SM container and / or a PDU session ID to the AMF, for example, via the N11 interface (S1418). Here, the N1 SM container may include a PDU session establishment rejection message. Furthermore, the PDU session ID may be included in the PDU session establishment rejection message.

[0317] Next, the AMF that has received the N1 SM container and / or the PDU session ID transmits a NAS message to the UE via a base station device included in the access network (S1420) (S1422). Here, the NAS message is transmitted, for example, via an N1 interface. The NAS message may be a downlink NAS transport (DL NAS TRANSPORT) message. The NAS message may include the PDU session ID and / or the N1 SM container.

[0318] The PDU session establishment rejection message may be a response message to a PDU session establishment request, and may indicate that the establishment of the PDU session has been rejected.

[0319] Here, the SMF and / or AMF may indicate that the UE's request via the PDU session establishment request message has been rejected by sending a PDU session establishment rejection message, and / or an N1 SM container, and / or a PDU session ID, and / or an NAS message.

[0320] Furthermore, by sending a PDU session establishment rejection message, the SMF may indicate that the UE request has been rejected, or that the request from the UE has not been permitted, or may indicate a combination of these.

[0321] Here, the SMF and / or AMF may include identification information 31 to 36 in the PDU session establishment rejection message, and / or the N1 SM container, and / or the NAS message, and / or the N2 SM information, and / or the N2 PDU session request message and send it.

[0322] Furthermore, the SMF and / or AMF may determine which identification information to include in the PDU session establishment rejection message, and / or the N1 SM container, and / or the NAS message, and / or the N2 SM information, and / or the N2 PDU session request message based on each received identification information, and / or subscriber information, and / or network capability information, and / or UE policy, and / or operator policy, and / or network status, and / or user registration information, and / or context held by the SMF and / or AMF, etc.

[0323] Furthermore, the SMF may transmit at least one of the identification information items 31 to 36 based on the reception of at least one of the identification information items 21 to 24. In addition to these identification information items, the SMF may also transmit a PDU session ID. This PDU session ID may be associated with the identification information items 31 to 36. This PDU session ID may be the same as the PDU session ID transmitted in the PDU session establishment request message, or may be a new PDU session ID newly assigned on the network side.

[0324] In addition, if the NW supports some or all of the functions of Network energy related information exposure, and / or EE, and / or EC, and / or ES, and / or EEES, and / or CE, and / or RE, the SMF may include 32nd identification information indicating that the functions of Network energy related information exposure, and / or EE, and / or EC, and / or ES, and / or EEES, and / or CE, and / or RE are supported in the PDU session establishment rejection message and / or NAS message.

[0325] Furthermore, if the NW does not support some or all of the functions of network energy related information exposure, and / or EE, and / or EC, and / or ES, and / or EEES, and / or CE, and / or RE, the SMF may include in the PDU session establishment rejection message and / or NAS message a 32nd identification indicating that the functions of network energy related information exposure, and / or EE, and / or EC, and / or ES, and / or EEES, and / or CE, and / or RE are not supported. Furthermore, in this case, the SMF may not include the 33rd identification, and / or the 34th identification, and / or the 35th identification in the PDU session establishment rejection message and / or NAS message.

[0326] The SMF also receives from the NSACF and / or NSSF and / or PCF and / or OAM and / or new NF the UE ID, and / or the access type (corresponding to the access that sent the PDU session establishment request message), and / or the PDU session ID, and / or one or more S-NSSAIs included in the 21st identity and / or the 23rd identity, and / or control information indicating that the network energy related information exposure and / or the EE and / or the EC and / or the ES and / or the EEES and / or the CE and / or the RE have not reached the upper limit or threshold, and / or control information indicating that the network energy related information exposure and / or the EE and / or the EC and / or the ES and / or the EEES and / or the CE and / or the RE have not reached the upper limit or threshold, and / or network energy related information per UE and / or PDU session and / or QoS flow. When control information is received indicating that exposure and / or EE and / or EC and / or ES and / or EEES and / or CE and / or RE has not reached an upper limit value or threshold, the 31st identification information and / or the 32nd identification information may be transmitted.

[0327] The SMF also receives from the NSACF and / or NSSF and / or PCF and / or OAM and / or new NF the UE ID, and / or the access type (corresponding to the access that sent the PDU session establishment request message), and / or the PDU session ID, and / or one or more S-NSSAIs included in the 21st identity and / or the 23rd identity, and / or control information indicating that the network energy related information exposure and / or the EE and / or the EC and / or the ES and / or the EEES and / or the CE and / or the RE has reached an upper limit or threshold, and / or control information indicating that the network energy related information exposure and / or the EE and / or the EC and / or the ES and / or the EEES and / or the CE and / or the RE has reached an upper limit or threshold, and / or network energy related information per UE and / or PDU session and / or QoS flow. When control information is received indicating that exposure and / or EE and / or EC and / or ES and / or EEES and / or CE and / or RE has reached an upper limit or threshold, the 31st identification information and / or the 32nd identification information and / or the 33rd identification information and / or the 34th identification information and / or the 35th identification information may be transmitted.

[0328] Next, when the UE receives the NAS message, for example via the N1 interface (S1422), it can recognize that the UE's request via the PDU session establishment request message has been rejected and / or the contents of the information (message, container, information) contained in the NAS message.

[0329] Furthermore, when the UE receives at least one of the identification information from Nos. 31 to 36, the UE may store the content indicated by the received identification information or may behave based on the information indicated by the received identification information.

[0330] For example, when the UE receives at least one of the 31st to 36th identification information, it may recognize and store the content of the received identification information.

[0331] Furthermore, based on receiving the 34th identification information, the UE may recognize and store whether the network energy related information exposure and / or EE and / or EC and / or ES and / or EEES and / or CE and / or RE has reached an upper limit or threshold, and / or whether the network energy related information exposure and / or EE and / or EC and / or ES and / or EEES and / or CE and / or RE per NS has reached an upper limit or threshold, and / or whether the network energy related information exposure and / or EE and / or EC and / or ES and / or EEES and / or CE and / or RE per UE and / or PDU session and / or QoS flow has reached an upper limit or threshold.

[0332] Furthermore, based on receiving the 31st identification information and the 34th identification information, the UE may recognize and store that the S-NSSAI indicated by the 31st identification information is unavailable based on the reason value indicated by the 34th identification information.

[0333] Furthermore, based on receiving the 31st identification information, the 34th identification information, and the 35th identification information, the UE may recognize that the S-NSSAI indicated by the 31st identification information is unavailable based on the reason value indicated by the 34th identification information, and may also recognize and store that the S-NSSAI indicated by the 35th identification information is available, and / or that registration is possible using that S-NSSAI, and / or that a registration procedure is possible using that S-NSSAI, and / or that a PDU session establishment procedure is possible using that S-NSSAI, and / or that a PDU session establishment is possible using that S-NSSAI.

[0334] Furthermore, based on receiving the 31st identification information, the 33rd identification information, and the 34th identification information, the UE may recognize and store that the S-NSSAI indicated by the 31st identification information is unavailable based on the cause value indicated by the 34th identification information, and may start a timer using the timer value indicated by the 33rd identification information. In this case, if the timer has not expired, the UE may recognize and store that the S-NSSAI included in the 31st identification information is unavailable, and / or that registration using that S-NSSAI is unavailable, and / or that a registration procedure using that S-NSSAI is unavailable, and / or that a PDU session establishment procedure using that S-NSSAI is unavailable, and / or that a PDU session establishment using that S-NSSAI is unavailable. Furthermore, when the timer expires or when the timer is stopped based on an instruction from the network side (for example, a control message such as a PDU session change command sent from the SMF to the UE), the UE may recognize and memorize that the S-NSSAI included in the 31st identification information is available, and / or that registration is possible using that S-NSSAI, and / or that a registration procedure is possible using that S-NSSAI, and / or that a PDU session establishment procedure is possible using that S-NSSAI, and / or that a PDU session is possible to establish using that S-NSSAI.

[0335] Each device may complete this procedure based on sending and receiving a PDU session establishment acceptance message. At this time, each device may transition to a state in which it can communicate with the DN using the established PDU session. Alternatively, each device may complete this procedure based on sending and receiving a PDU session establishment rejection message. At this time, each device may not establish a PDU session.

[0336] In addition, the processes performed by the UE based on the reception of each piece of identification information described above may be performed during this procedure or after completion of this procedure.

[0337] In addition, the UE may send a PDU session establishment request message along with a first S-NSSAI and including UE capability information indicating that it supports energy efficiency functions, receive a PDU session establishment rejection message including the first S-NSSAI, a timer value for the first S-NSSAI, and a rejected NSSAI including a reason value indicating that the first S-NSSAI has reached an upper limit value for energy consumption per network slice, associate and store the first S-NSSAI and / or the timer value for the first S-NSSAI, and / or the fact that the first S-NSSAI has reached an upper limit value for energy consumption per network slice, start a timer using the timer value for the first S-NSSAI, and when the timer expires, send a PDU session establishment request message along with the first S-NSSAI.

[0338] Furthermore, the UE and / or NW may use what they have recognized and / or stored based on the identification information and / or control information exchanged through this procedure as a criterion for determining whether or not to initiate an MM procedure or SM procedure that will be executed separately after the completion of this procedure.

[0339] [4. Modifications] A program running on an apparatus according to one aspect of this embodiment may be a program that controls a central processing unit (CPU) or the like to cause a computer to function so as to realize the functions of an embodiment according to this embodiment. The program or information handled by the program is temporarily stored in a volatile memory such as a random access memory (RAM), a non-volatile memory such as a flash memory, a hard disk drive (HDD), or another storage device system.

[0340] A program for implementing the functions of an embodiment according to one aspect of this example may be recorded on a computer-readable recording medium. The program may be read into a computer system and executed to implement the functions. The term "computer system" as used herein refers to a computer system built into a device, including hardware such as an operating system and peripheral devices. The term "computer-readable recording medium" may also refer to a semiconductor recording medium, an optical recording medium, a magnetic recording medium, a medium that dynamically stores a program for a short period of time, or any other computer-readable recording medium.

[0341] Additionally, each functional block or feature of the device used in the above-described embodiments may be implemented or performed by an electrical circuit, such as an integrated circuit or multiple integrated circuits. The electrical circuit designed to perform the functions described herein may include a general-purpose processor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA), or other programmable logic device, discrete gate or transistor logic, discrete hardware components, or a combination thereof. The general-purpose processor may be a microprocessor, or a conventional processor, controller, microcontroller, or state machine. The electrical circuit may be composed of digital circuits or analog circuits. Furthermore, as advances in semiconductor technology emerge, one or more aspects of the present embodiments may utilize new integrated circuit technologies that replace current integrated circuits.

[0342] It should be noted that the present embodiment is not limited to the above-described embodiment. In the embodiment, one example of a device is described, but one aspect of the present embodiment is not limited to this, and can be applied to terminal devices or communication devices such as stationary or non-movable electronic devices installed indoors or outdoors, for example, AV equipment, kitchen equipment, cleaning / washing equipment, air conditioning equipment, office equipment, vending machines, and other household appliances.

[0343] Although this embodiment has been described in detail above with reference to the drawings, the specific configuration is not limited to this embodiment, and design modifications within the scope of this embodiment are also included. Furthermore, various modifications of one aspect of this embodiment are possible within the scope of the claims, and embodiments obtained by appropriately combining the technical means disclosed in different embodiments are also included in the technical scope of this embodiment. Furthermore, configurations in which elements described in each of the above embodiments are substituted with elements that achieve the same effect are also included.

Claims

1. A UE (User Equipment) comprising a transceiver unit, a control unit, and a memory unit, wherein the transceiver unit: transmits a registration request message including a first S-NSSAI and UE capability information indicating that an energy efficiency function is supported; receives a registration acceptance message including the first S-NSSAI, a reason value indicating that the first S-NSSAI has reached an upper limit of energy consumption per network slice, and a second S-NSSAI; the control unit associates and stores in the memory unit the first S-NSSAI, and / or the second S-NSSAI, and / or the first S-NSSAI has reached an upper limit of energy consumption per network slice; and the transceiver unit: transmits a PDU session establishment request message together with the second S-NSSAI.

Images