Network node and communication method

Abstract

A network node comprises: a transmission unit that transmits, to a first network node, a first message requesting subscriber information; and a reception unit that receives, from the first network node, a second message which includes subscriber information, including first configuration information and second configuration information. The first configuration information indicates that when a third message is received from a terminal, said third message requesting voice call setup and including information indicating that the terminal is using satellite access, the third message is to be transferred to a second network node. The second configuration information indicates that when a fourth message is received from a third network node, said fourth message requesting voice call setup and including information indicating that a terminal on the other-network side is using satellite access, the fourth message is to be transferred to the second network node.

Description

Network Node and Communication Method

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

[0002] In 3GPP (Registered Trademark) (3rd Generation Partnership Project), in order to achieve further increase in system capacity, further increase in data transmission speed, further reduction in latency in the radio section, etc., a radio communication method called 5G or NR (New Radio) (hereinafter, this radio communication method is referred to as "5G" or "NR") is being studied. In 5G, in order to meet the requirement of achieving a throughput of 10 Gbps or more and reducing the latency in the radio section to 1 ms or less, various radio technologies are being studied.

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

[0004] Also, as an IMS (IP Multimedia Subsystem) architecture that supports the data channel capabilities of terminals, the specifications of the IMS data channel network are being studied (for example, Non-Patent Document 2). In the IMS data channel network, on each of the calling side and the called side, a DCSF (Data Channel Signalling Function) having a signalling function, an MF (Media Function) having a function related to media, and a DCAS (Data Channel Application Server) which is an application server are arranged.

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

[0006] 3GPP TS 23.501 V18.5.0 (2024-06) 3GPP TS 23.228 V18.6.0 (2024-06) 3GPP TR23.700-29 V19.0.0 (2024-06) 3GPP TS 38.331 V18.0.0 (2023-12) 3GPP TS 38.413 V18.0.0 (2023-12) 3GPP TS 23.502 V18.7.0 (2024-06) 3GPP TS 29.512 V18.7.0 (2024-09) 3GPP TS 29.514 V18.7.0 (2024-09)

[0007] In 3GPP, for communications using satellite constellation communications and satellite-based IMS access gateways (IMS AGWs), the configuration of terminal-to-terminal communication (terminal-satellite-terminal) via satellite for voice calls, and the switching of satellite-based IMS AGWs due to satellite movement are being considered.

[0008] However, the currently considered method could not process the information about satellites included in the subscriber information.

[0009] The present invention has been made in view of the above points, and aims to enable voice call settings and IMS AGW switching on a satellite in a satellite-based wireless communication system, taking into account satellite-related information included in subscriber information.

[0010] According to the disclosed technology, a network node is provided having a transmitting unit that transmits a first message requesting subscriber information to a first network node, and a receiving unit that receives a second message from the first network node that includes subscriber information, including first configuration information and second configuration information, wherein the first configuration information indicates that if a third message requesting voice call setup is received from a terminal, including information indicating that the terminal is using satellite access, the third message should be forwarded to the second network node, and the second configuration information indicates that if a fourth message requesting voice call setup is received from the third network node, including information indicating that a terminal on another network side is using satellite access, the fourth message should be forwarded to the second network node.

[0011] According to the disclosed technology, in a satellite-based wireless communication system, it is possible to configure voice call settings and switch IMS AGWs on the satellite, taking into account satellite-related information included in subscriber information.

[0012] This is a diagram illustrating an example of a communication system. This is a diagram illustrating an example of a communication system in a roaming environment. This is a diagram illustrating an example of an IMS data channel network. This is a diagram showing an example of a first sequence diagram in an embodiment of the present invention. This is a diagram showing an example of a second sequence diagram in an embodiment of the present invention. This is a diagram showing an example of a third sequence diagram in an embodiment of the present invention. This is a diagram showing an example of a fourth sequence diagram in an embodiment of the present invention. This is a diagram showing an example of a fifth sequence diagram in an embodiment of the present invention. This is a diagram showing an example of a sixth sequence diagram in an embodiment of the present invention. This is a diagram showing an example of a seventh sequence diagram in an embodiment of the present invention. This is a diagram showing an example of an eighth sequence diagram in an embodiment of the present invention. This is a diagram showing an example of a ninth sequence diagram in an embodiment of the present invention. This is a diagram showing an example of a tenth sequence diagram in an embodiment of the present invention. This is a diagram showing an example of an eleventh sequence diagram in an embodiment of the present invention. This is a diagram showing an example of a twelfth sequence diagram in an embodiment of the present invention. This is a diagram showing an example of a thirteenth sequence diagram in an embodiment of the present invention. This is a diagram showing an example of a fourteenth sequence diagram in an embodiment of the present invention. This is a diagram showing an example of a fifteenth sequence diagram in an embodiment of the present invention. This is a diagram showing an example of a sixteenth sequence diagram in an embodiment of the present invention. This is a diagram showing an example of a seventeenth sequence diagram in an embodiment of the present invention. This is a diagram showing an example of the functional configuration of a base station 10 and a network node 30 in an embodiment of the present invention. This figure shows an example of the functional configuration of terminal 20 in an embodiment of the present invention. This figure shows an example of the hardware configuration of base station 10, terminal 20, and network node 30 in an embodiment of the present invention. This figure shows an example of the configuration of vehicle 2001 in an embodiment of the present invention.

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

[0014] 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, LTE-Advanced and later technologies (e.g., NR), or wireless LAN (Local Area Network), unless otherwise specified.

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

[0016] Figure 1 is a diagram illustrating 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 assumed to correspond to each function, but one network node 30 may implement multiple functions, or multiple network nodes 30 may implement one function. Also, the "connection" described below may be a logical connection or a physical connection.

[0017] The RAN (Radio Access Network) is a network node 30 having wireless access functionality, which may include a base station 10, and is connected to a 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 a PDU (Protocol Data Unit) session point 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, a plurality of network slices are constructed.

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

[0019] The 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. The NEF is a network node 30 that has the function of notifying other NFs (Network Functions) of capabilities and events. The 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. The PCF is a network node 30 that has the function of controlling network policies. The AF is a network node 30 that has the function of controlling application servers. The NRF is a network node 30 that has the function of discovering NF instances that provide services. The UDM is a network node 30 that manages subscriber data and authentication data. The UDM is connected to the UDR (User Data Repository) that holds the said data.

[0020] 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 assigned to each function, but one network node 30 may implement multiple functions, or multiple network nodes 30 may implement one function. Also, the "connection" described below may be a logical connection or a physical connection.

[0021] The RAN is a network node 30 having wireless access functionality and is connected to the UE, AMF, and UPF. The AMF is a network node 30 having 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, having 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.

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

[0023] SMF is a network node 30 that has functions such as session management, IP address allocation and management for UEs, DHCP functionality, ARP proxy, and roaming functionality. NEF is a network node 30 that has the function of notifying other NFs 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 which NSSAIs are allowed, determining which NSSAIs are configured, and determining which AMF set the UE connects to. PCF is a network node 30 that has the function of controlling network policies. 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. SEPP is an opaque proxy that filters control plane messages between PLMNs (Public Land Mobile Networks). In Figure 2, vSEPP is the SEPP in the visited network, and hSEPP is the SEPP in the home network.

[0024] As shown in Figure 2, the UE is in a roaming environment connected to the RAN and AMF in the Visited PLMN. The Visited PLMN and Home PLMN are connected via vSEPP and hSEPP. The UE can communicate with the UDM of the Home PLMN, for example, via the AMF of the Visited PLMN.

[0025] 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, but one network node 30 may implement multiple functions, or multiple network nodes 30 may implement one function. Also, the "connection" described below may be a logical connection or a physical connection. The network node 30 has, for example, the following functions as described in Non-Patent Document 2.

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

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

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

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

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

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

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

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

[0034] (Example) This section describes the procedure for configuring voice calls and switching the IMS AGW on a satellite in a satellite-based wireless communication system.

[0035] In this embodiment, it is assumed that a base station, an ULCL (Uplink Classifier), and multiple low-Earth orbit (LEO) satellites equipped with UPFs form a satellite constellation using an inter-satellite link (ISL). The ULCL has the function of selectively distributing uplink traffic between N9 interfaces.

[0036] Satellite communications operators primarily prepare base stations, ULCLs, UPFs deployed on LEOs, and ground-based intermediary equipment that communicates with satellite devices as dedicated equipment for satellite constellation communications. On the other hand, mobile communications operators primarily prepare network nodes deployed on the ground, such as AMFs and SMFs, as equipment for satellite constellation utilization.

[0037] In this embodiment, an IMS application server for satellite use (referred to as SAT IMS AS) is introduced, and three sessions are configured for terminal-to-terminal communication: between the originating terminal and the originating network SAT IMS AS, between the originating network SAT IMS AS and the receiving network SAT IMS AS, and between the receiving network SAT IMS AS and the receiving terminal.

[0038] The SAT IMS AS determines whether or not terminal-to-terminal communication via satellite is possible. If it determines that it is possible, the ULCL, local UPF, and IMS AGW are configured based on instructions from the SAT IMS AS.

[0039] S-CSCF receives filter criteria from the HSS (Home Subscriber Server) for subscribers authorized to communicate with terminals via satellite, which are the settings for data transfer to the SAT IMS AS. The HSS is a network node that manages subscriber information, etc.

[0040] The details of the processing in this embodiment will be explained below using a sequence diagram. Requests, responses, and notifications sent and received in the following procedures may be referred to as messages (for example, request messages). For details regarding existing specifications concerning the messages sent and received in this sequence diagram, please refer to Non-Patent Document 4-8, etc.

[0041] On the transmitting side, AMF30A, SMF30B, PCF30C, P-CSCF30G, S-CSCF30H, SAT IMS AS30X, HSS30J, remote IMS AGW30FR, and remote UPF(R-PSA1)30D1R, which is the first endpoint of the PDU session (PDU Session Anchor 1, PSA1), are deployed on the ground. Here, UPF may be referred to as the endpoint of the PDU session; for example, UPF(R-PSA1)30D1R may be referred to as UPF30D1R or PSA1. On the other hand, on the satellite to which terminal 20A is connected, base station 10A, ULCL30E, local IMS AGW30FL, and local UPF(L-PSA2)30D2L, which is the second endpoint of the PDU session (PSA2), are deployed.

[0042] In this sequence, after voice communication using satellites is established between terminal 20A, the transmitting terminal, and terminal 20B, the receiving terminal, a handover is performed by switching the satellite to which terminal 20A is connected. At this point, the destination satellite is equipped with base station 10C, ULCL30E3, local IMS AGWFL3, and local UPF(L-PSA3)30D3L3, which is the third termination point (PSA3) of the PDU session.

[0043] On the receiving end, AMF30A2, SMF30B2, PCF30C2, P-CSCF30G2, S-CSCF30H2, SAT IMS AS30X2, HSS30J2, remote IMS AGW30FR2, and remote UPF(R-PSA4)30D4R, which is the fourth termination point (PSA4) of the PDU session, are deployed on the ground. Meanwhile, on the satellite to which terminal 20B is connected, base station 10B, ULCL30E2, local IMS AGW30FL2, and local UPF(L-PSA5)30D5L, which is the fifth termination point (PSA5) of the PDU session, are deployed.

[0044] (Initial Registration of the Originating Terminal in IMS) The initial registration procedure of the originating terminal 20A in the IMS network will be described. FIG. 4 is a diagram showing an example of a first sequence diagram in an embodiment of the present invention. Hereinafter, the processing of each step will be described.

[0045] S101: The terminal 20A transmits a message (Register) requesting the initial registration of the terminal 20A to the P-CSCF 30G. The message includes information (PANI (P-Access-Network-Info)) indicating that satellite access is being used.

[0046] S102: The P-CSCF 30G transmits the message (Register) received in S101 to the S-CSCF 30H.

[0047] S103: The S-CSCF 30H transmits a request message (Nhss_ImsUECM_Registration request) requesting the registration of the terminal 20A to the HSS 30J.

[0048] S104: The HSS 30J transmits a response message (Nhss_ImsUECM_Registration response) to the request message received in S103 to the S-CSCF 30H.

[0049] S105: The S-CSCF 30H transmits a request message (Nhss_ImsSDM_Get request) requesting the acquisition of the subscriber information of the terminal 20A to the HSS 30J.

[0050] S106: The HSS 30J confirms that the subscriber information of the terminal 20A includes setting information (filter criteria) related to packet transfer, which is included only in the subscriber information of a specific subscriber that is included in the subscriber information of the terminal 20A. The setting information includes the following first setting information, second setting information, and third setting information.

[0051] The first setting information indicates that when the initial registration request message (Register) including information (PANI) indicating that the terminal 20A is using satellite access is received from the terminal 20A, the initial registration request message is transferred to the SAT IMS AS 30X.

[0052] The second configuration information indicates that when terminal 20A receives a voice call setup request message (SIP INVITE) from terminal 20A that includes information (PANI) indicating that terminal 20A is using satellite access, the SAT IMS AS30X will forward the voice call setup request message.

[0053] The third configuration information indicates that when I-CSCF30I receives a voice call setup request message (SIP INVITE) that includes information (P-Satellite-Info (PSI)) indicating that terminal 20B on the other network side is using satellite access, the SAT IMS AS30X will forward the voice call setup request message.

[0054] S107: HSS30J sends a response message (Nhss_ImsSDM_Get response) to S-CSCF30H for the request message received in S105. The response message includes subscriber information, including configuration information (filter criteria). For example, the response message is written as Nhss_ImsSDM_Get response (ImsProfileData (imsServiceProfiles (imsServiceProfile (ifcs(ifcList(ifc(trigger(conditionType(DNF), sptList (spt (sipMethod(INVITE), sipHeader(header(PANI), content(access-type=3GPP-NR-SAT)), spt (sipMethod (Register), regType(INITIAL_REGISTRATION))))), appServer(SAT IMS AS)))))))).

[0055] S108: S-CSCF30H stores the configuration information received in S107 in its own device and sets the configuration information (first configuration information, second configuration information, and third configuration information).

[0056] S109: Based on the configuration information (first configuration information) set in S108, S-CSCF30H decides to forward the message (Register) received in S102 to SAT IMS AS30X.

[0057] S110: S-CSCF30H forwards the message (Register) received in S102 to SAT IMS AS30X.

[0058] S111: The SAT IMS AS30X terminates the message received in S110 within its own device. The SAT IMS AS30X also stores the terminal context of terminal 20A, including the IP address of terminal 20A, within its own device.

[0059] S112: SAT IMS AS30X sends a response message (SIP 200 OK) to S-CSCF30H for the message received in S110.

[0060] S113: S-CSCF30H sends the response message (SIP 200 OK) received in S112 to P-CSCF30G.

[0061] S114: P-CSCF30G sends the response message (SIP 200 OK) received in S113 to terminal 20A.

[0062] (Initial Registration of Incoming Terminal in IMS) The initial registration procedure for the incoming terminal 20B in the IMS network is described below. Figure 5 is a diagram showing an example of a second sequence diagram in an embodiment of the present invention. The processing of each step is described below.

[0063] S201: Terminal 20B sends a message (Register) to P-CSCF30G2 requesting initial registration of terminal 20B. This message includes information (PANI (P-Access-Network-Info)) indicating that satellite access is being used.

[0064] S202: P-CSCF30G2 sends the message (Register) received in S201 to S-CSCF30H2.

[0065] S203: S-CSCF30H2 sends a request message (Nhss_ImsUECM_Registration request) to HSS30J2 requesting registration of terminal 20B.

[0066] S204: HSS30J2 sends a response message (Nhss_ImsUECM_Registration response) to S-CSCF30H2 for the request message received in S203.

[0067] S205: S-CSCF30H2 sends a request message (Nhss_ImsSDM_Get request) to HSS30J2 requesting to obtain subscriber information for terminal 20B.

[0068] S206: HSS30J2 confirms that the subscriber information of terminal 20B includes packet forwarding configuration information (filter criteria) that is included only in the subscriber information of a specific subscriber. This configuration information includes the first configuration information, the second configuration information, and the third configuration information shown below.

[0069] The first configuration information indicates that when terminal 20B receives an initial registration request message (Register) from terminal 20B, which includes information (PANI) indicating that terminal 20B is using satellite access, the SAT IMS AS30X2 will forward the initial registration request message.

[0070] The second configuration information indicates that when terminal 20B receives a voice call setup request message (SIP INVITE) from terminal 20B, which includes information (PANI) indicating that terminal 20B is using satellite access, the SAT IMS AS30X2 will forward the voice call setup request message.

[0071] The third configuration information indicates that when I-CSCF30I receives a voice call setup request message (SIP INVITE) containing information (P-Satellite-Info (PSI)) indicating that terminal 20A on the other network side is using satellite access, the SAT IMS AS30X2 will forward the voice call setup request message.

[0072] S207: HSS30J2 sends a response message (Nhss_ImsSDM_Get response) to S-CSCF30H2 for the request message received in S205. This response message includes subscriber information, including configuration information (filter criteria). For example, this response message is written as Nhss_ImsSDM_Get response (ImsProfileData (imsServiceProfiles (imsServiceProfile (ifcs(ifcList(ifc(trigger(conditionType(DNF), sptList (spt (sipMethod(INVITE), sipHeader(header(PANI), content(access-type=3GPP-NR-SAT)), spt (sipMethod (Register), regType(INITIAL_REGISTRATION))))), appServer(SAT IMS AS)))))))).

[0073] S208: S-CSCF30H2 stores the configuration information received in S207 in its own device and sets the configuration information (first configuration information, second configuration information, and third configuration information).

[0074] S209: Based on the configuration information (first configuration information) set in S208, S-CSCF30H2 decides to forward the message (Register) received in S202 to SAT IMS AS30X2.

[0075] S210: S-CSCF30H2 forwards the message (Register) received in S202 to SAT IMS AS30X2.

[0076] S211: SAT IMS AS30X2 terminates the message received in S210 within its own device. SAT IMS AS30X2 also stores the terminal context of terminal 20A, including the IP address of terminal 20B, within its own device.

[0077] S212: SAT IMS AS30X2 sends a response message (SIP 200 OK) to S-CSCF30H2 for the message received in S210.

[0078] S213: S-CSCF30H2 sends the response message (SIP 200 OK) received in S212 to P-CSCF30G2.

[0079] S214: P-CSCF30G2 sends the response message (SIP 200 OK) received in S213 to terminal 20B.

[0080] (IMS Voice Call) The procedure for making a voice call via the IMS AGW on the satellite will be described. Figure 6 is a diagram showing an example of a third sequence diagram in an embodiment of the present invention. The processing of each step will be described below.

[0081] S250: Terminal 20A sends a message (SIP INVITE) to P-CSCF30G requesting an IMS voice call. The message includes information in the PANI indicating that the connection is via satellite (access-type=3GPP-NR-SAT), MCC, MNC, TAC, and NR cell ID, and the SDP offer includes the IP address of the originating terminal 20A's endpoint. For example, the message is written as SIP INVITE (PANI(access-type=3GPP-NR-SAT, utran-cell-id-3gpp=MCC+MNC+TAC+NR cell ID), SDP offer(c= the originating UE IP address)).

[0082] S251: P-CSCF30G sends a request message (H.248 ADD request) to IMS AGW30FR requesting settings related to (additional) control of voice communication.

[0083] S252: The IMS AGW30FR acquires and sets the resources of the termination point on its own device for data transmission with the receiving end.

[0084] S253: IMS AGW30FR sends a response message (H.248 ADD response) to P-CSCF30G for the request message received in S252.

[0085] S254: P-CSCF30G sends a message (SIP INVITE) to S-CSCF30H requesting an IMS voice call. The message includes information in the PANI indicating that the connection is via satellite (access-type=3GPP-NR-SAT), MCC, MNC, TAC, and NR cell ID, and the SDP offer includes the IP address of the originating ground IMS AGW30FR's endpoint. For example, the message is written as SIP INVITE (PANI(access-type=3GPP-NR-SAT, utran-cell-id-3gpp=MCC+MNC+TAC+NR cell ID), SDP offer(c= the originating ground IMS AGW IP address)).

[0086] S255: Based on the configuration information (second configuration information) set in S108 in Figure 4, S-CSCF30H decides to forward the message (SIP INVITE) received in S254 to SAT IMS AS30X.

[0087] S256: S-CSCF30H forwards the message (SIP INVITE) received in S254 to SAT IMS AS30X. SAT IMS AS30X terminates the message.

[0088] S257: SAT IMS AS30X discovers PCF30C based on the IP address of terminal 20A. SAT IMS AS30X may use BSF (Binding Support Function) in this discovery.

[0089] S258: SAT IMS AS30X sends a request message (Npcf_PolicyAuthorization_Create request) to PCF30C requesting information about the satellite. For example, the request message is written as Npcf_PolicyAuthorization_Create request (AppSessionContext (ascReqData (evSubsc (events (event=ANI_REPORT, notifMethod=ONE_TIME), reqAnis(SATELLITE_INFO))))).

[0090] S259: PCF30C sends a response message (Npcf_PolicyAuthorization_Create response) to SAT IMS AS30X for the request message received in S258.

[0091] S260: PCF30C sends a request message (Npcf_SMPolicyControl_UpdateNotify request) to SMF30B requesting information about the satellite. For example, this message is written as Npcf_SMPolicyControl_UpdateNotify request (SmPolicyNotification(smPolicyDecision (lastReqRuleData(reqData(SATELLITE_INFO)),policyCtrlReqTriggers(AN_INFO)))).

[0092] S261: SMF30B sends a response message (Npcf_SMPolicyControl_UpdateNotify response) to PCF30C for the request message received in S260. The request message includes information about the satellite (satellite constellation identifier and satellite identifier) ​​and is written as, for example, Npcf_SMPolicyControl_UpdateNotify response(UeCampingRep(satelliteInfo (satellite constellation id, satellite id))).

[0093] S262: PCF30C sends a request message (Npcf_PolicyAuthorization_Notify request) to SAT IMS AS30X to notify it of information about the satellite. This request message includes information about the satellite (satellite constellation identifier and satellite identifier) ​​and is written as, for example, Npcf_PolicyAuthorization_Notify request (EventsNotification (evNotifs (event= ANI_REPORT), satelliteInfo(satellite constellation id, satellite id))).

[0094] S263: SAT IMS AS30X sends a response message (Npcf_PolicyAuthorization_Notify response) to PCF30C for the request message received in S262.

[0095] S264: SAT IMS AS30X sends a request message (Npcf_PolicyAuthorization_Update request) to PCF30C requesting update information about the satellite. This request message includes information requesting notification of the information when the satellite information is updated, and is written as, for example, Npcf_PolicyAuthorization_Update request(AppSessionContext(ascReqData(evSubsc(events(event=ANI_REPORT,notifMethod =EVENT_DETECTION),reqAnis(SATELLITE_INFO))))).

[0096] S265: PCF30C sends a response message (Npcf_PolicyAuthorization_Update response) to SAT IMS AS30X for the request message received in S264.

[0097] S266: PCF30C sends a request message (Npcf_SMPolicyControl_UpdateNotify request) to SMF30B requesting the transmission of update information when satellite information is updated. For example, this message is written as Npcf_SMPolicyControl_UpdateNotify request (SmPolicyNotification (smPolicyDecision(lastReqRuleData(reqData(SATELLITE_INFO_CH)),policyCtrlReqTriggers(AN_INFO_CH)))).

[0098] S267: SMF30B sends a response message (Npcf_SMPolicyControl_UpdateNotify response) to PCF30C for the request message received in S266.

[0099] S268: SAT IMS AS30X decides to behave as a B2B UA (Back to Back User Agent) in SIP.

[0100] S269: SAT IMS AS30X sends a message (SIP INVITE) to S-CSCF30H requesting an IMS voice call. This message is destined for another network and includes information (PSI (P-Satellite-Info)) indicating that terminal 20A is using satellite access. The message also includes the originating network's satellite constellation identifier and satellite identifier in the PSI header field, and the originating ground IMS AGW30FR's termination IP address in the negotiation offer (SDP offer). For example, this message is written as SIP INVITE (PSI(satellite constellation id, satellite-id), SDP offer (c= the originating ground IMS AGW IP address)).

[0101] S270: S-CSCF30H sends the message (SIP INVITE) received in S269 to I-CSCF30I.

[0102] The process following S270 will now be described. Figure 7 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.

[0103] S280: I-CSCF30I sends a request message (Nhss_ImsUECM_Authorize request) to HSS30J2 regarding the discovery of the S-CSCF that accommodates the incoming terminal.

[0104] S281: HSS30J2 sends a response message (Nhss_ImsUECM_Authorize response) to I-CSCF30I for the request message received in S280.

[0105] S282: I-CSCF30I sends the message (SIP INVITE) received in S270 in Figure 6 to S-CSCF30H2.

[0106] S283: Based on the configuration information (third configuration information) set in S208 in Figure 5, S-CSCF30H2 decides to forward the message (SIP INVITE) received in S282 to SAT IMS AS30X2.

[0107] S284: S-CSCF30H2 forwards the message (SIP INVITE) received in S282 to SAT IMS AS30X2. SAT IMS AS30X2 terminates the message.

[0108] S285: SAT IMS AS30X2 determines that it is possible to set an optimal inter-satellite route based on information from the satellite accommodating the terminal on the other network side and information from the satellite accommodating the terminal on its own network side. SAT IMS AS30X2 also discovers PCF30C2 based on the IP address of terminal 20B. SAT IMS AS30X2 may use BSF (Binding Support Function) in this discovery.

[0109] S286: SAT IMS AS30X2 sends a request message (Npcf_PolicyAuthorization_Create request) to PCF30C2 requesting information about the satellite. For example, the request message is written as Npcf_PolicyAuthorization_Create request (AppSessionContext (ascReqData (evSubsc(events(event=ANI_REPORT,notifMethod=ONE_TIME),reqAnis(SATELLITE_INFO))))).

[0110] S287: PCF30C2 sends a response message (Npcf_PolicyAuthorization_Create response) to SAT IMS AS30X2 for the request message received in S286.

[0111] S288: PCF30C2 sends a request message (Npcf_SMPolicyControl_UpdateNotify request) to SMF30B2 requesting information about the satellite. For example, the message is written as Npcf_SMPolicyControl_UpdateNotify request (SmPolicyNotification(smPolicyDecision (lastReqRuleData(reqData(SATELLITE_INFO)),policyCtrlReqTriggers(AN_INFO)))).

[0112] S289: SMF30B2 sends a response message (Npcf_SMPolicyControl_UpdateNotify response) to PCF30C2 for the request message received in S288. The request message includes information about the satellite (satellite constellation identifier and satellite identifier) ​​and is written as, for example, Npcf_SMPolicyControl_UpdateNotify response(UeCampingRep(satelliteInfo (satellite constellation id, satellite id))).

[0113] S290: PCF30C2 sends a request message (Npcf_PolicyAuthorization_Notify request) to SAT IMS AS30X2 to notify it of satellite information. This request message includes satellite information (satellite constellation identifier and satellite identifier) ​​and is written as, for example, Npcf_PolicyAuthorization_Notify request (EventsNotification (evNotifs (event= ANI_REPORT), satelliteInfo(satellite constellation id, satellite id))).

[0114] S291: SAT IMS AS30X2 sends a response message (Npcf_PolicyAuthorization_Notify response) to PCF30C2 for the request message received in S290.

[0115] S292: SAT IMS AS30X2 sends a request message() to PCF30C2 requesting update information about the satellite. This request message includes information requesting notification of the information when the satellite information is updated, and is written as, for example, Npcf_PolicyAuthorization_Update request(AppSessionContext(ascReqData(evSubsc(events(event=ANI_REPORT,notifMethod =EVENT_DETECTION),reqAnis(SATELLITE_INFO))))).

[0116] S293: PCF30C2 sends a response message (Npcf_PolicyAuthorization_Update response) to SAT IMS AS30X2 for the request message received in S292.

[0117] S294: PCF30C2 sends a request message (Npcf_SMPolicyControl_UpdateNotify request) to SMF30B2 requesting the transmission of update information when satellite information is updated. For example, this message is written as Npcf_SMPolicyControl_UpdateNotify request (SmPolicyNotification (smPolicyDecision(lastReqRuleData(reqData(SATELLITE_INFO_CH)),policyCtrlReqTriggers(AN_INFO_CH)))).

[0118] S295: SMF30B2 sends a response message (Npcf_SMPolicyControl_UpdateNotify response) to PCF30C2 for the request message received in S294.

[0119] S296: SAT IMS AS30X2 decides to act as a B2B UA (Back to Back User Agent) in SIP.

[0120] S297: SAT IMS AS30X2 verifies that the satellite constellation identifier and satellite identifier are the same for both the originating terminal 20A and the receiving terminal 20B. Based on this verification, SAT IMS AS30X2 decides to configure the system for routing voice media (voice data) on the satellite.

[0121] S298: SAT IMS AS30X2 sends a message to S-CSCFH2 requesting an IMS voice call (SIP INVITE). The message includes information (PSI) indicating that satellite access is being used. The message also includes a satellite constellation identifier and a satellite identifier in the PSI header field, and information (a=satellite-optimal-routing-requested) in the negotiating proposal (SDP offer) requesting the establishment of an optimal inter-satellite route. For example, the message is written as SIP INVITE (PSI(satellite constellation id, satellite-id), SDP offer (c=dummy, a=satellite-optimal-routing-requested)).

[0122] S299: S-CSCFH2 sends the message (SIP INVITE) received in S298 to P-CSCF30G2.

[0123] S300: P-CSCF30G2 decides to set up the optimal inter-satellite route based on the information (a=satellite-optimal-routing-requested) in the message (SIP INVITE) received in S299, which requests the setting up of the optimal inter-satellite route. At this time, P-CSCF30G2 will skip setting up the ground-based IMS AGW30FR2.

[0124] S301: P-CSCF30G2 sends a message (SIP INVITE) to terminal 20B requesting an IMS voice call.

[0125] S302: Terminal 20B sends a message (183 Session Progress) to P-CSCF30G2 indicating that voice communication is being set up. The message includes information in the PANI indicating that the connection is via satellite (access-type=3GPP-NR-SAT), MCC, MNC, TAC, and NR cell identifier (NR cell ID), and the SDP answer includes the IP address of the termination point of the receiving terminal 20B. For example, the message is written as SIP 183 Session Progress (PANI(access-type=3GPP-NR-SAT, utran-cell-id-3gpp=MCC+MNC+TAC+NR cell ID), SDP answer (c= the terminating UE IP address)).

[0126] S303: P-CSCF30G2 will skip configuring ULCL and media QoS flow at this time.

[0127] S304: Based on the negotiated response (SDP answer) in the message (SIP 183 Session Progress) received in S303, P-CSCF30G2 decides to select IMS AGW30FL2 on the satellite and perform the configuration of IMS AGW30FL2.

[0128] S305: P-CSCF30G2 sends a request message (H.248 ADD request) to IMS AGW30FL2 requesting settings related to (additional) control of voice communication.

[0129] S306: The IMS AGW30FL2 acquires and sets the resources of the termination point on its own device side for data transmission with the originating side.

[0130] S307: IMS AGW30FL2 sends a response message (H.248 ADD response) to P-CSCF30G2 for the request message received in S305.

[0131] S308: P-CSCF30G2 sends a message (SIP 183 Session Progress) to S-CSCF30H2 indicating that voice communication is being set up. The message includes information in the PANI indicating that the connection is via satellite (access-type=3GPP-NR-SAT), MCC, MNC, TAC, and NR cell ID, and the SDP answer includes the IP address of the termination point of IMS AGW30FL2 on the receiving satellite. For example, the message is written as SIP 183 Session Progress (PANI(access-type=3GPP-NR-SAT, utran-cell-id-3gpp=MCC+MNC+TAC+NR cell ID), SDP answer (c= the terminating satellite IMS AGW IP address)).

[0132] S309: S-CSCF30H2 sends the message received in S308 (SIP 183 Session Progress) to SAT IMS AS30X2.

[0133] S310: SAT IMS AS30X2 sends a message (SIP 183 Session Progress) to S-CSCF30H2 indicating that voice communication is being configured. This message is destined for another network and includes information (PSI (P-Satellite-Info)) indicating that terminal 20B is using satellite access. The message also includes a satellite constellation identifier and a satellite identifier in the PSI header field, and the negotiation response (SDP answer) includes the IP address of the termination point of IMS AGW30FL2 on the receiving satellite. For example, this message is written as SIP 183 Session Progress (PSI (satellite constellation id, satellite-id), SDP answer (c= the terminating satellite IMS AGW IP address)).

[0134] S311: S-CSCF30H2 sends the message received in S310 (SIP 183 Session Progress) to I-CSCF30I.

[0135] The process following S311 will now be described. Figure 8 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.

[0136] S351: I-CSCF30I sends the message received in S311 in Figure 7 (SIP 183 Session Progress) to S-CSCF30H.

[0137] S352: S-CSCF30H sends the message received in S351 (SIP 183 Session Progress) to SAT IMS AS30X. SAT IMS AS30X terminates the message.

[0138] S353: SAT IMS AS30X determines that it is possible to set an optimal inter-satellite route based on information from satellites accommodating terminals on the other network side and information from satellites accommodating terminals on its own network side.

[0139] S354: SAT IMS AS30X sends a message (SIP 183 Session Progress) to S-CSCF30H indicating that voice communication is being set up. The message includes information (PSI) indicating that satellite access is being used. The message also includes a satellite constellation identifier and a satellite identifier in the PSI header field, and in the negotiation response (SDP answer) information requesting the establishment of the IP address of the termination point of IMS AGW30FL2 on the receiving satellite and the setting of the optimal inter-satellite route (a=satellite-optimal-routing-requested). For example, the message is written as SIP 183 Session Progress (PSI(satellite constellation id, satellite-id), SDP answer (c= the terminating satellite IMS AGW IP address, a=satellite-optimal-routing-requested)).

[0140] S355: S-CSCF30H sends the message received in S354 (SIP 183 Session Progress) to P-CSCF30G.

[0141] S356: For the P-CSCF30G, skip the ULCL and media QoS flow configuration for now.

[0142] S357: P-CSCF30G decides to remove the ground-based IMS AGW30FR from the communication path.

[0143] S358: P-CSCF30G sends a request message (H.248 SUBTRACT request) to IMS AGW30FR requesting the setting related to the deletion of voice communication control.

[0144] S359: IMS AGW30FR deletes the settings executed in S252 in Figure 6.

[0145] S360: IMS AGW30FR sends a response message (H.248 SUBTRACT response) to P-CSCF30G for the request message received in S358.

[0146] S361: Based on the negotiated response (SDP answer) in the message (SIP 183 Session Progress) received in S355, P-CSCF30G decides to select IMS AGW30FL on the satellite and perform the configuration of IMS AGW30FL.

[0147] S362: P-CSCF30G sends a request message (H.248 ADD request) to IMS AGW30FL requesting settings related to (additional) control of voice communication.

[0148] S363: The IMS AGW30FL acquires and sets the resources of the termination point on its own device side for data transmission with the originating side.

[0149] S364: IMS AGW30FL sends a response message (H.248 ADD response) to P-CSCF30G for the request message received in S362.

[0150] S365: P-CSCF30G decides to perform ULCL and media QoS flow configuration.

[0151] S366: P-CSCF30G sends a request message (Npcf_PolicyAuthorization_Create request) to PCF30C, requesting SMF30B to set ULCL and UPF.

[0152] S367: PCF30C sends a response message (Npcf_PolicyAuthorization_Create response) to P-CSCF30G for the request message received in S366.

[0153] S368: PCF30C sends a request message (Npcf_SMPolicyControl_UpdateNotify request) to SMF30B requesting it to set ULCL and UPF.

[0154] S369: SMF30B sends a response message (Npcf_SMPolicyControl_UpdateNotify response) to PCF30C for the request message received in S368.

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

[0156] S371: SMF30B selects the ULCL and UPF to set based on the satellite identifier.

[0157] S372: SMF30B sends a request message (PFCP Session Establishment request) to UPF30D2L for the establishment of a user data transfer path.

[0158] S373: UPF30D2L sends a response message (PFCP Session Establishment response) to SMF30B for the request message received in S372.

[0159] S374: SMF30B sends a request message (PFCP Session Establishment request) to ULCL30E for the establishment of a user data transfer path.

[0160] S375: ULCL30E sends a response message (PFCP Session Establishment response) to SMF30B for the request message received in S374.

[0161] S376: SMF30B sends a request message (PFCP Session Modification request) to UPF30D1R for updating the user data transfer path.

[0162] S377: UPF30D1R sends a response message (PFCP Session Modification response) to SMF30B for the request message received in S376.

[0163] S378: SMF30B sends a request message (PFCP Session Modification request) to UPF30D2L for updating the user data transfer path.

[0164] S379: UPF30D2L sends a response message (PFCP Session Modification response) to SMF30B for the request message received in S378.

[0165] S380: SMF30B sends a request message (Namf_Communication_N1N2MessageTransfer request) to AMF30A for updating the PDU session resource settings. For example, this message is written as Namf_Communication_N1N2MessageTransfer request (N1N2MessageTransferReqData(n1MessageContainer(n1MessageContent(PDU Session Modification Command)), n2InfoContainer(smInfo(n2InfoContent(PDU Session Resource Modify Request Transfer))))).

[0166] S381: AMF30A sends a response message (Namf_Communication_N1N2MessageTransfer response) to SMF30B for the request message received in S380.

[0167] S382: AMF30A sends a request message to base station 10A for updating the PDU session resource settings (PDU Session Resource Modify Request). For example, this message is written as PDU Session Resource Modify Request (NAS-PDU(DL NAS transport(Payload container type(N1 SM information), Payload container(PDU Session Modification Command))), PDU Session Resource Modify Request Transfer).

[0168] S383: Base station 10A sends a message to terminal 20A regarding RRC configuration (RRCReconfiguration), which includes information indicating acceptance of the instruction to establish a PDU session update. For example, the message is written as RRCReconfiguration(dedicatedNAS-Message(DL NAS transport(Payload container type(N1 SM information), Payload container(PDU Session Modification Command)))).

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

[0170] S385: Base station 10A sends a response message (PDU Session Resource Modify response) to AMF30A for the request message received in S382.

[0171] S386: AMF30A sends a request message (Nsmf_PDUSession_UpdateSMContext request) to SMF30B requesting a context update for the PDU session. For example, this request message is written as Nsmf_PDUSession_UpdateSMContext request (SmContextUpdateData(n2SmInfo(PDU Session Resource ModifySetup Response Transfer))).

[0172] S387: SMF30B sends a response message (Nsmf_PDUSession_UpdateSMContext response) to AMF30A for the request message received in S386.

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

[0174] S389: Base station 10A sends a message to AMF30A notifying it that the PDU session update is complete. For example, this message is written as Uplink NAS Transport(NAS-PDU(UL NAS transport(Payload container type(N1 SM information), Payload container(PDU Session Modification Complete)))).

[0175] S390: AMF30A sends a request message (Nsmf_PDUSession_UpdateSMContext request) to SMF30B requesting a context update for the PDU session. For example, this request message is written as Nsmf_PDUSession_UpdateSMContext request (SmContextUpdateData(n2SmInfo(PDU Session Resource ModifySetup Response Transfer))).

[0176] S391: SMF30B sends a response message (Nsmf_PDUSession_UpdateSMContext response) to AMF30A for the request message received in S390.

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

[0178] S401: P-CSCF30G sends a message (SIP 183 Session Progress) to terminal 20A indicating that voice communication is being set up. This message includes the IP address of the termination point of the originating satellite IMS AGW30FL in the negotiation response (SDP answer), and is written as, for example, SIP 183 Session Progress (SDP answer (c= the originating satellite IMS AGW IP address)).

[0179] S402: Terminal 20A sends a PRACK (Provisional response acknowledgement) / UPDATE to P-CSCF30G as a response to the message received in S401. For example, the message is written as PRACK / UPDATE (PANI(access-type=3GPP-NR-SAT, utran-cell-id-3gpp=MCC+MNC+TAC+NR cell ID), SDP offer(c= the originating UE IP address)).

[0180] S403: P-CSCF30G sends a request message (H.248 MOD request) to IMS AGW30FL requesting settings related to the control (or modification) of voice communication.

[0181] S404: The IMS AGW30FL sets the termination point on its own side for data transmission with the originating side.

[0182] S405: IMS AGW30FL sends a response message (H.248 MOD response) to P-CSCF30G for the request message received in S403.

[0183] S406: P-CSCF30G sends a request message (H.248 ADD request) to IMS AGW30FL requesting settings related to (additional) control of voice communication.

[0184] S407: The IMS AGW30FL sets the endpoint of the receiving device for data transmission with the receiving device and acquires resources for the endpoint of its own device.

[0185] S408: IMS AGW30FL sends a response message (H.248 ADD response) to P-CSCF30G for the request message received in S406.

[0186] S409: P-CSCF30G sends PRACK / UPDATE to S-CSCF30H. For example, this message is written as PRACK / UPDATE (PANI(access-type=3GPP-NR-SAT, utran-cell-id-3gpp=MCC+MNC+TAC+NR cell ID), SDP offer (c= the originating satellite IMS AGW IP address)).

[0187] S410: S-CSCF30H transmits the PRACK / UPDATE received in S406 to SAT IMS AS30X.

[0188] S411: SAT IMS AS30X sends PRACK / UPDATE to S-CSCF30H. For example, this message is written as PRACK / UPDATE (SDP offer (c= the originating satellite IMS AGW IP address)).

[0189] S412: S-CSCF30H transmits the PRACK / UPDATE received in S411 to I-CSCF30I.

[0190] S413: I-CSCF30I transmits the PRACK / UPDATE received in S412 to S-CSCF30H2.

[0191] S414: S-CSCF30H2 sends the PRACK / UPDATE received in S413 to SAT IMS AS30X2.

[0192] S415: SAT IMS AS30X2 sends the PRACK / UPDATE received in S414 to S-CSCF30H2.

[0193] S416: S-CSCF30H2 transmits the PRACK / UPDATE received in S415 to P-CSCF30G2.

[0194] The process following S416 will now be described. Figure 11 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.

[0195] S421: P-CSCF30G2 sends a request message (H.248 MOD request) to IMS AGW30FL2 requesting settings related to the control (modification) of voice communication.

[0196] S422: IMS AGW30FL2 sets the originating side termination point for data transmission with the originating side.

[0197] S423: IMS AGW30FL2 sends a response message (H.248 MOD response) to P-CSCF30G2 for the request message received in S421.

[0198] S424: P-CSCF30G2 sends a request message (H.248 ADD request) to IMS AGW30FL2 requesting settings related to (additional) control of voice communication.

[0199] S425: The IMS AGW30FL2 sets the endpoint of the receiving device for data transmission with the receiving device and acquires resources for the endpoint of its own device.

[0200] S426: IMS AGW30FL2 sends a response message (H.248 ADD response) to P-CSCF30G2 for the request message received in S424.

[0201] S427: P-CSCF30G2 decides to perform ULCL and media QoS flow configuration.

[0202] S428: P-CSCF30G2 sends a request message (Npcf_PolicyAuthorization_Create request) to PCF30C2, requesting SMF30B to set ULCL and UPF.

[0203] S429: PCF30C2 sends a response message (Npcf_PolicyAuthorization_Create response) to P-CSCF30G2 for the request message received in S428.

[0204] S430: PCF30C2 sends a request message (Npcf_SMPolicyControl_UpdateNotify request) to SMF30B2 requesting it to set ULCL and UPF.

[0205] S431: SMF30B2 sends a response message (Npcf_SMPolicyControl_UpdateNotify response) to PCF30C2 for the request message received in S430.

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

[0207] S441: SMF30B2 selects the ULCL and UPF to set based on the satellite identifier.

[0208] S442: SMF30B2 sends a request message (PFCP Session Establishment request) to UPF30D5L for the establishment of a user data transfer path.

[0209] S443: UPF30D5L sends a response message (PFCP Session Establishment response) to SMF30B2 for the request message received in S442.

[0210] S444: SMF30B2 sends a request message (PFCP Session Establishment request) to ULCL30E2 for the establishment of a user data transfer path.

[0211] S445: ULCL30E2 sends a response message (PFCP Session Establishment response) to SMF30B2 for the request message received in S444.

[0212] S446: SMF30B2 sends a request message (PFCP Session Modification request) to UPF30D4R for updating the user data transfer path.

[0213] S447: UPF30D4R sends a response message (PFCP Session Modification response) to SMF30B2 for the request message received in S446.

[0214] S448: SMF30B2 sends a request message (PFCP Session Modification request) to UPF30D5L for updating the user data transfer path.

[0215] S449: UPF30D5L sends a response message (PFCP Session Modification response) to SMF30B2 for the request message received in S448.

[0216] S450: SMF30B2 sends a request message (Namf_Communication_N1N2MessageTransfer request) to AMF30A2 for updating the PDU session resource settings. For example, this message is written as Namf_Communication_N1N2MessageTransfer request (N1N2MessageTransferReqData(n1MessageContainer(n1MessageContent(PDU Session Modification Command)), n2InfoContainer(smInfo(n2InfoContent(PDU Session Resource Modify Request Transfer))))).

[0217] S451: AMF30A2 sends a response message (Namf_Communication_N1N2MessageTransfer response) to SMF30B2 for the request message received in S450.

[0218] S452: AMF30A2 sends a request message to base station 10B for updating the PDU session resource settings (PDU Session Resource Modify Request). For example, this message is written as PDU Session Resource Modify Request (NAS-PDU(DL NAS transport(Payload container type(N1 SM information), Payload container(PDU Session Modification Command))), PDU Session Resource Modify Request Transfer).

[0219] S453: Base station 10B sends a message to terminal 20B regarding RRC configuration (RRCReconfiguration), which includes information indicating acceptance of the instruction to establish a PDU session update. For example, the message is written as RRCReconfiguration(dedicatedNAS-Message(DL NAS transport(Payload container type(N1 SM information), Payload container(PDU Session Modification Command)))).

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

[0221] S455: Base station 10B sends a response message (PDU Session Resource Modify response) to AMF30A2 for the request message received in S452.

[0222] S456: AMF30A2 sends a request message (Nsmf_PDUSession_UpdateSMContext request) to SMF30B2 requesting a context update for the PDU session. For example, this request message is written as Nsmf_PDUSession_UpdateSMContext request (SmContextUpdateData(n2SmInfo(PDU Session Resource ModifySetup Response Transfer))).

[0223] S457: SMF30B2 sends a response message (Nsmf_PDUSession_UpdateSMContext response) to AMF30A2 for the request message received in S456.

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

[0225] S459: Base station 10B sends a message to AMF30A2 notifying it that the PDU session update is complete. For example, this message is written as Uplink NAS Transport(NAS-PDU(UL NAS transport(Payload container type(N1 SM information), Payload container(PDU Session Modification Complete)))).

[0226] S460: AMF30A2 sends a request message (Nsmf_PDUSession_UpdateSMContext request) to SMF30B2 requesting a context update for the PDU session. For example, this request message is written as Nsmf_PDUSession_UpdateSMContext request (SmContextUpdateData(n2SmInfo(PDU Session Resource ModifySetup Response Transfer))).

[0227] S461: SMF30B2 sends a response message (Nsmf_PDUSession_UpdateSMContext response) to AMF30A2 for the request message received in S460.

[0228] S462: P-CSCF30G2 transmits the PRACK / UPDATE received in S416 of Figure 10 to terminal 20B.

[0229] The process following S462 will now be described. Figure 13 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.

[0230] S471: Terminal 20B sends 200 OK(PRACK / UPDATE) to P-CSCF30G2 as a response to the PRACK / UPDATE received in S462 in Figure 10.

[0231] S472: P-CSCF30G2 transmits the PRACK / UPDATE received in S471 to S-CSCF30H2.

[0232] S473: S-CSCF30H2 transmits the PRACK / UPDATE received in S472 to SAT IMS AS30X2.

[0233] S474: SAT IMS AS30X2 transmits the PRACK / UPDATE received in S473 to S-CSCF30H2.

[0234] S475: S-CSCF30H2 transmits the PRACK / UPDATE received in S474 to I-CSCF30I.

[0235] S476: I-CSCF30I transmits the PRACK / UPDATE received in S475 to S-CSCF30H.

[0236] S477: S-CSCF30H transmits the PRACK / UPDATE received in S476 to SAT IMS AS30X.

[0237] S478: SAT IMS AS30X transmits the PRACK / UPDATE received in S477 to S-CSCF30H.

[0238] S479: S-CSCF30H transmits the PRACK / UPDATE received in S478 to P-CSCF30G.

[0239] S480: P-CSCF30G sends the PRACK / UPDATE received in S479 to terminal 20A.

[0240] S481: Terminal 20A sends an UPDATE message to P-CSCF30G, which is a message to update the session.

[0241] S482: P-CSCF30G transmits the UPDATE received in S481 to S-CSCF30H.

[0242] S483: S-CSCF30H transmits the UPDATE received in S482 to SAT IMS AS30X.

[0243] S484: SAT IMS AS30X transmits the UPDATE received in S483 to S-CSCF30H.

[0244] S485: S-CSCF30H transmits the UPDATE received in S484 to I-CSCF30I.

[0245] S486: I-CSCF30I transmits the UPDATE received in S485 to S-CSCF30H2.

[0246] S487: S-CSCF30H2 transmits the UPDATE received in S486 to SAT IMS AS30X2.

[0247] S488: SAT IMS AS30X2 transmits the UPDATE received in S487 to S-CSCF30H2.

[0248] S489: S-CSCF30H2 transmits the UPDATE received in S488 to P-CSCF30G2.

[0249] S490: P-CSCF30G2 sends the UPDATE received in S489 to terminal 20B.

[0250] S491: Terminal 20B sends 200 OK(UPDATE) to P-CSCF30G2 as a response to the UPDATE received in S490.

[0251] S492: P-CSCF30G2 sends the 200 OK (UPDATE) received in S491 to S-CSCF30H2.

[0252] S493: S-CSCF30H2 sends the 200 OK (UPDATE) received in S492 to SAT IMS AS30X2.

[0253] S494: SAT IMS AS30X2 sends the 200 OK (UPDATE) received in S493 to S-CSCF30H2.

[0254] S495: S-CSCF30H2 sends the 200 OK (UPDATE) received in S494 to I-CSCF30I.

[0255] S496: I-CSCF30I sends the 200 OK (UPDATE) received in S495 to S-CSCF30H.

[0256] S497: S-CSCF30H sends the 200 OK (UPDATE) received in S496 to SAT IMS AS30X.

[0257] S498: SAT IMS AS30X sends the 200 OK (UPDATE) received in S497 to S-CSCF30H.

[0258] S499: S-CSCF30H sends the 200 OK (UPDATE) received in S498 to P-CSCF30G.

[0259] S500: P-CSCF30G sends the 200 OK (UPDATE) received in S499 to terminal 20A.

[0260] The process following S500 will now be explained. Figure 14 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 explained below.

[0261] S501: Terminal 20B sends SIP 200 OK, a message indicating success, to P-CSCF30G2.

[0262] S502: P-CSCF30G2 sends SIP 200 OK, received by S501, to S-CSCF30H2.

[0263] S503: S-CSCF30H2 sends SIP 200 OK, received by S502, to SAT IMS AS30X2.

[0264] S504: SAT IMS AS30X2 sends SIP 200 OK, received in S503, to S-CSCF30H2.

[0265] S505: S-CSCF30H2 sends SIP 200 OK, received in S504, to I-CSCF30I.

[0266] S506: I-CSCF30I sends the SIP 200 OK received in S505 to S-CSCF30H.

[0267] S507: S-CSCF30H sends SIP 200 OK, received in S506, to SAT IMS AS30X.

[0268] S508: SAT IMS AS30X sends SIP 200 OK, received in S507, to S-CSCF30H.

[0269] S509: S-CSCF30H sends SIP 200 OK, received in S508, to P-CSCF30G.

[0270] S510: P-CSCF30G sends SIP 200 OK, received by S509, to terminal 20A.

[0271] S511: Terminal 20A sends an Ack to P-CSCF30G in response to the SIP 200 OK received at S510.

[0272] S512: P-CSCF30G transmits the Ack received in S511 to S-CSCF30H.

[0273] S513: S-CSCF30H sends the Ack received in S512 to SAT IMS AS30X.

[0274] S514: SAT IMS AS30X sends the Ack received in S513 to S-CSCF30H.

[0275] S515: S-CSCF30H transmits the Ack received in S514 to I-CSCF30I.

[0276] S516: I-CSCF30I transmits the Ack received in S515 to S-CSCF30H2.

[0277] S517: S-CSCF30H2 sends the Ack received in S516 to SAT IMS AS30X2.

[0278] S518: SAT IMS AS30X2 sends the Ack received in S517 to S-CSCF30H2.

[0279] S519: S-CSCF30H2 sends the Ack received in S518 to P-CSCF30G2.

[0280] S520: P-CSCF30G2 sends the Ack received in S519 to terminal 20B.

[0281] S530: The voice call setup is completed between terminal 20A and terminal 20B via the two IMS AGWs (IMS AGW30FL / IMS AGW30FL2) on the satellite.

[0282] (Satellite Transfer) After a voice call is completed via the IMS AGW on the satellite, the procedure for satellite transfer in which the satellite housing the calling terminal 20A switches to another satellite will be described. Figure 15 is a diagram showing an example of the twelfth sequence diagram in an embodiment of the present invention. The sequence diagram in Figure 15 is the Xn handover procedure. The processing of each step will be described below.

[0283] S541: Base station 10A sends a Handover Request to base station 10C.

[0284] S542: Base station 10C sends a Handover Request Acknowledgement to base station 10A, which includes a Handover Command, as a response to the Handover Request received in S541.

[0285] S543: Base station 10A sends a message (RRCReconfiguration) to terminal 20A requesting the execution of settings related to radio resource control (RRC). This message includes a handover command.

[0286] S544: Base station 10A transmits an SN status transfer to base station 10C.

[0287] S545: Terminal 20A sends a message to base station 10C notifying it that the RRC configuration is complete. This message includes a handover confirmation command.

[0288] S546: Base station 10C sends a request message (Path Switch request) to AMF30A requesting a route change due to the base station change.

[0289] S547: Based on the previously recognized correspondence between the transport layer settings and the source base station identifier, and the transport layer settings and base station identifier of the request message received in S546, AMF30A recognizes the satellite constellation identifier and satellite identifier currently accommodating terminal 20A, and recognizes that the satellite with the satellite identifier is accommodating terminal 20A.

[0290] S548: AMF30A sends a request message (Nsmf_PDUSession_UpdateSMContext request) to SMF30B requesting a route switch due to the base station change. This request message includes a satellite constellation identifier and a satellite identifier, and is written as, for example, Nsmf_PDUSession_UpdateSMContext request (SmContextUpdateData (satellite constellation id, satellite id)).

[0291] S549: SMF30B sends a request message (PFCP Session Modification request) to ULCL30E for updating the user data transfer path.

[0292] S550: ULCL30E sends a response message (PFCP Session Modification response) to SMF30B for the request message received in S549.

[0293] S551: SMF30B sends a response message (Nsmf_PDUSession_UpdateSMContext response) to AMF30A for the request message received in S548.

[0294] S552: The AMF30A sends a response message (Path Switch request response) to the base station 10C in response to the request message received in S546.

[0295] S553: ​​Base station 10C sends a message to base station 10A requesting the release of the terminal context (UE Context Release).

[0296] The process following S553 will now be explained. In the subsequent processes, the switching between ULCL and UPF on the satellite is performed. Figure 16 is a diagram showing an example of the 13th sequence diagram in an embodiment of the present invention. The process of each step will be explained below.

[0297] S601: SMF30B recognizes the change in base station 10B and the change in satellite identifier based on the request message received in S548 in Figure 15.

[0298] S602: SMF30B sends a request message (Npcf_SMPolicyControl_Update request) to PCF30C requesting an update of satellite information. This request message includes information about the new satellite to which terminal 20A will be located (satellite constellation identifier and satellite identifier), and is written as, for example, Npcf_SMPolicyControl_Update request (SmPolicyUpdateContextData (satelliteInfo (satellite constellation id, satellite id))).

[0299] S603: PCF30C sends a response message (Npcf_SMPolicyControl_Update response) to SMF30B for the request message received in S602.

[0300] S604: PCF30C sends a request message (Npcf_PolicyAuthorization_Notify request) to SAT IMS AS30X to notify it of information about the satellite. This request message includes information about the new satellite to which terminal 20A will be located (satellite constellation identifier and satellite identifier), and is written as, for example, Npcf_PolicyAuthorization_Notify request (EventsNotification (evNotifs (event= ANI_REPORT), satelliteInfo(satellite constellation id, satellite id))).

[0301] S605: SAT IMS AS30X sends a response message (Npcf_PolicyAuthorization_Notify response) to PCF30C for the request message received in S604.

[0302] S606: SAT IMS AS30X recognizes that the destination satellite belongs to the same satellite constellation as the satellite housing the arrival terminal 20B, that is, after the switch between ULCL and UPF, the satellite constellations of the departure and arrival terminals are the same, and determines that it is possible to set the optimal inter-satellite route.

[0303] S607: SAT IMS AS30X sends a message (SIP re-INVITE) to S-CSCF30H requesting a change in voice call settings. The message includes information (PSI) indicating that the terminal is using satellite access, including information about the satellite to which the terminal will be newly accommodated. The message also includes a negotiation proposal (SDP offer) requesting the establishment of an optimal inter-satellite route for the satellite to which the terminal will be newly accommodated (a=target satellite-optimal-routing-requested). The message also includes the IP address of the termination point of IMS AGW30FL2 on the receiving satellite. For example, the message is written as SIP re-INVITE (PSI(satellite constellation id, satellite-id), SDP offer (c=the terminating satellite IMS AGW IP address, a=target satellite-optimal-routing-requested)).

[0304] Additionally, the SAT IMS AS30X may start a timer to resend the message (SIP re-INVITE).

[0305] S608: S-CSCF30H sends the message received in S607 (SIP re-INVITE) to P-CSCF30G.

[0306] S609: Based on the information (a=target satellite-optimal-routing-requested) contained in the message (SIP re-INVITE) received in S608, which requests the establishment of an optimal inter-satellite route for the satellite that will newly accommodate the terminal, P-CSCF30G decides to select IMS AGW30FL3 on the destination satellite, perform the configuration of IMS AGW30FL3, and establish an optimal inter-satellite route on the destination satellite.

[0307] S610: P-CSCF30G sends a request message (H.248 ADD request) to IMS AGW30FL3 requesting settings related to (additional) control of voice communication.

[0308] S611: The IMS AGW30FL3 acquires and sets the resources of the termination point on its own device side for data transmission with the originating side.

[0309] S612: IMS AGW30FL3 sends a response message (H.248 ADD response) to P-CSCF30G for the request message received in S610.

[0310] S613: P-CSCF30G sends a message (SIP re-INVITE) to terminal 20A requesting a change in voice call settings. This message includes the IP address of the termination point of the originating satellite IMS AGW30FL in the negotiation offer (SDP offer). For example, this message is written as SIP re-INVITE (SDP offer (c= the originating source satellite IMS AGW IP address)).

[0311] S614: Terminal 20A sends a response message (SIP 200 OK) to P-CSCF30G for the message received in S613. This message includes the IP address of terminal 20A's endpoint in the negotiation response (SDP answer), and is written as, for example, SIP 200 OK (SDP answer (c= the originating UE IP address)).

[0312] S615: P-CSCF30G sends a request message (H.248 MOD request) to IMS AGW30FL3 requesting settings related to the control (or modification) of voice communication.

[0313] S616: The IMS AGW30FL3 sets the originating side termination point for data transmission with the originating side.

[0314] S617: IMS AGW30FL3 sends a response message (H.248 MOD response) to P-CSCF30G for the request message received in S615.

[0315] S618: P-CSCF30G sends a request message (H.248 ADD request) to IMS AGW30FL3 requesting settings related to (additional) control of voice communication.

[0316] S619: The IMS AGW30FL3 sets the destination termination point for data transmission with the destination device and acquires resources for the termination point on its own device side.

[0317] S620: IMS AGW30FL3 sends a response message (H.248 ADD response) to P-CSCF30G for the request message received in S618.

[0318] S621: P-CSCF30G sends a response message (SIP 200 OK) to S-CSCF30H. This message includes the negotiated response (SDP answer) of the termination point of IMS AGW30FL3 on the originating satellite, used by the receiving side, and is written as, for example, SIP 200 OK (SDP answer (c= the originating target satellite IMS AGW IP address used by the terminating side)).

[0319] S622: S-CSCF30H sends the response message (SIP 200 OK) received in S621 to SAT IMS AS30X.

[0320] S623: P-CSCF30G decides to set up UPF with ULCL30E3 on the destination satellite and modify the filter criteria for terminal 20A.

[0321] S624: P-CSCF30G sends a request message (Npcf_PolicyAuthorization_Update request) to PCF30C requesting an update of satellite information. This message requests that ULCL and UPF be set on the satellite indicated by the information of the new destination satellite, and requests that the packet filter in the terminal, which identifies the voice media and associates it with the QoS flow, add the termination point within IMS AGW30FL3 on the satellite as the destination. The request message also includes the IP address of the termination point of IMS AGW30FL3 on the destination satellite used by the terminal. For example, the message is written as Npcf_PolicyAuthorization_Update request (the originating target satellite IMS AGW IP address used by UE).

[0322] S625: PCF30C sends a response message (Npcf_PolicyAuthorization_Update response) to P-CSCF30G for the request message received in S624.

[0323] S626: PCF30C sends a request message (Npcf_SMPolicyControl_UpdateNotify request) to SMF30B requesting an update of satellite information. This request message includes the IP address of the endpoint of IMS AGW30FL3 on the originating target satellite used by the terminal, and is written as, for example, Npcf_SMPolicyControl_UpdateNotify request (the originating target satellite IMS AGW IP address used by UE).

[0324] S627: SMF30B sends a response message (Npcf_SMPolicyControl_UpdateNotify response) to PCF30C for the request message received in S626.

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

[0326] S631: SMF30B decides to set the ULCL and UPF on the destination satellite.

[0327] S632: SMF30B sends a request message (PFCP Session Establishment request) to UPF30D3L3 requesting the establishment of a route for transferring user data for the uplink (UL).

[0328] S633: UPF30D3L3 sends a response message (PFCP Session Establishment response) to SMF30B for the request message received in S632. This response message includes a Packet Detection Rule (PDR) that has information indicating the UL data endpoint (TEID for UL within PSA3) set. For example, this response message is written as PFCP Session Establishment response (PDR=TEID for UL within PSA3 (Tunnel Endpoint IDentifier)).

[0329] S634: SMF30B sends a request message (PFCP Session Establishment request) to ULCL30E3 requesting the establishment of a route for transferring user data. The request message includes information to set the endpoint of IMS AGW30FL3 on the destination satellite as a UL traffic filter for the destination L-UPF (UPF30D3L3), and information to set the endpoint of the source IMS AGW (IMS AGW30FL) as a UL traffic filter for the source ULCL (ULCL30E). For example, the request message includes a first request message for UL to PSA3, a second request message for UL to PSA1, a third request message for UL originating from base station 10B, a fourth request message for DL, a fifth request message for tunnel UL, and a sixth request message for tunnel DL. Furthermore, the first request message is written as PFCP Session Establishment request (Traffic filter for UL to PSA3=target satellite IMS AGW IP address, FAR=PSA3 UL TEID), the second request message as PFCP Session Establishment request (Traffic filter for UL to PSA1=default, FAR=PSA1 UL TEID), the fourth request message as PFCP Session Establishment request (FAR=target gNB DL TEID), the fifth request message as PFCP Session Establishment request (Traffic filter for UL to source ULCL=source satellite IMS AGW IP address, FAR=source ULCL UL TEID), and the sixth request message as PFCP Session Establishment request (PDR request). Here, FAR indicates the Forwarding Action Rule.

[0330] S635: ULCL30E3 sends a response message (PFCP Session Establishment response) to SMF30B for the request message received in S634. The response message for the third request message is denoted as PFCP Session Establishment response (PDR=target ULCL UL TEID), the response message for the fourth request message is denoted as PFCP Session Establishment response (PDR=target ULCL DL TEID), and the response message for the sixth request message is denoted as PFCP Session Establishment response (PDR=target ULCL DL forwarding TEID).

[0331] S636: SMF30B sends a request message (PFCP Session Modification request) to ULCL30E for updating the user data transfer path for tunnel DL. For example, this request message is written as PFCP Session Modification request (FAR=target ULCL DL forwarding TEID).

[0332] S637: ULCL30E sends a response message (PFCP Session Modification response) to SMF30B for the request message received in S636.

[0333] S638: SMF30B sends a request message (PFCP Session Modification request) to UPF30D1R for updating the user data transfer path for DL. For example, this request message is written as PFCP Session Modification request (FAR=target ULCL DL TEID).

[0334] S639: UPF30D1R sends a response message (PFCP Session Modification response) to SMF30B for the request message received in S638.

[0335] S640: SMF30B sends a request message (PFCP Session Modification request) to UPF30D3L3 for updating the user data transfer path for DL. For example, this request message is written as PFCP Session Modification request (FAR=target ULCL DL TEID).

[0336] S641: UPF30D3L3 sends a response message (PFCP Session Modification response) to SMF30B for the request message received in S640.

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

[0338] S651: SMF30B decides to simultaneously perform the following actions on terminal 20A: setting the ULCL and UPF on the destination satellite and updating the QoS rules.

[0339] S652: SMF30B sends a request message (Namf_Communication_N1N2MessageTransfer request) to AMF30A for updating the PDU session resource settings. For example, the request message is written as Namf_Communication_N1N2MessageTransfer request (N1N2MessageTransferReqData(n2InfoContainer(smInfo(n2InfoContent(PDU Session Resource Modify Request Transfer(UL NG-U UP TNL Information=target ULCL UL TEID)))))).

[0340] S653: AMF30A sends a response message (Namf_Communication_N1N2MessageTransfer response) to SMF30B for the request message received in S652.

[0341] S654: The AMF30A sends a request message to base station 10C for updating the PDU session resource settings (PDU Session Resource Modify Request). For example, this message is written as PDU Session Resource Modify Request (PDU Session Resource Modify Request Transfer(UL NG-U UP TNL Information=target ULCL UL TEID)).

[0342] S655: Base station 10C sends a message (DLInformationTransfer) to terminal 20A containing information indicating a request for updating the PDU session resource settings. For example, the message is written as DLInformationTransfer(dedicatedNAS-Message(DL NAS transport(Payload container type(N1 SM information), Payload container(PDU Session Modification Command)))).

[0343] S656: Base station 10C, AMF30A, sends a response message (PDU Session Resource Modify response) to the request message received in S654.

[0344] S657: AMF30A sends a request message (Nsmf_PDUSession_UpdateSMContext request) to SMF30B requesting a context update for the PDU session. For example, this request message is written as Nsmf_PDUSession_UpdateSMContext request (SmContextUpdateData(n2SmInfo(PDU Session Resource Modify Response Transfer))).

[0345] S658: SMF30B sends a response message (Nsmf_PDUSession_UpdateSMContext response) to AMF30A for the request message received in S657.

[0346] S659: Terminal 20A sends a message (ULInformationTransfer) to base station 10C that contains information indicating the completion of the PDU session resource configuration update requested by the message received in S655. For example, the message is written as ULInformationTransfer(dedicatedNAS-Message(UL NAS transport(Payload container type(N1 SM information), Payload container(PDU Session Modification Complete)))).

[0347] S660: Base station 10C sends a message (Uplink NAS Transport) to AMF30A containing information indicating the completion of the PDU session resource configuration update received in S659. For example, the message is written as Uplink NAS Transport(NAS-PDU(UL NAS transport(Payload container type(N1 SM information), Payload container(PDU Session Modification Complete)))).

[0348] S661: AMF30A sends a message to SMF30B containing information indicating the completion of the PDU session resource configuration update received in S660 (Nsmf_PDUSession_UpdateSMContext request). For example, this message is written as Nsmf_PDUSession_UpdateSMContext request (SmContextUpdateData(n1SmMsg(PDU Session Modification Complete))).

[0349] S662: SMF30B sends a response message (Nsmf_PDUSession_UpdateSMContext response) to AMF30A for the request message received in S661.

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

[0351] S671: The SAT IMS AS30X recognizes that the ULCL, UPF, and IMS AGW configurations have been completed on the satellite where the terminal will be newly accommodated. The SAT IMS AS30X also sends a message (SIP re-INVITE) requesting a change in voice call settings after the timer activated in S607 has expired. This message prompts the terminal and the receiving IMS AGW30FL3 to update information regarding the destination of the voice media. Alternatively, the SAT IMS AS30X may trigger the transmission of this message by a notification from the SMF30B instead of a timer.

[0352] S672: SAT IMS AS30X sends a message (SIP re-INVITE) to S-CSCF30H requesting a change in voice call configuration. The message includes information (PSI) indicating that the terminal is using satellite access, including information about the satellite to which the terminal will be newly accommodated. The message also includes a negotiation offer (SDP offer) which includes the IP address of the termination point of IMS AGW30FL3 on the destination satellite and information (a=target satellite-optimal-routing-requested-to-fixedpart) requesting that voice media be sent to IMS AGW30FL3 on the destination satellite. For example, the message is written as SIP re-INVITE (PSI(satellite constellation id, satellite-id), SDP offer (c=the terminating satellite IMS AGW IP address, a=target satellite-optimal-routing-requested-to-fixedpart)).

[0353] S673: S-CSCF30H sends the message received in S672 (SIP re-INVITE) to P-CSCF30G.

[0354] S674: P-CSCF30G decides to update the settings for the optimal inter-satellite route on the terminal and the originating IMS AGW30FL2, etc., based on the information (a=target satellite-optimal-routing-requested-to-fixedpart) contained in the message received in S672 that requests the transmission of voice media to IMS AGW30FL3 on the destination satellite.

[0355] S675: P-CSCF30G sends a message (SIP re-INVITE) to terminal 20A requesting a change in voice call settings. This message includes the IP address of the termination point of IMS AGW30FL3 on the satellite where the originating device is moving to, and is written as, for example, SIP re-INVITE (SDP offer (c= the originating target satellite IMS AGW IP address)).

[0356] S676: Terminal 20A sends a message (SIP 200 OK) to P-CSCF30G indicating a successful response. This message includes the IP address of the originating terminal 20A's endpoint and is written as, for example, SIP 200 OK (SDP answer (c= the originating UE IP address)).

[0357] S677: P-CSCF30G sends a success response message (SIP 200 OK) to S-CSCF30G. This message includes the IP address of the termination point of IMS AGW30FL3 on the satellite to which the originating side is traveling, and is written as, for example, SIP 200 OK (SDP answer (c= the originating target satellite IMS AGW IP address used by the terminating side)).

[0358] S678: S-CSCF30G sends the message received in S677 (SIP re-INVITE) to SAT IMS AS30X.

[0359] S679: SAT IMS AS30X sends a message (SIP re-INVITE) to S-CSCF30G requesting a change in voice call configuration. The message includes information (PSI) indicating that the terminal is using satellite access, including information about the satellite to which the terminal will be newly accommodated. The message also includes a negotiation offer (SDP offer) which includes the IP address of the termination point of IMS AGW30FL3 on the destination satellite and information (a=target satellite-optimal-routing-requested-to-fixedpart) requesting that voice media be sent to IMS AGW30FL3 on the destination satellite. For example, the message is written as SIP re-INVITE (PSI(satellite constellation id, satellite-id), SDP offer (c=the originating target satellite IMS AGW IP address used by the terminating side, a=target satellite-optimal-routing-requested-to-fixedpart)).

[0360] S680: S-CSCF30G sends the message received in S679 (SIP re-INVITE) to I-CSCF30I.

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

[0362] S681: I-CSCF30I sends the message (SIP re-INVITE) received in S680 in Figure 19 to S-CSCF30H2.

[0363] S682: S-CSCF30H2 sends the message received by S681 (SIP re-INVITE) to SAT IMS AS30X2.

[0364] S683: SAT IMS AS30X2 sends the message received in S682 (SIP re-INVITE) to S-CSCFH2.

[0365] S684: S-CSCF30H2 sends the message received in S683 (SIP re-INVITE) to P-CSCF30G2.

[0366] S685: P-CSCF30G2 sends a request message (H.248 MOD request) to IMS AGW30FL2 requesting settings related to the control (or modification) of voice communication.

[0367] S686: IMS AGW30FL2 sets the originating terminal point for data transmission with the originating side.

[0368] S687: IMS AGW30FL2 sends a response message (H.248 MOD response) to P-CSCF30G2 for the request message received in S685.

[0369] S688: P-CSCF30G2 sends a message (SIP re-INVITE) to terminal 20B requesting a change in voice call settings. This message includes the IP address of the termination point of the IMS AGW on the receiving satellite, and is written as, for example, SIP re-INVITE (SDP offer (c= the terminating satellite IMS AGW IP address)).

[0370] S689: Terminal 20B sends a message (SIP 200 OK) to P-CSCF30G2 indicating a successful response. This message includes information in the PANI indicating that the connection is via satellite (access-type=3GPP-NR-SAT), MCC, MNC, TAC, and NR cell ID, and the SDP answer includes the IP address of the termination point of the originating terminal 20B. For example, this message is written as SIP 200 OK (PANI(access-type=3GPP-NR-SAT, utran-cell-id-3gpp=MCC+MNC+TAC+NR cell ID), SDP answer (c= the terminating UE IP address)).

[0371] S690: P-CSCF30G2 sends a message (SIP 200 OK) to S-CSCF30H2 indicating a successful response. This message includes information in the PANI indicating that the connection is via satellite (access-type=3GPP-NR-SAT), MCC, MNC, TAC, and NR cell identifier (NR cell ID), and the SDP answer includes the IP address of the termination point of IMS AGW30FL2 on the receiving satellite. For example, this message is written as SIP 200 OK (PANI(access-type=3GPP-NR-SAT, utran-cell-id-3gpp=MCC+MNC+TAC+NR cell ID), SDP answer (c= the terminating satellite IMS AGW IP address)).

[0372] S691: S-CSCF30H2 sends the message received by S690 (SIP 200 OK) to SAT IMS AS30X2.

[0373] S692: SAT IMS AS30X2 sends SIP 200 OK, a message indicating success, to S-CSCF30H2. This message includes the IP address of the termination point of IMS AGW30FL2 on the receiving satellite. For example, the message is written as SIP 200 OK (SDP answer (c= the terminating satellite IMS AGW IP address)).

[0374] S693: S-CSCF30H2 sends the message received in S692 (SIP 200 OK) to I-CSCF30I.

[0375] S694: I-CSCF30I sends the message received in S693 (SIP 200 OK) to S-CSCF30H.

[0376] S695: S-CSCF30H sends the message received in S694 (SIP 200 OK) to SAT IMS AS30X.

[0377] In the above case, if no satellite change occurs on the receiving end, the processes shown in S685 to S687 may be executed, and if a satellite change occurs on the receiving end, the processes shown in S688 to S695 may be executed.

[0378] S700: The voice call between terminal 20A and terminal 20B continues seamlessly without interruption.

[0379] The above embodiment makes it possible to configure voice call settings and switch IMS AGWs on satellites in a satellite-based wireless communication system, taking into account satellite-related information included in subscriber information.

[0380] (Device Configuration) Next, an example of the functional configuration of the base station 10, network node 30, and terminal 20 that perform the processing and operations described above will be explained. 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 be equipped with only some of the functions in the embodiments.

[0381] <Base Station 10 and Network Node 30> Figure 21 is a diagram showing an example of the functional configuration of a base station 10 and a network node 30. As shown in Figure 21, 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 21 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.

[0382] 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, information from a higher layer. A communication unit including the transmitting unit 110 and the receiving unit 120 may be configured.

[0383] 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 them from the storage device as needed.

[0384] 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 unit of the control unit 140 may be included in the transmission unit 110, and the signal reception function unit of the control unit 140 may be included in the reception unit 120.

[0385] <Terminal 20> Figure 22 is a diagram showing an example of the functional configuration of terminal 20. As shown in Figure 22, terminal 20 has a transmitting unit 210, a receiving unit 220, a setting unit 230, and a control unit 240. The functional configuration shown in Figure 22 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. In addition, the communication device that becomes the resource holder 20 may have a functional configuration similar to that of terminal 20.

[0386] The transmitting unit 210 creates a transmission signal from the transmission data and transmits the transmission signal wirelessly. The receiving unit 220 wirelessly receives various signals and obtains signals from higher layers from the received physical layer signals. The receiving unit 220 also has the function of receiving control signals or reference signals transmitted from the network node 30. A communication unit including the transmitting unit 210 and the receiving unit 220 may be configured.

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

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

[0389] (Hardware Configuration) The block diagrams (Figures 21 and 22) 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.

[0390] Functions include, but are not limited to, judgment, decision, determination, 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. In all cases, as mentioned above, the method of implementation is not particularly limited.

[0391] 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 23 is a diagram showing an example of the hardware configuration of the base station 10 and terminal 20 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 above-mentioned base station 10 and terminal 20 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.

[0392] In the following explanation, the term "device" can be read as "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.

[0393] 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 data reading and writing in the storage device 1002 and auxiliary storage device 1003.

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

[0395] 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 the 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 21 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 22 may be implemented by a control program stored in the storage device 1002 and operated by the processor 1001. Although the above-described processes have been explained as being executed by one processor 1001, they may be executed simultaneously or sequentially by two or more processors 1001. The processor 1001 may be implemented by one or more chips. The program may also be transmitted from the network via a telecommunications line.

[0396] 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 the present disclosure.

[0397] 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 disk, a digital multipurpose disk, a Blu-ray® disk), 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.

[0398] The communication device 1004 is hardware (transmitting / receiving 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 be configured to include, for example, a high-frequency switch, duplexer, filter, frequency synthesizer, etc., in order to implement at least one of frequency division duplex (FDD) and time division duplex (TDD). For example, the transmitting and receiving antenna, amplifier section, transmitting and receiving section, transmission path interface, etc., may be implemented by the communication device 1004. The transmitting and receiving section may be implemented in a physically or logically separated manner, with a transmitting section and a receiving section.

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

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

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

[0402] Figure 24 shows an example of the configuration of vehicle 2001. As shown in Figure 24, vehicle 2001 includes a drive unit 2002, a steering unit 2003, an accelerator pedal 2004, a brake pedal 2005, a shift lever 2006, front wheels 2007, rear wheels 2008, an axle 2009, an electronic control unit 2010, various sensors 2021 to 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.

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

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

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

[0406] The Information Service 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 Service 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 Service 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.).

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

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

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

[0410] 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 the information based on the above input.

[0411] 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 a memory 2032 that can be used by the microprocessor 2031. Based on the information stored in the 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.

[0412] <Note> (Note 1) A network node comprising: a transmitting unit that transmits a first message requesting subscriber information to a first network node; and a receiving unit that receives a second message from the first network node that includes subscriber information, including first configuration information and second configuration information, wherein the first configuration information indicates that when a third message requesting voice call setup, including information indicating that the terminal is using satellite access, is received from a terminal, the third message should be forwarded to the second network node; and the second configuration information indicates that when a fourth message requesting voice call setup, including information indicating that a terminal on another network side is using satellite access, is received from the third network node, the fourth message should be forwarded to the second network node. (Appendix 2) A network node having: a receiving unit that receives a first message from a first network node requesting voice call setup, which includes information indicating that the terminal is using satellite access; and a control unit that terminates the first message, wherein the receiving unit further has a transmitting unit that receives information about the satellite accommodating the terminal from a second network node and transmits a second message to the first network node requesting voice call setup, which includes information about the satellite accommodating the terminal and information indicating that the terminal is using satellite access, destined for another network. (Note 3) A network node having: a receiving unit that receives from a first network node a first message requesting voice call setup, or a second message indicating that voice call setup is in progress, which includes information about the satellite accommodating the other network terminal and information indicating that the other network terminal is using satellite access; a control unit that terminates the first message or the second message and determines that it is possible to set an optimal inter-satellite route from the information about the satellite accommodating the other network terminal and the information about the satellite accommodating the local network terminal; and a transmitting unit that transmits to the first network node a third message requesting voice call setup, or a fourth message indicating that voice call setup is in progress, which includes information about the satellite accommodating the terminal, information indicating that the terminal is using satellite access and information requesting that an optimal inter-satellite route be set.(Appendix 4) A network node having: a receiving unit that receives from a first network node a first message requesting voice call setup, or a second message indicating voice setup in progress, which includes information indicating that the terminal is using satellite access, including information about the satellite accommodating the terminal, and information requesting the setting of an optimal inter-satellite route; and a control unit that selects an IMS (IP Multimedia Subsystem) access gateway on the satellite indicated by the satellite information and performs the setup of the IMS access gateway. (Appendix 5) A communication method performed by a network node, comprising the steps of: transmitting a first message to a first network node requesting subscriber information; and receiving a second message from the first network node containing subscriber information, which includes first configuration information and second configuration information, wherein the first configuration information indicates that if the network node receives a third message from a terminal requesting voice call setup, which includes information indicating that the terminal is using satellite access, the third message should be forwarded to the second network node; and the second configuration information indicates that if the network node receives a fourth message from a third network node requesting voice call setup, which includes information indicating that a terminal on another network side is using satellite access, the fourth message should be forwarded to the second network node.

[0413] In any of the provisions of Appendix 1 to Appendix 5, it is possible to configure voice call settings and switch the IMS AGW on the satellite in a satellite-based wireless communication system, taking into account satellite-related information included in subscriber information.

[0414] (Supplement to Embodiments) Embodiments of the present invention have been described above, but 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. The processing procedures described in the embodiments may be rearranged as long as they do 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 realized 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 any suitable storage medium such as random access memory (RAM), flash memory, read-only memory (ROM), EPROM, EEPROM, register, hard disk (HDD), removable disk, CD-ROM, database, server, or other appropriate storage medium.

[0415] Furthermore, notification of information is not limited to the embodiments described herein and may be carried out by other means. For example, 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.

[0416] Each aspect / embodiment described in this disclosure refers to 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)), IEEE 802.20 may apply to at least one system utilizing UWB (Ultra-WideBand), Bluetooth®, or other appropriate systems, and to next-generation systems extended, modified, created, or defined based thereon. Alternatively, multiple systems may be applied in combination (e.g., a combination of at least one of LTE and LTE-A with 5G).

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

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

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

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

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

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

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

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

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

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

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

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

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

[0430] A base station can accommodate one or more (e.g., three) cells. If a base station accommodates multiple cells, the entire coverage area of ​​the base station can be divided into multiple 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.

[0431] 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 control or operation based on the information.

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

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

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

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

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

[0437] 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, or inquiring (e.g., searching in a table, database, or other data structure), or ascertaining. “Determining” may also include receiving (e.g., receiving information), transmitting (e.g., sending information), inputting, outputting, or 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."

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

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

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

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

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

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

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

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

[0446] Each aspect / embodiment described in this disclosure 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).

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

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

Claims

A transmitting unit that transmits a first message requesting subscriber information to a first network node, A receiving unit that receives a second message from the first network node, which includes subscriber information, including first configuration information and second configuration information, It has, The first configuration information indicates that when the terminal receives a third message requesting voice call configuration, which includes information indicating that the terminal is using satellite access, the third message should be forwarded to the second network node. The second configuration information indicates that when the third network node receives a fourth message requesting voice call configuration, which includes information indicating that the terminal on the other network side is using satellite access, the second network node will forward the fourth message. Network node. 　 A receiving unit receives a first message from a first network node requesting voice call setup, which includes information indicating that the terminal is using satellite access. A control unit that terminates the first message, It has, The receiving unit receives information from the second network node regarding the satellite housing the terminal. The first network node further includes a transmitting unit that transmits a second message requesting voice call setup, which includes information about the satellite accommodating the terminal and information indicating that the terminal is using satellite access, to another network. Network node. 　 From the first network node, information including information about the satellite accommodating the other network terminal, and information indicating that the other network terminal is using satellite access, The first message requesting voice call setup, or A receiving unit that receives a second message indicating that voice call setup is in progress, Terminate the first message or the second message, A control unit that determines that it is possible to set an optimal inter-satellite route based on information from satellites accommodating terminals on other networks and information from satellites accommodating terminals on its own network, The first network node includes information indicating that the terminal is using satellite access, including information about the satellite accommodating the terminal, and information requesting the establishment of an optimal inter-satellite path. A third message requesting voice call setup, or A transmitting unit that sends a fourth message indicating that voice call setup is in progress, A network node that has 　 From the first network node, information indicating that the terminal is using satellite access, including information about the satellite accommodating the terminal, and information requesting the establishment of an optimal inter-satellite path, The first message requesting voice call setup, or A receiving unit that receives a second message indicating that voice settings are being configured, A control unit that selects an IMS (IP Multimedia Subsystem) access gateway on the satellite indicated by the satellite information and executes the configuration of the IMS access gateway, A network node that has 　 The steps include sending a first message requesting subscriber information to the first network node, The steps include receiving a second message from the first network node, which includes subscriber information, including first configuration information and second configuration information, It has, The first configuration information indicates that when the terminal receives a third message requesting voice call configuration, which includes information indicating that the terminal is using satellite access, the third message should be forwarded to the second network node. The second configuration information indicates that when the third network node receives a fourth message requesting voice call configuration, which includes information indicating that the terminal on the other network side is using satellite access, the second network node will forward the fourth message. The communication method used by network nodes.

Images