Voice call using satellite

The method enhances EPS/5GS system by enabling simultaneous Control Plane and User Plane usage for NB-IoT UE in IDLE state, reducing call setup time and improving QoS for voice calls via satellite.

WO2026235247A1PCT designated stage Publication Date: 2026-11-12LG ELECTRONICS INC
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
PCT/KR2025/022006
Authority / Receiving Office
WO · WO
Patent Type
Applications
Current Assignee / Owner
Priority Date
2025-05-09
Filing Date
2025-12-17
Publication Date
2026-11-12

AI Technical Summary

Technical Problem

Existing voice call setups via NB-IoT in GEO Satellite face challenges in minimizing call setup time due to the requirement for a Service Request and the inability to utilize both Control Plane and User Plane paths simultaneously, leading to inefficiencies in Quality of Service (QoS) for voice services.

Method used

A method is introduced to enhance the EPS/5GS system by allowing an NB-IoT UE in an IDLE state to send an INVITE message and activate the User Plane simultaneously, creating a dedicated bearer/QoS flow in advance, thereby reducing the call setup time.

Benefits of technology

This approach enables efficient voice call setup via satellite by reducing the terminal's call setup time and creating a dedicated bearer/QoS flow in advance, allowing the UE to send an INVITE message without waiting for a Service Accept response, thus enhancing QoS for voice services.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure KR2025022006_12112026_PF_FP_ABST
    Figure KR2025022006_12112026_PF_FP_ABST
Patent Text Reader

Abstract

The present disclosure provides a method and a device related to a voice call using a satellite. A UE sets a connection for an IMS voice service with a network node. The UE in a CM-Idle state transmits, to the network node, a first message including (i) information related to user data and (ii) information related to user plane activation.
Need to check novelty before this filing date? Find Prior Art

Description

Voice call via satellite

[0001] This specification relates to voice calls via satellite.

[0002] 3GPP (3rd Generation Partnership Project) LTE (Long-Term Evolution) is a technology designed to enable high-speed packet communication. Many methods have been proposed to achieve LTE goals, such as reducing costs for users and operators, improving service quality, expanding coverage, and increasing system capacity. As high-level requirements, 3GPP LTE demands reduced cost per bit, improved service availability, flexible use of frequency bands, a simple structure, open interfaces, and appropriate power consumption of terminals.

[0003] Work has begun at the ITU (International Telecommunication Union) and 3GPP to develop requirements and specifications for New Radio (NR) systems. 3GPP must identify and develop the technical components necessary to successfully standardize NR in a timely manner, satisfying both urgent market demands and the longer-term requirements presented by the ITU-R (ITU Radio communication sector) IMT (International Mobile Telecommunications)-2020 process. Furthermore, NR must be able to utilize any spectrum band up to at least 100 GHz so that it can be used for wireless communication even in the distant future.

[0004] NR targets a single technical framework that covers all deployment, usage, and requirements, including eMBB (enhanced Mobile Broadband), mMTC (massive Machine Type-Communications), and URLLC (Ultra-Reliable and Low Latency Communications). NR must be forward compatible by nature.

[0005] Regarding the limitations of voice calls to NB-IoT via GEO Satellite, minimizing Call Setup Time is an important factor in user experience.

[0006] For a UE in an IDLE state, a Service Request is required to access the network. To attempt a voice call, a UE in an IDLE state must request a Service Request from the network and, only after receiving a Service Accept Message in response, can it send an IMS INVITE message for the voice call.

[0007] Terminals operating with Control Plane CIoT EPS Optimization can use Control Plane Service Requests. Using a Control Plane Service Request offers the advantage of rapidly transmitting data before receiving a Service Accept message from the terminal, as it allows an INVITE message to be embedded within the request and sent to the counterparty over the network in advance.

[0008] However, it is difficult to satisfy the QoS for voice services using only the Control Plane, and a GBR dedicated bearer (GBR QoS Flow) is required to satisfy the QoS for voice services. To satisfy this, it is also necessary to allow the creation of a GBR dedicated bearer (GBR QoS Flow) for NB-IoT terminals.

[0009] Under the current specification, data is transmitted using only one path—either the Control Plane or the User Plane—within a single PDN, and both paths cannot be used simultaneously.

[0010] Therefore, in order to reduce the terminal's Call Setup Time in NB-IoT access via GEO Satellite, a method to enhance the existing EPS / 5GS is required.

[0011] In one embodiment, a method for voice calls via satellite is provided.

[0012] For example, the method includes: establishing a connection for an IMS (IP Multimedia Subsystem) voice service with a network node by a user device (UE); and transmitting a first message to the network node by the UE in a CM-Idle state, the message including (i) information related to user data and (ii) information related to user plane activation.

[0013] For example, the method comprises: establishing a connection for an IMS voice service with a user device (UE) by a network node; receiving a first message by the network node from the UE in a CM-IDLE state, the message including (i) information related to user data and (ii) information related to user plane activation; and activating the user plane by the network node.

[0014] In another aspect, a device for implementing the above method is provided.

[0015] The present disclosure may have various effects.

[0016] According to some embodiments of the present disclosure, voice calls via satellite can be efficiently set up.

[0017] According to some embodiments of the present disclosure, when an NB-IOT UE in a CM-IDLE state provides voice service via a GEO Satellite, an invite message and an UP activation indicator can be sent as a single message. Thus, the call setup time can be reduced. Additionally, a dedicated bearer / QoS flow can be created in advance at the network level to shorten the time required to create the bearer / QoS flow during call setup.

[0018] For example, when an NB-IOT UE in the (E)CM-IDLE state provides voice services via a GEO Satellite, the NB-IOT UE can send a Service Request to the network to send an INVITE message and can avoid waiting for the time it takes to receive Service Accept from the network and enter CONNECTED mode. The NB-IOT UE can reduce the terminal's Call Setup Time by sending a Control Plane Service Request containing the INVITE message to the network and creating a User Plane for voice during the time it takes to receive a response from the other party. Additionally, by pre-creating a dedicated bearer / QoS flow at the network level, the time required to create the corresponding bearer / QoS flow during Call Setup can be reduced.

[0019] According to some embodiments of the present disclosure, a wireless communication system can efficiently initiate an IMS Voice Call via an NB-IoT GEO satellite when the UE is in an IDLE state.

[0020] The effects obtainable through the specific examples of this specification are not limited to those listed above. For example, there may be various technical effects that a person with ordinary skill in the related art can understand or derive from this specification. Accordingly, the specific effects of this specification are not limited to those explicitly described herein, but may include various effects that can be understood or derived from the technical features of this specification.

[0021] FIG. 1 shows an example of a communication system to which the implementation of the present specification is applied.

[0022] FIG. 2 shows an example of a wireless device to which the implementation of the present specification applies.

[0023] FIG. 3 shows an example of a UE to which the implementation of the present specification applies.

[0024] FIG. 4 shows an example of a 5G system structure to which the implementation of the present specification is applied.

[0025] FIGS. 5 and FIGS. 6 illustrate examples of registration procedures to which the implementation of the present specification applies.

[0026] Figure 7 shows an example of an NTN structure.

[0027] Figures 8a and 8b show an example of the MO data transmission process of the control plane CIoT EPS / 5GS optimization.

[0028] Figures 9a and 9b show an example of the MO data transmission process of the control plane CIoT EPS / 5GS optimization.

[0029] Figure 10 shows an example of an S1-U bearer setup during data transmission in control plane CIoT EPS optimization.

[0030] Figures 11a and 11b show an example of a procedure for a VoLTE service.

[0031] Figure 12 shows an example of a method for a voice call via satellite.

[0032] Figure 13 shows an example of a method for a voice call via satellite.

[0033] Figures 14a and 14b show examples of high-level procedures for IMS voice via NB-IoT (GEO).

[0034] Figures 15a and 15b show examples of IMS voice call procedures via NB-IoT (GEO) in 5GS.

[0035] The following techniques, devices, and systems may be applied to various wireless multiple access systems. Examples of multiple access systems include Code Division Multiple Access (CDMA) systems, Frequency Division Multiple Access (FDMA) systems, Time Division Multiple Access (TDMA) systems, Orthogonal Frequency Division Multiple Access (OFDMA) systems, Single Carrier Frequency Division Multiple Access (SC-FDMA) systems, and Multi-Carrier Frequency Division Multiple Access (MC-FDMA) systems. CDMA may be implemented through wireless technologies such as Universal Terrestrial Radio Access (UTRA) or CDMA2000. TDMA may be implemented through wireless technologies such as Global System for Mobile Communications (GSM), General Packet Radio Service (GPRS), or Enhanced Data Rates for GSM Evolution (EDGE). OFDMA can be implemented through wireless technologies such as IEEE (Institute of Electrical and Electronics Engineers) 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE 802.20, or E-UTRA (Evolved UTRA). UTRA is part of UMTS (Universal Mobile Telecommunications System). 3GPP (3rd Generation Partnership Project) LTE (Long-Term Evolution) is part of E-UMTS (Evolved UMTS) using E-UTRA.3GPP LTE uses OFDMA in the downlink (DL) and SC-FDMA in the uplink (UL). Evolutions of 3GPP LTE include LTE-A (Advanced), LTE-A Pro, and / or 5G NR (New Radio).

[0036] For convenience of explanation, the implementation of this specification is described primarily in relation to 3GPP-based wireless communication systems. However, the technical characteristics of this specification are not limited thereto. For example, the following detailed description is provided based on a mobile communication system corresponding to a 3GPP-based wireless communication system, but aspects of this specification that are not limited to 3GPP-based wireless communication systems may be applied to other mobile communication systems.

[0037] For terms and technologies used in this specification that are not specifically described, reference may be made to wireless communication standard documents published prior to this specification.

[0038] In this specification, "A or B" may mean "only A," "only B," or "both A and B." Alternatively, in this specification, "A or B" may be interpreted as "A and / or B." For example, in this specification, "A, B or C" may mean "only A," "only B," "only C," or "any combination of A, B and C."

[0039] A slash ( / ) or a comma used in this specification may mean "and / or." For example, "A / B" may mean "A and / or B." Accordingly, "A / B" may mean "only A," "only B," or "both A and B." For example, "A, B, C" may mean "A, B or C."

[0040] In this specification, "at least one of A and B" may mean "only A," "only B," or "both A and B." Additionally, in this specification, the expressions "at least one of A or B" or "at least one of A and / or B" may be interpreted as synonymous with "at least one of A and B."

[0041] Additionally, in this specification, "at least one of A, B and C" may mean "only A," "only B," "only C," or "any combination of A, B and C." Furthermore, "at least one of A, B or C" or "at least one of A, B and / or C" may mean "at least one of A, B and C."

[0042] Additionally, parentheses used in this specification may mean "for example." Specifically, when indicated as "control information (PDCCH)," "PDCCH" may be proposed as an example of "control information." In other words, "control information" in this specification is not limited to "PDCCH," and "PDCCH" may be proposed as an example of "control information." Furthermore, even when indicated as "control information (i.e., PDCCH)," "PDCCH" may be proposed as an example of "control information."

[0043] Technical features described individually within a single drawing in this specification may be implemented individually or simultaneously.

[0044] Although not limited thereto, the various descriptions, functions, procedures, proposals, methods, and / or operation flowcharts disclosed in this specification may be applied to various fields where wireless communication and / or connectivity between devices (e.g., 5G) is required.

[0045] The present specification will be described in more detail below with reference to the drawings. In the following drawings and / or description, the same reference numerals may refer to the same or corresponding hardware blocks, software blocks, and / or function blocks unless otherwise indicated.

[0046] FIG. 1 shows an example of a communication system to which the implementation of the present specification is applied.

[0047] The 5G usage scenario shown in FIG. 1 is merely an example, and the technical features of this specification may be applied to other 5G usage scenarios not shown in FIG. 1.

[0048] The three main requirement categories for 5G are (1) enhanced Mobile BroadBand (eMBB) category, (2) massive Machine Type Communication (mMTC) category, and (3) Ultra-Reliable and Low Latency Communications (URLLC) category.

[0049] Referring to FIG. 1, the communication system (1) includes wireless devices (100a to 100f), a base station (BS; 200), and a network (300). FIG. 1 illustrates a 5G network as an example of the network of the communication system (1), but the implementation of the present specification is not limited to a 5G system and may be applied to future communication systems beyond a 5G system.

[0050] The base station (200) and the network (300) can be implemented as wireless devices, and a specific wireless device can operate as a base station / network node in relation to another wireless device.

[0051] Wireless devices (100a to 100f) represent devices that perform communication using Radio Access Technology (RAT) (e.g., 5G NR or LTE) and may also be referred to as communication / wireless / 5G devices. Wireless devices (100a to 100f) may include, but are not limited to, robots (100a), vehicles (100b-1 and 100b-2), eXtended Reality (XR) devices (100c), portable devices (100d), home appliances (100e), Internet-Of-Things (IoT) devices (100f), and Artificial Intelligence (AI) devices / servers (400). For example, vehicles may include vehicles with wireless communication capabilities, autonomous vehicles, and vehicles capable of performing communication between vehicles. Vehicles may include unmanned aerial vehicles (UAVs) (e.g., drones). XR devices may include AR (Augmented Reality) / VR (Virtual Reality) / MR (Mixed Reality) devices and may be implemented in the form of HMDs (Head-Mounted Devices) and HUDs (Head-Up Displays) mounted on vehicles, televisions, smartphones, computers, wearable devices, home appliances, digital signs, vehicles, robots, etc. Portable devices may include smartphones, smart pads, wearable devices (e.g., smartwatches or smart glasses), and computers (e.g., laptops). Home appliances may include TVs, refrigerators, and washing machines. IoT devices may include sensors and smart meters.

[0052] In this specification, wireless devices (100a to 100f) may be referred to as User Equipment (UE). The UE may include, for example, a mobile phone, a smartphone, a laptop computer, a digital broadcasting terminal, a PDA (Personal Digital Assistant), a PMP (Portable Multimedia Player), a navigation system, a slate PC, a tablet PC, an ultrabook, a vehicle, a vehicle with autonomous driving capabilities, a connected car, a UAV, an AI module, a robot, an AR device, a VR device, an MR device, a hologram device, a public safety device, an MTC device, an IoT device, a medical device, a fintech device (or financial device), a security device, a weather / environment device, a 5G service-related device, or a device related to the Fourth Industrial Revolution.

[0053] Wireless devices (100a to 100f) can be connected to a network (300) through a base station (200). AI technology may be applied to the wireless devices (100a to 100f), and the wireless devices (100a to 100f) can be connected to an AI server (400) through the network (300). The network (300) can be configured using a 3G network, a 4G (e.g., LTE) network, a 5G (e.g., NR) network, and a network after 5G. The wireless devices (100a to 100f) may communicate with each other through the base station (200) / network (300), but they may also communicate directly (e.g., sidelink communication) without going through the base station (200) / network (300). For example, vehicles (100b-1, 100b-2) can communicate directly (e.g., V2V (Vehicle-to-Vehicle) / V2X (Vehicle-to-everything) communication). Also, IoT devices (e.g., sensors) can communicate directly with other IoT devices (e.g., sensors) or other wireless devices (100a to 100f).

[0054] Wireless communication / connections (150a, 150b, 150c) can be established between wireless devices (100a to 100f) and / or between wireless devices (100a to 100f) and base station (200) and / or between base station (200). Here, the wireless communication / connections can be established through various RATs (e.g., 5G NR), such as uplink / downlink communication (150a), sidelink communication (150b) (or D2D (Device-To-Device) communication), and communication between base stations (150c) (e.g., relay, IAB (Integrated Access and Backhaul)). Through the wireless communication / connections (150a, 150b, 150c), wireless devices (100a to 100f) and base station (200) can transmit / receive wireless signals to / from each other. For example, wireless communication / connection (150a, 150b, 150c) can transmit / receive signals through various physical channels. To this end, based on various proposals of the present specification, at least some of the following may be performed: a process for setting various configuration information for transmitting / receiving wireless signals, a process for various signal processing (e.g., channel encoding / decoding, modulation / demodulation, resource mapping / demapping, etc.), and a resource allocation process.

[0055] NR supports multiple numerologies or subcarrier spacings (SCS) to support various 5G services. For example, when the SCS is 15 kHz, it supports a wide area in traditional cellular bands; when the SCS is 30 kHz / 60 kHz, it supports dense-urban areas, lower latency, and wider carrier bandwidth; and when the SCS is 60 kHz or higher, it supports a bandwidth greater than 24.25 GHz to overcome phase noise.

[0056] The NR frequency band can be defined by two types of frequency ranges (FR1, FR2). The numerical values ​​of the frequency ranges may change. For example, the two types of frequency ranges (FR1, FR2) may be as shown in Table 1 below. For convenience of explanation, among the frequency ranges used in the NR system, FR1 may mean "sub 6GHz range" and FR2 may mean "above 6GHz range" and may be referred to as Millimeter Wave (mmW).

[0057] Frequency Range Definition Frequency Range Subcarrier Spacing FR1 450 MHz - 6000 MHz 15, 30, 60 kHz FR2 24 250 MHz - 52600 MHz 60, 120, 240 kHz

[0058] As described above, the numerical value of the frequency range of the NR system may change. For example, FR1 may include a band of 410 MHz to 7125 MHz as shown in Table 2 below. That is, FR1 may include a frequency band of 6 GHz (or 5850, 5900, 5925 MHz, etc.) or higher. For example, the frequency band of 6 GHz (or 5850, 5900, 5925 MHz, etc.) or higher included within FR1 may include an unlicensed band. The unlicensed band may be used for various purposes, for example, for communication for vehicles (e.g., autonomous driving).

[0059] Frequency Range Definition Frequency Range Subcarrier Spacing FR1 4 10 MHz - 7 125 MHz 15, 30, 60 kHz FR2 24 250 MHz - 5 2600 MHz 60, 120, 240 kHz

[0060] Here, the wireless communication technology implemented in the wireless device of this specification may include LTE, NR, and 6G, as well as NarrowBand IoT (NB-IoT) for low-power communication. For example, NB-IoT technology may be an example of Low Power Wide Area Network (LPWAN) technology and may be implemented according to standards such as LTE Cat NB1 and / or LTE Cat NB2, but is not limited to the names mentioned above. Additionally, or generally, the wireless communication technology implemented in the wireless device of this specification may perform communication based on LTE-M technology. For example, LTE-M technology may be an example of LPWAN technology and may be referred to by various names such as eMTC (enhanced MTC). For example, LTE-M technology may be implemented in at least one of various standards such as 1) LTE CAT 0, 2) LTE Cat M1, 3) LTE Cat M2, 4) LTE non-BL (Non-Bandwidth Limited), 5) LTE-MTC, 6) LTE MTC, and / or 7) LTE M, and is not limited to the names mentioned above. Additionally or generally, wireless communication technology implemented in the wireless device of this specification may include at least one of ZigBee, Bluetooth, and / or LPWAN with consideration for low-power communication, and is not limited to the names mentioned above. For example, ZigBee technology may create Personal Area Networks (PANs) related to small / low-power digital communication based on various standards such as IEEE 802.15.4, and may be referred to by various names.

[0061] FIG. 2 shows an example of a wireless device to which the implementation of the present specification applies.

[0062] In FIG. 2, the first wireless device (100) and / or the second wireless device (200) may be implemented in various forms depending on the use example / service. For example, {the first wireless device (100) and the second wireless device (200)} may correspond to at least one of {wireless devices (100a–100f) and base station (200)}, {wireless devices (100a–100f) and wireless devices (100a–100f)} and / or {base station (200) and base station (200)} of FIG. 1. The first wireless device (100) and / or the second wireless device (200) may be composed of various components, devices / parts and / or modules.

[0063] The first wireless device (100) may include at least one transceiver such as a transceiver (106), at least one processing chip such as a processing chip (101), and / or one or more antennas (108).

[0064] The processing chip (101) may include at least one processor, such as a processor (102), and at least one memory, such as a memory (104). Additionally and / or generally, the memory (104) may be placed outside the processing chip (101).

[0065] The processor (102) can control the memory (104) and / or the transceiver (106) and may be configured to implement the descriptions, functions, procedures, proposals, methods, and / or operation flowcharts disclosed herein. For example, the processor (102) may process information within the memory (104) to generate a first information / signal and transmit a wireless signal containing the first information / signal through the transceiver (106). The processor (102) may receive a wireless signal containing a second information / signal through the transceiver (106) and process the second information / signal to store the obtained information in the memory (104).

[0066] Memory (104) may be connected to the processor (102) so as to be operable. Memory (104) may store various types of information and / or instructions. Memory (104) may store firmware and / or software code (105) that implements code, instructions, and / or a set of instructions that perform the descriptions, functions, procedures, proposals, methods, and / or operation flowcharts disclosed in this specification when executed by the processor (102). For example, firmware and / or software code (105) may implement instructions that perform the descriptions, functions, procedures, proposals, methods, and / or operation flowcharts disclosed in this specification when executed by the processor (102). For example, firmware and / or software code (105) may control the processor (102) to perform one or more protocols. For example, firmware and / or software code (105) may control the processor (102) to perform one or more wireless interface protocol layers.

[0067] Here, the processor (102) and memory (104) may be part of a communication modem / circuit / chip designed to implement RAT (e.g., LTE or NR). A transceiver (106) may be connected to the processor (102) and may transmit and / or receive a wireless signal through one or more antennas (108). Each transceiver (106) may include a transmitter and / or receiver. The transceiver (106) may be interchangeably used with an RF (Radio Frequency) unit. In this specification, the first wireless device (100) may represent a communication modem / circuit / chip.

[0068] The second wireless device (200) may include at least one transceiver such as a transceiver (206), at least one processing chip such as a processing chip (201), and / or one or more antennas (208).

[0069] The processing chip (201) may include at least one processor, such as a processor (202), and at least one memory, such as a memory (204). Additionally and / or alternatively, the memory (204) may be placed outside the processing chip (201).

[0070] The processor (202) can control the memory (204) and / or the transceiver (206) and may be configured to implement the descriptions, functions, procedures, proposals, methods, and / or operation flowcharts disclosed herein. For example, the processor (202) may process information within the memory (204) to generate a third information / signal and transmit a wireless signal containing the third information / signal through the transceiver (206). The processor (202) may receive a wireless signal containing a fourth information / signal through the transceiver (206) and process the fourth information / signal to store the obtained information in the memory (204).

[0071] Memory (204) may be connected to the processor (202) so as to be operable. Memory (204) may store various types of information and / or instructions. Memory (204) may store firmware and / or software code (205) that implements code, instructions, and / or sets of instructions that perform descriptions, functions, procedures, proposals, methods, and / or flowcharts disclosed in this specification when executed by the processor (202). For example, firmware and / or software code (205) may implement instructions that perform descriptions, functions, procedures, proposals, methods, and / or flowcharts disclosed in this specification when executed by the processor (202). For example, firmware and / or software code (205) may control the processor (202) to perform one or more protocols. For example, firmware and / or software code (205) may control the processor (202) to perform one or more wireless interface protocol layers.

[0072] Here, the processor (202) and memory (204) may be part of a communication modem / circuit / chip designed to implement a RAT (e.g., LTE or NR). A transceiver (206) may be connected to the processor (202) and transmit and / or receive a wireless signal through one or more antennas (208). Each transceiver (206) may include a transmitter and / or receiver. The transceiver (206) may be interchangeably used with an RF unit. In this specification, the second wireless device (200) may represent a communication modem / circuit / chip.

[0073] Hereinafter, hardware elements of the wireless device (100, 200) will be described in more detail. Although not limited thereto, one or more protocol layers may be implemented by one or more processors (102, 202). For example, one or more processors (102, 202) may implement one or more layers (e.g., functional layers such as a PHY (physical) layer, a MAC (Media Access Control) layer, an RLC (Radio Link Control) layer, a PDCP (Packet Data Convergence Protocol) layer, an RRC (Radio Resource Control) layer, and an SDAP (Service Data Adaptation Protocol) layer). One or more processors (102, 202) may generate one or more PDUs (Protocol Data Units), one or more SDUs (Service Data Units), messages, control information, data, or information according to the descriptions, functions, procedures, proposals, methods, and / or operation flowcharts disclosed in this specification. One or more processors (102, 202) may generate a signal (e.g., baseband signal) including a PDU, SDU, message, control information, data, or information according to the description, function, procedure, proposal, method, and / or operation flowchart disclosed in this specification and provide it to one or more transceivers (106, 206). One or more processors (102, 202) may receive a signal (e.g., baseband signal) from one or more transceivers (106, 206) and may obtain a PDU, SDU, message, control information, data, or information according to the description, function, procedure, proposal, method, and / or operation flowchart disclosed in this specification.

[0074] One or more processors (102, 202) may be referred to as a controller, a microcontroller, a microprocessor, and / or a microcomputer. One or more processors (102, 202) may be implemented by hardware, firmware, software, and / or a combination thereof. For example, one or more Application Specific Integrated Circuits (ASICs), one or more Digital Signal Processors (DSPs), one or more Digital Signal Processing Devices (DSPDs), one or more Programmable Logic Devices (PLDs), and / or one or more Field Programmable Gate Arrays (FPGAs) may be included in one or more processors (102, 202). For example, one or more processors (102, 202) may be composed of a set of communication control processors, application processors (APs), electronic control units (ECUs), central processing units (CPUs), graphic processing units (GPUs), and memory control processors. One or more memories (104, 204) may be connected to one or more processors (102, 202) and may store various forms of data, signals, messages, information, programs, codes, instructions, and / or commands. One or more memories (104, 204) may be composed of Random Access Memory (RAM), Dynamic RAM (DRAM), Read-Only Memory (ROM), Erasable Programmable ROM (EPROM), flash memory, volatile memory, non-volatile memory, hard drive, register, cache memory, computer read storage media, and / or combinations thereof.One or more memories (104, 204) may be located inside and / or outside of one or more processors (102, 202). Additionally, one or more memories (104, 204) may be connected to one or more processors (102, 202) through various technologies such as wired or wireless connections.

[0075] One or more transceivers (106, 206) may transmit user data, control information, wireless signals / channels, etc., as described in the descriptions, functions, procedures, proposals, methods, and / or operation flowcharts disclosed in this specification to one or more other devices. One or more transceivers (106, 206) may receive user data, control information, wireless signals / channels, etc., as described in the descriptions, functions, procedures, proposals, methods, and / or operation flowcharts disclosed in this specification from one or more other devices. For example, one or more transceivers (106, 206) may be connected to one or more processors (102, 202) and may transmit and receive wireless signals. For example, one or more processors (102, 202) may control one or more transceivers (106, 206) to transmit user data, control information, wireless signals, etc., to one or more other devices. Additionally, one or more processors (102, 202) can control one or more transceivers (106, 206) to receive user data, control information, wireless signals, etc. from one or more other devices.

[0076] One or more transceivers (106, 206) may be connected to one or more antennas (108, 208). Additionally and / or generally, one or more transceivers (106, 206) may include one or more antennas (108, 208). One or more transceivers (106, 206) may be configured to transmit and receive user data, control information, wireless signals / channels, etc., mentioned in the descriptions, functions, procedures, proposals, methods, and / or operation flowcharts disclosed herein through one or more antennas (108, 208). In this specification, one or more antennas (108, 208) may be a plurality of physical antennas or a plurality of logical antennas (e.g., antenna ports).

[0077] One or more transceivers (106, 206) can convert received user data, control information, wireless signals / channels, etc. from RF band signals to baseband signals in order to process received user data, control information, wireless signals / channels, etc. using one or more processors (102, 202). One or more transceivers (106, 206) can convert processed user data, control information, wireless signals / channels, etc. from baseband signals to RF band signals using one or more processors (102, 202). To this end, one or more transceivers (106, 206) may include (analog) oscillators and / or filters. For example, one or more transceivers (106, 206) can up-convert an OFDM baseband signal into an OFDM signal through an (analog) oscillator and / or filter under the control of one or more processors (102, 202) and transmit the up-converted OFDM signal at a carrier frequency. One or more transceivers (106, 206) can receive an OFDM signal at a carrier frequency and down-convert the OFDM signal into an OFDM baseband signal through an (analog) oscillator and / or filter under the control of one or more processors (102, 202).

[0078] Although not illustrated in FIG. 2, the wireless device (100, 200) may include additional components. The additional components (140) may be configured in various ways depending on the type of the wireless device (100, 200). For example, the additional components (140) may include at least one of a power unit / battery, an input / output (I / O) device (e.g., audio I / O port, video I / O port), a driving unit, and a computing unit. The additional components (140) may be connected to one or more processors (102, 202) through various technologies, such as wired or wireless connections.

[0079] In an implementation of the present specification, the UE may operate as a transmitting device in the uplink and as a receiving device in the downlink. In an implementation of the present specification, the base station may operate as a receiving device in the UL and as a transmitting device in the DL. For technical convenience, it is generally assumed that the first wireless device (100) operates as a UE and the second wireless device (200) operates as a base station. For example, a processor (102) connected to, mounted on, or released to the first wireless device (100) may be configured to perform UE operations according to an implementation of the present specification or to control a transceiver (106) to perform UE operations according to an implementation of the present specification. A processor (202) connected to, mounted on, or released to the second wireless device (200) may be configured to perform base station operations according to an implementation of the present specification or to control a transceiver (206) to perform base station operations according to an implementation of the present specification.

[0080] In this specification, the base station may be referred to as Node B, eNode B, or gNB.

[0081] FIG. 3 shows an example of a UE to which the implementation of the present specification applies.

[0082] Referring to FIG. 3, the UE (100) can correspond to the first wireless device (100) of FIG. 2.

[0083] The UE (100) includes a processor (102), memory (104), transceiver (106), one or more antennas (108), a power management module (141), a battery (142), a display (143), a keypad (144), a SIM (Subscriber Identification Module) card (145), a speaker (146), and a microphone (147).

[0084] The processor (102) may be configured to implement the descriptions, functions, procedures, proposals, methods, and / or operation flowcharts disclosed herein. The processor (102) may be configured to control one or more other components of the UE (100) to implement the descriptions, functions, procedures, proposals, methods, and / or operation flowcharts disclosed herein. Layers of a wireless interface protocol may be implemented in the processor (102). The processor (102) may include an ASIC, other chipsets, logic circuits, and / or data processing devices. The processor (102) may be an application processor. The processor (102) may include at least one of a DSP, a CPU (Central Processing Unit), a GPU (Graphics Processing Unit), and a modem (modulator and demodulator). An example of the processor (102) is the SNAPDRAGON manufactured by Qualcomm®. TM Series processor, EXYNOS made by Samsung® TM Series processors, A Series processors made by Apple®, HELIO made by MediaTek® TM Series processors, ATOM made by Intel® TM It can be found in series processors or corresponding next-generation processors.

[0085] Memory (104) is coupled to the processor (102) so as to be operable and stores various information for operating the processor (102). Memory (104) may include ROM, RAM, flash memory, memory card, storage medium and / or other storage device. When the implementation is implemented in software, the technology described herein may be implemented using modules (e.g., procedures, functions, etc.) that perform the descriptions, functions, procedures, proposals, methods and / or operation flowcharts disclosed herein. Modules may be stored in memory (104) and executed by the processor (102). Memory (104) may be implemented within the processor (102) or outside the processor (102), in which case it may be communicatively coupled to the processor (102) through various methods known in the technology.

[0086] A transceiver (106) is coupled to operate with a processor (102) and transmits and / or receives a wireless signal. The transceiver (106) includes a transmitter and a receiver. The transceiver (106) may include a baseband circuit for processing a wireless frequency signal. The transceiver (106) controls one or more antennas (108) to transmit and / or receive a wireless signal.

[0087] The power management module (141) manages the power of the processor (102) and / or the transceiver (106). The battery (142) supplies power to the power management module (141).

[0088] The display (143) outputs the result processed by the processor (102). The keypad (144) receives input to be used by the processor (102). The keypad (144) can be displayed on the display (143).

[0089] A SIM card (145) is an integrated circuit for securely storing an International Mobile Subscriber Identity (IMSI) and associated keys, and is used to identify and authenticate a subscriber in a mobile device such as a mobile phone or computer. Additionally, contact information can be stored on many SIM cards.

[0090] The speaker (146) outputs sound-related results processed by the processor (102). The microphone (147) receives sound-related input to be used by the processor (102).

[0091] FIG. 4 shows an example of a 5G system structure to which the implementation of the present specification is applied.

[0092] The 5G system (5GS) structure consists of the following network functions (NF).

[0093] - AUSF (Authentication Server Function)

[0094] -AMF (Access and Mobility Management Function)

[0095] - DN (Data Network), for example, operator services, internet access, or third-party services

[0096] - USDF (Unstructured Data Storage Function)

[0097] - NEF (Network Exposure Function)

[0098] - I-NEF (Intermediate NEF)

[0099] - NRF (Network Repository Function)

[0100] - NSSF (Network Slice Selection Function)

[0101] - PCF (Policy Control Function)

[0102] - SMF (Session Management Function)

[0103] - UDM (Unified Data Management)

[0104] - UDR (Unified Data Repository)

[0105] - UPF (User Plane Function)

[0106] - UCMF (UE radio Capability Management Function)

[0107] - AF (Application Function)

[0108] - UE (User Equipment)

[0109] - (R)AN ((Radio) Access Network)

[0110] - 5G-EIR (5G-Equipment Identity Register)

[0111] - NWDAF (Network Data Analytics Function)

[0112] - CHF (CHarging Function)

[0113] 또한, 다음과 같은 네트워크 기능이 고려될 수 있다.

[0114] - N3IWF (Non-3GPP InterWorking Function)

[0115] - TNGF (Trusted Non-3GPP Gateway Function)

[0116] - W-AGF (Wireline Access Gateway Function)

[0117] Figure 4 shows the 5G system structure in a non-roaming case using a reference point representation showing how various network functions interact with each other.

[0118] In Figure 4, UDSF, NEF, and NRF are not described for clarity of the point-to-point diagram. However, all network functions shown can interact with UDSF, UDR, NEF, and NRF as needed.

[0119] For clarity, the connection between UDR and other NFs (e.g., PCF) is not shown in FIG. 4. For clarity, the connection between NWDAF and other NFs (e.g., PCF) is not shown in FIG. 4.

[0120] The 5G system structure includes the following reference points.

[0121] - N1: Reference point between UE and AMF.

[0122] - N2: Reference point between (R)AN and AMF.

[0123] - N3: Reference point between (R)AN and UPF.

[0124] - N4: Reference point between SMF and UPF.

[0125] - N6: Reference point between the UPF and the data network.

[0126] - N9: Reference point between two UPFs.

[0127] The following reference points show the interactions that exist between the NF services of NF.

[0128] - N5: Reference point between PCF and AF.

[0129] - N7: Reference point between SMF and PCF.

[0130] - N8: Reference point between UDM and AMF.

[0131] - N10: Reference point between UDM and SMF.

[0132] - N11: Reference point between AMF and SMF.

[0133] - N12: Reference point between AMF and AUSF.

[0134] - N13: Reference point between UDM and AUSF.

[0135] - N14: Reference point between two AMFs.

[0136] - N15: Reference point between PCF and AMF for non-roaming scenarios, reference point between PCF and AMF of the visited network for roaming scenarios.

[0137] - N16: Reference point between two SMFs (in the case of roaming, between the SMF of the visited network and the SMF of the home network)

[0138] - N22: Reference point between AMF and NSSF.

[0139] In some cases, two NFs may need to be connected to each other to service the UE.

[0140] The registration procedure is described. Refer to Section 4.2.2.2 of 3GPP TS 23.502 V16.3.0 (2019-12).

[0141] FIGS. 5 and FIGS. 6 illustrate examples of registration procedures to which the implementation of the present specification applies.

[0142] The UE must register with the network to receive services, enable mobility tracking, and enable reachability. The UE initiates the registration process using one of the following registration types.

[0143] - Initial registration for the 5GS; or

[0144] - Mobility registration update; or

[0145] - Periodic registration update; or

[0146] - Emergency registration

[0147] The general registration procedure of Figures 5 and 6 applies to all registration procedures described above, but the periodic registration update does not need to include all parameters used in other registration procedures.

[0148] The general registration procedure of Figures 5 and 6 is used when a UE is registered to a 3GPP connection when it is already registered to a non-3GPP connection, and vice versa. To register a UE to a 3GPP connection when it is already registered to a non-3GPP connection scenario, an AMF change may be required.

[0149] First, the procedure of Fig. 5 is explained.

[0150] (1) Step 1: The UE sends a Registration Request message to the (R)AN. The Registration Request message corresponds to the AN message.

[0151] A registration request message may include AN parameters. For NG-RAN, AN parameters include, for example, 5G-S-TMSI (5G SAE temporary mobile subscriber identity) or GUAMI (globally unique AMF ID), a selected PLMN (public land mobile network) ID (or PLMN ID and NID (network identifier)), and requested NSSAI (Requested network slice selection assistance information). AN parameters also include an establishment cause. The establishment cause provides the reason for requesting the establishment of an RRC connection. Whether and how the UE includes the requested NSSAI as part of the AN parameters depends on the value of the access stratum connection establishment NSSAI inclusion mode parameter.

[0152] The registration request message may include a registration type. The registration type indicates whether the UE wants to perform an initial registration (i.e., the UE is in the RM-DEREGISTERED state), or a mobility registration update (i.e., the UE is in the RM-REGISTERED state and initiates the registration process because the UE moves, or the UE wants to update capabilities or protocol parameters, or requests a change to the set of network slices allowed for the UE to use), or a periodic registration update (i.e., the UE is in the RM-REGISTERED state and initiates the registration process due to the expiration of the periodic registration update timer), or an urgent registration (i.e., the UE is in the restricted service state).

[0153] When a UE performs initial registration, the UE specifies the UE ID in the registration request message as follows, listed in order of decreasing priority.

[0154] i) If the UE has a valid EPS (evolved packet system) GUTI (globally unique temporary identifier), the 5G-GUTI mapped from the EPS GUTI;

[0155] ii) Native 5G-GUTI assigned by the PLMN for which the UE is attempting to register (if available);

[0156] iii) Native 5G-GUTI assigned by a PLMN equivalent to the PLMN for which the UE is attempting to register;

[0157] iv) Native 5G-GUTI assigned by other PLMNs (if available);

[0158] v) Otherwise, the UE includes SUCI (subscriber concealed identifier) ​​in the registration request message.

[0159] If the UE performing the initial registration has both a valid EPS GUTI and a native 5G-GUTI, the UE also marks the native 5G-GUTI as an additional GUTI. If one or more native 5G-GUTIs are available, the UE selects the 5G-GUTIs from items (ii)-(iv) in the list above in decreasing order of priority.

[0160] When the UE performs initial registration with native 5G-GUTI, the UE displays relevant GUAMI information in AN parameters. When the UE performs initial registration with SUCI, the UE does not display GUAMI information in AN parameters.

[0161] In the case of emergency registration, SUCI is included if the UE does not have a valid 5G-GUTI, and PEI is included if the UE does not have a SUPI (subscriber permanent identifier) ​​and does not have a valid 5G-GUTI. In other cases, a 5G-GUTI is included, which indicates the last serving AMF.

[0162] The registration request message may also include security parameters, PDU session status, etc. Security parameters are used for authentication and integrity protection. The PDU session status indicates a previously established PDU session in the UE. When the UE is connected to two AMFs belonging to different PLMNs via a 3GPP connection and a non-3GPP connection, the PDU session status indicates the established PDU session of the current PLMN in the UE.

[0163] (2) Step 2: (R)AN selects AMF.

[0164] If 5G-S-TMSI or GUAMI is not included, or if 5G-S-TMSI or GUAMI does not represent a valid AMF, (R)AN selects an AMF based on (R)AT and the requested NSSAI, where available.

[0165] If the UE is in the CM-CONNECTED state, (R)AN can forward a registration request message to the AMF based on the UE's N2 connection.

[0166] If (R)AN cannot select a suitable AMF, (R)AN performs AMF selection by forwarding a registration request message to the AMF configured in (R)AN.

[0167] (3) Step 3: (R)AN sends a registration request message to the new AMF. The registration request message corresponds to the N2 message.

[0168] The registration request message may include all information and / or part of the information contained in the registration request message received from the UE described in Step 1.

[0169] The registration request message may include N2 parameters. When NG-RAN is used, the N2 parameters include the selected PLMN ID (or PLMN ID and NID), location information and cell ID associated with the cell where the UE is camping, and a UE context request indicating that a UE context including security information in NG-RAN must be established. When NG-RAN is used, the N2 parameters also include the cause for establishment.

[0170] If the registration type indicated by the UE is a periodic registration update, steps 4-19 described below may be omitted.

[0171] (4) Step 4: If the UE's 5G-GUTI is included in the registration request message and the serving AMF has changed since the last registration procedure, the new AMF may call the Namf_Communication_UEContextTransfer service operation on the previous AMF, including the full registration request NAS (non-access stratum) message to request the UE's SUPI and UE context.

[0172] (5) Step 5: The previous AMF can respond to the new AMF for the Namf_Communication_UEContextTransfer call, including the UE's SUPI and UE context.

[0173] (6) Step 6: If SUCI is not provided by the UE or is not retrieved from the previous AMF, the new AMF may initiate the identity request procedure by sending an identity request message to the UE to request SUCI.

[0174] (7) Step 7: The UE may respond with an Identity Response message containing SUCI. The UE derives SUCI using the provided public key of the home PLMN (HPLMN).

[0175] (8) Step 8: The new AMF may decide to call AUSF to initiate UE authentication. In this case, the new AMF selects AUSF based on SUPI or SUCI.

[0176] (9) Step 9: Authentication / security may be established by UE, new AMF, AUSF and / or UDM.

[0177] (10) Step 10: If the AMF is changed, the new AMF may call the Namf_Communication_RegistrationCompleteNotify service operation to notify the previous AMF that UE registration is complete for the new AMF. If the authentication / security procedure fails, registration is rejected and the new AMF may call the Namf_Communication_RegistrationCompleteNotify service operation with a reject indication reason code for the previous AMF. The previous AMF may continue as if no UE context passing service operation was received.

[0178] (11) Step 11: If the PEI is not provided by the UE or has not been retrieved from the previous AMF, the new AMF may initiate an Identity Request procedure by sending an Identity Request message to the UE to retrieve the PEI. The PEI is transmitted in encryption, except in cases where the UE cannot perform emergency registration and be authenticated.

[0179] (12) Step 12: Optionally, the new AMF can call the N5g-eir_EquipmentIdentityCheck_Get service operation to start ME ID checking.

[0180] Now, the procedure of Fig. 6 following the procedure of Fig. 5 is explained.

[0181] (13) Step 13: If you perform Step 14 below, the new AMF can select a UDM based on SUPI, and the UDM can select a UDR instance.

[0182] (14) Step 14: New AMFs can be registered with UDM.

[0183] (15) Step 15: The new AMF can select PCF.

[0184] (16) Step 16: The new AMF may optionally establish / modify AM policy associations.

[0185] (17) Step 17: The new AMF can send update / release SM context messages (e.g., Nsmf_PDUSession_UpdateSMContext and / or Nsmf_PDUSession_ReleaseSMContext) to the SMF.

[0186] (18) Step 18: If the new AMF and the previous AMF are in the same PLMN, the new AMF can send a request to modify the UE context to N3IWF / TNGF / W-AGF.

[0187] (19) Step 19: N3IWF / TNGF / W-AGF can send a UE context modification response to the new AMF.

[0188] (20) Step 20: After the new AMF receives a response message from N3IWF / TNGF / W-AGF in Step 19, the new AMF can register with UDM.

[0189] (21) Step 21: The new AMF sends a Registration Accept message to the UE.

[0190] The new AMF sends a registration acceptance message to the UE indicating that the registration request has been accepted. If the new AMF assigns a new 5G-GUTI, the 5G-GUTI is included. If the UE is already in the RM-REGISTERED state via another connection on the same PLMN, the UE uses the 5G-GUTI received in the registration acceptance message for both registrations. If the registration acceptance message does not include a 5G-GUTI, the UE uses the 5G-GUTI assigned to the existing registration for the new registration as well. If the new AMF assigns a new registration area, it transmits the registration area to the UE via the registration acceptance message. If the registration acceptance message does not contain a registration area, the UE considers the previous registration area to be valid. Mobility Restrictions are included when mobility restrictions apply to the UE and the registration type is not an urgent registration. The new AMF indicates the PDU session established for the UE in the PDU session state. The UE locally removes internal resources associated with PDU sessions that are not marked as established in the received PDU session state. When a UE connects to two AMFs belonging to different PLMNs via a 3GPP connection and a non-3GPP connection, the UE locally removes internal resources associated with the PDU session of the current PLMN that are not indicated as established in the received PDU session state. If PDU session state information is present in the registration acceptance message, the new AMF instructs the UE on the PDU session state.

[0191] The Allowed NSSAI provided in the registration acceptance message is valid in the registration area and applies to all PLMNs having a tracking area included in the registration area. The Mapping of Allowed NSSAI is to map the HPLMN S-NSSAI to each S-NSSAI of the Allowed NSSAI. The Mapping of Configured NSSAI is to map the HPLMN S-NSSAI to each S-NSSAI of the Configured NSSAI for the serving PLMN.

[0192] Additionally, the new AMF optionally performs UE policy association establishment.

[0193] (22) Step 22: If the UE succeeds in updating itself, it can send a Registration Complete message to the new AMF.

[0194] The UE can send a registration completion message to the new AMF to check if a new 5G-GUTI has been assigned.

[0195] (23) Step 23: In the case of registration via a 3GPP connection, if the new AMF does not release the signaling connection, the new AMF may send RRC Inactive Assistance information to the NG-RAN. In the case of registration via a non-3GPP connection, if the UE is in a CM-CONTENED state on the 3GPP connection, the new AMF may send RRC Inactive Assistance information to the NG-RAN.

[0196] (24) Step 24: AMF can perform information updates on UDM.

[0197] (25) Step 25: The UE can execute network slice-specific authentication and authorization (NSSAA) procedures.

[0198] Examples of Non-Terrestrial Networks (NTN) are described below. In addition to the contents described in the disclosure of this specification, for a specific description of NTN, refer to 3GPP TS 38.300 V18.1.0 S16.14.

[0199] The following drawings are made to illustrate a specific example of the present specification. The names of specific devices or specific signals / messages / fields described in the drawings are presented as examples, and therefore the technical features of the present specification are not limited to the specific names used in the following drawings.

[0200] Figure 7 shows an example of an NTN structure.

[0201] Figure 7 illustrates an example of an NTN providing NTN NR access to a UE through an NTN payload and an NTN gateway. Referring to the example in Figure 7, a service link between the NTN payload and the UE and a feeder link between the NTN gateway and the NTN payload are illustrated.

[0202] The NTN payload can receive radio protocols from the UE (via a service link). The NTN payload can transparently transmit radio protocols to the NTN gateway (via a feeder link) or vice versa. The connections supported by the NTN payload are as follows:

[0203] - An NTN gateway can provide multiple NTN payloads;

[0204] - A single NTN payload can be provided by multiple NTN gateways.

[0205] For NTNs, in addition to the network identifiers described in Section 8.2 of 3GPP TS 38.300 V18.1.0, the following may apply:

[0206] - Tracking areas correspond to fixed geographic areas. Each mapping can be configured in the RAN;

[0207] - Mapped cell ID.

[0208] Three types of service links can be supported:

[0209] - Earth-fixed: Can be provided by beam(s) that continuously cover the same geographical area (e.g., in the case of GSO satellites);

[0210] - Quasi-Earth-fixed: Can be provided as a beam that covers one geographic area for a limited period and another geographic area for a different period (e.g., in the case of NGSO satellites generating a steerable beam);

[0211] - Earth-moving: Coverage area may be provided by a beam sliding over the Earth's surface (e.g., for NGSO satellites generating a fixed or unsteering beam).

[0212] For example, a gNB using NGSO satellites can provide quasi-Earth-fixed service links or Earth-moving service links. A gNB based on GSO satellites can provide Earth-fixed service links or quasi-Earth-fixed service links.

[0213] In NTN, distance refers to Euclidean distance.

[0214] - Satellites (or UAS platforms) can implement transparent or regenerative (including onboard processing) payloads. Satellites (or UAS platforms) can generate beams. For example, satellites typically generate multiple beams for a designated service area based on their line of sight. The footprint, which is the geographical range over which a beam reaches the ground, is typically elliptical.

[0215] - Transparent Payload: Transparent payloads can support radio frequency filtering, frequency conversion, and amplification. Therefore, the waveform signal repeated by the payload is not altered.

[0216] - Regenerative Payload: The regenerative payload can support radio frequency filtering, frequency conversion and amplification, demodulation / decoding, switching and / or routing, and coding / modulation. This is virtually equivalent to equipping a satellite (or UAS platform) with all or part of base station functions (e.g., gNB).

[0217] In various examples of the present disclosure, technical features related to voice calls via satellite are described.

[0218] For example, a method is proposed to optimize the initiation of an IMS (IP Multimedia Subsystem) voice call via an NB-IoT GEO satellite when the UE is in IDLE.

[0219] The method proposed in the present disclosure may consist of a combination of one or more of the following operations / configurations / steps.

[0220] For the procedures and / or messages described below, conventional procedures / messages may be used, conventional procedures / messages may be used in an extended manner, or new procedures / messages may be defined and used.

[0221] In various examples of the disclosure of this specification, the terms Satellite and satellite are used interchangeably.

[0222] In various examples of the disclosure in this specification, User Equipment (UE) and terminal are described interchangeably.

[0223] In various examples of the disclosure of this specification, descriptions identical to those of the prior art are omitted, and the content is described primarily as proposed in the disclosure of this specification.

[0224] Discussions for supporting satellite communications are provided by 3GPP. (e.g., SP-250400, Study on Integration of satellite components in the 5G architecture Phase 4)

[0225] For example, in TR 23.700-19, a discussion on a method to support voice calls for a UE accessing an NB-IoT RAT via a GEO satellite is provided as follows.

[0226] Architectural Assumption

[0227] For IMS voice calls (or voice calls) via NB-IoT (GEO), the following architectural assumptions and principles are applied in this study.

[0228] - Uses the GEO satellite access EPC architecture for NB-IoT as the standard.

[0229] For example, research on CP CIoT EPS optimization, UP CIoT EPS optimization, and S1-U-based NB IoT NTN solutions is provided.

[0230] For example, the solution can use CP CIoT EPS optimized data from NB-IoT prior to Rel-20 as NAS signaling, and this can have a higher priority than UP data.

[0231] - NB-IoT (GEO), EPC, and IMS enhancement features for voice call support via GEO can be minimized.

[0232] - For example, only architecture options for data transmission via SGi may be considered. Data transmission options via SCEF / T8 may not be considered.

[0233] - The IMS reference architecture can be used as a standard for non-emergency calls.

[0234] For emergency IMS sessions via NB-IoT (GEO), the following additional architectural assumptions and principles may be applied.

[0235] - For emergency calls, the new IMS reference architecture can be used as the standard.

[0236] Key Issue #1

[0237] Support for IMS voice calls on NB-IoT NTN via GEO satellites connected to the EPC

[0238] This core issue investigates the following issues to support IMS voice calls in NB-IoT NTN via GEO satellites connected to the EPC.

[0239] - System improvement to support IMS voice services in NB-IoT NTN via GEO satellites connected to EPC

[0240] - QoS support status and support method for IMS voice services via GEO satellite

[0241] In the case of NB-IoT, the following limitations may apply.

[0242] For example, an NB-IoT UE can support up to two data radio bearers.

[0243] Connection control in NB-IoT

[0244] NB-IoT UEs support only 0, 1, or 2 DRBs depending on performance. NB-IoT UEs that support only control plane CIoT EPS optimization or control plane CIoT 5GS optimization do not need to support DRBs and related procedures.

[0245] Dedicated bearers may not be supported for NB-IoT RATs.

[0246] Dedicated bearers are not supported in NB-IoT. The PDN GW uses the RAT type to check if there are no active dedicated bearers when the UE accesses via NB-IoT. For mobility between RATs from WB-EUTRA to NB-IoT, the UE and MME indicate the local deactivation of non-default EPS bearers in the TAU as specified in TS 24.301.

[0247] - For example, NB-IoT may not support GBR (Guaranteed Bit Rate) bearers.

[0248] Bearer-level QoS parameters

[0249] GBR bearers may not be supported in NB-IoT. The PDN GW may not enable GBR bearers when the UE uses NB-IoT by using the RAT type.

[0250] For example, a PDU session can have only one QoS Flow and a default QoS rule.

[0251] NB-IoT QoS model

[0252] The 5GC QoS model can be applied to NB-IoT that meets the following requirements.

[0253] - The default QoS rule must be the only QoS rule for a PDU session of a UE connected to 5GC via NB-IoT. There can be only one QoS flow corresponding to the default QoS rule per PDU session.

[0254] Reflective QoS may not be supported in NB-IoT.

[0255] - In the case of NB-IoT, if a user plane resource is enabled for the corresponding PDU session, a 1:1 mapping can be applied between the QoS flow corresponding to the default QoS of the PDU session and the data wireless bearer.

[0256] - In NB-IoT, up to two data wireless bearers can be supported. Therefore, up to two PDU sessions can have active user plane resources simultaneously.

[0257] - Support for multiple UP resources for an NB-IoT UE can be specified in the UE 5GMM core network function. During PDU session setup or UP resource activation, the AMF can determine whether the UE can support user plane resource setup.

[0258] In the Key Issue Study, both control plane-based and user plane-based solutions can be discussed.

[0259] In EPS, information regarding whether data transmission is mutually possible through the User Plane and / or Control Plane of the terminal and the network, and information regarding the data transmission method preferred by the terminal, can be exchanged during the Attach or Tracking Area Update (TAU) process.

[0260] In 5GS, this information can be exchanged during the Registration / Mobility Registration Update process.

[0261] Regarding preferred and supported network behaviors, the EPS Spec is described as follows. Similar details are described in 5GS. Additionally, terminals supporting NB-IoT can indicate that they support Control Plane CIoT EPS / 5GS Optimization.

[0262] Preferred and supported network behavior

[0263] The UE can include network behaviors that the UE can support and preferred network behaviors in the preferred network behavior indication.

[0264] Preferred network behavior may include the following information.

[0265] - Whether Control Plane CIoT EPS Optimization is Supported

[0266] - Support for user-planar CIoT EPS optimization

[0267] - Whether to prefer control plane CIoT EPS optimization or user plane CIoT EPS optimization

[0268] - Whether S1-U data transfer is supported

[0269] - Whether to request SMS transmission without a combined connection

[0270] - Whether connection is supported without a PDN connection

[0271] - Support for header compression for Control Plane CIoT EPS optimization

[0272] If a UE requests SMS transmission without a coupled EPS connection, a supporting MME provides SMS transmission without the UE establishing a coupled EPS connection. An MME connected to NB-IoT must support SMS transmission without the UE establishing a coupled connection. This feature is available only to UEs that support NB-IoT only.

[0273] If the UE indicates that S1-U data transfer is supported, the UE supports data transfer that is not subject to CIoT EPS optimization. If the UE supports user plane CIoT EPS optimization, it must also support S1-U data transfer.

[0274] If a connection without a PDN is supported, the UE does not need to establish a PDN connection as part of the connection procedure, and the UE and MME can release all PDN connections and maintain the EPS connection at any time.

[0275] The MME indicates the network operations permitted by the network in the supported network operations information. This indication depends on the TAI list. The MME may indicate one or more of the following.

[0276] - Whether Control Plane CIoT EPS Optimization is Supported

[0277] - Support for user-planar CIoT EPS optimization

[0278] - Whether S1-U data transfer is supported

[0279] - Whether SMS transmission is allowed without a combined connection

[0280] - Whether connection is supported without a PDN connection

[0281] - Whether header compression is supported for control plane CIoT EPS optimization

[0282] If the MME supports user plane CIoT EPS optimization, it must also support S1-U data transmission. If both the UE and the MME support user plane CIoT EPS optimization, the MME sets the UE user plane CIoT support metric to "Supported" in the S1-AP message.

[0283] For NB-IoT UEs that support only control plane CIoT EPS optimization, the MME must include control plane CIoT EPS optimization support in the NAS acceptance message.

[0284] UEs that support NB-IoT must always indicate that they support control plane CIoT EPS optimization.

[0285] In networks supporting a dedicated core network (see Section 5.19), a UE's Preferred Network Behavior indication can be used to influence policy decisions that may trigger Attach or TAU rerouting from one MME to another.

[0286] Other CIoT EPS optimizations include "connect without PDN connection setup," "PDN type = non-IP," and "UE connection to SCEF." These features are requested through implicit and explicit signaling.

[0287] Control plane CIoT EPS / 5GS optimization is a method of transmitting data via NAS signaling. For the uplink, terminals in the IDLE state transmit data included in a Control Plane Service Request (CPSR) NAS message. Terminals in the CONNECTED state transmit IoT data included in a UL NAS Transport message.

[0288] In the case of Downlink, the terminal transmits IoT Data included in the DL NAS Transport message.

[0289] Figures 8a and 8b show an example of the MO data transmission process of the control plane CIoT EPS / 5GS optimization.

[0290] Specifically, FIGS. 8a and 8b illustrate examples of MO (Mobile Originated) data transmission within a NAS PDU.

[0291] Figures 9a and 9b show an example of the MO data transmission process of the control plane CIoT EPS / 5GS optimization.

[0292] Specifically, Figures 9a and 9b show examples of MO data transmission anchored to a UPF in control plane CIoT 5GS optimization.

[0293] When the terminal and the network support both control plane CIoT EPS optimization and S1-U data transmission, through control plane CIoT EPS optimization, the operating terminal can transmit a control plane service request containing an active flag while in the ECM-IDLE or ECM-CONNECTED state, or switch from data transmission through the control plane to data transmission through the user plane by creating a user plane based on the MME's judgment (e.g., data size to be transmitted or received).

[0294] Figure 10 shows an example of an S1-U bearer setup during data transmission in control plane CIoT EPS optimization.

[0295] In the case of 5GS, when control plane CIoT 5GS optimization is enabled, a procedure may be proposed in which control plane CIoT 5GS optimization is used for the N3 data transfer setup procedure, and then switches to performing N3 data transfer through the user plane.

[0296] Unlike EPS, 5GS does not activate all PDUs, but can request activation of the user plane by specifying the PDU session that is desired using the "list of PDU sessions to be activated."

[0297] N3 Data Transfer Setup Procedure When Control Plane CIoT 5GS Optimization Is Enabled

[0298] UE Trigger N3 Data Transfer Setup Procedure

[0299] If the UE and AMF successfully negotiate N3 data transmission in addition to control plane CIoT 5GS optimization, the UE can initiate the N3 data transmission setup procedure for all PDU sessions that do not include a control plane-only indicator (e.g., depending on the amount of data to be transmitted on the uplink).

[0300] The N3 data transmission setup procedure triggered by the UE can be initiated by the UE in the CM-IDLE or CM-CONNECTED state and can follow the UE-triggered service request procedure, including the following features.

[0301] Step 1. Send AN message from UE to (R)AN

[0302] The UE includes a service request for control plane CIoT 5GS optimization (list of PDU sessions to be enabled, list of allowed PDU sessions, security parameters, PDU session status, [NAS message container]) in an AN message.

[0303] When a UE attempts to activate a user plane resource for a PDU session, a List of PDU Sessions To Be Activated is provided by the UE. The UE does not include PDU sessions that have received a Control Plane Only Indicator in the List of PDU Sessions To Be Activated. If the UE is camping on NB-IoT, the UE must configure the List of PDU Sessions To Be Activated so that the number of PDU sessions with activated user plane resources does not exceed two.

[0304] If this procedure is triggered by a paging response and there is user data to be transmitted to the UE simultaneously, the UE may request N3 data transmission settings for one or more PDU sessions. The UE indicates this in the list of PDU sessions to be enabled. Otherwise, the UE does not identify any PDU sessions in the list of PDU sessions to be enabled.

[0305] Step 2. (R)AN to AMF: N2 message (N2 parameters, service request).

[0306] Step 3. If the service request is not transmitted in an integrity-protected state or fails to verify integrity protection, the AMF rejects the service request.

[0307] Step 4. [Conditional] From AMF to SMF: Nsmf_PDUSession_UpdateSMContext request(PDU Session ID, Action Type, UE Location Info, Access Type, RAT Type, UE Presence in LADN Service Area, Access Type Changeable, [MO Exception Data Counter], [Satellite Backhaul Category], [GEO Satellite ID]).

[0308] Step 4 or 5a. After receiving the Nsmf_PDUSession_UpdateSMContext request or after the SMF initiates an SM policy association modification based on the UE request and local policy, the SMF determines whether to establish N3 data transfer for the PDU session. The SMF does not establish N3 data transfer for the PDU session for which the Control Plane Only Indicator was received.

[0309] Step 11. The SMF indicates whether N3 data transmission settings (i.e., data radio bearer and N3 tunnel enabled) are configured for the PDU session in the Nsmf_PDUSession_UpdateSMContext response.

[0310] Step 12. If the RAT type is NB-IoT, the AMF must ensure that the number of PDU sessions with active user plane resources does not exceed 2. If the AMF decides not to include PDU sessions to be activated in the N2 message, the AMF notifies the SMF of this via the Nsmf_PDUSession_UpdateSMContext request in the list of PDU sessions that failed to be set up, along with the cause of failure provided in the N2 SM information element in Step 15.

[0311] For example, based on the request from SMF in step 11, AMF includes NAS service acceptance for control plane CIoT 5GS optimization, which includes information about the PDU session where N3 data transmission is set.

[0312] The network starts using the N3 bearer for all DL data in this PDU session. Control plane CIoT 5GS optimization is considered enabled for data transmission for all PDU sessions where N3 data transmission is not set.

[0313] Step 13. The UE starts using the N3 bearer for all UL data in this PDU session.

[0314] According to the current EPS TS 24.301 spec, if the active flag is included in the Control Plane Service Request, user data cannot be included in the ESM message container.

[0315] b) If there is pending user data to be transmitted to the UE in EMM-IDLE mode;

[0316] m) If a UE in EMM-CONNECTED mode with only NAS signaling connections is using an EPS service that uses control plane CIoT EPS optimization and there is pending user data to be transmitted via the user plane wireless bearer;

[0317] For example, if the UE has pending IP, non-IP, or Ethernet user data to be transmitted over a user plane wireless bearer, the UE must set the Control Plane Service Type of the Control Plane Service Request message to "Mobile Outgoing Request" and set the "Active" flag of the Control Plane Service Type IE to 1. The UE must not include an ESM message container or a NAS message container IE in the Control Plane Service Request message.

[0318] In 5GS, you can specify the PDU session to be activated through the Uplink data status IE within the control plane service request.

[0319] As described in TS 24.501 below, there is a case where an IDLE UE has uplink user data to send, and it is not allowed to include the Uplink data status IE along with the user data.

[0320] The purpose of the service request procedure is as follows.

[0321] c) If the UE uses 5GS services through control plane CIoT 5GS optimization and the 5GMM mode is 5GMM-IDLE mode, to initiate user data transmission through the control plane.

[0322] In the case of c), the uplink data status IE must not be included in the service request message.

[0323] The UE must call the service request procedure in the following cases.

[0324] d) If there is pending uplink user data on the UE in 5GMM-IDLE mode over 3GPP access (except for the case of j).

[0325] In cases c) and d), if the UE has pending CIoT user data to be transmitted through the control plane, the UE must set the control plane service type of the control plane service request message to "Mobile Outgoing Request". If the UE has only uplink CIoT user data, SMS, or location service messages to transmit, the UE must do the following:

[0326] a) If the data size does not exceed 254 octets, there are no other optional IEs to include in the CONTROL PLANE SERVICE REQUEST message, and the transmitted data is as follows:

[0327] 1) If it is CIoT user data, set the data type field to "Control Plane User Data" and include the PDU session ID, data, and expected downlink data (DDX) (if available) in the CIoT small data container IE.

[0328] 2) For location service messages, set the data type field in CIoT small data container IE to "Location service message container" and, if possible, set downlink data estimate (DDX).

[0329] i) When routing information is provided by the upper layer:

[0330] A) Set the length of the additional information field of the CIoT small data container IE to the length of the routing information provided by the upper-tier location service application, and set the additional information field of the CIoT small data container IE to the routing information provided by the upper-tier location service application; or

[0331] B) Otherwise, set the length of the additional information field of the CIoT small data container IE to 0. In this case, the additional information field of the CIoT small data container IE is not included; and

[0332] ii) Set the data content field of the CIoT small data container IE to the location service message payload; or

[0333] 3) For SMS, set the data type field to "SMS" and include SMS in the CIoT small data container in IE; or

[0334] b) Otherwise, if the data size exceeds 254 octets or there is another optional IE to be included in the control plane service request message and the data being transmitted is as follows:

[0335] 1) CIoT User Data: Set the payload container type IE to "CIoT User Data Container", include the PDU Session ID in PDU Session ID IE, and include the data in the payload container IE;

[0336] 2) Location Service Message: Set the payload container type IE to "Location Service Message Container" and include data in the payload container IE. If the upper-layer location service application provides routing information, set additional information IE to routing information; or

[0337] 3) For SMS, set the payload container type IE to "SMS" and include the data in the payload container IE. [...]

[0338] In the case of d) and k), if there is pending user data to be transmitted through the user plane in the UE:

[0339] a) If there is an urgent PDU session displayed in the uplink data status IE, the UE must set the Control Plane Service Type of the Control Plane Service Request message to "Emergency Service"; or

[0340] b) Otherwise, the UE must set the control plane service type to "Mobile Outgoing Request";

[0341] The UE must include the uplink data status IE in the control plane service request message to indicate whether there is pending user data to be transmitted through user plane resources or a PDU session associated with an active multicast MBS session;

[0342] For example, in the case of a UE in NB-N1 mode, user plane resource settings cannot be requested using the uplink data state IE. Therefore, user plane resources are set for a number of PDU sessions that exceed the maximum number of user plane resources supported by the UE.

[0343] When a terminal transmits and receives voice data using a separate dedicated bearer / QoS Flow, the P-CSCF delivers the SIP 183 Progress message to the terminal after the voice call is triggered and before the P-CSCF delivers the 183 Progress message. This is after the PCRF / PCF receives the Authorization Authentication (AA) Request message for the bearer / QoS flow, requests the PGW / SMF to create the dedicated bearer / QoS flow, and the creation of the dedicated bearer / QoS flow between the terminal and the network is completed and the PCRF / PCF sends the AA Answer to the P-CSCF.

[0344] Figures 11a and 11b show an example of a procedure for a VoLTE service.

[0345] For example, Figures 11a and 11b illustrate the procedures updated in the VoLTE Service Description and Implementation Guidelines, a document of the GSMA.

[0346] The following shows the KPIs for data rate and call setup time to support IMS voice calls when using GEO satellite access defined in SA1.

[0347] Table 3 shows one example of Consolidated potential KPIs.

[0348] For example, Table 3 shows the integrated performance requirements for IMS voice calls using GEO satellite access.

[0349] ScenarioUE typeTransmission data rateCall setup timeULDLIMS voice call using GEOHandheld[1-3] kbit / s[1-3] kbit / s≤30 s- call set up time refers;- 30s is the upper bound that is derived based on the user's patience suggestions (30s);

[0350] NB-IoT RAT has a very limited data rate, and the unidirectional latency between the terminal and the GEO satellite is up to 270ms. It may take up to 540ms to connect to the ground via the GEO satellite.

[0351] Regarding the limitations of voice calls to NB-IoT via GEO Satellite mentioned above, minimizing Call Setup Time is an important factor in user experience.

[0352] For a UE in an IDLE state, a Service Request is required to access the network. To attempt a voice call, a UE in an IDLE state must request a Service Request from the network and, only after receiving a Service Accept Message in response, can it send an IMS INVITE message for the voice call.

[0353] Terminals operating with Control Plane CIoT EPS Optimization can use Control Plane Service Requests. Using a Control Plane Service Request offers the advantage of rapidly transmitting data before receiving a Service Accept message from the terminal, as it allows an INVITE message to be embedded within the request and sent to the counterparty over the network in advance.

[0354] However, it is difficult to satisfy the QoS for voice services using only the Control Plane, and a GBR dedicated bearer (GBR QoS Flow) is required to satisfy the QoS for voice services. To satisfy this, it is also necessary to allow the creation of a GBR dedicated bearer (GBR QoS Flow) for NB-IoT terminals.

[0355] Under the current specification, data is transmitted using only one path—either the Control Plane or the User Plane—within a single PDN, and both paths cannot be used simultaneously.

[0356] Therefore, in order to reduce the terminal's Call Setup Time in NB-IoT access via GEO Satellite, a method to enhance the existing EPS / 5GS is required.

[0357] Hereinafter, a method and apparatus for a voice call via satellite according to some embodiments of the present disclosure will be described with reference to the following drawings.

[0358] The following drawings are made to illustrate a specific example of the present specification. The names of specific devices or specific signals / messages / fields described in the drawings are presented as examples, and therefore the technical features of the present specification are not limited to the specific names used in the following drawings. Hereinafter, a wireless device may be referred to as a User Equipment (UE).

[0359] Figure 12 shows an example of a method for a voice call via satellite.

[0360] In particular, FIG. 12 shows an example of a method performed by a wireless device (e.g., a user device (UE)).

[0361] In step S1201, the user device (UE) can establish a connection with the network node for the IMS (IP Multimedia Subsystem) voice service.

[0362] For example, IMS voice services can be based on NB-IoT (Narrowband Internet of Things (NB-IoT)) using satellites.

[0363] For example, a network node can be an MME (Mobility Management Entity) or an AMF (Access and Mobility Management Function). For example, in EPS, a UE can establish a connection with an MME for voice services. For example, in 5GS, a UE can establish a connection with an AMF for voice services.

[0364] For example, if the above network node is an MME, the MME can establish a PDN (Packet Data Network) connection with the UE for IMS voice services.

[0365] For example, if the above network node is an AMF, the AMF can establish a PDU (Protocol Data Unit) session connection with the UE for the IMS voice service.

[0366] According to some embodiments of the present disclosure, when establishing a connection for a voice service, the UE may establish a dedicated bearer or a dedicated QoS Flow for the IMS voice service, excluding the user plane radio bearer between the UE and the base station. In this case, the user plane radio bearer may be activated after the first message is transmitted.

[0367] For example, while establishing a connection for IMS voice services with a network node (e.g., a PDN connection or a PDU session connection), the UE may establish a dedicated bearer or a dedicated QoS Flow for IMS voice services, but may not establish a user plane radio bearer between the UE and the base station (e.g., a satellite). Subsequently, after transmitting the first message in step S1202, the UE may establish a user plane radio bearer between the UE and the base station.

[0368] For example, the network node may decide to establish a dedicated bearer or a dedicated QoS Flow for the IMS voice service, excluding the user plane wireless bearer between the UE and the base station. Additionally, the network node may convey the above decision to the UE. Based on the network node's decision, the UE may establish a dedicated bearer or a dedicated QoS Flow, excluding the user plane wireless bearer between the UE and the base station. For example, if a wireless bearer for the dedicated bearer is not to be created, the network node (MME) may not send a request to create a wireless bearer for the dedicated bearer through the base station. For example, the network node may decide to establish the user plane wireless bearer after receiving the first message. For example, the network node may convey the above decision to the UE. Based on the above decision, the UE may establish the user plane wireless bearer.

[0369] According to some embodiments of the present disclosure, when establishing a connection for voice services, the UE may not establish a dedicated bearer or a dedicated QoS Flow for IMS voice services. For example, after transmitting the first message in step S1202, the UE may establish a dedicated bearer or a dedicated QoS Flow for IMS voice services. In this case, the UE may establish the dedicated bearer or a dedicated QoS Flow together with a user plane wireless bearer.

[0370] In step S1202, the UE can transmit a first message to the network node in the CM-Idle state, which includes (i) information related to user data and (ii) information related to user plane activation.

[0371] For example, the first message may be a Control Plane Service Request message or a Non-Access-Stratum message.

[0372] For example, the first message may include an Invite message or a SIP (Session Initiation Protocol) Invite message. For example, information related to user data may include an Invite message or a SIP Invite message.

[0373] For example, the information related to the activation of the user plane may include an active flag for activating the user plane. For example, in an EPS, the terminal may transmit a first message containing an invite message and an active flag to a network node (e.g., MME). After receiving the first message containing the invite message and the active flag, the network node may activate the user plane. After activating the user plane, the network node may request the setup of a user plane radio bearer (e.g., a radio data bearer) through a base station and / or SGW. After the user plane radio bearer is set up, the terminal may transmit IMS signaling data through the user plane radio bearer.

[0374] For example, information related to the activation of the user plane may include an Uplink Data Status IE with the ID of the Protocol Data Unit (PDU) session for the IMS voice service. For example, in 5GS, the terminal may transmit a first message to the network node (e.g., AMF) containing a SIP Invite message and the Uplink Data Status IE with the ID of the PDU session. The AMF may know that a dedicated QoS flow is required for the IMS PDU session. The AMF may transmit a separate indication to the SMF (e.g., via Nsmf_PDUSession_UpdateSMContext). The SMF may perform configuration for the N3 user plane / radio bearer for the dedicated QoS flow. For example, the network node may request the configuration of a user plane radio bearer (e.g., radio data bearer) through the base station and / or the SMF. After the user plane radio bearer is configured, the terminal may transmit IMS signaling data through the user plane radio bearer.

[0375] According to some embodiments of the present disclosure, the UE can communicate with at least one of user equipment, a network, or an autonomous vehicle other than the UE.

[0376] Figure 13 shows an example of a method for a voice call via satellite.

[0377] In particular, Fig. 13 shows an example of a method performed by a network node.

[0378] For example, a network node can be an MME in EPS or an AMF in 5GS.

[0379] In step S1301, the network node may perform the step of establishing a connection with the user equipment (UE) for IMS voice services.

[0380] For example, if the above network node is an MME, the MME can establish a PDN connection with the UE for IMS voice services.

[0381] For example, if the network node is an AMF, the AMF can establish a PDU session connection with the UE for the IMS voice service.

[0382] For example, in step S1301, the network node may set a dedicated bearer or a dedicated QoS Flow for the IMS voice service, excluding the user plane radio bearer between the UE and the base station.

[0383] For example, the network node can set the user plane wireless bearer, characterized by being set after receiving the first message in step S1302.

[0384] For example, the network node may decide to set up a dedicated bearer or a dedicated QoS Flow for the IMS voice service, excluding the user plane wireless bearer between the UE and the base station. Additionally, the network node may convey the above decision to the UE. Based on the network node's decision, the UE may set up a dedicated bearer or a dedicated QoS Flow, excluding the user plane wireless bearer between the UE and the base station. For example, the network node may decide to set up the user plane wireless bearer after receiving the first message. For example, the network node may convey the above decision to the UE. Based on the above decision, the UE may set up the user plane wireless bearer.

[0385] According to some embodiments of the present disclosure, when establishing a connection for a voice service, a network node may establish a dedicated bearer or a dedicated QoS Flow for the IMS voice service, excluding a user plane radio bearer between the UE and the base station. In this case, the user plane radio bearer may be established after receiving the first message.

[0386] According to some embodiments of the present disclosure, when establishing a connection for voice services, the UE may not establish a dedicated bearer or a dedicated QoS Flow for IMS voice services. For example, after receiving the first message in step S1302, the network node may establish a dedicated bearer or a dedicated QoS Flow for IMS voice services. In this case, the network node may establish the dedicated bearer or a dedicated QoS Flow together with a user plane wireless bearer.

[0387] In step S1302, the network node may perform the step of receiving a first message from a UE in the CM-IDLE state, the message including (i) information related to user data and (ii) information related to user plane activation.

[0388] For example, the first message may be a control plane service request message or a NAS message (Non-Access-Stratum message).

[0389] For example, the first message may include an Invite message or a SIP Invite message. For example, information related to user data may include an Invite message or a SIP Invite message.

[0390] For example, the information related to the activation of the user plane may include an activation flag for activating the user plane.

[0391] For example, information related to the above user plane activation may include an uplink data status IE with an ID of the PDU session for the above IMS voice service.

[0392] In step S1303, the network node can perform the step of activating the user plane.

[0393] For example, in an EPS, a network node (e.g., MME) can enable a user plane for the UE. For example, the MME can establish a user plane radio bearer (e.g., a data radio bearer) with a base station and an SGW. The UE can transmit and receive voice data using the user plane radio bearer.

[0394] For example, in 5GS, a network node (e.g., AMF) can enable a user plane for the UE for a PDU session for the IMS voice service with the UE. For example, the AMF can establish a user plane radio bearer (e.g., a data radio bearer) with a base station and an SMF. The UE can transmit and receive voice data using the user plane radio bearer.

[0395] Below, several embodiments of a method for optimizing the initiation of an IMS Voice Call via an NB-IoT GEO satellite when the UE is in IDLE are described.

[0396] A method for optimizing an IDLE UE to initiate an IMS Voice Call via an NB-IoT GEO satellite consists of a combination of one or more of the following actions / configurations / steps.

[0397] These procedures and / or messages may use conventional procedures / messages, extend conventional procedures / messages, or define and use new procedures / messages.

[0398] In this specification, the terms Satellite and satellite are used interchangeably.

[0399] In this specification, the terms voice call and voice call are used interchangeably.

[0400] In this specification, MT Data, DL data, MT traffic, and DL traffic are used interchangeably.

[0401] In this specification, MO Data, UL data, MO traffic, and UL traffic are used interchangeably.

[0402] In this specification, the terms UE (User Equipment) and terminal are used interchangeably.

[0403] This specification focuses on the proposed content.

[0404] In this specification, satellites are assumed to be GEO satellites. However, other types of satellites are not excluded.

[0405] In this specification, the components and interfaces of EPS and 5GS are described, and each can be mapped as follows.

[0406] (MME - AMF, eNB - NG-RAN (gNB), HSS - UDM, Attach - Registration, TAU (Tracking Area Update) - Mobility Registration Update (MRU), S-GW - SMF (SMF / UPF), ECM-CONNECTED - CM-CONNECTED, ECM-IDLE - CM-IDLE) , PCRF - PCF

[0407] For NB-IoT terminals, IMS signaling for voice data and IMS voice are basically assumed to use a User Plane in an (E)CM-CONNECTED state. IMS signaling can be transmitted via a default bearer or default QoS flow, and IMS voice can be transmitted via a default bearer / QoS flow or a dedicated bearer / QoS flow for GBR QoS.

[0408] In the case of NB-IoT terminals, they may not support GBR dedicated bearer / GBR QoS Flow. However, if enhanced to support this, NB-IoT terminals may support GBR dedicated bearer / GBR QoS Flow.

[0409] In the present disclosure, to reduce the Call Setup Time of a terminal in NB-IoT access via GEO Satellite, a method is proposed to conduct a voice call by activating the User Plane along with the delivery of an INVITE message via a Control Plane Service Request. Additionally, in the proposed method, a method is proposed to generate a Dedicated Bearer / QoS Flow at the network level in advance and generate only the terminal's Radio Bearer at this time.

[0410] Hereinafter, a method for requesting UP activation while sending an INVITE message to a Control Plane Service Request according to some embodiments of the present disclosure will be described.

[0411] For example, an example in EPS can be suggested.

[0412] Optimizing IMS voice call initiation via NB-IoT (GEO) when UE is in idle state

[0413] The high-level principles of the solution are as follows:

[0414] - The UE and the network support both CP CIoT EPS optimization and S1-U data transmission.

[0415] - The UE uses the IMS user plane for IMS signaling and voice when in the ECM-CONNECTED state.

[0416] - When the UE is in the ECM-IDLE state and initiates a voice call, it marks the active flag in the Control Plane Service Request and includes a SIP INVITE in the ESM message container. This enables the S1-U bearer and the user plane wireless bearer for the IMS PDN connection.

[0417] - The remaining IMS procedure continues in the user plane.

[0418] - During the IMS PDN connection, an EPS bearer for IMS signaling and IMS voice is established. However, the user plane radio bearer is not activated. In this case, when the MME receives an active flag, it establishes the S1-U bearer, activates the user plane radio bearer for IMS signaling and voice, and uses the user plane for IMS signaling (default bearer) and IMS voice (dedicated GBR bearer).

[0419] A UE triggering an IMS voice call has the advantage of saving call setup time via CP because the INVITE message can be included in the control plane service request message. Therefore, service request and service acceptance waiting times in the network can be saved. To support the QoS of IMS voice data, a dedicated GBR bearer via NB-IoT RAT is required.

[0420] This solution describes enhancement based on CP CIoT EPS optimization and S1-U bearer setup during data transmission in CP CIoT EPS optimization. By default, when the UE is in the ECM-CONNECTED state, the UE uses a user plane default bearer for IMS signaling and a dedicated bearer for IMS voice. However, when the UE is in the ECM-IDLE state, the UE sends a SIP INVITE message containing an active flag using a Control Plan Service Request. The MME forwards the SIP INVITE contained in the ESM message to the SGW via the S11-U interface and sets up the S1-U bearer. Then, the remaining IMS SIP signaling and voice are transmitted through the user plane default bearer and the dedicated bearer, as in the existing procedure.

[0421] For example, since NB-IoT UEs support only up to two data radio bearers, the MME must set a Control Plane Only Indicator for all PDNs other than the IMS PDN.

[0422] Instead of the above action, the MME / AMF may request the release of data radio bearers for other PDN Connections if there are already created data radio bearers (i.e., if the number of data radio bearers for IMS is insufficient).

[0423] After the voice call ends, the eNB may initiate the S1 release procedure (e.g., due to user inactivity). The MME releases the UE context for the eNB and releases the wireless bearer.

[0424] The proposed solution optimizes the call initiation part by considering only when the UE is in the ECM-IDLE state, so it can be used in conjunction with other solutions.

[0425] In the existing IMS voice call setup procedure, a dedicated bearer is activated. Dedicated bearer activation is triggered by the P-CSCF requesting an AA request from the PCRF after receiving the UE response SIP 183 progress message from the receiving party regarding the SIP INVITE. The P-CSCF waits for an AA response from the PCRF until dedicated bearer activation is complete. Then, the P-CSCF forwards the SIP 183 progress message to the originating UE.

[0426] To save time waiting for the PCRF's AA response and to activate the user plane radio bearer for IMS voice before the P-CSCF delivers the SIP 183 progress during a voice call, the UE signals the MME with an active flag to activate the IMS voice bearer using a NAS message when initiating the IMS voice call. As specified in Clause 4.10 of TS 23.401, all SGi PDN connections of the UE must use S11-U or S1-U at any time. Therefore, upon receiving the active flag resulting from the initiation of a voice call (e.g., INVITE), the MME immediately activates both IMS bearers for signaling and voice. It then begins using UP for IMS signaling and voice.

[0427] Figures 14a and 14b show examples of high-level procedures for IMS voice via NB-IoT (GEO).

[0428] 0. The GEO satellite for NB-IoT access broadcasts that the SIB supports IMS voice services via NB-IoT.

[0429] 1. The UE provides an Attach Request to the NB-IoT (GEO) satellite with the voice domain preference set to IMS PS Voice only and the UE's usage setting set to voice centric. Additionally, the Preferred Network Behavior indicates that both Control Plane CIoT EPS optimization and S1-U data transmission are supported. The UE can use the IMS PDN as the attachment PDN.

[0430] The MME processes an Attach Request from the UE. If the connection is successful, the MME sends an Attach Accept message to the UE. The MME indicates in the supported network operation information that both Control Plane CIoT EPS optimization and S1-U data transmission are supported. The MME also indicates that it supports IMS voice over NB-IoT.

[0431] If the UE is not connected using the IMS PDN, the UE establishes an IMS PDN connection (PDN Connection).

[0432] You can also create a dedicated bearer for IMS voice during the PDN connection. The dedicated bearer is created in advance, but the radio data bearer may not be created.

[0433] During the process of configuring a PDN connection for IMS services, the PGW and SGW create a dedicated bearer for the PDN connection used for IMS services. The RAT type is NB-IoT (GEO), as described in Appendix F of TS 23.401, and has the following differences.

[0434] - In steps 7 and 10, the MME does not initiate a request to the eNB for UE initial context setup or bearer setup. Therefore, the data radio bearer is not activated.

[0435] - In step 13, the Create Bearer Response message from the MME may include a dummy F-TEID (e.g., 0) of the eNB for the dedicated bearer.

[0436] 2. After the Attach or PDN connection procedure, the UE in the ECM-CONNECTED state performs the IMS registration procedure through the IMS PDN connection (user plane).

[0437] 3. The eNB can trigger the S1 release procedure (e.g., due to user inactivity), and the RRC connection is released.

[0438] 4. The UE initiates a voice call to the MME using a SIP INVITE message through the control plane with CP CIoT EPS optimization.

[0439] The UE includes a SIP INVITE message in the ESM DATA TRANSPORT message within the ESM message container of the Control Plane Service Request. The UE indicates an active flag to the MME.

[0440] 5. If the S11-U connection is not established, the MME sends and receives Modify Bearer Request / Response with the SGW.

[0441] 6. The MME transmits uplink data (SIP INVITE message) from the UE through the S11-U bearer.

[0442] 7-9. Based on a Control Plane Service Request containing an active flag, the MME sends an S1-AP initial context setup request message to the eNodeB for an IMS PDN connection to enable the user plane wireless bearer and the S1-U bearer. At this time, a default bearer and a dedicated bearer can be created together.

[0443] This can be triggered by the active flag displayed by the terminal.

[0444] To create a dedicated bearer when sending an INVITE message via the user plane in Connected Mode, the terminal can include an active flag through a Control Plane Service Request.

[0445] Alternatively, when the MME activates the user plane for the IMS PDN, it can always request the activation of the dedicated bearer as well.

[0446] 10. The MME sends a Modify Bearer Request message to configure the S1-U user plane.

[0447] When the user plane wireless bearer is established, the UE uses the user plane bearer to transmit IMS signaling data.

[0448] 11. SIP 100 Trying signaling is transmitted through the primary EPS bearer (UP).

[0449] 12. P-CSCF sends an AA-Request to PCRF to activate a dedicated bearer for voice media.

[0450] 13-1. The dedicated bearer activation procedure specified in Section 5.4.1 of TS 23.401 is performed.

[0451] 13-2. If the PGW has already created a dedicated bearer in Step 1, the PGW may skip creating the dedicated bearer. The PGW decides not to enable a dedicated bearer for the PDN connection used for the IMS service that is already configured, and the RAT type is NB-IoT(GEO).

[0452] 14. PCRF responds to P-CSCF with AA-Answer.

[0453] 15. P-CSCF transmits SIP 183 progress through the basic EPS bearer (UP).

[0454] 16. The IMS voice call setup procedure continues through the basic EPS bearer (UP).

[0455] 17. IMS voice media is transmitted via a dedicated GBR EPS bearer (UP).

[0456] 18. The voice call ends.

[0457] When Step 1 and Step 13-2 are performed, even if the voice call is terminated and the PCRF receives a Session Termination Request from the IMS and transmits a Re-Auth-Request to the PGW, the PGW can maintain a dedicated bearer for the IMS PDN of the NB-IoT RAT. The MME can also maintain information about the dedicated bearer for the IMS PDN of the IoT RAT.

[0458] 19. The eNB may initiate the S1 release procedure (e.g., by user deactivation). And the RRC connection is released.

[0459] For example, the impact on services, entities, and interfaces is explained.

[0460] UE:

[0461] - Supports dedicated bearers via NB-IoT access in the GBR (Network Area).

[0462] - When a voice call is initiated in ECM-IDLE, it displays an active flag and includes an ESM message container to the MME using a control plane service request.

[0463] eNB:

[0464] - SIB displays IMS voice support via NB-IoT GEO satellite.

[0465] - Supports a dedicated bearer via NB-IoT (GEO) access to GBR.

[0466] MME:

[0467] - Displays IMS voice support via NB-IoT GEO satellite to the UE.

[0468] - Supports a dedicated bearer via NB-IoT (GEO) access to GBR.

[0469] PGW:

[0470] - Supports a dedicated bearer via NB-IoT (GEO) access to GBR.

[0471] Figures 15a and 15b show examples of IMS voice call procedures via NB-IoT (GEO) in 5GS.

[0472] 0. The GEO satellite with NB-IoT access broadcasts that the SIB supports IMS voice services via NB-IoT.

[0473] 1. The UE transmits a Registration Request to the NB-IoT (GEO) satellite with the Voice domain preference set to IMS PS Voice only and the UE usage setting set to voice centric. Additionally, the Preferred Network Behavior indicates both supported Control Plane CIoT 5GS optimization and N3 data transmission.

[0474] The AMF processes the UE's registration request. If registration is successful, it sends a registration acceptance message to the UE. The MME indicates in the supported network operation information that both control plane CIoT EPS optimization and N3 data transmission are supported. The AMF also indicates support for IMS voice over NB-IoT.

[0475] The UE establishes an IMS PDU session.

[0476] During the PDU Session creation procedure of TS 23.502 4.3.2.2.1, a dedicated QoS Flow for IMS voice may also be created. For a PDU Session for IMS Service, if the RAT type is NB-IoT (GEO), the SMF creates a dedicated QoS Flow for voice along with it. In this case, the SMF may decide not to create a data radio bearer for the dedicated QoS flow.

[0477] 2. After the IMS PDU session setup procedure, the UE in the CM-CONNECTED state performs the IMS registration procedure through the IMS PDU session (user plane).

[0478] 3. The gNB triggers the AN release procedure (e.g., due to user inactivity) and the RRC connection is released.

[0479] 4. The UE initiates a voice call to the AMF using a SIP INVITE message through the control plane with CP CIoT 5GS optimization.

[0480] The UE includes the SIP INVITE in the payload container of the Control Plane Service Request or the CIoT user data container, and indicates the PDU session ID of the IMS PDU session in the uplink data status IE for the AMF.

[0481] 5. AMF calls the Nsmf_PDUSession_SendMOData service operation to pass user data to SMF.

[0482] 6. SMF transmits uplink data (SIP INVITE message) through UPF.

[0483] 7-11. Based on a control plane service request containing the uplink data status IE for the IMS PDU session, the AMF sends an Nsmf_PDUSession_UpdateSMContext request, and the user plane wireless bearer and N3 user plane for the IMS PDU session are activated as in the existing mechanism.

[0484] The SMF creates an N3 user plane for the NB-IoT RAT's IMS PDU Session. At this time, it can simultaneously activate the default QoS Flow and the dedicated QoS Flow. This can be triggered by the AMF by displaying the IMS PDU Session in the terminal's Uplink data status IE.

[0485] To indicate the creation of a dedicated QoS Flow when sending an INVITE message via the user plane in Connected Mode, the terminal can include an IMS PDU Session in the Uplink data status IE via a Control Plane Service Request. The AMF, recognizing that a dedicated QoS flow is required for the IMS PDU Session, transmits a separate indication to the SMF (e.g., via Nsmf_PDUSession_UpdateSMContext), which can trigger the setup of the dedicated QoS flow for the N3 user plane / radio bearer.

[0486] Alternatively, when SMF activates a User Plane for an IMS PDU, it can always request the activation of a dedicated bearer along with it.

[0487] When the user plane wireless bearer is established, the UE uses the user plane to transmit IMS signaling data.

[0488] 12. SIP 100 Trying signaling is transmitted via the default QoS flow (UP).

[0489] 13. P-CSCF sends an Npcf_PolicyAuthorization request to PCF to enable a QoS flow dedicated to voice media.

[0490] 14-1. The PDU session modification procedure specified in Section 4.3.3.2 of TS 23.501 is performed.

[0491] 14-2. If a dedicated QoS Flow was created in advance in Step 1, the SMF may skip creating the dedicated QoS Flow. The SMF decides not to enable the dedicated QoS Flow for the PDU session used for the (already configured) IMS service, and the RAT type is NB-IoT(GEO).

[0492] 15. PCF sends the Npcf_PolicyAuthorization response to P-CSCF.

[0493] 16. P-CSCF conveys SIP 183 progress through the basic QoS flow (UP).

[0494] 17. The IMS voice call setup procedure continues through the basic QoS flow (UP).

[0495] 18. The voice call is terminated. If Step 1 and Step 13-2 are performed, the SMF can maintain the dedicated QoS Flow even after the voice call is terminated.

[0496] 19. The gNB can trigger the AN release procedure (e.g., due to user inactivity), and the RRC connection is released.

[0497] The above example illustrates the case where a dedicated bearer / QoS flow is used in EPS / 5GS, but it can also be used when transmitting IMS voice using the default bearer / QoS flow.

[0498] According to some embodiments of the present disclosure, when a terminal performs only signaling procedures such as IMS Registration (e.g., IP change, periodic registration, etc.) rather than voice calls in an IDLE state, it may perform these procedures using only the Control Plane without including active flag / Uplink session status IE, etc.

[0499] Alternatively, the terminal may include the Active flag / Uplink session status IE in a general Service Request message for the IMS PDN / PDU instead of a Control Plane Service Request while in the IDLE state. The MME / AMF, recognizing that it is not a voice call situation, may perform procedures such as Registration without creating a dedicated bearer / QoS flow.

[0500] When a voice call occurs in the CONNECTED state without a dedicated radio bearer, the terminal can request the creation of a dedicated bearer / QoS flow by including an active flag in a Control Plane Service Request (EPS) or by including an IMS PDU Session in the Uplink data status IE in a Control Plane Service Request (5GS).

[0501] Through this, the MME can create a radio bearer for the dedicated bearer.

[0502] Through this, the AMF can provide a separate indication to the SMF, allowing the SMF to trigger the setup of the N3 and data radio bearer for the dedicated QoS flow.

[0503] In the present disclosure, the SIP INVITE message is described as being transmitted via a Control Plane Service Request, but a new NAS message may be used to provide the SIP INVITE message and the Active flag / Uplink data status together.

[0504] According to some embodiments of the present disclosure, when receiving voice services by accessing via a GEO satellite in an EPS, the NB-IoT terminal may include an INVITE message in the ESM DATA TRANSPORT of the ESM msg container of a Control Plane Service Request message in an IDLE state and set an active flag to transmit it.

[0505] According to some embodiments of the present disclosure, when receiving voice services by accessing via a GEO satellite in 5GS, the NB-IoT terminal may include an INVITE message in the CIoT User data container or control plane user data of the Payload container of a Control Plane Service Request message in an IDLE state, and display and transmit the PDU Session ID of the IMS PDU to the Uplink data status IE.

[0506] According to some embodiments of the present disclosure, in an EPS, an MME that supports voice services through NB-IoT access includes an ESM msg container in a Control Plane Service Request message for an IMS PDN Connection received from a terminal, and if the active flag is set, transmits the User data included in the ESM msg container to the SGW through the S11 bearer.

[0507] For example, the MME can activate the User Plane of the terminal's IMS PDN Connection based on the Active flag received from the terminal.

[0508] According to some embodiments of the present disclosure, in 5GS, an AMF supporting voice services via NB-IoT access transmits the CIoT User data to an SMF using Nsmf_PDUSession_SendMOData when the CIoT User data container or control plane user data of the payload container of a Control Plane Service Request message for an IMS PDU Session from a terminal is included and the IMS PDU Session is displayed in the Uplink data status IE.

[0509] For example, the AMF can activate the User Plane of the IMS PDU Session based on the Uplink data status IE received from the terminal.

[0510] Some of the detailed steps illustrated in the examples of FIGS. 12 to 15 are not essential steps and may be omitted. In addition to the steps illustrated in FIGS. 12 to 15, other steps may be added, and the order of the steps may vary. Some of the above steps may have unique technical significance.

[0511] The present disclosure may have various effects.

[0512] According to some embodiments of the present disclosure, voice calls via satellite can be efficiently set up.

[0513] According to some embodiments of the present disclosure, when an NB-IOT UE in a CM-IDLE state provides voice service via a GEO Satellite, an invite message and an UP activation indicator can be sent as a single message. Thus, the call setup time can be reduced. Additionally, a dedicated bearer / QoS flow can be created in advance at the network level to shorten the time required to create the bearer / QoS flow during call setup.

[0514] For example, when an NB-IOT UE in the (E)CM-IDLE state provides voice services via a GEO Satellite, the NB-IOT UE can send a Service Request to the network to send an INVITE message and can avoid waiting for the time it takes to receive Service Accept from the network and enter CONNECTED mode. The NB-IOT UE can reduce the terminal's Call Setup Time by sending a Control Plane Service Request containing the INVITE message to the network and creating a User Plane for voice during the time it takes to receive a response from the other party. Additionally, by pre-creating a dedicated bearer / QoS flow at the network level, the time required to create the corresponding bearer / QoS flow during Call Setup can be reduced.

[0515] According to some embodiments of the present disclosure, a wireless communication system can efficiently initiate an IMS Voice Call via an NB-IoT GEO satellite when the UE is in an IDLE state.

[0516] The effects obtainable through the specific examples of this specification are not limited to those listed above. For example, there may be various technical effects that a person with ordinary skill in the related art can understand or derive from this specification. Accordingly, the specific effects of this specification are not limited to those explicitly described herein, but may include various effects that can be understood or derived from the technical features of this specification.

[0517] For reference, the operation of the terminal (e.g., UE) described in this specification may be implemented by the device of FIGS. 1 to 3 described above. For example, the terminal may be the first device (100) or the second device (200) of FIG. 2. For example, the operation of the terminal described in this specification may be processed by one or more processors (102 or 202). The operation of the terminal described in this specification may be stored in one or more memories (104 or 204) in the form of an instruction / program (e.g., instruction, executable code) executable by one or more processors (102 or 202). One or more processors (102 or 202) may control one or more memories (104 or 204) and one or more transceivers (105 or 206) and execute the instruction / program stored in one or more memories (104 or 204) to perform the operation of the terminal (e.g., UE) described in the disclosure of this specification.

[0518] Additionally, instructions for performing the operation of the terminal described in the disclosure of this specification may be stored in a non-volatile computer-readable storage medium. The storage medium may be included in one or more memories (104 or 204). And, the instructions recorded in the storage medium may perform the operation of the terminal described in the disclosure of this specification by being executed by one or more processors (102 or 202).

[0519] For reference, the operation of a network node (e.g., AMF, SMF, PCF, UDM, MME, etc.) or a base station (e.g., NG-RAN, gNB, RAN, eNB, (R)AN, etc.) described in this specification may be implemented by the device of FIGS. 1 to 3, which will be described below. For example, the network node or base station may be the first device (100) or the second device (200) of FIG. 2. For example, the operation of a network node or base station described in this specification may be processed by one or more processors (102 or 202). The operation of a terminal described in this specification may be stored in one or more memories (104 or 204) in the form of an instruction / program (e.g., instruction, executable code) executable by one or more processors (102 or 202). One or more processors (102 or 202) can control one or more memories (104 or 204) and one or more transceivers (106 or 206) and execute instructions / programs stored in one or more memories (104 or 204) to perform the operation of a network node or base station as described in the disclosure of this specification.

[0520] Additionally, instructions for performing the operation of a network node or base station described in the disclosure of this specification may be stored in a non-volatile (or non-transient) computer-readable storage medium. The storage medium may be contained in one or more memories (104 or 204). And, the instructions recorded in the storage medium may perform the operation of a network node or base station described in the disclosure of this specification by being executed by one or more processors (102 or 202).

[0521] Although preferred embodiments have been described by way of example above, the disclosure of this specification is not limited to such specific embodiments, and may be modified, changed, or improved in various forms within the scope of the spirit and claims of this specification.

[0522] In the exemplary system described above, methods are described based on a flowchart as a series of steps or blocks, but are not limited to the order of the described steps, and some steps may occur in a different order or simultaneously with other steps as described above. Furthermore, a person skilled in the art will understand that the steps shown in the flowchart are not exclusive, and that other steps may be included, or that one or more steps of the flowchart may be omitted without affecting the scope of rights.

[0523] The claims described in this specification may be combined in various ways. For example, the technical features of the method claims in this specification may be combined to be implemented as a device, and the technical features of the device claims in this specification may be combined to be implemented as a method. Furthermore, the technical features of the method claims and the technical features of the device claims in this specification may be combined to be implemented as a device, and the technical features of the method claims and the technical features of the device claims in this specification may be combined to be implemented as a method. Other implementations are within the scope of the following claims.

Claims

1. Regarding the method, A step of establishing a connection for an IMS (IP Multimedia Subsystem) voice service with a network node by user equipment (UE); and Characterized by including the step of transmitting a first message to the network node by the UE in the CM-Idle state, the message including (i) information related to user data and (ii) information related to user plane activation. method.

2. In claim 1, the step of establishing a connection between the network node and the IMS voice service is: For the above IMS voice service, the method is characterized by including the step of setting a dedicated bearer or a dedicated QoS Flow, excluding the user plane radio bearer between the UE and the base station. method.

3. In Paragraph 2, The above user plane wireless bearer is characterized by being set after transmitting the first message. method.

4. In Paragraph 1, Characterized by including the step of setting a dedicated bearer or a dedicated QoS Flow for the IMS voice service after transmitting the first message above. method.

5. In Paragraph 1, The above IMS voice service is characterized by being based on NB-IoT (Narrowband Internet of Things (NB-IoT)) using satellite, method.

6. In Paragraph 1, The first message is characterized as being a Control Plane Service Request message or a Non-Access-Stratum message. method.

7. In Paragraph 1, The information related to the activation of the user plane above is characterized by including an active flag for activating the user plane. method.

8. In Paragraph 1, The information related to the above user plane activation is characterized by including an uplink data status IE displaying the ID of the PDU (Protocol Data Unit) session for the above IMS voice service. method.

9. In Paragraph 1, The above first message is characterized by including an Invite message or a SIP (Session Initiation Protocol) Invite message. method.

10. In Paragraph 1, The above network node is characterized as being an MME (Mobility Management Entity) or an AMF (Access and Mobility Management Function). method.

11. In Paragraph 1, The above UE is characterized by communicating with at least one of user equipment, a network, or an autonomous vehicle other than the above UE. method.

12. Regarding the method, A step of establishing a connection for IMS voice services with user equipment (UE) by a network node; The step of receiving, by the above network node, a first message from the UE in the CM-IDLE state comprising (i) information related to user data and (ii) information related to user plane activation; and Characterized by including the step of activating a user plane by the above network node, method.

13. In claim 12, the step of establishing a connection for the IMS voice service is: The step of establishing a PDN (Packet Data Network) connection with the above UE is included, The above network node is characterized as being an MME, method.

14. In claim 13, the step of activating the user plane is, Characterized by including the step of activating a user plane for the above UE, method.

15. In claim 12, the step of establishing a connection for the IMS voice service is, The method further includes the step of establishing a PDU (Protocol Data Unit) session connection for the IMS voice service with the above UE, wherein The above network node is characterized as being an AMF, method.

16. In claim 15, the step of activating the user plane is, Characterized by including the step of activating a user plane for the PDU session for the IMS voice service. method.

17. In claim 12, the step of establishing a connection between the UE and the IMS voice service is: For the above IMS voice service, the method is characterized by including the step of setting a dedicated bearer or a dedicated QoS Flow, excluding the user plane radio bearer between the UE and the base station. method.

18. In Paragraph 17, The above user plane wireless bearer is characterized by being set after receiving the first message. method.

19. In the case of User Equipment (UE), Memory; and It includes at least one processor operably connected to the memory, wherein the at least one processor is adapted to perform at least one operation, and the at least one operation is, Step of establishing a connection between a network node and an IMS (IP Multimedia Subsystem) voice service; and Characterized by including the step of transmitting a first message to the network node in a CM-Idle state, the message including (i) information related to user data and (ii) information related to user plane activation. UE.

20. Regarding network nodes, Memory; and It includes at least one processor operably connected to the memory, wherein the at least one processor is adapted to perform at least one operation, and the at least one operation is, Step of establishing a connection between the user equipment (UE) and the IMS voice service; A step of receiving a first message from the UE in the CM-IDLE state, comprising (i) information related to user data and (ii) information related to user plane activation; and Characterized by including a step of activating a user plane, Network node.

21. In a wireless communication system, as a processor for a user device (UE), said processor is configured for said UE to perform operations, said operations are: Step of establishing a connection between a network node and an IMS (IP Multimedia Subsystem) voice service; and Characterized by including the step of transmitting a first message to the network node in a CM-Idle state, the message including (i) information related to user data and (ii) information related to user plane activation. Processor.

22. In a wireless communication system, a non-transitory computer-readable medium storing a plurality of instructions based on execution by a processor of a user device (UE), wherein the plurality of instructions are configured for the UE to perform operations, and the operations are: Step of establishing a connection between a network node and an IMS (IP Multimedia Subsystem) voice service; and Characterized by including the step of transmitting a first message to the network node in a CM-Idle state, the message including (i) information related to user data and (ii) information related to user plane activation. Non-transient computer-readable medium.

23. In a wireless communication system, as a processor for a network node, said processor is configured for said network node to perform operations, said operations are: Step of establishing a connection between the user equipment (UE) and the IMS voice service; A step of receiving a first message from the UE in the CM-IDLE state, comprising (i) information related to user data and (ii) information related to user plane activation; and Characterized by including a step of activating a user plane, Processor.

24. In a wireless communication system, a non-transitory computer-readable medium storing a plurality of instructions based on execution by a processor of a network node, wherein the plurality of instructions are configured for the network node to perform operations, and the operations are: Step of establishing a connection between the user equipment (UE) and the IMS voice service; A step of receiving a first message from the UE in the CM-IDLE state, comprising (i) information related to user data and (ii) information related to user plane activation; and Characterized by including a step of activating a user plane, Non-transient computer-readable medium.