Network node and communication method

Abstract

This network node includes: a transmission unit that transmits, to a first network node, a first message for requesting registration of information in which information related to a destination network, information related to a purpose of connection with the destination network, and information related to communication permission for each network function in the destination network are associated with each other; and a reception unit that receives, from the first network node, a second message that is a response to the first message.

Description

Network node and communication method

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

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

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

[0004] 3GPP TS 23.501 V18.3.0 (2023-09) 3GPP TS 23.573 V18.4.0 (2023-09) 3GPP TS 23.510 V18.4.0 (2023-09) 3GPP TS 23.500 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 set communication permission for each API (Application Interface) provided by the NF for communication in N32.

[0007] The present invention has been made in view of the above points, and has as its object to execute settings relating to permission of communication for each connection of a network function in communication with another network in a communication system.

[0008] According to the disclosed technology, there is provided a network node having: a transmitter that transmits to a first network node a first message requesting registration of information that associates information about a destination network, information about the purpose of connecting to the destination network, and information about communication permissions for each network function in the destination network; and a receiver that receives from the first network node a second message that is a response to the first message.

[0009] According to the disclosed technology, in a communication system, it is possible to execute settings related to permission of communication for each connection of a network function in communication with another network.

[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 first sequence diagram according to an embodiment of the present invention. FIG. 5 is a diagram for explaining an example of a second sequence diagram according to an embodiment of the present invention. FIG. 6 is a diagram for explaining an example of first data according to an embodiment of the present invention. FIG. 7 is a diagram for explaining an example of second data according to an embodiment of the present invention. FIG. 8 is a diagram for explaining an example of a fifth data according to an embodiment of the present invention. FIG. 9 is a diagram for explaining a data structure according to an embodiment of the present invention. FIG. 10 is a diagram for explaining an example of an error message according to an embodiment of the present invention. FIG. 11 is a diagram for explaining processing according to an embodiment of the present invention. FIG. 12 is a diagram for explaining processing according to an embodiment of the present invention. FIG. 13 is a diagram for explaining an example of a fourth data according to an embodiment of the present invention. FIG. 14 is a diagram for explaining an example of an eighth data according to an embodiment of the present invention. FIG. 15 is a diagram for explaining an example of the functional configuration of a base station 10 and a network node 30 according to an embodiment of the present invention. FIG. 16 is a diagram for explaining an example of the functional configuration of a terminal 20 according to an embodiment of the present invention. FIG. 17 is a diagram for explaining an example of the hardware configuration of a base station 10, a terminal 20, and a network node 30 according to an embodiment of the present invention. FIG. 18 is a diagram for explaining an example of the configuration of a vehicle 2001 according to 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 an 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 to the UDM, and session creation, modification, and termination to 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, 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] Under existing specifications, all communications on N32 are permitted, making it impossible for operators to exercise the necessary control in the event of congestion or a failure. Furthermore, when establishing multiple N32s to distribute communications, it is difficult to clarify the distribution conditions. Furthermore, when various types of signals are transmitted over the same route in a monitoring device, there is a risk that some signals may be overlooked, especially during periods of high load, as not all processing may be performed. Furthermore, relay operators that relay between networks provide additional services by processing signals destined for certain devices. However, if the load of extracting target signals increases, signals may be overlooked and necessary processing may not be performed.

[0027] (First embodiment) A first embodiment will be described. In the first embodiment, a procedure for executing 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 will be described.

[0028] FIG. 4 is a diagram illustrating an overview of an embodiment of the present invention. In FIG. 4, during capability exchange for an N32 connection performed in N32-c, the SEPP on the VPLMN side and the SEPP on the HPLMN side notify each other of the APIs of the NF producers they allow, and only communication using those APIs is allowed in N32-f. That is, a consumer NF on the VPLMN side is allowed to connect to an NF producer on the HPLMN side. For this purpose, the request message and response message transmitted during the capability exchange specify allowed APIs, disallowed APIs, and APIs for which permission or disallowance is not specified. Furthermore, multiple N32 connections may be established as necessary. This makes it possible to mitigate the impact of problems, etc., that occur on an API-by-API basis. That is, N32-f can be configured to allow or disallow connections between NFs (or network nodes having NFs) on the VPLMN side and the HPLMN side, respectively. Furthermore, an API is an interface that exists for each communication between an NF on the VPLMN side and an NF on the HPLMN side, and may be expressed as an NF type. In addition, in messages or data that handle NF types, it may be written as NFType or NfType.

[0029] 5 is a diagram showing an example of a first sequence diagram according to an embodiment of the present invention. In FIG. 5, SEPP30A1, SEPPA2, NF30C, and NRF30E are network nodes on the VPLMN side, and SEPP30B, NF30D, and NRF30F are network nodes on the HPLMN side. The processing of each step in FIG. 5 will be described below.

[0030] S101: N32-c is established between SEPP30A1 and SEPP30B.

[0031] S102: The SEPP 30A1 sends a request message to the SEPP 30B requesting a security capability exchange in N32-c. The request message includes configuration information regarding NF types that are requested, permitted, and / or not permitted in the capability exchange. That is, the configuration information is configuration information regarding communication permission for each connection with a network function (NF) in another network (HPLMN). Hereinafter, "permit and / or not permitted" will be expressed as "permit / not permitted." The capability exchange may also be referred to as capability negotiation.

[0032] S103: The SEPP 30B sends to the SEPP 30A1 a response message (200 OK) in response to the request message received in S102. The response message includes setting information related to permitted / non-permitted NF types received in the capability exchange. Here, the information received by the SEPP 30B may include, for example, non-permitted NF types as some of the permitted NF types requested by the SEPP 30A1. Furthermore, the SEPP 30A1 performs settings related to communication permission for each connection with a network function (NF) in another network (HPLMN) supported by the SEPP 30B based on the received setting information. Here, the settings related to the supported communication permission may be the same as the settings in the received setting information, or some of the permitted NF types received by the SEPP 30B may include non-permitted NF types.

[0033] That is, in S102 and S103, the procedure for security capability exchange in N32-c of the existing specifications is extended to set the NF type indicating the API type of the NF Producer permitted by SEPP30A1 on the side requesting the establishment of N32. Also, in order to update the capability information in the N32 connection for which the capability exchange has already been completed, the request message of S101 includes a value indicating whether or not re-exchange is to be performed for the N32 connection for which the capability exchange has already been completed.

[0034] Fig. 6 is a diagram showing an example of a second sequence diagram according to an embodiment of the present invention. Fig. 6 is a sequence diagram showing the procedure for security capability negotiation defined in section 5.2.2 of Non-Patent Document 2. The Initial SEPP and Responding SEPP in Fig. 6 correspond to SEPP30A1 and SEPP30B in Fig. 5, respectively. The first step, "1. POST .. / exchange-capability (SecNegotiateReqData)," and the second step, "2a. 200 OK (SecNegotiateRspData)," correspond to S102 and S103 in Fig. 5, respectively.

[0035] Here, newly defined data indicating the requested NF type is added to the data (SecNegotiateReqData) included in the first step of Fig. 6. Fig. 7 is a diagram showing an example of the first data in an embodiment of the present invention. Fig. 7 shows "requestingNfTypes", which is a newly defined attribute name indicating the requested NF type. Furthermore, the value of the requested NF type is set to "ConfigSeppAllowingNfs", which is a newly defined data type. Note that SecNegotiateReqData in the existing specifications is defined in Section 6.1.5.2.2 of Non-Patent Document 2.

[0036] Furthermore, newly defined data indicating the NF type, which indicates the type of API of the NF Producer permitted by the SEPP30B that accepts the request to establish an N32, is added to the data (SecNegotiateRspData) included in the second step of FIG. 6. FIG. 8 is a diagram showing an example of the second data in the embodiment of the present invention. FIG. 8 shows "acceptedNfTypes," which is a newly defined attribute name indicating the accepted NF type. Furthermore, the value of the accepted NF type is set to "ConfigSeppAllowingNfs," which is a newly defined data type. Note that SecNegotiateRspData in the existing specifications is defined in Section 6.1.5.2.3 of Non-Patent Document 2.

[0037] Returning to FIG.

[0038] S104: The SEPP 30A1 sends the NRF 30E a request message requesting registration of information regarding permitted / non-permitted NF types determined by the security capability exchange in S102 and S103.

[0039] S105: In response to the request message received in S104, the NRF 30E registers the NF type requested to be registered as information indicating the NF type supported by the SEPP 30A1. Furthermore, the NRF 30E transmits a response to the request message received in S104 to the SEPP 30A1.

[0040] S106: The SEPP 30B sends the NRF 30F a request message requesting registration of information regarding permitted / non-permitted NF types determined by the security capability exchange in S102 and S103.

[0041] S107: In response to the request message received in S106, the NRF 30F registers the NF type requested to be registered as information indicating the NF type supported by the SEPP 30B. Furthermore, the NRF 30F transmits a response to the request message received in S106 to the SEPP 30B.

[0042] Fig. 9 is a diagram showing an example of a third sequence diagram according to an embodiment of the present invention. Fig. 9 shows a sequence diagram of the procedure for registering information to the NRF defined in Section 5.2.2.2.2 of Non-Patent Document 2. The NF Service Consumer in Fig. 9 corresponds to the SEPP 30A1 or SEPP 30B in Fig. 5, and the NRF in Fig. 9 corresponds to the NRF 30E or NRF 30F in Fig. 5. Furthermore, the first step "1. POST .. / nf-instances / {nfInstanceID}(NF Profile)" and the second step "2a. 201 Created(NP Profile)" correspond to S104 and S105, or S106 and S107, respectively, in Fig. 5.

[0043] Here, newly defined data indicating supported NF types is added to the data included in the first step of FIG. 9 (SeppInfo included in the NF Profile). FIG. 10 is a diagram showing an example of the third data in an embodiment of the present invention. FIG. 10 shows "supportedNfTypes", which is a newly defined attribute name indicating supported NF types. The value of the supported NF types is set to "ConfigSeppAllowingNfs", which is a newly defined data type. Note that SeppInfo in the existing specifications is defined in Section 6.1.6.2.72 of Non-Patent Document 3.

[0044] Fig. 11 is a diagram showing an example of the fourth data in an embodiment of the present invention. Fig. 11 shows information on items such as the attribute name and data type in "ConfigSeppAllowingNfs," a newly defined data type. The attribute addedNfTypes and attribute deletedNfTypes indicate that information on allowed / disallowed NF types is to be added and deleted, respectively, from existing information. The information to be set is stored in the newly defined data type SeppAllowingNfs, which will be described later. The attribute resetConfig is used when initializing existing information in a specific attribute.

[0045] FIG. 12 is a diagram showing an example of the fifth data in an embodiment of the present invention. FIG. 12 describes information on items such as the attribute name and data type in "SeppAllowingNfs," a newly defined data type. The attributes allowedNFTypes and nonAllowedNFTypes are set with information on allowed and disallowed NF types, respectively, and are stored as a list containing multiple NF types in the existing data type array. This list is commonly used in processes related to requests, responses, configuration, discovery, and acceptance, thereby enabling efficient execution of configuration and other processes. The attribute defaultOfAllowingNFType is used when setting the initial value of the data type.

[0046] Fig. 13 is a diagram illustrating a data structure in an embodiment of the present invention. As shown in Fig. 13, requestingNfTypes indicating the requested NF type in SecNegotiateReqData of the first step in Fig. 6, acceptedNfTypes indicating the accepted NF type in SecNegotiateRspData of the second step in Fig. 6, and supportedNfTypes indicating the supported NF type in the NF Profile of the first step in Fig. 9 are stored in the data type ConfiSeppAllowingNfs shown in Fig. 11. Furthermore, the attributes addedNfTypes and deletedNfTypes of ConfiSeppAllowingNfs are stored in the data type SeppAllowingNfs shown in Fig. 12, forming a hierarchical structure.

[0047] Returning to FIG.

[0048] S108: N32-f is established between SEPP30A1 and SEPP30B.

[0049] S109: The NF 30C sends to the SEPP 30A2 a request message (HTTP Service Request) to connect to the NF 30D on the HPLMN side and start a service. Here, it is assumed that the SEPP 30A2 is not permitted to connect to the API (NF type) provided by the NF 30D on the HPLMN side (no setting to permit connection).

[0050] S110: SEPP 30A2 determines that connection via the request message is not permitted based on the setting information set in the SEPP 30A2 regarding permission for the API (NF type) provided by the network function on the HPLMN side. Furthermore, SEPP 30A2 transmits to NF 30C, as a response to the request message received in S109, an error message indicating that the SEPP 30A2 is not permitted to use the API (NF type) provided by NF 30D on the HPLMN side (i.e., connection to NF 30D is not permitted).

[0051] Fig. 14 is a diagram showing an example of an error message according to an embodiment of the present invention. As shown in Fig. 14, the error message sent in S110 of Fig. 5 is newly defined as one of the error messages defined in Table 5.2.7.4-1 of Non-Patent Document 4, for example.

[0052] 15 is a diagram illustrating processing in an embodiment of the present invention. As shown in FIG. 15, for example, in an N32 connection between a VPLMN and an HPLMN SEPP, if an N32 connection that allows only AUSF as the NF type is established and then a request for communication with the HPLMN UDM is received from an NF (e.g., AMF) on the VPLMN side, the VPLMN SEPP sends an error message rejecting the request as an unintended communication. The NF that receives the error message searches for an alternative SEPP and attempts to communicate with the HPLMN UDM.

[0053] 16 is a diagram illustrating processing in an embodiment of the present invention. As shown in FIG. 16, SEPPs 30A1 and 30A2, which are initiating SEPPs, acquire information about permitted NF types from SEPPs 30B1 and 30B2, which are responding SEPPs (S201, S201′), and then store the acquired information in NRF 30D within their own network (S202). Here, for example, assume that in S201, SEPP 30A1 sets the NF type to allow only AUSF, and in S201′, SEPP 30A2 sets the NF type to allow only UDM.

[0054] The NF30C sends a message to the NRF30D inquiring about the SEPP that authorizes the API of the communication destination (UDM), and the NRF30D sends information (SEPPA2) of the SEPP that authorizes the API of the communication destination (UDM) to the NF30C in response to the inquiry (S203).

[0055] Based on the information acquired in S203, NF30C selects SEPP30A2, which is an SEPP that authorizes the API of the communication destination (UDM), as the initiating SEPP, and transmits a signal such as a connection request message to the communication destination (UDM) of another network (HPLMN) to SEPP30A2 (S204).

[0056] Returning to Fig. 5, steps S111 and S112 in Fig. 5 correspond to step S203 in Fig. 16 described above.

[0057] S111: The NF 30C sends a message to the NRF 30E to inquire about information about the SEPP that permits the API of the communication destination (NF 30D) (to request acquisition of the information). The message includes information about the NF type corresponding to the API of the communication destination being inquired.

[0058] S112: The NRF 30E transmits to the NF 30C, as a response to the message received in S111, a message including information about the SEPP that permits the API of the communication destination.

[0059] Fig. 17 is a diagram showing an example of a fourth sequence diagram in an embodiment of the present invention. Fig. 17 shows a sequence diagram of an NF discovery procedure defined in section 5.3.2.2.2 of Non-Patent Document 2. The NF Service Consumer in Serving PLMN in Fig. 17 corresponds to the NF 30C in Fig. 5, and the NRF in Serving PLMN in Fig. 17 corresponds to the NRF 30E in Fig. 5. In addition, the first step, "1.GET .. / nf-instances? / <query parametes> " and the second step "2a. 200 OK (SearchResult)" correspond to S111 and S112 in FIG. 5, respectively.

[0060] Here, SeppInfo is included in the NF Profile included in the data included in the second step in Fig. 17 (SearchResult, see section 6.2.6.2.2 of Non-Patent Document 3). As described in Fig. 9, a newly defined attribute name "supportedNfTypes" indicating the supported NF types described in Fig. 10 is newly added to SeppInfo. That is, supportedNfTypes is included in SearchResult. Therefore, based on the received SearchResult, the NF30C can find a SEPP that allows the API (NF type) of the communication destination.

[0061] Returning to Fig. 5, S113 in Fig. 5 corresponds to S204 in Fig. 16 described above.

[0062] S113: Based on the message received in S112, NF30C selects SEPP 30A1 as the SEPP that will permit the API provided by NF30D. The subsequent processing is performed based on existing specifications. NF30C connects to NF30D and sends a request message (HTTP Service Request) to SEPP 30A1 requesting the start of the service.

[0063] S114: SEPP 30A1 sends an HTTP POST (N32ReformattedReqMsg) including the received request message to SEPP 30B via intermediaries A and B.

[0064] S115: The SEPP 30B sends a request message (HTTP Service Request) included in the received message to the NF 30D. The SEPP 30B may execute transmission of the request message after confirming that the NF type indicated in the request message is permitted.

[0065] S116: The NF 30D sends a 200 OK to the SEPP 30B as a positive response to the received request message.

[0066] S117: SEPP 30B transmits a message (N32ReformattedReqMsg) including the received 200 OK to SEPP 30A1 via the intermediaries A and B.

[0067] S118: The SEPP 30A1 sends a 200 OK to the NF 30C.

[0068] According to the above-described embodiment, in a communication system, it is possible to execute settings relating to permission of communication for each connection of a network function for communication with another network.

[0069] (Example 2) Example 2 will be described. In Example 1, as shown in Fig. 13, data having a data structure in which ConfigSeppAllowingNfs, which includes information about the NF type, includes supportedNfTypes, which indicates the supported NF types. In Example 2, it is possible to register information about a plurality of NF types associated with a destination network and the purpose of connecting to the network via an N32 interface.

[0070] Fig. 18 is a diagram showing an example of sixth data in an embodiment of the present invention. In the second embodiment, a data type "Targetinfo" is newly defined, which includes a list of information on destination PLMNs (remotePlmnList), a list of information on destination Standalone Non-Public Networks (SNPNs) (remoteSnpnList), a list of information on the purposes of the N32 interface (n32Purposes), and information on supported NF types (supportedNfTypes), as shown in Fig. 18.

[0071] Fig. 19 is a diagram showing an example of seventh data in an embodiment of the present invention. In Example 2, an attribute name "supportedTargets" including a list of Targetinfo shown in Fig. 18 is newly defined as shown in Fig. 19.

[0072] Fig. 20 is a diagram showing an example of eighth data in an embodiment of the present invention. In the data structure used in Example 2, Seppinfo, which stores information about the SEPP, includes supportedTargets shown in Fig. 19, which is an information attribute including a list of Targetinfo shown in Fig. 18. Furthermore, in Example 1, similar to the data structure shown in Fig. 13, requestingNfTypes, acceptedNfTypes, and supportedNfTypes (included in Targetinfo) are stored in ConfiSeppAllowingNfs.

[0073] In Example 2, by using the above-mentioned data structure, when information regarding permitted / prohibited NF types related to the SEPP described in Example 1 is registered in the NRF (S104-S105 in Figure 5, etc.), information regarding the destination network and information regarding the purpose of the N32 interface can be associated and information regarding the NF type can be registered.

[0074] That is, the SEPP sends a request message to the NRF requesting registration of information that associates information about the destination network, information about the purpose of connecting to the destination network, and information about communication permissions for each network function in the destination network. The SEPP also receives a response message to the request message from the NRF.

[0075] In addition, in Example 2, by using the above-mentioned data structure, when querying the NRF for information regarding the NF types that are permitted / not permitted in relation to the SEPP as described in Example 1 (S111-S112 in Figure 5), it is possible to query for information regarding the NF types based on the conditions of information regarding the destination network and information regarding the purpose of the N32 interface.

[0076] That is, the NF transmits a request message to the NRF requesting registration information related to communication permission for each network function in the destination network, which is associated with information about the destination network and information about the purpose of connecting to the destination network. In response to the request message, the NF receives a response message from the NRF including the requested registration information.

[0077] According to the above-described embodiment, in a communication system, it is possible to execute settings relating to permission of communication for each connection of a network function for communication with another network.

[0078] (Effect) In communications based on the processing according to the present invention, the types of communications that are permitted are separated, making it possible to improve the quality of monitoring, additional services, and troubleshooting.

[0079] Furthermore, since it is possible to block signals under specific conditions, operations can be implemented when trouble occurs. For example, when congestion occurs due to location registration, it is possible to limit access to only the related UDM, thereby minimizing the impact on communications of existing users who do not require new location registration. Furthermore, in the event of an abnormality, it is possible to prompt recovery from the abnormal state by (temporarily) blocking only communications of specific N32-f at the discretion of the operation.

[0080] Furthermore, it is possible to facilitate signal extraction at the monitoring device and relay carrier, and improve the reliability of the necessary processing at each. For example, it is possible to allocate a large part of the processing load to processing after signal extraction, and it is possible to prevent processing failures.

[0081] Furthermore, by using the data structure described in the second embodiment, it is possible to set different conditions such as NF type for each destination PLMN ID (i.e., destination network operator) in the SEPP, and establish an N32 interface with a different policy for each operator. For example, X and Y can be set as the permitted NF types for companies A and B, and Z can be set as the permitted NF type for companies C and D.

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

[0083] <Base Station 10 and Network Node 30> Fig. 21 is a diagram showing an example of the functional configuration of the base station 10 and the network node 30. As shown in Fig. 21, the base station 10 has a transmitting unit 110, a receiving unit 120, a setting unit 130, and a control unit 140. The functional configuration shown in Fig. 21 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.

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

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

[0086] As described in the embodiment, the control unit 140 performs processing such as making settings related to permission for communication for each connection of network functions between different networks. 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.

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

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

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

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

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

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

[0093] 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. 23 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.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0114] <Additional Notes> (Additional Item 1) A network node comprising: a transmitter that transmits to a first network node a first message requesting registration of information associating information about a destination network, information about a purpose for connecting with the destination network, and information about communication permission for each network function in the destination network, and a receiver that receives from the first network node a second message that is a response to the first message. (Additional Item 2) A network node comprising: a transmitter that transmits to a first network node a first message requesting registration information related to communication permission for each network function in the destination network, which is associated with information about the destination network and information about a purpose for connecting with the destination network, and a receiver that receives from the first network node a second message including the registration information as a response to the first message. (Supplementary Item 3) A network node comprising: a receiver that receives from a first network node a first message requesting registration of information associating information about a destination network, information about a purpose for connecting with the destination network, and information about communication permission for each network function in the destination network, and a transmitter that transmits to the first network node a second message that is a response to the first message. (Supplementary Item 4) A network node comprising: a receiver that receives from a first network node a first message requesting registration information for communication permission for each network function in the destination network, which is associated with information about the destination network and information about a purpose for connecting with the destination network, and a transmitter that transmits to the first network node a second message including the registration information in response to the first message.(Supplementary Item 5) A communication method executed by a network node, comprising: a step of sending a first message to a first network node requesting registration of information associating information regarding a destination network, information regarding the purpose of connecting to the destination network, and information regarding communication permission for each network function in the destination network; and a step of receiving a second message from the first network node as a response to the first message.

[0115] Any of supplementary items 1 to 5 allows the setting of permission for communication to be made for each connection of a network function in communication with another network in a communication system.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

Claims

1. A network node having: a transmitter that transmits a first message to a first network node requesting registration of information that associates information about a destination network, information about the purpose of connecting to the destination network, and information about communication permissions for each network function in the destination network; and a receiver that receives a second message from the first network node that is a response to the first message.

2. A network node having: a transmitter that transmits a first message to a first network node requesting registration information related to communication permission for each network function in the destination network, the registration information being associated with information related to the destination network and information related to the purpose of connecting to the destination network; and a receiver that receives a second message including the registration information from the first network node in response to the first message.

3. A network node having: a receiving unit that receives from a first network node a first message requesting registration of information that associates information about a destination network, information about the purpose of connecting to the destination network, and information about communication permissions for each network function in the destination network; and a transmitting unit that transmits to the first network node a second message that is a response to the first message.

4. A network node having: a receiving unit that receives from a first network node a first message requesting registration information related to communication permission for each network function in the destination network, the registration information being associated with information related to the destination network and information related to the purpose of connecting to the destination network; and a transmitting unit that transmits a second message including the registration information to the first network node in response to the first message.

5. A communication method executed by a network node, comprising: a step of sending a first message to a first network node requesting registration of information relating to a destination network, information relating to the purpose of connection with the destination network, and information relating to communication permissions for each network function in the destination network; and a step of receiving a second message from the first network node that is a response to the first message.

Images