Data transmission method, communication apparatus, and communication system
By establishing a separate session between the terminal device and the first node and directly sending uplink data, the transmission overhead problems caused by the TCP header and the IP header are solved, and efficient data transmission is achieved.
Patent Information
- Application Number
- PCT/CN2023/125980
- Authority / Receiving Office
- WO · WO
- Patent Type
- Applications
- Current Assignee / Owner
- Filing Date
- 2023-10-23
- Publication Date
- 2025-05-01
AI Technical Summary
In the data transmission, the existing TCP header and IP header leads to a large transmission overhead, which affects efficiency.
By establishing a separate session between the terminal device and the first node, the terminal device can directly send uplink data without relying on the TCP/IP address protocol, reducing transmission overhead.
The data transmission overhead is reduced, the transmission efficiency is improved, and the uplink data can be reliably transmitted to the node where the first server application is deployed.
Smart Images

Figure CN2023125980_01052025_PF_FP_ABST
Abstract
Description
Data transmission method, communication device and communication system Technical Field
[0001] The embodiments of the present application relate to the field of wireless communication technologies, and more specifically, to a method, device, and system for data transmission. Background Art
[0002] Currently, terminal devices can run an increasing number of client applications, each of which generates data that interacts with server applications developed by third-party systems. Typically, terminal devices transmit data based on the Transmission Control Protocol / Internet Protocol (TCP / IP). For example, terminal devices add TCP and IP headers to the front of the data to be sent. However, these headers occupy a large number of bytes, resulting in significant transmission overhead.
[0003] Summary of the Invention
[0004] The present application provides a method, device, and system for data transmission, which can reduce transmission overhead.
[0005] In a first aspect, a communication method is provided, which can be applied to a terminal device, and can also be applied to a chip, a chip system, a hardware circuit, a software module, or a combination of a hardware circuit and a software module installed in the terminal device. The terminal device is used as an example for explanation below, and the method includes: generating uplink data of a first client application; sending a first data packet through a first session, the first data packet including uplink data, the first session being a session between the terminal device and a first node, the first node being used to load a first server application corresponding to the first client application, the first node being a core network element, and the first server application coming from a third-party system.
[0006] Based on this technical solution, the terminal device can determine the first session corresponding to the first client application, and the terminal device can send uplink data through the first session, so that the uplink data can be transmitted to the first node where the first server application is deployed through the first session without relying on the TCP\IP address protocol, thereby reducing transmission overhead.
[0007] In combination with the first aspect, in some implementations, there is a first mapping relationship between the first session and the first client application.
[0008] Exemplarily, the terminal device includes a first function, and the first function is used to serve a first client application. For example, the first function is used to determine a first mapping relationship between a first session and the first client application.
[0009] In combination with the first aspect, in some implementations, the first node is used to load at least one server application, the first session is used to carry data of a first server application in the at least one server application, and the first client application corresponds to the first server application.
[0010] Based on this technical solution, a separate first session can be established between the first node and the terminal device based on the first server application. The terminal device can send the uplink data generated by the first client application through the first session. The first node can receive the uplink data through the first session and pass the uplink data to the first client application based on the first session, thereby realizing reliable transmission of data packets.
[0011] In combination with the first aspect, in some implementations, the first node is used to load into multiple server applications, the first session is used to carry data of the multiple server applications, and the first client application corresponds to one of the multiple server applications.
[0012] Based on this technical solution, a shared first session can be established between the first node and the terminal device, that is, at least one server application loaded on the first node can share the first session, and the terminal device can send uplink data generated by multiple client applications through the first session, saving the session establishment process.
[0013] In combination with the first aspect, in some implementations, the first data packet includes indication information of the first server application.
[0014] Based on this technical solution, a shared first session can be established between the first node and the terminal device. The first data packet can include indication information of the first server application. The first node or access network device that receives uplink data can manage the indication information of the first server application, thereby reliably delivering the uplink data to the first server device and realizing reliable transmission of the data packet.
[0015] Exemplarily, the indication information may indicate an identifier, index or serial number of the first server application.
[0016] In combination with the first aspect, in some implementations, the first data packet does not include at least one of the following: a Transmission Control Protocol (TCP) address of the first node, an Internet Protocol (IP) address of the first node.
[0017] On the second aspect, a method for data transmission is provided, which can be applied to an access network device, and can also be applied to a chip, a chip system, a hardware circuit, a software module, or a combination of a hardware circuit and a software module installed in the access network device. The following is explained using the first access network device as an example. The method includes: receiving a first data packet through a first session, the first data packet including uplink data of a first client application of a terminal device, the first session being a session between the terminal device and a first node, the first node being used to load a first server application corresponding to the first client application, the first node being a core network network element, and the first server application being from a third-party system; sending a second data packet through the first session, the second data packet being generated based on the first data packet.
[0018] Some implementations of the second aspect are implementations corresponding to some implementations of the first aspect. For the beneficial technical effects of some implementations of the second aspect, please refer to the description of the relevant implementations of the first aspect and will not be repeated here.
[0019] In combination with the second aspect, in some implementations, the first node is used to load at least one server application, the first session is used to carry data of a first server application in the at least one server application, and the first client application corresponds to the first server application.
[0020] In combination with the second aspect, in some implementations, the first node is used to load into multiple server applications, the first session is used to carry data of the multiple server applications, and the first client application corresponds to one of the multiple server applications.
[0021] In combination with the second aspect, in some implementations, the first data packet includes indication information of the first server application, and the second data packet includes indication information of the first server application and uplink data.
[0022] Based on this technical solution, a shared first session can be established between the first node and the terminal device, the first data packet sent by the terminal device can carry indication information of the first server application, the first node can manage the indication information of the first server application, and the access network device does not need to parse the indication information of the first server application, thereby simplifying the complexity of processing by the access network device.
[0023] In combination with the second aspect, in some implementations, the first data packet includes indication information of the first server application, the second data packet includes port information and uplink data of the first server application, and the port information of the first server application and the indication information of the first server application have a second mapping relationship.
[0024] Based on this technical solution, a shared first session can be established between the first node and the terminal device, the first data packet sent by the terminal device can carry indication information of the first server application, the access network device can obtain a second mapping relationship between the indication information of the first server application and the port information of the first server application, and the access network device can implement routing of uplink data based on the second mapping relationship, so that the uplink data is passed to the first server application for processing, thereby realizing reliable transmission of data packets.
[0025] In combination with the second aspect, in some implementations, the method further includes: receiving information indicating a second mapping relationship.
[0026] In combination with the second aspect, in some implementations, the method further includes: sending request information, where the request information is used to request information indicating the second mapping relationship.
[0027] Based on this technical solution, the access network device can obtain the second mapping relationship and implement routing of uplink data based on the second mapping relationship, so that the uplink data is transmitted to the first server application for processing, thereby improving the reliability of data transmission.
[0028] In combination with the second aspect, in some implementations, the first data packet does not include at least one of the following: a Transmission Control Protocol (TCP) address of the first node, an Internet Protocol (IP) address of the first node.
[0029] On the third aspect, a method for data transmission is provided, which can be applied to a first node, and can also be applied to a chip, chip system, hardware circuit, software module, or a combination of hardware circuit and software module installed in the first node. The first node is used as an example for explanation below. The first node is used to load a first server application corresponding to a first client application. The first node is a core network network element, and the first server application comes from a third-party system. The method includes: receiving a second data packet through a first session, the second data packet is generated based on a first data packet sent by a terminal device, the first data packet includes uplink data of the first client application, the first client corresponds to the first server, and the first session is a session between the terminal device and the first node; processing the uplink data through the first server application.
[0030] Some implementation methods of the third aspect are implementation methods corresponding to some implementation methods of the first and second aspects. Regarding the beneficial technical effects of some implementation methods of the third aspect, please refer to the description of the relevant implementation methods of the first and second aspects, and will not be repeated here.
[0031] In combination with the third aspect, in some implementations, the first node is used to load at least one server application, the first session is used to carry data of a first server application in the at least one server application, and the first client application corresponds to the first server application.
[0032] In combination with the third aspect, in some implementations, the first node is used to load into multiple server applications, the first session is used to carry data of the multiple server applications, and the first client application corresponds to one of the multiple server applications.
[0033] In combination with the third aspect, in some implementations, the first data packet includes indication information of the first server application, and the second data packet includes indication information of the first server application and uplink data.
[0034] In combination with the third aspect, in some implementations, the first data packet includes indication information of the first server application, the second data packet includes port information and uplink data of the first server application, and the port information of the first server application and the indication information of the first server application have a second mapping relationship.
[0035] In combination with the third aspect, in some implementations, the first data packet does not include at least one of the following: a Transmission Control Protocol (TCP) address of the first node, an Internet Protocol (IP) address of the first node.
[0036] In a fourth aspect, a communication method is provided, which can be applied to a first node, and can also be applied to a chip, chip system, hardware circuit, software module, or a combination of hardware circuit and software module installed in the first node. The first node is used as an example for explanation below. The first node is used to load a first server application corresponding to a first client application. The first node is a core network network element, and the first server application comes from a third-party system. The method includes: generating downlink data of the first server application; sending a third data packet through the first session, the third data packet including downlink data, and the first session is a session between the terminal device and the first node.
[0037] Based on this technical solution, the first node can send downlink data through the first session, so that the downlink data can be transmitted to the terminal device deployed with the first client application through the first session without relying on the TCP\IP address protocol, thereby reducing transmission overhead.
[0038] In combination with the fourth aspect, in some implementations, the first node is used to load at least one server application, the first session is used to carry data of a first server application in the at least one server application, and the first client application corresponds to the first server application.
[0039] Based on this technical solution, a separate first session can be established between the first node and the terminal device based on the first server application. The first node can send the downlink data generated by the first server application through the first session. The terminal device can receive the downlink data through the first session and pass the uplink data to the first client application based on the first session, thereby realizing reliable transmission of data packets.
[0040] In combination with the fourth aspect, in some implementations, the first node is used to load into multiple server applications, the first session is used to carry data of the multiple server applications, and the first client application corresponds to one of the multiple server applications.
[0041] Based on this technical solution, a shared first session can be established between the first node and the terminal device, that is, at least one server application loaded on the first node can share the first session, and the first node can send downlink data generated by multiple server applications through the first session, saving the session establishment process.
[0042] In combination with the fourth aspect, in some implementations, the third data packet includes indication information of the first server application.
[0043] Based on this technical solution, a shared first session can be established between the first node and the terminal device, the third data packet can include indication information of the first server application, and the terminal device receiving downlink data can obtain the indication information of the first server application, thereby reliably delivering the downlink data to the first client device, thereby realizing reliable transmission of the data packet.
[0044] In combination with the fourth aspect, in some implementations, the first data packet does not include at least one of the following: a Transmission Control Protocol TCP address of the terminal device, an Internet Protocol IP address of the terminal device.
[0045] In a fifth aspect, a communication method is provided, which can be applied to an access network device. In addition, it can also be applied to a chip, a chip system, a hardware circuit, a software module, or a combination of a hardware circuit and a software module installed in the access network device. The following is explained using the first access network device as an example. The method includes: receiving a third data packet through a first session, the third data packet including downlink data of a first server application of a first node, the first session being a session between a terminal device and a first node, the first node being used to load a first server application corresponding to a first client application, the first node being a core network network element, and the first server application coming from a third-party system; sending a fourth data packet through the first session, the fourth data packet being generated based on the third data packet.
[0046] Some implementation methods of the fifth aspect are implementation methods corresponding to some implementation methods of the fourth aspect. Regarding the beneficial technical effects of some implementation methods of the fifth aspect, please refer to the description of the relevant implementation methods of the fourth aspect, which will not be repeated here.
[0047] In combination with the fifth aspect, in some implementations, the first node is used to load at least one server application, the first session is used to carry data of a first server application in the at least one server application, and the first client application corresponds to the first server application.
[0048] In combination with the fifth aspect, in some implementations, the first node is used to load into multiple server applications, the first session is used to carry data of the multiple server applications, and the first client application corresponds to one of the multiple server applications.
[0049] In combination with the fifth aspect, in some implementations, the third data packet includes indication information of the first server application, and the fourth data packet includes indication information of the first server application and downlink data.
[0050] Based on this technical solution, a shared first session can be established between the first node and the terminal device. The third data packet sent by the first node can carry indication information of the first server application. The terminal device can obtain the indication information of the first server application, and the access network device does not need to parse the indication information of the first server application, thereby simplifying the complexity of processing by the access network device.
[0051] In combination with the fifth aspect, in some implementations, the fourth data packet includes indication information of the first server application, the third data packet includes port information and downlink data of the first server application, and the port information of the first server application and the indication information of the first server application have a second mapping relationship.
[0052] Based on this technical solution, a shared first session can be established between the first node and the terminal device, the third data packet sent by the first node can carry the port information of the first server application, the access network device can obtain the second mapping relationship between the indication information of the first server application and the port information of the first server application, and the access network device can implement routing of downlink data based on the second mapping relationship, so that the downlink data is passed to the first client application for processing, thereby realizing reliable transmission of data packets.
[0053] In combination with the fifth aspect, in some implementations, the method further includes: receiving information indicating a second mapping relationship.
[0054] In combination with the fifth aspect, in some implementations, the method further includes: sending request information, where the request information is used to request information indicating the second mapping relationship.
[0055] Based on this technical solution, the access network device can obtain the second mapping relationship and implement routing of downlink data based on the second mapping relationship, so that the downlink data is transmitted to the first client application for processing, thereby improving the reliability of data transmission.
[0056] In combination with the fifth aspect, in some implementations, the first data packet does not include at least one of the following: a Transmission Control Protocol TCP address of the terminal device, an Internet Protocol IP address of the terminal device.
[0057] In the sixth aspect, a data communication method is provided, which can be applied to a terminal device, and can also be applied to a chip, chip system, hardware circuit, software module, or a combination of a hardware circuit and a software module installed in the terminal device. The terminal device is used as an example for explanation below. The method includes: receiving a fourth data packet through a first session, the fourth data packet is generated based on the third data packet sent by the first node, the fourth data packet includes downlink data corresponding to the first server application, the first client corresponds to the first server, the first session is a session between the terminal device and the first node, the first node is used to load the first server application corresponding to the first client application, the first node is a core network network element, and the first server application comes from a third-party system; processing the downlink data through the first client application.
[0058] Some implementation methods of the sixth aspect are implementation methods corresponding to some implementation methods of the first and second aspects. Regarding the beneficial technical effects of some implementation methods of the sixth aspect, please refer to the description of the relevant implementation methods of the first and second aspects, and will not be repeated here.
[0059] In combination with the sixth aspect, in some implementations, there is a first mapping relationship between the first session and the first client application.
[0060] In combination with the sixth aspect, in some implementations, the first node is used to load at least one server application, the first session is used to carry data of a first server application in the at least one server application, and the first client application corresponds to the first server application.
[0061] In combination with the sixth aspect, in some implementations, the first node is used to load into multiple server applications, the first session is used to carry data of the multiple server applications, and the first client application corresponds to one of the multiple server applications.
[0062] In combination with the sixth aspect, in some implementations, the third data packet includes indication information of the first server application, and the fourth data packet includes indication information of the first server application and downlink data.
[0063] In combination with the sixth aspect, in some implementations, the third data packet includes port information of the first server application, the fourth data packet includes indication information and uplink data of the first server application, and the port information of the first server application and the indication information of the first server application have a second mapping relationship.
[0064] In combination with the sixth aspect, in some implementations, the third data packet does not include at least one of the following: a Transmission Control Protocol TCP address of the terminal device, an Internet Protocol IP address of the terminal device.
[0065] In the seventh aspect, a method for data transmission is provided, which is applied to a communication system, wherein the system includes a terminal device, an access network device and a first node, the first node is a core network network element, the first node is used to load a first server application, and the first server application comes from a third-party system, the method including: the terminal device generates uplink data of the first client application; the terminal device sends a first data packet to the access network device through a first session, the first data packet includes uplink data, and the first session is a session between the terminal device and the first node; the access network device sends a second data packet to the first node through the first session, and the second data packet is generated based on the first data packet; the first node processes the uplink data through the first server application.
[0066] Some implementation methods of the seventh aspect are implementation methods corresponding to some implementation methods of the first, second and third aspects. Regarding some implementation methods of the fourth aspect and the beneficial technical effects of some implementation methods, please refer to the relevant descriptions of the first, second and third aspects, and will not be repeated here.
[0067] In an eighth aspect, a communication method is provided, which is applied to a communication system, the system including a terminal device, an access network device and a first node, the first node being a core network network element, the first node being used to load a first server application, the first server application coming from a third-party system, the method including: the first node generating downlink data of the first server application; the first node sending a third data packet to the access network device through a first session, the third data packet including the downlink data; the access network device sending a fourth data packet to the terminal device through the first session, the fourth data packet being generated based on the third data packet; the terminal device processing the downlink data through the first client application.
[0068] Some implementation methods of the eighth aspect are implementation methods corresponding to some implementation methods of the fourth, fifth and sixth aspects. Regarding some implementation methods of the eighth aspect and the beneficial technical effects of some implementation methods, please refer to the relevant descriptions of the fourth, fifth and sixth aspects, and will not be repeated here.
[0069] In the ninth aspect, a communication device is provided, which is applied to a terminal device, and the device includes a processing module and a communication module, wherein the processing module is used to generate uplink data of a first client application; the communication module is used to send a first data packet through a first session, and the first data packet includes uplink data. The first session is a session between the terminal device and a first node, and the first node is used to load a first server application corresponding to the first client application. The first node is a core network network element, and the first server application comes from a third-party system.
[0070] The various implementation methods of the ninth aspect are implementation methods corresponding to the various implementation methods of the first aspect. Regarding the various implementation methods of the tenth aspect and the beneficial technical effects of the various implementation methods, please refer to the relevant description of the first aspect and will not be repeated here.
[0071] In the tenth aspect, a communication device is provided, which is applied to an access network device, and the device includes a processing module and a communication module. The communication module is used to receive a first data packet through a first session, and the first data packet includes uplink data of a first client application of a terminal device. The first session is a session between the terminal device and a first node. The first node is used to load a first server application corresponding to the first client application. The first node is a core network network element, and the first server application comes from a third-party system; the processing module is used to generate a second data packet; the communication module is used to send a second data packet through the first session, and the second data packet is generated based on the first data packet.
[0072] The various implementation methods of the tenth aspect are implementation methods corresponding to the various implementation methods of the second aspect. Regarding the various implementation methods of the tenth aspect and the beneficial technical effects of the various implementation methods, please refer to the relevant description of the second aspect and will not be repeated here.
[0073] In the eleventh aspect, a communication device is provided, which is applied to a first node, and the device includes a processing module and a communication module, wherein the first node is used to load a first server application corresponding to a first client application, the first node is a core network network element, and the first client application comes from a third-party system. The communication module is used to receive a second data packet through a first session, and the second data packet is generated based on the first data packet sent by the terminal device, the first data packet includes uplink data of the first client application, and the first session is a session between the terminal device and the first node; the processing module is used to process the uplink data through the first server application.
[0074] The various implementation methods of the eleventh aspect are implementation methods corresponding to the various implementation methods of the third aspect. Regarding the various implementation methods of the eleventh aspect and the beneficial technical effects of the various implementation methods, please refer to the relevant description of the third aspect and will not be repeated here.
[0075] In the twelfth aspect, a communication device is provided, which is applied to a first node, and the device includes a processing module and a communication module, wherein the first node is used to load a first server application corresponding to a first client application, the first node is a core network network element, and the first server application comes from a third-party system. The processing module is used to generate downlink data of the first server application; the communication module is used to send a third data packet through a first session, and the third data packet includes downlink data. The first session is a session between a terminal device and the first node.
[0076] The various implementation methods of the twelfth aspect are implementation methods corresponding to the various implementation methods of the fourth aspect. Regarding the various implementation methods of the twelfth aspect and the beneficial technical effects of the various implementation methods, please refer to the relevant description of the fourth aspect and will not be repeated here.
[0077] In the thirteenth aspect, a communication device is provided, which is applied to an access network device, and the device includes a processing module and a communication module, wherein the communication module is used to receive a third data packet, the third data packet includes downlink data of a first server application of a first node, the first session is a session between a terminal device and the first node, the first node is used to load a first server application corresponding to a first client application, the first node is a core network network element, and the first server application comes from a third-party system; the processing module is used to generate a fourth data packet based on the third data packet; the communication module is also used to send the fourth data packet through the first session.
[0078] The various implementation methods of the thirteenth aspect are implementation methods corresponding to the various implementation methods of the fifth aspect. Regarding the various implementation methods of the thirteenth aspect and the beneficial technical effects of the various implementation methods, please refer to the relevant description of the fifth aspect and will not be repeated here.
[0079] In the fourteenth aspect, a communication device is provided, which is applied to a terminal device, and the device includes a processing module and a communication module, wherein the communication module is used to receive a fourth data packet through a first session, the fourth data packet is generated based on a third data packet sent by the first node, and the fourth data packet includes downlink data of a first server application. The first client corresponds to the first server, and the first session is a session between the terminal device and the first node. The first node is used to load a first server application corresponding to the first client application. The first node is a core network network element, and the first server application comes from a third-party system; the processing module is used to process the downlink data through the first client application.
[0080] The various implementation methods of the fourteenth aspect are implementation methods corresponding to the various implementation methods of the sixth aspect. Regarding the various implementation methods of the fourteenth aspect and the beneficial technical effects of the various implementation methods, please refer to the relevant description of the sixth aspect and will not be repeated here.
[0081] In the fifteenth aspect, a communication device is provided, which includes a first function, wherein the first function is used to determine a first session corresponding to a first client application, the first session being a session between the communication device and a first node, the first node being used to load a first server application corresponding to the first client application, the first node being a core network element, and the first application task coming from a third-party system.
[0082] In combination with the fifteenth aspect, in some implementations, the first function is used to determine a first mapping relationship between the first session and the first client application.
[0083] In combination with the fifteenth aspect, in some implementations, the first function is used to deactivate a robust header compression (ROHC) function at the Packet Data Convergence Protocol (PDCP) layer.
[0084] In a sixteenth aspect, a communication device is provided, wherein the communication device has the function of implementing the method in any possible implementation of aspects 1 to 8, or aspects 1 to 8. The function can be implemented by hardware, or by hardware executing corresponding software implementation. The hardware or software includes one or more units or modules corresponding to the above-mentioned functions.
[0085] In the seventeenth aspect, a communication device is provided, comprising at least one processor coupled to at least one memory, and the at least one processor is used to execute a computer program or instruction stored in the at least one memory so that the communication device performs a method as in any aspect from the first aspect to the eighth aspect, or any implementation manner of any aspect.
[0086] In the eighteenth aspect, a communication device is provided, comprising a processor and a communication interface, wherein the communication interface is used to receive data and / or information and transmit the received data and / or information to the processor, and the processor processes the data and / or information, and the communication interface is also used to output the data and / or information processed by the processor, so that the method of any aspect from the first aspect to the eighth aspect, or any implementation of any aspect, is executed.
[0087] In the nineteenth aspect, a computer-readable storage medium is provided, in which computer instructions are stored. When the computer instructions are executed on a computer, the method in any one of the first to eighth aspects, or any possible implementation of any one of these aspects, is executed.
[0088] In the twentieth aspect, a computer program product is provided, which includes a computer program code, and when the computer program code is run on a computer, the method in any aspect from the first to the eighth aspect, or any possible implementation of any aspect of these aspects, is executed.
[0089] In aspect 21, a communication system is provided, comprising a communication device that executes the method of any one of aspects 1 to 3, and / or a communication device that executes the method of any one of aspects 4 to 6.
[0090] In aspect 22, a communication system is provided, comprising a communication device as described in any one or more of aspects 9 to 20, or a communication device in any possible implementation of any of these aspects. BRIEF DESCRIPTION OF THE DRAWINGS
[0091] FIG1 shows a schematic diagram of a network architecture provided in an embodiment of the present application.
[0092] Figure 2 is a schematic structural diagram of the communication architecture in which the server application is deployed in the core network element provided in an embodiment of the present application.
[0093] FIG3 is a schematic diagram of a 5G network protocol stack.
[0094] FIG4 is a schematic diagram of a data packet format.
[0095] FIG5 is a schematic diagram of a first determination method provided in an embodiment of the present application.
[0096] FIG6 is a schematic diagram of a protocol stack corresponding to the first determination method provided in an embodiment of the present application.
[0097] FIG7 is a schematic diagram of a second determination method provided in an embodiment of the present application.
[0098] FIG8 is a schematic diagram of a first protocol stack corresponding to the second determination method of an embodiment of the present application.
[0099] FIG9 is a schematic diagram of a second protocol stack corresponding to the second determination method of an embodiment of the present application.
[0100] FIG10 is a schematic flowchart of a communication method provided in an embodiment of the present application.
[0101] FIG11 is a schematic flowchart of another communication method provided in an embodiment of the present application.
[0102] FIG12 is a schematic flowchart of a method for an access network device to obtain a second mapping relationship according to an embodiment of the present application.
[0103] FIG13 is a schematic diagram of a communication device provided in an embodiment of the present application.
[0104] FIG14 is a schematic diagram of another communication device provided in an embodiment of the present application. DETAILED DESCRIPTION
[0105] The technical solution in this application will be described below with reference to the accompanying drawings.
[0106] The technical solutions provided in this application can be applied to various communication systems, such as fifth generation (5G) or satellite communication systems, sixth generation (6G) mobile communication systems, and other communication systems evolved after 5G, such as new radio (NR) systems, or fusion 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.
[0107] A node in a communication system can send signals to or receive signals from another node. The signals may include information, signaling, or data. A node may also be replaced by an entity, network entity, device, communication device, communication module, network element, communication node, etc. This application uses a node as an example for description.
[0108] Figure 1 shows a schematic diagram of a network architecture provided by an embodiment of the present application. As shown in Figure 1, the network architecture may include but is not limited to the following: a client application and a server application.
[0109] 1. Server Application
[0110] Server applications are applications running within a mobile network that are responsible for processing and responding to requests from clients, providing users with network services such as centralized computing, information processing, and data management. For example, the mobile network may be compliant with the 3GPP (3GPP) rd A network that complies with 3GPP (3rd Generation Partnership Project) specifications or future-defined mobile network specifications, such as a public land mobile network (PLMN).
[0111] For the sake of convenience, in the embodiment of the present application, the device on which the server application is deployed is referred to as the first node. The first node can obtain the server application file from a third-party system. The third-party system is a system outside the mobile network, such as the local server of each developer (producer) manufacturer, the cloud server, etc. For example, the first node can obtain the program file from the Internet that provides various application services (over the top, OTT) to users. The first node loads the program file so that the program file exists in itself to realize the deployment of the server application.
[0112] In the embodiments of the present application, the program file provided by the third-party system and deployed on the first node can be referred to as a server application, a network server (net server), a task, an application instance, or other possible names, which are not specifically limited in this application. For ease of description, the embodiments of the present application use the server application as an example, but any of the above names can be substituted.
[0113] One or more server applications may be deployed on the first node. The multiple server applications may be from the same or different third-party systems, which is not specifically limited in this application.
[0114] 2. Client application
[0115] A client application, also known as an application (APP), is an APP program that runs on user equipment (UE). The client is typically responsible for interacting with the user, displaying data and interfaces, and communicating with the server application to provide network services.
[0116] It should be noted that one server application corresponds to one client application, that is, the server application and the client application have a one-to-one correspondence.
[0117] It is understandable that the server application (network server) involved in the embodiment of the present application can exist in the first node to provide network services to users. For example, the first node can create a complete operating environment for the server application. This feature is different from existing general-purpose tasks. For example, for general-purpose tasks such as calculation, data collection or positioning, these general-purpose tasks are usually not based on services provided to users by a specific third-party system. The execution subject of the general-purpose task can provide execution results in a dynamic deployment and execution manner. The embodiment of the present application deploys the server application provided by the third-party system within the mobile network, and the first node within the mobile network provides users with services based on the server application. Compared with the services provided to users by devices outside the mobile network (such as devices where cloud servers are deployed), the first node can flexibly use the resources in the mobile network to provide services to users, thereby improving the quality of service.
[0118] The first node is in a mobile network. Exemplarily, the first node can be a core network element, such as a task process function (TPF). In an embodiment of the present application, the server application and the client application can interact via a communication protocol between the first node and the UE, such as interaction between the TPF and the UE. To facilitate understanding of the embodiment of the present application, the communication system is described below with reference to FIG2.
[0119] Figure 2 is a schematic diagram of a communication architecture in which a server application is deployed on a core network element according to an embodiment of the present application. As shown in Figure 2, the communication architecture includes:
[0120] 1. Management plane functions: These functions are responsible for communicating and interacting with third-party systems and core network elements. For example, these functions may include network AI management orchestration (NAMO).
[0121] 2. (Radio) Access Network (R)AN) equipment: This equipment provides authorized users in a specific area with access to the communications network. For ease of description, this equipment will be referred to as an AN.
[0122] AN equipment can adopt different wireless access technologies. There are currently two types of wireless access technologies: 3GPP access technology (for example, the wireless access technology used in the third generation (3rd generation, 3G), fourth generation (4G) or 5G systems) and non-3GPP (non-3GPP) access technology. 3GPP access technology refers to access technology that complies with 3GPP standard specifications. For example, the access network equipment in the 5G system is called the next generation Node Base station (gNB) or RAN equipment. Non-3GPP access technologies may include air interface technologies represented by access points (APs) in wireless fidelity (WiFi), worldwide interoperability for microwave access (WiMAX), code division multiple access (CDMA), etc. AN equipment can allow terminal devices and the 3GPP core network to interconnect and communicate using non-3GPP technologies.
[0123] AN equipment is responsible for radio resource management, quality of service (QoS) management, data compression and encryption, etc. on the air interface side. AN equipment provides access services to terminal devices and forwards control signals and user data between terminal devices and the core network.
[0124] AN devices may include, for example, but are not limited to: macro base stations, micro base stations (also known as small stations), radio network controllers (RNCs), node Bs (NBs), base station controllers (BSCs), base transceiver stations (BTSs), home base stations (e.g., home evolved NodeBs, or home NodeBs, HNBs), baseband units (BBUs), APs in WiFi systems, wireless relay nodes, wireless backhaul nodes, transmission points (TPs) or transmission and reception points (TRPs), etc., and may also be gNBs or transmission points (TRPs or TPs) in 5G (e.g., NR) systems, one or a group of (including multiple antenna panels) antenna panels of a base station in a 5G system, or a network node constituting a gNB or transmission point, such as a distributed unit (DU), or a base station in a 6G system. The embodiments of the present application do not limit the specific technology and specific device form adopted by the AN device.
[0125] 3. Terminal equipment: may be referred to as access terminal, UE, user station, mobile station, mobile station, remote station, remote terminal, mobile device, user terminal, terminal, wireless communication device, user agent or user device.
[0126] The terminal device can be a device that provides voice / data to users, for example, a handheld device or vehicle-mounted device with a wireless connection function. At present, some examples of terminals are: mobile phones, tablet computers, laptop computers, 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 wireless modems, wearable devices, terminal devices in 5G networks or future evolved public land mobile communication networks (PLMNs). The terminal equipment in the network (PLMN), etc., is not limited to this in the embodiments of the present application.
[0127] As an example and not a limitation, in the embodiment of the present application, the terminal device may also be a wearable device. Wearable devices may also be called wearable smart devices, which are a general term for wearable devices that are intelligently designed and developed using wearable technology for daily wear, such as glasses, gloves, watches, clothing, and shoes. A wearable device is a portable device that is worn directly on the body or integrated into the user's clothes or accessories. Wearable devices are not only hardware devices, but also achieve powerful functions through software support, data interaction, and cloud interaction. Broadly speaking, wearable smart devices include those that are fully functional, large in size, and can achieve complete or partial functions without relying on smartphones, such as smart watches or smart glasses, as well as those that only focus on a certain type of application function and need to be used in conjunction with other devices such as smartphones, such as various smart bracelets and smart jewelry for vital sign monitoring.
[0128] In the embodiments of the present application, the device for implementing the function of the terminal device can be the terminal device, or it can be a device that can support the terminal device to implement the function, such as a chip system or chip, which can be installed in the terminal device. In the embodiments of the present application, the chip system can be composed of a chip, or it can include a chip and other discrete devices.
[0129] 4. Core Network (CN): It can provide user connections, manage users, and carry services. The first node for deploying the server application can be any one or more core network elements in the core network.
[0130] It can be understood that the network architecture shown above is only an exemplary illustration, and the network architecture applicable to the embodiments of the present application is not limited to this. Any network architecture that can realize the functions of the above-mentioned network elements is applicable to the embodiments of the present application.
[0131] It can also be understood that the network elements of the embodiments of the present application, such as TPF, task control function (TCF), etc. can be understood as network elements used to implement different functions. For example, they can be combined into network slices as needed. These network elements can be independent devices, or they can be integrated into the same device to implement different functions, or they can be network elements in hardware devices, or they can be software functions running on dedicated hardware, or they can be virtualized functions instantiated on a platform (for example, a cloud platform). This application does not limit the specific form of the above-mentioned network elements.
[0132] It is also understood that the above naming is only defined to facilitate the distinction between different functions and should not constitute any limitation to this application. This application does not exclude the possibility of adopting other naming in other networks in the future.
[0133] In order to facilitate understanding of the technical solution of the present application, the concept of the communication protocol involved in the embodiments of the present application is introduced.
[0134] Two devices in a communication system can receive and send signals based on a communication protocol. For example, existing communication protocols include, but are not limited to, the physical layer (PHY), medium access control (MAC), radio link control (RLC), packet data convergence protocol (PDCP), service data adaptation protocol (SDAP), transmission control protocol / internet protocol (TCP / IP) layer, application (APP), layer 1 (L1), layer 2 (L2), internet protocol (IP) layer, user datagram protocol (UDP), general packet radio service (GPRS) tunnel protocol for the user plane (GTP-U), etc.
[0135] It is understood that the names of network elements, protocol layers, names of data units corresponding to some protocol layers, names of interfaces between network elements, etc. involved in this application are only examples. In future communication networks, the names of these network elements, protocol layers, names of data units corresponding to protocol layers, names of interfaces between network elements, etc. may also adopt other names. As long as they have the same or similar functions and achieve the same or similar technical purposes, they should all fall within the technical scope covered by this application. For example, in a 5G network, a network function may be represented as NF, a terminal device may also be referred to as UE, a medium access control layer may be represented as MAC layer, a protocol data unit may be represented as PDU, a service data unit may be represented as SDU, etc. In a 6G network, these names may also adopt new names.
[0136] For the sake of brevity in description, the following embodiments describe network elements, protocol layers, data units corresponding to some protocol layers, etc., using some abbreviations as examples. However, these abbreviations are only examples and can be replaced with other abbreviations or names without limitation.
[0137] Figure 3 is a schematic diagram of a 5G network protocol stack. As shown in Figure 3, a third-party device outside the mobile network can provide services for the UE, and the TCP / IP protocol can provide a connection-oriented communication service for the third-party device (such as the device where the cloud server is located) and the UE. For example, the third-party device and the UE have the need for data transmission, and the TCP / IP protocol stack entity can be responsible for establishing connections, sending data, and disconnecting based on the instructions of the APP. In order to achieve reliable transmission of data between the third-party device and the UE, the TCP entity can attach a TCP header to the front end of the data to be sent, and the IP entity can add an IP header before the TCP header. Thus, the third-party device and the UE can achieve reliable communication based on the TCP header and the IP header.
[0138] Figure 4 is a schematic diagram of a data packet format. As shown in Figure 4, a data packet includes at least data, a TCP header, and an IP header. For example, a TCP header includes at least the source port number and the destination port number, and an IP header includes at least the source IP address and the destination IP address. The port number can be used to distinguish apps, the source port number and source IP address combined can identify the sending address of the data, and the destination port number and destination IP address combined can identify the receiving address of the data.
[0139] As can be seen from Figures 3 and 4, when data is transmitted between a third-party device and the UE over TCP / IP, the TCP header and IP header account for a significant amount of transmission overhead. For example, the maximum transmission unit (MTU) is typically 576 bytes, and the TCP and IP headers are larger than 40 bytes. This means that the TCP and IP headers account for approximately 7% of the transmission overhead. In particular, for packets with a data size of less than 100 bytes, the TCP and IP headers can account for over 50% of the transmission overhead.
[0140] Therefore, the present application proposes a technical solution, in which the UE can determine the session corresponding to the client application, and the UE can send uplink data through the determined session, so that the uplink data can be transmitted to the first node where the first server application is deployed without relying on the TCP\IP address protocol, thereby reducing the transmission overhead.
[0141] The way in which the UE determines a session is related to the type of session. In some implementations, the UE may include a first function, and the first function may be used to serve a client application on the UE, for example, the first function may be used to determine a session corresponding to the client application. Exemplarily, the session between the UE and the first node is at an application granularity, for example, one session is used to carry data about a server application. Another exemplary embodiment, the session between the UE and the first node is at a node granularity, for example, one session is used to carry data of multiple server applications on the first node. To facilitate understanding of the embodiments of the present application, the two implementations are introduced below in conjunction with Figures 5 and 6, respectively.
[0142] Figure 5 is a schematic diagram of the first determination method provided by an embodiment of the present application. As shown in Figure 5, the first node is deployed with server application #1, server application #2 and server application #3, which respectively establish session #1, session #2 and session #3 with the UE. In other words, any server application in the first node can establish an independent session with the UE, and the session is application-granular. The first function can manage the mapping relationship between three client applications (represented by UE APPs in Figure 5) and the three sessions, and provide data sending function for UE APPs based on the mapping relationship.
[0143] For ease of description, in the embodiment of the present application, server application #1 corresponds to client application #1, server application #2 corresponds to client application #2, and server application #3 corresponds to client application #3, which will not be detailed below.
[0144] For example, in the uplink direction, the client application #1 corresponding to the server application #1 generates uplink data to be sent. The first function can add the APP description information corresponding to the client application #1 to the uplink data based on the mapping relationship, and pass the quality of service (QoS) flow corresponding to the uplink data to the SDAP entity of the UE. The SDAP entity can map the QoS flow based on the APP description information attached to the QoS flow, and map the QoS flow to the bearer of the session #1 corresponding to the server application #1. The SDAP entity of the RAN obtains the uplink data and can map the uplink data to the tunnel of the session #1 corresponding to the server application #1. Based on the tunnel corresponding to the server application #1, the first node can determine the server application #1 corresponding to the data based on the tunnel end point identifier (TEID), and pass the data to the server application #1 for processing by the server application #1.
[0145] For another example, in the downlink direction, server application #1 generates downlink data. Server application #1 can send the data to the RAN through the tunnel of session #1. The RAN sends the data to the UE through the bearer of session #1. The first function determines client application #1 based on the mapping relationship between the session and the client application, and passes the data to client application #1.
[0146] It should be understood that because the server application is deployed on the first node within the mobile network, the first node forwards data to the server application without passing through an interface connected to the external mobile network. In other words, the data packet is processed within the mobile network and is not transmitted outside the mobile network. The data packet does not need to be appended with a TCP header or an IP header, thereby improving the utilization of transmission resources.
[0147] Figure 6 is a schematic diagram of the protocol stack corresponding to the first determination method provided in an embodiment of the present application. As shown in Figure 6, in this protocol stack, there is no need to design a TCP / IP layer. The first function can determine the session corresponding to the data packet through UE APP information and map the data packet to the session. Without relying on TCP / IP, reliable data packet delivery can be achieved, saving the transmission overhead occupied by the TCP header and IP header, and improving the utilization of transmission resources.
[0148] Figure 7 is a schematic diagram of the second determination method provided by an embodiment of the present application. As shown in Figure 7, unlike Figure 7 where each server application can establish an independent session with the UE, multiple server applications deployed on the first node can share a session. For example, if the first node is deployed with server application #1, server application #2, and server application #3, the three server applications can share a session.
[0149] For example, server application #1, server application #2, and server application #3 each provide network services to a UE. Different server applications are assigned different identification information, such as task identification #1, task identification #2, and task identification #3. The first function can be used to determine a mapping relationship between the identification information of the management server application and the client application, and provide data transmission for the client application based on the mapping relationship.
[0150] It should be understood that in this implementation, the server application is deployed on the first node, and the first node passes data to the server application without going through an interface connected to the outside of the mobile network. That is, the data packet is processed within the mobile network and will not be transmitted outside the mobile network. The data packet can add the indication information of the server application without adding the TCP header and the IP header. In this case, a protocol layer for adding the indication information of the server application can be designed in the protocol stack. For example, the indication information of a server application may include the identifier, index or serial number of the server application, etc. This application does not specifically limit this. The following mainly uses the example of the indication information being an identifier to illustrate. In this implementation, the protocol stack can be designed to have a task layer for adding an identifier, and the TCP / IP layer is not designed. The following is a detailed description of the two protocol stacks in conjunction with Figures 8 and 9.
[0151] FIG8 is a schematic diagram of the first protocol stack corresponding to the second method of determining a session in an embodiment of the present application. As shown in FIG8 , in the protocol stack, the first node and the UE can each be provided with a protocol layer for adding indication information of the server application, such as a task layer, and the task layer can be responsible for encapsulating and parsing the task identifier. For example, the task layer at the sending end can add a task header at the front end of the data packet, and the task header includes a task identifier. After receiving the data, the task layer at the receiving end parses the task header, obtains the task identifier, and determines the target server application or target client application corresponding to the data based on the task identifier. In this protocol stack, there is no need to design a TCP / IP layer. The first node can determine the target server application or target client application corresponding to the data packet through the indication information of the server application. Without relying on TCP / IP, reliable transmission of the data packet can be achieved, saving the transmission overhead occupied by the TCP header and the IP header, and improving the utilization rate of transmission resources.
[0152] For example, in the uplink direction, client application #1 generates uplink data, and the UE can add the indication information of server application #1 to the uplink data. The UE sends the data carrying the indication information of server application #1 to the first node via the shared session. The first node forwards the to-be-sent data to the corresponding server application #1 based on the indication information of server application #1.
[0153] For another example, in the downlink direction, server application #1 generates downlink data. The first node adds indication information corresponding to server application #1 to the downlink data and sends the data of the indication information of server application #1 to the UE. The UE determines the client application #1 corresponding to server application #1 based on the indication information of server application #1 and transmits the data to client application #1.
[0154] In this implementation, the RAN does not need to parse the indication information of server application #1. In other words, the indication information of server application #1 can also be encapsulated as part of the payload in GTP-U, thereby simplifying the complexity of RAN communication processing.
[0155] It should be noted that the sender of the data mentioned above can obtain the indication information of the server application in a variety of ways. For example, when a third-party system deploys the server application in the first node, the network can assign an identifier to the server application and inform the third-party system and the first node. The third-party system can update the identifier to the policy control function (PCF), and the PCF can generate a terminal routing selection policy (UE route selection policy, URSP) for the server application. The URSP contains the indication information of the server application and sends it to the UE, so that the UE obtains the indication information of the server application. This application does not specifically limit this.
[0156] Figure 9 is a schematic diagram of the second protocol stack corresponding to the second determination method of an embodiment of the present application. As shown in Figure 9, unlike the protocol stack shown in Figure 8, in this protocol stack, the UE and the RAN can each design a protocol layer for adding the indication information of the server application, and the first node does not need to design a protocol layer for adding the indication information of the server application. The protocol layer of the UE can be responsible for the encapsulation and decapsulation of the indication information of the server application. The protocol layer of the RAN can be responsible for the decapsulation of the indication information of the server application, and determining the mapping relationship between the indication information of the server application and the port information of the server application. For example, data can be transmitted between the UE and the RAN based on the indication information of the server application, and data can be transmitted between the RAN and the first node based on the port information of the server application.
[0157] For example, in the uplink direction, client application #1 can generate uplink data, and the UE's protocol layer can add a task header to the front end of the uplink data. The task header contains the indication information of server application #1. The UE sends the data carrying the indication information of server application #1 to the RAN via a shared session. The RAN's protocol layer parses the task header to obtain the indication information of server application #1, determines the port number of the server application based on the indication information of server application #1, writes the port number of server application #1 to the destination port field of the UDP header, and then sends the data carrying the port number of server application #1 to the first node. The first node can forward the data to the corresponding server application #1 based on the port number of server application #1, and server application #1 will process it.
[0158] For another example, in the downlink direction, server application #1 generates downlink data. The first node writes the server application #1 port number into the source port field of the UDP header. The RAN's UDP header parses the UDP header to obtain the server application #1 port number. The RAN's protocol layer determines the corresponding server application #1 indication based on the server application #1 port number, reassembles the data, adds server application #1 to the front of the data, and sends the data carrying server application #1 to the UE. The UE's protocol layer parses the server application #1 indication and, based on the indication, passes the data to client application #1.
[0159] It is understandable that the embodiments of the present application do not specifically limit the number of server applications deployed by the first node. When the first node deploys a client application, in one possible implementation, a session as shown in Figure 5 can be established between the first node and the UE, and the data packets sent by the UE do not need to carry the indication information of the server application. In another possible implementation, a session as shown in Figure 7 can also be established between the first node and the UE, and the data packets sent by the UE can carry the indication information of the server application.
[0160] The embodiment of the present application does not specifically limit the number of server applications sharing a session. When the first node is deployed with multiple server applications, all server applications of the first node can share one session, or some server applications of the first node can share one session. The present application does not specifically limit this.
[0161] The above describes two communication methods between the first node and the UE. In these two methods, data packets do not need to be processed at the TCP / IP layer, thereby reducing the transmission overhead occupied by the TCP header and the IP header and improving the utilization of transmission resources. In some implementations, TCP / IP-related functions in the UE, the RAN, or the first node may also be deactivated. For example, the robust header compression (ROHC) function used to compress the TCP header and the IP header in the PDCP may be deactivated. This is not particularly limited in this application.
[0162] The above describes the system provided by this application. The following describes the method provided by this application. The terms mentioned below can be referred to in the above description and will not be repeated below. Among them, Figure 10 describes the method for transmitting data packets in the uplink direction, and Figure 11 describes the method for transmitting data packets in the downlink direction.
[0163] FIG10 is a schematic flowchart of a communication method provided in an embodiment of the present application.
[0164] S1001: The terminal device generates uplink data of the first client application.
[0165] For example, the first client application generates uplink data to be sent and transmits the uplink data to the first function of the terminal device. It should be understood that since there is a one-to-one correspondence between client applications and server applications, the uplink data of the first client application also corresponds to the uplink data of the first server.
[0166] S1002: The terminal device sends a first data packet to the access network device via a first session. Correspondingly, the access network device receives the first data packet from the terminal device via the first session.
[0167] Exemplarily, the first function may encapsulate uplink data to be transmitted to generate a first data packet. The first function may also determine a first session through which the first data packet is transmitted. The first session is a session between the terminal device and the first node.
[0168] It is understood that the first session may include two communication links, one of which is a communication link between the terminal device and the access network device (such as a data radio bearer (DRB)), and the other is a communication link between the access network device and the first node (such as a tunnel). The first session is indicated by indication information of the first session, such as an identifier of the first session.
[0169] The content included in the first data packet is related to the manner in which the first function determines the session.
[0170] In a first possible implementation, the first function may determine a first session using the method shown in FIG5 , where the first session is used to carry data with the first server application. The first function may obtain a first mapping relationship between the first session and the first client application. The first data packet may include the uplink data.
[0171] For example, the first client application generates uplink data to be sent and passes the uplink data to the first function. The first function determines that the uplink data is sent through the first session based on the first mapping relationship, and encapsulates the uplink data based on the relevant information of the first session to generate a first data packet, and sends the first data packet through the bearer corresponding to the first session.
[0172] In a second possible implementation, the first function determines a first session in the manner shown in FIG7 , where the first session is used to carry data with at least one server application. The first function may obtain indication information of the first server application. The first data packet may include the indication information of the first server application and uplink data.
[0173] For example, the first client application generates uplink data to be sent, passes the uplink data to the first function, the first function obtains the indication information of the first server application, and encapsulates the uplink data based on the indication information of the first server application, such as adding the indication information of the first server application to generate a first data packet, and sends the first data packet through the first session.
[0174] S1003: The access network device sends a second data packet to the first node via the first session. Correspondingly, the first node receives the second data packet from the access network device via the first session.
[0175] The access network device may use multiple methods to generate the second data packet based on the received first data packet. In other words, the access network device may use multiple methods to route the uplink data to be sent.
[0176] In a first possible implementation, if the first function determines the first session in the manner shown in Figure 5, the first data packet is encapsulated based on the relevant information of the first session, and the access network device can generate a second data packet based on the relevant information of the first session, and map the second data packet to the tunnel corresponding to the first session. For example, the second data packet may include TEID and uplink data.
[0177] The first node can obtain a mapping relationship between the first server application and the first session, such as a mapping relationship between the first server application and the TEID in the first session. Thus, when the first node receives the second data packet, it can determine the first server application based on the TEID in the second data packet and transmit the uplink data in the second data packet to the first server application.
[0178] In a second possible implementation, if the first function determines the first session in the manner shown in Figure 7, the first data packet is encapsulated based on the indication information of the first server application, and the first data packet includes the indication information of the first server application and uplink data. The access network device can route the uplink data in the following two ways.
[0179] Method 1:
[0180] The access network device may not parse the indication information of the first server application; the indication information of the first server application may be encapsulated as part of the payload. The second data packet still contains the indication information of the first server application. Thus, upon receiving the second data packet, the first node may determine the first server application based on the indication information of the first server application in the second data packet and transmit the uplink data in the second data packet to the first server application.
[0181] Method 2:
[0182] The access network device can parse the indication information of the first server application in the first data packet. The access network device can obtain a second mapping relationship between the indication information of the first server application and the port information of the first server application. The access network device can perform encapsulation based on the port information of the first server application, such as writing the port number of the first server application into the destination port number of the UDP header. Thus, when the first node receives the second data packet, it can pass the uplink data in the second data packet to the first server application based on the port information of the first server application in the second data packet.
[0183] S1004: The first node processes uplink data through the first server application.
[0184] The first node may transmit the uplink data to the first server application for processing based on the indication information or port information of the first server application in the second data packet.
[0185] Based on the present technical solution, the terminal device has a first function, which can be used to serve the first client application, for example, to determine the first session corresponding to the first client application. The terminal device can send uplink data through the first session, so that the uplink data can be transmitted to the first node where the first server application is deployed through the first session without relying on the TCP\IP address protocol, thereby reducing transmission overhead.
[0186] The above describes a method in which a terminal device sends uplink data based on a first server application to a first node. To facilitate understanding of the embodiments of the present application, the following describes a method in which a first node sends downlink data based on a first server application to a terminal device.
[0187] FIG11 is a schematic flowchart of another communication method provided in an embodiment of the present application.
[0188] S1101: A first node generates downlink data corresponding to a first server application.
[0189] Exemplarily, the first server application runs to generate downlink data to be sent, and transmits the downlink data to a unit or module responsible for communication in the first node.
[0190] S1102: The first node sends a third data packet to the access network device via the first session. Correspondingly, the access network device receives the third data packet from the first node via the first session.
[0191] Exemplarily, the first node may encapsulate the downlink data to be sent to generate a third data packet. The first node may also determine a first session and send the first data packet through the first session. The first session is a session between the terminal device and the first node.
[0192] The content included in the third data packet is related to the type of the first session.
[0193] In a first possible implementation, as shown in Figure 5 , the first session is used to carry data with the first server application. The first node may obtain a third mapping relationship between the first session and the first server application, where the third data packet includes downlink data.
[0194] For example, the first server application generates downlink data to be sent, and the first node determines that the downlink data is sent through the first session based on the third mapping relationship, and encapsulates the downlink data based on the relevant information of the first session, such as adding TEID, to generate a third data packet, and sends the third data packet through the tunnel corresponding to the first session.
[0195] In a second possible implementation, as shown in Figures 7 and 8, the first session is used to carry data with at least one server application. The first node may obtain indication information of the first server application, and the third data packet includes the indication information of the first server application and downlink data.
[0196] For example, the first server application generates downlink data to be sent, and the first node encapsulates the downlink data based on the indication information of the first server application, such as adding the indication information of the first server application to generate a third data packet, and sends the third data packet through the first session.
[0197] In a third possible implementation, as shown in Figures 7 and 9, the first session is used to carry data related to at least one server application. The first node can obtain port information of the first server application, and the third data packet can include the port information of the first server application and the downlink data.
[0198] For example, the first server application generates downlink data to be sent, and the first node encapsulates the downlink data based on the port information of the first server application, such as adding the port number of the first server application to the source port field of the UDP header to generate a third data packet, and sends the third data packet through the first session.
[0199] S1103: The access network device sends a fourth data packet to the terminal device via the first session. Correspondingly, the terminal device receives the fourth data packet from the access network device via the first session.
[0200] The access network device may use multiple methods to generate the fourth data packet based on the received third data packet. In other words, the access network device may use multiple methods to route the downlink data to be sent.
[0201] In a first possible implementation, as shown in FIG5 , the third data packet is encapsulated based on the relevant information of the first session. The access network device can generate a fourth data packet based on the relevant information of the first session, and send the fourth data packet through the bearer corresponding to the first session. For example, the fourth data packet includes downlink data.
[0202] The first function can obtain a first mapping relationship between the first session and the first client application. Thus, the first function receives the fourth data packet through the first session, can determine the first client application based on the first session, and transmit the downlink data in the fourth data packet to the first client application.
[0203] In a second possible implementation, as shown in Figures 7 and 8 , the third data packet is encapsulated based on the indication information of the first server application. The third data packet contains the indication information of the first server application. The access network device may not parse the indication information of the first server application, and the indication information of the first server application may be encapsulated as part of the payload. The fourth data packet still contains the indication information of the first server application. Thus, when the first function receives the fourth data packet, it can determine the first client application based on the indication information of the first server application in the fourth data packet and pass the downlink data in the fourth data packet to the first client application.
[0204] In a third possible implementation, as shown in Figures 7 and 9, the third data packet is encapsulated based on the port information of the first server application, and the third data packet contains the port information of the first server application. The access network device can parse the port information of the first server application in the third data packet. The access network device can obtain a second mapping relationship between the indication information of the first server application and the port information of the first server application. The access network device can obtain the indication information of the first server application based on the second mapping relationship, reorganize the data based on the indication information of the first server application to generate a fourth data packet, such as adding the indication information of the first server application, and sending the fourth data packet through the first session. Thus, the first function receives the fourth data packet, can determine the first client application based on the indication information of the first server application in the fourth data packet, and pass the downlink data in the fourth data packet to the first client application.
[0205] S1104, the terminal device processes the downlink data through the first client application.
[0206] The first function may deliver the downlink data to the first client application based on the first session, or deliver the downlink data to the first client application for processing based on the indication information of the first server application in the fourth data packet.
[0207] The above describes a method for a first node to send downlink data based on a first server application to a terminal device. In the above-described method, if the access network device manages the first session using the method shown in Figure 9, the access network device manages the second mapping relationship between the indication information of the first server application and the port information of the first server application. To facilitate understanding of the embodiments of the present application, the following provides an exemplary description of how the access network device obtains the second mapping relationship.
[0208] FIG12 is a schematic flowchart of a method for an access network device to obtain a second mapping relationship according to an embodiment of the present application.
[0209] Optionally, in S1201, the second node sends a first message to the first node. Correspondingly, the first node receives the first message from the second node.
[0210] The first message may include indication information of the first server application. Exemplarily, the first message is used to request the first node to load the first server application, and the first message includes the first server application and indication information of the first server application. Exemplarily, the first message may be a loading request message, and the loading request message carries the first server application including the first server application (such as a program file) and indication information of the first server application. Thus, the first node can load the first server application based on the request of the first message, manage the indication information of the first server application, and deploy the first server application in the network.
[0211] The second node may be a node for managing the first node. For example, the second node may be a task control function (TCF).
[0212] Optionally, in S1202, the first node sends a second message to the second node. Correspondingly, the second node receives the second message from the first node.
[0213] The second message may include the port information of the first server application. For example, the first node may allocate a port for the first server application during the process of loading the first server application, and indicate the port information of the first server application to the second node via the second message, so that the second node can obtain the second mapping relationship between the indication information of the first server application and the port information of the first server application.
[0214] The second node obtains the second mapping relationship and may proactively send information indicating the second mapping relationship to the access network device. Alternatively, the second node may send information indicating the second mapping relationship to the access network device based on a request from the access network device. In this implementation, the access network device may perform the following step S1203.
[0215] Optionally, in S1203, the access network device sends a third message to the second node. Correspondingly, the second node receives the third message from the access network device.
[0216] The third message is used to request the second mapping relationship. Exemplarily, when the access network device receives a first data packet from the terminal device, the first data packet including indication information of the first server application, or receives a third data packet from the first node, the third data packet including port information of the first server application, it can send information requesting the second mapping relationship to the second node.
[0217] S1204: The second node sends information indicating the second mapping relationship to the access network device. Correspondingly, the access network device receives the information indicating the second mapping relationship from the second node.
[0218] It is understood that the second node may send information indicating the second mapping relationship to the access network device based on the request of the third message. Alternatively, after obtaining the second mapping relationship, the second node may proactively send the information indicating the second mapping relationship to the access network device. For example, the second node may broadcast the information indicating the second mapping relationship. Thus, the access network device can obtain the second mapping relationship and manage the context of the first session based on the second mapping relationship.
[0219] In some implementations, if the first client application of a terminal device is uninstalled, the terminal device may inform the first node that the first client application is uninstalled, and the first node may inform the second node that the first client application is uninstalled. If the first server application has a separate first session, the second node may delete the first session. If the first server application shares the first session with other server applications, the second node may notify the access network device to delete relevant information about the first server application, such as sending information to the access network device indicating the deletion of the second mapping relationship. This application does not specifically limit this.
[0220] In order to realize the various functions of the communication devices (such as the first node, the second node, the terminal device, etc.) in the embodiments of the present application, each communication device can realize the corresponding functions through hardware structure, software module, or hardware structure plus software module.
[0221] FIG13 shows a communication device 2000 provided in this application.
[0222] As shown in Figure 13, a communication device 2000 includes a processing module 2001 and a communication module 2002. The communication device 2000 can be a communication device, or a device applied to a communication device and capable of implementing the corresponding functions of the communication device, such as a chip, a chip system, or a circuit. For example, the communication device can include a first node (such as a TPF), an access network device, a terminal device, etc.
[0223] Among them, the communication module can also be called a transceiver module, a transceiver, a transceiver, or a transceiver device, etc. The processing module can also be called a processor, a processing board, a processing unit, or a processing device, etc. Optionally, the communication module is used to perform the sending operation and the receiving operation of the terminal device or the network device in any method embodiment. The device used to implement the receiving function in the communication module can be regarded as a receiving unit, and the device used to implement the sending function in the communication module can be regarded as a sending unit, that is, the communication module includes a receiving unit and a sending unit. The processing module is used to perform operations / processing related to the internal implementation of the terminal device or the network device in any method embodiment. It should be understood that the corresponding specific operations of each module can be found in the description of the method embodiment and will not be repeated here.
[0224] Furthermore, it should be noted that the aforementioned communication module and / or processing module may be implemented as a virtual module. For example, the processing module may be implemented as a software functional unit or a virtual device, and the communication module may be implemented as a software function or a virtual device. Alternatively, the processing module or the communication module may be implemented as a physical device. For example, if the device is implemented as a chip / hardware circuit, the communication module may be an input / output circuit and / or a communication interface that performs input operations (corresponding to the aforementioned receiving operations) and output operations (corresponding to the aforementioned sending operations); the processing module may be an integrated circuit or a logic circuit, etc.
[0225] The division of modules in this application is illustrative and represents only a logical functional division. In actual implementation, other division methods may be used. Furthermore, the functional modules in the examples of this application may be integrated into a single module, physically exist separately, or two or more modules may be integrated into a single module. The aforementioned integrated modules may be implemented in the form of hardware, software functional modules, or a combination of hardware and software functional modules, without limitation.
[0226] FIG14 is a communication device 2100 provided by the present application. Referring to FIG14 , the present application also provides a communication device 2100.
[0227] Optionally, the communication device 2100 may be a chip or a chip system. Optionally, in the present application, a chip system may be composed of a chip, or may include a chip and other discrete devices.
[0228] The communication device 2100 can be used to implement the functions of any network element (for example, a first node, an access network device, a terminal device, etc.) in the communication system described in the above examples. The communication device 2100 may include at least one processor 2110. Optionally, the processor 2110 (or processing device) is coupled to a memory, and the memory may be located within the communication device, or the memory may be integrated with the processor, or the memory may be located outside the communication device. For example, the communication device 2100 may also include at least one memory 2120. The memory 2120 stores the necessary computer programs, instructions and / or data for implementing any of the above embodiments; the processor 2110 may execute the computer programs, instructions and / or data stored in the memory 2120 to complete the corresponding functions of any network element in any of the above embodiments.
[0229] The communication device 2100 may also include a communication interface 2130, through which the communication device 2100 can exchange information with other devices. Exemplarily, the communication interface 2130 may be a transceiver, circuit, bus, module, pin, or other type of communication interface. When the communication device 2100 is a chip-type device or circuit, the communication interface 2130 in the device 2100 may also be an input / output circuit that can input information (or receive information) and / or output information (or send information). The processor may be an integrated circuit or a logic circuit, etc., and the processor may determine output information based on the input information.
[0230] Coupling in this application refers to an indirect coupling or communication connection between devices, units, or modules, which can be electrical, mechanical, or other forms, and is used for information exchange between devices, units, or modules. The processor 2110 may operate in conjunction with the memory 2120 and the communication interface 2130. The specific connection medium between the processor 2110, memory 2120, and communication interface 2130 is not limited in this application.
[0231] Optionally, the processor 2110, the memory 2120, and the communication interface 2130 are interconnected via a bus 2140. For ease of illustration, FIG14 shows only one line, but this does not mean that there is only one bus or one type of bus.
[0232] In this application, a processor may be a general-purpose processor, a digital signal processor, an application-specific integrated circuit, a field-programmable gate array or other programmable logic device, a discrete gate or transistor logic device, or a discrete hardware component, and may implement or execute the methods, steps, and logic block diagrams disclosed in this application. A general-purpose processor may be a microprocessor or any conventional processor. The steps of the methods disclosed in this application may be directly executed by a hardware processor, or by a combination of hardware and software modules within the processor.
[0233] In this application, the memory may be a non-volatile memory, such as a hard disk drive (HDD) or a solid-state drive (SSD), or a volatile memory, such as a random-access memory (RAM). The memory is any other medium that can be used to carry or store desired program code in the form of instructions or data structures and can be accessed by a computer, but is not limited thereto. The memory in this application may also be a circuit or any other device that can implement a storage function, for storing program instructions and / or data.
[0234] In addition, the present application provides a communication device comprising at least one processor, wherein the at least one processor is coupled to at least one memory, and the at least one processor is used to execute a computer program or instruction stored in the at least one memory so that the communication device has the functions of the corresponding network element (for example, a first node, an access network device, a terminal device, etc.) in any of the above embodiments.
[0235] The present application also provides a chip, including a processor and a communication interface, wherein the communication interface is used to receive information and / or data to be processed and send the information and / or data to be processed to the processor, and the processor is used to process the information and / or data to be processed, so that the communication device installed with the chip has the functions of the corresponding network element (for example, a first node, an access network device, a terminal device, etc.) in any of the above embodiments.
[0236] The present application also provides a computer-readable storage medium, which stores computer instructions. When the computer instructions are executed on a computer, the functions of the corresponding network elements (for example, the first node, access network equipment, terminal equipment, etc.) in any of the above embodiments are implemented.
[0237] The present application also provides a computer program product, which includes computer program code. When the computer program code runs on a computer, the functions of the corresponding network elements (for example, the first node, access network equipment, terminal equipment, etc.) in any of the above embodiments are implemented.
[0238] The present application also provides a wireless communication system, including one or more network elements in any of the above embodiments. Exemplarily, the communication system includes, for example, a first node, an access network device, a terminal device, and the like.
[0239] It should be understood that the processor mentioned in the embodiments of the present application may be a central processing unit (CPU), or may be other general-purpose processors, digital signal processors (DSP), application-specific integrated circuits (ASIC), field programmable gate arrays (FPGA) or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc. The general-purpose processor may be a microprocessor or any conventional processor, etc.
[0240] The memory mentioned in the embodiments of the present application may be a volatile memory and / or a non-volatile memory. Among them, the non-volatile memory may be a read-only memory (ROM), a programmable read-only memory (PROM), an erasable programmable read-only memory (EPROM), an electrically erasable programmable read-only memory (EEPROM) or a flash memory. The volatile memory may be a random access memory (RAM). For example, RAM can be used as an external cache. As an example and not a 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 link dynamic random access memory (SLDRAM) and direct rambus RAM (DR RAM). When the processor is a general-purpose processor, a DSP, an ASIC, an FPGA or other programmable logic device, a discrete gate or transistor logic device, or a discrete hardware component, the memory (storage module) may be integrated into the processor.
[0241] The technical solutions provided in this application can be implemented in whole or in part through software, hardware, firmware, or any combination thereof. When implemented using software, they can be implemented in whole or in part 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, the processes or functions described in this application are generated in whole or in part. The computer can be a general-purpose computer, a special-purpose computer, a computer network, a terminal device, an access network device, or other programmable device. 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, optical fiber, digital subscriber line (DSL)) or wireless (e.g., infrared, wireless, microwave, etc.) means. The computer-readable storage medium can be any available medium accessible by a computer or a data storage device such as a server or data center that integrates one or more available media. The available medium may be a magnetic medium (eg, a floppy disk, a hard disk, a magnetic tape), an optical medium (eg, a digital video disc (DVD)), or a semiconductor medium.
[0242] In this application, under the premise of no logical contradiction, the examples can reference each other, for example, the methods and / or terms between method embodiments can reference each other, for example, the functions and / or terms between device embodiments can reference each other, for example, the functions and / or terms between device examples and method examples can reference each other.
[0243] In the description of the embodiments of this application, "multiple" refers to two or more than two. Any embodiment or design described as "exemplarily" or "for example" in the embodiments of this application should not be interpreted as being more preferred or advantageous than other embodiments or designs. Specifically, the use of words such as "exemplary" or "for example" is intended to present the relevant concepts in a concrete manner to facilitate understanding.
[0244] In the description of the embodiments of the present application, unless otherwise specified, " / " indicates that the objects associated before and after are in an "or" relationship, for example, A / B can represent A or B; "and / or" in the present application is merely a description of the association relationship of associated objects, indicating that three relationships may exist, for example, A and / or B can represent: A exists alone, A and B exist at the same time, and B exists alone, where A and B can be singular or plural.
[0245] In various embodiments of the present application, the size of the serial numbers of the above-mentioned processes does not mean the order of execution. The execution order of each process should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of the embodiments of the present application.
[0246] Those skilled in the art will appreciate that the units and algorithm steps of each example described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are performed in hardware or software depends on the specific application and design constraints of the technical solution. Professional and technical personnel can use different methods to implement the described functions for each specific application, but such implementation should not be considered beyond the scope of this application.
[0247] Those skilled in the art will clearly understand that, for the convenience and brevity of description, the specific working processes of the systems, devices and units described above can refer to the corresponding processes in the aforementioned method embodiments and will not be repeated here.
[0248] In the several embodiments provided in this application, it should be understood that the disclosed systems, devices and methods can be implemented in other ways. For example, the device embodiments described above are merely schematic. For example, the division of the units is merely a logical function division. In actual implementation, there may be other division methods, such as multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. Another point is that the mutual coupling or direct coupling or communication connection shown or discussed can be through some interfaces, indirect coupling or communication connection of devices or units, which can be electrical, mechanical or other forms.
[0249] The units described as separate components may or may not be physically separate, and the components shown as units may or may not be physical units, that is, they may be located in one place or distributed across multiple network units. Some or all of these units may be selected to achieve the purpose of this embodiment according to actual needs.
[0250] In addition, each functional unit in each embodiment of the present application may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit.
[0251] If the functions are implemented in the form of software functional units and sold or used as independent products, they can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the present application, or the part that contributes to the prior art, or the part of the technical solution, can be embodied in the form of a software product. The computer software product is stored in a storage medium and includes several instructions for enabling a computer device (which can be a personal computer, a server, or a network device, etc.) to execute all or part of the steps of the method described in each embodiment of the present application. The aforementioned storage medium includes various media that can store program codes, such as a USB flash drive, a mobile hard disk, a read-only memory (ROM), a random access memory (RAM), a magnetic disk or an optical disk.
[0252] The above description is merely a specific embodiment of the present application, but the scope of protection of the present application is not limited thereto. Any changes or substitutions that can be easily conceived by a person skilled in the art within the technical scope disclosed in this application should be included in the scope of protection of this application. Therefore, the scope of protection of this application should be based on the scope of protection of the claims.
Claims
1. A method for data transmission, characterized in that: Applied to a terminal device, the method comprises: Generate uplink data of the first client application; A first data packet is sent through a first session, wherein the first data packet includes the uplink data, the first session is a session between the terminal device and a first node, the first node is used to load a first server application corresponding to the first client application, the first node is a core network element, and the first server application comes from a third-party system.
2. The method according to claim 1, characterized in that There is a first mapping relationship between the first session and the first client application.
3. The method according to claim 1 or 2, characterized in that The first node is used to load at least one server application, the first session is used to carry data of the first server application in the at least one server application, and the first client application corresponds to the first server application.
4. The method according to claim 1 or 2, characterized in that: The first node is used to load multiple server applications, the first session is used to carry data of the multiple server applications, and the first client application corresponds to one of the multiple server applications.
5. The method according to claim 4, characterized in that The first data packet includes indication information of the first server application.
6. The method according to any one of claims 1 to 5, characterized in that The first data packet does not include at least one of the following: a Transmission Control Protocol (TCP) address of the first node, an Internet Protocol (IP) address of the first node.
7. A method for data transmission, characterized in that: Applied to a first node, the first node is used to load a first server application, the first node is a core network element, and the first server application comes from a third-party system, the method comprising: receiving a second data packet through a first session, where the second data packet is generated based on a first data packet sent by a terminal device, where the first data packet includes uplink data of a first client application, where the first client application corresponds to the first server application, and where the first session is a session between the terminal device and the first node; The uplink data is processed by the first server application.
8. The method according to claim 7, characterized in that The first node is used to load at least one server application, the first session is used to carry data of the first server application in the at least one server application, and the first client application corresponds to the first server application.
9. The method according to claim 8, characterized in that The first node is used to load multiple server applications, the first session is used to carry data of the multiple server applications, and the first client application corresponds to one of the multiple server applications.
10. The method according to claim 9, characterized in that The first data packet includes indication information of the first server application.
11. The method according to claim 9 or 10, characterized in that The first data packet includes indication information of the first server application and the uplink data, and the second data packet includes indication information of the first server application and the uplink data.
12. The method according to claim 9 or 10, characterized in that The first data packet includes the indication information of the first server application and the uplink data, the second data packet includes the port information of the first server application and the uplink data, and the port information of the first server application and the indication information of the first server application have a second mapping relationship.
13. The method according to any one of claims 7 to 12, characterized in that The first data packet does not include at least one of the following: a Transmission Control Protocol (TCP) address of the first node, an Internet Protocol (IP) address of the first node.
14. A communication device, characterized in that: The method comprises a module or a unit for executing the method according to any one of claims 1 to 6, or a module or a unit for executing the method according to any one of claims 7 to 13.
15. A communication device, characterized in that: include: A processor, the processor being coupled to a memory, the processor being configured to execute a computer program or instruction stored in the memory so that the communication device performs the method according to any one of claims 1 to 6, or so that the communication device performs the method according to any one of claims 7 to 13.
16. A chip, characterized in that: It includes a processor and a communication interface, wherein the communication interface is used to receive information and / or data to be processed and send the information and / or data to be processed to the processor, and the processor is used to process the information and / or data to be processed, so that the communication device installed with the chip executes the method as described in any one of claims 1 to 6, or executes the method as described in any one of claims 7 to 13.
17. A computer-readable storage medium, characterized in that: The computer-readable storage medium stores computer instructions, and when the computer instructions are executed on a computer, the method according to any one of claims 1 to 6 is implemented, or the method according to any one of claims 7 to 13 is implemented.
18. A computer program product, characterized in that The computer program product comprises a computer program code, and when the computer program code is run on a computer, the method according to any one of claims 1 to 6 is implemented, or the method according to any one of claims 7 to 13 is implemented.
19. A wireless communication system, characterized in that: The invention comprises a communication device for executing the method according to any one of claims 1 to 6, and a communication device for executing the method according to any one of claims 7 to 13.
Citation Information
Patent Citations
Communication method, device and system
CN115996374A
Communication method, communication device and communication system
CN116614556A
Communication method and apparatus
WO2022082680A1
Communication method and communication apparatus
WO2023020046A1