Data transmission method, network device, terminal device, and server device

Abstract

A data transmission method, a network device, a terminal device, and a server device are provided. The data transmission method is applied to a network device that communicates with the terminal device and the server device. The data transmission method includes the steps of: receiving application data transmitted by the terminal device, the application data corresponding to a packet feature identifier (S100); determining a corresponding first packet instance of the network device based on the packet feature identifier, the different first packet instances corresponding to the different packet feature identifiers (S200); transmitting the application data to the first packet instance, and transmitting the application data of the first packet instance to a corresponding second packet instance of the server device (S300), the server device processes the application data, and the second packet instance and the first packet instance have a one-to-one correspondence.

Description

Technical Field

[0001] This application is filed based on the Chinese patent application with application number 202111130091.7 and filing date September 26, 2021, and claims the priority of the Chinese patent application. All the contents of the Chinese patent application are hereby incorporated into this application by reference.

[0002] This application relates to the field of communication technologies, and in particular, to a data transmission method, network devices, terminal devices, server devices, and computer-readable storage media.

Background Art

[0003] Massive Machine Type Communication (MMTC) is one of the three main 5G scenarios defined by the International Telecommunication Union (ITU). In particular, in applications such as smart cities, environmental monitoring, and smart agriculture, small data, low power consumption, and massive connections are the main features.

[0004] Since this is mainly used for wide-range data collection, terminal devices in this scenario often have the characteristics of a large number, a wide distribution range, and a small amount of data per transmission. Therefore, not only does the network need to support ultra-large-scale user connections, but it is also necessary to consider the power consumption and cost issues when using a large number of terminals.

[0005] However, in the current network configuration mode, since it is necessary to establish a bearer every time data is transmitted, the data transmission of terminal devices is inefficient and the introduction cost is also high. On the other hand, the data transmission is limited by the access processing ability of network-side devices, occupies a large amount of bandwidth resources, and the network introduction cost is high.

Summary of the Invention

Problems to be Solved by the Invention

[0006] This application aims to solve at least one of the technical problems existing in the prior art. To this end, this application proposes a data transmission method, a network device, a terminal device, a server device, and a computer-readable storage medium that can quickly collect data of a large number of terminal devices and reduce the introduction costs of the terminal devices and network-side devices.

Means for Solving the Problem

[0007] In a first aspect, an embodiment of this application provides a data transmission method applied to a network device. The network device communicates with a terminal device and a server device. The data transmission method includes receiving application data transmitted by the terminal device, where the application data corresponds to a packet feature identifier, determining a corresponding first packet instance of the network device based on the packet feature identifier, where different first packet instances correspond to different packet feature identifiers, transmitting the application data to the first packet instance, and transmitting the application data of the first packet instance to a corresponding second packet instance of the server device, where the server device processes the application data, and the second packet instance and the first packet instance correspond one-to-one.

[0008] In a second aspect, an embodiment of this application provides a data transmission method applied to a terminal device. The terminal device communicates with a server device via a network device. The data transmission method includes A step of transmitting application data corresponding to a packet feature identifier to the network device, wherein the network device determines a corresponding first packet instance of the network device based on the packet feature identifier, transmits the application data to the first packet instance, and the network device transmits the application data of the first packet instance to a corresponding second packet instance of the server device, the server device processes the application data, different first packet instances correspond to different packet feature identifiers, and the second packet instance and the first packet instance correspond one-to-one, including the step.

[0009] In a third aspect, an embodiment of the present application provides a data transmission method applied to a server device. The server device communicates with a terminal device via a network device. The data transmission method includes A step of receiving application data of a first packet instance from the network device, wherein the application data is transmitted by the terminal device and corresponds to a packet feature identifier, and different first packet instances correspond to different packet feature identifiers, and the step; A step of transmitting the application data to a second packet instance corresponding to the first packet instance and processing the application data, wherein the second packet instance and the first packet instance correspond one-to-one, including the step.

[0010] In a fourth aspect, an embodiment of the present application also provides a network device including a memory, a processor, and a computer program stored in the memory and executable by the processor, wherein the processor realizes the data transmission method described in any of the embodiments of the first aspect, providing a network device.

[0011] In a fifth aspect, an embodiment of the present application also provides a terminal device including a memory, a processor, and a computer program stored in the memory and executable by the processor, wherein the processor implements the data transmission method according to any one of the embodiments of the second aspect.

[0012] In a sixth aspect, an embodiment of the present application also provides a server device including a memory, a processor, and a computer program stored in the memory and executable by the processor, wherein when the processor executes the computer program, it implements the data transmission method according to any one of the embodiments of the third aspect.

[0013] In a seventh aspect, an embodiment of the present application also provides a computer-readable storage medium storing computer-executable instructions for causing a computer to execute the data transmission method according to any one of the embodiments of the first aspect or the second aspect.

[0014] Other features and advantages of the present application will be described in the following specification, become partially apparent from the specification, or be understood by practicing the present application. The objectives and other advantages of the present application can be achieved by the structures particularly pointed out in the specification, the claims, and the accompanying drawings.

[0015] Additional aspects and advantages of the present application will become apparent and easier to understand by referring to the description of the embodiments with reference to the following accompanying drawings.

Brief Description of the Drawings

[0016]

Figure 1

Figure 2

Figure 3

Figure 4

Figure 5

Figure 6

Figure 7

Figure 8

Figure 9

Figure 10

Figure 11

Figure 12

Figure 13

Figure 14

Figure 15

Figure 16

Figure 17

Figure 18

Embodiments for Carrying Out the Invention

[0017] To more clearly understand the object, technical solution and advantages of this application, the following will further elaborate on this application with reference to the drawings and embodiments. The specific embodiments described in this specification are only used to explain this application and are not used to limit this application.

[0018] Note that the functional module division is shown in the schematic diagram of the device, and the logical order is shown in the flowchart. However, in some cases, it may be different from the module division of the device, or the steps shown or described may be executed in an order different from that shown in the flowchart. Terms such as "first", "second", etc. in the specification, claims, or the above drawings are not used to explain a specific order or priority, but are used to distinguish similar objects.

[0019] Massive Machine Type Communication (MMTC) is one of the three main 5G scenarios defined by the International Telecommunication Union (ITU). Especially in applications such as smart cities, environmental monitoring, and smart agriculture, small data, low power consumption, and massive connections are the main features.

[0020] Since this is mainly used for wide - range data collection, terminal devices in this scenario often have the characteristics of a large number, a wide distribution range, and a small amount of data per transmission. Therefore, not only does the network need to support ultra - large - scale user connections, but it is also necessary to consider the power consumption and cost issues when using a large number of terminal devices.

[0021] However, in the current network configuration mode, since a bearer needs to be established every time a terminal device transmits data, when applied to this scenario, the following problems occur. 1) The amount of transmitted data is not proportional to the signaling data volume, and the transmission efficiency is poor. 2) There are limitations to the access processing capabilities of network-side devices, and the number of terminal device accesses during the same period is restricted. If one attempts to increase the number of terminal device accesses, the only way to increase system capacity is to add more network-side devices, which results in higher network introduction costs. 3) Since a bearer needs to be established each time a terminal device transmits data, the terminal device must support a complete protocol stack. This increases the complexity and power consumption of the terminal device's implementation, raising the introduction cost of a single terminal device. 4) Establishing a bearer requires a large amount of time-frequency resources for terminal devices. In scenarios with a large number of terminals introduced, network-side devices and terminal devices must support a large system bandwidth, posing higher requirements for spectrum resource applications and network optimization by devices.

[0022] Based on this, the present application proposes a data transmission method, network device, terminal device, server device, and computer-readable storage medium that can quickly collect data from a large number of terminal devices and reduce the introduction costs of terminal devices and network-side devices.

[0023] Hereinafter, with reference to the drawings, the embodiments of the present application will be further described.

[0024] As shown in FIG. 1, FIG. 1 is a schematic diagram of a system architecture platform for executing a data transmission method according to an embodiment of the present application.

[0025] In the example of FIG. 1, the system architecture platform includes a processor 200 and a memory 100. Here, the processor 200 and the memory 100 may be connected via a bus or other means. In FIG. 1, a connection via a bus is illustrated as an example.

[0026] Memory 100 can be used to store non - temporary computer - readable programs and non - temporary computer - executable programs as a non - temporary computer - readable storage medium. Further, memory 100 may include high - speed random - access memory 100, and may also include non - temporary memory 100 such as at least one magnetic disk memory 100, flash memory devices, or other non - temporary solid - state memory 100. In some embodiments, memory 100 may optionally include memory 100 that is remotely located with respect to processor 200, and these remote memories 100 may be connected to the system architecture platform via a network. Examples of the above - mentioned network include, but are not limited to, the Internet, corporate intranets, local area networks, mobile communication networks, and combinations thereof.

[0027] The system architecture platform may be applied to 5G communication network systems and subsequent evolving mobile communication network systems, etc., and this embodiment does not particularly limit this.

[0028] The system architecture platform shown in FIG. 1 does not constitute a limitation of the embodiments of the present application, and may include more or fewer components than shown in the figure, combine some components, or take different arrangements of components.

[0029] In the system architecture platform shown in FIG. 1, processor 200 can call the control program stored in memory 100 to execute the data transmission method.

[0030] Based on the hardware structure of the above - mentioned system architecture platform, various embodiments of the data transmission system of the present application are proposed.

[0031] Specifically, as shown in FIG. 2, the data transmission system includes, but is not limited to, a terminal device 300, a network device 400, and a server device 500. Here, the network device 400 and the terminal device 300 communicate with the server device 500, and the terminal device 300, the network device 400, and the server device 500 may all include a memory 100 and a processor 200 as shown in FIG. 1.

[0032] Note that the server device 500 may be physically independent of the network device 400, or the server device 500 and the network device 400 may be integrated, but the present embodiment does not limit this.

[0033] Based on the module hardware structure of the above data transmission system, various embodiments of the data transmission method according to the first aspect of the present application are proposed below.

[0034] As shown in FIG. 3, FIG. 3 is a flowchart of the steps of a data transmission method according to an embodiment of the present application. The data transmission method is applied to a data transmission system and includes, but is not limited to, the following steps S100, step S200, and step S300.

[0035] Step S100: Receive application data transmitted by the terminal device 300, and the application data corresponds to a packet feature identifier.

[0036] Note that the packet feature identifier is predefined by the user in the terminal device 300.

[0037] Note that the packet feature identifier is the one corresponding to the current application data among a plurality of packet feature identifiers.

[0038] Note that the packet feature identifier may be included in the application data, or may correspond to a preset packet relationship according to the time-frequency position at which the application data is transmitted, but the present embodiment does not limit this.

[0039] Step S200: Based on the packet feature identifier, determine the corresponding first packet instance of the network device 400. Different first packet instances correspond to different packet feature identifiers.

[0040] Note that the packet feature identifier has a one-to-one correspondence with the first packet instance, and the first packet instance corresponds to a common packet instance. Each first packet instance contains several groups of application data with the same packet feature identifier.

[0041] Step S300: Send the application data to the first packet instance, and send the application data of the first packet instance to the corresponding second packet instance of the server device 500. The server device 500 processes the application data, and the second packet instance and the first packet instance correspond one-to-one.

[0042] Note that different first packet instances correspond to different second packet instances, and the second packet instance also corresponds to a common packet instance. Specifically, the network device 400 sends several groups of application data corresponding to the same packet feature identifier included in the first packet instance to the same second packet instance of the server device 500.

[0043] Specifically, when the network device 400 receives the application data transmitted by the terminal device 300 in steps S100 to S300, it determines the corresponding first packet instance based on the packet feature identifier corresponding to the application data. Thereafter, the network device 400 transmits the application data to the first packet instance, and transmits the application data of the first packet instance to the corresponding second packet instance of the server device 500. The server device 500 processes the application data.

[0044] According to the technical solution of the embodiment of the present application, the data transmission method provides a completely new and rapid data collection method with a small amount of data for a single data source but a wide data source collection range. Based on the predefined classification, the network device 400 does not establish each data source and data collection entity, but establishes a common packet instance for each classification. Thereby, the instance maintenance amount of the network side device is greatly reduced, and the access processing ability of the network side device is improved.

[0045] On the other hand, instead of establishing an upper-layer bearer, the method realizes efficient data transmission by using a lower-layer physical random access channel. Thereby, the system complexity is simplified, the requirement for time-frequency resources due to system introduction is reduced, and an effective means for deploying a large number of sensors at low cost is provided. Since the data is reported at the random access stage, a large amount of time-frequency resources are not required to establish a bearer. Thereby, the network side device and the terminal device 300 can also support the introduction of a large number of terminal scenarios without requiring a large system bandwidth. This has important significance in the 5G era.

[0046] In addition, this method can be easily extended to an existing wireless network system and is easily compatible with existing network side devices, so that significant cost reduction and improvement of network introduction flexibility can be achieved.

[0047] As shown in FIG. 4, illustratively, before the above step S100, specifically, it includes, but is not limited to, one of the following steps S110 and S120.

[0048] Step S110: Obtain configuration information including a packet feature identifier, and generate a first packet instance that corresponds one-to-one to the packet feature identifier based on the configuration information.

[0049] Note that the configuration information includes a plurality of packet feature identifiers. The network device 400 generates a plurality of first packet instances that correspond one-to-one to each packet feature identifier based on the plurality of packet feature identifiers.

[0050] Step S120: Obtain instance information for representing a second packet instance of the server device 500, generate a first packet instance that corresponds one-to-one to the second packet instance based on the instance information, the second packet instance is generated by the server device 500 based on the packet feature identifier in the configuration information, and the second packet instance and the packet feature identifier correspond one-to-one.

[0051] Specifically, a first packet instance that corresponds one-to-one to the packet feature identifier is preset in the network device 400, and a second packet instance that corresponds one-to-one to the packet feature identifier is also preset in the server device 500. That is, the preset first packet instance and the second packet instance also correspond one-to-one. Therefore, when a first packet instance is preset in the network device 400, the user may preset the corresponding configuration information in the background, or generate it corresponding to the second packet instance configured in the server device 500, but this embodiment does not limit this.

[0052] As shown in FIG. 5, illustratively, the above step S100 specifically includes, but is not limited to, the following step S130.

[0053] Step S130: Receive the application data transmitted by the terminal device 300 through a physical random access process.

[0054] Specifically, the terminal device 300 transmits information to the network device 400 through the Early Data Transmission (EDT) technology, that is, the Physical Random Access Channel (PRACH). Thereby, application data can be transmitted without establishing a bearer between each terminal device 300 and the network device 400.

[0055] As shown in FIG. 6, exemplarily, the above step S130 specifically includes, but is not limited to, the following steps S131, S132, and S133.

[0056] Step S131: Receive the first information from the terminal device 300, and determine the packet feature identifier of the terminal device 300 based on the time-frequency position where the first information exists.

[0057] Step S132: Generate second information based on the time-frequency position, and transmit the second information to the terminal device 300. The second information is for representing the uplink grant data amount of the application data.

[0058] Step S133: When receiving the third information including the application data transmitted by the terminal device 300 based on the second information, generate fourth information based on the third information, and transmit the fourth information to the terminal device 300 so that the terminal device 300 enters the idle state. The fourth information is for representing that the network device 400 has successfully received the application data.

[0059] Specifically, data is quickly collected between the terminal device 300 and the network device 400 by means of the EDT technology. When the terminal device 300 needs to transmit application data, the terminal device 300 first transmits first information to the network device 400. Next, the network device 400 can quickly identify whether the application data transmitted by the terminal device 300 needs to be assigned to a first packet instance by determining the time-frequency position of the terminal device 300 in the physical random access channel based on the first information. Then, the network device 400 generates second information based on the first information according to the size of the data volume corresponding to different predefined data classifications, and transmits the second information to the terminal device 300, thereby specifying the uplink permission data volume of the application data. Thereafter, the terminal device 300 feeds back third information including the application data to the network device 400 according to the permission specification of the second information. When the network device 400 successfully receives the application data, the network device 400 generates fourth information based on the third information, and transmits the fourth information to the terminal device 300 so that the terminal device 300 enters the idle state, thereby shortening the EDT processing time and reducing the energy consumed by the terminal device 300.

[0060] As shown in FIG. 7, exemplarily, the above step S200 specifically includes, but is not limited to, the following step S210.

[0061] Step S210: When the time-frequency position corresponds to a preset time-frequency position, determine the corresponding first packet instance of the network device 400 based on the packet feature identifier.

[0062] Specifically, when the time-frequency position at which the terminal device 300 transmits the first information corresponds to a preset time-frequency position reserved by the network device 400, the first packet instance corresponding to the terminal device 300 is determined based on the packet feature identifier.

[0063] Note that different time-frequency positions may correspond to different preset time-frequency positions, and different preset time-frequency positions may correspond one-to-one to different first packet instances. Thereby, based on the time-frequency position at which the terminal device 300 transmits the first information, the first packet instance corresponding to the application data can be determined.

[0064] As shown in FIG. 8, exemplarily, after the above step S100, specifically, the following step S140 is included, but is not limited thereto.

[0065] Step S140: If the time-frequency position does not correspond to a preset time-frequency position, transmit the application data to the PDN device 600.

[0066] Specifically, when the time-frequency position at which the terminal device 300 transmits the first information does not correspond to the preset time-frequency position reserved by the network device 400, the application data of the terminal device 300 is transmitted to a public data network (PDN) device.

[0067] As shown in FIG. 9, exemplarily, the application data includes a terminal identity identifier corresponding one-to-one to the terminal device 300. After the above step S300, specifically, the following step S310 is included, but is not limited thereto.

[0068] Step S310: Transmit the application data to the first packet instance, transmit the application data of the first packet instance to the corresponding second packet instance of the server device 500, and the server device 500 analyzes the application data to obtain the terminal identity identifier, and based on the terminal identity identifier and the packet feature identifier information, determines the terminal device 300 corresponding to the application data.

[0069] Specifically, the network device 400 transmits the application data of the first packet instance to the second packet instance of the server device 500. After that, the server device 500 determines the terminal device 300 corresponding to the application data based on the terminal identity identifier that corresponds one-to-one to the terminal device 300 included in the application data, and collects these application data. Thereby, the application data and the terminal device 300 can be accurately associated with each other, and the introduction cost for each terminal device 300 can be reduced.

[0070] Based on the module hardware structure of the above data transmission system and the data transmission method of the embodiment of the first aspect, various embodiments of the data transmission method of the second aspect of the present application are proposed below.

[0071] As shown in FIG. 10, FIG. 10 is a flowchart of steps of a data transmission method according to another embodiment of the present application. The data transmission method is applied to a data transmission system and includes, but is not limited to, the following step S400.

[0072] Step S400: Transmit the application data corresponding to the packet feature identifier to the network device 400. The network device 400 determines the corresponding first packet instance of the network device 400 based on the packet feature identifier, transmits the application data to the first packet instance, and the network device 400 transmits the application data of the first packet instance to the corresponding second packet instance of the server device 500. The server device 500 processes the application data. Different first packet instances correspond to different packet feature identifiers, and the second packet instance and the first packet instance correspond one-to-one.

[0073] Specifically, the terminal device 300 transmits application data corresponding to the packet feature identifier to the network device 400. The network device 400 determines the corresponding first packet instance based on the packet feature identifier, transmits the application data to the first packet instance, and the network device 400 transmits the application data of the first packet instance to the corresponding second packet instance of the server device 500, and the server device 500 processes the application data.

[0074] According to the technical solution of the embodiment of the present application, instead of establishing a bearer between each terminal device 300 and the network-side device, a common packet instance can be used, thereby quickly collecting data of a large number of terminal devices 300 and reducing the introduction cost of the terminal devices 300 and the network-side devices.

[0075] As shown in FIG. 11, exemplarily, the above step S400 specifically includes, but is not limited to, the following step S410.

[0076] Step S410: Transmit the application data corresponding to the packet feature identifier to the network device 400 by means of a physical random access process.

[0077] Specifically, the terminal device 300 transmits information to the network device 400 by means of the EDT technology, that is, the physical random access channel. Thereby, the application data can be transmitted without establishing a bearer between each terminal device 300 and the network device 400.

[0078] As shown in FIG. 12, exemplarily, the above step S410 specifically includes, but is not limited to, the following steps S411, S412, S413, and S414.

[0079] Step S411: Transmit the first information to the network device 400. The first information is for determining the time-frequency position of the terminal device 300 in the physical random access channel, and the time-frequency position is for determining the packet characteristic identifier of the terminal device 300.

[0080] Step S412: Receive the second information fed back by the network device 400 based on the first information. The second information represents the uplink grant data volume of the application data.

[0081] Step S413: Transmit the third information including the application data to the network device 400 based on the second information.

[0082] Step S414: Receive the fourth information fed back by the network device 400 based on the third information, and transition to the idle state according to the fourth information. The fourth information represents that the network device 400 has received the application data normally.

[0083] Specifically, data is quickly collected between the terminal device 300 and the network device 400 by means of EDT technology. When the terminal device 300 needs to transmit application data, the terminal device 300 first transmits first information to the network device 400. Next, the network device 400 can quickly identify whether the application data transmitted by the terminal device 300 needs to be transmitted to the first packet instance by determining the time-frequency position of the terminal device 300 in the physical random access channel based on the first information. Then, the network device 400 generates second information based on the first information according to the size of the data volume corresponding to different predefined data classifications, and transmits the second information to the terminal device 300, thereby specifying the uplink permission data volume of the application data. Thereafter, the terminal device 300 transmits third information including the application data to the network device 400 according to the permission specification of the second information. When the network device 400 successfully receives the application data, the network device 400 generates fourth information based on the third information and transmits the fourth information to the terminal device 300. The terminal device 300 enters an idle state based on the fourth information.

[0084] As shown in FIG. 13, exemplarily, the application data includes a terminal identity identifier that corresponds one-to-one to the terminal device 300. Specifically, the step S400 includes, but is not limited to, the following step S420.

[0085] Step S420: Transmit the application data corresponding to the packet feature identifier to the network device 400. The network device 400 determines the corresponding first packet instance of the network device 400 based on the packet feature identifier, transmits the application data to the first packet instance, and the network device 400 transmits the application data of the first packet instance to the corresponding second packet instance of the server device 500. The server device 500 analyzes to obtain the terminal identity identifier, and determines the terminal device 300 corresponding to the application data based on the terminal identity identifier and the packet feature identifier.

[0086] Specifically, the terminal device 300 transmits the application data corresponding to the packet feature identifier to the network device 400. Thereafter, the network device 400 transmits the application data of the first packet instance to the second packet instance of the server device 500. Then, the server device 500 determines the terminal device 300 corresponding to the application data based on the terminal identity identifier that corresponds one-to-one to the terminal device 300 included in the application data, and collects these application data. Thereby, the application data and the terminal device 300 can be accurately associated, and the introduction cost of the terminal device 300 alone can be reduced.

[0087] Based on the module hardware structure of the above data transmission system and the data transmission methods of the examples of the first aspect and the second aspect, various examples of the data transmission method of the third aspect of the present application are proposed below.

[0088] As shown in FIG. 14, FIG. 14 is a flowchart of the steps of a data transmission method according to another embodiment of the present application. The data transmission method is applied to a data transmission system and includes, but is not limited to, the following steps S500 and S600.

[0089] Step S500: Receive the application data of the first packet instance from the network device 400. The application data is sent by the terminal device 300, corresponds to the packet feature identifier, and different first packet instances correspond to different packet feature identifiers.

[0090] Step S600: Send the application data to the second packet instance corresponding to the first packet instance, process the application data, and the second packet instance and the first packet instance correspond one-to-one.

[0091] Specifically, the server device 500 receives the application data of the first packet instance from the network device 400. Since these application data correspond to the packet feature identifier, the server device 500 sends these application data to the second packet instance of the server device 500 corresponding to the first packet instance based on the packet feature identifier, and then processes these application data.

[0092] According to the technical solution of the embodiment of the present application, instead of establishing a bearer between each terminal device 300 and the network side device, a common packet instance can be used, thereby quickly collecting a large amount of data of the terminal devices 300 and reducing the introduction cost of the terminal devices 300 and the network side devices.

[0093] As shown in FIG. 15, exemplarily, the application data includes a terminal identity identifier that corresponds one-to-one to the terminal device 300. Step S600 specifically includes, but is not limited to, the following steps S610 and S620.

[0094] Step S610: Analyze the application data to obtain the terminal identity identifier.

[0095] Step S620: Determine the terminal device 300 corresponding to the application data based on the terminal identity identifier and the packet feature identifier.

[0096] Specifically, the server device 500 determines the terminal device 300 corresponding to the application data based on the terminal identity identifier that corresponds one-to-one to the terminal device 300 included in the application data, and collects these application data. Thereby, the application data and the terminal device 300 can be accurately associated, and the introduction cost of a single terminal device 300 can be reduced.

[0097] Based on the data transmission methods of the above-mentioned first aspect, second aspect, and third aspect of the embodiments, hereinafter, an overall embodiment of the data transmission method of the present application is proposed.

[0098] As shown in FIGS. 2 and 16, the data transmission method is applied to a data transmission system. Specifically, the data transmission method includes, but is not limited to, the following steps C110 to C160.

[0099] Step C110: Define in advance the packet type of the application data.

[0100] Specifically, classify and define in advance the application data that needs to be collected and reported into a plurality of classes, such as whether the type of temperature data to be collected is A, whether the type of pressure data to be collected is B, whether the type of speed information to be collected is C, etc., but this embodiment is not limited thereto.

[0101] Each dedicated terminal initially predefines one class or multiple classes of application data to be collected, and maps the data of each class to a set of protocol stack predefined parameters such as protocol stack X corresponding to class A data, protocol stack Y corresponding to class B data, and protocol stack Z corresponding to class C data. However, this embodiment is not limited thereto. In the case of a wireless system, the protocol stack includes a physical resource preset definition that is not limited to the broadcast of a network cell.

[0102] The network device 400 adds corresponding first packet instances such as I / II / III according to the type of application data such as A / B / C. Also, the server device 500 adds second packet instances such as I / II / III according to the type of data such as A / B / C.

[0103] Step C120: The terminal device 300 packages and transmits the application data.

[0104] Specifically, when the application data has not been transmitted, the terminal device 300 enters a sleep state released from the network. When there is application data that needs to be reported, the terminal device 300 uses the data obtained by adding its own terminal identity identifier UE ID to the application data that needs to be reported as the data entity that requires transmission. Then, the terminal device 300 reads the system broadcast and reports the application data corresponding to the packet feature identifier to the network device 400.

[0105] Step C130: The network device 400 collects data based on the packet feature identifier.

[0106] Specifically, regarding the interaction between the dedicated terminal and the network device 400, the application data reported by each dedicated terminal at a time must belong to the same class of application data. The network device 400 can identify the application data reported by all terminal devices 300 at a time as different packets based on the packet feature data in the application data, and put them into the corresponding first packet instance for processing.

[0107] Step C140: The network device 400 reports the application data to the server device 500.

[0108] Specifically, the network device 400 does not need to analyze the application data collected in the first packet instance, nor does it need to know a specific UE ID. It directly reports the application data to the server device 500 according to the packet granularity.

[0109] Step C150: The server device 500 processes the application data sent by the network device 400.

[0110] Specifically, the server device 500 assigns the data reported by the network device 400 to the corresponding second packet instance according to the packet feature identifier. Next, the packet processing unit corresponding to each second packet instance further analyzes the content of the application data to obtain the UE ID and specific data in the application data, and determines the application data reported by the terminal device 300 of each UE ID.

[0111] Note that the network device 400 can support both dedicated terminals and normal terminals. Specifically, a normal terminal acquires information from the system broadcast of the network device 400 and determines the time-frequency position in an initial radio resource such as a PRACH. On the other hand, for the initial radio resource of a dedicated terminal, different radio resources are defined in advance according to different application data packet mappings. Since this type of radio resource is different from the radio resource in the system broadcast, any packet type of the application data preset by the dedicated terminal has corresponding radio resource information. Thereby, in the first information in which the terminal device 300 and the network device 400 interact, the network device 400 can quickly distinguish between a dedicated terminal and a normal terminal according to the radio resource information used by the terminal device 300 to transmit information.

[0112] Between the dedicated terminal and the network device 400, data is collected quickly and efficiently by the EDT method. Specifically, the dedicated terminal is initially in an idle state and is activated when it is necessary to transmit data such as periodic or events defined by the network device 400. The dedicated terminal transmits the first information to the PRACH from the corresponding radio resource according to the preset packet type and the corresponding radio resource information. This is the first message in which the corresponding terminal device 300 and the network device 400 interact, and the radio universal tag is MSG1. The network device 400 can quickly identify whether it is a dedicated terminal from the time-frequency position of the PRACH resource, and can quickly determine the data classification that the dedicated terminal needs to report for quick processing. Thereafter, the network device 400 distributes the second information based on the size of the data volume corresponding to the predefined classification of different application data. This is the second message in which the corresponding terminal device 300 and the network device 400 interact, the radio universal tag is MSG2, and it is used to determine the size of the uplink permission data volume of the third information. Thereafter, the dedicated terminal transmits the third message according to the permission designation of MSG2. This is the third message in which the corresponding terminal device 300 and the network device 400 interact, and the radio universal tag is MSG3. This message includes the first upper layer signaling for the standard protocol. The content size that the third message may have may be set to be larger than the included upper layer signaling by X Bytes, or may be controlled by the uplink permission size indicated in MSG2 distributed by the network device 400, so this part of the resource may include the application data that the dedicated terminal needs to transmit. Next, the network device 400 needs to transmit the fourth information to the terminal device 300. This is the fourth message in which the corresponding terminal device 300 and the network device 400 interact, and the radio universal tag is MSG4.This fourth piece of information may feedback whether the terminal device 300 has won the competition and survived. In the case of a UE that has not survived, it will rise again to send uplink data after a certain period of time. In order to ensure that the retransmitted data is timely distributed to the network device 400, the retransmission of the selected PRACH resource may be further specially defined.

[0113] In addition, when a dedicated terminal reports application data using the EDT technology, after the reporting of the application data is completed, the terminal device 300 receives the MSG4 confirmation sent by the network device 400. After that, the terminal does not need to use the upper layer timer like a normal terminal and enters the idle state again. In this way, for a dedicated terminal, only the EDT process requires the transmission of uplink information and the listening of the downlink. Since the EDT process time is short, the energy consumption is low, and the power consumption of the terminal device 300 can be significantly reduced.

[0114] According to the technical solution of the embodiment of the present application, first, the capacity of the cell can be greatly increased, that is, more terminal numbers can be supported with the same coverage. In particular, in a scenario of large-scale connection with particularly low power consumption, by using the method of establishing a packet instance between the packet of the terminal device 300 and the base station, the network will be able to support more than 10 billion connections. Thereby, the introduction number of the network device 400 can be reduced and the cost can be lowered. On the other hand, since the terminal device 300 does not need to establish a bearer every time it transmits data, the uplink data transmission can be completed before the protocol stack is completed, thereby making the network introduction easier and reducing the power consumption. Next, by realizing the early transmission of uplink data through the random access process, the transmission efficiency can be greatly improved. For application scenarios targeting sensing and data collection, this method can transmit small data packets to the upper layer faster and improve the efficiency. Furthermore, in the present application, it does not require the support of additional devices, has good compatibility with the existing system, and has a low introduction cost. With the increase in the support ability of the terminal device 300, there is no need to add network-side devices either. Also, the reduction of the costs of the terminal device 300 and the network-side devices is more advantageous for the future of its application. Finally, the present application does not require support by a large bandwidth. Since the application data is reported at the random access stage, there is no need to use a large amount of time-frequency resources for bearer establishment, and neither the network-side device nor the terminal device 300 requires a large system bandwidth to support the introduction of a large number of terminal device 300 scenarios. This method can effectively save precious time-frequency resources and has important significance in the 5G era.

[0115] In order to describe the data identification method according to the present application in more detail, the technical solution of the present application will be described below with three specific examples.

[0116] Example 1 As shown in FIG. 17, FIG. 17 is a diagram showing that the network device 400 of the data transmission method according to another embodiment of the present application corresponds to and identifies the radio resources of dedicated terminals and normal terminals. In this data transmission method, the specific method by which the network device 400 corresponds to both dedicated terminals and normal terminals is as follows, taking the 5G network as an example.

[0117] Step C210: First, assume that the original network device 400 has a 10M bandwidth cell and a 15KHz subcarrier spacing. The network device 400 normally transmits the original system broadcast. The normal terminal determines the time domain information of the PRACH transmission (for example, when it is 16, the corresponding time domain corresponds to the first slot in 10 ms and lasts for 1 slot) according to the prach-ConfigurationIndex in the system broadcast. The normal terminal determines the time domain information of the PRACH transmission (for example, the 42nd RB) according to the msg1-FrequencyStart in the system broadcast. The normal terminal determines the range of the preamble value of the PRACH transmission (for example, 0 to 55) according to the totalNumberOfRA-Preambles in the system broadcast.

[0118] Step C220: Next, determine the application data classification reported from the dedicated terminal (for example, two classes: class A temperature information / class B pressure information). Set in advance so that application data classes A and B map the resources in the PRACH transmission time domain and frequency domain, and take values different from those in the system broadcast (for example, the period is 10 slots, the start slots are 2 and 7 respectively, it lasts for 2 slots, and the number of resource blocks (RBs) in the frequency domain is 4 for both). The preambles used for the PRACH mapped by classes A and B take the same values (0 to 55) as the range in the system broadcast. Denote the amount of data reported from the terminal each time as M bytes and N bytes for classes A and B respectively. When there are currently dedicated terminal devices 3001 to 3, the dedicated terminal device 1 is preset to report only data class A, the dedicated terminal device 2 is preset to report only two types (time division) of data classes A and B, and the dedicated terminal device 3 is preset to report only data class B.

[0119] Step C230: If the terminal device 300 is a dedicated terminal, at a certain point, assume that the upper layer of the dedicated terminal 2 reports application layer data (new transmission data), and the application data belongs to class B. In that case, the dedicated terminal 2 realizes the application data to be reported with a length of N by adding the unique UE ID of the dedicated terminal 2 and padding before the reported application data. Then, since it is new transmission data, the dedicated terminal 2 selects a preamble (for example, 0) from within the broadcast preamble range (0 to 55), the time domain period is 10 slots, the time domain starts from the 7th slot, it lasts for 2 slots, and the radio resources with the frequency domain RB starting at 4, and transmits a PRACH.

[0120] Step C240: When the terminal device 300 is a normal terminal, when the network device 400 performs uplink PUSCH scheduling for the normal terminal, it avoids using the RB4 - 9 resources in slot2 / 6 that are used by the dedicated terminal to transmit PRACH as specified in the EDT process of the dedicated terminal. When the network device 400 receives the PRACH of the dedicated terminal 2 at slot7 and frequency region RB start 4, the network device 400 can quickly grasp that the current dedicated terminal is accessing and that the current dedicated terminal belongs to class B, and perform subsequent processing flows of interacting with the dedicated terminal to collect class B data.

[0121] Example 2 As shown in FIG. 18, FIG. 18 is a diagram showing the process of the early data transmission (EDT) technology of the data transmission method according to another embodiment of the present application. The EDT process of the terminal device 300 in the data transmission method is specifically as follows, taking the 5G network as an example.

[0122] Step C310: At a certain point in time, the dedicated terminal 2 reports application layer data at the upper layer (if it is new transmission data or retransmission data that has failed in wireless transmission, it directly proceeds to step C360), and if the application data belongs to class B, the dedicated terminal 2 adds its unique UE ID and padding of the dedicated terminal 2 in front of the reported application data to form reported data with a length of N.

[0123] Step C320: The dedicated terminal 2 reads the cell synchronization and broadcast information of the current coverage area to obtain the strongest signal cell information (alternatively, the terminal device 300 pre - sets the access cell list information and preferentially selects the corresponding cell). The dedicated terminal 2 obtains the broadcast information of the selected cell and obtains the radio resources including the broadcast preamble range (for example, the preamble range 0 - 55 of the cell broadcast, and reserves the remaining 55 - 63 for retransmission), and also divides the RA - RNTI into the normal transmission and the reserved part.

[0124] Step C330: Based on the new transmission data, the dedicated terminal 2 selects a preamble (e.g., 0) within the broadcast preamble range (0 to 55), selects a normal transmission RA-RNTI, selects a radio resource corresponding to application data class B (e.g., slot 7, radio resource at the start of RB 4 in the frequency domain), and transmits the PRACH.

[0125] Step C340: When the network device 400 receives the PRACH of the dedicated terminal 2 at slot 7 and frequency domain RB start 4, it determines that the current dedicated terminal belongs to class B and uses the first packet instance II (corresponding to class B) to interact with the UE. Then, based on the preset grant size N Bytes corresponding to application data class B, it feeds back MSG2 to the dedicated terminal, indicating the uplink granted data amount of the corresponding size. The grant size excluding the upper layer signaling occupation length is at least greater than N.

[0126] Step C350: After the dedicated terminal 2 receives the uplink grant, the dedicated terminal 2 includes a C-RNTI MAC Control Element containing the UE's unique flag (C-RNTI) in MSG3. Because the collision has not yet been resolved at this point, MSG3 scrambles it using the TC-RNTI. In addition to the fixed content of MSG3, the N bytes added to the size of the uplink grant data amount can be used by the dedicated terminal 2 to fill in the reporting application data.

[0127] Step C360: After receiving MSG3 reported from the dedicated terminal, if another dedicated terminal (such as dedicated terminal 3) and dedicated terminal 2 simultaneously report MSG3 using the same resource, network device 400 includes this unique flag in the Msg4 message to identify the surviving dedicated terminal. If dedicated terminal 2 is the surviving dedicated terminal, proceed to step C370; if not, proceed to step C380.

[0128] Step C370: If dedicated terminal 2 survives the collision resolution, MSG4 of network device 400 indicates that dedicated terminal 2 has survived by putting the N bytes of application data included in MSG3 into the first packet instance II of network device 400 and processing them uniformly.

[0129] Step C380: If the dedicated terminal 2 fails to resolve the collision in step C240, the process proceeds to retransmission flow C290.

[0130] Step C390: First, different retransmission intervals and retransmission counts are adopted for different packet data types (for example, for Class A temperature information, the retransmission interval is 10 ms and the count is 3, and for Class B temperature information, the retransmission interval is 20 ms and the count is 5). For example, when the dedicated terminal 2 retransmits Class B application data, after the dedicated terminal 2 fails to retransmit three times, in order to prevent the dedicated terminal 2 from failing to resolve collisions each time, a preamble that is not specified for system broadcast in step C260 (in Example 1, 55 to 63 are not used) may be used, or a reserved preamble may be specially specified, such as 60. When the network device 400 makes another random access, if it finds that there is a dedicated terminal access with a preamble of 60 (within the reserved range of 55 to 63) and a reserved RA-RNTI, it prioritizes the success of this special priority collision resolution. In a collision resolution process, if the preambles of multiple terminals are within the reserved range of 55 to 63, one of them will be randomly selected as the terminal that successfully resolved the collision, and the other terminals that failed to resolve the collision will again select preamble access within the reserved range, and when the number of retransmissions of such data transmission is reached, the transmission will be abandoned.

[0131] Example 3 The specific flow of application data classification definition and data collection and reporting in this data transmission method is as follows:

[0132] Step C310: According to the needs of the actual network deployment, check the application data that needs to be collected from the dedicated terminal, and classify the application data, such as two types including temperature information data type A / pressure information data type B.

[0133] Step C320: According to the classification defined in Step C310, confirm that for various types of application data collected by the network device 400, there is a set of specific radio protocol stack resources (different from the preset specific values and the values of the radio resources set by the cell for general users through broadcast). The preset radio resource information includes, but is not limited to, PRACH time-frequency domain code resources, MSG2 / MSG3 allocation time-frequency resources and grant resources, as well as the number of retransmissions after random access collision and the physical resources for retransmission. For example, for data type A, radio resource X is preset, and for data type B, radio resource Y is preset.

[0134] Step C330: According to the classification of the application data determined in Step C310, define the respective data aggregation applications and analysis methods, including setting the data aggregation method for each application data on the network device 400 and setting the analysis method for each application data on the server device 500. For example, data types A and B adopt their respective data aggregation and analysis methods.

[0135] Step C340: When initialized, the network device 400 interacts with the server device 500 to obtain the classification information of the application data and obtain the corresponding radio resource information. The network device 400 may directly arrange the radio resource information of the corresponding packet on the network management of the network device 400.

[0136] Step C350: The network device 400 collects application data in the method of Example 1 or Example 2 according to the packet feature identifier by the first packet instance.

[0137] Step C360: The first packet instance of the network device 400 aggregates the collected application data in the corresponding aggregation method on the packet, and after aggregation, reports the application data to the corresponding second packet instance of the server device 500.

[0138] Step C370: The server device 500 then analyzes the instance processing according to a predefined analysis method. As one method, the second packet instance of the server device 500 further analyzes the collected data according to the data length (for example, N) defined on the packet, and analyzes the UE ID and application data to which the data belongs. Thereby, the data for each report of each UE ID can be accurately determined.

[0139] Based on the data transmission methods of the above-mentioned first aspect, second aspect, and third aspect of the embodiments, hereinafter, each embodiment of the network device 400 of the fourth aspect, the terminal device 300 of the fifth aspect, the server device 500 of the sixth aspect, and the computer-readable storage medium of the seventh aspect is proposed.

[0140] In the fourth aspect, an embodiment of the present application provides a network device 400 including a memory 100, a processor 200, and a computer program stored in the memory 100 and executable by the processor 200.

[0141] The processor 200 and the memory 100 may be connected via a bus or other means.

[0142] Note that the network device 400 in this embodiment includes the memory 100 and the processor 200 in the embodiment shown in FIG. 1, and can constitute a part of the system architecture platform in the embodiment shown in FIG. 1. Since both belong to the same inventive concept, they have the same realization principle and beneficial effects, which will not be described in detail here.

[0143] The non-temporary software programs and instructions necessary to implement the data transmission method of the above embodiment are stored in the memory 100 and executed by the processor 200, so that the data transmission method of the embodiment of the first aspect above, for example, the method steps S100 to S300 in FIG. 3 above, the method steps S110 to S120 in FIG. 4, the method step S130 in FIG. 5, the method steps S131 to S133 in FIG. 6, the method step S210 in FIG. 7, the method step S140 in FIG. 8, and the method step S310 in FIG. 9 are executed.

[0144] Note that since the network device 400 in the embodiment of the fourth aspect of the present application executes the data transmission method including any of the above embodiments of the first aspect, the specific implementation forms and technical effects of the network device 400 in the embodiment of the fourth aspect of the present application can refer to the specific implementation forms and technical effects of the data transmission method of any of the above embodiments of the first aspect, which will not be described in detail here.

[0145] The device embodiments described above are merely schematic. The units described as separate components may or may not be physically separated. That is, they may be arranged in one place or distributed among multiple network units. Some or all of these modules may be selected according to actual needs to achieve the purpose of the embodiment of this aspect.

[0146] In the fifth aspect, an embodiment of the present application provides a terminal device 300 including a memory 100, a processor 200, and a computer program stored in the memory 100 and executable by the processor 200.

[0147] The processor 200 and the memory 100 may be connected via a bus or other means.

[0148] Note that the terminal device 300 in this embodiment includes the memory 100 and the processor 200 in the embodiment shown in FIG. 1, and can constitute a part of the system architecture platform in the embodiment shown in FIG. 1. Since both belong to the same inventive concept, they have the same realization principle and beneficial effects, which will not be described in detail here.

[0149] The non-temporary software programs and instructions necessary to implement the data transmission method of the above embodiment are stored in the memory 100 and, when executed by the processor 200, the data transmission method of the embodiment of the second aspect above, for example, the method steps S400 in FIG. 10 above, the method steps S410 in FIG. 11, the method steps S411 - S413 in FIG. 12, and the method steps S420 in FIG. 13 are executed.

[0150] Note that since the terminal device 300 in the fifth aspect of the present application executes the data transmission method including any of the above embodiments of the second aspect, the specific embodiments and technical effects of the terminal device 300 in the fifth aspect of the present application can refer to the specific embodiments and technical effects of the data transmission method of any of the above embodiments of the second aspect, which will not be described in detail here.

[0151] The device embodiments described above are merely schematic. The units described as separate components may or may not be physically separated. That is, they may be arranged in one place or distributed among multiple network units. Some or all of these modules may be selected according to actual needs to achieve the purpose of this embodiment.

[0152] In a sixth aspect, an embodiment of the present application provides a terminal device 300 including a memory 100, a processor 200, and a computer program stored in the memory 100 and executable by the processor 200.

[0153] The processor 200 and the memory 100 may be connected via a bus or other means.

[0154] It should be noted that the terminal device 300 in this embodiment includes the memory 100 and processor 200 in the embodiment shown in FIG. 1, and can form part of the system architecture platform in the embodiment shown in FIG. 1. Since both belong to the same inventive concept, they have the same realization principles and beneficial effects, but will not be described in detail here.

[0155] The non-transitory software programs and instructions required to implement the data transmission method of the above embodiment are stored in memory 100 and executed by processor 200 to perform the data transmission method of the above third aspect embodiment, for example, method steps S500 to S600 of Figure 14 and method steps S610 to S620 of Figure 15 above.

[0156] In addition, since the terminal device 300 according to the embodiment of the sixth aspect of the present application executes a data transmission method including any of the embodiments of the third aspect described above, the specific embodiments and technical effects of the terminal device 300 according to the embodiment of the sixth aspect of the present application may refer to the specific embodiments and technical effects of the data transmission method according to any of the embodiments of the third aspect described above, and will not be described in detail here.

[0157] The above-described device embodiments are merely schematic. The units described as separate components may or may not be physically separated, i.e., they may be located in one place or distributed across multiple network units. Some or all of these modules may be selected to achieve the objectives of the present embodiment according to actual needs.

[0158] Furthermore, one embodiment of the present application provides a computer-readable storage medium storing computer-executable instructions. The computer-executable instructions are for executing the above data transmission method, for example, the method steps S100 to S300 in FIG. 3, the method steps S110 to S120 in FIG. 4, the method step S130 in FIG. 5, the method steps S131 to S133 in FIG. 6, the method step S210 in FIG. 7, the method step S140 in FIG. 8, the method step S310 in FIG. 9, the method step S400 in FIG. 10, the method step S410 in FIG. 11, the method steps S411 to S413 in FIG. 12, the method step S420 in FIG. 12, the method steps S500 to S600 in FIG. 14, and the method steps S610 to S620 in FIG. 15.

[0159] All or part of the steps in the methods and systems disclosed above may be implemented as software, firmware, hardware, and any suitable combination thereof. Some or all of the physical components may be implemented as software executed by the central processor 200, digital signal processor 200, or microprocessor 200, or as hardware, or as an integrated circuit such as an application-specific integrated circuit. Such software may be distributed on computer-readable media, which may include computer storage media (or non-transitory media) and communication media (or transitory media). The term computer storage media includes volatile and non-volatile, removable and non-removable media implemented in any method or technology for storing information (e.g., computer-readable instructions, data structures, program modules, or other data). Computer storage media includes, but is not limited to, RAM, ROM, EEPROM, flash memory or other memory technology, CD-ROM, digital versatile disk (DVD) or other optical disk storage device, magnetic cartridge, magnetic tape, magnetic disk storage device or other magnetic storage device, or any other medium that can be used to store the desired information and that can be accessed by a computer. Additionally, communication media typically includes computer-readable instructions, data structures, program modules, or other data in a modulated data signal such as a carrier wave or other transmission mechanism and may include any information delivery media.

[0160]

[0009] Embodiments of the present application include a data transmission method, a network device, a terminal device, a server device, and a computer-readable storage medium. The data transmission method is applied to the network device. The network device communicates with the terminal device and the server device. The method includes the steps of receiving application data transmitted by the terminal device, the application data corresponding to a packet feature identifier; determining a corresponding first packet instance of the network device based on the packet feature identifier, where different first packet instances correspond to different packet feature identifiers; and transmitting the application data to the first packet instance and the application data of the first packet instance to a corresponding second packet instance of the server device, where the server device processes the application data and the second packet instance corresponds one-to-one to the first packet instance. According to an aspect of the embodiment of the present application, the application data of the terminal device is transmitted by the first packet instance of the network device to the second packet instance of the server device based on the packet feature identifier. This allows the network side device to maintain multiple first and second packet instances containing application data, rather than establishing and maintaining one instance for each terminal device. This significantly reduces the number of instances maintained in the network side devices, enables the network side devices to support more terminal device access, and reduces the deployment costs of the terminal devices and the network side devices. Furthermore, the server device can process application data based on the second packet instance corresponding to the packet feature identifier, thereby realizing rapid collection of data from a large amount of terminal devices.

[0161] Although the above describes the preferred embodiments of the present application, the present application is not limited to the above embodiments. Those skilled in the art can make various equivalent modifications or substitutions under common conditions that do not violate the spirit of the present application. These equivalent modifications or substitutions are included in the scope defined by the claims of the present application.

Claims

1. A data transmission method applied to a network device, wherein the network device communicates with a terminal device and a server device, The data transmission method includes: Receiving, by means of a physical random access process, at least one type of application data transmitted by the terminal device, wherein each of the at least one type of application data corresponds to one packet feature identifier; Determining, based on the packet feature identifier, a corresponding first packet instance from a plurality of first packet instances in the network device, wherein the first packet instance and the packet feature identifier correspond one-to-one; Transmitting each of the at least one type of application data to the corresponding first packet instance, and transmitting the application data of the corresponding first packet instance to a second packet instance corresponding to the corresponding first packet instance among a plurality of second packet instances in the server device according to the granularity of the packet, wherein the server device processes the application data, and the second packet instance and the first packet instance correspond one-to-one.

2. The first packet instance is generated as follows: Obtaining configuration information including a plurality of packet feature identifiers, and generating a first packet instance corresponding one-to-one to the packet feature identifier based on the configuration information, wherein the configuration information is preset by a user, or The first packet instance is generated as follows: Obtaining instance information for representing a second packet instance in the server device, and generating a first packet instance corresponding one-to-one to the second packet instance based on the instance information, wherein the second packet instance is generated by the server device based on a plurality of packet feature identifiers in the configuration information, and the second packet instance and the packet feature identifier correspond one-to-one. The data transmission method according to Claim 1. According to claim 3, in the step of receiving at least one type of application data transmitted by the terminal device through a physical random access process, receiving first information from the terminal device, and determining a packet feature identifier of the terminal device based on a time-frequency position where the first information exists; generating second information based on the time-frequency position and transmitting the second information to the terminal device, where the second information is for representing an uplink grant data amount of the application data; when receiving third information including the application data transmitted by the terminal device based on the second information, generating fourth information based on the third information and transmitting the fourth information to the terminal device so that the terminal device enters an idle state, where the fourth information is for representing that the network device has normally received the application data; and the method includes the steps of According to claim 1, in the step of determining a corresponding first packet instance from a plurality of first packet instances in the network device based on the packet feature identifier, when the time-frequency position corresponds to a preset time-frequency position, the step includes determining a corresponding first packet instance of the network device based on the packet feature identifier; After receiving the application data transmitted by the terminal device, the data transmission method When the time-frequency position does not correspond to a preset time-frequency position, further includes the step of transmitting the application data to a PDN device. The data transmission method according to claim 1

4. The application data includes a terminal identity identifier that corresponds one-to-one to the terminal device. Transmitting each of at least one type of the application data to the corresponding first packet instance, and transmitting the application data of the corresponding first packet instance to a second packet instance corresponding to the corresponding first packet instance among a plurality of second packet instances in the server device according to the granularity of the packet. The step where the server device processes the application data A step of transmitting the application data to the first packet instance and transmitting the application data of the first packet instance to a corresponding second packet instance of the server device, wherein the server device analyzes the application data to obtain the terminal identity identifier, and determines the terminal device corresponding to the application data based on the terminal identity identifier and the packet feature identifier. The data transmission method according to claim 1 includes this step.

5. A data transmission method applied to a terminal device, wherein the terminal device communicates with a server device via a network device. The data transmission method includes: A step of transmitting at least one type of application data, each corresponding to one packet feature identifier, to the network device by a physical random access process. The network device determines a corresponding first packet instance from a plurality of first packet instances in the network device based on the packet feature identifier, transmits at least one type of the application data to the corresponding first packet instance, and the network device transmits the application data of the corresponding first packet instance to a second packet instance corresponding to the corresponding first packet instance among a plurality of second packet instances in the server device according to the packet granularity. The server device processes the application data, the first packet instance and the packet feature identifier correspond one-to-one, and the second packet instance and the first packet instance correspond one-to-one. The data transmission method includes this step.

6. A data transmission method applied to a server device, wherein the server device communicates with a terminal device via a network device. The data transmission method includes: Receiving, by means of a physical random access process, at least one type of application data of a plurality of first packet instances from the network device, wherein at least one type of the application data is transmitted by the terminal device, each corresponding to one packet feature identifier, and the first packet instance and the packet feature identifier correspond one-to-one; Transmitting each of at least one type of the application data to a second packet instance corresponding to the first packet instance among a plurality of second packet instances, and processing the application data, wherein the second packet instance and the first packet instance correspond one-to-one; A data transmission method including the steps.

7. A network device including a memory, a processor, and a computer program stored in the memory and executable by the processor, wherein when the processor executes the computer program, it realizes the data transmission method according to any one of Claims 1 to 4.

8. A terminal device including a memory, a processor, and a computer program stored in the memory and executable by the processor, wherein when the processor executes the computer program, it realizes the data transmission method according to Claim 5.

9. A server device including a memory, a processor, and a computer program stored in the memory and executable by the processor, wherein when the processor executes the computer program, it realizes the data transmission method according to Claim 6.

10. A computer-readable storage medium storing computer-executable instructions for realizing the data transmission method according to any one of Claims 1 to 6 by a processor.

Images