Data channel establishment method, apparatus, and communication device

Abstract

The present application relates to the technical field of communications, and discloses a data channel (DC) establishment method, an apparatus, and a communication device. The DC establishment method in embodiments of the present application comprises: a first network element receives a first message from a second network element, the first message being used for establishing a first DC for a first device; and when a first stream identifier corresponding to the first DC is the same as a second stream identifier corresponding to a second DC, the first network element sends a second message to the second network element.

Description

Data channel establishment method, device and communication equipment

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS

[0002] This application claims priority to a Chinese patent application filed with the Patent Office of China on April 2, 2024, with application number 202410395836.X and invention name “Data Channel Establishment Method, Device and Communication Equipment”. The entire contents of the Chinese patent application are incorporated herein by reference. Technical Field

[0003] The present application belongs to the field of communication technology, and specifically relates to a data channel establishment, device and communication equipment. Background Art

[0004] In related technologies, a Data Channel (DC) mechanism is introduced to enable additional services during a call, such as screen sharing, location sharing, and file transfer. In particular, a DC multiplexing mechanism can be used when the same terminal uses multiple DCs simultaneously to improve the effective utilization of media resources.

[0005] However, during the DC multiplexing process, the flow identifier used by the DC establishment initiator may be repeated with the flow identifier of the established DC, which may lead to problems such as DC multiplexing failure and affect the performance of the communication system. Summary of the Invention

[0006] In a first aspect, a method for establishing a data channel is provided, comprising: a first network element receives a first message from a second network element, the first message being used to establish a first data channel DC for a first device, the first network element and the second network element being network elements serving the first device; when a first flow identifier corresponding to the first DC is the same as a second flow identifier corresponding to the second DC, the first network element sends a second message to the second network element; wherein the second DC includes at least one of the established DCs corresponding to the first device; the second message includes at least one of the following: a third flow identifier, the third flow identifier being a flow identifier assigned by the first network element, the third flow identifier being different from the first flow identifier; a first indication information, the first indication information The information is used to indicate at least one of the following: flow identifier duplication, flow identifier modification, and flow identifier reallocation; a first label, the first label is allocated by the first network element and is used to distinguish different DCs with the same flow identifier; second indication information, the second indication information is used to indicate the allocation of a second label, the second label is used to distinguish different DCs with the same flow identifier; third indication information, the third indication information is used to indicate the rejection of the establishment of the first DC; fourth indication information, the fourth indication information is used to indicate the re-initiation of the DC establishment request; a flow identifier list, the flow identifier list includes the flow identifier of the established DC corresponding to the first device; the first flow identifier; fifth indication information, the fifth indication information is used to indicate the demultiplexing of the first DC.

[0007] According to a second aspect, a method for establishing a data channel is provided, including: a second network element sends a first message to a first network element, the first message being used to establish a first DC for the first device; the second network element receives a second message from the first network element; wherein the first network element and the second network element are network elements serving the first device, and the second message includes at least one of the following: a third flow identifier, the third flow identifier being a flow identifier assigned by the first network element, the third flow identifier being different from the first flow identifier corresponding to the first DC; first indication information, the first indication information being used to indicate at least one of flow identifier duplication, flow identifier modification, and flow identifier reallocation; a first label, the first label being assigned by the first network element and being used to distinguish different DCs with the same flow identifier; second indication information, the second indication information being used to indicate the allocation of a second label, the second label being used to distinguish different DCs with the same flow identifier; third indication information, the third indication information being used to indicate the rejection of the establishment of the first DC; fourth indication information, the fourth indication information being used to indicate the re-initiation of a DC establishment request; a flow identifier list, the flow identifier list including the flow identifiers of the established DC corresponding to the first device; the first flow identifier; and fifth indication information, the fifth indication information being used to indicate the demultiplexing of the first DC.

[0008] According to a third aspect, a method for establishing a data channel is provided, comprising: a second device sends a third message, the third message being used to request establishment of a first data channel DC for a first device; the second device receives a fourth message from a second network element; wherein the fourth message comprises at least one of the following: a third flow identifier or a fourth flow identifier, the third flow identifier being a flow identifier assigned by the first network element, the fourth flow identifier being a flow identifier assigned by the second network element, the third flow identifier and the fourth flow identifier being different from the first flow identifier corresponding to the first DC; sixth indication information, the sixth indication information being used to indicate at least one of a flow identifier duplication, a flow identifier being modified, a flow identifier being replaced, and an updated flow identifier; the first A label or a second label, the first label is allocated by the first network element, the second label is allocated by the second network element, the first label or the second label is used to distinguish different DCs with the same flow identifier; the flow identifier list; the seventh indication information, the seventh indication information is used to indicate the re-initiation of the DC establishment request; the eighth indication information, the eighth indication information is used to indicate the rejection of the establishment of the first DC; the ninth indication information, the ninth indication information is used to indicate the re-initiation of the DC establishment request based on the target m rows, the target m rows are different from the m rows corresponding to the second DC, the second DC includes at least one of the established DCs corresponding to the first device; the first flow identifier.

[0009] In a fourth aspect, a method for establishing a data channel is provided, including: a first device receives a fourth message from a second network element; wherein, the fourth message includes: a first label or a second label, the first label is assigned by the first network element, the second label is assigned by the second network element, the first label or the second label is used to distinguish different data channel DCs with the same flow identifier; a first flow identifier, the first flow identifier corresponds to the first DC.

[0010] In a fifth aspect, a data channel establishment device is provided, which is applied to a first network element, and the device includes: a receiving module, which is used to receive a first message from a second network element, the first message is used to establish a first data channel DC for a first device, and the first network element and the second network element are network elements serving the first device; a sending module, which is used to send a second message to the second network element when the first flow identifier corresponding to the first DC is the same as the second flow identifier corresponding to the second DC; wherein the second DC includes at least one of the established DCs corresponding to the first device; the second message includes at least one of the following: a third flow identifier, the third flow identifier is the flow identifier allocated by the first network element, and the third flow identifier is different from the first flow identifier; first indication information , the first indication information is used to indicate at least one of flow identifier duplication, flow identifier modification, and flow identifier reallocation; a first label, the first label is allocated by the first network element and is used to distinguish different DCs with the same flow identifier; second indication information, the second indication information is used to indicate the allocation of a second label, and the second label is used to distinguish different DCs with the same flow identifier; third indication information, the third indication information is used to indicate the rejection of the establishment of the first DC; fourth indication information, the fourth indication information is used to indicate the re-initiation of the DC establishment request; a flow identifier list, the flow identifier list includes the flow identifier of the established DC corresponding to the first device; the first flow identifier; fifth indication information, the fifth indication information is used to indicate the demultiplexing of the first DC.

[0011] In the sixth aspect, a data channel establishment device is provided, which is applied to the second network element, and the device includes: a sending module for sending a third message, and the third message is used to request to establish a first data channel DC for the first device; a receiving module for receiving a fourth message from the second network element; wherein the fourth message includes at least one of the following: a third flow identifier or a fourth flow identifier, the third flow identifier is the flow identifier assigned by the first network element, the fourth flow identifier is the flow identifier assigned by the second network element, and the third flow identifier and the fourth flow identifier are different from the first flow identifier corresponding to the first DC; sixth indication information, the sixth indication information is used to indicate that the flow identifier is repeated, the flow identifier is modified, the flow identifier is replaced, and the flow identifier is updated. at least one item; a first label or a second label, the first label is allocated by the first network element, the second label is allocated by the second network element, the first label or the second label is used to distinguish different DCs with the same flow identifier; the flow identifier list; seventh indication information, the seventh indication information is used to indicate the re-initiation of the DC establishment request; eighth indication information, the eighth indication information is used to indicate the rejection of the establishment of the first DC; ninth indication information, the ninth indication information is used to indicate the re-initiation of the DC establishment request based on the target m rows, the target m rows are different from the m rows corresponding to the second DC, the second DC includes at least one of the established DCs corresponding to the first device; the first flow identifier.

[0012] In the seventh aspect, a data channel establishment device is provided, which is applied to a second device, and the device includes: a sending module for sending a third message, and the third message is used to request to establish a first data channel DC for the first device; a receiving module for receiving a fourth message from the second network element; wherein the fourth message includes at least one of the following: a third flow identifier or a fourth flow identifier, the third flow identifier is a flow identifier assigned by the first network element, the fourth flow identifier is a flow identifier assigned by the second network element, and the third flow identifier and the fourth flow identifier are different from the first flow identifier corresponding to the first DC; sixth indication information, the sixth indication information is used to indicate that the flow identifier is repeated, the flow identifier is modified, the flow identifier is replaced, and the flow identifier is updated. at least one item; a first label or a second label, the first label is allocated by the first network element, the second label is allocated by the second network element, the first label or the second label is used to distinguish different DCs with the same flow identifier; the flow identifier list; seventh indication information, the seventh indication information is used to indicate the re-initiation of the DC establishment request; eighth indication information, the eighth indication information is used to indicate the rejection of the establishment of the first DC; ninth indication information, the ninth indication information is used to indicate the re-initiation of the DC establishment request based on the target m rows, the target m rows are different from the m rows corresponding to the second DC, the second DC includes at least one of the established DCs corresponding to the first device; the first flow identifier.

[0013] In the eighth aspect, a data channel establishment device is provided, which is applied to a first device, and the device includes: a receiving module, used to receive a fourth message from a second network element; wherein, the fourth message includes: a first label or a second label, the first label is assigned by the first network element, and the second label is assigned by the second network element, and the first label and the second label are used to distinguish different data channel DCs with the same flow identifier; a first flow identifier, and the first flow identifier corresponds to the first DC.

[0014] In the ninth aspect, a communication device is provided, which includes a processor and a memory, wherein 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 method described in the first aspect, or implements the steps of the method described in the second aspect, or implements the steps of the method described in the third aspect, or implements the steps of the method described in the fourth aspect.

[0015] In the tenth aspect, a terminal 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 a program or instruction 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.

[0016] In the eleventh 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.

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

[0018] In the thirteenth 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 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.

[0019] In the fourteenth 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.

[0020] In an embodiment of the present application, the first network element receives a first message from the second network element, and the first message is used to establish a first DC for the first device. When the first flow identifier corresponding to the first DC is the same as the second flow identifier corresponding to the second DC, the first network element sends a second message to the second network element to realize DC establishment and multiplexing in the case of repeated flow identifiers. BRIEF DESCRIPTION OF THE DRAWINGS

[0021] FIG1a is a schematic structural diagram of a wireless communication system provided by an exemplary embodiment of the present application.

[0022] FIG1 b is a schematic diagram of DC multiplexing provided by an exemplary embodiment of the present application.

[0023] FIG2 is a flowchart of a method for establishing a data channel according to an exemplary embodiment of the present application.

[0024] FIG3 is a second flowchart of a method for establishing a data channel provided by an exemplary embodiment of the present application.

[0025] FIG4 a is one of the interactive flow diagrams of a method for establishing a data channel provided by an exemplary embodiment of the present application.

[0026] FIG4 b is a second interactive flow diagram of a method for establishing a data channel provided by an exemplary embodiment of the present application.

[0027] FIG4c is a third interactive flow diagram of a method for establishing a data channel provided by an exemplary embodiment of the present application.

[0028] FIG4 d is a fourth interactive flow diagram of a method for establishing a data channel provided by an exemplary embodiment of the present application.

[0029] FIG5 is a third flowchart of a method for establishing a data channel provided by an exemplary embodiment of the present application.

[0030] FIG6 is a fourth flowchart of a method for establishing a data channel provided by an exemplary embodiment of the present application.

[0031] FIG7 is a fifth flowchart of a method for establishing a data channel provided by an exemplary embodiment of the present application.

[0032] FIG8 is a schematic diagram of a structure of a data channel establishment device according to an exemplary embodiment of the present application.

[0033] FIG9 is a second structural diagram of a data channel establishment device provided by an exemplary embodiment of the present application.

[0034] FIG10 is a third structural diagram of a data channel establishment device provided by an exemplary embodiment of the present application.

[0035] FIG11 is a fourth structural diagram of a data channel establishment device provided by an exemplary embodiment of the present application.

[0036] FIG12 is a schematic structural diagram of a communication device provided by an exemplary embodiment of the present application.

[0037] FIG13 is a schematic structural diagram of a terminal provided by an exemplary embodiment of the present application.

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

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

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

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

[0042] 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 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 6th generation (6G) systems. th Generation, 6G) communication system.

[0043] FIG1a shows 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 user equipment (VUE), a ship-borne 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 terminals, it can also be a chip in the terminal, such as a modem chip, a system-on-chip (SoC), etc. 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 (home evolved 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.

[0044] 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 user server (HSS), centralized network configuration (CNC), network storage function (NRF), network exposure function (NEF), local NEF (L-NEF), binding support function (BSF), application function ( Function, AF), data channel media function (Media Function, MF) / media resource function (Media Resource Function, MRF), data channel signaling function (Data Channel Signaling Function, DCSF), 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.

[0045] In addition, for ease of understanding, the relevant technical features involved in this application are explained below.

[0046] (1) DC mechanism

[0047] Related technologies have introduced a mechanism for establishing a DC (Data Channel) during a call. This DC allows for additional services during a call, such as screen sharing, location sharing, and file transfer, providing a better user experience. In this application, different services correspond to different DC applications. These DC applications can be dynamically downloaded to the terminal during a call, eliminating the need for pre-installation and facilitating user use. For ease of description, the DC application will be referred to as an APP.

[0048] In this application, DC can be divided into two types: bootstrap DC and application DC.

[0049] The Bootstrap DC is used to download APPs from a data channel server. In this application, the data channel server may be, but is not limited to, a DCSF.

[0050] In this application, the Bootstrap DC may be established by the UE. For example, when UE-1 and UE-2 communicate, UE-1 may request to establish a Bootstrap DC with its local DCSF (the DCSF serving UE-1), or request to establish a Bootstrap DC with the peer DCSF (the DCSF serving UE-2).

[0051] The Application DC is used to transmit data corresponding to the APP or data produced by the APP. In this application, the Application DC can be established by the UE or by the network-side server. For example, when UE-1 and UE-2 communicate, UE-1 can request to establish an application DC; UE-2 can also request to establish an application DC; or, the network-side server requests to establish an application DC with UE-1, etc. The network-side server can be, but is not limited to, a Data Channel Application Server (DC AS).

[0052] It is worth noting that the data channel mentioned in this application can be established along with the establishment of services such as voice calls, video calls, or text messages, or it can be established without the establishment of services such as voice calls, video calls, or text messages. The latter is called a standalone DC.

[0053] (2) DC multiplexing mechanism

[0054] When UE-1 uses multiple DCs simultaneously during an IP Multimedia Subsystem (IMS) session, if both the UE and the network side support the data channel multiplexing feature, the data channel streaming media description information corresponding to multiple applications can be carried in the same media (m) line during Session Description Protocol (SDP) negotiation, so that multiple application DCs can be transmitted in the same Stream Control Transmission Protocol (SCTP) connection, thereby saving the number of m lines used by the terminal and improving the effective utilization of media resources.

[0055] Taking Figure 1b as an example, assuming that the network where UE-1 is located is the originating network and the network where UE-2 is located is the terminating network, three application DCs corresponding to three different APPs can be transmitted within one SCTP connection between UE-1 and the MF / MRF. Among them, the DC corresponding to APP-1 is an application DC of the application-to-person (A2P) type between UE-1 and the DC application server (AS)-1; the DC corresponding to APP-2 is an application DC of the person-to-application (P2A) type between UE-1 and the DC AS-2; and the DC corresponding to APP-3 is an application DC of the person-to-person (P2P) type between UE-1 and UE-2. In addition, the MDC shown in Figure 1b is the Media Data Channel.

[0056] When initiating the establishment of an application DC, the UE can request multiplexing. For example, when UE-1 establishes the application DCs corresponding to APP-1 and APP-2, it can request multiplexing by including two application DCs in an m-line. If the network-side equipment (such as DCSF or IMS AS) allows it, the application DCs corresponding to APP-1 and APP-2 can be transmitted over a single SCTP connection. Correspondingly, when UE-1 initiates the establishment of the application DC corresponding to APP-3, UE-1 can request multiplexing by including three application DCs in an m-line.

[0057] In this application, when DC multiplexing is performed, in addition to multiplexing application DCs, Bootstrap DCs and Bootstrap DCs can also be multiplexed, and Bootstrap DCs and application DCs can also be multiplexed.

[0058] In addition, the aforementioned P2A type application DC may also be referred to as or replaced by P2A application DC.

[0059] A2P application DC may also be referred to as or replaced by A2P application DC.

[0060] P2P application DC can also be called or replaced by P2P application DC.

[0061] An A2P type application DC indicates that the application DC is established by a DC AS.

[0062] A P2A type application DC indicates that the application DC is established by the UE.

[0063] A P2P type application DC indicates that the application DC is established by the UE.

[0064] This application considers that the stream ID corresponding to each DC is assigned by the initiator of DC establishment, such as UE or DC AS. For example, in Figure 1b, APP-1 is an A2P type application DC, the initiator of this DC is DC AS-1, that is, stream ID-1 is assigned by DC AS-1; APP-3 is a P2P type application DC, the initiator of this DC is UE-1 or UE-2, that is, stream ID-3 is assigned by UE-1 or UE-2.

[0065] In this case, assuming that the stream IDs corresponding to application DCs start at 1000 and that application DC establishment requests are typically assigned sequentially starting from 1000, then if UE-1 allocates stream ID 1000 when initiating a P2P application DC establishment request with UE-2, and allocates stream ID 1001 when initiating a P2A application DC establishment request, UE-2, unaware that UE-1 has already established a P2A application DC using 1001, might also initiate a P2P application DC establishment request with UE-1 using 1001 and request DC reuse when initiating the request. This results in a duplicate stream ID. The DCSF serving UE-1 rejects the application establishment request due to the duplicate stream ID but does not notify UE-2 of the rejection reason. Consequently, UE-2, unable to determine the rejection reason, repeatedly attempts to establish the application DC, leading to DC reuse failure and resource waste.

[0066] In this regard, the present application provides a data channel establishment method that can solve the DC establishment problem in the case of repeated flow identifiers and ensure the performance of the communication system. The technical solution provided by the embodiments of the present application is described in detail below with reference to some embodiments and their application scenarios, in conjunction with the accompanying drawings.

[0067] Figure 2 is a flow chart of a data channel establishment method 200 provided in an exemplary embodiment of the present application. This method 200 may be, but is not limited to, executed by a first network element, specifically by at least one of hardware and software installed in the first network element. In this embodiment, the method 200 may include at least the following steps.

[0068] S210. A first network element receives a first message from a second network element.

[0069] The first network element and the second network element are network elements serving the first device. For example, in this embodiment, the first network element may be, but is not limited to, a DCSF, and the second network element may be, but is not limited to, an IMS AS.

[0070] The first device may be but is not limited to a terminal, a DC AS, etc.

[0071] The first message is used to establish a first DC for the first device, such as a Bootstrap DC, an application DC, etc. In this embodiment, the initiator of the first message or the initiator / sponsor of establishing the first DC may be a second device other than the first device, such as a terminal or a DC AS.

[0072] Optionally, the first message may be, but is not limited to, a Session Initiation Protocol (SIP) Invite message or a SIP re-Invite message.

[0073] S220: When the first flow identifier corresponding to the first DC is the same as the second flow identifier corresponding to the second DC, the first network element sends a second message to the second network element.

[0074] The second DC includes at least one of the established DCs corresponding to the first device.

[0075] In this embodiment, the second DC can be determined in various ways. For example, in some embodiments, if the first message is used to request multiplexing of the first DC, the first network element can determine the second DC based on, but not limited to, the DC multiplexing information corresponding to the first DC carried in the first message. The determination process can include: the first network element can determine the second DC based on information about the DC corresponding to APP in an m-line of the SDP carried in the first message. For example, assuming that an initiator (e.g., a second device) requests to establish a first DC corresponding to APP-2, the first message can include, in addition to information about the first DC corresponding to APP-2 (e.g., the application identifier and flow identifier of APP-2), DC multiplexing information corresponding to the first DC, such as information about a third DC that needs to be multiplexed with the first DC (e.g., the application identifier and flow identifier of the APP corresponding to the third DC). Upon receiving the first message, the first network element can determine the DC that is multiplexed with the third DC and has the same stream ID as the first DC as the second DC as the second DC. The third DC is the DC that the initiator (e.g., the second device) established with the first device before requesting to establish the first DC corresponding to APP-2.

[0076] It should be noted that, for the situation where the first message is also used to request multiplexing of the first DC, it can be understood or replaced as: the first network element sends a second message to the second network element when the first flow identifier corresponding to the first DC is the same as the second flow identifier corresponding to the second DC, and the first message is used to request multiplexing of the first DC.

[0077] In addition, the first message is used to request multiplexing of the first DC, which can be understood or replaced as follows: the first message is used to request multiplexing of the first DC and other DCs (e.g., a third DC). For example, the multiplexing request can be made by carrying information about the first DC and other DCs (e.g., a third DC) in an m line of the SDP; or, the multiplexing can be performed by transmitting data of the first DC and other DCs via an SCTP connection.

[0078] In other embodiments, if the first message does not request multiplexing of the first DC, then in order to save the number of m lines used by the terminal and improve the effective utilization of media resources, the first network element may also determine the second DC that can or can be multiplexed with the first DC from the established or multiplexed DC corresponding to the first device based on its own implementation.

[0079] However, no matter which of the aforementioned methods is used, considering that the DC establishment initiator / initiator (such as the second device) is not aware of the flow identifier of the established DC corresponding to the first device, the first DC requested to be established may have the same flow identifier as the second DC, which in turn causes problems such as failure to establish the first DC. In this case, for the first network element, after receiving the first message, if it is determined that the first flow identifier corresponding to the first DC requested to be established is the same as the second flow identifier corresponding to the established second DC, a second message can be sent to the second network element to solve the DC establishment and multiplexing problems in the case of repeated flow identifiers, thereby improving the effective utilization of media resources.

[0080] In this embodiment, there are multiple solutions to the DC establishment and multiplexing issues in the case of duplicate flow identifiers. For example, the flow identifier of the first DC can be modified, a tag can be added to the first DC to distinguish different DCs with the same flow identifier, the DC establishment request corresponding to the first DC can be retransmitted, the DC establishment request can be rejected, and the first DC can be demultiplexed. Based on this, in this embodiment, depending on the solution adopted, the second message can include but is not limited to at least one of the following 11)-19).

[0081] 11) A third flow identifier, which is a flow identifier assigned by the first network element and is different from the first flow identifier. That is, when the first flow identifier corresponding to the first DC is duplicated or identical to the second flow identifier corresponding to the second DC, the first network element may modify the flow identifier corresponding to the first DC or reallocate a flow identifier, i.e., a third flow identifier, to the first DC to resolve the DC establishment issue in the event of duplicate flow identifiers and enable multiplexing of the first DC and the second DC.

[0082] In some embodiments, the third flow identifier is unique within the first device, or the third flow identifier is unique within the m rows reused by the first device, thereby ensuring that the third flow identifier modified or reallocated for the first DC does not repeat the flow identifier of the established DC corresponding to the first device, thereby realizing the multiplexing of the first DC with other DCs.

[0083] 12) First indication information, the first indication information is used to indicate at least one of the following: flow identifier duplication, flow identifier modification, and flow identifier reallocation. That is, when the first flow identifier corresponding to the first DC is repeated or identical to the second flow identifier corresponding to the second DC, the first network element can indicate to the second network element through the first indication information that the requested first DC has a flow identifier duplication problem, so that the second network element can perform corresponding operations based on this, such as modifying the flow identifier, reallocating the flow identifier, re-initiating the DC establishment request, etc., to solve the DC establishment problem in the case of flow identifier duplication and realize the multiplexing of the first DC and the second DC.

[0084] 13) A first label, which is allocated by the first network element and is used to distinguish different DCs with the same flow identifier. That is, when the first flow identifier corresponding to the first DC is repeated or identical to the second flow identifier corresponding to the second DC, the first network element may add a label, i.e., the first label, to the first DC to distinguish different DCs with the same flow identifier. This resolves the DC establishment issue in the event of repeated flow identifiers and enables reuse of the first DC and the second DC.

[0085] In some embodiments, the first tag may include but is not limited to at least one of the following 131)-134).

[0086] 131) Information about the creator or initiator of the first DC, for example, UE, DC AS, sender, receiver, caller, or callee.

[0087] 132) The type of the first DC, the type including at least one of P2A, A2P, and P2P.

[0088] 133) Application information corresponding to the first DC, such as application ID, etc.

[0089] 134) Predetermined identification information, such as a preset tag, number, port number, etc. The number can be understood as a number or serial number generated to distinguish different DCs with the same flow identifier.

[0090] 14) Second indication information, the second indication information is used to indicate the allocation of a second label, and the second label is used to distinguish different DCs with the same flow identifier. That is, when the first flow identifier corresponding to the first DC is repeated or the same as the second flow identifier corresponding to the second DC, the first network element can send the second indication information so that the second network element adds a label for distinguishing different DCs with the same flow identifier to the first DC according to the second indication information, that is, the second label, to solve the DC establishment problem in the case of repeated flow identifiers and realize the multiplexing of the first DC and the second DC.

[0091] 15) Third indication information, the third indication information is used to indicate rejection of establishment of the first DC. That is, when the first flow identifier corresponding to the first DC is repeated or identical to the second flow identifier corresponding to the second DC, the first network element may instruct the first network element to reject establishment of the first DC by sending the second indication information.

[0092] It is worth noting that the first network element may also send the first indication information at the same time as sending the third indication information, wherein the first indication information is used to indicate or notify the second network element of the reason for rejecting the establishment of the first DC, so that the second network element can perform corresponding operations according to the rejection reason, such as modifying or reallocating the flow identifier of the first DC, re-initiating the DC establishment request corresponding to the first DC, abandoning the establishment of the first DC, etc., so as to solve the DC establishment problem in the case of repeated flow identifiers and realize the multiplexing of the first DC and the second DC.

[0093] 16) Fourth indication information, the fourth indication information is used to instruct the re-initiation of the DC establishment request. That is, when it is determined that the first flow identifier corresponding to the first DC is the same as or the same as the second flow identifier corresponding to the second DC, the first network element may instruct the first network element to re-initiate the DC establishment request by sending the fourth indication information to request the re-establishment of the first DC.

[0094] In some embodiments, the first network element may send the first indication information at the same time as sending the fourth indication information, so as to indicate to the second network element the reason for re-initiating the DC establishment request, thereby enabling the second network element to perform corresponding operations based on the rejection reason, such as re-initiating the DC establishment request based on a flow identifier different from the first flow identifier, etc., to solve the DC multiplexing problem in the case of repeated flow identifiers.

[0095] 17) A flow identifier list, wherein the flow identifier list includes the flow identifiers of the established DC corresponding to the first device. That is, when a first flow identifier corresponding to the first DC is duplicated or identical to a second flow identifier corresponding to a second DC, the first network element may implicitly indicate to the second network element, by sending the flow identifier list, that there is a duplicate flow identifier problem in the first DC requested to be established, so that the second network element performs corresponding operations based on the flow identifier list.

[0096] For example, if the first indication information is sent at the same time as the flow identifier list is sent, and the first indication information is used to indicate the modification of the flow identifier and the reallocation of the flow identifier, then the second network element can modify or reallocate the flow identifier of the first DC based on the first indication information and the flow identifier list, and the modified or reallocated flow identifier is different from the flow identifier in the flow identifier list to avoid the problem of repeated or identical flow identifiers.

[0097] For another example, if the fourth indication information is sent at the same time as the flow identifier list is sent, then the second network element may re-initiate the DC establishment request based on the fourth indication information to request the establishment of the first DC, and the flow identifier carried in the re-initiated DC establishment request is different from the flow identifier in the flow identifier list to avoid the problem of repeated or identical flow identifiers.

[0098] 18) Fifth indication information, the fifth indication information is used to instruct demultiplexing of the first DC. That is, when the first flow identifier corresponding to the first DC is repeated or identical to the second flow identifier corresponding to the second DC, the first network element may implicitly indicate that the requested establishment of the first DC has a duplicate flow identifier problem by sending the fifth indication information, so that the second network element demultiplexes the first DC based on the fifth indication information.

[0099] In some embodiments, for 17) and 18), in addition to implicitly indicating through the flow identifier list that the first DC requested by the second network element to be established has a flow identifier duplication problem, the first network element may also explicitly indicate that the first DC has a flow identifier duplication problem. For example, the first network element sends the first indication information at the same time as sending the flow identifier list, and the first indication information is used to indicate a flow identifier duplication problem.

[0100] 19) The first flow identifier. The first flow identifier is used to indicate the DC corresponding to the second message. For example, after receiving the second message, the second network element can determine, based on the first flow identifier, that the third flow identifier in the second message is the modified flow identifier corresponding to the first DC. The first indication information is used to indicate that the flow identifier of the first DC repeats, modifies, or reallocates the flow identifier of the first DC. The first label is used to distinguish the first DC from other DCs with the same flow identifier, etc.

[0101] It is worth noting that, for each of the information in 11)-19) above, the information included in the second message may be different depending on the solution.

[0102] For example, in the case of modifying the flow identifier of the first DC, if the first network element is modified autonomously, then the second message may include but is not limited to one or more of the third flow identifier, the first indication information for indicating flow repetition, the first flow identifier, etc.; if the second network element is modified, then the second message may include but is not limited to one or more of the first indication information, the flow identifier list, the first flow identifier, etc.

[0103] For the case where a label is added to the first DC to distinguish different DCs with the same flow identifier, if the first network element adds the label autonomously, then the second message may include but is not limited to one or more of the first label, the first indication information for indicating flow repetition, the first flow identifier, etc.; if the second network element is modified, then the second message may include but is not limited to one or more of the second indication information, the first indication information for indicating flow repetition, the first flow identifier, etc.

[0104] For the situation of triggering the retransmission of the DC establishment request corresponding to the first DC, the second network element may include one or more of the first flow identifier, the first indication information for indicating flow repetition, the fourth indication information, and the flow identifier list.

[0105] In the case of rejecting the DC establishment request, the second message may include one or more items of the third indication information, the first flow identifier, and the first indication information for indicating flow duplication.

[0106] For the case of demultiplexing the first DC, the second message may include one or more of the fifth indication information, the first flow identifier, etc.

[0107] It is worth noting that in this embodiment, for each of the aforementioned solutions, the first network element can be configured through protocol agreement or other means to determine which of the aforementioned solutions to actually adopt when solving the DC establishment and reuse problems in the case of repeated flow identifiers.

[0108] Correspondingly, for the second network element, after receiving the second message sent by the first network element according to the first message, it can perform corresponding operations according to the different information included in the second message to solve the DC establishment and multiplexing problems in the case of repeated flow identifiers. It should be noted that the first message sent by the second network element to the first network element can be sent when receiving the third message sent by the initiator of the establishment of the first DC (i.e., the second device), wherein the third message is used to request the establishment of the first DC for the first device.

[0109] Based on this, in this embodiment, after receiving the second message, the second network element may send a fourth message according to the second message. The fourth message may include but is not limited to at least one of the following 21)-29).

[0110] 21) The third flow identifier or the fourth flow identifier, where the fourth flow identifier is a flow identifier allocated by the second network element according to the first indication information, and the fourth flow identifier is different from the first flow identifier.

[0111] Among them, if the fourth information includes the third flow identifier, then the second network element can send the third flow identifier to the second device and the first device through the fourth message, so that the second device, the first device and the first network element and the second network element have a consistent understanding of the flow identifier of the first DC modified or reallocated by the first network element, and then realize reliable transmission of the data flow based on the multiplexed first DC.

[0112] If the fourth information includes the fourth flow identifier, then the second network element can send the fourth flow identifier to the first network element, the second device, and the first device through a fourth message, so that the first network element, the second device, and the first device have a consistent understanding of the flow identifier of the first DC modified or reallocated by the second network element, and thus realize reliable transmission of the data flow based on the multiplexed first DC.

[0113] It can be understood that the fourth flow identifier is generated by the second network element based on the first indication information, the flow identifier list, and one or more of the first indication information. For example, when the second network element determines that there is a flow identifier duplication problem in the first DC corresponding to the first flow identifier based on the first indication information, it generates a fourth flow identifier that is different from the flow identifiers in the flow identifier list to achieve modification, reallocation, etc. of the flow identifier.

[0114] In some embodiments, similar to the aforementioned third flow identifier, the fourth flow identifier is unique within the first device, or the third flow identifier or the fourth flow identifier is unique within the m rows reused by the first device, thereby ensuring that the fourth flow identifier modified or reallocated for the first DC does not repeat the flow identifier of the established DC corresponding to the first device, thereby realizing the multiplexing of the first DC with other DCs.

[0115] 22) Sixth indication information, where the sixth indication information is used to indicate at least one of a flow identifier being repeated, a flow identifier being modified, a flow identifier being replaced, and a flow identifier being updated.

[0116] The sixth indication information may be determined based on the first indication information included in the second message, or the sixth indication information may be determined based on the third flow identifier, first label, second indication information, etc. of the second message, and there is no limitation here.

[0117] In some embodiments, the second network element may send the sixth indication information to the second device via a fourth message, so that the second device is clear about the flow identification information of the first DC requested to be established, such as the reason for the failure to create the first DC, whether the flow identification corresponding to the established first DC is a modified or updated flow identification, etc.

[0118] 23) The first label or the second label, where the second label is allocated by the second network element according to the second indication information.

[0119] Among them, if the fourth message includes the first label, then the second network element can send the first label to the second device and the first device through the fourth message, so that the second device, the first device and the first network element and the second network element have a consistent understanding of the first label allocated by the first network element and used to distinguish the first DC, and then realize the multiplexing of the first DC and the reliable transmission of the data stream based on the first label and the first flow identifier.

[0120] If the fourth message includes the second label, then the second network element can send the second label to the first network element, the second device, and the first device through the fourth message, so that the first network element, the second device, and the first device have a consistent understanding of the second label allocated by the second network element and used to distinguish the first DC, and then realize the multiplexing of the first DC and the reliable transmission of the data stream based on the second label and the first flow identifier.

[0121] In some embodiments, similar to the aforementioned first label, the second label may also include but is not limited to at least one of the following 231)-234).

[0122] 231) Information about the creator or initiator of the first DC, for example, UE, DC AS, sender, receiver, caller, or callee.

[0123] 232) The type of the first DC, the type including at least one of P2A, A2P, and P2P.

[0124] 233) Application information corresponding to the first DC, such as application ID, etc.

[0125] 234) Predetermined identification information, such as tag, number, port number, etc.

[0126] 24) The flow identifier list.

[0127] Among them, the second network element can send the flow identifier list to the second device through the fourth message, so that the second device can re-initiate the DC establishment request based on the flow identifier list. For example, the second network element can re-initiate the DC establishment request based on other flow identifiers different from the flow identifiers included in the flow identifier list, thereby avoiding the problem of flow identifier duplication that may occur when establishing DC.

[0128] 25) Seventh indication information, where the seventh indication information is used to instruct to re-initiate a DC establishment request.

[0129] The second network element may send the seventh indication information to the second device, so that the second device re-initiates the DC establishment request based on the seventh indication information.

[0130] In some embodiments, when sending the seventh indication information, the second network element may also send the flow identifier list and at least one item of the first indication information, wherein the flow identifier list can be used by the second network element to use other flow identifiers different from the flow identifiers included in the flow identifier list when re-initiating a DC establishment request, thereby avoiding the problem of flow identifier duplication.

[0131] The first indication information is used for the second device to understand the reason for the failure of the first DC establishment or the reason for re-initiating the DC establishment request.

[0132] 26) Resource reservation request, where the resource reservation request is used to request to reserve DC demultiplexing resources for the first device and to reserve DC multiplexing resources for the second device.

[0133] In some embodiments, when the second network element sends the resource reservation request to, for example, the MF / MRF, through the fourth message, it may also send the first indication information to notify the MF / MRF, etc. of the reason for resource reservation.

[0134] 27) Eighth indication information, where the eighth indication information is used to indicate rejection of establishment of the first DC.

[0135] In some embodiments, when the second network element sends the eighth indication information to the second device, it may also send the first indication information to indicate to the second device the reason for rejecting the establishment of the first DC.

[0136] 28) Ninth indication information, where the ninth indication information is used to instruct the second device to re-initiate a DC establishment request based on target m rows, where the target m rows are different from the m rows corresponding to the second DC.

[0137] Among them, the second network element can send the ninth indication information to the second device through the fourth information, so that the second device can re-initiate the DC establishment request according to the target m line indicated by the ninth indication information, so as to avoid the second device requesting to multiplex the first DC and the second DC again, thereby avoiding the problem of duplicate flow identifiers.

[0138] In some embodiments, when the second network element sends the ninth indication information to the second device, it may also send the first indication information to indicate to the second device the reason for re-initiating the DC establishment request.

[0139] 29) The first flow identifier. The first flow identifier is used to indicate the DC corresponding to the fourth message. For example, after receiving the fourth message, the first network element may determine that each information in the fourth message corresponds to the first DC based on the first flow identifier.

[0140] It is worth noting that, in this embodiment, depending on the different flow identifier repetition processing schemes, the fourth message may include one or more of the aforementioned 21)-29).

[0141] For example, in the case of modifying the flow identifier of the first DC, the fourth message may include at least one of the third flow identifier (or fourth flow identifier), the first indication information, and the first flow identifier.

[0142] In the case where a label is added to the first DC to distinguish different DCs with the same flow identifier, the fourth message may include at least one of the first label (or second label), the first indication information for indicating the duplication of the flow identifier, and the first flow identifier.

[0143] In the case of rejecting or re-initiating the DC reconstruction request of the first DC reconstruction, the fourth message may include at least one of the flow identifier list, the seventh indication information, the first indication information for indicating the duplication of the flow identifier, and the first flow identifier.

[0144] In the case of demultiplexing the first DC, the fourth message may include at least one of the first indication information for indicating the duplication of the flow identifier, the ninth indication information, the first flow identifier, etc.

[0145] Based on this, for the second device, as the initiator of establishing the first DC, after receiving the fourth message sent by the second network element, it can adopt different operations according to the different information in the fourth message to solve the DC establishment and multiplexing problems in the case of repeated flow identifiers.

[0146] For example, if the fourth message includes the third flow identifier (or the fourth flow identifier) ​​and the first flow identifier, then the second device can determine that the first flow identifier corresponding to the first DC requested to be established is modified to the third flow identifier (or the fourth flow identifier), and data transmission can be performed based on the third flow identifier (or the fourth flow identifier).

[0147] For another example, if the fourth message includes the first tag (or the second tag) and the first flow identifier, then the second device can determine that the first flow identifier corresponding to the first DC requested to be established is repeated, and the first DC is newly added with the first tag (or the second tag), then the second device can transmit data based on the first tag (or the second tag) and the first flow identifier.

[0148] In some embodiments, the process of the second device performing data transmission based on the first tag (or the second tag) and the first flow identifier may include but is not limited to: the second device sending a fifth message, the fifth message including any one of the first tag and the second tag and the first flow identifier; wherein, as shown in FIG3 , the first tag or the second tag is carried in a target field, the target field is a reserved field in the message header of the fifth message, or the target field is a field in the fifth message used to carry user data. It can be understood that the field "Type" in FIG3 indicates the message type, "U" indicates whether the data is transmitted in an unordered manner, "B" indicates whether it is the first segment (Beginning fragment), "E" indicates whether it is the last segment (Ending fragment), "Length" indicates the length, "TSN" indicates the transmission sequence number (Transmission Sequence Number), "Stream Identifier S" indicates that the stream identifier is S, "Stream Sequence Number n" indicates that the stream sequence number is n, and "Payload Protocol Identifier" indicates the protocol identifier corresponding to the carried user data.

[0149] For another example, if the fourth message includes the flow identifier list, the seventh indication information and the first flow identifier, then the second device can determine that the first flow identifier corresponding to the first DC requested to be established is repeated, and the second device can re-initiate the DC establishment request based on the seventh indication information for the establishment of the first DC, and the flow identifier of the first DC carried in the DC establishment request is different from the flow identifier in the flow identifier list.

[0150] For example, if the fourth message includes the ninth indication information and the first flow identifier, then the second device can determine that the first flow identifier corresponding to the first DC requested to be established is repeated, and the second device can re-initiate the DC establishment request for the establishment of the first DC according to the target m line indicated in the ninth indication information to solve the flow identifier duplication problem that exists when the first DC is multiplexed.

[0151] Of course, for the above examples, the fourth message may also include sixth indication information so that the second device is aware of the reasons for flow identifier modification, label addition, and DC establishment request retransmission.

[0152] In addition, for the first device, the first device may receive a fourth message sent by the second network element. According to different fourth messages, the first device may perform different operations.

[0153] For example, if the fourth message includes the third flow identifier (or the fourth flow identifier) ​​and the first flow identifier, the first device may perform data transmission based on the third flow identifier (or the fourth flow identifier).

[0154] For another example, if the fourth message includes the first tag (or the second tag) and the first flow identifier, the second device may transmit data based on the first tag (or the second tag) and the first flow identifier.

[0155] In some embodiments, the process of data transmission by the first device based on the first tag (or the second tag) and the first flow identifier is similar to that of the second device. For example, it may include but is not limited to: the first device sends a sixth message, and the sixth message includes any one of the first tag and the second tag and the first flow identifier; wherein, as shown in Figure 3, the first tag or the second tag is carried in the target field, and the target field is a reserved field in the message header of the fifth message, or the target field is a field in the fifth message used to carry user data.

[0156] In this embodiment, the first network element receives a first message from the second network element, and the first message is used to establish a first DC for the first device. When the first flow identifier corresponding to the first DC is the same as the second flow identifier corresponding to the second DC, the first network element sends a second message to the second network element to realize DC establishment and multiplexing in the case of repeated flow identifiers.

[0157] For example, the problem of DC multiplexing being impossible due to duplicate flow identifiers can be solved by modifying the flow identifier, adding a label to distinguish DCs with the same flow identifier, re-initiating a DC establishment request, and demultiplexing, thereby ensuring the performance of the communication system and saving network resources.

[0158] Based on the description of the aforementioned method embodiment 200, the implementation process of the data channel establishment method provided in the embodiment of the present application is exemplarily described below with reference to examples, as follows. It is assumed that the first network element is a DCSF, the second network element is an IMS AS, the first device is UE-1, the second device is the first DC establishment requester, denoted as UE-2, and UE-1 has established at least one DC, such as an application DC, wherein the stream ID of the application DC (corresponding to the aforementioned second DC) corresponding to an APP-1 in the established DC is stream ID-1 (i.e., the second stream identifier).

[0159] Example 1

[0160] Assuming that the flow identifier duplication processing solution adopted in this example 1 is: modifying the flow identifier, then, as shown in FIG4 a , the data channel establishment process may include but is not limited to the following steps.

[0161] S401: UE-2 receives a third message sent by UE2 to the IMS AS providing service for UE-1, requesting to establish a first DC (such as application DC) for UE-1.

[0162] The third message may be a SIP Invite message or a SIP re-Invite message, and the third message may include but is not limited to at least one of the following 31)-32).

[0163] 31) Information about the application corresponding to the application DC, such as the application ID corresponding to APP-2.

[0164] 32) Stream ID corresponding to application DC: stream ID-1, which is the first stream identifier mentioned above.

[0165] Optionally, UE-2 may also carry the information of the application DC corresponding to APP-1 in the third message to request multiplexing of the first DC and the third DC corresponding to APP-1, such as requesting multiplexing by carrying the information of the application DCs of APP-1 and APP-2 in an m line of SDP.

[0166] S402: The IMS AS sends a first message to the DCSF serving UE-1 according to the third message, wherein the first message may be, but is not limited to, a Notify message, such as Nimsas_SessionEventControl_Notify.

[0167] Among them, the first message is determined according to the third message, so the first message may also include at least one of the aforementioned 31)-32).

[0168] S403: The DCSF determines a second DC to be multiplexed with the application DC (ie, the first DC) requested to be established.

[0169] Among them, if the first message is also used to request multiplexing, then the second DC can be determined by DCSF based on the DC multiplexing information (information of the third DC) corresponding to the first DC carried in the first message; or, if the first message is not used to request multiplexing, then the second DC can also be determined by DCSF based on the established DC corresponding to the UE-1.

[0170] S404: DSCF generates data channel media information (originating and terminating side DC media information) for the originating end and the terminating end, wherein the originating end is UE-2 and the terminating end is UE-1.

[0171] S405: When it is determined that the first DC requested to be established can be multiplexed with the established second DC, but the first stream identifier corresponding to the newly established first DC and the second stream identifier corresponding to the second DC are repeated, such as stream ID-1, the DCSF sends a second message to the IMS AS, such as Nimsas_MediaControl_MediaInstruction.

[0172] The second message may include at least one of the following: a third stream identifier (such as Stream ID-2), first indication information, and the first stream identifier.

[0173] The third flow identifier is obtained by DSCF modifying or reallocating the first flow identifier corresponding to the first DC, and is different from the second flow identifier corresponding to the second DC established in UE-1. The third flow identifier is unique within UE-1, or unique within m multiplexed rows of UE-1.

[0174] The first indication information is used to indicate at least one of: duplication of a flow identifier, modification of a flow identifier, and allocation of a new flow identifier.

[0175] S406, the IMS AS instructs the MF / MRF to reserve multiplexed resources (IMS AS requests MF / MRF to reserve media resource for multiplexed).

[0176] In one implementation, the second message may further include predetermined indication information to instruct the IMS AS to perform multiplexing. Then, the IMS AS may reserve resources according to the predetermined indication information.

[0177] S407: The IMS AS notifies the DCSF of the result of resource reservation, wherein the result of resource reservation may be carried in the Nimsas_MediaControl_MediaInstrution response.

[0178] S408: DCSF sends a response message to the IMS AS, such as Nimsas_SessionEventControl_Notify response.

[0179] In step S409, the IMS AS modifies the third message used to establish the application DC in step S401 by modifying or replacing the first stream identifier, stream ID-1, with a third stream identifier or a fourth stream identifier, such as stream ID-2, to obtain a fourth message. The fourth message may be, but is not limited to, a reINVITE message, and the IMS AS sends the fourth message, such as a reINVITE, to the I / S-CSCF.

[0180] The third flow identifier may be sent by the DCSF to the IMS AS through the second message, or the fourth flow identifier may be generated by the IMS AS according to the first indication information sent by the DCSF.

[0181] In addition, the IMS AS may further include information in the re-request message for multiplexing the newly established first DC with the established second DC.

[0182] S410, the I / S-CSCF sends the fourth message to UE-1, so as to request multiplexing of the DC (ie, the first DC) corresponding to APP-2 through the SDP in the fourth message.

[0183] Optionally, if the IMS AS generates the fourth flow identifier according to the first indication information, the IMS AS needs to notify the DCSF of the fourth flow identifier through a fourth message to ensure consistency in understanding of the flow identifier corresponding to the first DC by each network element.

[0184] S411-S12, UE-1 replies with an 18X message, indicating a response requesting reuse of the DC corresponding to APP-2 via SDP. The 18X message may be, but is not limited to, 183 or 180, and is routed to the IMS AS.

[0185] In addition, the 18X message may also include information on whether UE-1 accepts or does not accept the establishment of the first DC, and information on whether it accepts or does not accept multiplexing.

[0186] S413: The IMS AS sends a fourth message, such as an 18X message, to UE2.

[0187] Optionally, the fourth message may include at least one of the first flow identifier, the third flow identifier, the fourth flow identifier, and sixth indication information, wherein the sixth indication information is used to indicate at least one of the following: the flow identifier is modified, the flow identifier is replaced, and the flow identifier is updated.

[0188] It is worth noting that the purpose of carrying the first flow identifier in the fourth message is to notify UE-2 that the fourth message received is related to the first DC corresponding to the first flow identifier, such as the first flow identifier corresponding to the first DC is modified or replaced.

[0189] S414-S416, UE-1 responds with 200OK, completing the establishment and multiplexing of the first DC.

[0190] It is understood that the various implementations in this Example 1 can refer to the relevant descriptions in the aforementioned method embodiment 200. To avoid repetition, they will not be described here. In addition, this Example 1 may include more or fewer steps than the aforementioned ones, which is not limited here.

[0191] Example 2

[0192] Assuming that the flow identifier duplication processing solution adopted in this example 2 is: adding a label for distinguishing DCs with the same flow identifier, then, as shown in FIG4 b , the data channel establishment process may include but is not limited to the following steps.

[0193] S421: The IMS AS providing services for UE-1 receives a third message sent by UE2 for requesting to establish a first DC (such as an application DC), for example, a SIP Invite message or a SIP re-Invite message.

[0194] S422: The IMS AS sends a first message, such as a Notify message, to the DCSF providing service for UE-1 according to the third message. The first message may also include at least one of the above items 31)-32).

[0195] S423: The DCSF determines a second DC to be multiplexed with the application DC (ie, the first DC) requested to be established.

[0196] S424: DSCF generates data channel media information (originating and terminating side DC media information) for the originating end and the terminating end, wherein the originating end is UE-2 and the terminating end is UE-1.

[0197] It can be understood that the relevant contents of S421-S424 can refer to the relevant descriptions in the aforementioned S401-S404, and will not be repeated here.

[0198] S425: When it is determined that the first DC requested to be established can be multiplexed with the established second DC, but the first stream identifier corresponding to the newly established first DC and the second stream identifier corresponding to the second DC are repeated, such as stream ID-1, the DCSF sends a second message to the IMS AS, such as Nimsas_MediaControl_MediaInstruction.

[0199] The second message may include at least one of the first label (or second indication information), the first flow identifier, and the first indication information for indicating that the flow identifier is repeated.

[0200] The first label is allocated to the first DC by the DSCF to distinguish the first DC and the second DC having the same flow identifier.

[0201] The second indication information is used to instruct the second network element to allocate a second label to distinguish the first DC and the second DC having the same flow identifier.

[0202] S426, the IMS AS instructs the MF / MRF to reserve media resources for multiplexed.

[0203] In one implementation, the second message may further include predetermined indication information to instruct the IMS AS to perform multiplexing. Then, the IMS AS may instruct the MF / MRF to reserve resources according to the predetermined indication information.

[0204] In addition, when the IMS AS instructs the MF / MRF to reserve multiplexing resources, it may carry the first label or the second label in the resource reservation request. Then, after the MF / MRF receives a data packet from UE-1 or UE-2 through SCTP, it may determine the application DC corresponding to the data packet, such as the first DC, through the first flow identifier and the first label (or the second label), and then implement the correct routing of the data packet based on the corresponding first DC.

[0205] S427: The IMS AS notifies the DCSF of the resource reservation result, wherein the resource reservation result may be carried in the Nimsas_MediaControl_MediaInstrution response.

[0206] S428: DCSF sends a response message to the IMS AS, such as Nimsas_SessionEventControl_Notify response.

[0207] S429, the IMS AS modifies the third message used to establish the application DC in S421, such as additionally including the first tag or the second tag in the message, obtains a fourth message, such as a reINVITE message, and sends the fourth message to the I / S-CSCF.

[0208] The first label is sent by the DCSF to the IMS AS through the second message, and the second label is generated by the IMS AS according to the second indication information sent by the DCSF.

[0209] In addition, the IMS AS may further include in the re-request message information for multiplexing the newly established first DC with the established second DC.

[0210] S430, the I / S-CSCF sends the fourth message to UE-1, so as to request to reuse the DC (ie, the first DC) corresponding to APP-2 through the SDP in the fourth message.

[0211] Optionally, if the IMS AS generates the second label according to the second indication information, the IMS AS needs to notify the DCSF of the second label through a fourth message to ensure consistency in understanding of the second label among various network elements.

[0212] S431-S432, UE-1 replies with an 18X message, indicating a response to request multiplexing of the DC corresponding to APP-2 through SDP. The 18X message may be, but is not limited to, 183 or 180, and the 18X message is routed to the IMS AS.

[0213] In addition, the 18X message may also include information on whether UE-1 accepts or does not accept the establishment of the first DC, information on whether it accepts or does not accept multiplexing, etc.

[0214] S433: The IMS AS sends a fourth message, such as an 18X message, to UE2.

[0215] Optionally, the fourth message may include at least one of the first flow identifier, the first label, the second label, and sixth indication information, wherein the sixth indication information is used to indicate at least one of the flow identifier being modified, the flow identifier being replaced, and the flow identifier being updated.

[0216] It is worth noting that the purpose of carrying the first flow identifier in the fourth message is to notify UE-2 that the fourth message received is related to the first DC corresponding to the first flow identifier, such as adding a first label or a second label to the first DC.

[0217] S434-S436, UE-1 responds with 200OK, completing the establishment and multiplexing of the first DC.

[0218] Based on this, after completing the establishment of the first DC, if the UE-1 or the UE-2 needs to send a data packet, then UE-2 can send a fifth message, and the fifth message can carry the data packet, the first label (or the second label), and the first flow identifier, wherein, as shown in Figure 3, the first label (or the second label) can be carried through the reserved message header, or, carried through the first part of the user data.

[0219] Similar to the fifth message, the UE-1 can send a sixth message, which can carry the data packet, the first label (or the second label), and the first flow identifier, wherein, as shown in Figure 3, the first label (or the second label) can be carried through the reserved message header, or through the first part of the user data.

[0220] It is understood that the various implementations in this Example 2 can refer to the relevant descriptions in the aforementioned method embodiment 200. To avoid repetition, they will not be described here. In addition, this Example 2 may include more or fewer steps than the aforementioned ones, which is not limited here.

[0221] Example 3

[0222] Assuming that the flow identifier repetition processing solution adopted in this example 3 is: re-initiating a DC establishment request, then, as shown in FIG4c , the data channel establishment process may include but is not limited to the following steps.

[0223] Assuming that the solution for handling duplicate flow identifiers is to add a label for distinguishing DCs with the same flow identifier, then, as shown in FIG4 b , the data channel establishment process may include but is not limited to the following steps.

[0224] S441: The IMS AS providing services for UE-1 receives a third message sent by UE2 for requesting to establish a first DC (such as an application DC), for example, a SIP Invite message or a SIP re-Invite message.

[0225] S442: The IMS AS sends a first message, such as a Notify message, to the DCSF providing service for UE-1 according to the third message. The first message may also include at least one of the above items 31)-32).

[0226] S443: The DCSF determines a second DC to be multiplexed with the application DC (ie, the first DC) requested to be established.

[0227] S444: DSCF generates data channel media information (originating and terminating side DC media information) for the originating end and the terminating end, wherein the originating end is UE-2 and the terminating end is UE-1.

[0228] It can be understood that the relevant contents of S441-S444 can refer to the relevant descriptions in the aforementioned S401-S404, and will not be repeated here.

[0229] S445: When it is determined that the requested first DC can be multiplexed with the established second DC, but the first stream identifier corresponding to the newly established first DC and the second stream identifier corresponding to the second DC are repeated, such as stream ID-1, the DCSF sends a second message to the IMS AS, such as Nimsas_MediaControl_MediaInstruction.

[0230] The second message may include at least one of the third indication information, the fourth indication information, the flow identifier list, the first flow identifier, and the first indication information for indicating that the flow identifier is repeated.

[0231] The third indication information is used to instruct the first network element to reject the establishment of the first DC.

[0232] The fourth indication information is used to instruct UE-2 to re-initiate a DC establishment request.

[0233] S446: The IMS AS sends a fourth message, such as a 3xx, 4xx, 5xx, or 6xx message, to the initiator (ie, UE-2) according to the second message.

[0234] The fourth message may include at least one of the first flow identifier, the flow identifier list, seventh indication information, and sixth indication information for indicating that the flow identifier is repeated. The seventh indication information is used to instruct to re-initiate the DC establishment request.

[0235] Optionally, 3xx represents a response message starting with 3, such as 300, 301, 302, or 380.

[0236] 4xx represents a response message starting with 4, such as 405, 406, and 488.

[0237] 5xx represents a response message starting with 5, such as 500.

[0238] 6xx represents a response message starting with 6, such as 603 or 606.

[0239] S447, UE-2 performs corresponding operations according to the received fourth message (or response message), such as allocating a new flow identifier according to the seventh indication information, and re-initiating the request of S441 to request the reconstruction of the first DC.

[0240] Optionally, if the fourth message includes the flow identifier list, the UE-2 may allocate a flow identifier that is not repeated with any flow identifier in the flow identifier list according to the flow identifier list, so as to avoid a possible recurrence of a flow identifier duplication problem.

[0241] It is understood that the various implementations in this Example 3 can refer to the relevant descriptions in the aforementioned method embodiment 200. To avoid repetition, they will not be described here. In addition, this Example 2 may include more or fewer steps than the aforementioned ones, which is not limited here.

[0242] Example 4

[0243] Assuming that the flow identifier duplication processing scheme adopted in this example 4 is: demultiplexing the first DC, then, as shown in FIG4d , the data channel establishment process may include but is not limited to the following steps.

[0244] S451: The IMS AS providing services for UE-1 receives a third message sent by UE2 for requesting to establish a first DC (such as an application DC), for example, a SIP Invite message or a SIP re-Invite message.

[0245] S452: The IMS AS sends a first message, such as a Notify message, to the DCSF providing service for UE-1 according to the third message. The first message may also include at least one of the above 31)-32).

[0246] S453: The DCSF determines a second DC to be multiplexed with the application DC (ie, the first DC) requested to be established.

[0247] S454: DSCF generates data channel media information (originating and terminating side DC media information) for the originating end and the terminating end, wherein the originating end is UE-2 and the terminating end is UE-1.

[0248] It can be understood that the relevant contents of S451-S454 can refer to the relevant descriptions in the aforementioned S401-S404, and will not be repeated here.

[0249] S455: When it is determined that the first DC requested to be established can be multiplexed with the established second DC, but the first stream identifier corresponding to the newly established first DC and the second stream identifier corresponding to the second DC are repeated, such as stream ID-1, the DCSF determines to demultiplex the first DC and sends a second message, such as Nimsas_MediaControl_MediaInstruction, to the IMS AS.

[0250] The second message may include at least one of a first flow identifier, first indication information for indicating that the flow identifier is repeated, and fifth indication information, wherein the fifth indication information is used to indicate demultiplexing of the first DC.

[0251] S456, the IMS AS instructs the MF / MRF to reserve resources according to the fifth indication information (IMS AS requests MF / MRF to reserve media resources for multiplexed), wherein the reserved resources include demultiplexing resources reserved for UE-1 and multiplexing resources reserved for UE-2.

[0252] S457, the IMS AS notifies the DCSF of the result of resource reservation (Nimsas_MediaControl_MediaInstrution response).

[0253] S458, DCSF sends a response message (Nimsas_SessionEventControl_Notify response) to the IMS AS.

[0254] S459, the IMS AS modifies the third message used to establish the application DC in S451, such as additionally including the ninth indication information in the message, thereby obtaining a fourth message, such as a reINVITE message, and sending the fourth message to the I / S-CSCF.

[0255] The ninth indication information is used to instruct to re-initiate a DC establishment request based on target m rows, where the target m rows are different from the m rows corresponding to the second DC.

[0256] S460, I / S-CSCF sends the fourth message to UE-1, wherein the fourth message may include a ninth indication message, i.e., indicating that the application DC (i.e., the first DC) of APP-2 is carried through different m lines to realize the multiplexing of the first DC.

[0257] S461-S462, UE-1 replies with an 18X message, such as 183 or 180, which is routed to the IMS AS.

[0258] In addition, the 18X message may also include information on whether UE-1 accepts or does not accept the establishment of the first DC, and information on whether it accepts or does not accept multiplexing.

[0259] S463: The IMS AS sends a fourth message, such as an 18x message, to UE2 to respond to UE-2's multiplexing request for the first DC.

[0260] Optionally, the fourth message may include at least one of the first flow identifier and ninth indication information, wherein the ninth indication information is used to instruct to re-initiate the DC establishment request based on the target m row, that is, to agree to reuse the first DC.

[0261] It is worth noting that the purpose of carrying the first flow identifier in the fourth message is to notify UE-2 that the fourth message received is related to the first DC corresponding to the first flow identifier, such as demultiplexing the first DC corresponding to the first flow identifier and carrying the information of the first DC through different m lines.

[0262] S464-S466, UE-2 responds with 200OK, completing the establishment of the first DC.

[0263] It is understood that the various implementations in this Example 4 can refer to the relevant descriptions in the aforementioned method embodiment 200. To avoid repetition, they will not be described here. In addition, this Example 4 may include more or fewer steps than the aforementioned ones, which is not limited here.

[0264] FIG5 is a flow chart of a method 500 for establishing a data channel according to an exemplary embodiment of the present application. This method 500 may be, but is not limited to, performed by a second network element, specifically, by at least one of hardware and software installed in the second network element. In this embodiment, the method 500 may include at least the following steps.

[0265] S510. The second network element sends a first message to the first network element, where the first message is used to establish a first DC for the first device.

[0266] S520: The second network element receives a second message from the first network element.

[0267] Among them, the first network element and the second network element are network elements serving the first device, and the second message includes at least one of the following: a third flow identifier, the third flow identifier is the flow identifier allocated by the first network element, and the third flow identifier is different from the first flow identifier corresponding to the first DC; first indication information, the first indication information is used to indicate at least one of flow identifier duplication, flow identifier modification, and flow identifier reallocation; a first label, the first label is allocated by the first network element and is used to distinguish different DCs with the same flow identifier; second indication information, the second indication information is used to indicate the allocation of a second label, and the second label is used to distinguish different DCs with the same flow identifier; third indication information, the third indication information is used to indicate the rejection of the establishment of the first DC; fourth indication information, the fourth indication information is used to indicate the re-initiation of the DC establishment request; a flow identifier list, the flow identifier list includes the flow identifier of the established DC corresponding to the first device; the first flow identifier; fifth indication information, the fifth indication information is used to indicate the demultiplexing of the first DC.

[0268] In a possible implementation, the first message is further used to request multiplexing of the first DC.

[0269] In a possible implementation, the method also includes: the second network element sends a fourth message based on the second message; wherein the fourth message includes at least one of the following: the third flow identifier or the fourth flow identifier, the fourth flow identifier is the flow identifier assigned by the second network element based on the first indication information, and the fourth flow identifier is different from the first flow identifier; sixth indication information, the sixth indication information is used to indicate at least one of the flow identifier duplication, the flow identifier is modified, the flow identifier is replaced, and the flow identifier is updated; the first label or the second label, the second label is assigned by the second network element based on the second indication information; the flow identifier list; seventh indication information, the seventh indication information is used to indicate the re-initiation of the DC establishment request; a resource reservation request, the resource reservation request is used to request to reserve DC demultiplexing resources for the first device and to reserve DC multiplexing resources for the second device; eighth indication information, the eighth indication information is used to indicate the rejection of the establishment of the first DC; ninth indication information, the ninth indication information is used to indicate the re-initiation of the DC establishment request based on the target m row, the target m row is different from the m row corresponding to the second DC; the first flow identifier.

[0270] In a possible implementation, the third flow identifier or the fourth flow identifier is unique within the first device, or the third flow identifier or the fourth flow identifier is unique within m rows multiplexed by the first device.

[0271] In one possible implementation, the first tag or the second tag includes at least one of the following: information of the founder or initiator of the first DC; the type of the first DC, the type including at least one of person-to-application P2A, application-to-person A2P, and person-to-person P2P; application information corresponding to the first DC; and predetermined identification information.

[0272] In a possible implementation, the first network element includes a data channel signaling function DCSF; or the second network element includes an IP multimedia subsystem application server IMS AS; or the first device includes a terminal or a data channel application server DC AS.

[0273] It can be understood that each implementation method in method embodiment 500 has the same or corresponding technical features as each implementation method in the aforementioned method embodiment 200. Therefore, each implementation method in method embodiment 500 can refer to the relevant description in the aforementioned method embodiment 200 and achieve the same or corresponding technical effects. To avoid repetition, they will not be repeated here.

[0274] FIG6 is a flow chart of a method 600 for establishing a data channel according to an exemplary embodiment of the present application. This method 600 may be, but is not limited to, performed by a second device, specifically by at least one of hardware and software installed in the second device. In this embodiment, the method 600 may include at least the following steps.

[0275] S610: The second device sends a third message, where the third message is used to request to establish a first data channel DC for the first device.

[0276] S620: The second device receives a fourth message from the second network element.

[0277] The fourth message includes at least one of the following: a third flow identifier or a fourth flow identifier, the third flow identifier is the flow identifier assigned by the first network element, the fourth flow identifier is the flow identifier assigned by the second network element, and the third flow identifier and the fourth flow identifier are different from the first flow identifier corresponding to the first DC; sixth indication information, the sixth indication information is used to indicate at least one of the following: the flow identifier is repeated, the flow identifier is modified, the flow identifier is replaced, and the flow identifier is updated; a first label or a second label, the first label is assigned by the first network element, the second label is assigned by the second network element, and the first label or the second label is used to distinguish different DCs with the same flow identifier; the flow identifier list; seventh indication information, the seventh indication information is used to indicate the re-initiation of the DC establishment request; eighth indication information, the eighth indication information is used to indicate the rejection of the establishment of the first DC; ninth indication information, the ninth indication information is used to indicate the re-initiation of the DC establishment request based on the target m row, the target m row is different from the m row corresponding to the second DC, and the second DC includes at least one of the established DCs corresponding to the first device; the first flow identifier.

[0278] In a possible implementation, the third message is further used to request multiplexing of the first DC.

[0279] In a possible implementation, the third flow identifier or the fourth flow identifier is unique within the first device, or the third flow identifier or the fourth flow identifier is unique within m rows multiplexed by the first device.

[0280] In one possible implementation, the first tag or the second tag includes at least one of the following: information of the founder or initiator of the first DC; the type of the first DC, the type including at least one of person-to-application P2A, application-to-person A2P, and person-to-person P2P; application information corresponding to the first DC; and predetermined identification information.

[0281] In one possible implementation, the method also includes at least one of the following: the second device replaces the first flow identifier corresponding to the first DC with the third flow identifier or the fourth flow identifier, and performs data transmission based on the third flow identifier or the fourth flow identifier; the second device performs data transmission based on the first flow identifier and the first label; the second device re-initiates the DC establishment request for establishing the first DC based on the fifth flow identifier, wherein the fifth flow identifier is different from the flow identifiers in the flow identifier list; the second device re-initiates the DC establishment request for establishing the first DC based on the target m row.

[0282] In one possible implementation, the second device performs data transmission based on the first flow identifier and the first label, including: the second device sends a fifth message, the fifth message including any one of the first label and the second label and the first flow identifier; wherein the first label or the second label is carried in a target field, the target field is a reserved field in the message header of the fifth message, or the target field is a field in the fifth message used to carry user data.

[0283] In one possible implementation, the first network element includes a data channel signaling function DCSF; or, the second network element includes an IP multimedia subsystem application server IMS AS; or, the first device includes a terminal or a data channel application server DC AS; or, the second device is a terminal or a data channel application server DC AS.

[0284] It can be understood that each implementation method in method embodiment 600 has the same or corresponding technical features as each implementation method in the aforementioned method embodiment 200. Therefore, each implementation method in method embodiment 600 can refer to the relevant description in the aforementioned method embodiment 200 and achieve the same or corresponding technical effects. To avoid repetition, they will not be repeated here.

[0285] FIG7 is a flow chart of a method 700 for establishing a data channel according to an exemplary embodiment of the present application. This method 700 may be, but is not limited to, performed by a first device, specifically by at least one of hardware and software installed in the first device. In this embodiment, the method 700 may include at least the following steps.

[0286] S710. The first device receives a fourth message from the second network element.

[0287] Among them, the fourth message includes: a first label or a second label, the first label is allocated by the first network element, the second label is allocated by the second network element, the first label or the second label is used to distinguish different data channel DCs with the same flow identifier; a first flow identifier, the first flow identifier corresponds to the first DC.

[0288] In one possible implementation, the first tag or the second tag includes at least one of the following: information of the founder or initiator of the first DC; the type of the first DC, the type including at least one of person-to-application P2A, application-to-person A2P, and person-to-person P2P; application information corresponding to the first DC; and predetermined identification information.

[0289] In a possible implementation manner, the method further includes: the first device performing data transmission based on the first flow identifier and the first label.

[0290] In one possible implementation, the first device performs data transmission based on the first flow identifier and the first label, including: the first device sends a sixth message, the sixth message including any one of the first label and the second label and the first flow identifier; wherein the first label or the second label is carried in a target field, the target field is a reserved field in the message header of the sixth message, or the target field is a field in the sixth message used to carry user data.

[0291] In a possible implementation, the first network element includes a data channel signaling function DCSF; or the second network element includes an IP multimedia subsystem application server IMS AS; or the first device includes a terminal or a data channel application server DC AS.

[0292] It can be understood that each implementation method in method embodiment 700 has the same or corresponding technical features as each implementation method in the aforementioned method embodiment 200. Therefore, each implementation method in method embodiment 700 can refer to the relevant description in the aforementioned method embodiment 200 and achieve the same or corresponding technical effects. To avoid repetition, they will not be repeated here.

[0293] The data channel establishment method provided in the embodiment of the present application can be executed by a data channel establishment device. In the embodiment of the present application, the data channel establishment device executing the data channel establishment method is used as an example to illustrate the data channel establishment device provided in the embodiment of the present application.

[0294] As shown in Figure 8, it is a structural diagram of a data channel establishment device 800 provided in an embodiment of the present application, and the device 800 is applied to a first network element. The device 800 includes: a receiving module 810, for receiving a first message from a second network element, the first message is used to establish a first data channel DC for a first device, the first network element and the second network element are network elements serving the first device; a sending module, for sending a second message to the second network element when the first flow identifier corresponding to the first DC is the same as the second flow identifier corresponding to the second DC; the second DC includes at least one of the established DCs corresponding to the first device; the second message includes at least one of the following: a third flow identifier, the third flow identifier is a flow identifier assigned by the first network element, the third flow identifier is different from the first flow identifier; first indication information, the first indication information Used to indicate at least one of flow identifier duplication, flow identifier modification, and flow identifier reallocation; a first label, the first label is allocated by the first network element and is used to distinguish different DCs with the same flow identifier; second indication information, the second indication information is used to indicate the allocation of a second label, the second label is used to distinguish different DCs with the same flow identifier; third indication information, the third indication information is used to indicate the rejection of the establishment of the first DC; fourth indication information, the fourth indication information is used to indicate the re-initiation of the DC establishment request; a flow identifier list, the flow identifier list includes the flow identifiers of the established DC corresponding to the first device; the first flow identifier; fifth indication information, the fifth indication information is used to indicate the demultiplexing of the first DC.

[0295] In an optional implementation, the receiving module 810 is also used to: receive a fourth message from the second network element; wherein the fourth message includes at least one of the following: a fourth flow identifier, the fourth flow identifier is the flow identifier assigned by the second network element according to the first indication information, and the fourth flow identifier is different from the first flow identifier; a second label, the second label is assigned by the second network element according to the second indication information.

[0296] In an optional implementation manner, the third flow identifier or the fourth flow identifier is unique within the first device, or the third flow identifier or the fourth flow identifier is unique within m rows multiplexed by the first device.

[0297] In an optional implementation, the first tag or the second tag includes at least one of the following: information of the founder or initiator of the first DC; the type of the first DC, the type including at least one of person-to-application P2A, application-to-person A2P, and person-to-person P2P; application information corresponding to the first DC; and predetermined identification information.

[0298] In an optional implementation, the first message is further used to request multiplexing of the first DC.

[0299] In an optional implementation, when the first flow identifier corresponding to the first DC is the same as the second flow identifier corresponding to the second DC, sending a second message to the second network element includes: when it is determined that the first DC can or can be multiplexed with the second DC and the first flow identifier corresponding to the first DC is the same as the second flow identifier corresponding to the second DC, sending a second message to the second network element.

[0300] In an optional implementation, the first network element includes a data channel signaling function DCSF; or, the second network element includes an IP multimedia subsystem application server IMS AS; or, the first device includes a terminal or a data channel application server DC AS.

[0301] The first network element used by the data channel establishment device 800 in the embodiment of the present application can be a network-side device, or can be other devices other than the network-side device. For example, the network-side device can include, but is not limited to, the types of network-side devices 12 listed above. Other devices can include servers, network attached storage (NAS), etc., and are not specifically limited in the embodiment of the present application.

[0302] The data channel establishment device 800 provided in the embodiment of the present application can implement each process implemented by the method embodiment of Figure 2 and achieve the same technical effect. To avoid repetition, it will not be described here.

[0303] As shown in Figure 9, it is a structural diagram of a data channel establishment device 900 provided in an embodiment of the present application, and the device 900 is applied to a second network element, and the device 900 includes: a sending module 910, used to send a first message to a first network element, and the first message is used to establish a first DC for the first device; a receiving module 920, used to receive a second message from the first network element; wherein, the first network element and the second network element are network elements serving the first device, and the second message includes at least one of the following: a third flow identifier, the third flow identifier is a flow identifier assigned by the first network element, and the third flow identifier is different from the first flow identifier corresponding to the first DC; a first indication information, the first indication information is used to indicate the flow identifier At least one of: identifying duplication, modifying flow identifier, and reallocating flow identifier; a first label, the first label is allocated by the first network element and is used to distinguish different DCs with the same flow identifier; second indication information, the second indication information is used to indicate the allocation of a second label, the second label is used to distinguish different DCs with the same flow identifier; third indication information, the third indication information is used to indicate the rejection of the establishment of the first DC; fourth indication information, the fourth indication information is used to indicate the re-initiation of the DC establishment request; a flow identifier list, the flow identifier list includes the flow identifier of the established DC corresponding to the first device; the first flow identifier; fifth indication information, the fifth indication information is used to indicate the demultiplexing of the first DC.

[0304] In a possible implementation, the first message is further used to request multiplexing of the first DC.

[0305] In one possible implementation, the sending module 910 is also used to: send a fourth message according to the second message; wherein the fourth message includes at least one of the following: the third flow identifier or the fourth flow identifier, the fourth flow identifier is the flow identifier assigned by the second network element according to the first indication information, and the fourth flow identifier is different from the first flow identifier; sixth indication information, the sixth indication information is used to indicate at least one of the flow identifier duplication, the flow identifier is modified, the flow identifier is replaced, and the flow identifier is updated; the first label or the second label, the second label is assigned by the second network element according to the second indication information; the flow identifier list; seventh indication information, the seventh indication information is used to indicate the re-initiation of the DC establishment request; a resource reservation request, the resource reservation request is used to request to reserve DC demultiplexing resources for the first device and to reserve DC multiplexing resources for the second device; eighth indication information, the eighth indication information is used to indicate the rejection of the establishment of the first DC; ninth indication information, the ninth indication information is used to indicate the re-initiation of the DC establishment request based on the target m row, the target m row is different from the m row corresponding to the second DC; the first flow identifier.

[0306] In a possible implementation, the third flow identifier or the fourth flow identifier is unique within the first device, or the third flow identifier or the fourth flow identifier is unique within m rows multiplexed by the first device.

[0307] In one possible implementation, the first tag or the second tag includes at least one of the following: information of the founder or initiator of the first DC; the type of the first DC, the type including at least one of person-to-application P2A, application-to-person A2P, and person-to-person P2P; application information corresponding to the first DC; and predetermined identification information.

[0308] In a possible implementation, the first network element includes a data channel signaling function DCSF; or the second network element includes an IP multimedia subsystem application server IMS AS; or the first device includes a terminal or a data channel application server DC AS.

[0309] The second network element used by the data channel establishment device 900 in the embodiment of the present application can be a network-side device, or can be other devices other than the network-side device. For example, the network-side device can include, but is not limited to, the types of network-side devices 12 listed above. Other devices can include servers, network attached storage (NAS), etc., and are not specifically limited in the embodiment of the present application.

[0310] The data channel establishment device 900 provided in the embodiment of the present application can implement each process implemented by the method embodiment of Figure 5 and achieve the same technical effect. To avoid repetition, it will not be repeated here.

[0311] As shown in Figure 10, it is a structural diagram of a data channel establishment device 1000 provided in an embodiment of the present application, the device 1000 is applied to the second device, and the device 1000 includes: a sending module 1010, used to send a third message, the third message is used to request to establish a first data channel DC for the first device; a receiving module 1020, used to receive a fourth message from the second network element; wherein the fourth message includes at least one of the following: a third flow identifier or a fourth flow identifier, the third flow identifier is a flow identifier assigned by the first network element, the fourth flow identifier is a flow identifier assigned by the second network element, and the third flow identifier and the fourth flow identifier are different from the first flow identifier corresponding to the first DC; sixth indication information, the sixth indication information is used to indicate that the flow identifier is repeated, the flow identifier is At least one of the following items is modified, the flow identifier is replaced, and the flow identifier is updated; a first label or a second label, the first label is assigned by the first network element, the second label is assigned by the second network element, and the first label or the second label is used to distinguish different DCs with the same flow identifier; the flow identifier list; seventh indication information, the seventh indication information is used to indicate the re-initiation of the DC establishment request; eighth indication information, the eighth indication information is used to indicate the rejection of the establishment of the first DC; ninth indication information, the ninth indication information is used to indicate the re-initiation of the DC establishment request based on the target m rows, the target m rows are different from the m rows corresponding to the second DC, and the second DC includes at least one of the established DCs corresponding to the first device; the first flow identifier.

[0312] In a possible implementation, the third message is further used to request multiplexing of the first DC.

[0313] In a possible implementation, the third flow identifier or the fourth flow identifier is unique within the first device, or the third flow identifier or the fourth flow identifier is unique within m rows multiplexed by the first device.

[0314] In one possible implementation, the first tag or the second tag includes at least one of the following: information of the founder or initiator of the first DC; the type of the first DC, the type including at least one of person-to-application P2A, application-to-person A2P, and person-to-person P2P; application information corresponding to the first DC; and predetermined identification information.

[0315] In one possible implementation, the apparatus 1000 further includes a processing module for performing at least one of the following: replacing the first flow identifier corresponding to the first DC with the third flow identifier or the fourth flow identifier, and performing data transmission based on the third flow identifier or the fourth flow identifier; performing data transmission based on the first flow identifier and the first label; the second device re-initiating a DC establishment request for establishing the first DC based on a fifth flow identifier, wherein the fifth flow identifier is different from the flow identifiers in the flow identifier list; and re-initiating a DC establishment request for establishing the first DC based on a target m row.

[0316] In one possible implementation, the data transmission based on the first flow identifier and the first label includes: sending a fifth message, the fifth message including any one of the first label and the second label and the first flow identifier; wherein the first label or the second label is carried in a target field, the target field is a reserved field in the message header of the fifth message, or the target field is a field in the fifth message used to carry user data.

[0317] In one possible implementation, the first network element includes a data channel signaling function DCSF; or, the second network element includes an IP multimedia subsystem application server IMS AS; or, the first device includes a terminal or a data channel application server DC AS; or, the second device is a terminal or a data channel application server DC AS.

[0318] The second device used in the data channel establishment apparatus 1000 in the embodiment of the present application can be a terminal or other device other than a terminal. For example, the terminal can include but is not limited to the types of terminal 11 listed above, and the other device can be a data channel server, a network attached storage, etc., which is not specifically limited in the embodiment of the present application.

[0319] The data channel establishment device 1000 provided in the embodiment of the present application can implement each process implemented by the method embodiment of Figure 6 and achieve the same technical effect. To avoid repetition, it will not be repeated here.

[0320] As shown in Figure 11, it is a structural diagram of a data channel establishment device 1100 provided in an embodiment of the present application. The device 1100 is applied to a first device, and the device 1100 includes: a receiving module 1110, for receiving a fourth message from a second network element; wherein, the fourth message includes: a first label or a second label, the first label is assigned by the first network element, the second label is assigned by the second network element, the first label and the second label are used to distinguish different data channel DCs with the same flow identifier; a first flow identifier, the first flow identifier corresponds to the first DC.

[0321] In one possible implementation, the first tag or the second tag includes at least one of the following: information of the founder or initiator of the first DC; the type of the first DC, the type including at least one of person-to-application P2A, application-to-person A2P, and person-to-person P2P; application information corresponding to the first DC; and predetermined identification information.

[0322] In a possible implementation, the apparatus 1110 further includes: a processing module, configured to perform data transmission based on the first flow identifier and the first label.

[0323] In one possible implementation, the data transmission based on the first flow identifier and the first label includes: sending a sixth message, the sixth message including any one of the first label and the second label and the first flow identifier; wherein the first label or the second label is carried in a target field, the target field is a reserved field in the message header of the sixth message, or the target field is a field in the sixth message used to carry user data.

[0324] In a possible implementation, the first network element includes a data channel signaling function DCSF; or the second network element includes an IP multimedia subsystem application server IMS AS; or the first device includes a terminal or a data channel application server DC AS.

[0325] The first device used by the data channel establishment apparatus 1100 in the embodiment of the present application may be a terminal, or may be another device other than a terminal. For example, the terminal may include, but is not limited to, the types of terminal 11 listed above, and the other device may be a data channel server, a network attached storage (NAS), etc., which is not specifically limited in the embodiment of the present application.

[0326] The data channel establishment device 1100 provided in the embodiment of the present application can implement each process implemented by the method embodiment of Figure 7 and achieve the same technical effect. To avoid repetition, it will not be described here.

[0327] As shown in Figure 12, an embodiment of the present application also provides a communication device 1200, including a processor 1201 and a memory 1202, and the memory 1202 stores a program or instruction that can be run on the processor 1201. For example, 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 above-mentioned data channel establishment method embodiment 200 or 500, and can achieve the same technical effect; 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 above-mentioned data channel establishment method embodiment 600 or 700, and can achieve the same technical effect. To avoid repetition, it will not be repeated here.

[0328] 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 of the method embodiment shown in FIG6 or FIG7. This terminal embodiment corresponds to the first device-side or second device-side method embodiment described above. Each implementation process and implementation method of the above method embodiment can be applied to this terminal embodiment and can achieve the same technical effect. Specifically, FIG13 is a schematic diagram of the hardware structure of a terminal implementing an embodiment of the present application.

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

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

[0331] 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 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 an operating stick, which will not be repeated here.

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

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

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

[0335] Wherein, if the terminal acts as a second device, the radio frequency unit 1301 is used to send a third message, wherein the third message is used to request to establish a first data channel DC for the first device; and is used to receive a fourth message from the second network element; wherein the fourth message includes at least one of the following: a third flow identifier or a fourth flow identifier, wherein the third flow identifier is a flow identifier assigned by the first network element, and the fourth flow identifier is a flow identifier assigned by the second network element, and the third flow identifier and the fourth flow identifier are different from the first flow identifier corresponding to the first DC; sixth indication information, wherein the sixth indication information is used to indicate at least one of the following: a flow identifier is repeated, a flow identifier is modified, a flow identifier is replaced, and a flow identifier is updated; the first A label or a second label, the first label is allocated by the first network element, the second label is allocated by the second network element, the first label or the second label is used to distinguish different DCs with the same flow identifier; the flow identifier list; the seventh indication information, the seventh indication information is used to indicate the re-initiation of the DC establishment request; the eighth indication information, the eighth indication information is used to indicate the rejection of the establishment of the first DC; the ninth indication information, the ninth indication information is used to indicate the re-initiation of the DC establishment request based on the target m rows, the target m rows are different from the m rows corresponding to the second DC, the second DC includes at least one of the established DCs corresponding to the first device; the first flow identifier.

[0336] In a possible implementation, the third message is further used to request multiplexing of the first DC.

[0337] In a possible implementation, the third flow identifier or the fourth flow identifier is unique within the first device, or the third flow identifier or the fourth flow identifier is unique within m rows multiplexed by the first device.

[0338] In one possible implementation, the first tag or the second tag includes at least one of the following: information of the founder or initiator of the first DC; the type of the first DC, the type including at least one of person-to-application P2A, application-to-person A2P, and person-to-person P2P; application information corresponding to the first DC; and predetermined identification information.

[0339] In one possible implementation, the processor 1310 is used for at least one of the following: replacing the first flow identifier corresponding to the first DC with the third flow identifier or the fourth flow identifier, and performing data transmission based on the third flow identifier or the fourth flow identifier; performing data transmission based on the first flow identifier and the first label; the second device re-initiating a DC establishment request for establishing the first DC based on a fifth flow identifier, wherein the fifth flow identifier is different from the flow identifiers in the flow identifier list; and re-initiating a DC establishment request for establishing the first DC based on a target m row.

[0340] In one possible implementation, the data transmission based on the first flow identifier and the first label includes: sending a fifth message, the fifth message including any one of the first label and the second label and the first flow identifier; wherein the first label or the second label is carried in a target field, the target field is a reserved field in the message header of the fifth message, or the target field is a field in the fifth message used to carry user data.

[0341] In one possible implementation, the first network element includes a data channel signaling function DCSF; or, the second network element includes an IP multimedia subsystem application server IMS AS; or, the first device includes a terminal or a data channel application server DC AS; or, the second device is a terminal or a data channel application server DC AS.

[0342] If the terminal acts as the first device, the radio frequency unit 1301 is used to receive a fourth message from the second network element; wherein the fourth message includes: a first label or a second label, the first label is assigned by the first network element, the second label is assigned by the second network element, the first label and the second label are used to distinguish different data channels DC with the same flow identifier; a first flow identifier, the first flow identifier corresponds to the first DC.

[0343] In one possible implementation, the first tag or the second tag includes at least one of the following: information of the founder or initiator of the first DC; the type of the first DC, the type including at least one of person-to-application P2A, application-to-person A2P, and person-to-person P2P; application information corresponding to the first DC; and predetermined identification information.

[0344] In a possible implementation, the processor 1310 is configured to perform data transmission based on the first flow identifier and the first label.

[0345] In one possible implementation, the data transmission based on the first flow identifier and the first label includes: sending a sixth message, the sixth message including any one of the first label and the second label and the first flow identifier; wherein the first label or the second label is carried in a target field, the target field is a reserved field in the message header of the sixth message, or the target field is a field in the sixth message used to carry user data.

[0346] In a possible implementation, the first network element includes a data channel signaling function DCSF; or the second network element includes an IP multimedia subsystem application server IMS AS; or the first device includes a terminal or a data channel application server DC AS.

[0347] It can be understood that the implementation process of each implementation method mentioned in this embodiment can refer to the relevant description of method embodiment 600 or 700, and achieve the same or corresponding technical effects. To avoid repetition, it will not be repeated here.

[0348] 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 method embodiment shown in Figure 2 or Figure 5. This network-side device embodiment corresponds to the first network element side or second network element side method embodiment described above, and each implementation process and implementation method of the above method embodiment can be applied to this network-side device embodiment and can achieve the same technical effects.

[0349] Specifically, the embodiment of the present application further provides a network side device. As shown in FIG14 , 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).

[0350] Specifically, the network side device 1400 of the embodiment of the present application also includes: instructions or programs stored in the memory 1403 and executable on the processor 1401. The processor 1401 calls the instructions or programs in the memory 1403 to execute the methods executed by the modules shown in FIG8 or FIG9 and achieve the same technical effect. To avoid repetition, they will not be elaborated here.

[0351] 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 above-mentioned data channel establishment method embodiment 200 or 500 or 600 or 700 are implemented, and the same technical effect can be achieved. To avoid repetition, it will not be repeated here.

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

[0353] An embodiment of the present application further provides a chip, which includes a processor and a communication interface, the communication interface and the processor are coupled, and the processor is used to run programs or instructions to implement the various processes of the above-mentioned data channel establishment method embodiment 200 or 500 or 600 or 700, and can achieve the same technical effect. To avoid repetition, it will not be repeated here.

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

[0355] 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 above-mentioned data channel establishment method embodiment 200 or 500 or 600 or 700, and can achieve the same technical effect. To avoid repetition, it will not be repeated here.

[0356] An embodiment of the present application also provides a wireless communication system, including: a first network element, a second network element, a first device and a second device. The first network element can be used to implement the various processes of the above-mentioned data channel establishment method embodiment 200, the second network element can be used to implement the various processes of the above-mentioned data channel establishment method embodiment 500, the first device can be used to implement the various processes of the above-mentioned data channel establishment method embodiment 700, and the second network element can be used to implement the various processes of the above-mentioned data channel establishment method embodiment 600, and can achieve the same technical effect. To avoid repetition, they will not be repeated here.

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

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

[0359] 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, comprising: A first network element receives a first message from a second network element, where the first message is used to establish a first data channel DC for a first device, and the first network element and the second network element are network elements serving the first device; When the first flow identifier corresponding to the first DC is the same as the second flow identifier corresponding to the second DC, the first network element sends a second message to the second network element; wherein the second DC includes at least one of the established DCs corresponding to the first device; The second message includes at least one of the following: a third flow identifier, where the third flow identifier is a flow identifier allocated by the first network element and is different from the first flow identifier; first indication information, where the first indication information is used to indicate at least one of: a flow identifier duplication, a flow identifier modification, and a flow identifier reallocation; A first label, where the first label is allocated by the first network element and is used to distinguish different DCs having the same flow identifier; Second indication information, where the second indication information is used to indicate allocation of a second label, where the second label is used to distinguish different DCs having the same flow identifier; third indication information, where the third indication information is used to indicate that establishment of the first DC is rejected; Fourth indication information, where the fourth indication information is used to instruct to re-initiate a DC establishment request; a flow identifier list, wherein the flow identifier list includes flow identifiers of established DCs corresponding to the first device; the first stream identifier; Fifth indication information, where the fifth indication information is used to instruct demultiplexing of the first DC.

2. The method according to claim 1, wherein The method further comprises: The first network element receives a fourth message from the second network element; The fourth message includes at least one of the following: a fourth flow identifier, where the fourth flow identifier is a flow identifier assigned by the second network element according to the first indication information, and the fourth flow identifier is different from the first flow identifier; The second label is allocated by the second network element according to the second indication information.

3. The method according to claim 1 or 2, wherein The third stream identifier or the fourth stream identifier is unique within the first device, or the third stream identifier or the fourth stream identifier is unique within the media m multiplexed by the first device.

4. The method according to claim 1 or 2, wherein The first tag or the second tag includes at least one of the following: Information about the founder or initiator of the first DC; The type of the first DC, the type including at least one of person-to-application P2A, application-to-person A2P, and person-to-person P2P; application information corresponding to the first DC; Reservation identification information.

5. The method according to any one of claims 1 to 4, wherein The first message is also used to request multiplexing of the first DC.

6. The method according to any one of claims 1 to 4, wherein The sending of the second message by the first network element to the second network element when the first flow identifier corresponding to the first DC is the same as the second flow identifier corresponding to the second DC includes: The first network element sends a second message to the second network element when determining that the first DC can or can be multiplexed with the second DC and the first flow identifier corresponding to the first DC is the same as the second flow identifier corresponding to the second DC.

7. The method according to any one of claims 1 to 6, wherein The first network element includes a data channel signaling function DCSF; Or, the second network element includes an IP Multimedia Subsystem Application Server IMS AS; Alternatively, the first device includes a terminal or a data channel application server DC AS.

8. A method for establishing a data channel, comprising: The second network element sends a first message to the first network element, where the first message is used to establish a first DC for the first device; The second network element receives a second message from the first network element; The first network element and the second network element are network elements serving the first device, and the second message includes at least one of the following: A third flow identifier, where the third flow identifier is a flow identifier allocated by the first network element, and the third flow identifier is different from the first flow identifier corresponding to the first DC; first indication information, where the first indication information is used to indicate at least one of: a flow identifier duplication, a flow identifier modification, and a flow identifier reallocation; A first label, where the first label is allocated by the first network element and is used to distinguish different DCs having the same flow identifier; Second indication information, where the second indication information is used to indicate allocation of a second label, where the second label is used to distinguish different DCs having the same flow identifier; third indication information, where the third indication information is used to indicate that establishment of the first DC is rejected; Fourth indication information, where the fourth indication information is used to instruct to re-initiate a DC establishment request; a flow identifier list, wherein the flow identifier list includes flow identifiers of established DCs corresponding to the first device; the first stream identifier; Fifth indication information, where the fifth indication information is used to instruct demultiplexing of the first DC.

9. The method of claim 8, wherein: The first message is also used to request multiplexing of the first DC.

10. The method of claim 8, wherein: The method further comprises: The second network element sends a fourth message according to the second message; The fourth message includes at least one of the following: the third flow identifier or the fourth flow identifier, where the fourth flow identifier is a flow identifier allocated by the second network element according to the first indication information, and the fourth flow identifier is different from the first flow identifier; Sixth indication information, where the sixth indication information is used to indicate at least one of a flow identifier being repeated, a flow identifier being modified, a flow identifier being replaced, and an updated flow identifier; the first label or the second label, where the second label is allocated by the second network element according to the second indication information; the flow identifier list; Seventh indication information, where the seventh indication information is used to instruct to re-initiate a DC establishment request; A resource reservation request, the resource reservation request being used to request reservation of DC demultiplexing resources for the first device and DC multiplexing resources for the second device; eighth indication information, where the eighth indication information is used to indicate rejection of establishment of the first DC; ninth indication information, where the ninth indication information is used to instruct to re-initiate a DC establishment request based on target media rows m, where the target m rows are different from the m rows corresponding to the second DC; The first flow identifier.

11. The method according to any one of claims 8 to 10, wherein: The third flow identifier or the fourth flow identifier is unique within the first device, or the third flow identifier or the fourth flow identifier is unique within m rows multiplexed by the first device.

12. The method according to any one of claims 8 to 10, wherein: The first tag or the second tag includes at least one of the following: Information about the founder or initiator of the first DC; The type of the first DC, the type including at least one of person-to-application P2A, application-to-person A2P, and person-to-person P2P; application information corresponding to the first DC; Reservation identification information.

13. The method according to any one of claims 8 to 12, wherein: The first network element includes a data channel signaling function DCSF; Or, the second network element includes an IP Multimedia Subsystem Application Server IMS AS; Alternatively, the first device includes a terminal or a data channel application server DC AS.

14. A method for establishing a data channel, comprising: The second device sends a third message, where the third message is used to request to establish a first data channel DC for the first device; The second device receives a fourth message from the second network element; The fourth message includes at least one of the following: a third flow identifier or a fourth flow identifier, wherein the third flow identifier is a flow identifier allocated by the first network element, and the fourth flow identifier is a flow identifier allocated by the second network element, and the third flow identifier and the fourth flow identifier are different from the first flow identifier corresponding to the first DC; Sixth indication information, where the sixth indication information is used to indicate at least one of a flow identifier being repeated, a flow identifier being modified, a flow identifier being replaced, and an updated flow identifier; A first label or a second label, where the first label is allocated by the first network element, and the second label is allocated by the second network element, and the first label or the second label is used to distinguish different DCs with the same flow identifier; the flow identifier list; Seventh indication information, where the seventh indication information is used to instruct to re-initiate a DC establishment request; eighth indication information, where the eighth indication information is used to indicate rejection of establishment of the first DC; ninth indication information, where the ninth indication information is used to instruct to re-initiate a DC establishment request based on target media rows m, where the target m rows are different from the m rows corresponding to a second DC, where the second DC includes at least one of the established DCs corresponding to the first device; The first flow identifier.

15. The method of claim 14, wherein: The third message is also used to request multiplexing of the first DC.

16. The method of claim 14, wherein: The third flow identifier or the fourth flow identifier is unique within the first device, or the third flow identifier or the fourth flow identifier is unique within m rows multiplexed by the first device.

17. The method of claim 14, wherein: The first tag or the second tag includes at least one of the following: Information about the founder or initiator of the first DC; The type of the first DC, the type including at least one of person-to-application P2A, application-to-person A2P, and person-to-person P2P; application information corresponding to the first DC; Reservation identification information.

18. The method according to any one of claims 14 to 17, wherein: The method further comprises at least one of the following: The second device replaces the first flow identifier corresponding to the first DC with the third flow identifier or the fourth flow identifier, and performs data transmission based on the third flow identifier or the fourth flow identifier; The second device performs data transmission based on the first flow identifier and the first label; The second device re-initiates a DC establishment request for establishing the first DC based on a fifth flow identifier, wherein the fifth flow identifier is different from the flow identifiers in the flow identifier list; The second device re-initiates the DC establishment request for the first DC establishment based on the target m row.

19. The method of claim 18, wherein: The second device performs data transmission based on the first flow identifier and the first label, including: The second device sends a fifth message, where the fifth message includes any one of the first tag and the second tag and the first flow identifier; The first tag or the second tag is carried in a target field, and the target field is a reserved field in a message header of the fifth message, or the target field is a field in the fifth message used to carry user data.

20. The method according to any one of claims 14 to 19, wherein The first network element includes a data channel signaling function DCSF; Or, the second network element includes an IP Multimedia Subsystem Application Server IMS AS; Or, the first device includes a terminal or a data channel application server DC AS; Alternatively, the second device is a terminal or a data channel application server DC AS.

21. A method for establishing a data channel, comprising: The first device receives a fourth message from the second network element; The fourth message includes: A first label or a second label, where the first label is allocated by the first network element, and the second label is allocated by the second network element, and the first label or the second label is used to distinguish different data channels DC with the same flow identifier; A first flow identifier, where the first flow identifier corresponds to a first DC.

22. The method of claim 21, wherein: The first tag or the second tag includes at least one of the following: Information about the founder or initiator of the first DC; The type of the first DC, the type including at least one of person-to-application P2A, application-to-person A2P, and person-to-person P2P; application information corresponding to the first DC; Reservation identification information.

23. The method of any one of claims 21-22, wherein The method further comprises: The first device performs data transmission based on the first flow identifier and the first label.

24. The method of claim 23, wherein: The first device performs data transmission based on the first flow identifier and the first label, including: The first device sends a sixth message, where the sixth message includes any one of the first tag and the second tag and the first flow identifier; The first tag or the second tag is carried in a target field, and the target field is a reserved field in a message header of the sixth message, or the target field is a field in the sixth message used to carry user data.

25. The method of any one of claims 21 to 24, wherein The first network element includes a data channel signaling function DCSF; Or, the second network element includes an IP Multimedia Subsystem Application Server IMS AS; Alternatively, the first device includes a terminal or a data channel application server DC AS.

26. A data channel establishment device, applied to a first network element, comprising: a receiving module, configured to receive a first message from a second network element, where the first message is used to establish a first data channel DC for a first device, where the first network element and the second network element are network elements serving the first device; A sending module, configured to send a second message to the second network element when the first flow identifier corresponding to the first DC is the same as the second flow identifier corresponding to the second DC; wherein the second DC includes at least one of the established DCs corresponding to the first device; The second message includes at least one of the following: a third flow identifier, where the third flow identifier is a flow identifier allocated by the first network element and is different from the first flow identifier; first indication information, where the first indication information is used to indicate at least one of: a flow identifier duplication, a flow identifier modification, and a flow identifier reallocation; A first label, where the first label is allocated by the first network element and is used to distinguish different DCs having the same flow identifier; Second indication information, where the second indication information is used to indicate allocation of a second label, where the second label is used to distinguish different DCs having the same flow identifier; third indication information, where the third indication information is used to indicate that establishment of the first DC is rejected; Fourth indication information, where the fourth indication information is used to instruct to re-initiate a DC establishment request; a flow identifier list, wherein the flow identifier list includes flow identifiers of established DCs corresponding to the first device; the first stream identifier; Fifth indication information, where the fifth indication information is used to instruct demultiplexing of the first DC.

27. The apparatus of claim 26, wherein: The receiving module is further configured to receive a fourth message from the second network element; The fourth message includes at least one of the following: a fourth flow identifier, where the fourth flow identifier is a flow identifier assigned by the second network element according to the first indication information, and the fourth flow identifier is different from the first flow identifier; The second label is allocated by the second network element according to the second indication information.

28. A data channel establishment device, applied to a second network element, comprising: A sending module, configured to send a first message to a first network element, where the first message is used to establish a first DC for the first device; A receiving module, configured to receive a second message from the first network element; The first network element and the second network element are network elements serving the first device, and the second message includes at least one of the following: A third flow identifier, where the third flow identifier is a flow identifier allocated by the first network element, and the third flow identifier is different from the first flow identifier corresponding to the first DC; first indication information, where the first indication information is used to indicate at least one of: a flow identifier duplication, a flow identifier modification, and a flow identifier reallocation; A first label, where the first label is allocated by the first network element and is used to distinguish different DCs having the same flow identifier; Second indication information, where the second indication information is used to indicate allocation of a second label, where the second label is used to distinguish different DCs having the same flow identifier; third indication information, where the third indication information is used to indicate that establishment of the first DC is rejected; Fourth indication information, where the fourth indication information is used to instruct to re-initiate a DC establishment request; a flow identifier list, wherein the flow identifier list includes flow identifiers of established DCs corresponding to the first device; the first stream identifier; Fifth indication information, where the fifth indication information is used to instruct demultiplexing of the first DC.

29. The apparatus of claim 28, wherein The sending module is further configured to send a fourth message according to the second message; The fourth message includes at least one of the following: the third flow identifier or the fourth flow identifier, where the fourth flow identifier is a flow identifier allocated by the second network element according to the first indication information, and the fourth flow identifier is different from the first flow identifier; Sixth indication information, where the sixth indication information is used to indicate at least one of a flow identifier being repeated, a flow identifier being modified, a flow identifier being replaced, and an updated flow identifier; the first label or the second label, where the second label is allocated by the second network element according to the second indication information; the flow identifier list; Seventh indication information, where the seventh indication information is used to instruct to re-initiate a DC establishment request; A resource reservation request, the resource reservation request being used to request reservation of DC demultiplexing resources for the first device and DC multiplexing resources for the second device; eighth indication information, where the eighth indication information is used to indicate rejection of establishment of the first DC; ninth indication information, where the ninth indication information is used to instruct to re-initiate a DC establishment request based on target m rows, where the target m rows are different from the m rows corresponding to the second DC; The first flow identifier.

30. A data channel establishment device, applied to a second device, comprising: A sending module, configured to send a third message, where the third message is used to request establishment of a first data channel DC for the first device; A receiving module, configured to receive a fourth message from the second network element; The fourth message includes at least one of the following: a third flow identifier or a fourth flow identifier, wherein the third flow identifier is a flow identifier allocated by the first network element, and the fourth flow identifier is a flow identifier allocated by the second network element, and the third flow identifier and the fourth flow identifier are different from the first flow identifier corresponding to the first DC; Sixth indication information, where the sixth indication information is used to indicate at least one of a flow identifier being repeated, a flow identifier being modified, a flow identifier being replaced, and an updated flow identifier; A first label or a second label, where the first label is allocated by the first network element, and the second label is allocated by the second network element, and the first label or the second label is used to distinguish different DCs with the same flow identifier; the flow identifier list; Seventh indication information, where the seventh indication information is used to instruct to re-initiate a DC establishment request; eighth indication information, where the eighth indication information is used to indicate rejection of establishment of the first DC; ninth indication information, where the ninth indication information is used to instruct to re-initiate a DC establishment request based on target m rows, where the target m rows are different from the m rows corresponding to a second DC, where the second DC includes at least one of the established DCs corresponding to the first device; The first flow identifier.

31. The apparatus of claim 30, wherein: The apparatus further includes a processing module configured to: replacing the first flow identifier corresponding to the first DC with the third flow identifier or the fourth flow identifier, and performing data transmission based on the third flow identifier or the fourth flow identifier; performing data transmission based on the first flow identifier and the first label; re-initiating a DC establishment request for establishing the first DC based on a fifth flow identifier, wherein the fifth flow identifier is different from the flow identifiers in the flow identifier list; Re-initiate the DC establishment request for the first DC establishment based on the target m rows.

32. A data channel establishment device, applied to a first device, comprising: A receiving module, configured to receive a fourth message from the second network element; The fourth message includes: A first label or a second label, where the first label is allocated by the first network element, and the second label is allocated by the second network element, and the first label and the second label are used to distinguish different data channels DC with the same flow identifier; A first flow identifier, where the first flow identifier corresponds to a first DC.

33. The apparatus of claim 32, wherein: The device further comprises: A processing module is configured to transmit data based on the first flow identifier and the first label.

34. A communication device comprising a processor and a memory, the memory storing a program or instruction executable on the processor, wherein the program or instruction, when executed by the processor, implements the steps of the method according to any one of claims 1 to 7, or implements the steps of the method according to any one of claims 8 to 13, or implements the steps of the method according to any one of claims 14 to 20, or implements the steps of the method according to any one of claims 21 to 25.

35. A readable storage medium storing a program or instruction, wherein when the program or instruction is executed by a processor, the program or instruction implements the steps of the method according to any one of claims 1 to 7, or implements the steps of the method according to any one of claims 8 to 13, or implements the steps of the method according to any one of claims 14 to 20, or implements the steps of the method according to any one of claims 21 to 25.

Images