Network nodes and terminals

Abstract

To define the procedures for initiating priority calls in a radio communication system using geostationary satellites. [Solution] The network node includes a receiving unit that receives a message from a first network node requesting the commencement of voice communication regarding a priority call, and a transmitting unit that sends a message to a second network node requesting that the priority of a configured control plane route for sending and receiving general priority IMS messages be changed to a higher priority.

Description

[Technical Field]

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

[0002] In 3GPP (registered trademark) (3rd Generation Partnership Project), in order to achieve further increase in system capacity, further increase in data transmission rate, further reduction in latency in radio sections, and the like, studies are underway on a radio communication scheme called 5G or NR (New Radio) (hereinafter, this radio communication scheme is referred to as "5G" or "NR"). In 5G, various radio technologies are being studied to satisfy the requirement of reducing the latency in the radio section to 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 the LTE (Long Term Evolution) network architecture, and NG-RAN (Next Generation - Radio Access Network) corresponding to E-UTRAN (Evolved Universal Terrestrial Radio Access Network), which is the RAN (Radio Access Network) in the LTE network architecture, is under study (for example, Non-Patent Document 1).

[0004] Furthermore, as an IMS (IP Multimedia Subsystem) architecture that supports the data channel capability of terminals, specifications for an IMS data channel network are under study (for example, Non-Patent Document 2).

[0005] Furthermore, 3GPP Rel-20 is scheduled to discuss voice communications via geostationary Earth orbit (GEO). [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 TS 38.331 V18.4.0(2024-12) [Non-Patent Document 4] 3GPP TS 38.413 V18.0.0(2023-12) [Non-Patent Document 5] 3GPP TS 23.502 V19.2.0(2024-12) [Non-Patent Document 6] 3GPP TS 29.512 V19.1.0(2024-12) [Non-Patent Document 7] 3GPP TS 29.514 V19.1.0(2024-12) [Non-Patent Document 8] 3GPP TS 29.122 V19.1.0(2024-12) [Non-Patent Document 9] 3GPP TS 29.542 V19.0.0(2024-09) [Non-Patent Document 10] 3GPP TS 23.167 V19.0.0(2024-12) [Overview of the project] [Problems that the invention aims to solve]

[0007] In voice communications via geostationary Earth orbit (GEO), effectively utilizing radio resources is a challenge. Currently, measures such as efficiently transmitting SIP (Session Initiation Protocol) signals using control plane signals, reducing the number of signals in the SIP procedure, compressing SIP signals (SigComp), and using header compression technology are being discussed. However, procedures related to priority calls in voice communications via geostationary satellite (GEO) have not been considered.

[0008] This invention has been made in view of the above points, and aims to define a procedure for initiating priority calls in a radio communication system using geostationary satellites. [Means for solving the problem]

[0009] According to the disclosed technology, a network node is provided having a receiving unit that receives a message from a first network node requesting the initiation of voice communication relating to a priority call, and a transmitting unit that sends a message to a second network node requesting that the priority of a configured control plane route for sending and receiving general priority IMS messages be increased. [Effects of the Invention]

[0010] The disclosed technology can specify procedures for initiating priority calls in a radio communication system using geostationary satellites. [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]It is a diagram illustrating an example (2) of NTN. [Figure 6] It is a diagram illustrating an example (3) of NTN. [Figure 7] It is a diagram illustrating an example of a first sequence diagram in an embodiment of the present invention. [Figure 8] It is a diagram illustrating an example of a second sequence diagram in an embodiment of the present invention. [Figure 9] It is a diagram illustrating an example of a third sequence diagram in an embodiment of the present invention. [Figure 10] It is a diagram illustrating an example of a fourth sequence diagram in an embodiment of the present invention. [Figure 11] It is a diagram illustrating an example of a fifth sequence diagram in an embodiment of the present invention. [Figure 12] It is a diagram illustrating an example of a sixth sequence diagram in an embodiment of the present invention. [Figure 13] It is a diagram illustrating an example of a seventh sequence diagram in an embodiment of the present invention. [Figure 14] It is a diagram illustrating an example of an eighth sequence diagram in an embodiment of the present invention. [Figure 15] It is a diagram illustrating an example of a ninth sequence diagram in an embodiment of the present invention. [Figure 16] It is a diagram illustrating an example of a tenth sequence diagram in an embodiment of the present invention. [Figure 17] It is a diagram illustrating an example of an eleventh sequence diagram in an embodiment of the present invention. [Figure 18] It is a diagram illustrating an example of a twelfth sequence diagram in an embodiment of the present invention. [Figure 19] It is a diagram illustrating an example of a functional configuration of a base station 10 and a network node 30 in an embodiment of the present invention. [Figure 20] It is a diagram illustrating an example of a functional configuration of a terminal 20 in an embodiment of the present invention. [Figure 21] It is a diagram illustrating an example of a hardware configuration of the base station 10, the terminal 20, and the network node 30 in an embodiment of the present invention. [Figure 22] This figure shows an example of the configuration of a vehicle 2001 in an embodiment of the present invention. [Modes for carrying out the invention]

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

[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 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) This document outlines the procedures for initiating priority calls in a radio communication system using geostationary satellites. The requests, responses, and notifications transmitted and received in the following procedures may be referred to as messages (e.g., request messages).

[0043] In this procedure, a preferred NIDD PDU session is introduced. In a call initiated by a preferred user and received by a general user, the receiving general NIDD PDU session is changed to a preferred NIDD PDU session, and then SIP message exchange is performed.

[0044] (Procedure for priority users to communicate with general users) The procedure for a priority user to make a call to a general user will be explained using a sequence diagram. Figure 7 shows an example of a first sequence diagram in an embodiment of the present invention. The processing of each step will be explained below.

[0045] S100: Terminal 20 decides to initiate an IMS voice call.

[0046] S101: Terminal 20 receives broadcast information (System Information Block (SIB)) from base station 10, which includes information (ims-NasCombinedSupport) indicating that NAS / IMS integrated processing is permitted.

[0047] S102: Terminal 20 decides to transition to Connection mode, establish a 5GS-priority NIDD PDU session, establish a 5GS-priority IMS PDU session, and initiate an IMS voice call. Terminal 20 also recognizes that it is within range of a base station providing Narrow Band (NB) IoT (Internet of Things) wireless access via geostationary satellites.

[0048] S103: Terminal 20 sends a request message (RRCSetup request) to base station 10 requesting RRC configuration. This request message includes information indicating that the connection establishment cause is a priority call, and is written as, for example, RRCSetupRequest(EstablishmentCause(highPriorityAccess)).

[0049] S104: The base station 10 sends a response message (RRCSetup) to the terminal 20 for the request message received in S103.

[0050] S105: Terminal 20 is expected to make calls to IMS using SIP signals only after NAS encryption is complete.

[0051] S106: Terminal 20 sends a message (RRCSetupComplete) to base station 10 notifying it that the RRC setup is complete. This message is written as, for example, RRCSetupComplete (dedicatedNAS-Message(Service request)).

[0052] S107: Base station 10 sends an Initial UE message to AMF30A containing information indicating a service request. This message includes information indicating that the connection establishment cause is a priority call, and is written as, for example, Initial UE message(RRC Establishment Cause(highPriorityAccess), NAS-PDU(Service request)).

[0053] S108: The AMF30A sends an Initial Context Setup request to base station 10.

[0054] S109: Base station 10 sends a SecurityModeCommand to terminal 20.

[0055] S110: Terminal 20 sends SecurityModeComplete to base station 10.

[0056] S111: Base station 10 sends an Initial Context Setup response to AMF30A.

[0057] S112:AMF30A sends a Downlink NAS Transport to base station 10. This message is written as, for example, Downlink NAS Transport (NAS-PDU (Security Mode Command)).

[0058] S113: Base station 10 sends DLInformationTransfer to terminal 20. This message is written as, for example, DLInformationTransfer(dedicatedNAS-Message(Security Mode Command)).

[0059] The process following S113 will now be described. Figure 8 shows an example of a second sequence diagram in an embodiment of the present invention. In the following steps, an IMS call is performed using the encrypted NAS message. The process of each step will be described below.

[0060] S121: Terminal 20 sends a message (ULInformationTransfer) to base station 10 that forwards a NAS message containing a Service request, a Control Plane Service request, information indicating that it is a priority call (highPriority ims), and a SIP INVITE (Resource-Priority) request. This message may also include information about P-CSCF30J as the connection destination information (nefTargetAf) for NEF30H in NIDD, and is written as, for example, ULInformationTransfer(dedicatedNAS-Message(Security Mode Complete(NAS message container(Service request), NAS message container2(Control Plane Service request(Payload container type(CIoT user data container), Payload container type additional information(highPriority ims), Payload container(user data container(SIP INVITE(Resource-Priority))), nefTargetAf(P-CSCF)))))).

[0061] Specifically, terminal 20 generates a NAS message that includes an IMS message regarding the priority call. In this NAS message, terminal 20 includes the IMS message regarding the priority call in a payload container that is transparent to AMF30A, and includes information that the payload container contains content related to the priority call, which is information that AMF30A can verify.

[0062] S122: Base station 10 sends an Uplink NAS Transport message to AMF30A that includes a Service request, a Control Plane Service request, Payload container type additional information (highPriority ims) indicating that it is a priority call, and a SIP INVITE (Resource-Priority) request for priority calling. The message may include information about P-CSCF30J as the connection destination information (nefTargetAf) for NEF30H in NIDD, for example, it may be written as Uplink NAS Transport(NAS-PDU(Security Mode Complete(NAS message container(Service request), NAS message container2(Control Plane Service request(Payload container type(CIoT user data container), Payload container type additional information(highPriority ims), Payload container(user data container(SIP INVITE(Resource-Priority))), nefTargetAf(P-CSCF)))))).

[0063] S123: Based on the Control Plane Service request, AMF30A decides to start from its own device instead of the terminal, and to execute the NIDD procedure.

[0064] S124:AMF30A decides to establish a NIDD PDU session for the priority call based on information indicating that it is a priority call (Payload container type additional information (highPriority ims)).

[0065] In the following steps S125 to S135, the establishment of a 5GS-priority NIDD PDU session will be performed.

[0066] S125: AMF30A sends a request message (Nsmf_PDUSession_CreateSMContext request) to SMF30E requesting the creation of an SM (Session Management) context for the NIDD PDU session. That is, AMF30A sends a request message to SMF30E to set up a high-priority control plane route for sending and receiving IMS messages related to priority calls between itself and P-CSCF30J, which has proxy functionality, via SMF30E. This message includes information indicating that it is a priority call (CiotUserDataRequestType (highPriority ims)) and information about P-CSCF30J as the connection destination of NEF30H in NIDD (nefTargetAf), and is written as, for example, Nsmf_PDUSession_CreateSMContext request (SmContextCreateData (CiotUserDataRequestType (highPriority ims), nefTargetAf(P-CSCF))).

[0067] S126: SMF30E sends a response message (Nsmf_PDUSession_CreateSMContext response) to AMF30A for the request message received in S125. SMF30E then selects P-CSCF30J, derives the IP address of P-CSCF30J, and sets the IP address of P-CSCF30J.

[0068] S127: SMF30E sends a request message (Nnef_SMContext_Create request) to NEF30H requesting the creation of an SM context. That is, SMF30E sends a request message to NEF30H to set up a high-priority control plane route for sending and receiving IMS messages related to a priority call between itself and the P-CSCF30J, which has proxy functionality, via NEF30H. This message includes information indicating that it is a priority call (CiotUserDataRequestType (highPriority ims)) and the IP address of the P-CSCF30J, and is written as, for example, Nnef_SMContext_Create request (SmContextCreateData (CiotUserDataRequestType(highPriority ims), nefTargetAfIpAddress(P-CSCF IP address))).

[0069] S128: NEF30H sends a response message (Nnef_SMContext_Create response) to SMF30E for the request message received in S127.

[0070] S129: SMF30E sends a request message (Namf_Communication_N1N2MessageTransfer request) to AMF30A indicating that it has granted permission for the SM context generation request received in S127.

[0071] S130: AMF30A sends a response message (Namf_Communication_N1N2MessageTransfer response) to SMF30E for the request message received in S129.

[0072] S131:NEF30H decides to establish a connection with P-CSCF30J using the IP address of P-CSCF30J included in the request message received in S127.

[0073] S132:NEF30H sends a request message (Nnef_NIDDConfiguration_TriggerNotify request) to P-CSCF30J requesting that it activate the configuration of a high-priority route on the control plane for sending and receiving IMS messages related to priority calls. The request message includes information indicating high priority and is written as, for example, Nnef_NIDDConfiguration_TriggerNotify request(NiddConfigurationTrigger(Priority(highPriority))).

[0074] S133: P-CSCF30J sends a response message (Nnef_NIDDConfiguration_TriggerNotify response) to NEF30H for the request message received in S132.

[0075] S134: P-CSCF30J sends a request message (Nnef_NIDDConfiguration_Create request) to NEF30H requesting the activation of the configuration requested in S132. This request message includes information indicating high priority, for example, written as Nnef_NIDDConfiguration_Create request (NiddConfiguration(Priority(highPriority))).

[0076] S135: NEF30H sends a response message (Nnef_NIDDConfiguration_Create response) to P-CSCF30J for the request message received in S134.

[0077] The process following S135 will now be described. Figure 9 is a diagram showing an example of a third sequence diagram in an embodiment of the present invention. The process of each step will be described below.

[0078] S141:AMF30A sends a request message (Nsmf_PDUSession_SendMOData request) to SMF30E requesting data transmission. This message includes a priority call request (SIP INVITE(Resource-Priority)) and is written as, for example, Nsmf_PDUSession_SendMOData request (SendMoDataReqData (moData (RefToBinaryData), SIP INVITE (Resource-Priority))).

[0079] S142: SMF30E sends a response message (Nsmf_PDUSession_SendMOData response) to AMF30A for the request message received in S141.

[0080] S143: SMF30E sends a request message (Nnef_SMContext_Delivery request) to NEF30H requesting the transmission of SM context information. This message includes a priority call request (SIP INVITE (Resource-Priority)) and is written as, for example, Nnef_SMContext_Delivery request (data(RefToBinaryData), SIP INVITE (Resource-Priority)).

[0081] S144: NEF30H sends a response message (Nnef_SMContext_Delivery response) to SMF30E for the request message received in S143.

[0082] S145:NEF30H sends a request message (Nnef_NIDD_DeliveryNotify request) to P-CSCF30J requesting data transmission, which includes a priority call request (SIP INVITE (Resource-Priority)). This message is written, for example, as Nnef_NIDD_DeliveryNotify request (NiddUplinkDataNotification(data(SIP INVITE (Resource-Priority)))).

[0083] S146: P-CSCF30J sends a response message (Nnef_NIDD_DeliveryNotify response) to NEF30H for the request message received in S145.

[0084] S147: P-CSCF30J sends a priority call request (SIP INVITE (Resource-Priority)) to S-CSCF30K.

[0085] S148: S-CSCF30K sends a message (SIP 183 Session Progress) to P-CSCF30J indicating that the IMS voice call is being processed.

[0086] S149:P-CSCF30J recognizes that it is necessary to establish a new IMS PDU session for voice media. Here, the establishment of QoS flows, which is performed in a normal voice call, is not performed when using a NIDD PDU session.

[0087] S150:P-CSCF30J sends a request message (Nnef_NIDD_Delivery request) to NEF30H requesting the transmission of a message indicating that an IMS voice call is being processed (SIP 183 Session Progress). This request message is written, for example, as Nnef_NIDD_Delivery request (NiddDownlinkDataTransfer(data(SIP 183 Session Progress))).

[0088] S151:NEF30H sends a response message (Nnef_NIDD_Delivery response) to P-CSCF30J for the request message received in S150.

[0089] S152:NEF30H sends a request message (Nsmf_NIDD_Delivery request) to SMF30E requesting it to send a message indicating that an IMS voice call is being processed (SIP 183 Session Progress).

[0090] S153: SMF30E sends a response message (Nsmf_NIDD_Delivery response) to NEF30H for the request message received in S152.

[0091] S154: SMF30E sends a request message (Namf_Communication_N1N2MessageTransfer request) to AMF30A requesting the sending of a message indicating that an IMS voice call is being processed (SIP 183 Session Progress). This message is written, for example, as Namf_Communication_N1N2MessageTransfer request (N1N2MessageTransferReqData (mtData(RefToBinaryData)), SIP 183 Session Progress).

[0092] S155: AMF30A sends a response message (Namf_Communication_N1N2MessageTransfer response) to SMF30E for the request message received in S154.

[0093] S156: The AMF30A generates a NAS message that superimposes a message indicating that an IMS voice call is being processed (SIP 183 Session Progress) and information indicating service acceptance for the service request and control plane service request contained in the message received in S122.

[0094] S157: The AMF30A sends a message (Downlink NAS Transport) to the base station 10 to forward the NAS message generated in S156. This NAS message is written as, for example, Downlink NAS Transport(NAS-PDU(Service accept(NAS message container(Service accept(Payload container type(CIoT user data container), Payload container(user data container(SIP 183 Session Progress))))))).

[0095] S158: Base station 10 sends a message (DLInformationTransfer) to terminal 20 to transfer the NAS message received in S157.

[0096] The process following S158 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.

[0097] S170: Based on the message (SIP 183 Session Progress) received in S160 in Figure 9 indicating that IMS voice call processing is in progress, terminal 20 decides to establish a preferred PDU session for the IMS preferred call voice media in subsequent processing.

[0098] S171: Terminal 20 sends a message (ULInformationTransfer) to base station 10 that forwards a NAS message containing a request to establish a preferred PDU session for IMS preferred call voice media. This message is written as, for example, ULInformationTransfer(dedicatedNAS-Message(UL NAS transport(Request type(initial request), Payload container type(N1 SM information), Payload container(PDU Session Establishment request), DNN=ims))).

[0099] S172: Base station 10 sends an Uplink NAS Transport message to AMF30A that forwards a NAS message containing a request to establish a priority PDU session for IMS priority call voice media. This message is written as, for example, Uplink NAS Transport(NAS-PDU(UL NAS transport(Request type(initial request), Payload container type(N1 SM information), Payload container(PDU Session Establishment request), DNN=ims))).

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

[0101] S174: AMF30A sends a request message (Nsmf_PDUSession_CreateSMContext request) to SMF30E requesting the establishment / configuration of a preferred PDU session for IMS preferred call voice media. This request message includes a setting of the RAT type (ratType=nb-IoT-GEO) indicating NB IoT radio access via geostationary satellite, and is written as, for example, Nsmf_PDUSession_CreateSMContext request(SmContextCreateData(Dnn=ims, requestType(INITIAL_REQUEST), n1SmMsg(PDU session establishment request), ratType=NB_IOT_GEO)).

[0102] S175: SMF30E sends a response message (Nsmf_PDUSession_CreateSMContext response) to AMF30A for the request message received in S174.

[0103] S176: SMF30E sends a request message (Npcf_SMPolicyControl_Create request) to PCF30G 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)).

[0104] S177:PCF30G 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.

[0105] S178: PCF30G sends a response message (Npcf_SMPolicyControl_Create response) to the request message received in S176, which includes a policy that QoS should be set for voice media communication, to SMF30E. 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)))).

[0106] S179: SMF30E sends a request message (PFCP Session Establishment request) to UPF30F for the establishment of a user data transfer path.

[0107] S180:UPF30F sends a response message (PFCP Session Establishment response) to SMF30E for the request message received in S179.

[0108] S181: SMF30E sends a message to AMF30A 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))))).

[0109] S182: AMF30A sends a response message (Namf_Communication_N1N2MessageTransfer response) to SMF30E for the request message received in S181.

[0110] S183: The AMF30A 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 S182. 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)))).

[0111] S184: 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 S171. 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)))).

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

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

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

[0115] S188: SMF30C sends a response message (Nsmf_PDUSession_UpdateSMContext response) to AMF30B for the request message received in S187.

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

[0117] S190: UPF30A sends a response message (PFCP Session Modification response) to SMF30C for the request message received in S189.

[0118] The process following S190 will now be described. Figure 11 is a diagram showing an example of a fifth sequence diagram in an embodiment of the present invention. The process of each step will be described below.

[0119] S201: Terminal 20 decides to proceed with the configuration, assuming that local resources are available and the preconditions are met.

[0120] S202: Terminal 20 sends a message (ULInformationTransfer) to base station 10 that forwards a NAS message containing a provisional response (PRACK) to a message indicating that a voice call is being processed (SIP 183 Session Progress). This message is written as, for example, ULInformationTransfer(dedicatedNAS-Message(UL NAS transport(Payload container type(CIoT user data container), Payload container(user data container(PRACK))))).

[0121] S203: Base station 10 sends a message (Uplink NAS Transport) to AMF30A to forward the NAS message containing the provisional response (PRACK). This message is written as, for example, Uplink NAS Transport(NAS-PDU(UL NAS transport(Payload container type(CIoT user data container), Payload container(user data container(PRACK))))).

[0122] S204:AMF30A sends a request message (Nsmf_PDUSession_SendMOData request) to SMF30E requesting data transmission. This request message is written as, for example, Nsmf_PDUSession_SendMOData request (SendMoDataReqData(moData(RefToBinaryData), PRACK)).

[0123] S205: SMF30E sends a response message (Nsmf_PDUSession_SendMOData response) to AMF30A for the request message received in S204.

[0124] S206:SMF30E sends a request message (Nnef_SMContext_Delivery request) to NEF30H requesting the transmission of SM context information, including a provisional response (PRACK). This request message is written, for example, as Nnef_SMContext_Delivery request (data(RefToBinaryData), PRACK).

[0125] S207:NEF30H sends a response message (Nnef_SMContext_Delivery response) to SMF30E for the request message received in S206.

[0126] S208:NEF30H sends a request message (Nnef_NIDD_DeliveryNotify request) to P-CSCF30J requesting data transmission, including a provisional response (PRACK). This request message is written, for example, as Nnef_NIDD_DeliveryNotify request (NiddUplinkDataNotification(data(PRACK))).

[0127] S209: P-CSCF30J sends a response message (Nnef_NIDD_DeliveryNotify response) to NEF30H for the request message received in S208.

[0128] S210: P-CSCF30J sends a provisional response (PRACK) to S-CSCF30K.

[0129] S211: S-CSCF30K sends an acknowledgment (200 OK(PRACK)) to P-CSCF30J in response to the provisional response (PRACK).

[0130] S212: S-CSCF30K sends a response (SIP 200 OK) to P-CSCF30J for the priority call request (SIP INVITE (Resource-Priority)) received in S147.

[0131] S213:P-CSCF30J stores received messages after receiving an acknowledgment (200 OK (PRACK)) for a provisional response (PRACK) until it receives a response (SIP 200 OK) for a priority call request (SIP INVITE (Resource-Priority)).

[0132] S214:P-CSCF30J sends a request message (Nnef_NIDD_Delivery request) to NEF30H requesting data transmission, including 200 OK (PRACK) and SIP 200 OK. This request message is written as, for example, Nnef_NIDD_Delivery request (NiddDownlinkDataTransfer(data(200 OK(PRACK), SIP 200 OK))).

[0133] S215:NEF30H sends a response message (Nnef_NIDD_Delivery response) to P-CSCF30J for the request message received in S214.

[0134] S216:NEF30H sends a request message (Nsmf_NIDD_Delivery request) to SMF30E requesting data transmission, including 200 OK (PRACK) and SIP 200 OK. This request message is written, for example, as Nsmf_NIDD_Delivery request (DeliverReqData(mtData(RefToBinaryData)), 200 OK (PRACK), SIP 200 OK).

[0135] S217: SMF30E sends a response message (Nsmf_NIDD_Delivery response) to NEF30H for the request message received in S216.

[0136] S218: SMF30E sends a request message (Namf_Communication_N1N2MessageTransfer request) to AMF30A to transfer 200 OK (PRACK) and SIP 200 OK. This request message is written as Namf_Communication_N1N2MessageTransfer request (N1N2MessageTransferReqData (mtData(RefToBinaryData)), 200 OK (PRACK), SIP 200 OK).

[0137] S219: AMF30A sends a response message (Namf_Communication_N1N2MessageTransfer response) to SMF30E for the request message received in S218.

[0138] S220:AMF30A sends a message (Downlink NAS Transport) to base station 10 that forwards 200 OK (PRACK) and SIP 200 OK. This message is written as, for example, Downlink NAS Transport(NAS-PDU(DL NAS transport(Payload container type(CIoT user data container), Payload container(user data container(200 OK(PRACK), SIP 200 OK))))).

[0139] S221: Base station 10 sends a message (DLInformationTransfer) to terminal 20 that transfers 200 OK (PRACK) and SIP 200 OK. This message is written as, for example, DLInformationTransfer (dedicatedNAS-Message(DL NAS transport(Payload container type(CIoT user data container), Payload container(user data container(200 OK(PRACK), SIP 200 OK))))).

[0140] The process following S221 will now be described. Figure 12 shows an example of a sixth sequence diagram in an embodiment of the present invention. The process of each step will be described below.

[0141] S231: Terminal 20 sends a message (ULInformationTransfer) to base station 10 that forwards the response (ACK) to SIP 200 OK received in S221 in Figure 12. This message is written as, for example, ULInformationTransfer(dedicatedNAS-Message(UL NAS transport(Payload container type(CIoT user data container), Payload container(user data container(ACK))))).

[0142] S232: Base station 10 sends a message (Uplink NAS Transport) to AMF30A that forwards the acknowledgment (ACK) for SIP 200 OK. This message is written as, for example, Uplink NAS Transport(NAS-PDU(UL NAS transport(Payload container type(CIoT user data container), Payload container(user data container(ACK))))).

[0143] S233:AMF30A sends a request message (Nsmf_PDUSession_SendMOData request) to SMF30E, which includes an acknowledgment (ACK) for SIP 200 OK, requesting data transmission.

[0144] S234: SMF30E sends a response message (Nsmf_PDUSession_SendMOData response) to AMF30A for the request message received in S233.

[0145] S235:SMF30E sends a request message (Nnef_SMContext_Delivery request) to NEF30H requesting the transmission of SM context information, including an acknowledgment (ACK) for SIP 200 OK. This request message is written, for example, as Nnef_SMContext_Delivery request (data(RefToBinaryData), ACK).

[0146] S236: NEF30H sends a response message (Nnef_SMContext_Delivery response) to SMF30E for the request message received in S235.

[0147] S237:NEF30H sends a request message (Nnef_NIDD_DeliveryNotify request) to P-CSCF30J requesting data transmission, including an acknowledgment (ACK) for SIP 200 OK. This request message is written, for example, as Nnef_NIDD_DeliveryNotify request (NiddUplinkDataNotification (data(ACK))).

[0148] S238: P-CSCF30J sends a response message (Nnef_NIDD_DeliveryNotify response) to NEF30H for the request message received in S237.

[0149] S239: P-CSCF30J sends an acknowledgment (ACK) for SIP 200 OK to S-CSCF30K.

[0150] (Procedure for receiving incoming calls from priority users to general users) The procedure for receiving calls from priority users to general users will be explained using a sequence diagram. Figure 13 shows an example of the seventh sequence diagram in an embodiment of the present invention. The processing of each step will be explained below.

[0151] S301: Terminal 20 receives broadcast information (System Information Block (SIB)) from base station 10, including information (ims-NasCombinedSupport) indicating that NAS / IMS integrated processing is permitted. Terminal 20 also recognizes that it is within range of a base station that provides NB (Narrow Band) IoT (Internet of Things) wireless access via geostationary satellite.

[0152] S302: I-CSCF30M sends a priority call request (SIP INVITE (Resource-Priority)) for an IMS voice call to S-CSCF30K.

[0153] S303: S-CSCF30K sends an IMS voice call priority initiation request (SIP INVITE (Resource-Priority)) to P-CSCF30J, requesting the initiation of voice communication regarding the priority call.

[0154] S304: In response to the priority call request for the IMS voice call received in S303, P-CSCF30J decides to change the priority of the NIDD PDU session to a higher priority.

[0155] S305:P-CSCF30J sends a request message (Nnef_NIDDConfiguration_Update request) to NEF30H requesting that the priority of the NIDD PDU session be changed to a higher priority (i.e., that the priority of the configured control plane path for sending and receiving IMS messages of general priority be changed to a higher priority). This request message is written, for example, as Nnef_NIDDConfiguration_Update request (NiddConfigurationPatch (Priority (highPriority))).

[0156] S306: NEF30H sends a response message (Nnef_NIDDConfiguration_Update response) to P-CSCF30J for the request message received in S305. NEF30H increases the priority of the route in response to the request message.

[0157] S307:NEF30H sends a request message (Nnef_SMContext_UpdateNotify request) to SMF30E requesting an update to the SM context (i.e., changing the priority of the configured control plane path for sending and receiving IMS messages of general priority to a higher priority). This request message is written, for example, as Nnef_SMContext_UpdateNotify request (CiotUserDataRequestType(highPriority ims)).

[0158] S308: SMF30E sends a response message (Nnef_SMContext_UpdateNotify response) to NEF30H for the request message received in S307. SMF30E increases the priority of the route in response to the request message.

[0159] S309: SMF30E sends a request message (Namf_Communication_N1N2MessageTransfer request) to AMF30A requesting that the priority of the NIDD PDU session be changed to a higher priority (i.e., that the priority of the configured control plane route for sending and receiving IMS messages of general priority be changed to a higher priority). This request message is written, for example, as Namf_Communication_N1N2MessageTransfer request (CiotUserDataRequestType(highPriority ims)).

[0160] S310: AMF30A sends a response message (Namf_Communication_N1N2MessageTransfer response) to SMF30E for the request message received in S309.

[0161] S311:P-CSCF30J sends a request message (Nnef_NIDD_Delivery request) to NEF30H requesting the sending of a priority call request (SIP INVITE(Resource-Priority)) for an IMS voice call. This request message is written as, for example, Nnef_NIDD_Delivery request (NiddDownlinkDataTransfer(data(SIP INVITE(Resource-Priority)))).

[0162] S312:NEF30H sends a response message (Nnef_NIDD_Delivery response) to P-CSCF30J for the request message received in S311.

[0163] S313:NEF30H sends a request message (Nsmf_NIDD_Delivery request) to SMF30E requesting the sending of a priority call request for IMS voice calls (SIP INVITE (Resource-Priority)).

[0164] S314: SMF30E sends a response message (Nsmf_NIDD_Delivery response) to NEF30H for the request message received in S313.

[0165] S315: SMF30E sends a request message (Namf_Communication_N1N2MessageTransfer request) to AMF30A requesting the sending of a priority call request for IMS voice calls (SIP INVITE(Resource-Priority)). This message is written, for example, as Namf_Communication_N1N2MessageTransfer request (N1N2MessageTransferReqData (mtData(RefToBinaryData)), SIP INVITE(Resource-Priority)).

[0166] S316: AMF30A sends a response message (Namf_Communication_N1N2MessageTransfer response) to SMF30E for the request message received in S315.

[0167] S317: The AMF30A transmits a priority call (Paging) for an IMS voice call to base station 10.

[0168] S318: Base station 10 sends a priority call (Paging) for an IMS voice call to terminal 20.

[0169] The process following S318 will now be described. Figure 14 is a diagram showing an example of the eighth sequence diagram in an embodiment of the present invention. The process of each step will be described below.

[0170] S321: Terminal 20 sends a request message (RRCSetup request) to base station 10 requesting RRC configuration.

[0171] S322: The base station 10 sends a response message (RRCSetup) to the terminal 20 for the request message received in S321.

[0172] S323: Terminal 20 sends a message (RRCSetupComplete) to base station 10 notifying it that the RRC setup is complete. This message is written as, for example, RRCSetupComplete (dedicatedNAS-Message(Service request)).

[0173] S324: Base station 10 sends a message (Initial UE message) to AMF30A containing information indicating a service request to 5GS. This message is, for example, denoted as Initial UE message (NAS-PDU (Service request)).

[0174] S325:AMF30A sends an Initial Context Setup request to base station 10.

[0175] S326: Base station 10 sends a SecurityModeCommand to terminal 20.

[0176] S327: Terminal 20 sends SecurityModeComplete to base station 10.

[0177] S328: Base station 10 sends an Initial Context Setup response to AMF30A.

[0178] S329:AMF30A sends a Downlink NAS Transport to base station 10. This message is written as, for example, Downlink NAS Transport (NAS-PDU (Security Mode Command)).

[0179] S330: Base station 10 sends DLInformationTransfer to terminal 20. This message is written as, for example, DLInformationTransfer(dedicatedNAS-Message(Security Mode Command)).

[0180] S331: Terminal 20 sends a message (ULInformationTransfer) to base station 10 that forwards a NAS message containing a service request. This message is written as, for example, ULInformationTransfer(dedicatedNAS-Message(Security Mode Complete(NAS message container(Service request)))).

[0181] S332: Base station 10 sends an Uplink NAS Transport message to AMF30A that forwards a NAS message containing a service request. This message is written as, for example, Uplink NAS Transport(NAS-PDU(Security Mode Complete(NAS message container(Service request)))).

[0182] S333:AMF30A sends a request message (Downlink NAS Transport) to base station 10 requesting the transmission of a priority call request (SIP INVITE(Resource-Priority)) for IMS voice calls. This message is written as, for example, Downlink NAS Transport(NAS-PDU(Service accept(Payload container type(CIoT user data container), Payload container(user data container(SIP INVITE(Resource-Priority)))))).

[0183] S334: Base station 10 sends a request message (DLInformationTransfer) to terminal 20 requesting the sending of a priority call request (SIP INVITE(Resource-Priority)) for an IMS voice call. This message is written as, for example, DLInformationTransfer(dedicatedNAS-Message(Service accept(Payload container type(CIoT user data container), Payload container(user data container(SIP INVITE(Resource-Priority)))))).

[0184] The process following S334 will now be described. Figure 15 shows an example of the ninth sequence diagram in an embodiment of the present invention. The process of each step will be described below.

[0185] S340: Terminal 20 recognizes that it is necessary to establish a priority PDU session for the IMS priority call voice media based on the priority call request (SIP INVITE (Resource-Priority)) for the IMS voice call received in S334 in Figure 14. Terminal 20 also decides to behave as if it were the terminal of the priority user.

[0186] S341: Terminal 20 sends a message (ULInformationTransfer) to base station 10 that forwards a NAS message containing a request to establish a preferred PDU session for IMS preferred call voice media. This message is written as, for example, ULInformationTransfer(dedicatedNAS-Message(UL NAS transport(Request type(initial request), Payload container type(N1 SM information), Payload container(PDU Session Establishment request), DNN=ims))).

[0187] S342: Base station 10 sends an Uplink NAS Transport message to AMF30A that forwards a NAS message containing a request to establish a preferred PDU session for IMS preferred call voice media. This message is written as, for example, Uplink NAS Transport(NAS-PDU(UL NAS transport(Request type(initial request), Payload container type(N1 SM information), Payload container(PDU Session Establishment request), DNN=ims))).

[0188] S343: Based on the transport information that transmitted the message received in S342, the AMF30A recognizes that a base station (nb-IoT-GEO) providing NB IoT radio access via geostationary satellites is accommodating the terminal.

[0189] S344: AMF30A sends a request message (Nsmf_PDUSession_CreateSMContext request) to SMF30E requesting the establishment / configuration of a priority PDU session for IMS priority call voice media. This request message includes a setting of the RAT type (ratType=nb-IoT-GEO) indicating NB IoT radio access via geostationary satellite, and is written as, for example, Nsmf_PDUSession_CreateSMContext request(SmContextCreateData(Dnn=ims, requestType(INITIAL_REQUEST), n1SmMsg(PDU session establishment request), ratType=NB_IOT_GEO)).

[0190] S345: SMF30E sends a response message (Nsmf_PDUSession_CreateSMContext response) to AMF30A for the request message received in S344.

[0191] S346: SMF30E sends a request message (Npcf_SMPolicyControl_Create request) to PCF30G 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)).

[0192] S347:PCF30G 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.

[0193] S348: PCF30G sends a response message (Npcf_SMPolicyControl_Create response) to the request message received in S346, which includes a policy that QoS should be set for voice media communication, to SMF30E. 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)))).

[0194] S349: SMF30E sends a request message (PFCP Session Establishment request) to UPF30F for the establishment of a user data transfer path.

[0195] S350:UPF30F sends a response message (PFCP Session Establishment response) to SMF30E for the request message received in S349.

[0196] S351: SMF30E sends a message to AMF30A 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))))).

[0197] S352: AMF30A sends a response message (Namf_Communication_N1N2MessageTransfer response) to SMF30E for the request message received in S351.

[0198] S353: The AMF30A 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 S352. 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)))).

[0199] S354: Base station 10 sends a message to terminal 20 regarding the configuration of the RRC (RRCReconfiguration), which includes information indicating acceptance of the PDU session establishment requested in S351. 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)))).

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

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

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

[0203] S358: SMF30C sends a response message (Nsmf_PDUSession_UpdateSMContext response) to AMF30B for the request message received in S357.

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

[0205] S360:UPF30A sends a response message (PFCP Session Modification response) to SMF30C for the request message received in S359.

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

[0207] S361: Terminal 20 decides to proceed with the configuration, assuming that local resources are available and the preconditions are met.

[0208] S362: Terminal 20 sends a message (ULInformationTransfer) to base station 10 that forwards a NAS message containing a message indicating that a voice call is being processed (SIP 183 Session Progress). This message is written as, for example, ULInformationTransfer(dedicatedNAS-Message(UL NAS transport(Payload container type(CIoT user data container), Payload container(user data container(SIP 183 Session Progress))))).

[0209] S363: Base station 10 sends an Uplink NAS Transport message to AMF30A that forwards a NAS message containing a message indicating that a voice call is being processed (SIP 183 Session Progress). This message is written as, for example, Uplink NAS Transport(NAS-PDU(UL NAS transport(Payload container type(CIoT user data container), Payload container(user data container(SIP 183 Session Progress))))).

[0210] S364:AMF30A sends a request message (Nsmf_PDUSession_SendMOData request) to SMF30E requesting data transmission. This request message is written as, for example, Nsmf_PDUSession_SendMOData request (SendMoDataReqData(moData(RefToBinaryData), SIP 183 Session Progress)).

[0211] S365: SMF30E sends a response message (Nsmf_PDUSession_SendMOData response) to AMF30A for the request message received in S364.

[0212] S366:SMF30E sends a request message (Nnef_SMContext_Delivery request) to NEF30H requesting the transmission of SM context information, which includes a message indicating that a voice call is being processed (SIP 183 Session Progress). This request message is written, for example, as Nnef_SMContext_Delivery request (data(RefToBinaryData), SIP 183 Session Progress).

[0213] S367: NEF30H sends a response message (Nnef_SMContext_Delivery response) to SMF30E for the request message received in S366.

[0214] S368:NEF30H sends a request message (Nnef_NIDD_DeliveryNotify request) to P-CSCF30J that requests data transmission, including a message indicating that a voice call is being processed (SIP 183 Session Progress). This request message is written, for example, as Nnef_NIDD_DeliveryNotify request (NiddUplinkDataNotification(data(SIP 183 Session Progress))).

[0215] S369: P-CSCF30J sends a response message (Nnef_NIDD_DeliveryNotify response) to NEF30H for the request message received in S368.

[0216] S370:P-CSCF30J sends a message (SIP 183 Session Progress) to S-CSCF30K indicating that the voice call is being processed.

[0217] S371: S-CSCF30M sends a message (SIP 183 Session Progress) to I-CSCF30M indicating that the voice call is being processed.

[0218] S372: I-CSCF30M sends a provisional response (PRACK) to S-CSCF30K.

[0219] S373: S-CSCF30K sends a provisional response (PRACK) to P-CSCF30J.

[0220] S374:P-CSCF30J sends a request message (Nnef_NIDD_Delivery request) to NEF30H requesting the transmission of a provisional response (PRACK). This request message is written as, for example, Nnef_NIDD_Delivery request (NiddDownlinkDataTransfer(data(PRACK))).

[0221] S375:NEF30H sends a response message (Nnef_NIDD_Delivery response) to P-CSCF30J for the request message received in S373.

[0222] S376:NEF30H sends a request message (Nsmf_NIDD_Delivery request) to SMF30E requesting the sending of a provisional response (PRACK). This request message is written, for example, as Nsmf_NIDD_Delivery request (DeliverReqData(mtData(RefToBinaryData)), PRACK).

[0223] S377: SMF30E sends a response message (Nsmf_NIDD_Delivery response) to NEF30H for the request message received in S375.

[0224] S378: SMF30E sends a request message (Namf_Communication_N1N2MessageTransfer request) to AMF30A to transfer a provisional response (PRACK). This request message is written as Namf_Communication_N1N2MessageTransfer request (N1N2MessageTransferReqData (mtData(RefToBinaryData)), PRACK).

[0225] S379: AMF30A sends a response message (Namf_Communication_N1N2MessageTransfer response) to SMF30E for the request message received in S377.

[0226] S380:AMF30A sends a message (Downlink NAS Transport) to base station 10 to forward a provisional response (PRACK). This message is written as, for example, Downlink NAS Transport(NAS-PDU(DL NAS transport(Payload container type(CIoT user data container), Payload container(user data container(PRACK))))).

[0227] S381: Base station 10 sends a message (DLInformationTransfer) to terminal 20 to transfer a provisional response (PRACK). This message is written as, for example, DLInformationTransfer (dedicatedNAS-Message(DL NAS transport(Payload container type(CIoT user data container), Payload container(user data container(PRACK))))).

[0228] The process following S381 will now be described. Figure 17 is a diagram showing an example of the 11th sequence diagram in an embodiment of the present invention. The process of each step will be described below.

[0229] S391: Terminal 20 sends a message (ULInformationTransfer) to base station 10 that forwards a NAS message containing an acknowledgment (200 OK(PRACK)) for a provisional response (PRACK). This message is written as, for example, ULInformationTransfer(dedicatedNAS-Message(UL NAS transport(Payload container type(CIoT user data container), Payload container(user data container(200 OK(PRACK)))))).

[0230] S392: Base station 10 sends a message (Uplink NAS Transport) to AMF30A that forwards a NAS message containing an acknowledgment (200 OK(PRACK)) for a provisional response (PRACK). This message is written as, for example, Uplink NAS Transport(NAS-PDU(UL NAS transport(Payload container type(CIoT user data container), Payload container(user data container(200 OK(PRACK)))))).

[0231] S393: AMF30A sends a request message (Nsmf_PDUSession_SendMOData request) to SMF30E requesting data transmission. This request message is written as, for example, Nsmf_PDUSession_SendMOData request (SendMoDataReqData (moData(RefToBinaryData), 200 OK(PRACK))).

[0232] S394: SMF30E sends a response message (Nsmf_PDUSession_SendMOData response) to AMF30A for the request message received in S393.

[0233] S395:SMF30E sends a request message (Nnef_SMContext_Delivery request) to NEF30H requesting the transmission of SM context information, including an acknowledgment (200 OK(PRACK)) for the provisional response (PRACK). This request message is written, for example, as Nnef_SMContext_Delivery request (data(RefToBinaryData), 200 OK(PRACK)).

[0234] S396: NEF30H sends a response message (Nnef_SMContext_Delivery response) to SMF30E for the request message received in S395.

[0235] S397:NEF30H sends a request message (Nnef_NIDD_DeliveryNotify request) to P-CSCF30J requesting data transmission, which includes an acknowledgment (200 OK(PRACK)) for the provisional response (PRACK). This request message is written, for example, as Nnef_NIDD_DeliveryNotify request (NiddUplinkDataNotification(data(200 OK(PRACK)))).

[0236] S398: P-CSCF30J sends a response message (Nnef_NIDD_DeliveryNotify response) to NEF30H for the request message received in S397.

[0237] S399: P-CSCF30J sends an acknowledgment (200 OK(PRACK)) to S-CSCF30K in response to the provisional response (PRACK).

[0238] S400:S-CSCF30M sends an acknowledgment (200 OK(PRACK)) to I-CSCF30M in response to the provisional response (PRACK).

[0239] S401: I-CSCF30M sends an update to the voice communication channel settings to S-CSCF30K.

[0240] S402: S-CSCF30K sends an update to the voice communication channel settings to P-CSCF30J.

[0241] S403:P-CSCF30J sends a request message (Nnef_NIDD_Delivery request) to NEF30H requesting the transmission of an update to the voice communication channel settings. This request message is written as, for example, Nnef_NIDD_Delivery request (NiddDownlinkDataTransfer(data(UPDATE))).

[0242] S404:NEF30H sends a response message (Nnef_NIDD_Delivery response) to P-CSCF30J for the request message received in S403.

[0243] S405:NEF30H sends a request message (Nsmf_NIDD_Delivery request) to SMF30E requesting the transmission of an update to the voice communication channel settings. This request message is written as, for example, Nsmf_NIDD_Delivery request (DeliverReqData(mtData(RefToBinaryData)), UPDATE).

[0244] S406: SMF30E sends a response message (Nsmf_NIDD_Delivery response) to NEF30H for the request message received in S405.

[0245] S407: SMF30E sends a request message (Namf_Communication_N1N2MessageTransfer request) to AMF30A to transfer an update to the voice communication channel settings. This request message is written as Namf_Communication_N1N2MessageTransfer request (N1N2MessageTransferReqData (mtData(RefToBinaryData)), UPDATE).

[0246] S408: AMF30A sends a response message (Namf_Communication_N1N2MessageTransfer response) to SMF30E for the request message received in S407.

[0247] S409:AMF30A sends a message (Downlink NAS Transport) to base station 10 to transfer a voice communication channel configuration update (UPDATE). This message is written as, for example, Downlink NAS Transport(NAS-PDU(DL NAS transport(Payload container type(CIoT user data container), Payload container(user data container(UPDATE))))).

[0248] S410: Base station 10 sends a message (DLInformationTransfer) to terminal 20 to transfer a voice communication channel configuration update (UPDATE). This message is written as, for example, DLInformationTransfer (dedicatedNAS-Message(DL NAS transport(Payload container type(CIoT user data container), Payload container(user data container(UPDATE))))).

[0249] The process following S410 will now be described. Figure 18 is a diagram showing an example of the 12th sequence diagram in an embodiment of the present invention. The process of each step will be described below.

[0250] S420: Terminal 20 decides to superimpose 200 OK (UPDATE) and SIP 200 OK into the same message.

[0251] S421: Terminal 20 sends a message (ULInformationTransfer) to base station 10 that forwards NAS messages including 200 OK (UPDATE) and SIP 200 OK. This message is written as, for example, ULInformationTransfer(dedicatedNAS-Message(UL NAS transport(Payload container type(CIoT user data container), Payload container(user data container(200 OK(UPDATE), SIP 200 OK))))).

[0252] S422: Base station 10 sends a message (Uplink NAS Transport) to AMF30A that forwards NAS messages including 200 OK (UPDATE) and SIP 200 OK. This message is written as, for example, Uplink NAS Transport(NAS-PDU(UL NAS transport(Payload container type(CIoT user data container), Payload container(user data container(200 OK(UPDATE), SIP 200 OK))))).

[0253] S423:AMF30A sends a request message (Nsmf_PDUSession_UpdateSMContext request) to SMF30E requesting an update to the SM context for the PDU session. This request message is written as, for example, Nsmf_PDUSession_SendMOData request (SendMoDataReqData (moData(RefToBinaryData), 200 OK(UPDATE), SIP 200 OK)).

[0254] S424: SMF30E sends a response message (Nsmf_PDUSession_SendMOData response) to AMF30A for the request message received in S423.

[0255] S425:SMF30E sends a request message (Nnef_SMContext_Delivery request) to NEF30H requesting the transmission of SM context information, including 200 OK (UPDATE) and SIP 200 OK. This request message is written, for example, as Nnef_SMContext_Delivery request (data(RefToBinaryData), 200 OK(UPDATE), SIP 200 OK).

[0256] S426: NEF30H sends a response message (Nnef_SMContext_Delivery response) to SMF30E for the request message received in S425.

[0257] S427:NEF30H sends a request message (Nnef_NIDD_DeliveryNotify request) to P-CSCF30J requesting the transmission of data including 200 OK (UPDATE) and SIP 200 OK. This request message is written as, for example, Nnef_NIDD_DeliveryNotify request (NiddUplinkDataNotification(data(200 OK(UPDATE), SIP 200 OK))).

[0258] S428: P-CSCF30J sends a response message (Nnef_NIDD_DeliveryNotify response) to NEF30H for the request message received in S427.

[0259] S429: P-CSCF30J sends 200 OK (UPDATE) to S-CSCF30K.

[0260] S430: S-CSCF30M sends 200 OK (UPDATE) to I-CSCF30M.

[0261] S431:P-CSCF30J sends SIP 200 OK to S-CSCF30K.

[0262] S432: S-CSCF30M sends SIP 200 OK to I-CSCF30M.

[0263] The above-described embodiment allows for the definition of a procedure for initiating a priority call in a radio communication system using geostationary satellites.

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

[0265] <Base station 10 and network node 30> Figure 19 shows an example of the functional configuration of a base station 10 and a network node 30. As shown in Figure 19, 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 19 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.

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

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

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

[0269] <Terminal 20> FIG. 20 is a diagram illustrating an example of a functional configuration of the terminal 20. As illustrated in FIG. 20, the terminal 20 includes a transmitting unit 210, a receiving unit 220, a setting unit 230, and a control unit 240. The functional configuration illustrated in FIG. 20 is merely an example. Any functional classification and any name of a functional unit may be used as long as the operation according to the embodiment of the present invention can be performed. Further, a communication apparatus serving as the resource holder 20 may have the same functional configuration as that of the terminal 20.

[0270] The transmitting unit 210 generates a transmission signal from transmission data, and wirelessly transmits the transmission signal. The receiving unit 220 wirelessly receives various signals, and acquires a higher-layer signal from the received physical layer signal. Further, the receiving unit 220 has a function of receiving a control signal, a reference signal, or the like transmitted from the network node 30. A communication unit including the transmitting unit 210 and the receiving unit 220 may be configured.

[0271] The setting unit 230 stores various pieces of setting information received from the network node 30 by the receiving unit 220 into a storage device, and reads the information from the storage device as necessary. Further, the setting unit 230 also stores preset setting information.

[0272] The control unit 240 performs the processing described in the example. A functional unit related to signal transmission in the control unit 240 may be included in the transmitting unit 210, and a functional unit related to signal reception in the control unit 240 may be included in the receiving unit 220.

[0273] (Hardware Configuration) The block diagrams (Figures 19 and 20) 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 above one device or the above multiple devices with software.

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

[0275] 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 21 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.

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

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

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

[0279] 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 19 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 20 may be implemented by a control program stored in the storage device 1002 and operated by the processor 1001. Although the above processes have been described 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.

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

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

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

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

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

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

[0286] Figure 22 shows an example of the configuration of vehicle 2001. As shown in Figure 22, vehicle 2001 comprises 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.

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

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

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

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

[0291] The driving support system unit 2030 includes millimeter-wave radar, LiDAR (Light Detection and Ranging), cameras, positioning locators (e.g., GNSS, etc.), map information (e.g., high-definition (HD) maps, autonomous driving vehicle (AV) maps, etc.), gyro systems (e.g., IMU (Inertial Measurement Unit), INS (Inertial Navigation System), etc.), AI (Artificial Intelligence) chips, and AI processors. It is composed of various devices for providing functions to prevent accidents in advance and reduce the driving load of drivers, and one or more ECUs that control these devices. The driving support system unit 2030 also transmits and receives various types of information via the communication module 2013 to implement driving support functions or autonomous driving functions.

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

[0293] 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 transmits and receives 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, a mobile station, or the like.

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

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

[0296] <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 receiving unit receives a message (SIP INVITE) from the first network node (S-CSCF30K) requesting the initiation of voice communication regarding a priority call, and (S303) The transmission unit sends a message to the second network node (NEF30H) requesting that the priority of the configured control plane route for sending and receiving IMS messages of general priority be changed to a higher priority, (S305) A network node (P-CSCF30J) that has [this feature]. (Additional note 2) The receiving unit receives a message from the first network node (P-CSCF30J / NEF30H) requesting that the priority of the configured control plane route for sending and receiving general priority data be changed to a higher priority, (S305 / S307) A control unit that increases the priority of the aforementioned path, and (S306 / S308) A transmission unit that forwards the message to the second network node (SMF30E / AMF30A), and (S313 / S315) Network nodes (NEF30H / SMF30E) that have this feature. (Additional note 3) 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 receives a message (SIP INVITE) from the first network node (AMF30A) via the base station requesting the initiation of voice communication regarding a priority call, (S318) It has, The control unit recognizes that it is necessary to establish a high-priority PDU (Protocol Data Unit) session for transmitting and receiving audio media, (S340) 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 high-priority PDU session (S341-S342). Terminal. (Additional note 4) A receiving unit that receives NAS (Non-Access Stratum) messages, including IMS messages related to control in IMS (IP Multimedia Subsystem) regarding priority calls, from a terminal via a base station, and (S121-S122) A transmission unit sends a request message to the first network node (SMF30E) to set up a high-priority route for sending and receiving IMS messages related to priority calls via the first network node between itself and the second network node (P-CSCF30J) which has a proxy function, (S125) A network node (AMF30A) that has [this feature]. (Additional note 5) A receiving unit receives a request message from the first network node (AMF30A) to set up a route on the high-priority control plane for sending and receiving IMS messages related to control in IMS (IP Multimedia Subsystem) for priority calls via its own device between the first network node and the second network node (P-CSCF30J) which has a proxy function, (S125) A control unit that derives the IP (Internet Protocol) address of the second network node, and (S126) A transmission unit that sends a message requesting the setting, including the IP address, to the third network node (NEF30H), (S127) A network node (SMF30E) that has [this feature]. (Additional note 6) A control unit that generates a NAS (Non-Access Stratum) message containing an IMS (IP Multimedia Subsystem) message related to a priority call, and (S121) A transmission unit that transmits the NAS message to the first network node (AMF30A) via the base station, (S121-S122) It has, The control unit, in the NAS message, The payload container, which is transparent to the first network node, includes the IMS message relating to the priority call. The information that the first network node can verify includes information indicating that the payload container contains content related to a priority call. Terminal.

[0297] Any of the appendices 1 to 6 may specify the procedure for initiating priority calls in a radio communication system using geostationary satellites.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0321] 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."

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

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

[0324] 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."

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

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

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

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

[0329] 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."

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

[0331] 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]

[0332] 10 base station 110 Transmitter 120 Receiver 130 Setting section 140 Control Unit 20 devices 210 Transmitter 220 Receiver 230 Setting section 240 Control Unit 30 network nodes 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 Department 2004 Accelerator pedal 2005 Brake pedal 2006 Shift Lever 2007 Front Wheel 2008 Rear wheel 2009 Axle 2010 Electronic Control Unit 2012 Information Services Department 2013 Communication Module 2021 Current Sensor 2022 Rotation speed sensor 2023 Pneumatic Sensor 2024 Vehicle Speed ​​Sensor 2025 Accelerometer 2026 Brake Pedal Sensor 2027 Shift lever sensor 2028 Object Detection Sensor 2029 Accelerator pedal sensor 2030 Driver Support Systems Department 2031 Microprocessor 2032 memory (ROM, RAM) 2033 Communication port (I / O port)

Claims

1. A receiving unit that receives a message from the first network node requesting the start of voice communication regarding a priority call, A transmitting unit that sends a message to the second network node requesting that the priority of the configured control plane route for sending and receiving IMS messages of general priority be increased, A network node that has

2. A receiving unit receives a message from the first network node requesting that the priority of a configured control plane path for sending and receiving general priority data be changed to a higher priority, A control unit that increases the priority of the aforementioned path, The second network node includes a transmission unit that forwards the message, A network node that has

3. 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 initiation of voice communication regarding a priority call, It has, The control unit recognizes that it is necessary to establish a high-priority PDU (Protocol 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 a base station requesting the establishment of the high-priority PDU session. Terminal.

4. A receiving unit that receives NAS (Non-Access Stratum) messages from a terminal via a base station, including IMS messages related to control in IMS (IP Multimedia Subsystem) regarding priority calls, A transmission unit that transmits a request message to a first network node to set up a high-priority route for sending and receiving IMS messages related to a priority call via the first network node between itself and a second network node having proxy functionality, A network node that has

5. A receiving unit receives a request message from a first network node to set up a high-priority control plane route for sending and receiving IMS messages related to control in IMS (IP Multimedia Subsystem) for priority calls between the first network node and a second network node having proxy functionality, via its own device. A control unit that derives the IP (Internet Protocol) address of the second network node, A transmission unit that sends a message requesting the setting, including the IP address, to the third network node, A network node that has

6. A control unit that generates NAS (Non-Access Stratum) messages including IMS (IP Multimedia Subsystem) messages related to priority calls, A transmission unit that transmits the NAS message to the first network node via the base station, It has, The control unit, in the NAS message, The payload container, which is transparent to the first network node, includes the IMS message relating to the priority call. The information that the first network node can verify includes information indicating that the payload container contains content related to a priority call. Terminal.

Images