Method and apparatus for network energy saving
By activating or deactivating the on-demand SSB configuration of the secondary cell through MAC CE signaling, the on-demand SSB SCell operation of the UE is supported, which solves the problem of high base station power consumption in 5G networks and achieves network energy saving.
Patent Information
- Application Number
- CN202580024510.9
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Priority Date
- 2025-04-01
- Filing Date
- 2025-04-02
- Publication Date
- 2026-11-10
AI Technical Summary
Existing 5G network power-saving technologies lack detailed procedures and signaling methods for on-demand SSB SCell operations for UEs configured with CA and in the RRC_CONNECTED state, resulting in the inability to effectively reduce base station power consumption.
A method and apparatus are provided for activating or deactivating the on-demand synchronization signal block (SSB) configuration of a secondary cell (SCell) via MAC control unit (CE) signaling, enabling the UE to perform on-demand SSB SCell operations, including receiving and stopping on-demand SSB-based SCell operations.
By activating or deactivating SSB configurations on demand, base station power consumption can be reduced, network energy efficiency can be improved, and the service needs of different UEs can be adapted.
Smart Images

Figure CN123077206A_ABST
Abstract
Description
[0001] Cross-reference to related applications
[0002] This application claims the benefit of U.S. Provisional Application No. 63 / 573,555, filed April 3, 2024, entitled “Method and Apparatus for Network Energy Conservation”, and U.S. Application No. 19 / 096,830, filed April 1, 2025, entitled “Method and Apparatus for Network Energy Conservation”, the entire contents of which are incorporated herein by reference. Technical Field
[0003] This disclosure generally relates to wireless communications. More specifically, aspects of this disclosure relate to a method and apparatus for network energy saving. Background Technology
[0004] Unless otherwise stated herein, the methods described in this section are not prior art to the following claims and are not acknowledged as prior art by virtue of their inclusion in this section.
[0005] In recent years, due to the increase in the number of small cells and the use of massive MIMO antennas, network energy saving in 5G has received considerable attention. Reducing environmental impact and helping operators save operating costs are undoubtedly crucial. Therefore, targeted methods for 5G network energy saving need to be developed. In 3GPP Release 18, for network energy saving, an SSB-free (Synchronization Signal Block) SCell (Secondary Cell) operation technique based on inter-frequency CA (Carrier Aggregation) for FR1 and co-located cells was introduced. That is, for intra-frequency or inter-frequency CA SCells, without providing the UE with SSB configuration or SMTC (Synchronization Timing Configuration Based on SSB) configuration for that SCell, the UE can obtain timing references and AGC (Automatic Gain Control) sources from another serving cell, as described in TS 38.300 and TS 38.331 of Release 18. Furthermore, cell DTX / DRX (Discontinuous Transmission or Discontinuous Reception) mechanisms have been standardized to help reduce gNB downlink transmission or uplink reception activation time. Specifically, when cell DTX is configured and activated for a specific cell, during the cell DTX inactivity period of that specific cell, the UE may, under selected conditions, not listen to the PDCCH (Physical Downlink Control Channel) or not listen to the SPS (Semi-Persistent Scheduling) timing. When cell DRX is configured and activated for a specific cell, during the cell DRX inactivity period of that specific cell, the UE does not transmit CG (ConfiguredGrant) resources or SR (Scheduling Request). This feature only applies to UEs in the RRC_CONNECTED state and does not affect random access procedures, SSB transmissions, paging, and system information broadcasts. 3GPP Release 18 also includes other solutions to further save network (NW) power consumption. One solution is for the NG-RAN node with coverage cells to request neighboring NG-RAN nodes with capacity-enhanced cells to activate some deactivated SSB beams within that cell. Another solution is for the NG-RAN node to page certain UEs (e.g., stationary UEs) in the RRC_INACTIVE state on a limited set of beams, instead of paging on all beams within the cell.To avoid negative impacts on UEs that do not support network power saving features, if a cell is activating or about to activate NES cell DTX / DRX, the cell can allow UEs with NES cell DTX / DRX capabilities to access the cell through a single bit in SIB1, but use the blocking mechanism introduced in TS 38.300 version 18 to prevent UEs without cell DTX / DRX capabilities from accessing the cell.
[0006] Due to time constraints, some technologies that are beneficial for network energy saving have not yet been considered in 3GPP Release 18. There is an urgent need to introduce these beneficial technologies to fully achieve the goal of network energy saving.
[0007] One missing technology is support for on-demand SSB SCell operations for UEs (User Equipment) configured with CA in the RRC_CONNECTED state, as described in RP-234065. On-demand SSBs are not always sent by the cell, but only when the UE needs to perform time / frequency synchronization or SCell activation operations on the SSB-free cell. Because on-demand SSBs / SSB bursts are not always sent (or broadcast), base station power consumption can be reduced, especially when the cell does not need to provide service to any UE. However, the detailed procedures and signaling methods used to support on-demand SSB SCell operations are not yet clearly defined.
[0008] Therefore, how to design on-demand SSB SCell operation for network energy saving has become an important issue. Consequently, appropriate solutions are needed to address this problem. Summary of the Invention
[0009] The following overview is for illustrative purposes only and is not intended to be limiting in any way. That is, it is provided to introduce the concepts, key points, benefits, and advantages of the novel and non-obvious techniques described herein. Some, but not all, embodiments are further described in the detailed description below. Therefore, the following overview is not intended to identify the key features of the claimed subject matter, nor is it intended to determine the scope of the claimed subject matter.
[0010] Therefore, this disclosure provides a method and apparatus for network power saving. The main objective of this disclosure is to support on-demand SSB SCell operations for network power saving, including the design for performing on-demand SSB SCell operations for non-SSB SCells, the signaling for triggering the UE to perform on-demand SSB SCell operations for non-SSB SCells, the UE capabilities supporting on-demand SSB SCell operations, and the corresponding UE behaviors.
[0011] In an exemplary embodiment, a method for network power saving is provided. The method, implemented by a user equipment (UE), includes: receiving a first Medium Access Control (MAC) control element (CE), wherein the first MAC CE indicates that an on-demand synchronization signal block (SSB) configuration of a first secondary cell (SCell) is activated, and broadcasting one or more on-demand SSBs of the first SCell based on the on-demand SSB configuration. The method includes performing SCell operations based on the one or more on-demand SSBs. The method includes receiving a second MAC CE, wherein the second MAC CE indicates that the on-demand SSB configuration of the first SCell is deactivated. The method includes stopping the SCell operations based on the on-demand SSBs.
[0012] In an exemplary embodiment, an apparatus for network power saving is provided. The apparatus includes a transceiver and a processor. The transceiver wirelessly communicates with at least one network node during operation. The processor is communicatively coupled to the transceiver such that, during operation, the processor performs operations including: receiving a first Medium Access Control (MAC) control element (CE), wherein the first MAC CE indicates that an on-demand synchronization signal block (SSB) configuration for a first secondary cell (SCell) is activated, and broadcasting one or more on-demand SSBs for the first SCell based on the on-demand SSB configuration; performing an on-demand SSB-based SCell operation based on the one or more on-demand SSBs; receiving a second MAC CE, wherein the second MAC CE indicates that the on-demand SSB configuration for the first SCell is deactivated; and stopping the on-demand SSB-based SCell operation.
[0013] In an exemplary embodiment, a method for network energy saving is provided. The method is implemented by a source base station (BS) and includes: sending a first Medium Access Control (MAC) control element (CE) to a user equipment (UE), wherein the first MAC CE indicates that an on-demand synchronization signal block (SSB) configuration of a first secondary cell (SCell) is activated. The method further includes sending a second MAC CE to the UE, wherein the second MAC CE indicates that the on-demand SSB configuration of the first SCell is deactivated. Attached Figure Description
[0014] The accompanying drawings are included to provide a further understanding of this disclosure, and are incorporated in and form a part of this disclosure. The drawings illustrate embodiments of the present disclosure and, together with the description, serve to explain the principles of the disclosure. It should be understood that the drawings are not necessarily drawn to scale, as some components may not be shown to scale in actual implementation for the purpose of clearly illustrating the concepts of the disclosure.
[0015] Figure 1 The present disclosure illustrates a signaling process for adding an SCell by sending an RRC reconfiguration message having a first information element (IE) and a second IE from the network (NW) to the UE according to one embodiment of the present disclosure.
[0016] Figure 2 An on-demand SSBSCell operation triggered by an on-demand SSB notification command is illustrated according to one embodiment of this disclosure.
[0017] Figure 3 An on-demand SSB notification MAC CE for an octet is shown according to one embodiment of the present disclosure.
[0018] Figure 4 The UE capability reporting process according to one embodiment of the present disclosure is illustrated.
[0019] Figure 5 This is a block diagram of an exemplary communication system according to one embodiment of the present disclosure.
[0020] Figure 6 This is a flowchart of an exemplary process according to one embodiment of the present disclosure.
[0021] Figure 7 This is a flowchart of an exemplary process according to one embodiment of the present disclosure. Detailed Implementation
[0022] The following description contains specific information relating to exemplary embodiments in this disclosure. The accompanying drawings and detailed descriptions in this disclosure are only illustrative of exemplary embodiments. However, this disclosure is not limited to these exemplary embodiments only. Other variations and embodiments of this disclosure will be apparent to those skilled in the art. Unless otherwise stated, similar or corresponding elements in the various drawings are indicated by similar or corresponding reference numerals. Furthermore, the drawings and illustrations in this disclosure are generally not drawn to scale and are not intended to correspond to actual relative dimensions.
[0023] For the sake of consistency and ease of understanding, similar features may be identified by the same reference numerals in the exemplary figures (although not shown in some examples). However, features in different embodiments may differ in other respects, and therefore should not be narrowly limited to what is shown in the figures.
[0024] The specification uses the phrases "in one embodiment" or "in some embodiments," each of which can refer to one or more of the same or different embodiments. The term "coupled" is defined as a connection (whether direct or indirect via intermediate components) and is not necessarily limited to a physical connection. When the term "comprising" is used, it means "including but not limited to"; specifically, it indicates an open inclusion or membership in the described combination, group, series, and equivalents. The expression "at least one of A, B, and C" or "at least one of A, B, and C" means "only A, or only B, or only C, or any combination of A, B, and C."
[0025] Furthermore, for illustrative purposes rather than limiting, specific details such as functional entities, technologies, protocols, and standards are provided to offer an understanding of the described technologies. In other examples, detailed descriptions of well-known methods, technologies, systems, architectures, etc., are omitted to avoid making the description ambiguous due to unnecessary detail.
[0026] Those skilled in the art will readily recognize that any network function or algorithm described in this disclosure can be implemented by hardware, software, or a combination of hardware and software. The functions may correspond to modules, which can be software, hardware, firmware, or any combination thereof. Software implementations may include computer-executable instructions stored on a computer-readable medium, such as memory or other types of storage devices. For example, one or more microprocessors or general-purpose computers with communication processing capabilities may be programmed with corresponding executable instructions to execute the described network functions or algorithms. The microprocessor or general-purpose computer may be composed of an application-specific integrated circuit (ASIC), a programmable logic array, and / or use one or more digital signal processors (DSPs). Although some exemplary embodiments described in this specification are directed to software installed and executed on computer hardware, alternative exemplary embodiments implemented as firmware, hardware, or a combination of hardware and software are entirely within the scope of this disclosure.
[0027] Computer-readable media include, but are not limited to, random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), flash memory, compact disc read-only memory (CD-ROM), magnetic tape, magnetic tape, disk storage, or any other equivalent medium capable of storing computer-readable instructions.
[0028] Wireless communication network architectures (e.g., Long Term Evolution (LTE) systems, LTE-Advanced (LTE-A) systems, LTE-Advanced Pro systems, 5G New Radio (NR) Radio Access Networks (RANs), or 6G NR RANs) typically include at least one Base Station (BS), at least one User Equipment (UE), and one or more optional network elements providing connectivity to the network. The UE communicates with the network (e.g., Core Network (CN), Evolved Packet Core (EPC) network, Evolved Universal Terrestrial Radio Access Network (E-UTRAN), 5G Core (5GC), or the Internet) through the RAN established by one or more BSs.
[0029] It should be noted that in this disclosure, the UE may include, but is not limited to, a mobile station, mobile terminal or device, or a user communication radio terminal. For example, the UE may be a portable wireless device, including but not limited to a mobile phone, tablet computer, wearable device, sensor, vehicle, or personal digital assistant (PDA) with wireless communication capabilities. The UE is configured to receive and transmit signals to one or more cells in the radio access network via an air interface.
[0030] The BS can be configured to provide communication services based on at least one of the following radio access technologies (RATs): Worldwide Interoperability for Microwave Access (WiMAX), Global System for Mobile Communications (GSM, commonly referred to as 2G), GSM EDGE Radio Access Network (GERAN), General Packet Radio Service (GRPS), Universal Mobile Telecommunication System (UMTS, commonly referred to as 3G) based on Wideband-Code Division Multiple Access (W-CDMA), High-Speed Packet Access (HSPA), LTE, LTE-A, eLTE (evolved LTE, such as LTE connected to 5GC), NR (commonly referred to as 5G), 6G, and / or LTE-A Pro. However, the scope of this disclosure should not be limited to the protocols described above.
[0031] A BS can include, but is not limited to, Node B (NB) in UMTS, Evolved Node B (eNB) in LTE or LTE-A, Radio Network Controller (RNC) in UMTS, Base Station Controller (BSC) in GSM / GERAN, ng-eNB in an Evolved Universal Terrestrial Radio Access (E-UTRA) BS connected to 5GC, next-generation Node B (gNB) in 5G-RAN, and any other device capable of controlling wireless communication and managing radio resources within the cell. A BS can provide services to one or more UEs via a radio interface.
[0032] A Base Station (BS) is operable to provide radio coverage for a specific geographic area using multiple cells constituting a radio access network. The BS supports cell operation. Each cell is operable to provide service to at least one UE within its radio coverage area. More specifically, each cell (often referred to as the serving cell) provides service to one or more UEs within its radio coverage area (e.g., each cell schedules downlink resources and optional uplink resources for downlink packet transmission and optional uplink packet transmission for at least one UE within its radio coverage area). The BS can communicate with one or more UEs in a wireless communication system through multiple cells. Cells can allocate sidelink (SL) resources to support Proximity Service (ProSe) or Vehicle to Everything (V2X) services. Each cell can have overlapping coverage areas with other cells.
[0033] As mentioned above, the NR frame structure is designed to support flexible configuration to accommodate various next-generation (e.g., 5G) communication requirements, such as Enhanced Mobile Broadband (eMBB), Massive Machine Type Communication (mMTC), and Ultra-Reliable and Low-Latency Communication (URLLC), while meeting high reliability, high data rate, and low latency requirements. Orthogonal Frequency-Division Multiplexing (OFDM) technology, as agreed in the 3rd Generation Partnership Project (3GPP), can serve as the basis for NR waveforms. A scalable OFDM parameter set (numerology) can also be used, such as adaptive subcarrier spacing, channel bandwidth, and cyclic prefix (CP). Furthermore, two coding schemes are considered for NR: (1) Low-Density Parity-Check (LDPC) codes and (2) Polar codes. The coding scheme can be adapted and configured based on channel conditions and / or service applications.
[0034] Furthermore, it is considered that the transmission time interval (TX) of a single NR frame should include at least downlink (DL) transmission data, guard period, and uplink (UL) transmission data. The portions of the DL transmission data, guard period, and UL transmission data should also be configurable, for example, dynamically configured based on the NR network. Additionally, SL resources can be provided in the NR frame to support ProSe or V2X services.
[0035] Furthermore, the terms "system" and "network" are used interchangeably in this document. The term "and / or" is used only to describe the relationships between related objects, indicating that three relationships can exist. For example, A and / or B can indicate: A alone, A and B simultaneously, or B alone. Additionally, the character " / " in this document generally indicates that the preceding and following related objects are in an "or" relationship.
[0036] It should be understood that throughout this disclosure, the term "on-demand SSB SCell operation" is used interchangeably with the term "SCell operation based on on-demand SSB".
[0037] Design for on-demand SSB SCell operation
[0038] In one implementation, the UE may receive downlink (DL) signaling (e.g., RRC signaling, Medium Access Control (MAC) control element (CE), or Downlink Control Information (DCI)) to perform on-demand SSB-based SCell operations (e.g., by activating on-demand SSB configuration) and / or activate / deactivate the target SCell for a target SCell (e.g., a SCell without SSB). In one implementation, the target SCell for which the UE needs to perform on-demand SSB SCell operations (e.g., a SCell without SSB) may be a candidate cell configured by the network (NW) for carrier aggregation (CA) purposes (e.g., in the SCell configuration), and the state of the target SCell may be indicated as "activated" (e.g., when a specific information element (IE) exists) or "deactivated" (when a specific IE does not exist). For example, in a cell group configuration (e.g., CellGroupConfig In the first list (e.g., NW), NW can be in the first list. sCellToAddModList Add or modify SCells in the second list (e.g., sCellToReleaseListRelease the SCell in the first list. Each entry in the first list can be an SCell configuration, which includes the SCell's cell ID (SCell ID) (e.g., SCellIndex The SCell's serving cell configuration and / or the SCell's status (e.g., active or deactivated). The SCell's serving cell configuration may include bandwidth part (BWP) related information (e.g., uplink (UL) BWP configuration, downlink (DL) BWP configuration, or first active BWP, but should not be limited to this in this disclosure), DL data or control channel related information, UL data or control channel related information, and / or SCell deactivation timer (e.g., ...). sCellDeactivationTimer However, this disclosure should not be limited thereto. Each entry in the second list may be the SCell ID of the SCell (e.g., SCellIndex ), used to indicate that the associated SCell should be released.
[0039] In one implementation, the NW can configure the UE to add an SCell (e.g., a no-SSB SCell) using a first list, and the associated SCell configuration of that SCell can include a first IE indicating the SCell's state and a second IE indicating whether on-demand SSB SCell operations need to be performed (e.g., acquiring on-demand SSBs for a no-SSB cell to perform time or frequency synchronization for that no-SSB cell, and / or performing L1 or L3 measurements based on the on-demand SSBs for that no-SSB cell). In one implementation, when on-demand SSB SCell operations are required for an SCell, this means that the associated on-demand SSB configuration of that SCell is activated, allowing the UE to perform the on-demand SSB SCell operation using one or more on-demand SSBs broadcast based on the associated on-demand SSB configuration. In another implementation, when on-demand SSB SCell operations are not required for an SCell, this means that the associated on-demand SSB configuration of that SCell is deactivated, and since the UE can anticipate that one or more on-demand SSBs will not be broadcast based on the associated on-demand SSB configuration, the UE can stop on-demand SSB SCell operations. In one implementation, when a second IE indicating whether on-demand SSB SCell operation needs to be performed is present or set to a specific value (e.g., 1 or true) in the SCell configuration of the SCell, the UE receiving the SCell configuration can perform on-demand SSB SCell operation for the SCell (e.g., based on one or more on-demand SSBs broadcast according to the activated on-demand SSB configuration of the SCell). On-demand SSB SCell operation for the SCell may include actions such as performing cell search for the SCell, performing time or frequency synchronization for the SCell, performing L1 / L3 measurements for the SCell, and / or reporting measurement results based on one or more on-demand SSBs broadcast according to the activated on-demand SSB configuration of the SCell, but is not limited thereto in this disclosure. When configuring or instructing a UE (e.g., via RRC signaling or MAC CE) to perform on-demand SSB SCell operations for a SCell, the UE may follow relevant on-demand SSB information or configuration (e.g., on-demand SSB configuration) to perform the on-demand SSB SCell operations. This includes information related to the time or frequency of the on-demand SSB burst, the period and / or time of the on-demand SSB or SSB burst (e.g., when the on-demand SSB or SSB burst begins to be transmitted or broadcast, when the on-demand SSB or SSB burst stops to be transmitted and broadcast, or the time period for transmitting the on-demand SSB or SSB burst, but this disclosure is not limited thereto). Relevant on-demand SSB information or configuration (e.g., on-demand SSB configuration) for SSB SCells without an SSB may be provided via RRC signaling or MAC CE.The associated on-demand SSB information and configuration may also include information about the SSB to be sent in an SSB burst and / or the time interval between two SSB bursts. In another implementation, when the second IE (in the SCell configuration of the SCell) indicating whether on-demand SSB SCell operation is required is absent or set to another specific value (e.g., 0 or false), the UE receiving the SCell configuration of the SCell may not perform on-demand SSB SCell operation for that SCell.
[0040] Figure 1 This document illustrates a signaling process according to one embodiment of the present disclosure for adding an SCell by sending an RRC reconfiguration message with a first IE and a second IE from the network to the UE. When receiving RRC signaling including a configuration for adding an SCell (e.g., an SCell without an SSB), where the associated SCell configuration uses a first IE to indicate that the SCell's state is activated (e.g., the first IE exists and is set to a specific value, 1 or true), and uses a second IE to indicate that an on-demand SSB SCell operation needs to be performed (e.g., by activating the on-demand SSB configuration of the SCell)), the UE can perform an on-demand SSB SCell operation for that SCell and / or apply a corresponding SCell activation operation to activate the SCell. SCell activation operations may include Sounding Reference Signal (SRS) transmission on the associated SCell, Channel Status Information (CSI) reporting for the associated SCell, Physical Downlink Control Channel (PDCCH) monitoring on the associated SCell, PDCCH monitoring for the associated SCell, and / or Physical Uplink Control Channel (PUCCH) transmission on the associated SCell (when a PUCCH configuration for the associated SCell is configured), but are not limited thereto in this disclosure. In another embodiment, upon receiving a configuration including that for adding an SCell (where the associated SCell configuration uses a first IE to indicate that the SCell's status is activated and uses a second IE to indicate that an on-demand SSB SCell operation needs to be performed) and determining the configured first downlink BWP to be activated (e.g., by... firstActiveDownlinkBWP-IdWhen the specified SCell is not set to a dormant BWP, the UE can perform an on-demand SSB SCell operation and / or apply the corresponding SCell activation operation to activate the SCell. It should be noted that the UE may need to successfully complete the on-demand SSB SCell operation before applying the regular SCell operation. The UE determines the first configured downlink BWP to activate (e.g., by...) firstActiveDownlinkBWP-Id If the instruction is set to a dormant BWP, the UE may not need to apply the corresponding SCell activation operation to activate the SCell. Table 1 shows examples of UE (or MAC entity) operations.
[0041]
[0042] Table 1
[0043] In one implementation, under certain conditions, a higher layer (e.g., the UE's MAC layer) can inform, instruct, or notify a lower layer (e.g., the UE's PHY layer) to perform an on-demand SSB SCell operation for that SCell, for example, when the UE is configured to perform an on-demand SSB SCell operation for that SCell, or when receiving network (NW) signaling (e.g., RRC signaling, MAC CE, DCI, or on-demand SSB notification command) instructing the UE to perform an on-demand SSB SCell operation for that SCell. The higher layer (e.g., the UE's MAC layer) can do this by providing its SCell ID (e.g., ...). SCellIndex The UE can inform, instruct, or notify the lower layer (e.g., the UE's PHY layer) to perform an on-demand SSB SCell operation for the SCell, along with / or associated on-demand SSB related information / configuration. When the UE receives an on-demand SSB notification command for a SCell without an SSB, the UE can expect that an on-demand SSB or SSB burst will begin to be sent or broadcast, and may need to perform an on-demand SSB SCell operation to at least perform time or frequency synchronization and L1 / L3 measurement reporting (e.g., CSI reporting). In one implementation, the UE can perform an on-demand SSB SCell operation only for the SCell (e.g., a cell without an SSB) in the RRC_CONNECTED state. In another implementation, the lower layer (e.g., the UE's PHY layer) can inform or notify the higher layer (e.g., the UE's MAC layer or the UE's RRC layer) that the on-demand SSB SCell operation for the SCell has been successfully completed or not. The lower layer (e.g., the UE's PHY layer) can do so by providing the associated SCell ID (e.g., ...). SCellIndexThe NW can notify higher layers (e.g., the UE's MAC layer or RRC layer) that the on-demand SSB SCell operation for that SCell has been successfully completed. Lower layers (e.g., the UE's PHY layer) can notify higher layers (e.g., the UE's MAC layer or RRC layer) that the on-demand SSB SCell operation for that SCell has not been successfully completed by providing the associated SCell ID. Correspondingly, higher layers (e.g., the UE's MAC layer or RRC layer) can inform the NW that the on-demand SSB SCell operation for that SCell has been successfully completed and / or not successfully completed. In another implementation, when the NW receives a CSI report based on on-demand SSB or SSB burst measurements, the NW can consider the on-demand SSB SCell operation for the associated SCell to have been successfully completed.
[0044] In one implementation, upon receiving a configuration for adding an SCell (e.g., a SCell without an SSB), where the associated SCell configuration uses a first IE to indicate that the SCell is deactivated (e.g., the first IE is not present) and a second IE to indicate that an on-demand SSB SCell operation needs to be performed (e.g., by activating the on-demand SSB configuration of the SCell) , the UE can perform an on-demand SSB SCell operation for that SCell, but may not apply a corresponding SCell activation operation to activate the SCell. The purpose of performing an on-demand SSB SCell operation for a deactivated SCell may be to reduce the latency of activating the SCell without an SSB, since time or frequency synchronization and / or L1 or L3 measurements for the SCell without an SSB have been completed before applying the corresponding SCell activation operation. Examples of UE (or MAC entity) operations are shown in Table 2. An on-demand SSB notification command can instruct the associated on-demand SSB configuration of the SCell to be activated or deactivated. When the associated on-demand SSB configuration of an SCell is activated, the UE can perform on-demand SSB SCell operations for that SCell based on one or more on-demand SSBs broadcast according to the activated on-demand SSB configuration. When the associated on-demand SSB configuration of an SCell is deactivated, the UE can stop the ongoing on-demand SSB SCell operations for that SCell.
[0045]
[0046] Table 2
[0047] In one implementation, the UE can inform the NW whether the on-demand SSB SCell operation for the SCell (e.g., a SCell without an SSB) was successfully completed. For example, the UE can inform the NW via RRS signaling, MAC CE, UCI (Uplink Control Information), or UL signaling (e.g., CSI reporting) that the on-demand SSB SCell operation for the SCell with SCell ID #1 was successfully completed. As another example, the UE can inform the NW that the on-demand SSB SCell operation for the SCell with SCell ID #2 was not successfully completed. In this case, when the UE receives a MAC CE for activating the SCell with SCell ID #2 (e.g., a SCell activation / deactivation MAC CE introduced in TS 38.321 version 18), the UE may need to perform the on-demand SSB SCell operation again for that SCell, and apply the corresponding SCell activation operation to activate the SCell after the on-demand SSB SCell operation for that SCell is successfully completed. When the NW receives information from the UE indicating whether an on-demand SSB SCell operation for a given SCell was successfully completed, the NW can take appropriate action. For example, the NW is only allowed to send a MAC CE (e.g., a SCell activation / deactivation MAC CE as introduced in TS 38.321, version 18) to activate the SCell without an SSB if the on-demand SSB SCell operation for that SCell without an SSB was successfully completed. As another example, when the NW receives information from the UE that the on-demand SSB SCell operation for that SCell without an SSB was not successfully completed, the NW can instruct the UE to perform another on-demand SSB SCell operation for that SCell without an SSB via RRC signaling, MAC CE, DCI, or an on-demand SSB notification command. In some implementations, the on-demand SSB notification command may be a modified SCell activation / deactivation MAC CE. The original design of the SCell activation / deactivation MAC CE is as introduced in TS 38.321, version 18. In one implementation, when the UE receives a SCell activation / deactivation MAC CE for changing the state of the SCell from active to deactivated, the UE (or the UE's MAC entity) can stop any ongoing on-demand SSB SCell operations for that SCell.
[0048] In one implementation, upon receiving a configuration for adding an SCell (e.g., a SCell without an SSB) (where the associated SCell configuration uses a first IE to indicate that the SCell is active (e.g., the first IE exists and is set to a specific value, 1 or true), and uses a second IE to indicate that on-demand SSB SCell operation is not required (e.g., by deactivating the on-demand SSB configuration of the SCell)), the UE may not perform the on-demand SSB SCell operation for that SCell, but may apply a corresponding SCell activation operation to activate the SCell. In another implementation, the NW is not allowed to provide a configuration for adding a SCell without an SSB (where the associated SCell configuration uses a first IE to indicate that the SCell is active (e.g., the first IE exists and is set to a specific value, 1 or true), and uses a second IE to indicate that on-demand SSB SCell operation is not required). In another implementation, upon receiving a configuration for adding an SCell (e.g., a no-SSB SCell) (where the associated SCell configuration uses a first IE to indicate that the SCell is active (e.g., the first IE exists and is set to a specific value, 1 or true), and uses a second IE to indicate that on-demand SSB SCell operation is not required), the UE may report SCell activation failure (e.g., via a failure information message, MAC CE, or DCI).
[0049] In one implementation, upon receiving a configuration for adding an SCell (e.g., a no-SSB SCell) (where the associated SCell configuration uses a first IE to indicate that the SCell is inactive (e.g., the first IE does not exist) and uses a second IE to indicate that an on-demand SSB SCell operation is not required (e.g., by deactivating the on-demand SSB configuration of the SCell)), the UE may not perform an on-demand SSB SCell operation for the SCell and may not apply a corresponding SCell activation operation to activate the SCell.
[0050] In some implementations, under certain conditions, a higher layer (e.g., the MAC layer of the UE) may inform, instruct, or notify a lower layer (e.g., the PHY layer of the UE) not to perform time or frequency synchronization for that SCell (or its associated frequency or carrier), for example, if the SCell is configured, informed, or indicated as an SSB-free SCell, or if an activated SSB-free SCell is deactivated or released by an NW command (e.g., RRC signaling or MAC CE), but this disclosure is not limited thereto. In some implementations, under certain conditions, a higher layer (e.g., the MAC layer of the UE) may inform, instruct, or notify a lower layer (e.g., the PHY layer of the UE) of on-demand SSB information or configuration information for an SSB-free cell, for example, by receiving on-demand SSB information or configuration via RRC signaling or MAC CE, but this disclosure is not limited thereto.
[0051] Figure 2 An on-demand SSBSCell operation triggered by an on-demand SSB notification command according to one embodiment of this disclosure is illustrated. It should be noted that... Figure 2 One or more steps in the process may or may not be performed. For example, when the PCell knows that there is no predefined on-demand SSB information or configuration for the SCell, it may not be necessary. Figure 2 Step 201. Furthermore... Figure 2 The order of steps is not mandatory. For example, a PCell can send an on-demand SSB notification command before sending an on-demand SSB ON instruction to a (target) SSB-free SCell.
[0052] Step 201: An SSB-less SCell (or its associated base station) can provide on-demand SSB information or configuration to a cell (e.g., a cell that can serve the UE as the primary cell). The cell (e.g., a cell that can serve the UE as the primary cell) can send a request for its on-demand SSB information or configuration to the SSB-less SCell. If needed, the SSB-less SCell can provide the cell (e.g., a cell that can serve the UE as the primary cell) with the latest or updated on-demand SSB information or configuration.
[0053] Step 202: The UE's PCell can configure the SSB-less cell as an SCell via RRC signaling for carrier aggregation (CA) purposes (e.g., combining multiple frequency blocks or carriers to serve the UE with the highest experience quality). The initial state of the SSB-less cell can be "activated" or "deactivated," configured by the PCell (or its associated base station). In the same or different RRC signaling, the PCell (or its associated base station) can also provide the corresponding on-demand SSB information or configuration for the SSB-less cell configured as an SCell. The on-demand SSB information or configuration for the SSB-less cell may include time or frequency-related information of the on-demand SSB burst (e.g., the SSB to be transmitted in the SSB burst and / or the time interval between two SSB bursts), on-demand SSB / SSB burst period and / or time-related information (e.g., when the on-demand SSB / SSB burst begins to be transmitted or broadcast, when the on-demand SSB / SSB burst stops to be transmitted or broadcast, or the time period for transmitting the on-demand SSB / SSB burst), but should not be limited to this in this disclosure. In another implementation, the on-demand SSB information or configuration of an SSB-free cell can be provided in an on-demand SSB notification command (e.g., MAC CE). In another implementation, certain portions of the on-demand SSB information or configuration of an SSB-free cell can be provided via RRC signaling, and the remainder can be provided via MAC CE. For example, time or frequency-related information of the on-demand SSB burst can be provided via RRC signaling, while time-related information can be provided via MAC CE. In another implementation, all on-demand SSB information or configuration of an SSB-free cell can be provided via RRC signaling, and the PCell (or its associated base station) can update or change certain on-demand SSB information or configuration of the SSB-free cell via MAC CE or another RRC signaling.
[0054] Step 203: The UE's PCell (or its associated base station) can determine that the UE needs to perform on-demand SSB SCell operation for that SCell (e.g., an SSB-free SCell). Then, the PCell can send an on-demand SSB ON indication to that SCell. In one implementation, when on-demand SSB / SSB burst transmission is not required, the UE's PCell (or its associated base station) can send an on-demand SSB OFF indication to that SCell (e.g., an SSB-free SCell).
[0055] Step 204: The UE's PCell (or its associated base station) can send an on-demand SSB notification command to the UE. This on-demand SSB notification command can indicate the target SSB-free cell, for example, by using the SCell ID (e.g., SCellIndexThe on-demand SSB notification command may also include some or all of the on-demand SSB related information or configuration. When the UE receives the on-demand SSB notification command (e.g., to activate the received or configured on-demand SSB information or configuration), the UE can expect that the on-demand SSB for the SSB-less cell will be sent or broadcast based on the received or configured on-demand SSB information or configuration. In one implementation, the on-demand SSB notification command (e.g., to activate the received or configured on-demand SSB information or configuration) can instruct the UE to perform an on-demand SSB SCell operation for the target cell. That is, the UE can expect that the on-demand SSB for the SSB-less cell will be sent or broadcast based on the received or configured on-demand SSB configuration or information. In another implementation, the on-demand SSB notification command (e.g., to deactivate the received or configured on-demand SSB information or configuration) can instruct the UE to stop or suspend the on-demand SSB SCell operation for the target cell. That is, the UE can expect that the on-demand SSB for the SSB-less cell will not be sent or broadcast. For example, when a target cell is configured to deactivate or release, the UE's PCell (or its associated base station) can send an on-demand SSB SCell notification command to instruct the UE to stop the ongoing on-demand SSB SCell operation for the target cell. In one implementation, setting the value of a specific field in the on-demand SSB notification command to 1 indicates that the UE needs to perform an on-demand SSB SCell operation for the target cell. Setting the value of a specific field in the on-demand SSB notification command to 0 indicates that the UE does not need to perform (or needs to stop or pause) the on-demand SSB SCell operation for the target cell.
[0056] Step 205: The SSB-less cell can begin sending or broadcasting on-demand SSBs (or SSB bursts). For example, when it receives an on-demand SSB enable instruction from another cell, the SSB-less cell can begin sending or broadcasting on-demand SSBs (or SSB bursts). The SSB-less cell can send or broadcast on-demand SSBs or SSB bursts based on pre-given on-demand SSB configuration or information. In another implementation, when the SSB-less cell stops sending or broadcasting on-demand SSBs, it can begin sending or broadcasting regular SSBs (or SSB bursts) (e.g., based on SSB configuration or information provided in the system information). It should be noted that on-demand SSBs or SSB bursts and regular SSBs or SSB bursts can be configured with different sending or broadcasting periods. For example, on-demand SSBs or SSB bursts can be configured with shorter periods. Conversely, regular SSBs or SSB bursts can be configured with longer periods. In one implementation, when it receives an on-demand SSB disable instruction from another cell, the SSB-less cell can stop sending or broadcasting on-demand SSBs or SSB bursts.
[0057] Step 206: After receiving an on-demand SSB notification command (e.g., received or configured on-demand SSB information or configuration to activate the target SSB-free SCell) from the PCell (or its associated base station), the UE can perform on-demand SSB SCell operations for the target SSB-free SCell. For example, the UE can acquire the on-demand SSB of the SSB-free cell to perform time or frequency synchronization for the target SSB-free cell, and / or perform L1 or L3 measurements based on the on-demand SSB of the target SSB-free cell. In one implementation, when the target SSB-free SCell is active, the UE can perform on-demand SSB SCell operations for the target SSB-free SCell based on a pre-given on-demand SSB configuration or information (e.g., from RRC signaling or MAC CE). In one implementation, when the target SSB-less SCell is active and no on-demand SSB configuration or information (e.g., from RRC signaling or MAC CE) has been received, configured, or activated, the UE can perform an on-demand SSB SCell operation for the target SSB-less SCell based on regular SSB transmissions (e.g., SSB configuration or information provided in system information). In one implementation, setting the value of a specific field in the on-demand SSB notification command to 1 indicates that the UE needs to perform an on-demand SSB SCell operation for the target SSB-less SCell. Setting the value of a specific field in the on-demand SSB notification command to 0 indicates that the UE does not need to perform (or needs to stop or pause) the on-demand SSB SCell operation for the target SSB-less SCell.
[0058] Triggering on-demand SSB SCell operations
[0059] In one implementation, when the UE receives an on-demand SSB notification command for a configured SCell (e.g., RRC signaling or MAC CE for activating the associated on-demand SSB configuration), the UE can perform an on-demand SSB SCell operation for that configured SCell. The on-demand SSB SCell operation for a SCell may include performing a cell search for that SCell, performing time or frequency synchronization for that SCell, and / or performing L1 or L3 measurements for that SCell, but is not limited to these actions in this disclosure. In one implementation, when the UE receives an on-demand SSB notification command for an active configured SCell (e.g., RRC signaling or MAC CE for activating the associated on-demand SSB configuration), the UE can perform an on-demand SSB SCell operation for that configured SCell to at least maintain time or frequency synchronization and / or report CSI to the NW for reference. In this case, the UE can report CSI related to the on-demand SSB or SSB burst only while the on-demand SSB or SSB burst is still being transmitted or broadcast. When on-demand SSBs or SSB bursts are not transmitted or broadcast, the UE can report CSI when regular SSBs or SSB bursts (or always-on SSBs or SSB bursts) are transmitted or broadcast by the SCell. In one implementation, when the UE receives an on-demand SSB notification command (e.g., RRC signaling or MAC CE for activating the associated on-demand SSB configuration) for a configured SCell that is in a deactivated state, the UE can perform an on-demand SSB SCell operation for that configured SCell to achieve fast SCell activation. In this case, the UE can report CSI related to the on-demand SSB or SSB burst only when the on-demand SSB or SSB burst is still being transmitted or broadcast.
[0060] In one implementation, when the UE receives an on-demand SSB notification command for a configured SCell (e.g., a MAC CE or RRC signaling to activate the associated on-demand SSB configuration), the UE can perform an on-demand SSB SCell operation for that configured SCell after a time interval G1. For example, when the UE receives an on-demand SSB notification command (e.g., MAC CE) at time T1, the UE can expect that an on-demand SSB or SSB burst will be sent or broadcast at time T1+G1. The time units for T1 and G1 can be frames, time slots, subframes, symbols, or milliseconds (ms). The value of G1 can be provided by RRC signaling or the on-demand SSB notification command (e.g., MAC CE). The value of G1 can be configured, predetermined, or predefined. In one implementation, the higher layers of the UE (e.g., the MAC layer) can provide information about G1 and / or the on-demand SSB notification command to the lower layers of the UE (e.g., the PHY layer). Based on this information, the underlying layer of the UE can know when the UE starts performing on-demand SSBSCell operations for the target SCell, or when the UE stops or pauses the (ongoing) on-demand SSBSCell operations for the target SCell.
[0061] In one implementation, when the UE receives an on-demand SSB notification command for a configured SCell (e.g., MAC CE or RRC signaling for activating the associated on-demand SSB configuration), the UE can perform an on-demand SSB SCell operation for that configured SCell after time interval G1, until the NW sends a second command to notify that on-demand SSBs or SSB bursts will no longer be sent or broadcast. The second command can be RRC signaling or an on-demand SSB notification command (e.g., MAC CE). In one implementation, the on-demand SSB notification command can indicate whether on-demand SSB SCell operations for a SCell (e.g., a SCell without an SSB) should be performed, stopped, or suspended (e.g., by activating or deactivating the associated on-demand SSB configuration for that SCell). In one implementation, when the UE receives the second command associated with that SCell, the UE can immediately stop any ongoing on-demand SSB SCell operations for that SCell. In another implementation, when the UE receives the second command associated with that SCell, the UE can stop or suspend any ongoing on-demand SSB SCell operations for that SCell after time interval G2. For example, when the UE receives the second command at time T2, the UE can anticipate that the on-demand SSB or SSB burst will no longer be sent or broadcast at time T2+G2. The time units for T2 and G2 can be frames, time slots, subframes, symbols, or milliseconds. The value of G2 can be provided by RRC signaling or an on-demand SSB notification command (e.g., MAC CE). The value of G2 can be configured or predefined. In one implementation, the higher layer of the UE (e.g., the MAC layer) can provide information about G2, the on-demand SSB notification command, and / or the second command to the lower layer of the UE (e.g., the PHY layer). Based on this information, the lower layer of the UE can know when the UE begins performing on-demand SSB SCell operations for the target SCell, or when the UE stops or suspends (ongoing) on-demand SSB SCell operations for the target SCell.
[0062] In one implementation, when the UE receives an on-demand SSB notification command for a configured SCell (e.g., MAC CE or RRC signaling to activate the associated on-demand SSB configuration), the UE can perform an on-demand SSB SCell operation for that configured SCell after time interval G3, and stop any ongoing on-demand SSB SCell operations for that SCell after time interval G4. For example, when the UE receives an on-demand SSB notification command (e.g., MAC CE) at time T3, the UE can expect that an on-demand SSB or SSB burst will be sent or broadcast at time T3+G3. The UE can expect that an on-demand SSB or SSB burst will not be sent or broadcast at time T3+G4. The time units for T3, G3, and G4 can be frames, time slots, subframes, symbols, or milliseconds. The values of G3 and G4 can be provided by RRC signaling or the on-demand SSB notification command (e.g., MAC CE). The values of G3 and G4 can be configured or predefined. In one implementation, the higher layers of the UE (e.g., the MAC layer) can provide the lower layers of the UE (e.g., the PHY layer) with information about G3 / G4 and / or information about on-demand SSB notification commands. Based on this information, the lower layers of the UE can know when the UE begins performing on-demand SSB SCell operations for a target SCell, or when the UE stops or suspends (ongoing) on-demand SSB SCell operations for a target SCell. For example, when the UE receives an on-demand SSB notification command at time T3, the UE can expect that an on-demand SSB or SSB burst will be sent or broadcast at time T3+G3. The UE can expect that an on-demand SSB or SSB burst will not be sent or broadcast at time T3+G3+G4.
[0063] In one implementation, when the UE receives an on-demand SSB notification command for a configured SCell (e.g., MAC CE or RRC signaling to activate the associated on-demand SSB configuration), the UE can perform an on-demand SSB SCell operation for that configured SCell after time interval G3, and stop any ongoing on-demand SSB SCell operations for that SCell after time interval G4. However, when the UE is notified or configured to perform on-demand SSB SCell operations based on regular SSBs or SSB bursts, the UE can continue to perform on-demand SSB SCell operations based on regular SSBs or SSB bursts. In one implementation, once an on-demand SSB or SSB burst is not sent or broadcast (e.g., based on the on-demand SSB or SSB burst transmission or broadcast period or network notification), the UE can be notified or configured to perform on-demand SSB SCell operations based on regular SSBs or SSB bursts via RRC signaling or an on-demand SSB notification command (e.g., MAC CE).
[0064] In one implementation, the on-demand SSB notification command may be a MAC CE (i.e., an on-demand SSB notification MAC CE), identified by a MAC subheader having a specific logical channel identifier (LCID) or an extended LCID (eLCID). It should be noted that the LCID or eLCID of the on-demand SSB notification MAC CE is different from the LCID of the SCell activation / deactivation MAC CE (as introduced in TS 38.321, version 18). In one implementation, the on-demand SSB notification MAC CE may consist of at least one or more C fields and one or more R fields.
[0065] Figure 3 An octet of on-demand SSB notification MAC CE according to one embodiment of this disclosure is illustrated. It should be noted that other fields related to on-demand SSB information, such as time or frequency-related information of on-demand SSB bursts (e.g., the SSBs to be sent in an SSB burst and / or the time interval between two SSB bursts), and on-demand SSB periodicity and / or time-related information (e.g., when on-demand SSBs begin to be sent, when on-demand SSBs stop being sent, or the time period for sending on-demand SSBs), may also be included in the on-demand SSB notification MAC CE. Furthermore, the R field is used as a reserved bit.
[0066] In one implementation, the SSB notifies the C in the MAC CE on demand. i Field indicates that it has SCellIndex i's SCell's on-demand SSB state. When C i When a field is set to a specific value (e.g., 1), it means that it has SCellIndex The on-demand SSB or SSB burst of cell i is being (or will be) sent or broadcast (or the associated on-demand SSB configuration is activated). When C i When a field is set to a specific value (e.g., 0), it means that the on-demand SSB or SSB burst of the cell with SCellIndex i has not been (or will not be) sent or broadcast (or the associated on-demand SSB configuration is deactivated). The timing of sending or broadcasting the on-demand SSB or SSB burst of the cell can depend on different designs disclosed in the embodiments described above. In another embodiment, there is an on-demand SSB notification MAC CE with an octet identified by a MAC subheader having a first LCID (or eLCID), and an on-demand SSB notification MAC CE with four octets identified by a MAC subheader having a second LCID (or eLCID). An octet on-demand SSB notification MAC CE can consist of at least 7 OCs. iIt consists of a field and one R field. The on-demand SSB notification MAC CE with four octets can be at least composed of 31 Cs. i It consists of a field and one R field.
[0067] In another implementation, the SSB notifies the C in the MAC CE on demand. i Field indicates that it has SCellIndex i's SCell on-demand SSB SCell operation is triggered. When C i When a field is set to a specific value (e.g., 1), it means that the UE needs to target fields with... SCellIndex Cell i performs on-demand SSB SCell operations. When C i When a field is set to a specific value (e.g., 0), it means that the UE does not need to target fields with... SCellIndex Cell i performs (or needs to stop or pause) on-demand SSBSCell operations.
[0068] In one implementation, the SSB notifies the C in the MAC CE on demand. i The field indicates the on-demand SSB status of SCell i, where i is the ascending sequence number of the SCell ID in the SCell configured or notified as an SSB-free SCell. When C i When a field is set to a specific value (e.g., 1), it means that an on-demand SSB or SSB burst of SCell i is being (or will) sent or broadcast (or the associated on-demand SSB configuration is activated). When C i When the field is set to a specific value (e.g., 0), it means that the on-demand SSB or SSB burst of cell i has not been (or will not be) sent or broadcast (or the associated on-demand SSB configuration is deactivated). The timing of sending or broadcasting the on-demand SSB or SSB burst of the cell may depend on different designs disclosed in the embodiments described above.
[0069] In another implementation, the SSB notifies the C in the MAC CE on demand. i The field indicates the on-demand SSBSCell operation triggered for SCell i, where i is the ascending sequence number of the SCell ID in the SCell configured or notified as having no SSB SCell. When C i When a field is set to a specific value (e.g., 1), it means that the UE needs to target fields with... SCellIndex Cell i performs on-demand SSB SCell operations. When C i When a field is set to a specific value (e.g., 0), it means that the UE does not need to target fields with... SCellIndex Cell i performs (or needs to stop or pause) on-demand SSB SCell operations.
[0070] In one implementation, the SCell activation / deactivation MAC CE (as introduced in TS 38.321 version 18) can be modified to indicate the presence of an R field. SCellIndex i's SCell's on-demand SSB or SSB burst state. When the R field is set to a specific value (e.g., 0), the SCell activates / deactivates the C in the MAC CE. i Field indicates that it has SCellIndex The activation or deactivation state of i's SCell. When C i When a field is set to a specific value (e.g., 1), it means that it has SCellIndex Cell i can be activated. When C i When a field is set to a specific value (e.g., 0), it means that it has SCellIndex Cell i can be deactivated. When the R field is set to a specific value (e.g., 0), the Ci field in the SCell activation / deactivation MAC CE indicates that it has SCellIndex i's SCell's on-demand SSB state. When C i When a field is set to a specific value (e.g., 1), it means that it has SCellIndex The on-demand SSB or SSB burst of cell i is being (or will be) sent or broadcast (or the associated on-demand SSB configuration is activated). When C i When a field is set to a specific value (e.g., 0), it means that it has SCellIndex The on-demand SSB or SSB burst of cell i has not been (or will not be) sent or broadcast (or the associated on-demand SSB configuration has been deactivated).
[0071] In another implementation, the SCell activation / deactivation MAC CE (as introduced in version 18 TS 38.321) can be modified to indicate the presence of an R field. SCellIndex i's SCell's on-demand SSB or SSB burst state. When the R field is set to a specific value (e.g., 0), the SCell activates / deactivates the C in the MAC CE. i Field indicates that it has SCellIndex The activation or deactivation state of i's SCell. When C i When a field is set to a specific value (e.g., 1), it means that it has SCellIndex Cell i can be activated. When C i When a field is set to a specific value (e.g., 0), it means that it has SCellIndex Cell i can be deactivated. When the R field is set to a specific value (e.g., 0), SCell activates / deactivates C in MAC CE. i Field indicates that it has SCellIndexi's SCell on-demand SSB SCell operation is triggered. When C i When a field is set to a specific value (e.g., 1), it means that the UE needs to target fields with... SCellIndex Cell i performs on-demand SSB SCell operations. When C i When a field is set to a specific value (e.g., 0), it means that the UE does not need to target fields with... SCellIndex Cell i performs (or needs to stop or pause) on-demand SSB SCell operations.
[0072] In one implementation, based on the indication of the on-demand SSB notification MAC CE or SCell activation / deactivation MAC CE (or information included in the on-demand SSB notification MAC CE or SCell activation / deactivation MAC CE), the UE determines whether to perform an on-demand SSB SCell operation for that SCell, or to stop or suspend the on-demand SSB SCell operation for that SCell. For example, when the indication of the on-demand SSB notification MAC CE or SCell activation / deactivation MAC CE (or information included in the on-demand SSB notification MAC CE or SCell activation / deactivation MAC CE) indicates that an on-demand SSB or SSB burst for that SCell is being sent or broadcast (or will be sent or broadcast, or the associated on-demand SSB configuration is activated), the UE may perform an on-demand SSB SCell operation for that SCell. For example, when the on-demand SSB notification MAC CE or SCell activation / deactivation MAC CE indication (or information included in the on-demand SSB notification MAC CE or SCell activation / deactivation MAC CE) indicates that the on-demand SSB or SSB burst for that SCell has not been sent or broadcast (or will not be sent or broadcast, or the associated on-demand SSB configuration has been deactivated), the UE can stop or suspend on-demand SSB SCell operation for that SCell.
[0073] In one implementation, the network (NW) can configure a deactivation timer for each configured SCell (except for SCells configured with PUCCH). sCellDeactivationTimerWhen the deactivation timer expires, the associated SCell can be considered or determined to be deactivated. To prevent the SCell from transitioning to a deactivated state, the UE can restart the associated deactivation timer while an on-demand SSBSCell operation is in progress. In one implementation, when a deactivation timer for the SSB-less SCell is configured, the SSB-less SCell is active, and an on-demand SSBSCell operation for the SCell is in progress (or an on-demand SSB notification to the MAC CE or a SCell activation / deactivation MAC CE triggers an on-demand SSB SCell operation for the SCell), the UE (or the UE's MAC layer) can restart the associated deactivation timer. Examples of UE (or MAC entity) operations are shown in Table 3.
[0074]
[0075] Table 3
[0076] Table 4 shows examples of UE (or MAC entity) operations.
[0077]
[0078] Table 4
[0079] In one implementation, when a UE receives a SCell activation / deactivation MACCE for activating a deactivated SCell, and the deactivated SCell is notified (e.g., via RRC signaling or MAC CE) that it is an SSB-free SCell (or is considered an SSB-free SCell), the UE can first perform an on-demand SSB SCell operation (e.g., based on received or configured on-demand SSB information or configuration), and then apply a regular SCell activation operation. In one implementation, the network (NW) can add SCells (e.g., SSB-free SCells) to the UE using a first list configuration, and the associated SCell configuration includes a third IE for indicating that the SCell is an SSB-free SCell. In another implementation, when on-demand SSB information or configuration is configured for the SCell (or the SCell is associated with on-demand SSB information or configuration), the UE can consider the SCell as an SSB-free SCell.
[0080] UE capabilities
[0081] Figure 4This document illustrates a UE capability reporting process according to one embodiment of the present disclosure. When the network (NW) needs UE capability information, this process can be initiated for a UE in the RRC_CONNECTED state. That is, the NW can send a UE capability query message to the UE in S405 (i.e., UECapabilityEnquiry Message). Then, the UE can in S410 in the UE capability information message (i.e., UECapabilityInformation The requested UE capabilities are reported in the message.
[0082] In one implementation, the UE may report its ability to support on-demand SSB SCell operations. When the UE supports performing on-demand SSB SCell operations, this means that the UE is able to receive RRC signaling, MAC CE (e.g., on-demand SSB notification MAC CE or SCell activation / deactivation MAC CE), or DCI, which instruct the UE to perform on-demand SSB SCell operations for the indicated or target SCell (e.g., no SSB SCell). In another implementation, the UE may report its ability to receive on-demand SSB notification MAC CE or SCell activation / deactivation MAC CE. When the UE supports receiving on-demand SSB notification MAC CE or SCell activation / deactivation MAC CE, this means that the NW can send on-demand SSB notification MAC CE or SCell activation / deactivation MAC CE to instruct the UE to trigger on-demand SSB SCell operation (or activate / deactivate the associated on-demand SSB configuration) for a target SCell (e.g., a SCell without SSB). The UE can follow the information contained in the on-demand SSB notification MAC CE or SCell activation / deactivation MAC CE to perform on-demand SSB SCell operation for the target SCell based on the received or configured on-demand SSB information or configuration, in order to listen for or detect on-demand SSB or SSB bursts that are being sent or broadcast.
[0083] In one implementation, when the target SCell is active, the UE can report its ability to perform on-demand SSB SCell operations for the target SCell (e.g., a SCell without an SSB). When the UE supports performing on-demand SSB SCell operations for a target SCell that is "active," the UE can perform on-demand SSB SCell operations for the target SCell based on received or configured on-demand SSB information or configuration to listen for or detect on-demand SSBs or SSB bursts that are being transmitted or broadcast. If the UE does not have valid on-demand SSB information or configuration, the UE can perform on-demand SSB SCell operations for the target SCell based on regular SSBs or SSB bursts that are being transmitted or broadcast. Whether the UE can perform on-demand SSB SCell operations for the target SCell based on regular SSBs or SSB bursts may depend on NW indications or configurations, or on whether regular SSBs or SSB bursts are available. For example, system information (e.g., MIB or SIB1) may contain indications indicating whether regular SSBs or SSB bursts are being transmitted or broadcast. When this indicator is set to a specific value (e.g., 0), it means that a regular SSB or SSB burst is not sent or broadcast. Conversely, when the indicator is set to another specific value (e.g., 1), it means that a regular SSB or SSB burst is sent or broadcast.
[0084] In one implementation, when the target SCell is in a deactivated state, the UE can report its ability to perform on-demand SSB SCell operations for the target SCell (e.g., a SCell without an SSB).
[0085] In one implementation, the UE can report its ability to receive an on-demand SSB notification command to trigger on-demand SSB SCell operation for a target SCell (e.g., a SCell without an SSB). In one implementation, the UE can report its ability to receive an on-demand SSB notification MAC CE to trigger on-demand SSB SCell operation for a target SCell (e.g., a SCell without an SSB). In one implementation, the UE can report its ability to receive a modified SCell activation / deactivation MAC CE to trigger on-demand SSB SCell operation for a target SCell (e.g., a SCell without an SSB).
[0086] In one implementation, the UE can report its ability to receive an on-demand SSB notification command to stop or suspend on-demand SSB SCell operation for a target SCell (e.g., a PCell without an SSB). In one implementation, the UE can report its ability to receive an on-demand SSB notification MAC CE to stop or suspend on-demand SSB SCell operation for a target SCell (e.g., a SCell without an SSB). In one implementation, the UE can report its ability to receive a modified SCell activation / deactivation MAC CE to stop or suspend on-demand SSB SCell operation for a target SCell (e.g., a SCell without an SSB).
[0087] In some implementations, the aforementioned capabilities can be separated for TDD (Time Division Duplex) and FDD (Frequency Division Duplex). For example, a UE can report one capability that supports on-demand SSB SCell operation in TDD and another capability that supports on-demand SSB SCell operation in FDD.
[0088] In some embodiments, the aforementioned capabilities can be separated for FR1 (Frequency Range 1) and FR2 (Frequency Range 2). For example, a UE can report one capability that supports on-demand SSB SCell operation in FR1 and another capability that supports on-demand SSB SCell operation in FR2.
[0089] Figure 5 An exemplary communication system 500 having an exemplary communication device 510 and an exemplary network device 520 according to one embodiment of the present disclosure is shown. Each of the communication device 510 and the network device 520 can perform various functions to implement the network energy-saving schemes, techniques, processes and methods described herein, including the scenarios / schemes described above and the process 500 described below.
[0090] The communication device 510 may be part of an electronic device, such as a portable or mobile device, a wearable device, a wireless communication device, or a computing device (UE). For example, the communication device 510 may be implemented in a smartphone, smartwatch, personal digital assistant, digital camera, or computing device such as a tablet, laptop, or notebook computer. The communication device 510 may also be part of a machine-type device, such as an Internet of Things (IoT), Narrowband Internet of Things (NB-IoT), or Industrial Internet of Things (IIoT) device, such as a fixed or stationary device, a home appliance, a wired communication device, or a computing device. For example, the communication device 510 may be implemented in a smart thermostat, a smart refrigerator, a smart door lock, a wireless speaker, or a home control center. Alternatively, the communication device 510 may be implemented as one or more integrated circuit (IC) chips, such as, but not limited to, one or more single-core processors, one or more multi-core processors, one or more Reduced-instruction-set computing (RISC) processors, or one or more Complex-instruction-set computing (CISC) processors. Communication device 510 may include Figure 5 At least some of the components shown, such as processor 512. Communication device 510 may also include one or more other components unrelated to the embodiments presented in this disclosure (e.g., internal power supply, display device, and / or user interface device); therefore, for the sake of brevity, these components of communication device 510 are not listed in the present disclosure. Figure 5 It is shown in the text and is not described in the following text.
[0091] Network device 520 may be part of an electronic device, which may be a network node such as a BS, small cell, router, or gateway. For example, network device 520 may be implemented in a gNB in a 5G, B5G, 6G, IoT, NB-IoT, or IIoT network. Alternatively, network device 520 may be implemented as one or more IC chips, such as, but not limited to, one or more single-core processors, one or more multi-core processors, or one or more RISC or CISC processors. Network device 520 may include... Figure 5 At least some of the components shown, such as processor 522. Network device 520 may also include one or more other components (e.g., internal power supply, display device, and / or user interface device) unrelated to the embodiments presented in this disclosure; therefore, for the sake of brevity, these components of network device 520 are not listed in the present disclosure. Figure 5 It is shown in the text and is not described in the following text.
[0092] In one aspect, each of processors 512 and 522 may be implemented as one or more single-core processors, one or more multi-core processors, or one or more CISC processors. That is, although the singular term "processor" is used herein to refer to processors 512 and 522, according to this disclosure, in some embodiments each of processors 512 and 522 may include multiple processors, while in other embodiments a single processor. In another aspect, each of processors 512 and 522 may be implemented as hardware (and optionally firmware) having electronic components including, for example, but not limited to, one or more transistors, one or more diodes, one or more capacitors, one or more resistors, one or more inductors, one or more memristors, and / or one or more varactor diodes, configured and arranged to achieve a particular purpose according to this disclosure. In other words, in at least some embodiments, each of processors 512 and 522 is a dedicated machine specifically designed, arranged, and configured to perform specific tasks, including on-demand SSB SCell operations for network power saving in a UE (e.g., represented by communication device 510) and gNB (e.g., represented by network device 520) according to various embodiments of this disclosure.
[0093] In some embodiments, the communication device 510 may further include a transceiver 516 coupled to the processor 512 and capable of wirelessly transmitting and receiving control and data signals. In some embodiments, the transceiver 516 is capable of wireless communication with different types of gNBs on different RATs. In some embodiments, the transceiver 516 may be equipped with multiple antenna ports (not shown), for example, four antenna ports. That is, the transceiver 516 may be equipped with multiple transmit antennas and multiple receive antennas for multiple-input multiple-output (MIMO) wireless communication. In some embodiments, the network device 520 may further include a transceiver 526 coupled to the processor 522 and capable of wirelessly transmitting and receiving control and data signals. In some embodiments, the transceiver 526 is capable of wireless communication with different types of UEs on different RATs. In some embodiments, the transceiver 526 may be equipped with multiple antenna ports (not shown), for example, four antenna ports. That is, the transceiver 526 may be equipped with multiple transmit antennas and multiple receive antennas for MIMO wireless communication. Accordingly, the communication device 510 and the network device 520 can communicate wirelessly with each other via transceiver 516 and transceiver 526, respectively.
[0094] In some embodiments, the communication device 510 may further include a memory 514 coupled to the processor 512 and accessible by the processor 512 to store data. In some embodiments, the network device 520 may further include a memory 524 coupled to the processor 522 and accessible by the processor 522 to store data. Each of the memories 514 and 524 may include a random-access memory (RAM) type, such as dynamic RAM (DRAM), static RAM (SRAM), thyristor RAM (T-RAM), and / or zero-capacitor RAM (Z-RAM). Alternatively or additionally, each of memories 514 and 524 may include a read-only memory (ROM) type, such as mask ROM, programmable ROM (PROM), erasable programmable ROM (EPROM), and / or electrically erasable programmable ROM (EEPROM). Alternatively or additionally, each of memories 514 and 524 may include a non-volatile random-access memory (NVRAM) type, such as flash memory, solid-state memory, ferroelectric RAM (FeRAM), magnetoresistive RAM (MRAM), and / or phase-change memory.
[0095] Each of the communication device 510 and the network device 520 can be a communication entity capable of communicating with each other using various proposed schemes according to this disclosure. For illustrative and not limiting purposes, the following provides for implementations in or as a UE (e.g., Figure 1 , Figure 2 and Figure 4 The communication device 510 of the UE (in the network) and implemented in or as a network (e.g., Figure 1 and Figure 4 In the network or Figure 2 Description of the operation, functions and capabilities of the PCell network device 520.
[0096] According to certain embodiments of this disclosure, the processor 512 of the communication device 510 may receive a first Medium Access Control (MAC) control element (CE) from the network device 520 via a transceiver 516. Specifically, the first MAC CE indicates that the on-demand synchronization signal block (SSB) configuration of the first secondary cell (SCell) is activated, and broadcasts one or more on-demand SSBs of the first SCell based on the on-demand SSB configuration. The processor 512 may then perform SCell operations based on the one or more on-demand SSBs. Next, the processor 512 may receive a second MAC CE from the network device 520 via the transceiver 516, wherein the second MAC CE indicates that the on-demand SSB configuration of the first SCell is deactivated. The processor 512 may then stop the on-demand SSB-based SCell operations.
[0097] Figure 6 An exemplary process 600 according to one embodiment of this disclosure is illustrated. Process 600 may be an exemplary embodiment of some or all of the above-described scenarios / solutions regarding methods for network power saving. Process 600 may represent one aspect of an embodiment of features of communication device 510. Process 600 may include one or more operations, actions, or functions as shown in one or more of blocks S605, S610, S615, and S620. Although shown as discrete blocks, the individual blocks of process 600 may be divided into additional blocks, combined into fewer blocks, or eliminated, depending on the desired implementation. Furthermore, the blocks of process 600 may be arranged in... Figure 6 The process 600 may be executed in the order shown, or alternatively, in a different order. Process 600 may be implemented by communication device 510 or any suitable UE. For illustrative purposes only and not for limitation, process 600 is described below in the context of communication device 510 as a UE and network device 520 as a network or BS. Process 600 may begin at block S605.
[0098] In S605, process 600 may involve the processor 512 of communication device 510 receiving a first Medium Access Control (MAC) control element (CE) via transceiver 516, wherein the first MAC CE indicates that the on-demand synchronization signal block (SSB) configuration of the first secondary cell (SCell) is activated, and broadcasting one or more on-demand SSBs of the first SCell based on the on-demand SSB configuration. Process 600 may proceed from S605 to S610.
[0099] In S610, process 600 may involve the processor 512 of the communication device 510 performing an SCell operation based on the one or more on-demand SSBs. Process 600 can proceed from S610 to S615.
[0100] In S615, process 600 may involve the processor 512 of communication device 510 receiving a second MACCE via transceiver 516, wherein the second MACCE indicates that the on-demand SSB configuration of the first SCell is deactivated. Process 600 can proceed from S615 to S620.
[0101] In step S620, process 600 may involve the processor 512 of communication device 510 stopping SCell operation based on on-demand SSB.
[0102] In some implementations, on-demand SSB configuration is received via Radio Resource Control (RRC) signaling.
[0103] In some implementations, the on-demand SSB configuration includes the period of the one or more on-demand SSBs, which is configured separately from the period of one or more regular broadcast SSBs of the first SCell.
[0104] In some implementations, process 600 may involve the processor 512 of communication device 510 receiving Radio Resource Control (RRC) signaling to indicate whether the on-demand SSB configuration of the first SCell is activated.
[0105] In some implementations, process 600 may involve the processor 512 of communication device 510 stopping SCell operation based on on-demand SSB upon receiving a third MAC CE to deactivate the first SCell.
[0106] In some implementations, SCell operation based on on-demand SSB includes at least one of the following actions: performing a cell search procedure for a first SCell; performing a time synchronization procedure for the first SCell; performing a frequency synchronization procedure for the first SCell; performing L1 measurement based on the one or more on-demand SSBs; performing L3 measurement based on the one or more on-demand SSBs and reporting the measurement results to the source base station.
[0107] In some implementations, the first MAC CE has multiple cell index fields, and each different cell index field in the multiple cell index fields corresponds to a different SCell and indicates whether the on-demand SSB configuration of the different SCell is activated or deactivated.
[0108] In some implementations, when the on-demand SSB configuration is activated, one or more on-demand SSBs of the first SCell are broadcast at a first moment, and this first moment is calculated based on the reception time of the first MAC CE and a predefined timeslot value.
[0109] In some implementations, process 600 may involve the processor 512 of communication device 510 reporting the ability to support SCell operations based on on-demand SSB.
[0110] Figure 7 An exemplary process 700 according to one embodiment of this disclosure is illustrated. Process 700 may be an exemplary embodiment of some or all of the above scenarios / solutions regarding methods for network power saving. Process 700 may represent one aspect of an embodiment of features of network device 520. Process 700 may include one or more operations, actions, or functions as shown in one or more of blocks S705 and S710. Although shown as discrete blocks, the individual blocks of process 700 may be divided into additional blocks, combined into fewer blocks, or eliminated, depending on the desired implementation. Furthermore, the blocks of process 700 may be arranged in... Figure 7 The process 700 may be executed in the order shown, or alternatively, in a different order. Process 700 may be implemented by network device 520 or any suitable network. For illustrative purposes only and not for limitation, process 700 is described below in the context of communication device 510 as a UE and network device 520 as a network or BS. Process 700 may begin at block S705.
[0111] In S705, process 700 may involve the processor 522 of network device 520 sending a first Medium Access Control (MAC) control element (CE) to communication device 510 via transceiver 526, wherein the first MAC CE indicates that the synchronization signal block (SSB) configuration of the first secondary cell (SCell) is activated. Process 700 can proceed from S705 to S710.
[0112] In S710, process 700 may involve the processor 522 of network device 520 sending a second MAC CE to the UE via transceiver 526, wherein the second MAC CE indicates that the on-demand SSB configuration of the first SCell is deactivated.
[0113] While this disclosure has been described by way of example and in conjunction with preferred embodiments, it should be understood that this disclosure is not limited to the disclosed embodiments. Rather, it is intended to cover various modifications and similar arrangements (as will be apparent to those skilled in the art). Therefore, the scope of the appended claims should be interpreted in the broadest possible sense to cover all such modifications and similar arrangements.
Claims
1. A method for network energy saving, wherein the method is implemented by user equipment (UE), comprising: Receive a first Medium Access Control (MAC) Control Element (CE), wherein the first MAC CE indicates that the Synchronization Signal Block (SSB) configuration of the first secondary cell (SCell) is activated, and broadcasts one or more on-demand SSBs of the first SCell based on the on-demand SSB configuration; Perform SCell operations based on the one or more on-demand SSBs; Receive a second MAC CE, wherein the second MAC CE indicates that the on-demand SSB configuration of the first SCell is deactivated; as well as Stop the SCell operation based on on-demand SSB.
2. The method for network energy saving as claimed in claim 1, wherein the on-demand SSB configuration is received via Radio Resource Control (RRC) signaling.
3. The method for network energy saving as claimed in claim 1, wherein the on-demand SSB configuration includes the period of the one or more on-demand SSBs, the period being configured separately from the period of one or more regular broadcast SSBs of the first SCell.
4. The method for network energy saving as described in claim 1, further comprising: Receive Radio Resource Control (RRC) signaling to indicate whether the on-demand SSB configuration of the first SCell is activated.
5. The method for network energy saving as described in claim 1, further comprising: When a third MAC CE is received to deactivate the first SCell, the SCell operation based on on-demand SSB is stopped.
6. The method for network energy saving as claimed in claim 1, wherein the SCell operation based on on-demand SSB includes at least one of the following actions: Execute the cell search process for the first SCell; Execute the time synchronization process for the first SCell; Perform the frequency synchronization process for the first SCell; L1 measurements are performed based on one or more on-demand SSBs; L3 measurements are performed based on one or more on-demand SSBs; and Report the measurement results to the source base station.
7. The method for network energy saving as claimed in claim 1, wherein the first MAC CE has a plurality of cell index fields, and each different cell index field of the plurality of cell index fields corresponds to a different SCell, and indicates whether the on-demand SSB configuration of the different SCell is activated or deactivated.
8. The method for network energy saving as claimed in claim 1, wherein when the on-demand SSB configuration is activated, the one or more on-demand SSBs of the first SCell are broadcast at a first moment, and the first moment is calculated based on the reception time of the first MAC CE and a predefined time slot value.
9. The method for network energy saving as described in claim 1, further comprising: Report the capability to support the aforementioned SCell operations based on on-demand SSB.
10. A device for network energy saving, comprising: A transceiver that communicates wirelessly with at least one network node during operation; as well as A processor, communicatively coupled to the transceiver, enables the processor to perform operations including the following during operation: Receive a first Medium Access Control (MAC) Control Element (CE), wherein the first MAC CE indicates that the Synchronization Signal Block (SSB) configuration of the first secondary cell (SCell) is activated, and broadcasts one or more on-demand SSBs of the first SCell based on the on-demand SSB configuration; Perform SCell operations based on the one or more on-demand SSBs; Receive a second MAC CE, wherein the second MAC CE indicates that the on-demand SSB configuration of the first SCell is deactivated; as well as Stop the SCell operation based on on-demand SSB.
11. The apparatus for network energy saving as claimed in claim 10, wherein the on-demand SSB configuration is received via Radio Resource Control (RRC) signaling.
12. The apparatus for network energy saving as claimed in claim 10, wherein the on-demand SSB configuration includes the period of the one or more on-demand SSBs, the period being configured separately from the period of one or more regular broadcast SSBs of the first SCell.
13. The apparatus for network energy saving as claimed in claim 10, wherein the processor further performs operations including: Receive Radio Resource Control (RRC) signaling to indicate whether the on-demand SSB configuration of the first SCell is activated.
14. The apparatus for network energy saving as claimed in claim 10, wherein the processor further performs operations including: When a third MAC CE is received to deactivate the first SCell, the SCell operation based on on-demand SSB is stopped.
15. The apparatus for network power saving as claimed in claim 10, wherein the SCell operation based on on-demand SSB includes at least one of the following actions: Execute the cell search process for the first SCell; Execute the time synchronization process for the first SCell; Perform the frequency synchronization process for the first SCell; L1 measurements are performed based on one or more on-demand SSBs; L3 measurements are performed based on one or more on-demand SSBs; and Report the measurement results to the source base station.
16. The apparatus for network energy saving as claimed in claim 10, wherein the first MAC CE has a plurality of cell index fields, and each different cell index field of the plurality of cell index fields corresponds to a different SCell and indicates whether the on-demand SSB configuration of the different SCell is activated or deactivated.
17. The apparatus for network energy saving as claimed in claim 10, wherein when the on-demand SSB configuration is activated, the one or more on-demand SSBs of the first SCell are broadcast at a first moment, and the first moment is calculated based on the reception time of the first MAC CE and a predefined time slot value.
18. The apparatus for network energy saving as claimed in claim 10, wherein the processor further performs operations including: Report the capability to support the aforementioned SCell operations based on on-demand SSB.
19. A method for network energy saving, wherein the method is implemented by a source base station, comprising: Send a first Medium Access Control (MAC) Control Element (CE) to User Equipment (UE), wherein the first MAC CE indicates that the Synchronization Signal Block (SSB) configuration of the Secondary Cell (SCell) is activated; as well as A second MAC CE is sent to the UE, wherein the second MAC CE indicates that the on-demand SSB configuration of the first SCell is deactivated.
20. The method for network energy saving as described in claim 19, further comprising: The UE is sent Radio Resource Control (RRC) signaling to indicate whether the on-demand SSB configuration of the first SCell is activated.
21. The method for network energy saving as claimed in claim 19, wherein the first MAC CE has a plurality of cell index fields, and each different cell index field of the plurality of cell index fields corresponds to a different SCell and indicates whether the on-demand SSB configuration of the different SCell is activated or deactivated.
