PDCP COUNT processing during RRC connection restoration

By using a fixed-value PDCP COUNT synchronization mechanism during RRC connection restoration, the problem of lack of PDCP COUNT synchronization for new base stations is solved, enabling efficient connection restoration of wireless devices between different base stations.

CN117596719BActive Publication Date: 2026-11-17NOKIA TECHNOLOGIES OY
View PDF 2 Cites 0 Cited by

Patent Information

Application Number
CN202410012687.4
Authority / Receiving Office
CN · China
Patent Type
Patents(China)
Current Assignee / Owner
Priority Date
2016-09-13
Filing Date
2017-09-04
Publication Date
2026-11-17
Estimated Expiration
2037-09-04

AI Technical Summary

Technical Problem

During the RRC connection recovery process, when the user equipment moves to a new base station, the new base station lacks proper PDCP COUNT synchronization, resulting in integrity verification failure and inability to restore the connection.

Method used

A fixed-value PDCP COUNT synchronization mechanism is adopted, which ensures PDCP COUNT synchronization between the UE and the new base station by using a fixed HFN part (all bits set to 1) in the RRC connection recovery message for integrity protection.

Benefits of technology

This enables connection restoration without rebuilding during RRC connection recovery, improving the success rate and efficiency of connection recovery and reducing signaling overhead.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN117596719B_ABST
    Figure CN117596719B_ABST
Patent Text Reader

Abstract

Methods and apparatus including computer program products are provided for resuming a connection. In some example embodiments, a method may be provided comprising: receiving a Radio Resource Control (RFC) connection resumption message at a user equipment (UE); verifying the integrity of the received RFC connection resumption message at the UE, wherein the UE verifies integrity based on a predetermined value of a Packet Data Convergence Protocol (PaFC) superframe number; and resuming use of the suspended RFC connection by the UE upon successful integrity verification of the received RFC connection resumption message. Related systems, methods, and articles of art are also described.
Need to check novelty before this filing date? Find Prior Art

Description

[0001] This application is a divisional application of the invention patent application filed on September 4, 2017, with application number 201780056087.6 and invention title "PDCP COUNT processing in RRC connection recovery".

[0002] Cross-references to related applications

[0003] This application claims priority and benefit to U.S. Provisional Patent Application No. 62,394,057 (Attorney’s File: 49700-190P01US), filed September 12, 2016, entitled “PDCP COUNT HANDLING IN RRCCONNECTION RESUME”, the disclosure of which is incorporated herein by reference for all purposes. Technical Field

[0004] The topics described in this article relate to wireless. Background Technology

[0005] User equipment (UE) (such as smartphones, cellular phones, Internet of Things (IoT) devices, and / or other types of wireless devices accessing radio access networks including base stations) can suspend a connection and then resume it at a later time. For example, a radio resource control (RRC) connection can be suspended between the UE and a base station. In this case, some communications, such as user plane services between the UE and the base station, can be suspended. However, the UE and the base station can maintain the connection context, allowing them to quickly resume the RRC connection using the previous context without having to create a completely new RRC connection. The context may include radio bearer configuration information, security parameters, cell identifiers, physical layer configuration information, measurement and reporting configuration information, etc. Examples of connection suspension and RRC connection resumption can be found in TS 36.331. See, for example, 3GPP TS 36.331 V13.2.0 (2016-06), 3rd Generation Partnership Project; Technical Specification Group Radio Access Network; Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource Control (RRC); Protocol Specification, Version 13. Summary of the Invention

[0006] Methods and devices, including computer program products, are provided for restoring connections.

[0007] In some example embodiments, a method may be provided that includes receiving a Radio Resource Control Connection Resumption message at a user equipment; verifying the integrity of the received Radio Resource Control Connection Resumption message at the user equipment, wherein the user equipment verifies the integrity based on a predetermined value of a Packet Data Convergence Protocol superframe number; and resuming use of the suspended Radio Resource Control connection by the user equipment when the integrity verification of the received Radio Resource Control Connection Resumption message is successfully passed.

[0008] In some variations, one or more features disclosed herein, including the following features, may optionally be included in any feasible combination. When the use of a suspended connection is resumed, a Radio Resource Control (RFC) connection resumption completion message may be sent. Preset values ​​may be fixed to enable synchronization between the user equipment and the base station. Preset values ​​may include all bits set to the value 1. Use of the suspended RRC connection may only be resumed if the integrity verification of the received RRC connection resumption message is successfully passed. The base station may be different from the base station where the user equipment suspended RRC.

[0009] In some example embodiments, a method may be provided comprising: receiving at a base station a Radio Resource Control Connection Restoration Request message sent by a User Equipment; generating a Radio Resource Control Connection Restoration Message in response to the received Radio Resource Control Connection Restoration Request message; performing integrity protection on the Radio Resource Control Connection Restoration Message, wherein the integrity protection is performed based on a predetermined value of a Packet Data Convergence Protocol superframe number; and sending the Radio Resource Control Connection Restoration Message to the User Equipment, wherein the integrity of the Radio Resource Control Connection Restoration Message is protected.

[0010] In some variations, one or more features disclosed herein, including the following features, may optionally be included in any feasible combination: The ability to receive a Radio Resource Control Connection Restoration Request message to enable the restoration of a suspended Radio Resource Control connection. Preset values ​​may be fixed to enable synchronization between the user equipment and the base station. Preset values ​​may include all bits set to the value 1. The base station may be different from the base station where the user equipment has suspended Radio Resource Control.

[0011] The foregoing aspects and features can be implemented in systems, apparatus, methods, and / or articles according to desired configurations. Details of one or more variations of the subject matter described herein are set forth in the accompanying drawings and the following description. The features and advantages of the subject matter described herein will become apparent from the specification, the accompanying drawings, and the claims. Attached Figure Description

[0012] In the attached diagram,

[0013] Figure 1An example of a process for pausing and resuming a connection, according to some example embodiments, is described;

[0014] Figure 2A Another example of a process for pausing and resuming a connection, according to some example embodiments, is described;

[0015] Figure 2B An example of a PDCP COUNT is depicted according to some example embodiments;

[0016] Figure 3 Yet another example of a process for pausing and resuming a connection, according to some example embodiments, is described; and

[0017] Figure 4 Examples of apparatuses according to some example embodiments are depicted.

[0018] Similar labels are used in the accompanying drawings to refer to the same or similar items. Detailed Implementation

[0019] As noted, RRC connections can be suspended by user equipment and the network, and can be quickly restored by re-establishing the RRC connection using previously stored context information. When an RRC connection is suspended, this can also trigger a suspension of user plane service transmissions, such as PDCP (Packet Data Convergence Protocol) Protocol Data Unit (PDU) transmissions. PDCP can provide one or more services to RRC. These services may include control plane data transmission (e.g., via uplink and / or downlink), encryption, and / or integrity protection. PDCP can be implemented according to standards such as TS 36.323. See, for example, 3GPP TS 36.323 V13.2.0 (2016-06), 3GPP 3rd Generation Partnership Project; Technical Specification Group for Radio Access Networks; Evolved Universal Terrestrial Radio Access (E-UTRA); Packet Data Convergence Protocol (PDCP) Specification (Revision 13).

[0020] However, when a user equipment (UE) moves to a different base station (“new base station”) than the old base station that suspended the RRC connection, certain issues may arise in restoring the RRC connection. During restoration, both the UE and the old base station may have stored context information, but the new base station may lack certain portions of that context information to correctly restore the RRC connection. Specifically, the new base station may not have the correct last PDCP COUNT (e.g., the count or sequence number of the last PDCP Packet Data Unit (PDU)). In this case, the UE may fail to restore the connection because the lack of synchronization of the PDCP COUNT between the UE and the new base station could lead to integrity verification failure. This failure triggers the departure (as shown in Table 1 below, copied from TS 36.331) of the suspended RRC connection and the establishment of a new RRC connection.

[0021] TS 36.323 describes an example implementation of the PDCP COUNT that includes a PDCP sequence number (PDCP SN) and a superframe number (HFN), but other implementations of the PDCP COUNT can also be used. To limit signaling overhead, individual messages / packets (which can be sent between the UE and the base station) can include a short sequence number (PDCP SN) instead of the longer 32-bit PDCP COUNT (in which case the HFN will be synchronized between the base station and the UE).

[0022] Regarding the PDCP COUNT, it can be implemented according to TS.36.323. In this case, for each radio bearer, an independent counter, such as the PDCP COUNT (which can be specified by TS.36.323), can be maintained for each uplink and downlink. For each data radio bearer (DRB), the PDCP COUNT can be used as an input for encryption, while for each signaling radio bearer (SRB), the PDCP COUNT can be used for both encryption and integrity protection. Upon connection restoration, the PDCP COUNT can be reset for the PDUs exchanged after the RRC connection restoration.

[0023] While PDCP COUNTs can be wrapped or flipped, the same PDCP COUNT value may not be used multiple times for a given security key. For example, a base station could be responsible for preventing the use of radio bearer identities with the same key K. eNB The same PDCP COUNT value is reused. To avoid reuse, the base station can trigger an intra-cell handover or perform another action to renegotiate the key.

[0024] Table 1

[0025]

[0026] In some example embodiments, PDCPCOUNT synchronization can be provided between the UE and the base station during RRC connection suspension and resumption, regardless of whether the RRC connection is resumed at the same old base station where the RRC connection was suspended or at another new base station different from the so-called old base station. In some example embodiments, a predetermined value is used to perform PDCP COUNT synchronization.

[0027] In some example embodiments, at least a portion of the PDCP COUNT value used in the integrity protection and verification of the RRCConnectionResume message can be specified as a fixed predetermined value.

[0028] In some example embodiments, the HFN portion of the PDCP COUNT can be configured to a fixed predetermined value. This fixed value can set all bits to "1". After a PDCP reconstruction is invoked (which can be triggered by RRCConnectionResume), the UE's PDCP will expect the PDCP COUNT of the next PDU received on the SRB to be equal to zero, which is when the PDCP COUNT value is 2. 32 The next value in the PDCP COUNT after -1. Prescribing the fixed HFN portion of the PDCP COUNT value with all bits set to "1" maximizes the time before the fixed HFN portion of the PDCP COUNT value needs to be used again with the same key on the SRB (along with other connection parameters). Reusing previous COUNT values ​​should be avoided to reduce the need to trigger connection reconstruction, as described above. Even though the same PDCP COUNT value as the fixed HFN portion was previously used on the SRB at the base station (under which the UE's RRC connection is suspended), the previous use of the PDCP COUNT does not require resetting the RRC connection due to integrity protection, as the RRCConnectionResume message has already been processed with the new security key. In some implementations, the PDCP SN can also be fixed (e.g., with all bits set to "0" or all bits set to "1").

[0029] Figure 1 An example of a process 100 for processing a PDCP COUNT is depicted according to some example embodiments. The process depicts a user equipment 105 and a base station 110, such as an evolved Node B type base station (eNB), but other types of base stations and radio access points may also be used.

[0030] At point 112, according to some example embodiments, the RRC connection can be suspended. In this case, user plane service transmissions via the uplink and / or downlink can also be suspended. Furthermore, UE 105 and base station 110 (or other network nodes) can store the context associated with the suspended RRC connection between UE 105 and base station 110. The stored context may also include information related to the PDCP connection.

[0031] At 114, according to some example embodiments, UE 105 may send a message requesting the resumption of a suspended connection. For example, UE 105 may send an RRC connection resumption request message to base station 110.

[0032] Although 114 is requesting connection restoration to the same base station 110 where the RRC connection is suspended, the connection restoration request sent at 114 can be sent to other base stations, such as a new base station.

[0033] At 116, according to some example embodiments, base station 110 may send a connection restoration message. For example, base station 110 may send an RRC connection restoration message to UE 105 in response to message 114. In some example embodiments, a predetermined PDCP superframe number (HFN) may be used to protect the integrity of the RRC connection restoration message. This PDCP HFN is mapped to a PDCP COUNT value (e.g., 2 as described above). 32 -1). This predetermined PDCP HFN allows UE 105 and base station 110 to synchronize, even when UE 105 moves to another new base station after the initial pause and RRC connection context retention. In the case of a new base station, the new base station can obtain some context information instead of PDCP HFN or COUNT by signaling to the old base station or another network node, so the use of the predetermined value is minimal if any interruption occurs in this signaling.

[0034] At 118, according to some example embodiments, UE 105 can verify the integrity of the received RRC connection recovery message based on a predetermined PDCP HFN. If the verification is confirmed, the UE can resume the use of the previously suspended RRC connection. If the verification is not confirmed (e.g., the UE's expected PDCP COUNT and the PDCP COUNT used for integrity protection of message 116 do not match), the UE leaves the RRC connection, and therefore the UE does not reuse the previously suspended RRC connection (in this case, the UE can request a new RRC connection).

[0035] At 120, according to some example embodiments, the UE may send an RRC connection restoration complete message to the base station 110 to instruct the UE to resume the use of the previously suspended RRC connection.

[0036] Figure 2A An example of procedure 200 for processing a PDCP COUNT is depicted according to some example embodiments. Procedure 200 is similar in some respects to procedure 100, but in the case of procedure 200, the predetermined PDCP HFN is configured with all bits set to "1". At 218, UE 105 may request a lower layer to verify the integrity protection of the RRCConnectionResume message received at 216. For example, assuming the predetermined HFN, if the UE (or its lower layer) successfully verifies the integrity of the RRCConnectionResume message, the UE can use the context of that connection to enter or resume RRC connection mode. If verification fails, the UE does not resume the RRC connection and therefore leaves the RRC connection. Table 2 below depicts example RRC specification text for 218.

[0037] Table 2

[0038]

[0039] At 120, according to some example embodiments, the UE may send an RRC connection restoration complete message to the base station 110 to instruct the UE to resume the use of the previously suspended RRC connection.

[0040] Figure 2B An example of a PDCP COUNT according to some example embodiments is depicted. In the example shown, the HFN can have all its bits set to 1. When both the UE and the base station use a predetermined HFN value, the HFN used will be unambiguous, and the PDCP COUNT between the UE and the base station will be synchronized (assuming PDCP SN synchronization), therefore, the integrity verification performed on the message will pass. PDCP SN synchronization can be achieved in different ways. As an example, the PDCP SN included in the header of the PDCP PDU containing the RRC connection recovery message can be used. As another example, a predetermined value can also be used for the PDCP SN.

[0041] Figure 3 An example of a process 300 for processing a PDCP COUNT is described according to some example embodiments. Figure 3 Two base stations, 110 and 310, are shown. The first base station, 110, is where the RRC connection is suspended, while the second base station is where the RRC connection is restored.

[0042] At 312, according to some example embodiments, the RRC connection between UE 105 and base station 110 can be suspended. Furthermore, user plane service transmissions via uplink and / or downlink can also be suspended. Additionally, UE 105 and base station 110 can store the context and / or PDCP context associated with the suspended RRC connection. At 314, according to some example embodiments, UE 105 can send an RRC connection restoration request message to another base station 310. At 316, according to some example embodiments, the new base station 310 can send a connection restoration message. The RRC connection restoration message can be protected for integrity using a PDCPHFN with predetermined values ​​(such as all bits set to "1"). In some example embodiments, the new base station 310 can obtain some contextual information about the suspended connection (e.g., from base station 110 or another node) rather than the PDCP COUNT or SN. At 318, according to some example embodiments, UE 105 can verify the integrity of the received RRC connection restoration message. This verification can be performed at 118 and / or 218 as described above. At 320, according to some example embodiments, the UE may send an RRC connection restoration complete message to the base station 310 to instruct the UE to resume use of the previously suspended RRC connection.

[0043] In the example of process 300, the base station may receive a Radio Resource Control Connection Restoration Request message sent by a User Equipment (UE). In response to the received Radio Resource Control Connection Restoration Request message, the base station may generate a Radio Resource Control Connection Restoration message. The base station may perform integrity protection on the Radio Resource Control Connection Restoration message. Integrity protection may be performed based on a predetermined value of the Packet Data Convergence Protocol (PaGP) superframe number. The base station may also transmit the Radio Resource Control Connection Restoration message to the UE, wherein the Radio Resource Control Connection Restoration message is integrity protected.

[0044] Figure 4 A block diagram of apparatus 10 according to some example embodiments is shown. Apparatus 10 (or portions thereof) may be configured to provide radio, such as user equipment 105 and / or base station 110 and / or 310. The apparatus may be implemented as any device, including wireless devices, smartphones, cellular phones, machine-type communication devices, wireless sensors, radio relays, access points, and / or any other radio including processors and memory-based devices.

[0045] In some example embodiments, device 10 may be configured to support processing of fixed or predetermined PDCPHFN as described herein.

[0046] Device 10 may include at least one antenna 12 communicating with transmitter 14 and receiver 16. Alternatively, the transmitting and receiving antennas may be separate. Device 10 may also include a processor 20 configured to provide signals to and from the transmitter and receiver, respectively, and to control the functions of the device. Processor 20 may be configured to control the functions of the transmitter and receiver by implementing control signaling via electrical leads to the transmitter and receiver. Similarly, processor 20 may be configured to control other elements of device 10 by implementing control signaling via electrical leads connecting processor 20 to other elements, such as displays or memory. Processor 20 may be implemented, for example, in a variety of ways, including circuitry, at least one processing core, one or more microprocessors with an accompanying digital signal processor, one or more processors without an accompanying digital signal processor, one or more coprocessors, one or more multi-core processors, one or more controllers, processing circuitry, one or more computers, various other processing elements including integrated circuits (e.g., application-specific integrated circuits (ASICs), field-programmable gate arrays (FPGAs), etc.), or some combination thereof. Therefore, although in Figure 4 The processor is shown as a single processor, but in some example embodiments, processor 20 may include multiple processors or processing cores.

[0047] The signals transmitted and received by the processor 20 may include signaling information conforming to the applicable cellular system air interface standard, and / or any number of different wired or wireless networking technologies, including but not limited to Wi-Fi, Wireless Local Access Network (WLAN) technologies, such as IEEE 802.11, 802.16, etc. Additionally, these signals may include voice data, user-generated data, user-requested data, etc.

[0048] Device 10 can operate using one or more air interface standards, communication protocols, modulation types, access types, etc. For example, device 10 and / or its cellular modem can operate according to various first-generation (1G) communication protocols, second-generation (2G or 2.5G) communication protocols, third-generation (3G) communication protocols, fourth-generation (4G) communication protocols, Internet Protocol Multimedia Subsystem (IMS) communication protocols (e.g., Session Initiation Protocol (SIP), etc.). For example, device 10 can operate according to 2G wireless communication protocols such as IS-136, Time Division Multiple Access (TDMA), Global System for Mobile Communications (GSM), IS-95, Code Division Multiple Access (CDMA), etc. Furthermore, for example, device 10 can operate according to 2.5G wireless communication protocols such as General Packet Radio Service (GPRS), Enhanced Data GSM Environment (EDGE), etc. Furthermore, for example, device 10 can operate according to 3G wireless communication protocols, such as Universal Mobile Telecommunications System (UMTS), Code Division Multiple Access 2000 (CDMA2000), Wideband Code Division Multiple Access (WCDMA), and Time Division Synchronous Code Division Multiple Access (TD-SCDMA). Device 10 can also operate according to 3.9G wireless communication protocols, such as Long Term Evolution (LTE) and Evolved Universal Terrestrial Radio Access Network (E-UTRAN). Additionally, for example, device 10 can operate according to 4G wireless communication protocols, such as Advanced LTE, 5G, and similar wireless communication protocols that may be developed subsequently.

[0049] It is understood that processor 20 may include circuitry for implementing the audio / video and logic functions of device 10. For example, processor 20 may include a digital signal processor device, a microprocessor device, an analog-to-digital converter, a digital-to-analog converter, etc. The control and signal processing functions of device 10 can be distributed among these devices according to their respective capabilities. Processor 20 may additionally include an internal voice encoder (VC) 20a, an internal data modem (DM) 20b, etc. Furthermore, processor 20 may include the ability to operate one or more software programs that can be stored in memory. Typically, processor 20 and the stored software instructions can be configured to cause device 10 to perform actions. For example, processor 20 may be able to operate a connectivity program, such as a web browser. The connectivity program may allow device 10 to send and receive network content, such as location-based content, according to protocols such as Wireless Application Protocol, WAP, Hypertext Transfer Protocol, HTTP, etc.

[0050] Device 10 may also include a user interface operatively coupled to processor 20, including, for example, headphones or speaker 24, ringer 22, microphone 26, display 28, user input interface, etc. As described above, display 28 may include a touch-sensitive display, where a user can touch and / or gesture to make selections, input values, etc. Processor 20 may also include user interface circuitry configured to control at least some functions of one or more elements of the user interface (such as speaker 24, ringer 22, microphone 26, display 28, etc.). Processor 20 and / or the user interface circuitry including processor 20 may be configured to control one or more functions of one or more elements of the user interface via computer program instructions (e.g., software and / or firmware) stored in memory accessible to processor 20 (e.g., volatile memory 40, non-volatile memory 42, etc.). Device 10 may include a battery for powering various circuitry associated with the mobile terminal, such as circuitry for providing mechanical vibration as a detectable output. The user input interface may include devices that allow device 20 to receive data, such as keypad 30 (which may be a virtual keyboard displayed on display 28 or an externally coupled keyboard) and / or other input devices.

[0051] like Figure 4 As shown, device 10 may also include one or more mechanisms for sharing and / or acquiring data. For example, device 10 may include a short-range radio frequency (RF) transceiver and / or interrogator 64, so that data can be shared with and / or acquired from electronic devices according to RF technology. Device 10 may include other short-range transceivers, such as infrared (IR) transceiver 66, Bluetooth™ (BT) transceiver 68 operating using Bluetooth™ wireless technology, wireless universal serial bus (USB) transceiver 70, Bluetooth™ low-energy transceiver, ZigBee transceiver, ANT transceiver, cellular device-to-device transceiver, wireless local area link transceiver, and / or any other short-range radio technology. For example, device 10, and in particular the short-range transceiver, may be able to transmit data to and / or receive data from electronic devices in the vicinity of the device (e.g., within 10 meters). The device 10, including a Wi-Fi or wireless LAN modem, may also be able to send and / or receive data from electronic devices according to various wireless network technologies, including 6LoWpan, Wi-Fi, Wi-Fi Low Power, WLAN technology, such as IEEE 802.11 technology, IEEE 802.15 technology, IEEE 802.16 technology, etc.

[0052] Device 10 may include memory capable of storing information elements related to mobile users, such as a Subscriber Identity Module (SIM) 38, a Removable User Identity Module (R-UIM), an eUICC, a UICC, etc. In addition to the SIM, device 10 may also include other removable and / or fixed memory. Device 10 may include volatile memory 40 and / or non-volatile memory 42. For example, volatile memory 40 may include random access memory (RAM), including dynamic and / or static RAM, on-chip or off-chip cache memory, etc. The embedded and / or removable non-volatile memory 42 may include, for example, read-only memory, flash memory, magnetic storage devices such as hard disks, floppy disk drives, magnetic tape, optical disk drives and / or media, non-volatile random access memory (NVRAM), etc. Similar to volatile memory 40, non-volatile memory 42 may include cache areas for temporary data storage. At least a portion of the volatile and / or non-volatile memory may be embedded in processor 20. The memory may store one or more software programs, instructions, information, data, etc., that can be used by the device to perform the operations disclosed herein with respect to user equipment and / or base stations (see, for example, processes 100, 200, and / or 300). The memory may include identifiers capable of uniquely identifying device 10, such as International Mobile Equipment Identity (IMEI) codes. In an example embodiment, processor 20 may use computer code stored in memories 40 and / or 42 to be configured to control and / or provide one or more aspects disclosed herein with respect to user equipment and / or base stations (see, for example, processes 100, 200, and / or 300).

[0053] Some embodiments disclosed herein can be implemented using software, hardware, application logic, or a combination of software, hardware, and application logic. For example, the software, application logic, and / or hardware may reside on memory 40, control device 20, or electronic components. In some example embodiments, the application logic, software, or instruction set is held on any of a variety of conventional computer-readable media. In the context of this document, "computer-readable medium" can be any non-transitory medium that can contain, store, transmit, propagate, or transfer instructions for use by or in conjunction with an instruction execution system, apparatus, or device (such as computer or data processor circuitry), examples of which are provided in [document name missing]. Figure 4 As described herein, a computer-readable medium may include a non-transitory computer-readable storage medium, which may be any medium that can contain or store instructions for use by or in connection with an instruction execution system, apparatus or device (such as a computer).

[0054] Without limiting the scope, interpretation, or application of the claims that follow in any way, the technical effects of one or more example embodiments disclosed herein are enhanced use of radio resources, including RRC connection suspension and resumption.

[0055] Depending on the desired configuration, the subjects described herein can be implemented in systems, apparatuses, methods, and / or articles. For example, the base stations and user equipment (or one or more components thereof) and / or processes described herein can be implemented using one or more of the following: a processor executing program code, an application-specific integrated circuit (ASIC), a digital signal processor (DSP), an embedded processor, a field-programmable gate array (FPGA), and / or combinations thereof. These various implementations can include implementations in one or more computer programs executable and / or interpretable on a programmable system comprising at least one programmable processor (which may be dedicated or general-purpose), the at least one programmable processor being coupled to receive and transmit data and instructions from and to a storage system, at least one input device, and at least one output device. These computer programs (also referred to as programs, software, software applications, applications, components, program code, or code) include machine instructions for the programmable processor and can be implemented using high-level procedural and / or object-oriented programming languages ​​and / or assembly / machine languages. As used herein, the term "computer-readable medium" means any computer program product, machine-readable medium, computer-readable storage medium, apparatus, and / or device (e.g., magnetic disk, optical disk, memory, programmable logic device (PLD)) used to provide machine instructions and / or data to a programmable processor, including machine-readable media that receive machine instructions. Similarly, systems that may include a processor and memory coupled to the processor are also described herein. Memory may include one or more programs that cause the processor to perform one or more operations described herein.

[0056] While some variations have been described in detail above, other modifications or additions are possible. In particular, additional features and / or variations may be provided in addition to those described herein. Furthermore, the above implementations may involve various combinations and sub-combinations of the disclosed features and / or combinations and sub-combinations of several other features disclosed above. Other embodiments are within the scope of the following claims.

[0057] If necessary, the different functions discussed herein may be performed in different orders and / or simultaneously with each other. Furthermore, if necessary, one or more of the above functions may be optional or may be combined. Although various aspects of some embodiments are set forth in the independent claims, other aspects of some embodiments include other combinations of features from the described embodiments and / or dependent claims with features of the independent claims, not just those expressly set forth in the claims. It should also be noted herein that while exemplary embodiments have been described above, these descriptions should not be considered limiting. Rather, several variations and modifications may be made without departing from the scope of some embodiments defined in the appended claims. Other embodiments may fall within the scope of the following claims. The term “based on” includes “at least based on”. Unless otherwise stated, the phrase “such as” is used to mean “such as, for example”.

Claims

1. A method for communication, the method comprising: Receive the Radio Resource Control Connection Restoration Message at the user equipment; The integrity of the received Radio Resource Control Connection Restoration message is verified at the user equipment, wherein the user equipment verifies the integrity based on a predetermined value of a Packet Data Convergence Protocol (PDCP) superframe number, wherein the PDP superframe number comprises a plurality of bits, each bit being set to the same predetermined value. as well as If the user equipment successfully verifies the integrity of the received radio resource connection restoration message, the user equipment resumes use of the suspended radio resource control connection.

2. The method according to claim 1, further comprising: When the use of the suspended connection is restored, a Radio Resource Control Connection Restoration Complete message is sent.

3. The method of claim 1, wherein the predetermined value is fixed to enable synchronization between the user equipment and the base station.

4. The method according to any one of claims 1 to 3, wherein the use of the suspended radio resource control connection is restored only upon successful integrity verification of the received radio resource connection recovery message.

5. The method of claim 3, wherein the base station is different from the base station where the user equipment suspends the radio resource control connection.

6. A method for communication, the method comprising: At the base station, receive radio resource control connection restoration request messages sent by user equipment; In response to the received Radio Resource Control Connection Restoration Request message, a Radio Resource Control Connection Restoration message is generated; Integrity protection is performed on the radio resource connection restoration message, wherein the integrity protection is performed based on a predetermined value of the packet data convergence protocol superframe number, wherein the packet data convergence protocol superframe number comprises a plurality of bits, each bit being set to the same predetermined value; as well as The radio resource control connection restoration message is sent to the user equipment, wherein the radio resource control connection restoration message is protected by integrity.

7. The method of claim 6, wherein the radio resource control connection restoration request message is received to enable the restoration of a suspended radio resource control connection.

8. The method of claim 6, wherein the predetermined value is fixed to enable synchronization between the user equipment and the base station.

9. The method according to any one of claims 6 to 8, wherein the base station is different from the base station where the user equipment suspends the radio resource control connection.

10. A user equipment for communication, the user equipment comprising: At least one processor; as well as At least one memory storing instructions that, when executed by the at least one processor, cause the user equipment to perform at least the following: Receives a radio resource control connection restoration message; The integrity of the received Radio Resource Control Connection Restoration message is verified, wherein the user equipment verifies the integrity based on a predetermined value of a Packet Data Convergence Protocol (PDCP) superframe number, wherein the PDCP superframe number comprises a plurality of bits, each bit being set to the same predetermined value. as well as If the user equipment successfully verifies the integrity of the received radio resource connection restoration message, the use of the suspended radio resource control connection is restored.

11. The user equipment of claim 10, wherein the user equipment is further configured to at least: send a radio resource control connection restoration complete message when use of the suspended connection is restored.

12. The user equipment of claim 10, wherein the predetermined value is fixed to enable synchronization between the user equipment and the base station.

13. The user equipment of claim 10, wherein the use of the suspended radio resource control connection is restored only upon successful integrity verification of the received radio resource connection recovery message.

14. The user equipment of claim 12, wherein the base station is different from the base station where the user equipment suspends the radio resource control connection.

15. A base station for communication, the base station comprising: At least one processor; as well as At least one memory storing instructions that, when executed by the at least one processor, cause the base station to perform at least the following: Receive a Radio Resource Control Connection Restoration Request message sent by a user equipment; In response to the received Radio Resource Control Connection Restoration Request message, a Radio Resource Control Connection Restoration message is generated; Integrity protection is performed on the radio resource connection restoration message, wherein the integrity protection is performed based on a predetermined value of the packet data convergence protocol superframe number, wherein the packet data convergence protocol superframe number comprises a plurality of bits, each bit being set to the same predetermined value; as well as The radio resource control connection restoration message is sent to the user equipment, wherein the radio resource control connection restoration message is protected by integrity.

16. The base station of claim 15, wherein the radio resource control connection restoration request message is received to enable the restoration of a suspended radio resource control connection.

17. The base station of claim 15, wherein the predetermined value is fixed to enable synchronization between the user equipment and the base station.

18. The base station of claim 17, wherein the base station is different from the base station where the user equipment suspends the radio resource control connection.

19. A non-transitory computer-readable storage medium comprising program code that, when executed by at least one processor, causes operations including: Receive the Radio Resource Control Connection Restoration Message at the user equipment; The integrity of the received Radio Resource Control Connection Restoration message is verified at the user equipment, wherein the user equipment verifies the integrity based on a predetermined value of a Packet Data Convergence Protocol (PDCP) superframe number, wherein the PDP superframe number comprises a plurality of bits, each bit being set to the same predetermined value. as well as If the user equipment successfully verifies the integrity of the received radio resource connection restoration message, the user equipment resumes use of the suspended radio resource control connection.

20. A non-transitory computer-readable storage medium comprising program code that, when executed by at least one processor, causes operations including: At the base station, receive radio resource control connection restoration request messages sent by user equipment; In response to the received Radio Resource Control Connection Restoration Request message, a Radio Resource Control Connection Restoration message is generated; Integrity protection is performed on the radio resource connection restoration message, wherein the integrity protection is performed based on a predetermined value of the packet data convergence protocol superframe number, wherein the packet data convergence protocol superframe number comprises a plurality of bits, each bit being set to the same predetermined value; as well as The radio resource control connection restoration message is sent to the user equipment, wherein the radio resource control connection restoration message is protected by integrity.

Citation Information

Patent Citations

  • Method and apparatus for handling out-of-order packets during handover in a wireless communication system

    CN102938912A

  • Counter check procedure for packet data transmission

    WO2011133934A1