WO2018201621A1 - 数据传输的方法、终端设备和接入网设备 - Google Patents

数据传输的方法、终端设备和接入网设备 Download PDF

Info

Publication number
WO2018201621A1
WO2018201621A1 PCT/CN2017/093440 CN2017093440W WO2018201621A1 WO 2018201621 A1 WO2018201621 A1 WO 2018201621A1 CN 2017093440 W CN2017093440 W CN 2017093440W WO 2018201621 A1 WO2018201621 A1 WO 2018201621A1
Authority
WO
WIPO (PCT)
Prior art keywords
message
terminal device
access network
network device
data
Prior art date
Application number
PCT/CN2017/093440
Other languages
English (en)
French (fr)
Inventor
李晨琬
单宝堃
于映辉
王燕
罗林杰⋅奥黛尔
吉尔里⋅斯图尔特
黄正磊
王宏
Original Assignee
华为技术有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 华为技术有限公司 filed Critical 华为技术有限公司
Priority to JP2019560716A priority Critical patent/JP7088603B2/ja
Priority to CN202210868993.9A priority patent/CN115442775A/zh
Priority to BR112019023178A priority patent/BR112019023178A2/pt
Priority to EP17908302.7A priority patent/EP3611947A4/en
Priority to KR1020197035463A priority patent/KR102390889B1/ko
Priority to CN201780090235.6A priority patent/CN110603829A/zh
Publication of WO2018201621A1 publication Critical patent/WO2018201621A1/zh
Priority to US16/674,663 priority patent/US11140676B2/en
Priority to US17/477,207 priority patent/US11606786B2/en

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/04—Wireless resource allocation
    • H04W72/044—Wireless resource allocation based on the type of the allocated resource
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/70—Services for machine-to-machine communication [M2M] or machine type communication [MTC]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L9/00—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols
    • H04L9/08—Key distribution or management, e.g. generation, sharing or updating, of cryptographic keys or passwords
    • H04L9/0891—Revocation or update of secret information, e.g. encryption key update or rekeying
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/50—Allocation or scheduling criteria for wireless resources
    • H04W72/51—Allocation or scheduling criteria for wireless resources based on terminal or device properties
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W74/00—Wireless channel access
    • H04W74/002—Transmission of channel access control information
    • H04W74/004—Transmission of channel access control information in the uplink, i.e. towards network
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/10—Connection setup
    • H04W76/18—Management of setup rejection or failure
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W8/00—Network data management
    • H04W8/22—Processing or transfer of terminal data, e.g. status or physical capabilities
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W8/00—Network data management
    • H04W8/22—Processing or transfer of terminal data, e.g. status or physical capabilities
    • H04W8/24—Transfer of terminal data
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/01—Protocols
    • H04L67/12—Protocols specially adapted for proprietary or special-purpose networking environments, e.g. medical networks, sensor networks, networks in vehicles or remote metering networks
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W12/00—Security arrangements; Authentication; Protecting privacy or anonymity
    • H04W12/03—Protecting confidentiality, e.g. by encryption
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W12/00—Security arrangements; Authentication; Protecting privacy or anonymity
    • H04W12/10—Integrity
    • H04W12/106—Packet or message integrity
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W74/00—Wireless channel access
    • H04W74/08—Non-scheduled access, e.g. ALOHA
    • H04W74/0833—Random access procedures, e.g. with 4-step access
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/10—Connection setup
    • H04W76/19—Connection re-establishment
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/20—Manipulation of established connections
    • H04W76/27—Transitions between radio resource control [RRC] states
    • Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
    • Y02—TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
    • Y02D—CLIMATE CHANGE MITIGATION TECHNOLOGIES IN INFORMATION AND COMMUNICATION TECHNOLOGIES [ICT], I.E. INFORMATION AND COMMUNICATION TECHNOLOGIES AIMING AT THE REDUCTION OF THEIR OWN ENERGY USE
    • Y02D30/00—Reducing energy consumption in communication networks
    • Y02D30/70—Reducing energy consumption in communication networks in wireless communication networks

Definitions

  • the present application relates to the field of Internet of Things, and more particularly to a method, a terminal device and an access network device for data transmission.
  • IoT Internet of Thing
  • M2M Machine To Machine
  • MTC Machine Type Communications
  • a typical cellular Internet of Things system is the Narrowband IOT (NB-IoT).
  • NB-IoT Narrowband IOT
  • at least the uplink and downlink data transmission can be performed when the RRC connection is established, which causes the problem of excessive signaling overhead and wasted power consumption, which is disadvantageous for service transmission in the NB-IoT scenario. Therefore, a new data transmission method is needed, which can be applied to service transmission in an NB-IoT scenario.
  • the present application provides a data transmission method, a terminal, and an access network device, which can transmit data before the radio resource control (RRC) connection establishment is completed, and further, can save the required bearer for transmitting data. Signaling overhead and can reduce device power consumption.
  • RRC radio resource control
  • the first aspect relates to a data transmission method, the method includes: the terminal device sends a first indication to the access network device, where the first indication is used to indicate that data needs to be transmitted before the RRC connection establishment is completed; The terminal device transmits data to and from the access network device before the establishment of the RRC connection is completed.
  • data (including uplink data and downlink data) can be transmitted before the RRC establishment is completed according to the first indication, thereby saving signaling overhead for establishing a required bearer for transmitting data, and can reduce Device power consumption.
  • the terminal device when the first indication is a random access preamble, the terminal device sends the first indication to the access network device, where the terminal device sends the first random to the access network device. Access the preamble.
  • the access network device can determine, according to the first random access preamble, that data needs to be needed before the RRC connection establishment is completed, for example, it can be determined that the terminal device needs to perform uplink data early transmission, or can determine that the terminal device performs downlink data early transmission.
  • the terminal device sends the first indication to the access network device, where the terminal sends the random access request message by using the first time-frequency code resource or the second time-frequency code resource.
  • the first time-frequency code resource may be used to indicate that the uplink data is transmitted early, and the second time-frequency code resource may be used to indicate that the downlink data is transmitted early.
  • the terminal device sends the first indication to the access network device, where the terminal device sends a random access preamble to the access network device on the first random access resource.
  • the access network device can determine, according to the first random access resource, that data needs to be needed before the RRC connection establishment is completed, for example, it can be determined that the terminal device needs to perform uplink data early transmission, or can determine that the terminal device performs downlink data early transmission.
  • the terminal device sends the first indication to the access network device, where the terminal device sends a message 3 including the first indication to the access network device, where the message 3 is as follows A message:
  • the RRC Connection Request message The RRC Connection Request message, the RRC Connection Re-establishment Request message, and the RRC Connection Recovery Request.
  • the first indication is used to indicate that data needs to be transmitted before the RRC connection establishment is completed, including:
  • the first indication is used to indicate that downlink data needs to be transmitted before the establishment of the RRC connection is completed.
  • the terminal device transmits data to the access network device before the establishment of the RRC connection, including:
  • the terminal device transmits a Non-Access-Stratiction Protocol Data Unit (NASPDU) to the access network device before the establishment of the RRC connection is completed; or
  • NNASPDU Non-Access-Stratiction Protocol Data Unit
  • the terminal device transmits data to the access network device through a Data Radio Bearer (DRB) before the establishment of the RRC connection is completed.
  • DRB Data Radio Bearer
  • the method further includes: receiving, by the terminal device, a release message sent by the access network device, where the release message is a radio resource control RRC connection setup message, an RRC connection recovery message, and the RRC connection re-establishment is completed.
  • the release message is used to release the terminal device to an idle state.
  • the release message may carry data that needs to be transmitted.
  • the release message is an RRC connection setup message or an RRC connection re-establishment message, and the RRC connection is re-established
  • the message may include related information in the RRC connection release, and the connection may be released, specifically including a release reason. Redirection instructions, etc.
  • the indication information may be carried, such as a cause value, for indicating that the terminal device is released to the idle state;
  • release message is an RRC connection release message and carries the identification information of the terminal device
  • a RRC message may also be added with a Media Control Control (MAC CE) carrying the identifier, and the terminal device is directly released. To the idle state.
  • MAC CE Media Control Control
  • the RRC connection setup message, the RRC connection re-establishment message, the RRC connection re-establishment, or the RRC connection reject message can release the terminal device in advance when the MME has no downlink data transmission, which can save signaling overhead compared to the release process of the prior art. On the other hand, it is also possible to reduce the power consumption of the terminal device.
  • the second aspect provides a data transmission method, including: receiving, by the access network device, a first indication sent by the terminal device, where the first indication is used to indicate that data needs to be transmitted before the RRC connection establishment is completed; the access The network device transmits data to and from the terminal device before the establishment of the RRC connection is completed.
  • data (including uplink data and downlink data) can be transmitted before the RRC establishment is completed according to the first indication, thereby saving signaling overhead for establishing a required bearer for transmitting data, and can reduce Device power consumption.
  • the access network device when the first indication is a random access preamble, the access network device receives the first indication sent by the terminal device, where the access network device receives the A random access preamble.
  • the access network device can determine, according to the first random access preamble, that data needs to be needed before the RRC connection establishment is completed, for example, it can be determined that the terminal device needs to perform uplink data early transmission, or can determine that the terminal device performs downlink data early transmission.
  • the access network device receives the first indication sent by the terminal device, where the access network device receives the random access preamble sent by the terminal device in the first random access resource.
  • the access network device can determine, according to the first random access resource, that data needs to be needed before the RRC connection establishment is completed, for example, it can be determined that the terminal device needs to perform uplink data early transmission, or can determine that the terminal device performs downlink data early transmission.
  • the access network device receives the first indication sent by the terminal device, where the access network device receives the message 3 that is sent by the terminal device and includes the first indication, where the message 3 is as follows. Any kind of message:
  • the RRC Connection Request message The RRC Connection Request message, the RRC Connection Re-establishment Request message, and the RRC Connection Recovery Request.
  • the first indication is used to indicate that data needs to be transmitted before the RRC connection establishment is completed, and the first indication is used to indicate that downlink data needs to be transmitted before the RRC connection establishment is completed.
  • the access network device transmits data to the terminal device before the establishment of the RRC connection, including: the access network device, before the RRC connection establishment is completed, and the terminal device Non-access stratum protocol data unit NAS PDU is transmitted between; or
  • the access network device transmits data to the terminal device through the data radio bearer DRB before the establishment of the RRC connection is completed.
  • the method further includes: the access network device sending the NAS PDU to a core network device.
  • the method further includes: the access network device sends a release message to the terminal device, where the release message is a radio resource control RRC connection setup message, an RRC connection recovery message, and an RRC connection reestablishment complete message. And an RRC connection reject message or an RRC connection release message, the release message is used to release the terminal device to an idle state.
  • the release message is a radio resource control RRC connection setup message, an RRC connection recovery message, and an RRC connection reestablishment complete message.
  • an RRC connection reject message or an RRC connection release message the release message is used to release the terminal device to an idle state.
  • the release message may carry data that needs to be transmitted.
  • the release message is an RRC connection setup message or an RRC connection re-establishment message, and the RRC connection is re-established
  • the message may include related information in the RRC connection release, and the connection may be released, specifically including a release reason. Redirection instructions, etc.
  • the indication information may be carried, such as a cause value, for indicating that the terminal device is released to the idle state;
  • the release message is an RRC connection release message and carries the user equipment identification information
  • the MAC CE that carries the identifier may be added to the RRC message, and the terminal device is directly released to the idle state.
  • the RRC connection setup message, the RRC connection re-establishment message, the RRC connection re-establishment, or the RRC connection reject message can release the terminal device in advance when the MME has no downlink data transmission, which can save signaling overhead compared to the release process of the prior art. On the other hand, it is also possible to reduce the power consumption of the terminal device.
  • a terminal device for performing the method of the first aspect or any possible implementation of the first aspect.
  • the terminal device comprises means for performing the method of the first aspect or any of the possible implementations of the first aspect.
  • an access network device for performing the method in any of the possible implementations of the second aspect or the second aspect.
  • the access network device comprises means for performing the method of any of the possible implementations of the second aspect or the second aspect.
  • a terminal device including a receiver, a transmitter, a processor, and a storage And bus system.
  • the receiver, the transmitter, the processor and the memory are connected by a bus system, the memory is used for storing instructions, and the processor is configured to execute instructions stored in the memory to control the receiver to receive signals and control the transmitter to send signals.
  • the processor executes the instructions stored in the memory, the method of causing the processor to perform the first aspect or any of the possible implementations of the first aspect is performed.
  • an 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 by a bus system, the memory is used for storing instructions, and the processor is configured to execute instructions stored in the memory to control the receiver to receive signals and control the transmitter to send signals.
  • the processor executes the instructions stored in the memory, the method of causing the processor to perform the second aspect or any of the possible implementations of the second aspect is performed.
  • the application provides a computer readable medium for storing a computer program, the computer program comprising instructions for performing the method of the first aspect or any of the possible implementations of the first aspect.
  • a computer readable medium for storing a computer program comprising instructions for performing the method of the second aspect or any of the possible implementations of the second aspect.
  • a data transmission method includes: the terminal device sends a first indication to the access network device, where the first indication is used to indicate that the terminal device sends the first message to the access network device based on the terminal device Radio resource control RRC signaling transmission data, and/or,
  • the first indication is used to indicate, by the access network device, the first radio resource control RRC signaling transmission data that is sent by the access network device to the terminal device;
  • data is transmitted between the terminal device and the access network device.
  • the first indication is used to indicate that the terminal device and the access network device carry data by using the first signaling that is transmitted, or transmit data while transmitting the first signaling, or after transmitting the first signaling. Then transfer the data.
  • the first signaling is a first RRC signaling between the terminal device and the access network device in the random access process. That is, the first indication is used to indicate that the terminal device will transmit uplink data based on the first RRC signaling with the access network device, and/or the first indication is used to indicate that the access network device is to be based on the terminal The first RRC signaling between the devices transmits downlink data.
  • uplink and/or downlink data transmission can be implemented based on the first RRC signaling between the terminal device and the access network device, without establishing an RRC connection, thereby saving transmission
  • the data establishes the signaling overhead of the required bearers and can reduce the power consumption of the device.
  • the data is transmitted between the terminal device and the access network device based on the first RRC signaling, including:
  • Data is carried by the first RRC signaling, and data is transmitted between the terminal device and the access network device.
  • the data is transmitted between the terminal device and the access network device, including:
  • the terminal device and the access network device transmit data through the data radio bearer DRB.
  • the data may be sent via DRB or SRB0.
  • the data and the first RRC signaling may be multiplexed with one transport block, or may be separately transmitted as two transport blocks.
  • the first RRC signaling may carry the identifier of the terminal device.
  • the data may carry the identifier of the terminal device or be scrambled by the identifier of the terminal device.
  • the identifier of the terminal device may be, for example, a Radio Network Temporary Identifier (RNTI), a Hash Service Temporary Mobile Subscriber Identity (hash S-TMSI), an S-TMSI, and a truncated S-TMSI.
  • RNTI Radio Network Temporary Identifier
  • Hash S-TMSI Hash Service Temporary Mobile Subscriber Identity
  • S-TMSI Hash Service Temporary Mobile Subscriber Identity
  • S-TMSI truncated S-TMSI
  • the access random number, the International Mobile Subscriber Identification Number (IMSI), and the identifier of the terminal device carried in the MAC CE, etc., are not specifically limited in this application.
  • the NAS PDU carrying the data can be sent through SRB 1bis or SRB0, or the first RRC signaling is sent through SRB 0 and the data is sent through the DRB. .
  • the first RRC signaling is message 3 or message 4.
  • message 3 is any of the following messages:
  • RRC Connection Request message RRC Connection Re-establishment Request message, and RRC Connection Recovery Request message;
  • Message 4 is any of the following messages:
  • the conflict resolution message the RRC connection setup message, the RRC connection re-establishment message, and the RRC connection recovery message.
  • the terminal device when the first indication is a random access preamble, the terminal device sends the first indication to the access network device, including:
  • the terminal device sends the first random access preamble to the access network device.
  • the terminal device sends the first indication to the access network device, including:
  • the terminal device sends a random access preamble to the access network device on the first random access resource.
  • the method before the data is transmitted between the terminal device and the access network device based on the first RRC signaling, the method further includes:
  • the terminal device receives a system message, where the system message includes data volume information, where the data volume information is used to indicate a maximum amount of data that the terminal device can transmit based on the first RRC signaling;
  • the transmitting, by the terminal device, the data between the terminal device and the access network device, based on the first RRC signaling, includes:
  • the terminal device determines that the data volume of the data is less than or equal to the maximum data amount, the terminal device transmits the data to the access network device based on the first RRC signaling.
  • the method may further include:
  • the terminal device receives the candidate message sent by the access network device, where the candidate message includes indication information, where the candidate message is an RRC connection setup message, an RRC connection recovery message, an RRC connection re-establishment complete message, an RRC connection reject message, or an RRC connection release message, the indication information It is used to indicate that the terminal device remains in the idle state.
  • the candidate message may be message 4.
  • the terminal device can be released in advance when there is no downlink data transmission, and the signaling overhead can be saved compared with the release process of the prior art. On the other hand, the power consumption of the terminal device can also be reduced. .
  • a data transmission method including:
  • the access network device receives the first indication sent by the terminal device, where the first indication is used to indicate that the terminal device transmits the data according to 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 indicate, by the access network device, the first radio resource control RRC signaling transmission data that is sent by the access network device to the terminal device;
  • data is transmitted between the access network device and the terminal device.
  • uplink and/or downlink data transmission can be implemented based on the first RRC signaling between the terminal device and the access network device, without establishing an RRC connection, thereby saving transmission
  • the data establishes the signaling overhead of the required bearers and can reduce the power consumption of the device.
  • the data is transmitted between the access network device and the terminal device, including:
  • the data is carried by the first RRC signaling, and the data is transmitted between the access network device and the terminal device.
  • the data is transmitted between the access network device and the terminal device, including:
  • the access network device and the terminal device transmit data through the non-access stratum protocol data unit NAS PDU; or
  • the data between the access network device and the terminal device is transmitted through the data radio bearer DRB.
  • the first RRC signaling is message 3 or message 4.
  • message 3 is any of the following messages:
  • RRC Connection Request message RRC Connection Re-establishment Request message, and RRC Connection Recovery Request message;
  • Message 4 is any of the following messages:
  • the conflict resolution message the RRC connection setup message, the RRC connection re-establishment message, and the RRC connection recovery message.
  • the access network device receives the first indication sent by the terminal device, including:
  • the access network device receives the first random access preamble sent by the terminal device.
  • the access network device receives the first indication sent by the terminal device, including:
  • the access network device receives a random access preamble sent by the terminal device in the first random access resource.
  • the method may further include:
  • the access network device sends a NAS PDU to the core network device.
  • the NAS PDU may be carried by acquiring a Retrieve UE Information Message or an Initial UE Message.
  • the method before the transmitting the data between the access network device and the terminal device based on the first RRC signaling, the method further includes: Receiving, by the network access device, the NAS PDU sent by the core network device;
  • the data transmission between the access network device and the terminal device based on the first RRC signaling includes: the access network device is located according to the first RRC signaling The terminal device transmits the NAS PDU.
  • the first RRC signaling is a UE Information Transfer Message or a Downlink NAS Transport Message.
  • the NAS PDU includes indication information, where the indication information is used to indicate that the access network device indicates that the terminal device is saved in an idle state.
  • the method may further include:
  • the access network device sends a candidate message to the terminal device, where the candidate message includes indication information, where the candidate message is an RRC connection setup message, an RRC connection recovery message, an RRC connection re-establishment complete message, an RRC connection reject message or an RRC connection release message, and the indication information is used by the Instructing the terminal device to remain in an idle state.
  • a terminal device for performing the method of any of the possible aspects of the ninth aspect or the ninth aspect.
  • the terminal device comprises means for performing the method of any of the possible aspects of the ninth aspect or the ninth aspect.
  • an access network device for performing any of the tenth or tenth aspects The method in the implementation.
  • the access network device comprises means for performing the method of any of the tenth or tenth aspects of the tenth aspect.
  • a thirteenth aspect a terminal device, a memory, a processor, and a transceiver, wherein the memory is used to store program code, and the processor is configured to execute program code stored in the memory to perform The operation corresponding to the method in the nine possible aspects or the various possible implementations of the ninth aspect.
  • an access network device comprising a memory, a processor, and a transceiver, the memory for storing program code, the processor for executing a program stored in the memory Code to perform the operations corresponding to the method of the tenth aspect or the various possible implementations of the tenth aspect.
  • the present application provides a computer readable medium for storing a computer program, the computer program comprising instructions for performing the method of any of the ninth or ninth aspect of the ninth aspect.
  • a sixteenth aspect a computer readable medium for storing a computer program, the computer program comprising instructions for performing the method of any of the tenth or tenth aspects of the tenth aspect.
  • FIG. 1 is a schematic diagram of a communication system that can be applied to the present application.
  • FIG. 2 is a schematic flowchart of a data transmission method according to an embodiment of the present application.
  • FIG. 3 is a schematic flowchart of a method for early transmission of uplink data according to the present application.
  • FIG. 4 is a schematic flowchart of a method for uplink data early transmission based on a CP scheme according to the present application.
  • FIG. 5 is a schematic flowchart of a method for uplink data uplink transmission based on an UP scheme according to the present application.
  • FIG. 6 is a schematic flowchart of a method for downlink data early transmission based on a CP scheme according to the present application.
  • FIG. 7 is a schematic flowchart of a method for downlink data early transmission based on an UP scheme according to the present application.
  • FIG. 8 is a schematic block diagram of a terminal device according to the present application.
  • FIG. 9 is a schematic block diagram of an access network device in accordance with the present application.
  • FIG. 10 is a schematic flowchart of a data transmission method according to another embodiment of the present application.
  • 11 is a schematic diagram of a format of Message 2.
  • Figure 13 is a schematic illustration of one format of Message 2.
  • FIG. 15 is a schematic flowchart of another method for uplink data uplink transmission based on the CP scheme according to the present application.
  • FIG. 16 is a schematic flowchart of another method for uplink data uplink transmission based on the UP scheme according to the present application.
  • FIG. 17 is a schematic flowchart of another method for downlink data early transmission based on the CP scheme according to the present application.
  • FIG. 18 is a schematic flowchart of another method for downlink data early transmission based on the UP scheme according to the present application.
  • 19 is a schematic block diagram of another terminal device in accordance with the present application.
  • 20 is a schematic block diagram of another access network device in accordance with the present application.
  • GSM Global System of Mobile communication
  • CDMA Code Division Multiple Access
  • WCDMA Wideband Code Division Multiple Access
  • GPRS General Packet Radio Service
  • LTE Long Term Evolution
  • LTE-A Advanced Long Term Evolution
  • Universal Mobile Telecommunication System Universal Mobile Telecommunication System
  • NR New Radio Access Technology
  • the terminal device may also be referred to as a terminal or a user equipment (User Equipment, UE), and may include, but is not limited to, a terminal device applied in the Internet of Things, for example, may be applied to the NB- Terminal devices in IoT (may be referred to as "NB-IoT terminals"): smart meter reading devices, logistics tracking devices, environmental monitoring devices, etc.; the terminals may also include, but are not limited to, mobile stations (MS), mobile terminals (Mobile Terminal), Mobile Telephone, User Equipment (UE), mobile phone (handset) and portable equipment (portable equipment), etc., the terminal equipment can pass through the Radio Access Network (RAN) Communicating with one or more core networks, for example, the terminal device may be a mobile phone (or "cellular" phone), a computer with wireless communication function, etc., and the terminal device may also be portable, pocket, handheld, computer Built-in or in-vehicle mobile device.
  • RAN Radio Access Network
  • the access network device may also be referred to as a Radio Access Network (RAN) device, and may be, for example, a base station, a base station controller, a Radio Network Controller (RNC), and a transmitting and receiving device.
  • RAN Radio Access Network
  • RNC Radio Network Controller
  • TRP Transmit and Receive Point
  • the base station may be a Base Transceiver Station (BTS) in GSM or CDMA, or a base station (NodeB) in WCDMA, or an evolved base station in LTE (evolved)
  • BTS Base Transceiver Station
  • NodeB base station
  • the Node B, eNB or e-NodeB may also be an NR or a 5G base station (gNB), which is not specifically limited in this embodiment of the present application.
  • gNB 5G base station
  • the embodiment of the invention further relates to a core network (CN) device, which mainly comprises a Mobility Management Entity (MME) and a Serving GateWay (S-GW).
  • MME Mobility Management Entity
  • S-GW Serving GateWay
  • the MME may have different names in different systems or networks of different standards.
  • MME Mobility Management Entity
  • S-GW Serving GateWay
  • the MME is uniformly described as an MME.
  • the S-GW may have different names in different systems or networks of different standards.
  • the S-GW is uniformly described as S-GW.
  • a terminal device can communicate with a core network device through one or more access network devices.
  • the terminal device 10a in FIG. 1 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.
  • PSTN Public Switched Telephone Network
  • PSTN Public Switched Telephone Network
  • the uplink and downlink data transmission can be performed when the RRC connection is established, which results in a late transmission of data, which causes a problem of excessive signaling overhead and wasted power consumption.
  • the present application proposes a data transmission method, which can realize early data transmission, thereby saving power consumption and signaling overhead.
  • Early data transmission can be understood as performing uplink and/or downlink data transmission before the RRC connection setup/recovery/re-establishment completion message.
  • Early data transmission can also be understood as uplink and/or downlink data transmission during random access.
  • the early data transmission can also be understood as the uplink and/or downlink data transmission by the terminal device through the first RRC signaling with the access network device.
  • the terminal device supports the data transmission method, and the terminal device To support this capability, the access network device supports the terminal device to use this method, indicating that the access network device supports the ability of such data to be transmitted early.
  • the access network device When the access network device sends a system message, it can perform an indication of whether or not to support such data early transmission.
  • the terminal device can determine, according to the received system message, whether the access network device supports the capability before random access. If not supported, the terminal device supporting the capability and the terminal device that wants to use the capability to transmit may choose not to access the access network device.
  • the system message may also indicate an upper limit or threshold of the data volume of the uplink data sent by the terminal device in the first RRC signaling message, or an upper limit or threshold of the data volume of the first RRC message and the uplink data, or
  • the first RRC signaling RRC message allows an upper limit or threshold of data volume of the uplink data to be transmitted, 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 data volume broadcast by the system, the terminal device may select to access the normal data transmission manner. If the amount of uplink data that the terminal device needs to send is less than the upper limit or the threshold of the data volume, the uplink data may be selected to transmit data.
  • the system message may be SIB2, SIB22 or other system message.
  • a default threshold may be specified in the protocol, where the threshold may indicate an upper limit of the data volume of the uplink data sent by the terminal device in the first RRC signaling message, or an upper limit of the data volume of the uplink RRC message and the uplink data. Or an upper limit of the amount of data allowed to be transmitted in addition to the first RRC signaling RRC message. If the terminal device finds that the data volume of the first RRC signaling and the uplink data exceeds the threshold, the terminal device may select 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 may be selected to be transmitted early.
  • the terminal device may select whether to use the early data transmission method to send data according to the amount of data to be sent or the type of service. If the terminal device selects the method of early data transmission, when the access network device allocates sufficient resources for transmitting data, the terminal device transmits data in the manner of early transmission. If the data resources allocated by the access network device are insufficient to transmit all the uplink data that the terminal device needs to send, the terminal device may select a normal data transmission process, that is, first establish an RRC connection, and then send data, such as in message 5 (for example, Data may be transmitted in an RRC Connection Complete message, an RRC Connection Reestablishment Complete message, or the like. Alternatively, the terminal device first sends a part of data on the resource of the access network device allocation message 3, and the remaining data may send data after the subsequent establishment of the RRC connection.
  • a normal data transmission process that is, first establish an RRC connection, and then send data, such as in message 5 (for example, Data may be transmitted in an RRC Connection Complete message, an RRC Connection Re
  • FIG. 2 illustrates detailed communication steps or operations of the method, but these steps or operations are merely examples, and embodiments of the present application may perform other operations or variations of the various operations in FIG. 2. Moreover, the various steps in FIG. 2 may be performed in a different order than that presented in FIG. 2, and it is possible that not all operations in FIG. 2 are to be performed.
  • FIG. 2 is a schematic flowchart of a method for data transmission according to an embodiment of the present application.
  • the terminal device sends a first indication to the access network device.
  • the access network device receives the first indication.
  • the first indication is used to indicate that data needs to be transmitted before the RRC connection establishment is completed. Therefore, the access network device can determine, according to the first indication, that data needs to be needed before the RRC connection establishment is completed, for example, can determine that the terminal device needs to perform uplink data early transmission, or can determine that the terminal device performs downlink data early transmission.
  • the uplink data early transmission indicates that uplink data needs to be transmitted before the RRC connection establishment is completed.
  • the downlink data early transmission indicates that downlink data needs to be transmitted before the RRC connection establishment is completed.
  • the message 1 is used to distinguish between the uplink data transmission and the downlink data transmission, and 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.
  • the data is transmitted early, so that a large uplink resource allocation (UL Grant) or multiple UL Grants are allocated when a random access response is sent to the terminal device when the uplink data is required to be transmitted early, and a large uplink is not required when the downlink is transmitted early.
  • UL Grant or multiple UL Grants.
  • the terminal device may send a first indication to the access network device by using a message 3 (Msg3), that is, the Msg3 may include the first indication.
  • the indication information is used to indicate that downlink early transmission is required, that is, downlink data is received before the RRC connection establishment is completed.
  • the indication of this mode is used when the message 1 is not used to distinguish between the uplink and the downlink, and the message 3 may be instructed to indicate that the terminal device wants to perform downlink data early transmission.
  • Msg3 may be any one of the following messages: an RRC Connection Request message, an RRC Connection Re-establishment Request message, and an RRC Connection Recovery Request.
  • the RRC connection request message or the RRC connection re-establishment request message carries a non-access stratum protocol data unit NAS PDU that may include data to be transmitted. That is, the uplink data may be sent through the RRC Connection Request message or the NAS PDU in the RRC Connection Re-establishment Request message.
  • the first indication may be a dedicated preamble (for example, referred to as a first random access preamble).
  • the terminal device sends the first random to the access network device. Access the preamble.
  • the first random access preamble is used to indicate early transmission of uplink data or early transmission of downlink data.
  • the terminal device may send a random access preamble to the access network device by using a specific resource (for example, as the first random access resource), thereby indicating that the uplink data is early. Pass or downlink data early transmission.
  • a specific resource for example, as the first random access resource
  • the terminal device may indicate that the data is transmitted early by using a time-frequency code. For example, if the terminal device sends a random access request message by using a specific time-frequency code resource (for example, the first time-frequency code resource), it indicates that the terminal device needs to perform early uplink data transmission, and the terminal device uses another time-frequency code resource ( For example, the second time-frequency code resource indicates that the terminal device is to perform early reception of downlink data.
  • the time-frequency code can be any combination of time domain, frequency domain, and code domain, such as different time-frequency resources, different code domain resources, different time-frequency code resources, and the like.
  • the access network device may also send an indication to the terminal device by using a Physical Downlink Control Channel (PDCCH) command, to indicate that the UE needs to perform random transmission of data early transmission.
  • PDCCH Physical Downlink Control Channel
  • Incoming such as uplink data early transmission or downlink data early transmission. That is, random access is performed by the PDCCH order method.
  • Specific indication information can be carried by DCI.
  • the terminal device transmits data to and from the access network device before the establishment of the RRC connection is completed.
  • the terminal device may transmit the data by transmitting a non-access stratum protocol data unit NAS PDU with the access network device before the RRC connection establishment is completed.
  • NAS PDU non-access stratum protocol data unit
  • the terminal device may further pass data with the access network device before the RRC connection establishment is completed.
  • the radio bearers the DRB to transmit data.
  • data (including uplink data and downlink data) can be transmitted before the RRC establishment is completed, thereby saving signaling overhead for establishing a required bearer for transmitting data, and reducing device power consumption.
  • FIG. 3 is a schematic flowchart of a method for data transmission according to an embodiment of the present application. The method shown in Figure 3 is suitable for early transmission of upstream data.
  • the terminal device sends a random access preamble to the access network device.
  • the terminal device sends a random access request message, that is, message 1 (Msg1), to the access network device.
  • the terminal device may transmit Msg1 on a specific resource (for example, referred to as random access resource #A).
  • the random access resource #A can be used to indicate early transmission of uplink data or early transmission of downlink data.
  • the terminal device may also transmit a dedicated preamble (for example, referred to as random access preamble #A).
  • the random access preamble #A can also be used to indicate early transmission of uplink data or early transmission of downlink data.
  • the random access resource #A is an example of the first random access resource, and may also be a combination of other examples, such as a time-frequency code, where the random access preamble #A is the first random access preamble. Example.
  • the access network device After receiving the Msg1, the access network device sends a random access response message to the terminal device. That is, the access network device sends a message 2 (Msg2).
  • Msg2 message 2
  • Msg2 carries Timing Advance (TA) and uplink resource allocation (UL Grant).
  • the UL Grant is a resource allocated to the terminal device by the access network device and used for the terminal device to transmit the message 3 (Msg3).
  • Msg3 message 3
  • the access network device may learn, according to the time-frequency code resource information, such as the first random access preamble or the first random access resource, that the UE wants to perform early data transmission, and if it is uplink When the data is transmitted early, the terminal device is allocated resources for transmitting uplink data.
  • the resource allocated by the access network device to the terminal device for transmitting uplink data together with the UL Grant is referred to as a target resource.
  • the target resource allocated by the access network device may be a large uplink resource for transmitting the message 3 and the uplink data, or two independent resources, one for transmitting the message 3 and one for transmitting the uplink data.
  • 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 It is 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 resource size that needs to be allocated can be further distinguished according to the access resources.
  • the terminal device sends the Msg3 and the uplink data to the access network device according to the Msg2.
  • Msg3 can be transmitted together with the uplink data or separately. In the case where Msg3 is transmitted together with the uplink data, Msg3 can carry the identity of the terminal device. In the case that the Msg3 and the uplink data are separately transmitted, the uplink data may carry the identifier of the terminal device or be scrambled by the identifier of the terminal device.
  • the identifier of the terminal device may be, for example, a Radio Network Temporary Identifier (RNTI)--a cell radio network temporary identifier, a hash service temporary mobile subscriber identity (hash S-TMSI), an S-TMSI, a truncated S -TMSI, access random number, International Mobile Subscriber Identification Number (IMSI), and MAC CE
  • RNTI Radio Network Temporary Identifier
  • RNTI Radio Network Temporary Identifier
  • IMSI International Mobile Subscriber Identification Number
  • MAC CE MAC CE
  • the uplink data may be transmitted on the pre-configured or reserved resource for uplink data early transmission while transmitting the Msg3.
  • the terminal device may also simultaneously transmit the Msg3 and the uplink data on the target resource indicated by the Msg2.
  • the Msg3 may be an RRC connection request message or an RRC connection re-establishment request message, where the RRC connection request message or the RRC connection re-establishment request message includes a non-access stratum protocol that includes the uplink data.
  • Data unit NAS PDU Data unit NAS PDU. Therefore, the uplink data early transmission can be realized by the Control Plane CIoT EPS optimisation (CP).
  • CP Control Plane CIoT EPS optimisation
  • the NAS PDU may be sent by using a Bearer Signaling Radio Bearer (SRB) 1 bit.
  • SRB Bearer Signaling Radio Bearer
  • the message carrying the NAS PDU is a UL information transfer, so that the access network device can learn that the terminal device uses the CP according to the corresponding logical channel identifier (Identity, ID).
  • the RRC connection request message and the RRC connection re-establishment request message are both one type of Msg3
  • the RRC connection request message is used to establish an RRC connection
  • the RRC connection re-establishment request message is used to re-establish an RRC connection.
  • the RRC connection request message and the RRC connection re-establishment request message reference may be made to the prior art, which is not specifically described in this application.
  • the 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 by the data radio bearer DRB. Therefore, the uplink data early transmission can be realized by the User plane CIoT EPS optimisation (UP). Similarly, the data can be sent to the access network device along with the message 3, or it can be sent separately.
  • UP User plane CIoT EPS optimisation
  • the RRC connection recovery request message or the RRC connection re-establishment request message is used to re-recover the RRC connection after the RRC connection is released by the access network device.
  • the RRC connection recovery request message or the RRC connection re-establishment request message is used to re-recover the RRC connection after the RRC connection is released by the access network device.
  • the access network device sends the uplink data to the MME or the S-GW.
  • the terminal device may be in the form of reserved resources, so that the terminal device has the requirement of early transmission of uplink data.
  • the terminal device may indicate the access network device by using Msg1, and the terminal device needs to perform uplink data early transmission, or may not indicate to the access network device that the terminal device data is transmitted early.
  • the access network device may perform uplink data early transmission, for example, by randomly accessing resource #A or The random access preamble #A knows that the terminal device needs to perform uplink data early transmission, and allocates resources for transmitting uplink data, for example, target resources, to the terminal device, so that the terminal device can be allocated by the access network device while transmitting the Msg3.
  • the resources simultaneously send upstream data.
  • uplink data early transmission can be implemented, thereby saving power consumption and signaling overhead.
  • FIGS. 4 and 5 a data transmission method based on the CP scheme and the UP scheme will be separately described with reference to FIGS. 4 and 5. It should be understood that the steps shown in FIG. 4 and FIG. 5 that are the same or corresponding to FIG. 2 may refer to the description of FIG. 2 above. To avoid repetition, when referring to FIG. 4 and FIG. 5, it will no longer be The same or corresponding content is described in detail.
  • FIG. 4 is a schematic flowchart of uplink data uplink transmission based on the CP scheme according to an embodiment of the present application.
  • the terminal device sends the Msg1 to the access network device.
  • the access network device After receiving the Msg1, the access network device sends the Msg2 to the terminal device.
  • the terminal device sends an RRC connection request message or an RRC connection re-establishment request message to the access network device, where the RRC connection request message or the RRC connection re-establishment request message carries a NAS PDU including the uplink data.
  • the access network device can save the terminal device capability information of the CP solution.
  • the access network device can find the capability information of the access network device to store the terminal device according to the S-TMSI, and then access the network device.
  • the network device can determine whether the terminal device has the capability of early data transmission. If the terminal device does not have the capability, the connection can be rejected or rolled back to a normal process.
  • the access network device does not know that the S-TMSI is changed through the NAS information transmission. Therefore, the information stored by the access network device (such as the information obtained from the UE Information Transfer message) does not match the saved S-TMSI of the terminal device. Therefore, when the terminal device sends the S-TMSI carried in the message 3, it may be the S-TMSI used by other terminal devices, such that the access device device stores the terminal device capability, and the terminal device quality of service (QoS) information. There will be a corresponding error, so the following solutions are proposed:
  • the access network device When the MME re-assigns the S-TMSI to a certain terminal device, the access network device is notified, and the access network device can delete the information corresponding to the S-TMSI, including the capability information, or notify the access network device to newly allocate.
  • the S-TMSI after receiving the access network device, updates the S-TMSI, so that the new S-TMSI of the terminal device can match the related information of the terminal device.
  • the notification message is an S1AP message, such as a NAS transmission message, a connection establishment indication message, and the like. That is, the downlink NAS transport message carries the S-TMSI for updating the S-TMSI to correspond to the related information of the terminal device previously received from the UE information transmission message.
  • the MME will notify the terminal device of several access networks recently accessed when the S-TMSI is reassigned.
  • the devices enable them to update the S-TMSI in time or notify the terminal devices that the terminal device recently accesses to delete the stored old S-TMSI and its associated terminal device related information, such as UE Qos, terminal device radio capabilities, etc. .
  • the access network device and the MME have a timer.
  • the S-TMSI has the context of the terminal device.
  • the access network device starts the timer, and when the timer overflows, the relevant context is deleted.
  • the MME also has a timer. When an S-TMSI is allocated, it is started. Before the timer overflows, the S-TMSI cannot be allocated to other terminal devices.
  • the access network device sends a Retrieve UE Information Message to the MME, where the acquiring the terminal device information message includes the uplink data, and may also be another message name, and the specific signaling name is not limited. .
  • the MME can obtain the uplink data of the terminal device, and implement early transmission of the uplink data.
  • the acquiring the terminal device information message further includes requesting the downlink data indication information, and the method may further include:
  • the MME sends a UE information transmission message (UE Information Transfer) to the access network device, where the user information transmission message includes downlink data, and may also be other message names, and the specific signaling name is not limited;
  • UE Information Transfer UE Information Transfer
  • the access network device sends the downlink data to the terminal.
  • the method may further include:
  • 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.
  • the release message may be an RRC connection setup message, an RRC connection re-establishment message, an RRC connection recovery, an RRC connection reject message, or an RRC connection release message.
  • the message may include related information in the RRC connection release, and is used to release the connection of the terminal device, which may include the release reason. , redirection instructions, etc.;
  • the device may also carry an indication information, such as a cause value, to indicate that the terminal device is released to the idle state;
  • the access network device sends the RRC connection release message and carries the identifier information of the terminal device
  • the MAC CE that carries the identifier may be added to the RRC message, and the terminal device is directly released to the idle state.
  • the terminal device may also send a message 5 to the access network device. After the RRC connection is established, the access network device sends an RRC connection release message to the terminal device.
  • the access network device may send downlink data to the terminal device by using a release message in S370. That is, the downlink data may be carried in the release message. Further, the downlink data is data encapsulated in the NAS PDU.
  • the S470 may also be sent in a scenario where the MME does not have downlink data transmission, that is, if the MME does not have downlink data to transmit, the access network device may release the terminal device to the idle state by sending a release message to the terminal device.
  • the RRC connection setup message, the RRC connection re-establishment message, the RRC connection re-establishment, or the RRC connection reject message can release the terminal device in advance when the MME has no downlink data transmission, which can save signaling overhead compared to the release process of the prior art. On the other hand, it is also possible to reduce the power consumption of the terminal device.
  • FIG. 5 is a schematic flowchart of uplink data early transmission based on an UP scheme according to an embodiment of the present application.
  • the terminal device sends the Msg1 to the access network device.
  • the access network device After receiving the Msg1, the access network device sends the Msg2 to the terminal device.
  • the terminal device sends an RRC connection setup request or an RRC connection reestablishment request message or an RRC connection re-establishment request message to the access network device.
  • the uplink data may be sent by a data radio bearer DRB.
  • the upstream data needs to be encrypted, and the key can be updated by the last hop chaining count (NCC).
  • the access network device sends a second request message to the MME.
  • the content in the second request message may be the same as the content in the terminal device context recovery request message.
  • the second request message may be a terminal device context recovery request message.
  • the access network device After receiving the RRC connection recovery request message or the RRC connection re-establishment request message, the access network device performs verification of 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 interface, and the source access network device performs verification. After successful, the terminal is successfully used. The context information of the 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.
  • short-MAC-I Short Message Authentication Code for Integrity
  • the content in the second response message may be the same as the content in the terminal device context recovery response message.
  • the second response message is a terminal device context recovery response message.
  • the access network device If the response message received by the access network device 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 the RRC.
  • the connection recovery message or the RRC connection setup message is sent to the terminal device, and the message may include an indication information indicating that the data E-RAB is rejected or the transmission fails or indicating that the terminal device needs to resend the previously transmitted data packet.
  • the access network device additionally divides a UL grant for this data transmission.
  • the access network device receives the second response message, and sends the uplink data to the S-GW.
  • the S-GW can obtain the uplink data of the terminal device, and realize the early transmission of the uplink data.
  • the method may further include:
  • the access network device may send a terminal device context release request message or a terminal device context suspension request message to the MME.
  • 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.
  • 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, where the release message is used to release the terminal device to Idle state.
  • the release message herein may be an RRC connection setup message, an RRC connection recovery message, an RRC connection re-establishment message, an RRC connection reject message, or an RRC connection release message.
  • the message may include related information in the RRC connection release, for releasing the connection of the terminal device, which may specifically include releasing Reason, redirection indication, etc.;
  • the device may also carry an indication message, such as a cause value, indicating that the terminal device is released to the idle state;
  • the terminal device If the access network device sends an RRC connection release message, the terminal device is directly released to the idle state.
  • the access network device also receives the downlink data in this process, it can be sent to the terminal device together with the release message.
  • the RRC connection setup message, the RRC connection recovery message, the RRC connection re-establishment complete message, the RRC connection reject message, or the RRC connection release message may release the terminal device in advance when the S-GW has no downlink data transmission, compared to the prior art.
  • the release process can save signaling overhead, and on the other hand, can reduce the power consumption of the terminal device.
  • FIG. 6 is a data transmission method based on a CP scheme according to another embodiment of the present application. The method shown in Figure 6 is suitable for early transmission of downlink data.
  • the terminal device sends a random access preamble to the access network device.
  • the terminal device sends a random access request message, that is, message 1 (Msg1), to the access network device.
  • message 1 Msg1
  • the access network device After receiving the Msg1, the access network device sends a random access response message to the terminal device. That is, the access network device sends a message 2 (Msg2).
  • Msg2 carries TA and UL Grant.
  • the UL Grant is a resource allocated to the terminal device by the access network device and used for the terminal device to transmit the message 3 (Msg3).
  • Msg3 message 3
  • the terminal device sends an Msg3 to the access network device, where the Msg3 may include a service request message. Request Message).
  • the message 3 may be instructed to indicate that the UE is to perform downlink data early transmission, that is, downlink data transmission is performed before the RRC connection establishment is completed.
  • the access network device may trigger signaling interaction with the core network device earlier.
  • the Msg3 may be an RRC Connection Request message or an RRC Connection Re-establishment Request message.
  • the access network device After receiving the Msg3, the access network device sends a request message to the MME.
  • the message may be a UE information message or other messages.
  • the MME After receiving the request message, the MME sends the downlink data to the access network device.
  • the MME may send the downlink data to the access network device by using a UE information transmission message. That is, the UE information transmission message may carry the downlink data.
  • the access network device sends the downlink data to the terminal device.
  • the access network device may send the downlink data to the terminal device by releasing a message.
  • the terminal device can enter the idle state after receiving the release message.
  • the release message herein may be an RRC connection setup message, an RRC connection recovery message, an RRC connection re-establishment message, an RRC connection reject message, or an RRC connection release message.
  • the message may include related information in the RRC connection release, for releasing the connection of the terminal device, which may specifically include releasing Reason, redirection indication, etc.;
  • the device may also carry an indication message, such as a cause value, indicating that the terminal device is released to the idle state;
  • the terminal device If the access network device sends an RRC connection release message, the terminal device is directly released to the idle state.
  • the RRC connection setup message, the RRC connection reestablishment message, the RRC connection re-establishment message, the RRC connection reject message, or the RRC connection release message may release the terminal device in advance when the MME has no downlink data transmission, compared to the release process of the prior art. It can save signaling overhead, and on the other hand, can reduce the power consumption of the terminal device.
  • uplink data early transmission can be implemented, thereby saving power consumption and signaling overhead.
  • FIG. 7 is a data transmission method based on an UP scheme according to another embodiment of the present application. The method shown in Figure 7 is suitable for early transmission of downlink data.
  • FIG. 7 is a schematic flowchart of a method for data transmission according to an embodiment of the present application.
  • the terminal device sends a random access preamble to the access network device.
  • the terminal device sends a random access request message, that is, message 1 (Msg1), to the access network device.
  • message 1 Msg1
  • the access network device After receiving the Msg1, the access network device sends a random access response message to the terminal device. That is, the access network device sends a message 2 (Msg2).
  • Msg2 message 2
  • Msg2 carries TA and UL Grant.
  • the UL Grant is a resource allocated to the terminal device by the access network device and used for the terminal device to transmit the message 3 (Msg3).
  • Msg3 message 3
  • the terminal device sends an Msg3 to the access network device according to the Msg2, where the Msg3 may include a Service Request Message.
  • the message 3 may be instructed to indicate that the downlink data is transmitted early, that is, the downlink data transmission is performed before the RRC connection establishment is completed, and the access network is accessed.
  • the device may trigger signaling interaction with the core network device earlier. See S740 and subsequent operations.
  • the Msg3 may be an RRC connection request or an RRC connection re-establishment request message or an RRC connection re-establishment request message.
  • the access network device After receiving the service request message in the Msg3, the access network device sends the service request message to the MME.
  • the access network device may send the service request message to the MME by using a terminal device context recovery request message.
  • the MME sends a service response message to the access network device according to the service request message.
  • the MME may resume the response message to the terminal device context after receiving the terminal device context recovery request message sent by the access network device.
  • S760 The MME sends a modify bearer request message to the S-GW.
  • the S-GW returns a modify bearer response message to the MME. Thereby the S-GW can obtain the address of the access network device.
  • the S-GW sends the downlink data to the access network device.
  • the access network device sends the downlink data to the terminal device.
  • the method may further include:
  • the access network device sends a terminal device context release request message or a terminal device context suspension request message to the MME;
  • 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;
  • 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, where the release message is used to release the terminal device to an idle state. .
  • the release message herein may be an RRC connection setup message, an RRC connection recovery message, an RRC connection re-establishment message, an RRC connection reject message, or an RRC connection release message. Specific information on the release can be found in other embodiments.
  • the message may include related information in the RRC connection release, and is used to release the connection of the terminal device, which may include a release reason, a redirection indication, and the like;
  • the access network device may also carry a cause value for sending, and the reason value indicates that the terminal device is released to the idle state;
  • the terminal device If the access network device sends an RRC connection release message, the terminal device is directly released to the idle state.
  • the access network device may send the downlink data to the terminal device by using the release message.
  • the RRC connection setup message, the RRC connection recovery message, the RRC connection re-establishment complete message, the RRC connection reject message, or the RRC connection release message may release the terminal device in advance when the S-GW has no downlink data transmission, compared to the prior art. Release the process, which can save signaling overhead, and on the other hand, can also reduce the terminal device Power consumption.
  • uplink data early transmission can be implemented, thereby saving power consumption and signaling overhead.
  • the paging message when the UE receives the paging message, the paging message may include an indication information, indicating that the UE may perform the downlink data early reception operation, so that the UE may perform the early downlink operation according to the downlink data.
  • the further core network device may carry an indication message in the paging message sent to the base station, which is used to indicate that the UE needs to perform the downlink data early reception operation.
  • the access network device may also send an indication to the terminal device by using a Physical Downlink Control Channel (PDCCH) command, to indicate that the UE needs to perform random transmission of data early transmission.
  • PDCCH Physical Downlink Control Channel
  • Incoming such as uplink data early transmission or downlink data early transmission. That is, random access is performed by the PDCCH order method.
  • the specific indication information may be carried by the DCI, or the resource location accessed by the UE indicated by the access network device is a resource location used for early data transmission to implement early data transmission.
  • the access network device can indicate, by using the PDCCH, how the UE uses the data early transmission.
  • FIG. 8 shows a schematic block diagram of a terminal device 800 of an embodiment of the present application.
  • the terminal device 800 includes a processing unit 810 and a transceiver unit 820.
  • the processing unit 810 is configured to generate a first indication, where the first indication is used to indicate that data needs to be transmitted before the RRC connection establishment is completed.
  • the transceiver unit 820 is configured to send, to the access network device, a first indication, where the first indication is used to indicate that data needs to be transmitted before the RRC connection establishment is completed;
  • the transceiver unit 820 is specifically configured to: send the first random access preamble to the access network device.
  • the transceiver unit 820 is specifically configured to: send a random access preamble to the access network device on the first random access resource.
  • the transceiver unit 820 is specifically configured to: send, to the access network device, a message 3 that includes a first indication, where the message 3 is any one of the following messages:
  • An RRC connection request message, an RRC connection re-establishment request message, and an RRC connection re-establishment 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. .
  • the first indication is used to indicate that data needs to be transmitted before the RRC connection establishment is completed, including:
  • the first indication is used to indicate that downlink data needs to be transmitted before the establishment of the RRC connection is completed.
  • the transceiver unit 820 is configured to: transmit a non-access stratum protocol data unit NAS PDU with the access network device before the RRC connection establishment is completed; or
  • the transceiver unit 820 is specifically configured to: receive a release message sent by the access network device, where the release message is a radio resource control RRC connection setup message, an RRC connection recovery message, an RRC connection reestablishment complete message, and an RRC connection. A reject message or an RRC Connection Release message, the release message being used to release the terminal device to an idle state.
  • the release message is a radio resource control RRC connection setup message, an RRC connection recovery message, an RRC connection reestablishment complete message, and an RRC connection.
  • a reject message or an RRC Connection Release message the release message being used to release the terminal device to an idle state.
  • processing unit 810 can be implemented by a processor
  • transceiver unit 820 can be implemented by a transceiver.
  • terminal device 800 may correspond to the terminal device described in the foregoing method, and each module or unit in the terminal device 800 is used to perform each performed by the terminal device in the method embodiment shown in FIG. 2 to FIG. The operation or processing procedure is omitted here for avoiding redundancy.
  • FIG. 9 shows a schematic block diagram of an access network device 900 in an embodiment of the present application.
  • the access network device 900 includes a processing unit 910 and a transceiver unit 920.
  • the transceiver unit 920 is configured to receive a first indication sent by the terminal device, where the first indication is used to indicate that data needs to be transmitted before the RRC connection establishment is completed.
  • the processing unit 910 is configured to determine whether the current state is before the completion of the establishment of the RRC connection
  • the transceiver unit 920 is configured to transmit data with the terminal device before the processing unit 910 determines that the RRC connection establishment is completed.
  • the transceiver unit 920 is specifically configured to: receive the first random access preamble sent by the terminal device.
  • the transceiver unit 920 is configured to: receive the random access preamble sent by the terminal device in the first random access resource.
  • the transceiver unit 920 is configured to: receive the message 3 that is sent by the terminal device and includes the first indication, where the message 3 is any one of the following messages:
  • An RRC connection request message, an RRC connection re-establishment request message, and an RRC connection re-establishment 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. .
  • the first indication is used to indicate that data needs to be transmitted before the RRC connection establishment is completed, including:
  • the first indication is used to indicate that downlink data needs to be transmitted before the establishment of the RRC connection is completed.
  • the transceiver unit 920 processing unit 910 transmitting a non-access stratum protocol data unit NAS PDU with the terminal device before the RRC connection establishment is completed; or
  • the transceiver unit 920 is configured to: send, to the terminal device, a release message, where the release message is a radio resource control RRC connection setup message, an RRC connection recovery message, an RRC connection reestablishment complete message, an RRC connection reject message, or An RRC connection release message is used to release the terminal device to an idle state.
  • the release message is a radio resource control RRC connection setup message, an RRC connection recovery message, an RRC connection reestablishment complete message, an RRC connection reject message, or An RRC connection release message is used to release the terminal device to an idle state.
  • processing unit 910 can be implemented by a processor
  • transceiver unit 920 can be implemented by a transceiver.
  • the access network device 900 can correspond to the access network device described in the foregoing method, and each module or unit in the access network device 900 is used to perform the method embodiments shown in FIG. 2 to FIG. 7, respectively.
  • the operations and processes performed by the access network device are omitted here for the sake of avoiding redundancy.
  • FIG. 10 is a schematic flowchart of a data transmission method according to another embodiment of the present application. It should be understood that FIG. 10 illustrates detailed communication steps or operations of the method, but these steps or operations are merely examples, and other embodiments of the present application or variations of the various operations in FIG. 10 may be performed. Moreover, the various steps in FIG. 10 may be performed in a different order than that presented in FIG. 10, and it is possible that not all operations in FIG. 10 are to be performed.
  • the terminal device sends a first indication to the access network device.
  • the access network device receives the first finger Show.
  • the first indication is used to instruct the terminal device to control RRC signaling transmission data (ie, uplink data) based on the first radio resource transmitted by the terminal device to the access network device, and/or the first indication is used for Instructing the access network device to control RRC signaling transmission data (ie, downlink data) based on the first radio resource transmitted by the access network device to the terminal device.
  • the first indication is used to indicate that the terminal device and the access network device carry data by using the first signaling that is transmitted, or transmit data while transmitting the first signaling, or after transmitting the first signaling. Then transfer the data.
  • the first signaling is a first RRC signaling between the terminal device and the access network device in the random access process.
  • the first indication is used to indicate that the terminal device will transmit uplink data based on the first RRC signaling with the access network device, and/or the first indication is used to indicate that the access network device is to be based on the terminal
  • the first RRC signaling between the devices transmits downlink data.
  • the first RRC signaling sent by the terminal device to the access network device is referred to 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.
  • the terminal device may send uplink data to the access network device based on RRC signaling #1, and the access network device may send downlink data to the terminal device based on RRC signaling #2. That is, the terminal device may perform uplink data early transmission based on RRC signaling #1, and the access network device may perform downlink data early transmission based on RRC signaling #2.
  • RRC signaling #1 may be message 3 (Msg3).
  • Msg3 may be, for example, an RRC Connection Request message, an RRC Connection Re-establishment Request message, or an RRC Connection Recovery Request message.
  • RRC connection request message For details of the RRC connection request message, the RRC connection re-establishment request message, and the RRC connection re-request request message, reference may be made to the prior art, and details are not described herein for brevity.
  • the RRC signaling #1 may also be a newly defined first RRC signaling (for example, referred to as an RRC connection data transmission message) sent by the terminal device to the access network device in the random access procedure.
  • the RRC connection data transmission message is a message that does not need to perform RRC connection management.
  • the RRC Connection Data Transfer message may be the first message after Message 2 (Msg2, ie, Random Access Response Message).
  • the RRC signaling #1 may further carry a Release Assistance Indication (RAI) for indicating that there is no uplink data in a short time.
  • RAI Release Assistance Indication
  • the terminal device remains in the RRC idle state according to the release assistance indication information.
  • the NAS may also carry a Release Assistance Indication (RAI), where the indication message may indicate to the core network device whether there is uplink data. Or downlink data, or just a confirmation or response to the receipt of the uplink data.
  • RAI Release Assistance Indication
  • RRC signaling #1 as the message 3 as an example.
  • the terminal device may send the first indication to the access network device by sending a message 1 (Msg1), that is, a random access request message. That is, the information in Message 1 or Message 1 can be used to indicate early transmission of uplink data or early transmission of downlink data.
  • Msg1 a message 1
  • Message 1 or Message 1 can be used to indicate early transmission of uplink data or early transmission of downlink data.
  • the preamble (or referred to as a 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 that the uplink data is transmitted early; if the preamble in message 1 is preamble #3, it indicates that the downlink data is transmitted early; if the preamble in message 1 is The preamble #3 indicates that the uplink data is transmitted early and the downlink data is transmitted early.
  • the terminal device may send a message 1 to the access network device on a specific resource, by using the specific resource.
  • the source indicates early transmission of uplink data and/or early transmission of downlink data.
  • the specific resource may be a time-frequency code resource. For example, if the terminal device sends the message 1 by using the time-frequency code resource #2, it indicates that the terminal device is to perform uplink data early transmission, and the terminal device uses the time-frequency code resource #3 to indicate that the terminal device needs to perform downlink data early transmission.
  • the time-frequency code can be any combination of a time domain, a frequency domain, and a code domain.
  • the access network device allocates the time frequency used by the RRC signaling #1 to the terminal device through the message 2 (Msg2), that is, the random access response message.
  • Msg2 the message 2
  • the time-frequency resource for transmitting the uplink data can also be allocated at the same time.
  • 11 to 14 show several formats of the message 2.
  • the message 2 can adopt any one of the formats.
  • the format of the message 2 shown in FIG. 11 to FIG. 14 includes an Up Timing Advance Command (TAC) and a Temporary Cell Radio Network Temporary Identity Field (TC-RNTI).
  • TAC Up Timing Advance Command
  • TC-RNTI Temporary Cell Radio Network Temporary Identity Field
  • the value in the uplink timing control field indicates the time advance adjustment amount, and is used by the terminal device to perform uplink synchronization.
  • the value in the Radio Network Temporary Identity field indicates the unique identifier within the cell that the access network device assigned to the terminal device.
  • the time advance adjustment amount and the C-RNTI can be specifically referred to the prior art, and will not be described in detail herein.
  • the TC-RNTI may be, for example, RNTI, hashS-TMSI, S-TMSI, truncated S-TMSI, access random number, IMSI, identifier of the terminal device carried in the MAC CE, etc. Make specific limits.
  • the value in the reserved field (R) is used to indicate the number of uplink resource allocation fields (UL Grants) included in the message 2. For example, when the value in the reserved field is 1, it indicates that the message 2 includes two uplink resource allocation fields (named as UL Grant #1 and UL Grant #2, respectively), and UL Grant #1 and UL Grant #2 are not related. adjacent.
  • the value in the UL Grant #1 is used to indicate the time-frequency resource used for transmitting the RRC signaling #1
  • the value in the UL Grant #2 is used to indicate the time-frequency resource for transmitting the uplink data.
  • the number of bits occupied by each field in the message 2 shown in FIG. 11 is only an example, and the present application does not specifically limit the number of bits occupied by each field in the message 2.
  • UL Grant #1 and UL Grant #2 shown in FIG. 12 occupy 20 bits and 16 bits, respectively. In practical applications, UL Grant #1 and UL Grant #2 can also occupy 16 bits and 20 bits, respectively. Take up 16 bits.
  • the value in the reserved field (R) is used to indicate the number of uplink resource allocation fields (UL Grants) included in the message 2. For example, when the value in the reserved field is 1, it indicates that the message 2 includes two uplink resource allocation fields (referred to as UL Grant #1 and UL Grant #2, respectively), and UL Grant #1 and UL Grant #2 are adjacent to each other. .
  • the value in the UL Grant #1 is used to indicate the time-frequency resource used for transmitting the RRC signaling #1, and the value in the UL Grant #2 is used to indicate the time-frequency resource for transmitting the uplink data.
  • the number of bits occupied by each field in the message 2 shown in FIG. 12 is only an example, and the present application does not specifically limit the number of bits occupied by each field in the message 2.
  • UL Grant #1 and UL Grant #2 shown in FIG. 12 occupy 20 bits and 16 bits, respectively.
  • UL Grant #1 and UL Grant #2 can also occupy 16 bits and 20 bits, respectively. Take up 16 bits.
  • Figure 13 is a schematic illustration of another format of Message 2.
  • the value in the reserved field (R) is used to indicate the role of the time-frequency resource 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 resource indicated by the UL Grant field is used to transmit RRC signaling #1 and uplink data; when the value in the reserved field is 0, it indicates that the UL Grant is in the UL Grant.
  • the time-frequency resources indicated by the values are only used to transmit RRC signaling #1.
  • the value in the reserved field When the value in the reserved field is 0, it indicates that the time-frequency resource indicated by the UL Grant field is used to transmit RRC signaling #1 and uplink data; when the value in the reserved field is 1, it indicates that in the UL Grant The time-frequency resource indicated by the value is only used to transmit RRC signaling #1.
  • the number of bits occupied by each field in the message 2 shown in FIG. 13 is only an example, and the present application does not specifically limit the number of bits occupied by each field in the message 2.
  • the UL Grant shown in FIG. 13 occupies 36 bits. In practical applications, the UL Grant can occupy 30 bits.
  • 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 uplink included in the message 2.
  • the number of resource allocation (UL Grant) fields For example, when the value in R#2 is 1, it indicates that the message 2 includes two uplink resource allocation fields (referred to as UL Grant #1 and UL Grant #2, respectively).
  • the value in the UL Grant #1 is used to indicate the time-frequency resource used for transmitting the RRC signaling #1
  • the value in the UL Grant #2 is used to indicate the time-frequency resource for transmitting the uplink data.
  • the first bit in R#2 may be any bit in R#2.
  • the number of bits occupied by each field in the message 2 shown in FIG. 6 is only an example, and the present application does not specifically limit the number of bits occupied by each field in the message 2.
  • the format of the message 2 shown in FIG. 11 to FIG. 14 is only an example.
  • the message 2 may also adopt other formats or a modification of the format in FIG. 11 to FIG.
  • the location of each field in message 2 may be different from the location of each field in the format of message 2 shown in Figures 11-14.
  • the format of the message 2 may further include other fields than the fields shown in FIGS. 11 to 14, or the format of the message 2 may include only some of the fields shown in FIGS. 11 to 14.
  • RRC signaling #2 may be message 4 (Msg4).
  • the message 4 may be, for example, a Contention Resolution message, an RRC Connection Setup message, an RRC Connection Re-establishment message, an RRC Connection Recovery message, an RRC Connection Reject message, or an RRC Connection Release message.
  • the message 4 may also be a newly defined first RRC signaling that is sent by the access network device to the terminal device in the random access process, which is not limited in this embodiment of the present application.
  • S1020 The data is transmitted between the terminal device and the access network device based on the first RRC signaling.
  • the terminal device transmits uplink data to the access network device based on RRC signaling #1; and/or, the access network device transmits downlink data to the terminal device based on RRC signaling #2.
  • the uplink data and/or the downlink data may be sent through a non-access stratum protocol data unit NAS PDU.
  • NAS PDU non-access stratum protocol data unit
  • RRC signaling #1 may carry NAS PDUs of uplink data. That is, the terminal device can transmit uplink data through the NAS PDU carried by the RRC signaling #1. For example, the terminal device can simultaneously send the NAS PDU carrying the uplink data and the RRC signaling #1 to the access network device, or the terminal device sends the NAS PDU carrying the uplink data immediately after transmitting the RRC signaling #1.
  • RRC signaling #2 can carry NAS PDUs of downlink data. That is, the access network device can send downlink data through the NAS PDU carried by the RRC signaling #2. For example, the access network device can simultaneously send the NAS PDU carrying the downlink data and the RRC signaling #1 to the terminal device, or the access network device sends the RRC signaling #2, and then sends the NAS PDU carrying the downlink data. .
  • uplink data or downlink data may be sent through DRB or SRB0.
  • the uplink data and the RRC signaling #1 may be multiplexed into one transport block, or may be used as two or more The transport blocks are transmitted separately.
  • the downlink data may be multiplexed with RRC signaling #2 by one transport block, or may be transmitted separately as two or more transport blocks.
  • the RRC signaling #1 and the uplink data may carry the identifier of the terminal device.
  • the uplink data may carry the identifier of the terminal device or be scrambled by the identifier of the terminal device.
  • RRC signaling #2 and downlink data may carry the identifier of the terminal device.
  • the downlink data may carry the identifier of the terminal device or be scrambled by the identifier of the terminal device.
  • the identifier of the terminal device may be, for example, an RNTI, a hashS-TMSI, an S-TMSI, a truncated S-TMSI, an access random number, an IMSI, an identifier of a terminal device carried in a MAC CE, and the like.
  • the logo is not specifically limited.
  • the uplink data can be separately transmitted as RRC signaling #1 as two transport blocks
  • the NAS PDU carrying the uplink data can be sent through SRB 1bis or SRB0, or RRC signaling #1 through SRB. 0 is sent and the uplink data is sent through the DRB.
  • the transmission of the downlink data may refer to the manner of transmitting the uplink data. For brevity, no further details are provided herein.
  • the NAS message may be a Control Plane Service Request (ESM Data Transport).
  • uplink and/or downlink data transmission can be implemented based on the first RRC signaling between the terminal device and the access network device, without establishing an RRC connection, thereby saving transmission
  • the data establishes the signaling overhead of the required bearers and can reduce the power consumption of the device.
  • FIG. 15 to FIG. 18 a data transmission method according to an embodiment of the present application is separately described for uplink data early transmission and downlink data early transmission, respectively.
  • the steps, terms, concepts, and the like shown in FIG. 15 to FIG. 18 which are the same or corresponding to FIG. 2 can refer to the description of FIG. 2 above, and in order to avoid repetition, when referring to FIG. 15 to FIG. The same or corresponding content will not be described in detail.
  • RRC signaling #1 as the message 3
  • RRC signaling #2 as the message 4.
  • FIG. 15 is a schematic flowchart of a method for data transmission according to an embodiment of the present application. The method shown in FIG. 15 is applicable to uplink data early transmission based on the CP scheme.
  • the terminal device sends a message 1 to the access network device.
  • the message 1 is used to instruct the terminal device to transmit data by using uplink and/or downlink data early transmission. .
  • the terminal device allocates resources for transmitting uplink data.
  • the size of the resource for transmitting the uplink data may be fixed, such as 100 bytes.
  • the size of the resource for transmitting the uplink data may also be determined by the access network device according to the first message (eg, the resource that sent the first message or the preamble in the first message). That is, the first message, for example, the resource that sends the first message or the preamble in the first message, can also be used to indicate the size of the uplink data, so that the access network device can be reasonably allocated for transmission according to the size of the uplink data.
  • Resources for upstream data are examples of the first message or the preamble in the first message.
  • the terminal device sends a message 3 to the access network device.
  • message 3 can carry uplink data.
  • the terminal device may transmit the message 3 if there is uplink data to be transmitted.
  • uplink data is transmitted on pre-configured or reserved resources for early transmission of uplink data.
  • the terminal device may also transmit the message 3 and the uplink data on the target resource indicated by the message 2.
  • the message 3 is defined as defined in the above embodiment, and the specific message name is not limited.
  • the access network device sends a candidate message #1 to the MME.
  • 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 a newly defined other message, which is not limited in this embodiment of the present application.
  • the MME can obtain the uplink data of the terminal device, and implement early transmission of the uplink data.
  • the method may further include:
  • the access network device sends the candidate message #3 to the terminal device.
  • candidate message #3 may be message 4.
  • the 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 by the embodiment of the present application.
  • the candidate message #3 may carry an indication information (for example, as indication information #2).
  • the indication information #2 is used to indicate that the current process or session process can end, or indicate that the terminal device needs to return or maintain in an idle state.
  • the indication information #2 may be expressed as an End Indication or a release indication.
  • the terminal device after receiving the message 4, the terminal device sends a message 5 to the access network device.
  • the message 5 may be, for example, an RRC Connection Complete message, an RRC Connection Reestablishment Complete message, or an RRC Connection Recovery Complete message.
  • the message 5 does not carry the NAS message. If the access network device needs to transmit downlink data at this time, the access network device sends the downlink data to the terminal device after receiving the message 5, and indicates that the terminal device returns to the idle state or remains in the idle state.
  • the terminal device after receiving the message 4 (for example, a contention resolution message, an RRC connection setup message, an RRC connection re-establishment message, or an RRC connection recovery), the terminal device establishes an RRC connection according to a normal RRC connection establishment procedure. If the terminal device does not have data on the uplink at this time, the terminal device may send an empty NAS message (for example, as a NAS message) on message 5 (such as RRC connection establishment completion, RRC connection re-establishment completion, and RRC connection recovery completion).
  • #1 such as ESM Data Transport, NAS message #1 has only a message header and no data unit.
  • the access network device After receiving the NAS message #1, the access network device sends the NAS message #1 to the MME through an initial UE message or other message. After receiving the message, the MME may ignore or discard the NAS message.
  • the subsequent process is the same as the prior art, and is not described here for brevity.
  • the terminal device may send the same NAS message as in the message 3 in the message 5, such as the RRC connection setup completion, the RRC connection re-establishment completion, and the RRC connection recovery completion (for example, as the NAS message # 2), such as Control Plane Service Request (ESM Data Transport) message.
  • the NAS message #2 may include an indication information (for example, indicated 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, when the access network device After receiving the NAS message #2, the NAS message is sent to the MME, and the MME can ignore the message according to the indication information.
  • the UE may send a NAS message (for example, as NAS message #3) in the message 5, such as RRC connection establishment completion, RRC connection re-establishment completion, RRC connection recovery completion, NAS message# 3 may include an indication information (for example, indicated as indication information #4), and the indication information #4 is used to distinguish between the NAS message #3 and the NAS message in the message 5 in the prior art, so that the MME performs subsequent processing, and when the MME receives the finger After the message #4 is displayed, the NAS message can be ignored or discarded. Or the NAS message and the indication information are two fields. Therefore, the NAS message #3 can be either carrying the indication information or dividing the indication information into different fields.
  • the application scenario of NAS message #3 is: the uplink data has been transmitted through RRC signaling #1, and the NAS message #3 is used when there is no additional uplink NAS data in message 5. Since the terminal device has already sent the NAS message in the message 3, the NAS message in the existing message 5 and the initial UE message is required to be overcome by the foregoing implementation manners.
  • the foregoing implementation manner may be applicable to a processing manner when there is one downlink packet but the access network device cannot transmit, or when the core network device has multiple downlink packets, thereby completing data transmission.
  • the terminal device can be released in advance or the terminal is in an idle state, which can save signaling overhead compared with the prior art release procedure. On the one hand, it is also possible to reduce the power consumption of the terminal device.
  • the candidate message #3 may further include a redirection indication or the like.
  • the candidate message #3 may further carry indication information, where the indication information is used to indicate that the terminal returns or remains in the idle state.
  • candidate message #3 may carry downlink data.
  • the downlink data may be encapsulated in a NAS PDU. That is, the candidate message #3 may carry the NAS PDU including the downlink data.
  • the NAS PDU can be carried on SRB0.
  • the downlink data may be sent by the MME to the access network device by using a paging message, or may be sent by the MME to the access network device by using the candidate message #2.
  • the downlink data may also be sent to the access network device by using the downlink NAS transmission between the MME and the access network device after the MME sends the candidate message #2 and the access network device sends the candidate message #3. .
  • the access network device can inform the MME in advance of the size of the data packet that can be scheduled by itself. For example, the access network device indicates the size of the data packet that can be scheduled by using the candidate message #1, and the MME can send the downlink data to the unpacked data. Access network equipment. In this case, the access network device can continuously send multiple data packets to the terminal device, and each data packet carries the identification information of the terminal device. After the last data packet is sent, the access network device can send the indication information to the terminal. #2, to release the terminal device or instruct the terminal to return or remain idle.
  • the method further includes:
  • the MME sends the candidate message #2 to the access network device.
  • the candidate message #2 includes the downlink data.
  • the candidate message #2 may be, for example, a UE Information Transfer Message, or a Downlink NAS Transport Message, or a newly defined message, which is not limited in this embodiment of the present application.
  • the candidate message #2 may further include an indication information (for example, referred to as indication information #1), the indication information #1 is used to indicate that the current process or the session process may end, or indicate that the terminal device needs to return or maintain Idle state.
  • indication information #1 can be expressed as an End Indication.
  • the MME when the MME sends the candidate message #2 to the access network device, if there is no downlink data, the MME may carry the indication information in the message, where the indication information is used to indicate that the process ends or the access network device indicates the terminal. The device returns to the idle state or remains idle.
  • the MME when the MME sends the candidate message #2 to the access network device, if there is downlink data, if there is only one
  • the MME carries the indication information in the message, and the indication information is used to indicate that the process ends or the access network device is instructed to indicate that the terminal device returns to the idle state or maintains the idle state.
  • the MME does not carry the indication information when transmitting the 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 an intermediate state of the idle state or the idle state-connected state or the transition state of the terminal is that the air interface does not enter the connected state, and the S1 port enters the connected state.
  • the MME can instruct the access network device to notify the terminal device to return or maintain the idle state by transmitting the indication information #1.
  • the indication information #2 may be the same as or different from the indication information #1, and the embodiment of the present application is not limited thereto.
  • the access network device may send an Acknowledgement (ACK) to the MME, for example, sending a 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 the paging message to the access network device.
  • the access network device may feed back to the MME that the data is not successfully sent or the unsent data is sent to the MME, and the MME may pass the paging. The way the terminal device acquires data.
  • uplink data transmission can be implemented 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.
  • FIG. 16 is a schematic flowchart of a method for data transmission according to an embodiment of the present application.
  • the method shown in FIG. 16 is applicable to uplink data early transmission based on the UP scheme. It should be understood that the terms, concepts, and the like, which are the same or corresponding to those of FIG. 16 appearing below, may refer to the description of FIG. 15 above, and in order to avoid repetition, the details will not be described below.
  • the terminal device sends a message 1 to the access network device.
  • the terminal device sends a message 3 to the access network device.
  • Message 3 includes uplink data, and uplink data can be transmitted through the data radio bearer DRB.
  • the upstream data needs to be encrypted, and the key can be updated by the last hop chaining count (NCC).
  • the bearer DRB that the terminal device sends data may be based on the DRB configuration in the last connection or adopts 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 is reconfigured, for example, by using an RRC reconfiguration message or an RRC connection recovery message.
  • the access network device sends a second request message to the MME.
  • the content in the second request message may be the same as the content in the UE context recovery request message (UE Context Resume Request).
  • the second request message may be a UE context recovery request message.
  • the access network device After receiving the 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, the short-MAC-I needs to be sent to the source access network device through the X2 interface, and the source access network device performs verification. After the verification succeeds, the source is verified. The 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.
  • short-MAC-I Short Message Authentication Code for Integrity
  • S1650 The MME sends a second response message to the access network device according to the second request message.
  • the content in the second response message may be the same as the content in the UE context recovery response message (UE Context Resume Response).
  • the second response message is a UE context recovery response message.
  • the access network device finds that the E-UTRAN Radio Access Bearer (E-RAB) corresponding to the data received by the access network device is rejected according to the received second response message, the access network device And sending an RRC connection recovery message or an RRC connection setup message to the terminal device, where the RRC connection recovery message or the RRC connection setup message may include an indication information, where the indication information is used to indicate that the data E-RAB is rejected or the transmission fails or indicates the terminal.
  • the device needs to resend the previously sent packets.
  • the access network device additionally allocates a UL grant for the data transmission.
  • the access network device After receiving the second response message, the access network device sends the uplink data to the S-GW.
  • the S-GW can obtain the uplink data of the terminal device, and realize the early transmission of the uplink data.
  • the method may further include:
  • the access network device may send a UE context release request message, a UE context suspension request message, or a release connection request message to the MME.
  • 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 complete message to the access network device according to the UE context suspension request message; or the MME sends a UE context suspension request according to the release connection request.
  • the access network device sends a UE context release message.
  • S1690 The access network device sends a candidate message #4 to the terminal device according to the terminal device.
  • the candidate message #4 may be a message 4, such as an RRC connection setup message, an RRC connection re-establishment message, an RRC connection recovery message, or an RRC connection release message.
  • the 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 by this embodiment.
  • candidate message #4 may be the same as or different from the candidate message #3, which is not limited by the embodiment of the present application.
  • the candidate message #4 may carry an indication information (for example, as indication information #5).
  • the indication information #5 is used to indicate that the current process or session process can end, or indicate that the terminal device needs to return or maintain in an idle state.
  • the indication information #5 can be expressed as an End Indication.
  • the indication information #5 may be the same as or different from the indication information #2, which is not limited by the embodiment of the present application.
  • the terminal device can be released in advance when the S-GW has no downlink data transmission, and the signaling overhead can be saved compared with the prior art release procedure. Reduce the power consumption of the terminal device.
  • the candidate message #4 may further include a redirection indication or the like.
  • candidate message #4 may carry downlink data.
  • the transmission is performed in several ways similar to S1560, such as establishing an RRC connection, and placing an empty NAS in message 5.
  • the data transmission method according to the embodiment of the present application may be based on the terminal device transmitting to the access network device.
  • the first RRC signaling implements uplink data transmission without establishing an RRC connection, thereby saving power consumption and signaling overhead.
  • FIG. 17 is a schematic flowchart of a data transmission method according to another embodiment of the present application. The method shown in FIG. 17 is applicable to downlink data early transmission based on the CP scheme.
  • the terminal device sends a message 1 to the access network device.
  • the terminal device sends a message 3 to the access network device, where the message 3 may include a service request message.
  • the message 3, like the above embodiment, may be existing RRC signaling, and may be newly defined RRC signaling.
  • the indication information (for example, the indication information #6) in the message 3 may be used to indicate that the terminal device is to perform downlink data early transmission, 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 may trigger signaling interaction with the core network device earlier.
  • the access network device After receiving the message 3, the access network device sends a request message to the MME.
  • the request message may be a UE information message or an initial UE message, or other newly defined message, which is not limited in this embodiment of the present application.
  • the MME After receiving the request message, the MME sends the downlink data to the access network device.
  • the MME may send the downlink data to the access network device by using a UE Information Transfer Message or a Downlink NAS Transport Message.
  • the access network device sends the downlink data to the terminal device by using a message 4.
  • the message 4 is further used to indicate that the terminal device remains in the idle state or returns to the idle state, and the terminal device returns to the idle state according to the message 4 or remains in the idle state.
  • the downlink data can be transmitted through the message 4, that is, the downlink data is transmitted early, thereby saving power consumption and signaling overhead.
  • FIG. 18 is a schematic flowchart of a data transmission method according to another embodiment of the present application. The method shown in FIG. 18 is applicable to downlink data early transmission based on the UP scheme.
  • S1810 The terminal device sends a message 1 to the access network device.
  • 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.
  • the access network device may send the service request message to the MME by using a terminal device context recovery request message.
  • S1850 The MME sends a service response message to the access network device according to the service request message.
  • the MME may resume the response message to the terminal device context after receiving the terminal device context recovery request message sent by the access network device.
  • S1860 The MME sends a modify bearer request message to the S-GW.
  • the S-GW returns a modify bearer response message to the MME. Thereby the S-GW can obtain the address of the access network device.
  • the S-GW sends the downlink data to the access network device.
  • the access network device sends the downlink data to the terminal device by using the message 4.
  • the method may further include:
  • the access network device sends a UE context release request message, a UE context suspension request message, or a release connection request message or other release request message to the MME;
  • 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 complete message to the access network device according to the UE context suspension request message; or the MME forwards the connection according to the release connection request.
  • the network access device sends a UE context release message.
  • the access network device sends a candidate message #5 to the terminal device according to the UE context suspension complete message of the UE context release command message.
  • candidate message #5 may be message 4.
  • the message 4 is, for example, an RRC Connection Setup message, an RRC Connection Re-establishment message, an RRC Connection Recovery message, or an RRC Connection Release message.
  • the 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 by the embodiment of the present application.
  • candidate message #5 may be the same as or different from the candidate message #3, which is not limited by the embodiment of the present application.
  • the candidate message #5 may carry an indication information (for example, as indication information #6).
  • the indication information #5 is used to indicate that the current process or session process can end, or indicate that the terminal device needs to return or maintain in an idle state.
  • the indication information #6 can be expressed as an End Indication.
  • the indication information #6 may be the same as or different from the indication information #2, which is not limited by the embodiment of the present application.
  • the terminal device can be released in advance when the S-GW has no downlink data transmission, and the signaling overhead can be saved compared with the prior art release procedure. Reduce the power consumption of the terminal device.
  • the candidate message #5 is an RRC connection setup message, an RRC connection re-establishment message, or an RRC connection recovery message.
  • the candidate message #5 may also include related information in the RRC connection release message, such as a release reason, a redirection indication, and the like.
  • the candidate message #5 may also carry a cause value indicating the reason for the RRC connection rejection.
  • the candidate message #5 is an RRC connection release message, the terminal is instructed to return or remain in an idle state.
  • the candidate message #5 may carry the identification information of the terminal device, and may be carried in the MAC CE or scrambled by the PDCCH.
  • the access network device may send the downlink data to the terminal device by using the candidate message #5.
  • uplink data transmission can be implemented 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.
  • the paging message may include an indication information, indicating that the access network device needs to perform downlink data early transmission operation, so that the terminal device can follow
  • the downlink data is transmitted early to perform the subsequent process
  • the core network device may carry an indication message on the paging message sent to the access network device, which is used to indicate that the access network device needs to perform downlink data early transmission.
  • the access network device receives the downlink packet and/or the indication information from the core network.
  • the indication information is used to indicate that the downlink data packet can be sent to the terminal by means of early data transmission (the following data is transmitted early).
  • the access network device may also send an indication to the terminal device by using the PDCCH, and is used to indicate that the UE needs to perform random access for early data transmission, such as uplink data early transmission or downlink data early. pass. That is, random access is performed by the PDCCH order method.
  • the specific indication information may be carried by the DCI, or the resource location accessed by the UE indicated by the access network device is a resource location for early data transmission to implement early data transmission.
  • the access network device can indicate, by using the PDCCH, the manner in which the UE uses the data early transmission.
  • FIG. 19 shows a schematic block diagram of a terminal device 1900 of an embodiment of the present application.
  • the terminal device 1900 includes a processing unit 1910 and a transceiver unit 1920.
  • the processing unit 1910 is configured to generate a first indication, where the first indication is used to indicate that the terminal device transmits RRC signaling data according to the first radio resource control sent by the terminal device to the access network device, and /or,
  • the first indication is used to instruct the access network device to control RRC signaling transmission data based on the first radio resource sent by the access network device to the terminal device.
  • the transceiver unit 1920 is configured to send, by the access network device, a first indication generated by the processing unit, and transmit data between the terminal device and the access network device based on the first RRC signaling.
  • processing unit 1910 can be implemented by a processor
  • transceiver unit 1920 can be implemented by a transceiver.
  • terminal device 1900 may correspond to the terminal device described in the foregoing method, and each module or unit in the terminal device 1900 is used to perform each performed by the terminal device in the method embodiment shown in FIG. 10 to FIG. 18, respectively.
  • the operation or processing procedure is omitted here for avoiding redundancy.
  • FIG. 20 shows a schematic block diagram of an access network device 2000 in the embodiment of the present application.
  • the access network device 2000 includes a processing unit 2010 and a transceiver unit 2020.
  • the processing unit 2010 is configured to control the transceiver unit 2020:
  • the terminal device Receiving a first indication sent by the terminal device, where the first indication is used to indicate that the terminal device transmits RRC signaling data according to the first radio resource control sent by the terminal device to the access network device, and/or ,
  • the first indication is used to instruct the access network device to control RRC signaling transmission data based on the first radio resource sent by the access network device to the terminal device;
  • processing unit 2010 can be implemented by a processor
  • transceiver unit 2020 can be implemented by a transceiver
  • the access network device 2000 may correspond to the access network device described in the foregoing method, and each module or unit in the access network device 2000 is used to perform the method embodiments shown in FIG. 10 to FIG. 18, respectively.
  • the operations and processes performed by the access network device are omitted here for the sake of avoiding redundancy.
  • the embodiments of the present application may 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 foregoing method embodiment may be completed by an integrated logic circuit of hardware in a processor or an instruction in a form of software.
  • the processor may be a central processing unit (CPU), the processor may be another general-purpose processor, a digital signal processor (DSP), or an application specific integrated circuit (ASIC). ), a field programmable gate array (FPGA) or other programmable logic device, discrete gate or transistor logic device, discrete hardware components.
  • the embodiment of the present application can be implemented or executed. The various methods, steps, and logic blocks disclosed.
  • the general purpose processor may be a microprocessor or the processor or any conventional processor or the like.
  • the steps of the method disclosed in the embodiments of the present application may be directly implemented by the hardware decoding processor, or may be performed by a combination of hardware and software in the decoding processor.
  • the software can be located in a random storage medium, such as a flash memory, a read only memory, a programmable read only memory or an electrically erasable programmable memory, a register, and the like.
  • the storage medium is located in the memory, and the processor reads the information in the memory and combines the hardware to complete the steps of the above method.
  • 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 memory.
  • the non-volatile memory may be a read-only memory (ROM), a programmable read only memory (ROMM), an erasable programmable read only memory (erasable PROM, EPROM), or an electrical Erase programmable EPROM (EEPROM) or flash memory.
  • the volatile memory can be a random access memory (RAM) that acts as an external cache.
  • RAM random access memory
  • RAM random access memory
  • many forms of RAM are available, such as static random access memory (SRAM), dynamic random access memory (DRAM), synchronous dynamic random access memory (Synchronous DRAM).
  • SDRAM double data rate synchronous DRAM
  • DDR SDRAM double data rate synchronous DRAM
  • ESDRAM enhanced synchronous dynamic random access memory
  • SLDRAM synchronously connected dynamic random access memory
  • DRRAM direct memory bus random access memory
  • the size of the sequence numbers of the foregoing processes does not mean the order of execution sequence, and the order of execution of each process should be determined by its function and internal logic, and should not be applied to the embodiment of the present application.
  • the implementation process constitutes any limitation.
  • the disclosed systems, devices, and methods may be implemented in other manners.
  • the device embodiments described above are merely illustrative.
  • the division of the unit is only a logical function division.
  • there may be another division manner for example, multiple units or components may be combined or Can be integrated into another system, or some features can be ignored or not executed.
  • the mutual coupling or direct coupling or communication connection shown or discussed may be an indirect coupling or communication connection through some interface, device or unit, and may be in an electrical, mechanical or other form.
  • the units described as separate components may or may not be physically separated, and the components displayed as units may or may not be physical units, that is, may be located in one place, or may be distributed to multiple network units. Some or all of the units may be selected according to actual needs to implement the solution of the embodiment. purpose.
  • 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.
  • the functions may be stored in a computer readable storage medium if implemented in the form of a software functional unit and sold or used as a standalone product.
  • the technical solution of the present application which is essential or contributes to the prior art, or a part of the technical solution, may be embodied in the form of a software product, which is stored in a storage medium, including
  • the instructions are used to cause a computer device (which may be a personal computer, server, or network device, etc.) to perform all or part of the steps of the methods described in various embodiments of the present application.
  • the foregoing storage medium includes: a U disk, a mobile hard disk, a read-only memory (ROM), a random access memory (RAM), a magnetic disk, or an optical disk, and the like, which can store program code. .

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Databases & Information Systems (AREA)
  • Computer Security & Cryptography (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

本申请提供了一种数据传输方法、终端设备和接入网设备，能够基于终端设备和接入网设备之间的第一条RRC信令传输数据，而不需要建立RRC连接，从而能够节省为传输数据而建立所需承载的信令开销。该方法包括：终端设备向接入网设备发送第一指示，第一指示用于指示终端设备基于终端设备向接入网设备发送的第一条无线资源控制RRC信令传输数据，和/或，第一指示用于指示接入网设备基于接入网设备向终端设备发送的第一条无线资源控制RRC信令传输数据；基于第一条RRC信令，终端设备与接入网设备之间传输数据。

Description

数据传输的方法、终端设备和接入网设备 技术领域
本申请涉及物联网领域，并且更具体涉及一种数据传输的方法、终端设备和接入网设备。
背景技术
随着无线通信的快速发展，人们早已不满足仅限于人与人的通信，物联网(Internet of Thing，IoT)技术应运而生，并且其市场需求增长迅猛。物联网(Internet of Thing，IoT)又称为机器间通信(Machine To Machine，M2M)或者机器类型通信(Machine Type Communications，MTC)。MTC业务具有一些特殊的业务特性，如传输数据量小、业务周期特性明显、低功耗和终端数量大等。
一种典型的蜂窝物联网系统是窄带物联网(Narrowband IOT，NB-IoT)。现有技术中，至少需要在RRC连接建立完成时才能够进行上下行数据传输，从而带来信令开销过大和浪费功耗的问题，这对于NB-IoT场景下的业务传输十分不利的。因此，需要一种新的数据传输方法，可以适用于NB-IoT场景下的业务传输。
发明内容
本申请提供了一种数据传输方法、终端和接入网设备，能够实现在无线资源控制(radio resource control，RRC)连接建立完成前传输数据，进而，能够节省为传输数据而建立所需承载的信令开销，并能够降低设备功耗。
第一方面，本申请涉及一种数据传输方法，该方法包括：终端设备向接入网设备发送第一指示，该第一指示用于指示在无线资源控制RRC连接建立完成前需要传输数据；该终端设备在该RRC连接建立完成前，与该接入网设备之间传输数据。
因此，根据本申请实施例的方法，能够根据第一指示在RRC建立完成前传输数据(包括上行数据和下行数据)，从而能够节省为传输数据而建立所需承载的信令开销，并能够降低设备功耗。
在一种可能的实现方式中，当该第一指示为随机接入前导码时，该终端设备向接入网设备发送第一指示，包括：该终端设备向该接入网设备发送第一随机接入前导码。
从而，接入网络设备根据第一随机接入前导码能够确定需要在RRC连接建立完成前需要数据，例如，能够确定终端设备需要进行上行数据早传，或者可以确定终端设备进行下行数据早传。
在一种可能的实现方式中，该终端设备向接入网设备发送第一指示，包括：终端使用第一时频码资源或第二时频码资源发送随机接入请求消息。其中，第一时频码资源可以用于指示上行数据早传，第二时频码资源可以用于指示下行数据早传。
在一种可能的实现方式中，该终端设备向接入网设备发送第一指示，包括：该终端设备在第一随机接入资源上向该接入网设备发送随机接入前导码。
从而，接入网络设备根据第一随机接入资源能够确定需要在RRC连接建立完成前需要数据，例如，能够确定终端设备需要进行上行数据早传，或者可以确定终端设备进行下行数据早传。
在一种可能的实现方式中，该终端设备向接入网设备发送第一指示，包括：该终端设备向该接入网设备发送包括第一指示的消息3，其中该消息3为下述任一种消息：
RRC连接请求消息、RRC连接重建立请求消息和RRC连接恢复请求。
在一种可能的实现方式中，该第一指示用于指示在无线资源控制RRC连接建立完成前需要传输数据，包括：
该第一指示用于指示在该RRC连接建立完成前需要传输下行数据。
在一种可能的实现方式中，该终端设备在该RRC连接建立完成前，与该接入网设备之间传输数据，包括：
该终端设备在该RRC连接建立完成前，与该接入网设备之间传输非接入层协议数据单元(Non-Access-Stratum Protocol Data Unit，NASPDU)；或者，
该终端设备在该RRC连接建立完成前，与该接入网设备之间通过数据无线承载(Data Radio Bearer，DRB)传输数据。
在一种可能的实现方式中，该方法还包括：该终端设备接收该接入网设备发送的释放消息，该释放消息为无线资源控制RRC连接建立消息、RRC连接恢复消息，RRC连接重建立完成消息、RRC连接拒绝消息或RRC连接释放消息，该释放消息用于将该终端设备释放到空闲态。
可选地，所述释放消息可以携带需要传输的数据。
进一步地，若该释放消息为RRC连接建立消息或RRC连接重建立消息、RRC连接恢复，该消息可以包括RRC连接释放里的相关信息，用于释放该终端设备的连接，具体可以包括释放原因，重定向指示等；
若该释放消息为RRC连接拒绝消息，则也可以携带一个指示信息，如原因值，用于表示将终端设备释放到空闲态；
若该释放消息为RRC连接释放消息并携带终端设备的标识信息，可以在RRC消息中也可以加一个承载该标识的无线媒体控制控制元素(Media Access Control，MAC CE)，则直接将终端设备释放到空闲态。
通过RRC连接建立消息、RRC连接重建立消息、RRC连接恢复或RRC连接拒绝消息，可以在MME没有下行数据传输时，提前释放终端设备，相对于现有技术的释放流程，能够节省信令开销，另一方面，也能够降低终端设备的功耗。
第二方面，提供了一种数据传输方法，包括：接入网设备接收终端设备发送的第一指示，该第一指示用于指示在无线资源控制RRC连接建立完成前需要传输数据；该接入网设备在该RRC连接建立完成前，与该终端设备之间传输数据。
因此，根据本申请实施例的方法，能够根据第一指示在RRC建立完成前传输数据(包括上行数据和下行数据)，从而能够节省为传输数据而建立所需承载的信令开销，并能够降低设备功耗。
在一种可能的实现方式中，当该第一指示为随机接入前导码时，该接入网设备接收终端设备发送的第一指示，包括：该接入网设备接收该终端设备发送的第一随机接入前导码。
从而，接入网络设备根据第一随机接入前导码能够确定需要在RRC连接建立完成前需要数据，例如，能够确定终端设备需要进行上行数据早传，或者可以确定终端设备进行下行数据早传。
在一种可能的实现方式中，该接入网设备接收终端设备发送的第一指示，包括：该接入网设备接收该终端设备在第一随机接入资源发送的随机接入前导码。
从而，接入网络设备根据第一随机接入资源能够确定需要在RRC连接建立完成前需要数据，例如，能够确定终端设备需要进行上行数据早传，或者可以确定终端设备进行下行数据早传。
在一种可能的实现方式中，接入网设备接收终端设备发送的第一指示，包括：该接入网设备接收该终端设备发送的包括第一指示的消息3，其中该消息3为下述任一种消息：
RRC连接请求消息、RRC连接重建立请求消息和RRC连接恢复请求。
在一种可能的实现方式中，该第一指示用于指示在无线资源控制RRC连接建立完成前需要传输数据，包括：该第一指示用于指示在该RRC连接建立完成前需要传输下行数据。
在一种可能的实现方式中，该接入网设备在该RRC连接建立完成前，与该终端设备之间传输数据，包括：该接入网设备在该RRC连接建立完成前，与该终端设备之间传输非接入层协议数据单元NAS PDU；或者，
该接入网设备在该RRC连接建立完成前，与该终端设备之间通过数据无线承载DRB传输数据。
在一种可能的实现方式中，所述方法还包括：该接入网设备向核心网设备发送所述NAS PDU。
在一种可能的实现方式中，该方法还包括：该接入网设备向该终端设备发送释放消息，该释放消息为无线资源控制RRC连接建立消息、RRC连接恢复消息，RRC连接重建立完成消息、RRC连接拒绝消息或RRC连接释放消息，该释放消息用于将该终端设备释放到空闲态。
可选地，所述释放消息可以携带需要传输的数据。
进一步地，若该释放消息为RRC连接建立消息或RRC连接重建立消息、RRC连接恢复，该消息可以包括RRC连接释放里的相关信息，用于释放该终端设备的连接，具体可以包括释放原因，重定向指示等；
若该释放消息为RRC连接拒绝消息，则也可以携带一个指示信息，如原因值，用于表示将终端设备释放到空闲态；
若该释放消息为RRC连接释放消息并携带用户设备标识信息，可以在RRC消息中也可以加一个承载该标识的MAC CE，则直接将终端设备释放到空闲态。
通过RRC连接建立消息、RRC连接重建立消息、RRC连接恢复或RRC连接拒绝消息，可以在MME没有下行数据传输时，提前释放终端设备，相对于现有技术的释放流程，能够节省信令开销，另一方面，也能够降低终端设备的功耗。
第三方面，提供了一种终端设备，用于执行第一方面或第一方面的任意可能的实现方式中的方法。具体地，该终端设备包括用于执行第一方面或第一方面的任意可能的实现方式中的方法的单元。
第四方面，提供了一种接入网设备，用于执行第二方面或第二方面的任意可能的实现方式中的方法。具体地，该接入网设备包括用于执行第二方面或第二方面的任意可能的实现方式中的方法的单元。
第五方面，提供了一种终端设备，该终端设备包括接收器、发送器、处理器、存储 器和总线系统。其中，接收器、发送器、处理器和存储器通过总线系统相连，存储器用于存储指令，处理器用于执行存储器存储的指令，以控制接收器接收信号和控制发送器发送信号。并且当处理器执行存储器存储的指令时，执行使得处理器执行第一方面或第一方面的任意可能的实现方式中的方法。
第六方面，提供了一种接入网设备，该接入网设备包括接收器、发送器、处理器、存储器和总线系统。其中，接收器、发送器、处理器和存储器通过总线系统相连，存储器用于存储指令，处理器用于执行存储器存储的指令，以控制接收器接收信号和控制发送器发送信号。并且当处理器执行存储器存储的指令时，执行使得处理器执行第二方面或第二方面的任意可能的实现方式中的方法。
第七方面，本申请提供一种计算机可读介质，用于存储计算机程序，该计算机程序包括用于执行第一方面或第一方面的任意可能的实现方式中的方法的指令。
第八方面，提供一种计算机可读介质，用于存储计算机程序，该计算机程序包括用于执行第二方面或第二方面的任意可能的实现方式中的方法的指令。
第九方面，提供了一种数据传输方法，其特征在于，包括：终端设备向接入网设备发送第一指示，第一指示用于指示终端设备基于终端设备向接入网设备发送的第一条无线资源控制RRC信令传输数据，和/或，
第一指示用于指示接入网设备基于接入网设备向终端设备发送的第一条无线资源控制RRC信令传输数据；
基于第一条RRC信令，终端设备与接入网设备之间传输数据。
具体来讲，第一指示用于指示终端设备与接入网设备之间通过传输的第一信令携带数据，或者在传输第一信令的同时传输数据，或者在传输第一信令后紧接着传输数据。该第一信令为随机接入过程中，终端设备与接入网设备之间的第一条RRC信令。也就是说，第一指示用于指示终端设备将基于与接入网设备之间的第一条RRC信令传输上行数据，和/或，第一指示用于指示接入网设备将基于与终端设备之间的第一条RRC信令传输下行数据。
因此，根据本申请实施例的方法，基于终端设备与接入网设备之间的第一条RRC信令可以实现上行和/或下行的数据传输，而不需要建立RRC连接，从而能够节省为传输数据而建立所需承载的信令开销，并能够降低设备功耗。
在一种可能的实现方式中，基于第一条RRC信令，终端设备与接入网设备之间传输数据，包括：
通过第一条RRC信令携带数据，终端设备与接入网设备之间传输数据。
在一种可能的实现方式中，终端设备与接入网设备之间传输数据，包括：
终端设备与接入网设备之间通过非接入层协议数据单元NAS PDU传输数据；或者，
终端设备与接入网设备之间通过数据无线承载DRB传输数据。
可选地，所述数据可以通过DRB或者SRB0发送。
在本申请中，数据和第一条RRC信令可以复用一个传输块，也可以作为两个传输块分别传输。
需要说明的是，在数据和第一条RRC信令一起传输的情况下，第一条RRC信令可以携带终端设备的标识。在数据和第一条RRC信令分别传输的情况下，数据可以携带终端设备的标识或通过终端设备的标识进行加扰。
所述终端设备的标识，例如可以是小区无线网络临时标识(RadioNetworkTemporaryIdentifier，RNTI)、哈希服务临时移动用户标识(hash Serving Temporary Mobile Subscriber Identity，hashS-TMSI)、S-TMSI、截断的S-TMSI、接入的随机数、国际移动用户识别码(InternationalMobileSubscriberIdentificationNumber，IMSI)、MAC CE里携带的终端设备的标识等，本申请对终端设备的标识不做具体限定。
进一步地，若数据可以和第一条RRC信令作为两个传输块分别传输，携带数据的NAS PDU可以通过SRB 1bis或者SRB0发送，或者第一条RRC信令通过SRB 0发送且数据通过DRB发送。
在一种可能的实现方式中，第一条RRC信令为消息3或消息4。
在一种可能的实现方式中，消息3为下述任一种消息：
RRC连接请求消息、RRC连接重建立请求消息和RRC连接恢复请求消息；和/或
消息4为下述任一种消息：
冲突解决消息、RRC连接建立消息、RRC连接重建立消息和RRC连接恢复消息。
在一种可能的实现方式中，当第一指示为随机接入前导码时，终端设备向接入网设备发送第一指示，包括：
终端设备向接入网设备发送第一随机接入前导码。
在一种可能的实现方式中，终端设备向接入网设备发送第一指示，包括：
终端设备在第一随机接入资源上向接入网设备发送随机接入前导码。
在一种可能的实现方式中，在基于所述第一条RRC信令，所述终端设备与所述接入网设备之间传输所述数据之前，所述方法还包括：
所述终端设备接收系统消息，所述系统消息包括数据量信息，所述数据量信息用于指示所述终端设备基于所述第一条RRC信令所能传输的最大数据量；
其中，所述基于所述第一条RRC信令，所述终端设备与所述接入网设备之间传输所述数据，包括：
当所述终端设备确定所述数据的数据量小于或等于所述最大数据量时，基于所述第一条RRC信令，所述终端设备向所述接入网设备传输所述数据。
在一种可能的实现方式中，该方法还可以包括：
终端设备接收接入网设备发送的候选消息，候选消息包括指示信息，候选消息为RRC连接建立消息、RRC连接恢复消息，RRC连接重建立完成消息、RRC连接拒绝消息或RRC连接释放消息，指示信息用于指示终端设备保持在空闲态。
可选地，该候选消息可以是消息4。
这样，通过消息4中的指示信息，可以在没有下行数据传输时，提前释放终端设备，相对于现有技术的释放流程，能够节省信令开销，另一方面，也能够降低终端设备的功耗。
第十方面，提供了一种数据传输方法，包括：
接入网设备接收终端设备发送的第一指示，第一指示用于指示终端设备基于终端设备向接入网设备发送的第一条无线资源控制RRC信令传输数据，和/或，
第一指示用于指示接入网设备基于接入网设备向终端设备发送的第一条无线资源控制RRC信令传输数据；
基于第一条RRC信令，接入网设备与终端设备之间传输数据。
因此，根据本申请实施例的方法，基于终端设备与接入网设备之间的第一条RRC信令可以实现上行和/或下行的数据传输，而不需要建立RRC连接，从而能够节省为传输数据而建立所需承载的信令开销，并能够降低设备功耗。
在一种可能的实现方式中，基于第一条RRC信令，接入网设备与终端设备之间传输数据，包括：
通过第一条RRC信令携带数据，接入网设备与终端设备之间传输数据。
在一种可能的实现方式中，接入网设备与终端设备之间传输数据，包括：
接入网设备与终端设备之间通过非接入层协议数据单元NAS PDU传输数据；或者，
接入网设备与终端设备之间通过数据无线承载DRB传输数据。
在一种可能的实现方式中，第一条RRC信令为消息3或消息4。
在一种可能的实现方式中，消息3为下述任一种消息：
RRC连接请求消息、RRC连接重建立请求消息和RRC连接恢复请求消息；和/或
消息4为下述任一种消息：
冲突解决消息、RRC连接建立消息、RRC连接重建立消息和RRC连接恢复消息。
在一种可能的实现方式中，当第一指示为随机接入前导码时，接入网设备接收终端设备发送的第一指示，包括：
接入网设备接收终端设备发送的第一随机接入前导码。
在一种可能的实现方式中，接入网设备接收终端设备发送的第一指示，包括：
接入网设备接收终端设备在第一随机接入资源发送的随机接入前导码。
在一种可能的实现方式中，该方法还可以包括：
接入网设备向核心网设备发送NAS PDU。
可选地，所述NAS PDU可以通过获取UE信息消息(Retrieve UE Information Message)或者初始UE消息(Initial UE Message)携带。
在一种可能的实现方式中，在所述基于所述第一条RRC信令，所述接入网设备与所述终端设备之间所述传输数据之前，所述方法还包括：所述接入网设备接收所述核心网设备发送的所述NAS PDU；
其中，所述基于所述第一条RRC信令，所述接入网设备与所述终端设备之间传输数据，包括：基于所述第一条RRC信令，所述接入网设备向所述终端设备传输所述NAS PDU。
可选地，所述第一条RRC信令为UE信息发送消息(UE Information Transfer Message)或下行NAS传输消息(Downlink NAS Transport Message)。
进一步地，所述NAS PDU包括指示信息，所述指示信息用于指示所述接入网设备指示所述终端设备保存在空闲态。
在一种可能的实现方式中，该方法还可以包括：
接入网设备向终端设备发送候选消息，候选消息包括指示信息，候选消息为RRC连接建立消息、RRC连接恢复消息，RRC连接重建立完成消息、RRC连接拒绝消息或RRC连接释放消息，指示信息用于指示终端设备保持在空闲态。
第十一方面，提供了一种终端设备，用于执行第九方面或第九方面的任意可能的实现方式中的方法。具体地，该终端设备包括用于执行第九方面或第九方面的任意可能的实现方式中的方法的单元。
第十二方面，提供了一种接入网设备，用于执行第十方面或第十方面的任意可能的 实现方式中的方法。具体地，该接入网设备包括用于执行第十方面或第十方面的任意可能的实现方式中的方法的单元。
第十三方面，提供了一种终端设备，该终端设备存储器、处理器和收发器，所述存储器用于存储程序代码，所述处理器用于执行所述存储器中存储的程序代码，以执行第九方面或第九方面各种可能的实现方式中的方法所对应的操作。
第十四方面，提供了一种接入网设备，该接入网设备包括存储器、处理器和收发器，所述存储器用于存储程序代码，所述处理器用于执行所述存储器中存储的程序代码，以执行第十方面或第十方面各种可能的实现方式中的方法所对应的操作。
第十五方面，本申请提供一种计算机可读介质，用于存储计算机程序，该计算机程序包括用于执行第九方面或第九方面的任意可能的实现方式中的方法的指令。
第十六方面，提供一种计算机可读介质，用于存储计算机程序，该计算机程序包括用于执行第十方面或第十方面的任意可能的实现方式中的方法的指令。
附图说明
图1是可以应用于本申请的一个通信系统的示意图。
图2是根据本申请实施例的数据传输方法的示意性流程图。
图3是根据本申请的上行数据早传的方法的示意性流程图。
图4是根据本申请的基于CP方案的上行数据早传的方法的示意性流程图。
图5是根据本申请的基于UP方案的上行数据早传的方法的示意性流程图。
图6是根据本申请的基于CP方案的下行数据早传的方法的示意性流程图。
图7是根据本申请的基于UP方案的下行数据早传的方法的示意性流程图。
图8是根据本申请的终端设备的示意性框图。
图9是根据本申请的接入网设备的示意性框图。
图10是根据本申请另一实施例的数据传输方法的示意性流程图。
图11是消息2的一种格式的示意图。
图12是消息2的另一种格式的示意图。
图13是消息2的一种格式的示意图。
图14是消息2的再一种格式的示意图。
图15是根据本申请的另一基于CP方案的上行数据早传的方法的示意性流程图。
图16是根据本申请的另一基于UP方案的上行数据早传的方法的示意性流程图。
图17是根据本申请的另一基于CP方案的下行数据早传的方法的示意性流程图。
图18是根据本申请的另一基于UP方案的下行数据早传的方法的示意性流程图。
图19是根据本申请的另一终端设备的示意性框图。
图20是根据本申请的另一接入网设备的示意性框图。
具体实施方式
下面将结合附图，对本申请中的技术方案进行描述。
应理解，本申请的技术方案可以应用于各种通信系统，例如：全球移动通讯(Global System of Mobile communication，GSM)系统、码分多址(Code Division Multiple Access，CDMA)系统、宽带码分多址(Wideband Code Division Multiple Access，WCDMA)系 统、通用分组无线业务(General Packet Radio Service，GPRS)、长期演进(Long Term Evolution，LTE)系统、先进的长期演进(Advanced long term evolution，LTE-A)系统、通用移动通信系统(Universal Mobile Telecommunication System，UMTS)、新空口(New Radio Access Technology，NR)、5G等。
还应理解，在本申请实施例中，终端设备也可以称为终端或用户设备(User Equipment，UE)，可以包括但不限于应用于物联网中的终端设备，例如，可以是应用于NB-IoT中的终端设备(可以称为“NB-IoT终端”)：智能抄表设备、物流追踪设备、环境监测设备等；该终端还可以包括但不限于移动台(Mobile Station，MS)、移动终端(Mobile Terminal)、移动电话(Mobile Telephone)、用户设备(User Equipment，UE)、手机(handset)及便携设备(portable equipment)等，该终端设备可以经无线接入网(Radio Access Network，RAN)与一个或多个核心网进行通信，例如，终端设备可以是移动电话(或称为“蜂窝”电话)、具有无线通信功能的计算机等，终端设备还可以是便携式、袖珍式、手持式、计算机内置的或者车载的移动装置。
本申请实施例中，接入网设备也可称为无线接入网(Radio Access Network，RAN)设备，例如可以是基站、基站控制器、线网络控制器(Radio Network Controller，RNC)、发射和接收点(Transmit and Receive Point，TRP)，基站可以是GSM或CDMA中的基站(Base Transceiver Station，BTS)，也可以是WCDMA中的基站(NodeB)，还可以是LTE中的演进型基站(evolved Node B，eNB或e-NodeB)，还可以是NR或5G的基站(gNB)，本申请实施例对此不作具体限定。
本发明实施例还涉及核心网(Core Network，CN)设备，主要包括移动管理实体(Mobility Management Entity，MME)和服务网关(Serving GateWay，S-GW)。MME可能在不同的系统或不同制式的网络中有不同的名称，本申请中为了便于理解，统一描述为MME。相应地，S-GW可能在不同的系统或不同制式的网络中有不同的名称，本申请中为了便于理解，统一描述为S-GW。
图1是可以应用于本申请的一个通信系统的示意图。在图1中，终端设备可以通过一个或多个接入网设备与核心网设备进行通信。举例来说，图1中的终端设备10a可以经由接入网设备110a与核心网设备12进行通信；终端设备10b可以经由接入网设备110a或者经由接入网设备110b与核心网设备12进行通信；终端设备10c可以经由接入网设备110b与核心网设备12进行通信。进一步地，可以与公共交换电话网络(Public Switched Telephone Network，PSTN)13或者其他网络14甚至整个因特网15进行通信。
现有技术中，至少需要在RRC连接建立完成时才能够进行上下行数据传输，从而导致传输数据较晚，带来信令开销过大和浪费功耗的问题。为解决该问题，本申请提出了一种数据传输的方法，能够实现数据早传，从而能够节省功耗以及信令开销。
在介绍本申请的数据传输的方法之前，首先介绍本申请所涉及到相关术语或概念。
数据早传可以理解为，在RRC连接建立/恢复/重建立完成消息之前进行上行和/或下行的数据传输。
数据早传也可以理解为，在随机接入过程中进行的上行和/或下行的数据传输。
数据早传还可以理解为，终端设备通过与接入网设备之间第一条RRC信令进行的上行和/或下行的数据传输。
数据早传可以被看作为一种能力。终端设备支持这种数据传输方法，则该终端设备 支持这种能力，接入网设备支持终端设备使用这种方法，表明接入网设备支持这种数据早传的能力。
接入网设备在发送系统消息时，可以进行指示是否支持这种数据早传的能力。终端设备在随机接入前可以根据接收的系统消息来判断，接入网设备是否支持该能力。如果不支持，则支持该能力的终端设备且想要使用这种能力进行传输的终端设备则可以选择不进行接入该接入网设备。
示例的，系统消息中也可以指示终端设备在第一条RRC信令消息中发送的上行数据的数据量上限或阈值，或上行第一条RRC消息和上行数据的数据量上限或阈值，或除了第一条RRC信令RRC消息外允许传输上行数据的数据量上限或阈值，如20字节。终端设备若发现要发送的上行数据量超过超过系统广播的数据量上限或阈值，则终端设备可以选择正常数据传输的方式接入。若终端设备需要发送的上行数据量小于此数据量上限或阈值，则可以选择上行数据早传的方式进行发送数据。
所述系统消息，可以是SIB2，SIB22或其他系统消息。
示例的，可以在协议中规定一个默认阈值，该阈值可以指示终端设备在第一条RRC信令消息中发送的上行数据的数据量上限，或上行第一条RRC消息和上行数据的数据量上限，或除了第一条RRC信令RRC消息外允许传输上行数据的数据量上限。终端设备若发现第一条RRC信令和上行数据的数据量超过该阈值，则终端设备可以选择正常的方式接入。若终端设备需要发送的上行数据量小于该阈值，则可以选择上行数据早传的方式进行发送数据。
示例的，若终端设备支持数据早传的能力，终端设备可以根据需要发送的数据量大小或者业务类型而选择是否使用数据早传的方式来发送数据。如果终端设备选择数据早传的方式，当接入网设备分配用于传输数据的资源充足时，终端设备就以上行早传的方式来传输数据。若接入网设备分配的数据资源不足以发送终端设备需要发送的全部上行数据时，则终端设备可以选择正常数据传输流程，即先进行建立RRC连接，再发送数据，如在消息5(例如，RRC连接完成消息、RRC连接重建立完成消息等)中可以传输数据。或者终端设备先在接入网设备分配消息3的资源上先发送一部分数据，剩余数据可以在后续建立RRC连接后，再发送数据。
应理解，本申请实施例所描述的与现有协议或现有技术中相同或类似地信令或消息等，均可以参照现有技术，为了简洁，下文中将不再对这些信令或消息的所包含的内容基于具体作用等进行详细介绍。
本申请中术语“和/或”，仅仅是一种描述关联对象的关联关系，表示可以存在三种关系，例如，A和/或B，可以表示：单独存在A，同时存在A和B，单独存在B这三种情况。另外，本文中字符“/”，一般表示前后关联对象是一种“或”的关系。
此外，可以理解的，本申请中术语“第一”和“第二”仅仅是为了描述和理解的方便，不应对本申请实施例构成任何限定。
下面，结合图2详细介绍本申请的数据传输的方法。应理解，图2示出了该方法的详细的通信步骤或操作，但这些步骤或操作仅是示例，本申请实施例还可以执行其它操作或者图2中的各种操作的变形。此外，图2中的各个步骤可以分别按照与图2所呈现的不同的顺序来执行，并且有可能并非要执行图2中的全部操作。
图2是本申请一个实施例的数据传输的方法的示意性流程图。
S210，终端设备向接入网设备发送第一指示。相应地，接入网设备接收所述第一指示。
具体地，所述第一指示用于指示在无线资源控制RRC连接建立完成前需要传输数据。从而，接入网络设备根据第一指示能够确定需要在RRC连接建立完成前需要数据，例如，能够确定终端设备需要进行上行数据早传，或者可以确定终端设备进行下行数据早传。
应理解，上行数据早传表示在无线资源控制RRC连接建立完成前需要传输上行数据。下行数据早传表示在无线资源控制RRC连接建立完成前需要传输下行数据。
在一种可能的实现方式中，通过消息1来区分上行数据早传和下行数据早传，可以及时通知接入网设备，避免接入网设备不清楚终端设备是想进行上行数据早传还是下行数据早传，使得当需要上行数据早传时向终端设备发送随机接入响应时分配较大的上行资源分配(UL Grant)或者多个UL Grant，而下行早传时，不需要分配较大的UL Grant或者多个UL Grant。
可选地，终端设备可以通过消息3(Msg3)向所述接入网设备发送第一指示，也就是说，Msg3可以包括第一指示。该指示信息用于指示需要进行下行早传，也就是在RRC连接建立完成前接收下行数据。这种方式的指示用于当没有使用消息1来区分上行和下行时，可以在消息3进行指示该终端设备想要进行下行数据早传。
进一步地，Msg3可以是下述任一种消息：RRC连接请求消息、RRC连接重建立请求消息和RRC连接恢复请求。
进一步地，所述RRC连接请求消息或所述RRC连接重建立请求消息携带可以包括需要传输的数据的非接入层协议数据单元NAS PDU。即可以通过RRC连接请求消息或所述RRC连接重建立请求消息中的NAS PDU发送上行数据。
可选地，第一指示可以是专用的前导码(例如，记作第一随机接入前导码)，在此情况下，作为S210的一个实施例：终端设备向接入网设备发送第一随机接入前导码。该第一随机接入前导码用于指示上行数据早传或下行数据早传。
可选地，作为S210的另一实施例，终端设备可以特定的资源(例如，记作第一随机接入资源)上向所述接入网设备发送随机接入前导码，从而指示上行数据早传或下行数据早传。
可选地，终端设备可以通过时频码进行指示数据早传。例如终端设备使用特定的时频码资源(例如，第一时频码资源)发送随机接入请求消息，则表示终端设备要进行上行数据早传，终端设备使用另一种时频码资源则(例如，第二时频码资源)表示终端设备要进行下行数据早接收。其中，时频码可以为时域，频域，码域的任一种组合，如不同的时频资源，不同的码域资源，不同的时频码资源等等。
可选地，终端设备在连接态时，接入网设备也可以通过物理下行控制信道(PhysicalDownlink Control Channel，PDCCH)命令向所述终端设备发送指示，用于指示UE需要进行数据早传的随机接入，如上行数据早传或者下行数据早传。即通过PDCCHorder方式进行随机接入。具体的指示信息可以通过DCI来承载。
S220，终端设备在RRC连接建立完成前，与接入网设备之间传输数据。
可选地，终端设备可以在RRC连接建立完成前，通过与接入网设备之间传输非接入层协议数据单元NAS PDU，传输数据。
可选地，终端设备还可以在RRC连接建立完成前，与所述接入网设备之间通过数据 无线承载DRB传输数据。
因此，根据本申请实施例的方法，能够在RRC建立完成前传输数据(包括上行数据和下行数据)，从而能够节省为传输数据而建立所需承载的信令开销，并能够降低设备功耗。
以下，分别针对上行数据早传和下行数据早传，分别描述根据本申请实施例的数据传输方法。
图3是本申请一个实施例的数据传输的方法的示意性流程图。图3所示的方法适用于上行数据早传。
S310，终端设备向接入网设备发送随机接入前导码。或者称，终端设备向接入网设备发送随机接入请求消息，即消息1(Msg1)。
可选地，终端设备可以在特定的资源(例如，记作随机接入资源#A)上发送Msg1。随机接入资源#A可以用于指示上行数据早传或下行数据早传。
可选地，终端设备也可以发送专用的前导码(例如，记作随机接入前导码#A)。随机接入前导码#A也可以用于指示上行数据早传或下行数据早传。
应理解，随机接入资源#A为第一随机接入资源的一个示例，也可以为其他示例如时频码的一种组合，随机接入前导码#A为第一随机接入前导码的示例。
S320，接入网设备接收到Msg1后，向终端设备发送随机接入响应消息。即接入网设备发送消息2(Msg2)。
Msg2携带上行定时(Timing Advance,TA)和上行资源分配(UL Grant)。其中，UL Grant是接入网设备分配给终端设备，用于终端设备传输消息3(Msg3)的资源，关于TA和UL Grant具体可以参照现有技术，此处不做详细介绍。
可选地，在本申请实施例中，接入网设备可以根据时频码资源信息如第一随机接入前导码或第一随机接入资源，获知UE想要进行数据早传，如果是上行数据早传，则向终端设备分配用于传输上行数据的资源。接入网设备向终端设备分配的用于传输上行数据的资源和UL Grant一起，称为目标资源。其中接入网设备分配的目标资源可以是用于传输消息3和上行数据的一个大的上行资源，也可以是两个独立的资源，一个用于传输消息3，一个用于传输上行数据。
进一步地，目标资源的大小可以是固定的，比如100字节(bytes)。该目标资源的大小也可以是接入网设备根据第一随机接入资源或第一随机接入前导码确定的，也就是说，第一随机接入资源或第一随机接入前导码还可以用于指示上行数据的大小，从而接入网设备能够根据上行数据的大小合理分配用于传输上行数据的资源。也就是说，在指示上行早传的基础上，可以进一步的根据接入资源区分需要分配的资源大小。
S330，终端设备根据Msg2，向接入网设备发送Msg3和上行数据。
应理解，Msg3可以和上行数据一起传输，也可以分别传输。在Msg3和上行数据一起传输的情况下，Msg3可以携带终端设备的标识。在Msg3和上行数据分别传输的情况下，上行数据可以携带终端设备的标识或通过终端设备的标识进行加扰。
所述终端设备的标识，例如可以是(RadioNetworkTemporaryIdentifier，RNTI)--小区无线网络临时标识、哈希服务临时移动用户标识(hash Serving Temporary Mobile Subscriber Identity，hashS-TMSI)、S-TMSI、截断的S-TMSI、接入的随机数、国际移动用户识别码(InternationalMobileSubscriberIdentificationNumber，IMSI)、MAC CE里携 带的终端设备的标识等，本申请对终端设备的标识不做具体限定。
可选地，终端设备接收到Msg2后，如果有上行数据需要传输，可以在传输Msg3的同时，在预先配置的或者预留的用于上行数据早传的资源上传输上行数据。
可选地，终端设备也可以在Msg2所指示的目标资源上同时传输Msg3和上行数据。
作为Msg3的一个实施例，Msg3可以为RRC连接请求消息或RRC连接重建立请求消息，所述RRC连接请求消息或所述RRC连接重建立请求消息包括携带包括所述上行数据的非接入层协议数据单元NAS PDU。从而，能够通过控制面优化方案(Control plane CIoT EPS optimisation,CP)实现上行数据早传。
进一步地，Msg3和上行数据分开传输时，该NAS PDU可以通过承载信令无线承载(Signal Radio Bearer，SRB)1bits发送。这个承载NAS PDU的消息为上行直传消息(UL information Transfer)，这样接入网设备可以根据相应的逻辑信道标识(Identity，ID)获知这是使用CP的终端设备。
应理解，RRC连接请求消息和RRC连接重建立请求消息都是Msg3的一种，RRC连接请求消息用于建立RRC连接，RRC连接重建立请求消息用于重建立RRC连接。对于RRC连接请求消息和RRC连接重建立请求消息具体地可以参照现有技术，本申请不作具体介绍。
作为Msg3的另一实施例，Msg3可以为RRC连接请求消息，RRC连接恢复请求消息或RRC连接重建立请求消息，所述上行数据是通过数据无线承载DRB发送的。从而，能够通过用户面优化方案(User plane CIoT EPS optimisation，UP)实现上行数据早传。同样，该数据可以和消息3一起发送给接入网设备，也可以分开发送。
应理解，这里的RRC连接恢复请求消息或RRC连接重建立请求消息用于在接入网设备释放RRC连接后，重新恢复RRC连接，具体地可以参照现有技术，本申请不作具体介绍。
S340，接入网设备向MME或S-GW发送所述上行数据。
综上，在本申请的一种数据传输方法中，如果接入网设备均支持数据早传的能力，则可以通过预留资源的形式，使得终端设备在有上行数据早传的需求时，在发送Msg3的同时通过预留资源同时发送上行数据。在此情况下，终端设备可以通过Msg1指示接入网设备，该终端设备需要进行上行数据早传，也可以不向接入网络设备指示该终端设备数据早传的需求。
在本申请的另一种数据传输方法中，如果接入网设备均支持数据早传的能力，接入网设备可以在终端设备需要进行上行数据早传时，例如通过随机接入资源#A或随机接入前导码#A知道终端设备需要进行上行数据早传时，向终端设备分配用于传输上行数据的资源，例如目标资源，从而使得终端设备可以在传输Msg3的同时通过接入网设备分配的资源同时发送上行数据。
因此，根据本申请实施例的数据传输方法，能够实现上行数据早传，从而能够节省功耗以及信令开销。
下面，结合图4和图5，分别描述基于CP方案和UP方案的数据传输方法。应理解，对于图4和图5中所示出的与图2相同或相应地步骤可以参照上文对图2的描述，为了避免重复，在对图4和图5进行介绍时，将不再对相同或相应地内容进行详细描述。
图4根据本申请实施例的基于CP方案的上行数据早传的示意性流程图。
S410，终端设备向接入网设备发送Msg1。
S420，接入网络设备接收到Msg1后，向终端设备发送Msg2。
S430，终端设备向接入网设备发送RRC连接请求消息或RRC连接重建立请求消息，所述RRC连接请求消息或所述RRC连接重建立请求消息携带包括所述上行数据的NASPDU。
可选的，接入网设备可以保存CP方案的终端设备能力信息，接入网设备收到消息3后，可以根据S-TMSI，找到接入网设备存储该终端设备的能力信息，然后接入网设备可以判断出终端设备是否具有数据早传的能力，如果终端设备不具有该能力，可以将连接拒绝或者回退到正常的流程。
其中，有一种异常情况需要处理，当MME对该终端设备重新分配S-TMSI时或终端设备的S-TMSI改变时，接入网设备并不知道因为S-TMSI是通过NAS信息传输更改的，所以接入网设备保存的信息(如从UE信息传输(UE Information Transfer)消息中获得的信息)并不匹配保存的该终端设备更新后的S-TMSI。因此，当终端设备发送消息3中携带的S-TMSI有可能是之前其他终端设备使用的S-TMSI，这样接入网设备存储的终端设备能力，终端设备服务质量(Quality of Service，Qos)信息将会出现对应错误的情况，因此，提出以下几种解决方案：
a：MME重新对某个终端设备分配S-TMSI时，通知接入网设备，则接入网设备可将对应这个S-TMSI存储的信息，包括能力信息等删除或者通知接入网设备新分配的S-TMSI，接入网设备接收到后则更新S-TMSI，使得终端设备新的S-TMSI能够匹配终端设备的相关信息。通知消息为一条S1AP消息，如下行NAS传输消息，连接建立指示消息等。即下行NAS传输消息携带S-TMSI用于更新S-TMSI以对应之前从UE信息传输消息里收到的终端设备的相关信息。
b：为保证切换接入网设备时，旧的接入网设备能够删除该消息以防重新分配的问题，MME在重新分配S-TMSI时，会通知终端设备最近接入的几个接入网设备，使得它们能及时更新S-TMSI或者通知终端设备最近接入的几个接入网设备删除存贮的旧S-TMSI和与其对应的终端设备相关信息，如UE Qos，终端设备无线电能力等。
c：接入网设备和MME会有个定时器，当接入网设备获得S-TMSI，对应该S-TMSI有该终端设备的上下文。接入网设备启动该定时器，当定时器溢出时，则删除相关上下文。MME也有个定时器，当分配了一个S-TMSI后，则启动，在定时器溢出前，不能将该S-TMSI分配给其他终端设备。
S440，所述接入网设备向所述MME发送获取UE信息消息(Retrieve UE Information Message)，所述获取终端设备信息消息包括所述上行数据，也可以为其他消息名称，具体信令名称不限。
此时，MME即可获得终端设备的上行数据，实现上行数据早传。
可选地，获取终端设备信息消息还包括请求下行数据指示信息，该方法还可以包括：
S450，如果MME有下行数据，则MME向接入网设备发送UE信息发送消息(UE Information Transfer)，所述用户信息发送消息包括下行数据，也可以为其他消息名称，具体信令名称不限；
S460，接入网设备向终端发送所述下行数据。
可选地，该方法还可以包括：
S470，接入网设备向所述终端设备发送释放消息，所述释放消息用于将所述终端设备释放到空闲态。
可选地，所述释放消息可以为RRC连接建立消息、RRC连接重建立消息、RRC连接恢复，RRC连接拒绝消息或RRC连接释放消息。
进一步地，若接入网设备发送RRC连接建立消息或RRC连接重建立消息、RRC连接恢复，该消息可以包括RRC连接释放里的相关信息，用于释放该终端设备的连接，具体可以包括释放原因，重定向指示等；
若接入网设备发送RRC连接拒绝消息，则也可以携带一个指示信息，如原因值，用于表示将终端设备释放到空闲态；
若接入网设备发送RRC连接释放消息并携带终端设备的标识信息，可以在RRC消息中也可以加一个承载该标识的MAC CE，则直接将终端设备释放到空闲态。也可以在终端设备向接入网设备发送消息5，如RRC连接建立完成后，接入网设备向终端设备发送RRC连接释放消息。
可选地，作为S460的一个具体实施例，接入网设备可以通过S370中的释放消息向终端设备发送下行数据。也就是说，所述下行数据可以携带在该释放消息中。进一步的，该下行数据为封装在NAS PDU中的数据。
可选地，S470也可以发送在MME没有下行数据传输的场景下，即若MME没有下行数据需要传输，则接入网设备可以通过向终端设备发送释放消息，将终端设备释放到空闲态。
通过RRC连接建立消息、RRC连接重建立消息、RRC连接恢复或RRC连接拒绝消息，可以在MME没有下行数据传输时，提前释放终端设备，相对于现有技术的释放流程，能够节省信令开销，另一方面，也能够降低终端设备的功耗。
图5是根据本申请实施例的基于UP方案的上行数据早传的示意性流程图。
S510，终端设备向接入网设备发送Msg1。
S520，接入网络设备接收到Msg1后，向终端设备发送Msg2。
S530，终端设备向接入网络设备发送RRC连接建立请求或RRC连接恢复请求消息或RRC连接重建立请求消息。
所述上行数据可以通过数据无线承载DRB发送。上行数据需要加密，密钥可以通过上次连接获得下一跳链计算(next hop chaining count，NCC)来更新。
S540，接入网设备向MME发送第二请求消息。
可选地，第二请求消息中的内容可以和终端设备上下文恢复请求消息中的内容相同。
进一步地，第二请求消息可以是终端设备上下文恢复请求消息。
接入网设备在接收到RRC连接恢复请求消息或RRC连接重建立请求消息后，根据短完整性消息验证码(short Message Authentication Code for Integrity，short-MAC-I)进行验证终端设备。若所接入网设备不是原来的接入网设备，则需要通过X 2口将short-MAC-I发送给源接入网设备，并由源接入网设备进行校验，成功后，将终端设备的上下文信息发送给当前的接入网设备，并进行后续的操作。S550，MME根据所述第二请求消息向接入网设备发送第二响应消息。
可选地，第二响应消息中的内容可以和终端设备上下文恢复响应消息中的内容相同。
进一步地，第二响应消息为终端设备上下文恢复响应消息。
若接入网设备收到的响应消息发现接入网设备所收到的数据对应的无线接入承载(E-UTRAN radio access bearer，E-RAB)被拒绝了，则接入网设备将发送RRC连接恢复消息或RRC连接建立消息给终端设备，该消息可以包含一条指示信息，该指示信息用于指示数据E-RAB被拒绝传输或者传输失败或者指示终端设备需要将之前发送的数据包重新发送。接入网设备额外分一个ULgrant用于该数据传输。
S560，接入网设备收到第二响应消息，向所述S-GW发送所述上行数据。
此时，S-GW即可获得终端设备的上行数据，实现上行数据早传。
可选地，该方法还可以包括：
S570，接入网设备成功发送完上行数据后，可以向MME发送终端设备上下文释放请求消息或终端设备上下文挂起请求消息；
S580，MME根据终端设备上下文释放请求消息向接入网设备发送终端设备上下文释放命令消息，或MME根据上下文挂起请求消息向接入网设备发送终端设备上下文挂起完成消息；
S590，接入网设备根据所述终端设备上下文释放命令消息或所述终端设备上下文挂起完成消息，向所述终端设备发送所述释放消息，所述释放消息用于将所述终端设备释放到空闲态。
可选地，这里的释放消息可以是RRC连接建立消息、RRC连接恢复消息，RRC连接重建立消息、RRC连接拒绝消息或RRC连接释放消息。
进一步地，若接入网设备发送RRC连接建立消息或者RRC连接重建立消息或RRC连接恢复消息，该消息可以包括RRC连接释放里的相关信息，用于释放该终端设备的连接，具体可以包括释放原因，重定向指示等；
若接入网设备发送RRC连接拒绝消息，则也可以携带一个指示信息，如原因值，表示将终端设备释放到空闲态；
若接入网设备发送RRC连接释放消息，则直接将终端设备释放到空闲态。
若此过程中接入网设备也接收到下行数据，则可以和释放消息一起发送给终端设备。
通过RRC连接建立消息、RRC连接恢复消息，RRC连接重建立完成消息、RRC连接拒绝消息或RRC连接释放消息，可以在S-GW没有下行数据传输时，提前释放终端设备，相对于现有技术的释放流程，能够节省信令开销，另一方面，也能够降低终端设备的功耗。
图6是根据本申请另一实施例基于CP方案的数据传输方法。图6所示的方法适用于下行数据早传。
S610，终端设备向接入网设备发送随机接入前导码。或者称，终端设备向接入网设备发送随机接入请求消息，即消息1(Msg1)。具体地，可以参照现有技术，为了简洁，此处不再赘述。
S620，接入网络设备接收到Msg1后，向终端设备发送随机接入响应消息。即接入网设备发送消息2(Msg2)。
Msg2携带TA和UL Grant。其中，UL Grant是接入网设备分配给终端设备，用于终端设备传输消息3(Msg3)的资源，关于TA和UL Grant具体可以参照现有技术，此处不做详细介绍。
S630，终端设备向接入网设备发送Msg3，所述Msg3可以包括服务请求消息(Service  Request Message)。
若下行早传没有通过消息1，或者时频码资源来区分情况下，可以在消息3中进行指示，指示是UE要进行下行数据早传，即在RRC连接建立完成前进行下行数据传输，则接入网设备接收该指示消息后，可较早触发与核心网设备的信令交互。
可选地，Msg3可以是RRC连接请求消息或RRC连接重建立请求消息。
S640，接入网设备在接收到Msg3后，向MME发送请求消息。
该消息可以为获取UE信息消息，也可以为其他消息。
S650，MME根据收到请求消息后，向接入网设备发送所述下行数据。
可选地，MME可以通过UE信息传输消息向接入网设备发送所述下行数据。即，UE信息传输消息可以携带所述下行数据。
S660，接入网设备向所述终端设备发送所述下行数据。
可选地，接入网设备可以通过释放消息，向终端设备发送所述下行数据。同时终端设备在接收到释放消息后，可以进入空闲态。
可选地，这里的释放消息可以是RRC连接建立消息、RRC连接恢复消息，RRC连接重建立消息、RRC连接拒绝消息或RRC连接释放消息。
进一步地，若接入网设备发送RRC连接建立消息或者RRC连接重建立消息或RRC连接恢复消息，该消息可以包括RRC连接释放里的相关信息，用于释放该终端设备的连接，具体可以包括释放原因，重定向指示等；
若接入网设备发送RRC连接拒绝消息，则也可以携带一个指示信息，如原因值，表示将终端设备释放到空闲态；
若接入网设备发送RRC连接释放消息，则直接将终端设备释放到空闲态。
通过RRC连接建立消息、RRC连接恢复消息，RRC连接重建立消息、RRC连接拒绝消息或RRC连接释放消息，可以在MME没有下行数据传输时，提前释放终端设备，相对于现有技术的释放流程，能够节省信令开销，另一方面，也能够降低终端设备的功耗。
因此，根据本申请实施例的数据传输方法，能够实现上行数据早传，从而能够节省功耗以及信令开销。
图7是根据本申请另一实施例基于UP方案的数据传输方法。图7所示的方法适用于下行数据早传。
图7是本申请一个实施例的数据传输的方法的示意性流程图。
S710，终端设备向接入网设备发送随机接入前导码。或者称，终端设备向接入网设备发送随机接入请求消息，即消息1(Msg1)。具体地，可以参照现有技术，为了简洁，此处不再赘述。
S720，接入网络设备接收到Msg1后，向终端设备发送随机接入响应消息。即接入网设备发送消息2(Msg2)。
Msg2携带TA和UL Grant。其中，UL Grant是接入网设备分配给终端设备，用于终端设备传输消息3(Msg3)的资源，关于TA和UL Grant具体可以参照现有技术，此处不做详细介绍。
S730，终端设备根据Msg2，向接入网设备发送Msg3，所述Msg3可以包括服务请求消息(Service Request Message)。
若下行早传没有通过消息1，或者时频码资源来区分情况下，可以在消息3中进行指示，指示是下行数据早传，即在RRC连接建立完成前进行下行数据传输，则接入网设备接收该指示消息后，可较早触发与核心网设备的信令交互，可参见S740及之后的操作。
可选地，Msg3可以是RRC连接请求或RRC连接恢复请求消息或RRC连接重建立请求消息。
S740，接入网设备在接收到Msg3中的服务请求消息后，向MME发送所述服务请求消息。
可选地，接入网设备可以通过终端设备上下文恢复请求消息向MME发送所述服务请求消息。
S750，MME根据所述服务请求消息，向接入网设备发送服务响应消息。
可选地，MME可以在接收到接入网设备发送的终端设备上下文恢复请求消息后，向终端设备上下文恢复响应消息。
S760，MME向S-GW发送修改承载请求消息；
S770，S-GW向MME回复修改承载响应消息。从而S-GW能够获得所述接入网设备的地址。
S780，S-GW向接入网设备发送所述下行数据。
S790，接入网设备向终端设备发送所述下行数据。
可选地，在S600之前，接入网设备接收到S-GW发送的下行数据后，该方法还可以包括：
接入网设备向MME发送终端设备上下文释放请求消息或终端设备上下文挂起请求消息；
MME根据终端设备上下文释放请求消息向接入网设备发送终端设备上下文释放命令消息，或MME根据上下文挂起请求消息向接入网设备发送终端设备上下文挂起完成消息；
接入网设备根据所述终端设备上下文释放命令消息或所述终端设备上下文挂起完成消息，向所述终端设备发送所述释放消息，所述释放消息用于将所述终端设备释放到空闲态。
可选地，这里的释放消息可以是RRC连接建立消息、RRC连接恢复消息，RRC连接重建立消息、RRC连接拒绝消息或RRC连接释放消息。释放的具体信息可参见其他实施例。
进一步地，若接入网设备发送RRC连接建立消息，该消息可以包括RRC连接释放里的相关信息，用于释放该终端设备的连接，具体可以包括释放原因，重定向指示等；
若接入网设备发送RRC连接拒绝消息，则也可以携带一个原因值进行发送，原因值表示将终端设备释放到空闲态；
若接入网设备发送RRC连接释放消息，则直接将终端设备释放到空闲态。
可选地，在S790中，接入网设备可以通过所述释放消息向终端设备发送所述下行数据。
通过RRC连接建立消息、RRC连接恢复消息，RRC连接重建立完成消息、RRC连接拒绝消息或RRC连接释放消息，可以在S-GW没有下行数据传输时，提前释放终端设备，相对于现有技术的释放流程，能够节省信令开销，另一方面，也能够降低终端设备 的功耗。
因此，根据本申请实施例的数据传输方法，能够实现上行数据早传，从而能够节省功耗以及信令开销。
可选地，在一种可能的实现中，当UE接收寻呼消息时，寻呼消息里可以包括一个指示信息，指示UE可以进行下行数据早收操作，这样UE就可以按照下行数据早收操作来进行后续流程，进一步的核心网设备可以在发送给基站的寻呼消息携带一个指示信息，用于指示UE需要进行下行数据早收操作。
可选地，终端设备在连接态时，接入网设备也可以通过物理下行控制信道(PhysicalDownlink Control Channel，PDCCH)命令向所述终端设备发送指示，用于指示UE需要进行数据早传的随机接入，如上行数据早传或者下行数据早传。即通过PDCCHorder方式进行随机接入。具体的指示信息可以通过DCI来承载，或者接入网设备指示的UE接入的资源位置是用于数据早传的的资源位置来实现数据早传。这样在连接态，接入网设备可以通过PDCCH指示UE使用数据早传的方式
图8示出了本申请实施例的终端设备800的示意性框图。如图8所示，该终端设备800包括：处理单元810和收发单元820。
处理单元810，用于生成第一指示，所述第一指示用于指示在无线资源控制RRC连接建立完成前需要传输数据。
收发单元820，用于向接入网设备发送第一指示，所述第一指示用于指示在无线资源控制RRC连接建立完成前需要传输数据；
并在所述RRC连接建立完成前，与所述接入网设备之间传输数据。
可选地，当所述第一指示为随机接入前导码时，收发单元820具体用于：向所述接入网设备发送第一随机接入前导码。
可选地，收发单元820具体用于：在第一随机接入资源上向所述接入网设备发送随机接入前导码。
可选地，收发单元820具体用于：向所述接入网设备发送包括第一指示的消息3，其中所述消息3为下述任一种消息：
RRC连接请求消息、RRC连接重建立请求消息和RRC连接恢复请求，其中，所述RRC连接请求消息或所述RRC连接重建立请求消息携带包括需要传输的数据的非接入层协议数据单元NAS PDU。
可选地，所述第一指示用于指示在无线资源控制RRC连接建立完成前需要传输数据，包括：
所述第一指示用于指示在所述RRC连接建立完成前需要传输下行数据。
可选地，收发单元820具体用于：在所述RRC连接建立完成前，与所述接入网设备之间传输非接入层协议数据单元NAS PDU；或者，
在所述RRC连接建立完成前，与所述接入网设备之间通过数据无线承载DRB传输数据。
可选地，收发单元820具体用于：接收所述接入网设备发送的释放消息，所述释放消息为无线资源控制RRC连接建立消息、RRC连接恢复消息，RRC连接重建立完成消息、RRC连接拒绝消息或RRC连接释放消息，所述释放消息用于将所述终端设备释放到空闲态。
应理解，处理单元810可以由处理器实现，收发单元820可以由收发器实现。
还应理解，该终端设备800可以对应上述方法中描述的终端设备，并且，该终端设备800中各模块或单元分别用于执行图2至图7所示方法实施例中终端设备所执行的各动作或处理过程，这里，为了避免赘述，省略其详细说明。
图9示出了本申请实施例的接入网设备900的示意性框图。如图9所示，该接入网设备900包括：处理单元910和收发单元920。
收发单元920，用于接收终端设备发送的第一指示，所述第一指示用于指示在无线资源控制RRC连接建立完成前需要传输数据；
所述处理单元910，用于确定当前状态为是否为所述RRC连接建立完成前；
所述收发单元920，用于在所述处理单元910确定所述RRC连接建立完成前，与所述终端设备之间传输数据。
可选地，当所述第一指示为随机接入前导码时，收发单元920具体用于：接收所述终端设备发送的第一随机接入前导码。
可选地，收发单元920处理单元910：接收所述终端设备在第一随机接入资源发送的随机接入前导码。
可选地，收发单元920处理单元910：接收所述终端设备发送的包括第一指示的消息3，其中所述消息3为下述任一种消息：
RRC连接请求消息、RRC连接重建立请求消息和RRC连接恢复请求，其中，所述RRC连接请求消息或所述RRC连接重建立请求消息携带包括需要传输的数据的非接入层协议数据单元NAS PDU。
可选地，所述第一指示用于指示在无线资源控制RRC连接建立完成前需要传输数据，包括：
所述第一指示用于指示在所述RRC连接建立完成前需要传输下行数据。
可选地，收发单元920处理单元910：在所述RRC连接建立完成前，与所述终端设备之间传输非接入层协议数据单元NAS PDU；或者，
在所述RRC连接建立完成前，与所述终端设备之间通过数据无线承载DRB传输数据。
可选地，收发单元920处理单元910：向所述终端设备发送释放消息，所述释放消息为无线资源控制RRC连接建立消息、RRC连接恢复消息，RRC连接重建立完成消息、RRC连接拒绝消息或RRC连接释放消息，所述释放消息用于将所述终端设备释放到空闲态。
应理解，处理单元910可以由处理器实现，收发单元920可以由收发器实现。
还应理解，该接入网设备900可以对应上述方法中描述的接入网设备，并且，该接入网设备900中各模块或单元分别用于执行图2至图7所示方法实施例中接入网设备所执行的各动作或处理过程，这里，为了避免赘述，省略其详细说明。
图10是本申请另一实施例的数据传输方法的示意性流程图。应理解，图10示出了该方法的详细的通信步骤或操作，但这些步骤或操作仅是示例，本申请实施例还可以执行其它操作或者图10中的各种操作的变形。此外，图10中的各个步骤可以分别按照与图10所呈现的不同的顺序来执行，并且有可能并非要执行图10中的全部操作。
S1010，终端设备向接入网设备发送第一指示。相应地，接入网设备接收所述第一指 示。
其中，该第一指示用于指示终端设备基于终端设备向所述接入网设备发送的第一条无线资源控制RRC信令传输数据(即，上行数据)，和/或，第一指示用于指示接入网设备基于接入网设备向终端设备发送的第一条无线资源控制RRC信令传输数据(即，下行数据)。具体来讲，第一指示用于指示终端设备与接入网设备之间通过传输的第一信令携带数据，或者在传输第一信令的同时传输数据，或者在传输第一信令后紧接着传输数据。该第一信令为随机接入过程中，终端设备与接入网设备之间的第一条RRC信令。也就是说，第一指示用于指示终端设备将基于与接入网设备之间的第一条RRC信令传输上行数据，和/或，第一指示用于指示接入网设备将基于与终端设备之间的第一条RRC信令传输下行数据。
以下，为了便于描述和理解，将终端设备向接入网设备发送的第一条RRC信令记作RRC信令#1，将接入网设备向终端设备发送的第一条RRC信令记作RRC信令#2。
相应地，终端设备可以基于RRC信令#1向接入网设备发送上行数据，接入网设备可以基于RRC信令#2向终端设备发送下行数据。也就是说，终端设备可以基于RRC信令#1进行上行数据早传，接入网设备可以基于RRC信令#2进行下行数据早传。
可选地，RRC信令#1可以是消息3(Msg3)。
Msg3，例如可以是RRC连接请求消息、RRC连接重建立请求消息或RRC连接恢复请求消息。
关于RRC连接请求消息、RRC连接重建立请求消息以及RRC连接恢复请求消息，具体地可以参照现有技术，为了简洁，此处不再赘述。
此外，RRC信令#1也可以是新定义的在随机接入过程中终端设备向接入网设备发送的第一条RRC信令(例如，记作RRC连接数据传输消息)。其中，RRC连接数据传输消息为不需要做RRC连接管理的消息。该RRC连接数据传输消息可以是消息2(Msg2，即，随机接入响应消息)后的第一条消息。
进一步的，RRC信令#1还可以携带释放辅助指示信息(Release Assistance Indication，RAI)，用于指示短时间内没有上行数据。终端设备根据该释放辅助指示信息，保持在RRC空闲状态。
进一步的，若数据通过NAS消息来传递，在发送该数据时，也可以在NAS消息中携带释放辅助指示信息(Release Assistance Indication，RAI)，该指示消息可以向核心网设备指示是否将有上行数据或者下行数据，或者只是对该上行数据的接收确认或者响应。
以下，为了便于理解，不失一般性地，以RRC信令#1为消息3为例，描述本申请的数据传输的方法。
可选地，终端设备可以通过发送消息1(Msg1)，即随机接入请求消息，向接入网设备发送第一指示。即，消息1或消息1中的信息可以用于指示上行数据早传或下行数据早传。
例如，消息1中的前导码(或称作，前导序列)可以用于指示上行数据早传和/或下行数据早传。比如，若消息1中的前导码为前导码#2，则指示上行数据早传；若消息1中的前导码为前导码#3，则指示下行数据早传；若消息1中的前导码为前导码#3，则同时指示上行数据早传和下行数据早传。
例如，终端设备可以在特定的资源上向所述接入网设备发送消息1，通过该特定的资 源指示上行数据早传和/或下行数据早传。该特定的资源，可以是时频码资源。比如，终端设备使用时频码资源#2发送消息1，则表示终端设备要进行上行数据早传，终端设备使用时频码资源#3表示终端设备要进行下行数据早传。其中，时频码可以为时域，频域，码域的任一种组合。
此外，在上行数据早传的场景下，示例性的，接入网设备在通过消息2(Msg2)，即，随机接入响应消息，向终端设备分配发送RRC信令#1所使用的时频资源的同时，还可以同时分配发送上行数据的时频资源。
图11至图14示出了消息2的几种格式，本申请中，消息2可以采用其中任一种格式。
如图11至图14所示的消息2的格式，均包括上行定时控制字段(Timing Advance Command，TAC)和临时小区无线网络临时标识字段(TC-RNTI)。其中，上行定时控制字段中的值表示时间提前调整量，用于终端设备进行上行同步。无线网络临时标识字段中的值表示接入网设备为终端设备分配的在小区内的唯一标识。时间提前调整量和C-RNTI具体可以参照现有技术，本文中不再进行详细介绍。
TC-RNTI，例如可以是RNTI、hashS-TMSI、S-TMSI、截断的S-TMSI、接入的随机数、IMSI、MAC CE里携带的终端设备的标识等，本申请对终端设备的标识不做具体限定。
下面，分别对图11至图14所示的消息2的格式进行详细介绍。
图11是消息2的一种格式的示意图。如图11所示，预留字段(R)中的值用于指示消息2中所包括的上行资源分配字段(UL Grant)的个数。例如，当预留字段中的值为1时，表示消息2中包括2个上行资源分配字段(分别记作UL Grant#1和UL Grant#2)，UL Grant#1和UL Grant#2不相邻。其中，UL Grant#1中的值用于指示发送RRC信令#1所使用的时频资源，UL Grant#2中的值用于指示发送上行数据的时频资源。
应理解，图11中示出的消息2中的各字段所占用的比特(bit)数仅是一种示例，本申请并不对消息2中的各字段所占用的比特数作具体限定。比如，图12示出的UL Grant#1和UL Grant#2分别占用20比特和16比特，在实际应用中，UL Grant#1和UL Grant#2也可以分别占用16比特和20比特，或者均占用16比特。
图12是消息2的另一格式的示意图。如图12所示，预留字段(R)中的值用于指示消息2中所包括的上行资源分配字段(UL Grant)的个数。例如，当预留字段中的值为1时，表示消息2中包括2个上行资源分配字段(分别记作UL Grant#1和UL Grant#2)，UL Grant#1和UL Grant#2相邻。其中，UL Grant#1中的值用于指示发送RRC信令#1所使用的时频资源，UL Grant#2中的值用于指示发送上行数据的时频资源。
应理解，图12中示出的消息2中的各字段所占用的比特数仅是一种示例，本申请并不对消息2中的各字段所占用的比特数作具体限定。比如，图12示出的UL Grant#1和UL Grant#2分别占用20比特和16比特，在实际应用中，UL Grant#1和UL Grant#2也可以分别占用16比特和20比特，或者均占用16比特。
图13是消息2的另一格式的示意图。如图13所示，预留字段(R)中的值用于指示上行资源分配字段(UL Grant)所指示的时频资源的作用。例如，当预留字段中的值为1时，表示UL Grant字段所指示的时频资源用于传输RRC信令#1和上行数据；当预留字段中的值为0时，表示UL Grant中的值所指示的时频资源仅用于传输RRC信令#1。或 者当预留字段中的值为0时，表示UL Grant字段所指示的时频资源用于传输RRC信令#1和上行数据；当预留字段中的值为1时，表示UL Grant中的值所指示的时频资源仅用于传输RRC信令#1。应理解，图13中示出的消息2中的各字段所占用的比特数仅是一种示例，本申请并不对消息2中的各字段所占用的比特数作具体限定。比如，图13示出的UL Grant占用36比特，在实际应用中，UL Grant可以占用30比特。
图14是消息2的一种格式的示意图。如图14所示，第一个预留字段(R#1)中的值或第二个预留字段(R#2)中的第一比特位的值用于指示消息2中所包括的上行资源分配(UL Grant)字段的个数。例如，当R#2中的值为1时，表示消息2中包括2个上行资源分配字段(分别记作UL Grant#1和UL Grant#2)。其中，UL Grant#1中的值用于指示发送RRC信令#1所使用的时频资源，UL Grant#2中的值用于指示发送上行数据的时频资源。
应理解，R#2中的第一比特位可以是R#2中的任一比特位。图6中示出的消息2中的各字段所占用的比特(bit)数仅是一种示例，本申请并不对消息2中的各字段所占用的比特数作具体限定。
还应理解，图11至图14所示出的消息2的格式仅是示例，本申请实施例中消息2还可以采用其它格式或者图11至图14中的格式的变形。例如，消息2中的各字段的位置可以不同于图11至图14所示出的消息2的格式中各字段的位置。再如，消息2的格式还可以包括除图11至图14所示出的字段外的其他字段，或者，消息2的格式可以只包括图11至图14所示出的字段中的部分字段。
综上，在上述实施例中，可以通过保留比特位指示是否是两个或多个ULgrant或者是否是一个大的UL grant(能够传输数据)。
可选地，RRC信令#2可以是消息4(Msg4)。
消息4，例如可以是竞争解决(Contention Resolution)消息、RRC连接建立消息、RRC连接重建立消息、RRC连接恢复消息，RRC连接拒绝消息或RRC连接释放消息。
此外，消息4也可以是新定义的在随机接入过程中接入网设备向终端设备发送的第一条RRC信令，本申请实施例对此不作限定。
S1020，基于第一条RRC信令，终端设备与接入网设备之间传输数据。
即，终端设备基于RRC信令#1，向接入网设备发送上行数据；和/或，接入网设备基于RRC信令#2，向终端设备发送下行数据。
可选地，上行数据和/或下行数据可以通过非接入层协议数据单元NAS PDU发送。
例如，RRC信令#1可以携带上行数据的NAS PDU。即，终端设备可以通过RRC信令#1携带的NAS PDU发送上行数据。再如，终端设备可以同时向接入网设备发送携带上行数据的NAS PDU与RRC信令#1，或者，终端设备在发送RRC信令#1后，紧接着发送携带上行数据的NAS PDU。
再如，RRC信令#2可以携带下行数据的NAS PDU。即，接入网设备可以通过RRC信令#2携带的NAS PDU发送下行数据。再如，接入网设备可以同时向终端设备发送携带下行数据的NAS PDU与RRC信令#1，或者，接入网设备在发送RRC信令#2后，紧接着发送携带下行数据的NAS PDU。
可选地，上行数据或下行数据可以通过DRB或者SRB0发送。
在本申请中，上行数据和RRC信令#1可以复用一个传输块，也可以作为两个或多个 传输块分别传输。下行数据可以和RRC信令#2可以复用一个传输块，也可以作为两个或多个传输块分别传输。
需要说明的是，在RRC信令#1和上行数据一起传输的情况下，RRC信令#1可以携带终端设备的标识。在RRC信令#1和上行数据分别传输的情况下，上行数据可以携带终端设备的标识或通过终端设备的标识进行加扰。同理，在RRC信令#2和下行数据一起传输的情况下，RRC信令#2可以携带终端设备的标识。在RRC信令#2和下行数据分别传输的情况下，下行数据可以携带终端设备的标识或通过终端设备的标识进行加扰。
所述终端设备的标识，例如可以是RNTI、hashS-TMSI、S-TMSI、截断的S-TMSI、接入的随机数、IMSI、MAC CE里携带的终端设备的标识等，本申请对终端设备的标识不做具体限定。
进一步地，以传输上行数据为例，若上行数据可以和RRC信令#1作为两个传输块分别传输，携带上行数据的NAS PDU可以通过SRB 1bis或者SRB0发送，或者RRC信令#1通过SRB 0发送且上行数据通过DRB发送。应理解，下行数据的传输可以参照传输上行数据的方式，为了简洁，此处不再赘述。
进一步地，若终端设备在消息3中通过NAS消息发送了上行数据，该NAS消息可以为控制面服务请求消息(Control Plane Service Request(ESM Data Transport))。
因此，根据本申请实施例的方法，基于终端设备与接入网设备之间的第一条RRC信令可以实现上行和/或下行的数据传输，而不需要建立RRC连接，从而能够节省为传输数据而建立所需承载的信令开销，并能够降低设备功耗。
以下，结合图15至图18，分别针对上行数据早传和下行数据早传，分别描述根据本申请实施例的数据传输方法。应理解，图15至图18中所示出的与图2相同或相应地步骤、术语、概念等可以参照上文对图2的描述，为了避免重复，在对图15至图18进行介绍时，将不再对相同或相应地内容进行详细描述。
不失一般性地，下文中均以RRC信令#1为消息3，RRC信令#2为消息4为例，描述本申请各实施例。
图15是本申请一个实施例的数据传输的方法的示意性流程图。图15所示的方法适用于基于CP方案的上行数据早传。
S1510，终端设备向接入网设备发送消息1。
其中，消息1用于指示终端设备使用上行和/或下行数据早传方式传输数据。。
S1520，接入网设备接收到消息1后，向终端设备发送消息2。
可选地，在本申请实施例中，若接入网设备根据消息1获知UE想要进行上行数据早传后，向终端设备分配用于传输上行数据的资源。
进一步地，用于传输上行数据的资源的大小可以是固定的，比如100字节(bytes)。该用于传输上行数据的资源的大小也可以是接入网设备根据第一消息(例如，发送第一消息的资源或第一消息中的前导码)确定的。也就是说，第一消息，例如发送第一消息的资源或第一消息中的前导码，还可以用于指示上行数据的大小，从而接入网设备能够根据上行数据的大小合理分配用于传输上行数据的资源。
S1530，终端设备向接入网设备发送消息3。
示例的，消息3可以携带上行数据。
例如，终端设备接收到消息2后，如果有上行数据需要传输，可以在传输消息3的 同时，在预先配置的或者预留的用于上行数据早传的资源上传输上行数据。
再如，终端设备也可以在消息2所指示的目标资源上传输消息3和上行数据。
消息3定义如同上述实施例定义，具体消息名称不限制。
S1540，接入网设备向MME发送候选消息#1。
候选消息#1包括所述上行数据。候选消息#1，例如可以是获取UE信息消息(Retrieve UE Information Message)或者初始UE消息(Initial UE Message)，或者是新定义的其他消息，本申请实施例对此不做限定。
此时，MME即可获得终端设备的上行数据，实现上行数据早传。
可选地，该方法还可以包括：
S1560，接入网设备向终端设备发送候选消息#3。
可选地，候选消息#3可以是消息4。
此外，候选消息#3还可以是新定义的接入网设备向所述终端设备发送的第一条RRC消息，本申请实施例并不对此限定。
可选地，候选消息#3可以携带一个指示信息(例如，记作指示信息#2)。其中，指示信息#2用于指示当前的流程或会话过程可以结束，或指示终端设备需要返回或维持在空闲态。该指示信息#2可以表现为停止指示(End Indication)或者释放指示(release indication)。
可选地，终端设备接收到消息4之后，向接入网设备发送消息5。消息5，例如可以是RRC连接完成消息、RRC连接重建立完成消息或RRC连接恢复完成消息等。
在一种可能的实现方式中，消息5中不携带NAS消息。若接入网设备此时有下行数据需要传输，接入网设备在接收到消息5后，向终端设备发送下行数据并指示终端设备返回空闲态或保持空闲态。
在另一可能的实现方式中，终端设备接收到消息4(例如，竞争解决消息、RRC连接建立消息、RRC连接重建立消息或RRC连接恢复)后，按照正常的RRC连接建立过程建立RRC连接。其中，若此时终端设备在上行没有数据，终端设备可以在消息5(如RRC连接建立完成，RRC连接重建立完成，RRC连接恢复完成)上发送一个空的NAS消息(例如，记作NAS消息#1)，如ESM Data Transport，NAS消息#1只有消息头，而没有数据单元。接入网设备接收到NAS消息#1后，将NAS消息#1通过初始UE消息或其他消息发送给MME。MME收到该消息后可以忽略或者丢弃该NAS消息。后续过程与现有技术相同，为了简洁，此处不再赘述。
在又一可能的实现方式中，终端设备可以在消息5如RRC连接建立完成，RRC连接重建立完成，RRC连接恢复完成)中发送与消息3中相同的NAS消息(例如，记作NAS消息#2)，如控制面服务请求(Control Plane Service Request(ESM Data Transport))消息。进一步地，该NAS消息#2可以包括一个指示信息(例如，记作指示信息#3)，指示信息#3用于指示NAS消息#2与消息3中传输的NAS消息一样，当接入网设备接收NAS消息#2后，将该NAS消息发送给MME，MME可以根据指示信息忽略此消息。
在又一可能的实现方式中，UE可以在消息5如RRC连接建立完成，RRC连接重建立完成，RRC连接恢复完成)中发送一个NAS消息(例如，记作NAS消息#3)，NAS消息#3可以包括一个指示信息(例如，记作指示信息#4)，指示信息#4用于区分NAS消息#3和现有技术中消息5中的NAS消息，便于MME进行后续处理，当MME接收指 示信息#4后，可以忽略或者丢弃该NAS消息。或者该NAS消息和指示信息是两个字段。因此，该NAS消息#3既可以是携带指示信息，又可以与指示信息分为不同的字段。NAS消息#3的应用场景为：上行数据已经通过RRC信令#1完成传输，而消息5中没有额外的上行NAS数据时，才使用NAS消息#3。由于终端设备已经在消息3中发送了NAS消息，因此，通过上述各实现方式，可以克服现有消息5和初始UE消息中NAS消息为必选的问题。
上述实现方式，可以适用于当有一个下行包但接入网设备无法传输时，或者核心网设备有多个下行包时的处理方式，以此来完成数据传输。
这样，通过候选消息#3中的指示信息#2，可以在MME没有下行数据传输时，提前释放终端设备或指示终端处于空闲态，相对于现有技术的释放流程，能够节省信令开销，另一方面，也能够降低终端设备的功耗。
进一步地，若候选消息#3为RRC连接建立消息、RRC连接重建立消息、RRC连接恢复消息，候选消息#3还可以包括重定向指示等。
若候选消息#3为RRC连接拒绝消息，候选消息#3还可以携带指示信息，该指示信息用于指示终端返回或保持在空闲态。
可选地，候选消息#3可以携带下行数据。
进一步的，该下行数据可以封装在NAS PDU中。即候选消息#3可以携带包括所述下行数据的NAS PDU。该NAS PDU可以承载在SRB0上。
所述下行数据可以是MME通过寻呼(Paging)消息向接入网设备发送的，也可以是MME通过候选消息#2向接入网设备发送的。
此外，所述下行数据也可以是在MME发送候选消息#2之后且接入网设备发送候选消息#3之前，MME通过与接入网设备之间的下行NAS传输，向接入网设备发送的。
比如，接入网设备可以提前告诉MME自己所能调度的数据包大小，比如，接入网设备通过候选消息#1来指示其所能调度的数据包大小，MME可以将下行数据拆包发送给接入网设备。在此情况下，接入网设备可以连续发送多个数据包给终端设备，每个数据包携带终端设备的标识信息，当发送完最后一个数据包后，接入网设备可以向终端发送指示信息#2，以释放终端设备或指示终端返回或保持空闲态。
可选地，若所述下行数据为MME通过候选消息#2向接入网设备发送的，则在S1560之前，该方法还包括：
S1550，MME向接入网设备发送候选消息#2。其中，候选消息#2包括所述下行数据。
候选消息#2，例如可以是UE信息发送消息(UE Information Transfer Message)，或下行NAS传输消息(Downlink NAS Transport Message)，或者是新定义的消息，本申请实施例对此不做限定。
可选地，候选消息#2还可以包括一个指示信息(例如，记作指示信息#1)，指示信息#1用于指示当前的流程或会话过程可以结束，或指示终端设备需要返回或维持在空闲态。指示信息#1可以表现为停止指示(End Indication)。
示例的，当MME向接入网设备发送候选消息#2时，若无下行数据时，MME可以在该消息中携带指示信息，该指示信息用于指示该流程结束或者指示接入网设备指示终端设备返回空闲态或者维持空闲态。
示例的，当MME向接入网设备发送候选消息#2时，若有下行数据时，如果只有一 个数据包，MME在该消息中携带指示信息，该指示信息用于指示该流程结束或者指示接入网设备指示终端设备返回空闲态或者维持空闲态。
示例的，若MME有多个终端的下行包到达MME，则MME向接入网设备发送候选消息#2时不会携带该指示信息。应理解，此时终端设备还未进入连接态，属于空闲态或者空闲态-连接态的一种中间态或者终端的转态是空口未进入连接态，S1口进入连接态。
因此，MME可以通过发送指示信息#1，指示接入网设备可以通知终端设备返回或维持在空闲态。还应理解，指示信息#2可以与指示信息#1相同，也可以不同，本申请实施例并不对此限定。
进一步地，接入网设备向终端设备发送下行数据后，可以向MME发送肯定确认(Acknowledgement，ACK)，例如发送NAS deliver ACK。ACK用于指示接入网设备已经将下行数据发送给了终端设备，MME不需要向接入网设备发送寻呼消息。
可选地，在S1560中，若接入网设备没有将下行数据发送给终端设备，接入网设备可以向MME反馈数据未发送成功或将未发送的数据发送给MME，MME会通过寻呼的方式使得终端设备获取数据。
因此，根据本申请实施例的数据传输方法，可以基于终端设备向接入网设备发送的第一条RRC信令实现上行数据的传输，而不需要建立RRC连接，从而能够节省功耗以及信令开销。
图16是本申请一个实施例的数据传输的方法的示意性流程图。图16所示的方法适用于基于UP方案的上行数据早传。应理解，下文中所出现的与图16相同或相应地术语、概念等可以参照上文对图15的描述，为了避免重复，下文中将不再赘述。
S1610，终端设备向接入网设备发送消息1。
S1620，接入网络设备接收到消息1后，向终端设备发送消息2。
S1630，终端设备向接入网络设备发送消息3。
消息3包括上行数据，上行数据可以通过数据无线承载DRB发送。上行数据需要加密，密钥可以通过上次连接获得下一跳链计算(next hop chaining count，NCC)来更新。
进一步地，终端设备发送数据的承载DRB可以是基于上一次连接中的DRB配置或者是采用默认的DRB配置。若采用上一次连接的DRB配置，接入网设备若不支持该配置，则会重新对终端设备进行配置，如通过RRC重配置消息或者RRC连接恢复消息进行配置。
进一步还可以包括：
S1640，接入网设备向MME发送第二请求消息。
可选地，第二请求消息中的内容可以和UE上下文恢复请求消息(UE Context Resume Request)中的内容相同。
进一步地，第二请求消息可以是UE上下文恢复请求消息。
接入网设备在接收到消息3后，根据短完整性消息验证码(short Message Authentication Code for Integrity，short-MAC-I)验证终端设备。若该接入网设备不是原来的接入网设备，则需要通过X2接口将short-MAC-I发送给源接入网设备，并由源接入网设备进行校验，校验成功后，源接入网设备将终端设备的上下文信息发送给当前的接入网设备，当前的接入网设备进行后续的操作。
进一步还可以包括：
S1650，MME根据所述第二请求消息向接入网设备发送第二响应消息。
可选地，第二响应消息中的内容可以和UE上下文恢复响应消息(UE Context Resume Response)中的内容相同。
进一步地，第二响应消息为UE上下文恢复响应消息。
若接入网设备根据收到的第二响应消息发现接入网设备所收到的数据对应的无线接入承载(E-UTRAN Radio Access Bearer，E-RAB)被拒绝了，则接入网设备将发送RRC连接恢复消息或RRC连接建立消息给终端设备，该RRC连接恢复消息或RRC连接建立消息可以包含一条指示信息，该指示信息用于指示数据E-RAB被拒绝传输或者传输失败或者指示终端设备需要将之前发送的数据包重新发送。此时，接入网设备额外分配一个ULgrant用于该数据传输。
S1660，接入网设备收到第二响应消息后，向所述S-GW发送所述上行数据。
此时，S-GW即可获得终端设备的上行数据，实现上行数据早传。
可选地，该方法还可以包括：
S1670，接入网设备成功发送完上行数据后，可以向MME发送UE上下文释放请求消息、UE上下文挂起请求消息或释放连接请求消息；
S1680，MME根据UE上下文释放请求消息向接入网设备发送UE上下文释放消息；或MME根据UE上下文挂起请求消息向接入网设备发送UE上下文挂起完成消息；或MME根据释放连接请求，向接入网设备发送UE上下文释放消息。
S1690，接入网设备根据，向所述终端设备发送候选消息#4。
可选地，候选消息#4可以是消息4，如RRC连接建立消息、RRC连接重建立消息、RRC连接恢复消息也可以是RRC连接释放消息
此外，候选消息#4还可以是新定义的接入网设备向所述终端设备发送的第一条RRC消息，本申请实施例并不对此限定。
应理解，候选消息#4可以与候选消息#3相同，也可以不同，本申请实施例对此不作限定。
可选地，候选消息#4可以携带一个指示信息(例如，记作指示信息#5)。其中，指示信息#5用于指示当前的流程或会话过程可以结束，或指示终端设备需要返回或维持在空闲态。该指示信息#5可以表现为停止指示(End Indication)。
应理解，指示信息#5可以与指示信息#2相同，也可以不同，本申请实施例对此不作限定。
这样，通过候选消息#4中指示信息#5，可以在S-GW没有下行数据传输时，提前释放终端设备，相对于现有技术的释放流程，能够节省信令开销，另一方面，也能够降低终端设备的功耗。
进一步地，若候选消息#4为RRC连接建立消息、RRC连接重建立消息、RRC连接恢复消息，候选消息#4还可以包括重定向指示等。
可选地，候选消息#4可以携带下行数据。
若下行数据已到达接入网设备，而接入网设备无法将下行数据发送到终端设备，则采用类似S1560中的几种方式来传输，如建立RRC连接，并在消息5中放置空的NAS消息，或者一个指示信息等方式，然后使用正常的数据传输流程。
因此，根据本申请实施例的数据传输方法，可以基于终端设备向接入网设备发送的 第一条RRC信令实现上行数据的传输，而不需要建立RRC连接，从而能够节省功耗以及信令开销。
图17是根据本申请另一实施例的数据传输方法的示意性流程图。图17所示的方法适用于基于CP方案的下行数据早传。
S1710，终端设备向接入网设备发送消息1。
S1720，接入网络设备接收到消息1后，向终端设备发送消息2。
S1730，终端设备向接入网设备发送消息3，所述消息3可以包括服务请求消息(Service Request Message)。
消息3如同上述实施例，可以是现有的RRC信令，可以是新定义的RRC信令。
可以通过消息3中的指示信息(例如，记作指示信息#6)指示终端设备要进行下行数据早传，即基于接入网设备向终端设备发送的第一条RRC信令传输下行数据。接入网设备接收该指示信息#6后，可较早触发与核心网设备的信令交互。
S1740，接入网设备在接收到消息3后，向MME发送请求消息。
该请求消息可以是获取UE信息消息或者初始UE消息，或者是新定义的其他消息，本申请实施例对此不做限定。
S1750，MME接收到请求消息后，向接入网设备发送所述下行数据。
可选地，MME可以通过UE信息发送消息(UE Information Transfer Message)，或下行NAS传输消息(Downlink NAS Transport Message)向接入网设备发送所述下行数据。
S1760，接入网设备通过消息4向所述终端设备发送所述下行数据。
进一步地，消息4还用于指示终端设备保持在空闲态或者返回空闲态，终端设备根据消息4返回空闲态或保持在空闲态。
因此，根据本申请实施例的数据传输方法，能够通过消息4传输下行数据，即实现下行数据早传，从而能够节省功耗以及信令开销。
图18是根据本申请另一实施例的数据传输方法的示意性流程图。图18所示的方法适用于基于UP方案的下行数据早传。
S1810，终端设备向接入网设备发送消息1。
S1820，接入网络设备接收到消息1后，向终端设备发送消息2。
S1830，终端设备根据消息2，向接入网设备发送消息3。所述消息3可以包括服务请求消息(Service Request Message)。
S1840，接入网设备在接收到消息3中的服务请求消息后，向MME发送所述服务请求消息。
可选地，接入网设备可以通过终端设备上下文恢复请求消息向MME发送所述服务请求消息。
S1850，MME根据所述服务请求消息，向接入网设备发送服务响应消息。
可选地，MME可以在接收到接入网设备发送的终端设备上下文恢复请求消息后，向终端设备上下文恢复响应消息。
S1860，MME向S-GW发送修改承载请求消息。
S1870，S-GW向MME回复修改承载响应消息。从而S-GW能够获得所述接入网设备的地址。
S1880，S-GW向接入网设备发送所述下行数据。
S1890，接入网设备通过消息4向终端设备发送所述下行数据。
可选地，在S1890之前，接入网设备接收到S-GW发送的下行数据后，该方法还可以包括：
接入网设备向MME发送UE上下文释放请求消息、UE上下文挂起请求消息或释放连接请求消息或者其他释放请求消息；
MME根据UE上下文释放请求消息向接入网设备发送UE上下文释放命令消息；或MME根据UE上下文挂起请求消息向接入网设备发送UE上下文挂起完成消息；或MME根据释放连接请求，向接入网设备发送UE上下文释放消息；
接入网设备根据所述UE上下文释放命令消息所述UE上下文挂起完成消息，向所述终端设备发送候选消息#5。
可选地，候选消息#5可以是消息4。
消息4，例如为RRC连接建立消息、RRC连接重建立消息、RRC连接恢复消息或者RRC连接释放消息。
此外，候选消息#5还可以是新定义的接入网设备向所述终端设备发送的第一条RRC消息，本申请实施例并不对此限定。
应理解，候选消息#5可以与候选消息#3相同，也可以不同，本申请实施例对此不作限定。
可选地，候选消息#5可以携带一个指示信息(例如，记作指示信息#6)。其中，指示信息#5用于指示当前的流程或会话过程可以结束，或指示终端设备需要返回或维持在空闲态。该指示信息#6可以表现为停止指示(End Indication)。
应理解，指示信息#6可以与指示信息#2相同，也可以不同，本申请实施例对此不作限定。
这样，通过候选消息#5中指示信息#6，可以在S-GW没有下行数据传输时，提前释放终端设备，相对于现有技术的释放流程，能够节省信令开销，另一方面，也能够降低终端设备的功耗。
进一步地，若候选消息#5为RRC连接建立消息、RRC连接重建立消息或RRC连接恢复消息。候选消息#5还可以包括RRC连接释放消息中的相关信息，比如释放原因，重定向指示等。
若候选消息#5为RRC连接拒绝消息，候选消息#5还可以携带原因值，该原因值表示RRC连接拒绝的原因。
若候选消息#5为RRC连接释放消息，指示终端返回或者保持空闲态。该候选消息#5可以携带终端设备的标识信息，具体可以在MAC CE中携带或者通过PDCCH加扰。
可选地，在S1890中，接入网设备可以通过候选消息#5向终端设备发送所述下行数据。
因此，根据本申请实施例的数据传输方法，可以基于终端设备向接入网设备发送的第一条RRC信令实现上行数据的传输，而不需要建立RRC连接，从而能够节省功耗以及信令开销。
可选地，在一种可能的实现中，当终端设备接收寻呼消息时，寻呼消息里可以包括一个指示信息，指示接入网设备需要进行下行数据早传操作，这样终端设备就可以按照 下行数据早传操作来进行后续流程，进一步的核心网设备可以在发送给接入网设备的寻呼消息携带一个指示信息，用于指示接入网设备需要进行下行数据早传。在接入网设备发送寻呼消息给终端之前，接入网设备从核心网接收到了下行包和/或者指示信息。指示信息用于指示有下行数据包可以通过数据早传(如下行数据早传)的方式发送给终端。
可选地，终端设备在连接态时，接入网设备也可以通过PDCCH向所述终端设备发送指示，用于指示UE需要进行数据早传的随机接入，如上行数据早传或者下行数据早传。即通过PDCCH order方式进行随机接入。具体的指示信息可以通过DCI来承载，或者接入网设备指示的UE接入的资源位置是用于数据早传的资源位置来实现数据早传。这样在连接态，接入网设备可以通过PDCCH指示UE使用数据早传的方式。
图19示出了本申请实施例的终端设备1900的示意性框图。如图19所示，该终端设备1900包括：处理单元1910和收发单元1920。
处理单元1910，用于生成第一指示，所述第一指示用于指示所述终端设备基于所述终端设备向所述接入网设备发送的第一条无线资源控制RRC信令传输数据，和/或，
所述第一指示用于指示所述接入网设备基于所述接入网设备向所述终端设备发送的第一条无线资源控制RRC信令传输数据。
收发单元1920，用于向接入网设备发送所述处理单元生成的第一指示，以及在基于所述第一条RRC信令，所述终端设备与所述接入网设备之间传输数据。
应理解，处理单元1910可以由处理器实现，收发单元1920可以由收发器实现。
还应理解，该终端设备1900可以对应上述方法中描述的终端设备，并且，该终端设备1900中各模块或单元分别用于执行图10至图18所示方法实施例中终端设备所执行的各动作或处理过程，这里，为了避免赘述，省略其详细说明。
图20示出了本申请实施例的接入网设备2000的示意性框图。如图20所示，该接入网设备2000包括：处理单元2010和收发单元2020。
处理单元2010用于控制所述收发单元2020：
接收终端设备发送的第一指示，所述第一指示用于指示所述终端设备基于所述终端设备向所述接入网设备发送的第一条无线资源控制RRC信令传输数据，和/或，
所述第一指示用于指示所述接入网设备基于所述接入网设备向所述终端设备发送的第一条无线资源控制RRC信令传输数据；以及
基于所述第一条RRC信令，所述接入网设备与所述终端设备之间传输数据。
应理解，处理单元2010可以由处理器实现，收发单元2020可以由收发器实现。
还应理解，该接入网设备2000可以对应上述方法中描述的接入网设备，并且，该接入网设备2000中各模块或单元分别用于执行图10至图18所示方法实施例中接入网设备所执行的各动作或处理过程，这里，为了避免赘述，省略其详细说明。
本申请实施例可以应用于处理器中，或者由处理器实现。处理器可以是一种集成电路芯片，具有信号的处理能力。在实现过程中，上述方法实施例的各步骤可以通过处理器中的硬件的集成逻辑电路或者软件形式的指令完成。上述的处理器可以是中央处理单元(central processing unit，CPU)、该处理器还可以是其他通用处理器、数字信号处理器(digital signal processor，DSP)、专用集成电路(application specific integrated circuit，ASIC)、现成可编程门阵列(field programmable gate array，FPGA)或者其他可编程逻辑器件、分立门或者晶体管逻辑器件、分立硬件组件。可以实现或者执行本申请实施例 中的公开的各方法、步骤及逻辑框图。通用处理器可以是微处理器或者该处理器也可以是任何常规的处理器等。结合本申请实施例所公开的方法的步骤可以直接体现为硬件译码处理器执行完成，或者用译码处理器中的硬件及软件器组合执行完成。软件器可以位于随机存储器，闪存、只读存储器，可编程只读存储器或者电可擦写可编程存储器、寄存器等本领域成熟的存储介质中。该存储介质位于存储器，处理器读取存储器中的信息，结合其硬件完成上述方法的步骤。
还应理解，本申请实施例中的存储器可以是易失性存储器或非易失性存储器，或可包括易失性和非易失性存储器两者。其中，非易失性存储器可以是只读存储器(read-only memory，ROM)、可编程只读存储器(programmable ROM，PROM)、可擦除可编程只读存储器(erasable PROM，EPROM)、电可擦除可编程只读存储器(electrically EPROM，EEPROM)或闪存。易失性存储器可以是随机存取存储器(random access memory，RAM)，其用作外部高速缓存。通过示例性但不是限制性说明，许多形式的RAM可用，例如静态随机存取存储器(static RAM，SRAM)、动态随机存取存储器(dynamic RAM，DRAM)、同步动态随机存取存储器(synchronous DRAM，SDRAM)、双倍数据速率同步动态随机存取存储器(double data rate SDRAM，DDR SDRAM)、增强型同步动态随机存取存储器(enhanced SDRAM，ESDRAM)、同步连接动态随机存取存储器(synchlink DRAM，SLDRAM)和直接内存总线随机存取存储器(direct rambus RAM，DRRAM)。应注意，本文描述的系统和方法的存储器旨在包括但不限于这些和任意其它适合类型的存储器。
应理解，本文中术语“和/或”，仅仅是一种描述关联对象的关联关系，表示可以存在三种关系，例如，A和/或B，可以表示：单独存在A，同时存在A和B，单独存在B这三种情况。另外，本文中字符“/”，一般表示前后关联对象是一种“或”的关系。
应理解，在本申请的各种实施例中，上述各过程的序号的大小并不意味着执行顺序的先后，各过程的执行顺序应以其功能和内在逻辑确定，而不应对本申请实施例的实施过程构成任何限定。
本领域普通技术人员可以意识到，结合本文中所公开的实施例描述的各示例的单元及算法步骤，能够以电子硬件、或者计算机软件和电子硬件的结合来实现。这些功能究竟以硬件还是软件方式来执行，取决于技术方案的特定应用和设计约束条件。专业技术人员可以对每个特定的应用来使用不同方法来实现所描述的功能，但是这种实现不应认为超出本申请的范围。
所属领域的技术人员可以清楚地了解到，为描述的方便和简洁，上述描述的系统、装置和单元的具体工作过程，可以参考前述方法实施例中的对应过程，在此不再赘述。
在本申请所提供的几个实施例中，应该理解到，所揭露的系统、装置和方法，可以通过其它的方式实现。例如，以上所描述的装置实施例仅仅是示意性的，例如，所述单元的划分，仅仅为一种逻辑功能划分，实际实现时可以有另外的划分方式，例如多个单元或组件可以结合或者可以集成到另一个系统，或一些特征可以忽略，或不执行。另一点，所显示或讨论的相互之间的耦合或直接耦合或通信连接可以是通过一些接口，装置或单元的间接耦合或通信连接，可以是电性，机械或其它的形式。
所述作为分离部件说明的单元可以是或者也可以不是物理上分开的，作为单元显示的部件可以是或者也可以不是物理单元，即可以位于一个地方，或者也可以分布到多个网络单元上。可以根据实际的需要选择其中的部分或者全部单元来实现本实施例方案的 目的。
另外，在本申请各个实施例中的各功能单元可以集成在一个处理单元中，也可以是各个单元单独物理存在，也可以两个或两个以上单元集成在一个单元中。
所述功能如果以软件功能单元的形式实现并作为独立的产品销售或使用时，可以存储在一个计算机可读取存储介质中。基于这样的理解，本申请的技术方案本质上或者说对现有技术做出贡献的部分或者该技术方案的部分可以以软件产品的形式体现出来，该计算机软件产品存储在一个存储介质中，包括若干指令用以使得一台计算机设备(可以是个人计算机，服务器，或者网络设备等)执行本申请各个实施例所述方法的全部或部分步骤。而前述的存储介质包括：U盘、移动硬盘、只读存储器(read-only memory，ROM)、随机存取存储器(random access memory，RAM)、磁碟或者光盘等各种可以存储程序代码的介质。
以上所述，仅为本申请的具体实施方式，但本申请的保护范围并不局限于此，任何熟悉本技术领域的技术人员在本申请揭露的技术范围内，可轻易想到变化或替换，都应涵盖在本申请的保护范围之内。因此，本申请的保护范围应以所述权利要求的保护范围为准。

Claims (28)

  1. 一种数据传输方法，其特征在于，包括：
    终端设备向接入网设备发送第一指示，所述第一指示用于指示所述终端设备基于所述终端设备向所述接入网设备发送的第一条无线资源控制RRC信令传输数据，和/或，
    所述第一指示用于指示所述接入网设备基于所述接入网设备向所述终端设备发送的第一条无线资源控制RRC信令传输数据；
    基于所述第一条RRC信令，所述终端设备与所述接入网设备之间传输所述数据。
  2. 如权利要求1所述的方法，其特征在于，所述基于所述第一条RRC信令，所述终端设备与所述接入网设备之间传输所述数据，包括：
    通过所述第一条RRC信令携带所述数据，所述终端设备与所述接入网设备之间传输所述数据。
  3. 如权利要求1或2所述的方法，其特征在于，所述终端设备与所述接入网设备之间传输所述数据，包括：
    所述终端设备与所述接入网设备之间通过非接入层协议数据单元NAS PDU传输所述数据；或者，
    所述终端设备与所述接入网设备之间通过数据无线承载DRB传输所述数据。
  4. 如权利要求1至3任一权要所述的方法，其特征在于，所述第一条RRC信令为消息3或消息4。
  5. 如权利要求4所述的方法，其特征在于，所述消息3为下述任一种消息：
    RRC连接请求消息、RRC连接重建立请求消息和RRC连接恢复请求消息；和/或
    所述消息4为下述任一种消息：
    冲突解决消息、RRC连接建立消息、RRC连接重建立消息和RRC连接恢复消息。
  6. 如权利要求1至5任一权要所述的方法，其特征在于，在基于所述第一条RRC信令，所述终端设备与所述接入网设备之间传输所述数据之前，所述方法还包括：
    所述终端设备接收系统消息，所述系统消息包括数据量信息，所述数据量信息用于指示所述终端设备基于所述第一条RRC信令所能传输的最大数据量；
    其中，所述基于所述第一条RRC信令，所述终端设备与所述接入网设备之间传输所述数据，包括：
    当所述终端设备确定所述数据的数据量小于或等于所述最大数据量时，基于所述第一条RRC信令，所述终端设备向所述接入网设备传输所述数据。
  7. 一种数据传输方法，其特征在于，包括：
    接入网设备接收终端设备发送的第一指示，所述第一指示用于指示所述终端设备基于所述终端设备向所述接入网设备发送的第一条无线资源控制RRC信令传输数据，和/或，
    所述第一指示用于指示所述接入网设备基于所述接入网设备向所述终端设备发送的第一条无线资源控制RRC信令传输数据；
    基于所述第一条RRC信令，所述接入网设备与所述终端设备之间传输所述数据。
  8. 如权利要求7所述的方法，其特征在于，基于所述第一条RRC信令，所述接入网设备与所述终端设备之间所述传输数据，包括：
    通过所述第一条RRC信令携带数据，所述接入网设备与所述终端设备之间传输所述数据。
  9. 如权利要求7或8所述的方法，其特征在于，所述接入网设备与所述终端设备之间传输数据，包括：
    所述接入网设备与所述终端设备之间通过非接入层协议数据单元NAS PDU传输所述数据；或者，
    所述接入网设备与所述终端设备之间通过数据无线承载DRB传输所述数据。
  10. 如权利要求7至9任一权要所述的方法，其特征在于，所述第一条RRC信令为消息3或消息4。
  11. 如权利要求10所述的方法，其特征在于，所述消息3为下述任一种消息：
    RRC连接请求消息、RRC连接重建立请求消息和RRC连接恢复请求消息；和/或
    所述消息4为下述任一种消息：
    冲突解决消息、RRC连接建立消息、RRC连接重建立消息和RRC连接恢复消息。
  12. 如权利要求9所述的方法，其特征在于，所述方法还包括：
    所述接入网设备向核心网设备发送所述NAS PDU。
  13. 如权利要求9所述的方法，其特征在于，在所述基于所述第一条RRC信令，所述接入网设备与所述终端设备之间所述传输数据之前，所述方法还包括：
    所述接入网设备接收所述核心网设备发送的所述NAS PDU；
    其中，所述基于所述第一条RRC信令，所述接入网设备与所述终端设备之间传输数据，包括：
    基于所述第一条RRC信令，所述接入网设备向所述终端设备传输所述NAS PDU。
  14. 如权利要求13所述的方法，其特征在于，携带所述NAS PDU的NAS消息包括指示信息，所述指示信息用于指示所述接入网设备指示所述终端设备保存在空闲态。
  15. 一种终端设备，其特征在于，包括：
    处理单元和收发单元，其中，
    所述处理单元用于生成第一指示，所述第一指示用于指示所述终端设备基于所述终端设备向所述接入网设备发送的第一条无线资源控制RRC信令传输数据，和/或，
    所述第一指示用于指示所述接入网设备基于所述接入网设备向所述终端设备发送的第一条无线资源控制RRC信令传输数据；
    所述收发单元，用于向接入网设备发送所述处理单元生成的第一指示，以及在基于所述第一条RRC信令，所述终端设备与所述接入网设备之间传输所述数据。
  16. 如权利要求15所述的终端设备，其特征在于，所述收发单元具体用于：
    通过所述第一条RRC信令携带数据，与所述接入网设备之间传输所述数据。
  17. 如权利要求15或16所述的终端设备，其特征在于，所述收发单元具体用于：
    与所述接入网设备之间通过非接入层协议数据单元NAS PDU传输所述数据；或者，
    与所述接入网设备之间通过数据无线承载DRB传输所述数据。
  18. 如权利要求15至17任一权要所述的终端设备，其特征在于，所述第一条RRC信令为消息3或消息4。
  19. 如权利要求18所述的终端设备，其特征在于，所述消息3为下述任一种消息：
    RRC连接请求消息、RRC连接重建立请求消息和RRC连接恢复请求消息；和/或
    所述消息4为下述任一种消息：
    冲突解决消息、RRC连接建立消息、RRC连接重建立消息和RRC连接恢复消息。
  20. 如权利要求15至19任一权要所述的终端设备，其特征在于，所述收发单元还用于：
    接收系统消息，所述系统消息包括数据量信息，所述数据量信息用于指示所述终端设备基于所述第一条RRC信令所能传输的最大数据量；
    当所述处理单元确定所述数据的数据量小于或等于所述最大数据量时，所述收发单元具体用于，基于所述第一条RRC信令，向所述接入网设备传输所述数据。
  21. 一种接入网设备，其特征在于，包括：
    处理单元和收发单元，其中，所述处理单元用于控制所述收发单元：
    接收终端设备发送的第一指示，所述第一指示用于指示所述终端设备基于所述终端设备向所述接入网设备发送的第一条无线资源控制RRC信令传输数据，和/或，
    所述第一指示用于指示所述接入网设备基于所述接入网设备向所述终端设备发送的第一条无线资源控制RRC信令传输数据；以及
    基于所述第一条RRC信令，所述接入网设备与所述终端设备之间传输所述数据。
  22. 如权利要求21所述的接入网设备，其特征在于，所述收发单元具体用于：
    通过所述第一条RRC信令携带数据，与所述终端设备之间传输所述数据。
  23. 如权利要求21或22所述的接入网设备，其特征在于，所述收发单元具体用于：
    与所述终端设备之间通过非接入层协议数据单元NAS PDU传输所述数据；或者，
    与所述终端设备之间通过数据无线承载DRB传输所述数据。
  24. 如权利要求21至23任一权要所述的接入网设备，其特征在于，所述第一条RRC信令为消息3或消息4。
  25. 如权利要求24所述的接入网设备，其特征在于，所述消息3为下述任一种消息：
    RRC连接请求消息、RRC连接重建立请求消息和RRC连接恢复请求消息；和/或
    所述消息4为下述任一种消息：
    冲突解决消息、RRC连接建立消息、RRC连接重建立消息和RRC连接恢复消息。
  26. 如权利要求23所述的接入网设备，其特征在于，所述收发单元还用于：
    向核心网设备发送所述NAS PDU。
  27. 如权利要求23所述的接入网设备，其特征在于，所述收发单元具体用于：
    接收所述核心网设备发送的所述NAS PDU；
    基于所述第一条RRC信令，向所述终端设备传输所述NAS PDU。
  28. 如权利要求27所述的接入网设备，其特征在于，所
    携带所述NAS PDU的NAS消息包括指示信息，所述指示信息用于指示所述接入网设备指示所述终端设备保存在空闲态。
PCT/CN2017/093440 2017-05-05 2017-07-18 数据传输的方法、终端设备和接入网设备 WO2018201621A1 (zh)

Priority Applications (8)

Application Number Priority Date Filing Date Title
JP2019560716A JP7088603B2 (ja) 2017-05-05 2017-07-18 データ伝送方法、端末デバイス及びアクセスネットワークデバイス
CN202210868993.9A CN115442775A (zh) 2017-05-05 2017-07-18 数据传输的方法、终端设备和接入网设备
BR112019023178A BR112019023178A2 (pt) 2017-05-05 2017-07-18 método de transmissão de dados, dispositivo terminal e dispositivo de rede de acesso
EP17908302.7A EP3611947A4 (en) 2017-05-05 2017-07-18 DATA TRANSFER METHOD, TERMINAL DEVICE AND ACCESS NETWORK DEVICE
KR1020197035463A KR102390889B1 (ko) 2017-05-05 2017-07-18 데이터 송신 방법, 단말 디바이스, 및 액세스 네트워크 디바이스
CN201780090235.6A CN110603829A (zh) 2017-05-05 2017-07-18 数据传输的方法、终端设备和接入网设备
US16/674,663 US11140676B2 (en) 2017-05-05 2019-11-05 Data transmission method, terminal device, and access network device
US17/477,207 US11606786B2 (en) 2017-05-05 2021-09-16 Data transmission method, terminal device, and access network device

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
PCT/CN2017/083332 WO2018201483A1 (zh) 2017-05-05 2017-05-05 数据传输的方法、终端设备和接入网设备
CNPCT/CN2017/083332 2017-05-05

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US16/674,663 Continuation US11140676B2 (en) 2017-05-05 2019-11-05 Data transmission method, terminal device, and access network device

Publications (1)

Publication Number Publication Date
WO2018201621A1 true WO2018201621A1 (zh) 2018-11-08

Family

ID=64015669

Family Applications (2)

Application Number Title Priority Date Filing Date
PCT/CN2017/083332 WO2018201483A1 (zh) 2017-05-05 2017-05-05 数据传输的方法、终端设备和接入网设备
PCT/CN2017/093440 WO2018201621A1 (zh) 2017-05-05 2017-07-18 数据传输的方法、终端设备和接入网设备

Family Applications Before (1)

Application Number Title Priority Date Filing Date
PCT/CN2017/083332 WO2018201483A1 (zh) 2017-05-05 2017-05-05 数据传输的方法、终端设备和接入网设备

Country Status (7)

Country Link
US (2) US11140676B2 (zh)
EP (1) EP3611947A4 (zh)
JP (1) JP7088603B2 (zh)
KR (1) KR102390889B1 (zh)
CN (2) CN115442775A (zh)
BR (1) BR112019023178A2 (zh)
WO (2) WO2018201483A1 (zh)

Cited By (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2020120608A1 (en) * 2018-12-11 2020-06-18 Nordic Semiconductor Asa Efficient cellular communication
WO2021190278A1 (zh) * 2020-03-25 2021-09-30 展讯通信（上海）有限公司 业务的请求方法及装置
CN114026911A (zh) * 2019-06-28 2022-02-08 诺基亚技术有限公司 用于双连接性或载波聚合的早期数据传输

Families Citing this family (17)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP3145269A1 (en) * 2015-09-16 2017-03-22 Alcatel Lucent Method, devices and system for a hybrid bearer service
WO2019019200A1 (zh) 2017-07-28 2019-01-31 华为技术有限公司 数据传输方法和装置
WO2019031820A1 (en) * 2017-08-08 2019-02-14 Lg Electronics Inc. METHOD AND APPARATUS FOR MANAGING FAILURE OF EARLY DATA TRANSMISSION IN A WIRELESS COMMUNICATION SYSTEM
US20190208411A1 (en) * 2018-03-16 2019-07-04 Intel Corporation Security framework for msg3 and msg4 in early data transmission
JP6889331B2 (ja) * 2018-05-09 2021-06-18 京セラ株式会社 通信制御方法、無線端末、及び基地局
EP4236603A3 (en) * 2018-08-03 2023-09-13 Telefonaktiebolaget LM Ericsson (publ) User plane optimizations for 5g cellular internet of things
EP3834573B1 (en) * 2018-08-09 2023-12-20 Sony Group Corporation Communications device, infrastructure equipment and methods
US10779160B2 (en) * 2018-12-17 2020-09-15 Verizon Patent And Licensing Inc. Method and device for updating user devices via a cellular connection
CN112566273B (zh) * 2019-09-26 2022-12-23 维沃移动通信有限公司 一种数据接收、发送方法、终端及网络侧设备
US11665772B2 (en) * 2020-08-10 2023-05-30 Acer Incorporated Apparatuses and methods for small data transmission in a radio resource control (RRC) inactive state
CN114126091B (zh) * 2020-08-26 2024-05-31 大唐移动通信设备有限公司 上行数据处理方法、装置、网络设备、终端设备及介质
CN112425225B (zh) * 2020-10-21 2024-01-09 北京小米移动软件有限公司 信息发送方法及装置、存储介质
WO2022133682A1 (zh) * 2020-12-21 2022-06-30 Oppo广东移动通信有限公司 数据传输方法、终端设备和网络设备
EP4040910A1 (en) * 2021-02-06 2022-08-10 Deutsche Telekom AG Contention based random access procedure for mobile communications
CN116709168A (zh) * 2022-02-28 2023-09-05 华为技术有限公司 一种通信方法及装置
US20230319929A1 (en) * 2022-03-30 2023-10-05 Qualcomm Incorporated Rrc reestablishment between tn and ntn
CN117202373A (zh) * 2022-05-26 2023-12-08 荣耀终端有限公司 通信方法、通信装置和通信系统

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102223715A (zh) * 2011-07-21 2011-10-19 电信科学技术研究院 一种数据传输方法及装置
CN102387495A (zh) * 2010-08-30 2012-03-21 电信科学技术研究院 一种机器类通信设备的数据传输处理方法及设备
CN102457825A (zh) * 2010-10-15 2012-05-16 电信科学技术研究院 一种数据的传输方法和设备
CN102638900A (zh) * 2011-02-15 2012-08-15 电信科学技术研究院 一种连接建立方法及装置
WO2014181178A1 (en) * 2013-05-10 2014-11-13 Alcatel Lucent Data transmission method and device

Family Cites Families (19)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101426253B (zh) * 2007-10-31 2013-08-07 华为技术有限公司 一种实现信息传输的方法、装置及系统
KR101835042B1 (ko) 2010-03-23 2018-03-08 인터디지탈 패튼 홀딩스, 인크 기계형 통신을 위한 효율적 시그널링을 위한 장치 및 그에 관한 방법
KR101789327B1 (ko) * 2011-01-04 2017-10-24 엘지전자 주식회사 무선 통신 시스템에서 상향링크 전송방법 및 장치
CN102333293B (zh) * 2011-09-21 2014-07-09 电信科学技术研究院 一种小数据的传输方法和设备
CN104488308B (zh) * 2012-05-21 2019-04-23 三星电子株式会社 用于在移动通信系统中传送和接收数据的方法和设备
CN103731808A (zh) * 2012-10-15 2014-04-16 中兴通讯股份有限公司 发送、接收数据的方法、装置及数据的收发系统
US9420511B2 (en) * 2012-11-01 2016-08-16 Intel Corporation Signaling QoS requirements and UE power preference in LTE-A networks
CN104144524B (zh) * 2013-05-08 2018-05-11 电信科学技术研究院 一种小数据传输方法和演进基站及用户终端
KR102003273B1 (ko) * 2013-05-10 2019-10-01 주식회사 팬택 이중연결을 지원하는 무선 통신 시스템에서 단말 식별자 구성 방법 및 그 장치
US10129802B2 (en) 2013-12-06 2018-11-13 Idac Holdings, Inc. Layered connectivity in wireless systems
CN104754759B (zh) * 2013-12-31 2018-11-23 中国移动通信集团公司 一种rrc状态转移控制与数据传输方法、设备及系统
CN104981022B (zh) * 2014-04-04 2020-07-10 北京三星通信技术研究有限公司 数据传输的方法、基站及终端
CN117835198A (zh) 2015-04-22 2024-04-05 交互数字专利控股公司 用于3gpp网络中的小数据使用使能的设备和方法
US10299244B2 (en) 2015-06-19 2019-05-21 Qualcomm Incorporated Small data transmission in a wireless communications system
MX2018013639A (es) * 2016-05-11 2019-05-15 Sony Corp Control distribuido en sistemas inalambricos.
KR20180035638A (ko) * 2016-09-29 2018-04-06 삼성전자주식회사 RRC Inactive 및 active 상태에서 data 전송 결정 및 방법 및 장치
JP6935489B2 (ja) * 2017-04-28 2021-09-15 エルジー エレクトロニクス インコーポレイティドＬｇ Ｅｌｅｃｔｒｏｎｉｃｓ Ｉｎｃ． Ｅｄｔによってデータを送信する方法
US20180324854A1 (en) 2017-05-04 2018-11-08 Qualcomm Incorporated Uplink small data transmission for enhanced machine-type-communication (emtc) and internet of things (iot) communication
WO2019004690A1 (en) * 2017-06-27 2019-01-03 Lg Electronics Inc. METHOD AND APPARATUS FOR CONFIGURING MULTIPLE COMMON CONTROL CHANNELS IN A WIRELESS COMMUNICATION SYSTEM

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102387495A (zh) * 2010-08-30 2012-03-21 电信科学技术研究院 一种机器类通信设备的数据传输处理方法及设备
CN102457825A (zh) * 2010-10-15 2012-05-16 电信科学技术研究院 一种数据的传输方法和设备
CN102638900A (zh) * 2011-02-15 2012-08-15 电信科学技术研究院 一种连接建立方法及装置
CN102223715A (zh) * 2011-07-21 2011-10-19 电信科学技术研究院 一种数据传输方法及装置
WO2014181178A1 (en) * 2013-05-10 2014-11-13 Alcatel Lucent Data transmission method and device

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
See also references of EP3611947A4 *

Cited By (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2020120608A1 (en) * 2018-12-11 2020-06-18 Nordic Semiconductor Asa Efficient cellular communication
CN114026911A (zh) * 2019-06-28 2022-02-08 诺基亚技术有限公司 用于双连接性或载波聚合的早期数据传输
WO2021190278A1 (zh) * 2020-03-25 2021-09-30 展讯通信（上海）有限公司 业务的请求方法及装置

Also Published As

Publication number Publication date
KR102390889B1 (ko) 2022-04-26
CN110603829A (zh) 2019-12-20
CN115442775A (zh) 2022-12-06
US11606786B2 (en) 2023-03-14
BR112019023178A2 (pt) 2020-05-19
EP3611947A1 (en) 2020-02-19
JP7088603B2 (ja) 2022-06-21
US20220007345A1 (en) 2022-01-06
JP2020519193A (ja) 2020-06-25
US20200068547A1 (en) 2020-02-27
US11140676B2 (en) 2021-10-05
EP3611947A4 (en) 2020-02-19
WO2018201483A1 (zh) 2018-11-08
KR20200003126A (ko) 2020-01-08

Similar Documents

Publication Publication Date Title
WO2018201621A1 (zh) 数据传输的方法、终端设备和接入网设备
EP3399819B1 (en) Method and device for establishing radio resource control connection
WO2021169775A1 (zh) 数据传输方法与设备
US20180124598A1 (en) Grant-free transmission method, user equipment, access network device, and core network device
KR101487557B1 (ko) 공통제어채널의 데이터를 전송하는 방법
CN108541034B (zh) 处理状态的转换的装置及方法
KR102081013B1 (ko) 무선 단말, 무선국, 코어 네트워크 노드, 및 그것들에서의 방법
US10575349B2 (en) Device and method for handling a new radio connection in inter-system mobility
JP7305797B2 (ja) ランダムアクセスプリアンブル送信方法及び通信装置
WO2017096535A1 (zh) 连接建立的方法和装置
CN116368920A (zh) 用于在小数据传输期间处理非小数据传输无线电承载的方法及其装置
WO2022236484A1 (zh) Sdt失败上报的方法、终端设备和网络设备
CN115119311A (zh) 传输小数据的方法和通信装置
CN116962306A (zh) 数据传输的方法和通信装置
WO2022078867A1 (en) Methods, apparatuses and computer program for data transmission in inactive state
EP4002925A1 (en) Method and device for transmitting data
CN114930887A (zh) 一种密钥管理方法、通信装置
WO2022236499A1 (zh) Cg资源维护方法、终端设备和网络设备
US20220191098A1 (en) Wireless communication method and terminal device
WO2022027527A1 (zh) 信号的发送和接收方法、装置和通信系统
WO2022110048A1 (zh) 一种信息指示方法及装置、终端设备、网络设备
WO2023001149A1 (zh) 一种控制传输的方法及相关装置
EP3506699B1 (en) Data transmission methods, radio access network device and mobile terminal for configuring a preset data bearer
WO2020155174A1 (zh) 信息传输的方法和通信装置
CN116546489A (zh) 用于随机接入过程中数据处理的方法和装置

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 17908302

Country of ref document: EP

Kind code of ref document: A1

ENP Entry into the national phase

Ref document number: 2019560716

Country of ref document: JP

Kind code of ref document: A

NENP Non-entry into the national phase

Ref country code: DE

REG Reference to national code

Ref country code: BR

Ref legal event code: B01A

Ref document number: 112019023178

Country of ref document: BR

ENP Entry into the national phase

Ref document number: 2017908302

Country of ref document: EP

Effective date: 20191112

ENP Entry into the national phase

Ref document number: 20197035463

Country of ref document: KR

Kind code of ref document: A

ENP Entry into the national phase

Ref document number: 112019023178

Country of ref document: BR

Kind code of ref document: A2

Effective date: 20191104