Data channel (DC) establishment method, message processing method, resource allocation method, and related devices

Abstract

The present application relates to the technical field of communications, and discloses a data channel (DC) establishment method, a message processing method, a resource allocation method, and related devices. The DC establishment method in an embodiment of the present application comprises: when a voice, video, or message media connection is not established, a first terminal sending a first message, wherein the first message is used to request establishment of a target DC, and the target DC comprises at least one of a bootstrap DC and an application DC; and the first terminal receiving a first response message, and establishing the target DC on the basis of the first response message.

Description

Data channel DC establishment, message processing, resource allocation method and related equipment

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS

[0002] This application claims priority to the Chinese patent application filed with the China Patent Office on November 2, 2023, with application number 202311452312.1, and invention name “Data channel DC establishment, message processing, resource allocation method and related equipment”, and the Chinese patent application filed with the China Patent Office on June 21, 2024, with application number 202410809427.X, and invention name “Data channel DC establishment, message processing, resource allocation method and related equipment”, the entire contents of which are incorporated by reference into this application. Technical Field

[0003] The present application belongs to the field of communication technology, and specifically relates to a data channel DC establishment, message processing, resource allocation method and related equipment. Background Art

[0004] The 3rd Generation Partnership Project (3GPP) standard introduced a mechanism for establishing a Data Channel (DC) during a call. DC enables additional services during a call, such as screen sharing, location sharing, and file transfer, thereby providing a better user experience.

[0005] However, in related technologies, the establishment of a DC is always accompanied by the establishment of services such as voice calls, video calls or text messages, which makes the DC establishment process inflexible.

[0006] Summary of the Invention

[0007] The embodiments of the present application provide a DC establishment, message processing, resource allocation method and related equipment, which can solve the problem that the DC establishment process is not flexible enough.

[0008] In a first aspect, a DC establishment method is provided, which is performed by a first terminal. The method includes:

[0009] Without establishing a voice, video, or message media connection, the first terminal sends a first message for requesting to establish a target DC, where the target DC includes at least one of a bootstrap DC and an application DC.

[0010] The first terminal receives the first response message and establishes the target DC according to the first response message.

[0011] In a second aspect, a message processing method is provided, which is executed by a second terminal, and the method includes:

[0012] When the second terminal receives the third message and satisfies the third condition, it sends a 180 message corresponding to the third message, wherein the third message is used to request to establish a target DC, and the target DC includes at least one of a bootstrap DC and an application DC;

[0013] The third condition includes at least one of the following:

[0014] The third message is used to request the establishment of an application DC;

[0015] The second terminal completes downloading of the DC application corresponding to the application DC;

[0016] The second terminal completes the establishment of the bearer corresponding to the application DC.

[0017] In a third aspect, a message processing method is provided, which is executed by an IP Multimedia Subsystem Application Server (IMS AS), the method comprising:

[0018] The IMS AS receives a first message from the first terminal;

[0019] The IMS AS performs a first operation according to the first message, where the first operation includes at least one of the following:

[0020] When the first message is used to request establishment of a bootstrap DC, second indication information is sent to the DCSF, wherein the second indication information is used to instruct to establish only a bootstrap DC;

[0021] When the first message is used to request establishment of a bootstrap DC and an application DC, sending a first SDP offer message to the second terminal, where the first SDP offer message is used to establish the bootstrap DC; and when the IMS AS receives a first SDP answer message from the second terminal, sending a second SDP offer message to the second terminal, where the first SDP answer message is SDP answer information corresponding to the first SDP offer message, and the second SDP offer message is used to establish the application DC;

[0022] In the case where the first message is used to request the establishment of an application DC, a fourth message is sent to the DCSF, where the fourth message is used to notify the DCSF to only establish a bootstrap DC for the second terminal.

[0023] In a fourth aspect, a resource allocation method is provided, which is performed by a Data Channel Signaling Function (DCSF), and the method includes:

[0024] The DCSF receives a fourth message from the IMS AS;

[0025] In a case where the fourth message is used to notify that a bootstrap DC is established only for the first terminal, the DCSF allocates or reserves resources corresponding to the bootstrap DC for the first terminal; or

[0026] In a case where the fourth message is used to notify the establishment of a bootstrap DC only for the second terminal, the DCSF allocates or reserves resources corresponding to the bootstrap DC for the second terminal.

[0027] In a fifth aspect, a DC establishment device is provided, for use with a first terminal, the device including:

[0028] A first sending module is configured to send a first message without establishing a voice, video, or message media connection, where the first message is used to request establishment of a target DC, where the target DC includes at least one of a bootstrap DC and an application DC;

[0029] The first establishing module is configured to receive a first response message and establish the target DC according to the first response message.

[0030] In a sixth aspect, a message processing device is provided for a second terminal, the device including:

[0031] a first transmission module, configured to, upon receiving a third message, send a 180 message corresponding to the third message if a third condition is met, wherein the third message is used to request establishment of a target data channel DC, where the target DC includes at least one of a bootstrap DC and an application DC;

[0032] The third condition includes at least one of the following:

[0033] The third message is used to request the establishment of an application DC;

[0034] The second terminal completes downloading of the DC application corresponding to the application DC;

[0035] The second terminal completes the establishment of the bearer corresponding to the application DC.

[0036] In a seventh aspect, a message processing device is provided for use in an IMS AS, the device comprising:

[0037] A first receiving module, configured to receive a first message from a first terminal;

[0038] an execution module, configured to perform a first operation according to the first message, where the first operation includes at least one of the following:

[0039] When the first message is used to request establishment of a bootstrap data channel DC, sending second indication information to the data channel signaling function DCSF, wherein the second indication information is used to indicate that only the bootstrap DC is established;

[0040] When the first message is used to request establishment of a bootstrap DC and an application DC, sending a first SDP offer message to the second terminal, where the first SDP offer message is used to establish the bootstrap DC; and when the IMS AS receives a first SDP answer message from the second terminal, sending a second SDP offer message to the second terminal, where the first SDP answer message is SDP answer information corresponding to the first SDP offer message, and the second SDP offer message is used to establish the application DC;

[0041] In the case where the first message is used to request the establishment of an application DC, a fourth message is sent to the DCSF, where the fourth message is used to notify the DCSF to only establish a bootstrap DC for the second terminal.

[0042] In an eighth aspect, a resource allocation device is provided for use in a DCSF, the device comprising:

[0043] A second receiving module, configured to receive a fourth message from an IP multimedia subsystem application server IMS AS;

[0044] A first resource allocation module is configured to allocate or reserve resources corresponding to the bootstrap data channel DC for the first terminal when the fourth message is used to notify that only the first terminal is to be established; or

[0045] The second resource allocation module is configured to allocate or reserve resources corresponding to the bootstrap DC for the second terminal by the DCSF when the fourth message is used to notify that a bootstrap DC is established only for the second terminal.

[0046] In a ninth aspect, a terminal is provided, comprising a processor and a memory, wherein the memory stores programs or instructions that can be run on the processor, and when the programs or instructions are executed by the processor, the steps of the method described in the first aspect or the second aspect are implemented.

[0047] In a tenth aspect, a terminal is provided, comprising a processor and a communication interface;

[0048] When the terminal is a first terminal, the communication interface is used to send a first message and receive a first response message without establishing a voice, video, or message media connection, and establish a target DC according to the first response message, wherein the first message is used to request establishment of the target DC, and the target DC includes at least one of a bootstrap DC and an application DC;

[0049] When the terminal is the second terminal, the communication interface is configured to, upon receiving the third message, send a 180 message corresponding to the third message if a third condition is met, wherein the third message is used to request establishment of a target data channel DC, where the target DC includes at least one of a bootstrap DC and an application DC;

[0050] The third condition includes at least one of the following:

[0051] The third message is used to request the establishment of an application DC;

[0052] The second terminal completes downloading of the DC application corresponding to the application DC;

[0053] The second terminal completes the establishment of the bearer corresponding to the application DC.

[0054] In the eleventh aspect, a network side device is provided, which includes a processor and a memory, wherein the memory stores programs or instructions that can be run on the processor, and when the program or instructions are executed by the processor, the steps of the method described in the third aspect or the fourth aspect are implemented.

[0055] In a twelfth aspect, a network-side device is provided, including a processor and a communication interface;

[0056] When the network-side device is an IMS AS, the communication interface is configured to receive a first message from the first terminal, and the processor is configured to perform a first operation according to the first message, where the first operation includes at least one of the following:

[0057] When the first message is used to request establishment of a bootstrap data channel DC, sending second indication information to the data channel signaling function DCSF, wherein the second indication information is used to indicate that only the bootstrap DC is established;

[0058] When the first message is used to request establishment of a bootstrap DC and an application DC, sending a first SDP offer message to the second terminal, where the first SDP offer message is used to establish the bootstrap DC; and when the IMS AS receives a first SDP answer message from the second terminal, sending a second SDP offer message to the second terminal, where the first SDP answer message is SDP answer information corresponding to the first SDP offer message, and the second SDP offer message is used to establish the application DC;

[0059] In a case where the first message is used to request establishment of an application DC, sending a fourth message to the DCSF, where the fourth message is used to notify the DCSF to establish only a bootstrap DC for the second terminal;

[0060] When the network side device is DCSF, the communication interface is used to receive a fourth message from the IP Multimedia Subsystem Application Server IMS AS; the processor is used to allocate or reserve resources corresponding to the bootstrap DC for the first terminal when the fourth message is used to notify that a bootstrap data channel DC is established only for the first terminal, or the processor is used to allocate or reserve resources corresponding to the bootstrap DC for the second terminal when the fourth message is used to notify that a bootstrap DC is established only for the second terminal.

[0061] In the thirteenth aspect, a readable storage medium is provided, on which a program or instruction is stored. When the program or instruction is executed by a processor, the steps of the method described in the first aspect are implemented, or the steps of the method described in the second aspect are implemented, or the steps of the method described in the third aspect are implemented, or the steps of the method described in the fourth aspect are implemented.

[0062] In the fourteenth aspect, a wireless communication system is provided, including: a terminal and a network side device, wherein the terminal can be used to execute the steps of the method described in the first aspect or the second aspect, and the network side device can be used to execute the steps of the method described in the third aspect or the fourth aspect.

[0063] In the fifteenth aspect, a chip is provided, comprising a processor and a communication interface, wherein the communication interface is coupled to the processor, and the processor is used to run programs or instructions to implement the method described in the first aspect, or the method described in the second aspect, or the method described in the third aspect, or the method described in the fourth aspect.

[0064] In the sixteenth aspect, a computer program / program product is provided, which is stored in a storage medium, and the program / program product is executed by at least one processor to implement the steps of the method described in the first aspect, or the steps of the method described in the second aspect, or the steps of the method described in the third aspect, or the steps of the method described in the fourth aspect.

[0065] In an embodiment of the present application, the first terminal can establish at least one of a bootstrap DC and an application DC by sending a first message and receiving a first response message corresponding to the first message without establishing a voice, video, or message media connection. This decouples the establishment process of at least one of the bootstrap DC and the application DC from the establishment request process of services such as voice calls, video calls, or text messages, thereby improving the flexibility of the DC establishment process. BRIEF DESCRIPTION OF THE DRAWINGS

[0066] FIG1 is a schematic diagram of the structure of a communication network to which an embodiment of the present application can be applied;

[0067] FIG2 is a schematic diagram of the interactive process of establishing bootstrapDC in the related art;

[0068] FIG3 is a flow chart of a DC establishment method provided in an embodiment of the present application;

[0069] FIG4 is a flowchart of a message processing method according to an embodiment of the present application;

[0070] FIG5 is a second flowchart of a message processing method provided in an embodiment of the present application;

[0071] FIG6 is a flow chart of a resource allocation method provided in an embodiment of the present application;

[0072] FIG7 a is a schematic diagram of the interactive process of establishing bootstrapDC in an embodiment of the present application;

[0073] FIG7 b is a schematic diagram of the interactive process of establishing bootstrapDC and application DC in an embodiment of the present application;

[0074] FIG7 c is a second schematic diagram of the interactive process of establishing bootstrapDC and application DC in an embodiment of the present application;

[0075] FIG7 d is a third schematic diagram of the interactive process of establishing bootstrapDC and application DC in an embodiment of the present application;

[0076] FIG7e is a fourth schematic diagram of the interactive process of establishing bootstrapDC and application DC in an embodiment of the present application;

[0077] FIG8 is a schematic structural diagram of a DC establishment device provided in an embodiment of the present application;

[0078] FIG9 is a structural diagram of a message processing device according to an embodiment of the present application;

[0079] FIG10 is a second structural diagram of a message processing device provided in an embodiment of the present application;

[0080] FIG11 is a schematic structural diagram of a resource allocation device provided in an embodiment of the present application;

[0081] FIG12 is a schematic diagram of the structure of a communication device provided in an embodiment of the present application;

[0082] FIG13 is a schematic diagram of the hardware structure of a terminal provided in an embodiment of the present application;

[0083] FIG14 is a schematic structural diagram of a network-side device provided in an embodiment of the present application. DETAILED DESCRIPTION

[0084] The following will be combined with the accompanying drawings in the embodiments of this application to clearly describe the technical solutions in the embodiments of this application. Obviously, the embodiments described are part of the embodiments of this application, not all of the embodiments. Based on the embodiments in this application, all other embodiments obtained by ordinary technicians in this field are within the scope of protection of this application.

[0085] The terms "first", "second", etc. in this application are used to distinguish similar objects, and are not used to describe a specific order or sequence. It should be understood that the terms used in this way are interchangeable where appropriate, so that the embodiments of the present application can be implemented in an order other than those illustrated or described herein, and the objects distinguished by "first" and "second" are generally of the same type, and do not limit the number of objects, for example, the first object can be one or more. In addition, "or" in this application represents at least one of the connected objects. For example, "A or B" covers three options, namely, Option 1: including A but not including B; Option 2: including B but not including A; Option 3: including both A and B. The character " / " generally indicates that the objects associated before and after are in an "or" relationship.

[0086] The term "indication" in this application can be either a direct indication (or explicit indication) or an indirect indication (or implicit indication). A direct indication can be understood as the sender explicitly informing the receiver of specific information, the operation to be performed, or the requested result, etc. in the instruction sent; an indirect indication can be understood as the receiver determining the corresponding information based on the instruction sent by the sender, or making a judgment and determining the operation to be performed or the requested result, etc. based on the judgment result.

[0087] It is worth noting that the technology described in the embodiments of the present application is not limited to the Long Term Evolution (LTE) / LTE-Advanced (LTE-A) system, but can also be used in other wireless communication systems, such as Code Division Multiple Access (CDMA), Time Division Multiple Access (TDMA), Frequency Division Multiple Access (FDMA), Orthogonal Frequency Division Multiple Access (OFDMA), Single-carrier Frequency Division Multiple Access (SC-FDMA) or other systems. The terms "system" and "network" in the embodiments of the present application are often used interchangeably, and the technology described can be used for the systems and radio technologies mentioned above, as well as for other systems and radio technologies. The following description describes a New Radio (NR) system for illustrative purposes, and the NR terminology is used in most of the following description, but these technologies can also be applied to systems other than NR systems, such as the 6th generation (6G) system. th Generation, 6G) communication system.

[0088] FIG1 is a block diagram of a wireless communication system applicable to an embodiment of the present application. The wireless communication system includes a terminal 11 and a network-side device 12. The terminal 11 may be a mobile phone, a tablet computer (Tablet Personal Computer), a laptop computer (Laptop Computer), a notebook computer, a personal digital assistant (PDA), a handheld computer, a netbook, an ultra-mobile personal computer (UMPC), a mobile internet device (MID), an augmented reality (AR), a virtual reality (VR) device, a robot, a wearable device (Wearable Device), an aircraft (Flight Vehicle), a vehicle-mounted device (VUE), a ship-mounted device, a pedestrian user equipment (PUE), a smart home (home appliances with wireless communication capabilities, such as refrigerators, televisions, washing machines, or furniture), a game console, a personal computer (PC), an ATM, or a self-service machine, or other terminal-side devices. Wearable devices include: smart watches, smart bracelets, smart headphones, smart glasses, smart jewelry (smart bracelets, smart bracelets, smart rings, smart necklaces, smart anklets, smart anklets, etc.), smart wristbands, smart clothing, etc. Among them, the vehicle-mounted device can also be called a vehicle-mounted terminal, a vehicle-mounted controller, a vehicle-mounted module, a vehicle-mounted component, a vehicle-mounted chip or a vehicle-mounted unit, etc. In addition to the above-mentioned terminal devices, the terminal 11 can also be a chip in the terminal, such as a modem chip, a system-on-chip (SoC). It should be noted that the specific type of the terminal 11 is not limited in the embodiment of the present application. The network side device 12 may include an access network device or a core network device, wherein the access network device may also be called a radio access network (RAN) device, a radio access network function or a radio access network unit. The access network device may include a base station, a wireless local area network (WLAN) access point (AS) or a wireless fidelity (WiFi) node, etc.Among them, the base station can be referred to as Node B (NB), Evolved Node B (eNB), the next generation Node B (gNB), New Radio Node B (NR Node B), access point, Relay Base Station (RBS), Serving Base Station (SBS), Base Transceiver Station (BTS), radio base station, radio transceiver, Basic Service Set (BSS), Extended Service Set (ESS), Home Node B (HNB), Home Evolved Node B (homeevolved Node B), Transmission Reception Point (TRP) or other appropriate terms in the relevant field. As long as the same technical effect is achieved, the base station is not limited to specific technical vocabulary. It should be noted that in the embodiment of the present application, only the base station in the NR system is used as an example for introduction, and the specific type of the base station is not limited.

[0089] The core network equipment may include but is not limited to at least one of the following: core network node, core network function, mobility management entity (MME), access mobility management function (AMF), session management function (SMF), user plane function (UPF), policy control function (PCF), policy and charging rules function unit (PCRF), edge application service discovery function (EASDF), unified data management (UDM), unified data repository (UDR), home subscriber server (HSS), centralized network configuration (CNC), network storage function (NRF), network exposure function (NEF), local NEF (L-NEF), binding support function (BSF), etc. Function, BSF), application function (Application Function, AF), etc. It should be noted that, in the embodiment of the present application, only the core network device in the NR system is introduced as an example, and the specific type of the core network device is not limited. It should be noted that, in the embodiment of the present application, only the core network device in the NR system is introduced as an example, and the specific type of the core network device is not limited.

[0090] DC allows for additional services during a call, such as screen sharing, location sharing, and file transfer. Different services correspond to different DC applications, which can be dynamically downloaded to the terminal during the call, eliminating the need for pre-installation and facilitating user convenience. In related technologies, data channels are established alongside services such as voice calls, video calls, or text messages.

[0091] As shown in FIG2 , the process of establishing a bootstrapDC in the related art includes the following steps:

[0092] Step 1: User Equipment (UE)-1 initiates a call request to UE-2 through a Session Initiation Protocol (SIP) invite message. The SIP invite message carries a Session Description Protocol (SDP) offer, which describes the media description information for this call.

[0093] It is worth noting that the SDP offer includes the description information of the voice / video and the description information for establishing the BootstrapDC. The description information of the BootstrapDC is as follows:

[0094] m=application 52718 UDP / DTLS / SCTP webrtc-datachannel

[0095] b=AS:500

[0096] a=max-message-size:1024

[0097] a=sctp-port:5000

[0098] a=dcmap:0 subprotocol="http"

[0099] Among them, row m represents that the media type is a data channel; row b represents that the bandwidth corresponding to the data channel is 500kbps; and row a represents the attribute information of the data channel.

[0100] Specifically, a=max-message-size:1024 means that the maximum size of the message that can be transmitted by this data channel is 1024 bytes;

[0101] a=sctp-port:5000 means the port number corresponding to the data channel is 5000;

[0102] a=dcmap:0 subprotocol="http" indicates that the DC application corresponding to the bootstrap DC is provided by UE-1's network operator;

[0103] In line a, 0 is the stream ID, which is used to identify the DC. Typically, 0-999 identifies the bootstrap DC, and 1000 or greater identifies the application DC.

[0104] The invite message passes through the Proxy Call Session Control Function (P-CSCF) and the Serving CSCF (S-CSCF) serving UE-1, and is ultimately routed to the IMS AS serving UE-1, such as the Telephony Application Server (TAS).

[0105] Step 2: The IMS AS verifies UE-1 based on the user's subscription information. If UE-1 can use the DC service, the IMS AS selects the DCSF.

[0106] Step 3: The IMS AS sends a Nimsas_SessionEventControl_Notify message to the DCSF to notify the DCSF to establish a Bootstrap DC.

[0107] The Nimsas_SessionEventControl_Notify message carries the following information:

[0108] Event ID: For example, when establishing a bootstrap DC, the Event ID is SessionEstablishmentRequestEvent

[0109] Calling ID: the ID of UE-1, such as the IMS Public Identity (IMPU) of UE-1;

[0110] Called ID: the ID of UE-2, such as UE-2's IMPU;

[0111] SessionCase: Indicates whether the session is triggered by the calling party or the called party;

[0112] Session ID (SessionID);

[0113] MediaInfoList: Each media information contains the MediaID and media attribute information, for example, the MediaInfo corresponding to the Bootstrap DC or the MediaInfo corresponding to the application DC.

[0114] Step 4: DCSF decides whether to provide DC and decides the control policy information for DC.

[0115] Step 5: DCSF reserves media information of Media Data Channel (MDC) 1 for the initiating end (UE-1) according to the Policy information, and reserves media information of MDC1 for the terminating end (UE-2).

[0116] Among them, MDC1 is the interface between the Data Channel Media Function (MF) / enhance Media Resource Function (enhance MRF) and DCSF, and is used to transmit media data between DCSF and MF / enhance MRF, for example, transmitting the installation package of DC application, application list, graphical user interface, etc.

[0117] Step 6: The DCSF sends a Nimsas_MediaControl_MediaInstruction message to the IMS AS, instructing the IMS AS to establish a connection with the MF for both communicating parties (UE-1 and UE-2).

[0118] The Nimsas_MediaControl_MediaInstruction message contains the following information:

[0119] Session ID, which is the same as the Session ID in step 3;

[0120] The media instruction set (MediaInstructionSet) includes: mediaID and mediaInstruction. The mediaID is used to uniquely identify a media and is the same as the media ID in step 3. The mediaInstruction instructs the IMS AS how to handle the media, for example, connect the MF, disconnect the MF, etc.

[0121] Step 7: The IMS AS discovers the MF / enhance MRF.

[0122] Step 8: The IMS AS sends an Nmf_MediaResourceManagement_Create message to the MF according to the DCSF instruction (MediaInstructionSet) in step 6. The message includes the media resource information reserved for the calling party and the media resource information reserved for the called party.

[0123] Step 9: The IMS AS sends a response message to the DCSF to inform the DCSF whether the resource reservation is successful and the data channel media resource information negotiated for MDC1.

[0124] Step 10: DCSF sends a response message.

[0125] Step 11: The IMS AS modifies the content of the SDP sent to UE-2, adds the media information of the MF or enhance MRF, and sends the Invite message to the S-CSCF.

[0126] Step 12: The S-CSCF sends an Invite message to UE-2.

[0127] Step 13: UE-2 replies with an SDP answer via a 183 response message, which is routed to UE-1.

[0128] The above SDP answer contains the media information of the voice and bootstrap DC determined by UE-2.

[0129] Step 14: The network of UE-2 establishes a dedicated Quality of Service flow (QoS flow) for UE-2 for transmitting voice services, and a dedicated QoS flow for transmitting bootstrap DC.

[0130] Step 15: The network of UE-1 establishes a dedicated QoS flow for UE-1 to transmit voice services and a dedicated QoS flow for transmitting bootstrap DC.

[0131] Step 16: After the dedicated QoS flow of UE-2 is established, UE-2 sends a 180 message to UE-1 and starts ringing.

[0132] Step 17: When the user of UE-2 answers the incoming call, UE-2 sends a 200 OK message.

[0133] Step 18: The IMS AS sends a notification message to the DCSF to notify that the session is successfully established.

[0134] Step 19: DCSF sends a response message.

[0135] Step 20: The IMS AS sends a 200 OK message to UE-1.

[0136] Step 21: UE-1 downloads the DC application list (applicationlist) through the bootstrap DC.

[0137] Step 22: When the user of UE-1 selects an application from the DC application list, UE-1 downloads the DC application through the bootstrap DC.

[0138] Step 23: UE-1 initiates a request to establish an application DC through a re-Invite message. The application DC is used to transmit data corresponding to the downloaded DC application.

[0139] The SDP offer in the re-Invite message includes the description of the audio / video, the description of the established BootstrapDC, and the description of the application DC to be established. The description of the application DC to be established includes application information, such as the application ID.

[0140] Step 24: The IMS AS sends a notification message to the DCSF.

[0141] Step 25: DCSF determines how to establish the application DC based on the notification message.

[0142] Step 26: DCSF determines whether to allow UE-1 and UE-2 to establish the application DC, and whether to add the MF to the application DC.

[0143] Step 27: The DCSF instructs the IMS AS how to process the media.

[0144] Step 28: If it is not necessary to add the MF to the application DC, the IMS AS directly sends the re-Invite message to UE-2.

[0145] Step 29: UE-2 determines the DC application requested by UE-1 based on the content of the application DC in the SDP offer.

[0146] It should be noted that, in this step, when UE-2 determines that the DC application has not been downloaded, it downloads the DC application through the bootstrap DC.

[0147] Step 30: UE-2 responds with a 200 OK message.

[0148] Step 31: The IMS AS sends a notification message to the DCSF to inform the application DC that the establishment is successful.

[0149] Step 32: DCSF sends a response message.

[0150] Step 33: The IMS sends a 200 OK message to UE-1.

[0151] Step 34: Optionally, the called network side establishes a QoS flow corresponding to application DC for UE-2.

[0152] Step 35: Optionally, the calling network side establishes a QoS flow corresponding to application DC for UE-1.

[0153] It should be noted that steps 34 and 35 are optional. Specifically, if the DC application has high requirements for data transmission quality, a dedicated QoS flow needs to be established. If the requirements are not high, the QoS flow corresponding to the bootstrap DC can be used for data transmission.

[0154] Step 36: UE-1 responds with an Acknowledgement (ACK) message.

[0155] Step 37: The application DC is activated and the DC application can use the application DC to transmit data.

[0156] Based on the process of establishing bootstrapDC in the above related technologies, it can be seen that the establishment of DC in the related technologies is established along with the establishment of services such as voice calls, video calls or text messages, and it is impossible to establish DC separately.

[0157] In an embodiment of the present application, the process of establishing at least one of the bootstrap DC and the application DC is decoupled from the voice / or video call request. In this way, even before the calling UE initiates an outgoing voice / or video call request, at least one of the bootstrap DC and the application DC of the calling UE and the called UE can be established, making the process of establishing the bootstrap DC and the application DC more flexible.

[0158] The DC establishment method, message processing method, resource allocation method and related equipment provided in the embodiments of the present application are described in detail below with reference to the accompanying drawings through some embodiments and their application scenarios.

[0159] Referring to FIG3 , an embodiment of the present application provides a DC establishment method, which is executed by a first terminal. As shown in FIG3 , the DC establishment method includes the following steps:

[0160] Step 301: A first terminal sends a first message without establishing a voice, video or message media connection. The first message is used to request the establishment of a target DC, where the target DC includes at least one of a bootstrap DC and an application DC.

[0161] The bootstrap DC is used to download the DC application from the data channel server (such as DCSF), and the application DC is used to transmit DC application data.

[0162] It should be noted that the DC application in the embodiment of the present application can also be called an application (APP).

[0163] Step 302: The first terminal receives a first response message and establishes the target DC according to the first response message.

[0164] In some implementations, the first message may include at least one of an Invite message, a Re-Invite message, and an Update message.

[0165] In some implementations, the first terminal sending the first message may be that the first terminal may send at least one of an Invite message, a re-Invite message, and an Update message to the second terminal, where the first terminal represents a calling terminal and the second terminal represents a called terminal.

[0166] In some embodiments, the first terminal sending the first message may be the first terminal sending an Invite message to a preset destination address, where the preset destination address may be a preset special number, such as a customer service phone number of a communications operator, the first terminal's own phone number, a DCSF phone number, an IMS AS phone number, a Public Service Identity (PSI) for indicating that only a bootstrap DC is established, etc. The phone number may also be understood as a number, a SIP Uniform Resource Identifier (URI), an IP Multimedia Public Identity (IMPU), or a PSI.

[0167] It should be noted that the boostrapDC established without establishing a voice, video or message media connection can also be understood or replaced by a standalone bootstrap DC; the application DC established without establishing a voice, video or message media connection can also be understood or replaced by a standalone application DC.

[0168] It should be noted that establishing only the bootstrap DC can also be understood or replaced by the standalonebootstrap DC.

[0169] It should be noted that the PSI for indicating that only a bootstrap DC is established may also be understood or replaced by a PSI for indicating a standalone bootstrap DC (PSI indicating standalone bootstrap DC).

[0170] In some embodiments, the first response message is a response message to the above-mentioned first message, and the first response message may carry information for the first terminal to establish a target DC. For example, the first message may carry an SDP answer for establishing a bootstrap DC.

[0171] It should be noted that the type of the first response message is related to the type of the first message and the destination address of the first message. For example, when the first message is an Invite message sent to a preset special number, the first response message may include a 183 message or a 200OK message from the IMS AS, and the 183 message or 200OK message carries an SDP answer.

[0172] Furthermore, in an embodiment of the present application, without establishing a voice, video, or message media connection, the first terminal requests the establishment of a target DC through the first message, without having to request the establishment of a DC based on the process of establishing a service such as a voice, video call, or SMS. This decouples the process of establishing the target DC from the process of requesting the establishment of a service such as a voice call, video call, or SMS, thereby increasing the flexibility of the DC establishment process.

[0173] It is worth mentioning that in order to achieve the establishment of a separate DC, the voice / video description information carried in the SDP offer in the SIP invite message in the related art can be deleted, and only the description information for establishing the bootstrapDC can be retained. However, this solution has the following drawbacks:

[0174] 1) The calling UE can download the DC application list and select a DC application through the bootstrap DC only after sending a SIP Invite request to the communication peer. That is, the calling UE cannot determine which DC applications can be used or select a DC application before initiating a SIP Invite request, which provides a poor user experience for the calling UE.

[0175] 2) The called UE can only know which DC application to use after receiving the SIP Invite request and waiting for the calling UE to select the DC application. That is, the called UE does not know which DC application the calling UE wants to use when the call is ringing, which is not a good user experience for the called UE.

[0176] In an embodiment of the present application, by independently requesting to establish a target DC without establishing a voice, video, or message media connection, the calling UE can establish at least one of the bootstrap DC and application DC of the calling UE and download the DC application list before sending a SIP Invite request to the communication peer, so that the user can know which DC applications can be used or select a DC application from them before initiating a request to the communication peer. For example, the DC application list is displayed on the user interface (UI) for the user to select the DC application to be used for communication with the communication peer. By independently requesting to establish a target DC, the called UE can establish a bootstrap DC before the call rings, or, if the calling UE selects a DC application, download the DC application and establish the application DC corresponding to the DC application before the call rings. In this way, after the calling UE initiates a SIP Invite request to the called UE, the waiting time for the calling UE and the called UE to transmit DC application data using the application DC can be reduced, thereby improving the user experience.

[0177] As an optional implementation manner, the target DC includes a bootstrap DC, and the first terminal sends a first message including:

[0178] The first terminal sends a first Invite message to a preset destination address, where the first Invite message includes SDP offer information for establishing the bootstrap DC.

[0179] In some implementations, the preset destination address may be a preset special number, such as a communication operator number or the first terminal's own communication number, etc., which is not specifically limited here.

[0180] In this implementation, the first terminal may establish a bootstrap DC of the first terminal by sending a first Invite message to a preset destination address.

[0181] For example: As shown in Figure 7a, assuming that the first terminal is UE-1, UE-1 sends an Invite message to a preset special number. The Invite message carries an SDP offer for bootstrap DC. At this time, the IMS AS verifies UE-1 based on UE-1's subscription. If UE-1 can use DC services, the IMS AS selects DCSF and sends a Nimsas_SessionEventControl_Notify message to the selected DCSF; DCSF reserves MDC1 media information for UE-1 based on the received Nimsas_SessionEventControl_Notify message, and instructs the IMS AS to establish a connection with MF for UE-1; IMS AS discovers MF / enhance MRF based on the DCSF's instruction, and instructs MF to reserve media resource information for UE-1; finally, the IMS AS sends a 200OK message to UE-1, carrying an SDP answer.

[0182] Optionally, the first Invite message further includes first indication information, where the first indication information is used to indicate that only a bootstrap DC is to be established.

[0183] In this implementation, the first indication information may be used to explicitly instruct the network side to only establish a bootstrap DC for the terminal.

[0184] Of course, in the case where the first Invite message does not include the first indication information, the network side may also learn that the first Invite message is only used to request the establishment of a bootstrap DC based on the fact that the first Invite message only carries the SDP offer information corresponding to the bootstrap DC but does not carry the SDP offer information for the application DC. Alternatively, the network side may also learn that the first Invite message is only used to request the establishment of a bootstrap DC but not for the establishment of an application DC based on a preset special called number.

[0185] Optionally, the first terminal sending the first message includes:

[0186] The first terminal sends a first message when a first condition is met;

[0187] The first condition includes at least one of the following:

[0188] Turning on the first terminal;

[0189] The first terminal releases or turns off the flight mode;

[0190] The first terminal completes IMS registration or IMS re-registration;

[0191] The dialing application (APP) of the first terminal is started;

[0192] The preset APP of the first terminal is started, and the preset APP is used to establish the target DC. For example, the preset APP is used for the user to select a DC application from a DC application list and establish an application DC.

[0193] In this embodiment, the first terminal can initiate the process of establishing the target DC when it is turned on, the flight mode is released or turned off, IMS registration or IMS re-registration is completed, the dial-up application APP is started, or the preset APP is started, without following the establishment request of services such as voice calls, video calls or text messages to initiate the process of establishing the target DC.

[0194] As an optional implementation manner, when the target DC includes a bootstrap DC, the method further includes:

[0195] The first terminal downloads an application list (applicationlist) based on the bootstrap DC.

[0196] In some implementations, the application list may be a list of DC applications.

[0197] In this embodiment, after establishing the bootstrap DC, the bootstrap DC can be used to download a list of DC applications. Since the bootstrap DC can be established before initiating a request to the communication peer, the list of DC applications can be downloaded before initiating a request to the communication peer, so that the user can select the DC application to be used with the communication peer.

[0198] For example: before the user of the first terminal dials a number, such as when the device is turned on, the process of establishing a bootstrap DC can be initiated. After the bootstrap DC is established, the bootstrap DC is used to download an application list (i.e., a DC application list). When the user needs to initiate a request to the communication peer, the DC application list that can be used by the first terminal can be displayed on the dial-up interface, so that the user can select the DC application to be used in subsequent communications with the communication peer.

[0199] In some embodiments, the method further comprises:

[0200] The first terminal downloads the first DC application in the application list based on the bootstrap DC.

[0201] In some implementations, the first DC application may be one or at least two commonly used DC applications in the application list. For example, the first terminal downloads a frequently used DC application in the application list based on the bootstrap DC, or a DC application marked as a default download by the network.

[0202] In some embodiments, the first DC application may include a DC application selected by a user from the application list. For example, the first DC application may include a DC application selected by the user to be used in subsequent communications with a communication peer.

[0203] In this embodiment, one or at least two first DC applications may be downloaded in a pre-download manner, and when the first DC application is subsequently used, the waiting time for downloading the first DC application may be omitted.

[0204] As an optional implementation, the method further includes:

[0205] The first terminal releases the bootstrap DC.

[0206] In some implementations, the bootstrap DC may be released after at least one of the application list and the first DC application is downloaded.

[0207] In other implementations, the bootstrap DC may be released when the bootstrap DC is not used for a long time.

[0208] For example, the first terminal releases the bootstrap DC, including:

[0209] The first terminal releases the bootstrap DC when a second condition is met, where the second condition includes at least one of the following:

[0210] When the first timer expires, the first terminal does not send a message or data using the bootstrap DC;

[0211] When the first timer times out, the first terminal does not initiate a request message for establishing an application DC;

[0212] The first timer is started when the first terminal successfully establishes the bootstrap DC, or is started after the first terminal downloads the application list, or is started after the first DC application is downloaded.

[0213] In this implementation, after the bootstrap DC is established, the bootstrap DC may be released to reduce resource consumption and energy consumption caused by maintaining the bootstrap DC.

[0214] The above implementation mainly describes the application scenario of establishing a unilateral bootstrap DC for the first terminal. The process of establishing the bootstrap DC and application DC for the first terminal and the second terminal can be divided into the following four situations:

[0215] Scenario 1: The first terminal obtains a list of DC applications in advance and has not established a bootstrap DC or has already released the established bootstrap DC. In this case, after determining the DC application to be used with the communication peer, the first terminal can request to establish a bootstrap DC again so that the first and second terminals can use the established bootstrap DC to download the DC application. Based on the request to establish the bootstrap DC, the network can initiate the process of establishing the application DC corresponding to the DC application.

[0216] Scenario 2: The first terminal has previously acquired a DC application for use with the communication peer, and has not established a bootstrap DC or has already released the established bootstrap DC. In this case, the first terminal determines that the DC application for use with the communication peer has been downloaded and can request to establish a bootstrap DC and application DC again. This allows the second terminal to download the DC application using the established bootstrap DC, and the first and second terminals can interact with the application data of the DC application using the established application DC.

[0217] Scenario 3: The first terminal has previously acquired a DC application for use with the communication peer. At this point, the first terminal determines that the DC application needed for use with the communication peer has been downloaded, and can send the SDP offer information for the application DC and information for downloading the DC application to the second terminal. This allows the second terminal to initiate the bootstrap DC establishment process based on the information for downloading the DC application, download the DC application based on the established bootstrap DC, and establish an application DC between the first and second terminals based on the SDP offer information for the application DC, enabling the first and second terminals to interact with the application data of the DC application using the established application DC.

[0218] Case 4: The first terminal has established a bootstrap DC, and the bootstrap DC is available. At this time, after determining that the DC application used with the communication peer has been downloaded, the first terminal can send a re-invite message carrying the bootstrap DC and application DC to the second terminal. At this time, the network-side device (such as the IMS AS) can determine, based on the indication in the re-invite message or based on the fact that the first terminal has established a bootstrap DC, that the SDP offer information of the bootstrap DC in the re-invite message is only used to establish the bootstrap DC of the second terminal, and not to establish the bootstrap DC of the first terminal, so that the second terminal can download the required DC application based on the established bootstrap DC. Then, the network-side device can establish the application DC of the first terminal and the second terminal based on the SDP offer information of the application DC in the re-invite message, so that the first terminal and the second terminal can use the established application DC to interact with the application data of the DC application.

[0219] It is worth noting that in some embodiments, in the above four situations, the way in which the first terminal obtains the list of DC applications or DC applications in advance can be, as in the above embodiment, the way in which the first terminal sends a first Invite message to a preset destination address, so that the network side device establishes a unilateral bootstrap DC for the first terminal, and the first terminal downloads the list of DC applications or DC applications based on the unilateral bootstrap DC.

[0220] Of course, the first terminal can also obtain the list of DC applications or DC applications in advance through other methods, for example: the network side preconfigures the list of DC applications or certain DC applications to the first terminal; or, locally preconfigures the list of DC applications or certain DC applications on the first terminal side.

[0221] The following are specific explanations for the above four situations:

[0222] Case 1:

[0223] As an optional implementation manner, the target DC includes a bootstrap DC and an application DC, and the first terminal sends a first message including:

[0224] The first terminal sends a second Invite message to the second terminal, wherein the second Invite message includes first SDP offer information, where the first SDP offer information is used to establish a bootstrap DC;

[0225] When the first terminal receives the first SDP answer information, the second terminal sends a second message to the second terminal, where the second message includes second SDP offer information, wherein the first SDP answer information is the SDP answer information corresponding to the first SDP offer information, and the second SDP offer information is used to establish an application DC.

[0226] In some implementations, the first message includes the second Invite message and the second message.

[0227] In some implementation manners, the first response message may include a response message carrying the first SDP answer information and a response message carrying second SDP answer information corresponding to the second SDP offer information.

[0228] In some embodiments, the type of the second message is related to the type of the first response message.

[0229] For example, when the first terminal receives the first SDP answer information, sending the second message to the second terminal includes:

[0230] As shown in steps 13 and 18 in FIG. 7b , when the first terminal receives a 183 response message including the first SDP answer information, the second terminal sends an update message; or,

[0231] When the first terminal receives the 200OK message including the first SDP answer information, the second terminal sends a re-Invite message.

[0232] It should be noted that, in an embodiment of the present application, the first terminal sending a message to the second terminal may be the first terminal sending a message with the second terminal as the destination address. For example, when the first terminal sends a message with the second terminal as the destination address, the message is processed by the network side device and then forwarded to the second terminal.

[0233] In some implementations, after the first terminal determines to establish an application DC corresponding to the DC application with the second terminal, the first terminal may send a second Invite message to the second terminal, where the second Invite message is used to request to establish a bootstrap DC.

[0234] In some implementations, upon receiving the first SDP answer information, the first terminal establishes a bootstrap DC. Thereafter, the first terminal may use the bootstrap DC to download a DC application for establishing an application DC with the second terminal.

[0235] Optionally, the first terminal may obtain a list of DC applications in advance, and select a DC application for establishing application DC with the second terminal according to a user operation.

[0236] In some implementations, the first terminal may establish a bootstrap DC by sending a first invitation message to a preset destination address, and download a list of DC applications based on the established bootstrap DC.

[0237] Of course, the first terminal may also obtain the list of DC applications in advance through other methods, for example, the network side pre-configures the list of DC applications in the first terminal.

[0238] Among them, for the situation where the first terminal establishes a bootstrap DC by sending a first invitation Invite message to a preset destination address, and downloads a list of DC applications based on the established bootstrap DC, the application scenario of this embodiment is: the bootstrap DC has been released, and the first terminal has not downloaded the DC application used to establish an application DC with the second terminal.

[0239] In some implementations, the second SDP offer information includes SDP offer information of a bootstrap DC and an application DC.

[0240] It should be noted that in this embodiment, after receiving the first SDP offer, the second terminal does not respond with a 180 ringing message or an incoming call notification message. Instead, it only responds with the first SDP answer message based on the first SDP offer. At this point, the first and second terminals complete the negotiation and establishment of the bootstrap DC. Thereafter, the first and second terminals can download the DC application used with the communicating peer based on the established bootstrap DC.

[0241] In this embodiment, after the first terminal has obtained a list of DC applications in advance and selected a DC application to be used with the communication counterpart based on a user operation, it first sends a second Invite message, and establishes a bootstrap DC between the first terminal and the second terminal based on the first SDP answer information received from the second terminal and modified and forwarded by the network side device (IMS AS); after establishing the bootstrap DC, the first terminal sends a second message carrying the second SDP offer information to the second terminal to request the establishment of an application DC.

[0242] Scenario 2

[0243] As an optional implementation manner, the target DC includes a bootstrap DC and an application DC, and the first terminal sending the first message includes:

[0244] The first terminal sends a third Invite message to the second terminal, wherein the third Invite message includes third SDP offer information, and the third SDP offer information is used to establish a bootstrap DC and an application DC.

[0245] In some embodiments, when the network side device receives the above-mentioned third Invite message, it can first establish the bootstrap DC of the first terminal and the second terminal based on the SDP offer information for the bootstrap DC in the third Invite message. When the second terminal replies with the SDP answer information of the bootstrap DC, it can establish the application DC of the first terminal and the second terminal based on the SDP offer information for the application DC in the third Invite message.

[0246] Optionally, after establishing the bootstrap DC, the second terminal can determine the DC application requested by the first terminal based on the content of the application DC in the third SDP offer information. When the second terminal has not downloaded the DC application, it can use the established bootstrap DC to download the DC application.

[0247] For example, as shown in Figure 7c, the first terminal sends a third Invite message in step 1, and the network allocates resources for the bootstrap DC to the first terminal and the second terminal in steps 2 to 12. In step 13, the second terminal replies with an SDP answer message, wherein the SDP answer message includes the media information of the bootstrap DC determined by the second terminal. Thereafter, the IMS AS can send SDP offer information of the bootstrap DC and application DC to UE-2 based on an Update message or a 200OK message, so that the second terminal can determine the DC application requested by the first terminal based on the content of the application DC in the SDP offer, establish an application DC for transmitting the application data of the DC application, and reply with the SDP answer corresponding to the bootstrap DC and application DC.

[0248] In some embodiments, the method further comprises:

[0249] When the first terminal receives the second response message including the third SDP answer information, the first terminal initiates a process of downloading the DC application, wherein the third SDP answer information is SDP answer information corresponding to the third SDP offer information.

[0250] The third SDP answer information includes SDP answer information for bootstrap DC.

[0251] For example, assuming the first terminal is UE-1, as shown in step 17 of Figure 7c , the IMS sends the SDP answers corresponding to the bootstrap DC and application DC to UE-1. The SDP answer for the bootstrap DC includes the resources reserved by the MF for UE-1. UE-1 can then establish a bootstrap DC based on the resources reserved by the MF and download the DC application for use with the communicating peer using the established bootstrap DC.

[0252] In this implementation manner, when the first terminal has not downloaded the DC application used with the communication peer, it can download the DC application based on the SDP answer information used to bootstrap DC.

[0253] Optionally, the second response message includes at least one of the following:

[0254] 183 news;

[0255] 180 news;

[0256] 200 OK message.

[0257] In some implementations, as shown in step 17 of FIG. 7 c , the IMS sends a 183 message carrying the SDP answers corresponding to the bootstrap DC and the application DC to UE- 1 .

[0258] In other implementations, the second terminal may reply to the SDP answer corresponding to the bootstrap DC and the application DC via a 180 message or a 200OK message. At this time, the network side modifies the 180 message or the 200OK message and forwards it to the first terminal.

[0259] It is worth noting that when the second terminal replies to the SDP answer corresponding to the bootstrap DC and the application DC through the 180 message, the second terminal can output incoming call prompt information, such as playing an incoming call prompt tone, displaying an incoming call prompt interface, etc.

[0260] In this embodiment, after the first terminal has obtained a list of DC applications in advance and selected a DC application to be used with the communication counterpart based on user operations, it can initiate the process of establishing the bootstrap DC and the application DC by sending a third Invite message. Compared with the embodiment described in "Case 1", this simplifies the interaction process of the first terminal.

[0261] Scenario 3

[0262] As an optional implementation manner, the target DC includes an application DC, and the first terminal sends a first message including:

[0263] The first terminal sends a fourth Invite message to the second terminal, wherein the fourth Invite message includes fourth SDP offer information and information for downloading a DC application, the fourth SDP offer information is used to establish an application DC, and the first terminal has downloaded the DC application using bootstrap DC.

[0264] In some implementations, the information for downloading the DC application is used to provide guidance for the second terminal to establish a bootstrap DC or download the DC application.

[0265] For example: as shown in Figure 7d, when DCSF-1 establishes a bootstrap DC for the first terminal so that the first terminal can download a DC application based on the bootstrap DC, the first terminal sends SDP offer information for establishing an application DC and information for downloading a DC application through step 3. Through steps 8 to 10, the second terminal can establish a bootstrap DC with the DCSF-1 based on the information for downloading the DC application, and then the second terminal determines the DC application that needs to be downloaded from DCSF-1 based on the SDP offer information of the application DC.

[0266] Optionally, the information for downloading the DC application includes at least one of the following:

[0267] SDP information of the bootstrap DC;

[0268] a preset destination address used by the first terminal when downloading the DC application;

[0269] The address of the data channel signaling function DCSF corresponding to the DC application;

[0270] The DCSF corresponding to the DC application is an identifier allocated to the first terminal;

[0271] A stream identifier (Stream ID) used by the first terminal when establishing a bootstrap DC.

[0272] In some implementations, the stream ID used by the first terminal when establishing the bootstrap DC is used to identify the source of the DC application stored in the DCSF.

[0273] There are two sources of DC applications saved in DCSF:

[0274] 1) Local network provider;

[0275] 2) Local user: a user creates and uploads a DC application.

[0276] For example, the correspondence between Stream ID and DC application source is shown in Table 1 below:

[0277] Table 1

[0278] In one embodiment, when the stream ID used by the terminal to establish the bootstrap DC is 10, it means downloading the DC application of the local user from the DCSF; when the stream ID is 0, it means downloading the DC application of the local network provider from the DCSF.

[0279] In this embodiment, the second terminal downloads the corresponding DC application based on the identifier assigned to the first terminal by the DCSF corresponding to the DC application, as well as the Stream ID used by the first terminal when establishing the bootstrap DC. For example, assume that the first terminal is UE-1 and the second terminal is UE-2. If UE-1 downloads the local user DC application, UE-2 needs to use UE-1's identifier and stream ID to indicate that it is downloading the local user DC application.

[0280] In another embodiment, the stream ID used by the second terminal when establishing the bootstrap DC may be 10 or 110, where 10 represents the local user of the first terminal and 110 represents the remote user of the second terminal.

[0281] In some implementations, at least part of the information used to download the DC application may be determined by the first terminal according to relevant information for establishing a bootstrap DC or downloading a DC application.

[0282] In other implementations, at least part of the information used to download the DC application may be provided by the DCSF corresponding to the bootstrap DC.

[0283] For example, the method further includes:

[0284] The first terminal receives first information from a first DCSF, where the first DCSF is used to establish the bootstrap DC for the first terminal, and the first information includes at least one of the following:

[0285] the address of the first DCSF;

[0286] The first DCSF is an identifier allocated to the first terminal.

[0287] In some implementations, the DCSF used to establish the application DC for the first terminal and the second terminal is a second DCSF, where the second DCSF and the first DCSF may be the same or different DCSFs.

[0288] In this embodiment, the first terminal sends information for downloading a DC application to the second terminal, enabling the second terminal to initiate the bootstrap DC establishment process based on the information and download the DC application based on the established bootstrap DC. The first terminal does not need to initiate the bootstrap DC establishment process. Furthermore, the purpose of the SDP offer information sent by the first terminal to the second terminal for establishing an application DC is the same as the purpose of the SDP offer information for establishing an application DC in "Case 2" above, and will not be further described here.

[0289] Scenario 4

[0290] As an optional implementation manner, the target DC includes an application DC, and the first terminal sends a first message including:

[0291] The first terminal sends a re-Invite message to the second terminal, wherein the re-Invite message includes fifth SDP offer information, and the fifth SDP offer information is used to establish an application DC.

[0292] In some implementations, the fifth SDP offer information may include SDP offer information for both an application DC and a bootstrap DC, and the re-Invite message may carry an instruction to establish a bootstrap DC only for the second terminal, i.e., an instruction not to establish a bootstrap DC for the first terminal. In this way, the network device can, based on this instruction, establish a bootstrap DC only for the second terminal, allowing the second terminal to download the DC application based on the established bootstrap DC. Furthermore, the network device can also establish an application DC for the first terminal and the second terminal, allowing the first and second terminals to exchange application data of the DC application via the application DC.

[0293] In other embodiments, the fifth SDP offer information may include SDP offer information for both an application DC and a bootstrap DC. In this case, the network device may, based on the first terminal already having an available bootstrap DC, establish a bootstrap DC only for the second terminal, rather than for the first terminal, so that the second terminal downloads the DC application based on the established bootstrap DC. Furthermore, the network device may also establish an application DC for the first terminal and the second terminal, so that the first and second terminals can exchange application data of the DC application via the application DC.

[0294] In this embodiment, when the bootstrap DC established by the first terminal is available, the first terminal sends a re-Invite message so that the network side only establishes a bootstrap DC for the second terminal instead of the first terminal, and establishes an application DC for the first terminal and the second terminal.

[0295] Referring to FIG4 , an embodiment of the present application provides a message processing method, the execution subject of which is the second terminal. As shown in FIG4 , the message processing method includes the following steps:

[0296] Step 401: Upon receiving a third message, the second terminal sends a 180 message corresponding to the third message if a third condition is met. The third message is used to request establishment of a target data channel DC, where the target DC includes at least one of a bootstrap DC and an application DC.

[0297] The third condition includes at least one of the following:

[0298] The third message is used to request the establishment of an application DC;

[0299] The second terminal completes downloading of the DC application corresponding to the application DC;

[0300] The second terminal completes the establishment of the bearer corresponding to the application DC.

[0301] In some embodiments, the third message corresponds to the first message in the first terminal side method embodiment, wherein the first message is a message sent by the first terminal, and after the first message is processed by the network side (such as IMS AS modifies the SDP content or adds media information of MF or enhance MRF), the processed first message is sent to the second terminal. At this time, the processed first message is the third message.

[0302] Optionally, the third message includes at least one of the following:

[0303] Invite message, re-Invite message, and Update message.

[0304] In some implementations, the bearer corresponding to the application DC may include a QoS flow or an Evolved Packet System bearer (EPS bearer).

[0305] Optionally, the method further includes:

[0306] The second terminal outputs incoming call prompt information.

[0307] In this embodiment, after sending the 180 message corresponding to the third message, the second terminal may output incoming call prompt information to implement an incoming call reminder function.

[0308] In some embodiments, if the third condition is not met, such as when the second terminal receives a third message requesting to establish a bootstrap DC, the second terminal may not send a 180 message and may not output incoming call prompt information, such as incoming call ringing, caller ID, etc.

[0309] For example: Assuming that the second terminal is UE-2, as shown in steps 12 and 13 in Figure 7b, after receiving the invite message, and the invite message carrying the SDP offer information for establishing the bootstrap DC, UE-2 replies with a 183 message, which carries the SDP answer information for the bootstrap DC.

[0310] In an embodiment of the present application, the second terminal may reply to the 180 message, that is, output a reminder (incoming call) message to the user of the second terminal, only after receiving an Invite message, a re-Invite message or an Update message for establishing a DC application, or downloading the DC application selected by the first terminal, or establishing the QoS flow corresponding to the application DC.

[0311] As an optional implementation manner, the third message includes information for downloading the DC application, and the method further includes:

[0312] The second terminal establishes a bootstrap DC according to the information for downloading the DC application;

[0313] The second terminal downloads the DC application based on the established bootstrap DC.

[0314] Optionally, after the second terminal downloads the DC application, the second terminal may execute an application DC establishment process according to the DC application.

[0315] Optionally, the information for downloading the DC application includes at least one of the following:

[0316] SDP information of the bootstrap DC;

[0317] a preset destination address used by the first terminal when downloading the DC application;

[0318] The address of the data channel signaling function DCSF corresponding to the DC application;

[0319] The DCSF corresponding to the DC application is an identifier allocated to the first terminal;

[0320] The flow identifier used by the first terminal when establishing the bootstrap DC.

[0321] Among them, the above information used to download the DC application has the same meaning and function as the information used to download the DC application in the first terminal side method embodiment, and will not be repeated here.

[0322] Optionally, if the second terminal outputs the incoming call message to the user and the user chooses to reject the call, the second terminal locally deletes the downloaded DC application immediately or retains it for a period of time before deleting the downloaded DC application.

[0323] Optionally, if the second terminal outputs an incoming call message to the user and the user chooses to answer the call, after the call ends, the second terminal may delete the downloaded DC application immediately locally or retain it for a period of time before deleting the downloaded DC application.

[0324] For example, in the embodiment shown in Figure 7d, a first terminal sends an invite message (i.e., the fourth invite message in the first terminal-side method embodiment) carrying information for downloading a DC application to a second terminal, causing the DCSF storing the DC application to establish a bootstrap DC for the second terminal. The second terminal can then download the same DC application from the DCSF based on the information used to download the DC application.

[0325] In some implementations, the second terminal establishes a bootstrap DC according to the information for downloading the DC application, including:

[0326] Upon receiving the SDP information of the bootstrap DC, the second terminal sends a temporary response message according to the SDP information of the bootstrap DC and establishes a bootstrap DC; or

[0327] Upon receiving the second information, the second terminal initiates a request to establish a bootstrap DC according to the second information, where the second information includes at least one of the following:

[0328] a preset destination address used by the first terminal when downloading the DC application;

[0329] The address of the data channel signaling function DCSF corresponding to the DC application;

[0330] The DCSF corresponding to the DC application is an identifier allocated to the first terminal;

[0331] The flow identifier used by the first terminal when establishing the bootstrap DC.

[0332] In one implementation, if the information received by the second terminal for downloading the DC application is the SDP information of the bootstrap DC, the second terminal may send a temporary response message to establish the bootstrap DC.

[0333] In another embodiment, if the information received by the second terminal for downloading the DC application includes second information, the second terminal initiates a request to establish a bootstrap DC based on the second information, and the destination address of the request to establish a bootstrap DC is the preset destination address used by the first terminal when downloading the DC application or the address of the data channel signaling function DCSF corresponding to the DC application, or the second terminal determines the DC application to be downloaded based on at least one of the identifier assigned to the first terminal by the DCSF corresponding to the DC application and the flow identifier used by the first terminal when establishing the bootstrap DC, and establishes a bootstrap DC for the second terminal by saving the DCSF with the DC application through the request to establish a bootstrap DC.

[0334] In this embodiment, when the first terminal has downloaded the DC application used with the communication peer, it can establish a bootstrap DC only for the second terminal by sending information for downloading the DC application, while omitting the process of establishing a bootstrap DC for the first terminal.

[0335] As an optional implementation manner, the second terminal downloads the DC application based on the established bootstrap DC, including:

[0336] The second terminal sends third information to the DCSF based on the established bootstrap DC, where the third information includes at least one of an identifier of the first terminal and a stream identifier streamID sent by the first terminal;

[0337] The second terminal receives the DC application sent by the DCSF.

[0338] In some embodiments, the third information can be carried in a request message for establishing a bootstrap DC, so that the DCSF that receives the request message for establishing a bootstrap DC establishes a bootstrap DC for the second terminal, and sends a DC application corresponding to the third information to the second terminal through the established bootstrap DC, that is, sends the DC application that the first terminal has downloaded and used with the communication counterpart to the second terminal.

[0339] Optionally, the method further includes:

[0340] The second terminal sends SDP answer information, where the SDP answer information is carried in the 180 message or the 183 message.

[0341] In some implementations, the SDP answer information sent by the second terminal may include SDP answer information for application DC, so that the first terminal completes the application DC establishment process according to the SDP answer information for application DC.

[0342] In an embodiment of the present application, the second terminal executes a process corresponding to the first terminal, and when the second terminal receives a third message, it may reply to the 180 message only when the third message is used to request the establishment of an application DC, or wait for the download of the DC application, or wait for the establishment of the bearer corresponding to the application DC to be completed. This can reduce the waiting time from ringing to establishing the bearer corresponding to the application DC caused by sending a ringing message when the establishment of the application DC is not requested, the DC application is not downloaded, or the bearer corresponding to the application DC is not established. In addition, the second terminal can establish a corresponding bootstrap DC based on the information used by the first terminal for downloading the DC application, so as to download the same DC application as the first terminal based on the bootstrap DC.

[0343] Referring to FIG5 , an embodiment of the present application provides a message processing method, which is executed by an IMS AS. As shown in FIG5 , the message processing method includes the following steps:

[0344] Step 501: An IMS AS receives a first message from a first terminal.

[0345] Step 502: The IMS AS performs a first operation according to the first message. The first operation includes at least one of the following:

[0346] When the first message is used to request establishment of a bootstrap data channel DC, sending second indication information to the data channel signaling function DCSF, wherein the second indication information is used to indicate that only the bootstrap DC is established;

[0347] When the first message is used to request establishment of a bootstrap DC and an application DC, sending a first SDP offer message to the second terminal, where the first SDP offer message is used to establish the bootstrap DC; and when the IMS AS receives a first SDP answer message from the second terminal, sending a second SDP offer message to the second terminal, where the first SDP answer message is SDP answer information corresponding to the first SDP offer message, and the second SDP offer message is used to establish the application DC;

[0348] In the case where the first message is used to request the establishment of an application DC, a fourth message is sent to the DCSF, where the fourth message is used to notify the DCSF to only establish a bootstrap DC for the second terminal (ie, not to establish a bootstrap DC for the first terminal).

[0349] In the embodiment of the present application, the first message, the first SDP offer information, the first SDP answer information, and the second SDP offer information have the same meaning and function as the first message, the first SDP offer information, the first SDP answer information, and the second SDP offer information in the method embodiment executed by the first terminal and the second terminal in the above-mentioned embodiment of the present application, and are not repeated here.

[0350] In one embodiment, when the first message carries only SDP offer information of bootstrap DC but not SDP offer information of application DC, the IMS AS may determine that the first message is used to request to establish only bootstrap DC but not application DC, thereby sending second indication information to DCSF.

[0351] In another embodiment, when the first message carries first indication information, the IMS AS may send second indication information to the DCSF based on the first indication information, wherein the first indication information is used to indicate that only a bootstrap DC is to be established, but not an application DC.

[0352] Optionally, the second indication information is used to indicate at least one of the following:

[0353] Only the bootstrap DC is established, that is, no application DC is established;

[0354] Only a bootstrap DC is established for the first terminal, that is, no bootstrap DC is established for the second terminal, and no application DC is established;

[0355] A unilateral bootstrap DC is established, that is, a bootstrap DC is not established for the peer end (second terminal), and an application DC is not established.

[0356] In some embodiments, the second indication information includes at least one of the following:

[0357] Only carries the SDP offer information corresponding to the bootstrap DC;

[0358] The SDP offer information corresponding to the application DC is not carried;

[0359] Preset destination address.

[0360] In some implementations, the preset destination address includes at least one of the following:

[0361] The customer service phone number of the telecommunications operator;

[0362] The first terminal's own telephone number;

[0363] DCSF telephone number;

[0364] The telephone number of the IMS AS;

[0365] Used to indicate that only the bootstrap DC is established.

[0366] In some embodiments, when the first message is used to request the establishment of a bootstrap DC and an application DC, and when a first SDP offer information is sent to the second terminal, the first SDP offer information is carried in a third message, and the third message has the same meaning as the third message in the message processing method embodiment on the second terminal side, and will not be repeated here.

[0367] In some embodiments, after the IMS AS sends the first SDP offer information to the second terminal, if it receives the first SDP answer information from the second terminal, it means that the SDP answer information for establishing the bootstrap DC has been obtained. Thereafter, based on the SDP offer information for the application DC in the first message, a second SDP offer information can be sent to the second terminal to request the establishment of the application DC.

[0368] Of course, after sending the second SDP offer information to the second terminal, the IMS AS can receive the second SDP answer information from the second terminal, that is, the SDP answer information for the application DC. Thereafter, the first SDP answer information and the second SDP answer information can be sent to the first terminal so that the first terminal can complete the process of establishing the bootstrap DC and the application DC.

[0369] In some embodiments, when a first terminal uses an established bootstrap DC to download a DC application and requests to use the DC application to interact with a second terminal for application data, a first message is sent to the second terminal to request the establishment of an application DC for transmitting the application data of the DC application. At this time, the second terminal may not have downloaded the DC application requested by the first terminal, or has not established a bootstrap DC with the DCSF that stores the DC application. At this time, the IMS sends a fourth message to the DCSF to notify the DCSF to only establish a bootstrap DC for the second terminal, and not to establish a bootstrap DC for the first terminal.

[0370] In some other implementations, when the first message is used to establish an application DC, sending a fourth message to the DCSF includes:

[0371] In the case where the first message is a re-Invite message from the first terminal and the destination address is the second terminal, a fourth message is sent to the DCSF, wherein the re-Invite message includes second SDP offer information and information for downloading the DC application, and the second SDP offer information is used to establish an application DC.

[0372] Optionally, the fourth message includes third indication information, where the third indication information is used to instruct to establish only the bootstrap D of the second terminal, that is, to instruct to establish the bootstrap DC of the first terminal.

[0373] Of course, the DCSF may, based on the record of establishing the bootstrap DC, establish a bootstrap DC only for the second terminal based on the second SDP offer information, but not for the first terminal, if it determines that the first terminal has established a bootstrap DC with it and the bootstrap DC is available.

[0374] In this embodiment, a first terminal uses an established bootstrap DC to download a DC application, requests to use the DC application to exchange application data with a second terminal, and sends information for downloading the DC application to the second terminal, so that the second terminal can establish a bootstrap DC corresponding to the first terminal based on the information for downloading the DC application and download the same DC application as the first terminal. At this time, the second terminal may not have downloaded the DC application requested by the first terminal, or may not have established a bootstrap DC with the DCSF that stores the DC application. Therefore, the IMS sends a fourth message to the DCSF to notify the DCSF to establish only a bootstrap DC for the second terminal, and not to establish a bootstrap DC for the first terminal. In this way, the second terminal can use the established bootstrap DC to download the same DC application as the first terminal.

[0375] It should be noted that in the embodiment of the present application, the various steps in the message processing method executed by the IMS AS correspond to the steps in the method embodiments executed by the first terminal and the second terminal in the above-mentioned embodiment of the present application. The message processing method executed by the IMS AS cooperates with the DC establishment method on the first terminal side and the message processing method on the second terminal side to jointly achieve the purpose of the DC establishment process. It can achieve beneficial effects corresponding to the DC establishment method on the first terminal side and the message processing method on the second terminal side, which will not be repeated here.

[0376] As an optional implementation manner, when the first message is used to request establishment of a bootstrap DC, sending the second indication information to the DCSF includes:

[0377] When the first message carries the first indication information or the first message only carries the SDP of the bootstrap DC (i.e., does not carry the SDP of the application DC), the second indication information is sent to the data channel signaling function DCSF, wherein the first indication information is used to indicate that only the bootstrap DC is established without establishing the application DC.

[0378] Optionally, the second indication information is used to indicate at least one of the following:

[0379] Only the bootstrap DC is established;

[0380] Only establish a bootstrap DC for the first terminal;

[0381] Establish a unilateral bootstrap DC.

[0382] Optionally, the second indication information includes at least one of the following:

[0383] Only carries the SDP offer information corresponding to the bootstrap DC;

[0384] The SDP offer information corresponding to the application DC is not carried;

[0385] Preset destination address.

[0386] Optionally, the preset destination address includes at least one of the following:

[0387] The customer service phone number of the telecommunications operator;

[0388] The first terminal's own telephone number;

[0389] DCSF telephone number;

[0390] The telephone number of the IMS AS;

[0391] Used to indicate that only the bootstrap DC is established.

[0392] Among them, the above-mentioned first indication information and second indication information have the same meaning and function as the first indication information and second indication information in the first terminal side and second terminal side method embodiments, and will not be repeated here.

[0393] As an optional implementation, the method further includes:

[0394] In a case where the first message is used to request establishment of a bootstrap DC, the IMS AS sends SDP answer information of the bootstrap DC to the first terminal.

[0395] In some implementations, when the first message is used to request establishment of a bootstrap DC, a bootstrap DC may be established only for the first terminal, while a bootstrap DC is not established for the second terminal, and an application DC is not established.

[0396] For example: assuming that the first terminal is UE-1, as shown in Figure 7a, in steps 5 to 8, DCSF only reserves the media information of MDC1 for UE-1, and instructs IMS AS to establish a connection with MF for UE-1; when IMS AS discovers MF / enhance MRF, it instructs MF to reserve media resource information for UE-1 and sends a response message to DCSF to inform DCSF whether the resource reservation is successful, as well as the data channel media resource information negotiated for MDC1. After DCSF sends the response message to IMS AS, IMS AS can send the SDP answer information of the bootstrap DC to the first terminal through a 200OK message.

[0397] As an optional implementation, the method further includes:

[0398] Upon receiving the second SDP answer information of the second terminal, the IMS AS sends third SDP answer information to the first terminal, wherein the third SDP answer information is SDP answer information of the bootstrap DC and the application DC.

[0399] In some implementations, the SDP answer information of the bootstrap DC may include resource information reserved by the MF for UE-1.

[0400] Among them, the above-mentioned second SDP answer information and third SDP answer information have the same meaning and function as the second SDP answer information and third SDP answer information in the first terminal side and second terminal side method embodiments, and are not repeated here.

[0401] Referring to FIG6 , an embodiment of the present application provides a resource allocation method, which is executed by a DCSF. As shown in FIG6 , the resource allocation method includes the following steps:

[0402] Step 601: The DCSF receives a fourth message from the IMS AS.

[0403] Step 602: When the fourth message is used to notify the establishment of a bootstrap DC only for the first terminal, the DCSF allocates or reserves resources corresponding to the bootstrap DC for the first terminal.

[0404] Step 603: When the fourth message is used to notify the establishment of a bootstrap DC only for the second terminal, the DCSF allocates or reserves resources corresponding to the bootstrap DC for the second terminal.

[0405] It should be noted that, in the following embodiments, the DCSF may only execute one of the above steps 602 and 603. The method flowchart shown in FIG6 is only an example, and the execution of step 602 or step 603 by the DCSF is not specifically limited here.

[0406] In one implementation, when the DCSF executes step 602, a unilateral bootstrap DC may be established for the first terminal.

[0407] For example, when the first condition is met, a first message is sent to the first terminal to request establishment of a bootstrap DC for the first terminal, so that the first terminal can download a list of DC applications based on the bootstrap DC.

[0408] In another implementation, when the DCSF executes step 603 , a unilateral bootstrap DC may be established for the second terminal.

[0409] For example: when the first terminal has downloaded the DC application used with the communication counterpart, the first terminal sends a first message to request the establishment of an application DC. At this time, if the second terminal has not downloaded the DC application or has not established a bootstrap DC with the DCSF that stores the DC application, the network side establishes a bootstrap DC for the second terminal based on the first message. At this time, the DCSF only allocates or reserves resources corresponding to the bootstrap DC for the second terminal, and does not allocate or reserve resources corresponding to the bootstrap DC for the first terminal.

[0410] In the embodiment of the present application, the fourth message has the same meaning and function as the fourth message in the embodiment of the method executed by the IMS AS in the above embodiment of the present application, and will not be repeated here.

[0411] In addition, in the embodiment of the present application, each step in the resource allocation method executed by DCSF corresponds to the steps in the method embodiment executed by the first terminal, the second terminal and the IMS AS in the above-mentioned embodiment of the present application, and the resource allocation method executed by DCSF cooperates with the DC establishment method on the first terminal side, the message processing method on the second terminal side and the message processing method on the IMS AS side to jointly achieve the purpose of the DC establishment process. It can achieve beneficial effects corresponding to the DC establishment method on the first terminal side, the message processing method on the second terminal side and the message processing method on the IMS AS side, and will not be repeated here.

[0412] As an optional implementation manner, when the fourth message carries the second indication information, the fourth message is used to notify that only the bootstrap DC is established for the first terminal, wherein the second indication information is used to indicate that only the bootstrap DC of the first terminal is established; or,

[0413] When the fourth message is triggered based on the first terminal initiating the first Invite message to a preset destination address, the fourth message is used to notify that a bootstrap DC is established only for the first terminal, and not for the second terminal, wherein the first Invite message includes Session Description Protocol SDP offer information for establishing a bootstrap DC.

[0414] Among them, the second indication information, the preset destination address, and the first Invite message have the same meaning and function as the second indication information, the preset destination address, and the first Invite message in the aforementioned first terminal side and IMS AS side method embodiments of the present application, and are not repeated here.

[0415] Optionally, the second indication information is used to indicate at least one of the following:

[0416] Only the bootstrap DC is established;

[0417] Only establish a bootstrap DC for the first terminal;

[0418] Establish a unilateral bootstrap DC.

[0419] Optionally, the second indication information includes at least one of the following:

[0420] Only carries the SDP offer information corresponding to the bootstrap DC;

[0421] The SDP offer information corresponding to the application DC is not carried;

[0422] Preset destination address.

[0423] Optionally, the preset destination address includes at least one of the following:

[0424] The customer service phone number of the telecommunications operator;

[0425] The first terminal's own telephone number;

[0426] DCSF telephone number;

[0427] The telephone number of the IMS AS;

[0428] Used to indicate that only the bootstrap DC is established.

[0429] As an optional implementation, when the fourth message carries the third indication information, the fourth message is used to notify that only the bootstrap DC of the second terminal is established, and the third indication information is used to indicate that only the bootstrap DC of the second terminal is established, without establishing the bootstrap DC of the first terminal.

[0430] The third indication information has the same meaning and function as the third indication information in the aforementioned IMS AS side method embodiment of this application, and will not be described in detail here.

[0431] As an optional implementation, the method further includes:

[0432] In a case where the first terminal downloads the DC application based on the bootstrap DC, the DCSF sends information for downloading the DC application to the first terminal.

[0433] Optionally, the information for downloading the DC application includes at least one of the following:

[0434] the address of the DCSF;

[0435] The DCSF is an identifier allocated to the first terminal.

[0436] Among them, the information used to download the DC application has the same meaning and function as the information provided by DCSF for downloading the DC application in the first terminal side method embodiment mentioned above in this application, and will not be repeated here.

[0437] To facilitate understanding of the DC establishment method, message processing method, and resource allocation method provided in the embodiments of the present application, taking the first terminal as UE-1, the second terminal as UE-2, the DCSF used to establish the bootstrap DC as DCSF-1, and the DCSF used to establish the application DC as DCSF-1 as an example, the interaction process between UE-1, UE-2, and network-side devices such as the IMS AS, DCSF-1, and DCSF-1 is illustrated below:

[0438] Example 1

[0439] This embodiment shows a process for UE-1 to obtain a DC application list before a call. As shown in FIG7 a , the process includes the following steps:

[0440] Step 0. UE-1 determines whether the first condition is met.

[0441] The first condition includes at least one of the following:

[0442] Turn on the UE-1 or disable flight mode;

[0443] UE-1 completes IMS registration or IMS re-registration;

[0444] UE-1's dialer app is started;

[0445] The default APP of UE-1 is started (for example, a default APP dedicated to establishing DC, which may be separate from the dial-up APP).

[0446] Wherein, only when it is determined in step 0 that the first condition is satisfied, the subsequent steps are executed.

[0447] Step 1. UE-1 sends an Invite message (ie, the first Invite message), which carries only the SDP offer information corresponding to the bootstrap DC in the SDP, but does not carry the SDP offer information corresponding to the application DC.

[0448] The destination address of the Invite message is a preset destination address, which may be a called number dedicated to establishing a bootstrap DC, such as a customer service phone number of a communication operator, or UE-1's own communication number.

[0449] Step 2. Same as step 2 in Figure 2.

[0450] Optionally, the Invite message includes instruction information for establishing only a bootstrap DC, that is, instruction information for not establishing an application DC.

[0451] Step 3. The IMS AS sends a Nimsas_SessionEventControl_Notify message to the DCSF.

[0452] Optionally, the Nimsas_SessionEventControl_Notify message includes second indication information, where the second indication information indicates at least one of the following:

[0453] Only the instructions for establishing the bootstrap DC are provided;

[0454] Only indicates the establishment of a bootstrap DC for the calling UE;

[0455] Instructions for establishing a unilateral bootstrap DC.

[0456] The IMS AS may determine that the second indication information is included based on the fact that the Invite message sent by UE-1 only carries the SDP of the bootstrap DC but not the SDP of the application DC; or, the second indication information is included based on the indication information carried in the Invite message sent by UE-1.

[0457] Step 4: The DCSF determines that only a bootstrap DC needs to be established for the calling UE. The DCSF makes this determination based on at least one of the following conditions:

[0458] 1) The called number is a special number;

[0459] 2) Second indication information sent by the IMS AS.

[0460] Optionally, the called number includes at least one of the following:

[0461] The customer service phone number of the telecommunications operator;

[0462] The first terminal's own telephone number;

[0463] DCSF telephone number;

[0464] The telephone number of the IMS AS;

[0465] Used to indicate that only the bootstrap DC is established.

[0466] Step 5: DCSF reserves the media information of MDC1 only for UE-1, but does not reserve the media information of MDC1 for UE-2.

[0467] Step 6. The DCSF sends a Nimsas_MediaControl_MediaInstruction message to the IMS AS, instructing the IMS AS to establish a connection between UE-1 and the MF.

[0468] Step 7. The IMS AS discovers the MF / enhance MRF.

[0469] Step 8. The IMS AS instructs the MF on the media resource information reserved for the calling party.

[0470] Steps 9 and 10 are the same as steps 9 and 10 in FIG2 .

[0471] Step 11. The IMS AS sends a 200 OK message to UE-1, carrying an SDP answer.

[0472] Step 12. UE-1 downloads the DC application list through the bootstrap DC.

[0473] Optionally, UE-1 downloads several frequently used applications in the application list, such as screen sharing, file transfer, positioning, etc.

[0474] Optionally, UE-1 releases the established bootstrap DC.

[0475] For example, after establishing a bootstrap DC, UE-1 starts a timer. If no request to use the bootstrap DC (for example, downloading a DC application) or to establish an application DC is received before the timer expires, UE-1 releases the bootstrap DC through a Bye message.

[0476] Through embodiment 1, UE-1 can obtain the available DC application list and display to the user on the interface of UE-1 which DC applications can be used to communicate with UE-2.

[0477] Example 2

[0478] In this embodiment, UE-1 obtains an application list before a call. Afterwards, it can use the application list to select a DCapplication to use. Based on the selected DCapplication, it first establishes a bootstrap DC and then an application DC. As shown in Figure 7b, this process includes the following steps:

[0479] Step 1. When the user selects a DC application from the application list to establish an application DC with UE-2, UE-1 first initiates a bootstrap DC establishment request (i.e., the second Invite message).

[0480] Steps 2 to 15 are the same as steps 2 to 15 in Figure 2. The differences are as follows: after receiving the bootstrap DC establishment request, UE-2 does not reply with a 180 ringing message and does not display an incoming call interface to the called user.

[0481] Step 16. Optionally, UE-1 downloads the application list.

[0482] It should be noted that step 16 is an optional step. When UE-1 downloads the application list through the process shown in embodiment 1 before the call, step 16 may not be performed.

[0483] Step 17. UE-1 downloads the DC application selected by the user.

[0484] Step 18. UE-1 establishes an application DC through an Update message, which contains the contents of the bootstrap DC and the application DC.

[0485] It should be noted that, in step 13, if UE-2 responds with 200OK, then in step 18, a re-Invite message is sent, and the message includes the content of the bootstrap DC and the content of the application DC.

[0486] Steps 19 to 24 are the same as steps 24 to 29 in FIG. 2 .

[0487] Step 25. UE-2 replies with a 183 message, carrying the SDP answer corresponding to the application DC.

[0488] It should be noted that in addition to the 183 message in step 25, UE-2 can also reply with a 180 message carrying the SDP answer for application DC. In this case, step 25 includes the contents of step 27 in Figure 7b, i.e., UE-2 replies with a 180 message and plays an incoming call alert tone to the user.

[0489] Step 26. Optionally, the called network side establishes a QoS flow corresponding to application DC for UE-2.

[0490] It should be noted that, when UE-2 replies to the 180 message in step 25 to carry the SDP answer of application DC, the establishment of the QoS flow is performed after UE-2 replies to the 180 message.

[0491] If UE-2 replies with the 183 message in step 25, step 27 is executed.

[0492] Step 27. UE-2 replies with a 180 message and plays an incoming call prompt tone to the user.

[0493] It should be noted that UE-2 can play prompt sounds in the following situations:

[0494] Receive the Invite message in step 23;

[0495] After downloading DC application DC;

[0496] Complete the establishment of the QoS flow corresponding to the application DC.

[0497] Step 28. When the called user agrees to use the DC application, UE-2 sends a 200 OK message.

[0498] Steps 29 to 31 are the same as steps 31 to 33 in Figure 2. The difference is that in this embodiment, the 200OK message does not carry SDP answer information.

[0499] Steps 32 to 34 are the same as steps 35 to 37 in FIG. 2 .

[0500] It should be noted that step 32 in this embodiment can also be executed after receiving the SDP answer. For example, if the 183 message carries the SDP answer, step 32 is executed after step 25; or if the 180 message carries the SDP answer, step 32 is executed after step 27.

[0501] Example 3

[0502] In this embodiment, UE-1 obtains an application list and commonly used DCapplications before a call. Afterwards, when the user selects a downloaded DCapplication, it can simultaneously request the establishment of a bootstrap DC and an application DC based on the selected DCapplication. As shown in FIG7 c , this process includes the following steps:

[0503] Step 0. UE-1 executes the process of embodiment 1 and pre-downloads the commonly used DC application.

[0504] Step 1. The user of UE-1 chooses to use the pre-downloaded DC application to communicate with UE-2, so UE-1 sends an Invite message (i.e., the third Invite message) with the destination address being UE-2, and carries the SDP offer information of the bootstrap DC and application DC in the SDP.

[0505] Steps 2 to 12 are the same as steps 2 to 12 in FIG. 2 .

[0506] Step 13. UE-2 replies with an SDP answer via a 183 response message.

[0507] The SDP answer in this step contains the media information of the bootstrap DC determined by UE-2.

[0508] Step 14. The IMS AS sends the SDP offer information of the bootstrap DC and application DC to UE-2 through an Update message.

[0509] It should be noted that if UE-2 replies with a 200OK message in step 13 as shown in FIG7c , the IMS AS sends SDP offer information of bootstrap DC and application DC to UE-2 via a re-Invite message in step 18 .

[0510] Step 15. UE-2 determines the DC application requested by UE-1 based on the content of the application DC in the SDP offer.

[0511] Optionally, when UE-2 determines that the DC application requested by UE-1 has not been downloaded, UE-2 downloads the DC application through bootstrap DC.

[0512] Step 16. UE-2 replies with the SDP answers corresponding to the bootstrap DC and application DC via the 183 message.

[0513] It should be noted that, in addition to the 183 message, UE-2 can also carry the SDP answer of application DC in the 180 message. In this case, as shown in FIG7c , step 22 can be omitted and the actions of step 22 can be merged into step 25.

[0514] Step 17. The IMS sends the SDP answers corresponding to the bootstrap DC and application DC to UE-1.

[0515] The SDP answer for the bootstrap DC includes the resources reserved by the MF for UE-1.

[0516] Steps 18 to 19: The network of UE-2 establishes a dedicated QoS flow for UE-2 to transmit bootstrap DC; the network of UE-1 establishes a dedicated QoS flow for UE-1 to transmit bootstrap DC.

[0517] Step 20. Optionally, UE-1 downloads the DC application list through the bootstrap DC.

[0518] Step 21. Optionally, UE-1 updates the DC application selected by the user through the bootstrap DC.

[0519] Step 22. UE-2 replies with a 180 message and plays an incoming call prompt tone to the user.

[0520] It should be noted that UE-2 can play prompt sounds in the following situations:

[0521] Receive the Invite message in step 12;

[0522] After downloading DC application DC;

[0523] Complete the establishment of the QoS flow corresponding to the application DC.

[0524] Steps 23 to 26 are the same as steps 30 to 33 in Figure 2. The difference is that in this embodiment, the 200OK message does not carry SDP answer information.

[0525] Steps 27 to 28 are the same as steps 36 to 37 in FIG. 2 .

[0526] Example 4

[0527] In this embodiment, UE-1 downloads an application list and commonly used DCapplications from DCSF-1 before a call. Afterwards, when the user selects a downloaded DCapplication, UE-1 can request to establish an application DC based on the selected DCapplication and send information for downloading the selected DCapplication to UE-2, so that UE-2 can establish a bootstrap DC with DCSF-1 that stores the DCapplication based on the information for downloading the selected DCapplication. As shown in Figure 7d, this process includes the following steps:

[0528] Step 1. UE-1 executes the process of embodiment 1 and pre-downloads the commonly used DC application.

[0529] Optionally, DCSF-1 sends DC application download information to UE-1, including at least one of the following:

[0530] The address of DCSF-1;

[0531] The identifier allocated by DCSF-1 to UE-1.

[0532] Step 2. Optionally, UE-1 downloads the DC application according to the user's selection.

[0533] For example: When the selected DC application has an update, download the updated DC application.

[0534] Step 3. UE-1 communicates with UE-2 using the DC application selected by the user.

[0535] In this step 3, UE-1 sends an Invite message (ie, the fourth Invite message), the destination address of which is UE-2. The SDP of the Invite message carries the SDP offer information of the application DC and the information for downloading the DC application.

[0536] The information used to download the DC application includes at least one of the following:

[0537] SDP information of the bootstrap DC;

[0538] a preset destination address used by the first terminal when downloading the DC application;

[0539] The address of the data channel signaling function DCSF corresponding to the DC application;

[0540] The DCSF corresponding to the DC application is an identifier allocated to the first terminal;

[0541] The flow identifier used by the first terminal when establishing the bootstrap DC.

[0542] Steps 4 to 9 are the same as steps 24 to 28 in FIG2 . The differences include: in this embodiment, the re-Invite message in FIG2 is replaced with an Invite message, and the Invite message additionally carries information for downloading the DC application.

[0543] It should be noted that the DCSF-1 used when UE-1 downloads the DC application and the DCSF-2 used when UE-2 establishes the application DC can be the same or different, and no specific limitation is made here.

[0544] Step 10. UE-2 initiates the process of establishing a bootstrap DC based on the information downloaded by the DC application. For the specific process, refer to the process of initiating the process of establishing a bootstrap DC in the first embodiment, which will not be repeated here.

[0545] Optionally, UE-2 may carry the identifier of UE-1 and the stream ID sent by UE-1 during the establishment of the bootstrap DC.

[0546] Step 11. Optionally, if UE-2 has not downloaded the DC application selected by UE-1, it downloads the DC application through the established bootstrap DC.

[0547] Steps 12 to 20 are the same as steps 16 to 28 in Figure 2. The difference is that in this embodiment, the SDP answer replied by UE-2 only includes the SDP answer corresponding to the application DC, but does not include the SDP answer corresponding to the bootstrap DC.

[0548] Example 5

[0549] In this embodiment, UE-1 downloads the application list and commonly used DCapplication from DCSF-1 before a call. Afterwards, when UE-1 receives a request to establish an application DC, if the bootstrap DC can continue to be used, it can request to establish an application DC based on the selected DCapplication and establish a bootstrap DC corresponding to the DCapplication information for UE-2. As shown in Figure 7e, this process includes the following steps:

[0550] Step 1. UE-1 executes the process of embodiment 1 and pre-downloads the commonly used DC application.

[0551] Step 2. Same as step 2 in Example 4.

[0552] Step 3. UE-1 communicates with UE-2 using the DC application selected by the user.

[0553] In this step, UE-1 sends a re-Invite message with the destination address being UE-2. The SDP of the re-Invite message carries the SDP offer information of the bootstrap DC and application DC.

[0554] Step 4. The IMS AS sends a notification message (ie, the fourth message) to the DCSF.

[0555] Optionally, the notification message may include instruction information for establishing a bootstrap DC for the opposite UE.

[0556] Step 5. The DCSF determines to establish a bootstrap DC for UE-2 according to the notification message.

[0557] Step 6. The DCSF only creates DC media information for UE-2, but does not create DC media information for UE-1.

[0558] In this step, DCSF may execute the step of creating DC media information only for UE-2 according to the instruction information in the above-mentioned step 4 of this embodiment; or it may execute the step of creating DC media information only for UE-2 according to its own judgment, for example: DCSF records that media information has only been allocated to the calling UE, and when a request to establish a bootstrap DC is received again, DC media information is only created for the opposite UE.

[0559] Step 7. Same as step 6 in Figure 2.

[0560] Step 8. The IMS AS requests the MF / MRF to allocate media resources for the opposite UE. The MF only allocates MDC1 media resources for the opposite UE, but does not allocate MDC1 media resources for UE-1.

[0561] Step 9. Same as Step 8 to Step 28 in Example 3.

[0562] The DC establishment method provided in the embodiment of the present application can be executed by a DC establishment device. In the embodiment of the present application, the DC establishment method executed by the DC establishment device is taken as an example to illustrate the DC establishment device provided in the embodiment of the present application.

[0563] As shown in FIG8 , the DC establishment device provided in the embodiment of the present application may be a device corresponding to the first terminal. As shown in FIG8 , the DC establishment device 800 includes the following modules:

[0564] A first sending module 801 is configured to send a first message requesting establishment of a target DC without establishing a voice, video, or message media connection. The target DC includes at least one of a bootstrap DC and an application DC.

[0565] The first establishing module 802 is configured to receive a first response message and establish the target DC according to the first response message.

[0566] Optionally, the first sending module 801 is specifically configured to:

[0567] A first Invite message is sent to a preset destination address, where the first Invite message includes Session Description Protocol (SDP) offer information for establishing the bootstrap DC.

[0568] Optionally, the first Invite message further includes first indication information, where the first indication information is used to indicate that only a bootstrap DC is to be established.

[0569] Optionally, the first sending module 801 is specifically configured to:

[0570] When the first condition is met, sending the first message;

[0571] The first condition includes at least one of the following:

[0572] Turning on the first terminal;

[0573] The first terminal releases or turns off the flight mode;

[0574] The first terminal completes IMS registration or IMS re-registration;

[0575] The dialing application APP of the first terminal is started;

[0576] A preset APP of the first terminal is started, and the preset APP is used to establish the target DC.

[0577] Optionally, the DC establishing device 800 further includes:

[0578] The first downloading module is used to download an application list based on the bootstrap DC.

[0579] Optionally, the DC establishing device 800 further includes:

[0580] The second downloading module is configured to download the first DC application in the application list based on the bootstrap DC.

[0581] Optionally, the DC establishing device 800 further includes:

[0582] A release module is used to release the bootstrap DC.

[0583] Optionally, the release module is specifically configured to:

[0584] If a second condition is met, the bootstrap DC is released. The second condition includes at least one of the following:

[0585] When the first timer times out, the first terminal does not use the bootstrap DC to send a message or data;

[0586] When the first timer times out, the first terminal does not initiate a request message for establishing an application DC;

[0587] The first timer is started when the first terminal successfully establishes the bootstrap DC, or is started after the first terminal downloads the application list, or is started after the first DC application is downloaded.

[0588] Optionally, the target DC includes a bootstrap DC and an application DC, and the first sending module 801 includes:

[0589] A first sending unit is configured to send a second Invite message to the second terminal, wherein the second Invite message includes first SDP offer information, where the first SDP offer information is used to establish a bootstrap DC;

[0590] The first transmission unit is used to send a second message to the second terminal when receiving the first SDP response answer information, wherein the second message includes second SDP offer information, wherein the first SDP answer information is the SDP answer information corresponding to the first SDP offer information, and the second SDP offer information is used to establish an application DC.

[0591] Optionally, the first transmission unit is specifically configured to:

[0592] When the first terminal receives the 183 response message including the first SDP answer information, sending an Update message; or

[0593] When the first terminal receives the 200OK message including the first SDP answer information, it sends a re-Invite message.

[0594] Optionally, the target DC includes a bootstrap DC and an application DC. The first sending module 801 is specifically configured to:

[0595] A third Invite message is sent to the second terminal, wherein the third Invite message includes third SDP offer information, and the third SDP offer information is used to establish a bootstrap DC and an application DC.

[0596] Optionally, the DC establishing device 800 further includes:

[0597] The initiating module is configured to initiate a process of downloading a DC application upon receiving a second response message containing third SDP answer information, wherein the third SDP answer information is SDP answer information corresponding to the third SDP offer information.

[0598] Optionally, the second response message includes at least one of the following:

[0599] 183 news;

[0600] 180 news;

[0601] 200 OK message.

[0602] Optionally, the target DC includes an application DC, and the first sending module 801 is specifically configured to:

[0603] A fourth Invite message is sent to the second terminal, wherein the fourth Invite message includes fourth SDP offer information and information for downloading a DC application, the fourth SDP offer information is used to establish an application DC, and the first terminal has downloaded the DC application using bootstrap DC.

[0604] Optionally, the information for downloading the DC application includes at least one of the following:

[0605] SDP information of the bootstrap DC;

[0606] a preset destination address used by the first terminal when downloading the DC application;

[0607] The address of the data channel signaling function DCSF corresponding to the DC application;

[0608] The DCSF corresponding to the DC application is an identifier allocated to the first terminal;

[0609] The flow identifier used by the first terminal when establishing the bootstrap DC.

[0610] Optionally, the DC establishing device 800 further includes:

[0611] The third receiving module is configured to receive first information from a first DCSF, where the first DCSF is used to establish the bootstrap DC for the first terminal, and the first information includes at least one of the following:

[0612] the address of the first DCSF;

[0613] The first DCSF is an identifier allocated to the first terminal.

[0614] Optionally, the target DC includes an application DC, and the first sending module 801 is specifically configured to:

[0615] A re-Invite message is sent to the second terminal, wherein the re-Invite message includes fifth SDP offer information, and the fifth SDP offer information is used to establish an application DC.

[0616] The message processing method provided in the embodiment of the present application can be executed by a message processing device. In the embodiment of the present application, the message processing device provided in the embodiment of the present application is described by taking the message processing method executed by the message processing device as an example.

[0617] As shown in FIG9 , a message processing device provided in an embodiment of the present application may be a device corresponding to the second terminal. As shown in FIG9 , the message processing device 900 includes the following modules:

[0618] The first transmission module 901 is configured to, upon receiving a third message, send a 180 message corresponding to the third message if a third condition is met, wherein the third message is used to request establishment of a target data channel DC, where the target DC includes at least one of a bootstrap DC and an application DC;

[0619] The third condition includes at least one of the following:

[0620] The third message is used to request the establishment of an application DC;

[0621] The second terminal completes downloading of the DC application corresponding to the application DC;

[0622] The second terminal completes the establishment of the bearer corresponding to the application DC.

[0623] Optionally, the third message includes the information message processing device 900 for downloading the DC application, and further includes:

[0624] An establishment module, configured to establish a bootstrap DC according to the information for downloading the DC application;

[0625] The third downloading module is used to download the DC application based on the established bootstrap DC.

[0626] Optionally, the information for downloading the DC application includes at least one of the following:

[0627] SDP information of the bootstrap DC;

[0628] a preset destination address used by the first terminal when downloading the DC application;

[0629] The address of the data channel signaling function DCSF corresponding to the DC application;

[0630] The DCSF corresponding to the DC application is an identifier allocated to the first terminal;

[0631] The flow identifier used by the first terminal when establishing the bootstrap DC.

[0632] Optionally, the establishing module is specifically configured to:

[0633] When the second terminal receives the SDP information of the bootstrap DC, the second terminal sends a temporary response message according to the SDP information of the bootstrap DC and establishes a bootstrap DC; or

[0634] When the second terminal receives the second information, the second terminal initiates a request to establish a bootstrap DC according to the second information, where the second information includes at least one of the following:

[0635] a preset destination address used by the first terminal when downloading the DC application;

[0636] The address of the data channel signaling function DCSF corresponding to the DC application;

[0637] The DCSF corresponding to the DC application is an identifier allocated to the first terminal;

[0638] The flow identifier used by the first terminal when establishing the bootstrap DC.

[0639] Optionally, the third download module includes:

[0640] a second sending unit, configured to send third information to the DCSF based on the established bootstrap DC, where the third information includes at least one of an identifier of the first terminal and a stream identifier streamID sent by the first terminal;

[0641] The first receiving unit is configured to receive the DC application sent by the DCSF.

[0642] Optionally, the third message includes at least one of the following:

[0643] Invite message, re-Invite message, and Update message.

[0644] Optionally, the message processing device 900 further includes:

[0645] Output module, used to output incoming call prompt information.

[0646] Optionally, the message processing device 900 further includes:

[0647] The second sending module is configured to send SDP answer information, where the SDP answer information is carried in the 180 message or the 183 message.

[0648] As shown in FIG10 , another message processing device provided in an embodiment of the present application may be a device corresponding to an IMS AS. As shown in FIG10 , the message processing device 1000 includes the following modules:

[0649] A first receiving module 1001 is configured to receive a first message from a first terminal;

[0650] The execution module 1002 is configured to perform a first operation according to the first message, where the first operation includes at least one of the following:

[0651] When the first message is used to request establishment of a bootstrap data channel DC, sending second indication information to the data channel signaling function DCSF, wherein the second indication information is used to indicate that only the bootstrap DC is established;

[0652] When the first message is used to request establishment of a bootstrap DC and an application DC, sending a first SDP offer message to the second terminal, where the first SDP offer message is used to establish the bootstrap DC; and when the IMS AS receives a first SDP answer message from the second terminal, sending a second SDP offer message to the second terminal, where the first SDP answer message is SDP answer information corresponding to the first SDP offer message, and the second SDP offer message is used to establish the application DC;

[0653] In the case where the first message is used to request the establishment of an application DC, a fourth message is sent to the DCSF, where the fourth message is used to notify the DCSF to only establish a bootstrap DC for the second terminal.

[0654] Optionally, the execution module 1002 includes:

[0655] The third sending unit is used to send a fourth message to the DCSF when the first message is a re-Invite message from the first terminal and the destination address is the second terminal, wherein the re-Invite message includes second SDP offer information and information for downloading the DC application, and the second SDP offer information is used to establish an application DC.

[0656] Optionally, the fourth message includes third indication information, where the third indication information is used to indicate that only the bootstrap DC of the second terminal is to be established.

[0657] Optionally, the execution module 1002 includes:

[0658] The fourth sending unit is used to send second indication information to the data channel signaling function DCSF when the first message carries first indication information or the first message only carries the SDP of the bootstrap DC, wherein the first indication information is used to indicate that only the bootstrap DC is established.

[0659] Optionally, the second indication information is used to indicate at least one of the following:

[0660] Only the bootstrap DC is established;

[0661] Only establish a bootstrap DC for the first terminal;

[0662] Establish a unilateral bootstrap DC.

[0663] Optionally, the message processing apparatus 1000 further includes:

[0664] The third sending module is configured to send SDP answer information of the bootstrap DC to the first terminal when the first message is used to request establishment of a bootstrap DC.

[0665] Optionally, the message processing apparatus 1000 further includes:

[0666] The fourth sending module is configured to send third SDP answer information to the first terminal when the IMS AS receives the second SDP answer information of the second terminal, wherein the third SDP answer information is SDP answer information of the bootstrap DC and the application DC.

[0667] The resource allocation method provided in the embodiment of the present application can be executed by a resource allocation device. In the embodiment of the present application, the resource allocation device provided in the embodiment of the present application is described by taking the resource allocation device executing the resource allocation method as an example.

[0668] As shown in FIG11 , the resource allocation apparatus provided in the embodiment of the present application may be an apparatus corresponding to DCSF. As shown in FIG11 , the resource allocation apparatus 1100 includes the following modules:

[0669] The second receiving module 1101 is configured to receive a fourth message from the IP Multimedia Subsystem Application Server IMS AS;

[0670] The first resource allocation module 1102 is configured to allocate or reserve resources corresponding to the bootstrap data channel DC for the first terminal when the fourth message is used to notify that only the first terminal is to establish the bootstrap data channel DC; or

[0671] The second resource allocation module is configured to allocate or reserve resources corresponding to the bootstrap DC for the second terminal by the DCSF when the fourth message is used to notify that a bootstrap DC is established only for the second terminal.

[0672] Optionally, when the fourth message carries second indication information, the fourth message is used to notify that a bootstrap DC is only established for the first terminal, wherein the second indication information is used to indicate that a bootstrap DC is only established for the first terminal; or,

[0673] When the fourth message is triggered based on the first terminal initiating a first invitation Invite message to a preset destination address, the fourth message is used to notify that a bootstrap DC is established only for the first terminal, wherein the first Invite message includes Session Description Protocol SDP offer information for establishing a bootstrap DC.

[0674] Optionally, the second indication information is used to indicate at least one of the following:

[0675] Only the bootstrap DC is established;

[0676] Only establish a bootstrap DC for the first terminal;

[0677] Establish a unilateral bootstrap DC.

[0678] Optionally, when the fourth message carries the third indication information, the fourth message is used to notify that only the bootstrap DC of the second terminal is established, and the third indication information is used to instruct that only the bootstrap DC of the second terminal is established.

[0679] Optionally, the resource allocation apparatus 1100 further includes:

[0680] The fifth sending module is configured to send information for downloading the DC application to the first terminal when the first terminal downloads the DC application based on the bootstrap DC.

[0681] Optionally, the information for downloading the DC application includes at least one of the following:

[0682] the address of the DCSF;

[0683] The DCSF is an identifier allocated to the first terminal.

[0684] The DC establishment device, message processing device, and resource allocation device in the embodiments of the present application can be electronic devices, such as electronic devices with an operating system, or components within electronic devices, such as integrated circuits or chips. The electronic devices can be terminals or network-side devices. For example, terminals can include, but are not limited to, the types of terminals 11 listed above, and network-side devices can include, but are not limited to, the types of network-side devices 12 listed above. These are not specifically limited in the embodiments of the present application.

[0685] The DC establishment device, message processing device, and resource allocation device provided in the embodiments of the present application can implement the various processes implemented in the aforementioned DC establishment method, message processing method, and resource allocation method embodiments of the present application, and achieve the same technical effects. To avoid repetition, they will not be repeated here.

[0686] As shown in Figure 12, an embodiment of the present application further provides a communication device 1200, including a processor 1201 and a memory 1202. The memory 1202 stores programs or instructions that can be run on the processor 1201. For example, when the communication device 1200 is a terminal, the program or instruction is executed by the processor 1201 to implement the various steps of the aforementioned DC establishment method, message processing method, and resource allocation method embodiments of the present application, and can achieve the same technical effects. When the communication device 1200 is a network-side device, the program or instruction is executed by the processor 1201 to implement the various steps of the aforementioned DC establishment method, message processing method, and resource allocation method embodiments of the present application, and can achieve the same technical effects. To avoid repetition, they will not be repeated here.

[0687] An embodiment of the present application also provides a terminal, including a processor and a communication interface, wherein the communication interface is coupled to the processor, and the processor is configured to execute a program or instruction to implement the steps in the aforementioned DC establishment method or the second terminal-side message processing method embodiment of the present application. This terminal embodiment corresponds to the aforementioned terminal-side method embodiment, and each implementation process and implementation method of the aforementioned method embodiment can be applied to this terminal embodiment and can achieve the same technical effect. Specifically, Figure 13 is a schematic diagram of the hardware structure of a terminal implementing an embodiment of the present application.

[0688] The terminal 1300 includes but is not limited to: a radio frequency unit 1301, a network module 1302, an audio output unit 1303, an input unit 1304, a sensor 1305, a display unit 1306, a user input unit 1307, an interface unit 1308, a memory 1309 and at least some of the components of the processor 1310.

[0689] Those skilled in the art will appreciate that the terminal 1300 may also include a power supply (such as a battery) to power various components. The power supply may be logically connected to the processor 1310 via a power management system, thereby enabling the power management system to manage charging, discharging, and power consumption. The terminal structure shown in FIG13 does not limit the terminal. The terminal may include more or fewer components than shown, or may combine certain components, or have different component arrangements, which will not be described in detail here.

[0690] It should be understood that in an embodiment of the present application, the input unit 1304 may include a graphics processing unit (GPU) 13041 and a microphone 13042, and the graphics processor 13041 processes the image data of a static picture or video obtained by an image capture device (such as a camera) in a video capture mode or an image capture mode. The display unit 1306 may include a display panel 13061, and the display panel 13061 may be configured in the form of a liquid crystal display, an organic light emitting diode, etc. The user input unit 1307 includes a touch panel 13071 and at least one of the other input devices 13072. The touch panel 13071 is also called a touch screen. The touch panel 13071 may include two parts: a touch detection device and a touch controller. Other input devices 13072 may include, but are not limited to, a physical keyboard, function keys (such as volume control keys, switch keys, etc.), a trackball, a mouse, and a joystick, which will not be repeated here.

[0691] In the embodiment of the present application, after receiving downlink data from a network-side device, the RF unit 1301 may transmit the data to the processor 1310 for processing. Furthermore, the RF unit 1301 may send uplink data to the network-side device. Typically, the RF unit 1301 includes, but is not limited to, an antenna, an amplifier, a transceiver, a coupler, a low-noise amplifier, a duplexer, and the like.

[0692] The memory 1309 can be used to store software programs or instructions and various data. The memory 1309 may mainly include a first storage area for storing programs or instructions and a second storage area for storing data, wherein the first storage area may store an operating system, applications or instructions required for at least one function (such as a sound playback function, an image playback function, etc.). In addition, the memory 1309 may include a volatile memory or a non-volatile memory. Among them, the non-volatile memory may be a read-only memory (ROM), a programmable read-only memory (PROM), an erasable programmable read-only memory (EPROM), an electrically erasable programmable read-only memory (EEPROM), or a flash memory. Volatile memory can be random access memory (RAM), static random access memory (SRAM), dynamic random access memory (DRAM), synchronous dynamic random access memory (SDRAM), double data rate synchronous dynamic random access memory (DDRSDRAM), enhanced synchronous dynamic random access memory (ESDRAM), synchronous link dynamic random access memory (SLDRAM), and direct RAM bus random access memory (DRRAM). The memory 1309 in the embodiment of the present application includes but is not limited to these and any other suitable types of memory.

[0693] Processor 1310 may include one or more processing units. Optionally, processor 1310 integrates an application processor and a modem processor. The application processor primarily handles operations related to the operating system, user interface, and application programs, while the modem processor primarily processes wireless communication signals, such as a baseband processor. It is understood that the modem processor may not be integrated into processor 1310.

[0694] In some implementations, terminal 1300 is a first terminal.

[0695] In this embodiment, the radio frequency unit 1301 is configured to send a first message requesting establishment of a target DC without establishing a voice, video, or message media connection. The target DC includes at least one of a bootstrap DC and an application DC.

[0696] The radio frequency unit 1301 is further configured to receive a first response message and establish the target DC according to the first response message.

[0697] Optionally, the target DC includes a bootstrap DC, and the sending of the first message performed by the radio frequency unit 1301 includes:

[0698] A first Invite message is sent to a preset destination address, where the first Invite message includes Session Description Protocol (SDP) offer information for establishing the bootstrap DC.

[0699] Optionally, the first Invite message further includes first indication information, where the first indication information is used to indicate that only a bootstrap DC is to be established.

[0700] Optionally, the sending of the first message performed by the radio frequency unit 1301 includes:

[0701] When the first terminal meets a first condition, sending a first message;

[0702] The first condition includes at least one of the following:

[0703] Turning on the first terminal;

[0704] The first terminal releases or turns off the flight mode;

[0705] The first terminal completes IMS registration or IMS re-registration;

[0706] The dialing application APP of the first terminal is started;

[0707] A preset APP of the first terminal is started, and the preset APP is used to establish the target DC.

[0708] Optionally, the processor 1310 is configured to control the radio frequency unit 1301 to download an application list based on the bootstrap DC.

[0709] Optionally, the processor 1310 is further configured to control the radio frequency unit 1301 to download the first DC application in the application list based on the bootstrap DC.

[0710] Optionally, the processor 1310 is further configured to control the radio frequency unit 1301 to release the bootstrap DC.

[0711] Optionally, the controlling the RF unit 1301 to release the bootstrap DC executed by the processor 1310 includes:

[0712] If it is determined that the first terminal meets a second condition, the radio frequency unit 1301 is controlled to release the bootstrap DC, where the second condition includes at least one of the following:

[0713] When the first timer times out, the first terminal does not use the bootstrap DC to send a message or data;

[0714] When the first timer times out, the first terminal does not initiate a request message for establishing an application DC;

[0715] The first timer is started when the first terminal successfully establishes the bootstrap DC, or is started after the first terminal downloads the application list, or is started after the first DC application is downloaded.

[0716] Optionally, the target DC includes a bootstrap DC and an application DC, and the sending of the first message performed by the radio frequency unit 1301 includes:

[0717] Sending a second Invite message to the second terminal, wherein the second Invite message includes the first SDP offer information, where the first SDP offer information is used to establish a bootstrap DC;

[0718] Upon receiving the first SDP answer information, a second message is sent to the second terminal, where the second message includes second SDP offer information, wherein the first SDP answer information is the SDP answer information corresponding to the first SDP offer information, and the second SDP offer information is used to establish an application DC.

[0719] Optionally, the sending of the second message to the second terminal by the radio frequency unit 1301 upon receiving the first SDP response answer information includes:

[0720] Upon receiving the 183 response message containing the first SDP answer information, the second terminal sends an Update message; or,

[0721] Upon receiving the 200OK message including the first SDP answer information, the second terminal sends a re-Invite message.

[0722] Optionally, the target DC includes a bootstrap DC and an application DC, and the sending of the first message performed by the radio frequency unit 1301 includes:

[0723] A third Invite message is sent to the second terminal, wherein the third Invite message includes third SDP offer information, and the third SDP offer information is used to establish a bootstrap DC and an application DC.

[0724] Optionally, the processor 1310 is further used to initiate a process of downloading a DC application when a second response message containing third SDP answer information is received through the radio frequency unit 1301, wherein the third SDP answer information is SDP answer information corresponding to the third SDP offer information.

[0725] Optionally, the second response message includes at least one of the following:

[0726] 183 news;

[0727] 180 news;

[0728] 200 OK message.

[0729] Optionally, the target DC includes an application DC, and the sending of the first message performed by the radio frequency unit 1301 includes:

[0730] A fourth Invite message is sent to the second terminal, wherein the fourth Invite message includes fourth SDP offer information and information for downloading a DC application, the fourth SDP offer information is used to establish an application DC, and the first terminal has downloaded the DC application using bootstrap DC.

[0731] Optionally, the information for downloading the DC application includes at least one of the following:

[0732] SDP information of the bootstrap DC;

[0733] a preset destination address used by the first terminal when downloading the DC application;

[0734] The address of the data channel signaling function DCSF corresponding to the DC application;

[0735] The DCSF corresponding to the DC application is an identifier allocated to the first terminal;

[0736] The flow identifier used by the first terminal when establishing the bootstrap DC.

[0737] Optionally, the radio frequency unit 1301 is further configured to receive first information from a first DCSF, where the first DCSF is used to establish the bootstrap DC for the first terminal, and the first information includes at least one of the following:

[0738] the address of the first DCSF;

[0739] The first DCSF is an identifier allocated to the first terminal.

[0740] Optionally, the target DC includes an application DC, and the sending of the first message performed by the radio frequency unit 1301 includes:

[0741] A re-Invite message is sent to the second terminal, wherein the re-Invite message includes fifth SDP offer information, and the fifth SDP offer information is used to establish an application DC.

[0742] In other implementations, terminal 1300 is a second terminal.

[0743] In this embodiment, the processor 1310 is configured to, when receiving a third message through the radio frequency unit 1301, control the radio frequency unit 1301 to send a 180 message corresponding to the third message if a third condition is met, wherein the third message is used to request establishment of a target data channel DC, where the target DC includes at least one of a bootstrap DC and an application DC;

[0744] The third condition includes at least one of the following:

[0745] The third message is used to request the establishment of an application DC;

[0746] The second terminal completes downloading of the DC application corresponding to the application DC;

[0747] The second terminal completes the establishment of the bearer corresponding to the application DC.

[0748] Optionally, the third message includes information for downloading a DC application. The processor 1310 is further configured to:

[0749] Establish a bootstrap DC based on the information used to download the DC application;

[0750] Based on the established bootstrap DC, the radio frequency unit 1301 is controlled to download the DC application.

[0751] Optionally, the information for downloading the DC application includes at least one of the following:

[0752] SDP information of the bootstrap DC;

[0753] a preset destination address used by the first terminal when downloading the DC application;

[0754] The address of the data channel signaling function DCSF corresponding to the DC application;

[0755] The DCSF corresponding to the DC application is an identifier allocated to the first terminal;

[0756] The flow identifier used by the first terminal when establishing the bootstrap DC.

[0757] Optionally, the step of establishing a bootstrap DC according to the information for downloading the DC application, performed by the processor 1310, includes:

[0758] When the SDP information of the bootstrap DC is received through the radio frequency unit 1301, the radio frequency unit 1301 is controlled to send a temporary response message and establish a bootstrap DC according to the SDP information of the bootstrap DC; or

[0759] When the RF unit 1301 receives the second information, the RF unit 1301 is controlled to initiate a request to establish a bootstrap DC according to the second information, where the second information includes at least one of the following:

[0760] a preset destination address used by the first terminal when downloading the DC application;

[0761] The address of the data channel signaling function DCSF corresponding to the DC application;

[0762] The DCSF corresponding to the DC application is an identifier allocated to the first terminal;

[0763] The flow identifier used by the first terminal when establishing the bootstrap DC.

[0764] Optionally, the controlling the RF unit 1301 to download the DC application based on the established bootstrap DC performed by the processor 1310 includes:

[0765] Controlling the radio frequency unit 1301 to send third information to the DCSF based on the established bootstrap DC, where the third information includes at least one of an identifier of the first terminal and a stream identifier streamID sent by the first terminal;

[0766] The DC application sent by the DCSF is received through the radio frequency unit 1301.

[0767] Optionally, the third message includes at least one of the following:

[0768] Invite message, re-Invite message, and Update message.

[0769] Optionally, the processor 1310 is further configured to control at least one of the display unit 1306 and the audio output unit 1303 to output incoming call prompt information.

[0770] Optionally, the radio frequency unit 1301 is further configured to send SDP answer information, where the SDP answer information is carried in the 180 message or the 183 message.

[0771] It can be understood that the implementation process of each implementation method mentioned in this embodiment can refer to the relevant description of the DC establishment method and the message processing method embodiment on the second terminal side, and can achieve the same or corresponding technical effects as the DC establishment method and the message processing method embodiment on the second terminal side. To avoid repetition, it will not be repeated here.

[0772] The present application also provides a network-side device, including a processor and a communication interface, wherein the communication interface is coupled to the processor, and the processor is configured to execute a program or instruction to implement the steps of the message processing method and resource allocation method embodiments on the IMS AS side. This network-side device embodiment corresponds to the aforementioned network-side device method embodiment. Each implementation process and implementation method of the aforementioned method embodiment is applicable to this network-side device embodiment and can achieve the same technical effects. Specifically, the present application provides a network-side device.

[0773] As shown in Figure 14, the network side device 1400 includes: a processor 1401, a network interface 1402, and a memory 1403. The network interface 1402 is, for example, a Common Public Radio Interface (CPRI).

[0774] Specifically, the network side device 1400 of the embodiment of the present application also includes: instructions or programs stored in the memory 1403 and can be run on the processor 1401. The processor 1401 calls the instructions or programs in the memory 1403 to execute the method executed by each module as shown in Figure 10 or Figure 11, and achieves the same technical effect. To avoid repetition, it will not be repeated here.

[0775] An embodiment of the present application also provides a readable storage medium, on which a program or instruction is stored. When the program or instruction is executed by a processor, the various processes of the aforementioned DC establishment method, message processing method and resource allocation method embodiments of the present application are implemented, and the same technical effects can be achieved. To avoid repetition, they will not be repeated here.

[0776] The processor is the processor in the terminal described in the above embodiment. The readable storage medium includes a computer-readable storage medium, such as a computer read-only memory (ROM), a random access memory (RAM), a magnetic disk, or an optical disk. In some examples, the readable storage medium may be a non-transitory readable storage medium.

[0777] An embodiment of the present application further provides a chip, which includes a processor and a communication interface, wherein the communication interface is coupled to the processor, and the processor is used to run programs or instructions to implement the various processes of the aforementioned DC establishment method, message processing method and resource allocation method embodiments of the present application, and can achieve the same technical effects. To avoid repetition, they will not be repeated here.

[0778] It should be understood that the chip mentioned in the embodiments of the present application can also be called a system-level chip, a system chip, a chip system or a system-on-chip chip, etc.

[0779] An embodiment of the present application further provides a computer program / program product, which is stored in a storage medium. The computer program / program product is executed by at least one processor to implement the various processes of the aforementioned DC establishment method, message processing method and resource allocation method embodiments of the present application, and can achieve the same technical effects. To avoid repetition, they will not be repeated here.

[0780] An embodiment of the present application also provides a wireless communication system, including: a terminal and a network side device, wherein the terminal can be used to execute the steps of the DC establishment method or the message processing method on the second terminal side mentioned above in the present application, and the network side device can be used to execute the steps of the message processing method or resource allocation method on the IMS AS side mentioned above in the present application.

[0781] It should be noted that, in this article, the terms "comprise", "include" or any other variants thereof are intended to cover non-exclusive inclusion, so that a process, method, article or device comprising a series of elements includes not only those elements, but also other elements not explicitly listed, or also includes elements inherent to such process, method, article or device. In the absence of further restrictions, an element defined by the sentence "comprises a ..." does not exclude the presence of other identical elements in the process, method, article or device comprising the element. In addition, it should be pointed out that the scope of the methods and devices in the embodiments of the present application is not limited to performing functions in the order shown or discussed, and may also include performing functions in a substantially simultaneous manner or in the opposite order according to the functions involved. For example, the described method may be performed in an order different from that described, and various steps may also be added, omitted or combined. In addition, the features described with reference to certain examples may be combined in other examples.

[0782] Through the description of the above embodiments, those skilled in the art can clearly understand that the above-mentioned embodiment methods can be implemented by means of a computer software product plus a necessary general-purpose hardware platform, or of course, by hardware. The computer software product is stored in a storage medium (such as ROM, RAM, magnetic disk, optical disk, etc.) and includes a number of instructions for enabling a terminal or network-side device to execute the methods described in each embodiment of the present application.

[0783] The embodiments of the present application are described above in conjunction with the accompanying drawings, but the present application is not limited to the above-mentioned specific implementation methods. The above-mentioned specific implementation methods are merely illustrative and not restrictive. Under the guidance of this application, ordinary technicians in this field can also make many forms of implementation methods without departing from the purpose of this application and the scope of protection of the claims. These implementation methods are all within the protection of this application.

Claims

1. A method for establishing a data channel DC, wherein: include: In the case where a voice, video or message media connection is not established, the first terminal sends a first message, where the first message is used to request to establish a target DC, where the target DC includes at least one of a bootstrap DC and an application DC; The first terminal receives the first response message, and establishes the target DC according to the first response message.

2. The method according to claim 1, wherein: The target DC includes a bootstrap DC, and the first terminal sends a first message including: The first terminal sends a first invitation Invite message to a preset destination address, where the first Invite message includes Session Description Protocol SDP offer information for establishing the bootstrap DC.

3. The method according to claim 2, wherein: The first Invite message also includes first indication information, where the first indication information is used to indicate that only a bootstrap DC is established.

4. The method according to any one of claims 1 to 3, wherein: The first terminal sends a first message, including: The first terminal sends a first message when a first condition is met; The first condition includes at least one of the following: The first terminal is turned on; The first terminal releases or turns off the flight mode; The first terminal completes IP Multimedia Subsystem IMS registration or IMS re-registration; The dialing application APP of the first terminal is started; A preset APP of the first terminal is started, and the preset APP is used to establish the target DC.

5. The method according to any one of claims 2 to 4, wherein: The method further comprises: The first terminal downloads an application list based on the bootstrap DC.

6. The method according to claim 5, wherein: The method further comprises: The first terminal downloads the first DC application in the application list based on the bootstrap DC.

7. The method according to any one of claims 2 to 6, wherein: The method further comprises: The first terminal releases the bootstrap DC.

8. The method according to claim 7, wherein: The first terminal releases the bootstrap DC, including: The first terminal releases the bootstrap DC when a second condition is met, where the second condition includes at least one of the following: When the first timer times out, the first terminal does not use the bootstrap DC to send a message or data; When the first timer times out, the first terminal does not initiate a request message for establishing an application DC; The first timer is started when the first terminal successfully establishes the bootstrap DC, or after the first terminal downloads the application list, or after the first DC application is downloaded.

9. The method according to any one of claims 1 to 8, wherein: The target DC includes a bootstrap DC and an application DC, and the first terminal sends a first message including: The first terminal sends a second Invite message to the second terminal, wherein the second Invite message includes first SDP offer information, and the first SDP offer information is used to establish a bootstrap DC; When the first terminal receives the first SDP answer information, the second terminal sends a second message to the second terminal, where the second message includes second SDP offer information, wherein the first SDP answer information is the SDP answer information corresponding to the first SDP offer information, and the second SDP offer information is used to establish an application DC.

10. The method according to claim 9, wherein: When the first terminal receives the first SDP response answer information, sending the second message to the second terminal includes: When the first terminal receives the 183 response message including the first SDP answer information, the second terminal sends an Update message; or, When the first terminal receives the 200OK message including the first SDP answer information, the second terminal sends a re-Invite message.

11. The method according to any one of claims 1 to 8, wherein: The target DC includes a bootstrap DC and an application DC, and the first terminal sending the first message includes: The first terminal sends a third Invite message to the second terminal, wherein the third Invite message includes third SDP offer information, and the third SDP offer information is used to establish a bootstrap DC and an application DC.

12. The method according to claim 11, wherein: The method further comprises: When the first terminal receives the second response message including the third SDP answer information, the first terminal initiates the process of downloading the DC application, wherein the third SDP answer information is the SDP answer information corresponding to the third SDP offer information.

13. The method according to claim 12, wherein: The second response message includes at least one of the following: 183 messages; 180 messages; 200 OK message.

14. The method according to any one of claims 1 to 8, wherein: The target DC includes an application DC, and the first terminal sends a first message including: The first terminal sends a fourth Invite message to the second terminal, wherein the fourth Invite message includes fourth SDP offer information and information for downloading a DC application, the fourth SDP offer information is used to establish an application DC, and the first terminal has downloaded the DC application using a bootstrap DC.

15. The method according to claim 14, wherein: The information for downloading the DC application includes at least one of the following: SDP information of the bootstrap DC; A preset destination address used by the first terminal when downloading the DC application; The address of the data channel signaling function DCSF corresponding to the DC application; The DCSF corresponding to the DC application is an identifier allocated to the first terminal; The flow identifier used by the first terminal when establishing the bootstrap DC.

16. The method according to claim 15, wherein: The method further comprises: The first terminal receives first information from a first DCSF, wherein the first DCSF is used to establish the bootstrap DC for the first terminal, and the first information includes at least one of the following: the address of the first DCSF; The first DCSF is an identifier allocated to the first terminal.

17. The method according to any one of claims 1 to 8, wherein: The target DC includes an application DC, and the first terminal sends a first message including: The first terminal sends a re-Invite message to the second terminal, wherein the re-Invite message includes fifth SDP offer information, and the fifth SDP offer information is used to establish an application DC.

18. A message processing method, wherein: include: When the second terminal receives the third message, if the third condition is met, it sends a 180 message corresponding to the third message, wherein the third message is used to request to establish a target data channel DC, and the target DC includes at least one of a bootstrap DC and an application DC; The third condition includes at least one of the following: The third message is used to request to establish an application DC; The second terminal completes downloading of the DC application corresponding to the application DC; The second terminal completes the establishment of the bearer corresponding to the application DC.

19. The method according to claim 18, wherein: The third message includes information for downloading the DC application, and the method further includes: The second terminal establishes a bootstrap DC according to the information for downloading the DC application; The second terminal downloads the DC application based on the established bootstrap DC.

20. The method according to claim 19, wherein: The information for downloading the DC application includes at least one of the following: Session Description Protocol SDP information of the bootstrap DC; A preset destination address used by the first terminal when downloading the DC application; The address of the data channel signaling function DCSF corresponding to the DC application; The DCSF corresponding to the DC application is an identifier allocated to the first terminal; The flow identifier used by the first terminal when establishing the bootstrap DC.

21. The method according to claim 20, wherein: The second terminal establishes a bootstrap DC according to the information for downloading the DC application, including: When the second terminal receives the SDP information of the bootstrap DC, the second terminal sends a temporary response message according to the SDP information of the bootstrap DC and establishes a bootstrap DC; or, When the second terminal receives the second information, it initiates a request to establish a bootstrap DC according to the second information, where the second information includes at least one of the following: A preset destination address used by the first terminal when downloading the DC application; The address of the data channel signaling function DCSF corresponding to the DC application; The DCSF corresponding to the DC application is an identifier allocated to the first terminal; The flow identifier used by the first terminal when establishing the bootstrap DC.

22. The method according to claim 19, wherein: The second terminal downloads the DC application based on the established bootstrap DC, including: The second terminal sends third information to the DCSF based on the established bootstrap DC, where the third information includes at least one of an identifier of the first terminal and a stream identifier streamID sent by the first terminal; The second terminal receives the DC application sent by the DCSF.

23. The method according to any one of claims 18 to 22, wherein: The third message includes at least one of the following: Invite message, re-Invite message, and Update message.

24. The method according to any one of claims 18 to 23, wherein: The method further comprises: The second terminal outputs incoming call prompt information.

25. The method according to any one of claims 18 to 24, wherein: The method further comprises: The second terminal sends an SDP answer message, where the SDP answer message is carried in the 180 message or the 183 message.

26. A message processing method, wherein: include: The IP multimedia subsystem application server IMS AS receives a first message from the first terminal; The IMS AS performs a first operation according to the first message, where the first operation includes at least one of the following: In the case where the first message is used to request the establishment of a bootstrap data channel DC, sending second indication information to a data channel signaling function DCSF, wherein the second indication information is used to indicate that only a bootstrap DC is established; In a case where the first message is used to request the establishment of a bootstrap DC and an application DC, sending a first session description protocol SDP offer information to the second terminal, where the first SDP offer information is used to establish a bootstrap DC, and in a case where the IMS AS receives a first SDP answer information from the second terminal, sending a second SDP offer information to the second terminal, where the first SDP answer information is SDP answer information corresponding to the first SDP offer information, and the second SDP offer information is used to establish an application DC; In the case where the first message is used to request the establishment of an application DC, a fourth message is sent to the DCSF, where the fourth message is used to notify the DCSF to only establish a bootstrap DC for the second terminal.

27. The method according to claim 26, wherein: When the first message is used to establish an application DC, sending a fourth message to the DCSF includes: In the case that the first message is a re-Invite message from the first terminal and the destination address is the second terminal, a fourth message is sent to DCSF, wherein the re-Invite message includes second SDP offer information and information for downloading a DC application, and the second SDP offer information is used to establish an application DC.

28. The method according to claim 27, wherein: The fourth message includes third indication information, where the third indication information is used to indicate that only the bootstrap DC of the second terminal is to be established.

29. The method according to claim 26, wherein: The sending second indication information to a data channel signaling function DCSF when the first message is used to request to establish a bootstrap DC includes: In the case where the first message carries the first indication information or the first message only carries the SDP of the bootstrap DC , sending second indication information to the data channel signaling function DCSF, wherein the first indication information is used to indicate that only a bootstrap DC is established.

30. The method according to claim 26 or 29, wherein: The second indication information is used to indicate at least one of the following: Only the bootstrap DC is established; Only establish a bootstrap DC for the first terminal; Establish a unilateral bootstrap DC.

31. The method of claim 26, 29 or 30, wherein: The method further comprises: In the case where the first message is used to request establishment of a bootstrap DC, the IMS AS sends SDP answer information of the bootstrap DC to the first terminal.

32. The method according to any one of claims 26 to 31, wherein: The method further comprises: When receiving the second SDP answer information of the second terminal, the IMS AS sends third SDP answer information to the first terminal, wherein the third SDP answer information is SDP answer information of bootstrap DC and application DC.

33. The method according to any one of claims 26 to 31, wherein: The second indication information includes at least one of the following: Only carries the SDP offer information corresponding to the bootstrap DC; The SDP offer information corresponding to the application DC is not carried; Preset destination address.

34. The method of claim 33, wherein: The preset destination address includes at least one of the following: a customer service telephone number of a communication operator; The first terminal's own telephone number; DCSF telephone number; The telephone number of the IMS AS; The public service identifier (PSI) used to indicate that only the bootstrap DC is established.

35. A resource allocation method, wherein: The method comprises: The data channel signaling function DCSF receives a fourth message from the IP multimedia subsystem application server IMS AS; In a case where the fourth message is used to notify that a bootstrap data channel DC is established only for the first terminal, the DCSF allocates or reserves resources corresponding to the bootstrap DC for the first terminal; or, In a case where the fourth message is used to notify that a bootstrap DC is established only for the second terminal, the DCSF allocates or reserves resources corresponding to the bootstrap DC for the second terminal.

36. The method of claim 35, wherein: In the case where the fourth message carries the second indication information, the fourth message is used to notify that only the bootstrap DC is established for the first terminal, wherein the second indication information is used to indicate that only the bootstrap DC for the first terminal is established; or, In the case where the fourth message is triggered based on the first terminal sending a first invitation Invite message to a preset destination address, the fourth message is used to notify that a bootstrap DC is established only for the first terminal, wherein the first Invite The message contains the Session Description Protocol (SDP) offer information used to establish the bootstrap DC.

37. The method of claim 36, wherein: The second indication information is used to indicate at least one of the following: Only the bootstrap DC is established; Only establish a bootstrap DC for the first terminal; Establish a unilateral bootstrap DC.

38. The method of claim 35, wherein: In the case where the fourth message carries the third indication information, the fourth message is used to notify that only the bootstrap DC of the second terminal is established, and the third indication information is used to indicate that only the bootstrap DC of the second terminal is established.

39. The method according to any one of claims 35 to 38, wherein: The method further comprises: In a case where the first terminal downloads the DC application based on the bootstrap DC, the DCSF sends information for downloading the DC application to the first terminal.

40. The method of claim 39, wherein: The information used to download the DC application includes at least one of the following: the address of the DCSF; The DCSF is an identifier allocated to the first terminal.

41. The method according to any one of claims 36 to 40, wherein: The second indication information includes at least one of the following: Only carries the SDP offer information corresponding to the bootstrap DC; The fourth message includes a preset destination address.

42. The method according to claim 41, wherein: The preset destination address includes at least one of the following: a customer service telephone number of a communication operator; The first terminal's own telephone number; DCSF telephone number; The telephone number of the IMS AS; The public service identifier (PSI) used to indicate that only the bootstrap DC is established.

43. A data channel DC establishment device, wherein: For a first terminal, the device comprises: A first sending module, configured to send a first message without establishing a voice, video or message media connection, wherein the first message is used to request to establish a target DC, wherein the target DC includes at least one of a bootstrap DC and an application DC; The first establishing module is used to receive a first response message and establish the target DC according to the first response message.

44. A message processing device, wherein: For a second terminal, the device comprises: a first transmission module, configured to, upon receiving a third message, send a 180 message corresponding to the third message if a third condition is met, wherein the third message is used to request to establish a target data channel DC, and the target DC includes at least one of a bootstrap DC and an application DC; The third condition includes at least one of the following: The third message is used to request to establish an application DC; The second terminal completes downloading of the DC application corresponding to the application DC; The second terminal completes the establishment of the bearer corresponding to the application DC.

45. A message processing device, wherein: Used for an IP multimedia subsystem application server IMS AS, the device comprises: A first receiving module, configured to receive a first message from a first terminal; An execution module is configured to execute a first operation according to the first message, where the first operation includes at least one of the following: In the case where the first message is used to request the establishment of a bootstrap data channel DC, sending second indication information to a data channel signaling function DCSF, wherein the second indication information is used to indicate that only a bootstrap DC is established; In a case where the first message is used to request the establishment of a bootstrap DC and an application DC, sending a first session description protocol SDP offer information to the second terminal, where the first SDP offer information is used to establish a bootstrap DC, and in a case where the IMS AS receives a first SDP answer information from the second terminal, sending a second SDP offer information to the second terminal, where the first SDP answer information is SDP answer information corresponding to the first SDP offer information, and the second SDP offer information is used to establish an application DC; In the case where the first message is used to request the establishment of an application DC, a fourth message is sent to the DCSF, where the fourth message is used to notify the DCSF to only establish a bootstrap DC for the second terminal.

46. ​​A resource allocation device, wherein: For a data channel signaling function DCSF, the device comprises: A second receiving module, configured to receive a fourth message from an IP multimedia subsystem application server IMS AS; A first resource allocation module is configured to allocate or reserve resources corresponding to a bootstrap DC for the first terminal by the DCSF when the fourth message is used to notify that only a bootstrap data channel DC is established for the first terminal; or The second resource allocation module is configured to allocate or reserve resources corresponding to the bootstrap DC for the second terminal by the DCSF when the fourth message is used to notify that a bootstrap DC is established only for the second terminal.

47. A terminal, wherein: It includes a processor and a memory, the memory stores a program or instruction that can be run on the processor, and when the program or instruction is executed by the processor, it implements the steps of the data channel DC establishment method as described in any one of claims 1 to 17, or implements the steps of the message processing method as described in any one of claims 18 to 25.

48. A network side device, wherein: It includes a processor and a memory, the memory stores a program or instruction that can be run on the processor, and when the program or instruction is executed by the processor, it implements the steps of the message processing method as described in any one of claims 26 to 34, or implements the steps of the resource allocation method as described in any one of claims 35 to 42.

49. A readable storage medium, wherein: The readable storage medium stores programs or instructions, and when the programs or instructions are executed by the processor, they implement the steps of the data channel DC establishment method as described in any one of claims 1 to 17, or implement the steps of the message processing method as described in any one of claims 18 to 25, or implement the steps of the message processing method as described in any one of claims 26 to 34, or implement the steps of the resource allocation method as described in any one of claims 35 to 42.

Images