Network node, communication method, and communication system

Abstract

This network node comprises: a reception unit that receives a user identification information request including first user identification information from a user authentication server in a first network; and a transmission unit that, upon receiving the user identification information request, transmits, to a network node that manages second user identification information used in a second network, a request for causing the network node to identify the second user identification information corresponding to the first user identification information. The transmission unit transmits the identified second user identification information to the server.

Description

Network node, communication method and communication system

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

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

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

[0004] In a conventional 5G system (5GS), when the execution environment of the computational resources, which are the IdP (Identify Provider) and the RP (Relying Party), exists within the core network, ID federation is performed using the OIDC-CIBA procedure.

[0005] 3GPP TS 23.501 V17.9.0 (2023-06) 3GPP TS 23.502 V17.9.0 (2023-06) OpenID Specification "OpenID Connect Client-Initiated Backchannel Authentication Flow - Core 1.0", September 1, 2021

[0006] However, in conventional 5GS, if the IdP exists within a third-party network (i.e., if the IdP is not an authorization function of the core network such as CAPIF), it is not possible to perform ID federation using the OIDC-CIBA procedure with the execution environment within 5GS as the RP.

[0007] The present invention has been made in view of the above points, and makes it possible to execute an authentication procedure when the execution environment on the network is an RP and the IdP exists in a third party's network.

[0008] The network node in this embodiment includes a receiving unit that receives a user identification information request including first user identification information from a server that performs user authentication in a first network, and a transmitting unit that, upon receiving the user identification information request, transmits a request to a network node that manages second user identification information used in a second network to identify the second user identification information corresponding to the first user identification information. The transmitting unit transmits the identified second user identification information to the server.

[0009] According to this embodiment, an authentication procedure can be performed when the execution environment on the network is a RP (Relying Party) and the IdP exists in a third party's network.

[0010] FIG. 1 is a diagram for explaining an example of a communication system. FIG. 2 is a diagram for explaining an example of a communication system in a roaming environment. FIG. 3 is a sequence diagram showing an example of a procedure for an AF in this embodiment to acquire a 5GS side user identifier. FIG. 4 is a diagram showing an example of an OIDC-CIBA procedure in this embodiment. FIG. 5 is a diagram showing an example of the functional configuration of a base station in this embodiment. FIG. 6 is a diagram showing an example of the functional configuration of a terminal in this embodiment. FIG. 7 is a diagram showing an example of the hardware configuration of a base station and a terminal in this embodiment. FIG. 8 is a diagram showing an example of the configuration of a vehicle 2001 in this embodiment.

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

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

[0013] Furthermore, in this embodiment, "configuring" radio parameters etc. may mean that predetermined values ​​are pre-configured, or that radio parameters notified from the network node 30 or the terminal 20 are set.

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

[0015] The RAN (Radio Access Network) is a network node 30 having a radio access function, which may include a base station 10, and is connected to a UE, an AMF (Access and Mobility Management Function), and a UPF (User plane function). The AMF is a network node 30 having functions such as terminating the RAN interface, terminating the NAS (Non-Access Stratum), registration management, connection management, reachability management, and mobility management. The UPF is a network node 30 having functions such as a PDU (Protocol Data Unit) session point to the outside that interconnects with a DN (Data Network), packet routing and forwarding, and user plane QoS (Quality of Service) handling. The UPF and the DN constitute a network slice. In the wireless communication network of this embodiment, multiple network slices may be constructed.

[0016] The AMF is connected to the UE, RAN, SMF (Session Management function), NSSF (Network Slice Selection Function), NEF (Network Exposure Function), NRF (Network Repository Function), UDM (Unified Data Management), AUSF (Authentication Server Function), PCF (Policy Control Function), and AF (Application Function). The AMF, SMF, NSSF, NEF, NRF, UDM, AUSF, PCF, and AF are network nodes 30 connected to each other via interfaces based on their respective services, Namf, Nsmf, Nnssf, Nnef, Nnrf, Nudm, Nausf, Npcf, and Naf. In this embodiment, a third-party authorization server 40 (described later) may have the function of an AF.

[0017] The SMF is a network node 30 having functions such as session management, UE IP (Internet Protocol) address allocation and management, DHCP (Dynamic Host Configuration Protocol) function, ARP (Address Resolution Protocol) proxy, and roaming function. The NEF is a network node 30 having a function of notifying other NFs (Network Functions) of capabilities and events. The NSSF is a network node 30 having functions such as selecting a network slice to which a UE connects, determining an allowed NSSAI (Network Slice Selection Assistance Information), determining an NSSAI to be set, and determining an AMF set to which a UE connects. The PCF is a network node 30 having a function of controlling network policies. The AF is a network node 30 having a function of controlling application servers. The NRF is a network node 30 having a function of discovering NF instances that provide services. The UDM is a network node 30 that manages subscriber data and authentication data. The UDM is connected to a UDR (User Data Repository) that stores the data.

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

[0019] The RAN is a network node 30 having a radio access function, and is connected to the UE, the AMF, and the UPF. The AMF is a network node 30 having functions such as RAN interface termination, NAS termination, registration management, connection management, reachability management, and mobility management. The UPF is a network node 30 having functions such as a PDU session point to the outside that interconnects with the DN, packet routing and forwarding, and user plane QoS handling. The UPF and the DN constitute a network slice. In the wireless communication network of this embodiment, multiple network slices are constructed.

[0020] The AMF is connected to the UE, RAN, SMF, NSSF, NEF, NRF, UDM, AUSF, PCF, AF, and SEPP (Security Edge Protection Proxy). The AMF, SMF, NSSF, NEF, NRF, UDM, AUSF, PCF, and AF are network nodes 30 that are interconnected via respective service-based interfaces, Namf, Nsmf, Nnssf, Nnef, Nnrf, Nudm, Nausf, Npcf, and Naf.

[0021] The SMF is a network node 30 having functions such as session management, UE IP address allocation and management, DHCP function, ARP proxy, and roaming function. The NEF is a network node 30 having a function of notifying other NFs of capabilities and events. The NSSF is a network node 30 having functions such as selecting a network slice to which a UE connects, determining an allowed NSSAI, determining a configured NSSAI, and determining an AMF set to which a UE connects. The PCF is a network node 30 having a function of controlling network policies. The AF is a network node 30 having a function of controlling application servers. The NRF is a network node 30 having a function of discovering NF instances that provide services. The SEPP is a non-transparent proxy that filters control plane messages between PLMNs (Public Land Mobile Networks). The vSEPP shown in FIG. 2 is a SEPP in the visited network, and the hSEPP is a SEPP in the home network.

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

[0023] Here, some of the 5G Advanced / 6G use cases have common requirements shown in 1) and 2) below.

[0024] 1) A telecommunications carrier provides a service that lends computing resources within the network and the execution environment on those computing resources to subscribers. If a cloud environment is assumed, this may be equivalent to the telecommunications carrier providing containers to subscribers. However, no specific technology related to containers is required. 2) Subscribers use those computing resources and execution environments as the termination point for sending and receiving communications related to them.

[0025] To achieve the above requirements, a function called UCRF (User Computing Resource Function) may be introduced, which allows the container to be set for each subscriber. Furthermore, a new function called CRMF (Computing Resource Management Function) that controls UCRF may be introduced. Note that the names UCRF and CRMF are merely examples, and the functions may be called by other names.

[0026] Regarding the session-related procedures, the CRMF may be regarded as the SMF and the UCRF as the UPF. For example, the following 1) to 3) may be defined.

[0027] 1) CRMF session establishment procedures, CRMF session modification procedures, and CRMF session release procedures similar to the procedures related to PDU sessions may be defined between the UE and CRMF.

[0028] 2) A UCRF session establishment procedure, a UCRF session modification procedure, and a UCRF session release procedure similar to the procedures related to a PFCP (Packet Forwarding Control Protocol) session may be defined between the CRMF and the UCRF.

[0029] 3) A service request procedure may be defined to activate a deactivated container.

[0030] It is expected that telecommunications carriers will provide services such as UCRF and CRMF that lend computing resources within the network and the execution environment on the computing resources to subscribers. One use case is when an application launched on an execution environment (e.g., UCRF and / or CRMF) within 5GS that is not directly under the management or operation of the user accesses a third-party service outside the core network and performs ID federation (e.g., obtaining a user profile on the service side).

[0031] To achieve ID federation as in the above case, the OIDC-CIBA (OpenID Connect Client-Initiated Backchannel Authentication) procedure is used in the CAPIF core function and CAPIF authorization function, with the execution environment in 5GS as the RP (Relying Party). In conventional 5GS, when an IdP (ID Provider) exists in a core network such as CAPIF, ID federation can be achieved using the OIDC-CIBA procedure.

[0032] However, in conventional 5GS, if the IdP exists within a third-party network (i.e., if the IdP is not an authorization function of the core network such as CAPIF), ID federation using the OIDC-CIBA procedure cannot be realized.

[0033] According to this embodiment, ID federation is possible using an authentication procedure (e.g., OIDC-CIBA) when the execution environment in a network (e.g., 5GS) is the RP and the third-party authorization server is the IdP. According to this embodiment, the RP is the execution environment in 5GS, and the network user identification information used in the OIDC-CIBA procedure when the IdP exists in a third-party network can be provided to the IdP in the third-party network.

[0034] Below, we will describe a method for enabling the execution of OIDC-CIBA procedures in a system where the RP is an execution environment within 5GS and the IdP is a third-party authorization server.

[0035] In the conventional system, when the IdP is a third-party authorization server, the IdP cannot obtain the 5GS-side user identifier used in the OIDC-CIBA procedure. This embodiment extends the NEF service and the UDM service to provide a method for the IdP to obtain the 5GS-side user identifier.

[0036] In this embodiment, the IdP operates as an AF. The IdP is an example of a server that performs user authentication.

[0037] FIG. 3 is a sequence diagram showing an example of a procedure for the AF to acquire a 5GS-side user identifier in this embodiment.

[0038] 3, the third-party authorization server 40 is an IdP and operates as an AF. The third-party authorization server 40 is a server located in a third-party network. The third-party network is a network different from the core network (e.g., 5GC).

[0039] The NEF 30A may be referred to as a network node that provides an NEF service or a network node that has the functionality of an NEF, and the UDM 30B may be referred to as a network node that provides a UDM service or a network node that has the functionality of a UDM.

[0040] In step S101, the third-party authorization server 40 (that is, the AF 40) which is an IdP sends a user identifier request to the NEF 30A.

[0041] The user identifier request includes AF-side user identification information possessed by the AF 40. The AF-side user identification information is information that is held in common by the IdP and the 5GS and uniquely identifies a user. The AF-side user identification information may include, for example, at least one of a telephone number, an address, or a full name, or may include any combination of these. The AF-side user identification information is not limited to information such as a telephone number, but may be any information that can uniquely identify a user. The AF-side user identification information possessed by the AF may also be referred to as IdP-side user identification information possessed by the IdP. The AF-side user identification information (IdP-side user identification information) is an example of first user identification information.

[0042] In step S102, the NEF 30A determines whether to approve the user identifier request from the AF 40.

[0043] If the user identifier request is not approved in step S102, the NEF 30A sends the AF 40 a user identifier request response including a Result value indicating failure of approval in step S103b.

[0044] If the user identifier request is approved in step S102, the NEF 30A transmits a 5GS-side user identifier request to the UDM 30B in step S103a. The 5GS-side user identifier request includes the AF-side user identification information.

[0045] The UDM 30B manages and provides the 5GS-side user identifier. The UDM 30B in this embodiment is extended so as to be able to execute a new service that provides the 5GS-side user identifier based on the AF-side user identification information. The 5GS-side user identifier is, for example, a Subscription Permanent Identifier (SUPI). The 5GS-side user identifier is not limited to a SUPI, and may be other subscriber information that identifies a user. The 5GS-side user identifier is an example of second user identification information. The 5GS-side user identifier may also be referred to as a 5GC-side user identifier. For example, the UDR holds information (e.g., a table) in which the 5GS-side user identifier and the AF-side user identification information are associated, and the UDM 30B uses the information held in the UDR.

[0046] In step S104, the UDM 30B identifies a 5GS-side user identifier based on the received AF-side user identification information. The UDM 30B identifies a 5GS-side user identifier that corresponds to the received AF-side user identification information from among the 5GS-side user identifiers it holds.

[0047] If the 5GS-side user identifier is identified in step S104, then in step S105a, the UDM 30B transmits a 5GS-side user identifier request response including the identified 5GS-side user identifier to the NEF 30A.

[0048] In step S106a, the NEF 30A transmits to the AF 40 a user identifier request response including the 5GS side user identifier received from the UDM 30B.

[0049] On the other hand, if the 5GS side user identifier is not identified in step S104, in step S105b, UDM30B sends a 5GS side user identifier request response to NEF30A, which includes a Result value indicating that the 5GS side user identifier is not available.

[0050] In step S106b, the NEF 30A transmits to the AF 40 a user identifier request response including a Result value indicating that the 5GS-side user identifier is not available.

[0051] Thus, according to this embodiment, based on a request from an IdP (i.e., AF) in a third-party network, the identified 5GS-side user identifier identified by the extended NEF service and UDM service can be provided to the IdP. In this way, the third-party authorization server (IdP) in this embodiment can associate the IdP-side user identification information (AF-side user identification information) with the 5GS-side user identifier. As a result, even when the IdP exists in the third-party network, an authentication procedure can be performed using the execution environment in the 5GS as the RP, and ID federation can be performed.

[0052] Next, we will explain the OIDC-CIBA procedure in this embodiment in a system where the RP is an execution environment within 5GS and the IdP is a third-party authorization server.

[0053] In conventional OIDC-CIBA procedures, authentication using a 5GS-side user identifier could not be performed. According to the OIDC-CIBA procedure in this embodiment, the 5GS internal execution environment sends a backchannel authentication request including a 5GS-side user identifier to a third-party authorization server, and the third-party authorization server identifies the IdP-side user identifier based on the 5GS-side user identifier. As a result, the OIDC-CIBA procedure in this embodiment enables authentication using a 5GS-side user identifier.

[0054] FIG. 4 shows an example of an OIDC-CIBA procedure when the intra-5GS execution environment 30C in this embodiment is an RP and the third-party authorization server 40 is an IdP. The intra-5GS execution environment 30C may be, for example, CRMF and / or UCRF. The flow in FIG. 4 may be a flow for the CIBA Ping mode. As shown in FIG. 4, the intra-5GS execution environment 30C includes a client notification EP (Endpoint). The third-party authorization server 40 includes a backchannel authentication EP, a token EP, and an introspection EP. The terminal 20 (UE) may be an authentication device. The intra-5GS execution environment 30C may be a consumption device or a client.

[0055] The third-party authorization server 40 (IdP) in the example of Fig. 4 holds information in which the IdP-side user identification information and the 5GS-side user identifier are associated, or has access to information in which the IdP-side user identification information and the 5GS-side user identifier are associated. For example, the IdP-side user identification information and the 5GS-side user identifier may be associated in the third-party authorization server 40 by the procedure of Fig. 3.

[0056] In step S1, the intra-5GS execution environment 30C sends a backchannel authentication request (HTTP POST) to the backchannel authentication EP of the third-party authorization server 40. The backchannel authentication request includes a 5GS-side user identifier (for example, SUPI) as a login_hint parameter.

[0057] In step S2, the third-party authorization server 40 verifies the client and identifies the user based on the 5GS-side user identifier included in the backchannel authentication request. For example, the third-party authorization server 40 identifies the IdP-side user identifier corresponding to the 5GS-side user identifier included in the backchannel authentication request from the stored information associating the IdP-side user identifier with the 5GS-side user identifier.

[0058] In step S3, the third-party authorization server 40 uses the identified IdP-side user identifier to send a request for authentication and authorization of the user to the terminal 20. The backchannel authentication EP of the third-party authorization server 40 sends an ACK indicating that the authentication request was successful, including the auth_req_id, to the intra-5GS execution environment 30C.

[0059] In step S4, the user transmits a response to the authentication and authorization request from the terminal 20 to the third-party authorization server 40. The intra-5GS execution environment 30C transmits a token request including auth_req_id to the token EP of the third-party authorization server 40.

[0060] In step S5, the token EP of the third-party authorization server 40 generates an ID token and an access token based on the token request, and sends a token response including the generated ID token and access token to the 5GS execution environment 30C.

[0061] In step S6, the third-party authorization server 40 sends a completion notification including the auth_req_id to the intra-5GS execution environment 30C. The intra-5GS execution environment 30C sends the access token and the ID token to the upper service user profile and calls the API.

[0062] In step S7, the upper service user profile performs signature and token verification with the introspection EP of the third-party authorization server 40.

[0063] In step S8, the 5GS execution environment 30C obtains resources from the higher-level service user profile.

[0064] Thus, according to this embodiment, in a system in which the RP is an execution environment within the 5GS and the IdP is a third-party authorization server, the OIDC-CIBA procedure can be executed using a 5GS-side user identifier.

[0065] (Device Configuration) Next, a description will be given of an example of the functional configuration of the base station 10, network node 30, and terminal 20 that perform the processes and operations described above. The base station 10, network node 30, and terminal 20 include functions for performing the above-described embodiments. However, the base station 10, network node 30, and terminal 20 may each include only a part of the functions of the embodiments.

[0066] <Base Station 10 and Network Node 30> Fig. 5 is a diagram showing an example of the functional configuration of the base station 10. As shown in Fig. 5, the base station 10 has a transmitting unit 110, a receiving unit 120, a setting unit 130, and a control unit 140. The functional configuration shown in Fig. 5 is merely an example. As long as the operation according to this embodiment can be performed, the names of the functional divisions and functional units may be any. Note that the network node 30 may have the same functional configuration as the base station 10. Furthermore, a network node 30 having multiple different functions in the system architecture may be composed of multiple network nodes 30 separated by function.

[0067] The transmitter 110 includes a function of generating a signal to be transmitted to the terminal 20 or another network node 30 and transmitting the signal by wire or wirelessly. The receiver 120 includes a function of receiving various signals transmitted from the terminal 20 or another network node 30 and acquiring, for example, information of a higher layer from the received signal.

[0068] The setting unit 130 stores in a storage device preset setting information and various setting information to be transmitted to the terminal 20, and reads out the information from the storage device as needed. The content of the setting information includes, for example, settings related to computational resources and authentication procedures.

[0069] As described in the embodiments, the control unit 140 performs processing related to computational resources and authentication procedures in the network. The control unit 140 also performs processing related to communication with the terminal 20. The function unit related to signal transmission in the control unit 140 may be included in the transmitting unit 110, and the function unit related to signal reception in the control unit 140 may be included in the receiving unit 120.

[0070] <Terminal 20> Fig. 6 is a diagram showing an example of the functional configuration of the terminal 20. As shown in Fig. 6, the terminal 20 has a transmitting unit 210, a receiving unit 220, a setting unit 230, and a control unit 240. The functional configuration shown in Fig. 6 is merely an example. The names of the functional divisions and functional units may be any names as long as they can perform the operations according to this embodiment.

[0071] The transmitter 210 creates a transmission signal from the transmission data and transmits the transmission signal wirelessly. The receiver 220 receives various signals wirelessly and acquires higher layer signals from the received physical layer signals. The receiver 220 also has a function of receiving NR-PSS, NR-SSS, NR-PBCH, DL / UL control signals, reference signals, etc. transmitted from the network node 30.

[0072] The setting unit 230 stores various setting information received from the network node 30 by the receiving unit 220 in a storage device and reads it from the storage device as needed. The setting unit 230 also stores setting information that is set in advance. The setting information includes, for example, settings related to computational resources and authentication procedures.

[0073] As described in the embodiments, the control unit 240 performs processing related to connection control to the network and the network slice. The control unit 240 also performs processing related to the authentication procedure. A functional unit related to signal transmission in the authentication control unit 240 may be included in the transmitting unit 210, and a functional unit related to signal reception in the control unit 240 may be included in the receiving unit 220.

[0074] (Hardware Configuration) The block diagrams (FIGS. 5 and 6) used to explain the above embodiments show functional blocks. These functional blocks (components) are realized by any combination of at least one of hardware and software. Furthermore, the method for realizing each functional block is not particularly limited. That is, each functional block may be realized using a single device that is physically or logically coupled, or may be realized using two or more physically or logically separated devices that are directly or indirectly connected (for example, using wires, wirelessly, etc.) and these multiple devices. The functional block may be realized by combining software with the single device or the multiple devices.

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

[0076] For example, the network node 30, the terminal 20, etc. according to an embodiment of the present disclosure may function as a computer that performs processing of the wireless communication method of the present disclosure. Fig. 7 is a diagram illustrating an example of the hardware configuration of the base station 10 and the terminal 20 according to an embodiment of the present disclosure. The network node 30 may have the same hardware configuration as the base station 10. The above-described base station 10 and the terminal 20 may be physically configured as a computer device including a processor 1001, a storage device 1002, an auxiliary storage device 1003, a communication device 1004, an input device 1005, an output device 1006, a bus 1007, etc.

[0077] In the following description, the term "apparatus" can be interpreted as a circuit, a device, a unit, etc. The hardware configuration of the base station 10 and the terminal 20 may be configured to include one or more of the apparatuses shown in the drawings, or may be configured to exclude some of the apparatuses.

[0078] Each function in the base station 10 and the terminal 20 is realized by loading specified software (programs) onto hardware such as the processor 1001, the memory device 1002, etc., so that the processor 1001 performs calculations, controls communication by the communication device 1004, and controls at least one of reading and writing data in the memory device 1002 and the auxiliary memory device 1003.

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

[0080] Furthermore, the processor 1001 reads programs (program codes), software modules, data, etc. from at least one of the auxiliary storage device 1003 and the communication device 1004 into the storage device 1002 and executes various processes in accordance with the programs. The programs used are those that cause a computer to execute at least some of the operations described in the above-described embodiments. For example, the control unit 140 of the base station 10 shown in FIG. 5 may be implemented by a control program stored in the storage device 1002 and running on the processor 1001. Furthermore, for example, the control unit 240 of the terminal 20 shown in FIG. 6 may be implemented by a control program stored in the storage device 1002 and running on the processor 1001. While the above-described various processes have been described as being executed by one processor 1001, they may also be executed simultaneously or sequentially by two or more processors 1001. The processor 1001 may be implemented by one or more chips. The programs may also be transmitted from a network via a telecommunications line.

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

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

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

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

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

[0086] Furthermore, the base station 10 and the terminal 20 may be configured to include hardware such as a microprocessor, a digital signal processor (DSP), an application specific integrated circuit (ASIC), a programmable logic device (PLD), or a field programmable gate array (FPGA), and some or all of the functional blocks may be realized by the hardware. For example, the processor 1001 may be implemented using at least one of these pieces of hardware.

[0087] Fig. 8 shows an example configuration of a vehicle 2001. As shown in Fig. 8, the vehicle 2001 includes a drive unit 2002, a steering unit 2003, an accelerator pedal 2004, a brake pedal 2005, a shift lever 2006, front wheels 2007, rear wheels 2008, an axle 2009, an electronic control unit 2010, various sensors 2021 to 2029, an information service unit 2012, and a communication module 2013. Each aspect / embodiment described in the present disclosure may be applied to a communication device mounted on the vehicle 2001, and may be applied to the communication module 2013, for example.

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

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

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

[0091] The information service unit 2012 is composed of various devices, such as a car navigation system, an audio system, speakers, a television, and a radio, for providing various types of information such as driving information, traffic information, and entertainment information, and one or more ECUs for controlling these devices. The information service unit 2012 provides various types of multimedia information and multimedia services to the occupants of the vehicle 2001 by using information acquired from external devices via the communication module 2013, etc.

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

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

[0094] The communication module 2013 is a communication device that can be controlled by the microprocessor 2031 of the electronic control unit 2010 and can communicate with an external device. For example, it transmits and receives various information to and from the external device via wireless communication. The communication module 2013 may be located either inside or outside the electronic control unit 2010. The external device may be, for example, a base station, a mobile station, or the like.

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

[0096] The communication module 2013 receives various information (traffic information, traffic signal information, vehicle distance information, etc.) transmitted from external devices and displays it on the information service unit 2012 provided in the vehicle 2001. The communication module 2013 also stores the various information received from the external devices in a memory 2032 that can be used by the microprocessor 2031. Based on the information stored in the memory 2032, the microprocessor 2031 may control the drive unit 2002, steering unit 2003, accelerator pedal 2004, brake pedal 2005, shift lever 2006, front wheels 2007, rear wheels 2008, axles 2009, sensors 2021 to 2029, etc. provided in the vehicle 2001.

[0097] As described above, a network node (e.g., a network node having the functionality of a NEF) in this embodiment includes a receiving unit that receives a user identification information request including first user identification information from a server (e.g., an IdP) that performs user authentication in a first network, and a transmitting unit that, upon receiving the user identification information request, transmits a request to a network node that manages second user identification information used in a second network to identify the second user identification information corresponding to the first user identification information. The transmitting unit transmits the identified second user identification information to the server.

[0098] With the above configuration, the RP is an execution environment within a network (e.g., 5GS), and the network user identification information (e.g., SUPI) used in an authentication procedure (e.g., OIDC-CIBA) when the IdP exists in a third-party network can be provided to the IdP in the third-party network. As a result, even when the IdP exists in the third-party network, an authentication procedure can be performed with the execution environment on the network as the RP, and ID federation can be performed.

[0099] In this embodiment, the network node that manages the second user identification information has a function of Unified Data Management (UDM). In this embodiment, the first network is a third party network.

[0100] The above configuration allows the RP to provide 5GS user identification information to an IdP in a third-party network for use in the OIDC-CIBA procedure when the RP is an execution environment within the 5GS and the IdP is located in a third-party network.

[0101] In this embodiment, the communication method performed by the first network node includes the steps of receiving a user identification request including first user identification information from a server in the first network that performs user authentication; upon receiving the user identification information request, sending a request to a second network node that manages second user identification information used in a second network to identify the second user identification information corresponding to the first user identification information; and sending the identified second user identification information to the server.

[0102] With the above configuration, the RP is an execution environment within the network, and the IdP is located in a third-party network, and the network user identification information (e.g., SUPI) used in the authentication procedure (e.g., OIDC-CIBA) can be provided to the IdP in the third-party network.

[0103] The communication system in this embodiment includes a first network node and a second network node that manages second user identification information. The first network node receives a user identification information request including a first user identification information from a server that performs user authentication in a first network, and upon receiving the user identification information request, transmits a request to a network node that manages second user identification information used in a second network to identify the second user identification information corresponding to the first user identification information. The second network node identifies the second user identification information corresponding to the first user identification information based on the request, and transmits the identified second user identification information to the first network node. The first network node transmits the identified second user identification information to the server.

[0104] With the above configuration, the RP is an execution environment within the network, and the IdP is located in a third-party network, and the network user identification information (e.g., SUPI) used in the authentication procedure (e.g., OIDC-CIBA) can be provided to the IdP in the third-party network.

[0105] The above communication system in this embodiment further includes a third network node in a second network, the third network node sending a backchannel authentication request including second user identification information to the server.

[0106] With the above configuration, the RP is an execution environment within the network (e.g., 5GS), and the IdP is in a third-party network, and an authentication procedure (e.g., OIDC-CIBA) can be performed. In the above configuration, the third network node is, for example, an execution environment within the 5GS that provides an execution environment for computational resources.

[0107] (Supplementary Notes on the Embodiments) Although the present embodiment has 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 replacements. While specific numerical examples have been used to facilitate understanding of the invention, unless otherwise specified, these numerical values ​​are merely examples, and any appropriate values ​​may be used. The division of items in the above description is not essential to the present invention. Two or more items may be combined as needed, and items described in one item may apply to items described in another item (as long as there is no contradiction). Boundaries between functional units or processing units in functional block diagrams do not necessarily correspond to physical component boundaries. The operations of multiple functional units may be physically performed by a single component, or the operations of a single functional unit may be physically performed by multiple components. The order of processing steps described in the embodiments may be reversed as long as there is no contradiction. For convenience of processing description, the network node 30 and the terminal 20 have been described using functional block diagrams. However, such devices may be realized by hardware, software, or a combination thereof. The software operated by the processor of the network node 30 according to this embodiment and the software operated by the processor of the terminal 20 according to this embodiment 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.

[0108] Furthermore, the notification of information is not limited to the aspects / embodiments described in the present disclosure, and may be performed using other methods. For example, the notification of information may be performed by physical layer signaling (e.g., Downlink Control Information (DCI) and Uplink Control Information (UCI)), higher layer signaling (e.g., Radio Resource Control (RRC) signaling, Medium Access Control (MAC) signaling, broadcast information (Master Information Block (MIB) and System Information Block (SIB)), other signals, or a combination thereof. Furthermore, the RRC signaling may be referred to as an RRC message, and may be, for example, an RRC Connection Setup message, an RRC Connection Reconfiguration message, or the like.

[0109] Each aspect / embodiment described in the present disclosure may be applied to at least one of systems using LTE (Long Term Evolution), LTE-Advanced (LTE-A), SUPER 3G, IMT-Advanced, 4G (4th generation mobile communication system), 5G (5th generation mobile communication system), FRA (Future Radio Access), NR (New Radio), W-CDMA (registered trademark), GSM (registered trademark), CDMA2000, UMB (Ultra Mobile Broadband), IEEE 802.11 (Wi-Fi (registered trademark)), IEEE 802.16 (WiMAX (registered trademark)), IEEE 802.20, UWB (Ultra-Wide Band), Bluetooth (registered trademark), or other suitable systems, and next-generation systems enhanced based on these. Furthermore, a combination of multiple systems (e.g., a combination of at least one of LTE and LTE-A with 5G, etc.) may also be applied.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0127] At least one of the base station and the mobile station may be referred to as a transmitting device, a receiving device, a communication device, etc. At least one of the base station and the mobile station may be a device mounted on a mobile body, the mobile body itself, etc. The mobile body may be a vehicle (e.g., a car, an airplane, etc.), an unmanned mobile body (e.g., a drone, an autonomous vehicle, etc.), or a robot (manned or unmanned). At least one of the base station and the mobile station may also include devices that do not necessarily move during communication operations. For example, at least one of the base station and the mobile station may be an IoT (Internet of Things) device such as a sensor.

[0128] Furthermore, a base station in the present disclosure may be read as a user terminal. For example, the aspects / embodiments of the present disclosure may be applied to a configuration in which communication between a base station and a user terminal is replaced with communication between multiple terminals 20 (which may be called, for example, Device-to-Device (D2D) or Vehicle-to-Everything (V2X)). In this case, the terminal 20 may be configured to have the functions of the above-described network node 30. Furthermore, terms such as "uplink" and "downlink" may be read as terms corresponding to terminal-to-terminal communication (for example, "side"). For example, terms such as an uplink channel and a downlink channel may be read as a side channel.

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

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

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

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

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

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

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

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

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

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

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

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

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

Claims

1. A network node comprising: a receiving unit that receives a user identification information request including a first user identification information from a server in a first network that performs user authentication; and a transmitting unit that, upon receiving the user identification information request, transmits a request to a network node that manages second user identification information used in a second network to identify the second user identification information corresponding to the first user identification information, wherein the transmitting unit transmits the identified second user identification information to the server.

2. The network node according to claim 1, wherein the network node that manages the second user identification information has a UDM (Unified Data Management) function.

3. The network node of claim 1, wherein the first network is a third party network.

4. A communication method executed by a first network node, comprising: a step of receiving a user identification information request including a first user identification information from a server in a first network that performs user authentication; upon receiving the user identification information request, a step of sending a request to a second network node that manages second user identification information used in a second network to identify the second user identification information corresponding to the first user identification information; and a step of sending the identified second user identification information to the server.

5. A communications system comprising a first network node and a second network node that manages second user identification information, wherein the first network node: receives a user identification information request including a first user identification information from a server in a first network that performs user authentication; upon receiving the user identification information request, transmits a request to a network node that manages second user identification information used in a second network to identify the second user identification information corresponding to the first user identification information; the second network node: identifies the second user identification information corresponding to the first user identification information based on the request; and transmits the identified second user identification information to the first network node; and the first network node transmits the identified second user identification information to the server.

6. The communication system of claim 5, further comprising a third network node in a second network, the third network node transmitting a backchannel authentication request including the second user identification information to the server.

Images