Network node and communication method

Abstract

This network node includes: a reception unit that receives, from a first network node, a first message requesting the determination of a policy and the transmission of the policy for a protocol data unit (PDU) session using a satellite constellation; a control unit that determines a policy for setting an uplink classifier (ULCL) and a user plane function on a satellite; and a transmission unit that transmits, to the first network node, a second message which includes a policy that includes a packet filter having no matching Internet Protocol (IP) packet, a name indicating an exit of the user plane function, and a route setting information identifier for a route to the exit of the user plane function.

Description

Network node and communication method

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

[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), reducing the impact on existing specifications when deploying 5GC network functions and IMS components on satellites is an issue (see, for example, Non-Patent Document 3). Here, terminal-satellite-terminal communication refers to terminal-to-terminal communication 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). Furthermore, for low Earth orbit satellites and medium Earth orbit satellites, satellite constellations can be formed without using inter-satellite links (ISLs) or using inter-satellite links.

[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.4.0 (2024-03) 3GPP TS 38.331 V18.0.0 (2023-12) 3GPP TS 38.413 V18.0.0 (2023-12) 3GPP TS 29.502 V18.5.0 (2023-12) 3GPP TS 29.512 V18.5.1 (2024-04) 3GPP TS 23.514 V18.5.0 (2024-03) 3GPP TS 23.571 V18.5.0 (2024-03)

[0007] In terminal-satellite-terminal communications, for example, when a satellite constellation is formed using inter-satellite links among low-earth-orbit satellites, each satellite is equipped with communication devices such as a base station, a user plane function (UPF), and an IMS access gateway (AGW). A configuration is being considered in which a base station, an uplink classifier (ULCL), and a local user plane function are deployed on the satellite, and a regular user plane function is deployed on the ground. When performing voice communications in this configuration, if an IMS AGW is used, the voice media is sent to the terrestrial UPF and IMS AGW. If an IMS AGW is not used, the voice media is sent to the satellite's UPF.

[0008] However, if the IMS AGW is not used in this configuration, the ULCL and UPF on the satellite must be configured, which increases the time required to set up a voice call.

[0009] The present invention has been made in view of the above points, and an object of the present invention is to reduce the time required for voice call setup in a wireless communication system when an IMS AGW is not used.

[0010] According to the disclosed technology, there is provided a network node having: a receiver that receives from a first network node a first message requesting policy determination and policy transmission for a Protocol Data Unit (PDU) session using a satellite constellation; a controller that determines a policy for setting an Uplink Classifier (ULCL) and a user plane function on the satellite; and a transmitter that transmits to the first network node a second message including a policy that includes a packet filter that does not match any IP (Internet Protocol) packets, a name indicating an exit for the user plane function, and an identifier of route setting information to the exit for the user plane function.

[0011] According to the disclosed technology, it is possible to reduce the time required for voice call setup in a wireless communication system when an IMS AGW is not used.

[0012] FIG. 1 is a diagram for explaining an example of a communication system. FIG. 1 is a diagram for explaining an example of a communication system in a roaming environment. FIG. 1 is a diagram for explaining an example of an IMS data channel network. FIG. 2 is a diagram showing an example of a first sequence diagram in an embodiment of the present invention. FIG. 3 is a diagram showing an example of a second sequence diagram in an embodiment of the present invention. FIG. 4 is a diagram showing an example of a fourth sequence diagram in an embodiment of the present invention. FIG. 5 is a diagram showing an example of a fifth sequence diagram in an embodiment of the present invention. FIG. 6 is a diagram showing an example of a sixth sequence diagram in an embodiment of the present invention. FIG. 7 is a diagram showing an example of a seventh sequence diagram in an embodiment of the present invention. FIG. 1 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. 2 is a diagram showing an example of the functional configuration of a terminal 20 in an embodiment of the present invention. FIG. 3 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. 4 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] In this embodiment, a satellite constellation is formed using an inter-satellite link (ISL) with multiple low-earth orbit satellites (LEOs) equipped with base stations, uplink classifiers (ULCLs), and local UPFs. The ULCLs have the function of selectively allocating uplink traffic between the N9 interfaces. An N2 intermediary, an ULCL gateway, and an extended N4 intermediary are deployed on the ground as intermediary devices that communicate with devices deployed in the multiple LEOs.

[0035] The N2 intermediary performs communication with the base station and communication with the AMF based on the interface (N2) between the base station and the AMF, i.e., the N2 intermediary acts as an AMF to the base station and as a base station to the AMF.

[0036] The enhanced N4 intermediary communicates with the UPF and with the SMF based on the interface (N4) between the UPF and the SMF. That is, the enhanced N4 intermediary acts as an SMF to the UPF and as a UPF to the SMF. The enhanced N4 intermediary also performs processing related to ULCL, which will be described later.

[0037] The intermediary device and the terminal connect to different LEOs depending on the time based on the satellite ephemeris, which is information indicating the relationship between the position of a satellite in its orbit and time.

[0038] Satellite communications operators prepare dedicated equipment for satellite constellation communications, primarily base stations, ULCLs, local UPFs, and intermediary devices deployed on the ground, while mobile communications operators prepare network nodes, such as AMFs, SMFs, and UPFs, deployed on the ground, as satellite constellation utilization equipment.

[0039] In this embodiment, the following procedure is executed to reduce the time required for voice call setup when the IMS AGW is not used.

[0040] First, after establishing an IMS PDU session, an ULCL and local UPF are established using an empty destination. Next, if an IMS AGW is not used when setting up a voice call, a ULCL filter is set up with the IP address of the remote terminal as the destination, simultaneously with the QoS flow setup procedure. The ULCL filter is also reconfigured on the destination network side. This filter is also called a traffic filter or packet filter. This makes it possible to shorten the time required for voice call setup compared to the existing method, which establishes an ULCL and local UPF after determining that an IMS AGW is not required.

[0041] The details of the processing in this embodiment will be described below using sequence diagrams. Requests, responses, notifications, and the like transmitted and received in the procedures described below may be referred to as messages (e.g., request messages). For details of existing specifications regarding the messages transmitted and received in this sequence diagram, see Non-Patent Documents 4-6. UPF 30A1, deployed on the ground, may be expressed as UPF(PSA1)30A1, serving as the first termination point (PDU Session Anchor 1, PSA1) in the PDU session. UPF 30A2 and UPF 30A3, deployed on satellites connected to the source and destination terminals, respectively, may be expressed as UPF(PSA2)30A2 and UPF(PSA3)30A3, serving as the second termination point (PSA2) and third termination point (PSA3) in the PDU session, respectively. Furthermore, UPF(PSA1) 30A1, UPF(PSA2) 30A2, and UPF(PSA3) 30A3 may be simply referred to as PSA1, PSA2, and PSA3, respectively.

[0042] (IMS PDU Session Establishment Procedure) The IMS PDU session establishment procedure in this embodiment will be described in detail using a sequence diagram. Fig. 4 is a diagram showing an example of a first sequence diagram in the embodiment of the present invention. The processing of each step will be described below.

[0043] S101: The terminal 20A transmits a request message requesting PDU session establishment to the base station 10A. The request message includes information indicating the PDU session establishment request and information related to the Data Network Name (DNN), and is expressed as, for example, ULInformationTransfer(dedicatedNAS-Message(UL NAS transport(Payload container type(N1 SM information), Payload container(PDU Session Establishment request), DNN=ims))).

[0044] S102: The base station 10A sends a request message requesting PDU session establishment to the N2 intermediary 30B. The request message includes information indicating the PDU session establishment request and information about the DNN, and is expressed as, for example, Uplink NAS Transport(NAS-PDU(UL NAS transport(Payload container type(N1 SM information), Payload container(PDU Session Establishment request), DNN=ims))).

[0045] S103: The N2 intermediary 30B sends the request message (Uplink NAS Transport) received in S102 to the AMF 30D.

[0046] S104: The AMF 30D recognizes that the request is from the terminal 20A under the satellite constellation (ID (identifier) ​​= aa) based on the base station identifier corresponding to the N2 intermediary 30B.

[0047] S105: The AMF 30D sends a request message requesting establishment of a PDU session to the SMF 30E. The request message includes the satellite constellation identifier (ID=aa) recognized in S104, information related to the DNN, and information indicating the PDU session establishment request, and is expressed as, for example, Nsmf_PDUSession_CreateSMContext request (SmContextCreateData (Dnn=ims, n1SmMsg (PDU session establishment request), satellite constellation ID=aa)).

[0048] S106: SMF30E sends a response message (Nsmf_PDUSession_CreateSMContext response) to the request message received in S105 to AMF30D.

[0049] S107: The SMF 30E sends a request message (Npcf_SMPolicyControl_Create request) to the PCF 30F to create a session management policy. The request message requests the determination and transmission of the policy. The request message also includes a PDU session identifier and a satellite constellation identifier (ID=aa), and is expressed as, for example, Npcf_SMPolicyControl_Create request (SmPolicyContextData(pduSessionId, satellite constellation ID=aa)).

[0050] S108: The PCF 30F determines that a policy for setting the ULCL and local UPF is required on the satellite for the satellite constellation (ID=aa).

[0051] S109: The PCF 30F instructs the SMF 30E to set a DNAI (Data Network Access Identifier) ​​for the satellite local UPF, UPF(PSA2) 30A2, regarding the destination of the empty IP packet. This setting can be performed based on existing specifications (see Non-Patent Documents 7 to 9, etc.).

[0052] S110: The PCF 30F sends a response message (Npcf_SMPolicyControl_Create response) to the request message received in S107 to the SMF 30E. The response message includes a policy that includes a packet filter to which no matching IP packets apply, a name indicating an exit point for the user plane function, and an identifier of route setting information to the exit point for the user plane function. The response message is expressed as, for example, Npcf_SMPolicyControl_Create response (SmPolicyDecision(PccRule(empty destination, DNAI=satellite constellation ID=aa satellite local UPF, routeProfId=satellite constellation ID=aa satellite local UPF profile), PccRule(default))).

[0053] S111: The SMF 30E determines to set the remote UPF, UPF (PSA1) 30A1, and also to set the ULCL 30A and UPF (PSA2) 30A2 on the satellite based on the instructions of the corresponding satellite local UPF profile.

[0054] S112: SMF30E sends a request message (PFCP Session Establishment request) to UPF(PSA1)30A1 to establish a user data transfer path.

[0055] S113: UPF (PSA1) 30A1 transmits to SMF 30E a response message (PFCP Session Establishment response) to the request message received in S112.

[0056] S114: The SMF30E sets the pre-stored IP (Internet Protocol) address (P-CSCF address=bb) of a special P-CSCF deployed on the ground that can handle the satellite IMS AGW as the P-CSCF address of the ePCO (extended Protocol Configuration Options).

[0057] S115: When the SMF 30E assigns an IP address to the terminal 20A that uses a satellite, it assigns it from the IP address range used by the satellite constellation with the identifier (ID=aa) received in S105.

[0058] S116: The SMF 30E transmits a message including information indicating acceptance of the PDU session establishment request to the AMF 30D. The message also includes the IP address of the terminal 20A and the IP address (=bb) of the P-CSCF, and is expressed as, for example, Namf_Communication_N1N2MessageTransfer request (N1N2MessageTransferReqData(n1MessageContainer(PDU Session Establishment accept(Extended protocol configuration options(P-CSCF address=bb))) n2InfoContainer(smInfo(n2InfoContent(PDU Session Resource Setup Request Transfer))))).

[0059] S117: The AMF 30D sends a response message to the SMF 30E in response to the request message received in S116.

[0060] S118: The AMF 30D sends a request message (PDU Session Resource Setup request) requesting the setting of a PDU session resource to the N2 intermediary 30B. The message also includes the IP address (=bb) of the P-CSCF, and is expressed as, for example, PDU Session Resource Setup request(NAS-PDU(DL NAS transport(Payload container type(N1 SM information), Payload container(PDU Session Establishment accept(Extended protocol configuration options(P-CSCF address=bb)))))).

[0061] S119: The N2 intermediary 30B transmits the request message (PDU Session Resource Setup request) received in S118 to the base station 10A.

[0062] S120: The base station 10A transmits a message including information indicating acceptance of the PDU session establishment request to the terminal 20A. The message also includes the IP address of the terminal 20A and the IP address (=bb) of the P-CSCF, and is expressed as, for example, RRCReconfiguration(dedicatedNAS-Message(DL NAS transport(Payload container type(N1 SM information), Payload container(PDU Session Establishment accept(Extended protocol configuration options(P-CSCF address=dd)))))).

[0063] S121: The base station 10A transmits a response message (PDU Session Resource Setup response) to the request message received in S119 to the N2 intermediary 30B.

[0064] S122: The N2 intermediary 30B sends a response message (PDU Session Resource Setup response) to the request message received in S118 to the AMF 30D.

[0065] S123: The AMF 30D sends a request message (Nsmf_PDUSession_UpdateSMContext request) requesting a PDU session context update to the SMF 30E. The request message is expressed as, for example, Nsmf_PDUSession_UpdateSMContext request (SmContextUpdateData(n2SmInfo(PDU Session Resource Setup Response Transfer))).

[0066] S124: SMF 30E sends a response message (Nsmf_PDUSession_UpdateSMContext response) to the request message received in S123 to AMF 30D.

[0067] S125: SMF30E sends a request message (PFCP Session Modification request) to UPF (PSA1) 30A1 to modify the user data transfer path.

[0068] S126: UPF (PSA1) 30A1 sends a response message (PFCP Session Modification response) to the request message received in S125 to SMF 30E.

[0069] (Procedure for adding a ULCL to an IMS PDU session) The procedure for adding a ULCL to an IMS PDU session in this embodiment will be described in detail using a sequence diagram. Figure 5 is a diagram showing an example of a second sequence diagram in the embodiment of the present invention. The processing of each step will be described below.

[0070] S201: The SMF 30E selects an N4 intermediary corresponding to the satellite constellation (ID=aa).

[0071] S202: SMF30E decides to transmit the identifier (PDU session ID) of the PDU session to facilitate operation within the satellite.

[0072] S203: The SMF 30E transmits a request message (PFCP Session Establishment request) to the enhanced N4 intermediary 30C, requesting establishment of a path for transferring uplink (UL) user data in the UPF (PSA2) 30B. The request message includes a PDU session identifier.

[0073] S204: The extended N4 intermediary 30C refers to a list of pairs of start time, end time, and destination UPF, which is created with reference to the satellite ephemeris, and selects the UPF (PSA2) 30A2.

[0074] S205: The enhanced N4 intermediary 30C transmits a request message (PFCP Session Establishment request) to the UPF (PSA2) 30A2 to request establishment of a path for transferring uplink user data (UL data). The request message includes a PDU session identifier.

[0075] S206: UPF (PSA2) 30A2 sends a response message (PFCP Session Establishment response) to the request message received in S205 to extended N4 intermediary 30C. The response message includes a packet detection rule (PDR) in which information indicating the UL data termination point (TEID for UL in PSA2) is set.

[0076] S207: The extended N4 intermediary 30C sends the response message (PFCP Session Establishment response) received in S206 to the SMF 30E.

[0077] S208: The SMF 30E transmits a first request message (PFCP Session Establishment request) to the enhanced N4 intermediary 30C, requesting establishment of a path for forwarding user data for UL to PSA2 in the ULCL 30A. The first request message includes a traffic filter for UL to PSA2, a forwarding action rule (FAR) in which a TEID for UL in PSA2 is set, a PDU session identifier, and ULCL indication information. The first request message is expressed as, for example, PFCP Session Establishment request (Traffic filter for UL to PSA2, FAR = TEID for UL in PSA2, PDU session ID, ULCL indication).

[0078] Furthermore, the SMF 30E transmits a second request message (PFCP Session Establishment request) to the enhanced N4 intermediary 30C, requesting the establishment of a path for transferring user data for the UL for PSA1. The second request message includes a traffic filter for the UL for PSA1, a FAR in which a TEID for the UL in PSA1 is set, a PDU session identifier, and ULCL indication information. The second request message is expressed as, for example, PFCP Session Establishment request (Traffic filter for UL to PSA1, FAR = TEID for UL in PSA1, PDU session ID, ULCL indication).

[0079] Furthermore, the SMF 30E transmits a third request message (PFCP Session Establishment request) to the enhanced N4 intermediary 30C, requesting establishment of a path for transferring UL user data to the base station 10 in the ULCL 30A. The third request message includes a PDU session identifier and ULCL indication information. The third request message is expressed as, for example, PFCP Session Establishment request (PDU session ID, ULCL indication).

[0080] Furthermore, the SMF 30E transmits a fourth request message (PFCP Session Establishment request) to the enhanced N4 intermediary 30C, requesting the establishment of a path for transferring DL user data in the ULCL 30A. The fourth request message includes a FAR in which the intra-base station 10 DL TEID is set, a PDU session identifier, and ULCL indication information. The fourth request message is expressed as, for example, a PFCP Session Establishment request (FAR = intra-gNB DL TEID, PDU session ID, ULCL indication).

[0081] S209: The extended N4 intermediary 30C refers to a list of pairs of start time, end time, and destination UPF, created with reference to the satellite ephemeris, and selects ULCL 30A. The extended N4 intermediary 30C may also refer to the PDU session identifier and ULCL display information received in S208 and select a UPF close to UPF (PSA2) 30A2 selected with the same PDU session identifier as ULCL 30A.

[0082] S210: The extended N4 intermediary 30C transmits the first to fourth request messages received in S208 to the ULCL 30A.

[0083] S211: ULCL 30A transmits first to fourth response messages (PFCP Session Establishment responses) to the extended N4 intermediary 30C in response to the first to fourth request messages received in S210. Here, the third response message includes a PDR in which the UL TEID in the ULCL is set. Also, the fourth response message includes a PDR in which the DL TEID in the ULCL is set.

[0084] The process following S211 will be described. 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 will be described below.

[0085] S212: The extended N4 intermediary 30C performs the configuration of the ULCL GW10Y in the subsequent processing in order to make the ULCL 30A appear to be a normal device rather than a satellite device with respect to DL user data in the UPF (PSA1) 30A1 (i.e., to conceal the ULCL switching due to satellite movement).

[0086] S213: The extended N4 intermediary 30C transmits a request message (PFCP Session Establishment request) to the ULCL GW 30Y to request establishment of a path for transferring DL data. The request message includes a FAR in which the TEID for DL ​​data within the ULCL is set and a PDU session identifier.

[0087] S214: The ULCL GW 30Y transmits a response message (PFCP Session Establishment response) to the request message received in S213 to the extended N4 intermediary 30C. The response message includes a PDR in which the intra-ULCL GW DL TEID is set and a PDU session identifier.

[0088] S215: The extended N4 intermediary 30C stores the association of the TEID for DL ​​in the ULCL and the TEID for DL ​​in the ULCL GW.

[0089] S216: The extended N4 intermediary 30C decides to swap the two TEIDs stored in S215.

[0090] S217: The enhanced N4 intermediary 30C transmits to the SMF 30E first to fourth response messages (PFCP Session Establishment responses) in response to the first to fourth request messages received in S208 of Fig. 5. Here, the third response message includes a PDR in which the UL TEID in the ULCL is set. Also, the fourth response message includes a PDR in which the DL TEID in the ULCL GW is set.

[0091] S218: The SMF30E recognizes the TEID for DL ​​within the ULCL GW as a normal TEID for DL ​​within the ULCL.

[0092] S219: The SMF 30E transmits to the UPF (PSA1) 30A1 a request message (PFCP Session Modification request) requesting a change in the setting of a path for transferring DL user data. The request message includes a FAR in which the intra-ULCL GW DL TEID is set and a PDU session identifier.

[0093] S220: UPF (PSA1) 30A1 sends a response message (PFCP Session Modification response) to the request message received in S219 to SMF 30E.

[0094] S221: The SMF 30E transmits a request message (PFCP Session Establishment request) to the extended N4 intermediary 30C to request the establishment of a path for transferring DL data. The request message includes a FAR in which the TEID for DL ​​within the ULCL GW is set and a PDU session identifier.

[0095] S222: The extended N4 intermediary 30C decides to replace the TEIDs replaced in S216 again.

[0096] S223: The extended N4 intermediary 30C transmits a request message (PFCP Session Establishment request) to the UPF (PSA2) 30A2 to request the establishment of a path for transferring DL data. The request message includes a FAR in which the TEID for DL ​​in the ULCL is set and a PDU session identifier.

[0097] S224: The UPF (PSA2) 30A2 transmits a response message (PFCP Session Establishment response) to the request message received in S223 to the extended N4 intermediary 30C.

[0098] S225: The extended N4 intermediary 30C sends a response message (PFCP Session Establishment response) to the request message received in S221 to the SMF 30E.

[0099] S226: SMF 30E sends a request message for updating the PDU session resource setup to AMF 30D. This message is expressed as, for example, Namf_Communication_N1N2MessageTransfer request (N1N2MessageTransferReqData(n2InfoContainer(smInfo(n2InfoContent(PDU Session Resource Setup Request Transfer))))).

[0100] S227: The AMF 30D sends a response message to the SMF 30E in response to the request message received in S226.

[0101] S228: AMF30D sends a request message (PDU Session Resource Modification request) to N2 intermediary 30B to update the PDU session resource settings.

[0102] S229: The N2 intermediary 30B transfers the request message received in S228 to the base station 10A.

[0103] S230: The base station 10A transmits to the N2 intermediary 30B a response message (PDU Session Resource Modification response) in response to the request message received in S229.

[0104] S231: The N2 intermediary 30B transfers the response message received in S230 to the AMF 30D.

[0105] S232: The AMF 30D sends a request message (Nsmf_PDUSession_UpdateSMContext request) requesting a PDU session context update to the SMF 30E. The request message is expressed as, for example, Nsmf_PDUSession_UpdateSMContext request (SmContextUpdateData(n2SmInfo(PDU Session Resource Setup Response Transfer))).

[0106] S233: SMF30E sends a response message (Nsmf_PDUSession_UpdateSMContext response) to the request message received in S232 to AMF30D.

[0107] (IMS Voice Call Procedure) The IMS voice call procedure in this embodiment will be described in detail using a sequence diagram. Fig. 7 is a diagram showing an example of a fourth sequence diagram in the embodiment of the present invention. The processing of each step will be described below.

[0108] S301: The terminal 20A sends a message (SIP INVITE) requesting an IMS voice call to the P-CSCF 30G.

[0109] S302: The P-CSCF 30G stores a list of IP address ranges used by terminals under the satellite constellation (ID=aa).

[0110] S303: The P-CSCF 30G recognizes from the IP address of the terminal 20A that the originating terminal is using the satellite constellation (ID=aa).

[0111] S304: P-CSCF30G adds the attribute "a=satellite: satellite constellation id=aa" indicating that the originating terminal 20A is under the control of the satellite constellation (ID=aa) to the setting information (SDP offer) in the message (SIP INVITE) received in S301.

[0112] S305: The P-CSCF 30G transmits to the IMS AGW 30H a request message (H.248 ADD request) requesting settings related to (addition of) voice communication control.

[0113] S306: The IMS AGW 30H acquires resources of the termination point on the device side related to data transmission with the destination network side.

[0114] S307: The IMS AGW 30H transmits to the P-CSCF 30G a response message (H.248 ADD response) in response to the request message received in S305.

[0115] S308: The P-CSCF30G transmits the message (SIP INVITE) received in S301 to the P-CSCF30G2 on the destination network side. This message includes the IP address of the termination point in the source network IMS AGW 30H in the "c=" line of the configuration information (SDP offer), and also includes the attribute information set in S304. This message is expressed, for example, as SIP INVITE (SDP offer (c=IP address of the termination point in the source network IMS AGW, a=satellite: satellite constellation id=aa)).

[0116] S309: The P-CSCF30G2 stores a list of IP address ranges used by terminals under the satellite constellation (ID=aa).

[0117] S310: The P-CSCF 30G2 recognizes from the IP address of the destination terminal 20B that the destination terminal 20B uses the satellite constellation (ID=aa).

[0118] S311: The P-CSCF 30G2 determines that the source terminal 20A and the destination terminal 20B belong to the same satellite constellation, and decides not to set up an IMS AGW.

[0119] S312: The P-CSCF 30G2 deletes the attribute "a=satellite: satellite constellation id=aa" related to the originating terminal 20A from the setting information (SDP offer) addressed to the destination terminal 20B.

[0120] S313: The P-CSCF 30G2 transmits a message (SIP INVITE) requesting the establishment of a voice communication path to the terminal 20B. The message includes the IP address of the termination point in the source network IMS AGW 30H in the “c=” line of the establishment information (SDP offer).

[0121] S314: The terminal 20B transmits to the P-CSCF 30G2 a message (SIP 183 Session Progress) indicating that the voice communication path is being set up. The message includes the IP address of the terminal 20B in the "c=" line of the setting information (SDP answer).

[0122] The process following S314 will be described. Fig. 8 is a diagram showing an example of a fifth sequence diagram according to an embodiment of the present invention. The process of each step will be described below.

[0123] S321: The P-CSCF 30G2 determines to use the UPF (PSA2) 30A2, which is a local UPF on the satellite, because the source terminal 20A and the destination terminal 20B are in the satellite constellation (ID=aa) and do not use the IMS AGW 30H. Furthermore, the P-CSCF 30G2 also determines to set route conditions in the voice media setting.

[0124] S322: The P-CSCF30G2 sends to the PCF30F2 a request message (Npcf_PolicyAuthorization_Create request) requesting policy configuration for QoS flow configuration for transmitting voice media. The request message includes a packet filter specifying the other-network termination point of the voice media as the destination IP address (the IP address of the termination point in the source network IMS AGW), a name indicating the exit of the local UPF, and an identifier of route configuration information to the exit of the local UPF. The request message is expressed as, for example, Npcf_PolicyAuthorization_Create request(AppSessionContext(AppSessionContextReqData(MediaComponent(AfRoutingRequirement(RouteToLocation(DNAI=satellite constellation ID=aa satellite local UPF, routeProfId=satellite constellation ID=aa satellite local UPF profile)), FlowInformation(IP address of the termination point whose destination is in the source network IMS AGW))))).

[0125] S323: The PCF 30F2 transmits to the P-CSCF 30G2 a response message (Npcf_PolicyAuthorization_Create response) in response to the request message received in S321.

[0126] S324: The PCF 30F2 sends a request message (Npcf_SMPolicyControl_UpdateNotify request) to the SMF 30E2 to update the session management policy. The request message includes a packet filter specifying the other network side termination point of the voice media as the destination IP address, a name indicating the exit of the local UPF, and an identifier of the route setting information to the exit of the local UPF. The request message is expressed as, for example, Npcf_SMPolicyControl_UpdateNotify request (SmPolicyNotification(smPolicyDecision(PccRule(IP address of the termination point in the IMS AGW whose destination is the source network, DNAI=satellite constellation ID=aa satellite local UPF, routeProfId=satellite constellation ID=aa satellite local UPF profile)))).

[0127] S325: The SMF 30E2 sends a response message (Npcf_SMPolicyControl_UpdateNotify response) to the request message received in S324 to the PCF 30F2.

[0128] S326: The SMF 30E2 sends the enhanced N4 intermediary 30C2 first and second request messages (PFCP Session Modification Request) requesting a change in the settings of the paths for transferring UL and DL user data. The first and second request messages include an updated QER (QoS Enforcement Rule).

[0129] S327: The extended N4 intermediary 30C2 sends the first and second request messages (PFCP Session Modification requests) received in S326 to the UPF (PSA3) 30A3.

[0130] S328: The UPF (PSA3) 30A3 sends to the extended N4 intermediary 30C2 first and second response messages (PFCP Session Modification responses) in response to the first and second request messages received in S327, respectively.

[0131] S329: The extended N4 intermediary 30C2 sends to the SMF 30E2 first and second response messages (PFCP Session Modification responses) to the first and second request messages received in S326, respectively.

[0132] S330: The SMF 30E2 transmits to the enhanced N4 intermediary 30C2 first to third request messages (PFCP Session Modification requests) requesting changes to the settings of paths for forwarding user data for UL to PSA3, UL from the base station, and DL. The first to third request messages include updated QoS Enforcement Rules (QERs). The first request message also includes a request to set the IP address of a termination point in the source network IMS AGW 30H in the UL traffic filter for PSA3.

[0133] S331: The extended N4 intermediary 30C2 transmits the first to third request messages (PFCP Session Modification requests) received in S330 to the ULCL 30X2.

[0134] S332: The ULCL 30X2 transmits to the extended N4 intermediary 30C2 first to third response messages (PFCP Session Modification responses) in response to the first to third request messages received in S331, respectively.

[0135] S333: The extended N4 intermediary 30C2 sends to the SMF 30E2 first to third response messages (PFCP Session Modification responses) in response to the first to third request messages received in S330, respectively.

[0136] S334: SMF 30E2 sends a request message for updating the PDU session resource settings to AMF 30D2. This message is expressed as, for example, Namf_Communication_N1N2MessageTransfer request (N1N2MessageTransferReqData (n2InfoContainer(smInfo(n2InfoContent(PDU Session Resource Modify Request Transfer))))).

[0137] S335: The AMF 30D2 sends a response message to the SMF 30E2 in response to the request message received in S334.

[0138] S336: AMF30D2 sends a request message (PDU Session Resource Modify request) to N2 intermediary 30B2 to update the PDU session resource settings.

[0139] S337: The N2 intermediary 30B2 transfers the request message received in S336 to the base station 10B.

[0140] S338: The base station 10B transmits a response message (PDU Session Resource Modify response) to the request message received in S337 to the N2 intermediary 30B2.

[0141] S339: The N2 intermediary 30B2 sends a response message (PDU Session Resource Modify response) to the request message sent in S336 to the AMF 30D2.

[0142] S340: AMF 30D2 sends a request message (Nsmf_PDUSession_UpdateSMContext request) to SMF 30E2 requesting a PDU session context update. The request message is expressed as, for example, Nsmf_PDUSession_UpdateSMContext request (SmContextUpdateData(n2SmInfo(PDU Session Resource Setup Response Transfer))).

[0143] S341: SMF30E2 sends a response message (Nsmf_PDUSession_UpdateSMContext response) to AMF30D2 in response to the request message received in S340.

[0144] The processing following S341 will now be described. Fig. 9 is a diagram showing an example of a sixth sequence diagram according to an embodiment of the present invention. The procedures shown in S351 to S377 are executed in parallel with the processing in the destination network shown in Fig. 8. The processing of each step will now be described.

[0145] S351: The P-CSCF30G2 adds the attribute “a=satellite: satellite constellation id=aa”, which indicates that the destination terminal 20B is under the control of the satellite constellation (ID=aa), to the setting information (SDP answer) included in the message (SIP 183 Session Progress) received in S314 of FIG. 7.

[0146] S352: The P-CSCF 30G2 sends a message (SIP 183 Session Progress) to the P-CSCF 30G on the source network side, indicating that the voice communication path is being set up. This message includes the IP address of the terminal 20B in the "c=" line of the setting information (SDP answer). This message also includes an attribute in the "a=" line of the setting information (SDP answer) indicating that the destination terminal 20B is under the control of the satellite constellation (ID=aa).

[0147] S353: The P-CSCF 30G determines that the source terminal 20A and the destination terminal 20B belong to the same satellite constellation, and decides to cancel the setting of the IMS AGW.

[0148] S354: The P-CSCF 30G transmits to the IMS AGW 30H a request message (H.248 SUBTRACT request) requesting settings related to the deletion of control of voice communication.

[0149] S355: The IMS AGW 30H deletes the setting performed based on the request message received in S305 of FIG.

[0150] S356: The IMS AGW 30H transmits to the P-CSCF 30G a response message (H.248 SUBTRACT response) in response to the request message received in S354.

[0151] S357: The P-CSCF 30G uses the local UPF on the satellite because the satellite constellation (ID=aa) does not use the IMS AGW. When setting the voice media, the route conditions are also set.

[0152] S358: The P-CSCF 30G sends the PCF 30F a request message (Npcf_PolicyAuthorization_Create request) requesting policy configuration for QoS flow configuration for transmitting voice media. The request message includes a packet filter specifying the other-network-side termination point of the voice media as the destination IP address (the IP address of the terminating terminal 20B), a name indicating the exit of the local UPF, and an identifier of route configuration information to the exit of the local UPF. The request message is expressed as, for example, Npcf_PolicyAuthorization_Create request(AppSessionContext(AppSessionContextReqData(MediaComponent(AfRoutingRequirement(RouteToLocation(DNAI=satellite constellation ID=aa satellite local UPF, routeProfId=satellite constellation ID=aa satellite local UPF profile)), FlowInformation(destination is the IP address of the terminating terminal 20B))))).

[0153] S359: The PCF 30F transmits to the P-CSCF 30G a response message (Npcf_PolicyAuthorization_Create response) in response to the request message received in S358. That is, the PCF 30F authorizes the policy included in the request message.

[0154] S360: The PCF 30F sends a request message (Npcf_SMPolicyControl_UpdateNotify request) to the SMF 30E to update the session management policy. The request message includes a packet filter that specifies the other-network-side termination point of the voice media as the destination IP address of the destination terminal 20B, a name indicating an exit point of the local UPF, and an identifier of route setting information to the exit point of the local UPF. The request message is expressed as, for example, Npcf_SMPolicyControl_UpdateNotify request (SmPolicyNotification(smPolicyDecision(PccRule(destination is the IP address of the destination terminal, DNAI=satellite constellation ID=aa satellite local UPF, routeProfId=satellite constellation ID=aa satellite local UPF profile)))).

[0155] S361: The SMF 30E sends to the PCF 30F a response message (Npcf_SMPolicyControl_UpdateNotify response) in response to the request message received in S360.

[0156] S362: The SMF 30E transmits to the enhanced N4 intermediary 30C first and second request messages (PFCP Session Modification Requests) requesting a change in the settings of the paths for transferring UL and DL user data. The first and second request messages include an updated QER (QoS Enforcement Rule).

[0157] S363: The extended N4 intermediary 30C transmits the first and second request messages (PFCP Session Modification requests) received in S362 to the UPF (PSA2) 30A2.

[0158] S364: The UPF (PSA2) 30A2 sends to the extended N4 intermediary 30C first and second response messages (PFCP Session Modification responses) to the first and second request messages received in S363, respectively.

[0159] S365: The enhanced N4 intermediary 30C sends to the SMF 30E first and second response messages (PFCP Session Modification responses) to the first and second request messages received in S362, respectively.

[0160] S366: The SMF 30E transmits to the enhanced N4 intermediary 30C first to third request messages (PFCP Session Modification requests) requesting changes to the settings of paths for forwarding user data for UL to PSA2, for UL originating from the base station, and for DL. The first to third request messages include updated QoS Enforcement Rules (QERs). The first request message also includes a request to set the IP address of the terminating terminal 20B in the UL traffic filter for PSA2.

[0161] S367: The extended N4 intermediary 30C transmits the first to third request messages (PFCP Session Modification requests) received in S366 to the ULCL 30X.

[0162] S368: The ULCL 30X transmits to the extended N4 intermediary 30C first to third response messages (PFCP Session Modification responses) in response to the first to third request messages received in S367, respectively.

[0163] S369: The extended N4 intermediary 30C sends to the SMF 30E first to third response messages (PFCP Session Modification responses) in response to the first to third request messages received in S366, respectively.

[0164] S370: SMF 30E sends a request message for updating the setting of PDU session resources to AMF 30D. This message is expressed as, for example, Namf_Communication_N1N2MessageTransfer request (N1N2MessageTransferReqData (n2InfoContainer(smInfo(n2InfoContent(PDU Session Resource Modify Request Transfer))))).

[0165] S371: The AMF 30D sends a response message to the SMF 30E in response to the request message received in S370.

[0166] S372: AMF30D sends a request message (PDU Session Resource Modify request) to N2 intermediary 30B to update the PDU session resource settings.

[0167] S373: The N2 intermediary 30B transfers the request message received in S372 to the base station 10A.

[0168] S374: The base station 10A transmits to the N2 intermediary 30B a response message (PDU Session Resource Modify response) to the request message received in S373.

[0169] S375: The N2 intermediary 30B sends a response message (PDU Session Resource Modify response) to the request message sent in S372 to the AMF 30D.

[0170] S376: AMF 30D sends a request message (Nsmf_PDUSession_UpdateSMContext request) requesting a PDU session context update to SMF 30E. This request message is expressed as, for example, Nsmf_PDUSession_UpdateSMContext request (SmContextUpdateData(n2SmInfo(PDU Session Resource Setup Response Transfer))).

[0171] S377: SMF30E sends a response message (Nsmf_PDUSession_UpdateSMContext response) to the request message received in S376 to AMF30D.

[0172] The process following S377 will now be described. Fig. 10 is a diagram showing an example of a seventh sequence diagram according to an embodiment of the present invention. The procedures shown in S381 to S397 are executed in parallel with the process in the source network shown in Fig. 9. The process of each step will now be described.

[0173] S381: The P-CSCF 30G deletes the attribute "a=satellite: satellite constellation id=aa" related to the destination terminal 20B from the setting information (SDP answer) addressed to the source terminal 20A.

[0174] S382: The P-CSCF 30G sends a message (SIP 183 Session Progress) to the terminal 20A indicating that the voice communication path is being set up. The message includes the IP address of the terminal 20B in the “c=” line of the setting information (SDP answer).

[0175] S383: The terminal 20A acquires the IP address of the destination terminal 20B from the message received in S382.

[0176] S384: The terminal 20A sends a message (PRACK / UPDATE) to the P-CSCF 30G requesting an update of the setting information of the voice communication path. The message includes the IP address of the terminal 20A in the "c=" line of the setting information (SDP offer).

[0177] S385: If terminal 20A does not send configuration information (SDP offer), i.e., if the message (PRACK / UPDATE) received in S384 does not include configuration information (SDP offer), P-CSCF30G generates configuration information (SDP offer) and includes it in the message (PRACK / UPDATE).

[0178] S386: The P-CSCF30G on the source network side sends a message (PRACK / UPDATE) to the P-CSCF30G2 on the destination network side, requesting an update of the voice communication path setting information. This message includes the IP address of the terminal 20A in the "c=" line of the setting information (SDP offer). This message also includes an attribute indicating that the source terminal 20A is under the control of the satellite constellation (ID=aa) in the "a=" line of the setting information (SDP answer).

[0179] S387: The P-CSCF 30G2 transmits a message (PRACK / UPDATE) requesting an update of the setting information of the voice communication path to the destination terminal 20B. The message includes the IP address of the terminal 20A in the “c=” line of the setting information (SDP offer).

[0180] S388: The terminal 20B acquires the IP address of the source terminal 20A from the message received in S387.

[0181] S389: The terminal 20B transmits to the P-CSCF 30G2 a response message (200 OK (PRACK / UPDATE)) in response to the message received in S387. The response message includes setting information (SDP answer) related to the voice communication path.

[0182] S390: P-CSCF30G2 sends a request message (Npcf_PolicyAuthorization_Update request) to PCF30F2 to update the packet filter settings. The request message includes a packet filter that specifies the other network side termination point of the voice media as the destination IP address (IP address of the source terminal), and is expressed as, for example, Npcf_PolicyAuthorization_Update request (AppSessionContextUpdateDataPatch (AppSessionContextUpdateData (MediaComponent (FlowInformation (destination is the IP address of the source terminal))))).

[0183] S391: The PCF 30F2 transmits to the P-CSCF 30G2 a response message (Npcf_PolicyAuthorization_Update response) in response to the request message received in S390.

[0184] S392: The PCF 30F2 sends a request message (Npcf_SMPolicyControl_UpdateNotify request) to the SMF 30E2 to update the session management policy. The request message includes a packet filter that specifies the other-network-side termination point of the voice media as the IP address of the source terminal (i.e., a packet filter with content different from the packet filter received in S324), a name indicating an exit point of the local UPF, and an identifier of route setting information to the exit point of the local UPF. The request message is expressed, for example, as Npcf_SMPolicyControl_UpdateNotify request (SmPolicyNotification (smPolicyDecision(PccRule(PccRule id, destination is the IP address of the source terminal, DNAI = satellite constellation ID = aa satellite local UPF, routeProfId = satellite constellation ID = aa satellite local UPF profile)))).

[0185] S393: The SMF 30E2 sends a response message (Npcf_SMPolicyControl_UpdateNotify response) to the request message received in S392 to the PCF 30F2.

[0186] S394: The SMF 30E2 sends a request message (PFCP Session Modification request) to the enhanced N4 intermediary 30C2 to modify the user data forwarding path. The request message includes a traffic filter for UL to PSA3, a name indicating the exit of the local UPF, and an identifier of the path setting information to the exit of the local UPF, and is expressed as, for example, PFCP Session Modification request (Traffic filter for UL to PSA3 (related to the IP address of the originating terminal)).

[0187] S395: The extended N4 intermediary 30C2 transmits the request message (PFCP Session Modification request) received in S394 to the ULCL 30X2.

[0188] S396: The ULCL 30X2 sends a response message (PFCP Session Modification response) to the request message received in S395 to the extended N4 intermediary 30C2.

[0189] S397: The extended N4 intermediary 30C2 sends a response message (PFCP Session Modification response) to the request message received in S394 to the SMF 30E2.

[0190] The procedures shown in S398 to S405 are executed in parallel with the processing in the destination network.

[0191] S398: The P-CSCF 30G2 on the destination network side transmits a response message (200 OK) to the P-CSCF 30G on the source network side in response to the message received in S389.

[0192] S399: The P-CSCF 30G transmits the message (200 OK) received in S398 to the terminal 20A.

[0193] S400: The terminal 20B transmits a success response (SIP 200 OK) to the P-CSCF 30G2.

[0194] S401: The P-CSCF 30G2 on the destination network side transmits the success response (SIP 200 OK) received in S400 to the P-CSCF 30G on the source network side.

[0195] S402: The P-CSCF 30G transmits the success response (SIP 200 OK) received in S401 to the terminal 20A.

[0196] S403: The terminal 20A transmits to the P-CSCF 30G an acknowledgement (Ack) in response to the success response (SIP 200 OK) received in S402.

[0197] S404: The P-CSCF 30G on the source network side transmits the acknowledgement (Ack) received in S403 to the P-CSCF 30G2 on the destination network side.

[0198] S405: The P-CSCF 30G2 transmits the acknowledgement (Ack) received in S404 to the destination terminal 20B.

[0199] S406: Voice communication is established between the calling terminal 20A and the called terminal 20B via the UPF without using the IMS AGW.

[0200] According to the above-described embodiment, it is possible to reduce the time required for voice call setup in a wireless communication system when an IMS AGW is not used.

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

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

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

[0204] The setting unit 130 stores preset setting information and various setting information to be transmitted to the terminal 20 in a storage device, and reads out the information from the storage device as needed.

[0205] The control unit 140 performs the processes described in the embodiments, etc. The control unit 140 also performs processes 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.

[0206] <Terminal 20> Fig. 12 is a diagram showing an example of the functional configuration of the terminal 20. As shown in Fig. 12, 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. 12 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, a communication device that becomes a resource holder 20 may have the same functional configuration as the terminal 20.

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

[0208] 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 out from the storage device as needed. The setting unit 230 also stores setting information that is set in advance.

[0209] The control unit 240 performs the processes described in the embodiments. 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.

[0210] (Hardware Configuration) The block diagrams (FIGS. 11 and 12) 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 be realized by combining software with the single device or the multiple devices.

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

[0212] 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. 13 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.

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

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

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

[0216] Furthermore, the processor 1001 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. 11 may be implemented by a control program stored in the storage device 1002 and running on the processor 1001. Furthermore, for example, the control unit 240 of the terminal 20 shown in FIG. 12 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.

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

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

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

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

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

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

[0223] Fig. 14 shows an example configuration of a vehicle 2001. As shown in Fig. 14, 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.

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

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

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

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

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

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

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

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

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

[0233] <Additional Notes> (Additional Note 1) A network node having: a receiving unit that receives, from a first network node, a first message requesting the determination of a policy and the transmission of the policy regarding a Protocol Data Unit (PDU) session using a satellite constellation; a control unit that determines a policy for setting an Uplink Classifier (ULCL) and a user plane function on the satellite; and a transmitting unit that transmits, to the first network node, a second message including a policy that includes a packet filter that does not match any IP (Internet Protocol) packets, a name indicating an exit for the user plane function, and an identifier of route setting information to the exit for the user plane function. (Supplementary Item 2) The network node according to Supplementary Item 1, wherein the receiver receives from a second network node a third message requesting setting of a policy for the PDU session, the policy including the packet filter specifying a destination IP address, the name, and an identifier of the route setting information, the controller authorizing setting of the policy included in the third message, and the transmitter transmits to the first network node a fourth message including a policy including the packet filter to which the same identifier as the identifier of the policy included in the second message is assigned, the name, and the identifier of the route setting information. (Supplementary Item 3) The network node according to Supplementary Item 1, wherein the network node comprises: a receiver that receives from the first network node a first message including a policy including a packet filter, a name indicating an exit of a user plane function, and an identifier of route setting information to the exit of the user plane function, and a transmitter that transmits to the second network node a second message requesting packet forwarding setting, the second message including the packet filter, the second message being addressed to an uplink classifier (ULCL) on a satellite, based on route setting information to the exit of the user plane function that is preset in the network node.(Supplementary Item 4) The network node according to Supplementary Item 3, wherein the receiving unit receives from the first network node a third message including a policy including a packet filter having content different from the packet filter and having the same identifier as the identifier of the policy included in the first message assigned thereto, the policy including the name and an identifier of the route setting information, and the transmitting unit transmits to the second network node a fourth message requesting an update of packet forwarding settings including the packet filter addressed to a ULCL on a satellite. (Supplementary Item 5 ... A network node comprising: a control unit that determines to use a user plane function on a satellite for transmission of voice media; and a transmitting unit that transmits to the first network node a message requesting setting of a policy including a packet filter having a destination IP address that is a termination point on the other network side of the voice media, a name that indicates an exit point of the user plane function, and an identifier of route setting information to the exit point of the user plane function. (Supplementary Item 6) A communication method executed by a network node, comprising: receiving a first message from a first network node requesting policy determination and policy transmission for a PDU (Protocol Data Unit) session using a satellite constellation; determining a policy for setting an ULCL (Uplink Classifier) ​​and a user plane function on the satellite; and transmitting a second message to the first network node including a policy that includes a packet filter that does not match any IP (Internet Protocol) packets, a name indicating an exit for the user plane function, and an identifier of route setting information to the exit for the user plane function.

[0234] Any of Supplementary Items 1 to 6 can reduce the time required for voice call setup in a wireless communication system when an IMS AGW is not used.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0269] 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 receiver that receives from a first network node a first message requesting the determination of a policy and the transmission of the policy regarding a Protocol Data Unit (PDU) session using a satellite constellation; a controller that determines a policy for setting an Uplink Classifier (ULCL) and a user plane function on the satellite; and a transmitter that transmits to the first network node a second message including a policy that includes a packet filter that does not match any IP (Internet Protocol) packets, a name indicating an exit for the user plane function, and an identifier of route setting information to the exit for the user plane function.

2. The network node described in claim 1, wherein the receiving unit receives from the second network node a third message requesting the setting of a policy for the PDU session, the policy including the packet filter specifying a destination IP address, the name, and an identifier of the route setting information; the control unit approves the setting of the policy included in the third message; and the transmitting unit transmits to the first network node a fourth message including a policy including the packet filter to which an identifier identical to the identifier of the policy included in the second message has been assigned, the name, and an identifier of the route setting information.

3. A network node having: a receiving unit that receives from a first network node a first message including a policy that includes a packet filter, a name indicating an exit point for a user plane function, and an identifier of route setting information to the exit point for the user plane function; and a transmitting unit that transmits to a second network node a second message that requests packet forwarding setting, including the packet filter, addressed to an ULCL (Uplink Classifier) ​​on a satellite, based on route setting information to the exit point for the user plane function that has been pre-set within the device.

4. The network node according to claim 3, wherein the receiver receives from the first network node a third message including a policy including a packet filter having different content from the packet filter and having the same identifier as the identifier of the policy included in the first message, the name, and an identifier of the route setting information, and the transmitter transmits to the second network node a fourth message requesting an update of packet forwarding settings including the packet filter addressed to the ULCL on the satellite.

5. A network node having: a control unit that determines to use a user plane function on a satellite for transmitting voice media; and a transmission unit that transmits a message to a first network node requesting the setting of a policy including a packet filter that specifies the other network side termination point of the voice media as the destination IP address, a name indicating an exit point of the user plane function, and an identifier of route setting information to the exit point of the user plane function.

6. A communication method executed by a network node, comprising the steps of: receiving a first message from a first network node requesting policy determination and policy transmission for a Protocol Data Unit (PDU) session using a satellite constellation; determining a policy for configuring an Uplink Classifier (ULCL) and a user plane function on the satellite; and transmitting a second message to the first network node including a policy that includes a packet filter that does not match any IP (Internet Protocol) packets, a name indicating an exit for the user plane function, and an identifier of route setting information to the exit for the user plane function.

Images