Network energy saving techniques using rach procedures

Abstract

Various aspects of the present disclosure relate to receiving broadcast signaling from a first cell, the broadcast signaling including a configuration for requesting a first system information block (SIB1) of a second cell. Aspects of the present disclosure can relate to transmitting a first random access message (Msg 1) indicating a request for the SIB1 of the second cell. Aspects of the present disclosure can relate to monitoring for the SIB1 of the second cell based at least in part on reception of a second random access message (Msg 2); and evaluating cell reselection based at least in part on reception of the SIB1.

Description

Technical Field

[0001] This disclosure relates to wireless communications, and more specifically to network power-saving techniques using the Random Access Procedure (RACH procedure). Background Technology

[0002] A wireless communication system may include one or more network communication devices (which may be referred to as network devices (NEs)) that support wireless communication with one or more user communication devices, which may also be referred to as user equipment (UEs) or other suitable terms. The wireless communication system can support wireless communication with one or more user communication devices by utilizing the resources of the wireless communication system (e.g., time resources (e.g., symbols, time slots, subframes, frames, etc.) or frequency resources (e.g., subcarriers, carriers, etc.)). Additionally, the wireless communication system can support wireless communication across various radio access technologies (RATs), including third-generation (3G), fourth-generation (4G), fifth-generation (5G), and other suitable radio access technologies other than 5G (e.g., 5G Advanced (5G-A), sixth-generation (6G)). Summary of the Invention

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

[0004] A UE for wireless communication is described. The UE may be configured, enabled, or operable to: receive broadcast signaling from a first cell, the broadcast signaling including a configuration for requesting a first system information block of a second cell; send a first random access message indicating a request for the first system information block of the second cell; monitor the first system information block of the second cell based at least in part on the transmission of the first random access message; and evaluate cell reselection based at least in part on the reception of the first system information block.

[0005] A processor for wireless communication is described. The processor may be configured, capable of, or operable to: receive broadcast signaling from a first cell, the broadcast signaling including a configuration for requesting a first system information block from a second cell; transmit a first random access message indicating a request for the first system information block from the second cell; monitor the first system information block from the second cell, at least in part based on the transmission of the first random access message; and evaluate cell reselection, at least in part based on the reception of the first system information block.

[0006] A method for wireless communication, performed or executable by a UE, is described. The method may include: receiving broadcast signaling from a first cell, the broadcast signaling including configuration for requesting a first system information block of a second cell; sending a first random access message indicating a request for the first system information block of the second cell; monitoring the first system information block of the second cell, at least in part based on the transmission of the first random access message; and evaluating cell reselection, at least in part based on the reception of the first system information block.

[0007] A base station for wireless communication is described. The base station may be configured, capable of, or operable to: transmit broadcast signaling in a first cell, the broadcast signaling including a configuration for requesting a first system information block for a second cell; receive from a UE a first random access message indicating a request for the first system information block for the second cell; transmit a second random access message in response to the first random access message; and transmit the first system information block for the second cell.

[0008] A processor for wireless communication is described. The processor may be configured, capable of, or operable to: transmit broadcast signaling in a first cell, the broadcast signaling including configuration for requesting a first system information block of a second cell; receive from a UE a first random access message indicating a request for the first system information block of the second cell; transmit a second random access message in response to the first random access message; and transmit the first system information block of the second cell.

[0009] A method for wireless communication, performed or executable by a base station, is described. The method may include: transmitting broadcast signaling in a first cell, the broadcast signaling including configuration for requesting a first system information block of a second cell; receiving from a UE a first random access message indicating a request for the first system information block of the second cell; transmitting a second random access message in response to the first random access message; and transmitting the first system information block of the second cell. Attached Figure Description

[0010] Figure 1 Examples of wireless communication systems according to various aspects of this disclosure are illustrated.

[0011] Figure 2 An example of a protocol stack according to various aspects of this disclosure is illustrated, showing different protocol layers in the UE and the network.

[0012] Figure 3A An example of a contention-based random access (CBRA) procedure employing a 4-step random access (RA) type is illustrated according to various aspects of this disclosure.

[0013] Figure 3B An example of a CBRA process employing a 2-step RA type is illustrated according to various aspects of this disclosure.

[0014] Figure 3C An example of a contention-free random access (CFRA) procedure using a 4-step RA type is illustrated according to various aspects of this disclosure.

[0015] Figure 3D An example of a CFRA process employing a two-step RA type according to various aspects of this disclosure is illustrated.

[0016] Figure 3E An example of a rollback process for a CBRA employing a 2-step RA type is illustrated according to various aspects of this disclosure.

[0017] Figure 4 An example of a RACH-based delivery process for SIB1 from an anchor cell is illustrated in accordance with various aspects of this disclosure.

[0018] Figure 5 An example of a RACH-based delivery process for SIB1 from a non-anchor cell is illustrated according to various aspects of this disclosure.

[0019] Figure 6 An example of a paging-based acquisition process for SIB1 from an anchor cell is illustrated according to various aspects of this disclosure.

[0020] Figure 7An example of a paging-based acquisition process for SIB1 from a non-anchor cell is illustrated according to various aspects of this disclosure.

[0021] Figure 8 Another example of a paging-based acquisition process for SIB1 according to various aspects of this disclosure is illustrated.

[0022] Figure 9 Examples of UEs according to various aspects of this disclosure are illustrated.

[0023] Figure 10 Examples of processors according to various aspects of this disclosure are illustrated.

[0024] Figure 11 Examples of NEs according to various aspects of this disclosure are illustrated.

[0025] Figure 12 The diagram illustrates a flowchart of a method performed by a UE according to various aspects of this disclosure.

[0026] Figure 13 The diagram illustrates a flowchart of a method performed by a RAN entity according to various aspects of this disclosure. Detailed Implementation

[0027] In general, this disclosure describes systems, methods, and apparatuses for cell measurement in network energy-efficient cells. In some embodiments, these methods can be performed using computer-executable code embedded in a computer-readable medium. In some embodiments, the apparatus or system may include a computer-readable medium containing computer-readable code that, when executed by a processor, causes the apparatus or system to perform at least a portion of the solutions described below.

[0028] Emissions and energy consumption from various components of the telecommunications system have adverse effects on the climate. Synchronization signal and physical broadcast channel (SS / PBCH) transmissions are necessary for initial access to the radio access network, but lead to significant network energy consumption. Furthermore, these SS / PBCH transmissions waste energy when no UE is attempting to access the cell.

[0029] Furthermore, the operating costs of running telecommunications services are substantial. In the telecommunications sector, several industry-specific factors stemming from rising network costs further impact efficiency. Mobile data services continue to grow, estimated at 6.4 gigabytes (GB) per user per month in 2019, and projected to triple over the next five years. Combined with rising spectrum costs, capital investment, and ongoing RAN maintenance / upgrades, energy-saving measures in network operations are necessary, not required.

[0030] Compared to previous generations of mobility, 5G New Radio (NR) offers significant energy efficiency improvements per gigabyte. However, new 5G use cases and the adoption of millimeter waves will require more sites and antennas. This leads to the prospect of a more efficient network, which may paradoxically result in higher emissions without aggressive intervention.

[0031] A study on network energy efficiency in NR demonstrates the necessity of energy conservation. Network energy efficiency is crucial for environmental sustainability, reducing environmental impact (greenhouse gas emissions) and saving operating costs. With the proliferation of 5G across industries and geographic regions, and the handling of more advanced services and applications requiring very high data rates (e.g., extended reality (XR) services and applications), networks are becoming increasingly dense, using more antennas, greater bandwidth, and more frequency bands. The environmental impact of 5G needs to be controlled, and new solutions for improving network energy efficiency need to be developed.

[0032] Energy consumption has become a critical component of operators' operating costs. According to some reports, energy costs for mobile networks account for approximately 23% of operators' total costs. The majority of energy consumption comes from the radio access network, particularly from active antenna units (AAUs), with data centers and fiber optic transmission accounting for a smaller share. Radio access power consumption can be divided into two parts: a dynamic component, which is consumed only when data transmission / reception is in progress; and a static component, which is consumed even when data transmission or reception is not in progress to maintain the necessary operation of the radio access equipment.

[0033] Although UE power consumption models have been defined by the 3rd Generation Partnership Project (3GPP), there is a need to research and develop network energy consumption models, particularly for base stations, key performance indicators (KPIs), evaluation methods, and to identify and study network energy-saving technologies in target deployment scenarios. This research investigates how to achieve more efficient operation of transmission and / or reception with dynamic and / or semi-static and finer-grained adaptation using one or more network energy-saving technologies, leveraging potential support / feedback from the UE, potential UE assistance information, and information exchange / coordination at the network interface in the time, frequency, spatial, and power domains.

[0034] 3GPP studies not only assess potential network energy consumption benefits, but also evaluate and balance the impact on network and user performance, for example, by looking at KPIs such as spectrum efficiency, capacity, user-aware throughput (UPT), latency, UE power consumption, complexity, handover performance, call drop rate, initial access performance, and service level agreement (SLA) guarantee-related KPIs.

[0035] The network consumes a significant amount of energy in transmitting Synchronization Signal Blocks (SSBs) and Physical Broadcast Channels (PBCHs) (i.e., those containing Master Information Blocks (MIBs) and System Information Block Type 1 (SIB1)). In traditional 5G networks, System Information Blocks (SIBs), except for SIB1, can be provided on demand.

[0036] To address the network energy consumption issues discussed herein, this disclosure describes how energy for SSB and SIB1 can be saved. One direct option is to provide these services as needed, i.e., on-demand transmission. Another option is not to provide SSB and SIB1 in energy-efficient cells, but instead to use anchor cells as proxy transmitters for these energy-efficient cells (e.g., for time-frequency synchronization, SIB1).

[0037] Since the network serves both RRC idle / inactive UEs and RRC connected UEs, and the service requirements and UE activities in these RRC states are very different from each other, energy-saving technologies for the network should also address these issues separately.

[0038] To further address the network power consumption issues discussed herein, this disclosure provides UE and network methods for enabling network power saving for RRC idle UEs and RRC inactive UEs.

[0039] In various embodiments, aspects of this disclosure optimize energy efficiency in the network by accurately notifying the UE when to begin searching for non-anchor cells, rather than before, for example, until another "good enough" cell becomes available to camp on. Furthermore, some embodiments disclose efficient methods in which the UE can request the SSB / SIB1 of a non-anchor cell, and these embodiments also disclose optimized methods for supplying the requested information / SSB to the UE.

[0040] A simple technique for SSB acquisition is to use the anchor cell's timing as a proxy for the downlink (DL) timing of non-anchor cells that do not transmit SSBs. This is clearly suboptimal, as it is not suitable for all cell sizes and does not provide frequency synchronization for non-anchor cells.

[0041] Similarly, for SIB1 supply, a simple technique for SIB1 acquisition is for the anchor cell to broadcast SIB1 from the non-anchor cell. However, unless some optimizations are applied, the anchor cell providing SIB1 from the non-anchor cell does not truly offer overall energy savings, since the same number of bits are broadcast anyway. The disclosed solution overcomes these drawbacks.

[0042] In one solution, the UE uses PRACH transmission as an SIB1 request for a non-anchor cell. This request can be sent to the anchor cell, or, if the SSB transmission is "ON", to the non-anchor cell. The PRACH resources used for the SIB1 request can be (pre)configured, for example, by the anchor cell, or can be known to the UE, for example, by specification. If the SIB1 request is for the anchor cell, the PRACH resources used signal to the network that the UE is requesting SIB1 information from a neighboring cell, or Msg3 can be used to signal which cell the SIB1 request is for (Physical Cell Identifier (PCID) and / or frequency). Alternatively, MsgA can be used to signal which cell the SIB1 request is for (PCID and / or frequency).

[0043] As another solution, the SIB1 of non-anchor cells is included in the MsgB by the network. In order to achieve efficient SIB1 delivery via the MsgB, the provided SIB1 information can be a subset of the SIB1 broadcast "periodically".

[0044] In a first aspect of this disclosure, SIB1 information may be a subset of SIB1s that are “periodically” broadcast, and some restricted broad categories may be specified or configured. The UE signals one of these based on: A) the UE’s RRC status (e.g., RRC_Idle, RRC_Inactive); and / or B) the UE type (e.g., Reduced Capability (REDCAP) UE, Non-Terrestrial Network (NTN) UE, etc.).

[0045] In a second aspect of this disclosure, MsgB includes SIB1, or a portion of SIB1 related to the UE based on the MsgA content.

[0046] In a third aspect of this disclosure, MsgB is transmitted by the same cell as MsgA, which receives the SIB1 request. Alternatively, MsgA is transmitted to the anchor cell, but MsgB is transmitted by a non-anchor cell itself, for example, according to anchor-to-non-anchor communication disclosed below.

[0047] In the fourth aspect of this disclosure, ra - ResponseWindow It can be started after a configurable and / or specified time following the transmission of MsgA.

[0048] In a fifth aspect of this disclosure, in order to achieve signaling enhancement, only a portion of the regular SIB1 information of the non-anchor cell is included in the MsgB, and for the remaining unincluded SIB1 information, the value provided by the anchor cell (i.e., periodically broadcast) is used.

[0049] In a sixth aspect of this disclosure, the anchor cell can provide the necessary PBCH to neighboring cells to provide parameters (e.g., CORESET#0 configuration) to the UE for monitoring the SIB1 of neighboring cells, i.e., for receiving the physical downlink control channel (PDCCH) to schedule the physical downlink shared channel (PDSCH) carrying SIB1.

[0050] In the seventh aspect of this disclosure, the transmission of RACH message 1 (Msg1) directly results in an attempt to receive SIB1 from a non-anchor cell in a broadcast manner.

[0051] In an eighth aspect of this disclosure, alternatively, after Msg1 is transmitted, the UE may wait for an acknowledgment (ACK) message (e.g., RACH message 2 (Msg2)) before attempting to receive SIB1 from a non-anchor cell via broadcast. If SIB1 is not received until a certain time has elapsed, the UE retransmits the SIB1 request. If SIB1 is not received after a configured number of trials, the UE considers the cell to be blocked (e.g., 300 seconds).

[0052] In a ninth aspect of this disclosure, paging can be used by the network to: A) signal that SIB1 is now being broadcast; or B) i) provide SIB1 information (or a portion thereof) directly in the paging DCI or ii) using PDSCH (instead of the paging message); or C) provide the information required to receive SIB1.

[0053] In the tenth aspect of this disclosure, the SIB1 request for a non-anchor cell can be issued for either the non-anchor cell or the anchor cell.

[0054] In the eleventh aspect of this disclosure, the paging configuration may be obtained from the anchor cell (i.e., for both cases in the tenth aspect) or pre-configured.

[0055] In the twelfth aspect of this disclosure, if the UE includes its paging identifier in the SIB1 request, the network may send SIB1-related paging only when the UE is paging; otherwise, the default identifier UE_ID=0 may be used for SIB1-related paging.

[0056] In a thirteenth aspect of this disclosure, to indicate that an SIB1 from a non-anchor cell is being broadcast "now," an SIB1 paging may be performed using the Short Message field in DCI format 1_0 and transmitted on the PDCCH using P-RNTI, with or without an associated paging message. In one implementation, this may be performed directly by the anchor cell or by the non-anchor cell after receiving the UE's SIB1 request from the anchor cell.

[0057] In the fourteenth aspect of this disclosure, non-anchor cells may reuse paging P-RNTIs, whereas if "" should be used for that purpose systemInfoModification "If the bit is '1,' the anchor cell can use a new paging RNTI, such as P-RNTI-2. In one implementation, the network reuses bit 1 to indicate..." systemInfoModification Alternatively, the network uses one bit from the unused bits (5-8) to indicate "". systemInfoModification In another implementation, the network uses a reserved field (bit field "00") in the short message indicator in the paging DCI to indicate " systemInfoModification ".

[0058] In the fifteenth aspect of this disclosure, an RRC-inactive UE may use the Small Data Transmission (SDT) procedure to obtain SIB1.

[0059] In a sixteenth aspect of this disclosure, the SDT procedure can be initiated on an anchor cell (indicating which cell the SIB1 request is directed to) or a non-anchor cell. According to the foregoing aspect, a new recovery reason value is used for the SIB1 request, or the LCID is reserved for SIB1, or a new RRC CCCH message is reserved for SIB1. Additionally, access stratum (AS) security may not apply to the SIB1 request. Upon receiving the SIB1 request, the network can schedule DL data containing the requested SIB1 to the UE during an ongoing SDT session.

[0060] In the seventeenth aspect of this disclosure, information for SIB1 acquisition is broadcast as a separate Information Element (IE) in the anchor SIB1. In one implementation, the IE is a Boolean flag indicating the presence of at least one overlapping / adjacent non-anchor cell. In another implementation, the Boolean flag (i.e., yes / no) may also indicate whether a non-anchor cell is "currently" broadcasting SIB1. Alternatively, the IE contains detailed Msg1 / 2 configuration.

[0061] In the eighteenth aspect of this disclosure, only limited information is included in the anchor's SIB1, and the remaining information is included in a new SIB for that purpose.

[0062] In the nineteenth aspect of this disclosure, the triggers for finding non-anchor cells include: A) no suitable cell; B) no cell that meets the S criterion; C) explicit signaling for camping on a non-anchor cell; D) a new threshold broadcast by the anchor to conditionally trigger the UE to select a non-anchor cell; and / or E) a random persistence check.

[0063] In the twentieth aspect of this disclosure, only UEs with a specific access identifier can request SIB1.

[0064] In the twenty-first aspect of this disclosure, if SSB transmission is disabled and no anchor cell is available, the UE will use a fixed time slot based on the Global Navigation Satellite System (GNSS) to perform uplink (UL) transmission using a pre-configured Physical Random Access Channel (PRACH) configuration.

[0065] Various aspects of this disclosure are described in the context of wireless communication systems.

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

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

[0068] NE 102 can provide a geographic coverage area 112, for which NE 102 can support services (e.g., voice, video, packet data, messaging, broadcasting, etc.) for one or more UEs 104 within the geographic coverage area 112. For example, NE 102 and UE 104 can support wireless communication of signals associated with services (e.g., voice, video, packet data, messaging, broadcasting, etc.) based on one or more wireless access technologies. In some implementations, NE 102 can be mobile, for example, a satellite associated with a non-terrestrial network. In some implementations, different geographic coverage areas associated with the same or different radio access technologies can overlap, but different geographic coverage areas can be associated with different NEs 102.

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

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

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

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

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

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

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

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

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

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

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

[0080] Wireless communication in unlicensed spectrum (also known as “shared spectrum”) offers several significant cost advantages compared to licensed spectrum, allowing communication to avoid overriding operator-licensed spectrum and instead utilize unlicensed spectrum in accordance with local regulations in a particular region. From a 3GPP technology perspective, unlicensed operation can occur on the Uu interface (referred to as NR-U) or on the sidelink interface (e.g., SL-U).

[0081] For initial access, UE 104 detects candidate cells and performs downlink (DL) synchronization. For example, a gNB (e.g., an embodiment of NE 102) may transmit synchronization signals and broadcast channel (SS / PBCH) transmissions, referred to as synchronization signal blocks (SSBs). The synchronization signal is a predefined data sequence known to UE 104 (or derived using information already stored at UE 104) and located at a predefined time position relative to frame / subframe boundaries, etc. UE 104 searches for SSBs and uses them to obtain DL timing information (e.g., symbol timing) for DL ​​synchronization. UE 104 may also decode system information (SI) based on the SSBs. It should be noted that, utilizing beam-based communication, each DL beam can be associated with a corresponding SSB.

[0082] After performing DL synchronization and acquiring basic system information (such as the Master Information Block (MIB) and System Information Block Type 1 (SIB1)), UE 104 performs an uplink (UL) synchronization and resource request by selecting and transmitting a preamble on the Physical Random Access Channel (PRACH) to execute a random access procedure (referred to as the "RACH procedure"). The PRACH preamble is transmitted during the RACH timing, i.e., a predetermined set of time-frequency resources available for the reception of the PRACH preamble. It should be noted that, using beam-based communication, UE 104 can select a specific DL beam and transmit the PRACH preamble on the corresponding UL beam. In such embodiments, a mapping may exist between the SSB and the RACH timing to allow the network to determine which beam UE 104 has selected.

[0083] To complete the RACH procedure, after sending the PRACH preamble (also known as "Msg1"), the UE 104 monitors the Random Access Response (RAR) message (also known as "Msg2"). The gNB sends UL timing adjustment information in the RAR and can also schedule UL resources, known as the initial uplink grant.

[0084] In 3GPP NR, a gNB can transmit up to 64 SSBs and up to 64 corresponding copies of the Physical Downlink Control Channel (PDCCH) and / or Physical Downlink Shared Channel (PDSCH) for SIB1 delivery in high-frequency bands (e.g., 28 GHz). Even under very low traffic load conditions, this can lead to significant network power consumption. According to 3GPP Technical Report (TR) 38.864 (v18.1.0), for network power saving, on-demand SSB and / or SIB1 (SSB / SIB1) transmission and cells without SSB / SIB1 transmission are considered. When a cell does not transmit SSB / SIB1, in order for a UE to access that cell, the UE should obtain the SI of that cell from other associated carriers / cells and synchronize from other associated carriers / cells. When a cell is in an inactive state for an extended period, a UE served by that cell can trigger SSB / SIB1 transmission by sending a request to that cell.

[0085] Figure 2 An example of a protocol stack 200 according to various aspects of this disclosure is illustrated. Although Figure 2 The diagram illustrates UE 206, RAN node 208, and 5G core network (5GC) 210 (e.g., including at least AMF), but these represent a group of UEs 104 interacting with NE 102 (e.g., a base station) and CN 106. As shown, protocol stack 200 includes user plane protocol stack 202 and control plane protocol stack 204. User plane protocol stack 202 includes a physical (PHY) layer 212, a media access control (MAC) sublayer 214, a radio link control (RLC) sublayer 216, a packet data convergence protocol (PDCP) sublayer 218, and a serving data adaptation protocol (SDAP) layer 220. Control plane protocol stack 204 includes PHY layer 212, MAC sublayer 214, RLC sublayer 216, and PDCP sublayer 218. Control plane protocol stack 204 also includes a radio resource control (RRC) layer 222 and a non-access stratum (NAS) layer 224.

[0086] The Access Layer (AS) layer 226 (also referred to as the "AS protocol stack") for the user plane protocol stack 202 consists of at least SDAP, PDCP, RLC, and MAC sublayers, and a physical layer. The AS layer 228 for the control plane protocol stack 204 consists of at least RRC, PDCP, RLC, and MAC sublayers, and a physical layer. Layer 1 (L1) includes the PHY layer 212. Layer 2 (L2) is split into the SDAP layer 220, the PDCP sublayer 218, the RLC sublayer 216, and the MAC sublayer 214. Layer 3 (L3) includes the RRC layer 222 and the NAS layer 224 for the control plane, and includes, for example, the Internet Protocol (IP) layer and / or the PDU layer (not shown) for the user plane. L1 and L2 are referred to as "lower layers," while L3 and above (e.g., transport layer, application layer) are referred to as "higher layers" or "upper layers."

[0087] PHY layer 212 provides a transport channel to MAC sublayer 214. PHY layer 212 can perform beam fault detection procedures using energy detection thresholds, as described herein. In some embodiments, PHY layer 212 can send a beam fault indication to the MAC entity at MAC sublayer 214. MAC sublayer 214 provides a logical channel to RLC sublayer 216. RLC sublayer 216 provides an RLC channel to PDCP sublayer 218. PDCP sublayer 218 provides radio bearers to SDAP sublayer 220 and / or RRC layer 222. SDAP sublayer 220 provides Quality of Service (QoS) flows to the core network (e.g., 5GC). RRC layer 222 provides the addition, modification, and release of carrier aggregation and / or dual connectivity. RRC layer 222 also manages the establishment, configuration, maintenance, and release of signaling radio bearers (SRBs) and data radio bearers (DRBs).

[0088] NAS layer 224 is located between UE 206 and the AMF in 5GC 210. NAS messages are transparently passed through the RAN. NAS layer 224 is used to manage the establishment of communication sessions and to maintain continuous communication with UE 206 when UE 206 moves between different cells in the RAN. In contrast, AS layers 226 and 228 are located between UE 206 and the RAN (i.e., RAN node 208) and carry information through the radio portion of the network. Although Figure 2 It is not described in the text, but the IP layer exists above the NAS layer 224, the transport layer exists above the IP layer, and the application layer exists above the transport layer.

[0089] MAC sublayer 214 is the lowest sublayer in the L2 architecture of the NR protocol stack. Its connection to the PHY layer 212 below is via a transport channel, and its connection to the RLC sublayer 216 above is via a logical channel. Therefore, MAC sublayer 214 performs multiplexing and demultiplexing between the logical and transport channels: the transmitting MAC sublayer 214 constructs a MAC PDU (also known as a transport block (TB)) based on the MAC Service Data Unit (SDU) received via the logical channel, and the receiving MAC sublayer 214 recovers the MAC SDU based on the MAC PDU received via the transport channel.

[0090] MAC sublayer 214 provides data transmission services to RLC sublayer 216 via a logical channel. This logical channel can be a control logical channel carrying control data (e.g., RRC signaling) or a service logical channel carrying user plane data. On the other hand, data from MAC sublayer 214 is exchanged with PHY layer 212 via transport channels classified as UL or downlink (DL). Depending on how the data is transmitted over the air, it is multiplexed into the transport channel.

[0091] PHY layer 212 is responsible for the actual transmission of data and control information via the air interface; that is, PHY layer 212 carries all information from the MAC transport channel on the transmission side through the air interface. Some of the important functions performed by PHY layer 212 include coding and modulation, link adaptation (e.g., Adaptive Modulation and Coding (AMC)), power control, cell search and random access (for initial synchronization and handover purposes), and other measurements for RRC layer 222 (within 3GPP systems (i.e., NR and / or LTE systems) and between systems). PHY layer 212 performs transmission based on transmission parameters such as modulation scheme, coding rate (i.e., modulation and coding scheme (MCS)), number of physical resource blocks (PRBs), etc.

[0092] In some implementations, protocol stack 200 may be the NR protocol stack used in 5G NR systems. It should be noted that the LTE protocol stack includes a similar structure to protocol stack 200, except that the LTE protocol stack lacks the SDAP sublayer 220 in AS layer 226, EPC replaces 5GC 210, and NAS layer 224 is located between the UE 206 and the MME in the EPC. It should also be noted that this disclosure distinguishes between protocol layers (such as the aforementioned PHY layer 212, MAC sublayer 214, RLC sublayer 216, PDCP sublayer 218, SDAP layer 220, RRC layer 222, and NAS layer 224) and transport layers (also referred to as "MIMO layers" or "data streams") in multiple-input multiple-output (MIMO) communication.

[0093] It should be noted that throughout this disclosure, the terms "symbol" and "slot" are terms used to refer to time units with a specific duration. For example, a symbol can be a fraction / percentage of the OFDM symbol length associated with a specific subcarrier spacing (SCS). As another example, a slot can refer to a predetermined set of symbols and can be part of a radio frame. In the following, a UL transmission can consist of multiple transmissions and can include: Physical Uplink Shared Channel (PUSCH) transmissions, Physical Uplink Control Channel (PUCCH) transmissions, PRACH transmissions, scheduling requests (SRs), and / or UL reference signals (RSs), such as sounding reference signals (SRSs).

[0094] Regarding RRC states, 3GPP defines three different RRC states / modes for 5G NR: RRC_IDLE, RRC_INACTIVE, and RRC_CONNECTED. Initially, upon power-up, the UE is in idle mode corresponding to the RRC_IDLE state. Before performing data transmission (including making phone calls), the UE must establish a connection with the network, which is accomplished via the RRC connection establishment procedure using initial access. After the RRC connection is established, the UE is in the RRC_CONNECTED state. The RRC connection can be suspended due to inactivity, in which case the UE transitions to the RRC_INACTIVE state. The RRC connection is released via the RRC release procedure, and the UE transitions to the RRC_IDLE state.

[0095] Regarding random access, two types of RACH procedures are supported in 3GPP wireless communication networks: A) a 4-step RA type initiated by sending RACH message 1 (Msg1); and B) a 2-step RA type using RACH message A (MsgA). Both types of RACH procedures support contention-based random access (CBRA) and contention-free random access (CFRA).

[0096] When initiating the RACH procedure, the UE selects the RA type, for example, based on network configuration. In one example, when CFRA resources are not configured, the RSRP threshold is used by the UE to select between a 2-step RA type and a 4-step RA type. In another example, when CFRA resources for the 4-step RA type are configured, the UE performs random access using the 4-step RA type. In yet another example, when CFRA resources for the 2-step RA type are configured, the UE performs random access using the 2-step RA type.

[0097] It should be noted that for the Bandwidth Partial (BWP), the network will not configure CFRA resources for both 4-step and 2-step RA types simultaneously. Furthermore, CFRA using the 2-step RA type is only supported for handover.

[0098] The 4-step RA type Msg1 consists of a preamble transmitted on the Physical Random Access Channel (PRACH). After the Msg1 transmission, the UE monitors (i.e., attempts to receive and decode) the response from the network within a configured window. For CFRA, a dedicated preamble for the Msg1 transmission is assigned by the network, and the UE terminates the random access procedure after receiving a Random Access Response (RAR) from the network. For CBRA, after receiving the RAR, the UE uses the UL grant scheduled in the RAR to transmit RACH message 3 (Msg3) and monitors for contention resolution. If contention resolution fails after (multiple) Msg3 (re)transmissions, the UE returns to the Msg1 transmission.

[0099] The 2-step RA type MsgA includes a preamble on the PRACH and a payload on the Physical Uplink Shared Channel (PUSCH). After the MsgA transmission, the UE monitors (i.e., attempts to receive and decode) the response from the network within a configured window. For CFRA, dedicated preamble and PUSCH resources are configured for the MsgA transmission, and the UE terminates the random access procedure after receiving the network response. For CBRA, if contention resolution is successful after receiving the network response, the UE terminates the random access procedure; however, if a backoff indication is received in RACH message B (MsgB), the UE performs the Msg3 transmission using the UL grant scheduled in the backoff indication and monitors for contention resolution. If contention resolution fails after (multiple) Msg3 (re)transmissions, the UE returns to the MsgA transmission.

[0100] If a random access procedure using the 2-step RA type is not completed after multiple MsgA transmissions, the UE can be configured to switch to the CBRA using the 4-step RA type.

[0101] Figures 3A to 3E The signaling flow for the RACH procedure supporting different RA types, including CBRA and CFRA, is described.

[0102] Figure 3A The illustration shows a first RACH procedure 300 for a CBRA employing a 4-step RA type according to various aspects of this disclosure. The UE 206 initiates the RACH procedure 300 by sending Msg1, which contains a random access (e.g., PRACH) preamble, to the RAN node 208 (e.g., a gNB or other base station) (see signaling 302). Upon receiving Msg1, the RAN node 208 sends RACH message 2 (Msg2), which contains a RAR message (see signaling 304).

[0103] Based on the RAR content, UE 206 prepares and transmits Msg3 containing the scheduled transmissions (see signaling 306). Since the RACH procedure 300 is a contention-based procedure, there is a possibility that more than one UE may transmit the same random access preamble. Therefore, RAN node 208 transmits RACH message 4 (Msg4) containing a contention resolution message (see signaling 308).

[0104] Figure 3B The illustration shows a second RACH procedure 310 for a CBRA employing a 2-step RA type, according to various aspects of this disclosure. UE 206 initiates RACH procedure 310 by sending MsgA, which includes a random access (e.g., PRACH) preamble (see signaling 312) and a PUSCH payload (see signaling 314), to RAN node 208 (e.g., gNB or other base station). Since RACH procedure 310 is a contention-based procedure, it is possible for more than one UE to send the same random access preamble. Therefore, upon receiving MsgA, RAN node 208 sends MsgB, which includes a contention resolution message (see signaling 316).

[0105] Figure 3C The diagram illustrates a third RACH procedure 320 for CFRA employing a 4-step RA type, according to various aspects of this disclosure. To support CFRA, RAN node 208 (e.g., gNB or other base station) sends a random access preamble (RA preamble) allocation to UE 206 (see signaling 322). Later, UE 206 initiates RACH procedure 320 by sending Msg1 containing the allocated RA preamble to RAN node 208 (see signaling 324). Upon receiving Msg1, RAN node 208 sends Msg2 containing a RAR message (see signaling 326). Although... Figure 3C Not depicted, but UE 206 can then prepare and send Msg3 (or other scheduled transmissions) based on the RAR message. It should be noted that since the RA preamble is assigned to UE 206, contention resolution for CFRA is not required.

[0106] Figure 3DThe illustration shows a fourth RACH procedure 330 for CFRA employing a 2-step RA type according to various aspects of this disclosure. To support CFRA, RAN node 208 (e.g., gNB or other base station) sends an RA preamble allocation to UE 206 (see signaling 332). Later, UE 206 initiates the RACH procedure 330 by sending MsgA to RAN node 208 containing the allocated RA preamble (see signaling 334) and a PUSCH payload (see signaling 336). Upon receiving MsgA, RAN node 208 sends MsgB containing a RAR message (see signaling 338). Although... Figure 3D Not depicted, but UE 206 can then prepare and send the scheduled transmission based on the RAR message. It should be noted that since the RA preamble is assigned to UE 206, contention resolution for CFRA is not required.

[0107] Figure 3E The illustration shows a fifth RACH procedure 340 with backoff for a CBRA employing a 2-step RA type, according to various aspects of this disclosure. UE 206 initiates RACH procedure 310 by sending MsgA to RAN node 208 (e.g., gNB or other base station) containing a random access (e.g., PRACH) preamble (see signaling 342) and a PUSCH payload (see signaling 344). However, in RACH procedure 340, RAN node 208 sends MsgB to UE 206 containing a backoff indication (see signaling 346).

[0108] Therefore, based on the content of MsgB, UE 206 switches to the 4-step RA type and sends Msg3 containing the scheduled transmission (see signaling 348). Since RACH procedure 340 is a contention-based procedure, there is a possibility that more than one UE may send the same random access preamble. Therefore, RAN node 208 sends RACH message 4 (Msg4) containing a contention resolution message (see signaling 350).

[0109] According to various aspects of the first solution, when the energy-efficient, non-anchor cell does not broadcast SIB1, the UE can use a PRACH transmission as an SIB1 request. In one embodiment, the SIB1 request (PRACH transmission) can be sent to the anchor cell. In another embodiment, if the SSB transmission of the non-anchor cell is "ON", the UE can send the SIB1 request (PRACH transmission) to the non-anchor cell. In one example, the UE can be provided with a list of valid areas, which includes a list of frequencies, and optionally, for each frequency, a list of cells within which the UE can send the SIB1 request.

[0110] In some embodiments, the PRACH resources requested for SIB1 can be pre-configured or configured (e.g., by the anchor cell). Alternatively, the PRACH resources requested for SIB1 may be known to the UE through specifications or provisioning by the network (e.g., for the home PLMN). Similarly, the configuration for receiving Msg2 (e.g., ra-ResponseWindow Public control resource set (CORESET, etc.) and included in Downlink configuration public Information in the SIB (including frequency information DL and initial DLBWP, etc.) can be pre-configured, configured (e.g. by the anchor cell), known through specifications, or provided by the network.

[0111] If the SIB1 request is for the anchor cell, the PRACH resource used signals to the network that the UE is requesting SIB1 information for a neighboring cell, or Msg3 can be used to signal which cell the SIB1 request is for (e.g., using the Physical Cell Identifier (PCID) and / or frequency indication). Alternatively, according to the foregoing, MsgA can be used instead of Msg1 / Msg3 to request SIB1 for a specific cell.

[0112] As one implementation, an RRC idle UE only uses Msg1 to request SIB1. However, if the requesting UE is an RRC inactive UE, it can use MsgA to be able to include its recovery ID, for example, if the requesting UE has a valid UL timing alignment, thus allowing the use of the Small Data Transmission (SDT) feature.

[0113] Furthermore, for the DL RSRP of the highest-ranking SSB measurements configured, anchor cell measurements can be used if SSBs in non-anchor cells are not periodically transmitted. Here, the use of Msg1 or MsgA can also be configurable by the anchor cell. If the UE cannot access the anchor cell (or its coverage area), a default behavior can be used, i.e., the UE always uses Msg1 (or MsgA). In such embodiments, the default behavior can be specified / pre-configured.

[0114] In some implementations where only Msg1 is available, an indication may be included that signals whether the requesting UE is an RRC idle UE or an RRC inactive UE. This information helps the serving cell determine which SIB1 information should be provided to the requesting UE. For example, the network may not provide RRC idle UEs with SIB1 information that is only applicable to RRC inactive UEs (e.g., using the full recovery ID, some SIB1 information applicable only to RRC inactive UEs). ue-Timers and constant parameter, sdt-Config Common Similarly, the network will only provide relevant information to inactive UEs under RRC.

[0115] In some implementations where only Msg1 is available, PRACH resource partitioning can be used to distinguish between RRC idle UEs and RRC inactive UEs. For example, certain PRACH preambles and / or time-frequency resources can be indicated / allocated for use by RRC idle UEs, while different PRACH preambles and / or time-frequency resources can be indicated / allocated for use by RRC inactive UEs.

[0116] For cases where MsgA is required, in some implementations, inactive RRC UEs will include their recovery ID (e.g., Inactive Radio Network Temporary Identifier (I-RNTI)). In such implementations, idle RRC UEs (lacking a recovery ID / I-RNTI) may include a virtual / special I-RNTI, for example, where all bits are set to "1" (alternatively, set to "0").

[0117] In some embodiments, resources for PRACH transmission can be provided to the UE by the anchor cell. Alternatively, particularly if the UE cannot access the anchor cell, but cell search reveals a power-efficient, non-anchor cell (i.e., a cell that periodically broadcasts SIB1), the UE can use a default configuration (e.g., pre-configured and / or specified) for PRACH transmission and Msg2 reception. For example, this could be multiple PRACH preambles (e.g., UL reference signals) and time-frequency resources reserved for this use, such that the combination of preambles and time-frequency resources used reveals the optimal downlink beam (SSB) for the UE to the network.

[0118] If the cell is transmitting SSB / PBCH, the actual PRACH transmission to the SIB1 requirement (which is also PUSCH in the case of MsgA) can be performed on the non-anchor cell (i.e., the cell that does not provide SIB1). Otherwise, the PRACH transmission (which is also PUSCH in the case of MsgA) is performed on the anchor cell.

[0119] If one or more non-anchor cells are transmitting SSBs, the UE will perform a measurement based on radio quality satisfaction (e.g., based on a new radio threshold comparison, or even cell selection criteria) after the initial measurement. S (As described below) can be reused for this purpose to select one or more non-anchor cells among such non-anchor cells to request SIB1. In this case, it will include the PCID of each of these non-anchor cells in MsgA / Msg3 used for the SIB1 request.

[0120] In different implementations, the UE sends an SIB1 request for only one cell at a time, starting with the best radio candidate. If, after receiving an SIB1, the requesting UE cannot select a suitable cell, the UE can continue to request SIB1s for the next candidate (e.g., in order of radio quality).

[0121] According to various aspects of the second solution, the network includes SIB1 information in the MsgB transmission. To improve the resource efficiency of SIB1 delivery via MsgB, the provided SIB1 information may be a subset of SIB1 information broadcast "periodically". For example, the subset of SIB1 information sent in MsgB may include one or more of the following: cell selection information, cell access related information, etc. si-Scheduling Information and services The community is equipped with public facilities , IMS-Emergency support IMS support for eCall, and some other features ue-Timers and constants Prohibited information.

[0122] As an enhancement, the distribution of SIB1 information can be based on the actual needs of the requesting UE, which ultimately depends on the requesting UE's RRC state and its UE type (e.g., REDCAP UE, NTN UE, etc.). To this end, some restricted broad categories can be specified or configured to indicate which category the UE selects and signals in Msg1 / MsgA. This restricted classification helps the network determine which subset of the "regular" SIB1 information needs to be provided to the requesting UE in the MsgB PDSCH portion. In this case, MsgB includes a MAC subheader and MAC SDU for the Common Control Channel (CCCH), which contains the required SIB1 information. In some embodiments, MsgB is transmitted by the same cell as the one receiving the MsgA request including the SIB1 request.

[0123] In some embodiments, the UE sends MsgA to the anchor cell. Here, upon receiving an SIB1 request for a specific neighbor, the anchor cell notifies its non-anchor cell neighbors of the SIB1 request (via the F1 DU-CU interface or through Xn). The information sent by the anchor cell may include MsgB-RNTI, ra - ResponseWindow The start and length of the MsgB transmission, the DL beam to be used for MsgB transmission (or alternatively, the UL beam to be used by the UE for MsgA transmission), and the MsgA content (e.g., the UE's RRC status, the selected SIB1 category, the UE type, etc.).

[0124] After receiving this information, the non-anchor cell can attempt to include the necessary SIB1 information in the MsgB, and ra - ResponseWindowIt then sends it to the UE. As an enhancement, in this case, ra - ResponseWindow It can be started after a configurable / specified time following the MsgA transfer, instead of starting immediately.

[0125] Figure 4 An exemplary process 400 for SIB1 delivery according to various aspects of this disclosure is illustrated. Process 400 involves UE 402 (e.g., embodiments of UE 104 and / or UE 206), anchor cell 404 (e.g., implemented by NE 102 and / or RAN node 208), and non-anchor cell 406 (e.g., implemented by NE 102 and / or RAN node 208). In the depicted embodiment, the anchor cell uses MsgB to provide non-anchor SIB1.

[0126] In step 1, anchor cell 404 determines the SSB / SIB1 request configuration associated with non-anchor cell 406 (see box 408).

[0127] In step 2, UE 402 sends MsgA to anchor cell 404, where MsgA includes an SSB / SIB1 request (see signaling 410).

[0128] In conditional step 3, if the SSB has not been previously sent "regularly" in the non-anchor cell 406 (e.g., in the case where the non-anchor cell 406 has an irregular SSB transmission pattern), the anchor cell 404 sends an SSB request to the non-anchor cell 406 (see signaling 412). Here, the anchor cell 404 requests the non-anchor cell 406 to send the SSB / PBCH.

[0129] In conditional step 4, if the SSB has not been previously “regularly” sent in non-anchor cell 406, non-anchor cell 406 initiates an SSB / PBCH transmission (see signaling 414).

[0130] In step 5, anchor cell 404 sends MsgB to UE 402, wherein MsgB includes SIB1 of non-anchor cell 406 (see signaling 416). In various embodiments, UE 402 receiving MsgB including SIB1 of non-anchor cell 406 may assume that SSB transmission of non-anchor cell 406 exists / is sent after the last time slot of MsgB reception (plus processing time).

[0131] As an enhancement to the process described above, only a portion of the regular SIB1 information of non-anchor cell 406 is provided in MsgB (e.g., included). In such embodiments, the remaining SIB1 not included in MsgB can be determined based on values ​​provided by anchor cell 404 (i.e., periodically broadcast).

[0132] According to various aspects of the third solution, the UE can use a Msg1-based SIB1 request, whereby, after sending Msg1, the UE is requested to monitor SIB1 transmissions in non-anchor cells. In various embodiments, the UE is requested to attempt to acquire SIB1 in non-anchor cells based on conventional principles, i.e., the Master Information Block (MIB) sent on the PBCH provides the UE with parameters (e.g., CORESET#0 configuration) for monitoring the PDCCH to schedule the PDSCH carrying SIB1.

[0133] In some embodiments, the PBCH transmission may also indicate the absence of an associated SIB1, in which case the UE may be directed to search for another frequency on which an SSB associated with SIB1 exists, and in which the UE may assume that no SSB associated with SIB1 exists within a frequency range. In some embodiments, the indicated frequency range may be limited to consecutive spectrum allocations of the same operator in which the SSB is detected.

[0134] In some embodiments, if SIB1 is not broadcast by a non-anchor cell within a defined time period (e.g., the next 20ms), the UE retransmits the SIB1 request. In some embodiments, SIB1 is transmitted on the DL-SCH (transmission channel) with a period of 160ms and a variable transmission repetition period within 160ms. It should be noted that the default transmission repetition period for SIB1 is 20ms, but the actual transmission repetition period depends on the network implementation.

[0135] In some embodiments, the UE is requested to issue an SIB1 request to a non-anchor cell. In other embodiments, the UE is requested to issue an SIB1 request to an anchor cell, in which case the anchor cell needs to relay relevant information to the non-anchor cell. Therefore, upon receiving an SIB1 request for a specific neighbor, the anchor call notifies the non-anchor neighbor cell of the SIB1 request, including RA-RNTI, based on the reserved PRACH resources used by the UE for Msg1 transmission (e.g., via the F1 DU-CU interface or through Xn). ra- ResponseWindow The start and length of the Msg2 transmission, the DL beam to be used for Msg2 transmission (or alternatively, the UL beam to be used by the UE for Msg1 transmission), the Msg1 content, such as the UE's RRC status, the selected SIB1 category, the UE type, etc. ra - ResponseWindow It can be started after a configurable / specified time following the Msg1 transfer, instead of starting immediately.

[0136] Figure 5An exemplary process 500 for SIB1 delivery according to various aspects of this disclosure is illustrated. Process 500 involves UE 502 (e.g., embodiments of UE 104 and / or UE 206), anchor cell 504 (e.g., implemented by NE 102 and / or RAN node 208), and non-anchor cell 506 (e.g., implemented by NE 102 and / or RAN node 208). In the depicted embodiment, non-anchor cell 504 broadcasts SIB1 after receiving a request from UE 502 via anchor cell 504.

[0137] In step 1, anchor cell 504 determines the SSB / SIB1 request configuration associated with non-anchor cell 506 (see box 508).

[0138] In step 2, UE 502 sends an SSB / SIB1 request to anchor cell 504 (see signaling 510). In some embodiments, the SIB1 request may be included in a RACH message, such as Msg1.

[0139] In step 3, anchor cell 504 notifies non-anchor cell 506 of the SSB / SIB1 request (see signaling 512). In one embodiment, anchor cell 504 forwards the SSB / SIB1 request received in step 2. In another embodiment, anchor cell 504 sends a second (independent) SSB / SIB1 request message based on the SSB / SIB1 request received in step 2.

[0140] In step 4, non-anchor cell 506 sends SSB and / or SIB1 to UE 502 (see signaling 514).

[0141] In various embodiments, UE 502 receiving MsgB, including SIB1 of non-anchor cell 506, may assume that SSB transmission of non-anchor cell 506 exists / is sent after the last time slot of MsgB reception (plus processing time).

[0142] As an enhancement, only a portion of the regular SIB1 information of non-anchor cell 506 is provided (e.g., included) in MsgB. In such embodiments, the remaining SIB1 not included in MsgB can be determined based on values ​​provided by anchor cell 504 (i.e., periodically broadcast).

[0143] In a variation of the above process, the SSB / SIB1 request sent by UE 502 includes multiple Physical Cell Identifiers (PCIDs). In this case, anchor cell 504 notifies each requested non-anchor cell 506 to begin broadcasting SIB1. After the SIB1 request is transmitted, UE 502 begins acquiring the SIB1 broadcast transmission.

[0144] In one embodiment, UE 502 may first acquire SIB1 from the cell with the best radio quality (e.g., based on SSB measurements) and attempt to camp on the cell with the best radio quality as a suitable cell. However, if the cell with the best radio quality is not suitable for camping, UE 502 may then attempt to acquire SIB1 for the next cell (i.e., in order of radio quality). Alternatively, if UE 502 fails to acquire SIB1 for one of the cells that has already been requested, UE 503 may simply re-request SIB1 for that cell. Furthermore, if UE 502 continues to fail to acquire SIB1 for one of the cells that has already been requested (i.e., after a certain number of attempts or within a time period), UE 502 may consider that cell to be blocked (e.g., within 300 seconds).

[0145] According to various aspects of the fourth solution, when Msg1 is used for an SIB1 request, Msg2 may only contain a MAC subheader with the Random Access Preamble ID (RAPID), i.e., an acknowledgment (ACK) of the System Information (SI) request. It should be noted that the fourth solution is proposed as an alternative to the above solutions, where Msg2 also contains the RAR payload UL authorization. Because Msg1 is used for the SIB1 request, UL authorization is not required. In various embodiments, the UE waits for an ACK received from the receiving network for Msg1 before retransmitting the SIB1 request. As mentioned above, the ACK may be Msg2 containing only the preamble ID included in Msg1.

[0146] In this scenario, after receiving the ACK, the UE does not resend the SIB1 request. Instead, it attempts to obtain SIB1 based on conventional principles. That is, the MIB sent on the PBCH provides the UE with parameters (e.g., CORESET#0 configuration) for monitoring the PDCCH to schedule the PDSCH carrying SIB1.

[0147] In some embodiments, the PBCH transmission may also indicate the absence of an associated SIB1, in which case the UE may be directed to search for another frequency on which an SSB associated with SIB1 exists, and in which the UE may assume that no SSB associated with SIB1 exists within a frequency range. In some embodiments, the indicated frequency range is limited to consecutive spectrum allocations of the same operator in which the SSB is detected.

[0148] In some embodiments, the network transmits SIB1 on the DL-SCH with a period of 160ms and a variable transmission repetition period within 160ms. In some embodiments, the default transmission repetition period for SIB1 is 20ms, but the actual transmission repetition period depends on the network implementation.

[0149] To reiterate, after Msg1 is transmitted, the UE waits for ACK (Msg2) before attempting to receive SIB1 from the non-anchor cell via broadcast. If SIB1 is not received after a specific time, the UE retransmits the SIB1 request. Additionally, if SIB1 is not received after a configured number of attempts, the UE considers the cell blocked (e.g., 300 seconds).

[0150] Refer again Figure 5 In one variant, the SSB / SIB1 request sent by UE 502 includes multiple PCIDs. In this case, anchor cell 504 notifies each requested non-anchor cell 506 to begin broadcasting SIB1. Additionally, anchor cell 504 sends an ACK to UE 502 for the SSB / SIB1 request. Upon receiving the ACK, UE 502 begins acquiring SIB1 broadcast transmissions.

[0151] In one embodiment, UE 502 may first acquire SIB1 from the cell with the best radio quality (e.g., based on SSB measurements) and attempt to camp on the cell with the best radio quality as a suitable cell. However, if the cell with the best radio quality is not suitable for camping, UE 502 may then attempt to acquire SIB1 for the next cell (i.e., in order of radio quality). Alternatively, if UE 502 fails to acquire SIB1 for one of the cells that has already been requested, UE 503 may simply re-request SIB1 for that cell. Furthermore, if UE 502 continues to fail to acquire SIB1 for one of the cells that has already been requested (i.e., after a certain number of attempts or within a time period), UE 502 may consider that cell to be blocked.

[0152] In various embodiments, anchor cell 504 can provide the necessary PBCH to neighboring non-anchor cell 506, thereby providing the UE with parameters (e.g., CORESET#0 configuration) for monitoring PDCCH to schedule PDSCH carrying SIB1. In this case, non-anchor cell 506 does not need to periodically broadcast MIB, and MIB can be provided to the UE in response to an SIB1 request. In such embodiments, signaling 508 can be considered as an MIB / SIB1 request.

[0153] According to various aspects of the fifth solution, upon receiving an SIB1 request, the network may use paging to indicate that SIB1 is currently being broadcast, directly provide a portion of the SIB1 information, and / or provide the information required to receive SIB1. In various embodiments, the SIB1 request may be based on Msg1 and / or Msg3, as described above. In other embodiments, the SIB1 request may be based on MsgA, as described above.

[0154] In some embodiments, an SIB1 request for a non-anchor cell may be issued to the non-anchor cell itself. In other embodiments, an SIB1 request for a non-anchor cell may be issued to the anchor cell, which may then forward the request to the non-anchor cell via a backhaul, as described above. In some embodiments, an SIB1 paging may be sent by the anchor cell. In other embodiments, an SIB1 paging may be sent by the non-anchor cell.

[0155] Figure 6 An exemplary procedure 600 for obtaining SIB1 according to various aspects of this disclosure is illustrated. Procedure 600 involves UE 602 (e.g., embodiments of UE 104 and / or UE 206), anchor cell 604 (e.g., implemented by NE 102 and / or RAN node 208), and non-anchor cell 606 (e.g., implemented by NE 102 and / or RAN node 208). In the depicted embodiment, UE 602 sends a RACH message (e.g., MsgA) to anchor cell 604, and anchor cell 604 pagees UE 602 to obtain SIB1 from non-anchor cell 606.

[0156] In step 1, anchor cell 604 determines the paging configuration associated with anchor cell 604 and the SIB1 request configuration associated with non-anchor cell 606 (see box 608). Anchor cell 604 broadcasts this configuration information, and UE 602 receives the broadcast (see signaling 610).

[0157] In step 2, UE 602 sends MsgA to anchor cell 604, where MsgA includes an SSB / SIB1 request (see signaling 612).

[0158] In conditional step 3, if the SSB has not been previously sent "regularly" in non-anchor cell 606, anchor cell 604 sends an SSB request to non-anchor cell 606 (see signaling 614). Here, anchor cell 604 requests non-anchor cell 606 to send SSB / PBCH.

[0159] In conditional step 4, if the SSB has not been previously sent "regularly" in non-anchor cell 606 (e.g., if non-anchor cell 606 has an irregular SSB transmission pattern), then non-anchor cell 606 initiates an SSB transmission (see signaling 616).

[0160] In step 5, anchor cell 604 sends a paging message to UE 602, wherein the paging message is used for SIB1 acquisition (see signaling 618). In some embodiments, the paging message from the anchor cell uses a special / new paging radio network temporary identifier (P-RNTI), as discussed in further detail below. In various embodiments, UE 602 receiving the paging message for SIB1 acquisition may assume that SSB transmission from a non-anchor cell exists / is being transmitted, for example, starting after the last time slot of the paging message reception (plus processing time).

[0161] In step 6, non-anchor cell 606 sends SIB1 (see signaling 620).

[0162] Figure 7 An exemplary process 700 for obtaining SIB1 according to various aspects of this disclosure is illustrated. Process 700 involves UE 702 (e.g., embodiments of UE 104 and / or UE 206), anchor cell 704 (e.g., implemented by NE 102 and / or RAN node 208), and non-anchor cell 706 (e.g., implemented by NE 102 and / or RAN node 208). In the depicted embodiment, UE 702 sends a RACH message (e.g., MsgA) to non-anchor cell 706, and non-anchor cell 706 pagees UE 702 to obtain SIB1 of non-anchor cell 706.

[0163] In step 1, non-anchor cell 706 sends SSB and / or MIB, and UE 702 receives the transmission (see signaling 708).

[0164] In step 2, anchor cell 704 determines the paging configuration associated with anchor cell 704 and the SIB1 request configuration associated with non-anchor cell 706 (see box 710). Anchor cell 704 broadcasts this configuration information, and UE 702 receives the broadcast (see signaling 712).

[0165] In step 3, UE 702 sends MsgA to non-anchor cell 706, where MsgA includes an SSB / SIB1 request (see signaling 714).

[0166] In step 4, non-anchor cell 706 sends a paging message to UE 702, wherein the paging message is used for SIB1 acquisition (see signaling 716).

[0167] In step 5, non-anchor cell 706 sends SIB1 (see signaling 718).

[0168] Figure 8An exemplary procedure 800 for obtaining SIB1 according to various aspects of this disclosure is illustrated. Procedure 800 involves UE 802 (e.g., embodiments of UE 104 and / or UE 206), anchor cell 804 (e.g., implemented by NE 102 and / or RAN node 208), and non-anchor cell 806 (e.g., implemented by NE 102 and / or RAN node 208). In the depicted embodiment, UE 802 sends a RACH message (e.g., MsgA) to anchor cell 804, and non-anchor cell 806 pagees UE 802 to obtain SIB1 of non-anchor cell 806.

[0169] In step 1, non-anchor cell 806 sends SSB and / or MIB, and UE 802 receives the transmission (see signaling 808).

[0170] In step 2, anchor cell 804 determines the paging configuration associated with anchor cell 804 and the SIB1 request configuration associated with non-anchor cell 806 (see box 810). Anchor cell 804 broadcasts this configuration information, and UE 802 receives the broadcast (see signaling 812).

[0171] In step 3, UE 802 sends MsgA to anchor cell 804, where MsgA includes an SSB / SIB1 request (see signaling 814).

[0172] In step 4, anchor cell 804 notifies non-anchor cell 806 of the SSB / SIB1 request (see signaling 816). In one embodiment, anchor cell 804 forwards the SSB / SIB1 request received in step 3. In another embodiment, anchor cell 804 sends a second (independent) SSB / SIB1 request message based on the SSB / SIB1 request received in step 3.

[0173] In conditional step 5, if the SSB / MIB has not been previously sent "regularly" in the non-anchor cell (e.g., if the non-anchor cell 806 has an irregular SSB transmission pattern), the non-anchor cell 806 initiates an SSB / MIB transmission (see signaling 818).

[0174] In step 6, non-anchor cell 806 sends a paging message to UE 802, wherein the paging message is used for SIB1 acquisition (see signaling 820).

[0175] In step 7, non-anchor cell 806 sends SIB1 (see signaling 822).

[0176] In some embodiments, configuration information for sending SIB1 requests from non-anchor cells and receiving SIB1 paging directly from non-anchor cells (e.g., RNTI, search space and CORESET configuration for receiving paging DCI, and configuration for calculating paging timing) is provided. PCCH-Config For example, configuration information (as defined in 3GPP Technical Specification (TS) 38.331) can be provided by the anchor cell (or can be pre-configured / specified). In some embodiments, the configuration information used to receive SIB1 paging can be the same as the information used to receive paging in the anchor cell, or configured with some kind of increment on top (where the difference between the two configurations is signaled). If SIB1 paging will be received in the anchor cell, much of the traditional paging configuration can be reused, except for the new RNTI in some examples, as further explained.

[0177] If the UE includes its paging identifier in the SIB1 request, the network can send SIB1-related paging only when the UE is paging. The UE's paging identifier includes the UE_ID, and if the UE is operating in eDRX, the paging identifier also includes 5G-S-TMSI, modulo 4096. Otherwise (i.e., if the UE is not operating in eDRX), the paging identifier includes 5G-S-TMSI, modulo 1024. If the UE does not have a 5G-S-TMSI, for example when the UE has not yet registered on the network, the UE uses a default identifier, for example, UE_ID=0.

[0178] Alternatively, for SIB1-related paging purposes, the default identifier UE_ID=0 can be used, regardless of the UE-specific 5G-S-TMSI value (if any). This alternative also allows other UEs interested in receiving SIB1 to check whether SIB1 is being transmitted using the paging-based techniques described herein, without first sending an SIB1 request.

[0179] According to the first set of embodiments of the fifth solution, in order to indicate that SIB1 “now” is being broadcast from a non-anchor cell, the SIB1 paging message can be sent on the PDCCH using a P-RNTI, with or without an associated paging message using the short message field in DCI format 1_0. Non-anchor cells can reuse the paging P-RNTI, while anchor cells can use a new paging RNTI for this purpose, such as P-RNTI-2. Table 1 describes the conventional short messages (8 bits) used by the paging DCI. Table 1

[0180] In some embodiments, non-anchor cells can reuse bit 1 (i.e., as shown in Table 1). systemInfoModificationThe bit 1 in the short message field indicates that SIB1 from the non-anchor cell is being broadcast "now"; therefore, for a UE sending an SIB1 request, if set to "1", bit 1 in the short message field means that SIB1 is being broadcast now. In other embodiments, the non-anchor cell may use one of bits 5-8 to signal to the UE that SIB1 is being broadcast by the non-anchor cell.

[0181] Similarly, the anchor cell can also use one of bits 5-8 to directly page a UE within its cell to find the SIB1 of a specific neighboring (non-anchor) cell. In this case, the UE served by the anchor cell (which does not seek the SIB1 of a neighboring cell) takes no action. Alternatively, even the anchor cell can reuse bit 1 for the same purpose when using the SIB1-related paging identifier (denoted as "P-RNTI-2"), i.e., " systemInfoModification "and will not affect UEs served by anchor cells."

[0182] To further illustrate this example implementation, the paging DCI is transmitted by the anchor cell, and the P-RNTI used for the non-anchor cell SIB transmission indication can be different from the paging identifier (i.e., P-RNTI-2) associated with SIB1 used by the anchor cell to page its own served UE. The paging DCI content (including short messages) can be reused to indicate the SIB1 and SI being broadcast by the non-anchor / neighboring cell (or, for example, to be broadcast from the next modification period (calculated based on anchor cell parameters), as well as other parameters associated with the non-anchor cell (e.g., SSB subcarrier spacing, frequency information, physical cell identifier, or indications of one or more sets of parameters configured on the anchor cell for the non-anchor cell).

[0183] In another implementation of this example, the paging DCI is sent by the anchor cell, and the reserved field in the short message indicator (bit field "00") in the paging DCI is used to page the UE in its cell to find the SIB1 of a specific non-anchor / neighboring cell that SIB1 is being / will be broadcast by the non-anchor cell.

[0184] In another example, fields in the short message indicator (e.g., the reserved bit field "00") in the paging DCI are used to indicate that the short message includes SI information for the non-anchor cell. Here, the 8-bit short message content can be reused to indicate SIB1 and SI being / will be broadcast by the non-anchor cell, as well as other parameters associated with the non-anchor cell (e.g., SSB subcarrier spacing, frequency information, physical cell identifier, or an indication of one or more sets of parameters configured on the anchor cell for the non-anchor cell). Table 2 describes the conventional short message indicator fields (2 bits) in the paging DCI. Table 2

[0185] As mentioned above, the reserved field (bit field "00") in the short message indicator in the paging DCI can be used to indicate that the short message includes SI information for non-anchor cells.

[0186] In one variant, the SIB request in MsgA includes multiple PCIDs. In this case, the anchor cell notifies each requested non-anchor cell to begin broadcasting SIB1. After the SIB1 request is transmitted, the UE waits to receive a paging message. Upon receipt, the UE may first acquire SIB1 from the cell with the best radio quality (e.g., based on SSB measurements) and attempt to camp on the cell with the best radio quality as the appropriate cell. However, if this does not work, the UE is requested to continue acquiring SIB1 for the next cell (i.e., in order of radio quality). Additionally, if the requesting UE fails to acquire SIB1 for one of the already requested cells, the UE may re-request SIB1 for only that cell. Furthermore, if the requesting UE continues to fail to acquire SIB1 for one of the already requested cells within a certain number of times or time period, the UE may consider that cell to be blocked (e.g., 300 seconds).

[0187] Furthermore, the network can extend paging messages, and the extensions created therefrom can be used to send SIB1 (or related portions thereof) of non-anchor cells to the UE. Inventors Prateek Basu Mallick, Ravi Kuchibhotla, JoachimLoehr, Genadi Velev, and Hyung-Nam Choi describe various techniques for paging extensions in U.S. Patent Application Publication 2023 / 0300794 A1, which is incorporated herein by reference. Some examples of paging message extensions are provided below:

[0188] According to the second set of embodiments of the fifth solution, the paging DCI (i.e., DCI format 1_0 with cyclic redundancy check (CRC) scrambled by P-RNTI) is reused / reused. For example, in DCI format 1_0, at least 6 bits are already available as "reserved bits". In addition, when "Short Messages" are not included, an additional 8 bits become available. Even if "Short Messages" are actually included, the remaining bits of the Short Message (e.g., from section 6.5 of 3GPP TS 38.331) can also be used for this purpose.

[0189] Therefore, the current traditional DCI format 1_0 has a minimum of 6 bits and a maximum of 14 bits available for SIB1 related information in the paging DCI. Furthermore, if the actual RRC paging message in the PDSCH does not need to be sent, then the IE "frequency domain resource allocation" and "time domain resource allocation" are also unnecessary. Therefore, some of these bits (e.g., 'N' bits) can be used to send SIB1 (or related portions thereof) of the non-anchor cell to the UE.

[0190] Alternatively, some of these available bits can be encoded in various ways to carry up to 2^N lines of information, each indicating some combinations of SIB1 IEs. Here, it is necessary to specify, store, or pre-configure a SIB1 IE for each possible combination for the UE, for example, as an indexed table. In one example, when 100 such combinations are defined, one of these combinations is signaled to the UE using 7 bits (i.e., out of the aforementioned "N" bits). Upon receiving the short message, the UE checks the stored table and then uses the SIB1 parameters corresponding to the index entry pointed to by the 7 bits.

[0191] When a valid DCI with P-RNTI is detected, certain fields exist in the corresponding DCI, as shown in Table 3: Table 3: Fields in Paging DCI

[0192] According to another variation of the second set of embodiments of the fifth solution, in conjunction with one of the disclosed techniques, the PDSCH resources allocated in the paging DCI can be used to actually signal a portion of the SIB1 content of the non-anchor cell.

[0193] According to the third set of embodiments of the fifth solution, the short message field in DCI format 1_0 can indicate the necessary information from the MIB in the DCI during paging (only the information required for non-anchor cell SIB1 is needed). This information will include one or more of the following: 1) subCarrierSpacingCommon ,2) dmrs-TypeA-Position ,3) ssb- SubcarrierOffset , and 4) from non-anchor cell MIBs pdcch-ConfigSIB1 .

[0194] It should be noted that the various aspects of the paging implementation described above can be applied to both anchor cells and non-anchor cells to send a paging message to the UE. For example, after receiving a SIB1 request from the UE to a non-anchor cell, the paging message can be sent directly by the anchor cell (in various forms, such as short message-based methods, RRC paging messages, etc.).

[0195] According to various aspects of the sixth solution, a UE in an RRC inactive state can use the Small Data Transfer (SDT) procedure to acquire SIB1. The SDT procedure allows data and / or signaling transfers while the UE remains in the RRC_INACTIVE state (i.e., supporting data / signaling transfers without transitioning to the RRC_CONNECTED state). In various embodiments, the SDT procedure is considered to be enabled for SIB1 requests. In some embodiments, certain SDT constraints, such as UL data volume and DL RSRP, can be ignored for SIB1 requests; alternatively, specific thresholds can be used for new SIB1 requests.

[0196] The SDT process configures authorized (CG) resources via RACH (configured via system information) or Type 1 (e.g., via...). RRCRelease Transmissions are initiated on a carrier configured with dedicated signaling in the message. Here, SDT resources can be configured on the initial BWP for both RACH and CG. In various embodiments, RACH and CG resources for SDT can be configured on either (or both) the Supplemental Uplink (SUL) and Normal (i.e., Non-Supplemental) Uplink (NUL) carriers.

[0197] In some embodiments, when there is a suspend indication RRCRelease When a message is received, the CG resources used for SDT are only valid within the UE's primary cell (PCell). CG resources are associated with one or more SSBs. For RACH, the network can configure 2-step and / or 4-step RA resources for SDT. When 2-step and 4-step RA resources for SDT are configured, the UE selects the RA type accordingly.

[0198] In some embodiments, CFRA can also be supported for SDT-based SIB1 requests on RACH. In some embodiments, the SIB1 request may include a recovery ID in MsgA or Msg3, for example, a recovery request (or RRCResumeRequest1 If the anchor cell configuration or specification includes a complete recovery ID (which may contain a new recovery reason value for the SIB1 request), or if the LCID is retained for the SIB1 request, the retained LCID is included by the MAC carrying the recovery request. Alternatively, a new RRC CCCH message may be used for the SIB1 request.

[0199] In some embodiments, AS security may not apply to SDT-based SIB1 requests. In some embodiments, upon receiving an SDT-based SIB1 request, the network may schedule DL data containing the requested SIB1 to the UE within an ongoing SDT session.

[0200] In some embodiments, the SDT procedure can be initiated on an anchor cell (indicating which cell the SIB1 request is being sent to) or a non-anchor cell. If the UE has valid CG resources for any of these cells, the UE can decide to send an SDT-based SIB1 request to that cell. In some embodiments, when supported, the UE configuration can indicate a preference for SDT-based SIB1 requests.

[0201] According to various aspects of the seventh solution, after any of the previously disclosed techniques are used to request and receive SIB1 from a non-anchor cell, the non-anchor cell will not continue to send SIB1 according to conventional behavior. Instead, in order to support network energy conservation, the non-anchor cell will provide SIB1 a certain number of times (e.g., within a full modification period) and then stop sending SIB1. Thereafter, new UEs entering the next modification period will be required to send SIB1 requests.

[0202] In some embodiments, a UE that has already acquired SIB1 does not need to continuously monitor the SIB1 broadcast to ensure it has a valid version of the basic system information (e.g., included in the MIB and SIB1). Instead, a UE that has already acquired SIB1 continues to monitor the paging channel, and in the absence of systemInfoModification In such cases, it will continue to assume that it has a valid version of SIB1.

[0203] Therefore, the network has an obligation to: a) paging the UE (including systemInfoModification Alternatively, for this purpose, another available bit may be included in the paging DCI, as previously described, reusing bits in the DCI; and b) SIB1 may be broadcast when the content should change. This avoids the need for currently idle / inactive UEs to re-request SIB1. In one example, the broadcast of SIB1 can still be based on at least one UE requesting SIB1.

[0204] Therefore, from the perspective of a UE that has already acquired SIB1 in a non-anchor cell, the UE first attempts to receive SIB1 broadcasts, for example, upon receiving paging DCIs (including...). systemInfoModification After that, if SIB1 is not broadcast, then an SIB1 request is issued.

[0205] According to various aspects of the eighth solution, in order to optimize broadcast signaling, information for obtaining SIB1 for energy-efficient non-anchor cells is broadcast in the anchor cell's SIB1, i.e., as a separate IE or a list of such IEs, one IE for each non-anchor cell. In some embodiments, the anchor cell may also signal the SIB1-Request configuration (e.g., PRACH configuration or another reference signal configuration) to each non-anchor cell.

[0206] In its simplest form, the IE can be a Boolean flag indicating the presence (i.e., yes / no) of at least one overlapping / adjacent non-anchor cell, specifically a cell that broadcasts SIB1 intermittently. In a variant, the Boolean flag (or a second such flag in the IE) can also indicate whether the corresponding non-anchor cell (with a specific PCID) is "currently" broadcasting SIB1. In this case, the SIB1 broadcast must continue until the end of the current modification period (calculated based on the anchor cell parameters).

[0207] In addition, the IE may include one or more of the following: frequency information, PCID, SSB subcarrier spacing, tracking area code (TAC), public land mobile network (PLMN) ID of the non-anchor cell, and configuration for receiving Msg2 (e.g., ra- ResponseWindow Public control resource set (CORESET, etc.) and included in Downlink configuration public Information in the SIB (including frequency information DL and initial DL BWP, etc.).

[0208] Because SIB1 transmission introduces a very high signaling load, SIB1 is broadcast approximately every 20ms. In the improved embodiment described above, limited information about SIB1 for only the (multiple) non-anchor cells is included in the anchor cell's SIB1, and the remaining information about the (multiple) non-anchor cells' SIB1 is included in a new SIB for this purpose. Here, the new SIB can be configured as needed.

[0209] In such embodiments, the anchor cell's SIB1 indicates the Boolean presence of at least one overlapping / adjacent non-anchor cell, and may also indicate that remaining information can be broadcast in the new SIB. As an optimization, the presence of scheduling information in the new SIB implicitly indicates to the UE that at least one overlapping / adjacent non-anchor cell is nearby, rather than broadcasting a Boolean flag indicating the presence (i.e., yes / no) of at least one overlapping / adjacent non-anchor cell.

[0210] According to various aspects of the ninth solution, one or more triggers are disclosed that the UE can use to determine whether it should begin searching for a non-anchor cell / carrier. This is done according to 3GPP TS 38.304 when no suitable available cell exists; or alternatively, when no detected cell meets the cell selection criteria. S At this time, the UE can determine that it should start searching for non-anchor cells (e.g., as described in Clause 5.2.3.2 of 3GPP TS 38.304).

[0211] When S rxlev >0 and S qual When >0, the selection criteria for the community S Satisfaction is achieved, where:

[0212] Signaling value Q rxlevminoffset and Q qualminoffset It is applied when performing cell selection evaluation for a cell only when normally camped in a visited PLMN (VPLMN) as a result of a periodic search for a higher priority PLMN (see 3GPP TS23.122). During the periodic search for a higher priority PLMN, the UE may use parameter values stored from different cells of that higher priority PLMN to check the S-criterion of the cell.

[0213] The terms of the above equation are defined in Table 4 below: Table 4

[0214] According to aspects of the tenth solution, when the anchor cell includes at least one of the following information, the UE may determine that it should start looking for a non-anchor cell: explicit signaling for camping on a non-anchor cell; a new cell selection threshold; and / or a random persistence check.

[0215] Regarding the explicit signaling for camping on a non-anchor cell, in this case, the UE must attempt to receive SIB1 of the indicated non-anchor cell and check whether the same cell (after SIB1 is received) meets the cell selection criterion S and, optionally, prove to be a suitable cell. Only when it fails, the UE is allowed to remain camped on the anchor cell.

[0216] Regarding the new cell selection threshold, the anchor cell may broadcast a new threshold to conditionally trigger the UE to select a non-anchor cell. Therefore, when the radio quality of the anchor cell (or the detected best cell) is lower than the new threshold, the UE attempts to obtain SIB1 of the non-anchor cell. Alternatively, when the radio quality is between two thresholds, i.e., new threshold 1 < radio quality of the anchor < new threshold 2, the UE attempts to obtain SIB1 of the non-anchor cell. In various embodiments, the radio quality is measured by RSRP / RSRQ.

[0217] Regarding the random persistence check, a decimal value 0.0 < p < 1.0 is broadcast. When the value of a randomly drawn fraction is less than (alternatively, greater than) the broadcast persistence value "p", the UE should request SIB1 of the non-anchor cell (and thus attempt to camp on it).

[0218] According to various aspects of the eleventh solution, a UE can use access control to request SIB1. In its simplest form, no access control is required for the request to SIB1, meaning any UE can request it. In its variants, only UEs with specific access identifiers are allowed to send requests to SIB1. These access identifiers can be specified or configured by the anchor cell, or they can be pre-configured.

[0219] Based on various aspects of the twelfth solution, different network scenarios and UE behaviors for each scenario are described. In the first scenario, the SSB transmission of the non-anchor cell is "ON," and the UE cannot find the anchor cell. In this case, the SSB / PBCH transmission is "ON," and the UE can use the pre-configured PRACH configuration to request SIB1. The UE should perform this operation based on the indication in the Master Information Block (MIB) on the PBCH that SIB1 has not been broadcast.

[0220] The MIB provides the UE with parameters (e.g., CORESET#0 configuration) for monitoring the PDCCH to schedule the PDSCH carrying SIB1. The PBCH may also indicate that no associated SIB1 exists. In this case, the MIB may not point to another frequency, which the UE would otherwise search for the SSB associated with SIB1 from. Instead, the UE performs the SIB1 request according to one or more aspects of this disclosure.

[0221] In the second scenario, SSB transmission on the non-anchor cell is "ON", and the UE finds the anchor cell. In this case, for example, according to one or more aspects of this disclosure, the UE can receive / determine the SIB1 content of the non-anchor cell from the anchor cell.

[0222] As another implementation of the second scenario, the PRACH configuration for on-demand SIB1 can be obtained from the anchor cell. Upon receiving a PRACH-based SIB1 request, the network can initiate SIB1 transmission on a non-anchor cell. If the request is sent to a non-anchor cell, the non-anchor cell itself can provide SIB1. However, if the request is sent via the anchor cell, network communication on the backhaul (Xn, F1, and / or X2 interfaces) ensures that the non-anchor cell is informed of the request and that it can provide SIB1. After a period of transmission, the network can stop SIB1 transmission based on network implementations (such as idle mode load of neighboring / anchor cells (or even RRC connection load acting as a proxy)) and restart it based on SIB1 requests from (multiple) UEs to anchor to a non-anchor cell.

[0223] In the third scenario, the SSB transmission on the non-anchor cell is "OFF", and the UE finds the anchor cell. In this case, if the SSB transmission is "OFF", the UE should request the anchor cell to turn both the SSB and SIB-1 of the non-anchor cell "ON".

[0224] In the fourth scenario, SSB transmission on the non-anchor cell is "OFF," and the UE has not found an anchor cell. In this case, if SSB transmission is "OFF" and no available anchor cell exists, the UE will use a fixed GNSS-based time slot to perform UL transmission using a pre-configured PRACH configuration. For example, starting from GPS Initiation Time (GPST), a PRACH opportunity can be used every 10 seconds.

[0225] The PRACH configuration itself can use default / (pre)configured / specified values ​​for the preamble (e.g., reference signal) and frequency resources. A limited number of power ramps are performed. Here, the network sends both SSB / SIB-1 after receiving the RACH preamble from “N” UEs.

[0226] It should be noted that the various aspects of the solutions described above can be combined. For example, one or more solutions may be implemented together in the UE and / or network. Therefore, the numbering of the solutions described above is for the purpose of organizing similar concepts, and unless otherwise explicitly stated, the aspects described herein are assumed to be jointly implementable.

[0227] Figure 9 An example of a UE 900 according to various aspects of this disclosure is illustrated. The UE 900 may include a processor 902, a memory 904, a controller 906, and a transceiver 908. The processor 902, memory 904, controller 906, or transceiver 908, or various combinations thereof, or various components thereof, may be examples of parts for performing various aspects of this disclosure described herein. These components may be coupled via one or more interfaces (e.g., operational ground, communication ground, functional ground, electronic ground, electrical ground).

[0228] Processor 902, memory 904, controller 906, or transceiver 908, or various combinations or components thereof, may be implemented in hardware (e.g., a circuit system). The hardware may include a processor, digital signal processor (DSP), application-specific integrated circuit (ASIC), or other programmable logic device, or any combination thereof, configured or otherwise supporting components for performing the functions described in this disclosure.

[0229] Processor 902 may include intelligent hardware devices (e.g., a general-purpose processor, DSP, central processing unit (CPU), ASIC, field-programmable gate array (FPGA), or any combination thereof). In some implementations, processor 902 may be configured to operate memory 904. In some other implementations, memory 904 may be integrated into processor 902. Processor 902 may be configured to execute computer-readable instructions stored in memory 904 to cause UE 900 to perform various functions of this disclosure.

[0230] Memory 904 may include volatile or non-volatile memory. Memory 904 may store computer-readable, computer-executable code, including instructions that, when executed by processor 902, cause UE 900 to perform the various functions described herein. The code may be stored in a non-transitory computer-readable medium, such as memory 904 or another type of memory. Computer-readable media include both non-transitory computer storage media and communication media, including any medium that facilitates the transfer of a computer program from one place to another. Non-transitory storage media may be any available medium that can be accessed by a general-purpose or special-purpose computer.

[0231] In some implementations, processor 902 and memory 904 coupled to processor 902 can be configured such that UE 900 performs various functions described herein (e.g., operations, signaling) (e.g., instructions stored in memory 904 are executed by processor 902). In some implementations, processor 902 may include multiple processors, and memory 904 may include multiple memories. One or more of the multiple processors may be coupled to one or more of the multiple memories, which may be configured individually or collectively to perform the various functions of UE 900 disclosed herein (e.g., operations, signaling).

[0232] The processor 902 coupled to the memory 904 may be configured, enabled, or operable to cause the UE 900 to: receive broadcast signaling from a first cell, the broadcast signaling including configuration for requesting a first system information block (i.e., SIB1) of a second cell; send a first random access message (i.e., Msg1) indicating the request for SIB1 of the second cell; monitor the SIB1 of the second cell based at least in part on the reception of a second random access message (Msg2); and perform cell selection based at least in part on the reception of SIB1.

[0233] In some implementations, the processor 902 coupled to the memory 904 may be configured, enabled, or operable to cause the UE 900 to send Msg1 to the first cell. In other implementations, the processor 902 coupled to the memory 904 may be configured, enabled, or operable to cause the UE 900 to send Msg1 to the second cell.

[0234] In some implementations, the processor 902 coupled to the memory 904 may be configured, enabled, or operable to cause the UE 900 to perform cell reselection to a second cell, at least in part based on a positive evaluation of one or more cell reselection criteria.

[0235] In some implementations, in order to receive broadcast signaling, a processor 902 coupled to memory 904 may be configured, capable, or operable such that UE 900: receives a new SIB, which includes configuration for requesting a corresponding SIB1 for one or more neighboring cells. In some implementations, the broadcast signaling also includes at least one condition for the UE to camp on a second cell, wherein the processor 902 coupled to memory 904 may be configured, capable, or operable such that UE 900: A) determines, based on at least one condition, whether to attempt to camp on the second cell; and B) in response to the determination to attempt to camp on the second cell, sends Msg1. In some implementations, the determination to attempt to camp on the second cell is based at least in part on the received radio quality of the best cell available to UE 900 on the frequency associated with the second cell.

[0236] In some implementations, the processor 902 coupled to the memory 904 may be configured, able, or operable to cause the UE 900 to send a MsgA indicating a request for SIB1. In some implementations, the MsgA includes the cell identifier of the second cell, the UE RRC state, and the UE type.

[0237] In some implementations, the processor 902 coupled to the memory 904 may be configured, enabled, or operable such that the UE 900: receives MsgB from a first cell in response to MsgA, wherein MsgB includes at least a portion of SIB1 of the second cell. In other implementations, the UE 900 is configured to receive MsgB from a second cell in response to MsgA, wherein MsgB includes at least a portion of SIB1 of the second cell.

[0238] In some implementations, the processor 902 coupled to the memory 904 may be configured, capable, or operable such that the UE 900 determines to perform a CFRA procedure based at least in part on an assessment of the first cell. In other implementations, the processor 902 coupled to the memory 904 may be configured, capable, or operable such that the UE 900 determines to perform a CBRA procedure based at least in part on an assessment of the first cell.

[0239] In some implementations, the processor 902 coupled to the memory 904 may be configured, enabled, or operable to cause the UE 900 to: determine, at least in part, to perform a two-step RACH procedure based on an assessment of the first cell, wherein the two-step RACH procedure includes the transmission of MsgA and the reception of MsgB.

[0240] In some implementations, the processor 902 coupled to the memory 904 may be configured, capable, or operable such that the UE 900: determines to perform a CFRA procedure based at least in part on an assessment of the first cell. In some implementations, the processor 902 coupled to the memory 904 may be configured, capable, or operable such that the UE 900: determines to perform a CBRA procedure based at least in part on an assessment of the first cell.

[0241] In some implementations, the processor 902 coupled to the memory 904 may be configured, capable, or operable such that the UE 900: determines, at least in part based on an evaluation of the first cell, to perform a four-step RACH procedure, wherein the four-step RACH procedure includes the transmission of Msg1, the reception of Msg2, the transmission of Msg3, and the reception of Msg4. In some embodiments, Msg3 may include the cell identifier of the second cell, the UE RRC state, and the UE type.

[0242] Controller 906 can manage input and output signals for UE 900. Controller 906 can also manage peripheral devices not integrated into UE 900. In some implementations, controller 906 can utilize an operating system (OS) such as iOS®, ANDROID®, WINDOWS®, or other operating systems. In some implementations, controller 906 can be implemented as part of processor 902.

[0243] In some implementations, UE 900 may include at least one transceiver 908. In other implementations, UE 900 may have more than one transceiver 908. Transceiver 908 may represent a wireless transceiver. Transceiver 908 may include one or more receiver chains 910, one or more transmitter chains 912, or a combination thereof.

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

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

[0246] Figure 10 An example of a processor 1000 according to various aspects of this disclosure is illustrated. The processor 1000 may be an example of a processor configured to perform various operations according to the examples described herein. The processor 1000 may include a controller 1002 configured to perform various operations according to the examples described herein. The processor 1000 may optionally include at least one memory 1004, which may be, for example, an L1 / L2 / L3 cache. Additionally or alternatively, the processor 1000 may optionally include one or more arithmetic logic units (ALUs) 1006. One or more of these components may be electronically communicated or otherwise coupled (e.g., operative ground, communicative ground, functional ground, electronic ground, electrical ground) via one or more interfaces (e.g., buses).

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

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

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

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

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

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

[0253] In some implementations, based on the examples disclosed herein, processor 1000 may support various functions of the UE (e.g., operation, signaling). For example, controller 1002 coupled to memory 1004 may be configured, enabled, or operable to cause processor 1000 to: receive broadcast signaling from a first cell, the broadcast signaling including configuration for requesting a first system information block of a second cell; send a first random access message indicating a request for the first system information block of the second cell; monitor the first system information block of the second cell at least in part based on the transmission of the first random access message; and perform cell selection at least in part based on the reception of the first system information block. Additionally, controller 1002 coupled to memory 1004 may be configured, enabled, or operable to cause processor 1000 to perform one or more functions of the UE as described herein (e.g., operation, signaling).

[0254] Alternatively or additionally, in some other implementations, processor 1000 may support various functions (e.g., operation, signaling) of the NE (e.g., base station) according to the examples disclosed herein. For example, controller 1002 coupled to memory 1004 may be configured, enabled, or operable to cause processor 1000 to: transmit broadcast signaling in a first cell, the broadcast signaling including configuration for requesting a first system information block for a second cell; receive from a UE a first random access message (i.e., Msg1) indicating a request for the first system information block for the second cell; transmit a second random access message (i.e., Msg2) in response to Msg1; and transmit the first system information block for the second cell. Additionally, controller 1002 coupled to memory 1004 may be configured, enabled, or operable to cause processor 1000 to perform one or more functions (e.g., operation, signaling) of the NE as described herein.

[0255] Figure 11 An example of an NE 1100 according to various aspects of this disclosure is illustrated. The NE 1100 may include a processor 1102, a memory 1104, a controller 1106, and a transceiver 1108. The processor 1102, memory 1104, controller 1106, or transceiver 1108, or various combinations thereof, or various components thereof, may be examples of parts for performing various aspects of this disclosure described herein. These components may be coupled via one or more interfaces (e.g., operational ground, communication ground, functional ground, electronic ground, electrical ground).

[0256] Processor 1102, memory 1104, controller 1106, or transceiver 1108, or various combinations or components thereof, may be implemented in hardware (e.g., a circuit system). The hardware may include a processor, digital signal processor (DSP), application-specific integrated circuit (ASIC), or other programmable logic device, or any combination thereof, configured or otherwise supporting components for performing the functions described in this disclosure.

[0257] Processor 1102 may include intelligent hardware devices (e.g., a general-purpose processor, DSP, CPU, ASIC, FPGA, or any combination thereof). In some implementations, processor 1102 may be configured to operate memory 1104. In some other implementations, memory 1104 may be integrated into processor 1102. Processor 1102 may be configured to execute computer-readable instructions stored in memory 1104 to cause NE 1100 to perform various functions of this disclosure.

[0258] Memory 1104 may include volatile or non-volatile memory. Memory 1104 may store computer-readable, computer-executable code, including instructions that, when executed by processor 1102, cause NE 1100 to perform the various functions described herein. The code may be stored in a non-transitory computer-readable medium, such as memory 1104 or another type of memory. Computer-readable media include both non-transitory computer storage media and communication media, including any medium that facilitates the transfer of a computer program from one place to another. Non-transitory storage media may be any available medium that can be accessed by a general-purpose or special-purpose computer.

[0259] In some implementations, processor 1102 and memory 1104 coupled to processor 1102 may be configured such that NE 1100 performs various functions described herein (e.g., operations, signaling) (e.g., instructions stored in memory 1104 are executed by processor 1102). In some implementations, processor 1102 may include multiple processors, and memory 1104 may include multiple memories. One or more of the multiple processors may be coupled to one or more of the multiple memories, which may be configured individually or collectively to perform the various functions of NE 1100 disclosed herein (e.g., operations, signaling).

[0260] The processor 1102 coupled to the memory 1104 may be configured, enabled, or operable to cause the NE 1100 to: transmit broadcast signaling in the first cell, the broadcast signaling including a configuration for requesting a first system information block (i.e., SIB1) for the second cell; receive a first random access message (i.e., Msg1) from the UE requesting SIB1 for the second cell; transmit a second random access message (Msg2) in response to Msg1; and transmit SIB1 for the second cell.

[0261] In some implementations, in order to send broadcast signaling, the processor 1102 coupled to the memory 1104 can be configured, enabled, or operable such that NE 1100: sends a second random access message (i.e., Msg2) in response to Msg1; and sends SIB1 in response to sending RACH Msg2.

[0262] In some implementations, the processor 1102 coupled to the memory 1104 may be configured, enabled, or operable such that the NE 1100 receives a third random access message (i.e., Msg3) in response to Msg2, Msg3 including the cell identifier of the second cell, the UE RRC state, and the UE type.

[0263] In some implementations, for transmitting broadcast signaling, the processor 1102 coupled to the memory 1104 may be configured, capable, or operable such that NE 1100 receives Msg1 via a first cell. In other implementations, for transmitting broadcast signaling, the processor 1102 coupled to the memory 1104 may be configured, capable, or operable such that NE 1100 receives Msg1 via a second cell.

[0264] In some implementations, in order to send broadcast signaling, the processor 1102 coupled to the memory 1104 can be configured, enabled, or operable such that NE 1100: sends a new SIB including a configuration for requesting SIB1. In some implementations, the broadcast signaling also includes at least one condition regarding the UE being camped on a second cell.

[0265] In some implementations, in order to send broadcast signaling, the processor 1102 coupled to the memory 1104 can be configured, enabled, or operable such that NE 1100: in response to sending Msg2, sends SIB1 of the second cell.

[0266] In some implementations, in order to send broadcast signaling, the processor 1102 coupled to the memory 1104 can be configured, enabled, or operable to cause NE 1100 to initiate SS / PBCH transmission in the second cell in response to Msg1.

[0267] In some implementations, in order to receive a request for SIB1, the processor 1102 coupled to memory 1104 may be configured, capable, or operable such that NE 1100: receives MsgA via a first cell. In some implementations, RACHMsgA includes the cell identifier of a second cell, the UE RRC state, and the UE type. In other implementations, in order to receive a request for SIB1, the processor 1102 coupled to memory 1104 may be configured, capable, or operable such that NE 1100: receives Msg1.

[0268] In some implementations, the processor 1102 coupled to memory 1104 may be configured, capable, or operable such that NE 1100: transmits MsgB from a first cell in response to MsgA. In other implementations, the processor 1102 coupled to memory 1104 may be configured, capable, or operable such that NE 1100: transmits MsgB from a second cell in response to MsgA. In various implementations, MsgB includes at least a portion of SIB1 of the second cell.

[0269] Controller 1106 can manage input and output signals for NE 1100. Controller 1106 can also manage peripheral devices not integrated into NE 1100. In some implementations, controller 1106 can utilize an operating system such as iOS®, ANDROID®, WINDOWS®, or other operating systems. In some implementations, controller 1106 can be implemented as part of processor 1102.

[0270] In some implementations, NE 1100 may include at least one transceiver 1108. In other implementations, NE 1100 may have more than one transceiver 1108. Transceiver 1108 may represent a wireless transceiver. Transceiver 1108 may include one or more receiver chains 1110, one or more transmitter chains 1112, or a combination thereof.

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

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

[0273] Figure 12 An embodiment of method 1200 according to various aspects of this disclosure is depicted. In various embodiments, the operation of method 1200 can be implemented by the UE described herein. In some implementations, the UE can execute a set of instructions to control the functional elements of the UE to perform the described functions.

[0274] At step 1202, method 1200 may include: receiving broadcast signaling from a first cell, the broadcast signaling including configuration for requesting SIB1 of a second cell. The operation of step 1202 can be performed according to the examples described herein. In some implementations, aspects of the operation of step 1202 may be derived from references... Figure 9 The UE described is used for execution.

[0275] At step 1204, method 1200 may include sending Msg1 indicating a request for SIB1 of the second cell. The operation of step 1204 can be performed according to the examples described herein. In some implementations, aspects of the operation of step 1204 may be derived from references... Figure 9 The UE described is used for execution.

[0276] At step 1206, method 1200 may include: monitoring the SIB1 of the second cell, at least in part based on the reception of the second random access message (Msg2). The operation of step 1206 can be performed according to the examples described herein. In some implementations, aspects of the operation of step 1206 may be derived from references... Figure 9 The UE described is used for execution.

[0277] At step 1208, method 1200 may include: evaluating cell reselection based at least in part on SIB1 reception. The operation of step 1208 can be performed according to the examples described herein. In some implementations, aspects of the operation of step 1208 may be derived from references... Figure 9 The UE described is used for execution.

[0278] It should be noted that the method 1200 described herein describes one possible implementation, and the operations and steps can be rearranged or otherwise modified, and other implementations are also possible.

[0279] It should be noted that the method 1200 described herein describes one possible implementation, and the operations and steps can be rearranged or otherwise modified, and other implementations are also possible.

[0280] Figure 13 An embodiment of method 1300 according to various aspects of this disclosure is depicted. Operation of method 1300 may be implemented by the RAN described herein. In some implementations, the RAN may execute a set of instructions to control the functional elements of the RAN to perform the described functions.

[0281] At step 1302, method 1300 may include: sending broadcast signaling in the first cell, the broadcast signaling including configuration for requesting SIB1 of the second cell. The operation of step 1302 can be performed according to the examples described herein. In some implementations, aspects of the operation of step 1302 may be derived from references... Figure 11 The described NE is used for execution.

[0282] At step 1304, method 1300 may include receiving from the UE a Msg1 indicating a request for SIB1 of the second cell. The operation of step 1304 can be performed according to the examples described herein. In some implementations, aspects of the operation of step 1304 may be derived from references... Figure 11 The described NE is used for execution.

[0283] At step 1306, method 1300 may include: sending Msg2 in response to Msg1; and. The operation of step 1306 can be performed according to the examples described herein. In some implementations, aspects of the operation of step 1306 may be derived from references. Figure 11 The described NE is used for execution.

[0284] At step 1308, method 1300 may include: transmitting SIB1 of the second cell. The operation of step 1308 can be performed according to the examples described herein. In some implementations, aspects of the operation of step 1308 may be derived from references... Figure 11 The described NE is used for execution.

[0285] It should be noted that the method 1300 described herein describes one possible implementation, and the operations and steps can be rearranged or otherwise modified, and other implementations are also possible.

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

Claims

1. A user equipment (UE) for wireless communication, comprising: At least one memory; as well as At least one processor, coupled to the at least one memory, and configured such that the UE: Receive broadcast signaling from the first cell, the broadcast signaling including configuration for requesting the first system information block SIB1 of the second cell; Send a first random access message Msg1 indicating a request for SIB1 of the second cell; The SIB1 of the second cell is monitored, at least in part based on the reception of the second random access message Msg2; as well as Cell reselection is evaluated based at least in part on the reception of the SIB1.

2. The UE according to claim 1, wherein the at least one processor is configured to cause the UE to send the Msg1 to the first cell.

3. The UE according to claim 1, wherein the at least one processor is configured to cause the UE to send the Msg1 to the second cell.

4. The UE of claim 1, wherein the at least one processor is configured to cause the UE to perform cell reselection to the second cell based at least in part on a positive assessment of one or more cell reselection criteria.

5. The UE of claim 1, wherein, in order to receive the broadcast signaling, the at least one processor is configured to cause the UE to receive a new System Information Block (SIB), the new SIB including the configuration for requesting a corresponding SIB1 for one or more neighboring cells.

6. The UE of claim 1, wherein the broadcast signaling further includes at least one condition for the UE to be camped on a second cell, and wherein the at least one processor is configured to cause the UE to: Based on at least one of the conditions, determine whether to attempt to camp on the second cell; and In response to the confirmation of attempting to camp on the second cell, Msg1 is sent.

7. The UE of claim 6, wherein the determination to attempt to camp on the second cell is based at least in part on the received radio quality of the best cell available to the UE on the frequency associated with the second cell.

8. The UE of claim 1, wherein the at least one processor is configured such that the UE determines to perform a contention-based RACH procedure based at least in part on the evaluation of the first cell.

9. A processor for wireless communication, comprising: At least one controller, coupled to at least one memory, and configured such that the processor: Receive broadcast signaling from the first cell, the broadcast signaling including configuration for requesting the first system information block SIB1 of the second cell; Send a first random access message Msg1 indicating a request for SIB1 of the second cell; The SIB1 of the second cell is monitored, at least in part based on the reception of the second random access message Msg2; as well as Cell reselection is evaluated based at least in part on the reception of the SIB1.

10. The processor of claim 9, wherein the at least one controller is configured to cause the processor to send the Msg1 to the first cell.

11. The processor of claim 9, wherein the at least one controller is configured to cause the processor to send the Msg1 to the second cell.

12. The processor of claim 9, wherein, in order to receive the broadcast signaling, the at least one controller is configured to cause the processor to receive a new System Information Block (SIB), the new SIB including the configuration for requesting a corresponding SIB1 for one or more neighboring cells.

13. A base station for wireless communication, comprising: At least one memory; as well as At least one processor, coupled to the at least one memory, and configured such that the base station: A broadcast signaling is sent in the first cell, the broadcast signaling including a configuration for requesting the first system information block SIB1 of the second cell; Receive a first random access message Msg1 from the user equipment (UE) indicating a request for SIB1 of the second cell; In response to Msg1, a second random access message Msg2 is sent; as well as The SIB1 of the second cell is transmitted.

14. The base station of claim 13, wherein the at least one processor is configured to cause the base station to receive Msg1 via the first cell.

15. The base station of claim 13, wherein the at least one processor is configured to cause the base station to receive Msg1 via the second cell.

16. The base station of claim 13, wherein, in order to transmit the broadcast signaling, the at least one processor is configured to cause the base station to transmit a new System Information Block (SIB), the new SIB including the configuration for requesting the SIB1.

17. The base station of claim 13, wherein the at least one processor is configured to cause the base station to transmit the SIB1 of the second cell in response to transmitting the Msg2.

18. The base station of claim 13, wherein the broadcast signaling further includes at least one condition for the UE to be camped on a second cell.

19. The base station of claim 13, wherein the at least one processor is configured to cause the base station to initiate a synchronization signal and physical broadcast channel block (SS / PBCH) transmission in the second cell in response to Msg1.

20. A method for wireless communication performed by a base station, comprising: A broadcast signaling is sent in the first cell, the broadcast signaling including a configuration for requesting the first system information block SIB1 of the second cell; Receive a first random access message Msg1 from the user equipment (UE) indicating a request for SIB1 of the second cell; In response to Msg1, a second random access message Msg2 is sent; as well as The SIB1 of the second cell is transmitted.

Images