WO2018082548A1 - 一种数据传输方法、终端及网络侧设备 - Google Patents

一种数据传输方法、终端及网络侧设备 Download PDF

Info

Publication number
WO2018082548A1
WO2018082548A1 PCT/CN2017/108642 CN2017108642W WO2018082548A1 WO 2018082548 A1 WO2018082548 A1 WO 2018082548A1 CN 2017108642 W CN2017108642 W CN 2017108642W WO 2018082548 A1 WO2018082548 A1 WO 2018082548A1
Authority
WO
WIPO (PCT)
Prior art keywords
message
data
data packet
network side
terminal
Prior art date
Application number
PCT/CN2017/108642
Other languages
English (en)
French (fr)
Inventor
张晨璐
龚海辉
秦飞
沈晓冬
丁昱
李小龙
Original Assignee
维沃移动通信有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 维沃移动通信有限公司 filed Critical 维沃移动通信有限公司
Priority to EP17868241.5A priority Critical patent/EP3537840B1/en
Priority to US16/346,868 priority patent/US11013026B2/en
Priority to ES17868241T priority patent/ES2926392T3/es
Publication of WO2018082548A1 publication Critical patent/WO2018082548A1/zh
Priority to US17/227,594 priority patent/US11546932B2/en

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W92/00—Interfaces specially adapted for wireless communication networks
    • H04W92/04—Interfaces between hierarchically different network devices
    • H04W92/10—Interfaces between hierarchically different network devices between terminal device and access point, i.e. wireless air interface
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/12—Wireless traffic scheduling
    • H04W72/1263—Mapping of traffic onto schedule, e.g. scheduled allocation or multiplexing of flows
    • H04W72/1268—Mapping of traffic onto schedule, e.g. scheduled allocation or multiplexing of flows of uplink data flows
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/20—Control channels or signalling for resource management
    • H04W72/23—Control channels or signalling for resource management in the downlink direction of a wireless link, i.e. towards a terminal
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/50—Allocation or scheduling criteria for wireless resources
    • H04W72/56—Allocation or scheduling criteria for wireless resources based on priority criteria
    • H04W72/566—Allocation or scheduling criteria for wireless resources based on priority criteria of the information or information source or recipient
    • H04W72/569—Allocation or scheduling criteria for wireless resources based on priority criteria of the information or information source or recipient of the traffic information
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W74/00—Wireless channel access
    • H04W74/08—Non-scheduled access, e.g. ALOHA
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • 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
    • 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

Definitions

  • the present disclosure relates to the field of communications technologies, and in particular, to a data transmission method, a terminal, and a network side device.
  • 5G technology has become the development direction of the next generation mobile communication technology.
  • the connection density will reach 1 million / Km 2
  • the end-to-end minimum delay will reach 1 ms. This puts extremely high demands on the standardization of mobile communications.
  • the future 5G will support all vertical industries, and new technologies will incubate many new business forms.
  • 3GPP three major application scenarios have been identified:
  • eMBB Enhanced Mobile Broadband Communication, Enhanced mobile broadband
  • uRLLC Ultra reliable and low latency communications
  • the mMTC scenario is mainly aimed at the optimization of the Internet of Things scene, such as smart water meters, smart meters, wearable devices, and the like.
  • the Internet of Things scene such as smart water meters, smart meters, wearable devices, and the like.
  • One of the main features of this scenario is: a large number of terminals and connections, relatively small data to send requirements and data concurrency.
  • the uRLLC scene is also an important scene of 5G such as the Internet of Things scene, VR/AR application, telemedicine and other scenarios. In this scenario, there is a very low user plane and signaling plane delay from end to end.
  • the method for sending the uplink data packet to the terminal access network is as follows: first, the terminal initiates a random access request message, and then the network side device responds to the random access request message, and returns a random access response. And sending an initial RRC message according to the data sending parameter configured by the random access response message, and finally starting the initial RRC message according to the network side device.
  • the process of establishing an RRC connection after the RRC connection, sends the uplink data packet to the core network. Due to the poor flexibility of network control, an RRC connection needs to be established each time an uplink packet is sent, so it is not applicable to scenarios with low latency requirements.
  • the embodiments of the present disclosure provide a data transmission method, a terminal, and a network side device, to solve the problem of performing state transition every time uplink data is sent.
  • an embodiment of the present disclosure provides a data transmission method, including:
  • the data message carrying the state transition data is sent to the network side device;
  • the uplink data packet is sent to the network side device.
  • an embodiment of the present disclosure further provides a data transmission method, including:
  • an embodiment of the present disclosure further provides a terminal, where the terminal includes:
  • a data message sending module configured to send a data message carrying the state transition data to the network side device before establishing the air interface signaling connection
  • a response message receiving module configured to receive a response message returned by the network side device to the data message, where the response message carries a data sending indication
  • a data packet sending module configured to send an uplink data packet to the network side device when the data sending indication is sent.
  • the embodiment of the present disclosure further provides a network side device, where the network side device includes:
  • a data message receiving module configured to receive, by the terminal, a data message that carries the state transition data sent before establishing the air interface signaling connection;
  • a response message sending module configured to return, according to the data message, a response message to the terminal, where the response message carries a data sending indication
  • the data packet receiving module is configured to receive, by the terminal, an uplink data packet that is sent when the data sending indication is sent.
  • an embodiment of the present disclosure further provides a mobile terminal, including: a memory, a processor, and a computer program stored on the memory and executable on the processor, the processor executing the computer
  • the steps of the data transmission method in the first aspect are implemented in the program.
  • an embodiment of the present disclosure further provides a network side device, including: a memory, a processor, and a computer program stored on the memory and executable on the processor, where the processor performs the The computer program implements the steps of the data transmission method in the second aspect.
  • the data message carrying the state transition data is sent to the network side device; the response message returned by the network side device to the data message is received, and the response message carries the data sending indication. And sending an uplink data packet to the network side device when the data sending indication is sending. Since the uplink data packet can be controlled to be transmitted to the RRC connection state, the delay requirement of the service data can be effectively reduced, thereby improving the flexibility of the network behavior.
  • FIG. 1 is a flowchart of a data transmission method according to a first embodiment of the present disclosure
  • FIG. 2 is a flowchart of a data transmission method according to a second embodiment of the present disclosure
  • FIG. 3 is a second flowchart of a data transmission method according to a second embodiment of the present disclosure.
  • FIG. 4 is a third flowchart of a data transmission method according to a second embodiment of the present disclosure.
  • FIG. 5 is a third flowchart of a data transmission method according to a second embodiment of the present disclosure.
  • FIG. 6 is a fourth flowchart of a data transmission method according to a second embodiment of the present disclosure.
  • FIG. 7 is a flowchart of a data transmission method according to a third embodiment of the present disclosure.
  • FIG. 8 is a flowchart of a data transmission method according to a fourth embodiment of the present disclosure.
  • FIG. 9 is a second flowchart of a data transmission method according to a fourth embodiment of the present disclosure.
  • FIG. 10 is a third flowchart of a data transmission method according to a fourth embodiment of the present disclosure.
  • FIG. 11 is a schematic structural diagram of a terminal according to a fifth embodiment of the present disclosure.
  • FIG. 12 is a second structural diagram of a terminal according to a fifth embodiment of the present disclosure.
  • FIG. 13 is a third structural diagram of a terminal according to a fifth embodiment of the present disclosure.
  • FIG. 14 is a fourth structural diagram of a terminal according to a fifth embodiment of the present disclosure.
  • FIG. 15 is a schematic structural diagram of a network side device according to a sixth embodiment of the present disclosure.
  • FIG. 16 is a second structural diagram of a network side device according to a sixth embodiment of the present disclosure.
  • 17 is a third structural structure of a network side device according to a sixth embodiment of the present disclosure.
  • FIG. 18 is a fourth structural diagram of a network side device according to a sixth embodiment of the present disclosure.
  • FIG. 19 is a structural diagram of a mobile terminal to which the seventh embodiment of the present disclosure is applied.
  • FIG. 20 is a structural diagram of a mobile terminal to which the eighth embodiment of the present disclosure is applied.
  • FIG. 1 is a flowchart of a data transmission method according to an embodiment of the present disclosure. As shown in FIG. 1, the method includes the following steps:
  • Step 101 Before establishing the air interface signaling connection, send a data message carrying the state transition data to the network side device.
  • the air interface signaling is a data transmission signaling protocol between the end and the end.
  • the existing air interface signaling includes radio resource control protocol signaling.
  • the radio resource control protocol is RRC (Radio Resource Control)
  • the state transition data is a data feature for a data transmission manner for responding to whether or not to support state transition.
  • the state transition refers to a change in the connection state of the RRC. Specifically, it means that the RRC connection is not established to the recommended RRC connection.
  • the type of the above data features can be
  • the setting may be based on actual needs, and may be, for example, a determination condition of whether or not to support the data transmission method in which state transition is not performed, or a determination result of the determination condition, which will be described in detail in the following embodiments.
  • the above network side device refers to a base station.
  • the mobile terminal when the mobile terminal does not generate service data for a long time, the mobile terminal will automatically disconnect the RRC connection from the core network.
  • the uplink service data uplink data packet
  • an RRC connection may be required to be sent to the core network.
  • data pack the type of the service data may be any type, such as a smart water meter service, a car network service, and an eMBB (Enhanced Mobile Broadband communication) service.
  • Step 102 Receive a response message returned by the network side device to the data message, where the response message carries a data sending indication.
  • the foregoing data transmission indication includes two states of sending and not transmitting.
  • the network side device After receiving the data message, the network side device will respond to the data message, and the data sending indication will be carried in the response message. Specifically, the manner of response matches the content of the data message. Since the state transition data in the foregoing data message can be in multiple forms, the corresponding response mode can be correspondingly set to multiple response modes. For example, when the state transition data is a condition for determining whether to support the data transmission mode in which the state transition is not performed, the network side device determines, according to the determination condition, whether the terminal supports the data transmission mode in which the state transition is not performed, thereby transmitting the data transmission indication.
  • the data transmission indication may be directly sent according to the determination result, or the network side information acquired by the network side device may be used to determine whether the terminal is allowed to perform data without state transition. Send, and then send a data transmission indication.
  • Step 103 When the data sending indication is sent, send an uplink data packet to the network side device.
  • the terminal performs a corresponding operation according to the data transmission indication in the response message.
  • the uplink data packet may be sent to the network side device, and after receiving the uplink data packet, the network side device sends the uplink data packet to the core network, thereby completing the uplink data. The delivery of the package.
  • the determination rule of the data transmission mode that does not support the state transition of the different service data can be set according to actual needs, and is not further limited herein.
  • the foregoing terminal may be any mobile device having the function of displaying and installing an application.
  • Mobile terminals such as mobile phones, tablet personal computers, laptop computers, personal digital assistants (PDAs), mobile Internet devices (MIDs) or wearables Equipment (Wearable Device), etc.
  • PDAs personal digital assistants
  • MIDs mobile Internet devices
  • WPAs wearables Equipment
  • the data message carrying the state transition data is sent to the network side device; the response message returned by the network side device to the data message is received, and the response message carries the data sending indication. And sending an uplink data packet to the network side device when the data sending indication is sending. Since the uplink data packet can be controlled to be transmitted to the RRC connection state, the delay requirement of the service data can be effectively reduced, thereby improving the flexibility of the network behavior.
  • the present disclosure can solve a large number of mMTC (Massive Machine Type Communication) access networks for bursty small data packet transmission in an Internet of Things (IoT) scenario, because it needs to migrate from the terminal IDLE state to the RRC state zone.
  • IoT Internet of Things
  • FIG. 2 is a flowchart of a data transmission method according to an embodiment of the present disclosure. As shown in FIG. 2, the method includes the following steps:
  • Step 201 Before establishing the air interface signaling connection, send a data message carrying the state transition data to the network side device.
  • the air interface signaling is a data transmission signaling protocol between the end and the end.
  • the existing air interface signaling includes radio resource control protocol signaling.
  • the radio resource control protocol is RRC (Radio Resource Control)
  • the state transition data is a data feature for a data transmission manner for responding to whether or not to support state transition.
  • the state transition refers to a change in the connection state of the RRC. Specifically, it means that the RRC connection is not established to the recommended RRC connection.
  • the type of the data feature may be set according to actual needs, for example, a determination condition of whether or not to support the data transmission mode in which the state transition is not performed, or a determination result of the determination condition, which will be described in detail in the following embodiments.
  • the above network side device refers to a base station.
  • the data message is a random access request message. That is, in the random access procedure, it is determined whether to establish a radio resource control protocol connection to send an uplink data packet. Specifically, msg1 to msg4 are included in the random access procedure, where msg1 is a random access request message, msg2 is a random access response message replied to the random access request message, and msg3 is an initial RRC message, msg4 A reply message to the initial RRC message. In this embodiment, the state transition data is carried in the msg1 sent by the terminal.
  • the mobile terminal when the mobile terminal does not generate service data for a long time, the mobile terminal will automatically disconnect the RRC connection from the core network.
  • the uplink service data uplink data packet
  • an RRC connection may be required to be sent to the core network.
  • data pack the type of the service data may be any type, such as a smart water meter service, a car network service, and an eMBB (Enhanced Mobile Broadband communication) service.
  • Step 202 Receive a response message returned by the network side device to the data message, where the response message carries a data sending indication.
  • the foregoing data transmission indication includes two states of sending and not transmitting.
  • the network side device After receiving the data message, the network side device will respond to the data message, and the data sending indication will be carried in the response message. Specifically, the manner of response matches the content of the data message. Since the state transition data in the foregoing data message can be in multiple forms, the corresponding response mode can be correspondingly set to multiple response modes. For example, when the state transition data is a condition for determining whether to support the data transmission mode in which the state transition is not performed, the network side device determines, according to the determination condition, whether the terminal supports the data transmission mode in which the state transition is not performed, thereby transmitting the data transmission indication.
  • the data transmission indication may be directly sent according to the determination result, or the network side information acquired by the network side device may be used to determine whether the terminal is allowed to perform data without state transition. Send, and then send a data transmission indication. For example, when the network side device does not support data transmission without state transition, the data transmission indication may be directly set to not be transmitted.
  • the foregoing random access response message further carries an uplink timing TA used for uplink synchronization, a temporary identifier C-RNTI used as a temporary identifier UE, used as uplink power control signaling P, and used as msg3.
  • the scheduled uplink scheduling indication (UL grant); the time for transmitting the uplink data packet can be controlled according to the parameter value of each parameter in the random access response message.
  • Step 203 When the data message is a random access request message, and the response message is a random access response message, when the data sending indication is sent, the random access response message is carried.
  • the uplink frequency indication location indicated by the uplink scheduling indication sends an uplink data packet, or sends an uplink data packet to the network side device on a default physical channel.
  • the terminal After the terminal receives the response message of the network side device, the terminal will cancel according to the response.
  • the data transmission in the message indicates that the corresponding operation is performed.
  • the uplink data packet may be sent to the network side device, and after receiving the uplink data packet, the network side device sends the uplink data packet to the core network, thereby completing the uplink data. The delivery of the package.
  • the determination rule of the data transmission mode that does not support the state transition of the different service data can be set according to actual needs, and is not further limited herein.
  • the manner in which the uplink data packet is sent may be set according to actual needs, for example, may be sent on a default physical channel, or may be sent in a time-frequency domain location indicated by the uplink scheduling indication.
  • the default physical channel refers to the physical channel (pre-configured physical channel) known by the terminal.
  • the method for transmitting the uplink data packet may be set according to actual needs.
  • the random access response message may be configured to carry a selection identifier for indicating the manner of sending the uplink data packet.
  • the uplink scheduling indication is not included in the message, the default physical channel is used to send uplink packets by default.
  • the mobile terminal may be any mobile terminal having the function of displaying and installing an application, such as a mobile phone, a tablet personal computer, a laptop computer, and a personal digital assistant.
  • PDA Personal Digital Assistant
  • MID Mobile Internet Device
  • Wearable Device any mobile terminal having the function of displaying and installing an application, such as a mobile phone, a tablet personal computer, a laptop computer, and a personal digital assistant.
  • PDA Personal Digital Assistant
  • MID Mobile Internet Device
  • Wearable Device any mobile terminal having the function of displaying and installing an application, such as a mobile phone, a tablet personal computer, a laptop computer, and a personal digital assistant.
  • PDA Personal Digital Assistant
  • MID Mobile Internet Device
  • Wearable Device any mobile terminal having the function of displaying and installing an application, such as a mobile phone, a tablet personal computer, a laptop computer, and a personal digital assistant.
  • PDA Personal Digital Assistant
  • MID Mobile Internet Device
  • Wearable Device any mobile terminal having the function of displaying and installing an application, such as
  • the data message carrying the state transition data is sent to the network side device; the response message returned by the network side device to the data message is received, and the response message carries the data sending indication.
  • the data message is a random access request message
  • the response message is a random access response message
  • the uplink scheduling carried in the random access response message Instructing the indicated time-frequency domain location to send an uplink data packet, or sending an uplink data packet to the network side device on a default physical channel. Since the uplink data packet can be controlled to be transmitted to the RRC connection state, the delay requirement of the service data can be effectively reduced, thereby improving the flexibility of the network behavior.
  • the present disclosure can solve a large number of mMTC (Massive Machine Type Communication) access networks for bursty small data packet transmission in an Internet of Things (IoT) scenario, because it needs to migrate from the terminal IDLE state to the RRC state zone.
  • IoT Internet of Things
  • the network side device determines before sending the msg4, and then determines to send the content of the msg4 according to the result of the determination; or after the device receives the msg4, first determines whether the terminal supports the terminal. If the data transmission mode of the state transition data is not performed, the data message of the state transition data is sent to the network side device, and then whether the data transmission is performed before the signaling connection is determined according to the result of the feedback of the network side device.
  • the method further includes:
  • Step 204 When the data transmission indication is not to be sent, send an initial radio resource control protocol message in a time-frequency domain location indicated by the uplink scheduling indication.
  • the foregoing data transmission indication includes two schemes of not transmitting and transmitting
  • an RRC connection needs to be established, and the RRC connection procedure may be entered.
  • the initial radio resource control protocol message is sent in the time-frequency domain location indicated by the uplink scheduling indication, that is, the msg3 is sent, and then the network side device determines whether the terminal is allowed to establish an RRC connection, and returns the msg3 through the msg4. Reply to tell the terminal whether to allow the establishment of an RRC connection. If allowed, an RRC connection can be established and the uplink packet can be sent after the connection is established.
  • the type of the data feature may be set according to actual needs, for example, a judgment condition of whether to support a data transmission mode in which state transition is not performed, or a determination result of the determination condition. This is described in detail below:
  • the terminal determines by the terminal whether to support data transmission without state transition.
  • the foregoing state transition data includes a data sending identifier, where the data sending identifier includes an identifier carried by the random access request message or a random preamble sequence carried by the random access request message.
  • the terminal determines whether to support the data transmission mode that does not perform state transition.
  • the data transmission identifier is sent in two ways. When the identifier is used, it is a plaintext transmission mode. For example, a 1-bit identifier may be used. If the identifier is equal to 1 to indicate migration, the identifier is equal to 0 to indicate no migration.
  • a random preamble sequence is used as the data transmission identifier, it is a secret text transmission manner. Specifically, the random preamble sequence includes a first type of random preamble sequence for identifying a migration and a second type of random preamble sequence for identifying a non-migration.
  • An identification bit used to indicate the transmission of data ie, the identifier is superimposed on a random preamble sequence.
  • the security of data transmission can be improved. For example, when the data transmission mode without state transition is not supported, the first type of random preamble sequence is used for random access; when the data transmission mode without state transition is supported, the second type of random preamble sequence is used for random access.
  • the method further includes:
  • Step 205 Acquire service characteristic information of the uplink data packet.
  • the terminal may obtain the service feature information of the uplink data packet.
  • the content of the service feature information may be set according to actual needs.
  • the service feature information includes At least one of a service type, a service cache information, a service quality requirement, and a service priority.
  • the service type includes the smart water meter service, the car network service, and the eMBB service;
  • the service cache information is the amount of the user's uplink data cache, for example, the specific cache amount (such as XX bit);
  • the service service quality requirement is the Qos parameter, which may include Packet loss rate, maximum delay, etc.; service priority can be high priority, medium priority, and low priority.
  • Step 206 Determine, according to the service feature information, whether data transmission is needed.
  • the state transition data carried by the data message is: determining whether a data transmission result is needed. After the service feature information is obtained, according to the service feature information, whether the data transmission mode that does not perform the state transition is supported according to a predefined rule. For example, when the required delay is low, and the amount of uplink data buffer of the user is low, it can be determined to support data that does not undergo state transition; when the required delay is high, and the user has a higher amount of data cache, It is determined that data that does not undergo state transition is not supported.
  • the determination rule of the data transmission method for judging whether or not to support the state transition based on the service feature information is not enumerated here.
  • the network side information acquired by the network side device may be used to determine whether to support the data transmission mode without state transition to optimize the network state.
  • the network side information may include at least one of a network side load status, a terminal subscription data, and operator configuration data.
  • the network-side load status includes the load status of the network-side device and/or the load status of the core network;
  • the subscription data of the terminal includes the terminal subscription type and the terminal subscription priority level, and
  • the carrier configuration data includes whether the carrier configuration supports the status. Data that is not migrated is sent.
  • the foregoing state transition data includes service feature information, where the service feature information is used by the network side device to determine whether data transmission is required according to the service feature information; or the network The side device determines whether data transmission is required according to the service characteristic information and the network side information acquired by the network side device.
  • the terminal may obtain the service feature information of the uplink data packet.
  • the content of the service feature information may be set according to actual needs.
  • the service feature information includes At least one of a service type, a service cache information, a service quality requirement, and a service priority.
  • the service type includes the smart water meter service, the car network service, and the eMBB service;
  • the service cache information is the amount of the user's uplink data cache, for example, the specific cache amount (such as XX bit);
  • the service service quality requirement is the Qos parameter, which may include Packet loss rate, maximum delay, etc.; service priority can be high priority, medium priority, and low priority.
  • the service cache information is represented by the cache amount (such as N bit) or by the cache level (high, medium, low, or the level number corresponding to the amount of data to be sent (such as 1 to 100 bit number is group 1, and the group number 1 is used)) Express
  • the service quality requirement is expressed by the quality of service parameter (such as low/high delay, small/large data packet), or by the number of the quality of service parameter group (such as QCI serial number), or by the packet loss rate and Maximum allowable delay (ie implicit) representation;
  • the quality of service parameter such as low/high delay, small/large data packet
  • the number of the quality of service parameter group such as QCI serial number
  • the packet loss rate and Maximum allowable delay ie implicit
  • Business priorities are represented by high priority, medium priority, and low priority.
  • the network side device determines whether to support the data transmission mode without state transition according to the service feature information, and the determination rule for whether to support the data transmission mode that does not perform the state transition may be The rules for the terminal to make judgments are the same.
  • the network side information acquired by the network side device may be used for determining.
  • the network side information includes at least a network side load status, a terminal subscription data, and an operator configuration data.
  • the network-side load status includes the load status of the network-side device and/or the load status of the core network.
  • the subscription data of the terminal includes the terminal subscription type and the terminal subscription priority level.
  • the carrier configuration data includes whether the carrier configuration support is not performed. State transition The method of sending data to be moved.
  • the uplink data packet carries a completion identifier for identifying whether the uplink data packet is sent, and after the step 203, the method further includes:
  • Step 207 Receive a feedback message that the network side device returns according to the uplink data packet receiving status and the completion identifier.
  • the signaling type of the feedback message may be set according to actual needs.
  • the feedback message is the foregoing msg4. That is, in the present embodiment, the uplink packet is placed in msg3 for transmission. It can be understood that the manner in which the uplink data packet is sent in the msg3 for sending may be set according to actual needs.
  • the foregoing step 203 includes: placing the uplink data packet in media access.
  • the control layer (MAC, Media Access Control) data packet or the RRC layer signaling placed in the medium access control layer data packet is sent in the time-frequency domain location indicated by the uplink scheduling indication.
  • the uplink data packet is placed in the initial radio resource control protocol message, and the connection reason for configuring the initial radio resource control protocol message is uplink data packet transmission.
  • the initial RRC connection request message may be an RRC Connection Request message or an RRC Connection Resume Request message.
  • the feedback message to the initial RRC message in msg4 may include RRC Connection Reject or RRC Connection Resume Reject, and the rejection reason is “completed data transmission”. ".
  • the feedback message to the initial RRC message in msg4 may include RRC Connection Setup or RRC Connection Resume, and includes allowing the connection to be established. the reason.
  • the feedback message to the initial RRC message in msg4 may include RRC Connection Reject or RRC Connection Resume Reject, and includes the reason for rejection. It is "retransmitted” and carries the reassigned time-frequency domain location (ie, slot resource).
  • Step 208 When the feedback message is marked as successful, the uplink data packet is stopped or an air interface signaling connection is established.
  • the uplink data packet transmission may be stopped; if the uplink data packet is not transmitted, the air interface signaling connection may be established.
  • the feedback message of the network side device according to the uplink data packet receiving state and the completion identifier reply includes: when the uplink data packet is successfully received, if the completion identifier is completed, the feedback message carries There is a reject message for canceling the initial radio resource control protocol; if the completion flag is incomplete, the feedback message carries an allow connection message for establishing an initial radio resource control protocol.
  • the foregoing completion identifier may be set according to an actual situation, for example, it may be identified whether the uplink data packet is the last data packet. When it is the last packet, it indicates that the transmission has been completed.
  • the uplink data packet sent is relatively small, and can be sent once, it can be directly sent.
  • a certain number of uplink data packets may be preferentially transmitted in a non-RRC connection state, and then the next uplink data packet is sent after the RRC connection is established. Therefore, the transmission of network data packets can be well controlled.
  • Step 209 When the feedback message is marked as a failure, the uplink data packet is resent in the time-frequency domain location indicated by the re-determined uplink scheduling indication carried in the feedback message, or the allowed connection is carried according to the feedback message.
  • the message establishes an air interface signaling connection.
  • establishing an air interface signaling connection is: establishing a radio resource control protocol connection.
  • the network side device may determine whether to perform data retransmission or state transition according to actual conditions (for example, the load status on the network side).
  • the feedback message may be carried by the re-determined uplink scheduling indication, and then the terminal resends the uplink data packet in the time-frequency domain location indicated by the re-determined uplink scheduling indication carried in the feedback message.
  • the permission connection message that is, the foregoing RRC Connection Setup or RRC Connection Resume, is carried in the feedback message, so that the terminal initiates the process of establishing the RRC.
  • the network side device when the network side device fails to receive the uplink data packet, the network side device can comprehensively consider the state of the network side, and the network side device determines to perform the retransmission or the state transition, thereby improving the flexibility of the network control.
  • the multiple random terminals may select the same random preamble sequence, which may cause interference when the network side device receives the message, and finally form a random access conflict.
  • the increase in the number of 5G terminals will increase the random preamble sequence space, because the possibility of collision of random preambles will not be proportional to the number of 5G terminals.
  • conflicts such as conflicts, which are resolved as follows.
  • the terminal does not blindly detect its own RA-RNTI in the PDCCH (Physical Downlink Control Channel) in the process of receiving the msg2, the msg1 preamble transmission fails, and the terminal sends the random preamble again according to the preset mode. ;
  • the terminal If the terminal detects its own RA-RNTI in the PDCCH and receives the RAPID (random preamble sequence) corresponding to itself in the MAC (Medium Access Control Layer) data packet, it indicates that the msg1 preamble is successfully transmitted. .
  • the terminal sends the random access again according to the configured backoff value of the MAC data packet
  • the terminal sends an uplink data packet at the time-frequency domain location indicated in msg2. If multiple terminals use the same random preamble sequence and time-frequency domain location, and the time-frequency domain locations allocated in msg2 used by multiple terminals are the same, a collision occurs.
  • the terminal determines whether the uplink data packet sent by itself is successfully received by receiving msg4, and retransmits if it is not successful.
  • the network side device may consider retransmission or state transition according to the reception condition of the uplink data packet.
  • the manner of sending the identifier to the network side device belongs to the terminal decision; and the terminal directly sends the service feature information to the network side device.
  • the manner in which the network side device determines whether to support data transmission without state transition belongs to the base station decision.
  • the service feature information can be directly obtained in the terminal, and the data transmission mode without state transition can be determined before the access process is triggered. Therefore, the method of terminal decision-making can reduce the time for data transmission. That is to say, in the present embodiment, the decision by the terminal is faster than the decision by the base station.
  • FIG. 7 is a flowchart of a data transmission method according to an embodiment of the present disclosure. As shown in FIG. 7, the method includes the following steps:
  • Step 701 The data message that carries the state transition data sent by the receiving terminal before establishing the air interface signaling connection.
  • the air interface signaling is a data transmission signaling protocol between the end and the end, for example.
  • existing air interface signaling includes radio resource control protocol signaling.
  • the radio resource control protocol is RRC (Radio Resource Control)
  • the state transition data is a data feature for a data transmission manner for responding to whether or not to support state transition.
  • the state transition refers to a change in the connection state of the RRC. Specifically, it means that the RRC connection is not established to the recommended RRC connection.
  • the type of the data feature may be set according to actual needs, for example, a determination condition of whether or not to support the data transmission mode in which the state transition is not performed, or a determination result of the determination condition, which will be described in detail in the following embodiments.
  • the above network side device refers to a base station.
  • the mobile terminal when the mobile terminal does not generate service data for a long time, the mobile terminal will automatically disconnect the RRC connection from the core network.
  • the uplink service data uplink data packet
  • an RRC connection may be required to be sent to the core network.
  • data pack the type of the service data may be any type, such as a smart water meter service, a car network service, and an eMBB (Enhanced Mobile Broadband communication) service.
  • Step 702 Return, according to the data message, a response message to the terminal, where the response message carries a data transmission indication.
  • both the sending and the non-sending states are included.
  • the network side device After receiving the data message, the network side device will respond to the data message, and the data sending indication will be carried in the response message. Specifically, the manner of response matches the content of the data message. Since the state transition data in the foregoing data message can be in multiple forms, the corresponding response mode can be correspondingly set to multiple response modes. For example, when the state transition data is a condition for determining whether to support the data transmission mode in which the state transition is not performed, the network side device determines, according to the determination condition, whether the terminal supports sending data in the case of no state transition, thereby transmitting data transmission.
  • the data transmission instruction may be directly sent according to the judgment result, or the network side information acquired by the network side device may be used to determine whether the terminal is allowed to perform the state transition without the state transition. Data transmission is performed to deliver a data transmission indication.
  • Step 703 The uplink data packet sent by the receiving terminal when the data sending indication is sent.
  • the terminal performs a corresponding operation according to the data transmission indication in the response message.
  • the uplink data packet may be sent to the network side device, and after receiving the uplink data packet, the network side device sends the uplink data packet to the core network, thereby completing the uplink data. The delivery of the package.
  • the determination rule of the data transmission mode that does not support the state transition of the different service data can be set according to actual needs, and is not further limited herein.
  • the terminal may be any mobile terminal having the function of displaying and installing an application, such as a mobile phone, a tablet personal computer, a laptop computer, and a personal digital assistant. , referred to as PDA), Mobile Internet Device (MID) or Wearable Device.
  • PDA mobile phone, a tablet personal computer, a laptop computer, and a personal digital assistant.
  • MID Mobile Internet Device
  • Wearable Device any mobile terminal having the function of displaying and installing an application, such as a mobile phone, a tablet personal computer, a laptop computer, and a personal digital assistant.
  • PDA mobile phone
  • MID Mobile Internet Device
  • Wearable Device a mobile Internet Device
  • the receiving terminal sends a data message carrying the state transition data before establishing the air interface signaling connection, and returns a response message to the terminal according to the data message, where the response message carries the data.
  • the present disclosure can solve a large number of mMTC (Massive Machine Type Communication) access networks for bursty small data packet transmission in an Internet of Things (IoT) scenario, because it needs to migrate from the terminal IDLE state to the RRC state zone.
  • IoT Internet of Things
  • FIG. 8 is a flowchart of a data transmission method according to an embodiment of the present disclosure. As shown in FIG. 8, the method includes the following steps:
  • Step 801 The data message that carries the state transition data sent by the receiving terminal before establishing the air interface signaling connection.
  • the air interface signaling is a data transmission signaling protocol between the end and the end.
  • the existing air interface signaling includes radio resource control protocol signaling.
  • the radio resource control protocol is RRC (Radio Resource Control)
  • the state transition data is a data feature for a data transmission manner for responding to whether or not to support state transition.
  • the state transition refers to a change in the connection state of the RRC. Specifically, it means that the RRC connection is not established to the recommended RRC connection.
  • the type of the data feature may be set according to actual needs, for example, a determination condition of whether or not to support the data transmission mode in which the state transition is not performed, or a determination result of the determination condition, which will be described in detail in the following embodiments.
  • the above network side device refers to a base station.
  • the data message is a random access request message. That is, in the random access procedure, it is determined whether to establish a radio resource control protocol connection to send an uplink data packet. Specifically, msg1 to msg4 are included in the random access procedure, where msg1 is a random access request message, msg2 is a random access response message replied to the random access request message, msg3 is an initial RRC message, and msg4 is an initial RRC message. Reply message. In this embodiment, the state transition data is carried in the msg1 sent by the terminal.
  • the mobile terminal when the mobile terminal does not generate service data for a long time, the mobile terminal will automatically disconnect the RRC connection from the core network.
  • the uplink service data uplink data packet
  • an RRC connection may be required to be sent to the core network.
  • data pack the type of the service data may be any type, such as a smart water meter service, a car network service, and an eMBB (Enhanced Mobile Broadband communication) service.
  • Step 802 Return, according to the data message, a response message to the terminal, where the response message carries a data transmission indication.
  • the foregoing data transmission indication includes two states of sending and not transmitting.
  • the network side device After receiving the data message, the network side device will respond to the data message, and the data sending indication will be carried in the response message. Specifically, the manner of response matches the content of the data message. Since the state transition data in the foregoing data message can be in multiple forms, the corresponding response mode can be correspondingly set to multiple response modes. For example, when the state transition data is a condition for determining whether to support the data transmission mode in which the state transition is not performed, the network side device determines, according to the determination condition, whether the terminal supports sending data without performing state transition, thereby transmitting data.
  • the data transmission indication may be directly sent according to the judgment result, or the network side information acquired by the network side device may be used to determine whether the terminal is allowed to perform the state transition. Data transmission is performed to deliver a data transmission indication. For example, when the network side device does not support data transmission without state transition, the data transmission indication may be directly set to not be transmitted.
  • the foregoing random access response message further carries an uplink timing TA used for uplink synchronization, a temporary identifier C-RNTI used as a temporary identifier UE, used as uplink power control signaling P, and used as msg3.
  • the scheduled uplink scheduling indication (UL grant); the time for transmitting the uplink data packet can be controlled according to the parameter value of each parameter in the random access response message.
  • Step 803 When the data message is a random access request message, and the response message is a random access response message, the time frequency indicated by the uplink scheduling indication carried by the receiving terminal in the random access response message is received by the receiving terminal.
  • the terminal performs a corresponding operation according to the data transmission indication in the response message.
  • the uplink data packet may be sent to the network side device, and after receiving the uplink data packet, the network side device sends the uplink data packet to the core network, thereby completing the uplink data. The delivery of the package.
  • the determination rule of the data transmission mode that does not support the state transition of the different service data can be set according to actual needs, and is not further limited herein.
  • the manner in which the uplink data packet is sent may be set according to actual needs, for example, may be sent on a default physical channel, or may be sent in a time-frequency domain location indicated by the uplink scheduling indication.
  • the default physical channel refers to the physical channel (pre-configured physical channel) known by the terminal.
  • the method for transmitting the uplink data packet may be set according to actual needs.
  • the random access response message may be configured to carry a selection identifier for indicating the manner of sending the uplink data packet.
  • the uplink scheduling indication is not included in the message, the default physical channel is used to send uplink packets by default.
  • the mobile terminal may be any mobile terminal having the function of displaying and installing an application, such as a mobile phone, a tablet personal computer, a laptop computer, and a personal digital assistant.
  • PDA Personal Digital Assistant
  • MID Mobile Internet Device
  • Wearable Device any mobile terminal having the function of displaying and installing an application, such as a mobile phone, a tablet personal computer, a laptop computer, and a personal digital assistant.
  • PDA Personal Digital Assistant
  • MID Mobile Internet Device
  • Wearable Device any mobile terminal having the function of displaying and installing an application, such as a mobile phone, a tablet personal computer, a laptop computer, and a personal digital assistant.
  • PDA Personal Digital Assistant
  • MID Mobile Internet Device
  • Wearable Device any mobile terminal having the function of displaying and installing an application, such as a mobile phone, a tablet personal computer, a laptop computer, and a personal digital assistant.
  • PDA Personal Digital Assistant
  • MID Mobile Internet Device
  • Wearable Device any mobile terminal having the function of displaying and installing an application, such as
  • the receiving terminal sends a data message carrying the state transition data before establishing the air interface signaling connection, and returns a response message to the terminal according to the data message, where the response message carries the data.
  • Sending an indication; when the data message is a random access request message, and the response message is a random access response message, the time frequency indicated by the uplink scheduling indication carried by the receiving terminal in the random access response message The uplink data packet sent by the domain location; or the uplink data packet sent by the receiving terminal on the default physical channel. Since the uplink data packet can be transmitted to the RRC connection state, the number of services can be effectively reduced. According to the delay requirements, the flexibility of network behavior is improved.
  • the present disclosure can solve a large number of mMTC (Massive Machine Type Communication) access networks for bursty small data packet transmission in an Internet of Things (IoT) scenario, because it needs to migrate from the terminal IDLE state to the RRC state zone.
  • IoT Internet of Things
  • the network side device determines before sending the msg4, and then determines to send the content of the msg4 according to the result of the determination; or after the device receives the msg4, first determines whether the terminal supports the terminal. If the data transmission mode of the state transition data is not performed, the data message of the state transition data is sent to the network side device, and then whether the data transmission is performed before the signaling connection is determined according to the result of the feedback of the network side device.
  • the type of the data feature may be set according to actual needs, for example, a judgment condition of whether to support a data transmission mode in which state transition is not performed, or a determination result of the determination condition. This is described in detail below:
  • the foregoing state transition data includes a data transmission identifier
  • the foregoing step 802 further includes:
  • the data transmission indication is directly sent as a transmission.
  • the network side needs to be performed again. The information determines whether data transmission is required.
  • the network side information may include at least one of a network side load status, a terminal subscription data, and operator configuration data.
  • the network side load status includes a load condition of the network side device and/or a load condition of the core network
  • the subscription data of the terminal includes the terminal subscription type and the terminal subscription priority. Level, etc.
  • Carrier configuration data includes whether the carrier configured to support data transmission without state migration.
  • the terminal may obtain the service feature information of the uplink data packet, and the content of the service feature information may be set according to actual needs.
  • the service feature information includes the service type and service. At least one of cache information, business service quality requirements, and business priorities.
  • the service type includes the smart water meter service, the car network service, and the eMBB service;
  • the service cache information is the amount of the user's uplink data cache, for example, the specific cache amount (such as XX bit);
  • the service service quality requirement is the Qos parameter, which may include Packet loss rate, maximum delay, etc.; service priority can be high priority, medium priority, and low priority.
  • the service feature information it is determined according to a predefined rule whether to support the data transmission mode without state transition. For example, when the required delay is low, and the amount of uplink data buffer of the user is low, it can be determined to support the data transmission mode without state transition; when the required delay is high, and the user has the higher data buffer amount. , you can determine that the data transmission method without state migration is not supported.
  • the determination rule of the data transmission method for judging whether or not to support the state transition based on the service feature information is not enumerated here.
  • the terminal determines whether a state transition is required.
  • the data transmission identifier is sent in two ways. When the identifier is used, it is a plaintext transmission mode. For example, a 1-bit identifier may be used. If the identifier is equal to 1 to indicate migration, the identifier is equal to 0 to indicate no migration.
  • a random preamble sequence is used as the data transmission identifier, it is a secret text transmission manner. Specifically, the random preamble sequence includes a first type of random preamble sequence for identifying a migration and a second type of random preamble sequence for identifying a non-migration.
  • the security of data transmission can be improved. For example, when the data transmission mode without state transition is not supported, the first type of random preamble sequence is used for random access; when the data transmission mode without state transition is supported, the second type of random preamble sequence is used for random access.
  • the foregoing state transition data includes service feature information, as shown in FIG.
  • Step 804 Determine, according to the service feature information carried in the random access request message, whether data transmission is required, or according to the service feature information carried in the random access request message. Obtain the network side information to determine whether data transmission is required.
  • the terminal may obtain the service feature information of the uplink data packet.
  • the content of the service feature information may be set according to actual needs.
  • the service feature information includes At least one of a service type, a service cache information, a service quality requirement, and a service priority.
  • the service type includes the smart water meter service, the car network service, and the eMBB service;
  • the service cache information is the amount of the user's uplink data cache, for example, the specific cache amount (such as XX bit);
  • the service service quality requirement is the Qos parameter, which may include Packet loss rate, maximum delay, etc.; service priority can be high priority, medium priority, and low priority.
  • the service cache information is represented by the cache amount (such as N bit) or by the cache level (high, medium, low, or the level number corresponding to the amount of data to be sent (such as 1 to 100 bit number is group 1, and the group number 1 is used)) Express
  • the service quality requirement is expressed by the quality of service parameter (such as low/high delay, small/large data packet), or by the number of the quality of service parameter group (such as QCI serial number), or by the packet loss rate and Maximum allowable delay (ie implicit) representation;
  • the quality of service parameter such as low/high delay, small/large data packet
  • the number of the quality of service parameter group such as QCI serial number
  • the packet loss rate and Maximum allowable delay ie implicit
  • Business priorities are represented by high priority, medium priority, and low priority.
  • the network side device determines whether the state transition is not supported according to the service feature information, and the determination rule for the data transmission mode that supports the state transition is not determined by the terminal.
  • the rules are consistent.
  • the network side information acquired by the network side device may be used for determining.
  • the network side information includes at least a network side load status, a terminal subscription data, and an operator configuration data.
  • the load status of the network side includes the load status of the network side device and/or the load status of the core network.
  • the subscription data of the terminal includes the terminal subscription type and the terminal subscription priority level.
  • the carrier configuration data includes whether the carrier configuration status is not supported.
  • the migrated data is sent.
  • the method further includes:
  • Step 805 When the uplink data packet is successfully received, send a feedback message of successful reception to the terminal, and send the received data packet to the core network.
  • whether the receiving is successful according to the content of the received feedback message when the receiving is successful, if the sending of the uplink data packet is completed, the sending of the uplink data packet may be stopped; if the uplink data packet is not sent, the data packet may be established. Air interface signaling connection.
  • the uplink data packet carries a completion identifier for identifying whether the uplink data packet is sent.
  • the feedback message carries an RRC Connection Reject or RRC Connection Resume Reject for establishing an initial radio resource control protocol; when the received uplink data packet is located in an initial radio resource control protocol message, and the uplink data packet is successfully received If the completion flag is complete, the feedback message carries a reject message (RRC Connection Reject or RRC Connection Resume Reject) for canceling the initial radio resource control protocol; if the completion flag is not completed, the feedback message is carried Establish an allow connection message for the initial RRC protocol.
  • the foregoing completion identifier may be set according to an actual situation, for example, it may be identified whether the uplink data packet is the last data packet. When it is the last packet, it indicates that the transmission has been completed.
  • the uplink data packet sent is relatively small, and can be sent once, it can be directly sent.
  • a certain number of uplink data packets may be preferentially transmitted in a non-RRC connection state, and then the next uplink data packet is sent after the RRC connection is established. Therefore, the transmission of network data packets can be well controlled.
  • the signaling type of the feedback message may be set according to actual needs.
  • the feedback message is the foregoing msg4. That is, in the present embodiment, the uplink packet is placed in msg3 for transmission. It can be understood that the manner in which the uplink data packet is sent in the msg3 for sending may be set according to actual needs.
  • the foregoing step 203 includes: placing the uplink data packet in media access.
  • the control layer (MAC, Media Access Control) data packet or the RRC layer signaling placed in the medium access control layer data packet is sent in the time-frequency domain location indicated by the uplink scheduling indication.
  • the uplink data packet is placed in the initial radio resource control protocol message, and the connection reason for configuring the initial radio resource control protocol message is uplink data packet transmission.
  • the initial RRC connection protocol message may be an RRC Connection Request message, or may be an RRC connection protocol. RRC Connection Resume Request message.
  • the feedback message to the initial RRC message in msg4 may include RRC Connection Reject or RRC Connection Resume Reject, and the rejection reason is “completed data transmission”. ".
  • the feedback message to the initial RRC message in msg4 may include RRC Connection Setup or RRC Connection Resume, and includes allowing the connection to be established. the reason.
  • the feedback message to the initial RRC message in msg4 may include RRC Connection Reject or RRC Connection Resume Reject, and includes the reason for rejection. It is "retransmitted” and carries the reassigned time-frequency domain location (ie, slot resource).
  • Step 806 When the uplink data packet fails to be received, send, to the terminal, a feedback message that fails to receive, and the feedback message carries a re-determined uplink scheduling indication or an allowed connection message used to trigger the terminal to establish a connection.
  • establishing an air interface signaling connection is: establishing a radio resource control protocol connection.
  • the network side device may determine whether to perform data retransmission or state transition according to actual conditions (for example, the load status on the network side).
  • the feedback message may be carried by the re-determined uplink scheduling indication, and then the terminal resends the uplink data packet in the time-frequency domain location indicated by the re-determined uplink scheduling indication carried in the feedback message.
  • the permission connection message that is, the foregoing RRC Connection Setup or RRC Connection Resume, is carried in the feedback message, so that the terminal initiates the process of establishing the RRC.
  • the network side device when the network side device fails to receive the uplink data packet, the network side device can comprehensively consider the state of the network side, and the network side device determines to perform the retransmission or the state transition, thereby improving the flexibility of the network control.
  • the multiple random terminals may select the same random preamble sequence, which may cause interference when the network side device receives the message, and finally form a random access conflict.
  • the increase in the number of 5G terminals will increase the random preamble sequence space, because the possibility of collision of random preambles will not be proportional to the number of 5G terminals.
  • conflicts may still occur, such as encountering conflicts, which are resolved as follows.
  • the terminal does not blindly detect its own RA-RNTI in the PDCCH (Physical Downlink Control Channel) in the process of receiving the msg2, the msg1 preamble transmission fails, and the terminal sends the random preamble again according to the preset mode. ;
  • the terminal If the terminal detects its own RA-RNTI in the PDCCH and receives the RAPID (random preamble sequence) corresponding to itself in the MAC (Medium Access Control Layer) data packet, it indicates that the msg1 preamble is successfully transmitted. .
  • the terminal sends the random access again according to the configured backoff value of the MAC data packet
  • the terminal sends an uplink data packet at the time-frequency domain location indicated in msg2. If multiple terminals use the same random preamble sequence and time-frequency domain location, and the time-frequency domain locations allocated in msg2 used by multiple terminals are the same, a collision occurs.
  • the terminal determines whether the uplink data packet sent by itself is successfully received by receiving msg4, and retransmits if it is not successful.
  • the network side device may consider retransmission or state transition according to the reception condition of the uplink data packet.
  • the receiving terminal before receiving the RRC connection, sends a data message carrying state transition data; and returning a response message to the terminal based on the data message, where the response message carries a state transition indication;
  • the uplink data packet sent by the receiving terminal when the state transition indication is not to be migrated since the uplink data packet can be controlled to be transmitted to the RRC connection state, the delay requirement of the service data can be effectively reduced, thereby improving the flexibility of the network behavior.
  • FIG. 11 is a structural diagram of a terminal provided by an implementation of the present disclosure, which can implement details of the data transmission method in the first embodiment to the second embodiment, and achieve the same effect.
  • the terminal 1100 includes: a data message sending module 1101, a response message receiving module 1102, and a data packet sending module 1103, where
  • the data message sending module 1101 is configured to send a data message carrying the state transition data to the network side device before establishing the air interface signaling connection;
  • the response message receiving module 1102 is configured to receive a response message returned by the network side device to the data message, where the response message carries a data sending indication.
  • a data packet sending module 1103 configured to send to the network when the data sending indication is sent
  • the side device sends an upstream packet.
  • the data packet sending module 1103 is specifically configured to: when the data message is a random access request message, and the response message is a random access response message, carried in the random access response message
  • the uplink data packet is sent by the time-frequency domain location indicated by the uplink scheduling indication; or the uplink data packet is sent to the network side device on the default physical channel.
  • the random access response message carries a selection identifier for indicating a manner of sending the uplink data packet.
  • the terminal further includes:
  • the protocol message sending module 1104 is configured to: when the data sending indication is not to be sent, send an initial radio resource control protocol message in a time-frequency domain location indicated by the uplink scheduling indication.
  • the state transition data includes a data sending identifier, where the data sending identifier includes an identifier carried by the random access request message or a random preamble sequence carried by the random access request message.
  • the random preamble sequence includes a first type of random preamble sequence for identifying a transmission and a second type of random preamble sequence for identifying not to be sent.
  • an identifier for indicating whether a transmission needs to be sent is added to the random preamble sequence.
  • the terminal further includes:
  • the obtaining module 1105 is configured to obtain service characteristic information of the uplink data packet.
  • the first determining module 1106 is configured to determine, according to the service feature information, whether data transmission is required;
  • the state transition data carried by the data message is: determining whether a data transmission result is needed.
  • the state transition data includes service feature information, where the service feature information is used by the network side device to determine, according to the service feature information, whether data transmission is required;
  • the network side device determines, according to the service feature information and the network side information acquired by the network side device, whether data transmission is required.
  • the network side information includes at least one of a network side load status, a terminal subscription data, and operator configuration data.
  • the service feature information includes: a service type, a service cache information, and a service service. At least one of quality requirements and business priorities.
  • the service cache information is represented by a cache amount or by a cache level
  • the service quality requirement is represented by a service quality parameter feature, or a number representation of a service quality parameter feature, or a packet loss rate and a maximum allowable delay.
  • the uplink data packet carries a completion identifier for identifying whether the uplink data packet is sent.
  • the terminal further includes:
  • the feedback message receiving module 1107 is configured to receive a feedback message that the network side device returns according to the uplink data packet receiving status and the completion identifier;
  • the control module 1108 is configured to stop sending the uplink data packet or establish an air interface signaling connection when the feedback message is successfully received, and carry the information in the feedback message when the feedback message is marked as receiving failure
  • the time-frequency domain location indicated by the re-determined uplink scheduling indication re-transmits the uplink data packet, or establishes an air interface signaling connection according to the allowed connection message carried in the feedback message.
  • the feedback message when the uplink data packet is successfully received, if the completion identifier is complete, the feedback message carries a reject message for canceling the initial radio resource control protocol; if the completion identifier is not completed, the feedback message carries An open connection message is established for establishing an initial radio resource control protocol.
  • the data packet sending module 1103 is specifically configured to:
  • the uplink data packet is placed in the RRC layer signaling in the media access control layer data packet, and is sent in a time-frequency domain location indicated by the uplink scheduling indication;
  • the uplink data packet is used as a medium access control layer data packet, and is sent in a time-frequency domain location indicated by the uplink scheduling indication.
  • the data packet sending module 1103 is specifically configured to: place the uplink data packet in an initial RRC message, and configure a connection reason of the initial RRC message to be uplink data packet transmission.
  • the data message carrying the state transition data is sent to the network side device; the response message returned by the network side device to the data message is received, and the response message carries the data sending indication;
  • the data transmission indication is sent, to the network side
  • the device sends an upstream packet. Since the uplink data packet can be controlled to be transmitted to the RRC connection state, the delay requirement of the service data can be effectively reduced, thereby improving the flexibility of the network behavior.
  • FIG. 15 is a structural diagram of a network side device provided by an implementation of the present disclosure, which can implement the details of the data transmission method in the third embodiment to the fourth embodiment, and achieve the same effect.
  • the network side device 1500 includes: a data message receiving module 1501, a response message sending module 1502, and a data packet receiving module 1503, where
  • the data message receiving module 1501 is configured to receive a data message that is sent by the terminal and that carries the state transition data before establishing the air interface signaling connection;
  • the response message sending module 1502 is configured to return, according to the data message, a response message to the terminal, where the response message carries a data sending indication;
  • the data packet receiving module 1503 is configured to receive an uplink data packet that is sent by the terminal when the data sending indication is sent.
  • the data packet receiving module 1503 is specifically configured to:
  • the random access response message carries a selection identifier for indicating a manner of sending the uplink data packet.
  • the network side device further includes:
  • a second determining module 1504 configured to determine, according to the data sending identifier carried in the random access request message, whether data transmission is needed;
  • the data sending identifier includes an identifier carried by the random access request message or a random preamble sequence carried by the random access request message.
  • the random preamble sequence when the data sending identifier includes a random preamble sequence carried by the random access request message, the random preamble sequence includes a first type of random preamble sequence used to identify the sending, and A second type of random preamble sequence that is not sent.
  • the data sending identifier includes a random preamble sequence carried by the random access request message
  • an identifier for indicating whether a transmission needs to be sent is added to the random preamble sequence.
  • the network side device further includes:
  • the third determining module 1505 is configured to determine, according to the service feature information carried in the random access request message, whether data transmission is required, or according to the service feature information carried in the random access request message and the acquired network side information, Determine if you need to send data.
  • the service feature information includes at least one of a service type, a service cache information, a service quality requirement, and a service priority.
  • the service cache information is represented by a cache amount or by a cache level
  • the service quality requirement is represented by a service quality parameter feature, or a number representation of a service quality parameter feature, or a packet loss rate and a maximum allowable delay.
  • the network side information includes at least one of a network side load status, a terminal subscription data, and operator configuration data.
  • the network side device further includes:
  • the processing module 1056 is configured to: when the uplink data packet is successfully received, send a feedback message that is successfully received to the terminal, and send the received data packet to the core network;
  • the feedback message sending module 1507 is configured to: when the uplink data packet fails to be received, send a feedback message of the receiving failure to the terminal, where the feedback message carries a re-determined uplink scheduling indication or is used to trigger the terminal to establish a connection. Allow connection messages.
  • the uplink data packet carries a completion identifier for identifying whether the uplink data packet is sent.
  • the feedback message When the received uplink data packet is located in the initial RRC message and the uplink data packet is successfully received, if the completion identifier is complete, the feedback message carries a reject message for canceling the initial RRC protocol; If not completed, the feedback message carries an allowed connection message for establishing an initial radio resource control protocol.
  • the receiving terminal sends a data message carrying state transition data before establishing the air interface signaling connection; and returning a response message to the terminal according to the data message, where the response message carries a data sending indication Receiving by the receiving terminal when the data transmission indication is sent
  • the upstream packet sent Since the uplink data packet can be controlled to be transmitted to the RRC connection state, the delay requirement of the service data can be effectively reduced, thereby improving the flexibility of the network behavior.
  • the receiving terminal sends a data message carrying the state transition data before establishing the RRC connection, and returns a response message to the terminal to the data message, where the response message carries a state transition indication;
  • the uplink data packet sent by the receiving terminal when the state transition indication is not to be migrated since the uplink data packet can be controlled to be transmitted to the RRC connection state, the delay requirement of the service data can be effectively reduced, thereby improving the flexibility of the network behavior.
  • FIG. 19 is a structural diagram of a mobile terminal to which the embodiment of the present disclosure is applied, which can implement the details of the data transmission method in the first embodiment to the second embodiment, and achieve the same effect.
  • the mobile terminal 1900 includes at least one processor 1901, a memory 1902, at least one network interface 1904, and a user interface 1903.
  • the various components in mobile terminal 1900 are coupled together by a bus system 1905.
  • the bus system 1905 is used to implement connection communication between these components.
  • the bus system 1905 includes a power bus, a control bus, and a status signal bus in addition to the data bus.
  • various buses are labeled as bus system 1905 in FIG.
  • the user interface 1903 may include a display, a keyboard, or a pointing device (eg, a mouse, a track ball, a touch pad, or a touch screen, etc.).
  • a pointing device eg, a mouse, a track ball, a touch pad, or a touch screen, etc.
  • the memory 1902 in the embodiments of the present disclosure may be a volatile memory or a non-volatile memory, or may include both volatile and non-volatile memory.
  • the non-volatile memory may be a read-only memory (ROM), a programmable read only memory (PROM), an erasable programmable read only memory (Erasable PROM, EPROM), or an electric Erase programmable read only memory (EEPROM) or flash memory.
  • the volatile memory can be a Random Access Memory (RAM) that acts as an external cache.
  • RAM Random Access Memory
  • many forms of RAM are available, such as static random access memory (SRAM), dynamic random access memory (DRAM), synchronous dynamic random access memory (Synchronous DRAM).
  • SDRAM Double Data Rate Synchronous Dynamic Random Access Memory
  • DDRSDRAM Double Data Rate Synchronous Dynamic Random Access Memory
  • ESDRAM Enhanced Synchronous Dynamic Random Access Memory
  • SDRAM Synchronous Connection Dynamic Random Access Memory
  • DRRAM direct memory bus random access memory
  • the memory 1902 stores elements, executable modules or data structures, or a subset thereof, or their extended set: an operating system 19021 and an application 19022.
  • the operating system 19021 includes various system programs, such as a framework layer, a core library layer, a driver layer, and the like, for implementing various basic services and processing hardware-based tasks.
  • the application program 19022 includes various applications, such as a media player (Media Player), a browser (Browser), etc., for implementing various application services.
  • a program implementing the method of the embodiments of the present disclosure may be included in the application 19022.
  • the program or the instruction stored in the memory 1902 may be a program or an instruction stored in the application program 19022.
  • the processor 1901 is configured to send the network interface device to the network side device before establishing the air interface signaling connection. a data message carrying the state transition data; receiving a response message returned by the network side device to the data message, the response message carrying the data sending indication; and sending the uplink data to the network side device when the data sending indication is sent package.
  • the method disclosed in the above embodiments of the present disclosure may be applied to the processor 1901 or implemented by the processor 1901.
  • the processor 1901 may be an integrated circuit chip with signal processing capabilities. In the implementation process, each step of the above method may be completed by an integrated logic circuit of hardware in the processor 1901 or an instruction in a form of software.
  • the processor 1901 may be a general-purpose processor, a digital signal processor (DSP), an application specific integrated circuit (ASIC), a field programmable gate array (FPGA), or the like. Programming logic devices, discrete gates or transistor logic devices, discrete hardware components.
  • the methods, steps, and logical block diagrams disclosed in the embodiments of the present disclosure may be implemented or carried out.
  • the general purpose processor may be a microprocessor or the processor or any conventional processor or the like.
  • the steps of the method disclosed in connection with the embodiments of the present disclosure may be directly embodied by the hardware decoding processor.
  • the completion is performed by a combination of hardware and software modules in the decoding processor.
  • the software module can be located in a conventional storage medium such as random access memory, flash memory, read only memory, programmable read only memory or electrically erasable programmable memory, registers, and the like.
  • the storage medium is located in the memory 1902, and the processor 1901 reads the information in the memory 1902 and completes the steps of the above method in combination with its hardware.
  • the embodiments described herein can be implemented in hardware, software, firmware, middleware, microcode, or a combination thereof.
  • the processing unit can be implemented in one or more Application Specific Integrated Circuits (ASICs), Digital Signal Processing (DSP), Digital Signal Processing Equipment (DSP Device, DSPD), programmable Programmable Logic Device (PLD), Field-Programmable Gate Array (FPGA), general purpose processor, controller, microcontroller, microprocessor, other for performing the functions described herein In an electronic unit or a combination thereof.
  • ASICs Application Specific Integrated Circuits
  • DSP Digital Signal Processing
  • DSP Device Digital Signal Processing Equipment
  • PLD programmable Programmable Logic Device
  • FPGA Field-Programmable Gate Array
  • the techniques described herein can be implemented by modules (eg, procedures, functions, and so on) that perform the functions described herein.
  • the software code can be stored in memory and executed by the processor.
  • the memory can be implemented in the processor or external to the processor.
  • the processor 1901 is further configured to: when the data message is a random access request message, and the response message is a random access response message, the uplink scheduling indicator carried in the random access response message Sending an uplink data packet at the indicated time-frequency domain location;
  • the uplink data packet is sent to the network side device on a default physical channel.
  • the random access response message carries a selection identifier for indicating a manner of sending the uplink data packet.
  • the processor 1901 is further configured to: when the data sending indication is not to be sent, send an initial radio resource control protocol message in a time-frequency domain location indicated by the uplink scheduling indication.
  • the state transition data includes a data sending identifier, where the data sending identifier includes an identifier carried by the random access request message or a random preamble sequence carried by the random access request message.
  • the random preamble sequence includes a first type of random preamble sequence for identifying a transmission and a second type of random preamble sequence for identifying not to be sent.
  • an identifier for indicating whether a transmission needs to be sent is added to the random preamble sequence.
  • the processor 1901 is further configured to: obtain service characteristic information of the uplink data packet;
  • the state transition data carried by the data message is: determining whether a data transmission result is needed.
  • the state transition data includes service feature information, where the service feature information is used by the network side device to determine, according to the service feature information, whether data transmission is required;
  • the network side device determines, according to the service feature information and the network side information acquired by the network side device, whether data transmission is required.
  • the network side information includes at least one of a network side load status, a terminal subscription data, and operator configuration data.
  • the service feature information includes at least one of a service type, a service cache information, a service quality requirement, and a service priority.
  • the service cache information is represented by a cache amount or by a cache level
  • the service quality requirement is represented by a service quality parameter feature, or a number representation of a service quality parameter feature, or a packet loss rate and a maximum allowable delay.
  • the uplink data packet carries a completion identifier for identifying whether the uplink data packet is sent.
  • the processor 1901 is further configured to: receive, by the network side device, a feedback message according to the uplink data packet receiving state and the completion identifier reply. ;
  • the uplink data packet is retransmitted in the time-frequency domain location indicated by the re-determined uplink scheduling indication carried in the feedback message, or the air interface is established according to the allowed connection message carried in the feedback message. Signaling connection.
  • the feedback message when the uplink data packet is successfully received, if the completion identifier is complete, the feedback message carries a reject message for canceling the initial radio resource control protocol; if the completion identifier is not completed, the feedback message carries An open connection message is established for establishing an initial radio resource control protocol.
  • the processor 1901 is further configured to: place the uplink data packet in a media access control layer data packet, and send the information in a time-frequency domain location indicated by the uplink scheduling indication;
  • the uplink data packet is placed in the RRC layer signaling in the media access control layer data packet, and is sent in a time-frequency domain location indicated by the uplink scheduling indication;
  • the uplink data packet is used as a medium access control layer data packet, and is sent in a time-frequency domain location indicated by the uplink scheduling indication.
  • the placing the uplink data packet in the RRC layer signaling in the medium access control layer data packet includes: placing the uplink data packet in an initial RRC message, and The reason for configuring the connection of the initial RRC message is uplink packet transmission.
  • the data message carrying the state transition data is sent to the network side device; the response message returned by the network side device to the data message is received, and the response message carries the data sending indication;
  • the uplink data packet is sent to the network side device. Since the uplink data packet can be controlled to be transmitted to the RRC connection state, the delay requirement of the service data can be effectively reduced, thereby improving the flexibility of the network behavior.
  • FIG. 20 is a structural diagram of a mobile terminal according to an embodiment of the present disclosure, which can implement details of the data transmission method in the first embodiment to the second embodiment, and achieve the same effect.
  • the mobile terminal 2000 includes a radio frequency (RF) circuit 2010, a memory 2020, an input unit 2030, a display unit 2040, a processor 2050, an audio circuit 2060, a communication module 2070, and a power source 2080.
  • RF radio frequency
  • the input unit 2030 can be configured to receive numeric or character information input by the user, and generate signal input related to user settings and function control of the mobile terminal 2000.
  • the input unit 2030 may include a touch panel 2031.
  • the touch panel 2031 also referred to as a touch screen, can collect touch operations on or near the user (such as the operation of the user using any suitable object or accessory such as a finger or a stylus on the touch panel 2031), and according to the preset The programmed program drives the corresponding connection device.
  • the touch panel 2031 may include two parts: a touch detection device and a touch controller.
  • the touch detection device detects the touch orientation of the user, and detects a 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 the touch information into contact coordinates, and sends the touch information.
  • the processor 2050 is provided and can receive commands from the processor 2050 and execute them.
  • the touch panel 2031 can be implemented in various types such as resistive, capacitive, infrared, and surface acoustic waves.
  • the input unit 2030 Other input devices 2032 may also be included.
  • Other input devices 2032 may include, but are not limited to, one or more of a physical keyboard, function keys (such as volume control buttons, switch buttons, etc.), trackballs, mice, joysticks, and the like.
  • the display unit 2040 can be used to display information input by the user or information provided to the user and various menu interfaces of the mobile terminal 2000.
  • the display unit 2040 can include a display panel 2041.
  • the display panel 2041 can be configured in the form of an LCD or an Organic Light-Emitting Diode (OLED).
  • the touch panel 2031 may cover the display panel 2041 to form a touch display screen, and when the touch display screen detects a touch operation on or near it, it is transmitted to the processor 2050 to determine the type of the touch event, and then the processor The 2050 provides a corresponding visual output on the touch display depending on the type of touch event.
  • the touch display includes an application interface display area and a common control display area.
  • the arrangement manner of the application interface display area and the display area of the common control is not limited, and the arrangement manner of the two display areas can be distinguished by up-and-down arrangement, left-right arrangement, and the like.
  • the application interface display area can be used to display the interface of the application. Each interface can contain interface elements such as at least one application's icon and/or widget desktop control.
  • the application interface display area can also be an empty interface that does not contain any content.
  • the common control display area is used to display controls with high usage, such as setting buttons, interface numbers, scroll bars, phone book icons, and the like.
  • the processor 2050 is a control center of the mobile terminal 2000, and connects various parts of the entire mobile phone by using various interfaces and lines, by running or executing software programs and/or modules stored in the first memory 2021, and calling the second storage.
  • the data in the memory 2022 performs various functions and processing data of the mobile terminal 2000, thereby performing overall monitoring of the mobile terminal 2000.
  • the processor 2050 can include one or more processing units.
  • the processor 2050 is configured to: establish an air interface signaling connection to the network
  • the side device sends a data message carrying the state transition data, and receives a response message returned by the network side device to the data message, where the response message carries a data sending indication; when the data sending indication is sent, the network side device is sent to the network side device. Send an upstream packet.
  • the processor 2050 is further configured to: when the data message is a random access request message, and When the response message is a random access response message, the uplink data packet is sent in a time-frequency domain location indicated by the uplink scheduling indication carried in the random access response message;
  • the uplink data packet is sent to the network side device on a default physical channel.
  • the random access response message carries a selection identifier for indicating a manner of sending the uplink data packet.
  • the processor 2050 is further configured to: when the data sending indication is not sent, send an initial radio resource control protocol message in a time-frequency domain location indicated by the uplink scheduling indication.
  • the state transition data includes a data sending identifier, where the data sending identifier includes an identifier carried by the random access request message or a random preamble sequence carried by the random access request message.
  • the random preamble sequence includes a first type of random preamble sequence for identifying a transmission and a second type of random preamble sequence for identifying not to be sent.
  • an identifier for indicating whether a transmission needs to be sent is added to the random preamble sequence.
  • the processor 2050 is further configured to: obtain service characteristic information of the uplink data packet;
  • the state transition data carried by the data message is: determining whether a data transmission result is needed.
  • the state transition data includes service feature information, where the service feature information is used by the network side device to determine, according to the service feature information, whether data transmission is required;
  • the network side device determines, according to the service feature information and the network side information acquired by the network side device, whether data transmission is required.
  • the network side information includes at least one of a network side load status, a terminal subscription data, and operator configuration data.
  • the service feature information includes at least one of a service type, a service cache information, a service quality requirement, and a service priority.
  • the service cache information is represented by a cache amount or by a cache level
  • the service quality requirement is represented by a service quality parameter feature, or a number representation of a service quality parameter feature, or a packet loss rate and a maximum allowable delay.
  • the uplink data packet carries identifiers for identifying whether the uplink data packet is sent.
  • the processor 2050 is further configured to: receive a feedback message that the network side device returns according to the uplink data packet receiving status and the completion identifier;
  • the uplink data packet is retransmitted in the time-frequency domain location indicated by the re-determined uplink scheduling indication carried in the feedback message, or the air interface is established according to the allowed connection message carried in the feedback message. Signaling connection.
  • the feedback message when the uplink data packet is successfully received, if the completion identifier is complete, the feedback message carries a reject message for canceling the initial radio resource control protocol; if the completion identifier is not completed, the feedback message carries An open connection message is established for establishing an initial radio resource control protocol.
  • the processor 2050 is further configured to: place the uplink data packet in a medium access control layer data packet, and send the information in a time-frequency domain location indicated by the uplink scheduling indication;
  • the uplink data packet is placed in the RRC layer signaling in the media access control layer data packet, and is sent in a time-frequency domain location indicated by the uplink scheduling indication;
  • the uplink data packet is used as a medium access control layer data packet, and is sent in a time-frequency domain location indicated by the uplink scheduling indication.
  • the placing the uplink data packet in the RRC layer signaling in the medium access control layer data packet includes: placing the uplink data packet in an initial RRC message, and The reason for configuring the connection of the initial RRC message is uplink packet transmission.
  • the data message carrying the state transition data is sent to the network side device; the response message returned by the network side device to the data message is received, and the response message carries the data sending indication;
  • the uplink data packet is sent to the network side device. Since the uplink data packet can be controlled to be transmitted to the RRC connection state, the delay requirement of the service data can be effectively reduced, thereby improving the flexibility of the network behavior.
  • the disclosed apparatus and method may be implemented in other manners.
  • the device embodiments described above are merely illustrative.
  • the division of the unit is only a logical function division.
  • there may be another division manner for example, multiple units or components may be combined or Can be integrated into another system, or some features can be ignored or not executed.
  • the mutual coupling or direct coupling or communication connection shown or discussed may be an indirect coupling or communication connection through some interface, device or unit, and may be in an electrical, mechanical or other form.
  • the units described as separate components may or may not be physically separated, and the components displayed as units may or may not be physical units, that is, may be located in one place, or may be distributed to multiple network units. Some or all of the units may be selected according to actual needs to achieve the objectives of the embodiments of the present disclosure.
  • each functional unit in various embodiments of the present disclosure may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit.
  • the functions may be stored in a computer readable storage medium if implemented in the form of a software functional unit and sold or used as a standalone product. Based on such understanding, the portion of the technical solution of the present disclosure that contributes in essence or to the prior art or the portion of the technical solution may be embodied in the form of a software product stored in a storage medium, including The instructions are used to cause a computer device (which may be a personal computer, server, or network device, etc.) to perform all or part of the steps of the methods described in various embodiments of the present disclosure.
  • the foregoing storage medium includes various media that can store program codes, such as a USB flash drive, a mobile hard disk, a ROM, a RAM, a magnetic disk, or an optical disk.
  • an embodiment of the present disclosure further provides a network side device, including: a memory, a processor, and a computer program stored on the memory and operable on the processor, the processor The steps of the data transfer method of Figures 7 through 10 are implemented when the computer program is executed.
  • uplink scheduling indication may be one or more, and is not further limited herein.

Landscapes

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

Abstract

本公开提供一种数据传输方法、终端及网络侧设备，数据传输方法包括：建立空口信令连接前，向网络侧设备发送携带有状态迁移数据的数据消息；接收网络侧设备对数据消息返回的应答消息，所述应答消息携带有数据发送指示；当所述数据发送指示为发送时，向所述网络侧设备发送上行数据包。

Description

一种数据传输方法、终端及网络侧设备
相关申请的交叉引用
本申请主张在2016年11月4日在中国提交的中国专利申请号No.201610964285.X的优先权，其全部内容通过引用包含于此。
技术领域
本公开涉及通信技术领域，尤其涉及一种数据传输方法、终端及网络侧设备。
背景技术
随着无线技术的不断发展，5G技术已经成为下一代移动通信技术的发展方向。根据目前ITU对5G的需求定义，在未来的5G时代，连接密度将达到1百万/Km2，端到端最低时延达到1ms。这对移动通信标准化提出了极高要求。与此同时，未来5G还会对各垂直行业进行支持，新的技术将孵化出众多的新型业务形态。在3GPP的需求定义中，已经确定三大应用场景：
eMBB(增强的移动宽频通信，Enhanced mobile broadband)；
mMTC(大规模物联网，Massive machine-type-communications)；
uRLLC(低时延和超高可靠性通信，Ultra reliable and low latency communications)；
其中，mMTC场景主要针对物联网场景的优化，比如智能水表，智能电表，可穿戴设备等。该场景的一个主要特征是：大量的终端数目及连接数，相对小的数据要发送需求和数据并发。另一方面，uRLLC场景，也是5G的重要场景如车联网场景、VR/AR应用、远程医疗等场景。在该场景中，端到端具备极低的用户面和信令面时延。
然而，传统的系统中，对于终端接入网络发送上行数据包通常的做法是：首先由终端发起随机接入请求消息，然后由网络侧设备对随机接入请求消息进行应答，返回随机接入应答消息，接着根据随机接入应答消息配置的数据发送参数发送初始RRC消息，最后根据网络侧设备对初始RRC消息发起建 立RRC连接的流程，在RRC连接后，将上行数据包发送至核心网。由于网络控制的灵活性较差，每次发送上行数据包均需要建立RRC连接，因此不适用于低时延需求的场景。
发明内容
本公开实施例提供一种数据传输方法、终端及网络侧设备，以解决每次发送上行数据时，均进行状态迁移的问题。
第一方面，本公开实施例提供了一种数据传输方法，包括：
建立空口信令连接前，向网络侧设备发送携带有状态迁移数据的数据消息；
接收网络侧设备对数据消息返回的应答消息，所述应答消息携带有数据发送指示；
当所述数据发送指示为发送时，向所述网络侧设备发送上行数据包。
第二方面，本公开实施例还提供了一种数据传输方法，包括：
接收终端在建立空口信令连接前所发送的携带有状态迁移数据的数据消息；
基于所述数据消息，向所述终端返回应答消息，所述应答消息携带有数据发送指示；
接收终端在所述数据发送指示为发送时所发送的上行数据包。
第三方面，本公开实施例还提供了一种终端，该终端包括：
数据消息发送模块，用于建立空口信令连接前，向网络侧设备发送携带有状态迁移数据的数据消息；
应答消息接收模块，用于接收网络侧设备对数据消息返回的应答消息，所述应答消息携带有数据发送指示；
数据包发送模块，用于当所述数据发送指示为发送时，向所述网络侧设备发送上行数据包。
第四方面，本公开实施例还提供了一种网络侧设备，该网络侧设备包括：
数据消息接收模块，用于接收终端在建立空口信令连接前所发送的携带有状态迁移数据的数据消息；
应答消息发送模块，用于基于所述数据消息，向所述终端返回应答消息，所述应答消息携带有数据发送指示；
数据包接收模块，用于接收终端在所述数据发送指示为发送时所发送的上行数据包。
第五方面，本公开实施例还提供了一种移动终端，包括：存储器、处理器及存储在所述存储器上并可在所述处理器上运行的计算机程序，所述处理器执行所述计算机程序时实现第一方面中数据传输方法的步骤。
第六方面，本公开实施例还提供了一种网络侧设备，包括：存储器、处理器及存储在所述存储器上并可在所述处理器上运行的计算机程序，所述处理器执行所述计算机程序时实现第二方面中数据传输方法的步骤。
这样，本公开实施例中，建立空口信令连接前，向网络侧设备发送携带有状态迁移数据的数据消息；接收网络侧设备对数据消息返回的应答消息，所述应答消息携带有数据发送指示；当所述数据发送指示为发送时，向所述网络侧设备发送上行数据包。由于可以对上行数据包是否迁移到RRC连接状态下进行发送进行了控制，从而可以有效降低业务数据的时延需求，因此提高了网络行为的灵活性。
附图说明
为了更清楚地说明本公开实施例的技术方案，下面将对本公开实施例描述中所需要使用的附图作简单地介绍，显而易见地，下面描述中的附图仅仅是本公开的一些实施例，对于本领域普通技术人员来讲，在不付出创造性劳动性的前提下，还可以根据这些附图获得其他的附图。
图1是本公开第一实施例提供的数据传输方法的流程图；
图2是本公开第二实施例提供的数据传输方法的流程图之一；
图3是本公开第二实施例提供的数据传输方法的流程图之二；
图4是本公开第二实施例提供的数据传输方法的流程图之三；
图5是本公开第二实施例提供的数据传输方法的流程图之三；
图6是本公开第二实施例提供的数据传输方法的流程图之四；
图7是本公开第三实施例提供的数据传输方法的流程图；
图8是本公开第四实施例提供的数据传输方法的流程图之一；
图9是本公开第四实施例提供的数据传输方法的流程图之二；
图10是本公开第四实施例提供的数据传输方法的流程图之三；
图11是本公开第五实施例提供的终端的结构之一；
图12是本公开第五实施例提供的终端的结构之二；
图13是本公开第五实施例提供的终端的结构之三；
图14是本公开第五实施例提供的终端的结构之四；
图15是本公开第六实施例提供的网络侧设备的结构之一；
图16是本公开第六实施例提供的网络侧设备的结构之二；
图17是本公开第六实施例提供的网络侧设备的结构之三；
图18是本公开第六实施例提供的网络侧设备的结构之四；
图19为本公开第七实施例应用的移动终端的结构图；
图20为本公开第八实施例应用的移动终端的结构图。
具体实施方式
下面将结合本公开实施例中的附图，对本公开实施例中的技术方案进行清楚、完整地描述，显然，所描述的实施例是本公开一部分实施例，而不是全部的实施例。基于本公开中的实施例，本领域普通技术人员在没有作出创造性劳动前提下所获得的所有其他实施例，都属于本公开保护的范围。
第一实施例
参见图1，图1是本公开实施例提供的数据传输方法的流程图，如图1所示，包括以下步骤：
步骤101、建立空口信令连接前，向网络侧设备发送携带有状态迁移数据的数据消息。
本公开实施例中，上述空口信令为端与端之间的数据传输信令协议，例如现有的空口信令包括无线资源控制协议信令。其中无线资源控制协议为RRC(Radio Resource Control)，状态迁移数据为用于反应是否支持不进行状态迁移的数据发送方式的数据特征。其中状态迁移是指RRC的连接状态变化，具体地，是指从未建立RRC连接到建议RRC连接。上述数据特征的类型可 以根据实际需要进行设置，例如可以为是否支持不进行状态迁移的数据发送方式的判断条件，也可以是对该判断条件的判断结果，以下实施例中对此进行详细说明。上述网络侧设备是指基站。
例如，当移动终端长期未产生业务数据时，移动终端将自动与核心网断开RRC连接，当再次需要发送上行业务数据(上行数据包)时，则可能需要建立RRC连接，以向核心网发送数据包。具体地，该业务数据的类型可以为任意类型，如智能水表业务、车联网业务和eMBB(增强的移动宽频通信，Enhanced mobile broadband)业务等。
步骤102、接收网络侧设备对数据消息返回的应答消息，所述应答消息携带有数据发送指示。
该步骤中，上述数据发送指示包括发送和不发送两种状态。当网络侧设备接收到上述数据消息后，将会对该数据消息进行应答，在应答消息中将会携带该数据发送指示。具体的，应答的方式与数据消息的内容相匹配。由于上述数据消息中的状态迁移数据可以为多种形式，对应的应答方式可以对应设置为多种应答方式。例如，当状态迁移数据为是否支持不进行状态迁移的数据发送方式的判断条件，网络侧设备将会根据该判断条件确定终端是否支持不进行状态迁移的数据发送方式，从而下发数据发送指示；当状态迁移数据为对该判断条件的判断结果时，可以根据判断结果直接下发数据发送指示，也可以按照网络侧设备获取的网络侧信息判断是否允许终端在不进行状态迁移的情况下进行数据发送，从而下发数据发送指示。
步骤103、当所述数据发送指示为发送时，向所述网络侧设备发送上行数据包。
该步骤中，当终端接收到网络侧设备的应答消息后，将会根据该应答消息中的数据发送指示执行相应的操作。具体地，当数据发送指示为发送时，则可以向网络侧设备发送上行数据包，当网络侧设备接收到该上行数据包后，将会把该上行数据包发送到核心网，从而完成上行数据包的发送。
可以理解的是，对于不同的业务数据是否支持不进行状态迁移的数据发送方式的判断规则可以根据实际需要进行设置，在此不做进一步的限定。
本公开实施例中，上述终端可以任何具备显示和安装应用程序功能的移 动终端，例如：手机、平板电脑(Tablet Personal Computer)、膝上型电脑(Laptop Computer)、个人数字助理(personal digital assistant，简称PDA)、移动上网装置(Mobile Internet Device，MID)或可穿戴式设备(Wearable Device)等。
这样，本公开实施例中，建立空口信令连接前，向网络侧设备发送携带有状态迁移数据的数据消息；接收网络侧设备对数据消息返回的应答消息，所述应答消息携带有数据发送指示；当所述数据发送指示为发送时，向所述网络侧设备发送上行数据包。由于可以对上行数据包是否迁移到RRC连接状态下进行发送进行了控制，从而可以有效降低业务数据的时延需求，因此提高了网络行为的灵活性。
本公开可以在物联网(IoT)场景下，解决大量mMTC(Massive Machine Type Communication，大规模物联网)接入网络进行突发的小数据包发送时，由于需要从终端IDLE状态迁移到RRC状态带来的信令负载问题。
第二实施例
参见图2，图2是本公开实施例提供的数据传输方法的流程图，如图2所示，包括以下步骤：
步骤201、建立空口信令连接前，向网络侧设备发送携带有状态迁移数据的数据消息。
本公开实施例中，上述空口信令为端与端之间的数据传输信令协议，例如现有的空口信令包括无线资源控制协议信令。其中无线资源控制协议为RRC(Radio Resource Control)，状态迁移数据为用于反应是否支持不进行状态迁移的数据发送方式的数据特征。其中状态迁移是指RRC的连接状态变化，具体地，是指从未建立RRC连接到建议RRC连接。上述数据特征的类型可以根据实际需要进行设置，例如可以为是否支持不进行状态迁移的数据发送方式的判断条件，也可以是对该判断条件的判断结果，以下实施例中对此进行详细说明。上述网络侧设备是指基站。
在本实施例中，上述数据消息为随机接入请求消息。即在随机接入流程中，确定是否建立无线资源控制协议连接发送上行数据包。具体地，在随机接入流程中包括msg1至msg4，其中msg1为随机接入请求消息，msg2为对随机接入请求消息应答的随机接入应答消息，msg3是初始RRC消息，msg4 为初始RRC消息的回复消息。本实施例中，具体在终端发送的msg1中携带状态迁移数据。
例如，当移动终端长期未产生业务数据时，移动终端将自动与核心网断开RRC连接，当再次需要发送上行业务数据(上行数据包)时，则可能需要建立RRC连接，以向核心网发送数据包。具体地，该业务数据的类型可以为任意类型，如智能水表业务、车联网业务和eMBB(增强的移动宽频通信，Enhanced mobile broadband)业务等。
步骤202、接收网络侧设备对数据消息返回的应答消息，所述应答消息携带有数据发送指示。
该步骤中，上述数据发送指示包括发送和不发送两种状态。当网络侧设备接收到上述数据消息后，将会对该数据消息进行应答，在应答消息中将会携带该数据发送指示。具体的，应答的方式与数据消息的内容相匹配。由于上述数据消息中的状态迁移数据可以为多种形式，对应的应答方式可以对应设置为多种应答方式。例如，当状态迁移数据为是否支持不进行状态迁移的数据发送方式的判断条件，网络侧设备将会根据该判断条件确定终端是否支持不进行状态迁移的数据发送方式，从而下发数据发送指示；当状态迁移数据为对该判断条件的判断结果时，可以根据判断结果直接下发数据发送指示，也可以按照网络侧设备获取的网络侧信息判断是否允许终端在不进行状态迁移的情况下进行数据发送，从而下发数据发送指示。例如当网络侧设备不支持不进行状态迁移的数据发送，则可以直接将数据发送指示设置为不发送。
应当说明的是，在上述随机接入应答消息中还携带有用作上行同步的上行定时TA、用作临时标识UE的临时标识符C-RNTI、用作上行功率控制信令P、以及用作msg3调度的上行调度指示(UL grant)；根据随机接入应答消息中各参数的参数值可以控制发送上行数据包的时间。
步骤203、在所述数据消息为随机接入请求消息，且所述应答消息为随机接入应答消息的情况下，当所述数据发送指示为发送时，在所述随机接入应答消息携带的上行调度指示所指示的时频域位置发送上行数据包，或者在默认的物理信道上向所述网络侧设备发送上行数据包。
该步骤中，当终端接收到网络侧设备的应答消息后，将会根据该应答消 息中的数据发送指示执行相应的操作。具体地，当数据发送指示为发送时，则可以向网络侧设备发送上行数据包，当网络侧设备接收到该上行数据包后，将会把该上行数据包发送到核心网，从而完成上行数据包的发送。
可以理解的是，对于不同的业务数据是否支持不进行状态迁移的数据发送方式的判断规则可以根据实际需要进行设置，在此不做进一步的限定。
可以理解的是，上行数据包发送的方式可以根据实际需要进行设置，例如可以在默认的物理信道上进行发送，也可以在上行调度指示所指示的时频域位置发送。其中默认的物理信道是指终端知晓的物理信道(预先配置的物理信道)。具体的，对于采用哪种方式发送上行数据包可以根据实际需要进行设定，例如可以设置上述随机接入应答消息携带有用于指示所述上行数据包发送方式的选择标识；此外，还可以当应答消息中未包含上行调度指示时，默认使用默认的物理信道进行发送上行数据包。
本公开实施例中，上述移动终端可以为任何具备显示和安装应用程序功能的移动终端，例如：手机、平板电脑(Tablet Personal Computer)、膝上型电脑(Laptop Computer)、个人数字助理(personal digital assistant，简称PDA)、移动上网装置(Mobile Internet Device，MID)或可穿戴式设备(Wearable Device)等。
这样，本公开实施例中，建立空口信令连接前，向网络侧设备发送携带有状态迁移数据的数据消息；接收网络侧设备对数据消息返回的应答消息，所述应答消息携带有数据发送指示；在所述数据消息为随机接入请求消息，且所述应答消息为随机接入应答消息的情况下，当所述数据发送指示为发送时，在所述随机接入应答消息携带的上行调度指示所指示的时频域位置发送上行数据包，或者在默认的物理信道上向所述网络侧设备发送上行数据包。由于可以对上行数据包是否迁移到RRC连接状态下进行发送进行了控制，从而可以有效降低业务数据的时延需求，因此提高了网络行为的灵活性。
本公开可以在物联网(IoT)场景下，解决大量mMTC(Massive Machine Type Communication，大规模物联网)接入网络进行突发的小数据包发送时，由于需要从终端IDLE状态迁移到RRC状态带来的信令负载问题。
应当说明的是，本实施例中，在随机接入过程中加入，终端是否支持不 进行状态迁移的数据发送方式的状态判断，因此可以不需要额外增加信令，从而无需增加网络侧设备的负载。进一步地，还可以不对现有的随机接入过程进行改变，网络侧设备发送msg4前进行判断，然后根据判断的结果确定发送msg4的内容；或者由设备在接收到msg4后，首先判断终端是否支持不进行状态迁移的数据发送方式，若是，则发送上述状态迁移数据的数据消息到网络侧设备，然后根据网络侧设备反馈的结果确定在信令连接前是否进行数据发送。
进一步地，参照图3，基于上述实施例，上述步骤202之后还包括：
步骤204、当所述数据发送指示为不发送时，在所述上行调度指示所指示的时频域位置发送初始无线资源控制协议消息。
该步骤中，由于上述数据发送指示包括不发送和发送两种方案，当数据发送指示为不发送时，则需要建立RRC连接，此时可以进入RRC连接流程。具体的，在上述上行调度指示所指示的时频域位置发送初始无线资源控制协议消息，也就是说发送msg3，然后由网络侧设备决定是否允许该终端建立RRC连接，并通过msg4返回对msg3的回复，以告诉终端是否允许建立RRC连接，如果允许，则可以建立RRC连接，并在建立连接后发送上述上行数据包。
进一步地，上述数据特征的类型可以根据实际需要进行设置，例如可以为是否支持不进行状态迁移的数据发送方式的判断条件，也可以是对该判断条件的判断结果。以下对此进行详细说明：
在一种方案中，由终端判断是否支持不进行状态迁移的数据发送。例如上述状态迁移数据包括数据发送标识，所述数据发送标识包括所述随机接入请求消息携带的标识符或者所述随机接入请求消息携带的随机前导序列。
该方案中，由终端判断是否支持不进行状态迁移的数据发送方式送。其中，上述数据发送标识的发送的方式为两种，当采用标识符时，为明文发送方式，例如可以采用1bit的标识符，设置标识符等于1表示迁移，设置标识符等于0标识不迁移。当采用随机前导序列作为数据发送标识时，为暗文发送方式，具体的，所述随机前导序列包括用于标识迁移的第一类随机前导序列和用于标识不迁移的第二类随机前导序列；或者所述随机前导序列中添加 用于表示数据发送的标识位(即将标识符叠加在随机前导序列上)。本实施例中，由于采用暗文的方式发送数据发送标识，从而可以提高数据传输的安全性。例如当不支持不进行状态迁移的数据发送方式时，采用第一类随机前导序列进行随机接入；支持不进行状态迁移的数据发送方式时，采用第二类随机前导序列进行随机接入。
进一步地，参照图4，在上述步骤201之前还包括：
步骤205、获取所述上行数据包的业务特征信息；
该步骤中，在终端进行发送上行数据包前，终端可以获取上行数据包的业务特征信息，具体地，该业务特征信息的内容可以根据实际需要进行设置，本实施例中，该业务特征信息包括业务类型、业务缓存信息、业务服务质量要求和业务优先级中的至少一项。其中，业务类型包括智能水表业务、车联网业务和eMBB业务等；业务缓存信息为用户上行数据缓存量，例如可以为具体的缓存量(如XX bit)；业务服务质量要求为Qos参数，可以包括丢包率、最大时延等；业务优先级可以为高优先级、中优先级和低优先级。
步骤206、根据所述业务特征信息，确定是否需要进行数据发送。
该步骤中，上述数据消息携带的状态迁移数据为：确定是否需要进行数据发送的结果。在获取到业务特征信息后，根据业务特征信息，按照预先定义的规则确定是否支持不进行状态迁移的数据发送方式。例如，当需要的时延较低，且用户上行数据缓存量较低时，可以确定为支持不进行状态迁移的数据；当需要的时延较高，且用户上述数据缓存量较高时，可以确定为不支持不进行状态迁移的数据。对于根据业务特征信息判断是否支持不进行状态迁移的数据发送方式的判断规则在此不进行一一列举。
应当说明的是，在终端根据业务特征信息判定支持不进行状态迁移时，还可以根据网络侧设备获取的网络侧信息确定是否支持不进行状态迁移的数据发送方式，以优化网络状态。其中网络侧信息可以包括网络侧负载状态、终端的签约数据和运营商配置数据中的至少一项。具体的，网络侧负载状态包括网络侧设备的负载情况和/或核心网的负载情况；终端的签约数据包括终端签约类型和终端签约优先等级等；运营商配置数据包括运营商配置的是否支持状态不迁移的数据发送。
在另一方案中，参照图5、上述状态迁移数据包括业务特征信息，其中，所述业务特征信息用于所述网络侧设备根据所述业务特征信息确定是否需要进行数据发送；或者所述网络侧设备根据所述业务特征信息和网络侧设备获取的网络侧信息确定是否需要进行数据发送。
该方案中，在终端进行发送上行数据包前，终端可以获取上行数据包的业务特征信息，具体地，该业务特征信息的内容可以根据实际需要进行设置，本实施例中，该业务特征信息包括业务类型、业务缓存信息、业务服务质量要求和业务优先级中的至少一项。其中，业务类型包括智能水表业务、车联网业务和eMBB业务等；业务缓存信息为用户上行数据缓存量，例如可以为具体的缓存量(如XX bit)；业务服务质量要求为Qos参数，可以包括丢包率、最大时延等；业务优先级可以为高优先级、中优先级和低优先级。
应当说明的是，对于终端业务特征信息中各参数的表示方式可以采用以下形式进行表示：
业务类型，可以直接给出业务类型表示；
业务缓存信息采用缓存量(如N bit)表示或者采用缓存等级(高、中、低或者待发数据量对应的级别编号(如1～100bit编号为组1，此时采用编组号1表示))表示；
业务服务质量要求采用服务质量参数特征(如低/高时延、小/大数据包)表示，或者采用对服务质量参数特征进行编组的编号(如QCI序列号)表示，或者采用丢包率及最大允许时延(即隐式)表示；
业务优先级采用高优先级、中优先级和低优先级进行表示。
在将上述业务特征信息发送至网络侧设备后，由网络侧设备根据业务特征信息进行判断是否支持不进行状态迁移的数据发送方式，对于是否支持不进行状态迁移的数据发送方式的判断规则可以与终端进行判断的规则一致。在本实施例中，为了优化网络环境，还可以结合网络侧设备获取的网络侧信息进行判断，具体地，该网络侧信息包括网络侧负载状态、终端的签约数据和运营商配置数据中的至少一项。其中，网络侧负载状态包括网络侧设备的负载情况和/或核心网的负载情况；终端的签约数据包括终端签约类型和终端签约优先等级等；运营商配置数据包括运营商配置的是否支持不进行状态迁 移的数据发送方式。
进一步地，参照图6，所述上行数据包中携带有用于标识上行数据包是否发送完成的完成标识，在上述步骤203之后还包括：
步骤207、接收网络侧设备根据所述上行数据包接收状态和完成标识回复的反馈消息。
该步骤中，上述反馈消息的信令类型可以根据实际需要进行设置，本实施例中，可选的，该反馈消息为上述msg4。即在本实施例中，上述上行数据包放置在msg3中进行发送。可以理解的是，将上行数据包放置在msg3中进行发送的方式可以根据实际需要进行设置，可选的，在本实施例中，上述步骤203包括：将所述上行数据包放置在媒体接入控制层(MAC，Media Access Control)数据包中或者放置在媒体接入控制层数据包内的无线资源控制协议层信令中，在所述上行调度指示所指示的时频域位置发送。例如，将上行数据包放置在初始无线资源控制协议消息中，且配置所述初始无线资源控制协议消息的连接原因为上行数据包发送。其中，初始无线资源控制协议消息可以为RRC连接请求(RRC Connection Request)消息，也可以为RRC恢复连接请求(RRC Connection Resume Request)消息。
若接收上行数据包成功，则在msg4中对初始无线资源控制协议消息的反馈消息中可以包含RRC Connection Reject(拒绝)或RRC Connection Resume Reject(恢复拒绝)，并包含拒绝原因为“已完成数据发送”。
若接收上行数据包失败、且决定进行状态迁移，则在msg4中对初始无线资源控制协议消息的反馈消息中可以包含RRC Connection Setup(允许)或RRC Connection Resume(恢复允许)，并包含允许建立连接原因。
若接收上行数据包失败、且决定进行重传，则在msg4中对初始无线资源控制协议消息的反馈消息中可以包含RRC Connection Reject(拒绝)或RRC Connection Resume Reject(恢复拒绝)，并包含拒绝原因为“重传”，并携带重新分配的时频域位置(即时隙资源)。
步骤208、当所述反馈消息标识为接收成功时，则停止发送所述上行数据包或者建立空口信令连接。
该步骤中，可以根据接收到的反馈消息内容确定是否接收成功，当接收 成功时，若上行数据包发送完成，则可以停止上行数据包的发送；若上行数据包未发送完成，且可以建立空口信令连接。
具体的，在本实施例中，上述网络侧设备根据所述上行数据包接收状态和完成标识回复的反馈消息包括：当上行数据包接收成功时，若完成标识为完成，则所述反馈消息携带有用于取消初始无线资源控制协议的拒绝消息；若完成标识为未完成，则所述反馈消息携带有用于建立初始无线资源控制协议的允许连接消息。
上述完成标识可以根据实际情况进行标识设定，例如，可以标识该上行数据包是否为最后一个数据包。当为最后一个数据包时，则表示已经发送完成。
例如在实际应用中，若发送的上行数据包比较少，一次能够发完，则可以直接发送。当发送的上行数据包较多时，可以优先采用非RRC连接状态发送一定数量的上行数据包，然后在建立RRC连接后，再发送接下来的上行数据包。从而可以很好的对网络数据包的发送进行控制。
步骤209、当所述反馈消息标识为接收失败时，在所述反馈消息携带的重新确定的上行调度指示所指示的时频域位置重新发送上行数据包，或者根据所述反馈消息携带的允许连接消息建立空口信令连接。
该步骤中，建立空口信令连接即为：建立无线资源控制协议连。当接收失败时，可以由网络侧设备根据实际情况(例如网络侧的负载状态)确定是进行数据重传还是进行状态迁移。当确定进行重传时，可以在反馈消息中携带重新确定的上行调度指示所指示，然后由终端在所述反馈消息携带的重新确定的上行调度指示所指示的时频域位置重新发送上行数据包。或者确定为改变RRC连接状态时，将会在反馈消息中携带允许连接消息，即上述RRC Connection Setup或RRC Connection Resume；从而由终端发起建立RRC的流程。本实施例由于网络侧设备在接收上行数据包失败的情况下，可以综合考虑网络侧的状态，由网络侧设备决定进行重传或者状态迁移，因此提高了网络控制的灵活性。
应当说明的是，在进行随机接入时，可能由于多个终端选择相同的随机前导序列，则导致网络侧设备接收消息时的干扰，并最终形成随机接入冲突。 考虑到5G终端数目的增强将增加随机前导序列空间，因为随机前导发生冲突的可能性不会和5G终端数量增强成正比。但任然有可能发生冲突，如遇到冲突，如下方式解决。
如果终端在接收msg2过程中，在PDCCH(Physical Downlink Control Channel，物理下行控制信道)中未盲检出自己的RA-RNTI，则说明msg1前导发送失败，终端根据预设的方式，再次发送随机前导；
如果终端在接收mg2过程中，在PDCCH中检测到自己的RA-RNTI，且在MAC(媒体接入控制层)数据包中发现与自己对应的RAPID(随机前导序列)，则表示msg1前导发送成功。
如果基站由于负载原因拒绝此次发送申请，则终端根据MAC数据包的配置回退值，再次发送随机接入；
如果基站允许此次发送申请，终端在msg2中指示的时频域位置发送上行数据包。如果多个终端使用相同随机前导序列和时频域位置，多个终端使用的msg2中分配的时频域位置相同，则发生冲突。终端通过接收msg4确定是否自己发送的上行数据包被成功接收，若未成功则进行重传。网络侧设备可以根据上行数据包的接收情况考虑重传或者进行状态转移。
应当说明的是，采用终端对业务特征信息进行判断是否支持不进行状态迁移的数据发送方式后，发送标识符到网络侧设备的方式属于终端决策；而终端直接将业务特征信息发送到网络侧设备，由网络侧设备判断是否支持不进行状态迁移的数据发送的方式属于基站决策。由于在终端中直接可以获取业务特征信息，并在触发接入流程前即可判断出是否支持不进行状态迁移的数据发送方式，因此基于终端决策的方式可以减少数据发送的时间。也就是说，在本实施例中，由终端决策比由基站决策快。
第三实施例
参见图7，图7是本公开实施例提供的数据传输方法的流程图，如图7所示，包括以下步骤：
步骤701、接收终端在建立空口信令连接前所发送的携带有状态迁移数据的数据消息。
本公开实施例中，上述空口信令为端与端之间的数据传输信令协议，例 如现有的空口信令包括无线资源控制协议信令。其中无线资源控制协议为RRC(Radio Resource Control)，状态迁移数据为用于反应是否支持不进行状态迁移的数据发送方式的数据特征。其中状态迁移是指RRC的连接状态变化，具体地，是指从未建立RRC连接到建议RRC连接。上述数据特征的类型可以根据实际需要进行设置，例如可以为是否支持不进行状态迁移的数据发送方式的判断条件，也可以是对该判断条件的判断结果，以下实施例中对此进行详细说明。上述网络侧设备是指基站。
例如，当移动终端长期未产生业务数据时，移动终端将自动与核心网断开RRC连接，当再次需要发送上行业务数据(上行数据包)时，则可能需要建立RRC连接，以向核心网发送数据包。具体地，该业务数据的类型可以为任意类型，如智能水表业务、车联网业务和eMBB(增强的移动宽频通信，Enhanced mobile broadband)业务等。
步骤702、基于所述数据消息，向所述终端返回应答消息，所述应答消息携带有数据发送指示。
该步骤中，包括发送和不发送两种状态。当网络侧设备接收到上述数据消息后，将会对该数据消息进行应答，在应答消息中将会携带该数据发送指示。具体的，应答的方式与数据消息的内容相匹配。由于上述数据消息中的状态迁移数据可以为多种形式，对应的应答方式可以对应设置为多种应答方式。例如，当状态迁移数据为是否支持不进行状态迁移的数据发送方式的判断条件，网络侧设备将会根据该判断条件确定终端是否支持在不状态迁移的情况进行下发送数据，从而下发数据发送指示；当状态迁移数据为对该判断条件的判断结果时，可以根据判断结果直接下发数据发送指示，也可以按照网络侧设备获取的网络侧信息判断是否允许终端在不进行状态迁移的情况下进行数据发送，从而下发数据发送指示。
步骤703、接收终端在所述数据发送指示为发送时所发送的上行数据包。
该步骤中，当终端接收到网络侧设备的应答消息后，将会根据该应答消息中的数据发送指示执行相应的操作。具体地，当数据发送指示为发送时，则可以向网络侧设备发送上行数据包，当网络侧设备接收到该上行数据包后，将会把该上行数据包发送到核心网，从而完成上行数据包的发送。
可以理解的是，对于不同的业务数据是否支持不进行状态迁移的数据发送方式的判断规则可以根据实际需要进行设置，在此不做进一步的限定。
本公开实施例中，上述终端可以为任何具备显示和安装应用程序功能的移动终端，例如：手机、平板电脑(Tablet Personal Computer)、膝上型电脑(Laptop Computer)、个人数字助理(personal digital assistant，简称PDA)、移动上网装置(Mobile Internet Device，MID)或可穿戴式设备(Wearable Device)等。
这样，本公开实施例中，接收终端在建立空口信令连接前所发送的携带有状态迁移数据的数据消息；基于所述数据消息，向所述终端返回应答消息，所述应答消息携带有数据发送指示；接收终端在所述数据发送指示为发送时所发送的上行数据包。由于可以对上行数据包是否迁移到RRC连接状态下进行发送进行了控制，从而可以有效降低业务数据的时延需求，因此提高了网络行为的灵活性。
本公开可以在物联网(IoT)场景下，解决大量mMTC(Massive Machine Type Communication，大规模物联网)接入网络进行突发的小数据包发送时，由于需要从终端IDLE状态迁移到RRC状态带来的信令负载问题。
第四实施例
参见图8，图8是本公开实施例提供的数据传输方法的流程图，如图8所示，包括以下步骤：
步骤801、接收终端在建立空口信令连接前所发送的携带有状态迁移数据的数据消息。
本公开实施例中，上述空口信令为端与端之间的数据传输信令协议，例如现有的空口信令包括无线资源控制协议信令。其中无线资源控制协议为RRC(Radio Resource Control)，状态迁移数据为用于反应是否支持不进行状态迁移的数据发送方式的数据特征。其中状态迁移是指RRC的连接状态变化，具体地，是指从未建立RRC连接到建议RRC连接。上述数据特征的类型可以根据实际需要进行设置，例如可以为是否支持不进行状态迁移的数据发送方式的判断条件，也可以是对该判断条件的判断结果，以下实施例中对此进行详细说明。上述网络侧设备是指基站。
在本实施例中，上述数据消息为随机接入请求消息。即在随机接入流程中，确定是否建立无线资源控制协议连接发送上行数据包。具体地，在随机接入流程中包括msg1至msg4，其中msg1为随机接入请求消息，msg2为对随机接入请求消息应答的随机接入应答消息，msg3是初始RRC消息，msg4为初始RRC消息的回复消息。本实施例中，具体在终端发送的msg1中携带状态迁移数据。
例如，当移动终端长期未产生业务数据时，移动终端将自动与核心网断开RRC连接，当再次需要发送上行业务数据(上行数据包)时，则可能需要建立RRC连接，以向核心网发送数据包。具体地，该业务数据的类型可以为任意类型，如智能水表业务、车联网业务和eMBB(增强的移动宽频通信，Enhanced mobile broadband)业务等。
步骤802、基于所述数据消息，向所述终端返回应答消息，所述应答消息携带有数据发送指示。
该步骤中，上述数据发送指示包括发送和不发送两种状态。当网络侧设备接收到上述数据消息后，将会对该数据消息进行应答，在应答消息中将会携带该数据发送指示。具体的，应答的方式与数据消息的内容相匹配。由于上述数据消息中的状态迁移数据可以为多种形式，对应的应答方式可以对应设置为多种应答方式。例如，当状态迁移数据为是否支持不进行状态迁移的数据发送方式的判断条件，网络侧设备将会根据该判断条件确定终端是否支持在不进行状态迁移的情况进行下发送数据，从而下发数据发送指示；当状态迁移数据为对该判断条件的判断结果时，可以根据判断结果直接下发数据发送指示，也可以按照网络侧设备获取的网络侧信息判断是否允许终端在不进行状态迁移的情况下进行数据发送，从而下发数据发送指示。例如当网络侧设备不支持不进行状态迁移的数据发送，则可以直接将数据发送指示设置为不发送。
应当说明的是，在上述随机接入应答消息中还携带有用作上行同步的上行定时TA、用作临时标识UE的临时标识符C-RNTI、用作上行功率控制信令P、以及用作msg3调度的上行调度指示(UL grant)；根据随机接入应答消息中各参数的参数值可以控制发送上行数据包的时间。
步骤803、在所述数据消息为随机接入请求消息，且所述应答消息为随机接入应答消息的情况下，接收终端在所述随机接入应答消息携带的上行调度指示所指示的时频域位置所发送的上行数据包；或者，接收终端在默认的物理信道上所发送的上行数据包。
该步骤中，当终端接收到网络侧设备的应答消息后，将会根据该应答消息中的数据发送指示执行相应的操作。具体地，当数据发送指示为发送时，则可以向网络侧设备发送上行数据包，当网络侧设备接收到该上行数据包后，将会把该上行数据包发送到核心网，从而完成上行数据包的发送。
可以理解的是，对于不同的业务数据是否支持不进行状态迁移的数据发送方式的判断规则可以根据实际需要进行设置，在此不做进一步的限定。
可以理解的是，上行数据包发送的方式可以根据实际需要进行设置，例如可以在默认的物理信道上进行发送，也可以在上行调度指示所指示的时频域位置发送。其中默认的物理信道是指终端知晓的物理信道(预先配置的物理信道)。具体的，对于采用哪种方式发送上行数据包可以根据实际需要进行设定，例如可以设置上述随机接入应答消息携带有用于指示所述上行数据包发送方式的选择标识；此外，还可以当应答消息中未包含上行调度指示时，默认使用默认的物理信道进行发送上行数据包。
本公开实施例中，上述移动终端可以为任何具备显示和安装应用程序功能的移动终端，例如：手机、平板电脑(Tablet Personal Computer)、膝上型电脑(Laptop Computer)、个人数字助理(personal digital assistant，简称PDA)、移动上网装置(Mobile Internet Device，MID)或可穿戴式设备(Wearable Device)等。
这样，本公开实施例中，接收终端在建立空口信令连接前所发送的携带有状态迁移数据的数据消息；基于所述数据消息，向所述终端返回应答消息，所述应答消息携带有数据发送指示；在所述数据消息为随机接入请求消息，且所述应答消息为随机接入应答消息的情况下，接收终端在所述随机接入应答消息携带的上行调度指示所指示的时频域位置所发送的上行数据包；或者，接收终端在默认的物理信道上所发送的上行数据包。由于可以对上行数据包是否迁移到RRC连接状态下进行发送进行了控制，从而可以有效降低业务数 据的时延需求，因此提高了网络行为的灵活性。
本公开可以在物联网(IoT)场景下，解决大量mMTC(Massive Machine Type Communication，大规模物联网)接入网络进行突发的小数据包发送时，由于需要从终端IDLE状态迁移到RRC状态带来的信令负载问题。
应当说明的是，本实施例中，在随机接入过程中加入，终端是否支持不进行状态迁移的数据发送方式的状态判断，因此可以不需要额外增加信令，从而无需增加网络侧设备的负载。进一步地，还可以不对现有的随机接入过程进行改变，网络侧设备发送msg4前进行判断，然后根据判断的结果确定发送msg4的内容；或者由设备在接收到msg4后，首先判断终端是否支持不进行状态迁移的数据发送方式，若是，则发送上述状态迁移数据的数据消息到网络侧设备，然后根据网络侧设备反馈的结果确定在信令连接前是否进行数据发送。
进一步地，上述数据特征的类型可以根据实际需要进行设置，例如可以为是否支持不进行状态迁移的数据发送方式的判断条件，也可以是对该判断条件的判断结果。以下对此进行详细说明：
在一种方案中，上述状态迁移数据包括数据发送标识，上述步骤802之前还包括：
根据所述随机接入请求消息携带的数据发送标识，确定是否需要进行数据发送；或者根据所述随机接入请求消息携带的数据发送标识和获取的网络侧信息，确定是否需要进行数据发送。
该步骤中，当根据所述随机接入请求消息携带的数据发送标识，确定是否需要进行数据发送时，则在终端进行判断确定支持不进行状态迁移的数据发送，则直接返回数据发送指示为发送。当根据所述随机接入请求消息携带的数据发送标识和获取的网络侧信息，确定是否需要进行数据发送时，则在终端进行判断确定支持不进行状态迁移的数据发送，则需要再次根据网络侧信息判断是否需要进行数据发送。
上述网络侧信息可以包括网络侧负载状态、终端的签约数据和运营商配置数据中的至少一项。具体地，网络侧负载状态包括网络侧设备的负载情况和/或核心网的负载情况；终端的签约数据包括终端签约类型和终端签约优先 等级等；运营商配置数据包括运营商配置的是否支持状态不迁移的数据发送。
具体地，在终端进行发送上行数据包前，终端可以获取上行数据包的业务特征信息，该业务特征信息的内容可以根据实际需要进行设置，本实施例中，该业务特征信息包括业务类型、业务缓存信息、业务服务质量要求和业务优先级中的至少一项。其中，业务类型包括智能水表业务、车联网业务和eMBB业务等；业务缓存信息为用户上行数据缓存量，例如可以为具体的缓存量(如XX bit)；业务服务质量要求为Qos参数，可以包括丢包率、最大时延等；业务优先级可以为高优先级、中优先级和低优先级。
根据业务特征信息，按照预先定义的规则确定是否支持不进行状态迁移的数据发送方式。例如，当需要的时延较低，且用户上行数据缓存量较低时，可以确定为支持不进行状态迁移的数据发送方式；当需要的时延较高，且用户上述数据缓存量较高时，可以确定为不支持不进行状态迁移的数据发送方式。对于根据业务特征信息判断是否支持不进行状态迁移的数据发送方式的判断规则在此不进行一一列举。
该方案中，由终端判断是否需要进行状态迁移。其中，上述数据发送标识的发送的方式为两种，当采用标识符时，为明文发送方式，例如可以采用1bit的标识符，设置标识符等于1表示迁移，设置标识符等于0标识不迁移。当采用随机前导序列作为数据发送标识时，为暗文发送方式，具体的，所述随机前导序列包括用于标识迁移的第一类随机前导序列和用于标识不迁移的第二类随机前导序列；或者所述随机前导序列中添加用于表示状态迁移的标识位(即将标识符叠加在随机前导序列上)。本实施例中，由于采用暗文的方式发送数据发送标识，从而可以提高数据传输的安全性。例如当不支持不进行状态迁移的数据发送方式时，采用第一类随机前导序列进行随机接入；支持不进行状态迁移的数据发送方式时，采用第二类随机前导序列进行随机接入。
在另一方案中，上述状态迁移数据包括业务特征信息，如图9所示，上述步骤802之前还包括：
步骤804、根据所述随机接入请求消息携带的业务特征信息，确定是否需要进行数据发送；或者根据所述随机接入请求消息携带的业务特征信息和 获取的网络侧信息，确定是否需要进行数据发送。
该方案中，在终端进行发送上行数据包前，终端可以获取上行数据包的业务特征信息，具体地，该业务特征信息的内容可以根据实际需要进行设置，本实施例中，该业务特征信息包括业务类型、业务缓存信息、业务服务质量要求和业务优先级中的至少一项。其中，业务类型包括智能水表业务、车联网业务和eMBB业务等；业务缓存信息为用户上行数据缓存量，例如可以为具体的缓存量(如XX bit)；业务服务质量要求为Qos参数，可以包括丢包率、最大时延等；业务优先级可以为高优先级、中优先级和低优先级。
应当说明的是，对于终端业务特征信息中各参数的表示方式可以采用以下形式进行表示：
业务类型，可以直接给出业务类型表示；
业务缓存信息采用缓存量(如N bit)表示或者采用缓存等级(高、中、低或者待发数据量对应的级别编号(如1～100bit编号为组1，此时采用编组号1表示))表示；
业务服务质量要求采用服务质量参数特征(如低/高时延、小/大数据包)表示，或者采用对服务质量参数特征进行编组的编号(如QCI序列号)表示，或者采用丢包率及最大允许时延(即隐式)表示；
业务优先级采用高优先级、中优先级和低优先级进行表示。
在将上述业务特征信息发送至网络侧设备后，由网络侧设备根据业务特征信息进行判断是否支持不进行状态迁移，对于是否支持不进行状态迁移的数据发送方式的判断规则可以与终端进行判断的规则一致。在本实施例中，为了优化网络环境，还可以结合网络侧设备获取的网络侧信息进行判断，具体地，该网络侧信息包括网络侧负载状态、终端的签约数据和运营商配置数据中的至少一项。其中，网络侧负载状态包括网络侧设备的负载情况和/或核心网的负载情况；终端的签约数据包括终端签约类型和终端签约优先等级等；运营商配置数据包括运营商配置的是否支持状态不迁移的数据发送。
进一步地，参照图10，在上述步骤803之后还包括：
步骤805、当所述上行数据包接收成功时，向所述终端发送接收成功的反馈消息，将接收到的数据包向核心网发送。
本实施例中，可以根据接收到的反馈消息内容确定是否接收成功，当接收成功时，若上行数据包发送完成，则可以停止上行数据包的发送；若上行数据包未发送完成，且可以建立空口信令连接。
具体的，在本实施例中，上行数据包中携带有用于标识上行数据包是否发送完成的完成标识；当接收的上行数据包位于初始无线资源控制协议消息中、且上行数据包接收失败时，所述反馈消息携带有用于建立初始无线资源控制协议的允许连接消息(RRC Connection Reject或RRC Connection Resume Reject)；当接收的上行数据包位于初始无线资源控制协议消息中、且上行数据包接收成功时，若完成标识为完成，则所述反馈消息携带有用于取消初始无线资源控制协议的拒绝消息(RRC Connection Reject或RRC Connection Resume Reject)；若完成标识为未完成，则所述反馈消息携带有用于建立初始无线资源控制协议的允许连接消息。
上述完成标识可以根据实际情况进行标识设定，例如，可以标识该上行数据包是否为最后一个数据包。当为最后一个数据包时，则表示已经发送完成。
例如在实际应用中，若发送的上行数据包比较少，一次能够发完，则可以直接发送。当发送的上行数据包较多时，可以优先采用非RRC连接状态发送一定数量的上行数据包，然后在建立RRC连接后，再发送接下来的上行数据包。从而可以很好的对网络数据包的发送进行控制。
该步骤中，上述反馈消息的信令类型可以根据实际需要进行设置，本实施例中，可选的，该反馈消息为上述msg4。即在本实施例中，上述上行数据包放置在msg3中进行发送。可以理解的是，将上行数据包放置在msg3中进行发送的方式可以根据实际需要进行设置，可选的，在本实施例中，上述步骤203包括：将所述上行数据包放置在媒体接入控制层(MAC，Media Access Control)数据包中或者放置在媒体接入控制层数据包内的无线资源控制协议层信令中，在所述上行调度指示所指示的时频域位置发送。例如，将上行数据包放置在初始无线资源控制协议消息中，且配置所述初始无线资源控制协议消息的连接原因为上行数据包发送。其中，初始无线资源控制协议消息可以为RRC连接请求(RRC Connection Request)消息，也可以为RRC恢复连 接请求(RRC Connection Resume Request)消息。
若接收上行数据包成功，则在msg4中对初始无线资源控制协议消息的反馈消息中可以包含RRC Connection Reject(拒绝)或RRC Connection Resume Reject(恢复拒绝)，并包含拒绝原因为“已完成数据发送”。
若接收上行数据包失败、且决定进行状态迁移，则在msg4中对初始无线资源控制协议消息的反馈消息中可以包含RRC Connection Setup(允许)或RRC Connection Resume(恢复允许)，并包含允许建立连接原因。
若接收上行数据包失败、且决定进行重传，则在msg4中对初始无线资源控制协议消息的反馈消息中可以包含RRC Connection Reject(拒绝)或RRC Connection Resume Reject(恢复拒绝)，并包含拒绝原因为“重传”，并携带重新分配的时频域位置(即时隙资源)。
步骤806、当所述上行数据包接收失败时，向所述终端发送接收失败的反馈消息，所述反馈消息携带有重新确定的上行调度指示或者用于触发所述终端建立连接的允许连接消息。
该步骤中，建立空口信令连接即为：建立无线资源控制协议连。当接收失败时，可以由网络侧设备根据实际情况(例如网络侧的负载状态)确定是进行数据重传还是进行状态迁移。当确定进行重传时，可以在反馈消息中携带重新确定的上行调度指示所指示，然后由终端在所述反馈消息携带的重新确定的上行调度指示所指示的时频域位置重新发送上行数据包。或者确定为改变RRC连接状态时，将会在反馈消息中携带允许连接消息，即上述RRC Connection Setup或RRC Connection Resume；从而由终端发起建立RRC的流程。本实施例由于网络侧设备在接收上行数据包失败的情况下，可以综合考虑网络侧的状态，由网络侧设备决定进行重传或者状态迁移，因此提高了网络控制的灵活性。
应当说明的是，在进行随机接入时，可能由于多个终端选择相同的随机前导序列，则导致网络侧设备接收消息时的干扰，并最终形成随机接入冲突。考虑到5G终端数目的增强将增加随机前导序列空间，因为随机前导发生冲突的可能性不会和5G终端数量增强成正比。但仍然有可能发生冲突，如遇到冲突，如下方式解决。
如果终端在接收msg2过程中，在PDCCH(Physical Downlink Control Channel，物理下行控制信道)中未盲检出自己的RA-RNTI，则说明msg1前导发送失败，终端根据预设的方式，再次发送随机前导；
如果终端在接收mg2过程中，在PDCCH中检测到自己的RA-RNTI，且在MAC(媒体接入控制层)数据包中发现与自己对应的RAPID(随机前导序列)，则表示msg1前导发送成功。
如果基站由于负载原因拒绝此次发送申请，则终端根据MAC数据包的配置回退值，再次发送随机接入；
如果基站允许此次发送申请，终端在msg2中指示的时频域位置发送上行数据包。如果多个终端使用相同随机前导序列和时频域位置，多个终端使用的msg2中分配的时频域位置相同，则发生冲突。终端通过接收msg4确定是否自己发送的上行数据包被成功接收，若未成功则进行重传。网络侧设备可以根据上行数据包的接收情况考虑重传或者进行状态转移。
本公开实施例中，接收终端在建立无线资源控制协议连接前，所发送的携带有状态迁移数据的数据消息；基于数据消息向所述终端返回应答消息，所述应答消息携带有状态迁移指示；接收终端在所述状态迁移指示为不迁移时，所发送的上行数据包。由于可以对上行数据包是否迁移到RRC连接状态下进行发送进行了控制，从而可以有效降低业务数据的时延需求，因此提高了网络行为的灵活性。
第五实施例
参见图11，图11是本公开实施提供的终端的结构图，能实现第一实施例至第二实施例中的数据传输方法的细节，并达到相同的效果。如图11所示，终端1100包括：数据消息发送模块1101、应答消息接收模块1102和数据包发送模块1103，其中，
数据消息发送模块1101，用于建立空口信令连接前，向网络侧设备发送携带有状态迁移数据的数据消息；
应答消息接收模块1102，用于接收网络侧设备对数据消息返回的应答消息，所述应答消息携带有数据发送指示；
数据包发送模块1103，用于当所述数据发送指示为发送时，向所述网络 侧设备发送上行数据包。
可选的，所述数据包发送模块1103具体用于，当所述数据消息为随机接入请求消息，且所述应答消息为随机接入应答消息时，在所述随机接入应答消息携带的上行调度指示所指示的时频域位置发送上行数据包；或者，在默认的物理信道上向所述网络侧设备发送上行数据包。
可选的，所述随机接入应答消息携带有用于指示所述上行数据包发送方式的选择标识。
可选的，参照图12，所述终端还包括：
协议消息发送模块1104，用于当所述数据发送指示为不发送时，在所述上行调度指示所指示的时频域位置发送初始无线资源控制协议消息。
可选的，所述状态迁移数据包括数据发送标识；所述数据发送标识包括所述随机接入请求消息携带的标识符或者所述随机接入请求消息携带的随机前导序列。
可选的，所述随机前导序列包括用于标识发送的第一类随机前导序列和用于标识不发送的第二类随机前导序列。
可选的，所述随机前导序列中添加用于表示是否需要发送的标识位。
可选的，参照图13，所述终端还包括：
获取模块1105，用于获取所述上行数据包的业务特征信息；
第一确定模块1106，用于根据所述业务特征信息，确定是否需要进行数据发送；
其中，所述数据消息携带的状态迁移数据为：确定是否需要进行数据发送的结果。
可选的，所述状态迁移数据包括业务特征信息，其中，所述业务特征信息用于所述网络侧设备根据所述业务特征信息确定是否需要进行数据发送；
或者所述网络侧设备根据所述业务特征信息和网络侧设备获取的网络侧信息确定是否需要进行数据发送。
可选的，所述网络侧信息包括网络侧负载状态、终端的签约数据和运营商配置数据中的至少一项。
可选的，所述业务特征信息包括：业务类型、业务缓存信息、业务服务 质量要求和业务优先级中的至少一项。
可选的，所述业务缓存信息采用缓存量表示或者采用缓存等级表示；
所述业务服务质量要求采用服务质量参数特征表示，或者采用对服务质量参数特征进行编组的编号表示，或者采用丢包率及最大允许时延表示。
可选的，参照图14，所述上行数据包中携带有用于标识上行数据包是否发送完成的完成标识；所述终端还包括：
反馈消息接收模块1107，用于接收网络侧设备根据所述上行数据包接收状态和完成标识回复的反馈消息；
控制模块1108，用于当所述反馈消息标识为接收成功时，则停止发送所述上行数据包或者建立空口信令连接；当所述反馈消息标识为接收失败时，在所述反馈消息携带的重新确定的上行调度指示所指示的时频域位置重新发送上行数据包，或者根据所述反馈消息携带的允许连接消息建立空口信令连接。
可选的，当上行数据包接收成功时，若完成标识为完成，则所述反馈消息携带有用于取消初始无线资源控制协议的拒绝消息；若完成标识为未完成，则所述反馈消息携带有用于建立初始无线资源控制协议的允许连接消息。
可选的，所述数据包发送模块1103具体用于：
将所述上行数据包放置在媒体接入控制层数据包中，在所述上行调度指示所指示的时频域位置发送；
或者将所述上行数据包放置在媒体接入控制层数据包内的无线资源控制协议层信令中，在所述上行调度指示所指示的时频域位置发送；
或者将所述上行数据包作为媒体接入控制层数据包，在所述上行调度指示所指示的时频域位置发送。
可选的，所述数据包发送模块1103具体用于：将所述上行数据包放置在初始无线资源控制协议消息中，且配置所述初始无线资源控制协议消息的连接原因为上行数据包发送。
本公开实施例中，建立空口信令连接前，向网络侧设备发送携带有状态迁移数据的数据消息；接收网络侧设备对数据消息返回的应答消息，所述应答消息携带有数据发送指示；当所述数据发送指示为发送时，向所述网络侧 设备发送上行数据包。由于可以对上行数据包是否迁移到RRC连接状态下进行发送进行了控制，从而可以有效降低业务数据的时延需求，因此提高了网络行为的灵活性。
第六实施例
参见图15，图15是本公开实施提供的网络侧设备的结构图，能实现第三实施例至第四实施例中的数据传输方法的细节，并达到相同的效果。如图15所示，网络侧设备1500包括：数据消息接收模块1501、应答消息发送模块1502和数据包接收模块1503，其中，
数据消息接收模块1501，用于接收终端在建立空口信令连接前所发送的携带有状态迁移数据的数据消息；
应答消息发送模块1502，用于基于所述数据消息，向所述终端返回应答消息，所述应答消息携带有数据发送指示；
数据包接收模块1503，用于接收终端在所述数据发送指示为发送时所发送的上行数据包。
可选的，所述数据包接收模块1503具体用于：
接收终端在所述随机接入应答消息携带的上行调度指示所指示的时频域位置所发送的上行数据包；
或者，接收终端在默认的物理信道上所发送的上行数据包。
可选的，所述随机接入应答消息携带有用于指示所述上行数据包发送方式的选择标识。
可选的，参照图16，所述网络侧设备还包括：
第二确定模1504，用于根据所述随机接入请求消息携带的数据发送标识，确定是否需要进行数据发送；
或者根据所述随机接入请求消息携带的数据发送标识和获取的网络侧信息，确定是否需要进行数据发送。
可选的，所述数据发送标识包括所述随机接入请求消息携带的标识符或者所述随机接入请求消息携带的随机前导序列。
可选的，当所述数据发送标识包括所述随机接入请求消息携带的随机前导序列时，所述随机前导序列包括用于标识发送的第一类随机前导序列和用 于标识不发送的第二类随机前导序列。
可选的，当所述数据发送标识包括所述随机接入请求消息携带的随机前导序列时，所述随机前导序列中添加用于表示是否需要发送的标识位。
可选的，参照图17，所述网络侧设备还包括：
第三确定模块1505，用于根据所述随机接入请求消息携带的业务特征信息，确定是否需要进行数据发送；或者根据所述随机接入请求消息携带的业务特征信息和获取的网络侧信息，确定是否需要进行数据发送。
可选的，所述业务特征信息包括：业务类型、业务缓存信息、业务服务质量要求和业务优先级中的至少一项。
可选的，所述业务缓存信息采用缓存量表示或者采用缓存等级表示；
所述业务服务质量要求采用服务质量参数特征表示，或者采用对服务质量参数特征进行编组的编号表示，或者采用丢包率及最大允许时延表示。
可选的，所述网络侧信息包括网络侧负载状态、终端的签约数据和运营商配置数据中的至少一项。
可选的，参照图18，所述网络侧设备还包括：
处理模块1056，用于当所述上行数据包接收成功时，向所述终端发送接收成功的反馈消息，将接收到的数据包向核心网发送；
反馈消息发送模块1507，用于当所述上行数据包接收失败时，向所述终端发送接收失败的反馈消息，所述反馈消息携带有重新确定的上行调度指示或者用于触发所述终端建立连接的允许连接消息。
可选的，所述上行数据包中携带有用于标识上行数据包是否发送完成的完成标识；
当接收的上行数据包位于初始无线资源控制协议消息中、且上行数据包接收成功时，若完成标识为完成，则所述反馈消息携带有用于取消初始无线资源控制协议的拒绝消息；若完成标识为未完成，则所述反馈消息携带有用于建立初始无线资源控制协议的允许连接消息。
本公开实施例中，接收终端在建立空口信令连接前所发送的携带有状态迁移数据的数据消息；基于所述数据消息，向所述终端返回应答消息，所述应答消息携带有数据发送指示；接收终端在所述数据发送指示为发送时所发 送的上行数据包。由于可以对上行数据包是否迁移到RRC连接状态下进行发送进行了控制，从而可以有效降低业务数据的时延需求，因此提高了网络行为的灵活性。
本公开实施例中，接收终端在建立无线资源控制协议连接前，所发送的携带有状态迁移数据的数据消息；对数据消息向所述终端返回应答消息，所述应答消息携带有状态迁移指示；接收终端在所述状态迁移指示为不迁移时，所发送的上行数据包。由于可以对上行数据包是否迁移到RRC连接状态下进行发送进行了控制，从而可以有效降低业务数据的时延需求，因此提高了网络行为的灵活性。
第七实施例
参见图19，图19是本公开实施例应用的移动终端的结构图，能够实现第一实施例至第二实施例中数据传输方法的细节，并达到相同的效果。如图19所示，移动终端1900包括：至少一个处理器1901、存储器1902、至少一个网络接口1904和用户接口1903。移动终端1900中的各个组件通过总线系统1905耦合在一起。可理解，总线系统1905用于实现这些组件之间的连接通信。总线系统1905除包括数据总线之外，还包括电源总线、控制总线和状态信号总线。但是为了清楚说明起见，在图19中将各种总线都标为总线系统1905。
其中，用户接口1903可以包括显示器、键盘或者点击设备(例如，鼠标，轨迹球(track ball)、触感板或者触摸屏等。
可以理解，本公开实施例中的存储器1902可以是易失性存储器或非易失性存储器，或可包括易失性和非易失性存储器两者。其中，非易失性存储器可以是只读存储器(Read-Only Memory，ROM)、可编程只读存储器(Programmable ROM，PROM)、可擦除可编程只读存储器(Erasable PROM，EPROM)、电可擦除可编程只读存储器(Electrically EPROM，EEPROM)或闪存。易失性存储器可以是随机存取存储器(Random Access Memory，RAM)，其用作外部高速缓存。通过示例性但不是限制性说明，许多形式的RAM可用，例如静态随机存取存储器(Static RAM，SRAM)、动态随机存取存储器(Dynamic RAM，DRAM)、同步动态随机存取存储器(Synchronous DRAM， SDRAM)、双倍数据速率同步动态随机存取存储器(Double Data Rate SDRAM，DDRSDRAM)、增强型同步动态随机存取存储器(Enhanced SDRAM，ESDRAM)、同步连接动态随机存取存储器(Synchlink DRAM，SLDRAM)和直接内存总线随机存取存储器(Direct Rambus RAM，DRRAM)。本文描述的系统和方法的存储器1902旨在包括但不限于这些和任意其它适合类型的存储器。
在一些实施方式中，存储器1902存储了如下的元素，可执行模块或者数据结构，或者他们的子集，或者他们的扩展集：操作系统19021和应用程序19022。
其中，操作系统19021，包含各种系统程序，例如框架层、核心库层、驱动层等，用于实现各种基础业务以及处理基于硬件的任务。应用程序19022，包含各种应用程序，例如媒体播放器(Media Player)、浏览器(Browser)等，用于实现各种应用业务。实现本公开实施例方法的程序可以包含在应用程序19022中。
在本公开实施例中，通过调用存储器1902存储的程序或指令，具体的，可以是应用程序19022中存储的程序或指令，处理器1901用于：建立空口信令连接前，向网络侧设备发送携带有状态迁移数据的数据消息；接收网络侧设备对数据消息返回的应答消息，所述应答消息携带有数据发送指示；当所述数据发送指示为发送时，向所述网络侧设备发送上行数据包。
上述本公开实施例揭示的方法可以应用于处理器1901中，或者由处理器1901实现。处理器1901可能是一种集成电路芯片，具有信号的处理能力。在实现过程中，上述方法的各步骤可以通过处理器1901中的硬件的集成逻辑电路或者软件形式的指令完成。上述的处理器1901可以是通用处理器、数字信号处理器(Digital Signal Processor，DSP)、专用集成电路(Application Specific Integrated Circuit，ASIC)、现成可编程门阵列(Field Programmable GateArray，FPGA)或者其他可编程逻辑器件、分立门或者晶体管逻辑器件、分立硬件组件。可以实现或者执行本公开实施例中的公开的各方法、步骤及逻辑框图。通用处理器可以是微处理器或者该处理器也可以是任何常规的处理器等。结合本公开实施例所公开的方法的步骤可以直接体现为硬件译码处理器执行完 成，或者用译码处理器中的硬件及软件模块组合执行完成。软件模块可以位于随机存储器，闪存、只读存储器，可编程只读存储器或者电可擦写可编程存储器、寄存器等本领域成熟的存储介质中。该存储介质位于存储器1902，处理器1901读取存储器1902中的信息，结合其硬件完成上述方法的步骤。
可以理解的是，本文描述的这些实施例可以用硬件、软件、固件、中间件、微码或其组合来实现。对于硬件实现，处理单元可以实现在一个或多个专用集成电路(Application Specific Integrated Circuits，ASIC)、数字信号处理器(Digital Signal Processing，DSP)、数字信号处理设备(DSP Device，DSPD)、可编程逻辑设备(Programmable Logic Device，PLD)、现场可编程门阵列(Field-Programmable Gate Array，FPGA)、通用处理器、控制器、微控制器、微处理器、用于执行本申请所述功能的其它电子单元或其组合中。
对于软件实现，可通过执行本文所述功能的模块(例如过程、函数等)来实现本文所述的技术。软件代码可存储在存储器中并通过处理器执行。存储器可以在处理器中或在处理器外部实现。
可选的，处理器1901还用于：当所述数据消息为随机接入请求消息，且所述应答消息为随机接入应答消息时，在所述随机接入应答消息携带的上行调度指示所指示的时频域位置发送上行数据包；
或者，在默认的物理信道上向所述网络侧设备发送上行数据包。
可选的，所述随机接入应答消息携带有用于指示所述上行数据包发送方式的选择标识。
可选的，处理器1901还用于：当所述数据发送指示为不发送时，在所述上行调度指示所指示的时频域位置发送初始无线资源控制协议消息。
可选的，所述状态迁移数据包括数据发送标识；所述数据发送标识包括所述随机接入请求消息携带的标识符或者所述随机接入请求消息携带的随机前导序列。
可选的，所述随机前导序列包括用于标识发送的第一类随机前导序列和用于标识不发送的第二类随机前导序列。
可选的，所述随机前导序列中添加用于表示是否需要发送的标识位。
可选的，处理器1901还用于：获取所述上行数据包的业务特征信息；
根据所述业务特征信息，确定是否需要进行数据发送；
其中，所述数据消息携带的状态迁移数据为：确定是否需要进行数据发送的结果。
可选的，所述状态迁移数据包括业务特征信息，其中，所述业务特征信息用于所述网络侧设备根据所述业务特征信息确定是否需要进行数据发送；
或者所述网络侧设备根据所述业务特征信息和网络侧设备获取的网络侧信息确定是否需要进行数据发送。
可选的，所述网络侧信息包括网络侧负载状态、终端的签约数据和运营商配置数据中的至少一项。
可选的，所述业务特征信息包括：业务类型、业务缓存信息、业务服务质量要求和业务优先级中的至少一项。
可选的，所述业务缓存信息采用缓存量表示或者采用缓存等级表示；
所述业务服务质量要求采用服务质量参数特征表示，或者采用对服务质量参数特征进行编组的编号表示，或者采用丢包率及最大允许时延表示。
可选的，所述上行数据包中携带有用于标识上行数据包是否发送完成的完成标识；处理器1901还用于：接收网络侧设备根据所述上行数据包接收状态和完成标识回复的反馈消息；
当所述反馈消息标识为接收成功时，则停止发送所述上行数据包或者建立空口信令连接；
当所述反馈消息标识为接收失败时，在所述反馈消息携带的重新确定的上行调度指示所指示的时频域位置重新发送上行数据包，或者根据所述反馈消息携带的允许连接消息建立空口信令连接。
可选的，当上行数据包接收成功时，若完成标识为完成，则所述反馈消息携带有用于取消初始无线资源控制协议的拒绝消息；若完成标识为未完成，则所述反馈消息携带有用于建立初始无线资源控制协议的允许连接消息。
可选的，处理器1901还用于：将所述上行数据包放置在媒体接入控制层数据包中，在所述上行调度指示所指示的时频域位置发送；
或者将所述上行数据包放置在媒体接入控制层数据包内的无线资源控制协议层信令中，在所述上行调度指示所指示的时频域位置发送；
或者将所述上行数据包作为媒体接入控制层数据包，在所述上行调度指示所指示的时频域位置发送。
可选的，所述将所述上行数据包放置在媒体接入控制层数据包内的无线资源控制协议层信令中包括：将所述上行数据包放置在初始无线资源控制协议消息中，且配置所述初始无线资源控制协议消息的连接原因为上行数据包发送。
本公开实施例中，建立空口信令连接前，向网络侧设备发送携带有状态迁移数据的数据消息；接收网络侧设备对数据消息返回的应答消息，所述应答消息携带有数据发送指示；当所述数据发送指示为发送时，向所述网络侧设备发送上行数据包。由于可以对上行数据包是否迁移到RRC连接状态下进行发送进行了控制，从而可以有效降低业务数据的时延需求，因此提高了网络行为的灵活性。
第八实施例
请参阅图20，图20是本公开实施例应用的移动终端的结构图，能够实现第一实施例至第二实施例中数据传输方法的细节，并达到相同的效果。如图20所示，移动终端2000包括射频(Radio Frequency，RF)电路2010、存储器2020、输入单元2030、显示单元2040、处理器2050、音频电路2060、通信模块2070和电源2080。
其中，输入单元2030可用于接收用户输入的数字或字符信息，以及产生与移动终端2000的用户设置以及功能控制有关的信号输入。具体地，本公开实施例中，该输入单元2030可以包括触控面板2031。触控面板2031，也称为触摸屏，可收集用户在其上或附近的触摸操作(比如用户使用手指、触笔等任何适合的物体或附件在触控面板2031上的操作)，并根据预先设定的程式驱动相应的连接装置。可选的，触控面板2031可包括触摸检测装置和触摸控制器两个部分。其中，触摸检测装置检测用户的触摸方位，并检测触摸操作带来的信号，将信号传送给触摸控制器；触摸控制器从触摸检测装置上接收触摸信息，并将它转换成触点坐标，再送给该处理器2050，并能接收处理器2050发来的命令并加以执行。此外，可以采用电阻式、电容式、红外线以及表面声波等多种类型实现触控面板2031。除了触控面板2031，输入单元2030 还可以包括其他输入设备2032，其他输入设备2032可以包括但不限于物理键盘、功能键(比如音量控制按键、开关按键等)、轨迹球、鼠标、操作杆等中的一种或多种。
其中，显示单元2040可用于显示由用户输入的信息或提供给用户的信息以及移动终端2000的各种菜单界面。显示单元2040可包括显示面板2041，可选的，可以采用LCD或有机发光二极管(Organic Light-Emitting Diode，OLED)等形式来配置显示面板2041。
应注意，触控面板2031可以覆盖显示面板2041，形成触摸显示屏，当该触摸显示屏检测到在其上或附近的触摸操作后，传送给处理器2050以确定触摸事件的类型，随后处理器2050根据触摸事件的类型在触摸显示屏上提供相应的视觉输出。
触摸显示屏包括应用程序界面显示区及常用控件显示区。该应用程序界面显示区及该常用控件显示区的排列方式并不限定，可以为上下排列、左右排列等可以区分两个显示区的排列方式。该应用程序界面显示区可以用于显示应用程序的界面。每一个界面可以包含至少一个应用程序的图标和/或widget桌面控件等界面元素。该应用程序界面显示区也可以为不包含任何内容的空界面。该常用控件显示区用于显示使用率较高的控件，例如，设置按钮、界面编号、滚动条、电话本图标等应用程序图标等。
其中处理器2050是移动终端2000的控制中心，利用各种接口和线路连接整个手机的各个部分，通过运行或执行存储在第一存储器2021内的软件程序和/或模块，以及调用存储在第二存储器2022内的数据，执行移动终端2000的各种功能和处理数据，从而对移动终端2000进行整体监控。可选的，处理器2050可包括一个或多个处理单元。
在本公开实施例中，通过调用存储该第一存储器2021内的软件程序和/或模块和/或该第二存储器2022内的数据，处理器2050用于：建立空口信令连接前，向网络侧设备发送携带有状态迁移数据的数据消息；接收网络侧设备对数据消息返回的应答消息，所述应答消息携带有数据发送指示；当所述数据发送指示为发送时，向所述网络侧设备发送上行数据包。
可选的，处理器2050还用于：当所述数据消息为随机接入请求消息，且 所述应答消息为随机接入应答消息时，在所述随机接入应答消息携带的上行调度指示所指示的时频域位置发送上行数据包；
或者，在默认的物理信道上向所述网络侧设备发送上行数据包。
可选的，所述随机接入应答消息携带有用于指示所述上行数据包发送方式的选择标识。
可选的，处理器2050还用于：当所述数据发送指示为不发送时，在所述上行调度指示所指示的时频域位置发送初始无线资源控制协议消息。
可选的，所述状态迁移数据包括数据发送标识；所述数据发送标识包括所述随机接入请求消息携带的标识符或者所述随机接入请求消息携带的随机前导序列。
可选的，所述随机前导序列包括用于标识发送的第一类随机前导序列和用于标识不发送的第二类随机前导序列。
可选的，所述随机前导序列中添加用于表示是否需要发送的标识位。
可选的，处理器2050还用于：获取所述上行数据包的业务特征信息；
根据所述业务特征信息，确定是否需要进行数据发送；
其中，所述数据消息携带的状态迁移数据为：确定是否需要进行数据发送的结果。
可选的，所述状态迁移数据包括业务特征信息，其中，所述业务特征信息用于所述网络侧设备根据所述业务特征信息确定是否需要进行数据发送；
或者所述网络侧设备根据所述业务特征信息和网络侧设备获取的网络侧信息确定是否需要进行数据发送。
可选的，所述网络侧信息包括网络侧负载状态、终端的签约数据和运营商配置数据中的至少一项。
可选的，所述业务特征信息包括：业务类型、业务缓存信息、业务服务质量要求和业务优先级中的至少一项。
可选的，所述业务缓存信息采用缓存量表示或者采用缓存等级表示；
所述业务服务质量要求采用服务质量参数特征表示，或者采用对服务质量参数特征进行编组的编号表示，或者采用丢包率及最大允许时延表示。
可选的，所述上行数据包中携带有用于标识上行数据包是否发送完成的 完成标识；处理器2050还用于：接收网络侧设备根据所述上行数据包接收状态和完成标识回复的反馈消息；
当所述反馈消息标识为接收成功时，则停止发送所述上行数据包或者建立空口信令连接；
当所述反馈消息标识为接收失败时，在所述反馈消息携带的重新确定的上行调度指示所指示的时频域位置重新发送上行数据包，或者根据所述反馈消息携带的允许连接消息建立空口信令连接。
可选的，当上行数据包接收成功时，若完成标识为完成，则所述反馈消息携带有用于取消初始无线资源控制协议的拒绝消息；若完成标识为未完成，则所述反馈消息携带有用于建立初始无线资源控制协议的允许连接消息。
可选的，处理器2050还用于：将所述上行数据包放置在媒体接入控制层数据包中，在所述上行调度指示所指示的时频域位置发送；
或者将所述上行数据包放置在媒体接入控制层数据包内的无线资源控制协议层信令中，在所述上行调度指示所指示的时频域位置发送；
或者将所述上行数据包作为媒体接入控制层数据包，在所述上行调度指示所指示的时频域位置发送。
可选的，所述将所述上行数据包放置在媒体接入控制层数据包内的无线资源控制协议层信令中包括：将所述上行数据包放置在初始无线资源控制协议消息中，且配置所述初始无线资源控制协议消息的连接原因为上行数据包发送。
本公开实施例中，建立空口信令连接前，向网络侧设备发送携带有状态迁移数据的数据消息；接收网络侧设备对数据消息返回的应答消息，所述应答消息携带有数据发送指示；当所述数据发送指示为发送时，向所述网络侧设备发送上行数据包。由于可以对上行数据包是否迁移到RRC连接状态下进行发送进行了控制，从而可以有效降低业务数据的时延需求，因此提高了网络行为的灵活性。
本领域普通技术人员可以意识到，结合本文中所公开的实施例描述的各示例的单元及算法步骤，能够以电子硬件、或者计算机软件和电子硬件的结合来实现。这些功能究竟以硬件还是软件方式来执行，取决于技术方案的特 定应用和设计约束条件。专业技术人员可以对每个特定的应用来使用不同方法来实现所描述的功能，但是这种实现不应认为超出本公开的范围。
所属领域的技术人员可以清楚地了解到，为描述的方便和简洁，上述描述的系统、装置和单元的具体工作过程，可以参考前述方法实施例中的对应过程，在此不再赘述。
在本申请所提供的实施例中，应该理解到，所揭露的装置和方法，可以通过其它的方式实现。例如，以上所描述的装置实施例仅仅是示意性的，例如，所述单元的划分，仅仅为一种逻辑功能划分，实际实现时可以有另外的划分方式，例如多个单元或组件可以结合或者可以集成到另一个系统，或一些特征可以忽略，或不执行。另一点，所显示或讨论的相互之间的耦合或直接耦合或通信连接可以是通过一些接口，装置或单元的间接耦合或通信连接，可以是电性，机械或其它的形式。
所述作为分离部件说明的单元可以是或者也可以不是物理上分开的，作为单元显示的部件可以是或者也可以不是物理单元，即可以位于一个地方，或者也可以分布到多个网络单元上。可以根据实际的需要选择其中的部分或者全部单元来实现本公开实施例方案的目的。
另外，在本公开各个实施例中的各功能单元可以集成在一个处理单元中，也可以是各个单元单独物理存在，也可以两个或两个以上单元集成在一个单元中。
所述功能如果以软件功能单元的形式实现并作为独立的产品销售或使用时，可以存储在一个计算机可读取存储介质中。基于这样的理解，本公开的技术方案本质上或者说对现有技术做出贡献的部分或者该技术方案的部分可以以软件产品的形式体现出来，该计算机软件产品存储在一个存储介质中，包括若干指令用以使得一台计算机设备(可以是个人计算机，服务器，或者网络设备等)执行本公开各个实施例所述方法的全部或部分步骤。而前述的存储介质包括：U盘、移动硬盘、ROM、RAM、磁碟或者光盘等各种可以存储程序代码的介质。
此外，本公开实施例还提供了一种网络侧设备，包括：存储器、处理器及存储在所述存储器上并可在所述处理器上运行的计算机程序，所述处理器 执行所述计算机程序时实现图7至10中数据传输方法的步骤。
以上所述，仅为本公开的具体实施方式，但本公开的保护范围并不局限于此，任何熟悉本技术领域的技术人员在本公开揭露的技术范围内，可轻易想到变化或替换，都应涵盖在本公开的保护范围之内。因此，本公开的保护范围应以权利要求的保护范围为准。
应当说明的时，上述上行调度指示可以为一个可以为多个，在此不作进一步的限定。

Claims (60)

  1. 一种数据传输方法，包括：
    建立空口信令连接前，向网络侧设备发送携带有状态迁移数据的数据消息；
    接收网络侧设备对数据消息返回的应答消息，所述应答消息携带有数据发送指示；
    当所述数据发送指示为发送时，向所述网络侧设备发送上行数据包。
  2. 根据权利要求1所述的方法，其中，当所述数据消息为随机接入请求消息，且所述应答消息为随机接入应答消息时，所述向所述网络侧设备发送上行数据包的步骤，包括：
    在所述随机接入应答消息携带的上行调度指示所指示的时频域位置发送上行数据包；
    或者，在默认的物理信道上向所述网络侧设备发送上行数据包。
  3. 根据权利要求2所述的方法，其中，所述随机接入应答消息携带有用于指示所述上行数据包发送方式的选择标识。
  4. 根据权利要求2所述的方法，其中，所述接收网络侧设备对数据消息返回的应答消息，所述应答消息携带有数据发送指示的步骤之后，所述方法还包括：
    当所述数据发送指示为不发送时，在所述上行调度指示所指示的时频域位置发送初始无线资源控制协议消息。
  5. 根据权利要求2所述的方法，其中，所述状态迁移数据包括数据发送标识；所述数据发送标识包括所述随机接入请求消息携带的标识符或者所述随机接入请求消息携带的随机前导序列。
  6. 根据权利要求5所述的方法，其中，所述随机前导序列包括用于标识发送的第一类随机前导序列和用于标识不发送的第二类随机前导序列。
  7. 根据权利要求6所述的方法，其中，所述随机前导序列中添加用于表示是否需要发送的标识位。
  8. 根据权利要求2所述的方法，其中，所述向网络侧设备发送携带有状 态迁移数据的数据消息的步骤之前，所述方法还包括：
    获取所述上行数据包的业务特征信息；
    根据所述业务特征信息，确定是否需要进行数据发送；
    其中，所述数据消息携带的状态迁移数据为：确定是否需要进行数据发送的结果。
  9. 根据权利要求2所述的方法，其中，所述状态迁移数据包括业务特征信息，其中，所述业务特征信息用于所述网络侧设备根据所述业务特征信息确定是否需要进行数据发送；
    或者所述网络侧设备根据所述业务特征信息和网络侧设备获取的网络侧信息确定是否需要进行数据发送。
  10. 根据权利要求9所述的方法，其中，所述网络侧信息包括网络侧负载状态、终端的签约数据和运营商配置数据中的至少一项。
  11. 根据权利要求8或9所述的方法，其中，所述业务特征信息包括：业务类型、业务缓存信息、业务服务质量要求和业务优先级中的至少一项。
  12. 根据权利要求11所述的方法，其中，所述业务缓存信息采用缓存量表示或者采用缓存等级表示；
    所述业务服务质量要求采用服务质量参数特征表示，或者采用对服务质量参数特征进行编组的编号表示，或者采用丢包率及最大允许时延表示。
  13. 根据权利要求2所述的方法，其中，所述上行数据包中携带有用于标识上行数据包是否发送完成的完成标识；所述当所述数据发送指示为发送时，在空口信令连接前向所述网络侧设备发送上行数据包的步骤之后，所述方法还包括：
    接收网络侧设备根据所述上行数据包接收状态和完成标识回复的反馈消息；
    当所述反馈消息标识为接收成功时，则停止发送所述上行数据包或者建立空口信令连接；
    当所述反馈消息标识为接收失败时，在所述反馈消息携带的重新确定的上行调度指示所指示的时频域位置重新发送上行数据包，或者根据所述反馈消息携带的允许连接消息建立空口信令连接。
  14. 根据权利要求13所述的方法，其中，所述网络侧设备根据所述上行数据包接收状态和完成标识回复的反馈消息包括：
    当上行数据包接收成功时，若完成标识为完成，则所述反馈消息携带有用于取消初始无线资源控制协议的拒绝消息；若完成标识为未完成，则所述反馈消息携带有用于建立初始无线资源控制协议的允许连接消息。
  15. 根据权利要求13所述的方法，其中，所述在所述随机接入应答消息携带的上行调度指示所指示的时频域位置发送上行数据包的步骤，包括：
    将所述上行数据包放置在媒体接入控制层数据包中，在所述上行调度指示所指示的时频域位置发送；
    或者将所述上行数据包放置在媒体接入控制层数据包内的无线资源控制协议层信令中，在所述上行调度指示所指示的时频域位置发送；
    或者将所述上行数据包作为媒体接入控制层数据包，在所述上行调度指示所指示的时频域位置发送。
  16. 根据权利要求15所述的方法，其中，所述将所述上行数据包放置在媒体接入控制层数据包内的无线资源控制协议层信令中包括：将所述上行数据包放置在初始无线资源控制协议消息中，且配置所述初始无线资源控制协议消息的连接原因为上行数据包发送。
  17. 一种数据传输方法，包括：
    接收终端在建立空口信令连接前所发送的携带有状态迁移数据的数据消息；
    基于所述数据消息，向所述终端返回应答消息，所述应答消息携带有数据发送指示；
    接收终端在所述数据发送指示为发送时所发送的上行数据包。
  18. 根据权利要求17所述的方法，其中，当所述数据消息为随机接入请求消息，且所述应答消息为随机接入应答消息时，接收终端在所述数据发送指示为发送时所发送的上行数据包步骤，包括：
    接收终端在所述随机接入应答消息携带的上行调度指示所指示的时频域位置所发送的上行数据包；
    或者，接收终端在默认的物理信道上所发送的上行数据包。
  19. 根据权利要求18所述的方法，其中，所述随机接入应答消息携带有用于指示所述上行数据包发送方式的选择标识。
  20. 根据权利要求18所述的方法，其中，所述状态迁移数据包括数据发送标识，所述基于数据消息向所述终端返回应答消息的步骤之前，还包括：
    根据所述随机接入请求消息携带的数据发送标识，确定是否需要进行数据发送；
    或者根据所述随机接入请求消息携带的数据发送标识和获取的网络侧信息，确定是否需要进行数据发送。
  21. 根据权利要求20所述的方法，其中，所述数据发送标识包括所述随机接入请求消息携带的标识符或者所述随机接入请求消息携带的随机前导序列。
  22. 根据权利要求21所述的方法，其中，当所述数据发送标识包括所述随机接入请求消息携带的随机前导序列时，所述随机前导序列包括用于标识发送的第一类随机前导序列和用于标识不发送的第二类随机前导序列。
  23. 根据权利要求21所述的方法，其中，当所述数据发送标识包括所述随机接入请求消息携带的随机前导序列时，所述随机前导序列中添加用于表示是否需要发送的标识位。
  24. 根据权利要求18所述的方法，其中，所述状态迁移数据包括业务特征信息，所述基于所述数据消息，向所述终端返回应答消息的步骤之前，所述方法还包括：
    根据所述随机接入请求消息携带的业务特征信息，确定是否需要进行数据发送；
    或者根据所述随机接入请求消息携带的业务特征信息和获取的网络侧信息，确定是否需要进行数据发送。
  25. 根据权利要求24所述的方法，其中，所述业务特征信息包括：业务类型、业务缓存信息、业务服务质量要求和业务优先级中的至少一项。
  26. 根据权利要求25所述的方法，其中，所述业务缓存信息采用缓存量表示或者采用缓存等级表示；
    所述业务服务质量要求采用服务质量参数特征表示，或者采用对服务质 量参数特征进行编组的编号表示，或者采用丢包率及最大允许时延表示。
  27. 根据权利要求20或24所述的方法，其中，所述网络侧信息包括网络侧负载状态、终端的签约数据和运营商配置数据中的至少一项。
  28. 根据权利要求18所述的方法，其中，所述接收终端在所述数据发送指示为发送时，所发送的上行数据包的步骤之后，所述方法还包括：
    当所述上行数据包接收成功时，向所述终端发送接收成功的反馈消息，将接收到的数据包向核心网发送；
    当所述上行数据包接收失败时，向所述终端发送接收失败的反馈消息，所述反馈消息携带有重新确定的上行调度指示或者用于触发所述终端建立连接的允许连接消息。
  29. 根据权利要求28所述的方法，其中，所述上行数据包中携带有用于标识上行数据包是否发送完成的完成标识；
    当接收的上行数据包位于初始无线资源控制协议消息中、且上行数据包接收成功时，若完成标识为完成，则所述反馈消息携带有用于取消初始无线资源控制协议的拒绝消息；若完成标识为未完成，则所述反馈消息携带有用于建立初始无线资源控制协议的允许连接消息。
  30. 一种终端，包括：
    数据消息发送模块，用于建立空口信令连接前，向网络侧设备发送携带有状态迁移数据的数据消息；
    应答消息接收模块，用于接收网络侧设备对数据消息返回的应答消息，所述应答消息携带有数据发送指示；
    数据包发送模块，用于当所述数据发送指示为发送时，向所述网络侧设备发送上行数据包。
  31. 根据权利要求30所述的终端，其中，所述数据包发送模块具体用于，当所述数据消息为随机接入请求消息，且所述应答消息为随机接入应答消息时，在所述随机接入应答消息携带的上行调度指示所指示的时频域位置发送上行数据包；或者，在默认的物理信道上向所述网络侧设备发送上行数据包。
  32. 根据权利要求31所述的终端，其中，所述随机接入应答消息携带有用于指示所述上行数据包发送方式的选择标识。
  33. 根据权利要求31所述的终端，其中，所述终端还包括：
    协议消息发送模块，用于当所述数据发送指示为不发送时，在所述上行调度指示所指示的时频域位置发送初始无线资源控制协议消息。
  34. 根据权利要求31所述的终端，其中，所述状态迁移数据包括数据发送标识；所述数据发送标识包括所述随机接入请求消息携带的标识符或者所述随机接入请求消息携带的随机前导序列。
  35. 根据权利要求34所述的终端，其中，所述随机前导序列包括用于标识发送的第一类随机前导序列和用于标识不发送的第二类随机前导序列。
  36. 根据权利要求35所述的终端，其中，所述随机前导序列中添加用于表示是否需要发送的标识位。
  37. 根据权利要求31所述的终端，其中，所述终端还包括：
    获取模块，用于获取所述上行数据包的业务特征信息；
    第一确定模块，用于根据所述业务特征信息，确定是否需要进行数据发送；
    其中，所述数据消息携带的状态迁移数据为：确定是否需要进行数据发送的结果。
  38. 根据权利要求31所述的终端，其中，所述状态迁移数据包括业务特征信息，其中，所述业务特征信息用于所述网络侧设备根据所述业务特征信息确定是否需要进行数据发送；
    或者所述网络侧设备根据所述业务特征信息和网络侧设备获取的网络侧信息确定是否需要进行数据发送。
  39. 根据权利要求38所述的终端，其中，所述网络侧信息包括网络侧负载状态、终端的签约数据和运营商配置数据中的至少一项。
  40. 根据权利要求37或38所述的终端，其中，所述业务特征信息包括：业务类型、业务缓存信息、业务服务质量要求和业务优先级中的至少一项。
  41. 根据权利要求40所述的终端，其中，所述业务缓存信息采用缓存量表示或者采用缓存等级表示；
    所述业务服务质量要求采用服务质量参数特征表示，或者采用对服务质量参数特征进行编组的编号表示，或者采用丢包率及最大允许时延表示。
  42. 根据权利要求31所述的终端，其中，所述上行数据包中携带有用于标识上行数据包是否发送完成的完成标识；所述终端还包括：
    反馈消息接收模块，用于接收网络侧设备根据所述上行数据包接收状态和完成标识回复的反馈消息；
    控制模块，用于当所述反馈消息标识为接收成功时，则停止发送所述上行数据包或者建立空口信令连接；当所述反馈消息标识为接收失败时，在所述反馈消息携带的重新确定的上行调度指示所指示的时频域位置重新发送上行数据包，或者根据所述反馈消息携带的允许连接消息建立空口信令连接。
  43. 根据权利要求42所述的终端，其中，当上行数据包接收成功时，若完成标识为完成，则所述反馈消息携带有用于取消初始无线资源控制协议的拒绝消息；若完成标识为未完成，则所述反馈消息携带有用于建立初始无线资源控制协议的允许连接消息。
  44. 根据权利要求42所述的终端，其中，所述数据包发送模块具体用于：
    将所述上行数据包放置在媒体接入控制层数据包中，在所述上行调度指示所指示的时频域位置发送；
    或者将所述上行数据包放置在媒体接入控制层数据包内的无线资源控制协议层信令中，在所述上行调度指示所指示的时频域位置发送；
    或者将所述上行数据包作为媒体接入控制层数据包，在所述上行调度指示所指示的时频域位置发送。
  45. 根据权利要求44所述的终端，其中，所述数据包发送模块具体用于：将所述上行数据包放置在初始无线资源控制协议消息中，且配置所述初始无线资源控制协议消息的连接原因为上行数据包发送。
  46. 一种网络侧设备，包括：
    数据消息接收模块，用于接收终端在建立空口信令连接前所发送的携带有状态迁移数据的数据消息；
    应答消息发送模块，用于基于所述数据消息，向所述终端返回应答消息，所述应答消息携带有数据发送指示；
    数据包接收模块，用于接收终端在所述数据发送指示为发送时所发送的上行数据包。
  47. 根据权利要求46所述的网络侧设备，其中，所述数据包接收模块具体用于：
    当所述数据消息为随机接入请求消息，且所述应答消息为随机接入应答消息时，接收终端在所述随机接入应答消息携带的上行调度指示所指示的时频域位置所发送的上行数据包；
    或者，接收终端在默认的物理信道上所发送的上行数据包。
  48. 根据权利要求47所述的网络侧设备，其中，所述随机接入应答消息携带有用于指示所述上行数据包发送方式的选择标识。
  49. 根据权利要求47所述的网络侧设备，其中，所述网络侧设备还包括：
    第二确定模块，用于根据所述随机接入请求消息携带的数据发送标识，确定是否需要进行数据发送；
    或者根据所述随机接入请求消息携带的数据发送标识和获取的网络侧信息，确定是否需要进行数据发送。
  50. 根据权利要求49所述的网络侧设备，其中，所述数据发送标识包括所述随机接入请求消息携带的标识符或者所述随机接入请求消息携带的随机前导序列。
  51. 根据权利要求50所述的网络侧设备，其中，当所述数据发送标识包括所述随机接入请求消息携带的随机前导序列时，所述随机前导序列包括用于标识发送的第一类随机前导序列和用于标识不发送的第二类随机前导序列。
  52. 根据权利要求50所述的网络侧设备，其中，当所述数据发送标识包括所述随机接入请求消息携带的随机前导序列时，所述随机前导序列中添加用于表示是否需要发送的标识位。
  53. 根据权利要求47所述的网络侧设备，其中，所述网络侧设备还包括：
    第三确定模块，用于根据所述随机接入请求消息携带的业务特征信息，确定是否需要进行数据发送；或者根据所述随机接入请求消息携带的业务特征信息和获取的网络侧信息，确定是否需要进行数据发送。
  54. 根据权利要求53所述的网络侧设备，其中，所述业务特征信息包括：业务类型、业务缓存信息、业务服务质量要求和业务优先级中的至少一项。
  55. 根据权利要求54所述的网络侧设备，其中，所述业务缓存信息采用 缓存量表示或者采用缓存等级表示；
    所述业务服务质量要求采用服务质量参数特征表示，或者采用对服务质量参数特征进行编组的编号表示，或者采用丢包率及最大允许时延表示。
  56. 根据权利要求49或53所述的网络侧设备，其中，所述网络侧信息包括网络侧负载状态、终端的签约数据和运营商配置数据中的至少一项。
  57. 根据权利要求47所述的网络侧设备，其中，所述网络侧设备还包括：
    处理模块，用于当所述上行数据包接收成功时，向所述终端发送接收成功的反馈消息，将接收到的数据包向核心网发送；
    反馈消息发送模块，用于当所述上行数据包接收失败时，向所述终端发送接收失败的反馈消息，所述反馈消息携带有重新确定的上行调度指示或者用于触发所述终端建立连接的允许连接消息。
  58. 根据权利要求57所述的网络侧设备，其中，所述上行数据包中携带有用于标识上行数据包是否发送完成的完成标识；
    当接收的上行数据包位于初始无线资源控制协议消息中、且上行数据包接收成功时，若完成标识为完成，则所述反馈消息携带有用于取消初始无线资源控制协议的拒绝消息；若完成标识为未完成，则所述反馈消息携带有用于建立初始无线资源控制协议的允许连接消息。
  59. 一种移动终端，包括：存储器、处理器及存储在所述存储器上并可在所述处理器上运行的计算机程序，所述处理器执行所述计算机程序时实现如权利要求1至16中任一项所述的数据传输方法的步骤。
  60. 一种网络侧设备，包括：存储器、处理器及存储在所述存储器上并可在所述处理器上运行的计算机程序，所述处理器执行所述计算机程序时实现如权利要求17至29中任一项所述的数据传输方法的步骤。
PCT/CN2017/108642 2016-11-04 2017-10-31 一种数据传输方法、终端及网络侧设备 WO2018082548A1 (zh)

Priority Applications (4)

Application Number Priority Date Filing Date Title
EP17868241.5A EP3537840B1 (en) 2016-11-04 2017-10-31 Data transmission method, terminal and network-side device
US16/346,868 US11013026B2 (en) 2016-11-04 2017-10-31 Data transmission method, terminal and network-side device
ES17868241T ES2926392T3 (es) 2016-11-04 2017-10-31 Método de transmisión de datos, terminal y dispositivo del lado de la red
US17/227,594 US11546932B2 (en) 2016-11-04 2021-04-12 Data transmission method, terminal and network side device

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201610964285.XA CN108377580A (zh) 2016-11-04 2016-11-04 一种数据传输方法、终端及网络侧设备
CN201610964285.X 2016-11-04

Related Child Applications (2)

Application Number Title Priority Date Filing Date
US16/346,868 A-371-Of-International US11013026B2 (en) 2016-11-04 2017-10-31 Data transmission method, terminal and network-side device
US17/227,594 Division US11546932B2 (en) 2016-11-04 2021-04-12 Data transmission method, terminal and network side device

Publications (1)

Publication Number Publication Date
WO2018082548A1 true WO2018082548A1 (zh) 2018-05-11

Family

ID=62075688

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2017/108642 WO2018082548A1 (zh) 2016-11-04 2017-10-31 一种数据传输方法、终端及网络侧设备

Country Status (7)

Country Link
US (2) US11013026B2 (zh)
EP (1) EP3537840B1 (zh)
CN (1) CN108377580A (zh)
ES (1) ES2926392T3 (zh)
HU (1) HUE059870T2 (zh)
PT (1) PT3537840T (zh)
WO (1) WO2018082548A1 (zh)

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN110858987A (zh) * 2018-08-24 2020-03-03 中兴通讯股份有限公司 一种数据传输方法、装置、设备及计算机可读介质
CN111800824A (zh) * 2020-05-28 2020-10-20 上海诺行信息技术有限公司 智能仪表的数据传输系统、驱动接口封装装置及方法

Families Citing this family (9)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US8404967B2 (en) 2008-01-08 2013-03-26 Certainteed Corporation Photovoltaic module
CN108377580A (zh) * 2016-11-04 2018-08-07 维沃移动通信有限公司 一种数据传输方法、终端及网络侧设备
US10805434B2 (en) 2017-06-08 2020-10-13 Hyannis Port Research, Inc. Dynamic TCP stream processing with modification notification
WO2019056271A1 (zh) * 2017-09-21 2019-03-28 北京小米移动软件有限公司 网络连接方法及装置
EP3506547A1 (en) * 2017-12-28 2019-07-03 Flytxt B.V. Providing security against user collusion in data analytics using random group selection
CN110149718B (zh) * 2018-02-14 2022-03-29 华为技术有限公司 数据发送的方法和通信设备
CN111277658A (zh) * 2020-01-21 2020-06-12 神华神东电力有限责任公司 数据传输方法及远端数据中心
CN113207173B (zh) * 2020-02-01 2022-11-25 上海朗帛通信技术有限公司 一种被用于无线通信的通信节点中的方法和装置
US11622388B2 (en) * 2021-03-08 2023-04-04 Nokia Technologies Oy Energy efficient, RRC state aware uplink radio resource allocation

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20120287877A1 (en) * 2009-11-23 2012-11-15 Lg Electronics Inc. Method and Apparatus for Performing Contention-Based Uplink Transmission in a Wireless Communication System
CN102892192A (zh) * 2011-07-20 2013-01-23 中兴通讯股份有限公司 一种多定时组下的初始接入方法、装置及系统
WO2014056426A1 (zh) * 2012-10-08 2014-04-17 联发科技（新加坡）私人有限公司 数据传输方法
WO2015129985A1 (ko) * 2014-02-28 2015-09-03 엘지전자(주) 무선 통신 시스템에서 낮은 지연을 가지는 상향링크 데이터 전송 방법 및 장치

Family Cites Families (10)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101411095B (zh) * 2006-03-28 2013-06-19 三星电子株式会社 用于移动通信系统中的连接终端的非连续接收的方法和设备
CN102170677B (zh) * 2010-02-25 2013-08-14 电信科学技术研究院 一种传输请求消息的方法、系统和装置
KR20110113484A (ko) * 2010-04-09 2011-10-17 주식회사 팬택 다중 반송파 시스템에서 랜덤 액세스의 수행장치 및 방법
US9042326B2 (en) * 2010-06-24 2015-05-26 Lg Electronics Inc. Method and device for transmitting uplink data in wireless connection system
JP4923161B1 (ja) * 2010-09-29 2012-04-25 シャープ株式会社 移動通信システム、移動局装置、基地局装置、通信方法および集積回路
KR102023016B1 (ko) * 2011-06-28 2019-09-19 엘지전자 주식회사 상향링크 신호 전송/수신 방법 및 장치와, 하향링크 신호 전송/수신 방법 및 장치
CN104105214B (zh) * 2013-04-01 2017-08-18 电信科学技术研究院 一种数据传输方法及装置
CN105636207A (zh) * 2014-10-28 2016-06-01 电信科学技术研究院 一种传输上行数据的方法和设备
CN110691429B (zh) 2016-05-13 2021-02-12 华为技术有限公司 Rrc状态的控制方法和装置
CN108377580A (zh) * 2016-11-04 2018-08-07 维沃移动通信有限公司 一种数据传输方法、终端及网络侧设备

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20120287877A1 (en) * 2009-11-23 2012-11-15 Lg Electronics Inc. Method and Apparatus for Performing Contention-Based Uplink Transmission in a Wireless Communication System
CN102892192A (zh) * 2011-07-20 2013-01-23 中兴通讯股份有限公司 一种多定时组下的初始接入方法、装置及系统
WO2014056426A1 (zh) * 2012-10-08 2014-04-17 联发科技（新加坡）私人有限公司 数据传输方法
WO2015129985A1 (ko) * 2014-02-28 2015-09-03 엘지전자(주) 무선 통신 시스템에서 낮은 지연을 가지는 상향링크 데이터 전송 방법 및 장치

Non-Patent Citations (1)

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

Cited By (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN110858987A (zh) * 2018-08-24 2020-03-03 中兴通讯股份有限公司 一种数据传输方法、装置、设备及计算机可读介质
CN110858987B (zh) * 2018-08-24 2022-09-30 中兴通讯股份有限公司 一种数据传输方法、装置、设备及计算机可读介质
CN111800824A (zh) * 2020-05-28 2020-10-20 上海诺行信息技术有限公司 智能仪表的数据传输系统、驱动接口封装装置及方法

Also Published As

Publication number Publication date
PT3537840T (pt) 2022-09-08
EP3537840B1 (en) 2022-08-10
CN108377580A (zh) 2018-08-07
EP3537840A4 (en) 2019-10-16
ES2926392T3 (es) 2022-10-25
US11546932B2 (en) 2023-01-03
US20190289620A1 (en) 2019-09-19
US20210235472A1 (en) 2021-07-29
US11013026B2 (en) 2021-05-18
HUE059870T2 (hu) 2023-01-28
EP3537840A1 (en) 2019-09-11

Similar Documents

Publication Publication Date Title
WO2018082548A1 (zh) 一种数据传输方法、终端及网络侧设备
EP3541127B1 (en) Downlink packet transmission method and device
US11096200B2 (en) Methods, devices and systems for device to device (D2D) data transmission and retransmission
CN110169194B (zh) 用于非活动状态的配置信息
CN108347779B (zh) 上行数据发送方法、接收方法、用户终端和网络侧设备
US11930523B2 (en) Data transmission method and terminal device
KR102371187B1 (ko) 제어 시그널링을 전송하는 방법, 기지국 및 단말기
US11647482B2 (en) Method and device for selecting grant-free and grant-based uplink transmission
EP3490304B1 (en) Method for identifying access point and hotspot, and related products
KR20220010450A (ko) 뉴 라디오 차량 대 사물에서 자원 선택을 위한 사용자 장비 지원
US9838313B2 (en) Method, system, control device and node device for data transmission
EP3113401B1 (en) Information transmission method and device
WO2022017354A1 (zh) Pdcch的校验方法、发送方法、终端及网络侧设备
US10237861B2 (en) Information transmission method, device, and system
CN108811162B (zh) 一种系统信息传输方法、终端及基站
CN113747559B (zh) 功率余量的上报方法、装置、终端及可读存储介质
JP7367553B2 (ja) 通信装置及びプログラム
WO2023061345A1 (zh) 数据接收方法、数据发送方法及终端
WO2023185819A1 (zh) Pdcch监听方法、终端、网络侧设备及介质
WO2023011309A1 (zh) 反馈方法、相关设备及可读存储介质
WO2022152039A1 (zh) 上行数据发送方法、配置方法、终端及网络侧设备
JP6931535B2 (ja) 通信制御装置
KR20230045043A (ko) 타겟 자원 유형의 결정 방법, 타겟 자원 유형의 결정 장치 및 통신 장치
KR20230006508A (ko) 다중 자원 경합에 대한 처리 방법 및 단말 디바이스
JP2024514145A (ja) Ｒｒｃ接続維持方法、関連機器及び可読記憶媒体

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: 17868241

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: 2017868241

Country of ref document: EP

Effective date: 20190604