Terminals and network nodes

By transmitting packets without IP headers between the terminal and P-GW in geostationary satellite communication, the method enhances wireless resource utilization efficiency by reducing IP header overhead.

JP2026182238APending Publication Date: 2026-11-19NTT DOCOMO INC
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
JP2025078294
Authority / Receiving Office
JP · JP
Patent Type
Applications
Current Assignee / Owner
Filing Date
2025-05-08
Publication Date
2026-11-19

AI Technical Summary

Technical Problem

The large header size of IP packets in voice communication via geostationary satellites reduces the efficiency of wireless resource utilization.

Method used

A method where packets are transmitted without an IP header between the terminal and the P-GW, with the P-GW adding and removing IP headers for uplink and downlink packets respectively, and the terminal obtains its IP address from the P-GW to generate SIP and SDP messages.

Benefits of technology

Prevents a decrease in wireless resource utilization efficiency by minimizing IP header overhead during voice communication.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure 2026182238000001_ABST
    Figure 2026182238000001_ABST
Patent Text Reader

Abstract

In a wireless communication system using geostationary satellites, the objective is to prevent a decrease in the efficiency of wireless resource utilization caused by packet headers added to data during voice communication. [Solution] The terminal has a transmitting unit that sends a first message to a first network node that includes a request to establish a PDN (Packet Data Network) connection, which appears as an IP (Internet Protocol) connection from an external system perspective and as a connection that sends and receives packets without an IP header from the perspective of the device itself, and a receiving unit that receives a second message from the first network node that includes the IP address of the terminal as seen from an external system perspective and information accepting the request, and the transmitting unit sends a packet without an IP header to the first network node or the second network node, which may or may not include information generated using the IP address of the terminal itself.
Need to check novelty before this filing date? Find Prior Art

Description

TECHNICAL FIELD

[0001] The present invention relates to a terminal and a network node in a communication system. BACKGROUND ART

[0002] In 3GPP (registered trademark) (3rd Generation Partnership Project), studies are underway on a radio communication scheme called 5G or NR (New Radio) (hereinafter, this radio communication scheme is referred to as "5G" or "NR") in order to achieve further increases in system capacity, further increases in data transmission speed, further reduction of delay in the radio section, and the like. In 5G, various radio technologies are being studied to satisfy the requirement that the delay in the radio section is 1 ms or less while realizing a throughput of 10 Gbps or higher.

[0003] In NR, a network architecture including 5GS (5G System) corresponding to EPS (Evolved Packet System), which is the core network in the LTE (Long Term Evolution) network architecture, and NG-RAN (Next Generation - Radio Access Network) corresponding to E-UTRAN (Evolved Universal Terrestrial Radio Access Network), which is the RAN (Radio Access Network) in the LTE network architecture, is being studied (for example, Non-Patent Document 1).

[0004] In addition, as an IMS (IP Multimedia Subsystem) architecture that supports the data channel capability of a terminal, specifications for an IMS data channel network are being studied (for example, Non-Patent Document 2).

[0005] Furthermore, in 3GPP Rel-20, discussions regarding voice communication via geostationary satellites (Geostationary Earth Orbit, GEO) are being conducted. [Prior art documents] [Non-patent literature]

[0006] [Non-Patent Document 1] 3GPP TS 23.501 V19.3.0(2025-03) [Non-Patent Document 2] 3GPP TS 23.228 V19.2.0(2024-12) [Non-Patent Document 3] 3GPP TS 23.401 V19.2.0(2025-03) [Overview of the Initiative] [Problems that the invention aims to solve]

[0007] In voice communication via geostationary satellites (GEO), before considering a configuration using 5GS (5G System), we are first considering a configuration using terminals compatible with EPS (Evolved Packet System) and NB (Narrow Band)-IoT (Internet of Things). In this voice communication, a method is being considered in which SIP (Session Initiation Protocol) signals are transferred from the terminal to the MME (Mobility Management Entity) via the control plane, and from the MME to the P-CSCF (Proxy-Call Session Control Function) via the S-GW (Serving-Gateway) and P-GW (Packet Data Network Gateway) using the user plane, and the voice media is transferred using the user plane as usual.

[0008] Here, both SIP signals and voice media are IP (Internet Protocol) based, and the large header size of IP packets becomes a problem that reduces the efficiency of wireless resource utilization.

[0009] The present invention has been made in view of the above points, and aims to prevent a decrease in the efficiency of utilizing wireless resources due to packet headers added to data (i.e., SIP signals or voice media) during voice communication in a wireless communication system using geostationary satellites. [Means for solving the problem]

[0010] According to the disclosed technology, a transmitting unit sends a first message to a first network node that includes a request to establish a PDN (Packet Data Network) connection, which appears to be an IP (Internet Protocol) connection from an external system perspective and appears to be a connection that sends and receives packets without an IP header from the perspective of the device itself; and a receiving unit that receives a second message from the first network node that includes the IP address of the device itself from an external system perspective and information accepting the request, wherein the transmitting unit is provided with a terminal that sends packets without an IP header to the first network node or the second network node, which may or may not include information generated using the device's IP address. [Effects of the Invention]

[0011] According to the disclosed technology, in a wireless communication system using geostationary satellites, it is possible to prevent a decrease in the efficiency of wireless resource utilization caused by packet headers added to data during voice communication. [Brief explanation of the drawing]

[0012] [Figure 1] This is a diagram illustrating example (1) of a communication system. [Figure 2] This is a diagram illustrating example (2) of a communication system. [Figure 3] This diagram illustrates an example of a communication system in a roaming environment. [Figure 4] This diagram illustrates an example of an IMS data channel network. [Figure 5] This is a diagram showing an example from NTN (1). [Figure 6] It is a diagram illustrating Example (2) of NTN. [Figure 7] It is a diagram illustrating Example (3) of NTN. [Figure 8] It is a diagram illustrating an example of the first sequence diagram according to the embodiment of the present invention. [Figure 9] It is a diagram illustrating an example of the second sequence diagram according to the embodiment of the present invention. [Figure 10] It is a diagram illustrating an example of the third sequence diagram according to the embodiment of the present invention. [Figure 11] It is a diagram illustrating an example of the fourth sequence diagram according to the embodiment of the present invention. [Figure 12] It is a diagram illustrating an example of the fifth sequence diagram according to the embodiment of the present invention. [Figure 13] It is a diagram illustrating an example of the functional configuration of the base station 10 and the network node 30 according to the embodiment of the present invention. [Figure 14] It is a diagram illustrating an example of the functional configuration of the terminal 20 according to the embodiment of the present invention. [Figure 15] It is a diagram illustrating an example of the hardware configuration of the base station 10, the terminal 20, and the network node 30 according to the embodiment of the present invention. [Mode for Carrying Out the Invention]

[0013] Hereinafter, embodiments of the present invention will be described with reference to the drawings. Note that the embodiments described below are examples, and the embodiments to which the present invention is applied are not limited to the following embodiments.

[0014] In the operation of the radio communication system according to the embodiment of the present invention, existing techniques are appropriately used. However, the existing techniques are, for example, existing LTE, but are not limited to existing LTE. In addition, unless otherwise specified, the term "LTE" used in the present specification has a broad meaning including LTE-Advanced, systems subsequent to LTE-Advanced (e.g., NR), or wireless LAN (Local Area Network).

[0015] Furthermore, in the embodiments of the present invention, "configuring" wireless parameters may mean that predetermined values ​​are pre-configured, or that wireless parameters notified from the network node 30 or terminal 20 are configured.

[0016] Figure 1 is a diagram illustrating example (1) of a communication system. As shown in Figure 1, a 5G communication system consists of a terminal 20 (UE) and multiple network nodes 30. Hereafter, one network node 30 will be assumed to correspond to each function, however, one network node 30 may implement multiple functions, or multiple network nodes 30 may implement one function. Furthermore, the "connection" described below may be a logical connection or a physical connection.

[0017] The RAN (Radio Access Network) is a network node 30 having radio access functionality, which may include a base station 10, and is connected to the UE, AMF (Access and Mobility Management Function), and UPF (User plane function). The AMF is a network node 30 having functions such as terminating the RAN interface, terminating the NAS (Non-Access Stratum), registration management, connection management, reachability management, and terminal mobility management. The UPF is a network node 30 interconnected with the DN (Data Network) and having functions related to processing user plane data, such as PDU (Protocol Data Unit) session points to the outside, packet routing and forwarding, and user plane QoS (Quality of Service) handling. The UPF and DN constitute a network slice. In the wireless communication network in the embodiment of the present invention, multiple network slices are constructed.

[0018] AMF is connected to UE, RAN, SMF (Session Management function), NSSF (Network Slice Selection Function), NEF (Network Exposure Function), NRF (Network Repository Function), UDM (Unified Data Management), AUSF (Authentication Server Function), PCF (Policy Control Function), and AF (Application Function). AMF, SMF, NSSF, NEF, NRF, UDM, AUSF, PCF, and AF are network nodes 30 that are interconnected via interfaces based on their respective services: Namf, Nsmf, Nnssf, Nnef, Nnrf, Nudm, Nausf, Npcf, and Naf.

[0019] SMF is a network node 30 that has functions such as session management, IP (Internet Protocol) address allocation and management for UEs, DHCP (Dynamic Host Configuration Protocol) functionality, ARP (Address Resolution Protocol) proxy, and roaming functionality. NEF is a network node 30 that has the function of notifying other NFs (Network Functions) of capabilities and events. NSSF is a network node 30 that has functions such as selecting the network slice to which the UE connects, determining the allowed NSSAI (Network Slice Selection Assistance Information), determining the NSSAI to be set, and determining the AMF set to which the UE connects. PCF is a network node 30 that has the function of controlling network policy. AF is a network node 30 that has the function of controlling application servers. NRF is a network node 30 that has the function of discovering NF instances that provide services. UDM is a network node 30 that manages subscriber data and authentication data. UDM is connected to UDR (User Data Repository) which holds the said data. Furthermore, the UDM may include, or be able to connect to, an ARPF (Authentication credential Repository and Processing Function) that has the function of a repository and processing for authentication credentials, and a SIDF (Subscription Identifier De-concealing Function) that has the function of decrypting subscriber identifiers.

[0020] Similarly, regarding the Evolved Packet System (EPS), a communication system in 4G, see Non-Patent Document 3. Figure 2 is a diagram illustrating example (2) of a communication system. As shown in Figure 2, the EPS is equipped with a Mobility Management Entity (MME) that manages the movement of the UE, a Packet Data Network Gateway (P-GW) that processes user plane data with the external network, a Serving Gateway (S-GW) that processes user plane data between the E-UTRAN, including the base station 10 (eNB), and the P-GW, and a Home Subscriber Server (HSS) that manages subscriber data and authentication data.

[0021] Figure 3 is a diagram illustrating an example of a communication system in a roaming environment. As shown in Figure 3, the network consists of a terminal 20 (UE) and multiple network nodes 30. Hereafter, one network node 30 will be assigned to each function, however, one network node 30 may implement multiple functions, or multiple network nodes 30 may implement one function. Furthermore, the "connection" described below may be a logical connection or a physical connection.

[0022] The RAN is a network node 30 with wireless access capabilities and is connected to the UE, AMF, and UPF. The AMF is a network node 30 with functions such as RAN interface termination, NAS termination, registration management, connection management, reachability management, and mobility management. The UPF is a network node 30 interconnected with the DN and has functions such as external PDU session point, packet routing and forwarding, and user plane QoS handling. The UPF and DN constitute a network slice. In the wireless communication network according to the embodiment of the present invention, multiple network slices are constructed.

[0023] AMF is connected to UE, RAN, SMF, NSSF, NEF, NRF, UDM, AUSF, PCF, AF, and SEPP (Security Edge Protection Proxy). AMF, SMF, NSSF, NEF, NRF, UDM, AUSF, PCF, and AF are network nodes 30 that are interconnected via interfaces based on their respective services: Namf, Nsmf, Nnssf, Nnef, Nnrf, Nudm, Nausf, Npcf, and Naf.

[0024] SMF is a network node 30 with functions such as session management, UE IP address assignment and management, DHCP functionality, ARP proxy, and roaming functionality. NEF is a network node 30 with the function of notifying other NFs of capabilities and events. NSSF is a network node 30 with functions such as selecting the network slice to which the UE connects, determining the allowed NSSAI, determining the NSSAI to be configured, and determining the AMF set to which the UE connects. PCF is a network node 30 with the function of controlling network policy. AF is a network node 30 with the function of controlling application servers. NRF is a network node 30 with the function of discovering NF instances that provide services. SEPP is an opaque proxy that filters control plane messages between PLMNs (Public Land Mobile Networks). vSEPP shown in Figure 3 is SEPP in the visited network, and hSEPP is SEPP in the home network.

[0025] As shown in Figure 3, the UE is in a roaming environment connected to the RAN and AMF in the VPLMN (Visited PLMN). The VPLMN and HPLMN (Home PLMN) are connected via vSEPP and hSEPP. The UE can communicate with the HPLMN's UDM, for example, via the VPLMN's AMF.

[0026] Figure 4 is a diagram illustrating an example of an IMS data channel network. As shown in Figure 4, the IMS data channel network consists of a terminal 20 (UE) and multiple network nodes 30 in both the originating network and the terminating network. Hereafter, one network node 30 will be assumed to correspond to each function, but one network node 30 may implement multiple functions, or multiple network nodes 30 may implement one function. Also, the "connection" described below may be a logical connection or a physical connection. The network node 30 has, for example, the following functions as described in Non-Patent Literature 2.

[0027] The IMS-AGW (Access Gateway) is a network node 30 that has the functions of a gateway between the UE and the IMS network, as well as functions related to voice communication access processing.

[0028] P-CSCF (Proxy-Call Session Control Function) is a network node 30 that has proxy functions between the UE and the IMS network, as well as access control functions for voice communications.

[0029] S-CSCF (Serving-Call Session Control Function) is a network node 30 that has functions related to session control for the UE.

[0030] The I-CSCF (Interrogate-Call Session Control Function) is a network node 30 that is the connection point on the receiving side between networks in the IMS network (for example, the sending side and the receiving side), and has functions such as forwarding received SIP requests to the S-CSCF of its own network.

[0031] The IMS AS (IP Multimedia Subsystem Application Server) is a network node 30 in the IMS network that has functions such as communicating with the DCSF for event notification and receiving data channel control instructions from the DCSF and communicating with the MF. The IMS AS also receives a registration request for the communication termination point from the DCSF (Data Channel Signaling Function), converts the received registration request into a SIP Register, and sends it to the S-CSCF (Serving-Call Session Control Function). Furthermore, the IMS AS converts a data channel establishment request received from the DCSF into a SIP INVITE and sends it to the S-CSCF.

[0032] DCSF (Data Channel Signaling Function) is a network node 30 that has functions such as receiving event reports from IMS-AS and deciding whether or not to allow the provision of data channel services, managing bootstrap data channels, and HTTP web server functionality.

[0033] The Media Function (MF) is a network node 30 in the IMS network that has functions such as media resource management and data channel media traffic forwarding. The MF also processes media between the Data Channel Application Server (DCAS), which is the communication termination point, and the destination termination point based on configuration information received from the Data Channel Application Server (DCSF). The MF may also be called the Data Channel Media Function (DCMF). The MF may also be called the Multimedia Resource Function (MRF).

[0034] DCAS (Data Channel Application Server) is a network node 30 that has functions such as being a communication termination point for media and signaling in the IMS network.

[0035] Figure 5 shows an example of NTN (1). NTN (Non-Terrestrial Network) uses non-terrestrial equipment such as satellites to provide services to areas that cannot be covered by terrestrial 5G networks, mainly due to cost constraints. Furthermore, NTN can provide more reliable services. For example, it is envisioned to be applied to IoT (Inter-of-Things), ships, buses, trains, and critical communications. NTN also has scalability through efficient multicast or broadcast.

[0036] As an example from NTN, as shown in Figure 5, satellite 10A can retransmit signals from ground base station 10B to provide service to areas where ground base stations are not located, such as mountainous regions. In this example, the base station is deployed on the ground, but a configuration in which the base station is deployed on a satellite is also being considered.

[0037] Furthermore, the terrestrial 5G network may have the configuration described below. The terrestrial 5G network includes one or more base stations 10 and terminals 20. The base station 10 is a communication device that provides one or more cells and performs wireless communication with the terminals 20. A configuration in which the base station 10 is deployed on a satellite is also being considered.

[0038] Terminal 20 is a communication device equipped with wireless communication capabilities, such as a smartphone, mobile phone, tablet, wearable device, or M2M (Machine-to-Machine) communication module. Terminal 20 receives control signals or data from base station 10 via DL and transmits control signals or data to base station 10 via UL, thereby utilizing various communication services provided by the wireless communication system.

[0039] Figure 6 shows an example of NTN (2). The area per cell or beam in NTN is very large compared to terrestrial networks (TN). The connection between satellite 10A and NTN gateway 10B is called a feeder link, and the connection between satellite 10A and UE20 is called a service link.

[0040] As shown in Figure 6, the delay difference between the near-side UE20A and the far-side UE20B is, for example, 10.3 ms for GEO (Geosynchronous orbit) and 3.2 ms for LEO (Low Earth orbit). The beam size in NTN is, for example, 3500 km for GEO and 1000 km for LEO.

[0041] Figure 7 shows an example of NTN (3). As shown in Figure 7, NTN is realized by a satellite in space or an aircraft in the air. For example, a GEO satellite may be located at an altitude of 35,786 km and have a geostationary orbit. For example, a LEO satellite may be located at an altitude of 500-2000 km and orbit with a period of 88-127 minutes. For example, a HAPS (High Altitude Platform Station) may be located at an altitude of 8-50 km and perform a circular flight.

[0042] As shown in Figure 7, GEO satellites, LEO satellites, and HAPS aircraft may be connected to ground stations (gNBs) via gateways. While base stations are deployed on the ground here, configurations where base stations are deployed on satellites are also conceivable. In that case, equipment including base stations deployed on satellites may be connected to ground-based network nodes via gateways. Furthermore, the service area may increase in the order of HAPS, LEO, and GEO.

[0043] For example, NTN can extend the coverage of a 5G network to areas that are not yet served or are already served. Also, for example, NTN can improve the continuity, availability, and reliability of services in ships, buses, trains, or other critical communications. The fact that it is NTN may be indicated by the transmission of a specific parameter to terminal 20.

[0044] (Examples) This document outlines a procedure for preventing a decrease in the efficiency of radio resource utilization caused by packet headers added to data during voice communication in a radio communication system using geostationary satellites.

[0045] In this voice communication, packets without an IP header are transmitted between the terminal and the P-GW. The P-GW adds an IP header to the uplink (UL) packets and removes the IP header from the downlink (DL) packets. The terminal obtains its own IP address information from the P-GW and uses this information when creating SIP and SDP messages. The terminal also obtains the IMS AGW's IP address from the information contained in the SDP and notifies the P-GW. In other words, packets within the 4G wireless system and core network do not have an IP header, while packets sent to network nodes (P-CSCF, IMS AGW, etc.) of the EPS external system (IMS) have an IP header. This procedure may also be applied to wireless systems other than 4G, such as 5G and 6G.

[0046] The details of this procedure will be explained below using sequence diagrams. The requests, responses, and notifications sent and received in the following procedures may be referred to as messages (e.g., request messages) or packets.

[0047] (Request for PDN connection) The procedure for requesting a PDN connection is described below. Hereinafter, the PDN connection may also be referred to as PDN connection or PDN connectivity. Figure 8 shows an example of a first sequence diagram in an embodiment of the present invention. The processing of each step is described below.

[0048] S201: Terminal 20 recognizes that when using NB-IoT, two PDN (Packet Data Network) connections (one for SIP messages and the other for voice media) are required for voice calls, and sets the PDN connection pair ID. The PDN connection pair ID is an identifier used to identify the two related PDN connections.

[0049] S202: Terminal 20 may request a Control Plane Only Indicator while holding a Data Radio Bearer (DRB). A Control Plane Only Indicator is an example of a configuration instruction to use the control plane for sending and receiving user data.

[0050] S203: Terminal 20 decides to request an IPv6 (Internet Protocol version 6) PDN connection and CN (Core Network) header handling. CN header handling means that no headers will be added to packets between Terminal 20 and P-GW30E. P-GW30E will add an IP header to the uplink (UL) packets and remove the IP header from the downlink (DL) packets. Alternatively, Terminal 20 may request a Non-IP PDN connection and CN (Core Network) header handling, which means that packets without IP headers will be transmitted between the terminal and the P-GW, and the P-GW will add an IP header to the uplink (UL) packets and remove the IP header from the downlink (DL) packets.

[0051] S204: Terminal 20 sends a message (ULInformationTransfer) to base station 10 to forward a request for PDN connectivity. This request includes a setting instruction to set the PDN type to IPv6, a setting instruction to set the access point name to "ims", a setting instruction to use the control plane for sending and receiving user data (Control Plane Only Indicator), a setting instruction to set the PDN connection pair ID to "xx", and a request for CN header handling. In other words, this message requests the establishment of a PDN connection that appears as an IP (Internet Protocol) connection from the perspective of the system outside, and as a connection that sends and receives packets without an IP header from the perspective of terminal 20. This message is also written as, for example, ULInformationTransfer(dedicatedInfoNAS(PDN connectivity request(PDN type(IPv6), Access point name=ims, Extended request type(Control Plane Only Indicator requested), PDN connectivity pair ID=xx, Extended protocol configuration options(CN header handling request)))).

[0052] S205: Base station 10 sends a message (Uplink NAS Transport) to MME30A that forwards the PDN connection request received in S204. This message is written as, for example, Uplink NAS Transport(NAS-PDU(PDN connectivity request(PDN type(IPv6), Access point name=ims, Extended request type(Control Plane Only Indicator requested), PDN connectivity pair ID=xx, Extended protocol configuration options(CN header handling request)))).

[0053] S206: Based on the "Control Plane Only Indicator" included in the PDN connection request received in S205, MME30A decides to set a configuration instruction (Control Plane Only PDN Connection Indication) to use the control plane for sending and receiving user data in the PDN connection.

[0054] S207:MME30A sends a message to S-GW30D requesting the creation of a PDN connection (Create Session Request). This message includes configuration instructions to set the PDN type to IPv6, the access point name to "ims", the configuration instruction to use the control plane for sending and receiving user data in the PDN connection (Control Plane Only PDN Connection Indication), the configuration instruction to set the PDN connection pair ID to "xx", and a request for CN header handling. This message is also written as, for example, Create Session Request(PDN Type(IPv6), Access Point Name=ims, Control Plane Only PDN Connection Indication, PDN connectivity pair ID=xx, Extended protocol configuration options(CN header handling request)).

[0055] S208: S-GW30D sends a message to P-GW30E requesting the creation of the PDN connection received in S207 (Create Session request).

[0056] S209:P-GW30E sends a message (CC (Credit-Control Request)-Request) to PCRF30F requesting information regarding policies and billing rules. This message includes information that the destination is ims, a configuration instruction to use the control plane for sending and receiving user data in the PDN connection (Control Plane Only PDN Connection Indication), and a configuration instruction to set the PDN connection pair ID to "xx". This message is also written as, for example, CC-Request(Called-Station-Id (ims), Control Plane Only PDN Connection Indication, PDN connectivity pair ID=xx).

[0057] S210: PCRF30F recognizes, based on the message received in S209, that the requested PDN connection will be used only for exchanging SIP messages and not for sending or receiving voice media.

[0058] S211: PCRF30F sends a CC-answer message to P-GW30E in response to the message received in S209.

[0059] S212:P-GW30E recognizes that CN header handling is required for the PDN connection requested in S208.

[0060] S213: Regarding the PDN connection requested in S208, the P-GW30E recognizes the IP address assigned to terminal 20 and stores that IP address in its own device.

[0061] S214: Regarding the PDN connection requested in S208, the P-GW30E recognizes the IP address of the P-CSCF to be connected to and stores that IP address in its own device.

[0062] S215: P-GW30E recognizes that, in the PDN connection requested in S208, the access point name is "ims" and based on the PDN connection pair ID, the IP address of the P-CSCF recognized in S214 will be used for CN header handling.

[0063] S216: P-GW30E sends a response message (Create Session Response) to S-GW30D for the message received in S208. This response message includes the IPv6 IP address assigned to terminal 20 for the PDN connection and an acquisition of CN header handling (CN header handling accepted indication). This response message may also indicate acceptance of the PDN connection request received in S208. In addition, this response message may include, for example, Create Session Response(PDN Address Allocation (<IPv6 address> This is referred to as "Extended protocol configuration options (CN header handling accepted indication)").

[0064] S217: S-GW30D sends a response message (Create Session Response) to MME30A for the message received in S207. This response message includes the IPv6 IP address assigned to terminal 20 for the PDN connection and acceptance of the CN header handling. The response message also includes, for example, Create Session Response(PDN Address Allocation (<IPv6 address> This is referred to as "Extended protocol configuration options (CN header handling accepted indication)").

[0065] S218: MME30A sends a message (Downlink NAS Transport) to base station 10 that forwards a request to activate the default EPS bearer. The request includes the IPv6 IP address assigned to terminal 20 for the PDN connection, a configuration instruction to use the control plane for sending and receiving user data in the PDN connection, and acceptance of CN header handling. The response message is, for example, Downlink NAS Transport (NAS-PDU(Activate Default EPS Bearer Context Request(PDN address (<IPv6 address> This is indicated as "Control plane only indication, Extended protocol configuration options (CN header handling accepted indication))))"

[0066] S219: The base station 10 sends a message (DLInformationTransfer) to the terminal 20 that forwards a request to activate the default EPS bearer. The request includes the IPv6 IP address assigned to the terminal 20 for the PDN connection, a configuration instruction to use the control plane for sending and receiving user data in the PDN connection, and acceptance of CN header handling. The request may also indicate acceptance of the PDN connection request received in S204. The response message may also include, for example, DLInformationTransfer (dedicatedInfoNAS(Activate Default EPS Bearer Context Request(PDN address (<IPv6 address> This is indicated as "Control plane only indication, Extended protocol configuration options (CN header handling accepted indication))))"

[0067] S220: Terminal 20 recognizes the IPv6 IP address assigned to its device for the requested PDN connection based on the message received in S219, and stores that IP address in its device in order to include it in the SIP message sent in subsequent steps, including S221.

[0068] S221: Terminal 20 sends a message (ULInformationTransfer) to base station 10 that forwards acceptance of the activation of the default EPS bearer. This message is written as, for example, ULInformationTransfer(dedicatedInfoNAS(Activate Default EPS Bearer Context Accept)).

[0069] S222: Base station 10 sends a message (Uplink NAS Transport) to MME30A that forwards acceptance of the activation of the default EPS bearer. This message is written as, for example, Uplink NAS Transport (NAS-PDU (Activate Default EPS Bearer Context Accept)).

[0070] (IMS initial registration) The procedure for the initial registration of terminal 20 to IMS is described below. For the procedure in the existing specifications, please refer to section 5.3.4B.2 of Non-Patent Document 3. Figure 9 is a diagram showing an example of a second sequence diagram in an embodiment of the present invention. The processing of each step is described below.

[0071] S301: Terminal 20 is assumed to generate a SIP message without an IP header using the assigned IP address based on the result of the PDN connection request described in Figure 8.

[0072] S302: Terminal 20 sends a message (ULInformationTransfer) to base station 10 that includes the IMS initial registration (SIP Register) in a NAS (Non-Access Stratum) message (i.e., control plane) and forwards it. This message is written as, for example, ULInformationTransfer(dedicatedInfoNAS(ESM Data Transport(User data container(SIP Register)))).

[0073] S303: Base station 10 sends a message (Uplink NAS Transport) to MME30A that includes the IMS initial registration (SIP Register) in a NAS message (i.e., control plane) and forwards it. This message is written as, for example, Uplink NAS Transport (NAS-PDU(ESM Data Transport(User data container(SIP Register)))).

[0074] S304: MME30A sends a SIP Register to P-GW30E via S-GW30D.

[0075] S305: P-GW30E generates an IP packet containing the IMS initial registration (SIP Register) received in S304. Here, based on the information obtained in the PDN connection request procedure described in Figure 8, P-GW30E includes the IP address of P-CSCF30G as the destination address and the IP address of terminal 20 as the source address in the IP header of the IP packet.

[0076] S306: P-GW30E sends an IP packet containing the IMS initial registration (SIP Register) generated in S305 to P-CSCF30G.

[0077] S307:P-CSCF30G sends the IMS initial registration (SIP Register) to S-CSCF30H.

[0078] S308:S-CSCF30H sends a message to HSS30C requesting to obtain the IMS authentication information for terminal 20 (Nhss_ImsUEAuthenticate_Get request).

[0079] S309:HSS30C sends a response message (Nhss_ImsUEAuthenticate_Get response) to S-CSCF30H for the message received in S308.

[0080] S310:S-CSCF30H sends a message (401 Unauthorized) to P-CSCF30G indicating authentication failure.

[0081] S311: P-CSCF30G sends a message (401 Unauthorized) to P-GW30E indicating authentication failure.

[0082] S312:P-GW30E removes the IP header from the message received in S311 and generates a message indicating authentication failure (401 Unauthorized) without adding an IP header.

[0083] S313: P-GW30E sends an authentication failure message (401 Unauthorized) to MME30A via S-GW30D, which does not include the IP header generated in S312.

[0084] S314: MME30A sends a message (Downlink NAS Transport) to base station 10 that includes the authentication failure message (401 Unauthorized) received in S313 in a NAS message (i.e., control plane) and forwards it. This message is, for example, written as Downlink NAS Transport (NAS-PDU(ESM Data Transport(User data container(401 Unauthorized))).

[0085] S315: Base station 10 sends a message (DLInformationTransfer) to terminal 20 that includes the authentication failure message (401 Unauthorized) received in S314 as a NAS message (i.e., control plane) and forwards it. This message is written as, for example, DLInformationTransfer (dedicatedInfoNAS(ESM Data Transport(User data container(401 Unauthorized))).

[0086] S316: Terminal 20 sends SIP Register again, and if authentication is successful, IMS registration is completed. At this point, steps S301 to S315 are repeated, but instead of a message indicating authentication failure (401 Unauthorized), a message indicating authentication success (200 OK) is sent to terminal 20.

[0087] (IMS voice call) The procedure for initiating an IMS voice call will be described below. Figure 10 shows an example of a third sequence diagram in an embodiment of the present invention. The processing of each step will be described below.

[0088] S401: Terminal 20 is assumed to generate a SIP message without an IP header using the assigned IP address in the PDN connection, based on the result of the PDN connection request described in Figure 8.

[0089] S402: Terminal 20 sends a message (ULInformationTransfer) to base station 10 that includes a voice call request (SIP INVITE) in a NAS message (i.e., control plane) and forwards it. This message is written as, for example, ULInformationTransfer(dedicatedInfoNAS(ESM Data Transport(User data container(SIP INVITE)))).

[0090] S403: Base station 10 sends a message (Uplink NAS Transport) to MME30A that includes a voice call request (SIP INVITE) in a NAS message (i.e., control plane) and forwards it. This message is written as, for example, Uplink NAS Transport(NAS-PDU(ESM Data Transport(User data container(SIP INVITE)))).

[0091] S404: MME30A sends a voice call request (SIP INVITE) to P-GW30E via S-GW30D.

[0092] S405: P-GW30E generates an IP packet containing the voice call request (SIP INVITE) received in S404. Here, based on the information obtained in the PDN connection request procedure described in Figure 8, P-GW30E includes the IP address of P-CSCF30G as the destination address and the IP address of terminal 20 as the source address in the IP header of the IP packet.

[0093] S406: P-GW30E sends an IP packet containing the voice call request (SIP INVITE) generated in S405 to P-CSCF30G.

[0094] S407:P-CSCF30G sends a voice call request (SIP INVITE) to S-CSCF30H.

[0095] S408: S-CSCF30H sends a voice call request (SIP INVITE) to I-CSCF30J.

[0096] S409: I-CSCF30J sends a message (SIP 183 Session Progress) to S-CSCF30H indicating that voice communication is being configured.

[0097] S410:S-CSCF30H sends a message (SIP 183 Session Progress) to P-CSCF30G indicating that voice communication is being configured.

[0098] S411:P-CSCF30G sends a message to PCRF30F requesting policy control (AA (Authorization and Authentication Request)-Request) for the PDN connection.

[0099] S412: PCRF30F recognizes that the PDN connection is for SIP message exchange only and will not be used for voice media. PCRF30F also assumes that terminal 20 will establish a PDN connection for voice media when it receives SIP 183 Session Progress. PCRF30F also decides that it does not need to send any requests to P-GW30D and will send a normal success response to P-CSCF30G.

[0100] S413:PCRF30F sends a response message (AA-answer) to P-CSCF30G for the message received in S411. This message includes the policy decision result applied to the PDN connection.

[0101] S414: P-CSCF30G sends a message (SIP 183 Session Progress) to P-GW30E indicating that voice communication is being configured. The IP address of terminal 20 is set as the destination for this message.

[0102] S415: P-GW30E removes the IP header from the message received in S414 and generates a message indicating voice communication setup (SIP 183 Session Progress) without adding an IP header.

[0103] S416: P-GW30E sends a message (SIP 183 Session Progress) to MME30A via S-GW30D, which was generated in S415 and does not include an IP header, indicating that voice communication is being configured.

[0104] S417: MME30A sends a message (Downlink NAS Transport) to base station 10 that includes the message (SIP 183 Session Progress) received in S416 indicating that voice communication is being set up, in a NAS message (i.e., control plane) and forwards it. This message is written as, for example, Downlink NAS Transport(NAS-PDU(ESM Data Transport(User data container(SIP 183 Session Progress))).

[0105] S418: Base station 10 sends a message (DLInformationTransfer) to terminal 20 that includes the message (SIP 183 Session Progress) received in S417 indicating that voice communication is being set up, in a NAS message (i.e., control plane) and forwards it. This message is written as, for example, DLInformationTransfer(dedicatedInfoNAS(ESM Data Transport(User data container(SIP 183 Session Progress)))).

[0106] S419: Terminal 20 decides to establish an IMS PDN connection for voice media.

[0107] S420: Terminal 20 may request a Control Plane Only Indicator while holding the DRB. The Control Plane Only Indicator is an identifier that requests that the PDN connection be established using only the control plane. Note that the following procedure is an example where this is not requested.

[0108] S421: When terminal 20 requests the establishment of an IMS PDN connection, it uses DNN=ims_media to ensure that the appropriate default QoS is applied.

[0109] S422: Terminal 20 decides to request an IPv6 (Internet Protocol version 6) PDN connection and CN (Core Network) header handling. CN header handling means that no headers will be added to packets between Terminal 20 and P-GW30E. P-GW30E will add an IP header to the uplink (UL) packets and remove the IP header from the downlink (DL) packets. Alternatively, Terminal 20 may request a Non-IP PDN connection and CN (Core Network) header handling, which means that packets without IP headers will be transmitted between the terminal and P-GW, and P-GW will request that it add an IP header to the uplink (UL) packets and remove the IP header from the downlink (DL) packets.

[0110] S423: Terminal 20 extracts the IP address of the IMS AGW30K, which is set in the SDP answer to the negotiation proposal, contained in the message (SIP 183 Session Progress) received in S418 indicating that voice communication is being set up.

[0111] S424: Terminal 20 sends a message (ULInformationTransfer) to base station 10 to forward a PDN connectivity request. This PDN connectivity request includes a setting instruction to set the access point name to "ims_media", a setting instruction to set the PDN connection pair ID to "xx", a request for CN header handling, and the destination address for CN header handling. In other words, the message requests the establishment of a PDN connection that appears as an IP connection from an external system perspective, and as a connection that sends and receives packets without an IP header from terminal 20's perspective, by requesting that the IP address of IMS AGW30K be used as the destination. This message is written as, for example, ULInformationTransfer(dedicatedInfoNAS(PDN connectivity request(Access point name=ims_media, PDN connectivity pair ID=xx, Extended protocol configuration options(CN header handling request), Destination Address for CN header handling))).

[0112] S425: Base station 10 sends an Uplink NAS Transport message to MME30A to forward a PDN connectivity request. This PDN connectivity request includes a setting instruction to set the access point name to "ims_media", a setting instruction to set the PDN connection pair ID to "xx", a request for CN header handling, and the destination address for CN header handling. This message is written as, for example, Uplink NAS Transport(NAS-PDU(PDN connectivity request(Access point name=ims_media, PDN connectivity pair ID=xx, Extended protocol configuration options(CN header handling request), Destination Address for CN header handling))).

[0113] S426:MME30A determines whether terminal 20 has available user plane resources. For example, this operation may be based on an existing specification.

[0114] S427: If the determination in S426 is YES (retained), MME30A decides to establish an IMS PDN connection using user plane resources; otherwise, it decides to establish another IMS PDN connection using the control plane without using user plane resources.

[0115] The following describes the operation when the decision in S426 is YES (retained) and an IMS PDN connection is established using user plane resources. Figure 11 shows an example of a fourth sequence diagram in an embodiment of the present invention. The processing of each step will be described below.

[0116] S431:MME30A sends a message to S-GW30D requesting the creation of a PDN connection (Create Session Request). This message includes a configuration instruction to set the access point name to "ims_media", a configuration instruction to set the bearer's QoS level to QCI (QoS Class Identifier)=11, a configuration instruction to set the PDN connection pair ID to "xx", and a request for CN header handling. This message is also written as, for example, Create Session Request(Access Point Name=ims_media, Bearer Context to be created (Bearer Level QoS(QCI=11)), PDN connectivity pair ID=xx, Extended protocol configuration options(CN header handling request), Destination Address for CN header handling).

[0117] S432: S-GW30D sends a message to P-GW30E requesting the creation of the PDN connection received in S431 (Create Session request).

[0118] S433:P-GW30E sends a CC-Request message to PCRF30F requesting information regarding policies and billing rules. This message includes information that the destination is ims_media, a setting instruction to set the QoS level to QCI=11, and a setting instruction to set the PDN connection pair ID to "xx". This message is also written as, for example, CC-Request(Called-Station-Id (ims_media), QoS-Information (QoS-Class-Identifier=11), PDN connectivity pair ID=xx).

[0119] S434: PCRF30F recognizes that two PDN connections are linked via a PDN connection pair ID, and that this PDN connection is for voice media. PCRF30F also confirms that a PDN connection for SIP message exchange and a PDN connection for voice media are associated.

[0120] S435: PCRF30F links the contexts of two PDN connections corresponding to the PDN connection pair ID. Subsequently, when PCRF30F receives a request from P-CSCF30G for the first PDN connection, PCRF 30F also applies that request to the second PDN connection. This ensures that PDN connections for voice media are properly managed in conjunction with SIP signaling.

[0121] S436: PCRF30F sends a message (CC-answer) to P-GW30E in response to the message received in S433. This message is written as, for example, CC-Answer(QoS-Information (QoS-Class-Identifier=11)).

[0122] S437:P-GW30E recognizes that CN header handling is required for the PDN connection requested in S432.

[0123] S438: Regarding the PDN connection requested in S432, the P-GW30E recognizes the IP address assigned to terminal 20 and stores that IP address in its own device.

[0124] S439: Regarding the PDN connection requested in S432, the P-GW30E recognizes the IP address of the IMS AGW to connect to and stores that IP address in its own device.

[0125] S440:P-GW30E recognizes that, in the PDN connection requested in S432, the access point name is "ims_media" and based on the PDN connection pair ID, the IP address of the IMS AGW recognized in S439 will be used for CN header handling.

[0126] S441: P-GW30E sends a response message (Create Session Response) to S-GW30D for the message received in S432. This response message includes information indicating that the bearer's QoS level has been set to QCI=11, and is written as, for example, Create Session Response(Bearer Contexts created (Bearer Level QoS(QCI=11))).

[0127] S442: S-GW30D sends a response message (Create Session Response) to MME30A for the message received in S431. This response message includes information indicating that the bearer's QoS level has been set to QCI=11, and is written as, for example, Create Session Response(Bearer Contexts created (Bearer Level QoS(QCI=11))).

[0128] S443:MME30A sends a message to base station 10 requesting the configuration of the wireless access bearer (E-RAB Setup Request). This message includes a setting instruction to set the bearer's QoS level to QCI=11, and is written as, for example, E-RAB Setup Request(E-RAB to be Setup List(E-RAB To Be Setup Item(E-RAB Level QoS Parameters(QCI=11), NAS-PDU (Activate Default EPS Bearer Context Request)))).

[0129] S444: Base station 10 sends a message to terminal 20 regarding RRC reconfiguration (RRCConnectionReconfiguration), which includes a request to activate the default EPS bearer. This message is written, for example, as RRCConnectionReconfiguration (dedicatedInfoNAS(Activate Default EPS Bearer Context Request)).

[0130] S445: Terminal 20 sends a response message (RRCConnectionReconfigurationComplete) to base station 10 for the message received in S444.

[0131] S446: Base station 10 sends a response message (E-RAB Setup response) to MME30A for the message received in S443.

[0132] S447: Terminal 20 sends a message (ULInformationTransfer) to base station 10 that forwards acceptance of the activation of the default EPS bearer. This message is written as, for example, ULInformationTransfer(dedicatedInfoNAS(Activate Default EPS Bearer Context Accept)).

[0133] S448: Base station 10 sends a message (Uplink NAS Transport) to MME30A that forwards acceptance of the activation of the default EPS bearer. This message is written as, for example, Uplink NAS Transport (NAS-PDU (Activate Default EPS Bearer Context Accept)).

[0134] S449:MME30A sends a message to S-GW30D requesting a modification of the bearer (Modify Bearer request).

[0135] S450: S-GW30D sends a response message (Modify Bearer response) to MME30A for the message received in S449.

[0136] The following describes the process following S450. Figure 12 is a diagram showing an example of a fifth sequence diagram in an embodiment of the present invention. The process of each step will be described below.

[0137] S461: Procedures for exchanging SIP messages (such as Provisional Response Acknowledgment (PRACK) and Update) are performed based on existing specifications.

[0138] S462:I-CSCF30J sends an acknowledgment (SIP 200 OK) to S-CSCF30H.

[0139] S463: S-CSCF30H sends an acknowledgment (SIP 200 OK) to P-CSCF30G.

[0140] S464:P-CSCF30G sends a message to PCRF30F requesting policy control (AA-Request) for the PDN connection.

[0141] S465: When PCRF30F receives a request for the first PDN connection, it also checks the context for the second PDN connection. PCRF30F then sends an appropriate request for the second PDN connection to P-GW30E.

[0142] S466:PCRF30F sends a response message (AA-answer) to P-CSCF30G for the message received in S464. This message includes the policy decision result applied to the PDN connection.

[0143] S467:PCRF30F sends a message to P-GW30E requesting re-authentication (RA (Re-Authorization)-Request) for the PDN connection.

[0144] S468: P-GW30E sends a response message (RA-answer) to PCRF30F for the message received in S467.

[0145] S469: P-CSCF30G sends an acknowledgment (SIP 200 OK) to P-GW30E.

[0146] S470:P-GW30E generates an acknowledgment (SIP 200 OK) for the message received in S469, removing the IP header and not adding an IP header.

[0147] S471: P-GW30E sends an acknowledgment (SIP 200 OK) without an IP header, generated in S469, to MME30A via S-GW30D.

[0148] S472: MME30A sends a message (Downlink NAS Transport) to base station 10 that includes the acknowledgment (SIP 200 OK) received in S471 in a NAS message (i.e., control plane) and forwards it. This message is written as, for example, Downlink NAS Transport(NAS-PDU(ESM Data Transport(User data container(SIP 200 OK))).

[0149] S473: Base station 10 sends a message (DLInformationTransfer) to terminal 20 that includes the acknowledgment (SIP 200 OK) received in S472 in a NAS message (i.e., control plane) and forwards it. This message is written as, for example, DLInformationTransfer(dedicatedInfoNAS (ESM Data Transport(User data container(SIP 200 OK))).

[0150] S474: Based on existing specifications, procedures for exchanging SIP messages (such as acknowledgments (SIP 200 OK, ACK)) and establishing voice calls will be carried out.

[0151] S475: Terminal 20 generates audio media that does not include an IP header.

[0152] S476: Terminal 20 transmits the voice media packet, which was generated in S475 and does not have an IP header, to P-GW30E via the base station and S-GW30D.

[0153] S477: P-GW30E generates an IP packet containing the voice media received in S476. Here, P-GW30E includes the IP address of IMS-AGW30K as the destination address and the IP address of terminal 20 as the source address in the IP header of the IP packet.

[0154] S478:P-GW30E sends an IP packet containing the voice media generated in S477 to IMS AGW30K.

[0155] S479: IMS AGW30K sends an IP packet containing voice media to P-GW30E.

[0156] S480:P-GW30E removes the IP header from the IP packet received in S479 and generates audio media without an IP header.

[0157] S481:P-GW30E transmits a voice media packet to terminal 20 via S-GW30D and the base station, without the IP header generated by S480.

[0158] In the above embodiment, the transmission and reception of messages between the terminal 20 and P-GW30E via the base station, MME30A, and S-GW30D may also be performed between the terminal 20 and P-GW30E via the base station and S-GW30D. Furthermore, the transmission and reception of voice media between the terminal 20 and P-GW30E via the base station and S-GW30D may also be performed between the terminal 20 and P-GW30E via the base station, MME30A, and S-GW30D.

[0159] The above embodiment makes it possible to prevent a decrease in the efficiency of utilizing wireless resources due to packet headers added to data during voice communication in a wireless communication system using geostationary satellites.

[0160] (Device configuration) Next, an example of the functional configuration of the base station 10, network node 30, and terminal 20 that perform the processes and operations described above will be explained. The base station 10, network node 30, and terminal 20 include the functions to implement the embodiments described above. However, the base station 10, network node 30, and terminal 20 may each have only some of the functions in the embodiments.

[0161] <Base station 10 and network node 30> Figure 13 shows an example of the functional configuration of a base station 10 and a network node 30 in an embodiment of the present invention. As shown in Figure 13, the base station 10 has a transmitting unit 110, a receiving unit 120, a setting unit 130, and a control unit 140. The functional configuration shown in Figure 13 is merely an example. The functional classifications and names of the functional units can be anything as long as they can perform the operations according to the embodiment of the present invention. The network node 30 may have a functional configuration similar to that of the base station 10. Furthermore, a network node 30 having multiple different functions in the system architecture may be composed of multiple network nodes 30 separated by function.

[0162] The transmitting unit 110 includes the function of generating a signal to be transmitted to the terminal 20 or other network node 30 and transmitting the signal by wire or wireless. The receiving unit 120 includes the function of receiving various signals transmitted from the terminal 20 or other network node 30 and obtaining information from the received signal, for example, higher layer information. A communication unit including the transmitting unit 110 and the receiving unit 120 may be configured.

[0163] The setting unit 130 stores pre-configured setting information and various setting information to be transmitted to the terminal 20. The content of the setting information includes, for example, information related to the operation described in the embodiment.

[0164] The control unit 140 performs control related to setting, instructing, and notifying the operation described in the embodiment. The signal transmission function unit of the control unit 140 may be included in the transmission unit 110, and the signal reception function unit of the control unit 140 may be included in the reception unit 120.

[0165] <Terminal 20> Figure 14 shows an example of the functional configuration of a terminal 20 in an embodiment of the present invention. As shown in Figure 14, the terminal 20 has a transmitting unit 210, a receiving unit 220, a setting unit 230, and a control unit 240. The functional configuration shown in Figure 14 is merely an example. Any functional classification and functional unit names are acceptable as long as they can perform the operations according to the embodiment of the present invention. The transmitting unit 210 and the receiving unit 220 may be collectively referred to as the communication unit.

[0166] The transmitting unit 210 creates a transmission signal from the transmission data and transmits the transmission signal wirelessly. The receiving unit 220 wirelessly receives various signals and acquires signals from higher layers from the received physical layer signals. The receiving unit 220 also has the function of receiving PSS, SSS, PBCH, DL / UL / SL control signals, etc. transmitted from the base station 10. The setting unit 230 also stores pre-set setting information. The content of the setting information is, for example, information related to the operation described in the embodiment.

[0167] As described in the embodiment, the control unit 240 performs control related to setting, instructing, and notifying the operations described in the embodiment. The signal transmission function unit of the control unit 240 may be included in the transmission unit 210, and the signal reception function unit of the control unit 240 may be included in the reception unit 220.

[0168] (Hardware configuration) The block diagrams (Figures 13 and 14) used in the description of the above embodiments show functional units. These functional blocks (components) are realized by hardware, software, or a combination thereof. Furthermore, the method of realizing each functional block is not particularly limited. That is, each functional block may be realized using one device that is physically or logically coupled, or it may be realized using two or more physically or logically separated devices that are directly or indirectly connected (for example, using wired, wireless, etc.). A functional block may also be realized by combining the above one device or the above multiple devices with software.

[0169] For example, a base station, terminal, network node, etc. in one embodiment of the present disclosure may function as a computer that processes the wireless communication method of the present disclosure. Figure 15 is a diagram showing an example of the hardware configuration of a base station and a terminal according to one embodiment of the present disclosure. The base station 10 and terminal 20 described above may be physically configured as a computer device including a processor 1001, memory 1002, storage 1003, communication device 1004, input device 1005, output device 1006, bus 1007, etc.

[0170] In this disclosure, any two terms selected from the set of terms such as circuit, device, unit, module, chip, and means may be used interchangeably. The hardware configuration of the base station 10 and terminal 20 may include one or more of the devices shown in the figures, or it may be configured to omit some of the devices.

[0171] Each function in the base station 10 and terminal 20 is realized by loading predetermined software (programs) onto hardware such as the processor 1001 and memory 1002, which allows the processor 1001 to perform calculations and control communication by the communication device 1004, or control the reading, writing, or both of the reading and writing of data in the memory 1002 and storage 1003.

[0172] The processor 1001 controls the entire computer, for example, by running the operating system. The processor 1001 may be composed of a central processing unit (CPU) that includes interfaces with peripheral devices, control units, arithmetic units, registers, etc. For example, the baseband signal processing unit 104 and call processing unit 105 described above may be implemented by the processor 1001. Although only one processor 1001 is shown in the diagram, there may be multiple processors.

[0173] Furthermore, the processor 1001 reads programs (program code), software modules, data, etc., from the storage 1003, the communication device 1004, or both the storage 1003 and the communication device 1004 into the memory 1002, and executes various processes accordingly. The program used is one that causes the computer to execute at least a part of the operations described in the above embodiment. For example, the control unit 401 of the terminal 20 may be implemented by a control program stored in the memory 1002 and running on the processor 1001, and other functional blocks may be implemented similarly. The above-described various processes have been explained as being executed by one processor 1001, but they may be executed simultaneously or sequentially by two or more processors 1001. The processor 1001 may be implemented by one or more chips. The program may be transmitted from the network via a telecommunications line, or provided to the computer device via the communication device 1004, for example.

[0174] Furthermore, this disclosure also provides a computer program product, which includes a computer program. This computer program product may implement the steps of the method described in the above embodiments when the computer program is executed by a computer (e.g., a processor 1001).

[0175] Memory 1002 is a computer-readable recording medium and may consist of, for example, ROM (Read Only Memory), EPROM (Erasable Programmable ROM), EEPROM (Electrically Erasable Programmable ROM), RAM (Random Access Memory), or a combination of at least two of these. Memory 1002 may also be called a register, cache, main memory, etc. Memory 1002 can store executable programs (program code), software modules, etc., for implementing a wireless communication method according to one embodiment of this disclosure.

[0176] The storage 1003 is a computer-readable recording medium and may consist of, for example, an optical disc such as a CD-ROM (Compact Disc ROM), a hard disk drive, a flexible disk, a magneto-optical disk (e.g., a compact disc, a digital multipurpose disc, a Blu-ray® disc), a smart card, flash memory (e.g., a card, a stick, a key drive), a floppy® disk, a magnetic strip, or at least a combination of these. The storage 1003 may also be called an auxiliary storage device. The above-mentioned storage medium may be, for example, a database, server, or other suitable medium including memory 1002, storage 1003, or both memory 1002 and storage 1003.

[0177] The communication device 1004 is hardware (transceiver / receiver device) for communicating between computers via a wired network, a wireless network, or both wired and wireless networks, and is also referred to as a network device, network controller, network card, or communication module, for example. The communication device 1004 may include a high-frequency switch, duplexer, filter, frequency synthesizer, or a combination of at least two of these. For example, the aforementioned transmit / receive antenna 101, amplifier unit 102, transmit / receive unit 103, or transmission path interface 106 may be implemented by the communication device 1004. The transmit / receive unit 103 may be implemented in physically or logically separated form, consisting of a transmit unit 103a and a receive unit 103b.

[0178] The input device 1005 is an input device that accepts input from an external source (e.g., a keyboard, mouse, microphone, switch, button, sensor, or a combination of at least two of these). The output device 1006 is an output device that outputs to an external source (e.g., a display, speaker, LED lamp, or a combination of at least two of these). The input device 1005 and the output device 1006 may be configured as an integrated unit (e.g., a touch panel).

[0179] Furthermore, each device, such as the processor 1001 and memory 1002, is connected by a bus 1007 for communicating information. The bus 1007 may be configured using a single bus, or different buses may be configured for each device.

[0180] Furthermore, the base station 10 and terminal 20 may be configured with hardware such as a microprocessor, a digital signal processor (DSP), an ASIC (Application Specific Integrated Circuit), a PLD (Programmable Logic Device), an FPGA (Field Programmable Gate Array), a GPU (Graphics Processing Unit), an NPU (Neural Processing Unit), or a combination of at least two of these, and some or all of each functional block may be realized by such hardware. For example, the processor 1001 may be implemented using at least one of these hardware components.

[0181] O-CU may be interpreted as CU, control device, communication device, aggregation device, central device, management device, etc. Each of these devices may be rephrased as a unit, node, etc. For example, O-CU may be interpreted as a central unit, aggregation node, etc.

[0182] O-DU may be interpreted as DU, control device, communication device, distributed device, high-PHY device, etc. Each of these devices may be rephrased as a unit, node, etc. For example, O-DU may be interpreted as a distributed unit, distributed node, etc.

[0183] O-RU may be interpreted as RU, radio equipment, RF (Radio Frequency) equipment, low PHY equipment, etc. Each piece of equipment may be rephrased as a unit, node, etc. For example, O-RU may be interpreted as a radio unit, radio node, etc.

[0184] SMO may be interpreted as control device, communication device, or management device. Each of these devices may be rephrased as a unit, node, etc. For example, SMO may be interpreted as a management unit, management node, etc.

[0185] Non-Real Time RIC may be interpreted as RIC, non-real-time control device, control device, or communication device. Each of these devices may be rephrased as a unit, node, etc. For example, Non-Real Time RIC may be interpreted as a control unit, control node, etc.

[0186] Near-Real Time RIC may be interpreted as RIC, quasi-real-time control device, control device, or communication device. Each of these devices may be rephrased as a unit, node, etc. For example, Non-Real Time RIC may be interpreted as a control unit, control node, etc.

[0187] <Note> The following supplementary information shows the correspondence between network nodes and components and the terms and steps described in the examples. The names of the network nodes are examples only and are not limiting. (Additional note 1) The transmitting unit sends a first message to the first network node (=MME30A) that includes a request to establish a PDN (Packet Data Network) connection, which appears to be an IP (Internet Protocol) connection from an external system perspective, and appears to be a connection that sends and receives packets without an IP header from the perspective of the device itself, (S204) A receiving unit receives a second message from the first network node, which includes the IP address of the terminal from an external perspective and information accepting the request, (S218-S219) It has, The transmitting unit transmits to the first network node (=MME30A) or the second network node (S-GW30D) a packet that includes (or does not include) information generated using the terminal's IP address (=SDP / SIP message (S221)) or does not include (=voice media (S476)), and does not have an IP header. Terminal. (Additional note 2) A receiving unit that receives a first message (=SDP answer in SIP 183 Progress) containing the destination IP (Internet Protocol) address of the voice media from the first network node (=MME30A) or the second network node (=S-GW30D), and (S418) A second message is sent to the first network node requesting the establishment of a PDN connection, which appears to be an IP connection from an external system perspective and to the device itself as a connection that sends and receives packets without an IP header, requesting that the IP address be used as the destination (S424) Terminal. (Additional note 3) The receiving unit receives a first message from the first network node (=S-GW30D) that includes a request to establish a PDN connection, which appears as an IP (Internet Protocol) connection from an external system perspective, and as a connection that sends and receives packets without an IP header from the terminal's perspective, (S208) A transmitting unit that transmits a second message to the first network node, which includes the IP address of the terminal from an external system perspective and information accepting the request, (S216) A network node (=P-GW30E) that has this feature. (Additional note 4) The receiving unit receives packets transmitted by the terminal in the PDN connection that do not have an IP header, (S403-S404) The system further includes a control unit that generates an IP packet to which the IP header is added to the packet that does not have the aforementioned IP header, and which includes the IP address of the terminal, which is the source IP address, and the destination IP address, (S405) The transmitting unit transmits the IP packets to an external network node (=P-CSCF30G or IMS AGW30K) (S406, S478). The network node described in Appendix 3. (Additional note 5) The first message includes the destination IP address (= the IP address of P-CSCF30G), (S208) The network node described in Appendix 4. (Additional note 6) The receiving unit receives an IP packet from a network node outside the system, with the IP address of the terminal set as the destination, (S414, S479) The control unit removes the IP header from the IP packet (S415, S480) The transmitting unit sends a packet without an IP header to the terminal (S416, S481). The network node described in Appendix 4.

[0188] In any of the above configurations, it is possible to prevent a decrease in the efficiency of utilizing radio resources due to packet headers added to data during voice communication in a wireless communication system using geostationary satellites.

[0189] (Supplement to the embodiment) While embodiments of the present invention have been described above, the disclosed invention is not limited to such embodiments, and those skilled in the art will understand various modifications, alterations, alternatives, substitutions, etc. Specific numerical examples have been used to facilitate understanding of the invention, but unless otherwise specified, these numerical values ​​are merely examples, and any appropriate values ​​may be used. The division of items in the above description is not essential to the present invention, and matters described in two or more items may be combined as needed, and matters described in one item may be applied to matters described in another item (as long as they do not contradict each other). The boundaries of functional units or processing units in the functional block diagram do not necessarily correspond to the boundaries of physical parts. The operation of multiple functional units may be physically performed by one part, or the operation of one functional unit may be physically performed by multiple parts. Regarding the processing procedures described in the embodiments, the order of processing may be changed as long as it does not contradict each other. For the convenience of explaining the processing, the base station 10 and terminal 20 have been described using functional block diagrams, but such devices may be implemented in hardware, software, or a combination thereof. The software operated by the processor of the base station 10 according to an embodiment of the present invention and the software operated by the processor of the terminal 20 according to an embodiment of the present invention may be stored in random access memory (RAM), flash memory, read-only memory (ROM), EPROM, EEPROM, registers, hard disk (HDD), removable disk, CD-ROM, database, server, or any other suitable storage medium.

[0190] Each aspect / embodiment described in this disclosure is a combination of LTE (Long Term Evolution), LTE-A (LTE-Advanced), IMT-Advanced (International Mobile Telecommunications-Advanced), 4G (4th generation mobile communication system), 5G (5th generation mobile communication system), 5G-A (5G-Advanced), 6G (6th generation mobile communication system), xG (xth generation mobile communication system (where x is, for example, an integer or decimal)), FRA (Future Radio Access), NR (new Radio), NX (New radio access), FX (Future generation radio access), O-RAN (Open Radio Access Network), W-CDMA (Wideband Code Division Multiple Access) (registered trademark), GSM (Global System for Mobile communications) (registered trademark), CDMA2000, UMB (Ultra Mobile Broadband), and IEEE (Institute of Electrical and Electronics). Engineers) 802.11, IEEE 802.11x (where x is any string such as b, a, g, n, ac, ax, be, bn, etc., and x=n is also called Wi-Fi 4, x=ac is Wi-Fi 5, x=ax is Wi-Fi 6 or Wi-Fi 6E, x=be is Wi-Fi 7, x=bn is Wi-Fi 8, etc. Note that Wi-Fi is a registered trademark.This may be applied to systems based on technologies such as ), IEEE 802.16 (WiMAX®), IEEE 802.20, UWB (Ultra-WideBand), Bluetooth®, network virtualization technologies (e.g., NFV (Network Function Virtualization), SFC (Service Function Chaining), SDN (Software Defined Networking)), or LPWA (Low Power Wide Area). Furthermore, each aspect / embodiment described in this disclosure may be applied to systems based on a combination of at least two of these technologies. Of course, "based on" means not only systems that utilize the technology in question, but also systems that utilize extensions or modifications of the technology in question.

[0191] In this disclosure, any two terms selected from the set of terms such as "Base Station (BS)", "Radio Base Station", "Fixed Station", "NodeB", "eNodeB (eNB)", "gNodeB (gNB)", "Access Point (AP)", "Transmission Point (TP)", "Reception Point (RP)", "Transmission / Reception Point (TRP)", "Radio Unit (RU)", "Remote Unit (RU)", "Control Unit (CU)", "Distributed Unit (DU)", "Remote Radio Head (RRH)", "Node", "Gateway", "Ground Base Station", "Stratospheric Base Station", "Unmanned Aerial Vehicle", "High Altitude Platform Station (HAPS)", "Airborne Platform", "Panel", "Cell", "Radio Access Network (RAN)", and "Network" may be used interchangeably.

[0192] Each cell contained within a base station may be referred to as a macrocell, small cell, femtocell, picocell, serving cell, or supercell, among other terms. In this disclosure, any two terms selected from the set of terms such as "cell," "sector," "cell group," "carrier," "component carrier," "cluster," "bandwidth part (BWP)," and "carrier bandwidth" may be used interchangeably.

[0193] In this disclosure, any two terms selected from the set of terms such as "Mobile Station (MS)", "user terminal", "User Equipment (UE)", "Device", "module", and "Terminal" may be used interchangeably.

[0194] The terminal may be called a subscriber station, mobile unit, subscriber unit, wireless unit, remote unit, mobile device, wireless device, wireless communication device, remote device, mobile subscriber station, access terminal, mobile terminal, wireless terminal, remote terminal, handset, user agent, mobile client, client, router (e.g., home router, mobile router, etc.), TCU (Telematics Control Unit), or some other appropriate term.

[0195] A base station and a terminal may each consist of one or more devices. Devices constituting at least a part of each base station and terminal may be called transmitting devices, receiving devices, communication devices, etc. Devices constituting at least a part of each base station and terminal may be, but are not limited to, objects themselves such as vehicles, transport vehicles, automobiles, motorcycles, bicycles, connected cars, excavators, bulldozers, wheel loaders, dump trucks, forklifts, trains, buses, handcarts, rickshaws, ships and other watercraft, airplanes, rockets, unmanned aerial vehicles, stratospheric base stations (e.g., High Altitude Platform Stations (HAPS)), artificial satellites (e.g., Low Earth Orbit (LEO) satellites, Middle Earth Orbit (MEO) satellites, Geostationary Earth Orbit (GEO) satellites), drones (registered trademark), multicopters, quadcopters, balloons, and IoT (Internet of Things) devices (e.g., smart meters, sensors), or objects or devices mounted on such objects. Furthermore, the object in question may be a moving object (hereinafter referred to as a "moving object"; this does not exclude the possibility of the moving object being in a stationary state) or a fixedly positioned object (hereinafter referred to as a "non-moving object").

[0196] Furthermore, the term "base station" in this disclosure may be interpreted as "terminal." For example, the various aspects / embodiments of this disclosure may be applied to configurations in which communication between a base station and a terminal is replaced with communication between multiple terminals (which may be called D2D (Device-to-Device), V2X (Vehicle-to-Everything), etc.) or communication over a non-terrestrial network (NTN). In this case, the terminal 20 may have at least some of the functions of the base station 10 described above. Also, terms such as "uplink" and "downlink" may be interpreted as terms corresponding to terminal-to-terminal communication (e.g., "sidelink") or terms corresponding to NTN (e.g., feeder link or service link). For example, an uplink channel or a downlink channel may be interpreted as a sidelink channel.

[0197] Furthermore, this disclosure is also applicable when at least some of the equipment constituting the base station and terminal operates outside of the ground (for example, in the atmosphere or in outer space).

[0198] Furthermore, the term "terminal" in this disclosure may be interpreted as "base station." In this case, the base station 10 may be configured to have the same functions as the terminal 20 described above.

[0199] Information notification is not limited to the embodiments described herein and may be carried out by other methods. For example, information notification may be carried out by physical layer signaling (e.g., DCI (Downlink Control Information), UCI (Uplink Control Information)), upper layer signaling (e.g., RRC (Radio Resource Control) signaling, MAC (Medium Access Control) signaling, broadcast information (MIB (Master Information Block), SIB (System Information Block))), other signals, or at least two combinations thereof. Physical layer signaling may also be called L1 (Layer 1) control information. MAC signaling may be called, for example, a MAC control element (CE) or a MAC PDU (Protocol Data Unit). RRC signaling may also be called an RRC message or an information element (IE) within the RRC message. The RRC message may be used for purposes such as controlling an RRC connection (e.g., setup, reconfiguration, establishment, reestablishment, release, or resume), mobility, measurement reporting, or terminal capability notification, or it may be an information element within the message. Furthermore, the notification of information may be explicit or implicit. An explicit notification of information is the notification of the information itself, while an implicit notification of information may be the notification of other information or the fulfillment of certain conditions which constitutes notification of the information.Furthermore, notification of information may include not only notification between the same layer of different devices (e.g., between lower layers or upper layers of base station 10 and terminal 20), but also notification between different layers within the same or different devices (e.g., between lower and upper layers within base station 10 or terminal 20). Also, notification of information from one device to another may be carried out via one or more devices. With respect to any information described in this disclosure (e.g., variables, constants, parameters, settings), information indicating / specifying (or relating to) the value of such arbitrary information may be notified from any first device (e.g., terminal / base station) to any second device (e.g., base station / terminal), even if not specifically stated in the embodiments described above.

[0200] The processing procedures, sequences, flowcharts, etc., of each aspect / embodiment described in this disclosure may be reordered, provided they are consistent with each other. For example, the methods described in this disclosure present various step elements using exemplary order and are not limited to the specific order presented.

[0201] The specific operations described in this disclosure as being performed by a base station may, in some cases, be performed by its upper node, or by a part of it (e.g., CU, RU, or DU). It is clear that various operations performed for communication with terminals in the RAN or core network may be performed by at least a part of the base station and other network nodes other than the base station. The other network nodes may be a single node or a combination of multiple nodes. Network nodes are, for example, nodes located in various core networks such as EPC (Evolved Packet Core) and 5GC (5G Core Network), and provide one or more network functions (NFs).

[0202] Furthermore, in this disclosure, the action of "a terminal receiving information from a base station" is accompanied by the actions of "a base station transmitting the information to the terminal," "a base station generating the information," or both. Similarly, the action of "a terminal transmitting information to a base station" is accompanied by the action of "a base station receiving the information from the terminal." In addition, actions such as "a terminal is configured to..." or "a terminal is configured to..." may include the actions of "a base station transmitting configuration information regarding the terminal's settings" and "the terminal setting a predetermined action based on the configuration information."

[0203] Each aspect / embodiment described herein may be used individually, in combination, or switched between as needed during execution.

[0204] The above description of the disclosure is illustrative, and the present invention is not limited to the embodiments described herein. The disclosure can be implemented in modified and altered forms without departing from the spirit of the invention. The disclosure and its modifications and alterations are included within the scope of the present invention and its equivalents.

[0205] Any reference to elements using the designations “first,” “second,” etc., as used in this disclosure does not generally limit the quantity or order of those elements. These designations may be used in this disclosure as a convenient way to distinguish between two or more elements. Accordingly, references to the first and second elements do not imply that only two elements may be employed, or that the first element must precede the second element in any way.

[0206] Radio resources can be defined by a combination of units of resources in one or more domains, such as the time domain, frequency domain, spatial domain, code domain, and power domain.

[0207] For example, resources in the time domain may be defined by one or more time units. These one or more time units include, for example, radio frames, subframes, slots, symbols, transmission time intervals (TTI), or at least two combinations thereof, but the names of the time units are not limited to these. Furthermore, these time units may be fixed-length time units that do not depend on numerology, variable-length time units that do depend on numerology, or both. Examples of fixed-length time units include, but are not limited to, subframes consisting of one or more slots, and radio frames containing multiple subframes. Examples of variable-length time units include, but are not limited to, symbols and slots containing a fixed number of symbols. Note that a certain time unit may be divided into shorter time units. Examples of shorter time units include, but are not limited to, mini-slots consisting of fewer symbols than the number of symbols that make up a slot. The time units described above may include, for example, time units used as units for scheduling, link adaptation, etc. Furthermore, any time unit in this disclosure may be interpreted as being interchangeable with other time units.

[0208] Numerology refers to parameters that define the physical layer structure, and may be based on, for example, at least one of the subcarrier spacing (SCS), symbol length, cyclic prefix length, and sampling time.

[0209] Resources in the frequency domain may be defined, for example, by one or more frequency units. Such one or more frequency units may include, for example, subcarriers, resource blocks (RBs), bandwidth parts (BWPs), carrier bandwidths, or a combination of at least two of these, but the names of frequency units are not limited to these. Furthermore, the number of subcarriers included in a frequency unit may be a fixed number regardless of the neurology, or a variable number that changes depending on the neurology. For example, an RB may consist of a predetermined number of consecutive subcarriers in the frequency domain, and the number of subcarriers included in the RB may be the same regardless of the neurology, for example, 12, but is not limited to this. Similarly, a BWP may consist of, for example, one or more consecutive RBs within a carrier bandwidth, but is not limited to this. For terminal 20, one or more BWPs may be set within one carrier, and at least one of the BWPs may be activated. Furthermore, any frequency unit in this disclosure may be interpreted as another frequency unit.

[0210] Furthermore, resources in both the time domain and the frequency domain may be defined, for example, by one or more time / frequency units composed of time units and frequency units. Such time / frequency units are, but are not limited to, a resource element (RE) consisting of one symbol and one subcarrier, a resource element group (REG) consisting of a predetermined number of REs, or a control resource set (CORESET) consisting of a predetermined number of symbols and a predetermined number of RBs.

[0211] Furthermore, resources in the spatial domain may be defined, for example, by one or more spatial units. Such spatial units include, but are not limited to, beams, MIMO (Multi Input Multi Output) layers, antenna ports, or at least two combinations thereof.

[0212] Furthermore, resources in the code domain may be defined, for example, by one or more code units. Such code units may be, but are not limited to, cyclic shifts (CS), orthogonal spread codes (OCC), or combinations thereof.

[0213] In this disclosure, if articles are added through translation, such as a, an, and the in English, this disclosure may include the fact that the noun following these articles is plural.

[0214] In the configuration of each of the above devices, "means" may be replaced with "part," "circuit," "device," etc. [Explanation of symbols]

[0215] 10 base station 110 Transmitter 120 Receiver 130 Setting section 140 Control Unit 20 devices 210 Transmitter 220 Receiver 230 Setting section 240 Control Unit 1001 Processor 1002 Storage device 1003 Auxiliary storage device 1004 Communication device 1005 Input device 1006 Output device

Claims

1. A transmitting unit sends a first message to the first network node, which includes a request to establish a PDN (Packet Data Network) connection that appears as an IP (Internet Protocol) connection from an external system perspective, and as a connection that sends and receives packets without an IP header from the perspective of the device itself. A receiving unit receives a second message from the first network node, which includes the IP address of the terminal from an external perspective and information accepting the request. It has, The transmitting unit transmits a packet to the first network node or the second network node that may or may not contain information generated using the IP address of its own terminal, and does not include an IP header. Terminal.

2. A receiving unit that receives a first message from a first network node or a second network node, which includes the destination IP (Internet Protocol) address of the voice media, A second message is sent to the first network node, which includes a request to establish a PDN connection that appears to be an IP connection from an external system perspective and appears to be a connection that sends and receives packets without an IP header from the perspective of the device itself, requesting that the IP address be used as the destination. Terminal.

3. A receiving unit receives a first message from the first network node, which appears to be an IP (Internet Protocol) connection from an external system perspective, and appears to be a connection that sends and receives packets without an IP header from the terminal's perspective, including a request to establish a PDN connection. A transmitting unit transmits a second message to the first network node, which includes the IP address of the terminal from an external system perspective and information accepting the request. A network node that has

4. The receiving unit receives packets transmitted by the terminal in the PDN connection that do not have an IP header attached. The system further includes a control unit that generates an IP packet to which the aforementioned packet without an IP header has an IP header that includes the source IP address, which is the IP address of the terminal, and the destination IP address. The transmitting unit transmits the IP packets to a network node outside the system. The network node according to claim 3.

5. The first message includes the destination IP address, The network node according to claim 4.

6. The receiving unit receives an IP packet from a network node outside the system, with the IP address of the terminal set as the destination. The control unit removes the IP header from the IP packet. The transmitting unit sends a packet without an IP header to the terminal. The network node according to claim 4.