WO2021057897A1 - 数据接收、发送方法、终端及网络侧设备 - Google Patents

数据接收、发送方法、终端及网络侧设备 Download PDF

Info

Publication number
WO2021057897A1
WO2021057897A1 PCT/CN2020/117717 CN2020117717W WO2021057897A1 WO 2021057897 A1 WO2021057897 A1 WO 2021057897A1 CN 2020117717 W CN2020117717 W CN 2020117717W WO 2021057897 A1 WO2021057897 A1 WO 2021057897A1
Authority
WO
WIPO (PCT)
Prior art keywords
terminal
data
message
rrc
edt
Prior art date
Legal status (The legal status 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 status listed.)
Ceased
Application number
PCT/CN2020/117717
Other languages
English (en)
French (fr)
Inventor
鲍炜
吴昱民
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Vivo Mobile Communication Co Ltd
Original Assignee
Vivo Mobile Communication Co Ltd
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 Vivo Mobile Communication Co Ltd filed Critical Vivo Mobile Communication Co Ltd
Priority to KR1020227010624A priority Critical patent/KR20220054658A/ko
Priority to EP20868248.4A priority patent/EP4037416B1/en
Priority to BR112022005577A priority patent/BR112022005577A2/pt
Priority to ES20868248T priority patent/ES3055181T3/es
Priority to PL20868248.4T priority patent/PL4037416T3/pl
Publication of WO2021057897A1 publication Critical patent/WO2021057897A1/zh
Priority to US17/702,672 priority patent/US12295060B2/en
Anticipated expiration legal-status Critical
Ceased legal-status Critical Current

Links

Images

Classifications

    • 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
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L5/00—Arrangements affording multiple use of the transmission path
    • H04L5/003—Arrangements for allocating sub-channels of the transmission path
    • H04L5/0053—Allocation of signalling, i.e. of overhead other than pilot signals
    • 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
    • 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
    • H04W74/00—Wireless channel access
    • H04W74/08—Non-scheduled access, e.g. ALOHA
    • H04W74/0833—Random access procedures, e.g. with 4-step access
    • H04W74/0836—Random access procedures, e.g. with 4-step access with 2-step access
    • 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 disclosure relates to the field of communication technology, and in particular to a data receiving and sending method, a terminal and a network side device.
  • LTE Long Term Evolution
  • MTC Machine-to-machine communication
  • NarrowBand Internet of Things NB-IOT
  • a typical scenario is the automatic reporting of a water meter, and its data transmission characteristic is about 12 hours to send a data packet with a size of about one hundred to several hundred bytes.
  • RRC Radio Resource Control
  • RRC signaling overhead LTE introduces Early Data Transmission (EDT) technology.
  • the embodiments of the present disclosure provide a data receiving and sending method, a terminal, and a network side device to solve the problem that how DL EDT data is transmitted is not clear in the related technology, and the network side does not know how to perform downlink early data transmission, and the reliability of communication cannot be guaranteed. .
  • some embodiments of the present disclosure provide a data receiving method applied to a terminal, including:
  • the network side device needs to perform early data transmission EDT, and the terminal is in the radio resource control RRC idle state or the RRC inactive state, in the process of random access with the network side device, receive the network EDT data sent by the side device and perform RRC state transition.
  • some embodiments of the present disclosure also provide a data sending method, which is applied to a network side device, including:
  • the EDT data is sent to the terminal, And instruct the terminal to perform RRC state transition.
  • some embodiments of the present disclosure also provide a terminal, including:
  • the execution module is used to perform the random access process with the network side device when the network side device needs to perform early data transmission EDT and the terminal is in the radio resource control RRC idle state or the RRC inactive state , Receiving the EDT data sent by the network side device, and performing RRC state transition.
  • some embodiments of the present disclosure also provide a terminal, including: a memory, a processor, and a computer program stored in the memory and running on the processor, and the computer program is implemented when the processor is executed The steps of the data receiving method described above.
  • some embodiments of the present disclosure also provide a network side device, including:
  • the sending module is used to send EDT data during the random access process with the terminal when the network side equipment needs to perform early data transmission EDT and the terminal is not in the radio resource control RRC idle state or the RRC inactive state To the terminal and instruct the terminal to perform RRC state transition.
  • some embodiments of the present disclosure also provide a network-side device, including: a memory, a processor, and a computer program stored in the memory and running on the processor, the computer program being executed by the processor When realizing the steps of the above-mentioned data sending method.
  • some embodiments of the present disclosure also provide a computer-readable storage medium on which a computer program is stored, and when the computer program is executed by a processor, the steps of the above-mentioned data receiving method are implemented Or the steps of the data sending method described above.
  • Figure 1 shows a typical uplink (UL) EDT control plane (Control Plane, CP) process diagram
  • FIG. 2 shows a schematic flowchart of a data receiving method according to some embodiments of the present disclosure
  • FIG. 3 shows a schematic flowchart of a data sending method according to some embodiments of the present disclosure
  • Figure 4 shows a schematic diagram of a terminal module of some embodiments of the present disclosure
  • FIG. 5 shows a structural block diagram of a terminal according to some embodiments of the present disclosure
  • FIG. 6 shows a schematic diagram of modules of a network side device according to some embodiments of the present disclosure
  • Fig. 7 shows a structural block diagram of a network-side device according to some embodiments of the present disclosure.
  • the characteristic of efficient small data transmission is that for non-connected user equipment (UE, also called terminal), it prevents them from performing radio resource control (Radio Resource Control, RRC) state changes and RRC information because they need to transmit small data.
  • RRC Radio Resource Control
  • the cost of the order, the purpose of small data transmission is completed through a very simple signaling process.
  • LTE Long Term Evolution
  • EDT Early Data Transmission
  • CP Control Plane
  • UP User Plane
  • the characteristic of the CP scheme is to piggyback the transmission of small data with RRC signaling, avoiding the establishment of a data radio bearer (DRB).
  • the uplink user data is directly attached to the uplink RRC early data request (RRCEarlyDataRequest) message in a form similar to a non-access stratum (NAS) message for transmission.
  • the downlink user data can optionally be attached to a downlink RRC early data complete (RRCEarlyDataComplete) message in a form similar to a NAS message for transmission. There is no need to enter the RRC connection state. All messages are sent on the signaling radio bearer 0 (SRB0) with the default configuration.
  • Radio Link Control (RLC) transparent mode (TM) does not support segmentation.
  • the typical UL EDT CP process is shown in Figure 1.
  • Msg1 sends a preamble (preamble) for time advance (TA) measurement and request
  • Msg2 allocates UL grant and TA
  • Msg3 performs uplink common control channel ( Common Control Channel (CCCH) transmission, generally in this case, is an RRC connection establishment request or an RRC connection recovery request
  • CCCH Common Control Channel
  • the Msg3 for the EDT purpose needs a larger UL grant to carry user data. Therefore, since the preamble is sent by the Msg1, the traditional random access channel (RACH) and the RACH accompanied by the EDT need to be performed on the network side.
  • the request is distinguished so that the network side can allocate sufficient resources for the UE in Msg2 for data transmission.
  • LTE DL EDT There is no implementation for LTE DL EDT. Some embodiments of the present disclosure address this problem and provide a data receiving and sending method, a terminal, and a network side device.
  • some embodiments of the present disclosure provide a data receiving method applied to a terminal, including:
  • Step 201 When the network side device needs to perform early data transmission EDT, and the terminal is in the radio resource control RRC idle state or the RRC inactive state, in the random access process with the network side device, receive EDT data sent by the network side device, and RRC state transition is performed;
  • EDT early data transmission
  • the EDT data is early small data
  • the EDT data is downlink data sent by the network side device to the terminal.
  • the fact that the terminal is in the radio resource control (RRC) idle state or the RRC inactive state means that the terminal is not in the RRC connected state.
  • RRC radio resource control
  • the above steps realize that the terminal receives the early small data during the random access process, and the terminal performs the RRC state transition according to the random access message.
  • the RRC state transition mainly refers to the RRC state transition of the terminal according to the random access message.
  • the idle state or the RRC inactive state enters the RRC connected state.
  • the early small data is transmitted to the terminal during the random access process between the terminal and the network side device, so as to ensure that the terminal can receive the early small data in time , It can reduce the transmission delay of early small data, and at the same time, it can make the terminal directly enter the RRC connection state, thereby improving the system efficiency, and solving the problem that the random access process and the EDT RRC process cannot work together.
  • Method 1 Directly transmit EDT data in the last step of random access signaling
  • step 201 is as follows:
  • Radio resource control RRC
  • the RRC connection setup message (RRCConnectionSetup message) carries the EDT data.
  • the network side device carries the EDT data in the RRCConnectionSetup message sent to the terminal, and the terminal receives the RRCConnectionSetup message, and obtains the EDT data by parsing the RRCConnectionSetup message.
  • the RRCConnectionSetup message includes a non-access stratum dedicated information indication field (DedicatedInfoNAS field), and the EDT data is located in the non-access stratum dedicated information indication field.
  • DedicatedInfoNAS field non-access stratum dedicated information indication field
  • the network side device When the network side device initiates the downlink early small data transmission (DL EDT) process and there is a small amount of data to be sent to the terminal, if the terminal is in an idle state at this time, the network side device sends the data through the control plane DL EDT.
  • the network side device explicitly carries this is a DL EDT indication in the paging message, so that the terminal can initiate the random access process related to early small data transmission.
  • the specific process is as follows:
  • Step A10 The core network has downlink data about a certain terminal to be sent, and the terminal is currently in an idle state, the core network first determines whether the data transmission meets the DL EDT condition, and if the DL EDT condition is met, it sends to the terminal's tracking area
  • the network-side device for example, eNB/gNB
  • TA tracking area
  • the bit DL EDT mark can also carry DL data size, etc.), where the conditions for satisfying DL EDT can be one of the following or a combination:
  • the amount of data to be sent by the terminal is less than a certain threshold
  • the delay can tolerate a certain length and above.
  • Step A11 When the network side device receives the paging instruction message from the core network, it judges whether to initiate a DL EDT-related paging according to its own state, and if it needs to initiate a DL EDT paging, it carries the DL EDT instruction in the paging message , If it is not needed, initiate a normal paging process, the main judgment basis includes the following:
  • Step A12 The terminal receives a paging message containing a DL EDT indication (if it is a normal paging message, the terminal initiates according to the existing process);
  • Step A13 The terminal initiates a random access process
  • the terminal selects a 4-step random access (4-step RACH) process, it selects an EDT-related preamble to initiate a random access message one (Msg1) process;
  • the terminal selects a 2-step random access (2-step RACH) process, it selects an uplink message with itself (for example, an authentication message, identity information, and/or RRC early data request (RRCEarlyDataRequest) of the terminal is required).
  • an uplink message with itself for example, an authentication message, identity information, and/or RRC early data request (RRCEarlyDataRequest) of the terminal is required.
  • the physical uplink shared channel (PUSCH) resource size of the matching size and the corresponding preamble initiates the MsgA process;
  • Step A14 The network side device receives the Msg1 or MsgA of the terminal;
  • the specific execution process of the network side device is also different, specifically:
  • the network side device knows that the EDT process is required through the preamble, and the uplink grant (UL grant) allocated to the terminal in the message 2 (Msg2) needs to be larger than that of ordinary random access to meet
  • the terminal transmits messages (for example, uplink authentication message, identity information, and/or RRCEarlyDataRequest, etc.);
  • the network side device can obtain the identity and authentication information of the terminal from it, and if there is authentication information, it will be sent to the core network for authentication. After success, it will perform terminal authentication from the core network according to the identity of the terminal. Data acquisition.
  • the downlink data of the terminal for example, a large amount of downlink data arrives, it is not suitable for transmission only through DL EDT) or other conditions (for example, the terminal has a new service trigger, such as voice or video, etc.), it is required To make the terminal enter the connected state, the network side will send a small amount of data to the terminal simultaneously through the RRCConnectionSetup message via MsgB;
  • Step A15 The terminal side receives the Msg2 or MsgB message sent by the network side device;
  • the terminal obtains the timing advance (TA) information and UL grant in Msg2, and organizes message three (Msg3) to send, where the Msg3 information is similar to the information sent on the PUSCH in MsgA.
  • TA timing advance
  • Msg3 message three
  • the terminal when the terminal receives the MsgB, it parses the RRCConnectionSetup message and the data in it, and performs data processing and connection establishment operations.
  • the 2-step RACH process ends, and at the same time, the transmission of the predetermined data is completed and the terminal is sent to RRC. Connection state conversion.
  • Step A16 The network side device receives the targeted Msg3 message
  • the network side device parses the Msg3 message, and can obtain the identity and authentication information of the terminal from it. If there is authentication information, it is sent to the core network for authentication. After success, it obtains terminal data from the core network according to the terminal identity. If the terminal needs to enter the connected state according to the downlink data of the terminal (for example, the arrival of a large amount of downlink data, which is not suitable for transmission only through DL EDT) or other conditions (for example, the terminal has a new service trigger, such as voice or video, etc.), the terminal needs to enter the connected state, then the network side Use Msg4 to simultaneously piggyback a small amount of data to the terminal through the RRCConnectionSetup message. For example, add a DedicatedInfoNAS field to the message. This field is optional and used to piggyback early downlink data.
  • Step A17 The terminal receives the Msg4 message of the network
  • the terminal When the terminal receives Msg4, it parses the RRCConnectionSetup message and the data in it, and performs data processing and connection establishment operations.
  • the 4-step RACH process ends, which not only completes the transmission of the predetermined data, but also makes the terminal transition to the RRC connection state. So far, the 4-step RACH process ends.
  • the above implementation process solves the problem that the random access process and the EDT RRC process cannot work together.
  • the terminal enters the RRC connected state from the RRC idle state or the RRC inactive state, which reduces the transmission delay of early small data and at the same time improves the system efficiency.
  • the data field is optional and does not affect the existing normal process.
  • Method 2 Combine the last step of random access signaling with the RRC early data completion message and send it
  • step 201 is as follows:
  • the RRC early data completion message carries the EDT data.
  • this situation refers to that the network side device simultaneously sends the RRC connection establishment message and the RRC early data completion message to the terminal, and the terminal performs subsequent operations according to the received message.
  • the specific behavior of receiving EDT data sent by the network-side device and performing RRC state transition includes:
  • the terminal does not perform the operation of media access control (MAC) entity reset, that is, the terminal cannot enter the idle state according to the RRC early data completion message.
  • MAC media access control
  • the terminal may first perform the acquisition of the EDT data in the RRC early data completion message, and the terminal does not perform the operation of entering the idle state, and then perform the operation according to the RRC connection establishment message Perform state transition operations; in some cases, the terminal may first perform state transition operations based on the RRC connection establishment message, and then perform the acquisition of the EDT data in the RRC early data completion message, and the terminal The operation to enter the idle state is not performed.
  • the combined transmission of the RRC connection establishment message and the RRC early data completion message can be performed in one of the following situations:
  • the pre-appointed message grouping order the grouping order also implicitly indicates the execution order of the message received by the terminal.
  • the terminal first executes the RRC early data completion message, that is, the terminal First obtain the EDT data therein according to the RRC early data complete message, but the terminal does not perform the operation of entering the idle state according to the RRC early data complete message, and then the terminal executes the process of entering the connected state according to the RRC connection establishment message.
  • this method adopts the RRCEarlyDataComplete message to carry the EDT data, and combines the RRCConnectionSetup message and the RRCEarlyDataComplete message to send, which also meets the needs of transmitting a small amount of data and can complete the state transition of the terminal the goal of.
  • the RRCConnectionSetup message makes the terminal enter the RRC connected state
  • the RRCEarlyDataComplete message makes the terminal enter the RRC idle state after extracting the data
  • sending these two messages together will cause confusion and uncertainty to the behavior of the terminal, and the execution order needs to be further clarified.
  • the RRC early data completion message is set before the RRC connection establishment message to clarify the execution sequence of the terminal.
  • Step A20 The core network has to send downlink data about a certain terminal, and the terminal is currently in an idle state, the core network first judges whether the data transmission meets the DL EDT condition, and if it meets the DL EDT condition, it sends it to the terminal's tracking area
  • the network-side device for example, eNB/gNB
  • TA tracking area
  • the bit DL EDT mark can also carry DL data size, etc.), where the conditions for satisfying DL EDT can be one of the following or a combination:
  • the amount of data to be sent by the terminal is less than a certain threshold
  • the delay can tolerate a certain length and above.
  • Step A21 When the network side device receives the paging instruction message from the core network, it judges whether to initiate a DL EDT-related paging according to its own state, and if it needs to initiate a DL EDT paging, it carries the DL EDT instruction in the paging message , If it is not needed, initiate a normal paging process, the main judgment basis includes the following:
  • Step A22 The terminal receives a paging message containing a DL EDT indication (if it is a normal paging message, the terminal initiates according to the existing process);
  • Step A23 The terminal initiates a random access process
  • the terminal selects the 4-step RACH process, select the EDT-related preamble to initiate the random access message one (Msg1) process;
  • the terminal selects the 2-step RACH process, it selects the physical uplink sharing that matches the size of its own uplink message (for example, the authentication message of the terminal, the identity information and/or the RRC early data request (RRCEarlyDataRequest), etc.) size matching Channel (PUSCH) resource size and corresponding preamble to initiate the MsgA process;
  • the physical uplink sharing matches the size of its own uplink message (for example, the authentication message of the terminal, the identity information and/or the RRC early data request (RRCEarlyDataRequest), etc.) size matching Channel (PUSCH) resource size and corresponding preamble to initiate the MsgA process;
  • PUSCH size matching Channel
  • Step A24 The network side device receives the Msg1 or MsgA of the terminal;
  • the network side device knows that the EDT process is required through the preamble, and the uplink grant (UL grant) allocated to the terminal in the message 2 (Msg2) needs to be larger than that of ordinary random access to meet
  • the terminal transmits messages (such as uplink authentication messages, identity information, and/or RRCEarlyDataRequest, etc.);
  • the network side device can obtain the identity and authentication information of the terminal from it, and if there is authentication information, it will be sent to the core network for authentication. After success, it will perform terminal authentication from the core network according to the identity of the terminal. Data acquisition.
  • the network-side device sends the RRCArlyDataComplete message and the RRCConnectionSetup message carrying a small amount of data to the target at the same time with MsgB. It is necessary to pay attention to putting the RRCEarlyDataComplete message in the front and the RRCConnectionSetup message in the back of the packet to indicate implicitly. Terminal execution sequence.
  • Step A25 The terminal side receives the Msg2 or MsgB message sent by the network side device;
  • the terminal obtains the timing advance (TA) information and UL grant in Msg2, and organizes message three (Msg3) to send, where the Msg3 information is similar to the information sent on the PUSCH in MsgA.
  • TA timing advance
  • Msg3 message three
  • the terminal when the terminal receives the MsgB, it parses the RRCArlyDataComplete message and the RRCConnectionSetup message in order from front to back, and at this time, the terminal knows that there are two signalings for data piggybacking and RRC state transition, so when the terminal processes the RRCEarlyDataComplete message , Only the data can be processed (for example, the data in the NAS container is submitted to the higher level), no other operations (for example, MAC entity resetting is not required, etc.). What needs to be explained is what the terminal needs to perform at this time The operation can be clearly specified in the standard, which is different from the traditional receiving RRCEarlyDataComplete message), and then execute the RRCConnectionSetup message to establish the connection.
  • the 2-step RACH process ends, and at the same time, the transmission of the predetermined data is completed and the terminal is also enabled. The conversion to the RRC connected state is performed.
  • Step A26 The network side device receives the targeted Msg3 message
  • the network side device parses the Msg3 message, and can obtain the identity and authentication information of the terminal from it. If there is authentication information, it is sent to the core network for authentication. After success, it obtains terminal data from the core network according to the terminal identity. If the terminal needs to enter the RRC connection state according to the downlink data of the terminal (for example, the arrival of a large number of downlink data, which is not suitable for transmission only through DL EDT) or other conditions (for example, the terminal has a new service trigger, such as voice or video, etc.), the terminal needs to enter the RRC connection state.
  • the side sends the RRCArlyDataComplete message and the RRCConnectionSetup message carrying a small amount of data to the terminal at the same time with Msg4. It is necessary to pay attention to putting the RRCEarlyDataComplete message in front and the RRCConnectionSetup message behind it to implicitly indicate the execution order of the terminal.
  • Step A27 The terminal receives the Msg4 message of the network
  • the terminal When the terminal receives Msg4, it parses the RRCArlyDataComplete message and the RRCConnectionSetup message in order from front to back, and at this time, the terminal knows that there are two signalings for data piggybacking and RRC state transition, so when the terminal processes the RRCEarlyDataComplete message, it only performs data Just do the processing, and there is no need to perform other operations to return to the RRC idle state, such as MAC entity reset and other operations. (It should be noted that what operations the terminal needs to perform at this time can be clearly specified in the standard. There is a difference between receiving the RRCEarlyDataComplete message), and then execute the RRCConnectionSetup message to perform the operation of connection establishment.
  • the 4-step RACH process ends, and at the same time, the transmission of the predetermined data is completed and the terminal is converted to the RRC connection state.
  • the above implementation process solves the problem that the random access process and the EDT RRC process cannot work together.
  • the RRC connection establishment message and the RRC early data completion message are sent to the terminal together, and the grouping of the two messages is used.
  • the sequence implicitly instructs the terminal to execute the sequence of two messages, which not only meets the need to transmit a small amount of data, but also realizes that the terminal enters the RRC connected state from the RRC idle state or the RRC inactive state, which reduces the transmission delay of early small data and improves at the same time
  • the system efficiency is improved, and the existing signaling format is selected for this method, and the standard workload is small.
  • the terminal receives the message execution order indication information sent by the network side device;
  • the message execution order indication information is used to instruct the terminal to first obtain the EDT data in the RRC early data completion message, and then perform state transition according to the RRC connection establishment message;
  • the message execution sequence indication information is used to instruct the terminal to first perform state transition according to the RRC connection establishment message, and then obtain the EDT data in the RRC early data completion message.
  • this situation means that the network side device needs to send an indication message to indicate the execution order of the RRC connection establishment message and the RRC early data completion message.
  • the indication information may be located in the combined transmission. Radio resource control RRC connection establishment message and RRC early data completion message MAC header or control information.
  • this situation refers to the use of different logical channel identifiers to distinguish two messages.
  • the terminal receives the combined radio resource control RRC connection establishment message and the RRC early data completion message, it can be based on the different The logical channel identifier determines the execution order of the two messages.
  • the RRC early data complete message carries first indication information, and the first indication information is used to instruct the terminal to acquire the EDT data according to the RRC early data complete message;
  • RRC early data completion message which is used to instruct the terminal to obtain the EDT data carried in the RRC early data completion message when it executes the RRC early data completion message, and the terminal does not follow this
  • the RRC early data completion message executes the operation to enter the idle state.
  • case 2 case 3, and case 4 are all explicit instructions, and the execution order of the terminal is indicated by explicitly indicating the execution order or special marking the RRCEarlyDataComplete message; the following is this case
  • the following specific implementation process is illustrated as follows.
  • Step A30 The core network has to send downlink data about a certain terminal, and the terminal is currently in an idle state, the core network first determines whether the data transmission meets the DL EDT condition, and if the DL EDT condition is met, it will send it to the terminal's tracking area
  • the network-side device for example, eNB/gNB
  • TA tracking area
  • the bit DL EDT mark can also carry DL data size, etc.), where the conditions for satisfying DL EDT can be one of the following or a combination:
  • the amount of data to be sent by the terminal is less than a certain threshold
  • the delay can tolerate a certain length and above.
  • Step A31 When the network side device receives the paging instruction message from the core network, it judges whether to initiate a DL EDT-related paging according to its own state, and if it needs to initiate a DL EDT paging, it carries the DL EDT instruction in the paging message , If it is not needed, initiate a normal paging process, the main judgment basis includes the following:
  • Step A32 The terminal receives a paging message containing a DL EDT indication (if it is a normal paging message, the terminal initiates according to the existing process);
  • Step A33 The terminal initiates a random access process
  • the terminal selects the 4-step RACH process, select the EDT-related preamble to initiate the random access message one (Msg1) process;
  • the terminal selects the 2-step RACH process, it selects the physical uplink shared channel that matches the size of its own uplink message (for example, the authentication message of the terminal, identity information, and/or RRC early data request (RRCEarlyDataRequest), etc.) (PUSCH) Resource size and corresponding preamble to initiate the MsgA process;
  • PUSCH Physical uplink shared channel that matches the size of its own uplink message (for example, the authentication message of the terminal, identity information, and/or RRC early data request (RRCEarlyDataRequest), etc.)
  • Step A34 The network side device receives the Msg1 or MsgA of the terminal;
  • the network side device knows that the EDT process is required through the preamble, and the uplink grant (UL grant) allocated to the terminal in the message 2 (Msg2) needs to be larger than that of ordinary random access to meet
  • the terminal transmits messages (such as uplink authentication messages, identity information, and/or RRCEarlyDataRequest, etc.);
  • the network side device can obtain the identity and authentication information of the terminal from it. If there is authentication information, it will be sent to the core network for authentication. After success, the terminal data will be obtained from the core network according to the identity of the terminal.
  • the terminal needs to enter RRC In the connected state, the network side sends the RRCEarlyDataComplete message and the RRCConnectionSetup message carrying a small amount of data to the terminal at the same time through MsgB, and uses at least one of the following methods to make an explicit indication:
  • the RRCEarlyDataComplete message needs to be executed first, and the RRCConnectionSetup message needs to be executed later;
  • a Logical Channel Identifier can be assigned to the CCCH, specifically for the RRCEarlyDataComplete message that only processes data.
  • Step A35 The terminal side receives the Msg2 or MsgB message sent by the network side device;
  • the terminal obtains the timing advance (TA) information and UL grant in Msg2, and organizes message three (Msg3) to send, where the Msg3 information is similar to the information sent on the PUSCH in MsgA.
  • TA timing advance
  • Msg3 message three
  • the terminal when the terminal receives the MsgB, it parses the RRCArlyDataComplete message and the RRCConnectionSetup message in the order indicated explicitly, and at this time, the terminal knows that there are two signalings for data piggybacking and RRC state transition. Therefore, when the terminal processes the RRCEarlyDataComplete message , Only the data is processed, no other operations to return to the RRC idle state are required (for example, no MAC entity reset is required, etc.). It should be noted that what operations the terminal needs to perform at this time can be specified in the standard It is well specified, which is different from the traditional receiving RRCEarlyDataComplete message), and then execute the RRCConnectionSetup message to perform the operation of connection establishment.
  • the 2-step RACH process ends, and at the same time, the transmission of the predetermined data is completed and the terminal is in the RRC connection state. Conversion; or,
  • the terminal can execute the RRCArlyDataComplete message and the RRCConnectionSetup message at will.
  • the terminal because the RRCArlyDataComplete message has a special instruction, the terminal only needs to process the data when processing the RRCArlyDataComplete message, and there is no need to do anything else to return to RRC. Idle state operations (for example, do not need to perform operations such as MAC entity resetting. It should be noted that what operations the terminal needs to perform at this time can be clearly specified in the standard. It is different from the traditional receiving RRCEarlyDataComplete message, and is different from the above display instructions. The operations when the two messages are executed in sequence may also be different); or,
  • the RRCEarlyDataComplete message is executed first and then the RRCConnectionSetup message. Because the RRCEarlyDataComplete message has a special instruction, the terminal is processing When the RRCEarlyDataComplete message is used, only the data is processed, and other operations to return to the RRC idle state are not required (for example, there is no need to perform operations such as MAC entity reset. It should be noted that what operations the terminal needs to perform at this time can be clarified.
  • the terminal When the terminal receives MsgB, it uses different logical channel identifiers according to the RRCEarlyDataComplete message and the RRCConnectionSetup message.
  • the terminal When processing the RRCEarlyDataComplete message, the terminal only needs to process the data, and does not need to perform other operations to return to the RRC idle state (for example, no need to perform MAC entity reset and other operations, it needs to be explained that what operations the terminal needs to perform at this time can be clearly specified in the standard, which is different from the traditional receiving RRCEarlyDataComplete message), and then execute the RRCConnectionSetup message to perform the operation of connection establishment.
  • the RACH process ends, and at the same time, the transmission of the predetermined data is completed and the terminal is converted to the RRC connected state.
  • Step A36 The network side device receives the targeted Msg3 message
  • the network side device parses the Msg3 message, and can obtain the targeted identity and authentication information from it. If there is authentication information, it will be sent to the core network for authentication. After success, it will obtain terminal data from the core network according to the terminal identity. If the terminal needs to enter the connected state according to the downlink data of the terminal (for example, the arrival of a large amount of downlink data, which is not suitable for transmission only through DL EDT) or other conditions (for example, the terminal has a new service trigger, such as voice or video, etc.), the terminal needs to enter the connected state, then the network side Use Msg4 to send the RRCEarlyDataComplete message and the RRCConnectionSetup message carrying a small amount of data to the terminal at the same time, and use at least one of the following methods to make an explicit indication:
  • an explicit content indicates the execution sequence of the terminal
  • the RRCEarlyDataComplete message needs to be executed first, and the RRCConnectionSetup message needs to be executed later;
  • An LCID can be allocated to the CCCH, specifically for the RRCEarlyDataComplete message that only processes data.
  • Step A37 The terminal receives the Msg4 message of the network
  • the terminal parses the RRCArlyDataComplete message and the RRCConnectionSetup message in the order of the explicit instructions. At this time, the terminal knows that there are two signalings for data piggybacking and RRC state transition. Therefore, when the terminal processes the RRCArlyDataComplete message, it only performs data Just do the processing and do not need to perform other operations to return to the RRC idle state (for example, do not need to perform MAC entity reset and other operations. It should be noted that what operations the terminal needs to perform at this time can be clearly specified in the standard. It is different from the traditional receiving RRCEarlyDataComplete message), and then execute the RRCConnectionSetup message to establish the connection.
  • the 4-step RACH process ends, and at the same time, the transmission of the predetermined data is completed and the terminal is converted to the RRC connection state; or ,
  • the terminal can execute the RRCArlyDataComplete message and the RRCConnectionSetup message at will.
  • the terminal because the RRCArlyDataComplete message has a special instruction, the terminal only needs to process the data when processing the RRCArlyDataComplete message, and there is no need to do anything else to return to RRC. Idle state operations (for example, do not need to perform operations such as MAC entity resetting. It should be noted that what operations the terminal needs to perform at this time can be clearly specified in the standard. It is different from the traditional receiving RRCEarlyDataComplete message, and is different from the above display instructions. The operations when the two messages are executed in sequence may also be different); or,
  • the RRCEarlyDataComplete message is executed first and then the RRCConnectionSetup message. Because the RRCEarlyDataComplete message has a special instruction, the terminal is processing When the RRCEarlyDataComplete message is used, only the data is processed, and other operations to return to the RRC idle state are not required (for example, there is no need to perform operations such as MAC entity reset. It should be noted that what operations the terminal needs to perform at this time can be clarified.
  • the terminal When receiving Msg4, the terminal uses different logical channel identifiers according to the RRCEarlyDataComplete message and the RRCConnectionSetup message.
  • the terminal When processing the RRCEarlyDataComplete message, the terminal only needs to process the data, and does not need to perform other operations to return to the RRC idle state (for example, do not need to perform MAC entity reset and other operations, it needs to be explained that what operations the terminal needs to perform at this time can be clearly specified in the standard, which is different from the traditional receiving RRCEarlyDataComplete message), and then execute the RRCConnectionSetup message to perform the operation of connection establishment.
  • the RACH process ends, and at the same time, the transmission of the predetermined data is completed and the terminal is converted to the RRC connected state.
  • the RRC connection establishment message and the RRC early data completion message are sent to the terminal together, and additional instructions are used to explicitly indicate
  • the terminal executes the sequence of two messages, which not only meets the need to transmit a small amount of data, but also realizes that the terminal enters the RRC connected state from the RRC idle state or the RRC inactive state, which reduces the transmission delay of early small data and improves system efficiency. And in this way, the related message format is improved to make the behavior of the terminal clearer.
  • Step A40 The core network has downlink data about a certain terminal to be sent, and the terminal is currently in an idle state, the core network first determines whether the data transmission meets the DL EDT condition, and if it meets the DL EDT condition, it sends to the terminal's tracking area
  • the network-side device for example, eNB/gNB
  • TA tracking area
  • the bit DL EDT mark can also carry DL data size, etc.), where the conditions for satisfying DL EDT can be one of the following or a combination:
  • the amount of data to be sent by the terminal is less than a certain threshold
  • the delay can tolerate a certain length and above.
  • Step A41 When the network side device receives the paging instruction message from the core network, it judges whether to initiate a DL EDT-related paging according to its own state. If it needs to initiate a DL EDT paging, it carries the DL EDT instruction in the paging message , If it is not needed, initiate a normal paging process, the main judgment basis includes the following:
  • Step A42 The terminal receives a paging message containing a DL EDT indication (if it is a normal paging message, the terminal initiates according to the existing process);
  • Step A43 The terminal initiates a random access process
  • the terminal selects the 4-step RACH process, select the EDT-related preamble to initiate the random access message one (Msg1) process;
  • the terminal selects the 2-step RACH process, it selects the physical uplink shared channel that matches the size of its own uplink message (for example, the authentication message of the terminal, the identity information and/or the RR Early Data Request (RRCEarlyDataRequest), etc.) size matching (PUSCH) Resource size and corresponding preamble to initiate the MsgA process;
  • the physical uplink shared channel that matches the size of its own uplink message (for example, the authentication message of the terminal, the identity information and/or the RR Early Data Request (RRCEarlyDataRequest), etc.) size matching (PUSCH) Resource size and corresponding preamble to initiate the MsgA process;
  • Step A44 The network side device receives the Msg1 or MsgA of the terminal;
  • the specific execution process of the network side device is also different, specifically:
  • the network side device knows that the EDT process is required through the preamble transmission, and the uplink grant (UL grant) allocated to the terminal in the message 2 (Msg2) needs to be larger than that of ordinary random access. Satisfy the terminal to transmit messages (for example, uplink authentication message, identity information and/or RRCEarlyDataRequest, etc.);
  • the network can obtain the identity and authentication information of the terminal from it. If it finds that there is a need to transfer the terminal to the RRC connection state at this time, it directly sends the RRCConnectionSetup message in the MsgB message;
  • Step A45 The terminal side receives the Msg2 or MsgB message sent by the network side device;
  • the terminal obtains the timing advance (TA) information and UL grant in Msg2, and organizes message three (Msg3) to send, where the Msg3 information is similar to the information sent on the PUSCH in MsgA.
  • TA timing advance
  • Msg3 message three
  • the terminal receives the MsgB, establishes an RRC connection according to the content of the RRCConnectionSetup message, the 2-step RACH process ends, and the network side device establishes a dedicated data bearer for the terminal, and transmits early small data in the dedicated data bearer.
  • Step A46 The network side device receives the targeted Msg3 message
  • the network parses the Msg3 message, from which it can obtain the terminal's identity and authentication information, etc. If it finds that there is a need to transfer the terminal to the RRC connection state at this time, it directly sends the RRCConnectionSetup message in the Msg4 message;
  • Step A47 The terminal receives the Msg4 message of the network
  • the terminal receives Msg4, establishes an RRC connection according to the content of the RRCConnectionSetup message, the 4-step RACH process ends, and the network side device establishes a dedicated data bearer for the terminal, and transmits early small data in the dedicated data bearer.
  • this method is initiated according to the DL EDT process when it is initiated, and the subsequent network side changes according to requirements and converts it into a normal RRC connection establishment process and then performs the data bearer establishment and data transmission process.
  • some embodiments of the present disclosure ensure the coordination of the random access process and the EDT RRC process, improve the efficiency of downlink small data transmission, complete small data transmission and signaling transmission, and reduce time to a certain extent. Extension, which greatly improves the system efficiency.
  • some embodiments of the present disclosure also provide a data sending method, which is applied to a network side device, including:
  • Step 301 When the network side device needs to perform early data transmission EDT, and the terminal is not in the radio resource control RRC idle state or the RRC inactive state, the EDT data is sent to the terminal during the random access process with the terminal. The terminal, and instruct the terminal to perform RRC state transition.
  • the sending EDT data to the terminal includes:
  • the EDT data is carried in the RRC connection establishment message and sent to the terminal.
  • the RRC connection establishment message includes a non-access stratum dedicated information indication field, and the EDT data is located in the non-access stratum dedicated information indication field.
  • the sending EDT data to the terminal includes:
  • the RRC early data completion message carries the EDT data.
  • the RRC early data completion message is located before the RRC connection establishment message.
  • the data sending method further includes:
  • the message execution order indication information is used to instruct the terminal to first obtain the EDT data in the RRC early data completion message, and then perform state transition according to the RRC connection establishment message; or,
  • the message execution sequence indication information is used to instruct the terminal to first perform state transition according to the RRC connection establishment message, and then obtain the EDT data in the RRC early data completion message.
  • the RRC early data completion message and the RRC connection establishment message are marked with different logical channel identifiers.
  • the RRC early data complete message carries first indication information, and the first indication information is used to instruct the terminal to acquire the EDT data according to the RRC early data complete message.
  • a terminal 400 including:
  • the execution module 401 is configured to perform a random access process with the network side device when the network side device needs to perform early data transmission EDT, and the terminal is in the radio resource control RRC idle state or the RRC inactive state , Receiving the EDT data sent by the network side device, and performing RRC state transition.
  • the execution module 401 is configured to:
  • the RRC connection establishment message carries the EDT data.
  • the RRC connection establishment message includes a non-access stratum dedicated information indication field, and the EDT data is located in the non-access stratum dedicated information indication field.
  • the execution module 401 is configured to:
  • the RRC early data completion message carries the EDT data.
  • the RRC early data completion message is located before the RRC connection establishment message.
  • the terminal further includes:
  • the instruction receiving module is used to receive the message execution sequence instruction information sent by the network side device
  • the message execution order indication information is used to instruct the terminal to first obtain the EDT data in the RRC early data completion message, and then perform state transition according to the RRC connection establishment message; or,
  • the message execution sequence indication information is used to instruct the terminal to first perform state transition according to the RRC connection establishment message, and then obtain the EDT data in the RRC early data completion message.
  • the RRC early data completion message and the RRC connection establishment message are marked with different logical channel identifiers.
  • the RRC early data complete message carries first indication information, and the first indication information is used to instruct the terminal to acquire the EDT data according to the RRC early data complete message.
  • execution module 401 is configured to implement:
  • the implementation manner for the terminal not to perform the operation of entering the idle state is specifically as follows:
  • the terminal does not perform the operation of resetting the media access control MAC entity.
  • the terminal embodiment is a terminal corresponding to the above-mentioned data receiving method applied to the terminal, and all the implementation manners of the above-mentioned embodiment are applicable to the terminal embodiment, and the same technical effect can be achieved.
  • Fig. 5 is a schematic diagram of the hardware structure of a terminal for implementing some embodiments of the present disclosure.
  • the terminal 50 includes but is not limited to: a radio frequency unit 510, a network module 520, an audio output unit 530, an input unit 540, a sensor 550, a display unit 560, a user input unit 570, an interface unit 580, a memory 590, a processor 511, and a power supply 512 and other parts.
  • a radio frequency unit 510 includes but is not limited to: a radio frequency unit 510, a network module 520, an audio output unit 530, an input unit 540, a sensor 550, a display unit 560, a user input unit 570, an interface unit 580, a memory 590, a processor 511, and a power supply 512 and other parts.
  • the terminal structure shown in FIG. 5 does not constitute a limitation on the terminal, and the terminal may include more or fewer components than those shown in the figure, or combine certain components, or arrange different components.
  • the terminal includes, but is not limited to, a mobile phone, a tablet computer, a notebook
  • the radio frequency unit 510 is used to perform random access with the network side device when the network side device needs to perform early data transmission EDT, and the terminal is in the radio resource control RRC idle state or the RRC inactive state.
  • the processor 511 performs RRC state transition.
  • the terminal receives the EDT data sent by the network side device during the random access process, which reduces the data transmission delay, improves the system efficiency, and ensures the reliability of network communication.
  • the radio frequency unit 510 can be used for receiving and sending signals during the process of sending and receiving information or talking. Specifically, after receiving the downlink data from the network side device, it is processed by the processor 511. ; In addition, the uplink data is sent to the network side device.
  • the radio frequency unit 510 includes, but is not limited to, an antenna, at least one amplifier, a transceiver, a coupler, a low noise amplifier, a duplexer, and the like.
  • the radio frequency unit 510 can also communicate with the network and other devices through a wireless communication system.
  • the terminal provides users with wireless broadband Internet access through the network module 520, such as helping users to send and receive emails, browse web pages, and access streaming media.
  • the audio output unit 530 may convert the audio data received by the radio frequency unit 510 or the network module 520 or stored in the memory 590 into an audio signal and output it as sound. Moreover, the audio output unit 530 may also provide audio output related to a specific function performed by the terminal 50 (for example, call signal reception sound, message reception sound, etc.).
  • the audio output unit 530 includes a speaker, a buzzer, a receiver, and the like.
  • the input unit 540 is used to receive audio or video signals.
  • the input unit 540 may include a graphics processing unit (GPU) 541 and a microphone 542, and the graphics processor 541 is configured to respond to still pictures or video images obtained by an image capture device (such as a camera) in a video capture mode or an image capture mode.
  • the data is processed.
  • the processed image frame may be displayed on the display unit 560.
  • the image frame processed by the graphics processor 541 can be stored in the memory 590 (or other storage medium) or sent via the radio frequency unit 510 or the network module 520.
  • the microphone 542 can receive sound, and can process such sound into audio data.
  • the processed audio data can be converted into a format that can be sent to the mobile communication network side device via the radio frequency unit 510 for output in the case of a telephone call mode.
  • the terminal 50 also includes at least one sensor 550, such as a light sensor, a motion sensor, and other sensors.
  • the light sensor includes an ambient light sensor and a proximity sensor.
  • the ambient light sensor can adjust the brightness of the display panel 561 according to the brightness of the ambient light.
  • the proximity sensor can close the display panel 561 and/or when the terminal 50 is moved to the ear. Or backlight.
  • the accelerometer sensor can detect the magnitude of acceleration in various directions (usually three-axis), and can detect the magnitude and direction of gravity when stationary, and can be used to identify terminal posture (such as horizontal and vertical screen switching, related games, Magnetometer posture calibration), vibration recognition related functions (such as pedometer, percussion), etc.; sensor 550 can also include fingerprint sensors, pressure sensors, iris sensors, molecular sensors, gyroscopes, barometers, hygrometers, thermometers, infrared Sensors, etc., will not be repeated here.
  • the display unit 560 is used to display information input by the user or information provided to the user.
  • the display unit 560 may include a display panel 561, and the display panel 561 may be configured in the form of a liquid crystal display (LCD), an organic light-emitting diode (OLED), etc.
  • LCD liquid crystal display
  • OLED organic light-emitting diode
  • the user input unit 570 may be used to receive inputted numeric or character information, and generate key signal input related to user settings and function control of the terminal.
  • the user input unit 570 includes a touch panel 571 and other input devices 572.
  • the touch panel 571 also called a touch screen, can collect the user's touch operations on or near it (for example, the user uses any suitable objects or accessories such as fingers, stylus, etc.) on the touch panel 571 or near the touch panel 571. operating).
  • the touch panel 571 may include two parts, a touch detection device and a touch controller.
  • the touch detection device detects the user's touch position, and detects the signal brought by the touch operation, and transmits the signal to the touch controller; the touch controller receives the touch information from the touch detection device, converts it into contact coordinates, and then sends it To the processor 511, the command sent by the processor 511 is received and executed.
  • the touch panel 571 can be implemented in multiple types such as resistive, capacitive, infrared, and surface acoustic wave.
  • the user input unit 570 may also include other input devices 572.
  • other input devices 572 may include, but are not limited to, a physical keyboard, function keys (such as volume control buttons, switch buttons, etc.), trackball, mouse, and joystick, which will not be repeated here.
  • the touch panel 571 can cover the display panel 561.
  • the touch panel 571 detects a touch operation on or near it, it transmits it to the processor 511 to determine the type of the touch event, and then the processor 511 determines the type of the touch event according to the touch.
  • the type of event provides corresponding visual output on the display panel 561.
  • the touch panel 571 and the display panel 561 are used as two independent components to realize the input and output functions of the terminal, in some embodiments, the touch panel 571 and the display panel 561 can be integrated Realize the input and output functions of the terminal, which are not limited here.
  • the interface unit 580 is an interface for connecting an external device and the terminal 50.
  • the external device may include a wired or wireless headset port, an external power source (or battery charger) port, a wired or wireless data port, a memory card port, a port for connecting a device with an identification module, audio input/output (I/O) port, video I/O port, headphone port, etc.
  • the interface unit 580 may be used to receive input (for example, data information, power, etc.) from an external device and transmit the received input to one or more elements in the terminal 50 or may be used to communicate between the terminal 50 and the external device. Transfer data between.
  • the memory 590 can be used to store software programs and various data.
  • the memory 590 may mainly include a program storage area and a data storage area.
  • the program storage area may store an operating system, an application program required by at least one function (such as a sound playback function, an image playback function, etc.), etc.; Data created by the use of mobile phones (such as audio data, phone book, etc.), etc.
  • the memory 590 may include a high-speed random access memory, and may also include a non-volatile memory, such as at least one magnetic disk storage device, a flash memory device, or other volatile solid-state storage devices.
  • the processor 511 is the control center of the terminal. It uses various interfaces and lines to connect various parts of the entire terminal, and executes by running or executing software programs and/or modules stored in the memory 590, and calling data stored in the memory 590. Various functions of the terminal and processing data, so as to monitor the terminal as a whole.
  • the processor 511 may include one or more processing units; optionally, the processor 511 may integrate an application processor and a modem processor, where the application processor mainly processes the operating system, user interface, and application programs, etc.
  • the adjustment processor mainly deals with wireless communication. It can be understood that the foregoing modem processor may not be integrated into the processor 511.
  • the terminal 50 may also include a power source 512 (such as a battery) for supplying power to various components.
  • a power source 512 such as a battery
  • the power source 512 may be logically connected to the processor 511 through a power management system, so as to manage charging, discharging, and power consumption management through the power management system. And other functions.
  • the terminal 50 includes some functional modules not shown, which will not be repeated here.
  • some embodiments of the present disclosure further provide a terminal, including a processor 511, a memory 590, a computer program stored on the memory 590 and running on the processor 511, and the computer program is executed by the processor 511.
  • a terminal including a processor 511, a memory 590, a computer program stored on the memory 590 and running on the processor 511, and the computer program is executed by the processor 511.
  • Each process of the embodiment of the data receiving method applied to the terminal side is implemented during execution, and the same technical effect can be achieved. To avoid repetition, details are not described here.
  • Some embodiments of the present disclosure also provide a computer-readable storage medium on which a computer program is stored, and when the computer program is executed by a processor, each process of the embodiment of the data receiving method applied to the terminal side is realized, And can achieve the same technical effect, in order to avoid repetition, I will not repeat them here.
  • the computer-readable storage medium such as read-only memory (Read-Only Memory, ROM for short), random access memory (Random Access Memory, RAM for short), magnetic disk, or optical disk, etc.
  • some embodiments of the present disclosure also provide a network side device 600, including:
  • the sending module 601 is used to transfer the EDT data during the random access process with the terminal when the network side equipment needs to perform early data transmission EDT and the terminal is not in the radio resource control RRC idle state or the RRC inactive state. It is sent to the terminal and instructs the terminal to perform RRC state transition.
  • the sending module 601 is used to implement:
  • the EDT data is carried in the RRC connection establishment message and sent to the terminal.
  • the RRC connection establishment message includes a non-access stratum dedicated information indication field, and the EDT data is located in the non-access stratum dedicated information indication field.
  • the sending module 601 is used to implement:
  • the RRC early data completion message carries the EDT data.
  • the RRC early data completion message is located before the RRC connection establishment message.
  • the network side device further includes:
  • Indication sending module used to send message execution order indication information to the terminal
  • the message execution order indication information is used to instruct the terminal to first obtain the EDT data in the RRC early data completion message, and then perform state conversion according to the RRC connection establishment message; or,
  • the message execution sequence indication information is used to instruct the terminal to first perform state transition according to the RRC connection establishment message, and then obtain the EDT data in the RRC early data completion message.
  • the RRC early data completion message and the RRC connection establishment message are marked with different logical channel identifiers.
  • the RRC early data complete message carries first indication information, and the first indication information is used to instruct the terminal to acquire the EDT data according to the RRC early data complete message.
  • Some embodiments of the present disclosure also provide a network-side device, including: a memory, a processor, and a computer program stored in the memory and capable of running on the processor.
  • the computer program is executed by the processor to realize the above
  • Each process in the embodiment of the data sending method applied to the network side device can achieve the same technical effect. To avoid repetition, details are not repeated here.
  • Some embodiments of the present disclosure further provide a computer-readable storage medium, wherein a computer program is stored on the computer-readable storage medium, and when the computer program is executed by a processor, the above-mentioned data applied to the network-side device is realized
  • a computer program is stored on the computer-readable storage medium, and when the computer program is executed by a processor, the above-mentioned data applied to the network-side device is realized
  • the computer-readable storage medium such as read-only memory (Read-Only Memory, ROM for short), random access memory (Random Access Memory, RAM for short), magnetic disk, or optical disk, etc.
  • FIG. 7 is a structural diagram of a network side device according to an embodiment of the present disclosure, which can implement the details of the above-mentioned data sending method and achieve the same effect.
  • the network side device 700 includes: a processor 701, a transceiver 702, a memory 703, and a bus interface, where:
  • the processor 701 is configured to read a program in the memory 703 and execute the following process:
  • the EDT data is sent to the terminal, And instruct the terminal to perform RRC state transition.
  • the bus architecture may include any number of interconnected buses and bridges. Specifically, one or more processors represented by the processor 701 and various circuits of the memory represented by the memory 703 are linked together.
  • the bus architecture can also link various other circuits such as peripheral devices, voltage regulators, and power management circuits, which are all known in the art, and therefore, will not be further described in this article.
  • the bus interface provides the interface.
  • the transceiver 702 may be a plurality of elements, including a transmitter and a receiver, and provide a unit for communicating with various other devices on a transmission medium.
  • the processor 701 is configured to read the program in the memory 703 for sending the EDT data corresponding to the early data transmission to the terminal, and execute the following process:
  • the EDT data is carried in the RRC connection establishment message through the transceiver 702 and sent to the terminal.
  • the RRC connection establishment message includes a non-access stratum dedicated information indication field, and the EDT data is located in the non-access stratum dedicated information indication field.
  • the processor 701 is configured to read the program for sending EDT data to the terminal in the memory 703, and execute the following process:
  • the RRC early data completion message carries the EDT data.
  • the RRC early data completion message is located before the RRC connection establishment message.
  • processor 701 is configured to read the program in the memory 703 and execute the following process:
  • the message execution order indication information is used to instruct the terminal to first obtain the EDT data in the RRC early data completion message, and then perform state transition according to the RRC connection establishment message; or,
  • the message execution sequence indication information is used to instruct the terminal to first perform state transition according to the RRC connection establishment message, and then obtain the EDT data in the RRC early data completion message.
  • the RRC early data completion message and the RRC connection establishment message are marked with different logical channel identifiers.
  • the RRC early data complete message carries first indication information, and the first indication information is used to instruct the terminal to acquire the EDT data according to the RRC early data complete message.
  • the network-side equipment can be a base station (BTS) in Global System of Mobile Communications (GSM) or Code Division Multiple Access (CDMA), or it can be a broadband code division multiple access (BTS).
  • BTS Global System of Mobile Communications
  • CDMA Code Division Multiple Access
  • the base station (NodeB, NB) in the address (Wideband Code Division Multiple Access, WCDMA) can also be an evolved base station (Evolutional Node B, eNB or eNodeB) in LTE, or a relay station or access point, or in the future 5G network
  • the base stations, etc., are not limited here.
  • modules, units, sub-modules, sub-units, etc. can be implemented in one or more application specific integrated circuits (ASICs), digital signal processors (Digital Signal Processing, DSP), digital signal processing equipment ( DSP Device, DSPD), Programmable Logic Device (Programmable Logic Device, PLD), Field-Programmable Gate Array (Field-Programmable Gate Array, FPGA), general-purpose processors, controllers, microcontrollers, microprocessors, Other electronic units or combinations thereof that perform the functions described in this application.
  • ASICs application specific integrated circuits
  • DSP Digital Signal Processing
  • DSP Device digital signal processing equipment
  • PLD Programmable Logic Device
  • Field-Programmable Gate Array Field-Programmable Gate Array
  • FPGA Field-Programmable Gate Array

Landscapes

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

Abstract

本公开提供了一种数据接收、发送方法、终端及网络侧设备。数据接收方法，应用于终端，包括：在网络侧设备需要进行早期数据传输EDT、且所述终端处于无线资源控制RRC空闲态或RRC非激活态的情况下，在与所述网络侧设备进行的随机接入过程中，接收所述网络侧设备发送的EDT数据，并进行RRC状态转换。

Description

数据接收、发送方法、终端及网络侧设备
相关申请的交叉引用
本申请主张在2019年9月26日在中国提交的中国专利申请号No.201910920203.5的优先权，其全部内容通过引用包含于此。
技术领域
本公开涉及通信技术领域，特别涉及一种数据接收、发送方法、终端及网络侧设备。
背景技术
在长期演进(Long Term Evolution，LTE)研究后期，引入了针对小数据的快速传输方法，主要应用于机对机通信(Machine Type Communication，MTC)和基于蜂窝的窄带物联网(NarrowBand Internet of Things，NB-IOT)等终端。典型场景是水表的自动上报，其数据发送特点大概为12小时左右发送一个数据包，大小为一百至几百字节左右。为了使这样稀发的小数据能够高效的进行传输，避免因此引起的无线资源控制(Radio Resource Control，RRC)状态转换和RRC信令的开销，LTE引入了早期数据传输(Early Data Transmission，EDT)技术。该技术最先应用于上行，使得用户设备(User Equipment，UE，也称终端)可以在空闲态(Idle)和非激活态(Inactive)，不进行RRC状态转换即完成数据传输。后续发现下行也有类似的数据传输需求，因此引入了下行(Downlink，DL)EDT。但DL EDT数据如何进行传输，没有解决方案。
发明内容
本公开实施例提供一种数据接收、发送方法、终端及网络侧设备，以解决相关技术中未明确DL EDT数据如何进行传输，网络侧不知如何进行下行早期数据传输，无法保证通信可靠性的问题。
为了解决上述技术问题，本公开的一些实施例采用如下方案：
第一方面，本公开的一些实施例提供一种数据接收方法，应用于终端，包括：
在网络侧设备需要进行早期数据传输EDT、且所述终端处于无线资源控制RRC空闲态或RRC非激活态的情况下，在与所述网络侧设备进行的随机接入过程中，接收所述网络侧设备发送的EDT数据，并进行RRC状态转换。
第二方面，本公开的一些实施例还提供一种数据发送方法，应用于网络侧设备，包括：
在网络侧设备需要进行早期数据传输EDT、且终端未处于无线资源控制RRC空闲态或RRC非激活态的情况下，在与终端进行的随机接入过程中，将EDT数据发送给所述终端，并指示所述终端进行RRC状态转换。
第三方面，本公开的一些实施例还提供一种终端，包括：
执行模块，用于在网络侧设备需要进行早期数据传输EDT、且所述终端处于无线资源控制RRC空闲态或RRC非激活态的情况下，在与所述网络侧设备进行的随机接入过程中，接收所述网络侧设备发送的EDT数据，并进行RRC状态转换。
第四方面，本公开的一些实施例还提供一种终端，包括：存储器、处理器及存储在存储器上并可在处理器上运行的计算机程序，所述计算机程序被所述处理器执行时实现上述的数据接收方法的步骤。
第五方面，本公开的一些实施例还提供一种网络侧设备，包括：
发送模块，用于在网络侧设备需要进行早期数据传输EDT、且终端未处于无线资源控制RRC空闲态或RRC非激活态的情况下，在与终端进行的随机接入过程中，将EDT数据发送给所述终端，并指示所述终端进行RRC状态转换。
第六方面，本公开的一些实施例还提供一种网络侧设备，包括：存储器、处理器及存储在存储器上并可在处理器上运行的计算机程序，所述计算机程序被所述处理器执行时实现上述的数据发送方法的步骤。
第七方面，本公开的一些实施例还提供一种计算机可读存储介质，所述计算机可读存储介质上存储有计算机程序，所述计算机程序被处理器执行时实现上述的数据接收方法的步骤或上述的数据发送方法的步骤。
本公开的有益效果是：
上述方案，通过在随机接入过程中接收网络侧设备发送的EDT数据，降低了数据传输时延，提升了系统效率，保证了网络通信的可靠性。
附图说明
图1表示典型的上行(Uplink，UL)EDT控制面(Control Plane，CP)的过程示意图；
图2表示本公开的一些实施例的数据接收方法的流程示意图；
图3表示本公开的一些实施例的数据发送方法的流程示意图；
图4表示本公开的一些实施例的终端模块示意图；
图5表示本公开的一些实施例的终端的结构框图；
图6表示本公开的一些实施例的网络侧设备的模块示意图；
图7表示本公开的一些实施例的网络侧设备的结构框图。
具体实施方式
为使本公开的目的、技术方案和优点更加清楚，下面将结合附图及具体实施例对本公开进行详细描述。
在进行本公开实施例的说明时，首先对下面描述中所用到的一些概念进行解释说明。
高效小数据传输的特点是对于非连接态的用户设备(User Equipment，UE，也称终端)，避免它们因为需要传输小数据而进行无线资源控制(Radio Resource Control，RRC)状态的改变和RRC信令的开销，通过极简单的信令过程即完成小数据传输的目的。在长期演进(Long Term Evolution，LTE)阶段，早期数据传输(Early Data Transmission，EDT)引入了针对上行(UL)的控制面(Control Plane，CP)和用户面(User Plane，UP)两种方案。
CP方案的特点是以RRC信令来捎带小数据的传输，避免建立数据无线承载(DRB)。上行用户数据直接以类似非接入层(NAS)消息的形式附着在上行RRC早期数据请求(RRCEarlyDataRequest)消息里进行传输。下行用户数据可选地可以以类似NAS消息的形式附着在下行RRC早期数据完成 (RRCEarlyDataComplete)消息里进行传输。不需要进入RRC连接状态，所有消息均在信令无线承载0(SRB0)上以默认配置进行发送，无线链路控制(Radio Link Control，RLC)透明模式(TM)不支持分段。典型的UL EDT CP的过程如图1所示。
上述介绍了EDT方案对应的RRC过程。EDT过程在媒体接入控制(Medium Access Control，MAC)层的体现，主要是影响了随机接入过程。按照原有的随机接入过程，Msg1发送前导码(preamble)，用于进行定时提前(Time Advance，TA)测量和请求，Msg2分配上行授权(UL grant)和TA，Msg3进行上行公共控制信道(Common Control CHannel，CCCH)的传输，一般在这种情况下是RRC连接建立请求或者RRC连接恢复请求，Msg4进行竞争解决。而在EDT中，由于需要进行非伴随状态转换的数据传输，因此在Msg3里就直接发送用户数据了。相比于传统的Msg3，EDT目的的Msg3需要更大的UL grant，才能足够承载用户数据，因此从Msg1发送preamble起，就需要向网络侧进行传统随机接入信道(RACH)和EDT伴随的RACH请求进行区分，以便于网络侧能够在Msg2为UE分配足够的资源用于数据传输。
相应的EDT伴随的RACH过程，由于Msg3中将用户数据进行了捎带发送，后续竞争解决时间将会比较长，因此需要使用专用于EDT的竞争解决定时器的长度，以保证EDT过程成功结束。
相关的并没有针对LTE DL EDT的实现方式，本公开的一些实施例针对此问题，提供一种数据接收、发送方法、终端及网络侧设备。
如图2所示，本公开的一些实施例提供一种数据接收方法，应用于终端，包括：
步骤201，在网络侧设备需要进行早期数据传输EDT、且所述终端处于无线资源控制RRC空闲态或RRC非激活态的情况下，在与所述网络侧设备进行的随机接入过程中，接收所述网络侧设备发送的EDT数据，并进行RRC状态转换；
需要说明的是，早期数据传输(EDT)传输的是早期小数据，也就是说，该EDT数据为早期小数据，且该EDT数据为网络侧设备发送给终端的下行 数据。
需要说明的是，终端处于无线资源控制(RRC)空闲态或RRC非激活态指的是终端未处于RRC连接态。
需要说明的是，上述步骤实现了终端在随机接入过程中接收该早期小数据，同时终端根据随机接入消息进行RRC状态转换，该RRC状态转换主要指的是终端根据随机接入消息由RRC空闲态或RRC非激活态进入RRC连接态。
也就是说，当网络侧设备需要进行早期小数据传输时，在终端与网络侧设备进行的随机接入过程中将早期小数据传输给终端，以此可以保证终端能及时接收到该早期小数据，能够降低早期小数据的传输时延，同时能够使得终端直接进入RRC连接态，以此提升了系统效率，解决了随机接入过程与EDT RRC过程不能协调工作的问题。
下面分别对EDT数据的不同传输方式进行具体说明如下。
方式一、直接在随机接入的最后一步信令中传输EDT数据
具体地，在此种情况下，步骤201的具体实现方式为：
接收所述网络侧设备发送的无线资源控制(RRC)连接建立消息；
其中，所述RRC连接建立消息(RRCConnectionSetup消息)中携带所述EDT数据。
也就是说，在此种情况下，网络侧设备在发送给终端的RRCConnectionSetup消息中携带该EDT数据，终端接收到该RRCConnectionSetup消息，通过解析该RRCConnectionSetup消息得到EDT数据。
可选地，RRCConnectionSetup消息携带该EDT数据的一种方式为：RRCConnectionSetup消息中包含非接入层专用信息指示域(DedicatedInfoNAS域)，所述EDT数据位于所述非接入层专用信息指示域中。
下面对此种情况下的具体实现过程进行举例说明如下。
当网络侧设备发起了下行早期小数据传输(DL EDT)过程，有少量数据要给终端发送时，如果这时候终端处于空闲态，则网络侧设备通过控制面 DL EDT进行数据发送。一般来说，网络侧设备在寻呼消息里显式携带这是一个DL EDT的指示，以便于终端发起早期小数据传输相关随机接入过程。具体地流程如下：
步骤A10、核心网有关于某个终端的下行数据要发送，该终端当前处于空闲态，则核心网首先判断该数据发送是否满足DL EDT的条件，如果满足DL EDT条件，则向终端的跟踪区域(tracking area，TA)内的网络侧设备(例如，eNB/gNB)发送DL EDT特殊的寻呼请求(指在传统寻呼里携带终端标识的基础上，增加DL EDT标记，例如，可以是1比特DL EDT标记，也可以是携带DL数据大小等)，其中满足DL EDT的条件可以如下一条或者组合：
B11、终端要发的数据量小于一定的门限；
B12、终端要发的数据的服务质量满足一定要求；
例如，时延可以忍受一定的长度及以上。
B13、终端的能力支持DL EDT。
步骤A11、网络侧设备收到核心网的寻呼指示消息，则根据自己的状态判断是否发起DL EDT相关的寻呼，如果需要发起DL EDT的寻呼，则在寻呼消息里携带DL EDT指示，如果不需要则发起普通的寻呼过程，主要判断依据包含以下一项：
B21、网络是否支持DL EDT；
B22、资源是否允许DL EDT；
B23、网络配置是否支持满足DL数据大小的DL EDT；
步骤A12、终端接收到含有DL EDT指示的寻呼消息(如果是普通寻呼消息，则终端按照现有过程发起)；
步骤A13、终端发起随机接入过程；
可选地，如果终端选择四步随机接入(4-step RACH)过程，则选择EDT相关的前导码(preamble)发起随机接入消息一(Msg1)过程；
可选地，如果终端选择两步随机接入(2-step RACH)过程，则选择与自己的上行消息(例如，需要终端的鉴权消息、身份信息和/或RRC早期数据请求(RRCEarlyDataRequest)等)大小匹配的物理上行共享信道(PUSCH)资源大小和对应的前导码发起MsgA过程；
步骤A14、网络侧设备接收到终端的Msg1或者MsgA；
针对两步和四步随机接入过程，网络侧设备的具体执行过程也不相同，具体为：
可选地，如果是Msg1，则网络侧设备通过前导码获知针对需要EDT过程，则在消息二(Msg2)中分配给终端的上行授权(UL grant)需要比普通随机接入大一些，以满足终端进行消息(例如，上行鉴权消息、身份信息和/或RRCEarlyDataRequest等)的传输；
可选地，如果是MsgA消息，则网络侧设备从中可以获得终端的身份和鉴权信息等，如果有鉴权信息则发送至核心网进行鉴权，成功之后，按照终端身份从核心网进行终端数据的获取，此时如果根据终端的下行数据(例如，下行数据大量到达，不适合仅仅通过DL EDT传输)或者其它条件(例如，终端有新的业务触发，例如，语音或者视频等)，需要使终端进入连接态，则网络侧以MsgB将通过RRCConnectionSetup消息同时捎带少量数据发送给终端；
步骤A15、终端侧接收到网络侧设备发送的Msg2或者MsgB消息；
可选地，如果是Msg2，则终端获取Msg2中的定时提前量(Timing Advance，TA)信息和UL grant，组织消息三(Msg3)发送，其中Msg3信息与上述MsgA中PUSCH上发送信息类似，可以包含终端的鉴权消息、身份信息和/或RRCEarlyDataRequest等；
可选地，终端接收到MsgB，则解析RRCConnectionSetup消息和其中的数据，进行数据处理和连接建立的操作，该2-step RACH过程结束，同时既完成了既定数据的传输也使终端进行了到RRC连接态的转换。
步骤A16、网络侧设备接收到针对的Msg3消息；
需要说明的是，仅有4-step RACH过程继续执行该步骤A16。
网络侧设备解析Msg3消息，从中可以获得终端的身份和鉴权信息等，如果有鉴权信息则发送至核心网进行鉴权，成功之后，按照终端身份从核心网进行终端数据的获取，此时如果根据终端的下行数据(例如下行数据大量到达，不适合仅仅通过DL EDT传输)或者其它条件(例如终端有新的业务触发，例如语音或者视频等)，需要使终端进入连接态，则网络侧以Msg4将 通过RRCConnectionSetup消息同时捎带少量数据发送给终端，例如，在该消息里增加DedicatedInfoNAS域，该域为可选出现，用于捎带下行早期数据。
步骤A17、终端接收到网络的Msg4消息；
终端接收到Msg4，则解析RRCConnectionSetup消息和其中的数据，进行数据处理和连接建立的操作，该4-step RACH过程结束，既完成了既定数据的传输也使终端进行了到RRC连接态的转换，至此4-step RACH过程结束。
需要说明的是，上述实现过程，解决了随机接入过程与EDT RRC过程不能协调工作的问题，通过将EDT数据直接在RRC连接建立消息中发送，既满足传输少量数据的需要也同时可以实现了终端由RRC空闲态或RRC非激活态进入RRC连接态，降低了早期小数据的传输时延，同时提升了系统效率，而且该数据域是可选的，并不影响现有正常过程。
方式二、将随机接入的最后一步信令与RRC早期数据完成消息合并发送
具体地，在此种情况下，步骤201的具体实现方式为：
接收所述网络侧设备合并发送的RRC连接建立消息和RRC早期数据完成消息；
其中，所述RRC早期数据完成消息中携带所述EDT数据。
需要说明的是，此种情况指的是网络侧设备同时发送RRC连接建立消息和RRC早期数据完成消息给终端，终端根据接收到的消息进行后续操作。
具体地，接收所述网络侧设备发送的EDT数据，并进行RRC状态转换的具体行为包括：
获取所述RRC早期数据完成消息中的所述EDT数据、且终端不执行进入空闲态的操作，并根据所述RRC连接建立消息进行状态转换。
例如，在此种情况下，终端不执行媒体接入控制(MAC)实体复位的操作，也就是说，终端根据RRC早期数据完成消息不能进入空闲态。
需要说明的是，在某些情况下，终端可能先执行获取所述RRC早期数据完成消息中的所述EDT数据、且终端不执行进入空闲态的操作，然后再执行根据所述RRC连接建立消息进行状态转换的操作；在某些情况下，终端可能会先执行根据所述RRC连接建立消息进行状态转换的操作，然后再执行获取 所述RRC早期数据完成消息中的所述EDT数据、且终端不执行进入空闲态的操作。
需要说明的是，在此种情况下，合并发送的RRC连接建立消息和RRC早期数据完成消息的传输可以采用如下情况中的一种进行：
情况1、合并发送的RRC连接建立消息和RRC早期数据完成消息中所述RRC早期数据完成消息位于所述RRC连接建立消息之前；
需要说明的是，此种情况下，预先约定消息的组包顺序，该组包顺序也隐式表明终端接收到消息的执行顺序，此种情况下，终端先执行RRC早期数据完成消息，即终端先根据RRC早期数据完成消息获取其中的EDT数据，但是终端并不依据RRC早期数据完成消息执行进入空闲态的操作，然后终端再根据RRC连接建立消息执行进入连接态的过程。
不同于上面方式一中在RRCConnectionSetup消息里携带数据，此种方式采用在RRCEarlyDataComplete消息携带EDT数据，并将RRCConnectionSetup消息和RRCEarlyDataComplete消息合并发送，也达到满足传输少量数据的需要也同时可以完成终端的状态转换的目的。但由于RRCConnectionSetup消息使得终端进入RRC连接态，而RRCEarlyDataComplete消息使得终端解出数据之后就进入RRC空闲态，因此这两条消息一起发送，会给终端的行为造成混淆和不确定，需要进一步明确执行顺序，此种方式中便是设置RRC早期数据完成消息位于RRC连接建立消息之前而明确终端的执行顺序。
下面对此种情况下的具体实现过程进行举例说明如下。
步骤A20、核心网有关于某个终端的下行数据要发送，该终端当前处于空闲态，则核心网首先判断该数据发送是否满足DL EDT的条件，如果满足DL EDT条件，则向终端的跟踪区域(tracking area，TA)内的网络侧设备(例如，eNB/gNB)发送DL EDT特殊的寻呼请求(指在传统寻呼里携带终端标识的基础上，增加DL EDT标记，例如，可以是1比特DL EDT标记，也可以是携带DL数据大小等)，其中满足DL EDT的条件可以如下一条或者组合：
B11、终端要发的数据量小于一定的门限；
B12、终端要发的数据的服务质量满足一定要求；
例如，时延可以忍受一定的长度及以上。
B13、终端的能力支持DL EDT。
步骤A21、网络侧设备收到核心网的寻呼指示消息，则根据自己的状态判断是否发起DL EDT相关的寻呼，如果需要发起DL EDT的寻呼，则在寻呼消息里携带DL EDT指示，如果不需要则发起普通的寻呼过程，主要判断依据包含以下一项：
B21、网络是否支持DL EDT；
B22、资源是否允许DL EDT；
B23、网络配置是否支持满足DL数据大小的DL EDT；
步骤A22、终端接收到含有DL EDT指示的寻呼消息(如果是普通寻呼消息，则终端按照现有过程发起)；
步骤A23、终端发起随机接入过程；
可选地，如果终端选择4-step RACH过程，则选择EDT相关的preamble发起随机接入消息一(Msg1)过程；
可选地，如果终端选择2-step RACH过程，则选择与自己的上行消息(例如，需要终端的鉴权消息、身份信息和/或RRC早期数据请求(RRCEarlyDataRequest)等)大小匹配的物理上行共享信道(PUSCH)资源大小和对应的前导码发起MsgA过程；
步骤A24、网络侧设备接收到终端的Msg1或者MsgA；
可选地，如果是Msg1，则网络侧设备通过前导码获知针对需要EDT过程，则在消息二(Msg2)中分配给终端的上行授权(UL grant)需要比普通随机接入大一些，以满足终端进行消息(例如上行鉴权消息、身份信息和/或RRCEarlyDataRequest等)的传输；
可选地，如果是MsgA消息，则网络侧设备从中可以获得终端的身份和鉴权信息等，如果有鉴权信息则发送至核心网进行鉴权，成功之后，按照终端身份从核心网进行终端数据的获取，此时如果根据终端的下行数据(例如，下行数据大量到达，不适合仅仅通过DL EDT传输)或者其它条件(例如，终端有新的业务触发，例如，语音或者视频等)，需要使终端进入连接态，则网络侧设备以MsgB将捎带少量数据的RRCEarlyDataComplete消息和RRCConnectionSetup消息同时发送给针对，需要注意在组包时将 RRCEarlyDataComplete消息置于前面，RRCConnectionSetup消息置与其后面，以隐式指示终端执行顺序。
步骤A25、终端侧接收到网络侧设备发送的Msg2或者MsgB消息；
可选地，如果是Msg2，则终端获取Msg2中的定时提前量(Timing Advance，TA)信息和UL grant，组织消息三(Msg3)发送，其中Msg3信息与上述MsgA中PUSCH上发送信息类似，可以包含终端的鉴权消息、身份信息和/或RRCEarlyDataRequest等；
可选地，终端接收到MsgB，则按从前往后的顺序依次解析RRCEarlyDataComplete消息和RRCConnectionSetup消息，而且此时终端知道有两条信令分别进行数据捎带和RRC状态转换，因此终端在处理RRCEarlyDataComplete消息时，仅对数据进行处理即可(例如，将NAS container中的数据递交给高层)，不需要进行其它的操作(例如不需要进行MAC实体复位等操作，需要说明的是，终端此时需要执行哪些操作，可以明确在标准中规定好，与传统的接收RRCEarlyDataComplete消息有差别)，接着执行RRCConnectionSetup消息，进行连接建立的操作，该2-step RACH过程结束，同时既完成了既定数据的传输也使终端进行了到RRC连接态的转换。
步骤A26、网络侧设备接收到针对的Msg3消息；
需要说明的是，仅有4-step RACH过程继续执行该步骤A26。
网络侧设备解析Msg3消息，从中可以获得终端的身份和鉴权信息等，如果有鉴权信息则发送至核心网进行鉴权，成功之后，按照终端身份从核心网进行终端数据的获取，此时如果根据终端的下行数据(例如下行数据大量到达，不适合仅仅通过DL EDT传输)或者其它条件(例如终端有新的业务触发，例如语音或者视频等)，需要使终端进入RRC连接态，则网络侧以Msg4将捎带少量数据的RRCEarlyDataComplete消息和RRCConnectionSetup消息同时发送给终端，需要注意在组包时将RRCEarlyDataComplete消息置于前面，RRCConnectionSetup消息置与其后面，以隐式指示终端执行顺序。
步骤A27、终端接收到网络的Msg4消息；
终端接收到Msg4，则按从前往后的顺序依次解析RRCEarlyDataComplete 消息和RRCConnectionSetup消息，而且此时终端知道有两条信令分别进行数据捎带和RRC状态转换，因此终端在处理RRCEarlyDataComplete消息时，仅对数据进行处理即可，不需要进行其它回到RRC空闲态的操作，例如不需要进行MAC实体复位等操作(需要说明的是，终端此时需要执行哪些操作，可以明确在标准中规定好，与传统的接收RRCEarlyDataComplete消息有差别)，接着执行RRCConnectionSetup消息，进行连接建立的操作，该4-step RACH过程结束，同时既完成了既定数据的传输也使终端进行了到RRC连接态的转换。
需要说明的是，上述实现过程，解决了随机接入过程与EDT RRC过程不能协调工作的问题，通过将RRC连接建立消息和RRC早期数据完成消息一同发送给终端，并利用两个消息的组包顺序隐式指示终端执行两个消息的顺序，既满足传输少量数据的需要也同时实现了终端由RRC空闲态或RRC非激活态进入RRC连接态，降低了早期小数据的传输时延，同时提升了系统效率，而且此种方式均选用现有信令格式，标准工作量少。
情况2、终端接收网络侧设备发送的消息执行顺序指示信息；
其中，所述消息执行顺序指示信息用于指示所述终端先获取所述RRC早期数据完成消息中的EDT数据，再根据所述RRC连接建立消息进行状态转换；或者
所述消息执行顺序指示信息用于指示所述终端先根据所述RRC连接建立消息进行状态转换，再获取所述RRC早期数据完成消息中的EDT数据。
需要说明的是，此种情况指的是，网络侧设备需要发送一个指示信息，用于指示RRC连接建立消息和RRC早期数据完成消息的执行顺序，可选地，该指示信息可以位于合并发送的无线资源控制RRC连接建立消息和RRC早期数据完成消息的MAC包头或者是控制信息中。
情况3、所述RRC早期数据完成消息和所述RRC连接建立消息使用不同的逻辑信道标识进行标记；
需要说明的是，此种情况指的是用不同的逻辑信道标识区分两条消息，终端在接收到该合并发送的无线资源控制RRC连接建立消息和RRC早期数据完成消息时，便能根据不同的逻辑信道标识确定两条消息的执行顺序。
情况4、所述RRC早期数据完成消息中携带第一指示信息，所述第一指示信息用于指示所述终端根据所述RRC早期数据完成消息进行所述EDT数据的获取；
需要说明的是，此种情况下，只在RRC早期数据完成消息中增加一个指示信息，用于指示终端在执行RRC早期数据完成消息时，主要是获取其中携带的EDT数据，终端并不根据该RRC早期数据完成消息执行进入空闲态的操作。
需要说明的是，上述的情况2、情况3和情况4都是显式的指示方式，通过显式指示执行顺序或者对RRCEarlyDataComplete消息进行特殊标记的方式指示终端的执行顺序；下面对此种情况下的具体实现过程进行举例说明如下。
步骤A30、核心网有关于某个终端的下行数据要发送，该终端当前处于空闲态，则核心网首先判断该数据发送是否满足DL EDT的条件，如果满足DL EDT条件，则向终端的跟踪区域(tracking area，TA)内的网络侧设备(例如，eNB/gNB)发送DL EDT特殊的寻呼请求(指在传统寻呼里携带终端标识的基础上，增加DL EDT标记，例如，可以是1比特DL EDT标记，也可以是携带DL数据大小等)，其中满足DL EDT的条件可以如下一条或者组合：
B11、终端要发的数据量小于一定的门限；
B12、终端要发的数据的服务质量满足一定要求；
例如，时延可以忍受一定的长度及以上。
B13、终端的能力支持DL EDT。
步骤A31、网络侧设备收到核心网的寻呼指示消息，则根据自己的状态判断是否发起DL EDT相关的寻呼，如果需要发起DL EDT的寻呼，则在寻呼消息里携带DL EDT指示，如果不需要则发起普通的寻呼过程，主要判断依据包含以下一项：
B21、网络是否支持DL EDT；
B22、资源是否允许DL EDT；
B23、网络配置是否支持满足DL数据大小的DL EDT；
步骤A32、终端接收到含有DL EDT指示的寻呼消息(如果是普通寻呼 消息，则终端按照现有过程发起)；
步骤A33、终端发起随机接入过程；
可选地，如果终端选择4-step RACH过程，则选择EDT相关的preamble发起随机接入消息一(Msg1)过程；
可选地，如果终端选择2-step RACH过程，则选择与自己的上行消息(例如需要终端的鉴权消息、身份信息和/或RRC早期数据请求(RRCEarlyDataRequest)等)大小匹配的物理上行共享信道(PUSCH)资源大小和对应的前导码发起MsgA过程；
步骤A34、网络侧设备接收到终端的Msg1或者MsgA；
可选地，如果是Msg1，则网络侧设备通过前导码获知针对需要EDT过程，则在消息二(Msg2)中分配给终端的上行授权(UL grant)需要比普通随机接入大一些，以满足终端进行消息(例如上行鉴权消息、身份信息和/或RRCEarlyDataRequest等)的传输；
如果是MsgA消息，则网络侧设备从中可以获得终端的身份和鉴权信息等，如果有鉴权信息则发送至核心网进行鉴权，成功之后，按照终端身份从核心网进行终端数据的获取，此时如果根据终端的下行数据(例如，下行数据大量到达，不适合仅仅通过DL EDT传输)或者其它条件(例如，终端有新的业务触发，例如，语音或者视频等)，需要使终端进入RRC连接态，则网络侧以MsgB将捎带少量数据的RRCEarlyDataComplete消息和RRCConnectionSetup消息同时发送给终端，采用如下方式中的至少一项进行显式指示：
H11、在数据包里或者包头位置以显式的内容指示终端执行顺序；
例如，RRCEarlyDataComplete消息需要先执行，RRCConnectionSetup消息需要后执行；
H12、在RRCEarlyDataComplete消息里携带特殊指示，指示该消息只需要处理其中的数据部分，其余的传统操作不需要执行，或者只需要执行部分操作，例如不需要进行MAC实体复位等操作(终端此时需要执行哪些操作，可以明确在标准中规定好，与传统的接收RRCEarlyDataComplete消息有差别)。
H13、可以为CCCH再分配一个逻辑信道标识(LCID)，专门用于只处 理数据的RRCEarlyDataComplete消息。
步骤A35、终端侧接收到网络侧设备发送的Msg2或者MsgB消息；
可选地，如果是Msg2，则终端获取Msg2中的定时提前量(Timing Advance，TA)信息和UL grant，组织消息三(Msg3)发送，其中Msg3信息与上述MsgA中PUSCH上发送信息类似，可以包含终端的鉴权消息、身份信息和/或RRCEarlyDataRequest等；
可选地，终端接收到MsgB，则按显式指示的顺序依次解析RRCEarlyDataComplete消息和RRCConnectionSetup消息，而且此时终端知道有两条信令分别进行数据捎带和RRC状态转换，因此终端在处理RRCEarlyDataComplete消息时，仅对数据进行处理即可，不需要进行其它回到RRC空闲态的操作(例如，不需要进行MAC实体复位等操作，需要说明的是，终端此时需要执行哪些操作，可以明确在标准中规定好，与传统的接收RRCEarlyDataComplete消息有差别)，接着执行RRCConnectionSetup消息，进行连接建立的操作，该2-step RACH过程结束，同时既完成了既定数据的传输也使终端进行了到RRC连接态的转换；或者，
虽然没有显式指示的顺序，终端可以任意执行RRCEarlyDataComplete消息和RRCConnectionSetup消息，但由于RRCEarlyDataComplete消息带有特殊的指示，终端在处理RRCEarlyDataComplete消息时，仅对数据进行处理即可，不需要进行其它回到RRC空闲态的操作(例如，不需要进行MAC实体复位等操作，需要说明的是，终端此时需要执行哪些操作，可以明确在标准中规定好，与传统的接收RRCEarlyDataComplete消息有差别，与上述显示指示顺序的两条消息顺序执行时的操作也有可能不一样)；或者，
当然，也可以同时接收到显式的顺序指示和RRCEarlyDataComplete消息带有的特殊标记，则终端的执行将更确定，先执行RRCEarlyDataComplete消息再执行RRCConnectionSetup消息，由于RRCEarlyDataComplete消息带有特殊的指示，终端在处理RRCEarlyDataComplete消息时，仅对数据进行处理即可，不需要进行其它回到RRC空闲态的操作(例如，不需要进行MAC实体复位等操作，需要说明的是，终端此时需要执行哪些操作，可以明确在标准中规定好，与传统的接收RRCEarlyDataComplete消息有差别)，接着执行 RRCConnectionSetup消息，进行连接建立的操作，该2-step RACH过程结束，同时既完成了既定数据的传输也使终端进行了到RRC连接态的转换；或者，
终端接收到MsgB，根据RRCEarlyDataComplete消息和RRCConnectionSetup消息使用不同的逻辑信道标识，终端在处理RRCEarlyDataComplete消息时，仅对数据进行处理即可，不需要进行其它回到RRC空闲态的操作(例如，不需要进行MAC实体复位等操作，需要说明的是，终端此时需要执行哪些操作，可以明确在标准中规定好，与传统的接收RRCEarlyDataComplete消息有差别)，接着执行RRCConnectionSetup消息，进行连接建立的操作，该2-step RACH过程结束，同时既完成了既定数据的传输也使终端进行了到RRC连接态的转换。
步骤A36、网络侧设备接收到针对的Msg3消息；
需要说明的是，仅有4-step RACH过程继续执行该步骤A36。
网络侧设备解析Msg3消息，从中可以获得针对的身份和鉴权信息等，如果有鉴权信息则发送至核心网进行鉴权，成功之后，按照终端身份从核心网进行终端数据的获取，此时如果根据终端的下行数据(例如下行数据大量到达，不适合仅仅通过DL EDT传输)或者其它条件(例如终端有新的业务触发，例如语音或者视频等)，需要使终端进入连接态，则网络侧以Msg4将捎带少量数据的RRCEarlyDataComplete消息和RRCConnectionSetup消息同时发送给终端，采用如下方式中的至少一项进行显式指示：
H21、在数据包里或者包头位置以显式的内容指示终端执行顺序；
例如，RRCEarlyDataComplete消息需要先执行，RRCConnectionSetup消息需要后执行；
H22、在RRCEarlyDataComplete消息里携带特殊指示，指示该消息只需要处理其中的数据部分，其余的传统操作不需要执行，或者只需要执行部分操作，例如不需要进行MAC实体复位等操作(终端此时需要执行哪些操作，可以明确在标准中规定好，与传统的接收RRCEarlyDataComplete消息有差别)。
H23、可以为CCCH再分配一个LCID，专门用于只处理数据的RRCEarlyDataComplete消息。
步骤A37、终端接收到网络的Msg4消息；
终端接收到Msg4，则按显式指示的顺序依次解析RRCEarlyDataComplete消息和RRCConnectionSetup消息，而且此时终端知道有两条信令分别进行数据捎带和RRC状态转换，因此终端在处理RRCEarlyDataComplete消息时，仅对数据进行处理即可，不需要进行其它回到RRC空闲态的操作(例如，不需要进行MAC entity reset复位等操作，需要说明的是，终端此时需要执行哪些操作，可以明确在标准中规定好，与传统的接收RRCEarlyDataComplete消息有差别)，接着执行RRCConnectionSetup消息，进行连接建立的操作，该4-step RACH过程结束，同时既完成了既定数据的传输也使终端进行了到RRC连接态的转换；或者，
虽然没有显式指示的顺序，终端可以任意执行RRCEarlyDataComplete消息和RRCConnectionSetup消息，但由于RRCEarlyDataComplete消息带有特殊的指示，终端在处理RRCEarlyDataComplete消息时，仅对数据进行处理即可，不需要进行其它回到RRC空闲态的操作(例如，不需要进行MAC实体复位等操作，需要说明的是，终端此时需要执行哪些操作，可以明确在标准中规定好，与传统的接收RRCEarlyDataComplete消息有差别，与上述显示指示顺序的两条消息顺序执行时的操作也有可能不一样)；或者，
当然，也可以同时接收到显式的顺序指示和RRCEarlyDataComplete消息带有的特殊标记，则终端的执行将更确定，先执行RRCEarlyDataComplete消息再执行RRCConnectionSetup消息，由于RRCEarlyDataComplete消息带有特殊的指示，终端在处理RRCEarlyDataComplete消息时，仅对数据进行处理即可，不需要进行其它回到RRC空闲态的操作(例如，不需要进行MAC实体复位等操作，需要说明的是，终端此时需要执行哪些操作，可以明确在标准中规定好，与传统的接收RRCEarlyDataComplete消息有差别)，接着执行RRCConnectionSetup消息，进行连接建立的操作，该4-step RACH过程结束，同时既完成了既定数据的传输也使终端进行了到RRC连接态的转换；或者，
终端接收到Msg4，根据RRCEarlyDataComplete消息和RRCConnectionSetup消息使用不同的逻辑信道标识，终端在处理 RRCEarlyDataComplete消息时，仅对数据进行处理即可，不需要进行其它回到RRC空闲态的操作(例如，不需要进行MAC实体复位等操作，需要说明的是，终端此时需要执行哪些操作，可以明确在标准中规定好，与传统的接收RRCEarlyDataComplete消息有差别)，接着执行RRCConnectionSetup消息，进行连接建立的操作，该2-step RACH过程结束，同时既完成了既定数据的传输也使终端进行了到RRC连接态的转换。
需要说明的是，上述实现过程，解决了随机接入过程与EDT RRC过程不能协调工作的问题，通过将RRC连接建立消息和RRC早期数据完成消息一同发送给终端，并利用额外的指示显式指示终端执行两个消息的顺序，既满足传输少量数据的需要也同时实现了终端由RRC空闲态或RRC非激活态进入RRC连接态，降低了早期小数据的传输时延，同时提升了系统效率，且此种方式对相关的消息格式进行改进，使终端的行为更清晰。
还需要说明是，本公开的一些实施例还提供一种早期小数据的传输方式，具体实现过程为：
步骤A40、核心网有关于某个终端的下行数据要发送，该终端当前处于空闲态，则核心网首先判断该数据发送是否满足DL EDT的条件，如果满足DL EDT条件，则向终端的跟踪区域(tracking area，TA)内的网络侧设备(例如，eNB/gNB)发送DL EDT特殊的寻呼请求(指在传统寻呼里携带终端标识的基础上，增加DL EDT标记，例如，可以是1比特DL EDT标记，也可以是携带DL数据大小等)，其中满足DL EDT的条件可以如下一条或者组合：
B11、终端要发的数据量小于一定的门限；
B12、终端要发的数据的服务质量满足一定要求；
例如，时延可以忍受一定的长度及以上。
B13、终端的能力支持DL EDT。
步骤A41、网络侧设备收到核心网的寻呼指示消息，则根据自己的状态判断是否发起DL EDT相关的寻呼，如果需要发起DL EDT的寻呼，则在寻呼消息里携带DL EDT指示，如果不需要则发起普通的寻呼过程，主要判断依据包含以下一项：
B21、网络是否支持DL EDT；
B22、资源是否允许DL EDT；
B23、网络配置是否支持满足DL数据大小的DL EDT；
步骤A42、终端接收到含有DL EDT指示的寻呼消息(如果是普通寻呼消息，则终端按照现有过程发起)；
步骤A43、终端发起随机接入过程；
可选地，如果终端选择4-step RACH过程，则选择EDT相关的preamble发起随机接入消息一(Msg1)过程；
可选地，如果终端选择2-step RACH过程，则选择与自己的上行消息(例如需要终端的鉴权消息、身份信息和/或RR早期数据请求(RRCEarlyDataRequest)等)大小匹配的物理上行共享信道(PUSCH)资源大小和对应的前导码发起MsgA过程；
步骤A44、网络侧设备接收到终端的Msg1或者MsgA；
针对两步和四步随机接入过程，网络侧设备的具体执行过程也不相同，具体为：
可选地，如果是Msg1，则网络侧设备通过前导码发获知针对需要EDT过程，则在消息二(Msg2)中分配给终端的上行授权(UL grant)需要比普通随机接入大一些，以满足终端进行消息(例如，上行鉴权消息、身份信息和/或RRCEarlyDataRequest等)的传输；
可选地，如果是MsgA消息，则网络从中可以获得终端的身份和鉴权信息等，如果发现这时候有将终端转移至RRC连接态的需要，则直接在MsgB消息中发送RRCConnectionSetup消息；
步骤A45、终端侧接收到网络侧设备发送的Msg2或者MsgB消息；
可选地，如果是Msg2，则终端获取Msg2中的定时提前量(Timing Advance，TA)信息和UL grant，组织消息三(Msg3)发送，其中Msg3信息与上述MsgA中PUSCH上发送信息类似，可以包含终端的鉴权消息、身份信息和/或RRCEarlyDataRequest等；
可选地，终端接收到MsgB，按照RRCConnectionSetup消息内容，建立RRC连接，2-step RACH过程结束，网络侧设备为终端建立专用数据承载，在专用数据承载中进行早期小数据的传输。
步骤A46、网络侧设备接收到针对的Msg3消息；
需要说明的是，仅有4-step RACH过程继续执行该步骤A46。
网络解析Msg3消息，从中可以获得终端的身份和鉴权信息等，如果发现这时候有将终端转移至RRC连接态的需要，则直接在Msg4消息中发送RRCConnectionSetup消息；
步骤A47、终端接收到网络的Msg4消息；
具体地，终端接收到Msg4，按照RRCConnectionSetup消息内容，建立RRC连接，4-step RACH过程结束，网络侧设备为终端建立专用数据承载，在专用数据承载中进行早期小数据的传输。
需要说明的是，此种方式在发起时是按照DL EDT过程发起的，后续网络侧根据需求发生变化，将其转换成一个正常的RRC连接建立过程再进行数据承载建立和数据传输的过程。
综上可知，本公开的一些实施例保证了随机接入过程与EDT RRC过程的协调工作，提升了下行小数据发送的效率，同时完成小数据传输和信令传输，并一定程度上降低了时延，很好的提升了系统效率。
如图3所示，本公开的一些实施例还提供一种数据发送方法，应用于网络侧设备，包括：
步骤301，在网络侧设备需要进行早期数据传输EDT、且终端未处于无线资源控制RRC空闲态或RRC非激活态的情况下，在与终端进行的随机接入过程中，将EDT数据发送给所述终端，并指示所述终端进行RRC状态转换。
可选地，所述将EDT数据发送给所述终端，包括：
将所述EDT数据携带在RRC连接建立消息中，发送给终端。
进一步地，所述RRC连接建立消息中包含非接入层专用信息指示域，所述EDT数据位于所述非接入层专用信息指示域中。
可选地，所述将EDT数据发送给所述终端，包括：
合并发送无线资源控制RRC连接建立消息和RRC早期数据完成消息给所述终端；
其中，所述RRC早期数据完成消息中携带所述EDT数据。
进一步地，所述RRC早期数据完成消息位于所述RRC连接建立消息之前。
进一步地，所述的数据发送方法，还包括：
发送消息执行顺序指示信息给终端；
其中，所述消息执行顺序指示信息用于指示所述终端先获取所述RRC早期数据完成消息中的EDT数据，再根据所述RRC连接建立消息进行状态转换；或者，
所述消息执行顺序指示信息用于指示所述终端先根据所述RRC连接建立消息进行状态转换，再获取所述RRC早期数据完成消息中的EDT数据。
进一步地，所述RRC早期数据完成消息和所述RRC连接建立消息使用不同的逻辑信道标识进行标记。
进一步地，所述RRC早期数据完成消息中携带第一指示信息，所述第一指示信息用于指示所述终端根据所述RRC早期数据完成消息进行所述EDT数据的获取。
需要说明的是，上述实施例中所有关于网络侧设备的描述均适用于该数据发送方法的实施例中，也能达到与之相同的技术效果。
如图4所示，本公开的一些实施例提供一种终端400，包括：
执行模块401，用于在网络侧设备需要进行早期数据传输EDT、且所述终端处于无线资源控制RRC空闲态或RRC非激活态的情况下，在与所述网络侧设备进行的随机接入过程中，接收所述网络侧设备发送的EDT数据，并进行RRC状态转换。
可选地，所述执行模块401，用于：
接收所述网络侧设备发送的RRC连接建立消息；
其中，所述RRC连接建立消息中携带所述EDT数据。
进一步地，所述RRC连接建立消息中包含非接入层专用信息指示域，所述EDT数据位于所述非接入层专用信息指示域中。
可选地，所述执行模块401，用于：
接收所述网络侧设备合并发送的RRC连接建立消息和RRC早期数据完成消息；
其中，所述RRC早期数据完成消息中携带所述EDT数据。
进一步地，所述RRC早期数据完成消息位于所述RRC连接建立消息之前。
进一步地，所述终端，还包括：
指示接收模块，用于接收网络侧设备发送的消息执行顺序指示信息；
其中，所述消息执行顺序指示信息用于指示所述终端先获取所述RRC早期数据完成消息中的EDT数据，再根据所述RRC连接建立消息进行状态转换；或者，
所述消息执行顺序指示信息用于指示所述终端先根据所述RRC连接建立消息进行状态转换，再获取所述RRC早期数据完成消息中的EDT数据。
进一步地，所述RRC早期数据完成消息和所述RRC连接建立消息使用不同的逻辑信道标识进行标记。
进一步地，所述RRC早期数据完成消息中携带第一指示信息，所述第一指示信息用于指示所述终端根据所述RRC早期数据完成消息进行所述EDT数据的获取。
具体地，所述执行模块401，用于实现：
获取所述RRC早期数据完成消息中的所述EDT数据、且终端不执行进入空闲态的操作，并根据所述RRC连接建立消息进行状态转换。
进一步地，所述终端不执行进入空闲态的操作的实现方式具体为：
终端不执行媒体接入控制MAC实体复位的操作。
需要说明的是，该终端实施例是与上述应用于终端的数据接收方法相对应的终端，上述实施例的所有实现方式均适用于该终端实施例中，也能达到与其相同的技术效果。
图5为实现本公开的一些实施例的一种终端的硬件结构示意图。
该终端50包括但不限于：射频单元510、网络模块520、音频输出单元530、输入单元540、传感器550、显示单元560、用户输入单元570、接口单元580、存储器590、处理器511、以及电源512等部件。本领域技术人员可以理解，图5中示出的终端结构并不构成对终端的限定，终端可以包括比图示更多或更少的部件，或者组合某些部件，或者不同的部件布置。在本公开 的一些实施例中，终端包括但不限于手机、平板电脑、笔记本电脑、掌上电脑、车载终端、可穿戴设备、以及计步器等。
其中，射频单元510用于在网络侧设备需要进行早期数据传输EDT、且所述终端处于无线资源控制RRC空闲态或RRC非激活态的情况下，在与所述网络侧设备进行的随机接入过程中，接收所述网络侧设备发送的EDT数据，处理器511进行RRC状态转换。
本公开的一些实施例的终端通过在随机接入过程中接收网络侧设备发送的EDT数据，降低了数据传输时延，提升了系统效率，保证了网络通信的可靠性。
应理解的是，本公开的一些实施例中，射频单元510可用于收发信息或通话过程中，信号的接收和发送，具体的，将来自网络侧设备的下行数据接收后，给处理器511处理；另外，将上行的数据发送给网络侧设备。通常，射频单元510包括但不限于天线、至少一个放大器、收发信机、耦合器、低噪声放大器、双工器等。此外，射频单元510还可以通过无线通信系统与网络和其他设备通信。
终端通过网络模块520为用户提供了无线的宽带互联网访问，如帮助用户收发电子邮件、浏览网页和访问流式媒体等。
音频输出单元530可以将射频单元510或网络模块520接收的或者在存储器590中存储的音频数据转换成音频信号并且输出为声音。而且，音频输出单元530还可以提供与终端50执行的特定功能相关的音频输出(例如，呼叫信号接收声音、消息接收声音等等)。音频输出单元530包括扬声器、蜂鸣器以及受话器等。
输入单元540用于接收音频或视频信号。输入单元540可以包括图形处理器(Graphics Processing Unit，GPU)541和麦克风542，图形处理器541对在视频捕获模式或图像捕获模式中由图像捕获装置(如摄像头)获得的静态图片或视频的图像数据进行处理。处理后的图像帧可以显示在显示单元560上。经图形处理器541处理后的图像帧可以存储在存储器590(或其它存储介质)中或者经由射频单元510或网络模块520进行发送。麦克风542可以接收声音，并且能够将这样的声音处理为音频数据。处理后的音频数据可以 在电话通话模式的情况下转换为可经由射频单元510发送到移动通信网络侧设备的格式输出。
终端50还包括至少一种传感器550，比如光传感器、运动传感器以及其他传感器。具体地，光传感器包括环境光传感器及接近传感器，其中，环境光传感器可根据环境光线的明暗来调节显示面板561的亮度，接近传感器可在终端50移动到耳边时，关闭显示面板561和/或背光。作为运动传感器的一种，加速计传感器可检测各个方向上(一般为三轴)加速度的大小，静止时可检测出重力的大小及方向，可用于识别终端姿态(比如横竖屏切换、相关游戏、磁力计姿态校准)、振动识别相关功能(比如计步器、敲击)等；传感器550还可以包括指纹传感器、压力传感器、虹膜传感器、分子传感器、陀螺仪、气压计、湿度计、温度计、红外线传感器等，在此不再赘述。
显示单元560用于显示由用户输入的信息或提供给用户的信息。显示单元560可包括显示面板561，可以采用液晶显示器(Liquid Crystal Display，LCD)、有机发光二极管(Organic Light-Emitting Diode，OLED)等形式来配置显示面板561。
用户输入单元570可用于接收输入的数字或字符信息，以及产生与终端的用户设置以及功能控制有关的键信号输入。具体地，用户输入单元570包括触控面板571以及其他输入设备572。触控面板571，也称为触摸屏，可收集用户在其上或附近的触摸操作(比如用户使用手指、触笔等任何适合的物体或附件在触控面板571上或在触控面板571附近的操作)。触控面板571可包括触摸检测装置和触摸控制器两个部分。其中，触摸检测装置检测用户的触摸方位，并检测触摸操作带来的信号，将信号传送给触摸控制器；触摸控制器从触摸检测装置上接收触摸信息，并将它转换成触点坐标，再送给处理器511，接收处理器511发来的命令并加以执行。此外，可以采用电阻式、电容式、红外线以及表面声波等多种类型实现触控面板571。除了触控面板571，用户输入单元570还可以包括其他输入设备572。具体地，其他输入设备572可以包括但不限于物理键盘、功能键(比如音量控制按键、开关按键等)、轨迹球、鼠标、操作杆，在此不再赘述。
进一步的，触控面板571可覆盖在显示面板561上，当触控面板571检 测到在其上或附近的触摸操作后，传送给处理器511以确定触摸事件的类型，随后处理器511根据触摸事件的类型在显示面板561上提供相应的视觉输出。虽然在图5中，触控面板571与显示面板561是作为两个独立的部件来实现终端的输入和输出功能，但是在某些实施例中，可以将触控面板571与显示面板561集成而实现终端的输入和输出功能，具体此处不做限定。
接口单元580为外部装置与终端50连接的接口。例如，外部装置可以包括有线或无线头戴式耳机端口、外部电源(或电池充电器)端口、有线或无线数据端口、存储卡端口、用于连接具有识别模块的装置的端口、音频输入/输出(I/O)端口、视频I/O端口、耳机端口等等。接口单元580可以用于接收来自外部装置的输入(例如，数据信息、电力等等)并且将接收到的输入传输到终端50内的一个或多个元件或者可以用于在终端50和外部装置之间传输数据。
存储器590可用于存储软件程序以及各种数据。存储器590可主要包括存储程序区和存储数据区，其中，存储程序区可存储操作系统、至少一个功能所需的应用程序(比如声音播放功能、图像播放功能等)等；存储数据区可存储根据手机的使用所创建的数据(比如音频数据、电话本等)等。此外，存储器590可以包括高速随机存取存储器，还可以包括非易失性存储器，例如至少一个磁盘存储器件、闪存器件、或其他易失性固态存储器件。
处理器511是终端的控制中心，利用各种接口和线路连接整个终端的各个部分，通过运行或执行存储在存储器590内的软件程序和/或模块，以及调用存储在存储器590内的数据，执行终端的各种功能和处理数据，从而对终端进行整体监控。处理器511可包括一个或多个处理单元；可选的，处理器511可集成应用处理器和调制解调处理器，其中，应用处理器主要处理操作系统、用户界面和应用程序等，调制解调处理器主要处理无线通信。可以理解的是，上述调制解调处理器也可以不集成到处理器511中。
终端50还可以包括给各个部件供电的电源512(比如电池)，可选的，电源512可以通过电源管理系统与处理器511逻辑相连，从而通过电源管理系统实现管理充电、放电、以及功耗管理等功能。
另外，终端50包括一些未示出的功能模块，在此不再赘述。
可选的，本公开的一些实施例还提供一种终端，包括处理器511，存储器590，存储在存储器590上并可在所述处理器511上运行的计算机程序，该计算机程序被处理器511执行时实现应用于终端侧的数据接收方法实施例的各个过程，且能达到相同的技术效果，为避免重复，这里不再赘述。
本公开的一些实施例还提供一种计算机可读存储介质，计算机可读存储介质上存储有计算机程序，该计算机程序被处理器执行时实现应用于终端侧的数据接收方法实施例的各个过程，且能达到相同的技术效果，为避免重复，这里不再赘述。其中，所述的计算机可读存储介质，如只读存储器(Read-Only Memory，简称ROM)、随机存取存储器(Random Access Memory，简称RAM)、磁碟或者光盘等。
如图6所示，本公开的一些实施例还提供一种网络侧设备600，包括：
发送模块601，用于在网络侧设备需要进行早期数据传输EDT、且终端未处于无线资源控制RRC空闲态或RRC非激活态的情况下，在与终端进行的随机接入过程中，将EDT数据发送给所述终端，并指示所述终端进行RRC状态转换。
可选地，所述发送模块601，用于实现：
将所述EDT数据携带在RRC连接建立消息中，发送给终端。
进一步地，所述RRC连接建立消息中包含非接入层专用信息指示域，所述EDT数据位于所述非接入层专用信息指示域中。
可选地，所述发送模块601，用于实现：
合并发送无线资源控制RRC连接建立消息和RRC早期数据完成消息给所述终端；
其中，所述RRC早期数据完成消息中携带所述EDT数据。
进一步地，所述RRC早期数据完成消息位于所述RRC连接建立消息之前。
进一步地，所述网络侧设备，还包括：
指示发送模块，用于发送消息执行顺序指示信息给终端；
其中，所述消息执行顺序指示信息用于指示所述终端先获取所述RRC早期数据完成消息中的EDT数据，再根据所述RRC连接建立消息进行状态转 换；或者，
所述消息执行顺序指示信息用于指示所述终端先根据所述RRC连接建立消息进行状态转换，再获取所述RRC早期数据完成消息中的EDT数据。
进一步地，所述RRC早期数据完成消息和所述RRC连接建立消息使用不同的逻辑信道标识进行标记。
进一步地，所述RRC早期数据完成消息中携带第一指示信息，所述第一指示信息用于指示所述终端根据所述RRC早期数据完成消息进行所述EDT数据的获取。
本公开的一些实施例还提供一种网络侧设备，包括：存储器、处理器及存储在存储器上并可在处理器上运行的计算机程序，所述计算机程序被所述处理器执行时实现上述的应用于网络侧设备的数据发送方法实施例中的各个过程，且能达到相同的技术效果，为避免重复，这里不再赘述。
本公开的一些实施例还提供一种计算机可读存储介质，其中，所述计算机可读存储介质上存储有计算机程序，所述计算机程序被处理器执行时实现上述的应用于网络侧设备的数据发送方法实施例中的各个过程，且能达到相同的技术效果，为避免重复，这里不再赘述。其中，所述的计算机可读存储介质，如只读存储器(Read-Only Memory，简称ROM)、随机存取存储器(Random Access Memory，简称RAM)、磁碟或者光盘等。
图7是本公开一实施例的网络侧设备的结构图，能够实现上述的数据发送方法的细节，并达到相同的效果。如图7所示，网络侧设备700包括：处理器701、收发机702、存储器703和总线接口，其中：
处理器701，用于读取存储器703中的程序，执行下列过程：
在网络侧设备需要进行早期数据传输EDT、且终端未处于无线资源控制RRC空闲态或RRC非激活态的情况下，在与终端进行的随机接入过程中，将EDT数据发送给所述终端，并指示所述终端进行RRC状态转换。
在图7中，总线架构可以包括任意数量的互联的总线和桥，具体由处理器701代表的一个或多个处理器和存储器703代表的存储器的各种电路链接在一起。总线架构还可以将诸如外围设备、稳压器和功率管理电路等之类的各种其他电路链接在一起，这些都是本领域所公知的，因此，本文不再对其 进行进一步描述。总线接口提供接口。收发机702可以是多个元件，即包括发送机和接收机，提供用于在传输介质上与各种其他装置通信的单元。
可选地，处理器701，用于读取存储器703中的所述将早期数据传输所对应的EDT数据发送给所述终端的程序，执行下列过程：
通过收发机702将所述EDT数据携带在RRC连接建立消息中，发送给终端。
进一步地，所述RRC连接建立消息中包含非接入层专用信息指示域，所述EDT数据位于所述非接入层专用信息指示域中。
可选地，处理器701，用于读取存储器703中的所述将EDT数据发送给所述终端的程序，执行下列过程：
通过收发机702合并发送无线资源控制RRC连接建立消息和RRC早期数据完成消息给所述终端；
其中，所述RRC早期数据完成消息中携带所述EDT数据。
进一步地，所述RRC早期数据完成消息位于所述RRC连接建立消息之前。
进一步地，处理器701，用于读取存储器703中的程序，执行下列过程：
通过收发机702发送消息执行顺序指示信息给终端；
其中，所述消息执行顺序指示信息用于指示所述终端先获取所述RRC早期数据完成消息中的EDT数据，再根据所述RRC连接建立消息进行状态转换；或者，
所述消息执行顺序指示信息用于指示所述终端先根据所述RRC连接建立消息进行状态转换，再获取所述RRC早期数据完成消息中的EDT数据。
进一步地，所述RRC早期数据完成消息和所述RRC连接建立消息使用不同的逻辑信道标识进行标记。
进一步地，所述RRC早期数据完成消息中携带第一指示信息，所述第一指示信息用于指示所述终端根据所述RRC早期数据完成消息进行所述EDT数据的获取。
其中，网络侧设备可以是全球移动通讯(Global System of Mobile communication，GSM)或码分多址(Code Division Multiple Access，CDMA) 中的基站(Base Transceiver Station，BTS)，也可以是宽带码分多址(Wideband Code Division Multiple Access，WCDMA)中的基站(NodeB，NB)，还可以是LTE中的演进型基站(Evolutional Node B，eNB或eNodeB)，或者中继站或接入点，或者未来5G网络中的基站等，在此并不限定。
可以理解的是，本公开的一些实施例描述的这些实施例可以用硬件、软件、固件、中间件、微码或其组合来实现。对于硬件实现，模块、单元、子模块、子单元等可以实现在一个或多个专用集成电路(Application Specific Integrated Circuits，ASIC)、数字信号处理器(Digital Signal Processing，DSP)、数字信号处理设备(DSP Device，DSPD)、可编程逻辑设备(Programmable Logic Device，PLD)、现场可编程门阵列(Field-Programmable Gate Array，FPGA)、通用处理器、控制器、微控制器、微处理器、用于执行本申请所述功能的其它电子单元或其组合中。
以上所述的是本公开的可选实施方式，应当指出对于本技术领域的普通人员来说，在不脱离本公开所述的原理前提下还可以作出若干改进和润饰，这些改进和润饰也在本公开的保护范围内。

Claims (39)

  1. 一种数据接收方法，应用于终端，包括：
    在网络侧设备需要进行早期数据传输EDT、且所述终端处于无线资源控制RRC空闲态或RRC非激活态的情况下，在与所述网络侧设备进行的随机接入过程中，接收所述网络侧设备发送的EDT数据，并进行RRC状态转换。
  2. 根据权利要求1所述的数据接收方法，其中，所述接收所述网络侧设备发送的EDT数据，包括：
    接收所述网络侧设备发送的RRC连接建立消息；
    其中，所述RRC连接建立消息中携带所述EDT数据。
  3. 根据权利要求2所述的数据接收方法，其中，所述RRC连接建立消息中包含非接入层专用信息指示域，所述EDT数据位于所述非接入层专用信息指示域中。
  4. 根据权利要求1所述的数据接收方法，其中，所述接收所述网络侧设备发送的EDT数据，包括：
    接收所述网络侧设备合并发送的RRC连接建立消息和RRC早期数据完成消息；
    其中，所述RRC早期数据完成消息中携带所述EDT数据。
  5. 根据权利要求4所述的数据接收方法，其中，所述RRC早期数据完成消息位于所述RRC连接建立消息之前。
  6. 根据权利要求4所述的数据接收方法，还包括：
    接收网络侧设备发送的消息执行顺序指示信息；
    其中，所述消息执行顺序指示信息用于指示所述终端先获取所述RRC早期数据完成消息中的EDT数据，再根据所述RRC连接建立消息进行状态转换；或者，
    所述消息执行顺序指示信息用于指示所述终端先根据所述RRC连接建立消息进行状态转换，再获取所述RRC早期数据完成消息中的EDT数据。
  7. 根据权利要求4所述的数据接收方法，其中，所述RRC早期数据完成消息和所述RRC连接建立消息使用不同的逻辑信道标识进行标记。
  8. 根据权利要求4所述的数据接收方法，其中，所述RRC早期数据完成消息中携带第一指示信息，所述第一指示信息用于指示所述终端根据所述RRC早期数据完成消息进行所述EDT数据的获取。
  9. 根据权利要求5-8任一项所述的数据接收方法，其中，所述接收所述网络侧设备发送的EDT数据，并进行RRC状态转换，包括：
    获取所述RRC早期数据完成消息中的所述EDT数据、且终端不执行进入空闲态的操作，并根据所述RRC连接建立消息进行状态转换。
  10. 根据权利要求9所述的数据接收方法，其中，所述终端不执行进入空闲态的操作，包括：
    终端不执行媒体接入控制MAC实体复位的操作。
  11. 一种数据发送方法，应用于网络侧设备，包括：
    在网络侧设备需要进行早期数据传输EDT、且终端未处于无线资源控制RRC空闲态或RRC非激活态的情况下，在与终端进行的随机接入过程中，将EDT数据发送给所述终端，并指示所述终端进行RRC状态转换。
  12. 根据权利要求11所述的数据发送方法，其中，所述将EDT数据发送给所述终端，包括：
    将所述EDT数据携带在RRC连接建立消息中，发送给终端。
  13. 根据权利要求12所述的数据发送方法，其中，所述RRC连接建立消息中包含非接入层专用信息指示域，所述EDT数据位于所述非接入层专用信息指示域中。
  14. 根据权利要求11所述的数据发送方法，其中，所述将EDT数据发送给所述终端，包括：
    合并发送无线资源控制RRC连接建立消息和RRC早期数据完成消息给所述终端；
    其中，所述RRC早期数据完成消息中携带所述EDT数据。
  15. 根据权利要求14所述的数据发送方法，其中，所述RRC早期数据完成消息位于所述RRC连接建立消息之前。
  16. 根据权利要求14所述的数据发送方法，还包括：
    发送消息执行顺序指示信息给终端；
    其中，所述消息执行顺序指示信息用于指示所述终端先获取所述RRC早期数据完成消息中的EDT数据，再根据所述RRC连接建立消息进行状态转换；或者，
    所述消息执行顺序指示信息用于指示所述终端先根据所述RRC连接建立消息进行状态转换，再获取所述RRC早期数据完成消息中的EDT数据。
  17. 根据权利要求14所述的数据发送方法，其中，所述RRC早期数据完成消息和所述RRC连接建立消息使用不同的逻辑信道标识进行标记。
  18. 根据权利要求14所述的数据发送方法，其中，所述RRC早期数据完成消息中携带第一指示信息，所述第一指示信息用于指示所述终端根据所述RRC早期数据完成消息进行所述EDT数据的获取。
  19. 一种终端，包括：
    执行模块，用于在网络侧设备需要进行早期数据传输EDT、且所述终端处于无线资源控制RRC空闲态或RRC非激活态的情况下，在与所述网络侧设备进行的随机接入过程中，接收所述网络侧设备发送的EDT数据，并进行RRC状态转换。
  20. 根据权利要求19所述的终端，所述执行模块，用于：
    接收所述网络侧设备发送的RRC连接建立消息；
    其中，所述RRC连接建立消息中携带所述EDT数据。
  21. 根据权利要求20所述的终端，其中，所述RRC连接建立消息中包含非接入层专用信息指示域，所述EDT数据位于所述非接入层专用信息指示域中。
  22. 根据权利要求19所述的终端，所述执行模块，用于：
    接收所述网络侧设备合并发送的RRC连接建立消息和RRC早期数据完成消息；
    其中，所述RRC早期数据完成消息中携带所述EDT数据。
  23. 根据权利要求22所述的终端，其中，所述RRC早期数据完成消息位于所述RRC连接建立消息之前。
  24. 根据权利要求22所述的终端，还包括：
    指示接收模块，用于接收网络侧设备发送的消息执行顺序指示信息；
    其中，所述消息执行顺序指示信息用于指示所述终端先获取所述RRC早期数据完成消息中的EDT数据，再根据所述RRC连接建立消息进行状态转换；或者，
    所述消息执行顺序指示信息用于指示所述终端先根据所述RRC连接建立消息进行状态转换，再获取所述RRC早期数据完成消息中的EDT数据。
  25. 根据权利要求22所述的终端，其中，所述RRC早期数据完成消息和所述RRC连接建立消息使用不同的逻辑信道标识进行标记。
  26. 根据权利要求22所述的终端，其中，所述RRC早期数据完成消息中携带第一指示信息，所述第一指示信息用于指示所述终端根据所述RRC早期数据完成消息进行所述EDT数据的获取。
  27. 根据权利要求23-26任一项所述的终端，所述执行模块，用于：
    获取所述RRC早期数据完成消息中的所述EDT数据、且终端不执行进入空闲态的操作，并根据所述RRC连接建立消息进行状态转换。
  28. 根据权利要求27所述的终端，其中，所述终端不执行进入空闲态的操作，包括：
    终端不执行媒体接入控制MAC实体复位的操作。
  29. 一种终端，包括：存储器、处理器及存储在存储器上并可在处理器上运行的计算机程序，所述计算机程序被所述处理器执行时实现如权利要求1至10中任一项所述的数据接收方法的步骤。
  30. 一种网络侧设备，包括：
    发送模块，用于在网络侧设备需要进行早期数据传输、且终端未处于无线资源控制RRC空闲态或RRC非激活态的情况下，在与终端进行的随机接入过程中，将EDT数据发送给所述终端，并指示所述终端进行RRC状态转换。
  31. 根据权利要求30所述的网络侧设备，所述发送模块，用于：
    将所述EDT数据携带在RRC连接建立消息中，发送给终端。
  32. 根据权利要求31所述的网络侧设备，其中，所述RRC连接建立消息中包含非接入层专用信息指示域，所述EDT数据位于所述非接入层专用信息指示域中。
  33. 根据权利要求30所述的网络侧设备，所述发送模块，用于：
    合并发送无线资源控制RRC连接建立消息和RRC早期数据完成消息给所述终端；
    其中，所述RRC早期数据完成消息中携带所述EDT数据。
  34. 根据权利要求33所述的网络侧设备，其中，所述RRC早期数据完成消息位于所述RRC连接建立消息之前。
  35. 根据权利要求33所述的网络侧设备，还包括：
    指示发送模块，用于发送消息执行顺序指示信息给终端；
    其中，所述消息执行顺序指示信息用于指示所述终端先获取所述RRC早期数据完成消息中的EDT数据，再根据所述RRC连接建立消息进行状态转换；或者，
    所述消息执行顺序指示信息用于指示所述终端先根据所述RRC连接建立消息进行状态转换，再获取所述RRC早期数据完成消息中的EDT数据。
  36. 根据权利要求33所述的网络侧设备，其中，所述RRC早期数据完成消息和所述RRC连接建立消息使用不同的逻辑信道标识进行标记。
  37. 根据权利要求33所述的网络侧设备，其中，所述RRC早期数据完成消息中携带第一指示信息，所述第一指示信息用于指示所述终端根据所述RRC早期数据完成消息进行所述EDT数据的获取。
  38. 一种网络侧设备，包括：存储器、处理器及存储在存储器上并可在处理器上运行的计算机程序，所述计算机程序被所述处理器执行时实现如权利要求11至18中任一项所述的数据发送方法的步骤。
  39. 一种计算机可读存储介质，其中，所述计算机可读存储介质上存储有计算机程序，所述计算机程序被处理器执行时实现如权利要求1至10中任一项所述的数据接收方法的步骤或如权利要求11至18中任一项所述的数据发送方法的步骤。
PCT/CN2020/117717 2019-09-26 2020-09-25 数据接收、发送方法、终端及网络侧设备 Ceased WO2021057897A1 (zh)

Priority Applications (6)

Application Number Priority Date Filing Date Title
KR1020227010624A KR20220054658A (ko) 2019-09-26 2020-09-25 데이터 수신 방법, 데이터 송신 방법, 단말기 및 네트워크측 기기
EP20868248.4A EP4037416B1 (en) 2019-09-26 2020-09-25 Data receiving method, data sending method, terminal, and network side device
BR112022005577A BR112022005577A2 (pt) 2019-09-26 2020-09-25 Método de recepção de dados, método de envio de dados, terminal e dispositivo de lado de rede.
ES20868248T ES3055181T3 (en) 2019-09-26 2020-09-25 Data receiving method, data sending method, terminal, and network side device
PL20868248.4T PL4037416T3 (pl) 2019-09-26 2020-09-25 Sposób odbierania danych, sposób wysyłania danych, terminal oraz urządzenie po stronie sieci
US17/702,672 US12295060B2 (en) 2019-09-26 2022-03-23 Data receiving method, data sending method, terminal, and network side device

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201910920203.5A CN112566273B (zh) 2019-09-26 2019-09-26 一种数据接收、发送方法、终端及网络侧设备
CN201910920203.5 2019-09-26

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US17/702,672 Continuation US12295060B2 (en) 2019-09-26 2022-03-23 Data receiving method, data sending method, terminal, and network side device

Publications (1)

Publication Number Publication Date
WO2021057897A1 true WO2021057897A1 (zh) 2021-04-01

Family

ID=75030223

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2020/117717 Ceased WO2021057897A1 (zh) 2019-09-26 2020-09-25 数据接收、发送方法、终端及网络侧设备

Country Status (8)

Country Link
US (1) US12295060B2 (zh)
EP (1) EP4037416B1 (zh)
KR (1) KR20220054658A (zh)
CN (1) CN112566273B (zh)
BR (1) BR112022005577A2 (zh)
ES (1) ES3055181T3 (zh)
PL (1) PL4037416T3 (zh)
WO (1) WO2021057897A1 (zh)

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20220007422A1 (en) * 2020-07-02 2022-01-06 Shanghai Langbo Communication Technology Company Limited Method and device used in communication node for wireless communication
US12538349B2 (en) 2021-04-01 2026-01-27 Google Llc Managing data communication before and after a state transition

Families Citing this family (9)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN118972980A (zh) * 2019-02-14 2024-11-15 松下电器（美国）知识产权公司 终端、基站、通信方法及集成电路
EP4514046A3 (en) * 2020-05-14 2025-05-21 Koninklijke Philips N.V. Small data transmission
CN113891345B (zh) * 2020-07-03 2024-04-19 大唐移动通信设备有限公司 数据传输方法、指示方法及设备
CN115226153A (zh) * 2021-04-20 2022-10-21 大唐移动通信设备有限公司 信令发送方法、装置及存储介质
CN113207158B (zh) * 2021-04-21 2023-02-10 中国移动通信集团陕西有限公司 物联网接入的方法、装置、设备及存储介质
CN115315018B (zh) * 2021-05-08 2025-02-11 维沃移动通信有限公司 随机接入的处理方法、装置及终端
CN113365281B9 (zh) * 2021-05-10 2023-03-28 哈尔滨工业大学 一种基于移动捎带的5g物联网络架构及其数据传输方法
WO2025166775A1 (zh) * 2024-02-08 2025-08-14 北京小米移动软件有限公司 响应消息接收方法、装置
CN121645201A (zh) * 2024-08-28 2026-03-10 中国电信股份有限公司技术创新中心 通信方法及相关设备

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2018139888A1 (ko) * 2017-01-29 2018-08-02 엘지전자 주식회사 단말 컨텍스트의 관리 방법 및 이를 지원하는 장치
WO2019032222A1 (en) * 2017-08-11 2019-02-14 Qualcomm Incorporated METHODS AND APPARATUSES FOR EARLY DATA TRANSMISSION IN UPLINK
CN110063085A (zh) * 2017-09-29 2019-07-26 联发科技股份有限公司 高可靠性和数据提前传送
CN110235513A (zh) * 2017-07-27 2019-09-13 Lg电子株式会社 用于执行edt的方法和装置
CN111565459A (zh) * 2019-02-14 2020-08-21 华为技术有限公司 一种通信方法及装置

Family Cites Families (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20180324869A1 (en) * 2017-05-04 2018-11-08 Qualcomm Incorporated Uplink early data transmission
WO2018201483A1 (zh) * 2017-05-05 2018-11-08 华为技术有限公司 数据传输的方法、终端设备和接入网设备
CN110999404A (zh) * 2017-08-10 2020-04-10 京瓷株式会社 通信控制方法
US10602445B2 (en) * 2017-09-29 2020-03-24 Mediatek Inc. M2M semi-persistent scheduling in wireless communications
WO2020069103A1 (en) * 2018-09-27 2020-04-02 Intel Corporation System and methods for enabling dl-edt
US10856217B1 (en) * 2019-05-28 2020-12-01 Verizon Patent And Licensing Inc. Methods and systems for intelligent AMF assignment to minimize re-direction

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2018139888A1 (ko) * 2017-01-29 2018-08-02 엘지전자 주식회사 단말 컨텍스트의 관리 방법 및 이를 지원하는 장치
CN110235513A (zh) * 2017-07-27 2019-09-13 Lg电子株式会社 用于执行edt的方法和装置
WO2019032222A1 (en) * 2017-08-11 2019-02-14 Qualcomm Incorporated METHODS AND APPARATUSES FOR EARLY DATA TRANSMISSION IN UPLINK
CN110063085A (zh) * 2017-09-29 2019-07-26 联发科技股份有限公司 高可靠性和数据提前传送
CN111565459A (zh) * 2019-02-14 2020-08-21 华为技术有限公司 一种通信方法及装置

Non-Patent Citations (1)

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

Cited By (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20220007422A1 (en) * 2020-07-02 2022-01-06 Shanghai Langbo Communication Technology Company Limited Method and device used in communication node for wireless communication
US11856611B2 (en) * 2020-07-02 2023-12-26 Shanghai Langbo Communication Technology Company Limited Method and device for determining a type of random access procedure
US20240080906A1 (en) * 2020-07-02 2024-03-07 Shanghai Langbo Communication Technology Company Limited Method and device used in communication node for wireless communication
US12538349B2 (en) 2021-04-01 2026-01-27 Google Llc Managing data communication before and after a state transition

Also Published As

Publication number Publication date
EP4037416A1 (en) 2022-08-03
US12295060B2 (en) 2025-05-06
EP4037416C0 (en) 2025-11-05
US20220217810A1 (en) 2022-07-07
CN112566273A (zh) 2021-03-26
BR112022005577A2 (pt) 2022-06-21
EP4037416A4 (en) 2022-10-26
CN112566273B (zh) 2022-12-23
PL4037416T3 (pl) 2026-02-09
ES3055181T3 (en) 2026-02-10
EP4037416B1 (en) 2025-11-05
KR20220054658A (ko) 2022-05-03

Similar Documents

Publication Publication Date Title
CN112566273B (zh) 一种数据接收、发送方法、终端及网络侧设备
CN110769505B (zh) 随机接入方法、终端及网络设备
US11234275B2 (en) Method for receiving and sending information, user equipment and network device
CN109699067B (zh) 同步信号块的处理方法、同步信号块的指示方法及装置
US20210204331A1 (en) Random access information obtaining method, random access information sending method, and network node
CN111836280B (zh) 一种数据传输方法及终端
JP7210755B2 (ja) ランダムアクセス方法及び機器
US12219612B2 (en) Random access method, terminal, and network device
JP7235874B2 (ja) 接続管理方法、端末及びネットワーク側機器
EP3998831A1 (en) Random access method, configuration method, terminal, and network-side device
CN110719647B (zh) 一种随机接入方法、终端及网络设备
US20210219128A1 (en) Method for processing terminal device capability information, terminal device, and network-side device
WO2020200117A1 (zh) 随机接入方法、指示方法、网络设备及终端
US12295001B2 (en) Information indicating method, indication receiving method, terminal, and network-side device
WO2021012991A1 (zh) 随机接入、信息发送、资源配置方法、网络侧设备及终端
WO2020221125A1 (zh) 配置信息获取、发送方法、终端及网络侧设备
KR102851913B1 (ko) 랜덤 액세스 요청 자원의 선택 방법, 단말 및 네트워크 기기
WO2020244479A1 (zh) 连接管理方法、终端及网络侧设备
JPWO2021023219A5 (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: 20868248

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

ENP Entry into the national phase

Ref document number: 20227010624

Country of ref document: KR

Kind code of ref document: A

REG Reference to national code

Ref country code: BR

Ref legal event code: B01A

Ref document number: 112022005577

Country of ref document: BR

ENP Entry into the national phase

Ref document number: 2020868248

Country of ref document: EP

Effective date: 20220426

ENP Entry into the national phase

Ref document number: 112022005577

Country of ref document: BR

Kind code of ref document: A2

Effective date: 20220324

WWR Wipo information: refused in national office

Ref document number: 1020227010624

Country of ref document: KR

WWG Wipo information: grant in national office

Ref document number: 2020868248

Country of ref document: EP