Support of multiple carriers in energy-saving network

CN118901266APending Publication Date: 2024-11-05LENOVO (BEIJING) LTD
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202280094642.5
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Filing Date
2022-06-13
Publication Date
2024-11-05

Smart Images

  • Figure CN118901266A_ABST
    Figure CN118901266A_ABST
Patent Text Reader

Abstract

Methods and apparatus for ensuring traffic performance are disclosed. The UE comprises a processor; and a transceiver coupled to the processor, where the processor is configured to receive, via the transceiver, a configuration of a mapping restriction for a logical channel, and select the logical channel for the UL grant if a state associated with the UL grant satisfies the mapping restriction for the logical channel.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] The subject matter disclosed herein relates generally to wireless communications, and more particularly to methods and apparatus for support of multiple carriers in energy-efficient networks. Background Art

[0002] The following abbreviations are defined herein, at least some of which are referred to in the following description: New Radio (NR), Very Large Scale Integration (VLSI), Random Access Memory (RAM), Read Only Memory (ROM), Erasable Programmable Read Only Memory (EPROM or Flash Memory), Compact Disc Read Only Memory (CD-ROM), Local Area Network (LAN), Wide Area Network (WAN), User Equipment (UE), Evolved Node B (eNB), Next Generation Node B (gNB), Uplink (UL), Downlink (DL), Central Processing Unit (CPU), Graphics Processing Unit (GPU), Field Programmable Gate Array (FPGA), Orthogonal Frequency Division Multiplexing (OFDM), Radio Resource Control (RRC), User Entity / Equipment (Mobile Terminal), Transmitter (TX), Receiver (RX), Media Access Media Access Control (MAC), Control Element (CE), Logical Channel Priority (LCP), Configuration Grant (CG), Downlink Control Information (DCI), Carrier Aggregation (CA), Dual Connectivity (DC), (NAS), Primary Cell (PCell), Secondary Cell (SCell), Primary Secondary Cell (PSCell), Conditional PSCell Addition (CPA), Conditional PSCell Change (CPC), Primary Cell Group (MCG), Secondary Cell Group (SCG), Packet Data Convergence Protocol (PDCP), Protocol Data Unit (PDU), Radio Link Control (RLC), Radio Bearer (RB), Data Radio Bearer (DRB), Quality of Service (QoS), Packet Delay Budget (PDB), Information Element (IE), Synchronization Signal Block (SSB), Transmission Reception Point (TRP).

[0003] A UE that supports the features of network energy-saving technology may be referred to as a new UE. A UE that does not support the features of network energy-saving technology may be referred to as a legacy UE. A cell that supports the features of network energy-saving technology may be referred to as a new cell. A cell that does not support the features of network energy-saving technology may be referred to as a legacy cell.

[0004] The new cell may have different states, for example, a non-sleeping state and multiple sleeping states.

[0005] However, in example scenarios including single carrier and multi-carrier deployments, the priorities of different cells in different states are discussed.

[0006] The present invention is aimed at the above-mentioned problems. Summary of the invention

[0007] A method and apparatus for ensuring service performance are disclosed.

[0008] In one embodiment, the UE includes a processor; and a transceiver coupled to the processor, wherein the processor is configured to receive, via the transceiver, a configuration of mapping restrictions for logical channels, and select a logical channel for the UL grant if a state associated with the UL grant satisfies the mapping restrictions for the logical channels.

[0009] In some embodiments, the state associated with the UL grant is indicated in the DCI that schedules the UL grant, or if the UL grant is a configuration grant, the state associated with the UL grant is indicated in the configuration of the configuration grant. Specifically, the DCI or the configuration of the configuration grant explicitly indicates the state associated with the UL grant, or implicitly indicates the state associated with the UL grant through a longer or shorter interval between scheduling signaling and transmission or between transmission and feedback.

[0010] In some embodiments, the state associated with the UL grant is the state of the cell from which the UL grant is received. Specifically, the state of the cell is identified by one of an indication of a state transition, a broadcast message, a cell on / off duration, reduced SSB or free SSB or normal SSB, and TRP on or off.

[0011] In some embodiments, the mapping restriction for the logical channel is a list of allowed states, and if the state associated with the UL grant is included in the list of allowed states, the state associated with the UL grant satisfies the mapping restriction for the logical channel.

[0012] In some embodiments, the mapping restriction of the logical channel is an allowed state, and if the state associated with the UL grant is the allowed state, the state associated with the UL grant satisfies the mapping restriction on the logical channel.

[0013] In some embodiments, the mapping restriction of the logical channel is an indication of whether the energy saving mode is allowed, and if the energy saving mode corresponding to the state associated with the UL grant matches the indication, the state associated with the UL grant satisfies the mapping restriction on the logical channel.

[0014] In another embodiment, a method performed by a UE includes receiving a configuration of mapping restrictions on logical channels, and selecting a logical channel for a UL grant if a state associated with the UL grant satisfies the mapping restrictions on the logical channels.

[0015] In yet another embodiment, the base station unit includes a processor; and a transceiver coupled to the processor, wherein the processor is configured to transmit, via the transceiver, a configuration of mapping restrictions on logical channels, wherein the mapping restrictions on logical channels are used to select logical channels for a UL grant associated with a state.

[0016] In some embodiments, the mapping constraints on the logical channels are a list of allowed states.

[0017] In some embodiments, the mapping restriction on the logical channel is an allowed state.

[0018] In some embodiments, the mapping of logical channels is restricted to an indication of whether power saving mode is allowed.

[0019] In yet another embodiment, a method performed by a base station unit includes transmitting a configuration of mapping restrictions to logical channels, wherein the mapping restrictions to logical channels are used to select a logical channel for a UL grant associated with a state. BRIEF DESCRIPTION OF THE DRAWINGS

[0020] A more particular description of the embodiments briefly described above will be presented by reference to specific embodiments shown in the accompanying drawings. Understanding that these drawings depict only some embodiments and are therefore not to be considered limiting of scope, the embodiments will be described and explained with additional specificity and detail through the use of the accompanying drawings, in which:

[0021] Figure 1 is a schematic flow chart illustrating an embodiment of a method;

[0022] Figure 2 is a schematic flow chart illustrating other embodiments of the method;

[0023] Figure 3 is a schematic flow chart illustrating another embodiment of the method;

[0024] Figure 4 is a schematic flow chart illustrating other embodiments of the method; and

[0025] Figure 5 is a schematic block diagram illustrating an apparatus according to one embodiment. DETAILED DESCRIPTION

[0026] As will be appreciated by those skilled in the art, certain aspects of the embodiments may be embodied as systems, devices, methods or program products. Thus, the embodiments may take the form of a complete hardware embodiment, a complete software embodiment (including firmware, resident software, microcode, etc.), or an embodiment combining software and hardware aspects, which are generally referred to herein as "circuits", "modules" or "systems". In addition, the embodiments may take the form of a program product embodied in one or more computer-readable storage devices storing machine-readable code, computer-readable code and / or program code (hereinafter referred to as "code"). The storage device may be tangible, non-temporary and / or non-transmitting. The storage device may not embody a signal. In a certain embodiment, the storage device employs only a signal for accessing the code.

[0027] Certain functional units described in this specification may be labeled as "modules" to more particularly emphasize their independent implementation. For example, a module may be implemented as a hardware circuit including a custom very large scale integration (VLSI) circuit or gate array, an off-the-shelf semiconductor such as a logic chip, a transistor, or other discrete components. A module may also be implemented in a programmable hardware device such as a field programmable gate array, a programmable array logic, a programmable logic device, etc.

[0028] Modules can also be implemented in code and / or software for execution by various types of processors. The identified code module can, for example, include one or more physical or logical blocks of executable code, which can, for example, be organized as objects, processes, or functions. However, the executable files of the identified modules do not need to be physically located together, but can include different instructions stored in different locations, which, when logically connected together, include the module and achieve the stated purpose of the module.

[0029] In fact, code modules can include a single instruction or multiple instructions, and can even be distributed on several different code segments, between different programs and across several memory devices. Similarly, operating data can be identified and illustrated in this article within the module, and can be embodied in any suitable form and organized within the data structure of any suitable type. The operating data can be collected as a single data set, or can be distributed in different locations, including being distributed on different computer-readable storage devices. When a module or part of a module is implemented with software, the software portion is stored on one or more computer-readable storage devices.

[0030] Any combination of one or more computer readable media may be utilized. The computer readable medium may be a computer readable storage medium. The computer readable storage medium may be a storage device storing code. The storage device may be, for example but not necessarily, an electronic, magnetic, optical, electromagnetic, infrared, holographic, micromechanical or semiconductor system, apparatus or device, or any suitable combination of the foregoing.

[0031] A non-exhaustive list of more specific examples of storage devices would include the following: an electrical connection with one or more cables, a portable computer floppy disk, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), a portable compact disk read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing. In the context of this document, a computer-readable storage medium may be any tangible medium that can contain or store a program for use by or in conjunction with an instruction execution system, apparatus, or device.

[0032] The code for performing the operations of the embodiments may include any number of lines and may be written in any combination of one or more programming languages, including object-oriented programming languages ​​such as Python, Ruby, Java, Smalltalk, C++, etc., as well as traditional procedural programming languages ​​such as the "C" programming language, etc., and / or machine languages ​​such as assembly language. The code may be executed entirely on the user's computer, partially on the user's computer, as a separate software package, partially on the user's computer and partially on a remote computer, or entirely on a remote computer or server. In the last scenario, the remote computer may be connected to the user's computer through any type of network, including a local area network (LAN) or a wide area network (WAN), or may be connected to an external computer (e.g., via the Internet using an Internet service provider).

[0033] References to "one embodiment", "embodiment" or similar language throughout this specification mean that a particular feature, structure or characteristic described in conjunction with the embodiment is included in at least one embodiment. Therefore, unless otherwise expressly specified, the phrases "in one embodiment", "in an embodiment" and similar language throughout this specification may, but not necessarily, all refer to the same embodiment, but rather mean "one or more but not all embodiments". Unless otherwise expressly specified, the terms "include", "comprising", "having" and their variations mean "including but not limited to". Unless otherwise expressly specified, the list of items listed does not mean that any or all items are mutually exclusive. Unless otherwise expressly specified, the terms "one", "an" and "the" also refer to "one or more".

[0034] In addition, the described features, structures or characteristics of the various embodiments may be combined in any suitable manner. In the following description, many specific details are provided, such as examples of programming, software modules, user selections, network transactions, database queries, database structures, hardware modules, hardware circuits, hardware chips, etc., to provide a thorough understanding of the embodiments. However, those skilled in the relevant art will recognize that the embodiments may be practiced without one or more of the specific details or using other methods, components, materials, etc. In other cases, well-known structures, materials or operations are not shown or described in detail to avoid any ambiguity in various aspects of the embodiments.

[0035] The various aspects of different embodiments are described below with reference to the schematic flow charts and / or schematic block diagrams of the methods, devices, systems and program products according to the embodiments. It will be understood that each frame of the schematic flow chart and / or schematic block diagram, and the combination of frames in the schematic flow chart and / or schematic block diagram can be implemented by code. The code can be provided to a processor of a general-purpose computer, a special-purpose computer or other programmable data processing device to produce a machine, so that instructions executed by the processor of the computer or other programmable data processing device create a device for implementing the functions specified in the schematic flow chart and / or schematic block diagram for one or more frames.

[0036] The code may also be stored in a storage device that can instruct a computer, other programmable data processing apparatus, or other device to function in a specific manner so that the instructions stored in the storage device produce a product including instructions for implementing the functions specified in the schematic flowchart and / or schematic block diagram.

[0037] The code may also be loaded onto a computer, other programmable data processing apparatus, or other device so that a series of operational steps are performed on the computer, other programmable apparatus, or other device to produce a computer-implemented process, so that the code executed on the computer or other programmable apparatus provides a process for implementing the functions specified in the flowcharts and / or block diagrams in one or more blocks.

[0038] The schematic flow charts and / or schematic block diagrams in the accompanying drawings illustrate the architecture, functionality, and operation of possible implementations of devices, systems, methods, and program products according to various embodiments. In this regard, each box in the schematic flow charts and / or schematic block diagrams may represent a module, segment, or portion of code, which includes one or more executable instructions of the code for implementing (one or more) specified logical functions.

[0039] It should also be noted that in some alternative implementations, the functions annotated in the blocks may not occur in the order noted in the drawings. For example, two blocks shown in succession may be executed substantially simultaneously, or the blocks may sometimes be executed in the reverse order, depending on the functions involved. Other steps and methods may be envisioned that are equivalent in function, logic, or effect to one or more blocks or portions thereof of the illustrated drawings.

[0040] Although various arrow types and line types can be adopted in flow chart and / or block diagram, they are understood to not limit the scope of corresponding embodiment.In fact, some arrows or other connectors can be used to indicate only the logical flow of the described embodiment.For example, the waiting or monitoring period of the unspecified duration between the enumeration steps of the described embodiment can be indicated by an arrow.It will be noted that each frame in the block diagram and / or flow chart and the combination of the frames in the block diagram and / or flow chart can be realized by a system based on dedicated hardware or a combination of dedicated hardware and code that performs a specified function or action.

[0041] The description of an element in each figure may refer to an element of a previous figure. The same reference numerals in all figures refer to the same elements, including alternative embodiments of the same elements.

[0042] Reference will now be made in detail to some embodiments of the present application, examples of which are illustrated in the accompanying drawings. For ease of understanding, embodiments are provided in specific network architectures and new service scenarios, such as 3GPP 5G, 3GPP LTE, 3GPP NR-U, NR radio access operating with shared spectrum channel access, etc. It is envisioned that with the development of network architectures and new service scenarios, all embodiments in the present application are also applicable to similar technical problems. In addition, the terms cited in the present application may change, which should not affect the principles of the present application. The embodiments disclosed herein can also be applied to unlicensed spectrum scenarios.

[0043] To make the description clearer, several concepts are explained.

[0044] For example, a UE in an idle (e.g., RRC_IDLE) state, camps on a cell. This means that the UE is able to receive system information broadcast by a base station unit (e.g., gNB) that manages the cell. For example, a UE in a connected (e.g., RRC_CONNECTED) state, is served by at least one cell. This means that for each of the at least one cell, the UE communicates with the gNB that manages the cell.

[0045] The new cell supporting the network energy-saving technical features may be in a non-sleep state (e.g., normal state, active state, etc.) or in a sleep state. The new cell being in a sleep state means that the new cell is in a low energy consumption state. There may be multiple sleep states, such as micro sleep, shallow sleep, deep sleep, etc. (note that the name of each sleep state may be different from the micro sleep state, shallow sleep state and / or deep sleep state. For example, multiple sleep states may be alternatively low-level sleep states, medium-level sleep states, high-level sleep states, etc.). Each sleep state corresponds to a different energy consumption level, and different energy consumption levels may be represented by different state transition times, or by different reference parameters or different configurations or different configuration cycles, or by different TX power levels, or by different power consumption levels, or by different resource allocation levels, etc. Each of the different levels may be less than 100%. The new cell being in a non-sleep state means that the new cell can utilize all levels of energy. Accordingly, the state transition time, or TX power, or power consumption, or resource allocation, etc. in the non-sleep state can be less than or equal to 100%, or can be higher than the level in the sleep state.

[0046] The first embodiment is directed to ensuring service performance in an energy efficient network.

[0047] Legacy UEs can access a new cell (or multiple new cells). This means that the new cell can serve both new UEs and legacy UEs. To save energy, if there is no latency-critical traffic to the new UE, the new cell can respond to the new UE in a longer duration than a legacy UE in the same cell, or compared to a new UE with latency-critical traffic.

[0048] According to the prior art, the UL grant scheduled or allocated by the network is per MAC entity, not per service. When a new transmission is performed, the MAC entity should allocate UL resources to the logical channel used for the service through the UL grant. Under the condition that the delay requirement of the service in the UE (e.g., a new UE) is relatively high, if UL resources are allocated to the UE for energy saving purposes, such UL resources can be allocated to the logical channel for the service with high delay requirements, because there is no restriction preventing UL resources from being allocated for the service with high delay requirements for energy saving purposes. Therefore, the service with high delay requirements will be transmitted on inappropriate UL resources.

[0049] This problem exists in both single-carrier and multi-carrier scenarios.

[0050] Whenever a new transmission is performed, the Logical Channel Prioritization (LCP) procedure is applied.

[0051] According to the first embodiment, mapping restrictions are added to the LCP procedure. The RRC configuration may control the LCP procedure by configuring mapping restrictions for each logical channel.

[0052] The mapping restriction for each logical channel can be (1) "allowedstate-List" consisting of a list of allowed states, (2) "allowedstate", or (3) "nesallowed".

[0053] The UL grant contains UL resources. If the state associated with the UL grant satisfies the mapping restriction configured to the logical channel, a logical channel can be selected for the UL grant (ie, UL resources).

[0054] The state associated with the UL grant may be indicated explicitly or implicitly. The indication can be indicated in the DCI that schedules the UL grant or in the configuration of the CG (configuration grant). For example, when the state associated with the UL grant is indicated in the configuration of the DCI or CG, the state associated with the UL grant can be explicitly indicated as corresponding to the energy-saving mode or the normal mode (ie, not the energy-saving mode). On the other hand, if a longer interval between the scheduling signaling and the transmission or between the transmission and the feedback is indicated in the configuration of the DCI or CG, the state associated with the UL grant is implicitly indicated as the energy-saving mode; while if a shorter interval is indicated, the state associated with the UL grant is implicitly indicated as the normal state. In addition, if a cell (eg, a new cell) only serves new UEs, the state associated with the UL grant can be regarded as the same as the state of the cell. In this case, the indication of the state of the cell can be regarded as implicitly indicating the state associated with the UL grant. The state of the cell can be indicated in one of the following ways. In the first way, the state of the cell can be indicated by an indication of a state transition or a broadcast message. In the second manner, if the on / off duration of the cell is semi-statically configured, the state of the cell can be derived from the on / off duration of the cell. In the third manner, if the cell is configured as reduced SSB (which means reducing the transmission and / or reception of SSB, for example, by increasing the period, or by transmitting and / or receiving on demand, or by occupying fewer symbols) or free SSB (which means not transmitting and / or receiving SSB) or TRP off, the state of the cell is implicitly indicated as corresponding to the energy saving mode; and if the cell is configured as normal SSB or TRP on, the state of the cell is implicitly indicated as corresponding to the normal mode.

[0055] When the mapping is restricted to (1) "allowedstate-List" consisting of a list of allowed states, a UL grant (i.e., UL resources) can be allocated to each logical channel that satisfies the following condition: the state associated with the UL grant is included in the list of allowed states of the logical channel. This means that a logical channel that satisfies the following condition: the state associated with the UL grant is included in the list of allowed states configured for each logical channel can be selected for each UL grant.

[0056] For the first example, the light sleep state is included in the "allowedstate-List" of the logical channel. The logical channel can be selected for the UL grant associated with the energy saving mode corresponding to the light sleep state (ie, the light sleep state associated with the UL grant is included in the "allowedstate-List" of the logical channel).

[0057] For the second example, the non-sleep state is included in the "allowedstate-List" of the logical channel (which implies that the light sleep state is not included in the "allowedstate-List" of the logical channel). A logical channel cannot be selected for a UL grant associated with a power saving mode corresponding to the light sleep state (i.e., the light sleep state associated with the UL grant is not included in the "allowedstate-List" of the logical channel).

[0058] The allowed states listed in "allowedstate-List" can alternatively be replaced with different levels of energy saving, corresponding to different levels of energy saving gains or different levels of network sleep or different levels of energy consumption or different levels of energy efficiency or different levels of latency. For example, a high level of energy saving may correspond to a deep sleep state, a medium level of energy saving may correspond to a light sleep state, and a low level of energy saving may correspond to a micro sleep state.

[0059] When the mapping restriction is (2) "allowedstate" indicating an allowed state, a UL grant (i.e., UL resources) can be allocated to each logical channel that satisfies the condition that the state associated with the UL grant is the allowed state. This means that a logical channel that satisfies the following condition can be selected for each UL grant: the state associated with the UL grant is the allowed state configured for each logical channel.

[0060] For example, the "allowedstate" of the logical channel is a sleep state (eg, it means any one of a deep sleep state, a light sleep state, and a micro sleep state). The logical channel can be selected for a UL grant associated with a power saving mode corresponding to any sleep state (eg, a light sleep state).

[0061] The mapping restriction may be (3) "nesallowed", which indicates whether the network energy saving mode is allowed. "nesallowed" can be set to "true" or "false". Alternatively, nesallowed can default to "false" and can be set to "true". Also alternatively, nesallowed can default to "true" and can be set to "false". If the energy saving mode corresponding to the state associated with the UL grant matches the nesallowed of the logical channel, the logical channel can be selected for the UL grant.

[0062] When a logical channel is configured with nesallowed defaulted or set to "true", if the state associated with the UL grant corresponds to the energy saving mode, the logical channel can be selected for the UL grant. If the state associated with the UL grant does not correspond to the energy saving mode, the logical channel cannot be selected for the UL grant.

[0063] When a logical channel is configured with nesallowed defaulted or set to "false", if the state associated with the UL grant corresponds to the energy saving mode, the logical channel cannot be selected for the UL grant. If the state associated with the UL grant does not correspond to the energy saving mode, the logical channel can be selected for the UL grant.

[0064] The second embodiment is directed to adding SCells in a carrier aggregation (CA) or dual connectivity (DC) scenario when considering the potential sleep state of the SCells.

[0065] When carrier aggregation (CA) is configured, the UE has only one RRC connection with the network. One serving cell provides NAS mobility information at RRC connection establishment, re-establishment and handover, and one serving cell provides security input at RRC connection re-establishment and handover. One serving cell is called a primary cell (PCell). Depending on the UE capabilities, a secondary cell (SCell) can be configured to form a set of serving cells together with the PCell. The configured set of serving cells for a UE consists of one PCell and one or more SCells. In the case of CA, the UE has only one MAC entity.

[0066] When dual connectivity (DC) is configured, the UE has two MAC entities. One MAC entity is used to connect to the Master Cell Group (MCG), which consists of a set of serving cells, including the primary cell (PCell) and possibly one or more SCells. The other MAC entity is used to connect to the Secondary Cell Group (SCG), which consists of a set of serving cells, including the Primary Secondary Cell (PSCell) and possibly one or more SCells.

[0067] In both CA and DC, SCells can be added to or deleted from the UE.

[0068] A brief introduction of conditional PSCell addition CPA and conditional PSCell change (CPC) is described as follows. Once the configured measurement conditions for the candidate target SpCell are met, conditional PSCell addition (CPA) or conditional PSCell change (CPC) is performed. The state of the additional or changed PSCell can be indicated.

[0069] Traditionally, a cell (e.g., SCell) can have only two alternating states, including an active state (or activated state) and an inactive state (or deactivated state). SCell can be activated (i.e., set to an active state or activated state) or deactivated (i.e., set to an inactive state or deactivated state) by signaling.

[0070] With the introduction of potential multiple states (eg, non-sleep state and multiple sleep states), SCell can be added to UE to save energy. When SCell is added to UE, it is not enough to just set SCell to active state or inactive state (eg, activated or deactivated).

[0071] According to the second embodiment, at the time of configuration or modification or activation of a service cell of an MCG or a service cell of an MCG other than a PCell or a service cell of an SCG or a service cell of an SCG other than a PSCell or SCell, or at the time of reconfiguration in conditional reconfiguration for CPA (Conditional PSCell Addition) or CPC (Conditional PSCell Change), if the cell is a new cell, the state of the service cell can be set.

[0072] The potential states of the serving cell can be, but are not limited to: an activated state, a sleep state or different levels of sleep states (eg, a deep sleep state, a light sleep state, a micro sleep state), a non-sleep state, a deactivated state, a dormant state, etc.

[0073] All potential states can be in parallel. This means that the serving cell can be set to one of the potential states.

[0074] Alternatively, the state can be classified into two levels. For example, the sleep state or different levels of sleep states (e.g., deep sleep state, light sleep state, micro sleep state) and / or the non-sleep state can be a lower state of any one of the activation state, the deactivation state, and the dormancy state. For example, if the deep sleep state, the light sleep state, the micro sleep state, and the non-sleep state are lower states of the activation state, the serving cell can be set to the activation state, and further set to the light sleep state.

[0075] If all potential states are in parallel, the state of the SCell (which is the new cell) can be set to

[0076] (1) one of an active state, a sleep state, or different levels of sleep states (e.g., a deep sleep state, a light sleep state, a micro-sleep state), a non-sleep state, and a deactivated state; or

[0077] (2) one of an active state, a sleep state, or different levels of sleep states (e.g., a deep sleep state, a light sleep state, a micro-sleep state), a non-sleep state, a deactivated state, and a dormant state; or

[0078] (3) One of an active state, a sleep state, or different levels of sleep states (e.g., a deep sleep state, a light sleep state, a micro-sleep state), and a non-sleep state.

[0079] If there are two levels of potential states, after setting the state of the SCell (which is a new cell) to a state with a lower state (e.g., an activated state, a deactivated state, or a dormant state), the state of the SCell can be further set. For example, the state of the SCell can be set to:

[0080] (4) an activation state (which is a state with subordinate states), and is further set to one of a sleep state and a non-sleep state (if there is only one sleep state), or is further set to one of different levels of sleep states (e.g., deep sleep state, light sleep state, micro-sleep state) and non-sleep state (if there are different levels of sleep states); or

[0081] (5) a deactivated state (which is a state having lower-level states), and further set to one of a sleep state and a non-sleep state (if there is only one sleep state), or further set to one of different levels of sleep states (e.g., a deep sleep state, a light sleep state, a micro-sleep state) and a non-sleep state (if there are different levels of sleep states); or

[0082] (6) A dormant state (which is a state having lower-level states), and is further set to one of a sleep state and a non-sleep state (if there is only one sleep state), or is further set to one of different levels of sleep states (e.g., a deep sleep state, a light sleep state, a micro-sleep state) and a non-sleep state (if there are different levels of sleep states).

[0083] An example IE of (4) above could be:

[0084]

[0085] In the above example, the SCell is in a deactivated state by default. It can be set to an activated state, and further set to one of a non-sleep state, a low-level sleep state, a medium-level sleep state, and a high-level sleep state.

[0086] The PCell or PSCell (which is a new cell) can be set to: a sleep state or different levels of sleep states (eg, a deep sleep state, a light sleep state, a micro sleep state), and a non-sleep state.

[0087] A sample IE for setting up the PCell is as follows:

[0088]

[0089] The example IE for setting up the PSCell is as follows:

[0090]

[0091] In general, each of the SCell, PCell, and PSCell (which is a new cell) can be set to at least one sleep state or one of different levels of sleep states (eg, deep sleep state, light sleep state, micro sleep state) or a non-sleep state.

[0092] Conventionally, a legacy serving cell (eg, SCell, PCell, or PSCell) can be activated or deactivated to one state (eg, activated state or deactivated state) by indicating a MAC CE (eg, SCell activation / deactivation MAC CE for activating or deactivating the state of the SCell).

[0093] With the introduction of a sleep state or different levels of sleep states (eg, deep sleep state, light sleep state, micro sleep state) and a non-sleep state, a new serving cell (eg, SCell, PCell, or PSCell) can be set as one of the potential states through a MAC CE.

[0094] If all potential states are in parallel, the new SCell can be set to one of the potential states through the state indication MAC CE. The number of bits used to indicate the set state contained in the state indication MAC CE can be designed according to the number of potential states. Generally, 3 bits are required to indicate 5 to 8 parallel potential states. For example, if the potential state includes 5 states: an activated state, a deep sleep state, a light sleep state, a non-sleep state, and a deactivated state, 3 bits are required to indicate one of the 5 potential states.

[0095] If there are two levels of potential states, and the sleep state or different levels of sleep states (e.g., deep sleep state, light sleep state, micro sleep state) and non-sleep are lower-level states, the traditional indication MAC CE can be used to set the first-level state if necessary. For example, the traditional indication MAC CE can set the state of the SCell (e.g., activated or deactivated) to an activated state or a deactivated state. If the set state (e.g., activated state) has a lower-level state (e.g., deep sleep state, light sleep state, micro sleep state, non-sleep state), an additional indication MAC CE containing 2 bits for indicating one of the 4 lower-level sleep states can be used to further set the state.

[0096] The state indication MAC CE can be used to indicate the state of the new SpCell (which is a PCell or a PSCell). The number of bits used to indicate the state of the setting contained in the state indication MAC CE (used to indicate the state of the new SpCell) can be designed according to the number of potential states for the new SpCell. For example, if the potential state for the new SpCell includes 4 states: deep sleep state, light sleep state, micro sleep state, and non-sleep, 2 bits are required to indicate one of the 4 potential states.

[0097] If one status indication MAC CE is used to indicate the status of a plurality of serving cells, the status indication for each serving cell can be arranged in octets in one status indication MAC CE.

[0098] The status indication MAC CE can be identified by a MAC subheader with a new LCID.

[0099] If the SCell is configured with an sCellState set to the state at the time of SCell configuration, or an SCell state transition related MAC CE is received, which transitions the SCell to a state (where the state can be deactivated, for example, a sleep state or different levels of sleep states (for example, a deep sleep state, a light sleep state, a micro sleep state), a non-sleep state, or a dormant state), and allows the UE to transmit or receive data or signaling, then a timer associated with the SCell (for example, sCellDeactivationTimer) is started or restarted.

[0100] Alternatively, if the SCell is configured with an sCellState set to the state at the time of SCell configuration, or an SCell state transition related MAC CE is received which transitions the SCell to a state (wherein the state is not fully activated, e.g., a sleep state) and allows the UE to transmit or receive data or signaling, then a timer associated with the SCell (e.g., sCellDeactivationTimer) is stopped.

[0101] The third embodiment involves split bearer and PDCP duplication.

[0102] When a PDCP PDU is submitted to lower layers, the transmitting PDCP entity may be associated with at least two RLC entities (eg, two RLC entities associated with different cells).

[0103] If PDCP duplication is activated for the RB, the PDCP data PDU can be duplicated and submitted to the associated RLC entity activated for PDCP duplication.

[0104] If PDCP duplication is disabled for the RB, a separate secondary RLC entity is configured, and the total amount of PDCP data and RLC data waiting for initial transmission in the primary RLC entity and the separate secondary RLC entity is equal to or greater than ul-DataSplitThreshold, the PDCP PDU is submitted to the primary RLC entity or the separate secondary RLC entity.

[0105] According to the third embodiment, the state of the cell associated with the RLC entity (especially the potential dormant state of the cell) is taken into account in splitting the bearer and PDCP duplication.

[0106] Specifically, under the condition that PDCP replication is deactivated for the RB and a separated secondary RLC entity is configured, if the total amount of PDCP data and RLC data waiting for initial transmission in the primary RLC entity and the separated secondary RLC entity is equal to or greater than a threshold (e.g., ul-DataSplitThreshold), then if the states of the cells associated with both the primary RLC entity and the separated secondary RLC entity meet the performance requirements of the DRB, the PDCP PDU is submitted to the primary RLC entity or the separated secondary RLC entity, or the PDCP PDU is submitted to one of the primary RLC entity and the separated secondary RLC entity, which is associated with a cell that is in a state that is more active (e.g., a shorter transition time) than the state of another cell associated with the other of the primary RLC entity and the separated secondary RLC entity.

[0107] Under the condition that PDCP duplication is activated for an RB, whether the PDCP data PDU can be duplicated and submitted to the associated RLC entity activated for PDCP duplication depends on the state of the cell associated with the RLC entity.

[0108] First rule: NG-RAN shall ensure that at least one serving cell is activated for each activated RLC entity of a DRB and that the status of the activated cells can meet the performance requirements of the DRB.

[0109] Second rule: If the status of each activated cell associated with the activated RLC entity of the DRB cannot meet the performance requirements of the DRB, the duplication of the DRB is disabled.

[0110] Third rule: If the status of any activated cell associated with the activated RLC entity of the DRB cannot meet the performance requirements of the DRB, the activated cell is deactivated.

[0111] All of the above rules can be applied to activation / deactivation of autonomous or network-based replication.

[0112] Whether the state of the cell associated with the RLC entity meets the performance requirement of the DRB is determined by referring to the configuration of the network or the first embodiment or the service QoS.

[0113] For example, PDB is greater than threshold #1, a medium (or light) level of sleep state or non-sleep state can be acceptable.

[0114] For another example, if PDB is less than threshold #2, the non-sleep state may be acceptable.

[0115] On the other hand, if the cell associated with one of the RLC entities of the split bearer is in a sleep state (e.g., light sleep state, deep sleep state), it can be considered that the cell does not meet the performance requirements of the DRB. This means that data will not be delivered to the RLC entity associated with the cell in any sleep state.

[0116] Figure 1 1 is a schematic flow chart illustrating an embodiment of a method 100 according to the present application. In some embodiments, the method 100 is performed by a device such as a remote unit (UE). In some embodiments, the method 100 may be performed by a processor that executes program code, for example, a microcontroller, a microprocessor, a CPU, a GPU, an auxiliary processing unit, an FPGA, etc.

[0117] The method 100 may be performed by a UE and includes 102 receiving a configuration of mapping restrictions on logical channels, and 104 selecting a logical channel for a UL grant if a state associated with the UL grant satisfies the mapping restrictions on the logical channels.

[0118] In some embodiments, the state associated with the UL grant is indicated in the DCI that schedules the UL grant, or if the UL grant is a configuration grant, it is indicated in the configuration of the configuration grant. Specifically, the DCI or the configuration of the configuration grant explicitly indicates the state associated with the UL grant, or implicitly indicates the state associated with the UL grant through a longer or shorter interval between scheduling signaling and transmission or between transmission and feedback.

[0119] In some embodiments, the state associated with the UL grant is the state of the cell from which the UL grant is received. Specifically, the state of the cell is identified by one of a state transition indication, a broadcast message, an on / off duration of the cell, a reduced SSB or a free SSB or a normal SSB, and a TRP on or off.

[0120] In some embodiments, the mapping restriction for the logical channel is a list of allowed states, and if the state associated with the UL grant is included in the list of allowed states, the state associated with the UL grant satisfies the mapping restriction for the logical channel.

[0121] In some embodiments, the mapping restriction of the logical channel is an allowed state, and if the state associated with the UL grant is the allowed state, the state associated with the UL grant satisfies the mapping restriction on the logical channel.

[0122] In some embodiments, the mapping restriction of the logical channel is an indication of whether the energy saving mode is allowed, and if the energy saving mode corresponding to the state associated with the UL grant matches the indication, the state associated with the UL grant satisfies the mapping restriction on the logical channel.

[0123] Figure 2 2 is a schematic flow chart illustrating other embodiments of the method 200 according to the present application. In some embodiments, the method 200 is performed by a device such as a base station unit or a network device. In some embodiments, the method 200 can be performed by a processor that executes program code, for example, a microcontroller, a microprocessor, a CPU, a GPU, an auxiliary processing unit, an FPGA, etc.

[0124] The method 200 may be performed by a base station unit and includes 202 transmitting a mapping restriction configuration for a logical channel, wherein the mapping restriction for the logical channel is used to select a logical channel for a UL grant associated with a state.

[0125] In some embodiments, the mapping constraints on the logical channels are a list of allowed states.

[0126] In some embodiments, the mapping restriction on the logical channel is an allowed state.

[0127] In some embodiments, the mapping of logical channels is restricted to an indication of whether power saving mode is allowed.

[0128] Figure 3 300 is a schematic flow chart illustrating an embodiment of a method 300 according to the present application. In some embodiments, the method 300 is performed by a device such as a remote unit (UE). In some embodiments, the method 300 can be performed by a processor that executes program code, for example, a microcontroller, a microprocessor, a CPU, a GPU, an auxiliary processing unit, an FPGA, etc.

[0129] The method 300 may be performed by a UE and includes 302, when configuring, modifying or activating a cell for the UE, receiving configuration of a cell state, wherein the cell state includes at least one of a non-sleep state and a sleep state or different levels of sleep states.

[0130] In some embodiments, the method further comprises submitting the PDCP PDU associated with the DRB to the RLC entity if a state of a cell associated with the RLC entity meets the performance requirements of the DRB.

[0131] When a separate secondary RLC entity is configured, the method includes submitting a PDCP PDU to the primary RLC entity or the separate secondary RLC entity if states of cells associated with both the primary RLC entity and the separate secondary RLC entity meet performance requirements of the DRB.

[0132] In another embodiment, at least one cell is activated for each RLC entity, and the status of the activated cell meets the performance requirement of the DRB.

[0133] Figure 4 4 is a schematic flow chart illustrating other embodiments of the method 400 according to the present application. In some embodiments, the method 400 is performed by an apparatus, such as a base station unit or a network device. In some embodiments, the method 400 can be performed by a processor that executes program code, for example, a microcontroller, a microprocessor, a CPU, a GPU, an auxiliary processing unit, an FPGA, etc.

[0134] The method 400 may be performed by a base station unit and includes 402 transmitting a configuration of a cell state to a UE when configuring, modifying or activating a cell for the UE, wherein the state of the serving cell includes at least one of a non-sleeping state and a sleeping state or different levels of sleeping states.

[0135] Figure 5 is a schematic block diagram illustrating an apparatus according to one embodiment.

[0136] refer to Figure 5 , UE (ie, remote unit or terminal equipment) includes a processor, a memory and a transceiver. Processor implementation Figure 1 The functions, processes and / or methods proposed in.

[0137] The UE includes a processor; and a transceiver coupled to the processor, wherein the processor is configured to receive a configuration of a mapping restriction for a logical channel via the transceiver, and select a logical channel for the UL grant if a state associated with the UL grant satisfies the mapping restriction for the logical channel.

[0138] In some embodiments, the state associated with the UL grant is indicated in the DCI that schedules the UL grant, or if the UL grant is a configuration grant, it is indicated in the configuration of the configuration grant. Specifically, the DCI or the configuration of the configuration grant explicitly indicates the state associated with the UL grant, or implicitly indicates the state associated with the UL grant through a longer or shorter interval between scheduling signaling and transmission or between transmission and feedback.

[0139] In some embodiments, the state associated with the UL grant is the state of the cell from which the UL grant is received. Specifically, the state of the cell is identified by one of a state transition indication, a broadcast message, an on / off duration of the cell, a reduced SSB or a free SSB or a normal SSB, and a TRP on or off.

[0140] In certain embodiments, the mapping restriction for the logical channel is a list of allowed states, and the state associated with the UL grant satisfies the mapping restriction for the logical channel if the state associated with the UL grant is included in the list of allowed states.

[0141] In some embodiments, the mapping restriction of the logical channel is an allowed state, and if the state associated with the UL grant is the allowed state, the state associated with the UL grant satisfies the mapping restriction on the logical channel.

[0142] In some embodiments, the mapping restriction of the logical channel is an indication of whether the energy saving mode is allowed, and if the energy saving mode corresponding to the state associated with the UL grant matches the indication, the state associated with the UL grant satisfies the mapping restriction on the logical channel.

[0143] The processor can also implement Figure 3 The functions, processes and / or methods proposed in.

[0144] The UE includes a processor; and a transceiver coupled to the processor, wherein the processor is configured to receive a configuration of a cell state via the transceiver when configuring, modifying, or activating a cell for the UE, wherein the cell state includes at least one of a non-sleep state and a sleep state or different levels of sleep states.

[0145] In some embodiments, the method further comprises submitting the PDCP PDU associated with the DRB to the RLC entity if a state of a cell associated with the RLC entity meets the performance requirements of the DRB.

[0146] When a separate secondary RLC entity is configured, the method includes submitting a PDCP PDU to the primary RLC entity or the separate secondary RLC entity if states of cells associated with both the primary RLC entity and the separate secondary RLC entity meet performance requirements of the DRB.

[0147] In another embodiment, at least one cell is activated for each RLC entity, and the status of the activated cell meets the performance requirement of the DRB.

[0148] refer to Figure 5 , gNB (i.e., base station unit or network equipment) includes a processor, memory, and a transceiver. Processor implementation Figure 2 The functions, processes and / or methods proposed in.

[0149] The base station unit includes a processor; and a transceiver coupled to the processor, wherein the processor is configured to transmit, via the transceiver, a configuration of mapping restrictions on logical channels, wherein the mapping restrictions on logical channels are used to select logical channels for state-associated UL grants.

[0150] In some embodiments, the mapping constraints on the logical channels are a list of allowed states.

[0151] In some embodiments, the mapping restriction on the logical channel is an allowed state.

[0152] In some embodiments, the mapping of logical channels is restricted to an indication of whether power saving mode is allowed.

[0153] The processor (of the base unit) can also implement Figure 4 The functions, processes and / or methods proposed in.

[0154] The base station unit includes a processor; and a transceiver, which is coupled to the processor, wherein the processor is configured to transmit the configuration of the cell status to the UE via the transceiver when configuring, modifying or activating a cell for the UE, wherein the status of the serving cell includes at least one of a non-sleep state and a sleep state or different levels of sleep states.

[0155] The wireless interface protocol layer can be implemented by a processor. The memory is connected to the processor to store various information for driving the processor. The transceiver is connected to the processor to transmit and / or receive radio signals. Needless to say, the transceiver can be implemented as a transmitter for transmitting radio signals and a receiver for receiving radio signals.

[0156] The memory may be located inside or outside the processor and connected to the processor through various well-known means.

[0157] In the above-described embodiments, the components and features of the embodiments are combined in a predetermined form. Unless otherwise clearly stated, each component or feature should be considered as an option. Each component or feature can be implemented as not being associated with other components or features. Further, the embodiment can be configured by associating some components and / or features. The order of the operations described in the embodiment can be changed. Some components or features of any embodiment can be included in another embodiment or replaced with components and features corresponding to another embodiment. It is obvious that claims that are not clearly cited in the claims are combined to form embodiments or are included in new claims.

[0158] The embodiments may be implemented by hardware, firmware, software or a combination thereof. In the case of hardware implementation, the exemplary embodiments described herein may be implemented using one or more application specific integrated circuits (ASICs), digital signal processors (DSPs), digital signal processing devices (DSPDs), programmable logic devices (PLDs), field programmable gate arrays (FPGAs), processors, controllers, microcontrollers, microprocessors, etc., according to the hardware implementation.

[0159] Embodiments may be practiced in other specific forms. The described embodiments are to be considered in all respects as merely illustrative and not restrictive. Therefore, the scope of the present invention is indicated by the appended claims rather than by the foregoing description. All changes within the meaning and scope of the equivalents of the claims are encompassed within their scope.

Claims

1. A user equipment (UE), the UE comprising: processor; as well as a transceiver coupled to the processor, Wherein, the processor is configured to receiving, via the transceiver, a configuration of mapping restrictions for logical channels, and If a state associated with an uplink (UL) grant satisfies a mapping restriction on the logical channel, the logical channel is selected for the UL grant.

2. The UE according to claim 1, wherein: The status associated with the UL grant is indicated in downlink control information (DCI) scheduling the UL grant, or in the configuration of the configuration grant if the UL grant is a configuration grant.

3. The UE according to claim 2, wherein: The DCI or the configuration of the configuration grant explicitly indicates the state associated with the UL grant, or implicitly indicates the state associated with the UL grant through a longer or shorter interval between scheduling signaling and transmission or between transmission and feedback.

4. The UE according to claim 1, wherein: The state associated with the UL grant is a state of a cell from which the UL grant was received.

5. The UE according to claim 4, wherein: The state of the cell is identified by one of the following: Indication of state transitions, Broadcast messages, the on / off duration of the cell, Reduced Synchronization Signal Block (SSB) or SSB-free or normal SSB, and Transmission Reception Point (TRP) is turned on or off.

6. The UE according to claim 1, wherein: The mapping restriction of the logical channel is a list of allowed states, and if the state associated with the UL grant is included in the list of allowed states, the state associated with the UL grant satisfies the mapping restriction on the logical channel.

7. The UE according to claim 1, wherein: The mapping restriction of the logical channel is an allowed state, and if the state associated with the UL grant is the allowed state, the state associated with the UL grant satisfies the mapping restriction on the logical channel.

8. The UE according to claim 1, wherein: The mapping restriction of the logical channel is an indication of whether the energy saving mode is allowed. If the energy saving mode corresponding to the state associated with the UL grant matches the indication, the state associated with the UL grant satisfies the mapping restriction on the logical channel.

9. A method at a user equipment (UE), comprising: receiving a configuration of mapping constraints for logical channels, and If the state associated with the UL grant satisfies the mapping restriction on the logical channel, the logical channel is selected for the UL grant.

10. A base station unit, comprising: processor; as well as a transceiver coupled to the processor, Wherein, the processor is configured to transmitting, via the transceiver, a configuration of mapping restrictions to logical channels, The mapping restriction on the logical channel is used to select the logical channel for a UL grant associated with a state.

11. The base station unit according to claim 10, wherein: The mapping constraints for the logical channel are a list of allowed states.

12. The base station unit according to claim 10, wherein: The mapping restriction on the logical channel is in the allowed state.

13. The base station unit according to claim 10, wherein: The mapping restriction to the logical channel is an indication of whether the energy saving mode is allowed.