[go: up one dir, main page]

WO2025094593A1 - Équipement utilisateur (ue) - Google Patents

Équipement utilisateur (ue) Download PDF

Info

Publication number
WO2025094593A1
WO2025094593A1 PCT/JP2024/035715 JP2024035715W WO2025094593A1 WO 2025094593 A1 WO2025094593 A1 WO 2025094593A1 JP 2024035715 W JP2024035715 W JP 2024035715W WO 2025094593 A1 WO2025094593 A1 WO 2025094593A1
Authority
WO
WIPO (PCT)
Prior art keywords
identification information
nssai
network
information
pdu session
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Pending
Application number
PCT/JP2024/035715
Other languages
English (en)
Japanese (ja)
Inventor
靖夫 菅原
周一郎 千葉
晶貴 泉
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Sharp Corp
Original Assignee
Sharp Corp
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Sharp Corp filed Critical Sharp Corp
Publication of WO2025094593A1 publication Critical patent/WO2025094593A1/fr
Pending legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W28/00—Network traffic management; Network resource management
    • H04W28/02—Traffic management, e.g. flow control or congestion control
    • H04W28/08—Load balancing or load distribution
    • H04W28/084—Load balancing or load distribution among network function virtualisation [NFV] entities; among edge computing entities, e.g. multi-access edge computing
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W52/00—Power management, e.g. Transmission Power Control [TPC] or power classes
    • H04W52/02—Power saving arrangements
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/10—Connection setup
    • H04W76/18—Management of setup rejection or failure
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W8/00—Network data management
    • H04W8/22—Processing or transfer of terminal data, e.g. status or physical capabilities
    • H04W8/24—Transfer of terminal data

Definitions

  • This embodiment relates to UE (User Equipment).
  • UE User Equipment
  • the 3GPP (3rd Generation Partnership Project) is studying the system architecture for the fifth generation (5G) mobile communication system (also called 5G System or 5GS) (see non-patent documents 1 to 3).
  • 5G fifth generation
  • 5GS 5G System
  • 3GPP is currently discussing the standardization of Release 18 (also called Rel-18) (see non-patent documents 1 to 3).
  • NAS Non-Access-Stratum
  • Non-Patent Document 4 lists network energy related information exposure as a key issue, specific solutions to this issue have not yet been discussed.
  • One aspect of this embodiment was made in consideration of the above circumstances, and aims to clarify a method for efficiently disclosing information related to network energy, in particular UE behavior and NW (network) behavior.
  • the UE of one aspect of this embodiment is a UE (User Equipment) having a transceiver, a control unit, and a memory unit, and the transceiver transmits a PDU session establishment request message including a first S-NSSAI and UE capability information indicating that the energy efficiency function is supported, receives 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 of energy consumption per network slice, the control unit associates and stores in the memory 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 of energy consumption per network slice, the control unit starts a timer using the timer value for the first S-NSSAI, and when the timer expires, the transceiver transmits a PDU session establishment request message along with the first
  • One aspect of this embodiment is to provide a method for efficiently disclosing information related to network energy, in particular clarifying UE behavior and NW behavior.
  • FIG. 1 is a diagram illustrating an overview of a mobile communication system (EPS/5GS). A diagram explaining the detailed configuration of a mobile communication system (EPS/5GS). A diagram explaining the device configuration of a UE. A diagram explaining the configuration of an access network device (gNB) in 5GS. A diagram explaining the configuration of a core network device (AMF/SMF) in 5GS.
  • FIG. 1 is a diagram illustrating a registration procedure. A diagram explaining the PDU session establishment procedure.
  • FIG. 1 is a diagram for explaining an outline of a mobile communication system 1 used in each embodiment
  • FIG. 2 is a diagram for explaining a detailed configuration of the mobile communication system 1. As shown in FIG.
  • 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.
  • PDN Packet Data Network
  • these devices and functions may be referred to without symbols, such as UE, access network_A, core network_A, PDN, access network_B, core network_B, DN, etc.
  • 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.
  • 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.
  • these devices and functions may be referred to without symbols, such as UE, E-UTRAN, MME, SGW, PGW-U, PGW-C, PCRF, HSS, 5G AN, AMF, UPF, SMF, PCF, UDM, N3IWF, etc.
  • the 4G system EPS (Evolved Packet System) is composed of 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) is composed of a UE, an access network_B and a core network_B, but may further include a DN.
  • the UE is a device that can connect to network services 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).
  • the UE may be a terminal device capable of wireless communication, such as a mobile phone or smartphone, and may be a terminal device that can connect to both EPS and 5GS.
  • the UE may be equipped with a UICC (Universal Integrated Circuit Card) or an eUICC (Embedded UICC).
  • UICC Universal Integrated Circuit Card
  • eUICC embedded UICC
  • the UE may be referred to as either a user device or a terminal device.
  • access network_A corresponds to E-UTRAN (Evolved Universal Terrestrial Radio Access Network) and/or a wireless LAN access network.
  • E-UTRAN Evolved Universal Terrestrial Radio Access Network
  • eNBs evolved Node B
  • eNB 45 may be written without the symbol eNB.
  • the eNBs are connected to each other, for example, via an X2 interface.
  • one or more access points are deployed in the wireless LAN access network.
  • 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.
  • NG-RAN NG Radio Access Network
  • NR NodeBs NR NodeBs
  • One or more gNBs (NR NodeBs) 122 are deployed in the NG-RAN.
  • the symbol for gNB 122 may be omitted, such as gNB.
  • the gNB is a node that provides the NR (New Radio) user plane and control plane to the UE, and is a node that connects to the 5GCN via an NG interface (including the N2 interface or N3 interface).
  • 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.
  • the gNBs are connected to each other, for example, via an Xn interface.
  • the non-3GPP access network may be an untrusted non-3GPP access network or a trusted non-3GPP access network.
  • 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.
  • the trusted non-3GPP access network may be an access network specified by 3GPP, and may have a TNAP (trusted non-3GPP access point) and a TNGF (trusted non-3GPP Gateway function).
  • E-UTRAN and NG-RAN may be referred to as 3GPP access.
  • wireless LAN access networks and non-3GPP AN may be referred to as non-3GPP access.
  • nodes placed in access network_B may be collectively referred to as NG-RAN nodes.
  • 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.
  • core network_A corresponds to the EPC (Evolved Packet Core).
  • the EPC includes, for example, the MME (Mobility Management Entity), SGW (Serving Gateway), PGW (Packet Data Network Gateway)-U, PGW-C, PCRF (Policy and Charging Rules Function), and HSS (Home Subscriber Server).
  • MME Mobility Management Entity
  • SGW Serving Gateway
  • PGW Packet Data Network Gateway
  • PGW-C Packet Data Network Gateway
  • PCRF Policy and Charging Rules Function
  • HSS Home Subscriber Server
  • core network_B corresponds to 5GCN (5G Core Network).
  • 5GCN includes, for example, AMF (Access and Mobility Management Function), UPF (User Plane Function), SMF (Session Management Function), PCF (Policy Control Function), UDM (Unified Data Management), etc.
  • AMF Access and Mobility Management Function
  • UPF User Plane Function
  • SMF Session Management Function
  • PCF Policy Control Function
  • UDM Unified Data Management
  • 5GCN may be expressed as 5GC.
  • 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, or core network devices, or devices within a core network.
  • the core network may be an IP mobile communications 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 communications operator that operates and manages the mobile communications system 1, or it may be a core network for a virtual mobile communications operator or virtual mobile communications service provider such as an MVNO (Mobile Virtual Network Operator) or MVNE (Mobile Virtual Network Enabler).
  • MNO Mobile Network Operator
  • MVNE Mobile Virtual Network Enabler
  • 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.
  • the PDN may include a connected communication terminal. Therefore, connecting to the PDN may be connecting to a communication terminal or a server device arranged in the PDN.
  • transmitting and receiving user data to and from the PDN may be transmitting and receiving user data to and from a communication terminal or a server device arranged in the PDN.
  • the PDN may be expressed as the DN, and the DN may be expressed as the PDN.
  • access network_A, core network_A, PDN, access network_B, core network_B, DN, and/or one or more devices included therein may be referred to as a network or network device.
  • a network and/or a network device transmits or receives a message and/or executes a procedure
  • 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.
  • the UE can send and receive (communicate) user data with the PDN or DN.
  • IP Internet Protocol
  • non-IP communication may be used.
  • IP communication refers to data communication using IP, and data is sent and received using IP packets.
  • An IP packet is composed of an IP header and a payload section.
  • the payload section may include data sent and received by devices and functions included in EPS and devices and functions included in 5GS.
  • Non-IP communication refers to data communication that does not use IP, and data is sent and received in a format different from the IP packet structure.
  • non-IP communication may be data communication realized by sending and receiving application data without an IP header, or it may be user data sent and received by the UE with a different header such as a MAC header or an Ethernet (registered trademark) frame header added.
  • devices not shown in FIG. 2 may be configured in access network_A, core network_A, access network_B, core network_B, PDN_A, and DN_A.
  • each device and function is shown one by one, but the mobile communication system 1 may be configured with multiple similar devices and functions. 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.
  • 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.
  • the network refers to at least a part of the access network _B, the core network _B, and the DN.
  • one or more devices included in at least a part of the access network _B, the core network _B, and the DN may be referred to as a network or a network device.
  • a network transmits, receives, and/or processes messages it may mean that devices in the network (network devices and/or control devices) transmit, receives, and/or processes messages.
  • a device in a network transmits, receives, receives, and/or processes messages, it may mean that the network transmits, receives, and/or processes messages.
  • each device may be configured as physical hardware, may be configured as logical (virtual) hardware configured on general-purpose hardware, or may be configured 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.
  • each memory unit (memory unit_A340, memory unit_B540, memory unit_B740) in each device/function mentioned below is composed of, for example, a semiconductor memory, SSD (Solid State Drive), HDD (Hard Disk Drive), etc.
  • each memory unit can store not only information that was originally set at the time of shipment, but also various information transmitted and received between the device/function other than the device/function itself (for example, UE, and/or access network device, and/or core network device, and/or PDN, and/or DN).
  • each memory unit can store identification information, control information, flags, parameters, etc. contained in control messages transmitted and received within various communication procedures described below.
  • each memory unit may store this information for each UE.
  • each memory unit can store control messages and user data transmitted and received between 5GS and/or devices/functions included in EPS. At this time, not only those sent and received via the N26 interface, but also those sent and received without going through the N26 interface can be stored.
  • 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.
  • the control unit_A300 is a functional unit that controls the operation and functions of the entire UE.
  • the control unit_A300 realizes various processes in the UE by reading and executing various programs stored in the memory unit_A340 as necessary.
  • the transceiver unit_A320 is a functional unit for wirelessly communicating with a base station device (eNB or gNB) in the access network via an antenna. That is, the UE can use the transceiver 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.
  • a base station device eNB or gNB
  • 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 send and receive AMF and NAS (Non-Access-Stratum) messages via the N1 interface by using the transceiver unit_A320.
  • AMF and NAS Non-Access-Stratum
  • the memory unit_A340 is a functional unit for storing programs, user data, control information, etc. required for each operation of the UE.
  • the memory unit_340 may also have a function for storing control information transmitted and received between the access network device, the core network device, and the DN.
  • 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.
  • 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.
  • the network connection unit _B520 is a functional unit that enables the gNB to communicate with the AMF and/or UPF. In other words, the gNB can send and receive user data and/or control information between the AMF and/or UPF using the network connection unit _B520.
  • 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 between the UE and the gNB using the transceiver unit_B530.
  • a gNB in a 5G AN can communicate with the AMF via the N2 interface by using the network connection unit_B520, and can communicate with the UPF via the N3 interface.
  • the gNB can also communicate with a UE by using the transceiver unit_B530.
  • the memory unit_B540 is a functional unit for storing programs, user data, control information, etc. required for each operation of the gNB.
  • the memory unit_540 may have a function for storing control information transmitted and received between the UE, other access network devices (base station devices), core network devices, and DN.
  • 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.
  • the control unit_B700 is a functional unit that controls the operation and functions of the entire AMF.
  • the control unit_B700 realizes various processes in the AMF by reading and executing various programs stored in the memory unit_B740 as necessary.
  • the network connection unit_B720 is a functional unit that enables the AMF to connect to a base station device (gNB), and/or an SMF, and/or a PCF, and/or an UDM, and/or a SCEF, and/or an NSACF in a 5G AN.
  • the AMF can use the network connection unit_B720 to transmit and receive user data and/or control information between a base station device (gNB), and/or an SMF, and/or a PCF, and/or an UDM, and/or a SCEF in a 5G AN.
  • the AMF in the 5GCN can communicate with the gNB via the N2 interface by using the network connection unit_A620, can communicate with the UDM via the N8 interface, can communicate with the SMF via the N11 interface, and can communicate with the PCF via the N15 interface.
  • the AMF can send and receive NAS messages to and from the UE via the N1 interface by using the network connection unit_A620.
  • the N1 interface is logical, in reality, communication between the UE and the AMF is performed via the 5G AN.
  • the AMF supports the N26 interface, it can communicate with the MME via the N26 interface by using the network connection unit_A620.
  • 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 a function for storing control information transmitted and received between the UE, access network devices, other core network devices, and the DN.
  • the AMF has the following functions: 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) function, connection management (CM) function, reachability management function, mobility management function for UEs, etc., forwarding Session Management (SM) messages between the UE and the SMF, access authentication (Access Authorization) function, security anchor functionality (SEA), security context management (SCM), supporting the N2 interface for the N3IWF (Non-3GPP Interworking Function), supporting the sending and receiving of NAS signals with the UE via the N3IWF, and authenticating UEs connected via the N3IWF.
  • RM registration management
  • CM connection management
  • CM reachability management function
  • mobility management function for UEs etc.
  • SM Session Management
  • SEA security anchor functionality
  • SCM security context management
  • supporting the N2 interface for the N3IWF Non-3GPP Interworking Function
  • the RM state for each UE is managed.
  • the RM state may be synchronized between the UE and the AMF.
  • RM-DEREGISTERED state the UE is not registered in the network, so the UE context in the AMF does not have valid location information or routing information for the UE, and the AMF is therefore unable to reach the UE.
  • the RM-REGISTERED state the UE is registered in the network, so the UE can receive services that require registration with the network.
  • the RM state may also be expressed as the 5GMM state.
  • the RM-DEREGISTERED state may be expressed as the 5GMM-DEREGISTERED state
  • the RM-REGISTERED state may be expressed as the 5GMM-REGISTERED state.
  • 5GMM-REGISTERED may be a state in which each device has established a 5GMM context, or a state in which a PDU session context has been established.
  • UE_A10 may start sending and receiving user data and control messages, and may respond to paging.
  • UE_A10 may execute registration procedures other than the registration procedure for initial registration, and/or a service request procedure.
  • 5GMM-DEREGISTERED may mean that each device has not established a 5GMM context, that the location information of UE_A10 is not known to the network, or that the network is unable to reach UE_A10.
  • UE_A10 may initiate a registration procedure or establish a 5GMM context by performing the registration procedure.
  • the 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).
  • 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.
  • the CM-IDLE state the UE does not have an N2 interface connection or an N3 interface connection.
  • the CM-CONNECTED state the UE has a NAS signaling connection established with the AMF via the N1 interface.
  • the CM-CONNECTED state the UE may have an N2 interface connection and/or an N3 interface connection.
  • the CM state in 3GPP access and the CM state in non-3GPP access may be managed separately.
  • the CM state in 3GPP access may be 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).
  • the CM state in non-3GPP access may be a non-connected state in non-3GPP access (CM-IDLE state over non-3GPP access) and a connected state in non-3GPP access (CM-CONNECTED state over non-3GPP access).
  • the non-connected state may be expressed as an idle mode
  • the connected state mode may be expressed as a connected mode.
  • the CM state may be expressed as 5GMM mode.
  • the unconnected state may be expressed as 5GMM unconnected mode (5GMM-IDLE mode), and the connected state may be expressed as 5GMM connected mode (5GMM-CONNECTED mode).
  • the unconnected state in 3GPP access may be expressed as 5GMM unconnected mode in 3GPP access (5GMM-IDLE mode over 3GPP access), and the connected state in 3GPP access may be expressed as 5GMM connected mode in 3GPP access (5GMM-CONNECTED mode over 3GPP access).
  • the unconnected state in non-3GPP access may be expressed as 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 5GMM connected mode in non-3GPP access (5GMM-CONNECTED mode over non-3GPP access).
  • 5GMM unconnected mode may be expressed as idle mode
  • 5GMM connected mode may be expressed as connected mode.
  • one or more AMFs may be placed within core network_B.
  • the AMF may be a Network Function (NF) that manages one or more Network Slice Instances (NSIs).
  • NF Network Function
  • NSIs Network Slice Instances
  • the AMF may be a shared CP function (CCNF; Common CPNF (Control Plane Network Function)) shared among multiple NSIs.
  • CCNF Common CPNF (Control Plane Network Function)
  • the N3IWF is a device and/or function that is placed between the non-3GPP access and the 5GCN when the UE connects to the 5GS via the non-3GPP access.
  • 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.
  • the control unit_B700 is a functional unit that controls the operation and functions of the entire SMF.
  • the control unit_B700 realizes various processes in the SMF by reading and executing various programs stored in the memory unit_B740 as necessary.
  • the network connection unit _B720 is a functional unit that allows the SMF to connect to the AMF, and/or the UPF, and/or the PCF, and/or the UDM.
  • the SMF can use the network connection unit _B720 to send and receive user data and/or control information between the AMF, and/or the UPF, and/or the PCF, and/or the UDM, and/or the NSACF.
  • 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.
  • the memory unit_B740 is a functional unit for storing programs, user data, control information, etc. required for each operation of the SMF.
  • the SMF has a session management function such as establishing, modifying, and releasing PDU sessions, an IP address allocation for UEs and its management function, a UPF selection and control function, a UPF configuration function for routing traffic to the appropriate destination (destination), a function for sending and receiving the SM part of NAS messages, a function for notifying that downlink data has arrived (Downlink Data Notification), a function for providing AN-specific (for each AN) SM information that is sent to the AN via the N2 interface via the AMF, a function for determining the SSC mode (Session and Service Continuity mode) for the session, a roaming function, etc.
  • a session management function such as establishing, modifying, and releasing PDU sessions, an IP address allocation for UEs and its management function, a UPF selection and control function, a UPF configuration function for routing traffic to the appropriate destination (destination), a function for sending and receiving the SM part of NAS messages, a function for notifying that down
  • the memory unit_740 may have a function of storing control information transmitted and received between the UE, the access network device, other core network devices, and the DN.
  • 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.
  • the control unit_B700 is a functional unit that controls the operation and functions of the entire UPF.
  • the control unit_B700 realizes various processes in the UPF by reading and executing various programs stored in the memory unit_B740 as necessary.
  • the network connection unit_B720 is a functional unit that enables the UPF to connect to a base station device (gNB) and/or SMF and/or DN in the 5G AN.
  • 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 in the 5G AN.
  • the UPF in the 5GCN can communicate with a gNB via the N3 interface, can communicate with an SMF via the N4 interface, can communicate with a DN via the N6 interface, and can communicate with other UPFs via the N9 interface, by using the network connection unit_A620.
  • the memory unit_B740 is a functional unit for storing programs, user data, control information, etc. required for each operation of the UPF.
  • the UPF has functions such as acting as an anchor point for intra-RAT or inter-RAT mobility, acting as an external PDU session point for interconnecting to DNs (i.e., as a gateway between DN and core network_B and forwarding user data), routing and forwarding packets, a UL CL (Uplink Classifier) function that supports the routing of multiple traffic flows to one DN, a Branching point function that supports multi-homed PDU sessions, QoS (Quality of Service) processing for the user plane, verification of uplink traffic, buffering of downlink packets, and triggering Downlink Data Notification.
  • DNs i.e., as a gateway between DN and core network_B and forwarding user data
  • a UL CL Uplink Classifier
  • Branching point function that supports multi-homed PDU sessions
  • QoS Quality of Service
  • 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 may also have a function for converting non-IP communication and IP communication.
  • the 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.
  • the memory unit_740 may have a function of storing control information transmitted and received between the UE, the access network device, other core network devices, and the DN.
  • control information and control messages may be information that is pre-stored by the UE, and/or the base station, and/or the AMF, and/or the SMF, and/or a core network device/function other than the AMF and the SMF (e.g., the NSSF or the PCF, etc.), or some of these may be pre-stored and stored in conjunction with the transmission and reception of this control information.
  • a core network device/function other than the AMF and the SMF e.g., the NSSF or the PCF, etc.
  • the NSSF Network Slice Selection Function
  • NF Network Slice Selection Function
  • NSI Network Slice Instance
  • a PCF Policy Control Function
  • a PCF Policy Control Function
  • NW network
  • a function for providing policy rules to the CP function etc.
  • an NSACF Network Slice Admission Control Function
  • NS network slice
  • EPC Network Slice Admission Control Function
  • a function of monitoring and controlling the number of UEs having at least one PDU session and/or PDN connection per NS and/or a function of monitoring and controlling the number of PDU sessions established per NS.
  • some or all of the function of disclosing information related to network energy 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 a NF other than these.
  • the NF may be, for example, an NF referred to as an Energy Efficiency Function (EEF, also referred to as an energy efficiency function), Energy Efficiency Management Function (EEMF, also referred to as an energy efficiency management function), Energy Consumption Function (ECF, also referred to as an energy consumption function), Energy Consumption Management Function (ECMF, also referred to as an energy consumption management function), Energy Saving Function (ESF, also referred to as an energy saving function), Energy Saving Management Function (ESMF, also referred to as an energy saving management function), Energy Efficiency and Energy Saving Function (EEESF, also referred to as an energy efficiency and energy saving function), Energy Efficiency and Energy Saving Management Function (EEESMF, also referred to as an energy efficiency and energy saving management function), etc.
  • EEF Energy Efficiency Function
  • EMF Energy Efficiency Management Function
  • EMF Energy Saving Function
  • EESMF Energy Efficiency and Energy Saving Function
  • EESMF Energy Efficiency and Energy Saving Management Function
  • Energy Consumption can be the amount of energy used to achieve a particular system.
  • the units can be expressed in joules or watt-hours.
  • Energy Efficiency can also be the relationship between energy consumption and useful output.
  • Energy Saving can mean saving energy or reducing EC.
  • Energy Efficiency and Energy Saving may be a concept that includes EC, and/or EE, and/or ES.
  • EC, EE, ES, and EEES may be interchanged.
  • EC used in this specification may be replaced with EE, ES, and EEES.
  • network energy related information exposure and/or EE, and/or EC, and/or ES, and/or EEES, and/or CE, and/or RE do not need to 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, and these functions may be applied to other services.
  • V2X Vehicle-to-Everything
  • A2X Aircraft-to-Everything
  • A2X services Aircraft-to-Everything
  • the user plane refers to user data transmitted and received between the UE and the 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.
  • 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.
  • 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 be expressed as the U-Plane.
  • the control plane refers to control messages sent and received to control UE communications, etc.
  • the CP may be a communication path for sending and receiving control messages, and may be composed of multiple bearers.
  • the CP may be sent and received using a NAS (Non-Access-Stratum) signaling connection between the UE and the MME.
  • the CP may be sent and received using a NAS (Non-Access-Stratum) signaling connection between the UE and the AMF.
  • the CP may be sent and received using the LTE-Uu interface and the S1-MME interface.
  • the CP may be sent and received using the interface between the UE and the NG RAN and the N2 interface.
  • the CP may be expressed as the control plane or the C-Plane.
  • the SM procedure (also referred to as the procedure for SM) may include a UE-initiated PDU session establishment procedure, a UE- or SMF- (or network-) initiated PDU session modification procedure, and a UE-requested PDU session release procedure, which is initiated by the UE or SMF- (or network).
  • the UE sends a PDU session establishment request message to the SMF, and upon receiving this, the SMF may send a PDU session establishment accept message or a PDU session establishment reject message to the UE.
  • the SMF may send a PDU session establishment accept message, and when it does not accept it, it may send a PDU session establishment reject message.
  • the UE sends a PDU session modification request message to the SMF, and the SMF that receives this may either execute the SMF-initiated PDU session modification procedure or send a PDU session modification reject message to the UE.
  • the SMF acknowledges the PDU session modification request from the UE, it may execute the SMF-initiated PDU session modification procedure, and when it does not acknowledge it, it may send a PDU session modification reject message.
  • the SMF sends a PDU session modification command message to the UE, and the UE that receives this may send a PDU session modification complete message or a PDU session modification command reject message to the SMF.
  • the UE may send a PDU session modification complete message when it accepts the PDU session modification instruction from the SMF, or send a PDU session modification command reject message when it does not accept it.
  • the UE sends a PDU session release request message to the SMF, and the SMF that receives this may either execute the SMF-initiated PDU session release procedure or send a PDU session release reject message to the UE.
  • the SMF acknowledges the PDU session release request from the UE, it may execute the SMF-initiated PDU session release procedure, and when it does not acknowledge it, it may send a PDU session release reject message.
  • 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.
  • 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 a NAS message (also called a NAS MM message).
  • 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 in an SM procedure, or may be a NAS message (also referred to as a NAS SM message).
  • NAS Non-Access-Stratum
  • the MM procedure (also referred to as the 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).
  • the UE sends a registration request message to the AMF, and upon receiving this, the AMF may send a registration accept message or a registration reject message to the UE.
  • the AMF may send a registration accept message when it accepts the registration request from the UE, or may send a registration reject message when it does not accept it.
  • the UE may send a deregistration request message to the AMF, and upon receiving this, the AMF may send a deregistration accept message to the UE.
  • 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.
  • the AMF sends a configuration update command message to the UE, and the UE that receives this may send a configuration update complete message to the AMF.
  • the UE sends a service request message to the AMF, and the AMF that receives this may send a service accept message or a service reject message to the UE.
  • the AMF may send a service accept message when it accepts the service request from the UE, and may send a service reject message when it does not accept it.
  • 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.
  • a paging request (Request Paging)
  • the base station that receives this sends a paging message to the UE
  • the UE that receives this may send a service request message or a registration request message to the AMF.
  • 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.
  • 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 a NAS message (also called a NAS MM message).
  • the 5GS (5G System) service may be a connection service provided using the core network_B190.
  • the 5GS service may be a service different from the EPS service, or may be a service similar to the EPS service.
  • non-5GS services may be services other than 5GS services and may include EPS services and/or non-EPS services.
  • 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 it may also be connectivity established between a UE and an external gateway.
  • a UE can transmit and receive user data between a DN and the DN using a PDU session by establishing a PDU session via an access network _B and a core network _B.
  • this external gateway may be a UPF, a SCEF, etc.
  • a UE can transmit and receive user data between a device such as an application server located in a DN and the DN using a PDU session.
  • each device may associate and manage one or more identification information with a PDU session.
  • this 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, and may further include other information.
  • each identification information associated with a PDU session may be the same or different.
  • the DNN may be identification information that identifies the core network and/or an external network such as a DN. Furthermore, the DNN may 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).
  • APN Access Point Name
  • 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 sent and received using IPv4. If IPv6 is specified, it indicates that data will be sent and received using IPv6. If Ethernet is specified, it indicates that Ethernet frames will be sent and received. Ethernet may also indicate that communication using IP is not performed. If Unstructured is specified, it indicates that data will be sent 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 when the UE is capable of using both IPv4 and IPv6.
  • a PLMN Public land mobile network
  • a PLMN is a communication network that provides mobile wireless communication services.
  • a PLMN is a network managed by an operator, which is a telecommunications carrier, and the operator can be identified by the PLMN ID.
  • a PLMN that matches the MCC (Mobile Country Code) and MNC (Mobile Network Code) of the UE's IMSI (International Mobile Subscriber Identity) may be a Home PLMN (HPLMN).
  • the UE may hold an Equivalent HPLMN list in the USIM to identify one or more EPLMNs (Equivalent HPLMNs).
  • a PLMN that is different from the HPLMN and/or EPLMN may be a Visited PLMN (VPLMN).
  • VPLMN Visited PLMN
  • a PLMN to which the UE has successfully registered may be a Registered PLMN (RPLMN).
  • RPLMN Registered PLMN
  • PLMN services services provided by PLMNs
  • SNPNs services provided by SNPNs
  • a network slice is a logical network that provides specific network capabilities and network characteristics.
  • a UE and/or a network can support network slices (NW slices; NS).
  • NW slices; NS network slices
  • a network slice may also be simply referred to as a slice.
  • a network slice instance is composed of an instance (entity) of a network function (NF) and a set of required resources, and forms a deployed network slice.
  • an NF is a processing function in a network, adopted or defined by 3GPP.
  • An NSI is an entity of an NS, of which one or more are configured in a core network_B.
  • An NSI may also be composed of a virtual NF (Network Function) generated using an NST (Network Slice Template).
  • NST Network Slice Template
  • an NST is associated with a resource requirement for providing a required communication service or capability, and is a logical representation of one or more NFs.
  • an NSI may be a collection in a core network_B190 composed of multiple NFs.
  • An NSI may also be a logical network configured to separate user data delivered by a service, etc.
  • An NS may be configured with one or more NFs.
  • An NF configured in an NS may or may not be a device shared with other NSs.
  • a UE and/or a device in the network may be assigned to one or more NSs based on registration information such as an NSSAI and/or an S-NSSAI and/or a UE usage type and/or one or more NSI IDs and/or an APN.
  • the UE usage type is a parameter value included in the UE registration information 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.
  • S-NSSAI Single Network Slice Selection Assistance Information
  • S-NSSAI may consist of only SST (Slice/Service type) or may consist of SST and SD (Slice Differentiator).
  • SST is information indicating the expected behavior of an NS in terms of functions and services.
  • SD may be information for interpolating SST when selecting one NSI from multiple NSIs indicated by SST.
  • 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 a UE as a default S-NSSAI. In addition, when S-NSSAI is the default S-NSSAI, if the UE does not send a valid S-NSSAI to the network in the registration request message, the network may provide the NS related to the UE.
  • NSSAI Network Slice Selection Assistance Information
  • 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.
  • the NSSAI may also be information used to select an AMF.
  • the configured NSSAI (also referred to as configured NSSAI) is an NSSAI 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 the S-NSSAI and the mapped S-NSSAI.
  • the requested NSSAI (also called the Requested NSSAI) is an NSSAI provided by 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.
  • the requested NSSAI may be information indicating the network slice that the UE wishes to access.
  • the S-NSSAI included in the requested NSSAI may be expressed as the requested S-NSSAI.
  • the requested NSSAI is transmitted included in an NAS message or a Radio Resource Control (RRC) message including a Non-Access-Stratum (NAS) message transmitted from the UE to the network, such as a registration request message or a PDU session establishment request message.
  • RRC Radio Resource Control
  • NAS Non-Access-Stratum
  • 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.
  • the allowed NSSAI is information that identifies the network slice to which the network has permitted 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.
  • the 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., when roaming).
  • the mapped S-NSSAI may basically be the S-NSSAI used when the UE is roaming, or may be the S-NSSAI that is not used when the UE is not roaming (also referred to as when not roaming).
  • the UE may store one or more mapped S-NSSAIs that are mapped to the configured NSSAI and the S-NSSAI included in the Allowed NSSAI of 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.
  • the rejected NSSAI (also referred to as the rejected NSSAI) is information indicating one or more network slices to which the UE is not permitted.
  • the rejected NSSAI is information identifying a network slice to which the network does not permit the UE to connect.
  • the 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 a rejection reason).
  • the rejection reason value is information indicating the reason why the network rejects the 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.
  • the rejected NSSAI may be included in an NAS message sent from the network to the UE, such as a registration acceptance message, a configuration update command, or a registration rejection message, or an RRC message including a NAS message.
  • the S-NSSAI included in the rejected NSSAI may be expressed as the rejected S-NSSAI.
  • rejected NSSAI may mean any of the first to fifth rejected NSSAIs.
  • rejected S-NSSAI may mean rejected S-NSSAI included in any of the first to fifth rejected NSSAIs, and these may be called rejected S-NSSAIs.
  • S-NSSAI included in rejected NSSAI may be expressed as rejected S-NSSAI.
  • Rejected S-NSSAI may be composed of S-NSSAI and mapped S-NSSAI.
  • the first rejected NSSAI may be a rejected NSSAI for the current PLMN or SNPN (also referred to as a rejected NSSAI for the current PLMN or SNPN).
  • the first rejected NSSAI may be an NSSAI that is not available in the current PLMN or SNPN.
  • the first rejected NSSAI may also be a set of one or more S-NSSAIs that are not available in the current PLMN or SNPN among the S-NSSAIs included in the requested NSSAI by the UE.
  • the first rejected NSSAI may also be a set of S-NSSAIs included in the requested NSSAI sent from the UE and sent from the AMF together with a rejection reason value (also referred to as a reason value) indicating that the S-NSSAI is not available in the current PLMN or SNPN.
  • a rejection reason value also referred to as a reason value
  • the second rejected NSSAI may also be a rejected NSSAI for the current RA (also referred to as a rejected NSSAI for the current registration area).
  • the second rejected NSSAI may be an NSSAI that is not available in the current RA.
  • the second rejected NSSAI may also 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 also 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.
  • the third rejected NSSAI may also be a rejected NSSAI for the failed or revoked NSSAA (also referred to as 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 that the S-NSSAI is not available due to the NSSAA having failed or been revoked.
  • 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 the S-NSSAI has failed or been revoked.
  • the fourth rejected NSSAI may also be a rejected NSSAI for the maximum number of UEs reached (also referred to as a rejected NSSAI for the maximum number of UEs reached).
  • the fourth rejected NSSAI may also be a set of S-NSSAIs sent from the AMF, which are S-NSSAIs included in the requested NSSAI sent from the UE, together with a reason value indicating that the S-NSSAI is not available because the maximum number of UEs has been reached.
  • the fourth rejected NSSAI may also be information including one or more S-NSSAIs for which the maximum number of UEs per network slice has been reached.
  • the fifth rejected NSSAI may also be a rejected NSSAI including an S-NSSAI 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 functionality.
  • the fifth rejected NSSAI may also be a set of S-NSSAIs included in a 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 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 with a reason value that the S-NSSAI is not available for 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 or a predetermined threshold.
  • the first to fifth rejected NSSAIs may be stored in the UE and/or NF (AMF and/or NSACF and/or NSSF and/or PCF and/or OAM and/or new NF) as separate rejected NSSAIs or as a common rejected NSSAI.
  • AMF and/or NSACF and/or NSSF and/or PCF and/or OAM and/or new NF may be stored in the UE and/or NF (AMF and/or NSACF and/or NSSF and/or PCF and/or OAM and/or new NF) as separate rejected NSSAIs or as a common rejected NSSAI.
  • a pending NSSAI (also referred to as a Pending NSSAI) is a collection of one or more S-NSSAIs that are S-NSSAIs for which the network requires network slice specific authentication, for which network slice specific authentication has not been completed and which are not available for use in the current PLMN.
  • 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 sent 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.
  • the pending NSSAI may be information including one or more combinations of an S-NSSAI and a rejection reason value.
  • the rejection reason value in this case 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.
  • the pending NSSAI is valid for the entire registered PLMN.
  • 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.
  • 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.
  • the pending NSSAI is an NSSAI consisting of one or more S-NSSAIs that identify slices for which the UE is pending a procedure. Specifically, while the UE stores the pending NSSAI, the UE 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 pending for the 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.
  • 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.
  • a TA may be a range in which control messages such as paging are broadcast, or a range in which UE_A10 can move without performing a handover procedure.
  • a TA may be a routing area, a location area, or anything similar.
  • a TA may be identified by a Tracking Area Identity (TAI) consisting of a PLMN Identifier (PLMN ID) and a Tracking Area Code (TAC).
  • TAI Tracking Area Identity
  • PLMN ID PLMN ID
  • TAC Tracking Area Code
  • 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).
  • MCC is an identifier used to identify the country in which the UE is addressed
  • MNC is an identifier used to identify the HPLMN in the country in which the UE is addressed.
  • TAC is an identifier used to identify a TA in a PLMN.
  • a registration area (also called a registration area, RA) is a collection of one or more TAs that the AMF assigns to a UE. Note that while UE_A10 is moving within one or more TAs included in the RA, it may be able to move without sending or receiving signals for TA update. In other words, an 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.
  • the UE ID is information for identifying a UE.
  • the UE ID may be a SUCI (SUbscription Concealed Identifier), or a SUPI (Subscription Permanent Identifier), or a GUTI (Globally Unique Temporary Identifier), or an IMEI (International Mobile Subscriber Identity), or an IMEISV (IMEI Software Version), or a TMSI (Temporary Mobile Subscriber Identity).
  • the UE ID may be other information set within an application or network.
  • the UE ID may be information for identifying a user.
  • NSSAA Network Slice-Specific Authentication and Authorization
  • PLMNs and network devices with NSSAA functionality can perform NSSAA procedures for a certain S-NSSAI based on the UE's registration information.
  • UEs with NSSAA functionality can manage and store rejected NSSAIs for pending NSSAA and/or rejected NSSAIs for failed NSSAA.
  • NSSAA may be referred to as network slice-specific authentication and authorization procedures or authentication and authorization procedures.
  • the S-NSSAI that requires an NSSAA is an S-NSSAI that requires an NSSAA and is managed by the core network and/or core network device.
  • the core network and/or core network device may store the S-NSSAI that requires an NSSAA by associating the S-NSSAI with information indicating whether or not an NSSAA is required.
  • the core network and/or core network device may further store the S-NSSAI that requires an NSSAA with information indicating whether or not the NSSAA has been completed, or information indicating that the NSSAA has been completed and is permitted or successful, in association with each other.
  • the core network and/or core network device may manage the S-NSSAI that requires an NSSAA as information unrelated to the access network.
  • 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 register to either 5GC or EPC, when moving between EPC and 5GC, mapping between EPS-GUTI (also called 4G-GUTI) and 5G-GUTI is required.
  • EPS-GUTI also called 4G-GUTI
  • a UE in dual registration mode may be in a state where it can register independently to 5GC and EPC.
  • a UE in dual registration mode can maintain 5G-GUTI and EPS-GUTI (also called 4G-GUTI) independently.
  • the first identification information may also be a requested NSSAI (also referred to as a requested NSSAI IE (Information Element)).
  • the first identification information may also include one or more S-NSSAI indicating a network slice requested by the UE.
  • the first identification information may also include an S-NSSAI included in the 11th identification information, the 15th identification information, the 31st identification information, or the 35th identification information.
  • the second identification information may also be information indicating the capabilities of the UE (UE capability).
  • the second identification information may also be information included in 5GMM capability (also referred to as 5GMM capability IE).
  • the second identification information may also be information indicating whether the UE supports some or all of the functions of network energy related information exposure (also referred to as Network energy related information exposure), and/or Energy Efficiency (also referred to as EE), and/or Energy Consumption (also referred to as EC), and/or Energy Saving (also referred to as ES), and/or Energy Efficiency and Energy Saving (also referred to as EEES), and/or Carbon Emission (also referred to as CE), and/or Renewable Energy (also referred to as RE).
  • network energy related information exposure also referred to as Network energy related information exposure
  • EE Energy Efficiency
  • EC Energy Consumption
  • ES Energy Saving
  • EEES Energy Efficiency and Energy Saving
  • CE Carbon Emission
  • RE Renewable Energy
  • the third identification information may also be information indicating the type of registration requested.
  • the third identification information may also be information included in the 5GS registration type (also referred to as the 5GS registration type IE).
  • the third identification information may also indicate network energy related information exposure, and/or EE, and/or EC, and/or ES, and/or EEES, and/or CE, and/or RE.
  • the fourth identification information may be information that includes at least one of the first to third identification information.
  • transmitting and receiving at least one of the first to third identification information may be equivalent to transmitting and receiving the fourth identification information.
  • transmitting and receiving at least one of the first to third identification information may mean transmitting and receiving the fourth identification information
  • transmitting and receiving the fourth identification information may mean transmitting and receiving at least one of the first to third identification information.
  • the 11th identification information may be an NSSAI.
  • the 11th 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).
  • the 11th identification information may include one or more S-NSSAIs indicating network slices transmitted from the NW.
  • the 11th identification information may include an S-NSSAI included in the first identification information, or an S-NSSAI not included in the first identification information.
  • the 11th identification information may include an S-NSSAI not included in the 15th identification information.
  • 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.
  • 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 upper limit or a predetermined threshold has been exceeded.
  • 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. Furthermore, the 11th identification information may be the fifth rejected NSSAI. Furthermore, the 11th identification information may be an NSSAI that includes the fifth rejected S-NSSAI. Furthermore, the 11th identification information may include the 13th identification information, and/or the 14th identification information, and/or the 15th identification information.
  • the 12th identification information may be information indicating network capability (NW capability).
  • the 12th identification information may be information included in 5GS (5G System) network feature support (also referred to as 5GS network feature support IE).
  • the 12th 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.
  • the 13th identification information may be a timer (also called a backoff timer) value.
  • the 13th identification information may be a timer value corresponding to the 11th identification information.
  • 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.
  • the 13th identification information may be a timer value corresponding to the S-NSSAIs included in the 11th identification information.
  • the corresponding timer value indicated by the 13th identification information may be applied to each S-NSSAI included in the 11th identification information.
  • the 14th identification information may also be a reason value indicating that the UE request is rejected.
  • the 14th 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.
  • this S-NSSAI may be the S-NSSAI included in the first identification information or the 11th identification information.
  • the 14th identification information may also indicate that the PDU session has reached an upper limit or threshold of energy consumption.
  • the 14th identification information may also indicate that the PDU session in the S-NSSAI indicated by the first identification information or the 11th identification information has reached an upper limit or threshold of energy consumption.
  • the 14th 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.
  • the 14th identification information may also indicate information indicating quantities 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.
  • the 14th identification information may indicate information indicating current energy consumption and/or future energy consumption.
  • the 15th identification information may be one or more S-NSSAIs.
  • the 15th 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.
  • the 15th identification information may include one or more S-NSSAIs indicating a network slice transmitted from the NW.
  • the 15th 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.
  • the 15th identification information may include an S-NSSAI not included in the 11th identification information.
  • the 15th identification information may be referred to as an alternative S-NSSAI.
  • the 16th identification information may be information that includes at least one of the 11th to 15th identification information.
  • transmitting and receiving at least one of the 11th to 15th identification information may be equivalent to transmitting and receiving the 16th identification information.
  • transmitting and receiving at least one of the 11th to 15th identification information may mean transmitting and receiving the 16th identification information
  • transmitting and receiving the 16th identification information may mean transmitting and receiving at least one of the 11th to 15th identification information.
  • the 21st identification information may be an S-NSSAI.
  • 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.
  • 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.
  • the 22nd identification information may be information indicating the capabilities of the UE (UE capability).
  • the second identification information may be information included in the 5GSM capability (also referred to as the 5GSM capability IE).
  • 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.
  • the 23rd identification information may be S-NSSAI.
  • the 23rd identification information may be the same as the 11th identification information, or may be the same as the 15th identification information.
  • the 24th identification information may be information that includes at least one of the 21st to 23rd identification information.
  • transmitting and receiving at least one of the 21st to 23rd identification information may be equivalent to transmitting and receiving the 24th identification information.
  • transmitting and receiving at least one of the 21st to 23rd identification information may mean transmitting and receiving the 24th identification information
  • transmitting and receiving the 24th identification information may mean transmitting and receiving at least one of the 21st to 23rd identification information.
  • the 31st identification information may be an S-NSSAI.
  • the 31st identification information may include one or more S-NSSAIs indicating network slices for which the NW permits or rejects the establishment of a PDU session.
  • the 31st 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.
  • the 31st identification information may be an S-NSSAI that is not included in the 35th identification information.
  • the 31st identification information may also 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 and is unavailable.
  • the 31st identification information may also 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 and is unavailable because the upper limit value or a predetermined threshold has been exceeded.
  • the 31st identification information may also 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. Additionally, the 31st identification information may include the 33rd identification information, and/or the 34th identification information, and/or the 35th identification information.
  • the 32nd identification information may also be information indicating network capability (NW capability).
  • the 32nd identification information may also be information included in 5GSM (5G Session Management) network feature support (also referred to as 5GSM network feature support IE).
  • the 32nd identification information may also 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.
  • the 33rd identification information may be a timer (also referred to as a backoff timer) value.
  • the 33rd identification information may be a timer value corresponding to the 31st identification information.
  • 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, there may be only one 33rd identification information, and one timer value indicated by the 33rd identification information may be applied to all S-NSSAIs included in the 31st identification information.
  • the 33rd identification information may be a timer value corresponding to the S-NSSAIs included in the 31st identification information.
  • the corresponding timer value indicated by the 33rd identification information may be applied to each S-NSSAI included in the 31st identification information.
  • the 34th identification information may also be a reason value indicating that the UE request is rejected.
  • 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.
  • 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 the PDU session has reached an upper limit or threshold of energy consumption.
  • the 34th identification information may also indicate that the 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. Additionally, the 34th identification information may 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.
  • the 34th identification information may also indicate information indicating quantities 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.
  • the 34th identification information may indicate information indicating current energy consumption and/or future energy consumption.
  • the 35th identification information may be one or more S-NSSAIs.
  • 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.
  • the 35th identification information may include one or more S-NSSAIs indicating a network slice transmitted from the NW.
  • 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.
  • the 35th identification information may include an S-NSSAI not included in the 31st identification information.
  • the 35th identification information may be referred to as an alternative S-NSSAI.
  • the 36th identification information may be information that includes at least one of the 31st to 35th identification information.
  • transmitting and receiving at least one of the identification information from the 31st to the 35th may be equivalent to transmitting and receiving the 36th identification information.
  • transmitting and receiving at least one of the identification information from the 31st to the 35th may mean transmitting and receiving the 36th identification information
  • transmitting and receiving the 36th identification information may mean transmitting and receiving at least one of the identification information from the 31st to the 35th.
  • the HSS and UDM, PCF and PCRF, SMF and PGW-C, and UPF and PGW-U are each configured as the same device/function (i.e., the same physical hardware, or the same logical hardware, or the same software).
  • the contents described in this embodiment are also applicable to cases where these are configured as different devices/functions (i.e., different physical hardware, or different logical hardware, or different software).
  • data may be sent and received directly between them, or data may be sent and received via the N26 interface between the AMF and MME, or data may be sent and received via the UE.
  • the registration procedure is a procedure for the UE to take the initiative in registering to the access network_B, and/or the core network_B, and/or the DN. If the UE is not registered to the network, it can execute this procedure at any timing, such as when the power is turned on. In other words, if the UE is in a non-registered state (5GMM-DEREGISTERED state), it can start this procedure at any timing. Furthermore, each device (particularly the UE and the AMF) can transition to a registered state (5GMM-REGISTEDED 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 non-registered state) for 3GPP access and the registration state for non-3GPP access.
  • the registration procedure may be a procedure for updating the location registration information of the UE in the network and/or for periodically notifying the network of the status of the UE from the UE and/or for updating certain parameters related to the UE in the network.
  • the UE may initiate the registration procedure when it moves to a TA outside the current registration area. In other words, the UE may initiate the registration procedure when it moves to a TA different from the TA indicated in the TA list it holds. Furthermore, the UE may initiate the registration procedure when it is necessary to update the context of each device due to disconnection or invalidation of a PDU session. Furthermore, the UE may initiate the registration procedure when there is a change in the capability information and/or preferences regarding the establishment of the UE's PDU session. Furthermore, the UE may initiate the registration procedure periodically. Furthermore, the UE may initiate the registration procedure based on the completion of the registration procedure, the completion of the PDU session establishment procedure, or information received from the network in each procedure. Furthermore, the UE may initiate this procedure after performing the procedure in Chapter 3 one or more times. Note that the UE can execute the registration procedure at any timing, not limited to these.
  • 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.
  • PLMN HPLMN or VPLMN
  • SNPN SNPN
  • SNPN SNPN
  • ON-SNPN ON-SNPN
  • SO-SNPN SO-SNPN
  • the procedure for the UE to transition from a state in which it is not registered in the network (unregistered state) to a state in which it is registered (registered state) may be an initial registration procedure or a registration procedure for initial registration.
  • the registration procedure performed 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.
  • the UE may or may not store each NSSAI and/or S-NSSAI contained in each NSSAI described in Chapter 2.6 at the time of initiating this procedure.
  • the UE may also 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.
  • the UE may also execute this procedure one or more times after storing each NSSAI and/or S-NSSAI contained in each NSSAI acquired from the network by executing this procedure.
  • the UE starts the registration procedure by transmitting a NAS message including a registration request message to the AMF via 3GPP access or non-3GPP access (S600) (S602) (S604).
  • the UE transmits an RRC message including a NAS message including a registration request message to a base station device (also referred to as a 5G AN or gNB) (S600).
  • the registration request message is a NAS message transmitted and received on the N1 interface.
  • the RRC message may be a control message transmitted and received between the UE and the base station device.
  • the NAS message is processed in the NAS layer, and the RRC message is processed in the RRC layer.
  • the NAS layer is a layer higher than the RRC layer.
  • the UE may transmit at least one of the first to fourth identification information in a registration request message and/or a NAS message and/or an RRC message.
  • the first to fourth identification information may be as described in Chapter 2.6.
  • the UE may indicate that the UE supports each function, may indicate a request from the UE, or may indicate the information indicated by each identification information to the network.
  • the UE may select and decide whether or not to transmit at least one of the first to fourth pieces of identification information to the network based on the UE's capability information, and/or the UE policy, and/or the UE's state, and/or the user's registration information, and/or the context held by the UE, and/or the identification information transmitted or received in a procedure executed prior to this procedure, etc.
  • the UE may include a second identification indicating that it supports 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 in the registration request message and/or NAS message.
  • the UE may also include a third identification indicating 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 register or perform registration procedures relating to network energy related information exposure, and/or EE, and/or EC, and/or ES, and/or EEES, and/or CE, and/or RE.
  • a third identification indicating 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 the S-NSSAI included in the 11th identification information in the first identification information.
  • the 11th identification information is an allowed NSSAI and/or a configured NSSAI including one or more S-NSSAIs
  • the UE may include one or more of those S-NSSAIs in the first identification information.
  • the 11th 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 of those S-NSSAIs in the first identification information.
  • the UE may include the S-NSSAI indicated by the 15th identification information in the first 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.
  • the UE does not need to include the S-NSSAI contained in the 11th identification information in the first identification information.
  • the UE may include the S-NSSAI included in the 15th identification information in the first identification information.
  • the UE 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 first identification information.
  • the UE 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 in 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 included in the 11th identification information in the first identification information.
  • the UE may include the S-NSSAI indicated in the 31st identification information in the first identification information.
  • the UE may include the S-NSSAI indicated by the 35th identification information in the first 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.
  • the UE 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 first identification information.
  • the UE may include the S-NSSAI included in the 35th identification information in the first identification information.
  • the UE 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 included in the 31st identification information in the first identification information.
  • the UE 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 in 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.
  • a control message such as a PDU session change command or a setting update command
  • the UE may determine whether to include the S-NSSAI included in the 11th identification information in the first identification information based on the current energy consumption or future energy consumption indicated in the 14th identification information for the S-NSSAI included in the 11th identification information. For example, the UE may not include the S-NSSAI included in the 11th identification information in the first identification information when the current energy consumption or future energy consumption indicated in the 14th identification information exceeds a predetermined value. In addition, the UE may include the S-NSSAI included in the 11th identification information in the first identification information when the current energy consumption or future energy consumption indicated in the 14th identification information does not exceed a predetermined value.
  • 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 in the 34th identification information for the S-NSSAI included in the 31st identification information. For example, the UE may not include the S-NSSAI included in the 31st identification information in the first identification information when the current energy consumption or future energy consumption indicated in the 34th identification information exceeds a predetermined value. In addition, the UE may include the S-NSSAI included in the 31st identification information in the first identification information when the current energy consumption or future energy consumption indicated in the 34th identification information does not exceed a predetermined value.
  • two or more of these pieces of identification information may be configured as one or more pieces of identification information.
  • the information indicating support for each function and the information indicating a request to use each function may be transmitted and received as the same identification information, or may be transmitted and received as different identification information.
  • the base station device when the base station device receives an RRC message including a NAS message including a registration request message, it 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 and/or 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, it 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 a network function corresponding to the UE capability information indicated by the second identification information.
  • the base station device may also select an AMF that supports a network function corresponding to the 5GS registration type (also referred to as a registration type) indicated by the third identification information.
  • the method for selecting AMF is not limited to this, and the base station device may select AMF based on other conditions.
  • the AMF when the AMF receives a registration request message or the like from the base station device, it can execute a first condition determination.
  • the first condition determination is for determining whether or not the network accepts the UE's request.
  • the AMF determines that the first condition determination is true, it may execute the procedures from S610 to S612. Also, when the AMF determines that the first condition determination is false, it may execute the procedure of S610.
  • 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 included in a NAS message and transmitted.
  • the NAS message may be included in an RRC message and transmitted.
  • the first condition determination may be performed based on the reception of a registration request message or the like received from a base station device, and/or the identification information contained in the registration request message or the like, 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.
  • the first condition determination may be determined to be true, and if the network does not permit or reject the UE's request, the first condition determination may be determined to be false. If the network does not permit or reject a part of the UE's request, the first condition determination may be determined to be true. If the network does not permit or reject all of the UE's request, the first condition determination may be determined to be false. 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 to be true, and if the network does not support the function requested by the UE, the first condition determination may be determined to be false. Furthermore, if the received identification information is permitted, the first condition determination may be determined to be true, and if the received identification information is not permitted, the first condition determination may be determined to be false.
  • the first condition determination may be performed by a network function (also referred to as NF) other than the AMF.
  • NF network function
  • 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).
  • 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 the identification information and/or control message to be sent to the UE based on the result of the first condition determination received from the NF.
  • 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.
  • the AMF may also request the NSACF and/or NSSF and/or PCF and/or OAM and/or new NF to check 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 has been reached.
  • 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 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
  • 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 may be transmitted.
  • the AMF does not need to transmit these control information to the NSACF and/or NSSF and/or PCF and/or OAM and/or new NF.
  • the AMF does not have to transmit this control information to the NSACF and/or the NSSF and/or the PCF and/or the OAM and/or the new NF.
  • the NSACF and/or NSSF and/or PCF and/or OAM and/or new NF receiving these control information from the AMF may confirm or determine 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 has been reached.
  • This confirmation or determination may or may not be made for each access type.
  • the NSACF and/or NSSF and/or PCF and/or OAM and/or new NF may not 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 Vehicle-to-Everything (V2X) and/or V2X services and/or Aircraft-to-Everything (A2X) and/or A2X services and/or emergency services.
  • V2X Vehicle-to-Everything
  • A2X Aircraft-to-Everything
  • the NSACF and/or NSSF and/or PCF and/or OAM and/or new NF may provide a UE ID, and/or 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 indicating that the upper limits or thresholds have been reached.
  • the AMF may transmit control 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 per NS has reached an upper limit or threshold, 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 has reached an upper limit or threshold.
  • these control information may be transmitted in the 14th identification information.
  • 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 in the 11th identification information. Furthermore, the NSACF and/or NSSF and/or PCF and/or OAM and/or new NF may transmit to the AMF an S-NSSAI (alternative S-NSSAI) replacing the S-NSSAI that has reached these upper limits or thresholds. This S-NSSAI may be transmitted in the 15th identification information. Furthermore, the NSACF and/or NSSF and/or PCF and/or OAM and/or new NF may transmit to the AMF a timer (back-off timer) value for the S-NSSAI that has reached these upper limits or thresholds. This timer value may be transmitted in the 13th identification information. Furthermore, 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 transmit the access type (corresponding to the access that transmitted the registration request message).
  • S-NSSAI alternative S-NSSAI replacing the S-NSSAI that
  • the NSACF and/or NSSF and/or PCF and/or OAM and/or new NF may send a notification indicating that the UE ID, and/or 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 have not reached the upper limits or thresholds.
  • the AMF may transmit control 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 per NS has not reached the upper limit or threshold, 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 has not reached the upper limit or threshold.
  • 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 sent the registration request message).
  • 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 the other access type (e.g., non-3GPP access).
  • one access type e.g., 3GPP access
  • the other access type e.g., non-3GPP access
  • the exchange of control information between these AMFs and the NSACF and/or NSSF and/or PCF and/or OAM and/or new NF may be performed by one or more procedures.
  • all of the above exchanges may be performed by performing some of the above exchanges between the AMF and the NSACF and/or NSSF and/or PCF and/or OAM and/or new NF, and performing the remaining of the above exchanges between the AMF and the NSACF and/or NSSF and/or PCF and/or OAM and/or new NF.
  • the AMF may include at least one of the identification information items 11 to 16 in the control message and transmit the control message to the UE via the base station device.
  • the identification information items 11 to 16 may be as described in Chapter 2.6.
  • the AMF may indicate whether the network supports each function, may indicate whether the UE request has been accepted, or may indicate a combination of these.
  • two or more of these identification information items may be configured as one or more identification information items. 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.
  • the AMF may transmit a control message including at least one of the eleventh to sixteenth identification information.
  • the AMF may determine whether or not 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.
  • the AMF may also indicate to the UE that the UE's request has been accepted by sending a registration accept message, or may indicate to the UE that the UE's request has been rejected by sending a registration reject message.
  • the AMF may include a 12th identification information in the control message and/or NAS message 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.
  • the AMF may include in the control message and/or NAS message a 12th 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 AMF may not include the 13th identification, and/or the 14th identification, and/or the 15th identification in the control message and/or NAS message.
  • the AMF also receives from the NSACF and/or NSSF and/or PCF and/or OAM and/or the 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 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 not reached an upper limit or threshold, and/or the number of network energy
  • 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 has not reached an upper limit or threshold is received, the 11th identification information and/or the 12th identification information may be transmitted.
  • the AMF also receives from the NSACF and/or NSSF and/or PCF and/or OAM and/or the 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 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 or threshold, and/or the number of network energy related information exposures per NS.
  • control information indicating that the ion 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 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 has reached an upper limit or threshold
  • the 11th identification information and/or the 12th identification information and/or the 13th identification information and/or the 14th identification information and/or the 15th identification information may be transmitted.
  • the UE receives the control message (registration acceptance message or registration rejection message) and/or the transmitted identification information (at least one of the identification information items 11 to 16) via the base station device (S610).
  • the control message is a registration acceptance message
  • the UE may recognize, by receiving the registration acceptance message, that the UE's request via the registration request message has been accepted and/or the contents of the various identification information included in the registration acceptance message.
  • the control message is a registration rejection message
  • the UE may recognize, by receiving the registration rejection message, that the UE's request via the registration request message has been rejected and/or the contents of the various identification information included in the registration rejection message.
  • 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.
  • the UE may recognize and store the content of the received identification information.
  • the UE may also recognize and store, based on the reception of the 14th identification information, 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.
  • the UE may also recognize and store, based on receiving the 11th identification information and the 14th identification information, that the S-NSSAI indicated by the 11th identification information is unavailable based on the reason value indicated by the 14th identification information.
  • the UE may recognize and store, based on receiving the 11th identification information, the 13th identification information, and the 14th identification information, that the S-NSSAI indicated in the 11th identification information is unavailable based on the reason value indicated in the 14th identification information, and may start a timer using the timer value indicated in the 13th identification information.
  • the UE may recognize and store, when the timer has not expired, 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 registration procedures using that S-NSSAI are unavailable, and/or that PDU session establishment procedures using that S-NSSAI are unavailable, and/or that PDU session establishment using that S-NSSAI is unavailable.
  • the UE may recognize and store 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 can be established using that S-NSSAI.
  • an instruction from the network side e.g., a control message such as a configuration update command sent from the AMF to the UE
  • the UE may recognize and store 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 can be established using that S-NSSAI.
  • the UE may further transmit a registration completion message to the AMF via the base station device as a response message to the registration acceptance message (S612).
  • the registration completion message is a NAS message transmitted and received on the N1 interface, but may be transmitted and received between the UE and the base station device as part of an RRC message.
  • the AMF receives a registration completion message via the base station device (S612).
  • each device completes this procedure based on sending and receiving a registration acceptance message and/or a registration completion message. Furthermore, each device may recognize that this procedure has been successfully completed based on sending and receiving a registration acceptance message and/or a registration completion message.
  • each device may complete the registration procedure based on sending and receiving a registration rejection message. In addition, each device may recognize that the procedure was not completed normally or that the procedure was completed abnormally based on sending and receiving a registration rejection message.
  • each device may transition to or maintain a state in which the UE is registered in the network (RM_REGISTERED state or 5GMM-REGISTERED state) based on the transmission and reception of a registration acceptance message and/or a registration completion message. Furthermore, each device may transition to or maintain a state in which the UE is not registered in the network on the access on which the registration rejection message was received for the current PLMN (RM_DEREGISTERED state or 5GMM-DEREGISTERED state) based on the transmission and reception of a registration rejection message. Furthermore, the transition to each state of each device may be based on the transmission and reception of a registration completion message or the completion of the registration procedure.
  • 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, when transmitting and receiving information indicating that some of the UE's requests have been rejected, the device may recognize the reason why the UE's requests were rejected. Furthermore, each device may perform this procedure again based on the reason why the UE's request was rejected, or may perform the registration procedure for core network_A or another cell.
  • 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 upon completion of the registration procedure.
  • each device may store the information sent and received in this procedure in association with each other.
  • the UE may transmit a registration request message including a first S-NSSAI and UE capability information indicating that the UE supports an energy efficiency function, receive a registration acceptance message including the first S-NSSAI and 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 has reached an upper limit of energy consumption per network slice, and transmit a PDU session establishment request message together with the second S-NSSAI.
  • 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 deciding whether or not to start an MM procedure or SM procedure that is executed separately after the completion of this procedure.
  • PDU Session Establishment Procedure Next, the behavior of each device when the UE executes the PDU session establishment procedure will be described with reference to Fig. 7.
  • the PDU session establishment procedure may be referred to as this procedure.
  • the PDU session establishment procedure may also be an SM procedure.
  • This procedure may be performed after the registration procedure and/or PDU session establishment procedure have been performed one or more times.
  • 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.
  • S1400 3GPP access or non-3GPP access
  • 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.
  • the AMF may determine the SMF based on the NAS message received from the UE and/or the network status (S1402). Further, the AMF may forward the identification information included in the received PDU session establishment request message and/or NAS message to the selected SMF (S1404).
  • the UE may transmit a PDU session establishment request message based on receiving at least one of the identification information 11 to 16.
  • the UE may include at least one of the identification information items 21 to 24 in the PDU session establishment request message or NAS message and transmit it.
  • the UE may also include other identification information in the PDU session establishment request message or NAS message.
  • the UE may include the requested DNN or PDU session ID in the PDU session establishment request message or NAS message.
  • the UE may indicate that the UE supports each function, may indicate a request from the UE, or may indicate to the network the information indicated by each piece of identification information.
  • the UE may select and decide whether or not to transmit at least one of the identification information items 21 to 24 to the network based on the UE capability information, and/or the UE policy, and/or the UE state, and/or the user registration information, and/or the context held by the UE, and/or the identification information transmitted or received in a procedure executed prior to this procedure, etc.
  • the UE may include in the PDU session establishment request message and/or NAS message identification information 22 indicating that it supports 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.
  • 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.
  • the UE may recognize the meaning indicated by that identification information.
  • the UE may include the S-NSSAI included in the 11th identification information in the 21st identification information.
  • the 11th identification information is an allowed NSSAI and/or a configured NSSAI including one or more S-NSSAIs
  • the UE may include one or more of those S-NSSAIs in the 21st identification information.
  • the 11th 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 of those S-NSSAIs in the 21st identification information.
  • the UE may include the S-NSSAI indicated by the 15th identification information in the 21st 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.
  • the UE does not need to include the S-NSSAI contained in the 11th identification information in the 21st identification information.
  • the UE may include the S-NSSAI contained in the 15th identification information in the 21st identification information.
  • the UE does not need to include the S-NSSAI included in the 11th identification information in the 21st identification information.
  • the UE 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 in 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 included in the 11th identification information in the 21st identification information.
  • the UE may include the S-NSSAI indicated in the 31st identification information in the 21st identification information.
  • the UE may include the S-NSSAI indicated by the 35th identification information in the 21st 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.
  • the UE 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 first identification information.
  • the UE does not need to include the S-NSSAI contained in the 31st identification information in the 21st identification information.
  • the UE may include the S-NSSAI contained in the 35th identification information in the 21st identification information.
  • the UE 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.
  • the UE 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 in 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 21st identification information.
  • a control message such as a PDU session change command or a setting update command
  • 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 in the 14th identification information for the S-NSSAI included in the 11th identification information. For example, the UE may not include the S-NSSAI included in the 11th identification information in the 21st identification information when the current energy consumption or future energy consumption indicated in the 14th identification information exceeds a predetermined value. In addition, the UE may include the S-NSSAI included in the 11th identification information in the 21st identification information when the current energy consumption or future energy consumption indicated in the 14th identification information does not exceed a predetermined value.
  • 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 in the 34th identification information for the S-NSSAI included in the 31st identification information. For example, the UE may not include the S-NSSAI included in the 31st identification information in the 21st identification information when the current energy consumption or future energy consumption indicated in the 34th identification information exceeds a predetermined value. In addition, the UE may include the S-NSSAI included in the 31st identification information in the 21st identification information when the current energy consumption or future energy consumption indicated in the 34th identification information does not exceed a predetermined value.
  • the AMF 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.).
  • the AMF selects an SMF as a destination for transferring at least a portion of the information (message, container, information) contained in the NAS message received from the UE (S1402).
  • the AMF may select the SMF as the destination based on the information (message, container, information) contained 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.
  • 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.
  • the AMF may also select an SMF for establishing a PDU session for an S-NSSAI having an SST configured similar to the SST of the S-NSSAI with which the first PDU session is associated.
  • the AMF may select an SMF for establishing a PDU session for an S-NSSAI different from the S-NSSAI with which the first PDU session is associated.
  • the AMF transmits 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).
  • the SMF when the SMF receives information etc. (message, container, information) sent from the AMF, it can recognize what the UE is requesting and/or the contents of the information etc. (message, container, information) received from the AMF.
  • information etc. messages, container, information
  • the SMF may make a second condition determination.
  • the second condition determination may be for determining whether or not the network accepts the UE request. If the SMF determines that the second condition determination is true, it may start the procedure in FIG. 8 (A), and if the SMF determines that the second condition determination is false, it may start the procedure in FIG. 8 (B).
  • 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.
  • the second condition determination may be determined to be true, and if the network does not permit the UE's request, the second condition determination may be determined to be false. Also, 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 to be true, and if the function requested by the UE is not supported, the second condition determination may be determined to be false. Also, if the transmitted and received identification information is permitted, the second condition determination may be determined to be true, and if the transmitted and received identification information is not permitted, the second condition determination may be determined to be false.
  • the conditions for determining whether the second condition determination is true or false do not have to be limited to the conditions described above.
  • 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.
  • the SMF may provide the NF with information necessary to perform the second condition determination, specifically, at least a portion of the information received from the UE (S1406).
  • 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., true or false) to the SMF.
  • the SMF may determine the identification information and/or control message to be transmitted to the UE based on the result of the second condition determination received from the NF.
  • 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.
  • the SMF may also use the UE ID and/or (PDU session) to ascertain to 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.
  • PDU session the UE ID and/or (PDU session) to ascertain to the NSACF and/or NSSF and/or PCF and/or OAM and/or new NF whether the upper
  • the SMF may send an access type (corresponding to the access which sent the establishment request message), and/or a PDU session ID, and/or one or more S-NSSAIs included in the 21st identification and/or the 23rd identification, 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 is increased, 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 is increased, 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 and/or PDU session and/or QoS flow is increased.
  • the SMF may send these to the NSACF and/or NSSF and/or PCF and/or OAM and/or new NF via the AMF
  • the SMF does not need to transmit these control information to the NSACF and/or NSSF and/or PCF and/or OAM and/or new NF.
  • the NSACF and/or NSSF and/or PCF and/or OAM and/or new NF receiving these control information from the SMF may check or determine 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 NSACF and/or NSSF and/or PCF and/or OAM and/or new NF may not check or determine whether or not these upper limits or thresholds have been reached when one or more S-NSSAIs included in the 21st identification information and/or the 23rd identification information received from the SMF correspond to Vehicle-to-Everything (V2X) and/or V2X services and/or Aircraft-to-Everything (A2X) and/or A2X services and/or emergency services.
  • V2X Vehicle-to-Everything
  • A2X Aircraft-to-Everything
  • 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 shall notify the UE ID and/or access type (corresponding to the access that sent the PDU session establishment request message) and/or 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 EE and/or EC and/or ES and/or EEES and/or CE and/or RE that the upper limits or thresholds have been reached.
  • the UE ID and/or access type corresponding to the access that sent the PDU session establishment request message
  • the SMF may transmit to the SMF 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 has reached an upper limit or threshold, 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 and/or PDU session and/or QoS flow has reached an upper limit or threshold.
  • this control information may be transmitted in the 34th identification information.
  • the NSACF and/or NSSF and/or PCF and/or OAM and/or new NF may transmit to the SMF an S-NSSAI that has reached these upper limits or thresholds.
  • This S-NSSAI may be transmitted in the 31st identification information. Furthermore, the NSACF and/or NSSF and/or PCF and/or OAM and/or new NF may transmit to the SMF an S-NSSAI (alternative S-NSSAI) that replaces the S-NSSAI that has reached these upper limits or thresholds. This S-NSSAI may be transmitted in the 35th identification information. Furthermore, the NSACF and/or NSSF and/or PCF and/or OAM and/or new NF may transmit to the SMF a timer (back-off timer) value for the S-NSSAI that has reached these upper limits or thresholds. This timer value may be transmitted in the 33rd identification information. Furthermore, 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 transmit an access type (corresponding to the access that transmitted the PDU session establishment request message).
  • an S-NSSAI alternative S-NSSAI
  • 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 shall determine whether the UE ID, and/or access type (corresponding to the access that sent the PDU session establishment request message), and/or 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 EE and/or EC and/or ES and/or EEES and/or CE and/or RE have reached their upper limits or thresholds.
  • the SMF may transmit 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 has not reached the upper limit or threshold, 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 and/or PDU session and/or QoS flow has not reached the upper limit or threshold.
  • 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).
  • the NSACF and/or NSSF and/or PCF and/or OAM and/or new NF may transmit these to the SMF via the AMF.
  • 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 the other access type (e.g., non-3GPP access).
  • one access type e.g., 3GPP access
  • the other access type e.g., non-3GPP access
  • the exchange of control information between these SMFs (via AMF as necessary) and the NSACF and/or NSSF and/or PCF and/or OAM and/or new NF may be performed by one or more procedures.
  • all of the above exchanges may be performed by performing some of the above exchanges between the SMF and the NSACF and/or NSSF and/or PCF and/or OAM and/or new NF, and performing the remaining of the above exchanges between the SMF and the NSACF and/or NSSF and/or PCF and/or OAM and/or new NF.
  • the SMF may select a UPF for the PDU session to be established and 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.
  • the SMF may decide whether or not to approve the C2 communication during this procedure based on information received from the AMF (messages, containers, information), and/or information such as PCC rules received from the PCF, and/or subscriber information, and/or network capability information, and/or UE policies, and/or operator policies, and/or network status, and/or user registration information, and/or context held by the SMF, etc.
  • information received from the AMF messages, containers, information
  • information such as PCC rules received from the PCF, and/or subscriber information, and/or network capability information, and/or UE policies, and/or operator policies, and/or network status, and/or user registration information, and/or context held by the SMF, etc.
  • the SMF may decide to approve the establishment of the PDU session requested by the UE based on at least one of the identification information items 21 to 23.
  • 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. Furthermore, 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.
  • the UPF when the UPF receives the N4 session establishment request message (S1408), it can recognize the contents of the information received from the SMF. Furthermore, based on the reception of the N4 session establishment request message, the UPF may transmit an N4 session establishment response message to the SMF, for example, via the N4 interface (S1410).
  • the SMF 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.
  • the SMF transmits a PDU session establishment acceptance 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.
  • the UE then receives the PDU session establishment acceptance message and/or the identification information from the SMF (S1412)(S1414)(S1416).
  • the SMF transmits an N1 SM container and/or N2 SM information and/or a PDU session ID to the AMF, for example via the N11 interface, based on receipt of a PDU session establishment request message and/or selection of a UPF and/or receipt of an N4 session establishment response message (S1412).
  • the N1 SM container may include a PDU session establishment acceptance message.
  • the PDU session ID may be included in the PDU session establishment acceptance message.
  • the AMF having 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).
  • 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.
  • the AMF transmits an N2 PDU session request message to a base station device included in the access network (S1414), and the base station device that receives the N2 PDU session request message transmits a NAS message to the UE (S1416).
  • the N2 PDU session request message may include a NAS message and/or N2 SM information.
  • the NAS message may include a PDU session ID and/or an N1 SM container.
  • the PDU session establishment acceptance message may also be a response message to a PDU session establishment request.
  • the PDU session establishment acceptance message may also indicate that the establishment of the PDU session has been accepted.
  • 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 accept message, and/or an N1 SM container, and/or a PDU session ID, and/or a NAS message, and/or N2 SM information, and/or an N2 PDU session request message.
  • the SMF and/or AMF may send a PDU session establishment acceptance message, and/or an N1 SM container, and/or an NAS message, and/or an N2 SM information, and/or an N2 PDU session request message including at least one of the identification information 31 to 36.
  • the SMF may indicate that the network supports each function, that the UE request has been accepted, that the request from the UE has not been permitted, or a combination of these by transmitting these identification information and/or a PDU session establishment acceptance message.
  • two or more of these identification information may be configured as one or more identification information.
  • one identification information has multiple meanings, it may be divided into multiple identification information and transmitted and received.
  • the information indicating support for each function and the information indicating a request to use each function may be transmitted and received as the same identification information, or may be transmitted and received as different identification information.
  • 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.
  • the SMF may also 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.
  • the SMF may also transmit a PDU session ID in addition to these identification information items.
  • 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 NW side.
  • the SMF may include identification information No. 32 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.
  • the SMF may include the 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 not supported in the PDU session establishment acceptance message and/or NAS message. Furthermore, in this case, the SMF may not include the 33rd identification information, and/or the 34th identification information, and/or the 35th identification information in the PDU session establishment acceptance message and/or NAS message.
  • the SMF also receives from the NSACF and/or NSSF and/or PCF and/or OAM and/or the 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 identification information and/or the 23rd 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 not reached their upper limit or threshold, and/or the network energy related information exposure per NS.
  • control information indicating that the rk energy related information 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 or threshold 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 and/or PDU session and/or QoS flow has not reached an upper limit or threshold
  • the 31st identification information and/or the 32nd identification information may be transmitted.
  • the SMF also receives from the NSACF and/or NSSF and/or PCF and/or OAM and/or the 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 contained in the 21st identification information and/or the 23rd 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 an upper limit or threshold, and/or the number of network energy related information exposures per NS.
  • 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.
  • the network may indicate the contents of the above identification information to the UE by sending a PDU session establishment acceptance message.
  • the network may also transmit identification information other than the identification information nos. 31 to 36 in the PDU session establishment acceptance 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.
  • the network may send the S-NSSAI and/or DNN associated with the established PDU session in a PDU session establishment accept message.
  • the UE when the UE receives the NAS message, for example via the N1 interface (S1416), it can recognize that the UE's request in the PDU session establishment request message has been accepted and/or the contents of the information, etc., included in the NAS message (message, container, information).
  • 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.
  • the UE may recognize and store the content of the received identification information.
  • the UE may also recognize and store, based on the reception of the 34th identification information, 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.
  • the UE may also recognize and store, based on receiving the 31st identification information and the 34th identification information, that the S-NSSAI indicated by the 31st identification information is unavailable based on the reason value indicated by the 34th identification information.
  • the UE may recognize that the S-NSSAI indicated in the 31st identification information is unavailable based on the reason value indicated in the 34th identification information, and may recognize and store that the S-NSSAI indicated in 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.
  • the UE may recognize and store, based on receiving the 31st identification information, the 33rd identification information, and the 34th identification information, that the S-NSSAI indicated in the 31st identification information is unavailable based on the reason value indicated in the 34th identification information, and may start a timer using the timer value indicated in the 33rd identification information.
  • the UE may recognize and store, when the timer has not expired, 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 registration procedures using that S-NSSAI are 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.
  • the UE may recognize and store 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 can be established using that S-NSSAI.
  • an instruction from the network side e.g., a control message such as a PDU session change command sent from the SMF to the UE
  • the UE may recognize and store 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 can be established using that S-NSSAI.
  • the SMF sends an N1 SM container and/or a PDU session ID to the AMF, for example via the N11 interface (S1418).
  • the N1 SM container may include a PDU session establishment rejection message.
  • the PDU session ID may be included in the PDU session establishment rejection message.
  • 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).
  • the NAS message is transmitted, for example, via the 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.
  • the PDU session establishment rejection message may also be a response message to a PDU session establishment request.
  • the PDU session establishment rejection message may also indicate that the establishment of a PDU session has been rejected.
  • the SMF and/or AMF may indicate that the UE's request in 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 a NAS message.
  • the SMF may indicate that the UE request has been rejected, or that the request from the UE has not been authorized, or may indicate a combination of these.
  • the SMF and/or AMF may send a PDU session establishment rejection message, and/or an N1 SM container, and/or an NAS message, and/or an N2 SM information, and/or an N2 PDU session request message including identification information 31 to 36.
  • 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.
  • the SMF may also 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.
  • the SMF may also transmit a PDU session ID in addition to these identification information items.
  • 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 NW side.
  • the SMF may include identification information No. 32 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.
  • the SMF may include the 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 not supported in the PDU session establishment rejection message and/or NAS message. Furthermore, in this case, the SMF may not include the 33rd identification information, and/or the 34th identification information, and/or the 35th identification information in the PDU session establishment rejection message and/or NAS message.
  • the SMF also receives from the NSACF and/or NSSF and/or PCF and/or OAM and/or the 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 identification information and/or the 23rd 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 not reached their upper limit or threshold, and/or the network energy related information exposure per NS.
  • control information indicating that the rk energy related information 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 or threshold 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 and/or PDU session and/or QoS flow has not reached an upper limit or threshold
  • the 31st identification information and/or the 32nd identification information may be transmitted.
  • the SMF also receives from the NSACF and/or NSSF and/or PCF and/or OAM and/or the 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 contained in the 21st identification information and/or the 23rd 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 an upper limit or threshold, and/or the number of network energy related information exposures per NS.
  • 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.
  • the UE when the UE receives the NAS message, for example via the N1 interface (S1422), it can recognize that the UE's request in the PDU session establishment request message has been rejected and/or the contents of the information, etc. (message, container, information) contained in the NAS message.
  • the UE may store the content indicated by the received identification information, and may behave based on the information indicated by the received identification information.
  • the UE may recognize and store the content of the received identification information.
  • the UE may also recognize and store, based on the reception of the 34th identification information, 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.
  • the UE may also recognize and store, based on receiving the 31st identification information and the 34th identification information, that the S-NSSAI indicated by the 31st identification information is unavailable based on the reason value indicated by the 34th identification information.
  • the UE may recognize that the S-NSSAI indicated in the 31st identification information is unavailable based on the reason value indicated in the 34th identification information, and may recognize and store that the S-NSSAI indicated in 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.
  • the UE may recognize and store, based on receiving the 31st identification information, the 33rd identification information, and the 34th identification information, that the S-NSSAI indicated in the 31st identification information is unavailable based on the reason value indicated in the 34th identification information, and may start a timer using the timer value indicated in the 33rd identification information.
  • the UE may recognize and store, when the timer has not expired, 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 registration procedures using that S-NSSAI are 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.
  • the UE may recognize and store 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 can be established using that S-NSSAI.
  • an instruction from the network side e.g., a control message such as a PDU session change command sent from the SMF to the UE
  • the UE may recognize and store 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 can be established using that S-NSSAI.
  • 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. Also, 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.
  • the UE may transmit a PDU session establishment request message together with a first S-NSSAI and including UE capability information indicating that the UE supports an energy efficiency function, 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 of 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 of energy consumption per network slice, start a timer using the timer value for the first S-NSSAI, and when the timer expires, transmit a PDU session establishment request message together with the first S-NSSAI.
  • 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 deciding whether or not to start an MM procedure or SM procedure that is executed separately after the completion of this procedure.
  • the program that operates in the device according to one aspect of this embodiment may be a program that controls a Central Processing Unit (CPU) or the like to make a computer function so as to realize the functions of the 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 other storage device system.
  • RAM Random Access Memory
  • HDD Hard Disk Drive
  • a program for realizing the functions of an embodiment related to one aspect of this embodiment may be recorded on a computer-readable recording medium.
  • the program recorded on this recording medium may be read into a computer system and executed to realize the functions.
  • the "computer system” here refers to a computer system built into a device, and includes hardware such as an operating system and peripheral devices.
  • the "computer-readable recording medium” may be a semiconductor recording medium, an optical recording medium, a magnetic recording medium, a medium that dynamically holds a program for a short period of time, or any other recording medium that can be read by a computer.
  • each functional block or feature of the device used in the above-described embodiment may be implemented or performed by an electric circuit, for example, an integrated circuit or multiple integrated circuits.
  • the electric 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 electric circuit may be composed of digital circuits or analog circuits. Furthermore, if an integrated circuit technology that replaces current integrated circuits emerges due to advances in semiconductor technology, one or more aspects of the present embodiment may use a new integrated circuit based on that technology.
  • this embodiment is not limited to the above embodiment.
  • one example of a device is described, but one aspect of this 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.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Databases & Information Systems (AREA)
  • Physics & Mathematics (AREA)
  • Mathematical Physics (AREA)
  • Theoretical Computer Science (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

L'UE selon l'invention : transmet un message de demande d'établissement de session PDU comprenant des informations de capacité d'UE indiquant qu'une fonction d'efficacité énergétique est prise en charge et des premières S-NSSAI ; lors de la réception d'un message de rejet d'établissement de session PDU comprenant des NSSAI rejetées comprenant une valeur de raison indiquant que les premières S-NSSAI ont atteint une valeur limite supérieure de quantité de consommation d'énergie par tranche de réseau, une valeur de temporisateur par rapport aux premières S-NSSAI, et les premières S-NSSAI, associe et stocke les premières S-NSSAI et/ou la valeur de temporisateur par rapport aux premières S-NSSAI, et/ou le fait que les premières S-NSSAI ont atteint la valeur limite supérieure de quantité de consommation d'énergie par tranche de réseau ; utilise la valeur de temporisateur par rapport aux premières S-NSSAI pour démarrer un temporisateur ; et à l'expiration du temporisateur, transmet un message de demande d'établissement de session PDU conjointement avec les premières S-NSSAI.
PCT/JP2024/035715 2023-11-02 2024-10-07 Équipement utilisateur (ue) Pending WO2025094593A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
JP2023188297 2023-11-02
JP2023-188297 2023-11-02

Publications (1)

Publication Number Publication Date
WO2025094593A1 true WO2025094593A1 (fr) 2025-05-08

Family

ID=95581891

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/JP2024/035715 Pending WO2025094593A1 (fr) 2023-11-02 2024-10-07 Équipement utilisateur (ue)

Country Status (1)

Country Link
WO (1) WO2025094593A1 (fr)

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20220159605A1 (en) * 2019-03-13 2022-05-19 Convida Wireless, Llc Dynamic network capability configuration
WO2023286779A1 (fr) * 2021-07-16 2023-01-19 Nec Corporation Procédé exécuté par un terminal radio, et terminal radio
WO2023068119A1 (fr) * 2021-10-22 2023-04-27 Nec Corporation Procédé d'équipement utilisateur, procédé d'appareil amf géographiquement sélectionné, équipement utilisateur, appareil amf géographiquement sélectionné, et procédé de terminal de communication

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20220159605A1 (en) * 2019-03-13 2022-05-19 Convida Wireless, Llc Dynamic network capability configuration
WO2023286779A1 (fr) * 2021-07-16 2023-01-19 Nec Corporation Procédé exécuté par un terminal radio, et terminal radio
WO2023068119A1 (fr) * 2021-10-22 2023-04-27 Nec Corporation Procédé d'équipement utilisateur, procédé d'appareil amf géographiquement sélectionné, équipement utilisateur, appareil amf géographiquement sélectionné, et procédé de terminal de communication

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
CHINA MOBILE: "pCR on resolving EN in 5.6 Use case on supporting service-level energy efficiency analysis for verticals", 3GPP DRAFT; S1-231127, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. 3GPP SA 1, no. Berlin, Germany; 20230522 - 20230526, 21 May 2023 (2023-05-21), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France, XP052487155 *

Similar Documents

Publication Publication Date Title
JP7614751B2 (ja) ＵＥ（Ｕｓｅｒ Ｅｑｕｉｐｍｅｎｔ）及び通信制御方法
JP7651569B2 (ja) ＵＥ（Ｕｓｅｒ Ｅｑｕｉｐｍｅｎｔ）及びＡＭＦ（Ａｃｃｅｓｓ ａｎｄ Ｍｏｂｉｌｉｔｙ Ｍａｎａｇｅｍｅｎｔ Ｆｕｎｃｔｉｏｎ）
JP7671280B2 (ja) ＵＥ（Ｕｓｅｒ Ｅｑｕｉｐｍｅｎｔ）及びＡＭＦ（Ａｃｃｅｓｓ ａｎｄ ｍｏｂｉｌｉｔｙ Ｍａｎａｇｅｍｅｎｔ Ｆｕｎｃｔｉｏｎ）
US12452781B2 (en) User Equipment (UE)
US12445949B2 (en) Method and user equipment for enhancing network slicing
JP7623797B2 (ja) ＵＥ（Ｕｓｅｒ Ｅｑｕｉｐｍｅｎｔ）及び通信制御方法
JP7576972B2 (ja) ＵＥ（Ｕｓｅｒ Ｅｑｕｉｐｍｅｎｔ）
JP7644584B2 (ja) ＵＥ（Ｕｓｅｒ Ｅｑｕｉｐｍｅｎｔ）及び通信制御方法
JP7644585B2 (ja) ＵＥ（Ｕｓｅｒ Ｅｑｕｉｐｍｅｎｔ）及び通信制御方法
JP7777091B2 (ja) ＵＥ（Ｕｓｅｒ Ｅｑｕｉｐｍｅｎｔ）
JP7624933B2 (ja) Ｕｅ、制御装置、及び通信制御方法
JP7644648B2 (ja) ＵＥ（Ｕｓｅｒ Ｅｑｕｉｐｍｅｎｔ）
JP7566618B2 (ja) ＵＥ（Ｕｓｅｒ Ｅｑｕｉｐｍｅｎｔ）
JP2024066696A (ja) ＵＥ（Ｕｓｅｒ Ｅｑｕｉｐｍｅｎｔ）
JP2024066695A (ja) ＵＥ（Ｕｓｅｒ Ｅｑｕｉｐｍｅｎｔ）
JP2025085037A (ja) ＵＥ（Ｕｓｅｒ Ｅｑｕｉｐｍｅｎｔ）
JP2025069484A (ja) ＵＥ（Ｕｓｅｒ Ｅｑｕｉｐｍｅｎｔ）
JP2025085034A (ja) ＵＥ（Ｕｓｅｒ Ｅｑｕｉｐｍｅｎｔ）
JP2025027162A (ja) ＵＥ（Ｕｓｅｒ Ｅｑｕｉｐｍｅｎｔ）
JP2024125448A (ja) ＵＥ（Ｕｓｅｒ Ｅｑｕｉｐｍｅｎｔ）
WO2025094593A1 (fr) Équipement utilisateur (ue)
WO2025094592A1 (fr) Équipement utilisateur (ue)
JP7768882B2 (ja) ＵＥ（Ｕｓｅｒ Ｅｑｕｉｐｍｅｎｔ）
JP7689114B2 (ja) ＵＥ（Ｕｓｅｒ Ｅｑｕｉｐｍｅｎｔ）
JP7606326B2 (ja) ＵＥ（Ｕｓｅｒ Ｅｑｕｉｐｍｅｎｔ）及び通信制御方法

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 24885368

Country of ref document: EP

Kind code of ref document: A1