Selection of initial acquisition parameters for reduced capability devices

Abstract

Aspects of the disclosure relate to various apparatuses, methods, and computer readable media for providing or utilizing initial acquisition parameters for reduced-capability wireless user equipment (UEs). In one example, a wireless base station can transmit a plurality of synchronization signal blocks (SSBs), where at least one of the SSBs is designated for a reduced-capability UE group. The base station can also transmit a plurality of control resource sets, at least one of the control resource sets designated for the reduced-capability UE group. In another example, the base station can transmit a shared SSB / control resource set configured to be compatible with both legacy UEs and reduced-capability UEs. Other aspects, embodiments, and features are also claimed and described.

Description

[0001] Cross-references to related applications

[0002] This application is a PCT application claiming priority to non-provisional patent application No. 17 / 230,923, filed with the United States Patent and Trademark Office on April 14, 2021, which claims priority to provisional patent application No. 63 / 010,640, filed with the United States Patent and Trademark Office on April 15, 2020. The entire contents of the above applications are incorporated herein by reference as fully set forth herein and for all applicable purposes. Technical Field

[0003] In general, the technologies discussed below relate to wireless communication systems, and more specifically, to the initial acquisition of wireless connectivity. Some aspects may include providing and implementing technologies for selecting, configuring, or communicating with various types of communication devices (e.g., initial acquisition for devices with reduced capabilities). The technologies implement and provide new communication devices and methods compatible with an expanded set of use case categories, including UEs that do not require peak capabilities but offer improved efficiency and system operation. Background Technology

[0004] In a wireless communication system configured according to the 3GPP specifications for 5G New Radio (NR), a mobile device can perform an initial acquisition of a connection with a base station. One approach includes searching for a synchronization signal (SS) and a physical broadcast channel (PBCH) carrying basic system information about the network. The mobile device receiving the SS and system information can then seek to receive a set of control resources, which provides information that it can use to receive further system information about the network.

[0005] In some scenarios, future NR specifications may address the use cases of mobile devices with reduced capabilities. For example, low-end smartphones, wireless sensors (e.g., pressure, humidity, temperature, motion, acceleration sensors), actuators, data collection and processing devices, video surveillance equipment, and wearable devices may have small form factors and / or potentially several years of battery life. In a specific example, wearable devices like smartwatches can operate as companion devices to smartphones, reducing the need for independent operation of the watch. In this use case, peak device capabilities may not be required, and sufficient 5G connectivity can be provided through low-end services. Utilizing these devices with reduced capabilities can achieve increased efficiency and / or cost-effectiveness at the potential cost of reduced capabilities, such as relatively narrow bandwidth, a reduced number of antennas, relaxed processing time requirements, extended idle time, or other reduced or limited functions or capabilities.

[0006] As the demand for mobile broadband access continues to increase, research and development continue to improve wireless communication technologies, not only to meet the growing demand for mobile broadband access, but also to improve and enhance the user experience of mobile communications. Summary of the Invention

[0007] The following is a brief overview of one or more aspects of this disclosure to provide a basic understanding of those aspects. This overview is not a general summary of all intended features of this disclosure, nor is it intended to identify key or essential elements of all aspects of this disclosure or to describe the scope of any or all aspects of this disclosure. Its sole purpose is to provide some concepts of one or more embodiments in a simplified form as an introduction to the more detailed description provided below.

[0008] In various aspects, this disclosure relates to various apparatuses, methods, and computer-readable media for providing or utilizing initial acquisition parameters for a degraded radio user equipment (UE). In one example, a radio base station may transmit multiple synchronization signal blocks (SSBs), wherein at least one of these SSBs is designated for a category or group of degraded UEs. The base station may also transmit one or more control resource sets (CORESETs), wherein at least one of these CORESETs is designated for a category or group of degraded UEs. In another example, the base station may transmit shared SSBs / CORESETs configured to be compatible with both legacy UEs and degraded UEs. Further examples provide different behaviors of degraded UEs and legacy UEs in response to signaling from the network.

[0009] For example, in one example, a method for wireless communication is disclosed. The method includes: transmitting a first synchronization signal block (SSB), the first SSB including information for identifying a first control resource set (CORESET) for a first group of one or more user equipments (UEs); and transmitting the first control resource set on a first bandwidth for the first group of UEs. The method further includes: transmitting a second SSB, the second SSB including information for identifying a second CORESET for a second group of one or more UEs; and transmitting the second CORESET on a second bandwidth for the second group of one or more UEs, the second bandwidth being wider than the first bandwidth.

[0010] In another example, a method for wireless communication is disclosed. The method includes: transmitting an SSB, the SSB including information for identifying a first core set for a first group of one or more UEs and information for identifying a second core set for a second group of one or more UEs. The method further includes: transmitting the first core set on a first bandwidth for the first group of one or more UEs; and transmitting the second core set on a second bandwidth for the second group of one or more UEs, the second bandwidth being wider than the first bandwidth.

[0011] In yet another example, a method for wireless communication is disclosed. The method includes: transmitting an SSB for identifying a first System Information Block (SIB) of one or more UEs in a first group within a shared CORESET, and information for identifying a second SIB of one or more UEs in a second group within the shared CORESET. The method further includes: transmitting the CORESET, the CORESET including the first SIB having a first bandwidth and including the second SIB having a second bandwidth wider than the first bandwidth.

[0012] In another example, a method for wireless communication is disclosed. The method includes: transmitting an SSB configured to be shared by at least a first category of UEs and a second category of UEs. The method further includes: configuring a CORESET to have a bandwidth corresponding to an assumed bandwidth capability of one or more UEs in a first group. Here, the assumed bandwidth capability of the first category of UEs is narrower than the assumed bandwidth capability of the second category of UEs. The method further includes: transmitting the CORESET on the bandwidth for sharing by at least the first category of UEs and the second category of UEs.

[0013] In yet another example, a method for wireless communication is disclosed. The method includes: transmitting an SSB configured to be shared by at least two classes of UEs. Here, the SSB includes an index value for indicating a configuration of a CORESET. The method further includes: transmitting a first CORESET configured according to a first translation of one or more SSB fields associated with the index value; and transmitting a second CORESET configured according to a second translation of one or more SSB fields associated with the index value, the second translation being different from the first translation.

[0014] In another example, an apparatus for wireless communication is disclosed. The apparatus includes a processor, a transceiver communicatively coupled to the processor, and a memory communicatively coupled to the processor. The processor and the memory are configured such that the apparatus scans a set of frequencies for acquisition by a wireless network. The apparatus receives a first synchronization signal block (SSB) designated for a first group of one or more user equipments (UEs), the first SSB including information for identifying a first control resource set. The apparatus receives the first control resource set and obtains corresponding system information for the wireless network, and establishes a connection with the wireless network based on the system information.

[0015] In another example, an apparatus for wireless communication is disclosed. The apparatus includes a processor, a transceiver communicatively coupled to the processor, and a memory communicatively coupled to the processor. The processor and the memory are configured such that the apparatus scans a set of frequencies for acquisition by a wireless network. The apparatus receives a synchronization signal block (SSB), the SSB including information for identifying a first control resource set designated for a first group of one or more user equipments (UEs), and further including information for identifying a second control resource set designated for a second group of one or more UEs. The apparatus receives the first control resource set based on the premise that it is a member of the first group of one or more UEs, and obtains corresponding first system information for the wireless network. The apparatus establishes a connection with the wireless network based on the system information.

[0016] In another example, an apparatus for wireless communication is disclosed. The apparatus includes a processor, a transceiver communicatively coupled to the processor, and a memory communicatively coupled to the processor. The processor and the memory are configured such that the apparatus scans a set of frequencies for wireless network acquisition. The apparatus receives a synchronization signal block (SSB), the SSB including information for identifying a control resource set. The apparatus receives the control resource set, the control resource set including first system information designated for a first group of UEs, and further including second system information designated for a second group of UEs. Based on the control resource set, the apparatus obtains the corresponding first system information for the wireless network based on the fact that the apparatus is a member of one or more UEs in the first group. The apparatus establishes a connection with the wireless network based on the first system information.

[0017] In another example, an apparatus for wireless communication is disclosed. The apparatus includes a processor, a transceiver communicatively coupled to the processor, and a memory communicatively coupled to the processor. The processor and the memory are configured such that the apparatus scans a set of frequencies for wireless network acquisition. The apparatus receives a synchronization signal block (SSB), the SSB including information elements for identifying a control resource set. The apparatus also receives a first control resource set based on a first translation of the information elements for identifying the control resource set, the first translation being designated for a first group of one or more UEs. The apparatus obtains corresponding first system information for the wireless network based on the first control resource set, and establishes a connection with the wireless network based on the first system information.

[0018] A more comprehensive understanding of these and other aspects of the techniques discussed herein will be gained after reviewing the following detailed description. Other aspects, features, and embodiments will become apparent to those skilled in the art after reviewing the following description of specific, exemplary embodiments in conjunction with the accompanying drawings. While the following description may discuss various advantages and features with respect to certain embodiments and drawings, all embodiments may include one or more of the advantageous features discussed herein. In other words, while this description may discuss one or more embodiments having certain advantageous features, one or more of these features may also be used according to the various embodiments discussed herein. Similarly, while this description may discuss exemplary embodiments as device, system, or method embodiments, it should be understood that these exemplary embodiments may be implemented in various devices, systems, and methods. Attached Figure Description

[0019] Figure 1 This is a schematic diagram of a wireless communication system based on some aspects of this disclosure.

[0020] Figure 2 This is a schematic diagram illustrating an example of a radio access network based on some aspects of this disclosure.

[0021] Figure 3 This is a conceptual illustration of the organization of radio resources in an air interface utilizing orthogonal frequency division multiplexing (OFDM) based on some aspects of this disclosure.

[0022] Figure 4 This is a conceptual illustration of an OFDM air interface utilizing a scalable digital scheme (numerology) based on some aspects of this disclosure.

[0023] Figure 5 This is a block diagram illustrating an example of a hardware implementation of a scheduling entity (e.g., a base station) according to some aspects of this disclosure.

[0024] Figure 6 This is a block diagram illustrating an example of a hardware implementation of a scheduled entity (e.g., a UE) according to some aspects of this disclosure.

[0025] Figure 7 This is a flowchart of an exemplary UE process for initial acquisition of network connectivity, based on some aspects of this disclosure.

[0026] Figure 8 This is a conceptual illustration of base station transmissions for separate SSBs and separate sets of control resources for different UE categories or groups, based on a further aspect of this disclosure.

[0027] Figure 9 This is a conceptual illustration of base station transmissions for separate SSBs and separate sets of control resources for different UE categories or groups, based on a further aspect of this disclosure.

[0028] Figure 10 This is a flowchart illustrating an exemplary process for the initial acquisition of network connectivity between a scheduling entity and two UE categories or groups, according to some aspects of this disclosure.

[0029] Figure 11 This is a conceptual diagram illustrating the transmission of shared SSBs and separately controlled resource sets by scheduling entities based on some aspects of this disclosure.

[0030] Figure 12 This is a flowchart illustrating an exemplary process for the initial acquisition of network connectivity between a scheduling entity and two UE categories or groups, according to some aspects of this disclosure.

[0031] Figure 13 This is a conceptual illustration of the transmission of a shared SSB and a shared control resource set for scheduling entities with separate system information blocks for different UE categories or groups, based on some aspects of this disclosure.

[0032] Figure 14 This is a flowchart illustrating an exemplary process for the initial acquisition of network connectivity between a scheduling entity and two UE categories or groups, according to some aspects of this disclosure.

[0033] Figure 15 This is a conceptual illustration of the scheduling entity transmission for a shared SSB and a shared set of control resources for multiple UE categories or groups, based on some aspects of this disclosure.

[0034] Figure 16 This is a flowchart illustrating an exemplary process for the initial acquisition of network connectivity between a scheduling entity and two UE categories or groups, according to some aspects of this disclosure.

[0035] Figure 17 This is a conceptual illustration of base station transmissions for different UE categories or groups with separate SSBs and separate control resource sets, based on the application of different control element interpretation or translation rules according to further aspects of this disclosure.

[0036] Figure 18 This is a flowchart illustrating an exemplary process for the initial acquisition of network connectivity between a scheduling entity and two UE categories or groups, according to some aspects of this disclosure. Detailed Implementation

[0037] The detailed description set forth below with reference to the accompanying drawings is intended as a description of various configurations, and not as representing only the configurations in which the concepts described herein can be implemented. To provide a thorough understanding of the various concepts, the detailed description includes specific details. However, those skilled in the art will readily recognize that these concepts can be implemented without these specific details. In some cases, well-known structures and components are provided in the form of block diagrams to avoid obscuring such concepts.

[0038] While this description illustrates aspects and embodiments by way of example, those skilled in the art will understand that additional implementations and use cases may arise in many different arrangements and scenarios. The innovations described herein can be implemented across many different platform types, devices, systems, shapes, sizes, and package arrangements. For example, embodiments and / or uses may arise via integrated chip embodiments and other devices based on non-modular components (e.g., end-user devices, vehicles, communication devices, computing devices, industrial equipment, retail / purchasing devices, medical devices, AI-enabled devices, etc.). While some examples may or may not be specific to a particular use case or application, a wide variety of applicability to the described embodiments is possible. Implementations can range from chip-level or modular components to non-modular, non-chip-level implementations, and further to aggregated, distributed, or OEM devices or systems incorporating one or more aspects of the described innovations. In some practical settings, devices incorporating the described aspects and features may also include additional components and features for the implementation and execution of the claimed and described embodiments. For example, the transmission and reception of wireless signals necessarily involve multiple components for analog and digital purposes (e.g., hardware components including antennas, RF chains, power amplifiers, modulators, buffers, processors, interleavers, adders / converters, etc.). The innovations described herein are intended to be implemented in a variety of devices, chip-level components, systems, distributed arrangements, end-user equipment, etc., with different sizes, shapes, and constructions.

[0039] The following disclosure presents various concepts that can be implemented in various telecommunications systems, network architectures, and communication standards. Refer to [link / reference here]. Figure 1This schematic illustration, as an illustrative example and not a limiting example, shows various aspects of the present disclosure with reference to a wireless communication system 100. The wireless communication system includes several interaction domains: a core network 102, a radio access network (RAN) 104, and a user equipment (UE) 106. With the aid of the wireless communication system 100, the UE 106 is able to communicate data with an external data network 110 (e.g., but not limited to, the Internet).

[0040] RAN 104 can implement any suitable one or more wireless communication technologies to provide radio access to UE 106. As an example, RAN 104 can operate according to the 3GPP New Radio (NR) specification (commonly referred to as 5G). As another example, RAN 104 can operate under a hybrid of 5G NR and the Evolved Universal Terrestrial Radio Access Network (eUTRAN) standard (commonly referred to as LTE). 3GPP refers to this hybrid RAN as Next Generation RAN or NG-RAN. Of course, many other examples can be utilized within the scope of this disclosure.

[0041] As shown in the figure, RAN 104 includes multiple base stations 108. Broadly speaking, a base station is a network element in a radio access network responsible for radio transmission and reception to or from a UE in one or more cells. In different technologies, standards, or contexts, those skilled in the art may refer to a base station as a base transceiver unit (BTS), radio base station, radio transceiver, transceiver function, basic service set (BSS), extended service set (ESS), access point (AP), node B (NB), evolved node B (eNode B, eNB), next-generation node B (gNode B, gNB), or some other suitable term. As discussed further below, a base station may fall within the scope of the terminology used herein for scheduling entities.

[0042] Radio access network 104 supports wireless communication for multiple mobile devices. Those skilled in the art may refer to a mobile device as a User Equipment (UE) in the 3GPP standard, but it may also refer to a mobile station (MS), user station, mobile unit, user unit, radio unit, remote unit, mobile device, radio device, wireless communication device, remote device, mobile user station, access terminal (AT), mobile terminal, radio terminal, remote terminal, handphone, terminal, user agent, mobile client, client, or some other suitable term. A UE can be a device that provides access to network services. A UE can take many forms and may include a range of devices. As discussed further below, a UE can be within the scope of the terminologically assigned entity.

[0043] In this document, a “mobile” device (also known as a UE) does not necessarily need to be mobile; it can be stationary. The term mobile device or mobile equipment broadly refers to a wide variety of devices and technologies. A UE may include multiple hardware structural components whose size, shape, and arrangement facilitate communication; such components may include antennas, antenna arrays, RF chains, amplifiers, one or more processors, etc., electrically coupled to each other. Furthermore, RAN 104 can support connections to multiple different categories of UEs with different capabilities and / or supporting different operations. For example, some non-limiting examples of mobile devices include mobile stations, cellular phones, smartphones, Session Initiation Protocol (SIP) phones, laptops, personal computers (PCs), notebooks, netbooks, smartbooks, tablet devices, personal digital assistants (PDAs), and a wide variety of embedded systems, for example, corresponding to the “Internet of Things” (IoT). Additionally, mobile devices can be automobiles or other vehicles, remote sensors or actuators, robots or robotic devices, satellite radios, Global Positioning System (GPS) devices, object tracking devices, drones, multi-rotor helicopters, quadcopter helicopters, remote control devices, consumer devices and / or wearable devices such as glasses, wearable cameras, virtual reality devices, smartwatches, health or fitness trackers, digital audio players (e.g., MP3 players), cameras, game consoles, etc. In some examples, such mobile devices can operate as companion devices to another device (e.g., paired smartphones) that can control or perform at least some of its wireless operations. Furthermore, mobile devices can be digital home or smart home devices, such as home audio, video and / or multimedia equipment, home appliances, vending machines, smart lighting, home security systems, smart meters, etc. Additionally, mobile devices can be smart energy devices, security devices, solar panels or solar arrays, municipal infrastructure equipment controlling electricity (e.g., smart grids), lighting, water, etc.; industrial automation and enterprise equipment; logistics controllers; agricultural equipment; military defense equipment, vehicles, aircraft, ships, weapons, etc. Additionally, mobile devices can provide connected medical or telemedicine support (e.g., telehealth). Telemedicine devices may include telemedicine monitoring and telemedicine management devices, whose communications may be given priority processing or access relative to other types of information, for example, priority access for transmissions of critical service data, and / or relevant QoS aspects for transmissions of critical service data.

[0044] It has been observed that Releases 15 and 16 of the 3GPP specifications for 5G NR appear to primarily focus on throughput, communication reliability and latency for mobile broadband services, and other vertical sectors (e.g., vehicle-to-vehicle (V2V), vehicle-to-everything (V2X), and industrial Internet of Things (IIOT)). However, there is a growing demand in the art for wireless networks to address use cases that can be handled by degraded UEs (sometimes referred to as RedCap UEs in 3GPP literature). For these use cases, UEs with peak, high-capacity, or even typical capabilities may not be required. Instead, it is desirable to deploy degraded UEs (e.g., those with one or more lower or reduced capabilities relative to higher-capacity devices) for these use cases and configure them to operate, for example, to improve efficiency and cost-effectiveness. Some examples of these degraded devices include wearable devices, industrial wireless sensor networks (IWSNs), and surveillance cameras. Within the scope of this disclosure, a reduced-capability UE or a reduced-capability device generally refers to a UE with one or more reduced functional parameters, including but not limited to reduced bandwidth support compared to a conventional or regular UE (such as a smartphone); a reduced number of UE antennas; use of half-duplex communication; relaxed UE processing time; and / or relaxed UE processing capabilities. A reduced-capability UE may additionally or alternatively employ one or more power-saving and battery-life-enhancing features, such as reduced control channel monitoring, extended discontinuous reception (DRX) time, etc.

[0045] Wireless communication between RAN 104 and UE 106 can be described as utilizing an air interface. Transmissions via the air interface from a base station (e.g., base station 108) to one or more UEs (e.g., UE 106) can be referred to as downlink (DL) transmissions. According to certain aspects of this disclosure, the term downlink can refer to point-to-multipoint transmissions originating from a scheduling entity (further described below; e.g., base station 108). Another way to describe this scheme is to use the term broadcast channel multiplexing. Transmissions from a UE (e.g., UE 106) to a base station (e.g., base station 108) can be referred to as uplink (UL) transmissions. According to other aspects of this disclosure, the term uplink can refer to point-to-point transmissions originating from a scheduled entity (further described below; e.g., UE 106).

[0046] In some examples, access to the air interface can be scheduled, where a scheduling entity (e.g., base station 108) allocates resources for communication between some or all devices and equipment within its service area or cell. As further discussed below in this disclosure, the scheduling entity may be responsible for scheduling, assigning, reconfiguring, and releasing resources for one or more scheduled entities. That is, for scheduled communication, a UE 106 of a scheduled entity may utilize resources allocated by the scheduling entity or base station 108.

[0047] Base station 108 is not the only entity that can be used as a scheduling entity. That is, in some examples, a UE can be used as a scheduling entity to schedule resources for one or more scheduled entities (e.g., one or more other UEs).

[0048] like Figure 1 As shown, scheduling entity 108 can broadcast downlink service 112 to one or more scheduled entities 106. Broadly speaking, scheduling entity 108 is a node or device responsible for scheduling services in a wireless communication network, including downlink service 112, and in some examples, uplink service 116 from one or more scheduled entities 106 to scheduling entity 108. On the other hand, scheduled entity 106 is a node or device that receives downlink control information 114, including but not limited to scheduling information (e.g., permission), synchronization or timing information, or other control information from another entity in the wireless communication network (e.g., scheduling entity 108).

[0049] Generally, base station 108 may include a backhaul interface for communicating with the backhaul section 120 of a wireless communication system. Backhaul 120 provides a link between base station 108 and core network 102. Furthermore, in some examples, the backhaul network can provide interconnection between the individual base stations 108. Various types of backhaul interfaces can be employed, such as a direct physical connection using any suitable transport network, a virtual network, etc.

[0050] Core network 102 may be part of wireless communication system 100 and may be independent of the radio access technology used in RAN 104. In some examples, core network 102 may be configured according to 5G standards (e.g., 5GC). In other examples, core network 102 may be configured according to 4G Evolved Packet Core (EPC) or any other suitable standard or configuration.

[0051] By using examples rather than limitations Figure 2 A schematic diagram of RAN 200 is provided. In some examples, RAN 200 can be used in conjunction with the configuration described above and... Figure 1 The same as RAN 104 shown. The geographical area covered by RAN 200 can be divided into cellular areas (cells), and user equipment (UE) can be uniquely identified based on an identifier broadcast from an access point or base station. Figure 2Macro cells 202, 204, and 206, and small cell 208 are shown. Each cell can include one or more sectors (not shown). A sector is a sub-area of ​​a cell. All sectors within a cell are served by the same base station. Radio links within a sector can be identified by a single logical identifier belonging to that sector. In a cell divided into sectors, multiple sectors within the cell can be formed by antenna groups, where each antenna is responsible for communicating with UEs in a portion of the cell.

[0052] Figure 2 Two base stations 210 and 212 in cells 202 and 204 are shown; and a third base station 214 controlling the Remote Radio Header (RRH) 216 in cell 206 is shown. That is, the base stations may have integrated antennas or may be connected to the antenna or RRH via feeder cables. In the example shown, cells 202, 204, and 216 can be referred to as macro cells because base stations 210, 212, and 214 support cells with large sizes. Furthermore, a base station 218 is shown in small cell 208 (e.g., microcell, picocell, femtocell, home base station, home node B, home eNode B, etc.), which may overlap with one or more macro cells. In this example, cell 208 can be referred to as a small cell because base station 218 supports cells with relatively small sizes. Cell sizes can be determined based on system design and component constraints.

[0053] RAN 200 may include any number of radio base stations and cells. Furthermore, the RAN may include relay nodes to extend the size or coverage area of ​​a given cell. Base stations 210, 212, 214, and 218 provide radio access points to the core network for any number of mobile devices. In some examples, base stations 210, 212, 214, and / or 218 may be used in conjunction with the aforementioned... Figure 1 The base station / scheduling entity 108 shown is the same.

[0054] Figure 2 It also includes a quadcopter or drone 220 that can be configured to serve as a base station. That is, in some examples, the cell may not necessarily be stationary, and the geographical area of ​​the cell may move depending on the location of the mobile base station (e.g., the quadcopter 220).

[0055] Within RAN 200, a cell may include one or more UEs, which can communicate with one or more sectors of each cell. Furthermore, each base station 210, 212, 214, 218, and 220 can be configured to provide access to the core network 102 (see [link to core network]) for the UEs in each cell. Figure 1Access points. For example, UE 222 and UE 224 can communicate with base station 210; UE 226 and UE 228 can communicate with base station 212; UE 230 and UE 232 can communicate with base station 214 via RRH 216; UE 234 can communicate with base station 218; and UE 236 can communicate with mobile base station 220. In some examples, UEs 222, 224, 226, 228, 230, 232, 234, 236, 238, 240 and / or 242 can communicate with the access points described above and... Figure 1 The UE / scheduled entity 106 shown is the same.

[0056] In some examples, a mobile network node (e.g., a quadcopter 220) can be configured to act as a UE. For example, the quadcopter 220 can operate within cell 202 by communicating with base station 210.

[0057] In a further aspect of RAN 200, sidelink signals can be used between UEs without relying on information from the base station for scheduling or control. For example, two or more UEs (e.g., UE 226 and UE 228) can communicate with each other using peer-to-peer (P2P) or sidelink signal 227 without relaying the communication through a base station (e.g., base station 212). In a further example, UE 238 is shown communicating with UE 240 and UE 242. Here, UE 238 can act as a scheduling entity or a primary sidelink device, and UE 240 or UE 242 can act as a scheduled entity or a non-primary (e.g., secondary) sidelink device. In yet another example, UEs can act as scheduling entities in device-to-device (D2D), peer-to-peer (P2P), or vehicle-to-vehicle (V2V) networks and / or mesh networks. In a mesh network example, UE 240 and UE 242 can optionally communicate directly with each other in addition to communicating with scheduling entity 238. Therefore, in access systems with scheduled time and frequency resources and wireless communication systems with cellular, P2P, or mesh configurations, a scheduling entity and one or more scheduled entities can communicate using the scheduled resources.

[0058] The air interface in RAN 200 can utilize one or more duplex technologies. Duplex refers to a point-to-point communication link where two endpoints can communicate with each other in both directions. Full-duplex means that two endpoints can communicate with each other simultaneously. Half-duplex means that only one endpoint can send information to the other endpoint at a time using given resources. In a wireless link, a full-duplex channel typically depends on the physical isolation between the transmitter and receiver, as well as appropriate interference cancellation techniques. Full-duplex simulation is typically implemented by using Frequency Division Duplex (FDD) or Time Division Duplex (TDD) to realize the wireless link. In FDD, transmissions in different directions operate at different carrier frequencies. In TDD, time division multiplexing is used to separate transmissions in different directions on a given channel. That is, at some times, the channel is dedicated to transmission in one direction, and at other times, the channel is dedicated to transmission in the other direction, where the direction may change very rapidly, for example, several times per time slot.

[0059] The air interface in RAN 200 can further utilize one or more multiplexing and multiple access technologies to enable simultaneous communication of various devices. For example, the 5G NR specification provides multiple access for UL transmissions from UE 222 and UE 224 to base station 210, and multiplexes DL transmissions from base station 210 to one or more UEs 223 and UE 224 using Orthogonal Frequency Division Multiplexing (OFDM) with a Cyclic Prefix (CP). Furthermore, for UL transmissions, the 5G NR specification provides support for Discrete Fourier Transform Extended OFDM (DFT-s-OFDM) with CP (also known as Single-Carrier FDMA (SC-FDMA)). However, within the scope of this disclosure, multiplexing and multiple access are not limited to the above schemes. For example, UEs can provide UL multiple access using Time Division Multiple Access (TDMA), Code Division Multiple Access (CDMA), Frequency Division Multiple Access (FDMA), Sparse Code Multiple Access (SCMA), Resource Extended Multiple Access (RSMA), or other suitable multiple access schemes. In addition, the base station can use Time Division Multiplexing (TDM), Code Division Multiplexing (CDM), Frequency Division Multiplexing (FDM), Orthogonal Frequency Division Multiplexing (OFDM), Sparse Code Multiplexing (SCM) or other suitable multiplexing schemes to multiplex DL transmissions to the UE.

[0060] Depending on the specific application, radio protocol architectures can take many forms. Based on some examples, radio protocols can be described in three layers. Here, Layer 1 is the lowest layer, implementing various physical layer signal processing functions. Layer 1 is referred to here as the physical layer. Layer 2 is responsible for the physical layer link between the UE and the base station.

[0061] In the user plane, Layer 2 includes the Media Access Control (MAC) sublayer, the Radio Link Control (RLC) sublayer, and the Packet Data Convergence Protocol (PDCP) sublayer. The MAC sublayer provides multiplexing between logical and transport channels. It is also responsible for allocating various radio resources (e.g., resource blocks) within a cell between UEs. The MAC sublayer is also responsible for Hybrid Automatic Repeat Request (HARQ) operations. The RLC sublayer provides segmentation and reassembly of upper-layer data packets, retransmission of lost data packets, and reordering of data packets to compensate for out-of-order reception due to HARQ. The PDCP sublayer provides multiplexing between different radio bearers and logical channels. It also provides header compression for upper-layer data packets to reduce radio transmission overhead, security through encrypted data packets, and handover support for UEs between base stations. A UE can have several upper layers above Layer 2, including, for example, network layers (e.g., IP layers) and application layers.

[0062] In the control plane, the radio protocol architecture of the physical layer and layer 2 is largely the same. In layer 3, the control plane also includes a Radio Resource Control (RRC) sublayer. The RRC sublayer is responsible for acquiring radio resources (i.e., radio bearers) and configuring lower layers using RRC signaling between the base station and the UE.

[0063] Figure 3 Various aspects of this disclosure are illustrated schematically with reference to OFDM waveforms. Those skilled in the art will understand that various aspects of this disclosure can be applied to DFT-s-OFDMA waveforms in substantially the same manner as described below. That is, while some examples of this disclosure may focus on OFDM links for clarity, it should be understood that the same principles can also be applied to DFT-s-OFDMA waveforms.

[0064] In some examples, a frame can refer to a predetermined duration for wireless transmission (e.g., 10 ms). Furthermore, each frame can consist of a set of subframes (e.g., 10 subframes, each 1 ms). A given carrier can include one set of frames in the UL and another set of frames in the DL. Figure 3 An extended view of an exemplary DL subframe 302 is shown, which illustrates the OFDM resource grid 304. However, as will readily be understood by those skilled in the art, the physical transport structure for any particular application may differ from the example described herein, depending on any number of factors. Here, time is in the horizontal direction in units of OFDM symbols; and frequency is in the vertical direction in units of subcarriers or tones.

[0065] Resource grid 304 can schematically represent time-frequency resources for a given antenna port. That is, in examples employing multiple-input multiple-output (MIMO) or spatial multiplexing with multiple available antenna ports, the corresponding multiple resource grids 304 can be available for communication. Each resource grid 304 is divided into multiple resource elements (REs) 306. An RE (which is 1 carrier × 1 symbol) is the smallest discrete part of the time-frequency grid and can contain a single complex value representing data from a physical channel or signal. Depending on the modulation used in a particular implementation, each RE can represent one or more bits of information. In some examples, a block of REs may be referred to as a physical resource block (PRB) or more simply as a resource block (RB) 308, which contains any appropriate number of consecutive subcarriers in the frequency domain. In one example, an RB may include 12 subcarriers, the number of which is independent of the digital scheme used. In some examples, depending on the digital scheme, an RB may include any appropriate number of consecutive OFDM symbols in the time domain. For example, this disclosure assumes that a single RB (such as RB 308) corresponds exactly to a single communication direction (for a given device, either the transmit or receive direction). Such RBs can often be used as bandwidth units to describe the bandwidth of a set of resources (e.g., the bandwidth of n RBs can be used to transmit a channel).

[0066] The UE typically utilizes only a subset of resource grid 304. An RB can be the smallest resource unit that the scheduler can allocate to the UE. Therefore, the more RBs scheduled for the UE and the more advanced the modulation scheme selected for the air interface, the higher the data rate for the UE.

[0067] In this illustration, RB 308 occupies less than the entire bandwidth of subframe 302, with some subcarriers shown above and below RB 308. In a given implementation, subframe 302 can have a bandwidth corresponding to any number of one or more RB 308s. Furthermore, although RB 308 is shown to occupy less than the entire duration of subframe 302, this is only one possible example.

[0068] Each 1ms subframe 302 can consist of one or more adjacent time slots. Figure 3 In this example, a subframe 302 includes four time slots 310, as an illustrative example. In some examples, time slots may be defined based on a specified number of OFDM symbols with a given cyclic prefix (CP) length. For example, a time slot may include 7 or 14 OFDM symbols with a nominal CP. Other examples may include micro-time slots with shorter durations (e.g., one or two OFDM symbols). In some cases, the base station may use resources scheduled for ongoing time slot transmissions for the same or different UEs to transmit these micro-time slots.

[0069] An expanded view of time slot 310 shows that time slot 310 includes a control area 312 and a data area 314. Typically, control area 312 may carry a control channel (e.g., PDCCH), and data area 314 may carry a data channel (e.g., PDSCH or PUSCH). Of course, a time slot may contain all DLs, all ULs, or at least one DL portion and at least one UL portion. Figure 3 The simple structure shown is merely exemplary in nature, and different time slot structures can be utilized, and different time slot structures can include one or more regions in each of the control region and data region.

[0070] Although not in Figure 3 As shown, each RE 306 within a given transmission can carry one or more physical channels, including control channels, shared channels, data channels, etc. Other REs 306 within RB 308 can also carry pilot or reference signals. These pilot or reference signals can provide information for the receiving device to perform channel estimation for the corresponding channels, which enables coherent demodulation / detection of the control and / or data channels within the transmission.

[0071] In DL transmission, a transmitting device (e.g., scheduling entity 108) may allocate one or more REs 306 (e.g., within control area 312) to carry one or more DL control channels. These DL control channels include DL control information (DCI) 114, which typically carries information originating from higher layers, such as the Physical Broadcast Channel (PBCH), Physical Downlink Control Channel (PDCCH), etc., to one or more scheduled entities 106. Additionally, the transmitting device may allocate one or more DL REs to carry DL physical signals that do not typically carry information originating from higher layers. These DL physical signals may include a primary synchronization signal (PSS); a secondary synchronization signal (SSS); a demodulation reference signal (DM-RS); a phase tracking reference signal (PT-RS); a channel state information reference signal (CSI-RS), etc.

[0072] In some examples, the scheduling entity may periodically, intermittently, and / or on-demand transmit SS blocks (SSBs), which include the synchronization signal PSS and SSS (collectively referred to as SS) and PBCH. The SSB may include four consecutive OFDM symbols and may be extended over 240 consecutive subcarriers. Of course, this disclosure is not limited to this particular SSB configuration. Within the scope of this disclosure, other non-limiting examples may utilize more or fewer synchronization signals; may include one or more supplementary channels in addition to the PBCH; may omit the PBCH; and / or may use discontinuous or non-adjacent symbols for the SSB.

[0073] The PDCCH can carry downlink control information (DCI) for one or more UEs in the cell. This may include, but is not limited to, power control commands, scheduling information, permission and / or assignment of REs for DL ​​and UL transmissions.

[0074] In UL transmission, the transmitting device (e.g., the scheduled entity 106) may utilize one or more REs 306 to carry one or more UL control channels (such as the Physical Uplink Control Channel (PUCCH), Physical Random Access Channel (PRACH), etc.). These UL control channels include UL control information 118 (UCI) typically originating from higher layers. Furthermore, UL REs may carry UL physical signals that do not typically carry information from higher layers, such as demodulation reference signals (DM-RS), phase tracking reference signals (PT-RS), probe reference signals (SR), etc. In some examples, the control information 118 may include a scheduling request (SR), i.e., a request for scheduling uplink transmissions for scheduling entity 108. Here, in response to an SR transmitted on control channel 118, scheduling entity 108 may transmit downlink control information 114, which may schedule resources for uplink packet transmissions.

[0075] UL control information may also include Hybrid Automatic Repeat Request (HARQ) feedback, such as Acknowledgment (ACK) or Negative Acknowledgment (NACK), Channel State Information (CSI), or any other suitable UL control information. HARQ is a technique well-known to those skilled in the art, in which the receiving device can verify the integrity of packet transmissions for accuracy, for example, using any appropriate integrity verification mechanism, such as checksum or Cyclic Redundancy Check (CRC). If the receiving device acknowledges the integrity of the transmission, it can send an ACK; otherwise, it can send a NACK. In response to a NACK, the transmitting device can send a HARQ retransmission, which can implement append-and-pause, incremental redundancy, etc.

[0076] In addition to control information, one or more REs 306 (e.g., within data area 314) may be allocated for user data or service data. These services may be carried on one or more service channels (e.g., for DL ​​transmissions, a Physical Downlink Shared Channel (PDSCH); or for UL transmissions, a Physical Uplink Shared Channel (PUSCH)).

[0077] The above description and in Figure 1 and Figure 3The channels or carriers shown may not be all channels or carriers that can be used between the scheduling entity 108 and the scheduled entity 106, and those skilled in the art will recognize that other channels or carriers, such as other service, control and feedback channels, may be used in addition to the channels or carriers shown.

[0078] In OFDM, to maintain subcarrier or tone orthogonality, the subcarrier spacing can be equal to the reciprocal of the symbol period. The digital scheme of an OFDM waveform refers to its specific subcarrier spacing and cyclic prefix (CP) overhead. A scalable digital scheme refers to the network's ability to select different subcarrier spacings and thus utilize each spacing to select the corresponding symbol duration (including the CP length). Using a scalable digital scheme, the nominal subcarrier spacing (SCS) can be scaled up or down by an integer multiple. In this way, regardless of the CP overhead and the selected SCS, symbol boundaries can be aligned at certain common multiples of symbols (e.g., aligned at the boundaries of each 1ms subframe). The range of SCSs can include any suitable SCS. For example, a scalable digital scheme can support SCSs ranging from 15kHz to 480kHz.

[0079] To illustrate this concept of scalable digital schemes, Figure 4 A first RB402 with a nominal digital scheme and a second RB 404 with a scaled digital scheme are shown. As an example, the first RB 402 may have a nominal subcarrier spacing (SCS) of 30 kHz. n ), and the "nominal" symbol duration of 333 μs. n Here, in the second RB 404, the scaled digital scheme includes either twice the nominal SCS or 2×SCS. n =60kHz. Because this provides twice the bandwidth per symbol, it results in a shortened symbol duration to carry the same information. Therefore, in the second RB404, the scaled digital scheme includes a scaled symbol duration of half the nominal symbol duration or (symbol duration...). n )÷2=167μs.

[0080] Figure 5 This is a block diagram illustrating an example hardware implementation of a scheduling entity 500 employing a processing system 514. For example, the scheduling entity 500 could be as shown in... Figure 1 , 2 The user equipment (UE) shown in any one or more of the figures 7, 10, 12, 14, 16, and / or 18. In another example, the scheduling entity 500 may be as shown in Figure 1 , 2The base stations (e.g., gNBs) shown in any one or more of the figures 10, 12, 14, 16, and / or 18. In some scenarios, a device can have both scheduling and being scheduled functions. This allows a single device to act as either a base station or a UE, depending on the desired operation.

[0081] Scheduling entity 500 may include a processing system 514 having one or more processors 504. Examples of processors 504 include microprocessors, microcontrollers, digital signal processors (DSPs), field-programmable gate arrays (FPGAs), programmable logic devices (PLDs), state machines, gated logic, discrete hardware circuitry, and other suitable hardware configured to perform the various functions described herein. In various examples, scheduling entity 500 may be configured to perform any one or more of the functions described herein. That is, the processor 504 used in scheduling entity 500 may be configured (e.g., in coordination with memory 505) to implement the functions described below and Figure 7-18 Any one or more of the processes and procedures shown in the document.

[0082] Processing system 514 can be implemented using a bus architecture, typically represented by bus 502. Depending on the specific application and overall design constraints of processing system 514, bus 502 may include any number of interconnect buses and bridges. Bus 502 communicatively couples together various circuits including one or more processors (typically represented by processor 504), memory 505, and computer-readable media (typically represented by computer-readable media 506). Bus 502 may also link various other circuits such as timing sources, peripheral devices, voltage regulators, and power management circuits, which are well known in the art and therefore will not be described further. Bus interface 508 provides an interface between bus 502 and transceiver 510. Transceiver 510 provides a communication interface or unit for communicating with various other devices over a transmission medium. Depending on the nature of the device, a user interface 512 (e.g., keypad, display, speaker, microphone, joystick) may also be provided. Of course, such a user interface 512 is optional, and in some examples (such as base stations), it may be omitted.

[0083] In some aspects of this disclosure, processor 504 may include SSB / CORESET circuitry 540. Circuitry 540 may be configured (e.g., coordinated with memory 505) for various functions, including, for example, configuring and / or sending one or more SSBs and / or CORESETs. For example, SSB / CORESET circuitry 540 may be configured to implement one or more of the functions described below with respect to the following figures: Figure 10 Including, for example, boxes 1021–1027; Figure 12 Including, for example, boxes 1221–1226; Figure 14 Including, for example, boxes 1421–1425; Figure 16 Including, for example, boxes 1621–1623; and / or Figure 18 This includes, for example, blocks 1821–1825. The SSB / CORESET circuit 540 may include a communication interface and may take the form of a receiver, transmitter, or transceiver. The SSB / CORESET circuit 540 may be one or more components.

[0084] Processor 504 may also include a reduced-capability UE communication circuitry 542. Circuitry 542 may be configured (e.g., coordinated with memory 505) for various functions, including, for example, communicating with one or more types or categories of reduced-capability UEs other than conventional UEs or other UEs. For example, reduced-capability UE communication circuitry 542 may be configured to implement one or more of the functions described below with respect to the following figures: Figure 10 Including, for example, boxes 1021–1027; Figure 12 Including, for example, boxes 1221–1226; Figure 14 Including, for example, boxes 1421–1425; Figure 16 Including, for example, boxes 1621–1623; and / or Figure 18 This includes, for example, boxes 1821–1825. The reduced-capability UE communication circuitry 542 may include a communication interface and may take the form of a receiver, transmitter, or transceiver. The communication circuitry 542 may be one or more components.

[0085] Processor 504 is typically responsible for managing bus 502 and general processing, including executing software stored on computer-readable medium 506. When executed by processor 504, this software causes processing system 514 to perform the various functions described below for any particular device. Processor 504 may also use computer-readable medium 506 and memory 505 to store data manipulated by processor 504 while executing the software.

[0086] One or more processors 504 in the processing system can execute software. Software, whether referred to as software, firmware, middleware, microcode, hardware description language, or other terms, should be broadly interpreted as instructions, instruction sets, code, code segments, program code, programs, subroutines, software modules, applications, software applications, software packages, routines, subroutines, objects, executable files, threads of execution, procedures, functions, etc. Software may reside on computer-readable medium 506. Computer-readable medium 506 may be a non-transitory computer-readable medium. For example, non-transitory computer-readable media include magnetic storage devices (e.g., hard disks, floppy disks, magnetic tapes), optical disks (e.g., compact discs (CDs) or digital versatile discs (DVDs)), smart cards, flash memory devices (e.g., card, stick, or key drives), random access memory (RAM), read-only memory (ROM), programmable ROM (PROM), erasable PROM (EPROM), electrically erasable PROM (EEPROM), registers, removable disks, and any other suitable medium for storing software and / or instructions that can be accessed and read by a computer. The computer-readable medium 506 may be located within, outside, or distributed among multiple entities including the processing system 514. The computer-readable medium 506 may be embodied in a computer program product. For example, the computer program product may include a computer-readable medium with encapsulation material. Those skilled in the art will recognize how the functions described herein are best implemented, depending on the specific application and the overall design constraints imposed on the system as a whole.

[0087] In one or more examples, computer-readable storage medium 506 may store computer-executable code including SSB / CORESET instructions 562, which configure scheduling entity 500 for various functions, including, for example, configuring and / or sending one or more SSBs and / or CORESETs. For example, SSB / CORESET instructions 562 may be configured to cause scheduling entity 500 to perform one or more of the functions described below with reference to the following figures: Figure 10 Including, for example, boxes 1021–1027; Figure 12 Including, for example, boxes 1221–1226; Figure 14 Including, for example, boxes 1421–1425; Figure 16 Including, for example, boxes 1621–1623; and / or Figure 18 , including, for example, boxes 1821–1825.

[0088] In one configuration, the apparatus 500 for wireless communication includes a unit for transmitting one or more signals (e.g., transceiver 510) and a unit for configuring signal transmission (e.g., SSB / CORESET circuitry 540 and / or a reduced-capability UE communication circuitry 542). In one aspect, the aforementioned unit may be... Figure 5 The processor 504 shown is configured to perform the functions described in the aforementioned unit. Alternatively, the aforementioned unit may be a circuit or any device configured to perform the functions described in the aforementioned unit.

[0089] Of course, in the above example, the circuitry included in processor 504 is provided merely as an example, and other units for performing the described functions may be included within various aspects of this disclosure, including but not limited to instructions stored in computer-readable storage medium 506, or Figure 1 , 2 The figures described in any of the figures 5 and / or 6, and utilizing, for example, the information presented herein regarding... Figure 7 , 8 Any other suitable device or unit for the process and / or algorithm described in 1, 9, 10, 11, 12, 13, 14, 15, 16, 17 and / or 18.

[0090] Figure 6 This is a conceptual diagram illustrating an example hardware implementation of an exemplary scheduled entity 600 employing a processing system 614. According to various aspects of this disclosure, elements, or any portion of elements, or any combination of elements, may be implemented using a processing system 614 including one or more processors 604. For example, the scheduled entity 600 may be a user equipment (UE), such as in… Figure 1 , 2 The reduced capability (RedCap) UE, low-end RedCap UE, high-end RedCap UE, or conventional UE shown in any one or more of the figures 7, 10, 12, 14, 16, and / or 18.

[0091] Processing system 614 can be with Figure 5 The processing system 514 shown is essentially the same, including a bus interface 608, a bus 602, a memory 605, a processor 604, and a computer-readable medium 606. Furthermore, the scheduled entity 600 may include a user interface 612 and a transceiver 610, which are substantially similar to those described above. Figure 5 The user interface and transceiver described below. That is, the processor 804, as utilized in the scheduled entity 800, can be configured (e.g., in coordination with memory 805) to implement the user interface and transceiver described below. Figure 9 Any one or more processes shown in the diagram.

[0092] In some aspects of this disclosure, processor 604 may include initial acquisition circuitry 640, configured (e.g., in coordination with memory 605) for various functions, including, for example, searching, receiving, decoding, and / or processing SSB / control resource sets and corresponding system information. For example, initial acquisition circuitry 640 may be configured to implement one or more of the functions described below with reference to the figures below: Figure 7 Including, for example, boxes 702–706; Figure 10 This includes, for example, boxes 1041–1044 and / or 1061–1065; Figure 12 This includes, for example, boxes 1241–1243 and / or boxes 1261–1264; Figure 14 This includes, for example, boxes 1441–1443 and / or boxes 1461–1464; Figure 16 This includes, for example, boxes 1641–1643 and / or boxes 1661–1663; and / or Figure 18 This includes, for example, boxes 1841–1843 and / or boxes 1861–1863.

[0093] Processor 604 may also include wireless communication circuitry 642, which is configured (e.g., coordinated with memory 605) for various functions, including, for example, wireless communication with a radio access network. For example, wireless communication circuitry 642 may be configured to implement one or more of the functions described below with respect to the following figures: Figure 7 Including, for example, boxes 702–706; Figure 10 This includes, for example, boxes 1041–1044 and / or 1061–1065; Figure 12 This includes, for example, boxes 1241–1243 and / or boxes 1261–1264; Figure 14 This includes, for example, boxes 1441–1443 and / or boxes 1461–1464; Figure 16 This includes, for example, boxes 1641–1643 and / or boxes 1661–1663; and / or Figure 18 This includes, for example, boxes 1841–1843 and / or boxes 1861–1863.

[0094] Furthermore, the computer-readable storage medium 606 may store computer-executable code including an initial fetch instruction 652, which will be configured by the scheduled entity 600 for various functions, including, for example, searching, receiving, decoding, and / or processing SSB / control resource sets and corresponding system information. For example, the initial fetch instruction 652 may be configured to cause the scheduled entity 600 to perform one or more of the functions described below with reference to the figures: Figure 7 Including, for example, boxes 702–706; Figure 10 This includes, for example, boxes 1041–1044 and / or 1061–1065; Figure 12 This includes, for example, boxes 1241–1243 and / or boxes 1261–1264; Figure 14 This includes, for example, boxes 1441–1443 and / or boxes 1461–1464; Figure 16 This includes, for example, boxes 1641–1643 and / or boxes 1661–1663; and / or Figure 18 This includes, for example, boxes 1841–1843 and / or boxes 1861–1863.

[0095] Computer-readable storage medium 606 may store computer-executable code including, for example, wireless communication instructions 654, which will be configured by the scheduled entity 600 for various functions, including, for example, wireless communication with a radio access network. For example, wireless communication instructions 654 may be configured to cause the scheduled entity 600 to perform one or more of the functions described below with reference to the figures below: Figure 7 Including, for example, boxes 702–706; Figure 10 This includes, for example, boxes 1041–1044 and / or 1061–1065; Figure 12 This includes, for example, boxes 1241–1243 and / or boxes 1261–1264; Figure 14 This includes, for example, boxes 1441–1443 and / or boxes 1461–1464; Figure 16 This includes, for example, boxes 1641–1643 and / or boxes 1661–1663; and / or Figure 18 This includes, for example, boxes 1841–1843 and / or boxes 1861–1863.

[0096] In one configuration, the wireless communication apparatus 600 includes units for transmitting and receiving wireless signals, units for scanning a frequency set for wireless network acquisition, and units for establishing a connection with the wireless network. In one aspect, the aforementioned units may be... Figure 6 The processor 604 shown is configured to perform the functions described in the aforementioned unit. Alternatively, the aforementioned unit may be a circuit or any device configured to perform the functions described in the aforementioned unit.

[0097] Of course, in the above example, the circuitry included in processor 604 is provided merely as an example, and other units for performing the described functions may be included within various aspects of this disclosure, including but not limited to instructions stored in computer-readable storage medium 606, or Figure 1 , 2 The figures described in any of the figures 5 and / or 6, and utilizing, for example, the information presented herein regarding... Figure 7 , 8Any other suitable device or unit for the process and / or algorithm described in 1, 9, 10, 11, 12, 13, 14, 15, 16, 17 and / or 18.

[0098] In some aspects of this disclosure, processor 604 may include initial acquisition circuitry 640 configured for various functions, including, for example, searching, receiving, decoding, and / or processing SSB / control resource sets and corresponding system information. Processor 604 may also include wireless communication circuitry 642 configured for various functions, including, for example, wireless communication with a radio access network.

[0099] Reduced device capabilities and initial network acquisition

[0100] For any wireless device operating in a given network, a key capability affecting its operation within that network is the bandwidth or bandwidth range that the device can support. And in some examples, a given UE may be able to dynamically modify its bandwidth; for example, the range of frequencies it uses to communicate with the network. Here, bandwidth may correspond to the difference between higher and lower frequencies and is not intended to imply any particular frequency. For example, a UE may utilize a narrower bandwidth (e.g., a relatively small difference between higher and lower frequencies) to conserve energy, or utilize a wider bandwidth (e.g., a relatively large difference between higher and lower frequencies) to increase data rates. A UE with dynamic bandwidth capability may be able to support one or more bandwidths (e.g., between minimum and maximum bandwidth, the range of bandwidth operation, or modify bandwidth usage during operation).

[0101] Bandwidth ranges can also be used for various deployments. For example, according to one aspect of this disclosure, the maximum bandwidth required for a UE to support operation in a given network is referred to as the “mandatory maximum bandwidth” of that network. In other words, a UE with dynamic bandwidth capabilities as described above can support a maximum bandwidth greater than or equal to a specified minimum or threshold value (which may be referred to as the mandatory maximum bandwidth for operation on that network). If the UE is capable, it is free to support larger bandwidths; for example, the UE can support a maximum bandwidth wider than the mandatory maximum bandwidth. And if permitted, the UE can also support smaller bandwidths; for example, the UE can support and employ a bandwidth narrower than the mandatory maximum bandwidth, but the UE should also be able to support at least the mandatory maximum bandwidth. That is, if the network is to support such a UE, it must generally support the mandatory maximum bandwidth.

[0102] In various aspects of this disclosure, the network may support wireless communication services for UEs using or employing relatively narrow bandwidth. In the art, such a UE may be referred to as a reduced-capacity UE or a RedCap UE. Here, narrow bandwidth does not specifically refer to any particular bandwidth, but rather to a reduced or narrower bandwidth relative to the bandwidth that another UE can use for wireless communication services on the same network.

[0103] Networks supporting RedCap UEs can do this through various characteristics. In a network supporting degraded UEs, the network may support more than one type of degraded device, each with different functionalities. For example, different degraded device types may have different supported bandwidths. Therefore, these different degraded device types can be classified based on given capabilities and / or operating parameters. Such classification of device types can be done in any suitable manner, including but not limited to device type (e.g., IoT devices, smart wearables, sensors, cameras, etc.) or device capabilities (e.g., low supported bandwidth, high supported bandwidth, etc.).

[0104] The UE discussed in this paper can access a communication network in various ways. An initial acquisition process can provide the UE with initial access to the network (e.g., attachment or connection), for example, when the UE is powered on. To facilitate initial network acquisition, a scheduling entity can provide neighboring UEs with System Information (SI) characterizing their corresponding cell. The scheduling entity can provide this system information in multiple components, for example, using a component called Minimal System Information (MSI) and another component called Other System Information (OSI). For this purpose, the scheduling entity can periodically, intermittently, or on demand broadcast Synchronization Signal Blocks (SSBs) on the cell. Such SSBs can include a Physical Broadcast Channel (PBCH), which can carry a set of information corresponding to the MSI to provide the UE with the most basic information required for initial cell access and enable the UE to acquire any OSI that the scheduling entity can periodically broadcast or send on demand. For example, the PBCH can carry a Master Information Block (MIB). Here, the MIB can provide the UE with parameters for monitoring the Control Resource Set (CORESET), such as the Control Resource Set Index value, which is configured to indicate to the UE the resource set or location on which the scheduling entity will broadcast the Control Resource Set. In some examples, although the control resource set index can signal the resource location corresponding to a downlink control channel (e.g., PDCCH), the control resource set can be carried on any suitable channel. Here, the control resource set can transmit parameters to the UE that identify or indicate the location on System Information Block Type 1 (SIB1) that can be referred to as the Residual Minimal System Information (RMSI). In some examples, although SIB1 can be carried on the downlink shared data channel (PDSCH), the SIB can be carried on any suitable channel. Once the UE obtains the MIB and SIB1, such a UE can possess the MSI for the corresponding cell.

[0105] OSI can include any SI that is not broadcast in MSI. In some examples, PDSCH can carry multiple SIBs, not limited to SIB1 discussed above. Here, the scheduling entity can provide OSI in these SIBs (e.g., SIB2 and above).

[0106] When a network supports two or more UE categories (including degraded UEs or other UE types), the initial acquisition process for the network may be incompatible with one or more UE categories. For example, Figure 7 This is a flowchart illustrating the UE acquisition process from a network generally described above, based on some aspects of this disclosure. As described below, a particular implementation may omit some or all of the shown features, and some of the shown features may not be required to implement all embodiments. In some examples, Figure 6The scheduled entity 600 shown (e.g., a degraded UE, a legacy UE, or any other suitable category of UE) can be configured to perform process 700. In some examples, any suitable means or unit for performing the functions or algorithms described below can perform process 700.

[0107] At box 702, the UE can initiate the network acquisition process by performing a cell search. For example, the UE can employ a grating (e.g., a frequency grating, channel grating, and / or synchronization grating) that defines a set or sequence of frequency bands and carrier frequencies that the UE can monitor or scan. The UE may include transceiver 610 to search a specified set of frequency bands. Alternatively or additionally, for each carrier frequency, the UE can identify the strongest cell, measure certain cell attributes, and obtain the cell's associated SSB. In various examples, the UE can utilize stored information (such as its connection history and / or configuration that the UE may have received from the RAN) to scan the set of carrier frequencies in some order or sequence. If and when the UE identifies a suitable cell (e.g., a cell that is not blocked and has measured cell attributes that meet a given cell selection criterion), the UE can then camp on that cell to acquire network connectivity.

[0108] At box 704, when the UE locates and receives an SSB, it can read or process the information contained in the SSB. For example, a portion of the SSB (e.g., the PBCH) may include a Master Information Block (MIB). The MIB may be an information packet or information element that includes parameters for the UE to use to monitor control resource sets. In some examples, such parameters may include a control resource set index value, which is configured to instruct the RAN to broadcast the resource set or location of the control resource set on it. Although the control resource set may reside on a control channel (such as the PDCCH), it can be implemented on any suitable channel.

[0109] At box 706, when the UE receives a control resource set as indicated in the MIB, it can read the information contained therein. For example, a portion of the control resource set (e.g., CORESET0) may include or point to a system information block (e.g., SIB1), which carries further system information beyond that provided in the MIB. In some examples, the MIB and SIB1 together can provide the minimum system information (MSI) for the UE to acquire from the network.

[0110] The capabilities of a given UE (e.g., corresponding to the UE category) can affect Figure 7The performance of the UE during the process. For example, consider a UE class configured with a reduced maximum bandwidth capability B. To accommodate UEs in this class, in some examples described herein, the RAN can configure SSB and / or control resource set transmissions with bandwidth C ≤ B. If the RAN is configured with SSB and / or control resource set transmissions with bandwidth C > B, UEs in this class may be unable to perform initial acquisition on that RAN.

[0111] In another example described herein, the RAN can therefore configure the SSB and control resource set differently for different UE categories, for example, based on the maximum bandwidth of different UE categories. However, if the maximum bandwidth capability of a given UE affects the first step of the initial acquisition process (e.g., box 702), the RAN may not be able to determine an appropriate UE-specific or UE-category-specific bandwidth for the SSB and / or control resource set. Even if the UE has a mechanism for sending its capability information (e.g., its maximum supported bandwidth) to the RAN, such a capability signaling phase will occur after the initial acquisition process 700. This raises the question of how the RAN considers the UE's capability information when configuring SSB and control resource set transmissions.

[0112] The techniques discussed herein can be used to deploy various types or categories of UEs for communication. In some aspects, this disclosure provides examples of network deployments that enable scheduling entities to support legacy UEs as well as various other (e.g., UEs other than legacy UEs) categories of UEs (e.g., including degraded UEs), including UEs with reduced bandwidth capabilities. In some disclosed examples, different categories of UEs (e.g., including but not limited to legacy UEs and degraded UEs) may share the same SSB and control resource set used for the initial acquisition process. In some further disclosed examples, the network may provide different or separate SSBs (e.g., dedicated SSBs) and / or control resource sets for a subset of supported UE categories (e.g., degraded UEs). That is, the network may broadcast two or more SSBs and / or control resource sets on two or more different corresponding radio resource sets (e.g., at different frequencies, at different times, and / or utilizing any other suitable multiplexing mechanism). Therefore, in some examples, this disclosure refers to SSB / control resource set sharing, wherein the SSB and control resource set are shared by two or more types of UEs (e.g., legacy UEs and degraded UEs); and refers to separate SSB / control resource sets, wherein separate SSBs and / or control resource sets are provided for a subset of supported UE types (e.g., degraded UEs).

[0113] In some of the examples disclosed herein, the network (e.g., RAN) or scheduling entity may send separate sets of SSBs and / or control resources specified for a subset of supported UE classes (e.g., for degraded UEs). That is, the scheduling entity may send one or more sets of SSBs and / or control resources specifically (or, in some examples, specifically) designated for one or more identified UE classes (such as degraded UEs), while simultaneously sending one or more other sets of SSBs and / or control resources intended to be received by one or more other identified UE classes (such as legacy UEs or other UEs). Using different SSB types (e.g., same, separate, different, etc.) allows for flexibility in network design and operation, taking into account device operating parameters.

[0114] As an example, a scheduling entity can send a separate SSB designated for a UE with reduced capabilities. Figure 8 An example is schematically illustrated of a single SSB 802 (denoted as SSB') designated for a degraded UE or intended for reception by it. As further shown, the scheduling entity sends a conventional SSB 804 (denoted as SSB) intended for reception by another UE category, such as a legacy UE. In this example, the scheduling entity can employ any suitable technique to enable different UE categories to distinguish the single SSB' 802 from the conventional SSB 804. That is, the scheduling entity can employ signaling mechanisms to indicate to a given UE which SSB it should monitor. For example, the scheduling entity can include an information element (e.g., an "extended" bit or any suitable information element) within the SSB, which the UE can use to distinguish the degraded UE's single SSB 802 from the legacy UE's SSB 804. In another example, the scheduling entity can deploy different SSBs on different rasteres so that the corresponding UE category will not search for the location of other SSBs during the initial acquisition process. In other words, the network can have the capability to support a given UE category (e.g., a degraded UE) that is known to have a separate or different grating for its cell search, which differs from the gratings used by one or more other UE categories (e.g., legacy UEs). Therefore, the scheduling entity can broadcast a separate SSB'802 on a frequency corresponding to the separate or different gratings used by degraded UEs, and can also broadcast the nominal gratings used by legacy UEs.

[0115] SSB transport can be deployed for various purposes. For example, in Figure 8In the provided description, the network also provides a separate control resource set 806 (labeled CS0') for the reduced-capability UE. This separate control resource set can be distinguished from the legacy control resource set 808 used for legacy or other UEs. As shown, the bandwidth of the legacy control resource set 808 may be wider than the bandwidth of the separate control resource set 806. Therefore, the forced maximum bandwidth for a reduced-capability UE receiving both the separate SSB 802 and the separate control resource set 806 may be narrower than the forced maximum bandwidth for a legacy UE receiving both the legacy SSB 804 and the legacy control resource set 808. In this description, the forced maximum bandwidth for a legacy UE is shown as wide enough to receive both the separate control resource set 806 and the legacy control resource set 808. While this is an option, it is not a requirement. That is, in some examples, the forced maximum bandwidth for a given UE or UE class can correspond to any suitable parameters, including but not limited to the SSB and control resource set provided for that UE or UE class.

[0116] By deploying different or separate SSB and / or control resource sets for different UE categories in this way, the network can signal different sets of parameters for different UE categories, in addition to or replacing the information elements used to distinguish the corresponding SSB and / or control resource sets. For example, a UE with reduced capabilities may only need a small set of information in SIB1, because other information carried in the traditional SIB1 can be applied to capabilities or features beyond those supported by such a UE. The network can correspondingly reduce the size of the individual control resource set 806 for UEs with reduced capabilities, thereby reducing signaling overhead.

[0117] Communication equipment can be configured to support different levels of communication capabilities. According to another aspect of this disclosure, the use of such a separate SSB and / or control resource set for a capability-reduced UE can be extended to cover situations where the network supports two or more different capability-reduced UE categories, such as high-end and low-end categories. For example, a high-end category capability-reduced UE may support a relatively wide mandatory maximum bandwidth (e.g., 20 MHz), and a low-end category capability-reduced UE may support a relatively narrow mandatory maximum bandwidth (e.g., 10 MHz).

[0118] like Figure 9As shown, the network can support different types or categories of UEs with reduced capabilities. This support can be achieved by deploying, for example, separate SSBs 902 and 906 corresponding to one or more different UE categories with reduced capabilities, as well as separate control resource sets 904 and 908. For example, to support high-end device categories, the network can deploy a first SSB / control resource set 904 / 908 with relatively wide bandwidth, and a second SSB / control resource set 902 / 906 with relatively narrow bandwidth. In some examples, the first SSB / control resource set 904 / 908 may be shared by high-end reduced-capability UEs and legacy UEs. However, this is not necessary, and those skilled in the art will recognize that these techniques can be modified so that another UE category (e.g., legacy UEs) can utilize any suitable SSB / control resource set, which may or may not correspond to a specific UE category. Figure 9 The SSB / control resource set is shown in the figure.

[0119] Considering different UE categories, the size and format of the operating bandwidth can be set. For example, the bandwidth used to receive the first SSB / control resource set 904 / 908 could be 20MHz. In this example, during network acquisition, a UE with reduced high-end capabilities can search for the first SSB 904 (in some examples, this can be shared with a legacy UE).

[0120] Furthermore, to support low-end device categories, the network can deploy a second (e.g., separate) SSB / control resource set 902 / 906 with relatively narrow bandwidth. For example, the bandwidth used to receive the second SSB / control resource set 902 / 906 could be 10 MHz. Therefore, during network acquisition, low-end, degraded UEs can search for the second SSB 902. The second SSB can be configured to be appropriately distinguished from the first (traditional) SSB 904. For example, as described above, one or both of the corresponding SSBs may include "extended" bits or other suitable information elements carrying information indicating whether the corresponding SSB is the second (separate) SSB 902 for low-end, degraded UEs or the first SSB 904 for high-end, degraded UEs.

[0121] In certain situations, UEs with reduced high-end capabilities may face challenging conditions, such as operating at or near cell edges. According to another aspect of this disclosure, UEs operating according to the example techniques described above may optionally utilize a second (separate) SSB / control resource set 902 / 906. That is, although the second (separate) SSB / control resource set 902 / 906 is provided or specified for low-end device categories, UEs with reduced high-end capabilities may utilize it. This is in... Figure 9As shown on the right. That is, according to another aspect of this disclosure, the cross-use of a second (separate) SSB / control resource set can be adopted, such that the second (separate) SSB / control resource set 902 / 906 is not entirely dedicated to low-end capability-reduced UEs, but can be used by high-end capability-reduced UEs or even by legacy UEs (where it may be beneficial).

[0122] In a further example, for low-end, reduced-capability device categories, the network can provide a second control resource set 906 and / or associated data channel transmissions (e.g., SIB1) 910. These can be transmitted, for example, via increased repetition or redundancy, to compensate for the potential loss due to the reduced number of antennas on such low-end, reduced-capability UEs. Although Figure 9 The repetition of SIB 910 within control resource set 906 is shown, but this is merely for visual reference. That is, as described above, control resource set 906 can provide information identifying or indicating a separate resource (e.g., PDSCH) carrying the SIB. By increasing redundancy in the SIB transmission, the UE can more easily detect the transmission. In other words, the initial network acquisition process may become more reliable. Therefore, in some cases, high-end degraded devices that may operate at the cell edge or otherwise under difficult channel conditions can utilize the separate control resource set 906 for low-end degraded devices, which they can receive more reliably.

[0123] Figure 10 This is a flowchart illustrating an exemplary process for network access according to some aspects of this disclosure (e.g., corresponding to...). Figure 8 / 9). As described below, a particular implementation may omit some or all of the features shown, and some of the features shown may not be required to implement all embodiments. Figure 10 The diagram illustrates function blocks or procedures corresponding to three exemplary nodes, each node having a separate corresponding column. For example, the first column 1002 could correspond to... Figure 5 The scheduling entity shown is 500; the second column, 1004, can correspond to... Figure 6 The scheduled entity 600 shown; and the third column 1006 can correspond to Figure 6 Another scheduled entity 600 is shown. In some examples, any suitable means or unit for performing the functions or algorithms described below can perform this task. Figure 10 The process is shown.

[0124] In the example shown, the scheduled entity or node corresponding to the second column 1004 is identified as a degraded UE 1004, as described herein. And the scheduled entity or node corresponding to the third column 1006 is identified as a conventional UE 1006, as described herein. The degraded UE 1004 can be considered as belonging to a first category by the network, and therefore can be considered as an element or member of a first group of one or more UEs (e.g., UEs of the degraded category). The conventional UE 1006 can be considered as belonging to a second category by the network, and therefore can be considered as an element or member of a second group of one or more UEs (e.g., UEs of the conventional category). Although the examples discussed below refer to conventional UE 1006, it should be understood that the processes and techniques discussed can be equivalently applied to or similarly applied to high-end degraded UEs. That is, in another example, the first category UE 1004 can correspond to a low-end degraded UE, and the second category UE 1006 can correspond to a high-end degraded UE, as discussed above.

[0125] In some examples, the discussion and corresponding flowcharts below may describe operations that occur in parallel or simultaneously at their respective nodes. Therefore, for clarity, the discussion below generally traces the operations sequentially. However, this disclosure is not limited to the specific order of operations disclosed.

[0126] At boxes 1041 and 1061, the reduced-capability UE 1004 and the conventional UE 1006 each perform a cell search procedure to attempt to locate and acquire a connection to the wireless network. For example, the respective UE may receive waveforms or signals of selected carrier frequencies specified in a channel grating or channel list stored in memory to seek transmissions of SSBs or other suitable reference signals from nearby cells.

[0127] At block 1021, scheduling entity 1002 transmits a first SSB; and at block 1022, scheduling entity 1002 transmits a second SSB. Here, the first SSB may include appropriate information indicating that the first SSB is designated for a first group of UEs. The second SSB can be distinguished or identified in a similar manner. Scheduling entity 1002 may employ any suitable mechanism to enable the UE receiving the SSB to determine that the SSB is designated for a selected category or UE group (e.g., designating the first SSB for a first UE category / group and the second SSB for a second UE category / group). For example, scheduling entity 1002 may transmit the SSB on a carrier frequency designated for a UE of the selected category, such that cell search performed by a UE of the selected category can locate the SSB transmission by a grating configured to include the corresponding carrier frequency. In another example, scheduling entity 1002 may employ an explicit signaling mechanism, such as including a corresponding information element in the SSB configured to identify the SSB as designated for a UE of the selected category.

[0128] At block 1042, the reduced-capability UE 1004 can receive a first SSB. Here, the reduced-capability UE 1004 can identify the first SSB as being designated for a first UE category or group, i.e., the reduced-capability UE 1004 is a member of that category or group. For example, if the reduced-capability UE 1004 performs a cell search using a raster appropriately configured to search for SSBs on selected carrier frequencies specified for SSBs designated for UEs of the first category, the reduced-capability UE 1004 can assume that the first SSB is designated for a first-category UE. In another example, the reduced-capability UE 1004 can read the information included in the first SSB and determine, based on the indications contained therein, that the first SSB is designated for a first-category UE. When the reduced-capability UE 1004 appropriately identifies the first SSB, the reduced-capability UE 1004 reads and obtains information for identifying and obtaining the identified control resource set (e.g., a first control resource set). In some examples, the information identifying the first control resource set may include an index value, such as a control resource set index value, which in some examples may be a 4-bit information element as described above.

[0129] At optional box 1062, conventional UE 1006 may optionally receive the first SSB. Here, conventional UE 1006 may identify the first SSB as being designated for a first UE category or group, i.e., a category or group to which conventional UE 1006 is not a member. In the example where scheduling entity 1002 uses appropriately configured channel gratings to distinguish or identify SSBs for different UE categories or groups, conventional UE 1006 may search for other carrier frequencies and may skip or ignore the first SSB (hence the optional nature of box 1062). In the example where scheduling entity 1002 uses explicit signaling in the SSB to distinguish or identify SSBs for different UE categories or groups, conventional UE 1006 may identify such a first SSB in essentially the same manner as described above for the capability-reduced UE 1004. When conventional UE 1006 appropriately identifies the first SSB, conventional UE 1006 may forgo reading and obtaining information that may be contained therein (such as the MIB).

[0130] At optional box 1043, the reduced-capability UE 1004 may optionally receive a second SSB. Here, the reduced-capability UE 1004 may identify the second SSB as being designated for a second UE category or group, i.e., a category or group to which the reduced-capability UE 1004 is not a member. In the example where scheduling entity 1002 uses appropriately configured channel gratings to distinguish or identify SSBs for different UE categories or groups, the reduced-capability UE 1004 may search for other carrier frequencies and may skip or ignore the second SSB (hence the optional nature of box 1043). In the example where scheduling entity 1002 uses explicit signaling in the SSB to distinguish or identify SSBs for different UE categories or groups, conventional UE 1006 may identify such a second SSB in essentially the same manner as described above for conventional UE 1006 in conjunction with the first SSB. When the reduced-capability UE 1004 appropriately identifies the second SSB, the reduced-capability UE 1004 may forgo reading and obtaining information that may be contained therein (such as the MIB).

[0131] At box 1063, conventional UE 1006 may receive a second SSB. Here, conventional UE 1006 may identify the second SSB as being designated for a second UE category or group, i.e., conventional UE 1006 is a member of that category or group. For example, if conventional UE 1006 performs a cell search using a raster appropriately configured to search for the SSB on a selected carrier frequency specified for the SSB designated for a UE of the second category, then conventional UE 1006 may assume that the second SSB is designated for a UE of the second category. In another example, conventional UE 1006 may read the information included in the second SSB and determine, based on the indication contained therein, that the second SSB is designated for a UE of the second category. When conventional UE 1006 appropriately identifies the second SSB, conventional UE 1006 reads and obtains information for identifying and obtaining the identified control resource set (e.g., a second control resource set). In some examples, the information identifying the first control resource set may include an index value, such as a control resource set index value, which in some examples may be a 4-bit information element as described above.

[0132] At block 1023, scheduling entity 1002 can configure a first bandwidth for a first control resource set based on the assumed bandwidth capability of a first UE category or group; and at block 1024, scheduling entity 1002 can configure a second bandwidth for a second control resource set based on the assumed bandwidth capability of a second UE category or group. For example, scheduling entity 1002 can establish the assumed bandwidth capability by obtaining or determining information related to the bandwidth capability of a given category of UEs (including guidance (or adherence to specified bandwidth capability requirements that various UEs may also know) in various ways. Configuring the bandwidth to be used for the control resource set can include, for example, scheduling the control resource set to transmit on a resource set corresponding to the bandwidth. According to some examples, the corresponding first and second bandwidths may be the same value, or they may be different values. In one example, the first bandwidth for UEs of the first category may be relatively narrower than the second bandwidth for UEs of the second category. That is, the first UE category or group may include UEs with reduced capabilities that could benefit from a narrower bandwidth control resource set.

[0133] At optional box 1025, scheduling entity 1002 may optionally configure a first control resource set to provide supplementary redundancy for the system information block. That is, in some examples, the first control resource set may at least partially include information representing a system information block (such as SIB1). According to one aspect of this disclosure, scheduling entity 1002 may configure the control resource set to improve the reliability of SIB transmission. For example, scheduling entity 1002 may schedule the control resource set such that information representing the system information block can be repeated two or more times to provide supplementary redundancy for the SIB. In another example, scheduling entity 1002 may employ a suitable channel coding mechanism to encode at least a portion of the information in the control resource set. Typically, such channel coding has a given code rate, where a higher code rate represents increased redundancy in the encoded output of the channel encoder, and a lower code rate represents reduced redundancy in the encoded output. Therefore, in some examples, scheduling entity 1002 may employ a higher code rate to encode the SIB compared to the code rate used by scheduling entity 1002 for other information in the control resource set and / or for the transmission of other control resource sets. In this way, the encoded SIB may exhibit supplementary redundancy.

[0134] At block 1026, scheduling entity 1002 may transmit a first control resource set on a first bandwidth; and at block 1027, scheduling entity 1002 may transmit a second control resource set on a second bandwidth. The corresponding transmissions may employ the bandwidths configured accordingly as described above.

[0135] At block 1044, the degraded UE 1004 can receive a first control resource set and obtain system information, such as that carried in the SIB. For example, the degraded UE 1004 can monitor radio resources based on the information in the first SSB, as described above. When the scheduling entity 1002 transmits the control resource set on these resources, the degraded UE 1004 can receive and read the information contained therein.

[0136] At optional box 1064, the conventional UE 1006 may optionally receive the first control resource set and obtain, for example, system information carried in the SIB. For example, as described above, in some examples, the conventional UE 1006 may operate at the cell edge or otherwise under difficult channel conditions. In such cases, the conventional UE 1006 may have difficulty reliably receiving and decoding its designated control resource set. Therefore, in some examples, the conventional UE 1006 may monitor a first bandwidth designated for different UE categories (e.g., a degraded UE category). In examples where the first control resource set or the first SIB contained therein is configured with supplementary redundancy, as described above, the conventional UE 1006 may receive the control resource set of a degraded UE more successfully, which may be advantageous to or usable by the conventional UE 100. However, in some examples, the conventional UE 1006 may choose not to receive the first control resource set.

[0137] At box 1065, the conventional UE 1006 can receive a second control resource set and obtain, for example, system information carried in the SIB. For example, the conventional UE 1006 can monitor radio resources based on the information in the second SSB, as described above. When the scheduling entity 1002 transmits the control resource set on these resources, the conventional UE 1006 can receive and read the information contained therein.

[0138] As another example, the network can send a shared SSB or an SSB that is received by two or more different categories of UEs (e.g., shared by both a degraded UE and a legacy UE). Here, in addition to the conventional control resource set intended for reception by legacy or other UE categories, the network can also send a separate control resource set for a given category (e.g., degraded UE). Figure 11 An example SSB / control resource set configuration according to this technology is shown. In this example, both a degraded UE and a legacy UE can perform a cell search procedure and receive the same SSB 1122. Here, the network can use appropriate signaling within SSB 1122 to instruct the degraded UE to read a separate control resource set (and corresponding SIB1) 1126, which may have reduced bandwidth compared to the legacy control resource set 1128. Such SSB signaling can be implemented in a backward-compatible manner with legacy UEs. For example, by utilizing “reserved” or otherwise unused bits in SSB 1122, a legacy UE can ignore this information element because its information is not specified according to the configuration of such a legacy UE. However, the degraded UE can read the corresponding information element to determine appropriate parameters for monitoring the separate control resource set 1126.

[0139] Figure 12This is a flowchart illustrating an exemplary process for network access according to some aspects of this disclosure (e.g., corresponding to...). Figure 11 As described below, a particular implementation may omit some or all of the shown features, and some of the shown features may not be required to implement all embodiments. Figure 10 Same, Figure 12 The flowchart shown illustrates functional blocks or processes corresponding to three exemplary nodes: scheduling entity 1202 (e.g., corresponding to...). Figure 5 The scheduling entity 500 shown), and the UE 1204 with reduced capabilities (for example, corresponding to...) Figure 6 The scheduled entity 600 shown), and the traditional UE 1206 (e.g., corresponding to Figure 6 The scheduled entity shown is 600. Similarly, with Figure 10 Similarly, in various examples, those skilled in the art can replace the capability-reduced UE 1204 and the conventional UE 1206 with the low-end capability-reduced UE 1204 and the high-end capability-reduced UE 1206. In some examples, any suitable means or unit for performing the functions or algorithms described below can perform... Figure 12 The process is shown.

[0140] At boxes 1241 and 1261, the reduced-capability UE 1204 and the conventional UE 1206 each perform a cell search procedure to attempt to locate and acquire a connection to the cellular network. For example, the respective UE may receive waveforms or signals of selected carrier frequencies specified in a channel grating or channel list stored in memory to seek transmissions of SSBs or other suitable reference signals from nearby cells.

[0141] At box 1221, scheduling entity 1202 sends an SSB. Here, the SSB may include appropriate information indicating that the SSB is designated for a group or category of one or more UEs, but in some examples, such designation may be omitted from the SSB. The SSB includes information for identifying a first set of control resources for one or more UEs (e.g., a degraded UE) in a first group or first category, and information for identifying a second set of control resources for one or more UEs (e.g., a legacy UE) in a second group or second category.

[0142] At box 1242, the reduced-capability UE 1204 can receive an SSB. Here, the reduced-capability UE 1204 can read and obtain information for identifying and obtaining the identified control resource set (e.g., a first control resource set). Here, any suitable implicit or explicit technique can be used (e.g., as described above, using bits reserved in the SSB or otherwise unused) to distinguish the information indicating or identifying the first control resource set from one or more other control resource sets that may be included in the SSB. In some examples, the information indicating or identifying the first control resource set may include an index value, such as a control resource set index value, which in some examples may be a 4-bit information element as described above.

[0143] At box 1262, conventional UE 1206 can receive an SSB. Here, conventional UE 1206 can read and obtain information used to identify and obtain an identified control resource set (e.g., a second control resource set). Here, the information indicating or identifying the second control resource set can be distinguished from one or more other control resource sets that may be included in the SSB in the same or similar manner as described above for the capability-reduced UE 1204. In some examples, the information indicating or identifying the first control resource set may include an index value, such as a control resource set index value, which in some examples may be a 4-bit information element as described above.

[0144] At block 1222, scheduling entity 1202 can configure a first bandwidth for a first control resource set based on the assumed bandwidth capability of a first UE category or group; and at block 1223, scheduling entity 1202 can configure a second bandwidth for a second control resource set based on the assumed bandwidth capability of a second UE category or group. For example, scheduling entity 1202 can establish the assumed bandwidth capability by obtaining or determining information related to the bandwidth capability of a given category of UEs (including guidance (or adherence to specified bandwidth capability requirements that various UEs may also know) in various ways. Configuring the bandwidth to be used for the control resource set can include, for example, scheduling the control resource set to transmit on a resource set corresponding to the bandwidth. According to some examples, the corresponding first and second bandwidths may be the same value, or they may be different values. In one example, the first bandwidth for UEs of the first category may be relatively narrower than the second bandwidth for UEs of the second category. That is, the first UE category or group may include UEs with reduced capabilities that could benefit from a narrower bandwidth control resource set.

[0145] At optional box 1224, scheduling entity 1202 may optionally configure a first control resource set to provide supplementary redundancy for the system information block. That is, in some examples, the first control resource set may at least partially include information representing the system information block (such as SIB1). According to one aspect of this disclosure, scheduling entity 1202 may configure the control resource set to improve the reliability of SIB transmission. For example, scheduling entity 1202 may schedule the control resource set such that information representing the system information block can be repeated two or more times to provide supplementary redundancy for the SIB. In another example, scheduling entity 1202 may employ an appropriate code rate for channel coding to provide supplementary redundancy, as described above.

[0146] At block 1225, scheduling entity 1202 may transmit a first control resource set on a first bandwidth; and at block 1226, scheduling entity 1202 may transmit a second control resource set on a second bandwidth. The corresponding transmissions may employ the bandwidths configured accordingly as described above.

[0147] At box 1243, the degraded UE 1204 can receive a first control resource set and obtain system information, such as that carried in the SIB. For example, the degraded UE 1204 can monitor radio resources based on the information in the SSB, as described above. When the scheduling entity 1202 transmits the control resource set on these resources, the degraded UE 1204 can receive and read the information contained therein.

[0148] At optional box 1263, the conventional UE 1206 may optionally receive the first control resource set and obtain, for example, system information carried in the SIB. For example, as described above, in some examples, the conventional UE 1206 may operate at the cell edge or otherwise under difficult channel conditions. In such cases, the conventional UE 1206 may have difficulty reliably receiving and decoding its designated control resource set. Therefore, in some examples, the conventional UE 1206 may monitor a first bandwidth designated for different UE categories (e.g., a degraded UE category). In examples where the first control resource set or the first SIB contained therein is configured with supplementary redundancy, as described above, the conventional UE 1206 may receive the control resource set of a degraded UE more successfully, which may be advantageous to or usable by the conventional UE 1206. However, in some examples, the conventional UE 1206 may choose not to receive the first control resource set.

[0149] At box 1264, the conventional UE 1206 can receive a second control resource set and obtain, for example, system information carried in the SIB. For example, the conventional UE 1206 can monitor radio resources based on the information in the SSB, as described above. When the scheduling entity 1202 transmits the control resource set on these resources, the conventional UE 1206 can receive and read the information contained therein.

[0150] As yet another example, such as Figure 13 As shown, SSB 1342 and Control Resource Set 1348 can be shared between two or more UE categories (e.g., shared by both degraded UEs and legacy UEs, as well as other UEs), but a split between them may occur at the SIB1 level. That is, as described above, Control Resource Set 1348 may include information indicating the location of SIB1 within the PDSCH. Therefore, the network may include (e.g., within SSB 1342) a special allocation of SIB1 1346 intended for a given category (e.g., degraded UEs), carried in the shared Control Resource Set 1348 but configured to be ignored by legacy or other UE categories. In this way, a degraded UE may receive a different SIB1 1346 than a legacy or other UE receives.

[0151] Figure 14 This is a flowchart illustrating an exemplary process for network access according to some aspects of this disclosure (e.g., corresponding to...). Figure 13 As described below, a particular implementation may omit some or all of the shown features, and some of the shown features may not be required to implement all embodiments. Figure 10 Same, Figure 14 The flowchart shown illustrates functional blocks or processes corresponding to three exemplary nodes: scheduling entity 1402 (e.g., corresponding to...). Figure 5 The scheduling entity 500 shown), and the UE 1404 with reduced capability (for example, corresponding to the scheduling entity 500 shown), are examples of UEs with reduced capability. Figure 6 The scheduled entity 600 shown), and the traditional UE 1406 (e.g., corresponding to Figure 6 The scheduled entity shown is 600. Similarly, with Figure 10 Similarly, in various examples, those skilled in the art can replace the capability-reduced UE 1404 and the conventional UE 1406 with the low-end capability-reduced UE 1404 and the high-end capability-reduced UE 1406. In some examples, any suitable means or unit for performing the functions or algorithms described below can perform... Figure 14 The process is shown.

[0152] At boxes 1441 and 1461, the reduced-capability UE 1404 and the conventional UE 1406 each perform a cell search procedure to attempt to locate and acquire a connection to the cellular network. For example, the respective UE may receive a waveform or signal of a selected carrier frequency specified in a channel grating or channel list stored in memory to seek transmissions of SSBs or other suitable reference signals from nearby cells.

[0153] At box 1421, scheduling entity 1402 sends an SSB. Here, the SSB may include appropriate information indicating that the SSB is designated for one or more UE groups or categories, but in some examples, such designation may be omitted. The SSB may contain information for identifying a shared control resource set. That is, the identified control resource set may be designated for two or more groups or categories of UEs and may include two or more corresponding SIBs. Here, the SSB may include information for identifying a first SIB for one or more UEs (e.g., a degraded UE) in a first group or first category within the shared control resource set and information for identifying a second SIB for one or more UEs (e.g., a legacy UE) in a second group or second category within the shared management resource set.

[0154] At box 1442, the reduced-capability UE 1404 can receive an SSB. Here, the reduced-capability UE 1404 can read and obtain information for identifying and obtaining an identified control resource set (e.g., a shared control resource set). In some examples, the information indicating or identifying the control resource set may include an index value, such as a control resource set index value, which in some examples may be a 4-bit information element as described above. Furthermore, the reduced-capability UE 1404 can read and obtain information for identifying and obtaining an identified SIB (e.g., a first SIB designated for a first UE category or group (such as a reduced-capability UE)) within the shared control resource set.

[0155] At box 1462, the conventional UE 1406 can receive an SSB. Here, the conventional UE 1406 can read and obtain information for identifying and obtaining an identified control resource set (e.g., a shared control resource set). In some examples, the information indicating or identifying the control resource set may include an index value, such as a control resource set index value, which in some examples may be a 4-bit information element as described above. Furthermore, the conventional UE 1406 can read and obtain information for identifying and obtaining an identified SIB (e.g., a second SIB designated for a second UE category or group, such as a conventional UE) within the shared control resource set.

[0156] At block 1422, scheduling entity 1402 may configure a shared control resource set to include a first SIB and a second SIB. Here, scheduling entity 1402 may configure the bandwidth of the first SIB based on the assumed bandwidth of a first group of UEs (e.g., a degraded UE). In some examples, the bandwidth of the first SIB may be less than (or narrower than) the bandwidth of the entire shared control resource set. That is, to accommodate the operation of degraded UEs, the shared control resource set may be configured such that degraded UEs can obtain network connectivity by receiving only a subset of the shared control resource set, which corresponds to the bandwidth of the first SIB within that shared control resource set. At block 1423, scheduling entity 1402 may configure a second bandwidth for a second system information block in the shared control resource set based on the assumed bandwidth capabilities of a second UE category or group. For example, scheduling entity 1402 may establish assumed bandwidth capabilities by obtaining or determining information related to the bandwidth capabilities of a given category of UEs in various ways (including guidance (or adherence to specified bandwidth capability requirements that various UEs may also be aware of). Configuring the bandwidth to be used for a shared resource set may include, for example, scheduling transmissions of two or more SIBs with different corresponding bandwidths on a portion of a shared control resource set. According to some examples, the corresponding first and second bandwidths may have the same value, or they may have different values. In one example, the first bandwidth for a first category of UEs may be relatively narrower than the second bandwidth for a second category of UEs. That is, the first UE category or group may include UEs with reduced capabilities that could benefit from a narrower bandwidth SIB.

[0157] At optional box 1424, scheduling entity 1402 may optionally configure a control resource set to provide supplementary redundancy for the first SIB. That is, in some examples, scheduling entity 1402 may configure the control resource set to improve the reliability of the transmission of the first SIB. For example, scheduling entity 1402 may schedule the shared control resource set such that information representing the first system information block can be repeated two or more times to provide supplementary redundancy for the first SIB. In another example, scheduling entity 1402 may employ an appropriate code rate for channel coding to provide supplementary redundancy, as described above.

[0158] At box 1425, scheduling entity 1402 may send a shared control resource set, which includes a first SIB with a first bandwidth and a second SIB with a second bandwidth that is wider than the first bandwidth. The respective SIBs may employ bandwidths configured accordingly as described above.

[0159] At block 1443, the reduced-capability UE 1404 can receive a shared control resource set and obtain system information, for example, carried in the first SIB. For instance, the reduced-capability UE 1404 can monitor radio resources based on information in the SSB, as described above. When the scheduling entity 1402 transmits the control resource set on these resources, the reduced-capability UE 1404 can receive and read the information contained therein. Here, as described above, the reduced-capability UE 1404 can receive a portion of the full control resource set corresponding to the first SIB.

[0160] At optional box 1463, the conventional UE 1406 may optionally receive a shared control resource set and obtain system information, for example, carried in a first SIB. For example, as described above, in some examples, the conventional UE 1406 may operate at the cell edge or otherwise under difficult channel conditions. In such cases, the conventional UE 1406 may have difficulty reliably receiving and decoding its designated control resource set. Therefore, in some examples, when the conventional UE 1406 receives a shared control resource set, the conventional UE 1406 may read and obtain a first SIB carried on a first bandwidth, which is designated for a different UE category (e.g., a degraded UE category). In examples where the first SIB is configured with supplementary redundancy, as described above, the conventional UE 1406 may receive the SIB of a degraded UE more successfully, which may be advantageous to or usable by the conventional UE 1406. However, in some examples, the conventional UE 1406 may choose not to read and utilize the first SIB.

[0161] At box 1464, the conventional UE 1406 can receive the shared control resource set and obtain system information, for example, carried in the second SIB. For example, the conventional UE 1406 can monitor radio resources based on the information in the SSB, as described above. When the scheduling entity 1402 transmits the control resource set on these resources, the conventional UE 1406 can receive and read the information contained therein. Here, as described above, the conventional UE 1406 can receive the full control resource set. Although in some examples, if the conventional UE 1406 corresponds to a UE with reduced high-end capabilities or other UE categories with a maximum bandwidth capability that may be lower than the full bandwidth of the control resource set, similar to the reduced-capability UE 1404, the conventional UE 1406 can receive a portion of the full control resource set. In any case, after receiving the control resource set, the conventional UE 1406 can read and obtain the second SIB carried in the shared control resource set, as indicated in the SSB.

[0162] In another example, two or more UE categories (e.g., both degraded UEs and legacy UEs) may share the full SSB / control resource set. Figure 15 An example of shared SSB 1502 and control resource set 1506 is shown. In this example, certain considerations can be taken into account when configuring the SSB / control resource set due to the potential limitations of devices with reduced capabilities. For example, such as... Figure 15 As can be seen, the bandwidth of SSB / control resource set transmission 1502 / 1506 can be limited to the mandatory maximum bandwidth for all supported UE classes (including reduced-capability UEs) and may not utilize any wider bandwidth capabilities of legacy UEs.

[0163] To illustrate this impact, Figure 16 This is a flowchart illustrating an exemplary process for network access according to some aspects of this disclosure (e.g., corresponding to...). Figure 15 As described below, a particular implementation may omit some or all of the shown features, and some of the shown features may not be required to implement all embodiments. Figure 10 Same, Figure 16 The flowchart shown illustrates functional blocks or processes corresponding to three exemplary nodes: scheduling entity 1602 (e.g., corresponding to...). Figure 5 The scheduling entity 500 shown), and the UE 1604 with reduced capability (for example, corresponding to the scheduling entity 500 shown), are examples of UEs with reduced capability. Figure 6 The scheduled entity 600 shown), and the traditional UE 1606 (e.g., corresponding to Figure 6 The scheduled entity shown is 600. Similarly, with Figure 10 Similarly, in various examples, those skilled in the art can replace the capability-reduced UE 1604 and the conventional UE 1606 with the low-end capability-reduced UE 1604 and the high-end capability-reduced UE 1606. In some examples, any suitable means or unit for performing the functions or algorithms described below can perform... Figure 16 The process is shown.

[0164] At boxes 1641 and 1661, the reduced-capability UE 1604 and the conventional UE 1606 each perform a cell search procedure to attempt to locate and acquire a connection to the cellular network. For example, the respective UE may receive waveforms or signals of selected carrier frequencies specified in a channel grating or channel list stored in memory to seek transmissions of SSBs or other suitable reference signals from nearby cells.

[0165] At box 1621, scheduling entity 1602 sends an SSB configured to be shared by one or more UEs of at least two categories or groups. Here, the SSB may contain information for identifying the shared control resource set. In some examples, the information indicating or identifying the control resource set may include an index value, such as a control resource set index value, which in some examples may be a 4-bit information element as described above.

[0166] At box 1642, the reduced-capability UE 1604 can receive SSB; and at box 1662, the conventional UE 1606 can receive SSB. Here, the corresponding UE 1604 / 1606 can read and obtain information for identifying and obtaining the identified control resource set (e.g., shared control resource set).

[0167] At box 1622, scheduling entity 1602 can configure a shared control resource set. Here, scheduling entity 1602 can configure the bandwidth of the shared control resource set based on the assumed bandwidth of one or more UEs in the first group (e.g., degraded UEs). That is, to accommodate the operation of degraded UEs, the shared control resource set can be configured such that degraded UEs can obtain network connectivity by receiving the shared control resource set. Therefore, as described above, conventional UEs or other higher-capacity UEs may be restricted to receiving a relatively narrow bandwidth control resource set to accommodate network sharing with UEs of the degraded category or group.

[0168] At box 1623, scheduling entity 1602 may send a shared control resource set, which includes system information (e.g., SIB). The shared control resource set uses the bandwidth configured as described above.

[0169] At block 1643, the reduced-capability UE 1604 can receive a shared control resource set and obtain, for example, system information carried in the SIB; and at block 1663, the conventional UE 1606 can receive a shared control resource set and obtain, for example, system information carried in the SIB. For example, as described above, UE 1604 / 1606 can monitor radio resources based on information in the SSB. When scheduling entity 1602 transmits a control resource set on these resources, UE 1604 / 1606 can receive and read the information contained therein.

[0170] Since this technology can limit a traditional UE or other UEs with relatively high bandwidth capabilities to a narrow set of control resources, another aspect of this disclosure provides a process for adapting a UE with reduced capabilities without affecting the bandwidth of the control resource set provided for a traditional UE.

[0171] Table 1 below is a repetition of Table 13-8 from Section 13 of 3GPP TS 38.213 Release 16.5. This table shows certain parameters related to control resource set (CORESET) transmissions, which the network can use for transmissions according to the 5G NR specifications.

[0172] Table 1

[0173]

[0174] In this table, the first column (index) shows the control resource set index value. According to some examples, the scheduling entity may provide this core resource set index value to the UE as a 4-bit field carried in the SSB transmission. In this way, the scheduling entity can indicate the multiplexing pattern or mode of the control resource set, which is shown in the second column (SS / PBCH block and CORESET multiplexing mode). For example, if the index value is 0, 1, 2, or 3, the SSB / control resource set multiplexing mode is defined as mode 1. In mode 1, the SSB and control resource set are time-division multiplexed (TDM) and transmitted in the same bandwidth, but the transmission time of the control resource set is later than that of the SSB.

[0175] The third column of Table 1 provides the bandwidth of the control resource set by the number of RBs (see above). Figure 3 (Description). When the network utilizes multiplexing mode 1 (again, the control resource set is transmitted in the same bandwidth as the SSB but later in time), if the UE can support the control resource set bandwidth, then since the SSB bandwidth is narrower than the control resource set bandwidth, the UE can support both the SSB and the control resource set. Therefore, in this multiplexing mode, the UE only needs to consider the control resource set bandwidth, and if it supports it, it can be assumed that the UE also supports the SSB bandwidth.

[0176] When the network utilizes multiplexing modes 2 or 3, the SSB and control resource set are frequency-division multiplexed (FDM) and transmitted simultaneously, separated from each other in frequency by a certain configured offset (see column 5 of Table 1). With this configuration, if a particular UE (e.g., a reduced-capacity UE) has a maximum supported bandwidth that matches the bandwidth of the control resource set, that UE cannot receive this configuration. That is, in FDM mode, the scheduling entity transmits the SSB at frequencies outside the UE's bandwidth capabilities. This can potentially limit network compatibility with reduced-capacity UEs that support relatively narrow maximum bandwidths (i.e., too narrow to receive both the FDM SSB and the control resource set).

[0177] When sharing an SSB / control resource set between a degraded UE and a legacy UE, one option for the network is to determine that the mandatory maximum bandwidth for any UE that can operate on the network must be large enough to cover all possible configurations of the SSB / control resource set. Therefore, according to one aspect of this disclosure, when the network shares an SSB / control resource set between two or more UE classes, the network can implement one or more rules for the SSB / resource set configuration. For example, one rule the network can utilize is that it can operate under a constraint or rule such that, for the SSB / control resource set configuration, the network is not allowed to adopt an SSB / control resource set multiplexing mode with a combined bandwidth greater than the mandatory maximum bandwidth of the supported UE classes. That is, the network can have a rule where the mandatory maximum bandwidth of all supported UE classes is ≥ the maximum SSB / control resource set bandwidth in the multiplexing mode to be utilized. However, for some degraded UEs that may have relatively narrow maximum bandwidths, such constraints can significantly reduce the set of information the network can provide to legacy UEs in SSB / control resource set messages, as described above regarding... Figure 15 and Figure 16 visible.

[0178] Therefore, according to another aspect of this disclosure, the network can define rules or employ techniques in which a degraded UE can apply different interpretations or translations to the contents of the control resource set index value (e.g., as shown in Table 1 above) provided in the SSB, or to the contents of one or more other fields associated with the control resource set index value, than to the nominal interpretations or translations provided in Table 1 above. That is, while conventional UEs configured according to specifications will typically interpret or translate the core resource set index value as prescribed, UEs according to certain aspects of this disclosure (e.g., degraded UEs) can interpret or translate the same core resource set index value in different ways to correspond to different SSB / control resource set multiplexing modes (besides expected or standard values).

[0179] For example, the scheduling entity can send a first control resource set 1702 for a traditional UE or other UE class, and can send different, separate control resource sets 1704 (in... Figure 17 This is marked as CS0' for use by UEs with reduced capabilities. Here, a UE with reduced capabilities can read the same control resource set index value contained in SSB 1706. However, here, a UE with reduced capabilities can interpret or translate this index value to have a different meaning than that described in Table 1 above, and may locate a separate control resource set 1704 based on this reinterpretation or separate translation. In yet another example, a UE with reduced capabilities can utilize any other suitable information element carried in SSB 1706 or otherwise to trigger its reinterpretation or separate translation of the multiplexing mode, as described below.

[0180] For example, the network can send SSB 1706, which includes information indicating that the control resource set index value is 4. This information indicates to a legacy UE (as seen in Table 1) that the SSB / control resource set multiplexing mode is operating in mode 3. That is, such a UE will interpret the control resource set index as indicating that SSB 1706 and control resource set 1702 will be used in mode 3. Figure 17 The FDM layout shown has an offset for a configuration of 20 or 21 RBs (e.g.). However, a UE with reduced capability can reinterpret the same control resource set index value 4, causing the UE to detect a temporal offset from SSB 1706 instead of a different control resource set 1704 (such as the first control resource set 1702) that performs FDM with SSB 1706. For example, as Figure 17 As shown, the network can transmit a separate control resource set 1704 that performs TDM with SSB 1706 (e.g., transmits with SSB 1706 at a different time but within the same bandwidth). In this way, a UE with a reduced capacity for a forced maximum bandwidth that is as wide as the separate control resource set 1704 but narrower than the first control resource set 1702 can properly receive the full SSB / control resource set 1706 / 1704.

[0181] According to a further aspect of this disclosure, when a degraded UE utilizes this reinterpretation rule, the scheduling entity may not need to transmit the control resource set in the same bandwidth as SSB 1706. That is, if the degraded UE supports RF retuning, the scheduling entity can transmit a third control resource set 1708 (labeled "CS0"), which can be time-offset from SSB 1706 and also frequency-offset, such as... Figure 17 As shown. In this way, a UE with reduced capabilities can have a relatively narrow forced maximum bandwidth and still be able to operate on a given network.

[0182] While such index reinterpretation rules could provide greater operability for different types of degraded UEs, it could mean that the scheduling entity would send one or more separate control resource sets 1704 / 1708 for the degraded UE. However, if such a degraded UE attempts to acquire a connection with a legacy base station configured according to legacy specifications that do not include such reinterpretation possibilities, the degraded UE might waste power by applying the reinterpretation and searching for a separate control resource set 1704 / 1708 that does not exist.

[0183] Furthermore, when a UE receives a control resource set as part of its initial acquisition process, the UE typically tunes its receiver / transceiver to an appropriate carrier frequency or bandwidth to receive the control resource set. Therefore, the bandwidth carrying the control resource set can be referred to as the initial bandwidth. Once such a UE is configured with initial bandwidth, it can typically use that initial bandwidth for transmissions to the network (e.g., random access procedures or other channel access procedures). However, in the case of SSB / control resource set sharing as described herein, the scheduling entity may cause a potentially large number of UEs to tune to receive the same control resource set. In such a case, a large number of UEs may cluster together and continue operating in the same bandwidth (i.e., the initial bandwidth). If a large number of such UEs attempt to use the same bandwidth for transmissions, such as for random access channel (RACH) transmissions, this can lead to network capacity issues. Therefore, in another aspect of this disclosure, the network can reconfigure the initial bandwidth to move different groups of UEs with reduced capabilities to different bandwidths to reduce such clustering effects.

[0184] Figure 18 This is a flowchart illustrating an exemplary process for network access according to some aspects of this disclosure (e.g., corresponding to...). Figure 17 As described below, a particular implementation may omit some or all of the shown features, and some of the shown features may not be required to implement all embodiments. Figure 10 Same, Figure 18 The flowchart shown illustrates functional blocks or processes corresponding to three exemplary nodes: scheduling entity 1802 (e.g., corresponding to...). Figure 5 The scheduling entity 500 shown), and the UE 1804 with reduced capabilities (for example, corresponding to...) Figure 6 The scheduled entity 600 shown), and the traditional UE 1806 (e.g., corresponding to Figure 6 The scheduled entity shown is 600. Similarly, with Figure 10 Similarly, in various examples, those skilled in the art can replace the capability-reduced UE 1804 and the conventional UE 1806 with the low-end capability-reduced UE 1804 and the high-end capability-reduced UE 1806. In some examples, any suitable means or unit for performing the functions or algorithms described below can perform... Figure 18 The process is shown.

[0185] At boxes 1841 and 1861, the reduced-capability UE 1804 and the conventional UE 1806 each perform a cell search procedure to attempt to locate and acquire a connection to the cellular network. For example, the respective UE may receive a waveform or signal of a selected carrier frequency specified in a channel grating or channel list stored in memory to seek transmissions of SSBs or other suitable reference signals from nearby cells.

[0186] At box 1821, scheduling entity 1802 sends an SSB configured to be shared by one or more UEs of at least two categories or groups. Here, the SSB may include information for identifying a control resource set. In some examples, the information indicating or identifying the control resource set may include an index value, such as a control resource set index value, which in some examples may be a 4-bit information element as described above. And as further discussed above, scheduling entity 102 may plan any appropriate number of two or more different or separate translations of the information for identifying the control resource set. In further examples (e.g., see boxes 1824 / 1825 below), the scheduling entity may optionally include translation information elements or translation modification information elements to provide instructions or parameters to be applied to UEs of a given category to identify the control resource set by translating the information.

[0187] At box 1842, the reduced-capability UE 1804 can receive an SSB. Here, the reduced-capability UE 1804 can read and obtain information for identifying and obtaining an identified control resource set (e.g., a first control resource set). According to one aspect of this disclosure, the reduced-capability UE 1804 can apply a first translation or interpretation rule to the control resource set index, and the reduced-capability UE 1803 can utilize this first translation or interpretation rule to identify and obtain the first control resource set.

[0188] At box 1862, conventional UE 1806 can receive an SSB. Here, conventional UE 1806 can read and obtain information for identifying and obtaining an identified control resource set (e.g., a second control resource set). According to one aspect of this disclosure, conventional UE 1806 can apply a second translation or interpretation rule to the control resource set index, and conventional UE 180 can utilize this second translation or interpretation rule to identify and obtain the second control resource set.

[0189] At box 1822, scheduling entity 1802 may configure and send a first control resource set based on a first translation of one or more SSB fields (e.g., control resource set index and / or one or more other SSB fields associated with the index value); and at box 1823, scheduling entity 1802 may configure and send a second control resource set based on a second translation of one or more SSB fields that is different from the first translation.

[0190] At box 1843, the reduced-capability UE 1804 can receive a first control resource set and obtain, for example, system information carried in the SIB. For example, as described above, the reduced-capability UE 1804 can monitor the first radio resource based on a first interpretation of one or more SSB fields associated with the control resource set index value in the SSB. When the scheduling entity 1802 transmits the control resource set on these resources, the reduced-capability UE 1804 can receive and read the information contained therein.

[0191] At box 1863, the conventional UE 1806 can receive a second control resource set and obtain, for example, system information carried in the SIB. For example, as described above, the conventional UE 1806 can monitor a second radio resource (different from the second resource) based on a second translation (different from the first translation) of one or more SSB fields associated with the control resource set index value in the SSB. When the scheduling entity 1802 transmits the control resource set on these resources, the conventional UE 1806 can receive and read the information contained therein.

[0192] In various examples, the first radio resource and / or the second radio resource can be multiplexed with the SSB in any suitable manner, for example, offset from the SSB in frequency, time, or both frequency and time.

[0193] At box 1824, scheduling entity 1802 may send control information for characterizing or modifying the translation rules of one or more SSB fields associated with the control resource set index value in the SSB to be used by a given UE category. For example, translation information elements or translation modification information elements may identify a given UE group or category (e.g., a degraded UE) and may provide instructions or parameters to the UE receiving the corresponding control resource set, characterizing the translation or interpretation rules. In some examples, translation modification information elements may be carried in the SSB sent in box 1821 above, allowing UEs of the corresponding category to apply the new rules during their respective initial acquisition processes.

[0194] At box 1825, scheduling entity 1802 can configure and send a third control resource set based on a third translation of one or more SSB fields (e.g., the control resource set index and / or one or more other SSB fields associated with the index value).

[0195] Another example with multiple characteristics:

[0196] Example 1: A method, apparatus, and non-transitory computer-readable medium for wireless communication. A UE (e.g., a RedCap UE) scans a set of frequencies for wireless network acquisition and receives a first SSB designated for a first group of one or more UEs. The first SSB includes information for identifying a first control resource set. The UE receives the first control resource set and obtains corresponding system information for the wireless network, and establishes a connection with the wireless network based on the system information.

[0197] Example 2: According to the method, apparatus, and non-transitory computer-readable medium of Example 1, wherein the UE further receives a second SSB designated for one or more UEs in a second group. The second SSB includes information for identifying a second control resource set. The UE waives the right to receive the second control resource set based on the fact that the UE is outside the second group of one or more UEs.

[0198] Example 3: According to the method, apparatus, and non-transitory computer-readable medium of Example 1, wherein the UE further receives a second SSB designated for a second group of one or more UEs. The second SSB includes information for identifying a second control resource set. The UE receives the first control resource set and obtains corresponding system information for the wireless network, regardless of whether the UE is outside the second group of one or more UEs.

[0199] Example 4: A method, apparatus, and nontransitory computer-readable medium according to any one of Examples 1 to 3, wherein the first SSB includes an information element indicating that the first SSB is designated for the first group of one or more UEs.

[0200] Example 5: A method, apparatus, and non-transitory computer-readable medium according to any one of Examples 1 to 3, wherein the first SSB is carried on a frequency designated for use with the first group of one or more UEs.

[0201] Example 6: A method, apparatus, and non-transitory computer-readable medium for wireless communication. A UE scans a set of frequencies for acquisition in a wireless network. The UE receives an SSB, the SSB including information for identifying a first control resource set designated for a first group of one or more UEs, and further including information for identifying a second control resource set designated for a second group of one or more UEs. The UE receives the first control resource set based on the fact that the UE is a member of the first group of one or more UEs. The UE obtains corresponding first system information for the wireless network and establishes a connection with the wireless network based on the system information.

[0202] Example 7: The method, apparatus, and non-transitory computer-readable medium according to Example 6, wherein the first SSB includes an information element indicating that the first control resource set is designated for the first group of one or more UEs.

[0203] Example 8: A method, apparatus, and non-transitory computer-readable medium for wireless communication. A UE scans a set of frequencies for acquisition in a wireless network and receives a SSB, the SSB including information for identifying a control resource set. The UE receives the control resource set, which includes first system information designated for a first group of UEs and second system information designated for a second group of UEs. Based on the control resource set, the UE obtains corresponding first system information for the wireless network based on whether the UE is a member of one or more UEs in the first group. The UE establishes a connection with the wireless network based on the first system information.

[0204] Example 9: The method, apparatus, and non-transitory computer-readable medium according to Example 8, wherein the first system information includes information elements indicating that the first system information is designated for the first group of one or more UEs.

[0205] Example 10: A method, apparatus, and non-transitory computer-readable medium according to any one of Examples 8 or 9, wherein the first system information occupies a first bandwidth, and wherein the second system information occupies a second bandwidth that is wider than the first bandwidth.

[0206] Example 11: A method, apparatus, and non-transitory computer-readable medium for wireless communication. A UE scans a set of frequencies for acquisition in a wireless network and receives a Service Stub (SSB), the SSB including information elements for identifying a control resource set. The UE also receives a first control resource set based on a first translation of the information elements for identifying the control resource set, the first translation being designated for a first group of one or more UEs. The UE obtains corresponding first system information for the wireless network based on the first control resource set and establishes a connection with the wireless network based on the first system information.

[0207] Example 12: According to the method, apparatus, and non-transitory computer-readable medium of Example 11, wherein the UE receives a translation information element indicating parameters for identifying the first translation of the information element of the first control resource set. The translation information element is designated for a first group of UEs, wherein the UE is a member of the first group of UEs.

[0208] Example 13: A method, apparatus, and non-transitory computer-readable medium for wireless communication. A scheduling entity transmits a first SSB, the first SSB including information for identifying a first control resource set for a first group of one or more UEs. The scheduling entity transmits a second SSB, the second SSB including information for identifying a second control resource set for a second group of one or more UEs. The scheduling entity transmits the first control resource set on a first bandwidth for the first group of UEs and transmits the second control resource set on a second bandwidth for the second group of one or more UEs, the second bandwidth being wider than the first bandwidth.

[0209] Example 14: The method, apparatus and non-transitory computer-readable medium according to Example 13, wherein the first SSB further includes information indicating that the first SSB is designated for the first group of one or more UEs.

[0210] Example 15: A method, apparatus, and non-transitory computer-readable medium according to any one of Examples 13 or 14, wherein the scheduling entity further configures the first bandwidth according to the assumed bandwidth capability of the first group of one or more UEs, and configures the second bandwidth according to the assumed broadband capability of the second group of one or more UEs.

[0211] Example 16: A method, apparatus, and non-transitory computer-readable medium according to any one of Examples 13-15, wherein the scheduling entity further configures the first control resource set to provide supplementary redundancy for system information blocks.

[0212] Example 17: A method, apparatus, and nontransitory computer-readable medium according to any one of Examples 13-16, wherein the scheduling entity further configures at least one of the first SSB or the first control resource set to be shared with one or more UEs in the second group.

[0213] Example 18: A method, apparatus, and non-transitory computer-readable medium for wireless communication. A scheduling entity transmits a Control Resource Set (SSB) including information for identifying a first control resource set for a first group of one or more UEs and information for identifying a second control resource set for a second group of one or more UEs. The scheduling entity transmits the first control resource set on a first bandwidth for the first group of one or more UEs and transmits the second control resource set on a second bandwidth for the second group of one or more UEs, the second bandwidth being wider than the first bandwidth.

[0214] Example 19: The method, apparatus, and non-transitory computer-readable medium according to Example 18, wherein the scheduling entity configures the first bandwidth according to the assumed bandwidth capabilities of the first group of one or more UEs, and configures the second bandwidth according to the assumed broadband capabilities of the second group of one or more UEs.

[0215] Example 20: A method, apparatus, and non-transitory computer-readable medium according to any one of Examples 18-19, wherein the scheduling entity further configures the first control resource set to provide supplementary redundancy for system information blocks.

[0216] Example 21: A method, apparatus, and non-transitory computer-readable medium according to any one of Examples 18-20, wherein the scheduling entity further configures the first control resource set to be shared with one or more UEs in the second group.

[0217] Example 22: A method, apparatus, and non-transitory computer-readable medium for wireless communication. A scheduling entity transmits an SSB for identifying a first SIB of one or more UEs in a first group within a shared control resource set, and information for identifying a second SIB of one or more UEs in a second group within the shared control resource set. The scheduling entity transmits the control resource set, which includes the first SIB having a first bandwidth and includes the second SIB having a second bandwidth that is wider than the first bandwidth.

[0218] Example 23: The method, apparatus, and non-transitory computer-readable medium according to Example 22, wherein the scheduling entity further configures the first bandwidth according to the assumed bandwidth capabilities of the first group of one or more UEs, and configures the second bandwidth according to the assumed broadband capabilities of the second group of one or more UEs.

[0219] Example 24: A method, apparatus, and non-transitory computer-readable medium according to any one of Examples 22 or 23, wherein the scheduling entity further configures the first control resource set to provide supplementary redundancy for the first SIB.

[0220] Example 25: A method, apparatus, and non-transitory computer-readable medium according to any one of Examples 22-24, wherein the scheduling entity further configures the first SIB to be shared with one or more UEs in the second group.

[0221] Example 26: A method, apparatus, and non-transitory computer-readable medium for wireless communication. A scheduling entity transmits an SSB configured to be shared by at least a first category of UEs and a second category of UEs. The scheduling entity configures a control resource set to have a bandwidth corresponding to the assumed bandwidth capabilities of a first group of one or more UEs, wherein the assumed bandwidth capabilities of the first category of UEs are narrower than those of the second category of UEs. The scheduling entity transmits the control resource set on said bandwidth for sharing by at least the first category of UEs and the second category of UEs.

[0222] Example 27: A method, apparatus, and non-transitory computer-readable medium for wireless communication. A scheduling entity transmits an SSB configured to be shared by at least two classes of UEs, the SSB including an index value for indicating a configuration of a control resource set. The scheduling entity transmits a first control resource set configured according to a first translation of one or more SSB fields associated with the index value; and transmits a second control resource set configured according to a second translation of one or more SSB fields associated with the index value, the second translation being different from the first translation.

[0223] Example 28: The method, apparatus, and non-transitory computer-readable medium according to Example 27, wherein the first translation associates a first resource set for the first control resource set, and wherein the second translation associates a second resource set for the second control resource set, the second resource set being offset in at least one of time or frequency.

[0224] Example 29: A method, apparatus, and non-transitory computer-readable medium according to any one of Examples 27-28, wherein the scheduling entity further transmits at least one additional control resource set, offset in frequency from the first control resource set, for a subset of the second group of one or more UEs. The scheduling entity further transmits the at least one additional control resource set for the subset of the second group of one or more UEs.

[0225] Several aspects of wireless communication networks are illustrated with reference to exemplary implementations. As will be readily apparent to those skilled in the art, the various aspects described herein can be extended to other telecommunications systems, network architectures, and communication standards.

[0226] For example, these aspects can be implemented in other systems defined by 3GPP, such as Long Term Evolution (LTE), Evolved Packet System (EPS), Universal Mobile Telecommunications System (UMTS), and / or Global System for Mobile Communications (GSM). These aspects can also be extended to systems defined by 3GPP2 (3rd Generation Partnership Project 2), such as CDMA2000 and / or Evolved Data Optimization (EV-DO). Other examples can be implemented in systems using IEEE 802.11 (Wi-Fi), IEEE 802.17 (WiMAX), IEEE 802.20, Ultra Wideband (UWB), Bluetooth, and / or other suitable systems. The actual telecommunications standards, network architecture, and / or communication standards used depend on the specific application and the overall design constraints imposed on the system.

[0227] In this disclosure, the term “exemplary” as used means “serving as an example, instance, or illustration.” Any implementation or aspect described herein as “exemplary” should not be construed as superior or advantageous to other aspects of this disclosure. Similarly, the term “aspect” does not require that all aspects of this disclosure include the features, advantages, or modes of operation discussed. The term “coupling” is used herein to refer to direct or indirect coupling between two objects. For example, if object A physically contacts object B, and object B contacts object C, objects A and C can still be considered coupled to each other, even if they are not in direct physical contact. For example, a first object can be coupled to a second object, even if the first object never physically contacts the second object. The terms “circuit” and “electronic circuit” are used broadly, and they are intended to include hardware implementations of electronic devices and conductors (whereby these electronic devices and conductors, when connected and configured, perform the functions described in this disclosure, without limitation on the type of electronic circuit) and software implementations of information and instructions (whereby these information and instructions, when executed by a processor, perform the functions described in this disclosure).

[0228] Can be Figure 1-18 One or more of the components, steps, features, and / or functions shown may be rearranged and / or combined into a single component, step, feature, or function, or embodied in several components, steps, or functions. Furthermore, additional elements, components, steps, and / or functions may be added without departing from the novel features disclosed herein. Figure 1-18 The apparatuses, devices, and / or components shown may be configured to perform one or more of the methods, features, or steps described herein. The novel algorithms described herein may also be implemented efficiently in software and / or embedded in hardware.

[0229] It should be understood that the specific order or hierarchy of steps in the methods disclosed herein is merely illustrative of exemplary processes. It should be understood that the specific order or hierarchy of steps in these methods may be rearranged based on design preferences. The appended method claims give the elements of each step in an illustrative order, but this does not imply that they are limited to the given specific order or hierarchy unless expressly stated herein.

[0230] The preceding description is provided to enable any person skilled in the art to implement the various aspects described herein. Various modifications to these aspects will be apparent to those skilled in the art, and the general principles defined herein can be applied to other aspects. Therefore, the claims are not intended to be limited to the aspects shown herein, but are given the full scope consistent with the text of the claims, wherein references to singular elements, unless expressly stated otherwise, are not intended to mean “one and only one,” but rather “one or more.” Unless expressly stated otherwise, the term “some” means one or more. The phrase “at least one” referring to a list of items means any combination of those items, including a single member. For example, “at least one of a, b, or c” is intended to cover: a; b; c; a and b; a and c; b and c; and a, b, and c. All structural and functional equivalents of the elements pervading the various aspects described in this disclosure are expressly incorporated herein by reference and are intended to be included by the claims, such structural and functional equivalents being known or to be known by those skilled in the art. Furthermore, nothing herein is intended to be offered to the public, whether or not such disclosure is expressly recited in the claims.

Claims

1. A method of wireless communication, comprising: transmitting a synchronization signal block (SSB) including information identifying a first control resource set for a first group of one or more user equipments (UEs) and information identifying a second control resource set for a second group of one or more UEs; configuring the first control resource set to provide supplemental redundancy for a system information block, wherein providing supplemental redundancy for the system information block includes repeating information representing a system information block two or more times; transmitting the first control resource set on a first bandwidth for the first group of one or more UEs; and transmitting the second control resource set on a second bandwidth for the second group of one or more UEs, the second bandwidth being wider than the first bandwidth.

2. The method of claim 1, further comprising: configuring the first bandwidth according to an assumed bandwidth capability of the first group of one or more UEs; and configuring the second bandwidth according to an assumed bandwidth capability of the second group of one or more UEs.

3. The method of claim 1, further comprising: configuring the first control resource set to be shared with the second group of one or more UEs.

4. A user equipment (UE), comprising: at least one processor; at least one transceiver; and at least one memory including instructions, wherein the at least one processor is configured to execute the instructions to cause the UE to: scan a set of frequencies for wireless network acquisition; receive, via the at least one receiver, a synchronization signal block (SSB) including information identifying a first control resource set designated for a first group of one or more UEs and further including information identifying a second control resource set designated for a second group of one or more UEs, wherein the first control resource set provides supplemental redundancy for a system information block, wherein providing supplemental redundancy for the system information block includes repeating information representing a system information block two or more times; receive, via the at least one receiver, the first control resource set based on the UE being a member of the first group of one or more UEs and obtain corresponding first system information for a wireless network; and establish a connection with the wireless network based on the system information. the SSB includes an information element indicating that the first control resource set is designated for the first group of one or more UEs. ​ ​ 5. The UE of claim 4, wherein, ​

Images