Cell global identifier reading enhancement

Abstract

The present application relates to apparatuses and components including devices and methods for determining a process cycle of a cell global identifier (CGI) reading process.

Description

Background Technology

[0001] The 3GPP (3rd Generation Partnership Project) network specifies that the network can request information about cells from the UE, allowing the UE to detect transmissions from these cells. The network can request information for a variety of reasons, such as for the UE to establish and / or transfer connections between cells. With the expansion and improvement of network technologies, the number of cells within a network has become enormous. Identifiers have been assigned to different cells, enabling the network and the UE to identify different cells. Attached Figure Description

[0002] Figure 1 An exemplary CGI reading process according to some implementation schemes is shown.

[0003] Figure 2 The CGI reading process according to some implementation schemes is shown.

[0004] Figure 3 An example of an exemplary timing arrangement according to some implementation schemes is shown.

[0005] Figure 4 An exemplary procedure period timing for a CGI read process is shown according to some implementation schemes.

[0006] Figure 5 An exemplary signaling diagram illustrating CGI reporting delays is shown according to some implementation schemes.

[0007] Figure 6 An exemplary process for determining the process cycle of a CGI reading process, according to some implementation schemes, is shown.

[0008] Figure 7 An exemplary process for determining the process cycle of a CGI reading process, according to some implementation schemes, is shown.

[0009] Figure 8 An exemplary process for performing a CGI reading and reporting process is shown according to some implementation schemes.

[0010] Figure 9 An exemplary beamforming circuit according to some implementation schemes is shown.

[0011] Figure 10 An example of an exemplary UE according to some implementation schemes is shown.

[0012] Figure 11 An exemplary gNB according to some implementation schemes is shown. Detailed Implementation

[0013] The following detailed description relates to the accompanying drawings. The same reference numerals may be used in different drawings to identify the same or similar elements. In the following description, specific details, such as particular structures, architectures, interfaces, technologies, etc., are set forth for illustrative and non-limiting purposes to provide a thorough understanding of various aspects of the various embodiments. However, it will be apparent to those skilled in the art that various aspects of the various embodiments may be practiced in other examples departing from these specific details. In some cases, descriptions of well-known devices, circuits, and methods have been omitted so as not to obscure the description of the various embodiments with unnecessary detail. For the purposes of this document, the phrase "A or B" means (A), (B), or (A and B).

[0014] The following is a glossary of terms that may be used in this disclosure.

[0015] As used herein, the term "circuit" refers to, is part of, or includes the following: hardware components such as electronic circuits, logic circuits, processors (shared, dedicated, or grouped) or memories (shared, dedicated, or grouped), application-specific integrated circuits (ASICs), field-programmable devices (FPDs) (e.g., field-programmable gate arrays (FPGAs), programmable logic devices (PLDs), complex PLDs (CPLDs), high-capacity PLDs (HCPLDs), structured ASICs, or programmable system-on-a-chip (SoCs)), digital signal processors (DSPs), etc. In some embodiments, a circuit may execute one or more software or firmware programs to provide at least some of the said functions. The term "circuit" may also refer to a combination of one or more hardware elements and program code for performing the functions (or a combination of circuits used in an electrical or electronic system). In these embodiments, the combination of hardware elements and program code may be referred to as a particular type of circuit.

[0016] As used herein, the term "processor circuit" means, is part of, or includes the following: a circuit capable of sequentially and automatically performing a series of arithmetic or logical operations or recording, storing, or transmitting digital data. The term "processor circuit" may also refer to an application processor, baseband processor, central processing unit (CPU), graphics processing unit, single-core processor, dual-core processor, triple-core processor, quad-core processor, or any other device capable of executing or otherwise operating computer-executable instructions (such as program code, software modules, and / or functional procedures).

[0017] As used herein, the term "interface circuit" refers to, is part of, or includes a circuit that enables the exchange of information between two or more components or devices. The term "interface circuit" can refer to one or more hardware interfaces, such as buses, I / O interfaces, peripheral component interfaces, network interface cards, etc.

[0018] As used herein, the term "user equipment" or "UE" refers to equipment of a remote user that has radio communication capabilities and can describe network resources in a communication network. Furthermore, the term "user equipment" or "UE" can be considered synonymous and can be referred to as a client, mobile phone, mobile device, mobile terminal, user terminal, mobile unit, mobile station, mobile user, subscriber, user, remote station, access agent, user agent, receiver, radio equipment, reconfigurable radio equipment, reconfigurable mobile device, etc. Additionally, the term "user equipment" or "UE" can include any type of wireless / wired equipment or any computing device that includes a wireless communication interface.

[0019] As used herein, the term "computer system" means any type of interconnected electronic device, computer device, or component thereof. Additionally, the term "computer system" or "system" may refer to the various components of a computer that are communicatively coupled to each other. Furthermore, the term "computer system" or "system" may refer to multiple computer devices or multiple computing systems that are communicatively coupled to each other and configured to share computing resources or network resources.

[0020] As used herein, the term "resource" refers to physical or virtual devices, physical or virtual components within a computing environment, or physical or virtual components within a specific device, such as computer equipment, mechanical equipment, memory space, processor / CPU time, processor / CPU utilization, processor and accelerator load, hardware time or utilization, power supply, input / output operations, port or network sockets, channel / link allocation, throughput, memory utilization, storage, network, databases and applications, units of workload, etc. "Hardware resource" can refer to computing, storage, or networking resources provided by physical hardware components. "Virtualized resource" can refer to computing, storage, or networking resources provided by virtualization infrastructure to applications, devices, systems, etc. The terms "network resource" or "communication resource" can refer to resources that computer equipment / systems can access via a communication network. The term "system resource" can refer to any kind of shared entity providing services and can include computing or network resources. System resources can be considered as a coherent set of functions, network data objects, or services accessible through a server, wherein such system resources reside on a single host or multiple hosts and are clearly identifiable.

[0021] As used herein, the term "channel" refers to any tangible or intangible transmission medium used for transmitting data or data streams. The term "channel" may be synonymous or equivalent with "communication channel," "data communication channel," "transmission channel," "data transmission channel," "access channel," "data access channel," "link," "data link," "carrier," "radio frequency carrier," or any other similar term indicating a path or medium through which data is transmitted. Additionally, as used herein, the term "link" refers to a connection between two devices used for transmitting and receiving information.

[0022] As used in this article, the terms "instantiate" and "instantiate" refer to the creation of an instance. "Instance" also refers to the concrete occurrence of an object, which may occur, for example, during the execution of program code.

[0023] The term "connection" can mean that two or more elements at a common communication protocol layer have an established signaling relationship with each other through a communication channel, link, interface, or reference point.

[0024] As used herein, the term "network element" refers to physical or virtualized equipment or infrastructure used to provide wired or wireless communication network services. The term "network element" may be considered synonymous with or referred to as networked computers, network hardware, network equipment, network nodes, virtualized network functions, etc.

[0025] The term "information element" refers to a structural element that contains one or more fields. The term "field" refers to the individual content of an information element, or the data element that contains that content. An information element may include one or more additional information elements.

[0026] Radio Access Network Group 4 (RAN4) introduced the requirement for Cell Global Identifier (CGI) readings for New Radio (NR) neighboring cells in Generation 3 Partnership Release 16 (Rel-16), and RAN4 also introduced Radio Resource Management (RRM) requirements for New Radio Unlicensed Spectrum (NR-U) in Rel-16. However, when performing CGI readings on NR-U cells, RAN4 does not consider any requirements or User Equipment (UE) behavior.

[0027] In Radio Access Network Group 1 (RAN1) and Radio Access Network Group 2 (RAN2), the CGI read capability in NR-U has been defined as follows:

[0028] cgi-Acquisition-r16:

[0029] The UE indicates whether it supports collecting CGI information from neighboring unlicensed NR cells in an unlicensed carrier by reading System Information Block Type 1 (SIB1) from adjacent unlicensed cells and reporting the collected information to the network.

[0030] Figure 1 An exemplary CGI reading procedure 100 according to some implementation schemes is illustrated. Specifically, the CGI reading procedure 100 illustrates a process that can be performed by a UE to read the CGI of a target cell. The CGI may allow the UE and the network to identify the same node, and the UE and the network may have separate identifiers for the same cell that is separate from the CGI prior to the CGI reading procedure 100. The UE may execute the CGI reading procedure 100 or a portion thereof in response to a CGI report being triggered.

[0031] Process 100 may include cell detection / measurement and timing / frequency (T / F) tracking process 102. Cell detection / measurement and T / F tracking process 102 may include detecting signals from a cell and performing measurements on signals transmitted by the cell. Signals transmitted by the cell may be broadcast, and the UE may detect the broadcast signals. In some embodiments, these signals may include one or more synchronization signals. The UE may measure the signals to determine one or more measurements associated with the cell, such as the cell's signal-to-noise ratio. Cell measurements can be used to determine in which cell the UE will establish a connection. The UE may further determine the timing and / or frequency of signals from the cell. For example, the UE may determine the cell's timing offset and / or frequency offset. The timing and / or frequency determined for the cell may allow the UE to detect additional signals from that cell.

[0032] Process 100 may also include a Master Information Block (MIB) acquisition phase 104. The UE may read the cell's MIB during MIB acquisition phase 104. The MIB may be included in a Synchronization Signal / Physical Broadcast Channel Block (SSB), where the UE may detect the SSB to read the MIB. The UE may utilize the cell's timing and / or frequency determined in process 102 to detect the SSB including the MIB. Based on the MIB read during MIB acquisition phase 104, the UE may determine the timing of other signals transmitted by the cell, such as the timing of the cell's System Information Block transmission.

[0033] Process 100 may also include a System Information Block Type 1 (SIB1) acquisition phase 106. During the SIB1 acquisition phase 106, the UE may detect one or more System Information Blocks (SIBs) (such as SIB1) of the cell. The UE may determine the timing of SIB1 based on the Physical Downlink Control Channel (PDCCH) transmission that schedules SIB1. SIB1 may be transmitted within a Physical Downlink Shared Channel (PDSCH) transmission, where the timing of the PDSCH transmission may be indicated by the PDCCH transmission. The UE may determine the timing of the PDSCH carrying SIB1 based on the PDCCH transmission that schedules SIB1. The UE may determine the CGI of the cell based on SIB1. For example, the UE may determine the cell identifier and the PLMN identifier of the Public Land Mobile Network (PLMN) from SIB1. The UE may determine the CGI from the cell identifier and the PLMN.

[0034] In unlicensed spectrum, a network cell can perform Listen-Before-Speak (LBT) before transmitting a signal. Specifically, before transmitting a signal on a communication channel, the cell can sense other transmissions occurring on that communication channel. For example, the cell can sense the energy level on the communication channel to verify that the channel is available for transmission. If the cell determines that the communication channel is unavailable based on the LBT (referred to as an LBT failure), the cell may not transmit a signal on the communication channel at this time. These LBT failures can cause problems with the CGI readout process 100, where signals from the CGI readout process 100 from the cell may not be provided to the cell. For example, the cell may not provide signals (such as synchronization signals and / or MIBs) for the cell detection / measurement and T / F tracking process 102 and / or MIB acquisition phase 104 based on an LBT failure occurring on an SSB transmission. Furthermore, the cell may not provide signals (such as PDCCH transmissions scheduling SIB1, PDSCHs as carriers, and / or MIBs) for the SIB1 acquisition phase 106.

[0035] Detailed UE behavior for NR-U CGI reads is not addressed in current networks. LBT failures should be carefully considered in CGI read functionality, as consistent LBT failures can ultimately cause the entire CGI read process to fail. For example, regarding... Figure 1 The described LBT fault can cause CGI read process 100 to fail. This situation, where an LBT fault occurs during CGI read process 100, is not currently addressed in the network.

[0036] In the traditional 3GPP Technical Specification (TS) 38.133 (3GPP Organization Partners (2020-09) 3GPP; Technical Specification Group Radio Access Networks; NR; Requirements for Supporting Radio Resource Management (Revision 16) (3GPP TS 38.133 V.16.5.0)), the traditional NR CGI read requirement is defined as:

[0037] 9.11.2 CGI Identification of NR Cells with Autonomous Gap

[0038] When reporting a CGI, the UE should identify and report the CGI of a known NR target cell. Only one cell is provided for identifying the CGI to a UE with cellForWhichToReportCGI. The UE can perform autonomous gaps in both downlink reception and uplink transmission to receive the Master Information Block (MIB) and SIB1 messages in accordance with Clause 5.5.3 of TS 38.331[2]. Note that if useAutonomousGaps is set to false, the UE is not required to use autonomous gaps. If autonomous gaps are used for measurement for the purpose of reporting a CGI, the UE should be able to identify new CGIs of NR cells within the following range, regardless of whether discontinuous reception (DRX) is used or whether a secondary cell (SCell) is configured:

[0039] T identify_CGI =(T MIB +T SIB1 milliseconds (ms)

[0040] in:

[0041] T MIB This is the time period used to collect MIB messages. (T) MIB =6*T SMTC ms is used for the target cell carrier frequency in frequency range 1 (FR1), and T MIB =

[25] *T SMTC ms is used for the target cell carrier frequency in frequency range 2 (FR2).

[0042] T SIB1 This is the time period used to collect SIB1 messages. T SIB1 =6*T SMTC ms.

[0043] Where T SMTC It is the period at which the Synchronization Signal / Physical Broadcast Channel Block Measurement Time Configuration (SMTC) timing is configured for the target cell carrier.

[0044] When DRX is not used and when either of the DRX cycles specified in TS 38.331[2] is used, in T identify_CGI The requirements for CGI identification of NR cells are applicable.

[0045] Given that the cell conditions have been defined as follows, and that it successfully receives downlink (DL) reference signals (RS) and channel responses,

[0046] In this requirement, the community is known in the following situations:

[0047] - During the last 5 seconds of FR1 or 3 seconds of FR2 before receiving the report CGI command:

[0048] -The UE has sent a valid Layer 3 Reference Signal Received Power (L3-RSRP) measurement report with the SSB index of the target cell, and

[0049] - During MIB decoding, at least the reported Synchronization Signal / Physical Broadcast Channel Block (SSB) remains detectable according to the cell identification conditions specified in Clause 9.2 or 9.3 of TS 38.133, and

[0050] - During SIB1 decoding, the SSB used for MIB decoding remains detectable according to the cell identification conditions specified in Clause 9.2 or 9.3 of TS 38.133, and

[0051] - During MIB decoding, the SSB used for MIB decoding remains detectable with a signal-to-noise ratio (SNR) ≥ [-3] dB.

[0052] - During SIB1 decoding, the Physical Downlink Shared Channel (PDSCH) used for SIB1 decoding remains detectable with an SNR ≥ [-3] dB.

[0053] However, this introduces problems for MIB and SIB1 reading, such as Figure 2 shown. Specifically, Figure 2 A CGI reading process 200 according to some embodiments is shown. The CGI reading process 200 may include one or more features of the CGI reading process 100. Figure 1 Specifically, the cell detection / measurement and T / F tracking process 202 may include the cell detection / measurement and T / F tracking process 102 ( Figure 1 The MIB acquisition phase 204 may include the MIB acquisition phase 104 (characteristics of MIB acquisition phase 104). Figure 1 The features of SIB1 acquisition phase 206 include SIB1 acquisition phase 106 ( Figure 1 ) characteristics.

[0054] like Figure 2 As shown by the dashed ellipse in the diagram, the UE behavior for LBT faults in a portion of the CGI read procedure 200 is not previously defined. Specifically, for signals related to cell detection / measurement and T / F tracking procedures 202, faults in the LBT can be resolved by using cell detection with the LBT. However, LBT faults for signals related to MIB acquisition phase 204 and SIB1 acquisition phase 206 are not addressed in conventional implementations. Because the operation of MIB acquisition phase 204 and SIB1 acquisition phase 206 is not defined for LBT faults, the CGI read procedure 200 may fail when an LBT fault occurs for signals related to MIB acquisition phase 204 and / or SIB1 acquisition phase 206.

[0055] Figure 3 An example of an exemplary timing arrangement 300 according to some implementation schemes is shown. Specifically, timing arrangement 300 illustrates a scenario where the UE may expect to receive a CGI read procedure (such as CGI read procedure 100). Figure 1 ) and / or CGI read process 200 ( Figure 2 Exemplary timings for related launches are provided. Each of these timings can be scheduled for a specific launch. For example, in some embodiments, a first timing 302 can be scheduled for an SSB. Furthermore, a second timing 304 can be scheduled for a PDCCH to be launched on a resource element of a Control Resource Set (CORESET), and a third timing 306 can be scheduled for a PDSCH. The scheduling of timings can be repeated, with a fourth timing 308 scheduled for an SSB, a fifth timing 310 scheduled for a CORESET launch (which may also be referred to as a "PDCCH launch" or simply "PDCCH"), and in some embodiments, a sixth timing 312 scheduled for a PDSCH.

[0056] Based on scheduling, each of these timings (or portions thereof) can be used to transmit signals used during CGI readout. For example, an SSB capable of being transmitted in the first timing 302 and / or the fourth timing 308 can be used for cell detection / measurement and T / F tracking procedures (such as cell detection / measurement and T / F tracking procedure 102). Figure 1 ) and / or cell detection / measurement and T / F tracking process 202 ( Figure 2 )) and / or MIB acquisition phase (such as MIB acquisition phase 104 ( Figure 1 ) and / or MIB acquisition phase 204 ( Figure 2 CORESET launches capable of being launched in the second timing 304 and / or the fifth timing 310 can be used in the MIB acquisition phase and / or the SIB1 acquisition phase (such as SIB1 acquisition phase 106). Figure 1 ) and / or SIB1 acquisition phase 206 ( Figure 2 The PDSCH that can be emitted in the third timing 306 and / or the sixth timing 312 can be used in the SIB1 acquisition phase.

[0057] Whether a scheduled transmission occurs during a given time slot can depend on the outcome of the LBT performed by the cell. Specifically, the cell may perform an LBT operation before transmission in each of these time slots. If the LBT succeeds for each of these time slots, the scheduled transmission can be transmitted in each time slot. For each of these time slots where the LBT fails, the scheduled transmission may not be transmitted in that time slot. For example, if the LBT operation in time slot 302 results in an LBT failure, the SSB may not be transmitted by the cell in time slot 302, and the SSB may be unavailable in time slot 302. Furthermore, if the LBT operation in time slot 304 results in an LBT failure, the CORESET transmission may not be transmitted by the cell in time slot 304, and the CORESET transmission may be unavailable in time slot 304. If the LBT operation in time slot 306 results in an LBT failure, the PDSCH may not be transmitted by the cell in time slot 306, and the PDSCH may be unavailable in time slot 306.

[0058] The UE performing the CGI read procedure can calculate the number of times a scheduled transmission has not been received. For example, the UE can calculate the number of times an SSB has not been received, the number of times a CORESET transmission has not been received, the number of times a PDSCH has not been received, or some combination thereof. For a transmission to be not received by the UE may mean that the transmission is unavailable at the UE. The UE can use the number of times a scheduled transmission has not been received to determine the procedure period for the CGI read procedure. While timing arrangement 300 illustrates a specific timing arrangement, it should be understood that the timing arrangement may differ in other embodiments.

[0059] Figure 4 An exemplary process cycle timing 400 for a CGI read process is shown according to some embodiments. For example, process cycle timing 400 shows a method that can be defined for a CGI read process (such as CGI read process 100). Figure 1 ) and / or CGI read process 200 ( Figure 2 An exemplary process cycle 402 is shown. Furthermore, process cycle timing 400 illustrates the components of process cycle 402.

[0060] Process cycle timing 400 illustrates an exemplary process cycle 402 that can be defined by the methods described herein. Process cycle 402 may include a basic cycle 404, and in some cases, may include an extension period 406. The basic cycle 404 can be defined and can be the minimum time period of process cycle 402. When no LBT fault occurs during the CGI read process, process cycle 402 can be set to the basic cycle 404, and therefore, at the transmit timing (such as... Figure 3 Each of the relevant transmissions scheduled within the timeframe shown (such as SSB, CORESET transmission, and / or PDSCH) is transmitted by the cell that has applied the CGI read procedure and is available at the UE performing the CGI read procedure.

[0061] The length of the extension period 406 can be variable, and can be defined based on the number of times a scheduled transmission has not yet been transmitted, and therefore is unavailable at the UE performing the CGI read procedure. For example, if no LBT failure occurs during the CGI read procedure, the extension period 406 can be set to zero, resulting in all relevant scheduled transmissions being transmitted during the times of the CGI read procedure. If an LBT failure occurs during the CGI read procedure, the length of the extension period 406 can be defined based on the number of times a relevant scheduled transmission has not been transmitted by the cell and is therefore unavailable at the UE. A non-zero extension period when an LBT failure occurs may result in a process period 402 being longer than the basic period 404, which may allow the UE performing the CGI read procedure to compensate for the LBT failure. The extension period 406 can be defined by methods described further throughout this disclosure.

[0062] The process cycle timing 400 also illustrates components that can generate process cycle 402 in some embodiments. Specifically, process cycle 402 may include a time cycle 408 for MIB reading and a time cycle 410 for SIB reading. Specifically, the time cycle 408 for MIB reading may be for the UE to read the MIB during the CGI reading process (such as during MIB acquisition phase 104). Figure 1 ) and / or MIB acquisition phase 204 ( Figure 2 The time period is defined during the CGI reading process (such as during the SIB1 acquisition phase 106). Figure 1 ) and / or SIB1 acquisition phase 206 ( Figure 2The time period 410 for SIB reading is defined during the SIB reading process. The time period 408 for MIB reading and / or the time period 410 for SIB reading can be defined as described further throughout this disclosure. In some embodiments, the process period 402 may also include a time period for cell detection / measurement and T / F tracking (such as for performing cell detection / measurement and T / F tracking process 102). Figure 1 ) and / or cell detection / measurement and T / F tracking process 202 ( Figure 2 (Time period).

[0063] In the first method of CGI reading in NR-U, the process period for CGI reading of the target NR-U cell can be implemented at the UE as T. identify_CGI_NR-U =(T MIB_NR-U +T SIB1_NR-U )ms. For example, the CGI read procedure for the target cell (such as CGI read procedure 100 ( Figure 1 ) and / or CGI read process 200 ( Figure 2 The process cycle (such as process cycle 402) Figure 4 )) can be made by T identify_CGI_NR-U =(T MIB_NR-U +T SIB1_NR-U Defined by ms. T MIB_NR-U This can be the time period for MIB readings in NR-U cells, and T SIBl_NR-U This can be the time period used for SIB1 reading. MIB_NR-U =6*T SMTC +K MIB *T SMTC T SMTC This could be the cycle of the SMTC timing. K MIB This could be the number of SMTC or SSB opportunities that are unavailable at the UE during the CGI read procedure for MIB read of the target cell. In this case, T SIB1_NR- U and 6*T SMTC The basic cycle of the process can be defined (such as the basic cycle 404). Figure 4 And K MIB *T SMTC The extension period of the process cycle can be defined (such as extension period 406). Figure 4 For example, K MIB This can be during a CGI read process (such as CGI read process 100). Figure 1 ) and / or CGI read process 200 ( Figure 2During the MIB read period, this refers to the number of times the SMTC or SSB corresponding to the MIB is unavailable at the UE. This means that if an LBT failure at the target cell causes the SMTC or SSB to be unavailable at the UE, the UE can extend its MIB read cycle during the CGI read (e.g., the time cycle 408 for MIB read). Figure 4 Therefore, the UE can determine the process cycle for the CGI read procedure based on the number of times the SSB is unavailable at the UE in these situations and the SMTC cycle during the CGI read procedure.

[0064] In some implementations, the process cycle for the CGI read procedure can have a maximum time that may be extended due to an LBT failure that occurs during the timing of the SSB. MIB ≤K MIB_MAX K MIB_MAX This can be the maximum number of SMTC cycles the UE can extend during the CGI read process due to LBT faults on the MIB. The UE can count LBT faults on the MIB (or the SSB carrying the MIB) during the MIB read phase of the CGI read to check if the total number of LBT faults on the MIB will exceed K. MIB_MAX The threshold. For example, the UE can determine the number of times an SSB scheduled for use by a UE is not transmitted by the cell and is therefore unavailable at the UE. The UE can determine whether the number of times exceeds a threshold number of times (defined as K). MIB ).

[0065] In CGI reading, the time exceeds K within the MIB acquisition phase cycle. MIB_MAX In this case, one of three options can be applied. In the first option, the UE can restart the MIB acquisition phase during CGI readings in the same NR-U target cell without interrupting the CGI reading process. For example, the UE can restart the MIB acquisition phase based on the fact that the number of times an SSB scheduled for use by the UE is unavailable at the UE exceeds a threshold number of times (such as MIB acquisition phase 104). Figure 1 ) and / or MIB acquisition phase 204 ( Figure 2 The UE can continue the CGI reading process while restarting the MIB acquisition phase.

[0066] In the second option, the UE can directly discard the CGI read procedure for this target NR-U cell and can exit the CGI read without any error indication or report a CGI read failure to the network. For example, the UE can stop the CGI read procedure based on the fact that the number of times an SSB scheduled for use by the UE is unavailable at the UE exceeds a threshold number of times. In these cases, the UE may not provide an error indication to the network or report a CGI read failure to the network.

[0067] In the third option, the UE can restart the MIB acquisition phase during CGI readings of the same NR-U target cell, but the UE can start another counter K. MIB_TOTAL (K MIB ≤K MIB_MAX ≤K MIB_TOTAL ), K MIB_TOTAL It can be a counter for all LBT faults acquired by the MIB during the CGI read cycle. Therefore, K MIB_TOTAL The counter can track LBT faults throughout the entire CGI read cycle, while K MIB A counter tracks LBT faults during a specific MIB acquisition phase. If K MIB_TOTAL Once a threshold is reached, the UE can stop and exit the CGI reading process, either without any error indication or by reporting a CGI reading failure to the network. For example, the UE can restart the MIB acquisition phase based on the determination that the number of times an SSB scheduled for use by the SSB is unavailable at the UE exceeds a threshold number of times. The UE can reset the LBT failure count on the MIB (or the SSB carrying the MIB) during the CGI reading MIB acquisition phase and restart the LBT failure count on the MIB (or the SSB carrying the MIB) during the CGI reading MIB acquisition phase. Whenever the number of times exceeds the threshold number of times, the UE can continue to restart the MIB acquisition phase and reset the counter. Furthermore, the UE can maintain a second counter for LBT failures on the MIB (or the SSB carrying the MIB) during the CGI reading MIB acquisition phase, where the second counter may not be reset when the MIB acquisition phase is restarted. The UE can exit the CGI reading process based on the determination that the second counter exceeds a second threshold number of times, where the second threshold number of times is greater than the threshold number of times the MIB acquisition phase is restarted. When the UE exits the CGI reading process, the UE may not provide any error indication to the network or report a CGI reading failure to the network.

[0068] In other implementations of the third option, the UE can restart the MIB acquisition phase if the number of times the SSB scheduled for the SSB is unavailable at the UE exceeds a threshold number of times. The UE can also count the number of times the MIB acquisition phase has been restarted and compare this count to a threshold number of MIB restarts. The UE can exit the CGI reading process based on the determination that the number of times the MIB acquisition phase has been restarted exceeds the threshold number of MIB restarts. In these cases, the UE may not provide an error indication to the network or report a CGI reading failure to the network. MIB K MIB_MAX and / or K MIB_TOTAL This can be predefined in the manual or configured from the network. Specifically, regarding the K described above... MIB K MIB_MAX and / or K MIB_TOTAL It can be predefined in the instruction manual or from the network configuration.

[0069] For the first method, it can be based on T SIB1_NR-U =6*T SMTC +K SIB1 *T SMTC The process cycle for reading the CGI of the target NR-U cell is implemented at the UE. For example, the CGI reading process for the target cell (such as CGI reading process 100) Figure 1 ) and / or CGI read process 200 ( Figure 2 The process cycle (such as process cycle 402) Figure 4 It can be based on T SIB1_NR-U =6*T SMTC +K SIB1 *T SMTC To define. K SIB1 This could be the number of times the Physical Downlink Control Channel (PDCCH) (SIB1 CORESET) or Residual Minimum System Information (RMSI) (SIB1-bearing PDSCH) is unavailable at the UE during the SIB1 acquisition phase of the SIB1 read for the target cell, or the number of times the SSB for the corresponding MIB is unavailable at the UE. In this case, T MIB_NR-U and 6*T SMTC The basic cycle of the process can be defined (such as the basic cycle 404). Figure 4 And K SIB1 *T SMTC The extension period of the process cycle can be defined (such as extension period 406). Figure 4 For example, K SIB1 This can be during a CGI read process (such as CGI read process 100). Figure 1) and / or CGI reading process ( Figure 2 The number of SMTC or SSB opportunities during which the SSB carrying the MIB, the CORESET of SIB1, and / or the PDSCH carrying the SIB1 of the target cell are unavailable at the UE. This means that if an LBT failure at the target cell causes any of the following unavailability events, the UE can extend its SIB1 read cycle during the CGI read: the SSB opportunity carrying the MIB of the target cell is unavailable at the UE (LBT failure disables SSB transmission); the CORESET of the SIB1 of the target cell (CORESET with index 0 (CORESET0)) is unavailable at the UE (LBT failure disables CORESET0 transmission); the RMSI of the target cell (PDSCH carrying SIB1) is unavailable at the UE (LBT failure disables RMSI transmission). Therefore, in these cases, the UE can extend its SIB1 read cycle based on the number of times during the SIB1 acquisition phase of SIB1 (such as SIB1 acquisition phase 106). Figure 1 ) and / or SIB1 acquisition phase 206 ( Figure 2 The number of times when the PDCCH of SIB1 is unavailable, the PDSCH carrying SIB1 is unavailable, and / or the MIB is unavailable determines the process cycle used for the CGI read procedure.

[0070] In some implementations, the CGI read process cycle can have a maximum time that may be extended due to an LBT failure during the SIB1 read process. SIB1 ≤K SIB1_MAX K SIB1_MAX This can be the maximum number of SMTC cycles that the UE can extend during the CGI read process due to any of the aforementioned SIB1 read unavailability issues. The UE can count the number of SMTC extensions during the SIB1 read phase of the CGI read to check whether the total extension caused by LBT failures on the SIB1 read will exceed K. SIB1_MAX The threshold. For example, the UE can count the number of times the PDCCH scheduling SIB1 is unavailable, the PDSCH carrying SIB1 is unavailable, and / or the MIB is unavailable during the SIB1 acquisition phase. In CGI reading, exceeding K within the SIB1 acquisition phase period. SIB1_MAX At that time, one of the five options can be used.

[0071] In the first option, the UE can restart the SIB1 acquisition phase during a CGI read in the same NR-U target cell without interrupting the CGI read process. For example, the UE can restart the SIB acquisition phase based on a threshold number of times the number of times the PDCCH scheduling SIB1, the PDSCH carrying SIB1, and / or the MIB is unavailable exceeds the threshold number (e.g., SIB1 acquisition phase 106). Figure 1 ) and / or SIB1 acquisition phase 206 ( Figure 2 The UE can continue the CGI reading process while restarting the SIB1 acquisition phase.

[0072] In the second option, the UE can restart the MIB acquisition phase during CGI readings in the same NR-U target cell without interrupting the CGI reading process. For example, the UE can restart the MIB acquisition phase based on a threshold number of times the PDCCH scheduling SIB1, the PDSCH carrying SIB1, and / or the MIB is unavailable during the SIB1 acquisition phase (e.g., MIB acquisition phase 104). Figure 1 ) and / or MIB acquisition phase 204 ( Figure 2 The UE can continue the CGI reading process while restarting the MIB acquisition phase.

[0073] In the third option, the UE can directly discard the CGI read procedure for this target NR-U cell and can exit the CGI read without any error indication or report a CGI read failure to the network. For example, the UE can stop the CGI read procedure based on the fact that the number of times the PDCCH scheduling SIB1, the PDSCH carrying SIB1, and / or the MIB is unavailable during the SIB1 acquisition phase exceeds a threshold number of times. In these cases, the UE may not provide an error indication or report a CGI read failure to the network.

[0074] In the fourth option, the UE can restart the MIB acquisition phase during CGI readings of the same NR-U target cell, but the UE can start another counter K. TOTA (K MIB_MAX +K SIB1_MAX ≤K TOTAL ), K TOTAL This could be a counter that collects all LBT faults on both MIB and SIB1 during the CGI read cycle. Therefore, K TOTAL The counter can track LBT faults throughout the entire CGI read cycle, while K SIB1 The counter tracks LBT faults during a specific SIB1 acquisition phase. If K TOTALOnce the threshold is reached, the UE can stop and exit the CGI reading process, either without any error indication or by reporting a CGI reading failure to the network. For example, the UE can restart the MIB acquisition phase (such as MIB acquisition phase 104) based on the number of times the PDCCH scheduling SIB1, the PDSCH carrying SIB1, and / or the MIB is unavailable during the SIB1 acquisition phase exceeds a threshold number of times. Figure 1 ) and / or MIB acquisition phase 204 ( Figure 2 The UE can reset the LBT fault count on both MIB and SIB1 acquisitions and restart the LBT fault count on both MIB and SIB1 acquisitions. Whenever the number of times exceeds a threshold number of times, the UE can continue to restart the MIB acquisition phase and reset the counter. Furthermore, the UE can maintain a second counter for LBT faults on both MIB and SIB1 acquisitions, where the second counter may not be reset when the MIB acquisition phase is restarted. The UE can exit the CGI reading process based on determining that the second counter exceeds a second threshold number of times, where the second threshold number of times exceeds the threshold number of times the MIB acquisition phase is restarted. When the UE exits the CGI reading process, the UE may not provide any error indication to the network or report a CGI reading fault to the network.

[0075] In other implementations of the fourth option, the UE may restart the MIB acquisition phase (such as MIB acquisition phase 104) based on the fact that the number of times the PDCCH scheduling SIB1 is unavailable, the PDSCH carrying SIB1 is unavailable, and / or the MIB is unavailable during the SIB1 acquisition phase exceeds a threshold number of times. Figure 1 ) and / or MIB acquisition phase 204 ( Figure 2 The UE can also count the number of times the MIB acquisition phase has been restarted and compare this count with a threshold number of MIB restarts. The UE can exit the CGI reading process if it determines that the number of times the MIB acquisition phase has been restarted exceeds the MIB restart threshold. In these cases, the UE may not provide an error indication to the network or report a CGI reading failure.

[0076] In the fifth option, the UE can restart the SIB1 acquisition phase during CGI readings in the same NR-U target cell, but the UE can start another counter K. SIB1_TOTAL (K SIB1 ≤K SIB1_MAX ≤K SIB1_TOTAL ), K SIB1_TOTALIt can be a counter that collects all LBT faults on SIB1 during the CGI read cycle. Therefore, K SIB1_TOTAL The counter can track LBT faults throughout the entire CGI read cycle, while K SIB1 The counter tracks LBT faults during a specific SIB1 acquisition phase. If K SIB1_TOTAL Once the threshold is reached, the UE can stop and exit the CGI reading process, either without any error indication or by reporting a CGI reading failure to the network. For example, the UE can restart the SIB1 acquisition phase based on a threshold number of times the number of times the PDCCH scheduling SIB1, the PDSCH carrying SIB1, and / or the MIB is unavailable exceeds the threshold number of times (e.g., SIB1 acquisition phase 106). Figure 1 ) and / or SIB1 acquisition phase 206 ( Figure 2 The UE can reset the LBT fault count on both the MIB and SIB1 acquisition stages and restart the LBT fault count on both stages. Whenever the number of times exceeds a threshold number of times, the UE can restart the SIB1 acquisition stage and reset the counter. Additionally, the UE can maintain a second counter for LBT faults on both the MIB and SIB1 acquisition stages, where the second counter does not need to be reset when the SIB1 acquisition stage is restarted. The UE can exit the CGI reading process based on determining that the second counter exceeds a second threshold number of times, where the second threshold number of times exceeds the threshold number of times the SIB1 acquisition stage can be restarted. When the UE exits the CGI reading process, it may not provide any error indication to the network or report a CGI reading fault to the network.

[0077] In other implementations of the fifth option, the UE may restart the SIB1 acquisition phase based on the number of times the PDCCH scheduling SIB1 is unavailable, the PDSCH carrying SIB1 is unavailable, and / or the MIB is unavailable during the SIB1 acquisition phase exceeding a threshold number of times (such as SIB1 acquisition phase 106). Figure 1 ) and / or SIB1 acquisition phase 206 ( Figure 2 The UE can also count the number of times the SIB1 acquisition phase has been restarted and compare this count with a threshold number of SIB1 restarts. The UE can exit the CGI reading process if it determines that the number of restarts exceeds the SIB1 restart threshold. In these cases, the UE may not provide an error indication or report a CGI reading failure to the network. SIB1 K SIB1_MAX K SIB1_TOTAL KTOTAL This can be predefined in the manual or configured from the network. Specifically, regarding the K described above... MIB K MIB_MAX and / or K MIB_TOTAL It can be predefined in the instruction manual or from the network configuration.

[0078] The second method for CGI reading in NR-U presents a general approach for MIB / SIB1. The process cycle for CGI reading of the target NR-U cell can be implemented at the UE as T. identify_CGI_NR-U =(T MIB_NR-U +T SIBl_NR-U +K CGI *T SMTC )ms. For example, the CGI read procedure for the target cell (such as CGI read procedure 100 ( Figure 1 ) and / or CGI read process 200 ( Figure 2 The process cycle (such as process cycle 402) Figure 4 )) can be made by T identify_CGI_NR-U =(T MIB_NR-U +T SIBl_NR-U +K CGI *T SMTC Defined by ms. T MIB_NR-U This can be the time period for MIB readings in NR-U cells, and T SIBl_NR-U This can be the time period used for SIB1 reading. K CGI This could be the number of times during the SIB1 acquisition phase for the target cell, the PDCCH (CORESET of SIB1) or RMSI (PDSCH carrying SIB1), or the SMTC timing when the corresponding MIB's SSB is unavailable at the UE. In this case, T MIB_NR-U and T SIBl_NR-U The basic cycle of the process can be defined (such as the basic cycle 404). Figure 4 And K CGI *T SMTC The extension period of the process cycle can be defined (such as extension period 406). Figure 4This means that if an LBT failure at the target cell causes any of the following unavailability events, the UE can extend its CGI read cycle: the SSB timing for the MIB carrying the target cell is unavailable at the UE (LBT failure disables SSB transmission); the CORESET (CORESET0) for SIB1 of the target cell is unavailable at the UE (LBT failure disables CORESET0 transmission); or the RMSI (PDSCH carrying SIB1) of the target cell is unavailable at the UE (LBT failure disables RMSI transmission). Therefore, in these cases, the UE can extend its CGI read cycle based on the unavailability of SSB during the CGI read process, during the SIB1 acquisition phase for SIB1 (such as SIB1 acquisition phase 106). Figure 1 ) and / or SIB1 acquisition phase 206 ( Figure 2 The number of times when the PDCCH of SIB1 is unavailable, the PDSCH carrying SIB1 is unavailable, and / or the MIB is unavailable determines the process cycle used for the CGI read procedure.

[0079] In some implementations, the process cycle for the CGI read procedure can have a maximum duration that may be extended due to LBT failures. CGI ≤K CGI_MAX K CGI_MAX This can be the maximum number of SMTC cycles that the UE can extend during CGI reading due to any of the aforementioned unavailability. The UE can extend the SMTC period during the MIB and SIB1 reading phases of the CGI reading (e.g., MIB acquisition phase 104 respectively). Figure 1 ) and / or MIB acquisition phase 204 ( Figure 2 ), and SIB1 acquisition phase 106 ( Figure 1 ) and / or SIB1 acquisition phase 206 ( Figure 2 The amount of SMTC extension is counted to check whether the total extension caused by LBT failures on MIB and SIB1 reads will exceed K. CGI_MAX The threshold. For example, the UE can determine that the number of times the SSB is unavailable during the CGI read process, the PDCCH scheduling SIB1 is unavailable during the SIB1 acquisition phase for SIB1, the PDSCH carrying SIB1 is unavailable, and / or the MIB is unavailable exceeds a threshold number of times (defined as K). CGI_MAX ).

[0080] More than K in the entire CGI read cycle CGI_MAXIn this case, one of three options can be applied. In the first option, the UE can restart the MIB acquisition phase during the CGI read of the same NR-U target cell (because the MIB read is the first phase of the CGI read), and the CGI read process can continue without interruption. For example, the UE can restart the MIB acquisition phase based on the number of times the SSB is unavailable during the CGI read process, the PDCCH scheduling SIB1 is unavailable during the SIB1 acquisition phase for SIB1 is unavailable, the PDSCH carrying SIB1 is unavailable, and / or the MIB is unavailable exceeds a threshold number of times (such as MIB acquisition phase 104). Figure 1 ) and / or MIB acquisition phase 204 ( Figure 2 The UE can continue the CGI reading process while restarting the MIB acquisition phase.

[0081] In the second option, the UE can directly discard the CGI read procedure for this target NR-U cell and can exit the CGI read without any error indication or report a CGI read failure to the network. For example, the UE can stop the CGI read procedure based on the number of times the SSB is unavailable during the CGI read procedure, the PDCCH scheduling SIB1 is unavailable during the SIB1 acquisition phase for SIB1 is unavailable, the PDSCH carrying SIB1 is unavailable, and / or the MIB is unavailable exceeds a threshold number of times. In these cases, the UE may not provide an error indication to the network or report a CGI read failure to the network.

[0082] In the third option, the UE can restart the MIB acquisition phase during CGI readings of the same NR-U target cell, but the UE can start another counter K. TOTA (K CGI ≤K CGI_MAX ≤K CGI_TOTAL ), K CGI_TOTAL It can be a counter for all LBT faults acquired by MIB and SIB1 during the CGI read cycle. Therefore, K CGI_TOTAL The counter can track LBT faults throughout the entire CGI read cycle, while K CGI The counter tracks LBT faults during specific MIB and SIB1 acquisition phases. If K CGI_TOTALUpon reaching a threshold, the UE will stop and exit the CGI reading process. It can exit CGI reading without any error indication or report a CGI reading failure to the network. For example, the UE can restart the MIB acquisition phase based on the number of times the SSB is unavailable during the CGI reading process, the PDCCH scheduling SIB1 is unavailable during the SIB1 acquisition phase of SIB1, the PDSCH carrying SIB1 is unavailable, and / or the MIB is unavailable exceeds a threshold number of times. The UE can reset the LBT failure count on the MIB (or the SSB carrying the MIB) during the CGI reading MIB acquisition phase and restart the LBT failure count on the MIB (or the SSB carrying the MIB) during the CGI reading MIB acquisition phase. Whenever the number of times exceeds the threshold number of times, the UE can continue to restart the MIB acquisition phase and reset the counter. Furthermore, the UE can maintain a second counter for LBT failures on the MIB (or the SSB carrying the MIB) during the MIB and SIB1 acquisition MIB reading phases, where the second counter may not be reset when MIB acquisition is restarted. The UE can exit the CGI reading process based on a second threshold number of times a second counter exceeds a threshold number of times the MIB acquisition phase can be restarted. When the UE exits the CGI reading process, it may not provide any error indication to the network or report a CGI reading failure.

[0083] In other implementations of the third option, the UE may restart the MIB acquisition phase based on the number of times the number of times the SSB is unavailable during the CGI read process, the PDCCH scheduling SIB1 is unavailable during the SIB1 acquisition phase for SIB1 is unavailable, the PDSCH carrying SIB1 is unavailable, and / or the MIB is unavailable exceeds a threshold number of times the MIB acquisition phase has been restarted. The UE may also count the number of times the MIB acquisition phase has been restarted and compare this number to a threshold number of MIB restarts. The UE may exit the CGI read process based on the determination that the number of times the MIB acquisition phase has been restarted exceeds the MIB restart threshold number. In these cases, the UE may not provide an error indication to the network or report a CGI read failure to the network. CGI K CGI_MAX K CGI_TOTAL This can be predefined in the manual or configured from the network. Specifically, regarding the K described above... MIB K MIB_MAX and / or K MIB_TOTAL It can be predefined in the instruction manual or from the network configuration.

[0084] The CGI reporting method in NR-U is described below. Specifically, considering possible LBT failures, a CGI reporting delay can be defined for CGI reporting. The traditional CGI reporting process timeline (TS38.133) is as follows:

[0085] 9.11.3 CGI report delay

[0086] CGI report delay is defined as the time between the command that triggers the CGI report and the point at which the UE begins transmitting measurement reports via the air interface. This requirement assumes that the measurement report is not delayed by other Radio Resource Control (RRC) signaling on the Dedicated Control Channel (DCCH). This measurement report delay excludes the 2×TTI delay caused when the measurement report is inserted into the uplink DCCH Transmit Time Interval (TTI). DCCH The delay uncertainty is excluded. This measurement report delay excludes any delay caused by a lack of uplink (UL) resources for the UE to send measurement reports.

[0087] The CGI reporting delay should be less than T as defined in Clause 9.11.2. identify_CGI Add the RRC process delay defined in Clause 12 of TS 38.331[2], and add a 20ms margin if the target cell is on FR2.

[0088] The proposed CGI reporting process timeline for the NR-U target cell can be as follows (NR-U only on FR1 in Rel-16). The CGI reporting delay can be less than T defined in Method 1 or 2 for CGI reads in NR-U. identify_CGI_NR-U In addition to the RRC procedure delay defined in Clause 12 of TS 38.331, and the delay until successful transmission of the report caused by "no UL resources available for the UE to transmit the CGI report on it" and "all delays due to UL LBT failure". For example, this can be based on the CGI read procedure (such as CGI read procedure 100). Figure 1 ) and / or CGI read process 200 ( Figure 2 The CGI reporting delay can be determined by the number of times the SSB, PDCCH, or PDSCH is unavailable during the reporting period. Additionally, the CGI reporting delay can be determined based on delays caused by ULLBT failures, where a ULLBT failure may be caused by the UE performing an LBT operation to transmit a CGI report and determining that the communication channel used to transmit the CGI report is unavailable.

[0089] Figure 5An exemplary signaling diagram 500 illustrating CGI reporting delays according to some embodiments is shown. Specifically, signaling diagram 500 illustrates a CGI reporting delay 502 that can be generated by the methods described herein. Signaling diagram 500 illustrates transmissions exchanged between network 504, target cell 506, and UE 508 according to some embodiments.

[0090] Signaling diagram 500 includes a report configuration message 510 transmitted from network 504 to UE 508. The report configuration message 510 can define one or more reports that will be provided by UE 508 to network 504. For example, the report configuration message 510 can define that UE 508 will provide CGI reports to network 504. The report configuration message 510 can further define which cells will be included in the CGI reports, the triggering of CGI reports (such as periodic reports or reports based on the occurrence of defined events), or some combination thereof. The report configuration message 510 can configure UE 508 to provide CGI reports to the network.

[0091] Signaling diagram 500 includes trigger detection 512. Specifically, UE 508 can detect the trigger defined by the report configuration message 510. Detection of the configuration by UE 508 can cause UE 508 to initiate a CGI read procedure (such as CGI read procedure 100). Figure 1 ) and / or CGI read process 200 ( Figure 2 )).

[0092] During the CGI read process, there may be one or more opportunities for the transmission of SSB, PDCCH, and / or PDSCH (such as regarding...). Figure 3 The described timings are as follows: SSB timing 514, PDCCH timing 516, and PDSCH timing 518, respectively. SSB timing 514, PDCCH timing 516, and PDSCH timing may include SMTC or SSB timings. Target cell 506 may determine whether to transmit within each of these timings based on the LBT procedure. For example, if the LBT procedure for a timing performed by target cell 506 indicates a pass, then target cell 506 may transmit the corresponding transmission within that timing. If the LBT procedure for a timing performed by target cell 506 indicates a fault, then target cell 506 may not transmit the corresponding transmission within that timing.

[0093] UE 508 can receive transmissions transmitted by target cell 506 during SSB timing 514, PDCCH timing 516, and / or PDSCH timing 518. UE 508 can determine the CGI of target cell 506 based on the transmissions received from target cell 506. In the event that target cell 506 fails to transmit due to LBT failure, the UE can count the number of timings during which a transmission has not yet been transmitted. According to the methods described herein, CGI reporting delay 502 can be determined based on the number of timings during which a transmission has not yet been transmitted in some embodiments. In some embodiments, target cell 506 can determine CGI reporting delay 502 based on the number of timings during which target cell 506 has not transmitted a transmission, and / or UE 508 can determine CGI reporting delay 502 based on the number of timings during which UE 508 does not receive a transmission.

[0094] Signaling diagram 500 may also include measurement report transmission 520. Specifically, UE 508 may transmit a measurement report to network 504 in measurement report transmission 520. This measurement report may include the result of a CGI read procedure, which may be the CGI of target cell 506. CGI report delay 502 may be extended from the time of detection of trigger 512 to the time of measurement report transmission 520. For example, measurement report transmission 520 may be reported to network 504 when CGI report delay 502 expires.

[0095] If the UE reports CGI and the waiting time exceeds the threshold T report_MAX If so, one of three options can be applied. In the first option, the UE can restart the CGI read process from the MIB and discard the local CGI report. For example, the UE can determine that the CGI report delay (such as CGI report delay 502) exceeds a threshold T. report_MAX To restart the CGI read process (such as CGI read process 100) Figure 1 ) and / or CGI read process 200 ( Figure 2 In these cases, the UE may not send a CGI report (e.g., the UE may not send a measurement report transmission 520).

[0096] In the second option, the UE can wait until available UL resources for CGI reporting are available. For example, the UE can wait until the LBT process for transmitting the CGI report (such as via measurement report transmission 520) to the network (such as network 504) is completed to transmit the CGI report. Therefore, CGI report delays (such as CGI report delay 502) may be extended until the LBT process is completed for the UE to transmit the CGI report to the network.

[0097] In the third option, the UE can wait until available UL resources for CGI reporting are obtained, and can also indicate a timeout flag to the network along with the CGI report. For example, the UE can wait until the LBT process for transmitting the CGI report (such as via measurement report transmission 520) to the network (such as network 504) passes to transmit the CGI report. Therefore, a CGI report delay (such as CGI report delay 502) may be extended until the LBT process passes for the UE to transmit the CGI report to the network. Additionally, the UE can include a timeout flag in the CGI report to the network. This timeout flag can indicate that the CGI report delay exceeds a threshold T. report_MAX Threshold T report_MAX It can be predefined in the instruction manual or from the network configuration.

[0098] Figure 6 An exemplary process 600 for determining the process cycle of a CGI read process is shown according to some embodiments. Specifically, process 600 may include determining the process cycle for a CGI read process (such as CGI read process 100). Figure 1 ) and / or CGI read process 200 ( Figure 2 The process cycle (such as process cycle 402) Figure 4 Process 600 can be handled by the UE (such as UE 1000). Figure 10 ))implement.

[0099] Process 600 may include determining the number of timings at 602. Specifically, the UE may determine the number of timings scheduled for transmissions from the target cell that were not received during the CGI read procedure (e.g., unavailable at the UE). Transmissions that can be scheduled in timings may include SSB transmissions, PDCCH transmissions, PDSCH transmissions, or some combination thereof. The determination of the number of timings may be performed according to any of the methods for determining the number of timings where transmissions are unavailable at the UE as described throughout this disclosure.

[0100] Process 600 may further include determining at 604 that the number of times exceeds a threshold. Specifically, the UE may determine that the number of times determined at 602 exceeds the threshold. Determining that the number of times exceeds the threshold may be performed according to any of the methods for determining that the number of times exceeds the threshold as described throughout this disclosure. In some embodiments, 604 may be omitted.

[0101] Process 600 may also include restarting the MIB acquisition phase or the SIB1 acquisition phase at 606. Specifically, the UE may restart the MIB acquisition phase (such as MIB acquisition phase 104) based on the number of times the timing is determined at 604 exceeding a threshold. Figure 1 ) and / or MIB acquisition phase 204 ( Figure 2)) or SIB1 acquisition phase (such as SIB1 acquisition phase 106 ( Figure 1 ) and / or SIB1 acquisition phase 206 ( Figure 2 The restart of the MIB acquisition phase or the SIB1 acquisition phase can be performed according to any of the methods for restarting the MIB acquisition phase or the SIB1 acquisition phase as described throughout this disclosure. Furthermore, the count of the number of opportunities can be reset according to the restart of the MIB acquisition phase or the SIB1 acquisition phase as described throughout this disclosure. In some embodiments, 606 may be omitted.

[0102] Process 600 may further include determining a second number of timings at 608. Specifically, the UE may determine a second number of timings scheduled for transmissions from the target cell that were not received during the CGI read procedure (e.g., unavailable at the UE). Transmissions that can be scheduled in timings may include SSB transmissions, PDCCH transmissions, PDSCH transmissions, or some combination thereof. The determination of the second number of timings may be performed according to any of the methods for determining the number of timings where a transmission is unavailable at the UE as described throughout this disclosure. In some embodiments, 608 may be omitted.

[0103] Process 600 may further include determining at 610 that a second quantity of timing exceeds a second threshold. The second quantity of timing may not be reset when the MIB acquisition phase or SIB1 acquisition is restarted. Furthermore, the second threshold may be greater than the threshold used to restart the MIB acquisition phase or SIB1 acquisition phase. Determining that the second quantity of timing exceeds the second threshold may be performed according to any of the methods for determining that the quantity of timing exceeds the threshold as described throughout this disclosure. In some embodiments, 610 may be omitted.

[0104] Process 600 may further include exiting the CGI reading process or reporting a CGI reading failure at 612. Specifically, the UE may exit the CGI reading process or report a CGI reading failure based on a second quantity exceeding a second threshold at a time determined at 610. Process 600 may terminate in response to exiting the CGI reading process, and in these cases, 614 and 616 may be omitted. Exiting the CGI reading process or reporting a CGI reading failure may be performed according to any of the methods for exiting the CGI reading process or reporting a CGI reading failure as described throughout this disclosure. In some embodiments, 612 may be omitted.

[0105] Process 600 may further include determining a process period at 614. Specifically, the UE may determine the process period based on the number of opportunities determined at 602. The determination of the process period based on the number of opportunities may be performed according to any of the methods for determining the process period based on the number of opportunities as described throughout this disclosure.

[0106] Process 600 may further include using a process cycle to perform the CGI reading process at 616. Specifically, the UE may use the process cycle determined at 614 to perform the CGI reading process. The use of a process cycle for the CGI reading process may be performed according to any of the methods for using a process cycle for the CGI reading process described throughout this disclosure.

[0107] Figure 7 An exemplary process 700 for determining the process cycle of a CGI read process is shown according to some embodiments. Specifically, process 700 may include determining the process cycle for a CGI read process (such as CGI read process 100). Figure 1 ) and / or CGI read process 200 ( Figure 2 The process cycle (such as process cycle 402) Figure 4 Process 700 can be handled by the UE (such as UE 1000). Figure 10 ))implement.

[0108] Process 700 may include determining a time period for MIB reading at 702. Specifically, the UE may determine the time period for MIB reading based on the number of times the SSB is unavailable during the CGI reading process. The time period for MIB reading may be determined according to any of the methods for determining the time period for MIB reading described throughout this disclosure.

[0109] Process 700 may include determining the time period for SIB reading at 704. Specifically, the UE may determine the time period for SIB reading based on the number of times during the SIB1 acquisition phase for SIB1 that the PDCCH of SIB1 is unavailable, the PDSCH carrying SIB1 is unavailable, or the MIB is unavailable. The time period for SIB reading may be determined according to any of the methods for determining the time period for SIB reading described throughout this disclosure.

[0110] Process 700 may include determining the number of times at 706. Specifically, the UE may determine the number of times the SSB is unavailable during the CGI read process, the number of times the PDCCH scheduling SIB1 is unavailable during the SIB1 acquisition phase for SIB1, the number of times the PDSCH carrying SIB1 is unavailable, or the MIB is unavailable, or some combination thereof. The number of times may be determined according to any of the methods described throughout this disclosure for determining the number of times in which transmission is unavailable at the UE. In some embodiments, 706 may be omitted.

[0111] Process 700 may include determining at 708 that the number of times an event exceeds a threshold. Specifically, the UE may determine at 706 that the number of times an event exceeds the threshold. Determining that the number of times an event exceeds the threshold may be performed according to any of the methods for determining that the number of times an event exceeds the threshold as described throughout this disclosure. In some embodiments, 708 may be omitted.

[0112] Process 700 may include restarting the MIB acquisition phase or the SIB acquisition phase at 710. Specifically, the UE may restart the MIB acquisition phase (such as MIB acquisition phase 104) based on the number of times a threshold is exceeded at 708. Figure 1 ) and / or MIB acquisition phase 204 ( Figure 2 )) or SIB1 acquisition phase (such as SIB1 acquisition phase 106 ( Figure 1 ) and / or SIB1 acquisition phase 206 ( Figure 2 The restart of the MIB acquisition phase or the SIB1 acquisition phase can be performed according to any of the methods for restarting the MIB acquisition phase or the SIB1 acquisition phase as described throughout this disclosure. Furthermore, the count of the number of opportunities can be reset according to the restart of the MIB acquisition phase or the SIB1 acquisition phase as described throughout this disclosure. In some embodiments, 710 may be omitted.

[0113] Process 700 may further include determining a second number of timings at 712. Specifically, the UE may determine a second number of timings scheduled for transmissions from the target cell that were not received during the CGI read procedure (e.g., unavailable at the UE). Transmissions that can be scheduled in timings may include SSB transmissions, PDCCH transmissions, PDSCH transmissions, or some combination thereof. The determination of the second number of timings may be performed according to any of the methods for determining the number of timings where a transmission is unavailable at the UE as described throughout this disclosure. In some embodiments, 712 may be omitted.

[0114] Process 700 may further include determining at 714 that a second quantity of timing exceeds a second threshold. The second quantity of timing may not be reset when the MIB acquisition phase or SIB1 acquisition is restarted. Furthermore, the second threshold may be greater than the threshold used to restart the MIB acquisition phase or SIB1 acquisition phase. Determining that the second quantity of timing exceeds the second threshold may be performed according to any of the methods for determining that the quantity of timing exceeds the threshold as described throughout this disclosure. In some embodiments, 714 may be omitted.

[0115] Process 700 may further include exiting the CGI reading process or reporting a CGI reading failure at 716. Specifically, the UE may exit the CGI reading process or report a CGI reading failure based on a second quantity exceeding a second threshold at a time determined at 714. Process 700 may terminate in response to exiting the CGI reading process, and in these cases, 716 and 718 may be omitted. Exiting the CGI reading process or reporting a CGI reading failure may be performed according to any of the methods for exiting the CGI reading process or reporting a CGI reading failure as described throughout this disclosure. In some embodiments, 716 may be omitted.

[0116] Process 700 may further include determining a process period at 718. Specifically, the UE may determine the process period based on a determined time period for MIB reading determined at 702 and a determined time period for SIB reading determined at 704. The process period may be determined according to any of the methods for determining the process period described throughout this disclosure.

[0117] Figure 8 An exemplary process 800 for performing a CGI read and report process according to some embodiments is shown. Specifically, process 800 may include determining the process for the CGI read process (such as CGI read process 100). Figure 1 ) and / or CGI read process 200 ( Figure 2 The process cycle (such as process cycle 402) Figure 4 In addition, process 800 may include reporting measurement reports (such as in measurement report emission 520). Figure 5 The process 800 can be handled by the UE (such as UE1000). Figure 10 ))implement.

[0118] Process 800 may include identifying a trigger in 802. Specifically, the UE may identify a trigger of a CGI report associated with a CGI reading process. The trigger may be identified according to any of the methods for identifying or detecting triggers described throughout this disclosure. In some embodiments, 802 may be omitted.

[0119] Process 800 may include determining the number of timings at 804. Specifically, the UE may determine the number of timings scheduled for transmissions from the target cell that were not received during the CGI read procedure (e.g., unavailable at the UE). Transmissions that can be scheduled in timings may include SSB transmissions, PDCCH transmissions, PDSCH transmissions, or some combination thereof. The determination of the number of timings may be performed according to any of the methods for determining the number of timings where transmissions are unavailable at the UE as described throughout this disclosure.

[0120] Process 800 may include determining a process period at 806. Specifically, the UE may determine the process period based on the number of times determined at 804. The process period may be determined according to any of the methods for determining the process period described throughout this disclosure.

[0121] Process 800 may include performing a CGI reading process using a process cycle at 808. Specifically, the UE may perform the CGI reading process using a process cycle determined at 806. The CGI reading process using a process cycle may be performed according to any of the methods for using a process cycle for the CGI reading process described throughout this disclosure.

[0122] Process 800 may include determining, at 810, a delay due to a UL LBT failure. Specifically, the UE may determine a delay due to a UL LBT failure on a communication channel used to report measurement reports. The delay due to a UL LBT failure may be determined according to any of the methods described throughout this disclosure for determining a delay due to a UL LBT failure. In some embodiments, 810 may be omitted.

[0123] Process 800 may include determining a CGI reporting delay at 812. Specifically, the UE may determine the CGI reporting delay based on the number of times determined at 804 and / or the delay due to a UL LBT failure determined at 810. The CGI reporting delay may be determined according to any of the methods for determining CGI reporting delay described throughout this disclosure.

[0124] Process 800 may include reporting a measurement report in 814. Specifically, the UE may transmit a measurement report to the network, wherein the measurement report includes the results of the CGI reporting process in 808. The measurement report may be reported according to any of the methods for reporting and / or providing measurement reports described throughout this disclosure.

[0125] Figure 9 An exemplary beamforming circuit 900 according to some embodiments is shown. The beamforming circuit 900 may include a first antenna panel, namely panel 1 904, and a second antenna panel, namely panel 2 908. Each antenna panel may include multiple antenna elements. Other embodiments may include other numbers of antenna panels.

[0126] The digital beamforming (BF) component 928 can be derived from, for example, a baseband processor (e.g., Figure 10 The baseband processor 1004A receives the input baseband (BB) signal. The digital BF component 928 can rely on complex weights to precode the BB signal and provide beamformed BB signals to the parallel radio frequency (RF) chains 920 / 924.

[0127] Each RF chain 920 / 924 may include a digital-to-analog converter that converts the BB signal into the analog domain; a mixer that mixes the baseband signal into an RF signal; and a power amplifier that amplifies the RF signal for transmission.

[0128] The RF signal can be provided to analog beamforming components 912 / 916, which can further apply beamforming by providing a phase shift in the analog domain. The RF signal can then be provided to antenna panels 904 / 908 for transmission.

[0129] In some implementations, beamforming may be performed only in the digital domain or only in the analog domain, instead of the hybrid beamforming shown herein.

[0130] In various implementations, control circuitry residing in the baseband processor can provide BF weights to the analog / digital BF components to provide a transmission beam at the corresponding antenna panel. These BF weights can be determined by the control circuitry to provide directional allocation of the serving cell as described herein. In some implementations, the BF components and antenna panels can operate together to provide a dynamic phased array capable of guiding the beam in a desired direction.

[0131] Figure 10 An example of an exemplary UE 1000 according to some implementations is shown. The UE 1000 can be any mobile or non-mobile computing device, such as a mobile phone, computer, tablet, industrial wireless sensors (e.g., microphones, carbon dioxide sensors, pressure sensors, humidity sensors, thermometers, motion sensors, accelerometers, laser scanners, fluid level sensors, stock sensors, voltmeters / ammeters, actuators, etc.), video surveillance / monitoring devices (e.g., cameras, camcorders, etc.), wearable devices (e.g., smartwatches), and loosely coupled IoT devices. In some implementations, the UE 1000 can be a RedCap UE or an NR-Light UE.

[0132] UE 1000 may include a processor 1004, RF interface circuitry 1008, memory / storage device 1012, user interface 1016, sensor 1020, drive circuitry 1022, power management integrated circuit (PMIC) 1024, antenna structure 1026, and battery 1028. The components of UE 1000 may be implemented as integrated circuits (ICs), portions of integrated circuits, discrete electronic devices or other modules, logic components, hardware, software, firmware, or combinations thereof. Figure 10 The block diagram is intended to show a high-level view of some of the components of the UE 1000. However, some of the components shown may be omitted, additional components may be present, and different arrangements of the components shown may occur in other specific implementations.

[0133] The components of UE 1000 can be coupled to various other components via one or more interconnects 1032, which can represent any type of interface, input / output, bus (local, system, or extension), transmission line, trace, optical connector, etc., allowing various circuit components (on common or different chips or chipsets) to interact with each other.

[0134] Processor 1004 may include processor circuitry such as baseband processor circuitry (BB) 1004A, central processing unit circuitry (CPU) 1004B, and graphics processing unit circuitry (GPU) 1004C. Processor 1004 may include any type of circuitry or processor circuitry that executes or otherwise operates computer-executable instructions (such as program code, software modules, or functional processes from memory / storage device 1012) to cause UE 1000 to perform the operations described herein.

[0135] In some implementations, the baseband processor circuit 1004A can access the communication protocol stack 1036 in the memory / storage device 1012 to communicate over a 3GPP-compliant network. Generally, the baseband processor circuit 1004A can access the communication protocol stack to perform the following operations: user plane functions at the PHY, MAC, RLC, PDCP, SDAP, and PDU layers; and control plane functions at the PHY, MAC, RLC, PDCP, RRC, and non-access layers. In some implementations, PHY layer operations may additionally / optionally be performed by components of the RF interface circuit 1008.

[0136] The baseband processor circuit 1004A can generate or process baseband signals or waveforms carrying information in a 3GPP-compliant network. In some implementations, the waveforms used for NR can be based on cyclic prefix OFDM (CP-OFDM) in the uplink or downlink, and Discrete Fourier Transform Extended OFDM (DFT-S-OFDM) in the uplink.

[0137] The memory / storage device 1012 may include one or more non-transitory computer-readable media, including instructions (e.g., a communication protocol stack 1036) that can be executed by one or more processors in processor 1004 to cause UE 1000 to perform the various operations described herein. The memory / storage device 1012 includes any type of volatile or non-volatile memory that can be distributed throughout UE 1000. In some embodiments, some of the memory / storage devices 1012 may be located on processor 1004 itself (e.g., L1 cache and L2 cache), while other memory / storage devices 1012 may be located external to processor 1004 but accessible via a memory interface. The memory / storage device 1012 may include any suitable volatile or non-volatile memory, such as, but not limited to, dynamic random access memory (DRAM), static random access memory (SRAM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), flash memory, solid-state memory, or any other type of memory device technology.

[0138] The RF interface circuit 1008 may include transceiver circuitry and a radio frequency front-end module (RFEM), which allows the UE 1000 to communicate with other devices via a radio access network. The RF interface circuit 1008 may include various components arranged in the transmit or receive path. These components may include, for example, switches, mixers, amplifiers, filters, synthesizer circuitry, control circuitry, etc.

[0139] In the receiving path, the RFEM can receive the radiated signal from the air interface via antenna structure 1026 and continue to filter and amplify the signal (using a low-noise amplifier). This signal can be provided to the receiver of the transceiver, which downconverts the RF signal into a baseband signal that is provided to the baseband processor of processor 1004.

[0140] In the transmission path, the transceiver's transmitter upconverts the baseband signal received from the baseband processor and provides the RF signal to the RFEM. The RFEM amplifies the RF signal using a power amplifier before it is radiated across the air interface via antenna 1026.

[0141] In various implementations, the RF interface circuit 1008 can be configured to transmit / receive signals in a manner compatible with NR access technology.

[0142] Antenna 1026 may include antenna elements for converting electrical signals into radio waves to travel through the air and for converting received radio waves back into electrical signals. These antenna elements may be arranged in one or more antenna panels. Antenna 1026 may have omnidirectional, directional, or combinations thereof antenna panels to enable beamforming and multiple-input / multiple-output communication. Antenna 1026 may include microstrip antennas, printed antennas fabricated on the surface of one or more printed circuit boards, patch antennas, phased array antennas, etc. Antenna 1026 may have one or more panels designed for a specific frequency band included in FR1 or FR2.

[0143] In some implementations, UE 1000 may include beamforming circuitry 900. Figure 9 The beamforming circuit 900 can be used to communicate with the UE 1000. In some embodiments, components of the UE 1000 and the beamforming circuit can be shared. For example, the antenna 1026 of the UE may include panel 1 904 and panel 2 908 of the beamforming circuit 900.

[0144] User interface circuitry 1016 includes various input / output (I / O) devices designed to enable users to interact with UE 1000. User interface 1016 includes input device circuitry and output device circuitry. Input device circuitry includes any physical or virtual means for accepting input, particularly including one or more physical or virtual buttons (e.g., a reset button), a physical keyboard, a keypad, a mouse, a touchpad, a touchscreen, a microphone, a scanner, a headset, etc. Output device circuitry includes any physical or virtual means for displaying information or otherwise conveying information (such as sensor readings, actuator positions, or other similar information). Output device circuitry may include any number or combination of audio or visual displays, particularly including one or more simple visual outputs / indicators (e.g., binary status indicators such as light-emitting diodes "LEDs" and multi-character visual outputs), or more complex outputs such as display devices or touchscreens (e.g., liquid crystal displays (LCDs), LED displays, quantum dot displays, projectors, etc.), wherein the output of characters, graphics, multimedia objects, etc., is generated or produced by the operation of UE 1000.

[0145] Sensor 1020 may include devices, modules, or subsystems designed to detect events or changes in their environment and transmit information about the detected events (sensor data) to other devices, modules, subsystems, etc. Examples of such sensors include, in particular: inertial measurement units including accelerometers, gyroscopes, or magnetometers; microelectromechanical systems (MEMS) or nanoelectromechanical systems (NEMS) including triaxial accelerometers, triaxial gyroscopes, or magnetometers; level sensors; flow sensors; temperature sensors (e.g., thermistors); pressure sensors; barometric pressure sensors; gravimeters; altimeters; image capture devices (e.g., cameras or lensless aperture sensors); light detection and ranging sensors; proximity sensors (e.g., infrared radiation detectors, etc.); depth sensors; ambient light sensors; ultrasonic transceivers; microphones or other similar audio capture devices; etc.

[0146] The driving circuit 1022 may include software and hardware elements for controlling specific devices embedded in, attached to, or otherwise communicatively coupled to the UE 1000. The driving circuit 1022 may include various drivers that allow other components to interact with or control various input / output (I / O) devices that may exist within or be connected to the UE 1000. For example, the driving circuit 1022 may include: a display driver for controlling and allowing access to a display device; a touchscreen driver for controlling and allowing access to a touchscreen interface; a sensor driver for acquiring sensor readings of the sensor circuit 1020 and controlling and allowing access to the sensor circuit 1020; a driver for acquiring actuator positions of electromechanical components or controlling and allowing access to electromechanical components; a camera driver for controlling and allowing access to an embedded image capture device; and an audio driver for controlling and allowing access to one or more audio devices.

[0147] The PMIC 1024 manages the power supplied to various components of the UE 1000. Specifically, relative to the processor 1004, the PMIC 1024 controls power selection, voltage scaling, battery charging, or DC-DC conversion.

[0148] In some implementations, the PMIC 1024 can control or otherwise become part of various power-saving mechanisms of the UE 1000. For example, if the platform UE is in the RRC_Connected state, where it remains connected to the RAN node as it anticipates receiving traffic soon, it can enter a state known as Discontinuous Receive Mode (DRX) after a period of inactivity. During this state, the UE 1000 can power down for short intervals to conserve power. If there is no data traffic activity over an extended period, the UE 1000 can transition to the RRC_Idle state, where the UE disconnects from the network and does not perform operations such as channel quality feedback, handover, etc. The UE 1000 enters a very low-power state and performs paging, where the UE periodically wakes up again to listen to the network and then power down again. The UE 1000 may not receive data in this state; to receive data, the platform must transition back to the RRC_Connected state. Additional power-saving modes can allow the device to be unable to use the network for longer than the paging interval (ranging from a few seconds to several hours). During this period, the device is completely unable to connect to the network and can be completely powered off. Any data sent during this time will result in significant latency, which is assumed to be acceptable.

[0149] Battery 1028 can power UE 1000, but in some examples, UE 1000 may be mounted in a fixed location and may have a power source coupled to the mains. Battery 1028 may be a lithium-ion battery, a metal-air battery such as a zinc-air battery, an aluminum-air battery, a lithium-air battery, etc. In some specific implementations, such as in vehicle-based applications, battery 1028 may be a typical lead-acid automotive battery.

[0150] Figure 11 An exemplary gNB 1100 according to some embodiments is shown. The gNB 1100 may include a processor 1104, an RF interface circuit 1108, a core network (CN) interface circuit 1112, a memory / storage device circuit 1116, and an antenna structure 1126.

[0151] The components of gNB 1100 can be coupled to various other components via one or more interconnects 1128.

[0152] The processor 1104, RF interface circuit 1108, memory / storage device circuit 1116 (including communication protocol stack 1110), antenna structure 1126, and interconnect 1128 can be similar to those in the reference. Figure 10 Similar named elements are shown and described.

[0153] The CN interface circuit 1112 can provide connectivity to a core network (e.g., a 5th generation core network (5GC) using a 5GC-compatible network interface protocol (such as Carrier Ethernet) or some other suitable protocol). Network connectivity can be provided to / from the gNB 1100 via fiber optic or wireless backhaul. The CN interface circuit 1112 may include one or more dedicated processors or FPGAs for communicating using one or more of the aforementioned protocols. In some implementations, the CN interface circuit 1112 may include multiple controllers for providing connectivity to other networks using the same or different protocols.

[0154] As is widely recognized, the use of personally identifiable information should comply with privacy policies and practices that are generally accepted to meet or exceed industry or governmental requirements for protecting user privacy. Specifically, personally identifiable information data should be managed and processed to minimize the risk of unintentional or unauthorized access or use, and the nature of authorized use should be clearly explained to users.

[0155] For one or more embodiments, at least one of the components shown in one or more of the foregoing figures may be configured to perform one or more operations, techniques, processes, or methods as described in the Examples section below. For example, the baseband circuitry described above in conjunction with one or more of the foregoing figures may be configured to operate according to one or more of the examples below. Similarly, circuitry associated with the UE, base station, network element, etc., described above in conjunction with one or more of the foregoing figures may be configured to operate according to one or more of the examples shown in the Examples section below.

[0156] Example

[0157] Further exemplary implementations are provided in the following sections.

[0158] Example 1 may include one or more computer-readable media having instructions, when executed by one or more processors, to cause a user equipment (UE) to perform the following operations: determine the number of times a synchronization signal / physical broadcast channel block (SSB), physical downlink control channel (PDCCH), or physical downlink shared channel (PDSCH) is unavailable during a cell global identifier (CGI) read process; determine a process period for reading the CGI based at least in part on the number of times the SSB, PDCCH, or PDSCH is unavailable during the CGI read process; and utilize the process period to perform the CGI read process.

[0159] Example 2 may include one or more computer-readable media according to Example 1, wherein determining the process period includes determining the extension period of the process period based at least in part on the number of times the SSB, the PDCCH, or the PDSCH is unavailable during the CGI read process and on the measurement timing configuration (SMTC) period of the synchronization signal / physical broadcast channel block.

[0160] Example 3 may include one or more computer-readable media according to Example 1, wherein the number of times the SSB, the PDCCH, or the PDSCH is unavailable during the CGI read process includes the number of times the SSB is unavailable during the CGI read process, wherein the SSB carries a Master Information Block (MIB), and wherein the instructions, when executed by the one or more processors, further cause the UE to: determine that the number of times the SSB is unavailable during the CGI read process exceeds a threshold number of times, and restart the MIB acquisition phase of the CGI read process at least in part based on the determination that the number of times the SSB is unavailable during the CGI read process exceeds the threshold number of times.

[0161] Example 4 may include one or more computer-readable media according to Example 3, wherein the number of times the SSB is unavailable during the CGI read process is a first number of times the SSB is unavailable during the CGI read process, wherein a threshold number of times is a first threshold number of times, and wherein the instructions, when executed by the one or more processors, further cause the UE to: determine a second number of times the SSB is unavailable during the entire CGI read process; determine that the second number of times the SSB is unavailable during the entire CGI read process exceeds a second threshold number of times, the second threshold number of times being greater than the first threshold number of times, and exit the CGI read process at least in part based on the determination that the second number of times the SSB is unavailable during the entire CGI read process exceeds the second threshold number of times.

[0162] Example 5 may include one or more computer-readable media according to Example 1, wherein the number of times the SSB, the PDCCH, or the PDSCH is unavailable during the CGI read process includes the number of times the SSB is unavailable during the CGI read process, wherein the SSB carries a Master Information Block (MIB), and wherein the instructions, when executed by the one or more processors, further cause the UE to: determine that the number of times the SSB is unavailable during the CGI read process exceeds a threshold number of times, and exit the CGI read process at least in part based on the determination that the number of times the SSB is unavailable during the CGI read process exceeds the threshold number of times.

[0163] Example 6 may include one or more computer-readable media according to Example 1, wherein the number of times the SSB, PDCCH, or PDSCH is unavailable during the CGI read process includes the number of times the SSB is unavailable during the CGI read process, wherein the SSB carries a Master Information Block (MIB), and wherein the instructions, when executed by the one or more processors, further cause the UE to: determine that the number of times the SSB is unavailable during the CGI read process exceeds a threshold number of times, and report a CGI read failure to the network based at least in part on the determination of the number of times the SSB is unavailable during the CGI read process.

[0164] Example 7 may include one or more computer-readable media according to Example 1, wherein determining the number of times the SSB, PDCCH, or PDSCH is unavailable during the CGI read process includes determining: the number of times the SSB carrying the Master Information Block (MIB) is unavailable during the CGI read process; the number of times the PDCCH transmission of the Scheduled System Information Block Type 1 (SIB1) is unavailable during the CGI read process; or the number of times the PDSCH transmission of the SIB1 is unavailable during the CGI read process.

[0165] Example 8 may include one or more computer-readable media according to Example 1, wherein the number of times the SSB, the PDCCH, or the PDSCH is unavailable during the CGI read process includes the number of times the PDCCH or PDSCH is unavailable during the CGI read process, wherein the PDCCH or the PDSCH is for System Information Block Type 1 (SIB1), and wherein the instructions, when executed by the one or more processors, further cause the UE to: determine that the number of times the PDCCH or PDSCH is unavailable during the CGI read process exceeds a threshold number of times, and restart the SIB1 acquisition phase of the CGI read process at least in part based on the determination that the number of times the PDCCH or PDSCH is unavailable at the UE exceeds the threshold number of times of times.

[0166] Example 9 may include one or more computer-readable media according to Example 8, wherein the number of times the PDCCH or PDSCH is unavailable during the CGI read process is a first number of times the PDCCH or PDSCH is unavailable during the CGI read process, wherein a threshold number of times is a first threshold number of times, and wherein the instruction, when executed by the one or more processors, further causes the UE to: determine a second number of times the PDCCH or PDSCH is unavailable during the entire CGI read process; determine that the second number of times the PDCCH or PDSCH is unavailable during the entire CGI read process exceeds a second threshold number of times, the second threshold number of times being greater than the first threshold number of times, and exit the CGI read process at least in part based on the determination that the number of times the PDCCH or PDSCH is unavailable during the entire CGI read process exceeds the second threshold number of times.

[0167] Example 10 may include a user equipment (UE) comprising: a memory for storing a cell global identifier (CGI) of a target cell, and processing circuitry coupled to the memory, the processing circuitry being configured to: determine a time period for main information block (MIB) reading based on the number of times the synchronization signal / physical broadcast channel block (SSB) is unavailable during a CGI reading process; determine a time period for system information block (SIB) reading based on the number of times the physical downlink control channel (PDCCH) scheduling system information block type 1 (SIB1) is unavailable, the physical downlink shared channel (PDSCH) carrying SIB1 is unavailable, or the MIB is unavailable during the CGI reading process for SIB1; and determine a process period based on the time period for MIB reading and the time period for SIB reading.

[0168] Example 11 may include the UE according to Example 10, wherein the number of times the PDCCH of SIB1 is scheduled to be unavailable or the PDSCH of SIB1 is scheduled to be unavailable during the CGI read process for SIB1 is a first number of times the PDCCH of SIB1 is scheduled to be unavailable or the PDSCH of SIB1 is scheduled to be unavailable during the CGI read process for SIB1, wherein the threshold number of times is a first threshold number of times, and wherein the processing circuitry is further configured to: determine that the number of times the PDCCH of SIB1 is scheduled to be unavailable or the PDSCH of SIB1 is scheduled to be unavailable during the CGI read process for SIB1 exceeds the threshold number of times, and restart the MIB acquisition phase at least in part based on the determination that the number of times the PDCCH of SIB1 is scheduled to be unavailable or the PDSCH of SIB1 is scheduled to be unavailable during the CGI read process for SIB1 exceeds the threshold number of times.

[0169] Example 12 may include the UE according to Example 11, wherein the number of times the PDCCH of SIB1 is scheduled to be unavailable or the PDSCH of SIB1 is scheduled to be unavailable during the CGI read process for SIB1 is a first number of times the PDCCH of SIB1 is scheduled to be unavailable or the PDSCH of SIB1 is scheduled to be unavailable during the CGI read process for SIB1, wherein the threshold number of times is a first threshold number of times, and wherein the processing circuitry is further configured to: determine the times the PDCCH of SIB1 is scheduled to be unavailable or the PDSCH of SIB1 is scheduled to be unavailable during the entire CGI read process for SIB1. A second number of times when the PDSCH of IB1 is unavailable; determining that the second number of times when the PDCCH of SIB1 or the PDSCH of SIB1 is unavailable during the entire CGI read process for SIB1 exceeds a second threshold number of times, the second threshold number of times being greater than a first threshold number of times, and exiting the CGI read process at least in part based on the determination that the second number of times when the PDCCH of SIB1 or the PDSCH of SIB1 is unavailable during the entire CGI read process for SIB1 exceeds the second threshold number of times.

[0170] Example 13 may include the UE according to Example 11, wherein the number of times the PDCCH of SIB1 is scheduled to be unavailable or the PDSCH of SIB1 is scheduled to be unavailable during the CGI read process for SIB1 is a first number of times the PDCCH of SIB1 is scheduled to be unavailable or the PDSCH of SIB1 is scheduled to be unavailable during the CGI read process for SIB1, wherein the threshold number of times is a first threshold number of times, and wherein the processing circuitry is further configured to: determine the times the PDCCH of SIB1 is scheduled to be unavailable or the PDSCH of SIB1 is scheduled to be unavailable during the entire CGI read process for SIB1. A second number of times the PDSCH of IB1 is unavailable; determining that the second number of times the PDCCH of SIB1 or the PDSCH of SIB1 is unavailable during the entire CGI read process for SIB1 exceeds a second threshold number of times the second threshold number of times the times the times the times the times the times the times the PDCCH of SIB1 or the PDSCH of SIB1 is unavailable during the entire CGI read process for SIB1 exceeds the second threshold number of times the times the times the times the times the PDCCH of SIB1 is unavailable during the entire CGI read process for SIB1 exceeds the second threshold number of times the times the times the times the times the times the times the PDSCH of SIB1 is unavailable during the entire CGI read process for SIB1 exceeds the second threshold number of times the times the times the times the times the times the times the times the PDSCH of SIB1 is unavailable exceeds exceeds the second threshold number of times the times the CGI read failure is reported to the network.

[0171] Example 14 may include the UE according to Example 10, wherein the processing circuitry is further configured to: determine that the total number of times exceeds a threshold number of times, the total number of times including the number of times when the SSB is unavailable during the CGI read process and the number of times when the PDCCH of the SIB1 is unavailable, the PDSCH carrying the SIB1 is unavailable, or the MIB is unavailable during the CGI read process for SIB1, and restart the MIB acquisition phase of the CGI read process at least in part based on the determination that the total number of times exceeds the threshold number of times.

[0172] Example 15 may include the UE according to Example 14, wherein the total number of times is a first total number of times, wherein the threshold number of times is a first threshold number of times, and wherein the processing circuitry is further configured to: determine a second total number of times, the second total number of times including the number of times the SSB is unavailable during the entire CGI read process and the number of times the PDCCH of the SIB1 is unavailable, the PDSCH carrying the SIB1 is unavailable, or the MIB is unavailable during the entire CGI read process for the SIB1; determine that the second total number of times exceeds a second threshold number of times, the second threshold number of times being greater than the first threshold number of times; and exit the CGI read process at least in part based on the determination that the second total number of times exceeds the second threshold number of times.

[0173] Example 16 may include the UE according to Example 14, wherein the total number of opportunities is a first total number of opportunities, wherein the threshold number of opportunities is a first threshold number of opportunities, and wherein the processing circuitry is further configured to: determine a second total number of opportunities, the second total number of opportunities including the number of opportunities during the entire CGI read process during which the SSB is unavailable and the number of opportunities during the entire CGI read process for SIB1 during which the PDCCH of SIB1 is unavailable, the PDSCH carrying SIB1 is unavailable, or the MIB is unavailable; determine that the second total number of opportunities exceeds a second threshold number of opportunities, the second threshold number of opportunities being greater than the first threshold number of opportunities; and report a CGI read failure to the network at least in part based on the determination that the second total number of opportunities exceeds the second threshold number of opportunities.

[0174] Example 17 may include a method of operating a user equipment (UE), the method comprising: determining the number of times during a Cell Global Identifier (CGI) read procedure that a Synchronization Signal / Physical Broadcast Channel Block (SSB), Physical Downlink Control Channel (PDCCH), or Physical Downlink Shared Channel (PDSCH) is unavailable; determining a procedure period for reading the CGI based at least in part on the number of times the SSB, PDCCH, or PDSCH is unavailable during the CGI read procedure; and using the procedure period to perform the CGI read procedure.

[0175] Example 18 may include the method according to Example 17, further comprising: identifying triggering of a CGI report associated with the CGI read process; determining a CGI report delay based at least in part on the number of times the SSB, PDCCH, or PDSCH is unavailable during the CGI read process; and reporting a measurement report of the CGI report when the CGI report delay expires.

[0176] Example 19 may include the method according to Example 18, further including determining a delay due to an uplink (UL) listen-before-speak (LBT) failure, wherein the CGI reporting delay is further determined based on the delay due to the UL LBT failure.

[0177] Example 20 may include the method according to Example 17, wherein determining the process period includes extending the process period from the basic period of the process period by an extension period equal to the number of times the SSB, the PDCCH, or the PDSCH is unavailable during the CGI read process multiplied by the period of the Measurement Timing Configuration (SMTC) timing based on the Synchronization Signal / Physical Broadcast Channel Block.

[0178] Example 21 may include an apparatus comprising one or more elements for performing the method or any other method or process described herein, as described in or associated with any of Examples 1 to 20.

[0179] Example 22 may include one or more non-transitory computer-readable media, the one or more non-transitory computer-readable media including instructions that, when executed by one or more processors of an electronic device, cause the electronic device to perform one or more elements of the method or any other method or process described herein, as described or associated with any of Examples 1 to 20.

[0180] Example 23 may include an apparatus comprising logic components, modules, or circuitry for performing one or more elements of the method described or associated with any of Examples 1 to 20 or any other method or process described herein.

[0181] Example 24 may include a method, technique, or process, or a part or component thereof, described or associated with any of Examples 1 to 20.

[0182] Example 25 may include an apparatus comprising one or more processors and one or more computer-readable media, the one or more computer-readable media including instructions that, when executed by the one or more processors, cause the one or more processors to perform a method, technique, or process, or a portion thereof, as described or associated with any of Examples 1 to 20.

[0183] Example 26 may include a signal, or a portion thereof, described or associated with any of Examples 1 to 20.

[0184] Example 27 may include a datagram, information element, packet, frame, segment, PDU or message, or a portion or component thereof, as described or associated with any of Examples 1 to 20, or otherwise described in this disclosure.

[0185] Example 28 may include a signal encoded with data according to or associated with any of Examples 1 to 20, or a portion or component thereof, or otherwise described in this disclosure.

[0186] Example 29 may include a signal, or a portion or component thereof, encoded as a datagram, IE, packet, frame, segment, PDU, or message, as described or associated with any of Examples 1 to 20, or otherwise described in this disclosure.

[0187] Example 30 may include an electromagnetic signal carrying computer-readable instructions, wherein execution of the computer-readable instructions by one or more processors will cause one or more processors to perform the methods, techniques, or processes, or portions thereof, described or associated with any of Examples 1 to 20.

[0188] Example 31 may include a computer program comprising instructions, wherein execution of the program by a processing element will cause the processing element to perform, or in part with, the methods, techniques or processes described or associated with any of Examples 1 to 20.

[0189] Example 32 may include signals in a wireless network as shown and described herein.

[0190] Example 33 may include methods for communicating in a wireless network as shown and described herein.

[0191] Example 34 may include a system for providing wireless communication as shown and described herein.

[0192] Example 35 may include a device for providing wireless communication as shown and described herein.

[0193] Unless otherwise expressly stated, any of the examples above may be combined with any other example (or combination of examples). The foregoing description of one or more specific embodiments provides illustration and description, but is not intended to be exhaustive or to limit the scope of the embodiments to the precise form disclosed. In light of the teachings above, modifications and variations are possible, or modifications and variations may be derived from practice of various embodiments.

[0194] Although the above embodiments have been described in considerable detail, many variations and modifications will become apparent to those skilled in the art once the disclosure is fully understood. This disclosure is intended to render the following claims as encompassing all such variations and modifications.

Claims

1. One or more computer-readable media having instructions that, when executed by one or more processors, cause a user to equip a UE: Determine the number of times during which the Synchronization Signal / Physical Broadcast Channel Block (SSB), Physical Downlink Control Channel (PDCCH), or Physical Downlink Shared Channel (PDSCH) is unavailable during the Cell Global Identifier (CGI) read process, wherein determining the number of times the events are unavailable includes determining: The number of times the SSB carrying the main information block MIB is unavailable during the CGI read process; The number of times during the CGI read process when the PDCCH transmission of System Information Block Type 1 (SIB1) is unavailable; or The number of times during which the PDSCH carrying SIB1 is unavailable during the CGI read process; The process cycle for reading CGI is determined at least in part based on the number of times during which the SSB, PDCCH, or PDSCH is unavailable during the CGI reading process; as well as The CGI reading process is executed using the process cycle.

2. The one or more computer-readable media according to claim 1, wherein determining the process cycle comprises: The extension period of the process cycle is determined at least in part based on the number of times the SSB, PDCCH, or PDSCH is unavailable during the CGI read process and the measurement timing configuration SMTC period based on the synchronization signal / physical broadcast channel block.

3. One or more computer-readable media according to claim 1 or claim 2, wherein the number of times the SSB, the PDCCH, or the PDSCH is unavailable during the CGI reading process includes: The number of times the SSB is unavailable during the CGI read process, wherein the SSB carries the Master Information Block (MIB), and wherein the instructions, when executed by the one or more processors, further cause the UE to: The number of times the SSB was unavailable during the CGI read process was determined to exceed a threshold number of times; as well as The MIB acquisition phase of the CGI read process is restarted at least in part based on the number of times the SSB is determined to be unavailable during the CGI read process exceeding a threshold number of times the time is determined to be unavailable.

4. The one or more computer-readable media of claim 3, wherein the number of times the SSB is unavailable during the CGI reading process is a first number of times the SSB is unavailable during the CGI reading process, wherein the threshold number of times is a first threshold number of times, and wherein the instruction, when executed by the one or more processors, further causes the UE to: A second number of times when the SSB is unavailable during the entire CGI read process; The second number of times when the SSB is unavailable during the entire CGI read process exceeds a second threshold number of times, the second threshold number of times being greater than a first threshold number of times. as well as The CGI read process is terminated at least in part based on a second number of times when the SSB is unavailable during the entire CGI read process exceeds a second threshold number of times.

5. The computer-readable medium of claim 1, wherein the number of times during which the SSB, the PDCCH, or the PDSCH is unavailable during the CGI reading process includes: The number of times the SSB is unavailable during the CGI read process, wherein the SSB carries the Master Information Block (MIB), and wherein the instructions, when executed by the one or more processors, further cause the UE to: The number of times the SSB was unavailable during the CGI read process was determined to exceed a threshold number of times; as well as The CGI read process is terminated at least in part based on the fact that the number of times the SSB is unavailable during the CGI read process exceeds a threshold number of times the time is determined.

6. The one or more computer-readable media of claim 1, wherein the number of times during which the SSB, the PDCCH, or the PDSCH is unavailable during the CGI reading process includes: The number of times the SSB is unavailable during the CGI read process, wherein the SSB carries the Master Information Block (MIB), and wherein the instructions, when executed by the one or more processors, further cause the UE to: The number of times the SSB was unavailable during the CGI read process was determined to exceed a threshold number of times; as well as The CGI read failure is reported to the network at least in part based on the number of times the SSB is determined to be unavailable during the CGI read process.

7. The one or more computer-readable media of claim 1, wherein the number of times during which the SSB, the PDCCH, or the PDSCH is unavailable during the CGI reading process includes: The number of times the PDCCH or PDSCH is unavailable during the CGI read process, wherein the PDCCH or PDSCH is for System Information Block Type 1, i.e., SIB1, and wherein the instruction, when executed by the one or more processors, further causes the UE to: The number of times during which the PDCCH or the PDSCH is unavailable during the CGI read process exceeds a threshold number of times; and The SIB1 acquisition phase of the CGI read process is restarted at least in part based on the fact that the number of times the PDCCH or PDSCH is determined to be unavailable at the UE exceeds a threshold number of the time.

8. The one or more computer-readable media of claim 7, wherein the number of times the PDCCH or the PDSCH is unavailable during the CGI read process is a first number of times the PDCCH or the PDSCH is unavailable during the CGI read process, wherein the threshold number of times is a first threshold number of times, and wherein the instruction, when executed by the one or more processors, further causes the UE to: A second number of times when the PDCCH or the PDSCH is unavailable during the entire CGI read process; Determining that the second number of times the PDCCH or PDSCH is unavailable during the entire CGI read process exceeds a second threshold number of times, the second threshold number of times being greater than a first threshold number of times; and The CGI read process is terminated at least in part based on the determination that the number of times the PDCCH or PDSCH is unavailable during the entire CGI read process exceeds a second threshold number of times the time is determined.

9. A user equipment (UE), the UE comprising: A memory, wherein the memory is used to store the Cell Global Identifier (CGI) of the target cell; and Processing circuitry, coupled to the memory, is used for: The time period for reading the Master Information Block (MIB) is determined based on the number of times the Synchronization Signal / Physical Broadcast Channel Block (SSB) is unavailable during the CGI read process; The time period for reading the system information block SIB is determined based on the number of times during the CGI reading process for system information block type 1, i.e., SIB1, the physical downlink control channel (PDCCH) of SIB1 is unavailable, the physical downlink shared channel (PDSCH) carrying SIB1 is unavailable, or the MIB is unavailable; and The process cycle is determined based on the time period used for MIB reading and the time period used for SIB reading.

10. The UE of claim 9, wherein the number of times the PDCCH of SIB1 is scheduled to be unavailable, the PDSCH carrying SIB1 is unavailable, or the MIB is unavailable during the CGI read procedure for SIB1 includes: The number of times during the CGI read process of SIB1 that the PDCCH of SIB1 is unavailable or the PDSCH carrying SIB1 is unavailable, and wherein the processing circuitry is further configured to: The number of times during the CGI read process for SIB1 that the PDCCH of SIB1 is unavailable or the PDSCH carrying SIB1 is unavailable exceeds a threshold number of times. as well as The MIB acquisition phase is restarted at least in part based on the determination that the number of times the PDCCH of SIB1 or the PDSCH carrying SIB1 is unavailable during the CGI read process for SIB1 exceeds a threshold number of times.

11. The UE of claim 10, wherein the number of times the PDCCH of SIB1 is scheduled to be unavailable or the PDSCH carrying SIB1 is scheduled to be unavailable during the CGI read process for SIB1 is a first number of times the PDCCH of SIB1 is scheduled to be unavailable or the PDSCH carrying SIB1 is scheduled to be unavailable during the CGI read process for SIB1, wherein the threshold number of times is a first threshold number of times, and wherein the processing circuitry is further configured to: Determine a second number of times when the PDCCH of SIB1 or the PDSCH carrying SIB1 is unavailable during the entire CGI read process for SIB1; Determine that a second number of times during the entire CGI read process for SIB1 that the PDCCH of SIB1 is unavailable or the PDSCH carrying SIB1 is unavailable exceeds a second threshold number of times, the second threshold number of times being greater than a first threshold number of times; as well as The CGI read process is terminated at least in part based on a second threshold number of times during which the PDCCH of SIB1 or the PDSCH carrying SIB1 is unavailable, determined to occur during the entire CGI read process for SIB1.

12. The UE of claim 10, wherein the number of times during the CGI read process for SIB1 that the PDCCH of SIB1 is unavailable or the PDSCH carrying SIB1 is unavailable is a first number of times during the CGI read process for SIB1 that the PDCCH of SIB1 is unavailable or the PDSCH carrying SIB1 is unavailable is scheduled, wherein the threshold number of times is a first threshold number of times, and wherein the processing circuitry is further configured to: Determine a second number of times when the PDCCH of SIB1 or the PDSCH carrying SIB1 is unavailable during the entire CGI read process for SIB1; The determination that a second number of times when the PDCCH of SIB1 or the PDSCH carrying SIB1 is unavailable during the entire CGI read process for SIB1 exceeds a second threshold number of times, the second threshold number of times being greater than a first threshold number of times; as well as The CGI read failure is reported to the network at least in part based on the second number of times during which the PDCCH of SIB1 or the PDSCH of SIB1 is unavailable during the entire CGI read process for SIB1 exceeds a second threshold number of times.

13. The UE according to claim 9, wherein the processing circuitry is further configured to: The total number of identified opportunities exceeds a threshold number of opportunities, where the total number of opportunities includes: The number of times the SSB is unavailable during the CGI read process and the number of times the PDCCH of SIB1, the PDSCH carrying SIB1, or the MIB is unavailable during the CGI read process for SIB1; as well as The MIB acquisition phase of the CGI reading process may be restarted at least in part based on the total number of times the determined timing exceeds a threshold number of the timing.

14. The UE of claim 13, wherein the total number of timings is a first total number of timings, wherein the threshold number of timings is a first threshold number of timings, and wherein the processing circuitry is further configured to: A second total number of opportunities is determined, the second total number of opportunities including: The number of times the SSB is unavailable during the entire CGI read process, and the number of times the PDCCH of SIB1, the PDSCH carrying SIB1, or the MIB is unavailable during the entire CGI read process for SIB1; The second total number of the timings is determined to exceed a second threshold number of timings, and the second threshold number of timings is greater than a first threshold number of timings. as well as The CGI reading process may be terminated at least in part based on the second total number of times the timing is determined exceeding the second threshold number of times the timing is determined.

15. The UE of claim 13, wherein the total number of timings is a first total number of timings, wherein the threshold number of timings is a first threshold number of timings, and wherein the processing circuitry is further configured to: A second total number of opportunities is determined, the second total number of opportunities including: The number of times the SSB is unavailable during the entire CGI read process, and the number of times the PDCCH of SIB1, the PDSCH carrying SIB1, or the MIB is unavailable during the entire CGI read process for SIB1; The second total number of the timings is determined to exceed a second threshold number of timings, and the second threshold number of timings is greater than a first threshold number of timings. as well as A CGI read failure is reported to the network at least in part based on the second total number of times the timing is determined exceeding a second threshold number of times the timing is determined.

16. A method for operating a user equipment (UE), comprising: Determine the number of times when the Synchronization Signal / Physical Broadcast Channel Block (SSB), Physical Downlink Control Channel (PDCCH), or Physical Downlink Shared Channel (PDSCH) is unavailable during the Cell Global Identifier (CGI) read process; The process cycle for reading CGI is determined at least in part based on the number of times during which the SSB, PDCCH, or PDSCH is unavailable during the CGI reading process; The CGI reading process is executed using the aforementioned process cycle; Identify the triggering of CGI reports related to the CGI reading process; The CGI reporting delay is determined at least in part based on the number of times during which the SSB, PDCCH, or PDSCH is unavailable during the CGI read process; as well as The measurement report of the CGI report shall be reported when the CGI report is due.

17. The method of claim 16, further comprising determining a delay due to an uplink UL Listen-After-Speak (LBT) failure, wherein the CGI reporting delay is further determined based on the delay due to the UL LBT failure.

18. The method of claim 16 or claim 17, wherein determining the process period comprises extending the process period from the basic period of the process period by an extended period, the extended period being equal to the number of times the SSB, the PDCCH, or the PDSCH is unavailable during the CGI read process multiplied by the period of the measurement timing configuration SMTC timing based on the synchronization signal / physical broadcast channel block.

Images