Terminal and network node
The proposed solution addresses the challenge of user verification in 6G IMS data channel networks by authenticating the called user and confirming their identity through a controlled communication setup, ensuring secure and reliable communication paths in shared terminal scenarios.
Patent Information
- Application Number
- PCT/JP2023/017641
- Authority / Receiving Office
- WO · WO
- Patent Type
- Applications
- Current Assignee / Owner
- Filing Date
- 2023-05-10
- Publication Date
- 2024-11-14
AI Technical Summary
In 6G communication systems, there is no defined procedure to confirm whether the user using a shared terminal is the same as the intended user by the caller in an IMS data channel network, leading to potential authentication and verification challenges.
A procedure is established involving authentication of the called user using a called terminal in the called network, with confirmation by the calling user, and communication setup between terminals through a control unit that generates messages for data channel establishment after verifying user authenticity.
This procedure ensures that the user using a shared terminal is correctly identified as the intended user, enabling secure and reliable communication in IMS data channel networks by confirming user authenticity before establishing communication paths.
Smart Images

Figure JP2023017641_14112024_PF_FP_ABST
Abstract
Description
Terminals and Network Nodes
[0001] The present invention relates to a terminal and a network node in 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).
[0004] Furthermore, as an IMS (IP Multimedia Subsystem) architecture that supports the data channel capabilities of terminals, specifications for an IMS data channel network are being studied (see, for example, Non-Patent Document 2). In the IMS data channel network, a Data Channel Signalling Function (DCSF) having a signaling function, a Data Channel Media Function (DCMF) having a media-related function, and a Data Channel Application Server (DCAS) that is an application server are arranged on both the calling and called sides.
[0005] 3GPP TS 23.501 V18.1.0 (2023-03) 3GPP TS 23.228 V18.1.0 (2023-03) 3GPP TS 26.114 V18.2.0 (2023-03) IETF RFC8864
[0006] In 6G, the next generation after 5G, a use case is being considered in which communication is performed using a shared terminal that can be used by multiple users in an IMS network. However, in this use case, no procedure is specified for confirming whether the user using the shared terminal is the user intended by the calling user who is receiving the call.
[0007] The present invention has been made in view of the above points, and an object of the present invention is to define a procedure for confirming whether a user using a shared terminal is the same as the called user intended by the calling user in an IMS data channel network.
[0008] According to the disclosed technology, a terminal is provided which has a control unit that generates a message including a request to authenticate a called user using a called terminal in a called network and to confirm the called user by the calling user, and a request to set up a data channel between its own terminal and the calling network, and between the calling network and the called terminal, a transmitting unit that transmits the message, and a receiving unit that receives information about the called user, wherein the transmitting unit transmits information indicating that the calling user has confirmed the called user based on the information about the called user, the receiving unit receives completion information indicating that the authentication and the confirmation have been completed, and the control unit establishes a communication path between its own terminal and the called terminal after receiving the completion information.
[0009] According to the disclosed technique, in an IMS data channel network, it is possible to define a procedure for confirming whether a user using a shared terminal is the same as the called user intended by the calling user.
[0010] 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 an IMS data channel network. FIG. 2 is a diagram showing an example of a first sequence diagram in an embodiment of the present invention. FIG. 3 is a diagram showing an example of SDP contents in an embodiment of the present invention. FIG. 4 is a diagram showing an example of a second sequence diagram in an embodiment of the present invention. FIG. 5 is a diagram showing an example of a third sequence diagram in an embodiment of the present invention. FIG. 6 is a diagram showing an example of a fifth sequence diagram in an embodiment of the present invention. FIG. 7 is a diagram showing an example of a seventh sequence diagram in an embodiment of the present invention. FIG. 8 is a diagram showing an example of an eighth sequence diagram in an embodiment of the present invention. FIG. 9 is a diagram showing an example of a ninth sequence diagram in an embodiment of the present invention. FIG. 10 is a diagram showing an example of a tenth sequence diagram in an embodiment of the present invention. FIG. 11 is a diagram showing an eleventh sequence diagram in an embodiment of the present invention. FIG. 12 is a diagram showing an example of the functional configuration of a base station 10 and a network node 30 in an embodiment of the present invention. FIG. 13 is a diagram showing an example of the functional configuration of a terminal 20 in an embodiment of the present invention. FIG. 14 is a diagram showing an example of the hardware configuration of a base station 10, a terminal 20, and a network node 30 in an embodiment of the present invention. FIG. 15 is a diagram showing an example of the configuration of a vehicle 2001 in an embodiment of the present invention.
[0011] Hereinafter, an embodiment of the present invention will be described with reference to the drawings. Note that the embodiment described below is an example, and the embodiment to which the present invention is applied is not limited to the following embodiment.
[0012] In the operation of the wireless communication system according to the embodiment of the present invention, existing technology is used as appropriate. However, the existing technology is, for example, the existing LTE, but is not limited to the existing LTE. Furthermore, the term "LTE" used in this specification has a broad meaning including LTE-Advanced, and systems subsequent to LTE-Advanced (e.g., NR), or wireless LAN (Local Area Network), unless otherwise specified.
[0013] Furthermore, in the embodiments of the present invention, "configuring" radio parameters and the like may mean that predetermined values are pre-configured, or that radio parameters notified from the network node 30 or the terminal 20 are set.
[0014] Fig. 1 is a diagram illustrating an example of a communication system. As shown in Fig. 1, the communication system is composed of a UE, which is a terminal 20, and multiple network nodes 30. Hereinafter, it is assumed that one network node 30 corresponds to each function, but multiple functions may be realized by one network node 30, or multiple network nodes 30 may realize one function. Furthermore, the "connection" described below may be a logical connection or a physical connection.
[0015] The RAN (Radio Access Network) is a network node 30 having a radio access function, which may include a base station 10, and is connected to a UE, an AMF (Access and Mobility Management Function), and a UPF (User plane function). The AMF is a network node 30 having functions such as terminating the RAN interface, terminating the NAS (Non-Access Stratum), registration management, connection management, reachability management, and mobility management. The UPF is a network node 30 having functions such as a PDU (Protocol Data Unit) session point to the outside that interconnects with a DN (Data Network), packet routing and forwarding, and user plane QoS (Quality of Service) handling. The UPF and the DN constitute a network slice. In the wireless communication network according to the embodiment of the present invention, multiple network slices are 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 that are mutually connected via interfaces based on their respective services, Namf, Nsmf, Nnssf, Nnef, Nnrf, Nudm, Nausf, Npcf, and Naf.
[0017] The SMF is a network node 30 having functions such as session management, UE IP (Internet Protocol) address allocation and management, DHCP (Dynamic Host Configuration Protocol) function, ARP (Address Resolution Protocol) proxy, and roaming function. The NEF is a network node 30 having a function of notifying other NFs (Network Functions) of capabilities and events. The NSSF is a network node 30 having functions such as selecting a network slice to which a UE connects, determining an allowed NSSAI (Network Slice Selection Assistance Information), determining an NSSAI to be set, and determining an AMF set to which a UE connects. The PCF is a network node 30 having a function of controlling network policies. The AF is a network node 30 having a function of controlling application servers. The NRF is a network node 30 having a function of discovering NF instances that provide services. The UDM is a network node 30 that manages subscriber data and authentication data. The UDM is connected to a UDR (User Data Repository) that stores the data.
[0018] Fig. 2 is a diagram 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 according to the embodiment of the present invention, multiple network slices are constructed.
[0020] The AMF is connected to the UE, RAN, SMF, NSSF, NEF, NRF, UDM, AUSF, PCF, AF, and SEPP (Security Edge Protection Proxy). The AMF, SMF, NSSF, NEF, NRF, UDM, AUSF, PCF, and AF are network nodes 30 that are interconnected via respective service-based interfaces, Namf, Nsmf, Nnssf, Nnef, Nnrf, Nudm, Nausf, Npcf, and Naf.
[0021] The SMF is a network node 30 having functions such as session management, UE IP address allocation and management, DHCP function, ARP proxy, and roaming function. The NEF is a network node 30 having a function of notifying other NFs of capabilities and events. The NSSF is a network node 30 having functions such as selecting a network slice to which a UE connects, determining an allowed NSSAI, determining a configured NSSAI, and determining an AMF set to which a UE connects. The PCF is a network node 30 having a function of controlling network policies. The AF is a network node 30 having a function of controlling application servers. The NRF is a network node 30 having a function of discovering NF instances that provide services. The SEPP is a non-transparent proxy that filters control plane messages between PLMNs (Public Land Mobile Networks). The vSEPP shown in FIG. 2 is a SEPP in the visited network, and the hSEPP is a SEPP in the home network.
[0022] As shown in Figure 2, a UE is in a roaming environment connected to a RAN and an AMF in a Visited PLMN (VPLMN). The VPLMN and a Home PLMN (HPLMN) are connected via a vSEPP and an hSEPP. The UE can communicate with a UDM in the HPLMN via the AMF in the VPLMN, for example.
[0023] Fig. 3 is a diagram illustrating an example of an IMS data channel network. As shown in Fig. 3, the IMS data channel network is configured with a terminal 20 (UE) and multiple network nodes 30 on both the calling and called sides. 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. The network node 30 has, for example, the following functions described in Non-Patent Document 2:
[0024] The IMS-AGW (Access Gateway) is a network node 30 having a gateway function between the UE and the IMS network.
[0025] A P-CSCF (Proxy-Call Session Control Function) is a network node 30 having a proxy function between the UE and the IMS network.
[0026] The S-CSCF (Serving-Call Session Control Function) is a network node 30 having functions related to session control for the UE.
[0027] The I-CSCF (Interrogate-Call Session Control Function) is a connection point on the destination network side between networks (e.g., between the source network side and the destination network side) in the IMS network, and is a network node 30 that has, for example, the function of forwarding a received SIP request to the S-CSCF of its own network.
[0028] An IMS AS (IP Multimedia Subsystem Application Server) is a network node 30 in an IMS network that has functions such as communicating with a DCSF for event notification and receiving data channel control instructions from the DCSF and communicating with a DCMF. The IMS AS also receives a communication termination point registration request from a DCSF (Data Channel Signalling Function), converts the received registration request into a SIP Register, and sends it to a Serving-Call Session Control Function (S-CSCF). The IMS AS also converts a data channel establishment request received from the DCSF into a SIP INVITE and sends it to the S-CSCF.
[0029] The DCSF (Data Channel Signaling Function) is a network node 30 that has functions such as receiving an event report from the IMS-AS and determining whether to allow the provision of a data channel service, managing the bootstrap data channel, and performing HTTP web server functions.
[0030] A Data Channel Media Function (DCMF) is a network node 30 in an IMS network that has functions such as media resource management and forwarding of data channel media traffic. The DCMF processes media between a Data Channel Application Server (DCAS), which is a communication termination point, and a destination termination point based on configuration information received from the DCSF. The DCMF may also be a Multimedia Resource Function (MRF).
[0031] A DCAS (Data Channel Application Server) is a network node 30 having functions such as a communication termination point for media and signaling in the IMS network.
[0032] The HSS (Home Subscriber Server) is a network node 30 having functions such as managing information (subscriber information) of users of network services that operate UEs.
[0033] Furthermore, a network node in the IMS data channel network may be accessible to a network node having, for example, a CAPIF (Common API Framework) authorization function and a CAPIF core function for performing user authentication based on OIDC (Open ID Connect). CAPIF is a 3GPP framework that brings together common functions for providing northbound APIs. The CAPIF authorization function has, for example, a function for accepting an authentication request and issuing an authorization code. The CAPIF core function has, for example, a function for receiving an authorization code and issuing an ID token and an access token. The authorization function may also be called an authentication function.
[0034] (Example 1) Example 1 will be described. Example 1 specifies a procedure for verifying whether a user using a shared terminal and a called user intended by a caller are the same in an IMS data channel network. The calling terminal has a list of user names and telephone numbers of call destinations, and when calling a terminal owned by the called user, the caller uses the user's telephone number. On the other hand, Example 1 assumes a use case in which the caller calls the telephone number of a shared terminal available to multiple users, and the user who receives the call at the called user uses the shared terminal. Here, a network in which a terminal used by the caller (also referred to as a calling user or calling user) is located is referred to as the calling network side, and a network in which a shared terminal used by a called user (also referred to as a called user or called user) is located is referred to as the called network side. Furthermore, a terminal used by the calling user is referred to as a calling terminal, calling terminal, user equipment (UE) on the calling network side, a terminal 20 on the calling network side, etc., and a terminal used by the called user (shared terminal) is referred to as a called terminal, called terminal, UE on the called network side, a terminal 20 on the called network side, etc.
[0035] In the first embodiment, first, a Bootstrap DC (Data Channel) is established between the originating terminal and the DCSF on the originating network side, and between the destination terminal and the DCSF on the originating network side. Next, the Bootstrap DC is used to authenticate the called user and confirm whether the caller is the intended called user. Finally, a communication path is established between the originating terminal and the called terminal. Note that user authentication using OIDC is an example, and other authentication methods may be used. In addition, in the procedures described below, requests, responses, notifications, etc. transmitted and received between network nodes may be referred to as messages or information, for example, as request messages, request information, etc.
[0036] 4 is a diagram showing an example of a first sequence diagram according to an embodiment of the present invention. The processing of each step in FIG. 4 will now be described.
[0037] Step S301: The UE (terminal 20) on the calling network side sends a SIP INVITE to the P-CSCF, which includes a request for authentication and confirmation of the called user and a request for setting up a data channel, described based on the Session Description Protocol (SDP). Figure 5 shows an example of the SDP content in an embodiment of the present invention. In Figure 5, a test UDP port number (52718) is used. The label "label="in-bound authentication of the called user and consent by the calling user" is an identifier requesting user authentication and confirmation. Here, audio and video media are not configured. dcmap:0 corresponds to stream ID=0, indicates support for receiving DC applications from the local network provider, and includes a request for authentication and confirmation of the called user via an SDP offer. dcmap:100 corresponds to stream ID=100, indicates support for receiving DC applications from the remote network provider. For stream IDs, see, for example, Table 6.2.10.1-2 in Non-Patent Document 3. For details on how to write an SDP offer, see, for example, clause 6.2.10 of Non-Patent Document 3 and clause 5.1 of Non-Patent Document 4. In this way, the UE (terminal 20) on the originating network side generates a message including a request for the terminating network to authenticate the terminating user who uses the terminating terminal and for the terminating user to verify the terminating user, and a request for setting up data channels between the UE and the originating network and between the originating network and the terminating terminal, and transmits the generated message to the P-CSCF. Returning to Figure 4, the following description will be given.
[0038] Step S302: The P-CSCF sends the received SIP INVITE to the S-CSCF.
[0039] Step S304: The S-CSCF sends the received SIP INVITE to the IMS AS.
[0040] Step S305: The IMS AS sends an Nhss_ImsSDM_Get request to the HSS. The Nhss_ImsSDM_Get request is a Subscriber Data Management (SDM) request that enables acquisition of information related to an IMS subscriber.
[0041] Step S306: The HSS sends an Nhss_ImsSDM_Get response to the IMS AS.
[0042] Step S307: Based on the response received from the HSS, the IMS AS checks whether the Bootstrap DC configuration in the source network DCSF is permitted for the source terminal.
[0043] Step S308: The IMS AS sends a Nimsas_SessionEventControl_Notify request to the DCSF. Here, the IMS AS includes a called user authentication request in the information related to dcmap:0 (stream ID=100) in the Nimsas_SessionEventControl_Notify request. The Nimsas_SessionEventControl_Notify request includes a request to authenticate the called user using the called terminal in the called network and to verify the called user by the calling user, and a request to set up a data channel between the calling terminal and the calling network, and between the calling network and the called terminal.
[0044] Step S309: The DCSF configures its own device as the Bootstrap DC connection destination for the source terminal and destination terminal (shared terminal). The DCSF also configures a screen for the destination terminal requesting destination user authentication. The DCSF also generates DCMF configuration information including the contents to be configured in the DCMF (four paths: the source terminal and the source network side DCSF (i.e., its own device), the source terminal and the CAPIF authorization function, the destination terminal and the CAPIF authorization function, and the destination terminal and the source network side DCSF (i.e., its own device)). The DCSF also updates the media information (addresses, etc.) in the SDP offer.
[0045] Step S310: The DCSF sends a Nimsas_MediaControl_MediaInstruction request to the IMS AS, which includes DCMF configuration information.
[0046] Step S311: The IMS AS sends an Ndcmf_MRM_Create request to the DCMF, which includes DCMF setting information.
[0047] Step S312: The DCMF sets the received DCMF setting information in its own device.
[0048] Step S313: The DCMF sends an Ndcmf_MRM_Create response to the IMS AS.
[0049] Step S314: The IMS AS sends a Nimsas_MediaControl_MediaInstruction response to the DCSF.
[0050] Step S315: DCSF sends a Nimsas_SessionEventControl_Notify response to the IMS AS.
[0051] Step S316: The IMS AS sends a SIP INVITE to the S-CSCF, where dcmap:0 in the SIP INVITE includes the request for authentication and verification of the called user described in step S301 and information about the DCSF, which is the end of the originating network.
[0052] Step S317: The S-CSCF transmits the received SIP INVITE to the I-CSCF on the destination network side.
[0053] The process on the destination network side subsequent to step S317 will be described with reference to Fig. 6. Fig. 6 is a diagram showing an example of a second sequence diagram according to the embodiment of the present invention.
[0054] Step S318: The I-CSCF sends an Nhss_ImsUECM_Authorize request to the HSS.
[0055] Step S319: The HSS transmits an Nhss_ImsUECM_Authorize response to the I-CSCF. The I-CSCF acquires information for accessing the S-CSCF on the destination network side based on the received Nhss_ImsUECM_Authorize response.
[0056] Step S320: The I-CSCF sends the SIP INVITE received in step S317 to the S-CSCF.
[0057] Step S321: The S-CSCF sends the received SIP INVITE to the IMS AS.
[0058] Step S322: The IMS AS sends an Nhss_ImsSDM_Get request to the HSS.
[0059] Step S323: The HSS sends an Nhss_ImsSDM_Get response to the IMS AS.
[0060] Step S324: Based on the response received from the HSS, the IMS AS checks whether the Bootstrap DC setting in the destination network DCSF is permitted for the destination terminal.
[0061] Step S325: The IMS AS sends a Nimsas_SessionEventControl_Notify request to the DCSF.
[0062] Step S326: The DCSF configures itself as the Bootstrap DC (Data Channel) connection destination for the source terminal and destination terminal (shared terminal). The DCSF also configures a screen for the source terminal indicating that the destination terminal is a shared terminal. The DCSF also generates DCMF configuration information including the contents to be configured in the DCMF (two routes: the source terminal and the destination network side DCSF (i.e., its own device), and the destination terminal and the destination network side DCSF (i.e., its own device)). The DCSF also updates the media information (addresses, etc.) in the SDP offer.
[0063] Step S327: The DCSF sends a Nimsas_MediaControl_MediaInstruction request to the IMS AS. The Nimsas_MediaControl_MediaInstruction request includes DCMF configuration information.
[0064] Step S328: The IMS AS sends an Ndcmf_MRM_Create request to the DCMF, which includes DCMF setting information.
[0065] Step S329: The DCMF sets the received DCMF setting information in its own device.
[0066] Step S330: The DCMF sends an Ndcmf_MRM_Create response to the IMS AS.
[0067] Step S331: The IMS AS sends a Nimsas_MediaControl_MediaInstruction response to the DCSF.
[0068] Step S332: The DCSF sends a Nimsas_SessionEventControl_Notify response to the IMS AS.
[0069] The process on the destination network side following step S332 will be described with reference to Fig. 7. Fig. 7 is a diagram showing an example of a third sequence diagram according to the embodiment of the present invention.
[0070] Step S333: The IMS AS sends a SIP INVITE to the S-CSCF. Here, the SIP INVITE includes, in dcmap:0, a request for establishing a data channel between the originating network and the UE (shared terminal), including information about the DCSF, which is the end of the originating network, in addition to the request for authentication and confirmation of the called user described in step S301. The SIP INVITE further includes, in dcmap:100, a request for establishing a data channel between the terminating network and the UE (shared terminal), including information about the DCSF, which is the end of the destination network.
[0071] Step S334: The S-CSCF sends the received SIP INVITE to the P-CSCF.
[0072] Step S335: The P-CSCF sends the received SIP INVITE to the UE (shared terminal). The SIP INVITE includes a request for authentication and confirmation of the called user, as well as a request for establishing a data channel between the originating network and the UE (shared terminal), including information about the DCSF that is the end of the originating network. The SIP INVITE further includes a request for establishing a data channel between the terminating network and the UE (shared terminal), including information about the DCSF that is the end of the destination network.
[0073] Step S336: The UE (shared terminal) generates a SIP 183 Session Progress based on the received SIP INVITE and sends it to the P-CSCF. The SIP 183 Session Progress contains an SDP answer to the SDP offer in the received SIP INVITE. The SDP answer contains information about the DCSF, which is the end of the destination network, in dcmap:0 (stream ID=0), and information about the DCSF, which is the end of the source network, and a request for authentication and confirmation of the destination user, in dcmap:100 (stream ID=100).
[0074] Step S337: The P-CSCF accesses the PCF (Policy Control Function) and sets a QoS flow for the Bootstrap DC in the 5G system.
[0075] Step S338: The P-CSCF sends the received SIP 183 Session Progress to the S-CSCF.
[0076] Step S339: The S-CSCF sends the received SIP 183 Session Progress to the IMS AS.
[0077] Step S339a: The IMS AS sends a Nimsas_SessionEventControl_Notify request to the DCSF.
[0078] Step S339b: DCSF sends a Nimsas_SessionEventControl_Notify response to the IMS AS.
[0079] Step S340: The IMS AS sends the received SIP 183 Session Progress to the S-CSCF.
[0080] Step S341: The S-CSCF sends the received SIP 183 Session Progress to the I-CSCF.
[0081] The process on the source network side following step S341 will be described with reference to Fig. 8. Fig. 8 is a diagram showing an example of a fourth sequence diagram according to the embodiment of the present invention.
[0082] Step S342: The I-CSCF on the destination network side sends the received SIP 183 Session Progress to the S-CSCF on the source network side.
[0083] Step S343: The S-CSCF sends the received SIP 183 Session Progress to the IMS AS.
[0084] Step S344: The IMS AS sends a Nimsas_SessionEventControl_Notify request to the DCSF.
[0085] Step S345: DCSF sends a Nimsas_SessionEventControl_Notify response to the IMS AS.
[0086] Step S346: The IMS AS sends the received SIP 183 Session Progress to the S-CSCF.
[0087] Step S347: The S-CSCF sends the received SIP 183 Session Progress to the P-CSCF.
[0088] Step S348: The P-CSCF accesses the PCF (Policy Control Function) and sets up a QoS flow for the destination network termination Bootstrap DC in the 5G system.
[0089] Step S349: The P-CSCF sends the received SIP 183 Session Progress to the UE.
[0090] The processing on the source network side and the destination network side subsequent to step S349 will be described with reference to Fig. 9. Fig. 9 is a diagram showing an example of a fifth sequence diagram according to the embodiment of the present invention.
[0091] Step S350: The UE on the source network side sends a PRACK (Provisional response acknowledgement) to the P-CSCF as a response to the SIP 183 Session Progress received in step S349.
[0092] Step S351: The P-CSCF transmits the received PRACK to the S-CSCF.
[0093] Step S352: The S-CSCF sends the received PRACK to the IMS AS.
[0094] Step S353: The IMS AS sends the received PRACK to the S-CSCF.
[0095] Step S354: The S-CSCF transmits the received PRACK to the I-CSCF on the destination network side. The subsequent processing is performed by the network node on the destination network side or the UE (shared terminal).
[0096] Step S355: The I-CSCF sends the received PRACK to the S-CSCF.
[0097] Step S356: The S-CSCF sends the received PRACK to the IMS AS.
[0098] Step S357: The IMS AS sends the received PRACK to the S-CSCF.
[0099] Step S358: The S-CSCF transmits the received PRACK to the P-CSCF.
[0100] Step S359: The P-CSCF transmits the received PRACK to the UE (shared terminal).
[0101] Step S360: The UE (shared terminal) transmits a success response (200 OK) to the P-CSCF in response to the received PRACK.
[0102] Step S361: The P-CSCF sends a success response (200 OK) to the S-CSCF in response to the received PRACK.
[0103] Step S362: The S-CSCF sends a success response (200 OK) to the received PRACK to the IMS AS.
[0104] Step S363: The IMS AS sends a success response (200 OK) to the S-CSCF in response to the received PRACK.
[0105] Step S364: The S-CSCF sends a success response (200 OK) to the I-CSCF in response to the received PRACK.
[0106] Step S365: The I-CSCF sends a success response (200 OK) to the S-CSCF of the originating network in response to the received PRACK. The subsequent processing is performed by the network node or the UE of the originating network.
[0107] Step S366: The S-CSCF sends a success response (200 OK) to the received PRACK to the IMS AS.
[0108] Step S367: The IMS AS sends a success response (200 OK) to the S-CSCF in response to the received PRACK.
[0109] Step S368: The S-CSCF sends a success response (200 OK) to the P-CSCF in response to the received PRACK.
[0110] Step S369: The P-CSCF sends a success response (200 OK) to the UE in response to the received PRACK.
[0111] The processing on the source network side and the destination network side subsequent to step S369 will be described with reference to Fig. 10. Fig. 10 is a diagram showing an example of a sixth sequence diagram according to the embodiment of the present invention.
[0112] Step S370: The UE on the source network side sends UPDATE, which is a method for updating a session in SIP, to the P-CSCF.
[0113] Step S371: The P-CSCF sends the received UPDATE to the S-CSCF.
[0114] Step S372: The S-CSCF sends the received UPDATE to the IMS AS.
[0115] Step S373: The IMS AS sends the received UPDATE to the S-CSCF.
[0116] Step S374: The S-CSCF transmits the received UPDATE to the I-CSCF on the destination network side. The subsequent processing is performed by the network node or UE (shared terminal) on the destination network side.
[0117] Step S375: The I-CSCF sends the received UPDATE to the S-CSCF.
[0118] Step S376: The S-CSCF sends the received UPDATE to the IMS AS.
[0119] Step S377: The IMS AS sends the received UPDATE to the S-CSCF.
[0120] Step S378: The S-CSCF sends the received UPDATE to the P-CSCF.
[0121] Step S379: The P-CSCF transmits the received UPDATE to the UE (shared terminal).
[0122] Step S380: The UE (shared terminal) is configured as a shared terminal, so it does not execute an alert (call the user).
[0123] Step S381: The UE (shared terminal) transmits a success response (200 OK) to the P-CSCF in response to the received UPDATE.
[0124] Step S382: The P-CSCF sends a success response (200 OK) to the S-CSCF in response to the received UPDATE.
[0125] Step S383: The S-CSCF sends a success response (200 OK) to the IMS AS in response to the received UPDATE.
[0126] Step S384: The IMS AS sends a success response (200 OK) to the S-CSCF in response to the received UPDATE.
[0127] Step S385: The S-CSCF sends a success response (200 OK) to the I-CSCF in response to the received UPDATE.
[0128] Step S386: The I-CSCF sends a success response (200 OK) to the S-CSCF of the originating network in response to the received UPDATE. The subsequent processing is performed by the network node or the UE of the originating network.
[0129] Step S387: The S-CSCF sends a success response (200 OK) to the IMS AS in response to the received UPDATE.
[0130] Step S388: The IMS AS sends a success response (200 OK) to the S-CSCF in response to the received UPDATE.
[0131] Step S389: The S-CSCF sends a success response (200 OK) to the P-CSCF in response to the received UPDATE.
[0132] Step S390: The P-CSCF sends a success response (200 OK) to the UE in response to the received UPDATE.
[0133] The processing on the source network side and the destination network side subsequent to step S390 will be described with reference to Fig. 11. Fig. 11 is a diagram showing an example of a seventh sequence diagram according to the embodiment of the present invention.
[0134] Step S400: The UE (shared terminal) on the destination network side automatically responds to the SIP INVITE received in step S335 of Fig. 7 after receiving the UPDATE in step S379 of Fig. 10. The subsequent processing is performed by the network node or the UE (shared terminal) on the destination network side.
[0135] Step S401: The UE (shared terminal) sends a success response (SIP 200 OK) to the P-CSCF as an automatic response.
[0136] Step S402: The P-CSCF sends the received success response (SIP 200 OK) to the S-CSCF.
[0137] Step S403: The S-CSCF sends the received success response (SIP 200 OK) to the IMS AS.
[0138] Step S404: The IMS AS sends the received successful response (SIP 200 OK) to the S-CSCF.
[0139] Step S405: The S-CSCF sends the received success response (SIP 200 OK) to the I-CSCF.
[0140] Step S406: The I-CSCF sends a successful response (200 OK) to the S-CSCF of the originating network in response to the SIP INVITE. The subsequent processing is performed by the network node or the UE of the originating network.
[0141] Step S407: The S-CSCF sends the received success response (SIP 200 OK) to the IMS AS.
[0142] Step S408: The IMS AS sends the received successful response (SIP 200 OK) to the S-CSCF.
[0143] Step S409: The S-CSCF sends the received success response (SIP 200 OK) to the P-CSCF.
[0144] Step S410: The P-CSCF sends the received success response (SIP 200 OK) to the UE.
[0145] Step S411: The UE sends an acknowledgement (ACK) to the P-CSCF in response to the received success response (SIP 200 OK).
[0146] Step S412: The P-CSCF sends an acknowledgement (ACK) of the reception to the S-CSCF.
[0147] Step S413: The S-CSCF sends an acknowledgement (ACK) of the received message to the IMS AS.
[0148] Step S414: The IMS AS sends an acknowledgement (ACK) of the reception to the S-CSCF.
[0149] Step S415: The S-CSCF sends the received acknowledgement (ACK) to the I-CSCF on the destination network side. The subsequent processing is performed by the network node or the UE (shared terminal) on the destination network side.
[0150] Step S416: The I-CSCF sends an acknowledgement (ACK) of the reception to the S-CSCF.
[0151] Step S417: The S-CSCF sends an acknowledgement (ACK) of the received message to the IMS AS.
[0152] Step S418: The IMS AS sends an acknowledgement (ACK) of the reception to the S-CSCF.
[0153] Step S419: The S-CSCF sends an acknowledgement (ACK) of the reception to the P-CSCF.
[0154] Step S420: The P-CSCF sends an acknowledgement (ACK) of the received message to the UE (shared terminal).
[0155] The processing on the source network side and the destination network side subsequent to step S420 will be described with reference to Fig. 12. Fig. 12 is a diagram showing an example of an eighth sequence diagram according to an embodiment of the present invention. The subsequent processing is performed by a network node on the source network side, a UE on the source network side, or a UE (shared terminal) on the destination network side.
[0156] Step S500: The UE sends an HTTP GET request to the DCMF requesting screen information.
[0157] Step S501: The DCMF converts the host name so that the UE can download a caller-specific screen.
[0158] Step S502: The DCMF sends the received HTTP GET request to the DCSF.
[0159] Step S503: DCSF generates screen information for displaying the callee authentication wait state.
[0160] Step S504: The DCSF sends an HTTP GET response to the DCMF in response to the received HTTP GET request. The HTTP GET response includes screen information related to the display waiting for authentication of the called user.
[0161] Step S505: The DCMF transmits the received HTTP GET response to the UE. After that, the UE transmits an HTTP GET request to the DCMF to request screen information as necessary.
[0162] Step S506: The UE (shared terminal) on the destination network side transmits an HTTP GET request to the DCMF on the source network side to request screen information for user authentication.
[0163] Step S507: The DCMF converts the host name so that the UE (shared terminal) on the destination network side can download a screen specific to the caller.
[0164] Step S508: The DCMF sends the received HTTP GET request to the DCSF.
[0165] Step S509: DCSF operates as an RP (Relaying Party) during user authentication using OIDC (Open ID Connect).
[0166] Step S510: The DCSF sends an HTTP GET response to the DCMF in response to the received HTTP GET request. The HTTP GET response includes an OIDC authentication request for requesting user authentication using OIDC.
[0167] Step S511: The DCMF transmits the received HTTP GET response to the UE (shared terminal) on the destination network side.
[0168] Step S512: The browser of the UE (shared terminal) on the destination network side transfers the OIDC authentication request.
[0169] The processing on the source network side and the destination network side subsequent to step S505 will be described with reference to Fig. 13. Fig. 13 is a diagram showing an example of a ninth sequence diagram according to an embodiment of the present invention. The subsequent processing is performed by a network node on the source network side or a UE (shared terminal) on the destination network side.
[0170] Step S520: The UE (shared terminal) on the destination network side sends an HTTP request to the DCMF on the source network side to request user authentication.
[0171] Step S521: The DCMF transmits the received HTTP request to a network node that provides a CAPIF authorization function (hereinafter referred to as a CAPIF authorization function).
[0172] Step S522: The CAPIF authorization function sends an HTTP response to the DCMF, which is a response to the received HTTP request.
[0173] Step S523: The DCMF transmits the received HTTP response to the UE (shared terminal).
[0174] Step S524: The UE (shared terminal) displays an OIDC authentication screen based on the received HTTP response and accepts the user's input of authentication information. Here, it is assumed that the called user is a subscriber of the originating network and can be authenticated by the CAPIF authorization function of the originating network.
[0175] Step S525: The UE (shared terminal) sends an HTTP request to the DCMF in response to the user authentication request. The HTTP request includes the authentication information entered by the user in response to the OIDC authentication request.
[0176] Step S526: The DCMF sends the received HTTP request to the CAPIF authorization function.
[0177] Step S527: The CAPIF authorization function sends an HTTP response to the DCMF in response to the received HTTP request. The HTTP response includes an authorization code based on the result of user authentication.
[0178] Step S528: The DCMF transmits the received HTTP response to the UE (shared terminal).
[0179] Step S529: The browser of the UE (shared terminal) transfers the received authorization code.
[0180] Step S530: The UE (shared terminal) sends an HTTP request to the DCMF, which includes the authorization code received as the OIDC authentication response.
[0181] Step S531: The DCMF sends the received HTTP request to the DCSF.
[0182] Step S532: The DCSF sends an HTTP response to the DCMF in response to the received HTTP request.
[0183] Step S533: The DCMF transmits the received HTTP response to the UE (shared terminal).
[0184] Step S534: The UE (shared terminal) performs polling as needed to request an update of the screen display, etc.
[0185] The process on the source network side subsequent to step S534 will be described with reference to Fig. 14. Fig. 14 is a diagram showing an example of a tenth sequence diagram according to an embodiment of the present invention. The subsequent process is performed by a network node or UE on the source network side.
[0186] Step S550: The DCSF sends an OIDC token request to a network node having a CAPIF core function (hereinafter referred to as the CAPIF core function), requesting an OIDC token. The OIDC token request includes the authorization code that the DCSF received in step S531 of FIG. 13 .
[0187] Step S551: The CAPIF core function sends an OIDC token response to the DCSF in response to the received OIDC token request. The OIDC token response includes an ID token and an access token.
[0188] Step S552: DCSF completes the execution of called user authentication (verification of the called user's identity) by verifying the ID token. In the subsequent processing, it is verified whether the user using the shared terminal is the called user intended by the calling user. In this embodiment, a procedure based on OIDC CIBA (Client Initiated Backchannel Authentication) will be described as an example.
[0189] Step S553: The DCSF sends an OIDC authentication request to the CAPIF authorization function. The OIDC authentication request includes an identifier and information about the called user.
[0190] Step S554: The CAPIF authorization function sends an OIDC authentication response to the DCSF in response to the received OIDC authentication request. The OIDC authentication response includes auth_req_id (authentication request ID).
[0191] Step S555: The CAPIF authorization function sends an HTTP request to the DCSF, which includes an OIDC authentication request containing an identifier and information about the called user.
[0192] Step S556: The DCSF sends an HTTP response to the CAPIF authorization function as a response to the received HTTP request.
[0193] Step S557: The DCSF holds the information for performing OIDC CIBA authentication, and the OIDC CIBA authentication is performed when the calling terminal polls it. The DCSF also polls the CAPIF authorization function.
[0194] Step S558: The UE sends an HTTP GET request to the DCMF.
[0195] Step S559: The DCMF sends an HTTP GET request to the DCSF.
[0196] Step S560: The DCSF sends an HTTP GET response to the DCMF in response to the received HTTP GET request, the HTTP GET response including an identifier and information about the called user.
[0197] Step S561: The DCMF sends an HTTP GET response to the UE in response to the received HTTP GET request. The HTTP GET response includes an OIDC authentication request. The OIDC authentication request includes an identifier and information about the called user.
[0198] Step S562: The UE (originating terminal) on the originating network side displays an OIDC authentication screen based on the received HTTP GET response and accepts input of authentication information by the originating user. Based on the information about the destination user displayed on the screen, the originating user checks whether the user using the shared terminal is the intended destination user, and inputs the confirmation result as authentication information.
[0199] Step S563: The UE sends an HTTP GET request to the DCMF. The HTTP GET request includes an OIDC authentication response that is a response to the OIDC authentication request included in the HTTP GET response received in step S561.
[0200] Step S564: The DCMF sends the received HTTP request to the CAPIF authorization function.
[0201] Step S565: The CAPIF authorization function sends an HTTP response to the DCMF as a response to the received HTTP request.
[0202] Step S566: The DCMF sends an HTTP response to the UE as a response to the received HTTP request.
[0203] Step S567: The DCSF sends an OIDC token request to the CAPIF core function. The OIDC token request includes the auth_req_id (authentication request ID) received in step S554.
[0204] Step S568: The CAPIF core function sends an OIDC request to the CAPIF authorization function. The OIDC request includes auth_req_id (authentication request ID).
[0205] Step S569: The CAPIF authorization function sends an OIDC response to the CAPIF core function, which includes the authentication result information generated by the CAPIF authorization function after step S564.
[0206] Step S570: The CAPIF core function sends an OIDC token response to the DCSF in response to the received OIDC token request. The OIDC token response includes an ID token and an access token.
[0207] Step S571: The DCSF checks the ID token to confirm whether the user using the shared terminal is the same as the called user intended by the calling user. This check is called calling user consent check.
[0208] The processing on the source network side and the destination network side subsequent to step S571 will be described with reference to Fig. 15. Fig. 15 is a diagram showing an example of an eleventh sequence diagram according to an embodiment of the present invention. The subsequent processing is performed by a network node on the source network side, a UE on the source network side, a network node on the destination network side, or a UE (shared terminal) on the destination network side.
[0209] Step S600: The UE (shared terminal) on the destination network side sends an HTTP request to the DCMF on the source network side.
[0210] Step S601: The DCMF on the originating network side sends the received HTTP request to the DCSF on the originating network side.
[0211] Step S602: The DCSF of the originating network sends an HTTP response to the DCMF of the originating network in response to the received HTTP request, which includes information indicating that the called user authentication and the calling user consent confirmation have been completed.
[0212] Step S603: The DCMF on the source network side sends the received HTTP response to the UE (shared terminal) on the destination network side, which includes information indicating that the destination user authentication and the destination user consent confirmation have been completed.
[0213] Step S604: The UE (shared terminal) on the destination network side sends an HTTP request to the DCMF on the source network side. The HTTP request includes a message requesting an Application DC application, which includes configuration information for establishing communication between the UE on the source network side and the UE on the destination network side.
[0214] Step S605: The DCMF on the source network side sends the received HTTP request to the DCSF on the source network side.
[0215] Step S606: The DCSF of the source network sends an HTTP response to the DCMF of the source network in response to the received HTTP request, which includes an Application DC application including configuration information for establishing communication between the UE of the source network and the UE of the destination network.
[0216] Step S607: The DCMF on the source network side sends the received HTTP response to the UE (shared terminal) on the destination network side. The HTTP response includes an application for Application DC, which includes setting information for establishing communication between the UE on the source network side and the UE on the destination network side.
[0217] Step S608: The UE on the source network side sends an HTTP GET request to the DCMF on the source network side.
[0218] Step S609: The DCMF on the source network side sends the received HTTP GET request to the DCSF on the source network side.
[0219] Step S610: The DCSF of the originating network sends an HTTP GET response to the DCMF of the originating network in response to the received HTTP GET request, which includes information indicating that the called user authentication and the calling user consent confirmation have been completed.
[0220] Step S611: The DCMF of the originating network sends the received HTTP GET response to the UE of the originating network, which includes information indicating that the called user authentication and the calling user consent confirmation have been completed.
[0221] Step S612: The UE on the source network side sends an HTTP request to the DCMF on the source network side, which includes a message requesting an Application DC, including configuration information for establishing communication between the UE on the source network and the UE on the destination network.
[0222] Step S613: The DCMF on the source network side transmits the received HTTP request to the DCSF on the source network side.
[0223] Step S614: The DCSF of the source network sends an HTTP response to the DCMF of the source network in response to the received HTTP request, which includes an Application DC application including configuration information for establishing communication between the UE of the source network and the UE of the destination network.
[0224] Step S615: The DCMF of the source network sends the received HTTP response to the UE of the source network, which includes an application for Application DC, including configuration information for establishing communication between the UE of the source network and the UE of the destination network.
[0225] Step S616: The UE on the source network side sends an HTTP GET request to the DCMF on the destination network side.
[0226] Step S617: The DCMF on the destination network side converts the host name so that the UE on the source network side can download a screen specific to the destination party.
[0227] Step S618: The DCMF on the destination network side transmits the received HTTP GET request to the DCSF on the destination network side.
[0228] Step S619: The DCSF on the destination network side generates an HTTP GET response including information indicating that the terminal on the destination network side is a shared terminal.
[0229] Step S620: The DCSF on the destination network side transmits the HTTP GET response generated in step S619 to the DCMF on the destination network side as a response to the received HTTP GET request.
[0230] Step S621: The DCMF on the destination network side sends the received HTTP GET response to the UE on the source network side.
[0231] Step S622: The UE on the source network side reconfirms that the destination side is a shared terminal based on the received HTTP GET response.
[0232] Step S623: The source network UE sends a SIP reINVITE to the P-CSCF to establish a communication path between the source network UE and the destination network UE. The SDP offer in the SIP reINVITE may include a configuration for Application DC media or audio / video media. The source network UE establishes a communication path between the source network UE and the destination network UE based on the configuration information received in step S621 and the SIP reINVITE it sent. The destination network UE receives the SIP reINVITE sent by the source network UE. The destination network UE establishes a communication path between the source network UE and the destination network UE based on the configuration information received in step S607 and the SIP reINVITE it received.
[0233] According to the above-mentioned embodiment, in an IMS data channel network, it is possible to define a procedure for confirming whether a user using a shared terminal is the same as the called user intended by the calling user. Also, in the above-mentioned embodiment, it is possible to perform user authentication of the called user using the shared terminal.
[0234] (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.
[0235] <Base Station 10 and Network Node 30> Fig. 16 is a diagram showing an example of the functional configuration of the base station 10 and the network node 30. As shown in Fig. 16, 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. 16 is merely an example. As long as the operations according to the embodiment of the present invention can be performed, the names of the functional divisions and functional units may be any. Note that the network node 30 may have the same functional configuration as the base station 10. Furthermore, a network node 30 having multiple different functions in the system architecture may be composed of multiple network nodes 30 separated by function.
[0236] The transmitter 110 includes a function of generating a signal to be transmitted to the terminal 20 or another network node 30 and transmitting the signal by wire or wirelessly. The receiver 120 includes a function of receiving various signals transmitted from the terminal 20 or another network node 30 and acquiring, for example, information of a higher layer from the received signal. A communication unit including the transmitter 110 and the receiver 120 may be configured.
[0237] 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 from the storage device as needed. The content of the setting information is, for example, information related to a communication path in the IMS data channel network.
[0238] As described in the embodiment, the control unit 140 performs processing related to the IMS data channel 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.
[0239] <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. As long as the operations related to the embodiment of the present invention can be performed, the names of the functional divisions and functional units may be any. In addition, a communication device that becomes a resource holder 20 may have the same functional configuration as the terminal 20.
[0240] The transmitter 210 creates a transmission signal from transmission data and transmits the transmission signal wirelessly. The receiver 220 receives various signals wirelessly and acquires higher layer signals from the received physical layer signals. The receiver 220 also has a function of receiving control signals, reference signals, etc. transmitted from the network node 30. A communication unit including the transmitter 210 and the receiver 220 may be configured.
[0241] The setting unit 230 stores various pieces of setting information received from the network node 30 by the receiving unit 220 in a storage device and reads them out from the storage device as needed. The setting unit 230 also stores setting information that is set in advance. The content of the setting information is, for example, information related to communication paths in the IMS data channel network.
[0242] As described in the embodiment, the control unit 240 performs processing related to the communication path in the IMS data channel network. The function unit related to signal transmission in the control unit 240 may be included in the transmitting unit 210, and the function unit related to signal reception in the control unit 240 may be included in the receiving unit 220.
[0243] (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.
[0244] 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.
[0245] For example, the base station 10, the network node 30, the terminal 20, etc. according to an embodiment of the present disclosure may function as a computer that performs processing of the wireless communication method of the present disclosure. Fig. 18 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.
[0246] 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.
[0247] 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.
[0248] 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.
[0249] 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. 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.
[0250] 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.
[0251] 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.
[0252] 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.
[0253] 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).
[0254] 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.
[0255] 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.
[0256] Fig. 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.
[0257] 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.
[0258] 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).
[0259] 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.
[0260] 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.
[0261] 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.
[0262] 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.
[0263] 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.
[0264] The communication module 2013 may transmit at least one of signals from the above-mentioned various sensors 2021-2028 input to the electronic control unit 2010, information obtained based on the signals, and information based on input from the outside (user) obtained via the information service unit 2012 to an external device via wireless communication. The electronic control unit 2010, the various sensors 2021-2028, the information service unit 2012, etc. may be referred to as input units that accept input. For example, the PUSCH transmitted by the communication module 2013 may include information based on the above-mentioned input.
[0265] 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.
[0266] (Summary of embodiment) As described above, according to the embodiment of the present invention, there is provided a terminal having a control unit that generates a message including a request to authenticate a called user who uses a called terminal in a called network and to confirm the called user by a calling user, and a request to set up data channels between its own terminal and the calling network, and between the calling network and the called terminal, a transmitting unit that transmits the message, and a receiving unit that receives information about the called user, wherein the transmitting unit transmits information indicating that the calling user has confirmed the called user based on the information about the called user, the receiving unit receives completion information indicating that the authentication and the confirmation have been completed, and the control unit establishes a communication path between its own terminal and the called terminal after receiving the completion information.
[0267] With the above configuration, it is possible to define a procedure for confirming whether a user using a shared terminal is the same as the called user intended by the calling user in the IMS data channel network.
[0268] The communication path may be established based on the setting information and the message requesting establishment of the communication path, which is sent to the called terminal. With this configuration, it is possible to define a procedure for confirming whether a user using a shared terminal and a called user intended by a calling user are the same in an IMS data channel network.
[0269] Furthermore, according to an embodiment of the present invention, there is provided a network node comprising: a receiving unit that receives from an originating terminal via an IMS (IP Multimedia Subsystem) AS (Application Server) a message including a request to authenticate a called user using a called terminal in a called network and to verify the called user by the calling user, and a request to set up data channels between its own terminal and the calling network, and between the calling network and the called terminal; a control unit that generates route information that determines routes between an authentication function that performs the authentication and the calling terminal, between its own device and the calling terminal, between the authentication function and the called terminal, and between its own device and the called terminal; and a transmitting unit that transmits the route information to the IMS AS and transmits a message requesting execution of the authentication to the authentication function via the called terminal, wherein the receiving unit receives information indicating that the called user has been authenticated and information indicating that the calling user has verified the called user, and the transmitting unit transmits completion information indicating that the authentication and the verification have been completed to the calling terminal and the called terminal.
[0270] With the above configuration, it is possible to define a procedure for confirming whether a user using a shared terminal is the same as the called user intended by the calling user in the IMS data channel network.
[0271] The receiving unit may, after transmitting the completion information, receive from the calling terminal and the called terminal messages requesting setting information for establishing a communication path between the calling terminal and the called terminal, and the transmitting unit may transmit the setting information to the calling terminal and the called terminal. With this configuration, it is possible to define a procedure for confirming whether a user using a shared terminal and a called user intended by the calling user are the same in an IMS data channel network.
[0272] Furthermore, according to an embodiment of the present invention, there is provided a terminal comprising: a receiving unit that receives a message including a request to perform authentication of a called user using the terminal in a called network and a request to set up a data channel between the calling network and the terminal; and a transmitting unit that transmits authentication information used in authenticating the called user, wherein the receiving unit receives completion information indicating that the authentication of the called user and confirmation of the called user by the calling user using the calling terminal have been completed, and a control unit that establishes a communication path between the terminal and the calling terminal after receiving the completion information.
[0273] With the above configuration, it is possible to define a procedure for confirming whether a user using a shared terminal is the same as the called user intended by the calling user in the IMS data channel network.
[0274] The communication path may be established based on the setting information and the message sent by the calling terminal requesting establishment of the communication path. With this configuration, it is possible to define a procedure for confirming whether a user using a shared terminal and a called user intended by the calling user are the same in an IMS data channel network.
[0275] (Supplementary Notes on the Embodiments) Although the embodiments of the present invention have been described above, the disclosed invention is not limited to such embodiments, and those skilled in the art will understand various modifications, alterations, alternatives, and substitutions. While specific numerical examples have been used to facilitate understanding of the invention, unless otherwise specified, these numerical values are merely examples, and any appropriate values may be used. The division of items in the above description is not essential to the present invention; matters described in two or more items may be used in combination as needed, and matters described in one item may apply to matters described in another item (as long as there is no contradiction). Boundaries between functional units or processing units in functional block diagrams do not necessarily correspond to boundaries between physical components. The operations of multiple functional units may be performed by a single physical component, or the operations of a single functional unit may be performed by multiple physical components. The order of processing steps described in the embodiments may be reversed as long as there is no contradiction. For convenience of processing description, the base station 10 and terminal 20 have been described using functional block diagrams, but such devices may be realized by hardware, software, or a combination thereof. The software operated by the processor of the base station 10 in accordance with an embodiment of the present invention and the software operated by the processor of the terminal 20 in accordance with an embodiment of the present invention may each be stored in random access memory (RAM), flash memory, read-only memory (ROM), EPROM, EEPROM, register, hard disk (HDD), removable disk, CD-ROM, database, server, or any other suitable storage medium.
[0276] 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.
[0277] 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).
[0278] 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.
[0279] In this specification, a specific operation described as being performed by the base station 10 may be performed by its upper node in some cases. In a network consisting of one or more network nodes having the base station 10, it is clear that various operations performed for communication with the terminal 20 may be performed by at least one of the base station 10 and another network node other than the base station 10 (such as, but not limited to, an MME or an S-GW). Although the above example illustrates a case where there is one other network node other than the base station 10, the other network node may be a combination of multiple other network nodes (such as an MME and an S-GW).
[0280] 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.
[0281] 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.
[0282] 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).
[0283] 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.
[0284] 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.
[0285] 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.
[0286] 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.
[0287] As used in this disclosure, the terms "system" and "network" are used interchangeably.
[0288] 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.
[0289] 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.
[0290] 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.
[0291] 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.
[0292] 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.
[0293] In this disclosure, the terms "Mobile Station (MS)," "user terminal," "User Equipment (UE)," "terminal," and the like may be used interchangeably.
[0294] 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.
[0295] At least one of the base station and the mobile station may be referred to as a transmitting device, a receiving device, a communication device, etc. At least one of the base station and the mobile station may be a device mounted on a mobile object, the mobile object itself, etc. The mobile object refers to a movable object, and may move at any speed. Naturally, this also includes cases where the mobile object is stationary. Examples of the mobile object include, but are not limited to, vehicles, transport vehicles, automobiles, motorcycles, bicycles, connected cars, excavators, bulldozers, wheel loaders, dump trucks, forklifts, trains, buses, handcars, rickshaws, ships and other watercraft, airplanes, rockets, satellites, drones (registered trademark), multicopters, quadcopters, balloons, and objects mounted thereon. The mobile object may also be a mobile object that moves autonomously based on an operational command. It may be a vehicle (e.g., a car, an airplane, etc.), an unmanned mobile object (e.g., a drone, an autonomous vehicle, etc.), or a robot (manned or unmanned). At least one of the base station and the mobile station may be a device that does not necessarily move during communication operations. For example, at least one of the base station and the mobile station may be an IoT (Internet of Things) device such as a sensor.
[0296] 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.
[0297] 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.
[0298] 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.
[0299] 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.
[0300] The reference signal may be abbreviated as RS (Reference Signal) or may be called a pilot depending on the applicable standard.
[0301] 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."
[0302] 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.
[0303] The "means" in the configuration of each of the above devices may be replaced with "part," "circuit," "device," etc.
[0304] 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.
[0305] 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.
[0306] 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."
[0307] 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).
[0308] 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.
[0309] 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 terminal having: a control unit that generates a message including a request to authenticate a called user using a called terminal in a called network and to confirm the called user by the calling user, and a request to set up a data channel between the terminal itself and the calling network, and between the calling network and the called terminal; a transmitting unit that transmits the message; and a receiving unit that receives information regarding the called user, wherein the transmitting unit transmits information indicating that the calling user has confirmed the called user based on the information regarding the called user, the receiving unit receives completion information indicating that the authentication and confirmation have been completed, and the control unit establishes a communication path between the terminal itself and the called terminal after receiving the completion information.
2. The terminal according to claim 1, wherein after receiving the completion information, the transmitting unit transmits a message requesting setting information for establishing the communication path, and the control unit establishes the communication path based on the setting information and a message requesting establishment of the communication path to be sent to the receiving terminal.
3. A network node comprising: a receiving unit that receives a message from a calling terminal via an IMS (IP Multimedia Subsystem) AS (Application Server) including a request to authenticate a called user using a called terminal in a called network and to confirm the called user by the calling user, and a request to set up data channels between the calling terminal and the calling network, and between the calling network and the called terminal; a control unit that generates route information that determines routes between an authentication function that performs the authentication and the calling terminal, between the device itself and the calling terminal, between the authentication function and the called terminal, and between the device itself and the called terminal; and a transmitting unit that transmits the route information to the IMS AS and transmits a message requesting the execution of the authentication to the authentication function via the called terminal, wherein the receiving unit receives information indicating that the called user has been authenticated and information indicating that the calling user has confirmed the called user, and the transmitting unit transmits completion information indicating that the authentication and the confirmation have been completed to the calling terminal and the called terminal.
4. A network node as described in claim 3, wherein after transmitting the completion information, the receiving unit receives messages from the calling terminal and the called terminal requesting setting information for the calling terminal to establish a communication path between the calling terminal and the called terminal, and the transmitting unit transmits the setting information to the calling terminal and the called terminal.
5. A terminal having a receiving unit that receives a message including a request to perform authentication of a called user using the terminal in a called network and a request to set up a data channel between the calling network and the terminal, and a transmitting unit that transmits authentication information used in authenticating the called user, wherein the receiving unit receives completion information indicating that the authentication of the called user and confirmation of the called user by the calling user using the calling terminal have been completed, and a control unit that establishes a communication path between the terminal and the calling terminal after receiving the completion information.
6. The terminal according to claim 5, wherein after receiving the completion information, the transmitting unit transmits a message requesting setting information for establishing the communication path, and the control unit establishes the communication path based on the setting information and a message requesting establishment of the communication path transmitted by the originating terminal.
Citation Information
Patent Citations
Communication network system and its communication terminal
JP2002027549A
Connection control apparatus and connection control method
JP2010119048A
Cited By
Method and apparatus for supporting avatar call in wireless communication system
US20250141942A1
