Method and apparatus for supporting voice call through geostationary earth orbit satellite in wireless communication system

The method facilitates voice call services through NB-IoT satellite communication by negotiating satellite-based voice services and pre-allocating resources, addressing the challenge of providing voice services in areas with limited communication infrastructure.

WO2026235468A1PCT designated stage Publication Date: 2026-11-12SAMSUNG ELECTRONICS CO LTD
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
PCT/KR2026/096603
Authority / Receiving Office
WO · WO
Patent Type
Applications
Current Assignee / Owner
Priority Date
2025-05-08
Filing Date
2026-05-06
Publication Date
2026-11-12

AI Technical Summary

Technical Problem

There is a need for a method to provide voice services using NB-IoT satellite communication, particularly in areas where general communication services are not readily available, while minimizing changes to existing systems and accommodating the constraints of default EPS bearers.

Method used

A method for a terminal to transmit connection requests and negotiate satellite-based voice services, perform IMS connection procedures, and enable SIP compression, while a mobility management entity pre-allocates resources for IP multimedia subsystem services using a geostationary earth orbit satellite.

Benefits of technology

Enables efficient provision of voice call services via GEO satellites by supporting satellite-based voice services with minimal system changes, ensuring quality and connectivity in areas with limited communication infrastructure.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure KR2026096603_12112026_PF_FP_ABST
    Figure KR2026096603_12112026_PF_FP_ABST
Patent Text Reader

Abstract

The present disclosure relates to a 5G or 6G communication system for supporting higher data transmission rates. A method performed by a mobility management entity of a mobile communication system, according to an embodiment of the present disclosure, comprises the steps of: performing capability negotiation regarding whether a voice service through a non-terrestrial network (NTN) is supported, with user equipment that has accessed the NTN associated with a geostationary earth orbit (GEO) satellite; and before a voice call of the user equipment is initiated, transmitting, to a packet data network gateway (P-GW), a bearer modification request for pre-allocating resources for a bearer associated with an Internet protocol (IP) multimedia subsystem (IMS) service of the user equipment.
Need to check novelty before this filing date? Find Prior Art

Description

Method and apparatus for supporting voice calls via a geostationary satellite in a wireless communication system

[0001] The present disclosure relates to a wireless communication system. More specifically, the present disclosure relates to a method and apparatus for supporting voice calls via a Geostationary Earth Orbit (GEO) satellite.

[0002] 5G mobile communication technology defines a wide frequency band to enable fast transmission speeds and new services, and can be implemented not only in frequency bands below 6 GHz ('Sub 6 GHz'), such as 3.5 gigahertz (3.5 GHz), but also in ultra-high frequency bands called millimeter waves (mmWave), such as 28 GHz and 39 GHz ('Above 6 GHz'). In addition, for 6G mobile communication technology, which is referred to as a system beyond 5G, implementation in the terahertz band (e.g., the 3 terahertz (3 THz) band at 95 GHz) is being considered to achieve transmission speeds 50 times faster and ultra-low latency reduced to one-tenth compared to 5G mobile communication technology.

[0003] In the early stages of 5G mobile communication technology, aiming to satisfy service support and performance requirements for enhanced Mobile BroadBand (eMBB), Ultra-Reliable Low-Latency Communications (URLLC), and massive Machine-Type Communications (mMTC), technologies such as beamforming and Massive MIMO to mitigate path loss and increase transmission distance in ultra-high frequency bands, support for various numerologies (such as the operation of multiple subcarrier spacings) and dynamic operation of slot formats for the efficient utilization of ultra-high frequency resources, initial access techniques to support multi-beam transmission and broadband, definition and operation of Band-Width Parts (BWP), Low Density Parity Check (LDPC) codes for high-volume data transmission, new channel coding methods such as Polar Codes for the reliable transmission of control information, and L2 pre-processing (L2 Standardization has been carried out for pre-processing, network slicing which provides a dedicated network specialized for specific services, and other methods.

[0004] Currently, discussions are underway to improve and enhance the performance of the initial 5G mobile communication technology, taking into account the services that the 5G mobile communication technology was intended to support. Additionally, standardization of the physical layer is in progress for technologies such as V2X (Vehicle-to-Everything), which helps autonomous vehicles make driving decisions and enhance user convenience based on their own location and status information transmitted by the vehicle; NR-U (New Radio Unlicensed), which aims for system operation in unlicensed bands to comply with various regulatory requirements; NR terminal low power consumption technology (UE Power Saving); Non-Terrestrial Network (NTN), which is direct terminal-satellite communication for securing coverage in areas where communication with the terrestrial network is impossible; and positioning.

[0005] In addition, standardization is underway in the field of wireless interface architecture / protocols for technologies such as the Industrial Internet of Things (IIoT) for supporting new services through linkage and convergence with other industries, Integrated Access and Backhaul (IAB) which provides nodes for expanding network service areas by integrating wireless backhaul links and access links, Mobility Enhancement including Conditional Handover and Dual Active Protocol Stack (DAPS) Handover, and 2-step Random Access (2-step RACH for NR) which simplifies random access procedures. Standardization is also underway in the field of system architecture / services for 5G baseline architectures (e.g., Service based Architecture, Service based Interface) for incorporating Network Functions Virtualization (NFV) and Software-Defined Networking (SDN) technologies, and Mobile Edge Computing (MEC), which provides services based on the location of the terminal.

[0006] When such 5G mobile communication systems are commercialized, connected devices, which are increasing explosively, will be connected to communication networks. Accordingly, it is expected that there will be a need to enhance the functionality and performance of 5G mobile communication systems and to integrate the operation of connected devices. To this end, new research is planned to be conducted on 5G performance improvement and complexity reduction, support for AI services, support for metaverse services, and drone communication using eXtended Reality (XR), Artificial Intelligence (AI), and Machine Learning (ML) to efficiently support Augmented Reality (AR), Virtual Reality (VR), and Mixed Reality (MR).

[0007] Furthermore, the advancement of these 5G mobile communication systems encompasses multi-antenna transmission technologies such as new waveforms to guarantee coverage in the terahertz band of 6G mobile communication technology, Full Dimensional MIMO (FD-MIMO), array antennas, and large-scale antennas; metamaterial-based lenses and antennas to improve terahertz band signal coverage; high-dimensional spatial multiplexing technology using OAM (Orbital Angular Momentum); and Reconfigurable Intelligent Surface (RIS) technology; as well as Full Duplex technology for enhancing frequency efficiency and system networks in 6G mobile communication technology; AI-based communication technologies that realize system optimization by utilizing satellites and AI from the design stage and internalizing end-to-end AI support functions; and the realization of services of complexity exceeding the limits of terminal computing capabilities by utilizing ultra-high-performance communication and computing resources. It could serve as a foundation for the development of next-generation distributed computing technologies.

[0008] In wireless communication systems accessed via GEO satellites, communication with the ground is conducted through satellites located 35,786 km above the ground. Consequently, the signaling delay with the ground is approximately 285 ms, and the bandwidth may be limited due to factors such as signal attenuation caused by atmospheric conditions. However, compared to other satellite communications, it has the advantage of providing communication services using fewer satellites due to its wider coverage. Utilizing this characteristic, GEO satellites can be used to provide communication services that use small amounts of data, such as NB-IoT (Narrowband Internet of Things).

[0009] For example, there is a growing need for a method to enable a user to access a communication system and use voice services by utilizing NB-IoT satellite Geo communication (e.g., NB-IoT(Geo) access) in situations where general communication services are not readily available, such as in a desert. In particular, there is a need to provide voice services that offer at least minimal quality by minimizing changes to existing NB-IoT systems and / or EPS (evolved packet system) and / or IMS (IP multimedia subsystem).

[0010] In particular, in the case of the above NB-IoT system, the terminal can configure up to two DRBs (data radio bearers) and can configure only a default EPS bearer instead of a dedicated EPS bearer. In addition, voice services must be provided while accommodating as much as possible the constraint that the default EPS bearer must support a non-GBR bearer rather than a GBR (Guaranteed Bit Rate) bearer.

[0011] Accordingly, the present disclosure proposes a method for smoothly providing voice call services when a terminal connects to an EPS via NB-IoT (Geo) access.

[0012] Although the present disclosure describes the method based on a 4G communication system (e.g., EPS), it is applicable not only when connecting to a 5G communication system (e.g., 5GS) via NB-IoT (Geo) access, but also in the same way applicable to future 6G and subsequent communication systems.

[0013] According to one embodiment of the present disclosure, a method is provided to be performed by a terminal of a wireless communication system. The method comprises: transmitting a connection request message to a first network entity that includes information on whether the terminal supports a satellite-based voice service; receiving a connection response message from the first network entity that includes information on whether the first network entity supports the satellite-based voice service; if the satellite-based voice service is supported by the terminal and the first network entity, transmitting a connection creation request message to the first network entity for an IMS (Internet Protocol Multimedia Subsystem) service; receiving a connection creation response message from the first network entity that includes information on a bearer created for the IMS service; performing an IMS connection procedure based on the bearer and enabling SIP (Session Initiation Protocol) compression; and transmitting a first SIP message to a second network entity that includes traffic-related information for the satellite-based voice service. The method includes the step of receiving a second SIP message from the second network entity in response to the first SIP message; and the step of transmitting and receiving data of the satellite-based voice service based on the bearer.

[0014] According to one embodiment of the present disclosure, a method is provided to be performed by a mobility management entity of a mobile communication system. The method comprises: a step of performing capability negotiation with a terminal connected to a non-terrestrial network (NTN) associated with a geostationary earth orbit (GEO) satellite regarding whether voice services through said NTN are supported; and a step of transmitting a bearer modification request to a packet data network gateway (P-GW) to pre-allocate resources for a bearer associated with an IP (internet protocol) multimedia subsystem (IMS) service of said terminal before a voice call of said terminal is initiated.

[0015] According to one embodiment of the present disclosure, a method is provided to be performed by a proxy-call session control function (P-CSCF) of a mobile communication system. The method comprises: receiving an IMS (Internet Protocol Multimedia Subsystem) registration request message from a terminal connected to a non-terrestrial network (NTN) associated with a geostationary earth orbit (GEO) satellite; transmitting a registration response message to the terminal, the message including address information or fully qualified domain name (FQDN) information of an IMS-AGW (IMS access gateway) determined based on access type information included in the IMS registration request message; setting the IMS-AGW to perform voice codec transcoding of the voice call in response to receiving a session description protocol (SDP) answer message for a voice call requested by the terminal; and transmitting a Diameter authorization authentication request (AAR) message requesting resource reservation for the voice call to a policy control entity.

[0016] According to one embodiment of the present disclosure, a mobility management entity of a mobile communication system is provided. The mobility management entity comprises: at least one transceiver; at least one processor connected to communicate with the at least one transceiver; and a memory connected to communicate with the at least one processor and storing instructions that are executable individually or in any combination of the at least one processor. The instructions cause the mobility management entity to perform capability negotiation regarding whether voice services over the NTN are supported with a terminal connected to a geostationary earth orbit (GEO) satellite and to transmit a bearer modification request to a packet data network gateway (P-GW) to pre-allocate resources for a bearer associated with an IP (internet protocol) multimedia subsystem (IMS) service of the terminal before the voice call of the terminal is initiated.

[0017] According to one embodiment of the present disclosure, a proxy-call session control function (P-CSCF) of a mobile communication system is provided. The P-CSCF comprises at least one transceiver; at least one processor connected to communicate with the at least one transceiver; and a memory connected to communicate with the at least one processor and storing instructions that are executable by the at least one processor individually or in any combination thereof. The above command causes the P-CSCF to receive an IMS (Internet Protocol Multimedia Subsystem) registration request message from a terminal connected to a non-terrestrial network (NTN) associated with a geostationary earth orbit (GEO) satellite, transmit a registration response message to the terminal containing address information or fully qualified domain name (FQDN) information of an IMS-AGW (IMS access gateway) determined based on access type information included in the IMS registration request message, and, in response to receiving a session description protocol (SDP) answer message for a voice call requested by the terminal, to configure the IMS-AGW to perform voice codec transcoding for the voice call and to transmit a Diameter AAR (authorization authentication request) message requesting resource reservation for the voice call to a policy control entity.

[0018] According to various embodiments of the present disclosure, voice call services can be efficiently provided in a wireless communication system connected via a GEO satellite.

[0019] FIG. 1 illustrates the structure of a wireless communication system according to one embodiment of the present disclosure.

[0020] FIG. 2a illustrates a procedure in which a terminal connects to a communication network and a voice call service is provided using a control plane in a wireless communication system according to one embodiment of the present disclosure.

[0021] FIG. 2b illustrates a procedure in which a terminal connects to a communication network and a voice call service is provided using a control plane in a wireless communication system according to one embodiment of the present disclosure.

[0022] FIG. 3a illustrates a procedure in which a terminal connects to a communication network and a voice call service is provided using a user plane in a wireless communication system according to one embodiment of the present disclosure.

[0023] FIG. 3b illustrates a procedure in which a terminal connects to a communication network and a voice call service is provided using a user plane in a wireless communication system according to one embodiment of the present disclosure.

[0024] FIG. 4a illustrates a procedure in which a terminal connects to a communication network and a voice call service is provided using a control plane and a user plane in a wireless communication system according to one embodiment of the present disclosure.

[0025] FIG. 4b illustrates a procedure in which a terminal connects to a communication network and a voice call service is provided using a control plane and a user plane in a wireless communication system according to one embodiment of the present disclosure.

[0026] FIG. 5 is a block diagram of a terminal or user device according to one embodiment of the present disclosure.

[0027] FIG. 6 is a block diagram of a base station according to one embodiment of the present disclosure.

[0028] FIG. 7 is a block diagram of a network entity performing network functions according to one embodiment of the present disclosure.

[0029] Hereinafter, embodiments of the present disclosure will be described in detail with reference to the attached drawings.

[0030] In describing the embodiments, technical details that are well known in the art to which this disclosure belongs and are not directly related to this disclosure are omitted. This is intended to convey the essence of this disclosure more clearly without obscuring it by omitting unnecessary explanations.

[0031] For the same reason, some components in the attached drawings have been exaggerated, omitted, or schematically depicted. Additionally, the size of each component does not entirely reflect its actual dimensions. Identical or corresponding components in each drawing have been assigned the same or different reference numbers.

[0032] The advantages and features of the present disclosure, and the methods for achieving them, will become clear by referring to the embodiments described below in detail together with the accompanying drawings. However, the present disclosure is not limited to the embodiments disclosed below but may be implemented in various different forms. These embodiments are provided merely to ensure that the disclosure is complete and to fully inform those skilled in the art of the scope of the disclosure, and the present disclosure is defined only by the scope of the claims. Throughout the specification, the same reference numerals refer to the same components. Furthermore, in describing the present disclosure, if it is determined that a detailed description of a related function or configuration might unnecessarily obscure the essence of the present disclosure, such detailed description is omitted. Additionally, the terms described below are defined considering their functions in the present disclosure, and these may vary depending on the intentions or conventions of the user or operator. Therefore, their definitions should be based on the content throughout the specification.

[0033] In the present disclosure, it will be understood that each block of the process flow diagrams and combinations of the flow diagrams may be performed based on computer program instructions. Since these computer program instructions may be optionally loaded into at least one processor of a general-purpose computer, a computer for special purposes, or other programmable data processing equipment, the instructions performed through any one or any combination of at least one processor of the computer or other programmable data processing equipment create means for performing the functions described in the flow diagram block(s). Since these computer program instructions may also be stored in computer-available or computer-readable memory that can be directed toward the computer or other programmable data processing equipment to implement the functions in a specific manner, the instructions stored in computer-available or computer-readable memory may also produce a manufactured item containing means of instruction for performing the functions described in the flow diagram block(s). Since computer program instructions can be loaded onto a computer or other programmable data processing equipment, instructions that perform a series of operation steps on the computer or other programmable data processing equipment to create a process executed by the computer can also provide steps for executing the functions described in the flowchart block(s).

[0034] Additionally, each block may represent a module, segment, or part of code containing one or more executable instructions for executing a specified logical function(s). It should also be noted that in some alternative execution examples, the functions mentioned in the blocks may occur out of order. For example, two blocks (or functions) described in succession may actually be executed substantially simultaneously, or the blocks may sometimes be executed in reverse order according to the corresponding function.

[0035] As used in the embodiments of the present disclosure, the term “part” refers to a software or hardware component, such as a field programmable gate array (FPGA) or an application-specific integrated circuit (ASIC), and the “part” performs certain roles. However, the term including “part” is not limited to software or hardware. The “part” may be configured to reside in an addressable storage medium or may be configured to run on one or more processors. Thus, by example, the “part” includes components such as software components, object-oriented software components, class components, and task components, as well as processes, functions, attributes, procedures, subroutines, segments of program code, drivers, firmware, microcode, circuits, data, databases, data structures, tables, arrays, and variables. The functions provided within the components and “parts” may be combined into a smaller number of components and “parts” or further separated into additional components and “parts.” In addition, the components and 'parts' may be implemented to utilize one or more CPUs (central processing units) within the device or secure multimedia card. Also, in the embodiments, 'parts' may include one or more processors.

[0036] As stated above, it should be noted that the blocks of each flowchart and combinations of flowcharts described in this disclosure may be executed by one or more computer programs including instructions. The entirety of one or more computer programs may be stored in a single memory device, or one or more computer programs may be divided into different parts and stored across multiple memory devices.

[0037] Additionally, any / any function or operation described in this disclosure may be processed by a single processor or a combination of processors. The single processor or combination of processors is a circuitry that performs processing and may include an application processor (AP, e.g., a central processing unit (CPU)), a communication processor (CP, e.g., a modem), a graphics processing unit (GPU), a neural network processing unit (NPU) (e.g., an artificial intelligence (AI) chip), a Wi-Fi chip, a Bluetooth® chip, a global positioning system (GPS) chip, a near-field communication (NFC) chip, a connectivity chip, a sensor controller, a touch controller, a fingerprint sensor controller, a display driver integrated circuit (IC), an audio codec (CODEC) chip, a universal serial bus (USB) controller, a camera controller, an image processing IC, a microprocessor unit (MPU), a system-on-chip (SoC), an IC, or similar circuitry.

[0038] Additionally, it should be noted that various embodiments in the claims and description of the present disclosure may be implemented in the form of hardware, software, or a combination of hardware and software.

[0039] Such software may be stored on a non-transitory computer-readable storage medium. A non-transitory computer-readable storage medium stores one or more computer programs (software modules), and said one or more computer programs include computer-executable instructions that operate an electronic device to perform a method according to the present disclosure when executed alone or collectively by one or more processors of an electronic device.

[0040] The software may be stored in a transient or non-transient storage device, for example, in the form of read-only memory (ROM) (whether or not it is erasable or rewritable), or random access memory (RAM), memory chips, devices, or integrated circuits (ICs). Additionally, the software may be stored in the form of an optically or magnetically readable medium, for example, a compact disc (CD), a digital multifunction disc (DVD), a magnetic disc, or a magnetic tape. It should be understood that the storage device and the storage medium are examples of non-transient machine-readable storage media suitable for storing programs for implementing various embodiments of the present disclosure. Accordingly, various embodiments of the present disclosure may provide a program containing code for implementing a device or method according to any one of the claims of this specification, and a non-transient machine-readable storage medium storing such program.

[0041] In the following disclosure, determining the priority between A and B may be referred to in various ways, such as selecting the one with the higher priority according to a predetermined priority rule and performing the corresponding action, or omitting or dropping the action for the one with the lower priority.

[0042] Hereinafter, 'A or B' as described in the present disclosure may be understood as 'A and / or B', which may be understood as including 'A', or 'B', or 'A and B'.

[0043] Additionally, 'at least one of A, B, and C' described in the present disclosure may be understood to include 'A', or 'B', or 'C', or 'any combination of A, B, and C'.

[0044] Additionally, 'at least one of A, B, or C' described in the present disclosure may be understood to include 'A', or 'B', or 'C', or 'any combination of A, B, and C'.

[0045] Additionally, 'A / B' as described in the present disclosure may be understood as 'A and / or B', which may be understood as including 'A', or 'B', or 'A and B'.

[0046] Additionally, 'A, B' described in the present disclosure may be understood as 'A and / or B', which may be understood as including 'A', or 'B', or 'A and B'.

[0047] Additionally, 'A and B' described in the present disclosure may be understood as 'A and / or B', which may be understood as including 'A', or 'B', or 'A and B'.

[0048] Furthermore, the phrase "when conditions A and B are satisfied" as described in the present disclosure is not necessarily limited to cases where both conditions A and B are satisfied, but may be understood to include cases where either condition A or condition B is satisfied individually, cases where both conditions A and B are satisfied, or cases where one or more additional conditions are satisfied together.

[0049] Furthermore, throughout this specification, ordinal terms (and similar modifiers) such as 'first', 'second', 'third', etc. are used solely for the purpose of distinguishing various instances, occurrences, configurations, messages, stages, or aspects of elements, operations, or information, as described below. Unless clearly required otherwise by the context, the use of such ordinal terms does not require that the elements, operations, or information distinguished by such terms be structurally different, numerically distinct, or essentially different. For example, 'first signal' and 'second signal' may represent instances of the same signal transmitted at different times, signals containing the same core information even with some variations, or signals having different content or characteristics depending on the specific context. Similarly, 'first value' and 'second value' may represent the same magnitude measured or applied in different situations, or may represent different magnitudes. Such interpretation must be determined based on the specific technical context, function, and relationship described in the relevant parts of the specification and claims.

[0050] Furthermore, although terms such as "first," "second," etc., as used in this disclosure are used for various elements such as information, objects, actions, and sequences, they are not intended to limit such elements to a specific order. These terms may be understood merely as distinguishing one element from another. For example, a first element may be referred to as a second element, and likewise, a second element may be referred to as a first element.

[0051] Additionally, the terms 'first' and 'second' described in this disclosure may be understood to refer to identical or different elements. For example, if an element is information, the first information and the second information may both be information, and depending on the case, they may be the same information or different information.

[0052] Furthermore, the expressions 'if' and 'in case that' described in this disclosure or claims may be interpreted, depending on the context, as meaning 'when or upon,' 'in response to,' 'based on,' or 'according to,' and these expressions may be used interchangeably. In addition, other expressions having substantially the same meaning may be used as substitutes, provided that they do not impair the technical features of this disclosure.

[0053] Additionally, the term "not perform" as used in this disclosure or claims may be understood, depending on the context, to mean to omit or skip the corresponding step. Such a term may be replaced with other terms having the same or substantially similar meaning.

[0054] Additionally, the phrase "transmitting a message containing A and B" as described in this specification may be interpreted to include not only (i) cases where A and B are transmitted as a single message, but also (ii) cases where A and B are transmitted individually through multiple messages (e.g., transmitting a first message containing A and a second message containing B). This interpretation may also apply to cases where messages containing two or more items, such as A, B, and C, are transmitted together or individually.

[0055] In addition, 'transmitting a message containing A and transmitting a message containing B' can also be interpreted as transmitting a single message containing A and B.

[0056] In the specific embodiments of the present disclosure described below, terms or components included in the disclosure will be expressed in the singular or plural form according to the specific embodiments presented. However, the singular or plural expression is selected to suit the circumstances presented for convenience of explanation, and the present disclosure is not limited to singular or plural components; even if a component is expressed in the plural form, it may be composed in the singular form, and even if a component is expressed in the singular form, it may be composed in the plural form.

[0057] The drawings or flowcharts described below illustrate exemplary methods that may be implemented in accordance with the principles of the present disclosure, and various modifications may be made to the methods illustrated in the flowcharts of the present disclosure. For example, although illustrated as a series of steps, the various steps of each drawing or flowchart may overlap, occur in parallel, occur in a different order, or occur multiple times. In other examples, any step may be omitted or replaced with another step.

[0058] The methods and devices proposed in the embodiments of the present disclosure below are not limited to each embodiment and may be utilized as a combination of all or part of the embodiments proposed in the disclosure. Accordingly, the embodiments of the present disclosure may be applied with some modifications within the scope that does not deviate significantly from the scope of the present disclosure, at the judgment of a person skilled in the art.

[0059] In this case, any wording mentioned in different embodiments may be used interchangeably, combined, or substituted if the concepts correspond. For example, regarding the same or corresponding concepts, even if the expression 'A' is used in one embodiment and the expression 'B' is used in another embodiment, they may be understood by interchangeably, substituted, or combined.

[0060] Terms used in the following description to identify connection nodes, terms referring to network entities, terms referring to messages, terms referring to interfaces between network entities, terms referring to various identification information, etc., are examples provided for the convenience of explanation. Accordingly, the present disclosure is not limited to the terms described below, and other terms referring to objects having equivalent technical meanings may be used. Furthermore, where appropriate, such terms may be replaced with terms defined in the 3GPP (3rd generation partnership project) Technical Specifications (TS).

[0061] Hereinafter, the base station, as the entity performing resource allocation for terminals, may be at least one of gNode B, eNode B, Node B, BS (base station), wireless access unit, base station controller, or a node on a network. Additionally, the base station of the present disclosure may include a structure split into a central unit (CU) and a distributed unit (DU). In such a structure, the CU is responsible for the upper layer of the control and user plane, and the DU is responsible for wireless resource processing of the lower layer. The embodiments of the present disclosure can be equally applied to a 5G base station structure in which functions are separated into the CU and DU as described above.

[0062] The terminal may include a UE (user equipment), MS (mobile station), cellular phone, smartphone, computer, or a multimedia system capable of performing communication functions.

[0063] In the present disclosure, a downlink (DL) refers to a wireless transmission path of a signal transmitted by a base station to a terminal, and an uplink (UL) refers to a wireless transmission path of a signal transmitted by a terminal to a base station.

[0064] In addition, while a 5th generation mobile communication system (5G, new radio, NR) and a 6th generation mobile communication system (6G) may be described below as examples, embodiments of the present disclosure may also be applied to other communication systems having similar technical backgrounds or channel types. For example, new advanced mobile communication systems developed after 5G and 6G may be included therein. Furthermore, the present disclosure may be applied to other communication systems (e.g., Wi-Fi systems) with some modifications made in the judgment of a person with skilled technical knowledge, without significantly departing from the scope of the present disclosure.

[0065] In the following description, the terms "physical channel" and "signal" may be used interchangeably with "data" or "control signal." For example, PDSCH (physical downlink shared channel) is a term referring to a physical channel through which data is transmitted, but PDSCH may also be used to refer to data. That is, in this disclosure, the expression "transmits a physical channel" may be interpreted as equivalent to the expression "transmits data or a signal through a physical channel."

[0066] In describing the present disclosure below, the term "upper layer signaling" may be a signaling corresponding to at least one or a combination of at least one of MIB (master information block), SIB (system information block), SIB M (M=1, 2, …), RRC (radio resource control), MAC (medium access control), CE (control element), NAS (non-access stratum) signaling, or application layer messages. The RRC signaling may also be referred to as L3 signaling (layer 3 signaling).

[0067] Additionally, L1 signaling may be a signaling method corresponding to at least one or a combination of at least one of the following: a physical layer channel or signaling of a PDCCH (physical downlink control channel), a DCI (downlink control information), a UE-specific DCI, a group common DCI, a common DCI, a scheduling DCI (e.g., a DCI used for the purpose of scheduling downlink or uplink data), a non-scheduling DCI (e.g., a DCI not used for the purpose of scheduling downlink or uplink data), a PUCCH (physical uplink control channel), or an UCI (uplink control information). The above L1 signaling may also be referred to as physical layer signaling.

[0068] Hereinafter, the expression in the present disclosure or claims that information can be configured from a base station may mean that, depending on the context, a terminal receives said information from a base station through physical layer signaling or upper layer signaling, and such expression may be replaced with other terms having the same or substantially similar meaning.

[0069] The operating principle of the present disclosure will be explained in detail below with reference to the attached drawings.

[0070] FIG. 1 illustrates the structure of a wireless communication system according to one embodiment of the present disclosure.

[0071] Referring to FIG. 1, in a wireless communication system, a terminal connects to an EPS (Evolved Packet System) network through access for NB-IoT services (e.g., NB-IoT NTN (Geo)) to obtain IP (Internet Protocol) connectivity, and through this, can connect to an IMS (IP multimedia subsystem).

[0072] The network technology used in the various embodiments of the present disclosure may refer to standard specifications defined by the ITU (International Telecommunication Union) or 3GPP (e.g., TS 23.401, TS 23.501, TS 23.502, TS 23.503, etc.), and the components included in the network structure of FIG. 1 may each refer to a physical entity, or to software that performs an individual function, or to hardware combined with software. Hereinafter, the components included in the network structure of FIG. 1 will be referred to as NF (network functions).

[0073] Interfaces announced in the 4G core network (Evolved Packet Core, EPC) can be used between NFs, and since a detailed description can be found in the standard specification (TS 23.401), a detailed description will be omitted.

[0074] In addition, for 5G communication, interfaces disclosed in the 5G Core Network (5G Core, 5GC) can be used between NFs, and since a detailed explanation can be found in the standard specification (TS 23.501), a detailed explanation will be omitted.

[0075] The wireless communication system of FIG. 1 may include an NB-IoT NTN (Geo) satellite, an eNB, and an EPC. The eNB is a base station that supports wireless access technology in a 4G system, and a terminal can connect to the eNB through an NB-IoT NTN (Geo), which is a Geo satellite that supports NB-IoT, and a ground satellite central office (e.g., an NTN gateway).

[0076] In the embodiments of the present disclosure below, the terminal can be connected to an eNB via an NB-IoT NTN (Geo) as in FIG. 1 and perform communication mediated by a 4G system, and in particular, can receive voice services using IMS.

[0077] In Figure 1, the 4G core network (EPC) may include entities such as the Mobility Management Entity (MME), Serving Gateway (S-GW), Packet Data Network Gateway (P-GW), and Policy and Charging Rules Function (PCRF).

[0078] The eNB serves as a RAN (Radio Access Network) node and can correspond to the RNC (Radio Network Controller) of a UTRAN (Universal Terrestrial Radio Access Network) system and the BSC (Base Station Controller) of a GERAN (GSM EDGE Radio Access Network) system. The eNB is connected to the UE via a wireless channel and can perform roles similar to existing RNCs / BSCs, and can also operate multiple cells simultaneously. In 4G, since all user traffic is serviced through a shared channel, a device is required to collect status information from UEs and perform scheduling, and the eNB is responsible for this task.

[0079] An MME is a device responsible for various control functions, and a single MME can be connected to multiple base stations.

[0080] The S-GW is a device that provides data bearers and can create or remove bearers under the control of the MME.

[0081] PCRF is a device that controls policies related to the user's Quality of Service (QoS) and / or billing, and PCC (Policy and Charging Control) rules corresponding to the policy can be transmitted to and applied to the P-GW.

[0082] Generally, UP (User Plane) refers to the path connecting the UE, where user data is transmitted and received, the RAN node eNB, the ENB, the S-GW, and the S-GW, and the P-GW.

[0083] In wireless communication systems such as EPS, the unit to which QoS can be applied is the EPS bearer. A single EPS bearer can be used to transmit IP flows with the same QoS requirements. QoS-related parameters may be assigned to the EPS bearer, which may include a Quality of Service Class Identifier (QCI) and / or Allocation and Retention Priority (ARP). The QCI is a parameter that defines the QoS priority as an integer value, and the ARP is a parameter used to determine whether to allow or deny the creation of a new EPS bearer.

[0084] An EPS bearer can correspond to a Packet Data Protocol (PDP) context of a General Packet Radio Service (GPRS) system. An EPS bearer belongs to a Packet Data Network (PDN) connection, and a PDN connection can have an Access Point Name (APN) as an attribute. If a PDN connection is established for IP Multimedia Subsystem (IMS) services, that PDN connection may need to be established using a well-known IMS APN.

[0085] Meanwhile, although an EPC is illustrated as an example in this drawing, various embodiments of the present disclosure may be similarly applied to 5GC, 6G, or systems after 6G. For example, if the wireless communication system is 5GC, it may include network entities such as an Access and Mobility Management Function (AMF), a Session Management Function (SMF), a User Plane Function (UPF), a Policy Control Function (PCF), a Unified Data Management (UDM), and a Unified Data Repository (UDR).

[0086] An AMF is an entity for managing the access and mobility of a terminal. An AMF can serve as a terminal-core network endpoint through which a terminal connects with other entity(s) of the 5GC via the NG-RAN. For example, an AMF can perform network functions such as terminal registration, connection, reachability, mobility management, connection verification, authentication, and the generation of mobility events.

[0087] The SMF can perform management functions for the Protocol Data Unit (PDU) sessions of the terminal. For example, the SMF can perform network functions such as session management functions through the establishment, modification, and release of sessions and the maintenance of tunnels between the UPF and NG-RAN required for this, IP address allocation and management functions for the terminal, selection and control of the User Plane, control of traffic processing in the UPF, and control of billing data collection.

[0088] The UPF can perform the function of processing user data from the terminal. The UPF can perform data processing functions to transmit data generated by the terminal outside the network, for example, to an Application Function, a P-CSCF (Proxy Call Session Control Function), an Application Server, or an IMS-AGW, or to transmit data received from the aforementioned entities to the terminal. For example, the UPF can perform network functions such as acting as an anchor between Radio Access Technologies (RATs), providing connections between PDU sessions and Application Functions, P-CSCFs, Application Servers, or IMS-AGWs (IMS Access Gateways), packet routing and forwarding, packet inspection, application of user plane policies, generation of traffic usage reports, and buffering.

[0089] PCF can manage operator policy information for providing services in a 5G system. UDR stores terminal subscription information and can provide the stored subscription information to UDM. Additionally, UDR stores operator policy information and can provide the stored operator policy information to PCF.

[0090] Accordingly, the terminal registration and mobility management functions of the MME in the above 4G network can be performed similarly to the AMF, the session management functions of the MME and the control plane-related functions of the S-GW and P-GW can be performed similarly to the SMF, and the user plane-related functions of the P-GW can be performed similarly to the UPF. In addition, the functions of the PCRF can be performed similarly to the PCF, and the PDN connection can correspond to the PDU Session.

[0091] FIGS. 2a and 2b illustrate a procedure in which a terminal connects to a communication network and a voice call service is provided using a control plane in a wireless communication system according to one embodiment of the present disclosure.

[0092] This diagram describes, for example, the procedure for a terminal to connect to an EPS network via an NB-IoT NTN (Geo) satellite and use an IMS voice service.

[0093] Referring to FIGS. 2a and 2b, when a terminal (UE-1) receives a broadcast message from an NB-IoT NTN (Geo) satellite announcing the existence of an NB-IoT (Geo) network, the terminal may attempt to connect to the network. The broadcast message may include an indicator indicating that voice services are available through the NB-IoT satellite network or the NB-IoT (Geo) network.

[0094] In step 201a, the terminal connects to the network and informs the MME of the EPS network during the attach request process that it can receive voice services via NB-IoT NTN (Geo), and the MME may inform the terminal whether it can provide voice services via NB-IoT NTN (Geo) using a response message to the attach request. In the case of a 5G network, if the terminal informs during the registration process that it can provide voice services via NB-IoT NTN (Geo), the AMF may inform the terminal whether the network supports the corresponding function using a response message to the registration request.

[0095] Meanwhile, the terminal can negotiate with the MME or AMF during the attach or registration process whether NB-IoT functions are provided or supported. Alternatively, the terminal and the MME or AMF can negotiate during the attach or registration process whether Control plane CIoT (Cellular Internet-of-Things) optimization functions and / or User plane CIoT optimization functions are supported. Here, the Control plane CIoT 5GS optimization function is used to exchange user data in the uplink / downlink direction as the payload of NAS messages, and resources can be saved by not establishing a user plane connection for the PDU session. Additionally, through the User plane CIoT 5GS optimization function, the terminal can transmit user plane data in CM-IDLE without using the service request procedure.

[0096] The voice service support function through NB-IoT NTN (Geo) can be indicated by (1) a direct indicator such as a Geo voice capability indication, (2) a combination of an IMS voice over PS session supported indication and the fact that the terminal is camping on NB-IoT NTN (Geo) or NB-IoT (Geo), or (3) a combination of a Voice domain preference and UE's usage setting (= voice centric and IMS PS Voice only) and the fact that the terminal is camping on NB-IoT NTN (Geo) or NB-IoT (Geo).

[0097] In step 201b, when the terminal attaches to the communication network, it can create a PDN connection (or PDU Session) to receive IMS services. For example, when the terminal transmits a request to create a PDN connection, it may include an APN value for IMS services, and when the request to create a PDN connection is transmitted to the P-GW, a PDN connection and a default EPS bearer for IMS services are created, and this fact may be transmitted to the terminal along with a response to the request to create a PDN connection.

[0098] In step 201c, the terminal can perform IMS registration using the generated bearer. At this time, the terminal that has negotiated the voice service function via the NB-IoT NTN (Geo) can include in the IMS registration message the access type in the P-CSCF by setting the P-Access-Network-Info header field of the IMS registration message to “3GPP-NB-IoT (GEO)” or “3GPP-NB-IoT NTN (GEO)” and configuring SIP compression to be enabled (see 3GPP TS 24.229).

[0099] In addition, at step 201c, the P-CSCF may include address information or FQDN (Fully Qualified Domain Name) information of an IMS-AGW (access gateway) that performs / manages the IMS-ALG (access level gateway) function in the registration response message and transmit it to the terminal.

[0100] The address information or FQDN information of the above IMS-AGW may be provided by referring to the IMS-AGW assigned to “3GPP-NB-IoT(GEO)” based on the P-Access-Network-Info header field of the IMS registration message transmitted by the terminal.

[0101] In step 201b, (1) address information or FQDN information of a P-CSCF set in a PCRF or P-GW for an APN for IMS and / or (2) address information or FQDN information of an IMS-AGW (access gateway) may be stored in the P-GW or included in a response message to the request to create a PDN connection and transmitted to the terminal. This information may be provided to the terminal based on the fact that the terminal has connected to the network through an NB-IoT NTN (Geo) and has the ability to provide voice services through an NB-IoT NTN (Geo).

[0102] Meanwhile, in the case of a terminal that has negotiated a voice service support function through NB-IoT NTN (Geo) as in step 201a, the process of allocating resources to the bearer may be performed in advance before and after the IMS registration in step 201c, and before the Geo Voice call occurs in step 201d.

[0103] For example, for a terminal that has negotiated a voice service support function through NB-IoT NTN (Geo), if the P-GW obtains the address information of the P-CSCF and / or the address information of the IMS-AGW for the IMS APN through the above process before or after performing IMS registration, the P-GW can provide data for the voice service (or 'Geo Voice service', hereinafter used interchangeably) through the NB-IoT NTN (Geo) with sufficient QoS using the default EPS bearer. In addition, the P-GW may pre-allocate resources for the bearer before a Geo Voice call occurs by performing a bearer modification process for the terminal's default EPS bearer for IMS to update QoS information (e.g., QCI value or Geo voice-specific QCI value) and / or packet filters (e.g., TFT (Traffic Flow Template) information) so that the data can be forwarded to and received from the IMS-AGW.

[0104] In another way, if a terminal that has negotiated a voice service support function via NB-IoT NTN (Geo) obtains the address information of the P-CSCF and / or the address information of the IMS-AGW for the IMS APN through the above process before or after IMS registration, the terminal can receive data for the voice service via NB-IoT NTN (Geo) (or 'Geo Voice service', hereinafter used interchangeably) with sufficient QoS using the default EPS bearer. In addition, the terminal may pre-allocate resources for the bearer before a Geo Voice call occurs by sending a bearer modification request for the terminal's default EPS bearer for IMS to the P-GW (via MME) to update QoS information (e.g., QCI value or Geo voice-specific QCI value) and / or packet filters (e.g., TFT information) so that the data can be properly forwarded to and received from the IMS-AGW.

[0105] Meanwhile, if the terminal and the MME negotiate regarding the CIoT optimization function in step 201a and the application of Control plane CIoT optimization is possible, the terminal may not generate a DRB for the default EPS bearer and instead use a signaling radio bearer (SRB). For example, the terminal may include user plane data (mobile originated (MO) call data), such as the IMS registration process (step 201c) and / or SIP signaling that generates a voice call (step 202), in the NAS data of the SRB and transmit it to the MME via the eNB, and may transmit said data through the S-GW and P-GW. Additionally, when the terminal receives user plane data (mobile terminated (MT) call data), the data received from the P-GW is transmitted to the MME via the S-GW, and the MME may include said data in the NAS data of the SRB and transmit it to the terminal via the eNB.

[0106] In this embodiment, the terminal that negotiates the voice service support function through the NB-IoT NTN (Geo) can perform Control plane CIoT optimization in communication for IMS services.

[0107] In step 202, during the process of sending a voice call, the terminal includes traffic-related information for the Geo voice service in the Session Description Protocol (SDP) offer within the Session Initiation Protocol (SIP) INVITE message and transmits it to the P-CSCF; in steps 203 and 204, the traffic-related information for the Geo voice service can be transmitted to the counterparty terminal (UE-2) via the Serving-Call Session Control Function (S-CSCF) through the IMS network. Here, the traffic-related information for the Geo voice service may include information regarding the voice coding method and / or the supported coding speed.

[0108] In step 205, the other terminal may send a SIP 183 message in response to the SIP INVITE, including information regarding the voice service traffic it will use in the SDP answer. Here, the information regarding the voice service traffic may include information about the voice coding method and / or the supported coding rate.

[0109] Upon receiving a SIP 183 message containing an SDP answer at step 206, the P-CSCF can confirm that a terminal registered as “3GPP-NB-IoT(GEO)” has requested a voice call. For example, when receiving an SDP answer for a voice call during IMS registration or for a terminal where the P-Access-Network-Info header field of the SIP 183 message is set to “3GPP-NB-IoT(GEO)”, the P-CSCF can confirm that the terminal has requested a setup for a voice call service (Geo voice call) via NB-IoT(GEO). Accordingly, at step 208, the P-CSCF can send a Diameter AAR (Authorization Authentication Request) message to the PCRF requesting a resource reservation to receive QoS for servicing the Geo voice call. At this time, the Diameter AAR message may include QoS information for the Geo voice call service data traffic (e.g., QCI value or Geo voice-specific QCI value) and / or service request information. Optionally or additionally, the Diameter AAR message may include information indicating a setup for a voice service (Geo voice call) via NB-IoT (GEO). Optionally or additionally, the Diameter AAR message may include voice codec information for a Geo voice call for the terminal. Here, the voice codec information may be used exclusively for Geo voice to indirectly indicate that it is a setup for a Geo voice call.

[0110] Alternatively, if resource allocation for Geo voice calls has already been completed in step 201d or if the resource allocation process for Geo voice calls is set to be omitted, the resource setup request / allocation process from steps 208 to 212 may be omitted.

[0111] Meanwhile, if the PCRF receives a Diameter AAR message in step 208 containing information indicating the setup of a voice service (Geo voice call) via NB-IoT (GEO) and / or voice codec information for the Geo voice call, it may transmit a PCC rule to the P-GW in step 209 to perform a resource allocation process for the voice call. At this time, when the PCRF recognizes the setup of a voice service via NB-IoT (GEO), it may transmit an IP-CAN (IP-Connectivity Access Network) session Modification message containing PCC information (PCC rule) to the P-GW to update QoS information (e.g., QCI value or Geo voice-specific QCI value) and / or packet filter (TFT) information so that even data traffic with GBR characteristics for the voice call is mapped to a default EPS bearer that supports non-GBR. Alternatively, information indicating that it is a Geo voice call setup may be transmitted to the P-GW.

[0112] If the P-CSCF that recognizes the Geo voice call setup in step 207 has the IMS-ALG function, when a voice call with a high voice codec arrives, it may be configured to have the IMS-AGW perform transcoding into the voice codec of the Geo voice call.

[0113] If the P-GW that received the PCC rule in step 209 has already performed resource setup for the default EPS bearer for IMS in step 201d, it may omit performing resource setup in step 210. Alternatively, the P-GW that received the PCC rule for the Geo voice call setup may perform a bearer modification procedure in step 210 to allow Geo voice call data traffic to be serviced through the default EPS bearer. Subsequently, in step 211, the PGW transmits an IP-CAN session Modification message to the PCRF, and in step 212, the PCRF transmits a Diameter AAA (Authorization Authentication Answer) message, which is a response to the Diameter AAR message, to the P-CSCF.

[0114] Meanwhile, when Control plane CIoT optimization is applied, data can be included in a NAS message to perform bearer modification without setting up a DRB and transmitted to the terminal (via eNB).

[0115] Likewise, in steps 213 and 214, when Control plane CIoT optimization is applied, SIP signaling for voice call setup can be performed through eNB / MME / S-GW / P-GW using the default EPS bearer for IMS (i.e., the default EPS bearer of the PDN connection for IMS) and SRB. Also, in step 215, transmission of IMS voice call data traffic for Geo voice calls can be performed through eNB / MME / S-GW / P-GW using the default EPS bearer for IMS and SRB.

[0116] In this drawing, the case where a terminal connects to an eNB and an EPC / EPS network via NB-IoT (Geo) is described as an example, but as described in Fig. 1, the same method can be applied when a terminal connects to a gNB and a 5GC / 5GS or 6G or later system via NB-IoT (Geo), and in this case, the PDN connection can correspond to a PDU Session.

[0117] FIGS. 3a and 3b illustrate a procedure in which a terminal connects to a communication network and a voice call service is provided using a user plane in a wireless communication system according to one embodiment of the present disclosure.

[0118] This diagram describes, for example, the procedure for a terminal to connect to an EPS network via an NB-IoT NTN (Geo) satellite and use an IMS voice service.

[0119] Referring to FIGS. 3a and 3b, when a terminal (UE-1) receives a broadcast message from an NB-IoT NTN (Geo) satellite announcing the existence of an NB-IoT (Geo) network, the terminal may attempt to connect to the network. The broadcast message may include an indicator indicating that voice services are available through the NB-IoT satellite network or the NB-IoT (Geo) network.

[0120] In step 301a, the terminal informs the MME of the EPS network during the attach request process that it can receive voice services via NB-IoT NTN (Geo) by connecting to the network, and the MME may inform the terminal whether it can provide voice services via NB-IoT NTN (Geo) using a response message to the attach request. In the case of a 5G network, if the terminal informs during the registration process that it can provide voice services via NB-IoT NTN (Geo), the AMF may inform the terminal whether the network supports the corresponding function using a response message to the registration request.

[0121] Meanwhile, the terminal can negotiate with the MME or AMF during the attach or registration process whether NB-IoT functions are provided or supported. Alternatively, the terminal and the MME or AMF can negotiate during the attach or registration process whether Control plane CIoT (Cellular Internet-of-Things) optimization functions and / or User plane CIoT optimization functions are supported. Here, the Control plane CIoT 5GS optimization function is used to exchange user data in the uplink / downlink direction as the payload of NAS messages, and resources can be saved by not establishing a user plane connection for the PDU session. Additionally, through the User plane CIoT 5GS optimization function, the terminal can transmit user plane data in CM-IDLE without using the service request procedure.

[0122] The voice service support function through NB-IoT NTN (Geo) can be indicated by (1) a direct indicator such as a Geo voice capability indication, (2) a combination of an IMS voice over PS session supported indication and the fact that the terminal is camping on NB-IoT NTN (Geo) or NB-IoT (Geo), or (3) a combination of a Voice domain preference and UE's usage setting (= voice centric and IMS PS Voice only) and the fact that the terminal is camping on NB-IoT NTN (Geo) or NB-IoT (Geo).

[0123] In step 301b, when the terminal attaches to the network, it can create a PDN connection (or PDU Session) to receive IMS services. For example, when the terminal transmits a request to create a PDN connection, it may include an APN value for IMS services, and when the request to create a PDN connection is transmitted to the P-GW, a PDN connection and a default EPS bearer for IMS services are created, and this fact may be transmitted to the terminal along with a response to the request to create a PDN connection.

[0124] In step 301c, the terminal can perform IMS registration using the generated bearer. At this time, the terminal that has negotiated the voice service function via the NB-IoT NTN (Geo) may include in the IMS registration message the access type in the P-CSCF by setting the P-Access-Network-Info header field of the IMS registration message to “3GPP-NB-IoT (GEO)” or “3GPP-NB-IoT NTN (GEO)” and configuring SIP compression to be enabled (see 3GPP TS 24.229).

[0125] In addition, at step 301c, the P-CSCF may include address information or FQDN (Fully Qualified Domain Name) information of an IMS-AGW (access gateway) that performs / manages the IMS-ALG (access level gateway) function in the registration response message and transmit it to the terminal.

[0126] The address information or FQDN information of the above IMS-AGW may be provided by referring to the IMS-AGW assigned to “3GPP-NB-IoT(GEO)” based on the P-Access-Network-Info header field of the IMS registration message transmitted by the terminal.

[0127] In step 301b, (1) address information or FQDN information of a P-CSCF set in a PCRF or P-GW for an APN for IMS and / or (2) address information or FQDN information of an IMS-AGW (access gateway) may be stored in the P-GW or included in a response message to the request to create a PDN connection and delivered to the terminal. This information may be provided to the terminal based on the fact that the terminal has connected to the network through an NB-IoT NTN (Geo) and has the ability to provide voice services through an NB-IoT NTN (Geo).

[0128] Meanwhile, in the case of a terminal that has negotiated a voice service support function through NB-IoT NTN (Geo) as in step 301a, the resource allocation process for the bearer may be performed in advance before and after the IMS registration in step 301c, and before the Geo Voice call occurs in step 301d.

[0129] For example, for a terminal that has negotiated a voice service support function through NB-IoT NTN (Geo), if the P-GW obtains the address information of the P-CSCF and / or the address information of the IMS-AGW for the IMS APN through the above process before or after performing IMS registration, the P-GW can provide data for the voice service (or 'Geo Voice service', hereinafter used interchangeably) through the NB-IoT NTN (Geo) with sufficient QoS using the default EPS bearer. In addition, the P-GW may pre-allocate resources for the bearer before a Geo Voice call occurs by performing a bearer modification process for the terminal's default EPS bearer for IMS to update QoS information (e.g., QCI value or Geo voice-specific QCI value) and / or packet filters (e.g., TFT (Traffic Flow Template) information) so that the data can be forwarded to and received from the IMS-AGW.

[0130] In another way, if a terminal that has negotiated a voice service support function via NB-IoT NTN (Geo) obtains the address information of the P-CSCF and / or the address information of the IMS-AGW for the IMS APN through the above process before or after IMS registration, the terminal can receive data for the voice service via NB-IoT NTN (Geo) (or 'Geo Voice service', hereinafter used interchangeably) with sufficient QoS using the default EPS bearer. In addition, the terminal may pre-allocate resources for the bearer before a Geo Voice call occurs by sending a bearer modification request for the terminal's default EPS bearer for IMS to the P-GW (via MME) to update QoS information (e.g., QCI value or Geo voice-specific QCI value) and / or packet filters (e.g., TFT information) so that the data can be properly forwarded to and received from the IMS-AGW.

[0131] Meanwhile, if the terminal and the MME negotiate regarding the CIoT optimization function in step 301a and the application of User plane CIoT optimization is possible, the terminal may not clear the AS (Access Stratum) context between the terminal and the eNB even in an idle state. Additionally, if supported, the terminal may perform early data communication through Early Data Transmission, Suspension, and / or Resume processes. For example, the terminal may use the default EPS bearer and DRB of the IMS PDN connection to perform the IMS registration process (step 301c), SIP signaling to generate a voice call (step 302), and subsequently to transmit and receive user plane data such as voice call data.

[0132] In this embodiment, the terminal that has negotiated the voice service support function through the NB-IoT NTN (Geo) can perform User plane CIoT optimization in communication for IMS services.

[0133] In step 302, during the process of sending a voice call, the terminal includes traffic-related information for the Geo voice service in the Session Description Protocol (SDP) offer within the Session Initiation Protocol (SIP) INVITE message and transmits it to the P-CSCF; in steps 303 and 304, the traffic-related information for the Geo voice service can be transmitted to the counterparty terminal (UE-2) via the Serving-Call Session Control Function (S-CSCF) through the IMS network. Here, the traffic-related information for the Geo voice service may include information regarding the voice coding method and / or the supported coding speed.

[0134] In step 305, the other terminal may send a SIP 183 message in response to the SIP INVITE, including information regarding the voice service traffic it will use in the SDP answer. Here, the information regarding the voice service traffic may include information about the voice coding method and / or the supported coding rate.

[0135] Upon receiving a SIP 183 message containing an SDP answer at step 306, the P-CSCF can confirm that a terminal registered as “3GPP-NB-IoT(GEO)” has requested a voice call. For example, when receiving an SDP answer for a voice call during IMS registration or for a terminal where the P-Access-Network-Info header field of the SIP 183 message is set to “3GPP-NB-IoT(GEO)”, the P-CSCF can confirm that the terminal has requested a setup for a voice call service (Geo voice call) via NB-IoT(GEO). Accordingly, at step 308, the P-CSCF can send a Diameter AAR (Authorization Authentication Request) message to the PCRF requesting a resource reservation to receive QoS for servicing the Geo voice call. At this time, the Diameter AAR message may include QoS information for the Geo voice call service data traffic (e.g., QCI value or Geo voice-specific QCI value) and / or service request information. Optionally or additionally, the Diameter AAR message may include information indicating a setup for a voice service (Geo voice call) via NB-IoT (GEO). Optionally or additionally, the Diameter AAR message may include voice codec information for a Geo voice call for the terminal. Here, the voice codec information may be used exclusively for Geo voice to indirectly indicate that it is a setup for a Geo voice call.

[0136] Alternatively, if resource allocation for Geo voice calls has already been completed in step 301d or if the resource allocation process for Geo voice calls is set to be skipped, the resource setup request / allocation process from steps 308 to 312 may be skipped.

[0137] Meanwhile, if the PCRF receives a Diameter AAR message in step 308 containing information indicating the setup of a voice service (Geo voice call) via NB-IoT (GEO) and / or voice codec information for the Geo voice call, it may transmit a PCC rule to the P-GW in step 309 to perform a resource allocation process for the voice call. At this time, when the PCRF recognizes the setup of a voice service via NB-IoT (GEO), it may transmit an IP-CAN (IP-Connectivity Access Network) session Modification message containing PCC information (PCC rule) to the P-GW to update QoS information (e.g., QCI value or Geo voice-specific QCI value) and / or packet filter (TFT) information so that even data traffic with GBR characteristics for the voice call is mapped to a default EPS bearer that supports non-GBR. Alternatively, information indicating that it is a Geo voice call setup may be transmitted to the P-GW.

[0138] If the P-CSCF that recognizes the Geo voice call setup in step 307 has the IMS-ALG function, when a voice call with a high voice codec arrives, it may be configured to have the IMS-AGW perform transcoding into the voice codec of the Geo voice call.

[0139] If the P-GW that received the PCC rule in step 309 has already performed resource setup for the default EPS bearer for IMS in step 301d, the resource setup in step 310 may be omitted. Alternatively, the P-GW that received the PCC rule for the Geo voice call setup may perform a bearer modification procedure in step 310 to allow Geo voice call data traffic to be serviced through the default EPS bearer. Subsequently, in step 311, the PGW transmits an IP-CAN session Modification message to the PCRF, and in step 312, the PCRF transmits a Diameter AAA (Authorization Authentication Answer) message, which is a response to the Diameter AAR message, to the P-CSCF.

[0140] Likewise, communication with the terminal can be performed using the default EPS bearer for IMS (i.e., the default EPS bearer of the PDN connection for IMS) and the DRB, as well as SIP signaling for voice call setup in steps 313 and 314 and IMS voice call data traffic for Geo voice call in step 315.

[0141] In this drawing, the case where a terminal connects to an eNB and an EPC / EPS network via NB-IoT (Geo) is described as an example, but as described in Fig. 1, the same method can be applied when a terminal connects to a gNB and a 5GC / 5GS or 6G or later system via NB-IoT (Geo), and in this case, the PDN connection can correspond to a PDU Session.

[0142] FIGS. 4a and 4b illustrate a procedure in which a terminal connects to a communication network and a voice call service is provided using a control plane and a user plane in a wireless communication system according to one embodiment of the present disclosure.

[0143] This diagram describes, for example, the procedure for a terminal to connect to an EPS network via an NB-IoT NTN (Geo) satellite and use an IMS voice service.

[0144] More specifically, in this drawing, when a Geo voice call is set up while SIP messages are being transmitted and received using the SRB and S11-U bearer (user plane interface between MME and S-GW) through the Control plane CIoT optimization method of FIG. 2a and 2b, an S1-U bearer (user plane interface between eNB and S-GW) can be created to transmit and receive voice call traffic on the user plane.

[0145] Referring to FIGS. 4a and 4b, when a terminal (UE-1) receives a broadcast message from an NB-IoT NTN (Geo) satellite announcing the presence of an NB-IoT (Geo) network, the terminal may attempt to connect to the network. The broadcast message may include an indicator indicating that voice services are available through the NB-IoT satellite network or the NB-IoT (Geo) network.

[0146] In step 401a, the terminal informs the MME of the EPS network during the attach request process that it can connect to the network and receive voice services via NB-IoT NTN (Geo), and the MME may inform the terminal whether it can provide voice services via NB-IoT NTN (Geo) using a response message to the attach request. In the case of a 5G network, if the terminal informs during the registration process that it can provide voice services via NB-IoT NTN (Geo), the AMF may inform the terminal whether the network supports the corresponding function using a response message to the registration request.

[0147] Meanwhile, the terminal may negotiate with the MME or AMF during the attach or registration process whether NB-IoT functions are provided or supported. Alternatively, the terminal and the MME or AMF may negotiate during the attach or registration process whether Control plane CIoT (Cellular Internet-of-Things) optimization functions and / or User plane CIoT optimization functions are supported. Alternatively, the terminal and the MME or AMF may negotiate during the attach or registration process whether S1-U data transfer functions are supported along with Control plane CIoT optimization functions. Here, the Control plane CIoT 5GS optimization function is used to exchange user data in the uplink / downlink direction as the payload of NAS messages, and resources can be saved by not establishing a user plane connection for the PDU session. Additionally, through the User plane CIoT 5GS optimization function, the terminal can transmit user plane data in CM-IDLE without using the service request procedure.

[0148] The voice service support function through NB-IoT NTN (Geo) can be indicated by (1) a direct indicator such as a Geo voice capability indication, (2) a combination of an IMS voice over PS session supported indication and the fact that the terminal is camping on NB-IoT NTN (Geo) or NB-IoT (Geo), or (3) a combination of a Voice domain preference and UE's usage setting (= voice centric and IMS PS Voice only) and the fact that the terminal is camping on NB-IoT NTN (Geo) or NB-IoT (Geo).

[0149] In step 401b, when the terminal attaches to the network, it can create a PDN connection (or PDU Session) to receive IMS services. For example, when the terminal transmits a request to create a PDN connection, it may include an APN value for IMS services, and when the request to create a PDN connection is transmitted to the P-GW, a PDN connection and a default EPS bearer for IMS services are created, and this fact may be transmitted to the terminal along with a response to the request to create a PDN connection.

[0150] In step 401c, the terminal can perform IMS registration using the generated bearer. At this time, the terminal that has negotiated the voice service function via the NB-IoT NTN (Geo) may include in the IMS registration message the access type in the P-CSCF by setting the P-Access-Network-Info header field of the IMS registration message to “3GPP-NB-IoT (GEO)” or “3GPP-NB-IoT NTN (GEO)” and configuring SIP compression to be enabled (see 3GPP TS 24.229).

[0151] In addition, at step 401c, the P-CSCF may include address information or FQDN (Fully Qualified Domain Name) information of an IMS-AGW (access gateway) that performs / manages the IMS-ALG (access level gateway) function in the registration response message and transmit it to the terminal.

[0152] The address information or FQDN information of the above IMS-AGW may be provided by referring to the IMS-AGW assigned to “3GPP-NB-IoT(GEO)” based on the P-Access-Network-Info header field of the IMS registration message transmitted by the terminal.

[0153] In step 401b, (1) address information or FQDN information of a P-CSCF set in a PCRF or P-GW for an APN for IMS and / or (2) address information or FQDN information of an IMS-AGW (access gateway) may be stored in the P-GW or included in a response message to the request to create a PDN connection and transmitted to the terminal. This information may be provided to the terminal based on the fact that the terminal has connected to the network through an NB-IoT NTN (Geo) and has the ability to provide voice services through an NB-IoT NTN (Geo).

[0154] Meanwhile, in the case of a terminal that has negotiated a voice service support function through NB-IoT NTN (Geo) as in step 401a, the resource allocation process for the bearer may be performed in advance before and after the IMS registration in step 401c, and before the Geo Voice call occurs in step 401d.

[0155] For example, for a terminal that has negotiated a voice service support function through NB-IoT NTN (Geo), if the P-GW obtains the address information of the P-CSCF and / or the address information of the IMS-AGW for the IMS APN through the above process before or after performing IMS registration, the P-GW can provide data for the voice service (or 'Geo Voice service', hereinafter used interchangeably) through the NB-IoT NTN (Geo) with sufficient QoS using the default EPS bearer. In addition, the P-GW may pre-allocate resources for the bearer before a Geo Voice call occurs by performing a bearer modification process for the terminal's default EPS bearer for IMS to update QoS information (e.g., QCI value or Geo voice-specific QCI value) and / or packet filters (e.g., TFT (Traffic Flow Template) information) so that the data can be forwarded to and received from the IMS-AGW.

[0156] In another way, if a terminal that has negotiated a voice service support function via NB-IoT NTN (Geo) obtains the address information of the P-CSCF and / or the address information of the IMS-AGW for the IMS APN through the above process before or after IMS registration, the terminal can receive data for the voice service via NB-IoT NTN (Geo) (or 'Geo Voice service', hereinafter used interchangeably) with sufficient QoS using the default EPS bearer. In addition, the terminal may pre-allocate resources for the bearer before a Geo Voice call occurs by sending a bearer modification request for the terminal's default EPS bearer for IMS to the P-GW (via MME) to update QoS information (e.g., QCI value or Geo voice-specific QCI value) and / or packet filters (e.g., TFT information) so that the data can be properly forwarded to and received from the IMS-AGW.

[0157] Meanwhile, if, in step 401a, the terminal and the MME negotiate regarding the CIoT optimization function and the application of Control plane CIoT optimization and User plane CIoT optimization is possible, or if, in step 401a, the terminal and the MME negotiate regarding the CIoT optimization function and the application of Control plane CIoT optimization and S1-U data transfer is possible, the terminal may not generate a DRB for the default EPS bearer and instead use a signaling radio bearer (SRB). For example, the terminal may include user plane data (mobile originated (MO) call data), such as the IMS registration process (step 401c) and / or SIP signaling that generates a voice call (step 402), in the NAS data of the SRB and transmit it to the MME through the eNB, and transmit the data through the S-GW and P-GW. In addition, when the terminal receives user plane data (mobile terminated (MT) call data), the data received from the P-GW is transmitted to the MME via the S-GW, and the MME can include the data in the NAS data of the SRB and transmit it to the terminal via the eNB.

[0158] In this embodiment, the terminal that negotiates the voice service support function through the NB-IoT NTN (Geo) can perform Control plane CIoT optimization in communication for IMS services.

[0159] In step 402, during the process of sending a voice call, the terminal includes traffic-related information for the Geo voice service in the Session Description Protocol (SDP) offer within the Session Initiation Protocol (SIP) INVITE message and transmits it to the P-CSCF; in steps 403 and 404, the traffic-related information for the Geo voice service can be transmitted to the counterparty terminal (UE-2) via the Serving-Call Session Control Function (S-CSCF) through the IMS network. Here, the traffic-related information for the Geo voice service may include information regarding the voice coding method and / or the supported coding speed.

[0160] Subsequently, the process from step 405 to step 407 of the present drawing may correspond to the process from step 205 to step 213 of FIGS. 2a and 2b.

[0161] Here, if the terminal transmits the SIP invite message of step 402, receives a SIP 183 message (or a message such as SIP 180) from the counterparty terminal, or if the voice call setup process is performed, the terminal supporting Geo voice calls may transmit a Control plane service request containing an active flag to the MME in step 408. In step 409, the MME decides to create an S1-U bearer for the default EPS bearer for IMS and can delete the S11-U bearer through the process of step 410. Subsequently, by using the user plane and DRB set up through the process of steps 411 to 414, the user plane method of FIGS. 3a and 3b can be applied to transmit the remaining SIP signaling and voice data in steps 415 and 416. That is, data transmission and reception can be performed using the default EPS bearer for IMS (i.e., the default EPS bearer of the IMS PDN connection) and the corresponding DRB.

[0162] Meanwhile, in steps 411 to 414, during the resource allocation process for the Geo voice call of step 401d or step 407 (particularly, step 210 of FIG. 2a and 2b) and / or the bearer modification process for the default EPS bearer, a DRB can be set up using QoS information stored in the MME. Although the present drawing describes an example where the terminal connects to the eNB and the EPC / EPS network via NB-IoT (Geo), the same method can be applied when the terminal connects to the gNB and the 5GC / 5GS or 6G or subsequent systems via NB-IoT (Geo) as described in FIG. 1, and in this case, the PDN connection can correspond to the PDU Session.

[0163] FIG. 5 is a block diagram of a terminal or user equipment (500) according to one embodiment of the present disclosure.

[0164] The terminal (500) is an electronic device capable of wireless communication and may include user equipment (UE), mobile phones, smartphones, tablets, Internet of Things (IoT) devices having various form factors, and can perform wireless communication with a base station through a wireless channel.

[0165] Referring to FIG. 5, the terminal (500) may include at least one transceiver (501) (hereinafter, transceiver), at least one processor (502) (hereinafter, processor), and at least one memory (503) (hereinafter, memory). The transceiver (501), processor (502), and memory (503) of the terminal (500) may be operated according to at least one or a combination thereof of the methods corresponding to the embodiments of the present disclosure. However, the components of the terminal (500) are not limited to the examples of components shown in FIG. 5. In other embodiments, the terminal (500) may include additional components in addition to the aforementioned components, or some components may be omitted. Also, in some embodiments, any combination of the transceiver (501), processor (502), or memory (503) may be integrated into a single component.

[0166] The transceiver (501) may be a basic communication circuit or communication circuitry that enables the terminal (500) to perform wireless communication with a node or entity of a network. For example, the transceiver (501) may enable the terminal (500) to transmit and receive signals to and from a base station via cellular wireless communication, or to transmit and receive signals to and from another terminal via cellular wireless communication. For example, the transceiver (501) may support at least one of various cellular wireless communication technologies including 3G (3rd generation), 4G (4th generation) LTE (long-term evolution), 5G (5th generation) NR (new radio), 6G (6th generation), etc., and the various cellular wireless communication technologies supported by the transceiver (501) may include all subsequent generations of wireless communication.

[0167] According to one embodiment, the terminal (500) may include a plurality of transceivers, and for example, when supporting EN-DC (E-UTRA (evolved-universal terrestrial radio access) - NR dual connectivity), it may include a first transceiver supporting 4G LTE wireless communication and a second transceiver supporting 5G NR wireless communication. According to another embodiment, when the terminal (500) supports NR-DC (NR Dual Connectivity), the terminal (500) may include a plurality of transceivers supporting 5G NR wireless communication. According to another embodiment, if the terminal (500) supports short-range wireless communication, the terminal (500) may separately include a transceiver that supports at least one of a group of wireless communication protocol standards such as those defined by Bluetooth®, wireless LAN or WLAN (wireless local area network) network (including, but not limited to, IEEE (institute of electrical and electronics engineer) 802.11-2016 standard or modifications thereof such as 802.11ah, 802.11ad, 802.11ay, 802.11ax, 802.11az, 802.11ba and 802.11be).

[0168] According to one embodiment, the transceiver (501) may include various circuit structures used to transmit and receive signals through a base station and a wireless channel. The signals may include control information and data. For example, the transceiver (501) may be configured to include an RF (radio frequency) transmitter that up-converts and amplifies the frequency of a transmitted signal, and an RF receiver that low-noise amplifies a received signal and down-converts the frequency. The transceiver (501) may output the signal received through the wireless channel to a processor (502) and transmit the signal output from the processor (502) through the wireless channel.

[0169] A processor (502) can control the overall operation of a terminal (500) according to an embodiment of the present disclosure. The processor (502) may be implemented as one or more IC (integrated circuit (or circuitry)) chips and may perform various data processing operations. The processor (502) may include at least one electrical circuit and may execute instructions (or programs, code, data, etc.) stored in memory (503) individually, collectively, or in any combination. Additionally, the processor (502) may include a single-core processor or a multi-core processor, and in a specific implementation, may be composed of a processor assembly including a plurality of processing circuits.

[0170] The processor (502) is electrically, operatively, or communicatively coupled to the transceiver (501) so as to control the transceiver (501).

[0171] The processor (502) may include at least one processor (or, processing circuitry), and at least one processor may perform the following operations individually, collectively, or in any combination. For example, the processor (502) may include a communication processor (CP) that controls communication operations and an application processor (AP) that controls the execution of an upper layer (e.g., an application layer). In a specific embodiment, at least one part of the processor (502) may be included in one chip, and another part of the processor (502) may be included in a separate chip. Alternatively, at least one processor may be included in other components, e.g., a transceiver (501) or a memory (503).

[0172] The processor (502) may perform, cause, or control the operation of a terminal to perform at least one or a combination thereof of the methods according to the embodiments of the present disclosure. For example, the processor (502) may control the operation of a terminal to process a downlink signal received from a base station or to generate an uplink signal and transmit it to a base station. To this end, the processor (502) may control other components of the terminal (500) to perform various operations by executing computer programs, code, or instructions stored in memory (503).

[0173] Memory (503) is a hardware storage device capable of storing information temporarily or permanently and may include one or more storage media. For example, memory (503) may include a memory assembly comprising one or more storage media. For example, the one or more storage media may include a hard drive, flash memory, permanent memory such as ROM (read-only memory), semipermanent memory such as RAM (random access memory), cache memory, or any combination thereof.

[0174] The memory (503) can be electrically, operatively, or communically coupled with the processor (502) and can be accessed by the processor (502).

[0175] A computer program, code, or instruction that can be executed by a processor (502) may be stored in the memory (503). According to one embodiment, the computer program, code, or instruction that can be executed by the processor (502) may be stored in a single memory device or may be separated and distributed across two or more memory devices. The processor (502) can perform various functions according to the embodiments of the present disclosure by executing the instruction stored in the memory (503).

[0176] According to one embodiment of the present disclosure, the operation of the terminal (500) may be caused to be performed based on at least one processor (or processing circuit) configured to perform the features of the present disclosure individually, collectively, or in any combination based on the execution of instructions (or computer program or code) stored in memory (503), based on processing circuitry not configured to execute instructions, and / or based on components of a processing circuitry not configured to execute instructions.

[0177] FIG. 6 is a block diagram of a base station (600) according to one embodiment of the present disclosure.

[0178] The base station (600) can perform wireless communication with at least one terminal within the area of ​​the base station (600) through a wireless channel.

[0179] Referring to FIG. 6, a base station (600) may include at least one transceiver (601) (hereinafter, transceiver), at least one processor (602) (hereinafter, processor), and at least one memory (603) (hereinafter, memory). According to at least one or a combination thereof of methods corresponding to embodiments of the present disclosure, the transceiver (601), processor (602), and memory (603) of the base station (600) may be operated. However, the components of the base station (600) are not limited to the examples of components shown in FIG. 6. In other embodiments, the base station (600) may include additional components in addition to the aforementioned components, or some components may be omitted. Also, in some embodiments, any combination of the transceiver (601), processor (602), or memory (603) may be integrated into a single component.

[0180] The transceiver (601) may be a communication circuit or communication circuitry that enables the base station (600) to perform wireless communication with a node or entity of the network. For example, the transceiver (601) may enable the base station (600) to transmit and receive signals to and from a terminal (500) via cellular wireless communication or to transmit and receive signals to and from another network entity via wireless communication. For example, the transceiver (601) may support various cellular wireless communication technologies including 3G (3rd generation), 4G (4th generation) LTE (long-term evolution), 5G (5th generation) NR (new radio), 6G (6th generation), etc., and the various cellular wireless communication technologies supported by the transceiver (601) may include all subsequent generations of wireless communication. According to one embodiment, the transceiver (601) may include various circuit structures used to transmit and receive signals to and from a terminal via a wireless channel. The above signal may include control information and data. For example, the transceiver (601) may be configured to include an RF (radio frequency) transmitter that up-converts and amplifies the frequency of a transmitted signal, and an RF receiver that low-noise amplifies a received signal and down-converts the frequency. The transceiver (601) may output the signal received via a wireless channel to a processor (602) and transmit the signal output from the processor (602) via a wireless channel.

[0181] Meanwhile, according to one embodiment of the present disclosure, a base station (600) may communicate with an entity or node of a network via wired or wireless communication. For example, the base station (600) may communicate via wired or wireless communication with an entity or node of an adjacent base station or core network via a backhaul network. Although not shown in the drawings, when the base station (600) performs wired communication, the base station (600) may include a separate network interface for wired communication in addition to the transceiver (601). The network interface may be referred to as network interface circuitry, communication interface circuitry, etc.

[0182] The processor (602) can control the overall operation of the base station (600) according to an embodiment of the present disclosure. The processor (602) may be implemented as one or more IC (integrated circuit or circuitry) chips and may perform various data processing operations. The processor (602) may include at least one electrical circuit and may execute instructions (or programs, code, data, etc.) stored in memory (603) individually, collectively, or in any combination. Additionally, the processor (602) may include a single-core processor or a multi-core processor, and in a specific implementation, may be composed of a processor assembly including a plurality of processing circuits.

[0183] The processor (602) is electrically, operatively, or communicatively coupled to the transceiver (601) so as to control the transceiver (601).

[0184] The processor (602) may include at least one processor (or processor circuitry), and at least one processor may perform the following operations individually, collectively, or in any combination. In a particular embodiment, at least one part of the processor (602) may be included in one chip, and another part of the processor (602) may be included in a separate chip. Alternatively, at least one processor may be included in other components, such as a transceiver (601) or memory (603).

[0185] The processor (602) may perform, cause, or control the operation of a base station to execute at least one or a combination of methods according to embodiments of the present disclosure. For example, the processor (602) may control the operation of a base station to generate a downlink signal and transmit it to a terminal, or to process an uplink signal received from a terminal. Alternatively, the base station may transmit and receive signals with an adjacent base station, transmit a signal received from a terminal to an upper node of the network, or receive a signal from an upper node of the network and transmit it to a terminal. To this end, the processor (602) may control other components of the base station (600) to perform various operations by executing computer programs, codes, and instructions stored in memory (603).

[0186] Memory (603) is a hardware storage device capable of storing information temporarily or permanently and may include one or more storage media. For example, memory (603) may include a memory assembly comprising one or more storage media. For example, the one or more storage media may include a hard drive, flash memory, permanent memory such as ROM (read-only memory), semi-permanent memory such as RAM (random access memory), cache memory, or any combination thereof.

[0187] The memory (603) can be electrically, operatively, or communically coupled with the processor (602) and can be accessed by the processor (602).

[0188] A computer program, code, or instruction that can be executed by a processor (602) may be stored in the memory (603). According to one embodiment, the computer program, code, or instruction that can be executed by the processor (602) may be stored in a single memory device or may be separated and distributed among two or more memory devices. The processor (602) may perform various functions according to the embodiments of the present disclosure by executing the instruction stored in the memory (603).

[0189] According to one embodiment of the present disclosure, the operation of the base station (600) may be caused to be performed based on at least one processor (or processing circuit) configured to perform the features of the present disclosure individually, collectively, or in any combination based on the execution of instructions (or computer program or code) stored in memory (603), based on processing circuitry not configured to execute instructions, and / or based on components of a processing circuitry not configured to execute instructions.

[0190] A terminal or a base station can perform various communication procedures related to the control plane or user plane by interacting with network entities based on communication through a wireless channel. For example, a terminal can communicate with network entities such as an access and mobility management function (AMF) or a session management function (SMF) through a base station. Alternatively, the base station can perform at least one communication procedure by directly transmitting and receiving signals or relaying them with network entities. The structure of the above-mentioned network entities will be explained in more detail through the drawings below.

[0191] FIG. 7 is a block diagram of a network entity (700) that performs network functions according to one embodiment of the present disclosure.

[0192] A network entity (700) may include one or more network functions (NF) that constitute a core network (e.g., 5G (5th generation) core, 5GC) in a communication system, or entities (devices, devices, nodes, or servers, etc.) that perform part of a network function. In this case, multiple NFs may be implemented within a single network entity, or a single NF may be distributed and implemented across multiple network entities. Additionally, when an NF is implemented within a network entity, the NF may be implemented in the form of software, and in such cases, a program for running the NF may be loaded into the memory of the network entity (700).

[0193] A single NF can be implemented as one or more instances and can operate by being distributed across the same network entity or multiple network entities. Here, the instance is a software unit that logically executes a specific network function and may be separate from physical hardware resources. Additionally, one or more NFs may be implemented as a single network slice to operate in order to satisfy the specifications required by a specific service.

[0194] The above NF may include any one of an access and mobility management function (AMF), a session management function (SMF), a local session management function (L-SMF), a user plane function (UPF), a local user plane function (L-UPF), a policy control function (PCF), unified data management (UDM), a unified data repository (UDR), a network exposure function (NEF), a network repository function (NRF), an application function (AF), a network slice selection function (NSSF), a network data analytics function (NWDAF), a network slice admission control function (NSACF), an authentication server function (AUSF), or a data network (DN).

[0195] Referring to FIG. 7, a network entity (700) may include at least one network interface (701), at least one processor (702) (hereinafter referred to as processor), and at least one memory (703) (hereinafter referred to as memory). As described above, the NF may be implemented in the form of a physical device such as the network entity (700), or may be implemented and executed in the form of a virtualized instance. When the NF is implemented in the form of an instance, it may not necessarily include physical components as illustrated in FIG. 7. In such cases, the instance may be composed of one or more logical functional units and may be logically represented.

[0196] According to at least one or a combination thereof of the methods corresponding to the embodiments of the present disclosure, the network interface (701), processor (702), and memory (703) of the network entity (700) may be operated. However, the components of the network entity (700) are not limited to the examples of components shown in FIG. 7. In other embodiments, the network entity (700) may include additional components in addition to the aforementioned components, or some components may be omitted. Also, in one embodiment, the network interface (701), processor (702), or memory (703) may be implemented as a single component.

[0197] The network interface (701) is a collective term for the transmitting and receiving parts of a network entity and may be a communication circuit for transmitting and receiving signals with a terminal (user equipment, UE), a base station, or other network entities. In this case, the communication circuit may include both a communication circuit for wireless communication and a communication circuit for wired communication. For example, the network interface (701) may include circuits, logic, hardware, etc. configured to exchange control plane messages or user plane messages with a terminal, a base station, or other core network entities via wireless or wired communication. The network interface (701) may operate using various protocols (e.g., NAS (Non-Access Stratum) protocol). Depending on the convenience of explanation and technical implementation, the network interface (701) may be referred to as a communication circuitry, a network interface circuitry, or a communication interface circuitry.

[0198] The processor (702) may control the overall operation of the network entity (700) according to an embodiment of the present disclosure. In one embodiment, the processor (702) may be implemented as one or more IC (integrated circuit or circuitry) chips and may execute various data processing operations. The processor (702) may include at least one electrical circuit and may execute instructions (or programs, code, data, etc.) stored in memory (703) individually, collectively, or in any combination. Additionally, the processor (702) may include a single-core processor or a multi-core processor, and in a specific implementation, may be composed of a processor assembly including a plurality of processing circuits. Additionally, it should be noted that the processor (702) may not necessarily be composed of physical hardware when the network function (700) is implemented in an instance form according to another embodiment.

[0199] According to one embodiment, the processor (702) is electrically, operatively, or communicatively coupled to the network interface (701) so as to control the network interface (701).

[0200] The processor (702) may include at least one processor (or processor circuitry), and at least one processor may perform the following operations individually, collectively, or in any combination. In a particular embodiment, at least one part of the processor (702) may be included in one chip, and another part of the processor (702) may be included in a separate chip. Alternatively, at least one processor may be included in other components, such as a network interface (701) or memory (703).

[0201] The processor (702) may perform or control the operation of a network entity (700) to perform at least one or a combination thereof of the methods according to the embodiments of the present disclosure. For example, the processor (702) may control the operation of the network entity (700) to exchange control plane messages or user plane messages with terminals, base stations, or other core network entities via wireless or wired communication using various protocols (e.g., NAS protocols). To this end, the processor (702) may control other components of the network entity (700) to perform various operations by executing computer programs, code, or instructions stored in memory (703).

[0202] Memory (703) is a hardware storage device capable of storing information temporarily or permanently and may include one or more storage media. For example, memory (703) may include a memory assembly comprising one or more storage media. For example, the one or more storage media may include a hard drive, flash memory, permanent memory such as ROM (read-only memory), semipermanent memory such as RAM (random access memory), cache memory, or any combination thereof.

[0203] According to one embodiment, the memory (703) may be electrically, operatively, or communically coupled with the processor (702) and may be accessed by the processor (702).

[0204] A computer program, code, or instruction that can be executed by a processor (702) may be stored in the memory (703). According to one embodiment, the computer program, code, or instruction that can be executed by the processor (702) may be stored in a single memory or separated and distributed across two or more memories. The processor (702) can perform various functions according to the embodiments of the present disclosure by executing the instruction stored in the memory (703).

[0205] According to one embodiment of the present disclosure, the operation of a network entity (700) may be caused to be performed based on at least one processor (or processing circuit) configured to perform the features of the present disclosure individually, collectively, or in any combination based on the execution of instructions (or computer program or code) stored in memory (703), based on a processing circuitry not configured to execute instructions, and / or based on a component of a processing circuitry not configured to execute instructions.

[0206] Meanwhile, although specific embodiments have been described in the detailed description of the present disclosure, it is understood that various modifications are possible within the scope of the present disclosure. Therefore, the scope of the present disclosure should not be limited to the described embodiments, but should be defined by the claims set forth below as well as equivalents thereof.

Claims

1. A method performed by a mobility management entity of a mobile communication system, A step of performing capability negotiation regarding whether voice services through said NTN are supported with a terminal connected to a GEO (geostationary earth orbit) satellite and a non-terrestrial network (NTN); and A method comprising the step of transmitting a bearer modification request to a P-GW (packet data network gateway) to pre-allocate resources for a bearer associated with the IMS (IP (internet protocol) multimedia subsystem) service of the terminal before a voice call of the terminal is initiated.

2. In Paragraph 1, Whether voice services via the above NTN are supported is, An indicator indicating that voice services via the above NTN are supported, A combination of an indicator indicating that an IMS voice service is supported on a PS (packet switched) session and a determination that the terminal is camping on the NTN, and A combination of voice domain preference and usage settings of the above terminal and a judgment that the above terminal is camping on the NTN A method characterized by being identified based on at least one of the following.

3. In Paragraph 1, The above NTN supports NB-IoT (narrowband internet of things), and The above bearer belongs to a PDN (packet data network) connection or PDU (protocol data unit) session associated with an APN (access point name) for IMS services, and A method characterized in that the above-mentioned bearer is a non-GBR (non-guaranteed bit rate) bearer.

4. In Paragraph 1, The above bearer modification request includes information for updating QoS (quality of service) information or packet filter information for traffic for voice services through the above NTN, and The above QoS information includes a QCI (QoS class identifier) ​​value or a QCI value dedicated to voice services through the above NTN, and A method characterized in that the above packet filter information includes TFT (traffic flow template) information.

5. A method performed by the P-CSCF (proxy-call session control function) of a mobile communication system, A step of receiving an IMS (IP (Internet Protocol) Multimedia Subsystem) registration request message from a terminal connected to a non-terrestrial network (NTN) associated with a geostationary earth orbit (GEO) satellite; A step of transmitting to the terminal a registration response message containing address information of an IMS-AGW (IMS access gateway) or FQDN (fully qualified domain name) information determined based on access type information included in the IMS registration request message; A step of setting the IMS-AGW to perform voice codec transcoding of the voice call in response to receiving an SDP (session description protocol) answer message for a voice call requested by the terminal; and A method comprising the step of sending a Diameter AAR (authorization authentication request) message requesting resource reservation for the above voice call to a policy control entity.

6. In Paragraph 5, The above NTN supports NB-IoT (narrowband internet of things), and A method characterized in that the address information of the IMS-AGW or the FQDN information is determined based on the access type information indicating access to the NTN.

7. In Paragraph 5, The above Diameter AAR message is, QoS (quality of service) information including a QCI (QoS class identifier) ​​value dedicated to voice services through the above NTN, Information instructing the setup of a voice call through the above NTN, and Voice codec information for the above voice call A method characterized by including at least one of the following.

8. In Paragraph 5, A method further comprising the step of identifying that the terminal has requested a setup for a voice call through the NTN based on the access type information indicating the NTN access.

9. In a mobility management entity of a mobile communication system, At least one transceiver; At least one processor connected to the above at least one transceiver so as to be able to communicate; and The mobility management entity is connected to communicate with at least one processor and is executable individually or in any combination of the at least one processor. Performing capability negotiation with a terminal connected to a non-terrestrial network (NTN) associated with a geostationary earth orbit (GEO) satellite regarding whether voice services through the said NTN are supported, and A mobility management entity comprising a memory that stores a command causing a bearer modification request to be transmitted to a P-GW (packet data network gateway) to pre-allocate resources for a bearer associated with the IMS (IP (internet protocol) multimedia subsystem) service of the terminal before a voice call of the terminal is initiated.

10. In Paragraph 9, Whether voice services via the above NTN are supported is, An indicator indicating that voice services via the above NTN are supported, A combination of an indicator indicating that an IMS voice service is supported on a PS (packet switched) session and a determination that the terminal is camping on the NTN, and A combination of voice domain preference and usage settings of the above terminal and a judgment that the above terminal is camping on the NTN A mobility management entity characterized by being identified based on at least one of the following.

11. In Paragraph 9, The above NTN supports NB-IoT (narrowband internet of things), and The above bearer belongs to a PDN (packet data network) connection or PDU (protocol data unit) session associated with an APN (access point name) for IMS services, and A mobility management entity characterized in that the above-mentioned bearer is a non-GBR (non-guaranteed bit rate) bearer.

12. In Paragraph 9, The above bearer modification request includes information for updating QoS (quality of service) information or packet filter information for traffic for voice services through the above NTN, and The above QoS information includes a QCI (QoS class identifier) ​​value or a QCI value dedicated to voice services through the above NTN, and A mobility management entity characterized by the above packet filter information including TFT (traffic flow template) information.

13. In the P-CSCF (proxy-call session control function) of a mobile communication system, At least one transceiver; At least one processor connected to the above at least one transceiver so as to be able to communicate; and The P-CSCF is connected to communicate with at least one processor and is executable individually or in any combination of the at least one processor. A terminal connected to a non-terrestrial network (NTN) associated with a geostationary earth orbit (GEO) satellite receives an IMS (IP (Internet Protocol) multimedia subsystem) registration request message, and A registration response message including address information or FQDN (fully qualified domain name) information of an IMS-AGW (IMS access gateway) determined based on access type information included in the above IMS registration request message is transmitted to the terminal, and In response to receiving an SDP (session description protocol) answer message for a voice call requested by the terminal, the IMS-AGW is configured to perform voice codec transcoding of the voice call, and A P-CSCF comprising memory that stores a command causing a Diameter AAR (authorization authentication request) message requesting resource reservation for the above voice call to be sent to a policy control entity.

14. In Paragraph 13, The above NTN supports NB-IoT (narrowband internet of things), and The address information of the above IMS-AGW or the above FQDN information is determined based on the access type information indicating access to the above NTN, and The above Diameter AAR message is, QoS (quality of service) information including a QCI (QoS class identifier) ​​value dedicated to voice services through the above NTN, Information instructing the setup of a voice call through the above NTN, and Voice codec information for the above voice call P-CSCF characterized by including at least one of the following.

15. In Paragraph 13, The instruction executable individually or in any combination of the above-mentioned at least one processor is the P-CSCF A P-CSCF characterized by further causing the terminal to identify that it has requested a setup for a voice call through the NTN, based on the access type information indicating the NTN access.