Method, apparatus, and device for managing RRC connection

Abstract

An embodiment of the present invention provides a method, apparatus, and device for managing RRC connections, which relate to the field of communication technologies. The method includes: when the UE is in the RRC idle state, the UE uses a shared data transmission resource to send an uplink data request to an access network node, and the uplink data request includes uplink data and request information for requesting to enter the RRC connected state; the UE receives the access network specific identifier of the UE sent by the access network node, and the access network specific identifier of the UE is determined by the access network node according to the request information. During the validity period of the access network specific identifier of the UE, the UE is in the RRC connected state. The technical solution provided by the embodiment of the present invention requests to enter the RRC connected state while sending uplink data, reduces the signaling overhead required for creating or restoring an RRC connection, and achieves the technical effect of quickly and efficiently creating or restoring an RRC connection.

Description

Technical Field

[0001] Embodiments of the present invention relate to the field of communication technologies, and in particular, to a method, an apparatus, and a device for managing a Radio Resource Control (RRC) connection. Background Art

[0002] With the popularization of intelligent terminal devices such as smart phones, various Machine to Machine (M2M) services have been widely applied, such as intelligent meter reading, intelligent transportation, and intelligent medical services. These services have certain regularities. For example, the amount of data transmitted each time is small, the time interval between each transmission is relatively fixed, and the device is in an idle state when there is no service data transmission.

[0003] In view of the above small packet transmission scenario, in order to improve data transmission efficiency and reduce the large amount of signaling overhead caused by establishing a bearer, in the prior art, a solution for a User Equipment (UE) to switch from the RRC idle state to the RRC connected state is provided. The specific solution is as follows. When the UE switches from the RRC connected state to the RRC idle state, the base station instructs the UE to store the context information of the RRC connection and notifies the UE of an identifier for indicating the restoration of the RRC connection. In addition, the base station saves the context information of the S1 interface with the core network and notifies the Mobility Management Entity (MME) to deactivate the data channel between it and the Gateway (GW). When the UE needs to transmit uplink service data to the base station, the UE initiates a random access process and sends an RRC connection restoration request to the base station in the form of an RRC message. The RRC connection restoration request carries the above identifier for indicating the restoration of the RRC connection. After receiving the RRC connection restoration request, the base station restores the RRC connection with the UE and notifies the MME to restore the data channel between it and the GW. Then, the UE uses the restored RRC connection to send uplink service data to the base station. In addition, after receiving the above RRC message, the base station activates the original security parameters (i.e., the security parameters used by the UE in the previous RRC connected state), and the UE and the base station use the original security parameters to protect the security of the service data.

[0004] However, in the process of the UE switching from the RRC idle state to the RRC connected state in the above solution provided by the prior art, the UE requests the base station to restore the RRC connection through an RRC message, and there are many steps of signaling interaction between the UE and the base station to restore data transmission, resulting in low efficiency. Summary of the Invention

[0005] To overcome the problems existing in the prior art, an embodiment of the present invention provides a method, an apparatus, and a device for managing RRC connections. The technical solution is as follows:

[0006] In a first aspect, a method for managing RRC connections is provided. The method includes: when the UE is in the RRC idle state, the UE sends an uplink data request to an access network node by using a shared data transmission resource; wherein, the uplink data request includes uplink data and request information for requesting to enter the RRC connected state; the UE receives the access network specific identifier of the UE sent by the access network node; wherein, the access network specific identifier of the UE is determined by the access network node according to the request information, and within the validity period of the access network specific identifier of the UE, the UE is in the RRC connected state.

[0007] By the UE sending an uplink data request to the access network node by using a shared data transmission resource when the UE is in the RRC idle state, and the uplink data request includes, in addition to the uplink data, request information for requesting to enter the RRC connected state, so that the access network node establishes an RRC connection with the UE according to the request information; it solves the problem that in the process of the UE switching from the RRC idle state to the RRC connected state in the solution provided by the prior art, the UE requests the base station to resume the RRC connection through RRC messages, and there are many steps of signaling interaction between the UE and the base station to resume data transmission, resulting in low efficiency; requesting to enter the RRC connected state while sending the uplink data reduces the signaling overhead required to create or resume the RRC connection, and achieves the technical effect of quickly and efficiently creating or resuming the RRC connection.

[0008] In a first possible implementation manner of the first aspect, the request information includes: the non-access stratum identity of the UE (English: Non-access Atratum Identity; abbreviation: NAS ID) and a first indication information for requesting to create an RRC connection.

[0009] When the UE in the RRC idle state has uplink data to transmit, by the UE requesting to create an RRC connection while sending the uplink data to the access network node, fast and efficient data transmission and connection establishment are realized.

[0010] Combined with the first possible implementation manner of the first aspect, in a second possible implementation manner of the first aspect, before the UE sends an uplink data request to the access network node by using a shared data transmission resource, it further includes: the UE negotiates a first security parameter and a second security parameter with a core network node; wherein, the first security parameter is used for security protection of the uplink data, and the second security parameter is used for security protection of NAS signaling; the UE performs security protection on the uplink data by using the first security parameter.

[0011] The UE negotiates with the core network node for the first security parameter and uses the first security parameter to protect the security of the uplink data, thus ensuring the security of the uplink data.

[0012] In the third possible implementation manner of the first aspect, the request information includes: the access network specific identifier used by the UE in the RRC connected state before the RRC idle state and the second indication information for requesting to resume the RRC connection.

[0013] When the UE in the RRC idle state has uplink data to transmit, the UE requests to resume the RRC connection while sending the uplink data to the access network node, realizing fast and efficient data transmission and connection recovery.

[0014] Combined with the third possible implementation manner of the first aspect, in the fourth possible implementation manner of the first aspect, before the UE uses the shared data transmission resource to send an uplink data request to the access network node, it further includes: when the UE is in the RRC connected state before the RRC idle state, the UE negotiates with the access network node for the target security parameter to be used when entering the RRC connected state next time, and the target security parameter has not been used in the previous RRC connected state; the UE uses the target security parameter to protect the security of the uplink data.

[0015] When the UE is in the RRC connected state, it negotiates with the access network node for the target security parameter to be used when entering the RRC connected state next time, and the target security parameter has not been used in the previous RRC connected state, so as to ensure that different security parameters are used to protect the data in each RRC connected state, realizing secure connection recovery. Compared with the prior art that still uses the original security parameter to protect the data after resuming the RRC connection, the solution provided by this embodiment has higher security.

[0016] Combined with the first aspect or any possible implementation manner of the first aspect, in the fifth possible implementation manner of the first aspect, the method further includes: within the validity period of the access network specific identifier of the UE, if the UE moves outside the n cells corresponding to the access network specific identifier of the UE, the UE sends an identifier re-determination request to the access network node. Wherein, the access network specific identifier of the UE is unique within the n cells, and n is a positive integer. The identifier re-determination request is used to request the access network node to re-determine the access network specific identifier of the UE. The identifier re-determination request is sent together with the uplink data, or the identifier re-determination request is sent in the form of a Media Access Control (MAC) layer control packet.

[0017] By the above method, in the case of cross-cell movement of the UE, the availability of the RRC connection is still effectively ensured.

[0018] In combination with the first aspect or any possible implementation manner of the first aspect, in the sixth possible implementation manner of the first aspect, the UE receives the access network specific identifier of the UE sent by the access network node, including: the UE receives the confirmation response sent by the access network node. The confirmation response is used to indicate that the access network node has confirmed the receipt of the uplink data, and the confirmation response includes the first item or both items of the access network specific identifier of the UE and the security parameter confirmation information.

[0019] By carrying the access network specific identifier of the UE in the confirmation response fed back to the UE, the signaling overhead is further reduced.

[0020] In combination with the first aspect or any possible implementation manner of the first aspect, in the seventh possible implementation manner of the first aspect, after the UE receives the access network specific identifier of the UE sent by the access network node, it further includes: the UE starts a first timer, and before the first timer expires, the access network specific identifier of the UE is within the validity period.

[0021] By maintaining the timer, it is determined whether to disconnect the RRC connection according to whether the timer expires.

[0022] In combination with the seventh possible implementation manner of the first aspect, in the eighth possible implementation manner of the first aspect, after the UE starts the first timer, it further includes: after the UE sends the uplink data to the access network node, the first timer is restarted; or, after the UE receives the downlink data from the access network node, the first timer is restarted.

[0023] By the above method, it is ensured that the RRC connection is maintained in the case of data transmission, and the RRC connection is disconnected in the case of no data transmission for a long time, so as to realize the effective management of the RRC connection.

[0024] In a second aspect, a method for managing an RRC connection is provided. The method includes: the access network node receives an uplink data request sent by the UE using a shared data sending resource when the UE is in the RRC idle state; the uplink data request includes uplink data and request information for requesting to enter the RRC connected state; the access network node establishes an RRC connection with the UE according to the request information and determines the access network specific identifier of the UE; the access network node sends the access network specific identifier of the UE to the UE; during the validity period of the access network specific identifier of the UE, the UE is in the RRC connected state.

[0025] In the first possible implementation manner of the second aspect, the request information includes: the NAS ID of the UE and the first indication information for requesting to create an RRC connection. Accordingly, the access network node establishes an RRC connection with the UE according to the request information, and determines the access network specific identifier of the UE, including: the access network node creates an RRC connection with the UE according to the first indication information, and assigns an access network specific identifier of the UE corresponding to the NAS ID.

[0026] Combined with the first possible implementation manner of the second aspect, in the second possible implementation manner of the second aspect, the uplink data is protected by security using the first security parameter negotiated between the UE and the core network node. Among them, the UE and the core network node negotiate the first security parameter and the second security parameter. The first security parameter is used to protect the uplink data by security, and the second security parameter is used to protect the NAS signaling by security.

[0027] In the third possible implementation manner of the second aspect, the request information includes: the access network specific identifier used by the UE in the RRC connection state before the RRC idle state and the second indication information for requesting to resume the RRC connection. Accordingly, the access network node establishes an RRC connection with the UE according to the request information, and determines the access network specific identifier of the UE, including: the access network node resumes the RRC connection with the UE according to the second indication information, and resumes enabling the access network specific identifier of the UE.

[0028] Combined with the third possible implementation manner of the second aspect, in the fourth possible implementation manner of the second aspect, the uplink data is protected by security using the target security parameter negotiated between the UE and the access network node. Accordingly, before the access network node receives the uplink data request sent by the UE using the shared data transmission resource when the UE is in the RRC idle state, it further includes: when the UE is in the RRC connection state before the above RRC idle state, the access network node and the UE negotiate the target security parameter to be used when entering the RRC connection state next time, and this target security parameter has not been used in the previous RRC connection state.

[0029] Combined with the second aspect or any one of the possible implementation manners of the second aspect, in the fifth possible implementation manner of the second aspect, the access network node sends the access network specific identifier of the UE to the UE, including: the access network node sends an acknowledgment response to the UE. Among them, the acknowledgment response is used to indicate that the access network node acknowledges that it has received the uplink data, and the acknowledgment response includes the first item or both items of the access network specific identifier of the UE and the security parameter confirmation information.

[0030] Combined with the second aspect or any possible implementation manner of the second aspect, in the sixth possible implementation manner of the second aspect, after the access network node sends the access network specific identifier of the UE to the UE, it further includes: the access network node starts a second timer, and before the second timer expires, the access network specific identifier of the UE is within the valid period.

[0031] Combined with the sixth possible implementation manner of the second aspect, in the seventh possible implementation manner of the second aspect, after the access network node starts the second timer, it further includes: after the access network node sends downlink data to the UE, it restarts the second timer; or, after the access network node receives uplink data from the UE, it restarts the second timer.

[0032] Combined with the sixth possible implementation manner of the second aspect, in the eighth possible implementation manner of the second aspect, after the access network node starts the second timer, it further includes: after the second timer expires, the access network node sends a notification message to the MME. The notification message is used to instruct the MME to release the signaling connection between the MME and the access network node and the dedicated data bearer of the UE between the MME and the GW.

[0033] The method on the access network node side corresponds to the method on the UE side, and the achieved technical effects are the same or similar.

[0034] In a third aspect, a device for managing RRC connections is provided, and this device is applied to the UE. The functional units included in this device are used to implement the method provided in the first aspect above.

[0035] In a fourth aspect, a device for managing RRC connections is provided, and this device is applied to the access network node. The functional units included in this device are used to implement the method provided in the second aspect above.

[0036] In a fifth aspect, a UE is provided, and this UE includes: a processor, a memory, and a transceiver. The memory is used to store one or more instructions, and these instructions are configured to be executed by the processor, and these instructions are used to implement the method provided in the first aspect above.

[0037] In a sixth aspect, an access network node is provided, and this access network node includes: a processor, a memory, and a transceiver. The memory is used to store one or more instructions, and these instructions are configured to be executed by the processor, and these instructions are used to implement the method provided in the second aspect above. Description of the Drawings

[0038] To more clearly illustrate the technical solutions in the embodiments of the present invention, the following briefly introduces the accompanying drawings required for the description of the embodiments. Obviously, the accompanying drawings in the following description are only some embodiments of the present invention. For those of ordinary skill in the art, without creative efforts, other accompanying drawings can be obtained based on these drawings.

[0039] Figure 1 It is a schematic diagram of an implementation environment related to an embodiment of the present invention;

[0040] Figure 2 It is a flowchart of a method for managing RRC connections provided by an embodiment of the present invention;

[0041] Figure 3 It is a flowchart of a method for managing RRC connections provided by another embodiment of the present invention;

[0042] Figure 4 It is a flowchart of a method for managing RRC connections provided by another embodiment of the present invention;

[0043] Figure 5 It is a flowchart of a method for managing RRC connections provided by another embodiment of the present invention;

[0044] Figure 6A It is a block diagram of a device for managing RRC connections provided by an embodiment of the present invention;

[0045] Figure 6B It is a block diagram of a device for managing RRC connections provided by another embodiment of the present invention;

[0046] Figure 7A It is a block diagram of a device for managing RRC connections provided by another embodiment of the present invention;

[0047] Figure 7B It is a block diagram of a device for managing RRC connections provided by another embodiment of the present invention;

[0048] Figure 8 It is a block diagram of a system for managing RRC connections provided by an embodiment of the present invention;

[0049] Figure 9 It is a block diagram of a UE provided by an embodiment of the present invention;

[0050] Figure 10 It is a block diagram of an access network node provided by an embodiment of the present invention. Detailed implementation manners

[0051] The following describes the embodiments of the present invention with reference to the accompanying drawings.

[0052] Please refer to Figure 1, which shows a schematic diagram of an implementation environment related to an embodiment of the present invention. The implementation environment includes: UE110, access network node 120, and core network node 130.

[0053] UE110 may include a handheld device with wireless communication capabilities (such as a mobile phone), a vehicle-mounted device, a wearable device, a computing device, or other processing devices connected to a wireless modem, as well as various forms of user equipment (abbreviation: UE), mobile station (abbreviation: MS), terminal, terminal equipment (abbreviation: TE), etc. For convenience of description, it is simply referred to as user equipment or UE in this application.

[0054] The access network node 120 is a network element in the access network. As Figure 1 shown, taking the Universal Mobile Telecommunications System (abbreviation: UMTS) as an example, the access network node 120 can be a Node B or a Radio Network Controller (abbreviation: RNC) (not shown in the figure). In the Long Term Evolution (abbreviation: LTE) wireless network architecture, the base station is an Evolved Node Base station (abbreviation: eNB).

[0055] The core network node 130 is a network element in the core network (abbreviation: CN). As Figure 1 shown, taking the LTE wireless network architecture as an example, the core network node 130 includes an MME and a Serving GateWay (abbreviation: S-GW) / PDN GateWay (abbreviation: P-GW). The MME is mainly used to complete the mobility management and session management of UE110. The S-GW is mainly responsible for forwarding data between the eNB and the P-GW. The P-GW is mainly responsible for processing Internet Protocol (abbreviation: IP) data services.

[0056] In Figure 1In the illustrated implementation environment, only the network architecture of the Fourth Generation of Mobile Phone Mobile Communication Technology Standards (abbreviation: 4G) is used as an example for illustration. The technical solution provided by the present invention is equally applicable to other existing types of wireless communication networks or future wireless communication networks, such as the Fifth Generation of Mobile Communication Technology Standards (abbreviation: 5G) network, etc.

[0057] Please refer to Figure 2 , which shows a flowchart of a method for managing an RRC connection provided by an embodiment of the present invention. This method can be applied to Figure 1 the illustrated implementation environment. The method may include the following steps:

[0058] Step 202, when the UE is in the RRC idle state, the UE sends an uplink data request to the access network node by using a shared data transmission resource; wherein, the uplink data request includes uplink data and request information for requesting to enter the RRC connected state.

[0059] Extendably, the RRC idle state in the embodiment of the present invention may be a power-saving state that saves the access network specific identifier of the UE. That is, different from the traditional RRC idle state, when the UE is in the traditional RRC idle state, all context information in the RRC connected state (including the access network specific identifier of the UE) is released. In the embodiment of the present invention, when the UE is in the RRC idle state, the UE may save some context information in the RRC connected state, such as the access network specific identifier of the UE.

[0060] Correspondingly, the access network node receives the uplink data request sent by the UE.

[0061] Step 204, the access network node establishes an RRC connection with the UE according to the request information and determines the access network specific identifier of the UE.

[0062] Step 206, the access network node sends the access network specific identifier of the UE to the UE; wherein, within the validity period of the access network specific identifier of the UE, the UE is in the RRC connected state.

[0063] Correspondingly, the UE receives the access network specific identifier of the UE sent by the access network node.

[0064] In another possible implementation, the uplink data request sent by the UE to the access network node does not include the request information for requesting to enter the RRC connected state. That is, the UE uses the shared data transmission resource to send an uplink data request carrying uplink data to the access network node, as an implicit request method for requesting to enter the RRC connected state. Correspondingly, after receiving the uplink data request sent by the UE using the shared data transmission resource, the access network node establishes an RRC connection with the UE and determines the access network specific identifier of the UE. For example, an access network specific identifier is assigned to a UE without an access network specific identifier.

[0065] In summary, the method provided in this embodiment enables the access network node to establish an RRC connection with the UE according to the request information by the UE in the RRC idle state using the shared data transmission resource to send an uplink data request, where the uplink data request includes, in addition to the uplink data, the request information for requesting to enter the RRC connected state; it solves the problem that in the prior art solution during the process of the UE switching from the RRC idle state to the RRC connected state, the UE requests the base station to resume the RRC connection through RRC messages, and there are many steps of signaling interactions between the UE and the base station to resume data transmission, with low efficiency; by requesting to enter the RRC connected state while sending the uplink data, it reduces the signaling overhead required for creating or resuming the RRC connection, achieving the technical effect of quickly and efficiently creating or resuming the RRC connection.

[0066] The embodiments of the present invention provide two solutions for the UE to quickly enter the RRC connected state. In the embodiments shown below Figure 3 when the UE in the RRC idle state sends uplink data to the access network node, it requests to create an RRC connection. In the small packet transmission scenario, the requested RRC connection can be referred to as a lightweight RRC connection (i.e., light RRC connection). In the embodiments shown below Figure 4 when the UE in the RRC idle state sends uplink data to the access network node, it requests to resume the RRC connection. The requested RRC connection is the RRC connection used in the RRC connected state before the RRC idle state. Next, through Figure 3 and Figure 4 two embodiments, the above two solutions are respectively introduced and described.

[0067] Please refer to Figure 3 , which shows a flowchart of a method for managing an RRC connection provided by another embodiment of the present invention. This embodiment is illustrated by taking the application of this method in the Figure 1 shown implementation environment as an example. The method may include the following steps:

[0068] Step 301, the UE negotiates with the core network node for the first security parameter and the second security parameter.

[0069] The first security parameter is used to protect the security of the uplink data. Among them, the uplink data can be uplink user plane data or uplink control plane signaling. The first security parameter includes at least one of the following parameters: encryption algorithm, key corresponding to the encryption algorithm, integrity protection algorithm, and key corresponding to the integrity protection algorithm. The second security parameter is used to protect the security of the NAS signaling. In this embodiment, the UE negotiates the security parameters with the core network node. The core network node can be an MME or a GW.

[0070] Extendably, the first security parameter is used by the UE to send uplink data to the access network node through the shared data sending resource, and the second security parameter is used by the UE to send uplink data to the access network node through the dedicated data sending resource. Thus, two different encryption modes are adopted when requesting to enter the RRC connected state and after entering the RRC connection, to achieve security isolation.

[0071] Step 302, when the UE is in the RRC idle state, it uses the shared data sending resource to send an uplink data request to the access network node.

[0072] The uplink data request includes uplink data and request information for requesting to enter the RRC connected state. In this embodiment, the request information includes: the NAS ID of the UE and the first indication information for requesting to create an RRC connection. For example, the NAS ID can be the Serving–Temporary Mobile Subscriber Identity (S-TMSI) or IP.

[0073] In addition, in the prior art, when the UE is in the RRC idle state and needs to send uplink data to the access network node, it first needs to send a scheduling request to the access network node, and this scheduling request is used to request the access network node to allocate a data sending resource. Then the UE uses the allocated data sending resource to send the uplink data to the access network node. Different from the prior art, in this embodiment, the access network node pre-allocates a group of shared data sending resources (also called a shared resource pool) for the UEs in the cell. When the UE needs to send uplink data to the access network node, the UE selects a data sending resource from the above pre-configured shared resource pool and uses the selected data sending resource to send an uplink data request to the access network node. Optionally, the access network node pre-allocates a shared data sending resource for a group of UEs in the cell, and the UE uses this shared data sending resource to send the uplink data request when sending.

[0074] Taking the data transmission resource as the Physical Uplink Shared Channel (PUSCH) as an example. The access network node may pre-allocate a set of shared PUSCH resources for UEs in the cell by using the System Information Block (SIB) message. When a UE in the RRC idle state has uplink data transmission, it selects a PUSCH from the pre-allocated shared PUSCH resources according to a preset rule, and uses the selected PUSCH to send an uplink data request to the access network node.

[0075] Correspondingly, the access network node receives the uplink data request sent by the UE.

[0076] Optionally, in order to ensure the security of the uplink data, the UE uses the first security parameter negotiated with the core network node to protect the security of the uplink data.

[0077] Step 303, the access network node creates an RRC connection with the UE according to the first indication information, and allocates an access network specific identifier of the UE corresponding to the NAS ID.

[0078] In this embodiment, after receiving the uplink data request sent by the UE, the access network node creates an RRC connection with the UE according to the first indication information, that is, the light RRC connection described above. And the access network node allocates an access network specific identifier for the UE. The access network specific identifier of the UE may be a Radio Network Tempory Identity (RNTI). The RNTI may be unique in a cell, that is, the Cell Radio Network Tempory Identity (C-RNTI); or the RNTI may also be unique in multiple cells. In addition, the access network node stores the correspondence between the NAS ID of the UE and the access network specific identifier.

[0079] Step 304, the access network node sends the access network specific identifier of the UE to the UE.

[0080] Correspondingly, the UE receives the access network specific identifier sent by the access network node. During the validity period of the access network specific identifier of the UE, the UE is in the RRC connected state.

[0081] In a possible implementation, the access network node carries the access network specific identifier of the UE in the acknowledgment response sent to the UE. Specifically, the access network node sends an acknowledgment response to the UE, which is used to indicate that the access network node has received the uplink data, and the acknowledgment response includes the access network specific identifier of the UE. Correspondingly, the UE receives the acknowledgment response sent by the access network node.

[0082] Optionally, the access network node uses the Physical Downlink Shared Channel (PDSCH) to send the access network specific identifier of the UE, and uses the Physical Downlink Control Channel (PDCCH) or PDSCH to send information such as the UE's NAS ID. The UE can confirm whether the acknowledgment response is sent to itself based on the NAS ID, and save the access network specific identifier of the UE when it is confirmed that the acknowledgment response is for itself.

[0083] Optionally, the UE sends an acknowledgment message to the access network node, which is used to indicate that the UE has received the access network specific identifier of the UE. Correspondingly, the access network node receives the acknowledgment message sent by the UE.

[0084] In addition, after the UE receives the access network specific identifier of the UE sent by the access network node, the following step 305 is also performed:

[0085] Step 305, the UE starts a first timer.

[0086] There are two possible implementation methods for the timing when the UE starts the first timer: First, after the UE receives the access network specific identifier of the UE sent by the access network node and before sending an acknowledgment message to the access network node, the UE starts the first timer; Second, the UE starts the first timer when or after sending an acknowledgment message to the access network node.

[0087] Before the first timer expires, the UE is in the RRC connected state and the access network specific identifier of the UE is valid. In addition, when the UE is in the RRC connected state, after the UE sends uplink data to the access network node, the first timer is restarted; or, after the UE receives downlink data from the access network node, the first timer is restarted. Thus, the RRC connection is maintained in the case of data transmission.

[0088] After the first timer expires, the UE releases the access network specific identifier and switches from the RRC connected state to the RRC idle state.

[0089] Similarly, after the access network node sends the access network specific identifier of the UE to the UE, the following step 306 is also performed:

[0090] Step 306, the access network node starts a second timer.

[0091] There are two possible implementation methods for the access network node to start the second timer: First, the access network node starts the second timer when sending the access network specific identifier of the UE to the UE or after that; Second, the access network node starts the second timer after receiving the confirmation information sent by the UE.

[0092] Before the second timer expires, the access network node considers that the UE is in the RRC connected state and the access network specific identifier of the UE is within the valid period. In addition, when the UE is in the RRC connected state, after the access network node sends downlink data to the UE, it restarts the second timer; or, after the access network node receives uplink data from the UE, it restarts the second timer. Thus, it is ensured to maintain the RRC connection in the case of data transmission.

[0093] After the second timer expires, the access network node releases the access network specific identifier of the UE and considers that the UE switches from the RRC connected state to the RRC idle state. In addition, after the second timer expires, the access network node also sends a notification message to the MME, and the notification message is used to instruct the MME to release the signaling connection between the MME and the access network node and the dedicated data bearer of the UE between the MME and the GW.

[0094] In addition, within the valid period of the access network specific identifier, that is, when the UE is in the RRC connected state, cross-cell movement may occur. Therefore, to ensure the validity of the access network specific identifier of the UE, if the UE moves outside the n cells corresponding to the access network specific identifier of the UE, the UE sends an identifier re-determination request to the access network node. Among them, the access network specific identifier of the UE is unique within the n cells, and n is a positive integer. The identifier re-determination request is used to request the access network node to re-determine the access network specific identifier of the UE. Optionally, the identifier re-determination request is sent together with the uplink data, or the identifier re-determination request is sent in the form of a MAC layer control packet. For example, when there is uplink data to be sent, the UE carries the identifier re-determination request in the data packet of the uplink data; when there is no uplink data to be sent, the UE sends a MAC layer control packet to the access network node, which is used to request the access network node to re-allocate the access network specific identifier of the UE.

[0095] In summary, in the method provided in this embodiment, when the UE is in the RRC idle state, it uses a shared data transmission resource to send an uplink data request to the access network node. In addition to the uplink data, the uplink data request also includes request information for requesting to enter the RRC connected state, so that the access network node establishes an RRC connection with the UE according to the request information; it solves the problem that in the process of the UE switching from the RRC idle state to the RRC connected state in the solution provided by the prior art, the UE requests the base station to resume the RRC connection through RRC messages, and there are many steps of signaling interaction between the UE and the base station to resume data transmission, resulting in low efficiency; while sending uplink data, it requests to enter the RRC connected state, reducing the signaling overhead required to create or resume the RRC connection, and achieving the technical effect of quickly and efficiently creating or resuming the RRC connection.

[0096] In this embodiment, when the UE in the RRC idle state sends uplink data to the access network node, it requests to create a lightweight RRC connection to achieve fast and efficient data transmission and connection establishment.

[0097] In addition, the UE negotiates with the core network node for the first security parameter and uses the first security parameter to protect the security of the uplink data, thereby ensuring the security of the uplink data.

[0098] Please refer to Figure 4 , which shows a flowchart of a method for managing an RRC connection provided in another embodiment of the present invention. This embodiment is exemplified by the method being applied to the Figure 1 shown implementation environment. The method may include the following steps:

[0099] Step 401, when the UE is in the RRC connected state before the RRC idle state, it negotiates with the access network node for the target security parameter to be used when entering the RRC connected state next time.

[0100] Different from the Figure 3 shown embodiment, in this embodiment, the UE and the access network node negotiate security parameters. For example, when the access network node notifies the UE to enter the RRC idle state or before that, the access network node and the UE deduce a set of target security parameters to be used when entering the RRC connected state next time, and the target security parameter has not been used in the previous RRC connected state. Among them, after the UE enters the RRC connected state, the UE resumes using the radio configuration parameters used in the previous RRC connected state.

[0101] In a possible implementation, the UE and the access network node negotiate to determine the target security parameters by themselves. In another possible implementation, the MME notifies the UE and the access network node to negotiate to determine the target security parameters. In an example, the UE and the access network node can deduce the keys for protecting user plane data and the keys for protecting control plane signaling used when entering the RRC connected state next time based on the existing base station keys.

[0102] In this embodiment, after the UE switches from the RRC connected state to the RRC idle state, the access network node saves the context information of the UE.

[0103] Step 402, when the UE is in the RRC idle state, the UE sends an uplink data request to the access network node using the shared data transmission resource.

[0104] The uplink data request includes uplink data and request information for requesting to enter the RRC connected state. In this embodiment, the request information includes: the access network specific identifier used by the UE in the RRC connected state before the RRC idle state and the second indication information for requesting to resume the RRC connection. Different from Figure 3 the embodiment shown, in this embodiment, when the UE sends uplink data to the access network node, it requests to resume the previous RRC connection. Therefore, the UE continues to use the access network specific identifier used in the previous RRC connected state. In addition, the uplink data request can be sent in the form of a MAC packet.

[0105] Correspondingly, the access network node receives the uplink data request sent by the UE.

[0106] Optionally, to ensure the security of the uplink data, the UE uses the target security parameters negotiated with the access network node above to protect the security of the uplink data.

[0107] Optionally, the uplink data request further includes security parameter indication information, which is used to indicate the security parameters adopted by the UE. For example, the security parameter indication information can be an identifier of the target security parameters, including one of the following parameters: key identifier, algorithm identifier. In addition, if the UE does not provide the security parameter indication information to the access network node, the subsequent access network node defaults to select the unused keys deduced before and the data security algorithms used before.

[0108] Optionally, the UE may derive the key in the security parameters adopted in the RRC connection state to which it requests to enter this time based on the key in the previous RRC connected state (such as the base station key in the previous RRC connected state). Correspondingly, the uplink data request further includes a key derivation parameter, which is used to indicate the way for the UE to derive the key. The access network node may further derive the key in the security parameters adopted in the RRC connection state to which the UE requests to enter this time based on the key in the previous RRC connected state and the key derivation parameter.

[0109] Optionally, the UE may perform integrity protection on all or part of the information included in the uplink data request, and the access network node performs integrity verification accordingly. Only after the verification passes, the access network node sends an acknowledgment response to the UE.

[0110] Step 403: The access network node restores the RRC connection with the UE according to the second indication information, and restores and enables the access network specific identifier of the UE.

[0111] In this embodiment, after receiving the uplink data request sent by the UE, the access network node restores the RRC connection with the UE according to the second indication information. Moreover, the access network node restores and enables the context information of the UE and the access network specific identifier of the UE.

[0112] Step 404: The access network node sends the access network specific identifier of the UE to the UE.

[0113] Correspondingly, the UE receives the access network specific identifier sent by the access network node. During the validity period of the access network specific identifier of the UE, the UE is in the RRC connected state.

[0114] In a possible implementation manner, the access network node sends an acknowledgment response to the UE. The acknowledgment response is used to indicate that the access network node has confirmed receiving the uplink data. The acknowledgment response includes the first item or both items of the access network specific identifier of the UE and the security parameter confirmation information. Correspondingly, the UE receives the acknowledgment response sent by the access network node. Among them, the security parameter confirmation information is used to notify the UE of the security parameters confirmed to be used in the current RRC connected state. Usually, the security parameters confirmed to be used are the target security parameters negotiated previously.

[0115] In addition, Figure 3 Similar to the embodiment shown, the UE side and the access network node side may respectively maintain a timer to determine whether to disconnect the RRC connection according to whether the timer times out.

[0116] Optionally, when the access network node determines that the RRC connection needs to be disconnected, the access network node may notify the UE to release the RRC connection through RRC signaling.

[0117] In addition, when the UE does not switch cells, it can directly initiate the above-mentioned uplink data request to the access network node of the current cell, requesting the access network node to resume the RRC connection. When the UE switches cells (for example, the UE moves from the source cell to the target cell), the UE notifies the access network node in the target cell or the MME of the relevant information of the access network node in the source cell, so that the access network node in the target cell can obtain the UE's context information and the GW's address information from the access network node in the source cell. In addition, the access network node or the MME in the target cell, or the access network node or the MME in the source cell, notifies the GW of the relevant information of the access network node in the target cell where the UE is currently located, so that when there is downlink data for the UE to be sent, the GW can accurately locate the target cell where the UE is currently located to ensure the successful downlink of the data.

[0118] In summary, in the method provided in this embodiment, when the UE is in the RRC idle state, it uses the shared data transmission resource to send an uplink data request to the access network node. In addition to the uplink data, the uplink data request also includes request information for requesting to enter the RRC connected state, so that the access network node establishes an RRC connection with the UE according to the request information; it solves the problem that in the process of the UE switching from the RRC idle state to the RRC connected state in the solution provided by the prior art, the UE requests the base station to resume the RRC connection through RRC messages, and there are many steps of signaling interaction between the UE and the base station to resume data transmission, resulting in low efficiency; by requesting to enter the RRC connected state while sending the uplink data, the signaling overhead required for creating or resuming the RRC connection is reduced, achieving the technical effect of quickly and efficiently creating or resuming the RRC connection.

[0119] In this embodiment, the UE in the RRC idle state requests to resume the RRC connection while sending uplink data to the access network node, realizing fast and efficient data transmission and connection recovery.

[0120] In addition, when the UE is in the RRC connected state, it negotiates with the access network node the target security parameters to be used when entering the RRC connected state next time, and the target security parameters have not been used in the previous RRC connected state, so as to ensure that different security parameters are used to protect the data in each RRC connected state, realizing secure connection recovery. Compared with the prior art that still uses the original security parameters to protect the data after resuming the RRC connection, the solution provided in this embodiment has higher security.

[0121] In addition, after the UE enters the RRC idle state, a common data tunnel can be enabled between the base station and the GW. After the base station receives the uplink data sent by the UE, a dedicated data tunnel for the UE is established between the base station and the GW. After the UE enters the RRC idle state, the base station and the MME can choose to release the control plane connection. After the base station receives the uplink data sent by the UE, the base station resumes establishing the control plane connection with the MME.

[0122] In the above Figure 3 and Figure 4 In the embodiments shown, the uplink data transmission process of the UE in the RRC idle state is introduced and described. Next, through Figure 5 the embodiments shown, the downlink data transmission process of the UE in the RRC idle state is introduced and described.

[0123] Step 501, when the UE is in the RRC idle state, the access network node receives a downlink transmission indication sent by the core network node.

[0124] In a possible implementation manner, when there is downlink data for the UE to be sent, the GW sends the downlink data to the MME and notifies the MME to send a downlink transmission indication to the access network node. In another possible implementation manner, when there is downlink data for the UE to be sent, the GW sends a downlink transmission indication to the access network node through the common data tunnel between the GW and the base station.

[0125] The downlink transmission indication at least includes downlink data and the NAS ID of the UE (such as S-TMSI). Among them, the NAS ID of the UE is used to indicate which UE the access network node sends the downlink data to. Optionally, the downlink transmission indication further includes calculation parameters for the access network node to calculate the paging occasion. For example, the calculation parameter may be the modulo value of the International Mobile Subscriber Identification Number (English: International Mobile Subscriber Identification Number; Abbreviation: IMSI) of the UE, such as IMSI mod 1024.

[0126] Step 502, after receiving the downlink transmission indication, the access network node determines the paging occasion.

[0127] The UE in the RRC idle state wakes up every predetermined time interval to listen for information sent by the access network node. Among them, the adjacent two predetermined time intervals are the same or different. The access network node calculates the paging occasion according to the calculation parameters of the paging occasion, and the paging occasion is within the target time period for the UE in the RRC idle state to listen for information sent by the access network node.

[0128] For example, the access network node calculates the paging occasion based on the IMSI mod 1024 and the discontinuous reception (DRX) parameters of the UE in the RRC idle state. Among them, the IMSI mod 1024 can be informed to the access network node by the core network node when sending a downlink transmission indication to the access network node, or it can also be provided to the access network node by the core network node for storage when the UE transitions from the RRE connected state to the RRC idle state.

[0129] Step 503, the access network node sends a paging request to the UE according to the paging occasion.

[0130] Correspondingly, the UE receives the paging request sent by the access network node.

[0131] In a possible implementation manner, the access network node stores the access network specific identifier of the UE. The access network node looks up the access network specific identifier of the corresponding UE according to the NAS ID of the UE, and pages the UE based on the access network specific identifier of the UE. Correspondingly, the UE determines that the paging request is sent to itself according to the access network specific identifier.

[0132] In another possible implementation manner, when the UE transitions from the RRE connected state to the RRC idle state, the access network node notifies the UE of a shared access network identifier. The shared access network identifier refers to an access network identifier shared by multiple UEs in the cell. At this time, the access network node pages the UE based on the shared access network identifier and the NAS ID of the UE. Correspondingly, the UE determines that the paging request is sent to itself according to the shared access network identifier and the NAS ID of the UE.

[0133] Step 504, the UE sends a paging response corresponding to the paging request to the access network node.

[0134] After the UE successfully receives the paging request sent by the access network node, in response to the paging request, it notifies the access network node that the UE is ready to receive downlink data.

[0135] Optionally, if the UE has not released the access network specific identifier, the UE carries the access network specific identifier of the UE in the paging response. If the UE has already released the access network specific identifier, the UE carries the NAS ID of the UE in the paging response and requests the access network node to reallocate an access network specific identifier for the UE.

[0136] Correspondingly, the access network node receives the paging response sent by the UE.

[0137] Step 505, after the access network node receives the paging response sent by the UE, it establishes a dedicated data tunnel for the UE with the core network node.

[0138] After the base station receives the paging response sent by the UE, a dedicated data tunnel for the UE is established between the base station and the GW.

[0139] In addition, in a possible implementation manner, after the access network node receives the paging response sent by the UE, the access network node sends downlink data to the UE. In another possible implementation manner, when the access network node sends a paging request to the UE, downlink data is carried in the paging request, thereby reducing the interaction steps.

[0140] Optionally, if the UE and the base station negotiate security parameters using the solution provided in the above Figure 4 illustrated embodiment, the base station can perform security protection on the downlink data using the target security parameters negotiated with the UE. The base station can indicate the security parameters used when sending the downlink data, such as the key index value, etc.

[0141] In this embodiment, when the UE is in the RRC idle state, the access network node calculates the paging occasion and performs downlink data scheduling, realizing fast paging of the UE in the non-connected state.

[0142] In addition, in the above method embodiments, the steps on the UE side can be separately implemented as a method for managing the RRC connection on the UE side, and the steps on the access network node side can be separately implemented as a method for managing the RRC connection on the access network node side. In the above method embodiments, the access network node is usually a base station.

[0143] The following is an apparatus embodiment of the present invention, which can be used to execute the method embodiments of the present invention. For details not disclosed in the apparatus embodiments of the present invention, please refer to the method embodiments of the present invention.

[0144] Please refer to Figure 6A , which shows a block diagram of an apparatus for managing an RRC connection provided by an embodiment of the present invention. This apparatus can be implemented as a part or all of the UE through a hardware circuit or a combination of software and hardware. This apparatus can include: a sending unit 610 and a receiving unit 620.

[0145] The sending unit 610 is configured to send an uplink data request to the access network node using a shared data sending resource when in the RRC idle state. The uplink data request includes uplink data and request information for requesting to enter the RRC connected state.

[0146] The receiving unit 620 is configured to receive the access network specific identifier of the UE sent by the access network node. The access network specific identifier of the UE is determined by the access network node according to the above request information. During the validity period of the access network specific identifier of the UE, the UE is in the RRC connected state.

[0147] In summary, for the apparatus provided in this embodiment, when the UE is in the RRC idle state, it uses shared data transmission resources to send an uplink data request to the access network node. In addition to the uplink data, the uplink data request also includes request information for requesting to enter the RRC connected state, enabling the access network node to establish an RRC connection with the UE according to the request information; this solves the problem that in the prior art solution during the process of the UE switching from the RRC idle state to the RRC connected state, the UE requests the base station to restore the RRC connection through RRC messages, and there are many steps of signaling interaction between the UE and the base station to restore data transmission, resulting in low efficiency; while sending uplink data, it requests to enter the RRC connected state, reducing the signaling overhead required to create or restore the RRC connection, achieving the technical effect of quickly and efficiently creating or restoring the RRC connection.

[0148] In an alternative embodiment based on Figure 6A the embodiment shown, the request information includes: the NAS ID of the UE and first indication information for requesting to create an RRC connection.

[0149] Optionally, as Figure 6B shown, the apparatus further includes: a data protection unit 630.

[0150] The data protection unit 630 is specifically configured to: negotiate a first security parameter and a second security parameter with the core network node; wherein, the first security parameter is used for security protection of uplink data, and the second security parameter is used for security protection of NAS signaling; use the first security parameter to perform security protection on the uplink data.

[0151] In another alternative embodiment based on Figure 6A the embodiment shown, the request information includes: an access network specific identifier used by the UE in the RRC connected state before the RRC idle state and second indication information for requesting to restore the RRC connection.

[0152] Optionally, as Figure 6B shown, the apparatus further includes: a data protection unit 630.

[0153] The data protection unit 630 is specifically configured to: when in the RRC connected state before the RRC idle state, negotiate a target security parameter to be used when entering the RRC connected state next time with the access network node, and the target security parameter has not been used in the previous RRC connected state; use the target security parameter to perform security protection on the uplink data.

[0154] In an alternative embodiment based on Figure 6AIn another alternative embodiment provided by the illustrated embodiment, the sending unit 610 is further configured to: within the validity period of the access network specific identifier of the UE, if the UE moves outside the n cells corresponding to the access network specific identifier of the UE, send an identifier re-determination request to the access network node. Wherein, the access network specific identifier of the UE is unique within the n cells, and n is a positive integer. The identifier re-determination request is used to request the access network node to re-determine the access network specific identifier of the UE. The identifier re-determination request is sent together with the uplink data, or the identifier re-determination request is sent in the form of a MAC layer control packet.

[0155] In based on Figure 6A In another alternative embodiment provided by the illustrated embodiment, the receiving unit 620 is further configured to: receive an acknowledgment response sent by the access network node. Wherein, the acknowledgment response is used to indicate that the access network node has acknowledged receiving the uplink data, and the acknowledgment response includes the first item or both of the access network specific identifier of the UE and the security parameter acknowledgment information.

[0156] In based on Figure 6A In another alternative embodiment provided by the illustrated embodiment, as Figure 6B shown, the apparatus further includes: a timer unit 640.

[0157] The timer unit 640 is configured to start a first timer after the receiving unit 610 receives the access network specific identifier of the UE sent by the access network node. Wherein, before the first timer times out, the access network specific identifier of the UE is within the validity period.

[0158] Optionally, the timer unit 640 is further configured to: restart the first timer after the sending unit 610 sends uplink data to the access network node; or restart the first timer after the receiving unit 620 receives downlink data from the access network node.

[0159] Please refer to Figure 7A , which shows a block diagram of an apparatus for managing an RRC connection provided by another embodiment of the present invention. The apparatus can be implemented as part or all of an access network node through a hardware circuit or a combination of software and hardware. The apparatus may include: a receiving unit 710, a processing unit 720, and a sending unit 730.

[0160] The receiving unit 710 is configured to receive an uplink data request sent by the UE when it is in the RRC idle state using a shared data transmission resource. Wherein, the uplink data request includes uplink data and request information for requesting to enter the RRC connected state.

[0161] The processing unit 720 is configured to establish an RRC connection with the UE according to the request information and determine the access network specific identifier of the UE.

[0162] A sending unit 730, configured to send an access network specific identifier of a UE to the UE. Wherein, within the validity period of the access network specific identifier of the UE, the UE is in the RRC connected state.

[0163] In summary, the device provided in this embodiment receives, by an access network node, an uplink data request sent by the UE using a shared data transmission resource when the UE is in the RRC idle state. The uplink data request includes, in addition to uplink data, request information for requesting to enter the RRC connected state. The access network node establishes an RRC connection with the UE according to the request information; solves the problem in the solution provided by the prior art that in the process of the UE switching from the RRC idle state to the RRC connected state, the UE requests the base station to restore the RRC connection through an RRC message, and there are many steps of signaling interaction between the UE and the base station to restore data transmission, resulting in low efficiency; requests to enter the RRC connected state while sending uplink data, reducing the signaling overhead required to create or restore the RRC connection, and achieving the technical effect of quickly and efficiently creating or restoring the RRC connection.

[0164] Based on Figure 7A In an optional embodiment provided by the embodiment shown, the request information includes: the NAS ID of the UE and first indication information for requesting to create an RRC connection.

[0165] Correspondingly, the processing unit 720 is specifically configured to: create an RRC connection with the UE according to the first indication information, and allocate an access network specific identifier of the UE corresponding to the NAS ID to the UE.

[0166] Optionally, the uplink data is protected for security using first security parameters negotiated by the UE and a core network node. Wherein, the UE and the core network node negotiate first security parameters and second security parameters. The first security parameters are used to protect the uplink data for security, and the second security parameters are used to protect the NAS signaling for security.

[0167] Based on Figure 7A In another optional embodiment provided by the embodiment shown, the request information includes: the access network specific identifier used by the UE in the RRC connected state before the RRC idle state and second indication information for requesting to restore the RRC connection.

[0168] Correspondingly, the processing unit 720 is specifically configured to: restore the RRC connection with the UE according to the second indication information, and restore and enable the access network specific identifier of the UE.

[0169] Optionally, the uplink data is protected by security using the target security parameters negotiated between the UE and the access network node. The processing unit 720 is further configured to: when the UE is in the RRC connected state before entering the RRC idle state, negotiate with the UE the target security parameters to be used when entering the RRC connected state next time, where the target security parameters have not been used in the previous RRC connected state.

[0170] In another alternative embodiment provided by the embodiment shown in Figure 7A The sending unit 730 is further configured to send an acknowledgment response to the UE. The acknowledgment response is used to indicate that the access network node has received the uplink data, and the acknowledgment response includes the first item or both items of the access network specific identifier of the UE and the security parameter confirmation information.

[0171] In another alternative embodiment provided by the embodiment shown in Figure 7A As shown in Figure 7B The apparatus further includes: a timer unit 740.

[0172] The timer unit 740 is configured to start a second timer after the sending unit 730 sends the access network specific identifier of the UE to the UE. The access network specific identifier of the UE is valid before the second timer expires.

[0173] Optionally, the timer unit 740 is further configured to: restart the second timer after the sending unit 730 sends downlink data to the UE; or restart the second timer after the receiving unit 710 receives uplink data from the UE.

[0174] Optionally, the sending unit 730 is further configured to send a notification message to the MME after the second timer expires. The notification message is used to instruct the MME to release the signaling connection between the MME and the access network node and the dedicated data bearer of the UE between the MME and the GW.

[0175] Please refer to Figure 8 which shows a block diagram of a system for managing RRC connections provided by an embodiment of the present invention. The system includes a UE 810 and an access network node 820.

[0176] The UE 810 includes a device for managing RRC connections provided by the embodiment shown in Figure 6A or any of its alternative embodiments.

[0177] The access network node 820 includes a device for managing RRC connections provided by the embodiment shown in Figure 7A or any of its alternative embodiments.

[0178] It should be noted that when the device provided in the above embodiments realizes its functions, only the division of the above-mentioned functional units is used for illustration. In practical applications, the above functions can be allocated to different functional units according to needs, that is, the internal structure of the device is divided into different functional units to complete all or part of the functions described above. In addition, the device provided in the above embodiments and the method embodiments belong to the same concept. For the specific implementation process, please refer to the method embodiments and will not be elaborated here.

[0179] Please refer to Figure 9 , which shows a block diagram of a UE provided in an embodiment of the present invention. As Figure 9 shown, the UE 900 includes: a bus 910, and a processor 920, a memory 930, and a transceiver 940 that communicate through the bus 910. The memory 930 is used to store one or more instructions, which are configured to be executed by the processor 920. Among them:

[0180] The processor 920 is used to control the transceiver 940 to send an uplink data request to the access network node using shared data transmission resources when in the Radio Resource Control (RRC) idle state. Among them, the uplink data request includes uplink data and request information for requesting to enter the RRC connected state.

[0181] The processor 920 is further used to control the transceiver 940 to receive the access network specific identifier of the UE sent by the access network node. Among them, the access network specific identifier of the UE is determined by the access network node according to the request information, and the UE is in the RRC connected state within the validity period of the access network specific identifier of the UE.

[0182] In summary, the UE provided in this embodiment, when in the RRC idle state, uses shared data transmission resources to send an uplink data request to the access network node. In addition to including uplink data, the uplink data request also includes request information for requesting to enter the RRC connected state, enabling the access network node to establish an RRC connection with the UE according to the request information; solving the problem that in the process of the UE switching from the RRC idle state to the RRC connected state in the solution provided by the prior art, the UE requests the base station to resume the RRC connection through RRC messages, and there are many steps of signaling interaction between the UE and the base station to resume data transmission, with low efficiency; requesting to enter the RRC connected state while sending uplink data, reducing the signaling overhead required to create or resume the RRC connection, and achieving the technical effect of quickly and efficiently creating or resuming the RRC connection.

[0183] In an optional embodiment provided based on the Figure 9 embodiment shown, the request information includes: the NAS ID of the UE and the first indication information for requesting to create an RRC connection.

[0184] Optionally, the processor 920 is further configured to: negotiate a first security parameter and a second security parameter with a core network node; wherein the first security parameter is used to protect the security of uplink data, and the second security parameter is used to protect the security of NAS signaling; and use the first security parameter to protect the security of uplink data.

[0185] In another alternative embodiment provided based on Figure 9 the embodiment shown, the request information includes: an access network specific identifier used by the UE in the RRC connected state before the RRC idle state and a second indication information for requesting to resume the RRC connection.

[0186] Optionally, the processor 920 is further configured to: when in the RRC connected state before the RRC idle state, negotiate a target security parameter to be used when entering the RRC connected state next time with an access network node, where the target security parameter has not been used in the previous RRC connected state; and use the target security parameter to protect the security of uplink data.

[0187] In another alternative embodiment provided based on Figure 9 the embodiment shown, the processor 920 is further configured to, within the validity period of the access network specific identifier of the UE, if the UE moves outside the n cells corresponding to the access network specific identifier of the UE, control the transceiver 940 to send an identifier re-determination request to the access network node. Wherein, the access network specific identifier of the UE is unique within the n cells, and n is a positive integer. The identifier re-determination request is used to request the access network node to re-determine the access network specific identifier of the UE. The identifier re-determination request is sent together with the uplink data, or the identifier re-determination request is sent in the form of a MAC layer control packet.

[0188] In another alternative embodiment provided based on Figure 9 the embodiment shown, the processor 920 is further configured to control the transceiver 940 to receive an acknowledgment response sent by the access network node. Wherein, the acknowledgment response is used to indicate that the access network node has confirmed receiving the uplink data, and the acknowledgment response includes the first item or both items of the access network specific identifier of the UE and the security parameter confirmation information.

[0189] In another alternative embodiment provided based on Figure 9 the embodiment shown, the processor 920 is further configured to start a first timer after receiving the access network specific identifier of the UE sent by the access network node. Wherein, before the first timer times out, the access network specific identifier of the UE is within the validity period.

[0190] Optionally, the processor 920 is further configured to: restart the first timer after sending uplink data to the access network node; or restart the first timer after receiving downlink data from the access network node.

[0191] Please refer toFigure 10 , which shows a block diagram of an access network node provided by an embodiment of the present invention. As Figure 10 shown, the access network node 1000 includes: a bus 1010, and a processor 1020, a memory 1030, and a transceiver 1040 that communicate through the bus 1010. The memory 1030 is used to store one or more instructions, which are configured to be executed by the processor 1020. Among them:

[0192] The processor 1020 is used to control the transceiver 1040 to receive an uplink data request sent by the UE using a shared data transmission resource when the UE is in the RRC idle state. Among them, the uplink data request includes uplink data and request information for requesting to enter the RRC connected state.

[0193] The processor 1020 is further used to establish an RRC connection with the UE according to the request information and determine the access network specific identifier of the UE.

[0194] The processor 1020 is further used to control the transceiver 1040 to send the access network specific identifier of the UE to the UE. Among them, within the validity period of the access network specific identifier of the UE, the UE is in the RRC connected state.

[0195] In summary, the access network node provided by this embodiment, by receiving the uplink data request sent by the UE using a shared data transmission resource when the UE is in the RRC idle state, the uplink data request includes, in addition to the uplink data, request information for requesting to enter the RRC connected state, and then establishing an RRC connection with the UE according to the request information; solves the problem that in the process of the UE switching from the RRC idle state to the RRC connected state in the solution provided by the prior art, the UE requests the base station to restore the RRC connection through RRC messages, and there are many steps of signaling interaction between the UE and the base station to restore data transmission, with low efficiency; requests to enter the RRC connected state while sending uplink data, reducing the signaling overhead required to create or restore the RRC connection, and achieving the technical effect of quickly and efficiently creating or restoring the RRC connection.

[0196] In an optional embodiment provided based on the Figure 10 embodiment shown, the request information includes: the NAS ID of the UE and the first indication information for requesting to create an RRC connection.

[0197] Correspondingly, the processor 1020 is specifically used to: create an RRC connection with the UE according to the first indication information and allocate the access network specific identifier of the UE corresponding to the NAS ID for the UE.

[0198] Optionally, the uplink data is protected for security using the first security parameter negotiated between the UE and the core network node. Among them, the UE and the core network node negotiate the first security parameter and the second security parameter. The first security parameter is used to protect the uplink data for security, and the second security parameter is used to protect the NAS signaling for security.

[0199] In another alternative embodiment provided based on Figure 10 the embodiment shown, the request information includes: the access network specific identifier used by the UE in the RRC connected state before the RRC idle state and the second indication information for requesting to resume the RRC connection.

[0200] Correspondingly, the processor 1020 is specifically configured to: resume the RRC connection with the UE according to the second indication information, and resume enabling the access network specific identifier of the UE.

[0201] Optionally, the uplink data is protected for security using the target security parameter negotiated between the UE and the access network node. The processor 1020 is further configured to, when the UE is in the RRC connected state before the RRC idle state, negotiate with the UE the target security parameter to be used when entering the RRC connected state next time, and the target security parameter has not been used in the previous RRC connected state.

[0202] In another alternative embodiment provided based on Figure 10 the embodiment shown, the processor 1020 is further configured to control the transceiver to send an acknowledgment response to the UE. The acknowledgment response is used to indicate that the access network node has acknowledged receiving the uplink data, and the acknowledgment response includes the first item or both items of the access network specific identifier of the UE and the security parameter acknowledgment information.

[0203] In another alternative embodiment provided based on Figure 10 the embodiment shown, the processor 1020 is further configured to start a second timer after sending the access network specific identifier of the UE to the UE. Among them, before the second timer expires, the access network specific identifier of the UE is within the valid period.

[0204] Optionally, the processor 1020 is further configured to: restart the second timer after sending downlink data to the UE; or restart the second timer after receiving uplink data from the UE.

[0205] Optionally, the processor 1020 is further configured to control the transceiver 1040 to send a notification message to the MME after the second timer expires. The notification message is used to indicate that the MME releases the signaling connection between the MME and the access network node and the dedicated data bearer of the UE between the MME and the GW.

[0206] It should be understood that, as used herein, unless the context clearly supports the exception, the singular forms "a", "an", and "the" are intended to include the plural forms as well. It should also be understood that "and / or" as used herein refers to any and all possible combinations of one or more of the associated listed items.

[0207] The serial numbers of the embodiments of the present invention above are for description only and do not represent the superiority or inferiority of the embodiments.

[0208] Those of ordinary skill in the art can understand that all or part of the steps for implementing the above embodiments can be completed by hardware, or can be completed by instructing relevant hardware through a program. The program can be stored in a computer-readable storage medium, and the above-mentioned storage medium can be a read-only memory, a disk, an optical disc, etc.

[0209] The above are only the preferred embodiments of the present invention and are not intended to limit the present invention. Any modifications, equivalent replacements, improvements, etc. made within the spirit and principle of the present invention shall be included within the protection scope of the present invention.

Claims

1. A communication method, characterized in that, The method includes: When the user equipment UE is in the second RRC state, sending uplink data and request information to a first access network node; wherein, the second RRC state is the RRC power saving state, and the request information is used for establishing or restoring an RRC connection with the first access network node; the security protection of the uplink data is based on target security parameters, the target security parameters have not been used in a first RRC state before the second RRC state and the target security parameters are determined by an access network node having an RRC connection with the UE when the UE is in the first RRC state, the first RRC state is the RRC connected state, and when the UE is in the second RRC state, the UE saves part of the context information of the UE in the first RRC state.

2. The method according to claim 1, wherein The request information includes: The access network specific identifier used by the UE in the first RRC state before the second RRC state and a second indication information for requesting to establish or restore an RRC connection.

3. The method according to claim 1 or 2, characterized in that, The sending of the uplink data and the request information uses a shared data sending resource, and the data sending resource is allocated by a system information block SIB.

4. The method according to claim 1 or 2, characterized in that, It further includes: Receiving a second access network specific identifier of the UE from the first access network node.

5. The method according to claim 1 or 2, characterized in that The request information is also used for determining the access network specific identifier of the UE.

6. The method according to claim 1 or 2, characterized in that, Part of the context information of the UE includes the first access network specific identifier of the UE.

7. The method according to claim 1 or 2, characterized in that, The security protection includes integrity protection.

8. The method according to claim 1 or 2, characterized in that, After the establishment or restoration of the RRC connection, the radio configuration parameters used in the first RRC state are restored.

9. The method according to claim 4, wherein The method further includes: Within the validity period of the second access network specific identifier of the UE, if the UE moves outside n cells corresponding to the second access network specific identifier of the UE, the UE sends an identifier re - determination request to the first access network node; wherein, the second access network specific identifier of the UE is unique within the n cells, n is a positive integer; the identifier re - determination request is used to request the first access network node to re - determine the access network specific identifier of the UE; the identifier re - determination request is sent together with the uplink data, or the identifier re - determination request is sent in the form of a media access control MAC layer control packet.

10. The method according to claim 4, characterized in that, The receiving the second access network specific identifier of the UE from the first access network node includes: Receiving an acknowledgment response from the first access network node; wherein, the acknowledgment response is used to indicate that the first access network node acknowledges that it has received the uplink data, and the acknowledgment response includes the first item or both items of the second access network specific identifier of the UE and security parameter confirmation information.

11. The method according to claim 4, characterized in that, After receiving the second access network specific identifier of the UE from the first access network node, it further includes: Starting a first timer, and within the timeout of the first timer, the second access network specific identifier of the UE is within the validity period.

12. The method according to claim 11, characterized in that, After starting the first timer, it further includes: After sending uplink data to the first access network node, restarting the first timer; Or, After receiving downlink data from the first access network node, restart the first timer.

13. The method according to claim 4, characterized in that, During the validity period of the second access network specific identifier of the UE, the UE is in the RRC connected state.

14. The method according to claim 1, wherein The target security parameter is obtained through negotiation between the UE in the first RRC state and the access network node that has an RRC connection with the UE in the first RRC state.

15. A communication method, characterized in that, Applied to the first access network node, the method includes: Receiving uplink data and request information sent by a user equipment UE when in the second RRC state; wherein, the second RRC state is the RRC power saving state, and when the UE is in the second RRC state, part of the context information of the first RRC state before the second RRC state is saved, the first RRC state is the RRC connected state, and the request information is used for the establishment or restoration of an RRC connection with the first access network node; Establishing an RRC connection with the UE according to the request information; Wherein, the uplink data is protected for security based on a target security parameter that has not been used in the first RRC state and is determined by an access network node that has an RRC connection with the UE when the UE is in the first RRC state.

16. The method according to claim 15, wherein The request information includes: the access network specific identifier used by the UE in the first RRC state before the second RRC state and a second indication information for requesting the establishment or restoration of an RRC connection.

17. The method according to claim 16, wherein Further includes: Determining the second access network specific identifier of the UE according to the request information.

18. The method according to claim 15 or 16, characterized in that, The sending of the uplink data and request information uses a shared data sending resource, and the data sending resource is allocated by a system information block SIB.

19. The method according to claim 15 or 16, characterized in that, Further includes: Sending the second access network specific identifier to the UE.

20. The method according to claim 15 or 16, characterized in that, The request information is also used for the determination of the access network specific identifier of the UE.

21. The method according to claim 15 or 16, characterized in that, Part of the context information of the UE includes the first access network specific identifier of the UE.

22. The method according to claim 15 or 16, characterized in that, The security protection includes integrity protection.

23. The method according to claim 15 or 16, characterized in that, After the establishment or restoration of the RRC connection, restore the radio configuration parameters used in the first RRC state.

24. The method according to claim 19, wherein The sending the second access network specific identifier to the UE includes: Sending an acknowledgment response to the UE; Wherein, the acknowledgment response is used to indicate that the first access network node acknowledges receiving the uplink data, and the acknowledgment response includes the first item or both items of the second access network specific identifier and security parameter confirmation information.

25. The method according to claim 19, wherein After sending the second access network specific identifier to the UE, further includes: Starting a second timer, and before the second timer times out, the second access network specific identifier is within the validity period.

26. The method according to claim 25, wherein After starting the second timer, further includes: After sending downlink data to the UE, restart the second timer; Or, After receiving uplink data from the UE, restart the second timer.

27. The method according to claim 26, wherein After starting the second timer, further includes: After the second timer times out, sending a notification message to a mobility management entity MME; Wherein, the notification information is used to instruct the MME to release the signaling connection between the MME and the first access network node and the dedicated data bearer of the UE between the MME and the gateway GW.

28. The method according to claim 19, wherein During the validity period of the second access network specific identifier, the UE is in the RRC connected state.

29. The method according to claim 15, wherein The target security parameter is obtained through negotiation between the UE in the first RRC state and the access network node having an RRC connection with the UE in the first RRC state.

30. A communication device, characterized in that, A processor, which is coupled to a memory The memory is used to store instructions, and the processor is used to execute the instructions stored in the memory, so that the device executes the method according to any one of claims 1-29.

31. A communication device, characterized in that, It includes a module for implementing the method according to any one of claims 1-29.

32. A computer-readable storage medium stores a computer program, which when running on a computer, causes the method according to any one of claims 1-29 to be executed.

33. A program product includes a computer program, which when running on a computer, causes the method according to any one of claims 1-29 to be executed.

Images