WO2017107093A1 - 一种rrc连接释放方法、装置及设备 - Google Patents

一种rrc连接释放方法、装置及设备 Download PDF

Info

Publication number
WO2017107093A1
WO2017107093A1 PCT/CN2015/098406 CN2015098406W WO2017107093A1 WO 2017107093 A1 WO2017107093 A1 WO 2017107093A1 CN 2015098406 W CN2015098406 W CN 2015098406W WO 2017107093 A1 WO2017107093 A1 WO 2017107093A1
Authority
WO
WIPO (PCT)
Prior art keywords
sent
base station
timer
message
rrc
Prior art date
Application number
PCT/CN2015/098406
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 CN201580085258.9A priority Critical patent/CN108370605B/zh
Priority to EP15911092.3A priority patent/EP3383126B1/en
Priority to PCT/CN2015/098406 priority patent/WO2017107093A1/zh
Publication of WO2017107093A1 publication Critical patent/WO2017107093A1/zh
Priority to US16/015,867 priority patent/US10694576B2/en

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/30—Connection release
    • H04W76/38—Connection release triggered by timers
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/30—Connection release
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L47/00—Traffic control in data switching networks
    • H04L47/10—Flow control; Congestion control
    • H04L47/28—Flow control; Congestion control in relation to timing considerations
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L5/00—Arrangements affording multiple use of the transmission path
    • H04L5/003—Arrangements for allocating sub-channels of the transmission path
    • H04L5/0053—Allocation of signaling, i.e. of overhead other than pilot signals
    • H04L5/0055—Physical resource allocation for ACK/NACK
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W28/00—Network traffic management; Network resource management
    • H04W28/02—Traffic management, e.g. flow control or congestion control
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W28/00—Network traffic management; Network resource management
    • H04W28/02—Traffic management, e.g. flow control or congestion control
    • H04W28/0278—Traffic management, e.g. flow control or congestion control using buffer status reports
    • 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
    • H04W88/00—Devices specially adapted for wireless communication networks, e.g. terminals, base stations or access point devices
    • H04W88/02—Terminal devices

Definitions

  • the present invention relates to the field of communications technologies, and in particular, to an RRC connection release method, apparatus, and device.
  • the User Equipment has two Radio Resource Control (RRC) states in the air interface: idle state (IDLE) and connected state (Connected).
  • RRC Radio Resource Control
  • IDLE idle state
  • Connected connected state
  • the UE When the UE needs to perform service transmission, it first needs to establish a connection with the network side device, that is, the RRC connection is established, and the UE enters the connected state from the idle state, and then performs the transmission of the service data. After the UE completes the service data transmission, if the UE in the connected state has no data transmission for a long time, the inactivity timer expires, and the UE needs to release the RRC connection with the network side device, that is, the RRC connection is released, and the UE enters from the connected state. To the idle state.
  • the UE When there is downlink data arrival or uplink data arrives, the UE needs to re-establish the RRC connection, and after the data transmission is completed, if the UE does not have data transmission for a long time, the inactivity timer expires, the UE needs to release the RRC connection, and therefore, the UE needs to release the RRC connection.
  • the air interface state transition process more signaling overhead is generated during the transition between the idle state and the connected state.
  • CIoT Cellular Internet of Things
  • LTE Long Term Evolution
  • the UE After the UE completes the data transmission, if the UE has no data transmission for a long time, the inactivity timer expires, the UE releases the RRC connection, and saves the context information of the current connection, but still causes a large amount of signaling overhead during the RRC connection release process.
  • An embodiment of the present invention provides an RRC connection release method, apparatus, and device, which are used to solve the problem that a large number of signalings are required in an RRC connection release procedure, resulting in a heavy network load.
  • an RRC connection release method includes:
  • the user equipment UE sends a first message to the base station, where the first message carries a preset RRC release time determination parameter or a first RRC release time;
  • the UE If the UE carries the first RRC release time in the first message, the UE sets a timing duration of the first timer according to the first RRC release time, and starts the first timer; or If the UE carries the preset RRC release time determination parameter in the first message, the UE receives a response message that the base station feeds back to the first message, where the response message carries the Determining, by the base station, a second RRC release time determined by the parameter according to the preset RRC release time; the UE setting a timing duration of the first timer according to the second RRC release time, and starting the first timer ;
  • the UE releases the RRC connection when the first timer expires.
  • the preset RRC release time determining parameter is a data volume of the uplink data to be sent by the UE, and/or the uplink data to be sent. Estimated time to send.
  • the second in the first aspect in combination with the first aspect or the first possible implementation of the first aspect, the second in the first aspect, the UE further includes:
  • the UE reports a buffer status report BSR to the base station, where the BSR is used to indicate that the base station adjusts a timing duration of the second timer, where the timing duration of the second timer is that the base station according to the UE
  • the first message sent is set;
  • an RRC connection release method includes:
  • the base station Receiving, by the base station, the first message sent by the UE, where the first message carries a preset RRC release time determination parameter or a first RRC release time;
  • the base station determines that the first message carries the first RRC release time, the base station sets a timing duration of the second timer according to the first RRC release time, and starts the second timer; or If the base station determines that the first message carries the preset RRC release time determination parameter, the base station determines a second RRC release time according to the preset RRC release time determination parameter, and The response message sent by the message to the UE carries the second RRC release time; the base station sets the timing duration of the second timer according to the second RRC release time, and starts the second timer ;
  • the base station releases an RRC connection with the UE when the second timer expires.
  • the preset RRC release time determining parameter is a data volume of the uplink data to be sent by the UE, and/or the uplink data to be sent. Estimated time to send.
  • the base station before the second timer expires, further includes:
  • the base station receives the BSR reported by the UE, and adjusts the timing duration of the second timer according to the BSR;
  • the base station generates a first adjustment indication to return to the UE according to the timing adjustment result of the second timer, and generates a second adjustment indication notification to the mobility management entity MME.
  • the third in the second aspect after the base station feeds back the response message to the UE, the method further includes:
  • the base station After receiving the acknowledgement message sent by the UE for the response message, the base station sends an S1 connection recovery indication information to the MME, where the S1 connection recovery indication information carries the second timer;
  • the base station determines that the S1 connection between the base station and the MME has been restored according to the confirmation indication information of the S1 connection recovery.
  • an RRC connection release method includes:
  • the mobility management entity MME receives the S1 connection recovery indication information sent by the base station, where the S1 connection recovery indication information carries a timing duration of the second timer, where the timing duration of the second timer is sent by the base station according to the UE.
  • the first message carries a preset RRC release time determination parameter or a first RRC release time;
  • the MME determines that the UE releases the RRC connection.
  • the method further includes:
  • the MME sends an acknowledgement indication information of the S1 connection recovery to the base station.
  • the MME before the third timer expires, the MME further includes:
  • the MME receives the second adjustment indication sent by the base station, adjusting a timing duration of the third timer according to the second adjustment indication.
  • an RRC connection release method includes:
  • the UE sends a first message to the base station, where the first message carries indication information about whether the UE needs to receive downlink data.
  • the UE When the UE does not need to receive the downlink data, the UE sends the uplink data to be sent to the base station, and carries the endpoint tag Endmarker indication packet in the last uplink data packet, after the UE sends the last uplink data packet. And releasing the RRC connection; and/or, when the UE needs to receive downlink data, after receiving the uplink data to be sent, receiving the downlink data, and releasing the Endmarker indication packet after parsing the received downlink data packet, releasing RRC connection.
  • the UE carries an Endmarker indication packet on a packet data convergence protocol PDCP header of a last uplink data packet to be sent uplink data.
  • an RRC connection release method includes:
  • the base station determines that the indication information indicates that the UE does not need to receive downlink data, and receives the uplink data to be sent sent by the UE, and after the parsing into the received uplink data packet, including the Endmarker indication packet, releasing the RRC connection between UEs; and/or
  • the base station Determining, by the base station, that the indication information indicates that the UE needs to receive downlink data, and after the UE sends the uplink data to be sent, the downlink data is continuously sent to the UE, and is sent to the last downlink data.
  • the base station releases the RRC connection with the UE.
  • the method further includes:
  • the base station After the base station determines that the indication information indicates that the UE does not need to receive downlink data, after parsing the Endmarker indication packet in the uplink data to be sent sent by the UE, the base station will be in the uplink to be sent. Carrying the Endmarker indication packet to the serving gateway S-GW on the GTP header of the last packet of the last uplink data packet of the data; and/or
  • the base station When the indication information indicates that the UE needs to receive downlink data, the base station carries an Endmarker indication packet in the last downlink data packet, including:
  • the base station will carry the Endmarker indication packet on the PDCP header of the last downlink data packet.
  • an RRC connection release method includes:
  • the UE reports an application message to the network side device, where the application message carries an application layer protocol type of the UE;
  • the UE After the UE completes all data packets that need to be exchanged for the application layer protocol type, the UE releases the RRC connection.
  • the application layer protocol type is a transmission control protocol and a hypertext transfer protocol, TCP/HTTP, or a user datagram protocol, UDP.
  • an RRC connection release method includes:
  • the network side device receives an application message reported by the UE, where the application message carries an application layer protocol type of the UE;
  • the network side device determines that the number of recorded data packets reaches the number of transport data packets corresponding to the application layer protocol type, the network side device releases an RRC connection with the UE.
  • an RRC connection release apparatus includes:
  • a first sending unit configured to send a first message to the base station, where the first message carries a preset RRC release time determination parameter or a first RRC release time;
  • a first processing unit configured to: when the first RRC release time is carried in the first message, set a timing duration of the first timer according to the first RRC release time, and start the first timer; Or the first receiving unit is configured to receive a response message that is sent by the base station to the first message, where the response message carries the base station according to the preset RRC release time. a second RRC release time determined by the parameter, the first processing unit, configured to set the first RRC release time determining parameter according to the second RRC release time when the first message carries the preset RRC release time determination parameter a timing duration of a timer, and starting the first timer;
  • the first determining unit is configured to release the RRC connection when the first timer expires.
  • the preset RRC release time determining parameter is a data volume of the device to send uplink data and/or the uplink data to be sent Estimated time to send.
  • the first sending unit is further configured to report a BSR to the base station, where the BSR is used to instruct the base station to adjust a timing duration of the second timer, where a timing duration of the second timer is the base station Set according to the first message sent by the UE;
  • the first receiving unit is further configured to receive a first adjustment indication that is sent back by the base station;
  • the first processing unit is further configured to: when receiving the first adjustment indication returned by the base station, adjust a timing duration of the first timer according to the first adjustment indication.
  • an RRC connection release apparatus comprising:
  • a second receiving unit configured to receive a first message sent by the UE, where the first message carries a preset RRC release time determination parameter or a first RRC release time;
  • a second processing unit configured to determine a timing duration of the second timer according to the first RRC release time when the first RRC release time is carried in the first message, and start the second timer; Or the second processing unit is configured to determine that the preset RRC release time determination parameter is carried in the first message, and determine a second RRC release time according to the preset RRC release time determination parameter, and Setting a second RRC release time, setting a timing duration of the second timer, and starting the second timer; the second sending unit, configured to send a response message to the UE for the first message, where Carrying the second RRC release time in the response message;
  • a second determining unit configured to: when the second timer expires, the base station releases an RRC connection with the UE.
  • the preset RRC release time determining parameter is a data quantity of the uplink data to be sent by the UE, and/or the uplink data to be sent Estimated time to send.
  • the method further includes:
  • the second receiving unit is further configured to receive a BSR reported by the UE;
  • the second processing unit is further configured to: when receiving the BSR reported by the UE, adjust a timing duration of the second timer, and generate a first according to the timing duration adjustment result of the second timer Adjustment indication and second adjustment indication;
  • the second sending unit is further configured to: return the first adjustment indication to the UE, and notify the MME of the second adjustment indication.
  • the method further includes:
  • the second receiving unit is further configured to receive an acknowledgement message sent by the UE for the response message
  • the second sending unit is further configured to: after the second receiving unit receives the acknowledgement message sent by the UE for the response message, send the S1 connection recovery indication information to the MME, where the S1 connection recovery indication information Carrying a timing duration of the second timer;
  • the second receiving unit is further configured to receive the confirmation indication information of the S1 connection recovery sent by the MME;
  • the second processing unit is further configured to determine that the S1 connection between the base station and the MME has been restored according to the confirmation indication information of the S1 connection recovery.
  • an RRC connection release apparatus comprising:
  • a third receiving unit configured to receive, by the base station, the S1 connection recovery indication information, where the S1 connection recovery indication information carries a timing duration of the second timer, where the timing duration of the second timer is the base station according to the UE Set, by the first message sent, the first message carries a preset RRC release time determination parameter or a first RRC release time;
  • a third processing unit configured to set a timing duration of the third timer according to a timing duration of the second timer, and start the third timer
  • the third determining unit is configured to determine, when the third timer expires, that the UE releases the RRC connection.
  • the method further includes:
  • the third processing unit is configured to determine to restore an S1 connection with the base station according to the S1 connection recovery indication information
  • a third sending unit configured to send, to the base station, acknowledgement information of the S1 connection recovery.
  • the third receiving unit is further configured to receive a second adjustment indication sent by the base station;
  • the third processing unit is further configured to: when the third receiving unit receives the second adjustment indication sent by the base station, adjust a timing duration of the third timer according to the second adjustment indication.
  • an RRC connection release device comprising:
  • a fourth sending unit configured to send a first message to the base station, where the first message carries indication information about whether the UE needs to receive downlink data
  • a fourth sending unit configured to: when the fourth processing unit determines that the downlink data does not need to be received, send the uplink data to be sent to the base station, where the fourth processing unit is configured to carry the Endmarker indication packet in the last uplink data packet. And releasing the RRC connection after the fourth sending unit sends the last uplink data packet; and/or the fourth sending unit, when the fourth processing unit determines that the downlink data needs to be received, Sending uplink data to be sent to the base station, where the fourth receiving unit is configured to receive downlink data after the fourth processing unit determines that the uplink data transmission to be sent is completed, and the fourth processing unit is configured to analyze After the Endmarker indication packet is included in the downlink data packet received by the fourth receiving unit, the RRC connection is released.
  • the fourth processing unit is further configured to carry an Endmarker indication packet on a PDCP header of a last uplink data packet to be sent uplink data.
  • an RRC connection release apparatus includes:
  • a fifth receiving unit configured to receive a first message sent by the UE, where the first message carries indication information about whether the UE needs to receive downlink data;
  • a fifth receiving unit configured to: when the fifth processing unit determines that the indication information indicates that the UE does not need to receive downlink data, receive uplink data to be sent sent by the UE; Parsing that the uplink data packet received by the fifth receiving unit includes an Endmarker indication packet, releasing an RRC connection with the UE; and/or the fifth receiving unit, configured to be in the fifth processing unit Determining that the indication information indicates that the UE needs to receive downlink data, and the fifth sending unit is configured to continue to send downlink data to the device after the uplink data to be sent sent by the UE is received by the fifth receiving unit.
  • the fifth processing unit is configured to: when the fifth sending unit sends the last downlink data packet, carry an Endmarker indication packet in the last downlink data packet, and carry the Endmarker indication packet. After the last downlink data packet is sent to the UE, the RRC connection with the UE is released.
  • the method further includes:
  • the fifth processing unit is further configured to: after the indication information indicates that the UE does not need to receive downlink data, after parsing the Endmarker indication packet in the uplink data to be sent sent by the UE,
  • the General Packet Radio Service Technology Tunneling Protocol GTP header of the last uplink data packet to be sent uplink data carries the Endmarker indication packet to the serving gateway S-GW;
  • the Endmarker indication packet is carried in the last downlink data packet, and the fifth processing unit is further configured to:
  • the Endmarker indication packet will be carried on the PDCP header of the last downlink data packet.
  • an RRC connection release apparatus comprising:
  • a sixth sending unit configured to report an application message to a network side device, where the application message carries an application layer protocol type of the UE;
  • a sixth determining unit configured to complete the protocol type for the application layer with the network side device After all the packets that need to be exchanged, the RRC connection is released.
  • the application layer protocol type is a transmission control protocol and a hypertext transfer protocol TCP/HTTP, or a user datagram protocol UDP.
  • an RRC connection release apparatus includes:
  • a seventh receiving unit configured to receive an application message reported by the UE, where the application message carries an application layer protocol type of the UE;
  • a determining unit configured to determine, according to the application layer protocol type, a number of transport data packets corresponding to the application layer protocol type
  • a counting unit configured to receive and process a data packet transmitted by the UE for the application layer protocol type, and record the number of processed data packets
  • a seventh determining unit configured to release an RRC connection with the UE when determining that the number of recorded data packets reaches the number of transport data packets corresponding to the application layer protocol type.
  • an RRC connection release device includes:
  • a first transceiver configured to send a first message to the base station, where the first message carries a preset RRC release time determination parameter or a first RRC release time;
  • a first processor configured to: when the first RRC release time is carried in the first message, set a timing duration of the first timer according to the first RRC release time, and start the first timer; Or the first transceiver is configured to receive, when the first message carries the preset RRC release time determination parameter, a response message that is sent by the base station to the first message, where the response The message carries a second RRC release time determined by the base station according to the preset RRC release time determination parameter, and the first processor is configured to set a timing of the first timer according to the second RRC release time Duration, and start the first timer;
  • the first processor is further configured to release an RRC connection when the first timer expires.
  • the preset RRC release time determining parameter is an amount of data of the uplink data to be sent by the UE, and/or the to-be-sent Estimated time for sending upstream data.
  • the first transceiver is further configured to report a BSR to the base station
  • the BSR is configured to instruct the base station to adjust a timing duration of the second timer, where a timing duration of the second timer is set by the base station according to the first message sent by the UE; and receiving a first adjustment indication returned by the base station;
  • the first processor is further configured to: when receiving the first adjustment indication returned by the base station, adjust a timing duration of the first timer according to the first adjustment indication.
  • an RRC connection release device includes:
  • a second transceiver configured to receive a first message sent by the UE, where the first message carries a preset RRC release time determination parameter or a first RRC release time;
  • a second processor configured to determine a timing duration of the second timer according to the first RRC release time when the first RRC release time is carried in the first message, and start the second timer; Or the second processor is configured to determine that the preset RRC release time determination parameter is carried in the first message, and determine a second RRC release time according to the preset RRC release time determination parameter, and Setting a second RRC release time, setting a timing duration of the second timer, and starting the second timer; the second transceiver, configured to send a response message to the UE for the first message, where Carrying the second RRC release time in the response message;
  • the second processor is further configured to release an RRC connection with the UE when the second timer expires.
  • the method further includes:
  • the second transceiver is further configured to receive a BSR reported by the UE;
  • the second processor is further configured to: when the second transceiver receives the BSR reported by the UE, adjust a timing duration of the second timer, and according to the timing of the second timer The duration adjustment result generates a first adjustment indication and a second adjustment indication;
  • the second transceiver is further configured to: restore the first adjustment indication to the UE, and notify the MME of the second adjustment indication.
  • the second The transceiver is further configured to receive an acknowledgment message sent by the UE for the response message, and after receiving the acknowledgment message sent by the UE for the response message, send the S1 connection recovery indication information to the MME, where
  • the S1 connection recovery indication information carries the timing duration of the second timer; and the confirmation indication information of the S1 connection recovery sent by the MME is received;
  • the second processor is configured to determine that the S1 connection between the base station and the MME has been restored according to the confirmation indication information of the S1 connection recovery.
  • an RRC connection release device includes:
  • a third transceiver configured to receive the S1 connection recovery indication information sent by the base station, where the S1 connection recovery indication information carries a timing duration of the second timer, where the timing duration of the second timer is the base station according to the UE Set, by the first message sent, the first message carries a preset RRC release time determination parameter or a first RRC release time;
  • a third processor configured to set a timing duration of the third timer according to a timing duration of the second timer, and start the third timer
  • the method further includes:
  • the third processor is further configured to determine to restore an S1 connection with the base station according to the S1 connection recovery indication information
  • the third transceiver is further configured to send the confirmation indication information of the S1 connection recovery to the base station.
  • the third transceiver is configured to receive a second adjustment indication sent by the base station
  • the third processor is configured to adjust a timing duration of the third timer according to the second adjustment indication.
  • an RRC connection release device includes:
  • a fourth transceiver configured to send a first message to the base station, where the first message carries indication information about whether the UE needs to receive downlink data;
  • the fourth transceiver is configured to send uplink data to be sent to the base station when the RRC connection release device does not need to receive downlink data, where the fourth processor carries the last uplink data packet. Carrying an Endmarker indication packet, releasing an RRC connection after the fourth transceiver transmits the last uplink data packet; and/or the fourth transceiver is configured to: when the fourth processor determines that downlink data needs to be received And after receiving the uplink data to be sent, receiving the downlink data, where the fourth processor is configured to resolve the RRC connection after the received downlink packet includes the Endmarker indication packet.
  • the fourth processor is further configured to carry an Endmarker indication packet on a PDCP header of a last uplink data packet to be sent uplink data.
  • a base station includes:
  • a fifth transceiver configured to receive a first message sent by the UE, where the first message carries indication information about whether the UE needs to receive downlink data;
  • the fifth transceiver is configured to: when the fifth processor determines that the indication information indicates that the UE does not need to receive downlink data, receive uplink data to be sent sent by the UE; and the fifth processor is configured to: Parsing that the RRC connection with the UE is released after the received uplink packet includes the Endmarker indication packet; and/or the fifth transceiver is configured to determine the indication information indication at the fifth processor.
  • the UE needs to receive downlink data, and after the receiving of the uplink data to be sent sent by the UE is completed, continue to send downlink data to the UE; the fifth transceiver is configured to send in the fifth transceiver.
  • the Endmarker indication packet is carried in the last downlink data packet, and the last downlink data packet carrying the Endmarker indication packet is sent to the UE after the fifth transceiver sends the downlink data packet to the UE.
  • the method further includes:
  • the fifth processor is further configured to: after the indication information indicates that the UE does not need to receive downlink data, after parsing the Endmarker indication packet in the uplink data to be sent sent by the UE,
  • the General Packet Radio Service Technology Tunneling Protocol GTP header of the last uplink data packet to be sent uplink data carries the Endmarker indication packet to the serving gateway S-GW;
  • the Endmarker indication packet is carried in the last downlink data packet, and the fifth processor is further configured to:
  • the Endmarker indication packet will be carried on the PDCP header of the last downlink data packet.
  • an RRC connection release device includes:
  • a sixth transceiver configured to report an application message to a network side device, where the application message carries an application layer protocol type of the UE;
  • a sixth processor configured to release the RRC connection after completing, by the network side device, all the data packets that need to be exchanged for the application layer protocol type.
  • the application layer protocol type is a transmission control protocol and a hypertext transfer protocol TCP/HTTP, or a user datagram protocol UDP.
  • an RRC connection release device includes:
  • a seventh transceiver configured to receive an application message reported by the UE, where the application message carries an application layer protocol type of the UE;
  • a seventh processor configured to determine, according to the application layer protocol type, a number of transport data packets corresponding to the application layer protocol type
  • the seventh transceiver is configured to receive a data packet that is sent by the UE to the application layer protocol type;
  • the seventh processor is configured to process a data packet that is sent by the UE for the application layer protocol type, and record the number of processed data packets;
  • the base station receives the type and/or service type of the UE reported by each UE, and the base station receives the data packet sent by the at least two UEs, and the base station selects the UE that meets the preset condition according to the type and/or service type of the UE reported by each UE.
  • the packets are cascaded.
  • the default condition is to point to a specific UE or a specific service.
  • the base station transmits the cascaded data packets on a common channel.
  • the public channel can be built during the default bearer establishment process.
  • the base station selects one of the default bearer channels as a common channel, or the base station requests to establish a new bearer channel after determining that the UE meets the preset condition.
  • the base station When the base station cascades the data packets of different UEs that meet the preset condition, the base station identifies the data packets of different UEs based on the IP address of the UE or identifies the data packets of different UEs based on the GTP IP+GTP TEID of the UE.
  • the base station Before the base station cascades the data packets of different UEs that meet the preset condition, the base station receives the notification message that is sent by the MME and carries the IP address of each UE.
  • the base station cascades data packets of different UEs, and then puts the cascaded data packets on a common channel for transmission, thereby reducing transmission load and improving transmission efficiency.
  • the eNB and the UE retain the context information of the UE, including the RRC configuration, the bearer configuration, the security context, and the like, and join the preset paging related information, including the user identifier, the TA Lists, the default paging period of the UE, and the eNB in the system message. Broadcast paging cycle
  • the eNB can determine the UE to be paged according to the user identifier according to the preset paging related information recorded in the context information, and determine the paging area according to the TA Lists, and broadcast from the default paging cycle of the UE and the broadcast in the system message.
  • the smaller one of the call periods is selected to determine the timing at which the eNB pages the UE in the air interface.
  • the eNB sends a paging message to the UE.
  • the method provided by the embodiment of the present invention solves the problem that the S1 interface between the eNB and the MME may remain connected after the UE releases the RRC connection, and the MME does not send the paging message to the eNB when the S1 interface remains connected.
  • the eNB cannot page the UE in the air interface.
  • the beneficial effect of the present invention is as follows: the UE sends a first message to the base station, where the first message carries a preset RRC release time determination parameter or a first RRC release time; if the UE carries the first RRC release time in the first message, the UE according to the The RRC release time sets the timing duration of the first timer and starts the first timer; or if the UE carries the preset RRC release time determination parameter in the first message, the UE receives the response message of the base station for the first message feedback, where The response message carries a second RRC release time determined by the base station according to the preset RRC release time determination parameter. The UE sets the timing duration of the first timer according to the second RRC release time and starts the first timer.
  • the UE is in the first timer.
  • the RRC connection is released when the timeout expires, which greatly saves the signaling overhead in the RRC release process.
  • Base station based The first message determines a timing duration of the second timer, and sends indication information indicating a timing duration of the second timer to the MME.
  • the UE, the base station, and the MME respectively set the first timer, the second timer, and the third timer according to the RRC release time.
  • the UE When the UE determines that the first timer expires, the UE releases the RRC connection; when the base station determines that the second timer expires And releasing the RRC connection with the UE; when the MME determines that the third timer expires, it is determined that the UE releases the RRC connection, which greatly saves signaling overhead in the RRC release process.
  • the UE sends a first message to the base station, and carries the indication information of whether the UE needs to receive downlink data.
  • the UE sends the uplink data to be sent to the base station, and carries the Endmarker indication packet in the last uplink data packet, and after the last uplink data packet is sent, the UE releases the RRC connection, and the base station according to the base station
  • the indication information determines that the UE does not need to receive the downlink data, and resolves that the received uplink packet includes the Endmarker indication packet, and releases the RRC connection with the UE; and/or when the UE needs to receive the downlink data, the uplink to be sent.
  • the UE After the data transmission is completed, the UE receives the downlink data, and releases the RRC connection after parsing the received downlink data packet with the Endmarker indication packet.
  • the base station determines, according to the indication information, that the UE needs to receive the downlink data, and sends the last downlink data packet carrying the Endmarker indication packet to the UE, and releases the RRC connection with the UE, which greatly saves signaling during the RRC release process. Overhead.
  • the UE reports the application message carrying the application layer protocol type of the UE to the network side device, and after the network side device completes all the data packets that need to be exchanged for the application layer protocol type, releases the RRC connection; the network side device determines according to the application layer protocol type.
  • the RRC connection greatly saves the signaling overhead in the RRC release process.
  • FIG. 1 is a structural diagram of a network system in an embodiment of the present invention.
  • FIG. 2 is a flow chart A1 of an RRC connection release overview according to an embodiment of the present invention.
  • FIG. 3 is a flowchart A2 of an RRC connection release overview according to an embodiment of the present invention.
  • FIG. 4 is a flowchart A3 of an RRC connection release overview according to an embodiment of the present invention.
  • FIG. 5 is a specific flowchart A4 of an RRC connection release according to an embodiment of the present invention.
  • FIG. 6 is a flowchart B1 of an RRC connection release overview according to an embodiment of the present invention.
  • FIG. 7 is a flowchart B2 of an RRC connection release overview according to an embodiment of the present invention.
  • FIG. 8 is a specific flowchart B3 of an RRC connection release according to an embodiment of the present invention.
  • FIG. 9 is a specific flowchart B4 of an RRC connection release according to an embodiment of the present invention.
  • FIG. 10 is a flowchart C1 of an RRC connection release overview according to an embodiment of the present invention.
  • 11 is a standard protocol flow of HTTP/TCP in an embodiment of the present invention.
  • FIG. 13 is a flowchart C2 of an RRC connection release overview according to an embodiment of the present invention.
  • FIG. 14 is a schematic diagram of a user plane protocol stack of an S1 interface according to an embodiment of the present invention.
  • 15 is a schematic structural diagram of a transmission frame of an S1-U protocol stack according to an embodiment of the present invention.
  • FIG. 16 is a flowchart of cascading and transmitting data packets reported by an eNB by an eNB according to an embodiment of the present disclosure
  • FIG. 17 is a schematic structural diagram of an RRC connection release apparatus 1700 according to an embodiment of the present invention.
  • FIG. 18 is a schematic structural diagram of an RRC connection release apparatus 1800 according to an embodiment of the present invention.
  • FIG. 19 is a schematic structural diagram of an RRC connection release apparatus 1900 according to an embodiment of the present invention.
  • FIG. 20 is a schematic structural diagram of an RRC connection release apparatus 2000 according to an embodiment of the present invention.
  • FIG. 21 is a schematic structural diagram of an RRC connection release apparatus 2100 according to an embodiment of the present invention.
  • FIG. 22 is a schematic structural diagram of an RRC connection release device 2200 according to an embodiment of the present invention.
  • FIG. 23 is a schematic structural diagram of an RRC connection release device 2300 according to an embodiment of the present invention.
  • Figure 24 is an RRC connection release device 2400 according to an embodiment of the present invention.
  • FIG. 25 is an RRC connection release device 2500 according to an embodiment of the present invention.
  • Figure 26 is an RRC connection release device 2600 according to an embodiment of the present invention.
  • Figure 27 is an RRC connection release device 2700 according to an embodiment of the present invention.
  • Figure 28 is an RRC connection release device 2800 according to an embodiment of the present invention.
  • Figure 29 is an RRC connection release device 2900 according to an embodiment of the present invention.
  • FIG. 30 is an RRC connection release device 3000 according to an embodiment of the present invention.
  • An embodiment of the present invention provides an RRC connection release method, apparatus, and device, which are used to solve the problem that a large number of signalings are required in an RRC connection release procedure, resulting in a heavy network load.
  • the method and the device are based on the same inventive concept. Since the principles of the method and the device for solving the problem are similar, the implementation of the device and the method can be referred to each other, and the repeated description is not repeated.
  • the main application scenario of the embodiment of the present invention is a Long Term Evolution (LTE) system.
  • the system architecture of the system is as shown in FIG. 1.
  • the network element mainly included in the system includes: an Evolution Node B (eNB). Mobility Management Entity (MME), Serving Gateway (S-GW), and Packet Data Network Gateway (PDN).
  • eNB Evolution Node B
  • MME Mobility Management Entity
  • S-GW Serving Gateway
  • PDN Packet Data Network Gateway
  • FIG. 2 is a flowchart (1) of an RRC connection release overview according to an embodiment of the present invention.
  • Step 210 The UE sends a first message to the base station.
  • the first message carries a preset RRC release time determination parameter or a first RRC release time.
  • the first RRC request message here may be a new message or may be carried in an existing RRC connection request message.
  • the preset RRC release time determining parameter is the data amount of the uplink data to be sent of the UE and/or the estimated time of sending the uplink data to be sent.
  • Step 220 If the UE carries the first RRC release time in the first message, the UE sets the timing duration of the first timer according to the first RRC release time, and starts the first timer; or if the UE carries the pre-initial in the first message The RRC release time determining parameter, the UE receiving the response message that the base station feeds back the first message, where the response message carries the second RRC release time determined by the base station according to the preset RRC release time determination parameter; the UE according to the second RRC release time Setting a timing duration of the first timer, and starting the first timer;
  • the response message carries a second RRC release time determined by the base station according to the data volume of the uplink data to be sent sent by the UE and/or the estimated transmission time of the uplink data to be sent.
  • the response message here may be a new message or may be carried in an existing RRC setup message.
  • Step 230 The UE releases the RRC connection when the first timer expires.
  • the UE may also report a Buffer Status Report (BSR) to the base station according to the needs of the UE, where the BSR is used to indicate the timing duration of the second timer by the base station, where The timing duration of the second timer is set by the base station according to the first message sent by the UE.
  • BSR Buffer Status Report
  • the UE receives the first adjustment indication returned by the base station, for example, the indication carries the timing duration or the time adjustment amount ⁇ T of the adjusted latest second timer.
  • the UE adjusts the timing duration of the first timer according to the first adjustment indication.
  • the BSR is reported when the UE performs uplink data transmission, and the eNB adjusts the timing duration of the second timer according to the BSR.
  • the timing duration of the second timer needs to be extended by 10 seconds, and the value is notified to the UE by using the first adjustment indication.
  • the UE adjusts the timing duration of the first timer according to the indication, that is, the timing duration of the first timer is increased by 10 seconds.
  • the UE resumes the RRC connection with the base station, re-enters the UE in the connected state to perform uplink data transmission, and after the UE determines the timeout, releases the RRC connection, which saves the signaling overhead in the RRC release process.
  • FIG. 3 is a flowchart (A2) of an RRC connection release overview according to an embodiment of the present invention.
  • Step 310 The base station receives the first message sent by the UE.
  • the first message carries a preset RRC release time determination parameter or a first RRC release time.
  • the preset RRC release time determining parameter is the data amount of the uplink data to be sent of the UE and/or the estimated time of sending the uplink data to be sent.
  • the first RRC request message here may be a new message or may be carried in an existing RRC connection request message.
  • Step 320 If the base station determines that the first message carries the first RRC release time, the base station sets the timing duration of the second timer according to the first RRC release time, and starts the second timer; or if the base station determines that the first message carries the pre- The RRC release time determination parameter is set, the base station determines the second RRC release time according to the preset RRC release time determination parameter, and carries the second RRC release time in the response message fed back to the UE for the first message; the base station according to the second RRC The release time sets the timing of the second timer and starts the second timer.
  • the base station may determine, according to the data volume of the uplink data to be sent, the time required for the UE to send the uplink data, and determine the determined time required for sending the uplink data as the second RRC release time.
  • the base station when determining the second RRC release time, the base station directly determines the RRC release time according to the estimated transmission time of the uplink data to be sent, or increases the estimated time by a preset delay as the second RRC release time.
  • the response message here may be a new message or may be carried in an existing RRC setup message.
  • the base station After the base station feeds back the response message to the UE, it receives an acknowledgment message sent by the UE for the response message, where the acknowledgment message may be a new message or may be carried in the existing RRC connection setup complete message.
  • the eNB After the base station receives the acknowledgment message for the response message sent by the UE, the eNB sends the S1 resume connection indication information to the MME, where the S1 resumes the connection instruction to carry the second timer.
  • the base station receives the acknowledgment indication information of the S1 connection recovery sent by the MME, and determines that the S1 connection between the base station and the MME has been restored according to the acknowledgment indication of the S1 connection recovery.
  • Step 330 The base station releases the RRC connection with the UE when the second timer expires.
  • the base station before receiving the BSR reported by the UE, the base station adjusts the timing of the second timer according to the BSR, and generates a first adjustment indication to return to the UE, and a second adjustment indication notification to the base station before the second timer expires. MME.
  • the base station restores the RRC connection with the UE before the timeout, and receives the uplink data sent by the UE that re-enters the connected state, and releases the RRC connection with the UE after the base station determines the timeout, thereby saving the RRC release process. Signaling overhead.
  • FIG. 4 it is a flow chart A3 of an RRC connection release overview according to an embodiment of the present invention.
  • Step 410 The MME receives the S1 connection recovery indication information sent by the base station.
  • the S1 connection recovery indication information carries the timing duration of the second timer, where the timing duration of the second timer is set by the base station according to the first message sent by the UE, and the first message carries a preset RRC release time determination parameter or the first RRC release time.
  • the MME After the MME receives the S1 connection recovery indication information sent by the base station, the MME restores the S1 connection with the base station according to the S1 connection recovery indication information, and then transmits the confirmation indication information of the S1 connection restoration to the base station.
  • Step 420 The MME sets the timing duration of the third timer according to the timing duration of the second timer, and starts the third timer.
  • Step 430 When the third timer expires, the MME determines that the UE releases the RRC connection.
  • the MME adjusts the timing duration of the third timer according to the second adjustment indication.
  • FIG. 5 it is a specific flowchart A4 of RRC connection release according to an embodiment of the present invention.
  • the UE and the eNB retain the context information of the UE.
  • network trigger downlink data arrival
  • UE trigger uplink data arrival
  • Step 501 The UE sends an RRC connection request message to the eNB, where the request message carries the data quantity of the uplink data to be sent by the UE.
  • Step 502 The eNB calculates an RRC release time according to the data volume of the uplink data to be sent by the UE, and carries the RRC release time in the RRC setup message, and sends the second timer to the UE according to the RRC release time, and starts the second. Timer.
  • Step 503 The UE sets a first timer according to the RRC release time carried in the received RRC setup message, starts a first timer, and sends an RRC connection setup complete message to the eNB.
  • Step 504 After receiving the RRC connection setup complete message, the eNB sends the S1 connection recovery indication information to the MME, and carries the RRC release time in the S1 connection recovery indication information.
  • Step 505 The MME returns an acknowledgment indication message of the S1 connection recovery to the eNB, resumes the S1 connection with the eNB, and sets a third timer according to the RRC release time, and starts a third timer.
  • Step 506 The UE sends the uplink data to be sent to the network side device.
  • Step 507 The UE determines that the first timer expires, the UE releases the RRC connection, and the eNB determines that the second timer expires, releases the RRC connection with the UE; and the MME determines that the third timer expires, and determines that the UE releases the RRC connection.
  • the UE and the network side device need to retain the context information of the current connection of the UE.
  • the RRC release time is configured in the RRC connection establishment process, the UE performs the timing according to the RRC release time, and releases the RRC connection after the timeout, and the network side device also releases the time according to the RRC.
  • the timing is performed, and the RRC connection with the UE is released after the timeout, which saves the signaling overhead in the RRC connection release process.
  • FIG. 6 is a flowchart (1) of an RRC connection release overview according to an embodiment of the present invention.
  • Step 610 The UE sends a first message to the base station.
  • the first message carries indication information about whether the UE needs to receive downlink data.
  • the first message here may be a new message or may be carried in an existing RRC connection request message.
  • Step 620 When the UE does not need to receive downlink data, the UE sends the uplink data to be sent to the base station. And carrying the endpoint tag Endmarker indication packet in the last uplink data packet, the UE releases the RRC connection after transmitting the last uplink data packet; and/or the UE needs to receive the downlink data, after the uplink data transmission to be sent is completed, The downlink data is received, and after the Endmarker indication packet is included in the received downlink data packet, the RRC connection is released.
  • the UE does not need to receive downlink data, that is, the UE only sends uplink data and does not receive downlink data.
  • the UE After the UE resumes the RRC connection, the UE carries the Endmarker indication packet in the last uplink data packet, that is, the Packet Data Convergence Protocol (PDCP) header of the last uplink data packet of the UE to be sent uplink data.
  • the Endmarker indication packet is carried on the upper or medium access control (MAC) header.
  • the second case the UE needs to receive downlink data, that is, the UE sends both uplink data and downlink data.
  • the UE continues to receive the downlink data, and parses the downlink packet to include the Endmarker indication packet, and then releases the RRC connection.
  • FIG. 7 is a flowchart B2 of an RRC connection release overview according to an embodiment of the present invention.
  • Step 710 The base station receives the first message sent by the UE.
  • the first message carries indication information about whether the UE needs to receive downlink data.
  • the first message here may be a new message or may be carried in an existing RRC connection request message.
  • Step 720 The base station determines that the indication information indicates that the UE does not need to receive the downlink data, and receives the uplink data to be sent sent by the UE, and releases the RRC connection with the UE after parsing that the received uplink data packet includes the Endmarker indication packet. And/or the base station determines that the indication information indicates that the UE needs to receive the downlink data, and after the UE sends the uplink data to be sent, the downlink data is continuously sent to the UE, and when the last downlink data packet is sent, the last downlink data packet is sent. Carry the Endmarker indication packet and send the last downlink packet carrying the Endmarker indication packet to After the UE, the base station releases the RRC connection with the UE.
  • the eNB side also includes two cases:
  • the base station determines that the indication information indicates that the UE does not need to receive downlink data.
  • the base station After confirming that the RRC connection is established, the base station receives the uplink data sent by the UE, and after parsing the Endmarker indication packet from the uplink data sent by the UE, the base station releases the RRC connection with the UE.
  • the base station sends the received uplink data to be sent to the S-GW, and carries the Endmarker indication packet to the S on the GPRS Tunnelling Protocol (GTP) header of the last uplink data packet to be sent.
  • GTP GPRS Tunnelling Protocol
  • the second case the base station determines that the indication information indicates that the UE needs to receive downlink data.
  • the base station After confirming that the RRC connection is established, the base station receives the uplink data sent by the UE, and after receiving the uplink data to be sent sent by the UE, continues to receive the downlink data sent by the S-GW and sends the downlink data to the UE, where the base station sends the data from the S-GW. After the Endmarker indication packet is parsed in the downlink data, it is confirmed that the last downlink data packet has been received. The base station will carry the Endmarker indication packet on the PDCP header or the MAC header of the last downlink data packet, and after transmitting the last downlink data packet carrying the Endmarker indication packet to the UE, the base station releases the RRC connection with the UE.
  • FIG. 8 a specific flowchart B3 of RRC connection release according to an embodiment of the present invention is provided.
  • the UE and the eNB retain the context information of the UE.
  • network trigger downlink data arrival
  • UE trigger uplink data arrival
  • Step 801 The UE sends an RRC connection request message to the eNB, where the request message carries indication information that the UE does not need to receive downlink data.
  • Step 802 The eNB sends an RRC setup message to the UE.
  • Step 803 The UE sends an RRC Connection Setup Complete message to the eNB.
  • Step 804 After receiving the RRC connection setup complete message, the eNB sends the S1 connection recovery indication information to the MME, and carries the indication information that the UE does not need to receive the downlink data in the S1 connection recovery indication information.
  • Step 805 The MME returns an acknowledgement indication message of the S1 connection recovery to the eNB, indicating that the S1 connection between the MME and the eNB has been restored.
  • Step 806 The UE sends the uplink data to be sent to the network side device.
  • Step 807 The UE carries the Endmarker indication packet in the last uplink data packet, and after releasing the last uplink data packet, the UE releases the RRC connection; and the eNB parses out the received uplink data packet and includes the Endmarker indication packet, and releases the An RRC connection between the UEs; and the MME determines that the UE releases the RRC connection.
  • the MME and the S-GW may be combined devices, or the two network elements may be connected to each other.
  • the S-GW parses out that the received uplink data packet includes the Endmarker indication packet, it determines that the UE releases the RRC connection, and The message is notified to the MME.
  • the UE and the network side device need to retain the context information of the current connection of the UE.
  • the UE carries the Endmarker indication packet in the last uplink data packet of the uplink data, and releases the RRC connection when the UE sends the last packet uplink data carrying the Endmarker indication packet, and the network side device also analyzes the Endmarker according to the uplink data.
  • the indication packet is released, and the RRC connection with the UE is released, which saves the signaling overhead in the RRC connection release process.
  • FIG. 9 a specific flowchart B4 of RRC connection release according to an embodiment of the present invention is provided.
  • the UE and the eNB retain the context information of the UE.
  • network trigger downlink data arrival
  • UE trigger uplink data arrival
  • Step 901 The UE sends an RRC connection request message to the eNB, where the request message carries indication information that the UE needs to receive downlink data.
  • Step 902 The eNB sends an RRC setup message to the UE.
  • Step 903 The UE sends an RRC Connection Setup Complete message to the eNB.
  • Step 904 After receiving the RRC connection setup complete message, the eNB sends an S1 connection recovery indication message to the MME, and carries the UE to receive downlink data in the S1 connection recovery indication information. Instructions.
  • Step 905 The MME returns an acknowledgement indication message of the S1 connection restoration to the eNB, and resumes the S1 connection with the eNB.
  • Step 906 The UE sends the uplink data to be sent to the network side device.
  • Step 907 The UE receives downlink data sent by the eNB.
  • Step 908 After parsing the Endmarker indication packet in the downlink data, the UE releases the RRC connection; and the eNB carries the Endmarker indication packet in the last downlink data packet, and sends the last downlink data packet carrying the Endmarker indication packet to the UE. And releasing an RRC connection with the UE; and the MME determines that the UE releases the RRC connection.
  • the MME and the S-GW may be combined devices, or the two network elements are connected by an interface.
  • the S-GW sends the last downlink data packet carrying the Endmarker indication packet, it is determined that the UE releases the RRC connection, and The message is notified to the MME.
  • the UE and the network side device need to retain the context information of the current connection of the UE.
  • the UE After transmitting the uplink data, the UE receives the downlink data, and after the Endmarker indication packet is parsed in the downlink data, releases the RRC connection; and the eNB receives the uplink data sent by the UE, and forwards the downlink data to the UE, where the last downlink packet is sent. After the Endmarker indication packet is carried, and the last downlink data packet carrying the Endmarker indication packet is sent to the UE, the RRC connection with the UE is released, which saves the signaling overhead in the RRC connection release process.
  • FIG. 10 is a flowchart C1 of an RRC connection release overview according to an embodiment of the present invention.
  • Step 1010 The UE reports an application message to the network side device, where the application message carries the application layer protocol type of the UE.
  • the application layer protocol type is a Hyper Text Transfer Protocol (HTTP), a Transmission Control Protocol (TCP), and a User Datagram Protocol (UDP).
  • HTTP Hyper Text Transfer Protocol
  • TCP Transmission Control Protocol
  • UDP User Datagram Protocol
  • HTTP is a request based
  • the response mode protocol usually, the client initiates a request to establish a TCP connection to the server's designated port.
  • the server listens to the request sent by the client on the port, and sends a response message to the client once the request is received.
  • TCP is a connection-oriented reliable protocol. To ensure the reliability of transmission, the receiving end sends a corresponding acknowledgement (ACK) to the successfully received data. If the sender does not receive an acknowledgment within a reasonable round-trip delay, the corresponding The data will be retransmitted.
  • connection-oriented means that the client and the server must establish a TCP connection before exchanging data packets. After the TCP connection is successfully established, data transmission can begin.
  • UDP is a connectionless protocol. It does not guarantee the reliability of transmitted data packets, and has the advantages of low resource consumption and fast processing speed.
  • Step 1020 After the UE completes all the data packets that need to be exchanged for the application layer protocol type with the network side device, the UE releases the RRC connection.
  • the UE releases the RRC connection according to the standard protocol procedure of the application layer protocol type.
  • the UE when the UE uses the application layer protocol of TCP/HTTP, in order to complete the data transmission, the UE first initiates a DNS request to the Domain Name System (DNS) server, and the DNS server replies according to the domain name. To the UE, then the UE establishes a TCP connection using the three-way handshake protocol. After the three-way handshake is completed, the UE starts to transmit data. After receiving the TCP data, the server will reply to the TCP ACK, and the HTTP protocol layer will generate an HTTP 200 OK and send it to the UE. After receiving the UE, the UE receives the data. The server replies with a TCP ACK, and the TCP connection needs to be released after the data transfer ends. After completing all the data packets that TCP/HTTP needs to interact, the UE releases the RRC connection.
  • DNS Domain Name System
  • the number of signaling required to complete data transmission when the UE adopts different application layer protocols is also different.
  • FIG. 13 is a flowchart C2 of an RRC connection release overview according to an embodiment of the present invention.
  • Step 1310 The network side device receives the application message reported by the UE, where the application message carries the application layer protocol type of the UE.
  • the network side device here may be an eNB or an MME.
  • Step 1320 The network side device determines, according to an application layer protocol type, the number of transport data packets corresponding to the application layer protocol type.
  • the eNB determines that the UE needs to send 6 messages according to the standard protocol flow of TCP/HTTP, and needs to receive 5 messages.
  • Step 1330 The network side device processes the data packet transmitted by the UE for the application layer protocol type, and records the number of processed data packets.
  • the eNB determines that the UE needs to send six messages according to the standard protocol procedure of TCP/HTTP. After receiving five messages, the eNB records the situation in which the UE completes the TCP/HTTP standard process, and records how many messages are sent by the UE, and how many messages are received. Message, or just record how many messages the UE receives.
  • Step 1340 When the network side device determines that the number of recorded data packets reaches the number of transport data packets corresponding to the application layer protocol type, the network side device releases the RRC connection with the UE.
  • the eNB determines that the UE has sent 6 messages for TCP/HTTP, after receiving 5 messages, the RRC connection with the UE is released.
  • the UE when the UE uses the UDP protocol, the UE also needs to complete the DNS resolution first. After the UE learns the server address, the data is transmitted. Since the UDP does not guarantee the reliability of the data transmission, the server does not perform the data. Corresponding confirmation reply, the HTTP protocol layer will generate HTTP 200 OK as UDP data and send it to the UE. After receiving the UE, the corresponding confirmation reply will not be performed.
  • the UE reports that the application layer protocol type is UDP the eNB determines that the UE needs to send two messages according to the standard protocol procedure of the UDP, and needs to receive two messages. Therefore, when the number of messages received by the UE is 2, the eNB releases the UE. Between the RRC connections.
  • the UE only needs to send a message once, that is, the UE only ends the transmission of the data packet after transmitting the uplink data packet to the server, releasing the RRC connection, and correspondingly, the network side
  • the device releases the RRC connection with the UE after processing one data packet.
  • the network side device knows, according to the application layer protocol type reported by the UE, the number of data packets that need to be transmitted in the application layer protocol type, that is, the number of data packets that the UE needs to receive and send, and The data packets received and sent by the UE are counted, and it is determined that the application layer protocol class is reached. When the number of the specified data packets is determined, it is determined that the UE releases the RRC connection, thereby reducing the signaling overhead and the load of the network resources in the RRC connection release process.
  • FIG. 14 is a schematic diagram of a user plane protocol stack of an S1 interface, and the S1-U interface provides non-guaranteed transmission of user plane data between an eNB and an S-GW.
  • the GTP-U is located above the UDP layer and the IP layer for transmitting a User Data Protocol (PDU).
  • PDU User Data Protocol
  • Each bearer of each UE needs a GTP-U channel for transmission, that is, each data packet of each UE is transmitted to the GTP-U layer through the corresponding processing of the upper layer, and then transmitted to the lower layer through the corresponding processing of the GTP-U layer.
  • the base station receives the type and/or service type of the UE reported by each UE, and the base station receives the data packets sent by multiple UEs, and the base station according to the type and/or service type of the UE reported by each UE.
  • the cascading of the data packets of the UE that meets the preset condition is performed.
  • the cascading operation is mainly performed when the data packet to be transmitted is small. Therefore, the preset condition is for a specific UE or a specific service.
  • the base station transmits the cascaded data packets on a common channel.
  • the public channel may be built in the default bearer setup process, and the base station selects one of the default bearer channels as a common channel, or the base station requests to establish a new bearer channel after determining that the UE meets the preset condition.
  • the base station when the base station cascades the data packets of different UEs that meet the preset condition, the base station needs to identify the received data packets of each UE, that is, identify the different UEs by using the identifier of the UE.
  • the base station needs to identify the received data packets of each UE, that is, identify the different UEs by using the identifier of the UE.
  • the P-GW allocates a unique IP address to each UE, and the IP address is an end-to-end address, and only the UE and the MME know the place. Address, but the eNB cannot know.
  • the MME needs to notify the eNB of the IP address of each UE, that is, before the base station cascades the data packets of different UEs that meet the preset condition.
  • the base station receives a notification message that is sent by the MME and carries an IP address of each UE.
  • the eNB and the SGW can identify the UE based on the IP address immediately following each packet in the concatenated data packet.
  • the eNB cascades data packets of multiple UEs and transmits them on a common GTP-U channel. As shown in Table 1, the eNB concatenates the data packets of different UEs into the following format:
  • the UE-based GTP IP+GTP TEID identifies packets of different UEs.
  • a tunnel endpoint identifier is used for user plane transmission between the eNB and the S-GW.
  • the eNB can learn the GTP IP and the GTP TEID allocated by the S-GW, and the eNB and the S-GW can distinguish different UEs by using the GTP IP+GTP TEID.
  • the eNB concatenates the data packets of multiple UEs and transmits them on the common GTP-U channel, so different UEs can be identified based on the GTP IP+GTP TEID followed by each packet in the concatenated data packet. As shown in Table 2, the eNB concatenates the data packets of different UEs into the following format:
  • FIG. 16 is a flowchart of cascading and transmitting data packets reported by an eNB by an eNB according to an embodiment of the present invention.
  • Step 1601 UE1 and UE2 report the type/service type of the UE to the eNB.
  • Step 1602 UE1 and UE2 send uplink data to the eNB.
  • Step 1603 The eNB determines that UE1 and UE2 are special according to the reported information of the two UEs.
  • Type such as packet transmission in CIoT, meets preset conditions, and uplink data of UE1 and UE2 are cascaded to obtain a cascading data packet.
  • Step 1604 The eNB transmits the concatenated data packet through the S1-U.
  • Step 1605 The S-GW sends an acknowledgement message for the concatenated data packet.
  • the base station cascades the data packets of different UEs, and then puts the cascaded data packets on a common channel for transmission, thereby reducing the transmission load and improving the transmission efficiency.
  • the downlink data can be forwarded to the S-GW all the time because the S5 user plane bearer exists between the S-GW and the P-GW.
  • the S-GW After receiving the downlink data, the S-GW notifies the MME that the downlink message needs to be sent to the UE through the Downlink Data Notification message, and triggers the MME to send the paging message.
  • the MME sends a paging message to all the eNBs in the Tracking Area List (TA List) where the UE carries the SAE Temporary Mobile Station Identifier (SAE Temporary Mobile Station Identifier, S -TMSI), TA Lists and the default paging cycle of the UE, and the eNB also has a broadcast paging cycle in the system message, and the eNB selects between the default paging cycle of the UE and the broadcast paging cycle in the system message.
  • the smaller paging cycle is used to calculate the timing at which the eNB pages the UE in the air interface.
  • the eNB sends a paging message to the UE.
  • the S1 interface between the eNB and the MME may remain connected.
  • the MME does not send a paging message to the eNB.
  • the eNB cannot page the UE in the air interface.
  • this embodiment provides a scheme in which an eNB determines an air interface paging UE.
  • the eNB and the UE retain the context information of the UE, including the RRC configuration, the bearer configuration, the security context, and the like, and the preset paging related information is added to the context information saved in the embodiment of the present invention.
  • the eNB can determine the to-be-founded according to the user identifier according to the preset paging related information recorded in the context information.
  • Called UE ie which UE is paged in the air interface, and determines the paging area according to the TA Lists, and the default paging cycle and system message from the UE
  • the smaller one of the broadcast paging periods is selected to determine the timing at which the eNB pages the UE in the air interface.
  • the eNB sends a paging message to the UE.
  • an RRC connection release apparatus 1700 includes:
  • the first sending unit 1701 is configured to send a first message to the base station, where the first message carries a preset RRC release time determination parameter or a first RRC release time;
  • the first processing unit 1702 is configured to: when the first RRC release time is carried in the first message, set a timing duration of the first timer according to the first RRC release time, and start the first timer; or the first receiving unit 1703, And a response message, where the response message carries a second RRC release time determined by the base station according to the preset RRC release time determination parameter; the first processing unit 1702 is configured to carry in the first message.
  • the preset RRC release time determination parameter is set, the timing duration of the first timer is set according to the second RRC release time, and the first timer is started;
  • the first determining unit 1704 is configured to release the RRC connection when the first timer expires.
  • the preset RRC release time determining parameter is a data volume of the device to send uplink data and/or a sending estimated time of the uplink data to be sent.
  • it also includes:
  • the first sending unit 1701 is further configured to report the BSR to the base station, where the BSR is used to indicate that the base station adjusts the timing duration of the second timer, where the timing duration of the second timer is set by the base station according to the first message sent by the UE;
  • the first receiving unit 1703 is further configured to receive a first adjustment indication that is sent back by the base station;
  • the first processing unit 1702 is further configured to: when receiving the first adjustment indication returned by the base station, adjust the timing duration of the first timer according to the first adjustment indication.
  • an RRC connection release apparatus 1800 includes:
  • the second receiving unit 1801 is configured to receive a first message sent by the UE, where the first message carries a preset RRC release time determination parameter or a first RRC release time;
  • the second processing unit 1802 is configured to determine, when the first message carries the first RRC release time, set a timing duration of the second timer according to the first RRC release time, and start a second timer; or the second processing unit 1802, The method for determining that the first message carries a preset RRC release time determination parameter, Determining a second RRC release time according to the preset RRC release time determination parameter, and setting a timing duration of the second timer according to the second RRC release time, and starting a second timer; the second sending unit 1803, for the first Sending a response message to the UE, where the response message carries a second RRC release time;
  • the second determining unit 1804 is configured to: when the second timer expires, the base station releases the RRC connection with the UE.
  • the preset RRC release time determining parameter is a data quantity of the uplink data to be sent by the UE and/or an estimated time of sending the uplink data to be sent.
  • it also includes:
  • the second receiving unit 1801 is further configured to receive a BSR reported by the UE.
  • the second processing unit 1802 is further configured to: when receiving the BSR reported by the UE, adjust a timing duration of the second timer, and generate a first adjustment indication and a second adjustment indication according to the timing duration adjustment result of the second timer. ;
  • the second sending unit 1803 is further configured to: return the first adjustment indication to the UE, and notify the MME of the second adjustment indication.
  • it also includes:
  • the second receiving unit 1801 is further configured to receive an acknowledgement message sent by the UE for the response message.
  • the second sending unit 1803 is further configured to: after the second receiving unit receives the acknowledgement message for the response message sent by the UE, send the S1 connection recovery indication information to the MME, where the S1 connection recovery indication information carries the second timer;
  • the second receiving unit 1801 is further configured to receive the confirmation indication information of the S1 connection recovery sent by the MME;
  • the second processing unit 1802 is further configured to determine, according to the confirmation indication information of the S1 connection recovery, that the S1 connection between the base station and the MME has been restored.
  • an RRC connection release apparatus 1900 includes:
  • the third receiving unit 1901 is configured to receive the S1 connection recovery indication information sent by the base station, where the S1 connection recovery indication information carries a timing duration of the second timer, where the timing duration of the second timer
  • the first message is set by the base station according to the first message sent by the UE, where the first message carries a preset RRC release time determination parameter or a first RRC release time;
  • the third processing unit 1902 is configured to set a timing duration of the third timer according to a timing duration of the second timer, and start a third timer;
  • the third determining unit 1903 is configured to determine, when the third timer expires, that the UE releases the RRC connection.
  • it also includes:
  • the third processing unit 1902 is configured to determine, according to the S1 connection recovery indication information, that the S1 connection between the base station and the base station is restored;
  • the third sending unit 1904 is configured to send, to the base station, the confirmation indication information of the S1 connection recovery.
  • the third receiving unit 1901 is further configured to receive a second adjustment indication sent by the base station;
  • the third processing unit 1902 is further configured to: when the third receiving unit receives the second adjustment indication sent by the base station, adjust the timing duration of the third timer according to the second adjustment indication.
  • an RRC connection release apparatus 2000 includes:
  • the fourth sending unit 2001 is configured to send a first message to the base station, where the first message carries indication information about whether the UE needs to receive downlink data.
  • the fourth sending unit 2001 is configured to: when the fourth processing unit 2002 determines that the downlink data does not need to be received, send the uplink data to be sent to the base station, and the fourth processing unit 2002 is configured to carry the Endmarker indication packet in the last uplink data packet. And after the fourth sending unit 2001 sends the last uplink data packet, releasing the RRC connection; and/or the fourth sending unit 2001, configured to send the uplink data to be sent to the base station when the fourth processing unit determines that the downlink data needs to be received.
  • the fourth receiving unit 2003 is configured to receive downlink data after the fourth processing unit 2002 determines that the uplink data transmission to be sent is completed, and the fourth processing unit 2002 is configured to include in the downlink data packet that is parsed to the fourth receiving unit. After the Endmarker indicates the packet, the RRC connection is released.
  • the fourth processing unit 2002 is further configured to carry an Endmarker indication packet on a PDCP header of a last uplink data packet to be sent uplink data.
  • an RRC connection release apparatus 2100 includes:
  • the fifth receiving unit 2101 is configured to receive a first message sent by the UE, where the first message carries the UE. Whether it is necessary to receive indication information of downlink data;
  • the fifth receiving unit 2101 is configured to: when the fifth processing unit 2102 determines that the indication information indicates that the UE does not need to receive downlink data, receive the uplink data to be sent sent by the UE; and in the fifth processing unit 2102, After the end packet received by the unit includes the Endmarker indication packet, the RRC connection with the UE is released; and/or the fifth receiving unit 2101 is configured to determine, at the fifth processing unit 2102, that the indication information indicates that the UE needs to receive downlink data, and receives
  • the fifth sending unit 2103 is configured to: after the receiving of the uplink data to be sent by the UE is completed by the fifth receiving unit, continue to send the downlink data to the UE; in the fifth processing unit 2102, When the fifth sending unit sends the last downlink data packet, the last downlink data packet carries the Endmarker indication packet, and the last downlink data packet carrying the Endmarker indication packet is sent to the UE, and the RRC connection with the UE is released. .
  • it also includes:
  • the fifth processing unit 2102 is further configured to: when the indication information indicates that the UE does not need to receive the downlink data, after parsing the Endmarker indication packet in the uplink data to be sent sent by the UE, the last uplink data packet of the uplink data to be sent is The General Packet Radio Service Technology Tunneling Protocol (GTP) carries an Endmarker indication packet to the serving gateway S-GW; and/or
  • GTP General Packet Radio Service Technology Tunneling Protocol
  • the Endmarker indication packet is carried in the last downlink data packet, and the fifth processing unit 2102 is further configured to:
  • the Endmarker indication packet will be carried on the PDCP header of the last downstream packet.
  • an RRC connection release apparatus 2200 includes:
  • the sixth sending unit 2201 is configured to report an application message to the network side device, where the application message carries an application layer protocol type of the UE;
  • the sixth determining unit 2202 is configured to release the RRC connection after completing all the data packets that need to be exchanged for the application layer protocol type with the network side device.
  • the application layer protocol type is a transmission control protocol and a hypertext transfer protocol TCP/HTTP. Or User Datagram Protocol UDP.
  • an RRC connection release apparatus 2300 includes:
  • the seventh receiving unit 2301 is configured to receive an application message reported by the UE, where the application message carries an application layer protocol type of the UE.
  • a determining unit 2302 configured to determine, according to an application layer protocol type, a number of transport data packets corresponding to an application layer protocol type
  • a counting unit 2303 configured to receive and process a data packet transmitted by the UE for an application layer protocol type, and record the number of processed data packets;
  • the seventh determining unit 2304 is configured to release the RRC connection with the UE when determining that the number of recorded data packets reaches the number of transport data packets corresponding to the application layer protocol type.
  • each functional module in each embodiment of the present application may be used. It can be integrated into one processing module, or each module can exist physically separately, or two or more modules can be integrated into one module.
  • the above integrated modules can be implemented in the form of hardware or in the form of software functional modules.
  • An integrated module if implemented as a software functional module and sold or used as a standalone product, can be stored in a computer readable storage medium.
  • the technical solution of the present application in essence or the contribution to the prior art, or all or part of the technical solution may be embodied in the form of a software product stored in a storage medium.
  • a number of instructions are included to cause a computer device (which may be a personal computer, server, or network device, etc.) or a processor to perform all or part of the steps of the various embodiments of the present application.
  • the foregoing storage medium includes: a U disk, a mobile hard disk, a read-only memory (ROM), a random access memory (RAM), a magnetic disk, or an optical disk, and the like. .
  • an embodiment of the present invention provides an RRC connection release device 2400, including:
  • the device includes a first transceiver 2401, a first processor 2402, and a first storage. Reservoir 2403.
  • the first transceiver 2401, the first processor 2402, and the first memory 2403 are connected to each other.
  • the specific connecting medium between the above components is not limited in the embodiment of the present invention.
  • the first memory 2403, the first processor 2402, and the first transceiver 2401 are connected by a bus 2404 in FIG. 24, and the bus is indicated by a thick line in FIG. 24, and the connection manner between other components is It is for illustrative purposes only and is not intended to be limiting.
  • the bus can be divided into an address bus, a data bus, a control bus, and the like.
  • Figure 24 is shown with only one thick line, but does not indicate that there is only one bus or one type of bus.
  • the first memory 2403 is configured to store the program code executed by the first processor 2402, and may be a volatile memory, such as a random access memory (English: random-access memory, abbreviation) :RAM); the first memory 2403 may also be a non-volatile memory (English: non-volatile memory), such as read-only memory (English: read-only memory, abbreviation: ROM), flash memory (English: flash memory) , hard disk drive (English: hard disk drive, abbreviated: HDD) or solid state drive (English: solid-state drive, abbreviated: SSD), or the first memory 2403 is capable of carrying or storing the desired form of instructions or data structures. Program code and any other medium that can be accessed by a computer, but is not limited thereto.
  • the first memory 2403 may be a combination of the above memories.
  • the first transceiver 2401 is configured to send a first message to the base station, where the first message carries a preset RRC release time determination parameter or a first RRC release time;
  • the first processor 2402 is configured to: when the first RRC release time is carried in the first message, set a timing duration of the first timer according to the first RRC release time, and start the first timer; or the first transceiver 2401, And receiving, by the base station, a response message for the first message feedback, where the response message carries a second RRC release determined by the base station according to the preset RRC release time determination parameter, when the first message carries the preset RRC release time determination parameter.
  • a first processor 2402 configured to set a timing duration of the first timer according to the second RRC release time, and start a first timer;
  • the first processor 2402 is further configured to release the RRC connection when the first timer expires.
  • the preset RRC release time determining parameter is a data quantity of the uplink data to be sent by the UE and/or an estimated time of sending the uplink data to be sent.
  • the first transceiver 2401 is further configured to report the BSR to the base station, where the BSR is used to instruct the base station to adjust the timing duration of the second timer, where the timing duration of the second timer is the first message sent by the base station according to the UE. Provided; and receiving a first adjustment indication of the base station reply;
  • the first processor 2402 is further configured to: when receiving the first adjustment indication returned by the base station, adjust the timing duration of the first timer according to the first adjustment indication.
  • an embodiment of the present invention provides an RRC connection release device 2500, including:
  • the device includes a second transceiver 2501, a second processor 2502, and a second memory 2503.
  • the second transceiver 2501, the second processor 2502, and the second memory 2503 are connected to each other.
  • the specific connecting medium between the above components is not limited in the embodiment of the present invention.
  • the embodiment of the present invention is connected in FIG. 25 between the second memory 2503, the second processor 2502, and the second transceiver 2501 via a bus 2504.
  • the bus is indicated by a thick line in FIG. 25, and the connection manner between other components is It is for illustrative purposes only and is not intended to be limiting.
  • the bus can be divided into an address bus, a data bus, a control bus, and the like.
  • Figure 25 is shown with only one thick line, but does not indicate that there is only one bus or one type of bus.
  • the second memory 2503 is configured to store the program code executed by the second processor 2502, and may be a volatile memory, such as a random access memory (English: random-access memory, abbreviation) :RAM); the second memory 2503 may also be a non-volatile memory (English: non-volatile memory), such as read-only memory (English: read-only memory, abbreviation: ROM), flash memory (English: flash memory) , hard disk drive (English: hard disk drive, abbreviated: HDD) or solid state drive (English: solid-state drive, abbreviated: SSD), or second memory 2503 can be used to carry or store the desired form of instruction or data structure Program code and any other medium that can be accessed by a computer, but is not limited thereto.
  • the second memory 2503 may be a combination of the above memories.
  • the second transceiver 2501 is configured to receive a first message sent by the UE, where the first message carries a preset RRC release time determination parameter or a first RRC release time;
  • the second processor 2502 is configured to determine, when the first message carries the first RRC release time, set a timing duration of the second timer according to the first RRC release time, and start a second timer; or The second processor 2502 is configured to determine that the first message carries a preset RRC release time determination parameter, determine a second RRC release time according to the preset RRC release time determination parameter, and set a second timer according to the second RRC release time. And the second timer is used to send a response message to the UE for the first message, where the response message carries the second RRC release time;
  • the second processor 2502 is further configured to release an RRC connection with the UE when the second timer expires.
  • the preset RRC release time determining parameter is a data quantity of the uplink data to be sent by the UE and/or an estimated time of sending the uplink data to be sent.
  • it also includes:
  • the second transceiver 2501 is further configured to receive a BSR reported by the UE;
  • the second processor 2502 is further configured to: when the second transceiver 2501 receives the BSR reported by the UE, adjust a timing duration of the second timer, and generate a first adjustment indication according to the timing duration adjustment result of the second timer. And a second adjustment instruction;
  • the second transceiver 2501 is further configured to: restore the first adjustment indication to the UE, and notify the MME of the second adjustment indication.
  • the second transceiver 2501 is further configured to receive an acknowledgment message sent by the UE for the response message, and after receiving the acknowledgment message for the response message sent by the UE, send the S1 connection recovery indication information to the MME, where the S1 is connected. And determining, by the recovery indication information, a timing duration of the second timer; and receiving the confirmation indication information of the S1 connection recovery sent by the MME;
  • the second processor 2502 is configured to determine, according to the acknowledgment indication information of the S1 connection recovery, that the S1 connection between the base station and the MME has been restored.
  • an embodiment of the present invention provides an RRC connection release device 2600, including:
  • the device includes a third transceiver 2601, a third processor 2602, and a third memory 2603.
  • the third transceiver 2601, the third processor 2602, and the third memory 2603 are connected to each other.
  • the specific connecting medium between the above components is not limited in the embodiment of the present invention.
  • the embodiment of the present invention is connected in FIG. 26 between the third memory 2603, the third processor 2602, and the third transceiver 2601 via a bus 2604.
  • the bus is indicated by a thick line in FIG. 26, and the connection manner between other components is Only It is intended to be illustrative and not limited.
  • the bus can be divided into an address bus, a data bus, a control bus, and the like.
  • Figure 26 is shown with only one thick line, but does not indicate that there is only one bus or one type of bus.
  • the third memory 2603 is configured to store the program code executed by the third processor 2602, and may be a volatile memory, such as a random access memory (English: random-access memory, abbreviation) :RAM); the third memory 2603 may also be a non-volatile memory (English: non-volatile memory), such as read-only memory (English: read-only memory, abbreviation: ROM), flash memory (English: flash memory) , hard disk drive (English: hard disk drive, abbreviated: HDD) or solid state drive (English: solid-state drive, abbreviated: SSD), or third memory 2603 is capable of carrying or storing the desired form of instruction or data structure. Program code and any other medium that can be accessed by a computer, but is not limited thereto.
  • the third memory 2603 may be a combination of the above memories.
  • the third transceiver 2601 is configured to receive the S1 connection recovery indication information sent by the base station, where the S1 connection recovery indication information carries a timing duration of the second timer, where the timing duration of the second timer is the first message sent by the base station according to the UE.
  • the first message carries a preset RRC release time determination parameter or a first RRC release time.
  • the third processor 2602 is configured to set a timing duration of the third timer according to a timing duration of the second timer, and start a third timer;
  • it also includes:
  • the third processor 2602 is further configured to determine, according to the S1 connection recovery indication information, that the S1 connection between the base station and the base station is restored;
  • the third transceiver 2601 is further configured to send the confirmation indication information of the S1 connection recovery to the base station.
  • the third transceiver 2601 is configured to receive a second adjustment indication sent by the base station.
  • the third processor 2602 is configured to adjust a timing duration of the third timer according to the second adjustment indication.
  • an embodiment of the present invention provides an RRC connection release device 2700, including:
  • the device includes a fourth transceiver 2701, a fourth processor 2702, and a fourth storage. Reservoir 2703.
  • the fourth transceiver 2701, the fourth processor 2702, and the fourth memory 2703 are connected to each other.
  • the specific connecting medium between the above components is not limited in the embodiment of the present invention.
  • the embodiment of the present invention is connected in FIG. 27 between the fourth memory 2703, the fourth processor 2702, and the fourth transceiver 2701 via a bus 2704.
  • the bus is indicated by a thick line in FIG. 27, and the connection manner between other components is It is for illustrative purposes only and is not intended to be limiting.
  • the bus can be divided into an address bus, a data bus, a control bus, and the like.
  • Figure 27 is shown with only one thick line, but does not indicate that there is only one bus or one type of bus.
  • the fourth memory 2703 is configured to store the program code executed by the fourth processor 2702, and may be a volatile memory, such as a random access memory (English: random-access memory, abbreviation) :RAM); the fourth memory 2703 may also be a non-volatile memory (English: non-volatile memory), such as read-only memory (English: read-only memory, abbreviation: ROM), flash memory (English: flash memory) , hard disk drive (English: hard disk drive, abbreviated: HDD) or solid state drive (English: solid-state drive, abbreviated: SSD), or fourth memory 2703 is capable of carrying or storing the desired form of instruction or data structure. Program code and any other medium that can be accessed by a computer, but is not limited thereto.
  • the fourth memory 2703 may be a combination of the above memories.
  • the fourth transceiver 2701 is configured to send a first message to the base station, where the first message carries indication information about whether the UE needs to receive downlink data.
  • the fourth transceiver 2701 is configured to: when the fourth processor 2702 determines that the downlink data does not need to be received, send the uplink data to be sent to the base station, and the fourth processor 2702 carries the Endmarker indication packet in the last uplink packet, in the fourth After the transceiver 1701 sends the last uplink data packet, the RRC connection is released; and/or the fourth transceiver 2701 is configured to receive, after the fourth processor 2702 determines that the downlink data needs to be received, after receiving the uplink data to be sent, Downstream data; the fourth processor 2702 is configured to release the RRC connection after parsing into the received downlink data packet that includes the Endmarker indication packet.
  • the fourth processor 2702 is further configured to carry an Endmarker indication packet on a PDCP header of a last uplink data packet to be sent uplink data.
  • an RRC connection release device 2800 includes:
  • the device includes a fifth transceiver 2801, a fifth processor 2802, and a fifth memory 2803.
  • the fifth transceiver 2801, the fifth processor 2802, and the fifth memory 2803 are connected to each other.
  • the specific connecting medium between the above components is not limited in the embodiment of the present invention.
  • the embodiment of the present invention is connected in FIG. 28 between the fifth memory 2803, the fifth processor 2802, and the fifth transceiver 2801 via a bus 2804.
  • the bus is indicated by a thick line in FIG. 28, and the connection manner between other components is It is for illustrative purposes only and is not intended to be limiting.
  • the bus can be divided into an address bus, a data bus, a control bus, and the like.
  • Figure 28 is shown with only one thick line, but does not indicate that there is only one bus or one type of bus.
  • the fifth memory 2803 is configured to store the program code executed by the fifth processor 2802, and may be a volatile memory, such as a random access memory (English: random-access memory, abbreviation) :RAM); the fifth memory 2803 may also be a non-volatile memory (English: non-volatile memory), such as read-only memory (English: read-only memory, abbreviation: ROM), flash memory (English: flash memory) , hard disk drive (English: hard disk drive, abbreviated: HDD) or solid state drive (English: solid-state drive, abbreviated: SSD), or fifth memory 2803 is capable of carrying or storing the desired form of instruction or data structure. Program code and any other medium that can be accessed by a computer, but is not limited thereto.
  • the fifth memory 2803 may be a combination of the above memories.
  • the fifth transceiver 2801 is configured to receive a first message sent by the UE, where the first message carries indication information about whether the UE needs to receive downlink data.
  • the fifth transceiver 2801 is configured to receive the uplink data to be sent sent by the UE when the fifth processor 2802 determines that the indication information indicates that the UE does not need to receive downlink data, and the fifth processor 2802 is configured to parse the received uplink data packet.
  • the RRC connection with the UE is released; and/or the fifth transceiver 2801 is configured to determine, in the fifth processor 2802, that the indication information indicates that the UE needs to receive downlink data, and the uplink to be sent sent by the UE After the data is received, the downlink data is sent to the UE; the fifth processor 2802 is configured to carry the Endmarker indication packet in the last downlink data packet when the fifth transceiver sends the last downlink data packet, and the fifth transceiver The device 2801 sends the last downlink data packet carrying the Endmarker indication packet to the UE, and releases the UE with the UE. RRC connection.
  • it also includes:
  • the fifth processor 2802 is further configured to: after determining that the indication information indicates that the UE does not need to receive the downlink data, after parsing the Endmarker indication packet in the uplink data to be sent sent by the UE, the last uplink data packet to be sent in the uplink data is to be sent.
  • the general packet radio service technology tunneling protocol GTP carries an Endmarker indication packet to the serving gateway S-GW; and/or
  • the Endmarker indication packet is carried in the last downlink data packet, and the fifth processor 2802 is further configured to:
  • the Endmarker indication packet will be carried on the PDCP header of the last downstream packet.
  • an RRC connection release device 2900 includes:
  • the device includes a sixth transceiver 2901, a sixth processor 2902, and a sixth memory 2903.
  • the sixth transceiver 2901, the sixth processor 2902, and the sixth memory 2903 are connected to each other.
  • the specific connecting medium between the above components is not limited in the embodiment of the present invention.
  • the embodiment of the present invention is connected in FIG. 29 between the sixth memory 2903, the sixth processor 2902, and the sixth transceiver 2901 via a bus 2904.
  • the bus is indicated by a thick line in FIG. 29, and the connection manner between other components is It is for illustrative purposes only and is not intended to be limiting.
  • the bus can be divided into an address bus, a data bus, a control bus, and the like.
  • Figure 29 is shown with only one thick line, but does not indicate that there is only one bus or one type of bus.
  • the sixth memory 2903 is configured to store the program code executed by the sixth processor 2902, and may be a volatile memory, such as a random access memory (English: random-access memory, abbreviation) :RAM); the sixth memory 2903 may also be a non-volatile memory (English: non-volatile memory), such as read-only memory (English: read-only memory, abbreviation: ROM), flash memory (English: flash memory) , hard disk drive (English: hard disk drive, abbreviated: HDD) or solid state drive (English: solid-state drive, abbreviated: SSD), or sixth memory 2903 is capable of carrying or storing the desired form of instruction or data structure Program code and any other medium that can be accessed by a computer, but is not limited thereto.
  • the sixth memory 2903 may be a combination of the above memories.
  • the sixth transceiver 2901 is configured to report an application message to the network side device, where the application message carries an application layer protocol type of the UE;
  • the sixth processor 2902 is configured to release the RRC connection after completing all data packets that need to be interacted with the application layer protocol type with the network side device.
  • the application layer protocol type is Transmission Control Protocol and Hypertext Transfer Protocol TCP/HTTP, or User Datagram Protocol UDP.
  • a network side device 3000 includes:
  • the device includes a seventh transceiver 3001, a seventh processor 3002, and a seventh memory 3003.
  • the seventh transceiver 3001, the seventh processor 3002, and the seventh memory 3003 are connected to each other.
  • the specific connecting medium between the above components is not limited in the embodiment of the present invention.
  • the embodiment of the present invention is connected in FIG. 30 between the seventh memory 3003, the seventh processor 3002, and the seventh transceiver 3001 via a bus 3004.
  • the bus is indicated by a thick line in FIG. 30, and the connection manner between other components is It is for illustrative purposes only and is not intended to be limiting.
  • the bus can be divided into an address bus, a data bus, a control bus, and the like.
  • Figure 30 is shown with only one thick line, but does not indicate that there is only one bus or one type of bus.
  • the seventh memory 3003 is configured to store the program code executed by the seventh processor 3002, and may be a volatile memory, such as a random access memory (English: random-access memory, abbreviation) :RAM); the seventh memory 3003 may also be a non-volatile memory (English: non-volatile memory), such as read-only memory (English: read-only memory, abbreviation: ROM), flash memory (English: flash memory) , hard disk drive (English: hard disk drive, abbreviated: HDD) or solid state drive (English: solid-state drive, abbreviated: SSD), or seventh memory 3003 is capable of carrying or storing the desired form of instruction or data structure. Program code and any other medium that can be accessed by a computer, but is not limited thereto.
  • the seventh memory 3003 may be a combination of the above memories.
  • the seventh transceiver 3001 is configured to receive an application message reported by the UE, where the application message carries the UE Application layer protocol type;
  • the seventh processor 3002 is configured to determine, according to an application layer protocol type, a number of transport data packets corresponding to an application layer protocol type;
  • a seventh transceiver configured to receive a data packet transmitted by the UE for an application layer protocol type
  • a seventh processor configured to process a data packet transmitted by the UE for an application layer protocol type, and record the number of processed data packets
  • the UE sends a first message to the base station, where the first message carries a preset RRC release time determination parameter or a first RRC release time; if the UE carries the first RRC release time in the first message, the UE releases according to the first RRC.
  • the base station determines the timing duration of the second timer according to the first message, and sends the indication information of the timing duration of the second timer to the MME.
  • the UE, the base station, and the MME respectively set the first timer, the second timer, and the third timer according to the RRC release time.
  • the UE determines that the first timer expires, the UE releases the RRC connection;
  • the base station determines that the second timer expires And releasing the RRC connection with the UE;
  • the MME determines that the third timer expires, it is determined that the UE releases the RRC connection, which greatly saves signaling overhead in the RRC release process.
  • the UE sends a first message to the base station, and carries the indication information of whether the UE needs to receive downlink data.
  • the UE sends the uplink data to be sent to the base station, and carries the Endmarker indication packet in the last uplink data packet, and after the last uplink data packet is sent, the UE releases the RRC connection, and the base station according to the base station
  • the indication information determines that the UE does not need to receive the downlink data, and resolves to the RRC after the Endmarker indication packet is included in the received uplink data packet.
  • the UE when the UE needs to receive the downlink data, after the uplink data transmission to be sent is completed, the UE receives the downlink data, and after the resolution of the received downlink data packet includes the Endmarker indication packet, releases the RRC connection.
  • the base station determines, according to the indication information, that the UE needs to receive the downlink data, and sends the last downlink data packet carrying the Endmarker indication packet to the UE, and releases the RRC connection with the UE, which greatly saves signaling during the RRC release process. Overhead.
  • the UE reports the application message carrying the application layer protocol type of the UE to the network side device, and after the network side device completes all the data packets that need to be exchanged for the application layer protocol type, releases the RRC connection; the network side device determines according to the application layer protocol type.
  • the RRC connection greatly saves the signaling overhead in the RRC release process.
  • embodiments of the present invention can be provided as a method, system, or computer program product. Accordingly, the present invention may take the form of an entirely hardware embodiment, an entirely software embodiment, or a combination of software and hardware. Moreover, the invention can take the form of a computer program product embodied on one or more computer-usable storage media (including but not limited to disk storage, CD-ROM, optical storage, etc.) including computer usable program code.
  • computer-usable storage media including but not limited to disk storage, CD-ROM, optical storage, etc.
  • the computer program instructions can also be stored in a computer readable memory that can direct a computer or other programmable data processing device to operate in a particular manner, such that the instructions stored in the computer readable memory produce an article of manufacture comprising the instruction device.
  • the device is implemented in a flow chart or Multiple processes and/or block diagrams The functions specified in one or more boxes.
  • These computer program instructions can also be loaded onto a computer or other programmable data processing device such that a series of operational steps are performed on a computer or other programmable device to produce computer-implemented processing for execution on a computer or other programmable device.
  • the instructions provide steps for implementing the functions specified in one or more of the flow or in a block or blocks of a flow diagram.

Landscapes

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

Abstract

一种RRC连接释放方法、装置及设备。该方法为：UE向基站发送第一消息，第一消息携带预设的RRC释放时间确定参数或第一RRC释放时间；若UE在第一消息中携带第一RRC释放时间，UE根据第一RRC释放时间设置第一定时器的定时时长并启动第一定时器；或者若UE在第一消息中携带预设的RRC释放时间确定参数，UE接收基站针对第一消息反馈的响应消息，其中，响应消息携带基站根据预设的RRC释放时间确定参数确定的第二RRC释放时间；UE根据第二RRC释放时间设置第一定时器的定时时长并启动第一定时器；UE在第一定时器超时时释放RRC连接，极大地节省了RRC释放过程中的信令开销。

Description

一种RRC连接释放方法、装置及设备 技术领域
本发明涉及通信技术领域，特别是涉及一种RRC连接释放方法、装置及设备。
背景技术
用户设备(User Equipment，UE)在空口有两种无线资源控制(Radio Resource Control，RRC)状态：空闲态(IDLE)和连接态(Connected)。当UE需要进行业务传输时，首先需要与网络侧设备建立连接，即RRC连接建立，UE从空闲态进入到连接态，然后进行业务数据的传输。当UE完成业务数据传输后，处于连接态的UE如果长时间没有数据传输，不活动定时器(inactivity timer)超时，UE需要与网络侧设备释放RRC连接，即RRC连接释放，UE从连接态进入到空闲态。当有下行数据到达或上行数据到达时，UE需要重新建立RRC连接，以及在完成数据传输后，UE如果长时间没有数据传输，不活动定时器超时，UE需要释放RRC连接，因此，在UE的空口状态转换过程中，即空闲态和连接态之间的转换过程中会产生较多的信令开销。
蜂窝物联网(Cellular Internet of Things，CIoT)是基于长期演进***(Long Term Evolution，LTE)的新技术，对数据速率要求不高，能提供更大的覆盖增益和联接能力。在CIoT中，终端数量巨大，主要进行小包传输，即终端传输的数据包较小。随着通讯需求的频繁增长和终端数量的增加，RRC连接建立和RRC连接释放所造成的信令开销数量将会出现更加明显地增长，网络侧设备也需要更多的处理资源来处理这些控制信令，进而导致网络侧设备超负荷。
现有技术中，已经有针对UE和eNB在RRC连接建立过程中如何减少RRC信令开销的方法，具体的，UE和eNB在RRC连接被释放后，双方仍然 保留UE的上下文信息。当有下行数据到达或上行数据到达时，UE需要重新进入连接态，UE和eNB分别使用存储的UE上下文信息进行RRC连接建立。采用这种方法在UE与eNB的RRC连接建立过程中，无需再进行安全激活、承载建立等操作，从而减少RRC连接建立过程中的信令开销，并减轻了网络负载。在UE完成数据传输后，UE如果长时间没有数据传输，不活动定时器超时，UE释放RRC连接，保存本次连接的上下文信息，但是在RRC连接释放过程中还是会造成大量的信令开销。
发明内容
本发明实施例提供一种RRC连接释放方法、装置及设备，用以解决在RRC连接释放流程中所需信令数较多，导致网络负载较重的问题。
本发明实施例提供的具体技术方案如下：
第一方面，一种RRC连接释放方法，包括：
用户设备UE向基站发送第一消息，所述第一消息携带预设的RRC释放时间确定参数或第一RRC释放时间；
若所述UE在所述第一消息中携带所述第一RRC释放时间，所述UE根据所述第一RRC释放时间设置第一定时器的定时时长，并启动所述第一定时器；或者若所述UE在所述第一消息中携带所述预设的RRC释放时间确定参数，所述UE接收所述基站针对所述第一消息反馈的响应消息，其中，所述响应消息携带所述基站根据所述预设的RRC释放时间确定参数确定的第二RRC释放时间；所述UE根据所述第二RRC释放时间设置所述第一定时器的定时时长，并启动所述第一定时器；
所述UE在所述第一定时器超时时，释放RRC连接。
结合第一方面，在第一方面的第一种可能的实现方式中，所述预设的RRC释放时间确定参数为所述UE的待发送上行数据的数据量和/或所述待发送上行数据的发送预估时间。
结合第一方面或第一方面的第一种可能的实现方式，在第一方面的第二 种可能的实现方式中，所述UE在所述第一定时器超时之前，还包括：
所述UE上报缓冲状态报告BSR至所述基站，所述BSR用于指示所述基站调整第二定时器的定时时长，其中，所述第二定时器的定时时长是所述基站根据所述UE发送的所述第一消息设置的；
所述UE接收所述基站回复的第一调整指示，并根据所述第一调整指示，调整所述第一定时器的定时时长。
第二方面，一种RRC连接释放方法，包括：
基站接收UE发送的第一消息，所述第一消息携带预设的RRC释放时间确定参数或第一RRC释放时间；
若所述基站确定所述第一消息中携带所述第一RRC释放时间，所述基站根据所述第一RRC释放时间设置第二定时器的定时时长，并启动所述第二定时器；或者若所述基站确定所述第一消息中携带所述预设的RRC释放时间确定参数，所述基站根据所述预设的RRC释放时间确定参数确定第二RRC释放时间，并在针对所述第一消息反馈给所述UE的响应消息中携带所述第二RRC释放时间；所述基站根据所述第二RRC释放时间设置所述第二定时器的定时时长，并启动所述第二定时器；
所述基站在所述第二定时器超时时，释放与所述UE之间的RRC连接。
结合第二方面，在第二方面的第一种可能的实现方式中，所述预设的RRC释放时间确定参数为所述UE的待发送上行数据的数据量和/或所述待发送上行数据的发送预估时间。
结合第二方面或第二方面的第一可能的实现方式，在第二方面的第二种可能的实现方式中，所述基站在所述第二定时器超时之前，还包括：
若所述基站接收到所述UE上报的BSR，并根据所述BSR对所述第二定时器的定时时长进行调整；
所述基站根据所述第二定时器的定时时长调整结果生成第一调整指示回复至所述UE，以及生成第二调整指示通知给移动管理实体MME。
结合第二方面或第二方面的第一可能的实现方式，在第二方面的第三种 可能的实现方式中，在所述基站反馈所述响应消息至所述UE之后，还包括：
所述基站接收所述UE发送的针对所述响应消息的确认消息后，发送S1连接恢复指示信息至MME，所述S1连接恢复指示信息携带所述第二定时器的定时时长；
所述基站接收所述MME发送的S1连接恢复的确认指示信息；
所述基站根据所述S1连接恢复的确认指示信息确定已恢复所述基站与所述MME之间的S1连接。
第三方面，一种RRC连接释放方法，包括：
移动管理实体MME接收基站发送的S1连接恢复指示信息，所述S1连接恢复指示信息携带第二定时器的定时时长，其中，所述第二定时器的定时时长是所述基站根据UE发送的第一消息设置的，所述第一消息携带预设的RRC释放时间确定参数或第一RRC释放时间；
所述MME根据所述第二定时器的定时时长设置第三定时器的定时时长，并启动所述第三定时器；
所述MME在所述第三定时器超时时，确定所述UE释放RRC连接。
结合第三方面，在第三方面的第一种可能的实现方式中，在MME接收基站发送的S1连接恢复指示信息之后，还包括：
所述MME根据所述S1连接恢复指示消息确定恢复与所述基站之间的S1连接；
所述MME向所述基站发送S1连接恢复的确认指示信息。
结合第三方面，在第三方面的第二种可能的实现方式中，所述MME在所述第三定时器超时之前，还包括：
若所述MME接收到所述基站发送的第二调整指示，则根据所述第二调整指示调整所述第三定时器的定时时长。
第四方面，一种RRC连接释放方法，包括：
UE向基站发送第一消息，所述第一消息携带所述UE是否需要接收下行数据的指示信息；
所述UE在不需要接收下行数据时，发送待发送上行数据至所述基站，并在最后一个上行数据包中携带端点标记Endmarker指示包，所述UE在发送完所述最后一个上行数据包后，释放RRC连接；和/或所述UE在需要接收下行数据时，在所述待发送上行数据发送完成后，接收下行数据，并在解析到接收的下行数据包中包含Endmarker指示包后，释放RRC连接。
结合第四方面，在第四方面的第一种可能的实现方式中，所述UE在待发送上行数据的最后一个上行数据包的分组数据汇聚协议PDCP头上携带Endmarker指示包。
第五方面，一种RRC连接释放方法，包括：
基站接收UE发送的第一消息，所述第一消息携带所述UE是否需要接收下行数据的指示信息；
所述基站确定所述指示信息指示所述UE不需要接收下行数据时，接收所述UE发送的待发送上行数据，并在解析到接收的上行数据包中包含Endmarker指示包后，释放与所述UE之间的RRC连接；和/或
所述基站确定所述指示信息指示所述UE需要接收下行数据，在所述UE发送的所述待发送上行数据接收完成后，继续发送下行数据至所述UE，并在发送到最后一个下行数据包时，在所述最后一个下行数据包中携带Endmarker指示包，并将携带Endmarker指示包的最后一个下行数据包发送至所述UE后，所述基站释放与所述UE之间的RRC连接。
结合第五方面，在第五方面的第一种可能的实现方式中，还包括：
所述基站确定所述指示信息指示所述UE不需要接收下行数据时，在从所述UE发送的所述待发送上行数据中解析出Endmarker指示包后，所述基站将在所述待发送上行数据的最后一个上行数据包的通用分组无线服务技术隧道协议GTP头上携带所述Endmarker指示包发往服务网关S-GW；和/或
所述基站在所述指示信息指示所述UE需要接收下行数据时，所述基站在所述最后一个下行数据包中携带Endmarker指示包，包括：
所述基站在从所述S-GW发送的下行数据中解析出Endmarker指示包后， 确认已接收到最后一个下行数据包；
所述基站将在所述最后一个下行数据包的PDCP头上携带所述Endmarker指示包。
第六方面，一种RRC连接释放方法，包括：
UE上报应用消息至网络侧设备，所述应用消息携带所述UE的应用层协议类型；
所述UE在与所述网络侧设备完成针对所述应用层协议类型需要交互的所有数据包后，释放RRC连接。
结合第六方面，在第六方面的第一种可能的实现方式中，所述应用层协议类型为传输控制协议和超文本传输协议TCP/HTTP，或者用户数据报协议UDP。
第七方面，一种RRC连接释放方法，包括：
网络侧设备接收UE上报的应用消息，所述应用消息携带所述UE的应用层协议类型；
所述网络侧设备根据所述应用层协议类型，确定所述应用层协议类型对应的传输数据包的个数；
所述网络侧设备接收并处理所述UE针对所述应用层协议类型传输的数据包，并记录处理的数据包个数；
当所述网络侧设备确定记录的数据包个数达到所述应用层协议类型对应的传输数据包的个数时，所述网络侧设备释放与所述UE之间的RRC连接。
第八方面，一种RRC连接释放装置，包括：
第一发送单元，用于向基站发送第一消息，所述第一消息携带预设的RRC释放时间确定参数或第一RRC释放时间；
第一处理单元，用于在所述第一消息中携带所述第一RRC释放时间时，根据所述第一RRC释放时间设置第一定时器的定时时长，并启动所述第一定时器；或者第一接收单元，用于接收所述基站针对所述第一消息反馈的响应消息，其中，所述响应消息携带所述基站根据所述预设的RRC释放时间确定 参数确定的第二RRC释放时间；所述第一处理单元，用于在所述第一消息中携带所述预设的RRC释放时间确定参数时，根据所述第二RRC释放时间设置所述第一定时器的定时时长，并启动所述第一定时器；
第一判断单元，用于在所述第一定时器超时时，释放RRC连接。
结合第八方面，在第八方面的第一种可能的实现方式中，所述预设的RRC释放时间确定参数为所述装置的待发送上行数据的数据量和/或所述待发送上行数据的发送预估时间。
结合第八方面或第八方面的第一种可能的实现方式，在第八方面的第二种可能的实现方式中，还包括：
所述第一发送单元，还用于上报BSR至所述基站，所述BSR用于指示所述基站调整第二定时器的定时时长，其中，所述第二定时器的定时时长是所述基站根据所述UE发送的所述第一消息设置的；
所述第一接收单元，还用于接收所述基站回复的第一调整指示；
所述第一处理单元，还用于在接收到所述基站回复的第一调整指示时，根据所述第一调整指示，调整所述第一定时器的定时时长。
第九方面，一种RRC连接释放装置，包括：
第二接收单元，用于接收UE发送的第一消息，所述第一消息携带预设的RRC释放时间确定参数或第一RRC释放时间；
第二处理单元，用于确定所述第一消息中携带所述第一RRC释放时间时，根据所述第一RRC释放时间设置第二定时器的定时时长，并启动所述第二定时器；或者所述第二处理单元，用于确定所述第一消息中携带所述预设的RRC释放时间确定参数，根据所述预设的RRC释放时间确定参数确定第二RRC释放时间，并根据所述第二RRC释放时间设置所述第二定时器的定时时长，并启动所述第二定时器；所述第二发送单元，用于针对所述第一消息给所述UE反馈响应消息，所述响应消息中携带所述第二RRC释放时间；
第二判断单元，用于在所述第二定时器超时时，所述基站释放与所述UE之间的RRC连接。
结合第九方面，在第九方面的第一种可能的实现方式中，所述预设的RRC释放时间确定参数为所述UE的待发送上行数据的数据量和/或所述待发送上行数据的发送预估时间。
结合第九方面或第九方面的第一种可能的实现方式，在第九方面的第二可能的实现方式中，还包括：
所述第二接收单元，还用于接收所述UE上报的BSR；
所述第二处理单元，还用于在接收到所述UE上报的BSR时，对所述第二定时器的定时时长进行调整，并根据所述第二定时器的定时时长调整结果生成第一调整指示以及第二调整指示；
所述第二发送单元，还用于将所述第一调整指示回复至所述UE，将所述第二调整指示通知给MME。
结合第九方面或第九方面的第一种可能的实现方式，在第九方面的第三种可能的实现方式中，还包括：
所述第二接收单元，还用于接收所述UE发送的针对所述响应消息的确认消息；
所述第二发送单元，还用于在所述第二接收单元接收到所述UE发送的针对所述响应消息的确认消息之后，发送S1连接恢复指示信息至MME，所述S1连接恢复指示信息携带所述第二定时器的定时时长；
所述第二接收单元，还用于接收所述MME发送的S1连接恢复的确认指示信息；
所述第二处理单元，还用于根据所述S1连接恢复的确认指示信息确定已恢复所述基站与所述MME之间的S1连接。
第十方面，一种RRC连接释放装置，包括：
第三接收单元，用于接收基站发送的S1连接恢复指示信息，所述S1连接恢复指示信息携带第二定时器的定时时长，其中，所述第二定时器的定时时长是所述基站根据UE发送的第一消息设置的，所述第一消息携带预设的RRC释放时间确定参数或第一RRC释放时间；
第三处理单元，用于根据所述第二定时器的定时时长设置第三定时器的定时时长，并启动所述第三定时器；
第三判断单元，用于在所述第三定时器超时时，确定所述UE释放RRC连接。
结合第十方面，在第十方面的第一种可能的实现方式中，还包括：
所述第三处理单元，用于根据所述S1连接恢复指示信息确定恢复与所述基站之间的S1连接；
第三发送单元，用于向所述基站发送S1连接恢复的确认指示信息。
结合第十方面，在第十方面的第二种可能的实现方式中，所述第三接收单元，还用于接收所述基站发送的第二调整指示；
所述第三处理单元，还用于在所述第三接收单元接收到所述基站发送的第二调整指示时，根据所述第二调整指示调整所述第三定时器的定时时长。
第十一方面，一种RRC连接释放装置，其特征在于，包括：
第四发送单元，用于向基站发送第一消息，所述第一消息携带所述UE是否需要接收下行数据的指示信息；
第四发送单元，用于在第四处理单元确定不需要接收下行数据时，发送待发送上行数据至所述基站，所述第四处理单元，用于在最后一个上行数据包中携带Endmarker指示包，并在所述第四发送单元发送完所述最后一个上行数据包后，释放RRC连接；和/或所述第四发送单元，用于在所述第四处理单元确定需要接收下行数据时，发送待发送上行数据至所述基站，第四接收单元，用于在所述第四处理单元确定所述待发送上行数据发送完成后，接收下行数据，所述第四处理单元，用于在解析到所述第四接收单元接收的下行数据包中包含Endmarker指示包后，释放RRC连接。
结合第十一方面，在第十一方面的第一种可能的实现方式中，所述第四处理单元还用于在待发送上行数据的最后一个上行数据包的PDCP头上携带Endmarker指示包。
第十二方面，一种RRC连接释放装置，包括：
第五接收单元，用于接收UE发送的第一消息，所述第一消息携带所述UE是否需要接收下行数据的指示信息；
第五接收单元，用于在第五处理单元确定所述指示信息指示所述UE不需要接收下行数据时，接收所述UE发送的待发送上行数据；所述在第五处理单元，用于在解析到所述第五接收单元接收的上行数据包中包含Endmarker指示包后，释放与所述UE之间的RRC连接；和/或所述第五接收单元，用于在所述第五处理单元确定所述指示信息指示所述UE需要接收下行数据；第五发送单元，用于在所述UE发送的所述待发送上行数据由所述第五接收单元接收完成后，继续发送下行数据至所述UE；所述在第五处理单元，用于在所述第五发送单元发送到最后一个下行数据包时，在所述最后一个下行数据包中携带Endmarker指示包，并将携带Endmarker指示包的最后一个下行数据包发送至所述UE后，释放与所述UE之间的RRC连接。
结合第十二方面，在第十二方面的第一种可能的实现方式中，还包括：
所述第五处理单元还用于确定所述指示信息指示所述UE不需要接收下行数据时，在从所述UE发送的所述待发送上行数据中解析出Endmarker指示包后，将在所述待发送上行数据的最后一个上行数据包的通用分组无线服务技术隧道协议GTP头上携带所述Endmarker指示包发往服务网关S-GW；和/或
在所述指示信息指示所述UE需要接收下行数据时，在所述最后一个下行数据包中携带Endmarker指示包，所述第五处理单元还用于：
在从所述S-GW发送的下行数据中解析出Endmarker指示包后，确认已接收到最后一个下行数据包；
将在所述最后一个下行数据包的PDCP头上携带所述Endmarker指示包。
第十三方面，一种RRC连接释放装置，包括：
第六发送单元，用于上报应用消息至网络侧设备，所述应用消息携带所述UE的应用层协议类型；
第六判断单元，用于在与所述网络侧设备完成针对所述应用层协议类型 需要交互的所有数据包后，释放RRC连接。
结合第十三方面，在第十三方面的第一种可能的实现方式中，所述应用层协议类型为传输控制协议和超文本传输协议TCP/HTTP，或者用户数据报协议UDP。
第十四方面，一种RRC连接释放装置，包括：
第七接收单元，用于接收UE上报的应用消息，所述应用消息携带所述UE的应用层协议类型；
确定单元，用于根据所述应用层协议类型，确定所述应用层协议类型对应的传输数据包的个数；
计数单元，用于接收并处理所述UE针对所述应用层协议类型传输的数据包，并记录处理的数据包个数；
第七判断单元，用于当确定记录的数据包个数达到所述应用层协议类型对应的传输数据包的个数时，释放与所述UE之间的RRC连接。
第十五方面，一种RRC连接释放设备，包括：
第一收发器，用于向基站发送第一消息，所述第一消息携带预设的RRC释放时间确定参数或第一RRC释放时间；
第一处理器，用于在所述第一消息中携带所述第一RRC释放时间时，根据所述第一RRC释放时间设置第一定时器的定时时长，并启动所述第一定时器；或者所述第一收发器，用于在所述第一消息中携带所述预设的RRC释放时间确定参数时，接收所述基站针对所述第一消息反馈的响应消息，其中，所述响应消息携带所述基站根据所述预设的RRC释放时间确定参数确定的第二RRC释放时间；所述第一处理器，用于根据所述第二RRC释放时间设置所述第一定时器的定时时长，并启动所述第一定时器；
所述第一处理器，还用于在所述第一定时器超时时，释放RRC连接。
结合第十五方面，在第十五方面的第一种可能的实现方式中，所述预设的RRC释放时间确定参数为所述UE的待发送上行数据的数据量和/或所述待发送上行数据的发送预估时间。
结合第十五方面或第十五方面的第一种可能的实现方式，在第十五方面的第二种可能的实现方式中，所述第一收发器，还用于上报BSR至所述基站，所述BSR用于指示所述基站调整第二定时器的定时时长，其中，所述第二定时器的定时时长是所述基站根据所述UE发送的所述第一消息设置的；以及接收所述基站回复的第一调整指示；
所述第一处理器，还用于在接收到所述基站回复的第一调整指示时，根据所述第一调整指示，调整所述第一定时器的定时时长。
第十六方面，一种RRC连接释放设备，其特征在于，包括：
第二收发器，用于接收UE发送的第一消息，所述第一消息携带预设的RRC释放时间确定参数或第一RRC释放时间；
第二处理器，用于确定所述第一消息中携带所述第一RRC释放时间时，根据所述第一RRC释放时间设置第二定时器的定时时长，并启动所述第二定时器；或者所述第二处理器，用于确定所述第一消息中携带所述预设的RRC释放时间确定参数，根据所述预设的RRC释放时间确定参数确定第二RRC释放时间，并根据所述第二RRC释放时间设置所述第二定时器的定时时长，并启动所述第二定时器；所述第二收发器，用于针对所述第一消息给所述UE反馈响应消息，所述响应消息中携带所述第二RRC释放时间；
所述第二处理器，还用于在所述第二定时器超时时，释放与所述UE之间的RRC连接。
结合第十六方面，在第十六方面的第一种可能的实现方式中，还包括：
所述第二收发器，还用于接收所述UE上报的BSR；
所述第二处理器，还用于在所述第二收发器接收到所述UE上报的BSR时，对所述第二定时器的定时时长进行调整，并根据所述第二定时器的定时时长调整结果生成第一调整指示以及第二调整指示；
所述第二收发器，还用于将所述第一调整指示回复至所述UE，将所述第二调整指示通知给MME。
结合第十六方面，在第十六方面的第二种可能的实现方式中，所述第二 收发器，还用于接收所述UE发送的针对所述响应消息的确认消息，并在接收到所述UE发送的针对所述响应消息的确认消息之后，发送S1连接恢复指示信息至MME，所述S1连接恢复指示信息携带所述第二定时器的定时时长；以及接收所述MME发送的S1连接恢复的确认指示信息；
所述第二处理器，用于根据所述S1连接恢复的确认指示信息确定已恢复所述基站与所述MME之间的S1连接。
第十七方面，一种RRC连接释放设备，包括：
第三收发器，用于接收基站发送的S1连接恢复指示信息，所述S1连接恢复指示信息携带第二定时器的定时时长，其中，所述第二定时器的定时时长是所述基站根据UE发送的第一消息设置的，所述第一消息携带预设的RRC释放时间确定参数或第一RRC释放时间；
第三处理器，用于根据所述第二定时器的定时时长设置第三定时器的定时时长，并启动所述第三定时器；
以及用于在所述第三定时器超时时，确定所述UE释放RRC连接。
结合第十七方面，在第十七方面的第一种可能的实现方式中，还包括：
所述第三处理器，还用于根据所述S1连接恢复指示信息确定恢复与所述基站之间的S1连接；
所述第三收发器，还用于向所述基站发送S1连接恢复的确认指示信息。
结合第十七方面，在第十七方面的第二种可能的实现方式中，所述第三收发器，用于接收到所述基站发送的第二调整指示；
所述第三处理器，用于根据所述第二调整指示调整所述第三定时器的定时时长。
第十八方面，一种RRC连接释放设备，包括：
第四收发器，用于向基站发送第一消息，所述第一消息携带所述UE是否需要接收下行数据的指示信息；
所述第四收发器，用于在RRC连接释放设备不需要接收下行数据时，发送待发送上行数据至所述基站，所述第四处理器在最后一个上行数据包中携 带Endmarker指示包，在所述第四收发器发送完所述最后一个上行数据包后，释放RRC连接；和/或所述第四收发器用于在所述第四处理器确定需要接收下行数据时，将所述待发送上行数据发送完成后，接收下行数据；所述第四处理器，用于解析到接收的下行数据包中包含Endmarker指示包后，释放RRC连接。
结合第十八方面，在第十八方面的第一种可能的实现方式中，所述第四处理器还用于在待发送上行数据的最后一个上行数据包的PDCP头上携带Endmarker指示包。
第十九方面，一种基站，包括：
第五收发器，用于接收UE发送的第一消息，所述第一消息携带所述UE是否需要接收下行数据的指示信息；
所述第五收发器，用于在第五处理器确定所述指示信息指示所述UE不需要接收下行数据时，接收所述UE发送的待发送上行数据；所述第五处理器，用于解析到接收的上行数据包中包含Endmarker指示包后，释放与所述UE之间的RRC连接；和/或所述第五收发器，用于在所述第五处理器确定所述指示信息指示所述UE需要接收下行数据，在所述UE发送的所述待发送上行数据接收完成后，继续发送下行数据至所述UE；所述第五收发器，用于在所述第五收发器发送到最后一个下行数据包时，在所述最后一个下行数据包中携带Endmarker指示包，在所述第五收发器将携带Endmarker指示包的最后一个下行数据包发送至所述UE后，释放与所述UE之间的RRC连接。
结合第十九方面，在第十九方面的第一种可能的实现方式中，还包括：
所述第五处理器还用于确定所述指示信息指示所述UE不需要接收下行数据时，在从所述UE发送的所述待发送上行数据中解析出Endmarker指示包后，将在所述待发送上行数据的最后一个上行数据包的通用分组无线服务技术隧道协议GTP头上携带所述Endmarker指示包发往服务网关S-GW；和/或
在所述指示信息指示所述UE需要接收下行数据时，在所述最后一个下行数据包中携带Endmarker指示包，所述第五处理器还用于：
在从所述S-GW发送的下行数据中解析出Endmarker指示包后，确认已接收到最后一个下行数据包；
将在所述最后一个下行数据包的PDCP头上携带所述Endmarker指示包。
第二十方面，一种RRC连接释放设备，包括：
第六收发器，用于上报应用消息至网络侧设备，所述应用消息携带所述UE的应用层协议类型；
第六处理器，用于在与所述网络侧设备完成针对所述应用层协议类型需要交互的所有数据包后，释放RRC连接。
结合第二十方面，在第二十方面的第一种可能的实现方式中，所述应用层协议类型为传输控制协议和超文本传输协议TCP/HTTP，或者用户数据报协议UDP。
第二十一方面，一种RRC连接释放设备，包括：
第七收发器，用于接收UE上报的应用消息，所述应用消息携带所述UE的应用层协议类型；
第七处理器，用于根据所述应用层协议类型，确定所述应用层协议类型对应的传输数据包的个数；
所述第七收发器，用于接收所述UE针对所述应用层协议类型传输的数据包；
所述第七处理器，用于处理所述UE针对所述应用层协议类型传输的数据包，并记录处理的数据包个数；
以及当确定记录的数据包个数达到所述应用层协议类型对应的传输数据包的个数时，释放与所述UE之间的RRC连接。
基站接收每个UE上报UE的类型和/或业务类型，基站接收至少两个UE发送的数据包，基站根据每个UE对应上报的UE的类型和/或业务类型，对满足预设条件的UE的数据包进行级联。
预设条件是指针对特定UE或特定的业务。基站将级联后的数据包通过在公共的通道上进行传输。该公共的通道可以是默认承载建立过程中建成的， 基站选择其中一条默认承载的通道作为公共的通道，或者，基站在确定UE满足预设条件后请求建立一条新的承载通道。
基站对满足预设条件的不同UE的数据包进行级联时，基于UE的IP地址识别不同UE的数据包或者基于UE的GTP IP+GTP TEID识别不同UE的数据包。
在基站将满足预设条件的不同UE的数据包进行级联之前，基站接收MME发送的携带每个UE的IP地址的通知消息。
因此，本发明实施例中基站将不同UE的数据包进行级联，然后将级联后的数据包放在公共的通道上进行传输，减少了传输负荷且提高传输效率。
eNB和UE保留UE的上下文信息，包括RRC配置，承载配置，安全上下文等，以及加入预设的寻呼相关信息，包括用户标识、TA Lists、UE默认的寻呼周期及eNB在***消息中的广播寻呼周期
eNB根据上下文信息中记录的预设的寻呼相关信息便能根据用户标识确定待寻呼的UE，以及根据TA Lists确定寻呼区域，并从UE默认的寻呼周期和***消息中的广播寻呼周期两者中选择较小的寻呼周期用来确定eNB在空口寻呼UE的时机。当寻呼时机到达时，eNB给该UE发送寻呼消息。
本发明实施例提供的方法，解决了针对静止的UE，UE释放RRC连接后，eNB与MME间的S1接口可能保持连接，当S1接口保持连接时，MME不再给eNB发送寻呼消息，此时eNB无法在空口寻呼UE的问题。
本发明有益效果如下：UE向基站发送第一消息，第一消息携带预设的RRC释放时间确定参数或第一RRC释放时间；若UE在第一消息中携带第一RRC释放时间，UE根据第一RRC释放时间设置第一定时器的定时时长并启动第一定时器；或者若UE在第一消息中携带预设的RRC释放时间确定参数，UE接收基站针对第一消息反馈的响应消息，其中，响应消息携带基站根据预设的RRC释放时间确定参数确定的第二RRC释放时间；UE根据第二RRC释放时间设置第一定时器的定时时长并启动第一定时器；UE在第一定时器超时时释放RRC连接，极大地节省了RRC释放过程中的信令开销。基站根据 第一消息确定第二定时器的定时时长，以及向MME发送携带第二定时器的定时时长的指示信息。UE、基站和MME根据RRC释放时间分别设置第一定时器、第二定时器和第三定时器，当UE确定第一定时器超时时，UE释放RRC连接；当基站确定第二定时器超时时，释放与UE之间的RRC连接；当MME确定第三定时器超时时，确定UE释放RRC连接，极大地节省了RRC释放过程中的信令开销。
UE向基站发送第一消息，携带UE是否需要接收下行数据的指示信息。当UE不需要接收下行数据时，UE发送待发送上行数据至基站，并在最后一个上行数据包中携带Endmarker指示包，UE在发送完最后一个上行数据包后，释放RRC连接，同时，基站根据指示信息确定UE不需要接收下行数据时，解析到接收的上行数据包中包含Endmarker指示包后，释放与UE之间的RRC连接；和/或当UE在需要接收下行数据时，在待发送上行数据发送完成后，UE接收下行数据，并在解析到接收的下行数据包中包含Endmarker指示包后，释放RRC连接。同时，基站根据指示信息确定UE需要接收下行数据时，将携带Endmarker指示包的最后一个下行数据包发送至UE后，释放与UE之间的RRC连接，极大地节省了RRC释放过程中的信令开销。
UE上报携带UE的应用层协议类型的应用消息至网络侧设备，在与网络侧设备完成针对应用层协议类型需要交互的所有数据包后，释放RRC连接；网络侧设备根据应用层协议类型，确定应用层协议类型对应的传输数据包的个数，并针对该应用层协议类型的传输数据包计数，当达到应用层协议类型对应的传输数据包的个数时，网络侧设备释放与UE之间的RRC连接，极大地节省了RRC释放过程中的信令开销。
附图说明
图1为本发明实施例中网络***架构图；
图2为本发明实施例中一种RRC连接释放概述流程图A1；
图3为本发明实施例中一种RRC连接释放概述流程图A2；
图4为本发明实施例中一种RRC连接释放概述流程图A3；
图5为本发明实施例中一种RRC连接释放的具体流程图A4；
图6为本发明实施例中一种RRC连接释放概述流程图B1；
图7为本发明实施例中一种RRC连接释放概述流程图B2；
图8为本发明实施例中一种RRC连接释放的具体流程图B3；
图9为本发明实施例中一种RRC连接释放的具体流程图B4；
图10为本发明实施例中一种RRC连接释放概述流程图C1；
图11为本发明实施例中HTTP/TCP的标准协议流程；
图12为本发明实施例中UDP的标准协议流程；
图13为本发明实施例中一种RRC连接释放概述流程图C2；
图14为本发明实施例中S1接口用户面协议栈示意图；
图15为本发明实施例中S1-U协议栈传输帧结构示意图；
图16为本发明实施例中eNB对UE上报的数据包进行级联并传输的流程图；
图17为本发明实施例中一种RRC连接释放装置1700结构示意图；
图18为本发明实施例中一种RRC连接释放装置1800结构示意图；
图19为本发明实施例中一种RRC连接释放装置1900结构示意图；
图20为本发明实施例中一种RRC连接释放装置2000结构示意图；
图21为本发明实施例中一种RRC连接释放装置2100结构示意图；
图22为本发明实施例中一种RRC连接释放装置2200结构示意图；
图23为本发明实施例中一种RRC连接释放装置2300结构示意图；
图24为本发明实施例中一种RRC连接释放设备2400；
图25为本发明实施例中一种RRC连接释放设备2500；
图26为本发明实施例中一种RRC连接释放设备2600；
图27为本发明实施例中一种RRC连接释放设备2700；
图28为本发明实施例中一种RRC连接释放设备2800；
图29为本发明实施例中一种RRC连接释放设备2900；
图30为本发明实施例中一种RRC连接释放设备3000。
具体实施方式
为使本发明实施例的目的、技术方案和优点更加清楚，下面将结合本发明实施例中的附图，对本发明实施例中的技术方案进行清楚、完整地描述，显然，所描述的实施例是本发明一部分实施例，而不是全部的实施例。基于本发明中的实施例，本领域普通技术人员在没有做出创造性劳动前提下所获得的所有其他实施例，都属于本发明保护的范围。
本发明实施例提供一种RRC连接释放方法、装置及设备，用以解决在RRC连接释放流程中所需信令数较多，导致网络负载较重的问题。其中，方法和装置是基于同一发明构思的，由于方法及装置解决问题的原理相似，因此装置与方法的实施可以相互参见，重复之处不再赘述。
下面结合附图对本发明优选的实施方式进行详细说明。
本发明实施例的主要应用场景为长期演进(Long term evolution，LTE)***，该***的***架构如图1所示，该***中主要包含的网元有：基站(Evolution Node B，eNB)，移动管理实体(Mobility Management Entity，MME)，服务网关(Serving Gateway，S-GW)和分组数据网络网关(PDN Gateway，P-GW)。
参阅图2所示，为本发明实施例提供的一种RRC连接释放概述流程图A1。
下面结合附图对本发明实施例的具体实施过程进行说明。
步骤210：UE向基站发送第一消息。
第一消息携带预设的RRC释放时间确定参数或第一RRC释放时间。
这里的第一RRC请求消息可以为一种新的消息，也可以携带在现有的RRC连接请求消息中。
预设的RRC释放时间确定参数为UE的待发送上行数据的数据量和/或待发送上行数据的发送预估时间。
步骤220：若UE在第一消息中携带第一RRC释放时间，UE根据第一RRC释放时间设置第一定时器的定时时长，并启动第一定时器；或者若UE在第一消息中携带预设的RRC释放时间确定参数，UE接收基站针对第一消息反馈的响应消息，其中，响应消息携带基站根据预设的RRC释放时间确定参数确定的第二RRC释放时间；UE根据第二RRC释放时间设置第一定时器的定时时长，并启动第一定时器；
其中，该响应消息携带基站根据UE发送的待发送上行数据的数据量和/或待发送上行数据的发送预估时间确定的第二RRC释放时间。
这里的的响应消息可以为一种新的消息，也可以携带在现有的RRC建立消息中。
步骤230：UE在第一定时器超时时，释放RRC连接。
此外，UE在第一定时器超时之前，UE还可以根据自身需要上报缓冲状态报告(Buffer Status Report，BSR)至基站，其中，BSR用于指示基站对第二定时器的定时时长，其中，第二定时器的定时时长是基站根据UE发送的第一消息设置的
UE接收基站回复的第一调整指示，例如，该指示中携带调整后的最新第二定时器的定时时长或者时间调整量△T。UE根据第一调整指示，调整第一定时器的定时时长。
例如，BSR在UE进行上行数据传输时上报，eNB根据BSR相应地调整第二定时器的定时时长，例如第二定时器的定时时长需要延长10S，并将该值通过第一调整指示通知UE，UE根据该指示调整第一定时器的定时时长，即第一定时器的定时时长加10S。
因此，UE在超时前，恢复与基站之间的RRC连接，重新进入连接态的UE进行上行数据发送，在UE确定超时后，释放RRC连接，节省了RRC释放过程中的信令开销。
参阅图3所示，为本发明实施例提供的一种RRC连接释放概述流程图A2。
步骤310：基站接收UE发送的第一消息。
第一消息携带预设的RRC释放时间确定参数或第一RRC释放时间。
预设的RRC释放时间确定参数为UE的待发送上行数据的数据量和/或待发送上行数据的发送预估时间。
这里的第一RRC请求消息可以为一种新的消息，也可以携带在现有的RRC连接请求消息中。
步骤320：若基站确定第一消息中携带第一RRC释放时间，基站根据第一RRC释放时间设置第二定时器的定时时长，并启动第二定时器；或者若基站确定第一消息中携带预设的RRC释放时间确定参数，基站根据预设的RRC释放时间确定参数确定第二RRC释放时间，并在针对第一消息反馈给UE的响应消息中携带第二RRC释放时间；基站根据第二RRC释放时间设置第二定时器的定时时长，并启动第二定时器。
例如，基站在确定第二RRC释放时间时，可以根据待发送上行数据的数据量确定UE发送上行数据需要的时间，并将确定的发送上行数据需要的时间作为第二RRC释放时间。
又例如，基站在确定第二RRC释放时间时，根据待发送上行数据的发送预估时间直接确定为RRC释放时间，或者，将该预估时间增加预设的时延作为第二RRC释放时间。
这里的响应消息可以为一种新的消息，也可以携带在现有的RRC建立消息中。
此外，基站反馈该响应消息至UE之后，接收UE发送的针对响应消息的确认消息，这里的确认消息可以为一种新的消息，也可以携带在现有的RRC连接建立完成消息中。
在基站接收UE发送的针对响应消息的确认消息后，基站发送S1恢复连接指示信息至MME，该S1恢复连接指示信息携带第二定时器的定时时长。
进一步地，基站接收MME发送的S1连接恢复的确认指示信息，根据该S1连接恢复的确认指示确定基站与MME之间的S1连接已恢复。
步骤330：基站在第二定时器超时时，基站释放与UE之间的RRC连接。
此外，基站在第二定时器超时之前，若基站接收到UE上报的BSR，则根据BSR对第二定时器的定时时长调整，并生成第一调整指示回复至UE，以及第二调整指示通知给MME。
因此，基站在超时前，恢复与UE之间的RRC连接，接收重新进入连接态的UE发送的上行数据，在基站确定超时后，释放与UE之间的RRC连接，节省了RRC释放过程中的信令开销。
参阅图4所示，为本发明实施例提供的一种RRC连接释放概述流程图A3。
步骤410：MME接收基站发送的S1连接恢复指示信息。
S1连接恢复指示信息携带第二定时器的定时时长，其中，第二定时器的定时时长是基站根据UE发送的第一消息设置的，第一消息携带预设的RRC释放时间确定参数或第一RRC释放时间。
在MME接收基站发送的S1连接恢复指示信息后，MME根据该S1连接恢复指示信息恢复与基站之间的S1连接，然后向基站发送S1连接恢复的确认指示信息。
步骤420：MME根据第二定时器的定时时长设置第三定时器的定时时长，并启动第三定时器；
步骤430：MME在第三定时器超时时，确定UE释放RRC连接。
MME在第三定时器超时之前，若MME接收到基站发送的第二调整指示，则根据第二调整指示调整第三定时器的定时时长。
参阅图5所示，为本发明实施例提供的RRC连接释放的具体流程图A4。
在UE上次释放RRC连接后，UE和eNB都会保留UE的上下文信息，当有下行数据到达(网络触发)或上行数据到达(UE触发)时，UE需要重新建立RRC连接。在UE与eNB的随机接入完成后：
步骤501：UE发送RRC连接请求消息至eNB，该请求消息中携带UE的待发送上行数据的数据量。
步骤502：eNB根据UE的待发送上行数据的数据量计算RRC释放时间，并将该RRC释放时间携带在RRC建立消息中发送至UE，以及根据RRC释放时间设置第二定时器，并启动第二定时器。
步骤503：UE根据接收到的RRC建立消息中携带的RRC释放时间，设置第一定时器，并启动第一定时器，以及向eNB发送RRC连接建立完成消息。
步骤504：eNB在接收到RRC连接建立完成消息后，发送S1连接恢复指示信息至MME，并在该S1连接恢复指示信息中携带RRC释放时间。
步骤505：MME回复S1连接恢复的确认指示消息至eNB，恢复与eNB之间的S1连接，以及根据RRC释放时间设置第三定时器，并启动第三定时器。
步骤506：UE发送待发送上行数据至网络侧设备。
步骤507：UE确定第一定时器超时，UE释放RRC连接；以及eNB确定第二定时器超时，释放与UE之间的RRC连接；以及MME确定第三定时器超时，确定UE释放RRC连接。
此外，在UE释放RRC连接时，UE和网络侧设备需要保留UE本次连接的上下文信息。
因此，UE发起RRC连接的重新恢复时，将RRC释放时间，在RRC连接的建立过程中进行配置，UE根据RRC释放时间进行定时，并在超时后释放RRC连接，网络侧设备也根据RRC释放时间进行定时，在超时后释放与UE之间的RRC连接，节省了RRC连接释放过程中的信令开销。
参阅图6所示，为本发明实施例提供的一种RRC连接释放概述流程图B1。
步骤610：UE向基站发送第一消息。
第一消息携带UE是否需要接收下行数据的指示信息。这里的第一消息可以为一种新的消息，也可以携带在现有的RRC连接请求消息中。
步骤620：UE在不需要接收下行数据时，发送待发送上行数据至基站， 并在最后一个上行数据包中携带端点标记Endmarker指示包，UE在发送完最后一个上行数据包后，释放RRC连接；和/或UE在需要接收下行数据时，在待发送上行数据发送完成后，接收下行数据，并在解析到接收的下行数据包中包含Endmarker指示包后，释放RRC连接。
具体的，这里包含两种情况：
第一种情况：UE不需要接收下行数据，即UE只发送上行数据，不接收下行数据。
此时，UE在恢复RRC连接后，UE在最后一个上行数据包中携带Endmarker指示包，即UE在待发送上行数据的最后一个上行数据包的分组数据汇聚协议(Packet Data Convergence Protocol，PDCP)头上或介质访问控制(Medium Access Control，MAC)头上携带Endmarker指示包。在完成上行数据的发送后，无需等待下行数据，释放RRC连接。
第二种情况：UE需要接收下行数据，即UE既发送上行数据也接收下行数据。
此时，UE在恢复RRC连接并发送完上行数据后，继续接收下行数据，并解析出下行数据包中包含Endmarker指示包后，释放RRC连接。
参阅图7所示，为本发明实施例提供的一种RRC连接释放概述流程图B2。
步骤710：基站接收UE发送的第一消息。
第一消息携带UE是否需要接收下行数据的指示信息。这里的第一消息可以为一种新的消息，也可以携带在现有的RRC连接请求消息中。
步骤720：基站确定指示信息指示UE不需要接收下行数据时，接收UE发送的待发送上行数据，并在解析到接收的上行数据包中包含Endmarker指示包后，释放与UE之间的RRC连接；和/或基站确定指示信息指示UE需要接收下行数据，在UE发送的待发送上行数据接收完成后，继续发送下行数据至UE，并在发送到最后一个下行数据包时，在最后一个下行数据包中携带Endmarker指示包，并将携带Endmarker指示包的最后一个下行数据包发送至 UE后，基站释放与UE之间的RRC连接。
具体的，对应UE侧，在eNB侧也包含两种情况：
第一种情况：基站确定指示信息指示UE不需要接收下行数据。
在确认RRC连接建立完成后，基站接收UE发送的上行数据，在从UE发送的上行数据中解析出Endmarker指示包后，基站释放与UE之间的RRC连接。基站将接收到的待发送上行数据发送至S-GW，在待发送上行数据的最后一个上行数据包的通用分组无线服务技术隧道协议(GPRS Tunnelling Protocol，GTP)头上携带Endmarker指示包发往S-GW。
第二种情况：基站确定指示信息指示UE需要接收下行数据。
在确认RRC连接建立完成后，基站接收UE发送的上行数据，在UE发送的待发送上行数据接收完成后，继续接收S-GW发送的下行数据并发往UE，基站在从S-GW发送的下行数据中解析出Endmarker指示包后，确认已接收到最后一个下行数据包。基站将在最后一个下行数据包的PDCP头上或MAC头上携带Endmarker指示包，将携带Endmarker指示包的最后一个下行数据包发送至UE后，基站释放与UE之间的RRC连接。
参阅图8所示，为本发明实施例提供的一种RRC连接释放具体流程图B3。
在UE上次释放RRC连接后，UE和eNB都会保留UE的上下文信息，当有下行数据到达(网络触发)或上行数据到达(UE触发)时，UE需要重新建立RRC连接。在UE与eNB的随机接入完成后：
步骤801：UE发送RRC连接请求消息至eNB，该请求消息中携带UE不需要接收下行数据的指示信息。
步骤802：eNB将RRC建立消息发送至UE。
步骤803：UE向eNB发送RRC连接建立完成消息。
步骤804：eNB在接收到RRC连接建立完成消息后，发送S1连接恢复指示信息至MME，并在该S1连接恢复指示信息中携带UE不需要接收下行数据的指示信息。
步骤805：MME回复S1连接恢复的确认指示消息至eNB，表明MME与eNB之间的S1连接已恢复。
步骤806：UE发送待发送上行数据至网络侧设备。
步骤807：UE在最后一个上行数据包中携带Endmarker指示包，UE在发送完最后一个上行数据包后，释放RRC连接；以及eNB解析出到接收的上行数据包中包含Endmarker指示包后，释放与UE之间的RRC连接；以及MME确定UE释放RRC连接。
MME和S-GW可以为组合在一起的设备，或者，两个网元之间有接口相连，当S-GW解析出接收的上行数据包中包含Endmarker指示包时，确定UE释放RRC连接，并将该消息通知给MME。
此外，在UE释放RRC连接时，UE和网络侧设备需要保留UE本次连接的上下文信息。
因此，UE在上行数据的最后一个上行数据包中携带Endmarker指示包，在UE发送完携带Endmarker指示包的最后一包上行数据时，释放RRC连接，网络侧设备也根据上行数据中解析到的Endmarker指示包，释放与UE之间的RRC连接，节省了RRC连接释放过程中的信令开销。
参阅图9所示，为本发明实施例提供的一种RRC连接释放具体流程图B4。
在UE上次释放RRC连接后，UE和eNB都会保留UE的上下文信息，当有下行数据到达(网络触发)或上行数据到达(UE触发)时，UE需要重新建立RRC连接。在UE与eNB的随机接入完成后：
步骤901：UE发送RRC连接请求消息至eNB，该请求消息中携带UE需要接收下行数据的指示信息。
步骤902：eNB将RRC建立消息发送至UE。
步骤903：UE向eNB发送RRC连接建立完成消息。
步骤904：eNB在接收到RRC连接建立完成消息后，发送S1连接恢复指示消息至MME，并在该S1连接恢复指示信息中携带UE需要接收下行数据 的指示信息。
步骤905：MME回复S1连接恢复的确认指示消息至eNB，恢复与eNB之间的S1连接。
步骤906：UE发送待发送上行数据至网络侧设备。
步骤907：UE接收eNB发送的下行数据。
步骤908：UE在解析出下行数据中的Endmarker指示包后，释放RRC连接；以及eNB在最后一个下行数据包中携带Endmarker指示包，并将携带Endmarker指示包的最后一个下行数据包发送至UE后，释放与UE之间的RRC连接；以及MME确定UE释放RRC连接。
MME和S-GW可以为组合在一起的设备，或者，两个网元之间有接口相连，当S-GW发送完携带Endmarker指示包的最后一个下行数据包时，确定UE释放RRC连接，并将该消息通知给MME。
此外，在UE释放RRC连接时，UE和网络侧设备需要保留UE本次连接的上下文信息。
因此，UE发送完上行数据后，接收下行数据，并在下行数据中解析出Endmarker指示包后，释放RRC连接；以及eNB接收UE发送的上行数据，转发下行数据至UE，在最后一个下行数据包中携带Endmarker指示包，并将携带Endmarker指示包的最后一个下行数据包发送至UE后，释放与UE之间的RRC连接，节省了RRC连接释放过程中的信令开销。
参阅图10所示，为本发明实施例提供的一种RRC连接释放概述流程图C1。
步骤1010：UE上报应用消息至网络侧设备，应用消息携带UE的应用层协议类型。
其中，应用层协议类型为超文本传输协议(Hyper Text Transfer Protocol，HTTP)、传输控制协议(Transmission Control Protocol，TCP)、用户数据报协议(User Datagram Protocol，UDP)等。
参阅图11所示，为HTTP/TCP的标准协议流程。HTTP是一个基于请求 和响应模式的协议，通常，客户端发起请求，建立一个到服务器指定端口的TCP连接。服务器则在端口监听客户端发送的请求，一旦收到请求，向客户端发回一个响应消息。TCP是面向连接的可靠协议，为保证传输的可靠性，接收端对已成功收到的数据发相应的确认(ACK)，若发送端在合理的往返时延内未收到确认，则对应的数据将被重传。其中，面向连接意味着客户端和服务器在交换数据包前须建立一个TCP连接，TCP连接成功建立后，可以开始传输数据。
参阅图12所示，为UDP的标准协议流程。UDP是无连接的协议，不对传输的数据包进行可靠性保证，具有资源消耗小、处理速度快的优点。
步骤1020：UE在与网络侧设备完成针对应用层协议类型需要交互的所有数据包后，释放RRC连接。
因此，UE根据应用层协议类型的标准协议流程，完成对应应用层协议类型需要交互的所有数据包后，释放RRC连接。
如图11所示，当UE使用TCP/HTTP的应用层协议时，为完成数据传输，UE首先向域名***解析(Domain Name System，DNS)服务器发起DNS请求，DNS服务器根据域名解出地址后回复给UE，然后UE使用三次握手协议建立TCP连接，三次握手完成后，UE便开始传输数据，服务器收到TCP数据后会回复TCP ACK，HTTP协议层会产生HTTP 200OK发给UE，UE收到后给服务器回复TCP ACK，数据传输结束后需释放TCP连接。UE在完成TCP/HTTP需要交互的所有数据包后，释放RRC连接，
由图11和图12可知，当UE采用不同的应用层协议时完成数据传输所需要的信令数也不一样。
参阅图13所示，为本发明实施例提供的一种RRC连接释放概述流程图C2。
步骤1310：网络侧设备接收UE上报的应用消息，应用消息携带UE的应用层协议类型。
这里的网络侧设备可以是eNB，也可以是MME。
步骤1320：网络侧设备根据应用层协议类型，确定应用层协议类型对应的传输数据包的个数；
例如，如图11所示，UE上报应用层协议类型为TCP/HTTP时，eNB根据TCP/HTTP的标准协议流程确定UE需要发送6个消息，需要接收5个消息。
步骤1330：网络侧设备处理UE针对应用层协议类型传输的数据包，并记录处理的数据包个数。
例如，eNB根据TCP/HTTP的标准协议流程确定UE需要发送6个消息，需要接收5个消息后，对UE完成TCP/HTTP标准流程的情况进行记录，可以记录UE发送多少个消息，接收多少个消息，或只记录UE接收多少个消息。
步骤1340：当网络侧设备确定记录的数据包个数达到应用层协议类型对应的传输数据包的个数时，网络侧设备释放与UE之间的RRC连接。
例如，当eNB确定UE针对TCP/HTTP已经发送6个消息，接收5个消息后，释放与UE之间的RRC连接。
又例如，如图12所示，当UE使用UDP协议时，UE也需先完成DNS解析，UE得知服务器地址后便进行数据的传输，由于UDP不保证数据传输的可靠性，服务器不会进行相应的确认回复，HTTP协议层会产生HTTP 200OK作为UDP数据发给UE，UE收到后也不会进行相应的确认回复。UE上报应用层协议类型为UDP时，eNB根据UDP的标准协议流程确定UE需要发送2个消息，需要接收2个消息，因此，可以在记录UE接收消息的个数为2时，释放与UE之间的RRC连接。
此外，随着技术的发展，可能出现一种极端的情况，UE只需要发送一次消息，即UE只将上行数据包发给服务器后就结束数据包的传输，释放RRC连接，相应地，网络侧设备在处理一个数据包后释放与UE之间的RRC连接。
因此，从上述实施例可知，网络侧设备根据UE上报的应用层协议类型得知完成该应用层协议类型所需传输的数据包个数，即UE需要接收及发送的数据包个数，并对UE接收及发送的数据包进行计数，确定到达该应用层协议类 型规定的数据包个数时，确定UE释放RRC连接，从而减少了RRC连接释放过程中的信令开销及网络资源的负载。
现有技术中，图14是S1接口用户面协议栈示意图，S1-U接口提供了eNB和S-GW间的用户面数据的非保障传输。GTP-U位于UDP层和IP层之上用于传输用户面协议数据单元(PDU,Protocol Data Unit)。每个UE的每个承载需要一个GTP-U通道进行传输，即每个UE的每个数据包经过上层的相应处理后传递至GTP-U层，再经过GTP-U层相应的处理传递至下层。图15中，在S1-U协议栈进行传输时，假设应用层服务数据单元(Service Data Unit，SDU)的大小为30字节，加上TCP/IP头后，数据帧的大小为70字节，该数据帧传至GTP层加上GTP头后变为78字节，再往下传至UDP层加上UDP头后变为86字节，因此，数据帧每往下层传输，帧的大小都会增大，由图15可知最终数据帧大小为202字节，因此远大于实际要传输的30字节，由此可知，当多个UE在S1-U传输数据时会导致S1-U的传输负荷较高且传输效率低。
为了提高S1-U的传输效率，基站接收每个UE上报UE的类型和/或业务类型，基站接收多个UE发送的数据包，基站根据每个UE对应上报的UE的类型和/或业务类型，对满足预设条件的UE的数据包进行级联，这里主要针对待传输的数据包较小时才进行级联操作，因此，预设条件是针对特定UE或特定的业务。基站将级联后的数据包通过在公共的通道上进行传输。该公共的通道可以是默认承载建立过程中建成的，基站选择其中一条默认承载的通道作为公共的通道，或者，基站在确定UE满足预设条件后请求建立一条新的承载通道。
进一步地，基站对满足预设条件的不同UE的数据包进行级联时，还需要对接收到的每个UE的数据包进行识别，即通过UE的标识来识别不同的UE。可以有以下两种但不限于以下两种方法：
(1)基于UE的IP地址识别不同UE的数据包。
现有技术中，在默认承载的建立过程中，P-GW会给每一个UE分配一个唯一的IP地址，该IP地址是一个端到端的地址，只有UE和MME知道该地 址，而eNB无法得知。
因此，为了让eNB基于UE的IP地址来区分不同UE的数据包，MME需要将每个UE的IP地址通知给eNB，即在基站将满足预设条件的不同UE的数据包进行级联之前，基站接收MME发送的携带每个UE的IP地址的通知消息。这样，在数据传输时，eNB和SGW便能基于级联后的数据包里每个小包后紧跟的IP地址来识别UE。eNB将多个UE的数据包级联后在公共的GTP-U通道上传输。如表1所示，eNB将不同UE的数据包进行级联后的格式为：
表1
Figure PCTCN2015098406-appb-000001
(2)基于UE的GTP IP+GTP TEID识别不同UE的数据包。
GTP通道端点标识(Tunnel Endpoint Identifier，TEID)，用于eNB和S-GW之间的用户面传输。现有技术中，在默认承载的建立过程中，eNB可获知S-GW端分配的GTP IP和GTP TEID，eNB和S-GW间能通过GTP IP+GTP TEID来区分不同的UE。eNB将多个UE的数据包级联后在公共的GTP-U通道上传输，因此可基于级联后的数据包里每个小包后紧跟的GTP IP+GTP TEID来识别不同的UE。如表2所示，eNB将不同UE的数据包进行级联后的格式为：
表2
Figure PCTCN2015098406-appb-000002
参阅图16所示，为本发明实施例中eNB对UE上报的数据包进行级联并传输的流程图。
步骤1601：UE1和UE2上报UE的类型/业务类型给eNB。
步骤1602：UE1和UE2发送上行数据给eNB。
步骤1603：eNB根据两个UE的上报的信息判断出UE1和UE2为特殊的 类型，如CIoT中的小包传输，满足预设条件，UE1和UE2的上行数据进行级联，得到级联数据包。
步骤1604：eNB将级联数据包通过S1-U进行传输。
步骤1605：S-GW发送针对该级联数据包的确认消息。
因此，本实施例中基站将不同UE的数据包进行级联，然后将级联后的数据包放在公共的通道上进行传输，减少了传输负荷且提高传输效率。
此外，现有技术中，当网络侧要给UE发送下行数据时，由于S-GW和P-GW之间的S5用户面承载一直存在，下行数据可以一直转发给S-GW。S-GW在收到下行数据后，通过下行数据通知Downlink Data Notification消息通知MME网络侧有下行消息需要发送给UE，触发MME发送寻呼消息。MME向UE所在的跟踪区域列表(Tracking Area List，TA List)内的全部eNB发送寻呼消息，该寻呼消息中携带有SAE临时移动站标识(SAE Temporary Mobile Station Identifier SAE Temporary Mobile Station Identifier，S-TMSI)、TA Lists及UE默认的寻呼周期，同时eNB在***消息中也会有广播寻呼周期，eNB会在UE默认的寻呼周期和***消息中的广播寻呼周期两者中选择较小的寻呼周期用来计算eNB在空口寻呼UE的时机，当寻呼UE的时机到达时，eNB给UE发送寻呼消息。
但是，在UE释放RRC连接后，eNB与MME间的S1接口可能保持连接，当S1接口保持连接时，MME不再给eNB发送寻呼消息，此时eNB无法在空口寻呼UE。
针对处于静态的UE，本实施例给出了eNB确定空口寻呼UE的方案。现有技术中，UE释放RRC连接后，eNB和UE保留UE的上下文信息，包括RRC配置，承载配置，安全上下文等，本发明实施例中保存的上下文信息中加入预设的寻呼相关信息，包括用户标识、TA Lists、UE默认的寻呼周期及eNB在***消息中的广播寻呼周期，此时，eNB根据上下文信息中记录的预设的寻呼相关信息便能根据用户标识确定待寻呼的UE，即在空口寻呼哪个UE，以及根据TA Lists确定寻呼区域，并从UE默认的寻呼周期和***消息 中的广播寻呼周期两者中选择较小的寻呼周期用来确定eNB在空口寻呼UE的时机。当寻呼时机到达时，eNB给该UE发送寻呼消息。
参阅图17所示，本发明实施例一种RRC连接释放装置1700，包括：
第一发送单元1701，用于向基站发送第一消息，第一消息携带预设的RRC释放时间确定参数或第一RRC释放时间；
第一处理单元1702，用于在第一消息中携带第一RRC释放时间时，根据第一RRC释放时间设置第一定时器的定时时长，并启动第一定时器；或者第一接收单元1703，用于接收基站针对第一消息反馈的响应消息，其中，响应消息携带基站根据预设的RRC释放时间确定参数确定的第二RRC释放时间；第一处理单元1702，用于在第一消息中携带预设的RRC释放时间确定参数时，根据第二RRC释放时间设置第一定时器的定时时长，并启动第一定时器；
第一判断单元1704，用于在第一定时器超时时，释放RRC连接。
可选的，预设的RRC释放时间确定参数为装置的待发送上行数据的数据量和/或待发送上行数据的发送预估时间。
可选的，还包括：
第一发送单元1701，还用于上报BSR至基站，BSR用于指示基站调整第二定时器的定时时长，其中，第二定时器的定时时长是基站根据UE发送的第一消息设置的；
第一接收单元1703，还用于接收基站回复的第一调整指示；
第一处理单元1702，还用于在接收到基站回复的第一调整指示时，根据第一调整指示，调整第一定时器的定时时长。
参阅图18所示，本发明实施例一种RRC连接释放装置1800，包括：
第二接收单元1801，用于接收UE发送的第一消息，第一消息携带预设的RRC释放时间确定参数或第一RRC释放时间；
第二处理单元1802，用于确定第一消息中携带第一RRC释放时间时，根据第一RRC释放时间设置第二定时器的定时时长，并启动第二定时器；或者第二处理单元1802，用于确定第一消息中携带预设的RRC释放时间确定参数， 根据预设的RRC释放时间确定参数确定第二RRC释放时间，并根据第二RRC释放时间设置第二定时器的定时时长，并启动第二定时器；第二发送单元1803，用于针对第一消息给UE反馈响应消息，响应消息中携带第二RRC释放时间；
第二判断单元1804，用于在第二定时器超时时，基站释放与UE之间的RRC连接。
可选的，预设的RRC释放时间确定参数为UE的待发送上行数据的数据量和/或待发送上行数据的发送预估时间。
可选的，还包括：
第二接收单元1801，还用于接收UE上报的BSR；
第二处理单元1802，还用于在接收到UE上报的BSR时，对第二定时器的定时时长进行调整，并根据第二定时器的定时时长调整结果生成第一调整指示以及第二调整指示；
第二发送单元1803，还用于将第一调整指示回复至UE，将第二调整指示通知给MME。
可选的，还包括：
第二接收单元1801，还用于接收UE发送的针对响应消息的确认消息；
第二发送单元1803，还用于在第二接收单元接收到UE发送的针对响应消息的确认消息之后，发送S1连接恢复指示信息至MME，S1连接恢复指示信息携带第二定时器的定时时长；
第二接收单元1801，还用于接收MME发送的S1连接恢复的确认指示信息；
第二处理单元1802，还用于根据S1连接恢复的确认指示信息确定已恢复基站与MME之间的S1连接。
参阅图19所示，本发明实施例一种RRC连接释放装置1900，包括：
第三接收单元1901，用于接收基站发送的S1连接恢复指示信息，S1连接恢复指示信息携带第二定时器的定时时长，其中，第二定时器的定时时长 是基站根据UE发送的第一消息设置的，第一消息携带预设的RRC释放时间确定参数或第一RRC释放时间；
第三处理单元1902，用于根据第二定时器的定时时长设置第三定时器的定时时长，并启动第三定时器；
第三判断单元1903，用于在第三定时器超时时，确定UE释放RRC连接。
可选的，还包括：
第三处理单元1902，用于根据S1连接恢复指示信息确定恢复与基站之间的S1连接；
第三发送单元1904，用于向基站发送S1连接恢复的确认指示信息。
可选的，第三接收单元1901，还用于接收基站发送的第二调整指示；
第三处理单元1902，还用于在第三接收单元接收到基站发送的第二调整指示时，根据第二调整指示调整第三定时器的定时时长。
参阅图20所示，本发明实施例一种RRC连接释放装置2000，包括：
第四发送单元2001，用于向基站发送第一消息，第一消息携带UE是否需要接收下行数据的指示信息；
第四发送单元2001，用于在第四处理单元2002确定不需要接收下行数据时，发送待发送上行数据至基站，第四处理单元2002，用于在最后一个上行数据包中携带Endmarker指示包，并在第四发送单元2001发送完最后一个上行数据包后，释放RRC连接；和/或第四发送单元2001，用于在第四处理单元确定需要接收下行数据时，发送待发送上行数据至基站，第四接收单元2003，用于在第四处理单元2002确定待发送上行数据发送完成后，接收下行数据；第四处理单元2002，用于在解析到第四接收单元接收的下行数据包中包含Endmarker指示包后，释放RRC连接。
可选的，第四处理单元2002，还用于在待发送上行数据的最后一个上行数据包的PDCP头上携带Endmarker指示包。
参阅图21所示，本发明实施例一种RRC连接释放装置2100，包括：
第五接收单元2101，用于接收UE发送的第一消息，第一消息携带UE 是否需要接收下行数据的指示信息；
第五接收单元2101，用于在第五处理单元2102确定指示信息指示UE不需要接收下行数据时，接收UE发送的待发送上行数据；在第五处理单元2102，用于在解析到第五接收单元接收的上行数据包中包含Endmarker指示包后，释放与UE之间的RRC连接；和/或第五接收单元2101，用于在第五处理单元2102确定指示信息指示UE需要接收下行数据，接收UE发送的待发送上行数据；第五发送单元2103，用于在UE发送的待发送上行数据由第五接收单元接收完成后，继续发送下行数据至UE；在第五处理单元2102，用于在第五发送单元发送到最后一个下行数据包时，在最后一个下行数据包中携带Endmarker指示包，并将携带Endmarker指示包的最后一个下行数据包发送至UE后，释放与UE之间的RRC连接。
可选的，还包括：
第五处理单元2102还用于确定指示信息指示UE不需要接收下行数据时，在从UE发送的待发送上行数据中解析出Endmarker指示包后，将在待发送上行数据的最后一个上行数据包的通用分组无线服务技术隧道协议GTP头上携带Endmarker指示包发往服务网关S-GW；和/或
在指示信息指示UE需要接收下行数据时，在最后一个下行数据包中携带Endmarker指示包，第五处理单元2102还用于：
在从S-GW发送的下行数据中解析出Endmarker指示包后，确认已接收到最后一个下行数据包；
将在最后一个下行数据包的PDCP头上携带Endmarker指示包。
参阅图22所示，本发明实施例一种RRC连接释放装置2200，包括：
第六发送单元2201，用于上报应用消息至网络侧设备，应用消息携带UE的应用层协议类型；
第六判断单元2202，用于在与网络侧设备完成针对应用层协议类型需要交互的所有数据包后，释放RRC连接。
可选的，应用层协议类型为传输控制协议和超文本传输协议TCP/HTTP， 或者用户数据报协议UDP。
参阅图23所示，本发明实施例一种RRC连接释放装置2300，包括：
第七接收单元2301，用于接收UE上报的应用消息，应用消息携带UE的应用层协议类型；
确定单元2302，用于根据应用层协议类型，确定应用层协议类型对应的传输数据包的个数；
计数单元2303，用于接收并处理UE针对应用层协议类型传输的数据包，并记录处理的数据包个数；
第七判断单元2304，用于当确定记录的数据包个数达到应用层协议类型对应的传输数据包的个数时，释放与UE之间的RRC连接。
需要说明的是，本发明实施例中对模块的划分是示意性的，仅仅为一种逻辑功能划分，实际实现时可以有另外的划分方式，另外，在本申请各个实施例中的各功能模块可以集成在一个处理模块中，也可以是各个模块单独物理存在，也可以两个或两个以上模块集成在一个模块中。上述集成的模块既可以采用硬件的形式实现，也可以采用软件功能模块的形式实现。
集成的模块如果以软件功能模块的形式实现并作为独立的产品销售或使用时，可以存储在一个计算机可读取存储介质中。基于这样的理解，本申请的技术方案本质上或者说对现有技术做出贡献的部分或者该技术方案的全部或部分可以以软件产品的形式体现出来，该计算机软件产品存储在一个存储介质中，包括若干指令用以使得一台计算机设备(可以是个人计算机，服务器，或者网络设备等)或处理器(processor)执行本申请各个实施例方法的全部或部分步骤。而前述的存储介质包括：U盘、移动硬盘、只读存储器(ROM，Read-Only Memory)、随机存取存储器(RAM，Random Access Memory)、磁碟或者光盘等各种可以存储程序代码的介质。
参阅图24所示，本发明实施例提供一种RRC连接释放设备2400，包括：
如图24所示，该设备包括第一收发器2401、第一处理器2402、第一存 储器2403。第一收发器2401、第一处理器2402以及第一存储器2403相互连接。本发明实施例中不限定上述部件之间的具体连接介质。本发明实施例在图24中以第一存储器2403、第一处理器2402以及第一收发器2401之间通过总线2404连接，总线在图24中以粗线表示，其它部件之间的连接方式，仅是进行示意性说明，并不引以为限。总线可以分为地址总线、数据总线、控制总线等。为便于表示，图24仅用一条粗线表示，但并不表示仅有一根总线或一种类型的总线。
本发明实施例中第一存储器2403，用于存储第一处理器2402执行的程序代码，可以是易失性存储器(英文：volatile memory)，例如随机存取存储器(英文：random-access memory，缩写：RAM)；第一存储器2403也可以是非易失性存储器(英文：non-volatile memory)，例如只读存储器(英文：read-only memory，缩写：ROM)，快闪存储器(英文：flash memory)，硬盘(英文：hard disk drive，缩写：HDD)或固态硬盘(英文：solid-state drive，缩写：SSD)、或者第一存储器2403是能够用于携带或存储具有指令或数据结构形式的期望的程序代码并能够由计算机存取的任何其他介质，但不限于此。第一存储器2403可以是上述存储器的组合。
第一收发器2401，用于向基站发送第一消息，第一消息携带预设的RRC释放时间确定参数或第一RRC释放时间；
第一处理器2402，用于在第一消息中携带第一RRC释放时间时，根据第一RRC释放时间设置第一定时器的定时时长，并启动第一定时器；或者第一收发器2401，用于在第一消息中携带预设的RRC释放时间确定参数时，接收基站针对第一消息反馈的响应消息，其中，响应消息携带基站根据预设的RRC释放时间确定参数确定的第二RRC释放时间；第一处理器2402，用于根据第二RRC释放时间设置第一定时器的定时时长，并启动第一定时器；
第一处理器2402，还用于在第一定时器超时时，释放RRC连接。
可选的，预设的RRC释放时间确定参数为UE的待发送上行数据的数据量和/或待发送上行数据的发送预估时间。
可选的，第一收发器2401，还用于上报BSR至基站，BSR用于指示基站调整第二定时器的定时时长，其中，第二定时器的定时时长是基站根据UE发送的第一消息设置的；以及接收基站回复的第一调整指示；
第一处理器2402，还用于在接收到基站回复的第一调整指示时，根据第一调整指示，调整第一定时器的定时时长。
参阅图25所示，本发明实施例提供一种RRC连接释放设备2500，包括：
如图25所示，该设备包括第二收发器2501、第二处理器2502、第二存储器2503。第二收发器2501、第二处理器2502以及第二存储器2503相互连接。本发明实施例中不限定上述部件之间的具体连接介质。本发明实施例在图25中以第二存储器2503、第二处理器2502以及第二收发器2501之间通过总线2504连接，总线在图25中以粗线表示，其它部件之间的连接方式，仅是进行示意性说明，并不引以为限。总线可以分为地址总线、数据总线、控制总线等。为便于表示，图25仅用一条粗线表示，但并不表示仅有一根总线或一种类型的总线。
本发明实施例中第二存储器2503，用于存储第二处理器2502执行的程序代码，可以是易失性存储器(英文：volatile memory)，例如随机存取存储器(英文：random-access memory，缩写：RAM)；第二存储器2503也可以是非易失性存储器(英文：non-volatile memory)，例如只读存储器(英文：read-only memory，缩写：ROM)，快闪存储器(英文：flash memory)，硬盘(英文：hard disk drive，缩写：HDD)或固态硬盘(英文：solid-state drive，缩写：SSD)、或者第二存储器2503是能够用于携带或存储具有指令或数据结构形式的期望的程序代码并能够由计算机存取的任何其他介质，但不限于此。第二存储器2503可以是上述存储器的组合。
第二收发器2501，用于接收UE发送的第一消息，第一消息携带预设的RRC释放时间确定参数或第一RRC释放时间；
第二处理器2502，用于确定第一消息中携带第一RRC释放时间时，根据第一RRC释放时间设置第二定时器的定时时长，并启动第二定时器；或者第 二处理器2502，用于确定第一消息中携带预设的RRC释放时间确定参数，根据预设的RRC释放时间确定参数确定第二RRC释放时间，并根据第二RRC释放时间设置第二定时器的定时时长，并启动第二定时器；第二收发器2501，用于针对第一消息给UE反馈响应消息，响应消息中携带第二RRC释放时间；
第二处理器2502，还用于在第二定时器超时时，释放与UE之间的RRC连接。
可选的，预设的RRC释放时间确定参数为UE的待发送上行数据的数据量和/或待发送上行数据的发送预估时间。
可选的，还包括：
第二收发器2501，还用于接收UE上报的BSR；
第二处理器2502，还用于在第二收发器2501接收到UE上报的BSR时，对第二定时器的定时时长进行调整，并根据第二定时器的定时时长调整结果生成第一调整指示以及第二调整指示；
第二收发器2501，还用于将第一调整指示回复至UE，将第二调整指示通知给MME。
可选的，第二收发器2501，还用于接收UE发送的针对响应消息的确认消息，并在接收到UE发送的针对响应消息的确认消息之后，发送S1连接恢复指示信息至MME，S1连接恢复指示信息携带第二定时器的定时时长；以及接收MME发送的S1连接恢复的确认指示信息；
第二处理器2502，用于根据S1连接恢复的确认指示信息确定已恢复基站与MME之间的S1连接。
参阅图26所示，本发明实施例提供一种RRC连接释放设备2600，包括：
如图26所示，该设备包括第三收发器2601、第三处理器2602、第三存储器2603。第三收发器2601、第三处理器2602以及第三存储器2603相互连接。本发明实施例中不限定上述部件之间的具体连接介质。本发明实施例在图26中以第三存储器2603、第三处理器2602以及第三收发器2601之间通过总线2604连接，总线在图26中以粗线表示，其它部件之间的连接方式，仅 是进行示意性说明，并不引以为限。总线可以分为地址总线、数据总线、控制总线等。为便于表示，图26仅用一条粗线表示，但并不表示仅有一根总线或一种类型的总线。
本发明实施例中第三存储器2603，用于存储第三处理器2602执行的程序代码，可以是易失性存储器(英文：volatile memory)，例如随机存取存储器(英文：random-access memory，缩写：RAM)；第三存储器2603也可以是非易失性存储器(英文：non-volatile memory)，例如只读存储器(英文：read-only memory，缩写：ROM)，快闪存储器(英文：flash memory)，硬盘(英文：hard disk drive，缩写：HDD)或固态硬盘(英文：solid-state drive，缩写：SSD)、或者第三存储器2603是能够用于携带或存储具有指令或数据结构形式的期望的程序代码并能够由计算机存取的任何其他介质，但不限于此。第三存储器2603可以是上述存储器的组合。
第三收发器2601，用于接收基站发送的S1连接恢复指示信息，S1连接恢复指示信息携带第二定时器的定时时长，其中，第二定时器的定时时长是基站根据UE发送的第一消息设置的，第一消息携带预设的RRC释放时间确定参数或第一RRC释放时间；
第三处理器2602，用于根据第二定时器的定时时长设置第三定时器的定时时长，并启动第三定时器；
以及用于在第三定时器超时时，确定UE释放RRC连接。
可选的，还包括：
第三处理器2602，还用于根据S1连接恢复指示信息确定恢复与基站之间的S1连接；
第三收发器2601，还用于向基站发送S1连接恢复的确认指示信息。
可选的，第三收发器2601，用于接收到基站发送的第二调整指示；
第三处理器2602，用于根据第二调整指示调整第三定时器的定时时长。
参阅图27所示，本发明实施例提供一种RRC连接释放设备2700，包括：
如图27所示，该设备包括第四收发器2701、第四处理器2702、第四存 储器2703。第四收发器2701、第四处理器2702以及第四存储器2703相互连接。本发明实施例中不限定上述部件之间的具体连接介质。本发明实施例在图27中以第四存储器2703、第四处理器2702以及第四收发器2701之间通过总线2704连接，总线在图27中以粗线表示，其它部件之间的连接方式，仅是进行示意性说明，并不引以为限。总线可以分为地址总线、数据总线、控制总线等。为便于表示，图27仅用一条粗线表示，但并不表示仅有一根总线或一种类型的总线。
本发明实施例中第四存储器2703，用于存储第四处理器2702执行的程序代码，可以是易失性存储器(英文：volatile memory)，例如随机存取存储器(英文：random-access memory，缩写：RAM)；第四存储器2703也可以是非易失性存储器(英文：non-volatile memory)，例如只读存储器(英文：read-only memory，缩写：ROM)，快闪存储器(英文：flash memory)，硬盘(英文：hard disk drive，缩写：HDD)或固态硬盘(英文：solid-state drive，缩写：SSD)、或者第四存储器2703是能够用于携带或存储具有指令或数据结构形式的期望的程序代码并能够由计算机存取的任何其他介质，但不限于此。第四存储器2703可以是上述存储器的组合。
第四收发器2701，用于向基站发送第一消息，第一消息携带UE是否需要接收下行数据的指示信息；
第四收发器2701，用于在第四处理器2702确定不需要接收下行数据时，发送待发送上行数据至基站，第四处理器2702在最后一个上行数据包中携带Endmarker指示包，在第四收发器2701发送完最后一个上行数据包后，释放RRC连接；和/或第四收发器2701，用于在第四处理器2702确定需要接收下行数据时，将待发送上行数据发送完成后，接收下行数据；第四处理器2702，用于解析到接收的下行数据包中包含Endmarker指示包后，释放RRC连接。
可选的，第四处理器2702还用于在待发送上行数据的最后一个上行数据包的PDCP头上携带Endmarker指示包。
参阅图28所示，一种RRC连接释放设备2800，包括：
如图28所示，该设备包括第五收发器2801、第五处理器2802、第五存储器2803。第五收发器2801、第五处理器2802以及第五存储器2803相互连接。本发明实施例中不限定上述部件之间的具体连接介质。本发明实施例在图28中以第五存储器2803、第五处理器2802以及第五收发器2801之间通过总线2804连接，总线在图28中以粗线表示，其它部件之间的连接方式，仅是进行示意性说明，并不引以为限。总线可以分为地址总线、数据总线、控制总线等。为便于表示，图28仅用一条粗线表示，但并不表示仅有一根总线或一种类型的总线。
本发明实施例中第五存储器2803，用于存储第五处理器2802执行的程序代码，可以是易失性存储器(英文：volatile memory)，例如随机存取存储器(英文：random-access memory，缩写：RAM)；第五存储器2803也可以是非易失性存储器(英文：non-volatile memory)，例如只读存储器(英文：read-only memory，缩写：ROM)，快闪存储器(英文：flash memory)，硬盘(英文：hard disk drive，缩写：HDD)或固态硬盘(英文：solid-state drive，缩写：SSD)、或者第五存储器2803是能够用于携带或存储具有指令或数据结构形式的期望的程序代码并能够由计算机存取的任何其他介质，但不限于此。第五存储器2803可以是上述存储器的组合。
第五收发器2801，用于接收UE发送的第一消息，第一消息携带UE是否需要接收下行数据的指示信息；
第五收发器2801，用于在第五处理器2802确定指示信息指示UE不需要接收下行数据时，接收UE发送的待发送上行数据；第五处理器2802，用于解析到接收的上行数据包中包含Endmarker指示包后，释放与UE之间的RRC连接；和/或第五收发器2801，用于在第五处理器2802确定指示信息指示UE需要接收下行数据，在UE发送的待发送上行数据接收完成后，继续发送下行数据至UE；第五处理器2802，用于在第五收发器发送到最后一个下行数据包时，在最后一个下行数据包中携带Endmarker指示包，在第五收发器2801将携带Endmarker指示包的最后一个下行数据包发送至UE后，释放与UE之间 的RRC连接。
可选的，还包括：
第五处理器2802，还用于确定指示信息指示UE不需要接收下行数据时，在从UE发送的待发送上行数据中解析出Endmarker指示包后，将在待发送上行数据的最后一个上行数据包的通用分组无线服务技术隧道协议GTP头上携带Endmarker指示包发往服务网关S-GW；和/或
在指示信息指示UE需要接收下行数据时，在最后一个下行数据包中携带Endmarker指示包，第五处理器2802，还用于：
在从S-GW发送的下行数据中解析出Endmarker指示包后，确认已接收到最后一个下行数据包；
将在最后一个下行数据包的PDCP头上携带Endmarker指示包。
参阅图29所示，一种RRC连接释放设备2900，包括：
如图29所示，该设备包括第六收发器2901、第六处理器2902、第六存储器2903。第六收发器2901、第六处理器2902以及第六存储器2903相互连接。本发明实施例中不限定上述部件之间的具体连接介质。本发明实施例在图29中以第六存储器2903、第六处理器2902以及第六收发器2901之间通过总线2904连接，总线在图29中以粗线表示，其它部件之间的连接方式，仅是进行示意性说明，并不引以为限。总线可以分为地址总线、数据总线、控制总线等。为便于表示，图29仅用一条粗线表示，但并不表示仅有一根总线或一种类型的总线。
本发明实施例中第六存储器2903，用于存储第六处理器2902执行的程序代码，可以是易失性存储器(英文：volatile memory)，例如随机存取存储器(英文：random-access memory，缩写：RAM)；第六存储器2903也可以是非易失性存储器(英文：non-volatile memory)，例如只读存储器(英文：read-only memory，缩写：ROM)，快闪存储器(英文：flash memory)，硬盘(英文：hard disk drive，缩写：HDD)或固态硬盘(英文：solid-state drive，缩写：SSD)、或者第六存储器2903是能够用于携带或存储具有指令或数据结构形式的期望 的程序代码并能够由计算机存取的任何其他介质，但不限于此。第六存储器2903可以是上述存储器的组合。
第六收发器2901，用于上报应用消息至网络侧设备，应用消息携带UE的应用层协议类型；
第六处理器2902，用于在与网络侧设备完成针对应用层协议类型需要交互的所有数据包后，释放RRC连接。
可选的，应用层协议类型为传输控制协议和超文本传输协议TCP/HTTP，或者用户数据报协议UDP。
参阅图30所示，一种网络侧设备3000，包括：
如图30所示，该设备包括第七收发器3001、第七处理器3002、第七存储器3003。第七收发器3001、第七处理器3002以及第七存储器3003相互连接。本发明实施例中不限定上述部件之间的具体连接介质。本发明实施例在图30中以第七存储器3003、第七处理器3002以及第七收发器3001之间通过总线3004连接，总线在图30中以粗线表示，其它部件之间的连接方式，仅是进行示意性说明，并不引以为限。总线可以分为地址总线、数据总线、控制总线等。为便于表示，图30仅用一条粗线表示，但并不表示仅有一根总线或一种类型的总线。
本发明实施例中第七存储器3003，用于存储第七处理器3002执行的程序代码，可以是易失性存储器(英文：volatile memory)，例如随机存取存储器(英文：random-access memory，缩写：RAM)；第七存储器3003也可以是非易失性存储器(英文：non-volatile memory)，例如只读存储器(英文：read-only memory，缩写：ROM)，快闪存储器(英文：flash memory)，硬盘(英文：hard disk drive，缩写：HDD)或固态硬盘(英文：solid-state drive，缩写：SSD)、或者第七存储器3003是能够用于携带或存储具有指令或数据结构形式的期望的程序代码并能够由计算机存取的任何其他介质，但不限于此。第七存储器3003可以是上述存储器的组合。
第七收发器3001，用于接收UE上报的应用消息，应用消息携带UE的 应用层协议类型；
第七处理器3002，用于根据应用层协议类型，确定应用层协议类型对应的传输数据包的个数；
第七收发器，用于接收UE针对应用层协议类型传输的数据包；
第七处理器，用于处理UE针对应用层协议类型传输的数据包，并记录处理的数据包个数；
以及当确定记录的数据包个数达到应用层协议类型对应的传输数据包的个数时，释放与UE之间的RRC连接。
综上，UE向基站发送第一消息，第一消息携带预设的RRC释放时间确定参数或第一RRC释放时间；若UE在第一消息中携带第一RRC释放时间，UE根据第一RRC释放时间设置第一定时器的定时时长并启动第一定时器；或者若UE在第一消息中携带预设的RRC释放时间确定参数，UE接收基站针对第一消息反馈的响应消息，其中，响应消息携带基站根据预设的RRC释放时间确定参数确定的第二RRC释放时间；UE根据第二RRC释放时间设置第一定时器的定时时长并启动第一定时器；UE在第一定时器超时时释放RRC连接，极大地节省了RRC释放过程中的信令开销。基站根据第一消息确定第二定时器的定时时长，以及向MME发送携带第二定时器的定时时长的指示信息。UE、基站和MME根据RRC释放时间分别设置第一定时器、第二定时器和第三定时器，当UE确定第一定时器超时时，UE释放RRC连接；当基站确定第二定时器超时时，释放与UE之间的RRC连接；当MME确定第三定时器超时时，确定UE释放RRC连接，极大地节省了RRC释放过程中的信令开销。
UE向基站发送第一消息，携带UE是否需要接收下行数据的指示信息。当UE不需要接收下行数据时，UE发送待发送上行数据至基站，并在最后一个上行数据包中携带Endmarker指示包，UE在发送完最后一个上行数据包后，释放RRC连接，同时，基站根据指示信息确定UE不需要接收下行数据时，解析到接收的上行数据包中包含Endmarker指示包后，释放与UE之间的RRC 连接；和/或当UE在需要接收下行数据时，在待发送上行数据发送完成后，UE接收下行数据，并在解析到接收的下行数据包中包含Endmarker指示包后，释放RRC连接。同时，基站根据指示信息确定UE需要接收下行数据时，将携带Endmarker指示包的最后一个下行数据包发送至UE后，释放与UE之间的RRC连接，极大地节省了RRC释放过程中的信令开销。
UE上报携带UE的应用层协议类型的应用消息至网络侧设备，在与网络侧设备完成针对应用层协议类型需要交互的所有数据包后，释放RRC连接；网络侧设备根据应用层协议类型，确定应用层协议类型对应的传输数据包的个数，并针对该应用层协议类型的传输数据包计数，当达到应用层协议类型对应的传输数据包的个数时，网络侧设备释放与UE之间的RRC连接，极大地节省了RRC释放过程中的信令开销。
本领域内的技术人员应明白，本发明的实施例可提供为方法、***、或计算机程序产品。因此，本发明可采用完全硬件实施例、完全软件实施例、或结合软件和硬件方面的实施例的形式。而且，本发明可采用在一个或多个其中包含有计算机可用程序代码的计算机可用存储介质(包括但不限于磁盘存储器、CD-ROM、光学存储器等)上实施的计算机程序产品的形式。
本发明是参照根据本发明实施例的方法、设备(***)、和计算机程序产品的流程图和/或方框图来描述的。应理解可由计算机程序指令实现流程图和/或方框图中的每一流程和/或方框、以及流程图和/或方框图中的流程
和/或方框的结合。可提供这些计算机程序指令到通用计算机、专用计算机、嵌入式处理机或其他可编程数据处理设备的处理器以产生一个机器，使得通过计算机或其他可编程数据处理设备的处理器执行的指令产生用于实现在流程图一个流程或多个流程和/或方框图一个方框或多个方框中指定的功能的装置。
这些计算机程序指令也可存储在能引导计算机或其他可编程数据处理设备以特定方式工作的计算机可读存储器中，使得存储在该计算机可读存储器中的指令产生包括指令装置的制造品，该指令装置实现在流程图一个流程或 多个流程和/或方框图一个方框或多个方框中指定的功能。
这些计算机程序指令也可装载到计算机或其他可编程数据处理设备上，使得在计算机或其他可编程设备上执行一系列操作步骤以产生计算机实现的处理，从而在计算机或其他可编程设备上执行的指令提供用于实现在流程图一个流程或多个流程和/或方框图一个方框或多个方框中指定的功能的步骤。
尽管已描述了本发明的优选实施例，但本领域内的技术人员一旦得知了基本创造性概念，则可对这些实施例作出另外的变更和修改。所以，所附权利要求意欲解释为包括优选实施例以及落入本发明范围的所有变更和修改。
显然，本领域的技术人员可以对本发明实施例进行各种改动和变型而不脱离本发明实施例的精神和范围。这样，倘若本发明实施例的这些修改和变型属于本发明权利要求及其等同技术的范围之内，则本发明也意图包含这些改动和变型在内。

Claims (51)

  1. 一种无线资源控制RRC连接释放方法，其特征在于，包括：
    用户设备UE向基站发送第一消息，所述第一消息携带预设的RRC释放时间确定参数或第一RRC释放时间；
    若所述UE在所述第一消息中携带所述第一RRC释放时间，所述UE根据所述第一RRC释放时间设置第一定时器的定时时长，并启动所述第一定时器；或者若所述UE在所述第一消息中携带所述预设的RRC释放时间确定参数，所述UE接收所述基站针对所述第一消息反馈的响应消息，其中，所述响应消息携带所述基站根据所述预设的RRC释放时间确定参数确定的第二RRC释放时间；所述UE根据所述第二RRC释放时间设置所述第一定时器的定时时长，并启动所述第一定时器；
    所述UE在所述第一定时器超时时，释放RRC连接。
  2. 如权利要求1所述的方法，其特征在于，所述预设的RRC释放时间确定参数为所述UE的待发送上行数据的数据量和/或所述待发送上行数据的发送预估时间。
  3. 如权利要求1或2所述的方法，其特征在于，所述UE在所述第一定时器超时之前，还包括：
    所述UE上报缓冲状态报告BSR至所述基站，所述BSR用于指示所述基站调整第二定时器的定时时长，其中，所述第二定时器的定时时长是所述基站根据所述UE发送的所述第一消息设置的；
    所述UE接收所述基站回复的第一调整指示，并根据所述第一调整指示，调整所述第一定时器的定时时长。
  4. 一种RRC连接释放方法，其特征在于，包括：
    基站接收UE发送的第一消息，所述第一消息携带预设的RRC释放时间确定参数或第一RRC释放时间；
    若所述基站确定所述第一消息中携带所述第一RRC释放时间，所述基站 根据所述第一RRC释放时间设置第二定时器的定时时长，并启动所述第二定时器；
    或者若所述基站确定所述第一消息中携带所述预设的RRC释放时间确定参数，所述基站根据所述预设的RRC释放时间确定参数确定第二RRC释放时间，并在针对所述第一消息反馈给所述UE的响应消息中携带所述第二RRC释放时间；所述基站根据所述第二RRC释放时间设置所述第二定时器的定时时长，并启动所述第二定时器；
    所述基站在所述第二定时器超时时，释放与所述UE之间的RRC连接。
  5. 如权利要求4所述的方法，其特征在于，所述预设的RRC释放时间确定参数为所述UE的待发送上行数据的数据量和/或所述待发送上行数据的发送预估时间。
  6. 如权利要求4或5所述的方法，其特征在于，所述基站在所述第二定时器超时之前，还包括：
    若所述基站接收到所述UE上报的BSR，并根据所述BSR对所述第二定时器的定时时长进行调整；
    所述基站根据所述第二定时器的定时时长调整结果生成第一调整指示回复至所述UE，以及生成第二调整指示通知给移动管理实体MME。
  7. 如权利要求4或5所述的方法，其特征在于，在所述基站反馈所述响应消息至所述UE之后，还包括：
    所述基站接收所述UE发送的针对所述响应消息的确认消息后，发送S1连接恢复指示信息至MME，所述S1连接恢复指示信息携带所述第二定时器的定时时长；
    所述基站接收所述MME发送的S1连接恢复的确认指示信息；
    所述基站根据所述S1连接恢复的确认指示信息确定已恢复所述基站与所述MME之间的S1连接。
  8. 一种RRC连接释放方法，其特征在于，包括：
    移动管理实体MME接收基站发送的S1连接恢复指示信息，所述S1连 接恢复指示信息携带第二定时器的定时时长，其中，所述第二定时器的定时时长是所述基站根据UE发送的第一消息设置的，所述第一消息携带预设的RRC释放时间确定参数或第一RRC释放时间；
    所述MME根据所述第二定时器的定时时长，设置第三定时器的定时时长，并启动所述第三定时器；
    所述MME在所述第三定时器超时时，确定所述UE释放RRC连接。
  9. 如权利要求8所述的方法，其特征在于，在MME接收基站发送的S1连接恢复指示信息之后，还包括：
    所述MME根据所述S1连接恢复指示消息确定恢复与所述基站之间的S1连接；
    所述MME向所述基站发送S1连接恢复的确认指示信息。
  10. 如权利要求8所述的方法，其特征在于，所述MME在所述第三定时器超时之前，还包括：
    若所述MME接收到所述基站发送的第二调整指示，则根据所述第二调整指示调整所述第三定时器的定时时长。
  11. 一种RRC连接释放方法，其特征在于，包括：
    UE向基站发送第一消息，所述第一消息携带所述UE是否需要接收下行数据的指示信息；
    所述UE在不需要接收下行数据时，发送待发送上行数据至所述基站，并在最后一个上行数据包中携带端点标记Endmarker指示包，所述UE在发送完所述最后一个上行数据包后，释放RRC连接；和/或
    所述UE在需要接收下行数据时，在所述待发送上行数据发送完成后，接收下行数据，并在解析到接收的下行数据包中包含Endmarker指示包后，释放RRC连接。
  12. 如权利要求11所述的方法，其特征在于，所述UE在待发送上行数据的最后一个上行数据包的分组数据汇聚协议PDCP头上携带Endmarker指示包。
  13. 一种RRC连接释放方法，其特征在于，包括：
    基站接收UE发送的第一消息，所述第一消息携带所述UE是否需要接收下行数据的指示信息；
    所述基站确定所述指示信息指示所述UE不需要接收下行数据时，接收所述UE发送的待发送上行数据，并在解析到接收的上行数据包中包含Endmarker指示包后，释放与所述UE之间的RRC连接；和/或
    所述基站确定所述指示信息指示所述UE需要接收下行数据，在所述UE发送的所述待发送上行数据接收完成后，继续发送下行数据至所述UE，并在发送到最后一个下行数据包时，在所述最后一个下行数据包中携带Endmarker指示包，并将携带Endmarker指示包的最后一个下行数据包发送至所述UE后，所述基站释放与所述UE之间的RRC连接。
  14. 如权利要求13所述的方法，其特征在于，还包括：
    所述基站确定所述指示信息指示所述UE不需要接收下行数据时，在从所述UE发送的所述待发送上行数据中解析出Endmarker指示包后，所述基站将在所述待发送上行数据的最后一个上行数据包的通用分组无线服务技术隧道协议GTP头上携带所述Endmarker指示包发往服务网关S-GW；和/或
    所述基站在所述指示信息指示所述UE需要接收下行数据时，所述基站在所述最后一个下行数据包中携带Endmarker指示包，包括：
    所述基站在从所述S-GW发送的下行数据中解析出Endmarker指示包后，确认已接收到最后一个下行数据包；
    所述基站将在所述最后一个下行数据包的PDCP头上携带所述Endmarker指示包。
  15. 一种RRC连接释放方法，其特征在于，包括：
    UE上报应用消息至网络侧设备，所述应用消息携带所述UE的应用层协议类型；
    所述UE在与所述网络侧设备完成针对所述应用层协议类型需要交互的所有数据包后，释放RRC连接。
  16. 如权利要求15所述的方法，其特征在于，所述应用层协议类型为传输控制协议和超文本传输协议TCP/HTTP，或者用户数据报协议UDP。
  17. 一种RRC连接释放方法，其特征在于，包括：
    网络侧设备接收UE上报的应用消息，所述应用消息携带所述UE的应用层协议类型；
    所述网络侧设备根据所述应用层协议类型，确定所述应用层协议类型对应的传输数据包的个数；
    所述网络侧设备接收并处理所述UE针对所述应用层协议类型传输的数据包，并记录处理的数据包个数；
    当所述网络侧设备确定记录的数据包个数达到所述应用层协议类型对应的传输数据包的个数时，所述网络侧设备释放与所述UE之间的RRC连接。
  18. 一种RRC连接释放装置，其特征在于，包括：
    第一发送单元，用于向基站发送第一消息，所述第一消息携带预设的RRC释放时间确定参数或第一RRC释放时间；
    第一处理单元，用于在所述第一消息中携带所述第一RRC释放时间时，根据所述第一RRC释放时间设置第一定时器的定时时长，并启动所述第一定时器；或者第一接收单元，用于接收所述基站针对所述第一消息反馈的响应消息，其中，所述响应消息携带所述基站根据所述预设的RRC释放时间确定参数确定的第二RRC释放时间；所述第一处理单元，用于在所述第一消息中携带所述预设的RRC释放时间确定参数时，根据所述第二RRC释放时间设置所述第一定时器的定时时长，并启动所述第一定时器；
    第一判断单元，用于在所述第一定时器超时时，释放RRC连接。
  19. 如权利要求18所述的装置，其特征在于，所述预设的RRC释放时间确定参数为所述装置的待发送上行数据的数据量和/或所述待发送上行数据的发送预估时间。
  20. 如权利要求18或19所述的装置，其特征在于，还包括：
    所述第一发送单元，还用于上报BSR至所述基站，所述BSR用于指示所 述基站调整第二定时器的定时时长，其中，所述第二定时器的定时时长是所述基站根据所述UE发送的所述第一消息设置的；
    所述第一接收单元，还用于接收所述基站回复的第一调整指示；
    所述第一处理单元，还用于在接收到所述基站回复的第一调整指示时，根据所述第一调整指示，调整所述第一定时器的定时时长。
  21. 一种RRC连接释放装置，其特征在于，包括：
    第二接收单元，用于接收UE发送的第一消息，所述第一消息携带预设的RRC释放时间确定参数或第一RRC释放时间；
    第二处理单元，用于确定所述第一消息中携带所述第一RRC释放时间时，根据所述第一RRC释放时间设置第二定时器的定时时长，并启动所述第二定时器；或者所述第二处理单元，用于确定所述第一消息中携带所述预设的RRC释放时间确定参数，根据所述预设的RRC释放时间确定参数确定第二RRC释放时间，并根据所述第二RRC释放时间设置所述第二定时器的定时时长，并启动所述第二定时器；所述第二发送单元，用于针对所述第一消息给所述UE反馈响应消息，所述响应消息中携带所述第二RRC释放时间；
    第二判断单元，用于在所述第二定时器超时时，所述基站释放与所述UE之间的RRC连接。
  22. 如权利要求21所述的装置，其特征在于，所述预设的RRC释放时间确定参数为所述UE的待发送上行数据的数据量和/或所述待发送上行数据的发送预估时间。
  23. 如权利要求21或22所述的装置，其特征在于，还包括：
    所述第二接收单元，还用于接收所述UE上报的BSR；
    所述第二处理单元，还用于在接收到所述UE上报的BSR时，对所述第二定时器的定时时长进行调整，并根据所述第二定时器的定时时长调整结果生成第一调整指示以及第二调整指示；
    所述第二发送单元，还用于将所述第一调整指示回复至所述UE，将所述第二调整指示通知给MME。
  24. 如权利要求21或22所述的装置，其特征在于，还包括：
    所述第二接收单元，还用于接收所述UE发送的针对所述响应消息的确认消息；
    所述第二发送单元，还用于在所述第二接收单元接收到所述UE发送的针对所述响应消息的确认消息之后，发送S1连接恢复指示信息至MME，所述S1连接恢复指示信息携带所述第二定时器的定时时长；
    所述第二接收单元，还用于接收所述MME发送的S1连接恢复的确认指示信息；
    所述第二处理单元，还用于根据所述S1连接恢复的确认指示信息确定已恢复所述基站与所述MME之间的S1连接。
  25. 一种RRC连接释放装置，其特征在于，包括：
    第三接收单元，用于接收基站发送的S1连接恢复指示信息，所述S1连接恢复指示信息携带第二定时器的定时时长，其中，所述第二定时器的定时时长是所述基站根据UE发送的第一消息设置的，所述第一消息携带预设的RRC释放时间确定参数或第一RRC释放时间；
    第三处理单元，用于根据所述第二定时器的定时时长设置第三定时器的定时时长，并启动所述第三定时器；
    第三判断单元，用于在所述第三定时器超时时，确定所述UE释放RRC连接。
  26. 如权利要求25所述的装置，其特征在于，还包括：
    所述第三处理单元，用于根据所述S1连接恢复指示信息确定恢复与所述基站之间的S1连接；
    第三发送单元，用于向所述基站发送S1连接恢复的确认指示信息。
  27. 如权利要求25所述的装置，其特征在于，所述第三接收单元，还用于接收所述基站发送的第二调整指示；
    所述第三处理单元，还用于在所述第三接收单元接收到所述基站发送的第二调整指示时，根据所述第二调整指示调整所述第三定时器的定时时长。
  28. 一种RRC连接释放装置，其特征在于，包括：
    第四发送单元，用于向基站发送第一消息，所述第一消息携带所述UE是否需要接收下行数据的指示信息；
    第四发送单元，用于在第四处理单元确定不需要接收下行数据时，发送待发送上行数据至所述基站，所述第四处理单元，用于在最后一个上行数据包中携带Endmarker指示包，并在所述第四发送单元发送完所述最后一个上行数据包后，释放RRC连接；和/或所述第四发送单元，用于在所述第四处理单元确定需要接收下行数据时，发送待发送上行数据至所述基站，第四接收单元，用于在所述第四处理单元确定所述待发送上行数据发送完成后，接收下行数据；所述第四处理单元，用于在解析到所述第四接收单元接收的下行数据包中包含Endmarker指示包后，释放RRC连接。
  29. 如权利要求28所述的装置，其特征在于，所述第四处理单元，还用于在待发送上行数据的最后一个上行数据包的PDCP头上携带Endmarker指示包。
  30. 一种RRC连接释放装置，其特征在于，包括：
    第五接收单元，用于接收UE发送的第一消息，所述第一消息携带所述UE是否需要接收下行数据的指示信息；
    第五接收单元，用于在第五处理单元确定所述指示信息指示所述UE不需要接收下行数据时，接收所述UE发送的待发送上行数据；所述在第五处理单元，用于在解析到所述第五接收单元接收的上行数据包中包含Endmarker指示包后，释放与所述UE之间的RRC连接；和/或所述第五接收单元，用于在所述第五处理单元确定所述指示信息指示所述UE需要接收下行数据，接收所述UE发送的待发送上行数据；第五发送单元，用于在所述UE发送的所述待发送上行数据由所述第五接收单元接收完成后，继续发送下行数据至所述UE；所述第五处理单元，用于在所述第五发送单元发送到最后一个下行数据包时，在所述最后一个下行数据包中携带Endmarker指示包，并将携带Endmarker指示包的最后一个下行数据包发送至所述UE后，释放与所述UE 之间的RRC连接。
  31. 如权利要求30所述的装置，其特征在于，还包括：
    所述第五处理单元还用于确定所述指示信息指示所述UE不需要接收下行数据时，在从所述UE发送的所述待发送上行数据中解析出Endmarker指示包后，将在所述待发送上行数据的最后一个上行数据包的通用分组无线服务技术隧道协议GTP头上携带所述Endmarker指示包发往服务网关S-GW；和/或
    在所述指示信息指示所述UE需要接收下行数据时，在所述最后一个下行数据包中携带Endmarker指示包，所述第五处理单元还用于：
    在从所述S-GW发送的下行数据中解析出Endmarker指示包后，确认已接收到最后一个下行数据包；
    将在所述最后一个下行数据包的PDCP头上携带所述Endmarker指示包。
  32. 一种RRC连接释放装置，其特征在于，包括：
    第六发送单元，用于上报应用消息至网络侧设备，所述应用消息携带所述UE的应用层协议类型；
    第六判断单元，用于在与所述网络侧设备完成针对所述应用层协议类型需要交互的所有数据包后，释放RRC连接。
  33. 如权利要求32所述的装置，其特征在于，所述应用层协议类型为传输控制协议和超文本传输协议TCP/HTTP，或者用户数据报协议UDP。
  34. 一种RRC连接释放装置，其特征在于，包括：
    第七接收单元，用于接收UE上报的应用消息，所述应用消息携带所述UE的应用层协议类型；
    确定单元，用于根据所述应用层协议类型，确定所述应用层协议类型对应的传输数据包的个数；
    计数单元，用于接收并处理所述UE针对所述应用层协议类型传输的数据包，并记录处理的数据包个数；
    第七判断单元，用于当确定记录的数据包个数达到所述应用层协议类型 对应的传输数据包的个数时，释放与所述UE之间的RRC连接。
  35. 一种RRC连接释放设备，其特征在于，包括：
    第一收发器，用于向基站发送第一消息，所述第一消息携带预设的RRC释放时间确定参数或第一RRC释放时间；
    第一处理器，用于在所述第一消息中携带所述第一RRC释放时间时，根据所述第一RRC释放时间设置第一定时器的定时时长，并启动所述第一定时器；或者所述第一收发器，用于在所述第一消息中携带所述预设的RRC释放时间确定参数时，接收所述基站针对所述第一消息反馈的响应消息，其中，所述响应消息携带所述基站根据所述预设的RRC释放时间确定参数确定的第二RRC释放时间；所述第一处理器，用于根据所述第二RRC释放时间设置所述第一定时器的定时时长，并启动所述第一定时器；
    所述第一处理器，还用于在所述第一定时器超时时，释放RRC连接。
  36. 如权利要求35所述的设备，其特征在于，所述预设的RRC释放时间确定参数为所述UE的待发送上行数据的数据量和/或所述待发送上行数据的发送预估时间。
  37. 如权利要求35或36所述的设备，其特征在于，所述第一收发器，还用于上报BSR至所述基站，所述BSR用于指示所述基站调整第二定时器的定时时长，其中，所述第二定时器的定时时长是所述基站根据所述UE发送的所述第一消息设置的；以及接收所述基站回复的第一调整指示；
    所述第一处理器，还用于在接收到所述基站回复的第一调整指示时，根据所述第一调整指示，调整所述第一定时器的定时时长。
  38. 一种RRC连接释放设备，其特征在于，包括：
    第二收发器，用于接收UE发送的第一消息，所述第一消息携带预设的RRC释放时间确定参数或第一RRC释放时间；
    第二处理器，用于确定所述第一消息中携带所述第一RRC释放时间时，根据所述第一RRC释放时间设置第二定时器的定时时长，并启动所述第二定时器；或者所述第二处理器，用于确定所述第一消息中携带所述预设的RRC 释放时间确定参数，根据所述预设的RRC释放时间确定参数确定第二RRC释放时间，并根据所述第二RRC释放时间设置所述第二定时器的定时时长，并启动所述第二定时器；所述第二收发器，用于针对所述第一消息给所述UE反馈响应消息，所述响应消息中携带所述第二RRC释放时间；
    所述第二处理器，还用于在所述第二定时器超时时，释放与所述UE之间的RRC连接。
  39. 如权利要求38所述的设备，其特征在于，所述预设的RRC释放时间确定参数为所述UE的待发送上行数据的数据量和/或所述待发送上行数据的发送预估时间。
  40. 如权利要求38或39所述的设备，其特征在于，还包括：
    所述第二收发器，还用于接收所述UE上报的BSR；
    所述第二处理器，还用于在所述第二收发器接收到所述UE上报的BSR时，对所述第二定时器的定时时长进行调整，并根据所述第二定时器的定时时长调整结果生成第一调整指示以及第二调整指示；
    所述第二收发器，还用于将所述第一调整指示回复至所述UE，将所述第二调整指示通知给MME。
  41. 如权利要求38或39所述的设备，其特征在于，所述第二收发器，还用于接收所述UE发送的针对所述响应消息的确认消息，并在接收到所述UE发送的针对所述响应消息的确认消息之后，发送S1连接恢复指示信息至MME，所述S1连接恢复指示信息携带所述第二定时器的定时时长；以及接收所述MME发送的S1连接恢复的确认指示信息；
    所述第二处理器，用于根据所述S1连接恢复的确认指示信息确定已恢复所述基站与所述MME之间的S1连接。
  42. 一种RRC连接释放设备，其特征在于，包括：
    第三收发器，用于接收基站发送的S1连接恢复指示信息，所述S1连接恢复指示信息携带第二定时器的定时时长，其中，所述第二定时器的定时时长是所述基站根据UE发送的第一消息设置的，所述第一消息携带预设的RRC 释放时间确定参数或第一RRC释放时间；
    第三处理器，用于根据所述第二定时器的定时时长设置第三定时器的定时时长，并启动所述第三定时器；
    以及用于在所述第三定时器超时时，确定所述UE释放RRC连接。
  43. 如权利要求42所述的设备，其特征在于，还包括：
    所述第三处理器，还用于根据所述S1连接恢复指示信息确定恢复与所述基站之间的S1连接；
    所述第三收发器，还用于向所述基站发送S1连接恢复的确认指示信息。
  44. 如权利要求42所述的设备，其特征在于，所述第三收发器，用于接收到所述基站发送的第二调整指示；
    所述第三处理器，用于根据所述第二调整指示调整所述第三定时器的定时时长。
  45. 一种RRC连接释放设备，其特征在于，包括：
    第四收发器，用于向基站发送第一消息，所述第一消息携带所述UE是否需要接收下行数据的指示信息；
    所述第四收发器，用于在第四处理器确定不需要接收下行数据时，发送待发送上行数据至所述基站，所述第四处理器在最后一个上行数据包中携带Endmarker指示包，在所述第四收发器发送完所述最后一个上行数据包后，释放RRC连接；和/或所述第四收发器，用于在所述第四处理器确定需要接收下行数据时，将所述待发送上行数据发送完成后，接收下行数据；所述第四处理器，用于解析到接收的下行数据包中包含Endmarker指示包后，释放RRC连接。
  46. 如权利要求45所述的设备，其特征在于，所述第四处理器还用于在待发送上行数据的最后一个上行数据包的PDCP头上携带Endmarker指示包。
  47. 一种RRC连接释放设备，其特征在于，包括：
    第五收发器，用于接收UE发送的第一消息，所述第一消息携带所述UE 是否需要接收下行数据的指示信息；
    所述第五收发器，用于在第五处理器确定所述指示信息指示所述UE不需要接收下行数据时，接收所述UE发送的待发送上行数据；所述第五处理器，用于解析到接收的上行数据包中包含Endmarker指示包后，释放与所述UE之间的RRC连接；和/或所述第五收发器，用于在所述第五处理器确定所述指示信息指示所述UE需要接收下行数据，在所述UE发送的所述待发送上行数据接收完成后，继续发送下行数据至所述UE；所述第五处理器，用于在所述第五收发器发送到最后一个下行数据包时，在所述最后一个下行数据包中携带Endmarker指示包，在所述第五收发器将携带Endmarker指示包的最后一个下行数据包发送至所述UE后，释放与所述UE之间的RRC连接。
  48. 如权利要求47所述的设备，其特征在于，还包括：
    所述第五处理器，还用于确定所述指示信息指示所述UE不需要接收下行数据时，在从所述UE发送的所述待发送上行数据中解析出Endmarker指示包后，将在所述待发送上行数据的最后一个上行数据包的通用分组无线服务技术隧道协议GTP头上携带所述Endmarker指示包发往服务网关S-GW；和/或
    在所述指示信息指示所述UE需要接收下行数据时，在所述最后一个下行数据包中携带Endmarker指示包，所述第五处理器，还用于：
    在从所述S-GW发送的下行数据中解析出Endmarker指示包后，确认已接收到最后一个下行数据包；
    将在所述最后一个下行数据包的PDCP头上携带所述Endmarker指示包。
  49. 一种RRC连接释放设备，其特征在于，包括：
    第六收发器，用于上报应用消息至网络侧设备，所述应用消息携带所述UE的应用层协议类型；
    第六处理器，用于在与所述网络侧设备完成针对所述应用层协议类型需要交互的所有数据包后，释放RRC连接。
  50. 如权利要求49所述的设备，其特征在于，所述应用层协议类型为传输控制协议和超文本传输协议TCP/HTTP，或者用户数据报协议UDP。
  51. 一种RRC连接释放设备，其特征在于，包括：
    第七收发器，用于接收UE上报的应用消息，所述应用消息携带所述UE的应用层协议类型；
    第七处理器，用于根据所述应用层协议类型，确定所述应用层协议类型对应的传输数据包的个数；
    所述第七收发器，用于接收所述UE针对所述应用层协议类型传输的数据包；
    所述第七处理器，用于处理所述UE针对所述应用层协议类型传输的数据包，并记录处理的数据包个数；
    以及当确定记录的数据包个数达到所述应用层协议类型对应的传输数据包的个数时，释放与所述UE之间的RRC连接。
PCT/CN2015/098406 2015-12-23 2015-12-23 一种rrc连接释放方法、装置及设备 WO2017107093A1 (zh)

Priority Applications (4)

Application Number Priority Date Filing Date Title
CN201580085258.9A CN108370605B (zh) 2015-12-23 2015-12-23 一种rrc连接释放方法、装置及设备
EP15911092.3A EP3383126B1 (en) 2015-12-23 2015-12-23 Rrc link release method, device, and equipment
PCT/CN2015/098406 WO2017107093A1 (zh) 2015-12-23 2015-12-23 一种rrc连接释放方法、装置及设备
US16/015,867 US10694576B2 (en) 2015-12-23 2018-06-22 RRC connection release method, apparatus, and device

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2015/098406 WO2017107093A1 (zh) 2015-12-23 2015-12-23 一种rrc连接释放方法、装置及设备

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US16/015,867 Continuation US10694576B2 (en) 2015-12-23 2018-06-22 RRC connection release method, apparatus, and device

Publications (1)

Publication Number Publication Date
WO2017107093A1 true WO2017107093A1 (zh) 2017-06-29

Family

ID=59088876

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2015/098406 WO2017107093A1 (zh) 2015-12-23 2015-12-23 一种rrc连接释放方法、装置及设备

Country Status (4)

Country Link
US (1) US10694576B2 (zh)
EP (1) EP3383126B1 (zh)
CN (1) CN108370605B (zh)
WO (1) WO2017107093A1 (zh)

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN110301163A (zh) * 2017-08-11 2019-10-01 联发科技股份有限公司 用于物联网的用户设备自动释放
CN116634432A (zh) * 2023-07-21 2023-08-22 浙江大华技术股份有限公司 一种数据传输方法及装置

Families Citing this family (9)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP3419377B1 (en) * 2016-04-01 2020-05-13 KYOCERA Corporation Base station and wireless terminal
US10470218B2 (en) * 2016-05-16 2019-11-05 Cisco Technology, Inc. System and method for optimized idle and active state transitions of user equipment in a network environment
CN116033603A (zh) * 2017-11-16 2023-04-28 中兴通讯股份有限公司 连接控制、业务处理方法及装置
US10749784B2 (en) * 2018-06-29 2020-08-18 Rohde & Schwarz Gmbh & Co. Kg Test system and method for IoT e2e testing
CN111629434B (zh) * 2019-02-27 2023-06-30 ***通信有限公司研究院 一种控制rrc连接释放的方法和装置
CN113196858B (zh) * 2019-07-11 2022-08-12 Oppo广东移动通信有限公司 用于发送释放辅助指示消息的方法及设备
CN111148194B (zh) * 2019-07-31 2022-07-29 广东小天才科技有限公司 一种基于可穿戴设备的数据传输方法及可穿戴设备
US11751279B2 (en) * 2020-01-07 2023-09-05 Mediatek Inc. Apparatuses and methods for multi-radio access technology (RAT) coordination
CN114173431B (zh) * 2020-09-11 2023-12-29 华为技术有限公司 一种rrc连接释放的方法及装置

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20120033597A1 (en) * 2007-01-15 2012-02-09 Samsung Electronics Co., Ltd. Method and apparatus for processing uplink data by drx-mode terminal in mobile telecommunication system
CN103313311A (zh) * 2012-03-16 2013-09-18 中兴通讯股份有限公司 一种无线资源管理方法、用户设备和网络侧
US20140057639A1 (en) * 2012-08-24 2014-02-27 Samsung Electronics Co. Ltd. Method for achieving fast dormancy of user equipment (ue) in cell_pch or ura_pch state in umts
CN103716912A (zh) * 2012-10-09 2014-04-09 电信科学技术研究院 一种释放无线资源控制连接的方法、装置及***
CN103733658A (zh) * 2011-07-29 2014-04-16 Sca艾普拉控股有限公司 移动通信网络、基础设施设备和方法

Family Cites Families (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US9497566B2 (en) * 2010-03-23 2016-11-15 Interdigital Patent Holdings, Inc. Efficient signaling for machine type communication
WO2012096490A2 (ko) * 2011-01-10 2012-07-19 엘지전자 주식회사 무선 통신 시스템에서 단말의 셀 접속 제한 방법 및 이를 위한 장치
US9485726B2 (en) * 2012-02-06 2016-11-01 Samsung Electronics Co., Ltd. Method and apparatus for activating sleep mode of terminal
WO2014019139A1 (zh) * 2012-07-31 2014-02-06 华为技术有限公司 一种实现无线资源控制连接释放的方法、装置及***
US8923880B2 (en) * 2012-09-28 2014-12-30 Intel Corporation Selective joinder of user equipment with wireless cell
EP3337286B1 (en) 2015-09-16 2022-01-12 Huawei Technologies Co., Ltd. Method and apparatus for releasing radio resource control (rrc) connection

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20120033597A1 (en) * 2007-01-15 2012-02-09 Samsung Electronics Co., Ltd. Method and apparatus for processing uplink data by drx-mode terminal in mobile telecommunication system
CN103733658A (zh) * 2011-07-29 2014-04-16 Sca艾普拉控股有限公司 移动通信网络、基础设施设备和方法
CN103313311A (zh) * 2012-03-16 2013-09-18 中兴通讯股份有限公司 一种无线资源管理方法、用户设备和网络侧
US20140057639A1 (en) * 2012-08-24 2014-02-27 Samsung Electronics Co. Ltd. Method for achieving fast dormancy of user equipment (ue) in cell_pch or ura_pch state in umts
CN103716912A (zh) * 2012-10-09 2014-04-09 电信科学技术研究院 一种释放无线资源控制连接的方法、装置及***

Non-Patent Citations (1)

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

Cited By (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN110301163A (zh) * 2017-08-11 2019-10-01 联发科技股份有限公司 用于物联网的用户设备自动释放
CN116634432A (zh) * 2023-07-21 2023-08-22 浙江大华技术股份有限公司 一种数据传输方法及装置
CN116634432B (zh) * 2023-07-21 2023-10-03 浙江大华技术股份有限公司 一种数据传输方法及装置

Also Published As

Publication number Publication date
CN108370605B (zh) 2020-12-15
EP3383126A1 (en) 2018-10-03
US20180302947A1 (en) 2018-10-18
US10694576B2 (en) 2020-06-23
EP3383126B1 (en) 2021-03-03
CN108370605A (zh) 2018-08-03
EP3383126A4 (en) 2019-01-09

Similar Documents

Publication Publication Date Title
WO2017107093A1 (zh) 一种rrc连接释放方法、装置及设备
US10477428B2 (en) Node and method for buffering downlink data
CN109076330B (zh) 无线通信***中跟踪区域更新的方法及其装置
CN108370506B (zh) 无线通信***中的服务节点重新定位方法及其设备
US10034327B2 (en) Method and apparatus in a telecommunication system
CN107113598B (zh) 演进分组***中的移动台终止的通信的支持
EP2578043B1 (en) Connection states for a user entity in a serving gateway of an evolved packet core system
WO2018202351A1 (en) Paging policy differentiation in 5g system
US20170311371A1 (en) Method and nodes for handling connections in a communications system
WO2014127515A1 (zh) 业务提供***、方法、移动边缘应用服务器及支持节点
WO2013040962A1 (zh) 数据发送和接收方法及设备
EP3442290A1 (en) Data transmission method and apparatus, and computer storage medium
WO2020233249A1 (zh) 一种报文传输方法以及相关装置
CN112514528A (zh) 用于5g蜂窝物联网的用户平面优化
US11044696B2 (en) Downlink data notification message sending method, and apparatus
WO2015042911A1 (zh) 寻呼方法、网络设备和通信***
EP3375116B1 (en) Timeout of a communication radio link
TW201714435A (zh) 處理尋呼程序的裝置及方法
US20170111929A1 (en) Handling messages
WO2018087034A1 (en) Infrequent small data for battery saving wireless devices
WO2015010325A1 (zh) 数据传输方法及装置

Legal Events

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

Ref document number: 15911092

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

WWE Wipo information: entry into national phase

Ref document number: 2015911092

Country of ref document: EP

ENP Entry into the national phase

Ref document number: 2015911092

Country of ref document: EP

Effective date: 20180629