A communication method and a communication device

Abstract

The application provides a communication method and device, and the method provided by the application enables each node to transmit data through MQTT protocol by deploying MQTT protocol in each node in a data flow link, so that a data communication structure supporting on-the-fly calculation and arbitrary topology is constructed. The method provided by the application can improve the efficiency of data transmission.

Description

Technical Field

[0001] This application relates to the field of wireless communication technology, and more specifically, to a communication method and a communication device. Background Technology

[0002] With the development of wireless communication technology, the basic function of mobile communication networks will begin to shift from information transmission channels to data management platforms. Intrinsic sensing and intelligence are two major new capabilities for future communication networks. The former generates massive amounts of data through sensing devices, perceiving the network's own state, surrounding environment, and user / device behavior. The latter uses technologies such as Artificial Intelligence (AI) and digital twins for modeling, analysis, and automated decision-making to improve network operational efficiency, enhance system performance, or provide data services for intelligent applications. Existing data-bearing architectures cannot support the "on-the-path computing" and "arbitrary topology" capabilities required by future communication networks. Summary of the Invention

[0003] This application provides a communication method and apparatus that improves the flexibility and scalability of the communication system while meeting the requirements of in-path computing and arbitrary topology for future data transmission.

[0004] Firstly, a method is provided that can be performed by an apparatus (e.g., a communication apparatus). The apparatus can be a device (such as a network device), or it can be a component of a device (e.g., a chip (such as a modem chip, also known as a baseband chip, or a system-on-a-chip (SoC) chip containing a modem core, or a system-in-package (SIP) chip), a chip system, or a circuit), which is not limited in this application. The following description primarily uses a first communication apparatus as an example.

[0005] The first communication device may be a base station or a network function (NF) element; the second communication device may be a data controller (DC); and the third communication device may be a data communication proxy (DCP).

[0006] The method includes: receiving a first request message from a second communication device, the first request message being used to request the establishment of a data session, wherein the first request message includes a first topic, the first topic being the subject of data transmitted in the data session; establishing a data session with a third communication device based on the first request message; encapsulating first data corresponding to the first topic according to a first protocol stack to obtain a first data packet, the first protocol stack including the Message Queuing Telemetry Transport (MQTT) protocol; and sending the first data packet to the third communication device.

[0007] Based on the above scheme, with both the first and third communication devices deploying the MQTT protocol, each node can transmit data via the MQTT protocol, thus constructing a data communication structure that supports in-path computing and arbitrary topology. Furthermore, the MQTT protocol is a lightweight message transmission protocol, enabling efficient communication between nodes with minimal overhead, thereby improving the flexibility and scalability of the communication system.

[0008] In conjunction with the first aspect, in some implementations of the first aspect, the method further includes: receiving first data from a terminal device.

[0009] In conjunction with the first aspect, in some implementations of the first aspect, the method further includes: sending second data to a terminal device, the second data being obtained by processing the first data.

[0010] Based on the above scheme, the first communication device encapsulates the first data from the terminal device, thereby assisting the terminal device in data transmission and improving data transmission efficiency. Specifically, for terminal devices with limited capabilities (e.g., those that do not support the MQTT protocol), this method enables data transmission based on the MQTT protocol.

[0011] In conjunction with the first aspect, some implementations of the first aspect include: the first data packet includes a data service identifier (DSID) and / or a data agent identifier (DAID).

[0012] Based on the above scheme, by adding DSID and / or DAID to the first data packet, it is convenient for each node to collect relevant information while enabling differentiated management. For example, DSID is used to identify a specific data service task, so each node can perform different traffic control for different data services to improve the utilization of communication resources.

[0013] Secondly, a method is provided that can be performed by a device (e.g., a communication device). This device can be an equipment (such as a network device), or it can be a component of an equipment (e.g., a chip (such as a modem chip, also known as a baseband chip, or a SoC chip or SIP chip containing a modem core) or a chip system or circuit), and this application does not limit this. The following description primarily uses a fourth communication device as an example.

[0014] The fourth communication device may be, for example, a data processing function (DPF).

[0015] The method includes: receiving a first request message from a second communication device, the first request message being used to request the establishment of a data session, the first request message including a first topic, the first topic being the topic of data transmitted in the data session; establishing a data session with a third communication device based on the first request message; receiving a first data packet from the third communication device, parsing the first data packet according to a first protocol stack to obtain first data corresponding to the first topic, the first protocol stack including the MQTT protocol.

[0016] The second communication device may be, for example, a DC; the third communication device may be, for example, a DCP.

[0017] Based on the above scheme, with the MQTT protocol deployed in both the third and fourth communication devices, each node can transmit data via the MQTT protocol, thus constructing a data communication structure that supports on-the-path computing and arbitrary topology.

[0018] In conjunction with the second aspect, in some implementations of the second aspect, the method further includes: processing the first data to obtain the second data; and sending the second data to the third communication device.

[0019] In conjunction with the second aspect, in some implementations of the second aspect, the method further includes: sending a first subscription request to a third communication device, the first subscription request including a first topic, the first subscription request being used to subscribe to first data.

[0020] In conjunction with the second aspect, some implementations of the second aspect include: the first data packet includes DSID and / or DAID.

[0021] Thirdly, a method is provided that can be performed by a device (e.g., a communication device). This device can be an apparatus (such as a terminal device), or it can be a component of an apparatus (e.g., a chip (such as a modem chip, also known as a baseband chip, or a SoC chip or SIP chip containing a modem core) or a chip system or circuit), and this application does not limit this. The following description primarily uses a terminal device as an example.

[0022] The method includes: receiving a first request message from a second communication device, the first request message being used to request the establishment of a data session, the first request message including a first topic, the first topic being the subject of data to be transmitted in the data session; establishing a data session with a third communication device based on the first request message; encapsulating first data corresponding to the first topic according to a second protocol stack to obtain a first data packet, the second protocol stack including the MQTT protocol; and sending the first data packet to the third communication device.

[0023] The second communication device may be, for example, a DC; the third communication device may be, for example, a DCP.

[0024] Based on the above scheme, when both the terminal device and the third communication device are equipped with the MQTT protocol, the terminal device can directly encapsulate data according to the MQTT protocol for data transmission without the need for other nodes to process the data, thereby improving the security of the data transmission process.

[0025] In conjunction with the third aspect, in some implementations of the third aspect, the method further includes: sending a second request message to a first communication device, the second request message being used to request the establishment of a connection between the terminal device and the third communication device; and receiving a second request response message from the first communication device, the second request response message indicating that a connection has been successfully established between the terminal device and the third communication device.

[0026] The first communication device can refer to a base station or an NF (Network Functions).

[0027] Based on the above scheme, the second request message is used to request the establishment of a connection between the terminal device and the third communication device. Specifically, after the terminal device establishes a connection with the MQTT server (i.e., the server of the third communication device), the security and stability of subsequent data transmission can be improved.

[0028] In conjunction with the third aspect, in some implementations of the third aspect, the method further includes: receiving a session establishment request from a first communication device, the session establishment request being used to request the establishment of a data bearer; sending a session establishment request response to the first communication device, the session establishment request response indicating that the data bearer has been successfully established, wherein the data bearer is used for data transmission between the terminal device and the first communication device.

[0029] Based on the above scheme, the data bearer established between the terminal device and the first communication device can achieve stable data transmission.

[0030] In conjunction with the third aspect, some implementations of the third aspect include: sending a first data packet to a first communication device, and the first data packet being forwarded by the first communication device to a third communication device. In other words, the terminal device sends a first data packet to the first communication device, and the first communication device sends a first data packet to the third communication device.

[0031] Based on the above scheme, when the terminal device supports the MQTT protocol, a data bearer is established between the terminal device and the first communication device. The first communication device forwards the first data packet to the third communication device through transparent transmission. This method can achieve stable data transmission.

[0032] In conjunction with the third aspect, some implementations of the third aspect include: the first data packet includes DSID and / or DAID.

[0033] Fourthly, a method is provided that can be performed by an apparatus (e.g., a communication apparatus). The apparatus can be a device (such as a network device), or it can be a component of a device (e.g., a chip (such as a modem chip, also known as a baseband chip, or a SoC chip or SIP chip containing a modem core) or a chip system or circuit), and this application does not limit this. The following description primarily uses a third communication apparatus as an example.

[0034] The method includes: receiving a first establishment request from a first communication device in response to a first request message, the first establishment request being used to request the establishment of a data session between the first communication device and a third communication device; the first request message originating from a second communication device, the first request message including a first subject, the first subject being the subject of data transmitted in the data session; sending a first establishment request response to the first communication device, the first establishment request response indicating successful establishment of the data session; receiving a second request message from the first communication device, the second request message being used to request the establishment of a connection between a terminal device and the third communication device (or, in other words, the second request message being used to request the establishment of a connection between the terminal device and the server of the third communication device); sending a second request response message to the first communication device, the second request response message indicating successful establishment of a connection between the terminal device and the third communication device; receiving a first data packet from the first communication device, parsing the first data packet according to a second protocol stack to obtain first data, the second protocol stack including the MQTT protocol.

[0035] The first communication device may be a base station or an NF; the second communication device may be a DC; and the third communication device may be a DCP.

[0036] Based on the above scheme, when both the terminal device and the third communication device are equipped with the MQTT protocol, the terminal device can directly encapsulate data according to the MQTT protocol for data transmission without the need for the first communication device to process the data. This improves the security of the data transmission process.

[0037] In conjunction with the fourth aspect, some implementations of the fourth aspect include: the first data packet includes DSID and / or DAID.

[0038] Fifthly, a method is provided that can be performed by an apparatus (e.g., a communication apparatus). The apparatus may be a device (such as a network device), or it may be a component of a device (e.g., a chip (such as a modem chip, also known as a baseband chip, or a SoC chip or SIP chip containing a modem core) or a chip system or circuit), and this application does not limit this. The following description primarily uses a fifth communication apparatus as an example.

[0039] The fifth communication device may refer to the target base station, specifically, in a terminal device handover scenario, from one base station (which may be called the source base station) to the target base station.

[0040] The method includes: receiving a first handover request from a first communication device in response to a first request message, the first handover request instructing a fifth communication device to provide communication services to a terminal device; the first request message comes from a second communication device, the first request message is used to request the establishment of a data session, the first request message includes a first topic, the first topic being the subject of the data transmitted in the data session; establishing a data session with a third communication device based on the first handover request; encapsulating first data corresponding to the first topic according to the MQTT protocol and obtaining a first data packet; and sending the first data packet to the third communication device.

[0041] The first communication device may be a base station or an NF; the second communication device may be a DC; and the third communication device may be a DCP.

[0042] Based on the above scheme, in the scenario of base station handover, the target base station establishes a data session with the third communication device based on the handover request to assist the terminal device and each node in transmitting data via the MQTT protocol. In this way, it can be ensured that each node can achieve efficient communication with less overhead during base station handover, thereby improving the efficiency of data transmission.

[0043] In conjunction with the fifth aspect, in some implementations of the fifth aspect, the method further includes: receiving first data from the terminal device.

[0044] In conjunction with the fifth aspect, in some implementations of the fifth aspect, the method further includes: sending second data to a terminal device, wherein the second data is obtained by processing the first data.

[0045] In conjunction with the fifth aspect, some implementations of the fifth aspect include: the first data packet includes DSID and / or DAID.

[0046] A sixth aspect provides a communication apparatus for performing the method provided in any one of the first to fifth aspects. Specifically, the apparatus may include units and / or modules for performing the method provided in any of the above-described implementations of the first to fifth aspects, such as processing units and / or communication units.

[0047] In one implementation, the device is a communication device (such as a terminal device or a network device). When the device is a communication device, the communication unit can be a transceiver or an input / output interface; the processing unit can be at least one processor. Optionally, the transceiver can be a transceiver circuit. Optionally, the input / output interface can be an input / output circuit.

[0048] In another implementation, the device is a chip, chip system, or circuit used in a communication device. When the device is a chip, chip system, or circuit used in a communication device, the communication unit can be an input / output interface, interface circuit, output circuit, input circuit, pin, or related circuit on the chip, chip system, or circuit; the processing unit can be at least one processor, processing circuit, or logic circuit.

[0049] A seventh aspect provides a communication apparatus comprising: a memory for storing a program; and at least one processor for executing the computer program or instructions stored in the memory to perform the method provided by any of the above-described implementations of any of the first to fifth aspects.

[0050] In one implementation, the device is a communication device (such as a terminal device or a network device).

[0051] In another implementation, the device is a chip, chip system, or circuit used in a communication device.

[0052] Eighthly, this application provides a processor for performing the methods provided in the foregoing aspects.

[0053] Unless otherwise specified, or if it does not contradict its actual function or internal logic in the relevant description, the transmission and acquisition / reception operations involved in the processor can be understood as processor output and input operations, or as transmission and reception operations performed by radio frequency circuits and antennas. This application does not limit them in this regard.

[0054] Ninth aspect, a computer-readable storage medium is provided for program code executed by a device, the program code including a method for performing any of the above-described implementations of any of the first to fifth aspects.

[0055] In a tenth aspect, a computer program product comprising instructions is provided, which, when executed by a processor on a computer, causes the computer to perform a method provided by any of the above-described implementations of any of the first to fifth aspects.

[0056] Eleventhly, a chip is provided, the chip including a processor and a communication interface, the processor reading instructions stored in a memory through the communication interface and executing the method provided by any of the above implementations of any of the first to fifth aspects.

[0057] Optionally, as one implementation, the chip further includes a memory storing computer programs or instructions. The processor is used to execute the computer programs or instructions stored in the memory. When the computer programs or instructions are executed, the processor is used to execute the method provided by any of the above implementations of any of the first to fifth aspects.

[0058] In a twelfth aspect, a communication system is provided, comprising a first communication device, a second communication device, a third communication device, a fourth communication device, and a fifth communication device. Each communication device is configured to execute the method provided in any one of the implementations of the first to fifth aspects described above.

[0059] The beneficial effects of aspects six through twelfth and their possible implementations can be found in the descriptions of aspects one through five above, and will not be repeated here. Attached Figure Description

[0060] Figure 1 A schematic diagram of a network architecture is shown.

[0061] Figure 2 A schematic diagram of a protocol stack is shown.

[0062] Figure 3 A schematic diagram of another protocol stack is shown.

[0063] Figure 4This shows a schematic diagram of yet another protocol stack.

[0064] Figure 5 This is a schematic diagram of protocol stack #1 provided in an embodiment of this application.

[0065] Figure 6 This is a schematic diagram of method 600 provided in an embodiment of this application.

[0066] Figure 7 This is a schematic diagram of protocol stack #2 provided in an embodiment of this application.

[0067] Figure 8 This is a schematic diagram of method 800 provided in an embodiment of this application.

[0068] Figure 9 This is a schematic diagram of protocol stack #3 provided in an embodiment of this application.

[0069] Figure 10 This is a schematic diagram of the method 1000 provided in the embodiments of this application.

[0070] Figure 11 This is a schematic diagram of method 1100 provided in an embodiment of this application.

[0071] Figure 12 This is a schematic block diagram of a communication device 1200 provided in an embodiment of this application.

[0072] Figure 13 This is a schematic diagram of another communication device 1300 provided in an embodiment of this application.

[0073] Figure 14 This is a schematic block diagram of the chip system 1400 provided in the embodiments of this application. Detailed Implementation

[0074] Before introducing the scheme of this application, the following points should be noted.

[0075] (1) In this application, “instruction” may include direct instruction, indirect instruction, explicit instruction, and implicit instruction. When describing a certain instruction information for the purpose of instructing A, it can be understood that the instruction information carries A, directly instructs A, or indirectly instructs A.

[0076] In this application, the information indicated by the instruction information is called the information to be instructed. In specific implementations, there are many ways to indicate the information to be instructed, such as, but not limited to, directly indicating the information to be instructed, such as the information to be instructed itself or its index. It can also indirectly indicate the information to be instructed by indicating other information, where there is a relationship between the other information and the information to be instructed. It can also indicate only a part of the information to be instructed, while the other parts are known or pre-agreed upon. For example, the instruction of specific information can be achieved by using a pre-agreed (e.g., protocol-defined) arrangement of various pieces of information, thereby reducing instruction overhead to some extent. Furthermore, the information to be instructed can be sent as a whole or divided into multiple sub-information pieces, and the sending period and / or timing of these sub-information pieces can be the same or different.

[0077] (2) In this application, "send" and "receive" indicate the direction of signal transmission. For example, "send information to XX" can be understood as the destination of the information being XX, which may include direct transmission via the air interface or indirect transmission via the air interface by other units or modules. "Receive information from YY" can be understood as the source of the information being YY, which may include direct reception from YY via the air interface or indirect reception from YY via the air interface by other units or modules. "Send" can also be understood as the "output" of the chip interface, and "receive" can also be understood as the "input" of the chip interface. In other words, sending and receiving can occur between devices, such as between network devices and terminal devices, or within a device, such as between components, modules, chips, software modules, or hardware modules within the device via a bus, wiring, or interface.

[0078] (3) In the various embodiments of this application, unless otherwise specified or logically conflicting, the terms and / or descriptions of different embodiments are consistent and can be referenced by each other. The technical features of different embodiments can be combined to form new embodiments according to their inherent logical relationship.

[0079] (4) In this application, "first," "second," and "#1," "#2," etc., are merely for descriptive convenience and are used to distinguish objects, and are not intended to limit the scope of the embodiments of this application. They are not used to describe the order or sequence of features. It should be understood that such described objects can be interchanged where appropriate so as to describe solutions other than those in the embodiments of this application.

[0080] (5) In this application, “predefined” may mean a standard protocol predefined, or it may mean that the devices have agreed or negotiated in advance.

[0081] (6) In this application, the words “exemplary,” “for example,” etc., are used to indicate examples, illustrations, or descriptions. Any embodiment or design described as an “example” in this application should not be construed as being more preferred or advantageous than other embodiments or designs. Specifically, the use of the word “example” is intended to present the concept in a concrete manner. In the embodiments of this application, “of,” “corresponding, relevant,” and “corresponding” may sometimes be used interchangeably, and it should be noted that their intended meanings are consistent unless their distinction is emphasized.

[0082] (7) In this document, "at least one" means one or more. "More than one" means two or more. "And / or" describes the relationship between related objects, indicating that there can be three relationships. For example, A and / or B can mean: A exists alone, A and B exist simultaneously, or B exists alone, where A and B can be singular or plural. In the textual description of this application, the character " / " generally indicates that the related objects before and after are in an "or" relationship; in the formula of this application, the character " / " indicates that the related objects before and after are in a "division" relationship. "Including at least one of A, B and C" can mean: including A; including B; including C; including A and B; including A and C; including B and C; including A, B and C.

[0083] (8) The arrows or boxes indicated by dashed lines in the schematic diagrams in the accompanying drawings of this application indicate optional steps or optional modules.

[0084] The technical solutions in this application will now be described with reference to the accompanying drawings.

[0085] The technical solutions provided in this application can be applied to various communication systems, such as: future mobile communication systems, 5th generation (5G) or new radio (NR) systems, long term evolution (LTE) systems, LTE frequency division duplex (FDD) systems, LTE time division duplex (TDD) systems, wireless local area network (WLAN) systems, satellite communication systems, future communication systems, or integrated systems of multiple systems. The technical solutions provided in this application can also be applied to device-to-device (D2D) communication, vehicle-to-everything (V2X) communication, machine-to-machine (M2M) communication, machine-type communication (MTC), and Internet of Things (IoT) communication systems or other communication systems.

[0086] In a communication system, a device can send signals to or receive signals from another device. These signals can include information, signaling, or data. The term "device" can also be replaced by an entity, network entity, communication device, mobile device, network element, communication module, node, communication node, communication apparatus, etc. This disclosure uses "device" as an example. For instance, a communication system can include at least one terminal device and at least one network device. The network device can send downlink signals to the terminal device, and / or the terminal device can send uplink signals to the network device.

[0087] In the embodiments of this application, the terminal device may also be referred to as user equipment (UE), access terminal, user unit, user station, mobile station, mobile station, remote station, remote terminal, mobile device, user terminal, terminal, wireless communication device, user agent, or user apparatus.

[0088] Terminal devices can be devices that provide voice / data, such as handheld devices with wireless connectivity, in-vehicle devices, etc. Currently, examples of terminals include: mobile phones, tablets, laptops, PDAs, mobile internet devices (MIDs), wearable devices, virtual reality (VR) devices, augmented reality (AR) devices, wireless terminals in industrial control, wireless terminals in self-driving, wireless terminals in remote medical surgery, wireless terminals in smart grids, wireless terminals in transportation safety, wireless terminals in smart cities, wireless terminals in smart homes, cellular phones, cordless phones, session initiation protocol (SIP) phones, wireless local loop (WLL) stations, personal digital assistants (PDAs), handheld devices with wireless communication capabilities, computing devices or other processing devices connected to a wireless modem, wearable devices, terminal devices in 5G networks, or future public land mobile communication networks. Terminal devices in a network (PLMN), etc., are not limited to this in the embodiments of this application.

[0089] By way of example and not limitation, in this embodiment, the terminal device can also be a wearable device. Wearable devices, also known as wearable smart devices, are a general term for devices that utilize wearable technology to intelligently design and develop everyday wearables, such as glasses, gloves, watches, clothing, and shoes. Wearable devices are portable devices that are worn directly on the body or integrated into the user's clothing or accessories. Wearable devices are not merely hardware devices, but also achieve powerful functions through software support, data interaction, and cloud interaction. Broadly speaking, wearable smart devices include those that are feature-rich, large in size, and can achieve complete or partial functions without relying on a smartphone, such as smartwatches or smart glasses, as well as those that focus on a specific type of application function and require the use of other devices such as smartphones, such as various smart bracelets and smart jewelry for vital sign monitoring.

[0090] In this embodiment, the device for implementing the functions of the terminal device can be the terminal device itself, or it can be any device capable of supporting the terminal device in implementing those functions, such as a chip system. This device can be installed in or used in conjunction with the terminal device. In this embodiment, the chip system can be composed of chips or may include chips and other discrete components. This embodiment only uses the terminal device as an example to illustrate the device for implementing the functions of the terminal device, and does not constitute a limitation on the solution of this embodiment.

[0091] The network device in this application embodiment may include a device for communicating with a terminal device. For example, the network device may include an access network device or a wireless access network device, such as a base station (BS). The wireless access network device in this application embodiment may refer to a radio access network (RAN) node (or device) that connects the terminal device to the wireless network. A base station can broadly encompass, or be replaced by, various names including: NodeB, evolved NodeB (eNB), next-generation NodeB (gNB), relay station, access point, transmitting and receiving point (TRP), transmitting point (TP), master station, auxiliary station, motor slide retainer (MSR) node, home base station, network controller, access node, wireless node, access point (AP), transmission node, transceiver node, baseband unit (BBU), remote radio unit (RRU), active antenna unit (AAU), remote radio head (RRH), central unit (CU), distributed unit (DU), radio unit (RU), positioning node, etc. A base station can be a macro base station, micro base station, relay node, donor node, or similar entities, or combinations thereof. A base station can also refer to a communication module, modem, or chip installed within the aforementioned equipment or apparatus. A base station can also be a mobile switching center, a device that performs base station functions in D2D, V2X, and M2M communications, or a device that performs base station functions in future communication systems. A base station can support networks using the same or different access technologies. Optionally, a RAN node can also be a server, wearable device, vehicle, or in-vehicle equipment. For example, the access network equipment in vehicle-to-everything (V2X) technology can be a roadside unit (RSU). The embodiments of this application do not limit the specific technologies or equipment forms used in the network equipment.

[0092] Base stations can be fixed or mobile. For example, a helicopter or drone can be configured to act as a mobile base station, and one or more cells can move depending on the location of the mobile base station. In other examples, a helicopter or drone can be configured as a device to communicate with another base station.

[0093] In some deployments, the network devices mentioned in the embodiments of this application may be devices including CU, DU, or CU and DU, or devices with control plane CU nodes (central unit-control plane (CU-CP)) and user plane CU nodes (central unit-user plane (CU-UP)) and DU nodes. For example, the network devices may include gNB-CU-CP, gNB-CU-UP, and gNB-DU.

[0094] In some deployments, multiple RAN nodes collaborate to assist terminals in achieving wireless access, with different RAN nodes each implementing some of the base station's functions. For example, RAN nodes can be CUs, DUs, CU-CPs, CU-UPs, or RUs. CUs and DUs can be configured separately or included in the same network element, such as a BBU. RUs can be included in radio frequency equipment or radio frequency units, such as RRUs, AAUs, or RRHs.

[0095] RAN nodes can support one or more types of fronthaul interfaces, each corresponding to a DU and RU with different functions. If the fronthaul interface between the DU and RU is a common public radio interface (CPRI), the DU is configured to implement one or more baseband functions, and the RU is configured to implement one or more radio frequency functions. If the fronthaul interface between the DU and RU is another type of interface, relative to CPRI, some downlink and / or uplink baseband functions, such as, for downlink, precoding, digital beamforming (BF), or one or more of inverse fast Fourier transform (IFFT) / cyclic prefix addition (CP), are moved from the DU to the RU; and for uplink, one or more of digital beamforming (BF), or fast Fourier transform (FFT) / cyclic prefix removal (CP), are moved from the DU to the RU. In one possible implementation, the interface can be an enhanced common public radio interface (eCPRI). Under the eCPRI architecture, the segmentation between DU and RU differs, corresponding to different categories (Cat) of eCPRI, such as eCPRI Cat A, B, C, D, E, F.

[0096] Taking eCPRI Cat A as an example, for downlink transmission, layer mapping is used as the dividing line. DU is configured to implement one or more functions preceding layer mapping (i.e., coding, rate matching, scrambling, modulation, and layer mapping), while other functions following layer mapping (e.g., RE mapping, digital beamforming (BF), or one or more inverse fast Fourier transform (IFFT) / cyclic prefix (CP) addition) are moved to RU. For uplink transmission, deRE mapping is used as the dividing line. DU is configured to implement one or more functions preceding deRE mapping (i.e., decoding, rate matching de-matching, descrambling, demodulation, inverse discrete Fourier transform (IDFT), channel equalization, and deRE mapping), while other functions following deRE mapping (e.g., digital BF or fast Fourier transform (FFT) / CP removal) are moved to RU. It is understandable that the functional descriptions of the DU and RU corresponding to various types of eCPRI can be found in the eCPRI protocol, and will not be elaborated here.

[0097] In one possible design, the processing unit in the BBU used to implement baseband functions is called the baseband high (BBH) unit, and the processing unit in the RRU / AAU / RRH used to implement baseband functions is called the baseband low (BBL) unit.

[0098] In different systems, CU (or CU-CP and CU-UP), DU, or RU may have different names, but those skilled in the art will understand their meaning. For example, in an open RAN (ORAN) system, CU can also be called O-CU (open CU), DU can also be called O-DU, CU-CP can also be called O-CU-CP, CU-UP can also be called O-CU-UP, and RU can also be called O-RU. Any of the units among CU (or CU-CP, CU-UP), DU, and RU in this application can be implemented through software modules, hardware modules, or a combination of software modules and hardware modules.

[0099] In this embodiment, the apparatus for implementing the functions of a network device can be a network device itself; it can also be an apparatus capable of supporting the network device in implementing those functions, such as a chip system, hardware circuit, software module, or a hardware circuit plus a software module. This apparatus can be installed in the network device or used in conjunction with the network device. In this embodiment, the example of a network device being used to implement the functions of a network device is provided only and does not constitute a limitation on the solutions described in this embodiment.

[0100] Network devices and / or terminal devices can be deployed on land, including indoors or outdoors, handheld or vehicle-mounted; they can also be deployed on water; and they can also be deployed in the air on airplanes, balloons, and satellites. This application does not limit the scenario in which the network devices and terminal devices are located. Furthermore, terminal devices and network devices can be hardware devices, or software functions running on dedicated hardware or general-purpose hardware, such as virtualization functions instantiated on a platform (e.g., a cloud platform), or entities that include dedicated or general-purpose hardware devices and software functions. This application does not limit the specific form of the terminal devices and network devices.

[0101] The following section introduces the relevant technical background and concepts involved in the embodiments of this application.

[0102] I. Data Services

[0103] With the decrease in computing and storage costs, and the emergence of numerous low-latency services and local area applications, computing and storage, as well as the intelligent algorithms that rely on them, tend to be deployed at the network edge closer to the data source, thus forming a data-centric network architecture. The basic function of mobile communication networks will also begin to shift from being a conduit for information transmission to a platform for data management. Through analysis of numerous data application scenarios and needs, the data services that the data architecture can provide can be summarized into eight categories, as shown in Table 1:

[0104] Table 1: Descriptions of Various Data Services

[0105]

[0106]

[0107] II. Data Surface

[0108] With technological advancements and increasingly sophisticated user needs, the amount of data in future communication networks will increase dramatically. This places higher demands on the data processing capabilities of network architectures. For example, future network architectures need to support "in-the-path computing" and "arbitrary topology".

[0109] Figure 1 A schematic diagram of a network architecture is shown, and the functions of each component are described below.

[0110] 1) Data Orchestrator (DO): Provides data service orchestration (coarse-grained, non-real-time), lifecycle management of data service tasks, and translation of service requests. It acts as the portal for receiving data service requests, converting them into corresponding data pipeline construction requests before sending them to the Data Control (DC). The DO is also responsible for integrating with other network security and privacy protection technology libraries, including differential privacy, homomorphic encryption, and zero-knowledge proofs, to provide data security and privacy protection capabilities and, as needed, empower data protection technologies to the Data Agent (DA).

[0111] 2) Data Agent (DA): It can be built into network functions or deployed independently to perform functions such as data acquisition, data preprocessing, data storage, data analysis, and data forwarding.

[0112] 3) Data Controller (DC): Responsible for fine-grained real-time orchestration tasks, combining data pipelines within the local domain based on the capabilities of the Data Controller (DA) and data service requests. The collaboration between the Data Controller (DO) and the DC enables the elasticity and programmability of the data pipeline. Furthermore, the DC receives capability reports from the DAs and implements registration and deregistration functions for DAs, achieving real-time monitoring of DAs by detecting their heartbeats.

[0113] 4) Data Communication Proxy (DCP): Provides an efficient data transmission mechanism, decoupling data producers and data consumers.

[0114] DCP introduces a new network function in the 3rd Generation Partnership Project (3GPP) network. It should be understood that DCP is merely an example name; other names can be used instead. Any device with the same function as a DCP can be considered a DCP, and this application does not limit this. DCP can be deployed as an independent network element in a 3GPP network, or it can be co-located with other network elements or devices in the 3GPP network; this application does not limit this. Optionally, DCP can be deployed in the access network or the core network; this application does not limit this.

[0115] DCP supports multiple transport protocols, such as Transmission Control Protocol (TCP), User Datagram Protocol (UDP), Quick UDP Internet Connection (QUIC), or others. DCP can include an adapter layer and a distributed message queue (DMQ) for efficient data distribution. DCP supports the concept of data consumer groups, meaning that the same message can only be consumed by one data consumer belonging to the same group, but can be consumed simultaneously by different data consumer groups.

[0116] 5) Data Processing Function (DPF): This is a special type of Data Analyzer that performs data analysis and processing functions.

[0117] 6) Distributed Data Storage Function (DSF): This refers to a technology that manages data storage through a distributed architecture. It enables data to be stored in multiple physical locations (such as multiple nodes, servers, data centers, etc.), and the system can ensure the consistency, reliability, and high availability of data across these distributed locations.

[0118] III. Protocol Stack

[0119] Figure 2 This diagram illustrates a protocol stack. When data collected by the terminal device needs to be processed at the base station, the protocol stack used between the terminal device and the base station is as follows: Figure 2 As shown, the protocol stack from bottom to top consists of the Physical Layer (PHY), Medium Access Control (MAC), Radio Link Control (RLC), Packet Data Convergence Protocol (PDCP), and Data Forward Protocol-service (DFP-S). Among them, the main functions of DFP-S include data acquisition, data processing and analysis, data encryption, and privacy protection.

[0120] Figure 3 This diagram illustrates another protocol stack. When the base station currently hosting the terminal device transparently transmits the terminal device's data, the corresponding protocol stack is as follows: Figure 3As shown, it should be understood that the data processed by the terminal device can be handled by a DPF or other base stations, without limitation. Among them, the Data Spine Adaptor (DSA) is a new protocol layer introduced based on the introduction of DCP. The main function of the DSA layer is message queue adaptation (such as creating data consumers, creating data producers, data publishing, data subscription, data unsubscribing, data consumption, etc.).

[0121] Figure 4 This diagram illustrates yet another protocol stack, which can be used when a terminal device publishes data, such as... Figure 4 As shown. The GPRS Tunneling Protocol-User Plane (GTPU) is the protocol used by terminal devices to transmit data in mobile networks. GTPU sits on top of UDP, and terminal devices use IPv4 / IPv6 / PPP to send data. GTPU data is carried over IP. When the UE sends a message to the core side, it sends the message through the General Packet Radio Service (GPRS) Tunneling Protocol (GTP). The network element deletes the tunnel message, parses it, returns it to the terminal device, and then re-encapsulates the tunnel before sending it back to the terminal device.

[0122] IV. Message Queuing Telemetry Transport (MQTT) Protocol

[0123] MQTT is a lightweight messaging protocol based on the publish / subscribe paradigm. MQTT includes three roles: publisher, broker, and subscriber. Both publishers and subscribers are clients; a message publisher can also be a subscriber.

[0124] The MQTT protocol communicates by exchanging predefined MQTT control messages, which can be simply referred to as MQTT messages. An MQTT message consists of three parts: a fixed header, a variable header, and a payload / message body, which are briefly described below.

[0125] 1) Fixed header: All MQTT messages have this header, which indicates the message type and the message grouping identifier.

[0126] 2) Variable header: Some MQTT messages have a variable header. The message type determines whether a variable header exists and its specific content.

[0127] 3) Payload: Some MQTT messages have this feature, which stores the specific content of the message.

[0128] Table 2 provides the MQTT protocol definition.

[0129] Table 2: MQTT Protocol Definition

[0130]

[0131] Table 3 provides examples of messages in the MQTT protocol.

[0132] Table 3: Messages in the MQTT Protocol

[0133] name value Message flow direction describe Reserved 0 prohibit Reserved bits CONNECT 1 Client to server The client requests a connection to the server. CONNACK 2 server to client Connection confirmed PUBLISH 3 Two-way Announcement PUBACK 4 Two-way Release confirmed PUBREC 5 Two-way Release received (Part 1 guaranteed to have arrived) PUBREL 6 Two-way Released (guaranteeing Part 2's arrival) PUBCOMP 7 Two-way Release complete (Part 3 guaranteed to arrive) SUBCRIBE 8 Client to server Customer requests subscription SUBACK 9 server to client Subscription Confirmation UNSUBCRIBE 10 Client to server Request to unsubscribe UNSUBACK 11 server to client Cancel subscription confirmation PINGREQ 12 Client to server Heartbeat request PINGRESP 13 server to client Heartbeat response DISCONNECT 14 Client to server Interrupted connection RESERVED 15 prohibit Reserved bits

[0134] The message types include subscription, publication, and consumption.

[0135] As mentioned above, with the development of network scale, new technologies, and applications, there will be more demands for data transmission and processing. For example, future data transmission needs to realize functions such as in-path computing and arbitrary topology. However, the current data transmission methods have some problems. For example, the data transmission method based on the DSA protocol is relatively complex to implement and has high requirements for data transmission nodes.

[0136] In view of this, this application provides a method that can improve the flexibility and scalability of a communication system, while also meeting the requirements of in-path computing and arbitrary topology for future data transmission.

[0137] The embodiments of this application repeatedly mention NF, DCP, DPF, DC, and access and mobility management function (AMF) network elements, which are uniformly described here. It should be understood that NF / DCP / DPF / DC / AMF are merely examples, and their names do not limit the scope of protection of this application. This application does not exclude the possibility of using other names to replace the above nodes in future protocols to achieve their same or similar functions.

[0138] Figure 5 This is a schematic diagram of protocol stack #1 (i.e., the first protocol stack) provided in the embodiments of this application. It should be understood that protocol stack #1 can be applied to any node in the data flow process (such as...). Figure 5 (RAN / NF, DCP, DPF in the data).

[0139] exist Figure 5 In the protocol stack #1 shown, the MQTT protocol is deployed in the RAN / NF node, DCP node, and DPF node.

[0140] Figure 6 This is a schematic diagram of method 600 provided in an embodiment of this application. Method 600 describes the process of data transmission using protocol stack #1. It should be understood that the numbering of each step in method 600 is for ease of description, and the numbering of each step does not limit the execution order of the steps.

[0141] S601, DC determines the base station and DPF based on data service requests.

[0142] The data service request includes data requirement information, and is used to request the provision of corresponding data services.

[0143] Specifically, the DC selects a suitable base station to process the data service requested by one or more base stations based on the data service capability information of the base stations and the data service request; the DC also selects a suitable DPF to process the data service requested by one or more DPFs based on the data service capability information of the DPFs and the data service request. The data service capability information indicates the processing capability of the base station or DPF for the data service.

[0144] This application does not limit the specific implementation of the DC obtaining data service requests. For example, the DC receives data service requests from other nodes.

[0145] This application does not limit the specific method by which the DC obtains data service capability information from one or more base stations (or one or more DPFs). For example, one or more base stations (or one or more DPFs) send data service capability information to the DC.

[0146] S602, DC sends first request message #1, and correspondingly, base station receives first request message #1.

[0147] The first request message #1 is used to request the establishment of a data session, that is, to request the establishment of a data transmission channel between the base station and the DCP for data transmission. It should be understood that method 600 is for establishing a data transmission channel between the base station and the DPF; in other words, the base station requests the establishment of a data transmission channel with the DCP based on the first request message #1 so that communication can occur between the base station and the DPF. Therefore, it can be understood that the first request message #1 is used to request the establishment of a data transmission channel between the base station and the DPF for data transmission.

[0148] The first request message #1 includes one or more of the following: first topic, data service identifier (DSID), session ID, data type to be collected, time, and frequency.

[0149] The first topic is determined by the DC based on the data service request and is used to identify the topic of the data transmitted in the data session. For example, the first topic is the topic of the data that the base station needs to publish; the DSID is used to identify the data service task; the time indicates the duration of the data session; and the frequency indicates the rate of data interaction or data transmission.

[0150] S603, DC sends first request message #2, and DPF receives first request message #2 accordingly.

[0151] The first request message #2 is used to request the establishment of a data session, that is, to request the establishment of a data transmission channel between the DPF and the DCP for data transmission. It should be understood that the first request message #2 can also be understood as a request to establish a data transmission channel between the DPF and the base station for data transmission.

[0152] The first request message #2 includes one or more of the following: first topic, DSID, and data processing method. The data processing method includes preprocessing methods such as data cleaning, filtering, aggregation, and fusion, or data analysis methods based on AI, ML, and big data, and is not limited thereto.

[0153] S604, the base station sends a first establishment request based on the first request message #1, and correspondingly, the DCP receives the first establishment request.

[0154] Specifically, after receiving the first request message #1, the base station will select a suitable DCP to establish a data session. This application does not limit the specific method by which the base station selects the DCP. For example, the base station can select the DCP according to pre-configured rules.

[0155] S605, DCP sends a first establishment request response, and correspondingly, the base station receives the first establishment request response.

[0156] The first connection request response indicates that the base station and DCP have successfully established a connection.

[0157] As one possible implementation, the first connection request is a CONNECT message. Specifically, the base station sends a CONNECT message to the DCP according to the MQTT protocol. The response to the first connection request is a CONNECTACK message. After receiving the CONNECTACK message, the base station determines that a connection has been established with the DCP.

[0158] S606, the DPF sends a second establishment request based on the first request message #2, and the DCP receives the second establishment request accordingly.

[0159] Specifically, after receiving the first request message #2, the DPF will select a suitable DCP to establish a data session. This application does not limit the specific method by which the DPF selects the DCP. For example, the DPF may select the DCP through pre-configured rules.

[0160] S607, DCP sends a second establishment request response, and DPF receives the second establishment request response accordingly.

[0161] The second connection request response indicates that the base station and DCP have successfully established a connection.

[0162] As one possible implementation, the second connection request is a CONNECT message. Specifically, if the DPF sends a CONNECT message to the DCP according to the MQTT protocol, the response to the second connection request is a CONNECTACK message. After receiving the CONNECTACK message, the DPF determines that a connection has been established with the DCP.

[0163] Specifically, the data session between DPF and DCP is established. Since the data session between the base station and DCP is established in S604-S605, the data transmission channel between the base station and DPF is also established, and the base station and DPF can communicate with each other.

[0164] S608, DPF sends the first subscription request, and DCP receives the first subscription request accordingly.

[0165] The first subscription request includes a first topic, and the first subscription request is used to subscribe to the data corresponding to the first topic.

[0166] Optionally, the first subscription request may also include a session ID.

[0167] S609, DCP sends a first subscription request response, and DPF receives the first subscription request response accordingly.

[0168] The first subscription request response indicates that the DPF has successfully subscribed to the data corresponding to the first topic from the DCP.

[0169] As one possible implementation, the first subscription request is a SUBSCRIBE message. Specifically, the DPF sends a SUBSCRIBE message to the DCP according to the MQTT protocol, and the first subscription request response is a SUBACK message. After receiving the SUBACK message, the DPF determines that the subscription was successful.

[0170] S610, the base station obtains the data corresponding to the first topic (for example, denoted as data #1, an example of the first data), encapsulates data #1 according to protocol stack #1, and obtains data packet #1.

[0171] This application does not limit the specific implementation method of the base station acquiring data #1. For example, the base station may perform the data acquisition process itself to acquire data #1; or, for another example, the base station may acquire data #1 from other nodes.

[0172] S611, the base station sends data packet #1, and correspondingly, the DCP receives data packet #1.

[0173] As one possible implementation, the base station sends a PUBLISH message to the DCP according to the MQTT protocol, and sends data packet #1 to the DCP through the PUBLISH message.

[0174] As one possible implementation, the variable header of a PUBLISH message also includes a DSID and a data agent identifier (DAID). The DAID identifies the base station, allowing the recipient of the PUBLISH message to determine its origin, thus improving data transmission reliability.

[0175] S612, DCP sends data packet #1, and correspondingly, DPF receives data packet #1.

[0176] As one possible implementation, DCP sends a PUBLISH message to DPF according to the MQTT protocol, and sends data packet #1 to DPF through the PUBLISH message.

[0177] S613, DPF parses data packet #1 according to protocol stack #1, obtains data #1, and performs data processing.

[0178] Specifically, the DPF processes data #1 based on the data processing method indicated by the first request message #2.

[0179] In the above, method 600 uses protocol stack #1 for data transmission. Specifically, the MQTT protocol is deployed in the base station, DCP, and DPF, enabling each node to publish and subscribe to data through the MQTT protocol, thereby constructing an asynchronous data communication structure that supports multi-point to multi-point communication.

[0180] Figure 7 This is a schematic diagram of protocol stack #2 (i.e., the second protocol stack) provided in the embodiments of this application. It should be understood that protocol stack #2 can be applied to any node in the data flow process (such as...). Figure 7 (UE, RAN, DCP, DPF).

[0181] exist Figure 7 In the protocol stack #2 shown, the MQTT protocol is deployed in the UE node, DCP node, and DPF node.

[0182] Figure 8 This is a schematic diagram of method 800 provided in an embodiment of this application. Method 800 describes the process of data transmission using protocol stack #2. It should be understood that the numbering of each step in method 800 is for ease of description, and the numbering of each step does not limit the execution order of the steps.

[0183] S801, UE transmits capability information, and correspondingly, DC receives capability information.

[0184] Among them, the capability information indicates that the UE supports the MQTT protocol.

[0185] S802, DC determines the UE based on capability information and data service requests.

[0186] For information on data service requests, please refer to section S601; it will not be repeated here.

[0187] Specifically, the DC selects the appropriate UE to process the data service requested by the data service request based on the capability information and data service request of one or more UEs. In other words, if the data service requested by the data service request requires the UE to support the MQTT protocol, the DC determines the data service to be processed by the UE that supports the MQTT protocol based on the capability information and data service request of one or more UEs.

[0188] S803, DC sends first request message #1, and correspondingly, UE receives first request message #1.

[0189] The first request message #1 is used to request the establishment of a data session, that is, to request the establishment of a data transmission channel between the UE and the base station to transmit data. It should be understood that method 800 is for establishing a data transmission channel between the UE and the DCP; in other words, the UE establishes a data transmission channel with the base station based on the first request message #1 so that the UE and the DCP can communicate. Therefore, it can be understood that the first request message #1 is used to request the establishment of a data transmission channel between the UE and the DCP to transmit data.

[0190] The first request message #1 includes one or more of the following: first topic, DSID, session ID, data type to be collected, time, and frequency.

[0191] This application does not limit the specific method of sending the first request message #1. As one possible implementation, the first request message #1 is forwarded through an intermediate node. Specifically, the DC sends the first request message #1, the intermediate node receives the first request message #1, the intermediate node sends the first request message #1, and the UE receives the first request message #1. The intermediate node is, for example, an AMF network element, and is not limited thereto.

[0192] S804, DC sends first request message #2, and correspondingly, base station receives first request message #2.

[0193] The first request message #2 is used to request a data session, that is, to request the establishment of a data transmission channel between the base station and the DCP for data transmission. It should be understood that the first request message #2 can also be interpreted as a request to establish a data transmission channel between the UE and the DCP for data transmission.

[0194] The first request message #2 includes one or more of the following: first topic, DSID, session ID, data type to be collected, time, and frequency.

[0195] This application does not limit the specific method of sending the first request message #2. As one possible implementation, the first request message #2 is forwarded through an intermediate node. Specifically, the DC sends the first request message #2, the intermediate node receives the first request message #2, the intermediate node sends the first request message #2, and the base station receives the first request message #2. The intermediate node can be, for example, an AMF network element, and is not limited thereto.

[0196] S805, the base station sends a first establishment request, and correspondingly, the DCP receives the first establishment request.

[0197] The first establishment request is used to request the establishment of a data session, that is, to request the establishment of a data transmission channel between the base station and the DCP to transmit data.

[0198] As one possible implementation, the first establishment request is used to establish a GTPU tunnel between the base station and the DCP. The first establishment request includes one or more of the following: DSID, session ID, tunnel endpoint identification (TEID) corresponding to the base station, and the IP address of the base station. Among them, the TEID uniquely identifies a tunnel segment between the two nodes. The TEID is a temporarily assigned object, which is established as needed and discarded when not in use.

[0199] S806, DCP sends a first establishment request response, and correspondingly, the base station receives the first establishment request response.

[0200] The first establishment request response indicates that the DCP has successfully established a data session with the base station.

[0201] As one possible implementation, the first establishment request response indicates that the GTPU tunnel between the DCP and the base station has been successfully established. The first establishment request response includes one or more of the following: the TEID corresponding to the DCP and the IP address of the DCP.

[0202] S807, the base station sends a second establishment request, and the UE receives the second establishment request accordingly.

[0203] The second establishment request includes a session ID and is used to request the establishment of a data bearer between the UE and the base station to enable data transmission between the UE and the base station.

[0204] S808, the UE sends a second establishment request response, and the base station receives the second establishment request response accordingly.

[0205] The second establishment request response indicates that the data bearer between the UE and the base station has been successfully established.

[0206] Specifically, once the data session between the UE and the base station is established, and since the data session between the base station and the DCP is established in S805-S806, the data transmission channel between the UE and the DCP is also established, enabling communication between the UE and the DCP.

[0207] S809, the base station sends a first request response message #2, and correspondingly, the DC receives the first request response message #2.

[0208] The first request response message #2 includes a session ID and indicates that the data transmission channel between the base station and the DCP has been established.

[0209] As another possible implementation, the first request response message #2 indicates that the data transmission channel between the DCP and the UE has been established.

[0210] S810, the UE sends a first request response message #1, and correspondingly, the DC receives the first request response message #1.

[0211] The first request response message #1 includes a session ID and indicates that the data bearer between the UE and the base station has been successfully established.

[0212] As another possible implementation, the first request response message #1 indicates that the data transmission channel between the UE and the DCP has been established.

[0213] S811, the UE sends a second request message, and the base station receives the second request message accordingly.

[0214] The second request message is used to request the establishment of a connection between the UE and the MQTT server; in other words, the second request message is used to request the establishment of a connection between the UE and the DCP server.

[0215] As one possible implementation, the second request message is obtained by the UE encapsulating the CONNECT message according to the MQTT protocol. The second request message is then denoted as CONNECT message #1.

[0216] S812, the base station encapsulates the second request message according to protocol stack #2.

[0217] Specifically, the base station encapsulates the second request message according to the GTPU protocol.

[0218] As one possible implementation, the base station encapsulates the CONNECT message #1 according to the GTPU protocol to obtain the encapsulated CONNECT message (e.g., denoted as CONNECT message #2).

[0219] S813, the base station sends an encapsulated second request message, and correspondingly, the DCP receives the encapsulated second request message.

[0220] As one possible implementation, the base station sends CONNECT message #2, and correspondingly, the DCP receives CONNECT message #2.

[0221] S814, DCP sends a second request response message, and the base station receives the second request response message accordingly.

[0222] The second request response message indicates that the UE has successfully established a connection with the DCP server.

[0223] As one possible implementation, the second request response message is a CONNECTACK message.

[0224] S815, the base station sends a second request response message, and the UE receives the second request response message accordingly.

[0225] S816, the UE obtains data #2 corresponding to the first topic (an example of the first data), encapsulates data #2 according to protocol stack #2, and obtains data packet #2.

[0226] This application does not limit the specific implementation method of the UE acquiring data #2. For example, the UE may perform the data acquisition process itself to acquire data #2.

[0227] S817, the UE sends data packet #2, and the base station receives data packet #2 accordingly.

[0228] As one possible implementation, the UE sends a PUBLISH message to the base station according to the MQTT protocol, and sends data packet #2 to the base station through the PUBLISH message.

[0229] As one possible implementation, the variable header of the PUBLISH message also includes DSID and DAID. DAID is used to identify the UE.

[0230] S818, the base station sends data packet #2, and correspondingly, the DCP receives data packet #2.

[0231] As one possible implementation, the base station sends a PUBLISH message to the DCP, and then sends data packet #2 to the DCP via the PUBLISH message.

[0232] S819, DCP parses data packet #2 according to protocol stack #2 and obtains data #2.

[0233] In the above, method 800 uses protocol stack #2 for data transmission. Specifically, the MQTT protocol is deployed in the UE, base station, and DCP. When the UE publishes or subscribes to data to the DCP, it can encapsulate the data according to the MQTT protocol without having to process the data through the base station. This improves the security of data transmission.

[0234] Figure 9 This is a schematic diagram of protocol stack #3 provided in the embodiments of this application. It should be understood that protocol stack #3 can be applied to any node in the data flow process (such as...). Figure 9 (UE, RAN, DCP, DPF).

[0235] exist Figure 9 In the protocol stack #3 shown, the MQTT protocol is deployed in the RAN node, DCP node, and DPF.

[0236] Figure 10 This is a schematic diagram of method 1000 provided in an embodiment of this application. Method 1000 describes the process of data transmission using protocol stack #3. It should be understood that the numbering of each step in method 1000 is for ease of description, and the numbering of each step does not limit the execution order of the steps.

[0237] S1001, UE transmits capability information, and correspondingly, DC receives capability information.

[0238] Among them, the capability information indicates that the UE does not support the MQTT protocol.

[0239] S1002, DC determines the UE based on capability information and data service requests.

[0240] For information on data service requests, please refer to section S601; it will not be repeated here.

[0241] Specifically, the DC selects the appropriate UE to process the data service targeted by the data service request based on the capability information and data service request of one or more UEs.

[0242] As one possible implementation, if the UE does not support the MQTT protocol, the DC can configure the base station where the UE is located to handle the data service requested by the data service request. In other words, the base station where the UE is located assists the UE in handling the data service requested by the data service request.

[0243] S1003, DC sends first request message #1, and correspondingly, UE receives first request message #1.

[0244] The first request message #1 is used to request the establishment of a data session, that is, to request the establishment of a data transmission channel between the UE and the base station to transmit data.

[0245] For details regarding the specific content and sending method of the first request message #1, please refer to S803; it will not be repeated here.

[0246] S1004, DC sends first request message #2, and correspondingly, the source base station receives first request message #2.

[0247] The first request message #2 is used to request a data session, that is, to request the establishment of a data transmission channel between the base station and the DCP to transmit data.

[0248] For details regarding the specific content and sending method of the first request message #2, please refer to S804; it will not be repeated here.

[0249] S1005, the base station sends a first establishment request based on the first request message #2, and correspondingly, the DCP receives the first establishment request.

[0250] Specifically, after receiving the first request message #2, the base station will select a suitable DCP to establish a data session. This application does not limit the specific method by which the base station selects the DCP. For example, the base station can select the DCP through pre-configured rules.

[0251] S1006, DCP sends a first establishment request response, and correspondingly, the base station receives the first establishment request response.

[0252] The first connection request response indicates that the base station and DCP have successfully established a connection.

[0253] As one possible implementation, the first connection request is a CONNECT message. Specifically, the base station sends a CONNECT message to the DCP according to the MQTT protocol. The response to the first connection request is a CONNECTACK message. After receiving the CONNECTACK message, the base station determines that a connection has been established with the DCP.

[0254] S1007, the base station sends the first subscription request, and correspondingly, the DCP receives the first subscription request.

[0255] The first subscription request includes a first topic, and the first subscription request is used to subscribe to data that needs to be forwarded to the UE.

[0256] Optionally, the first subscription request may also include a session ID.

[0257] S1008, DCP sends a first subscription request response, and correspondingly, the base station receives the first subscription request response.

[0258] The first subscription request response indicates that the base station has successfully subscribed to the DCP.

[0259] As one possible implementation, the first subscription request is a SUBSCRIBE message. Specifically, the base station sends a SUBSCRIBE message to the DCP according to the MQTT protocol, and the response to the first subscription request is a SUBACK message. After receiving the SUBACK message, the base station determines that the subscription was successful.

[0260] S1009, the base station sends a second establishment request, and the UE receives the second establishment request accordingly.

[0261] The second establishment request includes a session ID and is used to request the establishment of a data bearer between the UE and the base station to enable data transmission between the UE and the base station.

[0262] S1010, the UE sends a second establishment request response, and the base station receives the second establishment request response accordingly.

[0263] The second establishment request response indicates that the data bearer between the UE and the base station has been successfully established.

[0264] Specifically, once the data session between the UE and the base station is established, the UE can communicate with the DCP through the base station because the data session between the base station and the DCP was established in S1005-S1006.

[0265] S1011, the base station sends a first request response message #2, and correspondingly, the DC receives the first request response message #2.

[0266] The first request response message #2 includes a session ID and indicates that the data transmission channel between the base station and the DCP has been established.

[0267] S1012, the UE sends a first request response message #1, and correspondingly, the DC receives the first request response message #1.

[0268] The first request response message #1 includes a session ID and indicates that the data bearer between the UE and the base station has been successfully established.

[0269] S1013, the UE sends data #3 (an example of the first data), and correspondingly, the base station receives data #3.

[0270] Among them, data #3 is the data corresponding to the first topic.

[0271] S1014, the base station encapsulates data #3 according to protocol stack #3 to obtain data packet #3.

[0272] Specifically, the base station encapsulates data #3 according to the MQTT protocol.

[0273] S1015, the base station sends data packet #3, and correspondingly, the DCP receives data packet #3.

[0274] As one possible implementation, the base station sends a PUBLISH message to the DCP according to the MQTT protocol, and then sends data packet #3 to the DCP through the PUBLISH message.

[0275] As one possible implementation, the variable header of the PUBLISH message also includes DSID and DAID, where DAID is used to identify the base station.

[0276] S1016, DCP sends downlink data (i.e., second data), and correspondingly, the base station receives the downlink data.

[0277] Downlink data is the data that needs to be forwarded to the UE.

[0278] As one possible implementation, the DCP obtains downlink data from other nodes. For example, the DCP obtains downlink data from the DPF. Specifically, the DPF parses data packet #3 according to protocol stack #3 to obtain data #3, processes data #3 to obtain downlink data, and then publishes the downlink data.

[0279] S1017, the base station sends downlink data, and the UE receives downlink data accordingly.

[0280] Specifically, in S1007, the base station sends a first subscription request to the DCP to subscribe to the data that needs to be forwarded to the UE. This can be understood as the UE subscribing to downlink data through the base station. Then, in S1016, after the DCP obtains the downlink data, it sends the downlink data to the base station, which then sends the downlink data to the UE.

[0281] The above method 1000 performs data transmission based on protocol stack #3. The MQTT protocol is deployed in the base station and DCP. If the UE does not support the MQTT protocol, the data can be processed through the base station. In this way, an asynchronous data communication structure supporting multi-point to multi-point is constructed.

[0282] The method proposed in this application can be applied to various scenarios and is not limited thereto. For example, the method proposed in this application can be applied to UE handover scenarios. Specifically, when the UE is in a mobile state, it may involve the UE handing over from a base station (e.g., referred to as the source base station) to a target base station. The following description is in conjunction with method 1100.

[0283] It should be understood that the target base station is only used as an example and its name does not limit this application. For example, the target base station may also be called the destination base station, etc.

[0284] Figure 11 This is a schematic diagram of method 1100 provided in an embodiment of this application. Method 1100 describes the data transmission process in a handover scenario. It should be understood that in method 1100, the source base station, the target base station, and the DCP all deploy the MQTT protocol.

[0285] This application does not limit the protocol stack used in method 1100, as long as the target base station and DCP support the MQTT protocol. For example, method 1100 can use protocol stack #3 for data transmission.

[0286] For ease of description, in this embodiment of the application, the base station accessed by the UE before handover is referred to as the source base station, and the base station accessed by the UE after handover is referred to as the target base station.

[0287] S1101, UE transmits capability information, and correspondingly, DC receives capability information.

[0288] Among them, the capability information indicates that the UE does not support the MQTT protocol.

[0289] S1102, DC determines UE based on capability information and data service request.

[0290] For information on data service requests, please refer to section S601; it will not be repeated here.

[0291] Specifically, the DC selects the appropriate UE to process the data service targeted by the data service request based on the capability information and data service request of one or more UEs.

[0292] As one possible implementation, if the UE does not support the MQTT protocol, the DC can configure the base station where the UE is located to handle the data service requested by the data service request. In other words, the base station where the UE is located assists the UE in handling the data service requested by the data service request.

[0293] S1103, DC sends first request message #1, and correspondingly, UE receives first request message #1.

[0294] The first request message #1 is used to request the establishment of a data session, that is, to request the establishment of a data transmission channel between the UE and the base station to transmit data.

[0295] For details regarding the specific content of the first request message #1, please refer to S803; it will not be repeated here.

[0296] S1104, DC sends first request message #2, and correspondingly, the source base station receives first request message #2.

[0297] The first request message #2 is used to request a data session, that is, to request the establishment of a data transmission channel between the base station accessed by the UE and the DCP to transmit data.

[0298] For details regarding the specific content of the first request message #2, please refer to S804; it will not be repeated here.

[0299] S1105, the source base station sends a handover request, and the target base station receives the handover request accordingly.

[0300] The handover request is used to switch the base station accessed by the UE from the source base station to the target base station. The handover request includes one or more of the following: a first topic and a data session information list.

[0301] As one possible implementation, the handover request can also be used to indicate that the UE does not support the MQTT protocol.

[0302] S1106, the target base station sends a first establishment request based on the handover request, and correspondingly, the DCP receives the first establishment request.

[0303] Specifically, after receiving the handover request, the target base station determines to establish a data session with the DCP. This application embodiment does not limit the specific method by which the target base station selects the DCP. For example, the target base station selects the DCP through pre-configured rules; or, the target base station determines the DCP based on indication information.

[0304] S1107, DCP sends a first establishment request response, and correspondingly, the target base station receives the first establishment request response.

[0305] The first connection request response indicates that a connection has been successfully established between the target base station and the DCP.

[0306] As one possible implementation, the first connection request is a CONNECT message. Specifically, the target base station sends a CONNECT message to the DCP according to the MQTT protocol. The response to the first connection request is a CONNECTACK message. After receiving the CONNECTACK message, the target base station determines that it has established a connection with the DCP.

[0307] S1108, the target base station sends a first subscription request, and correspondingly, the DCP receives the first subscription request.

[0308] The first subscription request includes a first topic, and the first subscription request is used to subscribe to data that needs to be forwarded to the UE.

[0309] Optionally, the first subscription request includes a session ID.

[0310] S1109, DCP sends a first subscription request response, and correspondingly, the target base station receives the first subscription request response.

[0311] The first subscription request response indicates that the target base station has successfully subscribed to DCP.

[0312] As one possible implementation, the first subscription request is a SUBSCRIBE message. Specifically, the target base station sends a SUBSCRIBE message to the DCP according to the MQTT protocol, and the first subscription request response is a SUBACK message. After receiving the SUBACK message, the target base station determines that the subscription was successful.

[0313] S1110, the target base station sends a handover request response, and the source base station receives the handover request response accordingly.

[0314] The handover request response indicates that the base station has successfully completed the handover.

[0315] S1111, the source base station sends a handover command, and the UE receives the handover command accordingly.

[0316] The handover command instructs the UE to perform base station handover, or in other words, instructs the UE to access the target base station.

[0317] S1112, the UE sends a handover success response, and the target base station receives the handover success response accordingly.

[0318] The successful handover response indicates that the UE has completed the base station handover, or in other words, the UE has accessed the target base station.

[0319] S1113, the target base station sends a second establishment request, and the UE receives the second establishment request accordingly.

[0320] The second establishment request includes a session ID and is used to request the establishment of a data bearer between the UE and the target base station to enable data transmission between the UE and the target base station.

[0321] S1114, the UE sends a second establishment request response, and the base station receives the second establishment request response accordingly.

[0322] The second establishment request response indicates that the data bearer between the UE and the target base station has been successfully established.

[0323] Specifically, once the data session between the UE and the target base station is established, and since the data session between the target base station and the DCP was established in S1106-S1107, the UE can communicate with the DCP through the target base station.

[0324] S1115, the target base station sends a first request response message #2, and correspondingly, the DC receives the first request response message #2.

[0325] The first request response message #2 includes a session ID and indicates that the data transmission channel between the target base station and the DCP has been established.

[0326] S1116, the UE sends a first request response message #1, and correspondingly, the DC receives the first request response message #1.

[0327] The first request response message #1 includes a session ID and indicates that the data bearer between the UE and the target base station has been successfully established.

[0328] S1117, the UE sends data #4 (an example of the first data), and the target base station receives data #4 accordingly.

[0329] Among them, data #4 corresponds to the first topic.

[0330] S1118, the target base station encapsulates data #4 according to the MQTT protocol to obtain data packet #4.

[0331] S1119, the target base station sends data packet #4, and correspondingly, the DCP receives data packet #4.

[0332] As one possible implementation, the target base station sends a PUBLISH message to the DCP according to the MQTT protocol, and then sends data packet #4 to the DCP through the PUBLISH message.

[0333] As one possible implementation, the variable header of the PUBLISH message also includes DSID and DAID, where DAID is used to identify the target base station.

[0334] S1120, DCP sends downlink data, and correspondingly, the target base station receives downlink data.

[0335] Downlink data is the data that needs to be forwarded to the UE.

[0336] As one possible implementation, the DCP obtains downlink data from other nodes. For example, the DCP obtains downlink data from the DPF. Specifically, the DPF parses packet #4 according to the MQTT protocol to obtain data #4, processes data #4 to obtain downlink data, and then publishes the downlink data.

[0337] S1121, the target base station sends downlink data, and the UE receives the downlink data accordingly.

[0338] Specifically, in S1108, the target base station sends a first subscription request to the DCP to subscribe to the data that needs to be forwarded to the UE. This can be understood as the UE subscribing to downlink data through the target base station. In S1120, after the DCP obtains the downlink data, it sends the downlink data to the target base station, which then sends the downlink data to the UE.

[0339] As mentioned above, the MQTT protocol is deployed in both the target base station and the DCP. In the scenario of base station handover, the target base station auxiliary terminal equipment transmits data through the MQTT protocol, thereby improving the efficiency of data transmission.

[0340] Figure 12 This is a schematic block diagram of a communication device 1200 provided in an embodiment of this application. The communication device includes a transceiver unit 1210. The transceiver unit 1210 can be used to implement corresponding communication functions. The transceiver unit 1210 can also be referred to as a communication interface or a communication unit. Optionally, the device 1200 further includes a processing unit 1220. The processing unit 1220 can be used to implement processing operations.

[0341] Optionally, the device 1200 may further include a storage unit, which can be used to store instructions and / or data, and the processing unit 1220 can read the instructions and / or data in the storage unit to enable the device to implement the aforementioned method embodiments.

[0342] Optionally, the transceiver unit 1210 includes a sending unit and / or a receiving unit, wherein the sending unit is used to perform the sending operation in the above embodiments, and the receiving unit is used to perform the receiving operation in the above embodiments.

[0343] It should be noted that the communication device 1200 may include a transmitting unit but not a receiving unit; or, the communication device 1200 may include a receiving unit but not a transmitting unit. Specifically, it depends on whether the above-described scheme executed by the communication device 1200 includes both transmitting and receiving actions. For example, the communication device 1200 is used to execute actions performed by the base station, DCP, DPF, UE, target base station, or DC in the above embodiments. For details, please refer to the relevant descriptions in the above embodiments, which will not be repeated here.

[0344] For example, the communication device 1200 is used to execute the following scheme.

[0345] In one possible design, the device 1200 can be a base station, or it can be a component of a base station (such as a chip, chip system, or circuit). The transceiver unit and processing unit can be used to implement the relevant operations of the base station.

[0346] In one possible implementation, transceiver unit 1210 is configured to receive a first request message from DC, the first request message being used to request the establishment of a data session, wherein the first request message includes a first topic, the first topic being the subject of the data to be transmitted in the data session; transceiver unit 1210 is further configured to establish a data session with DCP according to the first request message; processing unit 1220 is configured to encapsulate the first data corresponding to the first topic according to a first protocol stack and obtain a first data packet, the first protocol stack including the MQTT protocol; transceiver unit 1210 is further configured to send the first data packet to DCP.

[0347] Optionally, the transceiver unit 1210 is also used to receive first data from the UE.

[0348] Optionally, the transceiver unit 1210 is also used to send second data to the UE, the second data being obtained by processing the first data.

[0349] Optionally, the first data packet includes DSID and / or DAID.

[0350] In a second possible design, the device 1200 could be a DPF, or a component of a DPF (such as a chip, chip system, or circuit). The transceiver unit and processing unit could be used to implement the relevant operations of the DPF.

[0351] In one possible implementation, transceiver unit 1210 is configured to receive a first request message from DC, the first request message being used to request the establishment of a data session, the first request message including a first topic, the first topic being the topic of the data to be transmitted in the data session; transceiver unit 1210 is also configured to establish a data session with DCP according to the first request message; transceiver unit 1210 is also configured to receive a first data packet from DCP; and processing unit 1220 is configured to parse the first data packet according to a first protocol stack and obtain the first data corresponding to the first topic, the first protocol stack including the MQTT protocol.

[0352] Optionally, the processing unit 1220 is further configured to process the first data to obtain the second data; the transceiver unit 1210 is further configured to send the second data to the DCP.

[0353] Optionally, the transceiver unit 1210 is also configured to send a first subscription request to the DCP, the first subscription request including a first topic, the first subscription request being used to subscribe to first data.

[0354] In a third possible design, the device 1200 can be a UE, or it can be a component of the UE (such as a chip, chip system, or circuit). The transceiver unit and processing unit can be used to implement the relevant operations of the UE.

[0355] In one possible implementation, transceiver unit 1210 is configured to receive a first request message from DC, the first request message being used to request the establishment of a data session, the first request message including a first topic, the first topic being the subject of the data to be transmitted in the data session; transceiver unit 1210 is further configured to establish a data session with DCP according to the first request message; processing unit 1220 is configured to encapsulate the first data corresponding to the first topic according to a second protocol stack and obtain a first data packet, the second protocol stack including the MQTT protocol; transceiver unit 1210 is further configured to send the first data packet to a third communication device.

[0356] Optionally, the transceiver unit 1210 is further configured to send a second request message to the base station, the second request message being used to request the establishment of a connection between the UE and the DCP server; and to receive a second request response message from the base station, the second request response message indicating that the UE and the DCP server have successfully established a connection.

[0357] Optionally, the transceiver unit 1210 is further configured to receive a session establishment request from the base station, the session establishment request being used to request the establishment of a data bearer; the transceiver unit 1210 is further configured to send a session establishment request response to the base station, the session establishment request response indicating that the data bearer has been successfully established, wherein the data bearer is used for data transmission between the UE and the base station.

[0358] Optionally, the transceiver unit 1210 is also used to send a first data packet to the base station, and the first data packet is forwarded to the DCP by the base station.

[0359] A fourth possible design is that the device 1200 is a DCP, or it can be a component of a DCP (such as a chip, chip system, or circuit). The transceiver unit and processing unit can be used to implement the relevant operations of the DCP.

[0360] In one possible implementation, the transceiver unit 1210 is configured to receive a first establishment request from a base station in response to a first request message, the first establishment request being used to request the establishment of a data session between the base station and the DCP; the first request message originates from the DCP and includes a first subject, the first subject being the subject of the data to be transmitted in the data session; the transceiver unit 1210 is further configured to send a first establishment request response to the base station, the first establishment request response indicating that the data session has been successfully established; the transceiver unit 1210 is further configured to receive a second request message from the base station, the second request message being used to request the establishment of a connection between the UE and the DCP server; and send a second request response message to the base station, the second request response message indicating that the UE and the DCP server have successfully established a connection; the transceiver unit 1210 is further configured to receive a first data packet from the base station, and the processing unit 1220 is configured to parse the first data packet according to a second protocol stack and obtain the first data, the second protocol stack including the MQTT protocol.

[0361] In a fifth possible design, the device 1200 can be a target base station, or it can be a component of the target base station (such as a chip, chip system, or circuit). The transceiver unit and processing unit can be used to implement the relevant operations of the target base station.

[0362] In one possible implementation, the transceiver unit 1210 is configured to receive a first handover request from a base station in response to a first request message, the first handover request instructing the target base station to provide communication services to the UE; the first request message comes from the DC, the first request message is used to request the establishment of a data session, the first request message includes a first topic, the first topic being the subject of the data transmitted in the data session; the transceiver unit 1210 is further configured to establish a data session with the DCP according to the first handover request; the processing unit 1220 is configured to encapsulate the first data corresponding to the first topic according to the MQTT protocol and obtain a first data packet; the transceiver unit 1210 is further configured to send the first data packet to a third communication device.

[0363] Optionally, the transceiver unit 1210 is also used to receive first data from the UE.

[0364] Optionally, the transceiver unit 1210 is further configured to send second data to the UE, wherein the second data is obtained by processing the first data.

[0365] It is understood that the division of units in the above-described device is merely a logical functional division. Each function can correspond to a functional unit, or two or more functions can be integrated into one functional unit. In actual implementation, all or some units can be integrated into a single physical entity, or they can be distributed across different physical entities. Furthermore, the aforementioned functional units can be implemented in hardware, software, or a combination of both. Whether a function is executed in hardware or software depends on the specific application and design constraints of the technical solution. Those skilled in the art can use different methods to implement the described functions for each specific application, but such implementation should not be considered beyond the scope of this application.

[0366] In one example, the functional unit in any of the above devices may be one or more integrated circuits configured to implement the above methods, such as: one or more application-specific integrated circuits (ASICs), or one or more central processing units (CPUs), one or more microcontroller units (MCUs), one or more digital signal processors (DSPs), or one or more field-programmable gate arrays (FPGAs), or a combination of at least two of these integrated circuit forms.

[0367] In one example, the storage unit may include random access memory, flash memory, read-only memory, programmable read-only memory, or electrically erasable programmable memory and / or registers, etc.

[0368] Figure 13 This is a schematic diagram of another communication device 1300 provided in an embodiment of this application. The device 1300 includes a processor 1310, which is coupled to a memory 1320. The memory 1320 is used to store computer programs or instructions and / or data. The processor 1310 is used to execute the computer programs or instructions stored in the memory 1320, or to read the data stored in the memory 1320, in order to execute the methods in the above method embodiments.

[0369] Optionally, there may be one or more processors 1310.

[0370] Optionally, the memory 1320 may be one or more.

[0371] Alternatively, the memory 1320 may be integrated with the processor 1310, or the memory 1320 may be built into the processor 1310, or the memory 1320 may be separate from the processor 1310.

[0372] Optionally, such as Figure 13 As shown, the device 1300 also includes a transceiver 1330 for receiving and / or transmitting signals. For example, a processor 1310 is used to control the transceiver 1330 to receive and / or transmit signals.

[0373] For example, processor 1310 is used to execute computer programs or instructions stored in memory 1320 to implement the relevant operations of terminal devices or network devices in the various method embodiments described above.

[0374] Optionally, the transceiver 1330 includes a transmitter (or a transmitter module, a transmitting circuit, etc.) and / or a receiver (or a receiver module, a receiving circuit, etc.), wherein the transmitter is used to perform the transmitting operation in the above embodiments, and the receiver is used to perform the receiving operation in the above embodiments.

[0375] It should be noted that the communication device 1300 may include a transmitter but not a receiver; or, the communication device 1300 may include a receiver but not a transmitter. Specifically, it depends on whether the above-described scheme performed by the communication device 1300 includes both transmitting and receiving actions. For example, the communication device 1300 is used to perform actions performed by the base station, DCP, DPF, UE, target base station, or DC in the above embodiments. For details, please refer to the relevant descriptions in the above embodiments, which will not be repeated here.

[0376] It should be understood that the processor mentioned in the embodiments of this application can be a central processing unit (CPU), or other general-purpose processors, digital signal processors (DSPs), application-specific integrated circuits (ASICs), field-programmable gate arrays (FPGAs), or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc. A general-purpose processor can be a microprocessor or any conventional processor.

[0377] It should also be understood that the memory mentioned in the embodiments of this application can be volatile memory and / or non-volatile memory. Non-volatile memory can be read-only memory (ROM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), or flash memory. Volatile memory can be random access memory (RAM). For example, RAM can be used as an external cache. By way of example and not limitation, RAM includes the following forms: static random access memory (SRAM), dynamic random access memory (DRAM), synchronous dynamic random access memory (SDRAM), double data rate synchronous dynamic random access memory (DDR SDRAM), enhanced synchronous dynamic random access memory (ESDRAM), synchronous linked dynamic random access memory (SLDRAM), and direct rambus RAM (DR RAM).

[0378] It should be noted that when the processor is a general-purpose processor, DSP, ASIC, FPGA, or other programmable logic device, discrete gate or transistor logic device, or discrete hardware component, the memory (storage module) can be integrated into the processor.

[0379] It should also be noted that the memory described herein is intended to include, but is not limited to, these and any other suitable types of memory.

[0380] Figure 14 This is a schematic block diagram of a chip system 1400 provided in an embodiment of this application. The chip system 1400 (or may also be referred to as a processing system) includes logic circuitry 1410 and an input / output interface 1420.

[0381] The logic circuit 1410 can be a processing circuit in the chip system 1400. The logic circuit 1410 can be coupled to a memory unit, calling instructions from the memory unit, enabling the chip system 1400 to implement the methods and functions of the embodiments of this application. The input / output interface 1420 can be an input / output circuit in the chip system 1400, outputting processed information from the chip system 1400, or inputting data or signaling information to be processed into the chip system 1400 for processing.

[0382] As one option, the chip system 1400 is used to implement the operations performed by the communication device in the various method embodiments described above.

[0383] For example, logic circuit 1410 is used to implement processing-related operations performed by the communication device in the above method embodiments; input / output interface 1420 is used to implement sending and / or receiving-related operations performed by the communication device in the above method embodiments.

[0384] This application also provides a computer-readable storage medium storing computer instructions for implementing the methods executed by the communication device in the above-described method embodiments.

[0385] For example, when the computer program is executed by the computer, it enables the computer to implement the methods executed by the communication device in the various embodiments of the above methods.

[0386] This application also provides a computer program product comprising instructions which, when executed by a computer, implement the methods performed by the communication device in the above-described method embodiments.

[0387] This application also provides a communication system, which includes the base station and / or DCP and / or DPF and / or UE and / or target base station and / or DC in the above embodiments.

[0388] The explanations and beneficial effects of the relevant contents in any of the devices provided above can be found in the corresponding method embodiments provided above, and will not be repeated here.

[0389] In the several embodiments provided in this application, it should be understood that the disclosed apparatus and methods can be implemented in other ways. For example, the apparatus embodiments described above are merely illustrative; for instance, the division of units is only a logical functional division, and in actual implementation, there may be other division methods. For example, multiple units or components may be combined or integrated into another system, or some features may be ignored or not executed. Furthermore, the mutual coupling or direct coupling or communication connection shown or discussed may be through some interfaces, and the indirect coupling or communication connection of apparatus or units may be electrical, mechanical, or other forms.

[0390] In the above embodiments, implementation can be achieved entirely or partially through software, hardware, firmware, or any combination thereof. When implemented using software, it can be implemented entirely or partially in the form of a computer program product. The computer program product includes one or more computer instructions. When the computer program instructions are loaded and executed on a computer, all or part of the processes or functions described in the embodiments of this application are generated. The computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable device. For example, the computer can be a personal computer, a server, or a network device, etc. The computer instructions can be stored in a computer-readable storage medium or transmitted from one computer-readable storage medium to another. For example, the computer instructions can be transmitted from one website, computer, server, or data center to another website, computer, server, or data center via wired (e.g., coaxial cable, fiber optic, digital subscriber line (DSL)) or wireless (e.g., infrared, wireless, microwave, etc.) means. The computer-readable storage medium can be any available medium that a computer can access or a data storage device such as a server or data center that integrates one or more available media. The available media can be magnetic media (e.g., floppy disks, hard disks, magnetic tapes), optical media (e.g., DVDs), or semiconductor media (e.g., solid-state disks, SSDs). For example, the aforementioned available media include, but are not limited to, USB flash drives, portable hard drives, read-only memory (ROM), random access memory (RAM), magnetic disks, or optical disks, and other media capable of storing program code.

[0391] The above description is merely a specific embodiment of this application, but the scope of protection of this application is not limited thereto. Any variations or substitutions that can be easily conceived by those skilled in the art within the scope of the technology disclosed in this application should be included within the scope of protection of this application. Therefore, the scope of protection of this application should be determined by the scope of the claims.

Claims

1. A communication method, characterized in that, The method is applied to a first communication device, including: Receive a first request message from a second communication device, the first request message being used to request the establishment of a data session, the first request message including a first subject, the first subject being the subject of the data transmitted in the data session; A data session is established with the third communication device based on the first request message; The first data packet is obtained by encapsulating the first data corresponding to the first topic according to the first protocol stack, wherein the first protocol stack includes the Message Queue Telemetry Transmission (MQTT) protocol. The first data packet is sent to the third communication device.

2. The method according to claim 1, characterized in that, The method further includes: Receive the first data from the terminal device.

3. The method according to claim 2, characterized in that, The method further includes: The second data is sent to the terminal device, which is obtained by processing the first data.

4. A communication method, characterized in that, The method is applied to a fourth communication device, including: Receive a first request message from a second communication device, the first request message being used to request the establishment of a data session, the first request message including a first subject, the first subject being the subject of the data transmitted in the data session; A data session is established with the third communication device based on the first request message; The system receives a first data packet from the third communication device, parses the first data packet according to a first protocol stack, and obtains the first data corresponding to the first topic. The first protocol stack includes the MQTT protocol.

5. The method according to claim 4, characterized in that, The method further includes: A first subscription request is sent to the third communication device. The first subscription request includes the first topic and is used to subscribe to the first data.

6. A communication method, characterized in that, The method is applied to a terminal device and includes: Receive a first request message from a second communication device, the first request message being used to request the establishment of a data session, the first request message including a first subject, the first subject being the subject of the data transmitted in the data session; A data session is established with the third communication device based on the first request message; The first data packet is obtained by encapsulating the first data corresponding to the first topic according to the second protocol stack, wherein the second protocol stack includes the MQTT protocol; The first data packet is sent to the third communication device.

7. The method according to claim 6, characterized in that, The establishment of a data session with the third communication device based on the first request message includes: Send a second request message to the first communication device, the second request message being used to request the establishment of a connection between the terminal device and the third communication device; The terminal device receives a second request response message from the first communication device, the second request response message indicating that the terminal device has successfully established a connection with the third communication device.

8. The method according to claim 7, characterized in that, The method further includes: Receive a session establishment request from the first communication device, the session establishment request being used to request the establishment of a data bearer; A session establishment request response is sent to the first communication device, the session establishment request response indicating that the data bearer has been successfully established, wherein the data bearer is used for data transmission between the terminal device and the first communication device.

9. The method according to claim 7 or 8, characterized in that, Sending the first data packet to the third communication device includes: The first data packet is sent to the first communication device, and the first data packet is forwarded to the third communication device via the first communication device.

10. The method according to any one of claims 6 to 9, characterized in that, The method further includes: The terminal device sends capability information to the second communication device, the capability information indicating that the terminal device supports the MQTT protocol.

11. A communication method, characterized in that, The method is applied to a third communication device, including: Receive a first establishment request from a first communication device in response to a first request message, the first establishment request being used to request the establishment of a data session between the first communication device and the third communication device; The first request message comes from the second communication device, and the first request message includes a first topic, which is the topic of the data transmitted in the data session; Send a first establishment request response to the first communication device, the first establishment request response indicating that the data session has been successfully established; Receive a second request message from the first communication device, the second request message being used to request the establishment of a connection between the terminal device and the third communication device; Send a second request-response message to the first communication device, the second request-response message indicating that the terminal device has successfully established a connection with the third communication device; The system receives a first data packet from the first communication device, parses the first data packet according to the second protocol stack, and obtains first data. The second protocol stack includes the MQTT protocol.

12. A communication method, characterized in that, The method is applied to a fifth communication device, including: Receive a first handover request from a first communication device in response to a first request message, wherein the first handover request instructs the fifth communication device to provide communication services to the terminal device; The first request message comes from the second communication device. The first request message is used to request the establishment of a data session. The first request message includes a first topic, which is the topic of the data transmitted in the data session. A data session is established with the third communication device based on the first handover request; The first data packet is obtained by encapsulating the first data corresponding to the first topic according to the MQTT protocol; The first data packet is sent to the third communication device.

13. The method according to claim 12, characterized in that, The method further includes: Receive the first data from the terminal device.

14. The method according to claim 12 or 13, characterized in that, The method further includes: The second data is sent to the terminal device, which is obtained by processing the first data.

15. The method according to any one of claims 1 to 14, characterized in that, include: The first data packet includes a Data Service Identifier (DSID) and / or a Data Agent Identifier (DAID).

16. A communication device, characterized in that, include: A processor for executing computer programs or instructions to cause the communication device to perform the method as described in any one of claims 1 to 15.

17. A computer program product, characterized in that, The computer program product includes programs or instructions for performing the method as described in any one of claims 1 to 15.

18. A computer-readable storage medium, characterized in that, include: The computer-readable storage medium stores a computer program that, when run on a computer, causes the computer to perform the method as described in any one of claims 1 to 15.

Images