Communication method, device and system

Abstract

The invention relates to the technical field of communication, and discloses a communication method, device and system. The method comprises: a data channel control network element receiving request information from a first communication device, the request information being used for requesting to acquire a data channel application or requesting 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, rejecting the request corresponding to the request information or receiving the request corresponding to the request information; wherein the flow type is a flow exemption type or a non-flow exemption type, and the state of the flow switch is on or off. Thus, the data channel control network element manages and controls acquisition or use of the data channel application according to the traffic type of the data channel application and the traffic switch state of the first communication device, so that the data channel application is prevented from being acquired or used when the traffic switch of the first communication device is in a closed state. And accepting request information of a non-traffic exempt type data channel application causes waste of bandwidth resources of an operator network.

Description

Technical Field

[0001] The present application relates to the field of communication technology, and in particular to a communication method, device and system. Background Art

[0002] 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, it is used to transmit the data of DC applications (which can be any type of data, such as text and pictures), so as to achieve real-time interaction, screen sharing, overlay of augmented reality (AR), and even a fully immersive experience with synchronization of hearing, vision, touch, etc. in the IMS communication session process (such as audio and video call process).

[0003] Different DC applications can have different traffic types according to business needs. For example, 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. Summary of the invention

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

[0005] In a first aspect, an embodiment of the present application provides 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). Taking the application of this method to a data channel control network element as an example, in this 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.

[0006] In this way, 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.

[0007] In one possible design, based on the traffic type of the data channel application and the traffic switch status of the first communication device, 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.

[0008] In one possible design, based on the traffic type of the data channel application and the traffic switch status of the first communication device, 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.

[0009] In one possible design, 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.

[0010] In one possible design, 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.

[0011] In this way, by sending the reason information, the first communication device is informed of the reason for the rejection.

[0012] In one possible design, 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.

[0013] In one possible design, 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.

[0014] In a possible design, 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.

[0015] In one possible design, the status information includes a packet switched data interruption flag.

[0016] In one possible design, 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.

[0017] In one possible design, 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.

[0018] In the second aspect, 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). Taking the application of this method to an IMS application server as an example, in this method, 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.

[0019] In one possible design, 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.

[0020] In one possible design, 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.

[0021] In one possible design, 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.

[0022] In one possible design, 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.

[0023] In one possible design, 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.

[0024] In one possible design, 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.

[0025] In one possible design, the first communication device is a calling party user equipment, the IMS application server is a network element in an originating IMS network, 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, the IMS application server is a network element in a terminating IMS network, and the data channel control network element is a network element in a terminating IMS network.

[0026] In a third aspect, an embodiment of the present application provides an 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, and 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, and the request information is used to request to obtain a data channel application or to request to use 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.

[0027] In a fourth aspect, the present application provides a communication device, which has the function of implementing the first aspect or the second aspect mentioned above. For example, the communication device includes a module or unit or means corresponding to the operations involved in the first aspect or the second aspect mentioned above. The module or unit or means can be implemented by software, or by hardware, or the corresponding software can be implemented by hardware.

[0028] In a possible design, 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.

[0029] In one possible design, 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.

[0030] In one possible design, the communication device includes a processor and a memory, and 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.

[0031] In one possible design, 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.

[0032] It can be understood that in the fourth aspect above, the processor can be implemented by hardware or by software. When implemented by hardware, 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. In addition, 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.

[0033] In a fifth aspect, 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.

[0034] In a sixth aspect, the present application provides a computer-readable storage medium, in which computer-readable instructions are stored. When 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.

[0035] In a seventh aspect, the present application provides a computer program product. When a computer reads and executes the computer program product, the computer executes the method in any possible design of the first to third aspects above.

[0036] In an eighth aspect, 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. BRIEF DESCRIPTION OF THE DRAWINGS

[0037] Figure 1 A schematic diagram of a network architecture provided for an embodiment of the present application;

[0038] Figure 2 A schematic diagram of another network architecture provided in an embodiment of the present application;

[0039] Figure 3 A schematic diagram of a data channel protocol stack provided in an embodiment of the present application;

[0040] Figure 4 A flowchart of an application for obtaining a data channel provided in an embodiment of the present application;

[0041] Figure 5A schematic diagram of a process for UE 1 and UE 2 to communicate through a data channel provided in an embodiment of the present application;

[0042] Figure 6 A flow chart corresponding to the communication method provided in the embodiment of the present application;

[0043] Figure 7 A possible exemplary block diagram of the device involved in the embodiments of the present application;

[0044] Figure 8 A possible structural diagram of the device involved in the embodiments of the present application. DETAILED DESCRIPTION

[0045] In order to make the purpose, technical solutions and advantages of the present application clearer, the present application will be further described in detail below with reference to the accompanying drawings. The specific operating methods in the method embodiments can also be applied to device embodiments or system embodiments. In the various embodiments of the present application, if there is no special description and logical conflict, the terms and / or descriptions between different embodiments are consistent and can be referenced to each other, and the technical features in different embodiments can be combined to form new embodiments according to their inherent logical relationships.

[0046] It is to be understood that the various numbers involved in the present application are only for the convenience of description and are not intended to limit the scope of the present application. The size of the sequence number of the above-mentioned processes does not mean the order of execution, and the order of execution of each process should be determined by its function and inherent logic. The terms "first", "second" and other various terminology labels (if any) in the specification and claims and drawings of the present application are used to distinguish similar objects, and are not necessarily used to describe a specific order or sequence. It should be understood that the data used in this way can be interchangeable where appropriate, so that the embodiments described here can be implemented in an order other than the content illustrated or described here. In addition, the terms "including" and "having" and any of their variations are intended to cover non-exclusive inclusions, such as processes, methods, systems, products or equipment that include a series of steps or units, which are not necessarily limited to those steps or units that are clearly listed, but may include other steps or units that are not clearly listed or inherent to these processes, methods, products or equipment.

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

[0048] Combine the following Figure 1 The following example illustrates a communication system 100 provided in an embodiment of the present application. 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. Figure 1 The network elements (or functional network elements, functional entities, nodes, devices, etc.) shown in FIG. 1 are briefly introduced as follows:

[0049] 1. Terminal equipment: 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. For example, 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. In terms of product form, the terminal equipment can include handheld devices, vehicle-mounted devices, wearable devices or computing devices with communication functions. Exemplarily, the terminal device may be a mobile phone, a tablet computer, a computer with a 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 a smart grid, a wireless terminal in transportation safety, a wireless terminal in a smart city, a wireless terminal in a smart home, a cellular phone, a cordless phone, a SIP phone, a wireless local loop (WLL) station, a personal digital assistant (PDA), a handheld device with a wireless communication function, other processing devices connected to a wireless modem, a terminal in an Internet of Things (IoT) system, a desktop computer, or a 3rd Generation Partnership Project (3GPP) system. UE defined in the 3GPP (3rd Generation Partnership Project) standard specifications, etc., are not restricted.

[0050] In the network architecture provided in the embodiment of the present application, different UEs can make IMS calls through the IMS network. For example, Figure 1UE 1 and UE 2 in the figure can make an IMS call through the IMS network, wherein UE 2 can be referred to as the opposite device of the IMS call made by UE 1, and similarly, UE 1 can be referred to as the opposite device of the IMS call made by UE 2. Assuming that UE 1 is the calling user equipment and UE 2 is the called user equipment, the IMS network providing services for UE 1 can be referred to as the originating IMS network (originating IMS), and the IMS network providing services for UE 2 can be referred to as the terminating IMS network (terminatingIMS). In addition, for UE 1, the originating IMS network is the local IMS network (local IMS), and the terminating IMS network is the remote IMS network (remote IMS); for UE 2, the terminating IMS network is the local IMS network, and the originating IMS network is the remote IMS network. It can be understood that the network element architecture inside the terminating IMS network is similar to the network element architecture inside the originating IMS network. For the sake of simplicity, the network element architecture inside the remote IMS network is not shown in the figure.

[0051] 2. Call session control function (CSCF) network element: 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. For the sake of convenience, the CSCF network element in this application is referred to as "CSCF". Among them, 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.

[0052] As an example and not a limitation, CSCF is divided into proxy CSCF (P-CSCF), interrogating CSCF (I-CSCF), serving CSCF (S-CSCF), etc. according to its function. Among them, 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 it.

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

[0054] 3. IMS access media gateway (AGW): IMS AGW can provide IMS network access gateway and media gateway functions.

[0055] 4. Data channel server (DCS): DCS can be divided into two logical functional entities: data channel signaling function (DCSF) network element and media function (MF) network element. Among them, the MF network element is used to provide media resource management functions, including media resource management of data channels, and 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 this.

[0056] 5. Data channel application repository (DCAR): DCAR is a repository for storing data channel applications (DC App). After a developer completes the development of a DCApp, he uploads it to the operator's DCS, which then saves it to DCAR. When needed, DCS downloads DCApp from DCAR to the local computer for subsequent processing.

[0057] The data channel control network element (ie, DC control network element) in the embodiment of the present application includes a DCSF and optionally also includes a DCAR.

[0058] 6. Home Subscriber Server (HSS): HSS is a database for storing user information in IMS, where users save user data. As an example and not a limitation, user data may include information about data channel services that users have signed a contract with an operator to use.

[0059] 7. IMS application server (AS): 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. In addition, the terminal device is connected to the IMS AS in communication, and the IMS AS can establish a data channel for the terminal device. Exemplarily, the IMS AS can be a multimedia telephony application server (MMTEL AS) or a telephony application server (TAS).

[0060] 8. Data channel application server (DC AS): DC AS is used to provide data channel service 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).

[0061] 9. NEF network element: NEF network element is used to securely open various services of the 5GC network to third parties.

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

[0063] It can also be understood that the 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.

[0064] It is also understandable that the naming of the above network elements or devices is only defined for the convenience of distinguishing different functions and should not constitute any limitation to this application. This application does not exclude the possibility of using other names in 4G networks, 5G networks and other future networks. For example, in a 6G network, some or all of the above network elements may use the terminology in 4G / 5G, or may use other names.

[0065] based on Figure 1 The network architecture shown in the figure, in order to facilitate understanding of the technical solutions of the embodiments of the present application, some terms or concepts that may be involved in the embodiments of the present application are introduced here.

[0066] 1. Communication Session

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

[0068] Among them, communication services refer to services such as voice calls, video calls or data interactions between terminal devices as originating parties or terminating parties, and are connected to one or more other terminal devices through a communication network (such as an IMS network). Among them, the IMS network is an open system based on IP bearer and provides various multimedia services to users. The communication service can cover the entire process from the start of communication establishment (for example, dialing) to the end of communication in terms of time, or it 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 communication. The communication service can be a one-to-one communication service or a one-to-many (such as a conference) communication service; the embodiment of the present application takes a one-to-one communication service as an example, but the related schemes can be used for one-to-many communication services.

[0069] An IMS session can be understood as a logical connection between communication devices in a communication service. For example, 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. In specific applications, an IMS session can be negotiated (or established) based on the session initiation protocol (SIP) / session description protocol (SDP). It can be understood 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.

[0070] It can be understood that one communication service may correspond to at least one IMS session. Taking the communication service between UE1 and UE2 as an example, the communication service corresponds to one IMS session, such as the IMS session between UE1 and UE2. Taking the communication service between UE1, UE2 and UE3 as an example, 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.

[0071] It is understandable that in order to transmit various types of data, a channel for transmitting the corresponding type of data can be established based on the IMS session. Exemplarily, according to different data types, the channel can be divided into a media channel and a data channel. In some scenarios, the media channel can be further divided into an audio channel and a video channel. For example, in Figure 2In the example, UE 1 and UE 2 can communicate via an IMS network, and the channels established based on the IMS session between UE 1 and UE 2 include a data channel, an audio channel, and a video channel. It can be understood that Figure 2 This is only an example of an IMS session. In a specific application, 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.

[0072] In the embodiment of the present application, the audio channel can be used to transmit voice, and the video channel can be used to transmit video. The data channel is specifically described below.

[0073] 2. Data Channel

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

[0075] Exemplarily, according to the relationship between the data channel and the audio / video call, the data channel of the embodiment of the present application can be divided into at least the following types.

[0076] (1) During an IMS session, when an audio or video call is being made between the terminal device and another session participant (which may be another terminal device or a network element), there is also a data channel. The data channel at this time may be called an auxiliary data channel or a dependent data channel.

[0077] (2) During an IMS session, when there is only a data channel between the terminal device and other session participants, and no traditional voice call or video call exists, the data channel at this time can be called a standalone data channel or an independent data channel.

[0078] Whether it is an auxiliary data channel or an independent data channel, it can be used to transmit any type of application data between session participants. Exemplarily, 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.

[0079] (1) The application data transmitted by the data channel may be interactive application data (interactive data for short). Interactive application data may be application data used to support interactive operations (e.g., 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 (e.g., control instructions, control signals, or output files generated after the conversation participants perform the interactive operation, such as the number of "Likes" or the amount in a "Red Envelope"). It may also be data collected or stored by the terminal device, for example, data collected by the terminal device through an input / output (I / O) module, such as images or videos captured by a camera, voice collected by a microphone, text, symbols, or emoticons input by a keyboard, or data generated by actions such as clicking / sliding on a touch screen.

[0080] (2) The application data transmitted by the data channel may also be communication enhancement application data (communication enhancement data for short). Communication enhancement data may be 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 the sign language in a video call into text or voice. It may also be data superimposed on the audio call or video call, such as AR special effects images, etc. It may also be data independent of the audio call or video call, such as geographic location data, screen sharing data, etc.

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

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

[0083] As an example, data channels are divided into two types according to different uses: bootstrap data channel (BDC) and application data channel (ADC). BDC is used for terminal devices to obtain DC App from DCS. ADC is used to transmit interactive data generated by DC Apps running on both sides of the communication.

[0084] 3. IMS session protocol stack

[0085] In the embodiment of the present application, 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. As mentioned above, 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. For example, the protocol stack of the IMS session can be as follows: Figure 3 shown.

[0086] exist Figure 3 In the , 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). For the above channels, the protocols above UDP are different, which are explained below. For the audio channel or video channel, above UDP is the Real-time Transport Protocol (RTP) or RTP Control Protocol (RTCP), which can encapsulate the payload of voice, video or text, and above it is the conversational multimedia application, which is also above RTCP. For the data channel, above UDP is the Datagram Transport Layer Security (DTLS) protocol, above the DTLS protocol is the Stream Control Transmission Protocol (SCTP), above SCTP is the application data / application, and above the application data / application is the conversational multimedia application.

[0087] It can be understood that 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. In the embodiments of the present application, 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.

[0088] It is understandable that in the embodiment of the present application, the transport layer protocol stack of the data channel is not limited to Figure 3 The "UDP / DTLS / SCTP" protocol stack shown can also be other protocol stacks, such as: "TCP / DTLS / SCTP" protocol stack, "UDP / QUIC" (QUIC is the abbreviation of quick UDP internet connection) protocol stack, "UDP / SCTP" protocol stack, etc.

[0089] 4. Data channel application

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

[0091] Exemplarily, the data channel application involved in the embodiment of the present application can be a DC App in a 4G / 5G network. DCApp can transmit various data such as text, pictures, locations, files, etc. before and after the 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.

[0092] 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 other terminal device through the DC App except for voice calls or video calls. For example, UE 1 and UE 2 are in the same IMS communication session. Assume 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 phone. Then 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 other UE except for voice calls or video calls. The following is combined with Figure 4 The workflow shown briefly introduces the process of obtaining DC App on terminal devices. Figure 4 In the given example, UE 1 and UE 2 are taken as a calling party user equipment and a called party user equipment respectively for description.

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

[0094] ②. DCS stores DC App in DCAR.

[0095] ③. DCS downloads DC App from DCAR when needed.

[0096] ④. UE 1 establishes BDC with DCS and obtains the required DC App from DCS through BDC.

[0097] ⑤. UE 2 establishes BDC with DCS and obtains the required DC App from DCS through BDC.

[0098] ⑥. UE 1 and UE 2 establish ADC to transmit the interactive data of the DC App.

[0099] 5. Session event reporting message

[0100] In the embodiment of the present application, 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. For example, the events of a communication session may include one or more of the following:

[0101] The session establishment request event (SessionEstablishmentRequestEvent) indicates that the IMS AS receives a SIP invite request message.

[0102] The session establishment progress event (SessionEstablishmentProgressEvent) indicates that the IMS AS receives the SIP invite response message.

[0103] The session establishment success event (SessionEstablishmentSuccessEvent) indicates that the communication session is established successfully.

[0104] The session establishment failure event (SessionEstablishmentFailureEvent) indicates that the communication session establishment failed.

[0105] The media change request event (MediaChangeRequestEvent) 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 removal request event. The ADC establishment request event indicates that the IMS AS receives an ADC establishment request, and the ADC removal request event indicates that the IMS AS receives an ADC removal request.

[0106] The media change success event (MediaChangeSuccessEvent) indicates that the request to change the media resource is successful.

[0107] The media change failure event (MediaChangeFailureEvent) indicates that the request to change the media resource failed.

[0108] Session Termination Event: indicates the termination of a session.

[0109] It is understandable that the event of the communication session may also be other possible events, which is not limited in the embodiments of the present application.

[0110] 6. Packet switching data interruption

[0111] In order to enable users to clearly control the traffic sent or received, 3GPP introduced the packet switched data interruption (PSData Off) function. Among them, the PSData Off function of the terminal device corresponds to the flow switch of the terminal device. When the PSData Off function of the terminal device is activated, the flow switch state of the terminal device is closed. When the PSData Off function of the terminal device is closed or deactivated, the flow switch state of the terminal device is opened. Among them, the flow switch state of the terminal device can be set or changed by the user.

[0112] When the flow switch state of the terminal device is off, except for the services related to the PSData Off exemption service (i.e., PSData Off Exempt Service, which can be called flow exemption service), all other applications cannot access the PS network, please refer to 3GPP TS22.011 for details. Among them, the current protocol (such as 3GPP TS23.228) describes that the network can send a flow exemption service list to the terminal device when the terminal device registers, or it can also be configured to the terminal device in other ways.

[0113] In the embodiment of the present application, the type of application is a traffic exemption type or a non-traffic exemption type. Traffic exemption type applications can be called traffic exemption applications, or traffic exemption services; non-traffic exemption type applications can be called non-traffic exemption applications, or non-traffic exemption services. Among them, traffic 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-traffic 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. In other words, when the traffic switch state of the terminal device is off, traffic exemption type applications are allowed to access the PS network, that is, the terminal device is allowed to obtain or use traffic exemption type applications; while non-traffic exemption type applications are not allowed to access the PS network, that is, the terminal is not allowed to obtain or use non-traffic exemption type applications.

[0114] As mentioned above, the relevant terms are introduced. Figure 1 The illustrated network architecture describes a possible process to introduce a data channel between two communicating parties (eg, UE 1 and UE 2).

[0115] Among them, 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. Assuming that UE 1 is the calling party user equipment and UE 2 is the called party user equipment, for convenience, the network elements involved in the originating network in the embodiment of the present application are respectively recorded as IMS core 1, IMS AS1, and DCS1, and the network elements involved in the terminating network in the embodiment of the present application are respectively recorded as IMS core 2, IMS AS2, and DCS2. It can be understood that the above network elements are only used as examples, and the originating network and the terminating network may also include other network elements, which are not limited in this application; 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.

[0116] Figure 5 FIG. 1 is a flow chart of UE 1 and UE 2 communicating through a data channel. Figure 5 As shown, the process may include:

[0117] S501, UE 1 and UE 2 respectively establish a guided data channel with DCSF 1 and DCSF 2 through an initial invitation (INVITE) process; DCSF 1 and DCSF 2 obtain and save the association relationship between the calling number, the called number and the call identification (Call ID).

[0118] For example, when UE 1 and UE 2 need or want to communicate through a data channel application other than a voice call or a video call, UE 1 and UE 2 can establish a guided data channel with DCS 1 and DCS 2 respectively through an initial invitation process, so as to obtain a guided application through the guided data channel. Figure 5 As shown, UE 1 establishes a guided data channel #1 with DCS1 and a guided data channel #2 with DCS 2; UE 2 establishes a guided data channel #3 with DCS1 and a guided data channel #4 with DCS2.

[0119] For convenience, in the embodiment of the present application, the guided data channel between the UE and the originating DCSF (i.e., the DCSF of the originating network) is recorded as guided data channel No. 0 (i.e., the stream ID of the guided data channel = 0), and the guided data channel between the UE and the terminating DCSF (i.e., the DCSF of the terminating network) is recorded as guided data channel No. 100 (i.e., the stream ID of the guided data channel = 100). Therefore, guided data channel #1 and guided data channel #4 are guided data channel No. 0, and guided data channel #2 and guided data channel #3 are guided data channel No. 100. It can be understood that 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. For example, the guided data channel between the UE and the local DCSF can also be recorded as guided data channel No. 10 (i.e., stream ID = 10), and the guided data channel between the UE and the opposite DCSF can be recorded as guided data channel No. 110 (i.e., stream ID = 110), and the present application does not limit this.

[0120] DCSF 1 and DCSF 2 can respectively obtain and save the association between the calling number, the called number and the Call ID. For example, 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, the called number and the Call ID in the INVITE process. In addition, DCSF 1 also obtains the media resource information of the guided data channel #1 and the guided data channel #3, and DCSF 2 also obtains the media resource information of the guided data channel #2 and the guided data channel #4.

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

[0122] S502, UE 1 sends HTTP GET Request messages to DCSF 1 and DCSF 2 respectively, wherein the request URI of the HTTP GET Request message is the root directory, indicating that UE 1 requests to obtain the DC application list. Correspondingly, DCSF 1 and DCSF 2 receive the HTTP GET Request messages from UE 1 respectively.

[0123] S503, DCSF 1 and DCSF 2 respectively send HTTP response messages to UE 1, where the HTTP response messages include a DC application list. Correspondingly, UE 1 receives HTTP response messages from DCSF 1 and DCSF 2 respectively.

[0124] Exemplarily, 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 UE1 requests to obtain the DC application list on DCSF 1. In response to the HTTP get request message, 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. For convenience, 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.

[0125] Similarly, UE 1 obtains a bootstrap application (referred to as bootstrap application #2) on DCSF 2 from DCSF 2 through bootstrap data channel #2, where bootstrap application #2 includes a DC application list available to UE 1 on the termination network.

[0126] S504, 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, indicating that UE 2 requests to obtain the boot application. Correspondingly, DCSF 1 and DCSF 2 receive the HTTP get request messages from UE 2 respectively.

[0127] S505, DCSF 1 and DCSF 2 send HTTP response messages to UE 2 respectively, and the HTTP response messages include the boot application. Correspondingly, UE 2 receives the HTTP get response messages from DCSF 1 and DCSF 2 respectively.

[0128] It can be understood that S504 and S505 are similar to S502 and S503, respectively, and the specific process is not limited here. Through S504 and S505, 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.

[0129] It is understandable that the present application does not limit the execution order of S502 - S503 and S504 - S505.

[0130] S506, UE 1 determines to start application X, that is, determines that application X needs to be acquired.

[0131] Exemplarily, when UE 1 detects that the user has selected application X, UE 1 determines to start application X. For example, application X is any data channel application in the guide application #1 acquired by UE 1.

[0132] For example, 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 through pictures or texts, and the user can select any data channel application from the DC application list displayed on the screen. When the user selects application X, UE 1 determines to start application X. It can be understood that each DC application in the guide 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.

[0133] S507: UE 1 sends an HTTP get request message to DCSF 1. Correspondingly, DCSF 1 receives the HTTP get request message from UE 1.

[0134] Exemplarily, 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. For example, 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 (recorded as App ID-X), which is used to request to acquire the application X, or to request the installation package of application X.

[0135] It can be understood that the above is explained by taking the example of UE 1 obtaining application X during the IMS call establishment phase, but the present application is not limited to this. For example, UE 1 can also obtain application X after the IMS call is connected. In this case, 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).

[0136] S508: DCSF 1 sends an HTTP response message to UE 1. Correspondingly, UE 1 receives the HTTP response message from DCSF 1.

[0137] Exemplarily, after receiving the HTTP obtain request message from UE 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, carries the installation package of application X, in the HTTP response message.

[0138] Correspondingly, UE 1 receives the HTTP response message from DCSF 1, and obtains the installation package of application X from the HTTP response message.

[0139] S509: UE 1 runs application X, that is, uses application X.

[0140] Exemplarily, after acquiring application X, UE 1 runs application X. For example, UE 1 displays an HTML page corresponding to application X in a Web browser and executes a JavaScript script therein.

[0141] Further, 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 in addition to voice calls or video calls through application X. The following describes S510-S519 as an example.

[0142] S510, UE 1 sends a re-INVITE request message / update request message to IMS AS 1. Correspondingly, IMS AS 1 receives the re-INVITE request message / UPDATE request message from UE 1.

[0143] Exemplarily, after UE 1 executes the JavaScript script in application X, UE 1 is triggered 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.

[0144] The re-INVITE request message includes SDP Offer information, which 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). Optionally, the 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.

[0145] Optionally, 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.

[0146] S511, IMS AS1 reports media resource information of application data channels supported by UE1 to DCSF1.

[0147] S512, DCSF 1 allocates DC resources and instructs to update the SDP offer, and then IMS AS1 updates the SDP offer information.

[0148] Exemplarily, 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. Furthermore, 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.

[0149] S513, IMS AS1 sends a re-INVITE request message / UPDATE request message to UE 2. Correspondingly, UE 2 receives the re-INVITE request message / UPDATE request message from IMS AS1.

[0150] Exemplarily, after IMS AS1 updates the SDP offer information, it routes the re-INVITE request message / UPDATE request message to UE 2 through IMS core 1, IMS core 2, and IMS AS2. 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, and the updated SDPoffer information includes the information of application X as described in S510.

[0151] Optionally, at S514, UE 2 determines DCSF 1 according to application X information.

[0152] Exemplarily, after receiving the re-INVITE request message, 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 the APP ID-X. Optionally, 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.

[0153] S515, UE 2 sends an HTTP get request message to DCSF 1. Correspondingly, DCSF 1 receives the HTTP get request message from UE 2.

[0154] Exemplarily, UE 2 sends an HTTP acquisition request message to DCSF 1 through guided data channel #3 (i.e., guided data channel No. 100) according to the received information of application X, where the request URI (RequestURI) of the HTTP acquisition request message is App ID-X, for requesting to acquire application X.

[0155] S516: DCSF 1 sends an HTTP response message to UE 1. Correspondingly, UE 2 receives the HTTP response message from DCSF 1.

[0156] Exemplarily, after receiving the HTTP get request message from UE 2, 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.

[0157] Correspondingly, UE 2 receives the HTTP response message from DCSF 1, and obtains the installation package of application X from the HTTP response message.

[0158] S517: UE 2 runs application X.

[0159] Exemplarily, if UE 2 successfully obtains application X, UE 2 runs application X. For example, UE 2 displays an HTML page corresponding to application X in a Web browser and executes a JavaScript script therein.

[0160] S518, UE 2 sends a SIP response message to UE 1. Correspondingly, UE 1 receives the SIP response message from UE 2.

[0161] Exemplarily, UE 2 determines that it agrees to establish a corresponding application data channel with UE 1 according to the SDP Offer information (for example, UE 2 supports part or all of the media resource information in the media resource information provided by the SDP Offer information), and UE 2 successfully obtains application X and runs application X (that is, successfully executes S515-S517), then UE 2 sends a SIP response message for responding to the re-INVITE request message to UE 1, and at this time the SIP response message may be a 200OK response message.

[0162] The SIP response message includes SDP Answer information determined by UE 1 according to the SDP Offer information. The SDP Answer information includes media resource information of the application data channel supported (or willing to be used) by UE 2 in the media resource information provided by the SDP Offer information.

[0163] Optionally, in S519 , UE 1 sends an ACK message to UE 2. Correspondingly, UE 2 receives the ACK message from UE 1.

[0164] Exemplarily, after receiving the SIP response message from UE 2, UE 1 determines, based on the information carried in the SIP response message, that the media resource information negotiation is successful and UE 2 has successfully acquired application X. 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 application data channel No. 1000 carried in the SDP Answer information is not 0, UE 1 determines that the media resource information negotiation is successful and UE 2 has successfully acquired application X. Alternatively, UE 1 determines that the media resource information negotiation is successful and UE 2 has successfully acquired application X through other explicit indication information carried in the SIP response message.

[0165] In this case, UE 1 returns an ACK message to UE 2 to indicate successful message reception.

[0166] It is understandable that if UE 1 negotiates media resource information with UE 2 through an UPDATE process (ie, UE 1 sends an UPDATE request message in S510), UE 1 may not execute S519.

[0167] S520, UE 1 and UE 2 establish application data channel No. 1000.

[0168] Exemplarily, UE 1 and UE 2 establish a DTLS association (DTLS Association) and a SCTP association (SCTP Association) according to the negotiated media resource information, and allocate stream ID 1000 to application X, thereby establishing application data channel No. 1000 required by application X.

[0169] S521, application X on UE 1 and application X on UE 2 transmit additional communication information through application data channel No. 1000.

[0170] It is understandable that the above Figure 5In the illustrated process, the subsequent process is triggered by the calling party user equipment (i.e., UE 1) determining to start application X. In other possible examples, the process may also be triggered by the called party user equipment determining to start application Y (for example, application Y may be any DC application in the DC application list available to the called party user equipment on the terminating IMS network). In other words, the process illustrated in 5 above may also be applicable to the scenario of "UE 1 is the called party user equipment, UE 2 is the calling party user equipment, IMS core 1, IMS AS1, DCS 1 are network elements in the terminating IMS network, and IMS core 2, IMS AS2, DCS2 are network elements in the originating IMS network".

[0171] In addition, if UE 1 and UE 2 belong to the same IMS network, there is no need to perform the above-mentioned interaction between the network element in the originating IMS network and the network element in the terminating IMS network.

[0172] The above process introduces the data channel between UE 1 and UE 2. In the current standard, the IMS data network is a traffic-exempt data network. The PS network is a 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 state of the terminal device is on or off, the PS network will not intercept the uplink traffic packets to the IMS network.

[0173] However, different DC applications can have different traffic types according to business needs. For example, 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.

[0174] Based on this, 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.

[0175] Exemplarily, 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 the 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.

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

[0177] Figure 6 This is a flow chart corresponding to the communication method provided in the embodiment of the present application. Figure 6 As shown, the method comprises the following steps:

[0178] S601: The IMS application server obtains status information of a first communication device.

[0179] Here, the state 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. For example, the state information of the first communication device is the PSData Off tag of the first communication device.

[0180] There are multiple ways for the IMS application server to obtain the status information of the first communication device. One possible way is that 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. For example, 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. Each time 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.

[0181] S602, 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.

[0182] Exemplarily, 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.

[0183] The SIP message is used to manage a communication session between the first communication device and the second communication device, and the communication session is associated with a data channel. The SIP message can be a variety of possible SIP messages, for example, the SIP message can be 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 BYE message; a SIP NOTIFY message; a SIP REGISTER message; a SIP SUBSCRIBE message; a SIP PUBLISH message; a SIP CANCEL message; or a SIP MESSAGE.

[0184] As described above, when the IMS application server receives certain SIP messages, it can send a session event reporting message to the data channel control network element, and 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; for example, when 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, and 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 status information of the first communication device to the data channel control network element through the session event reporting message, that is, the session event reporting message includes the status information of the first communication device.

[0185] It is understandable that 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.

[0186] S603, 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.

[0187] Exemplarily, 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. For example, after a communication session between a first communication device and a second communication device is successfully established, 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. For example, the request information is an HTTP get request message, and the specific implementation can refer to Figure 5 S507 in.

[0188] Alternatively, the request information is used to request the use of a data channel application, and the use of a data channel application may include establishing an application data channel corresponding to the data channel application. For example, the first communication device has pre-cached the data channel application. In this case, 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. For example, after 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. Among them, the first communication device sending the request information to the data channel control network element may be a transit communication. For example, 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. Then, after receiving the re-invite request message / update request message, 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. For specific implementation, please refer to Figure 5 S509 to S511 in.

[0189] It can be understood that the above are two examples of request information, and the embodiments of the present application are not limited to this.

[0190] S604: 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.

[0191] Here, there are multiple ways for the data channel control network element to determine the type of data channel application. In one possible implementation, 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. For example, the data channel control network element is a DCSF network element, the traffic exemption application whitelist is stored in the DCAR network element, and the DCSF network element obtains the traffic exemption application whitelist from the DCAR network element. Or, the data channel control network element is a DCSF network element, and the traffic exemption application whitelist is stored in the DCSF network element.

[0192] In one possible implementation, 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. Alternatively, 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. In addition, optionally, when the traffic switch state of the first communication device is on, regardless of whether the traffic type of the data channel application is a non-traffic exemption type or a traffic exemption type, the data channel control network element can accept the request corresponding to the request information of the data channel application.

[0193] (1) 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.

[0194] If 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.

[0195] (2) 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 first response information to the IMS application server, and the first response information indicates the rejection of the request corresponding to the request information. For example, the first response information 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 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. Subsequently, 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 the 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 establish. For example, after receiving the first response information, if 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.

[0196] If 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. For example, the second response information includes media resource information for establishing an application data channel corresponding to the data channel application, see Figure 5 After receiving the second response information, the IMS application server may execute subsequent processes, with specific reference to the prior art.

[0197] It is understandable that the above Figure 6The illustrated process takes the example of the IMS application server sending the status information of the first communication device to the data channel control network element. In other embodiments, the data channel control network element may also obtain the status information of the first communication device in other ways, which is not limited in this embodiment of the present application.

[0198] In the embodiment of the present application, 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). Using the method provided in the embodiment of the present application, 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.

[0199] The above mainly introduces the solution provided by the embodiment of the present application from the perspective of network element interaction. It can be understood that in order to realize the above functions, each network element may include a hardware structure and / or software module corresponding to the execution of each function. Those skilled in the art should easily realize that, in combination with the units and algorithm steps of each example described in the embodiments disclosed in this document, 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.

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

[0201] In the case of an integrated unit, Figure 7 A possible exemplary block diagram of the device involved in the embodiments of the present application is shown. Figure 7As shown, the apparatus 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 apparatus 700. The communication unit 703 is used to support the communication between the apparatus 700 and other devices. Optionally, 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 apparatus 700 may also include a storage unit 701, which is used to store program codes and / or data of the apparatus 700.

[0202] (1) 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. Alternatively, 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.

[0203] For example, in one embodiment, the communication unit 703 is used to: receive request information from a first communication device, wherein the request information is used to request to obtain a data channel application or to request to use the data channel application; the processing unit 702 is used to: reject the request corresponding to the request information or accept 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; wherein the traffic type is a traffic exemption type or a non-traffic exemption type, and the traffic switch state is on or off.

[0204] In one possible design, 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.

[0205] In one possible design, 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.

[0206] In one possible design, 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.

[0207] In one possible design, 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.

[0208] In a possible design, 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.

[0209] In a possible design, 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.

[0210] In one possible design, the status information includes a packet switched data interruption flag.

[0211] In one possible design, 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.

[0212] In one possible design, 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.

[0213] (2) 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. Alternatively, 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.

[0214] For example, in one embodiment, 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.

[0215] In one possible design, 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.

[0216] In one possible design, 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.

[0217] In a possible design, 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.

[0218] In one possible design, 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.

[0219] In one possible design, 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.

[0220] In one possible design, the first communication device is a calling party user equipment, the IMS application server is a network element in an originating IMS network, 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, the IMS application server is a network element in a terminating IMS network, and the data channel control network element is a network element in a terminating IMS network.

[0221] It should be understood that the division of the units in the above device is only a division of logical functions. In actual implementation, they can be fully or partially integrated into one physical entity, or they can be physically separated. And 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. For example, each unit can be a separately established processing element, or it can be integrated in a certain chip of the device. In addition, 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. In addition, all or part of these units can be integrated together, or they can be implemented independently. The processing element described here can also be a processor, which can be an integrated circuit with signal processing capabilities. In the implementation process, 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.

[0222] In one example, 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. For another example, when 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. For another example, these units can be integrated together and implemented in the form of a system-on-a-chip (SOC).

[0223] The above unit for receiving is an interface circuit of the device, which is used to receive signals from other devices. For example, when the device is implemented in the form of a chip, 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. For example, when the device is implemented in the form of a chip, the sending unit is an interface circuit of the chip used to send signals to other chips or devices.

[0224] refer to Figure 8, is a schematic diagram of a structure of a device provided in an embodiment of the present application. Device 800 may be an IMS AS or DC control network element in the above embodiment, and is used to implement the functions of the IMS AS or DC control network element in the above embodiment.

[0225] like Figure 8 As shown, the device 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 communication data, and control the device 800. The memory 802 may be used to store programs and data, and the processor 801 may execute the method performed by the device 800 in the embodiment of the present application based on the program. The interface circuit 803 may be used for the device 800 to communicate with other devices, and the communication may be wired communication or wireless communication. The interface circuit may be, for example, a service-oriented interface.

[0226] 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. When both the interface circuit 803 and the memory 802 are externally connected to the device 800, the device 800 may include a processor 801.

[0227] Figure 8 The device 800 shown can implement each process related to the device 800 in the above method embodiment. Figure 8 The operations and / or functions of each module in the device 800 are respectively for implementing the corresponding processes in the above method embodiment. For details, please refer to the description in the above method embodiment. To avoid repetition, the detailed description is appropriately omitted here.

[0228] The terms "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). For example, "at least one of A, B or C" includes A, B, C, AB, AC, BC or ABC, and "at least one of A, B and C" can also be understood to include A, B, C, AB, AC, BC or ABC. And, unless otherwise specified, 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.

[0229] Those skilled in the art will appreciate that 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.

[0230] The present application is described with reference to the flowcharts and / or block diagrams of the methods, devices (systems), and computer program products according to the present application. It should be understood that each process and / or box in the flowchart and / or block diagram, as well as the combination of the processes and / or boxes in the flowchart and / or block diagram, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, a special-purpose computer, an embedded processor, or other programmable data processing device to produce a machine, so that the instructions executed by the processor of the computer or other programmable data processing device generate instructions for implementing the processes in the flowchart and / or block diagram. Figure 1 A process or multiple processes and / or boxes Figure 1 A device that provides the functions specified in a block or multiple blocks.

[0231] These computer program instructions may also be stored in a computer-readable memory capable of directing a computer or other programmable data processing device to operate in a specific manner, so that the instructions stored in the computer-readable memory produce an article of manufacture comprising an instruction device, which implements the process Figure 1 A process or multiple processes and / or boxes Figure 1 A function specified in one or more boxes.

[0232] These computer program instructions can also be loaded onto a computer or other programmable data processing device so that a series of operating steps are executed on the computer or other programmable device to produce a computer-implemented process, thereby providing instructions for implementing the process. Figure 1 A process or multiple processes and / or boxes Figure 1 The steps for the functions specified in one or more boxes.

[0233] Obviously, those skilled in the art can make various changes and modifications to the present application without departing from the spirit and scope of the present application. Thus, if these modifications and variations of the present application fall within the scope of the claims of the present application and their equivalents, the present application is also intended to include these modifications and variations.

Claims

1. A communication method, It is characterized in that The method is applied to a data channel control network element, and the method comprises: Receiving request information from the first communication device, the request information being used to request acquisition of a data channel application or request use of the data channel application; According to the traffic type of the data channel application 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; Among them, the flow type is a flow exemption type or a non-flow exemption type, and the flow switch state is open or closed.

2. The method according to claim 1, It is characterized in that According to the traffic type of the data channel application and the traffic switch state of the first communication device, rejecting the request corresponding to the request information includes: Determining that the flow type is a non-flow exemption type and the flow switch state is closed; A first response message is sent, where the first response message indicates that the request corresponding to the request message is rejected.

3. The method according to claim 1, It is characterized in that Receiving a 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 includes: Determining that the flow type is a flow exemption type and the flow switch state is closed; Sending second response information, where the second response information indicates acceptance of the request corresponding to the request information.

4. The method according to claim 2, It is characterized in that The first response information includes reason information, where 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.

5. The method according to claim 3, Features: The request information is used to request to obtain 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 the use of the data channel application, and the second response information includes media resource information used to establish an application data channel corresponding to the data channel application.

6. The method according to any one of claims 1 to 5, It is characterized in that The method further comprises: Receive status information from an Internet Protocol Multimedia Subsystem IMS application server, where the status information is used to indicate the flow switch status.

7. The method according to claim 6, It is characterized in that The receiving status information from the IMS application server includes: A session event reporting message is received from the IMS application server, where the session event reporting message includes the state information.

8. The method according to claim 6 or 7, It is characterized in that The status information includes a packet switched data interrupt flag.

9. The method according to any one of claims 1 to 8, It is characterized in that The method further comprises: Obtain a traffic exemption application whitelist, wherein the traffic exemption application whitelist includes multiple application identifiers, each application identifier is used to identify a data channel application identified as a traffic exemption type by the network side; Based on the fact that the traffic exemption application whitelist includes the identifier of the data channel application, the traffic type of the data channel application is determined to be the traffic exemption type; or, based on the fact that the traffic exemption application whitelist does not include the identifier of the data channel application, the traffic type of the data channel application is determined to be the non-traffic exemption type.

10. The method according to any one of claims 1 to 9, Features: The first communication device is a calling party user equipment, and the data channel control network element is a network element in the 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.

11. A communication method, It is characterized in that The method is applied to an IMS application server, and the method comprises: Acquire status information of the first communication device, where the status information is used to indicate a flow switch status of the first communication device, where the flow switch status is on or off; The status information is sent to a data channel control network element, where the status information is used to accept or reject a request corresponding to the request information sent by the first communication device, where the request information is used to request to obtain a data channel application or to request to use the data channel application.

12. The method according to claim 11, It is characterized in that Acquiring status information of a first communication device, including: A registration request message or a re-registration request message is received from the first communication device, where the registration request message or the re-registration request message includes the state information.

13. The method according to claim 11 or 12, It is characterized in that 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, wherein the SIP message is used to manage a communication session between the first communication device and the second communication device, wherein the communication session is associated with a data channel; The status information is sent to the data channel control network element according to the SIP message.

14. The method according to any one of claims 11 to 13, It is characterized in that 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 state information.

15. The method according to any one of claims 11 to 14, It is characterized in that The request information is used to request the use of the data channel application; the method further includes: receiving first response information from the data channel control network element, where 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.

16. The method according to any one of claims 11 to 14, It is characterized in that The request information is used to request the use of the data channel application; the method further includes: receiving second response information from the data channel control network element, where the second response information indicates acceptance of the request corresponding to the request information; The second response information includes media resource information used to establish an application data channel corresponding to the data channel application.

17. The method according to any one of claims 11 to 16, It is characterized in that The first communication device is a calling party user equipment, the IMS application server is a network element in an originating IMS network, 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, the IMS application server is a network element in a terminating IMS network, and the data channel control network element is a network element in a terminating IMS network.

18. A communication method, It is characterized in that The method comprises: The IMS application server obtains status information of the first communication device, where the status information is used to indicate a flow switch status of the first communication device, where the flow switch status is on or off; The IMS application server sends the status information to the 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, where the request information is used to request to obtain a data channel application or to request to use 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 traffic type of the data channel application and the traffic switch state; The traffic type is a traffic exemption type or a non-traffic exemption type.

19. A communication device, It is characterized in that It comprises a processor, the processor is coupled to a memory, and a computer program is stored in the memory; the processor is used to call the computer program in the memory so that the information transmission device executes the method as described in any one of claims 1 to 10.

20. A communication device, It is characterized in that It includes a processor, which is coupled to a memory, and a computer program is stored in the memory; the processor is used to call the computer program in the memory, so that the information transmission device executes the method as described in any one of claims 11 to 17.

21. A communication system, It is characterized in that The information delivery system comprises the apparatus as claimed in claim 19 and the apparatus as claimed in claim 20.

22. A computer-readable storage medium, It is characterized in that The storage medium stores a computer program or instruction. When the computer program or instruction is executed by a computer, the method according to any one of claims 1 to 10 is implemented, or the method according to any one of claims 11 to 17 is implemented, or the method according to claim 18 is implemented.

23. A computer program product, It is characterized in that When a computer reads and executes the computer program product, the computer is enabled to execute the method according to any one of claims 1 to 10, or implement the method according to any one of claims 11 to 17, or the method according to claim 18.

Images