WO2022189915A1 - Configuring a frequency resource for initial access - Google Patents

Abstract

Apparatuses, methods, and systems are disclosed for configuring a frequency resource for initial access. One method (1500) includes transmitting (1502) a first message to a user device. The first message includes a configuration of multiple frequency resources for initial access. The method (1500) includes receiving (1504) a second message from the user device in accordance with the configuration of the multiple frequency resources for initial access. The method (1500) includes determining (1506) a number of messages received from user devices on each configured frequency resource for initial access. The method (1500) includes transmitting (1508) a third message to the user device. The third message includes an indication to change a current frequency resource to another frequency resource for initial access. The method (1500) includes receiving (1510) a fourth message from the user device on the another frequency resource for initial access.

Description

CONFIGURING A FREQUENCY RESOURCE FOR INITIAL ACCESS

CROSS-REFERENCE TO RELATED APPLICATIONS

[0001] This application claims priority to United States Patent Application Serial Number 63/158,519 entitled “APPARATUSES, METHODS, AND SYSTEMS FOR CONFIGURATION AND USAGE OF MULTIPLE BANDWIDTH PARTS IN IDLE AND INACTIVE STATES” and fded on March 9, 2021 for Hyung-Nam Choi, which is incorporated herein by reference in its entirety.

FIELD

[0002] The subject matter disclosed herein relates generally to wireless communications and more particularly relates to configuring a frequency resource for initial access.

BACKGROUND

[0003] In certain wireless communications networks, a bandwidth configuration may be made for initial access to a cell. In such networks, the bandwidth configuration may need to be changed.

BRIEF SUMMARY

[0004] Methods for configuring a frequency resource for initial access are disclosed. Apparatuses and systems also perform the functions of the methods. One embodiment of a method includes transmitting, from a network device, a first message to a user device. The first message includes a configuration of multiple frequency resources for initial access. In some embodiments, the method includes receiving a second message from the user device in accordance with the configuration of the multiple frequency resources for initial access. In certain embodiments, the method includes determining a number of messages received from user devices on each configured frequency resource for initial access. In various embodiments, the method includes transmitting a third message to the user device. The third message includes an indication to change a current frequency resource to another frequency resource for initial access. In some embodiments, the method includes receiving a fourth message from the user device on the another frequency resource for initial access.

[0005] One apparatus for configuring a frequency resource for initial access includes a network device. In some embodiments, the apparatus includes a transmitter that transmits a first message to a user device. The first message includes a configuration of multiple frequency resources for initial access. In various embodiments, the apparatus includes a receiver that receives a second message from the user device in accordance with the configuration of the multiple frequency resources for initial access. In certain embodiments, the apparatus includes a processor that determines a number of messages received from user devices on each configured frequency resource for initial access. The transmitter transmits a third message to the user device. The third message includes an indication to change a current frequency resource to another frequency resource for initial access. The receiver receives a fourth message from the user device on the another frequency resource for initial access.

[0006] Another embodiment of a method for configuring a frequency resource for initial access includes receiving, at a user device, a first message from a network device. The first message includes a configuration of multiple frequency resources for initial access. In some embodiments, the method includes selecting a frequency resource for initial access in accordance with the first message. In certain embodiments, the method includes transmitting a second message to the network device in accordance with the selected frequency resource for initial access.

[0007] Another apparatus for configuring a frequency resource for initial access includes a user device . In some embodiments, the apparatus includes a receiver that receives a first message from a network device . The first message includes a configuration of multiple frequency resources for initial access. In various embodiments, the apparatus includes a processor that selects a frequency resource for initial access in accordance with the first message. In certain embodiments, the apparatus includes a transmitter that transmits a second message to the network device in accordance with the selected frequency resource for initial access.

BRIEF DESCRIPTION OF THE DRAWINGS

[0008] A more particular description of the embodiments briefly described above will be rendered by reference to specific embodiments that are illustrated in the appended drawings. Understanding that these drawings depict only some embodiments and are not therefore to be considered to be limiting of scope, the embodiments will be described and explained with additional specificity and detail through the use of the accompanying drawings, in which:

[0009] Figure 1 is a schematic block diagram illustrating one embodiment of a wireless communication system for configuring a frequency resource for initial access;

[0010] Figure 2 is a schematic block diagram illustrating one embodiment of an apparatus that may be used for configuring a frequency resource for initial access;

[0011] Figure 3 is a schematic block diagram illustrating one embodiment of an apparatus that may be used for configuring a frequency resource for initial access;

[0012] Figure 4 is a schematic block diagram illustrating one embodiment of a bandwidth configuration for initial access to a cell; [0013] Figures 5 A and 5B are schematic block diagrams illustrating one embodiment of a system for message flows for 4-step and 2-step CBRA procedures;

[0014] Figures 6A and 6B are schematic block diagrams illustrating one embodiment of a system for additional initial BWPs for TDD and FDD;

[0015] Figure 7 is a schematic block diagram illustrating one embodiment of a bandwidth adaptation in RRC CONNECTED;

[0016] Figure 8 is a schematic block diagram illustrating one embodiment of a simplified timing diagram with regards to transmissions in an initial UL/DL BWP in RRC IDLE and/or RRC INACTIVE for FDD mode;

[0017] Figure 9 is one embodiment of an ASN.l structure for signaling multiple initial BWP configurations;

[0018] Figure 10 is one embodiment of an ASN.l structure for signaling an initial BWP identity in an RRC release message;

[0019] Figure 11 is a schematic block diagram illustrating one embodiment of a configuration of RA resources in 1st and 2nd initial UL BWPs;

[0020] Figures 12A and 12B are schematic block diagrams illustrating one embodiment of a system for switching of an initial UL BWP during a CBRA procedure;

[0021] Figure 13 is a schematic block diagram illustrating one embodiment of a system for a message flow for a third embodiment;

[0022] Figure 14 is a schematic block diagram illustrating one embodiment of a system for a message flow for a fourth embodiment;

[0023] Figure 15 is a flow chart diagram illustrating one embodiment of a method for configuring a frequency resource for initial access; and

[0024] Figure 16 is a flow chart diagram illustrating another embodiment of a method for configuring a frequency resource for initial access.

DETAILED DESCRIPTION

[0025] As will be appreciated by one skilled in the art, aspects of the embodiments may be embodied as a system, apparatus, method, or program product. Accordingly, embodiments may take the form of an entirely hardware embodiment, an entirely software embodiment (including firmware, resident software, micro-code, etc.) or an embodiment combining software and hardware aspects that may all generally be referred to herein as a “circuit,” “module” or “system.” Furthermore, embodiments may take the form of a program product embodied in one or more computer readable storage devices storing machine readable code, computer readable code, and/or program code, referred hereafter as code. The storage devices may be tangible, non-transitory, and/or non-transmission. The storage devices may not embody signals. In a certain embodiment, the storage devices only employ signals for accessing code.

[0026] Certain of the functional units described in this specification may be labeled as modules, in order to more particularly emphasize their implementation independence. For example, a module may be implemented as a hardware circuit comprising custom very-large-scale integration (“VLSI”) circuits or gate arrays, off-the-shelf semiconductors such as logic chips, transistors, or other discrete components. A module may also be implemented in programmable hardware devices such as field programmable gate arrays, programmable array logic, programmable logic devices or the like.

[0027] Modules may also be implemented in code and/or software for execution by various types of processors. An identified module of code may, for instance, include one or more physical or logical blocks of executable code which may, for instance, be organized as an object, procedure, or function. Nevertheless, the executables of an identified module need not be physically located together, but may include disparate instructions stored in different locations which, when joined logically together, include the module and achieve the stated purpose for the module.

[0028] Indeed, a module of code may be a single instruction, or many instructions, and may even be distributed over several different code segments, among different programs, and across several memory devices. Similarly, operational data may be identified and illustrated herein within modules, and may be embodied in any suitable form and organized within any suitable type of data structure. The operational data may be collected as a single data set, or may be distributed over different locations including over different computer readable storage devices. Where a module or portions of a module are implemented in software, the software portions are stored on one or more computer readable storage devices.

[0029] Any combination of one or more computer readable medium may be utilized. The computer readable medium may be a computer readable storage medium. The computer readable storage medium may be a storage device storing the code. The storage device may be, for example, but not limited to, an electronic, magnetic, optical, electromagnetic, infrared, holographic, micromechanical, or semiconductor system, apparatus, or device, or any suitable combination of the foregoing.

[0030] More specific examples (a non-exhaustive list) of the storage device would include the following: an electrical connection having one or more wires, a portable computer diskette, a hard disk, a random access memory (“RAM”), a read-only memory (“ROM”), an erasable programmable read-only memory (“EPROM” or Flash memory), a portable compact disc read only memory (“CD-ROM”), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing. In the context of this document, a computer readable storage medium may be any tangible medium that can contain, or store a program for use by or in connection with an instruction execution system, apparatus, or device.

[0031] Code for carrying out operations for embodiments may be any number of lines and may be written in any combination of one or more programming languages including an object oriented programming language such as Python, Ruby, Java, Smalltalk, C++, or the like, and conventional procedural programming languages, such as the "C" programming language, or the like, and/or machine languages such as assembly languages. The code may execute entirely on the user's computer, partly on the user's computer, as a stand-alone software package, partly on the user's computer and partly on a remote computer or entirely on the remote computer or server. In the latter scenario, the remote computer may be connected to the user's computer through any type of network, including a local area network (“LAN”) or a wide area network (“WAN”), or the connection may be made to an external computer (for example, through the Internet using an Internet Service Provider).

[0032] Reference throughout this specification to “one embodiment,” “an embodiment,” or similar language means that a particular feature, structure, or characteristic described in connection with the embodiment is included in at least one embodiment. Thus, appearances of the phrases “in one embodiment,” “in an embodiment,” and similar language throughout this specification may, but do not necessarily, all refer to the same embodiment, but mean “one or more but not all embodiments” unless expressly specified otherwise. The terms “including,” “comprising,” “having,” and variations thereof mean “including but not limited to,” unless expressly specified otherwise. An enumerated listing of items does not imply that any or all of the items are mutually exclusive, unless expressly specified otherwise. The terms “a,” “an,” and “the” also refer to “one or more” unless expressly specified otherwise.

[0033] Furthermore, the described features, structures, or characteristics of the embodiments may be combined in any suitable manner. In the following description, numerous specific details are provided, such as examples of programming, software modules, user selections, network transactions, database queries, database structures, hardware modules, hardware circuits, hardware chips, etc., to provide a thorough understanding of embodiments. One skilled in the relevant art will recognize, however, that embodiments may be practiced without one or more of the specific details, or with other methods, components, materials, and so forth. In other instances, well-known structures, materials, or operations are not shown or described in detail to avoid obscuring aspects of an embodiment. [0034] Aspects of the embodiments are described below with reference to schematic flowchart diagrams and/or schematic block diagrams of methods, apparatuses, systems, and program products according to embodiments. It will be understood that each block of the schematic flowchart diagrams and/or schematic block diagrams, and combinations of blocks in the schematic flowchart diagrams and/or schematic block diagrams, can be implemented by code. The code may be provided to a processor of a general purpose computer, special purpose computer, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions/acts specified in the schematic flowchart diagrams and/or schematic block diagrams block or blocks.

[0035] The code may also be stored in a storage device that can direct a computer, other programmable data processing apparatus, or other devices to function in a particular manner, such that the instructions stored in the storage device produce an article of manufacture including instructions which implement the function/act specified in the schematic flowchart diagrams and/or schematic block diagrams block or blocks.

[0036] The code may also be loaded onto a computer, other programmable data processing apparatus, or other devices to cause a series of operational steps to be performed on the computer, other programmable apparatus or other devices to produce a computer implemented process such that the code which execute on the computer or other programmable apparatus provide processes for implementing the functions/acts specified in the flowchart and/or block diagram block or blocks.

[0037] The schematic flowchart diagrams and/or schematic block diagrams in the Figures illustrate the architecture, functionality, and operation of possible implementations of apparatuses, systems, methods and program products according to various embodiments. In this regard, each block in the schematic flowchart diagrams and/or schematic block diagrams may represent a module, segment, or portion of code, which includes one or more executable instructions of the code for implementing the specified logical function(s).

[0038] It should also be noted that, in some alternative implementations, the functions noted in the block may occur out of the order noted in the Figures. For example, two blocks shown in succession may, in fact, be executed substantially concurrently, or the blocks may sometimes be executed in the reverse order, depending upon the functionality involved. Other steps and methods may be conceived that are equivalent in function, logic, or effect to one or more blocks, or portions thereof, of the illustrated Figures. [0039] Although various arrow types and line types may be employed in the flowchart and/or block diagrams, they are understood not to limit the scope of the corresponding embodiments. Indeed, some arrows or other connectors may be used to indicate only the logical flow of the depicted embodiment. For instance, an arrow may indicate a waiting or monitoring period of unspecified duration between enumerated steps of the depicted embodiment. It will also be noted that each block of the block diagrams and/or flowchart diagrams, and combinations of blocks in the block diagrams and/or flowchart diagrams, can be implemented by special purpose hardware-based systems that perform the specified functions or acts, or combinations of special purpose hardware and code.

[0040] The description of elements in each figure may refer to elements of proceeding figures. Like numbers refer to like elements in all figures, including alternate embodiments of like elements.

[0041] Figure 1 depicts an embodiment of a wireless communication system 100 for configuring a frequency resource for initial access. In one embodiment, the wireless communication system 100 includes remote units 102 and network units 104. Even though a specific number of remote units 102 and network units 104 are depicted in Figure 1, one of skill in the art will recognize that any number of remote units 102 and network units 104 may be included in the wireless communication system 100.

[0042] In one embodiment, the remote units 102 may include computing devices, such as desktop computers, laptop computers, personal digital assistants (“PDAs”), tablet computers, smart phones, smart televisions (e.g., televisions connected to the Internet), set-top boxes, game consoles, security systems (including security cameras), vehicle on-board computers, network devices (e.g., routers, switches, modems), aerial vehicles, drones, or the like. In some embodiments, the remote units 102 include wearable devices, such as smart watches, fitness bands, optical head-mounted displays, or the like. Moreover, the remote units 102 may be referred to as subscriber units, mobiles, mobile stations, users, terminals, mobile terminals, fixed terminals, subscriber stations, UE, user terminals, a device, or by other terminology used in the art. The remote units 102 may communicate directly with one or more of the network units 104 via UL communication signals. In certain embodiments, the remote units 102 may communicate directly with other remote units 102 via sidelink communication.

[0043] The network units 104 may be distributed over a geographic region. In certain embodiments, a network unit 104 may also be referred to and/or may include one or more of an access point, an access terminal, a base, a base station, a location server, a core network (“CN”), a radio network entity, a Node-B, an evolved node-B (“eNB”), a 5G node-B (“gNB”), a Home Node-B, a relay node, a device, a core network, an aerial server, a radio access node, an access point (“AP”), new radio (“NR”), a network entity, an access and mobility management function (“AMF”), a unified data management (“UDM”), a unified data repository (“UDR”), a UDM/UDR, a policy control function (“PCF”), a radio access network (“RAN”), a network slice selection function (“NSSF”), an operations, administration, and management (“OAM”), a session management function (“SMF”), a user plane function (“UPF”), an application function, an authentication server function (“AUSF”), security anchor functionality (“SEAF”), trusted non- 3 GPP gateway function (“TNGF”), or by any other terminology used in the art. The network units 104 are generally part of a radio access network that includes one or more controllers communicably coupled to one or more corresponding network units 104. The radio access network is generally communicably coupled to one or more core networks, which may be coupled to other networks, like the Internet and public switched telephone networks, among other networks. These and other elements of radio access and core networks are not illustrated but are well known generally by those having ordinary skill in the art.

[0044] In one implementation, the wireless communication system 100 is compliant with NR protocols standardized in third generation partnership project (“3GPP”), wherein the network unit 104 transmits using an OFDM modulation scheme on the downlink (“DL”) and the remote units 102 transmit on the uplink (“UL”) using a single-carrier frequency division multiple access (“SC-FDMA”) scheme or an orthogonal frequency division multiplexing (“OFDM”) scheme. More generally, however, the wireless communication system 100 may implement some other open or proprietary communication protocol, for example, WiMAX, institute of electrical and electronics engineers (“IEEE”) 802.11 variants, global system for mobile communications (“GSM”), general packet radio service (“GPRS”), universal mobile telecommunications system (“UMTS”), long term evolution (“LTE”) variants, code division multiple access 2000 (“CDMA2000”), Bluetooth®, ZigBee, Sigfoxx, among other protocols. The present disclosure is not intended to be limited to the implementation of any particular wireless communication system architecture or protocol.

[0045] The network units 104 may serve a number of remote units 102 within a serving area, for example, a cell or a cell sector via a wireless communication link. The network units 104 transmit DL communication signals to serve the remote units 102 in the time, frequency, and/or spatial domain.

[0046] In various embodiments, a remote unit 102 may receive, at a user device, a first message from a network device. The first message includes a configuration of multiple frequency resources for initial access. In some embodiments, the remote unit 102 may select a frequency resource for initial access in accordance with the first message. In certain embodiments, the remote unit 102 may transmit a second message to the network device in accordance with the selected frequency resource for initial access. Accordingly, the remote unit 102 may be used for configuring a frequency resource for initial access.

[0047] In certain embodiments, a network unit 104 may transmit, from a network device, a first message to a user device. The first message includes a configuration of multiple frequency resources for initial access. In some embodiments, the network unit 104 may receive a second message from the user device in accordance with the configuration of the multiple frequency resources for initial access . In certain embodiments, the network unit 104 may determine a number of messages received from user devices on each configured frequency resource for initial access. In various embodiments, the network unit 104 may transmit a third message to the user device. The third message includes an indication to change a current frequency resource to another frequency resource for initial access. In some embodiments, the network unit 104 may receive a fourth message from the user device on the another frequency resource for initial access. Accordingly, the network unit 104 may be used for configuring a frequency resource for initial access.

[0048] Figure 2 depicts one embodiment of an apparatus 200 that may be used for configuring a frequency resource for initial access. The apparatus 200 includes one embodiment of the remote unit 102. Furthermore, the remote unit 102 may include a processor 202, a memory 204, an input device 206, a display 208, a transmitter 210, and a receiver 212. In some embodiments, the input device 206 and the display 208 are combined into a single device, such as a touchscreen. In certain embodiments, the remote unit 102 may not include any input device 206 and/or display 208. In various embodiments, the remote unit 102 may include one or more of the processor 202, the memory 204, the transmitter 210, and the receiver 212, and may not include the input device 206 and/or the display 208.

[0049] The processor 202, in one embodiment, may include any known controller capable of executing computer-readable instructions and/or capable of performing logical operations. For example, the processor 202 may be a microcontroller, a microprocessor, a central processing unit (“CPU”), a graphics processing unit (“GPU”), an auxiliary processing unit, a field programmable gate array (“FPGA”), or similar programmable controller. In some embodiments, the processor 202 executes instructions stored in the memory 204 to perform the methods and routines described herein. The processor 202 is communicatively coupled to the memory 204, the input device 206, the display 208, the transmitter 210, and the receiver 212. [0050] The memory 204, in one embodiment, is a computer readable storage medium. In some embodiments, the memory 204 includes volatile computer storage media. For example, the memory 204 may include a RAM, including dynamic RAM (“DRAM”), synchronous dynamic RAM (“SDRAM”), and/or static RAM (“SRAM”). In some embodiments, the memory 204 includes non-volatile computer storage media. For example, the memory 204 may include a hard disk drive, a flash memory, or any other suitable non-volatile computer storage device. In some embodiments, the memory 204 includes both volatile and non-volatile computer storage media. In some embodiments, the memory 204 also stores program code and related data, such as an operating system or other controller algorithms operating on the remote unit 102.

[0051] The input device 206, in one embodiment, may include any known computer input device including a touch panel, a button, a keyboard, a stylus, a microphone, or the like. In some embodiments, the input device 206 may be integrated with the display 208, for example, as a touchscreen or similar touch-sensitive display. In some embodiments, the input device 206 includes a touchscreen such that text may be input using a virtual keyboard displayed on the touchscreen and/or by handwriting on the touchscreen. In some embodiments, the input device 206 includes two or more different devices, such as a keyboard and a touch panel.

[0052] The display 208, in one embodiment, may include any known electronically controllable display or display device. The display 208 may be designed to output visual, audible, and/or haptic signals. In some embodiments, the display 208 includes an electronic display capable of outputting visual data to a user. For example, the display 208 may include, but is not limited to, a liquid crystal display (“LCD”), a light emitting diode (“LED”) display, an organic light emitting diode (“OLED”) display, a projector, or similar display device capable of outputting images, text, or the like to a user. As another, non-limiting, example, the display 208 may include a wearable display such as a smart watch, smart glasses, a heads-up display, or the like. Further, the display 208 may be a component of a smart phone, a personal digital assistant, a television, a table computer, a notebook (laptop) computer, a personal computer, a vehicle dashboard, or the like.

[0053] In certain embodiments, the display 208 includes one or more speakers for producing sound. For example, the display 208 may produce an audible alert or notification (e.g., a beep or chime). In some embodiments, the display 208 includes one or more haptic devices for producing vibrations, motion, or other haptic feedback. In some embodiments, all or portions of the display 208 may be integrated with the input device 206. For example, the input device 206 and display 208 may form a touchscreen or similar touch-sensitive display. In other embodiments, the display 208 may be located near the input device 206. [0054] In certain embodiments, the receiver 212 receives a first message from a network device. The first message includes a configuration of multiple frequency resources for initial access. In various embodiments, the processor 202 selects a frequency resource for initial access in accordance with the first message. In certain embodiments, the transmitter 210 transmits a second message to the network device in accordance with the selected frequency resource for initial access.

[0055] Although only one transmitter 210 and one receiver 212 are illustrated, the remote unit 102 may have any suitable number of transmitters 210 and receivers 212. The transmitter 210 and the receiver 212 may be any suitable type of transmitters and receivers. In one embodiment, the transmitter 210 and the receiver 212 may be part of a transceiver.

[0056] Figure 3 depicts one embodiment of an apparatus 300 that may be used for configuring a frequency resource for initial access. The apparatus 300 includes one embodiment of the network unit 104. Furthermore, the network unit 104 may include a processor 302, a memory 304, an input device 306, a display 308, a transmitter 310, and a receiver 312. As may be appreciated, the processor 302, the memory 304, the input device 306, the display 308, the transmitter 310, and the receiver 312 may be substantially similar to the processor 202, the memory 204, the input device 206, the display 208, the transmitter 210, and the receiver 212 of the remote unit 102, respectively.

[0057] In certain embodiments, the transmitter 310 transmits a first message to a user device. The first message includes a configuration of multiple frequency resources for initial access. In various embodiments, the receiver 312 receives a second message from the user device in accordance with the configuration of the multiple frequency resources for initial access. In certain embodiments, the processor 302 determines a number of messages received from user devices on each configured frequency resource for initial access. The transmitter 310 transmits a third message to the user device. The third message includes an indication to change a current frequency resource to another frequency resource for initial access. The receiver 312 receives a fourth message from the user device on the another frequency resource for initial access.

[0058] It should be noted that two or more embodiments described herein may be combined. In certain embodiments, initial access to a cell using a contention-based random access (“CBRA”) procedure is carried out by a user equipment (“UE”) in a radio resource control (“RRC”) idle (“RRC IDLE”) and/or RRC inactive (“RRC INACTIVE”) state in an initial uplink (“UL”) bandwidth part (“BWP”) of the cell. In such embodiments, the bandwidth of the initial UL BWP may be configured by a network up to 100 MHz in frequency range 1 (“FR1”) and 400 MHz in frequency range 2 (“FR2”). The bandwidth of the initial UL BWP may be lower due to: 1) the initial downlink (“DL”) BWP containing an entire control resource set (“CORESET”) (e.g., CORESET#0) of a serving cell in a frequency domain - a system information block (“SIB”) (e.g., SIB1) is transmitted on a physical downlink shared channel (“PDSCH”), which is scheduled by downlink control information (“DCI”) on a physical downlink control channel (“PDCCH”) using a control resource set with index zero (e.g., CORESET#0) - the bandwidth of CORESET#0 may be 24, 48, or 96 PRBs. The UE is mandated to support any of these bandwidths of CORESET#0 - the actual bandwidth in MHz depends on a subcarrier spacing (“SCS”) supported for the frequency band (e.g., FR1, FR2) - for instance, for 15 kHz SCS and a new radio (“NR”) band in FR1, the bandwidth of CORESET#0 is 4.32 MHz (e.g., = 24 PRBs), 8.64 MHz (e.g., = 48 PRBs), or 17.28 MHz (e.g., = 96 PRBs); 2) a UE can access a cell if the UE supports a channel bandwidth which is equal to or narrower than a channel bandwidth indicated in the SIB (e.g., SIB1) (e.g., indicated by field carrierBandwidth in information element (“IE”) UplinkConfigCommonSIB) and is equal to or wider than the bandwidth of an initial UL and/or DL BWP. That may mean that if the network configures the initial UL and/or DL BWP to the same bandwidth as the CORESET#0 then it can be sure that all UEs will be able to access the cell. If the network configures the initial UL and/or DL BWP wider than the CORESET#0, then there is the risk that some UEs might not support that bandwidth and consider the cell as barred.

[0059] Figure 4 is a schematic block diagram illustrating one embodiment of a bandwidth configuration 400 for initial access to a cell over a time 402 and a frequency 404. The bandwidth configuration 400 includes SSBs 405 (e.g., 20 physical resource blocks (“PRBs”)) for synchronization and master information block (‘MIB”) acquisition, CORESET#0 406 (e.g., 24 PRBs) for SIB1 acquisition, an initial DL BWP 408 (e.g., DL BWP#0, 24 PRBs) for random access, and an initial UL BWP 410 (e.g., UL BWP#0, 24 PRBs) for random access. Specifically, in this example it is assumed that the bandwidth of CORESET#0 406 and initial UL and/or DL BWP is set to 24 PRBs. An initial BWP has an index zero and is referred to as BWP#0. Referring to Figure 4, the UE performs time synchronization with respect to slot and radio frame timing and reads a MIB on a physical broadcast channel (“PBCH”) based on a synchronization signal block (“SSB”). The UE then proceeds with SIB1 acquisition based on the configuration of CORESET#0 406 in MIB. In SIB1 the UE can find the configuration of the initial UL and/or DL BWP and common random access channel (“RACH”) (e.g., cell-specific RACH parameters). In the initial DL BWP, the UE receives the PDCCH (e.g., carrying DCI for the associated PDSCH), and PDSCH (e.g., carrying paging and system information (“SI”) messages, random access response (“RAR”) and Msg4 and/or MsgB during the CBRA procedures). In the initial UL BWP, the UE transmits the PUCCH (e.g., carrying uplink control information (“UCI”) for the associated PUSCH), the PUSCH (e.g., carrying UL RRC messages), and physical random access channel (“PRACH”).

[0060] In various embodiments, for initial access in RRC IDLE and/or RRC INACTIVE, the common RACH configuration to be used in the initial UL BWP is signaled by the network per broadcast in SIB1 using the IE RACH-ConfigCommon. The common RACH resources include PRACH preambles (e.g., specific signal sequences used for random access) and RACH occasions (“RO”) in a time and/or frequency domain (e.g., instances to transmit PRACH preambles). In the time domain, the number of RACH occasions can vary from 1 RO in every 16th radio frame up to 10 ROs in every radio frame. In the frequency domain, 1, 2, 4, or 8 ROs can be configured. Furthermore, two types of CBRA procedures can be configured by the network: 1) 4-step CBRA procedure (e.g., also called “Type-1 RA”); and/or 2) 2-step CBRA procedure (e.g., also called “Type-2 RA”).

[0061] Figures 5 A and 5B are schematic block diagrams illustrating one embodiment of a system for message flows for 4-step 500 and 2-step 514 CBRA procedures. The system includes a UE 502 and a gNB 504. Each of the communications in the system may include one or more messages.

[0062] For the 4-step 500 CBRA procedure, in a first communication 506, a random access preamble is communicated. Further, in a second communication 508, a random access response is communicated. Moreover, in a third communication 510, a scheduled transmission is made to the gNB 504. In a fourth communication 512, contention resolution is communicated.

[0063] For the 2-step 514 CBRA procedure, in a first communication 516, a random access preamble is communicated. Further, in a second communication 518, a PUSCH payload is communicated. Moreover, in a third communication 520, contention resolution is communicated.

[0064] The simplified 2-step CBRA procedure may be used to reduce a number of interactions between the UE 502 and the network during the RRC connection setup procedure (e.g., for the UE 502 in the RRC IDLE state) or the RRC connection resume procedure (e.g., for the UE 502 in RRC INACTIVE state), thereby enabling a lower control plane latency. Random access (“RA”) partitioning in time and/or frequency (e.g., with regards to PRACH preambles and RACH occasions) between the 4-step CBRA and the 2-step CBRA procedures can be configured by the network if it supports both CBRA types. Table 1 shows RA type configuration options which are supported in NR.

Table 1 : RA type configuration options

[0065] In certain embodiments, usage of an initial UL BWP in RRC IDLE and/or RRC_INACTIVE state may: 1) in the context of radio access network (“RAN”) slicing enhancements, slice-specific RACH configurations may be signaled by the network per broadcast in SIB to enable the UE fast access to a specific slice that is supported by the cell - however, the bandwidth of the initial UL BWP may be limited to accommodate the additional configuration of the slice-specific RACH; 2) in the context of reduced capability NR devices, reduced capability UEs will share with normal UEs the initial UL BWP for initial access - however, this may lead to increased RACH collision and/or congestion if the number of reduced capability UEs in the cell is large; 3) in the context of small data transmission in RRC_INACTIVE, separate RA resources for normal RACH access and small data transmission (“SDT”) access may be configured by the network corresponding to different payload sizes for Msg3 and/or MsgA - however, the bandwidth of the initial UL BWP may be limited to accommodate the additional configuration of SDT RACH; and/or 4) in the context of the positioning enhancements transmission of positioning measurement reports and/or location estimates from the UE to the network in RRC INACTIVE may be supported. This may be done by enhancing small data transmission in RRC INACTIVE. This will affect the initial RACH procedure in RRC INACTIVE as well as the configuration of pre- configured PUSCH resources (e.g., by reusing the configured grant type 1) due to the fact that the size of positioning measurement reports and/or location estimates may be 1000 bits and more. [0066] In some embodiments, not to impact legacy UEs, it may be required to configure multiple UL and/or DL BWPs for initial access in RRC IDLE and/or RRC INACTIVE and for transmission of UL data on pre-configured PUSCH resources in RRC INACTIVE. However, the configuration and usage of multiple initial UL and/or DL BWPs in RRC IDLE and/or RRC INACTIVE may be used. [0067] In various embodiments, there may be: 1) signaling of an additional initial BWP configuration per broadcast in SIB; 2) criteria and/or conditions for initial selection of the initial BWPs and RA resources by a UE; and/or 3) criteria and/or conditions and mechanisms for switching between the initial BWPs.

[0068] Figures 6A and 6B are schematic block diagrams illustrating one embodiment of a system for additional initial BWPs for time division duplexing (“TDD”) 600 and frequency division duplexing (“FDD”) 612 over a time 602 and frequency 604. In TDD 600 there is an initial UF and/or DF (“UF/DF”) BWP#1 606, and an initial UF/DF BWP#0 608. In one embodiment, there may be an UF/DF BWP switch 610. Moreover, in FDD 612 there is an initial DF BWP#0 614, an initial UF BWP#1 616, and an initial UF BWP#0 618. In some embodiments, there may be an UF BWP switch 620.

[0069] In certain embodiments, there may be configuration and usage of UF/DF BWPs. In some embodiments, a UE in RRC IDFE and/or RRC INACTIVE state is configured and operated with only one BWP in UF/DF (e.g., the initial UF/DF BWP). In RRC CONNECTED state, a UE may be configured with up to 4 BWPs in UF/DF, but during UE operation only 1 BWP can be active in UF/DF at a time. The active BWP defines the UE's operating bandwidth within the cell's operating bandwidth.

[0070] Figure 7 is a schematic block diagram illustrating one embodiment of a bandwidth adaptation 700 in RRC CONNECTED over a time 702 and frequency 704. In Figure 7, the UE is configured with 3 DF BWPs to allow scheduling flexibility with respect to an amount of data and UE activity: BWP#1 706 with a bandwidth of 40 MHz and SCS of 15 kHz; BWP#2 708 with a bandwidth of 10 MHz and SCS of 15 kHz; and BWP#3 710 with a bandwidth of 20 MHz and SCS of 60 kHz. The example shown in Figure 7 is applicable to UF as well.

[0071] The change of an active BWP is done by BWP switching. BWP switching may be performed by: 1) DCI -based BWP switch: the network uses the DCI format 1 1 and/or format 1 2 (e.g., for DF) or DCI format 0 1 and/or format 0 2 (e.g., for UF) to switch the UE from the currently active BWP to another configured BWP - those DCI formats contain a BWP indicator field for BWP switch; 2) RRC-based BWP switch: the network transmits an RRC reconfiguration message to the UE (e.g., using the parameters firstActiveDownlinkBWP-Id and firstActiveUplinkBWP-Id in IE ServingCellConfig) - the RRC-based method is used to switch the UE from the initial BWP to another BWP (e.g., upon primary cell (“PCell”) change and primary serving cell (“PSCell”) addition and/or change); and/or 3) timer-based BWP switch: the network configures the UE with a default BWP to be used upon expiry of the BWP inactivity timer (e.g., timer value is in the range 2 ms to 2560 ms). The UE starts and/or restarts the timer whenever it decodes a DCI for the active BWP. So, the expiration of this timer indicates that the UE has no scheduled transmission and/or reception for a while on the currently active BWP. If the BWP inactivity timer is configured but not the default BWP then the UE uses the initial BWP as the default BWP. [0072] In some embodiments, such as in FDD mode, the UL and DL BWPs can be switched independently. In TDD, the DL BWPs and UL BWPs are linked and thus need to be switched together. BWP switching results in a switching delay t. The length of the switching delay t depends on the switching option.

[0073] In various embodiments, there may be transmissions in initial UL/DL BWP in RRC IDLE and/or RRC INACTIVE .

[0074] Figure 8 is a schematic block diagram illustrating one embodiment of a simplified timing diagram 800 with regards to transmissions in an initial UL/DL BWP in RRC IDLE and/or RRC INACTIVE for FDD mode over a time 802 and a frequency 804 for DL 806 and UL 808. The timing diagram 800 includes a discontinuous reception (“DRX”) cycle 810 and a RAR window 812.

[0075] If a UE initiates a CBRA procedure in an initial UL BWP (e.g., for 4-step RA as shown in Figure 5A), it randomly selects a RO and one preamble defined therein, and transmits the selected preamble (e.g., Msgl) at the allowed time instant of the selected RO. The RAR on PDSCH (e.g., Msg2) from gNB is expected by the UE within the configurable RAR window. If the RAR received from gNB contains a preamble identifier corresponding to the transmitted preamble, a temporary cell RNTI (“C-RNTI”) and a UL grant, the Msg2 reception is considered successful and the UE continues with the Msg3 transmission. The Msg3 carries the RRCSetupRequest message to request the establishment of an RRC connection (e.g., if the UE is in RRC IDLE) or the RRCResumeRequest message to request the resumption of a suspended RRC connection (e.g., if the UE is in RRC_INACTIVE). Once the Msg3 is transmitted, the UE starts the configurable contention resolution (“CR”) timer and monitors the PDCCH in DL while the CR timer is running. If the UE receives a PDCCH addressed with its temporary C-RNTI and an associated PDSCH containing the RRCSetup or RRCResume message and the UE contention resolution identity medium access control (“MAC”) control element (“CE”) (e.g., including the UL message sent in Msg3), the UE considers the contention resolution and CBRA procedure as successful. As a final step, the UE sends a Msg5 containing the RRCSetupComplete or RRCResumeComplete message to the gNB.

[0076] During the CBRA procedure, the UE may monitor one paging occasion (“PO”) per DRX cycle in the initial DL BWP to receive a paging message (e.g., for mobile terminating (“MT”) call) from the gNB. Paging messages are sent by the gNB on PDSCH and addressed with paging RNTI (“P-RNTI”) on PDCCH (e g., DCI format 1 0). As part of the PDCCH using P-RNTI and DCI format 1 0, short messages may be transmitted indicating: 1) a system information modification; or 2) an ETWS and CMAS indication. In the latter case the warning messages are according to ETWS (e.g., SIB6 and/or SIB7) or CMAS (e.g., SIB8) and will be transmitted by the gNB at the scheduled time instants.

[0077] In certain embodiments, it is left to UE implementation about whether to take the occurrence of paging occasions into account during a CBRA procedure (e.g., for determining a RACH occasion or for monitoring PDCCH for Msg2 and/or Msg4).

[0078] To support configuration and usage of multiple initial UL/DL BWPs in RRC IDLE and/or RRC INACTIVE the following solutions may include signaling of additional initial BWP configurations per broadcast in SIB.

[0079] In some embodiments, signaling of an additional initial BWP configuration with index #1 is carried on SIB1 by extending the IE ServingCellConfigCommonSIB and contains the following parameters: 1) a parameter “downlinkConfigCommonExt” that provides the frequency configuration, location and bandwidth of an additional initial DL BWP, parameters for the PDCCH and PDSCH of this BWP and the parameters for receiving SI and paging messages - the parameter “downlinkConfigCommonExt” is signaled for a TDD mode and may be signaled for an FDD mode if there is a need for an additional initial DL BWP; 2) a parameter “uplinkConfigCommonExt” provides the frequency configuration, location, and bandwidth of the additional initial UL BWP, and parameters for the RACH, PUCCH, and PUSCH of this BWP; and/or 3) a parameter “rach- ConfigCommonExt” provides the CBRA parameters for 4-step and/or 2-step RA to be used for a targeted type of UEs and features.

[0080] In various embodiments, if a 2nd initial DL BWP (e.g., an additional initial DL BWP) is not configured but a 2nd initial UL BWP (e.g., an additional initial UL BWP) is configured in a cell, a UE assumes that the 2nd initial UL BWP is associated with a 1st initial DL BWP of the cell (e.g., an initial DL BWP configured by MIB).

[0081] In certain embodiments, multiple initial BWP configurations may be signaled by a network to clearly separate the resources in RRC IDLE and/or RRC INACTIVE in accordance with the targeted type of UEs and features.

[0082] Figure 9 is one embodiment of an abstract syntax notation 1 (“ASN.1”) structure 900 for signaling multiple initial BWP configurations. In some embodiments, signaling of multiple initial BWP configurations can be carried on a new SIB. [0083] In various embodiments, there may be criteria and/or conditions for initial selection of the initial BWPs and RA resources by a UE.

[0084] In certain embodiments, for initial selection of the initial BWPs and RA resources by a UE the criteria and/or conditions may be defined for the UE and for the network.

[0085] In some embodiments, for the UE: 1) if the UE wants to initiate a CBRA procedure for initial access and the required type of RA resources is configured only on one of the initial UL BWPs, then the UE shall select the initial UL BWP where the required type of RA resources is configured; 2) if the UE wants to initiate a CBRA procedure for initial access and the required type of RA resources is configured on more than one initial UL BWPs, then the UE shall select the initial UL BWP based on a reference signal received power (“RSRP”) threshold configured by gNB - the UE shall select the initial UL BWP that is above the threshold - if more than one initial UL BWP satisfies the threshold, the UE shall select the best initial UL BWP with respect to the RSRP value; 3) for the selected initial UL BWP, the UE selects a RACH occasion such that the corresponding RAR window does not overlap with a paging occasion of the UE - that means, the RACH occasion selection shall also take a potential overlap of the corresponding RAR window with a PO into account - since gNB knows the UE identity (e.g., based on RACH Msg3) an overlap of RACH Msg4 with PO can be generally avoided by network implementation; and/or 4) if one or more RACH occasions associated with a particular SSB are configured only in one of multiple initial UL BWPs, a UE selects an initial UL BWP based on a SSB selected for RACH resource selection.

[0086] In various embodiments, for the network: 1) if the UE receives configuration information of additional initial DL and/or UL BWPs via SIB1 that is received in the 1st initial DL BWP configured by MIB, the UE may further receive an indication to use a specific initial UL BWP for a random access procedure and/or to use a specific initial DL BWP for monitoring paging DCI - for example, the indication includes an applicable UE type and/or capability for the specific initial UL/DL BWP - in another example, the indication includes information of paging frames and/or paging occasions associated with the specific initial DL BWP - the UE can determine which initial UL/DL BWP to use based on the UE type and/or capability or based on a paging frame and/or paging occasion determined based on a UE ID; 2) if the gNB decides to move the UE from RRC CONNE CTED to RRC IDLE and/or RRC INACTIVE and multiple initial BWPs are configured in the cell for initial access, then in accordance with the type of UE and its capabilities the gNB can configure the UE with the identity of the UL/DL BWP to be used for initial access to RRC IDLE and/or RRC INACTIVE in the RRC release message (e.g., by using the parameters “initialDownlinkBWP-rl7” and “initialUplinkBWP-rl7”) - Figure 10 is one embodiment of an ASN.l structure 1000 for signaling an initial BWP identity in an RRC release message; 3) for a UE in RRC CONNECTED, the gNB can indicate, via a PDCCH (e.g., by extending DCI format 1 0 by the field “Bandwidth part indicator” using one of the reserved bits or by introducing a new DCI format), an initial UL/DL BWP to the UE to use for a PDCCH ordered random access procedure; and/or 4) for a UE in RRC IDLE or RRC INACTIVE, a network can indicate an initial UL/DL BWP for the UE to use for a RRC connection establishment procedure or a RRC connection resume procedure via a paging message or via a short message in paging DCI.

[0087] In certain embodiments, there may be criteria and/or conditions and mechanisms for switching between initial BWPs.

[0088] In some embodiments, for switching between initial BWPs, the following criteria and/or conditions and mechanisms are defined: 1) if multiple initial DL BWPs (e.g., index #1, index #2, and so forth) are configured but without any parameters for receiving SI and paging messages and the UE initiated CBRA procedure for initial access on one of the additional initial UL BWPs (e.g., index #1, index #2, and so forth), then the UE shall switch autonomously to the 1st initial UL/DL BWP (e.g., index #0) if no RAR (e.g., Msg2) or contention resolution message (e.g., MsgB) has been received prior to the occurrence of the PO to not miss the reception of the paging or short message; and/or 2) if multiple initial UL BWP (e.g., index #1, index #2, and so forth) are configured, the UE initiated CBRA procedure for initial access on one of the UL BWPs and temporary congestion of the RA resources occurs on that UL BWP, then the gNB may decide to switch the UE from the current UL BWP to one of the other UL BWP if there is no congestion of the RA resources on that UL BWP. This may be done by either of the following options: 1) Ll- based by using DCI: the current DCI format 1 0 can be extended by the field “Bandwidth part indicator” using one of the reserved bits or a new DCI format can be defined for BWP switch in the context of CBRA procedure - the cyclic redundancy check (“CRC”) of the extended DCI format 1 0 or new DCI format is scrambled by RA-RNTI (e.g., in case of 4-step RA) or MsgB- RNTI (e.g., in case of 2-step RA) - considering the fact that the RA-RNTI or MsgB-RNTI is associated with the RACH occasion in which a preamble is transmitted, the DCI solution affects all UEs which transmitted preambles on the same RACH occasion; and/or 2) timer-based: if the UE does not receive the RAR (e.g., Msg2) successfully within a time configured by the gNB, then the UE shall switch autonomously from the current UL BWP to one of the other UL BWPs and initiate a CBRA procedure on the new UL BWP. If there are more than one initial UL BWP available as candidate, then the UE shall select the best initial UL BWP with respect to the RSRP value. [0089] In various embodiments, a configuration and usage of additional initial UL BWPs for FDD mode is used, but in-principle the embodiments are applicable for multiple initial UL BWPs and for TDD mode as well.

[0090] In a first embodiment, there may be configuration of initial UL BWPs to be used in an RRC IDLE and/or RRC INACTIVE for FDD mode. The gNB supports enhancements for initial access to the cell and configures additional RA resources for slices, reduced capability UEs (e.g., Redcap) and SDT (e.g., in RRC INACTIVE) for the initial UL BWP. Due to limited bandwidth of the legacy initial UL BWP (e.g., 1st UL BWP with index #0) and to not impact the legacy UEs, it configures an additional initial UL BWP (e.g., 2nd UL BWP with index #1) via IE ServingCellConfigCommonSIB in SIB1 using the parameter “uplinkConfigCommonExt-rl7” and sub-parameter “initialUplinkBWP-rl7”. The additional RA resources for slices, Redcap and SDT, are configured via sub-parameter “rach-ConfigCommonExt-rl7”. Figure 11 is a schematic block diagram illustrating one embodiment of a configuration 1100 of RA resources in 1st and 2nd initial UL BWPs over a time 1102 and frequency 1104. The configuration 1100 includes an initial DL BWP#0 1106, a 2nd initial UL BWP 1108 (BWP#1), and a 1st initial UL BWP 1110 (BWP#0). The 2nd initial UL BWP 1108 includes RA resources for Redcap 1112, RA resources for slices 1114, and RA resources for SDT 1116. Moreover, the 1st initial UL BWP 1110 includes legacy RA resources 1118. In the 2nd initial UL BWP 1108, the RA resources for slices 1114 and RA resources for SDT 1116 correspond to 2-step RA, and the RA resources for Redcap 1112 correspond to 4-step RA. In the 1st initial UL BWP 1110, the legacy RA resources 1118 correspond to 4-step RA. Both initial UL BWPs (e.g., with index #0 and index #1) are linked to the same initial DL BWP with index #0 for monitoring paging occasions and receiving paging and SI messages by the UEs.

[0091] In a second embodiment, there may be switching of an initial UL BWP during a CBRA procedure. In the second embodiment, an additional initial UL BWP (e.g., 2nd UL BWP with index #1) is configured with additional RA resources for slices, Redcap, and SDT. Multiple UEs are used which support SDT and initiate a 2-step CBRA procedure for SDT on the 2nd UL BWP. However, due to temporary congestion of the RA resources for SDT, the gNB decides to switch some UEs from the current UL BWP to the another UL BWP (e.g., 1st UL BWP with index #0) where there is no congestion of the RA resources for 4-step RA. The gNB sends to the UEs as MsgB a “BWP switch” indication by using the extended DCI format 1 0 (e.g., by setting the field “Bandwidth part indicator” to index #0) with CRC scrambled by MsgB-RNTI. All UEs monitoring the PDCCH with the respective DCI format receive the “BWP switch” indication from the gNB. The concerned UEs then switch to the 1st UL BWP and initiate the 4-step CBRA procedure there.

[0092] In some embodiments, the gNB may switch Redcap UEs from the 2nd UL BWP to the 1st UL BWP if temporary congestion of the 4-step RA resources for Redcap occurs. In this case, it sends to the UEs as Msg2 a “BWP switch” indication by using the extended DCI format 1_0 (e.g., by setting the field “Bandwidth part indicator” to index #0) with CRC scrambled by RA- RNTI.

[0093] Figures 12A and 12B are schematic block diagrams illustrating one embodiment of a system for switching of an initial UL BWP during a CBRA procedure. The system includes a UE 1202 and a gNB 1204. In a 4-step CBRA 1200, in a first communication 1206, the UE 1202 transmits a random access preamble to the gNB 1204. Further, in a second communication 1208, a BWP switch message is sent to the UE 1202. Moreover, in a 2-step CBRA 1210, in a first communication 1212, the UE 1202 transmits a random access preamble to the gNB 1204. In a second communication 1214, a PUSCH payload is transmitted to the gNB 1204. Further, in a third communication 1216, a BWP switch message is sent to the UE 1202.

[0094] In a third embodiment, there may be an initial selection of initial BWPs by an RRC release message. In such an embodiment, an additional initial UL BWP (e.g., 2nd UL BWP with index #1) is configured with additional RA resources for slices, Redcap, and SDT. Furthermore, a UE in RRC CONNECTED is assumed that supports SDT in RRC INACTIVE. Due to temporary data inactivity the gNB moves the UE from RRC CONNECTED to RRC INACTIVE.

[0095] Figure 13 is a schematic block diagram illustrating one embodiment of a system 1300 for a message flow for the third embodiment. The system 1300 includes a UE 1302 and a gNB 1304. Each of the communications in the system 1300 may include one or more messages.

[0096] In a first communication 1306, an RRC connection is established between the UE 1302 and the gNB 1304. Further, in a second communication 1308, in accordance with the type of the UE 1302 and its capabilities, the gNB 1304 sends the RRC release message to the UE 1302 including the parameter “initialUplinkBWP-rl7” set to index #1.

[0097] In RRC_INACTIVE, the UE 1302 monitors 1310 its paging occasions per DRX cycle in the initial DL BWP with index #0. Moreover, in a third communication 1312, the UE 1302 receives a paging message indicating an MT call and, to resume the suspended RRC connection, the UE initiates a CBRA procedure using the RA resources for SDT on the initial UL BWP with index # 1.

[0098] In a fourth embodiment, there may be an initial selection of initial BWPs by SIB signalling. In such embodiments, it is assumed that two additional initial UL BWPs (e.g., 2nd UL BWP with index #1, 3rd UL BWP with index #2) are configured in addition to the 1st initial UL BWP with index #0: 1) the 2nd UL BWP with index # 1 contains additional RA resources for slices, Redcap, and SDT; and/or 2) the 3rd UL BWP with index #2 contains additional RA resources for Redcap and SDT.

[0099] In various embodiments, the 1st initial UL BWP with index #0 contains RA resources only for legacy UEs (e.g., UEs not supporting slices, Redcap, or SDT). In certain embodiments, the CBRA parameters which are configured in the two additional initial UL BWPs are shared for the different types of UEs (e.g., they are not separated in time and/or frequency). Therefore, the gNB indicates for each BWP configuration the applicable UE types.

[0100] Figure 14 is a schematic block diagram illustrating one embodiment of a system 1400 for a message flow for a fourth embodiment. The system 1400 includes a UE 1402 and a gNB 1404. Each of the communications in the system 1400 may include one or more messages.

[0101] The Redcap UE 1402 is 1406 in an RRC IDLE state. Moreover, in a first communication 1408, the gNB 1404 indicates per SIB the applicable UE types for the configured additional UL BWPs. Further, in a second communication 1410, the Redcap UE 1402 determines that the 2nd UL BWP with index #1 and the 3rd UL BWP with index #2 are applicable for Redcap. Based on an RSRP threshold configured by gNB (e.g., as part of the SIB configuration) the UE 1402 selects the best initial UL BWP with respect to the RSRP value. It is assumed that the initial UL BWP with index #2 is the best one. Then, the UE 1402 initiates CBRA procedure using the RA resources for Redcap on the selected UL BWP with index #2 to establish RRC connection with the gNB.

[0102] Figure 15 is a flow chart diagram illustrating one embodiment of a method 1500 for configuring a frequency resource for initial access. In some embodiments, the method 1500 is performed by an apparatus, such as the network unit 104. In certain embodiments, the method 1500 may be performed by a processor executing program code, for example, a microcontroller, a microprocessor, a CPU, a GPU, an auxiliary processing unit, a FPGA, or the like.

[0103] In various embodiments, the method 1500 includes transmitting 1502, from a network device, a first message to a user device. The first message includes a configuration of multiple frequency resources for initial access. In some embodiments, the method 1500 includes receiving 1504 a second message from the user device in accordance with the configuration of the multiple frequency resources for initial access. In certain embodiments, the method 1500 includes determining 1506 a number of messages received from user devices on each configured frequency resource for initial access. In various embodiments, the method 1500 includes transmitting 1508 a third message to the user device. The third message includes an indication to change a current frequency resource to another frequency resource for initial access. In some embodiments, the method 1500 includes receiving 1510 a fourth message from the user device on the another frequency resource for initial access.

[0104] In certain embodiments, the first message comprises information to select a frequency resource for initial access, and the information comprises a resource type, a device type, a signal strength threshold, a timer value, or some combination thereof. In some embodiments, the second message comprises a random access preamble received from a frequency resource in accordance with a random access configuration defined for the frequency resource. In various embodiments, the third message is transmitted using a physical layer control channel.

[0105] In one embodiment, transmitting the third message to the user device comprises transmitting the third message to a plurality of user devices. In certain embodiments, the fourth message comprises a random access preamble received from the another frequency resource in accordance with a random access configuration defined for this frequency resource.

[0106] Figure 16 is a flow chart diagram illustrating another embodiment of a method 1600 for configuring a frequency resource for initial access. In some embodiments, the method 1600 is performed by an apparatus, such as the remote unit 102. In certain embodiments, the method 1600 may be performed by a processor executing program code, for example, a microcontroller, a microprocessor, a CPU, a GPU, an auxiliary processing unit, a FPGA, or the like.

[0107] In various embodiments, the method 1600 includes receiving 1602, at a user device, a first message from a network device. The first message includes a configuration of multiple frequency resources for initial access. In some embodiments, the method 1600 includes selecting 1604 a frequency resource for initial access in accordance with the first message. In certain embodiments, the method 1600 includes transmitting 1606 a second message to the network device in accordance with the selected frequency resource for initial access.

[0108] In certain embodiments, the first message comprises information to select a frequency resource for initial access, and the information comprises a resource type, a device type, a signal strength threshold, a timer value, or some combination thereof. In some embodiments, the second message comprises a random access preamble in accordance a random access configuration defined for the selected frequency resource.

[0109] In one embodiment, an apparatus comprises a network device. The apparatus further comprises: a transmitter that transmits a first message to a user device, wherein the first message comprises a configuration of multiple frequency resources for initial access; a receiver that receives a second message from the user device in accordance with the configuration of the multiple frequency resources for initial access; and a processor that determines a number of messages received from user devices on each configured frequency resource for initial access, wherein the transmitter transmits a third message to the user device, the third message comprises an indication to change a current frequency resource to another frequency resource for initial access, and the receiver receives a fourth message from the user device on the another frequency resource for initial access.

[0110] In certain embodiments, the first message comprises information to select a frequency resource for initial access, and the information comprises a resource type, a device type, a signal strength threshold, a timer value, or some combination thereof.

[0111] In some embodiments, the second message comprises a random access preamble received from a frequency resource in accordance with a random access configuration defined for the frequency resource.

[0112] In various embodiments, the third message is transmitted using a physical layer control channel.

[0113] In one embodiment, the transmitter transmitting the third message to the user device comprises the transmitter transmitting the third message to a plurality of user devices.

[0114] In certain embodiments, the fourth message comprises a random access preamble received from the another frequency resource in accordance with a random access configuration defined for this frequency resource.

[0115] In one embodiment, a method of a network device comprises: transmitting a first message to a user device, wherein the first message comprises a configuration of multiple frequency resources for initial access; receiving a second message from the user device in accordance with the configuration of the multiple frequency resources for initial access; determining a number of messages received from user devices on each configured frequency resource for initial access; transmitting a third message to the user device, wherein the third message comprises an indication to change a current frequency resource to another frequency resource for initial access; and receiving a fourth message from the user device on the another frequency resource for initial access.

[0116] In certain embodiments, the first message comprises information to select a frequency resource for initial access, and the information comprises a resource type, a device type, a signal strength threshold, a timer value, or some combination thereof.

[0117] In some embodiments, the second message comprises a random access preamble received from a frequency resource in accordance with a random access configuration defined for the frequency resource. [0118] In various embodiments, the third message is transmitted using a physical layer control channel.

[0119] In one embodiment, transmitting the third message to the user device comprises transmitting the third message to a plurality of user devices.

[0120] In certain embodiments, the fourth message comprises a random access preamble received from the another frequency resource in accordance with a random access configuration defined for this frequency resource.

[0121] In one embodiment, an apparatus comprises a user device. The apparatus further comprises: a receiver that receives a first message from a network device, wherein the first message comprises a configuration of multiple frequency resources for initial access; a processor that selects a frequency resource for initial access in accordance with the first message; and a transmitter that transmits a second message to the network device in accordance with the selected frequency resource for initial access.

[0122] In certain embodiments, the first message comprises information to select a frequency resource for initial access, and the information comprises a resource type, a device type, a signal strength threshold, a timer value, or some combination thereof.

[0123] In some embodiments, the second message comprises a random access preamble in accordance a random access configuration defined for the selected frequency resource.

[0124] In one embodiment, a method of a user device comprises: receiving a first message from a network device, wherein the first message comprises a configuration of multiple frequency resources for initial access; selecting a frequency resource for initial access in accordance with the first message; and transmitting a second message to the network device in accordance with the selected frequency resource for initial access.

[0125] In certain embodiments, the first message comprises information to select a frequency resource for initial access, and the information comprises a resource type, a device type, a signal strength threshold, a timer value, or some combination thereof.

[0126] In some embodiments, the second message comprises a random access preamble in accordance a random access configuration defined for the selected frequency resource.

[0127] Embodiments may be practiced in other specific forms. The described embodiments are to be considered in all respects only as illustrative and not restrictive. The scope of the invention is, therefore, indicated by the appended claims rather than by the foregoing description. All changes which come within the meaning and range of equivalency of the claims are to be embraced within their scope.

Claims

1. An apparatus comprising a network device, the apparatus further comprising: a transmitter that transmits a first message to a user device, wherein the first message comprises a configuration of multiple frequency resources for initial access; a receiver that receives a second message from the user device in accordance with the configuration of the multiple frequency resources for initial access; and a processor that determines a number of messages received from user devices on each configured frequency resource for initial access, wherein the transmitter transmits a third message to the user device, the third message comprises an indication to change a current frequency resource to another frequency resource for initial access, and the receiver receives a fourth message from the user device on the another frequency resource for initial access.

2. The apparatus of claim 1, wherein the first message comprises information to select a frequency resource for initial access, and the information comprises a resource type, a device type, a signal strength threshold, a timer value, or some combination thereof.

3. The apparatus of claim 1, wherein the second message comprises a random access preamble received from a frequency resource in accordance with a random access configuration defined for the frequency resource.

4. The apparatus of claim 1, wherein the third message is transmitted using a physical layer control channel.

5. The apparatus of claim 1, wherein the transmitter transmitting the third message to the user device comprises the transmitter transmitting the third message to a plurality of user devices.

6. The apparatus of claim 1, wherein the fourth message comprises a random access preamble received from the another frequency resource in accordance with a random access configuration defined for this frequency resource.

7. A method of a network device, the method comprising: transmitting a first message to a user device, wherein the first message comprises a configuration of multiple frequency resources for initial access; receiving a second message from the user device in accordance with the configuration of the multiple frequency resources for initial access; determining a number of messages received from user devices on each configured frequency resource for initial access; transmitting a third message to the user device, wherein the third message comprises an indication to change a current frequency resource to another frequency resource for initial access; and receiving a fourth message from the user device on the another frequency resource for initial access.

8. The method of claim 7, wherein the first message comprises information to select a frequency resource for initial access, and the information comprises a resource type, a device type, a signal strength threshold, a timer value, or some combination thereof.

9. The method of claim 7, wherein the second message comprises a random access preamble received from a frequency resource in accordance with a random access configuration defined for the frequency resource.

10. The method of claim 7, wherein the third message is transmitted using a physical layer control channel.

11 The method of claim 7, wherein transmitting the third message to the user device comprises transmitting the third message to a plurality of user devices.

12. The method of claim 7, wherein the fourth message comprises a random access preamble received from the another frequency resource in accordance with a random access configuration defined for this frequency resource.

13. An apparatus comprising a user device, the apparatus further comprising: a receiver that receives a first message from a network device, wherein the first message comprises a configuration of multiple frequency resources for initial access; a processor that selects a frequency resource for initial access in accordance with the first message; and a transmitter that transmits a second message to the network device in accordance with the selected frequency resource for initial access.

14. The apparatus of claim 13, wherein the first message comprises information to select a frequency resource for initial access, and the information comprises a resource type, a device type, a signal strength threshold, a timer value, or some combination thereof.

15. The apparatus of claim 13, wherein the second message comprises a random access preamble in accordance a random access configuration defined for the selected frequency resource.