System information acquisition method for reduced capability nr devices

Abstract

A system, apparatus, method, and non-transitory computer-readable medium for reduced capability NR device system information acquisition can include a UE device caused to determine, from a control resource set (CORESET), a plurality of physical downlink control channel (PDCCH) candidates, monitor a PDCCH from the plurality of PDCCH candidates, determine reduced capability (REDCAP) scheduling information from downlink control information (DCI) received on the PDCCH, and receive REDCAP system information based on the determined REDCAP scheduling information.

Description

[0001] Cross-reference to related applications

[0002] This application claims priority to U.S. Provisional Application No. 63 / 025,284, filed May 15, 2020, which is incorporated herein by reference in its entirety. Technical Field

[0003] Various example embodiments relate to methods, apparatus, systems, and / or non-transitory computer-readable media for acquiring System Information Block Type 1 (SIB1) for Reduced Capability User Equipment. Background Technology

[0004] Currently, the fifth-generation mobile network (5G) standard, called 5G New Radio (NR), is being developed to provide communication with higher capacity, higher reliability, and lower latency than the 4G Long Term Evolution (LTE) standard. One of the anticipated goals of the 5G standard is to provide these communication capabilities to new types of user equipment (UE) devices with reduced capabilities (e.g., fewer radio antennas, reduced processing time, reduced processing power, etc.), lower device resources (e.g., reduced memory storage, reduced battery capacity, etc.), cheaper devices, physically smaller devices (e.g., smaller form factor, etc.), and completely wireless devices (e.g., devices expected to operate without human intervention over extended periods). These new types of UE devices can be referred to as NR Lightweight and / or Reduced Capability (REDCAP) devices. Some potential use cases for NR Lightweight and / or REDCAP devices include, for example, consumer Internet of Things (IoT) devices, large-scale industrial networks, smart city infrastructure, wearable devices, connected medical devices, autonomous devices, and more. These types of UE devices can operate over extended periods without human intervention (e.g., the UE device can operate without performing routine maintenance, such as replacing or recharging the battery on the device), can have reduced processing power, can have a reduced number of radio antennas and / or can be configured to use less bandwidth, can have reduced battery storage capacity due to a smaller form factor, can be integrated into machinery (e.g., heavy machinery, factory machinery, sealing equipment, etc.), can be installed / located in hazardous or hard-to-reach environments, and so on.

[0005] Therefore, the desired goal of the 5G standard is to provide these types of UE devices with the ability to determine whether a particular cell of the wireless network supports the services expected by NR Light and / or REDCAP UE devices and / or allows access to the wireless network, while using less power and / or requiring less computational complexity compared to conventional technologies.

[0006] However, the current 5G standard defines a single protocol for UE devices to obtain system information for determining the services available on one or more cells of the 5G wireless network and / or access to the 5G wireless network, regardless of whether the UE device is a standard UE device (e.g., a legacy UE device, etc.) or an NR lightweight and / or REDCAP UE device.

[0007] Therefore, there is a desired method that provides a way to obtain system information from a wireless network for acquiring REDCAP-specific system information from a cell of the wireless network, a method that consumes less power and / or requires reduced computational complexity than conventional system information acquisition techniques. Summary of the Invention

[0008] At least one example embodiment relates to a user equipment (UE) device including a memory storing computer-readable instructions and a processing circuitry system configured to execute the computer-readable instructions.

[0009] In at least one example embodiment, the UE device is configured to: determine a plurality of physical downlink control channel (PDCCH) candidates from a control resource set (CORESET), monitor the PDCCH from the plurality of PDCCH candidates, determine reduction capability (REDCAP) scheduling information from downlink control information (DCI) received on the PDCCH, and receive REDCAP system information based on the determined REDCAP scheduling information.

[0010] Some example implementations specify that a CORESET is an extended CORESET, and an extended CORESET includes one or more conventional control resources and one or more extended control resources.

[0011] Some example implementations specify that the UE device is also configured to determine whether the radio access network (RAN) node supports extended CORESET.

[0012] Some example implementations specify that the UE device is also configured to determine whether the RAN node supports extended CORESET by: receiving a Master Information Block (MIB) from the RAN node, determining whether the MIB includes REDCAP support information, and determining whether the RAN node supports extended CORESET based on the result of determining whether the MIB includes REDCAP support information.

[0013] Some example implementations specify that the UE device is also configured to determine whether the RAN node supports extended CORESET by: blindly monitoring the search space associated with extended CORESET for multiple PDCCH candidates, and determining whether the RAN node supports extended CORESET based on the successful reception of DCI on the PDCCH.

[0014] Some example implementations specify that DCI includes scheduling information corresponding to Traditional System Information Block Type 1 (SIB1) and scheduling information corresponding to REDCAP SIB1.

[0015] Some example implementations specify that the DCI is scrambled using the REDCAP-specific Radio Network Temporary Identifier (RNTI), and the DCI includes scheduling information corresponding to REDCAP SIB1.

[0016] Some example implementations specify that multiple PDCCH candidates include control channel elements (CCEs) from one or more traditional control resources and one or more extended control resources.

[0017] Some example implementations specify that one or more conventional control resources and one or more extended control resources are continuous in the time domain or frequency domain.

[0018] Some example implementations specify that one or more traditional control resources and one or more extended control resources are located in different time slots.

[0019] Some example implementations specify that multiple PDCCH candidates include CCEs from extended control resources.

[0020] Some example implementations specify that the extended CORESET includes a joint control resource, which includes an extended control resource attached to a traditional control resource, and multiple PDCCH candidates are mapped to the joint control resource of the extended CORESET using a hash function.

[0021] Some example implementations specify that the UE device is also enabled to receive modified legacy SIB1 messages, which include legacy system information and REDCAP system information.

[0022] Some example implementations specify that the UE device is also enabled to receive REDCAP-specific SIB1 messages, which include REDCAP system information.

[0023] At least one example embodiment relates to a user equipment (UE) device including a memory storing computer-readable instructions and a processing circuitry system configured to execute the computer-readable instructions.

[0024] In at least one example embodiment, the UE device is configured to: determine whether a radio access network (RAN) node supports an extended control resource set (CORESET), determine a plurality of physical downlink control channel (PDCCH) candidates from the CORESET based on the result of determining whether the RAN node supports the extended CORESET, monitor the PDCCH from the plurality of PDCCH candidates, and decode downlink control information (DCI) received on the monitored PDCCH.

[0025] Some example implementations specify that the UE device is also configured to: determine Reduced Capability (REDCAP) scheduling information from the decoded DCI, and receive REDCAP system information from the RAN node based on the determined REDCAP scheduling information.

[0026] Some example embodiments specify that the UE device is also configured to receive REDCAP System Information Block Type 1 (SIB1) messages, which include REDCAP system information.

[0027] Some example implementations specify that the DCI is scrambled using the REDCAP-specific Radio Network Temporary Identifier (RNTI), and the DCI includes scheduling information corresponding to REDCAP SIB1.

[0028] Some example implementations specify that multiple PDCCH candidates include control channel elements (CCEs) from one or more traditional control resources and one or more extended control resources.

[0029] Some example implementations specify that one or more conventional control resources and one or more extended control resources are continuous in the time domain or frequency domain.

[0030] Some example implementations specify that one or more traditional control resources and one or more extended control resources are located in different time slots.

[0031] At least one example embodiment relates to a method of operating a user equipment (UE) device.

[0032] In at least one example embodiment, the method includes: using a processing circuitry system to determine a plurality of physical downlink control channel (PDCCH) candidates from a control resource set (CORESET); using a processing circuitry system to monitor PDCCHs from the plurality of PDCCH candidates; using a processing circuitry system to determine reduction capability (REDCAP) scheduling information from downlink control information (DCI) received on the PDCCHs; and using a processing circuitry system to receive REDCAP system information based on the determined REDCAP scheduling information.

[0033] Some example implementations specify that a CORESET is an extended CORESET, and an extended CORESET includes one or more conventional control resources and one or more extended control resources.

[0034] Some example embodiments specify that the method also includes using a processing circuitry system to determine whether a radio access network (RAN) node supports extended CORESET.

[0035] Some example implementations specify that determining whether a RAN node supports extended CORESET includes: receiving a Master Information Block (MIB) from the RAN node, determining whether the MIB includes REDCAP support information, and determining whether the RAN node supports extended CORESET based on the result of determining whether the MIB includes REDCAP support information.

[0036] Some example implementations specify that determining whether a RAN node supports extended CORESET includes: blindly monitoring the search space associated with extended CORESET for multiple PDCCH candidate nodes, and determining whether a RAN node supports extended CORESET based on successfully receiving DCI on the PDCCH.

[0037] At least one example embodiment relates to a user equipment (UE) device.

[0038] In at least one example embodiment, the UE device includes components for performing the following operations: determining a plurality of physical downlink control channel (PDCCH) candidates from a control resource set (CORESET), monitoring PDCCHs from the plurality of PDCCH candidates, determining reduction capability (REDCAP) scheduling information from downlink control information (DCI) received on the PDCCHs, and receiving REDCAP system information based on the determined REDCAP scheduling information.

[0039] Some example implementations specify that a CORESET is an extended CORESET, and an extended CORESET includes one or more conventional control resources and one or more extended control resources.

[0040] Some example embodiments specify that the UE device also includes components for determining whether a radio access network (RAN) node supports extended CORESET.

[0041] Some example embodiments specify that the UE device also includes components for performing the following operations: receiving a Master Information Block (MIB) from the RAN node, determining whether the MIB includes REDCAP support information, and determining whether the RAN node supports extended CORESET based on the result of determining whether the MIB includes REDCAP support information.

[0042] Some example embodiments specify that the UE device also includes components for determining whether the RAN node supports extended CORESET to perform the following operations: blindly monitoring the search space associated with extended CORESET for multiple PDCCH candidates, and determining whether the RAN node supports extended CORESET based on the successful reception of DCI on the PDCCH.

[0043] Some example implementations specify that DCI includes scheduling information corresponding to Traditional System Information Block Type 1 (SIB1) and scheduling information corresponding to REDCAP SIB1.

[0044] Some example implementations specify that the DCI is scrambled using the REDCAP-specific Radio Network Temporary Identifier (RNTI), and the DCI includes scheduling information corresponding to REDCAP SIB1.

[0045] Some example implementations specify that multiple PDCCH candidates include control channel elements (CCEs) from one or more traditional control resources and one or more extended control resources.

[0046] Some example implementations specify that one or more conventional control resources and one or more extended control resources are continuous in the time domain or frequency domain.

[0047] Some example implementations specify that one or more traditional control resources and one or more extended control resources are located in different time slots.

[0048] Some example implementations specify that multiple PDCCH candidates include CCEs from extended control resources.

[0049] Some example implementations specify that the extended CORESET includes a joint control resource, which includes an extended control resource attached to a traditional control resource, and multiple PDCCH candidates are mapped to the joint control resource of the extended CORESET using a hash function.

[0050] Some example embodiments specify that the UE device also includes a component for receiving modified legacy SIB1 messages, which include legacy system information and REDCAP system information.

[0051] Some example embodiments specify that the UE device also includes a component for receiving REDCAP-specific SIB1 messages, which include REDCAP system information.

[0052] At least one example embodiment relates to a user equipment (UE) device.

[0053] In at least one example embodiment, the UE device includes components for performing the following operations: determining whether a radio access network (RAN) node supports an extended control resource set (CORESET); determining a plurality of physical downlink control channel (PDCCH) candidates from the CORESET based on the result of determining whether the RAN node supports the extended CORESET; monitoring the PDCCH from the plurality of PDCCH candidates; and decoding downlink control information (DCI) received on the monitored PDCCH.

[0054] Some example embodiments specify that the UE device also includes components for performing the following operations: determining Reduced Capability (REDCAP) scheduling information from the decoded DCI, and receiving REDCAP system information from the RAN node based on the determined REDCAP scheduling information.

[0055] Some example embodiments specify that the UE device also includes a component for receiving REDCAP System Information Block Type 1 (SIB1) messages, which include REDCAP system information.

[0056] Some example implementations specify that the DCI is scrambled using the REDCAP-specific Radio Network Temporary Identifier (RNTI), and the DCI includes scheduling information corresponding to REDCAP SIB1.

[0057] Some example implementations specify that multiple PDCCH candidates include control channel elements (CCEs) from one or more traditional control resources and one or more extended control resources.

[0058] Some example implementations specify that one or more conventional control resources and one or more extended control resources are continuous in the time domain or frequency domain.

[0059] Some example implementations specify that one or more traditional control resources and one or more extended control resources are located in different time slots. Attached Figure Description

[0060] The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate one or more exemplary embodiments and explain these exemplary embodiments together with the specification. In the drawings:

[0061] Figure 1 A wireless communication system according to at least one example embodiment is shown;

[0062] Figure 2 A block diagram of an example RAN node according to at least one example embodiment is shown;

[0063] Figure 3 A block diagram of a UE device according to at least one example embodiment is shown;

[0064] Figure 4 An example transmission flowchart between a UE device and one or more RAN nodes according to some example embodiments is shown; and

[0065] Figures 5 to 7 An example of extended CORESET information is shown according to some example embodiments. Detailed Implementation

[0066] Various exemplary embodiments will now be described more fully with reference to the accompanying drawings, some of which illustrate exemplary embodiments.

[0067] Detailed exemplary embodiments are disclosed herein. However, the specific structural and functional details disclosed herein are merely representative for the purpose of describing exemplary embodiments. Furthermore, exemplary embodiments may be embodied in many alternative forms and should not be construed as being limited to the exemplary embodiments set forth herein.

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

[0069] It is understandable that when an element is described as "connected" or "coupled" to another element, it can be directly connected or coupled to the other element, or there may be intermediate elements. Conversely, when an element is described as "directly connected" or "directly coupled" to another element, there are no intermediate elements. Other terms used to describe the relationship between elements should be interpreted in a similar manner (e.g., "between" vs. "directly between", "adjacent to" vs. "directly adjacent to", etc.).

[0070] The terminology used herein is for the purpose of describing particular embodiments only and is not intended to limit the exemplary embodiments. As used herein, the singular forms “a,” “an,” and “the” also include the plural forms, unless the context clearly specifies otherwise. It will be further understood that the terms “comprising,” “including,” “including,” and / or “containing” as used herein specify the presence of the stated feature, integral, step, operation, element, and / or component, but do not exclude the presence or addition of one or more other features, integrals, steps, operations, elements, components, and / or groups thereof.

[0071] It should also be noted that in some alternative implementations, functions / actions may not occur in the order shown in the diagram. For example, depending on the functions / actions involved, two diagrams shown consecutively may actually be executed substantially simultaneously, or sometimes in reverse order.

[0072] Specific details are set forth in the following description to provide a thorough understanding of the exemplary embodiments. However, those skilled in the art will understand that the exemplary embodiments can be practiced without these specific details. For example, systems may be shown as block diagrams so as not to obscure the exemplary embodiments with unnecessary details. In other instances, well-known processes, structures, and techniques may be shown without unnecessary details to avoid confusing the exemplary embodiments.

[0073] Furthermore, it should be noted that the example embodiments can be described as processes shown in flowcharts, diagrams, data flow diagrams, structure diagrams, or block diagrams. Although flowcharts can describe operations as sequential processes, many operations can be performed in parallel, concurrently, or simultaneously. Moreover, the order of operations can be rearranged. A process may terminate upon completion of its operations, but it may also have additional steps not included in the diagram. A process can correspond to a method, function, procedure, subroutine, subroutine, etc. When a process corresponds to a function, its termination can correspond to the function returning to the calling function or the main function.

[0074] Furthermore, as disclosed herein, the term "memory" can refer to one or more devices for storing data, including random access memory (RAM), magnetic RAM, core memory, and / or other machine-readable media for storing information. The term "storage medium" can refer to one or more devices for storing data, including read-only memory (ROM), random access memory (RAM), magnetic RAM, core memory, disk storage media, optical storage media, flash memory devices, and / or other machine-readable media for storing information. The term "computer-readable medium" can include, but is not limited to, portable or fixed storage devices, optical storage devices, wireless channels, and various other media capable of storing, containing, or carrying instructions and / or data.

[0075] Furthermore, the example embodiments can be implemented by combining hardware circuitry and / or software, firmware, middleware, microcode, hardware description languages, etc., with hardware (e.g., software executed by hardware). When implemented as software, firmware, middleware, or microcode, program code or code segments for performing the desired task can be stored in a machine or computer-readable medium (such as a non-transitory computer storage medium) and loaded onto one or more processors to perform the desired task.

[0076] A code segment can represent a procedure, function, subroutine, program, routine, subroutine, module, software package, class, or any combination of instructions, data structures, or program statements. A code segment can be coupled to another code segment or hardware circuit by passing and / or receiving information, data, arguments, parameters, or memory contents. Information, arguments, parameters, data, etc., can be passed, forwarded, or transmitted via any appropriate means, including memory sharing, message passing, token passing, network transmission, etc.

[0077] In this application, the terms "circuit system" and / or "hardware circuit system" may refer to one or more or all of the following: (a) a hardware circuit implementation only (such as an implementation only in analog and / or digital circuit systems); (b) a combination of hardware circuits and software, such as (if applicable): (i) a combination of (multiple) analog and / or digital hardware circuits with software / firmware, and (ii) any portion of (multiple) hardware processors (including digital signal processors), software, and memory having software, which work together to enable a device (such as a mobile phone or server) to perform various functions; and (c) (multiple) hardware circuits and / or (multiple) processors, such as (multiple) microprocessors or portions thereof, which require software (e.g., firmware) to operate, but may be absent when the software is not required to operate. For example, a circuit system may more specifically include, but is not limited to, a central processing unit (CPU), an arithmetic logic unit (ALU), a digital signal processor, a microcomputer, a field-programmable gate array (FPGA), a system-on-a-chip (SoC), a programmable logic unit, a microprocessor, an application-specific integrated circuit (ASIC), etc.

[0078] This definition of "circuit system" applies to all uses of the term in this application, including in any claim. As another example, as used herein, the term "circuit system" also covers only the implementation of hardware circuitry or a processor (or processors) or a portion of hardware circuitry or a microprocessor and its accompanying software and / or firmware. For example, if applicable to a particular claim element, the term "circuit system" also covers baseband integrated circuits or processor integrated circuits for mobile devices, or similar integrated circuits in servers, cellular network devices, or other computing or network devices.

[0079] At least one example embodiment relates to a method for obtaining reduced capability-specific system information by a reduced capability UE device. While various example embodiments of this disclosure are discussed in conjunction with the 5G wireless communication standard for clarity and convenience, the example embodiments are not limited thereto, and those skilled in the art will recognize that the example embodiments can be applied to other wireless communication standards, such as the 4G standard, the Wi-Fi standard, future 6G standards, future 7G standards, etc.

[0080] Figure 1 A wireless communication system according to at least one example embodiment is shown. For example... Figure 1 As shown, the wireless communication system includes a core network 100 and a data network 105, at least one radio access network (RAN) node 110, a cell service area 120 corresponding to the RAN node 110, and at least one user equipment (UE) device (UE or UE equipment) 130 operating within the cell coverage area 120. However, the example embodiment is not limited thereto, and the example embodiment may include more or fewer components. For example, the wireless communication system may include multiple UE devices, multiple RAN nodes, etc.

[0081] RAN node 110 and / or UE device 130 can be connected via a wireless network, such as a cellular radio access network (e.g., a 3G radio access network, a 4G Long Term Evolution (LTE) network, a 5G New Radio (e.g., 5G) wireless network, a 6G network, a 7G network, a WiFi network, etc.). The wireless network may include core network 100 and / or data network 105. RAN node 110 can connect to other RAN nodes (not shown) and core network 100 or data network 105 via wired and / or wireless networks. Core network 100 and data network 105 can be connected to each other via wired and / or wireless networks. Data network 105 can refer to the Internet, intranet, wide area network, etc.

[0082] UE device 130 may be a device with reduced processing power, limited battery life, reduced form factor, etc., and may be a Reduced Capability (REDCAP) and / or NR lightweight device, but the example embodiments are not limited thereto. For example, UE device 130 may be a conventional UE device (e.g., a fully capable UE device, etc.), but may be configured to operate according to the REDCAP-specific methods discussed herein to achieve benefits such as lower power consumption, reduced computing resource usage for decoding system information, and / or reduced network usage provided by the example embodiments. According to at least one example embodiment, UE device 130 may be any of, but is not limited to, mobile devices, tablets, laptops, wearable devices, Internet of Things (IoT) devices, sensors (e.g., thermometers, humidity sensors, pressure sensors, motion sensors, accelerometers, etc.), actuators, robotic devices, robots, drones, connected medical devices, eHealth devices, smart city-related devices, security cameras, autonomous devices (e.g., autonomous vehicles, etc.), desktop computers, and / or any other type of fixed or portable device capable of operating according to 5G NR communication standards and / or other wireless communication standards.

[0083] The wireless communication system also includes at least one RAN node (e.g., a base station, a wireless access point, etc.), such as RAN node 110. RAN node 110 can operate according to a basic cellular and / or radio access technology (RAT) such as 5G NR, LTE, etc. For example, the RAN node can be a 5G gNB node, an LTE eNB node, or an LTE ng-eNB node, etc., but the example embodiment is not limited thereto. RAN node 110 can provide wireless network services to one or more UE devices within a cell service area (e.g., cell service area 120 surrounding RAN node 110) (e.g., broadcast area, service area, coverage area, etc.) surrounding the physical location of the RAN node. For example, UE device 130 is located within cell service area 120 and can connect to RAN node 110, receive broadcast messages from RAN node 110, receive paging messages from RAN node 110, receive / transmit signaling messages from / to RAN node 110, and / or access the wireless network through RAN node 110, etc., but the example embodiment is not limited thereto.

[0084] Furthermore, the RAN node and / or the corresponding cell service area can be referred to as a cell of the wireless network, and the wireless network can be segmented and / or defined as including one or more system areas having one or more cells.

[0085] RAN node 110 can connect to at least one core network element (not shown) residing on core network 100, such as core network equipment, core network server, access point, switch, router, node, etc., but the example embodiment is not limited thereto. Core network 100 can provide network functions such as Access and Mobility Management Function (AMF), Session Management Function (SMF), Policy Control Function (PCF), Unified Data Management (UDM), User Plane Function (UPF), Authentication Server Function (AUSF), Application Function (AF), and / or Network Slice Selection Function (NSSF), etc., but the example embodiment is not limited thereto.

[0086] Although some components of the wireless communication network are shown as Figure 1 As part of a wireless communication system, the example embodiments are not limited thereto, and the wireless communication network may include, in addition to Figure 1 Components other than those shown, which are desirable, necessary and / or beneficial for the operation of the underlying network within the wireless communication system 100, such as access points, switches, routers, nodes, servers, gateways, etc.

[0087] Figure 2 A block diagram of an example RAN node according to at least one example embodiment is shown. Figure 2 RAN node 2000 can correspond to Figure 1The RAN network node 110 is an example, but the example embodiment is not limited thereto.

[0088] refer to Figure 2 RAN node 2000 may include processing circuitry, such as at least one processor 2100, a communication bus 2200, a memory 2300, at least one core network interface 2400, and / or at least one radio access network (RAN) interface 2500, but the example embodiment is not limited thereto. For example, the core network interface 2400 and the RAN interface 2500 may be combined into a single network interface, or RAN node 2000 may include multiple RAN interfaces, multiple core network interfaces, and / or combinations thereof. Memory 2300 may include various special-purpose program code, including computer-executable instructions that can cause RAN node 2000 to perform one or more methods of the example embodiment.

[0089] In at least one example embodiment, the processing circuitry may include at least one processor (and / or processor core, distributed processor, networking processor, etc.), such as at least one processor 2100, which may be configured to control one or more elements of the RAN node 2000, thereby causing the RAN node 2000 to perform various operations. The processing circuitry (e.g., at least one processor 2100, etc.) is configured to perform processing by retrieving program code (e.g., computer-readable instructions) and data from memory 2300 for processing, thereby performing dedicated control and functions for the entire RAN node 2000. Once the dedicated program instructions are loaded into, for example, at least one processor 2100, the at least one processor 2100 executes the dedicated program instructions, thereby transforming at least one processor 2100 into a dedicated processor.

[0090] In at least one example embodiment, memory 2300 may be a non-transitory computer-readable storage medium and may include random access memory (RAM), read-only memory (ROM), and / or permanent mass storage devices, such as disk drives or solid-state drives. Stored in memory 2300 is data related to the operation of RAN node 2000 (such as in conjunction with...). Figures 4 to 7 The discussed methods, at least one core network interface 2400 and / or at least one RAN interface 2500, and related program code (i.e., computer-readable instructions). Such software elements can be loaded using a driver mechanism (not shown) connected to the RAN node 2000 or via at least one core network interface 2400 and / or at least one RAN interface 2500 from a non-transitory computer-readable storage medium independent of memory 2300.

[0091] In at least one example embodiment, the communication bus 2200 enables communication and data transfer that can be performed between elements of the RAN node 2000. The bus 2200 can be implemented using a high-speed serial bus, a parallel bus, and / or any other suitable communication technology. According to some example embodiments, the RAN node 2000 may include multiple communication buses (not shown).

[0092] RAN node 2000 can operate as, for example, a 4G RAN node, a 5G RAN node, a 6G RAN node, a 7G RAN node, etc., and can be configured to schedule resource blocks for UE devices connected to the RAN node.

[0093] For example, RAN node 2000 can allocate time-frequency resources (e.g., resource blocks with time and frequency dimensions) of a carrier based on operations in the time domain (e.g., time division duplex) and frequency domain (e.g., frequency division duplex). In the time domain context, RAN node 2000 will allocate a carrier (or a sub-band of a carrier) to one or more UEs (e.g., UE 130, etc.) connected to RAN node 2000 during a specified upload (e.g., uplink) time period and a specified download (e.g., downlink) time period. When multiple UEs are connected to RAN node 2000, the carrier is shared in time, such that each UE is scheduled by RAN node 2000, and RAN node 2000 allocates its own uplink time and / or downlink time for each UE. In the frequency domain context, RAN node 2000 will allocate separate frequency sub-bands of a carrier to UEs simultaneously served by RAN node 2000 for uplink and / or downlink transmissions. Data transmission between a UE and RAN node 2000 can occur based on radio frames in both the time and frequency domain contexts. The smallest resource unit (i.e., resource block) allocated and / or assigned by RAN node 2000 to a specific UE device corresponds to a specific downlink / uplink time slot (e.g., an OFDM symbol, a time slot, a subframe, etc.) and / or a specific downlink / uplink subband (e.g., twelve adjacent subcarriers, etc.).

[0094] For clarity and consistency, the example embodiments will be described as using the time domain, but the example embodiments are not limited thereto and may operate in the frequency domain.

[0095] Furthermore, according to at least one example embodiment, RAN node 2000 can transmit system information to one or more UE devices located within the cell service area of ​​RAN node 2000. This system information can be used by one or more UE devices to access the wireless network. For example, RAN node 2000 can periodically broadcast synchronization signal blocks (SSBs), physical broadcast channel (PBCH) blocks, and master information blocks (MIBs) to one or more UE devices located within a corresponding cell service area (e.g., cell service area 120). The SSB, PBCH, and MIB blocks may include information about system parameters used for cell discovery, establishing frame synchronization, information for implementing system information reception, etc. The UE devices can then use the information included in the SSB, PBCH, and / or MIB to identify the subcarrier spacing used by RAN node 2000 for various control and / or data channels, such as information related to the physical downlink control channel (PDCCH), information related to the physical uplink control channel (PUCCH), information related to the physical downlink shared channel (PDSCH), etc.

[0096] In addition, the MIB may include information such as PDCCH scheduling SIB1 (which defines the “search space 0” that the UE device should monitor to determine the timing of PDCCH monitoring) and information indicating the initial control resource set (CORESET), such as “CORESET 0”, which is a set of resources associated with at least search index 0 for decoding downlink control information (DCI) transmitted to the UE device via PDCCH.

[0097] The DCI may include information about frequency domain resources and / or time domain resources (e.g., resource block units) allocated to the UE device for data channel scheduling, modulation and coding schemes, etc. More specifically, the DCI (e.g., SIB1 DCI, DCI in format 1_0, etc.) may include information related to the scheduling of System Information Blocks (SIBs), including the scheduling of the initial SIB type 1 (SIB1) and / or the scheduling of subsequent SIBs (e.g., SIB2, SIB3, SIB4, etc.). The SIB may include information used by the UE device to access the wireless network, including system information, network parameters, etc.

[0098] However, the use of legacy SIBs (including legacy SIB1) can be inefficient when used with and / or incompatible with REDCAP UE devices. For example, legacy SIB1 may be relatively large, and therefore REDCAP UE devices with low processing power and / or low memory capacity may have difficulty decoding legacy SIB1 and / or may be unable to decode SIB1 within the time constraints under 5G RAT. Furthermore, transmitting SIB1 to REDCAP UE devices more frequently, transmitting SIB1 over narrower bandwidths, or using SIB1 with a higher code rate may be beneficial and / or advantageous compared to legacy SIB1.

[0099] Therefore, RAN node 2000 can be configured to transmit a new REDCAP-specific SIB1 (e.g., SIB-1REDCAP) at a different time and / or frequency than the conventional SIB1 for use by REDCAP UE devices. According to some example embodiments, the REDCAP-specific SIB1 may have a smaller data size than the conventional SIB1 and / or a different SIB1 format, and therefore, conventional UE devices not configured to operate in REDCAP and / or NR light mode may not be able to decode and / or use the REDCAP-specific SIB1. Furthermore, according to some example embodiments, REDCAP SIB1 scheduling information may be received based on a REDCAP-specific DCI scrambled with a REDCAP-specific radio network temporary identifier (RNTI) (which the conventional UE device may not decode), and therefore, the conventional UE device may not receive the REDCAP-specific SIB1. Additionally, according to some example embodiments, the conventional SIB1 may be modified to include REDCAP-related system information and scheduled using either the conventional DCI or the REDCAP-specific DCI, but the example embodiments are not limited to this.

[0100] Furthermore, to support REDCAP-specific SIB1 and / or modified SIB1, RAN node 2000 can be configured to transmit modified DCIs (e.g., modified conventional SIB1 DCIs, etc.), which can be modified to support the scheduling of new REDCAP-specific SIB1s and / or transmit new REDCAP-specific DCIs. Additionally, RAN node 2000 can be configured to transmit modified CORESETs (e.g., modified conventional CORESETs, extended CORESEs, REDCAP-specific CORESETs, etc.), which include information related to the modified and / or extended search space to accommodate REDCAP DCIs. An extended CORESET can include two different CORESETs, or can include one CORESET and an extension. For example, an extended CORESET can include a first CORESET and a second CORESET. In another example, an extended CORESET can include an extension of the first CORESET and the first CORESE (i.e., additional time-frequency resources for control).

[0101] According to some example embodiments, the REDCAP specific system information transmission method will combine Figures 4 to 7 Further detailed discussion.

[0102] RAN node 2000 may also include at least one core network interface 2400 and / or at least one RAN interface 2500, etc. At least one radio network interface 2500 may include an associated radio unit (not shown) and may be used to transmit radio signals (such as 4G LTE radio signals, 5G NR radio signals, 6G radio signals, 7G radio signals, etc.) to at least one UE device, such as UE 130, according to radio access technologies. According to some example embodiments, RAN interface 2500 may be a single antenna or may be multiple antennas, etc.

[0103] RAN node 2000 can communicate with the core network of a wireless communication network (e.g., backend network, backhaul network, backbone network, data network, etc.) via core network interface 2400. Core network interface 2400 can be a wired and / or wireless network interface, and enables RAN node 2000 to send and / or transmit data to and from network devices on the backend network, such as core network gateways (not shown), data networks (not shown), such as the Internet, intranets, wide area networks, telephone networks, VoIP networks, etc.

[0104] Although Figure 2An example embodiment of RAN node 2000 is depicted, but the RAN node is not limited thereto and may include additional and / or alternative architectures that may be suitable for the purposes demonstrated. For example, the functionality of RAN node 2000 may be divided into multiple physical, logical and / or virtual network elements, such as centralized units (CUs), distributed units (DUs) and / or radio units (RUs), but the example embodiment is not limited thereto.

[0105] Figure 3 A block diagram of an example UE device according to at least one example embodiment is shown. Figure 3 Example UE device 3000 can correspond to Figure 1 The UE device 130, however, is not limited to this example embodiment. According to at least one example embodiment, Figure 3 The UE device 3000 may be an NR Light and / or REDCAP UE device, or a conventional UE device configured to operate using NR Light and / or REDCAP-specific system information, but the example embodiments are not limited thereto. Furthermore, for clarity and convenience, the term "REDCAP UE device" will be used to refer to a REDCAP device, an NR Light device, and / or a conventional UE device configured to operate according to the methods of one or more example embodiments described herein.

[0106] refer to Figure 3 UE 3000 may include a processing circuitry system, such as at least one processor 3100, a communication bus 3200, a memory 3300, at least one wireless antenna 3400, at least one position sensor 3500, at least one input / output (I / O) device 3600 (e.g., keyboard, touchscreen, mouse, microphone, camera, speaker, etc.), and / or a display panel 3700 (e.g., monitor, touchscreen, etc.), but the example embodiment is not limited thereto. However, the example embodiment is not limited thereto, and UE 3000 may include more or fewer components. For example, UE 3000 may also include a battery, one or more additional sensors (e.g., thermometer, humidity sensor, pressure sensor, motion sensor, accelerometer, etc.), actuators, etc. Furthermore, the position sensor 3500, display panel 3700, and / or I / O device 3600 of UE 3000 may be optional.

[0107] In at least one example embodiment, the processing circuitry may include at least one processor (and / or processor core, distributed processor, networking processor, etc.), such as at least one processor 3100, which may be configured to control one or more elements of the UE 3000, thereby causing the UE 3000 to perform various operations. The processing circuitry (e.g., at least one processor 3100, etc.) is configured to perform processing by retrieving program code (e.g., computer-readable instructions) and data from memory 3300 for processing, thereby performing dedicated control and functions of the entire UE 3000. Once the dedicated program instructions are loaded into the processing circuitry (e.g., at least one processor 3100, etc.), the at least one processor 3100 executes the dedicated program instructions, thereby turning at least one memory 3100 into a dedicated processor.

[0108] In at least one example embodiment, the memory 3300 may be a non-transitory computer-readable storage medium and may include random access memory (RAM), read-only memory (ROM), and / or permanent mass storage devices, such as disk drives or solid-state drives. Stored in the memory 3300 is data related to the operation of the UE 3000 (such as in conjunction with...). Figures 4 to 7 The discussed methods, program code (i.e., computer-readable instructions) related to the wireless antenna 3400 and / or position sensor 3500, etc. Such software elements can be loaded using a driving mechanism (not shown) connected to the UE 3000 or via the wireless antenna 3400 from a non-transitory computer-readable storage medium independent of the memory 3300. Furthermore, the memory 3300 may store network configuration information, such as system information for communicating with at least one RAN node (e.g., RAN node 120, etc.) accessing the wireless network, but the example embodiments are not limited thereto.

[0109] For example, according to at least one example embodiment, UE 3000 can synchronize with the RAN node (e.g., acquire synchronization, etc.) based on information included in the SSB, MIB, and / or PBCH received from the RAN node. According to at least one example embodiment, UE 3000 can determine whether the RAN node supports a REDCAP UE device based on at least one REDCAP support information included in the MIB (such as at least one REDCAP support indicator bit in the MIB), and accordingly receive an extended CORESET 0 configured to support a REDCAP UE device (e.g., REDCAP CORESET 0, etc.). Furthermore, according to other example embodiments, UE 3000 can automatically assume that the RAN node supports a REDCAP UE device without relying on the REDCAP support information in the MIB (and / or the MIB transmitted by the RAN node may omit REDCAP support information, etc.), and can blindly search and decode the PDCCH in the extended CORESET 0. The extended CORESET 0 will combine... Figures 4 to 7 Let's discuss this in more detail.

[0110] UE 3000 may further determine a search space 0 for detecting PDCCHs associated with information included in Extended CORESET 0 and / or MIB. For example, UE 3000 may determine PDCCH candidates to be monitored in search space 0 associated with Extended CORESET 0 and / or MIB. UE 3000 may then detect the PDCCH assigned to and / or associated with UE 3000 from among multiple PDCCH candidates within the search space associated with Extended CORESET 0, and may then receive DCI from the detected PDCCH. According to at least one example embodiment, the DCI may be a REDCAP-specific DCI that has been masked and / or scrambled using a REDCAP-specific Radio Network Temporary Identifier (RNTI) and includes REDCAP UE device-specific DCI information. According to some example embodiments, in addition to conventional DCI, the RAN node may also transmit REDCAP-specific DCI. REDCAP-specific DCI may have the same bit length as conventional DCI, but is not limited to this, and may, for example, be smaller than conventional DCI, etc. Furthermore, the REDCAP-specific DCI may include REDCAP UE-specific information, such as REDCAP SIB1 scheduling information, time slot aggregation information corresponding to the REDCAP-specific SIB1, etc., and / or the resource allocation for the REDCAP-specific DCI may be more compact than that of the conventional DCI, which may therefore result in the REDCAP-specific DCI format being smaller in size than the conventional DCI format. According to at least one other example embodiment, the DCI may be a modified version of the conventional DCI (e.g., a modified DCI, etc.), wherein the expected (and / or predefined) number of reserved bits of the conventional DCI (e.g., within the conventional DCI, using 15 bits reserved for HARQ-ACK, HARQ ID, etc.) can be used to provide scheduling information (e.g., REDCAP SIB1 scheduling information, etc.) for SIB messages (such as SIB1, etc.) associated with the REDCAP UE device. The modified DCI may have the same bit length as the conventional DCI, or may be larger than the conventional DCI, etc., but the example embodiments are not limited thereto.

[0111] According to some example embodiments, the UE 3000 can also be configured to receive REDCAP SIB1 messages and / or modified SIB1 messages from the RAN node based on the SIB1 scheduling information (e.g., REDCAP SIB1 scheduling information) included in the REDCAP-specific DCI and / or the modified DCI, and to access the wireless network based on the system information included in the SIB1 messages.

[0112] In at least one example embodiment, the communication bus 3200 enables communication and data transfer between components of the UE 3000. The bus 3200 can be implemented using a high-speed serial bus, a parallel bus, and / or any other suitable communication technology. According to some example embodiments, the UE 3000 may include multiple communication buses (not shown).

[0113] UE 3000 may also include at least one wireless antenna 3400. The wireless antenna 3400 may include an associated radio unit (not shown) and may be used to transmit wireless signals according to at least one desired wireless access technology, such as 4G LTE, 5G NR, future 6G communication protocols, future 7G communication protocols, Wi-Fi, etc. According to some example embodiments, the wireless antenna 3400 may be a single antenna or may be multiple antennas, etc.

[0114] UE 3000 may also include at least one position sensor 3500 for calculating the absolute and / or relative position of UE 3000. The at least one position sensor 3500 may be a GNSS sensor (such as a GPS sensor, GLONASS sensor, Galileo sensor, BeiDou sensor, etc.) and an inertial motion sensor (such as a gyroscope, accelerometer, altimeter, etc.). Furthermore, the position sensor 3500 and / or processor 3100 may also use cellular network-based positioning services, such as cellular network positioning services (e.g., core network location management function (LMF) service), assisted GPS (A-GPS) functions, etc., to determine the current position of UE 3000. However, the example embodiment is not limited thereto, and at least one position sensor 3500 may be omitted from UE 3000.

[0115] Although Figure 3 An example embodiment of UE 3000 is depicted, but the UE device is not limited thereto and may include additional and / or alternative architectures that may be suitable for the purposes shown.

[0116] Figure 4 A transmission flowchart between at least one UE device and at least one RAN node according to some example embodiments is shown.

[0117] Now for reference Figure 4 In at least one example embodiment, the UE device (such as UE device 130) may be a REDCAP UE device, and / or a conventional UE device may be configured to operate as a REDCAP UE device, and the RAN node (such as RAN node 110) may be a RAN node that supports REDCAP SIB1 messages, but the example embodiment is not limited thereto.

[0118] In operation S4010, RAN node 110 may broadcast and / or transmit SSB and MIB messages to REDCAP UE 130, but is not limited thereto. UE device 130 may then decode and / or read the received SSB and MIB messages. In at least one example embodiment, in operation S4020, UE device 130 may determine whether RAN node 110 supports extended CORESET (e.g., REDCAP CORESET, etc.) and / or REDCAP SIB1 messages based on REDCAP support information and / or REDCAP support indicator bits included in the MIB, but the example embodiment is not limited thereto.

[0119] In operation S4030, UE device 130 can determine extended CORESET 0 (e.g., traditional CORESET 0 and REDCAP extensions to CORESET, etc.) and the associated search space, such as search space 0, from the MIB and / or the result of determining whether RAN node 110 supports extended CORESET and / or REDCAP SIB1 messages. For example, UE device 130 can determine PDDCH candidates (e.g., through which control channel elements of PDDCH can be transmitted from RAN node 110) based on the determined extended CORESET 0, etc.

[0120] Furthermore, in operation S4030, the UE device 130 decodes the determined CORESET 0 based on the result of determining whether the RAN node 110 supports extended CORESET and / or REDCAP SIB1 messages. More specifically, if the UE device 130 determines that the RAN node 110 supports extended CORESET and / or REDCAP SIB1 messages, the UE device 130 can use REDCAP-related aggregation levels to decode extended CORESET 0 and determine REDCAP UE device PDCCH candidates. For example, the UE device 130 can use aggregation levels 4, 8, and / or 16 to decode PDCCH candidates from conventional CORESET 0, and can use REDCAP-related aggregation level 24 to decode PDCCH candidates from REDCAP extensions to CORESET, but the example embodiment is not limited thereto. In other example embodiments, the UE device 130 can use REDCAP-related aggregation levels 4, 8, and / or 24 to decode PDCCH candidates from the search space, etc. This will be combined with... Figures 5 to 7 Further details on expanding CORESET.

[0121] In at least one other example embodiment, in operation S4030, UE device 130 may assume that CORESET is an extended CORESE by assuming that the determined CORESET 0 includes the REDCAP extension, and then may monitor (e.g., blind search, blind monitoring, etc.) the search space 0 for the PDCCH candidate corresponding to the extended CORESET 0.

[0122] Once extended CORESET 0 is decoded, in operation S4040, UE device 130 can detect the PDCCH to be used with RAN node 110 from a plurality of determined PDCCH candidates and can receive REDCAP-specific DCI. REDCAP-specific DCI may be a modified DCI (e.g., a modified legacy SIB1 DCI, etc.) that includes information about the scheduling of the new REDCAP-specific SIB1, and / or may be a new REDCAP DCI transmitted by RAN node 110.

[0123] In optional operation S4050, after blindly searching for PDDCH candidates based on the assumption that the determined CORESET 0 is extended CORESE 0, UE device 130 can determine that RAN node 110 supports extended CORESET and / or REDCAP SIB1 based on the successful reception of REDCAP-specific DCI from RAN node 110 using PDDCH candidates.

[0124] According to at least one example embodiment, in operation S4060, if the REDCAP-specific DCI is a modified DCI, the UE device 130 can determine the REDCAP SIB1 scheduling information from the expected number of bits (e.g., 15 bits, etc.) of the modified DCI. For example, the modified DCI may include the REDCAP SIB1 scheduling information in 15 (unused) bits reserved for HARQ-ACK, HARQ ID, etc., but the example embodiment is not limited to this, and more or fewer bits of the DCI may be used. According to another example embodiment, if the REDCAP-specific DCI is a new REDCAP DCI previously masked and / or scrambled by the RAN node 110 using the expected REDCAP-SI-RNTI, the UE device 130 can use the expected REDCAP-SI-RNTI (e.g., REDCAP-RNTI, etc.) to decode the REDCAP DCI to determine the scheduling information of the REDCAP SIB1 message.

[0125] In operation S4070, UE device 130 can receive REDCAP SIB1 messages from RAN node 110. The REDCAP SIB1 message can be a REDCAP-specific SIB1 (e.g., dedicated to REDCAP UE devices) and / or a modified SIB1 that can be used by legacy UE devices and RECAP UE devices.

[0126] In operation S4080, UE device 130 may access the wireless network (e.g., the cell corresponding to RAN node 110, etc.) (and / or initiate access to it) based on information (e.g., system information, network configuration information, etc.) included in the REDCAP SIB1 message or a modified SIB1 message, and / or any other subsequent REDCAP SIB message (e.g., REDCAP SIB2, SIB3, SIB4, etc. and / or modified SIB2, SIB3, SIC4, etc.). In other words, according to at least one example embodiment, the transmission of the REDCAP SIB1 message (and / or the modified SIB1 message) by RAN node 110 may cause and / or enable UE device 130 to access the wireless network or initiate access to the wireless network.

[0127] Now for reference Figures 5 to 7 Various examples of extended CORESET 0 (e.g., conventional CORESET with REDCAP extension) according to some example embodiments are shown.

[0128] exist Figure 5 In this example embodiment, according to at least one exemplary embodiment, extended CORESET 0 may be a conventional CORESET with REDCAP extensions, but is not limited thereto. CORESET 0 may be a resource set comprising multiple control channel elements (CCEs) spanning both frequency (e.g., resource blocks (RBs) or physical resource blocks (PRBs)) and time domain (e.g., orthogonal frequency division multiplexing (OFDM) symbols). CORESET 0 may be used by a UE device such as UE device 130 to determine PDCCH candidates for the associated search space to be monitored, and each PDCCH candidate may comprise a contiguous subset of logical CCEs of the CORESET. Each CCE in the CORESET corresponds to a desired number of resource element groups (REGs), for example, 6 REGs are defined in a 5G RAT, and each REG may comprise a desired number of resource elements carrying PDCCHs in RBs and OFDM symbols (e.g., 9 resource elements in a 5G RAT) and a desired number of resource elements carrying demodulation reference signals (DMRS) (e.g., 3 resource elements in a 5G RAN), but the exemplary embodiment is not limited thereto.

[0129] According to at least one example embodiment, Extended CORESET 0 may reserve 16 CCEs (e.g., traditional CCE, traditional control resource, traditional control resource element, etc.) for Traditional CORESET 0 using 2 OFDM symbols and 48 RBs, and may add an additional 8 CCEs (e.g., exCCE 0-7, Extended CCE, Extended Control Resource, Extended Control Resource Element, REDCAP CCE, REDCAP Control Resource, REDCAP Control Resource Element, etc.) reserved for REDCAP extension using additional OFDM symbols and 48 RBs, but the example embodiment is not limited thereto. The combination of traditional CCE and extended CCE may be referred to as joint control resource. UE device 130 may determine the CCE corresponding to the PDCCH candidate based on the desired aggregation level, to be used with a hash function defined corresponding to a RAT (e.g., 5G RAT, etc.) to determine the search space for monitoring the PDCCH.

[0130] For example, according to Figure 5 In example embodiments, if UE device 130 is a legacy UE device, UE device 130 can use aggregation levels 4, 8, and 16, which correspond only to legacy CORESET, to search for CCEs corresponding to legacy CORESET 0. If UE device 130 is a REDCAP UE device, UE device 130 uses extended aggregation level 24 (e.g., expected REDCAP aggregation level, etc.) to search for CCEs associated with legacy CORESET 0 (e.g., CCEs 0-15) and REDCAP extended CCEs (e.g., extended CCEs 0-7), but the example embodiments are not limited thereto. Furthermore, according to some example embodiments, UE device 130 can use all aggregation levels (e.g., aggregation levels 4, 8, 16, and 24) corresponding to both legacy CORESET 0 and REDCAP extended CCEs to determine PDCCH candidates to be monitored. Furthermore, according to other example embodiments, UE device 130 can determine which aggregation levels to use based on the result of determining whether RAN node 110 supports extended CORESET and / or REDCAP UE devices. For example, if UE device 130 determines that RAN node 110 only supports legacy CORESET 0, then UE device 130 can omit the use of the aggregation level corresponding to the REDCAP extension (e.g., REDCAP aggregation level and / or aggregation level 24, etc.). Furthermore, as in combination Figure 4As discussed in operation S4050, UE device 130 can automatically assume that CORESET 0 is an extended CORESET and attempt to determine PDCCH candidates using the traditional and REDCAP aggregation levels, and then determine whether the cell (e.g., RAN node 110) supports REDCAP UE devices based on whether the attempt to decode the PDCCH candidates is successful.

[0131] Now for reference Figure 6 , Figure 6 A second example extended CORESET 0 according to at least one example embodiment is illustrated. According to this example embodiment, extended CORESET 0 may include a conventional CORESET comprising CCEs 0-7 transmitted to UE device 130 across two OFDM symbols in a first time-frequency region indicated by a first CORESET configuration (e.g., PDCCH code blocks, etc.), and extensions (e.g., extended CCEs 0-7) transmitted to UE device 130 in subsequent separate time-frequency regions indicated by a second and / or extended CORESET configuration. According to this example embodiment, both the conventional CCE and the extended CCE may comprise 24 resource blocks spanning two OFDM symbols, and therefore, UE device 130 may use aggregation levels 4, 8, and 24 to search for conventional and extended CCEs to determine PDCCH candidates; the example embodiment is not limited thereto.

[0132] Now for reference Figure 7 , Figure 7A third example extended CORESET 0 is illustrated according to at least one example embodiment. According to this example embodiment, extended CORESET 0 may include a conventional CORESET 0 and an extended CORESET 0 appended to the conventional CORESET 0, but the example embodiment is not limited thereto. UE device 130 treats extended CORESET 0 as a CORESET (e.g., a single CORESET) and determines CCE and REG based on extended CORESET 0. According to some example embodiments, (multiple) joint control resources (such as CCE or REG) may be interleaved, and PDCCH candidates of the associated search space (e.g., search space 0, etc.) may be mapped to the joint control resources of the extended CORESET using a hash function. Based on the assumption that the extended CCE is appended in the frequency domain, PDCCH code blocks (e.g., encoded DCI bits) may be mapped to the CCE of the PDCCH candidate frequency in a first time and a second time, but the example embodiment is not limited thereto. Furthermore, according to some example embodiments, UE device 130 may use aggregation levels associated with conventional CORESET 0 (e.g., aggregation levels 4, 8, and 16) to decode extended CORESET 0, and UE device 130 may not need to use REDCAP aggregation levels associated with extended CORESET 0 (e.g., aggregation level 24, etc.).

[0133] Although Figures 4 to 7 Various methods for obtaining and / or transmitting REDCAP-specific system information from a wireless network by a UE device are illustrated, but the example embodiments are not limited thereto, and other methods may be used for obtaining REDCAP-specific system information from a wireless network by a UE device.

[0134] Various example embodiments relate to a wireless network system including one or more NR lightweight and / or REDCAP UE devices configured to acquire REDCAP-specific system information from at least one cell of the wireless network. Therefore, one or more of the example embodiments provide a method for acquiring system information from a wireless network cell that consumes less power and / or requires less computational complexity than conventional system information acquisition techniques, thereby extending battery life and increasing the efficiency and / or performance of the NR lightweight and / or REDCAP UE devices.

[0135] This written description uses examples of the disclosed subject matter to enable those skilled in the art to practice the subject matter, including making and using any device or system and performing any combined methods. The patentable scope of the subject matter is defined by the claims and may include other examples that would occur to those skilled in the art. These other examples are intended to be within the scope of the claims.

Claims

1. A user equipment (UE) device, comprising: Memory, which stores computer-readable instructions; as well as The processing circuitry is configured to execute the computer-readable instructions to cause the UE device, Multiple physical downlink control channel (PDCCH) candidates are determined from the control resource set CORESET. Monitor PDCCH from the plurality of PDCCH candidates The reduction capability (REDCAP) scheduling information is determined from the downlink control information (DCI) received on the PDCCH, and REDCAP system information is received based on the determined REDCAP scheduling information. The DCI is scrambled using the REDCAP-specific radio network temporary identifier RNTI, and the DCI includes scheduling information corresponding to REDCAP SIB1.

2. The UE device according to claim 1, wherein: The CORESET is an extended CORESET; and The extended CORESET includes one or more traditional control resources and one or more extended control resources.

3. The UE device according to claim 2, wherein the UE device is further configured to: Determine whether the radio access network (RAN) node supports the extended CORESET.

4. The UE device of claim 3, wherein the UE device is further configured to determine whether the RAN node supports the extended CORESET by: Receive the Master Information Block (MIB) from the RAN node; Determine whether the MIB includes REDCAP support information; and Whether the RAN node supports the extended CORESET is determined based on the result of determining whether the MIB includes the REDCAP support information.

5. The UE device of claim 3, wherein the UE device is further configured to determine whether the RAN node supports the extended CORESET by: The search space associated with the multiple PDCCH candidate blind monitoring and the extended CORESET; and Whether the RAN node supports the extended CORESET is determined based on the successful reception of the DCI on the PDCCH.

6. The UE device according to claim 1, wherein: The DCI includes scheduling information corresponding to traditional system information block type 1 SIB1 and scheduling information corresponding to REDCAP SIB1.

7. The UE device of claim 2, wherein the plurality of PDCCH candidates include control channel elements (CCEs) from the one or more conventional control resources and the one or more extended control resources.

8. The UE device according to claim 2, wherein: The one or more conventional control resources and the one or more extended control resources are continuous in the time domain or frequency domain.

9. The UE device according to claim 2, wherein: The one or more traditional control resources and the one or more extended control resources are located in different time slots.

10. The UE device of claim 2, wherein the plurality of PDCCH candidates includes CCEs from the one or more extended control resources.

11. A user equipment (UE) device, comprising: Memory, which stores computer-readable instructions; as well as The processing circuitry is configured to execute the computer-readable instructions to cause the UE device, Determine whether the radio access network (RAN) nodes support the extended control resource set (CORESET). Based on the result of determining whether the RAN node supports the extended CORESET, multiple physical downlink control channel (PDCCH) candidates are determined from the CORESET. Monitor PDCCH from the plurality of PDCCH candidates, and Decode the downlink control information (DCI) received on the monitored PDCCH. The DCI is scrambled using the reduced capability REDCAP-specific radio network temporary identifier RNTI, and the DCI includes scheduling information corresponding to REDCAP SIB1.

12. The UE device of claim 11, wherein the UE device is further configured to: The REDCAP scheduling information is determined from the decoded DCI; and REDCAP system information is received from the RAN node based on the determined REDCAP scheduling information.

13. The UE device of claim 11, wherein the UE device is further configured to: Receive a REDCAP System Information Block Type 1 (SIB1) message, which includes the REDCAP system information.

14. A method for operating a user equipment (UE) device, comprising: The processing circuitry system is used to determine multiple physical downlink control channel (PDCCH) candidates from the control resource set CORESET. The processing circuitry system is used to monitor the PDCCH from the plurality of PDCCH candidates; The processing circuitry system uses the downlink control information (DCI) received from the PDCCH to determine the reduction capability (REDCAP) scheduling information. as well as The processing circuitry system uses the determined REDCAP scheduling information to receive REDCAP system information. The DCI is scrambled using the REDCAP-specific radio network temporary identifier RNTI, and the DCI includes scheduling information corresponding to REDCAP SIB1.

15. The method of claim 14, wherein: The CORESET is an extended CORESET; and The extended CORESET includes one or more traditional control resources and one or more extended control resources.

16. The method of claim 15, further comprising: The processing circuitry system is used to determine whether the radio access network (RAN) node supports the extended CORESET.

17. The method of claim 16, wherein determining whether the RAN node supports the extended CORESET comprises: Receive the Master Information Block (MIB) from the RAN node; Determine whether the MIB includes REDCAP support information; as well as Whether the RAN node supports the extended CORESET is determined based on the result of determining whether the MIB includes the REDCAP support information.

18. The method of claim 16, wherein determining whether the RAN node supports the extended CORESET comprises: The search space associated with the multiple PDCCH candidate blind monitoring and the extended CORESET; as well as Whether the RAN node supports the extended CORESET is determined based on the successful reception of the DCI on the PDCCH.

Images