Terminal, network node, and communication method
The method allows IMS data channel networks to establish communication paths and data channels by configuring data channels between the terminal and originating network, overcoming destination network non-support, and enabling voice communication.
Patent Information
- Application Number
- PCT/JP2023/020548
- Authority / Receiving Office
- WO · WO
- Patent Type
- Applications
- Current Assignee / Owner
- Filing Date
- 2023-06-01
- Publication Date
- 2024-12-05
AI Technical Summary
In IMS data channel networks, when the destination network does not support data channels, existing specifications prevent the setup of communication paths and data channels between the originating network and destination terminal, and between the originating terminal and originating network.
A method where a terminal requests data channel setting from a network node, receives a response indicating non-support, and configures a data channel between the terminal and the originating network, and sets up a voice communication channel, enabling communication paths and data channels despite non-support from the destination network.
Enables the setup of communication paths and data channels between the originating network and destination terminal, and between the originating terminal and originating network, even when the destination network does not support data channels, facilitating voice communication.
Smart Images

Figure JP2023020548_05122024_PF_FP_ABST
Abstract
Description
Terminal, network node, and communication method
[0001] The present invention relates to a terminal, a network node, and a communication method in a communication system.
[0002] 3GPP (registered trademark) (3rd Generation Partnership Project) 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 RFC88643GPP TS 23.218 V17.0.0 (2022-03)
[0006] When an IMS data channel network is introduced, it is necessary to consider coexistence with networks and terminals that do not support the data channel function. In the existing specifications, when a destination network does not support the data channel in an IMS data channel network, it is not possible to set up a communication path between the source network and the destination terminal, or to set up a data channel between the source terminal and the source network.
[0007] The present invention has been made in view of the above points, and aims to enable an operation of setting up a communication path between a source network and a destination terminal and setting up a data channel between the source terminal and the source network in an IMS data channel network when the destination network does not support a data channel.
[0008] According to the disclosed technology, there is provided a terminal having a transmitting unit that transmits a request to a first network node to execute data channel setup, and a receiving unit that receives from the first network node a response that the data channel setup is not possible, wherein the transmitting unit transmits to the first network node a request to execute data channel setup between the terminal itself and a source network and voice communication path setup between the source network and the destination terminal, and the receiving unit receives from the first network node a response that a data channel setup is possible between the terminal itself and the source network, and further has a control unit that executes data channel setup between the terminal itself and the source network.
[0009] According to the disclosed technology, in an IMS data channel network, when the destination network does not support data channels, it is possible to set up a communication path between the source network and the destination terminal and to set up a data channel between the source terminal and the source network.
[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 a first SDP 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 sixth sequence diagram in an embodiment of the present invention. FIG. 6 is a diagram showing an example of a seventh sequence diagram in an embodiment of the present invention. FIG. 7 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 be a Multimedia Resource Function (MRF), or the DCMF and MRF may exist separately.
[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] In the current specifications of the IMS data channel network, if the destination network does not support the data channel function, the following operation is performed.
[0034] First, the terminal 20 originating from the IMS data channel network sets up a data channel with a line including "m=" in the SDP (Session Description Protocol) and sends a SIP INVITE. The destination network that receives the SIP INVITE responds with SIP 488 (Not Acceptable Here) because it cannot set up a data channel.
[0035] Next, the terminal 20 sets audio (or video) in the line including "m=" in the SDP and sends a SIP INVITE, after which audio (or video) communication is established between the calling terminal and the called terminal.
[0036] In other words, under the existing specifications, if the destination network does not support data channels, not only is one of the important functions of the IMS data channel network, "the operation of setting up a data channel between the originating network and the destination terminal, and the operation of setting up a data channel between the originating terminal and the originating network," impossible, but also a similar function, "the operation of setting up a communication path between the originating network and the destination terminal, and the operation of setting up a data channel between the originating terminal and the originating network," cannot be performed.
[0037] (First Embodiment) A first embodiment will be described. In the first embodiment, when a destination network does not support a data channel in an IMS data channel network, an operation of setting up a communication path between a source network and a destination terminal and setting up a data channel between the source terminal and the source network will be described. Here, a terminal originating from a data channel network is referred to as a source terminal, a source terminal, a UE (User Equipment) on the source network side, or a terminal 20 on the source network side, and a terminal on the destination side is referred to as a destination terminal, a destination terminal, a UE on the destination network side, or a terminal 20 on the destination network side. 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. A path between a source terminal and a source network may be referred to as a communication path.
[0038] 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.
[0039] Step S301: The UE (terminal 20) on the originating network side sends a SIP INVITE to the P-CSCF, which includes a Call ID value (e.g., 123) and a request for setting up a data channel, described based on the SDP (Session Description Protocol).
[0040] FIG. 5 is a diagram showing an example of the contents of the first SDP in an embodiment of the present invention. In FIG. 5, a test UDP port number (52718) is used. Here, audio and video media are not configured. dcmap:0 corresponds to stream ID=0 and indicates that data channel (DC) application reception from the local network provider is supported. For details about stream IDs, see, for example, Table 6.2.10.1-2 in Non-Patent Document 3. For details about how to write an SDP offer, see, for example, Clause 6.2.10 in Non-Patent Document 3 and Clause 5.1 in Non-Patent Document 4. In this way, the UE (terminal 20) on the originating network side generates a message including a request to set up a data channel between itself and the originating network, and between the originating network and the terminating terminal, and transmits the generated message to the P-CSCF. Returning to FIG. 4, the following explanation is given.
[0041] Step S302: The P-CSCF sends the received SIP INVITE to the S-CSCF.
[0042] Step S303: The S-CSCF sends the received SIP INVITE to the IMS AS.
[0043] Step S304: 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.
[0044] Step S305: The HSS sends an Nhss_ImsSDM_Get response to the IMS AS.
[0045] Step S306: Based on the response received from the HSS, the IMS AS checks whether the originating terminal is allowed to establish a bootstrap data channel (Bootstrap DC) in the originating network DCSF.
[0046] Step S307: The IMS AS sends a Nimsas_SessionEventControl_Notify request to the DCSF, which includes a request to set up a data channel between the originating terminal and the originating network, and between the originating network and the terminating terminal.
[0047] Step S308: The DCSF configures the DCSF for the source terminal and the destination terminal. The DCSF also generates configuration information to be configured in the DCMF (including the route from the source terminal to the DCSF and the route from the destination terminal to the DCSF). The DCSF also updates the media information (addresses, etc.) in the SDP offer.
[0048] Step S309: The DCSF sends a Nimsas_MediaControl_MediaInstruction request to the IMS AS, which includes the setting information to be set in the DCMF.
[0049] Step S310: The IMS AS sends an Ndcmf_MRM_Create request to the DCMF. The Ndcmf_MRM_Create request includes setting information to be set in the DCMF.
[0050] Step S311: The DCMF sets the received setting information in its own device.
[0051] Step S312: The DCMF sends an Ndcmf_MRM_Create response to the IMS AS.
[0052] Step S313: The IMS AS sends a Nimsas_MediaControl_MediaInstruction response to the DCSF.
[0053] Step S314: The DCSF sends a Nimsas_SessionEventControl_Notify response to the IMS AS.
[0054] Step S315: The IMS AS sends a SIP INVITE to the S-CSCF, where the SIP INVITE includes a Call ID value (e.g., 123), information indicating a request to set up a data channel, and information about the DCSF, which is the originating network termination.
[0055] Step S316: The S-CSCF sends the received SIP INVITE to the I-CSCF on the destination network side.
[0056] The process on the destination network side following step S316 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.
[0057] Step S317: The I-CSCF sends an Nhss_ImsUECM_Authorize request to the HSS.
[0058] Step S318: The HSS sends an Nhss_ImsUECM_Authorize response to the I-CSCF, which then acquires information for accessing the S-CSCF on the destination network side based on the response.
[0059] Step S319: The I-CSCF sends the SIP INVITE received in step S316 to the S-CSCF. The SIP INVITE includes the Call ID value (123), information indicating a request to set up a data channel, and information about the DCSF, which is the originating network termination.
[0060] Step S320: The S-CSCF does not accept (cannot set) the data channel, and therefore sends SIP 488 to the I-CSCF.
[0061] The process on the source network side following step S320 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.
[0062] Step S331: The I-CSCF sends the received SIP INVITE (Call ID=123) to the S-CSCF.
[0063] Step S332: The S-CSCF sends the received SIP INVITE (Call ID=123) to the IMS AS.
[0064] Step S333: The IMS AS sends a Nimsas_SessionEventControl_Notify request to the DCSF, in which the Session ID is set to 123 and the Event ID is set to the session establishment failure event.
[0065] Step S334: In response to the received request, the DCSF releases the DCSF settings for the originating terminal and the terminating terminal, and executes generation of an instruction to release the DCSF settings.
[0066] Step S335: The DCSF sends a Nimsas_MediaControl_MediaInstruction request to the IMS AS, which includes an instruction to release the DCMF configuration.
[0067] Step S336: The IMS AS sends an Ndcmf_MRM_Create request to the DCMF, which includes an instruction to release the DCMF setting.
[0068] Step S337: The DCMF releases the DCMF setting in response to the received request.
[0069] Step S338: The DCMF sends an Ndcmf_MRM_Create response to the IMS AS.
[0070] Step S339: The IMS AS sends a Nimsas_MediaControl_MediaInstruction response to the DCSF.
[0071] Step S340: The DCSF sends a Nimsas_SessionEventControl_Notify response to the IMS AS.
[0072] Step S341: The IMS AS sends the SIP 488 (Call ID=123) received in step S332 to the S-CSCF.
[0073] Step S342: The S-CSCF sends the received SIP 488 (Call ID=123) to the P-CSCF.
[0074] Step S343: The P-CSCF transmits the received SIP 488 (Call ID=123) to the UE. The SIP 488 is a response indicating that the data channel cannot be set up.
[0075] The process on the source network side following step S343 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.
[0076] Step S361: The UE sends a SIP INVITE to the P-CSCF, maintaining the Call ID as 123 and including an SDP that sets the calling terminal and the calling network as a data channel and the called terminal and the calling network as voice communication.
[0077] Fig. 9 is a diagram showing an example of the contents of the second SDP in an embodiment of the present invention. In Fig. 9, the setting from the line "m=application" to the line "a=leg between originating device and originating network" indicates that the connection between the originating terminal and the originating network is a data channel. Also, the setting from the line "m=audio" to the line "a=leg between originating network and terminating device" indicates that the connection between the destination terminal and the originating network is a voice communication. Returning to Fig. 8, the following explanation will be given.
[0078] Step S362: The P-CSCF sends the received SIP INVITE to the S-CSCF.
[0079] Step S363: The S-CSCF sends the received SIP INVITE to the IMS AS.
[0080] Step S364: The IMS AS sends a Nimsas_SessionEventControl_Notify request to the DCSF, in which 123 is set as the Session ID and the SDP content of the received SIP INVITE is included.
[0081] Step S365: The DCSF performs the following process in response to the received request.
[0082] DCSF sets up DCSF (its own device) as the web server used by the calling terminal (it can display "Voice being provided to the called terminal").
[0083] The DCSF generates setting information (including the route from the source terminal to the DCSF (its own device)) to be set in the DCMF.
[0084] The DCSF generates configuration information to be set in the MRF used by the destination terminal.
[0085] DCSF generates configuration information for the media information in the SDP offer to set up an audio communication path to be sent to the destination terminal. That is, it deletes the description of "m=application webrtc-datachannel" and generates information by changing the address information in "m=audio".
[0086] Step S366: The DCSF sends a Nimsas_MediaControl_MediaInstruction request to the IMS AS. The request includes the setting information set in step S365 to be set in the DCMF, the setting information to be set in the MRF used by the terminating terminal, and the setting information to be set in the voice communication path to be transmitted to the terminating terminal.
[0087] Step S367: The IMS AS sends an Ndcmf_MRM_Create request to the DCMF, which includes the setting information of the DCMF.
[0088] Step S368: The DCMF executes the setting of the DCMF (its own device) based on the received request.
[0089] Step S369: The DCMF sends an Ndcmf_MRM_Create response to the IMS AS.
[0090] Step S370: The IMS AS configures the MRF for the called terminal (see Section B.2.1 of Non-Patent Document 5). Here, the SIP INVITE used to perform the configuration is originated from the IMS AS, and therefore uses a Call ID (789) different from the Call ID (123) of the SIP INVITE received in step S363.
[0091] Step S371: The IMS AS sends a SIP INVITE (Call ID=789) to the MRF.
[0092] Step S372: The MRF reserves resources for making an announcement to the destination terminal.
[0093] Step S373: The MRF sends a SIP 200 OK (Call ID=789) to the IMS AS as a successful response to the received SIP INVITE.
[0094] Step S374: The IMS AS sends a Nimsas_MediaControl_MediaInstruction response to the DCSF.
[0095] Step S375: DCSF sends a Nimsas_SessionEventControl_Notify response to the IMS AS, which includes SDP information.
[0096] Step S376: The IMS AS sends the S-CSCF a SIP INVITE with a Call ID of 123. The SDP offer of the SIP INVITE specifies that the call is for voice communication (m=audio) and that the MRF of the originating network is the termination point.
[0097] Step S377: The S-CSCF transmits the received SIP INVITE to the I-CSCF on the destination network side.
[0098] The process on the destination network side following step S377 will be described with reference to Fig. 10. Fig. 10 is a diagram showing an example of a fifth sequence diagram according to the embodiment of the present invention.
[0099] Step S381: The I-CSCF sends an Nhss_ImsUECM_Authorize request to the HSS.
[0100] Step S382: 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.
[0101] Step S383: The I-CSCF sends the SIP INVITE received in step S377 to the S-CSCF. The SIP INVITE includes the Call ID value (123), information indicating a request for voice communication setup, and information about the MRF that is the originating network endpoint.
[0102] Step S384: The S-CSCF sends the received SIP INVITE to the IMS AS.
[0103] Step S385: The IMS AS sends an Nhss_ImsSDM_Get request to the HSS, which is a Subscriber Data Management (SDM) request that enables obtaining information about an IMS subscriber.
[0104] Step S386: The HSS sends an Nhss_ImsSDM_Get response to the IMS AS.
[0105] The process on the destination network side following step S386 will be described with reference to Fig. 11. Fig. 11 is a diagram showing an example of a sixth sequence diagram according to the embodiment of the present invention.
[0106] Step S391: The IMS AS sends the SIP INVITE received in step S386 to the S-CSCF.
[0107] Step S392: The S-CSCF sends the received SIP INVITE to the P-CSCF.
[0108] Step S393: The P-CSCF sends the received SIP INVITE to the UE (destination terminal).
[0109] Step S394: The UE (terminating terminal) sends a SIP 183 Session Progress to the P-CSCF in response to the received SIP INVITE. The SIP 183 Session Progress has a Call ID of 123 and includes information indicating that the communication is a voice call (m=audio) in the SDP answer, which is a response to the SDP offer included in the received SIP INVITE, and information about the MRF, which is the end of the source network.
[0110] Step S395: The P-CSCF accesses the PCF and sets up a voice QoS flow in the 5G system (5GS).
[0111] Step S396: The P-CSCF sends the received SIP 183 Session Progress to the S-CSCF.
[0112] Step S397: The S-CSCF sends the received SIP 183 Session Progress to the IMS AS.
[0113] Step S398: The IMS AS sends the received SIP 183 Session Progress to the S-CSCF.
[0114] Step S399: The S-CSCF sends the received SIP 183 Session Progress to the I-CSCF.
[0115] The process on the source network side following step S399 will be described with reference to Fig. 12. Fig. 12 is a diagram showing an example of a seventh sequence diagram according to the embodiment of the present invention.
[0116] Step S401: The I-CSCF sends the SIP 183 Session Progress received in step S399 to the S-CSCF.
[0117] Step S402: The S-CSCF sends the received SIP 183 Session Progress to the IMS AS.
[0118] Step S403: The IMS AS sends a Nimsas_SessionEventControl_Notify request to the DCSF. The request has a Session ID of 123 and includes the SDP content of the received SIP 183 Session Progress. That is, the request includes information (m=audio) indicating that the destination terminal is executing (continuing) the setup process for the audio channel.
[0119] Step S404: In response to the received request, the DCSF updates the media information in the SDP answer. That is, the DCSF deletes the description of "m=audio" and adds the description of "m=application webrtc-datachannel" to generate information indicating that a data channel setup process will be performed for transmission to the originating terminal.
[0120] Step S405: The DCSF sends a Nimsas_SessionEventControl_Notify response to the IMS AS, which includes the information generated in step S404 indicating that the data channel setup process for transmission to the originating terminal is to be executed.
[0121] Step S406: The IMS AS sends a SIP 183 Session Progress to the S-CSCF.
[0122] Step S407: The S-CSCF sends the received SIP 183 Session Progress to the P-CSCF.
[0123] Step S408: The P-CSCF accesses the PCF and sets up a QoS flow for the bootstrap data channel (Bootstrap DC) in the 5G system (5GS).
[0124] Step S409: The P-CSCF sends the received SIP 183 Session Progress to the UE (originating terminal). The SIP 183 Session Progress includes a response indicating that a data channel can be established between the UE (originating terminal) and the originating network. Furthermore, the UE (originating terminal) establishes a data channel between itself (originating terminal) and the originating network.
[0125] The processing on the source network side and the destination network side subsequent to step S409 will be described with reference to Fig. 13. Fig. 13 is a diagram showing an example of an eighth sequence diagram according to the embodiment of the present invention.
[0126] Step S500: 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 S409.
[0127] Step S501: The P-CSCF sends the received PRACK to the S-CSCF.
[0128] Step S502: The S-CSCF sends the received PRACK to the IMS AS.
[0129] Step S503: The IMS AS sends the received PRACK to the S-CSCF.
[0130] Step S504: The S-CSCF transmits the received PRACK to the I-CSCF on the destination network side.
[0131] The subsequent processing is performed by the network node on the destination network side or the UE.
[0132] Step S505: The I-CSCF sends the received PRACK to the S-CSCF.
[0133] Step S506: The S-CSCF sends the received PRACK to the IMS AS.
[0134] Step S507: The IMS AS sends the received PRACK to the S-CSCF.
[0135] Step S508: The S-CSCF sends the received PRACK to the P-CSCF.
[0136] Step S509: The P-CSCF sends the received PRACK to the UE.
[0137] Step S510: The UE sends a success response (200 OK) to the P-CSCF in response to the received PRACK.
[0138] Step S511: The P-CSCF sends a success response (200 OK) to the S-CSCF in response to the received PRACK.
[0139] Step S512: The S-CSCF sends a success response (200 OK) to the received PRACK to the IMS AS.
[0140] Step S513: The IMS AS sends a success response (200 OK) to the S-CSCF in response to the received PRACK.
[0141] Step S514: The S-CSCF sends a success response (200 OK) to the I-CSCF in response to the received PRACK.
[0142] Step S515: The I-CSCF sends a success response (200 OK) to the S-CSCF on the source network side in response to the received PRACK.
[0143] Subsequent processing is performed by the network node or UE on the originating network side.
[0144] Step S516: The S-CSCF sends a success response (200 OK) to the received PRACK to the IMS AS.
[0145] Step S517: The IMS AS sends a success response (200 OK) to the S-CSCF in response to the received PRACK.
[0146] Step S518: The S-CSCF sends a success response (200 OK) to the P-CSCF in response to the received PRACK.
[0147] Step S519: The P-CSCF sends a success response (200 OK) to the UE in response to the received PRACK.
[0148] The processing on the source network side and the destination network side subsequent to step S519 will be described with reference to Fig. 14. Fig. 14 is a diagram showing an example of a ninth sequence diagram according to the embodiment of the present invention.
[0149] Step S530: The UE on the source network side sends UPDATE, which is a method for updating a session in SIP, to the P-CSCF.
[0150] Step S531: The P-CSCF sends the received UPDATE to the S-CSCF.
[0151] Step S532: The S-CSCF sends the received UPDATE to the IMS AS.
[0152] Step S533: The IMS AS sends the received UPDATE to the S-CSCF.
[0153] Step S534: The S-CSCF transmits the received UPDATE to the I-CSCF on the destination network side.
[0154] The subsequent processing is performed by the network node on the destination network side or the UE.
[0155] Step S535: The I-CSCF sends the received UPDATE to the S-CSCF.
[0156] Step S536: The S-CSCF sends the received UPDATE to the IMS AS.
[0157] Step S537: The IMS AS sends the received UPDATE to the S-CSCF.
[0158] Step S538: The S-CSCF sends the received UPDATE to the P-CSCF.
[0159] Step S539: The P-CSCF sends the received UPDATE to the UE.
[0160] Step S540: A user call is performed in the UE.
[0161] Step S541: The UE sends a success response (200 OK) to the P-CSCF in response to the received UPDATE.
[0162] Step S542: The P-CSCF sends a success response (200 OK) to the S-CSCF in response to the received UPDATE.
[0163] Step S543: The S-CSCF sends a success response (200 OK) to the received UPDATE to the IMS AS.
[0164] Step S544: The IMS AS sends a success response (200 OK) to the S-CSCF in response to the received UPDATE.
[0165] Step S545: The S-CSCF sends a success response (200 OK) to the I-CSCF in response to the received UPDATE.
[0166] Step S546: The I-CSCF sends a success response (200 OK) to the S-CSCF on the source network side in response to the received UPDATE.
[0167] Subsequent processing is performed by the network node or UE on the originating network side.
[0168] Step S547: The S-CSCF sends a success response (200 OK) to the received UPDATE to the IMS AS.
[0169] Step S548: The IMS AS sends a success response (200 OK) to the S-CSCF in response to the received UPDATE.
[0170] Step S549: The S-CSCF sends a success response (200 OK) to the P-CSCF in response to the received UPDATE.
[0171] Step S550: The P-CSCF sends a success response (200 OK) to the UE in response to the received UPDATE.
[0172] The processing on the source network side and the destination network side subsequent to step S550 will be described with reference to Fig. 15. Fig. 15 is a diagram showing an example of a tenth sequence diagram according to an embodiment of the present invention. The subsequent processing is performed by a network node or UE on the destination network side.
[0173] Step S600: In the UE, a user response to the user call in step S540 is performed.
[0174] Step S601: The UE sends a success response (SIP 200 OK) to the P-CSCF.
[0175] Step S602: The P-CSCF sends the received success response (SIP 200 OK) to the S-CSCF.
[0176] Step S603: The S-CSCF sends the received success response (SIP 200 OK) to the IMS AS.
[0177] Step S604: The IMS AS sends the received successful response (SIP 200 OK) to the S-CSCF.
[0178] Step S605: The S-CSCF sends the received success response (SIP 200 OK) to the I-CSCF.
[0179] Step S606: The I-CSCF sends a success response (200 OK) to the S-CSCF on the source network side in response to the received UPDATE.
[0180] Subsequent processing is performed by the network node or UE on the originating network side.
[0181] Step S607: The S-CSCF sends the received success response (SIP 200 OK) to the IMS AS.
[0182] Step S608: Since the IMS AS has set an MRF for the called terminal for Call ID=123, it instructs the MRF to start an announcement.
[0183] Step S609: The IMS AS sends, to the MRF, an acknowledgment (ACK) in response to the SIP 200 OK received in step S373 of Fig. 8. The Call ID of the SIP ACK is 789, and includes an instruction to start an announcement to the UE on the destination network side.
[0184] Step S610: The MRF starts an announcement to the UE on the destination network side. For example, the MRF makes an announcement such as "If you want to make a voice call, please press 1."
[0185] Step S611: The IMS AS sends the success response (SIP 200 OK) received in step S607 to the S-CSCF.
[0186] Step S612: The S-CSCF sends the received success response (SIP 200 OK) to the P-CSCF.
[0187] Step S613: The P-CSCF sends the received success response (SIP 200 OK) to the UE.
[0188] Step S614: The UE sends an acknowledgement (ACK) to the P-CSCF for the received successful response (SIP 200 OK).
[0189] Step S615: The P-CSCF sends an acknowledgement (ACK) of the reception to the S-CSCF.
[0190] Step S616: The S-CSCF sends an acknowledgement (ACK) of the received message to the IMS AS.
[0191] Step S617: The IMS AS sends an acknowledgement (ACK) of the reception to the S-CSCF.
[0192] Step S618: The S-CSCF sends an acknowledgement (ACK) of the received message to the I-CSCF on the destination network side.
[0193] The subsequent processing is performed by the network node on the destination network side or the UE.
[0194] Step S619: The I-CSCF sends an acknowledgement (ACK) of the reception to the S-CSCF.
[0195] Step S620: The S-CSCF sends an acknowledgement (ACK) of the received message to the IMS AS.
[0196] Step S621: The IMS AS sends a received acknowledgement (ACK) to the S-CSCF.
[0197] Step S622: The S-CSCF sends an acknowledgement (ACK) of the received message to the P-CSCF.
[0198] Step S623: The P-CSCF sends an acknowledgement (ACK) of the reception to the UE.
[0199] The processing on the source network side and the destination network side subsequent to step S623 will be described with reference to Fig. 16. Fig. 16 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 or UE on the source network side, or a UE on the destination network side.
[0200] Step S700: The UE on the source network side sends an HTTP GET request to the DCMF to request screen information including information about the destination terminal.
[0201] Step S701: The DCMF converts the host name so that the UE on the calling network side can download a caller-specific screen.
[0202] Step S702: The DCMF sends the received HTTP GET request to the DCSF.
[0203] Step S703: The DCSF generates screen information for displaying "Called user's voice being provided." This information is the information that the calling terminal has requested to obtain from its own device (DCSF), which is a Web server.
[0204] Step S704: 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 for displaying "Called user's voice being provided."
[0205] Step S705: The DCMF sends the received HTTP GET response to the UE on the source network side, which includes information about the destination terminal.
[0206] Step S706: After that, the UE on the source network side sends an HTTP GET request to the DCMF to request screen information including information about the destination terminal, as necessary.
[0207] Step S707: The UE on the destination network side transmits input information in dual-tone multi-frequency (DTMF) according to the announcement received in step S610 to the MRF. DTMF may also be called dial tone.
[0208] Step S708: The MRF sends a SIP INFO containing DTMF input information (for example, abcd) corresponding to the received DTMF input and having a Call ID of 789 to the IMS AS.
[0209] Step S709: The IMS AS sends a Nimsas_SessionEventControl_Notify request to the DCSF, in which the Session ID is set to 123 and the Event ID is set to the session information event corresponding to the DTMF input information (DTMF=abcd).
[0210] Step S710: The UE on the source network side sends an HTTP GET request to the DCMF to request screen information including information about the destination terminal.
[0211] Step S711: The DCMF sends the received HTTP GET request to the DCSF.
[0212] Step S712: The DCSF generates screen information based on the DTMF input result of the called user. This information is the information that the calling terminal has requested to obtain from its own device (DCSF) which is a Web server.
[0213] Step S713: The DCSF sends an HTTP GET response to the DCMF in response to the received HTTP GET request. The HTTP GET response includes the screen information.
[0214] Step S714: The DCMF sends the received HTTP GET response to the UE on the source network side, which includes information about the destination terminal.
[0215] Step S715: In response to the received response, the UE on the originating network side sends a SIP reINVITE to the P-CSCF. In the SIP reINVITE, the Call ID is 123, and the SDP offer is set to voice communication (m=audio). That is, the UE on the originating network side sets up a voice communication path between its own terminal and the destination terminal. After that, a voice communication path is set up between the originating terminal and the destination terminal, and voice communication is established.
[0216] According to the above-mentioned embodiment, in an IMS data channel network, when the destination network does not support a data channel, a communication path can be established between the source network and the destination terminal, and a data channel can be established between the source terminal and the source network.Furthermore, a voice communication path can be established between the source terminal and the destination terminal, and voice communication can be established.
[0217] (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.
[0218] <Base Station 10 and Network Node 30> Fig. 17 is a diagram showing an example of the functional configuration of the base station 10 and the network node 30. As shown in Fig. 17, 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. 17 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.
[0219] 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.
[0220] 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.
[0221] 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.
[0222] <Terminal 20> Fig. 18 is a diagram showing an example of the functional configuration of the terminal 20. As shown in Fig. 18, 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. 18 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, the communication device that becomes the resource holder 20 may have the same functional configuration as the terminal 20.
[0223] 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.
[0224] 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.
[0225] 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.
[0226] (Hardware Configuration) The block diagrams (FIGS. 17 and 18) 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.
[0227] 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.
[0228] 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. 19 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.
[0229] 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.
[0230] 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.
[0231] 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.
[0232] 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. 17 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. 18 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.
[0233] 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.
[0234] 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.
[0235] 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.
[0236] 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).
[0237] 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.
[0238] 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.
[0239] Fig. 20 shows an example configuration of a vehicle 2001. As shown in Fig. 20, 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.
[0240] 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.
[0241] 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).
[0242] 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.
[0243] 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.
[0244] 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.
[0245] 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.
[0246] 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.
[0247] 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.
[0248] 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.
[0249] (Summary of embodiment) As described above, according to an embodiment of the present invention, there is provided a terminal having a transmitting unit that transmits a request to a first network node to execute data channel setup, and a receiving unit that receives from the first network node a response that the data channel setup is not possible, wherein the transmitting unit transmits to the first network node a request to execute data channel setup between the terminal itself and a source network and voice communication path setup between the source network and the destination terminal, and the receiving unit receives from the first network node a response that the data channel setup between the terminal itself and the source network is possible, and further having a control unit that executes data channel setup between the terminal itself and the source network.
[0250] With the above configuration, in an IMS data channel network, when the destination network does not support a data channel, it is possible to set up a communication path between the source network and the destination terminal and to set up a data channel between the source terminal and the source network.
[0251] The transmitting unit may transmit a request message to the first network node to obtain information regarding the receiving terminal from a second network node configured as a web server for use by the terminal itself; the receiving unit may receive from the first network node the information regarding the receiving terminal transmitted from the second network node configured as the web server; and the control unit may perform voice communication path setup between the terminal itself and the receiving terminal based on the information regarding the receiving terminal.
[0252] With this configuration, in an IMS data channel network, when the destination network does not support data channels, it is possible to set up a communication path between the source network and the destination terminal, and to set up a data channel between the source terminal and the source network.
[0253] According to an embodiment of the present invention, there is also provided a network node having: a receiving unit that receives from a first network node a request to execute a data channel setup between a calling terminal in its own network and its own network, and a voice communication path setup between a called terminal in another network and its own network; a control unit that sets its own network node as a web server to be used by the calling terminal, generates first setting information that sets a communication path between the calling terminal and its own network to be used by the calling terminal, generates second setting information that sets a second network node that is to be an end of the voice communication path to be used by the called terminal, and transmits this to the called terminal; and a transmitting unit that transmits the first setting information, the second setting information, and the third setting information to the first network node, wherein the receiving unit receives from the first network node a first message indicating that the called terminal is to execute processing to set up the voice communication path, the control unit generates a second message indicating that data channel setup processing is to be executed to be transmitted to the calling terminal, and the transmitting unit transmits the second message to the first network node.
[0254] With the above configuration, in an IMS data channel network, when the destination network does not support a data channel, it is possible to set up a communication path between the source network and the destination terminal and to set up a data channel between the source terminal and the source network.
[0255] The receiving unit may receive input information sent by the receiving terminal from the first network node, and the control unit may generate information to be acquired by the calling terminal from its own device configured as a Web server based on the input information.
[0256] With this configuration, in an IMS data channel network, when the destination network does not support data channels, it is possible to set up a communication path between the source network and the destination terminal, and to set up a data channel between the source terminal and the source network.
[0257] Furthermore, according to an embodiment of the present invention, there is provided a communication method executed by a terminal, comprising: a transmitting step of transmitting a request to a first network node to execute data channel setup; and a receiving step of receiving from the first network node a response transmitted from the terminating network indicating that the data channel setup is not possible, wherein the transmitting step transmits to the first network node a request to execute data channel setup between the terminal itself and a source network and voice communication path setup between the source network and the terminating terminal, and the receiving step receives from the first network node a response indicating that the data channel setup between the terminal itself and the source network is possible, and a control step of executing data channel setup between the terminal itself and the source network.
[0258] With the above configuration, in an IMS data channel network, when the destination network does not support a data channel, it is possible to set up a communication path between the source network and the destination terminal and to set up a data channel between the source terminal and the source network.
[0259] Furthermore, according to an embodiment of the present invention, there is provided a communication method executed by a network node, comprising: a receiving step of receiving from a first network node a request to execute a data channel setup between a calling terminal in its own network and its own network, and a voice communication path setup between a called terminal in another network and its own network; a control step of generating third setting information to set up the voice communication path, the control step setting up the first network node as a web server to be used by the calling terminal, generating first setting information to set up a communication path between the calling terminal and its own network to be used by the calling terminal, generating second setting information to set up a second network node to be a termination of the voice communication path to be used by the called terminal, and transmitting the second setting information to the called terminal; and a transmitting step of transmitting the first setting information, the second setting information, and the third setting information to the first network node,
[0260] With the above configuration, in an IMS data channel network, when the destination network does not support a data channel, it is possible to set up a communication path between the source network and the destination terminal and to set up a data channel between the source terminal and the source network.
[0261] (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.
[0262] 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.
[0263] 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).
[0264] 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.
[0265] 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).
[0266] 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.
[0267] Input and output information may be stored in a specific location (for example, memory) or may be managed using a management table. Input and output information may be overwritten, updated, or added to. Output information may be deleted. Input information may be transmitted to another device.
[0268] In the present disclosure, the determination may be made based on a value represented by one bit (0 or 1), a Boolean value (true or false), or a numerical comparison (e.g., comparison with a predetermined value).
[0269] 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.
[0270] 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.
[0271] 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.
[0272] 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.
[0273] As used in this disclosure, the terms "system" and "network" are used interchangeably.
[0274] 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.
[0275] 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.
[0276] 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.
[0277] 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.
[0278] 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.
[0279] In this disclosure, the terms "Mobile Station (MS)," "user terminal," "User Equipment (UE)," "terminal," and the like may be used interchangeably.
[0280] 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.
[0281] 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.
[0282] 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.
[0283] 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.
[0284] 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.
[0285] 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.
[0286] The reference signal may be abbreviated as RS (Reference Signal) or may be called a pilot depending on the applicable standard.
[0287] 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."
[0288] 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.
[0289] The "means" in the configuration of each of the above devices may be replaced with "part," "circuit," "device," etc.
[0290] 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.
[0291] 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.
[0292] 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."
[0293] 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).
[0294] 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.
[0295] 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 transmitting unit that transmits a request to a first network node to execute data channel setup; and a receiving unit that receives from the first network node a response transmitted from the terminating network indicating that the data channel setup is not possible, wherein the transmitting unit transmits to the first network node a request to execute data channel setup between the terminal itself and a source network and voice communication path setup between the source network and the terminating terminal, the receiving unit receives a response from the first network node indicating that a data channel setup is possible between the terminal itself and the source network, and further having a control unit that executes data channel setup between the terminal itself and the source network.
2. The terminal described in claim 1, wherein the transmitting unit transmits a request message to the first network node to obtain information regarding the called terminal from a second network node configured as a Web server for use by the terminal, the receiving unit receives from the first network node the information regarding the called terminal transmitted from the second network node configured as the Web server, and the control unit performs voice communication path setting between the terminal and the called terminal based on the information regarding the called terminal.
3. A network node comprising: a receiving unit that receives from a first network node a request to execute a data channel setup between a source terminal in its own network and its own network, and a voice communication path setup between a destination terminal in another network and its own network; a control unit that sets its own device as a web server to be used by the source terminal, generates first setting information to set a communication path between the source terminal and its own device to be used by the source terminal, generates second setting information to set a second network node that is an end of the voice communication path to be used by the destination terminal, and generates third setting information to set the voice communication path and to send to the destination terminal; and a transmitting unit that transmits the first setting information, the second setting information, and the third setting information to the first network node, wherein the receiving unit receives a first message from the first network node indicating that the destination terminal will execute setup processing for the voice communication path, the control unit generates a second message indicating that a data channel setup processing will be executed to be sent to the source terminal, and the transmitting unit transmits the second message to the first network node.
4. A network node as described in claim 3, wherein the receiving unit receives input information transmitted by the destination terminal from the first network node, and the control unit generates information to be acquired by the source terminal from the device configured as a Web server based on the input information.
5. A communications method executed by a terminal, comprising: a transmitting step of transmitting a request to a first network node to execute data channel setup; and a receiving step of receiving from the first network node a response transmitted from the terminating network indicating that the data channel setup is not possible, wherein the transmitting step transmits to the first network node a request to execute data channel setup between the terminal itself and a source network and voice communication path setup between the source network and the terminating terminal, and the receiving step receives from the first network node a response indicating that a data channel setup is possible between the terminal itself and the source network, and further comprising a control step of executing data channel setup between the terminal itself and the source network.
6. A communication method executed by a network node, comprising: a receiving step of receiving from a first network node a request to execute a data channel setup between a source terminal in its own network and its own network, and a voice communication path setup between a destination terminal in another network and its own network; a control step of setting its own device as a web server used by the source terminal, generating first setting information for setting a communication path between the source terminal and its own device used by the source terminal, generating second setting information for setting a second network node which is an end of the voice communication path used by the destination terminal, and generating third setting information for setting the voice communication path to be sent to the destination terminal; and a sending step of sending the first setting information, the second setting information, and the third setting information to the first network node.
Citation Information
Cited By
Method and apparatus for supporting avatar call in wireless communication system
US20250141942A1
