Terminal and network node

Abstract

This terminal comprises: a transmission unit that transmits, to a network, a connection request message which includes a certificate with personal data stored therein; and a control unit that, after authentication processing using the certificate is performed for the network, executes a post-authentication processing network registration procedure. The transmission unit encrypts the certificate or the connection request message with a public key for the network and transmits the encrypted certificate or connection request message.

Description

Terminals and network nodes

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

[0002] 3GPP (registered trademark) (3rd Generation Partnership Project) has introduced 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. 5G introduces various wireless technologies to meet the requirement of achieving a throughput of 10 Gbps or more while reducing latency in wireless sections to 1 ms or less. Furthermore, 6G, a future communication system, is also being studied.

[0003] In recent years, a new approach to identity management has been under consideration, namely the concept of Self-Sovereign Identity (SSI), in which users manage their own identifiers and identities and control who provides them, without relying on centralized identity providers (ID providers), and the technologies to realize this (W3C Decentralized Identifiers (DID), W3C Verifiable Credentials (VC), etc.).

[0004] In the world of SSI, for example, a user can present an attribute / credentials certificate that certifies attribute information and qualification information to a service provider, and the service provider can then make decisions about providing services to the user.

[0005] 3GPP TS 23.502 V18.3.0 (2023-09)W3C Decentralized Identifiers (DIDs) v1.0, https: / / www.w3.org / TR / did-core / W3C Verifiable Credentials Data Model v1.1, https: / / www.w3.org / TR / vc-data-model /

[0006] In conventional telecommunications carrier networks (NWs), authentication for connecting a terminal (which may also be called UE) to the NW is performed based on a SUPI included in a SIM card attached to the terminal.

[0007] However, in conventional networks, there is no mechanism for realizing network connection of a terminal based on authentication based on attributes / credentials.

[0008] The present invention has been made in consideration of the above points, and aims to provide a technology that enables a terminal to connect to a network based on authentication based on attributes / credentials.

[0009] According to the disclosed technology, a terminal is provided that includes: a transmitting unit that transmits a connection request message including a certificate storing personal data to a network; and a control unit that, after an authentication process using the certificate is performed in the network, executes a registration procedure to the network after the authentication process, wherein the transmitting unit encrypts the certificate or the connection request message with the public key of the network and transmits it.

[0010] According to the disclosed technology, a technology is provided that enables a terminal to connect to a network based on authentication based on attributes / credentials.

[0011] FIG. 1 is a diagram for explaining an example of a communication system. FIG. 1 is a diagram for explaining an example of a communication system in a roaming environment. FIG. 2 is a diagram for explaining an example of a system configuration common to the first to third embodiments. FIG. 2 is a diagram for explaining processing sequence example 1 in the first embodiment. FIG. 3 is a diagram for explaining the authentication processing of S106 in processing sequence example 1 in the first embodiment. FIG. 4 is a diagram for explaining processing sequence example 2 in the first embodiment. FIG. 5 is a diagram for explaining the authentication processing of S107 in processing sequence example 2 in the first embodiment. FIG. 6 is a diagram for explaining processing sequence example 1 in the second embodiment. FIG. 7 is a diagram for explaining the authentication processing of S213 in processing sequence example 1 in the second embodiment. FIG. 8 is a diagram for explaining the authentication processing of S214 in processing sequence example 2 in the second embodiment. FIG. 9 is a diagram for explaining processing sequence example 1-1 in the third embodiment. FIG. 10 is a diagram for explaining the authentication processing of S308 in processing sequence example 1-1 in the third embodiment. FIG. 11 is a diagram for explaining processing sequence example 1-2 in the third embodiment. FIG. 12 is a diagram for explaining existing 3GPP Key hierarchy generation processing. FIG. 13 is a diagram for explaining processing sequence example 2-1 in the third embodiment. FIG. 14 is a diagram for explaining the authentication processing of S309 in processing sequence example 2-1 in the third embodiment. FIG. 10 is a diagram showing a processing sequence example 2-2 in the third embodiment. FIG. 11 is a diagram showing an example of the functional configuration of the network node 100 in the embodiment of the present invention. FIG. 12 is a diagram showing an example of the functional configuration of the terminal 20 in the embodiment of the present invention. FIG. 13 is a diagram showing an example of the hardware configuration of the terminal 20 and the network node 100 in the embodiment of the present invention. FIG. 14 is a diagram showing an example of the configuration of a vehicle 2001 in the 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 technologies are used as appropriate. However, the existing technologies include, but are not limited to, the existing LTE or the existing NR.

[0014] In the following, we will first explain an example of the configuration of a 5G core network, which is an example of a network in which attribute / credential certificate-based authentication is performed in this embodiment, and then explain the configuration and operation related to this embodiment.

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

[0016] The (R)AN (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 20, an AMF (Access and Mobility Management Function) 30, and a UPF (User plane function). The AMF 30 is a network node 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 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 DN constitute a network slice.

[0017] The AMF 30 is connected to the UE 20, the (R)AN 10, an SMF (Session Management function), an NSSF (Network Slice Selection Function), an NEF (Network Exposure Function), an NRF (Network Repository Function), an UDM (Unified Data Management), an AUSF (Authentication Server Function), a PCF (Policy Control Function), and an AF (Application Function). The AMF 30, the SMF, the NSSF, the NEF, the NRF, the UDM 40, the AUSF 80, the PCF, and the AF are network nodes connected to each other via interfaces, Namf, Nsmf, Nnssf, Nnef, Nnrf, Nudm, Nausf, Npcf, and Naf, based on their respective services.

[0018] The SMF is a network node 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 having functions such as selecting a network slice to which the UE 20 connects, determining the allowed NSSAI (Network Slice Selection Assistance Information), determining the NSSAI to be set, and determining the AMF set to which the UE 20 connects. The PCF is a network node having a function of controlling network policies. The AF is a network node having a function of controlling application servers. The NRF is a network node having a function of discovering NF instances that provide services. The UDM 40 is a network node that manages subscriber data and authentication data. The UDM 40 is connected to a UDR (User Data Repository) that stores the data.

[0019] 2 is a diagram for explaining an example of a communication system in a roaming environment. As shown in Fig. 2, the network is made up of a UE, which is a terminal 20, and a plurality of network nodes.

[0020] The SEPP is a non-transparent proxy that filters control plane messages between PLMNs (Public Land Mobile Networks). The vSEPP shown in Figure 2 is a SEPP in a visited network, and the hSEPP is a SEPP in a home network.

[0021] As shown in Fig. 2, the UE 20 is in a roaming environment connected to an (R)AN and an AMF 30 in a Visited PLMN (VPLMN). The VPLMN and the Home PLMN (HPLMN) are connected via a vSEPP and an hSEPP. The UE 20 can communicate with the UDM of the HPLMN via the AMF 30 of the VPLMN, for example.

[0022] (About SSI) As mentioned above, in recent years, the concept of Self-Sovereign Identity (SSI) and the technologies to realize it (W3C Decentralized Identifiers (DID), W3C Verifiable Credentials (VC), etc.) have been considered as a new approach to identity management, in which users manage their own identifiers and identities and control who provides them, without relying on centralized identity providers (ID providers).

[0023] In the world of SSI, there are three parties: Holder, Issuer, and Verifier. A Holder is a user who manages / possesses their own digital identity. An Issuer certifies attribute information (name, age, address, etc.) and qualification information (employee of a company, membership of a service, etc.) to a user, and then issues an attribute / qualification certificate (e.g., VC). A Verifier verifies the Holder's attributes and qualifications by requesting and receiving the attribute / qualification certificate (VC) necessary to provide a service, and makes decisions about providing the service.

[0024] An example of an attribute / credential certificate is a VC (Verifiable Credentials). A VC is a signed document that stores personal data. The above attribute information and credential information are examples of personal data. An attribute / credential certificate may also be called a certificate that stores personal data. Furthermore, a certificate that stores personal data does not necessarily need to contain information that can uniquely identify an individual; for example, something like a membership card issued anonymously also falls under the category of a certificate that stores personal data.

[0025] Furthermore, for example, DIDs (Decentralized Identifiers) are used as identifiers for issuers and holders. DIDs are registered in a distributed ledger and are easily accessible but difficult to tamper with.

[0026] (Regarding the Issues) In conventional networks (NWs) of telecommunications carriers, authentication for connecting a UE to the NW is performed based on a SUPI included in a SIM card attached to the UE.

[0027] By performing network connection of a UE based on authentication based on attributes / credentials using DID, VC, etc., the following becomes possible, for example.

[0028] - Meeting the need for self-sovereign identity management - Simplifying user identity verification (e.g., KYC) using user attribute / credential certificates certified by a third party other than the telecommunications carrier - Realizing new network connection services for specific service subscribers - Network usage by a variety of UEs without relying on SIM However, in conventional 3GPP networks, there is no mechanism to realize network connection of UEs based on authentication based on attribute / credential certificates.

[0029] Hereinafter, a first embodiment, a second embodiment, and a third embodiment will be described as technologies for solving the above problems. First, an "overview of the embodiments" and an "example of system configuration" will be described as matters common to the first embodiment, the second embodiment, and the third embodiment, and then each of the first embodiment, the second embodiment, and the third embodiment will be described. Note that the first embodiment, the second embodiment, and the third embodiment can be implemented in any combination.

[0030] (Outline of the embodiment) First, an outline of the embodiment will be described. In this embodiment, a NW registration authentication function (authentication function based on attributes / credentials) using attributes / credentials such as VC is added to a 3GPP NW. In this embodiment, two patterns are assumed for this authentication function: one in which it is defined as a new Network Function (NF) and one in which it extends an existing function such as AUSF.

[0031] The "3GPP NW" may be called a core network defined by 3GPP (registered trademark). In addition, in this embodiment, the "3GPP NW" is taken as the "network" for description, but the technology according to the present invention is applicable to networks not limited to the "3GPP NW."

[0032] In each embodiment, a specific example of authentication logic using attributes / credentials will be described, but this authentication logic is merely an example and the present invention is not limited to this authentication logic.

[0033] In this embodiment, an IF (C-Plane) related to NW registration using attributes / credentials between a UE and a 3GPP network is added to an existing 3GPP network. Specifically, the IF is as follows: (1) and (2).

[0034] (1) An interface is added to transmit attributes / credentials from the UE to the 3GPP network via C-Plane communication. There are two patterns: one is defined as a new interface, and the other is added as information to be transmitted via a Registration Request.

[0035] (2) An interface is added for notifying the result from the authentication function that performs authentication processing using attributes / credentials to the UE. There are two patterns: one is defined as a new interface, and the other is an extension of an existing interface.

[0036] In addition, in this embodiment, logic for permitting NW registration and establishing communication with D-Plane after successful authentication using attributes / credentials is added.

[0037] In addition, in this embodiment, by utilizing the information of the attribute / qualification certificate, it is possible to register subscriber information in the UDM so that billing, etc. This subscriber information registration function has been explained in the first embodiment, but in the second and third embodiments, it is also possible to register in the UDM using this subscriber information registration function.

[0038] (System Configuration Example) FIG. 3 shows an example of a system configuration common to the first to third embodiments. As shown in FIG. 3, the communication system according to this embodiment includes a UE 20, an (R)AN 10, an authentication function 60 that performs authentication based on attributes / credentials, a UDM / UDR (40), and a VDR (Verifiable Data Registry) 70. Note that the UDM 40 is described as UDM / UDR because it is used together with the UDR. The "authentication function 60" shown here may be a newly defined device (network node) or may be an extension of the function of an existing device (e.g., AUSF). Note that in the explanation of each embodiment, the "authentication function 60" is described as a newly defined device (network node).

[0039] The UE 20 includes a network connection function 21. The network connection function 21 executes operations in each sequence described below. The UE 20 may also be referred to as a terminal 20.

[0040] As shown in FIG. 3, the UDM / UDR ( 40 ) includes a network information database (DB) 41 , a certificate information DB 42 , and a policy DB 43 .

[0041] The NW information DB 41 stores a NW identifier, a NW public key, and a NW private key. The certificate information DB 42 stores information on certificates that can be used for NW connection. The policy DB 43 stores an authentication method selection policy. Note that the above NW is a 3GPP NW, and for example, in the case of a "NW identifier" (the same applies to the NW public key and NW private key), it may be an identifier common to multiple network nodes in the 3GPP NW, or it may be an identifier used for a specific network node in the 3GPP NW.

[0042] In this embodiment, the VDR 70 is arranged outside the 3GPP network. However, the present invention is not limited to a configuration in which the VDR 70 is arranged outside the 3GPP network, and the VDR 70 may be provided within the 3GPP network.

[0043] The VDR 70 is a device that can be realized by a web server, a distributed ledger, etc. The VDR 70 includes a user information DB 71, an issuer information DB 72, a definition information DB 73, and a management information DB 74.

[0044] The user information DB 71 stores user identifiers and user public keys. The issuer information DB 72 stores identifiers of issuers of attribute / credential certificates used for network connection authentication and the public keys of the issuers. The definition information DB 73 stores schemas and definition information of attribute / credential certificates. The management information DB 74 stores management information indicating the validity / invalidation of attribute / credential certificates.

[0045] Note that "user" and "UE" (or "terminal") may be used interchangeably. Unless a contradiction occurs in the context, "user" described below may be replaced with "UE" or "terminal."

[0046] (First embodiment: overview) First, the first embodiment will be described. The first embodiment is the most basic embodiment. Below, an example in which the authentication function 60, which is a newly defined network node, is used as the "authentication function," will be described as processing sequence example 1, and an example in which the AUSF 80 is used as the "authentication function" will be described as processing sequence example 2.

[0047] (First embodiment: processing sequence example 1) Processing sequence example 1 in the first embodiment will be described with reference to Fig. 4. Processing sequence example 1 is an example in which a new NF and a new IF are used. The processing is premised on the following:

[0048] A user has a public key / private key pair corresponding to his / her own identifier, and stores his / her own identifier and public key in association with each other in a VDR 70 located in a place accessible by the 3GPP NW.

[0049] A user has attributes / credentials (which can be used for network connection) issued by any entity (such as a company or another user).

[0050] The certificate issuer holds a public key / private key pair corresponding to its own identifier, and stores its own identifier and public key in association with each other in a VDR 70 located in a place accessible to the 3GPP network.

[0051] The certificate issuer stores the format (schema or definition) of the certificate it issues and information for verifying the validity of the certificate in the VDR 70 located in a place accessible to the 3GPP network. The sequence will be described below.

[0052] In S101 (step 101) of FIG. 4, a NW connection process using an attribute / credential certificate is started when a user operates a NW connection application or when the UE 20 is turned on.

[0053] In S102, the UE 20 transmits a NW connection request message to the (R)AN 20 of the 3GPP network, requesting a network connection using attributes / credentials, including a user identifier (e.g., DID) and user attributes / credentials (e.g., VC). A signature (e.g., VP: Verifiable Presentation) generated by the UE 20 using a private key corresponding to the user identifier is added to the network connection request message. Note that the "network connection request message" may also be referred to as a "connection request message." Examples of the "connection request message" include a Registration Request message, which will be described later.

[0054] The NW connection request message includes information used for authentication as well as information similar to the information included in a Registration Request message, which is a message when a NW connection authentication request is made by SUPI / SUCI.

[0055] In S103, (R)AN20 transfers the NW connection request message received from UE20 to AMF30.

[0056] In S104, when the AMF 30 receives a NW connection request message requesting a NW connection using an attribute / credential certificate, the AMF 30 selects, as an authentication request destination, the authentication function 60. In S105, the AMF 30 transmits, to the authentication function 60, an authentication request message including the attribute / credential certificate included in the NW connection request message.

[0057] In S106, the authentication function 60 verifies the received attribute / credential by performing authentication processing using the attribute / credential. This processing corresponds to step 9 of 3GPP TS 23.502 4.2.2.2 Registration Procedure. S106'-1 to S106'-3 will be described later.

[0058] In S107, the authentication function 60 transmits an authentication response including the authentication result (success / failure) to the AMF 30.

[0059] In the subsequent step S108, connection processing (which may also be called registration processing) is executed. Specifically, the NW registration processing is completed by executing the processing from step 10 onwards, which is the procedure after the authentication processing in step 9 in 3GPP TS 23.502 4.2.2.2 Registration Procedure (Figure 4.2.2.2.2-1: Registration procedure).

[0060] The processing performed by the UE 20 after step 10 includes, for example, receiving a Registration Accept and sending a Registration Complete.

[0061] After the authentication in S106 is successful, the following steps S106'-1 to S106'-3 may be optionally executed for billing purposes.

[0062] In S106'-1, the authentication function 60 sends a subscriber information registration request to the UDM / UDR (40). The subscriber information registration request includes information such as the received user identifier, the user's name and address included in the received attribute / credentials certificate, etc. The UDM / UDR (40) registers this information as the user's subscriber information and returns a subscriber information registration response in S106'-3.

[0063] In the above optional form, it is assumed that the message sent in S102 includes, in addition to the attribute / credentials used for the NW connection, another attribute / credentials certificate describing information necessary for billing, etc. Note that when "attribute / credentials certificate" is written, it may be interpreted that the "attribute / credentials certificate" includes, in addition to the attribute / credentials certificate used for the NW connection, another attribute / credentials certificate describing information necessary for billing, etc.

[0064] Next, the authentication process of S106 will be described in detail with reference to FIG. 5. Here, as an example of the authentication / verification process logic, verification of an attribute / credential certificate in the W3C DID / VC / VP format is assumed. Note that in each embodiment, authentication process using an attribute / credential certificate is a process for authenticating a user (or terminal 20) using an attribute / credential certificate.

[0065] When the authentication process using the attribute / credential certificate starts, in S106-1 the authentication function 60 requests the VDR 70 for a public key corresponding to the identifier of the certificate issuer (Issuer) and a public key corresponding to the identifier of the user. In S106-2, the VDR 70 responds with these public keys to the authentication function 60.

[0066] In S106-3, the authentication function 60 verifies the authenticity of the certificate issuer's signature and the user's signature, and verifies that the message has not been tampered with.

[0067] Note that communication between the authentication function 60 in the 3GPP network and the VDR 70 outside the 3GPP network may be via a node (e.g., NEF, SCEF) that mediates communication between the authentication function 60 in the 3GPP network and the VDR 70 outside the 3GPP network.

[0068] Regarding S106-1 to S106-3, in more detail, in S106-1 and S106-2, the authentication function 60 receives as input DID0 (certificate issuer identifier) ​​and DID1 (user identifier) ​​included in the received VP / VC, and uses an arbitrary DID Method to obtain (resolve) the DID Document (public key) corresponding to DID0 and the DID Document (public key) corresponding to DID1 from the VDR 70. In S106-3, the authentication function 60 verifies that the VP Holder signature and the VC Issuer signature are each signatures made with private keys linked to the corresponding public keys (validity of the signature, no tampering with the message).

[0069] In S106-4, the authentication function 60 requests information regarding the certificate format and status (such as revocation status) from the VDR 70. In S106-5, the VDR 70 responds with the certificate format and status information. In S106-6, the authentication function 60 verifies the validity of the certificate.

[0070] Regarding S106-4 to S106-6, in more detail, the authentication function 60 acquires the VC schema, definition information, etc. from the VDR 70 and verifies that the VC syntax, etc. is correct. The authentication function 60 also acquires VC validity information / revocation information from the VDR 70 and verifies that the received VC is valid.

[0071] In S106-7, the authentication function 60 requests the UDM / UDR (40) for certificate information that can be used for network connection, and in S106-8, the UDM / UDR (40) responds with the certificate information. In S106-9, the authentication function 60 performs eligibility verification of the certificate. More specifically, the authentication function 60 verifies that the conditions for a VC that can be used for network connection (e.g., that it is a My Number VC and that it contains necessary information (e.g., name, address)) are met. Note that the My Number VC is assumed to be information equivalent to the current My Number that has been converted into VC format.

[0072] If the authentication function 60 determines that all of the above verification results are OK, it determines that the authentication has been successful.

[0073] (First embodiment: processing sequence example 2) Next, processing sequence example 2 in the first embodiment will be described with reference to Fig. 6. Processing sequence example 2 is an example in which an existing NF and an existing IF are extended. In processing sequence example 2, a function for performing authentication based on attributes / credentials is included in the AUSF 80. This function performs the authentication process of S107, which will be described later.

[0074] The UDM 40 holds an authentication method selection function (S105) based on attributes / credentials when selecting an authentication method, and the following information used in the attribute / credentials method.

[0075] NW identifier, and public and private keys associated with the identifier. Certificate information that can be used for NW connection (certificate type, data format, information that should be included in the certificate, etc.). The sequence will be described with reference to FIG. 6 .

[0076] At S101, the UE 20 includes attributes / credentials in a Registration Request message and sends the Registration Request message including the attributes / credentials to the (R)AN 10. At S102, the (R)AN 10 sends the Registration Request message including the attributes / credentials to the AMF / SEAF (30).

[0077] In S103, the AMF / SEAF (30) includes the attributes / credentials in a Nausf_UEAuthentication_Authenticate Request message and sends the Nausf_UEAuthentication_Authenticate Request message including the attributes / credentials to the AUSF 80 as an authentication request.

[0078] In S104, the AUSF 80 includes the attributes / credentials in a Nudm_UEAuthentication_Get Request message and sends the Nudm_UEAuthentication_Get Request message including the attributes / credentials to the UDM / ARPF / SIDF (40) as an authentication request.

[0079] In S105, the UDM / ARPF / SIDF (40) performs authentication method selection. Specifically, if the received message does not contain SUPI or SUCI but does contain attributes / credentials, the UDM / ARPF / SIDF (40) selects authentication based on attributes / credentials as the authentication method. Furthermore, if the received message contains both SUPI or SUCI and attributes / credentials, the UDM / ARPF / SIDF (40) selects an authentication method based on a pre-registered authentication method selection policy or a user request.

[0080] In S106, the UDM / ARPF / SIDF (40) includes a string (e.g., Credential Auth) indicating that the attribute / credential authentication method has been selected in the Nudm_UEAuthentication_Get Response message, and sends the Nudm_UEAuthentication_Get Response message including the string to the AUSF 80.

[0081] In S107, the AUSF 80 performs authentication processing using attributes / credentials.

[0082] In S108, the AUSF 80 includes a string indicating that attribute / credential authentication was successful (e.g., Credential Auth Success) in the Nausf_UEAuthentication_Authenticate Response message, and sends the Nausf_UEAuthentication_Authenticate Response message including the string to the AMF / SEAF (30).

[0083] Thereafter, in S109, the processes from step 10 onward of 3GPP TS 23.502 4.2.2.2 Registration Procedure are executed, and the NW Registration process is completed. In the NW Registration process, the SUPI / SUCI-based API and the SUPI / SUCI-based subscriber information registration process are extended so that they can be executed using the user identifier (DID, etc.) included in the attribute / credentials.

[0084] As with the Registration Request message, attributes / credentials are also added to the Mobility Registration Update / Periodic Registration Update messages.

[0085] The authentication process of S107 will be described in detail with reference to Fig. 7. Here, as in the processing sequence example 1, the verification of attributes / credentials in the W3C DID / VC / VP format is assumed as an example of the verification process logic. In the following sequence, all communications between the AUSF 80 and the VDR 70 or UDM 40 are performed using new C-Plane messages.

[0086] When the authentication process using the attribute / credential certificate is started, in S107-1, the AUSF 80 requests an identifier corresponding to the identifier of the certificate issuer (Issuer) and a public key corresponding to the identifier of the user from the VDR 70. In S107-2, the VDR 70 responds with these public keys to the AUSF 80.

[0087] In S107-3, the AUSF 80 verifies the authenticity of the certificate issuer's signature and the user's signature, and verifies that the message has not been tampered with.

[0088] Note that communication between the AUSF 80 within the 3GPP network and the VDR 70 outside the 3GPP network may be via a node (e.g., NEF, SCEF) that mediates the communication.

[0089] Regarding S107-1 to S107-3, in more detail, in S107-1 and S107-2, AUSF 80 receives DID0 (certificate issuer identifier) ​​and DID1 (user identifier) ​​included in the received VP / VC as input, and uses an arbitrary DID Method to obtain (resolve) the DID Document (public key) corresponding to DID0 and the DID Document (public key) corresponding to DID1 from VDR 70. In S107-3, AUSF 80 verifies that the VP Holder signature and VC Issuer signature are signatures made with private keys linked to those public keys (validity of the signatures, no tampering with the messages).

[0090] In S107-4, the AUSF 80 requests information regarding the certificate format and status (such as revocation status) from the VDR 70. In S107-5, the VDR 70 responds with the certificate format and status information. In S107-6, the AUSF 80 verifies the validity of the certificate.

[0091] Regarding S107-4 to S107-6, in more detail, the AUSF 80 acquires the VC schema, definition information, etc. from the VDR 70 and verifies that the VC syntax, etc. is correct. The AUSF 80 also acquires the VC validity information / revocation information from the VDR 70 and verifies that the received VC is valid.

[0092] In S107-7, the AUSF 80 requests the UDM / UDR (40) for certificate information that can be used for network connection, and in S107-8, the UDM / UDR (40) responds with the certificate information. In S107-9, the AUSF 80 performs eligibility verification of the certificate. More specifically, the AUSF 80 verifies that the conditions for a VC that can be used for network connection (e.g., that it is a My Number VC, and that required information (e.g., name, address) is included) are met.

[0093] If the AUSF 80 determines that all of the above verification results are OK, it determines that the authentication has been successful.

[0094] Note that S107-7 to S107-8 may be omitted by including the certificate information acquired in S107-7 to S107-8 in the message of S106 in FIG. 6 and sending it.

[0095] (Effects of the First Embodiment) The technology according to the first embodiment enables the terminal 20 to connect to the NW based on authentication based on attributes / credentials.

[0096] (Outline of Second Embodiment) Next, a second embodiment will be described. In the second embodiment, a method and an interface for notifying the UE of attributes / credentials to be provided for NW authentication from the NW side and for negotiating the same are added to the basic method described in the first embodiment.

[0097] Below, an example in which the newly defined network node authentication function 60 is used as the "authentication function" will be described as processing sequence example 1, and an example in which AUSF 80 is used as the "authentication function" will be described as processing sequence example 2.

[0098] (Second embodiment: processing sequence example 1) Processing sequence example 1 in the second embodiment will be described with reference to Fig. 8. Processing sequence example 1 is an example in which a new NF and a new IF are used. The processing is premised on the following:

[0099] A user has a public key / private key pair corresponding to his / her own identifier, and stores his / her own identifier and public key in association with each other in a VDR 70 located in a place accessible by the 3GPP NW.

[0100] A user has attributes / credentials (which can be used for network connection) issued by any entity (such as a company or another user).

[0101] The certificate issuer holds a public key / private key pair corresponding to its own identifier, and stores its own identifier and public key in association with each other in a VDR 70 located in a place accessible to the 3GPP network.

[0102] A certificate issuer stores the format (scheme or definition) of the certificate it issues and information for verifying the validity of the certificate in a VDR 70 that exists in a location accessible to the 3GPP network.

[0103] The sequence will be explained below.

[0104] In S201 of FIG. 8, the NW connection process using the attribute / credential certificate is started when the user operates the NW connection application or the UE 20 is powered on, or the like is used as a trigger.

[0105] In S202, the UE 20 transmits a message of a NW connection request to the (R)AN 10 of the 3GPP network, requesting a NW connection using attributes / credentials.

[0106] The NW connection request message may include a user identifier (e.g., DID), and may be sent after signing the message with a private key corresponding to the user identifier.

[0107] In addition to the information used for authentication, the NW connection request message includes the same information as that included in a Registration Request message, which is a message when a NW connection authentication request is made by SUPI / SUCI.

[0108] In S203, (R)AN20 transfers the NW connection request message received from UE20 to AMF30.

[0109] In S204, when the AMF 30 receives a NW connection request message requesting a NW connection using attributes / credentials, the AMF 30 selects the attribute / credential-based authentication function 60 as the authentication request destination. In S205, the AMF 30 transmits an authentication request message requesting authentication based on attributes / credentials to the authentication function 60. Here, it is assumed that the authentication request message does not include attributes / credentials.

[0110] When the authentication function 60 confirms that the received authentication request message does not include attributes / credentials, the authentication function 60 transmits to the AMF 30 a message for requesting the UE 20 to provide attributes / credentials for network connection. The message includes information (conditions) indicating the attributes / credentials to be provided. Examples of the conditions are as follows: The message includes any one or more of the following five pieces of information. Furthermore, the message may include information other than the following five pieces of information.

[0111] - Type of certificate (My Number VC, etc.) - Data format / encoding format of the certificate (W3C VC, JWT, etc.) - Information that should be included in the certificate (name, age, etc.) - Signature algorithm or signature format - Version Note that the information (conditions) indicating the attributes / qualification certificates that can be used for network connection may be held in the storage of the authentication function 60, or may be obtained from information stored in the UDM 40, etc.

[0112] In S207, the AMF 30 transfers the message received from the authentication device 60 to the (R)AN 10. In S208, the (R)AN 10 transfers the message to the UE 20.

[0113] At S209, the UE 20 displays the information contained in the message received from the (R)AN 10 on a display, and the user of the UE 20 confirms the conditions of the requested attributes / credentials.

[0114] If the user agrees to provide the information, at S210, the UE 20 sends a response message including the requested attributes / credentials (e.g., VC) and the user identifier (e.g., DID), along with a signature (e.g., VP) generated by the UE 20 using the private key corresponding to the user's identifier.

[0115] In the above example, the user (person) checks the conditions, but the UE 20 may automatically check the conditions.

[0116] In S211, the (R)AN 10 that has received the response message transfers the response message to the AMF 30. In S212, the AMF 30 transfers the response message to the authentication function 60.

[0117] In S213, the authentication function 60 verifies the received attribute / credential by performing authentication processing using the attribute / credential. In S214, the authentication function 60 transmits an authentication response including the authentication result (success / failure) to the AMF 30.

[0118] In the subsequent step S215, the connection process is executed. Specifically, the process from step 10 onward of 3GPP TS 23.502 4.2.2.2 Registration Procedure is executed to complete the NW registration process.

[0119] Next, details of S213 will be described with reference to Fig. 9. Here, as an example of authentication / verification processing logic, verification of attributes / credentials in W3C DID / VC / VP format is assumed. Note that with regard to authentication processing using attributes / credentials, similar processing is described in each embodiment.

[0120] When the authentication process using the attribute / credential certificate starts, in S213-1 the authentication function 60 requests the VDR 70 for a public key corresponding to the identifier of the certificate issuer (Issuer) and a public key corresponding to the identifier of the user. In S213-2, the VDR 70 responds with these public keys to the authentication function 60.

[0121] In S213-3, the authentication function 60 verifies the authenticity of the certificate issuer's signature and the user's signature and that the message has not been tampered with.

[0122] Note that communication between the authentication function 60 and the VDR 70 may be via a node (e.g., NEF, SCEF) that mediates communication between the authentication function 60 within the 3GPP NW and the VDR 70 outside the 3GPP NW.

[0123] Regarding S213-1 to S213-3, in more detail, in S213-1 and S213-2, the authentication function 60 inputs DID0 (certificate issuer identifier) ​​and DID1 (user identifier) ​​included in the received VP / VC, and uses an arbitrary DID Method to obtain (resolve) the DID Document (public key) corresponding to DID0 and the DID Document (public key) corresponding to DID1 from the VDR 70. In S213-3, the authentication function 60 verifies that the VP Holder signature and the VC Issuer signature are signatures made with private keys linked to those public keys (validity of the signature, no tampering with the message).

[0124] In S213-4, the authentication function 60 requests information regarding the certificate format and status (such as revocation status) from the VDR 70. In S213-5, the VDR 70 responds with the certificate format and status information. In S213-6, the authentication function 60 verifies the validity of the certificate.

[0125] Regarding S213-4 to S213-6, in more detail, the authentication function 60 acquires the VC schema, definition information, etc. from the VDR 70 and verifies that the VC syntax, etc. is correct. The authentication function 60 also acquires VC validity information / revocation information from the VDR 70 and verifies that the received VC is valid.

[0126] In S213-7, the authentication function 60 verifies the eligibility of the certificate. More specifically, the authentication function 60 verifies that the conditions of the VC available for the NW connection (e.g., that it is a My Number VC, and that it contains necessary information (e.g., name, address)) are met. Note that these conditions have already been acquired in order to make the request in S206 of FIG. 8.

[0127] If the authentication function 60 determines that all of the above verification results are OK, it determines that the authentication has been successful.

[0128] (Second embodiment: processing sequence example 2) Next, processing sequence example 2 in the second embodiment will be described with reference to Fig. 10. Processing sequence example 2 is an example in which an existing NF and an existing IF are extended. In processing sequence example 2, a function for performing authentication based on attributes / credentials is included in the AUSF 80. This function performs the authentication process of S207, which will be described later.

[0129] The UDM 40 holds an authentication method selection function (used in S205) based on attributes / credentials when selecting an authentication method, and the following information used in the attribute / credentials method.

[0130] NW identifier, and public and private keys associated with the identifier. Certificate information that can be used for NW connection (certificate type, data format, information that should be included in the certificate, etc.). The sequence will be described with reference to FIG. 10 .

[0131] In S201, the UE 20 includes information (e.g., an arbitrary character string) indicating a request to perform authentication using attributes / credentials in a Registration Request message, and transmits the Registration Request message including the information to the (R)AN 10. In S202, the (R)AN 10 transmits the Registration Request message including the information to the AMF / SEAF (30).

[0132] In S203, the AMF / SEAF (30) includes information indicating a request to perform authentication using attributes / credentials in the Nausf_UEAuthentication_Authenticate Request message, and sends the Nausf_UEAuthentication_Authenticate Request message including the information to the AUSF 80 as an authentication request.

[0133] In S204, the AUSF 80 sends a Nudm_UEAuthentication_Get Request message including the above information to the UDM / ARPF / SIDF (40) as an authentication request.

[0134] In S205, the UDM / ARPF / SIDF (40) performs Authentication Method Selection. Specifically, if the received message does not contain SUPI or SUCI but contains information requesting attribute / credential authentication, the UDM / ARPF / SIDF (40) selects authentication based on attribute / credentials as the authentication method. Furthermore, if the received message contains both SUPI or SUCI and information requesting attribute / credential authentication, the UDM / ARPF / SIDF (40) selects an authentication method based on a pre-registered authentication method selection policy or a user request.

[0135] In S206, the UDM / ARPF / SIDF (40) includes a string (e.g., Credential Auth) indicating that the attribute / credential authentication method has been selected in the Nudm_UEAuthentication_Get Response message, and sends the Nudm_UEAuthentication_Get Response message including the string to the AUSF 80.

[0136] Upon receiving the Nudm_UEAuthentication_Get Response message containing the character string, the AUSF 80 sends a message to the AMF / SEAF (30) requesting attributes / credentials that can be used for network connection in S207.

[0137] The information (conditions) about the attributes / credentials available for the NW connection, which is specified in the above request, may be held in the storage of the AUSF 80, or may be acquired from the storage of the UDM 40. In the latter case, this information (conditions) may be notified by being included in the message of S206, or may be acquired from the AUSF 80 to the UDM 40 upon receiving the message of S206, for example.

[0138] In S208, the AMF / SEAF (30) sends the message to the (R)AN 10, and in S209, the (R)AN 10 sends the message to the UE 20.

[0139] At S210, the UE 20 displays the information contained in the message received from the (R)AN 10 on a display, and the user of the UE 20 confirms the conditions of the requested attributes / credentials.

[0140] If the user agrees to the information provision, in S211, the UE 20 transmits a response message including the requested attributes / credentials (e.g., VC) and user identifier (e.g., DID). Note that the UE 20 may automatically check the conditions. The response message includes a signature (e.g., VP) generated by the UE 20 using a private key corresponding to the user's identifier.

[0141] In S212, the (R)AN 10 that has received the response message transfers the message to the AMF 30. In S213, the AMF 30 transfers the response message to the authentication function 60.

[0142] At S214, the authentication function 60 verifies the received attribute / credential by performing an authentication process using the attribute / credential.

[0143] In S215, the authentication function 60 includes a string (e.g., Credential Auth Success) indicating that authentication using attributes / credentials was successful in the Nausf_UEAuthentication_Authenticate Response message, and sends the Nausf_UEAuthentication_Authenticate Response message including the string to the AMF / SEAF (30).

[0144] In the subsequent S216, connection processing is executed. Specifically, the NW Registration processing is completed by executing the processing from step 10 onwards of 3GPP TS 23.502 4.2.2.2 Registration Procedure. In the NW Registration processing, the SUPI / SUCI-based API or the SUPI / SUCI-based subscriber information registration processing is extended so that it can be executed using the user identifier (DID, etc.) included in the attribute / credentials.

[0145] In the sequence of FIG. 10, a new C-Plane message is used in S207 to S209 and S211 to S213.

[0146] Attributes / credentials are also added to the Mobility Registration Update / Periodic Registration Update messages in the same way as in the above example.

[0147] Details of S214 will be described with reference to Fig. 11. Here, as in the previous examples, verification of attributes / credentials in the W3C DID / VC / VP format will be assumed as an example of authentication / verification processing logic.

[0148] When the authentication process using the attribute / credential certificate starts, in S214-1, the AUSF 80 requests the VDR 70 for a public key corresponding to the identifier of the certificate issuer (Issuer) and a public key corresponding to the identifier of the user. In S214-2, the VDR 70 responds with these public keys to the AUSF 80.

[0149] In S214-3, the AUSF 80 verifies the authenticity of the certificate issuer's signature and the user's signature and that the message has not been tampered with.

[0150] Note that communication between the AUSF 80 and the VDR 70 may be via a node (e.g., NEF, SCEF) that mediates communication between the AUSF 80 within the 3GPP network and the VDR 70 outside the 3GPP network.

[0151] Regarding S214-1 to S214-3, in more detail, in S214-1 and S214-2, AUSF 80 receives DID0 (certificate issuer identifier) ​​and DID1 (user identifier) ​​included in the received VP / VC as input, and uses an arbitrary DID Method to obtain (resolve) the DID Document (public key) corresponding to DID0 and the DID Document (public key) corresponding to DID1 from VDR 70. In S214-3, AUSF 80 verifies that the VP Holder signature and the VC Issuer signature are signatures made with private keys linked to those public keys (validity of the signatures, no tampering with the messages).

[0152] In S214-4, the AUSF 80 requests information regarding the certificate format and status (such as revocation status) from the VDR 70. In S214-5, the VDR 70 responds with the certificate format and status information. In S213-6, the AUSF 80 verifies the validity of the certificate.

[0153] Regarding S214-4 to S214-6, in more detail, the AUSF 80 acquires the VC schema, definition information, etc. from the VDR 70 and verifies that the VC syntax, etc. is correct. The AUSF 80 also acquires the VC validity information / revocation information from the VDR 70 and verifies that the received VC is valid.

[0154] In S214-7, the AUSF 80 verifies the eligibility of the certificate. More specifically, the AUSF 80 verifies that the conditions of a VC available for network connection (e.g., that it is a My Number VC, and that required information (e.g., name, address) is included) are met.

[0155] If the AUSF 80 determines that all of the above verification results are OK, it determines that the authentication is successful. Note that in the process of Figure 11, all communications between the AUSF 80 and the VDR 70 or the UDM 40 are performed using new C-Plane messages.

[0156] (Effects of the Second Embodiment) The technology according to the second embodiment enables the terminal 20 to connect to the NW based on authentication based on attributes / credentials.

[0157] In the second embodiment, the authentication function 60 / AUSF 80 can request the UE 20 for attributes / credentials to be used for NW connection, and the UE 20 can transmit the agreed attributes / credentials to the NW. Therefore, the UE 20 can avoid transmitting unnecessary attributes / credentials to the NW, and the NW can obtain the necessary attributes / credentials to perform authentication.

[0158] (Outline of Third Embodiment) Next, a third embodiment will be described. In the third embodiment, logic and an interface for "D-Plane communication encryption method, key generation, and key sharing" between the UE 20 and the 3GPP network are added to the basic method described in the first embodiment, and a method for authenticating the 3GPP network by the UE 20 and an interface for that purpose are added. Note that only one of the addition of the logic and an interface for "D-Plane communication encryption method, key generation, and key sharing" between the UE 20 and the 3GPP network and the addition of the method for authenticating the 3GPP network by the UE 20 may be added.

[0159] Below, an example in which the newly defined network node authentication function 60 is used as the "authentication function" will be described as processing sequence example 1, and an example in which AUSF 80 is used as the "authentication function" will be described as processing sequence example 2.

[0160] In the third embodiment, processing sequence example 1 includes processing sequence example 1-1 and processing sequence example 1-2, and processing sequence example 2 includes processing sequence example 2-1 and processing sequence example 2-2.

[0161] In processing sequence example 1-1 and processing sequence example 2-1, communications are encrypted using the public key of the network / user. In processing sequence example 1-2 and processing sequence example 2-2, a root key K is generated and communications are encrypted using a common key derived from the root key K.

[0162] An example of each processing sequence will be described below.

[0163] (Third embodiment: processing sequence example 1-1) Processing sequence example 1-1 in the third embodiment will be described with reference to Fig. 12. The encryption method used here is outlined below.

[0164] -Communications from UE to NW are encrypted with the public key of the NW and decrypted with the private key of the NW.

[0165] Communications in the NW → UE direction are encrypted with the user's public key and decrypted with the user's private key.

[0166] NW authentication by the UE is realized by signing a message in the NW → UE direction with the private key of the NW and verifying it on the UE side with the public key of the NW.

[0167] In addition, UE authentication by the network is achieved by signing a message in the UE → network direction with the user's private key (a private key corresponding to the user's identifier) ​​and verifying it on the network side with the user's public key (a public key corresponding to the user's identifier).

[0168] The processing assumptions for the sequence are as follows:

[0169] A user has a public key / private key pair corresponding to his / her own identifier, and stores his / her own identifier and public key in association with each other in a VDR 70 located in a place accessible by the 3GPP NW.

[0170] A user has attributes / credentials (which can be used for network connection) issued by any entity (such as a company or another user).

[0171] The certificate issuer holds a public key / private key pair corresponding to its own identifier, and stores its own identifier and public key in association with each other in a VDR 70 located in a place accessible to the 3GPP network.

[0172] A certificate issuer stores the format (scheme or definition) of the certificate it issues and information for verifying the validity of the certificate in a VDR 70 that exists in a location accessible to the 3GPP network.

[0173] The 3GPP network holds a public key / private key pair corresponding to its own identifier.

[0174] The method of distributing the public key of the NW to the UE 20 is not limited to a specific method, but for example, the following method (1) or (2) can be used.

[0175] Method (1): A network identifier and a public key are associated and stored in a VDR 70 located in a location accessible to the UE 20, and the public key is acquired by accessing the VDR 70 from the UE 20 at any time. This method assumes that the UE 20 has stored in advance the network identifier information that serves as a key for accessing the VDR.

[0176] Method (2): A public key is pre-installed in the UE 20 together with the network connection function / application of the UE 20 .

[0177] 12, it is assumed that the method (1) is used. In S301-1 of FIG. 12, the UE 20 requests a public key linked to an identifier of the 3GPP network from the VDR 70. In S301-2, the VDR 70 responds to the UE 20 with the public key linked to the identifier of the 3GPP network.

[0178] That is, in steps S301-1 and S301-2, the UE 20 receives the identifier of the 3GPP network as an input and acquires the corresponding public key from the VDR 70.

[0179] Steps S301-1 to S301-2 are executed by preparing a communication means other than the 3GPP network to be connected, or steps S301-1 to S301-2 may be realized by extending the UE and the 3GPP network so that this communication can be performed via the 3GPP network even before connection to the 3GPP network to be connected.

[0180] In S302, the NW connection process using the attribute / credential certificate is started when the user operates the NW connection application or the UE 20 is powered on, or the like.

[0181] In S303, the UE 20 transmits a NW connection request message to the (R)AN 20 of the 3GPP network to request a network connection based on attributes / credentials, including a user identifier (e.g., DID) and user attributes / credentials (e.g., VC). The information included in the NW connection request message is signed (e.g., VP) by the UE 20 with a private key corresponding to the user identifier. Furthermore, the information is encrypted by the UE 20 with a public key of the 3GPP network. The UE 20 may include the public key corresponding to the user identifier in the NW connection request message and transmit the NW connection request message including the public key.

[0182] The "information included in the NW connection request message" includes attributes / credentials. Also, the "information included in the NW connection request message" may be the entire "NW connection request message." In other words, the information to be signed or encrypted may be only the attributes / credentials, or may be "the attributes / credentials and other information," or may be the entire "NW connection request message."

[0183] Hereinafter, in the process of signing or encrypting "information contained in a message," as above, the process may sign or encrypt only the information within the message, or it may sign or encrypt the entire message.

[0184] That is, in the third embodiment, for both messages in the UE → NW direction and messages in the NW → UE direction, the entire message may be signed, or information included in the message (attributes / credentials, etc.) may be signed.

[0185] In addition, for both messages in the UE → NW direction and messages in the NW → UE direction, encryption may involve encrypting the entire message, or encrypting information contained in the message (attributes / credentials, etc.).

[0186] The NW connection request message may include, in addition to information used for authentication, information similar to the information included in a Registration Request message, which is a message when a NW connection authentication request is made by SUPI / SUCI.

[0187] In S304, the (R)AN 20 forwards a NW connection request message to the AMF 30 requesting a NW connection using attributes / credentials.

[0188] In S305, when the AMF 30 receives a NW connection request message requesting a NW connection using attributes / credentials, the AMF 30 selects the authentication function 60 that performs authentication based on the attributes / credentials as the authentication request destination. In S306, the AMF 30 transmits an authentication request message including the attributes / credentials encrypted with the public key of the 3GPP NW to the authentication function 60.

[0189] In S307, the authentication function 60 decrypts the information included in the received message with its own (3GPP NW) private key. The private key of the 3GPP NW may be set in advance in each NF (each network node), or may be stored in a DB such as a UDM / UDR and acquired by each NF via an API or the like.

[0190] In addition, in the above S306, the AMF 30 may decrypt the message with the private key of the NW, and then present the attribute / credential certificate in plain text to the authentication function 60.

[0191] In S308, the authentication function 60 verifies the received attribute / credential by executing authentication processing using the attribute / credential. More specifically, the authentication function 60 obtains a public key corresponding to the user's identifier from the VDR 70 during primary authentication processing (certificate verification procedure) using the attribute / certificate, and uses the public key. Note that if the message in S303 contains the user's public key, the user's public key may be extracted from the message and used.

[0192] In S309, the authentication function 60 transmits an authentication response including the authentication result (success / failure) to the AMF 30. Subsequent communication from the 3GPP NW to the UE 20 is performed by signing a message with the private key of the NW and encrypting it with the public key of the user.

[0193] In S310, the NW registration process is completed by executing the processes from step 10 onward in 3GPP TS 23.502 4.2.2.2 Registration Procedure. The following process is executed as part of the process in S310.

[0194] In S310-1, the AMF 30 sends an authentication acceptance message. Information included in the authentication acceptance message is signed by the AMF 30 with the private key of the NW and encrypted with the public key of the user.

[0195] In S310-2, the (R)AN 10 transfers the authentication acceptance message to the UE 20. The information included in the authentication acceptance message is signed with the private key of the NW and encrypted with the public key of the user.

[0196] In S310-3, the UE 20 decrypts the information included in the received authentication permission message with the user's private key and performs signature verification with the NW's public key. Since signature verification can detect NW spoofing, signature verification corresponds to NW authentication.

[0197] After confirming that the sender of the authentication permission message is not a spoofed network, the UE 20 encrypts the information to be included in the authentication completion message with the public key of the 3GPP network, transmits the authentication completion message including the encrypted information, and continues communication processing with the network.

[0198] Details of S308 will be described with reference to Fig. 13. Here, as an example of authentication / verification processing logic, verification of attributes / credentials in the W3C DID / VC / VP format is assumed.

[0199] When the authentication process using the attribute / credential certificate starts, in S308-1, the authentication function 60 requests the VDR 70 for a public key corresponding to the identifier of the certificate issuer (Issuer) and a public key corresponding to the identifier of the user. In S308-2, the VDR 70 responds with the public keys to the authentication function 60.

[0200] In S308-3, the authentication function 60 verifies the authenticity of the certificate issuer's signature and the user's signature and that the message has not been tampered with.

[0201] Note that communication between the authentication function 60 in the 3GPP network and the VDR 70 outside the 3GPP network may be via a node (e.g., NEF, SCEF) that mediates communication between the authentication function 60 in the 3GPP network and the VDR 70 outside the 3GPP network.

[0202] Regarding S308-1 to S308-3, in more detail, in S308-1 and S308-2, the authentication function 60 receives as input DID0 (certificate issuer identifier) ​​and DID1 (user identifier) ​​included in the received VP / VC, and uses an arbitrary DID Method to obtain (resolve) the DID Document (public key) corresponding to DID0 and the DID Document (public key) corresponding to DID1 from the VDR 70. In S308-3, the authentication function 60 verifies that the VP Holder signature and the VC Issuer signature are signatures made with private keys linked to those public keys (validity of the signatures, no tampering with the messages).

[0203] In S308-4, the authentication function 60 requests information regarding the certificate format and status (such as revocation status) from the VDR 70. In S308-5, the VDR 70 responds with the certificate format and status information. In S308-6, the authentication function 60 verifies the validity of the certificate.

[0204] Regarding S308-4 to S308-6, in more detail, the authentication function 60 acquires the VC schema, definition information, etc. from the VDR 70 and verifies that the VC syntax, etc. is correct. The authentication function 60 also acquires VC validity information / revocation information from the VDR 70 and verifies that the received VC is valid.

[0205] In S308-7, the authentication function 60 requests the UDM / UDR (40) for certificate information that can be used for network connection, and in S308-8, the UDM / UDR (40) responds with the certificate information. In S308-9, the authentication function 60 performs eligibility verification of the certificate. More specifically, the authentication function 60 verifies that the conditions for a VC that can be used for network connection (e.g., that it is a My Number VC and that required information (e.g., name, address) is included) are met. If the authentication function 60 determines that all of the above verification results are OK, it determines that the authentication is successful.

[0206] If the message in S303 in FIG. 12 includes the user's public key, S308-1 and S308-2 may be omitted.

[0207] (Third embodiment: processing sequence example 1-2) Next, processing sequence example 1-2 in the third embodiment will be described with reference to Fig. 14. Processing sequence example 1-2 differs from processing sequence example 1-1 in the encryption method. In processing sequence example 1-2, the (R)AN 10 and AMF 30 have the same functions as processing sequence example 1-1, and are also responsible for transferring new messages specific to processing sequence example 1-2.

[0208] Since the processing of (R)AN 10 and AMF 30 in processing sequence example 1-2 is basically the same as the processing of (R)AN 10 and AMF 30 in processing sequence example 1-1, the illustration of (R)AN 10 and AMF 30 is omitted in Figure 14.

[0209] The encryption method in the processing sequence example 1-2 is outlined below.

[0210] As a process after successful authentication, the 3GPP network generates a root key K to be used to derive a common key and shares it with the UE 20 side.

[0211] Based on K, various keys for encryption are derived on the NW side and the UE 20 side in accordance with the existing 3GPP key hierarchy generation process.

[0212] The NW authentication by the UE 20 is realized by signing a message in the NW→UE direction with the private key of the NW and verifying it on the UE 20 side with the public key of the NW.

[0213] The premise of the processing sequence example 1-2 is the same as the premise of the processing sequence example 1-1.

[0214] 14, the UE 20 requests a public key linked to the identifier of the 3GPP network from the VDR 70. In S301-2, the VDR 70 responds with the public key linked to the identifier of the 3GPP network to the UE 20. That is, in S301-1 to S301-2, the UE 20 receives the identifier of the 3GPP network as input and acquires the corresponding public key from the VDR 70.

[0215] Steps S301-1 to S301-2 are executed by preparing a communication means other than the 3GPP network to be connected, or steps S301-1 to S301-2 may be realized by extending the UE 20 and the 3GPP network so that this communication can be performed via the 3GPP network even before connection to the 3GPP network to be connected.

[0216] As in the processing sequence example 1-1, steps S301-1 to S301-2 may be omitted by pre-installing the NW public key in the UE 20 together with the NW connection function / application, etc.

[0217] In S302, the NW connection process using the attribute / credential certificate is started when the user operates the NW connection application or the UE 20 is powered on, or the like.

[0218] In S303, the UE 20 transmits to the authentication device 60 a NW connection request message for requesting a network connection using attributes / credentials, including a user identifier (e.g., DID) and user attributes / credentials (e.g., VC). The information included in the NW connection request message is signed (e.g., VP) by the UE 20 with a private key corresponding to the user identifier. Furthermore, the information included in the NW connection request message is encrypted by the UE 20 with a public key of the 3GPP network. The UE 20 may include the public key corresponding to the user identifier in the NW connection request message and transmit the NW connection request message including the public key.

[0219] In S304, the authentication function 60 decrypts the received message with its own (3GPP NW) private key. The private key of the 3GPP NW may be set in advance in each NF, or may be stored in a DB such as the UDM / UDR (40) and acquired by each NF via an API or the like.

[0220] In S305, the authentication function 60 verifies the received attribute / credential by executing authentication processing using the attribute / credential. More specifically, the authentication function 60 obtains a public key corresponding to the user's identifier from the VDR 70 during primary authentication processing (certificate verification procedure) using the attribute / certificate, and uses the public key. Note that if the message in S303 contains the user's public key, the user's public key may be extracted from the message and used. The details of S305 are the same as those of the authentication processing described above.

[0221] After the authentication is successful, the authentication function 60 generates a root key K to be used to derive a common key for encryption in S306.

[0222] In S307, the authentication function 60 encrypts K with the user's public key and transmits a message including the encrypted K to the UE 20. The authentication function 60 adds a signature generated with the private key of the NW to the information included in the message. The "information included in the message" may be the "message" itself.

[0223] In S308, the UE 20 decrypts the information included in the received message with the user's private key, extracts K, and performs signature verification with the NW's public key. The signature verification is performed by the UE 20 to detect NW spoofing, and corresponds to NW authentication by the UE 20.

[0224] In S309, each of the UE 20 and the NW derives various keys for encryption in accordance with the existing 3GPP Key hierarchy generation process ( FIG. 15 ) based on K. Subsequent communication between the 3GPP NW and the UE 20 is encrypted with the derived keys.

[0225] (Third embodiment: processing sequence example 2-1) Next, processing sequence example 2-1 in the third embodiment will be described with reference to Fig. 16. In processing sequence example 2-1, a function for performing authentication based on attributes / credentials is included in the AUSF 80. This function performs the authentication process of S309, which will be described later.

[0226] The UDM 40 holds an authentication method selection function (used in S307) based on attributes / credentials when selecting an authentication method, and the following information used in the attribute / credentials method.

[0227] NW identifier, and public and private keys associated with the identifier. Certificate information that can be used for NW connection (certificate type, data format, information that should be included in the certificate, etc.). The sequence will be described with reference to FIG.

[0228] In S301-1, the UE 20 requests a public key linked to the identifier of the 3GPP network from the VDR 70. In S301-2, the VDR 70 returns the public key linked to the identifier of the 3GPP network to the UE 20.

[0229] That is, in steps S301-1 and S301-2, the UE 20 receives the identifier of the 3GPP network as an input and acquires the corresponding public key from the VDR 70.

[0230] S301-1 to S301-2 are executed, for example, by preparing a communication means other than the 3GPP network to be connected. Alternatively, S301-1 to S301-2 may be realized by extending the UE and the 3GPP network so that this communication can be performed via the 3GPP network even before connection to the 3GPP network to be connected. Furthermore, S301-1 to S301-2 may be omitted by pre-installing the public key of the network in the UE 20 along with the network connection function / application, etc.

[0231] In S302, UE 20 includes the attributes / credentials in a Registration Request message and transmits the Registration Request message including the attributes / credentials to (R)AN 10. The information (attributes / credentials, etc.) included in the Registration Request message is signed (e.g., VP) by UE 20 with a private key corresponding to the user's identifier. Furthermore, the information is encrypted by UE 20 with the public key of the 3GPP network.

[0232] At S303, the (R)AN 10 forwards the Registration Request message, including the attributes / credentials encrypted with the public key of the 3GPP NW, to the AMF / SEAF (30).

[0233] In S304, the AMF / SEAF (30) includes the attributes / credentials encrypted with the public key of the 3GPP NW in the Nausf_UEAuthentication_Authenticate Request message, and sends the Nausf_UEAuthentication_Authenticate Request message including the attributes / credentials to the AUSF 80 as an authentication request.

[0234] In S305, the AUSF 80 includes the attributes / credentials encrypted with the public key of the 3GPP network in the Nudm_UEAuthentication_Get Request message, and sends the Nudm_UEAuthentication_Get Request message including the attributes / credentials to the UDM / ARPF / SIDF (40) as an authentication request.

[0235] In S306, the UDM / ARPF / SIDF (40) decrypts the information (attributes / credentials, etc.) included in the received message using its own (3GPP network) private key. It is assumed that the 3GPP network private key is stored in the UDM / UDR (40). Note that the 3GPP network private key may be handled only within the UDM, or may be shared with other nodes such as the AUSF 80 as necessary, or may be stored in the storage of each node.

[0236] In S307, the UDM / ARPF / SIDF (40) performs Authentication Method Selection.

[0237] Specifically, if a received message does not contain SUPI or SUCI but does contain attributes / credentials, authentication using attributes / credentials is selected as the authentication method. If both SUPI or SUCI and attributes / credentials are contained, an authentication method is selected based on a pre-registered authentication method selection policy or a user request.

[0238] In S308, the UDM / ARPF / SIDF (40) includes a character string (e.g., Credential Auth) indicating that the attribute / credential authentication method has been selected in the Nudm_UEAuthentication_Get Response message, and transmits the Nudm_UEAuthentication_Get Response message including the character string to the AUSF 80. The message includes the attribute / credential decrypted by the UDM 40. The message may also include the encrypted attribute / credential and the NW private key stored in the UDM 40. In this case, the AUSF 80 decrypts the attribute / credential.

[0239] In S309, the AUSF 80 executes authentication processing using attributes / credentials.

[0240] In S310, the AUSF 80 includes a string indicating that attribute / credential authentication was successful (e.g., Credential Auth Success) in the Nausf_UEAuthentication_Authenticate Response message, and sends the Nausf_UEAuthentication_Authenticate Response message including the string to the AMF / SEAF (30).

[0241] Thereafter, in S311, the processes from step 10 onward of 3GPP TS 23.502 4.2.2.2 Registration Procedure are executed, and the NW Registration process is completed. In the NW Registration process, the SUPI / SUCI-based API or the SUPI / SUCI-based subscriber information registration process is extended so that it can be executed using the user identifier (DID, etc.) included in the attribute / credentials.

[0242] As part of the processing in S311, the following processing is executed.

[0243] In step S311-1, the AMF / SEAF (30) sends a Registration Accept message, which includes information that is signed by the AMF / SEAF (30) with the private key of the network and encrypted with the public key of the user.

[0244] In S311-2, the (R)AN 10 transfers the Registration Accept message to the UE 20. The information included in the Registration Accept message is signed with the private key of the NW and encrypted with the public key of the user.

[0245] In S311-3, the UE 20 decrypts the information included in the received Registration Accept message with the user's private key and performs signature verification with the NW's public key.

[0246] After confirming that the sender of the Registration Accept message is not a spoofed network, the UE 20 encrypts the information included in the Registration Complete message with the public key of the 3GPP network, transmits the Registration Complete message including the encrypted information, and continues communication processing with the network.

[0247] As in the above example, attributes / credentials are also added to the Mobility Registration Update / Periodic Registration Update messages.

[0248] Details of S309 will be described with reference to Fig. 17. Here, as in the previous examples, as an example of the verification processing logic, verification of attributes / credentials in W3C DID / VC / VP format is assumed. In the following sequence, all communications between the AUSF and the VDR or UDM are performed using new C-Plane messages.

[0249] When the authentication process using the attribute / credential certificate starts, in S309-1, the AUSF 80 requests the VDR 70 for a public key corresponding to the identifier of the certificate issuer (Issuer) and a public key corresponding to the identifier of the user. In S309-2, the VDR 70 responds with the public keys to the AUSF 80.

[0250] In S309-3, the AUSF 80 verifies the authenticity of the certificate issuer's signature and the user's signature and that the message has not been tampered with.

[0251] Note that communication between the AUSF 80 within the 3GPP network and the VDR 70 outside the 3GPP network may be via a node (e.g., NEF, SCEF) that mediates the communication.

[0252] Regarding S309-1 to S309-3, in more detail, in S309-1 and S309-2, AUSF 80 inputs DID0 (certificate issuer identifier) ​​and DID1 (user identifier) ​​included in the received VP / VC, and uses an arbitrary DID Method to obtain (resolve) the DID Document (public key) corresponding to DID0 and the DID Document (public key) corresponding to DID1 from VDR 70. In S309-3, AUSF 80 verifies that the VP Holder signature and VC Issuer signature are signatures made with private keys linked to those public keys (validity of the signature, no tampering of the message).

[0253] If the message in S302 in FIG. 16 includes the user's public key, steps S309-1 to S309-3 may be omitted.

[0254] In S309-4, the AUSF 80 requests information regarding the certificate format and status (such as revocation status) from the VDR 70. In S309-5, the VDR 70 responds with the certificate format and status information. In S309-6, the AUSF 80 verifies the validity of the certificate.

[0255] In more detail, in S309-4 to S309-6, the AUSF 80 acquires the VC schema, definition information, etc. from the VDR 70 and verifies that the VC syntax, etc. is correct. The AUSF 80 also acquires the VC validity information / revocation information from the VDR 70 and verifies that the received VC is valid.

[0256] In S309-7, the AUSF 80 requests the UDM / UDR (40) for certificate information that can be used for network connection, and in S309-8, the UDM / UDR (40) responds with the certificate information. In S309-9, the AUSF 80 performs eligibility verification of the certificate. More specifically, the AUSF 80 verifies that the conditions for a VC that can be used for network connection (e.g., that it is a My Number VC, and that required information (e.g., name, address) is included) are met.

[0257] If the AUSF 80 determines that all of the above verification results are OK, it determines that the authentication has been successful. Note that S309-7 to S309-8 may be omitted by including the certificate information in the message of S308 in FIG.

[0258] (Third embodiment: processing sequence example 2-2) Next, processing sequence example 2-2 in the third embodiment will be described with reference to Fig. 18. In processing sequence example 2-2, the AUSF 80 also includes a function for performing authentication based on attributes / credentials. This function performs the authentication process of S309, which will be described later.

[0259] The UDM 40 holds an authentication method selection function (used in S307) based on attributes / credentials when selecting an authentication method, and the following information used in the attribute / credentials method.

[0260] NW identifier, and public and private keys associated with the identifier. Certificate information that can be used for NW connection (certificate type, data format, information that should be included in the certificate, etc.). The sequence will be described with reference to FIG.

[0261] In S301-1, the UE 20 requests a public key linked to the identifier of the 3GPP network from the VDR 70. In S301-2, the VDR 70 returns the public key linked to the identifier of the 3GPP network to the UE 20.

[0262] That is, in steps S301-1 and S301-2, the UE 20 receives the identifier of the 3GPP network as an input and acquires the corresponding public key from the VDR 70.

[0263] Steps S301-1 to S301-2 are executed by preparing a communication means other than the 3GPP network to be connected, or steps S301-1 to S301-2 may be realized by extending the UE and the 3GPP network so that this communication can be performed via the 3GPP network even before connection to the 3GPP network to be connected.

[0264] Furthermore, by pre-installing the NW public key in the UE 20 together with the NW connection function / application, etc., steps S301-1 to S301-2 may be omitted.

[0265] In S302, UE 20 includes the attributes / credentials in a Registration Request message and transmits the Registration Request message including the attributes / credentials to (R)AN 10. The information (attributes / credentials, etc.) included in the Registration Request message is signed (e.g., VP) by UE 20 with a private key corresponding to the user's identifier. Furthermore, the information is encrypted by UE 20 with the public key of the 3GPP NW.

[0266] At S303, the (R)AN 10 forwards the Registration Request message, including the attributes / credentials encrypted with the public key of the 3GPP NW, to the AMF / SEAF (30).

[0267] In S304, the AMF / SEAF (30) includes the attributes / credentials encrypted with the public key of the 3GPP NW in the Nausf_UEAuthentication_Authenticate Request message, and sends the Nausf_UEAuthentication_Authenticate Request message including the attributes / credentials to the AUSF 80 as an authentication request.

[0268] In S305, the AUSF 80 includes the attributes / credentials encrypted with the public key of the 3GPP network in the Nudm_UEAuthentication_Get Request message, and sends the Nudm_UEAuthentication_Get Request message including the attributes / credentials to the UDM / ARPF / SIDF (40) as an authentication request.

[0269] In S306, the UDM / ARPF / SIDF (40) decrypts the information (attributes / credentials, etc.) included in the received message using its own (3GPP network) private key. It is assumed that the 3GPP network private key is stored in the UDM / UDR (40). Note that the 3GPP network private key may be handled only within the UDM, or may be shared with other nodes such as the AUSF 80 as necessary, or may be stored in the storage of each node.

[0270] In S307, the UDM / ARPF / SIDF (40) performs Authentication Method Selection.

[0271] Specifically, if the received message does not contain SUPI or SUCI but does contain attributes / credentials, attribute / credential authentication is selected as the authentication method. If both SUPI or SUCI and attributes / credentials are contained, the authentication method is selected based on a pre-registered authentication method selection policy or a user request.

[0272] In S308, the UDM / ARPF / SIDF (40) includes a character string (e.g., Credential Auth) indicating that the attribute / credential authentication method has been selected in the Nudm_UEAuthentication_Get Response message, and transmits the Nudm_UEAuthentication_Get Response message including the character string to the AUSF 80. The message includes the attribute / credential decrypted by the UDM 40. The message may also include the encrypted attribute / credential and the NW private key stored in the UDM 40. In this case, the AUSF 80 decrypts the attribute / credential.

[0273] In S309, the AUSF 80 executes authentication processing using the attributes / credentials. The details of the authentication processing are the same as those described above.

[0274] In S310, the AUSF 80 generates a root key K, which is a common key shared by the UE 20 and the NW.

[0275] In S311, the AUSF 80 includes a string indicating that attribute / credential authentication was successful (e.g., Crendential Auth Success) and a root key K in the Nausf_UEAuthentication_Authenticate Response message, and sends the Nausf_UEAuthentication_Authenticate Response message including the string and the root key K to the AMF / SEAF (30).

[0276] Thereafter, in S312, the processes from step 10 onward of 3GPP TS 23.502 4.2.2.2 Registration Procedure are executed, and the NW Registration process is completed. In the NW Registration process, the SUPI / SUCI-based API or the SUPI / SUCI-based subscriber information registration process is extended so that it can be executed using the user identifier (DID, etc.) included in the attribute / credentials.

[0277] As part of the processing at S312, the following processing is executed.

[0278] In S312-1, the AMF / SEAF (30) includes the root key K in a Registration Accept message and transmits the Registration Accept message including the root key K. The information included in the Registration Accept message is signed by the AMF / SEAF (30) with the private key of the NW and encrypted with the public key of the user. Note that the message in which the root key K is included and notified to the UE 20 is not limited to the Registration Accept message, and any message can be used.

[0279] In S312-2, the (R)AN 10 transfers the Registration Accept message to the UE 20. The information included in the Registration Accept message is signed with the private key of the NW and encrypted with the public key of the user.

[0280] In S313-3, the UE 20 decrypts the information included in the received Registration Accept message with the user's private key and verifies the signature with the NW's public key, thereby extracting the root key K.

[0281] In S312-4, based on K and in accordance with the existing 3GPP NAS Security Procedure, various keys for encryption are derived on the NW side and UE 20, respectively, and subsequent communications are encrypted using these keys.

[0282] In S312-4, the UE 20 encrypts the information included in the Registration Complete message with the key derived from K, transmits the Registration Complete message including the encrypted information, and continues the communication process with the NW.

[0283] Instead of the AUSF 80 generating the root key K, the AMF / SEAF (30) may generate the root key K. In this case, the AMF / SEAF (30) may include the root key K with a signature generated with the private key of the NW in the message of S312-1 and transmit it. The "root key K with a signature generated with the private key of the NW" is transmitted to the UE 20, and the UE 20 performs signature verification.

[0284] As in the above example, attributes / credentials are also added to the Mobility Registration Update / Periodic Registration Update messages.

[0285] (Effects of the Third Embodiment) The technology according to the third embodiment enables the terminal 20 to connect to the NW based on authentication based on attributes / credentials.

[0286] In addition, in the third embodiment, the user identifier and the attribute / credential certificate are encrypted before transmission, thereby improving security. In a message transmitted from the NW side to the UE 20, fraud such as spoofing on the NW side can be detected, thereby improving security.

[0287] (Other Examples Common to the First to Third Embodiments) Hereinafter, other examples common to the first to third embodiments will be described. Note that matters related to specific embodiments will be noted accordingly.

[0288] The NW connection function 21 may include, for example, a digital identity wallet that manages user identifiers, attributes / credentials, and public keys / private keys associated with the identifiers.

[0289] The storage location for the user identifier, attribute / qualification certificate, and public key / private key linked to the identifier in the network connection function 21 may be the normal storage area within the UE 20, or may be within an HSM (hardware security module) within the UE 20, or may be storage outside the UE 20 that is accessible from the UE 20.

[0290] The issuer of the attribute / credential certificate may be a third party or the 3GPP NW operator itself.

[0291] When both a SIM and an attribute / credentials are available in the UE 20, or when multiple attributes / credentials are available for network connection, it may be possible to select which information to include in a message to present to the NW side based on a user operation / setting. In the second embodiment, a request message for attributes / credentials from the NW side to the UE 20 may be transmitted including conditions in the form of multiple attributes / credentials, and it may be possible to select which information to include in a message to present to the NW side based on a user operation / setting.

[0292] In existing 3GPP networks, SUPI or SUCI is used to identify a UE in order to provide a unified service to the UE, and in many cases, it is mandatory that SUPI or SUCI be included in messages exchanged between NFs or in input of APIs of services provided by the NFs. In contrast, in this embodiment, even in a situation where UE 20 cannot provide SUPI or SUCI to the 3GPP network, it is possible to identify / manage UE 20 based on a user identifier (DID, etc.) and an identifier that can uniquely identify attributes / credentials (e.g., the ID of the VC itself), etc.

[0293] In addition, all mechanisms that manage information using SUPI or SUCI as a key in the databases of each node, such as AMF 30 and UDM / UDR (40), can be adapted to management using a user identifier (DID, etc.) or an identifier that can uniquely identify an attribute / qualification certificate as a key.

[0294] (Device Configuration) Next, a description will be given of an example of the functional configuration of the "authentication function 60, AMF 30, UDM 40, VDR 70, AUSF 80, etc." and the terminal 20 (UE 20) that perform the processes and operations described above. Hereinafter, the network nodes such as the authentication function 60, AMF 30, UDM 40, VDR 70, AUSF 80, etc. will be collectively referred to as the "network node 100."

[0295] <Network Node 100> FIG. 19 is a diagram showing an example of the functional configuration of the network node 100. As shown in FIG.

[0296] As shown in Fig. 19, the network node 100 includes a transmitting unit 110, a receiving unit 120, a setting unit 130, and a control unit 140. The functional configuration shown in Fig. 19 is merely an example. The names of the functional divisions and functional units may be any names as long as they can perform the operations according to the embodiment of the present invention.

[0297] The transmitter 110 has a function of generating a signal to be transmitted to the terminal 20 or another network node and transmitting the signal via a wired or wireless connection. The receiver 120 has a function of receiving various signals transmitted from the terminal 20 or another network node 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.

[0298] The setting unit 130 stores pre-set 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. The control unit 140 controls the network node 100. 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. The transmitting unit 110 and the receiving unit 120 may be called a transmitter and a receiver, respectively.

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

[0300] 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 NR-PSS, NR-SSS, NR-PBCH, DL / UL control signals, reference signals, and the like transmitted from the network node 30. A communication unit including the transmitter 210 and the receiver 220 may be configured.

[0301] The setting unit 230 stores various setting information received from the network node by the receiving unit 220 in a storage device, and reads it out from the storage device as needed. The setting unit 230 also stores setting information that is set in advance.

[0302] The control unit 240 controls the terminal 20. The functional unit in the control unit 240 related to signal transmission may be included in the transmitting unit 210, and the functional unit in the control unit 240 related to signal reception may be included in the receiving unit 220. The transmitting unit 210 and the receiving unit 220 may be called a transmitter and a receiver, respectively.

[0303] (Hardware Configuration) The block diagrams (FIGS. 19 and 20) 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.

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

[0305] For example, the network node 100 and the terminal 20 according to an embodiment of the present disclosure may function as a computer that performs processing of the communication method of the present disclosure. Fig. 21 is a diagram illustrating an example of the hardware configuration of the network node 100 and the terminal 20 according to an embodiment of the present disclosure. The above-described EES 30 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.

[0306] In the following description, the term "apparatus" can be read as a circuit, a device, a unit, etc. The hardware configuration of the network node 100 and the terminal 20 may be configured to include one or more of the apparatuses shown in the figure, or may be configured to exclude some of the apparatuses.

[0307] Each function in the network node 100 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 via 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.

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

[0309] 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 network node 100 shown in FIG. 19 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. 20 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.

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

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

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

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

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

[0315] Furthermore, the network node 100 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.

[0316] 22 shows an example configuration of a vehicle 2001. As shown in FIG. 22 , 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. For example, the network node 100 or the terminal 20 may be included in the communication module 2013.

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

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

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

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

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

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

[0323] 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 terminal, a network node, or the like.

[0324] The communication module 2013 may transmit, via wireless communication, to an external device at least one of signals from the 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. 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.

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

[0326] Furthermore, when the communication module 2013 includes the network node 100 (or the terminal 20), the communication module 2013 can perform the operations of the network node 100 (or the terminal 20) described above.

[0327] This specification discloses at least the configurations described in Supplementary Notes 1 to 3 below.

[0328] <Supplementary Note 1> (Supplementary Item 1) A terminal comprising: a transmitter that transmits a connection request message including a certificate storing personal data to a network; and a controller that, after authentication processing using the certificate has been performed in the network, executes a registration procedure for the network after the authentication processing. (Supplementary Item 2) The terminal according to Supplementary Item 1, wherein the connection request message is a registration request message requesting registration with the network. (Supplementary Item 3) A network node comprising: a receiver that receives an authentication request message including a certificate storing personal data from a specific network node that has received from the terminal the connection request message including the certificate; a controller that performs authentication processing using the certificate; and a transmitter that transmits an authentication result to the specific network node. (Supplementary Item 4) The network node according to Supplementary Item 3, wherein the transmitter requests a management node that manages user data to register the personal data included in the certificate. (Supplementary Item 5) The network node according to Supplementary Item 3, wherein the network node is an AUSF. (Supplementary Item 6) A communication method executed by a network node, which receives an authentication request message including a certificate storing personal data from a specific network node that has received a connection request message including the certificate from a terminal, performs authentication processing using the certificate, and transmits the authentication result to the specific network node.

[0329] Supplementary clauses 1 to 6 all provide a technique that enables a terminal to connect to a network based on attribute / credential certificate-based authentication. Supplementary clauses 2 and 5 enable a technique that enables a terminal to connect to a network based on attribute / credential certificate-based authentication by extending messages or nodes defined in existing 3GPP standards. Supplementary clause 4 enables billing information and the like to be registered in a management node in attribute / credential certificate-based authentication.

[0330] <Supplementary Note 2> (Supplementary Item 1) A terminal comprising: a transmitter that transmits a connection request message to a network; a receiver that receives from the network a message requesting a certificate storing personal data; and a controller that executes a registration procedure to the network after the certificate is transmitted by the transmitter and authentication processing using the certificate is performed in the network. (Supplementary Item 2) The terminal according to Supplementary Item 1, wherein the connection request message is a registration request message that requests registration to the network. (Supplementary Item 3) A network node comprising: a receiver that receives an authentication request message from a specific network node that received the connection request message from the terminal; a transmitter that transmits to the terminal a message requesting a certificate storing personal data; and a controller that executes authentication processing using the certificate transmitted from the terminal based on the message. (Supplementary Item 4) The network node according to Supplementary Item 3, wherein the message includes conditions for the certificate requested of the terminal. (Supplementary Item 5) The network node according to Supplementary Item 3, wherein the network node is an AUSF. (Supplementary Item 6) A communication method executed by a network node, which receives an authentication request message from a specific network node that has received a connection request message from a terminal, transmits a message to the terminal requesting a certificate storing personal data, and performs authentication processing using the certificate transmitted from the terminal based on the message.

[0331] Any of Supplementary Items 1 to 6 provides a technique that enables a terminal to connect to a network based on authentication based on attributes / credentials. Supplementary Items 2 and 5 realize a technique that enables a terminal to connect to a network based on authentication based on attributes / credentials by extending messages or nodes defined in existing 3GPP standards. Supplementary Item 4 enables a network to request attributes / credentials of desired conditions from the terminal.

[0332] <Supplementary Item 3> (Supplementary Item 1) A terminal comprising: a transmitter that transmits a connection request message to the network, the connection request message including a certificate storing personal data; and a controller that executes a registration procedure to the network after authentication processing using the certificate has been performed in the network, wherein the transmitter encrypts the certificate or the connection request message with a public key of the network and transmits the encrypted message. (Supplementary Item 2) The terminal according to Supplementary Item 1, further comprising: a receiver that receives from the network a message including information signed with a private key of the network after authentication processing using the certificate has been performed in the network, the controller verifies the signature using the public key. (Supplementary Item 3) The terminal according to Supplementary Item 2, wherein the receiver receives from the network a message encrypted with the public key of the terminal. (Supplementary Item 4) The terminal according to Supplementary Item 1, further comprising: a receiver that receives a root key from the network, the controller using the root key to generate a key common to the network and the terminal. (Supplementary Item 5) A network node comprising: a receiving unit that receives, from a specific network node that has received from a terminal a connection request message including a certificate storing personal data, an authentication request message including the certificate, a control unit that performs authentication processing using the decrypted certificate, and a transmitting unit that transmits an authentication result to the specific network node, wherein the connection request message received by the specific network node or the certificate included in the connection request message is encrypted with a public key of the network. (Supplementary Item 6) A network node according to Supplementary Item 5, wherein the transmitting unit transmits to the terminal a root key used to generate a key common between the network and the terminal.

[0333] All of Supplementary Items 1 to 6 provide a technology that enables a terminal to connect to a network based on authentication based on attributes / credentials. Supplementary Item 2 makes it possible to detect impersonation on the network side. Supplementary Item 3 makes it possible to improve security. Supplementary Items 4 and 6 make it possible to realize encrypted communication using a common key.

[0334] (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 physically by a single component, or the operations of a single functional unit may be performed physically by multiple components. The order of processing procedures described in the embodiments may be reversed as long as there is no contradiction. For convenience of processing description, the network node 100 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 EES 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 random access memory (RAM), flash memory, read-only memory (ROM), EPROM, EEPROM, registers, hard disk (HDD), removable disk, CD-ROM, database, server, or any other suitable storage medium.

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

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

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

[0338] In this specification, a specific operation described as being performed by the base station 10 ((R)AN 10) may also be performed by its upper node in some cases. In a network consisting of one or more network nodes having a base station 10, it is clear that various operations performed for communication with a 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 (for example, an MME and an S-GW).

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0354] At least one of the base station and the mobile station (terminal 20) 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 an autonomous mobile object operating 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.

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

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

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

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

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

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

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

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

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

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

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

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

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

[0368] 10 Base station ((R)AN) 20 Terminal (UE) 21 NW connection function 30 AMF 40 UDM 41 NW information DB 42 Certificate information DB 43 Policy DB 60 Authentication function 70 VDR 71 User information DB 72 Issuer information DB 73 Definition information DB 74 Management information DB 80 AUSF 100 Network node 110 Transmission unit 120 Reception unit 130 Setting unit 140 Control unit 210 Transmission unit 220 Reception unit 230 Setting unit 240 Control unit 1001 Processor 1002 Storage device 1003 Auxiliary storage device 1004 Communication device 1005 Input device 1006 Output device

Claims

1. A terminal comprising: a transmitting unit that transmits a connection request message including a certificate storing personal data to a network; and a control unit that executes a registration procedure to the network after authentication processing using the certificate is performed in the network, wherein the transmitting unit encrypts and transmits the certificate or the connection request message with the public key of the network.

2. The terminal according to claim 1, further comprising a receiving unit that receives a message from the network including information signed with a private key of the network after the authentication process using the certificate has been performed in the network, and the control unit verifies the signature using the public key.

3. The terminal according to claim 2, wherein the receiving unit receives a message encrypted with the public key of the terminal from the network.

4. The terminal according to claim 1, further comprising a receiving unit that receives a root key from the network, wherein the control unit uses the root key to generate a common key between the network and the terminal.

5. A network node comprising: a receiving unit that receives an authentication request message including a certificate storing personal data from a specific network node that has received a connection request message from a terminal, the certificate including the connection request message; a control unit that performs authentication processing using the decrypted certificate; and a transmitting unit that transmits an authentication result to the specific network node, wherein the connection request message received by the specific network node or the certificate included in the connection request message is encrypted with a network public key.

6. The network node according to claim 5, wherein the transmission unit transmits to the terminal a root key used to generate a common key between the network and the terminal.

Images