Terminal, network node, and communication method

Abstract

This terminal comprises: a transmission unit that transmits, to a network, a connection request message including information related to a wallet end point; and a control unit that executes a registration procedure for the network after authentication processing is performed using a certificate storing personal data on the basis of the information related to the wallet end point in the network.

Description

Terminal, network node, and communication method

[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 information related to a wallet endpoint to a network; and a control unit that, after an authentication process is performed in the network using a certificate that stores personal data based on the information related to the wallet endpoint, executes a registration procedure to the network after the authentication process.

[0010] The disclosed technology provides a technology that enables a terminal to connect to a network based on attribute / credential-based authentication.

[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. 1 is a diagram for explaining an example of a system configuration common to the first and second embodiments. FIG. 2 is a diagram for explaining an overview of the first embodiment. FIG. 3 is a diagram for explaining processing sequence example 1 in the first embodiment. FIG. 4 is a diagram for explaining the processing of S106 in processing sequence example 1 in the first embodiment. FIG. 5 is a diagram for explaining the processing of S106 in processing sequence example 1 in the first embodiment. FIG. 6 is a diagram for explaining SUCI. FIG. 7 is a diagram for explaining processing sequence example 2 in the first embodiment. FIG. 8 is a diagram for explaining the authentication processing of S108 in processing sequence example 2 in the first embodiment. FIG. 9 is a diagram for explaining an overview of the second embodiment. FIG. 10 is a diagram for explaining processing sequence example 1 in the second embodiment. FIG. 11 is a diagram for explaining the authentication processing of S214 in processing sequence example 1 in the second embodiment. FIG. 12 is a diagram for explaining the authentication processing of S215 in processing sequence example 2 in the second embodiment. FIG. 13 is a diagram for explaining an example of the functional configuration of a network node 100 in an embodiment of the present invention. FIG. 14 is a diagram for explaining an example of the functional configuration of a terminal 20 in an embodiment of the present invention. FIG. 15 is a diagram for explaining an example of the hardware configuration of the terminal 20 and the network node 100 in an embodiment of the present invention. FIG. 16 is a diagram for explaining an example of the configuration of a vehicle 2001 in an embodiment of the present invention.

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

[0013] In the operation of the wireless communication system according to the embodiment of the present invention, existing 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] In particular, user attributes / credentials may be stored in a cloud wallet, but in such cases, there is no mechanism to realize network connectivity of the UE based on attribute / credential-based authentication.

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

[0031] A cloud wallet is a digital identity wallet provided on a cloud. In the first and second embodiments described below, an example using a cloud wallet will be described, but the technology according to the present invention is not limited to application to cloud wallets and can be applied to digital identity wallets in general that are provided outside the UE 20.

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

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

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

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

[0036] (1) An interface that transmits a wallet endpoint from the UE to the 3GPP network via C-Plane communication is added. There are two patterns: defining it as a new interface and adding information to be transmitted via a Registration Request.

[0037] (2) An IF is added between the 3GPP network and the cloud wallet to request and present attributes / credentials.

[0038] (3) 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.

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

[0040] 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 embodiment, it is also possible to register in the UDM using this subscriber information registration function.

[0041] (System Configuration Example) FIG. 3 shows an example of a system configuration common to the first and second 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), a Verifiable Data Registry (VDR) 70, and a cloud wallet 90. 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 functions 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).

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

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

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

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

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

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

[0048] The cloud wallet 90 has an attribute / credentials DB 91 that stores user attributes / credentials, and a presentation function 92 that presents the attributes / credentials. The cloud wallet 90 may be provided in a 3GPP network or in a network outside the 3GPP network.

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

[0050] (First embodiment: overview) First, the first embodiment will be described. A schematic flow in the first embodiment will be described with reference to Fig. 4. Note that, although the authentication function 60 is used in Fig. 4, the authentication function 60 may be replaced with an AUSF 80.

[0051] In S1, the UE 20 registers, in the cloud wallet 90, a key pair linked to the hardware of the UE 20, such as a Secure Element (SE).

[0052] In S2, the setting terminal 25 sets the attribute / credentials information presentation policy for the cloud wallet 90.

[0053] In S3, the UE 20 submits a network connection request and information related to the wallet endpoint to the authentication function 60. Note that the "information related to the wallet endpoint" may also be called "information related to the wallet endpoint."

[0054] In S4, if necessary, an exchange for selecting an authentication method is carried out between the authentication function 60 and the UDM / UDR (40).

[0055] In S5, the authentication function 60 sends a request to present attributes / credentials to the wallet endpoint (cloud wallet 90) based on the information received from the UE 20 in S3. In S6, the cloud wallet 90 sends the requested attributes / credentials to the authentication function 60. In S7, the authentication function 60 and the VDR 70 verify the attribute information / credentials.

[0056] In addition, in S8, the authentication function 60 transmits a UE authentication request to the UE 20. In S9, the UE 20 transmits a UE authentication response to the authentication function 80, and in S10, the authentication function 60 authenticates the UE 20 and returns the UE authentication result to the UE 20.

[0057] Below, processing sequence 1 and processing sequence 2 will be described as examples of detailed processing sequences relating to authentication using attributes / credentials.

[0058] An example using the authentication function 60, which is a newly defined network node, will be described as a processing sequence example 1, and an example using the AUSF 80 will be described as a processing sequence example 2.

[0059] (First embodiment: processing sequence example 1) Processing sequence example 1 in the first embodiment will be described with reference to Fig. 5. 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:

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

[0061] A user holds attribute / credential certificates (usable for network connection) issued by any entity (such as a company or another user) and registers them in, for example, the cloud wallet 90 .

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

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

[0064] In S101 (step 101) of FIG. 5, 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.

[0065] 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 information related to the wallet endpoint and attributes / credentials. Examples of the information related to the wallet endpoint will be described later. Note that the NW connection request message may include information related to the wallet endpoint.

[0066] The "NW connection request message" may also be called a "connection request message." Examples of the "connection request message" include a Registration Request message, which will be described later.

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

[0068] In S103, (R)AN20 transfers the NW connection request message received from UE20, which includes information related to the wallet endpoint, to AMF30.

[0069] 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 the authentication function 60 as the authentication request destination. In S105, the AMF 30 transmits an authentication request message including information related to the wallet endpoint included in the NW connection request message to the authentication function 60.

[0070] In S106, the authentication function 60 obtains the attributes / credentials using the wallet endpoint and performs authentication processing using the attributes / credentials to verify the attributes / credentials. 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.

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

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

[0073] The processing of the UE 20 after step 10 includes, for example, receiving Registration Accept, sending Registration Complete, etc. Also, in S108, S8 to S10 shown in FIG.

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

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

[0076] In the above optional form, it is assumed that in addition to the attribute / credentials certificate used for the network connection, another attribute / credentials certificate describing information necessary for billing, etc. is acquired from the cloud wallet 90. Note that when the term "attribute / credentials certificate" is used, it may be interpreted that the "attribute / credentials certificate" includes, in addition to the attribute / credentials certificate used for the network connection, another attribute / credentials certificate describing information necessary for billing, etc.

[0077] The attribute / credentials acquisition process in S106 of Fig. 5 will be described with reference to Fig. 6. In S11, the authentication function 60 identifies a wallet endpoint based on information related to the wallet endpoint. Note that the information related to the wallet endpoint may be partially encrypted.

[0078] Examples of information related to a wallet endpoint include a URL and URL parameters indicating the wallet endpoint, a character string indicating the wallet endpoint, and a bit string indicating the wallet endpoint.

[0079] The string indicating the wallet endpoint is a value encrypted with the public key of the cloud wallet operator, such as a user ID (e.g., alice), an authorization control option (e.g., presenting only VC-a), or a signature (a signature using a key linked to the UE hardware).

[0080] Furthermore, SUCI (FIG. 8) may be applied to the bit string indicating the wallet endpoint. For example, a possible method is to indicate a value that is a wallet endpoint in SUPI Type, indicate the identifier of the wallet provider in Home Network Identifier, and indicate the identifier of the user's wallet managed by the wallet provider in Encrypted MSIN.

[0081] In S12, the authentication function 60 and the cloud wallet mutually authenticate that they are legitimate communication partners. In addition, the authentication function 60 and the cloud wallet mutually confirm capabilities related to the presentation of subsequent attributes / credentials (e.g., whether selectively disclosable signatures can be used, whether zero-knowledge proofs can be used).

[0082] In S13, the authentication function 60 requests attributes / credentials from the wallet endpoint (cloud wallet 90). In S14, the cloud wallet 90 responds with the attributes / credentials to the authentication function 60. In S14, the cloud wallet 90 may send information (e.g., VC) indicating the attributes / credentials themselves, or may send attributes / credentials using zero-knowledge proof.

[0083] Next, the authentication process of S106 will be described in detail with reference to FIG. 7. 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.

[0084] When the authentication process using the attribute / credential certificate is started, in S21 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 S22, the VDR 70 responds with these public keys to the authentication function 60.

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

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

[0087] Regarding S21 to S23, in more detail, in S21 and S22, the authentication function 60 receives as input DID0 (certificate issuer identifier) ​​and DID1 (user identifier) ​​included in the received VP / VC, and, using an arbitrary DID Method, obtains (resolves) the DID Document (public key) corresponding to DID0 and the DID Document (public key) corresponding to DID1 from the VDR 70. In S23, 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 signatures, no tampering with the messages).

[0088] In S24, the authentication function 60 requests information regarding the certificate format and status (such as revocation status) from the VDR 70. In S25, the VDR 70 responds with the certificate format and status information. In S26, the authentication function 60 verifies the validity of the certificate.

[0089] Regarding S24 to S26, 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.

[0090] In S27, the authentication function 60 requests the UDM / UDR (40) for certificate information that can be used for network connection, and in S28, the UDM / UDR (40) responds with the certificate information. In S29, 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.

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

[0092] (First embodiment: processing sequence example 2) Next, processing sequence example 2 in the first embodiment will be described with reference to Fig. 9. Processing sequence example 2 is an example of extending an existing NF and an existing IF. In processing sequence example 2, the AUSF 80 includes a function for acquiring attributes / credentials and a function for performing authentication based on attributes / credentials. These functions perform the authentication process of S108, which will be described later.

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

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

[0095] In S101, the UE 20 includes information related to the wallet endpoint in a Registration Request message and sends the Registration Request message including the information related to the wallet endpoint to the (R)AN 10. In S102, the (R)AN 10 sends the Registration Request message including the information related to the wallet endpoint to the AMF / SEAF (30).

[0096] In S103, the AMF / SEAF (30) includes information related to the wallet endpoint in a Nausf_UEAuthentication_Authenticate Request message and sends the Nausf_UEAuthentication_Authenticate Request message including the information related to the wallet endpoint to the AUSF 80 as an authentication request.

[0097] In S104, the AUSF 80 sends a Nudm_UEAuthentication_Get Request message as an authentication request to the UDM / ARPF / SIDF (40).

[0098] At S105, the UDM / ARPF / SIDF (40) performs Authentication Method Selection, where attribute / credential-based authentication is selected as the authentication method.

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

[0100] In S107, the AUSF 80 uses information related to the wallet endpoint to obtain attributes / credentials from the cloud wallet 90. The procedure for obtaining attributes / credentials is the same as the procedure when the authentication function 60 in Fig. 6 is replaced with the AUSF 80. In S108, the AUSF 80 executes authentication processing using the attributes / credentials.

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

[0102] Thereafter, in S110, 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.

[0103] As in the case of the Registration Request message, information related to the wallet endpoint may also be added to the Mobility Registration Update / Periodic Registration Update message.

[0104] The authentication process of S108 will be described in detail with reference to Fig. 10. 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.

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

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

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

[0108] Regarding S108-1 to S108-3, in more detail, in S108-1 and S108-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 S108-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).

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

[0110] Regarding S108-4 to S108-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.

[0111] In S108-7, the AUSF 80 requests the UDM / UDR (40) for certificate information that can be used for network connection, and in S108-8, the UDM / UDR (40) responds with the certificate information. In S108-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.

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

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

[0114] (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 attribute / credentials. Furthermore, according to the technology according to the first embodiment, even if the attribute / credentials is stored in the cloud wallet 90, the attribute / credentials can be acquired on the NW side and authentication based on the attribute / credentials can be performed.

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

[0116] A schematic flow in the second embodiment will be described with reference to Fig. 11. Although the authentication function 60 is used in Fig. 11, the authentication function 60 may be replaced by the AUSF 80.

[0117] In S1, the UE 20 registers, in the cloud wallet 90, a key pair linked to the hardware of the UE 20, such as a Secure Element (SE).

[0118] In S2, the setting terminal 25 sets the attribute / credentials information presentation policy for the cloud wallet 90.

[0119] In S3, the UE 20 transmits a network connection request to the authentication function 60. In S4, as necessary, an exchange for selecting an authentication method is carried out between the authentication function 60 and the UDM / UDR (40).

[0120] In S5, the authentication function 60 transmits a request for information related to the wallet endpoint to the UE 20. The "information related to the wallet endpoint" is as described in the first embodiment. In S6, the UE 20 responds with information related to the wallet endpoint to the authentication function.

[0121] At S7, the authentication function 60 sends a request to present attributes / credentials to the wallet endpoint based on the information received from the UE 20 at S6. At S8, the cloud wallet 90 sends the requested attributes / credentials to the authentication function 60. At S9, the authentication function 60 and the VDR 70 verify the attribute information / credentials.

[0122] In addition, in S10, the authentication function 60 transmits a UE authentication request to the UE 20. In S11, the UE 20 transmits a UE authentication response to the authentication function 80, and in S12, the authentication function 60 authenticates the UE 20 and returns the UE authentication result to the UE 20.

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

[0124] (Second embodiment: processing sequence example 1) Processing sequence example 1 in the second embodiment will be described with reference to Fig. 12. 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:

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

[0126] A user holds attribute / credential certificates (usable for network connection) issued by any entity (such as a company or another user) and registers them in, for example, the cloud wallet 90 .

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

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

[0129] The sequence will be explained below.

[0130] In S201 of FIG. 12, 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.

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

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

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

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

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

[0136] In S206, the authentication function 60 requests the AMF 30 to present information related to the wallet endpoint and transmits a message to the AMF 30 to request 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 one or more of the following five pieces of information. The message may also include information other than the following five pieces of information.

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

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

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

[0140] If the user agrees to provide the information, then in S210, the UE 20 sends a response message including "information related to the wallet endpoint" for obtaining the requested attributes / credentials.

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

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

[0143] In S213, the authentication function 60 uses the information related to the wallet endpoint included in the response message to obtain the attributes / credentials from the cloud wallet 90. The procedure for obtaining the attributes / credentials is the same as the procedure described in the first embodiment with reference to FIG.

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

[0145] In the subsequent step S216, the connection process is executed. Specifically, 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. Also, in step S216, steps S10 to S12 shown in FIG. 11 may be executed.

[0146] Next, details of S214 will be described with reference to Fig. 13. 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.

[0147] When the authentication process using the attribute / credential certificate starts, in S214-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 S214-2, the VDR 70 responds with these public keys to the authentication function 60.

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

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

[0150] Regarding S214-1 to S214-3, in more detail, in S214-1 and S214-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 S214-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).

[0151] In S2134-4, the authentication function 60 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 S214-6, the authentication function 60 verifies the validity of the certificate.

[0152] Regarding S214-4 to S214-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.

[0153] In S214-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. 12.

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

[0155] (Second embodiment: processing sequence example 2) Next, processing sequence example 2 in the second embodiment will be described with reference to Fig. 14. 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 authentication processing, etc., which will be described later.

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

[0157] NW identifier, public key and private key associated with the identifier Certificate information usable for NW connection (certificate type, data format, information to be included in the certificate, etc.) The sequence will be described with reference to FIG. 14 .

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

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

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

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

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

[0163] Upon receiving the Nudm_UEAuthentication_Get Response message containing the string, AUSF80 sends a message to AMF / SEAF (30) in S207 requesting the presentation of information related to the wallet endpoint in order to obtain attributes / credentials that can be used for network connection.

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

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

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

[0167] If the user agrees to the provision of information, in S211, the UE 20 transmits a response message including "information related to the wallet endpoint" for obtaining the requested attributes / credentials. Note that the UE 20 may automatically check the conditions.

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

[0169] In S214, the AUSF 80 uses information related to the wallet endpoint to obtain attributes / credentials from the cloud wallet 90. The procedure for obtaining attributes / credentials is the same as the procedure when the authentication function 60 is replaced with the AUSF 80 in Figure 6.

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

[0171] In S216, 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).

[0172] In the subsequent S217, connection processing is executed. Specifically, the NW Registration processing is completed by executing the processing from step 10 onward 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.

[0173] In the sequence of FIG. 14, new C-Plane messages are used in S207 to S209 and S211 to S213.

[0174] In addition, information related to the wallet endpoint may be added to the Mobility Registration Update / Periodic Registration Update messages, as in the above example.

[0175] Details of S215 will be described with reference to Fig. 15. 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.

[0176] When the authentication process using the attribute / credential certificate starts, in S215-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 S215-2, the VDR 70 responds with these public keys to the AUSF 80.

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

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

[0179] Regarding S215-1 to S215-3, in more detail, in S215-1 and S215-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 S215-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).

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

[0181] Regarding S215-4 to S215-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.

[0182] In S215-7, the AUSF 80 verifies the eligibility of the certificate. More specifically, the AUSF 80 verifies that the conditions for 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.

[0183] 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 Fig. 15, all communications between the AUSF 80 and the VDR 70 or the UDM 40 are performed using new C-Plane messages.

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

[0185] In the second embodiment, the authentication function 60 / AUSF 80 can request information related to a wallet endpoint required to acquire attributes / credentials to be used for network connection from the UE 20, and the UE 20 can transmit information related to the wallet endpoint required to acquire the agreed-upon attributes / credentials to the NW. Therefore, the UE 20 can avoid transmitting unnecessary information to the NW, and the NW can acquire the necessary attributes / credentials to perform authentication.

[0186] According to the technology of the second embodiment, even if the attribute / credential certificate is stored in the cloud wallet 90, the attribute / credential certificate can be obtained on the network side and authentication based on the attribute / credential certificate can be performed.

[0187] (Variations on the First Embodiment) In the first embodiment, both the authentication function 60, which is a new NF, and the AUSF 80, which is an extension of an existing NF, may be used.

[0188] For example, after the AUSF 80 acquires the attribute / credentials through steps S101 to S107 described with reference to Fig. 9, the AUSF 80 transmits the attribute / credentials to the authentication function 60. In this case, the authentication function 60 performs authentication processing using the attribute / credentials and returns the authentication result to the AUSF 80. The subsequent processing is the same as steps S109 and S110 in Fig. 9.

[0189] In the first embodiment, after the AUSF 80 acquires information related to the wallet endpoint through S101 to S103 described with reference to Fig. 9, the AUSF 80 transmits the information related to the wallet endpoint to the authentication function 60. In this case, the authentication function 60 acquires attributes / credentials using the information related to the wallet endpoint, performs authentication processing using the attributes / credentials, and returns the authentication result to the AUSF 80. The subsequent processing is the same as S109 and S110 in Fig. 9.

[0190] (Variations on the Second Embodiment) In the second embodiment, both the authentication function 60, which is a new NF, and the AUSF 80, which is an extension of the existing NF, may be used.

[0191] For example, after the AUSF 80 acquires the attribute / credentials through steps S201 to S214 described with reference to Fig. 14, the AUSF 80 transmits the attribute / credentials to the authentication function 60. In this case, the authentication function 60 performs authentication processing using the attribute / credentials and returns the authentication result to the AUSF 80. The subsequent processing is the same as steps S216 and S217 in Fig. 14.

[0192] In the second embodiment, after the AUSF 80 acquires information related to the wallet endpoint through S201 to S213 described with reference to Fig. 14, the AUSF 80 transmits the information related to the wallet endpoint to the authentication function 60. In this case, the authentication function 60 acquires attributes / credentials using the information related to the wallet endpoint, performs authentication processing using the attributes / credentials, and returns the authentication result to the AUSF 80. The subsequent processing is the same as S216 and S217 in Fig. 14.

[0193] (Variations of Combination of First and Second Embodiments) The first and second embodiments may be combined. For example, when using the authentication function 60, which is a new NF, the authentication function 60 acquires attributes / credentials using information related to a wallet endpoint transmitted from the UE 20 together with a NW connection request, and verifies the attributes / credentials, but the verification fails. In this case, the authentication function 60 requests information related to another wallet endpoint from the UE 20 using the technology of the second embodiment, acquires information related to the wallet endpoint from the UE 20, acquires attributes / credentials using the information related to the wallet endpoint, and verifies the attributes / credentials.

[0194] Furthermore, when using AUSF 80, which is an extension of the existing NF, it is assumed that AUSF 80 acquires attributes / credentials using information related to a wallet endpoint transmitted from UE 20 together with a NW connection request, and verifies the attributes / credentials but fails to verify them. In this case, AUSF 80 requests information related to another wallet endpoint from UE 20 using the technology of the second embodiment, acquires information related to the wallet endpoint from UE 20, acquires attributes / credentials using the information related to the wallet endpoint, and verifies the attributes / credentials.

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

[0196] The NW connection function 21 may include, for example, a digital identity wallet that manages user identifiers, information related to wallet endpoints, and public keys and private keys associated with the identifiers.

[0197] In the network connection function 21, the storage location for the user identifier, information related to the wallet endpoint, and the public key and private key associated with the identifier 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.

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

[0199] When both information related to the SIM and the wallet endpoint are available in the UE 20, or when information related to multiple wallet endpoints is available for network connection, it may be possible to select which information to include in the message and present to the NW side based on a user operation / setting. In the second embodiment, a request message for wallet endpoint information 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 the message and present to the NW side based on a user operation / setting.

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

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

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

[0203] <Network Node 100> FIG. 16 is a diagram illustrating an example of the functional configuration of the network node 100. As shown in FIG.

[0204] As shown in Fig. 16, 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. 16 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.

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

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

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

[0208] 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 100. A communication unit including the transmitter 210 and the receiver 220 may be configured.

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

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

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

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

[0213] 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. 18 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 EES 30 and the terminal 20 described above 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.

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

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

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

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

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

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

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

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

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

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

[0224] 19 shows an example configuration of a vehicle 2001. As shown in FIG. 19 , 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.

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

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

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

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

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

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

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

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

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

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

[0235] This specification discloses at least the configurations described in Supplementary Notes 1 and 2 below.

[0236] <Supplementary Note 1> (Supplementary Item 1) A terminal comprising: a transmitter that transmits a connection request message including information related to a wallet endpoint to a network; and a controller that, in the network, performs authentication processing using a certificate storing personal data based on the information related to the wallet endpoint, and then executes a registration procedure to 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 to the network. (Supplementary Item 3) A network node comprising: a receiver that receives an authentication request message including information related to a wallet endpoint from a specific network node that has received from the terminal the connection request message including information related to the wallet endpoint; a controller that obtains a certificate storing personal data based on the information related to the wallet endpoint and executes 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 information related to a wallet endpoint from a specific network node that has received a connection request message including information related to the wallet endpoint from a terminal, obtains a certificate storing personal data based on the information related to the wallet endpoint, performs authentication processing using the certificate, and transmits the authentication result to the specific network node.

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

[0238] <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 information related to a wallet endpoint; and a controller that executes a registration procedure for the network after the information related to the wallet endpoint is transmitted by the transmitter and authentication is performed in the network using a certificate storing personal data based on the information related to the wallet endpoint. (Supplementary Item 2) The terminal according to Supplementary Item 1, wherein the connection request message is a registration request message that requests registration with 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 information related to a wallet endpoint; and a controller that obtains a certificate storing personal data based on the information related to the wallet endpoint transmitted from the terminal based on the message, and executes authentication using the certificate. (Supplementary Item 4) The network node according to Supplementary Item 3, wherein the message includes a condition for a certificate related to the information related to the wallet endpoint. (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 information related to a wallet endpoint, obtains a certificate storing personal data based on the information related to the wallet endpoint transmitted from the terminal based on the message, and performs authentication processing using the certificate.

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

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

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

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

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

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

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

[0246] Input and output information may be stored in a specific location (for example, memory) or may be managed using a management table. Input and output information may be overwritten, updated, or added to. Output information may be deleted. Input information may be sent to another device.

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

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

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

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

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

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

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

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

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

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

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

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

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

[0260] 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 a mobile object that travels autonomously based on an operational command. The mobile object 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.

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

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

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

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

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

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

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

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

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

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

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

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

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

[0274] DESCRIPTION OF SYMBOLS 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 90 Cloud wallet 91 Attribute / credential certificate DB 92 Presentation function 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 information related to a wallet endpoint to a network; and a control unit that, after an authentication process is performed in the network using a certificate that stores personal data based on the information related to the wallet endpoint, executes a registration procedure to the network after the authentication process.

2. The terminal according to claim 1, wherein the connection request message is a registration request message requesting registration with the network.

3. A network node comprising: a receiving unit that receives an authentication request message including information related to a wallet endpoint from a specific network node that has received a connection request message including information related to the wallet endpoint from a terminal; a control unit that obtains a certificate storing personal data based on the information related to the wallet endpoint and performs authentication processing using the certificate; and a transmitting unit that transmits an authentication result to the specific network node.

4. The network node according to claim 3, wherein the transmission unit requests a management node that manages user data to register the personal data included in the certificate.

5. The network node according to claim 3, wherein the network node is an AUSF.

6. A communication method executed by a network node, which receives an authentication request message including information related to a wallet endpoint from a specific network node that has received a connection request message including information related to the wallet endpoint from a terminal, obtains a certificate storing personal data based on the information related to the wallet endpoint, performs authentication processing using the certificate, and transmits the authentication result to the specific network node.

Images