WO2025118917A1 - Procédé, appareil et système de communication - Google Patents

Procédé, appareil et système de communication Download PDF

Info

Publication number
WO2025118917A1
WO2025118917A1 PCT/CN2024/131062 CN2024131062W WO2025118917A1 WO 2025118917 A1 WO2025118917 A1 WO 2025118917A1 CN 2024131062 W CN2024131062 W CN 2024131062W WO 2025118917 A1 WO2025118917 A1 WO 2025118917A1
Authority
WO
WIPO (PCT)
Prior art keywords
data channel
application
request
information
ims
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Pending
Application number
PCT/CN2024/131062
Other languages
English (en)
Chinese (zh)
Inventor
李牧
胡晓琨
左俊
纪孟迪
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Huawei Technologies Co Ltd
Original Assignee
Huawei Technologies Co Ltd
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Huawei Technologies Co Ltd filed Critical Huawei Technologies Co Ltd
Publication of WO2025118917A1 publication Critical patent/WO2025118917A1/fr
Pending legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L65/00—Network arrangements, protocols or services for supporting real-time applications in data packet communication
    • H04L65/80—Responding to QoS
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L65/00—Network arrangements, protocols or services for supporting real-time applications in data packet communication
    • H04L65/10—Architectures or entities
    • H04L65/1016—IP multimedia subsystem [IMS]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L65/00—Network arrangements, protocols or services for supporting real-time applications in data packet communication
    • H04L65/1066—Session management
    • H04L65/1101—Session protocols
    • H04L65/1104—Session initiation protocol [SIP]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W28/00—Network traffic management; Network resource management
    • H04W28/02—Traffic management, e.g. flow control or congestion control
    • H04W28/10—Flow control between communication endpoints

Definitions

  • the present application relates to the field of communication technology, and in particular to a communication method, device and system.
  • the 3rd Generation Partnership Project (3GPP) defines the IMS data channel (DC) based on the Internet protocol (IP) multimedia subsystem (IMS) audio and video communication architecture. That is, by establishing one or more data channels parallel to the audio channel and video channel in the IMS communication session, the data of the DC application (which can be any type of data, such as text, pictures) is transmitted, so that real-time interaction, screen sharing, overlay of augmented reality (AR), and even a fully immersive experience with synchronization of hearing, vision, and touch can be achieved in the IMS communication session process (such as audio and video call process).
  • IP Internet protocol
  • IMS Internet protocol
  • AR augmented reality
  • Different DC applications can have different traffic types according to business needs.
  • the traffic types of some DC applications may be configured as traffic exemption types, while the traffic types of some DC applications may be configured as non-traffic exemption types. Therefore, how to control the acquisition or use of DC applications still needs further study.
  • the present application provides a communication method, device and system for enabling a data channel control network element to manage and control the acquisition or use of a data channel application according to the traffic type of the data channel application and the traffic switch state of a communication device.
  • an embodiment of the present application provides a communication method (or an information transmission method), which can be applied to a data channel control network element or a component in a data channel control network element (such as a circuit or a chip).
  • a communication method or an information transmission method
  • the data channel control network element receives a request message from a first communication device, and the request message is used to request to obtain a data channel application or to request to use the data channel application; according to the traffic type of the data channel application and the traffic switch state of the first communication device, the request corresponding to the request message is rejected or the request corresponding to the request message is accepted; wherein the traffic type is a traffic exemption type or a non-traffic exemption type, and the traffic switch state is on or off.
  • the data channel control network element manages and controls the acquisition or use of the data channel application according to the traffic type of the data channel application and the traffic switch status of the first communication device, so as to avoid wasting the bandwidth resources of the operator network by accepting request information of non-traffic exemption type data channel applications when the traffic switch of the first communication device is in the closed state.
  • the request corresponding to the request information is rejected, including: determining that the traffic type is a non-traffic exemption type and the traffic switch status is closed; and sending a first response information, wherein the first response information indicates that the request corresponding to the request information is rejected.
  • a request corresponding to the request information is received, including: determining that the traffic type is a traffic exemption type and the traffic switch status is closed; and sending a second response information, wherein the second response information indicates acceptance of the request corresponding to the request information.
  • the first response information includes reason information, and the reason information is used to indicate that the reason for the rejection is that the traffic type of the data channel application is a non-traffic exemption type.
  • the reason information is used to indicate that the reason for the rejection is that the traffic type applied by the data channel is inconsistent with the traffic switch state of the first communication device.
  • the first communication device is informed of the reason for the rejection.
  • the request information is used to request acquisition of the data channel application, and the second response information includes an installation package of the data channel application; or, the request information is used to request use of the data channel application, and the second response information includes media resource information for establishing an application data channel corresponding to the data channel application.
  • the method further includes: receiving status information from an Internet Protocol Multimedia Subsystem IMS application server, wherein the status information is used to indicate the flow switch status.
  • the receiving the status information from the IMS application server includes: receiving a session event reporting message from the IMS application server, wherein the session event reporting message includes the status information.
  • the status information includes a packet switched data interruption flag.
  • the method also includes: obtaining a traffic exemption application whitelist, the traffic exemption application whitelist including multiple application identifiers, each application identifier being used to identify a data channel application identified as a traffic exemption type by the network side; based on the traffic exemption application whitelist including the identifier of the data channel application, determining that the traffic type of the data channel application is the traffic exemption type; or, based on the traffic exemption application whitelist not including the identifier of the data channel application, determining that the traffic type of the data channel application is the non-traffic exemption type.
  • the first communication device is a calling party user equipment, and the data channel control network element is a network element in an originating IMS network; or, the first communication device is a called party user equipment, and the data channel control network element is a network element in a terminating IMS network.
  • an embodiment of the present application provides a communication method, which can be applied to an IMS application server or a component in an IMS application server (such as a circuit or a chip).
  • the IMS application server obtains status information of a first communication device, and the status information is used to indicate the flow switch status of the first communication device, and the flow switch status is on or off; the status information is sent to a data channel control network element, and the status information is used to accept or reject a request corresponding to the request information sent by the first communication device, and the request information is used to request to obtain a data channel application or request to use the data channel application.
  • obtaining status information of a first communication device includes: receiving a registration request message or a re-registration request message from the first communication device, the registration request message or the re-registration request message including the status information.
  • sending the status information to the data channel control network element includes: receiving a session initiation protocol SIP message from an IMS communication control network element, the SIP message being used to manage a communication session between the first communication device and the second communication device, the communication session being associated with a data channel; and sending the status information to the data channel control network element according to the SIP message.
  • sending the status information to the data channel control network element includes: sending a session event reporting message to the data channel control network element, wherein the session event reporting message includes the status information.
  • the request information is used to request the use of the data channel application; the method also includes: receiving a first response information from the data channel control network element, the first response information indicating a rejection of the request corresponding to the request information; wherein the first response information includes reason information, and the reason information is used to indicate that the reason for the rejection is that the traffic type of the data channel application is a non-traffic exemption type.
  • the reason information is used to indicate that the reason for the rejection is that the traffic type applied by the data channel is inconsistent with the traffic switch state of the first communication device.
  • the request information is used to request the use of the data channel application; the method also includes: receiving a second response information from the data channel control network element, the second response information indicating acceptance of the request corresponding to the request information; the second response information includes media resource information for establishing an application data channel corresponding to the data channel application.
  • the first communication device is a calling party user equipment
  • the IMS application server is a network element in an originating IMS network
  • the data channel control network element is a network element in an originating IMS network
  • the first communication device is a called party user equipment
  • the IMS application server is a network element in a terminating IMS network
  • the data channel control network element is a network element in a terminating IMS network.
  • an embodiment of the present application provides a communication method (or information transmission method), in which an IMS application server obtains status information of a first communication device, wherein the status information is used to indicate a flow switch status of the first communication device, wherein the flow switch status is on or off; the IMS application server sends the status information to a data channel control network element, and the data channel control network element receives the status information; the data channel control network element receives request information from the first communication device, wherein the request information is used to request acquisition of a data channel application or request use of the data channel application; the data channel control network element rejects the request corresponding to the request information or accepts the request corresponding to the request information according to the flow type of the data channel application and the flow switch status; wherein the flow type is a flow exemption type or a non-flow exemption type.
  • the present application provides a communication device, wherein the communication device has the function of implementing the first aspect or the second aspect, for example, the communication device includes a module or unit or means corresponding to executing the operation involved in the first aspect or the second aspect,
  • the modules, units or means may be implemented by software or hardware, or the corresponding software may be implemented by hardware.
  • the communication device includes a processing unit and a communication unit, wherein the communication unit can be used to send and receive signals to achieve communication between the communication device and other devices; the processing unit can be used to perform some internal operations of the communication device.
  • the functions performed by the processing unit and the communication unit can correspond to the operations involved in the first aspect or the second aspect above.
  • the communication device includes a processor, which can be used to couple with a memory.
  • the memory can store necessary computer programs or instructions for implementing the functions involved in the first aspect or the second aspect.
  • the processor can execute the computer program or instructions stored in the memory, and when the computer program or instructions are executed, the communication device implements the method in any possible design or implementation of the first aspect or the second aspect.
  • the communication device includes a processor and a memory
  • the memory can store necessary computer programs or instructions for implementing the functions involved in the first aspect or the second aspect.
  • the processor can execute the computer program or instructions stored in the memory, and when the computer program or instructions are executed, the communication device implements the method in any possible design or implementation of the first aspect or the second aspect.
  • the communication device includes a processor and an interface circuit, wherein the processor is used to communicate with other devices through the interface circuit and execute the method in any possible design or implementation of the first aspect or the second aspect above.
  • the processor can be implemented by hardware or by software.
  • the processor can be a logic circuit, an integrated circuit, etc.; when implemented by software, the processor can be a general-purpose processor, which is implemented by reading the software code stored in the memory.
  • the above processors can be one or more, and the memories can be one or more.
  • the memory can be integrated with the processor, or the memory can be separately set from the processor. In the specific implementation process, the memory can be integrated with the processor on the same chip, or can be set on different chips respectively.
  • the embodiment of the present application does not limit the type of memory and the setting method of the memory and the processor.
  • the present application provides a communication system, which may include an IMS application server and a data channel control network element; wherein the data channel control network element is used to execute the method provided in the first aspect above, and the IMS application server is used for the method provided in the second aspect above.
  • the present application provides a computer-readable storage medium, in which computer-readable instructions are stored.
  • a computer reads and executes the computer-readable instructions, the computer executes a method in any possible design of the first to third aspects above.
  • the present application provides a computer program product.
  • the computer reads and executes the computer program product, the computer executes the method in any possible design of the first to third aspects above.
  • the present application provides a chip, comprising a processor, wherein the processor is coupled to a memory and is used to read and execute a software program stored in the memory to implement a method in any possible design of the first to third aspects above.
  • FIG1 is a schematic diagram of a network architecture provided in an embodiment of the present application.
  • FIG2 is a schematic diagram of another network architecture provided in an embodiment of the present application.
  • FIG3 is a schematic diagram of a data channel protocol stack provided in an embodiment of the present application.
  • FIG4 is a flow chart of an application for obtaining a data channel provided in an embodiment of the present application.
  • FIG5 is a schematic diagram of a process for UE 1 and UE 2 to communicate via a data channel provided in an embodiment of the present application;
  • FIG6 is a flow chart of a communication method according to an embodiment of the present application.
  • FIG. 7 is a possible exemplary block diagram of a device involved in an embodiment of the present application.
  • FIG8 is a schematic diagram of a possible structure of the device involved in the embodiments of the present application.
  • the technical solution provided in this application can be applied to various communication systems, such as: the fifth generation (5th generation, 5G) communication system (or called the new radio (new radio, NR) system), the fourth generation (4th generation, 4G) communication system (or called the long term evolution (long term evolution, LTE) system), LTE frequency division duplex (frequency division duplex, FDD) system, LTE time division duplex (time division duplex, TDD) system, etc.
  • the technical solution provided in this application can also be applied to future communication systems, such as the sixth generation (6th generation, 6G) mobile communication system.
  • FIG1 A communication system 100 provided in an embodiment of the present application is illustrated below with reference to FIG1. It should be understood that the communication system described in the present application is only an example and should not constitute any limitation to the present application.
  • each network element or referred to as a functional network element, functional entity, node, device, etc. shown in FIG1 is briefly introduced:
  • Terminal equipment can be called user equipment (UE), terminal, terminal device, access terminal, user unit, user station, mobile station, mobile station (MS), mobile terminal (MT), remote station, remote terminal, mobile device, user terminal, terminal, wireless communication equipment, user agent or user device, etc. It is a device with wireless or wired communication capabilities.
  • the terminal equipment can be connected to the wireless access equipment through the air interface, or the terminal equipment can be connected to the wired access equipment through the wired interface.
  • the terminal equipment can include handheld devices, vehicle-mounted devices, wearable devices or computing devices with communication functions.
  • the terminal device may be a mobile phone, a tablet computer, a computer with wireless communication function (such as a laptop computer, a PDA, etc.), a mobile Internet device (MID), a virtual reality (VR) terminal, an augmented reality (AR) terminal, a smart watch, a smart bracelet, smart glasses, a wireless terminal in industrial control, a wireless terminal in self-driving, a wireless terminal in remote medical, a wireless terminal in smart grid, a wireless terminal in transport safety, etc.
  • MID mobile Internet device
  • VR virtual reality
  • AR augmented reality
  • wireless terminals in smart cities wireless terminals in smart homes, cellular phones, cordless phones, SIP phones, wireless local loop (WLL) stations, personal digital assistants (PDAs), handheld devices with wireless communication functions, other processing devices connected to wireless modems, terminals in the Internet of things (IoT) system, desktop computers, or UEs defined in the 3rd Generation Partnership Project (3GPP) standard specifications, etc. are not restricted.
  • 3GPP 3rd Generation Partnership Project
  • UE 1 and UE 2 in Figure 1 can conduct IMS calls through the IMS network, wherein UE 2 can be referred to as the opposite end device of the IMS call conducted by UE 1, and similarly, UE 1 can be referred to as the opposite end device of the IMS call conducted by UE 2.
  • the IMS network providing services to UE 1 can be referred to as the originating IMS network (originating IMS), and the IMS network providing services to UE 2 can be referred to as the terminating IMS network (terminating IMS).
  • the originating IMS network is the local IMS network (local IMS)
  • the terminating IMS network is the remote IMS network (remote IMS)
  • the terminating IMS network is the local IMS network
  • the originating IMS network is the remote IMS network.
  • the network element architecture within the terminating IMS network is similar to the network element architecture within the originating IMS network.
  • the network element architecture within the remote IMS network is not shown in the figure.
  • CSCF Call session control function
  • CSCF is a functional entity within the IMS and is the core of the entire IMS. It is mainly responsible for processing signaling control during multimedia call sessions. It manages IMS user authentication, IMS bearer quality of service (QoS), cooperates with other network elements to control session initiation protocol (SIP) sessions, as well as service negotiation and resource allocation.
  • SIP session initiation protocol
  • the CSCF network element in this application is referred to as "CSCF”.
  • CSCF can communicate with terminal devices, and CSCF can communicate with gateway devices. For example, the CSCF can select a gateway device to communicate with the terminal device, and the CSCF can allocate routing information, such as IP addresses or ports, to the terminal device and the gateway device.
  • CSCF is divided into proxy CSCF (P-CSCF), interrogating CSCF (interrogating CSCF) and proxy CSCF (P-CSCF).
  • P-CSCF proxy CSCF
  • inter-CSCF proxy CSCF
  • serving CSCF serving CSCF
  • S-CSCF serving CSCF
  • P-CSCF is the entry node for users to access the IMS network, and is mainly responsible for forwarding SIP signaling between IMS users and their home networks.
  • I-CSCF is the unified entry point for IMS users' home networks, and is responsible for allocating or querying S-CSCFs that serve users.
  • S-CSCF is the unified entry point for IMS users' home networks, and is responsible for allocating or querying S-CSCFs that serve users. It can be understood that the above-mentioned P-CSCF, S-CSCF, and I-CSCF can be independently configured in different entities, or integrated in the same entity, and this application does not limit this.
  • the IMS communication control network element in the embodiments of the present application below may be a CSCF, and further, for example, an S-CSCF.
  • IMS access media gateway IMS AGW can provide IMS network access gateway and media gateway functions.
  • DCS Data channel server
  • DCSF data channel signaling function
  • MF media function
  • the DCSF network element is used to provide media resource management functions, including media resource management of data channels
  • the DCSF network element is used to provide data channel signaling control functions. It can be understood that in actual network deployment, the DCSF network element and the MF network element can be co-located (in this case, called DCS) or separately located, and this application does not limit it.
  • DCAR Data channel application repository
  • DCApp is a repository for storing data channel applications (DC App). After a developer completes the development of a DC App, it is uploaded to the operator's DCS, which then saves it to DCAR. When needed, DCS downloads the DC App from DCAR to the local computer for subsequent processing.
  • the data channel control network element in the embodiment of the present application includes a DCSF and optionally also includes a DCAR.
  • HSS Home Subscriber Server
  • IMS Internet Multimedia Subsystem
  • user data may include information about data channel services that users have signed a contract with the operator to use.
  • IMS application server IMS AS is the top-level application layer device in the IMS system, providing basic and supplementary services, such as multimedia conferencing, converged communications, SMS gateways, standard switchboards, and other services.
  • the IMS network is an open system based on IP bearer that provides users with various multimedia services.
  • the IMS AS interacts with the CSCF to trigger and execute various network services.
  • the terminal device and the IMS AS are connected in communication, and the IMS AS can establish a data channel for the terminal device.
  • the IMS AS can be a multimedia telephony application server (MMTEL AS) or a telephony application server (TAS).
  • MMTEL AS multimedia telephony application server
  • TAS telephony application server
  • DC AS Data channel application server
  • DC AS is used to provide data channel business logic. It is understandable that DC AS can be deployed in the IMS network, in which case DC AS can be directly connected to other network elements in the IMS network through interfaces (such as service-oriented interfaces); or DC AS can be deployed outside the IMS network, in which case DC AS can be connected to other network elements in the IMS network through network exposure function (NEF) network elements (or IMS border network management).
  • NEF network exposure function
  • NEF network element NEF network element is used to securely open various services of the 5GC network to third parties.
  • the above-mentioned network architecture applied to the embodiment of the present application is only an example, and the network architecture applicable to the embodiment of the present application is not limited to this. Any network architecture that can realize the functions of the above-mentioned network elements is applicable to the embodiment of the present application, that is, the network architecture and business scenarios described in the embodiment of the present application are for the purpose of more clearly illustrating the technical solution of the embodiment of the present application, and do not constitute a limitation on the technical solution provided in the embodiment of the present application. Ordinary technicians in this field can know that with the evolution of network architecture and the emergence of new business scenarios, the technical solution provided in the embodiment of the present application is also applicable to similar technical problems.
  • network elements or devices listed in the above network architecture are only exemplary, and the network architecture applicable to the present application may also include other network elements or devices, which is not limited in the present application.
  • the communication session described in the embodiment of the present application is an IMS session, which is used to transmit data in communication services, such as data between terminal devices in communication services, and/or data between terminal devices and communication networks in communication services.
  • communication services refer to services such as voice calls, video calls or data interactions between terminal devices as an originating party or a terminating party, and are connected to one or more other terminal devices via a communication network (such as an IMS network).
  • the IMS network is an open system based on IP bearer and provides various multimedia services to users.
  • communication services can cover the entire process from the start of communication establishment (for example, dialing) to the end of communication, or they can cover a part of the process from the start of communication establishment (for example, dialing) to the end of communication, such as the process from the parties participating in the communication service entering the communication state to the end of the communication.
  • Communication services can be one-to-one communication services or one-to-many (such as conferences); the embodiment of the present application takes a one-to-one communication service as an example, but related schemes can be used for one-to-many communication services.
  • An IMS session can be understood as a logical connection between communication devices in a communication service.
  • it can be understood as a logical connection between terminal devices in a communication service, which can transmit data between terminal devices; or it can be understood as a logical connection between a terminal device and a communication network in a communication service, which is used to transmit data between the terminal device and the communication network.
  • an IMS session can be negotiated (or established) based on the session initiation protocol (SIP)/session description protocol (SDP). It is understandable that an IMS session can also be replaced by a communication session, an IMS communication session, a session or a communication service session, etc., without limitation.
  • one communication service may correspond to at least one IMS session.
  • the communication service corresponds to one IMS session, such as the IMS session between UE1 and UE2.
  • the communication service corresponds to one IMS session, such as the IMS session between UE1, UE2 and UE3; or, the communication service corresponds to three IMS sessions, such as the IMS session between UE1 and UE2, the IMS session between UE1 and UE3, and the IMS session between UE2 and UE3.
  • a channel for transmitting the corresponding type of data can be established based on the IMS session.
  • the channel can be divided into a media channel and a data channel.
  • the media channel can be further divided into an audio channel and a video channel.
  • UE 1 and UE 2 can communicate through an IMS network, and the channel established based on the IMS session between UE 1 and UE 2 includes a data channel, an audio channel, and a video channel. It is understandable that Figure 2 is only an example of an IMS session.
  • the channel established based on the IMS session may include a data channel but not a media channel, or the channel established based on the IMS session may include one of an audio channel and a video channel, as well as a data channel, which is not limited in the embodiments of the present application.
  • the audio channel can be used to transmit voice
  • the video channel can be used to transmit video
  • the data channel is specifically described below.
  • the data channel described in the embodiment of the present application also referred to as an IMS data channel, is associated with the IMS session of the terminal device, or is created based on the IMS session of the terminal device, or is created during the IMS session of the terminal device, and is used to transmit application data or an application program (i.e., a program for generating/consuming application data) related to the terminal device during the duration of the IMS session.
  • an application program i.e., a program for generating/consuming application data
  • the data channel of the embodiment of the present application can be divided into at least the following types.
  • the data channel at this time can be called an auxiliary data channel or a dependent data channel.
  • the data channel at this time can be called a standalone data channel or an independent data channel.
  • auxiliary data channel or an independent data channel
  • it can be used to transmit any type of application data between session participants.
  • the purpose of the data channel in the embodiment of the present application or the type of data that can be transmitted has at least the following possibilities.
  • the application data transmitted by the data channel can be interactive application data (interactive data for short).
  • Interactive application data can be application data used to support interactive operations (such as data or code/script used to generate a graphical user interface (GUI) for users to perform interactive operations, such as a "Like” button or a "Red Envelope” button), or application data generated by executing the interactive operation (such as control instructions, control signals or output files generated after the conversation participants perform interactive operations, such as the number of "Likes" and the amount in a "Red Envelope”).
  • GUI graphical user interface
  • I/O input/output
  • the terminal device can also be data collected or stored by the terminal device, for example, data collected by the terminal device through the input/output (I/O) system module, such as images or videos captured by a camera, voice collected by a microphone, text, symbols or emoticons input through a keyboard, and data generated by actions such as clicking/sliding on a touch screen.
  • I/O input/output
  • the application data transmitted by the data channel can also be communication enhancement application data.
  • Communication enhancement data is a type of data generated based on the content of an audio call or video call, such as converting the voice in an audio call or video call into text, or converting sign language in a video call into text or voice. It can also be data superimposed on an audio call or video call, such as AR special effects images, etc. It can also be data independent of an audio call or video call, such as geographic location data, screen sharing data, etc.
  • the application data transmitted by the data channel may also be a remote control command, which can provide remote control services or remote IoT device connection services to users. It can be understood that in the above case, the data channel can also be used to transmit remote control commands.
  • the application transmitted by the data channel may be an installation package, executable code or script of the application.
  • the application may be an interactive enhanced application or a communication enhanced application for enhancing the interactive effect/communication effect of traditional voice calls/video calls. It may also be a remote control application/IoT communication application, which is not limited in the embodiments of the present application.
  • BDC bootstrap data channel
  • ADC application data channel
  • the protocol stack of the IMS session is used to indicate the sum of protocols applicable to the IMS session, which can reflect the transmission process of various data in the IMS session. It is mentioned above that the IMS session can transmit various data (for example, voice, video, text, and data other than voice, video, and text). Therefore, in order to match the transmission requirements of different types of data, different protocols can be configured for channels of different types of data.
  • the protocol stack of the IMS session can be shown in Figure 3.
  • the bottom layer protocol of the audio channel, video channel and data channel is the Internet protocol (IP), and above IP is the user datagram protocol (UDP).
  • IP Internet protocol
  • UDP user datagram protocol
  • the protocols above UDP are different, which are explained below.
  • RTP real-time transport protocol
  • RTCP RTP control protocol
  • SCTP stream control transmission protocol
  • SCTP SCTP
  • SCTP SCTP
  • application data/application the conversational multimedia application.
  • UDP, RTP, RTCP, DTLS and SCTP protocols are all transport layer protocols. Therefore, the UDP/RTP protocol stack can be understood as a type of transport layer protocol stack for audio channels/video channels, the UDP/RTCP protocol stack can be understood as another type of transport layer protocol stack for audio channels/video channels, and the UDP/DTLS/SCTP protocol stack can be understood as a transport layer protocol stack for data channels.
  • the symbol "/" used to describe the protocol stack represents the hierarchical relationship of the protocols in the protocol stack. For example, the UDP/DTLS/SCTP protocol stack indicates that the DTLS protocol is above UDP, and the SCTP protocol is above the DTLS protocol.
  • the transport layer protocol stack of the data channel is not limited to the "UDP/DTLS/SCTP” protocol stack shown in Figure 3, but can also be other protocol stacks, for example: “TCP/DTLS/SCTP” protocol stack, "UDP/QUIC” (QUIC is the abbreviation of quick UDP internet connection) protocol stack, "UDP/SCTP” protocol stack, etc.
  • the data channel application of the embodiment of the present application is an application that provides services based on the data channel.
  • the data channel application is usually downloaded by the terminal device from the network side and runs during the IMS communication session without installation and uninstallation. It is understandable that the data channel application can exist in the form of a web page, or in the form of a mini program/quick application/light application, etc., and this application does not limit this.
  • the data channel application involved in the embodiments of the present application may be a DC App in a 4G/5G network.
  • the DC App can transmit various data such as text, pictures, locations, files, etc. before and after an IMS call is established, and realize communication between the two parties in addition to voice calls or video calls, which can greatly enhance the experience of both parties.
  • the terminal device can obtain the DC App from the DCS through the BDC using the hypertext transfer protocol (HTTP) process, and can automatically or interactively update it at any time, and then communicate with the terminal device of the other end through the DC App except for voice calls or video calls.
  • UE 1 and UE 2 are in the same IMS communication session. Assuming that UE 1 wants to share its mobile phone screen with UE 2 during the call with UE 2 to guide B to set up the mobile phone, UE 1 and UE 2 can first obtain the DC App for screen sharing respectively, and then run the DC App respectively to communicate with the UE of the other end except for voice calls or video calls.
  • UE 1 and UE 2 are taken as the calling party user equipment and the called party user equipment as an example for explanation.
  • the developer completes the development of the DC App through an offline process, and then uploads the developed DC App to the operator's DCS.
  • DCS stores DC App in DCAR.
  • DCS downloads DC App from DCAR when needed.
  • UE 1 establishes BDC with DCS and obtains the required DC App from DCS through BDC.
  • UE 2 establishes BDC with DCS and obtains the required DC App from DCS through BDC.
  • UE 1 and UE 2 establish ADC to transmit the interactive data of the DC App.
  • the IMS application server may send a session event reporting message to the DC control network element.
  • the session event reporting message is a non-SIP message, such as an HTTP message.
  • the session event reporting message may be used to report events of a communication session.
  • the events of a communication session may include one or more of the following:
  • the session establishment request event (SessionEstablishmentRequestEvent) indicates that the IMS AS receives the SIP invite request message.
  • the session establishment progress event (SessionEstablishmentProgressEvent) indicates that the IMS AS receives the SIP invitation response message.
  • the session establishment success event (SessionEstablishmentSuccessEvent) indicates that the communication session is established successfully.
  • the session establishment failure event (SessionEstablishmentFailureEvent) indicates that the communication session establishment failed.
  • the media change request event indicates that the IMS AS receives a request for applying for a media resource change; further, the media change request event may include an ADC establishment request event and an ADC teardown request event.
  • the ADC establishment request event indicates that the IMS AS receives an ADC establishment request
  • the ADC teardown request event indicates that the IMS AS receives an ADC teardown request.
  • the media change success event (MediaChangeSuccessEvent) indicates that the request to change the media resource is successful.
  • the media change failure event (MediaChangeFailureEvent) indicates that the request to change the media resource failed.
  • Session TerminationEvent Session Termination Event
  • the event of the communication session may also be other possible events, which is not limited in the embodiment of the present application.
  • PSData Off function of the terminal device corresponds to the flow switch of the terminal device.
  • the PSData Off function of the terminal device is activated, the flow switch state of the terminal device is closed.
  • the PSData Off function of the terminal device is closed or deactivated, the flow switch state of the terminal device is opened.
  • the flow switch state of the terminal device can be set or changed by the user.
  • PS Data Off Exempt Service which can be called flow exemption service
  • all other applications cannot access the PS network.
  • PS Data Off Exempt Service which can be called flow exemption service
  • the current protocol such as 3GPP TS23.2278 describes that the network can send a flow exemption service list to the terminal device when the terminal device is registered, or it can also be configured to the terminal device in other ways.
  • the type of application is a flow exemption type or a non-flow exemption type.
  • Flow exemption type applications can be called flow exemption applications, or flow exemption services; non-flow exemption type applications can be called non-flow exemption applications, or non-flow exemption services.
  • flow exemption applications refer to applications that are allowed to access the PS network even if the user has activated the PSData Off function in the terminal device; non-flow exemption applications refer to applications that are not allowed to access the PS network when the user has activated the PSData Off function in the terminal device.
  • flow exemption type applications are allowed to access the PS network, that is, the terminal device is allowed to obtain or use flow exemption type applications; while non-flow exemption type applications are not allowed to access the PS network, that is, the terminal is not allowed to obtain or use non-flow exemption type applications.
  • UE 1 and UE 2 are two devices in the same IMS call session, or in other words, UE 1 and UE 2 are the opposite end devices of the IMS communication session.
  • IMS core IMS core network
  • IMS AS1, DCS1 or DCSF 1
  • IMS core 2 IMS core 2
  • IMS AS2, DCS2 or DCSF 2
  • UE 1 and UE 2 are both IMS multimedia telecommunication service (multimedia telephony service for IMS, MTSI) terminals (i.e. DC MTSI terminals) that support data channels, and the originating network and the terminating network also support data channels.
  • IMS multimedia telecommunication service multimedia telephony service for IMS, MTSI
  • DC MTSI terminals DC MTSI terminals
  • FIG5 is a schematic diagram of a process for UE 1 and UE 2 to communicate via a data channel. As shown in FIG5 , the process may include:
  • UE 1 and UE 2 establish a bootstrap data channel with DCSF 1 and DCSF 2 respectively through an initial invitation (INVITE) process; DCSF 1 and DCSF 2 obtain and store the association relationship between the calling number, the called number and the call ID.
  • ISVITE initial invitation
  • UE 1 and UE 2 can respectively establish a guided data channel with DCSF 1 and DCSF 2 through the initial invitation process, so as to obtain the guided application through the guided data channel.
  • UE 1 establishes a guided data channel #1 with DCSF 1 and a guided data channel #2 with DCSF 2;
  • UE 2 establishes a guided data channel #3 with DCSF 1 and a guided data channel #4 with DCSF 2.
  • the guided data channel between the UE and the originating DCSF i.e., the DCSF of the originating network
  • guided data channel between the UE and the terminating DCSF i.e., the DCSF of the terminating network
  • the stream IDs corresponding to the above-mentioned guided data channels are only examples, and different guided data channels can also be referred to by other stream IDs.
  • the present application does not limit this.
  • DCSF 1 and DCSF 2 can respectively obtain and save the association between the calling number, called number and Call ID.
  • UE 1 and UE 2 perform media negotiation through the INVITE process to negotiate the media resource information required to establish the guided data channels #1, #2, #3 and #4.
  • DCSF 1 and DCSF 2 obtain and save the association between the calling number, called number and Call ID in the INVITE process.
  • DCSF 1 also obtains the media resource information of guided data channel #1 and guided data channel #3
  • DCSF 2 also obtains the media resource information of guided data channel #2 and guided data channel #4.
  • UE 1 and UE 2 respectively request DCSF 1 and DCSF 2 to obtain the guidance application through the established guidance data channel.
  • the following is an exemplary description in conjunction with S502-S505.
  • UE 1 sends HTTP GET Request messages to DCSF 1 and DCSF 2 respectively, where the Request URI of the HTTP GET Request message is the root directory, indicating that UE 1 requests to obtain the DC application list.
  • DCSF 1 and DCSF 2 receive the HTTP GET Request messages from UE 1 respectively.
  • DCSF 1 and DCSF 2 respectively send HTTP response messages to UE 1, where the HTTP response messages include a DC application list.
  • UE 1 receives HTTP response messages from DCSF 1 and DCSF 2 respectively.
  • UE 1 sends an HTTP get request message to DCSF 1 through boot data channel #1 (i.e., boot data channel No. 0), and the request URI (Request URI) of the HTTP get request message is the root directory, which is used to indicate that UE 1 requests to obtain the DC application list on DCSF 1.
  • DCSF 1 sends an HTTP response message to UE 1 through boot data channel #1, and carries the DC application list on DCSF 1 in the response message.
  • the DC application list sent by DCSF 1 to UE 1 is recorded as boot application #1, and boot application #1 includes the DC application list available to UE 1 on the originating network.
  • bootstrap application #2 includes a list of DC applications available to UE 1 on the terminating network.
  • UE 2 sends HTTP get request messages to DCSF 1 and DCSF 2 respectively, the request URI of the HTTP get request message is the root directory, which is used to indicate that UE 2 requests to obtain the boot application.
  • DCSF 1 and DCSF 2 receive HTTP get request messages from UE 2 respectively.
  • DCSF 1 and DCSF 2 send HTTP response messages to UE 2 respectively, and the HTTP response messages include the boot application.
  • UE 2 receives the HTTP get response messages from DCSF 1 and DCSF 2 respectively.
  • S504 and S505 are similar to S502 and S503 respectively, and the specific process is not limited here.
  • UE 2 can obtain the guided application on DCSF 1 (referred to as guided application #3) from DCSF 1 through guided data channel #3; and obtain the guided application on DCSF 2 (referred to as guided application #4) from DCSF 2 through guided data channel #4.
  • UE 1 determines to start application X, that is, determines that application X needs to be obtained.
  • UE 1 determines to start application X.
  • application X is any data channel application in the guide application #1 obtained by UE 1.
  • UE 1 After UE 1 obtains the guide application #1, it displays the obtained guide application #1 (i.e., the DC application list) on the screen.
  • UE 1 can display the guide application on the screen in the form of pictures or texts, and the user can select any data channel application from the DC application list displayed on the screen.
  • application X When the user selects application X, UE 1 determines to start application X. It can be understood that the guide application #1 is displayed on the screen in the form of pictures or texts.
  • Each DC application in application #1 corresponds to an App ID, which can uniquely identify a DC application on DCSF1 and map to the resource location of the application on DCSF.
  • UE 1 sends an HTTP get request message to DCSF 1.
  • DCSF 1 receives the HTTP get request message from UE 1.
  • UE 1 when UE 1 determines to start application X, UE 1 sends an HTTP acquisition request message to the DCSF of the network to which application X belongs, so as to request to acquire the application X.
  • UE 1 sends an HTTP acquisition request message to DCSF 1 through boot data channel #1 (i.e., boot data channel No. 0), and the request URI (Request URI) of the HTTP acquisition request message is the App ID of application X (represented as App ID-X), which is used to request to acquire the application X, or to request the installation package of application X.
  • UE 1 may also obtain application X after the IMS call is connected.
  • UE 1 and UE 2 in S601 should negotiate to establish a boot data channel through the re-INVITE process (rather than the initial INVITE process).
  • DCSF 1 sends an HTTP response message to UE 1.
  • UE 1 receives the HTTP response message from DCSF 1.
  • DCSF 1 determines the resource location of application X according to App ID-X, and then sends an HTTP response message to UE 1 through data channel #1, and carries application X, that is, the installation package of application X, in the HTTP response message.
  • UE 1 receives the HTTP response message from the DCSF 1, and obtains the installation package of the application X from the HTTP response message.
  • UE 1 runs application X, that is, uses application X.
  • UE 1 After UE 1 obtains application X, it runs application X. For example, UE 1 displays the HTML page corresponding to application X in a web browser and executes the JavaScript script therein.
  • UE 1 and UE 2 negotiate media resource information of the application data channel required by application X, so that UE 1 and UE 2 can communicate other than voice call or video call through application X.
  • the following is explained with reference to S510-S519 as an example.
  • UE 1 sends a re-INVITE request message/update request message to IMS AS1.
  • IMS AS1 receives the re-INVITE request message/UPDATE request message from UE 1.
  • UE 1 executes the JavaScript script in application X, it triggers UE 1 to send a re-INVITE request message to UE 2.
  • the re-INVITE request message is used to negotiate the media resource information of the application data channel required by application X.
  • the re-INVITE request message includes SDP information (such as SDP Offer information), and the SDP Offer information includes media resource information of the application data channel supported (or intended to be used) by UE 1 (such as the IP address, port information, TLS ID and certificate, QoS requirements, etc. used by UE 1 to connect to the 1000th application data channel).
  • SDP Offer information also includes information of application X, such as the identifier of application X (App ID-X). The identifier of application X is used by UE 2 to obtain application X.
  • the information of application X also includes information for downloading application X.
  • the information for downloading application X is used by UE 2 to determine how to obtain application X (i.e., from which network to obtain, or through which boot data channel to obtain).
  • the information for downloading application X and the identifier of application X can be carried in the same parameter of an attribute line, or in different parameters of the same attribute line, or in different attribute lines, which is not limited in this application.
  • IMS AS1 reports the media resource information of the application data channel supported by UE 1 to DCSF 1.
  • DCSF 1 allocates DC resources and instructs to update the SDP offer, and then IMS AS1 updates the SDP offer information.
  • IMS AS1 after IMS AS1 receives the re-INVITE request message/UPDATE request message from UE 1, IMS AS1 reports the media resource information of the application data channel to DCSF 1.
  • DCSF 1 allocates DC resources to the corresponding application data channel based on this information, and instructs IMS AS1 to update the SDP Offer information.
  • IMS AS1 updates the SDP offer information according to the instruction of DCSF 1. For example, if the application data channel passes through the network side (i.e., UE 1—network side—UE 2), DCSF 1 can send the media resource information of the application data channel supported by the network side to IMS AS1, and then IMS AS1 updates the SDP offer information to the media resource information of the application data channel supported by the network side.
  • the specific method is not limited in this application. It can be understood that IMS AS1 retains (i.e., does not modify) the information of application X carried in the SDP offer information.
  • IMS AS1 sends a re-INVITE request message/UPDATE request message to UE 2.
  • UE 2 receives the re-INVITE request message/UPDATE request message from IMS AS1.
  • IMS AS1 updates the SDP offer information
  • IMS AS2 routes the re-INVITE request message/UPDATE request message to UE 2 through IMS core 1, IMS core 2, and IMS AS2.
  • IMS core 1 For convenience, the following description will only take the re-INVITE request message as an example.
  • the re-INVITE request message includes the updated SDP offer information
  • the updated SDP offer information includes the information of the application X as described in S510.
  • S544 UE 2 determines DCSF 1 based on the information of application X.
  • UE 2 parses the attribute line parameter corresponding to the application data channel to obtain the information of application X.
  • the information of application X includes APP ID-X, and UE 2 determines to obtain application X corresponding to APP ID-X according to APP ID-X.
  • the information of application X also includes information for downloading application X, and UE 2 determines DCSF 1 according to the information for downloading application X, that is, determines to request DCSF 1 of the originating network to obtain application X.
  • UE 2 sends an HTTP get request message to DCSF 1.
  • DCSF 1 receives the HTTP get request message from UE 2.
  • UE 2 sends an HTTP obtain request message to DCSF 1 through boot data channel #3 (i.e., boot data channel No. 100) based on the received information of application X.
  • the request URI (Request URI) of the HTTP obtain request message is App ID-X, which is used to request to obtain application X.
  • DCSF 1 sends an HTTP response message to UE 1.
  • UE 2 receives the HTTP response message from DCSF 1.
  • DCSF 1 determines the resource location of application X according to App ID-X, and then sends an HTTP response message to UE 2 through data channel #3, and carries application X, that is, the installation package of application X, in the HTTP response message.
  • UE 2 receives the HTTP response message from the DCSF 1, and obtains the installation package of the application X from the HTTP response message.
  • UE 2 if UE 2 successfully obtains application X, UE 2 runs application X. For example, UE 2 displays the HTML page corresponding to application X in a web browser and executes the JavaScript script therein.
  • UE 2 sends a SIP response message to UE 1.
  • UE 1 receives the SIP response message from UE 2.
  • UE 2 determines that it agrees to establish a corresponding application data channel with UE 1 based on the SDP Offer information (for example, UE 2 supports part or all of the media resource information provided by the SDP Offer information), and UE 2 successfully obtains application X and runs application X (i.e., successfully executes S515-S517), then UE 2 sends a SIP response message to UE 1 to respond to the re-INVITE request message, and the SIP response message can be a 200OK response message.
  • SDP Offer information for example, UE 2 supports part or all of the media resource information provided by the SDP Offer information
  • UE 2 successfully obtains application X and runs application X (i.e., successfully executes S515-S517)
  • UE 2 sends a SIP response message to UE 1 to respond to the re-INVITE request message, and the SIP response message can be a 200OK response message.
  • the SIP response message includes the SDP Answer information determined by UE 1 based on the SDP Offer information, and the SDP Answer information includes the media resource information of the application data channel supported (or willing to use) by UE 2 in the media resource information provided by the SDP Offer information.
  • UE 1 sends an ACK message to UE 2.
  • UE 2 receives the ACK message from UE 1.
  • UE 1 determines that the media resource information negotiation is successful and UE 2 successfully obtains application X according to the information carried in the SIP response message. For example, when the SIP response message carries SDP Answer information, and the IP address and/or port information of UE 2 used to connect to the 1000th application data channel carried in the SDP Answer information is not 0, UE 1 determines that the media resource information negotiation is successful and UE 2 successfully obtains application X. Alternatively, UE 1 determines that the media resource information negotiation is successful and UE 2 successfully obtains application X through other explicit indication information carried in the SIP response message.
  • UE 1 returns an ACK message to UE 2 to indicate successful message reception.
  • UE 1 may not execute S519.
  • UE 1 and UE 2 establish a DTLS association (DTLS Association) and a SCTP association (SCTP Association) based on the negotiated media resource information, and allocate stream ID 1000 to application X, thereby establishing application data channel No. 1000 required by application X.
  • DTLS Association DTLS Association
  • SCTP Association SCTP association
  • application X on UE 1 and application X on UE 2 transmit additional communication information through application data channel No. 1000.
  • the subsequent process is triggered by the calling party user equipment (i.e., UE 1) determining to start application X.
  • the process can also be triggered by the called party user equipment determining to start application Y (for example, application Y can be any DC application in the DC application list available to the called party user equipment on the terminating IMS network).
  • application Y can be any DC application in the DC application list available to the called party user equipment on the terminating IMS network.
  • the process illustrated in FIG. 5 above can also be applied to the scenario of "UE 1 is the called party user equipment, UE 2 is the calling party user equipment, IMS core 1, IMS AS 1, DCS1 are network elements in the terminating IMS network, and IMS core 2, IMS AS2, DCS2 are network elements in the originating IMS network".
  • UE 1 and UE 2 belong to the same IMS network, there is no need to perform the above-mentioned interaction between the network elements in the originating IMS network and the network elements in the terminating IMS network.
  • the IMS data network is a traffic-exempt data network.
  • the PS network is the transmission network between the terminal device and the IMS network. From the perspective of the PS network, the IMS network is a service network. Since the IMS data network is a traffic-exempt data network, regardless of whether the traffic switch status of the terminal device is on or off, the PS network will not intercept the uplink traffic packets to the IMS network.
  • the traffic types of some DC applications may be configured as traffic exemption types, while the traffic types of some DC applications may be configured as non-traffic exemption types. Therefore, how to control the acquisition or use of DC applications still needs further study.
  • an embodiment of the present application provides a communication method for enabling a DC control network element to manage and control the acquisition or use of a DC application according to the traffic type of a data channel application and the traffic switch status of a communication device.
  • the communication method of the embodiment of the present application involves one or more communication devices (such as a first communication device and a second communication device), and one or more network elements (such as an IMS application server, an IMS communication control network element, and a DC control network element) in an IMS network to which the first communication device belongs.
  • the communication device may be the terminal device described above, for example, the first communication device may be UE 1 in the above text, and the second communication device may be UE 2 in the above text.
  • the first communication device and the second communication device may belong to different IMS networks, or may belong to the same IMS network. For example, if the first communication device and the second communication device belong to different IMS networks, then when the first communication device is an initiating user device and the second communication device is a called user device, the IMS network to which the first communication device belongs is the originating IMS network, and the IMS network to which the second communication device belongs is the terminating IMS network; when the first communication device is the called user device and the second communication device is the initiating user device, the IMS network to which the second communication device belongs is the originating IMS network, and the IMS network to which the first communication device belongs is the terminating IMS network.
  • FIG6 is a flow chart of a communication method according to an embodiment of the present application. As shown in FIG6 , the method includes the following steps:
  • the IMS application server obtains status information of a first communication device.
  • the status information of the first communication device is used to indicate the flow switch state of the first communication device, and the flow switch state is on or off.
  • the status information of the first communication device is the PSData Off tag of the first communication device.
  • the IMS application server can obtain the status information of the first communication device.
  • the first communication device can send the status information of the first communication device (such as the PSData Off tag) to the IMS application server when registering or re-registering.
  • the first communication device can send the PSData Off tag to the S-CSCF through a registration request message or a re-registration request message, and then the S-CSCF can send the PSData Off tag to the IMS application server based on the third-party registration process defined in the protocol (such as TS24.229), and the IMS application server can store the PSData Off tag.
  • the first communication device modifies the PSData Off tag, it can trigger the re-registration process and send the modified PSData Off tag to the IMS application server.
  • the IMS application server sends the status information of the first communication device to the data channel control network element; accordingly, the data channel control network element receives the status information of the first communication device and stores the status information of the first communication device, so as to subsequently accept or reject the request corresponding to the request information sent by the first communication device according to the status information of the first communication device.
  • the IMS application server receives a SIP message from the IMS communication control network element, and sends the status information of the first communication device to the data channel control network element according to the SIP message. That is, after receiving the SIP message, the IMS application server can send the status information of the first communication device to the data channel control network element.
  • the SIP message is used to manage a communication session between a first communication device and a second communication device, and the communication session is associated with a data channel.
  • the SIP message may be a variety of possible SIP messages, such as one or more of the following: a SIP invitation request message; a SIP invitation response message; a SIP re-invite request message; a SIP re-invite response message; a SIP update request message; a SIP update response message; a SIP goodbye (SIP BYE) message; a SIP notification (SIP NOTIFY) message; a SIP registration (SIP REGISTER) message; a SIP subscription (SIP SUBSCRIBE) message; a SIP public (SIP PUBLISH) message; a SIP cancel (SIP CANCEL) message; and a SIP message (SIP MESSAGE).
  • the IMS application server when it receives certain SIP messages, it can send a session event reporting message to the data channel control network element.
  • the session event reporting message is used to report the event of the communication session between the first communication device and the second communication device.
  • the IMS application server receives a SIP invitation request message from the IMS communication control network element, it sends a session event reporting message to the data channel control network element.
  • the session event reporting message is used to report to the data channel control network element that the IMS AS has received the SIP invitation request message. Therefore, as a possible implementation, the IMS application server can send the first communication device to the data channel control network element through the session event reporting message.
  • the status information of the device that is, the session event reporting message includes the status information of the first communication device.
  • the IMS application server may also send the status information of the first communication device to the data channel control network element through other possible messages, and this embodiment of the present application does not limit this.
  • the first communication device sends request information to the data channel control network element; correspondingly, the data channel control network element receives the request information from the first communication device.
  • the request information is used to request to obtain a data channel application, or to download a data channel application, or to request an installation package of a data channel application.
  • a boot data channel can be established between the first communication device and the data channel control network element, and then the first communication device can send a request information to the data channel control network element through the boot data channel to request to download the data channel application.
  • the request information is an HTTP acquisition request message, and the specific implementation can refer to S507 in Figure 5.
  • the request information is used to request the use of the data channel application, and the use of the data channel application may include establishing an application data channel corresponding to the data channel application.
  • the first communication device pre-caches the data channel application.
  • the first communication device may not need to request the acquisition of the data channel application, but directly request the establishment of an application data channel corresponding to the data channel application.
  • the first communication device determines to run the data channel application, it sends a request message to the data channel control network element to request the establishment of an application data channel corresponding to the data channel application.
  • the first communication device sending the request information to the data channel control network element may be a transit communication.
  • the first communication device may send a re-invite request message/update request message to the IMS application server, and the re-invite request message/update request message includes the media resource information of the application data channel supported by the first communication device.
  • the IMS application server may send a request message to the data channel control network element, and the request message is used to request the establishment of an application data channel corresponding to the data channel application, and the request message includes the media resource information of the application data channel supported by the first communication device.
  • the data channel control network element rejects the request corresponding to the request information or accepts the request corresponding to the request information according to the traffic type of the data channel application and the traffic switch state of the first communication device.
  • the data channel control network obtains a traffic exemption application whitelist, and the traffic exemption application whitelist includes multiple application identifiers, each application identifier is used to identify the data channel application identified as a traffic exemption type by the network side; based on the traffic exemption application whitelist including the identifier of the data channel application, the traffic type of the data channel application is determined to be a traffic exemption type; or, based on the traffic exemption application whitelist not including the identifier of the data channel application, the traffic type of the data channel application is determined to be a non-traffic exemption type.
  • the data channel control network element is a DCSF network element
  • the traffic exemption application whitelist is stored in the DCAR network element
  • the DCSF network element obtains the traffic exemption application whitelist from the DCAR network element.
  • the data channel control network element is a DCSF network element
  • the traffic exemption application whitelist is stored in the DCSF network element.
  • the data channel control network element determines that the traffic type of the data channel application is a non-traffic exemption type, the traffic switch state of the first communication device is closed, and the request corresponding to the request information of the data channel application is rejected.
  • the data channel control network element determines that the traffic type of the data channel application is a traffic exemption type, the traffic switch state of the first communication device is closed, and the request corresponding to the request information of the data channel application is accepted.
  • the data channel control network element can accept the request corresponding to the request information of the data channel application.
  • the request information is used to request the acquisition of the data channel application: As described in S603, the request information may be an HTTP acquisition request message. If the data channel control network element rejects the request corresponding to the request information, it sends a first response message to the first communication device (for example, through the guided data channel between the first communication device and the data channel control network element, the first response information is sent to the first communication device, and the first response information is an HTTP response message), and the first response information indicates that the request corresponding to the request information is rejected.
  • the first response information includes reason information, and the reason information is used to indicate that the reason for the rejection is that the traffic type of the data channel application is a non-traffic exemption type. Optionally, the reason information is also used to indicate that the reason for the rejection is that the traffic type of the data channel application does not match the traffic switch state of the first communication device.
  • the data channel control network element accepts the request corresponding to the request information, it sends a second response information to the first communication device (for example, through the guided data channel between the first communication device and the data channel control network element, the second response information is sent to the first communication device, and the second response information is an HTTP response message), and the second response information indicates that the request corresponding to the request information is accepted.
  • the second response information includes an installation package of the data channel application.
  • the request information is used to request the use of the data channel application: As described in S603, the request information includes the media resource information of the application data channel supported by the first communication device. If the data channel control network element rejects the request corresponding to the request information, it sends a request to the IMS application server. A first response message is sent, and the first response message indicates that the request corresponding to the request message is rejected. For example, the first response message instructs the IMS application server to set the port information of the application data channel supported by the first communication device to 0.
  • the first response message includes reason information, and the reason information is used to indicate that the reason for the rejection is that the traffic type of the data channel application is a non-traffic exemption type; optionally, the reason information is also used to indicate that the reason for the rejection is that the traffic type of the data channel application does not match the traffic switch state of the first communication device.
  • the reason information can be sent to the first communication device via a SIP response message; optionally, the SIP response message includes indication information of failure to establish the application data channel, such as the port information of the application data channel in the SIP response message is 0, which is used to indicate that the application data channel failed to be established.
  • the IMS application server determines that it needs to interact with the peer IMS network (for example, the re-invite request message/update request message received by the IMS application server in S510 requests to establish other channels between the first communication device and the second communication device in addition to requesting to establish an application data channel between the first communication device and the second communication device), then after receiving the first response information, the IMS application server can continue to execute the subsequent process, and after executing the subsequent process, send the reason information to the first communication device through a SIP response message.
  • the SIP response message can be a response message to the re-invite request message/update request message received by the IMS application server in S510.
  • the data channel control network element accepts the request corresponding to the request information, it sends a second response information to the IMS application server, and the second response information indicates that the request corresponding to the request information is accepted.
  • the second response information includes media resource information for establishing an application data channel corresponding to the data channel application, see the description in FIG5.
  • the IMS application server can execute subsequent processes, and specifically refer to the prior art.
  • the process illustrated in FIG. 6 above is based on an example in which the IMS application server sends the status information of the first communication device to the data channel control network element.
  • the data channel control network element may also obtain the status information of the first communication device in other ways, and the embodiments of the present application are not limited to this.
  • the DC application is managed by the data channel control network element. Since the data channel control network element communicates with other network elements based on a service-oriented interface, that is, the data channel control network element does not receive SIP messages for managing communication sessions, and the UE communicates with network elements in the IMS network through SIP messages. Therefore, the data channel control network element cannot obtain the UE status information (used to indicate whether the UE's traffic switch status is on or off) from the UE, which in turn causes the data channel control network element to be unable to control the acquisition or use of the DC application based on the UE status information and the traffic type of the DC application (i.e., traffic exemption type or non-traffic exemption type).
  • the traffic type of the DC application i.e., traffic exemption type or non-traffic exemption type
  • the IMS application server can send the status information of the first communication device to the data channel control network element, so that the data channel control network element can control the acquisition or use of the DC application based on the traffic switch status of the first communication device and the traffic type of the DC application, thereby saving bandwidth resources of the operator network.
  • each network element may include a hardware structure and/or software module corresponding to the execution of each function.
  • each network element may include a hardware structure and/or software module corresponding to the execution of each function.
  • the embodiments of the present application can be implemented in the form of hardware or a combination of hardware and computer software. Whether a function is executed in hardware or in a computer software-driven hardware manner depends on the specific application and design constraints of the technical solution. Professional and technical personnel can use different methods to implement the described functions for each specific application, but such implementation should not be considered to exceed the scope of this application.
  • the embodiment of the present application can divide the IMS application server and the DC control network element into functional units according to the above method example.
  • each functional unit can be divided according to each function, or two or more functions can be integrated into one unit.
  • the above integrated unit can be implemented in the form of hardware or in the form of software functional units.
  • FIG7 shows a possible exemplary block diagram of the device involved in the embodiments of the present application.
  • the device 700 may include: a processing unit 702 and a communication unit 703.
  • the processing unit 702 is used to control and manage the actions of the device 700.
  • the communication unit 703 is used to support the communication between the device 700 and other devices.
  • the communication unit 703 is also called a transceiver unit, and may include a receiving unit and/or a sending unit, which are respectively used to perform receiving and sending operations.
  • the device 700 may also include a storage unit 701 for storing program code and/or data of the device 700.
  • the device 700 may be a data channel control network element in the above embodiment, or may be a component (such as a circuit or a chip) disposed in the data channel control network element.
  • the processing unit 702 may support the device 700 in executing the actions of the data channel control network element in each method example above.
  • the processing unit 702 mainly executes the internal actions of the data channel control network element in the method example, and the communication unit 703 may support the communication between the device 700 and other devices.
  • the communication unit 703 is used to: receive request information from the first communication device, the request information is used to request to obtain the data channel application or request to use the data channel application; the processing unit 702 is used to: The traffic type and the traffic switch state of the first communication device reject the request corresponding to the request information or accept the request corresponding to the request information; wherein, the traffic type is a traffic exemption type or a non-traffic exemption type, and the traffic switch state is open or closed.
  • the processing unit 702 is specifically used to: determine that the traffic type is a non-traffic exemption type and the traffic switch state is closed; and send a first response message, wherein the first response message indicates that the request corresponding to the request information is rejected.
  • the processing unit 702 is specifically used to: determine that the traffic type is a traffic exemption type and the traffic switch state is closed; and send a second response message, wherein the second response message indicates acceptance of the request corresponding to the request message.
  • the first response information includes reason information, and the reason information is used to indicate that the reason for the rejection is that the traffic type of the data channel application is a non-traffic exemption type.
  • the request information is used to request acquisition of the data channel application, and the second response information includes an installation package of the data channel application; or, the request information is used to request use of the data channel application, and the second response information includes media resource information for establishing an application data channel corresponding to the data channel application.
  • the communication unit 703 is further used to: receive status information from an Internet Protocol Multimedia Subsystem IMS application server, where the status information is used to indicate the flow switch status.
  • the communication unit 703 is further used to: receive a session event reporting message from the IMS application server, where the session event reporting message includes the state information.
  • the status information includes a packet switched data interruption flag.
  • the processing unit 702 is also used to: obtain a traffic exemption application whitelist, the traffic exemption application whitelist including multiple application identifiers, each application identifier being used to identify a data channel application identified as a traffic exemption type by the network side; based on the traffic exemption application whitelist including the identifier of the data channel application, determine that the traffic type of the data channel application is the traffic exemption type; or, based on the traffic exemption application whitelist not including the identifier of the data channel application, determine that the traffic type of the data channel application is the non-traffic exemption type.
  • the first communication device is a calling party user equipment, and the data channel control network element is a network element in an originating IMS network; or, the first communication device is a called party user equipment, and the data channel control network element is a network element in a terminating IMS network.
  • the apparatus 700 may be the IMS application server in the above embodiment, or may be a component (such as a circuit or a chip) disposed in the IMS application server.
  • the processing unit 702 may support the apparatus 700 in executing the actions of the IMS application server in each method example above.
  • the processing unit 702 mainly executes the internal actions of the IMS application server in the method example, and the communication unit 703 may support the communication between the apparatus 700 and other devices.
  • the processing unit 702 is used to: obtain status information of the first communication device, the status information is used to indicate the flow switch status of the first communication device, and the flow switch status is on or off;
  • the communication unit 703 is used to: send the status information to the data channel control network element, the status information is used to accept or reject the request corresponding to the request information sent by the first communication device, and the request information is used to request to obtain the data channel application or request to use the data channel application.
  • the communication unit 703 is further used to: receive a registration request message or a re-registration request message from the first communication device, and the registration request message or the re-registration request message includes the status information.
  • the communication unit 703 is also used to: receive a session initiation protocol SIP message from an IMS communication control network element, the SIP message being used to manage a communication session between the first communication device and the second communication device, the communication session being associated with a data channel; and send the status information to the data channel control network element according to the SIP message.
  • the communication unit 703 is further used to: send a session event reporting message to the data channel control network element, and the session event reporting message includes the status information.
  • the request information is used to request the use of the data channel application; the communication unit 703 is also used to: receive a first response message from the data channel control network element, the first response information indicating a rejection of the request corresponding to the request information; wherein the first response information includes reason information, and the reason information is used to indicate that the reason for the rejection is that the traffic type of the data channel application is a non-traffic exemption type.
  • the request information is used to request the use of the data channel application; the communication unit 703 is also used to: receive a second response information from the data channel control network element, the second response information indicating acceptance of the request corresponding to the request information; the second response information includes media resource information for establishing an application data channel corresponding to the data channel application.
  • the first communication device is a calling party user equipment
  • the IMS application server is a network element in an originating IMS network
  • the data channel control network element is a network element in an originating IMS network
  • the first communication device is a called party user equipment.
  • the IMS application server is a network element that terminates the IMS network
  • the data channel control network element is a network element that terminates the IMS network.
  • each unit in the above device can be fully or partially integrated into one physical entity, or they can be physically separated.
  • the units in the device can all be implemented in the form of software calling through processing elements; they can also be all implemented in the form of hardware; some units can also be implemented in the form of software calling through processing elements, and some units can be implemented in the form of hardware.
  • each unit can be a separately established processing element, or it can be integrated in a certain chip of the device.
  • it can also be stored in the memory in the form of a program, and called and executed by a certain processing element of the device. The function of the unit.
  • processing element described here can also be a processor, which can be an integrated circuit with signal processing capabilities.
  • each operation of the above method or each unit above can be implemented by an integrated logic circuit of hardware in the processor element or in the form of software calling through a processing element.
  • the unit in any of the above devices may be one or more integrated circuits configured to implement the above method, such as one or more application specific integrated circuits (ASIC), or one or more digital singnal processors (DSP), or one or more field programmable gate arrays (FPGA), or a combination of at least two of these integrated circuit forms.
  • ASIC application specific integrated circuits
  • DSP digital singnal processors
  • FPGA field programmable gate arrays
  • the unit in the device can be implemented in the form of a processing element scheduler
  • the processing element can be a processor, such as a general-purpose central processing unit (CPU), or other processors that can call programs.
  • CPU general-purpose central processing unit
  • these units can be integrated together and implemented in the form of a system-on-a-chip (SOC).
  • the above unit for receiving is an interface circuit of the device, which is used to receive signals from other devices.
  • the receiving unit is an interface circuit of the chip used to receive signals from other chips or devices.
  • the above unit for sending is an interface circuit of the device, which is used to send signals to other devices.
  • the sending unit is an interface circuit of the chip used to send signals to other chips or devices.
  • Device 800 may be the IMS AS or DC control network element in the above embodiments, and is used to implement the functions of the IMS AS or DC control network element in the above embodiments.
  • the apparatus 800 may include a processor 801, a memory 802, and an interface circuit 803.
  • the processor 801 may be used to process the communication protocol and the communication data, and to control the apparatus 800.
  • the memory 802 may be used to store programs and data, and the processor 801 may execute the method performed by the apparatus 800 in the embodiment of the present application based on the program.
  • the interface circuit 803 may be used for the apparatus 800 to communicate with other devices, and the communication may be wired communication or wireless communication, and the interface circuit may be, for example, a service-oriented interface.
  • the above memory 802 may also be externally connected to the device 800, in which case the device 800 may include an interface circuit 803 and a processor 801.
  • the above interface circuit 803 may also be externally connected to the device 800, in which case the device 800 may include a memory 802 and a processor 801.
  • the device 800 may include a processor 801.
  • the device 800 shown in FIG8 can implement each process related to the device 800 in the above method embodiment.
  • the operations and/or functions of each module in the device 800 shown in FIG8 are respectively to implement the corresponding processes in the above method embodiment.
  • system and “network” in the embodiments of the present application can be used interchangeably.
  • “At least one” refers to one or more, and “multiple” refers to two or more.
  • “And/or” describes the association relationship of the associated objects, indicating that there can be three relationships, for example, A and/or B, which can represent: the existence of A alone, the existence of A and B at the same time, and the existence of B alone, where A and B can be singular or plural.
  • the character “/” generally indicates that the associated objects before and after are in an “or” relationship.
  • “At least one of the following (individuals)” or similar expressions thereof refer to any combination of these items, including any combination of single items (individuals) or plural items (individuals).
  • At least one of A, B or C includes A, B, C, AB, AC, BC or ABC
  • at least one of A, B and C can also be understood to include A, B, C, AB, AC, BC or ABC.
  • the ordinal words such as “first” and “second” mentioned in the embodiments of the present application are used to distinguish multiple objects, and are not used to limit the order, timing, priority or importance of multiple objects.
  • the embodiments of the present application may be provided as methods, systems, or computer program products. Therefore, the present application may adopt the form of a complete hardware embodiment, a complete software embodiment, or an embodiment in combination with software and hardware. Moreover, the present application may adopt the form of a computer program product implemented on one or more computer-usable storage media (including but not limited to disk storage, optical storage, etc.) that contain computer-usable program code.
  • a computer-usable storage media including but not limited to disk storage, optical storage, etc.
  • These computer program instructions may also be stored in a computer-readable memory that can direct a computer or other programmable data processing device to work in a specific manner, so that the instructions stored in the computer-readable memory produce a manufactured product including an instruction device that implements the functions specified in one or more processes in the flowchart and/or one or more boxes in the block diagram.
  • These computer program instructions may also be loaded onto a computer or other programmable data processing device so that a series of operational steps are executed on the computer or other programmable device to produce a computer-implemented process, whereby the instructions executed on the computer or other programmable device provide steps for implementing the functions specified in one or more processes in the flowchart and/or one or more boxes in the block diagram.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Multimedia (AREA)
  • Business, Economics & Management (AREA)
  • General Business, Economics & Management (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

La présente demande concerne le domaine technique des communications. Un procédé de communication, un appareil et un système sont fournis. Le procédé comprend les étapes suivantes : un élément de réseau de commande de canal de données reçoit des informations de demande en provenance d'un premier dispositif de communication, les informations de demande étant utilisées pour demander l'acquisition d'une application de canal de données ou de demander l'utilisation d'une application de canal de données ; et, en fonction du type de trafic de l'application de canal de données et d'un état de commutation de trafic du premier dispositif de communication, rejeter la demande correspondant aux informations de demande ou accepter la demande correspondant aux informations de demande, le type de trafic étant un type d'exemption de trafic ou un type de non-exemption de trafic, et l'état de commutation de trafic étant allumé ou éteint. Ainsi, selon le type de trafic d'applications de canal de données et l'état de commutation de trafic du premier dispositif de communication, l'élément de réseau de commande de canal de données gère et commande l'acquisition ou l'utilisation des applications de canal de données, ce qui permet d'éviter le gaspillage de ressources de bande passante de réseaux d'opérateurs provoqués par l'acceptation d'informations de demande pour des applications de canal de données de type de non-exemption de trafic lorsque le commutateur de trafic du premier dispositif de communication est dans un état éteint.
PCT/CN2024/131062 2023-12-06 2024-11-08 Procédé, appareil et système de communication Pending WO2025118917A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN202311665820.8A CN120111039A (zh) 2023-12-06 2023-12-06 一种通信方法、装置及系统
CN202311665820.8 2023-12-06

Publications (1)

Publication Number Publication Date
WO2025118917A1 true WO2025118917A1 (fr) 2025-06-12

Family

ID=95890454

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2024/131062 Pending WO2025118917A1 (fr) 2023-12-06 2024-11-08 Procédé, appareil et système de communication

Country Status (2)

Country Link
CN (1) CN120111039A (fr)
WO (1) WO2025118917A1 (fr)

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2022262729A1 (fr) * 2021-06-15 2022-12-22 中国移动通信有限公司研究院 Procédé et appareil pour établir un canal de données, et dispositif, système de commande et support de stockage
CN116830669A (zh) * 2023-04-12 2023-09-29 北京小米移动软件有限公司 数据业务处理的方法、装置和计算机存储介质
CN117062110A (zh) * 2022-05-06 2023-11-14 中国移动通信有限公司研究院 信息处理方法、装置、通信设备和存储介质

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2022262729A1 (fr) * 2021-06-15 2022-12-22 中国移动通信有限公司研究院 Procédé et appareil pour établir un canal de données, et dispositif, système de commande et support de stockage
CN117062110A (zh) * 2022-05-06 2023-11-14 中国移动通信有限公司研究院 信息处理方法、装置、通信设备和存储介质
CN116830669A (zh) * 2023-04-12 2023-09-29 北京小米移动软件有限公司 数据业务处理的方法、装置和计算机存储介质

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
LEOPOLD MURHAMMER, DEUTSCHE TELEKOM, KPN, ORANGE, VODAFONE, KDDI: "Update on conclusion of KI#1.", 3GPP DRAFT; S2-2300280; TYPE PCR; FS_NG_RTC, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. SA WG2, no. Online; 20230116 - 20230120, 6 January 2023 (2023-01-06), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France, XP052231757 *

Also Published As

Publication number Publication date
CN120111039A (zh) 2025-06-06

Similar Documents

Publication Publication Date Title
JP5363461B2 (ja) グループ呼機能の問い合わせ
US11431774B2 (en) Method, user equipment and application server for adding media stream of multimedia session
EP4391611B1 (fr) Procédé et appareil de transmission d'informations
US20250202958A1 (en) Communication method, apparatus, and system
CN101360091B (zh) 一种实现会话初始协议终端入会的装置、系统和方法
CN103379096B (zh) 因特网与运营商网络业务共享方法、服务方及网页网关
EP4351103B1 (fr) Procédés de traitement des appels, appareil et support de stockage lisible par ordinateur
CN100495973C (zh) 用于一键通服务的方法和系统
US7953123B2 (en) Method and system for controlling the establishment of communications channels for allowing transmission of multimedia information
WO2023016172A1 (fr) Procédé, appareil et système de traitement d'appel
CN116633905A (zh) 一种通信方法、装置及通信系统
KR20240062604A (ko) 이동 통신 시스템에서 데이터 채널 응용 제공 방법 및 장치
EP3641262A1 (fr) Procédé et dispositif de communication, serveur d'application, équipement utilisateur et système
US20260025416A1 (en) Information transfer method, apparatus, and system
CN105122761B (zh) 基于分组的呼叫的附加媒体会话的本地控制
JP2010516131A (ja) 電話ベースのウェブサーバを発見する方法及び、当該方法に関連する電子機器とコンピュータプログラム
JP4078381B2 (ja) プッシュトゥートークのための方法及び装置
KR100727069B1 (ko) Ｓｉｐ 기반의 무선 패킷 교환망 시스템에서의 타망 연동방법 및 그 시스템
WO2025118917A1 (fr) Procédé, appareil et système de communication
EP4651463A1 (fr) Procédé et dispositif d'établissement d'un canal de données dans un système de communication sans fil
WO2025167808A1 (fr) Procédé et appareil d'établissement de canal de données
WO2025066513A1 (fr) Procédé et appareil de communication, et système de communication
WO2025189819A1 (fr) Procédé et appareil de communication
KR100706339B1 (ko) Ｓｉｐ 기반의 무선 패킷 교환망 시스템에서의 타망 연동방법 및 그 시스템
WO2024140041A1 (fr) Procédé de commande à distance et appareil de communication

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 24899559

Country of ref document: EP

Kind code of ref document: A1