Network node and communication method

Abstract

This network node comprises: a transmission unit that transmits a first message including a certain attribute to another network node in a first transport layer security (TLS) session for control; a reception unit that receives, from the other network node in the first TLS session, a second message that is a response to the first message; and a control unit that establishes, with the other network node, a second TLS session for signal transmission to which an encryption method negotiated in the first TLS session is applied. The control unit determines a method for establishing the second TLS session on the basis of whether the second message includes the attribute.

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 and Non-Patent Document 2).

[0004] 3GPP TS 23.501 V18.4.0 (2023-12)3GPP TS 23.502 V18.4.0 (2023-12)3GPP TS 29.573 V18.4.0 (2023-12)

[0005] 5GC defines N32 as the interface between operators. When NFs of a visited public land mobile network (VPLMN) and a home public land mobile network (HPLMN) communicate, an N32 connection is established between devices called SEPPs (Security Edge Protection Proxy) located at the network boundary, and necessary signals are included in the communication path. The two PLMNs communicate with each other as relay devices (equivalent to an HTTP proxy + alpha) that add security functions to SEPP.

[0006] N32 consists of two types of interfaces: N32-c for control and N32-f for signal transmission. The specifications have been expanded so that N32-c and N32-f can be operated on different devices. However, if devices that support this specification are mixed with devices that do not support it, it may not be possible to establish N32-f.

[0007] The present invention has been made in view of the above points, and has as its object to more reliably establish a signal transmission session.

[0008] According to the disclosed technology, there is provided a network node having a transmitter that transmits a first message including a certain attribute to another network node in a first TLS (Transport layer security) session for control, a receiver that receives a second message that is a response to the first message from the other network node in the first TLS session, and a controller that establishes a second TLS session for signal transmission with the other network node, applying an encryption method negotiated in the first TLS session, wherein the controller determines a method for establishing the second TLS session based on whether the second message includes the attribute.

[0009] According to the disclosed technology, a signal transmission session can be established more reliably.

[0010] FIG. 1 is a diagram for explaining an example of a communication system. FIG. 1 is a diagram for explaining an example (1) of a communication system in a roaming environment. FIG. 2 is a diagram for explaining an example (2) of a communication system in a roaming environment. FIG. 2 is a diagram for explaining a communication signal between operators. FIG. 1 is a diagram for explaining a configuration example (1) of N32-c. FIG. 1 is a diagram for explaining a configuration example (1) of N32-f. FIG. 1 is a diagram for explaining a configuration example (2) of N32-c. FIG. 1 is a diagram for explaining a configuration example (2) of N32-f. FIG. 1 is a diagram for explaining a configuration example (1) of N32. FIG. 1 is a diagram for explaining a configuration example (2) of N32. FIG. 1 is a diagram for explaining a configuration example (3) of N32. FIG. 1 is a diagram for explaining a configuration example (1) of N32 in an embodiment of the present invention. FIG. 2 is a diagram for explaining a configuration example (2) of N32 in an embodiment of the present invention. FIG. 2 is a diagram for explaining a configuration example (3) of N32 in an embodiment of the present invention. A diagram for illustrating an example of the functional configuration of a base station 10 in an embodiment of the present invention. A diagram for illustrating an example of the functional configuration of a terminal 20 in an embodiment of the present invention. A diagram for illustrating an example of the hardware configuration of a base station 10 and a terminal 20 in an embodiment of the present invention. A diagram for illustrating an example of the configuration of a vehicle 2001 in an embodiment of the present invention.

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

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

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

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

[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 may be configured.

[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 for explaining an example (1) 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 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. The VPLMN may be referred to as a visited network, and the HPLMN may be referred to as a home network.

[0023] Figure 2 shows an example of a local breakout scenario where user data is connected to a DN in a visited network. Control signals are exchanged between the visited and home networks via SEPP.

[0024] Figure 3 is a diagram illustrating an example (2) of a communication system in a roaming environment. Figure 3 shows an example of a home routed scenario in which user data is connected to a DN in a home network. Control signals are exchanged between the visited network and the home network via SEPP, similar to the local breakout scenario.

[0025] Fig. 4 is a diagram for explaining communication signals between carriers. As shown in Fig. 4, an NF Consumer (NFc) that uses the services of an NF in another network uses each API provided by an NF Producer (NFp) in the other network via N32-c and N32-f generated by the SEPPs of both networks.

[0026] By using each API, it is possible to query the NRF to discover the NF to communicate with, perform authentication using the AUSF, register status such as location in the UDM, obtain subscriber information, and create, change, and disconnect sessions to the SMF.

[0027] 5GC defines N32 as an interface between operators (see Non-Patent Document 3). When NFs of a visited network (VPLMN) and a home network (HPLMN) communicate, an N32 connection is established between devices called SEPPs located at the boundary of the networks, and necessary signals are included in the communication path. The two PLMNs communicate with each other as relay devices (equivalent to HTTP proxy + alpha) that add security functions to SEPP.

[0028] Currently, N32 consists of two types of interfaces.

[0029] One is N32-c, which is used to control N32 itself. Specifically, it specifies the encryption method used by N32-f and the additional information exchange required for some encryption methods. It is generally generated using TLS (Transport Layer Security).

[0030] The other is N32-f, which is the actual signal exchanged between the NFs of the two operators. N32-f exchanges signals using the encryption method negotiated and determined by N32-c, and although some signals may go through relay devices, they are generally generated using TLS between devices.

[0031] N32 specifies two connection methods: the TLS method and the PRINS (Protocol for N32 Interconnect Security) method. These connection methods are N32-f connection methods, and the difference is whether the relay carrier's equipment can check and operate the N32-f signal content.

[0032] Figure 5 is a diagram for explaining a configuration example (1) of N32-c. As shown in Figure 5, N32-c is used for controlling N32, and negotiates the security capabilities to be used between cSEPP and pSEPP (see Non-Patent Document 3). It negotiates whether to connect N32-f using TLS or PRINS (Application Level Security). This is usually performed when the device is started up, and N32-c is disconnected immediately after the negotiation is complete.

[0033] 6 is a diagram illustrating a configuration example (1) of N32-f. As shown in FIG. 6, N32-f is used for signal transmission of N32, and is a connection for ensuring security between cSEPP and pSEPP in communication between cNF and pNF. When N32-f is TLS, HTTP signals are transmitted on a layer encrypted by TLS.

[0034] FIG. 7 is a diagram illustrating a configuration example (2) of N32-c. As shown in FIG. 7, N32-c is used for controlling N32, and negotiates the security capabilities to be used between cSEPP and pSEPP. It also negotiates whether to connect N32-f using TLS or PRINS (Application Level Security). This is usually performed when the device is started up, and N32-c is disconnected immediately after the negotiation is complete. If N32-f uses PRINS, it can be routed via an intermediary device.

[0035] 8 is a diagram for explaining a configuration example (2) of N32-f. As shown in FIG. 6, N32-f is for signal transmission of N32, and is a connection for ensuring security between cSEPP and pSEPP in communication between cNF and pNF. When N32-f uses PRINS, it becomes possible to provide additional services by instructing an intermediary to change some parameters when relaying a signal.

[0036] FIG. 9 is a diagram illustrating an example of an N32 configuration (1). In Rel-18, senderN32fFqdn and senderN32fPortList were added so that N32-c FQDNs and N32-f ports other than the designated port can be used (see Non-Patent Document 3). senderN32fFqdn indicates a specific FQDN (Fully Qualified Domain Name) of the initiating SEPP that the initiating SEPP expects from the responding SEPP to establish an N32-f connection. senderN32fPortList indicates a specific port number that the initiating SEPP expects from the responding SEPP to use for the N32-f connection. This addition ensures the flexibility to separate the SEPP processing units and operate N32-c and N32-f on different devices.

[0037] 9, the initiating SEPP (cSEPP AAA) receives N32-f at cSEPP CCC by including senderN32fFqdn (=CCC) and senderN32fPortList in the HTTP Request signal. Similarly, the responding SEPP (pSEPP BBB) receives N32-f at pSEPP DDD by including senderN32fFqdn (=DDD) and senderN32fPort in the HTTP Response signal.

[0038] The cSEPP and pSEPP establish a TLS session for N32-f in accordance with the senderN32fFqdn and senderN32fPort / senderN32fPortList of the other party received by N32-c, and perform communication.

[0039] Here, when a SEPP that supports the extended N32-c is combined with an older SEPP (pre-Rel-17) that does not support the extended N32-c, the FQDN and port for establishing the N32-f cannot be recognized and the N32-f cannot be established. In other words, signals cannot be transmitted through the NF between operators. This is because the SEPP that sent the senderN32fFqdn and senderN32fPortList waits for a connection (for the required TLS) only on that port, assuming that the other party supports it.

[0040] 10 is a diagram for explaining an example of an N32 configuration (2). As shown in FIG. 10, when cSEPP supports Rel-18 and pSEPP supports Rel-17, the cSEPP side prepares to receive an N32-f connection with CCC, and therefore cannot receive it with the AAA assumed by pSEPP. Since the pSEPP side only understands AAA and does not know about the existence of CCC, it cannot establish an N32-f connection with CCC.

[0041] 11 is a diagram for explaining an example of an N32 configuration (3). As shown in FIG. 11, when cSEPP supports Rel-17 and pSEPP supports Rel-18, the cSEPP side only understands BBB and does not know about the existence of DDD, so it cannot establish an N32-f connection with DDD. Since the cSEPP side recognizes the N32-f connection only through BBB, it cannot support DDD.

[0042] Therefore, a new Attribute is added to the HTTP Request signal and the HTTP Response signal to realize a mechanism that enables mutual recognition of support. This is made possible by adding a new Attribute (supportOfSenderN32) to the HTTP Request signal, where the initiating SEPP (the requesting side of N32-c) notifies the receiving side that it supports senderN32fFqdn and senderN32fPort, and intends to apply the values ​​when receiving the response. The responding SEPP (the responding side of N32-c) notifies the receiving side by adding a new Attribute (supportOfSenderN32) to the HTTP Response signal, indicating that it supports senderN32fFqdn and senderN32fPortList as the receiving side and that it understands and operates based on the values ​​received from the initiating SEPP.

[0043] Upon receiving the notification of the new Attribute from the responding SEPP, the initiating SEPP can confirm that the senderN32fFqdn and senderN32fPortList sent by its own device have been interpreted.

[0044] The responding SEPP can confirm that the initiating SEPP supports and intends to receive the senderN32fFqdn and senderN32fPort, and can therefore confirm that the initiating SEPP will reliably process the senderN32fFqdn and senderN32fPort notified by its own device.

[0045] Fig. 12 is a diagram for explaining a configuration example (1) of N32 in an embodiment of the present invention, which shows an operation example when both cSEPP and pSEPP support Rel-18.

[0046] In the new Attribute(supportOfSenderN32), the cSEPP knows that the pSEPP supports and intends to receive the senderN32fFqdn and senderN32fPortList as the receiving side.

[0047] When the cSEPP receives a new Attribute (supportOfSenderN32) via an HTTP Response, it can be determined that the senderN32fFqdn and senderN32fPortList sent by the cSEPP in the HTTP Request have been reliably processed.

[0048] If the HTTP Response does not include the new Attribute (supportOfSenderN32), cSEPP will assume that the pSEPP did not interpret it and will handle it in the same way as before Rel-17 (=sender attribute).

[0049] If the HTTP Request contains a new Attribute (supportOfSenderN32), pSEPP knows that cSEPP supports and is willing to receive senderN32fFqdn and senderN32fPort as a receiver.

[0050] The pSEPP knows that if it sends senderN32fFqdn and senderN32fPort, they will be reliably processed by the cSEPP, so it can send them as needed.

[0051] If a new Attribute (supportOfSenderN32) is not included in the HTTP Request, the pSEPP does not need to send the senderN32fFqdn and senderN32fPort to the cSEPP.

[0052] 13 is a diagram for explaining a configuration example (2) of N32 in an embodiment of the present invention. Fig. 13 shows an operation example in which cSEPP supports Rel-18 and pSEPP supports Rel-17.

[0053] As shown in FIG. 13, cSEPP determines that the HTTP Response does not contain a new Attribute (supportOfSenderN32), and therefore pSEPP does not interpret it, and handles it using the behavior (=sender attribute) of before Rel-17.

[0054] Fig. 14 is a diagram for explaining a configuration example (3) of N32 in an embodiment of the present invention. Fig. 14 shows an operation example in which cSEPP supports Rel-17 and pSEPP supports Rel-18.

[0055] 14, since the HTTP Request did not include a new Attribute (supportOfSenderN32), even if the pSEPP notified the cSEPP of the senderN32fFqdn and senderN32fPort, the senderN32fFqdn and senderN32fPort would not be interpreted and the necessary processing would not be performed. Therefore, the pSEPP does not need to send the senderN32fFqdn and senderN32fPort to the cSEPP.

[0056] According to the above embodiment, the initiating SEPP receives a notification of a new Attribute from the responding SEPP and can confirm that the senderN32fFqdn and senderN32fPortList it sent have been interpreted. The responding SEPP can confirm that the initiating SEPP supports and intends to receive the senderN32fFqdn and senderN32fPort, and can therefore reliably confirm that the initiating SEPP will process the senderN32fFqdn and senderN32fPort it notifies.

[0057] That is, a signal transmission session can be established more reliably.

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

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

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

[0061] 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 the information from the storage device as needed. The content of the setting information includes, for example, settings related to the operations described in the embodiments.

[0062] As described in the embodiments, the control unit 140 performs processing related to the operations described in the embodiments. 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.

[0063] <Terminal 20> Fig. 16 is a diagram showing an example of the functional configuration of the terminal 20. As shown in Fig. 16, 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. 16 is merely an example. The names of the functional divisions and functional units may be any as long as they can perform the operations related to the embodiment of the present invention.

[0064] The transmitter 210 creates a transmission signal from the 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 NR-PSS, NR-SSS, NR-PBCH, DL / UL control signals, reference signals, etc. transmitted from the network node 30.

[0065] The setting unit 230 stores various setting information received from the network node 30 by the receiving unit 220 in a storage device and reads it from the storage device as needed. The setting unit 230 also stores setting information that is set in advance. The content of the setting information is, for example, settings related to the operations described in the embodiments.

[0066] The control unit 240 performs processing related to the operations described in the embodiments as described in the embodiments. The control unit 240 also performs processing related to the capacity-enhanced cell. 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.

[0067] (Hardware Configuration) The block diagrams (FIGS. 15 and 16) 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.

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

[0069] For example, 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. 17 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.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0084] 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 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 provides various types of multimedia information and multimedia services to the occupants of the vehicle 2001 by using information acquired from external devices via the communication module 2013, etc.

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

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

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

[0088] The communication module 2013 transmits, via wireless communication to an external device, a current signal from the current sensor that is input to the electronic control unit 2010. The communication module 2013 also transmits, via wireless communication to an external device, the rotation speed signals of the front and rear wheels acquired by a rotation speed sensor 2022, the air pressure signals of the front and rear wheels acquired by an air pressure sensor 2023, the vehicle speed signal acquired by a vehicle speed sensor 2024, the acceleration signal acquired by an acceleration sensor 2025, the accelerator pedal depression amount signal acquired by an accelerator pedal sensor 2029, the brake pedal depression amount signal acquired by a brake pedal sensor 2026, the shift lever operation signal acquired by a shift lever sensor 2027, and detection signals for detecting obstacles, vehicles, pedestrians, etc. acquired by an object detection sensor 2028, all of which are input to the electronic control unit 2010.

[0089] The communication module 2013 receives various information (traffic information, traffic signal information, vehicle distance information, etc.) transmitted from external devices and displays it on the information service unit 2012 provided in the vehicle 2001. The communication module 2013 also stores the various information received from the 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.

[0090] (Summary of Embodiments) As described above, according to the embodiments of the present invention, there is provided a network node having a transmitter that transmits a first message including an attribute to another network node in a first transport layer security (TLS) session for control, a receiver that receives a second message that is a response to the first message from the other network node in the first TLS session, and a controller that establishes with the other network node a second TLS session for signal transmission that applies an encryption method negotiated in the first TLS session, wherein the controller determines a method for establishing the second TLS session based on whether the second message includes the attribute.

[0091] With the above configuration, the initiating SEPP receives notification of a new Attribute from the responding SEPP and can confirm that the senderN32fFqdn and senderN32fPortList it sent have been interpreted. The responding SEPP can confirm that the initiating SEPP supports and intends to receive the senderN32fFqdn and senderN32fPort, and can therefore reliably confirm that the initiating SEPP will process the senderN32fFqdn and senderN32fPort it notifies. In other words, a signal transmission session can be established more reliably.

[0092] The control unit may set the attribute to an attribute indicating support for specifying a fully qualified domain name (FQDN) and port for the second TLS session. With this configuration, the initiating SEPP can confirm that the senderN32fFqdn and senderN32fPortList sent by the initiating SEPP have been interpreted upon receiving a new Attribute from the responding SEPP. The responding SEPP can confirm that the initiating SEPP supports and intends to receive the senderN32fFqdn and senderN32fPort, and can therefore reliably confirm that the initiating SEPP will process the senderN32fFqdn and senderN32fPort notified by the responding SEPP.

[0093] The control unit may include a fully qualified domain name (FQDN) and port related to the second TLS session in the first message. With this configuration, the initiating SEPP can receive a notification of a new Attribute from the responding SEPP and confirm that the senderN32fFqdn and senderN32fPortList sent by the initiating SEPP have been interpreted. The responding SEPP can confirm that the initiating SEPP supports and intends to receive the senderN32fFqdn and senderN32fPort, and can therefore reliably confirm that the initiating SEPP will process the senderN32fFqdn and senderN32fPort notified by the responding SEPP.

[0094] Furthermore, according to an embodiment of the present invention, there is provided a network node having a receiving unit that receives a first message from another network node in a first TLS (Transport layer security) session for control, a transmitting unit that transmits a second message that is a response to the first message to the other network node in the first TLS session, and a control unit that establishes a second TLS session with the other network node for signal transmission, applying an encryption method negotiated in the first TLS session, wherein the control unit determines a method for establishing the second TLS session based on whether the first message includes a certain attribute.

[0095] With the above configuration, the initiating SEPP receives notification of a new Attribute from the responding SEPP and can confirm that the senderN32fFqdn and senderN32fPortList it sent have been interpreted. The responding SEPP can confirm that the initiating SEPP supports and intends to receive the senderN32fFqdn and senderN32fPort, and can therefore reliably confirm that the initiating SEPP will process the senderN32fFqdn and senderN32fPort it notifies. In other words, a signal transmission session can be established more reliably.

[0096] The control unit may set the attribute to an attribute indicating support for specifying a fully qualified domain name (FQDN) and port for the second TLS session. With this configuration, the initiating SEPP can confirm that the senderN32fFqdn and senderN32fPortList sent by the initiating SEPP have been interpreted upon receiving a new Attribute from the responding SEPP. The responding SEPP can confirm that the initiating SEPP supports and intends to receive the senderN32fFqdn and senderN32fPort, and can therefore reliably confirm that the initiating SEPP will process the senderN32fFqdn and senderN32fPort notified by the responding SEPP.

[0097] Furthermore, according to an embodiment of the present invention, there is provided a communication method in which a network node executes the following procedures: a procedure of transmitting a first message including a certain attribute to another network node in a first TLS (Transport Layer Security) session for control; a procedure of receiving a second message that is a response to the first message from the other network node in the first TLS session; a procedure of establishing a second TLS session with the other network node for signal transmission, applying an encryption method negotiated in the first TLS session; and a procedure of determining a method of establishing the second TLS session based on whether the second message includes the attribute.

[0098] With the above configuration, the initiating SEPP receives notification of a new Attribute from the responding SEPP and can confirm that the senderN32fFqdn and senderN32fPortList it sent have been interpreted. The responding SEPP can confirm that the initiating SEPP supports and intends to receive the senderN32fFqdn and senderN32fPort, and can therefore reliably confirm that the initiating SEPP will process the senderN32fFqdn and senderN32fPort it notifies. In other words, a signal transmission session can be established more reliably.

[0099] (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. Two or more items may be used in combination as needed, and items described in one item may apply to items 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 physical component boundaries. The operations of multiple functional units may be physically performed by a single component, or the operations of a single functional unit may be physically performed by multiple 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 network node 30 and the terminal 20 have been described using functional block diagrams. However, such devices may be realized by hardware, software, or a combination thereof. The software operated by the processor of the network node 30 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 any suitable storage medium, such as random access memory (RAM), flash memory, read-only memory (ROM), EPROM, EEPROM, registers, hard disk (HDD), removable disk, CD-ROM, database, server, or the like.

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

[0101] Each aspect / embodiment described in the present disclosure may be applied to at least one of systems using LTE (Long Term Evolution), LTE-Advanced (LTE-A), SUPER 3G, IMT-Advanced, 4G (4th generation mobile communication system), 5G (5th generation mobile communication system), FRA (Future Radio Access), NR (New Radio), 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.20, UWB (Ultra-Wide Band), Bluetooth (registered trademark), or other suitable systems, and next-generation systems enhanced based on these. Furthermore, a combination of multiple systems (e.g., a combination of at least one of LTE and LTE-A with 5G, etc.) may also be applied.

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

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

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

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

[0106] 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 sent to another device.

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

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

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

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

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

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

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

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

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

[0116] 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 remote radio head (RRH)). The terms "cell" or "sector" refer to part or the entire coverage area of ​​a base station and / or base station subsystem that provides communication services within that coverage area.

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

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

[0119] 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 body, the mobile body itself, etc. The mobile body may be a vehicle (e.g., a car, an airplane, etc.), an unmanned mobile body (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 also include devices that do 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.

[0120] 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 above-described network node 30. 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.

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

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

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

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

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

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

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

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

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

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

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

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

[0133] 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 comprising: a transmitter that transmits a first message including a certain attribute to another network node in a first TLS (Transport Layer Security) session for control; a receiver that receives a second message that is a response to the first message from the other network node in the first TLS session; and a controller that establishes a second TLS session with the other network node for signal transmission, applying an encryption method negotiated in the first TLS session, wherein the controller determines how to establish the second TLS session based on whether the second message includes the attribute.

2. The network node according to claim 1, wherein the control unit sets the attribute to an attribute indicating that the control unit supports specification of a fully qualified domain name (FQDN) and a port related to the second TLS session.

3. The network node according to claim 1, wherein the control unit includes an FQDN (Fully Qualified Domain Name) and a port related to the second TLS session in the first message.

4. A network node comprising: a receiving unit that receives a first message from another network node in a first TLS (Transport layer security) session for control; a transmitting unit that transmits a second message that is a response to the first message to the other network node in the first TLS session; and a control unit that establishes a second TLS session with the other network node for signal transmission, applying an encryption method negotiated in the first TLS session, wherein the control unit determines how to establish the second TLS session based on whether the first message includes a certain attribute.

5. The network node according to claim 4, wherein said control unit sets said attribute to an attribute indicating that specification of a fully qualified domain name (FQDN) and a port related to said second TLS session is supported.

6. A communications method in which a network node executes the following steps: sending a first message including a certain attribute to another network node in a first TLS (Transport Layer Security) session for control; receiving a second message that is a response to the first message from the other network node in the first TLS session; establishing a second TLS session with the other network node for signal transmission, applying the encryption method negotiated in the first TLS session; and determining how to establish the second TLS session based on whether the second message includes the attribute.

Images