Method and system for sporadic uplink data transmission of mMTC terminals

Abstract

The application relates to an mMTC terminal sporadic uplink data transmission method and system. The method comprises the following steps: obtaining application layer generated to-be-sent uplink data, and then performing protocol processing on the to-be-sent uplink data based on a terminal side scheduling-free radio bearer and a base station side scheduling-free radio bearer; and a terminal side physical layer entity sends data transmission information to a base station side physical layer entity through a wireless channel, wherein the data transmission information carries the to-be-sent uplink data and a preamble; after the data transmission information reaches the base station, the base station forwards the to-be-sent uplink data to a server; and the base station side scheduling-free radio bearer serves multiple terminals. The method and system can reduce communication resource consumption.

Description

Technical Field

[0001] This application is applied to the field of wireless communication technology, specifically relating to 4G, 5G and other radio access networks, and particularly to a method and system for intermittent uplink data transmission in mMTC terminals. Background Technology

[0002] Massive Machine-Type Communication (mMTC), a typical application scenario in 5G, primarily targets applications focused on sensor and data acquisition, such as smart cities, smart transportation, smart homes, industrial IoT, and vehicle-to-everything (V2X) networks. mMTC communication involves the automatic reporting of sensor information with near-unmanned operation. It is characterized by a high number of terminals within the base station's coverage area, sporadic active terminals, and very small data packet lengths per transmission.

[0003] Future mMTC terminal connection densities will reach millions or even tens of millions of connections per square kilometer, far exceeding the connection density supported by existing standards, leading to greater communication overhead. Therefore, reducing the communication resource overhead of mMTC communication has become an urgent problem to be solved. Summary of the Invention

[0004] Therefore, it is necessary to provide a method and system for intermittent uplink data transmission in mMTC terminals that can reduce communication resource overhead, in order to address the above-mentioned technical problems.

[0005] Firstly, this application provides an uplink data transmission method applied to a terminal. The method includes:

[0006] Obtain the uplink data to be sent generated by the application layer;

[0007] Based on the terminal-side and base station-side scheduling-free radio bearers, after the uplink data to be transmitted is processed by the protocol, the terminal-side physical layer entity sends data transmission information to the base station-side physical layer entity via the wireless channel; the data transmission information carries the uplink data to be transmitted and the preamble; after the data transmission information arrives at the base station, the base station forwards the uplink data to the server;

[0008] Among them, the base station provides dispatch-free wireless bearer services to multiple terminals.

[0009] In one embodiment, the terminal-side dispatch-free radio bearer includes a terminal-side network layer entity, a terminal-side medium access control layer entity, and a terminal-side physical layer entity. The terminal-side dispatch-free radio bearer is a radio bearer pre-established in the access network protocol stack according to a dispatch-free random access protocol. Based on the terminal-side dispatch-free radio bearer and the base station-side dispatch-free radio bearer, after protocol processing of the uplink data to be transmitted, the terminal-side physical layer entity sends data transmission information to the base station-side physical layer entity via a wireless channel, including:

[0010] The terminal-side network layer entity generates access network layer data packets based on the uplink data to be sent.

[0011] The terminal-side media access control layer entity generates data transmission instructions based on the access network layer data packets.

[0012] The terminal-side physical layer entity generates the data transmission information according to the data transmission instruction and sends the data transmission information to the base station via the wireless channel.

[0013] In one embodiment, the generation of access network layer data packets by the terminal-side network layer entity based on the uplink data to be sent includes:

[0014] Obtain the network address of the server and the network address of the terminal to get the header of the network layer data packet of the access network;

[0015] The access network layer data packet is generated based on the header of the access network layer data packet and the uplink data to be sent. The access network layer data packet conforms to a first preset format.

[0016] In one embodiment, the terminal-side media access control layer entity generates a data transmission instruction based on the access network layer data packet, including:

[0017] Obtain the preamble number and terminal identifier;

[0018] The data transmission instruction is generated based on the preamble number, the terminal identifier, and the access network layer data packet. The data transmission instruction conforms to the second preset format.

[0019] In one embodiment, the terminal-side media access control layer entity generates a data transmission instruction based on the access network layer data packet, including:

[0020] When the length of the access network layer data packet is greater than the preset length, the terminal-side network layer entity segments the access network layer data packet to obtain multiple access network layer data packet fragments.

[0021] The terminal-side Media Access Control layer entity generates data transmission instructions corresponding to each network layer data packet fragment of the access network.

[0022] Secondly, this application provides an uplink data transmission method applied to a base station. The method includes:

[0023] Based on the terminal-side scheduling-free radio bearer and the base station-side scheduling-free radio bearer, the base station-side physical layer entity receives the data transmission information sent by the terminal-side physical layer entity via the wireless channel. The base station-side physical layer entity, the base station-side medium access control layer entity, and the base station-side network layer entity process the data transmission information in sequence to obtain the core network layer data packet. The data transmission information carries the uplink data to be sent generated by the terminal-side application layer.

[0024] The core network layer data packet containing the uplink data to be sent is forwarded to the server.

[0025] Among them, the base station provides dispatch-free wireless bearer services to multiple terminals.

[0026] In one embodiment, the base station-side dispatch-free radio bearer includes a base station-side network layer entity, a base station-side medium access control layer entity, and a base station-side physical layer entity. The base station-side dispatch-free radio bearer is a radio bearer pre-established in the access network protocol stack according to a dispatch-free random access protocol. Based on the terminal-side dispatch-free radio bearer and the base station-side dispatch-free radio bearer, the base station-side physical layer entity receives data transmission information sent by the terminal-side physical layer entity via a wireless channel. The base station-side physical layer entity, the base station-side medium access control layer entity, and the base station-side network layer entity sequentially process the data transmission information to obtain a core network layer data packet, including:

[0027] The physical layer entity on the base station side receives the data transmission information and parses and processes the data transmission information to obtain the data arrival instruction;

[0028] The base station-side medium access control layer entity parses and processes the data arrival instruction to obtain an access network layer data packet containing the uplink data to be sent.

[0029] The core network layer data packet is obtained by parsing the access network layer data packet containing the uplink data to be sent through the network layer entity on the base station side.

[0030] In one embodiment, the method further includes:

[0031] When there are multiple access network layer data packet fragments, the multiple access network layer data packet fragments are combined to obtain the core network layer data packet.

[0032] In one embodiment, the method further includes:

[0033] Obtain the network address of the server and determine the target tunnel corresponding to the network address of the server according to the pre-configured mapping relationship;

[0034] The core network layer data packets are sent to the data gateway through the target tunnel, and then the data gateway sends the core network layer data packets to the server.

[0035] Thirdly, this application also provides an uplink data transmission system. This uplink data transmission system includes a terminal and a base station;

[0036] This terminal is used to execute the method executed by the terminal in any of the above embodiments;

[0037] This base station is used to execute the method performed by the base station in any of the above embodiments.

[0038] The aforementioned method and system for intermittent uplink data transmission in mMTC terminals first involves the terminal acquiring uplink data to be transmitted generated by the application layer. Then, based on the terminal-side and base station-side dispatch-free radio bearers, the uplink data is processed according to protocols. Finally, the terminal-side physical layer entity sends data transmission information to the base station-side physical layer entity via a wireless channel. This data transmission information carries the uplink data to be transmitted and a preamble. Upon arrival at the base station, the base station forwards the uplink data to the server. The base station-side dispatch-free radio bearer serves multiple terminals. In traditional technologies, each terminal needs its own independent radio bearer for uplink data transmission. However, future terminal connection density will reach millions or even tens of millions of connections per square kilometer, far exceeding the connection density supported by existing standards. Using traditional technologies would incur significant communication resource overhead at the base station side. In this embodiment, multiple terminals can share the same unscheduled radio bearer on the base station. mMTC terminals not transmitting data are in a dormant state, while mMTC terminals with uplink data to transmit enter an active state. Using an unscheduled radio bearer, the uplink data generated by the application layer on the active terminal side can be sent to the base station. The base station then transmits the uplink data to the server, thus enabling the transmission of uplink data between the mMTC terminal and the mMTC server. This reduces the number of radio bearers and lowers system operating overhead. In other words, the uplink data transmission method provided in this embodiment can reduce communication resource overhead. Attached Figure Description

[0039] Figure 1 This is an application environment diagram of the uplink data transmission method in one embodiment;

[0040] Figure 2This is one of the flowcharts illustrating an uplink data transmission method provided in an embodiment of this application;

[0041] Figure 3 A flowchart illustrating a method for transmitting data information according to an embodiment of this application;

[0042] Figure 4 A schematic flowchart of a conventional random access method provided in an embodiment of this application;

[0043] Figure 5 A flowchart illustrating a scheduling-free random access method provided in an embodiment of this application;

[0044] Figure 6 A flowchart illustrating a method for generating network layer data packets in an access network according to an embodiment of this application;

[0045] Figure 7 A schematic diagram of a first preset format provided for an embodiment of this application;

[0046] Figure 8 A flowchart illustrating a data transmission instruction generation method provided in an embodiment of this application;

[0047] Figure 9 A second schematic flowchart illustrating an uplink data transmission method provided in this application embodiment;

[0048] Figure 10 This is a schematic diagram of IP packet segmentation provided in an embodiment of this application;

[0049] Figure 11 The third schematic flowchart of an uplink data transmission method provided in this application embodiment;

[0050] Figure 12 A flowchart illustrating a method for receiving data transmission information provided in an embodiment of this application;

[0051] Figure 13 This application provides a schematic diagram of IP packet reassembly.

[0052] Figure 14 A flowchart illustrating an uplink data forwarding method provided in an embodiment of this application;

[0053] Figure 15 A schematic diagram illustrating an end-to-end information exchange process for uplink data provided in an embodiment of this application;

[0054] Figure 16 The fourth flowchart illustrates an uplink data transmission method provided in this application embodiment.

[0055] Figure 17 This is one of the schematic diagrams of an uplink data transmission device provided in an embodiment of this application;

[0056] Figure 18 This is a second schematic diagram of an uplink data transmission device provided in an embodiment of this application. Detailed Implementation

[0057] To make the objectives, technical solutions, and advantages of this application clearer, the following detailed description is provided in conjunction with the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are merely illustrative and not intended to limit the scope of this application.

[0058] In traditional technologies, before a terminal can communicate with a base station, it must first establish a Radio Resource Control (RRC) connection, then the base station establishes a connection to the core network data gateway, and the base station configures relevant routes before it can interact with the data gateway. However, mMTC terminals are in a dormant state for extended periods, in an inactive RRC state. Due to this inactivity, the data route from the conventional 5G terminal to the core network data gateway (5G terminal data needs to be forwarded from the data gateway to the mMTC server) is inactive or nonexistent. Reactivating or establishing this route requires time and processing resources, and may even result in data loss. The second layer of the conventional data plane air interface protocol stack consists of protocols such as Radio Link Control (RLC) and Packet Data Convergence Protocol (PDCP). The base station needs to configure independent RLC and PDCP protocol entities for each access terminal to achieve data transmission and reception. In mMTC application scenarios, the number of mMTC terminals can reach millions or more, making it unimaginable to configure so many protocol entities on the base station, resulting in enormous communication and processing resource overhead.

[0059] Therefore, to solve the above problems, embodiments of this application provide an uplink data transmission method that can be applied to, for example... Figure 1 In the application environment shown, terminal 101 communicates with server 103 via base station 102. Terminal 101 can be, but is not limited to, various personal computers, laptops, smartphones, tablets, IoT devices, and portable wearable devices. IoT devices can include smart speakers, smart TVs, smart air conditioners, smart in-vehicle devices, etc. Portable wearable devices can include smartwatches, smart bracelets, head-mounted devices, etc. Server 103 can be implemented using a standalone server or a server cluster consisting of multiple servers.

[0060] In one embodiment, an uplink data transmission method is provided, referencing Figure 2 , Figure 2 This is one of the flowcharts illustrating an uplink data transmission method provided in an embodiment of this application. This method is now applied to... Figure 1 Taking the terminal in the example, the explanation includes the following steps:

[0061] S201. Obtain the uplink data to be sent generated by the application layer.

[0062] The terminal can be a massive machine-type communication (mMTC) terminal, i.e. an mMTC terminal used for massive machine-type communication. The uplink data to be transmitted refers to the data generated by the terminal that needs to be transmitted to the mMTC server via the base station. The "uplink data to be transmitted" in this application refers to this data.

[0063] In this embodiment of the application, the mMTC terminal can obtain uplink data to be sent generated by the application layer.

[0064] It should be noted that before transmitting uplink data, the base station's RRC layer can broadcast the resource configuration information for uplink scheduling-free transmission to the terminal side through System Information Block-1 (SIB1); or it can adopt a pre-configuration approach to uniformly plan and manage uplink scheduling-free resources on both the base station and the terminal.

[0065] S202. Based on the terminal-side scheduling-free radio bearer and the base station-side scheduling-free radio bearer, after the uplink data to be transmitted is processed by the protocol, the terminal-side physical layer entity sends the data transmission information to the base station-side physical layer entity via the wireless channel; the data transmission information carries the uplink data to be transmitted and the preamble, and after the data transmission information arrives at the base station, the base station forwards the uplink data to be transmitted to the server; among them, the base station-side scheduling-free radio bearer serves multiple terminals.

[0066] In this embodiment, a terminal-side dispatch-free radio bearer can be pre-established in the terminal access network protocol stack, and a base station-side dispatch-free radio bearer can be pre-established in the base station access network protocol stack. The mMTC terminal can perform protocol processing on the uplink data to be transmitted based on the pre-established terminal-side and base station-side dispatch-free radio bearers in the access network protocol stack. The terminal-side physical layer entity sends data transmission information carrying the uplink data to be transmitted and a preamble to the base station-side physical layer entity via a wireless channel. After the data transmission information reaches the base station, the base station forwards the uplink data to be transmitted to the server.

[0067] In addition, the application layer on the terminal side encapsulates the uplink data to be transmitted into an Application Packet Data Unit (appPDU) and sends it to the lower-level entity of the application layer on the mMTC terminal side based on the pre-established scheduling-free radio bearer in the access network protocol stack. The lower-level entity on the mMTC terminal side parses and transmits the data transmission information carrying the uplink data to be transmitted to the base station. It also instructs the base station to forward the uplink data to the data gateway through a data transmission command. The data gateway forwards the uplink data to the mMTC server according to the network address of the server in the uplink data, so as to realize the transmission of the uplink data between the mMTC terminal and the mMTC server.

[0068] It should be noted that all mMTC terminals use virtual access. mMTC terminals not transmitting data are in a dormant state, while those with uplink data to transmit are in an active state. The base station's dispatch-free radio bearer can serve multiple mMTC terminals; that is, multiple mMTC terminals can share a single dispatch-free radio bearer to transmit uplink data. The uplink dispatch-free access mechanism simplifies the network, significantly reduces transmission latency and signaling load, and can improve the performance of random access in mMTC slices while reducing system operating overhead. Future wireless communication systems will also need to simultaneously serve a variety of mMTC terminals with different service requirements, such as latency sensitivity, power consumption limitations, and reliability. Network slicing technology can dynamically adjust network configuration in real time according to changing device requirements, ensuring that such adjustments do not affect other services such as enhanced mobile broadband (eMBB). By utilizing network slicing technology, network owners virtualize their public physical network infrastructure into multiple distinct "sub-networks" (slices). Network service providers can then lease these network slices to offer customized services to users such as mMTC and eMBB, significantly enhancing network flexibility. These network service providers are known as slice tenants. Network slicing technology provides reliable support for addressing the diverse device service needs of mMTC scenarios. In scenarios such as the Industrial Internet of Things (IIoT), network slicing has become a frequently employed key technology for resolving the diverse service requirements of different types of mMTC terminals.

[0069] In the aforementioned uplink data transmission method, firstly, the terminal acquires the uplink data to be transmitted generated by the application layer. Then, based on the terminal-side and base station-side scheduling-free radio bearers, the uplink data to be transmitted undergoes protocol processing. Finally, the terminal-side physical layer entity sends data transmission information to the base station-side physical layer entity via a wireless channel. This data transmission information carries the uplink data to be transmitted and a preamble. After the data transmission information reaches the base station, the base station forwards the uplink data to the server. The base station-side scheduling-free radio bearer serves multiple terminals. In traditional technologies, each terminal needs its own independent radio bearer for uplink data transmission. However, future terminal connection density will reach millions or even tens of millions of connections per square kilometer, far exceeding the connection density supported by existing standards. Using traditional technologies would result in enormous communication resource overhead. In this embodiment, multiple terminals can share the same unscheduled radio bearer on the base station. mMTC terminals not transmitting data are in a dormant state, while mMTC terminals with uplink data to transmit enter an active state. Using an unscheduled radio bearer, the uplink data generated by the application layer on the active terminal side can be sent to the base station. The base station then transmits the uplink data to the server, thus enabling the transmission of uplink data between the mMTC terminal and the mMTC server. This reduces the number of radio bearers and lowers system operating overhead. In other words, the uplink data transmission method provided in this embodiment can reduce communication resource overhead.

[0070] It should be noted that the embodiments of this application do not involve sending downlink data from an mMTC server to an mMTC terminal. If it is necessary to send a small amount of downlink data to an mMTC terminal, paging or MsgB methods can be used, and the embodiments of this application do not limit the specific methods and processes.

[0071] In one embodiment, Figure 3 This is a flowchart illustrating a method for transmitting data transmission information according to an embodiment of this application. The terminal-side dispatch-free radio bearer includes a terminal-side network layer entity, a terminal-side medium access control layer entity, and a terminal-side physical layer entity. The terminal-side dispatch-free radio bearer is a radio bearer pre-established in the access network protocol stack according to a dispatch-free random access protocol. Based on the terminal-side dispatch-free radio bearer and the base station-side dispatch-free radio bearer, after protocol processing of the uplink data to be transmitted, the terminal-side physical layer entity sends data transmission information to the base station-side physical layer entity via a wireless channel. This embodiment relates to a possible implementation of how, based on the pre-established terminal-side dispatch-free radio bearer and base station-side dispatch-free radio bearer in the access network protocol stack, after protocol processing of the uplink data to be transmitted, the terminal-side physical layer entity sends data transmission information to the base station-side physical layer entity via a wireless channel. Based on the above embodiment, S202 includes:

[0072] S301. The terminal-side network layer entity generates access network layer data packets based on the uplink data to be sent.

[0073] The terminal-side dispatch-free radio bearer includes a terminal-side network layer entity, a terminal-side media access control layer entity, and a terminal-side physical layer entity. The terminal-side network layer entity can be a massive machine-type communication-IP data radio bearer (mMTC-ipDRB). The access network layer data packets can be IP data packets (Internet Protocol Data), X.25 protocol packets, ATM (Asynchronous Transfer Mode) protocol packets, etc. This embodiment uses IP data packets as an example.

[0074] In this embodiment, the mMTC terminal can generate IP data packets based on the uplink data to be sent via the mMTC-ipDRB. Specifically, the mMTC terminal first encapsulates the uplink data to be sent generated by the application layer into an Application Packet Data Unit (appPDU), and then hands the appPDU over to the mMTC-ipDRB in the access network air interface protocol stack. After receiving the appPDU, the mMTC-ipDRB places the appPDU into its transmission buffer. The mMTC-ipDRB transmission thread continuously polls this transmission buffer, reads the appPDU, and generates IP data based on the appPDU. The IP data can be encrypted based on the nature and requirements of the IP data content and the mMTC terminal's identity characteristics; however, this embodiment does not restrict the encryption behavior.

[0075] It should be noted that when an mMTC terminal pre-establishes a terminal-side dispatch-free radio bearer, it will create an mMTC-ipDRB. The network layer can receive mMTC application data sent down from the upper layer and hand it over to the mMTC-ipDRB for processing. After processing the IP data, the mMTC-ipDRB sends it to the terminal-side Medium Access Control (MAC) entity.

[0076] S302. The terminal-side medium access control layer entity generates data transmission instructions based on the access network layer data packets.

[0077] Among them, the terminal-side media access control layer entity can be a grant-free random access-medium access control layer (GFRA-MAC) entity.

[0078] In this embodiment, taking IP data packets as an example, the mMTC terminal can generate data transmission instructions based on IP data through GFRA-MAC. Specifically, the mMTC-ipDRB of the mMTC terminal can transmit IP data to the GFRA-MAC of the terminal-side media access control layer via the GFRA-MAC to the upper-layer service interface. The GFRA-MAC of the mMTC terminal uses a polling method to call the upper-layer service interface to obtain the data submitted by mMTC-ipDRB and generate a data transmission instruction MsgA.req. The GFRA-MAC sends MsgA.req to the terminal-side physical layer based on a scheduling-free random access method. If the IP data is divided into multiple IP data packet fragments, these fragments are transmitted to the GFRA-MAC accordingly. When the mMTC terminal pre-establishes a terminal-side dispatch-free radio bearer, it will create a GFRA-MAC. The GFRA-MAC can receive and parse IP data sent by the network layer, and for the dispatch-free random access method, it can send the MsgA.req request command to instruct the PHY to complete the dispatch-free random access and transmit the uplink data to be sent. It can control the msgB-ResponseWindow response time window and trigger the retransmission of the MsgA message.

[0079] It should be noted that after sending MsgA.req, the GFRA-MAC entity will start the corresponding msgB-ResponseWindow response time window. This window can be set to 20 TTIs (transmission time intervals). If the GFRA-MAC does not receive MsgB within 20 TTIs, it will attempt to resend MsgA.req to the physical layer until the preset maximum number of transmissions is reached. After the processing of a MsgA.req sent by the GFRA-MAC is completed (whether it ends when the maximum number of transmissions is reached or below), the GFRA-MAC can check if there is any other pending data. If so, it will generate a new MsgA.req.

[0080] S303. The terminal-side physical layer entity generates data transmission information according to the data transmission instruction and sends the data transmission information to the base station via the wireless channel.

[0081] Among them, the terminal-side physical layer entity PHY includes a wireless channel, namely the Physical Random Access Channel (Prach).

[0082] In this embodiment, the mMTC terminal can generate data transmission information MsgA via the PHY according to the data transmission instruction MsgA.req. Specifically, after receiving the MsgA.req instruction, the mMTC terminal PHY generates the corresponding MsgA encoding sequence. The PHY then transmits the MsgA encoding sequence to the radio frequency unit on the PUSCH (Physical Uplink Shared Channel), and then transmits it to the base station PHY via the air interface. It should be noted that if the IP data is divided into multiple IP data packet fragments, the mMTC terminal PHY receives multiple MsgA.req instructions sequentially and generates the corresponding MsgA encoding sequences in order (for example, they can be denoted as MsgA1, MsgA2, MsgA3, etc.).

[0083] In this embodiment, the terminal-side network layer entity first generates access network layer data packets based on the uplink data to be sent. Then, the terminal-side medium access control layer entity generates data transmission instructions based on the access network layer data packets. Finally, the terminal-side physical layer entity generates data transmission information based on the data transmission instructions and sends the data transmission information to the base station via the wireless channel. This simplifies the conventional data plane air interface protocol stack. This simplified data plane air interface protocol stack is used on both the terminal side and the base station side, thus forming an access network air interface protocol stack that supports a massive number of terminals, thereby simplifying the data transmission process and increasing transmission efficiency.

[0084] Figure 4 This is a flowchart illustrating a traditional random access method provided in an embodiment of this application. In 4G / 5G wireless networks, when conventional terminals such as mobile phones transmit data, they generally first access data via... Figure 4The diagram illustrates a contention-based random access method that establishes a connection before data transmission. This method typically employs a four-step random access process, consisting of four messages: Msg1, Msg2, Msg3, and Msg4. In this process, the terminal sends a preamble to the base station via Msg1. The base station verifies the preamble, allocates uplink resources for Msg3, and sends Msg2 to the terminal as a response to the random access. Upon receiving Msg2, the terminal sends Msg3 containing the uplink data to be transmitted. The base station, upon receiving Msg3, sends Msg4 to the terminal, indicating that the conflict has been resolved. However, directly applying this method to mMTC terminal scenarios results in massive signaling load due to the constant connection establishment and release for transmitting small amounts of data. Furthermore, the process of random access, connection establishment, and data transmission requires requesting channel resources from the base station scheduler, leading to low channel resource utilization and high data transmission latency.

[0085] Therefore, this application provides a method for implementing uplink data transmission of mMTC terminals through scheduling-free random access. Figure 5 This is a flowchart illustrating a scheduling-free random access method provided in an embodiment of this application. (Refer to...) Figure 5 The mMTC terminal can combine the two uplink channel information Msg1 and Msg3 from traditional random access into MsgA, and combine the two downlink channel information Msg2 and Msg4 into MsgB, and transmit uplink data in the GFRA (Grant-free Random Access) manner. That is, it can send information containing uplink data to the base station in the first message MsgA. In this embodiment, there is no restriction on the format of the scheduling-free message. The scheduling-free message format can follow the 5G MsgA format, that is, send two messages Msg1 and Msg3 one by one, or it can be a self-designed MsgA format. The specific format of MsgA is determined by the physical layer implementer. For example, it can combine the traditional Msg1 with the user identifier and the access network layer data packet to obtain a single message format.

[0086] In one embodiment, Figure 6 This is a flowchart illustrating a method for generating access network layer data packets according to an embodiment of this application. This embodiment relates to a possible implementation of how a terminal-side network layer entity generates access network layer data packets based on uplink data to be sent. Based on the above embodiment, step S301 includes:

[0087] S601. Obtain the network address of the server and the network address of the terminal to get the header of the access network layer data packet.

[0088] In this embodiment, the mMTC terminal can obtain the server's IP address and the terminal's IP address to obtain the IP data header. Specifically, after receiving the appPDU sent by the application layer, the mMTC-ipDRB reads the server's IP address from the appPDU and then obtains the IP data header based on the terminal's IP address.

[0089] It should be noted that an appPDU can consist of a terminal identifier (UEid, User Equipment identifier), a server IP address (IP01), an appPDU length (Len), and an application payload (AppPayload), totaling 72 bytes in length. The terminal's IP address is the one assigned when the mMTC terminal registers with the core network after powering on. The AppPayload carries the specific content of the uplink data to be transmitted. The basic structure of an appPDU is as follows:

[0090] appPDU{UEid[4Bytes], IP01[4Bytes], Len[4Bytes], AppPayload[60Byte]};

[0091] The appPDU is the encapsulated uplink data to be sent, that is, the uplink data to be sent generated by the application layer. In subsequent processes, the destination IP address (used for addressing the server) in the IP data header will come from IP01 in the appPDU. The header is 20 bytes long.

[0092] S602. Generate an access network layer data packet based on the header of the access network layer data packet and the uplink data appPDU to be sent. The access network layer data packet conforms to the first preset format.

[0093] The first preset format can be referenced. Figure 7 , Figure 7 This is a schematic diagram of a first preset format provided for an embodiment of this application.

[0094] In this embodiment, the mMTC terminal can generate IP data packets based on the header of IP data consisting of the server's IP address and the terminal's IP address, and the uplink data appPDU to be sent. The access network layer data conforms to a first preset format. The specific structure is as follows:

[0095] IP data{IPHeader[20Bytes], IPBody[80Bytes]};

[0096] The IPHeader represents the header of the IP packet, which is 20 bytes long, and the IPBody represents the data area of ​​the IP packet, which is 80 bytes long. The specific structure of the IPBody is as follows:

[0097] IPBody{UDPHeader[8Bytes], appPDU[72Bytes]};

[0098] The UDPHeader represents the User Datagram Protocol (UDP) header, which is 8 bytes long. The port number of the mMTC server in the UDPHeader is set to the port number that the mMTC server is pre-configured to listen for and receive UDP data, which can be denoted as DPort.

[0099] In this embodiment, by obtaining the IP address of the server and the IP address of the terminal, the header of the IP data packet can be generated, and then the IP data packet can be generated according to the first preset format, the header of the IP data packet and the uplink data appPDU to be sent.

[0100] In one embodiment, Figure 8 This is a flowchart illustrating a data transmission instruction generation method provided in this application embodiment. This embodiment relates to a possible implementation of how a terminal-side medium access control layer entity generates a data transmission instruction based on access network layer data packets. Based on the above embodiment, S302 includes:

[0101] S801. Obtain the preamble number and terminal identifier.

[0102] In this embodiment, the MsgA structure is used when the mMTC terminal and the base station perform air interface transmission. The aforementioned IP data needs to be filled into the MsgAPayload field of the MsgA structure. The specific filling process is triggered by the MsgA.req data transmission command. It can be assumed that MsgA.req consists of the preamble number (RapID, Random Access PreambleIdentifier), the terminal identifier UEid, and MsgAPayload carrying the uplink data to be transmitted. It is also assumed that the maximum length of MsgAPayload is 52 bytes. The basic structure is as follows:

[0103] MsgA.req{RapID[4Bytes], UEid[4Bytes], MsgAPayload[52Bytes]};

[0104] The mMTC terminal can obtain the preamble number RapID and the terminal identifier UEid from MsgA.req in the above embodiments.

[0105] It should be noted that in the pre-configuration, there is a single mapping relationship between the terminal identifier UEid and the preamble number RapID, that is, the base station and the terminal protocol stack can obtain the corresponding RapID based on the UEid; MsgAPayload carries the access network layer data packet IP data or its fragments.

[0106] S802. Generate a data transmission instruction based on the preamble number, terminal identifier, and access network layer data packet. The data transmission instruction conforms to the second preset format.

[0107] The second preset format can be customized according to requirements. For example, it can consist of a preamble numbered RapID, a terminal identifier UEid, and IP data.

[0108] In this embodiment, the mMTC terminal can generate a data transmission command based on the preamble RapID, the terminal identifier UEid, and the access network layer data packet IP data, wherein the data transmission command conforms to a second preset format. Specifically, after GFRA-MAC obtains the terminal identifier UEid and IP data submitted by mMTC-ipDRB, it generates a data transmission command based on the UEid and the preamble number RapID matched in the preconfiguration, according to the second preset format, the preamble number RapID, the terminal identifier UEid, and the access network layer data packet IP data. An example structure of this data transmission command is as follows:

[0109] MsgA.req{RapID[4Bytes], UEid[4Bytes], IP data[52Bytes].

[0110] Among them, the IP data[52Bytes] has a maximum length of 52 bytes and is an IP packet or fragment.

[0111] In this embodiment, by obtaining the preamble number and terminal identifier, a data transmission instruction is generated based on the preamble number, terminal identifier, and access network layer data packet, wherein the data transmission instruction conforms to a second preset format.

[0112] In one embodiment, Figure 9 This is a second flowchart illustrating an uplink data transmission method provided in this application. Based on the above embodiments, this application provides a possible implementation of how a terminal-side medium access control layer entity generates a data transmission instruction based on access network layer data packets. S302 includes:

[0113] S901. When the length of the access network layer data packet is greater than the preset length, the access network layer data packet is segmented by the terminal-side network layer entity to obtain multiple access network layer data packet fragments.

[0114] The preset length is the maximum length of MsgAPayload (MsgAPayload is used to carry access network layer data packets). For ease of explanation, this embodiment assumes it to be 52 bytes. In actual wireless systems, the specific value is determined by the physical layer and is not limited by the assumptions made in this embodiment.

[0115] In this embodiment, after obtaining a piece of IP data, mMTC-ipDRB determines the length of the IP data. If the length of the access network layer data packet exceeds the maximum data length that MsgAPayload can carry, mMTC-ipDRB segments the IP data to obtain multiple access network layer data packet fragments to meet transmission requirements.

[0116] For IP data segmentation, please refer to... Figure 10 , Figure 10 This diagram illustrates an IP packet fragmentation method provided in this application. As can be seen, the structure of an IP packet fragment is the same as the original unfragmented IP data, both consisting of an IP data header and an IP data data area. The header of the IP packet fragment is a copy of the original IP data header, but differs from the "Flags" and "Fragment Offset" in the header of the unfragmented IP data. In the "Flags" field, the lower two significant bits DF=0 indicate that fragmentation is allowed, and the lowest significant bit MF=0 indicates that there are no further fragments; otherwise, there are more fragments to follow. The data area of ​​the IP packet fragment is a continuation of the original IP data data area, and the "Identifier" of all IP packet fragments should be consistent. Here, MF and DF represent flags; MF can be used to indicate whether there are more fragments, and DF can be used to indicate whether fragmentation is allowed. Furthermore, the size of the data area of ​​each IP packet fragment should be divisible by 8, and the total length of the IP packet fragment should not exceed 52 bytes.

[0117] For example, if the IP data length of 100 bytes exceeds the maximum uplink data length of 52 bytes that MsgA can carry, then the IP data needs to be segmented. Based on the above segmentation principle, the IP data can be segmented into three IP data packet fragments: IP data1, IP data2, and IP data3.

[0118] S902, Generate data transmission instructions corresponding to data packet fragments of each access network network layer through the terminal-side medium access control layer entity.

[0119] In this embodiment, the mMTC terminal can generate data transmission instructions corresponding to each IP data packet fragment through the terminal-side Media Access Control (MACC) layer GFRA-MAC entity, thereby obtaining each IP data packet fragment. Specifically, the mMTC terminal mMTC-ipDRB submits three sets of data—UEid+IP data1, UEid+IP data2, and UEid+IP data3—to the upper-layer service interface via GFRA-MAC to the terminal-side MACC layer GFRA-MAC entity in sequence. The structure of the data transmission instruction can also be represented as follows:

[0120] MsgA.req{RapID[4Bytes], UEid[4Bytes], IP data1}.

[0121] MsgA.req{RapID[4Bytes], UEid[4Bytes], IP data2}.

[0122] MsgA.req{RapID[4Bytes], UEid[4Bytes], IP data3}.

[0123] It should be noted that the terminal-side physical layer generates multiple data transmission information sequentially based on the data transmission instructions corresponding to the fragmentation of multiple access network layer data packets, and sends these multiple data transmission information to the base station. Specifically, the mMTC terminal can generate multiple data transmission information sequentially based on the data transmission instructions corresponding to the fragmentation of multiple IP data packets through the terminal-side PHY, and send these multiple data transmission information to the base station's PHY. For example, after the mMTC terminal PHY receives three MsgA.req instructions sent by GFRA-MAC in sequence, it generates the corresponding MsgA encoding sequence in order. This can be denoted as MsgA1, MsgA2, and MsgA3 (data transmission information), and sent to the base station's PHY through the air interface. In this case, the structures of MsgA1, MsgA2, and MsgA3 are as follows:

[0124] MsgA1{preamble indexed by RapID, UEid, IP data1};

[0125] MsgA2{preamble indexed by RapID, UEid, IP data2};

[0126] MsgA3{preamble indexed by RapID, UEid, IP data3}.

[0127] In this embodiment, when the length of the access network layer data packet exceeds a preset length, the terminal-side network layer entity segments the IP data packet to obtain multiple IP data packet fragments. Then, the terminal-side medium access control layer entity generates data transmission instructions corresponding to each IP data packet fragment. Finally, the terminal-side physical layer sequentially generates multiple data transmission information messages based on the data transmission instructions corresponding to the multiple IP data packet fragments and sends these messages to the base station. This segmentation method improves the adaptability of uplink data transmission by allowing IP data packets exceeding the preset length to be forwarded.

[0128] In one embodiment, an uplink data transmission method is provided, applied to a base station, with reference to... Figure 11 , Figure 11 This is the third flowchart illustrating an uplink data transmission method provided in this application embodiment. The method is now applied to... Figure 1 Taking a base station as an example, the explanation includes the following steps:

[0129] S1101. Based on the terminal-side scheduling-free radio bearer and the base station-side scheduling-free radio bearer, the base station-side physical layer entity receives the data transmission information sent by the terminal-side physical layer entity through the radio channel. The base station-side physical layer entity, the base station-side medium access control layer entity, and the base station-side network layer entity process the data transmission information in sequence to obtain the core network layer data packet. The data transmission information carries the uplink data to be sent generated by the terminal-side application layer.

[0130] The terminal can be an mMTC terminal.

[0131] In this embodiment, a scheduling-free radio bearer can be pre-established in the base station access network protocol stack. Based on this pre-established scheduling-free radio bearer in the access network protocol stack, the base station can receive data transmission information sent by the mMTC terminal, carrying uplink data to be transmitted generated by the mMTC terminal's application layer. The base station-side physical layer entity, the base station-side medium access control layer entity, and the base station-side network layer entity sequentially process the data transmission information to obtain a core network layer data packet. The data transmission information carries uplink data to be transmitted generated by the terminal-side application layer.

[0132] S1102, forward the core network layer data packet containing the uplink data to be transmitted to the server. The base station-side dispatch-free radio bearer serves multiple terminals.

[0133] In this embodiment, the physical layer on the base station side parses the data transmission information and transmits it to the upper-layer entity on the base station side until it reaches the network layer on the base station side. The base station forwards the core network layer data packet containing the uplink data to be sent from the network layer to the data gateway. The data gateway forwards the core network layer data packet to the mMTC server according to the IP address of the server in the core network layer data packet.

[0134] It should be noted that all mMTC terminals use virtual access. mMTC terminals not transmitting data are in a dormant state, while those with uplink data to transmit are in an active state. The base station-side dispatch-free radio bearer can serve multiple mMTC terminals; that is, multiple mMTC terminals can share the same base station-side dispatch-free radio bearer on the base station to transmit uplink data. The uplink dispatch-free access mechanism simplifies the network, significantly reduces transmission latency and signaling load, improves the performance of random access for terminals in mMTC slices, and reduces system operating overhead.

[0135] In the aforementioned uplink data transmission method, firstly, based on the terminal-side scheduling-free radio bearer and the base station-side scheduling-free radio bearer, the base station-side physical layer entity receives the data transmission information sent by the terminal-side physical layer entity via a wireless channel. The base station-side physical layer entity, the base station-side medium access control layer entity, and the base station-side network layer entity sequentially process the data transmission information to obtain a core network layer data packet. The data transmission information carries uplink data to be sent generated by the terminal-side application layer. The core network layer data packet containing the uplink data to be sent is forwarded to the server. The base station-side scheduling-free radio bearer serves multiple terminals. Since multiple terminals can share a single base station-side scheduling-free radio bearer, the uplink data transmission method provided in this application embodiment can reduce communication resource overhead.

[0136] In one embodiment, Figure 12 This is a flowchart illustrating a method for receiving data transmission information provided in an embodiment of this application. The base station-side dispatch-free radio bearer includes a base station-side network layer entity, a base station-side medium access control layer entity, and a base station-side physical layer entity. The base station-side dispatch-free radio bearer is a radio bearer pre-established in the access network protocol stack according to a dispatch-free random access protocol. Based on the terminal-side dispatch-free radio bearer and the base station-side dispatch-free radio bearer, the base station-side physical layer entity receives data transmission information sent by the terminal-side physical layer entity via a wireless channel. The base station-side physical layer entity, the base station-side medium access control layer entity, and the base station-side network layer entity process the data transmission information sequentially to obtain a core network layer data packet. The above S1101 includes:

[0137] S1201: Receive data transmission information through the physical layer entity on the base station side, and parse and process the data transmission information to obtain the data arrival instruction.

[0138] In this embodiment, the base station can parse and process the data transmission information MsgA through the base station-side physical layer entity PHY to obtain data transmission instructions. Specifically, when the base station-side PHY receives three data transmission messages, the base station-side PHY can detect the signals MsgA1, MsgA2, and MsgA3 respectively. After successful parsing, it obtains three messages, MsgA1, MsgA2, and MsgA3, and then forms three corresponding MsgA.ind (indication) data arrival instructions (their structure is the same as MsgA.req). These data arrival instructions are used to instruct the three data transmission messages to be handed over to the base station-side GFRA-MAC.

[0139] S1202. The base station-side medium access control layer entity parses and processes the data arrival command to obtain the access network layer data packet containing the uplink data to be sent.

[0140] In this embodiment, the base station can parse and process the data arrival instruction through the base station-side medium access control layer entity GFRA-MAC (if the uplink data content to be sent is already encrypted on the terminal side, it needs to be decrypted on the base station side; this embodiment does not restrict the decryption behavior; this embodiment also does not restrict the base station's behavior of verifying user identity) to obtain IP data packets.

[0141] Specifically, the GFRA-MAC on the base station side parses the data arrival instructions from the PHY to obtain the terminal identifier UEid and the access network layer data packets. The PHY sends three data arrival instructions: MsgA1, MsgA2, and MsgA3. The GFRA-MAC on the base station side parses these instructions sequentially to obtain IPdata1, IPdata2, and IPdata3, and then passes IPdata1, IPdata2, and IPdata3 to the network layer entity mMTC-ipDRB.

[0142] It should be noted that when the base station pre-establishes a scheduling-free radio bearer, it will create a GFRA-MAC entity at the MAC layer. The GFRA-MAC can receive and parse the MsgA message arrival indication MsgA.ind handed over by the physical layer, extract the uplink data to be sent from the MsgA.ind indication message and hand it over to the mMTC-ipDRB entity, and perform relevant statistics on the activity of the terminal's UEid.

[0143] S1203. The access network layer data packets containing uplink data to be transmitted are parsed and processed by the network layer entity on the base station side to obtain the core network layer data packets.

[0144] In this embodiment, the base station can parse and process access network layer data packets containing uplink data to be transmitted through the base station-side network layer entity mMTC-ipDRB to obtain core network layer data packets containing uplink data to be transmitted. These core network layer data packets are suitable for transmission from the base station to the data gateway via the core network. These core network layer data packets can have longer packet lengths and do not compress the packet header; however, the access network layer data packets generated on the terminal side may compress the packet header (this embodiment does not restrict the terminal-side access network layer packet header compression behavior). If the terminal-side access network layer data packet header is compressed, the base station-side network layer entity needs to decompress the access network layer data packet header.

[0145] It should be noted that when the base station pre-establishes the base station-side dispatch-free radio bearer, it will create an mMTC-ipDRB entity at the network layer. After the mMTC-ipDRB is directly bound to the GFRA-MAC, it forms a dispatch-free radio bearer, which provides transmission services for all uplink data to be sent by all mMTC terminals to the server. The mMTC-ipDRB entity can read the configured IP address of the mMTC server.

[0146] In this embodiment, the MsgA information is parsed and processed by the physical layer entity on the base station side to obtain the data arrival instruction. Then, the data transmission instruction is parsed and processed by the medium access control layer entity on the base station side to obtain the access network layer data packet. Finally, the access network layer data packet containing the uplink data to be transmitted is parsed and processed by the network layer entity on the base station side to obtain the core network layer data packet (IP data). Multiple terminals can share a single channel that runs through this network layer and the layers below it, which can shorten the transmission latency of the uplink data to be transmitted, effectively ensure the performance of random reporting of massive amounts of terminal data with lower signaling overhead, and improve the transmission efficiency of the system.

[0147] In one embodiment, the uplink data transmission method further includes:

[0148] When there are multiple access network layer data packet fragments, the core network layer data packets are obtained by combining the multiple access network layer data packet fragments.

[0149] In this embodiment of the application, when there are multiple IP packet fragments, the mMTC-ipDRB on the base station side can combine the multiple IP packet fragments to obtain a new complete IP packet.

[0150] According to the above embodiment, the mMTC-ipDRB receives three sets of IP data: IP data 1, IP data 2, and IP data 3. The mMTC-ipDRB determines the IP data by analyzing the "Identifier" field in the header. Fields with the same "Identifier" indicate segmented IP data that needs to be reassembled to restore the original IP data. The "Fragment Offset" field of each IP data segment determines the position of the segmented data within the original IP data. When the last segment is received (the "MF" flag is set to 0), the length of the original IP data can be calculated by multiplying the offset of the last segment by eight and adding the size of the last segment.

[0151] Specifically, the process of reassembling IP data 1, IP data 2, and IP data 3 into a single IP data is as follows: Figure 13 As shown, Figure 13 This is a schematic diagram of IP data packet reassembly provided in an embodiment of this application. First, the "Identifier" field in the IP headers of the three segments is checked; if they are the same, they belong to the same IP data segment. Then, the data area is reassembled based on the "Fragment Offset" field of the three IP data segments. The "Total Length" field in the reassembled IP data header is calculated as: 8 (IP data 3 fragment offset) * 8 + 16 (IP data 3 size) + 20 (reassembled IP header) = 100 bytes. The DF, MF, and fragment offset fields in the IP data header are set to 0, while others remain unchanged. According to the above principles, mMTC-ipDRB assembles IP data 1, IP data 2, and IP data 3 sent from the MAC layer into a single IP data segment, occupying a total of 100 bytes, of which the IP data header occupies 20 bytes and the data area occupies 80 bytes.

[0152] In this embodiment, by combining multiple IP packet fragments to obtain IP packets when there are multiple IP packet fragments, the integrity of uplink data can be guaranteed.

[0153] In one embodiment, Figure 14 This is a flowchart illustrating an uplink data forwarding method provided in an embodiment of this application. The uplink data transmission method further includes:

[0154] S1401. Obtain the server's network address and determine the target tunnel corresponding to the server's network address based on the pre-configured mapping relationship.

[0155] The pre-configured mapping relationship can be established when creating the mMTC-ipDRB entity, based on the network address (IP address) of the server in the configuration module, to create a <server IP address, target tunnel> mapping relationship for each mMTC server, thus forming a corresponding route.

[0156] In this embodiment of the application, the mMTC-ipDRB on the base station side can obtain the IP address of the server from the header of the IP data sent by GFRA-MAC after obtaining the IP data, and determine the target tunnel corresponding to the IP address of the server according to the pre-configured mapping relationship.

[0157] S1402. Send core network layer data packets to the data gateway through the target tunnel, so that the core network layer data packets can be sent to the server through the data gateway.

[0158] In this embodiment, the base station can send core network layer data packets (IP data) to the data gateway via the target tunnel, so that the data gateway can forward the IP data to the mMTC server. Specifically, the mMTC-ipDRB on the base station side sends IP data carrying uplink data to be transmitted to the data gateway via the target tunnel, and the data gateway then forwards the IP data to the mMTC server.

[0159] It should be noted that after receiving the IP data, the mMTC server parses the destination IP address and protocol type in the IP data header, obtaining the destination address as IP01 and the protocol type as 17 (UDP protocol number). Once the server confirms that the obtained IP01 address is its own address, it removes the IP data header and continues transmission to the upper layer. The upper layer parses the UDP header to obtain the server's port number (DPort), removes the UDP header, and hands the appPDU to the upper-layer application corresponding to that DPort for processing. This completes the transmission of the uplink data to be sent.

[0160] In this embodiment, the server's IP address is obtained, and the target tunnel corresponding to the server's IP address is determined according to a pre-configured mapping relationship. Then, IP data is sent to the data gateway through the target tunnel, and the data gateway then sends the IP data to the server. Uplink data (appPDU) sent by the upper-layer application of the mMTC terminal is forwarded through the mMTC terminal, air interface, mMTC base station, tunnel, and data gateway, finally reaching the mMTC server. This allows uplink data to be transmitted through a target tunnel mapped from the server's IP address, shared by multiple mMTC terminals, improving the utilization rate of uplink data transmission resources.

[0161] Figure 15This is a schematic diagram illustrating an end-to-end information exchange process for uplink data, provided as an embodiment of this application. Figure 16 This is the fourth flowchart illustrating an uplink data transmission method provided in this application embodiment, referencing... Figure 15 , Figure 16 As described in the embodiments of this application, the application layer on the mMTC terminal side transmits the appPDU data packet containing information such as UEid and server IP address to the network layer. The network layer transmits the UEid and IP data to the MAC layer. The MAC layer transmits MsgA.req, containing RapID, UEid, and IP data, to the physical layer. The physical layer on the mMTC terminal side transmits the MsgA information to the physical layer on the base station side. After successful decoding, the physical layer on the base station side sends MsgA.ind, containing UEid and IP data, to the MAC layer on the base station side. The MAC layer on the base station side transmits the UEid and IP data to the network layer on the base station side. The network layer on the base station side forwards the IP data to the data gateway through the destination address and destination tunnel of the mMTC server. The data gateway then forwards the IP data to the mMTC server, thereby realizing the uplink data transmission of the mMTC terminal. Specifically, the mMTC terminal and the base station transmit data over the air interface. One or more tunnels with different service qualities are established on the core network between the base station and the data gateway to realize the transmission of IP data.

[0162] In the above embodiments, the scenario where mMTC terminals are sporadically active, have occasional uplink data transmission needs, and send small data packets at a time, can solve the problems of low channel resource utilization and large data transmission latency caused by the need for random access before terminals can send data in existing wireless networks. It avoids the huge difficulties brought about by base stations and core network data gateways configuring a large number of protocol entities for massive mMTC terminal connections, effectively improves the performance of occasional uplink data transmission of terminals in mMTC slices, reduces system operating overhead, and thus reduces communication resource overhead.

[0163] It should be understood that although the steps in the flowcharts of the above embodiments are shown sequentially according to the arrows, these steps are not necessarily executed in the order indicated by the arrows. Unless explicitly stated herein, there is no strict order restriction on the execution of these steps, and they can be executed in other orders. Moreover, at least some steps in the flowcharts of the above embodiments may include multiple steps or multiple stages. These steps or stages are not necessarily completed at the same time, but can be executed at different times. The execution order of these steps or stages is not necessarily sequential, but can be performed alternately or in turn with other steps or at least some of the steps or stages of other steps.

[0164] Based on the same inventive concept, this application also provides an uplink data transmission apparatus for implementing the uplink data transmission method described above. The solution provided by this apparatus is similar to the implementation described in the above method; therefore, the specific limitations in one or more uplink data transmission apparatus embodiments provided below can be found in the limitations of the uplink data transmission method described above, and will not be repeated here.

[0165] In one embodiment, an uplink data transmission device is provided, applied to a terminal, such as... Figure 17 As shown, Figure 17 This is one of the schematic diagrams of an uplink data transmission device provided in an embodiment of this application. The uplink data transmission device 1700 includes: an acquisition module 1701 and a first transmission module 1702, wherein:

[0166] The acquisition module 1701 is used to acquire the uplink data to be sent generated by the application layer.

[0167] The first transmitting module 1702 is used to perform protocol processing on the uplink data to be transmitted based on the terminal-side scheduling-free radio bearer and the base station-side scheduling-free radio bearer. After processing, the terminal-side physical layer entity sends data transmission information to the base station-side physical layer entity via the wireless channel. The data transmission information carries the uplink data to be transmitted and the preamble. After the data transmission information arrives at the base station, the base station forwards the uplink data to be transmitted to the server.

[0168] Among them, the base station-side dispatch-free wireless bearer service serves multiple terminals.

[0169] In one embodiment, the first transmitting module 1702 includes:

[0170] The first generation unit is used to generate access network layer data packets based on the uplink data to be sent by the terminal-side network layer entity.

[0171] The second generation unit is used to generate data transmission instructions based on the access network layer data packets through the terminal-side medium access control layer entity.

[0172] The third generation unit is used to generate data transmission information according to data transmission instructions through the physical layer entity on the terminal side, and send the data transmission information to the base station via the wireless channel.

[0173] In one embodiment, the first generation unit is specifically used to obtain the network address of the server and the network address of the terminal to obtain the header of the access network layer data packet; and to generate the access network layer data packet according to the header of the access network layer data packet and the uplink data to be sent, wherein the access network layer data packet conforms to a first preset format.

[0174] In one embodiment, the second generation unit is specifically used to obtain the preamble number and the terminal identifier; and to generate a data transmission instruction based on the preamble number, the terminal identifier, and the access network layer data packet, wherein the data transmission instruction conforms to a second preset format.

[0175] In one embodiment, the uplink data transmission device 1700 further includes a determining module and a generating module, wherein:

[0176] The determination module is used to segment the access network layer data packet by the terminal-side network layer entity when the length of the access network layer data packet is greater than the preset length, so as to obtain multiple access network layer data packet fragments.

[0177] The generation module is used to generate data transmission instructions corresponding to data packet fragments of each access network network layer through the terminal-side medium access control layer entity.

[0178] In one embodiment, an uplink data transmission device is provided, applied to a base station, such as... Figure 18 As shown, Figure 18 This is a second schematic diagram of an uplink data transmission device provided in an embodiment of this application. The uplink data transmission device 1800 includes a receiving module 1801 and a forwarding module 1802.

[0179] The receiving module 1801 is used to receive data transmission information sent by the physical layer entity on the terminal side via a wireless channel, based on the terminal-side scheduling-free radio bearer and the base station-side scheduling-free radio bearer. The physical layer entity on the base station side, the medium access control layer entity on the base station side, and the network layer entity on the base station side process the data transmission information in sequence to obtain the core network layer data packet. The data transmission information carries uplink data to be sent generated by the application layer on the terminal side.

[0180] Forwarding module 1802 is used to forward core network layer data packets containing uplink data to be sent to the server.

[0181] Among them, the base station-side dispatch-free wireless bearer service serves multiple terminals.

[0182] In one embodiment, the receiving module 1801 includes:

[0183] The first determining unit is used to parse and process the data transmission information through the physical layer entity on the base station side to obtain the data arrival instruction.

[0184] The second determining unit is used to parse and process the data arrival instruction through the base station-side medium access control layer entity to obtain the access network layer data packet containing the uplink data to be sent.

[0185] The third determining unit is used to parse and process the access network layer data packets containing uplink data to be transmitted through the network layer entity on the base station side to obtain the core network layer data packets.

[0186] In one embodiment, the uplink data transmission device 1800 further includes:

[0187] The determination module is used to combine multiple access network layer data packet fragments to obtain core network layer data packets when there are multiple access network layer data packet fragments.

[0188] In one embodiment, the uplink data transmission device 1800 further includes:

[0189] The acquisition unit is used to acquire the network address of the server and determine the target tunnel corresponding to the server's network address according to the pre-configured mapping relationship.

[0190] The sending unit is used to send core network layer data packets to the data gateway through the target tunnel, so that the core network layer data packets can be sent to the server through the data gateway.

[0191] Each module in the aforementioned uplink data transmission device can be implemented entirely or partially through software, hardware, or a combination thereof. These modules can be embedded in the processor of a computer device in hardware form or independent of it, or stored in the memory of a computer device in software form, so that the processor can call and execute the operations corresponding to each module.

[0192] The above embodiments illustrate the uplink data transmission method. Now, an uplink data transmission system is described using one embodiment. In one embodiment, an uplink data transmission system is provided, including: a terminal and a base station;

[0193] A terminal is used to execute the method executed by the terminal in any of the above embodiments.

[0194] A base station is used to execute the method executed by the base station in any of the above embodiments.

[0195] For specific limitations on the uplink data transmission system, please refer to the limitations on the uplink data transmission method mentioned above, which will not be repeated here.

[0196] Those skilled in the art will understand that all or part of the processes in the methods of the above embodiments can be implemented by a computer program instructing related hardware. The computer program can be stored in a non-volatile computer-readable storage medium. When executed, the computer program can include the processes of the embodiments of the above methods. Any references to memory, databases, or other media used in the embodiments provided in this application can include at least one of non-volatile and volatile memory. Non-volatile memory can include read-only memory (ROM), magnetic tape, floppy disk, flash memory, optical memory, high-density embedded non-volatile memory, resistive random access memory (ReRAM), magnetic random access memory (MRAM), ferroelectric random access memory (FRAM), phase change memory (PCM), graphene memory, etc. Volatile memory can include random access memory (RAM) or external cache memory, etc. By way of illustration and not limitation, RAM can take many forms, such as Static Random Access Memory (SRAM) or Dynamic Random Access Memory (DRAM). The databases involved in the embodiments provided in this application may include at least one type of relational database and non-relational database. Non-relational databases may include, but are not limited to, blockchain-based distributed databases. The processors involved in the embodiments provided in this application may be general-purpose processors, central processing units, graphics processing units, digital signal processors, programmable logic devices, quantum computing-based data processing logic devices, etc., and are not limited to these.

[0197] The technical features of the above embodiments can be combined in any way. For the sake of brevity, not all possible combinations of the technical features in the above embodiments are described. However, as long as there is no contradiction in the combination of these technical features, they should be considered to be within the scope of this specification.

[0198] The above embodiments are merely illustrative of several implementation methods of this application, and their descriptions are relatively specific and detailed. However, they should not be construed as limiting the scope of this application. It should be noted that those skilled in the art can make various modifications and improvements without departing from the concept of this application, and these all fall within the protection scope of this application. Therefore, the protection scope of this application should be determined by the appended claims.

Claims

1. An uplink data transmission method, characterized in that, Applied to a terminal, the method includes: Obtain the uplink data to be sent generated by the application layer; the uplink data to be sent is obtained after obtaining the resource configuration information broadcast by the radio resource control layer on the base station side, and the resource configuration information is used for uplink scheduling-free operation; Based on the terminal-side and base station-side dispatch-free radio bearers, after the uplink data to be transmitted is processed by the protocol, the terminal-side physical layer entity sends data transmission information to the base station-side physical layer entity via the wireless channel; the data transmission information carries the uplink data to be transmitted and a preamble; after the data transmission information arrives at the base station, the base station forwards the uplink data to be transmitted to the server; the terminal-side dispatch-free radio bearer is pre-established in the terminal access network protocol, and the base station-side dispatch-free radio bearer is pre-established in the base station access network protocol stack; The base station provides dispatch-free wireless bearer services to multiple terminals; the terminals are virtual access devices.

2. The method according to claim 1, characterized in that, The terminal-side dispatch-free radio bearer includes a terminal-side network layer entity, a terminal-side medium access control layer entity, and a terminal-side physical layer entity. The terminal-side dispatch-free radio bearer is a radio bearer pre-established in the access network protocol stack according to a dispatch-free random access protocol. Based on the terminal-side dispatch-free radio bearer and the base station-side dispatch-free radio bearer, after protocol processing of the uplink data to be transmitted, the terminal-side physical layer entity sends data transmission information to the base station-side physical layer entity via a wireless channel, including: The terminal-side network layer entity generates access network layer data packets based on the uplink data to be sent. The terminal-side medium access control layer entity generates data transmission instructions based on the access network layer data packets. The terminal-side physical layer entity generates the data transmission information according to the data transmission instruction, and sends the data transmission information to the base station via a wireless channel.

3. The method according to claim 2, characterized in that, The step of generating access network layer data packets by the terminal-side network layer entity based on the uplink data to be sent includes: The header of the access network layer data packet is obtained by acquiring the network address of the server and the network address of the terminal; The access network layer data packet is generated based on the header of the access network layer data packet and the uplink data to be sent, and the access network layer data packet conforms to a first preset format.

4. The method according to claim 2, characterized in that, The step of generating data transmission instructions based on the access network layer data packets by the terminal-side medium access control layer entity includes: Obtain the preamble number and terminal identifier; The data transmission instruction is generated based on the preamble number, the terminal identifier, and the access network layer data packet, and the data transmission instruction conforms to a second preset format.

5. The method according to claim 2, characterized in that, The step of generating data transmission instructions based on the access network layer data packets by the terminal-side medium access control layer entity includes: When the length of the access network layer data packet is greater than a preset length, the access network layer data packet is segmented by the terminal-side network layer entity to obtain multiple access network layer data packet fragments. The terminal-side media access control layer entity generates data transmission instructions corresponding to each access network layer data packet fragment.

6. An uplink data transmission method, characterized in that, Applied to a base station, the method includes: Based on terminal-side and base station-side dispatch-free radio bearers, the base station-side physical layer entity receives data transmission information sent by the terminal-side physical layer entity via a wireless channel. The base station-side physical layer entity, base station-side medium access control layer entity, and base station-side network layer entity process the data transmission information sequentially to obtain a core network layer data packet. The data transmission information carries uplink data to be sent generated by the terminal-side application layer. The uplink data to be sent is obtained by the terminal after acquiring resource configuration information broadcast by the base station-side radio resource control layer. This resource configuration information is used for uplink dispatch-free operation. The terminal-side dispatch-free radio bearer is pre-established in the terminal access network protocol, and the base station-side dispatch-free radio bearer is pre-established in the base station access network protocol stack. The core network layer data packet containing the uplink data to be sent is forwarded to the server. The base station provides dispatch-free wireless bearer services to multiple terminals; the terminals are virtual access devices.

7. The method according to claim 6, characterized in that, The base station-side dispatch-free radio bearer includes a base station-side network layer entity, a base station-side medium access control layer entity, and a base station-side physical layer entity. The base station-side dispatch-free radio bearer is a radio bearer pre-established in the access network protocol stack according to a dispatch-free random access protocol. Based on the terminal-side dispatch-free radio bearer and the base station-side dispatch-free radio bearer, the base station-side physical layer entity receives data transmission information sent by the terminal-side physical layer entity via a wireless channel. The base station-side physical layer entity, the base station-side medium access control layer entity, and the base station-side network layer entity process the data transmission information sequentially to obtain a core network layer data packet, including: The data transmission information is received by the physical layer entity on the base station side, and the data transmission information is parsed and processed to obtain the data arrival instruction; The base station-side medium access control layer entity parses and processes the data arrival instruction to obtain an access network layer data packet containing the uplink data to be sent. The core network layer data packet is obtained by parsing the access network layer data packet containing the uplink data to be transmitted through the network layer entity on the base station side.

8. The method according to claim 7, characterized in that, The method further includes: In the case of multiple access network layer data packet fragments, the multiple access network layer data packet fragments are combined to obtain the core network layer data packet.

9. The method according to claim 7, characterized in that, The method further includes: Obtain the network address of the server, and determine the target tunnel corresponding to the network address of the server according to the pre-configured mapping relationship; The core network layer data packets are sent to the data gateway through the target tunnel, and then sent to the server through the data gateway.

10. An uplink data transmission system, characterized in that, The uplink data transmission system includes a terminal and a base station; The terminal is used to perform the method according to any one of claims 1 to 5; The base station is used to perform the method according to any one of claims 6 to 9.

Images