Data transmission method, terminal equipment and access network equipment
By early data transmission before RRC connection is established in a cellular Internet of Things system, and the random access preamble or time frequency code resources are used to indicate the terminal equipment and access network equipment for data transmission, the problem of signaling overhead and power consumption is solved. , suitable for NB-IoT scenarios.
Patent Information
- Application Number
- CN202210868993.9
- Authority / Receiving Office
- CN · China
- Patent Type
- Patents(China)
- Current Assignee / Owner
- Priority Date
- 2017-05-05
- Filing Date
- 2017-07-18
- Publication Date
- 2024-11-15
- Estimated Expiration
- 2037-07-18
AI Technical Summary
In existing cellular IoT systems, uplink and downlink data transmission is required at least when the RRC connection is established, resulting in excessive signaling overhead and waste of power consumption, which is particularly unfavorable for service transmission in NB-IoT scenarios.
By transmitting data before the establishment of the wireless resource control RRC connection is completed, the terminal equipment and access network equipment are instructed to conduct uplink and downlink early data transmission using the random access preamble or time frequency code resources, saving signaling overhead and reducing device power consumption.
It realizes data transmission before RRC connection is established, saves signaling overhead and device power consumption, and is suitable for service transmission in NB-IoT scenarios.
Smart Images

Figure CN115442775B_ABST
Abstract
Description
Technical Field
[0001] The present application relates to the field of Internet of Things, and more specifically to a data transmission method, terminal equipment and access network equipment. Background Art
[0002] With the rapid development of wireless communications, people are no longer satisfied with human-to-human communications. The Internet of Things (IoT) technology has emerged, and its market demand is growing rapidly. The Internet of Things (IoT) is also known as Machine To Machine (M2M) or Machine Type Communications (MTC). MTC services have some special service characteristics, such as small amount of transmitted data, obvious service cycle characteristics, low power consumption and a large number of terminals.
[0003] A typical cellular IoT system is the narrowband IoT (NB-IoT). In the prior art, uplink and downlink data transmission can only be performed when at least the RRC connection is established, which leads to excessive signaling overhead and waste of power consumption, which is very unfavorable for service transmission in the NB-IoT scenario. Therefore, a new data transmission method is needed that can be applied to service transmission in the NB-IoT scenario. Summary of the invention
[0004] The present application provides a data transmission method, a terminal and an access network device, which can realize data transmission before the radio resource control (RRC) connection is established, thereby saving the signaling overhead of establishing the required bearer for data transmission and reducing the power consumption of the device.
[0005] In a first aspect, the present application relates to a data transmission method, which includes: a terminal device sends a first indication to an access network device, where the first indication is used to indicate that data needs to be transmitted before a wireless resource control (RRC) connection is established; and the terminal device transmits data between the terminal device and the access network device before the RRC connection is established.
[0006] Therefore, according to the method of the embodiment of the present application, data (including uplink data and downlink data) can be transmitted before the RRC establishment is completed according to the first indication, thereby saving the signaling overhead of establishing the required bearer for data transmission and reducing device power consumption.
[0007] In a possible implementation, when the first indication is a random access preamble code, the terminal device sends the first indication to the access network device, including: the terminal device sends the first random access preamble code to the access network device.
[0008] Thus, the access network device can determine that data is needed before the RRC connection is established based on the first random access preamble code. For example, it can determine that the terminal device needs to perform early uplink data transmission, or it can determine that the terminal device needs to perform early downlink data transmission.
[0009] In a possible implementation, the terminal device sends a first indication to the access network device, including: the terminal uses the first time-frequency code resource or the second time-frequency code resource to send a random access request message. The first time-frequency code resource can be used to indicate early transmission of uplink data, and the second time-frequency code resource can be used to indicate early transmission of downlink data.
[0010] In a possible implementation, the terminal device sends a first indication to the access network device, including: the terminal device sends a random access preamble code to the access network device on a first random access resource.
[0011] Thus, the access network device can determine that data is needed before the RRC connection is established based on the first random access resource. For example, it can determine that the terminal device needs to perform early transmission of uplink data, or it can determine that the terminal device needs to perform early transmission of downlink data.
[0012] In a possible implementation manner, the terminal device sends a first indication to the access network device, including: the terminal device sends a message 3 including the first indication to the access network device, wherein the message 3 is any one of the following messages:
[0013] RRC connection request message, RRC connection re-establishment request message and RRC connection recovery request.
[0014] In a possible implementation manner, the first indication is used to indicate that data needs to be transmitted before the radio resource control RRC connection establishment is completed, including:
[0015] The first indication is used to indicate that downlink data needs to be transmitted before the RRC connection establishment is completed.
[0016] In a possible implementation manner, the terminal device transmits data with the access network device before the RRC connection is established, including:
[0017] The terminal device transmits a non-access-stratum protocol data unit (NAS PDU) with the access network device before the RRC connection is established; or,
[0018] Before the RRC connection is established, the terminal device transmits data with the access network device via a data radio bearer (DRB).
[0019] In a possible implementation, the method also includes: the terminal device receives a release message sent by the access network device, the release message is a wireless resource control RRC connection establishment message, an RRC connection recovery message, an RRC connection re-establishment completion message, an RRC connection rejection message or an RRC connection release message, and the release message is used to release the terminal device to an idle state.
[0020] Optionally, the release message may carry data to be transmitted.
[0021] Further, if the release message is an RRC connection establishment message or an RRC connection re-establishment message or an RRC connection recovery, the message may include relevant information in the RRC connection release, which is used to release the connection of the terminal device, and may specifically include a release reason, a redirection indication, etc.;
[0022] If the release message is an RRC connection rejection message, it may also carry an indication information, such as a cause value, used to indicate that the terminal device is released to the idle state;
[0023] If the release message is an RRC connection release message and carries the identification information of the terminal device, a wireless media access control element (Media Access Control, MAC CE) carrying the identification can also be added to the RRC message, and the terminal device is directly released to the idle state.
[0024] Through RRC connection establishment message, RRC connection re-establishment message, RRC connection recovery or RRC connection rejection message, the terminal device can be released in advance when the MME has no downlink data transmission. Compared with the release process of the prior art, it can save signaling overhead and, on the other hand, can also reduce the power consumption of the terminal device.
[0025] In a second aspect, a data transmission method is provided, including: an access network device receives a first indication sent by a terminal device, the first indication being used to indicate that data needs to be transmitted before a radio resource control (RRC) connection is established; and the access network device transmits data between the terminal device and the access network device before the RRC connection is established.
[0026] Therefore, according to the method of the embodiment of the present application, data (including uplink data and downlink data) can be transmitted before the RRC establishment is completed according to the first indication, thereby saving the signaling overhead of establishing the required bearer for data transmission and reducing device power consumption.
[0027] In a possible implementation, when the first indication is a random access preamble code, the access network device receives the first indication sent by the terminal device, including: the access network device receives the first random access preamble code sent by the terminal device.
[0028] Thus, the access network device can determine that data is needed before the RRC connection is established based on the first random access preamble code. For example, it can determine that the terminal device needs to perform early uplink data transmission, or it can determine that the terminal device needs to perform early downlink data transmission.
[0029] In a possible implementation, the access network device receives a first indication sent by a terminal device, including: the access network device receives a random access preamble code sent by the terminal device in a first random access resource.
[0030] Thus, the access network device can determine that data is needed before the RRC connection is established based on the first random access resource. For example, it can determine that the terminal device needs to perform early transmission of uplink data, or it can determine that the terminal device needs to perform early transmission of downlink data.
[0031] In a possible implementation manner, the access network device receives a first indication sent by a terminal device, including: the access network device receives a message 3 including the first indication sent by the terminal device, wherein the message 3 is any one of the following messages:
[0032] RRC connection request message, RRC connection re-establishment request message and RRC connection recovery request.
[0033] In a possible implementation manner, the first indication is used to indicate that data needs to be transmitted before a radio resource control RRC connection is established, including: the first indication is used to indicate that downlink data needs to be transmitted before the RRC connection is established.
[0034] In a possible implementation, the access network device transmits data with the terminal device before the RRC connection is established, including: the access network device transmits a non-access layer protocol data unit NAS PDU with the terminal device before the RRC connection is established; or
[0035] Before the RRC connection is established, the access network device transmits data with the terminal device via the data radio bearer DRB.
[0036] In a possible implementation manner, the method further includes: the access network device sending the NAS PDU to the core network device.
[0037] In a possible implementation, the method also includes: the access network device sends a release message to the terminal device, the release message is a wireless resource control RRC connection establishment message, an RRC connection recovery message, an RRC connection re-establishment completion message, an RRC connection rejection message or an RRC connection release message, and the release message is used to release the terminal device to an idle state.
[0038] Optionally, the release message may carry data to be transmitted.
[0039] Further, if the release message is an RRC connection establishment message or an RRC connection re-establishment message or an RRC connection recovery, the message may include relevant information in the RRC connection release, which is used to release the connection of the terminal device, and may specifically include a release reason, a redirection indication, etc.;
[0040] If the release message is an RRC connection rejection message, it may also carry an indication information, such as a cause value, used to indicate that the terminal device is released to the idle state;
[0041] If the release message is an RRC connection release message and carries user equipment identification information, a MAC CE carrying the identification information may also be added to the RRC message, and the terminal device is directly released to the idle state.
[0042] Through RRC connection establishment message, RRC connection re-establishment message, RRC connection recovery or RRC connection rejection message, the terminal device can be released in advance when the MME has no downlink data transmission. Compared with the release process of the prior art, it can save signaling overhead and, on the other hand, can also reduce the power consumption of the terminal device.
[0043] In a third aspect, a terminal device is provided, which is used to execute the method in the first aspect or any possible implementation of the first aspect. Specifically, the terminal device includes a unit for executing the method in the first aspect or any possible implementation of the first aspect.
[0044] In a fourth aspect, an access network device is provided, which is used to execute the method in the second aspect or any possible implementation of the second aspect. Specifically, the access network device includes a unit for executing the method in the second aspect or any possible implementation of the second aspect.
[0045] In a fifth aspect, a terminal device is provided, which includes a receiver, a transmitter, a processor, a memory, and a bus system. The receiver, the transmitter, the processor, and the memory are connected via a bus system, the memory is used to store instructions, and the processor is used to execute the instructions stored in the memory to control the receiver to receive signals and control the transmitter to send signals. When the processor executes the instructions stored in the memory, the execution causes the processor to execute the method in the first aspect or any possible implementation of the first aspect.
[0046] In a sixth aspect, an access network device is provided, the access network device comprising a receiver, a transmitter, a processor, a memory and a bus system. The receiver, the transmitter, the processor and the memory are connected via a bus system, the memory is used to store instructions, and the processor is used to execute the instructions stored in the memory to control the receiver to receive signals and control the transmitter to send signals. When the processor executes the instructions stored in the memory, the execution causes the processor to execute the method in the second aspect or any possible implementation of the second aspect.
[0047] In a seventh aspect, the present application provides a computer-readable medium for storing a computer program, wherein the computer program includes instructions for executing the method in the first aspect or any possible implementation of the first aspect.
[0048] According to an eighth aspect, a computer-readable medium is provided for storing a computer program, wherein the computer program comprises instructions for executing the method in the second aspect or any possible implementation of the second aspect.
[0049] In a ninth aspect, a data transmission method is provided, characterized in that it includes: a terminal device sends a first indication to an access network device, the first indication is used to instruct the terminal device to transmit data based on a first radio resource control RRC signaling sent by the terminal device to the access network device, and / or,
[0050] The first indication is used to instruct the access network device to transmit data based on the first radio resource control RRC signaling sent by the access network device to the terminal device;
[0051] Based on the first RRC signaling, data is transmitted between the terminal device and the access network device.
[0052] Specifically, the first indication is used to indicate that the first signaling transmitted between the terminal device and the access network device carries data, or transmits data while transmitting the first signaling, or transmits data immediately after transmitting the first signaling. The first signaling is the first RRC signaling between the terminal device and the access network device during the random access process. In other words, the first indication is used to indicate that the terminal device will transmit uplink data based on the first RRC signaling between the terminal device and the access network device, and / or the first indication is used to indicate that the access network device will transmit downlink data based on the first RRC signaling between the terminal device and the access network device.
[0053] Therefore, according to the method of the embodiment of the present application, uplink and / or downlink data transmission can be achieved based on the first RRC signaling between the terminal device and the access network device without establishing an RRC connection, thereby saving the signaling overhead of establishing the required bearer for data transmission and reducing device power consumption.
[0054] In a possible implementation manner, based on the first RRC signaling, data is transmitted between the terminal device and the access network device, including:
[0055] The first RRC signaling carries data and transmits data between the terminal device and the access network device.
[0056] In a possible implementation, data transmission between a terminal device and an access network device includes:
[0057] Data is transmitted between the terminal device and the access network device via the non-access layer protocol data unit NAS PDU; or,
[0058] Data is transmitted between the terminal device and the access network device via the data radio bearer DRB.
[0059] Optionally, the data may be sent via DRB or SRB0.
[0060] In the present application, the data and the first RRC signaling may be multiplexed into one transmission block, or may be transmitted separately as two transmission blocks.
[0061] It should be noted that, when the data and the first RRC signaling are transmitted together, the first RRC signaling may carry the terminal device identifier. When the data and the first RRC signaling are transmitted separately, the data may carry the terminal device identifier or be scrambled by the terminal device identifier.
[0062] The identifier of the terminal device may be, for example, a radio network temporary identifier (RNTI), a hash serving temporary mobile subscriber identifier (hash S-TMSI), S-TMSI, a truncated S-TMSI, an access random number, an international mobile subscriber identification number (IMSI), an identifier of the terminal device carried in a MAC CE, etc. This application does not specifically limit the identifier of the terminal device.
[0063] Further, if the data can be transmitted separately with the first RRC signaling as two transport blocks, the NAS PDU carrying the data can be sent via SRB 1bis or SRB0, or the first RRC signaling is sent via SRB 0 and the data is sent via DRB.
[0064] In a possible implementation manner, the first RRC signaling is message 3 or message 4.
[0065] In a possible implementation, message 3 is any of the following messages:
[0066] RRC connection request message, RRC connection re-establishment request message and RRC connection recovery request message; and / or
[0067] Message 4 is any of the following messages:
[0068] Conflict resolution message, RRC connection establishment message, RRC connection re-establishment message and RRC connection recovery message.
[0069] In a possible implementation manner, when the first indication is a random access preamble code, the terminal device sends the first indication to the access network device, including:
[0070] The terminal device sends a first random access preamble code to the access network device.
[0071] In a possible implementation manner, the terminal device sends a first indication to the access network device, including:
[0072] The terminal device sends a random access preamble code to the access network device on the first random access resource.
[0073] In a possible implementation manner, before transmitting the data between the terminal device and the access network device based on the first RRC signaling, the method further includes:
[0074] The terminal device receives a system message, where the system message includes data amount information, where the data amount information is used to indicate a maximum amount of data that can be transmitted by the terminal device based on the first RRC signaling;
[0075] The transmitting of the data between the terminal device and the access network device based on the first RRC signaling includes:
[0076] When the terminal device determines that the data amount of the data is less than or equal to the maximum data amount, based on the first RRC signaling, the terminal device transmits the data to the access network device.
[0077] In a possible implementation, the method may further include:
[0078] The terminal device receives a candidate message sent by the access network device, the candidate message includes indication information, the candidate message is an RRC connection establishment message, an RRC connection recovery message, an RRC connection re-establishment completion message, an RRC connection rejection message or an RRC connection release message, and the indication information is used to instruct the terminal device to remain in an idle state.
[0079] Optionally, the candidate message may be message 4.
[0080] In this way, through the indication information in message 4, the terminal device can be released in advance when there is no downlink data transmission. Compared with the release process of the prior art, it can save signaling overhead and, on the other hand, reduce the power consumption of the terminal device.
[0081] In a tenth aspect, a data transmission method is provided, comprising:
[0082] The access network device receives a first indication sent by the terminal device, where the first indication is used to instruct the terminal device to transmit data based on a first radio resource control RRC signaling sent by the terminal device to the access network device, and / or,
[0083] The first indication is used to instruct the access network device to transmit data based on the first radio resource control RRC signaling sent by the access network device to the terminal device;
[0084] Based on the first RRC signaling, data is transmitted between the access network device and the terminal device.
[0085] Therefore, according to the method of the embodiment of the present application, uplink and / or downlink data transmission can be achieved based on the first RRC signaling between the terminal device and the access network device without establishing an RRC connection, thereby saving the signaling overhead of establishing the required bearer for data transmission and reducing device power consumption.
[0086] In a possible implementation manner, based on the first RRC signaling, data is transmitted between the access network device and the terminal device, including:
[0087] The first RRC signaling carries data and transmits data between the access network device and the terminal device.
[0088] In a possible implementation manner, transmitting data between an access network device and a terminal device includes:
[0089] Data is transmitted between the access network device and the terminal device via the non-access layer protocol data unit NAS PDU; or,
[0090] Data is transmitted between access network equipment and terminal equipment via data radio bearer DRB.
[0091] In a possible implementation manner, the first RRC signaling is message 3 or message 4.
[0092] In a possible implementation, message 3 is any of the following messages:
[0093] RRC connection request message, RRC connection re-establishment request message and RRC connection recovery request message; and / or
[0094] Message 4 is any of the following messages:
[0095] Conflict resolution message, RRC connection establishment message, RRC connection re-establishment message and RRC connection recovery message.
[0096] In a possible implementation manner, when the first indication is a random access preamble code, the access network device receives the first indication sent by the terminal device, including:
[0097] The access network device receives the first random access preamble code sent by the terminal device.
[0098] In a possible implementation manner, the access network device receives the first indication sent by the terminal device, including:
[0099] The access network device receives the random access preamble code sent by the terminal device in the first random access resource.
[0100] In a possible implementation, the method may further include:
[0101] The access network device sends NAS PDU to the core network device.
[0102] Optionally, the NAS PDU may be carried by a Retrieve UE Information Message or an Initial UE Message.
[0103] In a possible implementation, before the data is transmitted between the access network device and the terminal device based on the first RRC signaling, the method further includes: the access network device receiving the NAS PDU sent by the core network device;
[0104] The data transmission between the access network device and the terminal device based on the first RRC signaling includes: based on the first RRC signaling, the access network device transmits the NAS PDU to the terminal device.
[0105] Optionally, the first RRC signaling is a UE Information Transfer Message or a downlink NAS Transport Message.
[0106] Furthermore, the NAS PDU includes indication information, and the indication information is used to instruct the access network device to instruct the terminal device to remain in an idle state.
[0107] In a possible implementation, the method may further include:
[0108] The access network device sends a candidate message to the terminal device, the candidate message includes indication information, the candidate message is an RRC connection establishment message, an RRC connection recovery message, an RRC connection re-establishment completion message, an RRC connection rejection message or an RRC connection release message, and the indication information is used to instruct the terminal device to remain in an idle state.
[0109] In an eleventh aspect, a terminal device is provided, which is used to execute the method in the ninth aspect or any possible implementation of the ninth aspect. Specifically, the terminal device includes a unit for executing the method in the ninth aspect or any possible implementation of the ninth aspect.
[0110] In a twelfth aspect, an access network device is provided, which is used to execute the method in the tenth aspect or any possible implementation of the tenth aspect. Specifically, the access network device includes a unit for executing the method in the tenth aspect or any possible implementation of the tenth aspect.
[0111] In the thirteenth aspect, a terminal device is provided, which includes a memory, a processor and a transceiver, wherein the memory is used to store program code, and the processor is used to execute the program code stored in the memory to perform operations corresponding to the method in the ninth aspect or various possible implementations of the ninth aspect.
[0112] In the fourteenth aspect, an access network device is provided, which includes a memory, a processor and a transceiver, the memory is used to store program code, and the processor is used to execute the program code stored in the memory to perform the operations corresponding to the method in the tenth aspect or various possible implementations of the tenth aspect.
[0113] In a fifteenth aspect, the present application provides a computer-readable medium for storing a computer program, wherein the computer program includes instructions for executing the method in the ninth aspect or any possible implementation of the ninth aspect.
[0114] In a sixteenth aspect, a computer-readable medium is provided for storing a computer program, wherein the computer program includes instructions for executing the method in the tenth aspect or any possible implementation of the tenth aspect. BRIEF DESCRIPTION OF THE DRAWINGS
[0115] Figure 1 is a schematic diagram of a communication system that can be applied to the present application.
[0116] Figure 2 It is a schematic flowchart of a data transmission method according to an embodiment of the present application.
[0117] Figure 3 It is a schematic flow chart of the method for early transmission of uplink data according to the present application.
[0118] Figure 4 It is a schematic flow chart of a method for early transmission of uplink data based on the CP solution according to the present application.
[0119] Figure 5 It is a schematic flowchart of the method for early transmission of uplink data based on the UP solution according to the present application.
[0120] Figure 6 It is a schematic flow chart of a method for early transmission of downlink data based on a CP solution according to the present application.
[0121] Figure 7 It is a schematic flow chart of a method for early transmission of downlink data based on the UP solution according to the present application.
[0122] Figure 8 is a schematic block diagram of a terminal device according to the present application.
[0123] Fig. 9 It is a schematic block diagram of an access network device according to the present application.
[0124] Fig.10 is a schematic flowchart of a data transmission method according to another embodiment of the present application.
[0125] Fig.11This is a schematic diagram of a format of message 2.
[0126] Fig.12 This is a diagram of another format of message 2.
[0127] Fig.13 This is a schematic diagram of a format of message 2.
[0128] Fig.14 This is a schematic diagram of another format of message 2.
[0129] Fig.15 It is a schematic flow chart of another method for early transmission of uplink data based on the CP solution according to the present application.
[0130] Fig.16 It is a schematic flowchart of another method for early transmission of uplink data based on the UP solution according to the present application.
[0131] Fig.17 It is a schematic flow chart of another method for early transmission of downlink data based on the CP solution according to the present application.
[0132] Fig.18 It is a schematic flowchart of another method for early transmission of downlink data based on the UP solution according to the present application.
[0133] Fig.19 is a schematic block diagram of another terminal device according to the present application.
[0134] Fig. 20 is a schematic block diagram of another access network device according to the present application. DETAILED DESCRIPTION
[0135] The technical solution in this application will be described below in conjunction with the accompanying drawings.
[0136] It should be understood that the technical solution 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, Advanced long term evolution (LTE-A) system, Universal Mobile Telecommunication System (UMTS), New Radio Access Technology (NR), 5G, etc.
[0137] It should also be understood that in the embodiments of the present application, the terminal device may also be referred to as a terminal or user equipment (User Equipment, UE), which may include but is not limited to terminal devices used in the Internet of Things, for example, it may be a terminal device used in NB-IoT (which may be referred to as "NB-IoT terminal"): smart meter reading equipment, logistics tracking equipment, environmental monitoring equipment, etc.; the terminal may also include but is not limited to a mobile station (Mobile Station, MS), a mobile terminal (Mobile Terminal), a mobile phone (Mobile Telephone), a user equipment (User Equipment, UE), a mobile phone (handset) and a portable device (portable equipment), etc. The terminal device can communicate with one or more core networks via a radio access network (Radio Access Network, RAN). For example, the terminal device may be a mobile phone (or a "cellular" phone), a computer with wireless communication capabilities, etc. The terminal device may also be a portable, pocket-sized, handheld, computer-built-in or vehicle-mounted mobile device.
[0138] In the embodiment of the present application, the access network device may also be referred to as a radio access network (RAN) device, for example, a base station, a base station controller, a radio network controller (RNC), a transmit and receive point (TRP). The base station may be a base station (Base Transceiver Station, BTS) in GSM or CDMA, or a base station (NodeB) in WCDMA, or an evolved base station (evolved Node B, eNB or e-NodeB) in LTE, or a base station (gNB) of NR or 5G. The embodiment of the present application does not specifically limit this.
[0139] The embodiment of the present invention also relates to a core network (CN) device, which mainly includes a mobility management entity (MME) and a serving gateway (S-GW). MME may have different names in different systems or networks of different standards. For ease of understanding, it is uniformly described as MME in this application. Correspondingly, S-GW may have different names in different systems or networks of different standards. For ease of understanding, it is uniformly described as S-GW in this application.
[0140] Figure 1 is a schematic diagram of a communication system that can be applied to the present application. Figure 1 In the core network, the terminal device can communicate with the core network device through one or more access network devices. For example, Figure 1 The terminal device 10a can communicate with the core network device 12 via the access network device 110a; the terminal device 10b can communicate with the core network device 12 via the access network device 110a or via the access network device 110b; the terminal device 10c can communicate with the core network device 12 via the access network device 110b. Furthermore, it can communicate with the Public Switched Telephone Network (PSTN) 13 or other networks 14 or even the entire Internet 15.
[0141] In the prior art, uplink and downlink data transmission can only be performed when at least the RRC connection is established, which results in late data transmission, excessive signaling overhead and waste of power consumption. To solve this problem, the present application proposes a data transmission method that can achieve early data transmission, thereby saving power consumption and signaling overhead.
[0142] Before introducing the data transmission method of the present application, the relevant terms or concepts involved in the present application are first introduced.
[0143] Early data transmission can be understood as uplink and / or downlink data transmission before the RRC connection establishment / recovery / re-establishment completion message.
[0144] Early data transmission may also be understood as uplink and / or downlink data transmission performed during the random access process.
[0145] Early data transmission can also be understood as uplink and / or downlink data transmission performed by the terminal device through the first RRC signaling between the terminal device and the access network device.
[0146] Early data transmission can be regarded as a capability. If the terminal device supports this data transmission method, then the terminal device supports this capability. If the access network device supports the terminal device to use this method, it indicates that the access network device supports this capability of early data transmission.
[0147] When sending a system message, the access network device can indicate whether it supports the capability of early data transmission. Before random access, the terminal device can determine whether the access network device supports this capability based on the received system message. If not, the terminal device that supports this capability and wants to use this capability for transmission can choose not to access the access network device.
[0148] For example, the system message may also indicate the upper limit or threshold of the amount of uplink data sent by the terminal device in the first RRC signaling message, or the upper limit or threshold of the amount of uplink data in the first uplink RRC message and uplink data, or the upper limit or threshold of the amount of uplink data allowed to be transmitted in addition to the first RRC signaling RRC message, such as 20 bytes. If the terminal device finds that the amount of uplink data to be sent exceeds the upper limit or threshold of the amount of data broadcast by the system, the terminal device can choose to access using normal data transmission. If the amount of uplink data that the terminal device needs to send is less than this upper limit or threshold, it can choose to send the data using uplink data early transmission.
[0149] The system message may be SIB2, SIB22 or other system messages.
[0150] For example, a default threshold may be specified in the protocol, which may indicate the upper limit of the amount of uplink data sent by the terminal device in the first RRC signaling message, or the upper limit of the amount of uplink data in the first uplink RRC message and uplink data, or the upper limit of the amount of uplink data allowed to be transmitted in addition to the first RRC signaling RRC message. If the terminal device finds that the amount of the first RRC signaling and uplink data exceeds the threshold, the terminal device may choose to access in a normal manner. If the amount of uplink data that the terminal device needs to send is less than the threshold, the uplink data early transmission method may be selected to send the data.
[0151] For example, if the terminal device supports the capability of early data transmission, the terminal device can choose whether to use early data transmission to send data according to the amount of data to be sent or the type of service. If the terminal device chooses the early data transmission method, when the resources allocated by the access network device for data transmission are sufficient, the terminal device transmits the data in the uplink early transmission method. If the data resources allocated by the access network device are not sufficient to send all the uplink data that the terminal device needs to send, the terminal device can choose the normal data transmission process, that is, first establish an RRC connection, and then send data, such as in message 5 (for example, RRC connection completion message, RRC connection re-establishment completion message, etc.) Data can be transmitted. Or the terminal device first sends a part of the data on the resources allocated by the access network device to message 3, and the remaining data can be sent after the RRC connection is established later.
[0152] It should be understood that the signaling or messages described in the embodiments of the present application that are the same or similar to the existing protocols or prior arts can all refer to the prior arts. For the sake of brevity, the contents contained in these signaling or messages will not be introduced in detail based on their specific functions, etc.
[0153] The term "and / or" in this application is only a description of the association relationship of associated objects, indicating that there can be three relationships. For example, A and / or B can represent: A exists alone, A and B exist at the same time, and B exists alone. In addition, the character " / " in this article generally indicates that the associated objects before and after are in an "or" relationship.
[0154] In addition, it can be understood that the terms "first" and "second" in the present application are only for the convenience of description and understanding, and should not constitute any limitation to the embodiments of the present application.
[0155] Next, combine Figure 2 The data transmission method of the present application is described in detail. It should be understood that Figure 2 The detailed communication steps or operations of the method are shown, but these steps or operations are only examples. The embodiment of the present application may also perform other operations or Figure 2 In addition, Figure 2 The steps in Figure 2 are executed in a different order than those presented, and may not be executed in the order Figure 2 All operations in .
[0156] Figure 2 It is a schematic flowchart of a data transmission method according to an embodiment of the present application.
[0157] S210, the terminal device sends a first indication to the access network device. Correspondingly, the access network device receives the first indication.
[0158] Specifically, the first indication is used to indicate that data needs to be transmitted before the radio resource control RRC connection is established. Thus, the access network device can determine that data is needed before the RRC connection is established according to the first indication, for example, it can determine that the terminal device needs to perform early uplink data transmission, or it can determine that the terminal device performs early downlink data transmission.
[0159] It should be understood that early transmission of uplink data means that uplink data needs to be transmitted before the radio resource control RRC connection is established. Early transmission of downlink data means that downlink data needs to be transmitted before the radio resource control RRC connection is established.
[0160] In one possible implementation, message 1 is used to distinguish between uplink data early transmission and downlink data early transmission, so that the access network device can be notified in time to avoid the access network device being unclear whether the terminal device wants to perform uplink data early transmission or downlink data early transmission. When uplink data early transmission is required, a larger uplink resource allocation (UL Grant) or multiple UL Grants is allocated when a random access response is sent to the terminal device, while in the case of downlink early transmission, a larger UL Grant or multiple UL Grants does not need to be allocated.
[0161] Optionally, the terminal device may send a first indication to the access network device via message 3 (Msg3), that is, Msg3 may include the first indication. The indication information is used to indicate that downlink early transmission is required, that is, receiving downlink data before the RRC connection is established. This type of indication is used when message 1 is not used to distinguish between uplink and downlink, and the terminal device may indicate in message 3 that it wants to perform downlink data early transmission.
[0162] Furthermore, Msg3 may be any of the following messages: an RRC connection request message, an RRC connection re-establishment request message, and an RRC connection recovery request message.
[0163] Furthermore, the RRC connection request message or the RRC connection re-establishment request message carries a non-access stratum protocol data unit NAS PDU which may include data to be transmitted, that is, uplink data may be sent via the NAS PDU in the RRC connection request message or the RRC connection re-establishment request message.
[0164] Optionally, the first indication may be a dedicated preamble (for example, recorded as a first random access preamble). In this case, as an embodiment of S210: the terminal device sends a first random access preamble to the access network device. The first random access preamble is used to indicate early transmission of uplink data or early transmission of downlink data.
[0165] Optionally, as another embodiment of S210, the terminal device may send a random access preamble code to the access network device on a specific resource (for example, recorded as a first random access resource), thereby indicating early transmission of uplink data or early transmission of downlink data.
[0166] Optionally, the terminal device may indicate early data transmission through a time-frequency code. For example, if the terminal device uses a specific time-frequency code resource (e.g., a first time-frequency code resource) to send a random access request message, it indicates that the terminal device wants to perform early uplink data transmission, and if the terminal device uses another time-frequency code resource (e.g., a second time-frequency code resource), it indicates that the terminal device wants to perform early downlink data reception. The time-frequency code may be any combination of the time domain, the frequency domain, and the code domain, such as different time-frequency resources, different code domain resources, different time-frequency code resources, and the like.
[0167] Optionally, when the terminal device is in a connected state, the access network device may also send an indication to the terminal device through a physical downlink control channel (PDCCH) command to indicate that the UE needs to perform random access for early data transmission, such as early uplink data transmission or early downlink data transmission. That is, random access is performed through the PDCCH order method. The specific indication information can be carried by DCI.
[0168] S220, the terminal device transmits data with the access network device before the RRC connection is established.
[0169] Optionally, the terminal device may transmit data by transmitting a non-access layer protocol data unit NAS PDU between the terminal device and the access network device before the RRC connection is established.
[0170] Optionally, the terminal device may also transmit data with the access network device via a data radio bearer DRB before the RRC connection is established.
[0171] Therefore, according to the method of the embodiment of the present application, data (including uplink data and downlink data) can be transmitted before the RRC establishment is completed, thereby saving the signaling overhead of establishing the required bearer for data transmission and reducing device power consumption.
[0172] The following describes the data transmission method according to the embodiment of the present application for early transmission of uplink data and early transmission of downlink data respectively.
[0173] Figure 3 It is a schematic flowchart of a data transmission method according to an embodiment of the present application. Figure 3 The method shown is applicable to early transmission of uplink data.
[0174] S310, the terminal device sends a random access preamble to the access network device. In other words, the terminal device sends a random access request message, namely, message 1 (Msg1), to the access network device.
[0175] Optionally, the terminal device may send Msg1 on a specific resource (for example, recorded as random access resource #A). Random access resource #A may be used to indicate early transmission of uplink data or early transmission of downlink data.
[0176] Optionally, the terminal device may also send a dedicated preamble (for example, recorded as a random access preamble #A). The random access preamble #A may also be used to indicate early transmission of uplink data or early transmission of downlink data.
[0177] It should be understood that the random access resource #A is an example of the first random access resource, and may also be other examples such as a combination of time-frequency codes, and the random access preamble #A is an example of the first random access preamble.
[0178] S320, after receiving Msg1, the access network device sends a random access response message to the terminal device, that is, the access network device sends message 2 (Msg2).
[0179] Msg2 carries uplink timing (TA) and uplink resource allocation (UL Grant). Among them, UL Grant is the resource allocated by the access network device to the terminal device for the terminal device to transmit message 3 (Msg3). For details about TA and UL Grant, please refer to the existing technology and will not be introduced in detail here.
[0180] Optionally, in an embodiment of the present application, the access network device can learn that the UE wants to perform early data transmission based on time-frequency code resource information such as the first random access preamble or the first random access resource. If it is early transmission of uplink data, resources for transmitting uplink data are allocated to the terminal device. The resources for transmitting uplink data allocated by the access network device to the terminal device are together with the UL Grant and are called target resources. The target resource allocated by the access network device can be a large uplink resource for transmitting message 3 and uplink data, or it can be two independent resources, one for transmitting message 3 and the other for transmitting uplink data.
[0181] Furthermore, the size of the target resource may be fixed, such as 100 bytes. The size of the target resource may also be determined by the access network device according to the first random access resource or the first random access preamble, that is, the first random access resource or the first random access preamble may also be used to indicate the size of the uplink data, so that the access network device can reasonably allocate resources for transmitting the uplink data according to the size of the uplink data. That is to say, on the basis of indicating the uplink early transmission, the size of the resources to be allocated may be further distinguished according to the access resource.
[0182] S330, the terminal device sends Msg3 and uplink data to the access network device according to Msg2.
[0183] It should be understood that Msg3 can be transmitted together with uplink data or separately. When Msg3 and uplink data are transmitted together, Msg3 can carry the identifier of the terminal device. When Msg3 and uplink data are transmitted separately, the uplink data can carry the identifier of the terminal device or be scrambled by the identifier of the terminal device.
[0184] The identifier of the terminal device may be, for example, a Radio Network Temporary Identifier (RNTI) - a temporary identifier of a cell wireless network, a hashed serving temporary mobile subscriber identifier (hash Serving Temporary Mobile Subscriber Identity, hashed S-TMSI), S-TMSI, a truncated S-TMSI, an access random number, an International Mobile Subscriber Identification Number (IMSI), an identifier of the terminal device carried in a MAC CE, etc. This application does not specifically limit the identifier of the terminal device.
[0185] Optionally, after receiving Msg2, if the terminal device has uplink data to be transmitted, it can transmit the uplink data on the pre-configured or reserved resources for early transmission of uplink data while transmitting Msg3.
[0186] Optionally, the terminal device may also transmit Msg3 and uplink data simultaneously on the target resources indicated by Msg2.
[0187] As an embodiment of Msg3, Msg3 may be an RRC connection request message or an RRC connection re-establishment request message, wherein the RRC connection request message or the RRC connection re-establishment request message includes a non-access stratum protocol data unit NAS PDU carrying the uplink data. Thus, early transmission of uplink data can be achieved through a control plane CIoT EPS optimization scheme (CP).
[0188] Furthermore, when Msg3 and uplink data are transmitted separately, the NAS PDU can be sent via a 1-bit signaling radio bearer (SRB). The message carrying the NAS PDU is an uplink direct transfer message (UL information transfer), so that the access network device can know that this is a terminal device using CP based on the corresponding logical channel identifier (Identity, ID).
[0189] It should be understood that the RRC connection request message and the RRC connection re-establishment request message are both a type of Msg3, the RRC connection request message is used to establish an RRC connection, and the RRC connection re-establishment request message is used to re-establish an RRC connection. For the RRC connection request message and the RRC connection re-establishment request message, specific reference can be made to the prior art, and this application will not provide a specific introduction.
[0190] As another embodiment of Msg3, Msg3 may be an RRC connection request message, an RRC connection recovery request message or an RRC connection re-establishment request message, and the uplink data is sent via a data radio bearer DRB. Thus, early transmission of uplink data can be achieved through a user plane CIoT EPS optimisation (UP). Similarly, the data may be sent to the access network device together with message 3, or may be sent separately.
[0191] It should be understood that the RRC connection recovery request message or RRC connection re-establishment request message here is used to restore the RRC connection after the access network device releases the RRC connection. For details, reference may be made to the prior art and this application will not provide a detailed introduction.
[0192] S340: The access network device sends the uplink data to the MME or S-GW.
[0193] In summary, in a data transmission method of the present application, if the access network devices all support the capability of early data transmission, resources can be reserved so that when there is a need for early uplink data transmission, the terminal device can send uplink data simultaneously with Msg3 through reserved resources. In this case, the terminal device can indicate to the access network device through Msg1 that the terminal device needs to perform early uplink data transmission, or it may not indicate to the access network device the need for early data transmission of the terminal device.
[0194] In another data transmission method of the present application, if the access network devices all support the capability of early data transmission, the access network devices can allocate resources for transmitting uplink data, such as target resources, to the terminal device when the terminal device needs to perform early uplink data transmission, for example, when the access network devices know through random access resources #A or random access preamble code #A that the terminal device needs to perform early uplink data transmission. This allows the terminal device to send uplink data simultaneously through the resources allocated by the access network device while transmitting Msg3.
[0195] Therefore, according to the data transmission method of the embodiment of the present application, early transmission of uplink data can be achieved, thereby saving power consumption and signaling overhead.
[0196] Next, combine Figure 4 and Figure 5 , respectively describe the data transmission method based on the CP scheme and the UP scheme. It should be understood that for Figure 4 and Figure 5 As shown in Figure 2 The same or corresponding steps can refer to the above Figure 2 To avoid repetition, Figure 4 and Figure 5 When introducing, the same or corresponding contents will not be described in detail.
[0197] Figure 4 A schematic flowchart of early transmission of uplink data based on a CP solution according to an embodiment of the present application.
[0198] S410, the terminal device sends Msg1 to the access network device.
[0199] S420, after receiving Msg1, the access network device sends Msg2 to the terminal device.
[0200] S430, the terminal device sends an RRC connection request message or an RRC connection re-establishment request message to the access network device, and the RRC connection request message or the RRC connection re-establishment request message carries the NAS PDU including the uplink data.
[0201] Optionally, the access network device can save the terminal device capability information of the CP solution. After receiving message 3, the access network device can find the access network device storing the capability information of the terminal device according to the S-TMSI. Then the access network device can determine whether the terminal device has the capability of early data transmission. If the terminal device does not have this capability, the connection can be rejected or rolled back to the normal process.
[0202] Among them, there is an abnormal situation that needs to be handled. When the MME reallocates the S-TMSI to the terminal device or the S-TMSI of the terminal device changes, the access network device does not know that because the S-TMSI is changed through NAS information transmission, the information saved by the access network device (such as the information obtained from the UE Information Transfer message) does not match the updated S-TMSI of the terminal device. Therefore, when the terminal device sends message 3, the S-TMSI carried may be the S-TMSI used by other terminal devices before. In this way, the terminal device capabilities and terminal device service quality (Quality of Service, QoS) information stored by the access network device will have corresponding errors. Therefore, the following solutions are proposed:
[0203] a: When MME reallocates S-TMSI to a terminal device, it notifies the access network device. The access network device can delete the information stored corresponding to the S-TMSI, including capability information, or notify the access network device of the newly allocated S-TMSI. After receiving the information, the access network device updates the S-TMSI so that the new S-TMSI of the terminal device can match the relevant information of the terminal device. The notification message is an S1AP message, such as a downlink NAS transmission message, a connection establishment indication message, etc. That is, the downlink NAS transmission message carries the S-TMSI for updating the S-TMSI to correspond to the relevant information of the terminal device previously received from the UE information transmission message.
[0204] b: To ensure that when switching access network devices, the old access network device can delete the message to prevent reallocation problems, when reallocating S-TMSI, MME will notify the access network devices that the terminal device has recently accessed so that they can update the S-TMSI in time or notify the access network devices that the terminal device has recently accessed to delete the stored old S-TMSI and the corresponding terminal device related information, such as UE QoS, terminal device radio capabilities, etc.
[0205] c: The access network device and MME will have a timer. When the access network device obtains the S-TMSI, there is a context of the terminal device corresponding to the S-TMSI. The access network device starts the timer. When the timer overflows, the relevant context is deleted. The MME also has a timer. When an S-TMSI is allocated, it starts. Before the timer overflows, the S-TMSI cannot be allocated to other terminal devices.
[0206] S440, the access network device sends a Retrieve UE Information Message to the MME, where the Retrieve UE Information Message includes the uplink data and may also be other message names, with no limitation to specific signaling names.
[0207] At this point, the MME can obtain the uplink data of the terminal device and realize early transmission of the uplink data.
[0208] Optionally, the terminal device information acquisition message further includes requesting downlink data indication information, and the method may further include:
[0209] S450, if the MME has downlink data, the MME sends a UE information transfer message (UEInformation Transfer) to the access network device, where the user information transfer message includes the downlink data and may also be other message names, and the specific signaling name is not limited;
[0210] S460: The access network device sends the downlink data to the terminal.
[0211] Optionally, the method may further include:
[0212] S470, the access network device sends a release message to the terminal device, where the release message is used to release the terminal device to an idle state.
[0213] Optionally, the release message may be an RRC connection establishment message, an RRC connection re-establishment message, an RRC connection recovery message, an RRC connection rejection message or an RRC connection release message.
[0214] Further, if the access network device sends an RRC connection establishment message or an RRC connection re-establishment message or an RRC connection recovery, the message may include relevant information in the RRC connection release, which is used to release the connection of the terminal device, and may specifically include a release reason, a redirection indication, etc.;
[0215] If the access network device sends an RRC connection rejection message, it may also carry an indication information, such as a cause value, used to indicate that the terminal device is released to the idle state;
[0216] If the access network device sends an RRC connection release message and carries the identification information of the terminal device, a MAC CE carrying the identification can also be added to the RRC message, and the terminal device is directly released to the idle state. Alternatively, the terminal device can send message 5 to the access network device, such as after the RRC connection is established, the access network device sends an RRC connection release message to the terminal device.
[0217] Optionally, as a specific embodiment of S460, the access network device may send downlink data to the terminal device through the release message in S370. That is, the downlink data may be carried in the release message. Further, the downlink data is data encapsulated in a NAS PDU.
[0218] Optionally, S470 may also be sent in a scenario where the MME has no downlink data transmission, that is, if the MME has no downlink data to transmit, the access network device may release the terminal device to an idle state by sending a release message to the terminal device.
[0219] Through RRC connection establishment message, RRC connection re-establishment message, RRC connection recovery or RRC connection rejection message, the terminal device can be released in advance when the MME has no downlink data transmission. Compared with the release process of the prior art, it can save signaling overhead and, on the other hand, can also reduce the power consumption of the terminal device.
[0220] Figure 5 It is a schematic flowchart of early transmission of uplink data based on the UP solution according to an embodiment of the present application.
[0221] S510, the terminal device sends Msg1 to the access network device.
[0222] S520, after receiving Msg1, the access network device sends Msg2 to the terminal device.
[0223] S530, the terminal device sends an RRC connection establishment request or an RRC connection recovery request message or an RRC connection re-establishment request message to the access network device.
[0224] The uplink data may be sent via a data radio bearer DRB. The uplink data needs to be encrypted, and the key may be updated by obtaining a next hop chaining count (NCC) from the last connection.
[0225] S540: The access network device sends a second request message to the MME.
[0226] Optionally, the content in the second request message may be the same as the content in the terminal device context recovery request message.
[0227] Furthermore, the second request message may be a terminal device context recovery request message.
[0228] After receiving the RRC connection recovery request message or the RRC connection re-establishment request message, the access network device verifies the terminal device according to the short Message Authentication Code for Integrity (short-MAC-I). If the access network device is not the original access network device, the short-MAC-I needs to be sent to the source access network device through the X2 port, and the source access network device performs verification. After success, the context information of the terminal device is sent to the current access network device, and subsequent operations are performed. S550, the MME sends a second response message to the access network device according to the second request message.
[0229] Optionally, the content in the second response message may be the same as the content in the terminal device context recovery response message.
[0230] Furthermore, the second response message is a terminal device context recovery response message.
[0231] If the access network device receives a response message and finds that the E-UTRAN radio access bearer (E-RAB) corresponding to the data received by the access network device is rejected, the access network device will send an RRC connection recovery message or an RRC connection establishment message to the terminal device, which may include an indication message indicating that the data E-RAB is rejected for transmission or fails to transmit or that the terminal device needs to resend the previously sent data packet. The access network device allocates an additional ULgrant for the data transmission.
[0232] S560: The access network device receives the second response message and sends the uplink data to the S-GW.
[0233] At this point, the S-GW can obtain the uplink data of the terminal device and realize early transmission of the uplink data.
[0234] Optionally, the method may further include:
[0235] S570, after the access network device successfully sends the uplink data, it can send a terminal device context release request message or a terminal device context suspension request message to the MME;
[0236] S580, the MME sends a terminal device context release command message to the access network device according to the terminal device context release request message, or the MME sends a terminal device context suspension completion message to the access network device according to the context suspension request message;
[0237] S590, the access network device sends the release message to the terminal device according to the terminal device context release command message or the terminal device context suspension completion message, wherein the release message is used to release the terminal device to an idle state.
[0238] Optionally, the release message here may be an RRC connection establishment message, an RRC connection recovery message, an RRC connection re-establishment message, an RRC connection rejection message or an RRC connection release message.
[0239] Further, if the access network device sends an RRC connection establishment message or an RRC connection re-establishment message or an RRC connection recovery message, the message may include relevant information in the RRC connection release, which is used to release the connection of the terminal device, and may specifically include a release reason, a redirection indication, etc.;
[0240] If the access network device sends an RRC connection rejection message, it may also carry an indication information, such as a cause value, indicating that the terminal device is released to the idle state;
[0241] If the access network device sends an RRC connection release message, the terminal device is directly released to the idle state.
[0242] If the access network device also receives downlink data during this process, it can be sent to the terminal device together with the release message.
[0243] Through the RRC connection establishment message, RRC connection recovery message, RRC connection re-establishment completion message, RRC connection rejection message or RRC connection release message, the terminal device can be released in advance when the S-GW has no downlink data transmission. Compared with the release process of the prior art, it can save signaling overhead and, on the other hand, can also reduce the power consumption of the terminal device.
[0244] Figure 6 This is a data transmission method based on the CP scheme according to another embodiment of the present application. Figure 6 The method shown is applicable to early transmission of downlink data.
[0245] S610, the terminal device sends a random access preamble to the access network device. In other words, the terminal device sends a random access request message, namely, message 1 (Msg1), to the access network device. Specifically, reference may be made to the prior art, and for the sake of brevity, it will not be described here.
[0246] S620, after receiving Msg1, the access network device sends a random access response message to the terminal device, that is, the access network device sends message 2 (Msg2).
[0247] Msg2 carries TA and UL Grant, where UL Grant is a resource allocated by the access network device to the terminal device for the terminal device to transmit message 3 (Msg3). For details about TA and UL Grant, please refer to the prior art and will not be described in detail here.
[0248] S630, the terminal device sends Msg3 to the access network device, and the Msg3 may include a service request message (Service Request Message).
[0249] If downlink early transmission is not distinguished by message 1 or time-frequency code resources, an indication can be made in message 3, indicating that the UE wants to perform downlink data early transmission, that is, to transmit downlink data before the RRC connection is established. After the access network device receives the indication message, it can trigger signaling interaction with the core network device earlier.
[0250] Optionally, Msg3 may be an RRC connection request message or an RRC connection re-establishment request message.
[0251] S640: After receiving Msg3, the access network device sends a request message to the MME.
[0252] The message may be a message for obtaining UE information or other messages.
[0253] S650: After receiving the request message, the MME sends the downlink data to the access network device.
[0254] Optionally, the MME may send the downlink data to the access network device via a UE information transmission message. That is, the UE information transmission message may carry the downlink data.
[0255] S660, the access network device sends the downlink data to the terminal device.
[0256] Optionally, the access network device may send the downlink data to the terminal device via a release message. Meanwhile, the terminal device may enter an idle state after receiving the release message.
[0257] Optionally, the release message here may be an RRC connection establishment message, an RRC connection recovery message, an RRC connection re-establishment message, an RRC connection rejection message or an RRC connection release message.
[0258] Further, if the access network device sends an RRC connection establishment message or an RRC connection re-establishment message or an RRC connection recovery message, the message may include relevant information in the RRC connection release, which is used to release the connection of the terminal device, and may specifically include a release reason, a redirection indication, etc.;
[0259] If the access network device sends an RRC connection rejection message, it may also carry an indication information, such as a cause value, indicating that the terminal device is released to the idle state;
[0260] If the access network device sends an RRC connection release message, the terminal device is directly released to the idle state.
[0261] Through the RRC connection establishment message, RRC connection recovery message, RRC connection re-establishment message, RRC connection rejection message or RRC connection release message, the terminal device can be released in advance when the MME has no downlink data transmission. Compared with the release process of the prior art, it can save signaling overhead and, on the other hand, can also reduce the power consumption of the terminal device.
[0262] Therefore, according to the data transmission method of the embodiment of the present application, early transmission of uplink data can be achieved, thereby saving power consumption and signaling overhead.
[0263] Figure 7 This is a data transmission method based on the UP scheme according to another embodiment of the present application. Figure 7 The method shown is applicable to early transmission of downlink data.
[0264] Figure 7 It is a schematic flowchart of a data transmission method according to an embodiment of the present application.
[0265] S710, the terminal device sends a random access preamble to the access network device. In other words, the terminal device sends a random access request message, namely, message 1 (Msg1), to the access network device. Specifically, reference may be made to the prior art, and for the sake of brevity, it will not be described here.
[0266] S720, after receiving Msg1, the access network device sends a random access response message to the terminal device, that is, the access network device sends message 2 (Msg2).
[0267] Msg2 carries TA and UL Grant, where UL Grant is a resource allocated by the access network device to the terminal device for the terminal device to transmit message 3 (Msg3). For details about TA and UL Grant, please refer to the prior art and will not be described in detail here.
[0268] S730, the terminal device sends Msg3 to the access network device according to Msg2, and the Msg3 may include a service request message (Service Request Message).
[0269] If downlink early transmission is not distinguished by message 1 or time-frequency code resources, an indication can be made in message 3, indicating downlink data early transmission, that is, downlink data transmission before the RRC connection is established. After the access network device receives the indication message, it can trigger signaling interaction with the core network device earlier. Please refer to S740 and subsequent operations.
[0270] Optionally, Msg3 may be an RRC connection request or an RRC connection recovery request message or an RRC connection re-establishment request message.
[0271] S740, after receiving the service request message in Msg3, the access network device sends the service request message to the MME.
[0272] Optionally, the access network device may send the service request message to the MME via a terminal device context recovery request message.
[0273] S750, the MME sends a service response message to the access network device according to the service request message.
[0274] Optionally, the MME may send a terminal device context recovery response message after receiving the terminal device context recovery request message sent by the access network device.
[0275] S760, the MME sends a modify bearer request message to the S-GW;
[0276] S770, the S-GW replies a modify bearer response message to the MME, so that the S-GW can obtain the address of the access network device.
[0277] S780, the S-GW sends the downlink data to the access network device.
[0278] S790, the access network device sends the downlink data to the terminal device.
[0279] Optionally, before S600, after the access network device receives the downlink data sent by the S-GW, the method may further include:
[0280] The access network device sends a terminal device context release request message or a terminal device context suspension request message to the MME;
[0281] The MME sends a terminal device context release command message to the access network device according to the terminal device context release request message, or the MME sends a terminal device context suspension completion message to the access network device according to the context suspension request message;
[0282] The access network device sends the release message to the terminal device according to the terminal device context release command message or the terminal device context suspension completion message, and the release message is used to release the terminal device to the idle state.
[0283] Optionally, the release message here may be an RRC connection establishment message, an RRC connection recovery message, an RRC connection reestablishment message, an RRC connection rejection message or an RRC connection release message. For specific information on the release, refer to other embodiments.
[0284] Further, if the access network device sends an RRC connection establishment message, the message may include relevant information in the RRC connection release, which is used to release the connection of the terminal device, and may specifically include a release reason, a redirection indication, etc.;
[0285] If the access network device sends an RRC connection rejection message, it may also be sent with a cause value, where the cause value indicates that the terminal device is released to the idle state;
[0286] If the access network device sends an RRC connection release message, the terminal device is directly released to the idle state.
[0287] Optionally, in S790, the access network device may send the downlink data to the terminal device via the release message.
[0288] Through the RRC connection establishment message, RRC connection recovery message, RRC connection re-establishment completion message, RRC connection rejection message or RRC connection release message, the terminal device can be released in advance when the S-GW has no downlink data transmission. Compared with the release process of the prior art, it can save signaling overhead and, on the other hand, can also reduce the power consumption of the terminal device.
[0289] Therefore, according to the data transmission method of the embodiment of the present application, early transmission of uplink data can be achieved, thereby saving power consumption and signaling overhead.
[0290] Optionally, in one possible implementation, when the UE receives a paging message, the paging message may include an indication information, indicating that the UE can perform an early downlink data reception operation, so that the UE can perform subsequent processes according to the early downlink data reception operation. Further, the core network device may carry an indication information in the paging message sent to the base station, indicating that the UE needs to perform an early downlink data reception operation.
[0291] Optionally, when the terminal device is in a connected state, the access network device may also send an indication to the terminal device through a Physical Downlink Control Channel (PDCCH) command to indicate that the UE needs to perform random access for early data transmission, such as early uplink data transmission or early downlink data transmission. That is, random access is performed through the PDCCH order method. The specific indication information may be carried by DCI, or the resource location indicated by the access network device for UE access is a resource location for early data transmission to achieve early data transmission. In this way, in the connected state, the access network device can instruct the UE to use the method of early data transmission through PDCCH.
[0292] Figure 8 FIG. 8 is a schematic block diagram of a terminal device 800 according to an embodiment of the present application. Figure 8 As shown, the terminal device 800 includes: a processing unit 810 and a transceiver unit 820.
[0293] The processing unit 810 is used to generate a first indication, where the first indication is used to indicate that data needs to be transmitted before the radio resource control RRC connection is established.
[0294] The transceiver unit 820 is configured to send a first indication to the access network device, where the first indication is used to indicate that data needs to be transmitted before the radio resource control RRC connection is established;
[0295] And before the RRC connection is established, data is transmitted between the access network device.
[0296] Optionally, when the first indication is a random access preamble code, the transceiver unit 820 is specifically used to: send a first random access preamble code to the access network device.
[0297] Optionally, the transceiver unit 820 is specifically used to: send a random access preamble code to the access network device on the first random access resource.
[0298] Optionally, the transceiver unit 820 is specifically configured to: send a message 3 including a first indication to the access network device, wherein the message 3 is any one of the following messages:
[0299] RRC connection request message, RRC connection re-establishment request message and RRC connection recovery request, wherein the RRC connection request message or the RRC connection re-establishment request message carries a non-access stratum protocol data unit NAS PDU including data to be transmitted.
[0300] Optionally, the first indication is used to indicate that data needs to be transmitted before the radio resource control RRC connection is established, including:
[0301] The first indication is used to indicate that downlink data needs to be transmitted before the RRC connection is established.
[0302] Optionally, the transceiver unit 820 is specifically configured to: transmit a non-access layer protocol data unit NAS PDU between the access network device before the RRC connection is established; or,
[0303] Before the RRC connection is established, data is transmitted between the access network device via a data radio bearer DRB.
[0304] Optionally, the transceiver unit 820 is specifically used to: receive a release message sent by the access network device, the release message is a wireless resource control RRC connection establishment message, an RRC connection recovery message, an RRC connection re-establishment completion message, an RRC connection rejection message or an RRC connection release message, and the release message is used to release the terminal device to an idle state.
[0305] It should be understood that the processing unit 810 may be implemented by a processor, and the transceiver unit 820 may be implemented by a transceiver.
[0306] It should also be understood that the terminal device 800 may correspond to the terminal device described in the above method, and each module or unit in the terminal device 800 is respectively used to execute Figures 2 to 7 The detailed description of each action or processing process performed by the terminal device in the method embodiment is omitted here to avoid redundancy.
[0307] Fig. 9 FIG. 9 is a schematic block diagram of an access network device 900 according to an embodiment of the present application. Fig. 9 As shown, the access network device 900 includes: a processing unit 910 and a transceiver unit 920 .
[0308] The transceiver unit 920 is configured to receive a first indication sent by a terminal device, where the first indication is used to indicate that data needs to be transmitted before a radio resource control RRC connection is established;
[0309] The processing unit 910 is used to determine whether the current state is before the RRC connection establishment is completed;
[0310] The transceiver unit 920 is used to transmit data between the terminal device before the processing unit 910 determines that the RRC connection establishment is completed.
[0311] Optionally, when the first indication is a random access preamble code, the transceiver unit 920 is specifically used to: receive a first random access preamble code sent by the terminal device.
[0312] Optionally, the transceiver unit 920 processing unit 910: receives a random access preamble code sent by the terminal device in the first random access resource.
[0313] Optionally, the transceiver unit 920 processing unit 910: receives a message 3 including a first indication sent by the terminal device, wherein the message 3 is any one of the following messages:
[0314] RRC connection request message, RRC connection re-establishment request message and RRC connection recovery request, wherein the RRC connection request message or the RRC connection re-establishment request message carries a non-access stratum protocol data unit NAS PDU including data to be transmitted.
[0315] Optionally, the first indication is used to indicate that data needs to be transmitted before the radio resource control RRC connection is established, including:
[0316] The first indication is used to indicate that downlink data needs to be transmitted before the RRC connection is established.
[0317] Optionally, the transceiver unit 920 processing unit 910: before the RRC connection is established, transmits a non-access layer protocol data unit NAS PDU between the terminal device; or,
[0318] Before the RRC connection is established, data is transmitted between the terminal device via a data radio bearer DRB.
[0319] Optionally, the transceiver unit 920 processing unit 910: sends a release message to the terminal device, the release message is a radio resource control RRC connection establishment message, an RRC connection recovery message, an RRC connection re-establishment completion message, an RRC connection rejection message or an RRC connection release message, and the release message is used to release the terminal device to an idle state.
[0320] It should be understood that the processing unit 910 may be implemented by a processor, and the transceiver unit 920 may be implemented by a transceiver.
[0321] It should also be understood that the access network device 900 may correspond to the access network device described in the above method, and each module or unit in the access network device 900 is respectively used to execute Figures 2 to 7 The detailed description of each action or processing process performed by the access network device in the method embodiment is omitted here to avoid redundancy.
[0322] Fig.10 is a schematic flow chart of a data transmission method according to another embodiment of the present application. It should be understood that Fig.10The detailed communication steps or operations of the method are shown, but these steps or operations are only examples. The embodiment of the present application may also perform other operations or Fig.10 In addition, Fig.10 The steps in Fig.10 are executed in a different order than those presented, and may not be executed in the order Fig.10 All operations in .
[0323] S1010: The terminal device sends a first indication to the access network device. Correspondingly, the access network device receives the first indication.
[0324] Among them, the first indication is used to instruct the terminal device to transmit data (i.e., uplink data) based on the first radio resource control RRC signaling sent by the terminal device to the access network device, and / or, the first indication is used to instruct the access network device to transmit data (i.e., downlink data) based on the first radio resource control RRC signaling sent by the access network device to the terminal device. Specifically, the first indication is used to indicate that the first signaling transmitted between the terminal device and the access network device carries data, or transmits data while transmitting the first signaling, or transmits data immediately after transmitting the first signaling. The first signaling is the first RRC signaling between the terminal device and the access network device during the random access process. That is to say, the first indication is used to indicate that the terminal device will transmit uplink data based on the first RRC signaling between the terminal device and the access network device, and / or, the first indication is used to indicate that the access network device will transmit downlink data based on the first RRC signaling between the terminal device and the access network device.
[0325] In the following, for ease of description and understanding, the first RRC signaling sent by the terminal device to the access network device is recorded as RRC signaling #1, and the first RRC signaling sent by the access network device to the terminal device is recorded as RRC signaling #2.
[0326] Accordingly, the terminal device can send uplink data to the access network device based on RRC signaling #1, and the access network device can send downlink data to the terminal device based on RRC signaling #2. In other words, the terminal device can perform early transmission of uplink data based on RRC signaling #1, and the access network device can perform early transmission of downlink data based on RRC signaling #2.
[0327] Optionally, RRC signaling #1 may be message 3 (Msg3).
[0328] Msg3, for example, may be an RRC connection request message, an RRC connection re-establishment request message, or an RRC connection recovery request message.
[0329] Regarding the RRC connection request message, the RRC connection re-establishment request message and the RRC connection recovery request message, specific details may be referred to the prior art, and for the sake of brevity, they will not be described here.
[0330] In addition, RRC signaling #1 may also be the newly defined first RRC signaling sent by the terminal device to the access network device during the random access process (for example, recorded as an RRC connection data transmission message). The RRC connection data transmission message is a message that does not require RRC connection management. The RRC connection data transmission message may be the first message after message 2 (Msg2, i.e., the random access response message).
[0331] Furthermore, the RRC signaling #1 may also carry Release Assistance Indication (RAI) information, which is used to indicate that there is no uplink data in a short period of time. The terminal device maintains the RRC idle state according to the Release Assistance Indication information.
[0332] Furthermore, if the data is transmitted via a NAS message, when the data is sent, the NAS message may also carry release assistance indication information (RAI). The indication message may indicate to the core network device whether there will be uplink data or downlink data, or just a confirmation or response to the reception of the uplink data.
[0333] Below, for ease of understanding, without loss of generality, the data transmission method of the present application is described by taking RRC signaling #1 as message 3 as an example.
[0334] Optionally, the terminal device may send a first indication to the access network device by sending a message 1 (Msg1), ie, a random access request message. That is, the message 1 or the information in the message 1 may be used to indicate early transmission of uplink data or early transmission of downlink data.
[0335] For example, the preamble (or preamble sequence) in message 1 can be used to indicate early transmission of uplink data and / or early transmission of downlink data. For example, if the preamble in message 1 is preamble #2, it indicates early transmission of uplink data; if the preamble in message 1 is preamble #3, it indicates early transmission of downlink data; if the preamble in message 1 is preamble #3, it indicates early transmission of uplink data and early transmission of downlink data at the same time.
[0336] For example, the terminal device can send message 1 to the access network device on a specific resource, and indicate early transmission of uplink data and / or early transmission of downlink data through the specific resource. The specific resource can be a time-frequency code resource. For example, if the terminal device uses time-frequency code resource #2 to send message 1, it means that the terminal device wants to perform early transmission of uplink data, and the terminal device uses time-frequency code resource #3 to indicate that the terminal device wants to perform early transmission of downlink data. Among them, the time-frequency code can be any combination of time domain, frequency domain, and code domain.
[0337] In addition, in the scenario of early transmission of uplink data, exemplarily, the access network device can allocate time and frequency resources for sending uplink data at the same time while allocating time and frequency resources used to send RRC signaling #1 to the terminal device through message 2 (Msg2), i.e., the random access response message.
[0338] Figures 11 to 14 Several formats of message 2 are shown. In the present application, message 2 may adopt any of the formats.
[0339] like Figures 11 to 14 The format of the message 2 shown includes an uplink timing control field (Timing Advance Command, TAC) and a temporary cell radio network temporary identification field (TC-RNTI). The value in the uplink timing control field represents the time advance adjustment amount, which is used for the terminal device to perform uplink synchronization. The value in the radio network temporary identification field represents the unique identifier in the cell allocated by the access network device to the terminal device. The time advance adjustment amount and C-RNTI can be specifically referred to the prior art, and will not be introduced in detail in this article.
[0340] TC-RNTI, for example, can be RNTI, hash S-TMSI, S-TMSI, truncated S-TMSI, access random number, IMSI, the identifier of the terminal device carried in the MAC CE, etc. This application does not specifically limit the identifier of the terminal device.
[0341] Below, respectively Figures 11 to 14 The format of message 2 shown is described in detail.
[0342] Fig.11 This is a schematic diagram of a format of message 2. Fig.11As shown, the value in the reserved field (R) is used to indicate the number of uplink resource allocation fields (UL Grant) included in message 2. For example, when the value in the reserved field is 1, it means that message 2 includes two uplink resource allocation fields (respectively denoted as UL Grant #1 and UL Grant #2), and UL Grant #1 and UL Grant #2 are not adjacent. Among them, the value in UL Grant #1 is used to indicate the time-frequency resources used to send RRC signaling #1, and the value in UL Grant #2 is used to indicate the time-frequency resources used to send uplink data.
[0343] It should be understood that Fig.11 The number of bits occupied by each field in message 2 shown in FIG. 2 is only an example, and the present application does not specifically limit the number of bits occupied by each field in message 2. For example, Fig.12 The UL Grant #1 and UL Grant #2 shown occupy 20 bits and 16 bits respectively. In actual applications, UL Grant #1 and UL Grant #2 may also occupy 16 bits and 20 bits respectively, or both occupy 16 bits.
[0344] Fig.12 is a schematic diagram of another format of message 2. Fig.12 As shown, the value in the reserved field (R) is used to indicate the number of uplink resource allocation fields (UL Grant) included in message 2. For example, when the value in the reserved field is 1, it means that message 2 includes two uplink resource allocation fields (respectively denoted as UL Grant #1 and UL Grant #2), and UL Grant #1 and UL Grant #2 are adjacent. Among them, the value in UL Grant #1 is used to indicate the time-frequency resources used to send RRC signaling #1, and the value in UL Grant #2 is used to indicate the time-frequency resources used to send uplink data.
[0345] It should be understood that Fig.12 The number of bits occupied by each field in message 2 shown in FIG. 2 is only an example, and the present application does not specifically limit the number of bits occupied by each field in message 2. For example, Fig.12 The UL Grant #1 and UL Grant #2 shown occupy 20 bits and 16 bits respectively. In actual applications, UL Grant #1 and UL Grant #2 may also occupy 16 bits and 20 bits respectively, or both occupy 16 bits.
[0346] Fig.13 is a schematic diagram of another format of message 2. Fig.13As shown, the value in the reserved field (R) is used to indicate the role of the time-frequency resources indicated by the uplink resource allocation field (UL Grant). For example, when the value in the reserved field is 1, it indicates that the time-frequency resources indicated by the UL Grant field are used to transmit RRC signaling #1 and uplink data; when the value in the reserved field is 0, it indicates that the time-frequency resources indicated by the value in the UL Grant are only used to transmit RRC signaling #1. Or when the value in the reserved field is 0, it indicates that the time-frequency resources indicated by the UL Grant field are used to transmit RRC signaling #1 and uplink data; when the value in the reserved field is 1, it indicates that the time-frequency resources indicated by the value in the UL Grant are only used to transmit RRC signaling #1. It should be understood that Fig.13 The number of bits occupied by each field in message 2 shown in FIG. 2 is only an example, and the present application does not specifically limit the number of bits occupied by each field in message 2. For example, Fig.13 The UL Grant shown occupies 36 bits. In actual applications, the UL Grant may occupy 30 bits.
[0347] Fig.14 This is a schematic diagram of a format of message 2. Fig.14 As shown, the value in the first reserved field (R#1) or the value of the first bit in the second reserved field (R#2) is used to indicate the number of uplink resource allocation (ULGrant) fields included in message 2. For example, when the value in R#2 is 1, it means that message 2 includes two uplink resource allocation fields (respectively denoted as UL Grant#1 and UL Grant#2). Among them, the value in UL Grant#1 is used to indicate the time-frequency resources used to send RRC signaling #1, and the value in UL Grant#2 is used to indicate the time-frequency resources used to send uplink data.
[0348] It should be understood that the first bit in R#2 can be any bit in R#2. Figure 6 The number of bits occupied by each field in message 2 shown in the figure is only an example, and the present application does not specifically limit the number of bits occupied by each field in message 2.
[0349] It should also be understood that Figures 11 to 14 The format of the message 2 shown is only an example. In the embodiment of the present application, the message 2 may also adopt other formats or Figures 11 to 14 For example, the positions of the fields in message 2 may be different from Figures 11 to 14 The position of each field in the format of message 2 shown in FIG. For another example, the format of message 2 may also include Figures 11 to 14 Other fields than those shown, or the format of message 2 may include only Figures 11 to 14 Some of the fields shown.
[0350] In summary, in the above embodiments, it is possible to indicate through reserved bits whether there are two or more UL grants or whether it is a large UL grant (capable of transmitting data).
[0351] Optionally, RRC signaling #2 may be message 4 (Msg4).
[0352] Message 4 may be, for example, a contention resolution message, an RRC connection establishment message, an RRC connection re-establishment message, an RRC connection recovery message, an RRC connection rejection message or an RRC connection release message.
[0353] In addition, message 4 may also be the newly defined first RRC signaling sent by the access network device to the terminal device during the random access process, which is not limited in the embodiments of the present application.
[0354] S1020, based on the first RRC signaling, data is transmitted between the terminal device and the access network device.
[0355] That is, the terminal device sends uplink data to the access network device based on RRC signaling #1; and / or the access network device sends downlink data to the terminal device based on RRC signaling #2.
[0356] Optionally, the uplink data and / or the downlink data may be sent via a non-access stratum protocol data unit NAS PDU.
[0357] For example, RRC signaling #1 can carry NAS PDU of uplink data. That is, the terminal device can send uplink data through the NAS PDU carried by RRC signaling #1. For another example, the terminal device can send NAS PDU carrying uplink data and RRC signaling #1 to the access network device at the same time, or the terminal device can send NAS PDU carrying uplink data immediately after sending RRC signaling #1.
[0358] For another example, RRC signaling #2 can carry NAS PDU of downlink data. That is, the access network device can send downlink data through the NAS PDU carried by RRC signaling #2. For another example, the access network device can send NAS PDU carrying downlink data and RRC signaling #1 to the terminal device at the same time, or the access network device can send NAS PDU carrying downlink data immediately after sending RRC signaling #2.
[0359] Optionally, uplink data or downlink data may be sent via DRB or SRB0.
[0360] In the present application, uplink data and RRC signaling #1 can be multiplexed into one transport block, or can be transmitted separately as two or more transport blocks. Downlink data and RRC signaling #2 can be multiplexed into one transport block, or can be transmitted separately as two or more transport blocks.
[0361] It should be noted that, when RRC signaling #1 and uplink data are transmitted together, RRC signaling #1 can carry the identification of the terminal device. When RRC signaling #1 and uplink data are transmitted separately, the uplink data can carry the identification of the terminal device or be scrambled by the identification of the terminal device. Similarly, when RRC signaling #2 and downlink data are transmitted together, RRC signaling #2 can carry the identification of the terminal device. When RRC signaling #2 and downlink data are transmitted separately, the downlink data can carry the identification of the terminal device or be scrambled by the identification of the terminal device.
[0362] The identifier of the terminal device may be, for example, RNTI, hashed S-TMSI, S-TMSI, truncated S-TMSI, access random number, IMSI, the identifier of the terminal device carried in the MAC CE, etc. This application does not specifically limit the identifier of the terminal device.
[0363] Further, taking the transmission of uplink data as an example, if the uplink data can be transmitted separately with RRC signaling #1 as two transmission blocks, the NAS PDU carrying the uplink data can be sent through SRB 1bis or SRB0, or RRC signaling #1 is sent through SRB0 and the uplink data is sent through DRB. It should be understood that the transmission of downlink data can refer to the method of transmitting uplink data, and for the sake of brevity, it will not be repeated here.
[0364] Furthermore, if the terminal device sends uplink data via a NAS message in message 3, the NAS message may be a control plane service request message (Control Plane Service Request (ESM Data Transport)).
[0365] Therefore, according to the method of the embodiment of the present application, uplink and / or downlink data transmission can be achieved based on the first RRC signaling between the terminal device and the access network device without establishing an RRC connection, thereby saving the signaling overhead of establishing the required bearer for data transmission and reducing device power consumption.
[0366] The following, combined Figures 15 to 18 , respectively, for uplink data early transmission and downlink data early transmission, respectively, describe the data transmission method according to the embodiment of the present application. It should be understood that, Figures 15 to 18 As shown in Figure 2 The same or corresponding steps, terms, concepts, etc. can refer to the above Figure 2 To avoid repetition, Figures 15 to 18 When introducing, the same or corresponding contents will not be described in detail.
[0367] Without loss of generality, the following description uses RRC signaling #1 as message 3 and RRC signaling #2 as message 4 as an example to describe the various embodiments of the present application.
[0368] Fig.15 It is a schematic flowchart of a data transmission method according to an embodiment of the present application. Fig.15 The method shown is applicable to early transmission of uplink data based on the CP solution.
[0369] S1510, the terminal device sends message 1 to the access network device.
[0370] Among them, message 1 is used to instruct the terminal device to transmit data using the uplink and / or downlink data early transmission method.
[0371] S1520, after receiving message 1, the access network device sends message 2 to the terminal device.
[0372] Optionally, in an embodiment of the present application, if the access network device learns from message 1 that the UE wants to perform early transmission of uplink data, it allocates resources for transmitting uplink data to the terminal device.
[0373] Furthermore, the size of the resource used to transmit the uplink data may be fixed, such as 100 bytes. The size of the resource used to transmit the uplink data may also be determined by the access network device according to the first message (e.g., the resource for sending the first message or the preamble in the first message). In other words, the first message, such as the resource for sending the first message or the preamble in the first message, may also be used to indicate the size of the uplink data, so that the access network device can reasonably allocate the resources for transmitting the uplink data according to the size of the uplink data.
[0374] S1530, the terminal device sends message 3 to the access network device.
[0375] For example, message 3 may carry uplink data.
[0376] For example, after the terminal device receives message 2, if there is uplink data to be transmitted, it can transmit the uplink data on the pre-configured or reserved resources for early transmission of uplink data while transmitting message 3.
[0377] For another example, the terminal device may also transmit message 3 and uplink data on the target resources indicated by message 2.
[0378] The definition of message 3 is the same as that in the above embodiment, and the specific message name is not limited.
[0379] S1540, the access network device sends a candidate message #1 to the MME.
[0380] The candidate message #1 includes the uplink data. The candidate message #1 may be, for example, a Retrieve UE Information Message or an Initial UE Message, or other newly defined messages, which are not limited in the embodiments of the present application.
[0381] At this point, the MME can obtain the uplink data of the terminal device and realize early transmission of the uplink data.
[0382] Optionally, the method may further include:
[0383] S1560, the access network device sends candidate message #3 to the terminal device.
[0384] Alternatively, candidate message #3 may be message 4.
[0385] In addition, candidate message #3 may also be the first RRC message sent by the newly defined access network device to the terminal device, which is not limited to this in the embodiments of the present application.
[0386] Optionally, candidate message #3 may carry an indication information (for example, recorded as indication information #2). Indication information #2 is used to indicate that the current process or session process can be ended, or to indicate that the terminal device needs to return to or maintain an idle state. The indication information #2 may be expressed as a stop indication (End Indication) or a release indication (Release Indication).
[0387] Optionally, after receiving message 4, the terminal device sends message 5 to the access network device. Message 5 may be, for example, an RRC connection completion message, an RRC connection re-establishment completion message, or an RRC connection recovery completion message.
[0388] In a possible implementation, the NAS message is not carried in the message 5. If the access network device has downlink data to transmit at this time, after receiving the message 5, the access network device sends the downlink data to the terminal device and instructs the terminal device to return to the idle state or remain in the idle state.
[0389] In another possible implementation, after the terminal device receives message 4 (for example, a contention resolution message, an RRC connection establishment message, an RRC connection re-establishment message, or an RRC connection recovery), it establishes an RRC connection according to the normal RRC connection establishment process. If the terminal device has no uplink data at this time, the terminal device can send an empty NAS message (for example, recorded as NAS message #1) on message 5 (such as RRC connection establishment completed, RRC connection re-establishment completed, RRC connection recovery completed), such as ESM Data Transport, NAS message #1 has only a message header but no data unit. After receiving NAS message #1, the access network device sends NAS message #1 to the MME through the initial UE message or other messages. After receiving the message, the MME can ignore or discard the NAS message. The subsequent process is the same as the prior art and will not be repeated here for the sake of brevity.
[0390] In another possible implementation, the terminal device may send the same NAS message as in message 3 (e.g., recorded as NAS message #2), such as a control plane service request (Control Plane Service Request (ESM Data Transport)) message, in message 5 (e.g., RRC connection establishment complete, RRC connection re-establishment complete, RRC connection recovery complete). Further, the NAS message #2 may include an indication information (e.g., recorded as indication information #3), and the indication information #3 is used to indicate that the NAS message #2 is the same as the NAS message transmitted in the message 3. After receiving the NAS message #2, the access network device sends the NAS message to the MME, and the MME may ignore the message according to the indication information.
[0391] In another possible implementation, the UE may send a NAS message (e.g., recorded as NAS message #3) in message 5 (e.g., RRC connection establishment complete, RRC connection re-establishment complete, RRC connection recovery complete), and NAS message #3 may include an indication information (e.g., recorded as indication information #4), and indication information #4 is used to distinguish NAS message #3 from the NAS message in message 5 in the prior art, so as to facilitate subsequent processing by the MME. After receiving indication information #4, the MME may ignore or discard the NAS message. Or the NAS message and the indication information are two fields. Therefore, the NAS message #3 may carry the indication information and may be divided into different fields from the indication information. The application scenario of NAS message #3 is: NAS message #3 is used only when the uplink data has been transmitted through RRC signaling #1 and there is no additional uplink NAS data in message 5. Since the terminal device has sent the NAS message in message 3, the above-mentioned implementations can overcome the problem that the NAS message is mandatory in the existing message 5 and the initial UE message.
[0392] The above implementation method can be applied to the case where there is a downlink packet but the access network device cannot transmit it, or when the core network device has multiple downlink packets, so as to complete data transmission.
[0393] In this way, through the indication information #2 in the candidate message #3, the terminal device can be released in advance or the terminal can be indicated to be in idle state when the MME has no downlink data transmission. Compared with the release process of the prior art, it can save signaling overhead and, on the other hand, can also reduce the power consumption of the terminal device.
[0394] Furthermore, if candidate message #3 is an RRC connection establishment message, an RRC connection re-establishment message, or an RRC connection recovery message, candidate message #3 may also include a redirection indication, etc.
[0395] If candidate message #3 is an RRC connection rejection message, candidate message #3 may also carry indication information, where the indication information is used to instruct the terminal to return to or remain in the idle state.
[0396] Optionally, candidate message #3 may carry downlink data.
[0397] Furthermore, the downlink data may be encapsulated in a NAS PDU. That is, candidate message #3 may carry a NAS PDU including the downlink data. The NAS PDU may be carried on SRB0.
[0398] The downlink data may be sent by the MME to the access network device through a paging message, or may be sent by the MME to the access network device through a candidate message #2.
[0399] In addition, the downlink data may also be sent by the MME to the access network device through downlink NAS transmission between the MME and the access network device after the MME sends the candidate message #2 and before the access network device sends the candidate message #3.
[0400] For example, the access network device can tell the MME in advance the size of the data packet that it can schedule. For example, the access network device indicates the size of the data packet that it can schedule through candidate message #1, and the MME can depacketize the downlink data and send it to the access network device. In this case, the access network device can continuously send multiple data packets to the terminal device, each data packet carries the identification information of the terminal device, and after sending the last data packet, the access network device can send indication information #2 to the terminal to release the terminal device or instruct the terminal to return to or remain in an idle state.
[0401] Optionally, if the downlink data is sent by the MME to the access network device through the candidate message #2, before S1560, the method further includes:
[0402] S1550, the MME sends a candidate message #2 to the access network device, wherein the candidate message #2 includes the downlink data.
[0403] Candidate message #2 may be, for example, a UE Information Transfer Message, a Downlink NAS Transport Message, or a newly defined message, which is not limited in the embodiment of the present application.
[0404] Optionally, candidate message #2 may also include an indication message (for example, indicated as indication message #1), where indication message #1 is used to indicate that the current process or session can be ended, or to indicate that the terminal device needs to return to or remain in an idle state. Indication message #1 may be an end indication.
[0405] For example, when the MME sends candidate message #2 to the access network device, if there is no downlink data, the MME can carry indication information in the message, and the indication information is used to indicate the end of the process or instruct the access network device to instruct the terminal device to return to the idle state or maintain the idle state.
[0406] For example, when the MME sends candidate message #2 to the access network device, if there is downlink data, if there is only one data packet, the MME carries indication information in the message, and the indication information is used to indicate the end of the process or instruct the access network device to instruct the terminal device to return to the idle state or maintain the idle state.
[0407] For example, if the MME has multiple terminal downlink packets arriving at the MME, the MME will not carry the indication information when sending candidate message #2 to the access network device. It should be understood that at this time, the terminal device has not entered the connected state, and belongs to the idle state or an intermediate state between the idle state and the connected state, or the terminal's transition state is that the air interface does not enter the connected state, and the S1 port enters the connected state.
[0408] Therefore, the MME can send indication information #1 to indicate that the access network device can notify the terminal device to return to or maintain the idle state. It should also be understood that indication information #2 can be the same as indication information #1 or different, and the embodiment of the present application is not limited to this.
[0409] Furthermore, after the access network device sends downlink data to the terminal device, it can send a positive confirmation (ACK) to the MME, such as sending NAS deliver ACK. ACK is used to indicate that the access network device has sent the downlink data to the terminal device, and the MME does not need to send a paging message to the access network device.
[0410] Optionally, in S1560, if the access network device does not send the downlink data to the terminal device, the access network device may feedback to the MME that the data was not sent successfully or send the unsent data to the MME, and the MME will enable the terminal device to obtain the data by paging.
[0411] Therefore, according to the data transmission method of the embodiment of the present application, the transmission of uplink data can be achieved based on the first RRC signaling sent by the terminal device to the access network device without establishing an RRC connection, thereby saving power consumption and signaling overhead.
[0412] Fig.16 It is a schematic flowchart of a data transmission method according to an embodiment of the present application. Fig.16 The method shown is applicable to early transmission of uplink data based on the UP solution. Fig.16 The same or corresponding terms, concepts, etc. can be found in the above Fig.15 In order to avoid repetition, the description will not be repeated below.
[0413] S1610, the terminal device sends message 1 to the access network device.
[0414] S1620, after receiving message 1, the access network device sends message 2 to the terminal device.
[0415] S1630, the terminal device sends message 3 to the access network device.
[0416] Message 3 includes uplink data, which can be sent via a data radio bearer DRB. The uplink data needs to be encrypted, and the key can be updated by obtaining the next hop chaining count (NCC) obtained from the last connection.
[0417] Furthermore, the bearer DRB for the terminal device to send data can be based on the DRB configuration in the last connection or the default DRB configuration. If the DRB configuration of the last connection is used, if the access network device does not support the configuration, the terminal device will be reconfigured, such as through an RRC reconfiguration message or an RRC connection recovery message.
[0418] Further, it may include:
[0419] S1640: The access network device sends a second request message to the MME.
[0420] Optionally, the content in the second request message may be the same as the content in the UE context resume request message (UE Context Resume Request).
[0421] Further, the second request message may be a UE context recovery request message.
[0422] After receiving message 3, the access network device verifies the terminal device according to the short Message Authentication Code for Integrity (short-MAC-I). If the access network device is not the original access network device, it is necessary to send the short-MAC-I to the source access network device through the X2 interface, and the source access network device will verify it. After the verification is successful, the source access network device sends the context information of the terminal device to the current access network device, and the current access network device performs subsequent operations.
[0423] Further, it may include:
[0424] S1650: The MME sends a second response message to the access network device according to the second request message.
[0425] Optionally, the content in the second response message may be the same as the content in the UE context resumption response message (UE Context Resume Response).
[0426] Furthermore, the second response message is a UE context recovery response message.
[0427] If the access network device finds that the radio access bearer (E-UTRAN Radio Access Bearer, E-RAB) corresponding to the data received by the access network device has been rejected according to the received second response message, the access network device will send an RRC connection recovery message or an RRC connection establishment message to the terminal device. The RRC connection recovery message or the RRC connection establishment message may include an indication message, which is used to indicate that the data E-RAB is rejected for transmission or the transmission fails or indicates that the terminal device needs to resend the previously sent data packet. At this time, the access network device allocates an additional ULgrant for the data transmission.
[0428] S1660: After receiving the second response message, the access network device sends the uplink data to the S-GW.
[0429] At this point, the S-GW can obtain the uplink data of the terminal device and realize early transmission of the uplink data.
[0430] Optionally, the method may further include:
[0431] S1670, after the access network device successfully sends the uplink data, it may send a UE context release request message, a UE context suspension request message, or a connection release request message to the MME;
[0432] S1680, the MME sends a UE context release message to the access network device according to the UE context release request message; or the MME sends a UE context suspension completion message to the access network device according to the UE context suspension request message; or the MME sends a UE context release message to the access network device according to the connection release request.
[0433] S1690, the access network device sends candidate message #4 to the terminal device based on.
[0434] Optionally, candidate message #4 may be message 4, such as an RRC connection establishment message, an RRC connection reestablishment message, an RRC connection recovery message, or an RRC connection release message.
[0435] In addition, candidate message #4 may also be the first RRC message sent by the newly defined access network device to the terminal device, which is not limited to this in the embodiments of the present application.
[0436] It should be understood that candidate message #4 may be the same as or different from candidate message #3, and this embodiment of the present application does not limit this.
[0437] Optionally, candidate message #4 may carry an indication message (for example, recorded as indication message #5). Indication message #5 is used to indicate that the current process or session process can be ended, or to indicate that the terminal device needs to return to or maintain an idle state. Indication message #5 may be expressed as a stop indication (End Indication).
[0438] It should be understood that indication information #5 may be the same as indication information #2 or may be different, and this embodiment of the present application does not limit this.
[0439] In this way, by indicating information #5 in candidate message #4, the terminal device can be released in advance when the S-GW has no downlink data transmission. Compared with the release process of the prior art, it can save signaling overhead and, on the other hand, reduce the power consumption of the terminal device.
[0440] Furthermore, if candidate message #4 is an RRC connection establishment message, an RRC connection re-establishment message, or an RRC connection recovery message, candidate message #4 may also include a redirection indication, etc.
[0441] Optionally, candidate message #4 may carry downlink data.
[0442] If the downlink data has reached the access network device, but the access network device cannot send the downlink data to the terminal device, it is transmitted using several methods similar to S1560, such as establishing an RRC connection and placing an empty NAS message or an indication information in message 5, and then using the normal data transmission process.
[0443] Therefore, according to the data transmission method of the embodiment of the present application, the transmission of uplink data can be achieved based on the first RRC signaling sent by the terminal device to the access network device without establishing an RRC connection, thereby saving power consumption and signaling overhead.
[0444] Fig.17 is a schematic flowchart of a data transmission method according to another embodiment of the present application. Fig.17 The method shown is applicable to early transmission of downlink data based on the CP solution.
[0445] S1710, the terminal device sends message 1 to the access network device.
[0446] S1720, after receiving message 1, the access network device sends message 2 to the terminal device.
[0447] S1730, the terminal device sends a message 3 to the access network device, and the message 3 may include a service request message (Service Request Message).
[0448] Message 3 is similar to the above-mentioned embodiment, and may be an existing RRC signaling or a newly defined RRC signaling.
[0449] The indication information in message 3 (for example, recorded as indication information #6) can be used to indicate to the terminal device that early transmission of downlink data is to be performed, that is, to transmit downlink data based on the first RRC signaling sent by the access network device to the terminal device. After receiving the indication information #6, the access network device can trigger the signaling interaction with the core network device earlier.
[0450] S1740, after receiving message 3, the access network device sends a request message to the MME.
[0451] The request message may be a message for obtaining UE information or an initial UE message, or other newly defined messages, which is not limited in the embodiments of the present application.
[0452] S1750, after receiving the request message, the MME sends the downlink data to the access network device.
[0453] Optionally, the MME may send the downlink data to the access network device via a UE Information Transfer Message or a Downlink NAS Transport Message.
[0454] S1760, the access network device sends the downlink data to the terminal device through message 4.
[0455] Furthermore, message 4 is also used to instruct the terminal device to remain in the idle state or return to the idle state, and the terminal device returns to the idle state or remains in the idle state according to message 4.
[0456] Therefore, according to the data transmission method of the embodiment of the present application, downlink data can be transmitted through message 4, that is, early transmission of downlink data is achieved, thereby saving power consumption and signaling overhead.
[0457] Fig.18 is a schematic flowchart of a data transmission method according to another embodiment of the present application. Fig.18 The method shown is applicable to early transmission of downlink data based on the UP solution.
[0458] S1810, the terminal device sends message 1 to the access network device.
[0459] S1820, after receiving message 1, the access network device sends message 2 to the terminal device.
[0460] S1830: The terminal device sends a message 3 to the access network device according to the message 2. The message 3 may include a service request message (Service Request Message).
[0461] S1840, after receiving the service request message in message 3, the access network device sends the service request message to the MME.
[0462] Optionally, the access network device may send the service request message to the MME via a terminal device context recovery request message.
[0463] S1850, the MME sends a service response message to the access network device according to the service request message.
[0464] Optionally, the MME may send a terminal device context recovery response message after receiving the terminal device context recovery request message sent by the access network device.
[0465] S1860, MME sends a modify bearer request message to S-GW.
[0466] S1870, the S-GW replies a modify bearer response message to the MME, so that the S-GW can obtain the address of the access network device.
[0467] S1880, S-GW sends the downlink data to the access network device.
[0468] S1890, the access network device sends the downlink data to the terminal device through message 4.
[0469] Optionally, before S1890, after the access network device receives the downlink data sent by the S-GW, the method may further include:
[0470] The access network device sends a UE context release request message, a UE context suspension request message, a connection release request message, or other release request messages to the MME;
[0471] The MME sends a UE context release command message to the access network device according to the UE context release request message; or the MME sends a UE context suspension completion message to the access network device according to the UE context suspension request message; or the MME sends a UE context release message to the access network device according to the release connection request;
[0472] The access network device sends candidate message #5 to the terminal device according to the UE context release command message and the UE context suspension completion message.
[0473] Alternatively, candidate message #5 may be message 4.
[0474] Message 4, for example, is an RRC connection establishment message, an RRC connection re-establishment message, an RRC connection recovery message or an RRC connection release message.
[0475] In addition, candidate message #5 may also be the first RRC message sent by the newly defined access network device to the terminal device, which is not limited to this in the embodiments of the present application.
[0476] It should be understood that candidate message #5 may be the same as or different from candidate message #3, and this embodiment of the present application does not limit this.
[0477] Optionally, candidate message #5 may carry an indication message (for example, recorded as indication message #6). Indication message #5 is used to indicate that the current process or session process can be ended, or to indicate that the terminal device needs to return to or maintain an idle state. Indication message #6 may be expressed as a stop indication (End Indication).
[0478] It should be understood that indication information #6 may be the same as indication information #2 or may be different, and this embodiment of the present application does not limit this.
[0479] In this way, by indicating information #6 in candidate message #5, the terminal device can be released in advance when the S-GW has no downlink data transmission. Compared with the release process of the prior art, it can save signaling overhead and, on the other hand, reduce the power consumption of the terminal device.
[0480] Furthermore, if the candidate message #5 is an RRC connection establishment message, an RRC connection reestablishment message or an RRC connection recovery message, the candidate message #5 may also include relevant information in the RRC connection release message, such as a release reason, a redirection indication and the like.
[0481] If candidate message #5 is an RRC connection rejection message, candidate message #5 may also carry a cause value, which indicates the reason for the RRC connection rejection.
[0482] If the candidate message #5 is an RRC connection release message, it indicates that the terminal returns to or remains in an idle state. The candidate message #5 may carry the identification information of the terminal device, which may be carried in the MAC CE or scrambled through the PDCCH.
[0483] Optionally, in S1890, the access network device may send the downlink data to the terminal device via candidate message #5.
[0484] Therefore, according to the data transmission method of the embodiment of the present application, the transmission of uplink data can be achieved based on the first RRC signaling sent by the terminal device to the access network device without establishing an RRC connection, thereby saving power consumption and signaling overhead.
[0485] Optionally, in a possible implementation, when a terminal device receives a paging message, the paging message may include an indication information, indicating that the access network device needs to perform a downlink data early transmission operation, so that the terminal device can perform subsequent processes according to the downlink data early transmission operation. Further, the core network device may carry an indication information in the paging message sent to the access network device, indicating that the access network device needs to perform downlink data early transmission. Before the access network device sends a paging message to the terminal, the access network device receives a downlink packet and / or indication information from the core network. The indication information is used to indicate that a downlink data packet can be sent to the terminal by means of data early transmission (such as downlink data early transmission).
[0486] Optionally, when the terminal device is in a connected state, the access network device may also send an indication to the terminal device through PDCCH to indicate that the UE needs to perform random access for early data transmission, such as early uplink data transmission or early downlink data transmission. That is, random access is performed in a PDCCH order manner. The specific indication information may be carried by DCI, or the resource location indicated by the access network device for UE access is a resource location for early data transmission to achieve early data transmission. In this way, in the connected state, the access network device may instruct the UE to use the early data transmission method through PDCCH.
[0487] Fig.19 FIG. 1 is a schematic block diagram of a terminal device 1900 according to an embodiment of the present application. Fig.19As shown, the terminal device 1900 includes: a processing unit 1910 and a transceiver unit 1920.
[0488] The processing unit 1910 is configured to generate a first indication, wherein the first indication is used to instruct the terminal device to transmit data based on a first radio resource control RRC signaling sent by the terminal device to the access network device, and / or,
[0489] The first indication is used to instruct the access network device to transmit data based on the first radio resource control RRC signaling sent by the access network device to the terminal device.
[0490] The transceiver unit 1920 is used to send the first indication generated by the processing unit to the access network device, and to transmit data between the terminal device and the access network device based on the first RRC signaling.
[0491] It should be understood that the processing unit 1910 may be implemented by a processor, and the transceiver unit 1920 may be implemented by a transceiver.
[0492] It should also be understood that the terminal device 1900 may correspond to the terminal device described in the above method, and each module or unit in the terminal device 1900 is respectively used to execute Figures 10 to 18 The detailed description of each action or processing process performed by the terminal device in the method embodiment is omitted here to avoid redundancy.
[0493] Fig. 20 FIG. 2 shows a schematic block diagram of an access network device 2000 according to an embodiment of the present application. Fig. 20 As shown, the access network device 2000 includes: a processing unit 2010 and a transceiver unit 2020.
[0494] The processing unit 2010 is used to control the transceiver unit 2020:
[0495] receiving a first indication sent by a terminal device, where the first indication is used to instruct the terminal device to transmit data based on a first radio resource control RRC signaling sent by the terminal device to the access network device, and / or,
[0496] The first indication is used to instruct the access network device to transmit data based on a first radio resource control RRC signaling sent by the access network device to the terminal device; and
[0497] Based on the first RRC signaling, data is transmitted between the access network device and the terminal device.
[0498] It should be understood that the processing unit 2010 can be implemented by a processor, and the transceiver unit 2020 can be implemented by a transceiver.
[0499] It should also be understood that the access network device 2000 may correspond to the access network device described in the above method, and each module or unit in the access network device 2000 is respectively used to execute Figures 10 to 18 The detailed description of each action or processing process performed by the access network device in the method embodiment is omitted here to avoid redundancy.
[0500] The embodiments of the present application can be applied to a processor or implemented by a processor. The processor can be an integrated circuit chip with signal processing capabilities. In the implementation process, each step of the above method embodiment can be completed by an integrated logic circuit of hardware in the processor or an instruction in the form of software. The above processor can be a central processing unit (CPU), the processor can also be other general-purpose processors, digital signal processors (DSP), application specific integrated circuits (ASIC), field programmable gate arrays (FPGA) or other programmable logic devices, discrete gates or transistor logic devices, discrete hardware components. The methods, steps and logic block diagrams disclosed in the embodiments of the present application can be implemented or executed. The general processor can be a microprocessor or the processor can also be any conventional processor. The steps of the method disclosed in the embodiments of the present application can be directly embodied as a hardware decoding processor to execute, or a combination of hardware and software in the decoding processor to execute. The software can be located in a mature storage medium in the field 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. The storage medium is located in the memory, and the processor reads the information in the memory and completes the steps of the above method in combination with its hardware.
[0501] It should also be understood that the memory in the embodiments of the present application may be a volatile memory or a non-volatile memory, or may include both volatile and non-volatile memories. Among them, the non-volatile memory may be a read-only memory (ROM), a programmable read-only memory (PROM), an erasable programmable read-only memory (EPROM), an electrically erasable programmable read-only memory (EEPROM), or a flash memory. The volatile memory may be a random access memory (RAM), which is used as an external cache. By way of example and not limitation, many forms of RAM are available, such as static RAM (SRAM), dynamic RAM (DRAM), synchronous DRAM (SDRAM), double data rate SDRAM (DDR SDRAM), enhanced SDRAM (ESDRAM), synchronous link DRAM (SLDRAM), and direct RAM bus RAM (DRRAM). 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.
[0502] It should be understood that the term "and / or" in this article is only a description of the association relationship of the associated objects, indicating that there can be three relationships. For example, A and / or B can represent: A exists alone, A and B exist at the same time, and B exists alone. In addition, the character " / " in this article generally indicates that the associated objects before and after are in an "or" relationship.
[0503] It should be understood that in the various embodiments of the present application, the size of the serial numbers of the above-mentioned processes does not mean the order of execution. The execution order of each process should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of the embodiments of the present application.
[0504] Those of ordinary skill in the art will appreciate that the units and algorithm steps of each example described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are performed in hardware or software depends on the specific application and design constraints of the technical solution. Professional and technical personnel can use different methods to implement the described functions for each specific application, but such implementation should not be considered to be beyond the scope of this application.
[0505] Those skilled in the art can clearly understand that, for the convenience and brevity of description, the specific working processes of the systems, devices and units described above can refer to the corresponding processes in the aforementioned method embodiments and will not be repeated here.
[0506] In the 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 only schematic. For example, the division of the units is only a logical function division. There may be other division methods in actual implementation, such as multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. Another point is that the mutual coupling or direct coupling or communication connection shown or discussed can be through some interfaces, indirect coupling or communication connection of devices or units, which can be electrical, mechanical or other forms.
[0507] The units described as separate components may or may not be physically separated, and the components shown as units may or may not be physical units, that is, they may be located in one place or distributed on multiple network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution of this embodiment.
[0508] In addition, each functional unit in each embodiment of the present application may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit.
[0509] If the functions are implemented in the form of software functional units and sold or used as independent products, they can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the present application can be essentially or partly embodied in the form of a software product that contributes to the prior art. The computer software product is stored in a storage medium and includes several instructions for a computer device (which can be a personal computer, a server, or a network device, etc.) to perform all or part of the steps of the methods described in the various embodiments of the present application. The aforementioned storage media include: various media that can store program codes, such as USB flash drives, mobile hard disks, read-only memories (ROM), random access memories (RAM), magnetic disks or optical disks.
[0510] The above is only a specific implementation of the present application, but the protection scope of the present application is not limited thereto. Any person skilled in the art who is familiar with the present technical field can easily think of changes or substitutions within the technical scope disclosed in the present application, which should be included in the protection scope of the present application. Therefore, the protection scope of the present application should be based on the protection scope of the claims.
Claims
1. A data transmission method, characterized in that: include: The terminal device receives the system message; The terminal device determines, according to the system message, that the access network device supports the data early transmission function; The terminal device sends a first indication to the access network device, where the first indication is used to indicate that early data transmission is required; The terminal device and the access network device perform early data transmission, If the first indication is a first random access preamble code, the first indication is used to indicate early transmission of uplink data, and the early transmission of data between the terminal device and the access network device includes: The terminal device performs uplink data early transmission based on a first radio resource control RRC signaling after the first indication, wherein the first RRC signaling is message 3Msg 3; If the first indication is Msg 3 including a service request message, the first indication is used to indicate early transmission of downlink data, and the early transmission of data between the terminal device and the access network device includes: The terminal device receives message 4 Msg 4, where the Msg 4 carries downlink data and is further used to instruct the terminal device to remain in an idle state or return to an idle state. The method further includes: The terminal device remains in an idle state or returns to an idle state based on the message 4; The method further comprises: The terminal device and the access network device transmit data via a data radio bearer DRB, and the data transmitted via the data radio bearer DRB is encrypted using a key updated by a next hop calculation (NCC) obtained through the last connection.
2. The method according to claim 1, characterized in that: The terminal device sending the first indication information to the access network device includes: The terminal device uses the first time-frequency code resource or the second time-frequency code resource to send a random access request message to the access network device, wherein the first time-frequency code resource is used to indicate early transmission of uplink data, and the second time-frequency code resource is used to indicate early transmission of downlink data.
3. The method according to claim 1 or 2, characterized in that: The early transmission of data between the terminal device and the access network device includes: The terminal device and the access network device transmit a non-access layer protocol data unit NAS PDU; or, Data is transmitted between the terminal device and the access network device via a data radio bearer DRB.
4. The method according to claim 1 or 2, characterized in that: The method further comprises: The terminal device receives an RRC connection release message from the access network device, and the RRC connection release message is used to release the terminal device to an idle state.
5. The method according to claim 1 or 2, characterized in that: The method also includes: the terminal device receiving an RRC connection release message from the access network device, and the RRC connection release message carries data that needs to be transmitted.
6. A data transmission method, characterized in that: include: The access network device sends a system message to the terminal device; The access network device receives a first indication from the terminal device, where the first indication is used to indicate that early data transmission is required; The access network device and the terminal device perform early data transmission, If the first indication is a first random access preamble code, the first indication is used to indicate early transmission of uplink data, and the early transmission of data between the terminal device and the access network device includes: The access network device receives a first radio resource control RRC signaling after the first indication, where the first RRC signaling carries uplink data, wherein the first RRC signaling is message 3Msg 3; If the first indication is Msg 3 including a service request message, the first indication is used to indicate early transmission of downlink data, and the early transmission of data between the terminal device and the access network device includes: The access network device sends a message 4 Msg 4, wherein the Msg 4 carries downlink data and is also used to instruct the terminal device to remain in the idle state or return to the idle state. The method further comprises: The terminal device and the access network device transmit data via a data radio bearer DRB, and the data transmitted via the data radio bearer DRB is encrypted using a key updated by a next hop calculation (NCC) obtained through the last connection.
7. The method according to claim 6, characterized in that The access network device receiving a first indication sent by a terminal device includes: The access network device receives a random access request message from the terminal device, where the random access request message is sent by the terminal device using a first time-frequency code resource or a second time-frequency code resource, wherein the first time-frequency code resource is used to indicate early transmission of uplink data, and the second time-frequency code resource is used to indicate early transmission of downlink data.
8. The method according to claim 6 or 7, characterized in that: The data transmission between the access network device and the terminal device includes: The access network device transmits a non-access layer protocol data unit NAS PDU to the terminal device before the RRC connection is established; or Before the RRC connection is established, the access network device transmits data with the terminal device via a data radio bearer DRB.
9. The method according to claim 6 or 7, characterized in that: The method further comprises: The access network device sends an RRC connection release message to the terminal device, and the RRC connection release message is used to release the terminal device to an idle state.
10. The method according to claim 6 or 7, characterized in that: The method further comprises: The access network device sends an RRC connection release message to the terminal device, and the RRC connection release message carries data that needs to be transmitted.
11. A communication device, characterized in that: Comprising means for performing the method as claimed in any one of claims 1 to 5 or 6 to 10.
12. A communication device, characterized in that: It includes a processor and a communication interface, wherein the communication interface is used to receive signals from other communication devices outside the communication device and transmit them to the processor or send signals from the processor to other communication devices outside the communication device, and the processor is used to implement the method as described in any one of claims 1 to 5 or 6 to 10 through logic circuits or execution code instructions.
13. A computer-readable storage medium, characterized in that: The computer-readable storage medium stores a computer program, and when the computer program is executed, the method according to any one of claims 1 to 5 or 6 to 10 is implemented.
14. A computer program product, the computer program product comprising: Computer program code, when the computer program code is executed, implements the method according to any one of claims 1 to 5 or 6 to 10.
