A data transmission method, device, network device, and terminal

Abstract

An embodiment of the present application provides a data transmission method, apparatus, network device, and terminal. The method includes: a target base station receives first indication information sent by a terminal, where the first indication information is used to indicate the number of small packet data to be sent by the terminal and / or whether there is small packet data to be sent; the target base station sends first configuration information to the terminal, where the first configuration information is used for the terminal to determine at least one uplink transmission resource corresponding to at least one small packet data to be sent.

Description

[0001] This application is a divisional application of a patent application with an application number of 201980096075.5 and an invention title of "A Data Transmission Method, Device, Network Equipment, and Terminal", which was filed on July 4, 2019. Technical Field

[0002] Embodiments of this application relate to the field of mobile communication technologies, and specifically relate to a data transmission method, device, network equipment, and terminal. Background Art

[0003] In Long Term Evolution (LTE), Early Data Transmission (EDT) is introduced. EDT data transmission is also referred to as small data transmission or small packet transmission or small packet data transmission. For uplink small packet data transmission, currently only the transmission of one small packet of data is supported. However, in some actual scenarios, there may be a situation of continuous transmission of multiple small packets of data. How to achieve the continuous transmission of multiple small packets of data needs to be clarified. Summary of the Invention

[0004] Embodiments of this application provide a data transmission method, device, network equipment, and terminal.

[0005] The data transmission method provided by embodiments of this application includes:

[0006] A target base station receives first indication information sent by a terminal, where the first indication information is used to indicate the number of small packets of data to be sent by the terminal and / or whether there is small packet data to be sent;

[0007] The target base station sends first configuration information to the terminal, where the first configuration information is used for the terminal to determine at least one uplink transmission resource corresponding to at least one small packet of data to be sent.

[0008] The data transmission method provided by embodiments of this application includes:

[0009] The terminal sends first indication information to a target base station, where the first indication information is used to indicate the number of small packets of data to be sent by the terminal and / or whether there is small packet data to be sent;

[0010] The terminal receives the first configuration information sent by the target base station, where the first configuration information is used for the terminal to determine at least one uplink transmission resource corresponding to at least one small packet of data to be sent.

[0011] The data transmission device provided by embodiments of this application includes:

[0012] A receiving unit, configured to receive first indication information sent by a terminal, where the first indication information is used to indicate the number of small packet data to be sent by the terminal and / or whether there is small packet data to be sent;

[0013] A sending unit, configured to send first configuration information to the terminal, where the first configuration information is used for the terminal to determine at least one uplink transmission resource corresponding to at least one small packet data to be sent.

[0014] The data transmission device provided by an embodiment of this application includes:

[0015] A sending unit, configured to send first indication information to a target base station, where the first indication information is used to indicate the number of small packet data to be sent by the terminal and / or whether there is small packet data to be sent;

[0016] A receiving unit, configured to receive first configuration information sent by the target base station, where the first configuration information is used for the terminal to determine at least one uplink transmission resource corresponding to at least one small packet data to be sent.

[0017] The network device provided by an embodiment of this application includes a processor and a memory. The memory is used to store a computer program, and the processor is used to call and run the computer program stored in the memory to execute the above data transmission method.

[0018] The terminal provided by an embodiment of this application includes a processor and a memory. The memory is used to store a computer program, and the processor is used to call and run the computer program stored in the memory to execute the above data transmission method.

[0019] The chip provided by an embodiment of this application is used to implement the above data transmission method.

[0020] Specifically, the chip includes: a processor, configured to call and run a computer program from a memory, so that a device installed with the chip executes the above data transmission method.

[0021] The computer-readable storage medium provided by an embodiment of this application is used to store a computer program, and the computer program enables a computer to execute the above data transmission method.

[0022] The computer program product provided by an embodiment of this application includes computer program instructions, and the computer program instructions enable a computer to execute the above data transmission method.

[0023] The computer program provided by an embodiment of this application, when running on a computer, enables the computer to execute the above data transmission method.

[0024] With the above technical solution, when there are multiple consecutive small packet data to be sent at the terminal, the terminal sends a first indication message to the target base station, and the first indication message is used to indicate the number of small packet data to be sent by the terminal and / or whether there is small packet data to be sent. In this way, the target base station configures at least one uplink transmission resource corresponding to at least one small packet data to be sent according to the first indication message, ensuring the efficient transmission of small packet data. BRIEF DESCRIPTION OF THE DRAWINGS

[0025] The drawings described herein are used to provide a further understanding of the present application and constitute a part of the present application. The illustrative embodiments of the present application and their descriptions are used to explain the present application and do not constitute an improper limitation of the present application. In the drawings:

[0026] Figure 1 is a schematic diagram of a communication system architecture provided by an embodiment of the present application;

[0027] Figure 2-1 is a flowchart of an RNAU with context transfer provided by an embodiment of the present application;

[0028] Figure 2-2 is a flowchart of an RNAU without context transfer provided by an embodiment of the present application;

[0029] Figure 3 is a flowchart of user plane transmission of EDT data provided by an embodiment of the present application;

[0030] Figure 4 is a schematic flowchart of a data transmission method provided by an embodiment of the present application;

[0031] Figure 5-1 is a schematic diagram of uplink data transmission provided by an embodiment of the present application Figure 1 ;

[0032] Figure 5-2 is a second schematic diagram of uplink data transmission provided by an embodiment of the present application;

[0033] Figure 6 is a schematic diagram of the structural composition of a data transmission device provided by an embodiment of the present application Figure 1 ;

[0034] Figure 7 is a second schematic diagram of the structural composition of a data transmission device provided by an embodiment of the present application;

[0035] Figure 8 is a schematic structural diagram of a communication device provided by an embodiment of the present application;

[0036] Figure 9 is a schematic structural diagram of a chip provided by an embodiment of the present application;

[0037] Figure 10 It is a schematic block diagram of a communication system provided by an embodiment of the present application. Detailed implementation manners

[0038] Next, the technical solutions in the embodiments of the present application will be described with reference to the accompanying drawings in the embodiments of the present application. Obviously, the described embodiments are part of the embodiments of the present application, rather than all the embodiments. All other embodiments obtained by those of ordinary skill in the art based on the embodiments in the present application without creative efforts shall fall within the protection scope of the present application.

[0039] The technical solutions of the embodiments of the present application can be applied to various communication systems, such as: Global System of Mobile communication (GSM) system, Code Division Multiple Access (CDMA) system, Wideband Code Division Multiple Access (WCDMA) system, General Packet Radio Service (GPRS), Long Term Evolution (LTE) system, LTE Frequency Division Duplex (FDD) system, LTE Time Division Duplex (TDD), Universal Mobile Telecommunication System (UMTS), Worldwide Interoperability for Microwave Access (WiMAX) communication system or 5G system, etc.

[0040] Exemplarily, the communication system 100 to which the embodiments of the present application are applied is as Figure 1As shown. The communication system 100 may include a network device 110, which may be a device communicating with a terminal 120 (or referred to as a communication terminal, terminal). The network device 110 may provide communication coverage for a specific geographical area and may communicate with terminals located within the coverage area. Optionally, the network device 110 may be a Base Transceiver Station (BTS) in a GSM system or a CDMA system, may also be a Node B (NB) in a WCDMA system, may further be an Evolutional Node B (eNB or eNodeB) in an LTE system, or a radio controller in a Cloud Radio Access Network (CRAN), or the network device may be a mobile switching center, a relay station, an access point, a vehicle-mounted device, a wearable device, a hub, a switch, a bridge, a router, a network-side device in a 5G network, or a network device in a future-evolved Public Land Mobile Network (PLMN), etc.

[0041] The communication system 100 further includes at least one terminal 120 within the coverage area of the network device 110. As used herein, "terminal" includes, but is not limited to, being connected via a wired line, such as via a Public Switched Telephone Networks (PSTN), Digital Subscriber Line (DSL), digital cable, direct cable connection; and / or another data connection / network; and / or via a wireless interface, such as, for a cellular network, Wireless Local Area Network (WLAN), digital television network such as a DVB-H network, satellite network, AM-FM broadcast transmitter; and / or a device configured to receive / transmit communication signals for another terminal; and / or an Internet of Things (IoT) device. A terminal configured to communicate via a wireless interface may be referred to as a "wireless communication terminal", "wireless terminal" or "mobile terminal". Examples of mobile terminals include, but are not limited to, satellite or cellular telephones; Personal Communications System (PCS) terminals that may combine cellular radiotelephone with data processing, facsimile, and data communication capabilities; PDAs that may include a radiotelephone, pager, Internet / intranet access, Web browser, notepad, calendar, and / or Global Positioning System (GPS) receiver; and conventional laptop and / or palmtop receivers or other electronic devices including a radiotelephone transceiver. A terminal may refer to an access terminal, User Equipment (UE), user unit, user station, mobile station, mobile unit, remote station, remote terminal, mobile device, user terminal, terminal, wireless communication device, user agent, or user device. An access terminal may be a cellular phone, cordless phone, Session Initiation Protocol (SIP) phone, Wireless Local Loop (WLL) station, Personal Digital Assistant (PDA), a handheld device with wireless communication capabilities, a computing device or other processing device connected to a wireless modem, in-vehicle device, wearable device, a terminal in a 5G network, or a terminal in a future evolved PLMN, etc.

[0042] Optionally, Device to Device (D2D) communication may be performed between the terminals 120.

[0043] Optionally, the 5G system or 5G network may also be referred to as a New Radio (NR) system or NR network.

[0044] Figure 1 Exemplarily, one network device and two terminals are shown. Optionally, the communication system 100 may include multiple network devices, and the coverage range of each network device may include other numbers of terminals. The embodiments of the present application do not limit this.

[0045] Optionally, the communication system 100 may further include other network entities such as a network controller and a mobility management entity. The embodiments of the present application do not limit this.

[0046] It should be understood that in the embodiments of the present application, a device with communication functions in a network / system may be referred to as a communication device. Taking Figure 1 the shown communication system 100 as an example, the communication device may include a network device 110 and a terminal 120 with communication functions. The network device 110 and the terminal 120 may be the specific devices described above and will not be elaborated here; the communication device may also include other devices in the communication system 100, such as other network entities such as a network controller and a mobility management entity. The embodiments of the present application do not limit this.

[0047] It should be understood that the terms "system" and "network" are often used interchangeably in this article. The term " / and" in this article is merely a description of the association relationship between associated objects, indicating that there can be three relationships. For example, A and / or B may represent: A exists alone, A and B exist simultaneously, and B exists alone. In addition, the character " / " in this article generally represents an "or" relationship between the associated objects before and after.

[0048] To facilitate understanding of the technical solutions of the embodiments of the present application, the following describes the technical solutions related to the embodiments of the present application.

[0049] Three RRC states

[0050] In a 5G network environment, for the purpose of reducing air interface signaling and quickly restoring a wireless connection and quickly resuming data services, a new RRC state, namely the RRC Inactive (RRC_INACTIVE) state, is defined. This state is different from the RRC Idle (RRC_IDLE) state and the RRC Connected (RRC_CONNECTED) state.

[0051] The following describes the three RRC states in a 5G network environment:

[0052] 1) RRC_IDLE state (hereinafter referred to as the idle state): The mobility is based on UE cell selection and reselection. Paging is initiated by the Core Network (CN), and the paging area is configured by the CN. There is no UE AS context on the base station side. There is no RRC connection.

[0053] 2) RRC_CONNECTED state (hereinafter referred to as the connected state): There is an RRC connection, and there is a UE AS context between the base station and the UE. The network side knows the location of the UE at the specific cell level. The mobility is network-side controlled mobility. Unicast data can be transmitted between the UE and the base station.

[0054] 3) RRC_INACTIVE state (hereinafter referred to as the inactive state): The mobility is based on UE cell selection and reselection. There is a connection between the CN and the RAN. The UE AS context exists on a certain base station. Paging is triggered by the RAN, and the RAN-based paging area is managed by the RAN. The network side knows the location of the UE at the RAN-based paging area level.

[0055] When the UE is in the inactive state, the following situations trigger the UE to return to the idle state: 1) When receiving the initial paging message from the CN; 2) When initiating an RRC resume request, start timer T319, if the timer expires; 3) When the MSG4 integrity protection verification fails; 4) When the cell reselects to another Radio Access Technology (RAT); 5) When entering the state of camping on any cell.

[0056] RAN Notification Area (RNA)

[0057] When the UE is in the inactive state, the network side configures the configuration parameters for the inactive state for the UE through RRC dedicated signaling (such as the RRC release message). The main configuration parameters include: 1) Inactive Radio Network Temporary Identifier (I-RNTI). The I-RNTI is used to identify the UE inactive state context of the UE at the base station side and is unique within the base station. 2) RNA. The RNA is used to control the area where the UE performs cell selection and reselection in the inactive state and is also the paging range area for the initial paging of the RAN. 3) RAN Discontinuous Reception cycle (RAN DRX cycle). The RAN DRX cycle is used to calculate the paging occasion for the initial paging of the RAN. 4) RNA Update periodicity (RNAU periodicity). The RNAU periodicity is used to control the period for the UE to perform periodic RAN location updates. 5) Next hop Chaining Counter (NCC). The NCC is used for the key used in the RRC connection recovery process.

[0058] When the UE moves within the RNA area, it does not need to notify the network side and follows the mobility behavior in the idle state, that is, the cell selection and reselection principle. When the UE moves out of the paging area configured by the RAN, it will trigger the UE to resume the RRC connection and re-obtain the paging area configured by the RAN. When downlink data arrives for the UE, the base station that maintains the connection between the RAN and the CN for the UE will trigger all cells within the RAN paging area to send paging messages to the UE, enabling the inactive UE to resume the RRC connection and receive data. On the other hand, the inactive UE is configured with a RAN paging area. To ensure the reachability of the UE within this area, the UE needs to perform periodic location updates according to the period configured by the network (implemented based on the RNAU timer). Therefore, the scenarios that trigger the UE to perform RNAU are the timeout of the RNAU timer or the UE moving to an area outside the RNA.

[0059] When the target base station for the UE to initiate the RRC connection recovery process is not the anchor base station, the anchor base station determines whether it is necessary to transfer the UE context to the target base station side. Therefore, generally, the target base station will carry the cause value carried in the RRC connection recovery request message initiated by the UE in the message requesting the UE context and send it to the anchor base station, and the anchor base station determines whether it is necessary to transfer the UE context to the target base station side. The following takes the RNAU process as an example to illustrate the UE context transfer.

[0060] Figure 2-1Flowchart of RNAU with context transfer, including the following steps:

[0061] 1. The UE sends an RRC Resume Request message to the target base station.

[0062] Here, the RRC Resume Request message carries the cause value for RRC resume, i.e., RNAU.

[0063] 2. The target base station sends a RETRIEVE UE CONTEXT REQUEST message to the anchor base station.

[0064] Here, the RETRIEVE UE CONTEXT REQUEST message carries the information: RNAU.

[0065] 3. The anchor base station sends a RETRIEVE UE CONTEXT RESPONSE message to the target base station.

[0066] 4. The target base station restores the UE context.

[0067] 5. The target base station sends DATA FORWARDING ADDRESS INDICATION to the anchor base station.

[0068] 6. The target base station sends a PATH SWITCH REQUEST message to the Access and Mobility Management Function (AMF).

[0069] 7. The AMF sends a PATH SWITCH REQUEST RESPONSE message to the target base station.

[0070] 8. The target base station sends an RRC Release message to the UE, and the RRC Release message carries a Suspend Indication.

[0071] 9. The target base station sends a UE CONTEXT RELEASE message to the anchor base station.

[0072] Figure 2-2 Flowchart of RNAU without context transfer, including the following steps:

[0073] 1. The UE sends an RRC Resume Request message to the target base station.

[0074] Here, the RRC resume request message carries the cause value for RRC resume, i.e., RNAU.

[0075] 2. The target base station sends a RETRIEVE UE CONTEXT REQUEST message to the anchor base station.

[0076] Here, the RETRIEVE UE CONTEXT REQUEST message carries the information: RNAU.

[0077] 3. The anchor base station sends a RETRIEVE UE CONTEXT FAILURE message to the target base station.

[0078] 4. The target base station sends an RRC Release message to the UE, and the RRC Release message carries Suspend Indication.

[0079] It should be noted that Figure 2-1 and Figure 2-2 the anchor base station mentioned refers to the base station storing the UE context. In one example, the anchor base station is the base station that served the UE last time.

[0080] EDT data transmission

[0081] EDT data transmission is introduced in LTE. During the EDT data transmission process, the UE may always remain in the idle state or the suspend state or the inactive state to complete the uplink and / or downlink EDT data transmission.

[0082] The EDT data transmission can adopt a user plane transmission scheme. As Figure 3 shown, it includes the following steps:

[0083] 1. The UE sends an RRCConnectionResumeRequest message and uplink data to the eNB.

[0084] Here, the RRCConnectionResumeRequest carries the following information: resumeID, resumeCause, shortResumeMAC-I.

[0085] 2. The eNB sends a UE Context Resume Request message to the MME.

[0086] 3. The MME modifies the bearer with the S-GW.

[0087] 4. The MME sends a UE Context Resume Response message to the eNB.

[0088] 5. The eNB sends uplink data to the S-GW.

[0089] 6. The S-GW sends downlink data to the eNB.

[0090] 7. A bearer is modified between the MME and the S-GW, and an S1 Suspend procedure is performed between the eNB and the MME.

[0091] 8. The eNB sends an RRCConnectionRelease message and downlink data to the UE.

[0092] Here, the RRCConnectionRelease message carries the following information: releaseCause, releaseID, NCC.

[0093] It should be noted that Figure 3 this is illustrated by taking LTE as an example. The principle for NR is the same as that for LTE. The difference is that for NR, the eNB needs to be replaced by the gNB, the Mobility Management Entity (MME) needs to be replaced by the Access and Mobility Management Function (AMF), and the Serving Gateway (S-GW) needs to be replaced by the User Plane Function (UPF).

[0094] In Figure 3In it, the RRC connection restoration request message is carried in MSG3 of the random access procedure, and the uplink data belongs to the user plane data. Among them, the uplink data is transmitted in the Dedicated Transmission Channel (DTCH), the RRC connection restoration request message is transmitted in the Common Control Channel (CCCH), and the MAC SDU corresponding to the uplink data (i.e., DTCH SDU) and the MAC SDU corresponding to the RRC connection restoration request message (i.e., CCCH SDU) are multiplexed in the same MAC PDU at the MAC layer. Similarly for the downlink and uplink, the downlink data is transmitted in the DTCH, the RRC connection release message is transmitted in the CCCH, and the MAC SDU corresponding to the downlink data (i.e., DTCH SDU) and the MAC SDU corresponding to the RRC connection release message (i.e., CCCH SDU) are multiplexed in the same MAC PDU at the MAC layer. It should be noted that Figure 3 The uplink data or downlink data in it can be small packet data. Here, the small packet data is also called small data or small data packet or EDT data.

[0095] For the transmission of uplink small packet data, currently only the transmission of one small packet data is supported. However, in some actual scenarios, there may be a situation where several small packet data are transmitted continuously. At this time, the terminal can only enter the connected state, and then after transmitting the data through the dedicated bearer, enter the idle state or the inactive state again, increasing the signaling overhead and UE power consumption. For this reason, the following technical solutions of the embodiments of this application are proposed. The technical solutions of the embodiments of this application propose a new transmission method for small packet data, support the transmission of multiple consecutive small packet data, expand the scenario of small packet data transmission, make EDT more widely used, and better reduce the signaling overhead and UE power consumption.

[0096] Figure 4 It is a schematic flow diagram of the data transmission method provided by the embodiments of this application, as Figure 4 shown, the data transmission method includes the following steps:

[0097] Step 401: The terminal sends a first indication message to the target base station, and the target base station receives the first indication message sent by the terminal. The first indication message is used to indicate the number of small packet data to be sent by the terminal and / or whether there is small packet data to be sent.

[0098] In the embodiments of this application, the terminal can be any device capable of communicating with the network, such as a mobile phone, a tablet computer, a notebook, a vehicle-mounted terminal, a wearable device, etc. In an optional implementation manner, the terminal is a terminal in the inactive state.

[0099] In an embodiment of the present application, when the terminal is in an inactive state and there are N small packet data to be sent (N is a positive integer), the terminal initiates a random access process. Specifically, the terminal sends an RRC resume request message to the target base station. During or after the random access process, the terminal sends first indication information to the target base station, and indicates the number of small packet data to be sent by the terminal (that is, how many small packet data the terminal has to send) and / or whether there is small packet data to be sent (that is, whether there is small packet data to be sent subsequently) to the target base station through the first indication information.

[0100] It should be noted that the random access process initiated by the terminal may be a two-step random access process based on contention (hereinafter referred to as the two-step random access process), or a four-step random access process based on contention (hereinafter referred to as the four-step random access process).

[0101] Among them, the four-step random access process includes the following steps: (1) The UE sends MSG1 to the base station. (2) The base station sends MSG2 to the UE. (3) The UE sends MSG3 to the base station. (4) The base station sends MSG4 to the UE. By combining MSG1 and MSG3 in the four-step random access process, MSGA in the two-step random access process can be obtained. By combining MSG2 and MSG4 in the four-step random access process, MSGB in the two-step random access process can be obtained. It can be seen that the two-step random access process includes the following steps: (1) The UE sends MSGA to the base station. (2) The base station sends MSGB to the UE.

[0102] In an embodiment of the present application, the first indication information can be implemented in any one of the following ways or a combination of any multiple ways:

[0103] Method 1: The terminal sends a first preamble to the target base station on a first Physical Random Access Channel (PRACH) resource. The target base station receives the first preamble sent by the terminal on the first PRACH resource. The first PRACH resource and / or the first preamble has an association relationship with the number of small packet data to be sent by the terminal. The target base station determines the number of small packet data to be sent by the terminal based on the first PRACH resource and / or the first preamble.

[0104] Here, the association relationship is configured by the second configuration information. Specifically, the target base station sends the second configuration information to the terminal, and the terminal receives the second configuration information sent by the target base station. The second configuration information is used for the terminal to determine the association relationship between the number of small packet data to be sent and the first PRACH resource and / or the first preamble. Based on this, the terminal determines (or selects) the first PRACH resource and / or the first preamble based on the second configuration information and the number of small packet data to be sent.

[0105] In an alternative embodiment, the second configuration information is configured by a system broadcast message or dedicated signaling.

[0106] Method 2: The terminal sends a first message to the target base station, and the target base station receives the first message sent by the terminal. The first message carries the first indication information. The first message is MSG3 in the 4-step random access procedure; or, the first message is MSGA in the 2-step random access procedure.

[0107] Here, if it is a 2-step random access procedure, the first indication information is carried in the payload of MSGA.

[0108] Method 3: The terminal sends uplink data or uplink signaling to the target base station, and the target base station receives the uplink data or uplink signaling sent by the terminal. The MAC SDU corresponding to the uplink data or uplink signaling is multiplexed with the first MAC CE in the same MAC PDU, and the first MAC CE carries the first indication information.

[0109] Here, the first MAC CE is a newly defined uplink MAC CE, and the first indication information is carried in this uplink MAC CE.

[0110] Method 4: The terminal sends uplink data or uplink signaling to the target base station, and the target base station receives the uplink data or uplink signaling sent by the terminal. The MAC SDU corresponding to the uplink data or uplink signaling is multiplexed with the second MAC CE in the same MAC PDU, and the second MAC CE carries a Buffer Status Report (BSR), and the BSR indicates the existence of small packet data to be sent and / or the number of small packet data to be sent.

[0111] Here, the second MAC CE is an existing MAC CE, called the BSR MAC CE, and the BSR in the BSR MAC CE indicates the existence of small packet data to be sent and / or the number of small packet data to be sent.

[0112] Method 5: The terminal sends a first data packet to the target base station, and the target base station receives the first data packet sent by the terminal. The first indication information is carried in the packet header of the first data packet. Further, the packet header is a PDCP packet header or an RLC packet header.

[0113] Method 6: The terminal sends a control PDU to the target base station, and the target base station receives the control PDU sent by the terminal. The control PDU carries the first indication information. Further, the control PDU is a PDCP control PDU or an RLC control PDU.

[0114] In the embodiments of this application, the target base station receives the RRC resume request message sent by the terminal; the target base station obtains a first terminal identifier (such as I-RNTI) from the RRC resume request message, addresses the anchor base station according to the first terminal identifier, and sends a request message for the terminal context to the anchor base station; wherein, if the anchor base station determines to send the context of the terminal to the target base station, the target base station resumes the context of the terminal; if the anchor base station determines not to send the context of the terminal to the target base station, the anchor base station resumes the context of the terminal. Here, the RRC resume request message is carried in MSG3 in the 4-step random access procedure; or, the RRC resume request message is carried in MSGA in the 2-step random access procedure.

[0115] For example: 1) After receiving the RRC resume request message, the target base station decodes the message to obtain the identifier of the UE (i.e., I-RNTI). The target base station addresses the anchor base station according to the I-RNTI and sends a RETRIEVE UE CONTEXT REQUEST message to the anchor base station. 2) The anchor base station decides whether to migrate the UE context. If it decides to migrate the UE context, the anchor base station replies to the target base station with a RETRIEVE UE CONTEXT RESPONSE message and transfers the UE context to the target base station. If it decides not to migrate the UE context, the anchor base station replies to the target base station with a RETRIEVE UE CONTEXT FAILURE message. 3) If the UE context is migrated, after receiving the UE context sent by the anchor base station, the target base station resumes the UE context (such as resuming security, resuming DRB configuration, resuming SRB configuration, etc.). If the UE context is not migrated, the anchor base station resumes the UE context (such as resuming security, resuming DRB configuration, resuming SRB configuration, etc.).

[0116] Step 402: The target base station sends first configuration information to the terminal, and the terminal receives the first configuration information sent by the target base station. The first configuration information is used for the terminal to determine at least one uplink transmission resource corresponding to at least one small packet of data to be sent.

[0117] In the embodiments of the present application, the first configuration information can be implemented in any of the following ways:

[0118] Way I): The target base station sends a static configuration instruction to the terminal, and the terminal receives the static configuration instruction sent by the target base station. The static configuration instruction carries the first configuration information. Further, the static configuration instruction is an RRC message; the RRC message is MSG4 in the 4-step random access procedure; or, the second message is MSGB in the 2-step random access procedure.

[0119] For Way I), the target base station configures one or more uplink transmission resources (i.e., uplink grants) for the terminal in a pre-configured manner.

[0120] Way II): The target base station sends a dynamic scheduling instruction to the terminal, and the terminal receives the dynamic scheduling instruction sent by the target base station. The dynamic scheduling instruction carries the first configuration information. Further, the dynamic scheduling instruction is a DCI.

[0121] For Way II), the target base station schedules one or more UL grants for the terminal in a dynamic scheduling manner.

[0122] It should be noted that Way I) and Way II) in Step 402 can be combined with Ways 1 to 6 in Step 401 in any combination for implementation. For example: In the case of implementing the first indication information through Way 1 or Way 2, Way I) or Way II) can be used to schedule the UL grant. Another example: In the case of implementing the first indication information through Way 3 or Way 4 or Way 5 or Way 6, Way II) can be used to schedule the UL grant.

[0123] In the embodiments of the present application, the uplink transmission resource (i.e., UL grant) refers to a Physical Uplink Shared Channel (PUSCH) resource. The target base station can configure the correspondence between the preamble and the PUSCH. There can be a correspondence where one preamble corresponds to one or more PUSCHs. In this way, if the terminal has multiple small packets of data to be sent, it can select multiple PUSCH resources to send multiple small packets of data.

[0124] It should be noted that when the terminal in the embodiment of this application sends small packet data, it is in the inactive state, that is, the UL grant scheduled by the target base station is used for the inactive terminal to send small packet data. The following combines Figure 5-1 and Figure 5-2 to illustrate the situation of UL grant and small packet data transmission.

[0125] Referring to Figure 5-1 , the process is as follows: 1. When the UE is in the inactive state and there are X small packet data to be sent, it sends an RRC resume request message to the target base station. 2. The target base station sends a request message for asking for the UE context to the anchor base station. 3. The anchor base station decides to migrate the UE context and replies to the target base station with a response message for asking for the UE context. 4. The target base station resumes the UE context and initiates a path conversion process to the AMF. 5. The target base station sends a UL grant to the UE, and the UE sends uplink data based on the UL grant. Here, the uplink data refers to small packet data. The target base station can send the UL grant to the UE multiple times, so that the UE can continuously send multiple uplink data. 6. The target base station sends an RRC connection release message to the UE.

[0126] Referring to Figure 5-2 , the process is as follows: 1. When the UE is in the inactive state and there are X small packet data to be sent, it sends an RRC resume request message to the target base station. 2. The target base station sends a request message for asking for the UE context to the anchor base station. 3. The anchor base station decides to migrate the UE context and replies to the target base station with a response message for asking for the UE context. 4. The target base station resumes the UE context and initiates a path conversion process to the AMF. 5. The target base station sends an RRC connection release message to the UE. 6. The target base station sends a UL grant to the UE, and the UE sends uplink data based on the UL grant. Here, the uplink data refers to small packet data. The target base station can send the UL grant to the UE multiple times, so that the UE can continuously send multiple uplink data.

[0127] It should be noted that Figure 5-1 and Figure 5-2 in the processes shown, the target base station dynamically schedules the UL grant to the terminal multiple times. The embodiment of this application is not limited to this. The target base station can also schedule multiple UL grants to the terminal at one time, that is, the target base station uses a pre-configured method to configure one or more UL grants for the terminal at one time.

[0128] Figure 6 is a schematic structural composition of the data transmission device provided by the embodiment of this application Figure 1 , as Figure 6 shown, the data transmission device includes:

[0129] A receiving unit 601, configured to receive first indication information sent by a terminal, where the first indication information is used to indicate the number of small packet data to be sent by the terminal and / or whether there is small packet data to be sent;

[0130] A sending unit 602, configured to send first configuration information to the terminal, where the first configuration information is used for the terminal to determine at least one uplink transmission resource corresponding to at least one small packet data to be sent.

[0131] In an embodiment, the receiving unit 601 is configured to receive a first preamble sent by the terminal on a first PRACH resource, where the first PRACH resource and / or the first preamble has an association relationship with the number of small packet data to be sent by the terminal;

[0132] The apparatus further includes: a determining unit 603, configured to determine the number of small packet data to be sent by the terminal based on the first PRACH resource and / or the first preamble.

[0133] In an embodiment, the sending unit 602 is configured to send second configuration information to the terminal, where the second configuration information is used for the terminal to determine the association relationship between the number of small packet data to be sent and the first PRACH resource and / or the first preamble.

[0134] In an embodiment, the second configuration information is configured by a system broadcast message or dedicated signaling.

[0135] In an embodiment, the receiving unit 601 is configured to receive a first message sent by the terminal, where the first message carries the first indication information.

[0136] In an embodiment, the first message is MSG3 in a 4-step random access procedure; or, the first message is MSGA in a 2-step random access procedure.

[0137] In an embodiment, the receiving unit 601 is configured to receive uplink data or uplink signaling sent by the terminal, where the MAC SDU corresponding to the uplink data or uplink signaling is multiplexed with a first MAC CE in the same MAC PDU, and the first MAC CE carries the first indication information.

[0138] In an embodiment, the receiving unit 601 is configured to receive uplink data or uplink signaling sent by the terminal, where the MAC SDU corresponding to the uplink data or uplink signaling is multiplexed with a second MAC CE in the same MAC PDU, and the second MAC CE carries a BSR, and the BSR indicates the existence of small packet data to be sent and / or the number of small packet data to be sent.

[0139] In one embodiment, the receiving unit 601 is configured to receive a first data packet sent by the terminal, and the first indication information is carried in the header of the first data packet.

[0140] In one embodiment, the header is a PDCP header or an RLC header.

[0141] In one embodiment, the receiving unit 601 is configured to receive a control PDU sent by the terminal, and the first indication information is carried in the control PDU.

[0142] In one embodiment, the control PDU is a PDCP control PDU or an RLC control PDU.

[0143] In one embodiment, the sending unit 602 is configured to send a static configuration instruction to the terminal, and the first configuration information is carried in the static configuration instruction.

[0144] In one embodiment, the static configuration instruction is an RRC message; the RRC message is MSG4 in the 4-step random access procedure; or, the second message is MSGB in the 2-step random access procedure.

[0145] In one embodiment, the sending unit 602 is configured to send a dynamic scheduling instruction to the terminal, and the first configuration information is carried in the dynamic scheduling instruction.

[0146] In one embodiment, the dynamic scheduling instruction is a DCI.

[0147] In one embodiment, the receiving unit 601 is configured to receive an RRC resume request message sent by the terminal;

[0148] The receiving unit 601 is configured to obtain a first terminal identifier from the RRC resume request message, address an anchor base station according to the first terminal identifier, and send a request message for the terminal context to the anchor base station;

[0149] Wherein, if the anchor base station determines to send the context of the terminal to the target base station, the target base station restores the context of the terminal; if the anchor base station determines not to send the context of the terminal to the target base station, the anchor base station restores the context of the terminal.

[0150] In one embodiment, the RRC resume request message is carried in MSG3 in the 4-step random access procedure; or, the RRC resume request message is carried in MSGA in the 2-step random access procedure.

[0151] Those skilled in the art should understand that the relevant descriptions of the above data transmission device in the embodiments of the present application can be understood with reference to the relevant descriptions of the data transmission method in the embodiments of the present application.

[0152] Figure 7 FIG. 2 is a schematic diagram of the structural composition of the data transmission device provided in the embodiments of the present application. As Figure 7 shown, the data transmission device includes:

[0153] A sending unit 701, configured to send first indication information to a target base station, where the first indication information is used to indicate the number of small packet data to be sent by the terminal and / or whether there is small packet data to be sent;

[0154] A receiving unit 702, configured to receive first configuration information sent by the target base station, where the first configuration information is used for the terminal to determine at least one uplink transmission resource corresponding to at least one small packet data to be sent.

[0155] In an embodiment, the sending unit 701 is configured to send a first preamble to the target base station on a first PRACH resource, and there is an association relationship between the first PRACH resource and / or the first preamble and the number of small packet data to be sent by the terminal.

[0156] In an embodiment, the receiving unit 702 is configured to receive second configuration information sent by the target base station, where the second configuration information is used for the terminal to determine the association relationship between the number of small packet data to be sent and the first PRACH resource and / or the first preamble;

[0157] The device further includes: a determining unit 703, configured to determine a first PRACH resource and / or a first preamble based on the second configuration information and the number of small packet data to be sent.

[0158] In an embodiment, the second configuration information is configured by a system broadcast message or dedicated signaling.

[0159] In an embodiment, the sending unit 701 is configured to send a first message to the target base station, and the first message carries the first indication information.

[0160] In an embodiment, the first message is MSG3 in a 4-step random access process; or, the first message is MSGA in a 2-step random access process.

[0161] In one embodiment, the sending unit 701 is configured to send uplink data or uplink signaling to the target base station, where the MAC SDU corresponding to the uplink data or uplink signaling is multiplexed with a first MAC CE in the same MAC PDU, and the first MAC CE carries the first indication information.

[0162] In one embodiment, the sending unit 701 is configured to send uplink data or uplink signaling to the target base station, where the MAC SDU corresponding to the uplink data or uplink signaling is multiplexed with a second MAC CE in the same MAC PDU, and the second MAC CE carries a BSR, and the BSR indicates the existence of small packet data to be sent and / or the number of small packet data to be sent.

[0163] In one embodiment, the sending unit 701 is configured to send a first data packet to the target base station, and the first indication information is carried in the header of the first data packet.

[0164] In one embodiment, the header is a PDCP header or an RLC header.

[0165] In one embodiment, the sending unit 701 is configured to send a control PDU to the target base station, and the control PDU carries the first indication information.

[0166] In one embodiment, the control PDU is a PDCP control PDU or an RLC control PDU.

[0167] In one embodiment, the receiving unit 702 is configured to receive a static configuration instruction sent by the target base station, and the static configuration instruction carries the first configuration information.

[0168] In one embodiment, the static configuration instruction is an RRC message; the RRC message is MSG4 in a four-step random access procedure; or, the second message is MSGB in a two-step random access procedure.

[0169] In one embodiment, the receiving unit 702 is configured to receive a dynamic scheduling instruction sent by the target base station, and the dynamic scheduling instruction carries the first configuration information.

[0170] In one embodiment, the dynamic scheduling instruction is a DCI.

[0171] Those skilled in the art should understand that the relevant descriptions of the above data transmission device in the embodiments of the present application can be understood with reference to the relevant descriptions of the data transmission method in the embodiments of the present application.

[0172] Figure 8FIG. 800 is a schematic structural diagram of a communication device provided by an embodiment of the present application. The communication device may be a terminal or a network device (such as a base station). Figure 8 As shown in FIG. 800, the communication device includes a processor 810. The processor 810 may call and run a computer program from a memory to implement the method in the embodiment of the present application.

[0173] Optionally, as Figure 8 shown, the communication device 800 may further include a memory 820. Among them, the processor 810 may call and run a computer program from the memory 820 to implement the method in the embodiment of the present application.

[0174] Among them, the memory 820 may be a separate device independent of the processor 810 or integrated in the processor 810.

[0175] Optionally, as Figure 8 shown, the communication device 800 may further include a transceiver 830. The processor 810 may control the transceiver 830 to communicate with other devices. Specifically, it may send information or data to other devices or receive information or data sent by other devices.

[0176] Among them, the transceiver 830 may include a transmitter and a receiver. The transceiver 830 may further include an antenna, and the number of antennas may be one or more.

[0177] Optionally, the communication device 800 may specifically be the network device in the embodiment of the present application, and the communication device 800 may implement the corresponding processes implemented by the network device in the various methods of the embodiment of the present application. For the sake of brevity, it will not be elaborated here.

[0178] Optionally, the communication device 800 may specifically be the mobile terminal / terminal in the embodiment of the present application, and the communication device 800 may implement the corresponding processes implemented by the mobile terminal / terminal in the various methods of the embodiment of the present application. For the sake of brevity, it will not be elaborated here.

[0179] Figure 9 FIG. 900 is a schematic structural diagram of a chip according to an embodiment of the present application. Figure 9 As shown in FIG. 900, the chip includes a processor 910. The processor 910 may call and run a computer program from a memory to implement the method in the embodiment of the present application.

[0180] Optionally, as Figure 9 shown, the chip 900 may further include a memory 920. Among them, the processor 910 may call and run a computer program from the memory 920 to implement the method in the embodiment of the present application.

[0181] Among them, the memory 920 can be a separate device independent of the processor 910, or can be integrated in the processor 910.

[0182] Optionally, the chip 900 may further include an input interface 930. Among them, the processor 910 can control the input interface 930 to communicate with other devices or chips. Specifically, it can obtain information or data sent by other devices or chips.

[0183] Optionally, the chip 900 may further include an output interface 940. Among them, the processor 910 can control the output interface 940 to communicate with other devices or chips. Specifically, it can output information or data to other devices or chips.

[0184] Optionally, the chip can be applied to the network device in the embodiments of the present application, and the chip can implement the corresponding processes implemented by the network device in the various methods of the embodiments of the present application. For the sake of brevity, it will not be elaborated here.

[0185] Optionally, the chip can be applied to the mobile terminal / terminal in the embodiments of the present application, and the chip can implement the corresponding processes implemented by the mobile terminal / terminal in the various methods of the embodiments of the present application. For the sake of brevity, it will not be elaborated here.

[0186] It should be understood that the chip mentioned in the embodiments of the present application can also be referred to as a system-on-chip, system chip, chip system, or system-on-chip, etc.

[0187] Figure 10 is a schematic block diagram of a communication system 1000 provided by an embodiment of the present application. As Figure 10 shown, the communication system 1000 includes a terminal 1010 and a network device 1020.

[0188] Among them, the terminal 1010 can be used to implement the corresponding functions implemented by the terminal in the above method, and the network device 1020 can be used to implement the corresponding functions implemented by the network device in the above method. For the sake of brevity, it will not be elaborated here.

[0189] It should be understood that the processor in the embodiments of the present application may be an integrated circuit chip with signal processing capabilities. In the implementation process, each step of the above method embodiments can be completed by the integrated logic circuit in the hardware of the processor or instructions in the form of software. The above-mentioned processor may be a general-purpose processor, a digital signal processor (DSP), an application specific integrated circuit (ASIC), a field programmable gate array (FPGA), or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components. It can implement or execute the various methods, steps, and logic block diagrams disclosed in the embodiments of the present application. The general-purpose processor may be a microprocessor or the processor may also be any conventional processor, etc. The steps of the method disclosed in combination with the embodiments of the present application can be directly embodied as being executed by a hardware decoding processor, or completed by a combination of hardware and software modules in the decoding processor. The software module may be located in a mature storage medium in the art such as a random access memory, a flash memory, a read-only memory, a programmable read-only memory, or an electrically erasable programmable memory, a register, etc. This storage medium is located in the memory, and the processor reads the information in the memory and combines its hardware to complete the steps of the above method.

[0190] It can be understood that the memory in the embodiments of the present application can be a volatile memory or a non-volatile memory, or can include both volatile and non-volatile memories. Among them, the non-volatile memory can be a read-only memory (ROM), a programmable read-only memory (PROM), an erasable programmable read-only memory (EPROM), an electrically erasable programmable read-only memory (EEPROM), or a flash memory. The volatile memory can be a random access memory (RAM), which is used as an external cache. By way of example but not limitation, many forms of RAM are available, such as static random access memory (SRAM), dynamic random access memory (DRAM), synchronous dynamic random access memory (SDRAM), double data rate synchronous dynamic random access memory (DDR SDRAM), enhanced synchronous dynamic random access memory (ESDRAM), synchlink dynamic random access memory (SLDRAM), and direct rambus random access memory (DR RAM). It should be noted that the memory of the systems and methods described herein is intended to include, but is not limited to, these and any other suitable types of memory.

[0191] It should be understood that the above-mentioned memory is by way of example but not limitation. For example, the memory in the embodiments of the present application can also be a static random access memory (SRAM), a dynamic random access memory (DRAM), a synchronous dynamic random access memory (SDRAM), a double data rate synchronous dynamic random access memory (DDR SDRAM), an enhanced synchronous dynamic random access memory (ESDRAM), a synchlink dynamic random access memory (SLDRAM), and a direct rambus random access memory (DR RAM), etc. That is to say, the memory in the embodiments of the present application is intended to include, but is not limited to, these and any other suitable types of memory.

[0192] The embodiments of the present application also provide a computer-readable storage medium for storing a computer program.

[0193] Optionally, the computer-readable storage medium can be applied to the network device in the embodiments of the present application, and the computer program enables the computer to execute the corresponding processes implemented by the network device in the various methods of the embodiments of the present application. For the sake of brevity, details are not described herein again.

[0194] Optionally, the computer-readable storage medium can be applied to the mobile terminal / terminal in the embodiments of the present application, and the computer program enables the computer to execute the corresponding processes implemented by the mobile terminal / terminal in the various methods of the embodiments of the present application. For the sake of brevity, details are not described herein again.

[0195] The embodiments of the present application also provide a computer program product including computer program instructions.

[0196] Optionally, the computer program product can be applied to the network device in the embodiments of the present application, and the computer program instructions enable the computer to execute the corresponding processes implemented by the network device in the various methods of the embodiments of the present application. For the sake of brevity, details are not described herein again.

[0197] Optionally, the computer program product can be applied to the mobile terminal / terminal in the embodiments of the present application, and the computer program instructions enable the computer to execute the corresponding processes implemented by the mobile terminal / terminal in the various methods of the embodiments of the present application. For the sake of brevity, details are not described herein again.

[0198] The embodiments of the present application also provide a computer program.

[0199] Optionally, the computer program can be applied to the network device in the embodiments of the present application. When the computer program runs on the computer, it enables the computer to execute the corresponding processes implemented by the network device in the various methods of the embodiments of the present application. For the sake of brevity, details are not described herein again.

[0200] Optionally, the computer program can be applied to the mobile terminal / terminal in the embodiments of the present application. When the computer program runs on the computer, it enables the computer to execute the corresponding processes implemented by the mobile terminal / terminal in the various methods of the embodiments of the present application. For the sake of brevity, details are not described herein again.

[0201] Those of ordinary skill in the art can realize that the units and algorithm steps of the examples described in combination with the embodiments disclosed herein can be implemented by electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are executed in a hardware or software manner depends on the specific application and design constraints of the technical solution. Professional technicians can use different methods for each specific application to implement the described functions, but such implementation should not be considered to exceed the scope of the present application.

[0202] Those skilled in the art can clearly understand that for the convenience and conciseness of description, the specific working processes of the systems, devices, and units described above can refer to the corresponding processes in the foregoing method embodiments and will not be elaborated herein.

[0203] In several embodiments provided in the present application, it should be understood that the disclosed systems, devices, and methods can be implemented in other ways. For example, the device embodiments described above are merely illustrative. For example, the division of the units is only a logical function division, and there can be other division methods in actual implementation. For example, multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. Another point is that the displayed or discussed couplings or direct couplings or communication connections to each other can be through some interfaces, and the indirect couplings or communication connections of the devices or units can be in electrical, mechanical, or other forms.

[0204] The units described as separate components may or may not be physically separated, and the components displayed as units may or may not be physical units, that is, they can be located in one place or distributed to multiple network units. Some or all of the units can be selected according to actual needs to achieve the purpose of the solution of this embodiment.

[0205] In addition, in each embodiment of the present application, the functional units can be integrated in a processing unit, or each unit can exist physically alone, or two or more units can be integrated in one unit.

[0206] If the function is implemented in the form of a software functional unit and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the present application, in essence, or the part that contributes to the prior art or a part of this technical solution can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes several instructions for causing a computer device (which can be a personal computer, a server, or a network device, etc.) to execute all or part of the steps of the methods described in each embodiment of the present application. The foregoing storage medium includes: USB flash drives, mobile hard disks, read-only memories (ROM), random access memories (RAM), magnetic disks, or optical discs, etc., which can store program codes.

[0207] As described above, it is only the specific implementation manner of the present application, but the protection scope of the present application is not limited thereto. Any person skilled in the art within the technical scope disclosed by the present application can easily think of changes or substitutions, which should all be covered within the protection scope of the present application. Therefore, the protection scope of the present application should be subject to the protection scope of the claims.

Claims

1. A data transmission method, the method comprises: The target base station receives first indication information sent by a terminal, where the first indication information is used to indicate whether there is small data to be sent by the terminal; The target base station sends multiple dynamic scheduling instructions to the terminal multiple times, where the dynamic scheduling instructions carry first configuration information, and the first configuration information is used for the terminal to determine uplink transmission resources corresponding to the small data to be sent; The dynamic scheduling instruction is downlink control information DCI; The target base station receives multiple small data continuously sent by the terminal based on the multiple dynamic scheduling instructions; and After receiving the multiple small data, the target base station sends an RRC connection release message to the terminal.

2. The method according to claim 1, wherein, The target base station receiving first indication information sent by a terminal includes: The target base station receives a first message sent by the terminal, where the first message carries the first indication information.

3. The method according to claim 2, wherein, The first message is MSG3 in a 4-step random access procedure; or, the first message is MSGA in a 2-step random access procedure.

4. The method according to claim 1, wherein, The target base station receiving first indication information sent by a terminal includes: The target base station receives uplink data or uplink signaling sent by the terminal, where the MAC SDU corresponding to the uplink data or uplink signaling is multiplexed with a first MAC CE in the same MAC PDU, and the first MAC CE carries the first indication information.

5. The method according to claim 1, wherein, The target base station receiving first indication information sent by a terminal includes: The target base station receives uplink data or uplink signaling sent by the terminal, where the MAC SDU corresponding to the uplink data or uplink signaling is multiplexed with a second MAC CE in the same MAC PDU, and the second MAC CE carries a buffer status report BSR, and the BSR indicates that there is small data to be sent.

6. The method according to claim 1, wherein, The target base station receiving first indication information sent by a terminal includes: The target base station receives a first data packet sent by the terminal, and the first indication information is carried in the header of the first data packet.

7. The method according to claim 6, wherein, The header is a PDCP header or an RLC header.

8. The method according to claim 1, wherein, The target base station receiving first indication information sent by a terminal includes: The target base station receives a control PDU sent by the terminal, and the control PDU carries the first indication information.

9. The method according to claim 8, wherein, The control PDU is a PDCP control PDU or an RLC control PDU.

10. The method according to claim 1, wherein, The method further includes: The target base station receives an RRC resume request message sent by the terminal; The target base station obtains a first terminal identifier from the RRC resume request message, addresses an anchor base station according to the first terminal identifier, and sends a request message for the terminal context to the anchor base station; Wherein, if the anchor base station determines to send the context of the terminal to the target base station, the target base station resumes the context of the terminal.

11. The method according to claim 10, Wherein, If the anchor base station determines not to send the context of the terminal to the target base station, the anchor base station resumes the context of the terminal.

12. The method according to claim 10, Wherein, The RRC resume request message is carried in MSG3 in a 4-step random access procedure; or, the RRC resume request message is carried in MSGA in a 2-step random access procedure.

13. A data transmission method, the method comprises: A terminal sends first indication information to a target base station, where the first indication information is used to indicate whether there is small data to be sent by the terminal; The terminal receives multiple dynamic scheduling instructions sent by the target base station multiple times, where the dynamic scheduling instructions carry first configuration information, and the first configuration information is used for the terminal to determine uplink transmission resources corresponding to the small data to be sent; The dynamic scheduling instruction is downlink control information DCI; The terminal continuously sends multiple pieces of small data to the target base station based on the multiple dynamic scheduling instructions; And After sending the multiple pieces of small data, the terminal receives an RRC connection release message sent by the target base station.

14. The method according to claim 13, Wherein, The terminal sending the first indication information to the target base station includes: The terminal sends a first message to the target base station, and the first message carries the first indication information.

15. The method according to claim 14, Wherein, The first message is MSG3 in a 4-step random access procedure; or, the first message is MSGA in a 2-step random access procedure.

16. The method according to claim 13, Wherein, The terminal sending the first indication information to the target base station includes: The terminal sends uplink data or uplink signaling to the target base station, where the MAC SDU corresponding to the uplink data or uplink signaling is multiplexed with a first MAC CE in the same MAC PDU, and the first MAC CE carries the first indication information.

17. The method according to claim 13, Wherein, The terminal sending the first indication information to the target base station includes: The terminal sends uplink data or uplink signaling to the target base station, where the MAC SDU corresponding to the uplink data or uplink signaling is multiplexed with a second MAC CE in the same MAC PDU, and the second MAC CE carries a BSR, and the BSR indicates that there is small data to be sent.

18. The method according to claim 13, Wherein, The terminal sending the first indication information to the target base station includes: The terminal sends a first data packet to the target base station, and the first indication information is carried in the header of the first data packet.

19. The method according to claim 18, wherein, the packet header is a PDCP packet header or an RLC packet header.

20. The method according to claim 13, wherein, the terminal sends first indication information to the target base station, including: the terminal sends a control PDU to the target base station, and the control PDU carries the first indication information.

21. The method according to claim 20, wherein, the control PDU is a PDCP control PDU or an RLC control PDU.

22. A data transmission device, the device comprises: a receiving unit, configured to receive first indication information sent by a terminal, where the first indication information is used to indicate whether there is small data to be sent by the terminal; a sending unit, configured to send multiple dynamic scheduling instructions to the terminal multiple times, where the dynamic scheduling instructions carry first configuration information, and the first configuration information is used for the terminal to determine uplink transmission resources corresponding to the small data to be sent; the dynamic scheduling instructions are downlink control information DCI; wherein, the receiving unit is further configured to receive multiple small data continuously sent by the terminal based on the multiple dynamic scheduling instructions; the sending unit is further configured to send an RRC connection release message to the terminal after receiving the multiple small data.

23. The device according to claim 22, wherein, the receiving unit is configured to receive a first message sent by the terminal, and the first message carries the first indication information.

24. The device according to claim 23, wherein, the first message is MSG3 in a 4-step random access procedure; or, the first message is MSGA in a 2-step random access procedure.

25. The device according to claim 22, wherein, the receiving unit is configured to receive uplink data or uplink signaling sent by the terminal, where the MAC SDU corresponding to the uplink data or uplink signaling is multiplexed with a first MAC CE in the same MAC PDU, and the first MAC CE carries the first indication information.

26. The device according to claim 22, wherein, the receiving unit is configured to receive uplink data or uplink signaling sent by the terminal, where the MAC SDU corresponding to the uplink data or uplink signaling is multiplexed with a second MAC CE in the same MAC PDU, and the second MAC CE carries a BSR, and the BSR indicates that there is small data to be sent.

27. The device according to claim 22, wherein, the receiving unit is configured to receive a first data packet sent by the terminal, and the first indication information is carried in the packet header of the first data packet.

28. The device according to claim 27, wherein, the packet header is a PDCP packet header or an RLC packet header.

29. The device according to claim 22, wherein, the receiving unit is configured to receive a control PDU sent by the terminal, and the control PDU carries the first indication information.

30. The device according to claim 29, wherein, the control PDU is a PDCP control PDU or an RLC control PDU.

31. The device according to claim 22, Among them, the receiving unit is configured to receive the RRC resume request message sent by the terminal; the receiving unit is configured to obtain a first terminal identifier from the RRC resume request message, address an anchor base station according to the first terminal identifier, and send a request message for the terminal context to the anchor base station; Among them, if the anchor base station determines to send the context of the terminal to the target base station, the target base station resumes the context of the terminal.

32. The apparatus according to claim 31, Among them, if the anchor base station determines not to send the context of the terminal to the target base station, the anchor base station resumes the context of the terminal.

33. The apparatus according to claim 31, Among them, the RRC resume request message is carried in MSG3 in the 4-step random access procedure; or, the RRC resume request message is carried in MSGA in the 2-step random access procedure.

34. A data transmission apparatus, the apparatus comprises: a sending unit, configured to send an RRC resume request message to a target base station, and then send first indication information to the target base station, where the first indication information is used to indicate whether there is small data to be sent by the terminal; a receiving unit, configured to receive multiple dynamic scheduling instructions sent by the target base station multiple times, where the dynamic scheduling instruction carries first configuration information, and the first configuration information is used for the terminal to determine uplink transmission resources corresponding to the small data to be sent; the dynamic scheduling instruction is downlink control information DCI; the sending unit is further configured to continuously send multiple small data to the target base station based on the multiple dynamic scheduling instructions; and the receiving unit is further configured to receive an RRC connection release message sent by the target base station after sending the multiple small data.

35. The apparatus according to claim 34, Among them, the sending unit is configured to send a first message to the target base station, where the first message carries the first indication information.

36. The apparatus according to claim 35, Among them, the first message is MSG3 in the 4-step random access procedure; or, the first message is MSGA in the 2-step random access procedure.

37. The apparatus according to claim 34, Among them, the sending unit is configured to send uplink data or uplink signaling to the target base station, where the MAC SDU corresponding to the uplink data or uplink signaling is multiplexed with a first MAC CE in the same MAC PDU, and the first MAC CE carries the first indication information.

38. The apparatus according to claim 34, Among them, the sending unit is configured to send uplink data or uplink signaling to the target base station, where the MAC SDU corresponding to the uplink data or uplink signaling is multiplexed with a second MAC CE in the same MAC PDU, and the second MAC CE carries a BSR, and the BSR indicates that there is small data to be sent.

39. The apparatus according to claim 34, Among them, the sending unit is configured to send a first data packet to the target base station, and the first indication information is carried in the header of the first data packet.

40. The apparatus according to claim 39, wherein, the packet header is a PDCP packet header or an RLC packet header.

41. The apparatus according to claim 34, wherein, the sending unit is configured to send a control PDU to the target base station, and the control PDU carries the first indication information.

42. The apparatus according to claim 41, wherein, the control PDU is a PDCP control PDU or an RLC control PDU.

43. A network device, comprising: a processor and a memory, the memory is used to store a computer program, and the processor is used to call and run the computer program stored in the memory to execute the method according to any one of claims 1 to 12.

44. A terminal, comprising: a processor and a memory, the memory is used to store a computer program, and the processor is used to call and run the computer program stored in the memory to execute the method according to any one of claims 13 to 21.

45. A chip, comprising: a processor, configured to call and run a computer program from a memory, so that a device installed with the chip executes the method according to any one of claims 1 to 12.

46. A chip, comprising: a processor, configured to call and run a computer program from a memory, so that a device installed with the chip executes the method according to any one of claims 13 to 21.

47. A computer-readable storage medium for storing a computer program, and the computer program causes a computer to execute the method according to any one of claims 1 to 12.

48. A computer-readable storage medium for storing a computer program, and the computer program causes a computer to execute the method according to any one of claims 13 to 21.

49. A computer program product comprising computer program instructions, and the computer program instructions cause a computer to execute the method according to any one of claims 1 to 12.

50. A computer program product comprising computer program instructions, and the computer program instructions cause a computer to execute the method according to any one of claims 13 to 21.

Images