Patent Description:
Examples of mobile or wireless telecommunication systems may include the Universal Mobile Telecommunications System (UMTS) Terrestrial Radio Access Network (UTRAN), Long Term Evolution (LTE) Evolved UTRAN (E-UTRAN), LTE-Advanced (LTE-A), LTE-A Pro, and/or fifth generation (<NUM>) radio access technology or new radio (NR) access technology. Fifth generation (<NUM>) or new radio (NR) wireless systems refer to the next generation (NG) of radio systems and network architecture. It is estimated that NR will provide bitrates on the order of <NUM>-<NUM> Gbit/s or higher, and will support at least enhanced mobile broadband (eMBB) and ultra-reliable low-latency-communication (URLLC). NR is expected to deliver extreme broadband and ultra-robust, low latency connectivity and massive networking to support the Internet of Things (IoT). With IoT and machine-to-machine (M2M) communication becoming more widespread, there will be a growing need for networks that meet the needs of lower power, low data rate, and long battery life. It is noted that, in <NUM> or NR, the nodes that can provide radio access functionality to a user equipment (i.e., similar to Node B in UTRAN or eNB in LTE) may be referred to as a next generation or <NUM> Node B (gNB).

TS <NUM> (section <NUM>. <NUM>) describes that a SeNB may send a SeNB Counter Check request to a MeNB to execute a counter check procedure to verify the value of a PDCP COUNTs associated with SCG bearers established in the SeNB.

TS <NUM> (section <NUM>. <NUM>) describes that the SeNB Counter Check request may comprise an UL count information element and a DL count information element.

3GPP draft R2-<NUM> teaches that to prevent COUNT values from wrapping around on an SCG AM DRB (split or not), a SN may only request DRB release from the MN, without the MN knowing why.

For proper understanding of the disclosure, reference should be made to the accompanying drawings, wherein:.

It will be readily understood that the components of the disclosure, as generally described and illustrated in the figures herein, may be arranged and designed in a wide variety of different configurations. Thus, the following detailed description of the aspects of systems, methods, apparatuses, and computer program products for informing a multi-connectivity master node of an impending wrap around of packet counter value, as represented in the attached figures and described below, is not intended to limit the scope of the disclosure but is representative of selected aspects of the disclosure.

The features, structures, or characteristics of the disclosure described throughout this specification may be combined in any suitable manner in one or more aspects. For example, the usage of the phrases "certain aspects," "some aspects," or other similar language, throughout this specification refers to the fact that a particular feature, structure, or characteristic described in connection with the aspect may be included in at least one aspect of the present disclosure. Thus, appearances of the phrases "in certain aspects," "in some aspects," "in other aspects," or other similar language, throughout this specification do not necessarily all refer to the same group of aspects, and the described features, structures, or characteristics may be combined in any suitable manner in one or more aspects.

Additionally, if desired, the different functions or steps discussed below may be performed in a different order and/or concurrently with each other. Furthermore, if desired, one or more of the described functions or steps may be optional or may be combined. As such, the following description should be considered as merely illustrative of the principles, teachings and aspects of this disclosure, and not in limitation thereof.

Certain aspects may be directed to an approach for preventing the wrap-around of the packet data convergence protocol (PDCP) count value. It is noted that the new radio (NR) PDCP count is defined in the 3GPP NR PDCP technical specification (TS) <NUM>. A wrap-around of the count may refer to the count's re-assignment to <NUM> after reaching the maximum value. The 3GPP specification(s) indicate that the NR PDCP count does not wrap around, whereas, in LTE PDCP, the count is allowed to wrap around.

<FIG> illustrates an example block diagram depicting the format of the count <NUM>, according to one aspect. As illustrated in the example of <FIG>, the count value may be composed of a hyper frame number (HFN) <NUM> and PDCP sequence number (SN) <NUM>. In an example aspect, the length of count <NUM> may be <NUM> bits and the size of the HFN part <NUM> may be equal to <NUM> bits minus the length of the PDCP SN <NUM>.

Various example aspects are directed to avoiding a count wrap-around when a UE is configured in dual (or multi-) connectivity, and specifically on bearers mapped on radio link control (RLC) acknowledged mode (AM) where PDCP is not terminated in the Master Node (MN) (i.e., in the case of dual connectivity, Secondary-Node (SN)-terminated bearers).

A problem with avoiding count wrap-around on bearers mapped on RLC AM is that there is no proper PDCP procedure for resetting the count value. It is noted that the count value is maintained also at PDCP re-establishment (invoked for example at handover). So, the only way to reset the count is to release the data radio bearer (DRB) and add a new one.

In the context of an SN-terminated bearer, what is also problematic is that the SN has no means to request DRB release and add from the MN that has the control. The SN may request release of the bearer; however, when doing so, there is no way for the MN to determine that the reason for release is an impending count wrap-around, and that a new DRB should be established in place of the one being released. The consequence is that the DRB is simply released before the PDCP count reaches its maximum value, even though the traffic demand for the bearer remains.

One aspect provides a process for avoiding PDCP count wrap-around for non-MN-terminated bearers in multi-connectivity. In an aspect, the process includes, upon detecting that count wrap-around is impending on the bearer, the node hosting PDCP for the bearer (e.g., SN) sends to the MN a counter check request that includes the count value approaching its maximum value. Upon receiving this request message and observing the high count value in it, the Master Node initiates the DRB release and add a new bearer, as required.

In an aspect, the highest downlink (DL) and/or uplink (UL) count value (e.g., <NUM>) in the counter check request message may be used to indicate that the PDCP count wrap-around event is to occur soon and the Master Node should take an action for the given bearer. This option may be allowed given that the node hosting PDCP should not allow the count to progress that far (at least in UL).

An advantage of certain aspects includes avoiding or minimizing impact to the existing stage-<NUM> specification. Also, the usage of a counter check request message to advise a Master Node of a high count value can be understood to indicate that a bearer release and add is desired, whereas a SN may use a SN modification required message to just release bearers.

<FIG> illustrates an example signaling diagram depicting a process for preventing count wrap-around, according to one aspect. As illustrated in the example of <FIG>, a network node may determine or detect, at <NUM>, that count wrap-around is imminent on the bearer. In an aspect, the count may be a PDCP count and the node may be the node hosting PDCP for the bearer, such as a secondary node. According to one aspect, upon detecting that the count wrap-around is approaching on the bearer, the node hosting PDCP for the bearer may transmit, at <NUM>, a counter check request to a master node in order to indicate that the count wrap-around is to occur soon. In certain aspects, the counter check request message <NUM> may include the count value that is approaching its maximum value. Upon receiving the counter check request message and possibly observing or determining the high count value in it, at <NUM>, the master node may initiate DRB release and add a new bearer, as required. In one example aspect, the highest downlink (DL) and/or uplink (UL) count value (e.g., <NUM>) in the counter check request message <NUM> may be used to indicate that the count wrap-around event is to occur soon and that the master node should take an action for the given bearer. It is noted that the inclusion of the DL and UL count values in the counter check request message may be optional. According to an example aspect, the absence of count value fields in the counter check request message may then indicate, to the master node, that the counter check request was sent for the reason of indicating a count wrap-around event and the master node may take appropriate action at <NUM>.

<FIG> illustrates an example of an apparatus <NUM> according to an aspect. In an aspect, apparatus <NUM> may be a node, host, or server in a communications network or serving such a network. For example, apparatus <NUM> may be a base station, a Node B, an evolved Node B (eNB), <NUM> Node B or access point, next generation Node B (NG-NB or gNB), WLAN access point, mobility management entity (MME), and/or subscription server associated with a radio access network, such as a GSM network, LTE network, <NUM> or NR.

It should be understood that, in some example aspects, apparatus <NUM> may be comprised of an edge cloud server as a distributed computing system where the server and the radio node may be stand-alone apparatuses communicating with each other via a radio path or via a wired connection, or they may be located in a same entity communicating via a wired connection.

While a single processor <NUM> is shown in <FIG>, multiple processors may be utilized according to other aspects. For example, it should be understood that, in certain aspects, apparatus <NUM> may include two or more processors that may form a multiprocessor system (e.g., in this case processor <NUM> may represent a multiprocessor) that may support multiprocessing. In certain aspects, the multiprocessor system may be tightly coupled or loosely coupled (e.g., to form a computer cluster).

For example, memory <NUM> can be comprised of any combination of random access memory.

(RAM), read only memory (ROM), static storage such as a magnetic or optical disk, hard disk drive (HDD), or any other type of non-transitory machine or computer readable media.

In an aspect, apparatus <NUM> may further include or be coupled to (internal or external) a drive or port that is configured to accept and read an external computer readable storage medium, such as an optical disc, USB drive, flash drive, or any other storage medium.

In some aspects, apparatus <NUM> may also include or be coupled to one or more antennas <NUM> for transmitting and receiving signals and/or data to and from apparatus <NUM>. Apparatus <NUM> may further include or be coupled to a transceiver <NUM> configured to transmit and receive information. The transceiver <NUM> may include, for example, a plurality of radio interfaces that may be coupled to the antenna(s) <NUM>. The radio interfaces may correspond to a plurality of radio access technologies including one or more of GSM, NB-IoT, LTE, <NUM>, WLAN, Bluetooth, BT-LE, NFC, radio frequency identifier (RFID), ultrawideband (UWB), MulteFire, and the like. The radio interface may include components, such as filters, converters (for example, digital-to-analog converters and the like), mappers, a Fast Fourier Transform (FFT) module, and the like, to generate symbols for a transmission via one or more downlinks and to receive symbols (for example, via an uplink).

In other aspects, transceiver <NUM> may be capable of transmitting and receiving signals or data directly. Additionally or alternatively, in some aspects, apparatus <NUM> may include an input and/or output device (I/O device) or I/O circuitry.

In an aspect, memory <NUM> may store software modules that provide functionality when executed by processor <NUM>.

According to some aspects, processor <NUM> and memory <NUM> may be included in or may form a part of processing circuitry or control circuitry. In addition, in some aspects, transceiver <NUM> may be included in or may form a part of transceiving circuitry.

As introduced above, in certain aspects, apparatus <NUM> may be a network node or RAN node, such as a base station, access point, Node B, eNB, gNB, WLAN access point, or the like. In one example, aspect apparatus <NUM> may be a network node or gNB acting as a master node. According to certain aspects, apparatus <NUM> may be controlled by memory <NUM> and processor <NUM> to perform the functions associated with any of the aspects described herein, such as the flow, signaling or block diagrams illustrated in <FIG> or <FIG> discussed below. In certain aspects, apparatus <NUM> may be configured to prevent count wrap-around, for example, where a UE is configured in dual or multi-connectivity.

For instance, in some aspects, apparatus <NUM> may be controlled by memory <NUM> and processor <NUM> to receive, from a node hosting PDCP, a counter check request that indicates that the count wrap-around is to occur soon. In certain aspects, the counter check request message may include the count value that is approaching its maximum value. Upon receiving the counter check request message and possibly observing or determining the high count value approaching its maximum value, apparatus <NUM> may be controlled by memory <NUM> and processor <NUM> to initiate DRB release and add a new bearer, which in turn may avoid the count wrap-around. In one example aspect, the highest downlink (DL) and/or uplink (UL) count value (e.g., <NUM>) may be included in the received counter check request message to indicate that the count wrap-around event is to occur soon and that the master node should take an action for the given bearer. However, the inclusion of the DL and UL count values in the counter check request message may be optional. According to another aspect, the absence of count value fields in the received counter check request message may indicate, to the apparatus <NUM>, that the counter check request was sent for the reason of indicating a count wrap-around event and apparatus <NUM> may then be controlled to initiate DRB release and, in an optional aspect, to add the new bearer.

<FIG> illustrates an example of an apparatus <NUM> according to another aspect. In an aspect, apparatus <NUM> may be a node, host, or server in a communications network or serving such a network. For example, apparatus <NUM> may be a base station, a Node B, an evolved Node B (eNB), <NUM> Node B or access point, next generation Node B (NG-NB or gNB), WLAN access point, mobility management entity (MME), and/or subscription server associated with a radio access network, such as a GSM network, LTE network, <NUM> or NR.

In some example aspects, apparatus <NUM> may include one or more processors, one or more computer-readable storage medium (for example, memory, storage, or the like), one or more radio access components (for example, a modem, a transceiver, or the like), and/or a user interface. In some aspects, apparatus <NUM> may be configured to operate using one or more radio access technologies, such as GSM, LTE, LTE-A, NR, <NUM>, WLAN, WiFi, NB-IoT, Bluetooth, NFC, MulteFire, and/or any other radio access technologies.

While a single processor <NUM> is shown in <FIG>, multiple processors may be utilized according to other aspects. For example, it should be understood that, in certain aspects, apparatus <NUM> may include two or more processors that may form a multiprocessor system (e.g., in this case processor <NUM> may represent a multiprocessor) that may support multiprocessing. In certain aspects, the multiprocessor system may be tightly coupled or loosely coupled (e.g., to form a computer cluster).

In some aspects, apparatus <NUM> may also include or be coupled to one or more antennas <NUM> for receiving a downlink signal and for transmitting via an uplink from apparatus <NUM>.

In other aspects, transceiver <NUM> may be capable of transmitting and receiving signals or data directly. Additionally or alternatively, in some aspects, apparatus <NUM> may include an input and/or output device (I/O device) or I/O circuitry. In certain aspects, apparatus <NUM> may further include a user interface, such as a graphical user interface or touchscreen.

In an aspect, memory <NUM> stores software modules that provide functionality when executed by processor <NUM>. According to an example aspect, apparatus <NUM> may optionally be configured to communicate with apparatus <NUM> via a wireless or wired communications link <NUM>.

As discussed above, according to some aspects, apparatus <NUM> may be a network node or RAN node, such as a base station, access point, Node B, eNB, gNB, WLAN access point, or the like. In one example, aspect apparatus <NUM> may be a network node hosting PDCP, for example a secondary network node. According to certain aspects, apparatus <NUM> may be controlled by memory <NUM> and processor <NUM> to perform the functions associated with any of the aspects described herein, such as the flow, signaling or block diagrams illustrated in <FIG> or <FIG> discussed below. In certain aspects, apparatus <NUM> may be configured to prevent count wrap-around, for example, where a UE is configured in dual or multi-connectivity.

For example, in certain aspects, apparatus <NUM> may be controlled by memory <NUM> and processor <NUM> to determine or detect that count wrap-around is imminent on the bearer. In one example, the count may be a PDCP count. According to an aspect, upon detecting the imminent count wrap-around, apparatus <NUM> may be controlled by memory <NUM> and processor <NUM> to transmit, to a master node, a counter check request that indicates that the count wrap-around is to occur soon. In certain aspects, the counter check request message may include the count value that is approaching its maximum value. According to one aspect, the transmission of the counter check request message, and optionally including the high count value in the message, triggers the master node to initiate DRB release and add a new bearer, which in turn may avoid the count wrap-around. In one example aspect, the highest downlink (DL) and/or uplink (UL) count value (e.g., <NUM>) may be included in the transmitted counter check request message to indicate that the count wrap-around event is to occur soon and that the master node should take an action for the given bearer. However, the inclusion of the DL and UL count values in the counter check request message may be optional. According to another aspect, the absence of count value fields in the transmitted counter check request message may indicate, to the master node, that the counter check request was sent for the reason of indicating a count wrap-around event and the master node may then be triggered to initiate DRB release and add the new bearer.

<FIG> illustrates an example flow diagram of a method, according to an aspect. In certain aspects, the method is a process for preventing or avoiding count wrap-around (e.g., PDCP count) for non-master node terminated bearers in dual-connectivity or multi-connectivity, according to an example aspect. In one aspect, the method is performed by a master node.

In an aspect, the method of <FIG> includes at <NUM>, receiving, e.g., from a node hosting PDCP, a counter check request that indicates that the count wrap-around will be occurring soon. In certain aspects, the counter check request message includes the count value that is approaching its maximum value. Upon receiving the counter check request message and observing the high count value in it, the method includes, at <NUM>, initiating DRB release and adding a new bearer, which in turn may avoid the count wrap-around. In one example aspect, the highest downlink (DL) and/or uplink (UL) count value (e.g., <NUM>) may be included in the received counter check request message to indicate that the count wrap-around event is to occur soon and that the master node should take an action for the given bearer.

<FIG> illustrates an example flow diagram of a method, according to another aspect. The method of <FIG> is a process for informing a dual-connectivity or multi-connectivity master node of an impending packet counter value wrap-around. According to one aspect, the wrap-around is a PDCP counter for non-master node terminated bearers in dual-connectivity. In an aspect, the method is performed by a secondary node hosting PDCP.

In an aspect, the method of <FIG> includes at <NUM>, determining or detecting that a count wrap-around is imminent. The method then includes at <NUM>, transmitting, to a master node, a counter check request that indicates that the count wrap-around is to occur soon. In certain aspects, the transmitting <NUM> includes transmitting the counter check request message to include the count value that is approaching its maximum value. According to one aspect, the transmitting <NUM> of the counter check request message, and including the high count value in the message, triggers the master node to initiate DRB release and add a new bearer, which in turn may avoid the impending count wrap-around. In one example aspect, the highest downlink (DL) and/or uplink (UL) count value (e.g., <NUM>) may be included in the transmitted counter check request message to indicate that the count wrap-around event is to occur soon and that the master node should take an action for the given bearer.

Therefore, aspects of the disclosure provide several technical improvements, enhancements, and/or advantages. Various example aspects provide an approach for avoiding PDCP count wrap around. Accordingly, as a result of certain aspects, network throughput and UE throughput performance may be enhanced. As such, aspects of the disclosure can improve performance and throughput of networks and network nodes including, for example, access points, base stations/eNBs/gNBs, and mobile devices or UEs. Accordingly, the use of aspects of the disclosure result in improved functioning of communications networks and their nodes.

In some aspects, the functionality of any of the methods, processes, signaling diagrams, algorithms or flow charts described herein may be implemented by software and/or computer program code or portions of code stored in memory or other computer readable or tangible media, and executed by a processor.

In some aspects, an apparatus may be included or be associated with at least one software application, module, unit or entity configured as arithmetic operation(s), or as a program or portions of it (including an added or updated software routine), executed by at least one operation processor. Programs, also called program products or computer programs, including software routines, applets and macros, may be stored in any apparatus-readable data storage medium and include program instructions to perform particular tasks.

A computer program product may comprise one or more computer-executable components which, when the program is run, are configured to carry out aspects. The one or more computer-executable components may be at least one software code or portions of it. Modifications and configurations required for implementing functionality of an aspect may be performed as routine(s), which may be implemented as added or updated software routine(s). Software routine(s) may be downloaded into the apparatus.

Software or a computer program code or portions of it may be in a source code form, object code form, or in some intermediate form, and it may be stored in some sort of carrier, distribution medium, or computer readable medium, which may be any entity or device capable of carrying the program. The computer readable medium or computer readable storage medium may be a non-transitory medium.

In other aspects, the functionality may be performed by hardware or circuitry included in an apparatus (e.g., apparatus <NUM> or apparatus <NUM>), for example through the use of an application specific integrated circuit (ASIC), a programmable gate array (PGA), a field programmable gate array (FPGA), or any other combination of hardware and software. In yet another aspect, the functionality may be implemented as a signal, a non-tangible means that can be carried by an electromagnetic signal downloaded from the Internet or other network.

According to an aspect, an apparatus, such as a node, device, or a corresponding component, may be configured as circuitry, a computer or a microprocessor, such as single-chip computer element, or as a chipset, including at least a memory for providing storage capacity used for arithmetic operation and an operation processor for executing the arithmetic operation.

One aspect is directed to a method that may include receiving, from a node hosting PDCP for a data radio bearer (DRB), a counter check request that indicates that a count wrap-around will be occurring soon. In certain aspects, the method may then include, in response to receiving the request, initiating release of the DRB and optionally adding a new bearer.

Another aspect is directed to an apparatus including at least one processor and at least one memory comprising computer program code. The at least one memory and computer program code may be configured, with the at least one processor, to cause the apparatus at least to receive, from a node hosting PDCP for a data radio bearer (DRB), a counter check request that indicates that a count wrap-around will be occurring soon. In certain aspects, the at least one memory and computer program code may be configured, with the at least one processor, to cause the apparatus at least to, in response to receiving the request, initiate release of the DRB and optionally add a new bearer.

Another aspect is directed to an apparatus including receiving means for receiving, from a node hosting PDCP for a data radio bearer (DRB), a counter check request that indicates that a count wrap-around will be occurring soon. In certain aspects, the apparatus may then include, in response to receiving the request, initiating means for initiating release of the DRB and optionally adding a new bearer.

Another aspect is directed to a method that may include determining or detecting that a counter wrap-around is imminent. The method may then include transmitting, to a master node, a counter check request that indicates that the counter wrap-around is to occur soon, which may trigger the master node to initiate data radio bearer (DRB) release and optionally adding a new bearer. In certain aspects, the indicating may include transmitting the counter check request message to include the count value that is approaching its maximum value.

Another aspect is directed to an apparatus including at least one processor and at least one memory comprising computer program code. The at least one memory and computer program code may be configured, with the at least one processor, to cause the apparatus at least to determine or detect that a counter wrap-around is imminent. The at least one memory and computer program code may be further configured, with the at least one processor, to cause the apparatus at least to transmit, to a master node, a counter check request that indicates that the counter wrap-around is to occur soon, which may trigger the master node to initiate data radio bearer (DRB) release and optionally adding a new bearer. In certain aspects, the transmitted counter check request message may include the count value that is approaching its maximum value.

Claim 1:
A method, comprising:
receiving (<NUM>), by a master node from a secondary node hosting packet data convergence protocol for a data radio bearer that is terminated by the secondary node, a counter check request including a packet data convergence protocol count value approaching its maximum value, wherein the counter check request indicates that a count wrap-around event is to occur, wherein a user equipment is configured in multi-connectivity with the master node and the secondary node;
determining, by the master node, that the packet data convergence protocol count value is approaching its maximum value; and
in response to the determining, initiating (<NUM>), by the master node release of the data radio bearer and add of a new data radio bearer.