KR20200043457A - Methods and devices for NR PDCP preservation at RRC resumption / pause - Google Patents

Abstract

A method for use in a user equipment (UE) for resuming a radio bearer in a wireless communication network includes: establishing a radio resource control (RRC) connection with a first network node; Receiving a suspension message from the first network node; Storing the configuration of the radio bearer associated with the RRC connection; Suspending the radio bearer associated with the RRC connection; Receiving a connection resume message; Determining whether the connection resumption message includes configuration information for the NR packet data convergence protocol (PDCP) for the suspended radio bearer; When determining that the connection resume message includes configuration information for the NR PDCP, using the configuration information, configuring the suspended radio bearer; And resuming the suspended radio bearer.

Description

Methods and devices for NR PDCP preservation at RRC resumption / pause

Certain embodiments relate to wireless communications, and more particularly, to preserve new radio (NR) packet data convergence protocol (PDCP) connections upon resuming a suspended radio resource control (RRC) connection. It is about.

The 3rd Generation Partnership Project (3GPP) defines the 5th generation (5G) wireless communication including the NR. In a typical wireless, cellular, or radio communication network, wireless devices, also known as mobile stations, terminals, and / or user equipment (UE), communicate with one or more core networks via a radio access network (RAN). Communicate. The RAN is responsible for the geographic area divided into cells. Each cell is served by a base station (eg, a radio base station (RBS), or a network node, which in some networks may also be referred to as “NodeB”, “eNodeB”, or “eNB”, for example). A cell is a geographical area in which radio coverage is provided by a radio base station at an antenna site or base station site when the antenna and the radio base station are not in common location. One radio base station can serve one or more cells.

The specification for the evolved packet system (EPS) has been completed within 3GPP, and this work continues in subsequent 3GPP releases. EPS is an evolved universal terrestrial radio access network (E-UTRAN), also known as Long Term Evolution (LTE), radio access, and an evolved packet core also known as a system architecture evolution (SAE) core network. (EPC). E-UTRAN / LTE is a variant of 3GPP radio access technology in which wireless base station nodes are directly connected to the EPC core network, not RNCs. In general, in E-UTRAN / LTE, the functions of the RNC are distributed between wireless base station nodes (eg, eNodeBs in LTE) and the core network. The RAN of EPS essentially has a flat architecture that includes radio base station nodes that do not report to RNCs.

Radio resource control (RRC) can be used in the control plane. The main functions for the control plane include: broadcast of system information for both non-access stratum (NAS) and access stratum (AS) paging; RRC connection processing; Allocation of temporary identifiers for the UE; Configuration of signaling radio bearer (s) for RRC connection; Processing of radio bearers; Quality of service (QoS) management functions; Security functions including key management; Mobility functions (including UE measurement reporting and control of such reporting, handover, UE cell selection and reselection, and control of cell selection and reselection); And NAS direct message transfer to / from the UE.

There is one packet data convergence protocol (PDCP) entity for each radio bearer for the UE. PDCP is used for both the control plane (ie RRC) and user plane (ie user data received via GPRS tunneling protocol-user tunneling (GTP-U) signaling). The main functions of the control plane are encryption / decryption and integrity protection. The main functions of the user plane include: encryption / decryption, header compression using robust header compression (ROHC) and decompression and sequential delivery, duplication detection and retransmission.

LTE includes dual connectivity features. E-UTRAN supports dual connectivity (DC) operation, whereby multiple Rx / Tx UEs of RRC_CONNECTED are provided by two separate schedulers located at two eNBs connected via non-ideal backhaul via the X2 interface. It is configured to utilize the radio resources (see 3GPP 36.300). The eNB involved in DC for a particular UE can assume two different roles, that is, the eNB can act as a master node (MN) or as a secondary node (SN). In DC, the UE is connected to one MN and one SN.

In LTE DC, the radio protocol architecture used by a specific bearer depends on how the bearer is established. There are three bearer types: master cell group (MCG) bearer, secondary cell group (SCG) bearer and split bearer. The RRC is located in the MN, and signaling radio bearers (SRBs) are always configured as the MCG bearer type, and thus use only the radio resources of the MN. An example is shown in FIG. 1.

1 is a block diagram illustrating an LTE dual connectivity user plane. The master node includes an MCG bearer and a split bearer. The secondary node includes an SCG bearer.

LTE-NR also includes dual connectivity. LTE-NR (NR) DC may also be referred to as LTE-NR close interworking. The main changes from LTE DC are: (a) Introduction of split bearer from SN (known as SCG split bearer); (b) introduction of split bearers for RRC; And (c) direct RRC from SN (also referred to as SCG SRB). Examples are illustrated in FIGS. 2 and 3.

2 is a block diagram illustrating an LTE-NR closely linked user plane. The master node includes an MCG bearer and an MCG split bearer. The secondary node includes an SCG bearer and an SCG split bearer.

3 is a block diagram illustrating an LTE-NR closely interlocked control plane. 3 illustrates the protocol layer interaction between the master node, secondary node, and user equipment.

SN is sometimes referred to as SgNB (where gNB is the NR base station), and MN is referred to as MeNB when LTE is the master node and NR is the secondary node. In other cases where NR is the master and LTE is the secondary node, the corresponding terms are SeNB and MgNB.

Split RRC messages are mainly used to generate diversity, and the sender can decide to choose one of the links for scheduling RRC messages, or can duplicate the message over both links. In the downlink, path switching between MCG and SCG legs or replication on both depends on the network implementation. On the other hand, for the uplink, the network configures the UE to use MCG, SCG, or both legs. The terms "leg" and "path" are used interchangeably herein.

To distinguish different dual connectivity scenarios, the following terminology is used: DC: LTE DC (ie, both MN and SN use LTE); EN-DC: LTE-NR dual connectivity, where LTE is the master and NR is secondary; NE-DC: LTE-NR dual connectivity, where NR is the master and LTE is secondary; NR-DC (or NR-NR DC): both MN and SN use NR; And MR-DC (Multi-RAT DC): MN and SN are general terms to describe the case of using different RATs (EN-DC and NE-DC are two different exemplary cases of MR-DC).

The NR harmonizes what is previously referred to as MCG bearers, MCG split bearers, SCG bearers and SCG split bearers in the following manner. For all bearers, it is possible to configure the UE to use NR PDCP (even when the UE is operating in a standalone LTE mode and EN-DC is not set). For all bearers configured with NR PDCP, it is possible to configure the UE to use KeNB or S-KeNB as a security key. The configuration of PDCP layers is separated from the configuration of lower layers of MCG and SCG legs.

From the UE perspective, there are only three different bearers (as shown in FIG. 4), that is, (a) an MCG bearer using only the radio of the MN node; (b) an SCG bearer using only the radio of the SN node; And (c) a split bearer using both MN and SN radios.

4 is a block diagram illustrating three dual connectivity bearers from the perspective of user equipment. Where bearers are terminated in the network is no longer important from the perspective of the UEs (i.e., the UE will only use keys configured from each bearer). The NR supports MCG bearer termination at SN nodes and SCG bearer termination at MN nodes using S-KeNB. Similarly, it is possible to support both SN and MN termination bearers (i.e., both SN termination segmentation bearers and MN termination segmentation bearers) simultaneously.

LTE includes RRC suspend and resume functionality. A suspended UE can be considered to be in an intermediate state between idle and connected, where the UE AS context is maintained in both the UE and the RAN, and the UE is in connected mode from the perspective of the core network (CN) and the RAN From a perspective, it may appear to be in idle mode. The advantage of operating in this mode is to reduce signaling towards the CN and transition to a connected mode faster compared to legacy idle-connected mode transitions, while maintaining UE power saving benefits of idle mode. Both LTE rel-15 and NR may support an enhanced suspend / resume functional version (referred to as a lightly connected UE in LTE and inactive mode in NR).

In LTE, when the network decides to move the UE to an inactive state, the eNB sends an RRCConnectionRelease message with the release cause value of rrc -suspend to the UE, and the resume ID is also provided to it. The UE stores resumeIdentity and UE AS context (including current RRC configuration, current security context, PDCP state including ROHC state, C-RNTI used in the source PCell, cellIdentity of the source PCell, and physical cell identity), Reset all RLC entities (for both SRBs and DRBs) and suspend SRBs except for all DRBs and SRB0. An example is shown in FIG. 5.

5 is a sequence diagram illustrating an RRC connection suspend procedure. In step 1, based on some triggers (eg, expiration of the UE inactivity timer), the eNB decides to suspend the RRC connection. In step (2), the eNB initiates the S1-AP UE context suspension procedure to inform the MME that the RRC connection is suspended. In step (3), the MME requests the S-GW to release all S1-U bearers for the UE. In step (4), the MME acknowledges step (2). In step (5), eNB has to suspend the RRC connection by releaseCause sends the message set to RRCConnectionRelease rrc-Suspend. The message includes resumeIdentity stored by the UE. In step 6, the UE stores the AS context, suspends all SRBs and DRBs, and the UE enters the RRC_IDLE lightweight connection state.

When the UE wants to resume the connection later (in response to a paging request for uplink data or downlink data to be transmitted), it sends an RRCConnectionResumeRequest message with the saved resumeIdentity . The eNB responds with an RRCConnectionResume message, both the UE and the eNB restore the stored UE context, and data transmission / reception to / from the UE can be resumed.

The resume operation may be performed at the eNB except for the eNB serving the UE when the UE is suspended. In that case, the new eNB may perform context fetching, for example, by using the UE context search procedure from the previous eNB (because resumeIdentity includes information about the previous eNB / cell). Examples are illustrated in FIGS. 6 and 7.

6 is a sequence diagram illustrating an RRC connection resumption procedure at the same eNB. In step (1), at some later point in time (eg, when the UE is being paged or when new data has reached the uplink buffer), the UE resumes the connection by sending an RRCConnectionResumeRequest to the eNB. The UE includes its resume ID, reason for establishment, and authentication token. The authentication token is calculated in the same way as the short MAC-I used in RRC connection reconfiguration, and enables the eNB to verify the UE identity.

In step (2), if the resume ID exists and the authentication token is successfully verified, the eNB responds with RRCConnectionResume . The message includes the next hop chaining count (NCC) value required to reset the AS security.

In step (3), the UE resumes all SRBs and DRBs and resets AS security. The UE is now in RRC_CONNECTED. In step (4), the UE responds with RRCConnectionResumeComplete confirming that the RRC connection has been successfully resumed. In step 5, the eNB initiates the S1-AP context resume procedure to notify the MME about the UE state change. In step 6, the MME requests the S-GW to activate S1-U bearers for the UE. In step 7, the MME acknowledges step 5.

7 is a sequence diagram illustrating an RRC connection resumption procedure in a new eNB. Step (1) is the same as step (1) in FIG. 6. In step (2), the new eNB uses the resume ID to locate the previous eNB, and searches for the UE context by the X2-AP UE context search procedure. In step 3, the previous eNB responds with the UE context associated with the resume ID.

Steps 4-6 are the same as steps 2-4 in FIG. 6, respectively. In step (7), the new eNB initiates the S1-AP path switching procedure to establish an S1 UE associated signaling connection to the serving MME and request the MME to resume the UE context.

In step 8, the MME requests the S-GW to activate S1-U bearers for the UE and updates the downlink path. In step 9, the MME acknowledges step 7. In step 10, after the S1-AP path switching procedure, the new eNB triggers the release of the UE context at the previous eNB by the X2-AP UE context release procedure.

The particular problem is that the existing RRC messages cannot handle all the scenarios described above correctly. The contents of the RRCConnectionResume message and the optional RadioResourceConfigDedicated IE included therein are as follows:

RRCConnectionResume message

RadioResourceConfigDedicated information element

As can be seen from above, DRB ToAddMod-IE that may be included in the IE RadioResourceConfigDedicated include LTE PDCP configuration for the bearer.

It is assumed that when the UE is suspended, some of the bearers are using NR PDCP. This may be because the UE may have been operating in EN-DC mode or even in a standalone LTE mode. The NR can allow the configuration of the NR PDCP without the UE being in EN-DC as long as the UE is NR capable. When such a UE is resumed by receiving the RRCResume message shown above, since the only PDCP configuration available is LTE pdcp-config IE, any bearer resumed will have to use LTE PDCP. Also, since no pdcp-config is included in SRB-To-AddMod, SRBs will not resume with NR PDCP if they were using NR PDCP before suspending.

Thus, a particular problem is that applying RRC resume, as in legacy LTE, results in implicit conversion of the PDCP type of all suspended bearers to LTE PDCP upon resume.

Accordingly, additional reconfiguration is required to change the PDCP back to NR PDCP. This results in unnecessary disruption due to PDCP / RLC resets and possibly RLC / MAC resets that may be required to convert the PDCP version back from LTE to NR. Reconfiguration can disrupt ongoing traffic, which can mean that a longer time is used to ramp up the TCP window.

In addition, one of the advantages of using NR PDCP is that, for standalone LTE, further transitions to EN-DC further CN signaling by setting the endpoint of the associated bearer in the MN or SN (transparent to the UE). It is a possibility that can be performed without. In converting all bearers back to LTE PDCP, the endpoint of these bearers must be changed to MN (if not started with MN), thereby causing unnecessary CN signaling.

Additionally, if the UE was initially in the eNB supporting NR mode, is suspended, and resumed from the eNB not supporting NR mode, an error case may occur. This is because if the pdcp-config to be included in the DRB-ToAddMod is arbitrary, and the network does not want to change the configuration of the UE upon resumption, it may not include arbitrary fields. That is, the UE may eventually resume to the NR PDCP version, while the serving eNB does not understand the NR PDCP. Therefore, after resuming or even in the meantime, communication between the UE and the eNB may not be possible.

The embodiments described herein implicitly convert to all bearers of the user equipment (UE) upon resumption to use the LTE Packet Data Convergence Protocol (PDCP) even if they were using the NR PDCP version. Resolves the specific problems of the current Long Term Evolution (LTE) Resumption / Suspension Procedures that result in being.

According to some embodiments, a method for use in a user equipment (UE) for resuming a radio bearer in a wireless communication network includes: establishing a radio resource control (RRC) connection with a first network node; Receiving a suspension message from the first network node; Storing the configuration of the radio bearer associated with the RRC connection; Suspending the radio bearer associated with the RRC connection; Receiving a connection resume message; Determining whether the connection resumption message includes configuration information for the NR PDCP for the suspended radio bearer; When determining that the connection resume message includes configuration information for the NR PDCP, using the configuration information, configuring the suspended radio bearer; And resuming the suspended radio bearer.

In certain embodiments, the established RRC connection includes an NR PDCP bearer or LTE PDCP bearer. The connection resume message may be received from a second network node different from the first network node.

In certain embodiments, configuring the suspended radio bearer includes using configuration information and stored configuration information in the connection resume message. Configuration information in the connection resume message may take precedence over stored configuration information. The configuration information in the connection resume message may include security information different from the security information used before the suspension of the radio bearer.

In certain embodiments, the method further includes resuming the suspended radio bearer as an LTE PDCP bearer upon determining that the connection resume message does not include configuration information for the NR PDCP for the suspended radio bearer. . The method includes: establishing a signaling radio bearer 1 (SRB1) NR PDCP connection with the first network node; And converting the SRB1 connection to the LTE PDCP connection when receiving the connection suspension message (920). The connection resume message is received over the SRB1 connection.

According to some embodiments, the UE may resume the radio bearer in the wireless communication network. The UE includes processing circuitry, the processing circuitry: establishing an RRC connection with the first network node; Receive a suspension message from the first network node; Store the configuration of the radio bearer associated with the RRC connection; Suspend the radio bearer associated with the RRC connection; Receive a connection resume message; Determine whether the connection resumption message includes configuration information for the NR PDCP for the suspended radio bearer; Upon determining that the connection resumption message includes configuration information for the NR PDCP, configure the suspended radio bearer using the configuration information; It is operable to resume the suspended radio bearer.

In certain embodiments, the established RRC connection includes an NR PDCP bearer or LTE PDCP bearer. The connection resume message may be received from a second network node different from the first network node.

In certain embodiments, the processing circuitry is operable to configure the suspended radio bearer by using configuration information and stored configuration information in the connection resume message. Configuration information in the connection resume message may take precedence over stored configuration information. The configuration information in the connection resume message may include security information different from the security information used before the suspension of the radio bearer.

In certain embodiments, the processing circuitry is further operable to resume the suspended radio bearer as an LTE PDCP bearer upon determining that the connection resume message does not include configuration information for the NR PDCP for the suspended radio bearer. Do. The processing circuit establishes an SRB1 NR PDCP connection with the first network node; Upon receiving the connection suspension message, it may be further operable to convert the SRB1 connection to an LTE PDCP connection. The processing circuitry is operable to receive a connection resume message over the SRB1 connection.

According to some embodiments, a method for use in a network node that resumes a radio bearer in a wireless communication network includes: for a UE, determining to resume a radio bearer associated with an RRC connection; And transmitting a connection resume message to the user equipment. The connection resumption message includes configuration information for the NR PDCP for the radio bearer.

In certain embodiments, configuration information for the radio bearer to resume previously includes NR PDCP configuration information or LTE configuration information.

In certain embodiments, the method includes: receiving capability information for the UE; And determining that the UE is capable of supporting NR PDCP based on the capability information. The method includes: establishing a SRB1 NR PDCP connection with the UE; Transmitting a connection suspension message to the UE; And receiving a connection reconfiguration message for reconfiguring SRB1 from NR PDCP to LTE PDCP from the UE.

According to some embodiments, the network node may resume the radio bearer in the wireless communication network. The network node includes the processing circuitry, the processing circuitry: for the UE, decides to resume the radio bearer associated with the RRC connection; It is operable to send a connection resume message to the user equipment. The connection resumption message includes configuration information for the NR PDCP for the radio bearer.

In certain embodiments, configuration information for the radio bearer to resume previously includes NR PDCP configuration information or LTE configuration information.

In certain embodiments, the processing circuitry: receives capability information for the UE; It is further operable to determine that the UE can support NR PDCP based on capability information. The processing circuit: establishes the SRB1 NR PDCP connection with the UE; Send a connection suspension message to the UE; It may be further operable to receive a connection reconfiguration message from the UE to reconfigure SRB1 from NR PDCP to LTE PDCP.

According to some embodiments, the UE may resume the radio bearer in the wireless communication network. The UE includes a configuration module and a reception module. The configuration module is operable to establish an RRC connection with the first network node. The receiving module is operable to receive a suspension message from the first network node. The configuration module is further operable to store the configuration of the radio bearer associated with the RRC connection and to suspend the radio bearer associated with the RRC connection. The receiving module is further operable to receive the connection resume message. The configuration module is further operable to determine whether the connection resumption message includes configuration information for the NR PDCP for the suspended radio bearer. When determining that the connection resume message includes configuration information for the NR PDCP, the suspended radio bearer is configured using the configuration information, and the suspended radio bearer is resumed.

According to some embodiments, the network node may resume the radio bearer in the wireless communication network. The network node includes a configuration module and a transmission module. The configuration module is operable to determine, for the UE, to resume the radio bearer associated with the RRC connection. The sending module is operable to send a connection resume message to the user equipment. The connection resumption message includes configuration information for the NR PDCP for the radio bearer.

Computer program products are also disclosed. The computer program product includes instructions stored on a non-transitory computer readable medium, the instructions, when executed by a processor, establish a radio resource control (RRC) connection with the first network node; Receive a suspension message from the first network node; Store the configuration of the radio bearer associated with the RRC connection; Suspend the radio bearer associated with the RRC connection; Receive a connection resume message; Determine whether the connection resumption message includes configuration information for the NR PDCP for the suspended radio bearer; Upon determining that the connection resumption message includes configuration information for the NR PDCP, configure the suspended radio bearer using the configuration information; The steps of resuming the suspended radio bearer are performed.

Another computer program product includes instructions stored on a non-transitory computer readable medium, the instructions, when executed by the processor, for the UE, determine to resume the radio bearer associated with the RRC connection; The steps of transmitting the connection resume message to the user equipment are performed. The connection resumption message includes configuration information for the NR PDCP for the radio bearer.

Certain embodiments of the present disclosure can provide one or more technical advantages. For example, some embodiments may suspend and resume all associated bearers of a UE while preserving the version of PDCP that was in use prior to the suspension, whereby the UE's bearers and the corresponding network configuration for the UE are configured. The need to do additional reconfigurations or core network signaling to bring the same configuration as they were before the suspension was eliminated. Eliminating reconfigurations is a significant performance advantage in that uplink and downlink user data can continue to flow, allowing protocols such as Transmission Control Protocol (TCP) to speed up ramps of TCP windows, which increases link utilization. Have Other advantages may be readily available to those skilled in the art. Certain embodiments may have none or some or all of the benefits mentioned.

For a more complete understanding of the embodiments and features and advantages of the embodiments, reference is now made to the following description, which is interpreted in conjunction with the accompanying drawings.
1 is a block diagram illustrating an LTE dual connectivity user plane.
2 is a block diagram illustrating an LTE-NR closely linked user plane.
3 is a block diagram illustrating an LTE-NR closely interlocked control plane.
4 is a block diagram illustrating three dual connectivity bearers from the perspective of user equipment.
5 is a sequence diagram illustrating an RRC connection suspend procedure.
6 is a sequence diagram illustrating an RRC connection resumption procedure at the same eNB.
7 is a sequence diagram illustrating an RRC connection resumption procedure in a new eNB.
8 is a block diagram illustrating an example wireless network, in accordance with certain embodiments.
9 is a flow diagram illustrating an example method in a wireless device, in accordance with certain embodiments.
10 is a flow diagram illustrating an example method at a network node, according to certain embodiments.
11A is a block diagram illustrating an exemplary embodiment of a wireless device.
11B is a block diagram illustrating example components of a wireless device.
12A is a block diagram illustrating an exemplary embodiment of a network node.
12B is a block diagram illustrating exemplary components of a network node.

The 3rd Generation Partnership Project (3GPP) defines the 5th generation (5G) wireless communication including the NR. NR, like Long Term Evolution (LTE), includes dual connectivity. LTE and NR also include radio resource control (RRC) suspend and resume functionality. A particular problem is that LTE RRC messages cannot correctly handle all scenarios for NR RRC suspend and resume with respect to packet data convergence protocol (PDCP) connections in NR.

Certain embodiments described herein eliminate the problems described above and implicitly indicate that all bearers of the UE use LTE PDCP upon resumption if user equipment (UEs) were using NR PDCP prior to suspend. Includes procedures to prevent conversion. Some embodiments may suspend and resume all associated bearers of a UE while preserving the version of PDCP that was in use prior to the suspension, thereby suspending the UE's bearers and corresponding network configuration for the UE. The need to do additional reconfigurations or core network signaling to bring the same configuration as they had before was eliminated. Eliminating reconfigurations has a significant performance advantage in that uplink and downlink user data can continue to flow, allowing protocols such as TCP to speed up ramps of TCP windows, which increases link utilization.

The following description describes a number of specific details. However, it is understood that embodiments may be practiced without these specific details. In other instances, well-known circuits, structures, and techniques have not been shown in detail in order not to obscure the understanding of the present description. Those skilled in the art will be able to implement appropriate functionality without undue experimentation, using the included descriptions.

References to “one embodiment”, “an embodiment”, “an exemplary embodiment”, and the like in this specification, although the described embodiment may include a specific feature, structure, or characteristic, all each embodiment must necessarily have a specific feature , It may indicate that the structure, or properties may not be included. Moreover, such phrases are not necessarily referring to the same embodiment. Additionally, when a particular feature, structure, or characteristic is described in connection with an embodiment, implementing such feature, structure, or characteristic in relation to other embodiments, whether explicitly described or not, is related It is suggested that it is within the knowledge of those skilled in the art.

Certain embodiments are described with reference to FIGS. 8-12B of the drawings, and like reference numerals are used in similar and corresponding parts of the various drawings. LTE and NR are used as exemplary cellular systems throughout the present disclosure, but the ideas presented herein can also be applied to other wireless communication systems.

8 is a block diagram illustrating an example wireless network, in accordance with certain embodiments. Wireless network 100 includes one or more wireless devices 110 (such as mobile phones, smart phones, laptop computers, tablet computers, MTC devices, or any other devices capable of providing wireless communication) and multiple Network nodes 120 (eg, base stations or eNodeBs). Wireless device 110 may also be referred to as a UE. The network node 120 serves the mastery area 115 (also referred to as the cell 115).

In general, wireless devices 110 that are within the reach of the network node 120 (eg, within the cell 115 served by the network node 120) by transmitting and receiving wireless signals 130 It communicates with the network node 120. For example, wireless devices 110 and network node 120 may communicate wireless signals 130 including voice traffic, data traffic, and / or control signals. The network node 120 that communicates voice traffic, data traffic, and / or control signals to the wireless device 110 may be referred to as a serving network node 120 for the wireless device 110. Communication between the wireless device 110 and the network node 120 may be referred to as cellular communication. The wireless signals 130 are both for downlink transmissions (from network node 120 to wireless devices 110) and uplink transmissions (from wireless devices 110 to network node 120). It can contain.

Each network node 120 may have a single transmitter or multiple transmitters for transmitting signals 130 to wireless devices 110. In some embodiments, network node 120 may include a multiple-input multiple-output (MIMO) system. The wireless signal 130 may include one or more beams. Certain beams can be beamformed in a specific direction. Each wireless device 110 may have a single receiver or multiple receivers for receiving signals 130 from network nodes 120 or other wireless devices 110. The wireless device 110 can receive one or more beams including the wireless signal 130.

Wireless signals 130 may be transmitted on time-frequency resources. Time-frequency resources can be partitioned into radio frames, subframes, slots, and / or mini-slots. The network node 120 may dynamically schedule subframes / slots / mini-slots as an uplink, downlink, or a combination of uplink and downlink. Different radio signals 130 may include different transmission processing times.

Network node 120 may operate in a licensed frequency spectrum, such as the LTE spectrum. Network node 120 may also operate in an unlicensed frequency spectrum, such as the 5 GHz Wi-Fi spectrum. In the unlicensed frequency spectrum, network node 120 may coexist with other devices, such as IEEE 802.11 access points and terminals. To share the unlicensed spectrum, network node 120 can perform LBT protocols before transmitting or receiving wireless signals 130. Wireless device 110 may also operate in either or both of the licensed or unlicensed spectrum, and in some embodiments, may also perform LBT protocols before transmitting wireless signals 130. . Both network node 120 and wireless device 110 may also operate in the licensed shared spectrum.

For example, network node 120a may operate in the licensed spectrum, and network node 120b may operate in the unlicensed spectrum. The wireless device 110 can operate in both licensed and unlicensed spectrum. In certain embodiments, network nodes 120a and 120b may be configurable to operate in the licensed spectrum, the unlicensed spectrum, the licensed shared spectrum, or any combination. Although the range of coverage of the cell 115b is illustrated as being included in the range of coverage of the cell 115a, in certain embodiments, the range of coverage of the cells 115a and 115b may be partially overlapped or not overlapped at all. It may not.

In certain embodiments, wireless device 110 and network nodes 120 may perform carrier aggregation. For example, the network node 120a may serve the wireless device 110 as a PCell, and the network node 120b may serve the wireless device 110 as a SCell. The network nodes 120 may perform self-scheduling or cross-scheduling. If the network node 120a is operating in the licensed spectrum and the network node 120b is operating in the unlicensed spectrum, the network node 120a can provide grant support access to the unlicensed spectrum ( That is, the network node 120a is a LAA PCell, and the network node 120b is a LAA SCell).

In certain embodiments, wireless device 110 may have RRC and PDCP connections with network nodes 120. The wireless device 110 and the network nodes 120 may perform dual connectivity. For example, wireless device 110 may be coupled to both network node 120a and network node 120b, as described in connection with any of the Figures 1-7. The wireless device 110 and network nodes 120 may suspend and resume PDCP connections. The PDCP connections can be LTE PDCP connections or NR PDCP connections. For example, specific examples are described in more detail below with respect to FIGS. 9-12B.

In wireless network 100, each network node 120 may be any suitable wireless access technology, such as Long Term Evolution (LTE), LTE-Advanced, UMTS, HSPA, GSM, cdma2000, NR, WiMax, WiFi and / or Or other suitable radio access technology can be used. The wireless network 100 can include any suitable combination of one or more wireless access technologies. For purposes of example, various embodiments may be described within the context of specific radio access technologies. However, the scope of the present disclosure is not limited to examples, and other embodiments may use different radio access technologies.

As described above, embodiments of a wireless network may include one or more wireless devices, and one or more different types of wireless network nodes capable of communicating with the wireless devices. The network may also include any additional elements suitable for supporting communication between wireless devices, or between wireless devices and other communication devices (such as landline telephones). The wireless device can include any suitable combination of hardware and / or software. For example, in certain embodiments, the wireless device, such as wireless device 110, may include components described in connection with FIG. 11A below. Similarly, a network node can include any suitable combination of hardware and / or software. For example, in certain embodiments, a network node, such as network node 120, may include components described in connection with FIG. 12A below.

In certain embodiments, an information element including an NR PDCP configuration for bearers to resume to the NR PDCP version is included in the LTE RRC resume message to achieve resumption of bearers to the pre-suspend state of bearers upon resumption. Is included.

In some embodiments, the UE will maintain the NR PDCP configuration used when the UE was in the RRC connection even after the UE leaves the RRC connection state. When the UE resumes the RRC connection (entering the RRC connection state), the network will indicate to the UE that the UE should resume the NR PDCP configuration. The network can also indicate if any parameters of the NR PDCP configuration should be modified.

Also, in some embodiments, the NR PDCP configuration may be resumed using a different security key and / or security algorithm than was used prior to suspension. The security key to be used can be derived at the UE based on the previous keys and other parameters provided by the network, such as the Next Hop Chaining Counter (NCC).

In another embodiment of the present invention, if a UE using NR PDCP for some or all of its bearers is suspended, and later resumed at an eNB that does not support NR, the RRC resume message is configured for NR PDCP Will not include, therefore, all bearers will resume in the LTE PDCP version.

In some embodiments, if a UE using LTE PDCP for all of its bearers is suspended and later resumed at a different eNB, the UE (eg, by examining the broadcast information of the eNB) eNB Checks whether NR supports NR, and if the eNB supports NR, the UE includes an indication indicating that it wants to be configured with NR PDCP in the resume message. At that time, the target eNB responds by including the NR PDCP configurations in the RRC resume message it sends to the UE, so some or all of the bearers can be resumed with the NR PDCP.

In certain embodiments, when a UE that is served by an eNB supporting NR PDCP and was using NR PDCP for some or all of its bearers is suspended, the eNB may not support NR PDCP. To ensure that the UE can be resumed at the eNB, protocol parameters / configuration such as security parameters (eg, encryption algorithms) and sequence number lengths can also be ensured to be reused in LTE PDCP. If the configurations currently used by the UE's NR PDCP are not compatible with LTE PDCP, a reconfiguration is sent to the UE to change them to compatible values before the UE is suspended. This reconfiguration may be a separate RRC reconfiguration message, or the RRC suspend command is enhanced to include RRC reconfigurations.

In one embodiment of the present invention, when the UE resumes at a different eNB and the target eNB does not support NR PDCP, the target eNB configures all bearers to ensure that all bearers will resume to the LTE PDCP version. To ensure that the LTE PDCP config is included (even if it is an arbitrary parameter).

In one embodiment of the present invention, the NR capability of the UE is part of the context of the UE stored by the network / UE when the UE is suspended.

In another embodiment of the invention, when the UE is resuming and the context is being fetched by the target eNB from the source eNB, the source eNB implicitly or explicitly indicates the UE's NR capability to the target eNB in the UE context. (Eg, in an X2 message used for context fetching between two eNBs).

In one embodiment, it is detected that the UE using LTE PDCP for all of its bearers is suspended and later resumed at a different eNB, and the target eNB supports NR, and the UE supports NR In one case, the target eNB may include NR PDCP configurations in the RRC resume message that it sends to the UE, even if the bearers of the UE were using LTE PDCP before suspending, therefore, some or all of the bearers or All can be resumed with NR PDCP. NR PDCP parameters configured or resumed when the UE returns to the RRC connected state may include sequence number size, status report configuration, discard, or reordering timers.

Additionally, the UE may be configured to transmit NR PDCP data over LTE or NR radio or both LTE and NR radio upon returning to the RRC connection. The UE can also be configured to use NR PDCP for signaling radio bearers (eg, SRB1, SRB2). Signaling radio bearers may be configured at the UE such that the UE can transmit or receive signaling via LTE or NR radio or both LTE and NR radio.

9 is a flow diagram illustrating an example method in a wireless device, in accordance with certain embodiments. In certain embodiments, one or more steps of FIG. 9 may be performed by wireless device 110 of network 100 described with respect to FIG. 8.

The method begins at step 912, where the wireless device establishes an RRC connection with the first network node. For example, the wireless device 110 may establish an RRC connection with the network node 120a.

In step 914, the wireless device may establish an SRB1 NR PDCP connection with the first network node. For example, the wireless device 110 may establish an SRB1 NR PDCP connection with the network node 120 for transmission of RRC signaling messages.

In step 916, the wireless device receives a suspension message from the first network node. For example, the wireless device 110 may receive an RRC suspend message from the network node 120a.

In step 917, the wireless device stores the configuration of the radio bearer associated with the RRC connection. The wireless device may store configuration information for the NR PDCP bearer or LTE bearer. For example, the wireless device 110 may store information regarding the NR bearer connection, such as sequence number information, status information, security information, and the like. The wireless device 110 may store information locally or to a network node, for example, as part of the UE context. The wireless device 110 can store information according to any of the embodiments or examples described above.

In step 918, the wireless device suspends the radio bearer associated with the RRC connection. For example, the wireless device 110 may suspend the NR or LTE PDCP radio bearer.

In step 920, the wireless device may convert the SRB1 NR PDCP connection into an LTE PDCP connection. For example, the wireless device 110 may convert the SRB1 connection established in step 914 into an LTE PDCP connection. A particular advantage is that if any of the suspended bearers are resumed at a different network node that does not support NR, the wireless device can use the LTE PDCP configuration for SRB1 to send an RRC resume request to the network node. Is there.

In step 922, the wireless device receives a connection resume message from the second network node. In some embodiments, the second network node may be the same as the first network node. In other embodiments, the second network node may be different from the first network node. As one example, the wireless device 110 may receive an RRC resume message from the network node 120a. As another example, the wireless device 110 may have moved within the range of the network node 120b and may receive an RRC resume message from the network node 120b.

In step 924, the wireless device determines whether the connection resume message includes configuration information for the NR PDCP for the suspended radio bearer. For example, the wireless device 110 may determine that the RRC resume message includes information for configuring the NR PDCP bearer. The method continues with step 925.

In step 925, the wireless device configures the suspended radio bearer using the configuration information. For example, the wireless device 110 configures the suspended radio bearer using the configuration information. In some embodiments, wireless device 110 may use a combination of a received configuration and a stored configuration to establish a connection.

In step 926, the wireless device resumes the suspended radio bearer. For example, the wireless device 110 can resume the NR or LTE radio bearer based on the configuration from the previous step. The wireless device can resume the radio bearer according to any of the embodiments or examples described above.

Modifications, additions, or omissions may be made to the method 900 of FIG. 9. Additionally, one or more steps in the method of FIG. 9 can be performed in parallel or in any suitable order. As one example, step 916 may be performed after steps 917 or 918 in some embodiments. As another example, step 917 can be performed earlier or later. The steps can be repeated over time if necessary.

10 is a flow diagram illustrating an example method at a network node, according to certain embodiments. In certain embodiments, one or more steps of FIG. 10 may be performed by network node 120 of network 100 described with respect to FIG. 8.

The method may begin at step 1012, where a network node establishes an SRB1 NR PDCP connection with the UE. For example, the network node 120 may establish an SRB1 NR PDCP connection with the wireless device 110 for transmission of RRC signaling messages.

In step 1014, the network node may send a connection suspension message to the UE. For example, the network node 120 may send a connection suspension message to the wireless device 110 to suspend one or more radio bearers.

In step 1016, the network node may receive a connection reconfiguration message from the UE to reconfigure SRB1 from NR PDCP to LTE PDCP. For example, the network node 120 may receive a connection reconfiguration message from the wireless device 110. The wireless device may send a reconfiguration message, for example, if the wireless device resumes PDCP bearer connections with a different network node that does not support NR PDCP.

In step 1018, the network node, for the UE, determines to resume the radio bearer associated with the RRC connection. For example, the network node 120b may receive an RRC resume request from the wireless device 110 to resume the radio bearer. In some embodiments, the bearer connection can include any suitable bearer connection.

In step 1020, the network node may receive capability information for the UE. For example, the network node 120 may receive capability information from the wireless device 110 indicating capabilities of the wireless device 110, such as capability to communicate using NR PDCP or LTE PDCP.

In step 1022, the network node determines, based on the capability information, that the UE can support NR PDCP. For example, the network node 120 may determine that the wireless device 110 can support NR PDCP based on the received capability information.

In some embodiments, the network node can receive NR configuration information for the bearer connection from another network node. For example, the network node 120b may receive configuration information from the network node 120a if the wireless device 110 was previously connected to the network node 120a before the bearer was suspended. The network node may receive NR configuration information according to any of the embodiments or examples described above.

In step 1024, the network node sends a connection resumption message to the UE. The connection resumption message includes configuration information for the NR PDCP for the radio bearer. For example, the network node 120b may transmit an RRC resume message to the wireless device 110. The configuration information may include NR or LTE configuration information. Configuration information may include information according to any of the embodiments or examples described above.

Modifications, additions, or omissions can be made to the method 1000 of FIG. 10. Additionally, one or more steps in the method of FIG. 10 can be performed in parallel or in any suitable order. The steps can be repeated over time if necessary.

11A is a block diagram illustrating an exemplary embodiment of a wireless device. The wireless device is an example of the wireless device 110 illustrated in FIG. 8. In certain embodiments, the wireless device can pause and resume NR bearer connections.

Specific examples of wireless devices include mobile phones, smart phones, personal digital assistants (PDAs), portable computers (e.g. laptops, tablets), sensors, modems, machine type (MTC) devices / machine-to-machine communication (M2M) ) Device, built-in laptop (LEE), laptop-equipped equipment (LME), USB dongles, device-to-device capable devices, vehicle-to-vehicle devices, or wireless communication And any other device that can. The wireless device includes a transceiver 1310, a processing circuit 1320, a memory 1330, and a power supply 1340. In some embodiments, transceiver 1310 enables transmitting wireless signals to and receiving wireless signals from wireless network node 120 (eg, via an antenna), and processing circuit 1320 connects to the wireless device. Instructions are executed to provide some or all of the functionality described herein as provided by, and memory 1330 stores instructions executed by processing circuit 1320. The power supply 1340 supplies power to one or more of the components of the wireless device 110, such as the transceiver 1310, the processing circuit 1320, and / or the memory 1330.

Processing circuit 1320 includes any suitable combination of software and hardware implemented in one or more integrated circuits or modules for executing instructions and manipulating data to perform some or all of the described functions of a wireless device. do. In some embodiments, processing circuit 1320 may include, for example, one or more computers, one or more programmable logic devices, one or more central processing units (CPUs), one or more microprocessors, one or more applications, and / or other logic, And / or any suitable combination of the above. Processing circuit 1320 may include analog and / or digital circuitry configured to perform some or all of the described functions of wireless device 110. For example, the processing circuit 1320 may include resistors, capacitors, inductors, transistors, diodes, and / or any other suitable circuit components.

The memory 1330 is generally operable to store computer executable code and data. Examples of the memory 1330 include computer memory (eg, random access memory (RAM) or read-only memory (ROM)), mass storage media (eg, hard disk), removable storage media (eg, for storing information) , Compact disc (CD) or digital video disc (DVD)), and / or any other volatile or non-volatile non-transitory computer readable and / or computer executable memory devices.

The power supply 1340 is generally operable to supply power to the components of the wireless device 110. Power source 1340 can be any suitable type of battery, such as lithium-ion, lithium-air, lithium polymer, nickel cadmium, nickel metal hydride, or any other suitable type of battery for powering wireless devices. It may include.

Other embodiments of the wireless device specify the functionality of the wireless device, including any of the functionality described above and / or any additional functionality (including any functionality needed to support the solutions described above). It may include additional components (other than those shown in FIG. 11A) responsible for providing aspects.

11B is a block diagram illustrating example components of the wireless device 110. Components may include a configuration module 1350, a transmission module 1352, and a reception module 1354.

The configuration module 1350 may perform configuration functions of the wireless device 110. For example, the configuration module 1350 establishes an RRC connection, suspends the radio bearer associated with the RRC connection, and a connection resume message to the suspended radio bearer, according to any of the examples and embodiments described above. It is possible to determine whether to include the configuration information for the NR PDCP, and to use the configuration information, to configure the suspended radio bearer, and resume the suspended radio bearers. In certain embodiments, configuration module 1350 may include or be included in processing circuit 1320. In certain embodiments, the configuration module 1350 can communicate with the transmitting module 1352 and the receiving module 1354.

The transmission module 1352 may perform transmission functions of the wireless device 110. For example, the transmission module 1352 may set the network node 120 and radio bearers and / or transmit configuration information to the network node 120 according to any of the examples and embodiments described above. In certain embodiments, the transmission module 1352 can include or be included in the processing circuit 1320. In certain embodiments, the transmit module 1352 can communicate with the scheduling module 1350 and the receive module 1354.

The reception module 1354 may perform reception functions of the wireless device 110. For example, the receiving module 1354 can receive suspend and resume messages from the network node 120 according to any of the examples and embodiments described above. In certain embodiments, the receiving module 1354 can include or be included in the processing circuit 1320. In certain embodiments, the transmission module 1352 can communicate with the scheduling module 1350 and the transmission module 1352.

12A is a block diagram illustrating an exemplary embodiment of a network node. The network node is an example of the network node 120 illustrated in FIG. 8. In certain embodiments, the network node may pause and resume NR bearer connections.

The network node 120 includes an eNodeB, nodeB, base station, wireless access point (eg, Wi-Fi access point), low power node, base transceiver station (BTS), transmit point or node, remote RF unit (RRU) , A remote radio head (RRH), or other radio access node. The network node includes at least one transceiver 1410, at least one processing circuit 1420, at least one memory 1430, and at least one network interface 1440. The transceiver 1410 enables transmitting wireless signals to and receiving wireless signals (eg, via an antenna) to the wireless device, such as the wireless devices 110, and the processing circuit 1420 connects to the network node 120. Execute instructions to provide some or all of the functionality described above, such as provided by; memory 1430 stores instructions executed by processing circuit 1420; network interface 1440 configures the backend network The elements, such as gateways, switches, routers, the Internet, public switched telephone networks (PSTN), controllers, and / or communicate signals to other network nodes 120. Processing circuitry 1420 and memory 1430 , May have the same types as described above with respect to the processing circuit 1320 and memory 1330 of FIG. 11A above.

In some embodiments, the network interface 1440 is communicatively coupled to the processing circuit 1420, receiving input to the network node 120, transmitting output from the network node 120, input or Refers to any suitable device that is operable to perform suitable processing of the output or both, communicate to other devices, or do any combination of the above. The network interface 1440 includes suitable hardware (eg, ports, modems, network interface cards, etc.) and software, including protocol conversion and data processing capabilities, to communicate over the network.

11B is a block diagram illustrating exemplary components of network node 120. Components may include a configuration module 1450, a transmission module 1452, and a reception module 1454.

The configuration module 1450 may perform configuration functions of the network node 120. For example, configuration module 1450 may determine to resume the radio bearer and / or configure the radio bearer, according to any of the examples and embodiments described above. In certain embodiments, configuration module 1450 may include or be included in processing circuit 1420. In certain embodiments, the configuration module 1450 can communicate with the transmitting module 1452 and the receiving module 1454.

The transmission module 1452 may perform transmission functions of the network node 120. For example, the sending module 1452 can send radio bearer configuration information to another network node and / or send resume messages to the wireless device, according to any of the examples and embodiments described above. In certain embodiments, the transmission module 1452 can include or be included in the processing circuit 1420. In certain embodiments, the transmission module 1452 can communicate with the configuration module 1450 and the transmission module 1454.

The reception module 1454 may perform reception functions of the network node 120. For example, the receiving module 1454 can receive the radio bearer configuration information from another network node or wireless device, according to any of the examples and embodiments described above. In certain embodiments, the receiving module 1454 can include or be included in the processing circuit 1420. In certain embodiments, the transmission module 1452 can communicate with the configuration module 1450 and the transmission module 1452.

Modifications, additions, or omissions can be made to the systems and devices disclosed herein without departing from the scope of the invention. The components of the systems and devices can be integrated or separated. Moreover, the operations of the systems and devices can be performed by more, less, or other components. Additionally, the operations of the systems and devices can be performed using any suitable logic, including software, hardware, and / or other logic. As used herein, "each" refers to each member of a set or each element of a subset of a set.

Modifications, additions, or omissions to the methods disclosed herein can be made without departing from the scope of the invention. The methods may include more, fewer, or other steps. Additionally, the steps can be performed in any suitable order.

Although the present disclosure has been described in terms of specific embodiments, changes and permutations of those embodiments will be apparent to those skilled in the art. Accordingly, the above description of embodiments does not limit the present disclosure. Other changes, substitutions, and changes are possible without departing from the spirit and scope of the present disclosure as defined by the claims below.

Abbreviations used in the preceding description include:

3GPP 3rd Generation Partnership Project

5G 5th generation

BBU Baseband unit

BTS Transceiver base station

CC Component carrier

D2D Device-to-device communication

DC Dual connectivity

eMBB Enhanced mobile broadband

eNB eNodeB

EPC Advanced packet core

EPS Advanced packet system

FDD Frequency division redundancy

FFT Fast Fourier Transform

gNB Next-generation NodeB

LAA Authorized Support Access

LBT Listen-before-talk

LTE Long Term Evolution

LTE-U LTE in unlicensed spectrum

MeNB Master eNB

M2M Inter-machine communication

MCG Master cell group

MIB Master information block

MIMO Multi-input Multi-output

MTC Machine type communication

NAS Non-access layer

NR Yen

OFDM Orthogonal frequency division multiplexing

PCM Parity check matrix

PDCP Packet data convergence protocol

PRB Physical resource block

QoS Quality of service

RAN Wireless access network

RAT Wireless access technology

RBS Wireless base station

RNC Wireless network controller

RRC Radio resource control

RRH Remote wireless head

RRU Remote wireless unit

SAE System architecture evolution

SCell Secondary cell

SCG Secondary cell group

SeNB Secondary eNB

SI System information

SIB System information block

SRB Signaling radio bearer

TDD Time-division duplication

TNL Transport network layer

UE User equipment

UL Uplink

UTRAN Universal terrestrial radio access network

WAN Wireless access network

Claims (32)

A method for use in a user equipment (UE) for resuming a radio bearer in a wireless communication network,
Establishing a radio resource control (RRC) connection with the first network node (912);
Receiving a connection suspension message from the first network node (916);
Storing a configuration of a radio bearer associated with the RRC connection (917);
Suspending (918) the radio bearer associated with the RRC connection;
Receiving a connection resume message (922);
Determining (924) whether the connection resumption message includes configuration information for an NR packet data convergence protocol (PDCP) for a suspended radio bearer;
When determining that the connection resumption message includes configuration information for the NR PDCP, using the configuration information, configuring the suspended radio bearer (925); And
A method for use in a user equipment for resuming a radio bearer in a wireless communication network, comprising resuming (926) the suspended radio bearer. According to claim 1,
The established RRC connection comprises a NR PDCP bearer, a method for use in a user equipment that resumes a radio bearer in a wireless communication network. According to claim 1,
The established RRC connection comprises a Long Term Evolution (LTE) PDCP bearer, a method for use in a user equipment that resumes a radio bearer in a wireless communication network. The method according to any one of claims 1 to 3,
The method for use in user equipment for resuming a radio bearer in a wireless communication network, wherein the connection resume message is received from a second network node different from the first network node. The method according to any one of claims 1 to 4,
The step of configuring the suspended radio bearer comprises using the configuration information and stored configuration information in the connection resume message, a method for use in a user equipment for resuming a radio bearer in a wireless communication network. The method of claim 5,
A method for use in user equipment for resuming a radio bearer in a wireless communication network, wherein the configuration information in the connection resume message takes precedence over the stored configuration information. The method according to any one of claims 1 to 6,
The configuration information in the connection resume message comprises security information different from the security information used before the suspension of the radio bearer, the method for use in a user equipment for resuming a radio bearer in a wireless communication network. The method of claim 7,
The security information comprises security key information or security algorithm information, a method for use in user equipment for resuming a radio bearer in a wireless communication network. The method according to any one of claims 1 to 8,
Further 928 resuming the suspended radio bearer as a Long Term Evolution (LTE) PDCP bearer upon determining that the connection resume message does not include configuration information for NR PDCP for the suspended radio bearer. A method for use in a user equipment that resumes a radio bearer in a wireless communication network, comprising. The method according to any one of claims 1 to 9,
Establishing a signaling radio bearer 1 (SRB1) NR PDCP connection with the first network node (914); And
When receiving the connection suspension message, further comprising the step 920 of converting the SRB1 connection to a Long Term Evolution (LTE) PDCP connection,
The method for use in user equipment for resuming a radio bearer in a wireless communication network, wherein the connection resume message is received through the SRB1 connection. A user equipment (UE) 110 capable of resuming a radio bearer in a wireless communication network,
It includes a processing circuit 1320,
The processing circuit,
Establish a radio resource control (RRC) connection with the first network node 120;
Receive a connection suspension message from the first network node;
Store a configuration of a radio bearer associated with the RRC connection;
Suspend the radio bearer associated with the RRC connection;
Receive a connection resume message;
Determine whether the connection resumption message includes configuration information for a NR packet data convergence protocol (PDCP) for a suspended radio bearer;
Upon determining that the connection resumption message includes configuration information for the NR PDCP, configure the suspended radio bearer using the configuration information;
User equipment capable of resuming a radio bearer in a wireless communication network, operable to resume the suspended radio bearer. The method of claim 11,
User equipment capable of resuming a radio bearer in a wireless communication network, wherein the established RRC connection includes an NR PDCP bearer. The method of claim 11,
User equipment capable of resuming a radio bearer in a wireless communication network, wherein the established RRC connection includes a Long Term Evolution (LTE) PDCP bearer. The method according to any one of claims 11 to 13,
The connection resume message is received from a second network node different from the first network node, the user equipment capable of resuming the radio bearer in the wireless communication network. The method according to any one of claims 11 to 14,
Wherein the processing circuit is operable to configure the suspended radio bearer by using the configuration information and stored configuration information in the connection resume message, user equipment capable of resuming a radio bearer in a wireless communication network. The method of claim 15,
The user equipment capable of resuming a radio bearer in a wireless communication network, wherein the configuration information in the connection resume message takes precedence over the stored configuration information. The method according to any one of claims 11 to 16,
The user equipment capable of resuming the radio bearer in the wireless communication network, wherein the configuration information in the connection resume message includes security information different from the security information used before the suspension of the radio bearer. The method of claim 17,
The security information includes security key information or security algorithm information, user equipment capable of resuming a radio bearer in a wireless communication network. The method according to any one of claims 11 to 18,
The processing circuit adds to resume the suspended radio bearer as a Long Term Evolution (LTE) PDCP bearer when determining that the connection resume message does not include configuration information for NR PDCP for the suspended radio bearer. A user equipment capable of resuming a radio bearer in a wireless communication network, which is operable to. The method according to any one of claims 11 to 19,
The processing circuit,
Establish a signaling radio bearer 1 (SRB1) NR PDCP connection with the first network node;
When receiving the connection suspension message, it is further operable to convert the SRB1 connection into a Long Term Evolution (LTE) PDCP connection,
The processing circuit is user equipment capable of resuming a radio bearer in a wireless communication network, operable to receive the connection resume message via the SRB1 connection. A method for use in a network node that resumes a radio bearer in a wireless communication network,
For user equipment (UE), determining 1018 to resume a radio bearer associated with a radio resource control (RRC) connection; And
Transmitting 1024 a connection resume message to the user equipment, the connection resume message comprising configuration information for an NR packet data convergence protocol (PDCP) for the radio bearer, wireless in a wireless communication network Method for use in network nodes that resume bearers. The method of claim 21,
The configuration information for the radio bearer to resume previously includes NR PDCP configuration information, a method for use in a network node for resuming a radio bearer in a wireless communication network. The method of claim 21,
The configuration information for the radio bearer to resume previously includes long term evolution (LTE) configuration information, a method for use in a network node for resuming a radio bearer in a wireless communication network. The method of claim 23,
Receiving capability information for the UE (1020); And
And based on the capability information, determining (1022) that the UE is capable of supporting NR PDCP, for use in a network node resuming a radio bearer in a wireless communication network. The method of any one of claims 21 to 24,
Establishing a signaling radio bearer 1 (SRB1) NR PDCP connection with the UE (1012);
Transmitting a connection suspension message to the UE (1014); And
A method for use in a network node that resumes a radio bearer in a wireless communication network, further comprising receiving (1016) a connection reconfiguration message from the UE that reconfigures SRB1 from NR PDCP to long term evolution (LTE) PDCP. As a network node 120 capable of resuming a radio bearer in a wireless communication network,
A processing circuit 1420,
The processing circuit,
For user equipment (UE) 110, decide to resume a radio bearer associated with a radio resource control (RRC) connection;
Operable to send a connection resume message to the user equipment, wherein the connection resume message includes configuration information for an NR packet data convergence protocol (PDCP) for the radio bearer to resume the radio bearer in the wireless communication network. Network nodes. The method of claim 26,
The configuration information for the radio bearer to resume previously includes NR PDCP configuration information, a network node capable of resuming the radio bearer in the wireless communication network. The method of claim 26,
The configuration information for the radio bearer to resume previously includes long term evolution (LTE) configuration information, a network node capable of resuming a radio bearer in a wireless communication network. The method of claim 28,
The processing circuit,
Receiving capability information for the UE;
Based on the capability information, a network node capable of resuming a radio bearer in a wireless communication network, further operable to determine that the UE is capable of supporting NR PDCP. The method according to any one of claims 26 to 29,
The processing circuit,
Establish a signaling radio bearer 1 (SRB1) NR PDCP connection with the UE;
Transmit a connection suspension message to the UE;
A network node capable of resuming a radio bearer in a wireless communication network, further operable to receive a connection reconfiguration message from the UE that reconfigures SRB1 from NR PDCP to Long Term Evolution (LTE) PDCP. A user equipment (UE) 110 capable of resuming a radio bearer in a wireless communication network,
And a configuration module 1350 and a reception module 1354,
The configuration module is operable to establish a radio resource control (RRC) connection with the first network node 120,
The receiving module is operable to receive a connection suspension message from the first network node,
The configuration module,
Store a configuration of a radio bearer associated with the RRC connection;
Is further operable to suspend the radio bearer associated with the RRC connection,
The receiving module is further operable to receive a connection resumption message,
The configuration module,
Determine whether the connection resumption message includes configuration information for a NR packet data convergence protocol (PDCP) for a suspended radio bearer;
Upon determining that the connection resumption message includes configuration information for the NR PDCP, configure the suspended radio bearer using the configuration information;
User equipment capable of resuming a radio bearer in a wireless communication network, further operable to resume the suspended radio bearer. As a network node 120 capable of resuming a radio bearer in a wireless communication network,
It includes a configuration module 1450 and a transmission module 1452,
The configuration module is operable to determine, for user equipment (UE) 110, to resume a radio bearer associated with a radio resource control (RRC) connection,
The transmitting module is operable to send a connection resume message to the user equipment, the connection resume message comprising configuration information for an NR packet data convergence protocol (PDCP) for the radio bearer in a wireless communication network. A network node capable of resuming radio bearers.

Images