User equipment

Abstract

To solve a problem in which standardization of communications for UE connection to 5G core networks via New Radio (NR) satellite access that provides discontinuous coverage is underway, however, due to the discontinuous coverage of NR satellite access, the information required for control using time offsets to avoid overload caused by a large number of UE returning to the range of NR satellite access after a period of disabling NR satellite access coverage, when the UE is out of range, as well as the behavior and processing of the UE and each device involved in the transmission and reception of the information and overload control, have not been clarified.SOLUTION: The present invention provides means for transmitting and receiving information between UE and a network for appropriately executing a timer based on a time offset of overload control after an unavailable period in which the UE is out of range due to discontinuous coverage of NR satellite access, and a method for performing appropriate processing based on the information.SELECTED DRAWING: Figure 6

Description

[Technical field]

[0001] The present invention relates to User Equipment (UE). [Background technology]

[0002] 3GPP (3rd Generation Partnership Project: registered trademark) is considering the system architecture of 5GS (5G System), which is a fifth generation (5G) mobile communication system, and is discussing how to support new procedures and new functions (see Non-Patent Documents 1 to 4). In Release 18 of the 5G standard, the architecture for 5G communication via artificial satellites (also simply called "satellites"), procedures for communication and control, etc. are being considered (see Non-Patent Document 4). [Prior art documents] [Non-patent literature]

[0003] [Non-Patent Document 1] 3GPP TS 23.501 V18.2.2 (2023-07); 3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; System architecture for the 5G System (5GS); Stage 2 (Release 18) [Non-Patent Document 2] 3GPP TS 23.502 V18.2.0 (2023-06); 3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Procedures for the 5G System (5GS); Stage 2 (Release 18) [Non-Patent Document 3] 3GPP TS 24.501 V18.3.0 (2023-06); 3rd Generation Partnership Project; Technical Specification Group Core Network and Terminals; Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3; (Release 18) [Non-Patent Document 4] 3GPP TR 23.700-28 V18.1.0 (2023-03); 3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Study on Integration of satellite components in the 5G architecture; Phase 2 (Release 18) Summary of the Invention [Problem to be solved by the invention]

[0004] In the 5GS (5G System), a new core network, 5GCN (5G Core Network), is being considered to provide a wide variety of services. In addition, architecture for 5G communication via satellites (also simply called "satellites") is being considered.

[0005] Currently, in such communication architectures that use satellites as a wireless technology (radio access technology) connecting user equipment (UE) and a core network, studies are underway on extending conventional procedures, messages, or parameters to take into account the characteristics of wireless connections via satellite.

[0006] On the other hand, the information required to perform control using a time offset to avoid overload caused by a large number of UEs simultaneously returning to range of New Radio (NR) satellite access after a period of disabling when the UE is out of range due to discontinuous coverage via NR satellite access, the transmission and reception of such information, and the behavior and processing of the UE and each device involved in overload control are not clear.

[0007] One aspect of the present invention has been made in consideration of the above circumstances, and its purpose is to provide a means for transmitting and receiving information between a UE and a network that is necessary for the UE to appropriately execute a timer based on a time offset for overload control after a period when the UE is unavailable due to discontinuous coverage of NR satellite access, and a method for executing appropriate processing based on the information. [Means for solving the problem]

[0008] A UE (User Equipment) of one embodiment of the present invention is a UE having a transceiver unit, a control unit, and a memory unit, wherein the transceiver unit receives a first timer value, and / or a first type, and / or a maximum waiting time from a network (NW), the first timer value is a timer value indicating the duration of an Unavailability Period, and the first type is a type indicating that the Unavailability Period is not dependent on discontinuous coverage provided by NR (New Radio) satellite access, the control unit associates the first timer value with the first type and stores it in the memory unit, the control unit does not set and / or start a second timer after expiration of a timer based on the first timer value associated with the first type stored in the memory unit, and the second timer is a timer whose timer value is a period determined by the UE based on the maximum waiting time. A UE (User Equipment) of one embodiment of the present invention is a UE having a transceiver unit, a control unit, and a memory unit, wherein the memory unit stores a first timer and a second timer, the first timer is a timer whose timer value is an availability period associated with a type indicating that the availability period is not due to discontinuous coverage provided by NR (New Radio) satellite access, and the second timer is a timer whose timer value is an availability period associated with a type indicating that the availability period is due to discontinuous coverage provided by the NR satellite access, the transceiver unit receives first control information from a network, the first control information is information indicating the first or second timer value and / or type, and the control unit executes the timers based on the first control information.A UE (User Equipment) of one embodiment of the present invention is a UE having a transceiver unit, a control unit, and a memory unit, wherein the memory unit stores a first timer value in association with a first type, the first timer value being a timer value indicating the duration of an unavailability period, the first type being a type indicating that the unavailability period is not due to discontinuous coverage provided by NR (New Radio) satellite access, the memory unit further stores a waiting time, the waiting time being a value determined by the control unit based on a maximum waiting time received by the transceiver unit from a network, and the control unit executes a PLMN (Public Land Mobile Network) selection procedure when a timer based on an unavailability period due to discontinuous coverage provided by NR satellite access is running at the time when the timer based on the first timer value expires. Effect of the Invention

[0009] According to one aspect of the present invention, in overload control performed after an unavailable period due to discontinuous coverage of NR satellite access, a means for transmitting and receiving information required for the UE to properly execute a timer based on a time offset between the UE and a network, and a method for the UE and the network to execute appropriate processing based on the information are provided. [Brief description of the drawings]

[0010] [Figure 1] 1 is a diagram illustrating an overview of a mobile communication system (EPS / 5GS). [Diagram 2] A diagram explaining the detailed configuration of a mobile communication system (EPS / 5GS). [Diagram 3] A diagram explaining the device configuration of a UE. [Figure 4] A diagram explaining the configuration of an access network device (gNB) in 5GS. [Diagram 5]A diagram explaining the configuration of core network devices (AMF / SMF / UPF) in 5GS. [Figure 6] FIG. 1 is a diagram illustrating a registration procedure. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

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

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

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

[0014] In the following, these devices and functions may be described with abbreviated symbols, such as UE, access network_A, core network_A, PDN, access network_B, core network_B, DN, etc.

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

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

[0017] In addition, the 4G system EPS (Evolved Packet System) is configured to include an access network _A and a core network _A, but may further include a UE and / or a PDN. In addition, the 5G system 5GS (5G System) is configured to include a UE, an access network _B, and a core network _B, but may further include a DN.

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

[0019] Moreover, the access network_A corresponds to an E-UTRAN (Evolved Universal Terrestrial Radio Access Network) and / or a wireless LAN access network. In the E-UTRAN, one or more eNBs (evolved Node B) 45 are arranged. In the following, the eNB 45 may be written with the symbol omitted, such as eNB. In addition, when there are multiple eNBs, the eNBs are connected to each other, for example, by an X2 interface. In addition, one or more access points are arranged in the wireless LAN access network.

[0020] Moreover, the access network_B corresponds to a 5G access network (5G AN). The 5G AN is composed of an NG-RAN (NG Radio Access Network) and / or a non-3GPP access network. One or more gNBs (NR Node B) 122 are arranged in the NG-RAN. In the following, the gNB 122 may be written with the symbol omitted, such as gNB. The gNB is a node that provides the NR (New Radio) user plane and control plane to the UE, and is a node that connects to the 5GCN via an NG interface (including an N2 interface or an N3 interface). That is, the gNB is a base station device newly designed for the 5GS, and has a different function from the base station device (eNB) used in the EPS, which is a 4G system. In addition, when there are multiple gNBs, each gNB is connected to each other, for example, by an Xn interface.

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

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

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

[0024] Moreover, the core network_A corresponds to an EPC (Evolved Packet Core). In the EPC, for example, an MME (Mobility Management Entity), an SGW (Serving Gateway), a PGW (Packet Data Network Gateway)-U, a PGW-C, a PCRF (Policy and Charging Rules Function), an HSS (Home Subscriber Server), etc. are arranged.

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

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

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

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

[0029] In addition, in the following, at least a portion of the access network _A, the core network _A, the PDN, the access network _B, the core network _B, and the DN, and / or one or more devices included therein may be referred to as a network or a network device. In other words, when a network and / or a network device transmits or receives a message and / or executes a procedure, it means that at least a portion of the access network _A, the core network _A, the PDN, the access network _B, the core network _B, and the DN, and / or one or more devices included therein transmits or receives a message and / or executes a procedure.

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

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

[0032] In addition, the access network_A, the core network_A, the access network_B, the core network_B, the PDN_A, and the DN_A may be configured with devices not shown in Fig. 2. For example, the core network_A and / or the core network_B may include an AUSF (Authentication Server Function) and an AAA (Authentication, authorization, and accounting) server (AAA-S).

[0033] Here, the AUSF is a core network device having an authentication function for 3GPP access and non-3GPP access, specifically, a network function unit that receives an authentication request for 3GPP access and / or non-3GPP access from a UE and executes an authentication procedure.

[0034] The AAA server is a device that is connected to the AUSF directly or indirectly via another network device and has authentication, authorization, and accounting functions. The AAA server may be a network device in the core network. The AAA server may not be included in the core network_A and / or the core network_B, but may be included in the PLMN. In other words, the AAA server may be a core network device or a device outside the core network. For example, the AAA server may be a server device in the PLMN managed by a third party.

[0035] 2, for the sake of simplicity, one of each device and function is shown, but a plurality of similar devices and functions may be configured in the mobile communication system 1. Specifically, the mobile communication system 1 may be configured with a plurality of 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.

[0036] The UPF_A235 is connected to the DN, the SMF, other UPFs, and the access network. The UPF_A235 may perform roles such as an anchor for intra-RAT mobility or inter-RAT mobility, packet routing & forwarding, a UL CL (Uplink Classifier) ​​function supporting routing of multiple traffic flows for one DN, a branching point function supporting a multi-homed PDU session, QoS processing for the user plane, verification of uplink traffic, buffering of downlink packets, and a trigger function for downlink data notification. The UPF_A235 may also be a relay device that forwards user data as a gateway between the DN and the core network_B190. The UPF_A235 may also be a gateway for IP communication and / or non-IP communication. The UPF_A235 may also have a function of forwarding IP communication and a function of converting non-IP communication to IP communication. Furthermore, multiple gateways may be deployed, and may be gateways that connect the core network_B190 to a single DN. Note that UPF_A235 may have connectivity with other NFs and may be connected to each device via other NFs.

[0037] In addition, UPF_C239 (also called a branching point or uplink classifier), which is a UPF different from UPF_A235, may exist as a device or NF between UPF_A235 and the access network. When UPF_C239 exists, a PDU session between the UE and the DN is established via the access network, UPF_C239, and UPF_A235.

[0038] Moreover, the UPF 130 may be the same device as the UPF_A 235. Note that the UPF 130 and the UPF_A 235 may be described with the symbol omitted, such as UPF.

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

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

[0041] [2.1. UE device configuration] First, an example of the device configuration of UE (User Equipment) will be described with reference to Fig. 3. The UE is composed of a control unit _A300, an antenna 310, a transceiver unit _A320, and a memory unit _A340. The control unit _A300, the transceiver unit _A320, and the memory unit _A340 are connected via a bus. The transceiver unit _A320 is connected to the antenna 310.

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

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

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

[0045] The memory unit _A340 is a functional unit for storing programs, user data, control information, etc. necessary for each operation of the UE.

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

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

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

[0049] The transceiver unit _B530 is a functional unit for wirelessly communicating with the UE via the antenna 510. That is, the gNB can transmit and receive user data and / or control information between the UE and the transceiver unit _B530.

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

[0051] The memory unit _B540 is a functional unit for storing programs, user data, control information, etc. necessary for each operation of the gNB.

[0052] [2.3. AMF device configuration] Next, an example of the device configuration of the AMF will be described with reference to FIG. 5. The AMF is composed of a control unit _B700, a network connection unit _B720, and a memory unit _B740. The control unit _B700, the network connection unit _B720, and the memory unit _B740 are connected via a bus. The AMF may be a node that handles the control plane. The AMF may also be a network device. In other words, for example, in this specification, the network device may mean the AMF.

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

[0054] The network connection unit _B720 is a functional unit for the AMF to connect to a base station device (gNB), and / or an SMF, and / or a PCF, and / or an UDM, and / or an SCEF in a 5G AN. That is, the AMF can transmit and receive user data and / or control information between a base station device (gNB), and / or an SMF, and / or a PCF, and / or an UDM, and / or an SCEF in a 5G AN using the network connection unit _B720. In other words, for example, the network connection unit may be a transceiver unit.

[0055] Explaining in detail with reference to FIG. 2, the AMF in the 5GCN can communicate with the gNB via the N2 interface by using the network connection unit_A620, can communicate with the UDM via the N8 interface, can communicate with the SMF via the N11 interface, and can communicate with the PCF via the N15 interface. In addition, the AMF can transmit and receive NAS messages to and from the UE via the N1 interface by using the network connection unit_A620. However, since the N1 interface is logical, in reality, communication between the UE and the AMF is performed via the 5G AN. In addition, if the AMF supports the N26 interface, it can communicate with the MME via the N26 interface by using the network connection unit_A620.

[0056] The memory unit _B740 is a functional unit for storing programs, user data, control information, etc. necessary for each operation of AMF.

[0057] In addition, the AMF has a function of exchanging control messages with the RAN using the N2 interface, a function of exchanging NAS messages with the UE using the N1 interface, a function of encrypting and protecting the integrity of NAS messages, a registration management (RM) function, a connection management (CM) function, a reachability management function, a mobility management function for UEs, etc., a function of transferring SM (Session Management) messages between the UE and the SMF, an access authentication (access authorization) function, a security anchor functionality (SEA), a security context management (SCM) function, a function of supporting the N2 interface for the N3IWF (Non-3GPP Interworking Function), a function of supporting the transmission and reception of NAS signals with the UE via the N3IWF, and a function of authenticating UEs connected via the N3IWF.

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

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

[0060] Furthermore, 5GMM-DEREGISTERED may be a state in which each device has not established a 5GMM context, a state in which the location information of UE_A10 is not known to the network, or a state in which the network cannot reach UE_A10. Note that when each device is 5GMM-DEREGISTERED, UE_A10 may initiate a registration procedure or establish a 5GMM context by executing the registration procedure.

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

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

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

[0064] In addition, one or more AMFs may be placed in the core network_B. In addition, the AMF may be a network function (NF) that manages one or more network slice instances (NSIs). In addition, the AMF may be a common control plane network function (CCNF) shared between multiple NSIs.

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

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

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

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

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

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

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

[0072] [2.5. UPF device configuration] Next, an example of the device configuration of the UPF will be described with reference to Fig. 5. The UPF is composed of a control unit _B700, a network connection unit _B720, and a memory unit _B740. The control unit _B700, the network connection unit _B720, and the memory unit _B740 are connected via a bus. The UPF may be a node that handles the control plane.

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

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

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

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

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

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

[0079] The user plane refers to user data transmitted and received between the UE and the network. The user plane may be transmitted and received using a PDN connection or a PDU session. Furthermore, in the case of EPS, the user plane may be transmitted and received using the LTE-Uu interface, and / or the S1-U interface, and / or the S5 interface, and / or the S8 interface, and / or the SGi interface. Furthermore, in the case of 5GS, the user plane may be transmitted and received via an interface between the UE and the NG RAN, and / or the N3 interface, and / or the N9 interface, and / or the N6 interface. Hereinafter, the user plane may be expressed as U-Plane.

[0080] Furthermore, the control plane refers to a control message transmitted and received to control communication of the UE. The control plane may be transmitted and received using a Non-Access-Stratum (NAS) signaling connection between the UE and the MME. Furthermore, in the case of EPS, the control plane may be transmitted and received using the LTE-Uu interface and the S1-MME interface. Furthermore, in the case of 5GS, the control plane may be transmitted and received using the interface between the UE and the NG RAN and the N2 interface. Hereinafter, the control plane may be expressed as the control plane or the C-Plane.

[0081] Furthermore, the U-Plane (User Plane; UP) may be a communication path for transmitting and receiving user data and may be composed of multiple bearers. Furthermore, the C-Plane (Control Plane; CP) may be a communication path for transmitting and receiving control messages and may be composed of multiple bearers.

[0082] [2.6. Description of other equipment and / or functions] Next, other devices and / or functions will be described.

[0083] The PCF has a function of providing policy rules.

[0084] The UDM also has an authentication credential processing function, a user identification processing function, an access authentication function, a registration / mobility management function, a subscription management function, and the like.

[0085] The PCRF is connected to the PGW and / or the PDN and has a function of managing QoS for data delivery. For example, the PCRF manages the QoS of the communication path between the UE_A10 and the PDN. The PCRF may also be a device that creates and / or manages PCC (Policy and Charging Control) rules and / or routing rules used by each device when transmitting and receiving user data.

[0086] The HSS is connected to the MME and / or the SCEF and has a function of managing subscriber information. The subscriber information of the HSS is referred to, for example, when controlling access to the MME. Furthermore, the HSS may be connected to a location management device different from the MME.

[0087] [3. Explanation of terms and identification information used in each embodiment] Next, terms and identification information used in each embodiment will be explained in advance.

[0088] [3.1. Explanation of terms used in each embodiment] Next, highly specialized terms used in each embodiment and identification information used in the procedures will be described.

[0089] The network refers to at least a part of the access network _B, the core network _B, and the DN. Furthermore, one or more devices included in at least a part of the access network _B, the core network _B, and the DN may be referred to as a network or a network device. In other words, when a network transmits, receives, and / or processes messages, it may mean that a device in the network (a network device and / or a control device) transmits, receives, and / or processes messages. Conversely, when a device in the network transmits, receives, receives, and / or processes messages, it may mean that the network transmits, receives, and / or processes messages.

[0090] The SM (Session Management) message (also referred to as a NAS (Non-Access-Stratum) SM message) may be a NAS message used in procedures for SM, and may be a control message transmitted and received between UE_A10 and SMF_A230 via AMF_A240. Furthermore, the SM message may include a PDU session establishment request message, a PDU session establishment accept message, a PDU session establishment reject message, a PDU session modification request message, a PDU session modification command message, a PDU session modification complete message, a PDU session modification command reject message, a PDU session modification reject message, a PDU session release request message, a PDU session release reject message, a PDU session release command message, a PDU session release complete message, etc. Furthermore, the procedure for SM or the SM procedure may include a PDU session establishment procedure, a PDU session modification procedure, and a UE-requested PDU session release procedure.Each procedure may be initiated by the UE or may be initiated by the NW.

[0091] An MM (Mobility management) message (also referred to as a NAS MM message) may be a NAS message used in a procedure for MM, and may be a control message transmitted and received between UE_A10 and AMF_A240. Furthermore, the MM message may include a registration request message, a registration accept message, a registration reject message, a de-registration request message, a de-registration accept message, a configuration update command message, a configuration update complete message, a service request message, a service accept message, a service reject message, a notification message, a notification response message, and the like. Furthermore, the procedures for MM or MM procedures may include a Registration procedure, a De-registration procedure, a Generic UE configuration update procedure (also simply referred to as a UE configuration update procedure), an Authentication and / or Authorization procedure, a Service request procedure, a Paging procedure, and a Notification procedure.

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

[0093] Non-5GS services may be services other than 5GS services and may include EPS services and / or non-EPS services.

[0094] PDN (Packet Data Network) type indicates the type of PDN connection, and can be IPv4, IPv6, IPv4v6, or non-IP. If IPv4 is specified, it indicates that data will be sent and received using IPv4. If IPv6 is specified, it indicates that data will be sent and received using IPv6. If IPv4v6 is specified, it indicates that data will be sent and received using either IPv4 or IPv6. If non-IP is specified, it indicates that communication will not be via IP, but rather via a communication method other than IP.

[0095] A PDU (Protocol Data Unit / Packet Data Unit) session can be defined as an association between a DN providing a PDU connectivity service and a UE, but may also be connectivity established between a UE and an external gateway. In 5GS, a UE can transmit and receive user data between a DN and a DN by establishing a PDU session via an access network_B and a core network_B. Here, the external gateway may be a UPF, a SCEF, or the like. A UE can transmit and receive user data to and from a device such as an application server located in a DN by using a PDU session. Each device (UE, and / or an access network device, and / or a core network device) may manage one or more pieces of identification information in association with a PDU session. These pieces of identification information may include one or more of a DNN, a QoS rule, a PDU session type, an application identification information, an NSI identification information, an access network identification information, and an SSC mode, or may further include other information. Furthermore, when a plurality of PDU sessions are established, each piece of identification information associated with a PDU session may be the same or different.

[0096] The DNN (Data Network Name) may be identification information for identifying a core network and / or an external network such as a DN. Furthermore, the DNN may be used as information for selecting a gateway such as a PGW / UPF that connects the core network B190. Furthermore, the DNN may be equivalent to an APN (Access Point Name).

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

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

[0099] A tracking area is a single or multiple ranges managed by the core network that can be represented by the location information of UE_A10. The tracking area may be composed of multiple cells. Furthermore, the tracking area may be a range in which control messages such as paging are broadcast, or a range in which UE_A10 can move without performing a handover procedure. Furthermore, the tracking area may be a routing area, a location area, or anything similar to these. Hereinafter, the tracking area may be a TA (Tracking Area). The tracking area may be identified by a TAI (Tracking Area Identity) composed of a TAC (Tracking area code) and a PLMN.

[0100] A registration area is a collection of one or more TAs that the AMF assigns to a UE. Note that while UE_A10 is moving within one or more TAs included in the registration area, it may be able to move without sending or receiving a signal for tracking area update. In other words, a registration area may be a group of information indicating an area in which UE_A10 can move without performing a tracking area update procedure. A registration area may be identified by a TAI list consisting of one or more TAIs.

[0101] The Current TAI is the TAI broadcast by the selected PLMN in the cell where the UE is located or camped, or if the cell is a satellite NG-RAN cell that broadcasts multiple TACs in the selected PLMN, the UE NAS layer may select the current TAI from multiple Tracking Area Codes (TACs) in the selected PLMN.

[0102] The Lists of 5GS forbidden tracking areas may be a list of 5GS forbidden tracking areas for roaming and / or a list of 5GS forbidden tracking areas for regional provision of service stored by a UE not operating in an SNPN access operation mode. In other words, a UE not operating in an SNPN access operation mode must store a list of 5GS forbidden tracking areas for roaming and / or a list of 5GS forbidden tracking areas for regional provision of service. Furthermore, the UE needs to search for a suitable cell in the same PLMN that belongs to a TA that is not included in the list of 5GS forbidden tracking areas.

[0103] Furthermore, the UE is not permitted to request 5GS services other than emergency services if it is located in a cell of a TA that belongs to the list of 5GS forbidden tracking areas for regional provision of service.

[0104] The UE may also store the forbidden tracking area ID (TAI) in a list of 5GS forbidden tracking areas for regional service provision to prevent repeated access attempts to cells in the forbidden tracking area. Furthermore, the list of 5GS forbidden tracking areas for regional service provision may be deleted when the UE is powered off, when the SIM is removed, or periodically (for a period ranging from 12 to 24 hours).

[0105] In addition, information indicating the 5GS forbidden tracking areas for roaming may be included in an information element (Forbidden TAI(s) for the list of "5GS forbidden tracking areas for roaming" IE (Information Element)) included in a message sent by the network and transmitted to the UE.

[0106] In addition, the 5GS forbidden tracking areas for regional provision of service may be included in an information element (Forbidden TAI(s) for the list of "5GS forbidden tracking areas for regional provision of service" IE (Information Element)) included in a message sent by the network and transmitted to the UE.

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

[0108] An NTN (Non-terrestrial network) may be an NG-RAN consisting of multiple gNBs, which provides non-terrestrial NR access to UEs via NTN payloads and NTN gateways mounted on NTN transmission means such as satellites, aircraft, etc. installed in space or in the air.

[0109] Here, the NTN payload is a network node mounted on a satellite or a high altitude platform station and provides a connection function between a service link and a feeder link. Furthermore, the NTN payload may be a TNL (Transport Network Layer) node.

[0110] An NTN Gateway is an earth station installed on the Earth's surface that provides connectivity to an NTN payload using a feeder link, and may be a Transport Network Layer (TNL) node.

[0111] In other words, for example, a "NR connection via satellite" (NR satellite access) by a UE may be an NR connection via a satellite (also referred to simply as a satellite in this specification) carrying an NTN payload and a gNB consisting of an NTN gateway. Furthermore, the UE may perform procedures for registering with the network and / or establishing a PDU session via the NR connection, and may further perform communication using the established PDU session after completion of these procedures.

[0112] Herein, communication via an NTN is also referred to as communication via NR satellite access, or communication via an NTN, NTN communication, or satellite communication, etc. Also, an NR connection via an NTN is also referred to as NR satellite access, or connection or access via a satellite, or satellite access, satellite radio access, etc.

[0113] A TN (terrestrial network) may provide terrestrial radio access to UEs through an access network configured by base stations installed on the ground. In contrast to an NTN, which is a non-terrestrial network using satellites, a TN may be a terrestrial network. In addition, an access network installed and configured on the ground may be, for example, an NG-RAN configured by multiple gNBs, or an E-UTRAN configured by multiple eNBs, but is not limited to these.

[0114] Herein, communication via a TN is also referred to as communication via NR terrestrial access, or communication via a TN, TN communication, or non-satellite communication, etc. Also, an NR connection via a TN is also referred to as NR terrestrial access, or connection or access via a non-satellite, or non-satellite access, etc.

[0115] The satellite NG-RAN Radio Access Technology (RAT) type may be information used to identify or distinguish different types of satellite NG-RAN access in satellite NG-RAN access. The satellite NG-RAN RAT type may be, for example, "NR (LEO)", "NR (MEO)", "NR (GEO)", and "NR (OTHERSAT)". Here, "LEO" may mean a low earth orbit satellite, "MEO" may mean a middle earth orbit satellite, "GEO" may mean a geostationary earth orbit satellite, and "OTHERSAT" may mean other satellites.

[0116] Here, the access technology may be associated with a PLMN or an SNPN, and further, the PLMN or SNPN may be capable of supporting multiple access technologies, where the UE may use the access technology information to determine the type of wireless carrier when selecting a particular PLMN or SNPN.

[0117] The AMF may also determine the RAT type of the NR satellite access, and if the UE is accessing the NR using the satellite access, an indication indicating the type of the NR satellite access may be provided on the N2 interface. In addition, for the serving PLMN to implement efficient mobility restrictions for NR access, the TA in which the cell of each NR satellite RAT type is deployed must be different from the TAs of other different satellite RAT types and the TAs of the terrestrial access RAT types. Furthermore, the AMF may initiate deregistration of the UE when it receives an N2 UE Context Release Request with a cause value indicating that the UE is not in the PLMN serving area.

[0118] Herein, communication via an NTN is also referred to as communication via NR satellite access, or communication via satellite access, or 5GSAT communication, or NTN communication, etc. Also, an NR connection via a satellite (i.e., an NTN) is also referred to as NR satellite access, or connection or access via a satellite, or satellite access, etc. Also, the NR satellite access may be a 3GPP access.

[0119] In addition, the coverage of NR satellite access provided by a satellite or satellite constellation may be discontinuous, also referred to as discontinuous network coverage, discontinuous coverage, or NR satellite access discontinuous coverage. Here, discontinuous coverage may be due to, for example, the fact that the satellite or satellite constellation moves over time with respect to a particular location on the Earth, resulting in discontinuity in the coverage that the satellite or satellite constellation can provide.

[0120] In addition, it is assumed that a UE connected to a network via NR satellite access providing such discontinuous coverage will move between out of coverage and in coverage in a time series. For this reason, each device of the UE and / or the network may support part or all of one or more functions including controls, parameters, or procedures for supporting the discontinuous network coverage provided by the NR satellite access. In this case, in coverage may mean a coverage (area) where the UE can communicate with a satellite, or a coverage (area) where the UE can communicate via a satellite. In addition, out of coverage may mean a coverage (area) where the UE cannot communicate with a satellite, or a coverage (area) where the UE cannot communicate via a satellite.

[0121] More specifically, the one or more features including controls, parameters, or procedures for supporting NR satellite access discontinuous coverage may include satellite coverage availability information, and / or a mobility pattern, and / or an unavailability period, and / or an unavailability period support, and / or a type of unavailability period, and / or an unavailability period duration, and / or a start of unavailability period, and / or an overload control in the discontinuous coverage provided by the NR satellite access, and / or a maximum waiting time for overload control in the discontinuous coverage, and / or a discontinuous coverage wait timer value for overload control in the discontinuous coverage. The information may include a back-off timer in discontinuous coverage provided by the NR satellite access, a back-off timer, and / or timer offset information in the NR satellite access providing discontinuous coverage, and / or a maximum time offset, or a discontinuous coverage maximum NAS signalling wait time. These are described below.

[0122] Satellite coverage availability information may be location and time information related to the expected coverage availability of a satellite or satellite constellation that provides discontinuous coverage, where the UE may use the satellite coverage availability information for satellite access to support discontinuous coverage operation. The satellite coverage availability information may be provided to the UE from an external server via a PDU session or a Short Message Service (SMS).

[0123] The AMF may also use satellite coverage availability information to support satellite access by UEs with discontinuous coverage operation. Furthermore, satellite coverage availability information may be provided to the AMF from O&M (Operation and Maintenance). Here, the satellite coverage availability information provided to the AMF may describe when and where satellite reception is possible in an area. Also, the satellite coverage availability information is not UE specific, and the AMF may be applicable to any UE in the affected area. In other words, the satellite coverage availability information may be information of a location or time when the satellite access provided by a satellite or a group of satellites (satellite constellation) is expected to be available for use by the UE. That is, the satellite coverage availability information may be information indicating the expected in- or out-of-range of the UE at the location and time indicated by the information.

[0124] The satellite coverage availability information may include information indicating, for example, the time and location at which each satellite is expected to be able to provide NR satellite access to terrestrial UEs. Alternatively, the satellite coverage availability information may include information indicating the time and location at which each satellite is able to provide NR satellite access to terrestrial UEs, and the time and location at which each satellite is unable to provide NR satellite access to terrestrial UEs. It goes without saying that terrestrial UEs are not intended to refer only to UEs that are strictly adjacent to the Earth's surface, but also include UEs that are not adjacent to the Earth's surface.

[0125] An unavailability period may be a period or time during which a UE is out of coverage (i.e., out of range) or is expected or assumed to be out of coverage in NR satellite access discontinuous coverage. In addition, the unavailability period may be synonymous with a UE out-of-coverage period, an unreachable period, or an unreachability period. Here, the unavailability period may include an unavailability period due to NR satellite access discontinuous coverage and an unavailability period not due to NR satellite access discontinuous coverage. Furthermore, the unavailability period may be read as an unavailability period due to NR satellite access discontinuous coverage and / or an unavailability period not due to NR satellite access discontinuous coverage. In addition, the unavailability period may be read as an unavailability period duration.

[0126] In addition, an unavailability period that is not due to NR satellite access discontinuous coverage is a period during which the network (i.e., 5GS) becomes unavailable, for example, for several minutes, due to the UE executing a specific event at any time, such as an update of the OS to be executed, an update of the modem firmware, or a silent reset of the modem.

[0127] Here, since the UE cannot use the application function without prior notification from the NW and / or UE due to the unavailability period not depending on the NR satellite access discontinuous coverage, there is a possibility that the operation of the application server and / or the network that depends on the availability of the UE during the period may be affected. For this reason, the UE needs to adjust the unavailability period not depending on the NR satellite access discontinuous coverage between the network and / or the application function. Note that the UE and / or the network may transmit and receive information regarding the unavailability period in order to adjust the unavailability period not depending on the NR satellite access discontinuous coverage. Details will be described later.

[0128] In addition, here, the unavailability period not depending on the non-contiguous NR satellite access coverage may be referred to as a conventional function related to the unavailability period. In this specification, in order to distinguish from "support of the unavailability period by the non-contiguous NR satellite access coverage" described later, the conventional function related to the unavailability period may be referred to as "support of the unavailability period not depending on the non-contiguous NR satellite access coverage".

[0129] In addition, an unavailability period due to discontinuous NR satellite access coverage is a period during which a UE connected to an NR satellite access that provides discontinuous coverage is out of range of the NR satellite access and is unable to use the network (i.e., 5GS) for, for example, a few minutes.

[0130] Here, by considering, for example, ephemeris information and UE location information as information on the satellite orbit, it is possible to predict in advance whether the NR satellite access can provide connectivity to a UE at a specific location on the earth. That is, the UE and / or NW may be able to predict in advance an unavailability period due to non-contiguous coverage of the NR satellite access from the ephemeris information and the UE location information. The UE may receive the ephemeris information as broadcast information from the NR satellite access and / or a control message from the network or user data.

[0131] Here, in an unavailability period not due to NR satellite access discontinuous coverage, it is assumed that the behavior is due to a specific small number of UEs, and after the period, the UEs can reconnect to the NW and / or resume communication. On the other hand, in an unavailability period due to NR satellite access discontinuous coverage, it is assumed that excessive unavailability may occur in the network due to reconnection when a large number of UEs accommodated in the coverage of a cell provided by NR satellite access return to the coverage provided by NR satellite access after being unable to use the cell during the period. For this reason, overload control is required that takes into account the load caused by a large number of UEs reconnecting to the NW via NR satellite access, which is assumed after the unavailability period due to NR satellite access discontinuous coverage. The overload control will be described later. In this way, the parameters, judgments, behaviors, etc. considered by the UE and / or NW may differ depending on whether the unavailability period is due to NR satellite access discontinuous coverage or not.

[0132] In order to realize such an availability period function, information indicating the type of availability period, the duration of the availability period, and / or the start of the availability period is required to determine whether the availability period is due to non-contiguous NR satellite access coverage. These pieces of information are described below.

[0133] Unavailability period support may be capability information indicating support of a function for using an unavailable period. More specifically, in a registration procedure, a UE that supports the unavailable period function may indicate Unavailability period support as part of capability information (5GMM Core Network Capability, or 5GMM capability) in a registration request message for initial registration or every mobility registration (mobility registration, or mobility registration update).

[0134] In addition, the support of the unavailable period may include support of the unavailable period by the non-contiguous NR satellite access coverage and support of the unavailable period not by the non-contiguous NR satellite access coverage. Specific details of the operation etc. will be described later.

[0135] The information may indicate a type of unavailability period, whether the unavailability period is due to non-contiguous NR satellite access coverage, and / or whether the unavailability period is not due to non-contiguous NR satellite access coverage. In other words, for example, the information may indicate a type of unavailability period, whether the unavailability period is due to non-contiguous NR satellite access coverage.

[0136] The Unavailability period duration may be information indicating the duration of the Unavailability period. Furthermore, a timer may be executed using the Unavailability period duration as a timer value. Here, the Unavailability period duration may be information associated with the type of the Unavailability period, and the UE and / or NW may transmit or store the Unavailability period duration in association with the type of the Unavailability period.

[0137] The start of the unavailability period may be information indicating a timing or time that specifies the start of the unavailability period. More specifically, for example, the start of the unavailability period may be information indicating a timing or time at which an unavailability period due to NR satellite access discontinuous coverage starts. Note that the start of the unavailability period may be information that is not used in an unavailability period that is not due to NR satellite access discontinuous coverage, or may be information that is used. Also, the start of the unavailability period may be received and stored by the UE by broadcast information from the NR satellite access and / or a message from the NW. Furthermore, the start of the unavailability period may be information associated with the type of the unavailability period, or may not be associated with it.

[0138] Here, the UE out-of-coverage period may be determined based on satellite coverage information and a UE mobility pattern. The UE out-of-coverage period may be synonymous with the unavailability period, and the UE out-of-coverage period described in this specification may be read as the unavailability period. Furthermore, the UE out-of-coverage period may be determined by the UE, or by the network or each network device. More specifically, for example, the UE may transmit the determined UE out-of-coverage period to the network, and the network or each network device may receive and store it.

[0139] Also, for example, the network or any network device (e.g., AMF) may transmit the determined UE out-of-service period to the UE, the network, or other network device, and the UE, the network, or other network device may receive and store the UE out-of-service period. The UE out-of-service period is also referred to as a period during which the UE is out of service.

[0140] Here, the UE out-of-service period may be a period during which the UE is out of service, or a timer or timer value corresponding to the period during which the UE is out of service. Also, the UE out-of-service period may be an unreachability period, or a period indicated by the unreachability period or a corresponding timer or timer value. Furthermore, for example, the unreachability period may be a timer or timer value included in the "Unreachability period duration IE". Also, if the UE out-of-service period is a timer or timer value corresponding to the period during which the UE is out of service, the timer may be started when the UE transitions to an out-of-service state or an idle state (idle mode).

[0141] Also, for example, the UE may use an existing timer or a timer value corresponding to the UE out-of-coverage period, or may use a new timer different from the existing timer. More specifically, for example, the UE out-of-coverage period may be a timer or a timer value included in a "UE out-of-coverage period duration Information Element (IE)". Furthermore, the "UE out-of-coverage period duration IE" may be an existing timer or a timer value (for example, GPRS Timer 3 IE), or may be information indicating a new timer or a new timer value for 5GSAT communication. Note that, for example, when the UE out-of-coverage period is an unreachability period, a timer or a timer value indicating a period corresponding to the UE out-of-coverage period may be included in the "UE out-of-coverage period duration IE" and / or the "Unreachability period duration IE".

[0142] In addition, when the UE determines the UE out-of-service period, the determination may be based on satellite coverage availability information and a UE mobility pattern provided by the network, or on satellite coverage availability information and a UE mobility pattern held by the UE. For example, the UE may determine the UE out-of-service period based on satellite coverage availability information provided by the network and a UE mobility pattern provided by the network. Alternatively, for example, the UE may determine the UE out-of-service period based on satellite coverage availability information provided by the network and a UE mobility pattern held by the UE. Alternatively, for example, the UE may determine the UE out-of-service period based on satellite coverage availability information held by the UE and a UE mobility pattern held by the UE, but is not limited thereto.

[0143] Furthermore, for example, if the UE is able to determine the UE out-of-coverage period and if the UE determines that it will remain out of service for the period indicated by the UE out-of-coverage period, it may perform a Mobility Registration Update procedure before the start of the Unreachability period. Furthermore, the UE may request a Mobile Initiated Connection Only (MICO) mode parameter, extended DRX (eDRX) parameter in CM-IDLE, or other NAS timer using a related procedure that takes into account the UE out-of-coverage period, and in this case, not include the UE out-of-coverage period if the UE requests to use MICO mode or eDRX. Alternatively, the UE may inform the network of the UE out-of-coverage period when it is about to leave satellite coverage, and may further perform a Mobility Registration Update procedure when it returns to coverage via any access type.

[0144] The AMF may adjust the mobile reachable timer and / or the implicit unregistration timer so that the AMF does not implicitly deregister the UE during the availability period.

[0145] Overload control in discontinuous coverage provided by NR satellite access is a control and / or function for avoiding excessive signal load on the network when a large number of UEs return from outside the range of NR satellite access to the range again. Furthermore, overload control in discontinuous coverage may be control using a maximum waiting time, and / or a Disco wait range, and / or a maximum time offset, or a discontinuous coverage maximum NAS signalling wait time. Furthermore, the maximum waiting time may be a time determined by the AMF until a UE that has returned to the range of satellite access is allowed to start NAS signalling with the network. In other words, for the overload control, the AMF may determine a maximum waiting time until a UE is allowed to start NAS signalling with the network. Here, the maximum waiting time may be, for example, Disco wait range and / or Maximum Time Offset or Discontinuous coverage maximum NAS signalling wait time, and unless otherwise specified in this specification, these may be synonymous.

[0146] More specifically, for example, in the overload control in discontinuous coverage using the maximum latency, the AMF first determines the maximum latency based on the network configuration, or the priority user, or the priority service, and transmits the maximum latency to the UE during the registration procedure or the UE configuration update procedure. Next, if the UE that receives the maximum latency has already received the maximum latency of the same RAT type and PLMN, the UE may replace the stored or saved maximum latency. Furthermore, the UE that receives the maximum latency may select a random value with the maximum latency as an upper limit, and determine the discontinuous coverage wait timer value. In other words, for example, if the UE has stored or saved the discontinuous coverage maximum NAS signaling latency for each PLMN and / or satellite NG-RAN RAT type, when the UE receives the discontinuous coverage maximum NAS signaling latency for the same combination of PLMN and / or satellite NG-RAN RAT type, the UE may update the maximum NAS signaling latency to the latest value.

[0147] Wherein, the discontinuous coverage waiting timer may be a timer that restricts the UE from connecting to the network via the satellite access, and further, the UE may execute the discontinuous coverage waiting timer based on a discontinuous coverage waiting timer value determined by the UE.

[0148] In addition, when the UE returns to the coverage area of ​​the NR satellite access from outside the coverage area with the same RAT (Radio Access Technology) type and PLMN, the UE starts a discontinuous coverage wait timer. Note that the UE that is running the discontinuous coverage wait timer must not start NAS signaling for the RAT type and PLMN. Through the above procedures and processing, multiple UEs that return to the coverage area each run the discontinuous coverage wait timer with a different random value, which makes it possible to control and reduce excessive signal load on the network.

[0149] Here, the maximum waiting time determined by the AMF may be included in an MM message transmitted and received during an MM (Mobility Management) procedure and transmitted to the UE. More specifically, for example, the MM procedure in which the AMF transmits the maximum waiting time to the UE may be a registration procedure or a UE configuration update procedure. Furthermore, for example, the MM message in which the AMF includes the maximum waiting time may be, for example, a registration acceptance message, a registration rejection message, or a configuration update command message. In other words, the maximum waiting time may be included in an MM message and transmitted from the AMF to the UE in an MM procedure such as a registration procedure or a UE configuration update procedure.

[0150] Also, if the UE has stored a discontinuous coverage maximum NAS signal latency due to discontinuous coverage, when it goes out of coverage (i.e. out of range) and then comes back in coverage (i.e. in range) of the NR satellite access, the UE shall set the discontinuous coverage maximum NAS signal latency value to a random value up to the discontinuous coverage maximum NAS signal latency stored for this PLMN and satellite NG-RAN RAT type and start this timer. While the discontinuous coverage maximum NAS signal latency timer is running, the UE shall not initiate any NAS signals on that satellite NG-RAN RAT type and PLMN.

[0151] Furthermore, if the UE receives a paging message and there is an emergency service pending, or if the UE enters a TAI outside the registration area, the UE may stop the timer based on the non-continuous coverage maximum NAS signaling latency and start NAS signaling.

[0152] Also, the UE or the network or each device using the function related to the maximum latency may support the maximum latency. In other words, if the UE or the network or each device supports the maximum latency, for example, the AMF may have the capability to determine the maximum latency, or the UE may have the capability to select or determine the waiting timer for discontinuous coverage from the maximum latency received. In other words, the UE or the network or each device supporting communication via NR satellite access may support the maximum latency as a function for discontinuous coverage.

[0153] The back-off timer in discontinuous coverage provided by NR satellite access may be a timer provided by the AMF to the UE to prevent the initiation of Mobile Originated (MO) data transmission or signaling before the UE is about to go out of coverage.

[0154] In other words, the back-off timer in the discontinuous satellite coverage provided to the UE by the AMF may be a back-off timer that is started to end when the UE is in range (i.e., the coverage period of the NR satellite access) based on the satellite coverage availability information, and the UE may be prohibited from starting MO data transmission or signaling while the timer is running. Also, if the UE is still in the same satellite communication area after the timer expires, it may start MO data transmission or signaling, or if it finds a cell of another TN or NTN, it may stop the timer and register through a new access network and transmit MO data.

[0155] In addition, the AMF that provided the back-off timer to the UE may initiate an AN release procedure. In addition, the back-off timer in the discontinuous satellite coverage may use an existing timer or may be defined and used as a new timer.

[0156] The timer offset information in NR satellite access providing discontinuous coverage may be information indicating a timer offset value that corresponds to a timer executed while the UE is in range or a timer executed while the UE is out of range, taking into account the coverage recognized by the UE or the network from the satellite coverage availability information and a physical coverage gap due to the movement of the UE or the orbit of the satellite, etc. In this specification, the timer offset information in NR satellite access providing discontinuous coverage is also referred to as timer offset information indicating a time or period, or timer offset information, or timer offset, or offset information, or simply offset, etc.

[0157] Here, the offset information may be information or parameters preconfigured in the UE, determined by the UE, or determined by the network. More specifically, for example, the offset information may be information or parameters preconfigured in the UE. Or, the offset information may be information or parameters determined by the network, transmitted to the UE, and stored by the received UE. Or, the offset information may be information or parameters determined by the UE, transmitted to the network, and stored by the network or each device.

[0158] The timer offset information may be associated with one or more timers. That is, the timer offset information may be associated with the same number of offset information for one or more timers, or one offset information may be associated with one or more timers. Here, the timer to which the offset information is associated may be information associated with a period or timer indicating a time during which the UE corresponding to the satellite coverage availability information is in range, and / or information associated with a UE out-of-range period. More specifically, for example, the offset information may be an offset value of a timer used to specify a time to advance or delay the start or end of a timer corresponding to a period during which the UE is out of range or in range, taking into account discontinuous coverage in NR satellite access. In other words, for example, when the offset information is information indicating that the expiration time of a timer corresponding to a UE out-of-range period is extended, the UE may start the timer based on a value obtained by adding the value of the offset information to the timer value.

[0159] In addition, a UE connected to a network via a TN or NTN and in a registered state (RM-REGISTERED state) may perform a Mobility Registration Update procedure if the current TAI of the serving cell is not included in the list of TAIs that the UE has received from the network, in order to maintain the registration and enable the AMF to page the UE. In this specification, the Mobility Registration Update procedure is also simply referred to as Mobility Registration Update.

[0160] Furthermore, when the UE is connected to the network, particularly via an NTN (i.e., NR satellite access), in addition to the above conditions for performing the mobility registration update procedure when connecting to the network via a TN or NTN, the following conditions shall be taken into account:

[0161] First, a moving radio cell for NR satellite access may be able to indicate support of one or more TACs per PLMN, where a UE registered in a PLMN may access a radio cell as long as at least one supported TAC of the RPLMN or an equivalent RPLMN is part of the UE registration area and does not need to perform a mobility registration update procedure, and the UE must perform a mobility registration update procedure when accessing a radio cell where none of the TACs supported by the RPLMN or an equivalent RPLMN is part of the UE registration area.

[0162] Furthermore, when the UE indicates the last accessed TAI in a mobility registration update, it may be able to indicate a TAI that is supported in a radio cell of the RPLMN or an equivalent RPLMN that the UE last accessed before the registration update and that is part of the UE registration area.

[0163] [3.2. Description of Identification Information in Each Embodiment] The first identification information in the present invention is capability information of the UE. The first identification information may be 5GMM capability, or 5GMM capability IE (Information Element), or information included as a part of the 5GMM capability. The first identification information may be capability information of the UE indicating whether or not the UE supports an unavailability period taking into account NR satellite access discontinuous coverage.

[0164] Here, the support of the unavailability period may include support of the unavailability period by the NR satellite access non-contiguous coverage indicated by the first identification information, and / or support of the unavailability period not depending on the NR satellite access non-contiguous coverage. Also, the support of the unavailability period by the NR satellite access non-contiguous coverage indicated by the first identification information may indicate that the out-of-service period in the non-contiguous coverage during the NR satellite access connection can be controlled using a conventional function related to the unavailability period (see Non-Patent Document 3). In this specification, in order to distinguish from "support of the unavailability period by the NR satellite access non-contiguous coverage", the above-mentioned conventional function related to the unavailability period may be referred to as "support of the unavailability period not depending on the NR satellite access non-contiguous coverage".

[0165] Furthermore, the first identification information may have multiple forms, which are referred to herein as first identification information #1, and / or first identification information #2, and / or first identification information #3. Each form of the first identification information is described below.

[0166] First, the first identification information #1 may be capability information indicating whether the UE supports an unavailability period due to non-contiguous NR satellite access coverage. Here, the first identification information #1 may be information different from information indicating support of an unavailability period not depending on non-contiguous NR satellite access coverage. In other words, the information indicating unavailability period support may include information indicating unavailability period support not depending on non-contiguous NR satellite access coverage by the first identification information #1 and information indicating unavailability period support not depending on non-contiguous NR satellite access coverage.

[0167] The UE may indicate that it supports the unavailability period due to the NR satellite access non-contiguous coverage by including the first identification information #1 in a message and transmitting it to the network (NW). For example, when the UE indicates to the NW that it supports both the unavailability period due to the NR satellite access non-contiguous coverage and the unavailability period not due to the NR satellite access non-contiguous coverage, the UE may transmit the first identification information #1 and information indicating support of the unavailability period not due to the NR satellite access non-contiguous coverage in a message to the NW.

[0168] In addition, unavailability period support not based on NR satellite access non-contiguous coverage may be indicated as an UN-PER bit in the 5GMM capability IE, and the first identification information #1 may be indicated as information different from the UN-PER bit in the 5GMM capability IE.

[0169] Furthermore, the first identification information #2 may be capability information indicating whether the UE supports an availability period.

[0170] Here, for example, the first identification information #2 may be capability information indicating that the UE supports either an availability period due to NR satellite access non-contiguous coverage or an availability period not due to NR satellite access non-contiguous coverage.

[0171] Alternatively, for example, the first identification information #2 may be capability information indicating that the UE supports an unavailability period due to non-contiguous NR satellite access coverage. In this case, for example, the UE may indicate to the network that it supports the unavailability period due to non-contiguous NR satellite access coverage by transmitting the first identification information #2 together with the third identification information indicating the type of the unavailability period due to non-contiguous NR satellite access coverage in a message. Furthermore, in this case, the network that receives the message including the first identification information #2 together with the third identification information indicating the type of the unavailability period due to non-contiguous NR satellite access coverage from the UE may recognize that the UE supports the unavailability period due to non-contiguous NR satellite access coverage.

[0172] Conversely, for example, when a UE that includes first identification information #2 in a message does not include third identification information indicating a type of an unavailability period due to NR satellite access discontinuous coverage in the message, or includes third identification information indicating a type of an unavailability period not due to NR satellite access discontinuous coverage, the UE may indicate to the NW that it supports an unavailability period not due to NR satellite access discontinuous coverage. In this case, the NW that receives the message may recognize that the UE supports an unavailability period not due to NR satellite access discontinuous coverage.

[0173] Also, for example, when the UE supports an availability period due to discontinuous NR satellite access coverage, the first identification information #2 may be set to indicate that the availability period is supported. Also, for example, when the UE supports an availability period not due to discontinuous NR satellite access coverage, the first identification information #2 may be set to indicate that the availability period is supported.

[0174] In addition, the first identification information #2 may be indicated using the UN-PER bit in the 5GMM capability IE.

[0175] In addition, the first identification information #3 may be capability information indicating that the UE supports an availability period due to NR satellite access non-contiguous coverage and / or supports an availability period not due to NR satellite access non-contiguous coverage.

[0176] In other words, for example, the first identification information #3 may be capability information indicating that neither support of an availability period due to NR satellite access non-contiguous coverage nor support of an availability period not due to NR satellite access non-contiguous coverage is supported. Or, for example, the first identification information #3 may be capability information indicating that only support of an availability period due to NR satellite access non-contiguous coverage is supported. Or, for example, the first identification information #3 may be capability information indicating that only support of an availability period not due to NR satellite access non-contiguous coverage is supported. Or, for example, the first identification information #3 may be capability information indicating that both support of an availability period due to NR satellite access non-contiguous coverage and support of an availability period not due to NR satellite access non-contiguous coverage are supported.

[0177] More specifically, for example, when a UE indicates that it supports an unavailability period due to non-contiguous NR satellite access coverage, the UE may include first identification information #3 indicating that it supports an unavailability period due to non-contiguous NR satellite access coverage in a message and transmit the message to the NW. In this case, the NW that receives the first identification information #3 may recognize that the UE supports an unavailability period due to non-contiguous NR satellite access coverage.

[0178] In this specification, when simply referring to the first identification information, it may indicate any of the first identification information #1, the first periodic information #2, or the first identification information #3. Furthermore, when simply referring to the first identification information, it may indicate that the UE supports NR satellite access non-contiguous coverage, unless otherwise specified.

[0179] In other words, in this specification, when simply describing the first identification information, the first identification information may be in any form indicated by the description of the first identification information. More specifically, for example, when describing "first identification information indicating that the UE supports an unavailability period due to non-contiguous NR satellite access coverage," the first identification information may be any of first identification information #1 indicating that the UE supports an unavailability period due to non-contiguous NR satellite access coverage, first identification information #2 indicating that the UE supports an unavailability period due to non-contiguous NR satellite access coverage, or first identification information #3 indicating that at least the UE supports an unavailability period due to non-contiguous NR satellite access coverage.

[0180] Further details of the behavior of the UE and NW based on the first identification information are also described in Chapter 4 and / or Chapter 5.

[0181] The second identification information in the present invention is capability information of a network (NW). The second identification information may be included as a part of 5GS network feature support, 5GS network feature support IE, or 5GS network feature support. In addition, the second identification information may be capability information of a NW indicating whether or not the NW supports an unavailability period taking into account NR satellite access discontinuous coverage.

[0182] Here, the support of the unavailability period may include support of the unavailability period due to the non-contiguous NR satellite access coverage indicated by the second identification information, and / or support of the unavailability period not due to the non-contiguous NR satellite access coverage. Also, the support of the unavailability period due to the non-contiguous NR satellite access coverage indicated by the second identification information may indicate that the out-of-service period in the non-contiguous coverage during the NR satellite access connection can be controlled using a conventional function related to the unavailability period (see Non-Patent Document 3).

[0183] Furthermore, the second identification information may have multiple forms, which are referred to herein as second identification information #1, and / or second identification information #2, and / or second identification information #3. Each form of the second identification information is described below.

[0184] First, the second identification information #1 may be capability information indicating whether the NW supports an unavailability period due to non-contiguous NR satellite access coverage. Here, the second identification information #1 may be information different from information indicating support of an unavailability period not depending on non-contiguous NR satellite access coverage. In other words, the information indicating unavailability period support may include information indicating unavailability period support not depending on non-contiguous NR satellite access coverage by the second identification information #1 and information indicating unavailability period support not depending on non-contiguous NR satellite access coverage.

[0185] Furthermore, the UE may indicate that it supports the unavailability period due to the NR satellite access non-contiguous coverage by including the second identification information #1 in a message and transmitting the message to the UE. Furthermore, for example, when the NW indicates to the UE that it supports both the unavailability period due to the NR satellite access non-contiguous coverage and the unavailability period not due to the NR satellite access non-contiguous coverage, the NW may transmit the second identification information #1 and information indicating support of the unavailability period not due to the NR satellite access non-contiguous coverage in a message to the UE.

[0186] In addition, the availability period support not based on NR satellite access non-contiguous coverage may be indicated as an UN-PER bit in the 5GS network feature support IE, and the first identification information #1 may be indicated as information different from the UN-PER bit in the 5GS network feature support IE.

[0187] Also, the second identification information #2 may be capability information indicating whether the NW supports an availability period.

[0188] Here, for example, the second identification information #2 may be capability information indicating that the NW either supports an availability period due to NR satellite access non-contiguous coverage or supports an availability period not due to NR satellite access non-contiguous coverage.

[0189] Alternatively, for example, the second identification information #2 may be capability information indicating that the NW supports the unavailability period due to the non-contiguous NR satellite access coverage. In this case, for example, the UE may indicate to the UE that it supports the unavailability period due to the non-contiguous NR satellite access coverage by transmitting the second identification information #2 together with the third identification information indicating the type of the unavailability period due to the non-contiguous NR satellite access coverage in a message. Furthermore, in this case, the UE that receives the message including the second identification information #2 together with the third identification information indicating the type of the unavailability period due to the non-contiguous NR satellite access coverage from the UE may recognize that the NW supports the unavailability period due to the non-contiguous NR satellite access coverage.

[0190] Conversely, for example, when a network that includes second identification information #2 in a message does not include third identification information indicating a type of an unavailability period due to NR satellite access discontinuous coverage in the message, or includes third identification information indicating a type of an unavailability period not due to NR satellite access discontinuous coverage, the UE may indicate to the UE that it supports an unavailability period not due to NR satellite access discontinuous coverage. In this case, a UE that receives the message may recognize that the network supports an unavailability period not due to NR satellite access discontinuous coverage.

[0191] Also, for example, when the NW supports an unavailability period due to NR satellite access discontinuous coverage, the second identification information #2 may be set to indicate that the unavailability period is supported. Also, for example, when the NW supports an unavailability period not due to NR satellite access discontinuous coverage, the second identification information #2 may be set to indicate that the unavailability period is supported.

[0192] In addition, the second identification information #2 may be indicated using the UN-PER bit in the 5GS network feature support IE.

[0193] In addition, the second identification information #3 may be capability information indicating that the NW supports an availability period due to non-contiguous NR satellite access coverage and / or supports an availability period not due to non-contiguous NR satellite access coverage.

[0194] In other words, for example, the second identification information #3 may be capability information indicating that neither an availability period due to NR satellite access non-contiguous coverage nor an availability period not due to NR satellite access non-contiguous coverage is supported. Or, for example, the second identification information #3 may be capability information indicating that only support of an availability period due to NR satellite access non-contiguous coverage is supported. Or, for example, the second identification information #3 may be capability information indicating that only support of an availability period not due to NR satellite access non-contiguous coverage is supported. Or, for example, the second identification information #3 may be capability information indicating that both support of an availability period due to NR satellite access non-contiguous coverage and support of an availability period not due to NR satellite access non-contiguous coverage are supported.

[0195] More specifically, for example, when the NW indicates that it supports the unavailability period due to the non-contiguous NR satellite access coverage, the NW may include second identification information #3 indicating that it supports the unavailability period due to the non-contiguous NR satellite access coverage in a message and transmit it to the UE. In this case, the UE that receives the second identification information #3 may recognize that the NW supports the unavailability period due to the non-contiguous NR satellite access coverage.

[0196] In this specification, when simply referring to the second identification information, it may indicate any one of the second identification information #1, the second periodic information #2, or the second identification information #3. Furthermore, when simply referring to the second identification information, it may indicate that the NW supports NR satellite access non-contiguous coverage, unless otherwise specified.

[0197] In other words, in this specification, when simply describing the second identification information, the second identification information may be in any form indicated by the description of the second identification information. More specifically, for example, when describing "second identification information indicating that the UE supports an unavailability period due to non-contiguous NR satellite access coverage," the second identification information may be any of second identification information #1 indicating that the UE supports an unavailability period due to non-contiguous NR satellite access coverage, second identification information #2 indicating that the UE supports an unavailability period due to non-contiguous NR satellite access coverage, or second identification information #3 indicating that at least the UE supports an unavailability period due to non-contiguous NR satellite access coverage.

[0198] Further details of the behavior of the UE and NW based on the second identification information are also described in Chapter 4 and / or Chapter 5.

[0199] The third identification information in the present invention is information indicating a type of unavailability period. The type of unavailability period indicated by the third identification information may be a type indicating an unavailability period due to NR satellite access discontinuous coverage, or a type indicating an unavailability period not due to NR satellite access discontinuous coverage. Here, the type indicated by the third identification information may be information indicating the type of unavailability period duration and / or start of unavailability period included in a message transmitted together with the third identification information.

[0200] In other words, for example, the third identification information may indicate the type of the availability period or the availability period duration by being included in a message and transmitted together with the availability period duration. Furthermore, a UE or NW that receives the third identification information, the availability period duration, and the start of unavailability period may recognize that the availability period and the start of unavailability period are the types indicated by the third identification information, and may store the availability period in association with the type indicated by the third identification information.

[0201] More specifically, for example, a UE or NW that has received the third identification information indicating the type of the unavailability period due to NR satellite access discontinuous coverage, the unavailability period duration, and / or the start of the unavailability period may store the received unavailability period duration and / or the start of the unavailability period in association with the type of the unavailability period due to NR satellite access discontinuous coverage. Furthermore, the UE or NW may execute a timer based on the unavailability period duration as the unavailability period due to NR satellite access discontinuous coverage based on the start of the unavailability period.

[0202] The third identification information may have a plurality of forms, and these forms are referred to herein as third identification information #1, and / or third identification information #2, and / or third identification information #3. Each form of the third identification information is described below.

[0203] First, the third identification information #1 may be identification information indicating a type of an unavailability period due to non-contiguous NR satellite access coverage. In other words, the unavailability period duration and / or start of unavailability period transmitted together with the third identification information #1 may indicate the type of unavailability period due to non-contiguous NR satellite access coverage.

[0204] In other words, for example, if the UE or NW does not include the third identification information #1 in the message and transmits the unavailability period duration and / or the start of unavailability period, these may indicate that the unavailability period is a type that is not based on NR satellite access non-contiguous coverage. Furthermore, the UE or NW receiving the message may recognize that the unavailability period duration and / or the start of unavailability period are a type of unavailability period that is not based on NR satellite access non-contiguous coverage and may store them in association with the type.

[0205] Here, the UE and / or NW may indicate whether the type of the unavailability period is due to the NR satellite access non-contiguous coverage by including or not including the third identification information #1 in the message. Alternatively, the UE and / or NW may indicate whether the type of the unavailability period is due to the NR satellite access non-contiguous coverage by using the third identification information #1 together with the third identification information #2 described later, and details of this case will be described later.

[0206] Also, the third identification information #2 may be identification information indicating a type of unavailability period that is not based on NR satellite access non-contiguous coverage. That is, the unavailability period duration and / or start of unavailability period transmitted together with the third identification information #2 may mean that the type of unavailability period is not based on NR satellite access non-contiguous coverage.

[0207] The third identification information #2 may be an identification information used on the premise of the above-mentioned third identification information #1. In other words, for example, when the UE or NW indicates a type of unavailability period due to NR satellite access discontinuous coverage, the UE or NW may include the third identification information #1 in the message together with the unavailability period duration and / or the start of unavailability period. Or, for example, when the UE or NW indicates a type of unavailability period not due to NR satellite access discontinuous coverage, the UE or NW may include the third identification information #2 in the message together with the unavailability period duration and / or the start of unavailability period.

[0208] Also, the third identification information #3 may be identification information indicating a type of unavailability period due to NR satellite access discontinuous coverage and / or a type of unavailability period not due to NR satellite access discontinuous coverage, where the unavailability period duration and / or the start of unavailability period may be the type indicated by the third identification information #3.

[0209] In other words, for example, the third identification information #3 may be identification information indicating only the type of the unavailability period due to the NR satellite access non-contiguous coverage. Or, the third identification information #3 may be identification information indicating only the type of the unavailability period not due to the NR satellite access non-contiguous coverage. Or, the third identification information #3 may be identification information indicating both the type of the unavailability period due to the NR satellite access non-contiguous coverage and the type of the unavailability period not due to the NR satellite access non-contiguous coverage. Or, the third identification information #3 may be identification information indicating neither the type of the unavailability period due to the NR satellite access non-contiguous coverage nor the type of the unavailability period not due to the NR satellite access non-contiguous coverage.

[0210] In addition, when the third identification information is in the form of third identification information #3, the unavailability period duration and / or the start of unavailability period may be, for example, in a list format capable of storing information of the corresponding type. In other words, for example, when the third identification information #3 indicates both the type of unavailability period due to NR satellite access discontinuous coverage and the type of unavailability period not due to NR satellite access discontinuous coverage, the unavailability period duration and / or the start of unavailability period may be transmitted as information in a format corresponding to each type.

[0211] In this specification, when simply referring to the third identification information, it may indicate any one of the third identification information #1, the third identification information #1 and / or the third identification information #2, or the third identification information #3. Furthermore, when simply referring to the third identification information, it may be a type indicating an unavailability period due to non-contiguous NR satellite access coverage, unless otherwise specified.

[0212] Further details of UE and network behavior based on the third identity information are also provided in Chapter 4 and / or Chapter 5.

[0213] Details of the UE and network behavior based on one or a combination of the above first to third identification information are not limited to those described in this chapter, but are also described in Chapter 4 and / or Chapter 5.

[0214] [4. Description of procedures used in each embodiment] Next, procedures used in each embodiment will be described, which may include a registration procedure.

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

[0216] The details of the registration procedure are explained below.

[0217] [4.1. Registration Procedure] First, the registration procedure will be described with reference to FIG. 6. The registration procedure is a procedure in 5GS. In the following of this section, this procedure refers to the registration procedure. The registration procedure is a procedure for the UE to take the initiative in registering to the access network_B and / or the core network_B and / or the DN. If the UE is not registered to the network, it can execute this procedure at any time, such as when the power is turned on. In other words, if the UE is in a deregistered state (RM-DEREGISTERED state), it can start this procedure at any time. In addition, each device (especially the UE and the AMF) can transition to a registered state (RM-REGISTERED state) based on the completion of the registration procedure.

[0218] Also, the registration procedure may be an initial registration initiated by the UE, or a mobility and periodic registration update, or a mobility registration update procedure. Here, the mobility registration update procedure may be referred to as a registration procedure for mobility update. These registration procedures may also be MM procedures.

[0219] Furthermore, the registration procedure may be a procedure for updating the location registration information of the UE in the network and / or for periodically notifying the network of the status of the UE from the UE and / or for updating certain parameters related to the UE in the network, or the procedure may be a mobility registration update procedure performed to resume normal service after the expiration of the availability period after the completion of the initial registration procedure.

[0220] This procedure may also be a procedure for registration by the UE via NR satellite access. Furthermore, the PDU session established after completion of this procedure may be a PDU session via the satellite NG-RAN or NR satellite access. In other words, for example, a PDU session established by a PDU session establishment procedure performed after completion of the registration procedure via NR satellite access may be a PDU session via NR satellite access. Or, for example, a PDU session via NR satellite access may be established based on the completion of this procedure.

[0221] The UE may initiate a registration procedure when mobility across TAs is performed. More specifically, the UE may initiate a mobility registration update procedure for re-registration when the UE moves to a TA different from the TA indicated in the TA list held by the UE. Furthermore, the UE may initiate this procedure when a running timer expires. Furthermore, the UE may initiate a registration procedure when it is necessary to update the context of each device due to disconnection or invalidation of a PDU session. Furthermore, the UE may initiate a registration procedure when a change occurs in capability information and / or preferences regarding the establishment of a PDU session of the UE. Furthermore, the UE may initiate a registration procedure periodically. Furthermore, the UE may initiate a registration procedure based on the completion of a UE configuration update procedure. It should be noted that the UE may execute the registration procedure at any timing, not limited to the above.

[0222] Furthermore, even if the UE is in a registered state, the UE may initiate a registration procedure periodically. In other words, the UE may initiate a registration procedure based on the expiration of a timer. In other words, the registration procedure performed periodically may be a Periodic Registration Update procedure.

[0223] In addition, the registration procedure executed based on the mobility of the UE and the registration procedure executed periodically may be expressed as a registration procedure for mobility and registration update. In other words, the registration procedure for mobility and registration update may be a registration procedure executed based on the mobility of the UE, or may be a registration procedure executed periodically. Furthermore, the registration procedure for mobility and registration update may be a registration procedure executed based on a setting update of the UE. Furthermore, the registration procedure for mobility and registration update may be a registration procedure executed to establish a communication path for transmitting and receiving user data. Furthermore, the registration procedure for mobility and registration update may be a registration procedure executed based on a request from the network. Furthermore, in other words, the registration procedure for mobility and registration update may be a registration procedure other than the initial registration procedure. Hereinafter, the registration procedure for mobility and registration update may be expressed as this procedure.

[0224] Next, each step of the registration procedure will be described. Note that the registration procedure described below may be an initial registration procedure, or a registration procedure for mobility and registration renewal.

[0225] First, the UE starts the registration procedure by transmitting a registration request message to the AMF (S600) (S602) (S604). Specifically, the UE transmits an RRC message including a registration request message to the 5G AN (or gNB) (S600). The registration request message is a NAS message. The RRC message may be a control message transmitted and received between the UE and the 5G AN (or gNB). The NAS message is processed in the NAS layer, and the RRC message is processed in the RRC layer. The NAS layer is a layer higher than the RRC layer.

[0226] Here, the UE may transmit the first identification information, and / or the third identification information, and / or the unavailability period duration, and / or the start of the unavailability period in the registration request message.

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

[0228] The UE may also initiate a PDU session establishment procedure during the registration procedure by sending a SM message in or together with a registration request message, where the SM message may be a PDU session establishment request message.

[0229] When the 5G AN (or gNB) receives an RRC message including a registration request message, it selects an AMF to which the registration request message is to be transferred (S602). The 5G AN (or gNB) can select an AMF based on information included in the registration request message and / or the RRC message. The 5G AN (or gNB) extracts the registration request message from the received RRC message and transfers the registration request message to the selected AMF (S604).

[0230] The AMF that receives a registration request message from the UE may recognize and store the meaning of the identification information included in the registration request message.

[0231] When the AMF receives the registration request message, the AMF can execute a first condition determination. The first condition determination is for determining whether the network (or the AMF) accepts the request of the UE. When the first condition determination is true, the AMF starts the procedure of (A) in Fig. 6, whereas when the first condition determination is false, the AMF starts the procedure of (B) in Fig. 6.

[0232] The first condition determination may be performed based on the reception of a registration request message, and / or each identification information included in the registration request message, and / or subscriber information, and / or network capability information, and / or operator policy, and / or network status, and / or user registration information, and / or a context held by the AMF. For example, if the network permits the request of the UE, the first condition determination may be true, and if the network does not permit the request of the UE, the first condition determination may be false. In addition, if the network to which the UE is registered and / or a device in the network supports a function requested by the UE, the first condition determination may be true, and if the network does not support the function requested by the UE, the first condition determination may be false. Furthermore, if the identification information to be transmitted and received is permitted, the first condition determination may be true, and if the identification information to be transmitted and received is not permitted, the first condition determination may be false. In addition, the conditions for determining whether the first condition determination is true or false may not be limited to the above-mentioned conditions.

[0233] First, a case where the first condition determination is true will be described. In the procedure of (A) in Fig. 6, the AMF can first execute the fourth condition determination. The fourth condition determination is for determining whether the AMF transmits and receives an SM message between the AMF and the SMF.

[0234] In addition, the fourth condition determination may be performed based on whether the AMF has received an SM message. In addition, the fourth condition determination may be performed based on whether the registration request message includes an SM message. For example, if the AMF has received an SM message and / or if the registration request message includes an SM message, the fourth condition determination may be true, and if the AMF has not received an SM message and / or if the registration request message does not include an SM message, the fourth condition determination may be false. In addition, the conditions that determine the truth or falsehood of the fourth condition determination may not be limited to the above-mentioned conditions.

[0235] Next, the AMF transmits a registration accept message to the UE via the 5G AN (or gNB) as a response message to the registration request message based on the reception of the registration request message and / or the completion of the transmission and reception of the SM message with the SMF (S608). For example, when the fourth condition determination is false, the AMF may transmit a registration accept message based on the reception of the registration request message from the UE. Also, when the fourth condition determination is true, the AMF may transmit a registration accept message based on the completion of the transmission and reception of the SM message with the SMF. Note that the registration accept message is a NAS message transmitted and received on the N1 interface, but is transmitted and received between the UE and the 5G AN (gNB) in an RRC message.

[0236] The AMF may send a registration acceptance message including the second identification information and / or the third identification information, and / or the availability period duration, and / or the start of the unavailability period.

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

[0238] Furthermore, the AMF may select or determine whether to include the second identification information and / or the third identification information, and / or the availability period duration, and / or the start of unavailability period in the registration acceptance message based on each identification information received by the AMF from the UE or each device, and / or subscriber information, and / or network capability information, and / or operator policy, and / or network status, and / or user registration information, and / or context held by the AMF, etc.

[0239] Furthermore, the AMF may include and send the SM message in a registration accept message, or may send the SM message together with the registration accept message. However, this sending method may be executed when the SM message is included in the registration request message and the fourth condition determination is true. Also, this sending method may be executed when the SM message is included together with the registration request message and the fourth condition determination is true. By performing such a sending method, the AMF can indicate that the procedure for SM has been accepted in the registration procedure. Here, the SM message may be a PDU session establishment request message or a PDU session establishment acceptance message.

[0240] The AMF may also indicate that the UE's request has been accepted by sending a registration acceptance message based on the received identification information, and / or subscription information, and / or network capability information, and / or operator policies, and / or network status, and / or user registration information, and / or context held by the AMF, etc.

[0241] Furthermore, the AMF may include information indicating that some of the UE's requests have been rejected in the registration acceptance message and transmit it, or may indicate the reason why some of the UE's requests have been rejected by transmitting information indicating that some of the UE's requests have been rejected. Furthermore, the UE may recognize the reason why some of the UE's requests have been rejected by receiving information indicating that some of the UE's requests have been rejected. In addition, the reason for the rejection may be information indicating that the content indicated by the identification information received by the AMF is not permitted.

[0242] The UE receives a registration acceptance message from the AMF via the 5G AN (gNB) (S608). By receiving the registration acceptance message, the UE can recognize that the UE's request by the registration request message has been accepted and the contents of various identification information included in the registration acceptance message.

[0243] Here, a UE that receives a registration accept message from the AMF may recognize and store what the received second identification information and / or third identification information, and / or unavailability period duration, and / or start of unavailability period indicate.

[0244] Furthermore, the UE may transmit a registration completion message to the AMF via the 5G AN (gNB) as a response message to the registration acceptance message (S610). Here, the registration completion message is a NAS message transmitted and received on the N1 interface, but is transmitted and received between the UE and the 5G AN (gNB) in an RRC message.

[0245] The AMF receives a registration completion message via the 5G AN (gNB) (S610). In addition, each device completes the procedure of (A) in FIG. 6 based on the transmission and reception of the registration acceptance message and / or the registration completion message.

[0246] Next, a case where the first condition determination is false will be described. In the procedure of (B) of Fig. 6, the AMF transmits a registration reject message to the UE via the 5G AN (gNB) as a response message to the registration request message (S612). Here, the registration reject message is a NAS message transmitted and received on the N1 interface, but is included in an RRC message and transmitted and received between the UE and the 5G AN (gNB).

[0247] Furthermore, the AMF may indicate that the UE's request by the registration request message has been rejected by sending a registration rejection message. Furthermore, the AMF may include information indicating the reason for the rejection in the registration rejection message and transmit it, or may indicate the reason for the rejection by sending the reason for the rejection. Furthermore, the UE may recognize the reason for the rejection of the UE's request by receiving information indicating the reason for the rejection of the UE's request. In addition, the reason for the rejection may be information indicating that the content indicated by the identification information received by the AMF is not permitted.

[0248] The UE receives a registration rejection message from the AMF via the 5G AN (gNB) (S612). By receiving the registration rejection message, the UE can recognize that the UE's request by the registration request message has been rejected and the contents of various identification information included in the registration rejection message. In addition, if the UE does not receive a registration rejection message even after a predetermined period has elapsed after transmitting the registration request message, the UE may recognize that the UE's request has been rejected. Each device completes the procedure (B) in this procedure based on the transmission and reception of the registration rejection message.

[0249] The procedure in FIG. 6(B) may be started when the procedure in FIG. 6(A) is stopped.

[0250] Each device completes the registration procedure based on the completion of the procedure of (A) or (B) in Fig. 6. Each device may transition to a state in which the UE is registered in the network (RM-REGISTERED state) based on the completion of the procedure of (A) in Fig. 6, and may maintain a state in which the UE is not registered in the network (RM-DEREGISTERED state) or transition to a state in which the UE is not registered in the network based on the completion of the procedure of (B) in Fig. 6. Furthermore, the transition of each device to each state may be performed based on the completion of the registration procedure or the establishment of a PDU session.

[0251] The UE may also complete the registration procedure based on receiving the registration accept message or the registration reject message.

[0252] Furthermore, each device may perform processing based on the information transmitted and received in the registration procedure based on the completion of the registration procedure. For example, when transmitting and receiving information indicating that some of the UE's requests have been rejected, the device may recognize the reason why the UE's requests have been rejected. Furthermore, each device may perform this procedure again based on the reason why the UE's request has been rejected, or may perform the registration procedure for the core network_B or another cell.

[0253] Further, the UE may store the identification information received with the registration accept message and / or the registration reject message and may recognize the network's decision upon completion of the registration procedure.

[0254] The UE may recognize the content of the above identification information by receiving a registration acceptance message or a registration rejection message.

[0255] In addition, the behavior to be performed when each piece of identification information is received may be performed based on the received identification information.

[0256] [5. Embodiment] Next, each embodiment of the present invention will be described. Note that each embodiment described in this chapter is based on the definitions of terms and various identification information explained in Chapter 3, and the procedure explained in Chapter 4.

[0257] In addition, each embodiment may be an embodiment that starts in a state where the UE connects to the network via NR satellite access and registration is completed.

[0258] Furthermore, unless otherwise specified, the embodiments of the present invention are not limited to being implemented individually and independently as described in each section of this chapter, but may be implemented as a combination of one or more embodiments described in each section, or one or more embodiments described in each section may be implemented in any order.

[0259] Also, the UE in each embodiment may be in a state where the Maximum Time Offset or the Discontinuous coverage maximum NAS signalling wait time is provided from the network and stored. Here, the Maximum Time Offset and the Discontinuous coverage maximum NAS signalling wait time may be the same. Furthermore, the Maximum Time Offset or the Discontinuous coverage maximum NAS signalling wait time may be determined by the AMF. More specifically, for example, the AMF may determine a time or a timer value corresponding to the Maximum Time Offset or the Discontinuous coverage maximum NAS signalling wait time.

[0260] More specifically, for example, the AMF may provide the maximum time offset or the discontinuous coverage maximum NAS signalling wait time to the UE by including it in a registration accept message transmitted and received during a registration procedure for an initial or mobility update initiated by the UE, and / or a configuration update command message transmitted and received during a UE configuration update or generic UE configuration update procedure initiated by the NW. Furthermore, the UE may store the received maximum time offset or the discontinuous coverage maximum NAS signalling wait time. In addition, when the UE receives a new latest maximum time offset or discontinuous coverage maximum NAS signalling wait time, the UE may replace the already received and / or stored maximum time offset or discontinuous coverage maximum NAS signalling wait time with the latest value.

[0261] Furthermore, a UE that has received and stored the Maximum Time Offset or Discontinuous coverage maximum NAS signalling wait time may set a random value with the Maximum Time Offset or Discontinuous coverage maximum NAS signalling wait time as its maximum value.

[0262] Additionally, due to discontinuous coverage provided by NR satellite access, a UE that moves out of range and then comes back into range may start a timer set to a random value up to the value of the discontinuous coverage maximum NAS signaling latency for that PLMN and satellite NG-RAN RAT type.

[0263] Additionally, the UE of each embodiment may receive and store a discontinuous coverage maximum NAS signaling latency from the network prior to the start of the availability period.

[0264] In addition, unless otherwise specified, the UE and NW in each embodiment may support an availability period due to NR satellite access non-contiguous coverage and an availability period due to NR satellite access non-contiguous coverage.

[0265] In addition, the unavailability period may be interpreted as an unavailability period due to non-contiguous NR satellite access coverage and / or an unavailability period not due to non-contiguous NR satellite access coverage.

[0266] Each embodiment of the invention will be described below.

[0267] [5.1. First embodiment] A first embodiment of the present invention will be described. Hereinafter, in this section, the first embodiment will also be referred to as the present embodiment.

[0268] In the registration procedure for initial or registration update, the UE of this embodiment may transmit a registration request message including the first identity, and / or the third identity (e.g., the third identity #2 or #3), and / or the availability period duration, and / or the start of the unavailability period to the network. In addition, the network receiving this registration request message may transmit a registration accept message including the second identity, the third identity (e.g., the third identity #2 or #3), and the availability period duration, and / or the start of the unavailability period, and / or the discontinuous coverage maximum NAS signalling wait time to the UE, and the UE may receive this message.

[0269] The UE may further receive the discontinuous coverage maximum NAS signaling latency from the network in a Configuration Update Command message in a UE Configuration Update procedure.

[0270] More specifically, the UE of this embodiment, for example, when the UE receives from the network the third identification information #2 or #3 indicating that the value of the unavailability period duration and / or the unavailability period is a type that does not depend on discontinuous coverage provided by NR satellite access, may simply store the unavailability period duration and / or the start of unavailability period and the type of unavailability period indicated by the third identification information #2 or #3, or may store them in association with each other. Here, based on the unavailability period duration and / or the start of unavailability period received together with the type that does not depend on discontinuous coverage provided by NR satellite access, the UE may start or run a timer based on the unavailability period that does not depend on discontinuous coverage provided by NR satellite access. Then, the UE that has completed the execution of the timer may not determine a timer value based on the received discontinuous coverage maximum NAS signaling waiting time, and may not set or start a timer value based on the discontinuous coverage maximum NAS signaling waiting time.

[0271] Here, the UE and NW of this embodiment may support an unavailability period not depending on NR satellite access discontinuous coverage and an unavailability period due to NR satellite access discontinuous coverage. Alternatively, the UE and NW of this embodiment may support an unavailability period not depending on NR satellite access discontinuous coverage and may not support an unavailability period due to NR satellite access discontinuous coverage.

[0272] In addition, the UE may determine, store, and / or set a timer value based on the received discontinuous coverage maximum NAS signaling latency at the time of receiving the received discontinuous coverage maximum NAS signaling latency.

[0273] Alternatively, the UE may not determine and / or store and / or set a timer value based on the discontinuous coverage maximum NAS signaling latency at the time of receiving the discontinuous coverage maximum NAS signaling latency. Also, the UE may determine and / or store and / or set a timer value based on the discontinuous coverage maximum NAS signaling latency after the availability period has elapsed.

[0274] Here, these actions may be based on UE and / or NW capability information or may be determined by the content of information provided and / or stored by the UE and / or NW.

[0275] As described above, the UE of the present embodiment receives, for example, a timer value indicating the duration of an unavailability period, and / or third identification information indicating that the unavailability period is a type that does not depend on discontinuous coverage provided by NR satellite access, and / or a discontinuous coverage maximum NAS signaling waiting time from the network. The UE stores the received timer value indicating the duration of the unavailability period in association with the type indicating that the unavailability period does not depend on discontinuous coverage provided by NR satellite access indicated by the third identification information. The UE starts or executes a timer based on the timer value indicating the duration of an unavailability period that does not depend on discontinuous coverage provided by NR satellite access, and after the timer expires, sets and / or does not start a timer based on the discontinuous coverage maximum NAS signaling waiting time.

[0276] Here, the discontinuous coverage maximum NAS signaling waiting time may be a maximum value of a period or timer indicating the discontinuous coverage maximum NAS signaling waiting time received by the UE from the network. Furthermore, the UE of this embodiment may determine and store a timer value based on, for example, the discontinuous coverage maximum NAS signaling waiting time received from the network. That is, the timer based on the discontinuous coverage maximum NAS signaling waiting time may be a timer whose timer value is a period determined by the UE based on the discontinuous coverage maximum NAS signaling waiting time. When a timer based on a timer value indicating a period of an Unavailability Period not depending on discontinuous coverage provided by NR satellite access expires, the UE may not execute a timer based on a timer value determined based on the discontinuous coverage maximum NAS signaling waiting time, regardless of whether the UE stores a timer value determined based on the discontinuous coverage maximum NAS signaling waiting time.

[0277] Alternatively, the UE of this embodiment may not need to determine, and / or set, and / or start a timer value based on a discontinuous coverage maximum NAS signaling waiting time, for example, when a timer based on a timer value indicating the duration of an unavailability period that is not based on discontinuous coverage provided by NR satellite access expires.

[0278] In addition, when the unavailability period (or unavailability period duration) and / or start of unavailability period received from the network is not based on the discontinuous coverage provided by the NR satellite access, the UE may start a timer using the unavailability period (or unavailability period duration) and / or start of unavailability period that is not based on the discontinuous coverage provided by the NR satellite access, but after the timer expires (i.e., after the unavailability period (or unavailability period duration) that is not based on the discontinuous coverage provided by the NR satellite access has elapsed), the UE may not set a timer value based on the discontinuous coverage maximum NAS signaling waiting time applied to the unavailability period (or unavailability period duration) related to the discontinuous coverage provided by the NR satellite access, and may not start a timer using that timer value.

[0279] In addition, when the unavailability period (or unavailability period duration) and / or start of unavailability period received from the network is not based on the discontinuous coverage provided by the NR satellite access, the UE may start a timer using the unavailability period (or unavailability period duration) and / or start of unavailability period not based on the discontinuous coverage provided by the NR satellite access. However, when the timer expires (i.e., when the unavailability period (or unavailability period duration) not based on the discontinuous coverage provided by the NR satellite access has elapsed), if the UE is within the unavailability period (or unavailability period duration) related to the discontinuous coverage provided by the NR satellite access, the UE may set a timer value based on the discontinuous coverage maximum NAS signaling waiting time after the unavailability period (or unavailability period duration) has elapsed, or may start a timer using that timer value.

[0280] In addition, when the unavailability period (or unavailability period duration) and / or start of unavailability period received from the network is not based on the discontinuous coverage provided by the NR satellite access, the UE may start a timer using the unavailability period (or unavailability period duration) and / or start of unavailability period that is not based on the discontinuous coverage provided by the NR satellite access. However, when the timer expires (i.e., when the unavailability period (or unavailability period duration) that is not based on the discontinuous coverage provided by the NR satellite access has elapsed), if the unavailability period (or unavailability period duration) related to the discontinuous coverage provided by the NR satellite access has elapsed, the UE may not set a timer value based on the discontinuous coverage maximum NAS signaling waiting time, and may not start a timer using that timer value.

[0281] In addition, if the unavailability period (or unavailability period duration) and / or start of unavailability period received from the network is not based on the discontinuous coverage provided by the NR satellite access, the UE may start a timer using the unavailability period (or unavailability period duration) and / or start of unavailability period not based on the discontinuous coverage provided by the NR satellite access, but may stop the timer when the unavailability period (or unavailability period duration) related to the discontinuous coverage provided by the NR satellite access starts before the timer expires (i.e., before the unavailability period (or unavailability period duration) not based on the discontinuous coverage provided by the NR satellite access has elapsed).

[0282] In addition, if the unavailability period (or unavailability period duration) and / or start of unavailability period received from the network is due to discontinuous coverage provided by NR satellite access, the UE may start a timer using a timer value set based on the discontinuous coverage maximum NAS signaling latency, but may stop the timer if an unavailability period (or unavailability period duration) that is not due to discontinuous coverage provided by NR satellite access starts before the timer expires.

[0283] [5.2. Second embodiment] A second embodiment of the present invention will be described below. In this section, the second embodiment will also be referred to as the present embodiment.

[0284] This embodiment may be the case where the UE and NW support both an availability period not due to NR satellite access discontinuous coverage and an availability period due to NR satellite access discontinuous coverage.

[0285] In addition, when the UE stores a timer associated with an availability period not due to NR satellite access discontinuous coverage and a timer associated with an availability period due to NR satellite access discontinuous coverage, the UE may recognize which of the stored timers to execute based on control information transmitted from the NW, and start or execute the timer.

[0286] Here, the control information that the UE receives from the NW may be information indicating either or both of a timer associated with an unavailability period not due to NR satellite access discontinuous coverage and / or a timer associated with an unavailability period due to NR satellite access discontinuous coverage. Furthermore, the UE that receives the control information may recognize the contents indicated by the control information and start or execute the timer indicated by the control information.

[0287] More specifically, for example, when the control information received by the UE from the NW includes information indicating a timer associated with an unavailability period not depending on NR satellite access discontinuous coverage, the UE may recognize to execute the stored timer associated with the unavailability period not depending on NR satellite access discontinuous coverage, and may further start or execute it. Note that here, the control information indicating the timer associated with the unavailability period not depending on NR satellite access discontinuous coverage and / or the timer associated with the unavailability period due to NR satellite access discontinuous coverage received by the UE from the NW may be included in a registration accept message received by the UE from the AMF and / or a UE configuration command message, or may be included in an MM message transmitted by the NW to the UE, but is not limited thereto.

[0288] Or, for example, if the control information received by the UE from the NW includes information indicating a timer associated with an unavailability period due to NR satellite access discontinuous coverage, the UE may recognize to execute the timer associated with the unavailability period due to NR satellite access discontinuous coverage that it has stored, and may further start or execute the timer.

[0289] In addition, if the timer executed by the UE is a timer associated with the unavailability period due to the non-contiguous coverage of the NR satellite access, after the expiration of the timer, the UE may further execute a timer based on the non-contiguous coverage maximum NAS signaling latency, where the behavior of the timer based on the non-contiguous coverage maximum NAS signaling latency may be the behavior described in the fourth embodiment.

[0290] Here, for example, the NW may determine the control information to be transmitted to the UE by taking into consideration the larger timer value from a timer associated with an unavailability period not depending on the NR satellite access discontinuous coverage and a timer associated with an unavailability period depending on the NR satellite access discontinuous coverage. For example, the NW may select and determine a timer with a larger timer value.

[0291] Or, for example, the control information that the NW transmits to the UE may select and determine a timer with a later expiration time from among a timer associated with an availability period not due to NR satellite access discontinuous coverage and a timer associated with an availability period due to NR satellite access discontinuous coverage.

[0292] Or, for example, the control information transmitted by the NW to the UE may select and determine a timer value from a timer associated with an unavailability period not due to NR satellite access discontinuous coverage and a timer associated with an unavailability period due to NR satellite access discontinuous coverage based on a UE policy and / or a network policy.

[0293] Incidentally, storing a timer may mean storing a timer value in association with each timer.

[0294] The UE of this embodiment stores, for example, a timer associated with an unavailability period not depending on NR satellite access discontinuous coverage and a timer associated with an unavailability period due to NR satellite access discontinuous coverage. Furthermore, the UE storing these timers may recognize and / or determine which timer stored in the UE to execute based on control information received from the NW, and start or execute the timer. Here, the control information received by the UE from the network may be information indicating either or both of the timer associated with the unavailability period not depending on NR satellite access discontinuous coverage and / or the timer associated with the unavailability period due to NR satellite access discontinuous coverage. Furthermore, the UE receiving the control information may recognize the contents indicated by the control information, and start or execute the timer indicated by the control information.

[0295] [5.3. Third embodiment] A third embodiment of the present invention will be described below. In this section, the third embodiment is also referred to as the present embodiment.

[0296] The UE of this embodiment may store a timer value determined based on a timer based on a discontinuous coverage maximum NAS signaling latency in addition to a timer associated with an availability period not due to NR satellite access discontinuous coverage and / or a timer associated with an availability period due to NR satellite access discontinuous coverage, and may further start or execute a timer associated with an availability period not due to NR satellite access discontinuous coverage.

[0297] Subsequently, if the UE is out of range due to an unavailability period due to discontinuous coverage of the NR satellite access when the timer expires, the UE may perform a PLMN selection procedure and / or RAT selection.

[0298] Alternatively, if the UE determines that a timer associated with an unavailability period due to discontinuous coverage of the NR satellite access has not expired when the timer expires, the UE may perform a PLMN selection procedure and / or RAT selection, where the UE may be out of range of the NR satellite access when the timer expires and a timer associated with an unavailability period due to discontinuous coverage of the NR satellite access has not expired when the timer expires.

[0299] Alternatively, the UE of this embodiment may store, for example, a timer associated with an unavailability period not depending on NR satellite access non-contiguous coverage. Furthermore, the UE may store a timer value determined by the UE based on a timer based on a non-contiguous coverage maximum NAS signaling latency. The UE may perform a PLMN selection procedure if a timer associated with an unavailability period due to satellite access non-contiguous coverage is running after expiration of the stored timer associated with the unavailability period not depending on NR satellite access non-contiguous coverage. Note that the PLMN selection procedure may be to select different PLMN / access technology combinations for which the UE attempts to register. For example, the UE may select a PLMN / access technology combination from a list of PLMN IDs and access technologies (PLMN ID and access technology list) stored by the UE, taking into account the PLMN and / or access technology. Here, the access technology may be read as radio access technology, radio access, or access network. Further, the access technology may include wireless access via TN or wireless access via NTN.

[0300] [5.4. Fourth embodiment] A fourth embodiment of the present invention will be described. In this section, the fourth embodiment is also referred to as the present embodiment. This embodiment relates to a timer process based on a discontinuous coverage maximum NAS signaling latency. This embodiment may also be a behavior performed by the UE and / or NW in each of the first to third embodiments.

[0301] This embodiment may be the case where the UE and / or NW supports both an availability period due to NR satellite access non-contiguous coverage and an availability period not due to NR satellite access non-contiguous coverage.

[0302] Furthermore, the UE and / or the NW may receive and store both the unavailability period not depending on the NR satellite access discontinuous coverage and the unavailability period duration depending on the NR satellite access discontinuous coverage in the registration procedure and / or the UE configuration update procedure. Here, the unavailability period not depending on the NR satellite access discontinuous coverage may be stored in association with a type not depending on the NR satellite access discontinuous coverage indicated by the third identification information transmitted and received together with the unavailability period.

[0303] In the UE of this embodiment, when an availability period due to NR satellite access discontinuous coverage ends during the execution of an availability period not due to NR satellite access discontinuous coverage that starts at any timing, the UE may determine, set, and execute a timer value based on the discontinuous coverage maximum NAS signaling waiting time, or may not execute these.

[0304] More specifically, for example, when both the UE and the NW support at least an unavailability period due to NR satellite access discontinuous coverage and when the UE receives third identification information indicating the type of the unavailability period due to NR satellite access discontinuous coverage and the unavailability period duration from the network, the UE may determine, store, or set a timer value based on the discontinuous coverage maximum NAS signaling waiting time at the timing of receiving the timer based on the discontinuous coverage maximum NAS signaling waiting time.

[0305] Or, for example, the UE may determine, store, or set a timer value based on the discontinuous coverage maximum NAS signaling latency after receiving the timer based on the discontinuous coverage maximum NAS signaling latency after the availability period ends when the UE and the NW support at least an unavailability period due to NR satellite access discontinuous coverage and when the UE has received third identification information indicating a type of the unavailability period due to NR satellite access discontinuous coverage and an unavailability period duration from the network.

[0306] Or, for example, if the UE and the NW support at least an unavailability period due to NR satellite access discontinuous coverage and have not received third identification information indicating a type of unavailability period due to NR satellite access discontinuous coverage and an unavailability period duration from the network, after receiving the timer based on the discontinuous coverage maximum NAS signaling latency, the UE may not determine, and / or store, and / or set, and / or start a timer value based on the discontinuous coverage maximum NAS signaling latency. [6. Modifications] A program that operates on an apparatus according to an aspect of the present invention may be a program that controls a Central Processing Unit (CPU) or the like to cause a computer to function so as to realize the functions of an embodiment according to an aspect of the present invention. The program or information handled by the program is temporarily stored in a volatile memory such as a Random Access Memory (RAM), a non-volatile memory such as a flash memory, a Hard Disk Drive (HDD), or other storage device system.

[0307] A program for implementing the functions of the embodiment according to one aspect of the present invention may be recorded on a computer-readable recording medium. The program may be implemented by loading the program recorded on the recording medium into a computer system and executing it. The term "computer system" as used herein refers to a computer system built into an apparatus, and includes hardware such as an operating system and peripheral devices. The term "computer-readable recording medium" may be a semiconductor recording medium, an optical recording medium, a magnetic recording medium, a medium that dynamically holds a program for a short period of time, or any other recording medium that can be read by a computer.

[0308] In addition, each functional block or feature of the device used in the above-mentioned embodiment may be implemented or performed by an electric circuit, for example, an integrated circuit or a plurality of integrated circuits. The electric circuit designed to perform the functions described herein may include a general-purpose processor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a field programmable gate array (FPGA), or other programmable logic device, discrete gate or transistor logic, discrete hardware components, or a combination thereof. The general-purpose processor may be a microprocessor, or a conventional processor, controller, microcontroller, or state machine. The electric circuit described above may be composed of a digital circuit or an analog circuit. In addition, when a technology for integrated circuitization that replaces current integrated circuits appears due to the progress of semiconductor technology, one or more aspects of the present invention may use a new integrated circuit based on that technology.

[0309] The present invention is not limited to the above-mentioned embodiment. In the embodiment, one example of the device is described, but the present invention is not limited to this and can be applied to stationary or non-movable electronic devices installed indoors or outdoors, such as terminal devices or communication devices of AV equipment, kitchen equipment, cleaning / washing equipment, air conditioners, office equipment, vending machines, and other household appliances.

[0310] Although the embodiments of the present invention have been described above in detail with reference to the drawings, the specific configuration is not limited to this embodiment, and design changes and the like within the scope of the gist of the present invention are also included. Furthermore, the present invention can be modified in various ways within the scope of the claims, and embodiments obtained by appropriately combining the technical means disclosed in different embodiments are also included in the technical scope of the present invention. Furthermore, configurations in which elements described in the above embodiments are replaced with elements that have the same effect are also included. [Explanation of symbols]

[0311] 1 Mobile communication systems 10 UE_A 30 PGW-U 32 PGW-C 35 SGW 40 MME 45 eNB 50 HSS 60 PCRF 80 Access Network_A (E-UTRAN) 90 Core Network_A 120 Access Network_B (5G AN) 122 gNB 130 UPF 132 SMF 140 AMF 150 UDM 160 PCF 190 Core Network_B 235 UPF_A 239 UPF_C

Claims

1. A UE (User Equipment) including a transceiver unit, a control unit, and a storage unit, The transceiver receives a first timer value, a first type, and / or a maximum waiting time from a network (NW); the first timer value is a timer value indicating a duration of an Unavailability Period; The first type is a type indicating that the Unavailability Period does not depend on discontinuous coverage provided by NR (New Radio) satellite access, The control unit stores the first timer value and the first type in association with each other in the storage unit; The control unit does not set and / or start a second timer after expiration of a timer based on the first timer value associated with the first type stored in the storage unit; The second timer is a timer having a timer value that is a period determined by the UE based on the maximum waiting time. The UE is characterized by:

2. When the timer based on the second timer value expires, if an unavailability period due to discontinuous coverage provided by the NR satellite access has expired, The control unit does not determine and / or set a timer value of the second timer and does not start the second timer. The UE according to claim 1,

3. A UE (User Equipment) including a transceiver unit, a control unit, and a storage unit, the storage unit stores a first timer and a second timer; The first timer is a timer having an availability period associated with a type indicating that the availability period is not based on discontinuous coverage provided by NR (New Radio) satellite access as a timer value, The second timer is a timer having a timer value corresponding to an unavailability period associated with a type indicating that the unavailability period is due to discontinuous coverage provided by the NR satellite access, The transceiver receives first control information from a network; the first control information is information indicating the first or second timer value and / or a type, The control unit executes a timer based on the first control information. The UE is characterized by:

4. A UE (User Equipment) including a transceiver unit, a control unit, and a storage unit, the storage unit stores a first timer value and a first type in association with each other; the first timer value is a timer value indicating a duration of an Unavailability Period; The first type is a type indicating that the Unavailability Period does not depend on discontinuous coverage provided by NR (New Radio) satellite access, The storage unit further stores a waiting time, the waiting time is a value determined by the control unit based on a maximum waiting time received by the transceiver unit from a network, The control unit executes a PLMN (Public Land Mobile Network) selection procedure when a timer based on an Unavailability Period due to discontinuous coverage provided by the NR satellite access is running at the time when the timer based on the first timer value expires. The UE is characterized by:

Images