Network node and base station

Abstract

This network node includes: a reception unit that receives, from another network node, a first message that requests deployment information including an identifier of a satellite, a list of identifiers of communication devices deployed on the satellite, and information on a range of an internet protocol (IP) address allocated to a terminal using the satellite; and a transmission unit that transmits a second message including the deployment information to the other network node.

Description

Network Nodes and Base Stations

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

[0002] 3GPP (registered trademark) (3rd Generation Partnership Project) is currently studying a wireless communication system called 5G or NR (New Radio) (hereinafter, the wireless communication system will be referred to as "5G" or "NR") in order to achieve a larger system capacity, a higher data transmission speed, and a lower latency in wireless sections. Various wireless technologies are being studied for 5G to meet the requirements of achieving a throughput of 10 Gbps or more while keeping latency in wireless sections to 1 ms or less.

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

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

[0005] Furthermore, in 3GPP Rel-19, in order to realize IMS voice terminal-satellite-terminal communication (UE-satellite-UE communication), the issue of reducing the impact on existing specifications when deploying 5GC network functions and IMS components on satellites is a challenge (see, for example, Non-Patent Document 3). Here, terminal-satellite-terminal communication refers to communication between terminals under routing that keeps user plane traffic within the satellite. The types of satellites handled include geostationary satellites (GEO), low Earth orbit satellites (LEO), and medium Earth orbit satellites (MEO).

[0006] 3GPP TS 23.501 V18.4.0 (2023-12) 3GPP TS 23.228 V18.4.0 (2023-12) 3GPP TR 23.700-29 V0.2.0 (2023-11) 3GPP TS 38.413 V17.7.0 (2024-01) 3GPP TS 29.244 V18.4.0 (2023-12) 3GPP TS 23.334 V17.2.0 (2022-06) 3GPP TS 29.334 V17.2.0 (2022-06) 3GPP TS 24.501 V18.5.0 (2023-12) 3GPP TS 23.502 V18.4.0 (2023-12) 3GPP TS 29.502 V18.5.0 (2023-12) 3GPP TS 29.571 V18.4.0 (2023-12) 3GPP TS 29.512 V18.4.0 (2023-12) 3GPP TS 29.518 V18.4.0 (2023-12) 3GPP TS 24.008 V18.5.0 (2023-12)

[0007] In terminal-satellite-terminal communication, communication equipment such as base stations, user plane functions and IMS access gateways are deployed, for example, in geostationary satellites.

[0008] Here, the network nodes deployed on the satellite and the network nodes deployed on the ground need to discover and select communication partners.

[0009] The present invention has been made in view of the above points, and has as its object to enable communication between a communication device deployed on a satellite and a communication device deployed on the ground in a wireless communication system.

[0010] According to the disclosed technology, there is provided a network node having: a receiving unit that receives, from another network node, a first message requesting deployment information including an identifier of a satellite, a list of identifiers of communication devices deployed on the satellite, and information regarding a range of IP (Internet Protocol) addresses assigned to terminals that use the satellite; and a transmitting unit that transmits, to the other network node, a second message including the deployment information.

[0011] According to the disclosed technology, in a wireless communication system, a communication device deployed on a satellite and a communication device deployed on the ground can communicate with each other.

[0012] FIG. 1 is a diagram for explaining an example of a communication system. FIG. 2 is a diagram for explaining an example of a communication system in a roaming environment. FIG. 3 is a diagram for explaining an example of an IMS data channel network. FIG. 4 is a diagram showing an example of a first sequence diagram in an embodiment of the present invention. FIG. 5 is a diagram showing an example of a second sequence diagram in an embodiment of the present invention. FIG. 6 is a diagram showing an example of a third sequence diagram in an embodiment of the present invention. FIG. 7 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. FIG. 8 is a diagram showing an example of the functional configuration of a terminal 20 in an embodiment of the present invention. FIG. 9 is a diagram showing an example of the hardware configuration of a base station 10, a terminal 20, and a network node 30 in an embodiment of the present invention. FIG. 10 is a diagram showing an example of the configuration of a vehicle 2001 in an embodiment of the present invention.

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

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

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

[0016] Fig. 1 is a diagram illustrating an example of a communication system. As shown in Fig. 1, the communication system is composed of a UE, which is a terminal 20, and multiple network nodes 30. Hereinafter, it is assumed that one network node 30 corresponds to each function, but multiple functions may be realized by one network node 30, or multiple network nodes 30 may realize one function. Furthermore, the "connection" described below may be a logical connection or a physical connection.

[0017] The RAN (Radio Access Network) is a network node 30 having a radio access function, which may include a base station 10, and is connected to a UE, an AMF (Access and Mobility Management Function), and a 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), registering management, connecting management, reachability management, and terminal mobility management. The UPF is a network node 30 having functions related to processing user plane data, such as a PDU (Protocol Data Unit) session point to the outside that interconnects with the DN (Data Network), packet routing and forwarding, and user plane Quality of Service (QoS) handling. The UPF and the DN constitute a network slice. In the wireless communication network according to the embodiment of the present invention, multiple network slices are constructed.

[0018] The AMF is connected to the 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). The AMF, SMF, NSSF, NEF, NRF, UDM, AUSF, PCF, and AF are network nodes 30 that are mutually connected 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 having functions such as session management, UE IP (Internet Protocol) address allocation and management, DHCP (Dynamic Host Configuration Protocol) function, ARP (Address Resolution Protocol) proxy, and roaming function. The NEF is a network node 30 having a function of notifying other NFs (Network Functions) of capabilities and events. The NSSF is a network node 30 having functions such as selecting a network slice to which a UE connects, determining an allowed NSSAI (Network Slice Selection Assistance Information), determining an NSSAI to be set, and determining an AMF set to which a UE connects. The PCF is a network node 30 having a function of controlling network policies. The AF is a network node 30 having a function of controlling application servers. The NRF is a network node 30 having a 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 a UDR (User Data Repository) that stores the data.

[0020] Fig. 2 is a diagram illustrating an example of a communication system in a roaming environment. As shown in Fig. 2, the network is composed of a UE, which is a terminal 20, and multiple network nodes 30. Hereinafter, it is assumed that one network node 30 corresponds to each function, but multiple functions may be realized by one network node 30, or multiple network nodes 30 may realize one function. Furthermore, the "connection" described below may be a logical connection or a physical connection.

[0021] The RAN is a network node 30 having a radio access function, and is connected to the UE, the AMF, and the 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 having functions such as a PDU session point to the outside that interconnects with the DN, packet routing and forwarding, and user plane QoS handling. The UPF and the DN constitute a network slice. In the wireless communication network according to the embodiment of the present invention, multiple network slices are constructed.

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

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

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

[0025] Fig. 3 is a diagram illustrating an example of an IMS data channel network. As shown in Fig. 3, the IMS data channel network is configured with a terminal 20 (UE) and multiple network nodes 30 in each of an originating network and a terminating network. Hereinafter, it is assumed that one network node 30 corresponds to each function, but multiple functions may be realized by one network node 30, or multiple network nodes 30 may realize one function. Furthermore, the "connection" described below may be a logical connection or a physical connection. The network node 30 has, for example, the following functions described in Non-Patent Document 2:

[0026] The IMS-AGW (Access Gateway) is a network node 30 having a gateway function between the UE and the IMS network, a function related to access processing for voice communication, and the like.

[0027] A P-CSCF (Proxy-Call Session Control Function) is a network node 30 that has a proxy function between the UE and the IMS network, an access control function for voice communication, and the like.

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

[0029] The I-CSCF (Interrogate-Call Session Control Function) is a connection point on the destination network side between networks (e.g., between the source network side and the destination network side) in the IMS network, and is a network node 30 that has, for example, the function of forwarding a received SIP request to the S-CSCF of its own network.

[0030] An IMS AS (IP Multimedia Subsystem Application Server) is a network node 30 in an IMS network that has functions such as communicating with a DCSF for event notification and receiving data channel control instructions from the DCSF to communicate with an MF. The IMS AS also receives a communication termination point registration request from a DCSF (Data Channel Signalling Function), converts the received registration request into a SIP Register, and sends it to a Serving-Call Session Control Function (S-CSCF). The IMS AS also 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 an event report from the IMS-AS and determining whether to allow the provision of a data channel service, managing the bootstrap data channel, and performing HTTP web server functions.

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

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

[0034] (Example) A procedure for enabling communication between a communication device deployed on a satellite and a communication device deployed on the ground in a wireless communication system will be described.

[0035] In this embodiment, a pre-configured base station 10, a UPF 30A, and an IMS AGW 30B are deployed on a geostationary earth orbit (GEO) to realize IMS voice terminal-satellite-terminal communication (UE-satellite-UE communication).

[0036] The UDR 30F deployed on the ground stores satellite equipment deployment information that associates a satellite identifier, a list of identifiers of communication devices deployed on the satellite, and information on the range of IP (Internet Protocol) addresses assigned to terminals that use the satellite. Here, the UDR 30F obtains the satellite equipment deployment information from an OAM (Orchestration And Management) 30G, which is a management device that manages communication devices in its own network, or from an OAM 30H in another network (via the OAM 30G).

[0037] Furthermore, the AMF30C, SMF30D, PCF30E, and P-CSCF30J deployed on the ground use the on-satellite equipment deployment information to appropriately select communication equipment deployed on the satellite for each terminal. Communication between the communication equipment deployed on the satellite and the communication equipment deployed on the ground is performed via feeder link termination equipment deployed on the satellite and on the ground, respectively. As a result, when a satellite communications carrier provides satellite equipment and multiple mobile communications carriers use the satellite equipment, the communication equipment of the mobile communications carriers can obtain information about the on-satellite communication equipment online and appropriately use the communication equipment on the satellite.

[0038] The details of the process will be explained below using a sequence diagram. Requests, responses, notifications, etc. sent and received in the procedures described below may be called messages (for example, request messages).

[0039] Fig. 4 shows an example of a first sequence diagram according to an embodiment of the present invention. The processing of each step in Fig. 4 will be described below. This sequence diagram explains the procedure for pre-setting for IMS voice terminal-satellite-terminal communication.

[0040] Thereafter, in steps S101 to S103, processing is executed to acquire information about the communication devices deployed on the satellite (satellite device deployment information).

[0041] S101: The OAM 30H of the other network transmits a message including satellite equipment deployment information, which is information about communication equipment deployed on geostationary satellites (GEO), to the OAM 30G of the home network. The satellite equipment deployment information includes a satellite identifier and a list of identifiers of available communication equipment deployed on the satellite. The satellite equipment deployment information may also include information about the range of IP addresses assigned to the terminal 20.

[0042] S102: The OAM 30G transmits to the UDR 30F a message including the on-satellite equipment deployment information received in S101. If the on-satellite equipment deployment information received in S101 does not include information regarding the range of IP addresses to be assigned to the terminal 20, the OAM 30G may include information regarding the range of IP addresses to be assigned to the terminal 20, which has been determined by the OAM 30G itself, in the deployment information.

[0043] S103: The UDR 30F associates and stores the satellite identifier, the identifier of the communication device deployed on the satellite that is available and included in the satellite equipment deployment information received in S102, and the range of IP addresses to be assigned to the terminal 20. When the SMF 30D assigns an IP address to the terminal 20 that uses a satellite, the IP address is assigned on the mobile network side.

[0044] Thereafter, in steps S104 to S108, a process is executed to register the base station 10 on the satellite with the AMF 30C on the ground.

[0045] S104: The AMF 30C sends a request message (Nudr_DM_Query request) to the UDR 30F to request on-satellite equipment deployment information. The request message does not need to specify a satellite identifier (for example, geoSatelliteId=any) to request all on-satellite equipment deployment information held by the UDR 30F, or it may specify the identifier of the satellite for which on-satellite equipment deployment information is requested.

[0046] S105: The UDR 30F sends a response message (Nudr_DM_Query response) to the request message received in S104 to the AMF 30C. The response message includes a satellite identifier (geoSatelliteId=aa), an identifier of a communication device deployed on the satellite that is available, and a range of IP addresses to be assigned to the terminal 20. The identifiers of the communication devices include an identifier of the base station 10 (gNB ID=xx), an identifier of the UPF 30A (UPF ID=bb), and an identifier of the IMS AGW 30B (IMS AGW ID=cc).

[0047] S106: AMF30C sends a request message (AMF Ordered NG Setup) to base station 10 requesting coordinated information exchange with base station 10, requesting the initiation of interface establishment (NG Setup) for the information exchange.

[0048] S107: The base station 10 transmits a request message (NG Setup request, see section 8.7.1.2 of Non-Patent Document 4) to the AMF 30C requesting execution of NG Setup.

[0049] S108: The AMF 30C transmits to the base station 10 a response message (NG Setup response) in response to the request message received in S107.

[0050] Thereafter, in steps S109 to S112, a process is executed to register the UPF 30A on the satellite with the SMF 30D on the ground.

[0051] S109: The SMF 30D sends a request message (Nudr_DM_Query request) to the UDR 30F to request satellite equipment deployment information. The request message does not need to specify a satellite identifier (for example, geoSatelliteId=any) to request all satellite equipment deployment information held by the UDR 30F, or it may specify the identifier of the satellite for which satellite equipment deployment information is requested.

[0052] S110: The UDR 30F sends a response message (Nudr_DM_Query response) to the request message received in S109 to the SMF 30D. The response message includes a satellite identifier (geoSatelliteId=aa), identifiers of available communication devices deployed on the satellite, and a range of IP addresses to be assigned to the terminal 20. The identifiers of the communication devices include the identifier of the base station 10 (gNB ID=xx), the identifier of the UPF 30A (UPF ID=bb), and the identifier of the IMS AGW 30B (IMS AGW ID=cc).

[0053] S111: SMF 30D sends UPF 30A a request message (PFCP Association Setup request, see section 6.2.6.2 of Non-Patent Document 5) requesting the establishment of a Packet Forwarding Control Protocol (PFCP) association.

[0054] S112: UPF 30A transmits to SMF 30D a response message (PFCP Association Setup response) corresponding to the request message received in S111.

[0055] Thereafter, in steps S113 to S116, a process is executed to register the IMS AGW 30B on the satellite with the P-CSCF 30J on the ground.

[0056] S113: The P-CSCF 30J sends a request message (Nudr_DM_Query request) requesting satellite equipment deployment information to the UDR 30F. The request message does not need to specify a satellite identifier (for example, geoSatelliteId=any) to request all satellite equipment deployment information held by the UDR 30F, or it may specify the identifier of the satellite for which satellite equipment deployment information is requested.

[0057] S114: The UDR 30F sends a response message (Nudr_DM_Query response) to the request message received in S113 to the P-CSCF 30J. The response message includes a satellite identifier (geoSatelliteId=aa), identifiers of available communication devices deployed on the satellite, and a range of IP addresses to be assigned to the terminal 20. The identifiers of the communication devices include an identifier of the base station 10 (gNB ID=xx), an identifier of the UPF 30A (UPF ID=bb), and an identifier of the IMS AGW 30B (IMS AGW ID=cc).

[0058] S115: P-CSCF30J transmits to IMS AGW 30B a request message (IMS-ALG Ordered Re-register, see Section 6.1.7 of Non-Patent Document 6 and Section 5.17.3.7 of Non-Patent Document 7) requesting execution of re-registration based on a request from IMS-ALG (Application Level Gateway).

[0059] S116: The IMS AGW 30B transmits to the P-CSCF 30J a response message (IMS-ALG Ordered Re-register Ack) in response to the request message received in S115.

[0060] The processing following S116 will now be described. Fig. 5 is a diagram showing an example of a second sequence diagram according to an embodiment of the present invention. This sequence diagram explains the processing procedures executed for each terminal in IMS voice terminal-satellite-terminal communication.

[0061] Thereafter, the registration procedure is executed from S201 to S202.

[0062] S201: The terminal 20 transmits a registration request to the AMF 30C via the base station 10.

[0063] S202: The AMF 30C receives a registration accept from the terminal 20 as a response to the registration request received in S201.

[0064] Thereafter, the IMS PDU session establishment procedure is executed from S203 to S218.

[0065] S203: The terminal 20 sends a request message (UL NAS transport, see sections 8.2.10.1, 9.11.3.39, and 9.11.3.40 of Non-Patent Document 8) to the AMF 30C requesting the establishment of a session for a data network that handles voice calls. The request message includes information indicating that information related to Session Management (SM) is included, information indicating a request for establishment of a PDU session, and information related to a Data Network Name (DNN). For example, the request message is expressed as UL NAS transport(Payload container type (N1 SM information), Payload container (PDU Session Establishment request), DNN=ims).

[0066] S204: Based on the request message received via the base station 10 in S203, the AMF 30C confirms that the identifier of the base station 10 matches the identifier (gNB ID=xx) of the base station deployed on the satellite (GEO ID=aa) received in S105 of Figure 4.

[0067] S205: AMF 30C sends to SMF 30D a request message (Nsmf_PDUSession_CreateSMContext request, see Section 4.3.2.2.1 of Non-Patent Document 9, Sections 6.1.6.2.2 and 6.1.6.4.2 of Non-Patent Document 10, and Section 5.4.3.39 of Non-Patent Document 11) requesting the establishment of a session for a data network that handles voice calls. The request message includes information related to the DNN, information indicating a request for establishment of a PDU session, and information related to the SM, including information related to the satellite. The information related to the satellite also includes information indicating that the satellite category is a geostationary satellite (GEO) and an identifier of the satellite (geoSatelliteId=aa). For example, the request message is expressed as Nsmf_PDUSession_CreateSMContext request (Dnn=ims, SmContextCreateData (n1SmMsg (PDU session establishment request), satelliteBackhaulCat(GEO), geoSatelliteId=aa)).

[0068] S206: The SMF 30D sends a request message (Npcf_SMPolicyControl_Create request, see Section 4.3.2.2.1 of Non-Patent Document 9 and Sections 4.2.2.2 and 5.6.2.3 of Non-Patent Document 12) to the PCF 30E, requesting the determination of a policy for an IMS PDU session. The request message includes information related to the DNN and information related to the satellite. The information related to the satellite also includes information indicating that the satellite category is a geostationary satellite (GEO) and an identifier of the satellite (geoSatelliteId=aa). For example, the request message is expressed as Npcf_SMPolicyControl_Create request (SmPolicyContextData(Dnn=ims, satBackhaulCategory=GEO, geoSatelliteId=aa)).

[0069] S207: The PCF 30E sends a request message (Nudr_DM_Query request) to the UDR 30F requesting satellite equipment deployment information. The request message specifies the identifier (geoSatelliteId=aa) of the satellite for which the satellite equipment deployment information is requested.

[0070] S208: The UDR 30F sends a response message (Nudr_DM_Query response) to the request message received in S207 to the PCF 30E. The response message includes a satellite identifier (geoSatelliteId=aa), identifiers of available communication devices deployed on the satellite, and a range of IP addresses to be assigned to the terminal 20. The identifiers of the communication devices include an identifier of the base station 10 (gNB ID=xx), an identifier of the UPF 30A (UPF ID=bb), and an identifier of the IMS AGW 30B (IMS AGW ID=cc).

[0071] S209: The PCF 30E determines to use the UPF 30A and the IMS AGW 30B, both of which are deployed on the satellite, for the requested PDU session. The UPF 30A is used as a PDU Session Anchor (PSA) for the PDU session.

[0072] S210: The PCF 30E sends to the SMF 30D a response message (Npcf_SMPolicyControl_Create response, see section 4.3.2.2.1 of Non-Patent Document 9 and section 5.6.2.4 of Non-Patent Document 12) in response to the request message received in S206. The response message includes information indicating that the UPF 30A and IMS AGW 30B deployed on the satellite will be used for the requested PDU session, an identifier of the UPF 30A (UPF ID=bb), an identifier of the IMS AGW 30B (IMS AGW ID=cc), and information regarding the range of IP addresses to be assigned to the terminal 20. For example, the response message is expressed as Npcf_SMPolicyControl_Create response (SmPolicyDecision (sessRules (authSatelliteEquip (UPF(UPF ID=bb), IMS AGW (IMS AGW ID=cc))), ipv6Index=UE IP address range)).

[0073] S211: SMF30D sends a response message (Nsmf_PDUSession_CreateSMContext response) to the request message received in S205 to AMF30C.

[0074] S212: The SMF 30D sets the identifier (UPF ID=bb) of the UPF 30A based on the information determined by the PCF 30E in S209, which is included in the response message received in S210. Alternatively, the SMF 30D may select the identifier (UPF ID=bb) of the UPF 30A to be set based on the satellite identifier (GEO ID=aa).

[0075] S213: SMF 30D sends a request message (PFCP Session Establishment request, see section 6.3.2 of Non-Patent Document 5) to UPF 30A requesting the establishment of packet forwarding settings.

[0076] S214: UPF 30A transmits to SMF 30D a response message (PFCP Session Establishment response) to the request message received in S213.

[0077] S215: SMF 30D stores the IP address (address value = dd) of the satellite P-CSCF 30J deployed on the ground. In addition, SMF 30D sets the IP address (address value = dd) as the P-CSCF address of enhanced Protocol Configuration Options (ePCO).

[0078] S216: When the SMF 30D assigns an IP address to the terminal 20 that uses a satellite, the SMF 30D assigns an IP address from the range of IP addresses notified by the PCF 30E in S210.

[0079] S217: SMF 30D sends a message (Namf_Communication_N1N2MessageTransfer, see Section 8.3.2.1 of Non-Patent Document 8, Section 4.3.2.2.1 of Non-Patent Document 9, Sections 5.2.2.3.1.1 and 6.1.6.2.18 of Non-Patent Document 13, and Section 10.5.6.3A of Non-Patent Document 14) to AMF 30C to notify acceptance of the PDU session establishment. This message includes the address of P-CSCF 30J (address value = dd) in ePCO. For example, this message is expressed as Namf_Communication_N1N2MessageTransfer(N1N2MessageTransferReqData(n1MessageContainer(PDU Session Establishment accept(Extended protocol configuration options(P-CSCF address = dd))))).

[0080] S218: The AMF 30C sends a message (DL NAS transport, see sections 8.2.11.1, 9.11.3.39, and 9.11.3.40 of Non-Patent Document 8) to the terminal 20 to notify acceptance of the PDU session establishment. The message includes the address of the P-CSCF 30J (address value = dd) in the ePCO. For example, the message is expressed as DL NAS transport (Payload container type (N1 SM information), Payload container (PDU Session Establishment accept (Extended protocol configuration options (P-CSCF address = dd)))).

[0081] The process following S218 will be described below. Fig. 6 is a diagram showing an example of a third sequence diagram according to an embodiment of the present invention. The process of each step in Fig. 6 will be described below.

[0082] Thereafter, the IMS registration procedure is executed from S301 to S308.

[0083] S301: The terminal 20 uses the IP address (address value=dd) of the P-CSCF 30J acquired in S218 of FIG. 6 to transmit a request message (Register) relating to registration to the P-CSCF 30J.

[0084] S302: The P-CSCF 30J transmits the request message (Register) received in S301 to the S-CSCF 30K.

[0085] S303: The S-CSCF 30K transmits a request message (Nhss_ImsUECM_Registration request) requesting registration of the terminal 20 to the HSS 30L.

[0086] S304: The HSS 30L transmits to the S-CSCF 30K a response message (Nhss_ImsUECM_Registration response) in response to the request message received in S303.

[0087] S305: The S-CSCF 30K transmits to the HSS 30L a request message (Nhss_ImsSDM_Get request) requesting acquisition of subscriber information.

[0088] S306: The HSS 30L transmits a response message (Nhss_ImsSDM_Get response) to the request message received in S305 to the S-CSCF 30K. The response message includes the subscriber information.

[0089] S307: The S-CSCF 30K transmits to the P-CSCF 30J a response message (200 OK) in response to the request message received in S302.

[0090] S308: The P-CSCF 30J transmits to the terminal 20 a response message (200 OK) in response to the request message received in S301.

[0091] Thereafter, the IMS voice call procedure is executed from S309 to S322.

[0092] S309: The terminal 20 sends a request message (SIP INVITE) to the P-CSCF 30J, requesting an IMS voice call.

[0093] S310: The P-CSCF 30J recognizes that the terminal 20 is using the satellite (geoSatelliteId=aa) because the IP address of the terminal 20 identified from the request message received in S309 is within the address range assigned to the satellite. Furthermore, the P-CSCF 30J recognizes the identifier (IMS AGW ID=cc) of the IMS AGW 30B available on the satellite.

[0094] S311: The P-CSCF 30J transmits a request message (H.248 ADD request) related to media processing (addition of control) in the voice call to the IMS AGW 30B.

[0095] S312: The IMS AGW 30B acquires resources of the termination point on its own device side related to data transmission with the destination side.

[0096] S313: The IMS AGW 30B transmits to the P-CSCF 30J a response message (H.248 ADD response) in response to the request message received in S311.

[0097] S314: The P-CSCF 30J sends a request message (SIP INVITE) to the S-CSCF 30K, requesting an IMS voice call to the called party. After that, processing based on existing specifications is executed.

[0098] S315: The S-CSCF 30K sends (SIP 183 Session Progress) to the P-CSCF 30J.

[0099] S316: The P-CSCF 30J sends a request message (H.248 MOD) related to media processing (modification of control) for the voice call to the IMS AGW 30B.

[0100] S317: The IMS AGW 30B sets a termination point on the destination side for data transmission with the destination side.

[0101] S318: The IMS AGW 30B transmits to the P-CSCF 30J a response message (H.248 MOD response) in response to the request message received in S316.

[0102] S319: The P-CSCF 30J transmits a request message (H.248 ADD request) related to media processing (addition of control) in the voice call to the IMS AGW 30B.

[0103] S320: The IMS AGW 30B sets a terminal-side termination point for the terminal-destined data, and further acquires resources for the termination point on its own device side.

[0104] S321: The IMS AGW 30B transmits to the P-CSCF 30J a response message (H.248 ADD response) in response to the request message received in S319.

[0105] S322: The P-CSCF 30J sends to the terminal 20 a message (SIP 183 Session Progress) indicating that the request message received in S309 is being processed.

[0106] According to the above-described embodiment, in a wireless communication system, communication devices deployed on satellites and communication devices deployed on the ground can communicate with each other.

[0107] (Device Configuration) Next, a description will be given of an example of the functional configuration of the base station 10, network node 30, and terminal 20 that perform the processes and operations described above. The base station 10, network node 30, and terminal 20 include functions for performing the above-described embodiments. However, the base station 10, network node 30, and terminal 20 may each include only a part of the functions of the embodiments.

[0108] <Base Station 10 and Network Node 30> Fig. 7 is a diagram showing an example of the functional configuration of the base station 10 and the network node 30. As shown in Fig. 7, 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 Fig. 7 is merely an example. As long as the operations according to the embodiment of the present invention can be performed, the names of the functional divisions and functional units may be any. Note that the network node 30 may have the same functional configuration as the base station 10. Furthermore, a network node 30 having multiple different functions in the system architecture may be composed of multiple network nodes 30 separated by function.

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

[0110] The setting unit 130 stores in a storage device preset setting information and various setting information to be transmitted to the terminal 20, and reads out from the storage device as needed. The content of the setting information is, for example, information related to a communication path in the IMS data channel network.

[0111] As described in the embodiment, the control unit 140 performs processing to enable the communication device deployed on the satellite and the communication device deployed on the ground to communicate with each other. The control unit 140 also performs processing related to communication with the terminal 20. The function unit related to signal transmission in the control unit 140 may be included in the transmitting unit 110, and the function unit related to signal reception in the control unit 140 may be included in the receiving unit 120.

[0112] <Terminal 20> Fig. 8 is a diagram showing an example of the functional configuration of the terminal 20. As shown in Fig. 8, the terminal 20 has a transmitting unit 210, a receiving unit 220, a setting unit 230, and a control unit 240. The functional configuration shown in Fig. 8 is merely an example. As long as the operations related to the embodiment of the present invention can be performed, the names of the functional divisions and functional units may be any. In addition, the communication device that becomes the resource holder 20 may have the same functional configuration as the terminal 20.

[0113] The transmitter 210 creates a transmission signal from transmission data and transmits the transmission signal wirelessly. The receiver 220 receives various signals wirelessly and acquires higher layer signals from the received physical layer signals. The receiver 220 also has a function of receiving control signals, reference signals, etc. transmitted from the network node 30. A communication unit including the transmitter 210 and the receiver 220 may be configured.

[0114] The setting unit 230 stores various pieces of setting information received from the network node 30 by the receiving unit 220 in a storage device and reads them from the storage device as needed. The setting unit 230 also stores setting information that is set in advance. The content of the setting information is, for example, information related to communication paths in the IMS network.

[0115] As described in the embodiments, the control unit 240 performs processing to enable the communication device deployed on the satellite and the communication device deployed on the ground to communicate with each other. The function unit related to signal transmission in the control unit 240 may be included in the transmitting unit 210, and the function unit related to signal reception in the control unit 240 may be included in the receiving unit 220.

[0116] (Hardware Configuration) The block diagrams (FIGS. 7 and 8) used to explain the above embodiments show functional blocks. These functional blocks (components) are realized by any combination of at least one of hardware and software. Furthermore, the method for realizing each functional block is not particularly limited. That is, each functional block may be realized using a single device that is physically or logically coupled, or may be realized using two or more physically or logically separated devices that are directly or indirectly connected (for example, using wires, wirelessly, etc.) and these multiple devices. The functional block may also be realized by combining software with the single device or the multiple devices.

[0117] Functions include, but are not limited to, judgment, determination, assessment, calculation, computation, processing, derivation, investigation, search, confirmation, reception, transmission, output, access, resolution, selection, selection, establishment, comparison, assumption, expectation, consideration, broadcasting, notifying, communicating, forwarding, configuring, reconfiguring, allocating, mapping, and assignment. For example, a functional block (component) that performs transmission is called a transmitting unit or transmitter. As mentioned above, there are no particular limitations on how these functions are implemented.

[0118] For example, the base station 10, the network node 30, the terminal 20, etc. according to an embodiment of the present disclosure may function as a computer that performs processing of the wireless communication method of the present disclosure. Fig. 9 is a diagram illustrating an example of the hardware configuration of the base station 10 and the terminal 20 according to an embodiment of the present disclosure. The network node 30 may have the same hardware configuration as the base station 10. The above-described base station 10 and the 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.

[0119] In the following description, the term "apparatus" can be interpreted as a circuit, a device, a unit, etc. The hardware configuration of the base station 10 and the terminal 20 may be configured to include one or more of the apparatuses shown in the drawings, or may be configured to exclude some of the apparatuses.

[0120] Each function in the base station 10 and the terminal 20 is realized by loading specified software (programs) onto hardware such as the processor 1001, the memory device 1002, etc., so that the processor 1001 performs calculations, controls communication by the communication device 1004, and controls at least one of reading and writing data in the memory device 1002 and the auxiliary memory device 1003.

[0121] The processor 1001 controls the entire computer by running, for example, an operating system. The processor 1001 may be configured as a central processing unit (CPU) including an interface with peripheral devices, a control device, an arithmetic unit, a register, etc. For example, the above-mentioned control unit 140, control unit 240, etc. may be realized by the processor 1001.

[0122] The processor 1001 also reads programs (program codes), software modules, data, etc. from at least one of the auxiliary storage device 1003 and the communication device 1004 into the storage device 1002 and executes various processes in accordance with the programs. The programs used are those that cause a computer to execute at least some of the operations described in the above-described embodiments. For example, the control unit 140 of the base station 10 shown in FIG. 7 may be implemented by a control program stored in the storage device 1002 and running on the processor 1001. For example, the control unit 240 of the terminal 20 shown in FIG. 8 may be implemented by a control program stored in the storage device 1002 and running on the processor 1001. While the above-described various processes have been described as being executed by one processor 1001, they may also be executed simultaneously or sequentially by two or more processors 1001. The processor 1001 may be implemented by one or more chips. The programs may also be transmitted from a network via a telecommunications line.

[0123] The storage device 1002 is a computer-readable recording medium and may be configured, for example, by at least one of a read-only memory (ROM), an erasable programmable read-only memory (EPROM), an electrically erasable programmable read-only memory (EEPROM), a random access memory (RAM), etc. The storage device 1002 may also be called a register, a cache, a main memory, etc. The storage device 1002 can store executable programs (program codes), software modules, etc. for implementing a communication method according to an embodiment of the present disclosure.

[0124] The secondary storage device 1003 is a computer-readable recording medium, and may be, for example, at least one of an optical disk 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 versatile disk, a Blu-ray (registered trademark) disk), a smart card, a flash memory (e.g., a card, a stick, a key drive), a floppy (registered trademark) disk, a magnetic strip, etc. The above-mentioned storage medium may be, for example, a database, a server, or other appropriate medium including at least one of the storage device 1002 and the secondary storage device 1003.

[0125] The communication device 1004 is hardware (transmission / reception device) for communicating between computers via at least one of a wired network and a wireless network, and is also referred to as, for example, a network device, a network controller, a network card, a communication module, etc. The communication device 1004 may be configured to include a high-frequency switch, a duplexer, a filter, a frequency synthesizer, etc. to realize at least one of frequency division duplex (FDD) and time division duplex (TDD). For example, a transmission / reception antenna, an amplifier unit, a transmission / reception unit, a transmission path interface, etc. may be realized by the communication device 1004. The transmission / reception unit may be implemented as a transmission unit and a reception unit that are physically or logically separated.

[0126] The input device 1005 is an input device (e.g., a keyboard, a mouse, a microphone, a switch, a button, a sensor, etc.) that receives input from the outside. The output device 1006 is an output device (e.g., a display, a speaker, an LED lamp, etc.) that outputs to the outside. Note that the input device 1005 and the output device 1006 may be integrated into one device (e.g., a touch panel).

[0127] 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 may be configured using different buses between each device.

[0128] Furthermore, the base station 10 and the terminal 20 may be configured to include hardware such as a microprocessor, a digital signal processor (DSP), an application specific integrated circuit (ASIC), a programmable logic device (PLD), or a field programmable gate array (FPGA), and some or all of the functional blocks may be realized by the hardware. For example, the processor 1001 may be implemented using at least one of these pieces of hardware.

[0129] Fig. 10 shows an example configuration of a vehicle 2001. As shown in Fig. 10, the 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 the present disclosure may be applied to a communication device mounted on the vehicle 2001, and may be applied to the communication module 2013, for example.

[0130] The drive unit 2002 is configured, for example, by 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 operated by the user.

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

[0132] The signals from the various sensors 2021 to 2029 include a current signal from a current sensor 2021 that senses the current of the motor, a rotation speed signal of the front and rear wheels obtained by a rotation speed sensor 2022, an air pressure signal of the front and rear wheels obtained by an air pressure sensor 2023, a vehicle speed signal obtained by a vehicle speed sensor 2024, an acceleration signal obtained by an acceleration sensor 2025, an accelerator pedal depression amount signal obtained by an accelerator pedal sensor 2029, a brake pedal depression amount signal obtained by a brake pedal sensor 2026, a shift lever operation signal obtained by a shift lever sensor 2027, and a detection signal for detecting obstacles, vehicles, pedestrians, etc. obtained by an object detection sensor 2028.

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

[0134] The driving assistance system unit 2030 is composed of various devices that provide functions for preventing accidents and reducing the driving burden on the driver, such as millimeter-wave radar, LiDAR (Light Detection and Ranging), cameras, positioning locators (e.g., GNSS, etc.), map information (e.g., high-definition (HD) maps, autonomous vehicle (AV) maps, etc.), gyro systems (e.g., IMU (Inertial Measurement Unit), INS (Inertial Navigation System), etc.), AI (Artificial Intelligence) chips, and AI processors, as well as one or more ECUs that control these devices. In addition, the driving assistance system unit 2030 transmits and receives various information via the communication module 2013 to realize the driving assistance function or the autonomous driving function.

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

[0136] 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 an external device. For example, it transmits and receives various information to and from the external device via wireless communication. The communication module 2013 may be located either inside or outside the electronic control unit 2010. The external device may be, for example, a base station, a mobile station, or the like.

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

[0138] The communication module 2013 receives various information (traffic information, traffic signal information, vehicle-to-vehicle information, etc.) transmitted from external devices and displays it on an information service unit 2012 provided in the vehicle 2001. The information service unit 2012 may be called an output unit that outputs information (for example, outputs information to a device such as a display or speaker 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 external devices 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 to 2029, etc. provided in the vehicle 2001.

[0139] <Additional Notes> (Additional Item 1) A network node comprising: a receiver that receives, from another network node, a first message requesting deployment information, the first message including a satellite identifier, a list of identifiers of communication devices deployed on the satellite, and information regarding a range of IP (Internet Protocol) addresses to be assigned to terminals using the satellite; and a transmitter that transmits a second message including the deployment information to the other network node. (Additional Item 2) The network node according to Additional Item 1, wherein the receiver receives the list from a management device of another network. (Additional Item 3) A network node comprising: a receiver that receives, from a management device of another network, a first message including a satellite identifier and a list of identifiers of communication devices deployed on the satellite; and a second message from a management device of its own network, the second message including the satellite identifier and information regarding a range of IP (Internet Protocol) addresses to be assigned to terminals using the satellite; and a controller that stores the satellite identifier, the list, and information regarding the IP address range in association with each other. (Supplementary Item 4) A network node comprising: a receiver that receives a first message, sent by a terminal, requesting the establishment of a session for a data network that handles voice calls, and receives from a first network node a second message instructing the use of a media gateway deployed on a satellite, a controller that selects a second network node that controls the media gateway, and a transmitter that transmits to the terminal a third message accepting the establishment of the session, the third message including an IP (Internet Protocol) address of the second network node. (Supplementary Item 5) The network node according to Supplementary Item 4, wherein the receiver receives from the first network node a fourth message including information on a range of IP addresses that can be assigned to the terminal, and the controller includes one IP address selected from the range and assigned to the terminal in the third message.(Supplementary Item 6) A network node having: a receiver that receives, from a terminal, a first message requesting a voice call, a controller that identifies a satellite to which the terminal is connected based on an IP (Internet Protocol) address of the terminal included in the first message, and a transmitter that transmits a second message related to media processing for the voice call to a media gateway deployed on the satellite. (Supplementary Item 7) A base station having: a receiver that receives, from the first network node, a first message requesting initiation of establishment of an interface for exchanging information with a first network node, and a transmitter that transmits the second message requesting establishment of the interface to the first network node.

[0140] Any of supplementary items 1 to 7 enables communication devices deployed on satellites and communication devices deployed on the ground to communicate with each other in a wireless communication system.

[0141] (Supplementary Notes on the Embodiments) Although the embodiments of the present invention have been described above, the disclosed invention is not limited to such embodiments, and those skilled in the art will understand various modifications, alterations, alternatives, and substitutions. While specific numerical examples have been used to facilitate understanding of the invention, 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; matters described in two or more items may be used in combination as needed, and matters described in one item may apply to matters described in another item (as long as there is no contradiction). Boundaries between functional units or processing units in functional block diagrams do not necessarily correspond to boundaries between physical components. The operations of multiple functional units may be performed by a single physical component, or the operations of a single functional unit may be performed by multiple physical components. The order of processing steps described in the embodiments may be reversed as long as there is no contradiction. For convenience of processing description, the base station 10 and terminal 20 have been described using functional block diagrams, but such devices may be realized by hardware, software, or a combination thereof. The software operated by the processor of the base station 10 in accordance with an embodiment of the present invention and the software operated by the processor of the terminal 20 in accordance with an embodiment of the present invention may each be stored in random access memory (RAM), flash memory, read-only memory (ROM), EPROM, EEPROM, register, hard disk (HDD), removable disk, CD-ROM, database, server, or any other suitable storage medium.

[0142] Furthermore, the notification of information is not limited to the aspects / embodiments described in the present disclosure, and may be performed using other methods. For example, the notification of information may be performed by physical layer signaling (e.g., Downlink Control Information (DCI), Uplink Control Information (UCI)), higher layer signaling (e.g., Radio Resource Control (RRC) signaling, Medium Access Control (MAC) signaling), broadcast information (Master Information Block (MIB), System Information Block (SIB)), other signals, or a combination thereof. Furthermore, the RRC signaling may be referred to as an RRC message, and may be, for example, an RRC Connection Setup message, an RRC Connection Reconfiguration message, or the like.

[0143] Each aspect / embodiment described in the present disclosure may be implemented using any of the following standards: LTE (Long Term Evolution), LTE-Advanced (LTE-A), 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 (x is, for example, an integer or a decimal number)), 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.17 (WiMAX (registered trademark)), IEEE 802.19 (WiMAX (registered trademark)), IEEE 802.20 (WiMAX (registered trademark)), IEEE 802.21 (Wi-Fi (registered trademark)), IEEE 802.22 (WiMAX (registered trademark)), IEEE 802.23 (WiMAX (registered trademark)), IEEE 802.24 (WiMAX (registered trademark)), IEEE 802.25 (WiMAX (registered trademark)), IEEE 802.26 (WiMAX (registered trademark)), IEEE 802.27 (WiMAX (registered trademark)), IEEE 802.28 (WiMAX (registered trademark)), IEEE 802.29 (WiMAX (registered trademark)), IEEE 802.30 (WiMAX (registered trademark)), IEEE 802.31 (Wi-Fi (registered trademark)), IEEE 802.32 (WiMAX (registered trademark)), IEEE 802.33 (WiMAX (registered trademark)), IEEE 802.34 ( The present invention may be applied to at least one of systems using 802.20, UWB (Ultra-Wide Band), Bluetooth (registered trademark), or other suitable systems, and next-generation systems that are extended, modified, created, or defined based on these systems. The present invention may also be applied to a combination of multiple systems (e.g., a combination of LTE and / or LTE-A with 5G).

[0144] The order of the procedures, sequences, flowcharts, etc. of each aspect / embodiment described herein may be rearranged unless it is consistent. For example, the methods described in this disclosure present elements of various steps using an example order and are not limited to the particular order presented.

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

[0146] The information, signals, etc. described in the present disclosure may be output from a higher layer (or a lower layer) to a lower layer (or a higher layer), or may be input / output via multiple network nodes.

[0147] Input and output information may be stored in a specific location (for example, memory) or may be managed using a management table. Input and output information may be overwritten, updated, or added to. Output information may be deleted. Input information may be transmitted to another device.

[0148] In the present disclosure, the determination may be made by a value represented by one bit (0 or 1), by a Boolean value (true or false), or by a comparison of numerical values ​​(e.g., comparison with a predetermined value).

[0149] Software shall be construed broadly to mean instructions, instruction sets, code, code segments, program code, programs, subprograms, software modules, applications, software applications, software packages, routines, subroutines, objects, executable files, threads of execution, procedures, functions, etc., whether referred to as software, firmware, middleware, microcode, hardware description language, or otherwise.

[0150] Software, instructions, information, etc. may also be transmitted or received over a transmission medium. For example, if software is transmitted from a website, server, or other remote source using wired technologies (such as coaxial cable, fiber optic cable, twisted pair, Digital Subscriber Line (DSL)), and / or wireless technologies (such as infrared, microwave), then these wired and / or wireless technologies are included within the definition of transmission media.

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

[0152] Note that terms described 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 a channel and a symbol may be a signal (signaling). Furthermore, a signal may be a message. Furthermore, a component carrier (CC) may be called a carrier frequency, a cell, a frequency carrier, etc.

[0153] As used in this disclosure, the terms "system" and "network" are used interchangeably.

[0154] Furthermore, the information, parameters, etc. described in the present disclosure may be expressed using absolute values, may be expressed using relative values ​​from a predetermined value, or may be expressed using other corresponding information. For example, a radio resource may be indicated by an index.

[0155] The names used for the above-described parameters are not intended to be limiting in any way. Furthermore, the mathematical expressions using these parameters may differ from those explicitly disclosed in this disclosure. The various channels (e.g., PUCCH, PDCCH, etc.) and information elements may be identified by any suitable names, and therefore the various names assigned to these various channels and information elements are not intended to be limiting in any way.

[0156] In the present disclosure, terms such as "base station (BS)," "radio base station," "base station device," "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. A base station may also be referred to by terms such as a macrocell, a small cell, a femtocell, and a picocell.

[0157] A base station can accommodate one or more (e.g., three) cells. When a base station accommodates multiple cells, the overall coverage area of ​​the base station can be partitioned into multiple smaller areas, and each smaller area can also be provided with communication services by a base station subsystem (e.g., a small indoor base station (RRH: Remote Radio Head)). The terms "cell" or "sector" refer to part or all of the coverage area of ​​a base station and / or base station subsystem that provides communication services within that coverage.

[0158] In the present disclosure, the base station transmitting information to a terminal may be interpreted as the base station instructing the terminal to control or operate based on the information.

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

[0160] 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 some other suitable terminology.

[0161] At least one of the base station and the mobile station may be referred to as a transmitting device, a receiving device, a communication device, etc. At least one of the base station and the mobile station may be a device mounted on a mobile object, the mobile object itself, etc. The mobile object refers to a movable object, and may move at any speed. Naturally, this also includes cases where the mobile object is stationary. Examples of the mobile object include, but are not limited to, vehicles, transport vehicles, automobiles, motorcycles, bicycles, connected cars, excavators, bulldozers, wheel loaders, dump trucks, forklifts, trains, buses, handcars, rickshaws, ships and other watercraft, airplanes, rockets, satellites, drones (registered trademark), multicopters, quadcopters, balloons, and objects mounted thereon. The mobile object may also be a mobile object that moves autonomously based on an operational command. It may be a vehicle (e.g., a car, an airplane, etc.), an unmanned mobile object (e.g., a drone, an autonomous vehicle, etc.), or a robot (manned or unmanned). At least one of the base station and the mobile station may be a device that does 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.

[0162] Furthermore, a base station in the present disclosure may be read as a user terminal. For example, the aspects / embodiments of the present 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, Device-to-Device (D2D) or Vehicle-to-Everything (V2X)). In this case, the terminal 20 may be configured to have the functions of the base station 10 described above. Furthermore, terms such as "uplink" and "downlink" may be read as terms corresponding to terminal-to-terminal communication (for example, "side"). For example, terms such as an uplink channel and a downlink channel may be read as a side channel.

[0163] Similarly, the user terminal in the present disclosure may be read as a base station, in which case the base station may be configured to have the functions of the user terminal described above.

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

[0165] The terms "connected," "coupled," or any variation thereof, refer to 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" to each other. The coupling or connection between elements may be physical, logical, or a combination thereof. For example, "connected" may be read as "access." As used in this disclosure, two elements may be considered to be "connected" or "coupled" to each other using one or more wires, cables, and / or printed electrical connections, as well as electromagnetic energy having wavelengths in the radio frequency range, microwave range, and optical (both visible and invisible) range, as some non-limiting and non-exhaustive examples.

[0166] The reference signal may be abbreviated as RS (Reference Signal) or may be called a pilot depending on the applicable standard.

[0167] As used in this disclosure, the phrase "based on" does not mean "based only on," unless expressly stated otherwise. In other words, the phrase "based on" means both "based only on" and "based at least on."

[0168] As used in this disclosure, any reference to an element using a designation such as "first," "second," etc. does not generally limit the quantity or order of those elements. These designations may be used in this disclosure as a convenient method of distinguishing between two or more elements. Thus, a reference to a first and a second element does not imply that only two elements may be employed or that the first element must in some way precede the second element.

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

[0170] When the terms "include," "including," and variations thereof are used in this disclosure, these terms are intended to be inclusive, similar to the term "comprising." Furthermore, when the term "or" is used in this disclosure, it is not intended to be an exclusive or.

[0171] In this disclosure, where articles are added by translation, such as a, an, and the in English, the disclosure may include that the nouns following these articles are in the plural form.

[0172] In the present 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 "coupled" may also be interpreted in the same way as "different."

[0173] The aspects / embodiments described in this disclosure may be used alone, in combination, or switched depending on the implementation. Notification of predetermined information (e.g., notification that "X is true") is not limited to explicit notification, but may be implicit (e.g., not notifying the predetermined information).

[0174] Although the present disclosure has been described in detail above, it is 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 spirit and scope of the present disclosure as defined by the claims. Therefore, the description of the present disclosure is intended to be illustrative and does not have any limiting meaning on the present disclosure.

[0175] 10 Base station 110 Transmitter 120 Receiver 130 Setting unit 140 Control unit 20 Terminal 210 Transmitter 220 Receiver 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 wheels 2008 Rear wheels 2009 Axle 2010 Electronic control unit 2012 Information service unit 2013 Communication module 2021 Current sensor 2022 RPM sensor 2023 Tire pressure sensor 2024 Vehicle speed sensor 2025 Acceleration sensor 2026 Brake pedal sensor 2027 Shift lever sensor 2028 Object detection sensor 2029 Accelerator pedal sensor 2030 Driving assistance system unit 2031 Microprocessor 2032 Memory (ROM, RAM) 2033 Communication port (IO port)

Claims

1. A network node having: a receiving unit that receives, from another network node, a first message requesting deployment information including an identifier of a satellite, a list of identifiers of communication devices deployed on the satellite, and information regarding a range of IP (Internet Protocol) addresses to be assigned to terminals that use the satellite; and a transmitting unit that transmits, to the other network node, a second message including the deployment information.

2. The network node according to claim 1, wherein the receiving unit receives the list from a management device of another network.

3. A network node having: a receiving unit that receives a first message from a management device of another network, the first message including a satellite identifier and a list of identifiers of communication devices deployed on the satellite; and a second message from a management device of its own network, the second message including the satellite identifier and information regarding the range of IP (Internet Protocol) addresses to be assigned to terminals using the satellite; and a control unit that stores the satellite identifier, the list, and the information regarding the IP address range in association with each other.

4. A network node having a receiving unit that receives a first message sent by a terminal requesting the establishment of a session for a data network that handles voice calls, and receives a second message from a first network node instructing the use of a media gateway deployed on a satellite; a control unit that selects a second network node that controls the media gateway; and a transmitting unit that sends a third message to the terminal accepting the establishment of the session, the third message including the IP (Internet Protocol) address of the second network node.

5. The network node according to claim 4, wherein the receiving unit receives a fourth message from the first network node, the fourth message including information regarding a range of IP addresses that can be assigned to the terminal, and the control unit includes in the third message one IP address selected from the range and assigned to the terminal.

6. A network node having: a receiving unit that receives a first message requesting a voice call from a terminal; a control unit that identifies a satellite to which the terminal is connected based on the IP (Internet Protocol) address of the terminal included in the first message; and a transmitting unit that transmits a second message related to media processing in the voice call to a media gateway deployed on the satellite.

7. A base station having: a receiving unit that receives, from a first network node, a first message requesting initiation of interface establishment for exchanging information with the first network node; and a transmitting unit that transmits, to the first network node, a second message requesting the interface establishment.

Images