Network nodes, base stations, and terminals

Abstract

To define procedures for voice communications in a radio communication system using geostationary satellites, taking into account the provision that only default QoS (Quality of Service) rules are available. [Solution] The network node includes a control unit that stores the context of a PDU (Packet Data Unit) session set up by a terminal via a base station that provides NB (Narrow Band) IoT (Internet of Things) wireless access via a geostationary satellite; a receiving unit that receives a message from a first network node requesting the setting of a QoS (Quality of Service) flow for voice media communication within the PDU session, specifying a particular originating / destining IP (Internet Protocol) address; and a transmitting unit that sends a message to a second network node requesting the setting of a QoS flow for voice media communication within the PDU session, specifying that it is suitable for any originating / destining address.

Description

[Technical Field]

[0001] The present invention relates to a network node, a base station, and a terminal in a communication system. [Background Art]

[0002] In 3GPP (registered trademark) (3rd Generation Partnership Project), a radio communication system called 5G or NR (New Radio) (hereinafter, this radio communication system is referred to as "5G" or "NR") is being studied to achieve further increase in system capacity, further increase in data transmission rate, and further reduction in delay in a radio section, etc. In 5G, various radio technologies are being studied to satisfy the requirement that the delay in the radio section be 1 ms or less while achieving a throughput of 10 Gbps or more.

[0003] In NR, a network architecture including 5GC (5G Core Network) corresponding to EPC (Evolved Packet Core), which is the core network in 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 RAN (Radio Access Network) in LTE network architecture, is being studied (see, for example, Non-Patent Document 1).

[0004] Furthermore, the specifications for an IMS (IP Multimedia Subsystem) network are being considered as an IMS architecture to support the data channel capabilities of terminals (see, for example, Non-Patent Document 2). In an IMS data channel network, a DCSF (Data Channel Signaling Function) with signaling capabilities, an MF (Media Function) with media-related functions, and a DCAS (Data Channel Application Server) which is an application server are deployed on both the sending and receiving ends.

[0005] Furthermore, in 3GPP Rel-19, a challenge in realizing IMS voice terminal-satellite-UE communication is reducing the impact on existing specifications when deploying 5GC network functions and IMS components on satellites (see, for example, Non-Patent Document 3). Here, terminal-satellite-UE communication refers to terminal-to-terminal communication under routing that keeps user plane traffic within the satellite. The types of satellites dealt with are geostationary Earth Orbit (GEO), low Earth Orbit (LEO), and medium Earth Orbit (MEO). In addition, for low Earth Orbit and medium Earth Orbit satellites, there are cases where a satellite constellation is formed without using inter-satellite links (ISL), and cases where a satellite constellation is formed using inter-satellite links. [Prior art documents] [Non-patent literature]

[0006] [Non-Patent Document 1] 3GPP TS 23.501 V19.2.1(2025-01) [Non-Patent Document 2] 3GPP TS 23.228 V19.2.0(2024-12) [Non-Patent Document 3] 3GPP TR23.700-29 V19.0.0(2024-06) [Non-Patent Document 4] 3GPP TS 38.413 V18.4.0(2024-12) [Non-Patent Document 5] 3GPP TS 23.502 V19.2.0(2024-12) [Non-Patent Document 6] 3GPP TS 38.331 V18.4.0(2024-12) [Overview of the project] [Problems that the invention aims to solve]

[0007] 3GPP Rel-20 discusses the efficient use of radio resources and the use of wireless access for Narrow Band (NB) IoT (Internet of Things) in relation to voice communications via geostationary satellites (GEO). However, existing specifications stipulate that only default Quality of Service (QoS) rules are usable, and procedures that take this provision into consideration are necessary.

[0008] This invention has been made in view of the above points, and aims to define a procedure for voice communication in a radio communication system using geostationary satellites, taking into account the provision that only default QoS (Quality of Service) rules are available. [Means for solving the problem]

[0009] According to the disclosed technology, a network node is provided which includes: a control unit that stores the context of a PDU (Packet Data Unit) session established via a base station that provides NB (Narrow Band) IoT (Internet of Things) wireless access via a geostationary satellite; a receiving unit that receives a message from a first network node requesting the setting of a QoS (Quality of Service) flow for voice media communication within the PDU session, specifying a particular originating / destining IP (Internet Protocol) address; and a transmitting unit that sends a message to a second network node requesting the setting of a QoS flow for voice media communication within the PDU session, specified to match an arbitrary originating / destining address. [Effects of the Invention]

[0010] According to the disclosed technology, procedures for voice communications can be defined in a radio communication system using geostationary satellites, taking into account the provision that only default Quality of Service (QoS) rules are available. [Brief explanation of the drawing]

[0011] [Figure 1] This is a diagram illustrating an example of a communication system. [Figure 2] This diagram illustrates an example of a communication system in a roaming environment. [Figure 3] This diagram illustrates an example of an IMS data channel network. [Figure 4] This is a diagram showing an example from NTN (1). [Figure 5] This figure shows an example (2) of NTN. [Figure 6] This figure shows an example (3) of NTN. [Figure 7] This figure shows an example of a first sequence diagram in an embodiment of the present invention. [Figure 8] This figure shows an example of a second sequence diagram in an embodiment of the present invention. [Figure 9] FIG. 13 is a diagram showing an example of a third sequence diagram according to an embodiment of the present invention. [Figure 10] FIG. 14 is a diagram showing an example of a fourth sequence diagram according to an embodiment of the present invention. [Figure 11] FIG. 15 is a diagram showing an example of a fifth sequence diagram according to an embodiment of the present invention. [Figure 12] FIG. 16 is a diagram showing an example of a sixth sequence diagram according to an embodiment of the present invention. [Figure 13] FIG. 17 is a diagram showing an example of a seventh sequence diagram according to an embodiment of the present invention. [Figure 14] FIG. 18 is a diagram showing an example of an eighth sequence diagram according to an embodiment of the present invention. [Figure 15] FIG. 19 is a diagram showing an example of a ninth sequence diagram according to an embodiment of the present invention. [Figure 16] FIG. 20 is a diagram showing an example of a tenth sequence diagram according to an embodiment of the present invention. [Figure 17] FIG. 1 is a diagram showing an example of a functional configuration of a base station 10 and a network node 30 according to an embodiment of the present invention. [Figure 18] FIG. 2 is a diagram showing an example of a functional configuration of a terminal 20 according to an embodiment of the present invention. [Figure 19] FIG. 3 is a diagram showing an example of a hardware configuration of a base station 10, a terminal 20, and a network node 30 according to an embodiment of the present invention. [Figure 20] FIG. 4 is a diagram showing an example of a configuration of a vehicle 2001 according to an embodiment of the present invention. DETAILED DESCRIPTION OF THE INVENTION

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

[0013] In the operation of the wireless communication system according to the embodiments of the present invention, existing technologies may be used as appropriate. However, such existing technologies include, for example, existing LTE, but are not limited to existing LTE. Furthermore, the term "LTE" as used herein has a broad meaning that includes LTE-Advanced and LTE-Advanced and later methods (e.g., NR), or wireless LAN (Local Area Network), unless otherwise specified.

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

[0015] Figure 1 is a diagram illustrating an example of a communication system. As shown in Figure 1, the communication system 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.

[0016] 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.

[0017] 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.

[0018] 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.

[0019] Figure 2 is a diagram illustrating an example of a communication system in a roaming environment. As shown in Figure 2, the network 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.

[0020] 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.

[0021] 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.

[0022] 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 2 is SEPP in the visited network, and hSEPP is SEPP in the home network.

[0023] As shown in Figure 2, 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.

[0024] Figure 3 is a diagram illustrating an example of an IMS data channel network. As shown in Figure 3, 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, 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. The network node 30 has, for example, the following functions as described in Non-Patent Literature 2.

[0025] 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.

[0026] 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.

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

[0028] 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.

[0029] 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.

[0030] 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.

[0031] 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).

[0032] 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.

[0033] Figure 4 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.

[0034] As an example from NTN, as shown in Figure 4, 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.

[0035] 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.

[0036] 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.

[0037] Figure 5 shows an example (2) of NTN. 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.

[0038] As shown in Figure 5, 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.

[0039] Figure 6 shows an example of NTN (3). As shown in Figure 6, 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.

[0040] As shown in Figure 6, 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.

[0041] 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.

[0042] (Examples) Regarding procedures for voice communication in a radio communication system using geostationary satellites, taking into account the provision that only default QoS (Quality of Service) rules are available, three methods are described below.

[0043] (Method 1) An IMS PDU session is established before the IMS registration procedure. At this stage, the quality of service settings for the IMS PDU session (hereinafter referred to as 5QI (5G QoS Identifiler)) are not determined.

[0044] In the IMS voice calling procedure, the PCF receives a message requesting the establishment of a QoS flow for voice media, which includes information (e.g., codec2) that directly or implicitly indicates voice communication over the GEO satellite and is tied to a specific destination, i.e., specific flow information. The PCF then modifies the flow information to match the flow information for the desired destination and sends a request to the SMF to update the 5QI.

[0045] (Method 2) Before the IMS registration procedure, an IMS PDU session is established. At this point, the PCF determines that the 5QI of the IMS PDU session is for voice media. Furthermore, the PCF sends a request to the SMF to set the flow information associated with the 5QI to flow information that is suitable for the desired destination.

[0046] In the IMS voice calling procedure, the PCF receives a message requesting the establishment of a QoS flow for voice media, which includes information (e.g., codec2) that directly or implicitly indicates voice communication over the GEO satellite. The PCF recognizes that the QoS flow for voice media has already been established and does not send a request to the SMF.

[0047] (Method 3) Do not establish an IMS PDU session before the IMS registration procedure.

[0048] In the IMS voice call procedure, the P-CSCF receives a message (SIP 183 Session Progress) indicating that voice communication is being set up, which includes information (e.g., codec2) that directly or implicitly indicates voice communication over the GEO satellite.

[0049] At this point, the P-CSCF sends a device trigger to the NEF requesting the establishment of a PDU session that includes a QoS flow for voice media.

[0050] Alternatively, the system may assume that the terminal autonomously establishes an IMS PDU session before or after sending the message (SIP 183 Session Progress), and therefore does not send a device trigger to the NEF.

[0051] (Detailed explanation of Method 1) The following describes the details of the procedure based on Method 1 using a sequence diagram. Requests, responses, and notifications sent and received in the following procedures may be referred to as messages (e.g., request messages).

[0052] (NG setup) The procedure for NG setup will now be described. Figure 7 shows an example of a first sequence diagram in an embodiment of the present invention. For the procedure for NG setup in existing specifications, please refer to Section 8.7.1 of Non-Patent Document 4. The processing of each step will be described below.

[0053] S101: Base station 10 recognizes that its device is configured to provide NB IoT wireless access via geostationary satellites.

[0054] S102: Base station 10 sends an NG Setup request to AMF30B requesting the establishment of an interface between base station 10 and AMF30B, which includes information (RAT Information=nb-IoT-GEO) indicating the configuration for providing NB IoT radio access via geostationary satellites. This message is written, for example, as NG Setup request (RAT Information=nb-IoT-GEO).

[0055] S103: The AMF30B sends an NG Setup response to base station 10.

[0056] (Establishing a PDU session for IMS) The procedure for establishing a PDU session for IMS will be described. Figure 8 shows an example of a second sequence diagram in an embodiment of the present invention. For the procedure for establishing a PDU session for IMS in existing specifications, please refer to Section 4.3.2 of Non-Patent Document 6. The processing of each step will be described below.

[0057] S111: Terminal 20 sends a message (ULInformationTransfer) to base station 10 requesting the establishment / configuration of a PDU session. This message is written as, for example, ULInformationTransfer (dedicatedNAS-Message(UL NAS transport(Payload container type(N1 SM information), Payload container(PDU Session Establishment request), DNN=ims))).

[0058] S112: Base station 10 sends a message (Uplink NAS Transport) to AMF30B requesting the establishment / configuration of a PDU session. This message is written as, for example, Uplink NAS Transport(NAS-PDU(UL NAS transport(Payload container type(N1 SM information), Payload container(PDU Session Establishment request), DNN=ims))).

[0059] S113: Based on the transport information of the message received in S112, the AMF30B recognizes that a base station (nb-IoT-GEO) providing NB IoT radio access via geostationary satellites is accommodating the terminal.

[0060] S114: AMF30B sends a request message (Nsmf_PDUSession_CreateSMContext request) to SMF30C requesting the establishment / configuration of a PDU session. This request message includes setting the RAT type (ratType=nb-IoT-GEO) which indicates NB IoT radio access via a geostationary satellite. This message is written as, for example, Nsmf_PDUSession_CreateSMContext request (SmContextCreateData (Dnn=ims, n1SmMsg(PDU session establishment request), ratType=NB_IOT_GEO)).

[0061] S115: SMF30C sends a response message (Nsmf_PDUSession_CreateSMContext response) to AMF30B for the request message received in S114.

[0062] S116: SMF30C sends a request message (Npcf_SMPolicyControl_Create request) to PCF30D requesting the determination and transmission of the PDU session policy. This request message includes setting the RAT type (ratType=nb-IoT-GEO) indicating NB IoT radio access via geostationary satellite. This message is also written as, for example, Npcf_SMPolicyControl_Create request (SmPolicyContextData (ratType = NB_IOT_GEO)).

[0063] Based on the received request message, the PCF30D stores the context of the PDU session that terminal 20 established via base station 10, which provides NB IoT radio access via geostationary satellites.

[0064] S117: PCF30D sends a response message (Npcf_SMPolicyControl_Create response) to SMF30C for the request message received in S116.

[0065] S118: SMF30C sends a request message (PFCP Session Establishment request) to UPF30A for the establishment of a user data transfer path.

[0066] S119: UPF30A sends a response message (PFCP Session Establishment response) to SMF30C for the request message received in S118.

[0067] S120:SMF30C sends a message to AMF30B containing information indicating acceptance of the PDU session establishment request (Namf_Communication_N1N2MessageTransfer request). This message is written, for example, as Namf_Communication_N1N2MessageTransfer request (N1N2MessageTransferReqData (n1MessageContainer (PDU Session Establishment accept) n2InfoContainer (smInfo (n2InfoContent(PDU Session Resource Setup Request Transfer))))).

[0068] S121: AMF30B sends a response message (Namf_Communication_N1N2MessageTransfer response) to SMF30E for the request message received in S120.

[0069] S122: The AMF30B sends a request message (PDU Session Resource Setup request) to the base station 10 requesting the setup of a PDU session resource. This message includes information indicating acceptance of the PDU session establishment requested in S112. This request message is written as, for example, PDU Session Resource Setup request(NAS-PDU(DL NAS transport(Payload container type(N1 SM information), Payload container(PDU Session Establishment accept)))).

[0070] S123: The base station 10 sends a message to the terminal 20 regarding the configuration of the RRC (RRCReconfiguration), which includes information indicating acceptance of the PDU session establishment requested in S111. This message is written as, for example, RRCReconfiguration(dedicatedNAS-Message(DL NAS transport(Payload container type(N1 SM information), Payload container(PDU Session Establishment accept)))).

[0071] S124: Terminal 20 sends a message to base station 10 indicating that the RRC configuration is complete (RRCReconfigurationComplete).

[0072] S125: Base station 10 sends a response message (PDU Session Resource Setup response) to AMF30B for the request message received in S124.

[0073] S126:AMF30B sends a request message (Nsmf_PDUSession_UpdateSMContext request) to SMF30C requesting a context update for the PDU session.

[0074] S127: SMF30C sends a response message (Nsmf_PDUSession_UpdateSMContext response) to AMF30B for the request message received in S126.

[0075] S128: SMF30C sends a request message (PFCP Session Modification request) to UPF30A for updating the user data transfer path.

[0076] S129: UPF30A sends a response message (PFCP Session Modification response) to SMF30C for the request message received in S128.

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

[0078] S131: Terminal 20 recognizes that it is within range of base station 10, which provides NB IoT wireless access via geostationary satellite, and sets in its SDP offer that codec2 be used as the codec for the voice media and that the packet length (ptime) of the voice media be 80ms. In addition, if codec2 is set as the codec for the voice media in the message, it may implicitly mean that it is voice communication via geostationary satellite.

[0079] S132: Terminal 20 sends a message to P-CSCF30E requesting an IMS voice call (SIP INVITE). This message includes the negotiation proposal (SDP offer) set in S131, and is written as, for example, SIP INVITE (SDP offer(codec2, ptime:80)).

[0080] S133: P-CSCF30E sends a message to S-CSCF30F requesting an IMS voice call (SIP INVITE) that was received in S132.

[0081] S134: S-CSCF30F sends a message to I-CSCF30G requesting an IMS voice call (SIP INVITE) that was received in S133.

[0082] On the receiving end, processing related to IMS voice call initiation is performed based on existing specifications.

[0083] S135: The receiving I-CSCF30G sends a message (183 Session Progress) to the sending S-CSCF30F indicating that voice communication is being set up. This message includes a negotiated response (SDP answer) that sets the codec to use codec2 and the voice media packet length (ptime) to 80ms, and is written as, for example, SIP 183 Session Progress (SDP answer(codec2, ptime:80)).

[0084] S136: S-CSCF30F sends a message (183 Session Progress) to P-CSCF30E indicating that voice communication is being configured, which was received in S135.

[0085] S137: P-CSCF30E sends a message (183 Session Progress) to terminal 20 indicating that voice communication is being set up, which was received in S136.

[0086] S138: P-CSCF30E, based on its network policy that if the codec of the audio media is codec2, then the packet length (ptime) of the audio media is 80ms, and vice versa, decides not to notify PCF30D of the packet length (ptime) of the audio media, but only that the codec of the audio media is codec2.

[0087] S139: P-CSCF30E sends a request message (Npcf_PolicyAuthorization_Create request) to PCF30D requesting authorization of the session policy, which includes flow information between the terminal and the IMS AGW and information indicating that the codec for the audio media is codec2. The message also requests that the QoS flow for the audio media be set up for the PDU session specified by the IP address of terminal 20, which is the originating terminal. The message is written as, for example, Npcf_PolicyAuthorization_Create request(AppSessionContext(ascReqData(medComponents(1, MediaComponent(medSubComps(1, MediaSubComponent(fDescs=Flow information between UE and IMS AGW)), codecs=codec2))))).

[0088] S140: PCF30D sends a response message (Npcf_PolicyAuthorization_Create response) to P-CSCF30E for the request message received in S139.

[0089] S141: Based on the information received in S139 indicating that the codec of the audio media is codec2, the PCF30D implicitly determines that it is an audio communication via a geostationary satellite and sets the QoS. For example, the PCF30D determines the value of 5QI to a value corresponding to the quality of audio communication using a geostationary satellite (5QI=11).

[0090] S142: PCF30D recognizes that the flow information should be set to the default (i.e., to suit any flow) based on the RAT type (ratType=NB_IOT_GEO) included in the request message received in S139, which indicates NB IoT radio access via a geostationary satellite.

[0091] S143:PCF30D sends a request message (Npcf_SMPolicyControl_UpdateNotify request) to SMF30C requesting an update to the session policy. The request message also requests that the flow information be updated to the default (i.e., to match the flow of any origin / destination address) and that the 5QI value be updated to a newly defined value (5QI=11) corresponding to the quality of voice communication using geostationary satellites.

[0092] S144: SMF30C sends a response message (Npcf_SMPolicyControl_UpdateNotify response) to PCF30D for the request message received in S139.

[0093] The process following S144 will now be described. Figure 10 is a diagram showing an example of a fourth sequence diagram in an embodiment of the present invention. The process of each step will be described below.

[0094] S145: SMF30C sends a request message (PFCP Session Modification request) to UPF30A for updating the user data transfer path.

[0095] S146: UPF30A sends a response message (PFCP Session Modification response) to SMF30C for the request message received in S145.

[0096] S147: SMF30C sends a message to AMF30B (Namf_Communication_N1N2MessageTransfer request) containing information indicating acceptance of the PDU session update request. The request message also requests that the flow information be updated to the default (i.e., to suit any flow) and the 5QI value be updated to a newly defined value (5QI=11) corresponding to the quality of voice communication using geostationary satellites. The message is written as, for example, Namf_Communication_N1N2MessageTransfer request (N1N2MessageTransferReqData (n1MessageContainer(n1MessageContent(PDU Session Modification Command(Authorized QoS rules(Default Packet Filter, QFI=11)))), n2InfoContainer(smInfo(n2InfoContent(PDU Session Resource Modify Request Transfer(QoS Flow Add or Modify Request List(QoS Flow Add or Modify Request Item(QoS Flow Identifier=11)))))))).

[0097] S148: AMF30B sends a response message (Namf_Communication_N1N2MessageTransfer response) to SMF30C for the request message received in S147.

[0098] S149: The AMF30B sends a request message to base station 10 requesting an update to the PDU session resource settings (PDU Session Resource Modify request). This request message also requests that the flow information be updated to the default (i.e., to suit any flow) and the 5QI value be updated to a newly defined value (5QI=11) corresponding to the quality of voice communication using geostationary satellites. This message is written, for example, as PDU Session Resource Modify Request (NAS-PDU(DL NAS transport(Payload container type(N1 SM information), Payload container(PDU Session Modification Command(Authorized QoS rules(Default Packet Filter, QFI=11))))), PDU Session Resource Modify Request Transfer(QoS Flow Add or Modify Request List(QoS Flow Add or Modify Request Item(QoS Flow Identifier=11)))).

[0099] S150: Base station 10 recognizes from the information contained in the message received in S149 (5QI=11) that the packet length (ptime) is 80ms.

[0100] S151: The base station 10 may set up Configured Grant at 80ms intervals or set up SPS (Semi-persistent-scheduling) at 80ms intervals for controlling voice media.

[0101] S152: Base station 10 sends a message related to RRC configuration (RRCReconfiguration) to terminal 20, which includes information indicating a request for updating the PDU session configuration. The request message also requests that the flow information be updated to the default (i.e., to suit any flow) and the 5QI value be updated to a newly defined value (5QI=11) corresponding to the quality of voice communication using geostationary satellites. The message is written as, for example, RRCReconfiguration(dedicatedNAS-Message(DL NAS transport(Payload container type(N1 SM information), Payload container(PDU Session Modification Command(Authorized QoS rules(default packet filter, QFI=11)))))).

[0102] S153: Terminal 20 sends a response message (RRCReconfigurationComplete) to base station 10 for the request message received in S152.

[0103] S154: Base station 10 sends a response message (PDU Session Resource Modify response) to AMF30B for the request message received in S149. This message is written as, for example, PDU Session Resource Modify Response (PDU Session Resource Modify Response Transfer).

[0104] S155:AMF30B sends a request message (Nsmf_PDUSession_UpdateSMContext request) to SMF30C requesting a context update for the PDU session. This message is written as, for example, Nsmf_PDUSession_UpdateSMContext request (SmContextUpdateData(n2SmInfo(PDU Session Resource Modify Response Transfer))).

[0105] S156: SMF30C sends a response message (Nsmf_PDUSession_UpdateSMContext response) to AMF30B for the request message received in S155.

[0106] S157: Terminal 20 sends a message to base station 10 notifying it that the PDU session update is complete. This message is written as, for example, ULInformationTransfer(dedicatedNAS-Message(UL NAS transport(Payload container type(N1 SM information), Payload container(PDU Session Modification Complete)))).

[0107] S158: Base station 10 sends a message to AMF30B notifying it that the PDU session update is complete. This message is written as, for example, Uplink NAS Transport(NAS-PDU(UL NAS transport(Payload container type(N1 SM information), Payload container(PDU Session Modification Complete)))).

[0108] S159:AMF30B sends a request message (Nsmf_PDUSession_UpdateSMContext request) to SMF30B requesting a context update for the PDU session. This request message is written as, for example, Nsmf_PDUSession_UpdateSMContext request (SmContextUpdateData(n1SmMsg(PDU Session Modification Complete))).

[0109] S160: SMF30C sends a response message (Nsmf_PDUSession_UpdateSMContext response) to AMF30B for the request message received in S161.

[0110] S161: SMF30C sends a request message (PFCP Session Modification request) to UPF30A for updating the user data transfer path.

[0111] S162: UPF30A sends a response message (PFCP Session Modification response) to SMF30C for the request message received in S161.

[0112] (Detailed explanation of Method 2) The following describes the details of the procedure based on Method 2 using sequence diagrams. Requests, responses, and notifications sent and received in the following procedures may be referred to as messages (e.g., request messages).

[0113] (NG setup) The procedure for NG setup will now be described. Figure 11 shows an example of a fifth sequence diagram in an embodiment of the present invention. For the procedure for NG setup in existing specifications, please refer to Section 8.7.1 of Non-Patent Document 4. The processing of each step will be described below.

[0114] S201: Base station 10 recognizes that its device is configured to provide NB IoT wireless access via geostationary satellites.

[0115] S202: Base station 10 sends an NG Setup request to AMF30B requesting the establishment of an interface between base station 10 and AMF30B, which includes information (RAT Information=nb-IoT-GEO) indicating the configuration for providing NB IoT radio access via geostationary satellites. This message is written, for example, as NG Setup request (RAT Information=nb-IoT-GEO).

[0116] S203: AMF30B sends an NG Setup response to base station 10A.

[0117] (Establishing a PDU session for IMS) The procedure for establishing a PDU session for IMS will be described. Figure 12 shows an example of a sixth sequence diagram in an embodiment of the present invention. For the procedure for establishing a PDU session for IMS in existing specifications, please refer to Section 4.3.2 of Non-Patent Document 6. The processing of each step will be described below.

[0118] S211: Terminal 20 sends a message (ULInformationTransfer) to base station 10 requesting the establishment / configuration of a PDU session. This message is written as, for example, ULInformationTransfer (dedicatedNAS-Message(UL NAS transport(Payload container type(N1 SM information), Payload container(PDU Session Establishment request), DNN=ims))).

[0119] S212: Base station 10 sends a message (Uplink NAS Transport) to AMF30B requesting the establishment / configuration of a PDU session. This message is written as, for example, Uplink NAS Transport(NAS-PDU(UL NAS transport(Payload container type(N1 SM information), Payload container(PDU Session Establishment request), DNN=ims))).

[0120] S213: Based on the transport information of the message received in S212, the AMF30B recognizes that a base station (nb-IoT-GEO) providing NB IoT radio access via geostationary satellites is accommodating the terminal.

[0121] S214: AMF30B sends a request message (Nsmf_PDUSession_CreateSMContext request) to SMF30C requesting the establishment / configuration of a PDU session. This request message includes a setting for the RAT type (ratType=nb-IoT-GEO) indicating NB IoT radio access via a geostationary satellite. This message is written as, for example, Nsmf_PDUSession_CreateSMContext request (SmContextCreateData (Dnn=ims, n1SmMsg(PDU session establishment request), ratType=NB_IOT_GEO)).

[0122] S215: SMF30C sends a response message (Nsmf_PDUSession_CreateSMContext response) to AMF30B for the request message received in S214.

[0123] S216: SMF30C sends a request message (Npcf_SMPolicyControl_Create request) to PCF30D requesting the determination of the PDU session policy (and the transmission of the determined policy to its own device). This request message includes setting the RAT type (ratType=nb-IoT-GEO) indicating NB IoT wireless access via geostationary satellite. This message is also written as, for example, Npcf_SMPolicyControl_Create request (SmPolicyContextData(Dnn=ims, ratType=NB_IOT_GEO)).

[0124] S217:PCF30D recognizes that, based on the RAT type (ratType=NB_IOT_GEO) indicating NB IoT radio access via geostationary satellites, the default (i.e., suitable for any flow) QoS flow should be 5QI for voice media.

[0125] S218: PCF30D sends a response message (Npcf_SMPolicyControl_Create response) to SMF30C for the request message received in S216, which includes a policy that QoS should be set for voice media communication. The response message also instructs that the flow information be set to the default (i.e., to suit any flow) and the value of 5QI be set to a newly defined value (5QI=11) corresponding to the quality of voice communication using geostationary satellites. This message is written, for example, as Npcf_SMPolicyControl_Create response(SmPolicyDecision(pccRules(pccRuleId, pccRule(flowInfos(FlowInformation(flowDescription=default)))), QoSDecs(qosId, QosData(5qi=11)))).

[0126] S219: SMF30C sends a request message (PFCP Session Establishment request) to UPF30A for the establishment of a user data transfer path.

[0127] S220: UPF30A sends a response message (PFCP Session Establishment response) to SMF30C for the request message received in S219.

[0128] S221: SMF30C sends a message to AMF30B containing information indicating acceptance of the PDU session establishment request (Namf_Communication_N1N2MessageTransfer request). This message is written, for example, as Namf_Communication_N1N2MessageTransfer request (N1N2MessageTransferReqData (n1MessageContainer (PDU Session Establishment accept) n2InfoContainer (smInfo (n2InfoContent(PDU Session Resource Setup Request Transfer))))).

[0129] S222: AMF30B sends a response message (Namf_Communication_N1N2MessageTransfer response) to SMF30E for the request message received in S221.

[0130] S223: The AMF30B sends a request message (PDU Session Resource Setup request) to the base station 10 requesting the setup of a PDU session resource. This message includes information indicating acceptance of the PDU session establishment requested in S212. The request message is written as, for example, PDU Session Resource Setup request(NAS-PDU(DL NAS transport(Payload container type(N1 SM information), Payload container(PDU Session Establishment accept)))).

[0131] S224: Base station 10 recognizes that the QoS flow of the accepted PDU session in the message received in S223 should be the quality of voice communication using geostationary satellites (5QI=11), and that the packet length (ptime) is 80ms.

[0132] S225: Base station 10 may set up Configured Grant at 80ms intervals or set up SPS (Semi-persistent-scheduling) at 80ms intervals for controlling voice media.

[0133] S226: The base station 10 sends a message to the terminal 20 relating to the RRC configuration (RRCReconfiguration), which includes information indicating acceptance of the PDU session establishment requested in S211. This message is written as, for example, RRCReconfiguration(dedicatedNAS-Message(DL NAS transport(Payload container type(N1 SM information), Payload container(PDU Session Establishment accept)))).

[0134] S227: Terminal 20 sends a message to base station 10 indicating that the RRC configuration is complete (RRCReconfigurationComplete).

[0135] S228: Base station 10 sends a response message (PDU Session Resource Setup response) to AMF30B for the request message received in S223.

[0136] S229:AMF30B sends a request message (Nsmf_PDUSession_UpdateSMContext request) to SMF30C requesting a context update for the PDU session.

[0137] S230: SMF30C sends a response message (Nsmf_PDUSession_UpdateSMContext response) to AMF30B for the request message received in S229.

[0138] S231: SMF30C sends a request message (PFCP Session Modification request) to UPF30A for updating the user data transfer path.

[0139] S232: UPF30A sends a response message (PFCP Session Modification response) to SMF30C for the request message received in S231.

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

[0141] S241: Terminal 20 recognizes that it is within range of base station 10, which provides NB IoT wireless access via geostationary satellite, and sets in its SDP offer that codec2 be used as the codec for the voice media and that the packet length (ptime) of the voice media be 80ms. In addition, if codec2 is set as the codec for the voice media in the message, it may implicitly mean that it is voice communication via geostationary satellite.

[0142] S242: Terminal 20 sends a message to P-CSCF30E requesting an IMS voice call (SIP INVITE). This message includes the negotiation proposal (SDP offer) set in S241, and is written as, for example, SIP INVITE (SDP offer(codec2, ptime:80)).

[0143] S243: P-CSCF30E sends a message to S-CSCF30F requesting an IMS voice call (SIP INVITE) that was received in S242.

[0144] S244: S-CSCF30F sends a message to I-CSCF30G requesting an IMS voice call (SIP INVITE) that was received in S243.

[0145] On the receiving end, processing related to IMS voice call initiation is performed based on existing specifications.

[0146] S245: The receiving I-CSCF30G sends a message (183 Session Progress) to the sending S-CSCF30F indicating that voice communication is being set up. This message includes a negotiated response (SDP answer) that sets the codec to use codec2 and the voice media packet length (ptime) to 80ms, and is written as, for example, SIP 183 Session Progress (SDP answer(codec2, ptime:80)).

[0147] S246: S-CSCF30F sends a message (183 Session Progress) to P-CSCF30E indicating that voice communication is being configured, which was received in S245.

[0148] S247:P-CSCF30E sends a message (183 Session Progress) to terminal 20 indicating that voice communication setup is in progress, which was received in S246.

[0149] S248: Based on the network policy that if the codec of the audio media is codec2, then the packet length (ptime) of the audio media is 80ms, and vice versa, P-CSCF30E decides not to notify PCF30D of the packet length (ptime) of the audio media, but only that the codec of the audio media is codec2.

[0150] S249:P-CSCF30E sends a request message (Npcf_PolicyAuthorization_Create request) to PCF30D requesting authorization of the session policy, which includes flow information between the terminal and the IMS AGW, and information indicating that the codec for the audio media is codec2. The message also requests that the QoS flow for the audio media be set up for the PDU session specified by the IP address of terminal 20, which is the originating terminal. The message is written as, for example, Npcf_PolicyAuthorization_Create request(AppSessionContext(ascReqData(medComponents(1, MediaComponent(medSubComps(1, MediaSubComponent(fDescs=Flow information between UE and IMS AGW)), codecs=codec2))))).

[0151] S250: PCF30D sends a response message (Npcf_PolicyAuthorization_Create response) to P-CSCF30E for the request message received in S249.

[0152] S251: Based on the information received in S249 indicating that the codec of the audio media is codec2, the PCF30D implicitly determines that it is an audio communication via a geostationary satellite and sets the QoS. For example, the PCF30D determines the value of 5QI to a value corresponding to the quality of audio communication using a geostationary satellite (5QI=11).

[0153] S252:PCF30D recognizes that the flow information should be set to the default (i.e., to suit any flow) based on the RAT type (ratType=NB_IOT_GEO) included in the request message received in S249, which indicates NB IoT radio access via a geostationary satellite.

[0154] S253:PCF30D recognizes that the QoS flow for voice media is already established and does not send a request to SMF.

[0155] (Detailed explanation of Method 3) The following describes the details of the procedure based on Method 3 using a sequence diagram. Requests, responses, and notifications sent and received in the following procedure may be referred to as messages (e.g., request messages).

[0156] (NG setup) The procedure for NG setup will now be described. Figure 14 shows an example of the eighth sequence diagram in an embodiment of the present invention. For the procedure for NG setup in existing specifications, please refer to Section 8.7.1 of Non-Patent Document 4. The processing of each step will be described below.

[0157] S301: Base station 10 recognizes that its device is configured to provide NB IoT wireless access via geostationary satellites.

[0158] S302: Base station 10 sends an NG Setup request to AMF30B requesting the establishment of an interface between base station 10 and AMF30B, which includes information (RAT Information=nb-IoT-GEO) indicating the configuration for providing NB IoT radio access via geostationary satellites. This message is written, for example, as NG Setup request (RAT Information=nb-IoT-GEO).

[0159] S303: The AMF30B sends an NG Setup response to base station 10.

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

[0161] S311: Terminal 20 recognizes that it is within range of base station 10, which provides NB IoT wireless access via geostationary satellite, and sets in its SDP offer that codec2 be used as the codec for the voice media and that the packet length (ptime) of the voice media be 80ms. In addition, if codec2 is set as the codec for the voice media in the message, it may implicitly mean that it is voice communication via geostationary satellite.

[0162] S312: Terminal 20 sends a message to P-CSCF30E requesting an IMS voice call (SIP INVITE). This message includes information (=PANI(access-type=3GPP-NB IoT-SAT)) indicating that base station 10, which provides NB IoT radio access via geostationary satellites, is accommodating terminal 20, and a negotiation proposal (SDP offer) which sets the codec2 to be used and the packet length (ptime) of the voice media to 80ms. For example, it is written as SIP INVITE SIP INVITE (PANI(access-type=3GPP-NB IoT-SAT), SDP offer(codec2, ptime:80)).

[0163] S313: P-CSCF30E sends a message to S-CSCF30F requesting an IMS voice call (SIP INVITE) that was received in S312.

[0164] S314: S-CSCF30F sends a message to I-CSCF30G requesting an IMS voice call received in S313 (SIP INVITE).

[0165] On the receiving end, processing related to IMS voice call initiation is performed based on existing specifications.

[0166] S315: The receiving I-CSCF30G sends a message (183 Session Progress) to the sending S-CSCF30F indicating that voice communication is being set up. This message includes a negotiated response (SDP answer) that sets the codec to use codec2 and the voice media packet length (ptime) to 80ms, and is written as, for example, SIP 183 Session Progress (SDP answer(codec2, ptime:80)).

[0167] S316: S-CSCF30F sends a message (183 Session Progress) to P-CSCF30E indicating that voice communication is being configured, which was received in S315.

[0168] S317: P-CSCF30E sends a message (183 Session Progress) to terminal 20 indicating that voice communication setup is in progress, which was received in S316.

[0169] S318: P-CSCF30E recognizes from the information in the message received in S312 (PANI=3GPP-NB IoT-SAT) (or 3GPP-NB IoT-GEO) that a new IMS PDU session needs to be established / configured.

[0170] The following process will be executed: either Alt.1 or Alt.2.

[0171] (Alt.1) S319:P-CSCF30E sends a device trigger to NEF30E requesting the establishment of a PDU session including a QoS flow for voice media. This message is written, for example, as Nnef_Trigger_Delivery request (DeviceTriggering (triggerPayload (Message requesting the establishment of an IMS PDU session))).

[0172] Subsequently, the existing device triggering procedure (see section 4.13.2.2 of Non-Patent Document 5) is executed.

[0173] (Alt.2) S320: After receiving a message (183 Session Progress) in S316 indicating that voice communication is being configured, the P-CSCF30E assumes that the IMS PDU session will be established autonomously by terminal 20, and therefore does not send a device trigger to initiate the establishment of the IMS PDU session.

[0174] S321: Terminal 20 recognizes that it is necessary to establish a new voice communication IMS PDU session because it is under the control of base station 10, which provides NB IoT wireless access via geostationary satellite.

[0175] (Establishing a PDU session for IMS (receiving side)) The procedure for establishing an IMS PDU session (receiving side) is described below. Figure 16 shows an example of the 10th sequence diagram in an embodiment of the present invention. The processing of each step is described below.

[0176] S331: The receiving I-CSCF30G sends a message (SIP INVITE) to the receiving S-CSCF30F requesting the initiating IMS voice call sent from the originating terminal. This message is written as, for example, SIP INVITE (SDP offer(codec2, ptime:80)).

[0177] S332: S-CSCF30F sends a message to P-CSCF30H requesting an IMS voice call (SIP INVITE) that was received in S331.

[0178] S333:P-CSCF30H sends a message to terminal 20 requesting an IMS voice call (SIP INVITE) that was received in S332.

[0179] S334: Terminal 20 recognizes that it is necessary to establish a new voice communication IMS PDU session because it is under the control of base station 10, which provides NB IoT wireless access via geostationary satellite.

[0180] S335: Terminal 20 sends a message (183 Session Progress) to P-CSCF30E indicating that voice communication is being configured. This message includes a negotiated response (SDP answer) that sets the codec to use codec2 and the packet length (ptime) of the voice media to 80ms, and is written as, for example, SIP 183 Session Progress (SDP answer(codec2, ptime:80)).

[0181] S336:P-CSCF30E assumes that terminal 20 autonomously establishes an IMS PDU session before sending a message (183 Session Progress) indicating that voice communication is being set up, and therefore does not send a device trigger to initiate the establishment of the IMS PDU session.

[0182] The above embodiment makes it possible to define procedures for voice communication in a radio communication system using geostationary satellites, taking into account the provision that only default QoS (Quality of Service) rules are available.

[0183] (Device configuration) Next, we will describe 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. The base station 10, network node 30, and terminal 20 include the functions to perform 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.

[0184] <Base station 10 and network node 30> Figure 17 shows an example of the functional configuration of a base station 10 and a network node 30. As shown in Figure 17, 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 17 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 the same functional configuration as the base station 10. Furthermore, a network node 30 having multiple different functions on the system architecture may be composed of multiple network nodes 30 separated by function.

[0185] 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.

[0186] The setting unit 130 stores pre-configured setting information and various setting information to be transmitted to the terminal 20 in a storage device, and reads it from the storage device as needed.

[0187] The control unit 140 performs the processes described in the embodiment. The control unit 140 also performs processing related to communication with the terminal 20. The signal transmission function of the control unit 140 may be included in the transmission unit 110, and the signal reception function of the control unit 140 may be included in the reception unit 120.

[0188] <Terminal 20> Figure 18 shows an example of the functional configuration of terminal 20. As shown in Figure 18, 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 18 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. Furthermore, the communication device that becomes the resource holder 20 may have a functional configuration similar to that of terminal 20.

[0189] 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 obtains signals from higher layers from the received physical layer signals. The receiving unit 220 also has the function of receiving control signals or reference signals transmitted from the network node 30. A communication unit including the transmitting unit 210 and the receiving unit 220 may be configured.

[0190] The setting unit 230 stores various setting information received from the network node 30 by the receiving unit 220 in its storage device and reads it from the storage device as needed. The setting unit 230 also stores pre-configured setting information.

[0191] The control unit 240 performs the processing described in the embodiment. The signal transmission function in the control unit 240 may be included in the transmission unit 210, and the signal reception function in the control unit 240 may be included in the reception unit 220.

[0192] (Hardware configuration) The block diagrams (Figures 17 and 18) used in the description of the above embodiments show functional units. These functional blocks (components) are realized by any combination of at least one of hardware and software. 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 or wireless connections). A functional block may be realized by combining the one or more devices with software.

[0193] Functions include, but are not limited to, judgment, decision, judgment, calculation, calculation, processing, derivation, investigation, exploration, confirmation, reception, transmission, output, access, resolution, selection, selection, establishment, comparison, assumption, expectation, assumption, broadcasting, notifying, communicating, forwarding, configuring, reconfiguring, allocating (mapping), and assigning. For example, a functional block (configuration part) that enables transmission is called a transmitting unit or transmitter. As mentioned above, the method of implementation is not particularly limited.

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

[0195] In the following explanation, the term "device" can be replaced with "circuit," "device," "unit," etc. The hardware configuration of the base station 10 and terminal 20 may include one or more of the devices shown in the figure, or it may be configured without some of the devices.

[0196] 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 storage device 1002, which allows the processor 1001 to perform calculations, control communication by the communication device 1004, and control at least one of the reading and writing of data in the storage device 1002 and auxiliary storage device 1003.

[0197] The processor 1001 controls the entire computer, for example, by running an operating system. The processor 1001 may consist of a central processing unit (CPU) that includes interfaces with peripheral devices, control devices, arithmetic units, registers, etc. For example, the control unit 140, control unit 240, etc., described above may be implemented by the processor 1001.

[0198] Furthermore, the processor 1001 reads programs (program code), software modules, or data from at least one of the auxiliary storage device 1003 and the communication device 1004 into the storage device 1002, and executes various processes accordingly. The program used is one that causes a computer to execute at least a part of the operations described in the above embodiment. For example, the control unit 140 of the base station 10 shown in Figure 17 may be implemented by a control program stored in the storage device 1002 and operated by the processor 1001. Also, for example, the control unit 240 of the terminal 20 shown in Figure 18 may be implemented by a control program stored in the storage device 1002 and operated by the processor 1001. Although the above-described processes have been explained as being executed by one processor 1001, 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.

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

[0200] The auxiliary storage device 1003 is a computer-readable recording medium and may consist of at least one of the following: 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, etc. The above-mentioned storage medium may also be a database, server, or other suitable medium that includes at least one of the storage device 1002 and the auxiliary storage device 1003.

[0201] The communication device 1004 is hardware (transceiver / receiver device) for communicating between computers via at least one of a wired network and a wireless network, and is also referred to as a network device, network controller, network card, communication module, etc. The communication device 1004 may include high-frequency switches, duplexers, filters, frequency synthesizers, etc., to implement at least one of frequency division duplex (FDD) and time division duplex (TDD). For example, the transmit / receive antenna, amplifier section, transmit / receive section, transmission path interface, etc., may be implemented by the communication device 1004. The transmit / receive section may be implemented with physically or logically separated transmitting and receiving sections.

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

[0203] Furthermore, each device, such as the processor 1001 and the storage device 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.

[0204] Furthermore, the base station 10 and terminal 20 may be configured to include hardware such as a microprocessor, a digital signal processor (DSP), an ASIC (Application Specific Integrated Circuit), a PLD (Programmable Logic Device), and an FPGA (Field Programmable Gate Array), 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.

[0205] Figure 20 shows an example of the configuration of vehicle 2001. As shown in Figure 20, vehicle 2001 includes a drive unit 2002, a steering unit 2003, an accelerator pedal 2004, a brake pedal 2005, a shift lever 2006, front wheels 2007, rear wheels 2008, an axle 2009, an electronic control unit 2010, various sensors 2021-2029, an information service unit 2012, and a communication module 2013. Each aspect / embodiment described in this disclosure may be applied to a communication device mounted on vehicle 2001, for example, to the communication module 2013.

[0206] The drive unit 2002 consists of, for example, an engine, a motor, or a hybrid of an engine and a motor. The steering unit 2003 includes at least a steering wheel (also called a handle) and is configured to steer at least one of the front wheels and the rear wheels based on the operation of the steering wheel, which is operated by the user.

[0207] The electronic control unit 2010 consists of a microprocessor 2031, memory (ROM, RAM) 2032, and communication ports (IO ports) 2033. Signals from various sensors 2021 to 2029 installed in the vehicle 2001 are input to the electronic control unit 2010. The electronic control unit 2010 may also be called an ECU (Electronic Control Unit).

[0208] Signals from various sensors 2021-2029 include current signals from current sensor 2021 which senses motor current, front and rear wheel rotation speed signals obtained by rotation speed sensor 2022, front and rear wheel air pressure signals obtained by air pressure sensor 2023, vehicle speed signals obtained by vehicle speed sensor 2024, acceleration signals obtained by acceleration sensor 2025, accelerator pedal depression signals obtained by accelerator pedal sensor 2029, brake pedal depression signals obtained by brake pedal sensor 2026, shift lever operation signals obtained by shift lever sensor 2027, and detection signals obtained by object detection sensor 2028 for detecting obstacles, vehicles, pedestrians, etc.

[0209] The Information Services Unit 2012 consists of various devices for providing (outputting) various types of information such as driving information, traffic information, and entertainment information, including a car navigation system, audio system, speakers, television, and radio, and one or more ECUs that control these devices. The Information Services Unit 2012 uses information acquired from external devices via a communication module 2013, etc., to provide various multimedia information and multimedia services to the occupants of the vehicle 2001. The Information Services Unit 2012 may include input devices that accept input from the outside (e.g., keyboard, mouse, microphone, switch, button, sensor, touch panel, etc.) and output devices that perform output to the outside (e.g., display, speaker, LED lamp, touch panel, etc.).

[0210] The driver assistance system unit 2030 consists of various devices that provide functions to prevent accidents or reduce the driver's workload, such as millimeter-wave radar, LiDAR (Light Detection and Ranging), cameras, positioning locators (e.g., GNSS), map information (e.g., high-definition (HD) maps, autonomous vehicle (AV) maps, etc.), gyro systems (e.g., IMU (Inertial Measurement Unit), INS (Inertial Navigation System), etc.), AI (Artificial Intelligence) chips, and AI processors, as well as one or more ECUs that control these devices. The driver assistance system unit 2030 also sends and receives various information via the communication module 2013 to realize driver assistance functions or autonomous driving functions.

[0211] The communication module 2013 can communicate with the microprocessor 2031 and components of the vehicle 2001 via its communication port. For example, the communication module 2013 sends and receives data via its communication port 2033 to the drive unit 2002, steering unit 2003, accelerator pedal 2004, brake pedal 2005, shift lever 2006, front wheels 2007, rear wheels 2008, axle 2009, the microprocessor 2031 and memory (ROM, RAM) 2032 in the electronic control unit 2010, and sensors 2021-29 provided in the vehicle 2001.

[0212] The communication module 2013 is a communication device that can be controlled by the microprocessor 2031 of the electronic control unit 2010 and can communicate with external devices. For example, it can send and receive various types of information to and from external devices via wireless communication. The communication module 2013 may be located either inside or outside the electronic control unit 2010. The external device may be, for example, a base station or a mobile station.

[0213] The communication module 2013 may transmit at least one of the following to an external device via wireless communication: signals from the various sensors 2021-2028 input to the electronic control unit 2010, information obtained based on said signals, and information based on input from an external source (user) obtained via the information service unit 2012. The electronic control unit 2010, the various sensors 2021-2028, the information service unit 2012, etc., may also be called input units that accept input. For example, the PUSCH transmitted by the communication module 2013 may include information based on the above input.

[0214] The communication module 2013 receives various information (traffic information, signal information, inter-vehicle information, etc.) transmitted from an external device and displays it on the information service unit 2012 provided in the vehicle 2001. The information service unit 2012 may also be called an output unit, which outputs information (for example, outputs information to devices such as displays and speakers based on the PDSCH (or data / information decoded from the PDSCH) received by the communication module 2013). The communication module 2013 also stores the various information received from the external device in memory 2032, which is available to the microprocessor 2031. Based on the information stored in memory 2032, the microprocessor 2031 may control the drive unit 2002, steering unit 2003, accelerator pedal 2004, brake pedal 2005, shift lever 2006, front wheels 2007, rear wheels 2008, axles 2009, sensors 2021-2029, etc., provided in the vehicle 2001.

[0215] <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 terminal includes a control unit that stores the context of a PDU (Packet Data Unit) session established via a base station that provides NB (Narrow Band) IoT (Internet of Things) wireless access via a geostationary satellite, and (S116) A receiving unit receives a message from the first network node (P-CSCF30E) requesting the configuration of a Quality of Service (QoS) flow for voice media communication within the PDU session, specifying a particular originating / destining IP (Internet Protocol) address, (S139) A transmission unit sends a message to the second network node (SMF30C) requesting the configuration of a QoS flow for voice media communication within the PDU session, which is specified to match any origin / destination address, (S143) A network node (PCF30D) that has [this feature]. (Additional note 2) A control unit that recognizes the settings for providing NB (Narrow Band) IoT (Internet of Things) wireless access via geostationary satellites, and (S101) A transmission unit that sends a message to the first network node (AMF) requesting the establishment of an interface, which includes information related to the above configuration (RAT Information=nb-IoT-GEO), (S102) A base station having (Additional note 3) The receiving unit receives a message from the first network node (SMF30C) requesting a policy determination for a PDU (Packet Data Unit) session for IMS (IP Multimedia Subsystem), which was requested by the terminal via a base station providing NB (Narrow Band) IoT (Internet of Things) wireless access via geostationary satellite, (S216) A transmission unit that transmits a policy to the first network node (SMF30C) stating that QoS (Quality of Service) for voice media communication should be set, and (S218) A network node (PCF30D) that has [this feature]. (Additional note 4) A receiving unit receives a message (SIP INVITE) from a terminal requesting the commencement of voice communication, which includes information (PANI(access-type=3GPP-NB IoT-SAT)) indicating that a base station providing NB (Narrow Band) IoT (Internet of Things) wireless access via geostationary satellites is accommodating the terminal, and (S312) The control unit recognizes that a PDU (Packet Data Unit) session for IMS (IP Multimedia Subsystem) needs to be configured, and (S318) A transmission unit that sends a message to the first network node (NEF30H) requesting the configuration of a PDU session for IMS addressed to the terminal, (S319) A network node (P-CSCF30E) that has [this feature]. (Additional note 5) A control unit that recognizes that it is located in the vicinity of a base station providing NB (Narrow Band) IoT (Internet of Things) wireless access via a geostationary satellite, and (S311) A transmission unit sends a message (SIP INVITE) to the first network node (P-CSCF30E) requesting the start of voice communication, which includes information indicating the recognition (PANI(access-type=3GPP-NB IoT-SAT)), and (S312) A terminal. (Additional note 6) A control unit that recognizes that it is located in the vicinity of a base station providing NB (Narrow Band) IoT (Internet of Things) wireless access via a geostationary satellite, and (S311) A receiving unit that receives a message requesting the start of voice communication (SIP INVITE) (S333) or a message indicating that voice communication is being processed (SIP 183 Session Progress) (S317) from the first network node (P-CSCF30E) via the base station, It has, The control unit recognizes that it is necessary to establish a PDU (Packet Data Unit) session for transmitting and receiving audio media (S334, S321) The system further includes a transmission unit that transmits a message to the first network node via the base station requesting the establishment of the PDU session (similar processing to S111 and S211). Terminal.

[0216] Any of the appendices 1 to 6 can be used to specify procedures for voice communications that take into account the provision that only default QoS (Quality of Service) rules are available in a radio communication system using geostationary satellites.

[0217] (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.

[0218] Furthermore, the notification of information is not limited to the embodiments / models described herein and may be carried out by other methods. For example, the notification of information 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 combinations thereof. Also, RRC signaling may be called RRC messages, and may be, for example, RRC Connection Setup messages, RRC Connection Reconfiguration messages, etc.

[0219] Each aspect / embodiment described in this disclosure includes LTE (Long Term Evolution), LTE-A (LTE-Advanced), SUPER 3G, IMT-Advanced, 4G (4th generation mobile communication system), 5G (5th generation mobile communication system), 6th generation mobile communication system (6G), xth generation mobile communication system (xG) (xG (where x is, for example, an integer or decimal)), FRA (Future Radio Access), NR (new Radio), New radio access (NX), Future generation radio access (FX), W-CDMA (registered trademark), GSM (registered trademark), CDMA2000, UMB (Ultra Mobile Broadband), IEEE 802.11 (Wi-Fi (registered trademark)), IEEE 802.16 (WiMAX (registered trademark)), and IEEE This may apply to at least one system utilizing 802.20, UWB (Ultra-WideBand), Bluetooth®, or other appropriate systems, and to next-generation systems extended, modified, created, or defined based thereon. It may also apply to a combination of multiple systems (for example, a combination of at least one of LTE and LTE-A with 5G).

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

[0221] In this specification, specific operations performed by the base station 10 may, in some cases, be performed by its upper node. In a network consisting of one or more network nodes having a base station 10, it is clear that various operations performed for communication with the terminal 20 can be performed by the base station 10 and at least one of the other network nodes (for example, an MME or S-GW, but not limited to these). Although the above example illustrates the case where there is one other network node besides the base station 10, the other network node may be a combination of multiple other network nodes (for example, an MME and an S-GW).

[0222] The information or signals described in this disclosure may be output from a higher layer (or lower layer) to a lower layer (or higher layer). They may also be input and output via multiple network nodes.

[0223] Input and output information may be stored in a specific location (e.g., memory) or managed using a management table. Input and output information may be overwritten, updated, or appended to. Output information may be deleted. Input information may be transmitted to other devices.

[0224] The determination in this disclosure may be made by a value represented by one bit (0 or 1), by a boolean value (true or false), or by a numerical comparison (for example, a comparison with a predetermined value).

[0225] Software should be broadly interpreted to mean instructions, instruction sets, code, code segments, program code, programs, subprograms, software modules, applications, software applications, software packages, routines, subroutines, objects, executable files, execution threads, procedures, functions, and so on, whether they are called software, firmware, middleware, microcode, hardware description languages, or by any other name.

[0226] Furthermore, software, instructions, information, etc., may be transmitted and received via a transmission medium. For example, if software is transmitted from a website, server, or other remote source using at least one of wired technology (such as coaxial cable, fiber optic cable, twisted pair, or digital subscriber line (DSL)) and wireless technology (such as infrared or microwave), then at least one of these wired and wireless technologies is included in the definition of a transmission medium.

[0227] The information, signals, etc. described in this disclosure may be represented using any of the various different techniques. For example, the data, instructions, commands, information, signals, bits, symbols, chips, etc. that may be referred to throughout the above description may be represented by voltage, current, electromagnetic waves, magnetic fields or magnetic particles, optical fields or photons, or any combination thereof.

[0228] In addition, terms used in this disclosure and terms necessary for understanding this disclosure may be replaced with terms having the same or similar meanings. For example, at least one of the channel and symbol may be a signal (signaling). Also, a signal may be a message. Furthermore, a component carrier (CC) may be called a carrier frequency, cell, frequency carrier, etc.

[0229] The terms “system” and “network” as used in this disclosure are interchangeable.

[0230] Furthermore, the information, parameters, etc., described in this disclosure may be expressed using absolute values, relative values ​​from a given value, or other corresponding information. For example, wireless resources may be indicated by an index.

[0231] The names used for the parameters described above are not restrictive in any way. Furthermore, the formulas and other expressions using these parameters may differ from those expressly disclosed in this disclosure. Various channels (e.g., PUCCH, PDCCH, etc.) and information elements can be identified by any suitable name, and therefore, the various names assigned to these various channels and information elements are not restrictive in any way.

[0232] In this disclosure, terms such as "base station (BS)", "wireless base station", "base station equipment", "fixed station", "NodeB", "eNodeB (eNB)", "gNodeB (gNB)", "access point", "transmission point", "reception point", "transmission / reception point", "cell", "sector", "cell group", "carrier", and "component carrier" may be used interchangeably. Base stations may also be referred to by terms such as macrocell, small cell, femtocell, and picocell.

[0233] A base station can house one or more (e.g., three) cells. If a base station houses multiple cells, the entire coverage area of ​​the base station can be divided into several smaller areas, each of which may also be provided with communication services by a base station subsystem (e.g., a Remote Radio Head (RRH)). The terms “cell” or “sector” refer to part or all of the coverage area of ​​at least one of the base station and / or base station subsystems that provide communication services in that coverage.

[0234] In this disclosure, the transmission of information by a base station to a terminal may be interpreted as the base station instructing the terminal to perform information-based control or operation.

[0235] In this disclosure, terms such as "Mobile Station (MS)," "user terminal," "User Equipment (UE)," and "terminal" may be used interchangeably.

[0236] A mobile station may also be referred to by those skilled in the art as 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, or several other appropriate terms.

[0237] At least one of the base station and the mobile station may be called a transmitting device, a receiving device, a communication device, etc. At least one of the base station and the mobile station may also be a device mounted on a mobile body, the mobile body itself, etc. The mobile body refers to a movable object, and its speed of movement is arbitrary. This also includes the case when the mobile body is stationary. The mobile body includes, but is not limited to, 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, satellites, drones (registered trademark), multicopters, quadcopters, balloons, and items mounted on them. The mobile body may also be a mobile body that moves autonomously based on operation commands. It may be a vehicle (e.g., a car, an airplane, etc.), an unmanned mobile body (e.g., a drone, an autonomous vehicle, etc.), or a robot (manned or unmanned). Furthermore, at least one of the base station and the mobile station may include devices that do not necessarily move during communication operations. For example, at least one of the base station and the mobile station may be an IoT (Internet of Things) device such as a sensor.

[0238] Furthermore, the term "base station" in this disclosure may be interpreted as "user terminal." For example, the various aspects / embodiments of this disclosure may be applied to a configuration in which communication between a base station and a user terminal is replaced with communication between multiple terminals 20 (which may be called, for example, D2D (Device-to-Device), V2X (Vehicle-to-Everything), etc.). In this case, the terminals 20 may have the functions that the base station 10 has. Also, terms such as "uplink" and "downlink" may be interpreted as terms corresponding to terminal-to-terminal communication (for example, "side"). For example, uplink channel, downlink channel, etc., may be interpreted as side channel.

[0239] Similarly, the term "user terminal" in this disclosure may be replaced with "base station." In this case, the base station may be configured to have the same functions as the user terminal described above.

[0240] As used in this disclosure, the terms “determining” and “determining” may encompass a wide variety of actions. “Determining” may include, for example, judging, calculating, computing, processing, deriving, investigating, looking up, searching, inquiry (e.g., searching in a table, database, or other data structure), and ascertaining. “Determining” may also include, for example, receiving (e.g., receiving information), transmitting (e.g., sending information), input, output, and accessing (e.g., accessing data in memory). Furthermore, "judgment" and "decision" can include considering something as having been "judged" or "decided" after resolving, selecting, choosing, establishing, comparing, etc. In other words, "judgment" and "decision" can include considering something as having been "judged" or "decided" after some action. Also, "judgment (decision)" can be reinterpreted as "assuming," "expecting," or "considering."

[0241] The terms “connected,” “coupled,” or any variation thereof, mean any direct or indirect connection or coupling between two or more elements, and may include the presence of one or more intermediate elements between two elements that are “connected” or “coupled” with each other. The coupling or connection between elements may be physical, logical, or a combination thereof. For example, “connection” may be reinterpreted as “access.” As used in this disclosure, two elements may be considered to be “connected” or “coupled” with each other using at least one of one or more wires, cables, and printed electrical connections, and, in some non-limiting and non-exclusive examples, electromagnetic energy having wavelengths in the radio frequency domain, microwave domain, and optical (both visible and invisible) domain.

[0242] The reference signal can also be abbreviated as RS (Reference Signal), and may be called a pilot depending on the applicable standard.

[0243] In this disclosure, the phrase "based on" does not mean "based solely on" unless otherwise specified. In other words, the phrase "based on" means both "based solely on" and "based at least on."

[0244] Any reference to elements using designations such as “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.

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

[0246] Where the terms “include,” “including,” and variations thereof are used in this disclosure, these terms are intended to be inclusive, as is the term “comprising.” Furthermore, the term “or” as used in this disclosure is not intended to mean exclusive OR.

[0247] 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.

[0248] In this disclosure, the term "A and B are different" may mean "A and B are different from each other." The term may also mean "A and B are each different from C." Terms such as "separate" and "combine" may be interpreted similarly to "different."

[0249] Each aspect / embodiment described herein may be used individually, in combination, or switched between as needed during implementation. Furthermore, notification of specific information (e.g., notification that "X is") is not limited to explicit notification, but may also be implicit (e.g., by not providing such notification).

[0250] Although the present disclosure has been described in detail above, it will be clear to those skilled in the art that the present disclosure is not limited to the embodiments described herein. The present disclosure can be implemented in modified and altered forms without departing from the intent and scope of the present disclosure as defined by the claims. Therefore, the descriptions in the present disclosure are illustrative and not intended to be restrictive in any way. [Explanation of symbols]

[0251] 10 base station 110 Transmitter 120 Receiver 130 Setting section 140 Control unit 20 Terminal 210 Transmission unit 220 Reception unit 230 Setting unit 240 Control unit 30 Network node 1001 Processor 1002 Storage device 1003 Auxiliary storage device 1004 Communication device 1005 Input device 1006 Output device 2001 Vehicle 2002 Drive unit 2003 Steering unit 2004 Accelerator pedal 2005 Brake pedal 2006 Shift lever 2007 Front wheel 2008 Rear wheel 2009 Axle 2010 Electronic control unit 2012 Information service unit 2013 Communication module 2021 Current sensor 2022 Rotational speed sensor 2023 Air pressure sensor 2024 Vehicle speed sensor 2025 Acceleration sensor 2026 Brake pedal sensor 2027 Shift lever sensor 2028 Object detection sensor 2029 Accelerator pedal sensor 2030 Driving support system unit 2031 Microprocessor 2032 Memory (ROM, RAM) 2033 Communication port (IO port)

Claims

1. A control unit that stores the context of a PDU (Packet Data Unit) session established via a base station that provides NB (Narrow Band) IoT (Internet of Things) wireless access via a geostationary satellite, A receiving unit receives a message from the first network node requesting the configuration of a Quality of Service (QoS) flow for voice media communication within the PDU session, specifying a particular originating / destining IP (Internet Protocol) address. A transmission unit that sends a message to the second network node requesting the configuration of a QoS flow for voice media communication within the PDU session, which is specified to match any origin / destination address, A network node that has

2. A control unit that recognizes the settings for providing NB (Narrow Band) IoT (Internet of Things) wireless access via geostationary satellites, A transmitting unit that sends a message to the first network node requesting the establishment of an interface, which includes information relating to the above configuration, A base station having

3. A receiving unit receives a message from the first network node requesting a policy determination for a Packet Data Unit (PDU) session for IMS (IP Multimedia Subsystem), which was requested by the terminal via a base station providing NB (Narrow Band) IoT (Internet of Things) wireless access via a geostationary satellite. A transmitting unit that transmits a policy to the first network node stating that QoS (Quality of Service) for voice media communication should be set, A network node that has

4. A receiving unit receives a message from a terminal requesting the commencement of voice communication, which includes information indicating that a base station providing NB (Narrow Band) IoT (Internet of Things) wireless access via a geostationary satellite is accommodating the terminal. A control unit recognizes that a PDU (Packet Data Unit) session for IMS (IP Multimedia Subsystem) needs to be configured, A transmission unit that sends a message to the first network node requesting the configuration of a PDU session for IMS addressed to the terminal, A network node that has

5. A control unit that recognizes that it is located at a base station providing NB (Narrow Band) IoT (Internet of Things) wireless access via a geostationary satellite, A transmitting unit that transmits a message to the first network node requesting the start of voice communication, which includes information indicating the recognition, A terminal.

6. A control unit that recognizes that it is located at a base station providing NB (Narrow Band) IoT (Internet of Things) wireless access via a geostationary satellite, A receiving unit that receives a message from the first network node via the base station requesting the start of voice communication, or a message indicating that voice communication is being processed, It has, The control unit recognizes that it is necessary to establish a PDU (Packet Data Unit) session for transmitting and receiving audio media, The system further includes a transmitting unit that transmits a message to the first network node via the base station requesting the establishment of the PDU session. Terminal.

Images