Reporting uplink data arrival for a deactivated secondary cell group (SCG)

Abstract

An embodiment includes a method for a user equipment (UE) configured with a master cell group (MCG) and a secondary cell group (SCG) in a radio network. Such a method includes determining availability of uplink (UL) data for transmission via the SCG while the SCG is in a deactivated state and calculating an available UL data volume. Such a method also includes transmitting an indication of the available UL data volume to the radio network via one or more of the SCG in a deactivated state, the SCG after activation, the SCG after receiving an indication from the radio network that the SCG should be activated, and the MCG. Other embodiments include supplemental methods for a first node configured to provide an MCG and for a second node configured to provide an SCG, and UEs and network nodes configured to implement such methods.

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 a plurality of 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 for so-called fourth generation (4G) wireless access technologies 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), including the evolved packet core (EPC) network. LTE continues to evolve through subsequent releases.

[0003] An exemplary overall 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 term "user equipment" or "UE" used within the 3GPP specifications means any wireless communication device (e.g., a smartphone or a computing device) capable of communicating with 3GPP specification-compliant network equipment, including the E-UTRAN as well as the UTRAN and / or GERAN as is commonly known for the Third Generation ("3G") and Second Generation ("2G") 3GPP RANs.

[0004] 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 eNBs such as eNB 105, 110, and 115. Each eNB can serve a geographical coverage area that includes one or more cells, including cells 106, 111, and 115 served by eNB 105, 110, and 115, respectively.

[0005] As shown in FIG. 1, eNBs in the E-UTRAN communicate with each other via the X2 interface. The eNB also serves the role of the E-UTRAN interface to the EPC, specifically, the role of the S1 interface to the Mobility Management Entity (MME) and Serving Gateway (SGW), collectively shown as MME / S-GW 134 and 138 in FIG. 1. 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 serves as the local mobility anchor for data bearers when the UE moves between eNBs such as eNB 105, 110, and 115.

[0006] EPC 130 may also include a Home Subscriber Server (HSS) 131 that manages user relationship information and subscriber relationship 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 may relate to the functions and operations of a legacy Home Location Register (HLR) and an Authentication Center (AuC). The HSS 131 can also communicate with the MMEs 134 and 138 via their respective S6a interfaces.

[0007] 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 the user credentials are 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.

[0008] Figure 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 related to how characteristics are used and which characteristics are used to transfer data on a transport channel over the 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.

[0009] The RRC layer controls the communication between the UE and the eNB over the radio interface and 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). The UE returns to RRC_IDLE after the connection with the network is released. In the RRC_IDLE state, the UE does not belong to any cell, (for example, in the E-UTRAN) no RRC context is established for the UE, 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 allocated IP address.

[0010] Furthermore, in the RRC_IDLE state, the UE's radio is active on the discontinuous reception (DRX) schedule set by the upper layer. (Also referred to as the "DRX on duration") During the DRX active period, 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.

[0011] The UE must perform a random access (RA) procedure to move from the 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 at the serving eNB for the UE so that the UE and the eNB can communicate. 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.

[0012] 3GPP Rel-10 supports bandwidths larger than 20 MHz. One important Rel-10 requirement is backward compatibility with Rel-8. Thus, a wideband LTE Rel-10 carrier (e.g., >20 MHz) should appear as multiple carriers (referred to as "component carriers" or CCs) to Rel-8 ("legacy") terminals. Legacy terminals can be scheduled in all parts of the wideband Rel-10 carrier. One way to achieve this is by carrier aggregation (CA), whereby a Rel-10 terminal can receive multiple CCs, each of which preferably has the same structure as a Rel-8 carrier.

[0013] LTE Dual Connectivity (DC) was introduced in Rel-12. In DC operation, a UE in the RRC_CONNECTED state consumes radio resources provided by at least two different network points connected to each other using a non-ideal backhaul. In LTE, these two network points are sometimes referred to as the "Master eNB" (MeNB) and the "Secondary eNB" (SeNB). More generally, the terms Master Node (MN), Anchor Node, and MeNB can be used interchangeably, and the terms Secondary Node (SN), Booster Node, and SeNB can also be used interchangeably. DC can be considered a special case of CA, where the aggregated carriers (or cells) are provided by network nodes that are physically separated and not connected via a robust high-capacity connection.

[0014] Currently, the fifth generation ("5G") of cellular systems, also known as New Radio (NR), is being standardized within the 3rd Generation Partnership Project (3GPP). NR is 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 D2D (device-to-device), and several other use cases. 5G / NR technology shares many similarities with 4G LTE. For example, both PHYs utilize a similar structure of time-domain physical resources to form a 1ms subframe containing multiple slots of equal duration, with each slot containing multiple OFDM-based symbols. As another example, the NR RRC layer includes the RRC_IDLE state and the RRC_CONNECTED state, but adds another state known as RRC_INACTIVE.

[0015] DC is also envisioned as an important feature for 5G / NR networks. Several DC (or more generally, multi-connectivity) scenarios have been considered for NR. These include NR-DC which is similar to LTE-DC described above, except that both the MN and the SN (referred to as "gNB") employ NR interfaces to communicate with the UE. Furthermore, various multi-RAT DC (MR-DC) scenarios have been considered, whereby the UE can be configured to use resources provided by two different nodes, namely, one providing E-UTRA / LTE access and the other providing NR access. One node acts as the MN (e.g., providing the MCG), and the other acts as the SN (e.g., providing the SCG), and the MN and SN are connected via a network interface, with at least the MN connected to the core network (e.g., EPC or 5GC).

[0016] Each CG includes one MAC entity, one primary cell (PCell), and optionally one or more secondary cells (SCells). The term "special cell" (or abbreviated "SpCell") refers to the PCell of the MCG or the PSCell of the SCG, 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 UL control channel (PUCCH) transmission and contention-based random access by the UE.

[0017] To improve the network energy efficiency and battery life for the UE in MR-DC, 3GPP Rel-17 includes a work item for efficient SCG / SCell activation / deactivation. This can be particularly important for MR-DC setups with 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. SUMMARY OF THE INVENTION

[0018] However, when the UE's SCG is deactivated (or more generally, in a reduced-energy mode such as SCG suspended, SCG dormant, etc.), the UE may not be able to notify the network of the arrival of UL data that needs to be transmitted by the UE (e.g., from the application layer and / or NAS). This may cause various problems, issues, and / or difficulties related to SN awareness and scheduling of SCG resources for UL data transmission.

[0019] Embodiments of the present disclosure provide certain improvements to the UL data transmission procedure in a wireless network, such as by facilitating solutions to overcome the exemplary problems summarized above and described in more detail below.

[0020] Embodiments of the present disclosure include methods (e.g., procedures) for a UE in which an MCG and an SCG are configured in a wireless network.

[0021] These exemplary methods can include determining the availability of uplink (UL) data for transmission via the SCG while the SCG is deactivated. These exemplary methods can include calculating the available UL data volume and ● the SCG in the deactivated state, ● the SCG after activation, ● the SCG after receiving an indication from the wireless network that the SCG should be activated, and ● the MCG transmitting an indication of the available UL data volume to the wireless network via one or more of the above.

[0022] In some embodiments, these exemplary methods can also include receiving, from a first node configured to provide MCG, a first indication that the SCG should be deactivated, and deactivating the SCG in response to the first indication. In some embodiments, deactivating the SCG can include stopping or suspending one or more timers associated with periodic reporting of the available UL data volume related to the SCG.

[0023] In some embodiments, the indication of the available UL data volume is one of an indication that UL data is available for transmission via the SCG, an indication of the volume of UL data available for transmission via the SCG, or an indication that the SCG should be activated.

[0024] In some embodiments, transmitting the indication of the available UL data volume can include receiving, from a second node configured to provide the SCG, a UL grant for transmission of a buffer status report (BSR), and using the received UL grant to transmit, via the SCG, a BSR indicating the available UL data volume to the second node.

[0025] In some of these embodiments, transmitting the indication of the available UL data volume can also include sending a scheduling request (SR) to the second node. The UL grant can be received in response to the SR, ● The SR and BSR are transmitted while the SCG is in the deactivated state, ● The SR is transmitted while the SCG is in the deactivated state and the BSR is transmitted after activating the SCG, or ● The SR and BSR are transmitted after activating the SCG, and one of these is applicable.

[0026] In some variations, the UL grant can include a second indication that the SCG should be activated, and transmitting an indication of the available UL data volume can also include activating the SCG in response to the second indication and before transmitting the BSR.

[0027] In other ones of these embodiments, the UL grant can be a configured UL grant for use while the SCG is in an inactivated state. In such a case, the configured UL grant can be received from the second node before the SCG is inactivated.

[0028] In some embodiments, these exemplary methods can include activating the SCG based on determining the availability of UL data. In these embodiments, these exemplary methods can also include starting a timer in response to activating the SCG. In some of these embodiments, these exemplary methods can also include deactivating the SCG when the timer expires after reporting the available UL data volume.

[0029] In some embodiments, these exemplary methods can, before the expiration of the timer, receive from a second node configured to provide the SCG ● a third indication that the SCG should be activated, or ● a fourth indication that the SCG should be deactivated and can also include receiving one of them. In such a case, the UE can stop the timer in response to the third indication or the fourth indication.

[0030] In some embodiments, transmitting an indication of the available UL data volume may include transmitting an indication of the available UL data volume in one of a Medium Access Control (MAC) Buffer Status Report (BSR), a Radio Resource Control (RRC) message, or a Packet Data Convergence Protocol (PDCP) Protocol Data Unit (PDU) to a first node configured to provide the MCG. In some variations, the RRC message may be a UEAssistanceInformation message. In other variations, the MAC BSR may be transmitted using the RRC message as a container.

[0031] In some of these embodiments, these exemplary methods may also include receiving, from the first node in response to an indication of the available UL data volume, a fifth indication that the SCG should be activated, and activating the SCG in response to the fifth indication.

[0032] In various embodiments, calculating the available UL data volume may be ● based on one or more of the type of bearer associated with the available UL data, ● whether the MCG or SCG is configured as the PDCP primary path, ● whether PDCP duplication is enabled and may be based on one or more of the foregoing.

[0033] In some embodiments, transmitting an indication of the available UL data volume may include determining that the available UL data volume is greater than a first threshold applicable when the SCG is in a deactivated state and / or may be based on such determination. In some of these embodiments, the first threshold may be different from a second threshold applicable when the SCG is in an activated state.

[0034] Other embodiments include a method (e.g., a procedure) for a second node configured to provide an SCG to a UE in which an MCG is also configured, in a wireless network.

[0035] These exemplary methods can include receiving, from the UE, an indication of the UL data volume available for transmission by the UE via the SCG. The available UL data volume is determined by the UE while the SCG is in a deactivated state. The indication can be received via one or more of: ● the SCG in a deactivated state, and ● the SCG after activation of the SCG by the UE, and ● the SCG after sending an indication to the UE that the SCG should be activated, and ● the first node of the wireless network configured to provide the MCG. and can be received via one or more of the above.

[0036] In some embodiments, the indication of the available data volume is one of an indication that UL data is available for transmission via the SCG, an indication of the volume of UL data available for transmission via the SCG, or an indication that the SCG should be activated.

[0037] In various embodiments, the indicated volume of UL data available for transmission via the SCG is based on one or more of: ● the type of bearer associated with the available UL data, and ● whether the MCG or the SCG is configured as the PDCP primary path, and ● whether PDCP duplication is enabled. and is based on one or more of the above.

[0038] In some embodiments, the indicated volume of UL data available for transmission via the SCG can be greater than a first threshold applicable when the SCG is in a deactivated state. In such embodiments, the first threshold can be different from a second threshold applicable when the SCG is in an activated state.

[0039] In some embodiments, receiving the indication can include the UE being provided with a UL grant for transmission of a BSR, and receiving, from the UE via the SCG in accordance with the UL grant, a BSR indicating the volume of UL data available for transmission via the SCG.

[0040] In some of these embodiments, receiving the indication can include receiving an SR from the UE. The UL grant can be provided in response to the SR, ● The SR and the BSR are received while the SCG is in a deactivated state, ● The SR is received while the SCG is in a deactivated state and the BSR is received after the UE has activated the SCG, or ● The SR and the BSR are received after the UE has activated the SCG, and one of these applies.

[0041] In other ones of these embodiments, the UL grant is a configured UL grant for use while the SCG is deactivated. The configured UL grant can be provided to the UE before or together with an indication that the SCG should be deactivated.

[0042] In some embodiments, these exemplary methods, in response to an indication of the available UL data volume, cause the UE to ● a third indication that the SCG should be activated, or ● a fourth indication that the SCG should be deactivated It can also include transmitting one of them.

[0043] In some embodiments, these exemplary methods respond to an indication of the available UL data volume and, to a first node, ● a fifth indication that the SCG is to be activated, or ● a sixth indication that the SCG is to be deactivated It can also include transmitting one of them.

[0044] In some embodiments, the indication of the available UL data volume can be received from the first node. In such embodiments, these exemplary methods can also include, in response to the indication of the available UL data volume, transmitting to the first node a seventh indication that the SCG should be activated.

[0045] Other embodiments include methods (e.g., procedures) for a first node configured to provide an MCG to a UE in a wireless network in which an SCG is also configured.

[0046] These exemplary methods can include receiving, from the UE while the SCG is in a deactivated state, an indication of the UL data volume available for transmission by the UE via the SCG. These exemplary methods can also include transmitting the indication of the available UL data volume to a second node configured to provide the SCG.

[0047] In some embodiments, these exemplary methods can also include receiving, from the second node in response to the indication of the available UL data volume, a second indication that the SCG should be activated, and transmitting the second indication to the UE.

[0048] In some embodiments, an indication of the available UL data volume is received from the UE in one or more of the MAC BSR, the RRC message, and the PDCP PDU. In some variations, the RRC message is the UE Assistance Information message. In other variations, the MAC BSR is transmitted using the RRC message as a container.

[0049] In some embodiments, the indication of the available UL data volume is one of an indication that UL data is available for transmission via the SCG, an indication of the volume of UL data available for transmission via the SCG, or an indication that the SCG should be activated.

[0050] In various embodiments, the indicated volume of UL data available for transmission via the SCG is ● the type of bearer associated with the available UL data, and ● whether the MCG or the SCG is configured as the PDCP primary path, and ● whether PDCP duplication is enabled based on one or more of the above.

[0051] In some embodiments, the indicated volume of UL data available for transmission via the SCG can be greater than a first threshold applicable when the SCG is in the deactivated state. The first threshold can be different from a second threshold applicable when the SCG is in the activated state.

[0052] In some embodiments, these exemplary methods can also include transmitting to the UE a first indication that the SCG should be deactivated. This first indication can be transmitted before receiving the indication of the available UL data volume.

[0053] Other embodiments include a UE (e.g., a wireless device, an IoT device, etc., or one or more of their components) configured to perform operations corresponding to any of the exemplary methods described herein, and a network node (e.g., a base station, eNB, gNB, ng-eNB, en-gNB, etc., or one or more of their components). Other embodiments include a non-transitory computer-readable medium storing program instructions that, when executed by a processing circuit, configure such a UE or network node to perform operations corresponding to any of the exemplary methods described herein.

[0054] These and other embodiments described herein can facilitate a secondary node (SN) of a UE becoming aware that an inactivated SCG of the UE has available UL data related to an SCG bearer and / or a split bearer. This enables the SN to timely activate the inactivated SCG, thereby avoiding delays in receiving available UL data. By avoiding such delays, the performance of a UE application that generates UL data can be improved, which ultimately improves the user experience.

[0055] 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 briefly described below.

Brief Description of the Drawings

[0056]

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

Figure 14

Figure 15

Figure 16

Figure 17

Figure 18

Figure 19

Figure 20

Figure 21

Figure 22

Figure 23

Figure 24A

Figure 24B

Figure 25

Figure 26

Figure 27

Figure 28

Figure 29

Figure 30

Figure 31

Figure 32

Figure 33

Figure 34

Figure 35

DETAILED DESCRIPTION OF THE INVENTION

[0057] Next, some of the embodiments contemplated herein will be described more fully with reference to the accompanying drawings. 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.

[0058] 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. All references 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. None of the steps of any method disclosed herein need to 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.

[0059] 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 5th 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 (SGW), a packet data network gateway (P-GW), an access and mobility management function (AMF), a session management function (AMF), a user plane function (UPF), a service capability exposure function (SCEF), etc. ● Wireless Device: As used herein, a "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 another wireless device. 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, and the like. 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, a "network node" is any node that is part of either a wireless access network (e.g., the wireless 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 with 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.

[0060] 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, (especially with respect to 5G NR) beams may be used instead of cells, and thus it should be understood that the concepts described in this specification apply equally to both cells and beams.

[0061] As briefly described above, when the SCG of the UE is deactivated (or, more generally, in a reduced energy mode such as SCG interruption, SCG dormant, etc.), the UE may not be able to notify the network of the arrival of UL data that needs to be transmitted by the UE (e.g., from the application layer and / or NAS). This may cause various problems, issues, and / or difficulties related to SN awareness and SCG resource scheduling for UL data transmission. This will be described in more detail below after the following description of the NR network architecture and various dual connectivity (DC) configurations.

[0062] 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 to the 5GC via one or more NG interfaces, such as interfaces 302, 352, respectively. Further, the gNBs can be connected to each other via one or more Xn interfaces, such as Xn interface 340 between gNB 300 and gNB 350. With respect to the NR interface to the UE, each of the gNBs can support frequency division duplexing (FDD), time division duplexing (TDD), or a combination thereof.

[0063] NG-RAN 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. In some exemplary configurations, each gNB is connected to all 5GC nodes within an "AMF area", and the term "AMF" is further explained below.

[0064] The NG RAN logical nodes shown in Figure 3 include a Central (or Centralized) Unit (CU or gNB-CU) and one or more Distributed (or Decentralized) Units (DU or gNB-DU). For example, gNB300 includes gNB-CU310 and gNB-DUs 320 and 330. The CU (e.g., gNB-CU310) is a logical node that hosts upper layer protocols and performs 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 depending on the functional split. Thus, each of the CU and DU can include the various circuits required to perform their respective functions, including a processing circuit, a transceiver circuit (e.g., for communication), and a power supply circuit. Moreover, the terms "Central Unit" and "Centralized Unit" are used interchangeably herein, and the same applies to the terms "Distributed Unit" and "Decentralized Unit".

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

[0066] 3GPP TR38.804 (v14.0.0) describes various exemplary DC scenarios or configurations where the MN and SN can apply NR, LTE, or both. 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, 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 acting as the MN and one gNB acting as the SN. The ng-eNB is connected to the 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 acting as the MN and one ng-eNB acting as the SN. The gNB is connected to the 5GC, and the ng-eNB is connected to the gNB via the Xn interface. ● NR-DC (or NR-NR DC): Both the MN and SN employ NR. ● MR-DC (Multi-RAT DC): Generalization of intra-E-UTRA dual connectivity (DC) as described in 3GPP TS36.300 (v16.3.0), where multiple Rx / Tx UEs are 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. One of the nodes acts as the MN and the other as the SN. The MN and 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.

[0067] Figure 4 shows a high-level diagram of DC combined with carrier aggregation (CA). In this figure, each of the MN and SN can be either an eNB or a gNB according to the various DC scenarios described 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.

[0068] 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 510 (e.g., 510a, b) and eNBs 520 (e.g., 520a, b) interconnected with each other via their respective X2 (or X2-U) interfaces. The eNB can be similar to that shown in Figure 1, and the ng-eNB can be similar to the gNB shown in Figure 3 except that they are connected to the EPC via the S1-U interface instead of being connected to the 5GC via the X2 interface. The eNB is also connected to the EPC via the S1 interface, similar to the configuration shown in Figure 1. More specifically, the en-gNB and eNB 520 are connected to the MME (e.g., 530a, b) and S-GW (e.g., 540a, b) in the EPC.

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

[0070] In addition to providing coverage via "cells" as in the case of LTE, the NR network also provides coverage via "beams". Generally, a DL "beam" is a coverage area of network-transmitted RS that can be measured or monitored by a UE. In NR, for example, such 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), demodulation RS (DMRS), phase-tracking reference signals (PTRS), etc. Generally, the 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.

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

[0072] Each of the gNBs can be similar to those shown in FIG. 5, and each of the ng-eNBs can be similar to the eNBs shown in FIG. 1, except that they are connected to 5GC via the NG interface instead of being connected to the EPC via the S1 interface. Each of the gNBs and ng-eNBs can serve a geographic coverage area including one or more cells, 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 particular cell in which the UE 605 is located, the UE 605 can communicate with the gNB or ng-eNB serving that particular cell via an NR or LTE radio interface, respectively. Further, the UE 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.

[0073] 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 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 RATs 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.

[0074] 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, or 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 bearers 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 bearers 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 terminated at the SDAP.

[0075] Figures 9 to 10 also have some DC-specific deformation forms. In EN-DC using EPC, the network can set either LTE PDCP or NR PDCP for the MN-terminated MCG data radio bearer (DRB), but NR PDCP is used for all other DRBs. In MR-DC using 5GC, NR PDCP is always used for all DRB types. In NGEN-DC, LTE 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 LTE RLC / MAC is used at the SN. In NR-DC, NR RLC / MAC is used at both the MN and the SN.

[0076] Figure 11 is a block diagram showing a high-level comparison of the CP architectures in LTE DC, EN-DC, and MR-DC using 5GC. One major difference is that in EN-DC and MR-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 cooperates with the MN. In LTE-DC, RRC decisions are always made by the MN (from the MN to the UE). Even so, the LTE-DC SN still determines its own configuration because the SN is aware of the SN's resources, capabilities, etc., while the MN is not.

[0077] 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 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 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.

[0078] Packet duplication (also called "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.

[0079] Figure 12 shows an exemplary PDCP duplication scheme. 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 PDCP duplication state (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.

[0080] 3GPP has previously specified the concept of a dormant LTE SCell and dormancy-like behavior such as that 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 UL. This behavior is similar to that in the deactivated state, but the UE is also required to perform and report CQI measurements, which is different from the deactivated state behavior. A PUCCH SCell (an SCell with PUCCH configured) cannot become dormant.

[0081] In NR, dormancy-like behavior for an 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. If 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). 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 containing 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). A dormant BWP cannot be set for the SpCell (i.e., the PCell or PSCell) and the PUCCH SCell.

[0082] Figure 13 is an exemplary state transition diagram for an NR SCell. At a high level, the SCell of a UE can transition between a deactivated state and an activated state based on an explicit command from the network (e.g., MAC CE) or expiration of an inactivation timer. Within the activated state, a particular BWP can transition between an active condition and a dormant condition based on DCI received from the network.

[0083] However, when MR-DC is configured for a UE, the UE cannot fully benefit from energy reduction behaviors such as the dormant state or suspension because the PSCell cannot be configured to become dormant. Instead, existing solutions can, as needed, release the SCG (for power saving) and add the SCG (when traffic demand requires). However, 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 cause significant delay.

[0084] In the context of 3GPP Rel-16, there were several descriptions regarding putting the PSCell into suspension, also referred to as SCG interruption. Some agreed principles of this solution include the following. ● The UE supports network-controlled interruption of the SCG in RRC_CONNECTED. ● Further study (FFS) is needed for UE behavior regarding the interrupted SCG. ● The UE supports at most one SCG configuration, interrupted or not, in Rel16. ● At RRC_CONNECTED upon addition of the SCG, the SCG can be either interrupted or not interrupted by configuration.

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

[0086] In 3GPP RAN1, RAN2, and RAN3 WGs, discussions are ongoing regarding solutions for the Rel-17 MR-DC work item objective "Support efficient activation / de-activation mechanism for one SCG and SCells". One concept under discussion is "deactivated SCG" with reduced energy consumption when traffic demand is dynamically reduced. Figure 14 is an exemplary state transition diagram showing two SCG states (sometimes called "states for SCG activation") according to this concept. In Figure 14, these states are labeled "SCG deactivated 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.

[0087] The current RAN2 assumption is that in the "SCG deactivated state", the UE does not perform PDCCH monitoring of the PSCell in order to reduce energy consumption. This also means that UL / DL data transmission in the SCG is interrupted in the SCG deactivated state. The activation and deactivation 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 deactivated, even if 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.

[0088] 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 scheduling requests (SR), and measurement reports including buffer status reports (BSR) and power headroom reports (PHR). Further details regarding NR UL scheduling are given in 3GPP TS38.300 and 38.321.

[0089] 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 resource allocation for transmission (e.g., in time / frequency) and other instructions on how to transmit data on the PUSCH.

[0090] UL BSR (or more simply, BSR) is required for QoS-aware packet scheduling. In NR, the BSR indicates the amount of data buffered at the UE for each logical channel group (LCG). 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 SR. 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.

[0091] In NR, the RRC layer sets the following parameters to control the UE BSR. ● periodicBSR-Timer, per MAC entity configuration in BSR-Config (effectively optional), ● retxBSR-Timer, per MAC entity configuration in BSR-Config (mandatory), ● logicalChannelSR-DelayTimerApplied, per logical channel configuration (optional), ● logicalChannelSR-DelayTimer, per MAC entity configuration in BSR-Config, ● logicalChannelSR-Mask, per logical channel configuration, ● logicalChannelGroup, per 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.

[0092] 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 an 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.

[0093] 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 CE, including: ● Short BSR format (fixed size), ● Long BSR format (variable size), ● Short Truncated BSR format (fixed size), or ● Long Truncated BSR format (variable size).

[0094] Figure 15A shows an exemplary MAC CE in short BSR and short truncated BSR formats, and Figure 15B 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 15A to 15B are defined as follows. ● LCG ID: The logical channel group ID field identifies the group of (one or more) logical channels for which 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, this field indicates the presence of a buffer size field for logical channel group i. The LCG i field set to 1 indicates that a buffer size field for logical channel group i is reported. The LCG i field set to 0 indicates that a buffer size field for logical channel group i is not reported. In the case of the long truncated BSR format, this field indicates whether logical channel group i has available data. The LCG i field set to 1 indicates that logical channel group i has available data. The LCG i field set to 0 indicates that logical channel group i does not have available data. ● Buffer size i: The buffer size field identifies the total amount of data over 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 number of bytes. The sizes of the RLC and MAC headers are not considered in 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.

[0095] The procedure for UE BSR reporting is further specified in 3GPP TS38.321 (v16.2.0) section 5.4.5, which is hereby incorporated by reference in its entirety. 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, and the 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 16A - 16C show the ASN.1 data structures for exemplary CellGroupConfig, MAC-CellGroupConfig, and BSR-Config IEs, respectively.

[0096] The value of the buffer size field reported for LCG in BSR is determined by adding the results of the data volume calculations for each LCH of the LCG. The NR PDCP layer data volume calculation procedure is given by the following procedure text from 3GPP TS38.323 (v16.2.0). ***Start of text from 3GPP TS38.323*** For the purpose of the MAC buffer status report, the transmitting PDCP entity shall consider the following as the PDCP data volume. ● PDCP SDUs for which PDCP data PDUs were not constructed, ● PDCP data PDUs not submitted to the lower layer, ● PDCP control PDUs, ● For AM DRBs, PDCP SDUs to be retransmitted according to section 5.1.2 in 3GPP TS38.323, ● For AM DRBs, PDCP data PDUs to be retransmitted according to section 5.5 in 3GPP TS38.323. When the transmitting PDCP entity is associated with at least two RLC entities, when instructing the MAC entity of the PDCP data volume for BSR triggering and buffer size calculation (specified in TS38.321 and TS36.321), the transmitting PDCP entity shall do the following. ● When PDCP duplication is activated for an RB, ○ Instruct the MAC entity associated with the primary RLC entity of the PDCP data volume, ○ Instruct the MAC entity associated with an RLC entity other than the primary RLC entity activated for PDCP duplication of the PDCP data volume excluding PDCP control PDUs, ○ Instruct the MAC entity associated with the RLC entity deactivated for PDCP duplication that the PDCP data volume is 0, ● Otherwise (i.e., PDCP duplication is deactivated for the RB), ○ When a split secondary RLC entity is configured, and ○ When the total amount of PDCP data volume and RLC data volume pending for initial transmission (specified in TS38.322) in the primary RLC entity and the split secondary RLC entity is equal to or greater than ul-DataSplitThreshold, · Indicate the PDCP data volume to both the MAC entity associated with the primary RLC entity and the MAC entity associated with the split secondary RLC entity, · Indicate the PDCP data volume as 0 to the MAC entity associated with the RLC entity other than the primary RLC entity and the split secondary RLC entity, ○ Otherwise, when the transmitting PDCP entity is associated with a DAPS bearer, · When uplink data switching is not requested, indicate the PDCP data volume to the MAC entity associated with the source cell, · Otherwise, · Indicate the PDCP data volume excluding the PDCP control PDU for the punctured ROHC feedback associated with the source cell to the MAC entity associated with the target cell, · Indicate the PDCP data volume of the PDCP control PDU for the punctured ROHC feedback associated with the source cell to the MAC entity associated with the source cell, ○ Otherwise, · Indicate the PDCP data volume to the MAC entity associated with the primary RLC entity, · Indicate the PDCP data volume as 0 to the MAC entity associated with the RLC entity other than the primary RLC entity. ***End of text from 3GPP TS38.323***

[0097] Similarly, the NR RLC layer data volume calculation procedure is specified in 3GPP TS38.322 (v16.2.0) as follows. ***Start of text from 3GPP TS38.322*** For the purpose of the MAC buffer status report, the UE shall consider the following as the RLC data volume. · RLC SDUs and RLC SDU segments that are not yet included in the RLC data PDU, · RLC data PDUs that are pending for initial transmission, · RLC data PDUs that are pending for retransmission (RLC AM). Furthermore, if the status PDU is triggered and t-StatusProhibit is not active or has expired, the UE shall estimate the size of the status PDU that will be transmitted at the next transmission opportunity and consider this as part of the RLC data volume. ***End of text from 3GPP TS38.322***

[0098] The power headroom report (PHR) is used for transmit-power-aware packet scheduling. In NR, three types of reports are supported, namely, the first type for PUSCH transmission, the second type for PUSCH and PUCCH transmission in the LTE cell group in EN-DC, and the third type for SRS transmission on an SCell where only SRS is configured. In the case of CA, when transmission is not performed on the activated SCell, the reference power is used to provide a virtual report. The PHR is transmitted using a MAC CE.

[0099] In summary, upon arrival of UL data related to a radio bearer (e.g., DRB) (from the application layer for example), the UE triggers a BSR, which includes the amount of data volume calculated in the manner described above and indicates an LCID or LCG ID. Based on this information, the network can provide sufficient resources for UL data transmission. There are different rules for the UE to determine whether to send the BSR to the MCG MAC entity, the SCG MAC entity, or both MAC entities. These rules generally depend on the calculated data volume, the data volume threshold, and which cell group is set as the primary path.

[0100] However, it is considered that SCG transmission and reception are interrupted when a non-active SCG is configured for the UE, which is standardized in Rel-17 as a way to reduce UE energy consumption in response to dynamic reduction of data traffic. Since the BSR is one of the SCG transmissions to be interrupted, it is unclear how the UE should report to the network the arrival of UL data (and data volume) related to the SCG bearer or split bearer. In this situation, it is also unclear how scheduling should work on the SCG and / or MCG, compared to conventional techniques where both the MCG MAC entity and the SCG MAC entity may be aware of the data volume by the BSR via the MCG and / or SCG.

[0101] Accordingly, embodiments of the present disclosure provide novel, flexible, and efficient techniques for a UE configured for MR-DC with MCG and SCG in a wireless network (e.g., NG-RAN). When the SCG is deactivated, the UE can report UL data that needs to be transmitted via the SCG in a message to the network, e.g., via the MCG or the SCG. The UE can send a report (e.g., BSR) in a MAC CE or an RRC message.

[0102] In various embodiments, the UE can determine that UL data that needs to be transmitted on a DRB associated with the SCG has become available. The UE can determine the SCG state, such as the SCG deactivated state or the SCG activated state. Based on the determined SCG state, the DRB type associated with the available UL data, and / or the available UL data volume, the UE can determine a method for calculating the UL data volume and / or a procedure for reporting the calculated UL data volume to the network. In some variations, when reporting the UL data volume via the SCG, both the UE and the network can consider the SCG to be activated.

[0103] In various embodiments, the network can receive a BSR from the UE and determine to activate the deactivated SCG based on the BSR content. For example, an MN that receives a BSR from the UE can forward the BSR to the SN under some conditions, such as when the SCG is deactivated. This forwarding enables the SN to be aware of the available UL data available at the UE, which may be related to SCG bearers and / or SN-terminated split bearers. In response (e.g., in response to the forwarded UE BSR), the SN can determine to activate the deactivated SCG and indicate this activation status to the MN.

[0104] Embodiments can provide various benefits, advantages, and / or solutions to the problems described herein. For example, an embodiment, the SN of the UE, can notice that the deactivated SCG of the UE has available UL data related to the SCG bearer and / or split bearer. This enables the SN to activate the deactivated SCG in a timely manner, thereby avoiding delays in receiving the available UL data. By avoiding such delays, the performance of the UE application that generates the available UL data can be improved, which ultimately improves the user experience.

[0105] 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.

[0106] In the following, embodiments are described with respect to the SCG that is interrupted for a UE with DC configured. However, the same principle can be applied to the MCG that is interrupted for a UE with DC configured.

[0107] 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 a MAC CE based on a UL grant received from the network. This also includes cases where the UE has to obtain a UL grant by transmitting an SR on a valid PUCCH resource or by initiating a random access procedure without a valid PUCCH resource, i.e., when there is no UL grant for the transmission of a BSR.

[0108] 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 and 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.

[0109] In the following, various embodiments are described in the context of "groups", such as "the first group", "the second group", etc. However, those skilled in the art will recognize that these groups are not mutually exclusive and that features described as being part of one group of embodiments may also be part of one or more other groups of embodiments.

[0110] In the first group of embodiments, the UE determines the availability of UL data for which a BSR should be triggered in the SCG. The UE PDCP and RLC layers calculate the available UL data volume for the SCG. The UE then creates a BSR indicating the available UL data volume for the SCG and transmits the BSR in the SCG. In this first group, the UE transmits a BSR even when the SCG is deactivated. This generally requires the UE to maintain time alignment at the PSCell.

[0111] In an alternative form, the UE sends an SR to obtain a valid UL grant that enables the UE to send a BSR if necessary. In another alternative form, even in the SCG deactivated state, a semi-static UL grant (e.g., a configured grant) can be set for the UE for BSR transmission. After BSR transmission, the UE maintains the SCG state (activated or deactivated) prior to BSR transmission unless the network changes the SCG state, e.g., via an RRCReconfiguration message or MAC CE. In a variant, if the SCG was deactivated prior to BSR transmission, the UE considers the SCG to be temporarily activated for BSR transmission and then considers the SCG to be deactivated again.

[0112] When there is UL data available while the SCG is deactivated, the UE PDCP layer instructs the UE MCG and / or SCG MAC entities of the UL data volume according to a predefined set of rules that take into account the type of bearer associated with the available UL data, the available UL data volume relative to a threshold, whether the MCG and / or SCG is set as the primary path, whether PDCP duplication is set, etc.

[0113] When the BSR is triggered in the SCG MAC entity (e.g., according to pre - defined and / or configured rules), the SCG MAC entity can send the BSR to the SN without necessarily activating the SCG. This can be done, for example, when the UE requests UL data transmission in the de - activated SCG (e.g., in the PSCell) by sending an SR on the PUCCH or, if the SCG MAC entity does not have a valid PUCCH resource configured for SR, by random access. In one variant, regardless of whether the SCG is activated or de - activated, the SCG MAC entity uses the same rules for triggering the BSR and the same procedures and configured parameters for SR and (if necessary) initial random access.

[0114] In other words, when the MAC entity of the SCG is de - activated, the associated BSR state variables remain the same. These include the timer value for the periodic BSR (e.g., periodicBSR - Timer), the value of the re - transmission BSR timer (e.g., retxBSR - Timer), logicalChannelSR - DelayTimerApplied, and logicalChannelSR - DelayTimer when they are running. Thus, if any of these timers are running, they are not stopped when the SCG is de - activated. This simplifies the behavior of the SCG MAC entity while the SCG is de - activated.

[0115] The benefits of the first group include lower complexity and the fact that the SCG does not need to be activated only for transmitting the BSR. Further, the PDCP layer (for a given bearer having a related SCG, for example) does not need to be aware that the SCG (or another cell group) related to the bearer has been deactivated. Further, the SCG MAC entity can maintain BSR behavior while the SCG is deactivated. This means that the UE does not transition the SCG to the active state just because the UE needs to transmit a BSR; instead, for that purpose, the UE needs to perform an SR and read the PDCCH to obtain a UL grant for BSR transmission.

[0116] When the SCG is deactivated when the network (e.g., the MN) receives a BSR, it is up to the network to determine whether to perform SCG activation. FIG. 17 is a signal flow diagram between the UE, the MN, and the SN showing a first option according to some embodiments. First, the UE receives an indication from the MN that the SCG is to be deactivated and deactivates the SCG accordingly. Thereafter, a BSR is triggered for the SCG MAC entity. If it is necessary to obtain a valid UL grant to transmit the BSR, the UE sends an SR to the SN and receives a UL grant in response. The UE maintains the deactivated SCG while transmitting the BSR to the SN. When the SN receives the BSR, the SN decides to transition the SCG to the active state and instructs the MN (e.g., via Xn interface signaling) that the SCG should be activated. Thereafter, the MN can instruct the UE to activate the SCG, and the UE activates the SCG accordingly.

[0117] Figure 18 is a signal flow diagram between a UE, an MN, and an SN showing a second option according to some embodiments. Some operations in Figure 18 are equivalent to the corresponding operations in Figure 17 and, for the sake of brevity, these are not described. When the SN receives the SR of the UE, the SN determines to activate the SCG and includes an indication thereof in the UL grant in response to the SR (e.g., a MAC CE including an indication that the SCG should be activated). Accordingly, the UE activates the SCG accordingly upon receiving this indication. If this indication is not included in the UL grant, the SCG remains deactivated. Further, the SN can send an indication of SCG activation to the MN.

[0118] In the first group, the BSR can be triggered in the SCG MAC entity of the UE while the SCG is deactivated by any of the following events. ● UL data becomes available to the MAC entity for a logical channel belonging to an LCG, and ○ this UL data belongs to a logical channel having a priority higher than the priority of any logical channel containing available UL data belonging to any LCG, or ○ none of the logical channels belonging to the LCG contains available UL data, in which case the BSR is a "regular BSR", ● UL resources are allocated and the number of padding bits is equal to or greater than the size of the BSR MAC CE + its sub-header, in which case the BSR is a "padding BSR", ● the retxBSR-Timer expires and at least one of the logical channels belonging to the LCG contains UL data, in which case the BSR is a "regular BSR", as well as ● the periodicBSR-Timer expires, in which case the BSR is a "regular BSR".

[0119] In the second group of embodiments, the UE determines the availability of UL data for which a BSR should be triggered in the SCG. The UE PDCP and RLC layers calculate the available UL data volume for the SCG. Then, the UE determines the current SCG state, i.e., activation or deactivation. When the current SCG state is deactivated, the UE activates the SCG. In two alternative forms, upon triggering a BSR, SCG activation can be performed by the MAC layer either by initiating a random access procedure in the SCG or by transmitting an SR in the SCG.

[0120] When the current SCG state is activated (including that due to the above UE activation), the UE creates a BSR indicating the available UL data volume for the SCG and transmits the BSR in the SCG. After BSR transmission, the UE assumes that the SCG is activated and keeps the SCG activated unless the network explicitly deactivates the SCG, such as by sending an RRC message (e.g., RRCReconfiguration) to the UE or by sending a MAC CE indicating SCG deactivation.

[0121] FIG. 19 is a signal flow diagram between the UE, MN, and SN, showing some embodiments of the second group. The main difference from the first group is that the UE activates the SCG before sending a BSR (and optionally before an SR), rather than after an SR (FIG. 18) or after a BSR (FIG. 17). Other behaviors can be substantially the same as those of the first group.

[0122] When there is UL data available while the SCG is deactivated, the UE PDCP layer instructs the UE MCG and / or SCG MAC entity of the UL data volume according to a set of predefined rules that consider the type of bearer related to the available UL data, the available UL data volume against a threshold, whether the MCG and / or SCG is set as the primary path, whether PDCP duplication is set, etc.

[0123] In various embodiments, the data volume threshold for reporting via the SCG may be the same or different for the deactivated SCG and the activated SCG. One possible advantage of defining different thresholds may be that the network may only desire a BSR for the deactivated SCG when there is a significant amount of data. In such a case, the threshold for transmitting a BSR in the deactivated state may be set higher than that in the activated state.

[0124] In some embodiments, only a configurable subset of LCH (and / or LCG) can trigger an SR when the SCG is deactivated. For example, the traffic related to this subset may be delay intolerant (e.g., URLLC), while the traffic in the remaining LCH (and / or LCG) may be delay tolerant (e.g., UE application layer logging messages, application layer software updates, etc.). In this setting, additional parameters, such as an optional sr-AllowedInDeactivated field with a "true" enumeration value indicating the SR enabled for LCH when the SCG is deactivated, are added to the existing RRC LogicalChannelConfig IE. If the sr-AllowedInDeactivated field does not exist, SR is not enabled for LCH when the SCG is deactivated. This behavior may also be specified by the following procedure description, which may be part of the relevant 3GPP specifications. ***Start of the proposed 3GPP specification text*** 2> When a regular BSR is triggered and the logicalChannelSR - DelayTimer is not running, 3> When the MAC entity is deactivated and a regular BSR is triggered for a logical channel for which sr - AllowedInDeactivated is set, 4> Trigger a scheduling request ***End of the proposed 3GPP specification text***

[0125] One benefit of the second group is the reduced complexity since the SCG will always be activated when the UE performs UL transmission. For example, the UE can monitor the PDCCH for a UL grant for transmitting a BSR and for a UL grant for re - transmitting the BSR in case the initial BSR transmission cannot be correctly decoded by the network. This can be interpreted as a requirement for UL - triggered activation and / or for UL - triggered activation.

[0126] In a variation of the procedure shown in Figure 19, the arrival of UL data for transmission (e.g., a BSR for an LCG related to the SCG) triggers the UE to send a SCG activation request message (e.g., RRCActivationRequest, a MAC CE indicating a request for SCG activation, etc.) to the network. The UE waits for a response from the network before it can consider the SCG to be activated. Upon receiving that response, the UE can send an SR for the UL data in the manner shown in Figure 19.

[0127] Figure 20 is a signal flow diagram between a UE, an MN, and an SN, showing another embodiment of the second group. The main difference from Figure 19 is that when the SCG is activated in response to a triggered BSR, the UE starts a timer. The timer duration is set as part of the BSR configuration and / or can be provided in a message indication that the SCG should be deactivated. While the timer is running, the UE considers the SCG to be activated, and when the timer expires, the UE considers the SCG to be deactivated. While the timer is running, the UE monitors the PDCCH of the activated SCG (e.g., the PDCCH of the PSCell, CORESET, and / or any other DL control channel resource) that provides an opportunity for the SN to schedule DL transmissions to the UE. Two variations of this approach are described below.

[0128] Figure 21 is a signal flow diagram between a UE, an MN, and an SN, showing one of these variations. In Figure 21, upon receiving a BSR, the SN determines to permanently activate the SCG while the UE timer is running. The SN sends an indication to the UE that the SCG should be activated, which causes the UE to stop the timer and keep the SCG activated (at least until a subsequent event or message causes deactivation).

[0129] Figure 22 is a signal flow diagram between a UE, an MN, and an SN, showing another of these variations. In Figure 22, upon receiving a BSR, the SN determines to permanently deactivate the SCG while the UE timer is running. The SN sends an indication to the UE that the SCG should be deactivated, which causes the UE to stop the timer and keep the SCG deactivated (at least until a subsequent event or message causes activation).

[0130] In a second group of embodiments, the BSR may be triggered at the UE's SCG MAC entity while the SCG is deactivated by any of the events described above in the description of the first group.

[0131] In some embodiments, the triggering events for the BSR at the MAC entity of the deactivated SCG may be limited to a subset of those described above and / or a subset of the triggering events for the activated SCG. In one variation, the triggering events for the BSR at the MAC entity of the SCG include only the event that UL data becomes available for the SCG. As an example, one or both of the event that the periodicBSR - Timer expires and / or the event that the retxBSR - Timer expires may be excluded from triggering the BSR at the SCG MAC entity when the SCG is deactivated. This exclusion will avoid the UE transmitting a periodic BSR for the SCG when there is no UL data available for the SCG - related bearer. In such a case, the BSR for the deactivated SCG is triggered only when there is UL data available for the SCG, which in that case is a common trigger for activating the SCG.

[0132] In some embodiments, the retxBSR - Timer and / or the periodicBSR - Timer may be stopped for the SCG MAC entity when the UE deactivates the SCG. These timers may be restarted when the UE re - activates the SCG. In other embodiments, the retxBSR - Timer and / or the periodicBSR - Timer may be suspended by the SCG MAC entity when the UE deactivates the SCG. These timers may be resumed when the UE re - activates the SCG.

[0133] In some embodiments, the UE can have a separate BSR configuration for the SCG MAC entity for use while the SCG is in the deactivated state. This separate configuration can include different BSR triggering events compared to the BSR configuration for use in the SCG activated state. In one example, the network can provide separate BSR configurations for two SCG states, and the UE can apply the BSR configuration corresponding to the actual SCG state at any time. In another example, when the network moves the SCG to the deactivated state, it sets a first BSR configuration for the SCG MAC entity, and then, optionally, when moving the SCG to the activated state, it re-sets a second BSR configuration for the SCG MAC entity. In this latter example, the different triggering events are achieved by the network implementation.

[0134] In a third group of embodiments, the UE determines the availability of UL data for which a BSR should be triggered in the SCG. The UE PDCP and RLC layers calculate the available UL data volume for the SCG. The UE then determines the current SCG state, i.e., activated or deactivated. When the current SCG state is activated, the UE creates a BSR indicating the available UL data volume for the SCG and transmits the BSR in the SCG. Otherwise, when the current SCG state is deactivated, the UE creates a BSR indicating the available UL data volume for the SCG and transmits the BSR in the MCG.

[0135] In the embodiments of the third group, the BSR can be triggered in the UE's SCG MAC entity while the SCG is deactivated by any of the events described above in the description of the first group.

[0136] In some embodiments, the UE creates a BSR MAC CE for the SCG and encapsulates this MAC CE in another MAC CE to be transmitted in the MCG. In other embodiments, the UE creates a new BSR MAC CE to be transmitted in the MCG that includes the BSR for the SCG. In other embodiments, an existing BSR MAC CE to be transmitted in the MCG can be extended and / or augmented to include the LCG ID for the UE's SCG MAC entity. In other embodiments, the available UL data volume for split bearers can be reported only in the BSR from the MCG MAC entity.

[0137] In a third group of embodiments, when the SCG is deactivated, the SCG MAC entity does not send the triggered BSR to the SCG (e.g., via the PSCell), rather, the BSR is sent instead via the active MCG. In some embodiments, the SCG BSR transmission via the MCG can be triggered based on one or more rules and / or conditions. For example, the MCG transmission can be used if it is the only configured path for UL split bearers and / or for general SCG bearers. One way to implement this is for the SCG MAC entity to indicate to the MCG MAC entity that the BSR needs to be sent for the deactivated SCG. The SCG MAC entity can generate the BSR MAC CE according to the desired format for transmission and provide the BSR MAC CE to the MCG MAC entity, and the MCG MAC entity can encapsulate the BSR MAC CE as an SCG MAC CE (including an indication that it is the SCG MAC CE to be processed at the SN). The MCG MAC CE entity can send the encapsulated SCG MAC CE via the PCell.

[0138] In some embodiments, the BSR may be transmitted via the MCG regardless of UE configurations, such as UL split bearers, SCG bearers, BSR configurations, PDCP configurations regarding data volume, etc. Thus, when the BSR is triggered for the SCG (e.g., based on predefined and / or configured rules) and / or the PDCP instructs the SCG about the data volume, the SCG does not transmit the BSR via the SCG (e.g., does not send a scheduling request on the UL).

[0139] In some embodiments, after the SCG MAC entity instructs the MCG MAC entity that the BSR needs to be sent for the deactivated SCG BSR (and provides the necessary information regarding, e.g., the format, LCH / LCG having the data to be sent), the SCG MAC entity considers the BSR to be cancelled. In other embodiments, the SCG BSR is considered to be cancelled only when receiving a UL grant from the SCG or when the SCG is network-activated. In some embodiments, a timer is introduced to control how often the SCG can instruct the MCG MAC entity about the BSR, e.g., every t subframes.

[0140] In some embodiments, forwarding the BSR for the SCG MAC entity by the MCG MAC entity may be restricted to only the regular BSR and / or the periodic BSR. In such a case, since the SCG is deactivated without UL resources allocated for UL transmission, the padding BSR is neither triggered nor forwarded.

[0141] In other embodiments, forwarding the BSR for the SCG MAC entity by the MCG MAC entity may be restricted to only the regular BSR. This restriction is based on the argument that only the regular BSR can trigger the SR when there is no UL resource for data transmission, and the deactivated SCG is equivalent to having no UL resource for data transmission. When the periodic BSR is excluded, the SCG configuration related to the periodic BSR reporting can be simplified, and the unnecessary indication of the BSR MAC CE of the SCG via the MCG can be reduced and / or avoided.

[0142] The operation of the example where forwarding applies to the regular BSR and includes only the logical channel that triggered the BSR (only one LCH is reported) may be specified by the following procedure description, which may be part of the relevant 3GPP specifications, such as those in section 5.4.5 (NR MAC) of 3GPP TS38.321. ***Start of proposed 3GPP specification text*** The MAC entity shall do the following. 1> If it is determined that the buffer status report procedure has triggered at least one BSR and has not been cancelled, 2> If this MAC entity has been deactivated and the regular BSR has been triggered, 3> Indicate to the other MAC entity the logical channel that triggered the BSR and the buffer status. 2> Otherwise, if the UL-SCH resource is available for a new transmission and the UL-SCH resource can be adapted to the BSR MAC CE + its sub-header as a result of logical channel prioritization, ***End of proposed 3GPP specification text***

[0143] In some embodiments, receiving a BSR from the SCG MAC entity for a deactivated SCG causes the MCG to construct an SCG BSR MAC CE. For example, the SCG BSR MAC CE may be identified by the MCG MAC entity using a different LCID or (e)LCID than that used in existing BSR MAC CEs. On the other hand, such an SCG BSR MAC CE can have the same LCH priority as existing BSR MAC CEs (except for the BSR for padding) in the context of the resource allocation procedure for new data transmission as specified in 3GPP TS 38.321, section 5.4.3.1.1.

[0144] In some embodiments, only a configurable subset of LCHs (and / or LCGs) can trigger a BSR MAC CE when the SCG is deactivated. For example, the traffic related to this subset can be delay intolerant (e.g., URLLC), while the traffic in the remaining LCHs (and / or LCGs) can be delay tolerant (e.g., UE application layer logging messages, application layer software updates, etc.). In this setting, additional parameters, such as an optional bsr-AllowedInDeactivated field with a "true" enumerated value indicating the BSR MAC CE enabled for LCH when the SCG is deactivated, are added to the existing RRC LogicalChannelConfig IE. If the bsr-AllowedInDeactivated field does not exist, the BSR MAC CE is not enabled for LCH when the SCG is deactivated. This behavior can also be specified by the following procedure description, which may be part of the relevant 3GPP specifications. ***Start of proposed 3GPP specification text*** 3> If bsr-AllowedInDeactivated is set for a logical channel, indicate the logical channel that triggered the BSR and the buffer status to other MAC entities. ***End of the proposed 3GPP specification text***

[0145] In other embodiments, the reception of the SCG BSR MAC CE from the SCG MAC entity in the MSG MAC entity enables the UE to trigger an SR when there is no UL-SCH source available for a new transmission in the MCG. In this way, the SCG BSR MAC CE can be treated in the same way as the arrival of new UL data by the MCG MAC entity. This is different from other MAC CEs (e.g., configured grant confirmations, PHRs, etc.) that do not conventionally trigger an SR for UL resources. The operation of these embodiments can be specified by the following procedure descriptions, which can be part of the relevant 3GPP specifications, such as those in Section 5.4.5 (NR MAC) of 3GPP TS38.321. ***Start of the proposed 3GPP specification text*** 2> If the SCG BSR is triggered or the regular BSR is triggered and the logicalChannelSR-DelayTimer is not running, 3> If there are no UL-SCH resources available for a new transmission, or 3> If one or more configured uplink grants are set for the MAC entity and the regular BSR is triggered for a logical channel for which the logicalChannelSR-Mask is set to false, or 3> If the UL-SCH resources available for a new transmission do not meet the LCP mapping restrictions (see Section 5.4.3.1) set for the logical channel that triggered the BSR, 4> Trigger a scheduling request. ***End of the proposed 3GPP specification text***

[0146] FIG. 23 is a signal flow diagram between a UE, an MN, and an SN, showing some embodiments of a third group. When receiving a BSR from a UE having a deactivated SCG, the MN determines whether to forward the BSR (or information derived from the BSR, such as an indication) to the SN associated with the deactivated SCG. The determination may be based on whether the BSR includes information related to the deactivated SCG, information related to the SN-terminated bearer (e.g., when data is reported for the associated LCH and / or LCG), and / or the available UL data volume relative to a threshold. For example, the BSR (or more generally, information regarding the BSR) to be forwarded may be transmitted on the Xn interface via either the user plane or the control plane (e.g., as a signaling message). When receiving SCG BSR information from the MN, the SN determines whether the SN should activate the SCG. If the SN determines to activate the SCG, the SN sends an indication to the MN, and the MN sends an indication to the UE that the SCG should be activated. Upon reception, the UE considers the SCG to be activated.

[0147] In a variant, the MN can activate the SCG in response to receiving a BSR related to the deactivated SCG. The MN can inform the SN of this SCG activation, and then the SN can send an indication directly to the UE, rather than indirectly via the MN.

[0148] Conventionally, for a UE in MR-DC, the PDCP layer controls whether to indicate the data volume to the MCG and / or SCG for the BSR that should be transmitted on the MCG and / or SCG, in accordance with the rule(s) defined in the 3GPP specification. However, BSR transmission and related settings (e.g., retransmission timer, periodic timer, etc.) are performed for each cell group, i.e., each of the MCG and SCG has its own BSR setting.

[0149] The embodiments described above relate to modifications and / or extensions in the MAC layer, while other embodiments involve modifications and / or extensions in the PDCP layer when the SCG is deactivated. Some of these embodiments facilitate notifying the UE PDCP entity that the SCG is deactivated, and based on that notification, the UE PDCP entity determines whether to provide data volume to the primary path (e.g., SCG).

[0150] Generally, the SCG BSR report via the MCG may be conditional on whether the SCG is set as the primary path and / or the rule that the data volume should be provided only to the primary path. In other words, if the data volume exceeds a threshold and should be indicated to both the MCG MAC entity and the SCG MAC entity, the procedures described here are not triggered.

[0151] In some embodiments, the MN receives a BSR related to the SCG from the UE and determines to forward it to the SN only when at least one condition is satisfied, e.g., when the data volume exceeds a predetermined threshold (set by, e.g., the MN and / or the SN).

[0152] In some embodiments, the BSR is not transmitted via the SCG when the SCG is deactivated, regardless of other rules for transmission via the SCG (e.g., whether the SCG is the primary path and / or whether the data volume exceeds a data volume threshold). Thus, only the MN receives the SCG BSR and determines whether to activate the SCG upon receipt. Alternatively, upon receipt of the SCG BSR, the MN can instruct the SN of certain SCG data activity / traffic, from which the SN can determine whether to activate the SCG. For example, either of these decisions can be based on whether the BSR indicates a data volume above a certain threshold for the LCG associated with the SCG.

[0153] In some embodiments, if the SCG is configured as the primary path and the SCG is deactivated, the UE can ignore other rules (e.g., data volume relative to a threshold) for transmitting data on both the primary and secondary paths as defined in the PDCP layer and instead transmit the BSR via the MCG. In a variation, the network can reconfigure the MCG as the primary path when the SCG is deactivated (if not already so), and thus the BSR will be transmitted via the MCG / primary path while the SCG is deactivated.

[0154] In some embodiments, assuming the SCG is deactivated, the UE SCG MAC entity stops performing BSR-related actions. For example, upon receiving an indication to deactivate the SCG, the UE stops maintaining BSR-related state variables such as stopping the timer for periodic BSR (e.g., periodicBSR-Timer) if it is running, stopping the retransmission BSR timer (e.g., retxBSR-Timer), stopping logicalChannelSR-DelayTimerApplied if it is running, and stopping logicalChannelSR-DelayTimer if it is running.

[0155] In a fourth group of embodiments, the UE determines the availability of UL data for which a BSR should be triggered in the SCG. The UE PDCP and RLC layers calculate the available UL data volume for the SCG. The UE then determines the current SCG state, i.e., activation or deactivation. When the current SCG state is activation, the UE creates a BSR indicating the available UL data volume for the SCG and transmits the BSR in the SCG. Otherwise, when the current SCG state is deactivation, the UE creates an RRC message indicating the available UL data volume for the SCG and transmits the RRC message in the MCG. For example, the UEAssistanceInformation RRC message can be used for this purpose.

[0156] In some embodiments, the UE PDCP entity does not provide the data volume to the SCG MAC entity for the deactivated SCG regardless of whether other rules and / or conditions for instructing the data volume to the SCG (e.g., the SCG is the primary path, the data volume is greater than a threshold, etc.) are satisfied. In the case of a deactivated SCG, the PDCP layer instructs the data volume for the MCG MAC entity, which prevents the SCG MAC entity from triggering a BSR. The UE PDCP entity may provide the data volume to the SCG MAC entity for the activated SCG, optionally in conjunction with the satisfaction of other rules and / or conditions for reporting the data volume (described below).

[0157] In these embodiments, the PDCP entity must be informed when a cell group (e.g., SCG) becomes deactivated. For example, if the deactivation is performed in the MAC layer (via a deactivated MAC CE), the MAC layer instructs the upper layer that the cell group (e.g., SCG) has been deactivated. In other cases, the MAC layer instructs the upper layer that the cell group (e.g., SCG) has been activated. As another example, if the deactivation is performed in the RRC layer (e.g., via a deactivated field or IE), the RRC layer instructs the lower layer that the cell group (e.g., SCG) has been deactivated. In other cases, the RRC layer instructs the lower layer that the cell group (e.g., SCG) has been activated.

[0158] In another embodiment, the UE PDCP entity does not provide the data volume to the SCG MAC entity for the deactivated SCG if the data volume is directed (or can be directed) to the MAC entity of another cell group according to various predefined conditions and / or rules. In the example of a split DRB, if the PDCP entity is considered to provide the data volume to both MAC entities according to some predefined rules (e.g., a calculated data volume exceeding a set threshold), when the SCG MAC is deactivated, the PDCP entity only provides the data volume to the MCG MAC entity. In other words, the PDCP entity does not provide the data volume to the SCG MAC entity of the deactivated SCG as long as the PDCP entity can instead report the data volume to the MCG MAC entity. Based on this information, the MN can determine whether to activate the SCG. For example, a predefined rule can state that the MN should activate the SCG if the indicated data volume exceeds a certain threshold.

[0159] In another example of a split DRB, if the PDCP entity is considered to provide the data volume only to the SCG MAC entity according to some predefined rules (e.g., the SCG MAC is set as the primary path and the calculated data volume is below the set threshold), the PDCP entity provides the UL data volume to the MCG MAC entity instead when the SCG is deactivated.

[0160] In another example of the SCG DRB, when the SCG is deactivated, the UE reports the BSR of the (one or more) logical channels related to the SCG DRB via the MCG BSR CE. This can be achieved, for example, by adding a new field to the MCG BSR CE to also carry the buffer status for the logical channels of the SCG, as described above.

[0161] In some embodiments, when the PDCP entity does not provide the data volume to the SCG MAC entity of the deactivated SCG, but would have provided the data volume to the SCG MAC entity if the SCG had been active, the UE can send an RRC message to the MN via the MCG indicating that there is available UL data volume for which a BSR should have been triggered on the deactivated SCG. For example, the UE can send this RRC message when the SCG is configured as the primary path and the condition for providing the data volume to the SCG MAC entity indicates that the data volume should be provided only to the primary path. The message can include the UL data volume that would have been transmitted together with the BSR via the SCG and / or the MAC CE BSR generated by the UE's SCG (e.g., included in the RRC message as a container). On the other hand, if the data volume exceeds a threshold and should be indicated to both the MCG MAC entity and the SCG MAC entity, the UE does not send the RRC message.

[0162] In another embodiment, the PDCP entity does not provide data volume to the SCG MAC entity of the deactivated SCG, but if the SCG were to be activated, the PDCP entity would have provided data volume to both MAC entities as it should have been. When there is data for the SCG MAC entity and / or the SCG should be activated, the PDCP entity can instruct the MCG MAC entity. For example, the PDCP entity can send a PDCP PDU via the MCG MAC entity to instruct the MN that there is UL data available for the SCG.

[0163] In some variations, the instruction can be sent as a separate PDCP control PDU or as one or more parameters in another PDCP control PDU (e.g., in the header and / or within the PDU). In other variations, the instruction can be sent as one or more parameters in a PDCP data PDU (e.g., in the header and / or within the PDU). The instruction regarding UL data available for the SCG can also include information regarding the (one or more) radio bearers for which the data is available and the amount of data available.

[0164] The embodiments described above can be further illustrated with reference to FIGS. 24 - 26, which each show an exemplary method (e.g., procedure) implemented by a UE, a first node, and a second node. In other words, the various features of the operations described below correspond to the various embodiments described above. These exemplary methods can be used collaboratively to provide various exemplary benefits and / or advantages. FIGS. 24 - 26 show specific blocks in a specific order, but the operations of each method can be implemented in an order different from that shown, combined with and / or divided into blocks having functions different from those shown. Optional blocks or operations are indicated by dashed lines.

[0165] In particular, FIG. 24 (including FIGS. 24A-24B) shows a flowchart of an exemplary method (e.g., procedure) for a UE with MCG and SCG configured in a wireless network according to various embodiments of the present disclosure. The exemplary method may be implemented by a UE (e.g., a wireless device, an IoT device, a modem, etc., or components thereof) as described elsewhere herein.

[0166] The exemplary method may include the operation of block 2420, where the UE can determine the availability of UL data for transmission via the SCG while the SCG is in the deactivated state. The exemplary method may also include the operation of block 2435, where the UE can calculate the available UL data volume. The exemplary method may also include the operation of block 2440, where the UE ● the SCG in the deactivated state, ● the SCG after activation, ● the SCG after receiving an indication from the wireless network that the SCG should be activated, and ● the MCG can transmit an indication of the available UL data volume to the wireless network via one or more of them.

[0167] In some embodiments, an exemplary method may also include the operations of blocks 2410 - 2415, where the UE can receive from a first node configured to provide an MCG a first indication that the SCG should be deactivated, and in response to the first indication, deactivate the SCG. In some embodiments, deactivating the SCG (e.g., at block 2415) can include the operation of sub - block 2416, where the UE can stop or suspend one or more timers associated with the periodic reporting of the available UL data volume related to the SCG. As described above, this operation can avoid periodic BSRs (especially without actual UL data to report) while the SCG is in the deactivated state.

[0168] In some embodiments, an indication of the available UL data volume is one of an indication that UL data is available for transmission via the SCG, an indication of the volume of UL data available for transmission via the SCG, or an indication that the SCG should be activated.

[0169] In some embodiments, transmitting an indication of the available UL data volume (e.g., at block 2440) can include the operations of sub - blocks 2443 and 2445. In sub - block 2443, the UE can receive a UL grant for BSR transmission from a second node configured to provide the SCG. In sub - block 2445, the UE can use the received UL grant to transmit, via the SCG, a BSR indicating the available UL data volume to the second node.

[0170] In some of these embodiments, transmitting an indication of the available UL data volume (e.g., at block 2440) can also include the operation of sub-block 2442, where the UE can send a scheduling request (SR) to a second node. A UL grant can be received in response to the SR, ● The SR and BSR are transmitted while the SCG is in the deactivated state (e.g., as shown in FIG. 17), ● The SR is transmitted while the SCG is in the deactivated state, and the BSR is transmitted after the SCG is activated (e.g., as shown in FIG. 18), or ● The SR and BSR are transmitted after the SCG is activated (e.g., as shown in FIGS. 19 - 22), and one of these is applied.

[0171] In some variations, the UL grant can include a second indication that the SCG should be activated, and transmitting an indication of the available UL data volume can also include the operation of sub-block 2444, where the UE can activate the SCG in response to the second indication and before transmitting the BSR (e.g., at block 2445).

[0172] In other ones of these embodiments, the UL grant can be a configured UL grant for use while the SCG is in the deactivated state. In such a case, the configured UL grant can be received from the second node before the SCG is deactivated.

[0173] In some embodiments, an exemplary method can include the operation of block 2425, where the UE can activate the SCG based on determining the availability of UL data (e.g., at block 2420). In these embodiments, the exemplary method can also include the operation of block 2430, where the UE can start a timer in response to activating the SCG. Examples of such embodiments are shown in FIGS. 20-22. In some of these embodiments, the exemplary method can also include the operation of block 2470, where the UE can deactivate the SCG when the timer expires after reporting the available UL data volume.

[0174] In some of these embodiments, the exemplary method can also include the operations of blocks 2450-2460. At block 2450, the UE can receive from a second node configured to provide the SCG, ● a third indication that the SCG should be activated (shown in FIG. 21), or ● a fourth indication that the SCG should be deactivated (shown in FIG. 22) of which one can be received.

[0175] At block 2460, the UE can stop the timer in response to the third or fourth indication.

[0176] In some embodiments, transmitting an indication of the available UL data volume (e.g., at block 2440) can include the operation of sub-block 2446, where the UE can transmit an indication of the available UL data volume in one or more of a MAC BSR, an RRC message, or a PDCP PDU to a first node (e.g., the MN of the UE) configured to provide the MCG, in one of the following. An example is shown by FIG. 23. In some variations, the RRC message can be a UEAssistanceInformation message. In other variations, the MAC BSR can be transmitted using the RRC message as a container.

[0177] In some of these embodiments, the exemplary method can also include the operation of sub-blocks 2480-2490, where the UE can receive from the first node, in response to the indication of the available UL data volume, a fifth indication that the SCG should be activated, and activate the SCG in response to the fifth indication.

[0178] In various embodiments, calculating the available UL data volume (e.g., at block 2435) can be ● based on one or more of the type of bearer associated with the available UL data, ● whether the MCG or SCG is configured as the PDCP primary path, ● whether PDCP duplication is enabled and the like.

[0179] In some embodiments, transmitting an indication of the available UL data volume (e.g., at block 2440) may include and / or be based on the operation of sub-block 2441, where the UE determines that the available UL data volume is greater than a first threshold applicable when the SCG is in a deactivated state. In some of these embodiments, the first threshold may be different from a second threshold applicable when the SCG is in an activated state.

[0180] Further, FIG. 25 shows a flow diagram of an exemplary method (e.g., procedure) for a second node configured to provide an SCG to a UE in a wireless network, also having an MCG configured, according to various embodiments of the present disclosure. The exemplary method may be implemented by a network node (e.g., a base station, eNB, gNB, ng-eNB, en-gNB, etc., or components thereof) as described elsewhere herein.

[0181] The exemplary method can include the operation of block 2510, where the second node can receive from the UE an indication of the available UL data volume for transmission by the UE via the SCG. The available UL data volume is determined by the UE while the SCG is in a deactivated state. The indication can be received via one or more of ● the SCG in a deactivated state, and ● the SCG after activation of the SCG by the UE, and ● the SCG after sending an indication to the UE that the SCG should be activated, and ● the first node of the wireless network configured to provide the MCG.

[0182] ​In some embodiments, the indication of the available data volume is one of an indication that UL data is available for transmission via the SCG, an indication of the volume of UL data available for transmission via the SCG, or an indication that the SCG should be activated.

[0183] In various embodiments, the indicated volume of UL data available for transmission via the SCG is ● related to the type of bearer for the available UL data, and ● whether the MCG or SCG is configured as the PDCP primary path, and ● whether PDCP duplication is enabled based on one or more of the above.

[0184] In some embodiments, the indicated volume of UL data available for transmission via the SCG can be greater than a first threshold applicable when the SCG is in the deactivated state. In such embodiments, the first threshold can be different from a second threshold applicable when the SCG is in the activated state.

[0185] In some embodiments, receiving the indication (e.g., at block 2510) can include the operations of sub-blocks 2512 - 2513, where the second node can provide the UE with a UL grant for transmission of a BSR and receive from the UE via the SCG, in accordance with the UL grant, a BSR indicating the volume of UL data available for transmission via the SCG.

[0186] In some of these embodiments, receiving the indication (e.g., at block 2510) can also include the operation of sub-block 2511, where the second node can receive an SR from the UE. The UL grant can be provided in response to the SR, ● (e.g., as shown in Figure 17) SR and BSR are received while the SCG is in the deactivated state, ● (e.g., as shown in Figure 18) SR is received while the SCG is in the deactivated state, and BSR is received after the UE activates the SCG, or ● (e.g., as shown in Figures 19 - 22) SR and BSR are received after the UE activates the SCG, One of them is applied.

[0187] In other ones of these embodiments, the UL grant is a configured UL grant for use while the SCG is in the deactivated state. Moreover, the configured UL grant is provided to the UE before or together with the indication that the SCG should be deactivated.

[0188] In some embodiments, the exemplary method can also include the operation of block 2520, where the second node, in response to an indication of the available UL data volume (received, for example, at block 2510), sends to the UE ● A third indication that the SCG should be activated (shown in Figure 21), or ● A fourth indication that the SCG should be deactivated (shown in Figure 22) One of them.

[0189] In some embodiments, the exemplary method can also include the operation of block 2530, where the second node, in response to an indication of the available UL data volume (received, for example, at block 2510), sends to the first node ● A fifth indication that the SCG will be activated (shown in Figure 21), or ● A sixth indication that the SCG will be deactivated (shown in Figure 22) One of them.

[0190] In some embodiments, an indication of the available UL data volume may be received from a first node. In such embodiments, an exemplary method may also include the operation of block 2540, where the second node may send a seventh indication to the first node that the SCG should be activated in response to the indication of the available UL data volume. An example is shown in FIG. 23.

[0191] Furthermore, FIG. 26 shows a flow diagram of an exemplary method (e.g., procedure) for a first node configured to provide an MCG to a UE with an SCG also configured in a wireless network according to various embodiments of the present disclosure. The exemplary method may be implemented by a network node (e.g., a base station, eNB, gNB, ng-eNB, en-gNB, etc., or components thereof) as described elsewhere herein.

[0192] The exemplary method may include the operation of block 2620, where the first node may receive an indication of the UL data volume available for transmission by the UE via the SCG from the UE while the SCG is in a deactivated state. The exemplary method may also include the operation of block 2630, where the first node may send an indication of the available UL data volume to a second node configured to provide the SCG.

[0193] In some embodiments, the exemplary method may also include the operations of blocks 2640-2650, where the first node may receive a second indication from the second node that the SCG should be activated in response to the indication of the available UL data volume and send the second indication to the UE. An example is shown by FIG. 23.

[0194] In some embodiments, an indication of the available UL data volume is received from the UE in one or more of a MAC BSR, an RRC message, and a PDCP PDU. In some variations, the RRC message is a UE Assistance Information message. In other variations, the MAC BSR is transmitted using an RRC message as a container.

[0195] In some embodiments, the indication of the available UL data volume is one of an indication that UL data is available for transmission via the SCG, an indication of the volume of UL data available for transmission via the SCG, or an indication that the SCG should be activated.

[0196] In various embodiments, the indicated volume of UL data available for transmission via the SCG is ● the type of bearer associated with the available UL data, and ● whether the MCG or the SCG is configured as the PDCP primary path, and ● whether PDCP duplication is enabled based on one or more of the above.

[0197] In some embodiments, the indicated volume of UL data available for transmission via the SCG can be greater than a first threshold applicable when the SCG is in a deactivated state. The first threshold can be different from a second threshold applicable when the SCG is in an activated state.

[0198] In some embodiments, an exemplary method can include the operation of block 2610, where the first node can transmit to the UE a first indication that the SCG should be deactivated. This first indication can be transmitted before receiving an indication of the available UL data volume (e.g., at block 2620).

[0199] While various embodiments have been described herein above in terms of methods, apparatus, devices, computer-readable media, and receivers, it will be readily appreciated by those skilled in the art that such methods 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.

[0200] For example, FIG. 27 shows an exemplary wireless network in which various embodiments disclosed herein can be implemented. For simplicity, the wireless network of FIG. 27 shows only network 2706, network nodes 2760 and 2760b, and WDs 2710, 2710b, and 2710c. In practice, the wireless network can further include any additional elements suitable for supporting communication between wireless devices or between a wireless device and another communication device such as a landline phone, a service provider, or any other network node or end device. Of the components shown, network node 2760 and wireless device (WD) 2710 are illustrated with additional detail. The wireless network can provide communication and other types of services to one or more wireless devices to facilitate access of the wireless devices to the wireless network and / or use of services provided by or via the wireless network.

[0201] A wireless network can comprise any type of communication, telecommunication, data, cellular, and / or wireless network, or other similar type of system, and / or can interface with them. In some embodiments, the wireless network can be configured to operate according to a particular standard or other type of predefined rules or procedures. Thus, particular embodiments of a wireless network can implement communication standards such as the General Packet Radio Service (GSM), Universal Mobile Telecommunications System (UMTS), Long Term Evolution (LTE), and / or other suitable 2G, 3G, 4G, or 5G standards, wireless local area network (WLAN) standards such as the IEEE 802.11 standard, and / or any other suitable wireless communication standards such as Worldwide Interoperability for Microwave Access (WiMax), Bluetooth, Z-Wave, and / or ZigBee standards.

[0202] Network 2706 can comprise one or more backhaul networks, core networks, IP networks, public switched telephone networks (PSTN), packet data networks, optical networks, wide area networks (WAN), local area networks (LAN), wireless local area networks (WLAN), wired networks, wireless networks, metropolitan area networks, and other networks for enabling communication between devices.

[0203] Network nodes 2760 and WD2710 comprise various components that are described in more detail below. These components cooperate to provide network node and / or wireless device functionality, such as providing a wireless connection in a wireless network. In different embodiments, the wireless network can comprise any number of wired or wireless networks, network nodes, base stations, controllers, wireless devices, relays, 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.

[0204] Examples of network nodes include, but are not limited to, access points (APs) (e.g., wireless access points), base stations (BSs) (e.g., wireless base stations, Node B, evolved Node B (eNB), and NR Node B (gNB)). Base stations can be categorized based on the amount of coverage provided by the base station (or, alternatively, the transmission power level of the base station), in which case they may be referred to as femto base stations, pico base stations, micro base stations, or macro base stations. A base station can be a relay node or a relay donor node that controls a relay. A 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), which may be referred to as a remote radio head (RRH). Such remote radio units 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).

[0205] Further examples of network nodes include 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), core network nodes (e.g., MSC, MME), O&M nodes, OSS nodes, SON nodes, positioning nodes (e.g., E-SMLC), and / or MDTs. As another example, a network node can be a virtual network node, as described in more detail below. However, more generally, a network node can represent any suitable device (or group of devices) that is configured, arranged, and / or operable to enable access to a wireless network and / or provide to, or provide some service to, a wireless device that has accessed the wireless network.

[0206] In FIG. 27, network node 2760 includes a processing circuit 2770, a device-readable medium 2780, an interface 2790, auxiliary equipment 2784, a power supply 2786, a power circuit 2787, and an antenna 2762. The network node 2760 shown in the exemplary wireless network of FIG. 27 can represent a device that includes the shown combination of hardware components, although other embodiments can include network nodes with different combinations of components. It should be understood that the network node can comprise any suitable combination of hardware and / or software required to implement the tasks, features, functions, and methods and / or procedures disclosed herein. Moreover, although the components of network node 2760 are illustrated as a single box located within a larger box or as a single box nested within multiple boxes, in reality, the network node can comprise a plurality of different physical components that make up a single shown component (e.g., device-readable medium 2780 can comprise a plurality of separate hard drives as well as a plurality of RAM modules).

[0207] Similarly, network node 2760 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 network node 2760 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 a plurality of Node Bs. In such scenarios, each unique pair of Node B and RNC can, in some cases, be regarded as a single distinct network node. In some embodiments, network node 2760 can be configured to support a plurality of radio access technologies (RATs). In such embodiments, some components can be replicated (e.g., separate device-readable media 2780 for different RATs), and some components can be reused (e.g., the same antenna 2762 can be shared by RATs). Network node 2760 can also include a plurality of sets of various illustrated components for different radio technologies, such as, for example, GSM, WCDMA, LTE, NR, WiFi, or Bluetooth radio technology, integrated into network node 2760. These radio technologies can be integrated with the same or different chips or sets of chips, and other components within network node 2760.

[0208] The processing circuit 2770 may be configured to perform any decision-making operation, computational operation, or similar operation (e.g., some acquisition operations) as described herein as provided by a network node. These operations performed by the processing circuit 2770 may include processing the information obtained by the processing circuit 2770, for example, by converting the obtained information into other information, comparing the obtained information or the converted information with the information stored in the network node, and / or performing one or more operations based on the obtained information or the converted information and as a result of the processing having made a decision.

[0209] The processing circuit 2770 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, a combination of one or more of the resources, or a combination of hardware, software and / or encoded logic, operable to provide various functions of the network node 2760 either alone or in combination with other network node 2760 components (e.g., the device-readable medium 2780). Such functions can include any of the various wireless features, functions, or benefits described herein.

[0210] For example, the processing circuit 2770 can execute instructions stored in the device-readable medium 2780 or instructions stored in the memory within the processing circuit 2770. In some embodiments, the processing circuit 2770 can include a system-on-chip (SOC). As a more specific example, the instructions (also referred to as a computer program product) stored in the medium 2780 can include instructions that, when executed by the processing circuit 2770, can be configured to cause the network node 2760 to perform operations corresponding to the various exemplary methods (e.g., procedures) described herein.

[0211] In some embodiments, processing circuit 2770 can include one or more of radio frequency (RF) transceiver circuit 2772 and baseband processing circuit 2774. In some embodiments, radio frequency (RF) transceiver circuit 2772 and baseband processing circuit 2774 can be on separate chips (or sets of chips), boards, or units such as radio units and digital units. In alternative embodiments, some or all of RF transceiver circuit 2772 and baseband processing circuit 2774 can be on the same chip or set of chips, board, or unit.

[0212] In some embodiments, some or all of the functions described herein as provided by a network node, base station, eNB, or other such network device can be implemented by processing circuit 2770 executing instructions stored in device-readable medium 2780, or in memory within processing circuit 2770. In alternative embodiments, some or all of the functions can be provided by processing circuit 2770 without executing instructions stored in a separate or discrete device-readable medium, such as in a hardwired fashion. In any of those embodiments, whether or not executing instructions stored in a device-readable storage medium, processing circuit 2770 can be configured to implement the described functions. The benefits provided by such functions are not limited to processing circuit 2770 alone, or to other components of network node 2760, but are enjoyed generally by network node 2760 as a whole, and / or by end users and wireless networks.

[0213] The device-readable medium 2780 can comprise any form of volatile or non-volatile computer-readable memory, including but not limited to 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)), 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 the processing circuit 2770. The device-readable medium 2780 can store any suitable instructions, data, or information, including an application that includes one or more of a computer program, software, logic, rules, code, tables, etc., and / or other instructions that can be executed by the processing circuit 2770 and utilized by the network node 2760. The device-readable medium 2780 can be used to store calculations performed by the processing circuit 2770 and / or data received via the interface 2790. In some embodiments, the processing circuit 2770 and the device-readable medium 2780 can be considered integrated.

[0214] Interface 2790 is used in wired or wireless communication of signaling and / or data between network node 2760, network 2706, and / or WD 2710. As shown, interface 2790 includes (one or more) ports / (one or more) terminals 2794 for sending and receiving data to and from network 2706, for example, over a wired connection. Interface 2790 also includes a radio front-end circuit 2792 that is coupled to antenna 2762 or, in some embodiments, can be part of antenna 2762. The radio front-end circuit 2792 includes a filter 2798 and an amplifier 2796. The radio front-end circuit 2792 can be connected to antenna 2762 and processing circuit 2770. The radio front-end circuit can be configured to condition signals communicated between antenna 2762 and processing circuit 2770. The radio front-end circuit 2792 can receive digital data to be sent to other network nodes or WDs via a wireless connection. The radio front-end circuit 2792 can convert the digital data into a wireless signal having appropriate channel and bandwidth parameters using a combination of filter 2798 and / or amplifier 2796. The wireless signal can then be transmitted via antenna 2762. Similarly, when receiving data, antenna 2762 can collect the wireless signal, which is then converted into digital data by radio front-end circuit 2792. The digital data can be passed to processing circuit 2770. In other embodiments, the interface can comprise different components and / or different combinations of components.

[0215] In some alternative embodiments, network node 2760 may not include a separate radio front-end circuit 2792. Instead, processing circuit 2770 may include a radio front-end circuit and may be connected to antenna 2762 without a separate radio front-end circuit 2792. Similarly, in some embodiments, all or part of RF transceiver circuit 2772 may be considered part of interface 2790. In yet other embodiments, interface 2790 may include one or more ports or terminals 2794, radio front-end circuit 2792, and RF transceiver circuit 2772 as part of a wireless unit (not shown), and interface 2790 may communicate with baseband processing circuit 2774, which is part of a digital unit (not shown).

[0216] Antenna 2762 can include one or more antennas or antenna arrays configured to send and / or receive wireless signals. Antenna 2762 can be coupled to radio front-end circuit 2790 and can be any type of antenna capable of wirelessly transmitting and receiving data and / or signals. In some embodiments, antenna 2762 can comprise one or more omnidirectional, sector, or panel antennas operable to transmit / receive wireless signals, for example, between 2 GHz and 66 GHz. Omnidirectional antennas can be used to transmit / receive wireless signals in any direction, sector antennas can be used to transmit / receive wireless signals from devices within a particular area, and panel antennas can be line-of-sight antennas used to transmit / receive wireless signals in a relatively straight line. In some cases, the use of two or more antennas may be referred to as MIMO. In some embodiments, antenna 2762 can be separate from network node 2760 and can be connectable to network node 2760 through an interface or port.

[0217] Antenna 2762, interface 2790, and / or processing circuit 2770 may be configured to perform any receiving operations and / or some acquisition operations described herein as being performed by a network node. Any information, data, and / or signals may be received from a wireless device, another network node, and / or any other network equipment. Similarly, antenna 2762, interface 2790, and / or processing circuit 2770 may be configured to perform any transmission operations described herein as being performed by a network node. Any information, data, and / or signals may be transmitted to a wireless device, another network node, and / or any other network equipment.

[0218] Power circuit 2787 may comprise a power management circuit or be coupled to a power management circuit and be configured to supply power for performing the functions described herein to the components of network node 2760. Power circuit 2787 can receive power from power source 2786. Power source 2786 and / or power circuit 2787 may be configured to provide power to the various components of network node 2760 in a form suitable for each respective component (e.g., at the voltage and current levels required for each respective component). Power source 2786 may be either included in power circuit 2787 and / or network node 2760 or external to power circuit 2787 and / or network node 2760. For example, network node 2760 may be connectable to an external power source (e.g., an electrical outlet) via an input circuit or interface such as an electrical cable, whereby the external power source supplies power to power circuit 2787. As a further example, power source 2786 can comprise a power source in the form of a battery or battery pack connected to or integrated in power circuit 2787. The battery can provide backup power in case the external power source fails. Other types of power sources such as photovoltaic devices may also be used.

[0219] An alternative embodiment of network node 2760 can be responsible for providing some aspects of the functionality of a network node, including any of the functionality described herein and / or any functionality necessary to support the subject matter described herein, and can include additional components other than those shown in FIG. 27. For example, network node 2760 can include a user interface device to enable and / or facilitate the input of information to network node 2760 and to enable and / or facilitate the output of information from network node 2760. This can enable and / or facilitate a user to perform diagnostic, maintenance, repair, and other administrative functions for network node 2760.

[0220] In some embodiments, a wireless device (WD, e.g., WD2710) can be configured to send and / or receive information without direct human interaction. For example, a WD can be designed to send information to the network at a predetermined schedule when triggered by an internal or external event or in response to a request from the network. Examples of WDs 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 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, and the like.

[0221] WD can support device-to-device (D2D) communication, for example, by implementing 3GPP standards for sidelink communication, vehicle-to-vehicle (V2V), vehicle-to-infrastructure (V2I), and vehicle-to-everything (V2X). In this case, it may be referred to as a D2D communication device. As another specific example, in an Internet of Things (IoT) scenario, WD can represent a machine or other device that performs monitoring and / or measurement and transmits the results of such monitoring and / or measurement to another WD and / or network node. In this case, WD can be a machine-to-machine (M2M) device, and M2M devices may sometimes be referred to as machine type communication (MTC) devices in the 3GPP context. As one specific example, WD can be a user equipment (UE) that implements the 3GPP narrowband Internet of Things (NB-IoT) standard. Specific examples of such machines or devices include sensors, metering devices such as power meters, industrial machinery, or household or personal electrical appliances (e.g., refrigerators, televisions, etc.), and personal wearables (e.g., watches, fitness trackers, etc.). In other scenarios, WD can represent a vehicle or other device that can monitor and / or report on its operating status or perform other functions related to its operation. The WD described above can represent an endpoint of a wireless connection, in which case the device may sometimes be referred to as a wireless terminal. Furthermore, the WD described above can be mobile, in which case the device may also be referred to as a mobile device or mobile terminal.

[0222] As shown, the wireless device 2710 includes an antenna 2711, an interface 2714, a processing circuit 2720, a device-readable medium 2730, a user interface device 2732, an auxiliary device 2734, a power supply 2736, and a power circuit 2737. WD2710 can include one or more sets of the illustrated components for different wireless technologies supported by WD2710, for example, to name just a few, GSM, WCDMA, LTE, NR, WiFi, WiMAX, or Bluetooth wireless technologies. These wireless technologies can be integrated into the same or different chips or sets of chips as other components within WD2710.

[0223] Antenna 2711 can include one or more antennas or antenna arrays configured to send and / or receive wireless signals and is connected to interface 2714. In some alternative embodiments, antenna 2711 can be separate from WD2710 and connectable to WD2710 through an interface or port. Antenna 2711, interface 2714, and / or processing circuit 2720 can be configured to perform any receiving or transmitting operations described herein as being performed by the WD. Any information, data, and / or signals can be received from network nodes and / or another WD. In some embodiments, the radio front-end circuit and / or antenna 2711 can be regarded as an interface.

[0224] As shown, interface 2714 includes a radio front-end circuit 2712 and an antenna 2711. The radio front-end circuit 2712 includes one or more filters 2718 and an amplifier 2716. The radio front-end circuit 2714 is connected to the antenna 2711 and the processing circuit 2720 and can be configured to condition signals communicated between the antenna 2711 and the processing circuit 2720. The radio front-end circuit 2712 can be coupled to the antenna 2711 or can be part of the antenna 2711. In some embodiments, WD 2710 may not include a separate radio front-end circuit 2712; rather, the processing circuit 2720 can include a radio front-end circuit and can be connected to the antenna 2711. Similarly, in some embodiments, some or all of the RF transceiver circuit 2722 can be considered part of the interface 2714. The radio front-end circuit 2712 can receive digital data to be sent to other network nodes or WDs via a wireless connection. The radio front-end circuit 2712 can convert the digital data into a wireless signal having appropriate channel and bandwidth parameters using a combination of the filters 2718 and / or the amplifier 2716. The wireless signal can then be transmitted via the antenna 2711. Similarly, when receiving data, the antenna 2711 can collect a wireless signal, which can then be converted into digital data by the radio front-end circuit 2712. The digital data can be passed to the processing circuit 2720. In other embodiments, the interface can include different components and / or different combinations of components.

[0225] The processing circuit 2720 can comprise 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, one or more combinations of resources, or a combination of hardware, software and / or encoded logic, operable to provide the WD2710 functionality, either alone or in combination with other WD2710 components such as the device readable medium 2730. Such functionality can include any of the various wireless features or benefits described herein.

[0226] For example, the processing circuit 2720 can execute instructions stored on the device readable medium 2730, or instructions stored in memory within the processing circuit 2720, to provide the functionality disclosed herein. More specifically, the instructions (also referred to as a computer program product) stored on the medium 2730 can include instructions that, when executed by the processor 2720, can be configured to cause the wireless device 2710 to perform operations corresponding to the various exemplary methods (e.g., procedures) described herein.

[0227] As shown, processing circuit 2720 includes one or more of RF transceiver circuit 2722, baseband processing circuit 2724, and application processing circuit 2726. In other embodiments, the processing circuit can comprise different components and / or different combinations of components. In some embodiments, the processing circuit 2720 of WD 2710 can comprise a system-on-a-chip (SOC). In some embodiments, RF transceiver circuit 2722, baseband processing circuit 2724, and application processing circuit 2726 can be on separate chips or a set of chips. In an alternative embodiment, some or all of baseband processing circuit 2724 and application processing circuit 2726 can be combined to be on one chip or a set of chips, and RF transceiver circuit 2722 can be on a separate chip or a set of chips. In yet another alternative embodiment, some or all of RF transceiver circuit 2722 and baseband processing circuit 2724 can be on the same chip or a set of chips, and application processing circuit 2726 can be on a separate chip or a set of chips. In still other alternative embodiments, some or all of RF transceiver circuit 2722, baseband processing circuit 2724, and application processing circuit 2726 can be combined within the same chip or a set of chips. In some embodiments, RF transceiver circuit 2722 can be part of interface 2714. RF transceiver circuit 2722 can condition RF signals for processing circuit 2720.

[0228] In some embodiments, some or all of the functions described herein as being performed by the WD may be provided by a processing circuit 2720 that executes instructions stored on a device-readable medium 2730, which in some embodiments may be a computer-readable storage medium. In alternative embodiments, some or all of the functions may be provided by the processing circuit 2720 without executing instructions stored on a separate or discrete device-readable storage medium, such as in a hardwired manner. In any of those particular embodiments, whether or not executing instructions stored on a device-readable storage medium, the processing circuit 2720 may be configured to perform the functions described. The benefits provided by such functions are not limited to the processing circuit 2720 alone or to other components of the WD2710, but are enjoyed generally by the WD2710 as a whole and / or by an end user and a wireless network.

[0229] The processing circuit 2720 may be configured to perform any decision-making operation, computational operation, or similar operation (e.g., some acquisition operations) described herein as being performed by the WD. Such operations as performed by the processing circuit 2720 may include processing information obtained by the processing circuit 2720, e.g., by converting the obtained information into other information, comparing the obtained information or the converted information with information stored by the WD2710, and / or performing one or more operations based on the obtained information or the converted information and as a result of the processing having made a decision.

[0230] The device-readable medium 2730 can be operative to store an application including one or more of a computer program, software, logic, rules, code, tables, etc., and / or other instructions that can be executed by the processing circuitry 2720. The device-readable medium 2730 can include a computer memory (e.g., random access memory (RAM) or read-only memory (ROM)), a mass storage medium (e.g., a hard disk), a removable storage medium (e.g., a compact disk (CD) or digital video disk (DVD)), 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 the processing circuitry 2720. In some embodiments, the processing circuitry 2720 and the device-readable medium 2730 can be considered integrated.

[0231] The user interface device 2732 can include components that enable and / or facilitate interaction between a human user and the WD2710. Such interaction can be in many forms, such as visual, auditory, tactile, etc. The user interface device 2732 can be operable to produce output to the user and to enable and / or facilitate the user to provide input to the WD2710. The type of interaction may vary depending on the type of user interface device 2732 installed in the WD2710. For example, if the WD2710 is a smartphone, the interaction can be via a touch screen, and if the WD2710 is a smart meter, the interaction can be through a screen that provides usage (e.g., the number of gallons used) or a speaker that provides an audible alarm (e.g., if smoke is detected). The user interface device 2732 can include an input interface, devices and circuits, as well as an output interface, devices and circuits. The user interface device 2732 can be configured to enable and / or facilitate the input of information to the WD2710 and is connected to the processing circuit 2720 to enable and / or facilitate the processing circuit 2720 to process the input information. The user interface device 2732 can include, for example, a microphone, proximity or other sensors, keys / buttons, a touch display, one or more cameras, a USB port, or other input circuits. The user interface device 2732 is also configured to enable and / or facilitate the output of information from the WD2710 and to enable and / or facilitate the processing circuit 2720 to output information from the WD2710. The user interface device 2732 can include, for example, a speaker, a display, a vibration circuit, a USB port, a headphone interface, or other output circuits.Using one or more input and output interfaces, devices, and circuits of the user interface device 2732, the WD2710 can communicate with an end user and / or a wireless network, enabling and / or facilitating the end user and / or the wireless network to benefit from the functions described herein.

[0232] The auxiliary device 2734 is operable to provide more specific functions that may not generally be performed by the WD. This can include special sensors for making measurements for various purposes, interfaces for additional types of communication such as wired communication, etc. The inclusion of components of the auxiliary device 2734, and the types of components of the auxiliary device 2734, may vary depending on the embodiment and / or scenario.

[0233] The power source 2736 may, in some embodiments, be in the form of a battery or battery pack. Other types of power sources may also be used, such as an external power source (e.g., an electrical outlet), a photovoltaic device, or a battery. The WD2710 can further include a power circuit 2737 for distributing power from the power source 2736 to various parts of the WD2710 that require power from the power source 2736 to perform any of the functions described or indicated herein. The power circuit 2737 can, in some embodiments, include a power management circuit. The power circuit 2737 can alternatively or additionally be operable to receive power from an external power source, in which case the WD2710 can be connectable to the external power source (such as an electrical outlet) via an input circuit or interface such as a power cable. The power circuit 2737 can also, in some embodiments, be operable to distribute power from an external power source to the power source 2736. This can be, for example, for charging the power source 2736. The power circuit 2737 can perform any conversion or other modification to the power from the power source 2736 to make it suitable for supply to each component of the WD2710.

[0234] Figure 28 shows an embodiment of a UE according to various aspects described herein. A user equipment or UE as used herein does not necessarily have a user in the sense of a human user who owns and / or operates a relevant device. Instead, a UE can 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 initially be associated with a particular human user. Alternatively, a UE can represent a device (e.g., a smart power meter) that is not intended for sale to or operation by an end user but can be associated with a user or operated for the benefit of a user. UE28200 can be any UE identified by the Third Generation Partnership Project (3GPP) including, but not limited to, an NB-IoT UE, a machine type communication (MTC) UE, and / or an extended MTC (eMTC) UE. The UE2800 shown in FIG. 28 is an example of a WD configured for communication according to one or more communication standards published by 3GPP, such as the GSM, UMTS, LTE, and / or 5G standards of the Third Generation Partnership Project (3GPP). As previously mentioned, the terms WD and UE can be used interchangeably. Thus, while FIG. 28 shows a UE, the components described herein are equally applicable to a WD and vice versa.

[0235] In FIG. 28, the UE 2800 includes a processing circuit 2801 operatively coupled to an input / output interface 2805, a radio frequency (RF) interface 2809, a network connection interface 2811, a memory 2815 including a random access memory (RAM) 2817, a read-only memory (ROM) 2819, a storage medium 2821, etc., a communication subsystem 2831, a power supply 2833, and / or any other components, or any combination thereof. The storage medium 2821 includes an operating system 2823, an application program 2825, and data 2827. In other embodiments, the storage medium 2821 can include other similar types of information. Some UEs can utilize all of the components shown in FIG. 28 or only a subset of those components. 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.

[0236] In FIG. 28, the processing circuit 2801 can be configured to process computer instructions and data. The processing circuit 2801 can be any sequential state machine operable to execute machine instructions stored in memory as a machine-readable computer program, such as one or more hardware-implemented state machines (e.g., in discrete logic, FPGA, ASIC, etc.), programmable logic together with appropriate firmware, a microprocessor or digital signal processor (DSP) together with appropriate software, one or more program embedded, general-purpose processors, or any combination of the above. For example, the processing circuit 2801 can include two central processing units (CPUs). Data can be information in a form suitable for use by a computer.

[0237] In the illustrated embodiment, the input / output interface 2805 can be configured to provide a communication interface to an input device, an output device, or an input / output device. The UE 2800 can be configured to use an output device via the input / output interface 2805. The output device can use the same type of interface port as the input device. For example, a USB port can be used to provide input to and output from the UE 2800. The output device can be a speaker, a sound card, a video card, a display, a monitor, a printer, an actuator, an emitter, a smart card, another output device, or any combination thereof. The UE 2800 can be configured to use an input device via the input / output interface 2805 to enable and / or facilitate a user to capture information to the UE 2800. The input device can include a touch-sensitive or presence-sensitive display, a camera (e.g., a digital camera, a digital video camera, a web camera, etc.), a microphone, a sensor, a mouse, a trackball, a direction pad, a trackpad, a scroll wheel, a smart card, etc. The presence-sensitive display can include a capacitive or resistive touch sensor for detecting input from a user. The sensor can be, for example, an accelerometer, a gyroscope, a tilt sensor, a force sensor, a magnetometer, an optical sensor, a proximity sensor, another similar sensor, or any combination thereof. For example, the input device can be an accelerometer, a magnetometer, a digital camera, a microphone, and an optical sensor.

[0238] In FIG. 28, the RF interface 2809 can be configured to provide a communication interface to RF components such as a transmitter, a receiver, and an antenna. The network connection interface 2811 can be configured to provide a communication interface to the network 2843a. The network 2843a can include wired and / or wireless networks such as a local area network (LAN), a wide area network (WAN), a computer network, a wireless network, a communication network, another similar network, or any combination thereof. For example, the network 2843a can include a Wi-Fi network. The network connection interface 2811 can be configured to include a receiver and a transmitter interface for communicating with one or more other devices on the communication network according to one or more communication protocols such as Ethernet, TCP / IP, SONET, ATM, etc. The network connection interface 2811 can implement receiver and transmitter functions suitable for a communication network link (e.g., optical, electrical, etc.). The receiver and transmitter functions can share circuit components, software, or firmware, or alternatively, can be implemented separately.

[0239] The RAM 2817 can be configured to interface with the processing circuit 2801 via the bus 2802 to provide storage or caching of data or computer instructions during the execution of software programs such as an operating system, application programs, and device drivers. The ROM 2819 can be configured to provide computer instructions or data to the processing circuit 2801. For example, the ROM 2819 can be configured to store invariant low-level system code or data for basic system functions such as basic input / output (I / O), startup, or reception of keystrokes from a keyboard, which is stored in non-volatile memory. The storage medium 2821 can be configured to include memory such as RAM, ROM, programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), magnetic disk, optical disk, floppy disk, hard disk, removable cartridge, or flash drive.

[0240] In one example, the storage medium 2821 can be configured to include an operating system 2823, an application program 2825 such as a web browser application, a widget or gadget engine, or another application, and a data file 2827. The storage medium 2821 can store any of a variety of operating systems or combinations of operating systems for use by the UE 2800. For example, the application program 2825 can include executable program instructions (also referred to as a computer program product) that can be configured to perform operations corresponding to various exemplary methods (e.g., procedures) described herein for the UE 2800 when executed by the processor 2801.

[0241] The memory medium 2821 can be configured to include several physical drive units, such as a redundant array of independent disks (RAID), a floppy disk drive, a flash memory, a USB flash drive, an external hard disk drive, a thumb drive, a pen drive, a key drive, a high-definition 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), a synchronous dynamic random access memory (SDRAM), an external micro DIMM SDRAM, a subscriber identity module or removable user identity information (SIM / RUIM) module such as a smart card memory, other memories, or any combination thereof. The memory medium 2821 can enable and / or facilitate the UE2800 to access computer-executable 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 tangibly embodied in the memory medium 2821, and the memory medium 2821 can comprise a device-readable medium.

[0242] In FIG. 28, the processing circuit 2801 can be configured to communicate with the network 2843b using the communication subsystem 2831. The network 2843a and the network 2843b can be the same one or more networks or different one or more networks. The communication subsystem 2831 can be configured to include one or more transceivers used to communicate with the network 2843b. For example, the communication subsystem 2831 can be configured to include one or more transceivers for communicating with one or more remote transceivers of another WD, UE, or base station, etc. that can perform wireless communication, such as another device capable of wireless communication according to one or more communication protocols, such as IEEE802.28, CDMA, WCDMA, GSM, LTE, UTRAN, WiMax, etc. with a radio access network (RAN). Each transceiver can include a transmitter 2833 and / or a receiver 2835 for implementing a transmitter function or a receiver function suitable for a RAN link (such as frequency allocation, etc.), respectively. Further, the transmitter 2833 and the receiver 2835 of each transceiver can share circuit components, software, or firmware, or alternatively, can be implemented separately.

[0243] In the illustrated embodiment, the communication functions of the communication subsystem 2831 can include 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) to determine location, other similar communication functions, or any combination thereof. For example, the communication subsystem 2831 can include cellular communication, Wi-Fi communication, Bluetooth communication, and GPS communication. The network 2843b can include wired and / or wireless networks such as a local area network (LAN), a wide area network (WAN), a computer network, a wireless network, a communication network, other similar networks, or any combination thereof. For example, the network 2843b can be a cellular network, a Wi-Fi network, and / or a near-field network. The power supply 2813 can be configured to provide alternating current (AC) or direct current (DC) power to the components of the UE 2800.

[0244] The features, benefits, and / or functions described herein can be implemented in one of the components of UE2800 or can be partitioned across multiple components of UE2800. Further, the features, benefits, and / or functions described herein can be implemented in any combination of hardware, software, or firmware. In one example, communication subsystem 2831 can be configured to include any of the components described herein. Further, processing circuitry 2801 can be configured to communicate with any of such components over bus 2802. In another example, any of such components can be represented by program instructions stored in a memory that, when executed by processing circuitry 2801, implement the corresponding functions described herein. In another example, the functions of any of such components can be partitioned between processing circuitry 2801 and communication subsystem 2831. In another example, non-computation-intensive functions of any of such components can be implemented in software or firmware, and computation-intensive functions can be implemented in hardware.

[0245] FIG. 29 is a schematic block diagram showing a virtualization environment 2900 in which functions implemented by some embodiments can be virtualized. In this context, virtualizing can mean creating a virtual version of a device or apparatus that can include virtualizing the hardware platform, storage devices, and networking resources. Virtualization as used herein can be applied to a node (e.g., a virtualized base station or a virtualized radio access node), or to a device (e.g., a UE, a wireless device, or any other type of communication device) or a component of such device, and relates to an implementation form in which at least a portion of the function is implemented as one or more virtual components (e.g., via one or more applications, components, functions, virtual machines, or containers that execute on one or more physical processing nodes in one or more networks).

[0246] In some embodiments, some or all of the functions described herein may be implemented as virtual components that are executed by one or more virtual machines implemented in one or more virtual environments 2900 hosted by one or more of the hardware nodes 2930. Further, in embodiments where the virtual node is not a radio access node or does not require wireless connectivity (e.g., a core network node), the network node may be fully virtualized.

[0247] The functions may be implemented by one or more applications 2920 (alternatively, sometimes referred to as software instances, virtual appliances, network functions, virtual nodes, virtual network functions, etc.) operable to implement some of the features, functions, and / or benefits of some of the embodiments disclosed herein. The application 2920 is operated in a virtualized environment 2900 that provides hardware 2930 comprising a processing circuit 2960 and a memory 2990. The memory 2990 includes instructions 2995 executable by the processing circuit 2960, whereby the application 2920 is operable to provide one or more of the features, benefits, and / or functions disclosed herein.

[0248] The virtualized environment 2900 can include a general-purpose or special-purpose network hardware device (or node) 2930 that includes a set of one or more processors or a processing circuit 2960, where the set of one or more processors or the processing circuit 2960 can be a commercial off-the-shelf (COTS) processor, a dedicated application-specific integrated circuit (ASIC), or any other type of processing circuit that includes digital or analog hardware components or dedicated processors. Each hardware device can include a memory 2990-1, which can be a non-persistent memory for temporarily storing instructions 2995 or software executed by the processing circuit 2960. For example, the instructions 2995 can include program instructions (also referred to as a computer program product) that, when executed by the processing circuit 2960, can be configured to perform operations corresponding to various exemplary methods (e.g., procedures) described herein for the hardware node 2920. Such operations can also be by one or more virtual nodes 2920 hosted by the hardware node 2930.

[0249] Each hardware device can include one or more network interface controllers (NICs) 2970, also known as network interface cards, where the network interface controller (NIC) 2970 includes a physical network interface 2980. Each hardware device can also include a non-transitory, persistent, machine-readable storage medium 2990-2 that stores software 2995 and / or instructions executable by the processing circuit 2960. The software 2995 can include any type of software, including software for instantiating one or more virtualization layers (also referred to as hypervisors) 2950, software for executing virtual machines 2940, and software that enables it to perform functions, features, and / or benefits described in relation to some of the embodiments described herein.

[0250] The virtual machine 2940 includes virtual processing, virtual memory, virtual networking or interfaces, and virtual storage areas, and can be operated by a corresponding virtualization layer 2950 or hypervisor. Different embodiments of instances of the virtual appliance 2920 can be implemented on one or more of the virtual machines 2940, and the implementation can be done in different ways.

[0251] During operation, the processing circuit 2960 executes software 2995 to instantiate the hypervisor or virtualization layer 2950, which is sometimes called a virtual machine monitor (VMM). The virtualization layer 2950 can present a virtual operating platform to the virtual machine 2940 that appears like networking hardware.

[0252] As shown in FIG. 29, the hardware 2930 can be a stand-alone network node with general or specific components. The hardware 2930 can include an antenna 29225 and can implement some functions through virtualization. Alternatively, the hardware 2930 can be part of a larger class of hardware (such as in the case of a data center or customer premise equipment (CPE)) that is managed through a management and orchestration (MANO) 29100 where many hardware nodes cooperate and particularly oversee the lifecycle management of the application 2920.

[0253] The virtualization of hardware is called network function virtualization (NFV) in some contexts. NFV can be used to consolidate many network equipment types onto industry-standard high-volume server hardware, physical switches, and physical storage areas that can be located within data centers and customer premise equipment.

[0254] In the context of NFV, the virtual machine 2940 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 virtual machines 2940, whether it is dedicated hardware for that virtual machine and / or hardware shared with other virtual machines among the virtual machines 2940 by that virtual machine, forms a separate virtual network element (VNE) with that part of the hardware 2930 that executes that virtual machine.

[0255] Furthermore, in the context of NFV, the virtual network function (VNF) is responsible for handling specific network functions running on one or more virtual machines 2940 over the hardware networking infrastructure 2930, corresponding to the application 2920 in FIG. 29.

[0256] In some embodiments, one or more radio units 29200, each including one or more transmitters 29220 and one or more receivers 29210, can be coupled to one or more antennas 29225. The radio unit 29200 can communicate directly with the hardware node 2930 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 radio access node or a base station. The node configured in this way can also communicate with one or more UEs as described elsewhere in this specification.

[0257] In some embodiments, some signaling can be implemented via a control system 29230 that can alternatively be used for communication between the hardware node 2930 and the radio unit 29200.

[0258] Referring to FIG. 30, according to one embodiment, a communication network 3010, such as a 3GPP type cellular network, includes an access network 3011, such as a radio access network, and a core network 3014. The access network 3011 includes a plurality of base stations 3012a, 3012b, 3012c, such as NB, eNB, gNB, or other types of radio access points, each defining a corresponding coverage area 3013a, 3013b, 3013c. Each base station 3012a, 3012b, 3012c can be connected to the core network 3014 over a wired or wireless connection 3015. A first UE 3091 located in the coverage area 3013c can be configured to wirelessly connect to the corresponding base station 3012c or be paged by the corresponding base station 3012c. A second UE 3092 in the coverage area 3013a can be wirelessly connected to the corresponding base station 3012a. Although a plurality of UEs 3091, 3092 are shown in this example, the disclosed embodiments are equally applicable to situations where only one UE is in the coverage area or where only one UE is connected to, etc.

[0259] The communication network 3010 is itself connected to a host computer 3030, which may be embodied in the hardware and / or software of a stand-alone server, a cloud-implemented server, a distributed server, or as processing resources in a server farm. The host computer 3030 may be under the ownership or control of a service provider, or may be operated by or on behalf of a service provider. The connections 3021 and 3022 between the communication network 3010 and the host computer 3030 can extend directly from the core network 3014 to the host computer 3030, or can proceed via an optional intermediate network 3020. The intermediate network 3020 can be one of a public network, a private network, or a hosted network, or a combination of two or more of them, and the intermediate network 3020 can, if any, be a backbone network or the Internet. In particular, the intermediate network 3020 can comprise two or more sub-networks (not shown).

[0260] The communication system of FIG. 30 enables connectivity between the connected UEs 3091, 3092 and the host computer 3030. The connectivity can be described as an over-the-top (OTT) connection 3050. The host computer 3030 and the connected UEs 3091, 3092 are configured to communicate data and / or signaling via the OTT connection 3050, using the access network 3011, the core network 3014, any intermediate network 3020, and any additional infrastructure (not shown) that may be considered. The OTT connection 3050 can be transparent in the sense that the participating communication devices through which the OTT connection 3050 passes are unaware of the routing of the uplink and downlink communications. For example, the base station 3012 may not be informed or need to be informed about the past routing of an incoming downlink communication with data originating from the host computer 3030 that is to be forwarded (e.g., handed over) to the connected UE 3091. Similarly, the base station 3012 does not need to be aware of the future routing of an outgoing uplink communication originating from the UE 3091 and destined for the host computer 3030.

[0261] Next, an exemplary implementation of the UE, base station, and host computer described in the previous paragraph according to one embodiment will be described with reference to FIG. 31. In communication system 3100, host computer 3110 comprises hardware 3115 including a communication interface 3116 configured to set up and maintain a wired or wireless connection with an interface of different communication devices of communication system 3100. Host computer 3110 further comprises a processing circuit 3118 that can have a memory capacity and / or a processing capacity. In particular, processing circuit 3118 can comprise one or more programmable processors, application specific integrated circuits, field programmable gate arrays, or combinations thereof (not shown) adapted to execute instructions. Host computer 3110 further comprises software 3111 stored in or accessible by host computer 3110 and executable by processing circuit 3118. Software 3111 includes host application 3112. Host application 3112 can be operable to provide services to remote users, such as UE 3130, that connect via an OTT connection 3150 that terminates at UE 3130 and host computer 3110. When providing services to a remote user, host application 3112 can provide user data transmitted using OTT connection 3150.

[0262] The communication system 3100 can also include a base station 3120 provided in the communication system. The base station 3120 includes hardware 3125 that enables the base station 3120 to communicate with a host computer 3110 and a UE 3130. The hardware 3125 includes a communication interface 3126 for setting up and maintaining a wired or wireless connection with an interface of different communication devices in the communication system 3100, and a wireless interface 3127 for setting up and maintaining at least a wireless connection 3170 with a UE 3130 located in a coverage area (not shown in FIG. 31) served by the base station 3120. The communication interface 3126 can be configured to facilitate a connection 3160 to the host computer 3110. The connection 3160 can be direct, or the connection 3160 can pass through a core network (not shown in FIG. 31) of the communication system and / or one or more intermediate networks external to the communication system. In the illustrated embodiment, the hardware 3125 of the base station 3120 can also include a processing circuit 3128, which can include one or more programmable processors, application-specific integrated circuits, field-programmable gate arrays, or combinations thereof (not shown) adapted to execute instructions.

[0263] The base station 3120 also includes software 3121 that is stored internally or accessible via an external connection. For example, the software 3121 can include program instructions (also referred to as a computer program product) that, when executed by the processing circuit 3128, can be configured to perform operations corresponding to various exemplary methods (e.g., procedures) described herein for the base station 3120.

[0264] The communication system 3100 can also include the UE 3130 already mentioned, and the hardware 3135 of the UE 3130 can include a radio interface 3137 that is configured to set up and maintain a radio connection 3170 with a base station serving the coverage area where the UE 3130 is currently located. The hardware 3135 of the UE 3130 can also include a processing circuit 3138, and the processing circuit 3138 can comprise one or more programmable processors, application-specific integrated circuits, field-programmable gate arrays, or combinations thereof (not shown) that are adapted to execute instructions.

[0265] The UE 3130 also includes software 3128 that is stored in or accessible by the UE 3130 and executable by the processing circuit 3138. The software 3128 includes a client application 3132. The client application 3132 can be operable to provide services to a human or non-human user via the UE 3130 under the support of the host computer 3110. In the host computer 3110, the running host application 3112 can communicate with the running client application 3132 via an OTT connection 3150 that terminates at the UE 3130 and the host computer 3110. When providing services to the user, the client application 3132 can receive request data from the host application 3112 and provide user data in response to the request data. The OTT connection 3150 can transfer both the request data and the user data. The client application 3132 can interact with the user to generate the user data provided by the client application 3132. The software 3128 can also include program instructions (also referred to as a computer program product) that, when executed by the processing circuit 3138, can be configured to cause the UE 3130 to perform operations corresponding to various exemplary methods (e.g., procedures) described herein.

[0266] As an example, the host computer 3110, the base station 3120, and the UE 3130 shown in FIG. 31 can be the same as or equivalent to one of the host computer 2730, the base stations 2712a, 2712b, 2712c in FIG. 27, and one of the UEs 2791, 2792, respectively. That is, the operations inside these entities can be as shown in FIG. 31, and separately, the surrounding network topology can be that of FIG. 27.

[0267] In FIG. 31, the OTT connection 3150 is abstractly depicted to show the communication between the host computer 3110 and the UE 3130 via the base station 3120 without explicit mention of the intermediary device and the exact routing of messages through these devices. The network infrastructure can determine the routing, and the network infrastructure can be configured to hide the routing from the UE 3130 or from the service provider operating the host computer 3110, or both. While the OTT connection 3150 is active, the network infrastructure can further make a determination to dynamically change the routing (e.g., based on network load distribution considerations or reconfiguration).

[0268] The wireless connection 3170 between the UE 3130 and the base station 3120 follows the teachings of the embodiments described throughout this disclosure. One or more of the various embodiments improve the performance of the OTT services provided to the UE 3130 using the OTT connection 3150 of which the wireless connection 3170 forms the last segment. More precisely, the embodiments disclosed herein enable the network to improve the flexibility for monitoring the end-to-end quality of service (QoS) of data flows, which includes the corresponding radio bearers of the data flows associated with a data session between a user equipment (UE) and another entity such as an OTT data application or service external to the 5G network. These and other advantages can facilitate a more timely design, implementation, and deployment of 5G / NR solutions. Further, such embodiments can facilitate flexible and timely control of data session QoS, which can lead to improvements in capacity, throughput, latency, etc., as envisioned by 5G / NR and important for the growth of OTT services.

[0269] Measurement procedures can be provided for the purpose of monitoring data rate, latency, and other network operating modes that are improved by one or more embodiments. There may further be an optional network function for reconfiguring the OTT connection 3150 between the host computer 3110 and the UE 3130 in response to variations in the measurement results. The measurement procedures and / or the network function for reconfiguring the OTT connection 3150 can be implemented in the software 3111 and hardware 3115 of the host computer 3110 or in the software 3128 and hardware 3135 of the UE 3130, or both. In an embodiment, a sensor (not shown) can be deployed in or in relation to a communication device through which the OTT connection 3150 passes, and the sensor can participate in the measurement procedure by supplying values of the monitored quantities exemplified above or by supplying values of other physical quantities that the software 3111, 3128 can calculate or estimate the monitored quantities. The reconfiguration of the OTT connection 3150 can include a message format, retransmission settings, preferred routing, etc., and the reconfiguration need not affect the base station 3120 and can be unknown or imperceptible to the base station 3120. Such procedures and functions are known and practiced in the art. In some embodiments, the measurement can involve proprietary UE signaling that facilitates measurement of the host computer 3110 such as throughput, propagation time, latency, etc. The measurement can be implemented in that the software 3111 and 3128 cause messages, particularly empty or "dummy" messages, to be transmitted using the OTT connection 3150 while the software 3111 and 3128 monitor propagation time, errors, etc.

[0270] FIG. 32 is a flowchart showing an exemplary method (e.g., procedure) implemented in a communication system according to various embodiments. The communication system may include, in some embodiments, a host computer, a base station, and a UE, as described with reference to other figures herein. For simplicity of the present disclosure, only the reference to FIG. 32 is included in this section. In step 3210, the host computer provides user data. In an optional sub-step 3211 of step 3210, the host computer provides user data by executing a host application. In step 3220, the host computer initiates a transmission to carry the user data to the UE. In an optional step 3230, the base station transmits the user data carried in the transmission initiated by the host computer to the UE according to the teachings of the embodiments described throughout the present disclosure. In an optional step 3240, the UE executes a client application related to the host application executed by the host computer.

[0271] FIG. 33 is a flowchart showing an exemplary method (e.g., procedure) implemented in a communication system according to various embodiments. The communication system may include, as described with reference to other figures herein, a host computer, a base station, and a UE. For simplicity of the present disclosure, only the reference to FIG. 33 is included in this section. In step 3310 of the method, the host computer provides user data. In an optional sub-step (not shown), the host computer provides user data by executing a host application. In step 3320, the host computer initiates a transmission to carry the user data to the UE. The transmission can pass through the base station according to the teachings of the embodiments described throughout the present disclosure. In an optional step 3330, the UE receives the user data carried in the transmission.

[0272] FIG. 34 is a flowchart showing an exemplary method (e.g., procedure) implemented in a communication system according to various embodiments. The communication system can include a host computer, a base station, and a UE, as described with reference to other figures herein. For simplicity of the present disclosure, only the drawing reference to FIG. 34 is included in this section. In optional step 3410, the UE receives input data provided by the host computer. Additionally or alternatively, in step 3420, the UE provides user data. In optional sub-step 3421 of step 3420, the UE provides user data by executing a client application. In optional sub-step 3411 of step 3410, the UE executes a client application that provides user data in response to the received input data provided by the host computer. When providing user data, the executed client application can further consider user input received from the user. Regardless of the particular manner in which the user data is provided, the UE initiates, in optional sub-step 3430, the transmission of the user data to the host computer. In step 3440 of the method, the host computer receives the user data transmitted from the UE according to the teachings of the embodiments described throughout the present disclosure.

[0273] FIG. 35 is a flowchart showing an exemplary method (e.g., procedure) implemented in a communication system according to various embodiments. The communication system can include a host computer, a base station, and a UE, which can be the ones described with reference to other figures herein. For simplicity of the present disclosure, only the reference to FIG. 35 is included in this section. In optional step 3510, according to the teachings of the embodiments described throughout the present disclosure, the base station receives user data from the UE. In optional step 3520, the base station initiates the transmission of the received user data to the host computer. In optional step 3530, the host computer receives the user data carried in the transmission initiated by the base station.

[0274] The foregoing merely illustrates the principles of the present 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 present disclosure and, thus, can be within the spirit and scope of the present disclosure, although not explicitly shown or described herein, can be devised by those skilled in the art. As should be understood by those skilled in the art, various embodiments can be used together with each other and interchangeably with each other.

[0275] As used herein, the term unit can have its ordinary meaning in the field 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 discrete devices, computer programs or instructions, etc., for performing respective task, procedure, calculation, output, and / or display functions, such as those described herein.

[0276] Any suitable steps, methods, features, functions, or benefits disclosed herein may be implemented through one or more functional units or modules of one or more virtual devices. Each virtual device may comprise several of these functional units. These functional units may be implemented via a processing circuit, which may include one or more microprocessors or microcontrollers, and other digital hardware, which may include a digital signal processor (DSP), dedicated digital logic, etc. The processing circuit may be configured to execute program code stored in a memory, which may 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 may be used to cause each functional unit to perform the corresponding function according to one or more embodiments of the present disclosure.

[0277] As described herein, a device and / or apparatus may be represented by a semiconductor chip, a chip set, or a (hardware) module comprising such a chip or chip set, 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 executable software code portions for execution on or operating 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 function in cooperation with each other 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 maintained. Such and similar principles are considered to be known to those skilled in the art.

[0278] 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 in the context of this specification and the relevant art, and it should be further understood that they shall not be construed in an idealized or overly formal sense unless expressly so defined herein.

[0279] 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. Further, unless the knowledge of the prior art is explicitly incorporated herein by reference above, the knowledge of the prior art is not explicitly incorporated herein in its entirety. All publications referenced are incorporated herein by reference in their entirety.

[0280] The techniques and apparatuses described herein include, but are not limited to, the following enumerated examples.

[0281] A1. 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: determining the availability of uplink (UL) data for transmission via the SCG while the SCG is deactivated; calculating an available UL data volume; reporting the available UL data volume to the radio network based on one or more of: via the deactivated SCG, after activation of the SCG via the SCG, after receiving an indication that the SCG should be activated via the SCG from the radio network, and via the MCG. A method as described above.

[0282] A1a. The method according to embodiment A1, further comprising deactivating the SCG in response to receiving a first indication that the SCG should be deactivated from a first node configured to provide the MCG.

[0283] The method according to embodiment A1a, wherein deactivating the SCG further comprises stopping or suspending one or more timers associated with the periodic reporting of the available UL data volume related to the SCG.

[0284] Reporting the available UL data volume comprises receiving, from a second node configured to provide the SCG, a UL grant for transmission of a buffer status report (BSR); and using the received UL grant to transmit, via the SCG, a BSR indicating the available UL data volume to the second node. The method according to any one of embodiments A1 to A1b.

[0285] A3. Reporting the available UL data volume further comprises sending a scheduling request (SR) to the second node, wherein the UL grant is received in response to the SR, and the SR and BSR are transmitted while the SCG is deactivated, or the SR is transmitted while the SCG is deactivated and the BSR is transmitted after the SCG is activated. One of the above applies. The method according to embodiment A2.

[0286] A4. The UL grant includes a second indication that the SCG should be activated, and reporting the available UL data volume further comprises activating the SCG in response to the second indication and before transmitting the BSR. The method according to embodiment A3.

[0287] A5. The UL grant is a configured UL grant for use while the SCG is deactivated. The set UL grant is received from a second node before the SCG is deactivated, The method according to Embodiment A2.

[0288] A6. The method according to any one of Embodiments A1 to A2, further comprising activating the SCG based on determining the availability of UL data.

[0289] A7. The method according to Embodiment A6, further comprising starting a timer in response to activating the SCG.

[0290] A8. The method according to Embodiment A7, further comprising deactivating the SCG when the timer expires after reporting the available UL data volume.

[0291] A9. Before the timer expires, from a second node configured to provide the SCG, A third indication that the SCG should be activated, or A fourth indication that the SCG should be deactivated Receiving one of them, Stopping the timer in response to the third indication or the fourth indication, and The method according to Embodiment A7 or A8, further comprising.

[0292] A10. Reporting the available UL data volume to the wireless network includes transmitting an indication of the available UL data volume in one of a media access control (MAC) buffer status report (BSR) or a radio resource control (RRC) message to a first node of the wireless network configured to provide the MCG. The method according to any one of Embodiments A1 to A2.

[0293] A11. Receiving, from a first node in response to an indication of an available UL data volume, a fifth indication that the SCG should be activated; Activating the SCG in response to the fifth indication; The method according to embodiment A10, further comprising.

[0294] A12. Calculating the available UL data volume is based on one or more of: The type of bearer associated with the available UL data; Whether the MCG or SCG is configured as a packet data convergence protocol (PDCP) primary path; Whether PDCP duplication is enabled; The method according to any one of embodiments A1 to A11.

[0295] A13. Reporting the available UL data volume is based on determining that the available UL data volume is greater than a first threshold applicable when the SCG is deactivated, the method according to any one of embodiments A1 to A12.

[0296] A14. The method according to embodiment A13, wherein the first threshold is different from a second threshold applicable when the SCG is activated.

[0297] B1. A method for a second node of a radio network configured to provide a secondary cell group (SCG) to a user equipment (UE) also configured to communicate with the radio network via a master cell group (MCG), the method comprising: Receiving, while the SCG is deactivated, an indication of an available UL data volume determined by the UE for transmission via the SCG, the indication being via: The deactivated SCG; The SCG after activation of the UE of the SCG; After sending an instruction to the UE that the SCG should be activated, via the SCG, and Receiving, by the UE, an indication of the available UL data volume determined for transmission via the SCG, received based on one or more of a first node of the radio network configured to provide the MCG including a method

[0298] B2. Receiving an indication of the available UL data volume can be providing the UE with a UL grant for transmission of a buffer status report (BSR), and receiving, from the UE via the SCG in accordance with the UL grant, a BSR indicating the available UL data volume The method according to Embodiment B1, including

[0299] B3. Receiving an indication of the available UL data volume further includes receiving a scheduling request (SR) from the UE, where the UL grant is provided in response to the SR, where the SR and BSR are received via a deactivated SCG, or where the SR is received via a deactivated SCG and the BSR is received after activation of the UE of the SCG, one of which is applicable The method according to Embodiment B2.

[0300] B4. The UL grant includes an instruction that the UE should activate the SCG before transmitting the BSR, the method according to Embodiment B3.

[0301] B5. The UL grant is a configured UL grant for use while the SCG is deactivated, where the configured UL grant is provided to the UE before or together with an instruction that the SCG should be deactivated The method according to Embodiment B2.

[0302] B6. In response to an indication of the available UL data volume, to the UE, a third indication that the SCG should be activated, or a fourth indication that the SCG should be deactivated The method according to Embodiment B1 or B2, further comprising transmitting one of them.

[0303] B7. In response to an indication of the available UL data volume, to the first node, a fifth indication that the SCG will be activated, or a sixth indication that the SCG will be deactivated The method according to Embodiment B6, further comprising transmitting one of them.

[0304] B8. An indication of the available UL data volume is received from the first node, The method further comprises transmitting, in response to the indication of the available UL data volume, to the first node, a seventh indication that the SCG should be activated. The method according to Embodiment B1 or B2.

[0305] B9. The indicated available UL data volume is the type of bearer related to the available UL data, whether the MCG or SCG is configured as the packet data convergence protocol (PDCP) primary path, whether PDCP duplication is enabled The method according to any one of Embodiments B1 to B18, determined by the UE based on one or more of them.

[0306] B10. The indicated available UL data volume is greater than a first threshold applicable when the SCG is deactivated, The first threshold is different from a second threshold applicable when the SCG is activated, The method according to any one of Embodiments B1 to B9.

[0307] C1. A method for a first node of a radio network configured to provide a master cell group (MCG) to a user equipment (UE) also configured to communicate with the radio network via a secondary cell group (SCG), the method comprising: Receiving, from the UE while the SCG is deactivated, an indication of an available UL data volume determined by the UE for transmission via the SCG; Transmitting the indication of the available UL data volume to a second node of the radio network configured to provide the SCG; The method comprising.

[0308] C2. Receiving, from the second node in response to the indication of the available UL data volume, a second indication that the SCG should be activated; Transmitting the second indication to the UE; The method according to Embodiment C1, further comprising.

[0309] C3. The method according to Embodiment C1 or C2, wherein the indication of the available UL data volume is received from the UE in one of a media access control (MAC) buffer status report (BSR) or a radio resource control (RRC) message.

[0310] C4. The indicated available UL data volume is The type of bearer associated with the available UL data, Whether the MCG or the SCG is configured as a packet data convergence protocol (PDCP) primary path, Whether PDCP replication is effective or not and The method according to any one of Embodiments C1 to C3, determined by the UE based on one or more of them.

[0311] C5. The indicated available UL data volume is greater than a first threshold related to the deactivated SCG, The first threshold is different from a second threshold applicable when the SCG is activated, The method according to any one of Embodiments C1 to C4.

[0312] C6. The method according to any one of Embodiments C1 to C5, further comprising transmitting a first indication to the UE that the SCG should be deactivated.

[0313] D1. A user equipment (UE) configured to communicate with a radio network via a master cell group (MCG) and a secondary cell group (SCG), wherein the UE A radio transceiver circuit configured to communicate with a radio network via the SCG and a master cell group (MCG), A processing circuit operably coupled to the radio transceiver circuit, whereby the processing circuit and the radio transceiver circuit are configured to perform operations corresponding to any of the methods described in Embodiments A1 to A14, the processing circuit A user equipment (UE) comprising.

[0314] D2. A user equipment (UE) for communicating with a radio network via a master cell group (MCG) and a secondary cell group (SCG), wherein the UE is further configured to perform operations corresponding to any of the methods described in Embodiments A1 to A14.

[0315] 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 A14.

[0316] 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 A14.

[0317] E1. A second node of a radio network configured to provide a secondary cell group (SCG) to a user equipment (UE) also configured to communicate with the radio network via a master cell group (MCG), the second node comprising: A communication interface circuit configured to communicate with the UE via the SCG and communicate with a first node configured to provide the MCG; 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 B1 to B10. The second node comprising the above.

[0318] E2. A second node of a radio network configured to provide a secondary cell group (SCG) to a user equipment (UE) also configured to communicate with the radio network via a master cell group (MCG), the second node being further configured to perform operations corresponding to any of the methods described in Embodiments B1 to B10.

[0319] A non - transitory computer - readable medium storing computer - executable instructions that, when executed by a processing circuit of a second node of a radio network configured to provide a secondary cell group (SCG) to a user equipment (UE), configure the second node to perform operations corresponding to any of the methods described in Embodiments B1 to B10.

[0320] A computer program product comprising computer - executable instructions that, when executed by a processing circuit of a second node of a radio network configured to provide a secondary cell group (SCG) to a user equipment (UE), configure the second node to perform operations corresponding to any of the methods described in Embodiments B1 to B10.

[0321] F1. A first node of a radio network configured to provide a master cell group (MCG) to a user equipment (UE) also configured to communicate with the radio network via a secondary cell group (SCG), the first node comprising: A communication interface circuit configured to communicate with the UE via the MCG and communicate with a second node configured to provide the MCG; 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 C1 to C6. The first node comprising the above.

[0322] F2. A first node of a radio network configured to provide a master cell group (MCG) to a user equipment (UE) also configured to communicate with the radio network via a secondary cell group (SCG), the first node further configured to perform operations corresponding to any of the methods described in Embodiments C1 to C6.

[0323] A non-transitory computer-readable medium storing computer-executable instructions that, when executed by a processing circuit of a first node of a radio network configured to provide a master cell group (MCG) to a user equipment (UE), configure the first node to perform operations corresponding to any of the methods described in Embodiments C1 to C6.

[0324] A computer program product comprising computer-executable instructions that, when executed by a processing circuit of a first node of a radio network configured to provide a master cell group (MCG) to a user equipment (UE), configure the first node to perform operations corresponding to any of the methods described in Embodiments C1 to C6.

Claims

1. 1. A method for a user equipment (UE) in a wireless network with a master cell group (MCG) and a secondary cell group (SCG), the method comprising: determining (2420) availability of uplink (UL) data for transmission via the SCG; Calculating the available UL data volume (2435); determining whether the SCG is in an activated or deactivated state; If the SCG is in an active state, sending a Buffer Status Report (BSR) on the SCG; otherwise, sending an RRC UEAssistanceInformation message to the radio network via the MCG when the SCG is in a deactivated state, the message including an indication that UL data is available for transmission via the SCG; receiving an UL grant for transmission of a Buffer Status Report (BSR) from a second node configured to provide said SCG (2443); and transmitting the BSR indicating an available UL data volume to the second node via the SCG using the received UL grant (2445); A method comprising:

2. receiving 2410 a first indication from a first node configured to provide the MCG that the SCG should be deactivated; deactivating the SCG in response to the first indication (2415); The method of claim 1 further comprising:

3. 3. The method of claim 2, wherein deactivating the SCG (2415) further comprises stopping or pausing one or more timers (2416) associated with periodic reporting of available UL data volume associated with the SCG.

4. sending a scheduling request (SR) to the second node (2442); the UL grant is received in response to the SR; The SR and the BSR are transmitted while the SCG is in the deactivated state. The SR is sent while the SCG is in the deactivated state, and the BSR is sent after activating the SCG, or The SR and the BSR are transmitted after activating the SCG. One of the following applies:

4. The method according to any one of claims 1 to 3.

5. the UL grant includes a second indication that the SCG should be activated; activating (2444) the SCG in response to the second indication and prior to transmitting (2445) the BSR. The method according to claim 4.

6. the UL grant is a configured UL grant for use while the SCG is in the deactivated state; The configured UL grant is received from the second node before the SCG is deactivated.

4. The method according to any one of claims 1 to 3.

7. The method of claim 1 , further comprising activating (2425) the SCG based on determining (2420) the availability of the UL data.

8. 8. The method of claim 7, further comprising starting (2430) a timer in response to activating (2425) the SCG.

9. 10. The method of claim 8, further comprising: deactivating (2470) the SCG upon expiration of the timer after reporting that UL data is available for transmission via the SCG.

10. from a second node configured to serve the SCG prior to expiration of the timer: a third indication that the SCG should be activated; or A fourth indication that the SCG should be deactivated. receiving (2450) one of: stopping the timer in response to the third instruction or the fourth instruction (2460); 10. The method of claim 8 or 9, further comprising:

11. receiving a fifth indication from a first node configured to provide the MCG that the SCG should be activated in response to the RRC UEAssistanceInformation message including the indication that UL data is available for transmission via the SCG (2480); and activating the SCG in response to the fifth indication (2490); and The method of claim 1 , further comprising:

12. Calculating the available UL data volume comprises: a type of bearer associated with the available UL data; and Whether the MCG or SCG has been configured as a Packet Data Convergence Protocol (PDCP) primary path; and Whether PDCP replication is enabled and The method according to any one of claims 1 to 11, based on one or more of:

13. transmitting the RRC UEAssistanceInformation message including the indication that UL data is available for transmission via the SCG based on determining that the available UL data volume is greater than a first threshold applicable when the SCG is in the deactivated state (2441); the first threshold is different from a second threshold applicable when the SCG is in an activated state; 13. The method according to any one of claims 1 to 12.

14. A user equipment (UE) (120, 505, 605, 1710, 3010, 3100, 3430) in a wireless network (100, 399, 599, 699, 2843) in which a master cell group (MCG) and a secondary cell group (SCG) are configured, the UE comprising: determining availability of uplink (UL) data for transmission via the SCG; Calculating the available UL data volume; determining whether the SCG is in an activated or deactivated state; If the SCG is in an active state, sending a Buffer Status Report (BSR) on the SCG; otherwise, sending an RRC UEAssistanceInformation message to the radio network via the MCG when the SCG is in a deactivated state, the message including an indication that UL data is available for transmission via the SCG; receiving an UL grant for transmission of a Buffer Status Report (BSR) from a second node configured to provide the SCG; and using the received UL grant to transmit, via the SCG, the BSR indicating an available UL data volume to the second node. and a user equipment (UE) (120, 505, 605, 1710, 3010, 3100, 3430) further configured to:

15. A UE (120, 505, 605, 1710, 3010, 3100, 3430) according to claim 14, further configured to perform operations corresponding to any of the methods according to claims 2 to 13.

16. A computer program (2825, 3131) comprising computer-executable instructions which, when executed by a processing circuit (2720, 2801, 3138) of a user equipment (UE) (120, 505, 605, 1710, 3010, 3100, 3430) in a wireless network (100, 399, 599, 699, 2843) in which a master cell group (MCG) and a secondary cell group (SCG) are configured, configures the UE to perform operations corresponding to any of the methods described in claims 1 to 13.

Images