[go: up one dir, main page]

WO2020231311A1 - Signalisation de couche 1 (l1) permettant une gestion rapide de cellules secondaires (scell) - Google Patents

Signalisation de couche 1 (l1) permettant une gestion rapide de cellules secondaires (scell) Download PDF

Info

Publication number
WO2020231311A1
WO2020231311A1 PCT/SE2020/050445 SE2020050445W WO2020231311A1 WO 2020231311 A1 WO2020231311 A1 WO 2020231311A1 SE 2020050445 W SE2020050445 W SE 2020050445W WO 2020231311 A1 WO2020231311 A1 WO 2020231311A1
Authority
WO
WIPO (PCT)
Prior art keywords
scell
command
periodicity
pdcch
monitoring
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Ceased
Application number
PCT/SE2020/050445
Other languages
English (en)
Inventor
Ravikiran Nory
Ajit Nimbalker
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Telefonaktiebolaget LM Ericsson AB
Original Assignee
Telefonaktiebolaget LM Ericsson AB
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Telefonaktiebolaget LM Ericsson AB filed Critical Telefonaktiebolaget LM Ericsson AB
Publication of WO2020231311A1 publication Critical patent/WO2020231311A1/fr
Anticipated expiration legal-status Critical
Ceased legal-status Critical Current

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L5/00—Arrangements affording multiple use of the transmission path
    • H04L5/0001—Arrangements for dividing the transmission path
    • H04L5/0003—Two-dimensional division
    • H04L5/0005—Time-frequency
    • H04L5/0007—Time-frequency the frequencies being orthogonal, e.g. OFDM(A) or DMT
    • H04L5/001—Time-frequency the frequencies being orthogonal, e.g. OFDM(A) or DMT the frequencies being arranged in component carriers
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L5/00—Arrangements affording multiple use of the transmission path
    • H04L5/003—Arrangements for allocating sub-channels of the transmission path
    • H04L5/0053—Allocation of signalling, i.e. of overhead other than pilot signals
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L5/00—Arrangements affording multiple use of the transmission path
    • H04L5/0091—Signalling for the administration of the divided path, e.g. signalling of configuration information
    • H04L5/0094—Indication of how sub-channels of the path are allocated

Definitions

  • the present disclosure relates to wireless communications, and in particular, to Open Systems Interconnect (OSI) Layer 1 (LI) signaling for fast secondary cell (Scell) management (e.g., as compared to existing arrangements).
  • OSI Open Systems Interconnect
  • LI Layer 1
  • Carrier Aggregation is generally used in the 3 rd Generation Partnership Project (3GPP) New Radio (NR) (also known as“5G”) and Long-Term Evolution (LTE) systems to improve wireless device (WD) (e.g., user equipment (UE)) transmit and receive data rates.
  • 3GPP 3rd Generation Partnership Project
  • NR New Radio
  • LTE Long-Term Evolution
  • the WD typically operates initially on a single serving cell called a primary cell (Pcell).
  • the Pcell is operated on a component carrier in a frequency band.
  • the WD is then configured by the network (e.g., network node) with one or more secondary serving cells (Scell(s)).
  • Scell(s) secondary serving cells
  • Each Scell can correspond to a component carrier (CC) in the same frequency band (intra-band CA) or different frequency band (inter-band CA) from the frequency band of the CC corresponding to the Pcell.
  • CC component carrier
  • inter-band CA component carrier
  • the Scell(s) should be activated by the network, e.g., the network node.
  • the Scell(s) can also be deactivated and later reactivated as needed via activation/deactivation signaling.
  • FIG. 1 illustrates an example of Scell activation/deactivation related procedures specified for 3GPP Release 15 (Rel-15) New Radio (NR).
  • CSI channel state information
  • the WD is allowed to start performing other‘activation related actions’ (e.g., physical downlink control channel (PDCCH) monitoring for Scell, physical uplink control channel
  • PDCCH physical downlink control channel
  • PUCCH Physical Uplink Control Channel
  • SRS sounding reference signal
  • Some embodiments advantageously provide methods and apparatuses for LI signalling for fast secondary cell (Scell) management, e.g., fast carrier aggregation (CA) Scell management.
  • Scell secondary cell
  • CA fast carrier aggregation
  • a method for a network node includes signalling a command, e.g., layer 1 command, the layer 1 command activating/deactivating a secondary cell for the WD.
  • a command e.g., layer 1 command
  • a method for a wireless device includes receiving a command, e.g., layer 1 command, the layer 1 command
  • Scell secondary cell
  • a method for a WD includes receiving a command, e.g., layer 1 command, the layer 1 command modifying a PDCCH monitoring periodicity associated with a Scell.
  • a method implemented a wireless device, WD, configured to operate on at least one secondary cell, Scell includes receiving a Layer 1, LI, command in a downlink control information, DCI, on a primary cell, PCell; and responsive to receiving the LI command, adapting a periodicity for monitoring a physical downlink control channel, PDCCH, on at least one Scell of the at least one Scell based at least in part on the LI command.
  • adapting the periodicity includes if the received command indicates a first periodicity: responsive to receiving the LI command, performing PDCCH monitoring on the at least one Scell according to the first periodicity; and if the received command indicates a second periodicity:
  • the LI command received in the DCI is a physical layer command.
  • the WD is configured to operate on N Scells and each Scell of the N Scells is configured with one or more bandwidth parts, BWPs; and the LI command includes, for each Scell of the N Scells, a number of bits that indicate one or more periodicities for monitoring the PDCCH on the
  • the number of bits is based at least in part on a number of BWPs that the corresponding Scell is configured with.
  • a method implemented a network node configured to configure a wireless device, WD, to operate on at least one secondary cell, Scell.
  • the method includes sending a Layer 1, LI, command in a downlink control information, DCI, on a primary cell, PCell, the LI command indicating a periodicity for monitoring a physical downlink control channel, PDCCH, on at least one Scell of the at least one Scell.
  • the sending the LI command in the DCI further includes sending the LI command indicating one of a first periodicity for the monitoring the PDCCH on the at least one Scell and a second periodicity for the monitoring the PDCCH on the at least one Scell, the first periodicity being different from the second periodicity.
  • the first periodicity is less than the second periodicity.
  • the second periodicity indicates stopping the PDCCH monitoring on the at least one Scell.
  • the LI command in the DCI is a physical layer command.
  • the method further includes configuring the WD to operate on N Scells and configuring each Scell of the N Scells with one or more bandwidth parts, BWPs; and the LI command includes, for each Scell of the N Scells, a number of bits that indicate one or more periodicities for monitoring the PDCCH on the corresponding Scell and the number of bits is based at least in part on a number of BWPs that the corresponding Scell is configured with.
  • a wireless device configured to operate on at least one secondary cell, Scell.
  • the WD includes processing circuitry.
  • the processing circuitry is configured to cause the WD to receive a Layer 1, LI, command in a downlink control information, DCI, on a primary cell, PCell; and responsive to receiving the LI command, adapt a periodicity for monitoring a physical downlink control channel, PDCCH, on at least one Scell of the at least one Scell based at least in part on the LI command.
  • PDCCH physical downlink control channel
  • the processing circuitry is configured to adapt the periodicity by being configured to: if the received command indicates a first periodicity: responsive to receiving the LI command, perform PDCCH monitoring on the at least one Scell according to the first periodicity; and if the received command indicates a second periodicity: responsive to receiving the LI command, perform PDCCH monitoring on the at least one Scell according to the second periodicity, the first periodicity being different from the second periodicity.
  • the first periodicity is less than the second periodicity.
  • the second periodicity indicates performing the PDCCH monitoring by stopping the PDCCH monitoring on the at least one Scell.
  • the LI command received in the DCI is a physical layer command.
  • the WD is configured to operate on N Scells and each Scell of the N Scells is configured with one or more bandwidth parts, BWPs; and the LI command includes, for each Scell of the N Scells, a number of bits that indicate one or more periodicities for monitoring the PDCCH on the corresponding Scell and the number of bits is based at least in part on a number of BWPs that the corresponding Scell is configured with.
  • a network node configured to configure a wireless device, WD, to operate on at least one secondary cell, Scell.
  • the network node includes processing circuitry.
  • the processing circuitry is configured to cause the network node to send a Layer 1, LI, command in a downlink control information, DCI, on a primary cell, PCell, the LI command indicating a periodicity for monitoring a physical downlink control channel, PDCCH, on at least one Scell of the at least one Scell.
  • the processing circuitry is configured to send the LI command in the DCI by being configured to send the LI command indicating one of a first periodicity for the monitoring the PDCCH on the at least one Scell and a second periodicity for the monitoring the PDCCH on the at least one Scell, the first periodicity being different from the second periodicity.
  • the first periodicity is less than the second periodicity.
  • the second periodicity indicates stopping the PDCCH monitoring on the at least one Scell.
  • the LI command in the DCI is a physical layer command.
  • the processing circuitry is further configured to configure the WD to operate on N Scells and configure each Scell of the N Scells with one or more bandwidth parts, BWPs; and the LI command includes, for each Scell of the N Scells, a number of bits that indicate one or more periodicities for monitoring the PDCCH on the corresponding Scell and the number of bits is based at least in part on a number of BWPs that the corresponding Scell is configured with.
  • FIG. 1 illustrates an example of Scell activation/deactivation in 3GPP NR Rel- 15;
  • FIG. 2 is a schematic diagram of an exemplary network architecture illustrating a communication system connected via an intermediate network to a host computer according to the principles in the present disclosure
  • FIG. 3 is a block diagram of a host computer communicating via a network node with a wireless device over an at least partially wireless connection according to some embodiments of the present disclosure
  • FIG. 4 is a flowchart illustrating exemplary methods implemented in a communication system including a host computer, a network node and a wireless device for executing a client application at a wireless device according to some embodiments of the present disclosure
  • FIG. 5 is a flowchart illustrating exemplary methods implemented in a communication system including a host computer, a network node and a wireless device for receiving user data at a wireless device according to some embodiments of the present disclosure
  • FIG. 6 is a flowchart illustrating exemplary methods implemented in a communication system including a host computer, a network node and a wireless device for receiving user data from the wireless device at a host computer according to some embodiments of the present disclosure
  • FIG. 7 is a flowchart illustrating exemplary methods implemented in a communication system including a host computer, a network node and a wireless device for receiving user data at a host computer according to some embodiments of the present disclosure
  • FIG. 8 is a flowchart of an exemplary process in a network node for Scell management unit according to some embodiments of the present disclosure
  • FIG. 9 is a flowchart of an exemplary process in a wireless device for operational unit according to some embodiments of the present disclosure.
  • FIG. 10 is a flowchart of another exemplary process in a network node for Scell management unit according to some embodiments of the present disclosure.
  • FIG. 11 is a flowchart of another exemplary process in a wireless device for operational unit according to some embodiments of the present disclosure.
  • FIG. 12 illustrates an example of a first embodiment of the present disclosure
  • FIG. 13 illustrates an example of a second embodiment of the present disclosure
  • FIG. 14 illustrates an example of a third embodiment of the present disclosure.
  • a CA activation command may be sent in a Medium Access Control (MAC) control element (CE).
  • MAC Medium Access Control
  • CE Medium Access Control
  • the minimum required activation delay is ⁇ 5 ms for a typical case. This is quite slow as compared to other NR procedures. Also, the maximum allowed activation delays are quite long as compared to other NR procedures. Due to such long delays, it is riskier for the network (e.g., network node) to frequently deactivate the Scell, since bringing the wireless device back to Scell activated state can take a minimum of ⁇ 5 ms to a maximum allowed value of tens or hundreds of milliseconds depending on specific scenarios and wireless device implementation.
  • the network e.g., network node
  • some embodiments of the present disclosure provide mechanisms for faster Scell operation when compared to existing LTE or NR CA approaches. This can be accomplished by introducing new OSI Layer 1 (LI), i.e., physical layer, commands in addition to the existing MAC CE based higher layer signaling.
  • OSI Layer 1 i.e., physical layer
  • the MAC CE based Scell activation/deactivation commands may control a first set of WD procedures/actions associated with the Scell [e.g., a) CSI reporting for Scell, b) PDCCH monitoring for SCell, c) PUCCH/SRS transmissions on the SCell]
  • the LI commands may control a second set of WD procedures/actions [e.g., a) PDCCH monitoring for SCell, b) PUCCH/SRS transmissions on the SCell, c) bandwidth part (BWP) switching on Scell]
  • the WD can receive both MAC CE based activation/deactivation commands and LI based commands
  • the time for the WD to apply the second set of actions may be smaller than the time needed for applying the first set of actions (associated with the MAC CE based signaling).
  • the proposed mechanisms may enable the network to control Scell procedures more dynamically by sending frequent LI commands while continuing to use the MAC CE based activation/deactivation mechanism relatively infrequently. From the WD perspective, additional power savings can be achieved with this mechanism when compared with the current approach of only using MAC CE based activation/deactivation commands.
  • the WD receives an LI command in PDCCH downlink control information (DCI) with bit(s) corresponding to one or more SCell(s).
  • DCI downlink control information
  • the WD may use the bit(s) corresponding to the first Scell to turn on/tum off PDCCH monitoring for that SCell.
  • the WD may use the bit(s) corresponding to the second Scell to determine a BWP (of the multiple BWPs) to use for operation on the second SCell.
  • the WD may be configured with zero PDCCH candidates on one of the multiple BWPs configured for the second SCell
  • the PDCCH monitoring periodicity for one or more Scells may be modified based at least in part on the LI command in PDCCH DCI with bit(s) corresponding to one or more SCell(s), as described herein.
  • Some embodiments of proposed LI command structures can provide different options with varying trade-offs between flexibility and overhead to control Scell management actions for Scells with one or more configured BWPs.
  • relational terms such as“first” and“second,”“top” and “bottom,” and the like, may be used solely to distinguish one entity or element from another entity or element without necessarily requiring or implying any physical or logical relationship or order between such entities or elements.
  • the terminology used herein is for the purpose of describing particular embodiments only and is not intended to be limiting of the concepts described herein.
  • the singular forms“a”,“an” and“the” are intended to include the plural forms as well, unless the context clearly indicates otherwise.
  • the joining term,“in communication with” and the like may be used to indicate electrical or data communication, which may be accomplished by physical contact, induction, electromagnetic radiation, radio signaling, infrared signaling or optical signaling, for example.
  • electrical or data communication may be accomplished by physical contact, induction, electromagnetic radiation, radio signaling, infrared signaling or optical signaling, for example.
  • the term“coupled,”“connected,” and the like may be used herein to indicate a connection, although not necessarily directly, and may include wired and/or wireless connections.
  • network node can be any kind of network node comprised in a radio network which may further comprise any of base station (BS), radio base station, base transceiver station (BTS), base station controller (BSC), radio network controller (RNC), g Node B (gNB), evolved Node B (eNB or eNodeB), Node B, multi -standard radio (MSR) radio node such as MSR BS, multi-cell/multicast coordination entity (MCE), integrated access and backhaul (IAB) node, relay node, donor node controlling relay, radio access point (AP), transmission points, transmission nodes, Remote Radio Unit (RRU) Remote Radio Head (RRH), a core network node (e.g., mobile management entity (MME), self-organizing network (SON) node, a coordinating node, positioning node, MDT node, etc.), an external node (e.g., 3rd party node, a node external to the current network), nodes in distributed antenna system
  • BS base station
  • wireless device or a user equipment (UE) are used interchangeably.
  • the WD herein can be any type of wireless device capable of communicating with a network node or another WD over radio signals, such as wireless device (WD).
  • the WD may also be a radio communication device, target device, device to device (D2D) WD, machine type WD or WD capable of machine to machine communication (M2M), low-cost and/or low-complexity WD, a sensor equipped with WD, Tablet, mobile terminals, smart phone, laptop embedded equipped (LEE), laptop mounted equipment (LME), USB dongles, Customer Premises Equipment (CPE), an Internet of Things (IoT) device, or a Narrowband IoT (NB-IOT) device etc.
  • D2D device to device
  • M2M machine to machine communication
  • M2M machine to machine communication
  • Tablet mobile terminals
  • smart phone laptop embedded equipped (LEE), laptop mounted equipment (LME), USB dongles
  • CPE Customer Premises Equipment
  • IoT Internet of Things
  • NB-IOT Narrowband IoT
  • the generic term“radio network node” is used. It can be any kind of a radio network node which may comprise any of base station, radio base station, base transceiver station, base station controller, network controller, RNC, evolved Node B (eNB), Node B, gNB, Multi-cell/multicast Coordination Entity (MCE), IAB node, relay node, access point, radio access point, Remote Radio Unit (RRU) Remote Radio Head (RRH).
  • a radio network node may comprise any of base station, radio base station, base transceiver station, base station controller, network controller, RNC, evolved Node B (eNB), Node B, gNB, Multi-cell/multicast Coordination Entity (MCE), IAB node, relay node, access point, radio access point, Remote Radio Unit (RRU) Remote Radio Head (RRH).
  • command used in“layer 1/Ll command” is intended broadly to encompass instructions, indicators, bits, a field in a control information message, etc. and is not intended to be limiting.
  • activating/deactivating is intended broadly to encompass either activating an Scell, de-activating an Scell, activating/starting one or more procedures to be performed on the Scell, de-activating/stopping one or more procedures to be performed on the Scell and/or continuing a procedure that is already being performed on the Scell.
  • control information on one or more resources may be considered to be transmitted in a message having a specific format.
  • a message may comprise or represent bits representing payload information and coding bits, e.g., for error coding.
  • Receiving (or obtaining) control information may comprise receiving one or more control information messages (e.g., LI command). It may be considered that receiving control signaling comprises demodulating and/or decoding and/or detecting, e.g. blind detection of, one or more messages, in particular a message carried by the control signaling, e.g. based on an assumed set of resources, which may be searched and/or listened for the control information. It may be assumed that both sides of the communication are aware of the configurations, and may determine the set of resources, e.g. based on the reference size.
  • receiving control signaling comprises demodulating and/or decoding and/or detecting, e.g. blind detection of, one or more messages, in particular a message carried by the control signaling, e.g. based on an assumed set of resources, which may be searched and/or listened for the control information. It may be assumed that both sides of the communication are aware of the configurations, and may determine the set of resources, e.g. based on the reference size.
  • Signaling may generally comprise one or more symbols and/or signals and/or messages.
  • a signal may comprise or represent one or more bits.
  • An indication may represent signaling, and/or be implemented as a signal, or as a plurality of signals.
  • One or more signals may be included in and/or represented by a message.
  • Signaling, in particular control signaling may comprise a plurality of signals and/or messages, which may be transmitted on different carriers and/or be associated to different signaling processes, e.g. representing and/or pertaining to one or more such processes and/or corresponding information.
  • An indication may comprise signaling, and/or a plurality of signals and/or messages and/or may be comprised therein, which may be transmitted on different carriers and/or be associated to different acknowledgement signaling processes, e.g.
  • Signaling associated to a channel may be transmitted such that represents signaling and/or information for that channel, and/or that the signaling is interpreted by the transmitter and/or receiver to belong to that channel.
  • Such signaling may generally comply with transmission parameters and/or format/s for the channel.
  • Implicit indication may for example be based on position and/or resource used for transmission.
  • Explicit indication may for example be based on a parametrization with one or more parameters, and/or one or more index or indices corresponding to a table, and/or one or more bit patterns representing the information.
  • Configuring a radio node may refer to the radio node being adapted or caused or set and/or instructed to operate according to the configuration (e.g., to monitor an x-RNTI or a binary sequence for C-RNTI to determine which table to be used to interpret an indication or signal).
  • Configuring may be done by another device, e.g., a network node (for example, a base station or gNB) or network, in which case it may comprise transmitting configuration data to the radio node to be configured.
  • Such configuration data may represent the configuration to be configured and/or comprise one or more instruction pertaining to a
  • a radio node may configure itself, e.g., based on configuration data received from a network or network node.
  • a network node may utilize, and/or be adapted to utilize, its circuitry/ies for configuring.
  • Allocation information may be considered a form of configuration data.
  • Configuration data may comprise and/or be represented by configuration information, and/or one or more corresponding indications and/or message/s.
  • a channel may generally be a logical or physical channel.
  • a channel may comprise and/or be arranged on one or more carriers, in particular a plurality of subcarriers.
  • a wireless communication network may comprise at least one network node, in particular a network node as described herein.
  • a terminal e.g., WD
  • connected or communicating with a network may be considered to be connected or communicating with at least one network node, in particular any one of the network nodes described herein.
  • configuring may include determining configuration data representing the configuration and providing, e.g. transmitting, it to one or more other nodes (parallel and/or sequentially), which may transmit it further to the radio node (or another node, which may be repeated until it reaches the wireless device).
  • configuring a radio node may include receiving configuration data and/or data pertaining to configuration data, e.g., from another node like a network node, which may be a higher-level node of the network, and/or transmitting received configuration data to the radio node. Accordingly, determining a configuration and transmitting the configuration data to the radio node may be performed by different network nodes or entities, which may be able to communicate via a suitable interface, e.g., an X2 interface in the case of LTE or a corresponding interface for NR.
  • Configuring a terminal e.g. WD
  • acknowledgement signaling and/or configuring resources and/or a resource pool therefor.
  • a cell may be generally a communication cell, e.g., of a cellular or mobile communication network, provided by a node.
  • a serving cell may be a cell on or via which a network node (the node providing or associated to the cell, e.g., base station or eNodeB) transmits and/or may transmit data (which may be data other than broadcast data) to a user equipment, in particular control and/or user or payload data, and/or via or on which a user equipment transmits and/or may transmit data to the node;
  • a serving cell may be a cell for or on which the user equipment is configured and/or to which it is synchronized and/or has performed an access procedure, e.g., a random access procedure, and/or in relation to which it is in a RRC connected or RRC idle state, e.g., in case the node and/or user equipment and/or network follow the a standard.
  • One or more carriers e.g., uplink and/or down
  • WCDMA Wide Band Code Division Multiple Access
  • WiMax Worldwide Interoperability for Microwave Access
  • UMB Ultra Mobile Broadband
  • GSM Global System for Mobile Communications
  • functions described herein as being performed by a wireless device or a network node may be distributed over a plurality of wireless devices and/or network nodes.
  • the functions of the network node and wireless device described herein are not limited to performance by a single physical device and, in fact, can be distributed among several physical devices.
  • FIG. 2 a schematic diagram of a communication system 10, according to an embodiment, such as a 3GPP-type cellular network that may support standards such as LTE and/or NR (5G), which comprises an access network 12, such as a radio access network, and a core network 14.
  • the access network 12 comprises a plurality of network nodes 16a, 16b, 16c (referred to collectively as network nodes 16), such as NBs, eNBs, gNBs or other types of wireless access points, each defining a corresponding coverage area 18a, 18b, 18c (referred to collectively as coverage areas 18).
  • Each network node 16a, 16b, 16c is connectable to the core network 14 over a wired or wireless connection 20.
  • a first wireless device (WD) 22a located in coverage area 18a is configured to wirelessly connect to, or be paged by, the corresponding network node 16a.
  • a second WD 22b in coverage area 18b is wirelessly connectable to the corresponding network node 16b. While a plurality of WDs 22a, 22b (collectively referred to as wireless devices 22) are illustrated in this example, the disclosed embodiments are equally applicable to a situation where a sole WD is in the coverage area or where a sole WD is connecting to the corresponding network node 16. Note that although only two WDs 22 and three network nodes 16 are shown for convenience, the communication system may include many more WDs 22 and network nodes 16.
  • a WD 22 can be in simultaneous communication and/or configured to separately communicate with more than one network node 16 and more than one type of network node 16.
  • a WD 22 can have dual connectivity with a network node 16 that supports LTE and the same or a different network node 16 that supports NR.
  • WD 22 can be in communication with an eNB for LTE/E-UTRAN and a gNB for NR/NG-RAN.
  • the communication system 10 may itself be connected to a host computer 24, which may be embodied in the hardware and/or software of a standalone server, a cloud-implemented server, a distributed server or as processing resources in a server farm.
  • the host computer 24 may be under the ownership or control of a service provider, or may be operated by the service provider or on behalf of the service provider.
  • the connections 26, 28 between the communication system 10 and the host computer 24 may extend directly from the core network 14 to the host computer 24 or may extend via an optional intermediate network 30.
  • the intermediate network 30 may be one of, or a combination of more than one of, a public, private or hosted network.
  • the intermediate network 30, if any, may be a backbone network or the Internet.
  • the intermediate network 30 may comprise two or more sub-networks (not shown).
  • the communication system of FIG. 2 as a whole enables connectivity between one of the connected WDs 22a, 22b and the host computer 24.
  • the connectivity may be described as an over-the-top (OTT) connection.
  • the host computer 24 and the connected WDs 22a, 22b are configured to communicate data and/or signaling via the OTT connection, using the access network 12, the core network 14, any intermediate network 30 and possible further infrastructure (not shown) as intermediaries.
  • the OTT connection may be transparent in the sense that at least some of the participating communication devices through which the OTT connection passes are unaware of routing of uplink and downlink communications.
  • a network node 16 may not or need not be informed about the past routing of an incoming downlink communication with data originating from a host computer 24 to be forwarded (e.g., handed over) to a connected WD 22a. Similarly, the network node 16 need not be aware of the future routing of an outgoing uplink communication originating from the WD 22a towards the host computer 24.
  • a network node 16 is configured to include a Scell management unit 32 which is configured to cause the network node 16 to send a Layer 1, LI, command in a downlink control information, DCI, on a primary cell, PCell, the LI command indicating a periodicity for monitoring a physical downlink control channel, PDCCH, on at least one Scell of the at least one Scell.
  • a network node 16 is configured to include a Scell management unit 32 which is configured to cause a radio interface to signal a layer 1 command, the layer 1 command
  • a wireless device 22 is configured to include an operational unit 34 which is configured to receive a Layer 1, LI, command in a downlink control information,
  • a wireless device 22 includes an operational unit 34 which is configured to receive (and/or decode) a layer 1 command, the layer 1 command activating/deactivating a secondary cell (Scell) for the WD.
  • a host computer 24 comprises hardware (HW) 38 including a communication interface 40 configured to set up and maintain a wired or wireless connection with an interface of a different communication device of the communication system 10.
  • the host computer 24 further comprises processing circuitry 42, which may have storage and/or processing capabilities.
  • the processing circuitry 42 may include a processor 44 and memory 46.
  • the processing circuitry 42 may comprise integrated circuitry for processing and/or control, e.g., one or more processors and/or processor cores and/or FPGAs (Field Programmable Gate Array) and/or ASICs (Application Specific Integrated Circuitry) adapted to execute instructions.
  • processors and/or processor cores and/or FPGAs Field Programmable Gate Array
  • ASICs Application Specific Integrated Circuitry
  • the processor 44 may be configured to access (e.g., write to and/or read from) memory 46, which may comprise any kind of volatile and/or nonvolatile memory, e.g., cache and/or buffer memory and/or RAM (Random Access Memory) and/or ROM (Read- Only Memory) and/or optical memory and/or EPROM (Erasable Programmable Read-Only Memory).
  • memory 46 may comprise any kind of volatile and/or nonvolatile memory, e.g., cache and/or buffer memory and/or RAM (Random Access Memory) and/or ROM (Read- Only Memory) and/or optical memory and/or EPROM (Erasable Programmable Read-Only Memory).
  • Processing circuitry 42 may be configured to control any of the methods and/or processes described herein and/or to cause such methods, and/or processes to be performed, e.g., by host computer 24.
  • Processor 44 corresponds to one or more processors 44 for performing host computer 24 functions described herein.
  • the host computer 24 includes memory 46 that is configured to store data, programmatic software code and/or other information described herein.
  • the software 48 and/or the host application 50 may include instructions that, when executed by the processor 44 and/or processing circuitry 42, causes the processor 44 and/or processing circuitry 42 to perform the processes described herein with respect to host computer 24.
  • the instructions may be software associated with the host computer 24.
  • the software 48 may be executable by the processing circuitry 42.
  • the software 48 includes a host application 50.
  • the host application 50 may be operable to provide a service to a remote user, such as a WD 22 connecting via an OTT connection 52 terminating at the WD 22 and the host computer 24.
  • the host application 50 may provide user data which is transmitted using the OTT connection 52.
  • The“user data” may be data and information described herein as implementing the described functionality.
  • the host computer 24 may be configured for providing control and functionality to a service provider and may be operated by the service provider or on behalf of the service provider.
  • the processing circuitry 42 of the host computer 24 may enable the host computer 24 to observe, monitor, control, transmit to and/or receive from the network node 16 and/or the wireless device 22.
  • the processing circuitry 42 of the host computer 24 may include a monitor unit 54 configured to enable the service provider to observe, monitor, control, transmit to and/or receive from the network node 16 and/or the wireless device 22.
  • the communication system 10 further includes a network node 16 provided in a communication system 10 and including hardware 58 enabling it to communicate with the host computer 24 and with the WD 22.
  • the hardware 58 may include a communication interface 60 for setting up and maintaining a wired or wireless connection with an interface of a different communication device of the
  • the radio interface 62 may be formed as or may include, for example, one or more RF transmitters, one or more RF receivers, and/or one or more RF transceivers.
  • the communication interface 60 may be configured to facilitate a connection 66 to the host computer 24.
  • the connection 66 may be direct or it may pass through a core network 14 of the communication system 10 and/or through one or more intermediate networks 30 outside the communication system 10.
  • the hardware 58 of the network node 16 further includes processing circuitry 68.
  • the processing circuitry 68 may include a processor 70 and a memory 72.
  • the processing circuitry 68 may comprise integrated circuitry for processing and/or control, e.g., one or more processors and/or processor cores and/or FPGAs (Field Programmable Gate Array) and/or ASICs (Application Specific Integrated Circuitry) adapted to execute instructions.
  • FPGAs Field Programmable Gate Array
  • ASICs Application Specific Integrated Circuitry
  • the processor 70 may be configured to access (e.g., write to and/or read from) the memory 72, which may comprise any kind of volatile and/or nonvolatile memory, e.g., cache and/or buffer memory and/or RAM (Random Access Memory) and/or ROM (Read-Only Memory) and/or optical memory and/or EPROM (Erasable Programmable Read-Only Memory).
  • volatile and/or nonvolatile memory e.g., cache and/or buffer memory and/or RAM (Random Access Memory) and/or ROM (Read-Only Memory) and/or optical memory and/or EPROM (Erasable Programmable Read-Only Memory).
  • the network node 16 further has software 74 stored internally in, for example, memory 72, or stored in external memory (e.g., database, storage array, network storage device, etc.) accessible by the network node 16 via an external connection.
  • the software 74 may be executable by the processing circuitry 68.
  • the processing circuitry 68 may be configured to control any of the methods and/or processes described herein and/or to cause such methods, and/or processes to be performed, e.g., by network node 16.
  • Processor 70 corresponds to one or more processors 70 for performing network node 16 functions described herein.
  • the memory 72 is configured to store data, programmatic software code and/or other information described herein.
  • the software 74 may include instructions that, when executed by the processor 70 and/or processing circuitry 68, causes the processor 70 and/or processing circuitry 68 to perform the processes described herein with respect to network node 16.
  • processing circuitry 68 of the network node 16 may include Scell management unit 32 configured to cause the radio interface 62 to signal a layer 1 command, the layer 1 command
  • the communication system 10 further includes the WD 22 already referred to.
  • the WD 22 may have hardware 80 that may include a radio interface 82 configured to set up and maintain a wireless connection 64 with a network node 16 serving a coverage area 18 in which the WD 22 is currently located.
  • the radio interface 82 may be formed as or may include, for example, one or more RF transmitters, one or more RF receivers, and/or one or more RF transceivers.
  • the hardware 80 of the WD 22 further includes processing circuitry 84.
  • the processing circuitry 84 may include a processor 86 and memory 88.
  • the processing circuitry 84 may comprise integrated circuitry for processing and/or control, e.g., one or more processors and/or processor cores and/or FPGAs (Field Programmable Gate Array) and/or ASICs (Application Specific Integrated Circuitry) adapted to execute instructions.
  • the processor 86 may be configured to access (e.g., write to and/or read from) memory 88, which may comprise any kind of volatile and/or nonvolatile memory, e.g., cache and/or buffer memory and/or RAM (Random Access Memory) and/or ROM (Read-Only Memory) and/or optical memory and/or EPROM (Erasable Programmable Read-Only Memory).
  • memory 88 may comprise any kind of volatile and/or nonvolatile memory, e.g., cache and/or buffer memory and/or RAM (Random Access Memory) and/or ROM (Read-Only Memory) and/or optical memory and/or EPROM (Erasable Programmable Read-Only Memory).
  • the WD 22 may further comprise software 90, which is stored in, for example, memory 88 at the WD 22, or stored in external memory (e.g., database, storage array, network storage device, etc.) accessible by the WD 22.
  • the software 90 may be executable by the processing circuitry 84.
  • the software 90 may include a client application 92.
  • the client application 92 may be operable to provide a service to a human or non-human user via the WD 22, with the support of the host computer 24.
  • an executing host application 50 may communicate with the executing client application 92 via the OTT connection 52 terminating at the WD 22 and the host computer 24.
  • the client application 92 may receive request data from the host application 50 and provide user data in response to the request data.
  • the OTT connection 52 may transfer both the request data and the user data.
  • the client application 92 may interact with the user to generate the user data that it provides.
  • the processing circuitry 84 may be configured to control any of the methods and/or processes described herein and/or to cause such methods, and/or processes to be performed, e.g., by WD 22.
  • the processor 86 corresponds to one or more processors 86 for performing WD 22 functions described herein.
  • the WD 22 includes memory 88 that is configured to store data, programmatic software code and/or other information described herein.
  • the software 90 and/or the client application 92 may include instructions that, when executed by the processor 86 and/or processing circuitry 84, causes the processor 86 and/or processing circuitry 84 to perform the processes described herein with respect to WD 22.
  • the processing circuitry 84 of the wireless device 22 may include an operational unit 34 configured to receive a layer 1 command, the layer 1 command activating/deactivating a secondary cell (Scell) for the WD 22.
  • Scell secondary cell
  • the inner workings of the network node 16, WD 22, and host computer 24 may be as shown in FIG. 3 and independently, the surrounding network topology may be that of FIG. 2.
  • the OTT connection 52 has been drawn abstractly to illustrate the communication between the host computer 24 and the wireless device 22 via the network node 16, without explicit reference to any intermediary devices and the precise routing of messages via these devices.
  • Network infrastructure may determine the routing, which it may be configured to hide from the WD 22 or from the service provider operating the host computer 24, or both. While the OTT connection 52 is active, the network infrastructure may further take decisions by which it dynamically changes the routing (e.g., on the basis of load balancing consideration or
  • the wireless connection 64 between the WD 22 and the network node 16 is in accordance with the teachings of the embodiments described throughout this disclosure.
  • One or more of the various embodiments improve the performance of OTT services provided to the WD 22 using the OTT connection 52, in which the wireless connection 64 may form the last segment. More precisely, the teachings of some of these embodiments may improve the data rate, latency, and/or power consumption and thereby provide benefits such as reduced user waiting time, relaxed restriction on file size, better responsiveness, extended battery lifetime, etc.
  • a measurement procedure may be provided for the purpose of monitoring data rate, latency and other factors on which the one or more embodiments improve.
  • the measurement procedure and/or the network functionality for reconfiguring the OTT connection 52 may be implemented in the software 48 of the host computer 24 or in the software 90 of the WD 22, or both.
  • sensors (not shown) may be deployed in or in association with communication devices through which the OTT connection 52 passes; the sensors may participate in the measurement procedure by supplying values of the monitored quantities exemplified above, or supplying values of other physical quantities from which software 48, 90 may compute or estimate the monitored quantities.
  • the reconfiguring of the OTT connection 52 may include message format, retransmission settings, preferred routing etc.; the reconfiguring need not affect the network node 16, and it may be unknown or imperceptible to the network node 16. Some such procedures and functionalities may be known and practiced in the art.
  • measurements may involve proprietary WD signaling facilitating the host computer’s 24 measurements of throughput, propagation times, latency and the like.
  • the measurements may be implemented in that the software 48, 90 causes messages to be transmitted, in particular empty or ‘dummy’ messages, using the OTT connection 52 while it monitors propagation times, errors etc.
  • the host computer 24 includes processing circuitry 42 configured to provide user data and a communication interface 40 that is configured to forward the user data to a cellular network for transmission to the WD 22.
  • the cellular network also includes the network node 16 with a radio interface 62.
  • the network node 16 is configured to, and/or the network node’s 16 processing circuitry 68 is configured to perform the functions and/or methods described herein for
  • the host computer 24 includes processing circuitry 42 and a communication interface 40 that is configured to a communication interface 40 configured to receive user data originating from a transmission from a WD 22 to a network node 16.
  • the WD 22 is configured to, and/or comprises a radio interface 82 and/or processing circuitry 84 configured to perform the functions and/or methods described herein for
  • FIGS. 2 and 3 show various“units” such as Scell management unit 32, and operational unit 34 as being within a respective processor, it is contemplated that these units may be implemented such that a portion of the unit is stored in a corresponding memory within the processing circuitry. In other words, the units may be implemented in hardware or in a combination of hardware and software within the processing circuitry.
  • FIG. 4 is a flowchart illustrating an exemplary method implemented in a communication system, such as, for example, the communication system of FIGS. 2 and 3, in accordance with one embodiment.
  • the communication system may include a host computer 24, a network node 16 and a WD 22, which may be those described with reference to FIG. 3.
  • the host computer 24 provides user data (Block SI 00).
  • the host computer 24 provides the user data by executing a host application, such as, for example, the host application 50 (Block SI 02).
  • the host computer 24 initiates a transmission carrying the user data to the WD 22 (Block SI 04).
  • the network node 16 transmits to the WD 22 the user data which was carried in the transmission that the host computer 24 initiated, in accordance with the teachings of the embodiments described throughout this disclosure (Block SI 06).
  • the WD 22 executes a client application, such as, for example, the client application 92, associated with the host application 50 executed by the host computer 24 (Block SI 08).
  • FIG. 5 is a flowchart illustrating an exemplary method implemented in a communication system, such as, for example, the communication system of FIG. 2, in accordance with one embodiment.
  • the communication system may include a host computer 24, a network node 16 and a WD 22, which may be those described with reference to FIGS. 2 and 3.
  • the host computer 24 provides user data (Block SI 10).
  • the host computer 24 provides the user data by executing a host application, such as, for example, the host application 50.
  • the host computer 24 initiates a transmission carrying the user data to the WD 22 (Block S 112).
  • the transmission may pass via the network node 16, in accordance with the teachings of the embodiments described throughout this disclosure.
  • the WD 22 receives the user data carried in the transmission (Block SI 14).
  • FIG. 6 is a flowchart illustrating an exemplary method implemented in a communication system, such as, for example, the communication system of FIG. 2, in accordance with one embodiment.
  • the communication system may include a host computer 24, a network node 16 and a WD 22, which may be those described with reference to FIGS. 2 and 3.
  • the WD 22 receives input data provided by the host computer 24 (Block SI 16).
  • the WD 22 executes the client application 92, which provides the user data in reaction to the received input data provided by the host computer 24 (Block SI 18).
  • the WD 22 provides user data (Block SI 20).
  • the WD provides the user data by executing a client application, such as, for example, client application 92 (Block S122).
  • client application 92 may further consider user input received from the user.
  • the WD 22 may initiate, in an optional third substep, transmission of the user data to the host computer 24 (Block SI 24).
  • the host computer 24 receives the user data transmitted from the WD 22, in accordance with the teachings of the embodiments described throughout this disclosure (Block S126).
  • FIG. 7 is a flowchart illustrating an exemplary method implemented in a communication system, such as, for example, the communication system of FIG. 2, in accordance with one embodiment.
  • the communication system may include a host computer 24, a network node 16 and a WD 22, which may be those described with reference to FIGS. 2 and 3.
  • the network node 16 receives user data from the WD 22 (Block S128).
  • the network node 16 initiates transmission of the received user data to the host computer 24 (Block SI 30).
  • the host computer 24 receives the user data carried in the transmission initiated by the network node 16 (Block SI 32).
  • FIG. 8 is a flowchart of an exemplary process in a network node 16 for CA Scell management according to some embodiments of the present disclosure.
  • One or more Blocks and/or functions and/or methods performed by the network node 16 may be performed by one or more elements of network node 16 such as by Scell management unit 32 in processing circuitry 68, processor 70, communication interface 60, radio interface 62, etc. according to the example method.
  • the example method, implemented a network node configured to configure a wireless device, WD, to operate on at least one secondary cell, Scell includes sending (Block SI 34), such as via Scell management unit 32, processing circuitry 68, processor 70, communication interface 60 and/or radio interface 62, a Layer 1, LI, command in a downlink control information, DCI, on a primary cell, PCell, the LI command indicating a periodicity for monitoring a physical downlink control channel, PDCCH, on at least one Scell of the at least one Scell.
  • Block SI 34 such as via Scell management unit 32, processing circuitry 68, processor 70, communication interface 60 and/or radio interface 62, a Layer 1, LI, command in a downlink control information, DCI, on a primary cell, PCell, the LI command indicating a periodicity for monitoring a physical downlink control channel, PDCCH, on at least one Scell of the at least one Scell.
  • the sending the LI command in the DCI further includes sending, such as via Scell management unit 32, processing circuitry 68, processor 70, communication interface 60 and/or radio interface 62, the LI command indicating one of a first periodicity for the monitoring the PDCCH on the at least one Scell and a second periodicity for the monitoring the PDCCH on the at least one Scell, the first periodicity being different from the second periodicity.
  • the LI command indicating one of a first periodicity for the monitoring the PDCCH on the at least one Scell and a second periodicity for the monitoring the PDCCH on the at least one Scell, the first periodicity being different from the second periodicity.
  • the first periodicity is less than the second periodicity.
  • the second periodicity indicates stopping the PDCCH monitoring on the at least one Scell.
  • the LI command in the DCI is a physical layer command.
  • the method further includes configuring the WD 22 to operate on N S cells and configuring each Scell of the N Scells with one or more bandwidth parts, BWPs; and the LI command includes, for each Scell of the N Scells, a number of bits that indicate one or more periodicities for monitoring the PDCCH on the corresponding Scell and the number of bits is based at least in part on a number of BWPs that the corresponding Scell is configured with.
  • the method includes signalling, such as via a Scell management unit 32, processing circuitry 68, processor 70, and/or radio interface 62, a layer 1 command, the layer 1 command activating/deactivating a secondary cell for a wireless device (WD) 22.
  • signalling such as via a Scell management unit 32, processing circuitry 68, processor 70, and/or radio interface 62, a layer 1 command, the layer 1 command activating/deactivating a secondary cell for a wireless device (WD) 22.
  • the layer 1 command corresponds to a first delay time period before the WD 22 can perform a first set of procedures, the first set of procedures being different from a second set of procedures associated with a higher layer Scell activation/deactivation command. In some embodiments, the first delay time period is less than a second delay time period associated with the higher layer Scell activation/deactivation command. In some embodiments, the layer 1 command is included in a downlink control information (DCI) message sent via a physical downlink control channel (PDCCH). In some embodiments, the layer 1 command includes a bit map, each bit in the bit map activating/deactivating one of a plurality of Scells configured for the WD 22. In some embodiments, the layer 1 command includes a bit map, each bit in the bit map starting/stopping/continuing the at least one of the first set of procedures configured for the WD in the Scell. In some
  • the first set of procedures comprises PDCCH monitoring on the Scell, performing uplink transmissions on the SCell and bandwidth part (BWP) switching in the Scell.
  • the layer 1 command indicates to the WD 22 to switch BWPs based at least in part on which BWP is configured with PDCCH monitoring candidates.
  • the layer 1 command indicates a BWP index value of a BWP to which the WD 22 is to switch in the Scell.
  • the layer 1 command includes a bit map, the bit map mapping to BWPs in the Scell.
  • the method further includes transmitting, such as via a Scell management unit 32, processing circuitry 68, processor 70, and/or radio interface 62, a higher layer signaling indicating a number of bits for the layer 1 command.
  • a duration of the first delay time period is based at least in part on an offset value included, such as via a Scell management unit 32, processing circuitry 68, processor 70, and/or radio interface 62, in one of the DCI and higher layer signaling.
  • FIG. 9 is a flowchart of an exemplary process in a wireless device 22 for CA Scell management according to some embodiments of the present disclosure.
  • One or more Blocks and/or functions and/or methods performed by WD 22 may be performed by one or more elements of WD 22 such as by operational unit 34 in processing circuitry 84, processor 86, radio interface 82, etc.
  • the example method, implemented a wireless device, WD, configured to operate on at least one secondary cell, Scell includes receiving (Block S136), such as by operational unit 34, processing circuitry 84, processor 86 and/or radio interface 82, a Layer 1, LI, command in a downlink control information, DCI, on a primary cell, PCell.
  • Block S136 such as by operational unit 34, processing circuitry 84, processor 86 and/or radio interface 82, a Layer 1, LI, command in a downlink control information, DCI, on a primary cell, PCell.
  • the method includes responsive to receiving the LI command, adapting (Block SI 38), such as by operational unit 34, processing circuitry 84, processor 86 and/or radio interface 82, a periodicity for monitoring a physical downlink control channel, PDCCH, on at least one Scell of the at least one Scell based at least in part on the LI command.
  • adapting such as by operational unit 34, processing circuitry 84, processor 86 and/or radio interface 82, a periodicity for monitoring a physical downlink control channel, PDCCH, on at least one Scell of the at least one Scell based at least in part on the LI command.
  • adapting the periodicity includes if the received command indicates a first periodicity: responsive to receiving the LI command, performing PDCCH monitoring on the at least one Scell according to the first periodicity; and if the received command indicates a second periodicity: responsive to receiving the LI command, performing PDCCH monitoring on the at least one Scell according to the second periodicity, the first periodicity being different from the second periodicity.
  • the first periodicity is less than the second periodicity.
  • the second periodicity indicates performing the PDCCH monitoring by stopping the PDCCH monitoring on the at least one Scell.
  • the LI command received in the DCI is a physical layer command.
  • the WD 22 is configured to operate on N Scells and each Scell of the N Scells is configured with one or more bandwidth parts, BWPs; and the LI command includes, for each Scell of the N Scells, a number of bits that indicate one or more periodicities for monitoring the PDCCH on the corresponding Scell and the number of bits is based at least in part on a number of BWPs that the corresponding Scell is configured with.
  • the method includes receiving, such as via operational unit 34, processing circuitry 84, processor 86, radio interface 82, a layer 1 command, the layer 1 command activating/deactivating a secondary cell (Scell) for the WD 22.
  • Scell secondary cell
  • stopping performance such as via operational unit 34, processing circuitry 84, processor 86, radio interface 82, of the at least one of the first set of procedures.
  • the first delay time period is less than a second delay time period associated with the higher layer Scell activation/deactivation command.
  • the layer 1 command is included in a downlink control information (DCI) message via a physical downlink control channel (PDCCH).
  • DCI downlink control information
  • PDCCH physical downlink control channel
  • the layer 1 command includes a bit map, each bit in the bit map activating/deactivating one of a plurality of Scells configured for the WD 22.
  • the layer 1 command includes a bit map, each bit in the bit map starting/stopping/continuing the at least one of the first set of procedures configured for the WD 22 in the Scell.
  • the first set of procedures comprises PDCCH monitoring, such as via operational unit 34, processing circuitry 84, processor 86, radio interface 82, on the Scell, performing uplink transmissions, such as via operational unit 34, processing circuitry 84, processor 86, radio interface 82, on the SCell and bandwidth part (BWP) switching, such as via operational unit 34, processing circuitry 84, processor 86, radio interface 82, in the Scell.
  • the processing circuitry 84 is further configured to switch BWPs based on the layer 1 command and which BWP is configured with PDCCH monitoring candidates.
  • the layer 1 command indicates a BWP index value of a BWP to which the WD 22 is to switch in the Scell.
  • the layer 1 command includes a bit map, the bit map mapping to BWPs in the Scell.
  • the processing circuitry 84 is configured to receive a higher layer signaling indicating a number of bits for the layer 1 command.
  • a duration of the first delay time period is based at least in part on an offset value included in one of the DCI and higher layer signaling.
  • FIG. 10 is a flowchart of another exemplary process in a network node 16 for CA Scell management according to some embodiments of the present disclosure.
  • One or more Blocks and/or functions and/or methods performed by the network node 16 may be performed by one or more elements of network node 16 such as by Scell management unit 32 in processing circuitry 68, processor 70, radio interface 62, etc. according to the example method.
  • the example method includes signaling (Block SI 40) a layer 1 command where the layer 1 command is configured to modify a periodicity for monitoring a downlink control channel.
  • the layer 1 command is configured to reduce a periodicity for monitoring the downlink control channel based at least in part on a state of at least in bit (e.g., bO) in the layer 1 command.
  • the LI command includes ki bits that indicate respective values for modifying the periodicity for monitoring the downlink control channel, each value corresponding to a bandwidth part.
  • FIG. 11 is a flowchart of another exemplary process in a wireless device 22 for CA Scell management according to some embodiments of the present disclosure.
  • One or more Blocks and/or functions and/or methods performed by WD 22 may be performed by one or more elements of WD 22 such as by operational unit 34 in processing circuitry 84, processor 86, radio interface 82, etc.
  • the example method includes receiving (Block SI 42) a layer 1 command where the layer 1 command is configured to modify a periodicity for monitoring a downlink control channel.
  • the layer 1 command is configured to reduce a periodicity for monitoring the downlink control channel based at least in part on a state of at least in bit in the layer 1 command.
  • the LI command includes ki bits that indicate at least one value for modifying the periodicity for monitoring the downlink control channel, each value corresponding to a bandwidth part.
  • the WD 22 is further configured to, and/or comprising a radio interface and/or processing circuitry further configured to switch to at least one of the bandwidth parts associated with the at least one value indicated by the ki bits.
  • a WD 22 communicates with the network (e.g., network node 16) using a primary serving cell (Pcell), where the network node 16 may be providing the Pcell.
  • Pcell primary serving cell
  • the WD 22 may also configured with one or more secondary serving cells (Scell(s)).
  • Scell(s) secondary serving cells
  • the WD 22 receives a higher layer Scell activation/deactivation command. Upon reception of the higher layer
  • the WD 22 starts/stops performing a first set of actions.
  • the first set of actions may include periodic CSI reporting for the Scell (e.g., if the WD 22 is configured for periodic CSI reporting).
  • the first set of actions can also include PDCCH monitoring on the Scell. If the WD 22 is configured with multiple BWPs for the Scell, the PDCCH monitoring can be on a preconfigured/ default BWP of the Scell. If the WD 22 receives the higher layer activation command in time slot n, the WD 22 may apply the first set of actions starting with slot n+Dl (i.e., after an activation delay of D1 slots).
  • the WD 22 may also receive a physical layer command (LI command) (e.g., transmitted by the network node 16).
  • LI command physical layer command
  • the WD 22 Upon reception of the LI command, the WD 22 starts/ stops performing a second set of actions.
  • the second set of actions can be PDCCH monitoring or BWP switching as discussed in the examples below.
  • the second set of actions for an Scell can be different based on whether the WD 22 is configured with one BWP for the Scell or whether it is configured with multiple BWPs for the Scell. If the WD 22 receives the LI command in time slot nl, the WD 22 may apply the second set of actions starting with slot nl+D2 (i.e., after a delay of D2 slots). The delay D2 is smaller than Dl.
  • the higher layer Scell activation/deactivation command (e.g., transmitted by the network node 16) can be received by the WD 22 in a MAC CE (MAC control element).
  • the first set of actions can also include transmitting PUCCH/ periodic SRS on the Scell.
  • the LI command (e.g., transmitted by the network node 16) can be received by the WD 22 using a PDCCH.
  • the LI command can be part of PDCCH DCI (downlink control information).
  • the PDCCH DCI corresponding to the LI command can include the bits corresponding to the Scell(s) configured for the WD 22 based on which the WD 22 performs the second set of actions. The bits can be according to the examples discussed herein.
  • the WD 22 is configured with N SCell(s) (e.g., by network node 16).
  • the PDCCH DCI corresponding to the LI command can include N bits (b0,bl,... bN-l): bO can correspond to ScellO e.g., an Scell with lowest cell index among the configured Scell(s), bl can correspond to Scelll, e,g., Scell with next lowest cell index among the configured Scell(s) and so on.
  • bO is set for a first state (e.g., 1) the WD 22 can start PDCCH monitoring on the ScellO and if bO is set to a second state (e.g., 0) the WD 22 can stop PDCCH monitoring on the ScellO.
  • the WD 22 may adapt the periodicity of PDCCH monitoring on ScellO based at least in part on the state of bO.
  • the WD 22 may monitor (e.g., via processing circuitry 84, operational unit 34 and/or radio interface 82) PDCCH on ScellO with a first periodicity if bO is set to the first state (e.g., 1) and may monitor (e.g., via processing circuitry 84, operational unit 34 and/or radio interface 82) PDCCH with a second periodicity if bO is set to a second state (e.g., 0).
  • the second periodicity can be a periodicity corresponding to less frequent monitoring than the first periodicity.
  • the second periodicity value can be set to infinity or another predefined value that indicates to stop PDCCH monitoring on ScellO.
  • (b0,bl,... bN-1) in the DCI may be used to modify a configuration, trigger an action, alter a characteristic of monitoring of the PDCCH in accordance with the teachings of the disclosure.
  • the WD 22 continues (e.g., via processing circuitry 84, operational unit 34 and/or radio interface 82) PDCCH monitoring on that Scell. If the WD 22 is configured with multiple BWPs for ScellO, and if the WD 22 receives LI command with bO set to a second state, the WD 22 can stop (e.g., via processing circuitry 84, operational unit 34 and/or radio interface 82) monitoring PDCCH on the current active BWP of ScellO or alternately on all BWPs of SCellO.
  • the WD 22 can start PDCCH monitoring on one of the multiple BWPs configured for ScellO.
  • the BWP on which the WD 22 can start PDCCH monitoring can be preconfigured by higher layer (e.g., radio resource control (RRC)) signaling (e.g., by network node’s 16 radio interface 62).
  • RRC radio resource control
  • the WD 22 can start PDCCH monitoring (e.g., via processing circuitry 84, operational unit 34 and/or radio interface 82) on a BWP with specific BWP-index (e.g., firstActiveDownlinkBWP-Id) configured by higher layers.
  • the WD 22 can start PDCCH monitoring on a default DL BWP configured by higher layers.
  • the WD 22 can start PDCCH monitoring on a BWP with lowest index among the DL BWPs configured for SCellO.
  • WD 22 can continue PDCCH monitoring (e.g., via processing circuitry 84, operational unit 34 and/or radio interface 82) on its current active BWP of ScellO. Similar procedure can be used for other Scells configured for the WD 22.
  • FIG. 12 shows an example with option 1.
  • WD 22 is configured (e.g., by network node 16) with ScellO (with one BWP), SCelll (with two BWPs) and Scell2 (with 4 BWPs). All three Scells are in activated state (e.g, using a MAC CE based Scell activation command).
  • the WD 22 Before reception of an LI command Cl, the WD 22 is not monitoring PDCCH on ScellO, Scell 1 but monitoring PDCCH on BWP1 of Scell2 (as shown in the first column shown in FIG. 12 with shading on Scell2 BWP1).
  • the WD 22 starts PDCCH monitoring on ScellO (as indicated by the shading in ScellO BWP0), Scelll (e.g., on BWP0 of Scelll which can be default/preconfigured BWP for this Scell), and stops PDCCH monitoring on Scell2 (since the bit associated with Scell2 was set to the second state/0).
  • the WD 22 Upon reception of an LI command C2 with DCI bits corresponding to ⁇ SCellO,SCelll,Scell2 ⁇ set to ⁇ 0,1,1 ⁇ respectively, the WD 22 (e.g., via processing circuitry 84, operational unit 34 and/or radio interface 82) stops PDCCH monitoring on ScellO, continues PDCCH monitoring on its current active BWP (i.e., BWP0) and starts PDCCH monitoring on Scell2 (e.g. on BWP0 of Scell2 which can be default/preconfigured BWP for this Scell).
  • BWP0 current active BWP
  • the WD 22 is configured (e.g., by network node 16) with N SCell(s).
  • the PDCCH DCI corresponding to the LI command can include N bits (b0,bl,... bN-1).
  • the WD 22 can be configured with more than one BWP. If the WD 22 is configured with only one BWP for SCellx of the N Scells, the WD 22 can start/stop PDCCH monitoring on Scellx based on the state indicated by bit bx (where x may correspond to any one of 0,...,N-1)
  • the WD 22 may adapt/modify/change (e.g., via processing circuitry 84, operational unit 34 and/or radio interface 82) the periodicity of PDCCH monitoring on Scellx based at least in part on the state of bx.
  • the WD 22 may monitor PDCCH on Scellx with a first periodicity if bx is set to the first state (e.g., 1) and may monitor PDCCH with a second periodicity if bx is set to the second state (e.g., 0).
  • the second periodicity may correspond to a periodicity that monitors the PDCCH less frequently than the first periodicity.
  • the second periodicity value can be set to infinity or a predefined value that indicates to stop PDCCH monitoring on Scellx.
  • the WD 22 can perform (e.g., via processing circuitry 84, operational unit 34 and/or radio interface 82) a BWP switch operation by switching from its current active BWP (BWPc) to a predefined BWP (BWPd).
  • BWPc current active BWP
  • BWPd predefined BWP
  • y corresponds to any one of 0,...,N-1.
  • BWPd can be a BWP for which the WD 22 is not configured to monitor PDCCH (e.g., zero PDCCH monitoring candidates are configured for all search spaces and for aggregation levels configured for BWPd). If bit‘by’ corresponding to Scelly indicates a second state (e.g., 1), the WD 22 can perform a BWP switch operation by switching to a BWP (BWPe) for which the WD 22 is configured to monitor PDCCH.
  • BWPe can be a BWP with specific BWP -index (e.g.
  • BWPe can be a default DL BWP configured by higher layers.
  • BWPe can be a BWP with lowest index among the DL BWPs configured for SCelly.
  • BWPe can be the most recent current active BWP for the WD 22 on which it was monitoring PDCCH. If bit‘by’ corresponding to Scelly indicates the second state (e.g., 1), the WD 22 can perform (e.g., via processing circuitry 84, operational unit 34 and/or radio interface 82) a BWP switch operation by switching to a BWP (BWPe) for which the WD 22 is configured to monitor PDCCH only if prior to receiving the LI command with bit‘by’, the WD 22 is operating on a BWP for which the WD 22 is not configured to monitor PDCCH (e.g. BWPd). If the WD 22 is operating on a BWP with PDCCH monitoring prior to receiving the LI command with bit‘by’ indicating second state, the WD 22 can continue operating on that BWP and not perform any BWP switch operation.
  • BWPe BWP switch operation by switching to a BWP (BWPe) for which the WD 22 is
  • FIG. 13 shows an example with option 2.
  • WD 22 is configured with ScellO (with one BWP), SCelll (with two BWPs) and Scell2 (with 4 BWPs). All three Scells are in activated state (e.g, using a MAC CE based Scell activation command).
  • BWP1 of Scell 1 and BWP3 of SCell2 are not configured with any PDCCH monitoring candidates (e.g. denoted by BWP1* and BWP3* for convenience in FIG. 13).
  • the WD 22 Before reception of an LI command Cl, the WD 22 is not monitoring PDCCH on ScellO; on Scelll, the WD 22 is operating on BWP1 (which has no PDCCH monitoring candidates); and on Scell2 the WD 22 is operating on BWP1 (which has PDCCH monitoring candidates).
  • the WD 22 Upon reception of an LI command Cl (e.g., by WD’s 22 radio interface 82) with DCI bits corresponding to ⁇ SCellO,SCelll,Scell2 ⁇ set to ⁇ 1,1,0 ⁇ respectively, the WD 22 starts PDCCH monitoring (e.g., via processing circuitry 84, operational unit 34 and/or radio interface 82) on ScellO; on Scelll WD 22 switches to BWP0 (i.e., the BWP with PDCCH monitoring candidates); on Scell2 WD 22 switches to BWP3 (i.e., the BWP which has no PDCCH monitoring candidates since zero is indicated for this Scell).
  • PDCCH monitoring e.g., via processing circuitry 84, operational unit 34 and/or radio interface 82
  • BWP0 i.e., the BWP with PDCCH monitoring candidates
  • BWP3 i.e., the BWP which has no PDCCH monitoring candidates since zero is indicated for this Scell.
  • the WD 22 stops PDCCH monitoring on ScellO (since DCI bit set to 0); on Scelll WD 22 continues operating on BWP0; and on Scell2 WD 22 switches to BWP0 (which has PDCCH monitoring candidates and which can also be e.g. default/preconfigured BWP for this Scell).
  • the WD 22 can be configured (e.g., by network node 16) with N SCell(s) and for some or all of the N SCells the WD 22 can be configured (such as by network node 16) with more than one BWP.
  • the PDCCH DCI corresponding to the LI command can include
  • ceil(log2(NBx)) bits (where log2() is logarithm with base 2) corresponding to Scellx. If Scellx is configured with only one BWP the DCI includes 1 bit for Scellx and similar procedure as described for option 1 above is applied where if the one bit bx corresponding to Scellx is set for a first state (e.g. 1) the WD 22 can start/continue PDCCH monitoring (e.g., via processing circuitry 84, operational unit 34 and/or radio interface 82) on the Scellx and if bx is set to second state (e.g. 0) the WD 22 can stop PDCCH monitoring on the Scellx.
  • a first state e.g. 1
  • the WD 22 can start/continue PDCCH monitoring (e.g., via processing circuitry 84, operational unit 34 and/or radio interface 82) on the Scellx and if bx is set to second state (e.g. 0) the WD 22 can stop PDCCH monitoring
  • the WD 22 may adapt/modify/change (e.g., via processing circuitry 84, operational unit 34 and/or radio interface 82) the periodicity of PDCCH monitoring on Scellx based at least in part on the state of bx.
  • the WD 22 may monitor PDCCH on Scellx with a first periodicity if bx is set to the first state (e.g., 1) and may monitor PDCCH with a second periodicity if bx is set to the second state (e.g., 0).
  • the second periodicity may correspond to a periodicity that monitors the PDCCH less frequently than the first periodicity.
  • the second periodicity value can be set to infinity or a predefined value that indicates to stop PDCCH monitoring on Scellx.
  • one of the BWPs can be a BWP for which the WD 22 is not configured to monitor PDCCH (e.g., zero PDCCH monitoring candidates are configured for all search spaces and for aggregation levels configured for that BWP).
  • option 3 may be more flexible than options 1 or 2 discussed above, it may also have more overhead compared to these options.
  • a single DCI can be used for joint indication of BWP switching on some of the S cells and to start/stop PDCCH monitoring on a single BWP for some other of the Scells e.g., on Scells that correspond to single BWP.
  • FIG. 14 shows an example with option 3.
  • WD 22 is configured (e.g., by network node 16) with ScellO (with one BWP), SCelll (with two BWPs) and Scell2 (with 4 BWPs). All three Scells are in activated state (e.g, using a MAC CE based Scell activation command).
  • BWP1 of Scelll and BWP3 of SCell2 are not configured with any PDCCH monitoring candidates (e.g. denoted by BWP1* and BWP3* for convenience in Figure).
  • the WD 22 Before reception of an LI command Cl, the WD 22 is not monitoring PDCCH on ScellO; on Scelll, the WD 22 is operating on BWP1 (which has no PDCCH monitoring candidates); and on Scell2 the WD 22 is operating on BWP1 (which has PDCCH monitoring candidates).
  • the WD 22 stops PDCCH monitoring on ScellO; on Scelll, the WD 22 switches to BWPl which has indexl; and on Scell2 the WD 22 switches to BWPl which has index 1 which is mapped to DCI bit state 01.
  • the WD 22 can be configured with N SCell(s) and for some or all of the N SCells the WD 22 can be configured with more than one BWP.
  • the PDCCH DCI corresponding to the LI command can include a bitmap of NBx bits with first bit of the bitmap corresponding to first BWP of NBx BWPs, second bit corresponding to a second BWP of NBx BWPs and so on.
  • the DCI can include N such bitmaps for N Scells.
  • the WD 22 starts/continues monitoring PDCCH for those BWPs whose bits are set to 1 and stops PDCCH monitoring for those BWPs whose bits are set to 0. Similar to above examples, if the WD 22 is configured with only one BWP for Scellx, the bit indicates whether WD 22 can start/stop monitoring PDCCH for that SCell (e.g., via processing circuitry 84, operational unit 34 and/or radio interface 82). Alternatively, in one or more embodiments, the WD 22 may adapt/modify/change the periodicity of PDCCH monitoring on Scellx based at least in part on the state of bx.
  • the WD 22 may monitor PDCCH on Scellx with a first periodicity if bx is set to the first state (e.g., 1) and may monitor PDCCH with a second periodicity if bx is set to the second state (e.g., 0).
  • the second periodicity may correspond to a periodicity that monitors the PDCCH less frequently than the first periodicity.
  • the second periodicity value can be set to infinity or a predefined value that indicates to stop PDCCH monitoring on Scellx.
  • Option 4 has more overhead than options 1,2,3 but can provide extra flexibility e.g., for cases where WD 22 can operate with more than one active BWP in a given serving cell at a given time.
  • the WD 22 may be configured (e.g., by network node 16) with N SCell(s) and for one or more of the N S Cells the WD 22 may be configured (e.g., by network node 16) with more than one BWP.
  • the PDCCH DCI (e.g., from network node 16) corresponding to the LI command can include a PUCCH resource indicator (e.g., 3 bits).
  • a PUCCH resource indicator e.g., 3 bits.
  • the WD 22 can send a HARQ-ACK in the PUCCH resource given by the PUCCH resource indicator.
  • the PDCCH DCI (e.g., from network node 16) corresponding to the LI command can include a HARQ feedback timing indicator (e.g., 3 bits).
  • the WD 22 can transmit a HARQ-ACK in the PUCCH resource (given by the PUCCH resource indicator) where the slot in which the HARQ-ACK is transmitted is given by the HARQ feedback timing indicator.
  • the PDCCH DCI (e.g., from network node 16) corresponding to the LI command can include additional format bits indicating the format in which the bits corresponding to the Scell(s) are sent.
  • the format bits can indicate whether the bits corresponding to Scells are according to a first option (e.g. option 1) or a second option (e.g. option 2) of the options discussed above.
  • Higher layers can explicitly indicate (e.g., via higher layer signaling from network node 16) the number of bits per SCell within the DCI for LI command. For example, if the WD 22 is configured with multiple SCells with different number of BWPs per Scell, for simpler DCI formatting, higher layer can configure a fixed 2 bits per SCell regardless of the number of BWPs per Scell. If a WD 22 needs fewer states for an Scell, then additional states can be reserved.
  • the PDCCH DCI (e.g., from network node 16) corresponding to the LI command can include zero padding bits to size match the size of the PDCCH DCI to the size of PDCCH for another DCI format (e.g. DCI format 0-0 or 1-0).
  • the PDCCH DCI corresponding to the LI command can be configured to be monitored in common search space, in WD 22 search space or in both.
  • the PDCCH DCI corresponding to the LI command can include a cyclic redundancy check (CRC) (e.g. 24 bits), the CRC can be scrambled by an RNTI (radio network temporary identifier) that is specific to LI commands.
  • the RNTI can be different from C-RNTLRA-RNTI/P-RNTI/SI-RNTI/SP-CSI/MCS-C-RNTI (cell- RNTI/random access-RNTI/paging-RNTI/system information-RNTI/semi-persistent- channel state information/modulation and coding scheme-cell-RNTI) configured for the WD 22.
  • the RNTI can be a PDCCH monitoring RNTI or a PM-RNTI or Scell monitoring RNTI or SM-RNTI.
  • the WD 22 may be configured (e.g., by network node 16) with more than one RNTI to receive the PDCCH DCI corresponding LI commands.
  • the WD 22 may be configured with a first RNTI which corresponds to PDCCH DCI with the LI command having bits for a first set of Scells and a second RNTI which corresponds to PDCCH DCI with the LI command having bits for a second set of Scells.
  • Such a configuration is useful for cases where WD 22 has to receive Scell management bits for a large number of Scells and the size of PDCCH DCI exceeds the size of another DCI format to which it has to be size matched.
  • the WD 22 can apply the corresponding actions (e.g. start/stop of PDCCH monitoring, BWP switching), after a time offset t_offset.
  • the time offset can be from the slot in which the LI command is received by the WD 22. Alternately, the time offset can be from the slot in which the WD 22 transmits HARQ-ACK in response to successful decoding (or detecting) of the PDCCH DCI corresponding to the LI command.
  • the time offset can be used indicated to the WD 22 by separate bits in the PDCCH DCI. Alternately, the time offset can be a predefined value or a
  • the possible time offset value(s) can also be indicated by the WD 22 to the network node 16 via WD 22 capability signaling.
  • the time offset can depend on the numerology of the PDCCH and/or the numerology of the HARQ-ACK transmission. If the WD 22 is configured with multiple BWPs for an Scell, the time offset used by the WD 22 can depend on the BWP on which the WD 22 is operating on the Scell when an LI command corresponding to that Scell is received by the WD 22.
  • the WD 22 may apply a first time offset; and when switching from a BWP with PDCCH monitoring candidates to a BWP with no PDCCH monitoring candidates, the WD 22 may apply a second time offset.
  • the second time offset can be smaller than the first time offset.
  • the LI command indicates the WD 22 to stop PDCCH monitoring on Scellx
  • k_offset e.g. a certain number of slots.
  • the WD 22 is expected to start PDCCH monitoring for the Scell from slot n2+X. Knowing X in advance (i.e., before the LI‘on’ command is received) may allow the WD 22 to put its PDCCH decoding hardware in an appropriate sleep state based on X. Larger X value could allow the WD 22 to put its hardware in a state with higher power saving (i.e., by turning off most receiver (rx) components), while a smaller X would allow a state with relatively smaller power savings. However, as a trade-off, a smaller X would allow faster Scell management.
  • k offset can be configured for the WD 22 via higher layers (i.e., it can be indicated via RRC signalling or MAC CE signalling).
  • the WD 22 may have different k_offset values for different serving cells.
  • the LI command can be included in a PDCCH DCI scheduling PDSCH/PUSCH for the WD 22 for the corresponding Scell.
  • the bits corresponding‘TPC command for scheduled PUCCH’ field in DCI format 1-0 or 1-1 can be used for indicating‘off LI command and optionally k offset.
  • the PDCCH DCI corresponding to the LI command can include timer value Ttimer (e.g., a certain number of slots). If the WD 22 receives the LI command in slot nl, the WD 22 applies the second set of actions (e.g., via processing circuitry 84, operational unit 34 and/or radio interface 82) starting from slot nl+k_offset and for an amount of time given by the timer value after which the WD 22 stops applying the second set of actions is stopped.
  • Ttimer e.g., a certain number of slots
  • the LI command can be received by the WD 22 as a wake-up signal or a reference signal (e.g., CSI-RS) with a predefined resource/scrambling pattern.
  • the PDCCH corresponding to the LI command can be received by the WD 22 on the Pcell/PScell. If the LI command includes DCI bits corresponding to a set of Scells, the PDCCH corresponding to the LI command can be received by the WD 22 on a serving cell that is different from the set of Scells.
  • a set of Scells e.g., Scells in same frequency band as Scellx
  • This duration can occur starting from next slot in which DCI is received or alternate next slot after which a HARQ-ACK corresponding to the LI command is transmitted by the WD 22. If the DCI bits indicate that the WD 22 is to switch from a BWP2 to BWP1, there may be no need for WD 22 to stop transmitting/receiving on the set of Scells in response to the LI command. If any RF retuning is to be performed, the WD 22 can perform (e.g., via processing circuitry 84, operational unit 34 and/or radio interface 82) this at a later stage (e.g., during discontinuous reception (DRX) or measurement gap).
  • DRX discontinuous reception
  • the DCI bits discussed in options 1, 2, 3, 4 above can be included in the PDCCH DCI configured for power savings along with any other bits included for WD 22 power savings.
  • the PDCCH DCI corresponding to the LI command can be sent by the network to the WD 22 via a gNB or other network node 16.
  • DCI content for LI command is shown below:
  • -DCI format A_B is used for the transmission of LI commands for SCell PDCCH monitoring and associated BWP operation. -The following information is transmitted by means of the DCI format A_B with cyclic redundancy check (CRC) scrambled by SM-RNTI:
  • CRC cyclic redundancy check
  • the parameter Scell-in-SM-DCI provided by higher layers determines the index to the block number for the information of an Scell i, with the following fields defined for each block:
  • LI On/off indicator is 1 bit, otherwise there is no LI On/Off indicator in the block
  • Bandwidth part indicator - 0, 1 or 2 bits as determined by the number of DL BWPs By ⁇ RRC configured by higher layers for Scell i, excluding the initial downlink (DL) bandwidth part.
  • the bitwidth for this field is determined as
  • « BWP « BWP RRC + 1 if % VP.RRC 85 , in which case the bandwidth part indicator is equivalent to the ascending order of the higher layer parameter BWP -Id,
  • -DCI format A_B is used for the transmission of LI commands for SCell PDCCH monitoring and associated BWP operation.
  • the parameter Scell-in-SM-DCI provided by higher layers determines the index to the block number for the information of an Scell i, and the parameter length-of-Block-in-SM-DCI indicates the number of bits X for each block:
  • higher layers e.g., sent by network node 16
  • the number of information bits in format A_B may be equal to or less than the payload size of format 1 0 monitored in common search space in the same serving cell. If the number of information bits in format A_B is less than the payload size of format 1_0 monitored in common search space in the same serving cell, zeros may be appended to format A_B until the payload size equals that of format 1 0 monitored in common search space in the same serving cell.
  • the number of information bits in format A_B may be equal to or less than the payload size of format X_Y monitored in WD-specific search space in the same serving cell. If the number of information bits in format A_B is less than the payload size of format X_Y monitored in WD-specific search space in the same serving cell, zeros may be appended to format A_B until the payload size equals that of format X_Y monitored in WD-specific search space in the same serving cell.
  • the WD 22 can advantageously receive an LI command in PDCCH DCI with bit(s) corresponding to one or more SCell(s).
  • the WD 22 can use the bit(s) corresponding to the first Scell to turn on/tum off PDCCH monitoring on/for that SCell and/or adapt/modify/change PDCCH monitoring periodicity on/for that SCell.
  • the WD 22 can use the bit(s) corresponding to the second Scell to determine a BWP (of the multiple BWPs) to use for operation on the second SCell.
  • the WD 22 may be configured with zero PDCCH candidates on one of the multiple BWPs configured for the second SCell.
  • Embodiment A1 A network node configured to communicate with a wireless device (WD), the network node configured to, and/or comprising a radio interface and/or comprising processing circuitry configured to:
  • the layer 1 command configured to modify a periodicity for monitoring a downlink control channel.
  • Embodiment A2 The network node of Embodiment Al, wherein the layer 1 command is configured to reduce a periodicity for monitoring the downlink control channel based at least in part on a state of at least in bit in the layer 1 command.
  • Embodiment A3 The network node of Embodiment Al , wherein the L 1 command includes ki bits that indicate respective values for modifying the periodicity for monitoring the downlink control channel, each value corresponding to a bandwidth part.
  • Embodiment B A method implemented in a network node, the method comprising:
  • Embodiment B2 The method of Embodiment Bl, wherein the layer 1 command is configured to reduce a periodicity for monitoring the downlink control channel based at least in part on a state of at least in bit in the layer 1 command.
  • Embodiment B3 The method of Embodiment Bl, wherein the LI command includes ki bits that indicate respective values for modifying the periodicity for monitoring the downlink control channel, each value corresponding to a bandwidth part.
  • a wireless device configured to communicate with a network node, the WD configured to, and/or comprising a radio interface and/or processing circuitry configured to:
  • the layer 1 command configured to modify a periodicity for monitoring a downlink control channel.
  • Embodiment C2 The WD of Embodiment Cl, wherein the layer 1 command is configured to reduce a periodicity for monitoring the downlink control channel based at least in part on a state of at least in bit in the layer 1 command.
  • Embodiment C3 The WD of Embodiment Cl, wherein the LI command includes ki bits that indicate at least one value for modifying the periodicity for monitoring the downlink control channel, each value corresponding to a bandwidth part.
  • Embodiment C4 The WD of Embodiment C3, the WD is further configured to, and/or comprising a radio interface and/or processing circuitry further configured to switch to at least one of the bandwidth parts associated with the at least one value indicated by the ki bits.
  • Embodiment D1 A method implemented in a wireless device (WD), the method comprising:
  • the layer 1 command configured to modify a periodicity for monitoring a downlink control channel.
  • Embodiment D2 The method of Embodiment Dl, wherein the layer 1 command is configured to reduce a periodicity for monitoring the downlink control channel based at least in part on a state of at least in bit in the layer 1 command.
  • Embodiment D3. The method of Embodiment D 1 , wherein the L 1 command includes ki bits that indicate at least one value for modifying the periodicity for monitoring the downlink control channel, each value corresponding to a bandwidth part.
  • Embodiment D4 The method of Embodiment D3, further comprising switching to at least one of the bandwidth parts associated with the at least one value indicated by the ki bits.
  • the concepts described herein may be embodied as a method, data processing system, computer program product and/or computer storage media storing an executable computer program. Accordingly, the concepts described herein may take the form of an entirely hardware embodiment, an entirely software embodiment or an embodiment combining software and hardware aspects all generally referred to herein as a“circuit” or“module.” Any process, step, action and/or functionality described herein may be performed by, and/or associated to, a corresponding module, which may be implemented in software and/or firmware and/or hardware. Furthermore, the disclosure may take the form of a computer program product on a tangible computer usable storage medium having computer program code embodied in the medium that can be executed by a computer. Any suitable tangible computer readable medium may be utilized including hard disks, CD-ROMs, electronic storage devices, optical storage devices, or magnetic storage devices.
  • the computer program instructions may also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer implemented process such that the instructions which execute on the computer or other programmable apparatus provide steps for implementing the functions/acts specified in the flowchart and/or block diagram block or blocks.
  • Computer program code for carrying out operations of the concepts described herein may be written in an object oriented programming language such as Java® or C++.
  • the computer program code for carrying out operations of the disclosure may also be written in conventional procedural programming languages, such as the "C" programming language.
  • the program code may execute entirely on the user's computer, partly on the user's computer, as a stand-alone software package, partly on the user's computer and partly on a remote computer or entirely on the remote computer.
  • the remote computer may be connected to the user's computer through a local area network (LAN) or a wide area network (WAN), or the connection may be made to an external computer (for example, through the Internet using an Internet Service Provider).
  • LAN local area network
  • WAN wide area network
  • Internet Service Provider for example, AT&T, MCI, Sprint, EarthLink, MSN, GTE, etc.

Landscapes

  • Engineering & Computer Science (AREA)
  • Signal Processing (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

L'invention concerne un procédé et un appareil de signalisation de L1 permettant une gestion rapide de cellules secondaires (Scell). Selon un mode de réalisation, un procédé destiné à un nœud de réseau consiste à envoyer une instruction de couche 1, L1, dans des informations de commande de liaison descendante, DCI, sur une cellule primaire, PCell, l'instruction de L1 indiquant une périodicité de surveillance d'un canal de commande de liaison descendante physique, PDCCH, sur au moins une Scell de ladite Scell. Selon un autre mode de réalisation, un procédé destiné à un dispositif sans Fil (WD) consiste à recevoir une instruction de couche 1, L1, dans des informations de commande de liaison descendante, DCI, sur une cellule primaire, PCell ; et en réponse à la réception de l'instruction de L1, à adapter une périodicité de surveillance d'un canal de commande de liaison descendante physique, PDCCH, sur au moins une Scell de ladite Scell sur la base, au moins en partie, de l'instruction de L1.
PCT/SE2020/050445 2019-05-10 2020-05-04 Signalisation de couche 1 (l1) permettant une gestion rapide de cellules secondaires (scell) Ceased WO2020231311A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
US201962846208P 2019-05-10 2019-05-10
US62/846,208 2019-05-10

Publications (1)

Publication Number Publication Date
WO2020231311A1 true WO2020231311A1 (fr) 2020-11-19

Family

ID=73290301

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/SE2020/050445 Ceased WO2020231311A1 (fr) 2019-05-10 2020-05-04 Signalisation de couche 1 (l1) permettant une gestion rapide de cellules secondaires (scell)

Country Status (1)

Country Link
WO (1) WO2020231311A1 (fr)

Citations (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2016123393A1 (fr) * 2015-01-28 2016-08-04 Interdigital Patent Holdings, Inc. Signalisation de commande de liaison descendante

Patent Citations (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2016123393A1 (fr) * 2015-01-28 2016-08-04 Interdigital Patent Holdings, Inc. Signalisation de commande de liaison descendante

Non-Patent Citations (4)

* Cited by examiner, † Cited by third party
Title
ERICSSON: "Reduced latency Scell management for NR CA", R1-1909144, 26 August 2019 (2019-08-26), Prague, Czech Republic, XP051765749 *
ERICSSON: "Reduced latency Scell management for NR-NR CA", R1-1907333, 13 May 2019 (2019-05-13), Reno, USA, XP051709355 *
ERICSSON: "Summary of Efficient and low latency serving cell configuration/activation/setup", R1-1905835, 8 April 2019 (2019-04-08), Xi'an, China, XP051707882 *
ERICSSON: "Summary of email discussion [96b-NR-11", R1-1905915, 26 April 2019 (2019-04-26), XP051707958 *

Similar Documents

Publication Publication Date Title
US11647464B2 (en) Wake-up dci for wireless devices in connected mode
US12207197B2 (en) Method for causing a wireless device to enter a sleep state based on a GTS indication in a received DCI
US20250167971A1 (en) Serving cell activation and deactivation
US20250247854A1 (en) L1 signaling for scell dormancy indication
US20210400580A1 (en) Power-efficient configuration of time offset values
JP7579808B2 (ja) 高速な２次セル（ｓセル）管理のためのレイヤ１（ｌ１）シグナリング
US12082210B2 (en) Scell management for CA
US11963159B2 (en) Efficient BWP switching
US20210400761A1 (en) Methods and apparatuses for adaptive discontinuous reception configuration
WO2020201124A1 (fr) Informations d'état de canal rapide pendant l'activation de cellule secondaire dans un système new radio
WO2021071414A1 (fr) Nœud de réseau, dispositif sans fil et procédés en son sein permettant de réaliser des transmissions de liaison montante
US12490245B2 (en) Physical shared channel splitting at slot boundaries
EP3909177A1 (fr) Planification multi-créneau d'informations de commande de liaison descendante unique améliorée
WO2020231311A1 (fr) Signalisation de couche 1 (l1) permettant une gestion rapide de cellules secondaires (scell)

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 20806288

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 20806288

Country of ref document: EP

Kind code of ref document: A1