Network node and communication method

The network node facilitates secure communication in closed spaces by managing certificate chains within the mobile core network, addressing the challenge of obtaining and registering certificate chains for network devices, enabling secure authentication and authorization without external certificate authorities.

WO2024247226A1PCT designated stage expired Publication Date: 2024-12-05NTT DOCOMO INC
View PDF 2 Cites 0 Cited by

Patent Information

Application Number
PCT/JP2023/020498
Authority / Receiving Office
WO · WO
Patent Type
Applications
Current Assignee / Owner
Filing Date
2023-06-01
Publication Date
2024-12-05

AI Technical Summary

Technical Problem

In closed spaces like mobile networks, obtaining and registering certificate chains for secure communication between network devices is challenging due to the inability to connect to reliable certificate authorities via the Internet and frequent changes in communication destination devices.

Method used

A network node manages communication by receiving a generation request for a first network node, confirming a second network node, and transmitting requests to obtain certificate chains from a certificate management server and register with an authorization server, enabling secure communication within the mobile core network without external certificate authorities.

Benefits of technology

This method establishes secure communication between network devices in closed spaces by using certificate chains obtained from the mobile core network, allowing for mutual authentication and authorization without external network access, ensuring reliable security settings and user registration.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure JP2023020498_05122024_PF_FP_ABST
    Figure JP2023020498_05122024_PF_FP_ABST
Patent Text Reader

Abstract

Provided is a network node that manages communication between network nodes in a mobile core network, the network node comprising: a reception unit that receives a generation request for a first network node; a control unit that verifies a second network node that is a communication destination of the first network node; and a transmission unit that transmits, to a certificate management server, an acquisition request for the certificate chains of the first network node and the second network node and that transmits, to an authorization server, a registration request for the first network node.
Need to check novelty before this filing date? Find Prior Art

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] In 5G networks, authentication and authorization are performed between network devices, thereby realizing secure communication and cooperation within and between systems. For authentication, Mutual Transport Layer Security (MTLS) authentication is used, which performs mutual authentication using certificates in the transport layer to prevent tampering and verify authenticity. For authorization, OAuth is used to authorize device privileges. Furthermore, a method using a certificate chain is used to ensure the authenticity of certificates. For 5G, a communication method is specified in which the same certificate is used for authentication and authorization (e.g., Non-Patent Document 2).

[0005] In the ETSI (European Telecommunications Standards Institute) Network Functions Virtualization (NFV), studies are being conducted on the safe management and operation of virtualized core network functions (VNF: Virtual Network Function) (for example, Non-Patent Document 3).

[0006] 3GPP TS 23.501 V18.1.0 (2023-03) 3GPP TS 33.501 V18.1.0 (2023-03) ETSI GR NFV-SEC 005: Network Functions Virtualization (NFV); Trust; Report on Certificate Management v1.2.1 (2021-07)

[0007] When using mutual TLS authentication (Mutual TLS) and OAuth, it is necessary to be able to verify the certificates held by each device and to pre-register a user in OAuth using the certificate of the communication destination device. However, in a closed space such as a mobile network, it is difficult to obtain the certificate chain of the communication destination device due to problems such as the inability to connect to a trusted Certificate Authority (CA) via the Internet and frequent changes in the communication destination device. Therefore, there has been no method that solves these problems and allows a user to obtain the certificate chain of the communication destination device in a closed space and register a user in OAuth.

[0008] The present invention has been made in view of the above points, and has as its object to establish secure communication between network devices in a closed space.

[0009] According to the disclosed technology, there is provided a network node that manages communications between network nodes within a mobile core network, the network node having: a receiving unit that receives a generation request of a first network node; a control unit that confirms a second network node that is the communication destination of the first network node; and a transmitting unit that sends a request to obtain a certificate chain of the first network node and the second network node to a certificate management server, and sends a registration request of the first network node to an authorization server.

[0010] According to the disclosed technology, secure communication can be established between network devices in a closed space.

[0011] FIG. 1 is a diagram for explaining an example of a communication system. FIG. 2 is a diagram for explaining an example of a communication system in a roaming environment. FIG. 3 is a diagram for explaining an example of an architecture of an NFV. FIG. 4 is a diagram showing an example of a sequence diagram in an embodiment of the present invention. FIG. 5 is a diagram showing an example of the functional configuration of a base station 10 and a network node 30 in an embodiment of the present invention. FIG. 6 is a diagram showing an example of the functional configuration of a terminal 20 in an embodiment of the present invention. FIG. 7 is a diagram showing an example of the hardware configuration of a base station 10, a terminal 20, and a network node 30 in an embodiment of the present invention. FIG. 8 is a diagram showing an example of the configuration of a vehicle 2001 in an embodiment of the present invention.

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

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

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

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

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

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

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

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

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

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

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

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

[0024] 3 is a diagram illustrating an example of an architecture of NFV. The architecture of Network Functions Virtualization (NV) shown in FIG. 3 includes an Operation Support System (OSS), Management and Orchestration (MANO), Network Function Virtualization Infrastructure (NFVI), an authorization server, and a Certificate Management Function (CMF). The OSS, MANO, authorization server, CMF, and VNF may also be referred to as devices, network devices, network nodes, or the like.

[0025] OSS is an operational support system that detects, controls, and takes measures against faults and congestion that occur in mobile communication networks, and performs fault management, configuration management, billing management, performance management, and security management for networks and systems.

[0026] MANO uses Network Service Descriptors (NSDs) and Virtual Network Function Descriptions (VNFDs) to manage and control the lifecycle of virtual network functions (VNFs) that realize network services. MANO is sometimes called NFV-MANO.

[0027] NFVI is a virtualization infrastructure required for managing virtualized resources generated using virtualization technologies such as VMs and containers that make up VNFs, and includes general-purpose servers, storage, and network equipment.

[0028] The authorization server performs authorization based on, for example, OAuth when establishing communication between VNFs.

[0029] The CMF is a certificate management function that issues certificate chains, issues signed certificates, and manages certificates. The CMF may also be called a certificate management server with certificate management functions, or a certificate management authority. The authority that issues the root certificate is considered trustworthy, and the certification authorities authorized by that authority are also considered trustworthy, thereby ensuring the reliability of certificates signed with trusted root certificates. Checking whether distributed certificates and certificates held by communication target devices are connected by a certificate chain is called certificate verification. In mutual TLS authentication, communicating devices verify each other's certificates.

[0030] (Example 1) Example 1 will be described. Example 1 illustrates a process for establishing secure communication between network devices in a closed space. Specifically, in FIG. 3, a first VNF ​​is newly generated, and secure communication is established between the first VNF ​​and a second VNF. A first authorization server and a second authorization server are authorization servers that authorize the authority of the first VNF ​​and the second VNF, respectively. A first CMF and a second CMF are CMFs that manage certificates of the first VNF ​​and the second VNF, respectively. FIG. 4 is a diagram illustrating an example of a sequence diagram according to an embodiment of the present invention. The process of each step in FIG. 4 will be described below.

[0031] Step S301: Secure communication is established between the OSS, the MANO, the first authorization server, and the first CMF.

[0032] Step S302: The second VNF has been created, and the second VNF has obtained a certificate issued by the second CMF and has performed user registration of the second VNF with the second authorization server. The second CNF also holds the certificate chain of the second VNF.

[0033] Step S303: The OSS sends a request to the MANO to register a Network Service Descriptor (NSD) and a VNF Description (VNFD) to generate a first VNF. The MANO registers the received NSD and VNFD.

[0034] Step S304: Based on the NSD and VNFD registered in step S303, the OSS sends a request to the MANO to generate a first VNF ​​that provides the service specified in the NSD.

[0035] Step S305: MANO checks the requirements of the first VNF ​​and the communication destination (second VNF) based on the request received in step S304.

[0036] Step S306: MANO sends a first VNF ​​registration request to the first CNF requesting registration of the first VNF.

[0037] Step S307: In response to the first VNF ​​registration request, the first CNF generates an identifier of the first VNF ​​and a certificate chain of the first VNF. The certificate chain of the first VNF ​​is generated, for example, by adding a signature of the identifier of the first VNF ​​signed with the private key of the first CNF to the identifier of the first VNF. Furthermore, the first CNF sends a response to the registration request to MANO. The response includes the identifier of the first VNF ​​as registration information.

[0038] In step S308, the MANO sends a certificate chain acquisition request to the first CMF to request acquisition of the certificate chain of the first VNF ​​and the certificate chain of the second VNF. The certificate chain acquisition request includes an identifier of the first VNF ​​and an identifier of the second VNF.

[0039] Step S309: In response to the certificate chain acquisition request, the first CMF sends a certificate chain acquisition request to the second CMF, requesting acquisition of the certificate chain of the second VNF. The certificate chain acquisition request includes an identifier of the second VNF.

[0040] Step S310: In response to the certificate chain acquisition request, the second CMF sends the certificate chain of the second VNF to the first CMF.

[0041] Step S311: In response to the certificate chain acquisition request, the first CMF sends to MANO the certificate chain of the first VNF ​​generated in step S307 and the certificate chain of the second VNF received from the second CMF in step S310.

[0042] Step S312: MANO generates a public key and a private key for the first VNF.

[0043] In step S313, the MANO sends a first certificate signing request to the first CMF to request the generation of a certificate for the first VNF. The first certificate signing request includes the public key of the first VNF ​​generated in step S312.

[0044] Step S314: In response to the first certificate signing request, the first CMF generates a first certificate, for example, by signing the public key of the first VNF ​​with the private key of the first CMF, and then sends the generated first certificate to MANO.

[0045] Step S315: MANO sends a user registration request to the first authorization server to request user registration of the first VNF. The user registration request includes the first certificate. The user registration request also includes, for example, the NSD and VNFD of the first VNF ​​and information on the permissions required for the first VNF.

[0046] Step S316: The first authorization server performs user registration of the first VNF ​​by registering the first certificate in response to the user registration request. The first authorization server also registers, together with the first certificate, information on the authority to be granted to the first VNF, which is determined based on, for example, the NSD and VNFD of the first VNF ​​included in the user registration request and information on the authority required for the first VNF.

[0047] Step S317: MANO sends a VNF creation request to the NFVI, which is a virtualization infrastructure that creates VMs that configure the VNF, to create the first VNF. The VNF creation request includes the private key, public key, certificate (first certificate), and certificate chain of the first VNF.

[0048] Step S318: The first VNF ​​verifies the first certificate using the certificate chain. For example, the first VNF ​​accesses the first CMF to verify that the first certificate is a valid certificate issued by the first CMF. Furthermore, the first VNF ​​sends a VNF creation response to MANO in response to the VNF creation request.

[0049] Step S319: MANO sends a response to the request received in step S304 to the OSS.

[0050] Step S320: The OSS performs configuration for the first VNF ​​and starts monitoring the first VNF.

[0051] Step S321: Authentication and authorization are performed between the first VNF ​​and the second VNF by mutual TLS using their respective certificates and certificate chains. Here, the certificate chains used are those obtained from the first CMF and the second CMF. That is, mutual authentication can be performed using the certificate chains obtained from the mobile core network, which is a closed space, without accessing a certification authority present in an external network.

[0052] Furthermore, the following steps describe the process for authorizing the authority of the first VNF.

[0053] Step S322: The second VNF sends an authorization confirmation request to the second authorization server to confirm the authorization of the first VNF. The authorization confirmation request includes the certificate (first certificate) of the first VNF.

[0054] Step S323: Since the received authorization confirmation request is an authorization confirmation for the first VNF, the second authorization server sends the authorization confirmation request to the first authorization server.

[0055] Step S324: In response to the authorization confirmation request, the first authorization server confirms that the authority associated with the user-registered certificate, which is the same as the first certificate included in the authorization confirmation request, is the authority of the first VNF. Furthermore, the first authorization server transmits an authorization response indicating that the authority has been granted to the first VNF ​​to the second authorization server in response to the authorization confirmation request.

[0056] Step S325: The second authorization server sends the authorization response received from the first authorization server to the second VNF.

[0057] Step S326: The first VNF ​​and the second VNF start secure communication.

[0058] The above-described embodiment enables secure communication between network devices in a closed space. That is, mutual authentication between network devices can be performed using a certificate chain acquired from a closed mobile core network without accessing a certification authority in an external network. Furthermore, mutual authorization can be performed between network devices using a certificate registered in advance in an authorization server. Furthermore, VNFs can be generated by MANO, and reliable security settings can be automatically configured. That is, using NFV-MANO, it is possible to distribute and register a certificate chain for mutual TLS and certificate-binding authorization in a closed space.

[0059] In steps S312 and S313, the key generation and signed certificate generation or request performed by the MANO may be performed by the first VNF. Alternatively, when the MANO or VNF requests the certificate signing in step S313 (i.e., when issuing a CSR (Certificate Signing Request)), the CMF may generate the public key and private key and provide them to the VNF together with the certificate.

[0060] In addition, in step S304, the request to generate the first VNF ​​executed by the OSS and the request to generate the service provided by the first VNF ​​may be automatically executed by MANO.

[0061] In addition, the acquisition of the certificate chain of another network device (second VNF) performed in steps S309 to S319 may be performed by the MANO or VNF (first VNF) directly from the second CMF.

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

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

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

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

[0066] As described in the embodiment, the control unit 140 performs processes related to authentication and authorization. The control unit 140 also performs processes related to communication with the terminal 20. The function unit related to signal transmission in the control unit 140 may be included in the transmitting unit 110, and the function unit related to signal reception in the control unit 140 may be included in the receiving unit 120.

[0067] <Terminal 20> Fig. 6 is a diagram showing an example of the functional configuration of the terminal 20. As shown in Fig. 6, 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. 6 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.

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

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

[0070] The control unit 240 performs processes related to authentication and authorization as described in the embodiments. The function unit related to signal transmission in the control unit 240 may be included in the transmitting unit 210, and the function unit related to signal reception in the control unit 240 may be included in the receiving unit 220.

[0071] (Hardware Configuration) The block diagrams (FIGS. 5 and 6) 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.

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

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

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

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

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

[0077] 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. 5 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. 6 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.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0094] (Summary of embodiment) As described above, according to an embodiment of the present invention, there is provided a network node that manages communication between network nodes within a mobile core network, the network node having: a receiving unit that receives a generation request of a first network node; a control unit that confirms a second network node that is a communication destination of the first network node; and a transmitting unit that transmits a request to obtain a certificate chain of the first network node and the second network node to a certificate management server, and transmits a registration request of the first network node to an authorization server.

[0095] In addition, the control unit may generate a public key and a private key for the first network node, the receiving unit may receive a certificate for the first network node including a signature for the public key from the certificate management server, and the transmitting unit may transmit the registration request including the public key to the certificate management server.

[0096] The control unit may also generate the first network node using the certificate chain, the private key, the public key, and the certificate.

[0097] The certificate may also be used in authorizing the authority of the first network node.

[0098] The certificate management server may also be present in a mobile core network.

[0099] With the above configuration, secure communication can be established between network devices in a closed space.

[0100] Also, according to an embodiment of the present invention, there is provided a communication method executed by a network node that manages communication between network nodes in a mobile core network, the communication method comprising the steps of receiving a generation request for a first network node, confirming a second network node that is a communication destination of the first network node, sending a request to obtain a certificate chain for the first network node and the second network node to a certificate management server, and sending a registration request for the first network node to an authorization server.

[0101] With the above configuration, secure communication can be established between network devices in a closed space.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0136] 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 that manages communications between network nodes in a mobile core network, comprising: a receiving unit that receives a generation request of a first network node; a control unit that confirms a second network node with which the first network node communicates; and a transmitting unit that sends a request to obtain a certificate chain for the first network node and the second network node to a certificate management server, and sends a registration request for the first network node to an authorization server.

2. A network node as described in claim 1, wherein the control unit generates a public key and a private key for the first network node, the receiving unit receives a certificate for the first network node from the certificate management server, the certificate including a signature for the public key, and the transmitting unit transmits the registration request including the public key to the certificate management server.

3. The network node of claim 2, wherein the control unit generates the first network node using the certificate chain, the private key, the public key, and the certificate.

4. The network node of claim 3, wherein the certificate is used in authorizing the authority of the first network node.

5. A network node according to any one of claims 1 to 4, wherein the certificate management server is present within a mobile core network.

6. A communication method executed by a network node that manages communications between network nodes in a mobile core network, comprising the steps of: receiving a generation request from a first network node; confirming a second network node with which the first network node communicates; sending a request to obtain a certificate chain for the first network node and the second network node to a certificate management server, and sending a registration request for the first network node to an authorization server.

Citation Information

Patent Citations

  • Method and system for establishing secure channel

    CN106302394A

  • Certificate acquisition method and device

    JP2017521971A