User Equipment (UE)

By selecting a second PLMN when satellite coverage is discontinuous and using a waiting timer to manage emergency calls, the mobility management and power consumption issues of UEs in satellite communications are resolved, and effective UE behavior and resource optimization are achieved.

CN117997409BActive Publication Date: 2026-11-17SHARP KK
View PDF 2 Cites 0 Cited by

Patent Information

Application Number
CN202310101022.6
Authority / Receiving Office
CN · China
Patent Type
Patents(China)
Current Assignee / Owner
Priority Date
2022-11-02
Filing Date
2023-02-08
Publication Date
2026-11-17
Estimated Expiration
2043-02-08

AI Technical Summary

Technical Problem

In cases of discontinuous satellite coverage, improvements in UE mobility management and power consumption are not yet clear, especially with the expansion of satellite communication capabilities in Release 18, where the detailed behavior of the UE and network is unclear.

Method used

When satellite coverage is discontinuous, the UE selects a second PLMN for communication through the transceiver unit and the control unit, and uses a waiting timer to manage the emergency call process to ensure effective network connectivity within the waiting range.

Benefits of technology

The behavior of UE and network under discontinuous satellite coverage was clarified, power consumption management was improved, and effective UE mobility management and resource optimization were achieved.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN117997409B_ABST
    Figure CN117997409B_ABST
Patent Text Reader

Abstract

Problem: This invention addresses mobility management and power saving enhancement in the UE when satellite coverage is discontinuous, clarifying the detailed behavior of the UE and network. Solution: A UE capable of satellite communication receives a waiting range from a first PLMN via a first satellite. If communication via the first satellite becomes impossible, and communication via a second satellite connected to a second PLMN becomes possible, the second PLMN is selected. A waiting timer is generated based on the waiting range, and a timer using the waiting timer is started. If an emergency call is made while the timer is active, the timer is stopped, and a login procedure is performed to initiate an emergency call. If no emergency call is made while the timer is active, the login procedure is performed after the timer expires.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] This invention relates to a UE (User Equipment). Background Technology

[0002] In 3GPP (3rd Generation Partnership Project: registered trademark), the system architecture of 5GS (5G System) as a fifth-generation (5G) mobile communication system was studied, and discussions were made on supporting new processes and new functions (see Non-Patent Literature 1-3). Existing technical documents Non-patent literature

[0003] Non-patent document 1: 3GPP TS 23.501V17.6.0 (2022-09); 3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Systemarchitecture for the 5G System (5GS); Stage 2 (Release 17) Non-patent document 2: 3GPP TS 23.502V17.6.0 (2022-09); 3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Procedures for the 5G System (5GS); Stage 2 (Release 17) Non-patent document 3: 3GPP TS 24.501V17.8.0 (2022-09); 3rd Generation Partnership Project; Technical Specification Group Core Network and Terminals; Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3; (Release 17) Non-patent document 4: 3GPP TR 23.700-28V1.1.1(2022-10); 3rd GenerationPartnership Project; Technical Specification Group Services and SystemAspects; Study on Integration of satellite components in the 5G architecture; Phase 2(Release 18) Summary of the Invention The problem the invention aims to solve

[0004] Release 17 introduced satellite communication functionality from 3GPP, and Release 18 discussed the expansion of this functionality. Specifically, it discussed mobility management and power saving enhancement in the UE in the case of discontinuous satellite coverage. However, the detailed behavior of the UE and the network is not yet clear (see Non-Patent Literature 4).

[0005] One aspect of the present invention is made in view of the above circumstances, which clarifies the detailed behavior of the UE and the network for mobility management and power saving enhancement in the case of discontinuous satellite coverage. Technical solution

[0006] One embodiment of the present invention is a UE comprising a transceiver unit and a control unit, characterized in that the UE is a UE capable of communication via satellite; the transceiver unit receives a wait range from the network during a login process and / or configuration update process and / or service request process and / or non-login process performed in a first PLMN via a first satellite; if the UE is unable to communicate via the first satellite but is able to communicate via a second satellite connected to a second PLMN, the control unit selects the second PLMN; the control unit generates a wait timer based on the wait range; the control unit starts a timer using the wait timer; if an emergency call is made while the timer is in operation, the control unit stops the timer and executes a login process for the emergency call; if no emergency call is made while the timer is in operation, the control unit executes a login process after the timer expires. Beneficial effects

[0007] According to one aspect of the present invention, it is possible to clarify the detailed behavior of the UE and the network for mobility management and power saving enhancement in the case of discontinuous satellite coverage. Attached Figure Description

[0008] Figure 1 This is a diagram illustrating the general structure of a mobile communication system (EPS / 5GS). Figure 2 This is a diagram illustrating the detailed structure of a mobile communication system (EPS / 5GS). Figure 3 This is a diagram illustrating the device configuration of the UE. Figure 4 This diagram illustrates the configuration of the access network device (gNB) in 5GS. Figure 5 This diagram illustrates the configuration of the core network devices (AMF / SMF / UPF) in 5GS. Detailed Implementation

[0009] Hereinafter, a preferred embodiment for carrying out the present invention will be described with reference to the accompanying drawings. It should be noted that, in this embodiment, as an example, an implementation of a mobile communication system applying a solution of the present invention will be described. [1. System Overview]

[0010] first, Figure 1This is a schematic diagram illustrating the mobile communication system 1 used in various embodiments. Figure 2 This is a diagram used to illustrate the detailed configuration of the mobile communication system 1.

[0011] exist Figure 1 The document states that the mobile communication system 1 consists of UE_A10, access network_A80, core network_A90, PDN (Packet Data Network)_A5, access network_B120, core network_B190, and DN (Data Network)_A6.

[0012] In the following descriptions, the symbols for these devices and functions will sometimes be omitted, similar to those for UE, Access Network_A, Core Network_A, PDN, Access Network_B, Core Network_B, DN, etc.

[0013] In addition, Figure 2 The document describes 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 the interfaces for interconnecting these devices and functions.

[0014] Hereinafter, symbols are sometimes omitted to describe these devices / functions, such as UE, E-UTRAN, MME, SGW, PGW-U, PGW-C, PCRF, HSS, 5G AN, AMF, UPF, SMF, PCF, UDM, N3IWF, etc.

[0015] It should be noted that the EPS (Evolved Packet System) of a 4G system consists of an access network_A and a core network_A, but may further include the UE and / or PDN. Similarly, the 5GS (5G System) of a 5G system consists of a UE, an access network_B, and a core network_B, but may further include the DN.

[0016] A UE is a device capable of connecting to network services via 3GPP access (also known as 3GPP access network, 3GPP AN) and / or non-3GPP access (also known as non-3GPP access network, non-3GPP AN). A UE can be a mobile phone, smartphone, or other terminal device capable of wireless communication, or a terminal device capable of connecting to EPS and / or 5GS. A UE can possess a UICC (Universal Integrated Circuit Card) or eUICC (Embedded UICC). It should be noted that UE is sometimes referred to as a user equipment or terminal device.

[0017] Furthermore, Access Network A corresponds to E-UTRAN (Evolved Universal Terrestrial Radio Access Network) and / or the wireless LAN access network. One or more eNBs (evolved Node Bs) 45 are configured in the E-UTRAN. It should be noted that, hereinafter, the symbol for eNB 45 is sometimes omitted, for example, eNB. Furthermore, in the case of multiple eNBs, each eNB is interconnected, for example, via an X2 interface. In addition, one or more access points are configured in the wireless LAN access network.

[0018] Furthermore, the access network _B corresponds to the 5G access network (5G AN). The 5G AN consists of NG-RAN (NG Radio Access Network) and / or non-3GPP access networks. One or more gNBs (NR Node Bs) 122 are configured in the NG-RAN. It should be noted that, hereinafter, the symbol for gNB 122 is sometimes omitted, for example, gNB. A gNB is a node that provides the NR (New Radio) user plane and control plane to the UE, and is a node connected to the 5GCN via an NG interface (including the N2 or N3 interface). That is, a gNB is a base station device newly designed for 5GS, with different functions than the base station device (eNB) designed for EPS as a 4G system. Furthermore, in the case of multiple gNBs, each gNB is interconnected, for example, via an Xn interface.

[0019] Furthermore, non-3GPP access networks can include both untrusted non-3GPP access networks and trusted non-3GPP access networks. Untrusted non-3GPP access networks can be, for example, public wireless LANs or other non-3GPP access networks that do not undergo security management within the access network. On the other hand, trusted non-3GPP access networks can be access networks defined by 3GPP, and can possess TNAP (trusted non-3GPP access point) and TNGF (trusted non-3GPP gateway function).

[0020] Furthermore, E-UTRAN and NG-RAN will be referred to as 3GPP access in the following text. Additionally, wireless LAN access networks and non-3GPP ANs will be referred to as non-3GPP access. Furthermore, nodes configured in access network B are sometimes collectively referred to as NG-RAN nodes.

[0021] In addition, the devices included in Access Network A and Access Network B, and the devices included in Access Network A and Access Network B, are sometimes referred to as access networks or access devices or devices within access networks.

[0022] Furthermore, the 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).

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

[0024] In addition, the devices included in core network A and core network B and the devices included in core network A and core network B are sometimes referred to as core network or core network devices or devices within the core network.

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

[0026] In addition, Figure 1 The document describes situations where PDN and DN are similar, but they can also be different. A PDN can be a DN (Data Network) that provides communication services to the UE. It should be noted that a DN can be configured as a packet data service network or configured for each service. Furthermore, a PDN can include connected communication terminals. Therefore, connecting to a PDN can be a connection to a communication terminal or server device configured for the PDN. Moreover, sending and receiving user data with the PDN can be sending and receiving user data with a communication terminal or server device configured for the PDN. It should be noted that a PDN can be expressed as a DN, and vice versa.

[0027] Furthermore, hereinafter, at least a portion of Access Network_A, Core Network_A, PDN, Access Network_B, Core Network_B, DN, and / or more than one of these included devices are sometimes referred to as a network or network device. That is, the meaning of "network and / or network device sending and receiving messages and / or executing processes" is that at least a portion of Access Network_A, Core Network_A, PDN, Access Network_B, Core Network_B, DN, and / or more than one of these included devices send and receive messages and / or execute processes.

[0028] Furthermore, the UE can connect to the access network. Additionally, the UE can connect to the core network via the access network. Moreover, the UE can connect to the PDN or DN via the access network and core network. That is, the UE can send and receive user data with the PDN or DN. When sending and receiving user data, it can use not only IP (Internet Protocol) communication but also non-IP communication.

[0029] Here, IP communication refers to data communication using IP, which involves sending and receiving data via IP packets. An IP packet consists of an IP header and a payload. The payload may include data transmitted and received by devices / functions included in the EPS and 5GS. Furthermore, non-IP communication refers to data communication that does not use IP, but rather transmits and receives data using a structure different from IP packets. For example, non-IP communication can be data communication that transmits and receives application data without an IP header, or it can use other headers such as MAC headers or Ethernet (trademarked) frame headers to transmit and receive user data sent and received by the UE.

[0030] Furthermore, Access Network_A, Core Network_A, Access Network_B, Core Network_B, PDN_A, and DN_A may contain elements not described herein. Figure 2 The device may include, for example, an AUSF (Authentication Server Function) or an AAA (Authentication, Authorization, and Accounting) server (AAA-S) in core network A and / or core network B.

[0031] Here, AUSF is a core network device with authentication functions for both 3GPP and non-3GPP access. Specifically, it is a network function unit that receives authentication requests for 3GPP and / or non-3GPP access from the UE and performs the authentication process.

[0032] Furthermore, an AAA server is a device capable of authentication, authorization, and accounting functions, connecting directly to AUSF or indirectly via other network devices. An AAA server can be a network device within the core network. It should be noted that an AAA server can be included in the PLMN but not in core network A and / or core network B. That is, an AAA server can be a core network device or a device located outside the core network. For example, an AAA server can be a server device within the PLMN managed by a third party.

[0033] It should be noted that, in Figure 2 For the sake of simplicity, each device / function is shown as one in the diagram, but multiple identical devices / functions can be configured in the mobile communication system 1. Specifically, 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 can be configured in the mobile communication system 1. [2. Composition of each device]

[0034] Next, the configuration of the various devices (UE and / or access network device and / or core network device) used in each embodiment will be described using the accompanying drawings. It should be noted that each device can be configured as physical hardware, as logical (virtual) hardware built on general-purpose hardware, or as software. Furthermore, at least some (including all) of the functions possessed by each device can also be configured as physical hardware, logical hardware, or software.

[0035] It should be noted that the storage units (Storage Unit_A340, Storage Unit_B540, Storage Unit_B740) within the various devices and functions mentioned below are, for example, composed of semiconductor memory, SSD (Solid State Drive), HDD (Hard Disk Drive), etc. Furthermore, each storage unit can store not only the information originally set at the factory, but also various information exchanged between the device itself and devices / functions outside the function (e.g., UE and / or access network devices and / or core network devices and / or PDN and / or DN). In addition, each storage unit can store identification information, control information, flags, parameters, etc., included in the control messages exchanged during the various communication processes described later. Furthermore, each storage unit can store this information in each UE. Moreover, in the case of interoperability between 5GS and EPS, each storage unit can store control messages and user data exchanged between the 5GS and / or devices / functions included in EPS. In this case, it can store not only data exchanged via the N26 interface, but also data exchanged without using the N26 interface. [2.1. UE Device Configuration]

[0036] First, use Figure 3 An example of the device configuration of a UE (User Equipment) will be described. The UE consists of a control unit_A300, an antenna 310, a transceiver unit_A320, and a storage unit_A340. The control unit_A300, transceiver unit_A320, and storage unit_A340 are connected via a bus. The transceiver unit_A320 is connected to the antenna 310.

[0037] The control unit_A300 is a functional unit that controls the overall operation and functions of the UE. The control unit_A300 reads and executes various programs stored in the storage unit_A340 as needed, thereby realizing various processes in the UE.

[0038] The transceiver unit A320 is a functional unit used for wireless communication with base station devices (eNB or gNB) within the access network via an antenna. That is, the UE can use the transceiver unit A320 to send and receive user data and / or control information with access network devices and / or core network devices and / or PDN and / or DN.

[0039] When reference Figure 2In detail, the UE can communicate with the base station device (eNB) in the E-UTRAN via the LTE-Uu interface using the transceiver unit (A320). Furthermore, the UE can communicate with the base station device (gNB) in the 5G AN using the transceiver unit (A320). Additionally, the UE can send and receive NAS (Non-Access-Stratum) messages with the AMF via the N1 interface using the transceiver unit (A320). However, the N1 interface is a logical interface; therefore, communication between the UE and the AMF actually occurs via the 5G AN.

[0040] Storage unit A340 is a functional unit used to store programs, user data, control information, etc., required for various actions of the UE. Furthermore, storage unit A340 may also have the function of storing control information transmitted and received between the UE and the access network device, core network device, and DN. [2.2. gNB Device Configuration]

[0041] Next, use Figure 4 An example of the gNB device configuration will be described. The gNB consists of a control unit_B500, an antenna 510, a network connection unit_B520, a transceiver unit_B530, and a storage unit_B540. The control unit_B500, network connection unit_B520, transceiver unit_B530, and storage unit_B540 are connected via a bus. The transceiver unit_B530 is connected to the antenna 510.

[0042] The control unit_B500 is a functional unit that controls the overall operation and functions of the gNB. The control unit_B500 reads and executes various programs stored in the storage unit_B540 as needed, thereby realizing various processes within the gNB.

[0043] The network connection unit_B520 is a functional unit for enabling communication between the gNB and the AMF and / or UPF. That is, the gNB can use the network connection unit_B520 to send and receive user data and / or control information with the AMF and / or UPF.

[0044] The transceiver unit B530 is a functional unit used for wireless communication with the UE via the antenna 510. That is, the gNB can use the transceiver unit B530 to send and receive user data and / or control information with the UE.

[0045] When reference Figure 2 In detail, the gNB located in the 5G AN can communicate with the AMF via the N2 interface and with the UPF via the N3 interface using the network connection unit_B520. Furthermore, the gNB can communicate with the UE using the transceiver unit_B530.

[0046] The storage unit_B540 is a functional unit used to store programs, user data, control information, etc., required for various operations of the gNB. Furthermore, the storage unit_540 may also have the function of storing control information transmitted and received between the UE, other access network devices (base station devices), core network devices, and the DN. [2.3. AMF Device Configuration]

[0047] Next, use Figure 5 An example of the device configuration of an AMF will be described. The AMF consists of a control unit_B700, a network connection unit_B720, and a storage unit_B740. The control unit_B700, network connection unit_B720, and storage unit_B740 are connected via a bus. The AMF can be a node that processes the control plane.

[0048] The control unit_B700 is a functional unit that controls the overall operation and function of the AMF. The control unit_B700 reads and executes various programs stored in the storage unit_B740 as needed, thereby realizing various processes within the AMF.

[0049] The network connection unit_B720 is a functional unit for connecting the AMF to base station devices (gNB) and / or SMF and / or PCF and / or UDM and / or SCEF and / or NSACF within the 5G AN. That is, the AMF can use the network connection unit_B720 to send and receive user data and / or control information between itself and the base station devices (gNB) and / or SMF and / or PCF and / or UDM and / or SCEF within the 5G AN.

[0050] When reference Figure 2 In detail, the AMF located within the 5GCN can communicate with the gNB via the N2 interface, with the UDM via the N8 interface, with the SMF via the N11 interface, and with the PCF via the N15 interface using the network connection unit_A620. Furthermore, the AMF can send and receive NAS messages with the UE via the N1 interface using the network connection unit_A620. However, the N1 interface is a logical interface; therefore, communication between the UE and AMF is actually via the 5G AN. Additionally, when the N26 interface is supported, the AMF can communicate with the MME via the N26 interface using the network connection unit_A620.

[0051] Storage unit B740 is a functional unit used to store programs, user data, control information, etc., required for various operations of the AMF. Furthermore, storage unit B740 may also have the function of storing control information transmitted and received between the UE, access network devices, other core network devices, and the DN.

[0052] It should be noted that 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; performing registration management (RM) functions; connection management (CM) functions; reachability management functions; mobility management functions for UEs, etc.; transmitting SM (Session Management) messages between the UE and the SMF; access authentication (Access Authorization) functions; security anchor function (SEA); security context management (SCM); supporting the N2 interface for N3IWF (Non-3GPP Interworking Function); supporting the transmission and reception of NAS signals with the UE via N3IWF; and authenticating UEs connected via N3IWF.

[0053] Furthermore, the RM state of each UE is managed in login management. The RM state can be synchronized between the UE and the AMF. There are two RM states: a non-login state (RM-DEREGISTERED state) and a login state (RM-REGISTERED state). In the non-login state, the UE is not logged into the network; therefore, the UE context in the AMF does not have valid location and routing information for that UE, so the AMF is in a state where the UE cannot be reached. In the login state, the UE is logged into the network; therefore, the UE can receive services that require network login. It should be noted that the RM state can also be expressed as a 5GMM state (5GMMstate). In this case, the non-login state can also be expressed as the 5GMM-DEREGISTERED state, and the login state can also be expressed as the 5GMM-REGISTERED state.

[0054] In other words, 5GMM-REGISTERED can refer to either the state where each device has established a 5GMM context or the state where a PDU session context has been established. It should be noted that when each device is 5GMM-REGISTERED, UE_A10 can begin sending and receiving user data and control messages, and can also respond to paging. Furthermore, it should be noted that when each device is 5GMM-REGISTERED, UE_A10 can perform login procedures and / or service request procedures other than the login procedure used for initial login.

[0055] Furthermore, 5GMM-DEREGISTERED can indicate that the devices have not established a 5GMM context, the UE_A10's location information has not been obtained by the network, or the network cannot reach the UE_A10. It should be noted that when the devices are 5GMM-DEREGISTERED, the UE_A10 can begin the login process or establish a 5GMM context by executing the login process.

[0056] Furthermore, the CM state of each UE is managed within the connection management system. The CM state can be synchronized between the UE and the AMF. There are two CM states: an IDLE state and a CONNECTED state. In the IDLE state, the UE is logged in but does not have a NAS signaling connection established with the AMF via the N1 interface. Additionally, in the IDLE state, the UE does not have an N2 connection or an N3 connection. On the other hand, in the CONNECTED state, the UE has a NAS signaling connection established with the AMF via the N1 interface. Furthermore, in the CONNECTED state, the UE can also have an N2 connection and / or an N3 connection.

[0057] Furthermore, connection management can be divided into CM states in 3GPP access and CM states in non-3GPP access. In this case, the CM states in 3GPP access can be either an IDLE state (CM-IDLE state over 3GPP access) or a CONNECTED state (CM-CONNECTED state over 3GPP access). Similarly, the CM states in non-3GPP access can be either an IDLE state (CM-IDLE state over non-3GPP access) or a CONNECTED state (CM-CONNECTED state over non-3GPP access). It should be noted that the IDLE state can be expressed as an idle mode, and the CONNECTED state can be expressed as a connected mode.

[0058] It should be noted that the CM state can also be expressed as 5GMM mode. In this case, the non-connected state can also be expressed as 5GMM-IDLE mode, and the connected state can also be expressed as 5GMM-CONNECTED mode. Furthermore, the non-connected state in 3GPP access can also be expressed as 5GMM-IDLE mode over 3GPP access, and the connected state in 3GPP access can also be expressed as 5GMM-CONNECTED mode over 3GPP access. Similarly, the non-connected state in non-3GPP access can also be expressed as 5GMM-IDLE mode over non-3GPP access, and the connected state in non-3GPP access can also be expressed as 5GMM-CONNECTED mode over non-3GPP access. It should be noted that 5GMM non-connected mode can be expressed as idle mode, and 5GMM connected mode can be expressed as connected mode.

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

[0060] It should be noted that N3IWF is a device and / or function configured between non-3GPP access and 5GCN when the UE is connected to 5GS via non-3GPP access. [2.4. SMF Device Configuration]

[0061] Next, use Figure 5 An example of the device configuration of an SMF will be described. The SMF consists of a control unit_B700, a network connection unit_B720, and a storage unit_B740. The control unit_B700, network connection unit_B720, and storage unit_B740 are connected via a bus. The SMF can be a node that processes the control plane.

[0062] The control unit_B700 is a functional unit that controls the overall operation and function of the SMF. The control unit_B700 reads and executes various programs stored in the storage unit_B740 as needed, thereby realizing various processes within the SMF.

[0063] The network connection unit_B720 is a functional unit for enabling the SMF to connect with the AMF and / or UPF and / or PCF and / or UDM. That is, the SMF can use the network connection unit_B720 to send and receive user data and / or control information with the AMF and / or UPF and / or PCF and / or UDM and / or NSACF.

[0064] When reference Figure 2 In detail, the SMF located 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.

[0065] The storage unit B740 is a functional unit used to store programs, user data, control information, etc., required for various operations of the SMF.

[0066] The SMF has the following functions: session management functions such as establishing, modifying, and releasing PDU sessions; IP address allocation and management functions for UEs; UPF selection and control functions; UPF configuration functions for routing services to the appropriate destination (sending destination); SM part functions for sending and receiving NAS messages; Downlink Data Notification functions; AN-specific (each AN's) SM information sent to the AN via the N2 interface through the AMF; SSC (Session and Service Continuity mode) functions for sessions; and roaming functions, etc.

[0067] In addition, the storage unit _740 may have the function of storing control information transmitted and received between the UE, access network device, other core network device and DN. [2.5. UPF Device Configuration]

[0068] Next, use Figure 5 An example of the UPF device configuration will be described. The UPF consists of a control unit_B700, a network connection unit_B720, and a storage unit_B740. The control unit_B700, network connection unit_B720, and storage unit_B740 are connected via a bus. The UPF can be a node that processes the control plane.

[0069] The control unit_B700 is a functional unit that controls the overall operation and function of the UPF. The control unit_B700 reads and executes various programs stored in the storage unit_B740 as needed, thereby realizing various processes within the UPF.

[0070] The network connection unit_B720 is a functional unit for connecting the UPF to the base station device (gNB) and / or SMF and / or DN within the 5G AN. That is, the UPF can use the network connection unit_B720 to send and receive user data and / or control information between itself and the base station device (gNB) and / or SMF and / or DN within the 5G AN.

[0071] When reference Figure 2 In detail, the UPF located within the 5GCN can communicate with the gNB via the N3 interface, with the SMF via the N4 interface, with the DN via the N6 interface, and with other UPFs via the N9 interface by using the network connection unit _A620.

[0072] The storage unit B740 is a functional unit used to store the programs, user data, control information, etc. required for the various operations of the UPF.

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

[0074] Furthermore, a UPF can be a gateway for IP and / or non-IP communication. Additionally, a UPF can have the function of transmitting IP communication, or it can have the function of converting non-IP communication to IP communication. Moreover, multiple configured gateways can be gateways connecting the core network_B and a single DN. It should be noted that the UPF can have connectivity with other NFs, and can also connect to various devices via other NFs.

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

[0076] It should be noted that the user plane (also known as the UP) is the user data transmitted and received between the UE and the network. The user plane can use a PDN connection in 4G or a PDU session in 5G for transmission and reception. Furthermore, in the case of EPS, the user plane can also use 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 for transmission and reception. Moreover, in the case of 5GS, the user plane can also transmit and receive data via the interface between the UE and the NG RAN and / or the N3 interface and / or the N9 interface and / or the N6 interface. Hereinafter, the user plane can also be referred to as U-Plane.

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

[0078] Furthermore, the user plane (UP) can be a communication path for sending and receiving user data, and can be composed of multiple bearers. Similarly, the control plane (CP) can be a communication path for sending and receiving control messages, and can be composed of multiple bearers. [2.6. Description of other devices and / or functions and identification information of this embodiment]

[0079] Next, other devices and / or functions, as well as identification information, will be described.

[0080] A network refers to at least a portion of the access network_B, core network_B, and DN. Alternatively, one or more devices included in at least a portion of the access network_B, core network_B, and DN can also be referred to as a network or a network device. That is, the network performing message transmission, reception, and / or processing can mean that devices within the network (network devices and / or control devices) perform message transmission, reception, and / or processing. Conversely, the device within the network performing message transmission, reception, and / or processing can mean that the network itself performs message transmission, reception, and / or processing.

[0081] In addition, NSSF (Network Slice Selection Function) can refer to a network function (also known as NF) that has the ability to select the network slice serving the UE.

[0082] In addition, NWDAF (Network Data Analytics Function) can refer to an NF that has the ability to collect data based on NF and application functions (also known as AF).

[0083] In addition, PCF (Policy Control Function) can refer to an NF that has the function of determining policies for controlling the behavior of the network.

[0084] Furthermore, an NRF (Network Repository Function) can refer to an NF that has service discovery capabilities. An NRF can be an NF that provides information about a discovered NF when it receives a discovery request from another NF.

[0085] Furthermore, the NSACF (Network Slice Admission Control Function) can monitor and control the number of logged-in UEs and / or the number of PDU sessions for each network slice (NS) associated with the NSAC. Additionally, the NSACF can be configured with the maximum allowed number of UEs and / or the maximum number of PDU sessions per NS for each NS associated with the NSAC. Furthermore, the NSACF can also increase or decrease the number of UEs logged into a particular NS without exceeding the maximum allowed number of UEs. The NSACF can also maintain a list of UE IDs logged into the NS associated with the NSAC. Moreover, when the number of UEs logged into an NS increases (e.g., when a UE sends a new login request message to that NS), the NSACF can perform the following functions: verify whether the UE's ID is already included in the list of UE IDs logged into that NS; if the UE's ID is not included in the list, further verify whether the maximum number of UEs per NS has been reached for that NS. Furthermore, during login and / or non-login and / or NSAA procedures, if the registration status of a UE for an NS associated with the NSAC changes, the AMF can request the NSACF regarding the maximum number of UEs for each NS. Additionally, the NSACF may have the function of increasing or decreasing the number of PDU sessions for a given NS without exceeding the maximum number of PDU sessions allowed by that NS. Furthermore, when the number of PDU sessions using an NS increases (e.g., when a UE sends a PDU session establishment request message for that NS), the NSACF may have the function of confirming whether the maximum number of UEs for each NS has been reached. Moreover, the SMF can request the NSACF regarding the maximum number of PDU sessions for each NS during the PDU session establishment and / or PDU session release procedures.

[0086] Furthermore, SM (Session Management) messages (also known as NAS (Non-Access-Stratum) SM messages) can be NAS messages used during SM operations, or control messages exchanged between UE_A10 and SMF_A230 via AMF_A240. Moreover, SM messages can include: PDU session establishment request messages, PDU session establishment accept messages, PDU session establishment reject messages, PDU session modification request messages, PDU session modification command messages, PDU session modification complete messages, PDU session modification command reject messages, PDU session modification reject messages, PDU session release request messages, PDU session release reject messages, PDU session release command messages, and PDU session release complete messages, etc.

[0087] In addition, the SM procedure (also known as the procedure used in SM) may include: PDU session establishment procedure, PDU session modification procedure, and PDU session release procedure. It should be noted that each procedure can be initiated by the UE or by the NW.

[0088] Furthermore, MM (Mobility Management) messages (also known as NAS MM messages) can be NAS messages used in MM procedures, or control messages exchanged between UE_A10 and AMF_A240. Moreover, MM messages can include: Registration request messages, Registration accept messages, Registration reject messages, De-registration request messages (also known as non-login request), De-registration accept messages (also known as non-login accept), Configuration update command messages, Configuration update complete messages, Service request messages, Service accept messages, Service reject messages, Notification messages, and Notification response messages, etc.

[0089] In addition, the MM procedure (also known as the procedure used by MM) may include: registration procedure, de-registration procedure (also known as non-login procedure), generic UE configuration update procedure, authentication and authorization procedure, service request procedure, paging procedure, and notification procedure.

[0090] Furthermore, 5GS (5G System) service can be a connectivity service provided using the core network _B190. Moreover, 5GS service can be a different service from EPS service, or it can be the same service as EPS service.

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

[0092] Furthermore, the PDN (Packet Data Network) type indicates the type of PDN connection, which can be IPv4, IPv6, IPv4v6, or non-IP. Specifying IPv4 indicates that IPv4 is used for data transmission and reception. Specifying IPv6 indicates that IPv6 is used for data transmission and reception. Specifying IPv4v6 indicates that either IPv4 or IPv6 is used for data transmission and reception. Specifying non-IP indicates that communication is conducted not only through IP but also through communication methods other than IP.

[0093] Furthermore, a PDU (Protocol Data Unit) session can be defined as the association between the DN providing PDU connectivity services and the UE, but it can also be a connection established between the UE and an external gateway. In 5GS, the UE establishes a PDU session through the access network_B and core network_B, thereby enabling the UE to send and receive user data with the DN. Here, the external gateway can refer to UPF, SCEF, etc. The UE can use the PDU session to perform the sending and receiving of user data with devices such as application servers configured on the DN.

[0094] In addition, an MA PDU session can refer to a PDU session that provides PDU connectivity services using 3GPP access and / or non-3GPP access.

[0095] It should be noted that each device (UE and / or access network device and / or core network device) can manage the establishment of more than one identification information corresponding to a PDU session. This identification information can include one or more of the following: DNN, QoS rules, PDU session type, application identification information, NSI identification information, and access network identification information, and may further include other information. Furthermore, when multiple PDU sessions are established, the identification information corresponding to each PDU session can be the same or different.

[0096] Furthermore, the DNN (Data Network Name) can be identification information for identifying the core network and / or external networks such as DN. The DNN can also be used to select gateways such as PGW_A30 / UPF_A235 to connect the core network B190. Moreover, the DNN can also be equivalent to the APN (Access Point Name).

[0097] Furthermore, the PDU (Protocol Data Unit / Packet Data Unit) session type indicates the type of PDU session, which can be IPv4, IPv6, Ethernet, or Unstructured. Specifying IPv4 indicates that IPv4 is used for data transmission and reception. Specifying IPv6 indicates that IPv6 is used for data transmission and reception. Specifying Ethernet indicates that Ethernet frames are transmitted and received. Additionally, Ethernet can indicate that communication does not use IP. Specifying Unstructured indicates that point-to-point (P2P) tunneling technology is used to send and receive data to and from application servers, etc., located in the DN. For example, UDP / IP encapsulation technology can also be used as a P2P tunneling technology. It should be noted that IP can also be included in the PDU session type besides the above. IP can be specified if the UE can use both IPv4 and IPv6.

[0098] Furthermore, a PLMN (Public Land Mobile Network) is a communication network that provides mobile wireless communication services. A PLMN is a network managed by a communication operator and can be identified by its PLMN ID. A PLMN whose MCC (Mobile Country Code) and MNC (Mobile Network Code) match the UE's IMSI (International Mobile Subscriber Identity) can be a Home PLMN (HPLMN). Moreover, the UE can maintain a list of equivalent HPLMNs in its USIM to identify one or more EPLMNs. A PLMN different from an HPLMN and / or EPLMN can be a Visited PLMN (VPLMN). The PLMN the UE successfully logs into can be an RPLMN (Registered PLMN; also known as a Login PLMN). It should be noted that services provided by a PLMN can be read as PLMN services, and services provided by an SNPN can be read as SNPN services.

[0099] Furthermore, a network slice (NS) refers to a logical network that provides specific network capabilities and characteristics. The UE and / or network can support network slices (NW slices; NS) in 5GS. Sometimes, network slices are simply referred to as slices.

[0100] Furthermore, a Network Slice Instance (NSI) refers to a network slice that is formed and configured by a collection of instances (entities) of Network Functions (NFs) and the required resources. Here, NF refers to a processing function in the network, adopted or defined in 3GPP. An NSI is an entity that constitutes more than one NS within the core network_B. Furthermore, an NSI can be composed of virtual NFs (Network Functions) generated using an NST (Network Slice Template). Here, an NST is a logical expression of more than one NF associated with a resource request for providing the requested communication service or capability. That is, an NSI can refer to a collection within the core network_B190 composed of multiple NFs. Additionally, an NSI can be a logical network configured to divide transmitted user data according to services, etc. An NS can contain more than one NF. NFs constituting an NS can be devices shared with other NSs or devices not shared with other NSs. A UE and / or devices within the network can be assigned to more than one NS based on login information such as NSSAI and / or S-NSSAI and / or UE usage type and / or more than one NSI ID and / or APN. It should be noted that the UE usage type is a parameter value included in the login information of the UE used to identify the NSI. The UE usage type can be stored in the HSS. The AMF can select the SMF and UPF based on the UE usage type.

[0101] Furthermore, S-NSSAI (Single Network Slice Selection Assistance information) is used to identify NSs. S-NSSAI can consist solely of SST (Slice / Servicetype), or it can consist of SST and SD (Slice Differentiator). Here, SST refers to information indicating the expected actions of the NS in terms of function and service. SD can be information that interpolates the SST when selecting an NSI from multiple NSIs shown by the SST. S-NSSAI can be information specific to each PLMN, or it can be standard information common to all PLMNs. Additionally, the network can store more than one S-NSSAI in the UE's login information as the default S-NSSAI. It should be noted that when the S-NSSAI is the default S-NSSAI, the network can provide UE-related NSs even if the UE does not send a valid S-NSSAI to the network in the login request message.

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

[0103] Furthermore, a configured NSSAI (also known as a Configured NSSAI) is an NSSAI that can be applied to more than one PLMN or SNPN, and is provided to the UE for storage. The UE can store the configured NSSAI for each PLMN or for each NPN (hereinafter, SNPN and / or PNI-NPN are sometimes collectively referred to as NPN). The configured NSSAI can be information configured by the network (PLMN or SNPN). Furthermore, the S-NSSAI included in the configured NSSAI can be expressed as a configured S-NSSAI. Furthermore, the configured S-NSSAI can be configured to include both S-NSSAI and mapped S-NSSAI. Additionally, the configured NSSAI can include both the configured NSSAI stored in the UE and the configured NSSAI sent to the UE from the network.

[0104] Furthermore, the requested NSSAI (also known as Requested NSSAI) is the NSSAI provided by the UE to the network (the current PLMN or NPN) during the login process. The S-NSSAI included in the requested NSSAI can be an S-NSSAI selected from one or more S-NSSAIs included in the configured NSSAI and / or allowed NSSAI that correspond to the current PLMN or NPN. Additionally, the S-NSSAI included in the requested NSSAI can be an S-NSSAI selected without including one or more S-NSSAIs included in the pending NSSAI and / or rejected NSSAI. Furthermore, the requested NSSAI can be information indicating the network slice the UE wants to log in to or access. Moreover, the S-NSSAI included in the requested NSSAI can be expressed as a requested S-NSSAI. Furthermore, the NSSAI request may include NAS messages such as login request messages sent from the UE to the network (PLMN or SNPN) and / or RRC (Radio Resource Control) messages that include NAS (Non-Access-Stratum) messages. Additionally, the NSSAI request may contain both the NSSAI request stored in the UE and the NSSAI request sent from the UE to the network (PLMN or SNPN).

[0105] Furthermore, allowed NSSAI (also known as Allowed NSSAI) indicates information about one or more network slices that the UE is allowed to connect to. In other words, allowed NSSAI can be information that identifies network slices that allow the network to connect to the UE. Additionally, allowed NSSAI can be information indicating more than one S-NSSAI that can be used in the current PLMN or SNPN within the current login area. The UE and the network store and manage allowed NSSAI for each type of access (3GPP access or non-3GPP access) as information for the UE. S-NSSAIs included in allowed NSSAI can be expressed as allowed S-NSSAI. Allowed S-NSSAI can be configured to include both S-NSSAI and mapped S-NSSAI. Furthermore, allowed NSSAI can include allowed NSSAI stored in the UE and allowed NSSAI sent from the network to the UE.

[0106] Furthermore, a mapped S-NSSAI (also known as a Mapped S-NSSAI) can be an HPLMN S-NSSAI mapped to the S-NSSAI of the logged-in PLMN in a roaming scenario. Additionally, a mapped S-NSSAI can be an S-NSSAI used primarily when the UE is roaming, or an S-NSSAI not used when the UE is not roaming (also known as non-roaming). Furthermore, the UE can store mapped S-NSSAIs mapped to one or more S-NSSAIs included in the configured NSSAIs and the allowed NSSAIs for each access type. Additionally, the UE can store one or more mapped S-NSSAIs included in the rejected NSSAIs or mapped S-NSSAIs corresponding to the S-NSSAIs included in the rejected NSSAIs. Moreover, a mapped NSSAI can include mapped NSSAIs stored in the UE and mapped NSSAIs sent from the network to the UE.

[0107] Furthermore, a rejected NSSAI (also known as a Rejected NSSAI) indicates that the UE is not permitted access to one or more network slices. In other words, a rejected NSSAI identifies network slices that are not allowed for network-UE connection. A rejected NSSAI can be a combination of one or more S-NSSAIs and a rejection reason value (hereinafter also referred to as reason value or rejection reason). Here, the rejection reason value refers to the information indicating the reason why the network rejects the corresponding S-NSSAI. The UE and the network can appropriately store and manage rejected NSSAIs based on the corresponding rejection reason values ​​established for each S-NSSAI. Moreover, rejected NSSAIs can also be included in NAS messages sent from the network to the UE, such as login acceptance messages, configuration update commands, login rejection messages, etc., or in RRC messages that include NAS messages. The S-NSSAIs included in a rejected NSSAI can also be expressed as rejected S-NSSAIs (rejected S-NSSAI). Here, rejected NSSAI can mean any of the first to fourth rejected NSSAIs. Furthermore, "reject S-NSSAI" can also mean "reject S-NSSAI" included in any of the first to fourth "reject NSSAIs". "Reject NSSAI" can be any of the first to fourth "reject NSSAIs" and the pending NSSAI, or a combination thereof. "S-NSSAI" included in "reject NSSAI" can be expressed as "reject S-NSSAI". "Reject S-NSSAI" can be structured as including S-NSSAI and mapping S-NSSAI.

[0108] Here, the first rejected NSSAI can be a rejected NSSAI for the current PLMN or SNPN. In other words, the first rejected NSSAI can be an NSSAI that is unavailable in the current PLMN or SNPN. Furthermore, the first rejected NSSAI can also be a set of more than one S-NSSAI that is unavailable in the current PLMN or SNPN and is included in the S-NSSAIs included in the rejected NSSAI. The first rejected NSSAI can be a rejected NSSAI for the current PLMN or SNPN from the 5GS. Additionally, the first rejected S-NSSAI can be a rejected S-NSSAI for the current PLMN or SNPN, or it can be an S-NSSAI included in a rejected NSSAI for the current PLMN or SNPN. Furthermore, the first rejected NSSAI can be a rejected NSSAI stored by the UE and / or the NW, or it can be a rejected NSSAI sent from the NW to the UE. When the first rejection NSSAI is sent from the NW to the UE, the first rejection NSSAI can be a combination of one or more S-NSSAIs and a reason value. The reason value can indicate "S-NSSAI not available in the current PLMN or SNPN," or it can mean that the corresponding S-NSSAI is unavailable in the current PLMN or SNPN.

[0109] Furthermore, the First Denial NSSAI can be valid throughout the PLMN or SNPN login process. In other words, the UE and / or NW can treat the First Denial NSSAI and the S-NSSAI included within it as access type-independent information. That is, the First Denial NSSAI can be valid for both 3GPP access and non-3GPP access.

[0110] The UE can delete the First Rejection NSSAI from storage when it transitions to a non-login state for the current PLMN or SNPN in both 3GPP access and non-3GPP access. In other words, the UE can delete the First Rejection NSSAI when it transitions to a non-login state for the current PLMN or SNPN via some access, or when it successfully logs into a new PLMN or SNPN via some access, or when it fails to log into a new PLMN via some access and transitions to a non-login state, and when the UE is in a state where it has not logged in through the other access (non-login state).

[0111] Furthermore, the S-NSSAI included in the first denial NSSAI in the UE's storage section can be considered unavailable throughout the current PLMN or SNPN. That is, the UE can be in a state where the MM procedure and / or SM procedure that use the S-NSSAI is prohibited throughout the current PLMN or SNPN.

[0112] Furthermore, the second rejected NSSAI can be a rejected NSSAI for the current registration area (also known as the registration area). In other words, the second rejected NSSAI can be an NSSAI that is unavailable in the current registration area. Additionally, the second rejected NSSAI can also be a set of one or more S-NSSAIs that are unavailable in the current registration area, included in the S-NSSAI requested by the UE. Furthermore, the second rejected NSSAI can also be a rejected NSSAI for the current registration area from the 5GS. Furthermore, the second rejected NSSAI can also be a rejected NSSAI stored by the UE and / or NW, or a rejected NSSAI sent from the NW to the UE. When the second rejected NSSAI is a rejected NSSAI sent from the NW to the UE, the second rejected NSSAI can be information including a combination of one or more S-NSSAIs and a reason value. This reason value can indicate "S-NSSAI not available in the current registration area," or it can mean that the S-NSSAI corresponding to the reason value is unavailable in the current registration area.

[0113] Furthermore, the second rejection NSSAI can be valid within the current login area. That is, the UE and / or NW can treat the second rejection NSSAI and the S-NSSAI included in it as information for each access type. In other words, the second rejection NSSAI can be information valid for both 3GPP access and non-3GPP access. Also, the UE can delete the second rejection NSSAI from storage once it transitions to a non-login state for a certain access type.

[0114] Furthermore, the S-NSSAI included in the second denial NSSAI in the UE's storage can be considered unavailable in the current login zone. That is, the UE can be in a state where the MM procedure and / or SM procedure using the S-NSSAI is prohibited throughout the entire current login zone.

[0115] Furthermore, the third rejection NSSAI is an S-NSSAI that requires an NSSAA, and is a set of one or more S-NSSAIs for which an NSSAA has failed or been cancelled. The third rejection NSSAI can be an NSSAI stored by the UE and / or the NW, or it can be sent from the NW to the UE. When a third rejection NSSAI is sent from the NW to the UE, it can be information including a combination of one or more S-NSSAIs and a rejection reason value. The rejection reason value can be "S-NSSAI is not available due to the failed or revoked network slice-specific authorization and authentication," or it can be information indicating that an NSSAA has failed or been cancelled for an S-NSSAI corresponding to the rejection reason value.

[0116] Furthermore, the Third Denial NSSAI is valid throughout the PLMN login process. In other words, the UE and / or NW can treat the Third Denial NSSAI and the S-NSSAI included within it as access type-independent information. That is, the Third Denial NSSAI can be valid for both 3GPP and non-3GPP access. The Third Denial NSSAI can be a different NSSAI from the Denial NSSAI. The Third Denial NSSAI can also be the First Denial NSSAI.

[0117] The third rejection NSSAI is a rejection NSSAI used by the UE to identify slices rejected by the core network due to NSSAA failure or cancellation. Specifically, while storing the third rejection NSSAI, the UE does not initiate a login request process for the S-NSSAI included in the third rejection NSSAI. The third rejection NSSAI may include identification information received from the core network that corresponds to one or more rejection reason values ​​indicating NSSAA failure. The third rejection NSSAI is access type-independent information. Specifically, when the UE stores the third rejection NSSAI, the UE may not attempt to send login request messages including the S-NSSAI included in the third rejection NSSAI to either 3GPP access or non-3GPP access parties. Alternatively, the UE may send login request messages including the S-NSSAI included in the third rejection NSSAI based on UE policy. Alternatively, the UE may delete the third rejection NSSAI based on UE policy and transition to a state where it can send login request messages including the S-NSSAI included in the third rejection NSSAI. In other words, if the UE sends a login request message that includes the S-NSSAI included in the third rejection NSSAI based on the UE policy, the UE can remove the S-NSSAI from the third rejection NSSAI.

[0118] Furthermore, the S-NSSAI included in the third denial NSSAI in the UE's storage section can be considered unavailable throughout the current PLMN or SNPN. That is, the UE can be in a state where MM procedures and / or SM procedures using this S-NSSAI are prohibited throughout the entire current login area.

[0119] Furthermore, the fourth rejection NSSAI can be a rejection NSSAI for the current tracking area. In other words, the fourth rejection NSSAI can be an NSSAI that is unavailable in the current tracking area.

[0120] Furthermore, a fourth rejection NSSAI can also be a rejection NSSAI for the current tracking area in the current registration area. In other words, a fourth rejection NSSAI can also be an NSSAI that is unavailable in the current tracking area of ​​the current registration area.

[0121] In addition, the fourth rejection of NSSAI can also be an NSSAI that is not available in the current tracking zone of the current login zone, or an NSSAI that is available in other tracking zones of the current login zone.

[0122] In addition, the fourth rejection of NSSAI can also be an NSSAI that is not available in the current tracking area of ​​the current login area, or an NSSAI that is not available in other tracking areas of the current login area and other (different from the current login area) login areas.

[0123] In addition, the fourth rejection NSSAI can also be a set of S-NSSAIs included by the UE in the request NSSAI, or a set of S-NSSAIs sent by the AMF using an S-NSSAI that is not available in the current tracking area or a rejection reason indicating that the S-NSSAI is not available in the current tracking area.

[0124] Furthermore, in a roaming scenario (during roaming), the fourth rejection NSSAI may include more than one S-NSSAI for the current PLMN, and may also include a set of mapped S-NSSAIs where available.

[0125] Furthermore, the fourth rejection NSSAI can be a rejection NSSAI stored by the UE and / or NW, or it can be a rejection NSSAI sent from the NW to the UE. When the fourth rejection NSSAI is a rejection NSSAI sent from the NW to the UE, the fourth rejection NSSAI can be information including a combination of one or more S-NSSAIs and a reason value. This reason value can be the twelfth identification information.

[0126] Furthermore, the fourth rejection NSSAI can be valid for both 3GPP and non-3GPP access. In other words, the UE and / or NW can treat the fourth rejection NSSAI as either access type independent or access type dependent. Further, the UE and / or NW can manage and / or store the fourth rejection NSSAI for each access type, or they can choose not to manage and / or store it for each access type.

[0127] Furthermore, pending NSSAI (also known as pending NSSAI) is a set of one or more S-NSSAIs that require network slice-specific authentication (NSSAA) and are unusable in the current PLMN without completing NSSSAA. Pending NSSAIs can be 5GS NSSAIs rejected due to NSSAA or pending NSSAIs. Pending NSSAIs can be NSSAIs stored by the UE or NW, or NSSAIs sent from the NW to the UE. It should be noted that pending NSSAIs are not limited to rejected NSSAIs and can also be NSSAIs different from rejected NSSAIs. When pending NSSAIs are sent from the NW to the UE, they can be information including a combination of one or more S-NSSAIs and rejection reason values. At this time, the rejection reason value can be "S-NSSAI is pending for the S-NSSAI", which can indicate that the UE is prohibited or has its use of the S-NSSAI established with the rejection reason value until the NSAA for the S-NSSAI is completed.

[0128] Furthermore, the pending NSSAI is valid throughout the PLMN login process. In other words, the UE and / or NW can treat the S-NSSAI included in the third denial NSSAI and the pending NSSAI as access type-independent information. That is, the pending NSSAI can be information valid for both 3GPP access and non-3GPP access. The pending NSSAI can be a different NSSAI than the denial NSSAI. The pending NSSAI can also be the first denial NSSAI.

[0129] Furthermore, a pending NSSAI is an NSSAI consisting of one or more S-NSSAIs that the UE uses to identify the slice pending the process. Specifically, the UE does not initiate a login request process for the S-NSSAIs included in the pending NSSAI while storing the pending NSSAI. In other words, the UE does not use the S-NSSAIs included in the pending NSSAI during the login process until the NSSAA for the S-NSSAIs included in the pending NSSAI is completed. The pending NSSAI is identification information received from the core network that includes one or more S-NSSAIs corresponding to the pending rejection reason value used for the NSSAA. The pending NSSAI is access type-independent information. Specifically, when the UE stores the pending NSSAI, the UE does not attempt to send login request messages including the S-NSSAIs included in the pending NSSAI to either 3GPP access or non-3GPP access parties.

[0130] A tracking area is one or more ranges managed by the core network that can be represented as location information for UE_A10. A tracking area can consist of multiple cells. Furthermore, a tracking area can be a range used for broadcasting control messages such as paging, or a range that UE_A10 can move within without a handover process. Moreover, a tracking area (TA) can be a routing area or a location area, as long as it is the same as these areas. A tracking area can be identified by a TAI (Tracking Area Identity) consisting of a TAC (Tracking Area Code) and a PLMN.

[0131] A registration area (also known as a TA) is a set of one or more Tracking Areas (TAs) assigned to a UE by the AMF. It is important to note that it is preferable for UE_A10 to move without transmitting or receiving tracking area update signals while moving within one or more TAs included in the registration area. In other words, a registration area can be a group of information representing areas where UE_A10 can move without performing a tracking area update process. Registration areas can be identified through a TAI list consisting of one or more TAIs.

[0132] UE ID refers to information used to identify a UE. Specifically, for example, UE ID can be SUCI (Subscription Concealed Identifier), SUPI (Subscription Permanent Identifier), GUTI (Globally Unique Temporary Identifier), IMEI (International Mobile Subscriber Identity), IMEISV (IMEI Software Version), or TMSI (Temporary Mobile Subscriber Identity). Alternatively, UE ID can be other information set within an application or network. Furthermore, UE ID can also be information used to identify a user.

[0133] Network Slice-Specific Authentication and Authorization (NSSAA) refers to the authentication and authorization functions specific to network slices. NSAA enables UE authentication and authorization outside the core network, such as with third parties. PLMNs and network devices with NSAA capabilities can execute the NSAA procedure for a specific S-NSSAI based on the UE's login information. Furthermore, UEs with NSAA capabilities can manage and store pending NSSAI rejections and / or failed NSSAI rejections for NSAA purposes. In this document, NSAA is sometimes referred to as the network slice-specific authentication and authorization process, or simply the authentication and authorization process.

[0134] S-NSSAI requiring NSAAA is an S-NSSAI that is managed by the core network and / or core network devices. The core network and / or core network devices can store S-NSSAI requiring NSAAA by establishing a correspondence between information indicating whether S-NSSAI is required and NSAAA is required. The core network and / or core network devices can also store S-NSSAI requiring NSAAA by establishing a correspondence between information indicating whether NSAAA has been completed or information indicating the status of NSAAA being allowed or successfully completed. The core network and / or core network devices can manage S-NSSAI requiring NSAAA as information independent of the access network.

[0135] Furthermore, a UE in single login mode has only one active MM state. That is, a UE in single login mode can only be active in either the RM state (5GMM state) in the 5GC or the EMM state in the EPC. Additionally, a UE in single login mode is in 5GC NAS mode when connected to the 5GC and in EPC NAS mode when connected to the EPC. Moreover, a UE in single login mode can only log in to either the 5GC or the EPC; therefore, EPS-GUTI (also known as 4G-GUTI) mapping to 5G-GUTI is required when moving between the EPC and 5GC.

[0136] Furthermore, a UE in dual login mode can independently log in to both 5GC and EPC. A UE in dual login mode can independently maintain 5G-GUTI and EPS-GUTI (also known as 4G-GUTI).

[0137] Furthermore, SNPN is a type of 5GS NPN deployed for non-public use. It operates through the NPN operator and does not rely on the NF provided by the PLMN. SNPN can be identified by a combination of the PLMN ID and NID (Network Identifier). UEs capable of using SNPN can support SNPN access mode (also known as SNPN access operation mode). UEs configured to operate in SNPN access mode can select and log in to the SNPN, but may not be able to select the PLMN. UEs configured to operate in SNPN access mode can perform the SNPN selection process, but may not be able to perform the PLMN selection process. Even if a UE can utilize SNPN (SNPN enabled), a UE not configured to operate in SNPN access mode may not be able to select and log in to the SNPN, but may be able to select the PLMN. Furthermore, a UE not configured to operate in SNPN access mode may not be able to perform the SNPN selection process, but may perform the PLMN selection process.

[0138] Furthermore, UEs operating in SNPN access mode can select the SNPN via Uu (3GPP access). Alternatively, UEs operating in SNPN access mode can also select the SNPN via Uu or NWu, where Uu or NWu is established via a PDU session provided by the PLMN, and the PLMN is selected via Uu or NWu (non-3GPP access). Additionally, UEs not operating in SNPN access mode can also select the PLMN via Uu or NWu, where Uu or NWu is established via a PDU session provided by the SNPN, and the SNPN is selected via Uu or NWu (non-3GPP access).

[0139] It should be noted that SNPN access modes can be managed and / or applied on an access-by-access basis. That is, they can be managed and / or applied separately through 3GPP access and non-3GPP access. In other words, activating or disabling SNPN access modes for 3GPP access can be independent of activating or disabling SNPN access modes for non-3GPP access. Specifically, if an SNPN access mode for 3GPP access is activated, an SNPN access mode for non-3GPP access can also be activated or disabled. Furthermore, if an SNPN access mode for 3GPP access is disabled, an SNPN access mode for non-3GPP access can also be activated or disabled.

[0140] Here, the SNPN access mode for 3GPP access can also be called the SNPN access mode over 3GPP access or the SNPN access mode via 3GPP access.

[0141] In addition, the SNPN access mode for non-3GPP access can also be called the SNPN access mode over non-3GPP access or the SNPN access mode via non-3GPP access.

[0142] Furthermore, "activate" can be replaced with "action," and "disable" can be replaced with "no action." That is, activating the SNPN access mode for 3GPP access means taking action within the SNPN access mode for 3GPP access. Conversely, disabling the SNPN access mode for 3GPP access means not taking action within the SNPN access mode for 3GPP access. Similarly, activating the SNPN access mode for non-3GPP access means taking action within the SNPN access mode for non-3GPP access. And again, disabling the SNPN access mode for non-3GPP access means not taking action within the SNPN access mode for non-3GPP access.

[0143] Furthermore, when a UE roams between SNPNs, the SNPN can be classified as the Home SNPN (also known as the HSNPN) and the Visited SNPN (also known as the VSNPN). It should be noted that when a UE does not roam between SNPNs, the SNPN can be considered the same as the Home SNPN.

[0144] Furthermore, the home SNPN can refer to the SNPN that the UE can log in to as its home. Additionally, the home SNPN can refer to the SNPN that the UE first selects during SNPN selection. Furthermore, the home SNPN can refer to an SNPN whose information, at least a portion of its SNPN identity (also known as SNPN ID), matches at least a portion of the information included in the UE's IMSI. Additionally, the home SNPN can refer to an SNPN whose MCC and MNC, included in the PLMN identity (also known as PLMN ID) of its SNPN identity (also known as SNPN ID), match the MCC and MNC included in the UE's IMSI.

[0145] Furthermore, a visited SNPN can refer to an SNPN that the UE can register as other than its home SNPN. A visited SNPN can also refer to an SNPN that the UE does not register as its home SNPN. A visited SNPN can also refer to an SNPN that the UE does not initially select during SNPN selection. A visited SNPN can also refer to an SNPN in which at least a portion of the information included in the SNPN identifier (also known as SNPN ID) does not match at least a portion of the information included in the UE's IMSI. Furthermore, a visited SNPN can also refer to an SNPN in which the MCC and MNC included in the PLMN identifier (also known as PLMN ID) of the SNPN identifier (also known as SNPN ID) do not match the MCC and MNC included in the UE's IMSI.

[0146] Furthermore, an equivalent HSNPN (also known as an equivalent Home SNPN or EHSNPN) can be an SNPN considered equivalent to the current SNPN (here, the Home SNPN, also known as an HSNPN) during SNPN selection and / or cell selection and / or cell reselection. Additionally, an equivalent HSNPN can refer to more than one SNPN included in the equivalent HSNPN list, or more than one SNPN not included in the equivalent VSNPN list.

[0147] Furthermore, an equivalent VSNPN (also known as an equivalent Visited SNPN, EVSNPN) can refer to an SNPN that is considered equivalent to the current SNPN (here, the visited SNPN, also known as a VSNPN) in SNPN selection and / or cell selection and / or cell reselection. Additionally, an equivalent VSNPN can also refer to more than one SNPN included in the equivalent VSNPN list, or more than one SNPN not included in the equivalent HSNPN list.

[0148] Furthermore, an equivalent SNPN (also known as an ESNPN) can be a concept that includes equivalent HSNPN and / or equivalent VSNPN. That is, an ESNPN can refer to an equivalent HSNPN and / or an equivalent VSNPN.

[0149] In addition, the SNPN that the UE successfully logs in to can be an RSNPN (Registered SNPN; also known as the login SNPN).

[0150] Next, in this embodiment, the identification information transmitted, received, stored, and / or managed by each device will be described.

[0151] It should be noted that the UE and / or base station and / or AMF and / or SMF and / or other core network devices or network functions may pre-store information and generate new information as needed. Furthermore, when exchanging this information, the receiving side may store the received information and perform actions based on that information. [3. First Implementation Method]

[0152] First, the process used in the first embodiment will be described. The process used in the first embodiment may include the MM process and the SM process described above.

[0153] It should be noted that, in the first embodiment, as Figure 2As described herein, the example given is the case where HSS and UDM, PCF and PCRF, SMF and PGW-C, and UPF and PGW-U are configured as the same device / function (i.e., the same physical hardware, the same logical hardware, or the same software). However, the content described in this embodiment can also be applied to cases where they are configured as different devices / functions (i.e., different physical hardware, different logical hardware, or different software). For example, data can be sent and received directly between them, via the N26 interface between AMF and MME, or via UE.

[0154] The AMF can determine the RAT type for NR satellite access. Here, NR satellite access can mean a connection between the UE and the core network using NR and / or 5G communication functions via satellite. In other words, when the UE connects to the network via a satellite connection, the AMF can determine the RAT type. It should be noted that in this specification, NR satellite access is sometimes simply referred to as satellite access. Furthermore, NR satellite access can include NR(LEO), NR(MEO), NR(GEO), and NR(OTHERSAT). Specifically, NR(LEO) can mean a connection between the UE and the core network using NR and / or 5G communication functions via a LEO satellite. Similarly, NR(MEO) can mean a connection between the UE and the core network using NR and / or 5G communication functions via a MEO satellite. Finally, NR(GEO) can mean a connection between the UE and the core network using NR and / or 5G communication functions via a GEO satellite. In addition, NR (OTHERSAT) can refer to a satellite connection between the UE and the core network using NR and / or 5G communication functions other than LEO, MEO, and GEO. Furthermore, RAT type values ​​such as NR (LEO), NR (MEO), NR (GEO), and NR (OTHERSAT) can be used in 5GC to identify the type of satellite connection.

[0155] In addition, when the UE uses a satellite connection to connect to the NR or network (when connecting using an NR satellite connection), the N2 interface can be used to provide information indicating the type of NR satellite connection (which can also be RAT type) between the AMF and the base station.

[0156] Furthermore, the TA (Transmission Area) of a cell (communication area) of a satellite-connected RAT type can be different from the TA of cells of other RAN types, or it can be different from the TA of a terrestrial RAT type.

[0157] In addition, the AMF can initiate a non-login process to delog the UE from the base station when it receives a release request related to the N2 connection (e.g., an N2 UE context release request) along with a reason value indicating that the UE is not in the service area of ​​the PLMN.

[0158] In addition, the same network selection options (PLMN selection and access network selection) for satellite connections are available as for terrestrial network selection.

[0159] Furthermore, in satellite connectivity, a UE with location capability can use information related to its location to select a PLMN that can perform actions or connections at that location.

[0160] Furthermore, for mobile cells relative to satellite connections, that is, cells that move with the satellite, it can be said that more than one TAC is supported for each PLMN.

[0161] In addition, a UE that logs into a PLMN (a PLMN that provides satellite connectivity) can connect to a cell. If the TAC for the RPLMN or a PLMN that is equivalent to the RPLMN (also known as an EPLMN) is part of the UE's login area, the login process may not be performed (the login process performed with movement).

[0162] Furthermore, if the TAC for the RPLMN or a PLMN with an equivalent relationship to the RPLMN is not in the UE's login area, the UE can perform a login procedure (a login procedure performed with movement).

[0163] In addition, when indicating the last visited TAI during the login process, the UE may indicate at least a portion of the TAIs supported in cells whose TAIs for RPLMN or PLMNs with an equivalent relationship to RPLMN were connected prior to the login process and are part of the UE's login area.

[0164] Furthermore, even when the cell moves across the Earth's surface, the base station can change the TAC value and broadcast the changed TAC value through the cell's system information.

[0165] Furthermore, a base station can broadcast one TAC per PLMN within a cell, and can also change the TAC value as the cell moves. Additionally, a base station can broadcast more than one TAC per PLMN within a cell, and can also add or delete TAC values ​​as the cell moves.

[0166] In addition, the base station can also send the TAI for the selected PLMN to the AMF.

[0167] In addition, the base station can also indicate the TAI where the UE is located to the AMF. The AMF can then use the TAI received from the base station to generate a suitable login area for the UE.

[0168] Furthermore, the AMF and UE can receive more than one TAI broadcast from the base station. Additionally, if some or all of the received TAIs are blocked based on the UE's subscription data, the AMF may consider the UE to be in a forbidden area. Similarly, if some or all of the received TAIs are blocked, the UE may consider itself to be in a forbidden area. Furthermore, if at least one of the received TAIs is not blocked, the UE may consider itself not to be in a forbidden area.

[0169] Furthermore, the AMF can receive more than one TAI broadcast from the base station. Additionally, the AMF can provide service area restrictions consisting of allowed or non-allowed areas.

[0170] Furthermore, the login process can begin when the appropriate cell for multiple TAs is indicated to the RPLMN, i.e., when all of these multiple TAs exist outside the UE's login area in CM-CONNECTED and CM-IDLE states.

[0171] In addition, the UE can send the last visited TAI to the AMF to help the AMF generate a login area for the UE.

[0172] In addition, the AMF can verify the UE's location during the login process or service request process, and can also determine whether the PLMN can take action at the UE's location.

[0173] In addition, the UE can select another PLMN when it receives a login rejection message or service rejection message that includes a reason value indicating that the PLMN does not allow action at the current location of the UE.

[0174] Furthermore, the AMF can initiate a network-led non-login process when it detects that the PLMN the UE is logged into does not allow action at the current UE location. In this case, the AMF can send a non-login request message to the UE, including a reason value indicating that action is not allowed at the current UE location.

[0175] Furthermore, the AN (Access Network) release procedure can be initiated when a UE with a satellite connection moves outside the service area of ​​the PLMN (the communicable area within the PLMN). Here, the AN release procedure can be performed to release connections between the AN and AMF for the UE, release N3 user plane connections (connections between the AN and UPF), release connections between the UE and the AN, release AN resources, etc.

[0176] Furthermore, during the AN release process, if the reason value included in the N2 UE context release request sent from the AN to the AMF indicates that the UE requesting release is due to the UE having moved outside the service area of ​​the PLMN while maintaining a satellite connection, the AMF may not continue the AN release process and instead begin a non-login process to deregister the UE.

[0177] In addition, AMF can also verify the UE's location during the PDU session establishment process.

[0178] The UE can store a list of PLMNs (PLMNs not allowed to operate at the present UE location). The information included in this list (also called entries) may include the PLMN ID, the UE's location information, and the UE's distance information. Here, the PLMN ID may be the PLMN ID of the PLMN that sent a message including a 5GMM reason value indicating that operation is not allowed at the current UE location. Furthermore, the UE's location information may be the location information of the UE that received the message including a 5GMM reason value indicating that operation is not allowed at the current UE location. Additionally, the UE's distance information may be, for example, information related to the distance between the satellite and the UE.

[0179] Furthermore, the UE can delete an existing entry with the same PLMN ID before storing a new entry in the list of PLMNs where operation is not permitted at the current UE location. Additionally, a timer associated with a new entry can be started when storing a new entry in the list of PLMNs where operation is not permitted at the current UE location. Here, if a lower bound timer value is received from the network side, the UE can use a timer value higher than that value to start the timer. It should be noted that the lower bound timer value can include control messages such as login rejection messages, DL NASTRANSPORT messages, non-login request messages, and service rejection messages, which are received by the UE from the core network (e.g., AMF or SMF). Furthermore, if a lower bound timer value is not received from the network side, the UE can use a timer value set based on installation to start the timer.

[0180] Furthermore, given the current location of the UE, the UE's location information is stored in the entry of the PLMN, and if the distance from the current UE's location is greater than a specified value, the UE can connect to a PLMN included in the list of PLMNs where actions are not permitted at the current UE's location.

[0181] Furthermore, when the timer associated with the entry of the PLMN expires, the UE can connect to a PLMN included in the list of PLMNs whose operation is not permitted at the current UE location.

[0182] In addition, when the connection is used for emergency services, the UE can connect to PLMNs included in the list of PLMNs that are not allowed to operate at the current UE location.

[0183] Furthermore, the list of PLMNs whose current location does not allow operation can hold more than three entries. Additionally, if the list of PLMNs whose current location does not allow operation is full, and a new entry is added, the UE can delete the oldest entry.

[0184] In addition, aside from the case of logging in for emergency services, if the UE successfully logs in to or logs in to a PLMN stored in the entry, the UE can delete the entry from the list of PLMNs that are not allowed to operate at the current UE location.

[0185] In addition, when the timer associated with an entry expires, the UE can delete the entry from the list of PLMNs that are not allowed to operate at the current UE location.

[0186] Furthermore, given the current location of the UE, the PLMN's entry stores the UE's location information, and if the distance from the current UE's location is greater than a specified value, the UE can delete the entry from the list of PLMNs where actions are not permitted at the current UE's location.

[0187] In addition, when the UE is in the 5GMM-DEREGISTERED.LIMITED-SERVICE state, and an entry is removed from the list of PLMNs that do not allow action at the current UE location, the UE can select a PLMN.

[0188] Furthermore, when the power supply to the UE is cut off, the UE can maintain a list of PLMNs that are not allowed to operate at the current UE location in non-volatile memory.

[0189] In addition, when a USIM is removed, the UE can remove it from the list of PLMNs that are not allowed to operate at the current UE location.

[0190] Furthermore, the AMF can have the function of determining the waiting range (also known as the waiting range, wait range, or wait range) based on network settings. Additionally, the AMF can send this waiting range and / or information related to the waiting range, and / or information including the waiting range, to the UE via login procedures and / or configuration update procedures and / or service request procedures and / or non-login procedures. For example, the AMF can include the waiting range and / or information related to the waiting range, and / or information including the waiting range, in login acceptance messages and / or login rejection messages and / or configuration update commands and / or non-login request messages and / or service acceptance messages and / or service rejection messages and / or NAS messages when sending them to the UE.

[0191] Furthermore, the UE can calculate a wait timer (also called a wait timer) based on a wait range and / or information related to the wait range and / or information including the wait range received from the network. In other words, the wait range can represent the range used to determine the wait timer. Additionally, the wait timer can refer to a wait timer value or a timer value used to set a timer used in the UE. Alternatively, the network can generate a wait timer based on the wait range on behalf of the UE, sending the control message containing the wait range and / or information related to the wait range and / or information including the wait range to the UE. In this case, the UE can use the received wait timer.

[0192] Furthermore, the UE can start a timer using a wait timer after satellite communication becomes available again following a period of inaccessibility (also known as when returning to coverage from discontinuous coverage). Additionally, the UE can refrain from sending control messages (such as NAS messages and / or RRC messages) until the timer expires. In other words, a timer using a wait timer can be a timer started after satellite communication becomes available again following a period of inaccessibility; it is a timer used to set the period during which the UE cannot send control messages.

[0193] Furthermore, UEs capable of satellite communication can receive waiting ranges from the network during login and / or configuration update and / or service request and / or non-login processes performed in the first PLMN via the first satellite. It should be noted that the UE can send UE capability information to the network, indicating its ability to calculate / generate a waiting timer based on that waiting range, during the same or earlier process as receiving the waiting range. In other words, to determine whether the NW side can send a waiting range, the UE can send UE capability information indicating whether it supports a waiting range and / or a waiting timer and / or a timer for using the waiting timer. The network can then send waiting ranges only to UEs with that capability based on the received UE capability information. Then, if the UE cannot communicate via the first satellite but can communicate via a second satellite connected to the first PLMN, the UE can select the first PLMN. It should be noted that if the first PLMN has already been selected, the UE may not need to reselect it. The UE can then generate a waiting timer based on the waiting range. The UE can start the timer for using the waiting timer immediately after generating it, or it can start the timer for using the waiting timer when a specified time or specified conditions are met. Then, if an emergency call is made while the timer is active, the UE can stop the timer and execute the login procedure and / or MM procedure and / or SM procedure for the emergency call. Alternatively, if no emergency call is made while the timer is active, the UE can execute the login procedure and / or MM procedure and / or SM procedure in the first PLMN after the timer expires. Furthermore, the aforementioned PLMN can be replaced with a PLMN and / or RAT. It should be noted that the first PLMN can be an HPLMN or a VPLMN. Additionally, if communication via a second satellite connected to the first PLMN is again impossible before the timer expires using the waiting timer, the UE can stop the timer and perform PLMN selection to select another PLMN that can be connected via satellite (e.g., the second or third PLMN) and / or another PLMN that can be connected without satellite (e.g., the fourth PLMN). Furthermore, if communication via satellite to the second PLMN is again impossible before the timer expires using the waiting timer, the UE can perform PLMN selection without stopping the timer to select another PLMN that can be connected via satellite and / or another PLMN that can be connected without satellite. In addition, if the UE is unable to conduct satellite communication with the second PLMN again before the timer expires, it can perform PLMN selection to select other PLMNs that can be connected via satellite and / or other PLMNs that can be connected without satellite, and then stop the timer.Furthermore, during a login process within a PLMN, after the network sends the waiting range to the UE, during another login process and / or configuration update process within the same PLMN, the network updates the waiting range and / or the waiting timer and / or the timer using the waiting timer by sending the updated waiting range to the UE. In other words, after the UE receives the waiting range from the network during a login process within a PLMN, during another login process and / or configuration update process within the same PLMN, it updates the waiting range and / or the waiting timer and / or the timer using the waiting timer by receiving the updated waiting range from the network.

[0194] Furthermore, UEs capable of satellite communication can receive waiting ranges from the network during login and / or configuration update and / or service request and / or non-login processes performed in the first PLMN via the first satellite. It should be noted that the UE can send UE capability information to the network, indicating its ability to calculate / generate a waiting timer based on the waiting range, during the same or earlier process as receiving the waiting range. In other words, to determine whether the NW side can send a waiting range, the UE can send UE capability information indicating whether it supports a waiting range and / or a waiting timer and / or uses a timer with a waiting timer. The network can then send waiting ranges only to UEs with that capability based on the received UE capability information. Then, if the UE cannot communicate via the first satellite but can communicate via a second satellite connected to the second PLMN, the UE can select the second PLMN. The UE can then generate a waiting timer based on the waiting range. The UE can then start the timer using the waiting timer immediately after generating the waiting timer, or it can start the timer using the waiting timer when a specified time or specified conditions are met. Then, if an emergency call is made while the timer is in operation, the UE can stop the timer and execute the login procedure and / or MM procedure and / or SM procedure for the emergency call. Furthermore, if no emergency call is made while the timer is in operation, the UE can execute the login procedure and / or MM procedure and / or SM procedure in the second PLMN after the timer expires. It should be noted that the first PLMN can be an HPLMN or a VPLMN. Furthermore, the second PLMN can be a different PLMN from the first PLMN. Furthermore, the second PLMN can be an equivalent PLMN. Furthermore, the second PLMN can also be a PLMN included in the forbidden PLMN list. Furthermore, the aforementioned PLMN can be replaced with a PLMN and / or RAT. Additionally, if communication via a second satellite connected to the second PLMN is again impossible before the timer expires using the waiting timer, the UE can stop the timer and perform a PLMN selection to select another PLMN that can be connected via satellite (e.g., the first PLMN or the third PLMN) and / or another PLMN that can be connected without satellite (e.g., the fourth PLMN). In addition, if the UE is unable to conduct satellite communication with the second PLMN again before the timer expires using the waiting timer, it can perform PLMN selection without stopping the timer, in order to select other PLMNs that can be connected via satellite and / or other PLMNs that can be connected without satellite.Furthermore, if the UE is unable to conduct satellite communication with the second PLMN again before the waiting timer expires, it can perform a PLMN selection to choose another PLMN that can be connected via satellite and / or another PLMN that can be connected without satellite, and then stop the timer. Alternatively, during a login process in a PLMN, after the network sends the waiting range to the UE, during a login process and / or a configuration update process in the same PLMN, the network can update the waiting range and / or the waiting timer and / or the waiting timer by sending the updated waiting range to the UE. In other words, after the UE receives the waiting range from the network during a login process in a PLMN, during a login process and / or a configuration update process in the same PLMN, it can update the waiting range and / or the waiting timer and / or the waiting timer by receiving the updated waiting range from the network. Furthermore, during a login process executed in a PLMN, after the network sends the waiting range to the UE, during login processes and / or configuration update processes executed in different PLMNs, the network updates the waiting range and / or the waiting timer and / or the timer using the waiting timer by sending the updated waiting range to the UE. In other words, after the UE receives the waiting range from the network during a login process executed in a PLMN, during login processes and / or configuration update processes executed in different PLMNs, it updates the waiting range and / or the waiting timer and / or the timer using the waiting timer by receiving the updated waiting range from the network.

[0195] Furthermore, the UE can calculate the waiting timer based on the waiting range and / or information related to the waiting range received from the network and / or including information about the waiting range, citing the inability to conduct satellite communication (also known as discontinuous coverage). This waiting timer can be calculated either after the inability to conduct satellite communication and before the ability to conduct satellite communication becomes available. Additionally, the start of the timer using the waiting timer can occur either after the inability to conduct satellite communication and before the ability to conduct satellite communication becomes available, or after the inability to conduct satellite communication and after the ability to conduct satellite communication becomes available. In other words, when the timer using the waiting timer is a timer started after the inability to conduct satellite communication and the ability to conduct satellite communication for the same RAT and / or PLMN becomes available, the timer using the waiting timer can be a timer used to set the period during which the UE cannot send control messages. Furthermore, when the timer using the wait timer is a timer that is started after satellite communication becomes impossible and before satellite communication for the same RAN and / or PLMN becomes possible, the timer using the wait timer can function as a timer for setting the period during which the UE cannot send control messages and / or as a timer for specifying the period during which coverage for the same RAN and / or PLMN is restored.

[0196] Furthermore, the calculation of this wait timer can be performed after satellite communication becomes possible following a period when it was previously impossible. Additionally, the start of the timer using this wait timer can also be performed after satellite communication becomes possible following a period when it was previously impossible. In other words, the timer using the wait timer is a timer that starts after satellite communication becomes possible following a period when satellite communication for the same RAT and / or PLMN becomes possible; it is a timer used to set the period during which the UE cannot send control messages.

[0197] Furthermore, when a UE communicates with the core network via satellite using a PLMN (here, PLMN A) and a RAT (e.g., based on 3G, 4G, or 5G radio access technology, here denoted as RAT A), the core network generates a waiting range and notifies the UE. The UE receives this waiting range to understand it. Then, after satellite communication becomes possible again based on the same RAT (RAT A) and the same PLMN (PLMN A) (also known as returning to coverage from discontinuous coverage), the UE starts a timer using a waiting timer. In other words, the waiting range, the waiting timer, and the timer using the waiting timer can apply to the same RAT and the same PLMN. Further, the waiting range and / or the waiting timer and / or the timer using the waiting timer can be timers applied only to the same PLMN. Here, the UE can generate the waiting timer based on the waiting range either after coverage is restored or immediately after receiving the waiting range (i.e., before satellite communication becomes possible).

[0198] Furthermore, when a UE communicates with the core network via satellite using a PLMN (here, PLMN A) and a RAT (here, RAN A), the core network generates a waiting range and notifies the UE, which then receives and understands this waiting range. Then, after satellite communication becomes unavailable, and then becomes possible again based on a different RAT (RAT B) and the same PLMN (PLMN A) (also known as returning to coverage from discontinuous coverage), the UE starts a timer using a waiting timer. In other words, the waiting range, the waiting timer, and the timer using the waiting timer can be applied to different RATs and the same PLMN. Further, the waiting range and / or the waiting timer and / or the timer using the waiting timer can be timers applied to the same or different RATs and the same PLMN. Even further, the waiting range and / or the waiting timer and / or the timer using the waiting timer can be timers applied to the same PLMN, i.e., timers independent of the RAT. Here, the UE can generate a waiting timer based on the waiting range either after coverage is restored or immediately after receiving the waiting range (i.e., before satellite communication becomes possible).

[0199] Furthermore, when a UE communicates with the core network via satellite using a PLMN (here, PLMN A) and a RAT (here, RAN A), the core network generates a waiting range and notifies the UE, which then receives and understands this waiting range. Then, after satellite communication becomes unavailable, and communication based on the same RAT (RAT A) and a different PLMN (PLMN B) becomes possible (also known as returning to coverage from discontinuous coverage), the UE starts a timer using the waiting timer. In other words, the waiting range, the waiting timer, and the timer using the waiting timer can apply to the same RAT and different PLMNs. Further, the waiting range and / or the waiting timer and / or the timer using the waiting timer can be timers applied only to different PLMNs. Alternatively, the waiting range and / or the waiting timer and / or the timer using the waiting timer can be timers applied to all PLMNs. Here, the UE can generate the waiting timer based on the waiting range either after coverage is restored or immediately after receiving the waiting range (i.e., before satellite communication becomes possible).

[0200] Furthermore, when a UE communicates with the core network via satellite using a PLMN (here, PLMN A) and a RAT (here, RAN A), the core network generates a waiting range and notifies the UE, which then receives and understands this waiting range. Then, after satellite communication becomes unavailable, and subsequently becomes possible based on a different RAT (RAT B) and a different PLMN (PLMN B) (also known as returning to coverage from discontinuous coverage), the UE starts a timer using a waiting timer. In other words, the waiting range, the waiting timer, and the timer using the waiting timer can be applied to different RATs and different PLMNs. Further, the waiting range and / or the waiting timer and / or the timer using the waiting timer can be timers applied only to different PLMNs. Alternatively, the waiting range and / or the waiting timer and / or the timer using the waiting timer can be timers applied to all PLMNs. Here, the UE can generate the waiting timer based on the waiting range either after coverage is restored or immediately after receiving the waiting range (i.e., before satellite communication becomes possible).

[0201] Furthermore, when an emergency call is made while the timer using a waiting timer is in operation (i.e., before its expiration), the UE can still perform the MM procedure and / or SM procedure on the same PLMN even before the timer expires. In other words, when an emergency call is made while the timer using a waiting timer is in operation (i.e., before its expiration), the UE can still send and receive control messages (e.g., NAS messages and / or RRC messages) on the same PLMN even before the timer expires. In this case, the UE can perform the MM procedure and / or SM procedure after stopping the timer. However, the UE can stop the timer during the execution of the MM procedure and / or SM procedure, or it can stop the timer after performing the MM procedure and / or SM procedure. Additionally, during the MM procedure and / or SM procedure, the control messages sent by the UE can include information indicating that it is an emergency call via satellite. For example, if the MM procedure is a login procedure, the 5GS registration type IE included in the login request message sent by the UE can be set to emergency registration. Furthermore, during the MM and / or SM processes, if the control message received from the UE includes information indicating that it is an emergency call via satellite, the network (e.g., AMF and / or SMF) may send a control message including information indicating that an emergency call via satellite is permitted to the UE.

[0202] Furthermore, when an emergency call is made while the timer using a waiting timer is in operation (i.e., before its expiration), the UE can still perform the MM procedure and / or SM procedure on the same PLMN and / or the same or different RATs, even before the timer expires. In other words, when an emergency call is made while the timer using a waiting timer is in operation (i.e., before its expiration), the UE can still send and receive control messages (e.g., NAS messages and / or RRC messages) on the same PLMN and / or the same or different RATs, even before the timer expires. In this case, the UE can perform the MM procedure and / or SM procedure after stopping the timer. However, the UE can stop the timer during the execution of the MM procedure and / or SM procedure, or it can stop the timer after performing the MM procedure and / or SM procedure. Additionally, during the MM procedure and / or SM procedure, the control messages sent by the UE can include information indicating that it is an emergency call via satellite. For example, if the MM procedure is a login procedure, the 5GS login type IE included in the login request message sent by the UE can be set to emergency login. Furthermore, during the MM and / or SM processes, if the control message received from the UE includes information indicating that it is an emergency call via satellite, the network (e.g., AMF and / or SMF) may send a control message including information indicating that an emergency call via satellite is permitted to the UE.

[0203] Furthermore, when an emergency call is made while the timer using a waiting timer is in operation (i.e., before its expiration), the UE can select another PLMN and perform the MM procedure and / or SM procedure on the selected PLMN, even before the timer expires. In other words, when an emergency call is made while the timer using a waiting timer is in operation (i.e., before its expiration), the UE can select another PLMN and send and receive control messages (e.g., NAS messages and / or RRC messages) on the selected PLMN. Here, the other PLMNs may include PLMNs included in the prohibited PLMN list, equivalent PLMNs for HPLMNs or RPLMNs. Furthermore, this action can be performed, for example, in the event of congestion in the selected PLMN and / or the network slice within that PLMN. Additionally, the UE can perform the MM procedure and / or SM procedure after stopping the timer. However, the UE can stop the timer during the execution of the MM procedure and / or SM procedure, or stop the timer after executing the MM procedure and / or SM procedure. Furthermore, during the MM and / or SM procedures, the control messages sent by the UE may include information indicating that the call is an emergency call via satellite. For example, if the MM procedure is a login procedure, the 5GS login type IE included in the login request message sent by the UE may be set to emergency login. Additionally, during the MM and / or SM procedures, if the control messages received from the UE include information indicating that the call is an emergency call via satellite, the network (e.g., AMF and / or SMF) may send a control message to the UE including information indicating that an emergency call via satellite is permitted.

[0204] Furthermore, when an emergency call is made while the timer of the waiting timer is in operation (i.e., before its expiration), the UE can select another PLMN and / or the same or different RAT even before the timer expires, and perform the MM procedure and / or SM procedure on the selected PLMN and RAT. In other words, when an emergency call is made while the timer of the waiting timer is in operation (i.e., before its expiration), the UE can select another PLMN and / or the same or different RAT even before the timer expires, and send and receive control messages (e.g., NAS messages and / or RRC messages) on the selected PLMN and RAT. Here, the other PLMNs may include PLMNs included in the prohibited PLMN list, equivalent PLMNs for HPLMNs or RPLMNs. Furthermore, this action may be performed, for example, in the event of congestion in the selected PLMN and / or the network slice and / or RAT within that PLMN. Additionally, in this case, the UE can perform the MM procedure and / or SM procedure after stopping the timer. However, the UE can stop the timer during or after the execution of the MM and / or SM procedures. Furthermore, during the MM and / or SM procedures, the control messages sent by the UE may include information indicating that the call is an emergency call via satellite. For example, if the MM procedure is a login procedure, the 5GS login type IE included in the login request message sent by the UE can be set to emergency login. Additionally, during the MM and / or SM procedures, if the control messages received from the UE include information indicating that the call is an emergency call via satellite, the network (e.g., AMF and / or SMF) may send a control message to the UE including information indicating that an emergency call via satellite is permitted.

[0205] It should be noted that the above can be applied to NPN (SNPN and / or PNI-NPN). That is, this implementation method can also be applied to NPN by replacing PLMN with SNPN. [4. Improved Example]

[0206] The program that operates the apparatus according to one aspect of the present invention can be a program that controls a central processing unit (CPU) or the like to enable the computer to perform its functions in order to achieve the functions of the embodiments of the present invention. The program or the information processed by the program is temporarily stored in volatile memory such as random access memory (RAM) or non-volatile memory such as flash memory, hard disk drive (HDD) or other storage device system.

[0207] It should be noted that a program for implementing the functions of one embodiment of the present invention can also be recorded in a computer-readable recording medium. This can be achieved by reading the program recorded in the recording medium into a computer system and executing it. Here, "computer system" refers to a computer system built into a device, including hardware such as an operating system and peripherals. Furthermore, a "computer-readable recording medium" can be a semiconductor recording medium, an optical recording medium, a magnetic recording medium, a medium for short-term dynamic program retention, or other computer-readable recording media.

[0208] Furthermore, the functional blocks or features of the apparatus used in the above embodiments can be installed or executed by electronic circuits such as integrated circuits or multiple integrated circuits. Circuits designed to perform the functions described in this specification may include: general-purpose processors, digital signal processors (DSPs), application-specific integrated circuits (ASICs), field-programmable gate arrays (FPGAs) or other programmable logic elements, discrete gate or transistor logic, discrete hardware components, or combinations thereof. General-purpose processors may be microprocessors, or processors, controllers, microcontrollers, or state machines of conventional types. The aforementioned electronic circuits may be constructed from digital circuits or analog circuits. Furthermore, with the emergence of integrated circuit technologies that replace existing integrated circuits due to advancements in semiconductor technology, one or more embodiments of the present invention may also utilize new integrated circuits based on this technology.

[0209] It should be noted that the present invention is not limited to the embodiments described above. While one example of the device is described in the embodiments, the present invention is not limited to this and can be applied to fixed or non-movable electronic devices installed indoors or outdoors, such as AV equipment, kitchen equipment, cleaning / washing equipment, air conditioning equipment, office equipment, vending machines, and other household appliances, etc.

[0210] The embodiments of the present invention have been described in detail above with reference to the accompanying drawings. However, the specific configuration is not limited to these embodiments, and design changes that do not depart from the spirit of the present invention are also included. Furthermore, various modifications can be made to one aspect of the present invention within the scope shown in the technical solution. Embodiments obtained by appropriately combining the technical means disclosed in different embodiments are also included within the technical scope of the present invention. In addition, configurations obtained by replacing elements that have the same effect as the elements described in the above embodiments are also included. Explanation of reference numerals in the attached figures 1. Mobile communication system 10 UE_A 30 PGW-U 32 PGW-C 35 SGW 40 MME 45 eNB 50 HSS 60 PCRF 80 Access Network_A 90 Core Network_A 120 Access Network_B 122 gNB 130 UPF 132 SMF 140 AMF 150 UDM 160 PCF 170 N3IWF 190 Core Network_B

Claims

1. A user equipment (UE), comprising: Transceiver circuit; as well as Control circuit, in which When the transceiver circuit receives first information from the network in a login acceptance message or configuration update command message, indicating a first range for determining the value of a wait timer, wherein the first information is applied to a first public land mobile network (PLMN) and a first radio access technology (RAT), the control circuit is configured to use the first information to update second information indicating a second range for determining the value of the wait timer, wherein the second information has previously been received in the UE and applied to the first PLMN and the first RAT. In the case where the UE returns to coverage after being out of coverage due to discontinuous coverage, the control circuit is further configured to: Based on the first information, the value of the wait timer applied to the first PLMN and the first RAT is determined, and Start the waiting timer; and The waiting timer is a timer used to set the period during which the UE does not send non-access stratum (NAS) messages on the first PLMN and the first RAT.

2. A communication control method executed by a user equipment (UE), the communication control method comprising: When the UE receives first information from the network in a login acceptance message or a setting update command message, indicating a first range for determining the value of a wait timer, wherein the first information is applied to a first public land mobile network (PLMN) and a first radio access technology (RAT), the first information is used to update second information indicating a second range for determining the value of the wait timer, wherein the second information has previously been received in the UE and applied to the first PLMN and the first RAT. In the case where the UE returns to coverage after being out of coverage due to discontinuous coverage, Based on the first information, the value of the wait timer applied to the first PLMN and the first RAT is determined, and Start the waiting timer; and The waiting timer is a timer used to set the period during which the UE does not send non-access stratum (NAS) messages on the first PLMN and the first RAT.

Citation Information

Patent Citations

  • User equipment (UE)

    CN117997408A

  • Sleep wakeup methods for discontinuous coverage in non-terrestrial network

    US20230043459A1