Network node

Abstract

This network node comprises: a reception unit which receives, from a device of an intermediary business operator, a first message which requests creation of a session and includes capability information indicating that capability regarding a change in service conditions in communication between different networks is supported; and a transmission unit which transmits, to a first network node, a second message which requests the creation of the session and includes the capability information. The reception unit receives, from the first network node and as a response to the second message, a third message including the capability information. The transmission unit transmits, to the device of the intermediary business operator and as a response to the first message, a fourth message including the capability information. The reception unit receives, from the first network node, a fifth message requesting subscription regarding the change in the service conditions. When the reception unit has received, from the device of the intermediary business operator, a notification regarding the change in the service conditions, the transmission unit transmits the notification to the first network node.

Description

Network Node

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

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

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

[0004] 3GPP TS 23.501 V18.3.0 (2023-09)3GPP TS 23.502 V18.3.0 (2023-09)

[0005] In 5GC, N32 is specified as the interface between network operators, and when a network function (NF) communicates between a visited public land mobile network (VPLMN) and a home network (PLMN), an N32 connection is established between the Security Endpoint Protocol Proxy (SEPP) located at the boundary between the respective networks.

[0006] However, with the existing specifications, it is not possible to execute processing related to communication in N32 based on a trigger detected by the device of the intermediary business.

[0007] The present invention has been made in consideration of the above points, and aims to enable a communication system to execute processing related to communication between different networks based on a trigger detected by an intermediary operator's device.

[0008] According to the disclosed technology, there is provided a network node including: a receiving unit that receives, from a relay carrier device, a first message requesting the creation of a session, the first message including capability information indicating that the relay carrier device supports a capability related to a change in service conditions in communication between different networks; and a transmitting unit that transmits, to a first network node, a second message requesting the creation of the session, the second message including the capability information, wherein the receiving unit receives, from the first network node, a third message including the capability information as a response to the second message; the transmitting unit transmits, to the relay carrier device, a fourth message including the capability information as a response to the first message; the receiving unit receives, from the first network node, a fifth message requesting a subscription related to the change in service conditions; and, when the receiving unit receives from the relay carrier device a notification related to the change in service conditions, the transmitting unit transmits the notification to the first network node.

[0009] According to the disclosed technology, in a communication system, it is possible to execute processing related to communication between different networks based on a trigger detected by an intermediary device.

[0010] 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. 2 is a diagram for explaining the flow of signals between network operators. FIG. 3 is a diagram for explaining an overview of an embodiment of the present invention. FIG. 4 is a diagram for explaining an example of a sequence diagram relating to a first method in an embodiment of the present invention. FIG. 5 is a diagram for explaining an example of a sequence diagram relating to a modified version of the first method in an embodiment of the present invention. FIG. 6 is a diagram for explaining an example of a sequence diagram relating to a second method in an embodiment of the present invention. FIG. 7 is a diagram for explaining an example of a sequence diagram relating to a third method in an embodiment of the present invention. FIG. 8 is a diagram for explaining an example of a sequence diagram relating to a fourth method in an embodiment of the present invention. FIG. 9 is a diagram for explaining an example of a first service in an embodiment of the present invention. FIG. 10 is a diagram for explaining an example of a second service in an embodiment of the present invention. FIG. 11 is a diagram for explaining an example of a functional configuration of a base station 10 and a network node 30 in an embodiment of the present invention. FIG. 12 is a diagram for explaining an example of a functional configuration of a terminal 20 in an embodiment of the present invention. FIG. 13 is a diagram for explaining 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. 14 is a diagram for explaining an example of the configuration of a vehicle 2001 in an embodiment of the present invention.

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

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

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

[0014] Fig. 1 is a diagram illustrating an example of a communication system. As shown in Fig. 1, the communication system is composed of a terminal 20 (User Equipment (UE)) 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.

[0015] 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), registration management, connection management, reachability management, and mobility management. The UPF is a network node 30 having functions such as a PDU (Protocol Data Unit) session point to the outside that interconnects with a DN (Data Network), packet routing and forwarding, and user plane QoS (Quality of Service) 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.

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

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

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

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

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

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

[0022] 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 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. Although Figure 2 shows a local breakout topology in which a UPF connects to a DN in the VPLMN, a home routed topology in which a UPF connects to a DN in the HPLMN may also be used.

[0023] Figure 3 is a diagram explaining the flow of signals between network operators. As shown in Figure 3, an NF (which may be referred to as an NF consumer, NFc, cNF, etc.) using the services of an NF in another network, an HPLMN, from a VPLMN uses an API (Application Interface) provided by the NF (which may be referred to as an NF producer, NFp, pNF, etc.) in the HPLMN via N32-f, which is established between the SEPPs of both networks via N32-c. This enables queries to the NRF to discover the NF to communicate with, authentication by the AUSF, status registration (e.g., location) and acquisition of subscriber information in the UDM, and session creation, update, and termination with the SMF. The SEPP in the VPLMN may be referred to as an Initiating SEPP or consumer SEPP (cSEPP), etc., and the SEPP in the HPLMN may be referred to as a Responding SEPP or producer SEPP (pSEPP), etc. Furthermore, the SMF in the VPLMN may be referred to as a vSMF, and the SMF in the HPLMN may be referred to as an hSMF. Additionally, N32-c and N32-f may be collectively referred to as N32.

[0024] N32-c is an interface that exchanges security capabilities between the cSEPP and pSEPP.

[0025] N32-f is an interface that ensures security between the cSEPP and pSEPP in communications between the cNF and pNF. When TLS (Transport Layer Security) is used in N32-f, HTTP signals are sent over a TLS-encrypted layer. When PRINS (Protocol for N32 Interconnect Security) is used in N32-f, it is possible to provide additional services by instructing an intermediary to change some parameters when relaying signals.

[0026] The existing specifications are designed so that signals are relayed by SEPPs located at both ends of N32 between network operators. While relay operators can adjust the values ​​in the relayed signals based on PRINS, they cannot change the provision conditions based on conditions detected by the relay operators. Therefore, relay operators cannot provide additional services on behalf of network operators, such as limiting communication bandwidth after a specified data volume is exceeded or controlling the start and stop of data communication during roaming.

[0027] (First embodiment) A first embodiment will be described. In the first embodiment, a procedure for executing a process related to communication between different networks in a communication system based on a trigger detected by an apparatus of an intermediary company will be described.

[0028] FIG. 4 is a diagram illustrating an overview of an embodiment of the present invention. In FIG. 4, cSEPP 30A, AMF 30C, vSMF 30D, and UPF 30E are network nodes on the VPLMN side, and pSEPP 30B, UDM 30F, hSMF 30G, and UPF 30H are network nodes on the HPLMN side. Furthermore, the terminal 20 connects to the AMF 30C and UPF 30E in the VPLMN. In this embodiment, the relay carrier detects a condition as a trigger, and the terms of the service provided can be changed. For example, the relay carrier's device on the N32-f interface specified in PRINS can autonomously insert a signal. Alternatively, a new API can be specified or an attribute can be added to some existing NFs (such as SMFs and UDMs), and QoS information can be changed or disconnected for existing sessions, maintaining the same state between the VPLMN and the HPLMN. Note that the same NFs in the VPLMN and the HPLMN may have some different functions.

[0029] Below, we will explain four methods that take into consideration the introduction of new signals required to achieve the above-mentioned operations and the reduction of the impact on network functions (NFs) in existing 3GPP specifications.

[0030] (First Method) In the first method, as a newly defined NF service function, an intermediary acts on behalf of the hSMF 30G in the HPLMN to update and modify service conditions, etc. The network functions that are changed from the existing specifications are the cSEPP 30A, pSEPP 30B, hSMF 30G, and Intermediary. The Intermediary adds information (a flag) indicating a new capability for executing the function to the PDU session creation request (Create PDU Session). If the pSEPP 30B supports the new capability, it forwards the received flag to notify the hSMF 30G that it supports the new capability. The hSMF 30G requests the pSEPP 30B to subscribe to notifications of changes to the service conditions. When an update to the service conditions is required, the Intermediary notifies the vSMF 30D of the update. This notification is the same as the notification from hSMF30G to vSMF30D in the existing specifications, but in order for the Intermediary to execute the notification, it is necessary to generate a signal (Empty Reformatted data) in N32-f. The Intermediary sends this signal to cSEPP30A. The cSEPP30A sends a change notification (Notify) corresponding to the subscription (Subscribe) to hSMF30G.

[0031] 5 is a diagram showing an example of a sequence diagram relating to the first method in the embodiment of the present invention. The processing of each step in FIG. 5 will be described below. Note that the cSEPP 30A, pSEPP 30B, hSMF 30G, and Intermediary support the new function.

[0032] S101: N32-f is established between cSEPP30A and pSEPP30B.

[0033] S102: The terminal 20 transmits a message requesting establishment of a PDU session to the vSMF 30D via the AMF 30C. For details of the request, see section 4.3 of Non-Patent Document 2 (the same applies to the subsequent sequence diagrams).

[0034] S103: The vSMF 30D sends a message (Nsmf (Create PDU session)) requesting the creation of a PDU session to the cSEPP 30A. For details of this request, see section 4.3 of Non-Patent Document 2 (the same applies to the subsequent sequence diagrams).

[0035] S104: cSEPP30A transmits a request message (HTTP POST (N32RefomattedReqMsg)) on N32-f, including the message received in S103, to pSEPP30B via IntermediaryA and IntermediaryB, which are intermediaries.

[0036] S105: Intermediary B adds a flag indicating that it supports the ability to change the service conditions to the message sent in S104, and sends the message with the added flag to pSEPP30B. pSEPP30B recognizes that Intermediary B supports the ability.

[0037] S106: pSEPP 30B sends to hSMF 30G a message (Nsmf (Create PDU session)) requesting the creation of a PDU session, which is included in the message received in S105. The message includes a flag indicating that the capability to change service conditions is supported. hSMF 30G recognizes that Intermediary B and pSEPP 30B support this capability.

[0038] S107: The hSMF 30G sends a 200 OK to the pSEPP 30B as a response message to the message received in S106. The response message includes a flag indicating that the capability to change the service conditions is supported. The pSEPP 30B recognizes that the hSMF 30G supports the capability.

[0039] S108: The hSMF 30G sets information about the quality of service (QoS) corresponding to the PDU session related to the message received in S106. Here, the quality of service (QoS) information is set in accordance with the service conditions, such as the allowable user plane communication speed. The same applies to the setting of QoS information in the first to fourth methods.

[0040] S109: The hSMF 30G sends a message to the pSEPP 30B requesting a subscription to change the QoS information (service conditions). The pSEPP 30B accepts the subscription.

[0041] S110: The pSEPP 30B sends a 200 OK to the hSMF 30G as a response message to the message received in S109.

[0042] S111: pSEPP 30B sends a response message (N32RefomattedRspMsg) on ​​N32-f, including the 200 OK received in S107, to cSEPP 30A via Intermediary A and Intermediary B. The response message includes a flag indicating that it supports the capability to change the service conditions. Intermediary B recognizes that pSEPP 30B and hSMF 30G support the capability.

[0043] S112: Intermediary B transfers the message sent in S111 to pSEPP 30A.

[0044] S113: The cSEPP 30A sends a 200 OK to the vSMF 30D as a response message to the message received in S103.

[0045] S114: The vSMF 30D sets information related to the quality of service (QoS) corresponding to the PDU session related to the message sent in S103.

[0046] Thereafter, subsequent processing in the existing specifications regarding the establishment of the PDU session (see Section 4.3 of non-patent document 2) is performed between vSMF30D, AMF30C, and terminal 20.

[0047] S115: Intermediary B recognizes that a PDU session will be established based on the message received in S111, and sends a message to the communication traffic monitoring device that monitors the user plane communication traffic, instructing it to monitor the user plane communication traffic related to the PDU session.

[0048] S116: The traffic monitoring device detects that the traffic of the user plane that it has been instructed to monitor has exceeded a predetermined amount.

[0049] S117: The traffic monitoring device sends a message to Intermediary B notifying that an excess of traffic volume has been detected.

[0050] S118: Intermediary B sends a message (N32-f Error Reporting) on ​​N32-f to cSEPP30A requesting an update of the PDU session to change the QoS information (service conditions).

[0051] S119: cSEPP30A sends a message (Nsmf (Update PDU session)) to vSMF30D requesting an update of the PDU session.

[0052] S120: The vSMF 30D sends a 200 OK to the cSEPP 30A as a response message to the message received in S119.

[0053] S121: The vSMF 30D sets information related to the quality of service (QoS) corresponding to the update of the PDU session related to the message received in S119. For example, the vSMF 30D changes the allowable user plane communication speed set in S114 to a lower communication speed (i.e., performs a bandwidth restriction related to the communication speed).

[0054] Thereafter, subsequent processing in the existing specifications regarding updating the PDU session (see Section 4.3 of non-patent document 2) is performed between vSMF30D, AMF30C, and terminal 20.

[0055] S122: cSEPP30A sends to IntermediaryB a response message (N32RefomattedRspMsg) on ​​N32-f, including the 200 OK received in S120.

[0056] S123: IntermediaryB transmits a message (N32-f Error Reporting) on ​​N32-f to pSEPP30B requesting a change in QoS information (service conditions).

[0057] S124: The pSEPP 30B sends a notification to the hSMF 30G regarding the subscription accepted in S109.

[0058] S125: The hSMF 30G sends a 200 OK to the pSEPP 30B as a response message to the message received in S124.

[0059] S126: The hSMF 30G sets information related to the quality of service (QoS) corresponding to the update of the PDU session related to the notification received in S124. For example, the hSMF 30G changes the allowable user plane communication speed set in S108 to a lower communication speed.

[0060] S127: pSEPP30B sends 200 OK to IntermediaryB as a response message to the message received in S123.

[0061] (Modification of the First Method) A modification of the first method will be described. In this modification, processing will be described for the case where the hSMF 30G does not support the ability to change service conditions. The network functions that have been modified from the existing specifications are the cSEPP 30A, pSEPP 30B, and Intermediary.

[0062] 6 shows an example of a sequence diagram relating to a variation of the first method according to an embodiment of the present invention. In this variation, unlike the sequence diagram of the first method, the messages sent in S107 and S111 do not include a flag indicating that the ability to change service conditions is supported. Furthermore, steps S109, S110, and S123-S127, which are processes between Intermediary B, pSEPP 30B, and hSMF 30G, are not executed. Therefore, only the QoS information on the VPLMN side is changed, and the service conditions are changed based on this change.

[0063] (Second Method) In the second method, a newly defined NF service function changes the quality of service (QoS) value in the subscriber information (Subscription data) stored by the UDM30F. The network functions that are changed from the existing specifications are the pSEPP30B, the UDM30F, and the Intermediary. After completing PDU session generation (Create PDU Session) using the same procedure as in the existing specifications, the Intermediary acquires current subscriber information from the UDM30F via the pSEPP30B. The reason the Intermediary acquires the current subscriber information is that by retaining the information before the change, it is possible to restore the QoS information changed in subsequent processing to the information before the change. When it becomes necessary to change the QoS information, the Intermediary instructs the UDM30F to change the QoS information in the subscriber information via the pSEPP30B. Subsequently, based on the processing in the existing specifications, the UDM30F sends an instruction to the hSMF30G to change the QoS information for the PDU session, and then the instruction is notified to the vSMF30D, thereby updating the QoS information.

[0064] 7 is a diagram showing an example of a sequence diagram relating to the second method according to an embodiment of the present invention. The processing of each step in FIG. 7 will be described below. Note that pSEPP 30B, UDM 30F, and Intermediary support the new function.

[0065] S201: N32-f is established between cSEPP30A and pSEPP30B.

[0066] S202: The terminal 20 sends a message to the vSMF 30D via the AMF 30C requesting the establishment of a PDU session.

[0067] S203: vSMF30D sends a message (Nsmf (Create PDU session)) to cSEPP30A requesting the creation of a PDU session.

[0068] S204: cSEPP30A transmits a request message (HTTP POST (N32RefomattedReqMsg)) on N32-f including the message received in S203 to pSEPP30B via IntermediaryA and IntermediaryB, which are intermediaries.

[0069] S205: IntermediaryB transfers the message sent in S204 to pSEPP30B.

[0070] S206: pSEPP 30B sends to hSMF 30G a message (Nsmf (Create PDU session)) requesting the creation of a PDU session, which is included in the message received in S205.

[0071] S207: The hSMF 30G sends a 200 OK to the pSEPP 30B as a response message to the message received in S206.

[0072] S208: The hSMF 30G sets information about the quality of service (QoS) corresponding to the PDU session related to the message received in S206.

[0073] S209: pSEPP 30B transmits a response message (N32RefomattedRsqMsg) on ​​N32-f, including the 200 OK received in S207, to cSEPP 30A via Intermediary A and Intermediary B.

[0074] S210: Intermediary B transfers the message sent in S209 to cSEPP 30A.

[0075] S211: The cSEPP 30A sends a 200 OK to the vSMF 30D as a response message to the message received in S203.

[0076] S212: The vSMF30D sets information related to the quality of service (QoS) corresponding to the PDU session related to the message sent in S203.

[0077] Thereafter, subsequent processing in the existing specifications regarding the establishment of the PDU session (see Section 4.3 of non-patent document 2) is performed between vSMF30D, AMF30C, and terminal 20.

[0078] S213: Intermediary B recognizes that a PDU session will be established based on the message received in S209, and sends a message to the communication traffic monitoring device that monitors the user plane communication traffic, instructing it to monitor the user plane communication traffic related to the PDU session.

[0079] S214: Intermediary B sends a message (N32-f Error Reporting) on ​​N32-f to pSEPP30B, which includes a message requesting acquisition of subscriber information. The subscriber information includes information about service quality.

[0080] S215: The pSEPP 30B sends to the UDM 30F a message (Nudm_SDM_Get) requesting acquisition of the subscriber information included in the message received in S214.

[0081] S216: The UDM 30F sends to the pSEPP 30B a response message (200 OK) including the subscriber information requested in the message received in S215.

[0082] S217: pSEPP 30B sends the response message (200 OK) received in S216 to Intermediary B. Intermediary B saves the subscriber information included in the received response message.

[0083] S218: The traffic monitoring device detects that the traffic of the user plane that it is instructed to monitor has exceeded a predetermined amount.

[0084] S219: The traffic monitoring device sends a message to Intermediary B notifying that an excess of traffic volume has been detected.

[0085] S220: IntermediaryB sends to pSEPP30B a message (N32-f Error Reporting) on ​​N32-f, which includes a message requesting an update of subscriber information (change of QoS information) to change the service conditions (bandwidth limit of communication speed).

[0086] S221: The pSEPP 30B sends to the UDM 30F a message (Nudm (New Update)) requesting an update of the subscriber information, which is included in the message received in S220. The UDM 30F updates the subscriber information in accordance with the received message.

[0087] S222: The UDM 30F sends to the pSEPP 30B a response message (200 OK) notifying that the update of the subscriber information requested in the message received in S221 has been completed.

[0088] S223: The pSEPP30B transmits the response message (200 OK) received in S221 to IntermediaryB.

[0089] S224: The UDM 30F transmits to the hSMF 30G a notification requesting a change in QoS information in accordance with the subscriber information changed in S221. The transmission of this notification can be performed based on the operation of existing specifications.

[0090] S225: The hSMF 30G updates information related to quality of service (QoS) based on the notification received in S224.

[0091] S226: hSMF30G sends a message (Nsmf (Update PDU session)) to pSEPP30B requesting updating of the PDU session.

[0092] S227: pSEPP30B sends a request message (HTTP POST (N32RefomattedReqMsg)) on N32-f including the message received in S226 to cSEPP30A via IntermediaryA and IntermediaryB.

[0093] S228: cSEPP30A sends to vSMF30D a message (Nsmf (Update PDU session)) requesting update of the PDU session, which is included in the message received in S227.

[0094] S229: The vSMF 30D sends a 200 OK to the cSEPP 30A as a response message to the message received in S228.

[0095] S230: The vSMF 30D updates information related to quality of service (QoS) based on the message received in S228.

[0096] S231: cSEPP30A transmits a response message (N32RefomattedRspMsg) on ​​N32-f, including the 200 OK received in S229, to pSEPP30B via IntermediaryA and IntermediaryB.

[0097] S232: pSEPP 30B sends the 200 OK included in the message received in S231 to hSMF 30G.

[0098] (Third Method) In the third method, the hSMF30G triggers a PDU session update as a newly defined NF service function. The network functions that are changed from the existing specifications are the pSEPP30B, the hSMF30G, and the Intermediary. The Intermediary adds information (a flag) indicating that it supports a new capability for executing the function to a message requesting PDU session creation (Create PDU Session) and transmits the message to the pSEPP30B. Furthermore, the pSEPP30B transmits a message including the flag to the hSMF30G. The hSMF30G adds the flag to a response message to the message, thereby making the pSEPP30B and the Intermediary aware that it supports the new capability. Furthermore, when a change to QoS information is required, the Intermediary causes the QoS information to be updated by transmitting a message instructing the change to the hSMF30G via the pSEPP30B. Furthermore, based on the procedures of the existing specifications, the hSMF 30G sends a message to the vSMF 30D to update the PDU session, thereby updating the QoS information in the vSMF 30D.

[0099] 8 is a diagram showing an example of a sequence diagram relating to the third method according to the embodiment of the present invention. The processing of each step in FIG. 8 will be described below. Note that pSEPP 30B, hSMF 30G, and Intermediary support the new function.

[0100] S301: N32-f is established between cSEPP30A and pSEPP30B.

[0101] S302: The terminal 20 sends a message to the vSMF 30D via the AMF 30C requesting the establishment of a PDU session.

[0102] S303: vSMF30D sends a message (Nsmf (Create PDU session)) to cSEPP30A requesting the creation of a PDU session.

[0103] S304: cSEPP30A sends a request message (HTTP POST (N32RefomattedReqMsg)) on N32-f including the message received in S303 to pSEPP30B via IntermediaryA and IntermediaryB, which are intermediaries.

[0104] S305: Intermediary B adds a flag indicating that it supports the ability to change the service conditions to the message sent in S304, and sends the message with the added flag to pSEPP30B. pSEPP30B recognizes that Intermediary B supports the ability.

[0105] S306: pSEPP 30B sends to hSMF 30G a message (Nsmf (Create PDU session)) requesting the creation of a PDU session, which is included in the message received in S305. The message includes a flag indicating that the capability to change service conditions is supported. hSMF 30G recognizes that Intermediary B and pSEPP 30B support this capability.

[0106] S307: hSMF 30G sends 200 OK to pSEPP 30B as a response message to the message received in S306. The message includes a flag indicating that it supports the ability to change the service conditions. pSEPP 30B recognizes that hSMF 30G supports the ability.

[0107] S308: The hSMF 30G sets information about the quality of service (QoS) corresponding to the PDU session related to the message received in S306.

[0108] S309: pSEPP 30B sends a response message (N32RefomattedRspMsg) on ​​N32-f, including the 200 OK received in S307, to cSEPP 30A via Intermediary A and Intermediary B. The response message includes a flag indicating that the capability to change service conditions is supported. Intermediary A recognizes that pSEPP 30B and hSMF 30G support the capability.

[0109] S310: Intermediary B transfers the message sent in S309 to pSEPP30A.

[0110] S311: The cSEPP 30A sends a 200 OK to the vSMF 30D as a response message to the message received in S303.

[0111] S312: The vSMF30D sets information about the quality of service (QoS) corresponding to the PDU session related to the message sent in S303.

[0112] S313: Intermediary B recognizes that a PDU session will be established based on the message received in S309, and sends a message to the communication traffic monitoring device that monitors the user plane communication traffic, instructing it to monitor the user plane communication traffic related to the PDU session.

[0113] S314: The traffic monitoring device detects that the traffic of the user plane that has been instructed to be monitored has exceeded a predetermined amount.

[0114] S315: The traffic monitoring device sends a message to Intermediary B notifying that an excess of traffic volume has been detected.

[0115] S316: IntermediaryB transmits a message (N32-f Error Reporting) on ​​N32-f to pSEPP30B requesting a change in QoS information (service conditions).

[0116] S317: The pSEPP 30B sends to the hSMF 30G a message (Nsmf (New Update)) requesting a change of the QoS setting (service conditions) contained in the message received in S316.

[0117] S318: The hSMF 30G sends a response message (200 OK) to the pSEPP 30B in response to the message received in S317.

[0118] S319: The pSEPP30B transmits the response message (200 OK) received in S318 to IntermediaryB.

[0119] S320: The hSMF 30G updates information related to quality of service (QoS) in response to the request received in S317. For example, the hSMF 30G changes the allowable user plane communication speed set in S308 to a lower communication speed.

[0120] Thereafter, in steps S321 to S327, processing related to updating the PDU session based on the procedures of the existing specifications is performed.

[0121] S321: hSMF30G sends a message (Nsmf (Update PDU session)) to pSEPP30B requesting updating of the PDU session.

[0122] S322: pSEPP30B sends a request message (HTTP POST (N32RefomattedReqMsg)) on N32-f, including the message received in S321, to cSEPP30A via Intermediary A and Intermediary B. The message includes information about quality of service (QoS).

[0123] S323: cSEPP30A sends to vSMF30D a message (Nsmf (Update PDU session)) requesting update of the PDU session, which is included in the message received in S322.

[0124] S324: The vSMF 30D sends a 200 OK to the cSEPP 30A as a response message to the message received in S323.

[0125] S325: The vSMF30D updates information related to quality of service (QoS) based on the message received in S324.

[0126] S326: cSEPP30A transmits a response message (N32RefomattedRspMsg) on ​​N32-f, including the 200 OK received in S324, to pSEPP30B via IntermediaryA and IntermediaryB.

[0127] S327: pSEPP 30B sends the 200 OK included in the message received in S326 to hSMF 30G.

[0128] (Variation of the third method) A variation of the third method will be described. In this variation, in S321 of FIG. 8, the hSMF30G transmits to the pSEPP30B a message (Nsmf (Update PDU session)) requesting the release of the PDU session, rather than a message (Nsmf (Update PDU session)) requesting the update of the PDU session. In the subsequent steps, processing for the release of the PDU session is also executed instead of processing for the update of the PDU session. This causes the data communication service to be stopped.

[0129] (Fourth Method) In the fourth method, the vSMF 30D triggers the release of a PDU session as a newly defined NF service function. The network functions that are changed from the existing specifications are the vSMF 30D, the cSEPP 30A, and the Intermediary. The vSMF 30D adds information (a flag) indicating that it supports a new capability for executing the function to a message requesting PDU session creation (Create PDU Session), and transmits the message to the cSEPP 30A. Furthermore, the cSEPP 30A transmits a message including the flag to the pSEPP 30B via the Intermediary. The Intermediary checks the flag when relaying the message. Furthermore, the Intermediary adds the flag to a response message to the message, thereby making the pSEPP 30B and the Intermediary aware that it supports the new capability. Furthermore, when releasing the PDU session, the Intermediary transmits a message to the vSMF 30D via the cSEPP 30A instructing it to release the PDU session. The vSMF30D releases the PDU session based on the procedure of the existing specification.

[0130] 9 is a diagram showing an example of a sequence diagram relating to the fourth method according to the embodiment of the present invention. The processing of each step in FIG. 9 will be described below. Note that the vSMF 30D, cSEPP 30A, and Intermediary support the new function.

[0131] S401: N32-f is established between cSEPP30A and pSEPP30B.

[0132] S402: The terminal 20 sends a message to the vSMF 30D via the AMF 30C requesting the establishment of a PDU session.

[0133] S403: The vSMF 30D sends a message (Nsmf (Create PDU session)) to the cSEPP 30A requesting the creation of a PDU session. The message includes information (a flag) indicating that the vSMF 30D supports a new capability related to triggering the release of the PDU session. The cSEPP 30A recognizes that the vSMF 30D supports the new capability.

[0134] S404: cSEPP 30A sends a request message (HTTP POST (N32RefomattedReqMsg)) on N32-f including the message received in S103 to pSEPP 30B via intermediaries Intermediary A and Intermediary B. The message includes information (flag) indicating support for the new capability for triggering PDU session release.

[0135] S405: IntermediaryB confirms that the message sent in S404 contains information (flag) indicating that it supports the new capability for triggering the release of PDU sessions, recognizes that vSMF30D and cSEPP30A support the new capability, and forwards the message to pSEPP30B.

[0136] S406: pSEPP 30B sends to hSMF 30G a message (Nsmf (Create PDU session)) requesting the creation of a PDU session, which is included in the message received in S405.

[0137] S407: The hSMF 30G sends a 200 OK to the pSEPP 30B as a response message to the message received in S406.

[0138] S408: pSEPP 30B transmits a response message (N32RefomattedRspMsg) on ​​N32-f, including the 200 OK received in S407, to cSEPP 30A via Intermediary A and Intermediary B.

[0139] S409: Intermediary B adds information (a flag) indicating that it supports the new capability for triggering the release of a PDU session to the message sent in S408, and sends the message to pSEPP 30A. cSEPP 30A recognizes that Intermediary B supports the new capability.

[0140] S410: cSEPP 30A sends 200 OK to vSMF 30D as a response message to the message received in S403. The message includes information (a flag) indicating that the new capability related to triggering the release of a PDU session is supported. vSMF 30D recognizes that Intermediary B and vSMF 30D support the new capability.

[0141] S411: Intermediary B recognizes that a PDU session will be established based on the message received in S408, and sends a message to the communication traffic monitoring device that monitors the user plane communication traffic, instructing it to monitor the user plane communication traffic related to the PDU session.

[0142] S412: The traffic monitoring device detects that the traffic of the user plane that has been instructed to be monitored has exceeded a predetermined amount.

[0143] S413: The traffic monitoring device sends a message to Intermediary B notifying that an excess of traffic volume has been detected.

[0144] S414: Intermediary B sends a message (N32-f Error Reporting) on ​​N32-f to cSEPP30A requesting the release of the PDU session.

[0145] S415: cSEPP30A sends to vSMF30D a message (Nsmf (New Release)) requesting the release of the PDU session, which is included in the message received in S414.

[0146] S416: The vSMF 30D sends a response message (200 OK) to the cSEPP 30A in response to the message received in S415.

[0147] S417: The cSEPP 30A transmits the response message (200 OK) received in S416 to Intermediary B.

[0148] Thereafter, in steps S418 to S423, processing related to the release of the PDU session is performed based on the procedures of the existing specifications.

[0149] S418: vSMF30D sends a message (Nsmf (Release PDU session)) to cSEPP30A requesting the release of the PDU session.

[0150] S419: cSEPP30A sends a request message (HTTP POST (N32RefomattedReqMsg)) on N32-f including the message received in S418 to pSEPP30B via IntermediaryA and IntermediaryB.

[0151] S420: pSEPP30B sends to hSMF30G a message (Nsmf (Release PDU session)) requesting the release of the PDU session, which is included in the message received in S419.

[0152] S421: The hSMF 30G sends a 200 OK to the pSEPP 30B as a response message to the message received in S420.

[0153] S422: pSEPP30B transmits a response message (N32RefomattedRspMsg) on ​​N32-f, including the 200 OK received in S421, to cSEPP30A via IntermediaryA and IntermediaryB.

[0154] S423: The cSEPP 30A sends a 200 OK to the vSMF 30D as a response message to the message received in S422.

[0155] According to the above-described embodiment, it is possible to execute a process related to communication between different networks in a communication system based on a trigger detected by an intermediary operator's device. Note that, in the above-described embodiment, an example has been described in which the intermediary operator's device executes a process to change the service conditions (limit the communication speed) in response to a notification of an excess communication volume received from a communication volume monitoring device, but the trigger and the process may be different.

[0156] (Effects) The technology of the present invention makes it possible to execute processing (for example, limiting the bandwidth of data communication, and providing services such as starting and stopping data communication) based on the trigger detected by the relay carrier's device.

[0157] Fig. 10 is a diagram showing an example of a first service according to an embodiment of the present invention. As shown in Fig. 10, an intermediary operator can provide a supplementary service in which a predetermined amount of data (e.g., 5 GB) can be used at the maximum speed in a roaming destination network, and the intermediary operator limits the communication bandwidth after detecting that the data amount has been exceeded.

[0158] Fig. 11 is a diagram showing an example of a second service according to an embodiment of the present invention. As shown in Fig. 11, an intermediary service provider can control the start and stop of data communication (access permission to the Internet) in a roaming destination network, triggered by a portal operation by a user.

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

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

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

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

[0163] As described in the embodiment, the control unit 140 performs processing related to communication between different networks based on a trigger detected by the device of the intermediary business. The control unit 140 also performs processing related to communication with the terminal 20. A functional unit related to signal transmission in the control unit 140 may be included in the transmitting unit 110, and a functional unit related to signal reception in the control unit 140 may be included in the receiving unit 120.

[0164] <Terminal 20> Fig. 13 is a diagram showing an example of the functional configuration of the terminal 20. As shown in Fig. 13, 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. 13 is merely an example. As long as the operations related to the embodiment of the present invention can be performed, the names of the functional divisions and functional units may be any. In addition, the communication device that becomes the resource holder 20 may have the same functional configuration as the terminal 20.

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

[0166] 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. The content of the setting information is, for example, information related to communication paths in the IMS data channel network.

[0167] As described in the embodiments, the control unit 240 performs processes related to connection with the base station 10 and the network node 30. 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.

[0168] (Hardware Configuration) The block diagrams (FIGS. 12 and 13) 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.

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

[0170] 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. 14 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.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0191] <Additional Notes> (Additional Note 1) A network node comprising: a receiving unit that receives, from a relay carrier device, a first message requesting the creation of a session, the first message including capability information indicating that the relay carrier device supports a capability related to a change in service conditions in communication between different networks; and a transmitting unit that transmits, to a first network node, a second message requesting the creation of the session, the second message including the capability information, wherein the receiving unit receives, from the first network node, a third message including the capability information as a response to the second message; the transmitting unit transmits, to the relay carrier device, a fourth message including the capability information as a response to the first message; the receiving unit receives, from the first network node, a fifth message requesting a subscription related to the change in service conditions; and when the receiving unit receives a notification related to the change in service conditions from the relay carrier device, the transmitting unit transmits the notification to the first network node. (Supplementary Note 2) A network node comprising: a receiving unit that receives from a first network node a first message requesting the creation of a session, the first message including capability information indicating that the network node supports a capability related to a change in service conditions in communication between different networks; a transmitting unit that transmits to the first network node a second message including the capability information in response to the first message; and a control unit that sets quality of service information for the session, wherein the transmitting unit transmits to the first network node a third message requesting a subscription related to the change in service conditions; the receiving unit receives from the first network node a notification related to the change in service conditions; and the control unit updates the quality of service information based on the notification.(Supplementary Item 3) A network node comprising: a receiving unit that receives, from a relay carrier device, a first message requesting a session update in accordance with a change in service conditions in communication between different networks; and a transmitting unit that transmits, to a first network node, a second message requesting the session update, wherein the receiving unit receives, from the first network node, a response message in response to the second message, and the transmitting unit transmits, to the relay carrier device, the response message in response to the first message. (Supplementary Item 4) A network node comprising: a transmitting unit that transmits, to a first network node, a first message requesting the creation of a session in communication between different networks; a receiving unit that receives, from the first network node, a response message in response to the first message; and a control unit that sets quality of service information for the session, wherein the receiving unit receives, from the first network node, a second message requesting the session update in accordance with a change in service conditions in the communication, the transmitting unit transmits, to the first network node, a response message in response to the second message, and the control unit updates the quality of service information based on the session update. (Supplementary clause 5) A network node comprising: a receiving unit that receives a first message requesting acquisition of subscriber information from a relay carrier device; and a transmitting unit that transmits a second message requesting acquisition of the subscriber information to a first network node, wherein the receiving unit receives a third message including the subscriber information from the first network node; the transmitting unit transmits a fourth message including the subscriber information to the relay carrier device; the receiving unit receives a fifth message from the relay carrier device that requests updating of the subscriber information in accordance with a change in service conditions in communication between different networks; and the transmitting unit transmits a sixth message requesting updating of the subscriber information to the first network node.(Supplementary clause 6) A network node comprising: a receiving unit that receives a first message from a first network node requesting acquisition of subscriber information; and a transmitting unit that transmits a second message including the subscriber information to the first network node, wherein the receiving unit receives a third message from the first network node requesting an update of the subscriber information in response to a change in service conditions in communication between different networks; and the transmitting unit transmits a fourth message to a second network node requesting an update of service quality information in response to the update of the subscriber information.

[0192] Any of supplementary items 1 to 6 makes it possible to execute communication in which settings related to permission of communication are made for each connection of a network function in communication with another network in a communication system.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0227] 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 receiving unit that receives from a relay carrier's device a first message requesting generation of a session, the first message including capability information indicating the ability to support changes in service conditions in communication between different networks; a transmitting unit that transmits to a first network node a second message requesting generation of the session, the second message including the capability information; wherein the receiving unit receives from the first network node a third message including the capability information as a response to the second message; the transmitting unit transmits to the relay carrier's device a fourth message including the capability information as a response to the first message; the receiving unit receives from the first network node a fifth message requesting a subscription related to the change in service conditions; and when the receiving unit receives from the relay carrier's device a notification related to the change in service conditions, the transmitting unit transmits the notification to the first network node.

2. A receiving unit that receives from a first network node a first message requesting generation of a session, the first message including capability information indicating the ability to support changes in service conditions in communication between different networks; a transmitting unit that transmits to the first network node a second message including the capability information as a response to the first message; a control unit that sets service quality information for the session; wherein the transmitting unit transmits to the first network node a third message requesting a subscription related to the change in service conditions; the receiving unit receives from the first network node a notification related to the change in service conditions; and the control unit updates the service quality information based on the notification.

3. A receiving unit that receives from a relay carrier's device a first message requesting an update of a session in response to a change in service conditions in communication between different networks; a transmitting unit that transmits to a first network node a second message requesting the update of the session; wherein the receiving unit receives from the first network node a response message to the second message; and the transmitting unit transmits to the relay carrier's device a response message to the first message.

4. A network node comprising: a transmitting unit that transmits a first message requesting generation of a session in communication between different networks to a first network node; a receiving unit that receives a response message to the first message from the first network node; and a control unit that sets quality of service information for the session, wherein the receiving unit receives a second message from the first network node requesting an update of the session in response to a change in service conditions in the communication, the transmitting unit transmits a response message to the second message to the first network node, and the control unit updates the quality of service information based on the update of the session.

5. A network node comprising: a receiving unit that receives a first message requesting acquisition of subscriber information from an apparatus of a relay carrier; and a transmitting unit that transmits a second message requesting acquisition of the subscriber information to a first network node, wherein the receiving unit receives a third message including the subscriber information from the first network node, the transmitting unit transmits a fourth message including the subscriber information to the apparatus of the relay carrier, the receiving unit receives a fifth message from the apparatus of the relay carrier requesting an update of the subscriber information in response to a change in service conditions in communication between different networks, and the transmitting unit transmits a sixth message requesting an update of the subscriber information to the first network node.

6. A network node comprising: a receiving unit that receives a first message requesting acquisition of subscriber information from a first network node; and a transmitting unit that transmits a second message including the subscriber information to the first network node, wherein the receiving unit receives a third message from the first network node requesting an update of the subscriber information in response to a change in service conditions in communication between different networks, and the transmitting unit transmits a fourth message requesting an update of quality of service information in response to the update of the subscriber information to a second network node.

Images