TWI483641B - Method, mobile device, and non-transitory computer readable medium for use with a radio access network - Google Patents

Description

Method, mobile device and non-transitory computer readable medium for use with a radio access network (RAN)

The present invention relates to wireless communication systems and, more particularly, to the handling of connections between nodes in a wireless communication system.

Wireless communication systems that implement wireless data transfer between one or more user equipments (UEs) and one or more base stations (BSs) configured to provide a node of a cellular RAN are known. The prevalence of UEs operating on wireless cellular communication systems requires such networks to carry and support a wide variety of data traffic types and services. The UE can be viewed as a general-purpose computing platform that has wireless connectivity and is capable of executing a wide variety of applications and services that are pre-installed by the device manufacturer or installed/downloaded by the user based on the particular usage requirements of the user. The application itself can be derived from a corresponding group of software companies, manufacturers and third-party developers. Such UE platforms may include mobile devices such as mobile phones, "smart phones", personal digital assistants, handheld or laptop computers, tablets, and similar mobile devices with wireless communication connectivity, or similarly A UE referred to may include fixed devices that are relatively immovable during normal use, such fixed devices having wireless connectivity to enable them to communicate using a wireless communication system. The UE platform may also include other device types including embedded communication connectivity, such as home appliances, utility meters, and security and surveillance devices, or consumer electronics such as still cameras or video cameras, audio/visual entertainment devices, and gaming platforms. .

Wireless communication networks are often used in user plane traffic (which can be seen as carrying application level User data) and control plane traffic (which may be used to implement or support the transmission of user plane data over a wireless communication network, including, for example, mobility control and radio resource control (RRC) functionality) Make a distinction between them. Examples of user plane services and services carried by wireless communication networks include voice, video, internet/web browsing sessions, upload/download file transfers, instant messaging, email, navigation services, RSS feeds and Streaming media. Examples of control plane traffic include core network mobility and attachment control (so-called non-access stratum (NAS) signaling), radio access network control (such as radio resource control (RRC)), and work phase control Send signal.

Outside of the radio and core network communication layers (or "above"), applications can utilize and combine a large number of Internet-based (or other proprietary) agreements to achieve desired results when providing specific services. For example, the navigation application can utilize TCP for file transfer from the server to the device, but can also use a protocol that supports periodic or aperiodic persistence signaling towards the navigation server in the middle. Application level connections are maintained in the presence of network nodes such as stateful firewalls. Similarly, the email application can use a specific synchronization protocol to align the mailbox content on the UE with the mailbox content in the email server, but can also use a periodic or aperiodic server polling mechanism to check for new e-mail. The present invention relates to operating a wireless communication system to provide connectivity to a UE to support such applications.

For a fuller understanding of the present invention, reference should be made to

100‧‧‧Wireless communication system/wireless communication network

101‧‧‧User Equipment (UE)

102‧‧‧Radio Access Network (RAN)

102a‧‧‧Evolved Node B (eNB)

102b‧‧‧Evolved Node B (eNB)

103‧‧‧ Core Network (CN)

103a‧‧‧Servo Gateway (SGW)

103b‧‧‧Action Management Endpoint (MME)

103c‧‧‧Packaging Gateway (PGW)

103d‧‧‧New Mobile Management Endpoint (MME)

104‧‧‧Community Internet

200‧‧‧User Equipment (UE)

201‧‧‧Communication bus

202‧‧‧ processor

204‧‧‧Communication subsystem

206‧‧‧Wireless network

208‧‧‧Power supply

210‧‧‧ Random Access Memory (RAM)

212‧‧‧Mass storage

214‧‧‧Read-only memory (ROM)

216‧‧‧display screen

218‧‧‧i/o controller

301‧‧‧Communication Manager

302‧‧‧ Radio Resource Control (RRC) signaling layer

303‧‧‧ Radio Link Control (RLC) signaling layer

304‧‧‧Media Access Control (MAC) signaling layer

305‧‧‧ Physical layer (PHY)

401‧‧‧ idle mode

402‧‧‧Connection mode

402a‧‧‧Continuous reception

402b‧‧‧Short discontinuous reception (Short DRX)

402c‧‧‧Long discontinuous reception (Long DRX)

403‧‧‧ Radio Resource Control (RRC) Connection Establishment

404‧‧‧ Radio Resource Control (RRC) Connection Release

S1C‧‧‧ control plane bearer connection

SIU‧‧‧User plane bearer connection

1 shows a wireless communication system including an LTE radio access network coupled to an evolved packet core network, further coupled to an external packet data network, such as a public internet network.

2 shows a block diagram of selected components of an example UE for use in a wireless communication system in accordance with the present invention.

3 shows an illustration of a control manager in the RAM of the UE shown in FIG. 2 in accordance with the present invention for facilitating communication with a wireless communication system.

FIG. 4 illustrates an RRC connection state, a DRX substate, and a transition therebetween in LTE.

5 is a message sequence diagram illustrating a normal RRC connection procedure in a wireless communication system that does not provide RRC connection suspension functionality.

6 is a simplified flow diagram illustrating an RRC connection procedure in a wireless communication system that does not provide RRC connection abort functionality.

7 is a flow chart illustrating a simplified RRC connection restart procedure in a wireless communication system providing RRC connection abort functionality in accordance with the present invention.

Figure 8 is a message sequence diagram illustrating an exemplary RRC Connection Abort procedure in a wireless communication system in accordance with the present invention.

9 is an illustration of an illustrative mobility scenario for handling a signal variant by an action handler during an RRC connection suspension in accordance with the present invention.

FIG. 10 is a message sequence diagram illustrating an example of a signaling variant 1 in the mobile processing alternative B in a wireless communication system in which the UE has an RRC connection suspended.

11 is a message sequence chart illustrating an example of a signalling variant 2 in the mobile processing alternative B in a wireless communication system in which the UE has an RRC connection suspended.

FIG. 12 is a message sequence diagram illustrating an example of a signaling variant 3 in the mobile processing alternative B in a wireless communication system in which the UE has an RRC connection suspended.

Figure 13 is an illustration similar to another example of Figure 9, in which the UE moves back into the cell of the RAN that suspended the RRC connection and moves again outside of the cell.

14, 15 and 16 are message sequence diagrams illustrating example methods for handling downlink (DL) data in a network in different situations when the RRC connection between the UE and the RAN is aborted.

17, 18 and 19 show message sequence diagrams illustrating an example RRC restart method, The method is for handling a reply for user plane data transfer for a UE having a RRC connection with the RAN.

20 shows a message sequence chart illustrating a method of handling an RRC Connection Abort in Example Scenario 1.

21 shows a message sequence chart illustrating a method of handling an RRC Connection Abort in Example Scenario 2.

22 shows a message sequence chart illustrating a method of handling an RRC Connection Abort in Example Scenario 3.

23 shows a message sequence diagram illustrating a method of handling an RRC Connection Abort in Example Scenario 4.

24 shows a message sequence chart illustrating a method of handling an RRC Connection Abort in Example Scenario 5.

25 shows a message sequence chart illustrating a method of handling an RRC Connection Abort in Example Scenario 6.

26 shows a message sequence chart illustrating a method of handling an RRC Connection Abort in Example Scenario 7.

Figure 27 shows a message sequence diagram illustrating an example of a representative scenario for an active procedure.

28 shows a message sequence diagram illustrating a method of handling an RRC Connection Abort in Example Scenario 10.

29 shows a message sequence chart illustrating a method of handling an RRC Connection Abort in Example Scenario 11.

30 shows a message sequence diagram illustrating a method of handling an RRC Connection Abort in Example Scenario 13.

31 shows a message sequence diagram illustrating a method of handling RRC Connection Abort in Example Scenario 14.

32 shows a message sequence diagram illustrating a method of handling an RRC Connection Abort in Example Scenario 15.

33 shows a message sequence diagram illustrating a method of handling an RRC Connection Abort in an Example Scenario 16.

Many UE applications require or benefit from so-called always-on connectivity, which delivers a seamless and continuous connectivity experience to the user when using the UE and the applications executing thereon. Although the emergence of seamlessness is presented to the user at the service level, this can actually be achieved without permanent or continuous connectivity at all of the contract levels below the application layer. The fact is that the condition may be based on regularity or establishing and releasing connections as needed to deliver user data when needed but to allow for some power efficiency or system efficiency savings in the UE during the interference period. However, the frequent establishment and release of such connections may also require significant use of system resources or additional signal loading within the network, and the associated system resources and control burden may vary. For an application traffic, this can offset the power or system efficiency benefits of using this "on-demand" connection to establish a policy. There is therefore a need for systems and methods that are capable of reducing such system resources and control burdens such that overall system and power efficiency are improved when attempting to deliver a seamless user or service experience at the application level via a communication network.

Excessive prevalence of application types, services, and service delivery components in wireless communication systems results in excessive correspondence of data traffic distribution and statistics presented to the wireless communication network for delivery. Wireless communication networks are therefore less able to predict traffic profiles and distributions, and must be designed to adapt connections and assigned transmission resources to accommodate dynamically changing (possibly "clustering") traffic loads.

To do so, the wireless radio access network may include dynamic scheduling such that the number of assigned shared radio resources can be changed quickly in response to data needs (e.g., data buffer status). This dynamic schedule typically operates on a scale of 1 millisecond to a few milliseconds. At the time scale above (operating in the 100ms to a few seconds), the wireless communication network is also State machine oriented procedures are often used to adapt the radio connection status or sub-state to the degree of observed traffic activity. The radio connection state or sub-state can vary in a number of ways, including the degree of connectivity provided, the amount of system resources reserved or used for the connection, and the amount of UE battery power consumed.

The connectivity hierarchy can be characterized as a combination of various connectivity properties such as:

‧ Location granularity: The accuracy with which the wireless communication network tracks the current location of the UE (eg, for a more active UE to cell level, or for a less active UE to a cell only group)

‧ Mobility Control: The decision to change the cell with which the UE is associated may be made by the network (network control mobility) or by the UE (UE controlling mobility). In the case of network control mobility, the UE may be instructed to perform measurements and report measurement results to the network to assist the network in making decisions to perform the handover. Once a handover decision is made, the network will typically prepare any necessary resources in the target cell before instructing the UE to change the cell by sending a handover command. In the case where the UE controls mobility, the UE will perform measurements on neighboring cells and use such measurements in making a decision to perform cell reselection. The network can control the decision making process by transmitting various cell reselection parameters (e.g., threshold, offset, etc.) in the broadcast system information. Network control mobility (delivery) requires more air signaling, intra-network signaling, and network processing resources than UE control mobility.

‧ Assigned Resources: The presence, absence, type, or amount of radio transmission resources available to the UE for performing communications, as a function of the expected activity level.

‧Tx/Rx Ready: The power consumed by the UE is often a function of the "ready" of its transmission or reception. For example, if the data can arrive at any given time, the UE must permanently activate its receiver to receive downlink communications from the base station, resulting in high power consumption and battery grabbing. In order to save power, discontinuous reception (DRX) is often used, allowing the UE to "sleep" at certain times and turn off its receiver. The base station (BS) must consider the DRX pattern of the UE when it is determined that it will be able to successfully deliver the data to the UE. The DRX-type active cycle often varies with the assigned radio connection state or sub-state.

‧ Established interface or bearer: Inter-terminal communication (eg, from the UE towards an external network such as the Internet to a core network gateway or egress node) may require user-specific establishment between all participating network nodes or entities Connected (or carried). The establishment of some of these interfaces may be associated with a radio connection state or sub-state that varies with the current active level.

Methods, apparatus, and software are disclosed herein for use in a wireless communication system to suspend and handle a restart of a Radio Resource Control (RRC) connection for carrying user plane and control plane data between a UE and a RAN. Also disclosed herein are methods, apparatus, and software for handling mobility control and downlink data for a UE (for which the RRC connection is aborted).

In the context of the present invention, the term "suspending, suspend or suspension" in relation to an RRC connection means storing a message relating to one or more of the RRC connection (or storing RRC connection data) and: Suppressing transmission of user plane data between the mobile device and the RAN node but the mobile device is still capable of receiving paging from the RAN node and/or receiving notification of downlink data from the RAN node; ‧ RAN node indicating mobile device execution and idle mode functions Same or similar functionality (eg, paging and mobility procedures that may be different from paging and mobility procedures used in normal or non-suspended RRC connection mode); and ‧ release associated with RRC connection between RAN node and mobile device The air bearer or radio link or radio resource is coupled to the mobile device but the mobile device is still capable of receiving a paging from the RAN node and/or receiving a notification of downlink data from the RAN node.

The RRC connection data or information (which may alternatively be referred to as RRC message material) may include parameters or other information related to the RRC connection or more general parameters related to the RRC layer or other layers. For example, it may include parameters related to the current configuration of the radio bearer, radio resources, temporary cell identifiers, security parameters or keys, MAC configuration, physical layer configuration, and measurement and reporting configuration. It may also include material related to the RRC layer or other layers such as the physical layer, the MAC layer, the RLC layer, and the PDCP layer. The security parameters or keys may, for example, include K _asme , K _enb , K _RRCenc , K _RRCint , K _RRCUPenc , integrity algorithms, encryption algorithms, and radio bearer COUNT values.

According to a first aspect, there is provided a method implemented in a mobile device for use with a Radio Access Network (RAN), comprising: an indication that the mobile device is to be connected to a Radio Resource Control (RRC) of the RAN The token is sent to the RAN; wherein the indicator indicates a preference for the mobile device to suspend or release the RRC connection.

According to a second aspect, a mobile device for use with a Radio Access Network (RAN) is provided, the mobile device being configured to: send an indicator to a Radio Resource Control (RRC) connection to the RAN to RAN; wherein the indicator indicates a preference for the mobile device to suspend or release the RRC connection.

Typically, the indicator is a preference to suspend or release the RRC connection.

The indicator may be included in the request message sent by the mobile device to the RAN node in the RAN. Alternatively or additionally, the indicator may be included in a capability message sent by the mobile device to the RAN node in the RAN.

Preferably, the mobile device receives the command message from the RAN; and the mobile device performs at least one of: releasing the RRC connection in response to the command message; and suspending the RRC connection.

The command message can be received in response to the transmission of the indicator.

Preferably, the RRC connection suspension includes the mobile device storing the RRC connection data for the RRC connection. The stored RRC connection data can be used by the mobile device to re-establish the suspended RRC connection.

The stored RRC connection data may include data indicating one or more of the following: ‧ configuration of the radio bearer in the RRC connection; ‧ security parameters related to the RRC connection and/or the RRC layer, which are generally and not necessarily for abort The RRC connection is specific; ‧ temporary cell identifier; ‧ MAC configuration; ‧ physical layer configuration; and ‧ measurement and report configuration

In an example, the indicator can be sent in response to complying with the RRC Connection Abort criteria at the mobile device.

Generally, the RRC connection suspension criterion includes at least one of: expiration of a timer at the mobile device; no user plane data is received from the RAN or no user plane data is transmitted to the RAN in a period of time; The user plane data is not expected to be received from the RAN or the user plane data is sent to the RAN; the state of the input or output function of the mobile device; the state of one or more applications of the mobile device; and at the mobile device Higher layer indication of the RRC layer.

The higher layer indication can come from the application layer or from the non-access layer (NAS) layer.

Preferably, the mobile device initiates the re-establishment of the RRC connection in response to the following: the mobile device generates uplink data via the user plane of the RRC connection; or receives the paging at the mobile device; or at the mobile device A notification is received from the RAN or core network (CN) buffering downlink data for transmission to the mobile device.

The mobile device can be configured to communicate with the RAN in accordance with an LTE or LTE advanced protocol.

The RAN can be configured to communicate with mobile devices in accordance with LTE or LTE advanced protocols.

One or more RAN nodes may be (several) eNode Bs.

According to a third aspect, there is provided a method implemented in a node for a Radio Access Network (RAN) for use with a mobile device, the method comprising: receiving at a RAN node from a mobile device for re-establishment by another a RAN node suspended radio resource control (RRC) connection request; the RAN node attempts to retrieve RRC connection data related to the suspended RRC connection; and the RAN node performs one of the following: if the RRC connection is valid, the connection is re-established The setup command message is sent to the mobile device; and if the RRC connection is invalid, the connection re-establishment rejection message is sent to the mobile device.

According to a fourth aspect, there is provided a node for a Radio Access Network (RAN) for use with a mobile device, the RAN node configured to: receive radio resource control for reestablishing suspension by another RAN node (RRC) connection request; attempting to retrieve RRC connection data related to the suspended RRC connection; if the RRC connection is valid, transmitting a connection re-establishment command message to the mobile device; and if the RRC connection is invalid, the connection re-establishment rejection The message is sent to the mobile device.

In some examples, the connection re-establishment command message can be one of an RRC connection re-establishment command message or an RRC connection reconfiguration message. Other new or existing 3GPP messages are also possible. Similarly, the connection re-establishment reject message can re-establish a reject message for the RRC connection. Other new or existing 3GPP messages are also possible.

Generally, the RAN node determines whether the suspended RRC connection is valid by referring to the RRC connection data.

The RAN node may determine, by at least one of the following, whether the suspended RRC connection is valid: ‧ the determination timer has not expired; and ‧ whether the RRC connection data is retrieved.

In one example, the RRC connection data is retrieved from another network component. Another network component is a RAN network component (such as a RAN node), or a core network (CN) network component (such as a Mobility Management Entity (MME)). However, other CN network components, such as a servo gateway (S-GW), may be used.

In another example, the RRC connection profile may be stored by another RAN node in a memory device in the RAN node and the RAN node retrieves the RRC connection profile from the memory device.

The RAN node may retrieve the stored RRC connection data and re-establish the suspended RRC connection in response to the mobile device responding to the paging request or the notification of the downlink data.

The RAN node may retrieve the stored RRC connection profile and re-establish the suspended RRC connection in response to the re-establishment request message from the mobile device receiving the RRC connection for reestablishing the suspension.

One or more RAN nodes may be configured to communicate with the mobile device in accordance with an LTE or LTE advanced protocol.

The one or more RAN nodes may be (several) eNode Bs.

According to a fifth aspect, there is provided a method implemented in a node for a Radio Access Network (RAN) for use with a mobile device, the method comprising: radio resource control by a RAN node relating to an RRC connection of a mobile device The (RRC) connection data is transmitted to at least one other network component; and the RAN node suspends the RRC connection with the mobile device.

According to a sixth aspect, there is provided a node for a Radio Access Network (RAN) for use with a mobile device, the RAN node configured to: Radio Resource Control (RRC) related to an RRC connection of a mobile device Connection data Transfer to at least one other network component; and suspend the RRC connection with the mobile device.

At least one other network component can be a RAN network component (such as a RAN node), or a CN network component (such as an MME). However, other network components may be possible for another CN network component, such as an S-GW.

The RRC connection data can also be stored at the RAN node.

Preferably, the RRC connection data transmitted to other network components can be used by the RAN node or another RAN node to re-establish the suspended RRC connection.

The RRC connection profile may contain data indicating one or more of the following: ‧ configuration of the radio bearer in the RRC connection; ‧ security parameters related to the RRC connection or not specific to the RRC connection; ‧ temporary cell identifier; MAC configuration; ‧ physical layer configuration; and ‧ measurement and report configuration

The RRC connection profile may be flagged to indicate that the RRC connection is aborted.

Preferably, in response to the suspension criteria, the RAN node transmits the RRC connection data to other network components and suspends the RRC connection.

The suspension criterion includes at least one of: ‧ expiration of the timer at the RAN node; ‧ a message indicating the release of the established RRC connection is transmitted by the RAN node to the mobile device; ‧ receiving the suspension from the mobile device at the RAN node Request message; ‧ has not received user plane data from the mobile device or no user plane data sent to the mobile device during a period of time; ‧ has not expected to receive user plane data from the mobile device during a period of time or will cause User plane data is sent to the mobile device; and ‧ high level indication to the RRC layer

The higher layer indication can come from the application layer or the non-access layer (NAS) layer.

Typically, the RRC connection data contains the identification of the mobile device.

The RRC connection profile may include the identification of the cell of the servo mobile device when the RRC connection is aborted.

Typically, the RAN node may send a message to inform any other RAN node or core network (CN) node that the RRC connection has been aborted and the RRC connection data is stored in other network components.

Preferably, the RRC connection data is transmitted to other network components for storage at other network components.

The RAN can be configured to communicate with mobile devices in accordance with LTE or LTE advanced protocols.

One or more RAN nodes may be (several) eNode Bs.

According to a seventh aspect, a method in a network component is provided, the method comprising: receiving radio resource control (RRC) connection data, RRC connection data, and a first RAN node from a first radio access network (RAN) node In connection with the RRC connection between the mobile devices, the RRC connection is or will be suspended by the first RAN node; and the RRC connection data is stored.

According to an eighth aspect, a network component is provided configured to: receive radio resource control (RRC) connection data from a first radio access network (RAN) node, RRC connection data and a first RAN node and action The RRC connection between the devices is related to, the RRC connection is or will be suspended by the first RAN node; and the RRC connection data is stored.

Preferably, the network component can be a RAN network component or a CN network component. For example, where the network component is a RAN network component, it can be a RAN node, and where the network component is a CN network component, it can be an MME. However, the CN network component can be S-GW possible.

The first RAN node may be in the validity area of the MME, where the other network components are MMEs.

Typically, the stored RRC connection data may be retrieved by the RAN node to re-establish an RRC connection with the mobile device.

The RRC connection profile may be retrieved by the first RAN node, the second RAN node, or another RAN node (or the third RAN node) to reestablish an RRC connection with the mobile device abort.

Preferably, the RRC connection profile contains data indicating at least one of: ‧ configuration of the radio bearer in the RRC connection; ‧ security parameters related to the RRC connection or not specific to the RRC connection; ‧ temporary cell identifier ; ‧ MAC configuration; ‧ physical layer configuration; and ‧ measurement and report configuration

Typically, the RRC connection data contains the identification of the mobile device.

The RRC connection profile may include the identification of the cell of the servo mobile device when the RRC connection is aborted.

According to a ninth aspect, there is provided a method implemented in a node for a Radio Access Network (RAN) for use with a mobile device, the method comprising: the RAN node transmitting a connection abort command message to a mobile device to suspend RRC connection of mobile devices.

According to a tenth aspect, a radio access network (RAN) node for use with a mobile device is provided, the RAN node configured to: send a connection abort command message to the UE to suspend an RRC connection with the UE.

In an example, the connection abort command message may be sent in response to meeting the suspension criteria at the RAN node.

The suspension criteria can be at least one of the following: ‧ expiration of the timer at the RAN node; ‧ receiving the abort request message from the mobile device at the RAN node; ‧ having not received user plane data from the mobile device or no user plane data sent to the mobile device during a period of time ‧ has not expected to receive user plane data from the mobile device or to send user plane data to the mobile device during a period of time; and ‧ a higher level indication to the RRC layer. The higher layer can be an application layer or a non-access layer (NAS) layer.

In response to the connection abort command message, the RAN node can receive an acknowledgement message from the mobile device. The response message may include a response from at least one of an RRC layer or a Medium Access Control (MAC) layer of the mobile device.

When the RRC connection is aborted, the RAN node can release the mobility control of the mobile device to the mobile device.

The RAN node may also store RRC connection data for the RRC connection.

The RAN node can be an eNodeB.

According to an eleventh aspect, there is provided a method implemented in a mobile device for use with a Radio Access Network (RAN), the method comprising: the mobile device receiving, from the RAN, an indication that the mobile device suspends an RRC connection with the RAN The abort command message is connected; and in response to the connection abort command message, the mobile device suspends the RRC connection.

According to a twelfth aspect, a mobile device for use with a Radio Access Network (RAN) is provided, the mobile device being configured to: receive, from the RAN, a connection abort command indicating that the mobile device suspends an RRC connection with the RAN The message; and the RRC connection is aborted in response to the connection abort command message.

The mobile device can send a connection abort request message requesting the suspension of the RRC connection to RAN; and receives a connection abort command message from the RAN in response to the connection abort request message.

The connection abort request message may be sent in response to meeting the suspension criteria at the mobile device.

The suspension criterion may be at least one of: ‧ expiration of the timer at the mobile device; ‧ no user plane data received from the RAN or no user plane data sent to the RAN during a period of time; It is not expected to receive user plane data from the RAN or send user plane data to the RAN during the time period; ‧ state of the input function of the mobile device; ‧ state of the output function of the mobile device; ‧ one or more applications of the mobile device State; and ‧ a higher level indication of the RRC layer at the mobile device.

The higher layer can be the application layer or the non-access layer (NAS) layer of the mobile device.

In response to the connection abort command message, the mobile device can send an acknowledgement message to the RAN node.

The response message may include a response from at least one of an RRC layer or a Medium Access Control (MAC) layer of the mobile device.

When the RRC connection is aborted, the mobile device can control mobility.

The mobile device can be configured to communicate with the RAN in accordance with an LTE or LTE advanced protocol.

According to a thirteenth aspect, there is provided a method implemented in a node for a radio access network (RAN) for use with a mobile device, the method comprising: the RAN node receiving a reestablishment aborted RRC connection from a mobile device a connection re-establishment request message; in response to the connection re-establishment request message, the RAN node sends a connection re-establishment command message to the mobile device; and In response to the connection re-establishment command message, the RAN node receives a connection re-establishment complete message from the mobile device.

According to a fourteenth aspect, a radio access network (RAN) node for use with a mobile device is provided, the RAN node configured to: receive a re-establishment request message for re-establishing an aborted RRC connection from a UE Sending a connection re-establishment command message to the UE in response to the connection re-establishment request message; and receiving a connection re-establishment completion message from the UE in response to the connection re-establishment command message.

The connection re-establishment command message may be one of an RRC connection re-establishment command message and an RRC connection reconfiguration message.

The connection re-establishment completion message may be one of an RRC connection re-establishment completion message and an RRC connection reconfiguration complete message.

The RAN node can be an eNodeB.

According to a fifteenth aspect, there is provided a method implemented in a mobile device for use with a Radio Access Network (RAN), the method comprising: the mobile device re-establishing a suspended RRC connected connection re-establishment request message Transmitting to the RAN; in response to the connection re-establishment request message, the mobile device receives the connection re-establishment command message from the RAN; and in response to the connection re-establishment command message, the mobile device re-establishes the RRC connection with the RAN and sends a connection re-establishment completion message to RAN.

According to a sixteenth aspect, a mobile device for use with a Radio Access Network (RAN) is provided, the mobile device being configured to: send a connection re-establishment request message requesting re-establishment of an RRC connection to the suspension RAN; In response to the re-establishment request message, the connection re-establishment command message is received from the RAN; and in response to the connection re-establishment command message, the RRC connection with the RAN is re-established and the re-establishment completion message is sent to the RAN.

The connection re-establishment request message may be sent in response to compliance with the re-establishment criteria at the mobile device.

The re-establishment criteria may include at least one of: ‧ the mobile device generates uplink data via the RRC connected user plane; ‧ receives the paging at the mobile device; ‧ receives the RAN or core network (CN) at the mobile device The downlink data is buffered for notification to the mobile device; and the mobile device reselects to another cell.

The connection re-establishment command message may be one of an RRC connection re-establishment command message and an RRC connection reconfiguration message.

The connection re-establishment completion message may be one of an RRC connection re-establishment completion message and an RRC connection reconfiguration complete message.

The mobile device can be configured to communicate with the RAN in accordance with an LTE or LTE advanced protocol.

Preferably, one or more of the above aspects may be combined as needed. In addition, any aspect of the features may be combined with another aspect as appropriate.

Long Term Evolution (LTE) is the Third Generation Partnership Project (3GPP) standard for wireless communication network technologies. An illustrative example of a wireless communication system 100 that supports communication in accordance with LTE is shown in FIG.

The following detailed description is set forth in the context of a wireless communication system supporting LTE, but it should be understood that the applicability of the present invention is by no means limited to LTE. In fact, the broad concepts of UE-RAN RRC connection suspension and its handling disclosed herein are equally applicable to other wireless communication systems that support other technologies and protocols, whether currently known or not contemplated. In this regard, The present invention should in no way be limited to the following illustrative embodiments, drawings, and techniques, and may be modified and used in other wireless communication systems without departing from the scope of the appended claims. .

LTE describes a number of requirements for a wireless communication system in an evolved or advanced cellular broadband technology. These requirements include the provision of the Evolved Universal Mobile Telecommunications System (UMTS) Terrestrial Radio Access Network (E-UTRAN), also known as the RAN 102. As shown in FIG. 1, RAN 102 provides high speed radio access technology to support wireless communication between UE 101 and one or more BSs acting as nodes of RAN 102 to comply with increased network requirements, including improved user access. Volume and network capacity, reduce latency, and increase mobility. The LTE RAN 102 shown in FIG. 1 includes a node type that acts as a Node Base Station (BS), that is, an evolved Node B (eNB) 102a, b, ... n advanced LTE device that supports E-UTRAN null interfacing, At least some of the functionality of BSs, wireless access points, and other systems and devices may be provided, and some of the BSs, wireless access points, and other systems and devices may evolve more than equivalent devices in conventional wireless telecommunications systems. The term eNB or access device can be used herein to refer to any existing or advanced device that can be used to gain access to the network. This advanced or next generation device may be referred to herein as a Long Term Evolution (LTE) device.

The eNB may support communication with the UE via one or more cells. The communication between the eNB and the UE may include communication of a single cell via the eNB or may include simultaneous or non-simultaneous communication via more than one cell.

In some implementations, the functionality of an eNB may be self-contained within an entity node or entity, while in other implementations, the functionality may be distributed between more than one entity node or entity having an interconnection therebetween.

As can be seen in Figure 1, the LTE wireless communication network 100 provides a Uu radio interface between the UE 101 and the eNB 102a of the RAN 102 to facilitate radio communication therebetween.

LTE uses an evolved packet core (EPC) network architecture for core network (CN) 103 to support RAN 102 (E-UTRAN in the case of LTE). Therefore, as shown in Figure 1 The eNB RAN nodes 102a, b...n form a connection with one or more of the EPC CN 103 (described below). The EPC network architecture conveys protocols such as Transmission Control Protocol (TCP)/Internet Protocol (IP) for supporting IP-based services such as voice, video, other media, and messaging with inter-terminal quality of service (QoS). The EPC network architecture also enables improved connectivity and delivery to other fixed lines and improved mobility wireless access technologies.

The LTE Radio Access Network 102 (E-UTRAN) coupled to the EPC CN 103 can be further coupled to an external packet data network, such as the public internet network 104.

The EPC CN 103 shown in Figure 1 comprises three node types: a Servo Gateway (SGW) 103a that delivers user plane data within the core network, handling mobility and connection control between the UE and the core network. An active management endpoint (MME) 103b, and a packet gateway (PGW) 103c entry/exit node that delivers data between the core network and the external network. During the communication phase between the UE 101, the eNB 102a and the CN 103, an "S1" network interface is formed between the RAN 102 and the CN 103, including a control plane bearer connection "S1-MME" between the eNB 102a and the MME 103b. (Supple referred to as "S1c") "S1-MME", and the user plane bearer connection "S1u" between the eNB 102a and the SGW 103a. The "S5/S8" interface between SGW 103a and PGW 103c provides user plane communication therebetween. The MME 103b may be connected to the SGW 103a, for example, via an "S11" interface.

2 shows a block diagram illustrating some of the example components that may be used in the example UE 200 in the LTE capable wireless communication system shown in FIG. The UE 200 can be a wireless device and its associated Universal Integrated Circuit Card (UICC), which includes a User Identity Module (SIM) application, a Universal User Identity Module (USIM) application, or a removable user identity module. The group (R-UIM) application, or UE 200 can be the device itself without this card.

The UE 200 includes a plurality of components linked by a communication bus 201. The processor 202 controls the overall operation of the UE 200. Communication functions including data and voice communication are performed via communication subsystem 204. The communication subsystem 204 can take the form of a data machine, a data unit, an Ethernet device, a universal serial bus (USB) interface device, a serial interface, and a token ring , Fiber Distributed Data Interface (FDDI) devices, Wireless Local Area Network (WLAN) devices, Radio Transceiver Devices such as Code Division Multiple Access (CDMA) Devices, Global System for Mobile Communications (GSM) Radio Transceiver Devices, Microwave Access Global Interoperability (WiMAX) devices, and/or other known devices used to connect to the network. Communication subsystem 204 can enable processor 202 to communicate with the Internet or one or more telecommunications networks or other networks from which processor 202 can receive information or processor 202 can output information to such networks. road. In the context of FIG. 1, communication subsystem 204 receives messages from wireless network 206 and sends messages to wireless network 206, which may be shown in FIG. 1 for voice communication or data communication or both. RAN 102. A power source 208, such as one or more rechargeable batteries or to an external power supply, powers the UE 200.

The processor 202 interacts with other components of the electronic device, including random access memory (RAM) 210, mass storage 212 (including but not limited to disk and optical disk, magnetic tape, solid state drive, or RAID array). The read-only memory (ROM) 214 and the display screen 216 can be, for example, a liquid crystal display (LCD). The i/o controller 218 sends and receives signals regarding one or more user control devices, such as touch sensitive overlays on the display screen 216, to enable the user to interact with the UE 200.

Processor 202 executes instructions, code, software or computer programs that are accessible from communication subsystem 204, RAM 210, mass storage 212, or ROM 214. Processor 202 can include one or more data processing units or CPU chips. Processor 202 may execute instructions solely by itself, or in cooperation with other data processing components provided at a regional or remote location, or other components not shown in FIG. In particular, processor 202 can execute instructions such that UE 200 is operative to perform wireless communication in an LTE network in accordance with the invention set forth below.

For example, referring to FIG. 3, processor 202 can execute instructions that entity communication manager 301 and maintain it in RAM 210, which in operation operates communication subsystem 204 to perform signaling to communicate with RAN 102. interactive.

Communication manager 301 can, for example, materialize the LTE protocol stack in RAM 110 of UE 201 The stacking provides one or more of the following in an access layer layer of LTE: Radio Resource Control (RRC) signaling layer 302, which is typically responsible for the control of radio related functions, radio link control (RLC, which is generally responsible for the transmission of lost data) The signaling layer 303, the Media Access Control (MAC) signaling layer 304, which is typically responsible for controlling access to the physical layer (PHY) 305. Of course, the protocol stack layer can be implemented elsewhere, for example, MAC and PHY signaling can be provided in the UE by firmware or hardware and thus not maintained in RAM 110. In fact, the implementation of the protocol stack in the UE shown in Figure 3 is only one of many possible examples within the scope of the present invention and is provided for illustrative purposes only.

The LTE Physical Layer (PHY) uses advanced techniques including Orthogonal Frequency Division Multiple Access (OFDMA), Multiple Input and Multiple Output (MIMO) data transmission, and smart antennas to meet the above network requirements. The LTE PHY uses OFDMA for, for example, downlink transmission from BS to UE, and downlink transmission can be communicated by transmitting signals throughout a geographic area called a cell. In addition, within a carrier, the LTE PHY uses Single Carrier Frequency Division Multiple Access (SC-FDMA) for uplink transmissions, for example, from the UE to the BS. The OFDMA and SC-FDMA techniques promote an increase in system capacity and throughput as communication is performed via the associated spectrum or bandwidth.

As mentioned above, the LTE system includes protocols, such as Radio Resource Control (RRC) protocols, which are responsible for the connection between the UE 101 and the eNBs 102a, b, . . . n of the RAN 102 or other access or LTE devices and radio resources. Assign, configure, and release. The RRC protocol is described in detail in the 3GPP TS 36.331 specification. According to the RRC protocol, two basic RRC connection modes for UEs in LTE are defined as "idle mode" and "connection mode".

During the connection mode or state, the UE 101 can exchange signals with the network and perform other related operations, including the ability to perform user plane communication with the network, while during idle mode or state, the UE 101 can turn off its capabilities and operations. At least some of them are no longer able to perform user plane communication with the network. Idle and connected mode behavior is described in detail in the Third Generation Partnership Project (3GPP) specification TS 36.304 and TS 36.331.

Figure 4 illustrates an RRC state transition for LTE. The transition between the idle mode 401 and the connected mode 402 in LTE is implemented via an explicit RRC connection setup 403 (or setup) and release 404 procedure and involves an associated signaling burden. During the normal idle mode procedure, if a need for user plane communication occurs, an RRC connection is established via the currently camped cell. A sequence of messages exchanged during normal RRC connection setup to transition between idle mode and connected mode in LTE is shown in FIG. If the connection originates from the UE, the RRC Connection Request message is sent by the UE 101 (starting with the PRACH Random Access Channel). Conversely, if the connection originates from the network, the MME 103a first requests all of the eNBs 102a, b...n in the known tracking area to send a paging message to the UE 101 to motivate the UE to transmit the RRC Connection Request message.

Within connection mode 402, UE 101 may implement a DRX procedure that is controlled within a Medium Access Control (MAC) layer. The DRX pattern is defined by using multiple timers and programs that can be triggered by data activities or other events. However, the total DRX degree can be conceptualized to exist in one of three main modes, one of which can be in use at any one time. It is therefore possible to consider these DRX modes as the MAC substates of the RRC connected mode 402, with each MAC substate being associated with the DRX level:

‧ Continuous reception 402a: The receiver without DRX-UE 101 is always on and is ready to receive user plane data via the RRC connection.

‧ short DRX 402b: allows the UE to turn off its receiver (sleep, or DRX) for all subframes except M of the N (where the subframe is 1 ms transmission time unit in the LTE system), where M Is a small value, such as 1 or 2, and N is a relatively small value, such as 8.

‧Long DRX 402c: Allows the UE to turn off its receiver (sleep, or DRX) for all subframes except M of N, where M is a small value, such as 1 or 2, and N is a relatively large value , such as 256.

For proper system operation, both eNB 102a and UE 101 classify which subframes are classified as DRX (UE 101 sleepable) and which subframes are not classified as DRX (UE 101 cannot sleep) Sleeping and synchronizing is important. To achieve this coordination, the inactivity timer can be configured (in both UE 101 and eNB 102a) to implicitly control (ie, no signaling commands or instructions) toward the connected mode DRX with increased DRX. The change of state. In addition, the MAC command can also be used by the network (sent from the eNB 102a to the UE 101) to explicitly direct the transition to the increased DRX sub-state.

When in connection mode 402, any communication of new user plane data typically results in a continuous reception of substate 402a during the period determined by the ongoing packet data activity and the inactivity timer called the DRX inactivity timer. change. Each new data packet resets the DRX inactivity timer to a pre-configured value and when the timer expires, transitions from one of the continuous reception 402a to one of the DRX sub-states 402b, 402c.

In the LTE system, the mechanism for controlling UE mobility between cells of the network differs between the idle mode 401 and the connected mode 402:

In the idle mode 401, the mobility is UE controlled (i.e., the UE 101 performs the cell selection and reselection procedures in accordance with the 3GPP technical specification 36.304 and in accordance with the relevant configuration parameters set by the network). After selecting or reselecting a new cell by the UE 101, the UE 101 will inform the network of its new location only when the new cell belongs to a different tracking area than the tracking area of the previously camped cell. The tracking area is a group of cells - which cells belong to which - the tracking area depends on the network configuration. Thus, in the idle mode 401, the mobility report is rarely transmitted by the UE 101, and the network is aware of the location of the UE with a relatively coarse granularity (a tracking area level as compared to the cell level).

In connection mode 402, UE 101 performs measurements of other cells (on the same or other frequencies) according to the configuration sent by the network to the UE 101 in the measurement control message. The measurement is reported by the UE 101 to the network, where the measurements are used by the network to make a handover decision. After the handover decision is made by the network, the UE 101 is instructed to move to another cell or frequency. Thus, in connection mode 402, the measurement report can be sent relatively frequently and the network is aware of the location of the UE at a finer granularity (to the cell level).

The RRC and MAC/DRX sub-states for LTE are summarized in Table 1 below.

As will be apparent from the description below, the present invention is described for use in, for example, a RRC connection in an LTE wireless communication network such that at least user plane communication between the UE and the eNB is disabled (ie, not by the UE) And the eNB transmits or receives), but wherein the suspended RRC connection can be effectively restarted, so that communication between the UE and the eNB is replied across the same "established" RRC connection without having to create a new RRC connection. This provides significant advantages for wireless communication systems for the following reasons.

Some applications executing on the UE can generate traffic that requires transmission resources to be provided less frequently or in a short period of time. Traffic of this nature can be characterized as "cluster" or "occasional" and can involve extended periods of time with little or no data activity. When this traffic is handled within the system, frequent RRC state transitions for the UE 101 from the idle mode 401 to the connected mode 402 will each involve between the UE 101 and the RAN 102, and/or between the RAN 102 and the CN 103. Significant signal exchange. Signaling may, for example, require: 1. Establish or reconfigure a radio bearer (eg, via the Uu interface between UE 101 and RAN 102), 2. Establish or reconfigure other bearers, bearer fragments, or communication paths (eg, S1 bearer between LTE eNBs 102a, b...n and SGW 103a, or SGW 103a and PGW 103c Between S5/S8 bearers), 3. Perform security procedures to establish secure communications, 4. Establish or reconfigure physical radio resources to be used for connectivity or during connection, and/or 5. Configuration and RRC Other parameters related to the operation within the connection mode.

If for reasons of network efficiency, the UE 101 is always in the RRC connected mode 402 when handling this traffic, so that the repetitive state transitions described above and the associated network messaging burden are avoided, which may result in the UE 101. The high power usage and short battery life are due to the relatively high power requirements that are always on in the RRC connected mode 402. This is because, in the RRC connected mode 402, mobility is always network controlled at the cell level (which involves measurement reports from the UE). In addition, although DRX cycles (controlled by the MAC layer) can be used to reduce UE power consumption during periods of data inactivity, mobility remains network-controlled and the connected mode DRX configuration is also set by the network and may not The UE is provided with power consumption comparable to the power consumption of the idle mode 401. Moreover, some of the radio transmission resources may be assigned, reserved, or used by the UE when used in connected mode for control signaling purposes, although there may be no immediate user plane data for transmission. The connected mode DRX sub-state may thus exhibit excessive power consumption for the UE 101 or inefficient use of system resources for the RAN 102, and transition to the idle mode 401 (and then return to the connected mode 402 upon replying to the data activity) A significant signaling burden can be incurred in execution.

As will be apparent from the description below, as explained in the present invention, the suspension of the RRC connection controls the wireless communication system (i.e., the repeating state) during the so-called "clustering" or sporadic data transmission to the UE in particular. These two techniques of transitioning or maintaining the UE in the DRX sub-state of the connected mode 402 provide advantages such that in the present invention, network traffic and power consumption can be relatively low and battery life can be relatively high.

In the present invention, it is better than being in the connected mode 402 but temporarily not active (i.e., due to the fact that no immediate data transfer is required during the inactive period of the burst or sporadic communication) The UE 101 is transitioned to the idle mode 401 or to the connected mode DRX sub-states 402a, 402b, which are instead configured to perform UE control mobility (UE autonomous cell selection/reselection) and DRX procedures, just like In idle mode (re-use idle mode configuration to eliminate the need for new RRC state definitions or configurations). However, although acting as if in idle mode, the RRC connection for the UE can be considered "aborted" (as opposed to release). The difference between the RRC suspension and the RRC release is a network component that does not discard some or all of the RRC connection information or the RRC message and instead stores it in the Radio Access Network (RAN) or the Core Network (CN). And/or stored at the UE 101 (such as at one or more eNBs 102 and/or Mobility Management Entity (MME) 103b).

The stored (suspended) RRC connection information may include, for example, one or more of the following: current configuration with radio bearer, radio resource, temporary cell identifier, security parameter or key, MAC configuration, physical layer Configure and measure and report configuration related parameters. The RRC connection information or the RRC message information may also be composed of data related to the RRC layer or other layers such as the physical layer, the MAC layer, the RLC layer, and the PDCP layer. Safety parameters or keys may be (e.g.) comprises _{K asme, Kenb, KRRCenc, KRRCint} , KRRCUPenc, integrity algorithm, encryption algorithm, and radio bearer COUNT value. Therefore, one or more components of the radio connection "message" still exist in the network component and the memory in the UE 101, but these components can be marked as "not in use", "standby" or "Suspended." This may mean that one or more of the stored RRC connection parameters may not be used for immediate user plane communication between the UE 101 and the eNB 102a without first performing one or more of the following steps: determining its The current validity step is the step of restarting or re-establishing the connection via the cell of the radio access network to return to the normal connection mode from the suspended state.

When the RRC connection is aborted, the components of the RRC message data may be stored or maintained in the UE and/or the network. The criteria for triggering or initiating a connection abort can be linked to an activity or profile of data that is executed, turned on, or caused by one or more applications in use. This may include the amount of data or data speed required by a radio connection or by one or more applications. Estimation, prediction or measurement of the rate. It may further include an estimate, prediction or measurement of the packet arrival time or the arrival interval.

The criteria for triggering may also be linked to the UE or the state of the mobile device connected to the RAN via the UE. The aspect of the UE status may include one or more of the following:

‧ The degree to which the user interacts with the device, such as whether the keyboard of the device has been touched recently, the state of the screen or screen backlight, whether the touch screen has recently been touched, the state of the device that the other user inputs or responds to the user input gesture

‧ Execution status of the executed application, including whether the application is enabled, executed in the foreground or in the background, stored in memory in a pause or hibernation state

• The agreed status of the executed application, including whether the response or reply from the peer entity is on hold and whether, for example, further data exchange is expected within a period of time

In still other alternatives, the criteria for triggering can be linked to an application activity, an application type, an application tag, or an application identifier. The criteria for triggering can be further linked to application state or characterization, such as whether the application is executing in background communication mode. The background communication mode may include a state in which the current quality of service (QoS) requirements may be relaxed from the normal QoS level, for example due to the recent lack of user interaction with the device or due to the latency of the application data. Tolerance.

The criteria for triggering may also be linked to the UE's mobility situation, such as the link to the speed of motion or to the most recent, current or expected number of changes per unit of time in the cell. At higher speeds, a transition to triggering (or easier to trigger) to the RRC abort state may be required in order to avoid the need for network control handover procedures and the signaling burden associated therewith. The received or reported radio conditions (such as signal-to-noise ratio or signal-to-interference ratio, signal power or quality estimation, or path loss between nodes and UEs within the RAN) may also form criteria for initiating the suspension of the RRC connection. section.

Can be at a higher level (such as application manager, operating system controller or manager function, NAS (non-access layer) level) or at the AS (access layer) level (such as RRC, MAC or The physical layer level is determined by a decision from the user plane entity, or from the device input/output function, from the radio receiver or signal processing function or from the input of the application.

The eNB typically controls the connection abort, but the suspension can be initiated by the UE or eNB. In the UE initial condition, the eNB may take a decision to abort the connection after receiving a suspended request from the UE. However, the eNB may also decide not to suspend the RRC connection or decide to release the RRC connection after the request for termination from the UE. This can occur, for example, because the eNB is aware of something the UE is not aware of, such as for UE downlink user plane data. In the eNB initial condition, the eNB may decide to suspend the UE connection if the abort request is not received from the UE.

The RRC connection suspension can occur in one of two ways,

a. Implicitly, by associating an abort with another event or trigger, this is typically (but not necessarily) generally known to the UE and the eNB. The suspension may occur at the same time as another event, or may occur at the time of linking to another event (eg, by expiration of a timer or timer). Implied suspension can occur in the UE and/or eNB or

b. By using an explicit signaling exchanged between the UE and the eNB (or vice versa)

In some embodiments, if the need for user plane communication occurs for a UE with aborted RRC message, the RRC connection may only be checked after the suspension of the RRC connection or the associated suspension of the RRC message is currently valid. Used (by the network or UE when appropriate). The effective suspension of the RRC message is a RRC message that may be deactivated (ie, "restarted" or re-established) without the need to release the RRC connection and establish a new RRC connection. Thus, if the RRC message is considered "valid", the UE 101 or eNB 102a may initiate a restart or re-establish procedure instead of establishing a new RRC connection (and it will not utilize the stored RRC message material). The valid RRC message that has been deactivated is again ready for use so that user plane communication between the UE 101 and the eNB 102a can be replied without the need to extend the RRC release, setup or setup procedure. The set of cells on which the RRC message is considered "valid" is called the validity zone. Within the validity area, the UE or network can initiate or attempt to use The restart or re-establishment procedure of the RRC connection before the suspension.

The UE considers that the set of cells in which the RRC message is valid may be the same as or different from the set of cells that the network considers the RRC message to be valid. Therefore, the validity area of the UE may be the same as or different from the network validity area. If the UE or the eNB attempts to restart or re-establish the suspended RRC message in the cell in which the peer entity (eNB or UE) does not consider the RRC message valid, the restart or re-establishment may be unsuccessful and a new RRC connection may be established.

The "RRC Restart" or "Re-establish" message or procedure needs to restart the previously aborted RRC connection and allow the user plane data to be transmitted (using some or all of the previously stored RRC connection configuration). This procedure can be performed within the RRC connection previously suspended cell ("abort cell") or within the new cell. Similarly, the procedure may be performed in the case of an eNB ("sustained eNB") to which the UE is connected when the RRC connection was previously suspended, or in communication with the new eNB.

In some cases, the suspended RRC connection may be restarted (or re-established) without modifying the RRC message, its configuration, or its parameters. In this case, the RRC connection can be reused to continue to handle user plane communications. This situation may be more likely if the restart or re-establishment procedure is performed within the abort cell or within a cell controlled by the abort eNB. This is particularly useful when dealing with burst type data traffic and can save power and keep control plane traffic associated with RRC connection handling low. In other situations, one or more of the stored RRC messages may need to be updated during the restart or re-establishment process. This situation may be more likely if the restart or re-establishment procedure is performed in a cell other than the abort cell, or in a cell not controlled by the abort eNB.

In other cases, it may not be possible or possible to restart or re-establish the suspended RRC message. The criteria for controlling whether the RRC message can be restarted or re-established may be pre-established within a standard or may be provided to the UE, eNB, or to another network entity via configuration steps. If it is determined that many of the components of the stored RRC connection will need to be updated, a decision may be taken not to restart or re-establish the suspended RRC message. In this situation, normal The RRC connection setup procedure can then be as in the case of the normal idle mode UE (i.e., the RRC connection is set up after the random access or paging procedure).

A simplified diagram of this RRC restart procedure is shown in the flow chart of FIG.

This can be contrasted with the normal RRC connection setup procedure from the idle mode shown in Figure 6, where RRC abort functionality is not provided in the wireless communication network. As can be seen by comparing the flowcharts of FIG. 7 and FIG. 6, according to the present invention, after the suspension of the RRC connection, when the need for user plane data communication occurs and it is determined that the RRC connection is suspended or the associated suspension RRC message is "valid" The RRC connection may be successfully restarted by the RRC connection restart or re-establishment procedure before the user plane data can be transmitted. Optionally, various RRC connection/message validity criteria in UE 101 or eNB 102a or both may be checked prior to triggering an RRC Connection Restart or re-establish procedure. Also due to the fact that the active S1 interface must also exist before the communication of the user plane data, the node of the CN 103 (such as the MME 103b) may also be involved in checking the validity status of the suspension of the RRC connection when a restart is required. Examples of validity criteria that can be used as input to a decision-making process are listed below:

‧ When the RRC message is aborted, the UE 101 is currently camped on the same cell as the cell to which it is connected. Typically, the RRC configuration is applied on a per cell basis and the message remains valid only when the cell has not changed. Note that this does not exclude the possibility that the UE 101 has moved outside the cell in which the RRC message was aborted and moved back to the same cell again. Under these conditions, the RRC message can still be restarted and deemed to be a valid suspension of the RRC message.

‧ When the RRC message is aborted, the UE 101 is currently camped on the same cell group as the cell group to which it is connected. The eNBs 102a, b...n will typically support multiple cells, allowing for significant coordination between their cells at the radio resource management and RRC level without the need for a standardized interface. Thus, the RRC message information of the UE can be seen to the group of cells (such as in the same eNB 102a, b...n) and the operator or network provider can choose to coordinate some aspects of the RRC configuration between them. This can be aborted in one of the cells under eNB 102a. The RRC connection can be restarted or re-established under another cell of the same eNB 102a. In situations such as this, knowledge of whether the UE 101 is still attached to the same eNB 102a, b...n (or other defined cell group) may be useful when checking if this restart is possible or allowed. The cell group may alternatively include a tracking area. In a further alternative, each of the cells in which the RRC message is considered valid may not be controlled by the same eNB 102a, b...n. In this case, it may be necessary to transfer the RRC message information from the "old eNB" (the eNB responsible for the previous suspension) to the "new eNB" (the eNB controlling the cell to which the UE is located at the time of attempting to restart or re-establish) . This transmission of RRC message information will be required to complete the restart or re-establish procedure by the new eNB.

‧ Whether the period elapsed after the suspension of the RRC connection is lower than the predetermined timer expires. The system may wish to limit the length of time that the RRC connection can remain in the suspended state. Aborted connections with an age beyond the pre-configured value are no longer considered valid.

As described above, according to the present invention, the UE 101 in the temporarily inactive connection mode (i.e., having the "suspended" RRC connection) performs UE control mobility as if it is in the idle mode (UE autonomous cell selection/reselection). And the DRX procedure, and the RRC connection for this UE during this time period can be considered "aborted" (in contrast to the release). However, it is of course possible to look at the situation or state of the UE during this time in different ways, for example:

1. The UE 101 can be considered to be in idle mode (when it performs the UE Control Action and Idle Mode DRX procedure) but keeps storing some or all of the configuration associated with the most recent RRC connection to allow the old in some cases The RRC connection is quickly and effectively restarted or re-established.

2. The UE 101 may be considered to remain in the RRC connected mode but configured to perform UE Control Mobility and DRX procedures similar to the idle mode. All or most of the RRC connection information remains stored in the UE 101, and some portions of the RRC configuration are released.

3. The UE 101 may be considered to remain in the RRC connected mode but placed in a new state or sub-state or mode in which the UE 101 performs a mode similar to the idle mode. The UE controls the mobility and DRX procedures. All or most of the RRC connection information remains stored in the UE 101, and some portions of the RRC configuration are released.

In fact, the invention is not intended to be limited to the UE being considered to be in connected mode but wherein the RRC connection is "suspended". In fact, the present invention describes handling the RRC connection between the UE and the RAN, and the UE-related connection between the RAN and the CN, such that the transmission of the user plane data between the UE and the RAN is disabled and the storage indicates the RRC connection. The data allows the same "established" RRC connection to be used later (in the absence of the "established" RRC connection, the RRC connection is "released" (ie, abandoned) and without the need to create a new RRC connection A method of replying to user plane data transmission (on the same cell/eNB or on different cells/eNBs). This method can be used not only in wireless communication systems supporting LTE but also in other wireless communication protocols.

The method of the present invention associated with implementing and supporting the RRC connection suspension and restart procedure will now be described in more detail, including possible alternatives and variations. The procedures associated with the RRC connection suspension and restart can be divided into four aspects, which are described in the following sections:

‧ RRC connection procedure

‧Protect the action procedure during the RRC connection suspension (ie, the procedure when the UE moves)

‧ Procedure for handling the reception of downlink (DL) data during the RRC connection suspension period

‧ Disposal of the procedure of aborting the RRC connection to reply to Uu data transmission

The methods of operation of UE 101, eNBs 102a, b...n, SGW 103a, MME 103b, and other CN nodes described herein within the scope of the present invention, and other modes of operation may be at least partially comprised by UE 101, eNBs 102a, b...n Provided by one or more processors within SGW 103a, MME 103b, and other CN nodes, the one or more processors executing machine readable instructions to configure UE 101, eNBs 102a, b...n, SGW 103a, MME 103b And other CN nodes act accordingly to perform the methods. Instructions can be provided as a computer Software products. Each computer software product can be provided in, on, or supported by a computer readable medium that can be provided to be transitive in nature (such as, for example, transmitting data via, for example, the Internet) Or all possible permanent and non-permanent forms of computer readable media that are not intrinsically (such as in RAM or other non-volatile storage). In another aspect, a computer readable medium can be a non-transitory computer readable medium containing all computer readable media, except that the signal is temporarily propagated.

RRC connection abort procedure

In UE 101, when an RRC connection abort occurs, UE 101 may be configured to perform an idle mode mobility and paging reception procedure while maintaining some or all of its RRC message information for possible reuse. The stored RRC message information may include the following:

‧ Configuration of Data Radio Bearer (DRB) and Signaled Radio Bearer (SRB) has been established, including PDCP configuration and current status (eg counter value, etc.) and RLC configuration and status for each radio bearer ( For example, counter value, etc.).

‧Security configuration and status (eg, encryption and integrity algorithms, counter values, etc.)

‧ Measurement report configuration.

‧ Last used cell ID and cell-specific user ID (C-RNTI - "Cell Radio Network Temporary Identifier")

In addition, the stored RRC message may also include other information such as, but not limited to, configuration information or parameters related to any allocation of radio resources, MAC configuration, physical channel configuration, or physical layer configuration data.

In the network, when an RRC connection suspension occurs, one or more eNBs (such as eNBs 102a and 102b) and/or MME 103b store some or all of the UE's RRC message information for possible reuse. The RRC message information stored in the network should correspond to the RRC message information stored in the UE 101. In addition, there are two main alternatives to the network side suspension procedure, depending on whether the eNB informs the CN about the abort at the time of the suspension:

‧ RRC connection suspension alternative A - did not inform CN to suspend

If the CN 103 is not informed (by the UE 101 or the eNB 102a), the S1 user plane between the S-GW 103a and the eNB 102a will remain active and any inbound network origination material will be passed by the S-GW 103a via S1. Forwarded to the corresponding eNB 102a, the network origination material will need to be buffered at the eNB 102a to suspend delivery to the UE 101. The eNB 102a is then responsible for contacting the material and delivering the data to the aborted UE 101. If it is found that the aborted UE RRC message is invalid at this time (eg, because the UE has moved or reselected to another cell without notifying the network), the eNB 102a will need to initiate additional procedures (involving other eNBs such as eNB 102b and / or CN 103) to locate the UE 101 and to route the data to the correct eNB 102b...n and previously to the UE 101 (the procedure for contacting the UE 101 in this case is discussed below). Alternatively, rather than continuing to target the correct eNBs 102b...n once the UE 101 is located, the data may be discarded and may instead rely on higher layer protocols (e.g., TCP/IP) to ensure final delivery.

‧ RRC connection suspension alternative B - inform CN to abort

If the CN 103 is told to be aborted (e.g., by the UE 101 or the eNB 102a), then action may be taken to also suspend the S1 user plane between the S-GW 103a and the eNB 102a. The S1 user plane suspension may only affect the manner in which the S-GW 103a is to access the DL user profile of the S-GW 103a. Thus, in this case, it can be considered that only the DL S1 user plane is aborted such that any inbound network origination material is buffered at the S-GW 103a, thereby leaving the delivery to the UE 101. The CN 103 (i.e., the MME 103b and/or the S-GW 103a) is then responsible for identifying the location of the UE and then contacting the material and delivering the data to the aborted UE 101. The CN 103 may also not suspend the S1 user plane for the UE 101 when being informed of the suspension of the RRC connection of the UE.

The CN 103 will typically be notified of the suspension via a notification message received from the eNB 102a. The UE 101 may also inform the CN 103 that the connection is aborted (e.g., after it receives the abort message from the eNB 102a), but this may be less preferred, as this would involve the fact that additional signaling via the null plane is involved.

A CN node (e.g., MME 103b and/or S-GW 103a) may maintain a validity indicator for each UE (this may be effective with the presence of the S1 user plane for the UE, or for The UE suspends the current validity status of the S1 user plane. This indicator can be set based on one or more separate sub-criteria such as location based criteria or timer based criteria. The location-based validity criteria may involve, for example, recording a cell validity indicator set by the cell or eNBs 102a, b...n from which the RRC suspension notification was originally received and if the currently known location of the UE 101 matches the validity criteria. True, and otherwise set the location validity indicator to false. The timer based validity criterion may relate to setting the timer based validity indicator to true if the elapsed time after the RRC connection is aborted (or the S1 connection is aborted) is below the threshold and otherwise set to false. By way of example, the total validity criterion may include setting the total validity indicator to true if both the location validity indicator and the timer based validity indicator are true, and otherwise the total validity indicator Set to false.

An example message sequence diagram showing events related to RRC connection suspension is shown in FIG. Steps E through G of the procedure described below are performed only when the CN 103 is notified to be aborted (but not shown in Figure 8) (otherwise, these steps are omitted). The steps of the RRC connection abort procedure shown in Figure 8 can be described as follows:

A. The UE 101 is in connected mode.

B. Determine that the criteria for triggering the RRC connection suspension of the UE have been met. This determination may be made by the UE 101 or by the eNB 102a or by both the UE and the eNB. If the determination is made by the UE 101, the UE may send an RRC Connection Abort Request message to the eNB 102a.

C. Suspend the RRC connection of the UE. This may be achieved via an implicit mechanism such as an expiration of an inactivity timer in both the eNB 102a and the UE 101, or via an explicit mechanism such as the transmission of a message or command from the eNB 102a to the UE 101 indicating that the RRC connection was aborted. . In the implicit case, the eNB 102a and the UE 101 enter the suspended state at about the same time but no abort message needs to be sent.

D. UE 101 and eNB 102a suspend the RRC connection. Effectively "to start" Uu The user plane data is not transmitted between the eNB 102a and the UE 101 but the RRC connection information is stored by both the UE 101 and the eNB 102a. In some cases (not shown), RRC connection information may also be forwarded by eNB 102a to another eNB within RAN 102, or to a node within core network 103, such as MME 103b. However, the UE 101 continues to monitor notifications of paging or downlink data (see below).

E. The eNB 102a may optionally send an S1 User Plane Abort message to the MME 103b and/or the SGW 103a (possibly via the MME) to inform the CN 103 that the RRC is aborted. The message may include identifying one or more UEs that have been aborted and possibly carrying an identifier.

The F.MME 103b may deactivate (but store in memory) the existing S1-MME (S1c) bearer message associated with the UE 101. "Unboot" is understood here to mean stopping the transfer of data via the bearer.

The G.SGW 103a initiates (but stores in memory) the existing S1-u user plane associated with the UE to carry the message. Again, "going to start" is understood here to mean stopping the transfer of data via the bearer.

The specific actions taken by the CN 103 in response to receiving the suspension of S1 may thus include:

‧ Go to start (but store shelving restart) one or more S1 user planes and/or S1-MME bears messages in SGW 103a and MME 103b or in eNB 102a respectively

‧ buffer any network origin user data at SGW 103a to put aside the S1 user plane reply

‧ Monitoring the inbound tracking area or other location/cell update at the MME 103b from the UE whose RRC connection has been aborted (to help determine the validity status if a restart is required)

In order to use the above RRC Connection Abort procedure, both the UE 101 and the network of the wireless communication system need to be configured to support this functionality. The RRC Connection Suspend Support Indicator may be included in the UE Capability Message transmitted from the UE 101 to the network. Alternatively, support for RRC connection suspension in the UE may be implicitly inferred by the eNB to indicate to the UE as another (but associated) feature. The result of the UE capability within the support or UE capability message. As a further alternative, support for RRC connection suspension in the UE may be implicitly inferred by the eNB as a result of receipt of the RRC Connection Abort Request message. If the eNB determines that the UE supports the RRC Connection Abort functionality, the eNB 102a may choose to configure the UE 101 by triggering the appropriate parameters of the implicit suspension (eg, via configuration of the abort timer value) or the eNB 102a may choose to send the explicit The RRC connection aborts the message. The eNB 102a may also choose to configure the UE 101 to allow or disallow the components of the RRC Abort Procedure or RRC Abort Behavior.

Procedure for handling action during RRC connection suspension

When the RRC connection suspension of the UE is aborted, the UE 101 performs cell selection and reselection in a manner similar to that of the normal idle mode UE 101 (i.e., the UE 101 follows the general mobility procedure of 3GPP TS 36.304). However, if location-based validity criteria are used, the UE 101 may be aware of when the UE 101 selects/reselects a cell in which the RRC connection is not available (eg, may not restart or re-establish a cell that aborts the RRC message).

An example is shown in Figure 9, where UE 101 is initially on cell A (point 1) under eNB1 102a. Abort the RRC connection. The UE 101 reselects from the cell A under the eNB1 102a to the cell B (point 2) which is also under the eNB1 102a. Cells A and B may be located within the validity area and cell C may be outside the validity area. When the UE moves from cell A to cell B, from the location-based validity criteria, the UE 101 knows that its aborted RRC connection is still valid and therefore does not require action. The UE 101 then reselects from cell B to cell C (point 3) under a different eNB (i.e., eNB2 102b). From the location-based validity criteria, the UE 101 knows that the RRC connection it was aborted is no longer valid at point 3. At this point (crossing the validity region boundary), there are two primary alternative action handlers for the manner in which the UE 101 acts during the RRC connection suspension. The UE 101 can be configured to perform only one of the following methods, or to selectively perform either method.

‧Mobile alternative A - does not inform the network UE to be outside the area where the RRC connection is valid

Although at time 3 the UE 101 is aware that it is outside of the area in which it knows that the RRC connection is active, the UE 101 does not initiate any signaling towards the network. Alternatively, the UE 101 continues to perform UE-based mobility and paging reception procedures and continues to maintain its stored RRC message information. In the mobile alternative A, as long as the UE 101 remains within the registration tracking area (TA) of the cell, the cell reselection does not trigger any signaling towards the network (ie, the network is not aware of the reselection). However, if the UE 101 moves outside of its registered TA, the UE 101 will still need to perform a Tracking Area Update (TAU) as it would have to do in idle mode. The TA will typically cover many cells and many eNBs 102a, b, ... n. The RRC message information remains stored in the UE 101 and one or more RAN or CN nodes (such as eNB 102, eNB 102b, or MME 103b) such that if at the time of the data activity reply, the UE 101 has returned to suspend the RRC connection. For a valid cell, some or all of the RRC message information may be used. Depending on the validity area, the aborted RRC connection restarted cell or eNB may be the same or different from the last suspended cell or eNB of the RRC connection.

‧Actional Alternative B - Inform the network UE to be outside the area where the RRC connection is valid

When the UE 101 is aware at point 3 that it is outside of the area in which it knows that the RRC connection is active, in this alternative the UE 101 initiates a signal to inform the network. In the case of the mobile alternative B, the signaling procedure employed by the UE 101 can be, for example, one of the following three variants:

○ Signaling variant 1 - Discard the aborted RRC connection, execute the NAS program and return to idle.

On the new cell under eNB2 102b, in this variant the UE 101 discards the aborted RRC connection and performs signaling by initiating a non-access stratum (NAS) procedure (e.g., LTE "TAU" procedure). This may be an unmodified TAU procedure or may be a TAU procedure modified to include a cause value indicating the reason for transmitting the TAU (ie, the RRC connection that the UE has identified to abort is not Effective again). This TAU procedure causes MME 103b to release the S1 connection to eNB1 102a and cause eNB1 102a to release the suspended RRC connection. Upon completion of the TAU procedure, the UE 101 is placed in idle mode and thus does not have an RRC connection with any of the eNBs 102a, b...n.

○ Signaling variant 2 - Discarding the suspended RRC connection, executing the NAS procedure and maintaining the RRC connection.

On the new cell under eNB2 102b, in this variant the UE 101 discards the aborted RRC connection and performs signaling by initiating a NAS procedure (e.g., TAU or service request). This may be an unmodified TAU or service request or may be a modified TAU procedure or service request modified to include a cause value indicating the reason for the initial procedure (ie, the RRC connection that the UE has identified to abort is no longer valid). This TAU/Service Request causes MME 103b to release the S1 connection to eNB1 102a and cause eNB1 102a to release the suspended RRC connection. The MME 103b initiates the establishment of a new access layer security and data radio bearer (DRB) and the establishment of an S1 user plane connection to the eNB2 102b. Upon completion of the TAU/Service Request, the UE 101 maintains an RRC connection with the eNB2 102b. The eNB2 102b may choose to suspend the suspension of the RRC connection as described above such that the suspension of the new RRC connection between the UE 101 and the eNB2 102b is suspended. If so, the state of UE 101 at point 3 will be the same as it was at point 1 in Figure 9, but RRC is connected to eNB2 102b instead of eNB1 102a.

○ Signaling variant 3 - Maintaining the suspended RRC connection and performing a signal to inform the CN of action

On the new cell under eNB2 102b, in this variant the UE 101 maintains the suspended RRC message and performs a signal by the initiating procedure to inform the CN 103 that the UE 101 has an RRC connection with the current invalidation. This procedure may be a NAS procedure - for example, it may be an unmodified TAU or a TAU containing a new indication that the UE 101 has an invalid termination RRC connection, or it may be a new NAS message, such as a "NAS Mobility Update" message . Alternatively, this may be an access layer (AS) procedure that in turn triggers eNB2 102b to inform CN 103 that UE 101 has an RRC connection that is aborted but is currently inactive - for example, it may be sent from the UE to eNB2 102b The new "RRC Mobility Update" message, or it may be an existing RRC message containing a new "Action Update Indicator", followed by an "S1 Action Update" message from eNB2 102b to MME 103b. Regardless of the form in which the signal is sent, the purpose of the program is that it will cause the S-GW 103a to suspend the S1 user plane. Upon completion of the procedure, the UE 101 maintains the suspended RRC connection but camps on the eNB1 102a. Note that in order to perform the TAU procedure, the UE may or may not have to create an RRC connection with eNB2 102b and an S1 connection with MME 103b. If it is not necessary to create such a connection, this can be considered as a temporary RRC connection that is discarded when the TAU or other update message is completed. If the MME 103b will establish access layer security and establish a DRB, then the temporary RRC connection will become a "permanent" RRC connection and the aborted RRC connection will be discarded.

Action within the validity area

Mobility alternatives A and B describe example procedures associated with UE mobility events across the boundaries of the validity region (i.e., when the UE transitions into or out of the validity region). Other programs are possible. There is also a collection of possible actionable alternatives associated with the mobility of the UE between cells within the validity zone. In addition to procedures related to mobility across the boundaries of the effectiveness area, such "intra-regional action procedures" may be used as appropriate.

In an alternative in the first region, the UE performs signaling to inform the RAN and/or the mobility of the UE within the validity region. This may be used to allow the previously aborted RRC connection to migrate between the old cell and the new cell based on the mobility of the UE from the old cell to the new cell. The old cell and the new cell may be controlled by the same eNB and the MME, or may be controlled by different old eNBs and new eNBs, or different old MMEs and new MMEs. By referring further to Figure 9, cells A, B and C may all be located within the validity area. In this case, and when operating according to the mobility alternative in the first region, when the UE reselects to cell C (under eNB2 102b), the UE 101 communicates with eNB2 102b, thereby informing eNB2 102b that the UE is within the cell presence. This may take the form of an RRC re-establishment procedure or may include a new mobility update procedure. A modified version of an existing operational procedure, such as a procedure based on or containing signaling related to handover. Although eNB2 102b is located within the validity area, it may or may not have possessed RRC message material related to the RRC message for UE 101 suspension. This will depend on whether eNB1 102a has forwarded the RRC message data to eNB2 102b before the UE reselects to cell C. This transfer of RRC message data from eNB1 102a to eNB2 102b may be signaled via the use of handovers such as handover request (from eNB1 to eNB2) and handover request acknowledgment (from eNB2 to eNB1) (and this is shown in the figure) This is achieved in step 23 (10) and in step (8) of Figure 26, which is shown as an optional preparation by other eNBs of X2. If eNB2 102b does not own the RRC message material for UE 101, it may attempt to retrieve RRC message material from another node within RAN 102 (such as eNB1 102a) or from a node within CN 103 (such as MME 103b). The signaling procedure between eNB2 102b and other nodes (such as eNB1 102a or MME 103b) is used to retrieve RRC message data for UE 101 via the network interface between the RAN and the CN node. The RRC message can be retrieved from eNB1 102a by eNB2 102b via using, for example, an RLF indication message (from eNB1 to eNB2), a handover request message (from eNB1 to eNB2), and a handover request response message (from eNB2 to eNB1). The message is reached by signalling. An example of the message extraction signaling between the eNBs is shown in steps (4b) and (6) of FIG. 28 and an example of the message extraction signal between the eNB and the MME is shown in step (5) of FIG. Since eNB2 102b may also be in communication with a CN node (such as MME 103b and/or S-GW 103a) in order to switch the path of the active or suspended S1 connection associated with UE 101, such that it now terminates at eNB2 102b instead of the eNB. 102a. If eNB2 102b wishes to accept a connection with the UE, eNB 102b communicates with UE 101 to command or confirm the restart or re-establishment of the RRC connection within cell C (in this case RRC connection self-suspension reply), or only to UE 101 Acknowledgement or response to an action event (in this case, thereafter the RRC connection may return to the suspended state after successful transmission of the UE message to cell C under eNB2 102b).

In an active alternative in the first region, the RAN is informed each time the UE reselects another cell within the validity region. This carrying network can switch S1 connections (from the core network to RAN) to the correct RAN node (eNB) in order to track the advantages of the UE's mobility. Thus, inbound downlink data destined for the UE can always be routed (via S1) to the correct eNB and delivered to the UE, thereby avoiding the need to first page the UE across a wider area to determine its current cell or location.

In an active alternative in the second region, the UE may not inform the RAN or CN at the time of cell reselection within the validity region. Alternatively, the UE may wait until there is a need for user plane data before communicating with the eNB controlling the cell in which the UE is currently camped. Under such conditions, if the UE is located within the validity zone, the UE may attempt to restart or re-establish the suspended RRC connection on the currently camped cell. If the eNB controlling the currently camped cell does not own the stored RRC message data for the UE 101, it will again need to be invoked from another node in a manner similar to that described for the mobility alternative in the first region. Capture the RRC message program. Although this mobility alternative in the second region carries a certain advantage, since it is possible to avoid operative signaling (moving the suspended RRC connection to the new cell) at each cell reselection event, it also carries shortcomings. That is, in the case where the inbound downlink data goes to the UE, the network may not have the latest information about the current cell or location of the UE. Therefore, it may be desirable to page the UE in other cells before the data can be delivered.

An example message sequence diagram for three signaling variants (1, 2, 3) for mobility across the boundaries of the validity region is shown in Figures 10, 11 and 12, respectively. The initial steps of these figures are the same, with the difference between the three variants occurring in the area identified by the rectangle with rounded ends.

The signaling variant 1 shown in Figure 10 can be described as follows.

1. The UE 101 initially has an aborted RRC connection with the eNB1 102a.

2. The UE 101 performs cell reselection to the cell under the control of the eNB2 102b.

3. After the cell reselection, the UE 101 determines that it is now in a cell in which the RRC connection may not be valid.

4. The UE 101 releases the RRC connection for eNB1 102a. The UE 101 enters an idle mode.

5. The UE 101 starts the TAU. In order to perform TAU, the UE 101 first establishes an RRC connection with eNB2 102b and then sends a tracking area update request. The MME 103b responds with a tracking area update accept.

6. After the TAU procedure is completed, the UE 101 returns to the idle mode.

7. The MME 103b also sends an S1 Release command to the eNB1 102a to inform the eNB1 102a that it can release any active or suspended S1 connection for the UE 101 to suspend the RRC connection and/or release for the UE 101.

The signaling variant 2 shown in Figure 11 can be described as follows.

1. The UE 101 initially has an aborted RRC connection with the eNB1 102a.

2. The UE 101 performs cell reselection to the cell under the control of the eNB2 102b.

3. After the cell reselection, the UE 101 determines that it is now in a cell in which the RRC connection may not be valid.

4. The UE 101 releases the RRC connection for eNB1 102a. The UE 101 enters an idle mode.

5. The UE 101 initiates a TAU or service request procedure. In order to perform the TAU or service request procedure, the UE 101 first establishes an RRC connection with eNB2 102b and then sends a tracking area update request or service request. The MME 103b responds by triggering the establishment of an access layer security and the establishment of the DRB and the S1 user plane with the eNB2 102b. The figure shows the service requester, but the TAU program will be quite similar. Note that the figure does not mark individual messages that make up the general program.

6. After the TAU or service request procedure is completed, the UE maintains an RRC connection with eNB2 102b.

7. The MME 103b also sends an S1 Release command to the eNB1 102a to inform the eNB1 102a that it can release any for the UE 101 to suspend the RRC connection and/or release for the UE 101. Use the middle or stop S1 connection.

The signaling variant 3 shown in Figure 12 can be described as follows.

1. The UE 101 initially has an aborted RRC connection with the eNB1 102a.

2. The UE 101 performs cell reselection to the cell under the control of the eNB2 102b.

3. After the cell reselection, the UE 101 determines that it is now in a cell in which the RRC connection may not be valid.

4. The UE 101 maintains the RRC connection for eNB1 102a.

5. The UE 101 initiates signaling to inform the CN 103 that the UE 101 has an aborted RRC connection but has moved to the outside of the area where the known RRC connection is valid. The example in FIG. 12 shows that the UE 101 establishes a "temporary" RRC connection and the UE 101 includes the "activity update indicator" in the RRC Connection Setup Complete message, but other alternatives are possible, including the use of the TAU procedure (in this case) The outgoing signal variant 3 is similar to the signal variant 1, except that the aborted RRC connection is maintained and not released after the UE reselects to the cell under the control of the eNB2 102b - that is, the procedure follows the signal variant 1 but Steps 4, 6, and 7) are not performed.

6. Upon receipt of the mobility update indicator, eNB2 102b is aware of the purpose of this RRC connection setup and sends an S1 mobility update message to MME 103b. In response to this, the MME 103b transmits an S1 user plane suspension message to the S-GW 103a.

7. Upon receiving the S1 User Plane Abort message, the S-GW 103a knows that the DL data for this UE 101 should be buffered and locates the UE 101 before the data can be delivered (i.e., the S-GW 103a should not simply pass via S1 forwards the DL data to eNB1 102a because there is a possibility that UE 101 will not be located under eNB1 102a).

8. eNB2 102b instructs UE 101 to release a "temporary" RRC connection. The UE 101 still maintains the RRC connection for eNB1 102a but camps on the cell under eNB2 102b.

For the mobility across the validity area boundary, the result of the two signaling variants 1 and 2 is that the UE 101 releases the suspended RRC connection and initiates transmission as soon as it moves to the area where the known RRC connection is valid. Signal program. Whenever the data activity replies, at It will be necessary to establish a new RRC connection (and security and DRB) before data transfer can begin. Therefore, if the UE is moving, signaling variants 1 and 2 may not be extremely effective in reducing the signaling load.

The benefits of signaling variant 3 are further explained by reference to FIG. 13 compared to variants 1 and 2, which shows a mobility scenario similar to the mobility scenario shown in FIG. 9, with suspension RRC in FIG. The connected UE 101 moves to point 3 out of its cell to another cell in which the RRC connection is invalid, but the situation of Figure 13 additionally shows that the UE 101 moves to points 4 and 5. As explained above, in the case of Signaling variant 3, at point 3 the UE 101 has an RRC connection associated with eNB1 102a and signals the network that it has moved to the area where it knows that the RRC connection is valid. Outside. S-GW 103a has been suspended to the S1 user plane of eNB1 102a.

In the Figure 13 mobility scenario, after moving to point 4, the UE 101 reselects back to cell B under the control of eNB1 102a. There is no need to initiate a signal towards the network. If the data activity will reply at this point, the RRC connection with eNB1 102a may be restarted. Similarly, if the S1 connection between the SGW 103a and the eNB1 102a has been previously suspended, the S1 connection can also be restarted.

In the Figure 13 mobility scenario, after moving to point 5, when the RRC connection with eNB1 102a remains aborted, UE 101 reselects back to cell C under the control of eNB2 102b. Although the UE 101 moves again to the outside of the area where it knows that the RRC connection is valid, there is no need to initiate any signaling. This is because the S1 user plane connection between SGW 103a and eNB1 102a has been aborted at S-GW 103a (this occurs at the transition from point 2 to point 3). If the data activity will reply at this point, the RRC connection with eNB1 102a will be released and a new RRC connection with eNB2 102b will need to be established.

It can be seen that in the case of signaling variant 3, it is only necessary to signal towards the network when the first UE 101 moves to an area where it knows that the RRC connection is valid, and when the RRC connection remains suspended, it can be performed. Subsequent movements to and from the zone without any letter number. Thus, this method is effective in reducing signaling, which can be associated with a UE 101 positioned close to the boundary of two cells, where "ping-pong" reselection between cells can occur.

As an extension of the Signaling variant 3, the UE may be configured to additionally perform towards the RAN whenever it moves back to the cell or group of cells in which the RRC connection is again active (eg, the cell under the control of eNB1 102a) Or signal from the CN node. This may enable aborting the S1 connection between the SGW 103a and the eNB1 102a.

The above procedure can be supplemented by aborting the timer-based expiration of the RRC connection. For example, the timer can begin at the time of the suspension, or at the time of leaving the cell (or group of cells). When the timer expires, the UE 101 (and the eNBs 102a, b...n and CN 103 nodes) discard any UE 101 message information and the UE 101 returns to the normal idle mode of operation. If a common timer is used within both the UE 101 and the eNB 102a, b...n or CN 103 nodes, this can occur without any signaling between the UE 101 and any of the RAN or CN nodes. If the timer is implemented only on the eNB 102a, b...n or CN 103 node side, a signal may be required for the RAN or CN node to inform the UE that the aborted RRC connection is being released and to indicate a return to idle.

Some of the possibilities of signaling variants depend on the use of existing programs (NAS Service Requests and TAUs) and thus UE 101 can assume that such programs are supported by the network. However, other possibilities for signaling changes depend on new signaling functionality. Under these conditions, it may be necessary for the UE 101 to know that the eNB2 102b supports the other signal before starting the new signal towards the eNB2 102b. To address this, eNB2 102b may broadcast a support indicator in the system information. This may be a general indicator indicating support for all RRC connection abort functionality or it may only indicate support for new signaling functionality (such as the mobility update for signaling variant 3 described in Figure 12) Option). If UE 101 sees that eNB2 102b does not support the functionality, UE 101 may fall back to signaling variants that do not require new signaling functionality (eg, the UE may release the terminated RRC connection and then initiate a TAU or Service request sequence).

In the present invention, "release RRC connection" may mean ignoring only the stored RRC message data, or indicating or indicating that the data is released or invalid, or clearing the data, or deleting the data from the memory. Other methods of achieving the same functional effects of releasing the RRC connection are also intended to be within the scope of the present invention.

Handling downlink (DL) data reception during RRC connection suspension

When the RRC connection suspension of the UE is aborted, the UE 101 may perform cell selection and reselection in a manner similar to that of the normal idle mode UE 101 (i.e., the UE 101 follows the general mobility procedure of 3GPP TS 36.304). In addition, the UE 101 can monitor the paging channel in exactly the same way as it did in the idle mode; that is, the UE 101 will power its receiver at the time of the appropriate paging appearance in an attempt to receive the paging message and then check if the paging message has The identification code of the UE (for example, S-TMSI). Upon receiving a paging message containing the identity code of the UE, the UE 101 will attempt to reply to the suspended RRC connection as described below.

When the DL data arrives at the network for the UE 101 with the RRC connection suspended, the network may be necessary to contact or page the UE 101 regardless of which cell the UE 101 is currently locating. Depending on whether RRC Connection Abort Alternative A or B (described above) is used, and using Mobile Alternative A or B (described above), the difference in paging UE 101 when DL data arrives at S-GW 103a The situation is possible. Thus, three scenarios for handling DL data in a network will now be described with reference to Figures 14-16. 14 shows a message sequence diagram showing a method of handling DL data in a network when the UE 101 has an aborted RRC connection with the eNB1 102a. The UE 101 is currently located on a cell under eNB1 102a and the S1 user plane between SGW 103a and eNB1 102a is not suspended (1). When the DL data arrives at the S-GW 103a (2), the S-GW 103a directly forwards the user plane data to the eNB1 102a (3). This is the normal S-GW 103a behavior for the UE 101 in the RRC connected state. The eNB1 102a buffers the DL data (4) and then transmits a paging message or data arrival notification message to the UE 101 (5). When the UE 101 responds to the paging/notification, it can be restarted (eg, via the transmission of the RRC restart request) The RRC connection is aborted and then eNB1 102a will be able to deliver the DL data. Figure 15 shows a message sequence diagram showing a method of handling DL data in a network when the UE 101 has an aborted RRC connection with the eNB1 102a. The UE is currently located on a cell under a different eNB (i.e., eNB2 102b) and the S1 user plane between SGW 103a and eNB1 102a is not suspended (1). When the DL data arrives at the S-GW 103a (2), the S-GW 103a directly forwards the user plane data to the eNB1 102a (3). This is the normal S-GW 103a behavior for the UE 101 in the RRC connection. The S-GW 103a is unaware that the UE 101 has moved or can be moved away from the eNB1 102a and thus the S-GW 103a cannot take any alternative action. The eNB1 102a buffers the DL data (4) and then transmits a paging message or data arrival notification message to the UE 101 (5). When the UE 101 is no longer located in the cell under eNB1, then no response (in the form of an attempt to terminate the RRC connection with the UE restart) is received (6). The eNB1 102a sends a "Paging Upgrade" message to the MME 103b (7) to request the MME 103b to page the UE 101 (8) via the wider cell group (e.g., the MME 103b may be all of the Tracking Area (TA) registered by the UE 101). The paging UE 101) in the cell.

16 shows a message sequence diagram showing a method of handling DL data in a network when the UE 101 has an aborted RRC connection with the eNB1 102a and the S1 user plane connection between the SGW 103a and the eNB1 102a is suspended (1). Note that the S1 user plane abort may occur as a result of the RRC connection suspension alternative B or as a result of the mobility alternative B with the signal variant 3. The UE 101 may be located in a cell under eNB1 102a (i.e., an eNB with an RRC connection abort) or it may be located under a cell of a different eNB 102b,...n. When the DL data arrives at the S-GW 103a (2), the S-GW 103a buffers the user plane data (3). The S-GW 103a then initiates a paging procedure towards the MME 103b to request the MME 103b to page the UE 101(4). The MME 103b then pages the UE 101 via a wider community group, for example, it can page the UE 101 in all cells of the TA registered by the UE 101.

Disposition RRC connection to reply Uu data transmission

The RRC connection restart may be triggered by the UL data generated in the UE 101, or by indication The network has a paging trigger for the DL data waiting to be delivered or a trigger for the receipt of the DL data notification message. When this occurs, the UE 101 first determines whether the RRC connection in which it is suspended is valid for the cell it is currently locating. Many different options are possible depending on whether the RRC connection that determines the suspension is valid.

Figure 17 shows a message sequence diagram showing an RRC restart method for a UE 101 having an RRC connection (1) with eNB1 102a. The need for an active RRC connection is triggered by the UL data generated in the UE 101 or by the reception of the paging or DL data notification message (2). The UE 101 determines that the suspended RRC connection is valid for the cell it is targeting (3). The UE 101 initiates an RRC Connection Restart procedure by transmitting an RRC Connection Restart Request (4). Upon receiving this message, eNB1 102a checks that it has a valid abort RRC connection for this UE 101. Depending on the situation (and not shown), it may also call another node from RAN 102 or CN 103 to retrieve the RRC message data for the UE, and may communicate with other nodes of the RAN or CN to initiate S1. The path is switched. If eNB1 102a has a valid suspension RRC connection (or has been able to retrieve a valid suspension RRC connection from another node), it sends an RRC Connection Restart message to UE 101 (5) and UE 101 restarts the completion message via RRC connection ( 6) Come and respond. The RRC Connection Restart message may or may not include configuration updates for one or more of the previously stored RRC connection parameters for use by the UE after reboot. The UE 101 can now begin to send any user plane data (8) that it can buffer. If the S1 user plane has been aborted, eNB1 102a may send an S1 user plane reply message to S-GW 103a (7) (possibly via MME 103b, as shown by the dashed line in FIG. 17) and upon receiving At the time of the message, S-GW 103a may reply to the S1 user plane and begin to forward any DL user plane data that may be buffered in S-GW 103a to eNB1 102a (8). Alternatively, and if the S1 connection is only suspended in the DL direction, receipt of UL user plane data from the UE 101 may be used by the S-GW 103a as an implicit S1 user plane reply message.

Figure 18 shows a message sequence diagram showing another RRC restart method for a UE 101 having an RRC connection (1) with eNB1 102a (but no longer valid). In effect The RRC connection needs to be triggered by the UL data generated in the UE 101 or by the reception of the paging or DL data notification message (2). In this case, the UE 101 determines that the suspended RRC connection is invalid for its located cell (3) (eg, if the UE 101 is not located on a cell within the specified validity area, or if the validity timer has expired In the case, the situation can be as follows). The UE 101 releases the suspended RRC connection and enters the RRC idle state (4). The UE 101 then initiates a normal procedure for establishing an RRC connection towards the eNB2 102b and establishing a user plane radio bearer (ie, the UE initiates a NAS service request procedure) (5) and when the procedure is completed, the user plane data Transfer is possible (6).

Figure 19 shows a message sequence diagram showing another RRC restart method for UE 101 having eNB1 102a determined to be inactive to terminate RRC Connection (1). The need for an active RRC connection is triggered by the UL data generated in the UE 101 or by the reception of the paging or DL data notification message (2). The UE 101 determines that the suspended RRC connection is valid for the cell it is targeting (3). The UE 101 initiates an RRC Connection Restart procedure by transmitting an RRC Connection Restart Request (4). Upon receiving this message, eNB1 102a checks if it has a RRC connection for this UE 101 and can also check if all required parameters of the stored RRC connection remain valid. Depending on the situation (and not shown), eNB1 102a may also invoke a procedure for extracting RRC message data for the UE from another node of RAN 102 or CN 103. In FIG. 19, eNB1 102a determines that it does not have some of the invalidation (5) for the UE 101 to suspend the RRC connection or the stored RRC connection parameters. This may, for example, be due to the expiration of the validity timer in eNB1 102a. Alternatively, it may be due to eNB1 102a having assigned some of the resources associated with suspending the RRC connection to another UE, or because eNB1 102a additionally determines to suspend some or all of the RRC connections for any valid reason. No longer valid. In other alternatives, it may be attributable to the UE 101 accessing an eNB different from the eNB having the UE discontinuing the RRC connection and the failure of the eNB1 102a to retrieve the RRC message data from the other eNB. The eNB1 102a responds with a RRC Connection Restart Reject message (6). The UE 101 releases the suspended RRC connection and enters the RRC idle mode (7). UE 101 then initiates to establish an RRC connection and establish use The normal procedure of the plane radio bearer (i.e., the UE 101 initiates the NAS service request procedure) (8) and when the procedure is completed, user plane data transfer is possible (9).

It may be necessary for the UE 101 to know that the eNBs 102a, b...n support each other before starting the new RRC connection restart request/setup/rejection signaling towards the eNBs 102a, b...n. To address this, the eNBs 102a, b...n can broadcast support indicators in the system information. This may be a general indicator indicating support for all RRC connection abort functionality or it may only indicate support for request/setup/rejection signaling. If the UE 101 sees the eNB 102a, b...n does not support the functionality, the UE 101 will release the aborted RRC connection and then initiate the service request procedure.

An alternative to the eNB 102a, b...n broadcast support indicator would be to set the region-based validity criteria in such a way that the eNBs 102a, b...n that originally suspended the RRC connection of the UE are in a manner to ensure that the UE 101 only attempts to restart the known The RRC connection is suspended on the cell/eNB 102a, b...n supporting the functionality. In the simplest case, the eNBs 102a, b...n that suspend the RRC connection of the UE will only include cells located under the same eNB 102a, b...n in the validity criteria. However, the validity area may span substantially across cells controlled by different eNBs.

There are many ways to combine the various RRC connection aborts and mobility scenarios described above. Table 2 below provides four possible combinations, but it should be noted that other combinations or sub-combinations are possible. In the example of Table 2, the combination of RRC Connection Abort Alternative A or B and Mobility Alternative A or B is discussed. For each combination, Table 2 describes the RRC connection and the state in which the S1 user plane connection will reside at each point in time. The status of the RRC connection and the S1 user plane can be:

‧ Idle - no RRC connection, no S1 user plane established

‧ eNB 1/2 - there is an RRC connection with eNB1 or eNB2, establishing an S1 user plane between the S-GW and eNB1 or eNB2

‧Stop (eNB1) - There is an RRC connection with eNB1, and the S1 user plane between the S-GW and eNB1 is suspended.

Columns T0 through T2 are defined with respect to different times/examples and are described with reference to FIG.

‧T0 - UE 101 is in position 1 of Figure 9 before the RRC connection is aborted

‧T1 - After the RRC connection is aborted, the UE 101 is in position 1 of Figure 9 (or position 2 if the UE 101 has performed cell reselection)

‧T2-UE 101 is in position 3 of FIG.

In this example, it should be noted that for combinations 3 and 4 shown in Table 2, RRC and S1 connections are shown for respectively corresponding to the signal variant 1/2/3 that can be employed in the mobile alternative B. Three possible situations of the situation.

In addition, it should be noted that the combination 4 corresponding to the RRC connection suspension alternative B and the mobile alternative B is shown in the table for completeness. However, with this alternative, as long as the RRC connection aborts the S1 user plane, this means that any DL data will be buffered at the S-GW 103a until the UE 101 is paged/notified and its RRC connection has been restarted as stop. Thus, there may be little benefit in performing any signaling when the UE 101 moves to a cell under a different eNB 102a, b, ... n.

In view of the various possible procedures for handling RRC connection suspension in accordance with the present invention have been described above, a number of example scenarios showing how such various suspension RRC connection handlers can operate together will now be described.

Case scenario 1

Figure 20 shows the RRC connection suspension between the UE 101 and the RAN 102 and the suspension of the alternative A (not informed of the CN RRC suspension) and the mobility alternative A (not informed of the network mobility) according to the above description. A message sequence diagram of a possible disposition of a later attempted restart, where (at the time of the restart attempt) the UE 101 has moved outside of the area where the suspension of the RRC connection is valid. Due to this processing, the CN 103 is unaware that the RRC connection is aborted and thus the S1 connection is not suspended. When the DL data arrives at the network, the network does not know with certainty the cell currently located by the UE 101, and does not know whether any suspension of the RRC message is valid. The S1 connection is not aborted and remains active, so the DL data passed in to the SGW 103a is forwarded to the eNB1 102a via S1. The eNB1 102a attempts to contact the UE 101 via the transmission of the paging message and, in the absence of a response, uses the paging upgrade method to contact the UE 101. The abort RRC connection is invalid in the cell in which the UE 101 is found and is thus released and a new RRC connection is established for the data to be delivered.

Referring to Figure 20, the sequence of steps in this case is:

1. The UE 101 is initially in an RRC connection and the user plane bearer is established such that user data is likely to be transferred between the UE 101 and the S-GW 103a and then continues to be transmitted to the P-GW 103c (not shown in Figure 20). And further afield.

2. Compliance with the criteria for triggering abort and eNB-1 102a decides to change UE 101 to UE control mobility and suspend RRC connection.

3. The eNB-1 102a sends a message indicating that the UE 101 enters the UE control mobility and suspends the RRC connection to the UE 101. For example, this message can be referred to as the RRC shown in the figure. The connection is aborted, or may be referred to as an RRC UE Control Action Command, or some other suitable name.

4. eNB-1 102a and UE 101 suspend the RRC connection. The UE 101 performs UE control mobility similar to the UE control mobility of the idle mode.

5. Cell reselection may occur when the UE 101 has suspended the RRC connection and entered the UE control mobility. As long as the UE 101 remains within the registered TA, then such reselection does not trigger any signaling towards the network (i.e., the network is not aware of the reselection in the mobile alternative A). Steps 1 through 5 (in addition to cell reselection) are indicated in Figure 20 with a rectangle above the rounded end.

6. After a period of time, when the RRC connection with the UE 101 is required again, the user plane data arrives at the S-GW 103a in the event of network origin. The S-GW 103a immediately forwards the data to the eNB1 102a on the S1 user plane interface. When the user plane data arrives at eNB1 102a, eNB1 102a sends a paging message to UE 101 to trigger an RRC connection restart. However, in this case, eNB-1 102a does not receive any response to this paging message, and thus eNB-1 102a may conclude that UE 101 is no longer located in the cell under its control. In order to contact the UE 101 that may be located in a cell under different eNBs 102b,...n, eNB-1 102a must upgrade the paging, which means that it must trigger the MME 103b to send a paging request to the other eNBs 102b, ... n to page the UE 101 UE 101 within the currently registered TA. In this example scenario in Figure 20, the upgrade causes eNB-2 102b to send a page and this is successfully received by UE 101.

7. The UE 101 sends an RRC Connection Restart Request to the eNB-2 102b. As an alternative step 7, the UE 101 may be able to determine that the restart attempt on this cell will not be successful before transmitting the RRC Connection Restart Request to the eNB-2 102b. For example, the UE 101 may be able to determine this from the cell ID of the cell, or the eNB ID of the cell or some additional indicator that may be sent in the paging message. If the UE 101 does determine that the restart will not be successful, the UE 101 does not transmit the RRC Connection Restart Request and jumps directly to step 9.

8. Due to the fact that eNB-2 102b does not have the UE suspending the RRC connection (or cannot successfully suspend the RRC connection from another node) in this situation, eNB-2 102b rejects the response by means of the RRC connection.

9. The UE 101 releases its (suspend) RRC connection and enters the RRC idle mode. The UE 101 then performs a normal RRC connection setup procedure to set up a new RRC connection and continue user plane activity.

Case scenario 2

21 shows a message sequence diagram showing possible handling of RRC connection suspension and later restart between UE 101 and RAN 102 in accordance with the above description of Alternative B and Mobility Alternative A, where UE 101 is initially Moving to outside the cell where the RRC connection is active (and may have been reselected many times) but when the data activity will reply, the UE 101 is again camped on the cell where the RRC connection is suspended and thus it can be successfully restarted.

According to the suspension alternative B (informing the CN RRC suspension) and the mobility alternative A (not informing the network mobility), if the UE 101 reselects a cell (or several cells) that is far from the suspension of the RRC connection, the UE 101 does not perform the notification. Any signalling of the network (unless reselection causes the UE to cross the TA boundary so that a "normal" TAU is required). Therefore, when the DL data arrives, the network does not know the cell currently located by the UE, and therefore does not know whether any suspension of the RRC message is valid.

The steps of the sequence are:

1. The UE 101 is initially in an RRC connection and the user plane bearer is established such that user data is likely to be transferred between the UE 101 and the S-GW 103a and then continues to be transmitted to the P-GW 103c (not shown in Figure 21). And further afield.

2. Compliance with the criteria for triggering abort and eNB-1 102a decides to change UE 101 to UE control mobility and suspend RRC connection.

3. The eNB-1 102a sends a message indicating that the UE 101 enters the UE control mobility and suspends the RRC connection to the UE 101. For example, this message can be referred to as shown in FIG. The RRC connection is aborted, or may be referred to as an RRC UE Control Action Command, or some other suitable name.

4. eNB-1 102a and UE 101 suspend the RRC connection. The UE 101 performs UE control mobility similar to the UE control mobility of the idle mode.

5. eNB-1 102a informs CN 103 (MME 103b or S-GW 103a or both) about RRC suspension. The message informing CN 103 can be referred to as the S1 user plane abort. When receiving this message by CN 103, the S1 user plane bearer remains established but terminated (user plane transmission is stopped) and S-GW 103a will not immediately use S1 when receiving downlink user plane data. The plane forwards the data towards eNB-1 102a and will instead buffer the data to shelve its delivery. The S1 user plane suspension may only affect the manner in which the S-GW 103a is to access the DL user profile of the S-GW 103a. Therefore, in this case, it can be considered as only the DL S1 user plane abort.

6. Cell reselection may occur when the UE 101 has suspended the RRC connection and entered the UE control mobility. As long as the UE 101 remains within the registered TA, such reselection does not trigger any signaling towards the network (i.e., the network is not aware of the reselection). Steps 1 through 6 (except for cell reselection) are shown in Figure 21 with a rectangle above the rounded end.

7. In the case of network origination, user plane data arrives at S-GW 103a for data transfer initiated by UE 101. Due to the S1 user plane abort, this user plane profile is buffered at S-GW 103a and not immediately forwarded to eNB-1 102a at the S1 user plane interface. The S-GW 103a then initiates a paging procedure to contact the UE 101 in whichever cell it can locate. This is quite similar (or the same) to the paging procedure used by the UE 101 when it is idle. The paging indication is sent from the S-GW 103a to the MME 103b and to one or more eNBs 102a, b...n located within the TA registered by the UE 101. The receipt of the paging message in the UE 101 triggers the UE 101 to attempt an RRC connection restart. This is shown in the rectangle below the rounded end. In the UE origin condition, the elements in the lower rectangle do not occur and the user data arrives at the UE 101 directly triggers the UE 101 to attempt an RRC connection restart.

8. The remainder of the steps in FIG. 21 indicates that the UE 101 attempts to RRC connection re-establishment on the cell in which the associated eNB-1 102a does have the UE suspend RRC connection (ie, the eNB does have stored UE message information). The sequence of events at startup. The cell may be a cell in which the UE 101 is located when the RRC connection is aborted or it may be another cell controlled by the same eNB-1 102a or it may be a cell controlled by another eNB, but the other eNB owns (or can Capture the necessary RRC message data for the UE. The UE 101 transmits an RRC Connection Restart Request to the eNB-1 102a.

9. Due to the fact that eNB-1 102a does have the UE aborting the RRC connection in this situation, eNB-1 102a restarts the response by means of the RRC connection. If eNB-1 102a wishes to change any part of the previously aborted configuration, this message may contain some new or updated parameter values, or it may be an extremely simple "continue" message (eg, without any parameters or configuration) Update).

10. The UE 101 responds by completing the RRC connection restart. This is an optional step and is only required if eNB-1 102a requires an additional guarantee that the RRC connection restart has succeeded. In the case of the origin of the UE, the uplink user profile from the UE can be started as long as the RRC connection restart is received.

11. eNB-1 102a informs CN 103 (MME 103b or SGW 103a or both) that the S1 user plane can continue. This can be an explicit message as shown in FIG. Alternatively, in the case of UE origination, and in the case where only the DL of S1 is initially suspended, the uplink user profile from the UE 101 transmitted from the eNB-1 102a to the S-GW 103a may be regarded as implicit by the SGW 103a. Continue with the order.

12. Upon receiving the indication to continue the S1 user plane, the S-GW 103a will stop buffering the downlink user plane data and will forward the downlink user plane data to the eNB via the restarted S1 user plane. -1 102a for transmission to the UE 101.

Case scenario 3

Figure 22 shows the termination of the RRC connection between the UE 101 and the RAN 102 and later on A sequence diagram of newly launched possible dispositions. According to the above description, the alternative A and the mobile alternative B, when the UE 101 moves outside the cell in which the RRC connection is active, the CN 103 RRC suspension is not informed, but the UE 101 does inform the CN 103.

In summary, this shows that when the UE 101 moves to a cell where the suspension of the RRC connection is active, and via the mobility update message, the CN 103 is informed about the method of moving to the out of the suspended cell such that S1 is then aborted. When the DL data arrives at the paging 101 of the UE 101, the RRC connection is suspended in the cell and is therefore released and a new RRC connection is established for the data to be delivered.

In this case, the CN 103 initially does not know that the UE's RRC connection has been aborted. However, the validity indicator for each connected mode UE 101 can still be maintained in the CN 103. This indicator can be set based on location update information known to the CN 103 (e.g., MME 103b). In the connected mode, the CN 103 expects the UE 101 mobility event (e.g., to another cell or eNB 102b, ... n) to cause the S1-U and S1-MME to carry the corresponding handover to the eNB. Only tracking area updates from idle mode UEs are expected. When the validity criteria are met, the CN 103 continues to behave normally for the connected mode UE 101.

Using a mobile alternative B means that the UE 101 with the abort RRC connection (and the CN 103 may or may not be aware of this) may perform an autonomous mobile procedure and may be configured to suspend the RRC connection upon it leaves or re-enters A tracking area update (or other location update) message is sent to the CN 103 (e.g., MME 103b) in the case of a valid cell (or group of cells).

If the CN 103 is not informed at the time of the suspension, the MME 103b initially believes that the UE 101 is still RRC connected (i.e., not aborted) unless otherwise known. If the UE 101 is configured to transmit an additional/extended mobility message (e.g., TAU) of the mobility alternative B upon abort, the MME 103b may then infer from the receipt of the TAU that the RRC connection of the UE has actually been aborted and the UE 101 Currently camped on a cell (or cell group) where the suspension of the RRC connection is invalid. Therefore, the MME 103b is simultaneously and indirectly informed that the UE's RRC connection has been suspended and Currently invalid. It will thus be appreciated that signaling of additional/amplified mobility messages by the UE 101 may also serve as a message to inform the CN nodes (such as MME 103b and SGW 103a) of previous RRC suspensions.

In this case, the CN 103 (e.g., MME 103b) may choose to subsequently suspend the S1 connection. The MME 103b may optionally restart S1 if it receives a further TAU or mobility message from the UE 101 indicating that the UE 101 has re-entered the cell (or cell group) in which the RRC connection is once again active.

In this example scenario 3, many different sub-cases are possible, depending on whether the data activity causing the RRC connection is network origin or UE origin, and whether the RRC connection is still valid at the time when the restart is required. . These different sub-cases affect the manner in which the wireless communication system handles the processing of replying Uu user plane communications. Referring to Figure 22, the following describes the processing that occurs when the data activity is of network origin and the RRC connection is suspended at the time when the restart is required. The processing for other sub-cases can be derived using a logical combination of the processing steps previously described and is within the scope of the present invention.

1. During the RRC Connection Abort (shown in the upper rounding rectangle), eNB-1 102a does not inform CN 103 that RRC is suspended and that the S1 connection is maintained.

2. The UE 101 reselects the cell assigned to the eNB-2 102b to the RRC Connection Invalid.

3. The UE 101 may send an "enhanced" mobility message to the MME 103b (middle rectangle) via a temporary RRC connection with the eNB-2 102b, or via other means that does not require a temporary RRC connection with the eNB2 102b.

4. Upon receiving the mobile message, the MME 103b transmits a message aborting the existing S1 connection between the SGW 103a and the eNB1 102a to the S-GW 103a. Therefore, the MME 103b and the S-GW 103a have implicitly informed that the RRC connection that was previously suspended for the UE 101 and the suspension is currently invalid.

5. The data addressed to the UE 101 arrives at the PGW 103c from the external network 104 (not shown in Figure 22) In the picture).

6. The data is forwarded to the SGW 103a of the UE via the established S5/8 bearer

7. The SGW 103a and the MME 103b recognize that the RRC connection for this UE 101 has been aborted and that the data cannot be forwarded via the (suspended) S1-U connection. Therefore, the data is temporarily buffered by the SGW 103a.

8. The CN 103 (e.g., the MME 103b) checks the area storage validity status for suspending the RRC connection. For example, this may involve examining a location validity indicator or a timer based validity indicator as previously described.

9. The CN 103 (e.g., the MME 103b) determines that the suspended RRC connection is invalid.

10. The MME 103b invokes the normal idle mode RRC connection setup procedure:

a. The MME 103b sends a paging request to the eNBs 102a, b...n within the currently known tracking area location of the UE 101.

b. The eNBs 102a, b...n transmit paging messages within the cell under their control upon receiving the paging request. The paging message identifies the UE 101 that the eNB 102a, b...n is attempting to contact.

c. The UE 101 responds to the paging in the cell in which it is currently camped. The UE 101 responds to the paging in a normal manner by initiating a normal RRC connection setup procedure.

d. eNB-2 102b (in conjunction with MME 103b) establishes a new RRC connection with UE 101 and the S1-U and S1-MME bearers are established between eNB2 102b and SGW 103a and MME 103b, respectively.

11. The data is transmitted from the SGW 103a to the eNB-2 102b via the newly established S1-U (note that the previously stored and suspended S1-U can be released)

12. The user profile is communicated from the eNB-2 102b to the UE via Uu.

Example case 4

23 shows a message sequence diagram showing possible handling of an RRC connection suspension between UE 101 and RAN 102. In this example, the abort is requested by the UE 101 and accepted by the network. In this example, it is also contemplated in step 10 that the eNB 102a sends the connection information to the other. The possibility of an eNB (not shown).

Referring to Figure 23, the following describes the processing that occurs when the abort request is made by the UE 101:

1. Initially assume that the UE is in the RRC_CONNECTED state, where security is initiated.

2. The UE detects compliance with the RRC Connection Abort criteria (eg, at a higher layer, NAS or AS (eg, RRC), based on input from a user plane entity or application entity or based on an inactivity timer expires)

3. The UE RRC sends the newly proposed message RRC Connection Abort Request (other message names can be used but the message has the same intent) to the eNB. In an alternate embodiment, the UE signals the request message using a MAC CE (Control Element).

4. Suspension of the RRC connection is acceptable to the eNB, which is determined by the following conditions:

a. The eNB independently maintains compliance with the suspension criteria. This criterion can be based on aspects such as, but not limited to, the following:

‧ Communication activities and trends related to each UE and/or based on the traffic characteristics of each radio bearer or application supported by the UE.

• Alternative or additional use of the device, application, operation of the application at the UE or the type of traffic therein, eNB, S-GW, MME or any other associated entity within the system.

And/or

b. The eNB requests (and receives) one-time or periodic feedback from the MME/S-GW regarding:

i. When the S1-U connection for the UE is established between the S-GW and the eNB, the eNB may request a periodic or threshold-based traffic activity report for the UE from the S-GW. The S-GW may then provide reports to the eNB periodically or based on the threshold. Each report can be used for a particular UE or group for a UE, requiring reporting for groups of UEs or UEs. The traffic activity report can contain images like Details of data volume and trend, active/inactive time period statistics, and traffic predictions associated with each UE or other related entity, such as each radio bearer or application supported by the UE.

Ii. Or the S-GW may autonomously transmit a periodic or threshold-based report for each UE with an S1-U connection to the eNB at a specified rate.

Iii. Or when the criteria maintained by the eNB for the UE are met, the eNB may request a one-time traffic activity report from the S-GW and make a suspension decision after evaluating the report from the S-GW.

5. The eNB prepares the source RAN to the target RAN container as if it would be done for intra-RAT handover in order to establish RRC parameters for storage for UE RRC connection abort

6. The eNB stores such containers with appropriate UE identification codes as appropriate, so that they can be retrieved when needed

7. The eNB sends the prepared container with this additional UE ID (and or the indication for the use of the RRC Connection Abort) to the MME, as appropriate, in a manner similar to that that would be performed during the handover preparation phase via S1. [2]. These may be sent in the newly proposed explicit message "UE Message Abort Request" along with the eNB and MME UE ID that uniquely identifies the UE.

a. The eNB may alternatively use one of the existing S1 messages with special information elements (IEs) for handover preparation to indicate that the purpose of the message is for the UE RRC connection suspension.

8. The MME storage container along with the attached UE identification code. The MME deletes the user plane work phase at the S-GW or suspends the user plane work phase. S-GW responds to MME accordingly

9. The MME responds to the eNB by aborting the UE message.

10. The eNB optionally prepares all eNBs in the vicinity or all eNBs in the tracking area via the X2 interface via the X2 interface. This is similar to the existing procedure defined in [3] for X2 handover. Or, for example, by additionally including a UE identification code or display container for The UE abort indicator may define a new X2 message or may modify an existing message for handoff for aborting purposes.

This step enables the neighboring eNB to be prepared for fast re-establishment of the UE RRC message if the UE moves into the coverage area of the neighboring eNB. During this preparation phase, the proposed eNB should also have a Stop Validity Maximum Timer (proposed in Section 6.1.6) so that it can delete the stored UE message when the timer expires.

11. The eNB transmits the newly proposed "RRC Connection Abort" message to the UE and releases the UE RRC radio resource after receiving the lower layer L2 RLC Answer from the UE.

12. The UE receives the connection abort message and backs up and stores the same AS configuration as an eNB including the security configuration and releases the RRC connection state resource and entity. The UE considers itself to be in the RRC_SUSPENDED state and configures its RRC protocol (but with the stored RRC message) as in RRC_IDLE and follows the RRC_IDLE procedure including monitoring the appearance of the paging and using the UE-based mobility procedure. In the modified embodiment proposed herein, the paging cycle used by the UE in RRC_SUSPENDED may be different from the paging cycle of RRC_IDLE. This can be ensured, for example, by using a shorter paging appearance time to ensure that the UE detects the paging of the user plane data earlier, in order to comply with the application QoS for the delivery latency of such packets.

13. In an alternate embodiment, the UE will transmit a flag in the UE Capability Message (described in 3GPP TS 36.331) indicating that the UE prefers the RRC connection to be released in the event that the eNB chooses not to suspend the RRC connection. If this situation is acceptable to the eNB, the UE may then follow the RRC Connection Release procedure (refer to Section 3.3.8 of TS 36.331) instead of suspending the RRC connection by the RRC Connection Abort procedure or leaving the UE with some of its RRC messages or All behave as if it were in RRC idle or as if it were not in the RRC connection.

Case scenario 5

24 shows a message sequence diagram showing possible handling of an RRC connection between UE 101 and RAN 102 for a suspension request by UE 101. In this example, the suspension is not connected by the network. The network decides to keep the UE in connected mode.

Referring to Fig. 24, the following describes the processing that occurs when the suspension request is made by the UE 101.

1. Initially assume that the UE is in the RRC_CONNECTED state, where security is initiated.

2. The UE detects compliance with the RRC Connection Abort criteria (eg, at a higher layer, NAS or AS (eg, RRC), based on input from the user plane entity and the application entity or based on an inactivity timer)

3. The UE RRC sends the newly proposed message RRC Connection Abort Request (other message names can be used but the message has the same intent) to the eNB. In an alternate embodiment, the UE signals the request message using a MAC CE (Control Element).

4. The eNB does not accept the suspension of the RRC connection. This can be derived from one or more of the following reasons:

a. The eNB independently maintains non-compliance with the suspension criteria (as described for step 4a in Section 6.1.1);

b. The eNB requests (and receives) one-time or periodic traffic report feedback from the MME/S-GW.

5. The eNB sends an RRC connection abort reject message.

a. Depending on the situation, the eNB may indicate to the UE a back or disable timer so that the UE should not attempt to abort the request while the timer is running.

b. In an alternative embodiment, the eNB does not send a response message to the UE, in which case the UE may have a hard coded backoff or disable timer that prevents further transmission of the RRC Connection Abort request during runtime

6. The UE continues to remain in the RRC_CONNECTED state.

Example case 6

25 shows that the RRC connection between the UE 101 and the RAN 102 is performed by the UE 101. Sequence diagram of the message of possible disposition of the abort request. In this example, the suspension is not accepted by the network and the network decides to transition the UE to idle mode.

Referring to Fig. 25, the following describes the processing that occurs when the suspension request is made by the UE 101.

1. Initially assume that the UE is in the RRC_CONNECTED state, where security is initiated.

2. The UE detects compliance with the RRC Connection Abort criteria (eg, at a higher layer, NAS or AS (eg, RRC), based on input from the user plane entity and the application entity or based on an inactivity timer)

3. The UE RRC sends a newly proposed message RRC Connection Abort Request to the eNB. In an alternate embodiment, the UE signals the request message using a MAC CE (Control Element).

4. The eNB does not accept the suspension of the RRC connection and instead the eNB chooses to release the RRC connection, which may be derived for one or more of the following reasons: a. the eNB independently maintains the compliance release criteria; b. the eNB from the MME/S - GW requests and obtains one-time or periodic traffic report feedback; c. eNB determines that it does not want the UE to go to RRC_SUSPENDED, for example due to upcoming DL user plane data transmission or by internal radio resource management (RRM) policy; and d. eNB does not support functionality and has a policy of releasing the RRC connection when receiving an incomprehensible message from the UE.

5. The eNB sends an RRC connection release message.

6. The UE receives the message and leaves the RRC_CONNECTED state to move to the RRC_IDLE state.

Example case 7

Figure 26 shows an RRC connection between the UE 101 and the RAN 102. A sequence of messages that may be dispositioned for a pending request. In this example, UE 101 agrees to abort the connection.

Referring to Fig. 26, the following describes the processing that occurs when the suspension request is made by the UE 101.

1. Initially assume that the UE is in the RRC_CONNECTED state, where security is initiated.

2. The eNB detects compliance with the RRC Connection Abort criteria, which can be derived, for example, for the following reasons:

a. The eNB independently maintains compliance with the suspension criteria and/or

b. The eNB requests (and receives) one-time or periodic feedback from the MME/S-GW.

3. The eNB prepares the source RAN to the target RAN container as it would be for intra-RAT handover

4. The eNB will store such containers with appropriate UE identification codes as appropriate so that they can be retrieved when needed

5. The eNB sends the prepared container to the MME as appropriate, in a manner similar to that that would be performed during the handover preparation phase via S1. These may be sent in the newly proposed explicit message "UE Message Abort Request" along with the eNB and MME UE ID that uniquely identifies the UE.

a. The eNB may alternatively use one of the existing S1 messages with special IE for handover preparation to indicate that the purpose is for the UE RRC connection suspension.

6. The MME storage container along with the attached UE identification code. The MME deletes the user plane work phase at the S-GW or suspends the user plane work phase. The S-GW sends a response to the MME accordingly.

7. The MME responds to the eNB by aborting the UE message.

8. The eNB 102a optionally prepares all eNBs in the vicinity or all eNBs in the tracking area via the X2 interface via the X2 interface. This is similar to the existing process for X2 handover preparation. sequence. Alternatively, a new X2 message may be defined or an existing message for the delivery sequence may be modified for aborting purposes. During this preparation phase, the proposed eNB should also have a Stop Validity Maximum Timer (proposed in Section 6.1.6) so that it can delete the stored UE message when the timer expires.

9. The eNB sends the newly proposed "RRC Connection Abort" message to the UE and releases the UE message from the connected state after receiving the lower layer L2 RLC response from the UE.

10. The UE receives the RRC Connection Abort message and checks that it is willing to suspend the RRC connection based on its internal criteria. The UE backs up and stores the same AS configuration as an eNB including the security configuration and releases the RRC connection state resources and entities. The UE considers itself to be in the RRC_SUSPENDED state and configures its RRC protocol (but with the stored RRC message) as in RRC_IDLE and follows the RRC_IDLE procedure including monitoring the appearance of the paging and using the UE-based mobility procedure.

In the modified embodiment proposed herein, the paging cycle used by the UE in RRC_SUSPENDED may be different from the paging cycle of RRC_IDLE. This can, for example, ensure that the UE detects the paging of the user plane data earlier by using the shorter paging appearance time in order to comply with the application QoS for the delivery latency of such packets.

11. In an alternative embodiment proposed herein, a scenario is envisioned in which the UE prefers RRC Connection Release in the event that the RRC connection initiated by the eNB is aborted. It is proposed that the UE will transmit a flag in the UE capability, which indicates that if the network side complies with the suspension criterion, the UE prefers the RRC connection to be suspended or released. The eNB will then suspend/release the RRC connection accordingly.

Example case 8

One of the possible alternatives for Case 7 would be that when receiving an RRC Connection Abort message from the eNB, the UE does not want to comply with the eNB signal and instead decides to release the existing RRC connection and go to RRC_IDLE. This requires additional signaling between the UE and the eNB in the form of a subsequent "RRC Connection Release Request" or "RRC Connection Release Indication". Alternatively, the UE may send an RRC Connection Abort Confirmation message with an additional indicator to indicate a transition to RRC_IDLE and Release of the RRC connection. An alternate embodiment would transmit a flag for the UE in the UE Capability message indicating that the UE prefers the RRC connection to be aborted or released if the network side complies with the suspension criteria. The eNB will then suspend/release the connection accordingly (as shown in Figure 26).

A further alternative to receiving an RRC Connection Abort message from the eNB is that the UE decides that it wants to stay in the RRC connection. This UE-based response to the network initiated RRC connection suspension is considered possible, but does not comply with the system principles of the usual application of network directed control (ie, the alternative procedure instead allows the UE itself to determine the RRC state decision). The final result).

Although the UE 101 indicates its preference for RRC connection suspension or release or as a flag in the UE capability message or some other form of indicator in the RRC Connection Release Request message, the eNB 102a does not have to follow this request. The eNB 102a may choose to ignore the request and alternatively select another action.

Example case 9

In an embodiment, the proposed MME acts as an anchor for RRC connection abort, and the registered Tracking Area (TA) or Tracking Area (TA) group acts as a boundary for aborting validity. Within the validity area, the UE will treat the suspended RRC connection message as valid and the UE or network may initiate a restart. However, other areas of validity may be possible. These other areas of validity may be explicitly configured by the eNB or other network entity before the RRC connection is aborted or at the time the RRC connection is aborted, or may be additionally signaled to inform the UE about the parameters of the validity area (eg, cell) Group global ID).

The reason for selecting a registered TA (or several TAs) as a suspension validity area can be multiple:

a. Any signaling related to the RRC Connection Suspension Resume/Response/Release may be combined with any tracking area update that occurs at the TA boundary anyway. Additional new or existing RRC messages may be carried by modifying existing messages involved in the TAU procedure to carry additional signaling or may be via the same RRC connection established for TAU purposes.

b. The concept of TA has been defined in existing specifications and therefore the effectiveness of TA is used at this time. No additional specifications are required for area definition. Other validity boundaries may result in some increase in the air signal at the boundary of the validity region. This is in addition to signaling the mandatory TAU that occurs at the TA boundary anyway.

c. The TAU procedure involves the UE, the eNB and the MME and will therefore facilitate the reconfiguration of the security configuration and other UE configurations (eg, measurement configuration, dedicated configuration) at all relevant entities, thus making it easy to base on New configuration and continue to abort at the end of TAU

i. Library security for deriving access layer integrity protection and encryption is based on Kenb derived at the UE and MME and varying with the eNB. Each time there is a connection state cell change (due to handover or re-establishment or as proposed for the abort reply), the key for the new eNB needs to be derived. The new key will depend not only on the new eNB but also on the source eNB and the Kenb on the network link counter. Therefore, the UE cannot reply to the connection on any eNB simply by reusing the security message at the time of suspension. Alternatively, the security message must be renewed in the UE and the network entity. Therefore, the re-newing of the security message (if the new connection is established, the new AS security message or the modified AS security message if the connection is re-established) will allow further implementation with a lower signaling burden. Connect to reply.

In order to avoid having a UE with aborted connection requesting a restart too quickly, it is also proposed to have an optional suppression timer (such as a "minimum abort timer") that should be adhered to once the UE aborts the RRC connection. When the timer is running, it prevents the UE from initiating a restart of the aborted connection. This parameter may be specified by the eNB based on each UE or for all UEs in the UE-specific signaling by transmitting the co-signal in the system broadcast message. Or this timer should be configured by the eNB semi-statically (altime) via an existing message or a new RRC information element (IE) within the new RRC message, the value of which may be dependent on the time of the suspension. The QoS delay requirement for the working phase. However, the UE does not need to consider this timer in all cases, for example, the timer can be changed when an emergency call is initiated.

In a similar manner, an optional maximum timer can be specified, after which the aborted connection stops being active. When the timer expires, the UE and/or the eNB may delete the stored UE message. And the connection that is considered to be suspended is released, and the UE is in the normal RRC idle mode.

The UE may indicate its support for connection suspension in the UE capability message transmitted from the UE to the network, and the network will indicate its support for connection suspension in the broadcast system information.

S1-U behavior

In the case of the UE origination and the RRC suspension procedure of the eNB origin, the MME may request the S-GW to suspend or delete the S1-U for the UE between the S-GW and the Serving eNB. Under these conditions, the downlink traffic to the UE will be buffered at the S-GW, which will then have to request the MME to page the UE. In response to the paging, once the UE contacts the MME, it will then have to create or reply to the S1-U session for the UE between the S-GW and the current Serving eNB.

If the MME is responsible for paging the UE, it will likely need to page the UE in all cells belonging to the registered tracking area of the UE. This generally increases the paging load of the system. In order to manage the paging load, there are several schemes known to the experts of the field, such as: - Shortest distance first scheme (MME first paging in the last known eNB location of the UE, and if the MME is not elicited from the UE The response will be paged to other locations), - paging in sequence (each time paging UEs in different subsets of the eNB).

Two solutions for managing the paging load of the system are proposed here.

In the first solution, the MME stores an identification code of the eNB that informs the UE of the message suspension. As previously proposed, the S1-U session will then be aborted or deleted. If the need for paging the UE occurs, the MME may take the shortest distance first paging scheme by using the stored eNB identification code as the last known location of the UE. If this is a response from the UE, it will protect the MME from performing blanket paging for the UE in all cells of the TA.

In the second solution, it is proposed that the MME should keep the S1-U working phase of the UE between the S-GW and the eNB active at the time of the RRC connection suspension. In this case, the downlink user profile arrives at the eNB where the RRC connection was initially suspended. When the downlink data arrives, the eNB then pages the UE, thus reducing the system paging load. If the eNB does not receive Any response for paging, which in turn can escalate the paging request to the MME, the MME will then page the UE across all other eNBs.

Mobile program

When the UE's RRC connection is aborted, the UE may perform an action procedure as if it were an idle mode UE. For cell reselection within the validity region, the UE may need to perform any additional signaling until the UE, eNB, or MME wishes to reply (or restart or re-establish) the RRC connection.

The terms new MME and new eNB are used herein to indicate the MME and eNB that the UE with the suspended RRC message initiates signaling for mobility purposes or for RRC connection restart purposes, respectively. These new MMEs and new eNBs may be the same as the MME or eNB of the serving UE when the RRC connection is suspended or may be different eNBs and/or MMEs.

If the UE 101 finds itself outside the abort validity zone boundary (eg, one or more TAs), the UE should perform the tracking zone update in accordance with existing specifications. A representative situation is depicted in FIG. The details of the possible actions of the above sequence are as follows:

1. The UE 101 has an active suspension of the RRC connection (eg, the UE is located in the TA where the RRC connection is aborted) and follows the idle state mobility procedure.

2. Due to its mobility, the UE detects that it is on the cell where the TAU procedure needs to be performed. The UE also detects that the suspended RRC connection is no longer valid and therefore invalidates the stored RRC message regionally.

3. The UE 101 sends an RRC Connection Request by signaling the origin of the action (MO).

4. The eNB 102b sends an RRC Connection Setup to establish a Signaled Radio Bearer (SRB1)

5. The UE 101 sends an RRC Connection Setup Complete message containing the initial NAS message. In this case, the initial NAS message will be a TAU request.

a. Depending on the situation, a flag such as "RRC Connection Abort Status" indicating that the UE previously had aborted connection may also be included. This flag can be added as an RRC signaling (eg, RRC) The portion of the connection setup is completed or is part of the NAS signaling (eg, TAU).

b. Depending on the situation, in conjunction with or instead of the IE "RRC Connection Abort Status", the UE may include another flag such as "RRC Suspension Continue" indicating that it is necessary to remain suspended after the TAU. The eNB may initiate the abort procedure accordingly.

6. The eNB 102b forwards the "RRC Connection Abort Status" to the new MME 103d as requested by the TAU.

a. If the new eNB 102b wishes to retrieve the suspended RRC configuration from the old MME 103a, the new eNB 102b will include the abort state. This aborted RRC configuration can help the new eNB minimize over-the-air (OTA) signaling by transmitting only the differential configuration to the UE.

b. If the new eNB 102b wishes to provide the UE with a completely new RRC configuration that is unrelated to the previously suspended configuration, the new eNB 102b will not include the abort state.

7. In the normal TAU condition, the new MME 103d retrieves the UE message from the old MME 103b using the UE message request message.

a. If received from the UE, the new eNB 102b may send a corresponding "RRC Connection Abort Status" flag, which will be added to the UE message request as the case may be sent from the new MME 103d to the old MME 103b.

8. The old MME retrieves the UE message as requested by the new MME. If the "RRC Connection Abort Status" flag indicates a previously suspended RRC connection, the old MME will also retrieve the stored containers available to the UE. The old MME 103b will indicate to the old S-GW (not shown) that the S1-U session of the UE 101 was deleted after the expiration of the protection timer or when the acknowledgment from the location of the UE from the HSS has changed. At the time of the deletion confirmation from the old S-GW, the UE message at the old MME 103b will be deleted.

9. The old MME 103b provides the aborted UE message and provides the container to the new MME 103d as part of the "UE message response" as appropriate.

a. The existing "UE Message Response" message (as used during TAU) must be extended to accommodate the optional container of the new proposal related to the previously suspended RRC connection.

10. The new MME performs NAS level authentication and security procedures as appropriate.

11. The new eNB 102b creates a UE session with the new S-GW 103c using the "Create Work Order Request" message. If there is no change in the S-GW, the existing work phase will be modified instead.

12. New S-GW 103c response session creation

13. The new MME 103d provides the new eNB 102b with an optional container for TAU acceptance and new offer received from the old MME. The MME also provides the security configuration required to derive the keys for the AS security program. The bearer setup request may also be sent by the new MME to the new eNB as needed, so that the new eNB needs to set up the user plane data bearer for the UE.

14. The new eNB performs the AS security initiation procedure by the UE.

15. The eNB decodes the container containing the abort configuration as appropriate and will infer the need to issue a new differential reconfiguration to the UE.

a. Depending on the situation, the eNB may ignore the abort configuration and independently export a new configuration that needs to be sent to the UE.

16. The eNB transmits an RRC reconfiguration message containing the measurement configuration and the dedicated radio resource configuration to the UE. TAU accepts can be piggybacked on this message

a. Depending on the situation, the eNB may re-configure the RRC regionally and perform the remaining TAU procedure on SRB1 itself.

b. Optionally, the eNB may include the new proposed flag in the RRC Reconfiguration message to indicate whether the provided configuration is "Full Configuration" or "Differential Configuration". Therefore, the UE can understand whether it should delete the abort configuration or reuse the abort configuration (along with differential update) to derive the new configuration.

c. Optionally, the mandatory preset behavior for the received configuration from the eNB should be considered a full configuration or a differential configuration, as appropriate.

17. The UE applies the received configuration and sends an RRC Connection Reconfiguration Complete message to the eNB.

18. The UE sends a TAU Complete message to the eNB, and the TAU Complete message is forwarded to the new MME.

19. From this point forward, the RRC connection can be suspended again based on the abort procedure described above. For example, the eNB may initiate abort based on the "RRC Abort Continuation" flag provided in step 5 above.

Example case 10

The RRC connection restart initiated by the UE in the validity area (autonomously or in response to the reception of the paging signal for downlink data) may be achieved by re-establishing the signaling by the RRC connection. The RRC re-establishment signaling procedure is currently defined for E-UTRAN for promptly replying to the RRC connection and restarting AS security in the event of a handover error or radio link error (RLF). The re-establishment procedure allows a cell with a prepared UE RRC connection profile or RRC message (the UE message is provided by the previous serving eNB via the X2 interface) to reply to the signalling in the UE and the dedicated radio bearer based on its previously configured UE message ( SRB and DRB). Prior to the reply, SRB, DRB, measurement configuration and security configuration were also possible by re-establishing the program by modification of the new eNB.

Since the RRC connection re-establishment procedure does not involve signaling via the NAS level in the air and restarting the signal depending on the situation, it is much lighter than the conventional idle-to-connect mode transition in terms of the required signaling. Other advantages eNBs that reply to the connection on it can use the optionality of each field and thus minimize the size of the airborne signal during the re-establishment procedure and the radio resource configuration.

Referring to Figure 28, in order to extend this procedure for RRC Connection Reply, the following enhancements are required.

1. At the time of the RRC connection suspension, the Serving eNB

a. storing a full backup of the container that was sent to the MME along with the corresponding eNB and MME identification code associated with the UE at the time of the suspension, or

b. Store the eNB and MME identification codes of the UE, so that the suspension state and the eNB and the MME are recognized. The alias is associated and the actual container is forwarded to the MME along with the UE's eNB and MME identification code.

2. The Serving eNB may optionally prepare some nearby eNBs (eg, for X2 handover status) by means of UE messages and any other information required for re-establishment of connections on any of their eNBs. Or possibly all eNBs under the MME (or within the validity area such as the Tracking Area (TA)). The "abort indicator" flag is prepared to be marked to indicate to the target eNB that the RRC connection is actually ready for suspension.

3. Optionally, the X2 interface protocol may be enhanced such that based on the old eNB credentials provided in the "RRC Connection Re-establishment Request", the new eNB will be able to identify and query the old eNB to obtain the UE message. If available, the old eNB may provide UE messages to the new eNB in a similar manner as used during X2 handover preparation. Alternatively, the old eNB may be able to query the MME to obtain the UE message as it was done during the TAU using the UE identity code and the abort indicator. The new eNB may indicate to the old eNB this RRC connection for suspension.

The details of the possible actions in re-establishing the sequence of programs for the purpose of connection restart are as follows:

1. Initially the UE determines that the terminated RRC connection is valid.

2. The UE detects the need to reply to the RRC connection due to the data leaving the arrival of the uplink transmission or receiving a paging from the network.

3. On its current cell in the validity zone, the UE sends an RRC Connection Re-establishment Request with a new IE indicating a new cause of restart or an RRC connection or message restart that indicates suspension. The request message structure (3GPP TS 36.331) is re-established as usual, which may include some or all of the details. The details of the C-RNTI and the source entity cell identification code shall be details relating to the cell/eNB in which the RRC connection was initially suspended. The short MAC-I derivation is in accordance with the general procedure (refer to section 5.3.7.4 of 3GPP TS 36.331), however the parameters relating to the cell/eNB in which the RRC connection was initially suspended are used.

4. The new eNB will re-establish the cause detection as "restart" (or the RRC connection re-establishment request message includes a new IE that restarts the RRC connection requesting suspension)

a. it has a stored UE message available (the new eNB 102b may be the same as the old eNB that was initially suspended or may be one of the eNBs that have been prepared by the old eNB 102a) or

b. Based on the source cell details provided by the UE, the new eNB 102b can retrieve the aborted UE message from the old eNB 102a using the new or modified message via the X2 interface.

5. The old eNB 102a has the stored UE message available or can retrieve the message from the MME 103b using the stored UE identification code (in the same manner as it was for the S1 handover to retrieve the UE message).

6. The old eNB 102a provides the UE message (the container with the AS configuration containing the suspended RRC message and the AS message containing the information for reestablishing the RRC connection on the new eNB) to the new eNB 102b.

7. The new eNB 102b uses the received information to validate the security message of the UE 101 and sends an RRC Connection Re-establishment message to the UE for SRB1 replies and new security key derivation.

8. The UE replies to SRB1, derives a new security key, and sends an RRC Connection Reestablishment Complete message to the new eNB.

9. The new eNB 102b sets up the UE phase of operation with the MME 103b to follow the S1 path switch, as it would be done under normal RRC connection re-establishment conditions.

a. If the S1-U is deleted earlier, the MME 103b again creates a user plane work phase for the UE with the S-GW 103a or

b. If the S1-GW between the S-GW and the old eNB that originally connected the connection is kept active, the MME promotes the regular S1 path switch.

c. If S1-U is aborted at the time of suspension, the MME may facilitate S1 path switching but have an additional restart indicator for the S-GW

10. The new eNB sets up the SRB2 and DRB configuration and measurement configuration and sends an RRC Connection Reconfiguration message to the UE.

11. The UE receives the received configuration, restarts SRB2 and DRB, and connects the RRC. The reconfiguration is completed and transmitted to the eNB. Thereafter, the UE can perform any user plane data transfer as usual.

As an alternative to the reuse of the re-establishment procedure for restarting the aborted connection, an equivalent procedure can be used, but the equivalent procedure uses a different message or message definition. For example, the new RACH message 3 and message 4 (see 3GPP TS 36.331) may be defined for the purpose of RRC connection restart request and RRC connection restart, respectively, and the RRC connection restart request and the RRC connection restart may be followed. The same principles as the principle of re-establishment.

A further alternative option may be to take a conventional RRC connection setup procedure also within the validity area, thereby following the restart procedure described below (example case 12) in the validity zone change condition.

Example case 11

Figure 29 shows a sequence of information depicting the details of possible actions when a re-establishment procedure fails during a connection restart. The steps of Figure 29 include:

1. Initially UE 101 has an RRC connection with a suspension associated with a cell under the control of old eNB 102a.

2. The UE detects the need to restart the RRC connection due to the arrival of the data shelving uplink transmission or due to receiving a paging from the network.

3. The UE 101 camps on a cell under the control of the new eNB 102b, which is located within the validity area. The UE transmits an RRC Connection Re-establishment Request to the new eNB 102b with a new IE indicating a new cause of "restart" or a new IE indicating the suspension of the RRC connection or message. It may include some or all of the details that will be included in the conventional re-establishment request message structure. The details of the C-RNTI and source entity cell identification code shall be details relating to the cell/eNB 102a to which the RRC connection was initially suspended. Short MAC-I export follows the general procedure. However, parameters related to the cell/eNB 102a that was initially suspended by the RRC connection are used.

4. The new eNB 102b cannot parse the UE identification code to retrieve the prepared message or cannot The identification of the UE message must be extracted from the source eNB.

5. The new eNB 102b refuses to re-establish the request.

6. The UE 101 presets the configuration for the SRB0 application while maintaining the rest of the aborted UE message and starts the RRC connection setup procedure.

7. The UE 101 transmits the RRC Connection Request message identifying the reason for the reply as the case may be transmitted.

8. The new eNB 102b sets up SRB1 for the UE and transmits an RRC Connection Setup message to the UE.

9. The UE configures SRB1 and transmits an RRC Connection Setup Complete message including the initial NAS message (eg, a service request). The UE also includes the UE identifier and associated MME identifier assigned when the RRC connection is aborted.

10. The new eNB 102b requests the designated MME 103b to set up an S1 message for the UE.

11. From the message request, the MME 103b knows that it has stored containers for the RRC message for the UE to suspend and retrieves the containers.

12. The MME 103b switches the S1 path from the old eNB 102a that was initially suspended to the new eNB 102b.

13. If the S1 path switch is not possible, the S1 connection with the old eNB 102a is released and the S1 connection with the new eNB 102b is established.

14. The MME 103b forwards the security message and the stored container for the UE related to the suspended RRC connection.

15. The new eNB 102b can now derive a delta configuration that needs to be signaled to the UE by comparing the known current configuration at the UE with the configuration required by the new eNB 102b. Alternatively, the new eNB 102b may also instruct the UE to discard the abort configuration and adopt a new configuration by setting a "Full Configuration" IE.

16. The new eNB 102b transmits a security mode command to the UE and transmits an RRC Connection Reconfiguration message to the UE, which will result in a restart of the SRB2 and other DRBs at the UE.

Example case 12

The restart is based on the TAU procedure outlined above in the mobile procedure when the validity zone boundary changes. The RRC connection required to perform the TAU procedure can be established after the normal RRC connection setup method.

The advantages of the conventional RRC connection setup procedure are:

a. In any case, start NAS and AS security based on the new MME's library key.

b. Modify the bearer mapping and channel configuration to be suitable for the new MME/new eNB

c. Configuring a new measurement message by configuring a neighboring cell suitable for the new MME/new eNB

So this method of restarting the connection during the TAU procedure includes:

a. invalidate the suspended RRC connection and

b. Establish a new RRC connection via TAU (with new configuration or differential new configuration)

c. Once the ongoing data transfer and signaling is deemed complete, maintain/suspend/release new connections as needed

The details of this method are described above as part of an operational procedure.

However, if the establishment of a new RRC connection is considered to be inefficient at the TA boundary (eg, when the UE moves between TAs), the RRC Connection Re-establishment procedure may need to be modified to be between SRB1 restart and SRB2/DRB restart and Into the NAS to signal. This procedure is similar to the re-establishment procedure described in scenario 11 above, except that in this case the new eNB is connected to a different MME than the MME to which the old eNB is connected. Therefore, during the initial re-establishment, the new eNB will retrieve the UE RRC message from the old MME via the X2 interface (if available) or from the old MME via the new MME. A new signaling message for the message needs to be retrieved between the MMEs and between the eNB and the MME. Once the security of the re-establishment procedure is initiated and the SRB1 restart phase is successful, the rule TAU signal can occur via the reply SRB1. The TAU signal can be used to restart/release/suspend the RRC connection in the same manner as described above at the end of the TAU.

Example situation 13

There are many possible embodiments of the RRC suspension concept. In this case, an embodiment is described in which the goal is to maximize compatibility with existing system programs and signaling messages, and thereby minimize the specification work necessary to integrate the solution into the 3GPP LTE specifications.

The embodiment is based on the following guiding principles:

- The procedure for restarting the suspended RRC message is mainly based on the existing procedure for RRC re-establishment (and it is currently used for recovery from radio link errors)

- The S1 connection is not aborted during Uu abort. This avoids the need for signaling between the radio access network and the core network each time the Uu connection is aborted or replied (i.e., from the CN perspective, the UE remains in the connected mode).

- In case of reselecting another cell when the UE is aborted, the UE always informs the RAN. This avoids that the downlink data arrives at the eNB of the abort cell, but the UE has moved to another cell without notifying the network for paging upgrade (via other eNBs, or via a wide area spanning multiple cells/eNBs) Need. There are two possible variants of this cell location notification:

o) The first alternative is to move the UE to idle and send the TAU via the new cell after reselection. Upon receiving the TAU, the MME is made aware that the UE is currently idle and can initiate the release of S1 to the old cell. If the new data arrives at the UE beyond this point, the new RRC connection (and S1 connection) will be established (after the DL data arrives, after the UE's network paging).

○ ii) A second alternative is to have the UE send a re-establishment request in the new cell after reselection. The eNB of the new cell may then decide to perform operations similar to those used during handover in order to prevent the UE from moving back to the fully idle mode. If the eNB of the new cell is the same as the eNB of the old cell, the UE message information can be easily used in the eNB, so the eNB can complete the re-establishment procedure by the UE without contacting other network nodes. If the eNB of the new cell is different from the eNB of the old cell, the new eNB may attempt to use the existing X2 "delivery handover" procedure ("RLF indication message" of 3GPP TS 36.423) introduced in 3GPP Release 9 of RLF recovery from the old The eNB extracts the UE message and the new eNB can complete the re-establishment procedure by the UE and can The S1 path switch request is initiated to the MME in accordance with the normal handover procedure.

- If the re-establishment procedure fails (when accessing the abort cell or new cell is accessed), or if it is rejected by the network, the UE takes a NAS-based RLF recovery according to the existing procedure and thus returns to the idle and via the currently camped cell Send TAU. This will result in the establishment of a new RRC connection.

In order to implement the above embodiments, the following changes to the specification are required:

1) A new "Abort Request" message can be defined for uplink communications, thereby allowing the UE to request or initiate an RRC connection abort. If the abort is only triggered by the network (no UE input to the decision), the definition of this message is not required. The message may be a new RRC message or may include modifications to existing RRC messages. The message may alternatively be conveyed within the MAC layer (for example) within the MAC Control Element (CE).

2) An "Abort Command" message may be defined for downlink communications to allow the network to command the UE to terminate the current RRC connection. To provide this functionality, existing messages (such as RRC release, or RRC reconfiguration) can be modified, or new messages can be defined. Messages may alternatively be conveyed at the MAC layer, for example, within the MAC CE.

3) Define a new trigger for initiating RRC re-establishment. When the UE's RRC connection is currently aborted, this includes one or more of the following:

a. Receive paging messages from the network (DL data for network origin)

b. New Action Origin (UL) data arrives at the UE

c. Follow the reselection of UEs to any other cell

30 is a message sequence diagram showing an overview of the above steps for RRC connection re-establishment followed by RRC connection re-establishment between the UE 101 and the EUTRAN 102.

1. Initially UE 101 has an active (non-suspended) RRC connection with EUTRAN 102.

2. A trigger is generated at the UE 101 or EUTRAN 102 indicating that the RRC connection will preferably be suspended. This trigger may be generated by a suspension criterion or a criterion met at the UE or EUTRAN, As discussed in the examples above.

3a. If the trigger is generated at the UE, the UE sends a connection abort request message. In this example, the UE uses a new message to the EUTRAN (eg, an RRC Connection Abort Request message). Other new or existing 3GPP messages can also be used for this purpose. If the trigger is generated at EUTRAN, the connection abort request message is not sent by the EU and this step is omitted.

3b. When receiving the RRC Connection Abort Request message by the EUTRAN or if the trigger is generated at the EUTRAN, the EUTRAN sends a Connection Abort Command message to the UE. In this example, the EUTRAN uses a new message to the UE (eg, an RRC Connection Abort Command message). In another example, the EUTRAN may use a modified form of the RRC Connection Reconfiguration message or a modified form of the RRC Release message as the connection abort command message. Under these conditions, the modified RRC Connection Reconfiguration message or the modified RRC Release message will be modified so that the impact at the UE will cause the RRC connection to be aborted rather than reconfigured or released. This modification may, for example, include a new information element (IE) indicating that the purpose is to suspend the RRC connection. For example, the new IE can be marked as "abort RRC connection", "suspend command", "suspension command", "suspend indicator", "suspension indicator" (Suspension) Indicator) or something different. The new IE may be present in the message and the presence of the IE in the message may cause the UE to suspend the RRC connection. Alternatively, the new IE may be a Boolean value and setting the IE to true may cause the UE to suspend the RRC connection. Other new or existing 3GPP messages can also be used for this purpose.

3c. The UE may then send an RRC (L3) response or a MAC (L2) response to the EUTRAN, as appropriate.

4. The RRC connection is then suspended by at least a security message stored at the UE and/or EUTRAN.

5. After the RRC connection has been aborted, the paging reception and mobility procedure at the UE is similar to the procedure used by the UE when the UE is in idle mode (the UE monitors whether the downlink signal has a paging message and performs a UE-based mobility procedure) (eg, cell reselection)).

6. In order to re-establish the suspended RRC connection, the trigger for the abort reply is generated at the UE or EUTRAN. Typically, the trigger is generated at the UE and may be one of: (i) receiving paging information for the network originating downlink material of the UE from the EUTRAN; (ii) generating a new action originating uplink at the UE Data; or (iii) follow the reselection of the UE to another cell. Other triggers as described above are also possible.

7. When a trigger is generated, the UE sends a connection re-establishment request message. In this example, the UE sends an RRC Connection Re-establishment Request message with an RRC Abort indication to the EUTRAN. The RRC abort indication may be included in the re-establishment reason field of the RRC Connection Re-establishment Request message.

8. EUTRAN then responds by re-establishing the command message with the connection. In this example, the EUTRAN sends an RRC Connection Re-establishment command message to the UE.

9. When the RRC connection has been re-established, the UE sends a Connection Re-establishment Complete message to confirm that the RRC connection has been re-established. If the RRC Connection Re-establishment Command message is used as the Connection Re-establishment Command message, the UE transmits an RRC Connection Re-establishment Complete message to the EUTRAN.

Depending on the situation (and possibly as an alternative to using the RRC Connection Re-establishment command message shown in Step 8 above), the EUTRAN may also respond by an RRC Connection Reconfiguration message. In one scenario, where the EUTRAN will use the RRC Connection Reconfiguration message instead of the RRC Connection Reestablishment Command message as a connection re-establishment command message. In its example, the EUTRAN may use a modified form of RRC connection reconfiguration such that the impact at the UE will cause the RRC connection to be re-established. This modification may, for example, include a new information element (IE) indicating that the purpose is to re-establish an RRC connection. For example, the new IE may be marked as "aborted RRC connection", "Suspend Indicator", "Suspension Indicator" or something different. The new IE may be present in the message and the presence of the IE in the message may cause the UE to re-establish an RRC connection. Alternatively, the new IE may be a Boolean value and setting the IE to true may cause the UE to suspend the RRC connection. Other new or existing 3GPP news Interest can also be used for this purpose.

11. If the RRC Connection Reconfiguration message is received at the UE, the UE responds to the message by the RRC Connection Reconfiguration Complete message. The UE will use the RRC Connection Reconfiguration Complete message as the Connection Reestablishment Complete message. Other new or existing 3GGPP messages can also be used for this purpose.

12. At this point, the RRC connection is completely re-established and user plane data communication with the UE can be initiated or replied.

The example scenarios 14 through 16 below and the respective graphs 31 through 33 give a more detailed example of the particular situation within the general case discussed above in the context 13 and shown in FIG.

Example case 14

31 shows a message sequence diagram for re-establishing the UE 101 from the abort on the eNB 102a, the eNB 102a having RRC connection information or messages for the UE 101. The eNB 102a may be an eNB that suspends the RRC connection or it may be a different eNB.

1. When triggering an RRC connection generated at the UE 101 for re-establishing the suspension, the UE transmits an RRC Connection Re-establishment Request message to the eNB 102a. The re-establishment request message may contain a re-establishment reason field that allows the UE 101 to indicate to the eNB 102a that the re-establishment is to restart the previously suspended RRC connection.

2. When the eNB 102a receives the request message, the eNB 102a retrieves the stored RRC connection information for the UE 101 and transmits an RRC Connection Re-establishment command message to the UE 101.

3. The UE performs the reestablishment of the suspended RRC connection and sends an RRC Connection Reestablishment Complete message to the eNB.

4. The eNB then sends an RRC Connection Reconfiguration message to the UE.

5. The UE completes the RRC connection reconfiguration and sends an RRC Connection Reconfiguration Complete message to the eNB to complete the reestablishment of the RRC connection.

Example case 15

Figure 32 shows an eNB 102b for camping on an RRC connection message or message. A re-established message sequence diagram of the RRC connection of the UE 101's suspension.

1. When triggering an RRC connection generated at the UE 101 for re-establishing the suspension, the UE transmits an RRC Connection Re-establishment Request message to the eNB 102b. The re-establishment request message may contain a re-establishment reason field that allows the UE 101 to indicate to the eNB 102b that the re-establishment is to restart the previously suspended RRC connection. The re-establishment request message may also contain information that enables the eNB 102b to identify the eNB (eNB1 102a) that originally suspended the RRC connection of the UE.

2. The eNB 102b does not have RRC message information for the UE 101 and thus transmits an RLF indication message (message extraction) that suspends the RRC connection to the old eNB 102a.

3. The old eNB responds by transmitting a handover request including RRC connection connection information for the UE 101 to the new eNB 102b.

4. The new eNB 102b responds to the old eNB by handing over the request response.

5. The new eNB 102b then sends an RRC Connection Re-establishment message to the UE 101.

6. The UE 101 performs the reestablishment of the suspended RRC connection and responds to the new eNB 102b by the RRC Connection Reestablishment Complete message.

7. The new eNB then sends an RRC Connection Reconfiguration message to the UE.

8. The UE completes the RRC connection reconfiguration and sends an RRC Connection Reconfiguration Complete message to the new eNB to complete the reestablishment of the RRC connection.

9. The new eNB 102b then completes the S1 path switch by the MME 103b.

10. The MME 103b sends a handover request response to the new eNB.

11. The new eNB 102b will then send the old eNB 102a to release the message for the RRC connection configuration or message of the UE 102 to the old eNB 102a.

Example case 16

Figure 33 shows a message sequence diagram of a NAS recovery procedure using Tracking Area Update (TAU), discontinued from UE 101.

1. When triggering an RRC connection generated at the UE 101 for re-establishing abort, The UE transmits an RRC Connection Re-establishment Request message to the eNB 102a.

2. When the eNB 102a receives the request message, the eNB 102a determines that it does not have the RRC connection information for the UE 101 and decides to reject the re-establishment request. The eNB 102a then transmits an RRC Connection Rejection Command message to the UE 101.

3. The UE then sends an RRC Connection Request message to the eNB for a new RRC connection with the eNB.

4. The eNB 102a then sends an RRC Connection Setup message to the UE 101.

5. The UE completes the RRC connection setup and sends an RRC Connection Setup Complete message to the eNB 102a.

6. The eNB 102a then sends a DL Info Transfer message to the UE.

7. Thereafter, an RRC Connection Release message is sent to the UE 101 for the eNB 102a.

Additional aspects of the invention related to the operation of the UE to suspend the RRC connection will now be set forth in the following numbered clauses.

CLAIMS 1. A method implemented in a User Equipment (UE) for use with a Radio Access Network (RAN), the method comprising: the UE suspending an RRC connection established with one of the RANs; when the RRC When the connection is aborted, the UE monitors at least one of: paging and notification for downlink data of the UE; and the UE stores RRC connection data related to the suspended RRC connection, and the RRC connection data may be The UE uses to restart the suspended RRC connection.

2. The method as set forth in clause 1, wherein the RRC connection data comprises data indicating one or more of: ‧ a configuration of a radio bearer in the established RRC connection; ‧ security associated with the established RRC connection Sexual parameters; ‧ temporary cell identifier; ‧ MAC configuration; ‧ Physical layer configuration.

3. The method as set forth in clause 1 or 2, further comprising indicating the stored RRC connection profile to indicate the suspension of the RRC connection.

4. The method as set forth in clause 1, 2 or 3, wherein the UE suspends the established RRC connection in response to complying with an RRC Connection Abort criterion.

5. The method as set forth in clause 4, wherein the RRC connection suspension criterion comprises one or more of: ‧ expiration of a timer at the UE; ‧ reception of a message at the UE.

6. The method as set forth in any preceding clause, wherein the RAN has an established user plane connection with a core network (CN) for the UE, the method further comprising maintaining the RRC connection when it is suspended The established user plane connection between the RAN and the CN.

7. The method as recited in clause 6, wherein the RAN node buffers the downlink data and pages the UE or when the RRC node that is in the RRC connection with the suspension receives the downlink data for the UE from the CN A notification for the downlink data of the UE is transmitted.

8. The method as set forth in clause 7, wherein the RAN node sends a paging upgrade message to the CN in response to the RAN node not receiving a response to the paging or the notification of downlink data from the UE.

9. The method as set forth in any one of clauses 1 to 5, further comprising the UE or a RAN node transmitting a message to inform any node in the core network (CN) that the RRC connection is aborted.

10. The method as set forth in clause 9, wherein the RAN has an established user plane connection with the CN for the UE, the method further comprising aborting the established user plane between the CN and the RAN connection.

11. The method as set forth in clause 10, wherein the message sent to the CN comprises the UE One of the methods of identifying that the established user plane connection between the CN and the RAN includes one or more of the RAN or the CN or both: interrupting user plane data for the UE Transmitting and receiving via the established user plane connection between the RAN and the CN; and storing CN-RAN connection data indicating the established user plane connection, the CN-RAN connection data may be used by As a result of an RRC connection restart procedure, the user plane connection between the RAN and the CN is restarted to later retransmit the transmission and reception of user plane data to the UE.

12. The method as set forth in clause 10 or 11, wherein when receiving downlink data for the UE at the CN, one of the CN nodes buffers the downlink data and the CN is by the RAN One or more cells to initiate the paging of the UE.

13. The method as set forth in clause 10, 11 or 12, further comprising maintaining, by the one of the CN nodes, a validity indicator for the UE, the validity indicator being usable to check validity of the RRC connection as The RRC connection is part of the restart procedure.

14. The method as set forth in clause 13, wherein the value of the validity indicator is dependent on one or more of: a location of the UE; a timer.

15. The method as recited in any preceding clause, further comprising: the UE performing autonomous mobility control by a cell selection or reselection procedure during the time of the RRC connection suspension and as the restart of the suspended RRC connection As a result of a normal RRC connection procedure with the UE establishing a new RRC connection, the UE grants mobility control to the RAN.

16. The method as recited in clause 15, wherein when the UE selects one of the RANs in which the suspended RRC connection indicated by the stored RRC connection profile is invalid, the UE continues to store the RRC connection profile and omits execution Inform the CN of the UE's mobility of any communication with the CN.

17. The method as recited in clause 15, wherein the UE selects where the storage is When the RRC connection data indicates that the RRC connection of the suspended RRC connection is invalid, the UE transmits a message informing the RAN or the CN of the event.

18. The method as set forth in clause 17, wherein the UE also releases the RRC connection and enters an idle mode as a result of selecting a cell of the RAN in which the suspended RRC connection indicated by the stored RRC connection profile is invalid.

19. The method as set forth in clause 17 or 18, wherein the message transmitted by the UE is received by the RAN or the CN causing the RAN or CN to perform one or more of the following: releasing the invalid RRC connection; A normal RRC connection procedure to establish a new RRC connection with the UE; releasing a user plane connection between the CN and the RAN for establishment of one of the UEs.

20. The method as recited in clause 15, wherein the UE continues to store the RRC connected data and transmits a notification when the UE selects one of the RANs in which the suspended RRC connection indicated by the stored RRC connection data is invalid. The RAN or a message of the CN event.

21. The method as recited in any preceding clause, further comprising: determining, by the reference to the stored RRC connection data, whether the suspended RRC connection is still valid; and in response to the UE determining that the suspended RRC connection is still valid The UE sends an RRC Connection Restart Request message to the RAN.

22. The method as set forth in clause 21, further comprising: in response to receiving an RRC Connection Restart Complete message from the RAN, the UE replies to the user plane data transfer with the RAN via the restarted RRC connection.

23. The method as set forth in clause 22, further comprising: in response to receiving an RRC connection restart reject message from the RAN, the UE releasing the suspended RRC connection and entering an idle mode; and thereafter the UE initiates a normal RRC A connection setup procedure is established to establish a new RRC connection with the RAN.

24. The method of clause 23, wherein the RAN node transmits the RRC Connection Restart Reject message to the UE in response to a RAN node determining that it does not have an RRC connection for one of the valid terminations of the UE.

25. The method as recited in any preceding clause, further comprising: determining, by the reference to the stored RRC connection data, whether the suspended RRC connection is still valid; in response to the UE determining that the suspended RRC connection is invalid, The UE releases the aborted RRC connection and enters an idle mode; and thereafter the UE initiates a normal RRC connection setup procedure to establish a new RRC connection with the RAN.

The method of any one of clauses 21 to 25, wherein the UE determines whether the suspended RRC connection is still valid, comprising at least one of: determining whether the UE is currently in the RRC connection data by the storage The indicated RRC connection of the suspension is still valid in one of the RAN cells; and ‧ determines whether a timer has not expired.

27. The method of clauses 21 to 26, further comprising the result of the establishing of the restart or a new RRC connection as the suspended RRC connection, the UE granting the UE's mobility control to the RAN.

28. The method of any preceding clause, further comprising initiating the restart of the suspended RRC connection in response to: ???the UE generating uplink data via an RRC connected user plane; Or ‧ receiving a paging at the UE; or ‧ receiving the RAN or the CN buffered downlink material at the UE for transmission to one of the UE notifications

29. The method as set forth in any preceding clause, wherein the UE is configured to operate according to LTE or The LTE advanced protocol communicates with the RAN.

30. The method as set forth in any preceding clause, wherein the RAN is configured to communicate with the UE in accordance with the LTE or LTE advanced protocols.

31. The method as set forth in any preceding clause, wherein the or the RAN node is (several) eNode B.

32. A User Equipment (UE) for use with a Radio Access Network (RAN) configured to: suspend an RRC connection established with one of the RANs; when the RRC connection is aborted, Monitoring at least one of: paging and notification for downlink data of the UE; and storing RRC connection data indicating the suspended RRC connection, the RRC connection profile may be used by the UE to restart the suspended RRC connection.

33. The UE as set forth in clause 32, wherein the RRC connection profile comprises data representing one or more of: ‧ a configuration of a radio bearer in the established RRC connection; ‧ security associated with the established RRC connection Sexual parameters; ‧ temporary cell identifier; ‧ MAC configuration; ‧ physical layer configuration

34. The UE as set forth in clause 32 or 33, further comprising the UE configured to indicate the stored RRC connection profile to indicate the suspension of the RRC connection.

35. The UE as set forth in clause 32, 33 or 34, further comprising the UE being configured to suspend the established RRC connection in response to complying with an RRC Connection Abort criterion.

36. The UE as set forth in clause 35, wherein the RRC connection suspension criterion comprises one or more of: ‧ expiration of a timer at the UE; ‧ Reception of a message at the UE.

37. The UE as set forth in any one of clauses 32 to 36, further comprising: the UE configured to perform autonomous mobility control by a cell selection or reselection procedure during a time of the RRC connection suspension and as the As a result of the suspension of the RRC connection or the establishment of a new RRC connection with the UE as a result of the normal RRC connection procedure, the UE grants mobility control to the RAN.

38. The UE as set forth in clause 37, the UE configured to, when the UE selects one of the RANs in which the suspended RRC connection indicated by the stored RRC connection profile is invalid, the UE continues to store The RRC connects the data and omits any communication with the CN that performs the mobility of the UE to the CN.

39. The UE as set forth in clause 37, the UE configured to cause the UE to transmit a notification when the UE selects one of the RANs in which the suspended RRC connection indicated by the stored RRC connection profile is invalid The RAN or a message of the CN event.

40. The UE as set forth in clause 39, the UE being configured such that the UE also releases the RRC as a result of selecting one of the RANs in which the RRC connection of the suspension indicated by the stored RRC connection profile is invalidated Connect and enter idle mode.

41. The UE as set forth in clause 39 or 40, wherein the message transmitted by the UE is received by the RAN or the CN causes the RAN or CN to perform one or more of: releasing the invalid RRC connection; A normal RRC connection procedure to establish a new RRC connection with the UE; releasing a user plane connection between the CN and the RAN for establishment of one of the UEs.

42. The UE as set forth in clause 37, the UE configured to, when the UE selects one of the RANs in which the suspended RRC connection indicated by the stored RRC connection profile is invalid, the UE continues to store The RRC connects the data and transmits a message informing the RAN or the CN of the event.

43. The UE as set forth in any one of clauses 32 to 42, further comprising the UE being configured such that, as part of the RRC Connection Restart procedure: The UE determines whether the suspended RRC connection is still valid by referring to the stored RRC connection data; and in response to the UE determining that the suspended RRC connection is still valid, the UE sends an RRC Connection Restart Request message to the RAN.

44. The UE as set forth in clause 43 further comprising: the UE configured to, in response to receiving an RRC Connection Restart Complete message from the RAN, the UE replies with the RAN via the restarted RRC connection User plane data transfer.

45. The UE as set forth in clause 43 further comprising: the UE configured to, in response to receiving an RRC Connection Restart Reject message from the RAN, the UE releasing the suspended RRC connection and entering an idle mode; Thereafter the UE is configured to initiate a normal RRC connection setup procedure to establish a new RRC connection with the RAN.

46. The UE as set forth in clause 43 wherein the RAN node transmits the RRC Connection Restart Reject message to the UE in response to a RAN node determining that it does not have an RRC connection for one of the UE's active aborts.

47. The UE as set forth in any one of clauses 32 to 46, further comprising the UE configured to: determine, by reference to the stored RRC connection profile, whether the suspended RRC connection is still valid; in response to the UE determining The suspended RRC connection is invalid, the suspended RRC connection is released and enters the idle mode; and thereafter a normal RRC connection setup procedure is initiated to establish a new RRC connection with the RAN.

48. The UE as set forth in any one of clauses 43 to 47, further comprising the UE configured to determine whether the suspended RRC connection is still valid, determining the following One less: ‧ whether the UE is currently in a cell of the RAN in which the suspended RRC connection indicated by the stored RRC connection data is still valid; and ‧ whether a timer has not expired

49. The UE as set forth in any one of clauses 43 to 48, further comprising the UE configured to act as a result of the establishment of the restart or a new RRC connection of the suspended RRC connection, the UE The mobility control gives way to the RAN.

50. The UE as set forth in any one of clauses 32 to 49, further comprising the restarting of the RRC Connection Restart procedure in which the UE is configured to initiate the suspension in response to at least one of: The UE generates uplink data via an RRC connected user plane; ‧ receives a paging at the UE; and ‧ receives at the UE the indication that the RAN or the CN buffered downlink data to connect via an RRC The user plane sends a message to one of the UEs.

The UE as set forth in any one of clauses 32 to 50, wherein the UE is configured to communicate with the RAN according to an LTE or LTE advanced protocol.

52. A wireless communication system comprising one of the UEs as set forth in any one of clauses 32 to 51, and one of the user plane connections with an established core network (CN) for the UE The system is configured to maintain the established user plane connection between the RAN and the CN when the RRC connection is aborted.

53. The wireless communication system as set forth in clause 52, further comprising the RRC connection valid RAN node configured to cause the RAN node to receive downlink data for the UE from the CN, the RAN The node buffers the downlink data and pages the UE or transmits a notification for the downlink data of the UE.

54. The wireless communication system as set forth in clause 53, further comprising the RAN node configured to, in response to the RAN node not receiving the paging or downlink from the UE In response to the notification of the link profile, the RAN node sends a paging upgrade message to the CN.

55. A wireless communication system comprising a UE as set forth in any one of clauses 32 to 51, and a RAN, the wireless communication system being configured to cause the UE or a RAN node to send a message to inform the core The RRC connection is aborted by any node in the network (CN).

56. The wireless communication system as set forth in clause 55, wherein the RAN has an established user plane connection with the CN for the UE, the wireless communication system configured to cause the wireless communication system to suspend the CN and The established user plane connection between the RANs.

57. The wireless communication system as set forth in clause 56, further comprising the wireless communication system being configured such that the message sent to the CN includes identification by one of the UEs, and such that in order to suspend between the CN and the RAN The established user plane connection, the RAN or one or more of the CNs or both: interrupting transmission of user plane data for the UE via the user plane connection between the RAN and the CN And receiving; and storing CN-RAN connection data indicating the established user plane connection, the CN-RAN connection data can be used to reply between the RAN and the CN by being a result of an RRC connection restart procedure The user plane is connected to later transmit and receive the user plane data of the UE.

58. The wireless communication system as set forth in clause 56 or 57, further comprising the wireless communication system being configured such that when a downlink data for the UE is received at the CN, the CN node The downlink data is buffered and the CN initiates the paging of the UE by one or more cells of the RAN.

59. The wireless communication system as set forth in clause 56, 57 or 58, further comprising the wireless communication system being configured to cause one of the CN nodes to maintain a validity indicator for the UE, the validity indicator Can be used to check the validity of the RRC connection as the RRC Connect the part of the restarter.

60. The wireless communication system as set forth in clause 59, wherein the value of the validity indicator is dependent on one or more of: a location of the UE; a timer.

61. The wireless communication system as set forth in any one of clauses 52 to 60, wherein the RAN is configured to communicate with the UE in accordance with an LTE or LTE advanced protocol.

62. A wireless communication system as set forth in any one of clauses 52 to 60, wherein the or the RAN nodes are (several) eNode Bs.

63. A computer program product with instructions configured to, when executed by a processor for a user equipment (UE) for use with a radio access network (RAN), configured to One of the items 1 to 31 sets forth one of the method operations.

64. A computer program product with instructions for causing a RAN node to be executed by a processor for use in a node of a radio access network (RAN) for use with a user equipment (UE) It is configured to operate in accordance with one of the methods set forth in any one of clauses 1 to 31.

Additional aspects of the present invention related to the operation of the RAN node to suspend the RRC connection will now be set forth in the following numbered clauses.

CLAIMS 1. A method implemented in a node of a radio access network (RAN) for use with a user equipment (UE), the method comprising: the RAN node suspending an RRC connection established with one of the UEs Thereafter the RAN node is operable to, when the RRC connection is aborted, to page the UE to page or transmit a notification for the downlink data of the UE or both; and the RAN node stores an RRC related to the suspended RRC connection Connection data, the RRC connection data may be used by the RAN node to restart the suspended RRC connection.

2. The method as set forth in clause 1, wherein the RRC connection data includes data indicating one or more of: ‧ a configuration of a radio bearer in the established RRC connection; ‧ Security parameters related to the established RRC connection; ‧ Temporary cell identifier; ‧ MAC configuration; ‧ Physical layer configuration

3. The method as set forth in clause 1 or 2, further comprising indicating the stored RRC connection profile to indicate the suspension of the RRC connection.

4. The method as set forth in clause 1, 2 or 3, wherein the RAN node suspends the established RRC connection in response to complying with an RRC Connection Abort criterion.

5. The method as set forth in clause 4, wherein the RRC connection suspension criterion comprises one or more of: ‧ expiration of a timer at the RAN node; ‧ a message transmitted by the RAN node to the UE to indicate The establishment of the RRC connection is suspended.

6. The method as set forth in any one of clauses 1 to 5, wherein the RAN node has an established user plane connection with the core network (CN) for the UE, the method further comprising when the RRC The established user plane connection between the RAN node and the CN is maintained when the connection is aborted.

7. The method as set forth in clause 6, wherein when the RAN node receives downlink data for the UE from the CN, the RAN node buffers the downlink data and pages the UE or transmits the UE for transmission. A notification of the downlink data.

8. The method as set forth in clause 7, wherein the RAN node sends a paging upgrade message to the CN in response to the RAN node not receiving a response to the paging or the notification of downlink data from the UE.

9. The method as set forth in any one of clauses 1 to 5, further comprising the UE or the RAN node transmitting a message to inform any node in the core network (CN) that the RRC connection is aborted.

10. The method as set forth in clause 9, wherein the RAN node has an established user plane connection with the CN for the UE, the method further comprising suspending between the CN for the UE and the RAN The established user plane connection.

11. The method as set forth in clause 10, wherein the message sent to the CN comprises identification by one of the UEs, the method further comprising the RAN node or one or more CN nodes or both: interrupting use for the UE The plane data is transmitted and received via the established user plane connection between the CN and the RAN node; and the CN-RAN connection data indicating the user plane connection with the CN is stored, the CN-RAN The connection profile can be used to retransmit the user plane connection between the CN and the RAN node as a result of an RRC connection restart procedure to later transmit and receive user plane data to the UE .

12. The method as set forth in clause 10 or 11, wherein when receiving downlink data for the UE at the CN, one of the CN nodes buffers the downlink data and the CN is by the RAN One or more cells to initiate the paging of the UE.

13. The method as set forth in clause 10, 11 or 12, further comprising maintaining, by the one of the CN nodes, a validity indicator for the UE, the validity indicator being usable to check validity of the RRC connection as The RRC connection is part of the restart procedure.

14. The method as set forth in clause 13, wherein the value of the validity indicator is dependent on one or more of: a location of the user; a timer.

15. The method as set forth in any preceding clause, further comprising: the RAN granting the UE's mobility control to the UE until the restart as the suspended RRC connection or establishing a new RRC connection with the UE As a result of a normal RRC connection procedure, the RAN replies to the UE's mobility control.

16. The method as recited in clause 15, wherein when the UE selects one of the RANs in which the suspended RRC connection indicated by the stored RRC connection profile is invalid, the The RAN receives a message informing the RAN of this event.

17. The method as set forth in clause 16, wherein the message transmitted by the UE is caused by the RAN to cause the RAN to perform one or more of: releasing the RRC connection of the invalidation; starting with the UE A new RRC connection; releasing a user plane connection between the CN and the RAN for establishment of one of the UEs.

18. The method as set forth in clause 15, 16 or 17, further comprising as a result of a restart of the suspended RRC connection or a normal RRC connection procedure for establishing a new RRC connection with the UE, the RAN replies to the UE Mobile control.

19. The method as recited in any preceding clause, wherein, in response to receiving an RRC Connection Restart Request message from the UE, the RAN node: determining whether the suspended RRC connection is still valid by referring to the stored RRC connection profile; And in response to the RAN node determining that the suspended RRC connection is still valid, transmitting a restart request completion message to the UE and thereafter replying with the user plane data transmission of the UE via the restarted RRC connection; or responding to the The RAN node determines that the suspended RRC connection is invalid, and sends a restart request reject message to the UE.

20. The method as set forth in clause 19, wherein the RAN node determines whether the suspended RRC connection is still valid, comprising at least one of: ‧ determining that a timer has not expired; and ‧ determining that the RRC connection is not released.

21. The method as set forth in any preceding clause, wherein the UE is configured to communicate with the RAN in accordance with an LTE or LTE advanced protocol.

22. The method as set forth in any preceding clause, wherein the RAN is configured to communicate with the UE in accordance with the LTE or LTE advanced protocols.

23. The method as set forth in any preceding clause, wherein the or the RAN node is (if Dry) eNode B.

24. A node for use with a User Equipment (UE), a Radio Access Network (RAN), configured to: suspend an RRC connection established with one of the UEs; thereafter operable When the RRC connection is suspended, paging the UE or transmitting a notification for the UE downlink data or both; and storing RRC connection data related to the suspended RRC connection, the RRC connection data may be used by the RAN node Used to restart the aborted RRC connection.

25. The RAN node as set forth in clause 24, wherein the RRC connection profile comprises data indicative of one or more of: ‧ a configuration of a radio bearer in the established RRC connection; ‧ associated with the established RRC connection Security parameters; ‧ temporary cell identifier; ‧ MAC configuration; ‧ physical layer configuration

26. The RAN node as set forth in clause 24 or 25, further comprising an RRC connection profile indicating the store to indicate the suspension of the RRC connection.

27. The RAN node as set forth in clause 24, 25 or 26, further comprising the RAN node being configured to suspend the established RRC connection in response to complying with an RRC Connection Abort criterion.

28. The RAN node as set forth in clause 27, wherein the RRC connection suspension criterion comprises one or more of: ‧ expiration of a timer at the RAN node; ‧ a message transmitted by the RAN node to the UE To indicate the suspension of the established RRC connection.

29. The RAN node as set forth in any one of clauses 24 to 28, further comprising The RAN node is configured to receive an RRC Connection Restart Request message from the UE by determining whether the suspended RRC connection is still valid by referring to the stored RRC connection profile; in response to the RAN node determining the suspended RRC connection Still valid, sending a restart request completion message to the UE and thereafter replying with the user plane data transmission of the UE via the restarted RRC connection; and responding to the RAN node determining that the suspended RRC connection is invalid, A restart request rejection message is sent to the UE.

30. The RAN node as set forth in clause 29, the RAN node configured to cause the RAN node to determine whether the suspended RRC connection is still valid, comprising at least one of: determining that a timer has not expired; It is determined that the RRC connection is not released.

31. The RAN node as set forth in clause 29 or 30, further comprising, as a result of a restart of the suspended RRC connection or a normal RRC connection procedure for establishing a new RRC connection with the UE, the RAN replies to the action of the UE Sexual control.

32. The RAN node as set forth in any one of clauses 24 to 31, wherein the RAN node is configured to communicate with the UE in accordance with an LTE or LTE advanced protocol.

33. A RAN node as set forth in any preceding clause, wherein the RAN node is an eNode B.

34. The RAN node as set forth in any one of clauses 24 to 33, wherein the RAN node has an established user plane connection with the core network (CN) for the UE, further comprising when the RRC The established user plane connection between the RAN node and the CN is maintained when the connection is aborted.

35. The RAN node as set forth in clause 34, the RAN node being configured such that when the RAN node receives downlink data for the UE from the CN, the RAN node is slowed down The downlink data is punctured and the UE is paged or a notification for downlink data for the UE is transmitted.

36. The RAN node as set forth in clause 35, the RAN node configured to, in response to the RAN node not receiving a response to the paging or the notification of downlink data from the UE, the RAN node The CN sends a paging upgrade message.

37. The RAN node as set forth in any one of clauses 24 to 33, further comprising the UE or the RAN node transmitting a message to inform any node in the core network (CN) that the RRC connection is aborted.

38. The RAN node as set forth in clause 37, wherein the RAN node has an established user plane connection with the CN for the UE, further comprising terminating between the CN for the UE and the RAN The established user plane connection.

39. The RAN node as set forth in clause 38, wherein the message sent to the CN comprises one of the UEs identified, the RAN node or one or more CN nodes or both configured to: interrupt for the UE Transmitting and receiving user plane data via the established user plane connection between the CN and the RAN node; and storing CN-RAN connection data indicating a user plane connection established with the CN, the CN- The RAN connection profile can be used to reply to the user plane connection between the CN and the RAN node as a result of an RRC connection restart procedure to later transmit and receive user plane data to the UE .

40. A wireless communication system comprising a RAN node and a CN as set forth in clause 38 or 39, wherein the CN is configured such that when the downlink data for the UE is received at the CN, One of the CN nodes buffers the downlink data and the CN initiates the paging of the UE by one or more cells of the RAN.

41. A wireless communication system comprising a RAN node and a CN as set forth in clause 38 or 39, or a wireless communication system as set forth in clause 40, further comprising the wireless communication system being configured to cause one of the CN The node maintains a validity indication for the UE The validity indicator can be used to check the validity of the RRC connection as part of the RRC Connection Restart procedure.

42. The wireless communication system as set forth in clause 41, wherein the value of the validity indicator is dependent on one or more of: a location of the user; a timer.

43. A RAN comprising one of the RAN nodes as set forth in any one of clauses 24 to 39, further comprising: the RAN configured to re-use the UE's mobility control to the UE until reconnected as an RRC As a result of initiating the procedure or establishing a new RRC connection with the UE, the RAN replies to the UE's mobility control.

44. The RAN as set forth in clause 43, wherein the RAN receives a message informing the RAN of the event when the UE selects a cell of the RAN in which the suspended RRC connection indicated by the stored RRC connection profile is invalid .

45. The RAN as set forth in clause 44, wherein the RAN is configured such that the message transmitted by the UE is caused by the RAN to cause the RAN to perform one or more of: releasing the invalid terminated RRC connection Starting with a new RRC connection with one of the UEs; releasing a user plane connection between the CN and the RAN for establishment of one of the UEs.

46. A computer program product with instructions for causing a RAN node to be executed by a processor for use in a node of a radio access network (RAN) for use with a user equipment (UE) It is configured to operate in accordance with one of the methods set forth in any one of clauses 1 to 23.

Additional aspects of the invention related to the operation of the CN node to suspend the RRC connection will now be set forth in the following numbered clauses.

CLAIMS 1. A method implemented in a node of a core network (CN) for use with a node of a radio access network (RAN), comprising receiving an indication of the RAN and a use in response to the CN receiving An RRC connection between the UEs (UE) is aborted by one of the messages: the CN node interrupts user plane data for the UE via the CN and the RAN Transmitting and receiving an established user plane CN-RAN connection between the nodes; and storing CN-RAN connection data indicating the user plane connection established with the CN, the CN-RAN connection data may be used The transmission and reception of the user plane data of the UE is later replied to by replying to the user plane connection between the CN and the RAN node as a result of the RRC connection being restarted.

2. The method of clause 1, wherein when receiving downlink data for the UE at the CN, the method further comprises buffering the downlink data in one of the CN nodes and by using the One or more cells of the RAN initiate the paging of the UE.

3. The method as set forth in clause 1 or 2, further comprising responding to receiving a CN-RAN connection restart message at a node of the CN, replying to user plane data transfer between the CN and the RAN.

4. The method as set forth in any preceding clause, wherein the CN node is part of an evolved packet core (EPC) configured to communicate in accordance with an LTE or LTE advanced protocol.

5. A node for use with a radio access network (RAN), one of a core network (CN), the node of the CN being configured to receive an indication of the RAN and a user in response to the CN An RRC connection between devices (UE) is terminated by one of the messages: interrupting transmission and reception of user plane data for the UE via an established user plane CN-RAN connection between the CN and the RAN node And storing CN-RAN connection data indicating the user plane connection established with the CN, the CN-RAN connection data may be used to reply to the CN and the RAN by being restarted as the RRC connection The user plane connection between the nodes to later reply to the transmission and reception of the user plane data of the UE.

6. The CN node as set forth in clause 5, the CN node being configured such that when receiving downlink data for the UE at the CN, the CN node buffers the downlink data and by the One or more cells of the RAN initiate the paging of the UE.

7. The CN node as set forth in clause 5 or 6, further comprising responding to the CN A node receives a CN-RAN connection restart message, and the CN node replies to the user plane data transmission with the RAN.

8. The CN node as set forth in clause 5, 6 or 7, wherein the CN node is part of an evolved packet core (EPC) configured to communicate in accordance with an LTE or LTE advanced protocol.

9. A computer program product with instructions for causing the CN to be executed by a processor for use in a node of a core network (CN) for use with a Radio Access Network (RAN) The node is configured to operate in accordance with one of the methods set forth in any one of clauses 1 through 4.

Additional aspects of the present invention relating to the validity of the UE or RAN node for accessing the suspended RRC connection and the operation of restarting the suspended RRC connection will now be set forth in the following numbered clauses.

CLAIMS 1. A method implemented in a node of a Radio Access Network (RAN) for use with a User Equipment (UE), an established RRC connection between the RAN node and a UE has been discontinued And the RRC connection data related to the suspended RRC connection is stored by the RAN node, the method includes: receiving an RRC connection restart request message from the UE at the RAN node; determining by referring to the stored RRC connection data Whether the suspended RRC connection is still valid; and in response to the RAN node determining that the suspended RRC connection is still valid, the RAN node sends a restart request completion message to the UE and thereafter replies with the restarted RRC connection The user plane data transmission of the UE; or in response to the RAN node determining that the suspended RRC connection is invalid, the RAN node sends a restart request rejection message to the RAN.

2. The method as set forth in clause 1, wherein the RAN node determines whether the suspended RRC connection is still valid, comprising at least one of: determining that a timer has not expired; ‧ It is determined that the RRC connection is not released.

3. The method as set forth in clause 1 or 2, further comprising the result of a normal RRC connection procedure as a restart of the suspended RRC connection or establishing a new RRC connection with the UE, the RAN replies to the UE from the UE Action control.

4. The method as set forth in any preceding clause, wherein the or the RAN node is configured to communicate with the UE in accordance with an LTE or LTE advanced protocol.

5. The method as set forth in any preceding clause, wherein the or the RAN node is (several) eNode B.

6. A node for one of a Radio Access Network (RAN) for use with a User Equipment (UE), the RAN node being configured such that when the RAN node is established with a UE When the RRC connection has been suspended and the RRC connection data related to the suspended RRC connection has been stored by the RAN node, in response to receiving an RRC connection restart request message from the UE at the RAN node: the RAN node refers to the The stored RRC connection data determines whether the suspended RRC connection is still valid; in response to the RAN node determining that the suspended RRC connection is still valid, the RAN node sends a restart request completion message to the UE and thereafter via the restart The RRC connection replies with the user plane data transmission of the UE; and in response to the RAN node determining that the suspended RRC connection is invalid, the RAN node sends a restart request rejection message to the RAN.

7. The RAN node as set forth in clause 6, further comprising the RAN node being configured to determine, by the RAN node, whether the suspended RRC connection is still valid by at least one of: ‧ determining that a timer has expired Full; and ‧ determines that the RRC connection is not released.

8. A RAN comprising one of the RAN nodes as set forth in clause 5 or 6, the RAN The action is configured to reply to the UE's mobility control from the UE as a result of a restart of the aborted RRC connection or a normal RRC connection procedure with the UE establishing a new RRC connection.

9. The RAN node as set forth in any one of clauses 5 to 8, the or the RAN node being configured to communicate with the UE in accordance with an LTE or LTE advanced protocol.

10. The RAN node as set forth in any one of clauses 5 to 9, wherein the or the RAN node is (several) eNode B.

11. A computer program product with instructions for causing a RAN node to be executed by a processor for use in a node of a radio access network (RAN) for use with a user equipment (UE) It is configured to operate in accordance with one of the methods set forth in any one of clauses 1 to 5.

12. A method implemented in a User Equipment (UE) for use with a Radio Access Network (RAN), an established RRC connection between a node of the RAN and the UE has been suspended and The RRC connection data related to the suspended RRC connection has been stored by the UE, the method includes: determining, by the UE, whether the suspended RRC connection is still valid by referring to the stored RRC connection data; and determining, in response to the UE, the suspension The RRC connection is still valid, the UE: transmitting an RRC connection restart request message to the RAN node; and in response to receiving an RRC connection restart accept message from the RAN node, the UE thereafter connects via the restarted RRC Responding to the user plane data transmission with the RAN node, or in response to receiving an RRC connection restart rejection message from the RAN node, the UE releases the RRC connection; or in response to the UE determining that the suspended RRC connection is invalid, The UE releases the RRC connection.

13. The method as set forth in clause 12, wherein the UE determines whether the suspended RRC connection is still valid, comprising at least one of: determining whether the UE is currently in the middle of the stored RRC connection profile. The RRC connection is still valid in one of the RAN cells; and ‧ determines whether a timer has not expired.

14. The method as recited in clause 12 or 13, further comprising, in response to receiving the RRC Connection Restart Reject message or the UE determining that the suspended RRC connection is invalid, the UE also enters an idle mode and thereafter initiates a normal RRC connection A procedure is established to establish a new RRC connection with the RAN.

15. The method as set forth in clause 12, 13 or 14, further comprising as a result of a restart of the suspended RRC connection or a normal RRC connection procedure for establishing a new RRC connection with the RAN, the UE The mobility control gives way to the RAN.

16. The method as set forth in any one of clauses 12 to 15, wherein the UE is configured to communicate with the RAN according to an LTE or LTE advanced protocol.

17. A User Equipment (UE) for use with a Radio Access Network (RAN) configured to enable an established RRC connection between a node of the RAN and the UE Aborting and indicating that the RRC connection data of the configuration information and status information related to the suspended RRC connection has been stored by the UE: the UE determines whether the suspended RRC connection is still valid by referring to the stored RRC connection data; After the UE determines that the suspended RRC connection is still valid, the UE transmits an RRC Connection Restart Request message to the RAN node; and in response to receiving an RRC Connection Restart Accept message from the RAN node, the UE thereafter passes the Resending the RRC connection reply with the user plane data transmission of the RAN node, or in response to receiving an RRC connection restart rejection message from the RAN node, the UE releases the RRC connection; and in response to the UE determining the suspension The RRC connection is invalid, and the UE releases the RRC connection.

18. The UE as set forth in clause 17, further comprising the UE being configured to determine whether the suspended RRC connection is still valid by at least one of the following operations by the UE: Determining whether the UE is currently in a cell of the RAN in which the suspended RRC connection indicated by the stored RRC connection profile is still valid; and ‧ determining whether a timer has not expired.

19. The UE as set forth in clause 17 or 18, further comprising the UE being configured such that in response to receiving the RRC Connection Restart Reject message or the UE determining that the suspended RRC connection is invalid, the UE also enters an idle mode And then a normal RRC connection setup procedure is initiated to establish a new RRC connection with the RAN.

20. The UE as set forth in clause 17, 18 or 19, further comprising a result of the UE being configured to act as a restart of the aborted RRC connection or to establish a new RRC connection with the RAN as a result of a normal RRC connection procedure The mobility control of the UE is given to the RAN.

21. The UE as set forth in any one of clauses 17 to 20, wherein the UE is configured to communicate with the RAN according to an LTE or LTE advanced protocol.

22. A computer program product with instructions for causing a UE to be configured when executed by a processor of a User Equipment (UE) for use with a Radio Access Network (RAN) connection The method operates according to one of the methods as set forth in any one of clauses 12 to 16.

Additional aspects of the present invention relating to the operation of the CN node or RAN node for handling downlink data when the RRC connection is aborted will now be set forth in the following numbered clauses.

CLAIMS 1. A method implemented in a node of a Radio Access Network (RAN) for use with a User Equipment (UE), an established RRC connection between a RAN node and a UE has been discontinued And an RRC connection data related to the suspended RRC connection is stored by the RAN node, the method comprising: the RAN node receiving downlink data for the UE; the RAN node buffering the downlink data; The RAN node pages the UE or transmits a notification for the downlink data of the UE.

2. The method as set forth in clause 1, wherein the RAN node responds to the CN in response to the RAN node not receiving a response to the paging or the downlink data from the UE. Send a paging upgrade message.

3. The method as set forth in clause 2, further comprising: receiving, at the RAN node, an RRC connection restart request message from the UE; determining whether the suspended RRC connection is still valid by referring to the stored RRC connection data; And in response to the RAN node determining that the suspended RRC connection is still valid, the RAN node sends a restart request completion message to the UE and thereafter replies with the user plane data transmission of the UE via the restarted RRC connection; or In response to the RAN node determining that the suspended RRC connection is invalid, the RAN node sends a Restart Request Reject message to the RAN.

4. The method as set forth in any preceding clause, wherein the RAN node is configured to communicate with the UE in accordance with an LTE or LTE advanced protocol.

5. The method as set forth in any preceding clause, wherein the RAN node is an eNode B.

6. A node for one of a Radio Access Network (RAN) for use with a User Equipment (UE), the RAN node being configured such that when the RAN node is established with a UE When the RRC connection has been suspended and the RRC connection data related to the suspended RRC connection has been stored by the RAN node, the RAN node receives the downlink data for the UE in response to the RAN node: the RAN node buffers the downlink data; And the RAN node replies to the UE or transmits a message that gives a notification of downlink data.

7. The RAN node as set forth in clause 6, the RAN node being configured to, in response to the RAN node not receiving a response to the paging message or the message giving notification of downlink information from the UE The RAN node sends a paging upgrade message to the CN.

8. The RAN node as set forth in clause 6, further comprising the RAN node configured In response to the RAN node receiving an RRC Connection Restart Request message from the UE: the RAN node determines whether the suspended RRC connection is still valid by referring to the stored RRC connection profile; and in response to the RAN node determining the suspension The RRC connection is still valid, the RAN node sends a restart request completion message to the UE and thereafter replies to the UE plane data transmission with the UE via the restarted RRC connection; and in response to the RAN node determining the suspension The RRC connection is invalid, and the RAN node sends a restart request rejection message to the RAN.

9. The RAN node as set forth in any one of clauses 6 to 8, wherein the RAN node is configured to communicate with the UE in accordance with an LTE or LTE advanced protocol.

10. The method as set forth in any one of clauses 6 to 9, wherein the RAN node is an eNode B.

11. A computer program product with instructions for causing a RAN node to be executed by a processor for use in a node of a radio access network (RAN) for use with a user equipment (UE) It is configured to operate in accordance with one of the methods set forth in any one of clauses 1 to 5.

12. A method implemented in a node of a core network (CN) for use with a node of a radio access network (RAN), in response to the CN receiving an indication of the RAN and a user equipment An RRC connection between (UE) is terminated by one of the messages, the user plane data for the UE has been interrupted via the user plane CN-RAN established between the CN and the RAN node for one of the UEs The transmission and reception of the connection, and storing the CN-RAN connection data indicating the existing user plane connection between the CN and the RAN, the method comprising: receiving downlink data for the UE; the CN node buffering the Downlink data; The CN node initiates the paging of the UE by one or more cells of the RAN.

13. The method as set forth in clause 12, further comprising maintaining, by the one of the CN nodes, a validity indicator for the UE, the validity indicator being usable to check validity of the RRC connection as an RRC connection re Start the part of the program.

14. The method as set forth in clause 13, wherein the value of the validity indicator is dependent on one or more of: a location of the user; a timer.

The method as set forth in any one of clauses 12 to 14, wherein the CN node is part of an evolved packet core (EPC) configured to communicate in accordance with an LTE or LTE advanced protocol.

16. A node for a core network (CN) for use with a node of a Radio Access Network (RAN), the CN node being configured such that when the RAN is received in response to the CN indication An RRC connection between a user equipment (UE) is suspended by one of the messages, and the user plane data for the UE has been interrupted via the CN and the RAN node for the establishment of one of the UEs In response to transmission and reception of a planar CN-RAN connection, and storing CN-RAN connection data indicating an existing user plane connection between the CN and the RAN, in response to receiving downlink data for the UE: the CN The node buffers the downlink data; the CN node initiates the paging of the UE by one or more cells of the RAN.

17. The CN node as set forth in clause 16, further comprising one of the CN nodes maintaining a validity indicator for the UE, the validity indicator being usable to check validity of the RRC connection as an RRC connection Restart the part of the program.

18. The CN node as set forth in clause 17, wherein the value of the validity indicator is dependent on one or more of: a location of the user; a timer.

19. The CN node as set forth in any one of clauses 16 to 18, wherein the CN node is part of an evolved packet core (EPC) configured to communicate in accordance with an LTE or LTE advanced protocol.

20. A computer program product with instructions for execution by a processor for a node of a core network (CN) for communicating with a Radio Access Network (RAN) via a CN-RAN connection The node of the CN is configured to operate in accordance with one of the methods set forth in any one of clauses 12-15.

Additional aspects of the present invention related to the UE's operation for handling the UE's mobility when the RRC connection is aborted will now be set forth in the following numbered clauses.

CLAIMS 1. A method implemented in a User Equipment (UE) for use with a Radio Access Network (RAN), an established RRC connection between a node of the RAN and the UE has been suspended and The RRC connection data related to the suspended RRC connection has been stored by the UE, and the method includes: the UE performing autonomous mobility control by a cell selection or reselection procedure during the time when the RRC connection is suspended, and as the suspension As a result of the restart of the RRC connection or the establishment of a new RRC connection with the UE, a normal RRC connection procedure, the UE grants the UE's mobility control to the RAN.

2. The method as set forth in clause 1, wherein, when the UE selects one of the RANs in which the suspended RRC connection indicated by the RRC connection data is invalid, the UE continues to store the RRC connection data and omits execution to notify the CN The UE's mobility of any communication with the CN.

3. The method as set forth in clause 1, wherein the UE transmits a notification to the RAN or a core network when the UE selects one of the RANs in which the suspended RRC connection indicated by the stored RRC connection profile is invalid. (CN) A message for this event.

4. The method as set forth in clause 3, wherein the UE also releases the suspended RRC connection and enters an idle mode as a result of selecting one of the RANs in which the RRC connection is invalidated by the stored RRC connection data.

5. The method as set forth in any preceding clause, wherein the UE is configured to communicate with the RAN according to an LTE or LTE advanced protocol.

6. A User Equipment (UE) for communicating with a Radio Access Network (RAN) configured to cause an established RRC connection between a node of the RAN and the UE to be aborted And when the RRC connection data related to the suspended RRC connection has been stored by the UE: the UE performs autonomous mobility control by a cell selection or reselection procedure during the time when the RRC connection is suspended; and the RRC connection as the suspension As a result of a restart or a normal RRC connection procedure with the UE establishing a new RRC connection, the UE grants the UE's mobility control to the RAN.

7. The UE as set forth in clause 6, further comprising the UE being configured such that when the UE selects one of the RANs in which the suspended RRC connection indicated by the RRC connection profile is invalid, the UE continues The RRC connection profile is stored and any communication with the CN that informs the CN of the UE of the mobility is omitted.

8. The UE as set forth in clause 6, further comprising the UE configured to, when the UE selects one of the RANs in which the suspended RRC connection indicated by the stored RRC connection profile is invalid, The UE transmits a message informing the RAN or a core network (CN) of this event.

9. The UE as set forth in clause 8, further comprising the UE being configured such that, as a result of selecting a cell of the RAN in which the RRC connection indicated by the stored RRC connection profile is invalid, the UE is also released The suspended RRC is connected and enters the idle mode.

10. The UE as set forth in any one of clauses 6 to 9, wherein the UE is configured to communicate with the RAN according to an LTE or LTE advanced protocol.

11. A computer program product with instructions for causing a UE to be configured when executed by a processor of a User Equipment (UE) for use with a Radio Access Network (RAN) connection The method operates according to one of the methods as set forth in any one of clauses 1 to 5.

101‧‧‧User Equipment (UE)

102‧‧‧Radio Access Network (RAN)

Claims (40)

A method implemented in a mobile device for use with a radio access network (RAN), comprising: by the mobile device an indication of a radio resource control (RRC) connection with the RAN Is sent to the RAN, wherein the indicator has two values including aborting and releasing the RRC connection, and indicating one of the two values to the RAN; receiving, by the mobile device, a command message from the RAN And in response to the command message, performing at least one of: releasing the RRC connection; or suspending the RRC connection, wherein the suspension of the RRC connection includes the mobile device storing RRC connection data for the RRC connection, and The stored RRC connection data may be used by the mobile device to re-establish the suspended RRC connection. The method of claim 1, wherein the indicator is to abort one of the RRC connection preferences. The method of claim 1, wherein the indicator is to release one of the RRC connection preferences. The method of claim 1, wherein the indicator is included in a request message sent by the mobile device to one of the RAN nodes of the RAN. The method of claim 1, wherein the indicator is included in a capability message sent by the mobile device to one of the RAN nodes of the RAN. The method of claim 1, wherein the mobile device receives the command message in response to the transmitting of the indicator. The method of claim 1, wherein the RRC connection profile includes data indicating at least one of: a configuration of a radio bearer in the RRC connection, a security parameter related to the RRC connection, a temporary cell identifier, a MAC Configuration, entity layer group State, or measurement and report configuration. The method of claim 1, wherein the indicator is sent in response to complying with an RRC Connection Abort criterion at the mobile device. The method of claim 8, wherein the RRC connection suspension criterion comprises at least one of: an expiration of a timer at the mobile device, the user plane data has not been received from the RAN for a period of time or not used The plane data is sent to the RAN, and the user plane data is not expected to be received from the RAN or the user plane data is sent to the RAN, and one of the mobile devices inputs a state of the function, one of the mobile devices A state of the output function, one of the one or more applications of the mobile device, or a higher layer indication of one of the RRC layers at the mobile device. The method of claim 9, wherein the higher layer indicates from an application layer or from a non-access layer (NAS) layer. The method of claim 1, further comprising the mobile device resuming the suspension of the RRC connection in response to at least one of: the mobile device generating uplink data via an RRC connected user plane Receiving a page at the mobile device or receiving a notification at the mobile device regarding the RAN or a core network (CN) buffered downlink data for transmission to the mobile device. The method of claim 1, wherein the mobile device is configured to communicate with the RAN according to a Long Term Evolution (LTE) or LTE Advanced Agreement. The method of claim 1, wherein the RAN is configured to communicate with the mobile device in accordance with an LTE or LTE advanced protocol. The method of claim 1, wherein the RAN node is an eNode B. A mobile device for use with a Radio Access Network (RAN) configured to: issue an indicator regarding a Radio Resource Control (RRC) connection with the RAN Sent to the RAN, wherein the indicator has two values including aborting and releasing the RRC connection, and indicating one of the two values to the RAN; receiving a command message from the RAN; and responding to the command Transmitting at least one of: releasing the RRC connection; or aborting the RRC connection, wherein the suspension of the RRC connection includes the mobile device storing RRC connection data for the RRC connection, and the stored RRC connection The data may be used by the mobile device to re-establish the suspended RRC connection. The mobile device of claim 15, wherein the indicator is to suspend one of the RRC connections. The mobile device of claim 15, wherein the indicator is a preference for releasing the RRC connection. The mobile device of claim 15, wherein the indicator is included in a request message sent by the mobile device to one of the RAN nodes of the RAN. The mobile device of claim 15, wherein the indicator is included in a capability message sent by the mobile device to one of the RAN nodes of the RAN. The mobile device of claim 15 further configured to receive the command message in response to the transmitting of the indicator. The mobile device of claim 15, wherein the RRC connection profile includes data indicating at least one of: a configuration of a radio bearer in the RRC connection, a security parameter related to the RRC connection, a temporary cell identifier, MAC configuration, physical layer configuration, or measurement and report configuration. The mobile device of claim 15 wherein the indicator is transmitted in response to complying with an RRC Connection Abort criterion at the mobile device. The mobile device of claim 22, wherein the RRC connection suspension criterion includes the following At least one of: the timer of one of the mobile devices expires, and the user plane data has not been received from the RAN or no user plane data has been sent to the RAN for a period of time, which has not been expected from a period of time Receiving, by the RAN, user plane data or transmitting user plane data to the RAN, one of the mobile devices inputs a state of the function, one of the mobile devices outputs a state of the function, and the one or more applications of the mobile device A state, or a higher layer indication of one of the RRC layers at the mobile device. The mobile device of claim 23, wherein the higher layer indicates from an application layer or from a non-access layer (NAS) layer. The mobile device of claim 15, further configured to initiate re-establishment of the suspended RRC connection in response to at least one of: the mobile device generating uplink data via an RRC connected user plane Receiving a page at the mobile device or receiving a notification at the mobile device regarding the RAN or a core network (CN) buffered downlink data for transmission to the mobile device. The mobile device of claim 15, wherein the mobile device is configured to communicate with the RAN in accordance with an LTE or LTE advanced protocol. A non-transitory computer readable medium storing instructions to cause a processor to: transmit an indicator to a Radio Resource Control (RRC) connection to a Radio Access Network (RAN) to The RAN, wherein the indicator has two values including abort and release to indicate whether to suspend or release the RRC connection, and direct one of the two values to the RAN; receive a command message from the RAN; Responding to the command message to perform at least one of: releasing the RRC connection; or aborting the RRC connection, wherein the suspension of the RRC connection includes storing The RRC connected RRC connection data, and the stored RRC connection data may be used to re-establish the suspended RRC connection. The non-transitory computer readable medium of claim 27, wherein the indicator is to suspend one of the RRC connections. A non-transitory computer readable medium as claimed in claim 27, wherein the indicator is a preference for releasing the RRC connection. The non-transitory computer readable medium of claim 27, wherein the indicator is included in a request message sent to one of the RAN nodes of the RAN. The non-transitory computer readable medium of claim 27, wherein the indicator is included in a capability message sent to one of the RAN nodes in the RAN. A non-transitory computer readable medium as claimed in claim 27, wherein the command message is received in response to the transmitting of the indicator. The non-transitory computer readable medium of claim 27, wherein the RRC connection data includes data indicating at least one of: a configuration of a radio bearer in the RRC connection, a security parameter related to the RRC connection, Temporary cell identifier, MAC configuration, physical layer configuration, or measurement and report configuration. A non-transitory computer readable medium as claimed in claim 27, wherein the indicator is transmitted in response to conforming to an RRC Connection Abort criterion at a mobile device. The non-transitory computer readable medium of claim 34, wherein the RRC connection suspension criterion comprises at least one of: a timer expired, the user plane data has not been received from the RAN for a period of time or none The user plane data is sent to the RAN, and the user plane data is not expected to be received from the RAN or the user plane data is sent to the RAN during a period of time, a state of an input function, a state of an output function, and a state Or one of the status of one of the applications, or a higher layer for one of the RRC layers. The non-transitory computer readable medium of claim 35, wherein the higher layer indication is from An application layer or from a non-access layer (NAS) layer. The non-transitory computer readable medium of claim 27, the instructions further comprising initiating reestablishment of the suspended RRC connection in response to at least one of: generating an uplink via a user plane of an RRC connection Data, receive a page, or receive a notification about the RAN or a core network (CN) buffered downlink data to send. The non-transitory computer readable medium of claim 27, wherein the communication with the RAN is based on a Long Term Evolution (LTE) or LTE Advanced Agreement. A non-transitory computer readable medium as claimed in claim 27, wherein the RAN is configured to communicate in accordance with Long Term Evolution (LTE) or LTE Advanced Protocol. The non-transitory computer readable medium of claim 27, wherein the RAN node is an eNode B.