Acquisition of system information

Abstract

Aspects of the disclosure relate to acquisition of system information. In one aspect, a user equipment receives, from a base station, a first downlink control information (DCI) for paging in a first carrier or a first synchronization signal and a physical broadcast channel (PBCH) block (SSB) in a second carrier, where the first DCI includes a short message. And under the condition that the first DCI is received, the user equipment acquires system information of the second carrier in the first carrier based on the short message. In a case where the first SSB is received, the user equipment determines whether a system information block (SIB) is transmitted in a second carrier based on the first SSB. In this manner, a scheme for instructing a UE to acquire system information of a second carrier is designed.

Description

Technical Field

[0001] This disclosure relates to wireless communication, and more particularly to user equipment (UE) for obtaining system information, base stations, processors for wireless communication, methods, and non-transitory computer-readable media. Background Technology

[0002] A wireless communication system may include one or more network communication devices (such as base stations), which may also be referred to as eNodeB (eNB), next-generation NodeB (gNB), or other suitable terms. Each network communication device (such as a base station) may support wireless communication for one or more user communication devices, which may also be referred to as user equipment (UE), or other suitable terms. The wireless communication system may support wireless communication with one or more user communication devices by utilizing the resources of the wireless communication system (e.g., time resources (e.g., symbols, time slots, subframes, frames, etc.) or frequency resources (e.g., subcarriers, carriers)). Additionally, the wireless communication system may support wireless communication across a variety of radio access technologies, including third-generation (3G) radio access technology, fourth-generation (4G) radio access technology, fifth-generation (5G) radio access technology, and other suitable radio access technologies above 5G (e.g., sixth-generation (6G)).

[0003] In 5G New Radio (NR) systems, synchronization signals and Physical Broadcast Channel (PBCH) blocks (SSBs) are used by the UE to obtain the Physical Cell Identifier (ID), achieve downlink (DL) synchronization, and acquire system information. For example, the UE can determine whether Control Resource Set #0 (CORESET#0) exists in the cell based on the SSB. If the UE determines that CORESET#0 exists, the UE can acquire System Information Block 1 (SIB1) for the cell, at least based on a CORESET=0 configuration. Enhancements to the acquisition of system information are still needed. Summary of the Invention

[0004] This disclosure relates to a UE for acquiring system information, a base station, a processor for wireless communication, a method, and a non-transitory computer-readable medium.

[0005] In a first aspect of this solution, the user equipment receives a first downlink control information (DCI) for paging in a first carrier or a first synchronization signal and a physical broadcast channel (PBCH) block (SSB) in a second carrier from a base station, wherein the first DCI includes a short message. Upon receiving the first DCI, the user equipment obtains system information for the second carrier in the first carrier based on the short message. In this way, a scheme for on-demand system information acquisition is proposed, thereby reducing resource consumption in the transmission of system information. Furthermore, reusing the paging DCI for the instruction to obtain system information for another carrier is beneficial in terms of, for example, reducing signaling overhead and reducing the workload of UE implementation. Upon receiving the first SSB, the user equipment determines whether a system information block (SIB) is transmitted in the second carrier based on the first SSB. In this way, the UE can know whether the second carrier is an energy-saving (ES) carrier or a non-ES carrier. If the second carrier is an ES carrier, an ES-enabled UE can therefore be instructed to perform relevant actions to obtain the system information for the ES carrier. In summary, a scheme for instructing an ES-enabled UE to obtain the system information for the ES carrier is designed.

[0006] Some implementations of the methods and apparatus described herein may further include: switching from a first carrier to a second carrier upon receiving a first DCI; and receiving a first SSB of the second carrier from a base station in the second carrier.

[0007] In some implementations of the methods and apparatus described herein, a short message may include a bit field indicating at least one of the following: system information acquisition; or carrier switching.

[0008] In some implementations of the methods and apparatus described herein, the first DCI may include scheduling information of the system information of the second carrier, and the system information of the second carrier is scheduled by the scheduling information.

[0009] In some implementations of the methods and apparatus described herein, the first DCI may include an indication that scheduling information exists in the first DCI.

[0010] Some implementations of the methods and apparatus described herein may further include: receiving a second DCI from a base station in a first carrier during a first timing associated with the scheduling of a system information block. The first timing occurs after a paging timing associated with the first DCI or after a paging frame containing that paging timing.

[0011] Some implementations of the methods and apparatus described herein may further include: receiving a second DCI from a base station within a time window that includes at least one timing associated with the scheduling of system information blocks, on a first carrier. The time window is after a paging opportunity associated with the first DCI, or after a paging frame containing that paging opportunity.

[0012] In some implementations of the methods and apparatus described herein, the second DCI is scrambled by a Radio Network Temporary Identifier (RNTI), which is different from the System Information RNTI (SI-RNTI), and the System Information is scheduled by scheduling information in the second DCI.

[0013] In some implementations of the methods and apparatus described herein, the second DCI is scrambled by SI-RNTI. Some implementations of the methods and apparatus described herein may also include: receiving an SIB scheduled by the second DCI from a base station in a first carrier. The SIB may include an indication indicating whether system information of the second carrier or scheduling information of the system information of the second carrier is included in the SIB.

[0014] In some implementations of the methods and apparatus described herein, the second DCI is scrambled by SI-RNTI. Some implementations of the methods and apparatus described herein may also include: receiving an SIB scheduled by the second DCI from a base station in a first carrier. The second DCI may include an indication indicating whether system information of the second carrier or scheduling information of the system information of the second carrier is included in the SIB.

[0015] In some implementations of the methods and apparatus described herein, the first SSB may include information elements regarding subcarrier offset parameters. Some implementations of the methods and apparatus described herein may also include determining the configuration of the control resource set (CORESET) of the second carrier based on the first SSB of the second carrier, provided that a first value is indicated in the information elements.

[0016] Some implementations of the methods and apparatus described herein may further include: determining that the first SSB provides a valid configuration for CORESET when the first value is indicated in the information element.

[0017] In some implementations of the methods and apparatus described herein, determining whether the SIB is transmitted on the second carrier may include: determining that the SIB is not transmitted on the second carrier if a first value is indicated in the information element.

[0018] Some implementations of the methods and apparatus described herein may further include: receiving a second SSB of the first carrier from a base station in the first carrier; and determining a subcarrier offset based on information elements in the second SSB, the subcarrier offset being used for the frequency position of the CORESET of the second carrier.

[0019] In some implementations of the methods and apparatus described herein, the first SSB may include information elements regarding subcarrier offset parameters. Some implementations of the methods and apparatus described herein may also include: determining a first carrier based on the first SSB, provided a second value is indicated in the information elements; and determining the configuration of the CORESET of the second carrier and system information of the second carrier within the first carrier.

[0020] In some implementations of the methods and apparatus described herein, determining whether the SIB is transmitted on the second carrier may include: determining that the SIB is not transmitted on the second carrier when a second value is indicated in the information element.

[0021] In some implementations of the methods and apparatus described herein, the information element is a subcarrier offset field, which is included in the PBCH of the first SSB.

[0022] In a second aspect of the solution, the base station transmits first downlink control information (DCI) for paging to the user equipment in the first carrier. The first DCI may include a short message instructing the user equipment to acquire system information for the second carrier in the first carrier. Alternatively or additionally, the base station transmits a first synchronization signal and a Physical Broadcast Channel (PBCH) block (SSB) to the user equipment in the second carrier. The first SSB instructs the user equipment to determine, based on the first SSB, whether a System Information Block (SIB) is transmitted in the second carrier. In this way, a scheme for instructing the UE to acquire system information for the second carrier is designed.

[0023] In some implementations of the methods and apparatus described herein, a short message may include a bit field indicating at least one of the following: system information acquisition; or carrier switching.

[0024] In some implementations of the methods and apparatus described herein, the first DCI may include scheduling information of the system information of the second carrier, and the system information of the second carrier is scheduled by the scheduling information.

[0025] In some implementations of the methods and apparatus described herein, the first DCI may include an indication that scheduling information exists in the first DCI.

[0026] Some implementations of the methods and apparatus described herein may further include: transmitting a second DCI to a user equipment on a first carrier during a first timing associated with the scheduling of a system information block. The first timing follows a paging timing associated with the first DCI or follows a paging frame containing that paging timing.

[0027] Some implementations of the methods and apparatus described herein may further include: transmitting a second DCI to a user equipment within a first carrier within a time window that includes at least one timing associated with the scheduling of system information blocks. The time window follows either the paging timing associated with the first DCI or the paging frame containing that paging timing.

[0028] In some implementations of the methods and apparatus described herein, the second DCI is scrambled by a Radio Network Temporary Identifier (RNTI), which is different from the System Information RNTI (SI-RNTI), and the System Information is scheduled by scheduling information in the second DCI.

[0029] In some implementations of the methods and apparatus described herein, the second DCI is scrambled by SI-RNTI. Some implementations of the methods and apparatus described herein may also include: transmitting an SIB scheduled by the second DCI to the user equipment in the first carrier. The SIB may include an indication indicating whether system information of the second carrier or scheduling information of the system information of the second carrier is included in the SIB.

[0030] In some implementations of the methods and apparatus described herein, the second DCI is scrambled by SI-RNTI. Some implementations of the methods and apparatus described herein may also include: transmitting an SIB scheduled by the second DCI to the user equipment in the first carrier. The second DCI may include an indication indicating whether system information of the second carrier or scheduling information of the system information of the second carrier is included in the SIB.

[0031] In some implementations of the methods and apparatus described herein, the first SSB may include information elements regarding subcarrier offset parameters. A first value is indicated in the information element, indicating that the first SSB provides a valid configuration of the control resource set (CORESET) of the second carrier for a user equipment with first capabilities. The configuration of the CORESET of the second carrier is associated with the first SSB of the second carrier, and this configuration is used for the user equipment with first capabilities.

[0032] Some implementations of the methods and apparatus described herein may further include: transmitting a second SSB of the first carrier to the user equipment in the first carrier. A subcarrier offset is associated with an information element in the second SSB, the subcarrier offset being used for the frequency position of the CORESET of the second carrier.

[0033] In some implementations of the methods and apparatus described herein, a first value in the information element of the first SSB of the second carrier indicates that the SIB was not transmitted in the second carrier.

[0034] In some implementations of the methods and apparatus described herein, the first SSB may include information elements regarding subcarrier offset parameters, with a second value indicated in the information elements. The second value in the information elements of the first SSB of the second carrier indicates that the SIB was not transmitted in the second carrier.

[0035] In some implementations of the methods and apparatus described herein, the information element is a subcarrier offset field, which is included in the PBCH of the first SSB. Attached Figure Description

[0036] Figure 1A An example of a wireless communication system for obtaining support system information according to various aspects of this disclosure is illustrated.

[0037] Figure 1B An example of the reuse of SSB and CORESET#0 in FR1 according to some exemplary embodiments of the present disclosure is illustrated.

[0038] Figure 2A An example signaling diagram is illustrated for a communication process supporting the acquisition of system information according to some example embodiments of the present disclosure.

[0039] Figure 2B Another example signaling diagram illustrates a communication process for obtaining supporting system information according to some example embodiments of the present disclosure.

[0040] Figures 3A to 3B The illustration shows an example of obtaining scheduling information for system information of an ES carrier in a non-energy-saving (ES) carrier according to some example embodiments of the present disclosure.

[0041] Figures 4 to 5 An example of a device for obtaining support system information according to various aspects of this disclosure is illustrated.

[0042] Figures 6 to 7 An example of a processor for obtaining support system information according to various aspects of this disclosure is illustrated.

[0043] Figures 8 to 15 The diagram illustrates a flowchart of a method for obtaining support system information according to various aspects of this disclosure.

[0044] Throughout the accompanying drawings, the same or similar reference numerals denote the same or similar elements. Detailed Implementation

[0045] The principles of this disclosure will now be described with reference to some embodiments. It should be understood that these embodiments are described for illustrative purposes only and to assist those skilled in the art in understanding and implementing this disclosure, and do not imply any limitation on the scope of this disclosure. This disclosure described herein can be implemented in various ways other than those described below.

[0046] In the following description and claims, unless otherwise defined, all technical and scientific terms used herein have the same meaning as commonly understood by one of ordinary skill in the art to which this disclosure pertains.

[0047] References to "an embodiment," "example embodiment," "embodiment," "some embodiments," etc., in this disclosure indicate that the embodiments(s) described may include specific features, structures, or characteristics, but not every embodiment necessarily includes that specific feature, structure, or characteristic. Furthermore, such phrases do not necessarily refer to the same(s) embodiments(s). Additionally, when a specific feature, structure, or characteristic is described in connection with an embodiment, it is believed that in conjunction with other embodiments (whether explicitly described or not) affecting such feature, structure, or characteristic is within the knowledge of those skilled in the art.

[0048] It should be understood that although the terms “first” and “second”, etc., may be used herein to describe various elements, these elements should not be limited by these terms. These terms are used only to distinguish one element from another. For example, a first element may also be referred to as a second element without departing from the scope of the embodiments, and similarly, a second element may also be referred to as a first element. As used herein, the term “and / or” includes any and all combinations of one or more of the listed terms.

[0049] The terminology used herein is for the purpose of describing particular embodiments only and is not intended to limit the exemplary embodiments. Unless the context clearly indicates otherwise, the singular forms “a,” “an,” and “the” as used herein are also intended to include the plural forms. It should also be understood that the terms “comprising,” “including,” “having,” “having,” “containing,” and / or “comprising” as used herein specify the presence of the stated features, elements, and / or components, but do not exclude the presence or addition of one or more other features, elements, components, and / or combinations thereof. For example, the term “includes” and variations thereof should be understood as open terms meaning “including, but not limited to.” The term “based on” should be understood as “at least partially based on.” The terms “one embodiment” and “embodiment” should be understood as “at least one embodiment.” The term “another embodiment” should be understood as “at least one other embodiment.” The use of expressions such as “A and / or B” can mean “only A” or “only B” or “both A and B.” Other explicit or implicit definitions may be included below.

[0050] As used herein, the term "communication network" refers to a network that conforms to any suitable communication standard, such as 5G NR, LTE, LTE-A Advanced, Wideband Code Division Multiple Access (WCDMA), High-Speed ​​Packet Access (HSPA), Narrowband Internet of Things (NB-IoT), etc. Furthermore, communication between terminal devices and network devices in a communication network can be performed according to any suitable generation of communication protocols, including but not limited to first-generation (1G), second-generation (2G), 2.5G, 2.75G, third-generation (3G), fourth-generation (4G), 4.5G, fifth-generation (5G) communication protocols, and / or any other protocols currently known or to be developed in the future. Embodiments of this disclosure can be applied to various communication systems. Given the rapid development of communications, future types of communication technologies and systems will also exist, in which this disclosure can be embodied. This should not be construed as limiting the scope of this disclosure to the systems described above.

[0051] As used herein, the term "network device" generally refers to a node in a communication network through which terminal devices can access and receive services. Network devices can refer to base stations (BS) or access points (APs), such as Node B (NodeB or NB), Radio Access Network (RAN) nodes, Evolved Node B (eNodeB or eNB), NRNB (also known as gNB), Remote Radio Unit (RRU), Radio Header (RH), infrastructure equipment for V2X (vehicle-to-everything) communication, Transmitter Receiver Point (TRP), Receiver Point (RP), Remote Radio Header (RRH), relay, Integrated Access and Backhaul (IAB) nodes, and low-power nodes (such as femto-BS, pico-BS, etc.), depending on the terminology and technology applied.

[0052] As used herein, the term "terminal device" generally refers to any terminal device capable of wireless communication. By way of example and not limitation, a terminal device may also be referred to as a communication device, user equipment (UE), end user equipment, subscriber station (SS), unmanned aerial vehicle (UAV), portable subscriber station, mobile station (MS), or access terminal (AT). Terminal devices may include, but are not limited to, mobile phones, cellular phones, smartphones, Voice over IP (VoIP) phones, wireless local loop phones, tablets, wearable terminal devices, personal digital assistants (PDAs), portable computers, desktop computers, image capture terminal devices (such as digital cameras), gaming terminal devices, music storage and playback devices, in-vehicle wireless terminal devices, wireless endpoints, mobile stations, laptop embedded devices (LEEs), laptop-mounted devices (LMEs), USB dongles, smart devices, wireless customer premises equipment (CPEs), Internet of Things (IoT) devices, watches or other wearable devices, head-mounted displays (HMDs), vehicles, drones, medical devices (e.g., remote surgical equipment), industrial equipment (e.g., robots and / or other wireless devices operating in industrial and / or automated processing chain environments), consumer electronics devices, and devices operating on commercial and / or industrial wireless networks. In the following description, the terms "terminal device," "communication device," "terminal," "user equipment," and "UE" may be used interchangeably.

[0053] As used herein, the term "carrier" generally refers to a network frequency carrier in a low-frequency range (e.g., FR1) or a high-frequency range (e.g., FR2). Furthermore, "carrier" can be synonymous with "cell," and the two are used interchangeably.

[0054] As described above, during the initial NR access process, the SSB is used by the UE to obtain the Physical Cell ID, achieve DL synchronization, and acquire system information. The SSB consists of the Primary Synchronization Signal (PSS), the Secondary Synchronization Signal (SSS), and the Physical Broadcast Channel (PBCH). The Primary Information Block (MIB) is transmitted in the PBCH. The MIB carries the following configuration.

[0055] In the information provided in the MIB, ssb-SubcarrierOffset corresponds to parameter k. SSB This parameter indicates the frequency domain offset between the SSB and the entire resource block grid, in units of subcarriers. The value in the ssb-SubcarrierOffset field can be in the range [0, 15].

[0056] For FR2, k SSB The value can be determined via ssb-SubcarrierOffset in the MIB, and kSSB The value range can be 0≤ k SSB ≤15. For FR1, k SSB The range of values ​​for k can be extended by adding the most significant bit encoded within the PBCH. That is, k SSB The four least significant bits (LSBs) are indicated by ssb-SubcarrierOffset in the MIB, and k SSB One most significant bit (MSB) is carried in the physical layer payload of the PBCH. Therefore, for FR1, k SSB The value range can be 0≤ k SSB ≤31.

[0057] Additionally, the ssb-SubcarrierOffset field can indicate that CORESET#0 is not configured in the MIB. In this case, the pdcch-ConfigSIB1 field can indicate the frequency location where the UE (does not) find the synchronization signal and PBCH (SS / PBCH), which have a control resource set and search space set for SIB1, where SIB1 carries the remaining system information of the cell.

[0058] The field pdcch-ConfigSIB1 is used to configure CORESET#0, search space set #0, and necessary PDCCH parameters. If the field ssb-SubcarrierOffset indicates that CORESET#0 does not exist, then the field pdcch-ConfigSIB1 indicates either the frequency location where the UE can find an SS / PBCH block with CORESET=0, or the frequency range where the network does not provide an SS / PBCH block with CORESET#0.

[0059] CORESET#0 is used to house the PDCCH, which is used to schedule channels / signals transmitted during the initial access process, including, for example, SIB1, random access messages, paging, etc. The UE can then base its decisions on the determined k... SSB Determine if CORESET#0 exists.

[0060] As specified in 3GPP Technical Specification (TS) 38.213, for FR1, if k SSB If the range is [0, 23], then CORESET#0 exists; if k SSB If the range is [24, 31], then CORESET#0 does not exist. For FR2, if k SSB If the range is [0, 11], then CORESET#0 exists; if k SSBIf the range is [12,15], then CORESET#0 does not exist.

[0061] For FR1, 0≤ k SSB ≤23 or for FR2, 0≤ k SSB In the case of ≤11, SIB1 can be transmitted in the same initial bandwidth portion (BWP) in which the SSB is detected. From the UE's perspective, if the UE detects the SSB and determines that for FR1, 0≤ k SSB ≤23 or for FR2, 0≤ k SSB If the value is ≤11, the UE can determine that CORESET#0 exists. Then, the UE can obtain SIB1 for the cell based on the CORESET#0 configuration, the search space set #0 configuration, and other PDCCH parameters.

[0062] If the UE detects the first SSB and determines that for FR1... k SSB >23 or for FR2, k SSB If the value is greater than 11, then the UE can determine that CORESET#0 does not exist for the given search space. In this case, the UE can base its decision on k. SSB The associated offset is used to search for the synchronization raster.

[0063] For 24≤ based on the first SSB k SSB ≤29 (for FR1) or 12≤ k SSB For values ​​≤13 (for FR2), the UE can determine the information of the second SSB with CORESET#0. For example, the nearest (in the corresponding frequency direction) Global Synchronization Channel Number (GSCN) of the second SSB with CORESET#0 can be determined as... . It is the GSCN of the first SS / PBCH block, in FR1 (410MHz-7.125GHz) and FR2-1 (24.25GHz-52.6GHz). In FR2-2 (52.6GHz-71GHz), ,and The GSCN offsets are provided by Table 1-1 for FR1 and Table 1-2 for FR2. As shown in Tables 1-1 and 1-2, for FR1, k SSB =30 is retained, and for FR2, k SSB=14 is reserved. Table 1-1: For FR1, pdcch-ConfigSIB1 in k SSB The combination of controlResourceSetZero and searchSpaceZero with Mapping between Table 1-2: For FR2, in pdcch-ConfigSIB1 k SSB The combination of controlResourceSetZero and searchSpaceZero with Mapping between

[0064] If the UE detects a second SSB and the second SSB does not provide CORESET#0, the UE can ignore the GSCN information related to the SS / PBCH block location used to perform cell search.

[0065] If the UE detects the SSB and determines that for FR1, k SSB =31 or for FR2, k SSB =14, then the UE determines that CORESET#0 does not exist and is within the GSCN range. There is no SSB with an associated CORESET#0. and These are determined by `controlResourceSetZero` and `searchSpaceZero` in `pdcch-ConfigSIB1`, respectively. If the GSCN range is... If so, the UE determines that there is no information on the detected SSB for a second SSB with CORESET#0.

[0066] The above describes the process by which a UE obtains SIB1 based on the detected SSB during the initial access procedure in the 3GPP (3rd Generation Partnership Project). Next, the NR paging procedure in 3GPP will be described.

[0067] Paging allows the network to reach UEs in the RRC_IDLE or RRC_INACTIVE states via paging messages. Paging also allows the network to notify UEs in the RRC_IDLE, RRC_INACTIVE, and RRC_CONNECTED states of system information (SI) modifications, indications for Earthquake and Tsunami Warning Systems (ETWS), or indications for Commercial Mobile Alert Systems (CMAS) via short messages. Short messages are defined in Table 1-3 as follows. Table 1-3: Short Messages

[0068] Both paging messages and short messages are addressed using DCI format 1_0, which is identified by a Paging Radio Network Temporary Identifier (P-RNTI). DCI format 1_0 contains at least one of a short message indicator, a short message, and scheduling information for paging. The short message indicator can be used to indicate only a short message, only scheduling information for paging, or both a short message and scheduling information for paging carried in the DCI. The UE can interpret the bit fields of the short message indicator in the DCI, as defined in Table 1-4. Table 1-4: Short Message Indicators

[0069] As shown in Table 4, bit field 00 is reserved for future use. If scheduling information used only for paging exists in the Short Message Indicator (bit 01), then the bit field used for the Short Message Indicator is reserved. In other words, if both bits of the indicator are 01, the Short Message Indicator can indicate that the DCI is a normal DCI carrying control information to schedule the associated Physical Data Sharing Channel (PDSCH). The UE can receive the relevant paging message based on the scheduled PDSCH.

[0070] If only the short message exists in the short message indicator (bit 10), the bit field for scheduling information used for paging is reserved. In other words, if both bits of the indicator are 10, the short message indicator can indicate that the DCI is a specific DCI carrying a short message without an associated PDSCH. The UE can check the information carried in the corresponding short message in that specific DCI to perform relevant actions, which are defined in the table for short messages (i.e., Tables 1-3).

[0071] If both the paging scheduling information and the short message are present in the short message indicator (bit 11), then all information in the DCI is valid. In other words, if both bits of the indicator are 11, the short message indicator can indicate that the DCI carries both a short message and control information to schedule the associated PDSCH. The UE can check the information carried in the corresponding short message in the DCI to perform the relevant actions. The UE can also receive the relevant paging message based on the scheduled PDSCH.

[0072] For UEs in RRC_IDLE or RRC_INACTIVE states, the paging channel needs to be monitored during one paging opportunity (PO) in each Discontinuous Receive (DRX) cycle. For UEs in RRC_CONNECTED state, the paging channel is monitored in any PO signaled in the system information used for SI change indication and Common Warning System (PWS) notification. A DRX cycle can be configured to contain one or more paging frames (PF), and a paging frame can be configured to contain one or more POs. Each PO corresponds to a set of PDCCH monitoring opportunities, and each PDCCH monitoring opportunity is associated with a transmission beam.

[0073] RAN Plenary Meeting #98-e has reached an agreement on Network Energy Saving (NES) for NR. One objective is to have SIB1-less in a carrier (or cell) to achieve energy savings in the BS by not transmitting SIB1 on that carrier. From the UE's perspective, the UE can obtain system information for that carrier from another carrier. In the following description, the term "Network Energy Saving (NES)" may be used interchangeably with the term "Energy Saving (ES)". In the following description, the SIB1-less carrier may also be referred to as the ES carrier. The UE can obtain system information for the ES carrier / cell from other associated carriers / cells and synchronize from other associated carriers / cells, and / or from signals transmitted on the cell.

[0074] In view of the above, embodiments of this disclosure provide a solution for obtaining system information of an ES carrier from a non-ES carrier. In one aspect of this solution, a user equipment (UE) may receive a first DCI for paging in a first carrier (e.g., a non-ES carrier). The first DCI includes a short message. Based on the short message, the UE obtains system information of a second carrier in the first carrier. In this way, a scheme for on-demand system information acquisition is proposed, thereby reducing resource consumption in the transmission of system information. Furthermore, reusing the paging DCI for an instruction to obtain system information of another carrier is beneficial, for example, in terms of reducing signaling overhead and reducing UE implementation workload. In the following description, the terms "paging DCI" and "paging DCI" are used interchangeably.

[0075] Alternatively, the user equipment (UE) can receive a first SSB in the second carrier and, based on the first SSB, determine whether an SIB is being transmitted in the second carrier. In this way, the UE can determine whether the second carrier is a non-ES carrier or an ES carrier. If the second carrier is a non-ES carrier, the UE can obtain SIB1 based on the detected SSB as described above. If the second carrier is an ES carrier, and the UE is camped on the second carrier and detects an SSB, the UE can perform relevant actions to obtain the system information of the ES carrier in another carrier. In this way, ES-enabled UEs can be instructed to obtain the system information of the ES carrier in another carrier. Furthermore, it avoids ES-unsupported UEs detecting SIB1 in the ES carrier (since SIB1 is not provided), thereby avoiding unnecessary power consumption.

[0076] The aspects of this disclosure are described in the context of wireless communication systems.

[0077] Figure 1AAn example of a wireless communication system 100 for obtaining supporting system information according to various aspects of this disclosure is illustrated. The wireless communication system 100 may include one or more network entities 102 (also referred to as network devices (NEs)), one or more UEs 104, a core network 106, and a packet data network 108. The wireless communication system 100 may support various radio access technologies. In some implementations, the wireless communication system 100 may be a 4G network, such as an LTE network or an Advanced LTE (LTE-A) network. In some other implementations, the wireless communication system 100 may be a 5G network, such as an NR network. In other implementations, the wireless communication system 100 may be a combination of 4G and 5G networks, or other suitable radio access technologies, including IEEE 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), and IEEE 802.20. The wireless communication system 100 may support radio access technologies beyond 5G. Additionally, the wireless communication system 100 may support technologies such as Time Division Multiple Access (TDMA), Frequency Division Multiple Access (FDMA), or Code Division Multiple Access (CDMA).

[0078] One or more network entities 102 may be distributed throughout a geographic area to form a wireless communication system 100. One or more network entities among the network entities 102 described herein may be, include, or may be referred to as network nodes, base stations, network elements, radio access networks (RANs), base transceiver stations, access points, NodeBs, eNodeBs (eNBs), next-generation NodeBs (gNBs), or other suitable terms. Network entities 102 and UE 104 may communicate via communication link 110, which may be a wireless or wired connection. For example, network entities 102 and UE 104 may perform wireless communication (e.g., receive signaling, send signaling) via a Uu interface.

[0079] Network entity 102 may provide a geographic coverage area 112 for which network entity 102 may support services (e.g., voice, video, packet data, messaging, broadcasting, etc.) for one or more UEs 104 within the geographic coverage area 112. For example, network entity 102 and UE 104 may support wireless communication of signals associated with services (e.g., voice, video, packet data, messaging, broadcasting, etc.) based on one or more wireless access technologies. In some implementations, network entity 102 may be mobile, for example, a satellite associated with a non-terrestrial network. In some implementations, different geographic coverage areas 112 associated with the same or different radio access technologies may overlap, but different geographic coverage areas 112 may be associated with different network entities 102. The information and signals described herein may be represented using any of a variety of different technologies and techniques. For example, data, instructions, commands, information, signals, bits, symbols, and chips that may be referenced throughout the description may be represented by voltage, current, electromagnetic waves, magnetic fields or particles, light fields or particles, or any combination thereof.

[0080] One or more UEs 104 may be distributed throughout the geographic area of ​​the wireless communication system 100. UE 104 may include or be referred to as a mobile device, wireless device, remote device, remote unit, handheld device, or subscriber device, or some other suitable term. In some implementations, UE 104 may be referred to as a unit, station, terminal, or client, etc. Alternatively or additionally, UE 104 may be referred to as an Internet of Things (IoT) device, an Internet of Everything (IoE) device, or a Machine Type Communication (MTC) device, etc. In some implementations, UE 104 may be stationary within the wireless communication system 100. In some other implementations, UE 104 may be mobile within the wireless communication system 100.

[0081] One or more UEs 104 can be devices of different forms or with different capabilities. Some examples of UEs 104 are shown in... Figure 1A The diagram shows that UE 104 can communicate with various types of devices, such as network entity 102, other UEs 104, or network devices (e.g., core network 106, packet data network 108, relay equipment, integrated access and backhaul (IAB) node, or another network device). Figure 1A As shown. Alternatively or concurrently, UE 104 may support communication with other network entities 102 or UE 104, which may act as a relay in the wireless communication system 100.

[0082] UE 104 can also support direct wireless communication with other UE 104s via communication link 114. For example, UE 104 can support direct wireless communication with another UE 104 via a device-to-device (D2D) communication link. In some implementations, such as vehicle-to-vehicle (V2V) deployments, vehicle-to-everything (V2X) deployments, or cellular V2X deployments, communication link 114 may be referred to as a sidelink. For example, UE 104 can support direct wireless communication with another UE 104 via a PC5 interface.

[0083] Network entity 102 may support communication with core network 106, or with another network entity 102, or both. For example, network entity 102 may interface with core network 106 via one or more backhaul links 116 (e.g., via S1, N2, N2, or another network interface). Network entities 102 may communicate with each other via backhaul links 116 (e.g., via X2, Xn, or another network interface). In some implementations, network entities 102 may communicate directly with each other (e.g., between network entities 102). In some other implementations, network entities 102 may communicate with each other or indirectly (e.g., via core network 106). In some implementations, one or more network entities 102 may include sub-components, such as access network entities, which may be examples of access node controllers (ANCs). The ANC may communicate with one or more UEs 104 via one or more other access network transport entities (which may be referred to as radio heads, smart radio heads, or transmit-receive points (TRPs)).

[0084] In some implementations, network entity 102 can be configured with a decomposed architecture that can utilize protocol stacks physically or logically distributed across two or more network entities 102, such as an Integrated Access Backhaul (IAB) network, an Open RAN (O-RAN) (e.g., a network configuration sponsored by the O-RAN Alliance), or a Virtualized RAN (vRAN) (e.g., a Cloud RAN (C-RAN)). For example, network entity 102 may include one or more of the following: a Central Unit (CU), a Distributed Unit (DU), a Radio Unit (RU), a RAN Intelligent Controller (RIC) (e.g., a near-real-time RIC, a non-real-time RIC), a Service Management and Orchestration (SMO) system, or any combination thereof.

[0085] An RU can also be referred to as a radio head, intelligent radio head, remote radio head (RRH), remote radio unit (RRU), or transmit-receive point (TRP). One or more components of network entity 102 in the decomposed RAN architecture can be co-located, or one or more components of network entity 102 can be located in distributed locations (e.g., separate physical locations). In some implementations, one or more network entities 102 in the decomposed RAN architecture can be implemented as virtual units (e.g., virtual CU (VCU), virtual DU (VDU), virtual RU (VRU)).

[0086] The functional splitting among CU, DU, and RU can be flexible and can support different functions depending on which functions are performed at the CU, DU, or RU (e.g., network layer functions, protocol layer functions, baseband functions, radio frequency functions, and any combination thereof). For example, protocol stack functional splitting can be adopted between CU and DU, allowing the CU to support one or more layers of the protocol stack, and the DU to support one or more different layers of the protocol stack. In some implementations, the CU can host upper-layer protocol layer (e.g., Layer 3 (L3), Layer 2 (L2)) functions and signaling (e.g., Radio Resource Control (RRC), Serving Data Adaptation Protocol (SDAP), Packet Data Convergence Protocol (PDCP)). The CU can be connected to one or more DUs or RUs, and one or more DUs or RUs can host lower-layer protocol layer functions and signaling, such as Layer 1 (L1) (e.g., Physical (PHY) layer) or L2 (e.g., Radio Link Control (RLC) layer, Media Access Control (MAC) layer), and each can be at least partially controlled by the CU 160.

[0087] Alternatively or concurrently, functional splitting of the protocol stack can be employed between the DU and RU, such that the DU can support one or more layers of the protocol stack, and the RU can support one or more different layers of the protocol stack. The DU can support one or more different cells (e.g., via one or more RUs). In some implementations, functional splitting between the CU and DU, or between the DU and RU, can be within the protocol layer (e.g., some functions for the protocol layer can be performed by one of the CU, DU, or RU, while other functions of the protocol layer are performed by a different one of the CU, DU, or RU).

[0088] The CU can be further functionally divided into CU control plane (CU-CP) and CU user plane (CU-UP) functions. The CU can be connected to one or more DUs via midhaul communication links (e.g., F1, F1-c, F1-u), and the DUs can be connected to one or more RUs via fronthaul communication links (e.g., open fronthaul (FH) interfaces). In some implementations, the midhaul or fronthaul communication links can be implemented based on interfaces (e.g., channels) between layers of a protocol stack supported by corresponding network entities 102 communicating via such communication links.

[0089] Core network 106 can support user authentication, access authorization, tracking, connectivity, and other access, routing, or mobility functions. Core network 106 can be an evolved packet core (EPC) or a 5G core (5GC), which may include control plane entities that manage access and mobility (e.g., a mobility management entity (MME), access and mobility management functions (AMF)) and user plane entities that route packets or interconnects to external networks (e.g., a serving gateway (S-GW), a packet data network (PDN) gateway (P-GW), or a user plane function (UPF)). In some implementations, the control plane entities may manage non-access stratum (NAS) functions, such as mobility, authentication, and bearer management (e.g., data bearers, signaling bearers, etc.) for one or more UEs 104 served by one or more network entities 102 associated with core network 106.

[0090] Core network 106 can communicate with packet data network 108 via one or more backhaul links 116 (e.g., via S1, N2, N2, or another network interface). Packet data network 108 may include application server 118. In some implementations, one or more UEs 104 may communicate with application server 118. UE 104 may establish a session with core network 106 (e.g., Protocol Data Unit (PDU) session, etc.) via network entity 102. Core network 106 can use the established session (e.g., established PDU session) to route services (e.g., control information, data, etc.) between UE 104 and application server 118. A PDU session may be an example of a logical connection between UE 104 and core network 106 (e.g., one or more network functions of core network 106).

[0091] In the wireless communication system 100, network entity 102 and UE 104 can use the resources of the wireless communication system 100 (e.g., time resources (e.g., symbols, time slots, subframes, frames, etc.) or frequency resources (e.g., subcarriers, carriers)) to perform various operations (e.g., wireless communication). In some implementations, network entity 102 and UE 104 can support different resource structures. For example, network entity 102 and UE 104 can support different frame structures. In some implementations, such as in 4G, network entity 102 and UE 104 can support a single frame structure. In some other implementations, such as in 5G and other suitable radio access technologies, network entity 102 and UE 104 can support various frame structures (i.e., multiple frame structures). Network entity 102 and UE 104 can support various frame structures based on one or more parameter sets.

[0092] One or more parameter sets may be supported in the wireless communication system 100, and the parameter sets may include subcarrier spacing and cyclic prefixes. A first parameter set (e.g., μ=0) may be associated with a first subcarrier spacing (e.g., 15kHz) and a normal cyclic prefix. In some implementations, the first parameter set (e.g., μ=0) associated with the first subcarrier spacing (e.g., 15kHz) may utilize one time slot per subframe. A second parameter set (e.g., μ=1) may be associated with a second subcarrier spacing (e.g., 30kHz) and a normal cyclic prefix. A third parameter set (e.g., μ=2) may be associated with a third subcarrier spacing (e.g., 60kHz) and a normal cyclic prefix or an extended cyclic prefix. A fourth parameter set (e.g., μ=3) may be associated with a fourth subcarrier spacing (e.g., 120kHz) and a normal cyclic prefix. A fifth parameter set (e.g., μ=4) may be associated with a fifth subcarrier spacing (e.g., 240kHz) and a normal cyclic prefix.

[0093] The time intervals of resources (e.g., communication resources) can be organized according to frames (also known as radio frames). Each frame can have a duration, for example, 10 milliseconds (ms). In some implementations, each frame can include multiple subframes. For example, each frame can include 10 subframes, and each subframe can have a duration, for example, 1 ms. In some implementations, each frame can have the same duration. In some implementations, each subframe of a frame can have the same duration.

[0094] Alternatively or concurrently, the time intervals of resources (e.g., communication resources) can be organized according to time slots. For example, a subframe may include a certain number (e.g., quantity) of time slots. The number of time slots in each subframe may also depend on one or more parameter sets supported in the wireless communication system 100. For example, a first parameter set, a second parameter set, a third parameter set, a fourth parameter set, and a fifth parameter set (i.e., μ=0, μ=1, μ=2, μ=3, μ=4) associated with corresponding subcarrier intervals of 15 kHz, 30 kHz, 60 kHz, 120 kHz, and 240 kHz may utilize one time slot per subframe, two time slots per subframe, four time slots per subframe, eight time slots per subframe, and 16 time slots per subframe, respectively. Each time slot may include a certain number (e.g., quantity) of symbols (e.g., OFDM symbols). In some implementations, the number (e.g., quantity) of time slots used for a subframe may depend on the parameter set. For a normal cyclic prefix, a time slot may include 14 symbols. For an extended cyclic prefix (e.g., applicable to a 60 kHz subcarrier spacing), a time slot may include 12 symbols. The relationship between the number of symbols per time slot, the number of time slots per subframe, and the number of time slots per frame for both regular and extended cyclic prefixes can depend on the parameter set. It should be understood that references to the first parameter set (e.g., μ=0) associated with the first subcarrier spacing (e.g., 15 kHz) can be used interchangeably between subframes and time slots.

[0095] In the wireless communication system 100, the electromagnetic (EM) spectrum can be divided into various categories, frequency bands, frequency channels, etc., based on frequency or wavelength. For example, the wireless communication system 100 can support one or more operating frequency bands, such as frequency range names FR1 (410MHz-7.125GHz), FR2 (24.25GHz-52.6GHz), FR3 (7.125GHz-24.25GHz), FR4 (52.6GHz-114.25GHz), FR4a or FR4-1 (52.6GHz-71GHz), and FR5 (114.25GHz-300GHz). In some implementations, network entity 102 and UE 104 can perform wireless communication on one or more operating frequency bands. In some implementations, FR1 can be used by network entity 102 and UE 104, as well as other devices or apparatuses, for cellular communication services (e.g., control information, data). In some implementations, FR2 can be used by network entity 102 and UE 104, as well as other devices or apparatuses, for short-range, high-data-rate capabilities.

[0096] FR1 can be associated with one or more parameter sets (e.g., at least three parameter sets). For example, FR1 can be associated with: a first parameter set (e.g., μ=0) which includes a subcarrier spacing of 15 kHz; a second parameter set (e.g., μ=1) which includes a subcarrier spacing of 30 kHz; and a third parameter set (e.g., μ=2) which includes a subcarrier spacing of 60 kHz. FR2 can be associated with one or more parameter sets (e.g., at least two parameter sets). For example, FR2 can be associated with: a third parameter set (e.g., μ=2) which includes a subcarrier spacing of 60 kHz; and a fourth parameter set (e.g., μ=3) which includes a subcarrier spacing of 120 kHz.

[0097] Figure 1B The illustration shows an example of the reuse of SSB and CORESET#0 in FR1 according to some exemplary embodiments of this disclosure. For example... Figure 1B As shown, the SSB bandwidth comprises 20 RBs with a subcarrier spacing of 15 kHz. Based on the SSB, k SSB The value can be set to 15, indicating the frequency domain offset between the SSB and the entire resource block grid, in units of subcarriers. Therefore, a UE that detects an SSB can determine that CORESET#0 exists. The configuration of CORESET#0 can be determined based on the SSB. The UE can then obtain SIB1 for the cell based on the CORESET#0 configuration, the search space set #0 configuration, and other PDCCH parameters.

[0098] Now for reference Figure 2A The illustration shows an example signaling diagram of a communication process 200A supporting the acquisition of system information according to some example embodiments of the present disclosure. For discussion purposes, process 200A will be referred to... Figure 1A The process 200A can involve UE 104 and network entity (also referred to as BS) 102. It should be understood that... Figure 2A The steps and their order are for illustrative purposes only and are not intended to be limiting. It should be understood that process 200A may also include additional boxes not shown and / or omit some shown boxes, and the scope of this disclosure is not limited in this respect. Embodiments of this disclosure focus on the operation of UEs supporting ES. In the following embodiments, unless explicitly indicated, UE 104 refers to an ES-supporting UE.

[0099] like Figure 2AAs shown, BS 102 transmits 202 a first DCI 204 for paging on the first carrier. The first DCI 204 includes a short message instructing the UE to obtain system information for the second carrier on the first carrier. UE 104 receives 206 the first DCI 204 on the first carrier. Based on the short message, UE 104 obtains 208 the system information for the second carrier on the first carrier. In this way, a scheme for on-demand system information acquisition is proposed, thereby reducing resource consumption in the transmission of system information.

[0100] In the example implementation, a UE that supports ES and resides on a first carrier (e.g., a non-ES carrier) can be instructed to obtain system information for a second carrier (e.g., an ES carrier). Short messages in the DCI used for paging can be reused for this instruction. On-demand system information acquisition requires the BS to send system information for the ES carrier only when needed, which helps reduce overhead. Furthermore, reusing the DCI used for paging for obtaining system information for another carrier (e.g., an ES carrier) is beneficial in terms of, for example, reducing signaling overhead and reducing UE implementation workload.

[0101] In some example embodiments, the short message in the first DCI 204 may include a bit field indicating system information acquisition. In other words, the short message may instruct the UE to acquire system information for another carrier (e.g., an ES carrier). As an example implementation, after receiving the short message, the UE can acquire the system information for the configured ES carrier and can switch to the ES carrier.

[0102] Alternatively or additionally, the bit fields in the short message in the first DCI 204 can indicate carrier handover. In other words, the short message can explicitly instruct the UE to perform carrier handover. As an example implementation, the UE can obtain system information of the configured ES carrier based on this message and switch to the ES carrier.

[0103] As mentioned above, Figure 2A The order of steps described is for illustrative purposes only and is not intended to limit the scope. For example, obtaining step 208 may be performed before receiving step 206. For example, a short message may explicitly instruct the UE to perform a carrier handover. If the UE has already obtained the system information for the ES carrier before receiving the short message on a non-ES carrier, in which case the UE only needs to switch to the ES carrier based on that short message.

[0104] In some example embodiments, after receiving the first DCI 204, the UE 104 can switch from the first carrier to the second carrier. The UE 104 can then receive the first SSB of the second carrier from the BS 102 in the second carrier. In this way, based on the system information of the second carrier obtained in the first carrier and the SSB of the second carrier received in the second carrier, the UE 104 can communicate with the BS 102 in the second carrier. In this way, a scheme for instructing the UE to perform a carrier handover is designed. For the carrier handover instruction, reusing the short message in the DCI used for paging is beneficial in, for example, reducing signaling overhead and reducing the workload of UE implementation.

[0105] In some example implementations, the bits currently reserved in the short message can be used to instruct ES-enabled UEs to acquire system information about the ES carrier and / or perform carrier handover. This ensures no impact on UEs that do not support ES (also known as legacy UEs). An example implementation of a short message according to some embodiments of this disclosure is given in Table 2-1, wherein the new parameter SystemIofoRetrieving-ES is defined in the short message and indicated by the fifth bit in the short message (which is reserved for legacy UEs). Table 2-1: Short Messages

[0106] As shown in Table 2-1, if SystemIofoRetrieving-ES is set to 1, it indicates that a UE supporting ES is authorized to acquire system information about the ES carrier. In other words, for a UE supporting ES, upon receiving a short message with SystemIofoRetrieving-ES set to 1, the UE will acquire system information about the ES carrier in its currently camped carrier and can perform carrier handover to the ES carrier. UEs that do not support ES will omit this indication in the short message.

[0107] As proposed, when a short message is received for system information acquisition or carrier handover, the UE can acquire the system information of the ES carrier in a non-ES carrier, and the system information acquisition or carrier handover is performed in the DCI for paging in the non-ES carrier. Embodiments of specific aspects of how to instruct the UE to acquire the system information of the ES carrier and / or perform carrier handover are described. Another specific aspect of this disclosure is how to acquire the system information of the ES carrier.

[0108] In some example embodiments, the first DCI 204 may include scheduling information for the system information of the second carrier, and the system information of the second carrier may be scheduled by the scheduling information. In one embodiment, the first DCI 204 may include an indication that the scheduling information exists in the first DCI 204.

[0109] For example, the DCI used for paging can carry scheduling information for the PDSCH, which is used for system information of the ES carrier. The idea is to configure the short message indicator in the paging DCI to "00" (this indicator is temporarily reserved, as shown in Tables 1-4), indicating the presence of both scheduling information and short messages in the DCI. Here, the scheduling information is used to schedule paging messages, while the PDSCH carrying ES carrier system information is used to schedule ES-enabled UEs. Examples of short message indicators according to some embodiments of this disclosure are shown in Table 2-2. Table 2-2: Short Message Indicators

[0110] When the Short Message Indicator (SCI) is configured to "00" and the Short Message is configured to indicate system information acquisition (e.g., the fifth bit of the Short Message in Table 2-1 is configured to "1") or carrier switching, ES-enabled UEs will interpret the DCI as a PDSCH used to schedule system information carrying the ES carrier. The UE can detect the scheduled PDSCH, acquire the system information for the ES carrier, and then switch to the ES carrier. For ES-unsupported UEs, the UE can ignore the DCI, which has bit fields in the Short Message Indicator setting set to "00". This DCI is reserved for legacy UEs, as shown in Table 1-4. Using the reserved bits for indication will not have a significant impact on the behavior of ES-unsupported UEs.

[0111] In some example embodiments, the scheduling information for the system information of the second carrier can be sent in a separate message following the first DCI 204 used for paging. For example, the DCI for scheduling the PDSCH, which carries the system information of the ES carrier, can be received at a predefined timing or within a predefined time window after the UE receives the short message in the PO. From the BS's perspective, the system information of the ES carrier can be sent only at such corresponding timings. This reduces the overhead of system information configuration.

[0112] In an example embodiment, UE 104 may receive a second DCI (e.g., SIB1 DCI) from BS 102 on a first carrier during a first timing associated with the scheduling of a system information block. The first timing may be after a PO associated with the first DCI 204 or after a PF containing that PO. For example, UE 104 may receive the SIB1 DCI from BS 102 on a non-ES carrier during a first SIB1 scheduling timing after a PO associated with the paging DCI 204, or during a first SIP1 scheduling timing after a PF containing that PO, with UE 104 camped on that non-ES carrier. In other words, the SIB1 DCI for scheduling a PDSCH carrying system information for an ES carrier may be received during an SIB1 scheduling timing, which is after the last symbol of a PO with a short message, or after the last symbol of the last PO of the corresponding PF.

[0113] Figure 3A The illustration shows an example of obtaining scheduling information for system information on an ES carrier in a non-ES carrier according to some exemplary embodiments of the present disclosure. For discussion purposes, Figure 3A Reference Figure 1A and Figure 2A It can be described and may involve UE 104 and BS 102.

[0114] like Figure 3A As shown, the network can use four beams for transmitting SIB1 (and for transmitting SIB1 DCI) and for paging (including transmitting paging DCI and paging messages). Figure 3A As shown, each beam is illustrated with a specific filling pattern. UE 104 can camp on a non-ES carrier. BS 102 can determine to switch the UE 104's camping carrier to the ES carrier. Therefore, BS 102 can send a short message in the paging DCI of beam #2 in PO#j on a non-ES carrier, instructing the UE to obtain system information for the ES carrier. Then, in the first SIB1 scheduling timing after PO, UE 104 can monitor the SIB1 DCI for scheduling the PDSCH carrying the system information for the ES carrier. After receiving the SIB1 DCI for scheduling the PDSCH, UE 104 can receive the PDSCH carrying the system information for the ES carrier based on the scheduling information in the SIB1 DCI.

[0115] In another example embodiment, UE 104 may receive a second DCI (e.g., SIB1 DCI) from BS 102 within a first carrier within a time window that includes at least one timing associated with the scheduling of system information blocks. The time window may be after a PO associated with the first DCI 204 or after a PF containing that PO. In other words, the SIB1 DCI used to schedule the PDSCH may be received within a predefined time window after the last symbol of a PO carrying system information for the ES carrier, or within a predefined time window after the last symbol of the PO of the associated PF. The size of the time window may be configured or predefined.

[0116] Figure 3B The illustration shows an example of obtaining scheduling information for system information on an ES carrier in a non-ES carrier according to some exemplary embodiments of the present disclosure. For discussion purposes, Figure 3B Reference Figure 1A and Figure 2A It can be described and may involve UE 104 and BS 102.

[0117] like Figure 3B As shown, the network can use four beams for transmitting SIB1 (and for transmitting SIB1 DCI) and for paging (including transmitting paging DCI and paging messages). Figure 3B As shown, each beam is illustrated with a specific filling pattern. UE 104 can camp on a non-ES carrier. BS 102 can determine whether to switch the UE 104's camping carrier to an ES carrier. Therefore, BS 102 can send a short message in the paging DCI of beam #2 in PO#j on a non-ES carrier, instructing the UE to obtain system information for the ES carrier. Then, within a predefined / configured time window after PO, UE 104 can monitor SIB1 DCI for scheduling a PDSCH carrying the system information for the ES carrier. After receiving the SIB1 DCI for scheduling the PDSCH, UE 104 can receive the PDSCH carrying the system information for the ES carrier based on the scheduling information in the SIB1 DCI.

[0118] Back Figure 2AIn some embodiments, the second DCI can be scrambled by a Radio Network Temporary Identity (RNTI), which is different from the System Information RNTI (SI-RNTI). The system information can be scheduled by scheduling information in the second DCI. In other words, the DCI used for scheduling the PDSCH can be scrambled by a specific RNTI that carries the system information of the ES carrier. In this case, the PDSCH is transmitted separately (separately from the PDSCH of SIB1 used for non-ES carriers).

[0119] In some embodiments, the second DCI may be scrambled by SI-RNTI. UE 104 may receive the SIB scheduled by the second DCI from BS 102 in the first carrier. In addition to the system information of the first carrier, the SIB may also include the system information of the second carrier or the scheduling information of the second carrier's system information. The SIB may include an indication indicating whether the system information of the second carrier or the scheduling information of the second carrier's system information is included in the SIB. For example, a bit field may exist in SIB1, based on which the UE can know whether the system information of the ES carrier or the scheduling information of the ES carrier's system information is included in SIB1 of the non-ES carrier. In one implementation, if the bit field is set to "0", UE 104 can determine that the system information of the ES carrier is included in SIB1 of the non-ES carrier. If the bit field is set to "1", UE 104 can determine that the scheduling information for the system information of the ES carrier is included in SIB1 of the non-ES carrier. UE 104 may also detect the PDSCH for the system information of the ES carrier based on the scheduling information. In this way, the size of SIB1 can be limited, thus avoiding impacting the SIB1 PDSCH detection performance in non-ES carriers.

[0120] In some embodiments, the second DCI may be scrambled by SI-RNTI. UE 104 may receive the SIB scheduled by the second DCI from BS 102 in the first carrier. In addition to the system information of the first carrier, the SIB may also include the system information of the second carrier or the scheduling information of the second carrier's system information. The second DCI may include an indication indicating whether the system information of the second carrier or the scheduling information of the second carrier's system information is included in the SIB. For example, the second DCI may contain a bit field based on which the UE can determine whether the system information of the ES carrier or the scheduling information of the ES carrier's system information is included in the SIB1 of the camped non-ES carrier. In the implementation, if the bit field is set to "0", UE 104 can determine that the system information of the ES carrier is included in the SIB1 of the non-ES carrier. If the bit field is set to "1", UE 104 can determine that the scheduling information for the system information of the ES carrier is included in the SIB1 of the non-ES carrier. UE 104 may also detect the PDSCH for the system information of the ES carrier based on the scheduling information. In this way, the size of SIB1 can be limited, thus avoiding impacting the SIB1 PDSCH detection performance in non-ES carriers.

[0121] One specific aspect of system information acquisition is how the UE obtains the CORESET#0 and search space set#0 configuration of the ES carrier. When the UE camps on the ES carrier (e.g., based on the BS configuration as described above), or when the UE camps on a carrier without gNB indication, the UE needs to detect the SSB of the ES carrier to synchronize with the DL, obtain the cell ID, and obtain available information in the MIB. Subsequently, the SSB(s) transmitted on the ES carrier are defined as the ES-SSB(s).

[0122] To avoid impacting the behavior of UEs that do not support ES (i.e., legacy UEs), the ES-SSB(s) in the ES carrier should be SSBs that do not provide a valid CORESET#0 configuration for these legacy UEs. Otherwise, UEs that do not support ES may continuously detect SIB1 (which is not provided) in the ES carrier, resulting in unnecessary power consumption. For UEs that support ES, it is proposed that the ES-SSB(s) may or may not provide a CORESET#0 configuration based on different embodiments of this disclosure. Various solutions can be proposed to enable the UE to obtain the CORESET#0 and search space set #0 configuration of the ES carrier. Some embodiments may be based on k SSB Designed according to the configuration.

[0123] In some example embodiments, the first SSB may include information elements regarding subcarrier offset parameters. In some examples, the information element may be a subcarrier offset field included in the PBCH of the first SSB. If a first value is indicated in the information element, UE 104 may determine the configuration of the control resource set (CORESET) of the second carrier based on the first SSB of the second carrier. The first value in the information element may indicate that the first SSB provides a valid configuration of the CORESET of the second carrier for a UE with a first capability. Alternatively or additionally, the first value in the information element may indicate that the SIB may not be transmitted in the second carrier.

[0124] In some implementations, UE 104 may receive a second SSB of the first carrier from BS 102 within the first carrier. UE 104 may determine a subcarrier offset based on information elements in the second SSB, which is used for the frequency position of the CORESET of the second carrier.

[0125] For example, for (multiple) ES-SSBs, k SSB It can be configured to 30 for FR1 and 14 for FR2. In this case, for UEs that do not support ES, as specified (and refer to Table 1-1), this type of k SSB The value is a reserved value and it only indicates the UE; the SSB does not provide configuration for CORESET#0.

[0126] For UEs that support ES, the UE can interpret such an SSB as an ES-SSB and provide a CORESET#0 configuration. CORESET#0 exists within the ES carrier. This interpretation can be based on the configuration in the ES-SSB's MIB, such as dmrs-TypeA-Position or spare bits or other information fields. In this case, the subcarrier offset used to determine the CORESET#0 position should be provided in the system information obtained from the associated non-ES carrier.

[0127] In some example embodiments, the first SSB may include information elements regarding subcarrier offset parameters. In some examples, the information element may be a subcarrier offset field included in the PBCH of the first SSB. If a second value is indicated in the information element, the UE 104 can determine the first carrier based on the first SSB. The UE can determine the configuration of the CORESET of the second carrier and the system information of the second carrier in the first carrier. The second value in the information element may indicate that the SIB may not be transmitted in the second carrier.

[0128] For example, for (multiple) ES-SSBs, k SSBIt can be configured within [24, 29] for FR1 and within [12, 13] for FR2. In this case, for UEs that do not support ES, as specified, this type of k SSB The value indicates that CORESET#0 does not exist, and the UE can find the SSB that provides the CORESET#0 configuration based on PDCCH-configSIB1 in the MIB.

[0129] For UEs that support ES, the UE can interpret such an SSB as an ES-SSB. This interpretation can be based on the configuration in the MIB of the SSB, such as dmrs-TypeA-Position or spare bits or other information fields. CORESET#0 exists, but an ES-SSB does not provide a CORESET=0 configuration. Instead, the UE can find the SSB that provides the CORESET#0 configuration and system information for the ES carrier in the SSB of the carrier based on PDCCH-configSIB1 in the MIB.

[0130] Specifically, if the UE 104 that supports ES is determined to be for FR1, 24≤ k SSB ≤29 or for FR2, 12≤ k SSB If the value is ≤13, then UE 104 can determine that CORESET#0 exists, but the configuration of CORESET#0 is not provided by ES-SIB1. The UE can determine the nearest GSCN (in the corresponding frequency direction) of the second SSB as... . It is the GSCN of the first SS / PBCH block, in FR1 and FR2-1. In FR2-2, ,and The GSCN offset is provided by Table 1-1 for FR1 and Table 1-2 for FR2. UE 104 can obtain the CORESET#0 configuration and symbol information in the carrier through the second SSB.

[0131] Figure 2B Another example signaling diagram is illustrated for a communication process 200B supporting the acquisition of system information according to some example embodiments of the present disclosure. For discussion purposes, process 200B will be referred to... Figure 1A Described. Procedure 200B may involve UE 104 and BS 102. It should be understood that... Figure 2BThe steps and their order are for illustrative purposes only and are not intended to be limiting. It should be understood that process 200B may also include additional boxes not shown and / or omit some shown boxes, and the scope of this disclosure is not limited in this respect. Embodiments of this disclosure focus on the operation of UEs supporting ES. In the following embodiments, unless explicitly stated otherwise, UE 104 refers to an UE supporting ES.

[0132] like Figure 2B As shown, BS 102 transmits 212 first SSB 214 in the second carrier. UE 104 receives 216 first SSB 214 in the second carrier. Then, based on the first SSB 214, UE 104 determines whether 218 SIB can be transmitted in the second carrier. In this way, UE 104 can know whether the second carrier is an ES carrier or a non-ES carrier. If the second carrier is a non-ES carrier, the UE can obtain SIB1 based on the detected SSB as described above. If the second carrier is an ES carrier, and the UE camps on the second carrier and detects that the SSB supports ES, the UE can perform the relevant actions to obtain the system information of the ES carrier in another carrier. In other words, an ES-enabled UE can be instructed to obtain the system information of the ES carrier in another carrier.

[0133] A specific aspect of system information acquisition is how the UE obtains the CORESET#0 and search space set #0 configuration of the ES carrier. As mentioned above, in order not to affect the behavior of UEs that do not support ES (i.e., legacy UEs), the ES-SSB(s) in the ES carrier should be SSBs that do not provide a valid CORESET#0 configuration for these legacy UEs. Otherwise, UEs that do not support ES may continuously detect SIB1 (which is not provided) in the ES carrier, thus leading to unnecessary power consumption. For UEs that support ES, it is proposed that the ES-SSB(s) may or may not provide a CORESET#0 configuration based on different embodiments of this disclosure. Various solutions can be proposed to enable the UE to obtain the CORESET#0 and search space set #0 configuration of the ES carrier. Some embodiments may be based on k SSB Designed according to the configuration.

[0134] In some example embodiments, the first SSB 214 may include information elements regarding subcarrier offset parameters. In some examples, the information element may be a subcarrier offset field included in the PBCH of the first SSB 214. If a first value is indicated in the information element, the UE 104 may determine the configuration of the control resource set (CORESET) of the second carrier based on the first SSB 214 of the second carrier. The first value in the information element may indicate that the first SSB 214 provides a valid configuration of the CORESET of the second carrier for a UE with a first capability. Alternatively or additionally, the first value in the information element may indicate that the SIB may not be transmitted on the second carrier.

[0135] In some implementations, UE 104 may receive a second SSB of the first carrier from BS 102 within the first carrier. UE 104 may determine a subcarrier offset based on information elements in the second SSB, which is used for the frequency position of the CORESET of the second carrier.

[0136] For example, for (multiple) ES-SSBs, k SSB It can be configured to 30 for FR1 and 14 for FR2. In this case, for UEs that do not support ES, as specified (and refer to Table 1-1), this type of k SSB The value is a reserved value and it only indicates the UE; the SSB does not provide configuration for CORESET#0.

[0137] For UEs that support ES, the UE can interpret this type of SSB as an ES-SSB and provide a CORESET#0 configuration. CORESET#0 exists within the ES carrier. This interpretation can be based on the configuration in the ES-SSB's MIB, such as dmrs-TypeA-Position or spare bits or other information fields. In this case, the subcarrier offset used to determine the CORESET#0 position should be provided in the associated non-ES carrier.

[0138] In some example embodiments, the first SSB 214 may include information elements regarding subcarrier offset parameters. In some examples, the information element may be a subcarrier offset field included in the PBCH of the first SSB 214. If a second value is indicated in the information element, the UE 104 can determine the first carrier based on the first SSB 214. The UE can determine the CORESET configuration of the second carrier and the system information of the second carrier in the first carrier. The second value in the information element may indicate that the SIB may not be transmitted in the second carrier.

[0139] For example, for (multiple) ES-SSBs, kSSB It can be configured within [24, 29] for FR1 and within [12, 13] for FR2. In this case, for UEs that do not support ES, as specified, this type of k SSB The value indicates that CORESET#0 does not exist, and the UE can find the SSB that provides the CORESET#0 configuration based on PDCCH-configSIB1 in the MIB.

[0140] For UEs that support ES, the UE can interpret such an SSB as an ES-SSB. This interpretation can be based on the configuration in the MIB of the SSB, such as dmrs-TypeA-Position or spare bits. CORESET#0 exists, but an ES-SSB does not provide a CORESET=0 configuration. Instead, the UE can find the SSB that provides the CORESET#0 configuration and system information for the ES carrier in the SSB of the carrier, based on PDCCH-configSIB1 in the MIB.

[0141] Specifically, if the UE 104 that supports ES is determined to be for FR1, 24≤ k SSB ≤29 or for FR2, 12≤ k SSB If the value is ≤13, then UE 104 can determine that CORESET#0 exists, but the configuration of CORESET#0 is not provided by ES-SIB1. The UE can determine the nearest GSCN (in the corresponding frequency direction) of the second SSB as... . It is the GSCN of the first SS / PBCH block, in FR1 and FR2-1. In FR2-2, ,and The GSCN offset is provided by Table 1-1 for FR1 and Table 1-2 for FR2. UE 104 can obtain the CORESET#0 configuration and symbol information in the carrier through the second SSB.

[0142] Figure 4An example of a device 400 for obtaining support system information according to various aspects of this disclosure is illustrated. Device 400 may be an example of a UE 104 as described herein. Device 400 may support wireless communication with one or more network entities 102, UE 104, or any combination thereof. Device 400 may include components for bidirectional communication, including components for transmitting and receiving communications (such as processor 402, memory 404, transceiver 406, and optional I / O controller 408). These components may communicate electronically or be otherwise coupled (e.g., operative ground, communication ground, functional ground, electronic ground, electrical ground) via one or more interfaces (e.g., bus).

[0143] Processor 402, memory 404, transceiver 406, or various combinations thereof or various components thereof may be examples of components used to perform the various aspects of this disclosure described herein. For example, processor 402, memory 404, transceiver 406, or various combinations thereof or components thereof may support methods for performing one or more of the operations described herein.

[0144] In some implementations, processor 402, memory 404, transceiver 406, or various combinations or components thereof may be implemented in hardware (e.g., in a communication management circuitry system). The hardware may include a processor, digital signal processor (DSP), application-specific integrated circuit (ASIC), field-programmable gate array (FPGA) or other programmable logic device, discrete gate or transistor logic, discrete hardware components, or any combination thereof, configured to or otherwise supporting components for performing the functions described in this disclosure. In some implementations, processor 402 and memory 404 coupled to processor 402 may be configured to perform one or more of the functions described herein (e.g., instructions stored in memory 404 are executed by processor 402).

[0145] For example, processor 402 may support wireless communication at device 400 according to the examples disclosed herein. Processor 402 may be configured to operate to support components for: receiving from a base station, receiving first downlink control information (DCI) for paging in a first carrier or receiving a first synchronization signal and a physical broadcast channel (PBCH) block (SSB) in a second carrier, wherein the first DCI includes a short message; and, upon receiving the first DCI, acquiring system information of the second carrier in the first carrier based on the short message; or, upon receiving the first SSB, determining whether a system information block (SIB) is transmitted in the second carrier based on the first SSB.

[0146] Processor 402 may include intelligent hardware devices (e.g., general-purpose processors, DSPs, CPUs, microcontrollers, ASICs, FPGAs, programmable logic devices, discrete gate or transistor logic components, discrete hardware components, or any combination thereof). In some implementations, processor 402 may be configured to use a memory controller to operate a memory array. In some other implementations, the memory controller may be integrated into processor 402. Processor 402 may be configured to execute computer-readable instructions stored in memory (e.g., memory 404) to cause device 400 to perform various functions of this disclosure, such that device 400 can perform the functions described in Figures 2 to 3. Figure 6 Any process discussed in this disclosure.

[0147] Memory 404 may include random access memory (RAM) and read-only memory (ROM). Memory 404 may store computer-readable, computer-executable code, including instructions that, when executed by processor 402, cause device 400 to perform the various functions described herein. The code may be stored in a non-transitory computer-readable medium, such as system memory or another type of memory. In some implementations, the code may not be directly executed by processor 402, but may cause a computer (e.g., when compiled and executed) to perform the functions described herein. In some implementations, memory 404 may include a basic I / O system (BIOS) that controls basic hardware or software operations, such as interaction with peripheral components or devices.

[0148] I / O controller 408 can manage input and output signals for device 400. I / O controller 408 can also manage peripheral devices not integrated into device M02. In some implementations, I / O controller 408 can represent a physical connection or port to an external peripheral device. In some implementations, I / O controller 408 can utilize an operating system such as iOS®, Android®, MS-WINDOWS®, OS / 2®, UNIX®, LINUX®, or another known operating system. In some implementations, I / O controller 408 can be implemented as part of a processor (such as processor 406). In some implementations, a user can interact with device 400 via I / O controller 408 or via hardware components controlled by I / O controller 408.

[0149] In some implementations, device 400 may include a single antenna 410. However, in other implementations, device 400 may have more than one antenna 410 (i.e., multiple antennas), including multiple antenna planes or antenna arrays capable of concurrently transmitting or receiving multiple wireless transmissions. Transceiver 406 may communicate bidirectionally via one or more antennas 410, wired or wireless links as described herein. For example, transceiver 406 may represent a wireless transceiver and may communicate bidirectionally with another wireless transceiver. Transceiver 406 may also include a modem for modulating packets to provide modulated packets to one or more antennas 410 for transmission, and to demodulate packets received from one or more antennas 410. Transceiver 406 may include one or more transmit chains, one or more receive chains, or combinations thereof.

[0150] The transmission chain can be configured to generate and transmit signals (e.g., control information, data, packets). The transmission chain may include at least one modulator for modulating data onto a carrier signal, preparing it for transmission over a wireless medium. The at least one modulator may be configured to support one or more techniques, such as amplitude modulation (AM), frequency modulation (FM), or digital modulation schemes (e.g., phase shift keying (PSK) or quadrature amplitude modulation (QAM)). The transmission chain may also include at least one power amplifier configured to amplify the modulated signal to an appropriate power level suitable for transmission over a wireless medium. The transmission chain may also include one or more antennas 410 for transmitting the amplified signal into the air or wireless medium.

[0151] A receiver chain can be configured to receive signals (e.g., control information, data, packets) over a wireless medium. For example, the receiver chain may include one or more antennas 410 for receiving signals over the air or wireless medium. The receiver chain may include at least one amplifier (e.g., a low-noise amplifier (LNA)) configured to amplify the received signal. The receiver chain may include at least one demodulator configured to demodulate the received signal and acquire the transmitted data by reversing the modulation technique applied during signal transmission. The receiver chain may include at least one decoder for decoding the demodulated signal to receive the transmitted data.

[0152] Figure 5An example of a device 500 for obtaining support system information according to various aspects of this disclosure is illustrated. Device 500 may be an example of a network entity 102 as described herein. Device 500 may support wireless communication with one or more network entities 102, UE 104, or any combination thereof. Device 500 may include components for bidirectional communication, including components for transmitting and receiving communications (such as processor 502, memory 504, transceiver 506, and optional I / O controller 508). These components may communicate electronically or be otherwise coupled (e.g., operative ground, communication ground, functional ground, electronic ground, electrical ground) via one or more interfaces (e.g., bus).

[0153] Processor 502, memory 504, transceiver 506, or various combinations thereof or various components thereof may be examples of components used to perform the various aspects of this disclosure described herein. For example, processor 502, memory 504, transceiver 506, or various combinations thereof or components thereof may support methods for performing one or more of the operations described herein.

[0154] In some implementations, processor 502, memory 504, transceiver 506, or various combinations or components thereof may be implemented in hardware (e.g., in a communication management circuitry system). The hardware may include a processor, digital signal processor (DSP), application-specific integrated circuit (ASIC), field-programmable gate array (FPGA) or other programmable logic device, discrete gate or transistor logic, discrete hardware components, or any combination thereof, configured to or otherwise supporting components for performing the functions described in this disclosure. In some implementations, processor 502 and memory 504 coupled to processor 502 may be configured to perform one or more of the functions described herein (e.g., instructions stored in memory 504 are executed by processor 502).

[0155] For example, processor 502 may support wireless communication at device 500 according to the examples disclosed herein. Processor 502 may be configured to support components for transmitting first downlink control information (DCI) for paging to a user equipment in a first carrier, wherein the first DCI includes a short message instructing the user equipment to acquire system information of a second carrier in the first carrier.

[0156] Processor 502 may include intelligent hardware devices (e.g., general-purpose processors, DSPs, CPUs, microcontrollers, ASICs, FPGAs, programmable logic devices, discrete gate or transistor logic components, discrete hardware components, or any combination thereof). In some implementations, processor 502 may be configured to use a memory controller to operate a memory array. In some other implementations, the memory controller may be integrated into processor 502. Processor 502 may be configured to execute computer-readable instructions stored in memory (e.g., memory 504) to cause device 500 to perform various functions of this disclosure, so that device 500 can perform the functions described in Figures 2 to 3. Figure 6 Any process discussed in this disclosure.

[0157] Memory 504 may include random access memory (RAM) and read-only memory (ROM). Memory 504 may store computer-readable, computer-executable code, including instructions that, when executed by processor 502, cause device 500 to perform the various functions described herein. The code may be stored in a non-transitory computer-readable medium, such as system memory or another type of memory. In some implementations, the code may not be directly executed by processor 502, but may cause a computer (e.g., when compiled and executed) to perform the functions described herein. In some implementations, memory 504 may include a basic I / O system (BIOS) that controls basic hardware or software operations, such as interaction with peripheral components or devices.

[0158] I / O controller 508 can manage input and output signals for device 500. I / O controller 508 can also manage peripheral devices not integrated into device M02. In some implementations, I / O controller 508 can represent a physical connection or port to an external peripheral device. In some implementations, I / O controller 508 can utilize an operating system such as iOS®, ANDROID®, MS-WINDOWS®, OS / 2®, UNIX®, LINUX®, or another known operating system. In some implementations, I / O controller 508 can be implemented as part of a processor (such as processor 506). In some implementations, a user can interact with device 500 via I / O controller 508 or via hardware components controlled by I / O controller 508.

[0159] In some implementations, device 500 may include a single antenna 510. However, in other implementations, device 500 may have more than one antenna 510 (i.e., multiple antennas), including multiple antenna planes or antenna arrays capable of concurrently transmitting or receiving multiple wireless transmissions. Transceiver 506 may communicate bidirectionally via one or more antennas 510, wired or wireless links as described herein. For example, transceiver 506 may represent a wireless transceiver and may communicate bidirectionally with another wireless transceiver. Transceiver 506 may also include a modem for modulating packets to provide modulated packets to one or more antennas 510 for transmission, and to demodulate packets received from one or more antennas 510. Transceiver 506 may include one or more transmit chains, one or more receive chains, or combinations thereof.

[0160] The transmission chain can be configured to generate and transmit signals (e.g., control information, data, packets). The transmission chain may include at least one modulator for modulating data onto a carrier signal, preparing it for transmission over a wireless medium. The at least one modulator may be configured to support one or more techniques, such as amplitude modulation (AM), frequency modulation (FM), or digital modulation schemes (e.g., phase shift keying (PSK) or quadrature amplitude modulation (QAM)). The transmission chain may also include at least one power amplifier configured to amplify the modulated signal to an appropriate power level suitable for transmission over a wireless medium. The transmission chain may also include one or more antennas 510 for transmitting the amplified signal into the air or wireless medium.

[0161] A receiver chain can be configured to receive signals (e.g., control information, data, packets) over a wireless medium. For example, the receiver chain may include one or more antennas 510 for receiving signals over the air or wireless medium. The receiver chain may include at least one amplifier (e.g., a low-noise amplifier (LNA)) configured to amplify the received signal. The receiver chain may include at least one demodulator configured to demodulate the received signal and acquire the transmitted data by reversing the modulation technique applied during signal transmission. The receiver chain may include at least one decoder for decoding the demodulated signal to receive the transmitted data.

[0162] Figure 6An example of a processor 600 supporting the acquisition of system information according to various aspects of this disclosure is illustrated. Processor 600 may be an example of a processor configured to perform various operations according to the examples described herein. Processor 600 may be implemented in a device or component thereof as described herein. For example, the device may be an example of UE 104 described herein. Processor 600 may include a controller 602 configured to perform various operations according to the examples described herein. Processor 600 may optionally include at least one memory 604, such as an L1 / L2 / L3 cache. Additionally or alternatively, processor 600 may optionally include one or more arithmetic logic units (ALUs) 600. One or more of these components may be electronically communicated or otherwise coupled (e.g., operative ground, communicative ground, functional ground, electronic ground, electrical ground) via one or more interfaces (e.g., buses).

[0163] Processor 600 may be a processor chipset and includes a protocol stack (e.g., a software stack) executed by the processor chipset to perform various operations (e.g., receive, acquire, acquire, send, output, forward, store, determine, identify, access, write, read) according to the examples described herein. The processor chipset may include one or more cores, one or more caches (e.g., memory local to the processor chipset (e.g., processor 600) or included in the processor chipset) or other memory (e.g., random access memory (RAM), read-only memory (ROM), dynamic RAM (DRAM), synchronous dynamic RAM (SDRAM), static RAM (SRAM), ferroelectric RAM (FeRAM), magnetic RAM (MRAM), resistive RAM (RRAM), flash memory, phase-change memory (PCM), etc.).

[0164] Controller 602 can be configured to manage and coordinate various operations of processor 600 (e.g., signaling, receiving, acquiring, sending, outputting, forwarding, storing, determining, identifying, accessing, writing, and reading) to enable processor 600 to support various operations according to the examples described herein. For example, controller 602 can operate as a control unit of processor 600, generating control signals that manage the operation of various components of processor 600. These control signals include enabling or disabling functional units, selecting data paths, initiating memory accesses, and coordinating operation timing.

[0165] Controller 602 can be configured to fetch (e.g., fetch, get, receive) instructions from memory 604 and determine subsequent instructions(s) to be executed, enabling processor 600 to support various operations according to the examples described herein. Controller 602 can be configured to track the memory addresses of instructions associated with memory 604. Controller 602 can be configured to decode instructions to determine the operations to be performed and the operands involved. For example, controller 602 can be configured to interpret instructions and determine control signals to be output to other components of processor 600, enabling processor 600 to support various operations according to the examples described herein. Additionally or alternatively, controller 602 can be configured to manage data flow within processor 600. Controller 602 can be configured to control data transfers between registers, arithmetic logic unit (ALU), and other functional units of processor 600.

[0166] Memory 604 may include one or more caches (e.g., memory native to or included in processor 600) or other memories such as RAM, ROM, DRAM, SDRAM, SRAM, MRAM, flash memory, etc. In some implementations, memory 604 may reside within or on the processor chipset (e.g., native to processor 600). In some other implementations, memory 604 may reside outside the processor chipset (e.g., remote from processor 600).

[0167] Memory 604 may store computer-readable, computer-executable code, including instructions that, when executed by processor 600, cause processor 600 to perform the various functions described herein. The code may be stored in a non-transitory computer-readable medium, such as system memory or another type of memory. Controller 602 and / or processor 600 may be configured to execute the computer-readable instructions stored in memory 604 to cause processor 600 to perform various functions. For example, processor 600 and / or controller 602 may be coupled to or coupled to memory 604, and processor 600, controller 602, and memory 604 may be configured to perform the various functions described herein. In some examples, processor 600 may include multiple processors, and memory 604 may include multiple memories. One or more of the multiple processors may be coupled to one or more of the multiple memories, which may be configured individually or collectively to perform the various functions described herein.

[0168] One or more ALU 606s can be configured to support various operations according to the examples described herein. In some implementations, one or more ALU 606s may reside within or on a processor chipset (e.g., processor 600). In some other implementations, one or more ALU 606s may reside outside the processor chipset (e.g., processor 600). One or more ALU 606s can perform one or more computations, such as performing addition, subtraction, multiplication, and division on data. For example, one or more ALU 606s can receive input operands and an opcode that determines the operation to be performed. One or more ALU 606s are configured with various logic and arithmetic circuitry, including adders, subtractors, shifters, and logic gates, to process and manipulate data according to the operation. Additionally or alternatively, one or more ALU 606s may support logical operations such as AND, OR, XOR, NOR, and NAND, enabling one or more ALU 606s to handle conditional operations, comparisons, and bitwise operations.

[0169] Processor 600 can support wireless communication according to the examples disclosed herein. Processor 600 can be configured or operable to support components for: receiving from a base station, receiving first downlink control information (DCI) for paging in a first carrier or receiving a first synchronization signal and a physical broadcast channel (PBCH) block (SSB) in a second carrier, wherein the first DCI includes a short message; and, upon receiving the first DCI, acquiring system information of the second carrier in the first carrier based on the short message; or, upon receiving the first SSB, determining whether a system information block (SIB) is transmitted in the second carrier based on the first SSB.

[0170] Figure 7 An example of a processor 700 for acquiring support system information according to various aspects of this disclosure is illustrated. Processor 700 may be an example of a processor configured to perform various operations according to the examples described herein. Processor 700 may be implemented in a device or component thereof as described herein. For example, the device may be an example of a network entity 102 as described herein. Processor 700 may include a controller 702 configured to perform various operations according to the examples described herein. Processor 700 may optionally include at least one memory 704, such as an L1 / L2 / L3 cache. Additionally or alternatively, processor 700 may optionally include one or more arithmetic logic units (ALUs) 700. One or more of these components may be electronically communicated or otherwise coupled (e.g., operative ground, communicative ground, functional ground, electronic ground, electrical ground) via one or more interfaces (e.g., buses).

[0171] Processor 700 may be a processor chipset and includes a protocol stack (e.g., a software stack) executed by the processor chipset to perform various operations (e.g., receive, acquire, acquire, send, output, forward, store, determine, identify, access, write, read) according to the examples described herein. The processor chipset may include one or more cores, one or more caches (e.g., memory local to the processor chipset (e.g., processor 700) or included in the processor chipset) or other memory (e.g., random access memory (RAM), read-only memory (ROM), dynamic RAM (DRAM), synchronous dynamic RAM (SDRAM), static RAM (SRAM), ferroelectric RAM (FeRAM), magnetic RAM (MRAM), resistive RAM (RRAM), flash memory, phase-change memory (PCM), etc.).

[0172] Controller 702 can be configured to manage and coordinate various operations of processor 700 (e.g., signaling, receiving, acquiring, sending, outputting, forwarding, storing, determining, identifying, accessing, writing, and reading) to enable processor 700 to support various operations according to the examples described herein. For example, controller 702 can operate as a control unit of processor 700, generating control signals that manage the operation of various components of processor 700. These control signals include enabling or disabling functional units, selecting data paths, initiating memory accesses, and coordinating operation timing.

[0173] Controller 702 can be configured to fetch (e.g., fetch, get, receive) instructions from memory 704 and determine subsequent instructions(s) to be executed, enabling processor 700 to support various operations according to the examples described herein. Controller 702 can be configured to track the memory addresses of instructions associated with memory 704. Controller 702 can be configured to decode instructions to determine the operations to be performed and the operands involved. For example, controller 702 can be configured to interpret instructions and determine control signals to be output to other components of processor 700, enabling processor 700 to support various operations according to the examples described herein. Additionally or alternatively, controller 702 can be configured to manage data flow within processor 700. Controller 702 can be configured to control data transfers between registers, arithmetic logic unit (ALU), and other functional units of processor 700.

[0174] Memory 704 may include one or more caches (e.g., memory native to or included in processor 700) or other memories such as RAM, ROM, DRAM, SDRAM, SRAM, MRAM, flash memory, etc. In some implementations, memory 704 may reside within or on the processor chipset (e.g., native to processor 700). In some other implementations, memory 704 may reside outside the processor chipset (e.g., remote from processor 700).

[0175] Memory 704 may store computer-readable, computer-executable code, including instructions that, when executed by processor 700, cause processor 700 to perform the various functions described herein. The code may be stored in a non-transitory computer-readable medium, such as system memory or another type of memory. Controller 702 and / or processor 700 may be configured to execute the computer-readable instructions stored in memory 704 to cause processor 700 to perform various functions. For example, processor 700 and / or controller 702 may be coupled to or coupled to memory 704, and processor 700, controller 702, and memory 704 may be configured to perform the various functions described herein. In some examples, processor 700 may include multiple processors, and memory 704 may include multiple memories. One or more of the multiple processors may be coupled to one or more of the multiple memories, which may be configured individually or collectively to perform the various functions described herein.

[0176] One or more ALU 700s can be configured to support various operations according to the examples described herein. In some implementations, one or more ALU 700s may reside within or on a processor chipset (e.g., processor 700). In some other implementations, one or more ALU 700s may reside outside the processor chipset (e.g., processor 700). One or more ALU 700s can perform one or more computations, such as performing addition, subtraction, multiplication, and division on data. For example, one or more ALU 700s can receive input operands and an opcode that determines the operation to be performed. One or more ALU 700s are configured with various logic and arithmetic circuitry, including adders, subtractors, shifters, and logic gates, to process and manipulate data according to the operation. Additionally or alternatively, one or more ALU 700s may support logical operations such as AND, OR, XOR, NOR, and NAND, enabling one or more ALU 700s to handle conditional operations, comparisons, and bitwise operations.

[0177] Processor 700 may support wireless communication according to the examples disclosed herein. Processor 700 may be configured or operable to support components for transmitting first downlink control information (DCI) for paging to a user equipment in a first carrier, wherein the first DCI includes a short message instructing the user equipment to acquire system information of a second carrier in the first carrier.

[0178] Figure 8 A flowchart illustrating a method 800 for obtaining support system information according to various aspects of this disclosure is provided. The operation of method 800 can be implemented by the device or components thereof described herein. For example, the operation of method 800 can be performed by the UE 104 described herein. In some implementations, the device can execute a set of instructions to control the functional elements of the device to perform the described functions. Alternatively or additionally, the device can use dedicated hardware to perform aspects of the described functions.

[0179] At 805, the method may include receiving first downlink control information (DCI) for paging from a base station in a first carrier, wherein the first DCI includes a short message. The operation of 805 can be performed according to the examples described herein. In some implementations, aspects of the operation of 805 may be derived from references... Figure 1A The device described is used to perform this action.

[0180] At 810, the method may include obtaining system information of the second carrier based on a short message in the first carrier. The operation of 810 can be performed according to the examples described herein. In some implementations, aspects of the operation of 810 can be derived from references... Figure 1A The device described is used to perform this action.

[0181] Figure 9 A flowchart illustrating a method 900 for obtaining support system information according to various aspects of this disclosure is shown. The operation of method 900 can be implemented by the device or components thereof described herein. For example, the operation of method 900 can be performed by the UE 104 described herein. In some implementations, the device can execute a set of instructions to control the functional elements of the device to perform the described functions. Alternatively or additionally, the device can use dedicated hardware to perform aspects of the described functions. Method 900 can be considered a continuation of method 800.

[0182] At position 905, the method may include switching from a first carrier to a second carrier. The operation of position 905 can be performed according to the examples described herein. In some implementations, aspects of the operation of position 905 can be derived from references... Figure 1A The device described is used to perform this action.

[0183] At 910, the method may include receiving a first SSB of the second carrier from the base station in the second carrier. The operation of 910 can be performed according to the examples described herein. In some implementations, aspects of the operation of 910 may be derived from references... Figure 1A The device described is used to perform this action.

[0184] Figure 10 A flowchart illustrating a method 1000 for obtaining support system information according to various aspects of this disclosure is provided. The operation of method 1000 can be implemented by the device or components thereof described herein. For example, the operation of method 1000 can be performed by the UE 104 described herein. In some implementations, the device can execute a set of instructions to control the functional elements of the device to perform the described functions. Alternatively or additionally, the device can use dedicated hardware to perform aspects of the described functions.

[0185] At point 1005, the method may include receiving, from a base station, first downlink control information (DCI) for paging in a first carrier or receiving, in a second carrier, a first synchronization signal and a physical broadcast channel (PBCH) block (SSB). The operation of point 1005 can be performed according to the examples described herein. In some implementations, aspects of the operation of point 1005 may be derived from references. Figure 1A The device described is used to perform this action.

[0186] At point 1010, the method may include determining, based on the first SSB, whether a System Information Block (SIB) is transmitted on the second carrier. The operation at point 1010 can be performed according to the examples described herein. In some implementations, aspects of the operation at point 1010 may be derived from references... Figure 1A The device described is used to perform this action.

[0187] Figure 11 A flowchart illustrating a method 1100 for obtaining support system information according to various aspects of this disclosure is provided. The operation of method 1100 can be implemented by the device or components thereof described herein. For example, the operation of method 1100 can be performed by the UE 104 described herein. In some implementations, the device can execute a set of instructions to control the functional elements of the device to perform the described functions. Alternatively or additionally, the device can use dedicated hardware to perform aspects of the described functions. Method 1100 can be considered a continuation of method 900 or method 1000.

[0188] At 1105, the method may include determining whether a first value is indicated in an information element of the first SSB. The operation at 1105 can be performed according to the examples described herein. In some implementations, aspects of the operation at 1105 may be derived from references. Figure 1A The device described is used to perform this action.

[0189] If so, at 1110, the method may include determining the configuration of the control resource set (CORESET) of the second carrier based on the first SSB of the second carrier. The operation of 1110 can be performed according to the examples described herein. In some implementations, aspects of the operation of 1110 may be derived from references... Figure 1A The device described is used to perform this action.

[0190] At 1115, the method may include receiving a second SSB of the first carrier from the base station in the first carrier. The operation of 1115 can be performed according to the examples described herein. In some implementations, aspects of the operation of 1115 may be derived from references... Figure 1A The device described is used to perform this action.

[0191] At 1120, the method may include determining a subcarrier offset based on information elements in the second SSB, the subcarrier offset being used for the frequency position of the second carrier's CORESET. The operation at 1120 can be performed according to the examples described herein. In some implementations, aspects of the operation at 1120 may be derived from references... Figure 1A The device described is used to perform this action.

[0192] Figure 12 A flowchart illustrating a method 1200 for obtaining support system information according to various aspects of this disclosure is shown. The operation of method 1200 can be implemented by the device or components thereof described herein. For example, the operation of method 1200 can be performed by the UE 104 described herein. In some implementations, the device can execute a set of instructions to control the functional elements of the device to perform the described functions. Alternatively or additionally, the device can use dedicated hardware to perform aspects of the described functions. Method 1200 can be considered a continuation of method 900 or method 1000.

[0193] At 1205, the method may include determining whether a second value is indicated in an information element of the first SSB. The operation at 1205 can be performed according to the examples described herein. In some implementations, aspects of the operation at 1205 may be derived from references. Figure 1A The device described is used to perform this action.

[0194] If so, at 1210, the method may include determining the first carrier based on the first SSB. The operation of 1210 can be performed according to the examples described herein. In some implementations, aspects of the operation of 1210 may be derived from references... Figure 1A The device described is used to perform this action.

[0195] At 1215, the method may include determining the configuration of the CORESET of the second carrier and the system information of the second carrier in the first carrier. The operation of 1215 can be performed according to the examples described herein. In some implementations, aspects of the operation of 1215 may be derived from references... Figure 1A The device described is used to perform this action.

[0196] Figure 13 A flowchart illustrating a method 1300 for obtaining support system information according to various aspects of this disclosure is provided. The operation of method 1300 can be implemented by the device or components thereof described herein. For example, the operation of method 1300 can be performed by the network entity 102 described herein. In some implementations, the device can execute a set of instructions to control the functional elements of the device to perform the described functions. Alternatively or additionally, the device can use dedicated hardware to perform aspects of the described functions.

[0197] At 1305, the method may include sending first downlink control information (DCI) for paging to the user equipment in the first carrier, wherein the first DCI includes a short message instructing the user equipment to acquire system information of the second carrier in the first carrier. The operation of 1305 can be performed according to the examples described herein. In some implementations, aspects of the operation of 1305 may be derived from references... Figure 1A The device described is used to perform this action.

[0198] Figure 14 A flowchart illustrating a method 1400 for obtaining support system information according to various aspects of this disclosure is provided. The operation of method 1400 can be implemented by the device or components thereof described herein. For example, the operation of method 1400 can be performed by the network entity 102 described herein. In some implementations, the device can execute a set of instructions to control the functional elements of the device to perform the described functions. Alternatively or additionally, the device can use dedicated hardware to perform aspects of the described functions. Method 1400 can be considered a continuation of method 1300.

[0199] At 1405, the method may include transmitting a second DCI to the user equipment on a first carrier during a first timing associated with the scheduling of the system information block, wherein the first timing is after a paging timing associated with the first DCI or after a paging frame containing that paging timing. The operation of 1405 can be performed according to the examples described herein. In some implementations, aspects of the operation of 1405 may be derived from references... Figure 1A The device described is used to perform this action.

[0200] Figure 15A flowchart illustrating a method 1500 for obtaining support system information according to various aspects of this disclosure is provided. The operation of method 1500 can be implemented by the device or components thereof described herein. For example, the operation of method 1500 can be performed by the network entity 102 described herein. In some implementations, the device can execute a set of instructions to control the functional elements of the device to perform the described functions. Alternatively or additionally, the device can use dedicated hardware to perform aspects of the described functions.

[0201] At 1505, the method may include, on the second carrier, transmitting a first synchronization signal and a Physical Broadcast Channel (PBCH) block (SSB) to the user equipment, the first SSB instructing the user equipment to determine, based on the first SSB, whether a System Information Block (SIB) is to be transmitted on the second carrier. The operation of 1505 can be performed according to the examples described herein. In some implementations, aspects of the operation of 1505 may be derived from references... Figure 1A The device described is used to perform this action.

[0202] It should be noted that the methods described in this paper describe possible implementations, and the operations and steps can be rearranged or otherwise modified, and other implementations are also possible. Furthermore, aspects from two or more methods can be combined.

[0203] The various illustrative boxes and components described in connection with this disclosure may be implemented or performed by a general-purpose processor, DSP, ASIC, CPU, FPGA or other programmable logic device, discrete gate or transistor logic, discrete hardware component, or any combination thereof, designed to perform the functions described herein. The general-purpose processor may be a microprocessor, but alternatively, the processor may be any processor, controller, microcontroller, or state machine. The processor may also be implemented as a combination of computing devices (e.g., a combination of a DSP and a microprocessor, multiple microprocessors, one or more microprocessors combined with a DSP core, or any other such configuration).

[0204] The functions described herein can be implemented in hardware, software executed by a processor, firmware, or any combination thereof. If implemented in software executed by a processor, the functions can be stored on or transmitted via a computer-readable medium as one or more instructions or code. Other examples and implementations are within the scope of this disclosure and the appended claims. For example, due to the nature of software, the functions described herein can be implemented using software executed by a processor, hardware, firmware, hardwiring, or any combination of the foregoing. Features implementing the functions can also be physically located in various locations, including being distributed such that portions of the functions are implemented at different physical locations.

[0205] Computer-readable media include both non-transitory computer storage media and communication media, with the latter including any medium that facilitates the transfer of a computer program from one place to another. Non-transitory storage media can be any available medium accessible by a general-purpose or special-purpose computer. For example, non-transitory computer-readable media can include RAM, ROM, electrically erasable programmable ROM (EEPROM), flash memory, optical disc (CD) ROM or other optical disc storage, magnetic disk storage or other magnetic storage devices, or any other non-transitory medium that can be used to carry or store desired program code components, in the form of instructions or data structures, and that can be accessed by a general-purpose or special-purpose computer or a general-purpose or special-purpose processor.

[0206] As used herein, including in the claims, the article “a” preceding an element is unrestricted and should be understood to mean “at least one” or “one or more” of those elements. The terms “a,” “at least one,” “one or more,” and “at least one of one or more” are interchangeable. As used herein, including in the claims, the “or” used in a list of items (e.g., a list of items prefixed with phrases such as “at least one of…” or “one or more of…” or “one or two of…”) indicates an inclusive list, such that, for example, a list of at least one of A, B, or C means A or B or C or AB or AC or BC or ABC (i.e., A and B and C). Furthermore, as used herein, the phrase “based on” should not be construed as a reference to a closed set of conditions. For example, an example step described as “based on condition A” could be based on both condition A and condition B without departing from the scope of this disclosure. In other words, as used herein, the phrase “based on” should be interpreted in the same manner as the phrase “at least partially based on.” Moreover, as used herein, including in the claims, “set” can include one or more elements.

[0207] The description herein is provided to enable those skilled in the art to make or use this disclosure. Various modifications to this disclosure will be apparent to those skilled in the art, and the general principles defined herein can be applied to other variations without departing from the scope of this disclosure. Therefore, this disclosure is not limited to the examples and designs described herein, but should be accorded the widest scope consistent with the principles and novel features disclosed herein.

Claims

1. A user equipment, comprising: processor; as well as A transceiver, which is coupled to the processor, The processor is configured as follows: The transceiver receives, via a base station, first downlink control information (DCI) for paging on a first carrier or a first synchronization signal and a physical broadcast channel (PBCH) block (SSB) on a second carrier, wherein the first DCI includes a short message; and Upon receiving the first DCI, the system information of the second carrier is obtained from the first carrier based on the short message; or Upon receiving the first SSB, it is determined, based on the first SSB, whether the System Information Block (SIB) is transmitted in the second carrier.

2. The user equipment according to claim 1, wherein the processor is further configured to: Upon receiving the first DCI, the system switches from the first carrier to the second carrier; and In the second carrier, the first SSB of the second carrier is received from the base station via the transceiver.

3. The user equipment of claim 1, wherein the short message includes a bit field indicating at least one of the following: System information retrieval; or Carrier switching.

4. The user equipment according to claim 1, wherein the first DCI includes scheduling information of the system information of the second carrier, and the system information of the second carrier is scheduled by the scheduling information.

5. The user equipment according to claim 4, wherein the first DCI includes an indication that the scheduling information exists in the first DCI.

6. The user equipment according to claim 1, wherein the processor is further configured to: In a first timing associated with the scheduling of a system information block, in the first carrier, a second DCI is received from the base station via the transceiver, wherein the first timing is after a paging timing associated with the first DCI or after a paging frame containing the paging timing.

7. The user equipment according to claim 1, wherein the processor is further configured to: In a time window that includes at least one timing associated with the scheduling of system information blocks, a second DCI is received from the base station via the transceiver in the first carrier, wherein the time window is after the paging timing associated with the first DCI or after the paging frame that includes the paging timing.

8. The user equipment according to claim 6 or 7, wherein the second DCI is scrambled by a radio network temporary identifier RNTI, the RNTI being different from the system information RNTI (SI-RNTI), and The system information is scheduled by the scheduling information in the second DCI.

9. The user equipment according to claim 6 or 7, wherein the second DCI is scrambled by SI-RNTI, and the processor is further configured to: In the first carrier, the SIB scheduled by the second DCI is received from the base station via the transceiver, and The SIB includes an indication indicating whether the system information of the second carrier or the scheduling information of the system information of the second carrier is included in the SIB.

10. The user equipment according to claim 6 or 7, wherein the second DCI is scrambled by SI-RNTI, and the processor is further configured to: In the first carrier, the SIB scheduled by the second DCI is received from the base station via the transceiver. The second DCI includes an indication indicating whether the system information of the second carrier or the scheduling information of the system information of the second carrier is included in the SIB.

11. The user equipment according to claim 1 or 2, wherein the first SSB includes information elements regarding subcarrier offset parameters, and wherein the processor is further configured to: When the first value is indicated in the information element, the configuration of the control resource set CORESET of the second carrier is determined based on the first SSB of the second carrier.

12. The user equipment of claim 11, wherein the processor is further configured to: If the first value is indicated in the information element, it is determined that the first SSB provides a valid configuration for the CORESET.

13. The user equipment of claim 11, wherein determining whether the SIB is transmitted in the second carrier comprises: If the first value is indicated in the information element, it is determined that the SIB was not transmitted on the second carrier.

14. The user equipment of claim 11, wherein the processor is further configured to: In the first carrier, the second SSB of the first carrier is received from the base station via the transceiver; and Based on the information elements in the second SSB, a subcarrier offset is determined, the subcarrier offset being used for the frequency position of the CORESET of the second carrier.

15. The user equipment according to claim 1 or 2, wherein the first SSB includes information elements regarding subcarrier offset parameters, and wherein the processor is further configured to: When the second value is indicated in the information element Based on the first SSB, the first carrier is determined; and The configuration of the CORESET of the second carrier and the system information of the second carrier are determined in the first carrier.

16. The user equipment of claim 15, wherein determining whether the SIB is transmitted in the second carrier comprises: If the second value is indicated in the information element, it is determined that the SIB was not transmitted on the second carrier.

17. The user equipment according to claim 11 or 15, wherein the information element is a subcarrier offset field, the subcarrier offset field being included in the PBCH of the first SSB.

18. A base station, comprising: processor; as well as A transceiver, which is coupled to the processor, The processor is configured as follows: The transceiver transmits a first downlink control information (DCI) for paging to the user equipment in the first carrier, wherein the first DCI includes a short message instructing the user equipment to acquire system information of the second carrier in the first carrier; or In the second carrier, a first synchronization signal and a Physical Broadcast Channel (PBCH) block SSB are transmitted to the user equipment via the transceiver. The first SSB instructs the user equipment to determine whether a System Information Block (SIB) is transmitted in the second carrier based on the first SSB.

19. A method performed by a user equipment, the method comprising: The base station receives a first downlink control information (DCI) for paging on a first carrier or a first synchronization signal and a physical broadcast channel (PBCH) block (SSB) on a second carrier, wherein the first DCI includes a short message; and Upon receiving the first DCI, the system information of the second carrier is obtained from the first carrier based on the short message; or Upon receiving the first SSB, it is determined, based on the first SSB, whether the System Information Block (SIB) is transmitted in the second carrier.

20. A processor for wireless communication, comprising: At least one memory; as well as A controller, coupled to the at least one memory, and configured such that the controller: The transceiver receives, via a base station, first downlink control information (DCI) for paging on a first carrier or a first synchronization signal and a physical broadcast channel (PBCH) block (SSB) on a second carrier, wherein the first DCI includes a short message; and Upon receiving the first DCI, the system information of the second carrier is obtained from the first carrier based on the short message; or Upon receiving the first SSB, it is determined, based on the first SSB, whether the System Information Block (SIB) is transmitted in the second carrier.

Images