Handling of Media Access Control (MAC) Entities During Secondary Cell Group (SCG) Deactivation / Reactivation

Abstract

An embodiment includes a method for a user equipment (UE) configured to communicate with a wireless network via a plurality of cell groups (e.g., an MCG and an SCG). Such a method includes, upon deactivation of one of the cell groups (e.g., an SCG), suspending a medium access control (MAC) entity associated with the deactivated cell group, and performing one or more first operations on the MAC entity upon suspension of the MAC entity. Such a method also includes performing one or more second operations related to reporting uplink (UL) data available for transmission via the deactivated cell group while the MAC entity is suspended. Such a method also includes, upon reactivation of the deactivated cell group, performing one or more third operations on the MAC entity, and resuming the MAC entity based on the one or more third operations. Other embodiments include a UE configured to perform such a method.

Description

Technical Field

[0001] The present disclosure generally relates to wireless networks, and more particularly to techniques for reducing the energy consumed by a user equipment (UE) when connected to multiple cell groups in a wireless network, especially when one of the cell groups is in a deactivated state.

Background Art

[0002] Long Term Evolution (LTE) is an umbrella term referring to a radio access technology developed within the Third Generation Partnership Project (3GPP), also known as the Evolved UTRAN (E-UTRAN), and first standardized in Releases 8 (Rel-8) and 9 (Rel-9). LTE targets various licensed frequency bands and is accompanied by improvements to non-radio aspects, generally referred to as the System Architecture Evolution (SAE), which includes the Evolved Packet Core (EPC) network. LTE continues to evolve through subsequent releases.

[0003] LTE Rel-10 supports bandwidths greater than 20 MHz. To remain compatible with legacy UEs from previous releases (e.g., LTE Rel-8), wideband LTE Rel-10 carriers (e.g., >20 MHz) should each appear as a plurality of carriers ( "component carriers" or CCs), each preferably having the same structure as an LTE Rel-8 carrier. Rel-10 UEs can receive multiple CCs based on carrier aggregation (CA). A CC can also be regarded as a "cell", and thus a UE in CA has one primary cell (PCell) and one or more secondary cells (SCells).

[0004] LTE Rel-12 introduced dual connectivity (DC), whereby a UE can be connected to two network nodes simultaneously, thereby improving connection robustness and / or capacity. In LTE DC, these two network nodes are called the master eNB (MeNB) and the secondary eNB (SeNB), or more generally, the master node (MN) and the secondary node (SN). In particular, a master cell group (MCG) related to the MN and a secondary cell group (SCG) related to the SN are configured for the UE. Each cell group includes a PCell and may include one or more SCells.

[0005] Currently, the fifth generation of cellular systems (referred to as "5G"), also known as New Radio (NR), is being standardized within 3GPP. NR has been developed for maximum flexibility to support a variety of different use cases. These include enhanced mobile broadband (eMBB), machine type communication (MTC), ultra-reliable low latency communication (URLLC), sidelink device-to-device (D2D), and several other use cases. 5G / NR technology shares many similarities with 4G / LTE. For example, both PHYs utilize a similar configuration of time-domain physical resources, with a 1 ms subframe consisting of multiple slots of equal duration, and each slot containing multiple OFDM-based symbols.

[0006] Several DC (or more generally, multi-connectivity) scenarios are considered for NR. These include NR-DC which is similar to LTE-DC mentioned above, except that both the MN and the SN (referred to as "gNB") adopt the NR interface to communicate with the UE. Further, NR can support various multi-RAT DC (MR-DC) scenarios where the UE can be configured to utilize resources from a node providing E-UTRA / LTE access and another node providing NR access. One node acts as the MN (e.g., providing the MCG), the other acts as the SN (e.g., providing the SCG), the MN and the SN are connected via a network interface, and at least the MN is connected to the core network (e.g., EPC or 5GC).

Summary of the Invention

[0007] To improve the network energy efficiency and battery life for the UE in MR-DC, 3GPP Rel-17 includes techniques for efficient SCG / Secondary Cell activation / deactivation. This can be important for MR-DC setups involving NR SCG as in some cases it has been found that the NR UE energy consumption can be 3 to 4 times higher than that of LTE. However, there are various issues, problems, and / or difficulties regarding the handling of the MAC entities of the SCG during SCG deactivation and subsequent reactivation.

[0008] Embodiments of the present disclosure provide specific improvements for the handling of UE MAC entities during cell group (e.g., SCG) deactivation and / or reactivation, such as by facilitating solutions to overcome the exemplary problems summarized above and described in more detail below.

[0009] Embodiments of the present disclosure include a method (e.g., a procedure) for a UE configured to communicate with a wireless network via a plurality of cell groups.

[0010] These exemplary methods can include, when deactivating one of a plurality of cell groups, interrupting the MAC entity associated with the deactivated cell group, and performing one or more first operations on the MAC entity when interrupting the MAC entity. These exemplary methods can also include performing one or more second operations related to reporting UL data available for transmission via the deactivated cell group while the MAC entity is interrupted. These exemplary methods can further include, when reactivating the deactivated cell group, performing one or more third operations on the MAC entity and resuming the MAC entity based on the one or more third operations.

[0011] For example, the plurality of cell groups includes an MCG and an SCG, and the SCG is the cell group that is deactivated and reactivated.

[0012] In some embodiments, performing a first operation on the MAC entity when interrupting includes canceling one or more of the following ongoing procedures, namely, · Random access (RA), · Scheduling request (SR), · Power headroom report (PHR), · Consistent listen before talk (LBT) failure recovery, · Beam failure recovery (BFR), · Preemptive buffer status report (BSR), · Recommended bitrate query, · UL configured grant (CG) confirmation, · Sidelink (SL) CG confirmation, and · Desired guard symbol (DSG) query which can include canceling one or more of them.

[0013] In some of these embodiments, · An ongoing RA procedure not caused by a BSR pending for transmission is cancelled, but an ongoing RA procedure caused by a BSR pending for transmission is not cancelled, and · An ongoing SR procedure not caused by a BSR pending for transmission is cancelled, but an ongoing SR procedure caused by a BSR pending for transmission is not cancelled, One or more of which are applied.

[0014] In some embodiments, at the time of interruption, one or more first operations performed on the MAC entity include maintaining the BSR procedure for the LCH of the MAC entity that was in progress at the time of interruption of the MAC entity.

[0015] In some embodiments, at the time of interruption, one or more first operations performed on the MAC entity are the following operations, namely, · Setting the new data indicator (NDI) for the ongoing UL hybrid automatic repeat request (HARQ) process to a value of 0, and · Flushing the soft buffer for the ongoing downlink (DL) HARQ process, and · Resetting one or more active counters, and · Stopping or considering one or more running timers as expiring, and · Interrupting one or more UL resource grants, and · Releasing one or more physical UL control channel (PUCCH) resources, and · Releasing one or more temporary identifiers allocated by the radio network include one or more of.

[0016] In some of these embodiments, one or more operating timers that are considered to be stopped or expired, at the time of interruption, · a first timer that triggers a regular BSR, and · a second timer that triggers an SR on a primary cell of a deactivated cell group include all operating timers, except that at least one of them continues to operate.

[0017] In some of these embodiments, an interrupted UL resource grant includes only type-1 UL CG for all cells having an associated timer that has not expired. In some of these embodiments, a released PUCCH resource includes PUCCH resources for all cells having an associated timer that has not expired, excluding the PUCCH resource for transmitting an SR.

[0018] In some embodiments, one or more second operations performed while the MAC entity is interrupted include starting a BSR procedure for reporting UL data available for transmission via a deactivated cell group, starting an SR procedure when a physical UL shared channel (PUSCH) resource is not available for transmitting a BSR, and starting a RA procedure when a PUCCH resource is not available for transmitting an SR.

[0019] In some of these embodiments, the SR procedure is started with substantially zero delay after determining that a PUSCH resource is not available for transmitting a BSR. In other embodiments, starting the BSR procedure is based on the availability of UL data for transmission in a subset of all logical channels (LCH) of the MAC entity. In some of these embodiments, the subset of LCHs is · only LCHs not associated with split secondary RLC entities, · Only the LCHs belonging to the logical channel group (LCG), · Only the LCHs carrying delay-sensitive UL data, and · Specific LCHs indicated by the radio network via RRC signaling include one or more of them.

[0020] In other embodiments, one or more second operations performed while the MAC entity is suspended are to monitor the availability of UL data on one or more LCHs of the MAC entity, and based on detecting the availability of UL data on at least one of the monitored LCHs, start an SR procedure, and start an RA procedure when the PUCCH resource is not available for transmitting an SR. In some of these embodiments, starting the SR procedure is · While the MAC entity is suspended, no other SR procedure has been started, or · The physical UL shared channel (PUSCH) resource is not available for transmitting a BSR, and may be further based on one or more of them.

[0021] In some of these embodiments, the monitored LCH is the following subset of all LCHs of the MAC entity, namely, · Only the LCHs not related to the split secondary RLC entity, · Only the LCHs belonging to the LCG, · Only the LCHs carrying delay-sensitive UL data, and · Specific LCHs indicated by the radio network via RRC signaling include one of them.

[0022] In some embodiments, one or more third operations (2030) performed when reactivating a deactivated cell group are · Resume one or more interrupted UL resource grants, and · Reset each prioritization parameter associated with a plurality of logical channels of the MAC entity to a predetermined initial value, and include one or more of the above.

[0023] In some embodiments, resuming the MAC entity based on one or more third operations means (for example, at that time, the MAC entity is considered to be resumed) · Starting or resuming the buffer status reporting procedure for a plurality of logical channels of the MAC entity based on the prioritization parameters associated with the plurality of LCHs being reset to a predetermined initial value, and · Sending an acknowledgment response to a cell group activation command from the wireless network, and · Starting the SR procedure in the reactivated cell group, and · Starting the RA procedure in the reactivated cell group can include one or more of the above.

[0024] In some of these embodiments, the predetermined initial value to which the prioritization parameter is reset is 0.

[0025] Other embodiments include a UE (e.g., a wireless device, an IoT device, etc., or (one or more) components thereof) configured to perform operations corresponding to any of the exemplary methods described herein. Other embodiments include a non-transitory computer-readable medium storing program instructions that, when executed by a processing circuit, configure such a UE to perform operations corresponding to any of the exemplary methods described herein.

[0026] These and other embodiments disclosed herein enable a cell group (e.g., SCG) deactivation and reactivation and a corresponding reduction in UE energy consumption by, for example, enabling the UE to trigger the BSR procedure and / or data volume reporting in a fast and reliable manner, which can facilitate the interruption and resumption of the MAC entity. In this way, the network can be quickly informed of the UE's need for reactivation of a deactivated cell group (e.g., due to the arrival of UL data traffic for the SCG), which can reduce and / or minimize the transmission latency of UL data.

[0027] These and other objects, features, and advantages of the embodiments of the present disclosure will become apparent upon reading the following detailed description of the invention in view of the drawings described briefly below.

Brief Description of the Drawings

[0028]

Figure 1

Figure 2

Figure 3

Figure 4

Figure 5

Figure 6

Figure 7

Figure 8

Figure 9

Figure 10

Figure 11

Figure 12

Figure 13

Figures 14A - 14B

Figures 15A - 15C

Figure 16

Figure 17

Figure 18

Figure 19

Figures 20A - 20B

Figure 21

Figure 22

Figure 23

Figure 24

Figure 25

Figure 26

DETAILED DESCRIPTION OF THE INVENTION

[0029] Next, with reference to the accompanying drawings, some of the embodiments contemplated herein will be described more fully. However, other embodiments are included within the scope of the subject matter disclosed herein, and the disclosed subject matter should not be construed as limited to only the embodiments described herein. Rather, these embodiments are provided as examples to convey the scope of the subject matter to those skilled in the art.

[0030] Generally, all terms used in this specification should be interpreted according to their ordinary meanings in the relevant technical field, unless a different meaning is clearly given and / or implied from the context in which the term is used. Any reference to an element, apparatus, component, means, step, etc. should be construed openly as referring to at least one instance of that element, apparatus, component, means, step, etc., unless otherwise explicitly stated. Any step of any method disclosed herein need not be performed in the exact order disclosed, unless the step is explicitly described as following or preceding another step and / or it is implicit that the step must follow or precede another step. Any feature of any of the embodiments disclosed herein may, where appropriate, be applied to any other embodiment. Similarly, any advantage of any of the embodiments may be applied to any other embodiment, and vice versa. Other objects, features, and advantages of the enclosed embodiments will become apparent from the following description.

[0031] Furthermore, the following terms are used throughout the description given below. · Wireless node: As used herein, a "wireless node" can be either a "wireless access node" or a "wireless device". · Wireless access node: As used herein, a "wireless access node" (or equivalently, a "wireless network node", "wireless access network node", or "RAN node") can be any node in a radio access network (RAN) of a cellular communication network that is operative to transmit and / or receive signals wirelessly. Some examples of wireless access nodes include, but are not limited to, base stations (e.g., new radio (NR) base stations (gNB / en-gNB) in a 3GPP fifth generation (5G) NR network, or evolved or evolved node Bs (eNB / ng-eNB) in a 3GPP LTE network), base station distributed components (e.g., CU and DU), base station control plane and / or user plane components (e.g., CU-CP, CU-UP), high-power or macro base stations, low-power base stations (e.g., micro base stations, pico base stations, femto base stations, or home base stations, etc.), wireless access backhaul integrated transmission (IAB) nodes, transmission points, remote radio units (RRU or RRH), and relay nodes. · Core network node: As used herein, a "core network node" is any type of node in a core network. Some examples of core network nodes include, for example, a mobility management entity (MME), a serving gateway (S-GW), a packet data network gateway (P-GW), an access and mobility management function (AMF), a session management function (SMF), a user plane function (UPF), a service capability exposure function (SCEF), etc. · Wireless Device: As used herein, "Wireless Device" (or abbreviated as "WD") is any type of device that has access to a cellular communication network (i.e., is served by a cellular communication network) by communicating wirelessly with a network node and / or other wireless devices. Communicating wirelessly can involve transmitting and / or receiving wireless signals using electromagnetic waves, radio waves, infrared waves, and / or other types of signals suitable for transmitting information in the air. Some examples of wireless devices include, but are not limited to, smartphones, mobile phones, cell phones, Voice over IP (VoIP) phones, wireless local loop phones, desktop computers, personal digital assistants (PDAs), wireless cameras, gaming consoles or devices, music storage devices, playback appliances, wearable devices, wireless endpoints, mobile stations, tablets, laptop computers, laptop embedded equipment (LEE), laptop-mounted equipment (LME), smart devices, wireless customer premise equipment (CPE), machine type communication (MTC) devices, Internet of Things (IoT) devices, in-vehicle wireless terminal devices, etc. Unless otherwise stated, the term "Wireless Device" is used interchangeably herein with the term "User Equipment" (or abbreviated as "UE"). · Network Node: As used herein, "Network Node" is any node that is part of either a radio access network (e.g., the radio access node or equivalent name described above) or the core network of a cellular communication network (e.g., the core network node described above). Functionally, a network node is a device that is configured, constructed, and / or operable to communicate directly or indirectly with a wireless device and / or other network nodes or devices in the cellular communication network to enable and / or provide wireless access to the wireless device and / or to perform other functions (e.g., administration) in the cellular communication network.

[0032] The description in this specification focuses on 3GPP cellular communication systems, and thus it should be noted that 3GPP terminology or terminology similar to 3GPP terminology is often used. However, the concepts disclosed in this specification are not limited to 3GPP systems. Further, although the term "cell" is used in this specification, a beam may be used instead of a cell (especially with respect to 5G NR), and thus it should be understood that the concepts described in this specification apply equally to both cells and beams.

[0033] An overall exemplary architecture of a network with LTE and SAE is shown in FIG. 1. The E-UTRAN 100 includes one or more evolved Node Bs (eNBs), such as eNBs 105, 110, and 115, and one or more user equipments (UEs), such as UE 120. The "user equipment" or "UE" used within 3GPP specifications means any wireless communication device (e.g., a smartphone or a computing device) capable of communicating with 3GPP standard-compliant network equipment, including E-UTRAN as well as UTRAN and / or GERAN as is commonly known for 3rd generation ("3G") and 2nd generation ("2G") 3GPP RAN.

[0034] As specified by 3GPP, the E-UTRAN 100 serves the role of all radio-related functions in the network, including radio bearer control, radio admission control, radio mobility control, scheduling, and dynamic allocation of resources to the UE in the uplink and downlink, as well as the security of communication with the UE. These functions are present in the eNB, such as eNBs 105, 110, and 115. Each of the eNBs can serve a geographical coverage area that includes one or more cells, including cells 106, 111, and 115 served by eNBs 105, 110, and 115, respectively.

[0035] In E-UTRAN, eNBs communicate with each other via the X2 interface as shown in FIG. 1. The eNB also serves as the E-UTRAN interface to the EPC 130. Specifically, in FIG. 1, it serves as the S1 interface to the Mobility Management Entity (MME) and Serving Gateway (S-GW), collectively shown as MME / S-GW 134 and 138. Generally, the MME / S-GW handles both the overall control of the UE and the data flow between the UE and the rest of the EPC. More specifically, the MME processes the signaling (e.g., control plane) protocol between the UE and the EPC, known as the Non-Access Stratum (NAS) protocol. The S-GW handles all Internet Protocol (IP) data packets (e.g., data or user plane) between the UE and the EPC and acts as the local mobility anchor for the data bearer when the UE moves between eNBs such as eNB 105, 110, and 115.

[0036] The EPC 130 can also include a Home Subscriber Server (HSS) 131 that manages user-related information and subscriber-related information. The HSS 131 can also provide support functions in mobility management, call setup and session setup, user authentication, and access authorization. The functions of the HSS 131 can relate to the functions of the legacy Home Location Register (HLR) and the Authentication Center (AuC) function or operation. The HSS 131 can also communicate with the MMEs 134 and 138 via their respective S6a interfaces.

[0037] In some embodiments, the HSS 131 can communicate with a User Data Repository (UDR), labeled as EPC-UDR 135 in FIG. 1, via the Ud interface. The EPC-UDR 135 can store user credentials after they have been encrypted by an AuC algorithm. These algorithms are not standardized (i.e., vendor-specific), and thus the encrypted credentials stored in the EPC-UDR 135 are inaccessible by vendors other than the vendor of the HSS 131.

[0038] FIG. 2 shows a block diagram of an exemplary control plane (CP) protocol stack between a UE, an eNB, and an MME. The exemplary protocol stack includes a physical (PHY) layer, a media access control (MAC) layer, a radio link control (RLC) layer, a packet data convergence protocol (PDCP) layer, and a radio resource control (RRC) layer between the UE and the eNB. The PHY layer is concerned with how characteristics are used and what characteristics are used to transfer data on a transport channel over an LTE radio interface. The MAC layer provides data transfer services on logical channels, maps the logical channels to PHY transport channels, and reallocates PHY resources to support these services. The RLC layer provides error detection and / or correction, concatenation, segmentation, reassembly, and reordering of data transferred to or from upper layers. The PDCP layer provides encryption / decryption and integrity protection for both the CP and the user plane (UP), and also provides other UP functions such as header compression. The exemplary protocol stack also includes non-access stratum (NAS) signaling between the UE and the MME.

[0039] The RRC layer controls the communication between the UE and the eNB in the radio interface, as well as the mobility of the UE between cells in the E-UTRAN. After the UE is powered on, the UE will be in the RRC_IDLE state until an RRC connection with the network is established, and when the RRC connection is established, the UE will transition to the RRC_CONNECTED state (for example, where data transfer can occur). After the connection with the network is released, the UE returns to RRC_IDLE. In the RRC_IDLE state, the UE does not belong to any cell, no RRC context is established for the UE (in E-UTRAN, for example), and the UE is out of UL synchronization with the network. Even so, the UE in the RRC_IDLE state is known in the EPC and has an assigned IP address.

[0040] Furthermore, in the RRC_IDLE state, the UE's radio is active on an intermittent reception (DRX) schedule set by the upper layer. During the DRX active period (also called the "DRX on duration"), the RRC_IDLE UE receives the system information (SI) broadcast by the serving cell, performs neighbor cell measurements to support cell reselection, and monitors the paging channel for pages from the EPC via the eNB serving the cell where the UE is camping.

[0041] The UE must perform a random access (RA) procedure to move from RRC_IDLE to the RRC_CONNECTED state. In the RRC_CONNECTED state, the cell serving the UE is known, and an RRC context is established in the serving eNB so that the UE and the eNB can communicate with each other. For example, a cell radio network temporary identifier (C-RNTI), i.e., UE identification information used for signaling between the UE and the network, is set for the UE in the RRC_CONNECTED state.

[0042] As briefly mentioned above, LTE Rel-12 introduced dual connectivity (DC), whereby a master cell group (MCG) provided by a master node (MN) and a secondary cell group (SCG) provided by a secondary node (SN) can be configured for a UE. Each of the CGs is a group of serving cells that includes one MAC entity, a set of logical channels with associated RLC entities, a primary cell (PCell), and optionally one or more secondary cells (SCells). The term "special cell" (abbreviated as "SpCell") refers to the MCG PCell or the primary SCG cell (PSCell) depending on whether the UE's MAC entity is associated with the MCG or the SCG, respectively. In non-DC operation (e.g., CA), the SpCell refers to the PCell. The SpCell is always activated and supports physical uplink control channel (PUCCH) transmission and contention-based random access by the UE.

[0043] The MN provides system information (SI), terminates the control plane connection to the UE, and is thus the control node of the UE, including handovers to the SN. The SN provides additional radio resources (e.g., bearers) for some bearers having resources from both the MCG and the SCG. Reconfiguration, addition, and deletion of SCells can be performed by the RRC. When adding a new SCell, dedicated RRC signaling is used to send all the required SI of the SCell to the UE so that the UE does not need to obtain SI directly from the SCell broadcast. It is also possible to support CA in either or both of the MCG and the SCG. In other words, either or both of the MCG and the SCG can include multiple cells that function in CA.

[0044] Both the MN and the SN can terminate the user plane (UP) to the UE, which includes three different types of bearers. The MCG bearer is terminated at the MN, and the S1-U connection for the corresponding bearer(s) to the S-GW is terminated at the MN. The SN is not involved in the transport of UP data for the MCG bearer. Similarly, the SCG bearer is terminated at the SN that can be directly connected to the S-GW via S1-U. The MN is not involved in the transport of UP data for the SCG bearer. Split bearers (and their corresponding S1-U connections to the S-GW) are also terminated at the MN with PDCP data transferred between the MN and the SN via X2-U.

[0045] Figure 3 shows a high-level diagram of a 5G network architecture consisting of a Next Generation RAN (NG-RAN) 399 and a 5G Core (5GC) 398. The NG-RAN 399 can include a set of g Node Bs (gNBs) 300, 350, etc., connected via interfaces 302, 352 respectively, and connected to the 3GC via one or more NG interfaces. Further, the gNBs can be connected to each other via one or more Xn interfaces, such as the Xn interface 340 between gNB 300 and gNB 350. Regarding the NR interface to the UE, each of the gNBs can support Frequency Division Duplexing (FDD), Time Division Duplexing (TDD), or a combination thereof.

[0046] The NG-RAN 399 is stratified into a Radio Network Layer (RNL) and a Transport Network Layer (TNL). The NG-RAN architecture, i.e., the NG-RAN logical nodes and the interfaces between the NG-RAN logical nodes, is defined as part of the RNL. For each NG-RAN interface (NG, Xn, F1), the related TNL protocols and functions are specified. The TNL provides services for user plane transport and signaling transport.

[0047] The NG RAN logical nodes shown in FIG. 3 include a central (or centralized) unit (CU or gNB-CU) and one or more distributed (or non-centralized) units (DU or gNB-DU). For example, gNB 300 includes gNB-CU 310 and gNB-DUs 320 and 330. The CU is a logical node that hosts upper layer protocols and implements various gNB functions such as controlling the operation of the DUs. Each DU is a logical node that hosts lower layer protocols and can include various subsets of gNB functions. Thus, each of the CU and DU can include various circuits required to implement their respective functions, including a processing circuit, a transceiver circuit (e.g., for communication), and a power supply circuit.

[0048] The gNB-CU connects to the gNB-DU on each respective F1 logical interface, such as interfaces 322 and 332 shown in FIG. 3. The gNB-CU and the connected gNB-DUs appear to other gNBs and the 5GC as just a gNB. In other words, the F1 interface is not visible beyond the gNB-CU. In the gNB split CU-DU architecture shown by FIG. 3, DC can be achieved by configuring the UE to connect to multiple DUs served by the same CU, or by configuring the UE to connect to multiple DUs served by different CUs.

[0049] As briefly mentioned above, 5G / NR technology shares many similarities with 4G / LTE. For example, both PHYs utilize a similar configuration of time domain physical resources, making a 1 ms subframe that includes multiple slots of equal duration, and each slot includes multiple OFDM-based symbols. As another example, the NR RRC layer includes the RRC_IDLE state and the RRC_CONNECTED state as in LTE, but adds another state known as RRC_INACTIVE.

[0050] In addition to providing coverage via "cells" as in the case of LTE, the NR network also provides coverage via "beams". Generally, a downlink (DL) "beam" is the coverage area of network-transmitted RS that can be measured or monitored by a UE. For example, these RS can include any one of, or a combination of, SS / PBCH blocks (SSB), CSI-RS, 3rd reference signals (or any other synchronization signals), positioning RS (PRS), DMRS, phase-tracking reference signals (PTRS), etc. Generally, SSB is available to all UEs regardless of the RRC state, while other RS (e.g., CSI-RS, DM-RS, PTRS) are associated with specific UEs having a network connection, i.e., in the RRC_CONNECTED state.

[0051] DC is also an important feature for 5G / NR networks. 3GPP TR38.804 (v14.0.0) describes various exemplary DC scenarios or configurations where the MN and SN can apply NR RAT, LTE RAT, or both, and can be connected to either EPC or 5GC. The following terminology is used to describe these exemplary DC scenarios or configurations. · DC: LTE DC (i.e., as described above, both the MN and SN employ LTE). · EN-DC: LTE-NR DC where the MN (eNB) employs LTE and the SN (gNB) employs NR, and both are connected to the EPC. · NGEN-DC: LTE-NR dual connectivity where the UE is connected to one ng-eNB serving as the MN and one gNB serving as the SN. The ng-eNB is connected to 5GC, and the gNB is connected to the ng-eNB via the Xn interface. · NE-DC: LTE-NR dual connectivity where the UE is connected to one gNB serving as the MN and one ng-eNB serving as the SN. The gNB is connected to 5GC, and the ng-eNB is connected to the gNB via the Xn interface. · NR-DC (or NR-NR DC): Both the MN and the SN adopt NR and are connected to the 5GC via the NG. · MR-DC (Multi-RAT DC): Multiple Rx / Tx UEs can be configured to utilize resources provided by two different nodes connected via a non-ideal backhaul, namely, one providing E-UTRA access and the other providing NR access, which is a generalization of intra-E-UTRA dual connectivity (DC) described in 3GPP TS36.300 (v16.0.0). One node acts as the MN and the other as the SN, with one using LTE and the other using NR. The MN and the SN are connected via a network interface, and at least the MN is connected to the core network. EN-DC, NE-DC, and NGEN-DC are different exemplary cases of MR-DC.

[0052] Figure 4 shows a high-level diagram of DC combined with carrier aggregation. In this figure, each of the MN and the SN can be either an eNB or a gNB according to the various DC scenarios mentioned above. The MN provides an MCG consisting of a PCell and three SCell configured in CA, and the SN provides an SCG consisting of a PSCell and three SCell configured in CA.

[0053] Figure 5 shows a high-level diagram of an exemplary network architecture supporting EN-DC, including E-UTRAN 599 and EPC 598. As shown in the figure, E-UTRAN 599 can include en-gNBs (e.g., 510a, b) and eNBs (e.g., 520a, b) interconnected with each other via their respective X2 (or X2-U) interfaces. The eNBs can be similar to those shown in FIG. 1, and the ng-eNBs can be similar to the gNBs shown in FIG. 3, except that they are connected to the EPC 598 via the S1-U interface instead of being connected to the 5GC via the X2 interface. The eNBs are also connected to the EPC 598 via the S1 interface, similar to the configuration shown in FIG. 1. More specifically, the en-gNBs (e.g., 510a, b) and eNBs (e.g., 520a, b) are connected to the MMEs (e.g., 530a, b) and S-GWs (e.g., S-540a, b) in the EPC.

[0054] Each of the en-gNB and the eNB can serve a geographical coverage area including another cell, including the cells 511a~b and 521a~b illustrated as examples in FIG. 5. Depending on the cell in which the UE 505 is located, the UE 505 can communicate with the en-gNB or eNB serving that cell via the NR or LTE radio interface, respectively. Further, the UE 505 can be in EN-DC between a first cell served by an eNB, such as cells 520a and 510a shown in FIG. 5, and a second cell served by an en-gNB.

[0055] FIG. 6 shows a high-level diagram of an exemplary network architecture that supports an MR-DC configuration based on 5GC. More specifically, FIG. 6 shows an NG-RAN 699 and a 5GC 698. The NG-RAN 699 can include gNBs (e.g., 610a, b) and ng-eNBs (e.g., 620a, b) interconnected with each other via respective Xn interfaces. The gNBs and ng-eNBs are also connected to the 6GC 698 via an NG interface, and more specifically, are connected to access and mobility management functions (AMF, e.g., 630a, b) via respective NG-C interfaces and to user plane functions (UPF, e.g., 640a, b) via respective NG-U interfaces. Additionally, the AMF can communicate with one or more session management functions (SMF, e.g., 650a, b) and network exposure functions (NEF, e.g., 660a, b).

[0056] Each of the gNBs 610 can be similar to those shown in FIG. 5, and each of the ng-eNBs can be similar to the eNB shown in FIG. 1, except that they are connected to the 5GC 598 via an NG interface instead of being connected to the EPC via an S1 interface. Each of the gNBs and ng-eNBs can serve a geographic coverage area that includes another cell, including cells 611a - b and 621a - b shown as examples in FIG. 6. The gNBs and ng-eNBs can also use various directional beams to provide coverage in their respective cells. Depending on the cell in which the UE 605 is located, the UE 605 can communicate with the gNB or ng-eNB serving that cell via an NR or LTE radio interface, respectively. Further, the UE 605 can be in MR-DC connectivity with a first cell served by an ng-eNB and a second cell served by a gNB, such as cells 620a and 610a shown in FIG. 6.

[0057] Figures 7 to 8 show, respectively, the UP radio protocol architecture from the UE perspective for MR-DC using EPC (e.g., EN-DC) and the UP radio protocol architecture from the UE perspective for MR-DC using 5GC (e.g., NGEN-DC, NE-DC, and NR-DC). In both cases, the UE (700) supports MCG, SCG, and split bearers as described above. In the EN-DC configuration shown in Figure 7, the MCG bearer has either an LTE (e.g., E-UTRA) or NR PDCP layer, as well as the LTE RLC and MAC layers, and the SCG bearer has an NR PDCP, RLC, and MAC layers. The split bearer has an NR PDCP layer, as well as both the LTE RLC and MAC layers and the NR RLC and MAC layers. In the configuration shown in Figure 8, all bearers have an NR PDCP layer and the lower layers corresponding to the RAT used by the MN and SN. One difference between the architecture in Figure 7 and the architecture in Figure 8 is that the various bearers for MR-DC using 5GC are associated with QoS flows that terminate at the SDAP layer above PDCP.

[0058] Figures 9 to 10 show the UP radio protocol architecture from a network perspective for MR-DC (e.g., EN-DC) using EPC and the UP radio protocol architecture from a network perspective for MR-DC (e.g., NGEN-DC, NE-DC, and NR-DC) using 5GC, respectively. In the EN-DC configuration shown in Figure 9, the MCG bearers terminated at the MN have the PDCP layer of the RAT used by the MN, while all other bearers have the NR PDCP layer. All bearers have the lower layers related to the RAT of the (one or more) nodes at which they are terminated. In the configuration shown in Figure 10, all bearers have the NR PDCP layer and the lower layers related to the RAT of the (one or more) nodes at which they are terminated. From a network perspective, each MCG, SCG, and split bearer can be terminated either at the MN or at the SN. For example, the X2 or Xn interface between nodes will carry the traffic for the SCG or split bearer terminated at the MN PDCP layer to the lower layers at the SN. Similarly, X2 or Xn will carry the traffic for the MCG or split bearer terminated at the SN PDCP layer to the lower layers at the MN. One difference between the architecture in Figure 9 and the architecture in Figure 10 is that the various bearers for MR-DC using 5GC are related to the QoS flows at which they are terminated.

[0059] Figures 9 to 10 also have some DC-specific deformation modes. In EN-DC using EPC, the network can set either E-UTRA PDCP or NR PDCP for the MN-terminated MCG data radio bearer (DRB), but NR PDCP is always used for all other DRBs. In MR-DC using 5GC, NR PDCP is always used for all DRB types. In NGEN-DC, E-UTRA RLC / MAC is used at the MN, and NR RLC / MAC is used at the SN. In NE-DC, NR RLC / MAC is used at the MN, and E-UTRA RLC / MAC is used at the SN. In NR-DC, NR RLC / MAC is used at both the MN and the SN.

[0060] Figure 11 is a block diagram showing a high-level comparison of the CP architectures in LTE DC, EN-DC, and MR-DC using a 5G core network (5GC). One major difference is that in EN-DC and NR-DC, the SN has a separate NR RRC entity. This means that the SN can sometimes control the UE without the knowledge of the MN, but often the SN needs to cooperate with the MN. In LTE-DC, the RRC decision is always made by the MN (from the MN to the UE). Even so, since only the SN itself has knowledge of what kind of resources, capabilities, etc. the SN has, the LTE-DC SN still determines the SN configuration.

[0061] Another difference between LTE-DC and others is the use of split bearers for RRC. Split RRC messages are mainly used to create diversity, and the transmitting side can determine whether to select one of the links to schedule the RRC message, or the transmitting side can duplicate the message over both links. In DL, the path switching (or duplication over both) between the MCG leg or the SCG leg is left to the network implementation. On the other hand, in the case of UL, the network configures the UE to use MCG, SCG, or both for RRC messages. The terms "leg", "path" and "RLC bearer" are used interchangeably throughout this specification.

[0062] The UE receives bearer configuration in the radioBearerConfig IE that may be included in the RRCReconfiguration message. When MR-DC is configured for the UE, the UE will have two radio bearer configurations, one related to MCG (for the MN-terminated bearer) and one related to SCG (for the SN-terminated bearer). Each bearer has an associated PDCP configuration, and in the case of a split bearer, there is a field in the PDCP-Config IE that specifies the primary path to be used for UL data transmission, i.e., MCG or SCG. There is also a field ul-DataSplitThreshold included in the moreThanOneRLC IE. If the UL buffer in the UE corresponding to that split bearer is below this threshold, the UE will only perform a buffer status report (BSR) and / or send a UL scheduling request (SR) to the node hosting the primary path. For example, if the primary path is MCG, the UE will send the BSR and SR to the MN via the MCG MAC. If the UL buffer exceeds the threshold, the UE will send the BSR and SR to both the MN and the SN, and can transmit UL data in the (one or more) cell groups where the UE receives a UL grant.

[0063] Packet duplication (also referred to as "PDCP duplication" or "PDCP PDU duplication") can increase reliability and reduce latency, which can be extremely beneficial for ultra-reliable low-latency (URLLC) data services. When PDCP duplication is configured by RRC for a radio bearer, additional RLC entities and additional logical channels are added to the radio bearer to handle the duplicated PDCP protocol data units (PDUs). Thus, PDCP duplication involves sending the same PDCP PDU twice, i.e., once on the original (or primary) RLC entity and a second time on the additional (or secondary) RLC entity.

[0064] Note that the primary RLC entity is associated with the primary logical channel (LCH) and the secondary RLC entity is associated with the secondary LCH. When configuring duplication for a DRB, RRC also sets the state of PDCP duplication (i.e., activation or deactivation) at the time of (re)configuration. After configuration, the PDCP duplication state can then be dynamically controlled by MAC CE. In DC, the UE applies these MAC CE commands regardless of whether they are received via MCG or SCG.

[0065] As mentioned above, 3GPP Rel-17 includes a work item for efficient SCG / Secondary Cell (SCell) activation / deactivation for UEs in Multi-Radio Dual Connectivity (MR-DC). This can be particularly important for MR-DC configurations with NR Secondary Cell Group (SCG), as in some cases it has been found that the NR UE energy consumption can be 3 to 4 times higher than in the LTE case. 3GPP has previously specified the concept of a dormant LTE SCell and dormancy-like behavior such as the suspension of an NR SCell. In LTE, when an SCell is in a dormant state, the UE does not need to monitor the corresponding Physical Downlink Control Channel (PDCCH) or Physical Downlink Shared Channel (PDSCH) and cannot transmit on the corresponding uplink. This behavior is similar to that in the deactivated state, but the UE is also required to perform and report Channel Quality Indicator (CQI) measurements, which is different from the deactivated state behavior. A Physical Uplink Control Channel (PUCCH) SCell (an SCell with PUCCH configured) cannot become dormant.

[0066] FIG. 12 shows an exemplary state transition diagram for an NR SCell. At a high level, the SCell of a UE can transition between an activated / deactivated state and an activated state based on an explicit command from the network (e.g., MAC CE) or expiration of an activation / deactivation timer. The behavior such as suspension for a deactivated NR SCell is based on the concept of a dormant bandwidth part (BWP). One of the UE's dedicated BWPs configured via RRC signaling can be set as dormant for the SCell. When the active BWP of an activated SCell is the dormant BWP, the UE stops monitoring the PDCCH on the SCell but continues to perform CSI measurements, AGC, and beam management (if so configured). The downlink control information (DCI) on the PDCCH is used to control entry / exit into the dormant BWP for one or more SCell(s) or one or more SCG(s), and is sent to the SpCell of the cell group including the dormant SCell (i.e., to the PCell if the SCell belongs to the MCG, or to the PSCell if the SCell belongs to the SCG). The dormant BWP cannot be set for the SpCell (i.e., the PCell or PSCell) and the PUCCH SCell.

[0067] However, when MR-DC is configured for the UE, the UE cannot fully benefit from energy reduction of behaviors such as the dormant state or suspension, because the PSCell cannot be set to be dormant. Instead, existing solutions can be to release the SCG (for power saving) and add the SCG (when traffic demand requires), as needed. However, the traffic can be bursty, and thus adding and releasing the SCG as needed can involve a significant amount of RRC signaling and inter-node messaging between the MN and the SN. This can result in a significant delay being felt.

[0068] Regarding 3GPP Rel-16, there were some discussions about putting the PSCell into a dormant state, also known as an SCG interruption. Some agreed principles of this solution include the following. · The UE supports network-controlled interruptions of the SCG in RRC_CONNECTED. · Further study (FFS) is needed on UE behavior regarding the interrupted SCG. · The UE supports at most one SCG configuration in Rel16, whether interrupted or not. · In RRC_CONNECTED when adding an SCG, the SCG can be either interrupted or not interrupted by configuration.

[0069] More detailed solutions for Rel-16 have been proposed, but these have various problems. For example, one solution proposed that when it is expected that data traffic will not be sent over the SCG so that the UE retains the SCG configuration but does not use it for power saving purposes, the gNB can instruct the UE to interrupt SCG transmissions. The signaling for interrupting the SCG can be based on DCI / MAC-CE / RRC, but details beyond specific configurations from the gNB to the UE were not discussed. Even so, this solution for SCell may not be applicable to the PSCell associated with different network nodes (e.g., gNB operating as an SN).

[0070] 3GPP discussions on solutions for the Rel-17 MR-DC work item objective of "Support efficient activation / de-activation mechanism for one SCG and SCells" have started in RAN1 WG, RAN2 WG, and RAN3 WG. The concept of "de-activated SCG" to reduce energy consumption when traffic demand is dynamically reduced has been discussed. Figure 13 is an exemplary state transition diagram showing two SCG states (which may be called "states for SCG activation") according to this concept. In Figure 13, these states are labeled as "SCG de-activated state" and "SCG activated state", and are separate from the RRC state. Rather, these SCG states represent whether the SCG energy saving mode is applied or not.

[0071] The current RAN2 assumption is that in the "SCG de-activated state", the UE does not perform PDCCH monitoring of the PSCell to reduce energy consumption. This also means that UL / DL data transmission in the SCG is interrupted in the SCG de-activated state. The activation and de-activation of the SCG are generally controlled by the network (e.g., by the MN via RRC signaling). Moreover, RAN2 has agreed that PSCell mobility is supported while the SCG is de-activated, even though the details are FFS. When an SCG in the "SCG activated state" is configured for the UE, these energy reduction features are not used / applied.

[0072] In 3GPP regarding the Rel-17 work item mentioned above, the following agreements have been reached. · Network-triggered SCG activation is instructed to the UE via the MCG. · Network-triggered SCG de-activation may be instructed to the UE via the MCG. Instruction via the SCG is FFS. · SCG activation can be requested by the MN / SN / UE. Regarding how to accept / reject the FFS procedure. Regarding which signaling is used for FFS. · SCG deactivation can be requested by the MN / SN. Whether the UE can request deactivation. Regarding how to accept / reject the FFS procedure. Regarding which signaling is used for FFS. · An indication of SCG deactivation to the UE via the SCG is not supported. · The UE can indicate to the MN that the UE desires the SCG to be deactivated. Regarding details such as reusing the UE support information (UAI) or existing messages, the information contained, etc. The network can configure whether the UE is allowed to make such an indication.

[0073] The MAC layer in the network includes a dynamic resource scheduler that allocates DL and UL PHY resources. UL scheduling is based on the UE transmitting measurement reports including a scheduling request (SR), and a buffer status report (BSR) and a power headroom report (PHR). Further details regarding NR UL scheduling are given in 3GPP TS38.300 and 38.321.

[0074] The network schedules UL data transmission in the cell by dynamically or semi-statically allocating radio resources to the UE. These radio resources are provided to the UE either via the PDCCH or in a dynamic UL grant in the random access response (RAR), or as a configured (i.e., persistent) UL grant via RRC signaling (optionally with grant activation / deactivation by DCI). The UL grant includes a resource allocation for transmission (e.g., in time / frequency) and other instructions on how to transmit data on the PUSCH.

[0075] The UL BSR (or more simply, BSR) is required for QoS-aware packet scheduling. In NR, the BSR indicates, for each logical channel group (LCG), the amount of data buffered at the UE. As opposed to the SR, the BSR increases the scheduling rate by informing the network of the amount of UL data pending at the UE. Based on the received BSR, the network can then provide a UL grant to accommodate the transmission of all the data in the UE buffer without having to wait for further UE SRs. When the BSR is triggered (e.g., by the arrival of new UL data) and resources are not available to transmit the BSR, the UE can transmit an SR to obtain a UL grant for the BSR. When the UE does not have a valid PUCCH resource to transmit an SR (e.g., due to the expiration of a timing alignment timer), the UE initiates a random access to establish UL synchronization and receive the UL grant required for the BSR.

[0076] In NR, the RRC layer sets the following parameters to control the UE BSR. · periodicBSR-Timer, for each MAC entity configuration in BSR-Config (effectively optional), · retxBSR-Timer, for each MAC entity configuration in BSR-Config (mandatory), · logicalChannelSR-DelayTimerApplied, for each logical channel configuration (optional), · logicalChannelSR-DelayTimer, for each MAC entity configuration in BSR-Config, · logicalChannelSR-Mask, for each logical channel configuration, · logicalChannelGroup, for each logical channel configuration (optional). Each logical channel (LCH) can be assigned to an LCG using a logicalChannelGroup. The maximum number of LCGs is 8. The MAC entity determines the amount of UL data available for a logical channel according to the data volume calculation procedure specified in 3GPP TS38.322 and 38.323.

[0077] Generally, the following conditions can trigger the UE BSR. 1. Data arrives for a logical channel belonging to an LCG, and · the data is not available on any logical channel belonging to another LCG, or · the data is available only for logical channels belonging to a less prioritized LCG case. 2. When the retxBSR-Timer expires and the UE has data available for transmission on any of the logical channels belonging to the LCG. 3. The number of padding bits after a UL grant is allocated is equal to or greater than the size of the buffer status report MAC CE and its sub-header. 4. When the periodicBSR-Timer expires.

[0078] The BSR triggered in Conditions 1-2 is called a regular BSR, the BSR triggered by Condition 3 is called a padding BSR, and the BSR triggered by Condition 4 is called a periodic BSR. The buffer status report is performed by the UE MAC layer using different types of MAC CEs, including: · Short BSR format (fixed size), · Long BSR format (variable size), · Short Truncated BSR format (fixed size), or · Long Truncated BSR format (variable size).

[0079] Figure 14A shows an exemplary MAC CE in short BSR and short truncated BSR formats, and Figure 14B shows an exemplary MAC CE in long BSR and long truncated BSR formats. The BSR format is identified by a MAC subheader with a logical channel identifier (LCID). In NR, LCID 59 indicates a short truncated BSR, LCID 60 indicates a long truncated BSR, LCID 61 indicates a short BSR, and LCID 62 indicates a long BSR. The fields shown in Figures 14A to 14B are defined as follows. · LCG ID: The logical channel group ID field identifies the group of (one or more) logical channels for which the buffer status is reported. The length of the field is 3 bits. · LCG i : In the case of the long BSR format and the preemptive BSR format, the LCG field set to 1 indicates that the buffer size field for logical channel group i is reported, and being set to 0 indicates that the buffer size field for logical channel group i is not reported. In the case of the long truncated BSR format, the LCG field set to 1 indicates that logical channel group i has available data, and being set to 0 indicates that logical channel group i has no available data. i i · Buffer size i: The buffer size field identifies the total amount of data across all logical channels of logical channel group i after the MAC PDU has been created (i.e., after the logical channel prioritization procedure which may result in the value of the buffer size field becoming 0). The amount of data is indicated in bytes. The sizes of the RLC and MAC headers are not considered in the buffer size calculation. The length of this field for the short BSR format and the short truncated BSR format is 5 bits. The length of this field for the long BSR format and the long truncated BSR format is 8 bits.

[0080] Whenever a new transmission is performed, the MAC entity applies the logical channel prioritization (LCP) procedure to determine which LCH data (and how much data) should be multiplexed in this new transmission. In principle, the MAC entity prioritizes the logical channels according to the LCP and the priority bit rate. The MAC entity prioritizes logical channels with unsatisfied priority bit rate over those with satisfied priority bit rate. Within each of these two groups, the prioritization is based on the logical channel priority. This mechanism is achieved via parameter Bj and is described in more detail in 3GPP TS38.321 (v16.5.0) section 5.4.3.1.

[0081] The procedure for UE BSR reporting is further specified in Section 5.4.5 of 3GPP TS38.321 (v16.2.0). Further, UE BSR reporting is configured via RRC using the BSR-Config IE. In particular, BSR-Config is contained within the MAC-CellGroupConfig IE, which is contained within the CellGroupConfig IE. The CellGroupConfig IE is used to configure the master cell group (MCG) or the secondary cell group (SCG). A cell group consists of one MAC entity, a set of logical channels with associated RLC entities, a primary cell (SpCell), and one or more secondary cells (SCells). The MAC-CellGroupConfig IE is used to configure the MAC parameters for the cell group, including DRX. Figures 15A - 15C show the ASN.1 data structures for exemplary CellGroupConfig, MAC-CellGroupConfig, and BSR-Config IEs, respectively.

[0082] The value of the buffer size field reported for an LCG in the BSR is determined by adding the results of the data volume calculations for each LCH of the LCG. Further, the MAC entity performs the following actions when various reconfigurations of the MAC entity are requested by the upper layer (i.e., by an RRCReconfiguration message containing the mac-CellGroupConfig IE). · When adding an SCell, initialize the corresponding HARQ entity. · When deleting an SCell, delete the corresponding HARQ entity. · When a timer is (re)started, apply a new value for the timer. · When a counter is initialized, apply a new maximum parameter value. · For other parameters, immediately apply the settings received from the upper layer.

[0083] This is used to reset new parameters (e.g., timers) and add SCell.

[0084] Furthermore, when the reset of the MAC entity is requested by the upper layer, the MAC entity performs the following actions. · Initialize Bj for each logical channel to 0. · If sidelink resource allocation mode 1 is configured by RRC, initialize SBj for each logical channel to 0. · Stop all timers (if running). · Consider all timeAlignmentTimer as expired and perform the corresponding actions in Section 5.2. · Set NDI for all uplink HARQ processes to value 0. · Set NDI for all HARQ process IDs to value 0 for monitoring PDCCH in sidelink resource allocation mode 1. · Stop the ongoing random access procedure if any. · Discard the explicitly signaled contention-free random access resources for 4-step RA type and 2-step RA type if any. · Flush the Msg3 buffer. · Flush the MSGA buffer. · Cancel the triggered scheduling request procedure if any. · Cancel the triggered buffer status report procedure if any. · Cancel the triggered power headroom report procedure if any. · Cancel the triggered consistent LBT obstacle if any. · Cancel the triggered BFR if any. · If any, cancel the triggered sidelink buffer status reporting procedure. · If any, cancel the triggered preemptive buffer status reporting procedure. · If any, cancel the triggered recommended bitrate query procedure. · If any, cancel the triggered configured uplink grant confirmation. · If any, cancel the triggered configured sidelink grant confirmation. · If any, cancel the triggered desired guard symbol query. · Flush the soft buffer for all DL HARQ processes. · For each DL HARQ process, consider the next received transmission for the TB as the first transmission. · If any, release the temporary C-RNTI. · Reset all BFI_COUNTERs. · Reset all LBT_COUNTERs.

[0085] The MAC reset procedure is used to cancel related ongoing procedures and reset all UE internal states and counters. The MAC reset procedure can be applied in various scenarios including, but not limited to, the following. · During handover when the UE resets the MAC entity for the source before creating the MAC entity for the target. · Timer T300 expires. · When the upper layer aborts the RRC connection establishment procedure while the UE has not yet entered RRC_CONNECTED. · The SCG is released. · Timer T304 expires (reset failure with synchronization). · When entering RRC_IDLE, and · MCG or SCG failure.

[0086] Generally, existing MAC reset procedures give a "clean slate" to a MAC entity, for example, during handover, to set up another MAC entity for a target. In contrast, MAC reconfiguration applies new parameters from the network to the MAC entity, which continues to operate. However, neither procedure is suitable for the SCG in the deactivated state. The general understanding in 3GPP is that UL / DL data transmission in the SCG is interrupted when the SCG is in the deactivated state. However, there has been no discussion on how UE UP processes and procedures, including the processes and procedures implemented by the (one or more) UE MAC entities, are affected by the SCG deactivated state.

[0087] On the one hand, some MAC entity procedures should be stopped / canceled so that the UE can reduce SCG-related energy consumption. On the other hand, some other MAC entity procedures should not be stopped / canceled so that the UE can quickly reactivate the SCG when needed. Furthermore, the UE actions when reactivating the SCG are unclear. Because the MAC reset / reconfiguration actions are applied only once, it is unclear whether those actions are applied when the SCG is deactivated or when the SCG is reactivated later.

[0088] In some scenarios, in the SCG deactivated state, the UE uses the buffer status reporting function in the MAC entity on the SCG side so that the uplink data arrival on the SCG side can trigger a request for SCG reactivation. However, the BSR mechanism defined in the MAC specification does not function in the SCG deactivated state because the MAC entity is not activated and the necessary recovery mechanism for BSR is not provided (for example, the relevant timer is not running). For example, if the BSR procedure is cancelled (i.e., no BSR is sent) when receiving an SCG deactivation command, the UE does not trigger another BSR even if there is more data coming in the same LCH.

[0089] In another example, if the MAC entity is reset only when the MAC entity resumes, some ongoing procedures during a MAC entity interruption (such as SR due to BFR, consistent LBT failure, etc.) will trigger unnecessary SR and random access to indicate the need for SCG reactivation. In another example, if the MAC entity is reset only when the MAC entity is interrupted, some MAC parameters are not reset to the correct state or value (for example, Bj value for logical channels and periodic PHR).

[0090] Therefore, embodiments of the present disclosure provide new, flexible, and efficient techniques whereby an ongoing MAC procedure (i.e., when the MAC entity is in the normal operating state) is divided into a first part, a second part, and a third part. When the MAC entity is interrupted, the procedures in the first part are reset. When the MAC entity resumes, the procedures in the third part are reset. Further, the procedures in the second part remain active (e.g., continue to proceed) during the period between the interruption and the resume.

[0091] In summary, when the UE's MAC entity is interrupted, the UE cancels most of the ongoing MAC procedures, except that the following ongoing procedures are not cancelled and / or remain ongoing. · Buffer Status Report (BSR) procedure, · Scheduling Request (SR) procedure triggered by the BSR, i.e., for data volume reporting, and · Random access procedure by transmitting a pending BSR. When the UE's MAC entity is interrupted, the UE performs one of the following. · Monitor data traffic arrival with a BSR mechanism, consider logicalChannelSR-DelayTimer to have a value of 0, and / or consider logicalChannelSR-DelayTimerApplied to be false, · Enable BSR triggering based on the data volume of some logical channels set by the RRC, such BSR triggering being effective only when the MAC entity is interrupted, or · Trigger SR based on the data volume of some logical channels set by the RRC. When the UE's MAC entity resumes, the UE performs one or more of the following operations. · Reset the priority parameter Bj for each logical channel to 0, · Consider that all logical channels belonging to the LCG do not contain available UL data immediately before the MAC entity resumes, · Resume the type-1 UL configured grant (CG) from the network, · Trigger the PHR, and · Start a random process on the PCell.

[0092] Embodiments can provide various benefits, advantages, and / or solutions to the problems described herein. For example, embodiments can facilitate the interruption and resumption of MAC entities to support SCG deactivation and reactivation, and the corresponding reduction of UE energy consumption, such as by enabling the UE to trigger BSR procedures and / or data volume reports in a fast and reliable manner. In this way, the network can be quickly informed about the UE's need for reactivation of a deactivated SCG (e.g., due to UL traffic arrival), which can reduce and / or minimize the transmission latency of UL data.

[0093] In the following description, the terms "interrupted SCG", "deactivated SCG", "inactive SCG", and "SCG in reduced energy mode" are used interchangeably. However, from the UE perspective, "SCG in reduced energy mode" means that the UE is operating in reduced energy mode with respect to the SCG. Similarly, the terms "resumed SCG", "activated SCG", "active SCG", "SCG in normal energy mode", "normal SCG operation", and "legacy SCG operation" are used interchangeably. From the UE perspective, "SCG in normal energy mode" means that the UE is operating in normal (i.e., non-reduced) energy mode with respect to the SCG. Examples of operations are UE signal reception / transmission procedures, such as RRM measurements, signal reception, signal transmission, measurement configuration, measurement reporting, evaluation of triggered event measurement reports, etc.

[0094] In the following, embodiments are described with respect to an SCG interrupted for a UE with DC configured. However, similar principles can apply to an MCG interrupted for a UE with DC configured.

[0095] In the following, the terms "buffer status report" and "BSR" refer to an indication from the UE to the network regarding the available UL data volume at the UE. This includes the BSR transmitted via MAC CE based on UL grants received from the network. This also includes cases where the UE has to obtain a UL grant for the transmission of a BSR by transmitting an SR on an active PUCCH resource or by initiating a random access procedure without an active PUCCH resource.

[0096] In the following, the terms "buffer status report" and "BSR" are generally used to encompass all types of BSRs, including short BSR, short truncated BSR, long BSR, and long truncated BSR. For example, when a MAC PDU containing a BSR is created in the SCG MAC, if two or more LCGs have UL data available for transmission, the UE can transmit a long BSR for all LCGs having available UL data. Otherwise, if only one LCG has available UL data, the UE can transmit a short BSR reporting the available UL data volume for that LCG. Further selection of regular format or truncated format can also be implemented.

[0097] Generally, there is a single MAC entity for the SCG. When the SCG is deactivated, the associated MAC entity is interrupted (alternatively, it may be called deactivated) until the SCG is reactivated, and when the SCG is reactivated, the associated MAC entity is resumed (alternatively, it may be called reactivated).

[0098] The following description refers to the interruption and resumption of the SCG MAC entity. MAC interruption / resumption is also used in cases other than a deactivated SCG and may include, but is not limited to, the following. · During "make before break handover", the MCG MAC entity is interrupted (not reset) and then resumed after the UE is associated with the target PCell. · In the case of multiple RAT multiple connectivity (MR-MC), one or more SCGs can be deactivated, and thus their respective MAC entities can be interrupted and resumed later.

[0099] The following describes various operations performed by the MAC entity (hosted by the UE) when interrupted or resumed. The order in which these operations are described does not necessarily correspond to the order in which they are performed, unless otherwise specified or implicitly required by the surrounding context. In other words, these operations can be performed in various orders.

[0100] Figure 16 shows an overview of the operations performed by the UE when the MAC entity is interrupted. These operations are described in more detail below.

[0101] In some embodiments, when the MAC entity is interrupted, the UE sets the new data indicator (NDI) for all UL HARQ processes to a value of 0. This ensures that the UE and the network are synchronized with respect to the NDI value used to indicate whether a UL grant is a new transmission or a retransmission after the MAC entity is resumed. For example, an incorrect NDI value can result in the UE requiring a retransmission while the network intends to schedule an initial transmission. In an alternative form, the UE sets the NDI for all uplink HARQ processes to 0 when the MAC entity is resumed.

[0102] In some embodiments, when the MAC entity is interrupted, the UE cancels any of the following procedures that are triggered (i.e., in progress). · PHR, · Consistent LBT failure recovery, · Beam failure recovery (BFR), · Preemptive BSR, · Recommended bitrate query, · UL CG confirmation, · Sidelink (SL) CG confirmation, and · Desired guard symbol (DSG) query.

[0103] In some embodiments, upon interruption of the MAC entity, the UE flushes the soft buffer for the DL HARQ process and considers the next received transmission for the TB as the first transmission. This ensures that after the MAC entity resumes, the UE and the network are coordinated regarding whether to schedule an initial transmission or a retransmission for the DL HARQ process. In an alternative form, the UE flushes the soft buffer for each DL HARQ process when the MAC entity resumes.

[0104] In some embodiments, upon interruption of the MAC entity, the UE performs the following operations. · Release the temporary C-RNTI, · Reset all BFI_COUNTERs, · Reset all LBT_COUNTERs, and · Reset all SR_COUNTERs.

[0105] In some embodiments, upon interruption of the MAC entity, the UE performs the following operations. · Stop any ongoing random access (RA) procedure, · Flush the Msg3 buffer, · Flush the MSGA buffer, and · Cancel any triggered SA procedure.

[0106] In the deformed state, the UE performs the following operations when the MAC entity is interrupted, except when the ongoing RA procedure is caused by a pending BSR. · Stop the ongoing RA procedure, · Flash the Msg3 buffer, · Flash the MSGA buffer.

[0107] The RA procedure can be triggered, for example, by beam failure recovery or the lack of available PUCCH resources for transmitting SR triggered by LBT failure MAC CE. If the RA procedure is triggered by those events, it may not make sense for the RA procedure to continue operating because the network may not be able to recover anything after receiving this indication and may not know the reason for the UE's RA. On the other hand, if the RA procedure is triggered by a pending BSR, the network should know this as soon as possible. These procedures can also be triggered later in the SCG deactivation state, but this can cause unacceptable delays.

[0108] In another deformed state, when the MAC entity is interrupted, the UE cancels the triggered SR procedure, except for the SR triggered by a BSR triggered by a logical channel. For example, the UE can cancel the SR procedure triggered by SCell BFR or consistent LBT failure recovery. It may not make sense to maintain the SR procedures for these failure recoveries because the network may not be able to recover anything after receiving this indication. On the other hand, if the SR procedure is triggered by a pending BSR, the network should know this as soon as possible. These procedures can also be triggered later in the SCG deactivation state, but this can cause unacceptable delays.

[0109] In some embodiments, when the MAC entity is interrupted, the UE maintains (or continues) the ongoing BSR procedure. This is in contrast to the MAC entity reset procedure where the triggered BSR procedure is cancelled.

[0110] Generally, a BSR is triggered when the UE has data to transmit but does not have a suitable UL grant to do so. However, there can be a race condition where the network has not yet noticed that the UE has data to transmit when the network sent an SCG deactivation command very recently. For example, the network may deactivate the SCG almost simultaneously with the arrival of data for transmission in the SCG at the UE buffer. By maintaining the BSR procedure upon interruption of the MAC entity (i.e., due to SCG deactivation), the UE can indicate the need for SCG activation as soon as possible. If the BSR procedure is cancelled upon receiving an SCG deactivation command such that the BSR is not sent, there is a risk that the BSR procedure will never be triggered again when more data arrives on the LCH that triggered the BSR procedure. This can occur under the existing BFR procedure described above. Maintaining the ongoing BSR procedure upon interruption can avoid this problem.

[0111] The race condition described above is due to the fact that the UE cannot reject an SCG deactivation command from the network. In a variant, approximately when a BSR report is triggered by arriving UL data and the UE receives an SCG deactivation command from the network, the UE can reject the SCG deactivation command. This also avoids the race condition.

[0112] In some embodiments, upon interruption of the MAC entity, the UE stops all running timers and / or considers all running timers as expired, except as specified below for certain embodiments. · The retxBSR-Timer continues to run so that the UE can trigger the only type that can trigger a regular BSR, scheduling request / random access thereafter. · At least the timeAlignmentTimer related to the PCell timing advance group (PTAG) continues to run so that the UE can transmit an SR on the PSCell if this timer has not expired. In other words, the UE either considers only the timeAlignmentTimer related to the STAG as expired or considers none of the timeAlignmentTimers as expired.

[0113] In some embodiments, upon interruption of the MAC entity, the UE performs the following operations on the cell having an unexpired related timeAlignmentTimer. · Clear the configured DL allocation and UL CG, and · Clear the PUSCH resources for semi-persistent CSI reporting.

[0114] In a variant, upon interruption of the MAC entity, the UE then interrupts only the type-1 UL CG in the cell having an unexpired related timeAlignmentTimer.

[0115] In some embodiments, upon interruption of the MAC entity, the UE notifies the RRC layer to release the PUCCH resources for all serving cells for which the timeAlignmentTimer has not expired, except for the PUCCH resources for SR. In a variant, the UE notifies the RRC layer to release the PUCCH resources for all such serving cells, except for the PSCell. In this way, the UE can maintain the PUCCH resources on the PSCell, which eliminates the need for the network to monitor other serving cells for UE SR transmissions.

[0116] Next, the operations performed by the UE while the MAC entity is interrupted are described in more detail. The embodiments are described as first, second, and third alternatives, but these numbers do not indicate a particular preference among the three alternatives.

[0117] Next, the first alternative is described. In some embodiments, while the MAC entity is interrupted, the UE can trigger only the BSR procedure. This procedure will then trigger the SR if there is no UL-SCH in the SCG MAC entity. If there is no valid PUCCH resource configured for the pending SR, the RA procedure on the SpCell is triggered.

[0118] In a variant, while the MAC entity is interrupted, the regular BSR can be triggered in the MAC entity for which it has been deactivated, and regardless of how the parameters of the logicalChannelSR-DelayTimer and logicalChannelSR-DelayTimerApplied were previously set by the RRC, the logicalChannelSR-DelayTimer is set to a value of 0 or the logicalChannelSR-DelayTimerApplied is set to "false". In this way, there is no delay for the UE to trigger the SR while the SCG is in the deactivated state.

[0119] Next, a second alternative form is described. In some embodiments, while the MAC entity is interrupted, the regular BSR may be triggered only if the data volume of a particular LCH is non-zero. This triggering mechanism is applicable only when the MAC entity is in the interrupt mode. The data volume is calculated at the PDCP layer as described in 3GPP TS38.323 (v16.2.0) section 5.6.

[0120] As an example, only the data volume for LCHs other than split secondary RLC entities is considered to trigger the BSR. For those split secondary RLC entities, they only need to be activated if the total amount of PDCP data volume and RLC data volume pending for initial transmission is greater than ul-DataSplitThreshold, but the same data volume can also be indicated to the MCG MAC entity, and thus there is no need to trigger a data volume report for these RLC entities.

[0121] As another example, only the data volume for LCHs belonging to an LCG is considered to trigger the BSR. The field logicalChannelGroup is an optional field in the logical channel configuration, and thus logical channels not belonging to a logical channel group are assumed to have non-delayed critical data that does not require triggering a data volume report when the SCG is deactivated.

[0122] As another example, specific LCHs that can trigger a data volume report when the SCG is deactivated may be RRC-configured by the network. Generally, these configured LCHs must have more stringent latency requirements than other LCHs not configured in this way.

[0123] As another example, only LCHs other than LCH UL-CCCH can trigger a data volume report when the SCG is deactivated.

[0124] Next, a third alternative form is described. In some embodiments, while the MAC entity is interrupted, the UE cannot trigger a procedure except to monitor the data volume of some specific LCH(s). If the monitored data volume is non-zero, the UE triggers an SR, provided that there is no UL-SCH resource. In a variant, the SR is triggered only when the SR has not been triggered previously, i.e., only a single one of these SRs is triggered at the MAC entity.

[0125] Rather than being related to LCH, this SR may be related to a separate SR configuration in the RRC IE MAC-CellGroupConfig, such as schedulingRequestId. The following shows an exemplary ASN.1 data structure for the MAC-CellGroupConfig IE with this field added. ***Start of exemplary ASN.1 data structure*** MAC-CellGroupConfig::=SEQUENCE{ [...] schedulingRequestID-PCellActivate SchedulingRequestId OPTIONAL,--Need R } ***End of exemplary ASN.1 data structure***

[0126] When this SR is triggered, the SR is pending. The pending SR is cancelled and (when operating) the corresponding sr-ProhibitTimer is stopped when any of the following is true. · The UL-SCH source is assigned by the network in this MAC entity, for example, by detecting the correct PDCCH in the PSCell including the UL grant. · The MAC entity is resumed, for example, to activate the SCG, receive an RRC message from the MCG, and / or · The MAC entity does not have a valid PUCCH resource configured for the pending SR, in which case the RA procedure is triggered.

[0127] In some embodiments, a set of PUCCH resources for transmitting SR on the BWP is configured for the UE, and this set of PUCCH resources is always considered valid even when the SCG is deactivated.

[0128] The data volume is calculated at the PDCP layer as further described in 3GPP TS38.323 (v16.2.0) section 5.6. In one variant, only data for LCHs other than the split secondary RLC entity can trigger a data volume report. In another variant, only LCHs belonging to the LCG can trigger a data volume report. In another variant, the LCH that can trigger a data volume report for the deactivated SCG is configured by the network (e.g., via RRC). In another variant, only LCHs other than the LCH UL-CCCH are considered.

[0129] In a variant of the third alternative, when interrupted, the MAC entity stops all ongoing procedures and is reset according to the current procedure. While the MAC entity is interrupted, the UE monitors the data volume and triggers an SR according to any of the techniques described above. When the MAC entity is resumed, the MAC entity is reset again according to the current procedure.

[0130] Figure 17 shows an overview of the operations performed by the UE when resuming the MAC entity. These operations will be described in more detail below.

[0131] In various embodiments, the MAC entity is considered to be resumed when any of the following events occur, either individually or in combination. · Triggering the BSR procedure in the SCG, such as by sending a BSR. · Sending a confirmation response to a network command for activating the SCG. · Starting the SR procedure in the SCG, such as by sending an SR, and / or · Starting the RA procedure in the SCG, such as by sending an RA message (e.g., msg1).

[0132] In some embodiments, when the MAC entity is resumed, the UE resets the prioritization parameter Bj for each logical channel of the resumed MAC entity to 0 (e.g., the initial value). If not set to 0 upon resumption, the Bj calculation would have to consider the last time Bj was updated, which could be quite some time before the SCG was deactivated, and thus may not be accurate or useful. 3GPP TS38.321 (v16.5.0) section 5.4.3.1 obliges the UE to increment Bj by (PBR × T) before any instance of the LCP procedure, where T is the time elapsed since Bj was last incremented. In a variant, the UE also resets the corresponding sidelink SBj for each logical channel to 0 when sidelink resource allocation mode 1 is RRC-configured.

[0133] In some embodiments, when the SCG is reactivated, if the UE resumes the MAC entity, it considers that none of the logical channels belonging to the LCG contain available UL data. This ensures that the legacy BSR procedure can be resumed.

[0134] In some embodiments, when the MAC entity is resumed, the UE starts the RA procedure on the PSCell.

[0135] In some embodiments, when the MAC entity is resumed, the UE can re-initialize the interrupted type-1 UL CGs according to their stored settings for cells with an associated timeAlignmentTimer that is still operating (i.e., neither expired nor stopped). These type-1 UL CGs can be re-initialized to start in each respective symbol according to the rules in 3GPP TS38.321 section 5.8.2.2.

[0136] In some embodiments, when the MAC entity is resumed, the UE starts the phr-PeriodicTimer if 1) the MAC entity has UL resources allocated for a new transmission and 2) the UL resources are the first UL resources allocated for a new transmission. Otherwise, the network will not obtain the PHR according to what is set by the phr-PeriodicTimer since this periodic timer has been stopped. In a variant, the PHR is triggered when the MAC entity is resumed (i.e., at least when the PSCell is resumed).

[0137] FIG. 18 shows a high-level diagram of UE operation at interruption, during interruption, and at resume in the MAC entity for the first alternative described above, in particular where the UE can trigger the BSR procedure during interruption of the MAC entity.

[0138] FIG. 19 shows, in particular, another high-level diagram of UE operations at the time of, during, and after resumption of an interruption in a MAC entity, for the third alternative form described above, which can trigger SR during an interruption of the MAC entity based on the UE monitoring the data volume of one or more specific LCHs.

[0139] The embodiments described above can be further illustrated with respect to FIG. 20 (which has parts A - B), which shows a flowchart of an exemplary method (e.g., procedure) for a UE configured to communicate with a radio network via an MCG and an SCG according to various embodiments of the present disclosure. The exemplary method can be implemented by a UE (e.g., a wireless device, an IoT device, a modem, etc., or components thereof) as described elsewhere in this specification. FIG. 20 shows specific blocks in a specific order, but the operations of the method can be performed in an order different from that shown, combined into blocks having functions different from those shown, and / or divided. Optional blocks or operations are indicated by dashed lines.

[0140] The exemplary method can include the operation of block 2010, where the UE, when deactivating one of a plurality of cell groups, interrupts the MAC entity associated with the deactivated cell group and can perform one or more first operations on the MAC entity when the MAC entity is interrupted. The exemplary method can also include the operation of block 2020, where the UE can perform one or more second operations related to reporting UL data available for transmission via the deactivated cell group while the MAC entity is interrupted. The exemplary method can also include the operation of block 2030, where the UE, when reactivating the deactivated cell group, performs one or more third operations on the MAC entity and can resume the MAC entity based on the one or more third operations.

[0141] For example, the plurality of cell groups includes a MCG and an SCG, and the SCG is a cell group that is deactivated and reactivated.

[0142] In some embodiments, performing a first operation on a MAC entity upon interruption in block 2010 includes the operation of sub-block 2011, and the UE can cancel one or more of the following MAC entity procedures that were in progress. · Random Access (RA), · Scheduling Request (SR), · Power Headroom Report (PHR), · Consistent Listen Before Talk (LBT) failure recovery, · Beam Failure Recovery (BFR), · Preemptive Buffer Status Report (BSR), · Recommended Bitrate Query, · Uplink (UL) Set Grant (CG) confirmation, · Sidelink (SL) CG confirmation, and · Desired Guard Symbol (DSG) Query.

[0143] In some of these embodiments, · An in-progress RA procedure not caused by a BSR pending for transmission is cancelled, but an in-progress RA procedure caused by a BSR pending for transmission is not cancelled, and · An in-progress SR procedure not caused by a BSR pending for transmission is cancelled, but an in-progress SR procedure caused by a BSR pending for transmission is not cancelled, One or more of which are applied.

[0144] In some embodiments, at the time of interruption in block 2010, one or more first operations performed on the MAC entity include the operations of sub-block 2012, and the UE can maintain (e.g., continue to operate) the BSR procedure for the LCH of the MAC entity that was in progress at the time of interruption of the MAC entity.

[0145] In some embodiments, at the time of interruption in block 2010, one or more first operations performed on the MAC entity are indicated by the corresponding sub-block numbers in parentheses, · (2013) setting the new data indicator (NDI) for the ongoing UL hybrid automatic repeat request (HARQ) process to a value of 0, and · (2014) flushing the soft buffer for the ongoing DL HARQ process, and · (2015) resetting one or more active counters, and · (2016) stopping or considering as expiring one or more running timers, and · (2017) interrupting one or more UL resource grants, and · (2018) releasing one or more PUCCH resources, and · (2019) releasing one or more temporary identifiers allocated by the radio network include one or more of these.

[0146] In some of these embodiments, one or more running timers that are stopped or considered as expiring are, at the time of interruption, · a first timer (e.g., retxBSR-Timer) that triggers a regular BSR, and · a second timer (e.g., timeAlignmentTimer) that triggers an SR on the primary cell (e.g., PSCell) of a deactivated cell group At least one of which includes all the operating timers except for continuing to operate.

[0147] In some of these embodiments, the interrupted UL resource grant includes only type-1 UL CG for all cells having an associated timer that has not expired. In some of these embodiments, the released PUCCH resource includes the PUCCH resource for all cells having an associated timer that has not expired, excluding the PUCCH resource for transmitting SR.

[0148] In some embodiments, one or more second operations performed in block 2020 while the MAC entity is interrupted are indicated by the corresponding sub-block number, · (2021) Starting a BSR procedure for reporting UL data available for transmission via a deactivated SCG, · (2022) Starting an SR procedure when the PUSCH resource is not available for transmitting a BSR, · (2025) Starting a RA procedure when the PUCCH resource is not available for transmitting an SR including one or more of.

[0149] In some of these embodiments, the SR procedure is started with substantially zero delay in sub-block 2022 after determining that the PUSCH resource is not available for transmitting a BSR. In other embodiments, starting the BSR procedure in sub-block 2021 is based on the availability of UL data for transmission in a subset of all logical channels (LCH) of the MAC entity. In some of these embodiments, the subset of LCHs is · Only LCHs not associated with split secondary RLC entities, · Only LCHs belonging to a logical channel group (LCG), · Only the LCHs that carry delay-sensitive UL data, and · Specific LCHs indicated by the radio network via RRC signaling include one or more of them.

[0150] In other embodiments, one or more second operations performed in block 2020 while the MAC entity is interrupted are indicated by the corresponding sub-block numbers, · (2023) Monitoring the availability of UL data on one or more LCHs of the MAC entity, and · (2024) Starting an SR procedure based on detecting the availability of UL data on at least one of the monitored LCHs, and · (2025) Starting a RA procedure when the PUCCH resource is not available for transmitting an SR include one or more of them.

[0151] In some of these embodiments, starting the SR procedure in sub-block 2024 may be · While the MAC entity is interrupted, no other SR procedure has been started, or · The UL PUSCH resource is not available for transmitting a BSR, and may be further based on one or more of them.

[0152] In some of these embodiments, the monitored LCH (e.g., in sub-block 2023) is the following subset of all the LCHs of the MAC entity, i.e., · Only the LCHs not associated with split secondary RLC entities, · Only the LCHs belonging to an LCG, · Only the LCHs that carry delay-sensitive UL data, and · Specific LCHs indicated by the radio network via RRC signaling include one of them.

[0153] In some embodiments, when re - activating a de - activated cell group, one or more third operations performed at block 2030 are those indicated by the corresponding sub - block numbers, · (2031) Starting an RA procedure on the primary cell (e.g., PSCell) of the re - activated cell group; · (2032) Resuming one or more interrupted UL resource grants; · (2033) Starting a timer for periodic PHR; · (2034) Resetting each prioritization parameter (e.g., Bj) associated with a plurality of LCHs of the MAC entity to a predetermined initial value; · (2035) Considering each LCH belonging to the LCG as having zero UL data available for transmission including one or more of the above.

[0154] In some embodiments, resuming the MAC entity based on one or more third operations at block 2030 may include the following operations (e.g., when the MAC entity is considered to be resumed at that time), namely, · (2036) Starting or resuming a BSR procedure for a plurality of LCHs of the MAC entity based on the fact that the prioritization parameters associated with the plurality of LCHs (described, for example, in block 2034) are reset to a predetermined initial value; · (2037) Sending a confirmation response to a cell group activation command from the radio network; · (2038) Starting an SR procedure in the re - activated cell group; · (2039) Starting an RA procedure in the re - activated cell group and may include one or more of the above.

[0155] In some of these embodiments, the predetermined initial value at which the prioritization parameter is reset is 0.

[0156] Although various embodiments have been described herein above with respect to a method, apparatus, device, computer-readable medium, and receiver, those skilled in the art will readily understand that such a method can be implemented by various combinations of hardware and software in various systems, communication devices, computing devices, control devices, apparatuses, non-transitory computer-readable media, and the like.

[0157] FIG. 21 shows an example of a communication system 2100 according to some embodiments. In this example, the communication system 2100 includes a communication network 2102 that includes an access network 2104, such as a radio access network (RAN), and a core network 2106 that includes one or more core network nodes 2108. The access network 2104 includes one or more access network nodes, such as network nodes 2110a and 2110b (one or more of which may generally be referred to as network nodes 2110), or any other similar 3GPP access node or non-3GPP access point. The network node 2110 facilitates direct or indirect connection of the user equipment (UE), such as by connecting the UEs 2112a, 2112b, 2112c, and 2112d (one or more of which may generally be referred to as UEs 2112) to the core network 2106 over one or more radio connections.

[0158] Exemplary wireless communication over a wireless connection involves transmitting and / or receiving wireless signals using electromagnetic waves, radio waves, infrared waves, and / or other types of signals that are suitable for transmitting information without using wires, cables, or other material conductors. Moreover, in different embodiments, the communication system 2100 can include any number of wired or wireless networks, network nodes, UEs, and / or any other components or systems that can facilitate or participate in the communication of data and / or signals, whether via a wired connection or a wireless connection. The communication system 2100 can include and / or interface with any type of communication, telecommunication, data, cellular, wireless network, and / or other similar types of systems.

[0159] UE 2112 can be any of a variety of communication devices, including a wireless device configured, set, and / or operable to communicate wirelessly with network node 2110 and other communication devices. Similarly, network node 2110 can communicate directly or indirectly with UE 2112 and / or with other network nodes or devices in communication network 2102 to enable and / or provide network access, such as wireless network access, and / or to perform other functions, such as administration in communication network 2102, and is configured, set, and / or operable to do so.

[0160] In the illustrated example, the core network 2106 connects network nodes 2110 to one or more hosts such as host 2116. These connections can be direct or indirect via one or more intermediate networks or devices. In other examples, network nodes can be directly coupled to hosts. The core network 2106 includes one or more core network nodes (e.g., core network node 2108) structured with hardware and software components. The characteristics of these components can be substantially similar to those described with respect to the UE, network nodes, and / or hosts, and thus, those descriptions generally apply to the corresponding components of the core network node 2108. Exemplary core network nodes include one or more functions of a Mobile Switching Center (MSC), a Mobility Management Entity (MME), a Home Subscriber Server (HSS), an Access and Mobility Management Function (AMF), a Session Management Function (SMF), an Authentication Server Function (AUSF), a Subscription Identifier De-concealing Function (SIDF), Unified Data Management (UDM), a Security Edge Protection Proxy (SEPP), a Network Exposure Function (NEF), and / or a User Plane Function (UPF).

[0161] Host 2116 may be under the ownership or control of a service provider other than an operator or provider of access network 2104 and / or communication network 2102, and may be operated by or on behalf of the service provider. Host 2116 may host various applications to provide one or more services. Examples of such applications include data collection services, analytical functions, social media, functions for controlling or in some cases interacting with remote devices, functions for alarm and surveillance centers, or any other such functions implemented by a server, such as extracting and compiling data on various ambient conditions detected by multiple UEs, live and pre-recorded audio / video content.

[0162] Overall, the communication system 2100 of FIG. 21 enables connectivity between UEs, network nodes, and hosts. In that sense, the communication system may be configured to operate according to predefined rules or procedures, including but not limited to specific standards such as the General Packet Radio Service (GPRS), Universal Mobile Telecommunications System (UMTS), Long Term Evolution (LTE), and / or other suitable 2G, 3G, 4G, 5G standards, or any applicable future generation standards (e.g., 6G), wireless local area network (WLAN) standards such as the Institute of Electrical and Electronics Engineers (IEEE) 802.11 standards (WiFi), and / or Worldwide Interoperability for Microwave Access (WiMax), Bluetooth, Z-Wave, Near Field Communication (NFC), ZigBee, LiFi, and / or any other suitable wireless communication standards, such as any low power wide area network (LPWAN) standards like LoRa and Sigfox.

[0163] In some examples, the communication network 2102 is a cellular network implementing 3GPP standardized features. Thus, the communication network 2102 may support network slicing to provide different logical networks to different devices connected to the communication network 2102. For example, the communication network 2102 may provide ultra-reliable low-latency communication (URLLC) services to some UEs while providing enhanced mobile broadband (eMBB) services to other UEs and / or providing massive machine-type communication (mMTC) / massive IoT services to yet additional UEs.

[0164] In some examples, the UE 2112 is configured to send and / or receive information without direct human interaction. For example, the UE may be designed to send information to the access network 2104 at a predetermined schedule when triggered by an internal or external event or in response to a request from the access network 2104. Further, the UE may be configured to operate in single or multi-RAT or multi-standard modes. For example, the UE may operate in any one or a combination of Wi-Fi, NR (New Radio), and LTE, i.e., be configured for multi-radio dual connectivity (MR-DC) such as E-UTRAN (Evolved UMTS Terrestrial Radio Access Network) New Radio - Dual Connectivity (EN-DC).

[0165] In this example, the hub 2114 communicates with the access network 2104 to facilitate indirect communication between one or more UEs (e.g., UEs 2112c and / or 2112d) and a network node (e.g., network node 2110b). In some examples, the hub 2114 can be any of a controller, router, content source and content analysis, or other communication device described herein with respect to the UE. For example, the hub 2114 can be a broadband router that enables access to the core network 2106 for the UE. As another example, the hub 2114 can be a controller that sends commands or instructions to one or more actuators in the UE. The commands or instructions can be received from the UE, the network node 2110, or can be due to executable code, scripts, processes, or other instructions in the hub 2114. As another example, the hub 2114 can be a data collector that serves as temporary storage for UE data and, in some embodiments, can perform analysis or other processing of the data. As another example, the hub 2114 can be a content source. For example, for a UE that is a VR headset, display, loudspeaker, or other media delivery device, the hub 2114 can retrieve VR assets, video, audio, or other media or data related to sensory information via the network node and provide this to the UE either directly after performing local processing and / or after adding additional local content. In yet another example, the hub 2114 acts as a proxy server or orchestrator for the UE, particularly when one or more of the UEs are low energy IoT devices.

[0166] The hub 2114 may have a constant / permanent or intermittent connection to the network node 2110b. The hub 2114 may also enable different communication methods and / or schedules between the hub 2114 and the UEs (e.g., UEs 2112c and / or 2112d), and between the hub 2114 and the core network 2106. In other examples, the hub 2114 is connected to the core network 2106 and / or one or more UEs via a wired connection. Moreover, the hub 2114 may be configured to connect to an M2M service provider on the access network 2104 and / or to another UE on a direct connection. In some scenarios, the UE may establish a wireless connection to the network node 2110 while still being connected via a wired or wireless connection through the hub 2114. In some embodiments, the hub 2114 may be a dedicated hub, i.e., a hub whose main function is to route communications from / to the UEs to / from the network node 2110b. In other embodiments, the hub 2114 may be a non-dedicated hub, i.e., a device that is capable of operating to route communications between the UEs and the network node 2110b, but that is further capable of operating as a communication start and / or end point for some data channels.

[0167] FIG. 22 shows a UE2200 according to some embodiments. As used herein, a UE refers to a device that is capable of wirelessly communicating with a network node and / or another UE and is configured, constructed, and / or operable to do so. Examples of UEs include, but are not limited to, smartphones, mobile phones, cell phones, Voice over Internet Protocol (VoIP) phones, wireless local loop phones, desktop computers, personal digital assistants (PDAs), wireless cameras, gaming consoles or devices, music storage devices, playback appliances, wearable terminal devices, wireless endpoints, mobile stations, tablets, laptop computers, laptop embedded equipment (LEE), laptop-mounted equipment (LME), smart devices, wireless customer premise equipment (CPE), vehicle-mounted or vehicle-embedded / integrated wireless devices, etc. Other examples include any UE identified by the Third Generation Partnership Project (3GPP), including narrowband Internet of Things (NB-IoT) UEs, machine type communication (MTC) UEs, and / or enhanced MTC (eMTC) UEs.

[0168] The UE may support device-to-device (D2D) communication, for example, by implementing 3GPP standards for sidelink communication, dedicated short range communication (DSRC), Vehicle-to-Vehicle (V2V), Vehicle-to-Infrastructure (V2I), or Vehicle-to-Everything (V2X). In other examples, the UE does not necessarily have a user in the sense of a human user who owns and / or operates the associated device. Instead, the UE may represent a device (e.g., a smart sprinkler controller) that is intended for sale to or operation by a human user but may not be associated with a particular human user or may not be initially associated with a particular human user. Alternatively, the UE may represent a device (e.g., a smart power meter) that is not intended for sale to or operation by an end user but may be associated with a user or operated for the benefit of a user.

[0169] UE 2200 includes a processing circuit 2202 operably coupled via a bus 2204 to an input / output interface 2206, a power supply 2208, a memory 2210, a communication interface 2212, and / or any other component, or any combination thereof. Some UEs may utilize all or a subset of the components shown in FIG. 22. The level of integration between components may vary from UE to UE. Further, some UEs may include multiple instances of components, such as multiple processors, memories, transceivers, transmitters, receivers, etc.

[0170] The processing circuit 2202 is configured to process instructions and data and may be configured to implement any sequential state machine operable to execute instructions stored in the memory 2210 as a machine-readable computer program. The processing circuit 2202 may be implemented as one or more hardware-implemented state machines (such as in discrete logic, a field programmable gate array (FPGA), an application specific integrated circuit (ASIC), etc.), programmable logic in conjunction with appropriate firmware, a microprocessor or digital signal processor (DSP) in conjunction with appropriate software, one or more stored computer programs, a general purpose processor, or any combination of the above. For example, the processing circuit 2202 may include multiple central processing units (CPUs).

[0171] In this example, the input / output interface 2206 may be configured to provide one or more interfaces to an input device, an output device, or one or more input and / or output devices. Examples of output devices include speakers, sound cards, video cards, displays, monitors, printers, actuators, emitters, smart cards, another output device, or any combination thereof. The input device may enable a user to capture information to the UE 2200. Examples of input devices include touch-sensitive or presence-sensitive displays, cameras (e.g., digital cameras, digital video cameras, webcams, etc.), microphones, sensors, mice, trackballs, directional pads, trackpads, scroll wheels, smart cards, and the like. The presence-sensitive display may include a capacitive or resistive touch sensor for detecting input from a user. The sensor may be, for example, an accelerometer, gyroscope, tilt sensor, force sensor, magnetometer, optical sensor, proximity sensor, biometric sensor, or the like, or any combination thereof. The output device may use the same type of interface port as the input device. For example, a Universal Serial Bus (USB) port may be used to provide the input device and the output device.

[0172] In some embodiments, the power supply 2208 is structured as a battery or battery pack. Other types of power supplies may be used, such as an external power supply (e.g., an electrical outlet), a photovoltaic device, or a battery. The power supply 2208 may further include a power circuit for distributing power from the power supply 2208 itself and / or an external power supply to various parts of the UE 2200 via an input circuit or an interface such as a power cable. Distributing power may be, for example, for charging the power supply 2208. The power circuit may perform any formatting, conversion, or other modification to the power from the power supply 2208 so that it is suitable for each component of the UE 2200 to which the power is supplied.

[0173] The memory 2210 can be set to be a memory, such as a random access memory (RAM), a read-only memory (ROM), a programmable read-only memory (PROM), an erasable programmable read-only memory (EPROM), an electrically erasable programmable read-only memory (EEPROM), a magnetic disk, an optical disk, a hard disk, a removable cartridge, a flash drive, etc., or to include a memory. In one example, the memory 2210 includes one or more application programs 2214, such as an operating system, a web browser application, a widget, a gadget engine, or other applications, and corresponding data 2216. The memory 2210 can store any of a variety of operating systems or combinations of operating systems for use by the UE 2200.

[0174] Memory 2210 can be configured to include several physical drive units, such as a redundant array of independent disks (RAID), flash memory, a USB flash drive, an external hard disk drive, a thumb drive, a pen drive, a key drive, a high density digital versatile disc (HD-DVD) optical disc drive, an internal hard disk drive, a Blu-Ray optical disc drive, a holographic digital data storage (HDDS) optical disc drive, an external mini dual in-line memory module (DIMM), synchronous dynamic random access memory (SDRAM), an external micro DIMM SDRAM, a universal integrated circuit card (UICC) in the form of one or more subscriber identity modules (SIMs) such as a USIM and / or an ISIM, a smart card memory such as an anti-tampering module, other memories, or any combination thereof. The UICC can be, for example, an embedded UICC (eUICC), an integrated UICC (iUICC), or a removable UICC commonly known as a "SIM card". Memory 2210 can enable the UE2200 to access instructions, application programs, etc. stored in a temporary or non-temporary memory medium, offload data, or upload data. A manufactured product, such as a manufactured product using a communication system, can be embodied as or physically embodied in Memory 2210, and Memory 2210 can be a device-readable storage medium or include a device-readable storage medium.

[0175] The processing circuit 2202 may be configured to communicate with an access network or other network using the communication interface 2212. The communication interface 2212 may comprise one or more communication subsystems, may include an antenna 2222, or may be communicatively coupled to the antenna 2222. The communication interface 2212 may include one or more transceivers used for communication, such as by communicating with one or more remote transceivers of another device capable of wireless communication (e.g., another UE or network node in an access network). Each transceiver may include a transmitter 2218 and / or a receiver 2220 suitable for providing network communication (e.g., optical, electrical, frequency allocation, etc.). Moreover, the transmitter 2218 and the receiver 2220 may be coupled to one or more antennas (e.g., antenna 2222), and may share circuit components, software, or firmware, or alternatively, may be implemented separately.

[0176] In the illustrated embodiment, the communication functions of the communication interface 2212 may include cellular communication, Wi-Fi communication, LPWAN communication, data communication, voice communication, multimedia communication, short-range communication such as Bluetooth, near-field communication, location-based communication such as the use of the Global Positioning System (GPS) for determining location, another similar communication function, or any combination thereof. The communication may be implemented according to one or more communication protocols and / or standards, such as IEEE802.11, Code Division Multiple Access (CDMA), Wideband Code Division Multiple Access (WCDMA), GSM, LTE, New Radio (NR), UMTS, WiMax, Ethernet, Transmission Control Protocol / Internet Protocol (TCP / IP), Synchronous Optical Networking (SONET), Asynchronous Transfer Mode (ATM), QUIC, Hypertext Transfer Protocol (HTTP), etc.

[0177] Regardless of the type of sensor, the UE may provide the output of data captured by the UE's sensors to a network node via a wireless connection through the UE's communication interface 2212. The data captured by the UE's sensors may be communicated to the network node via another UE through the wireless connection. The output may be periodic (e.g., once every 15 minutes when reporting the detected temperature), in response to a triggering event (e.g., an alarm is sent when humidity is detected), in response to a request (e.g., a user-initiated request), random (e.g., to even out the load from reports from several sensors), or a continuous stream (e.g., a live video feed of a patient).

[0178] As another example, the UE comprises an actuator, a motor, or a switch related to a communication interface configured to receive a wireless input from a network node via a wireless connection. In response to the received wireless input, the state of the actuator, motor, or switch may change. For example, the UE may comprise a motor that adjusts the control surfaces or rotors of a drone in flight according to the received input, or a robotic arm that performs a medical procedure according to the received input.

[0179] When in the form of an Internet of Things (IoT) device, the UE can be a device for use in one or more application areas, which include, but are not limited to, urban wearable technologies, extended industrial applications, and healthcare. Non-limiting examples of such IoT devices include connected refrigerators or freezers, TVs, connected lighting devices, electricity meters, robotic vacuum cleaners, voice-controlled smart speakers, home security cameras, motion detectors, thermostats, smoke detectors, door / window sensors, flood / humidity sensors, electronic door locks, connected doorbells, air conditioning systems such as heat pumps, autonomous vehicles, surveillance systems, weather monitoring devices, vehicle parking monitoring devices, electric vehicle charging stations, smartwatches, fitness trackers, head-mounted displays for augmented reality (AR) or virtual reality (VR), wearables for tactile augmentation or perception enhancement, water sprinklers, animal or merchandise tracking devices, sensors for monitoring plants or animals, industrial robots, unmanned aerial vehicles (UAVs), and any type of medical device such as a heart rate monitor or a remotely controlled surgical robot, or a device embedded therein. The UE in the form of an IoT device comprises circuitry and / or software according to the intended application of the IoT device, in addition to the other components described with respect to the UE2200 shown in FIG. 22.

[0180] As yet another specific example, in an IoT scenario, a UE may represent a machine or other device that performs monitoring and / or measurements and transmits the results of such monitoring and / or measurements to another UE and / or network node. The UE may in this case be an M2M device, which may be referred to as an MTC device in a 3GPP context. As one specific example, the UE may implement the 3GPP NB-IoT standard. In other scenarios, the UE may represent a vehicle, such as a car, bus, truck, ship, and airplane, or other device capable of monitoring and / or reporting on its operating status, or other functions related to its operation.

[0181] In practice, for any single use case, any number of UEs may be used together. For example, a first UE may be a drone or integrated within a drone and provide drone speed information (obtained through a speed sensor) to a second UE that is a remote controller operating the drone. When the user makes a change from the remote controller, the first UE may adjust the throttle on the drone (e.g., by controlling an actuator) to increase or decrease the speed of the drone. The first and / or second UE may also include two or more of the functions described above. For example, a UE may include a sensor and an actuator and handle the communication of data for both the speed sensor and the actuator.

[0182] FIG. 23 shows a network node 2300 according to some embodiments. As used herein, a network node refers to a device configured, arranged, and / or operable to communicate directly or indirectly with a UE in a communication network and / or with other network nodes or devices. Examples of network nodes include, but are not limited to, access points (APs) (e.g., wireless access points), base stations (BSs) (e.g., radio base stations, Node B, evolved Node B (eNB), and NR Node B (gNB)).

[0183] The base station can be categorized based on the amount of coverage provided by the base station (or, in other words, the transmission power level of the base station), and thus, depending on the amount of coverage provided, may be referred to as a femto base station, a pico base station, a micro base station, or a macro base station. The base station can be a relay node or a relay donor node that controls a relay. The network node can also include one or more (or all) parts of a distributed radio base station, such as a centralized digital unit and / or a remote radio unit (RRU) that may be referred to as a remote radio head (RRH). Such a remote radio unit may or may not be integrated with an antenna as an antenna-integrated radio. Parts of a distributed radio base station may also be referred to as nodes in a distributed antenna system (DAS).

[0184] Other examples of network nodes include multi-transmission point (multi-TRP) 5G access nodes, MSR devices such as multi-standard radio (MSR) BSs, network controllers such as radio network controllers (RNCs) or base station controllers (BSCs), base transceiver stations (BTSs), transmission points, transmission nodes, multi-cell / multicast coordination entities (MCEs), operation and maintenance (O&M) nodes, operation support system (OSS) nodes, self-organizing network (SON) nodes, positioning nodes (e.g., evolved serving mobile location center (E-SMLC)), and / or minimization of drive test (MDT).

[0185] The network node 2300 includes a processing circuit 2302, a memory 2304, a communication interface 2306, and a power supply 2308. The network node 2300 can be assembled from a plurality of physically distinct components (e.g., a Node B component and an RNC component, or a BTS component and a BSC component, etc.), each of which can have its own respective components. In some scenarios where the network node 2300 comprises a plurality of distinct components (e.g., a BTS component and a BSC component), one or more of the distinct components can be shared among several network nodes. For example, a single RNC can control multiple Node Bs. In such scenarios, in some cases, each unique pair of Node B and RNC can be regarded as a single distinct network node. In some embodiments, the network node 2300 can be configured to support a plurality of radio access technologies (RATs). In such embodiments, some components can be replicated (e.g., separate memories 2304 for different RATs), and some components can be reused (e.g., the same antenna 2310 can be shared by different RATs). The network node 2300 can also include a plurality of sets of various illustrated components for different radio technologies integrated into the network node 2300, such as GSM, WCDMA, LTE, NR, WiFi, Zigbee, Z-wave, LoRaWAN, radio frequency identification (RFID), or Bluetooth radio technology. These radio technologies can be integrated into the same or different chips or sets of chips, and other components within the network node 2300.

[0186] The processing circuit 2302 can be a microprocessor, a controller, a microcontroller, a central processing unit, a digital signal processor, an application specific integrated circuit, a field programmable gate array, or any other suitable computing device, resource, a combination of one or more of them, or a combination of hardware, software and / or encoded logic, which is operable to provide the network node 2300 function either alone or in combination with other network node 2300 components such as the memory 2304.

[0187] In some embodiments, the processing circuit 2302 includes a system on chip (SOC). In some embodiments, the processing circuit 2302 includes one or more of a radio frequency (RF) transceiver circuit 2312 and a baseband processing circuit 2314. In some embodiments, the radio frequency (RF) transceiver circuit 2312 and the baseband processing circuit 2314 can be on separate chips (or a set of chips), boards, or units such as a radio unit and a digital unit. In alternative embodiments, some or all of the RF transceiver circuit 2312 and the baseband processing circuit 2314 can be on the same chip or a set of chips, board, or unit.

[0188] Memory 2304 may include, without limitation, persistent storage, solid-state memory, remotely mounted memory, magnetic media, optical media, random access memory (RAM), read-only memory (ROM), mass storage media (e.g., hard disk), removable storage media (e.g., flash drive, compact disc (CD) or digital video disc (DVD)), any form of volatile or non-volatile computer-readable memory, and / or any other volatile or non-volatile, non-transitory device-readable and / or computer-executable memory device that can store information, data, and / or instructions used by processing circuit 2302. Memory 2304 may store any suitable instructions, data or information, including one or more of computer programs, software, logic, rules, code, tables, applications, and / or other instructions that can be executed by processing circuit 2302 and utilized by network node 2300. Memory 2304 may be used to store calculations performed by processing circuit 2302 and / or data received via communication interface 2306. In some embodiments, processing circuit 2302 and memory 2304 are integrated.

[0189] The communication interface 2306 is used in the wired or wireless communication of signaling and / or data between network nodes, access networks, and / or UEs. As shown, the communication interface 2306 comprises (one or more) ports / (one or more) terminals 2316 for sending and receiving data to and from the network, for example, over a wired connection. The communication interface 2306 also includes a radio front-end circuit 2318 that is coupled to the antenna 2310 or, in some embodiments, can be part of the antenna 2310. The radio front-end circuit 2318 comprises a filter 2320 and an amplifier 2322. The radio front-end circuit 2318 can be connected to the antenna 2310 and the processing circuit 2302. The radio front-end circuit can be configured to condition the signals communicated between the antenna 2310 and the processing circuit 2302. The radio front-end circuit 2318 can receive digital data to be transmitted to other network nodes or UEs via a wireless connection. The radio front-end circuit 2318 can convert the digital data into a radio signal having appropriate channel and bandwidth parameters using a combination of the filter 2320 and / or the amplifier 2322. The radio signal can then be transmitted via the antenna 2310. Similarly, when receiving data, the antenna 2310 can collect the radio signal, which is then converted into digital data by the radio front-end circuit 2318. The digital data can be passed to the processing circuit 2302. In other embodiments, the communication interface can comprise different components and / or different combinations of components.

[0190] In some alternative embodiments, the network node 2300 does not include a separate radio front-end circuit 2318. Instead, the processing circuit 2302 includes a radio front-end circuit and is connected to the antenna 2310. Similarly, in some embodiments, all or part of the RF transceiver circuit 2312 is part of the communication interface 2306. In still other embodiments, the communication interface 2306 includes one or more ports or terminals 2316, a radio front-end circuit 2318, and an RF transceiver circuit 2312 as part of a wireless unit (not shown), and the communication interface 2306 communicates with a baseband processing circuit 2314 that is part of a digital unit (not shown).

[0191] The antenna 2310 may include one or more antennas or antenna arrays configured to send and / or receive wireless signals. The antenna 2310 may be coupled to the radio front-end circuit 2318 and may be any type of antenna capable of wirelessly transmitting and receiving data and / or signals. In some embodiments, the antenna 2310 is separate from the network node 2300 and can be connected to the network node 2300 through an interface or port.

[0192] The antenna 2310, the communication interface 2306, and / or the processing circuit 2302 may be configured to perform any of the receiving operations and / or some of the acquisition operations described herein as being performed by a network node. Any information, data, and / or signals may be received from a UE, another network node, and / or any other network device. Similarly, the antenna 2310, the communication interface 2306, and / or the processing circuit 2302 may be configured to perform any of the transmitting operations described herein as being performed by a network node. Any information, data, and / or signals may be transmitted to a UE, another network node, and / or any other network device.

[0193] Power supply 2308 provides power to the various components of network node 2300 in a form suitable for each component (e.g., at the voltage and current levels required for each respective component). The power supply 2308 may further comprise, or be coupled to, a power management circuit for supplying power to the components of network node 2300 for implementing the functions described herein. For example, network node 2300 may be connectable to an external power source (e.g., a power grid, an electrical outlet) via an input circuit or interface such as an electrical cable, whereby the external power source supplies power to the power circuit of power supply 2308. As a further example, power supply 2308 may comprise a power source in the form of a battery or battery pack connected to, or integrated in, the power circuit. The battery may provide backup power in the event of a loss of external power.

[0194] Embodiments of network node 2300 may include additional components other than those shown in FIG. 23 for providing some aspects of the functionality of a network node, including any of the functions described herein and / or any of the functions necessary to support the subject matter described herein. For example, network node 2300 may include user interface devices for enabling the input of information to network node 2300 and for enabling the output of information from network node 2300. This may enable a user to perform diagnostic, maintenance, repair, and other administrative functions for network node 2300.

[0195] FIG. 24 is a block diagram of a host 2400 that can be an embodiment of the host 2116 of FIG. 21 according to various aspects described herein. The host 2400 used herein can be various combinations of hardware and / or software, including a stand-alone server, a blade server, a cloud-implemented server, a distributed server, a virtual machine, a container, or processing resources in a server farm, or can comprise various combinations of hardware and / or software. The host 2400 can provide one or more services to one or more UEs.

[0196] The host 2400 includes a processing circuit 2402 operably coupled to an input / output interface 2406, a network interface 2408, a power supply 2410, and a memory 2412 via a bus 2404. In other embodiments, other components may be included. The features of these components can be substantially similar to those described for the devices in previous figures, such as FIGS. 22 and 23, and thus, those descriptions generally apply to the corresponding components of the host 2400.

[0197] Memory 2412 may include one or more computer programs including one or more host application programs 2414 and data 2416, and the data 2416 may include user data, for example, data generated by the UE for the host 2400, or data generated by the host 2400 for the UE. Embodiments of the host 2400 may utilize only a subset or all of the shown components. The host application program 2414 may be implemented in a container-based architecture and may provide support for video codecs (e.g., Versatile Video Coding (VVC), High Efficiency Video Coding (HEVC), Advanced Video Coding (AVC), MPEG, VP9) and audio codecs (e.g., FLAC, Advanced Audio Coding (AAC), MPEG, G.711), including transcoding for multiple different classes, types, or implementations of the UE (e.g., handsets, desktop computers, wearable display systems, head-up display systems). The host application program 2414 may also provide user authentication and license checking and may periodically report health, route, and content availability to a central node, such as a device in the core network or a device at the edge of the core network. Thus, the host 2400 may select and / or direct different hosts for an over-the-top service for the UE. The host application program 2414 may support various protocols such as the HTTP Live Streaming (HLS) protocol, Real-Time Messaging Protocol (RTMP), Real-Time Streaming Protocol (RTSP), and Dynamic Adaptive Streaming over HTTP (MPEG-DASH).

[0198] FIG. 25 is a block diagram showing a virtualization environment 2500 in which functions implemented by some embodiments can be virtualized. In this context, virtualizing means creating a virtual version of a device or apparatus, which may include virtualizing the hardware platform, memory devices, and networking resources. The virtualization used herein can be applied to any device described herein, or components thereof, and relates to implementations in which at least some of the functions are implemented as one or more virtual components. One or more virtual machines (VMs) hosted by one or more of the hardware nodes, such as a network node, a UE, a core network node, or a hardware computing device operating as a host, implement one or more virtual components that are executed in one or more virtual environments 2500, and one or more of the functions described herein can be implemented as virtual components. Further, in embodiments where the virtual node does not require wireless connectivity (e.g., a core network node or a host), the node can be fully virtualized.

[0199] (Alternatively, sometimes called a software instance, virtual appliance, network function, virtual node, virtual network function, etc.) Application 2502 operates in virtualization environment 2500 to implement some of the features, functions, and / or benefits of some of the embodiments disclosed herein.

[0200] Hardware 2504 includes a processing circuit, a memory that stores software and / or instructions executable by the hardware processing circuit, and / or other hardware devices described herein, such as a network interface, an input / output interface. The software is executed by the processing circuit to instantiate one or more virtualization layers 2506 (also referred to as a hypervisor or virtual machine monitor (VMM)), provide VM2508a and 2508b (one or more of which are generally referred to as VM2508), and / or implement any of the functions, features, and / or benefits described with respect to some of the embodiments described herein. The virtualization layer 2506 may present a virtual operating platform that appears to the VM2508 as networking hardware.

[0201] VM2508 includes virtual processing, virtual memory, virtual networking or interfaces, and virtual storage and can be operated by a corresponding virtualization layer 2506. Different embodiments of instances of the virtual appliance 2502 may be implemented on one or more of the VM2508, and the implementation may be done in different ways. The virtualization of hardware is referred to in some contexts as network function virtualization (NFV). NFV can be used to consolidate many network equipment types onto industry-standard high-volume server hardware, physical switches, and physical storage that may be located within data centers and customer premise equipment.

[0202] In the context of NFV, VM2508 can be a software implementation of a physical machine that runs programs as if those programs were running on a non-physically virtualized machine. Each of the VM2508s, whether it is dedicated hardware for that VM and / or hardware shared with other VMs among the VMs by that VM, forms a separate virtual network element with that part of the hardware 2504 that executes that VM. Further, in the context of NFV, the virtual network function is responsible for handling specific network functions running on one or more VMs2508 on the hardware 2504 and corresponds to the application 2502.

[0203] The hardware 2504 can be implemented in a stand-alone network node with general or specific components. The hardware 2504 can implement some functions via virtualization. Alternatively, the hardware 2504 can be part of a larger class of hardware (such as in the case of a data center or CPE) that is managed via management and orchestration 2510 where multiple hardware nodes cooperate and in particular oversee the lifecycle management of the application 2502. In some embodiments, the hardware 2504 is coupled to one or more radio units each including one or more transmitters and one or more receivers, which can be coupled to one or more antennas. The radio units can communicate directly with other hardware nodes via one or more appropriate network interfaces and can be used in combination with virtual components to provide a virtual node with wireless capabilities such as a wireless access node or a base station. In some embodiments, some signaling can be provided using a control system 2512 that can alternatively be used for communication between the hardware node and the radio unit.

[0204] Figure 26 shows a communication diagram of a host 2602 communicating with a UE 2606 via a network node 2604 over a partial wireless connection, according to some embodiments. Next, exemplary implementations according to various embodiments of a UE (such as UE 2112a of FIG. 21 and / or UE 2200 of FIG. 22), a network node (such as network node 2110a of FIG. 21 and / or network node 2300 of FIG. 23), and a host (such as host 2116 of FIG. 21 and / or host 2400 of FIG. 24) will be described with reference to FIG. 26.

[0205] Similar to host 2400, embodiments of host 2602 include hardware such as a communication interface, a processing circuit, and a memory. Host 2602 also includes software that is stored in or accessible by host 2602 and executable by the processing circuit. The software may include a host application that is operable to provide services to a remote user, such as UE 2606, that connects via an over-the-top (OTT) connection 2650 that extends between UE 2606 and host 2602. When providing services to a remote user, the host application may provide user data transmitted using OTT connection 2650.

[0206] Network node 2604 includes hardware that enables network node 2604 to communicate with host 2602 and UE 2606. Connection 2660 may be direct or may pass through one or more other intermediate networks, such as a core network (similar to core network 2106 of FIG. 21) and / or one or more public, private, or hosted networks. For example, the intermediate network may be a backbone network or the Internet.

[0207] UE2606 includes hardware and software that is stored in or accessible by UE2606 and executable by the UE's processing circuitry. The software can include client applications, such as a web browser or an operator-specific "app" that can be operative to provide services to a human or non-human user via UE2606 with the support of host 2602. At host 2602, the running host application can communicate with the running client application via OTT connection 2650 that terminates at UE2606 and host 2602. When providing services to the user, the client application of the UE can receive request data from the host application of the host and provide user data in response to the request data. OTT connection 2650 can transfer both request data and user data. The client application of the UE can interact with the user to generate the user data that the client application of the UE provides to the host application through OTT connection 2650.

[0208] OTT connection 2650 can extend via connection 2660 between host 2602 and network node 2604 and via wireless connection 2670 between network node 2604 and UE2606 to provide a connection between host 2602 and UE2606. The connection 2660 and wireless connection 2670 through which OTT connection 2650 can be provided are abstractly depicted to show communication between host 2602 and UE2606 through network node 2604 without explicit reference to an intermediary device and the exact routing of messages through these devices.

[0209] As an example of transmitting data via the OTT connection 2650, in step 2608, the host 2602 provides user data, which may be implemented by running a host application. In some embodiments, the user data is related to a specific human user who interacts with the UE 2606. In other embodiments, the user data is related to the UE 2606 that shares data with the host 2602 without explicit human interaction. In step 2610, the host 2602 initiates a transmission to convey the user data to the UE 2606. The host 2602 may initiate the transmission in response to a request sent by the UE 2606. The request may be caused by human interaction with the UE 2606 or by the operation of a client application running on the UE 2606. The transmission may proceed via the network node 2604 in accordance with the teachings of the embodiments described throughout this disclosure. Thus, in step 2612, the network node 2604 transmits the user data conveyed in the transmission initiated by the host 2602 to the UE 2606 in accordance with the teachings of the embodiments described throughout this disclosure. In step 2614, the UE 2606 receives the user data conveyed in the transmission, which may be implemented by a client application running on the UE 2606 related to the host application executed by the host 2602.

[0210] In some examples, UE 2606 executes a client application that provides user data to host 2602. The user data may be provided in response to or in reaction to data received from host 2602. Thus, at step 2616, UE 2606 may provide user data, which may be implemented by executing the client application. When providing the user data, the client application may further consider user input received from the user via the input / output interface of UE 2606. Regardless of the particular manner in which the user data is provided, at step 2618, UE 2606 initiates transmission of the user data to host 2602 via network node 2604. At step 2620, in accordance with the teachings of the embodiments described throughout this disclosure, network node 2604 receives the user data from UE 2606 and initiates transmission of the received user data to host 2602. At step 2622, host 2602 receives the user data carried in the transmission initiated by UE 2606.

[0211] One or more of the various embodiments improve the performance of OTT services provided to UE2606 using an OTT connection 2650 in which the wireless connection 2670 forms the last segment. More precisely, these embodiments support SCG deactivation and reactivation and corresponding reduction of UE energy consumption, for example, by enabling the UE to trigger the BSR procedure and / or data volume reporting in a fast and reliable manner, which can facilitate the interruption and resumption of the MAC entity. In this way, the network can be quickly informed of the UE's need for reactivation of a deactivated SCG (e.g., due to UL traffic arrival), which can reduce and / or minimize the transmission latency of UL data. Both users and providers of OTT services will benefit from these improvements in energy consumption and data latency, which will make these OTT services more beneficial for both types of entities.

[0212] In an exemplary scenario, factory status information can be collected and analyzed by host 2602. As another example, host 2602 can process audio and video data that may be retrieved from a UE for use in creating a map. As another example, host 2602 can collect and analyze real-time data to assist in controlling traffic congestion (e.g., controlling traffic signals). As another example, host 2602 can store surveillance video uploaded by a UE. As another example, host 2602 can store or control access to media content, such as video, audio, VR, or AR, that host 2602 can broadcast, multicast, or unicast to a UE. As another example, host 2602 can be used for energy price setting, remote control of non-time-critical electrical loads to balance power generation needs, location services, presentation services (such as compiling figures from data collected from remote devices), or any other function of collecting, retrieving, storing, analyzing, and / or transmitting data.

[0213] In some examples, a measurement procedure may be provided for the purpose of monitoring data rate, latency, and other factors that one or more embodiments improve. There may further be optional network functions for reconfiguring the OTT connection 2650 between the host 2602 and the UE 2606 in response to variations in the measurement results. The measurement procedure and / or the network function for reconfiguring the OTT connection may be implemented in the software and hardware of the host 2602 and / or the UE 2606. In some embodiments, sensors (not shown) may be deployed in or associated with other devices through which the OTT connection 2650 passes, and the sensors may participate in the measurement procedure by supplying values of the monitored quantities exemplified above, or by supplying values of other physical quantities whose values can be calculated or estimated by software for the monitored quantities. The reconfiguration of the OTT connection 2650 may include message format, retransmission settings, preferred routing, etc., and the reconfiguration does not need to directly change the operation of the network node 2604. Such procedures and functions are known and practiced in the art. In some embodiments, the measurement may involve proprietary UE signaling by the host 2602 to facilitate measurements such as throughput, propagation time, latency, etc. The measurement may be implemented in that software causes messages, particularly empty or "dummy" messages, to be sent using the OTT connection 2650 while monitoring propagation time, errors, etc.

[0214] The foregoing merely illustrates the principles of the disclosure. Various modifications and alterations of the described embodiments will become apparent to those skilled in the art in view of the teachings herein. Accordingly, it should be understood that numerous systems, configurations, and procedures that embody the principles of the disclosure, and thus fall within the spirit and scope of the disclosure, may be devised by those skilled in the art that are not explicitly shown or described herein. As should be understood by those skilled in the art, various embodiments may be used together with each other and in a mutually compatible manner.

[0215] As used herein, the term unit can have its ordinary meaning in the fields of electronics, electrical devices, and / or electronic devices, and can include, for example, electrical and / or electronic circuits, devices, modules, processors, memories, logic solids, and / or individual devices, computer programs or instructions, etc. for performing each task, procedure, calculation, output, and / or display function as described herein.

[0216] Any suitable step, method, feature, function, or benefit disclosed herein can be implemented through one or more functional units or modules of one or more virtual devices. Each virtual device can comprise several of these functional units. These functional units can be implemented via a processing circuit that can include one or more microprocessors or microcontrollers, and other digital hardware that can include, for example, a digital signal processor (DSP), dedicated digital logic, etc. The processing circuit can be configured to execute program code stored in a memory that can include one or several types of memory, such as read-only memory (ROM), random access memory (RAM), cache memory, flash memory devices, optical storage devices, etc. The program code stored in the memory includes program instructions for executing one or more communication and / or data communication protocols, as well as instructions for performing one or more of the techniques described herein. In some implementations, the processing circuit can be used to cause each functional unit to perform the corresponding function according to one or more embodiments of the present disclosure.

[0217] As described herein, a device and / or apparatus may be represented by a semiconductor chip, a chip set, or a (hardware) module comprising such chips or chip sets, but this does not exclude the possibility that the functionality of the device or apparatus may be implemented as a software module, such as a computer program or a computer program product, comprising a portion of executable software code for execution on or running on a processor, instead of being hardware-implemented. Further, the functionality of the device or apparatus may be implemented by any combination of hardware and software. The device or apparatus may also be regarded as an assembly of a plurality of devices and / or apparatuses, whether or not they cooperate with each other functionally or are independent of each other. Moreover, the device and apparatus may be implemented distributively throughout the system, as long as the functionality of the device or apparatus is retained. Such and similar principles are considered to be known to those skilled in the art.

[0218] Unless otherwise defined, all terms (including technical and scientific terms) used herein shall have the same meaning as commonly understood by one of ordinary skill in the art to which this disclosure belongs. The terms used herein shall be construed to have a meaning consistent with the meaning of those terms in the context of this specification and the relevant art, and it should be further understood that they are not to be construed in an idealized or overly formal sense unless expressly so defined herein.

[0219] Furthermore, some of the terms used in this disclosure, including the specification and drawings, may be used synonymously in some instances (e.g., "data" and "information"). It should be understood that while these terms (and / or other terms that may be synonymous with each other) may be used synonymously herein, there may be instances where such words are not intended to be used synonymously.

[0220] The techniques and apparatuses described herein include, but are not limited to, the following listed examples. A method for a user equipment (UE) configured to communicate with a radio network via a master cell group (MCG) and a secondary cell group (SCG), the method comprising: when deactivating the SCG, interrupting the media access control (MAC) entity associated with the SCG and, upon interruption, performing one or more first operations on the MAC entity; while the MAC entity is interrupted, performing one or more second operations related to reporting uplink (UL) data available for transmission via the SCG; when reactivating the SCG, resuming the MAC entity and, upon resuming, performing one or more third operations on the MAC entity The method comprising. A2. Performing a first operation on the MAC entity upon interruption is one of the following procedures that is in progress, namely: Random access (RA), Scheduling request (SR), Power headroom report (PHR), Consistent listen before talk (LBT) failure recovery, Beam failure recovery (BFR), Preemptive buffer status report (BSR), Recommended bitrate query, Uplink (UL) configured grant (CG) confirmation, Sidelink (SL) CG confirmation, and Desired guard symbol (DSG) query The method according to embodiment A1, comprising canceling one or more of them. A3. An ongoing RA procedure not caused by a pending BSR for transmission is canceled, but an ongoing RA procedure caused by a pending BSR for transmission is not canceled, and Ongoing SR procedures not caused by a BSR pending for transmission are cancelled, but ongoing SR procedures caused by a BSR pending for transmission are not cancelled. The method according to embodiment A2, to which one or more of A4. When interrupted, performing a first operation on the MAC entity includes setting the new data indicator (NDI) to a value of 0 for all ongoing UL hybrid automatic repeat request (HARQ) processes, flushing the soft buffer for each ongoing downlink (DL) HARQ process, resetting one or more active counters, stopping one or more running timers, considering one or more running timers as expiring, interrupting one or more UL resource grants or DL resource allocations, releasing one or more physical UL control channel (PUCCH) resources, releasing a temporary identifier allocated by the radio network and the method according to any one of embodiments A1 to A3, including one or more of A5. One or more running timers, when interrupted, include a first timer that triggers a regular buffer status report (BSR), and a second timer that triggers a scheduling request (SR) on the primary cell (PCell) of the MCG and the method according to embodiment A4, including all running timers except that at least one of them continues to run. A6. The method according to embodiment A4 or A5, wherein an interrupted UL resource grant includes only type-1 UL configured grants (CGs) for all cells having a related timer that has not expired. A7. The method according to any one of embodiments A4 to A6, wherein the released PUCCH resources include PUCCH resources for all cells having an associated timer that has not expired, excluding the PUCCH resources for transmitting a scheduling request (SR). A8. The method according to any one of embodiments A1 to A7, wherein performing a first operation on a MAC entity during an interruption includes maintaining an ongoing buffer status report (BSR) procedure. A9. The second operation performed while the MAC entity is interrupted is starting a buffer status report (BSR) procedure for reporting UL data available for transmission via the SCG, starting a scheduling request (SR) procedure when a physical UL shared channel (PUSCH) resource is not available for transmitting a BSR, starting a random access (RA) procedure when a physical UL control channel (PUCCH) resource is not available for transmitting an SR and the method according to any one of embodiments A1 to A8. A10. The method according to embodiment A9, wherein the SR procedure is started with substantially zero latency after determining that a PUSCH resource is not available for transmitting a BSR. A11. The method according to embodiment A9, wherein starting the BSR procedure is based on the availability of UL data for transmission in a subset of all logical channels (LCHs) of the MAC entity. A12. The subset of LCHs is only the LCHs not associated with a split secondary radio link control (RLC) entity, only the LCHs belonging to a logical channel group (LCG), only the LCHs carrying delay-sensitive UL data, and specific LCHs indicated by the radio network via radio resource control (RRC) signaling The method according to embodiment A11, comprising one or more of the following. A13. The second operation performed while the MAC entity is suspended is monitoring the availability of UL data on one or more logical channels (LCHs) of the MAC entity, and starting a scheduling request (SR) procedure based on detecting the availability of UL data on at least one of the monitored LCHs, and starting a random access (RA) procedure when a physical UL control channel (PUCCH) resource is not available for transmitting the SR The method according to any one of embodiments A1 to A8, comprising the following. A14. Starting the SR procedure is while the MAC entity is suspended, no other SR procedure has been started, or a physical UL shared channel (PUSCH) resource is not available for transmitting a buffer status report (BSR), The method according to embodiment A13, further based on one or more of the following. A15. The monitored LCH is the following subset of all LCHs of the MAC entity, namely only the LCHs not associated with the split secondary radio link control (RLC) entity, only the LCHs belonging to a logical channel group (LCG), only the LCHs carrying delay-sensitive UL data, and specific LCHs indicated by the radio network via radio resource control (RRC) signaling The method according to embodiment A13 or A14, comprising one of the following. A16. The third operation performed when the MAC entity is resumed is starting a random access (RA) procedure on the primary SCG cell (PSCell), and resuming one or more interrupted UL resource grants or DL resource allocations Starting a timer for a periodic power headroom report (PHR), and Resetting the prioritization parameters for each logical channel (LCH) of the MAC entity, and Considering each LCH belonging to a logical channel group (LCG) as having zero UL data available for transmission, and The method according to any one of Embodiments A1 to A15, including one or more of the above. A17. Resuming the MAC entity, Starting a buffer status report (BSR) procedure in the SCG, and Sending a confirmation response to a network command for activating the SCG, Starting a scheduling request (SR) procedure in the SCG, and Starting a random access (RA) procedure in the SCG, and The method according to any one of Embodiments A1 to A15, including one or more of the above. B1. A user equipment (UE) configured to communicate with a radio network via a master cell group (MCG) and a secondary cell group (SCG), the UE comprising: A communication interface circuit configured to communicate with the radio network via the SCG and the MCG, and A processing circuit operably coupled to the communication interface circuit, whereby the processing circuit and the communication interface circuit are configured to perform operations corresponding to any of the methods described in Embodiments A1 to A17. The user equipment (UE) comprising the above. B2. A user equipment (UE) configured to communicate with a radio network via a master cell group (MCG) and a secondary cell group (SCG), the UE being further configured to perform operations corresponding to any of the methods described in Embodiments A1 to A17. A non-transitory computer-readable medium storing computer-executable instructions that, when executed by a processing circuit of a user equipment (UE) configured to communicate with a radio network via a master cell group (MCG) and a secondary cell group (SCG), configure the UE to perform operations corresponding to any of the methods described in Embodiments A1 to A17. A computer program product comprising computer-executable instructions that, when executed by a processing circuit of a user equipment (UE) configured to communicate with a radio network via a master cell group (MCG) and a secondary cell group (SCG), configure the UE to perform operations corresponding to any of the methods described in Embodiments A1 to A17.

Claims

1. A method for a user equipment (UE) configured to communicate with a radio network via a plurality of cell groups including a master cell group (MCG) and a secondary cell group (SCG), the method comprising: performing one or more first operations on the MAC entity when deactivating the SCG and thus deactivating the media access control (MAC) entity associated with the SCG, the one or more first operations on the MAC entity including canceling one or more ongoing MAC entity procedures; performing one or more second operations related to reporting uplink (UL) data available for transmission via the SCG while the SCG and the associated MAC entity are deactivated (2020); performing one or more third operations (2030) on the MAC entity when reactivating the SCG and the associated MAC entity, the one or more third operations including resetting respective prioritization parameters associated with a plurality of logical channels of the MAC entity to a predetermined initial value of zero (2034); A method comprising the above.

2. Canceling the one or more ongoing MAC entity procedures includes canceling one or more of the following MAC entity procedures, namely: Random Access (RA), Scheduling Request (SR), Power Headroom Report (PHR), Consistent Listen Before Talk (LBT) failure recovery, Beam Failure Recovery (BFR), Pre-emptive Buffer Status Report (BSR), Recommended Bitrate Query, UL Configured Grant (CG) confirmation, SideLink (SL) CG confirmation, and Desired Guard Symbol (DSG) Query The method according to claim 1, comprising canceling one or more of the above.

3. An ongoing RA procedure not caused by a BSR pending for transmission is canceled, but an ongoing RA procedure caused by a BSR pending for transmission is not canceled, and Ongoing SR procedures not caused by the BSR pending for transmission are cancelled, but ongoing SR procedures caused by the BSR pending for transmission are not cancelled. The method according to claim 2, wherein one or more of the following apply.

4. When deactivating the SCG and the associated MAC entity, the one or more first operations performed on the MAC entity are setting the new data indicator (NDI) for the ongoing UL hybrid ARQ (HARQ) process to a value of 0 (2013); flushing the soft buffer for the ongoing downlink (DL) HARQ process (2014); resetting one or more active counters (2015); stopping or considering as expiring one or more running timers (2016); interrupting one or more UL resource grants (2017); releasing one or more physical UL control channel (PUCCH) resources (2018); releasing one or more temporary identifiers allocated by the radio network (2019); The method according to claim 1, comprising one or more of the following.

5. The one or more running timers that are stopped or considered as expiring, upon interruption, include a first timer that triggers a regular buffer status report (BSR); a second timer that triggers a scheduling request (SR) on the primary cell (PCell) of the deactivated SCG. The method according to claim 4, wherein at least one of the above timers continues to run, including all running timers except those that continue to run.

6. The method according to claim 4, wherein the interrupted UL resource grant includes only type-1 UL configured grants (CGs) for all cells having a related timer that has not expired.

7. The method according to claim 4, wherein the released PUCCH resources include PUCCH resources for all cells having a related timer that has not expired, excluding the PUCCH resources for transmitting scheduling requests.

8. The method according to claim 1, wherein the one or more first operations performed upon deactivation of the SCG and the associated MAC entity include maintaining a buffer status report (BSR) procedure for the logical channels of the MAC entity that was in progress at the time of deactivation of the MAC entity (2012).

9. The one or more second operations performed while the SCG and the associated MAC entity are deactivated are starting a BSR procedure for reporting UL data available for transmission via the deactivated cell group (2021); starting a scheduling request (SR) procedure (2022) when a physical UL shared channel (PUSCH) resource is not available for transmitting a BSR; starting a random access (RA) procedure (2025) when a physical UL control channel (PUCCH) resource is not available for transmitting an SR and including one or more of the foregoing, the method according to claim 1.

10. The SR procedure is started with substantially zero delay (2022) after it is determined that a PUSCH resource is not available for transmitting a BSR, or starting the BSR procedure (2021) is based on the availability of UL data for transmission in a subset of all logical channels (LCHs) of the MAC entity and one of the foregoing is applicable, the method according to claim 9.

11. The subset of LCHs includes only LCHs not associated with a split secondary radio link control (RLC) entity, only LCHs belonging to a logical channel group (LCG), only LCHs carrying delay-sensitive UL data, and specific LCHs indicated by the radio network via radio resource control (RRC) signaling and including one or more of the foregoing, the method according to claim 10.

12. The one or more second operations performed while the MAC entity is deactivated include monitoring the availability of UL data on one or more logical channels (LCHs) of the MAC entity (2023) and including the foregoing, the method according to claim 1.

13. The monitored LCH is the following subset of all LCHs of the MAC entity, i.e., only the LCHs not associated with the split secondary radio link control (RLC) entity, only the LCHs belonging to a logical channel group (LCG), only the LCHs carrying delay-sensitive UL data, and specific LCHs indicated by the radio network via radio resource control (RRC) signaling The method according to claim 12, comprising one of the above.

14. The one or more third operations (2030) performed when reactivating the deactivated cell group are further comprising resuming one or more interrupted UL resource grants (2032) The method according to claim 1, further comprising the above.

15. A user equipment (UE) (120, 505, 605, 700, 2112, 2200, 2606) configured to communicate with a radio network (100, 399, 599, 699, 2104) via a plurality of cell groups including a master cell group (MCG) and a secondary cell group (SCG), wherein the UE comprises a communication interface circuit (2212) configured to communicate with the radio network via the plurality of cell groups, and a processing circuit (2202) operably coupled to the communication interface circuit, whereby the processing circuit and the communication interface circuit perform one or more first operations on the MAC entity when deactivating the SCG and thus deactivating the MAC entity associated with the SCG, the one or more first operations on the MAC entity including canceling one or more ongoing MAC entity procedures; perform one or more second operations related to reporting uplink (UL) data available for transmission via the SCG while the SCG and the associated MAC entity are deactivated. When the SCG and the related MAC entity are reactivated, one or more third operations are performed on the MAC entity, and the one or more third operations include resetting respective prioritization parameters related to a plurality of logical channels of the MAC entity to a predetermined initial value of 0 (2034), and performing one or more third operations A user equipment (UE) (120, 505, 605, 700, 2112, 2200, 2606) configured to perform the above [

16. ] The UE according to claim 15, wherein the processing circuit and the communication interface circuit are further configured to perform operations corresponding to any one of the methods according to any one of claims 2 to 14 [

17. ] A user equipment (UE) (120, 505, 605, 700, 2112, 2200, 2606) configured to communicate with a radio network (100, 399, 599, 699, 2104) via a plurality of cell groups including a master cell group (MCG) and a secondary cell group (SCG), wherein the UE When the SCG is deactivated and thus the media access control (MAC) entity related to the SCG is deactivated, one or more first operations are performed on the MAC entity, and the one or more first operations on the MAC entity include canceling one or more ongoing MAC entity procedures, and performing one or more first operations While the SCG and the related MAC entity are deactivated, performing one or more second operations related to reporting uplink (UL) data available for transmission via the SCG When the SCG and the related MAC entity are reactivated, one or more third operations are performed on the MAC entity, and the one or more third operations include resetting respective prioritization parameters related to a plurality of logical channels of the MAC entity to a predetermined initial value of 0 (2034), and performing one or more third operations A user equipment (UE) (120, 505, 605, 700, 2112, 2200, 2606) further configured to perform **Claim 18** The UE according to claim 17, further configured to perform an operation corresponding to any one of the methods according to any one of claims 2 to 14. **Claim 19** A non-transitory computer-readable storage medium (2210) storing computer-executable instructions that, when executed by a processing circuit (2202) of a user equipment (UE) (120, 505, 605, 700, 2112, 2200, 2606) configured to communicate with a wireless network (100, 399, 599, 699, 2104) via a plurality of cell groups, configure the UE to perform an operation corresponding to any one of the methods according to any one of claims 1 to 14. **Claim 20** A computer program (2214) comprising computer-executable instructions that, when executed by a processing circuit (2202) of a user equipment (UE) (120, 505, 605, 700, 2112, 2200, 2606) configured to communicate with a wireless network (100, 399, 599, 699, 2104) via a plurality of cell groups, configure the UE to perform an operation corresponding to any one of the methods according to any one of claims 1 to 14.

Images