UE capability checking in mac based mobility
By ensuring that only cells within the UE's capabilities are activated through MAC-based mobility, the solution optimizes cell activation and mobility in 5G systems, addressing inefficiencies in UE capability checking.
Patent Information
- Authority / Receiving Office
- WO · WO
- Patent Type
- Applications
- Current Assignee / Owner
- NOKIA SOLUTIONS (SHANGHAI) CO LTD
- Filing Date
- 2024-12-20
- Publication Date
- 2026-06-25
AI Technical Summary
Existing 5G communication systems face inefficiencies in UE capability checking during MAC-based mobility, leading to potential activation of cells that exceed the UE's capabilities, which can hinder efficient cell activation and mobility.
Implementing a solution where the network ensures that only cells within the UE's capability are activated by transmitting cell configurations and commands through MAC signaling, ensuring compliance with the UE's capabilities, such as band combinations, thereby optimizing MAC layer mobility with carrier aggregation frameworks.
This approach enhances the efficiency of cell activation and UE mobility by ensuring that only capable cells are activated, reducing the risk of exceeding UE limits and improving overall network performance.
Smart Images

Figure CN2024141232_25062026_PF_FP_ABST
Abstract
Description
UE CAPABILITY CHECKING IN MAC BASED MOBILITYFIELD
[0001] Various example embodiments of the present disclosure generally relate to the field of telecommunication and in particular, to methods, devices, apparatuses and computer readable storage medium for user equipment (UE) capability checking in medium access control (MAC) based mobility.BACKGROUND
[0002] In 5G architecture, layer 3 (L3) level mobility (also referred to L3 mobility sometimes) may be characterized by the user equipment (UE) sending measurements using radio recontrol (RRC) signaling, and by the network issuing handover (HO) commands using RRC signaling. For example, after the network indicates to the UE that it is to perform a handover, the decision on the handover is performed from an RRC layer. Lower layer triggered mobility (LTM) allows the handover to be triggered at a MAC layer.SUMMARY
[0003] In a first aspect of the present disclosure, there is provided a first apparatus. The first apparatus comprises at least one processor; and at least one memory storing instructions that, when executed by the at least one processor, cause the first apparatus at least to: receive, from a second apparatus, a cell configuration indicating one or more cells; and receive, from the second apparatus, a cell command associated with at least one cell of the one or more cells, where one or more activated cells of the one or more cells do not exceed the capability of the first apparatus.
[0004] In a second aspect of the present disclosure, there is provided a second apparatus. The second apparatus comprises at least one processor; and at least one memory storing instructions that, when executed by the at least one processor, cause the second apparatus at least to: transmit, to a first apparatus, a cell configuration indicating one or more cells for the first apparatus; and transmit, to the first apparatus, a cell command associated with at least one cell of the one or more cells, where one or more activated cells of the one or more cells do not exceed the capability of the first apparatus.
[0005] In a third aspect of the present disclosure, there is provided a method. The method at a first apparatus comprises: receiving, from a second apparatus, a cell configuration indicating one or more cells; and receiving, from the second apparatus, a cell command associated with at least one cell of the one or more cells, where one or more activated cells of the one or more cells do not exceed the capability of the first apparatus.
[0006] In a fourth aspect of the present disclosure, there is provided a method at a second apparatus. The method comprises: transmitting, to a first apparatus, a cell configuration indicating one or more cells for the first apparatus; and transmitting, to the first apparatus, a cell command associated with at least one cell of the one or more cells, where one or more activated cells of the one or more cells do not exceed the capability of the first apparatus.
[0007] In a fifth aspect of the present disclosure, there is provided a first apparatus. The first apparatus comprises means for receiving, from a second apparatus, a cell configuration indicating one or more cells; and means for receiving, from the second apparatus, a cell command associated with at least one cell of the one or more cells, where one or more activated cells of the one or more cells do not exceed the capability of the first apparatus.
[0008] In a sixth aspect of the present disclosure, there is provided a second apparatus. The second apparatus comprises means for transmitting, to a first apparatus, a cell configuration indicating one or more cells for the first apparatus; and means for transmitting, to the first apparatus, a cell command associated with at least one cell of the one or more cells, where one or more activated cells of the one or more cells do not exceed the capability of the first apparatus.
[0009] In a seventh aspect of the present disclosure, there is provided a computer readable medium. The computer readable medium comprises instructions stored thereon for causing an apparatus to perform at least the method according to at least one of the third aspect or the fourth aspect.
[0010] It is to be understood that the Summary section is not intended to identify key or essential features of embodiments of the present disclosure, nor is it intended to be used to limit the scope of the present disclosure. Other features of the present disclosure will become easily comprehensible through the following description.BRIEF DESCRIPTION OF THE DRAWINGS
[0011] Some example embodiments will now be described with reference to the accompanying drawings, where:
[0012] FIG. 1 illustrates an example communication environment in which example embodiments of the present disclosure can be implemented;
[0013] FIG. 2 illustrates a schematic diagram of an example architecture 200 for handover with a single RRC entity;
[0014] FIG. 3 illustrates an example scenario of the MAC based mobility;
[0015] FIG. 4 illustrates an overall process for a cell change in MAC based mobility according to some example embodiments of the present disclosure;
[0016] FIG. 5 illustrates a signaling flow for UE capability checking in MAC based mobility according to some example embodiments of the present disclosure;
[0017] FIG. 6 illustrates a flowchart of a method implemented at a first apparatus in accordance with some example embodiments of the present disclosure;
[0018] FIG. 7 illustrates a flowchart of a method implemented at a second apparatus in accordance with some example embodiments of the present disclosure;
[0019] FIG. 8 illustrates a simplified block diagram of a device that is suitable for implementing example embodiments of the present disclosure; and
[0020] FIG. 9 illustrates a block diagram of an example computer readable medium in accordance with some example embodiments of the present disclosure.
[0021] Throughout the drawings, the same or similar reference numerals represent the same or similar element.DETAILED DESCRIPTION
[0022] Principles of example embodiments will now be described with reference to some example embodiments. It is to be understood that these embodiments are described only for the purpose of illustration and help those skilled in the art to understand and implement the present disclosure, without suggesting any limitation as to the scope of the disclosure. Embodiments described herein can be implemented in various manners other than the ones described below.
[0023] In the following description and claims, unless defined otherwise, all technical and scientific terms used herein have the same meaning as commonly understood by one of ordinary skills in the art to which this disclosure belongs.
[0024] References in the present disclosure to “one embodiment, ” “an embodiment, ” “an example embodiment, ” and the like indicate that the embodiment described may include a particular feature, structure, or characteristic, but it is not necessary that every embodiment includes the particular feature, structure, or characteristic. Moreover, such phrases are not necessarily referring to the same embodiment. Further, when a particular feature, structure, or characteristic is described in connection with an embodiment, it is submitted that it is within the knowledge of one skilled in the art to affect such feature, structure, or characteristic in connection with other embodiments whether or not explicitly described.
[0025] It shall be understood that although the terms “first, ” “second, ” …, etc. in front of noun (s) and the like may be used herein to describe various elements, these elements may not be limited by these terms. These terms are only used to distinguish one element from another and they do not limit the order of the noun (s) . For example, a first element could be termed a second element, and similarly, a second element could be termed a first element, without departing from the scope of example embodiments. As used herein, the term “and / or” includes any and all combinations of one or more of the listed terms.
[0026] As used herein, “at least one of the following: <a list of two or more elements>” and “at least one of <a list of two or more elements>” and similar wording, where the list of two or more elements are joined by “and” or “or” , mean at least any one of the elements, or at least any two or more of the elements, or at least all the elements.
[0027] As used herein, unless stated explicitly, performing a step “in response to A” does not indicate that the step is performed immediately after “A” occurs and one or more intervening steps may be included.
[0028] The terminology used herein is for the purpose of describing particular embodiments only and is not intended to be limiting of example embodiments. As used herein, the singular forms “a” , “an” and “the” are intended to include the plural forms as well, unless the context clearly indicates otherwise. It will be further understood that the terms “comprises” , “comprising” , “has” , “having” , “includes” and / or “including” , when used herein, specify the presence of stated features, elements, and / or components etc., but do not preclude the presence or addition of one or more other features, elements, components and / or combinations thereof.
[0029] As used in this application, the term “circuitry” may refer to one or more or all of the following: (a) hardware-only circuit implementations (such as implementations in only analog and / or digital circuitry) and (b) combinations of hardware circuits and software, such as (as applicable) : (i) a combination of analog and / or digital hardware circuit (s) with software / firmware and (ii) any portions of hardware processor (s) with software (including digital signal processor (s) ) , software, and memory (ies) that work together to cause an apparatus, such as a mobile phone or server, to perform various functions) and (c) hardware circuit (s) and or processor (s) , such as a microprocessor (s) or a portion of a microprocessor (s) , that requires software (e.g., firmware) for operation, but the software may not be present when it is not needed for operation.
[0030] This definition of circuitry applies to all uses of this term in this application, including in any claims. As a further example, as used in this application, the term circuitry also covers an implementation of merely a hardware circuit or processor (or multiple processors) or portion of a hardware circuit or processor and its (or their) accompanying software and / or firmware. The term circuitry also covers, for example and if applicable to the particular claim element, a baseband integrated circuit or processor integrated circuit for a mobile device or a similar integrated circuit in server, a cellular network device, or other computing or network device.
[0031] As used herein, the term “communication network” refers to a network following any suitable communication standards, such as new radio (NR) , long term evolution (LTE) , LTE-advanced (LTE-A) , wideband code division multiple access (WCDMA) , high-speed packet access (HSPA) , narrow band internet of things (NB-IoT) and so on. Furthermore, the communications between a user device and a network device in the communication network may be performed according to any suitable generation communication protocols, including, but not limited to, the first generation (1G) , the second generation (2G) , 2.5G, 2.75G, the third generation (3G) , the fourth generation (4G) , 4.5G, the fifth generation (5G) , 5G-advanced, the sixth generation (6G) communication protocols and the like, wireless local network communication protocols such as institute for electrical and electronics engineers (IEEE) 802.11 and the like, and / or any other protocols either currently known or to be developed in the future. Moreover, the communication may utilize any proper wireless communication technology, comprising but not limited to: code division multiple access (CDMA) , frequency division multiple access (FDMA) , time division multiple access (TDMA) , frequency division duplex (FDD) , time division duplex (TDD) , multiple-input multiple-output (MIMO) , orthogonal frequency division multiple (OFDM) , discrete fourier transform spread OFDM (DFT-s-OFDM) and / or any other technologies currently known or to be developed in the future. Embodiments may be applied in various communication systems. Given the rapid development in communications, there will of course also be future type communication technologies and systems with which the present disclosure may be embodied. It may not be seen as limiting the scope to only the aforementioned system.
[0032] As used herein, the term “network device” refers to a node in a communication network via which a user device accesses the network and receives services therefrom. The network device may comprise a base station (BS) or an access point (AP) , for example, a node B (NodeB or NB) , an evolved NodeB (eNodeB or eNB) , an NR NB (also referred to as a gNB) , a remote radio unit (RRU) , a radio header (RH) , a remote radio head (RRH) , a relay, an integrated access and backhaul (IAB) node, a low power node such as a femto, a home gNB (HgNB) , a pico, a non-terrestrial network (NTN) or non-ground network device such as a satellite network device, a low earth orbit (LEO) satellite and a geosynchronous earth orbit (GEO) satellite, an aircraft network device, and so forth, depending on the applied terminology and technology. In some example embodiments, the network device may utilize a radio access network (RAN) split architecture where the network device includes a central unit (CU) and a distributed unit (DU) .
[0033] The term “user device” refers to any end device that may be capable of wireless communication. By way of example rather than limitation, a terminal device may also be referred to as user equipment (UE) , a subscriber station (SS) , a portable subscriber station, a mobile station (MS) , or an access terminal (AT) . The terminal device may include, but not limited to, a mobile phone, a cellular phone, a smart phone, voice over IP (VoIP) phones, wireless local loop phones, a tablet, a wearable terminal device, a personal digital assistant (PDA) , portable computers, desktop computer, image capture terminal devices such as digital cameras, gaming terminal devices, music storage and playback appliances, vehicle-mounted wireless terminal devices, wireless endpoints, mobile stations, laptop-embedded equipment (LEE) , laptop-mounted equipment (LME) , USB dongles, smart devices, wireless customer-premises equipment (CPE) , an Internet of Things (IoT) device, a watch or other wearable, a head-mounted display (HMD) , a vehicle, a drone, a medical device and applications (e.g., remote surgery) , an industrial device and applications (e.g., a robot and / or other wireless devices operating in an industrial and / or an automated processing chain contexts) , a consumer electronics device, a device operating on commercial and / or industrial wireless networks, and the like. The user device may also correspond to a mobile termination (MT) part of an IAB node (e.g., a relay node) . In the following description, the terms “terminal device” , “user device” , “user equipment” and “UE” may be used interchangeably.
[0034] As used herein, the term “resource, ” “transmission resource, ” “reblock, ” “physical reblock” (PRB) , “uplink resource, ” or “downlink resource” may refer to any refor performing a communication, for example, a communication between a terminal device and a network device, such as a rein time domain, a rein frequency domain, a rein space domain, a rein code domain, or any other combination of the time, frequency, space and / or code domain reenabling a communication, and the like. In the following, unless explicitly stated, a rein both frequency domain and time domain will be used as an example of a transmission refor describing some example embodiments of the present disclosure. It is noted that example embodiments of the present disclosure are equally applicable to other resources in other domains.
[0035] FIG. 1 illustrates an example communication environment 100 in which example embodiments of the present disclosure can be implemented. In the communication environment 100, a plurality of communication devices, including a first apparatus 110 and a second apparatus 120 may communicate with each other. The first apparatus 110 may be a user device, such as a UE. The second apparatus 120 may be a network device, such as a BS or a gNB.
[0036] In some example embodiments, if the first apparatus 110 is a terminal device and the second apparatus 120 is a network device, a link from the second apparatus 120 to the first apparatus 110 is referred to as a downlink (DL) , while a link from the first apparatus 110 to the second apparatus 120 is referred to as an uplink (UL) . In the DL, the second apparatus 120 is a transmitting (TX) device (or a transmitter) and the first apparatus 110 is a receiving (RX) device (or a receiver) . In the UL, the first apparatus 110 is a TX device and the second apparatus 120 is a RX device.
[0037] In some example embodiments, the second apparatus 120 may operate as a gNB that utilizes a RAN split architecture where the gNB may comprise a gNB-CU and one or more gNB-DUs. In this architecture, different gNB-DUs may provide one or a plurality of cells to the first apparatus 110.
[0038] It is to be understood that the number of apparatuses and their connections shown in FIG. 1 are only for the purpose of illustration without suggesting any limitation. The communication environment 100 may include any suitable number of apparatuses configured to implement example embodiments of the present disclosure.
[0039] In the communication environment 100, the second apparatus 120 may provide a coverage area, which may be called a serving area. In the serving area, the second apparatus 120 may provide one or more serving cells in which the first apparatus 110 may be served by the second apparatus 120. In a mobility scenario, as the first apparatus 110 moves from a cell towards a neighbor cell, a handover to the neighbor cell may be triggered for the first apparatus 110.
[0040] The MAC based mobility (also referred to as MAC level mobility or MAC mobility) may be enabled in the communication environment 100. In the MAC mobility, the concept of “Cell at MAC” is introduced to grant lower layers, such as a physical (PHY) and the MAC layers, larger autonomy, as shown in FIG. 2 which illustrates a schematic diagram of an example architecture 200 for handover with a single RRC entity. In the concept of “Cell at MAC” , an entity cell is in the scope of a MAC layer and handover between cells is managed at the MAC layer. Packet data convergence protocol (PDCP) and radio link control (RLC) layers are not linked to a single cell and are not re-established during the handover at the MAC layer. In the case that the MAC mobility related feature is deployed in the RAN split architecture, CU-DU signaling exchange may be reduced because the RRC layer (for example, located at a CU) may not be involved during the handover that is managed at the MAC layer (for example, located at a DU) .
[0041] This architecture 200 may achieve several benefits. First, the mobility may be hidden from higher layers (such as PDCP, RLC and even RRC layers) . The re-establishment of PDCP, RLC, and RRC layers may be decoupled from handover. Second, a thin handover procedure may be achieved. Because the mobility is hidden from the RRC layer, the parameter updates related to the handover may contain only MAC and PHY relevant parameters. These parameters may be pre-configured and / or organized in a channel specific manner. For example, a cell switch command via MAC signaling may only include an configuration group identifier (ID) of the target cell. A configuration index of the target cell may be transmitted via a lower layer to a UE. Third, a lean preparation may be achieved. By defining and managing intercell mobility at the MAC layer, it frees the CU (or the entity of the RRC layer) from preparation of candidate cells.
[0042] FIG. 3 shows an example scenario 300 of the MAC based mobility. As shown in FIG. 3, a cell 301 and a cell 303 are on a frequency 1 while a cell 302 and a cell 304 are on a frequency 2. The first apparatus 110 may move among different cells on the same frequency, for example, from the cell 401 to the cell 403, or from the cell 402 to the cell 404. The cells 402 and 404 on the frequency 2 are optional, which may depend on a CA capability of the first apparatus 110, as discussed below.
[0043] The communication environment 100 may further enable carrier aggregation (CA) which may be a deployed feature for LTE and NR. In the CA, different carriers from different cells may be aggregated at the MAC layer and the different carriers may have the same RLC and PDCP layers, which is similar to the architecture 200 in FIG. 2. To enable the CA for the first apparatus 110, the second apparatus 120 may provide a primary cell (PCell) and one or more secondary cells (SCells) serving the first apparatus 110. The SCells may be configured and indicated to the first apparatus 110 by RRC signaling.
[0044] In some implementations, the CA may be used to achieve higher throughput for the first apparatus 110. The carriers in the CA may be on different frequencies and there may be one PCell on a primary carrier and one or more SCells on secondary carrier (s) . The primary carrier may be used to establish a connection to the network. The secondary carriers may be used to provide the first apparatus 110 with additional throughput. The secondary carriers may be added / removed or activated / deactivated without affecting the connectivity. In the CA, if the link quality of the primary carrier is not good, a change of a connection may result in a handover to a new cell. During the handover, the MAC layer may be reset with a hybrid automatic repeat request (HARQ) buffer flushed.
[0045] To enable the CA, CA band combinations may be reported by the first apparatus 110 as a capability of the first apparatus RRC signaling. Table 1 shows an example of a list of the CA band combinations. Table 1
[0046] In some example embodiments, the MAC level mobility may be combined with the CA framework. For example, RRC will pre-configure the potential cells may be pre-configured as SCells via the RRC layer, and a change of a PCell as well as activation / deactivation of the SCells may be performed at the MAC layer. In this case, the MAC entity may need to be aware of the CA band combination capability to ensure that only the cells within the UEs band combination capability are activated.
[0047] In accordance with some example embodiments, there is provided a solution for UE capability checking in the MAC based mobility. In this solution, the second apparatus 120 transmits, to the first apparatus 110, a cell configuration indicating one or more cells for the first apparatus 110. The second apparatus 120 transmits, a cell command associated with at least one cell of the one or more cells. One or more activated cells of the one or more cells does not exceed the capability of the first apparatus.
[0048] In this way, after the MAC level mobility happens, the MAC entity at a network may ensure that it only activates the cells within the capability of a UE, for example, in terms of the band combinations. In this way, the network may not activate serving cells beyond the capability of UEs, thereby improving the efficiency of cell activation and UE mobility.
[0049] It enables MAC layer being aware of the UE CA band combination capabilities for MAC layer mobility with CA framework, so that the NW would not activates serving cells beyond the UEs capability.
[0050] The proposed solution may be based on the concept of “cell at MAC” with a CA framework. FIG. 4 shows an overall procedure 400 of a cell change in MAC mobility with a CA framework according to some example embodiments. In the procedure 400, a UE 401 may be an example of the first apparatus 110. An SCell 403 or a PCell 404, a MAC entity (shortly MAC) 402 or an RRC entity (shortly RRC) 405 may be provided by the second apparatus 120.
[0051] As shown in FIG. 4, the UE 401 may transmit (407) an L3 measurement report to the RRC 405. In some example embodiments, the L3 measurement may be triggered under some events such as the measurement of a neighbor cell is better than a threshold. After the RRC 405 may receive (411) the L3 measurement report, the RRC 405 may send (413) a UE context modification request to the MAC 402, for example, to add or remove a SCell to a UE context. For example, the RRC 405 may decide on adding or removing the SCell 403 and send this decision to the MAC 402 via the UE context modification request. After the MAC 402 receives (415) the UE context modification request, the MAC 402 may send (417) a UE context modification response to the RRC 405. Correspondingly, the RRC 405 may receive (419) the UE context modification response from the MAC 402.
[0052] The RRC 405 may send (421) , to the UE 401, an RRCReconfiguration message which may include a list of cell configurations. The multiple serving cells may include one cell currently operation as the PCell as legacy and other cells as the SCells. In some example embodiments, the RRCReconfiguration message may provide preconfigured common resources for the SCell (s) and unified PSCell / Scell (GCell) configurations. After the UE 401 may receive (427) the RRCReconfiguration message, the UE 401 may send (429) an RRCReconfiguration Complete message to the RRC 405. Correspondingly, the RRC 405 may receive (435) the RRCReconfiguration Complete message.
[0053] The UE 401 may transmit (437) , to the MAC 402, a layer 1 (L1) measurement report to achieve a flexible L1 measurement management. The L1 measurement report may be associated with a CSI feedback and a load condition to help the MAC 402 to make a decision (441) . Correspondingly, the MAC 402 may receive (439) the L1 measurement report from the UE 401. Then, if the MAC mobility happens, the MAC 402 may decide (441) which cell to be a PCell and which cell to be a Scell. In some example embodiments, the decision (441) may be made based on a UE capability at the MAC layer.
[0054] Then, the MAC 402 may transmit (443) the decision result to the UE 401 via a new MAC CE or by reusing the cell switch command carried in a MAC CE defined for LTM. In some example embodiments, the MAC 402 may transmit (443) a MAC message including a delta Scell configuration. The delta Scell configuration may contain a physical uplink control channel (PUCCH) configuration, a dedicated random access channel (RACH) configuration, a synchronization signal block (SSB) measurement timing configuration (SMTC) , and / or a potential timing advance group (TAG) update.
[0055] After the UE 401 receives (445) the MAC message from the MAC 402, the UE 401 may transmit (447) a MAC response to the MAC 402. Correspondingly, the MAC 402 may receive (449) the MAC response from the UE 401.
[0056] The MAC 402 may transmit (451) a MAC-CE command indicating the PCell and SCell activation to the UE 401. The MAC-CE command may indicate a single cell role swap or a cell group role swap and indicate the MAC reset (and RLC reset) . After the UE 401 receives (453) the MAC-CE command, the UE 401 may transmit (455) a MAC-CE SCell activation response to the MAC 402. Then, the UE 401 may move (459) to the new PCell 404 and receive (461) a DL data from the SCell 403 for a higher throughput. In the RAN split architecture, there is no need to update a CU from the MAC 402. If the CU needs to know where the UE is located, the CU may request it from the MAC 402.
[0057] The serving cells preconfigured by the RRC entity may exceed the band combination that the UE supports. According to some example embodiments, the MAC entity may ensure not activating one or more cells beyond the capability of the UE. Some example implementations will be described below with reference to FIG. 5.
[0058] FIG. 5 illustrates a signaling flow showing a process 500 for UE capability checking in MAC based mobility according to some example embodiments of the present disclosure. For the purposes of discussion, the process 500 will be discussed with reference to FIG. 1, for example, by using the first apparatus 110 and the second apparatus 120. In some example embodiments, the first apparatus 110 may be discussed as a terminal device, for example, a UE. The second apparatus 120 may be discussed as a network device, for example, a BS or a gNB.
[0059] In the process 500, the second apparatus 120 transmits (505) , to the first apparatus 110, a cell configuration indicating one or more cells for the first apparatus 110. Correspondingly, the first apparatus 110 receives (510) the cell configuration from the second apparatus 120. In some example embodiments, the cell configuration may be carried in an RRC reconfiguration message.
[0060] In some example embodiments, the one or more cells may include at least one cell exceeding a capability of the first apparatus 110. The capability may be related to any feature supported by the first apparatus 110, such as a carrier or frequency, a band combination, a maximum transmit power and / or the like. In some example embodiments, the capability of the first apparatus may be associated with at least one carrier or frequency supported by the first apparatus 110. The at least one carrier may comprise at least one band combination, for example, as shown in Table 1.
[0061] In an example, RRC preconfigured multiple serving cells indicated by the cell configuration may be on the same frequency or different frequencies. The preconfigured serving cells could exceed the band combination that the first apparatus 110 supports, with the assumption that the MAC entity may ensure not activating them beyond the capability of the first apparatus 110 as will be detailed below. Upon reception of such a configuration, the first apparatus 110 may not consider it as an invalid configuration.
[0062] In some example embodiments, the first apparatus 110 may transmit (501) a first indication of the first apparatus 110 before receiving (510) the cell configuration such that the second apparatus 120 only configures the cells within the capability of the first apparatus 110. Some example embodiments in this regard will be detailed in the following paragraphs.
[0063] After transmitting (505) the cell configuration, the second apparatus 120 transmits (530) , to the first apparatus 110, a cell command associated with at least one cell of the one or more cells. Correspondingly, the first apparatus 110 receives (535) the cell command from the second apparatus 120. In some example embodiments, the cell command may be carried via MAC signaling. One or more activated cells of the one or more cells do not exceed the capability of the first apparatus 110. For example, if one cell is activated for the first apparatus 110, the one activated cell needs to comply with the capability of the first apparatus 110, for example, in terms of carrier frequencies. If two or more cells are activated for the first apparatus 110, the two or more activated cells need to comply with the capability of the first apparatus 110, for example, in terms of band combinations. In this way, it may be ensured that only cells within the capability of the first apparatus 110 are activated.
[0064] To ensure that one or more activated cells do not exceed the capability of the first apparatus 110, in some example embodiments, responsive to receiving the cell configuration, the first apparatus 110 may perform (515) a capability compliance check associated with the one or more cells, based on the capability of the first apparatus 110. For example, the second apparatus 120 may use the cell configuration to indicate, to the first apparatus 110, the SCells for which the capability compliance check may be triggered on reception of an RRC reconfiguration message (for example, including the cell configuration) . For the remaining SCells, the first apparatus 110 may not apply the compliance check against its capability.
[0065] In some example embodiments, the second apparatus 120 may trigger an early verification for the capability of the first apparatus 110 for a potential PCell change by indicating the new set of SCells in the cell configuration. The early verification may reduce the time taken for the first apparatus 110 to do the capability verification at the time of executing the change of the PCell.
[0066] In some example embodiments, if the first apparatus 110 determines, based on the capability compliance check, that one or more cells to be activated in the one or more cells exceeds the capability of the first apparatus 110, the first apparatus 110 may transmit, to the second apparatus 120, a second indication that activation of the one or more cell is failed. The second indication may be transmitted via MAC signaling. In this way, the first apparatus 110 may indicate a capability of handling such a configuration to the network. Alternatively, this indication may be implicitly linked to the capability of MAC mobility with the CA framework, as shown in Table 1.
[0067] Then, when the MAC entity of the second apparatus 120 performs PCell change, and / or activates / deactivates the RRC pre-configured serving cells, the MAC entity may ensure that it only simultaneously activates the serving cells on the carriers that are supported by the first apparatus 110.
[0068] In some other example embodiments, responsive to receiving the cell command, the first apparatus 110 may perform (540) the capability compliance check associated with the at least one cell, based on the capability of the first apparatus 110. The capability compliance check may be done at the MAC layer of the first apparatus 110 upon reception of the indication related to the PCell change and / or SCell activation / deactivation in the cell command.
[0069] Likewise, if it is determined that one or more cells to be activated in the one or more cells exceeds the capability of the first apparatus 110, the first apparatus 110 may transmit, to the second apparatus 120, via the MAC signaling, the second indication that activation of the one or more cell is failed. For example, if an activation command exceeding the capability of the first apparatus 110 is received, the first apparatus 110 may send a failure indication as a MAC CE to the network on the PCell without activating the SCells.
[0070] In some example embodiments, the RRC entity may configure the serving cells in groups and the MAC entity may only activate the cells within the same group. In this case, the first apparatus 110 may check the band combination upon a RRC configuration (as an example of the cell configuration) per group or upon a PCell change at the MAC layer (responsive to the cell command) .
[0071] In some other example embodiments, the capability compliance check may be delegated to the second apparatus 120. In some example embodiments, the cell configuration transmitted by the second apparatus 120 may include a third indication that at least one of the one or more cells exceeds the capability of the first apparatus. For example, the second apparatus 120 may perform the capability compliance check and indicate in the cell configuration that simultaneously configured cells may go beyond the capability of the first apparatus 110, but that the second apparatus 120 assures not to activate configured cells or switch to new cells beyond the band combinations supported by the first apparatus 110.
[0072] Alternatively, the RRC entity of the second apparatus 120 may perform the capability compliance check (or capability check) with the assumption that RRC only configures the cells on the band combination that the first apparatus 110 supports. For example, if the first apparatus 110 does not support CA, then the RRC entity may only configure multiple cells on a single carrier for the MAC layer mobility control. If the first apparatus 110 supports the band combination on different frequencies (for example, frequency 1 and frequency 2 in FIG. 3) , the RRC entity may configure multiple serving cells on each frequency for the MAC mobility. When the serving frequency changes, L3 HO may be needed.
[0073] As described above, in some example embodiments, the first apparatus 110 may transmit (501) the first indication of the first apparatus 110. The first indication may be reported via RRC signaling. For example, the first indication may comprise a list of the at least one band combination shown in Table 1. Correspondingly, the second apparatus 120 may receive (503) the first indication from the first apparatus 110. In this case, based on the first indication, the RRC entity may only configure the cells on the band combination that the first apparatus 110 supports.
[0074] To enable band combination awareness at the MAC layer of the second apparatus 120 in the RAN split architecture with CU / DU split, a CU may inform a DU about a capability of the first apparatus 110 on band combinations and the DU may ensure it only activate the serving cells within the band combination that is supported by the first apparatus 110.
[0075] Alternatively, the capability (in terms of band combinations) may be reported by the first apparatus 110 to the MAC layer of the second apparatus 120 other than to the RRC layer of the second apparatus 120. For example, in some example embodiments, the first indication may be carried via MAC signaling.
[0076] By way of example, taking the scenario 300 of FIG. 3 as an example, the cell 301 on frequency 1 is the cell when the first apparatus 110 gets connected. The RRC entity of the second apparatus 120 may additionally configure the cell 303 on the frequency 1 as a deactivated serving cell as well as the cell 302 and the cell 304 on the frequency 2 as serving cells to the first apparatus 110. The first apparatus 110 does not declare it as an invalid configuration even if the first apparatus 110 does not support a band combination on frequency 1 and frequency 2.
[0077] The MAC entity of the second apparatus 120 may control which cell operates as the PCell and which cell (s) operate as activated SCell (s) to serving the first apparatus 110 without involving the RRC layer. When the MAC layer mobility of the first apparatus 110 triggers a PCell change among the cells 301, 302, 303 and 304 as well as activation / deactivation of the other cells as Scell (s) , it may ensure it only activates the combination of the serving cells supported by the first apparatus 110.
[0078] If the first apparatus 110 supports the band combination on frequency 1 and frequency 2, the network may activate one serving cell on each frequency. Otherwise, it could only activate serving cells on either one of them. The MAC entity of the first apparatus 110 may check the capability compliance and if its capability is exceeded, the first apparatus 110 may declare an SCell activation failure and send a failure indication to the network, e.g. as a MAC CE via the PCell.
[0079] It may enable the MAC entity to be aware of the capability of the first apparatus, for example, in terms of CA band combinations, for the MAC layer mobility with CA framework. Accordingly, the network may not activate serving cells beyond the UEs capability. In some example embodiments, the first apparatus 110 may indicate to the second apparatus 120 that it supports the proposed solution which enables the second apparatus 120 to check whether it can use this optimized solution for the first apparatus 110, and to execute the proposed solution with the first apparatus 110.
[0080] FIG. 6 shows a flowchart of an example method 600 implemented at a first apparatus in accordance with some example embodiments of the present disclosure. For the purpose of discussion, the method 600 will be described from the perspective of the first apparatus 110 in FIG. 1.
[0081] At block 610, the first apparatus 110 receives, from the second apparatus 120, a cell configuration indicating one or more cells.
[0082] At block 620, the first apparatus 110 receives, from the second apparatus 120, a cell command associated with at least one cell of the one or more cells, where one or more activated cells of the one or more cells do not exceed the capability of the first apparatus 110.
[0083] In some example embodiments, the first apparatus 110 may transmit, to the second apparatus 120, a first indication of a capability of the first apparatus 110.
[0084] In some example embodiments, the capability of the first apparatus may be associated with at least one carrier supported by the first apparatus 110.
[0085] In some example embodiments, the at least one carrier may comprise at least one band combination.
[0086] In some example embodiments, the first indication may comprise a list of the at least one band combination.
[0087] In some example embodiments, the one or more cells may include at least one cell exceeding the capability of the first apparatus.
[0088] In some example embodiments, responsive to receiving the cell command, the first apparatus 110 may perform a capability compliance check associated with the at least one cell, based on a capability of the first apparatus 110.
[0089] In some example embodiments, responsive to receiving the cell configuration, the first apparatus 110 may perform a capability compliance check associated with the one or more cells, based on a capability of the first apparatus 110.
[0090] In some example embodiments, in accordance with a determination, based on the capability compliance check, that one or more cells to be activated in the one or more cells exceeds the capability of the first apparatus, the first apparatus 110 may transmit, to the second apparatus 120, a second indication that activation of the one or more cells is failed.
[0091] In some example embodiments, the second indication may be transmitted via MAC signaling.
[0092] In some example embodiments, the cell configuration may comprise a third indication that at least one of the one or more cells exceeds the capability of the first apparatus 110.
[0093] In some example embodiments, the cell command may be carried via MAC signaling.
[0094] In some example embodiments, the cell configuration may be received via RRC signaling.
[0095] In some example embodiments, the first apparatus 110 may comprise a terminal device, and the second apparatus 120 may comprise a network device.
[0096] In some example embodiments, an apparatus capable of performing the method 600 (for example, the first apparatus 110 in FIG. 1) may comprise means for performing the respective operations of the method 800 and / or any of the described one or more example embodiments thereof. The means may be implemented in any suitable form. For example, the means may be implemented in a circuitry or software module. The apparatus may be implemented as or included in the first apparatus 110 in FIG. 1.
[0097] FIG. 7 shows a flowchart of an example method 700 implemented at a second apparatus in accordance with some example embodiments of the present disclosure. For the purpose of discussion, the method 700 will be described from the perspective of the second apparatus 120 in FIG. 1.
[0098] At block 710, the second apparatus 120 transmits, to the first apparatus 110, a cell configuration indicating one or more cells for the first apparatus 110.
[0099] At block 720, the second apparatus 120 transmits, to the first apparatus 110, a cell command associated with at least one cell of the one or more cells, where one or more activated cells of the one or more cells do not exceed the capability of the first apparatus.
[0100] In some example embodiments, the second apparatus 120 may receive, from the first apparatus 110, a first indication of a capability of the first apparatus 110.
[0101] In some example embodiments, the capability of the first apparatus 110 may be associated with at least carrier supported by the first apparatus 110.
[0102] In some example embodiments, the at least one carrier may comprise at least one band combination.
[0103] In some example embodiments, the first indication may comprise a list of at least one band combination.
[0104] In some example embodiments, the one or more cells may include at least one cell exceeding a capability of the first apparatus 110.
[0105] In some example embodiments, the second apparatus 120 may receive, from the first apparatus 110, a second indication that activation of one or more cells to be activated in the one or more cells is failed.
[0106] In some example embodiments, the second indication may be transmitted via MAC signaling.
[0107] In some example embodiments, the cell configuration may comprise a third indication that at least one of the one or more cells exceeds the capability of the first apparatus 110.
[0108] In some example embodiments, at least one of the first indication or the cell command may be carried via MAC signaling.
[0109] In some example embodiments, the cell configuration may be received via RRC signaling.
[0110] In some example embodiments, the first apparatus 110 may comprise a terminal device, and the second apparatus 110 may comprise a network device.
[0111] In some example embodiments, an apparatus capable of performing the method 700 (for example, the second apparatus 120 in FIG. 1) may comprise means for performing the respective operations of the method 700 and / or any of the described one or more example embodiments thereof. The means may be implemented in any suitable form. For example, the means may be implemented in a circuitry or software module. The apparatus may be implemented as or included in the second apparatus 120 in FIG. 1.
[0112] FIG. 8 is a simplified block diagram of a device 800 that is suitable for implementing example embodiments of the present disclosure. The device 800 may be provided to implement a communication device, for example, the first apparatus 110 or the second apparatus 120 as shown in FIG. 1. As shown, the device 800 includes one or more processors 810, one or more memories 820 coupled to the processor 810, and one or more communication modules 840 coupled to the processor 810.
[0113] The communication module 840 is for bidirectional communications. The communication module 840 has one or more communication interfaces to facilitate communication with one or more other modules or devices. The communication interfaces may represent any interface that is necessary for communication with other network elements. In some example embodiments, the communication module 840 may include at least one antenna.
[0114] The processor 810 may be of any type suitable to the local technical network and may include one or more of the following: general purpose computers, special purpose computers, microprocessors, digital signal processors (DSPs) and processors based on multicore processor architecture, as non-limiting examples. The device 800 may have multiple processors, such as an application specific integrated circuit chip that is slaved in time to a clock which synchronizes the main processor.
[0115] The memory 820 may include one or more non-volatile memories and one or more volatile memories. Examples of the non-volatile memories include, but are not limited to, a Read Only Memory (ROM) 824, an electrically programmable read only memory (EPROM) , a flash memory, a hard disk, a compact disc (CD) , a digital video disk (DVD) , an optical disk, a laser disk, and other magnetic storage and / or optical storage. Examples of the volatile memories include, but are not limited to, a random-access memory (RAM) 822 and other volatile memories that will not last in the power-down duration.
[0116] A computer program 830 includes computer executable instructions that are executed by the associated processor 810. The instructions of the program 830 may include instructions for performing operations / acts of some example embodiments of the present disclosure. The program 830 may be stored in the memory, e.g., the ROM 824. The processor 810 may perform any suitable actions and processing by loading the program 1030 into the RAM 822.
[0117] The example embodiments of the present disclosure may be implemented by means of the program 830 so that the device 800 may perform any process of the disclosure as discussed with reference to FIG. 1 to FIG. 7. The example embodiments of the present disclosure may also be implemented by hardware or by a combination of software and hardware.
[0118] In some example embodiments, the program 830 may be tangibly contained in a computer readable medium which may be included in the device 800 (such as in the memory 820) or other storage devices that are accessible by the device 800. The device 800 may load the program 830 from the computer readable medium to the RAM 822 for execution. In some example embodiments, the computer readable medium may include any types of non-transitory storage medium, such as ROM, EPROM, a flash memory, a hard disk, CD, DVD, and the like. The term “non-transitory, ” as used herein, is a limitation of the medium itself (i.e., tangible, not a signal) as opposed to a limitation on data storage persistency (e.g., RAM vs. ROM) .
[0119] FIG. 9 shows an example of the computer readable medium 900 which may be in form of CD, DVD or other optical storage disk. The computer readable medium 900 has the program 830 stored thereon.
[0120] Generally, various embodiments of the present disclosure may be implemented in hardware or special purpose circuits, software, logic or any combination thereof. Some aspects may be implemented in hardware, and other aspects may be implemented in firmware or software which may be executed by a controller, microprocessor or other computing device. Although various aspects of embodiments of the present disclosure are illustrated and described as block diagrams, flowcharts, or using some other pictorial representations, it is to be understood that the block, apparatus, system, technique or method described herein may be implemented in, as non-limiting examples, hardware, software, firmware, special purpose circuits or logic, general purpose hardware or controller or other computing devices, or some combination thereof.
[0121] Some example embodiments of the present disclosure also provide at least one computer program product tangibly stored on a computer readable medium, such as a non-transitory computer readable medium. The computer program product includes computer-executable instructions, such as those included in program modules, being executed in a device on a target physical or virtual processor, to carry out any of the methods as described above. Generally, program modules include routines, programs, libraries, objects, classes, components, data structures, or the like that perform particular tasks or implement particular abstract data types. The functionality of the program modules may be combined or split between program modules as desired in various embodiments. Machine-executable instructions for program modules may be executed within a local or distributed device. In a distributed device, program modules may be located in both local and remote storage media.
[0122] Program code for carrying out methods of the present disclosure may be written in any combination of one or more programming languages. The program code may be provided to a processor or controller of a general-purpose computer, special purpose computer, or other programmable data processing apparatus, such that the program code, when executed by the processor or controller, cause the functions / operations specified in the flowcharts and / or block diagrams to be implemented. The program code may execute entirely on a machine, partly on the machine, as a stand-alone software package, partly on the machine and partly on a remote machine or entirely on the remote machine or server.
[0123] In the context of the present disclosure, the computer program code or related data may be carried by any suitable carrier to enable the device, apparatus or processor to perform various processes and operations as described above. Examples of the carrier include a signal, computer readable medium, and the like.
[0124] The computer readable medium may be a computer readable signal medium or a computer readable storage medium. A computer readable medium may include but not limited to an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any suitable combination of the foregoing. More specific examples of the computer readable storage medium would include an electrical connection having one or more wires, a portable computer diskette, a hard disk, a random-access memory (RAM) , a read-only memory (ROM) , an erasable programmable read-only memory (EPROM or Flash memory) , an optical fiber, a portable compact disc read-only memory (CD-ROM) , an optical storage device, a magnetic storage device, or any suitable combination of the foregoing.
[0125] Further, although operations are depicted in a particular order, this may not be understood as requiring that such operations be performed in the particular order shown or in sequential order, or that all illustrated operations be performed, to achieve desirable results. In certain circumstances, multitasking and parallel processing may be advantageous. Likewise, although several specific implementation details are contained in the above discussions, these may not be construed as limitations on the scope of the example embodiments, but rather as descriptions of features that may be specific to particular embodiments. Unless explicitly stated, certain features that are described in the context of separate embodiments may also be implemented in combination in a single embodiment. Conversely, unless explicitly stated, various features that are described in the context of a single embodiment may also be implemented in a plurality of embodiments separately or in any suitable sub-combination.
[0126] Although the present disclosure has been described in languages specific to structural features and / or methodological acts, it is to be understood that the present disclosure defined in the appended claims is not necessarily limited to the specific features or acts described above. Rather, the specific features and acts described above are disclosed as example forms of implementing the claims.
Claims
1.A first apparatus comprising:at least one processor; andat least one memory storing instructions that, when executed by the at least one processor, cause the first apparatus at least to:receive, from a second apparatus, a cell configuration indicating one or more cells; andreceive, from the second apparatus, a cell command associated with at least one cell of the one or more cells,wherein one or more activated cells of the one or more cells do not exceed the capability of the first apparatus.2.The first apparatus of claim 1, wherein the first apparatus is further caused to:transmit, to the second apparatus, a first indication of a capability of the first apparatus.3.The first apparatus of claim 2, wherein the capability of the first apparatus is associated with at least one carrier supported by the first apparatus.4.The first apparatus of claim 3, wherein the at least one carrier comprises at least one band combination.5.The first apparatus of claim 4, wherein the first indication comprises a list of the at least one band combination.6.The first apparatus of any of claims 1 to 5, wherein the one or more cells include at least one cell exceeding the capability of the first apparatus.7.The first apparatus of any of claims 1 to 6, wherein the first apparatus is further caused to:responsive to receiving the cell command, perform a capability compliance check associated with the at least one cell, based on a capability of the first apparatus.8.The first apparatus of any of claims 1 to 6, wherein the first apparatus is further caused to:responsive to receiving the cell configuration, perform a capability compliance check associated with the one or more cells, based on a capability of the first apparatus.9.The first apparatus of claim 7 or 8, wherein the first apparatus is further caused to:in accordance with a determination, based on the capability compliance check, that one or more cells to be activated in the one or more cells exceeds the capability of the first apparatus; andtransmit, to the second apparatus, a second indication that activation of the one or more cell is failed.10.The first apparatus of claim 9, wherein the second indication is transmitted via medium access control (MAC) signaling.11.The first apparatus of any of claims 1 to 10, wherein the cell configuration includes a third indication that at least one of the one or more cells exceeds the capability of the first apparatus.12.The first apparatus of any of claims 1 to 11, wherein at least one of the first indication or the cell command is carried via medium access (MAC) signaling.13.The first apparatus of any of claims 1 to 12, wherein the cell configuration is received via radio resource signaling (RRC) signaling.14.The first apparatus of any claims of 1 to 13, wherein the first apparatus comprises a terminal device, and the second apparatus comprises a network device.15.A second apparatus comprising:at least one processor; andat least one memory storing instructions that, when executed by the at least one processor, cause the second apparatus at least to:transmit, to a first apparatus, a cell configuration indicating one or more cells for the first apparatus; andtransmit, to the first apparatus, a cell command associated with at least one cell of the one or more cells,wherein one or more activated cells of the one or more cells do not exceed the capability of the first apparatus.16.The second apparatus of claim 15, wherein the second apparatus is further caused to:receive, from the first apparatus, a first indication of a capability of the first apparatus.17.The second apparatus of claim 16, wherein the capability of the first apparatus is associated with at least carrier supported by the first apparatus.18.The second apparatus of claim 17, wherein the at least one carrier comprises at least one band combination.19.The second apparatus of claim 18, wherein the first indication comprises a list of at least one band combination.20.The second apparatus of any of claims 15 to 19, wherein the one or more cells include at least one cell exceeding a capability of the first apparatus.21.The second apparatus of any of claims 15 to 20, wherein the second apparatus is further caused to:receive, from the first apparatus, a second indication that activation of one or more cells to be activated in the one or more cells is failed.22.The second apparatus of claim 21, wherein the second indication is transmitted via medium access control (MAC) signaling.23.The second apparatus of any of claims 15 to 22, wherein the cell configuration comprises a third indication that at least one of the one or more cells exceeds the capability of the first apparatus.24.The second apparatus of any of claims 15 to 23, wherein at least one of the first indication or the cell command is carried via medium access (MAC) signaling.25.The second apparatus of any of claims 15 to 24, wherein the cell configuration is received via radio resource signaling (RRC) signaling.26.The second apparatus of any of claims 15 to 25, wherein the first apparatus comprises a terminal device, and the second apparatus comprises a network device.27.A method comprising:at a first apparatus,receiving, from a second apparatus, a cell configuration indicating one or more cells; andreceiving, from the second apparatus, a cell command associated with at least one cell of the one or more cells,wherein one or more activated cells of the one or more cells do not exceed the capability of the first apparatus.28.A method comprising:at a second apparatus,transmitting, to a first apparatus, a cell configuration indicating one or more cells for the first apparatus; andtransmitting, to the first apparatus, a cell command associated with at least one cell of the one or more cells,wherein one or more activated cells of the one or more cells do not exceed the capability of the first apparatus.29.A first apparatus comprising:means for receiving, from a second apparatus, a cell configuration indicating one or more cells; andmeans for receiving, from the second apparatus, a cell command associated with at least one cell of the one or more cells,wherein one or more activated cells of the one or more cells do not exceed the capability of the first apparatus.30.A second apparatus comprising:means for transmitting, to a first apparatus, a cell configuration indicating one or more cells for the first apparatus; andmeans for transmitting, to the first apparatus, a cell command associated with at least one cell of the one or more cells,wherein one or more activated cells of the one or more cells do not exceed the capability of the first apparatus.31.A computer readable medium comprising instructions stored thereon for causing an apparatus at least to perform the method of claim 27 or the method of claim 28.