DL control resource set and rach procedure during initial access

Abstract

The present disclosure provides apparatuses, systems and methods for downlink control resource set and RACH procedure during initial access in wireless communications, for example, in 5G NR systems and beyond, including methods for CORESET#0 configuration, SSB / CORESET#0 multiplexing pattern 1 for hybrid SCS, time domain RO determination for 480kHz SCS / 960kHz SCS, and RA-RNTI determination for 480kHz SCS / 960kHz SCS.

Description

Technical Field

[0001] This invention relates to wireless communication, and more particularly to apparatus, systems, and methods for the downlink control resource set and random access channel (RACH) process during initial access in wireless communication, such as in 5G NR systems and later versions.

[0002] Related technical descriptions

[0003] The use of wireless communication systems is growing rapidly. In recent years, wireless devices such as smartphones and tablets have become increasingly sophisticated. In addition to supporting phone calls, many mobile devices now offer access to the internet, email, text messaging, and navigation using the Global Positioning System (GPS), and can operate complex applications that utilize these functions.

[0004] Long Term Evolution (LTE) is currently the technology of choice for most wireless network operators worldwide, providing mobile broadband data and high-speed internet access to their user base. LTE was first proposed in 2004 and first standardized in 2008. Since then, with the exponential growth in the use of wireless communication systems, the demand for wireless network operators has increased to support higher capacity for a higher density of mobile broadband users. Therefore, research into new radio access technologies began in 2015, and in 2017, the first version of 5G New Radio (5G NR) was standardized.

[0005] Compared to LTE, 5G-NR (also known as NR) offers higher capacity for higher density mobile broadband users, while also supporting ultra-reliable and massive machine-type communication between devices, as well as lower latency and / or lower battery consumption. Furthermore, NR allows for more flexible UE scheduling compared to current LTE. Therefore, efforts are underway to leverage the potentially higher throughput at higher frequencies in the ongoing development of 5G-NR. Summary of the Invention

[0006] The implementation scheme relates to wireless communication, and more specifically to apparatus, systems, and methods for downlink control resource sets and RACH procedures during initial access in wireless communication, such as in 5G NR systems and later versions.

[0007] For example, the implementation includes methods for CORESET#0 configuration, SSB / CORESET#0 multiplexing mode 1 with hybrid SCS, time-domain RO determination of 480kHz SCS / 960kHz SCS, and RA-RNTI determination of 480kHz SCS / 960kHz SCS. Therefore, the UE can configure and / or receive: a control resource set (CORESET) configuration based on a Type 0 physical downlink control channel (PDCCH) search space set supporting at least 96 physical resource blocks (PRBs) of one or more of 120kHz, 480kHz, or 960kHz subcarrier spacing (SCS), and resource block offsets based on one or more of synchronization gratings and component carrier gratings. The CORESET is configured by a data structure including one or more indexes.

[0008] For example, the UE may receive one or more SSB transmissions in a Synchronization Signal Block (SSB) burst window (SSBBW) based on configuration and resource block offset, and at least one of the following: a Type 0 PDCCH search space set in CORESET#0, or a Residual Minimum System Information (RMSI) paired with an SSB transmission in the same SSBBW. Furthermore, the UE may monitor a Type 0 Physical Downlink Control Channel (PDCCH) search space set in at least one of the RMSI slots paired with the SSB indexes of one or more SSB transmissions within the SSBBW.

[0009] As another example, the UE can determine the location of a Random Access Channel (RACH) Opportunity (RO) slot with a third SCS within the physical RACH (PRACH) slot of the reference subcarrier interval (SCS) based on a configuration index included in higher-layer parameters. Additionally, the UE can determine the distribution of ROs with the third SCS based on the total number of time-domain ROs within the PRACH slots of the reference SCS. This third SCS can be either a 480kHz SCS or a 960kHz SCS, which can be larger than the reference SCS of the PRACH slot.

[0010] As another example, the UE can receive the segment index of the corresponding RACH timing (RO) via a downlink control indicator (DCI) format 1_0 transmitted in the Scheduled Random Access Channel (RACH) Response (RAR). This segment index can be based at least in part on the subcarrier spacing (SCS). Additionally, the UE can determine the Random Access (RA) Radio Network Temporary Identifier (RNTI) based on the Physical Random Access Channel (PRACH) transmission window, which is divided into many time slot subgroups. It should be noted that the number of time slot subgroups can be based on the SCS of the RO, and the segment index can be determined accordingly.

[0011] The techniques described herein can be implemented in and / or used with a variety of different types of devices, including but not limited to any one of the following computing devices: unmanned aerial vehicles (UAVs), unmanned controllers (UACs), UTM servers, base stations, access points, cellular phones, tablet computers, wearable computing devices, portable media players, and various other computing devices.

[0012] The present invention is intended to provide a brief overview of some of the subjects described in this document. Therefore, it should be understood that the above features are merely illustrative and should not be construed as narrowing the scope or substance of the subjects described herein in any way. Other features, aspects, and advantages of the subjects described herein will become apparent from the following detailed description, drawings, and claims. Attached Figure Description

[0013] A better understanding of the subject matter can be obtained by considering the following detailed description of the various embodiments in conjunction with the accompanying drawings, in which:

[0014] Figure 1A An exemplary wireless communication system according to some implementation schemes is shown.

[0015] Figure 1B Examples of base stations and access points communicating with user equipment (UE) devices according to some implementation schemes are shown.

[0016] Figure 2 An exemplary block diagram of a base station according to some implementation schemes is shown.

[0017] Figure 3 An exemplary block diagram of a server according to some implementation schemes is shown.

[0018] Figure 4 An exemplary block diagram of a UE according to some implementation schemes is shown.

[0019] Figure 5 An example block diagram of a cellular communication circuit according to some implementation schemes is shown.

[0020] Figure 6A Examples of 5G network architectures according to some implementation schemes are shown, which combine 3GPP (e.g., cellular) and non-3GPP (e.g., non-cellular) access to 5G CN.

[0021] Figure 6B Examples of 5G network architectures according to some implementation schemes are shown, which combine dual 3GPP (e.g., LTE and 5G NR) access to 5G CN as well as non-3GPP access.

[0022] Figure 7 An example of a baseband processor architecture for a UE according to some implementation schemes is shown.

[0023] Figure 8 An example of a table is shown that defines a set of RBs and slot symbols for the CORESET used for the Type0-PDCCH search space set, according to some implementation schemes.

[0024] Figure 9 An example of a resource block offset according to some implementation schemes is shown.

[0025] Figure 10 Another example is shown, illustrating a table defining a set of RBs and slot symbols for the Type0-PDCCH search space set according to some implementation schemes.

[0026] Figure 11 and Figure 12 Examples of multiplexing modes that can be used to transmit CORESET#0 / RMSI with a large SCS, according to some implementation schemes, are shown.

[0027] Figure 13A and Figure 13B An example of time-domain RO determination according to some implementation schemes is shown.

[0028] Figure 14A Another example of time-domain RO determination based on some implementation schemes is shown.

[0029] Figure 14B An example table of scrambling sequences for time-domain RO determination is shown according to some implementation schemes.

[0030] Figure 15 An example of RA-RNTI determination based on some implementation schemes is shown.

[0031] Figures 16 to 19 An example block diagram of a method for configuring initial access communication according to some implementation schemes is shown.

[0032] While the features described herein may be subject to various modifications and alternatives, specific embodiments thereof are shown by way of example in the accompanying drawings and described in detail herein. However, it should be understood that the drawings and their detailed description are not intended to limit this document to the specific forms disclosed, but rather are intended to cover all modifications, equivalents, and alternatives falling within the substance and scope of the subject matter as defined by the appended claims. Detailed Implementation

[0033] acronym

[0034] Various acronyms are used throughout this disclosure. The definitions of the most prominent acronyms that may appear throughout this disclosure are as follows:

[0035] 3GPP: Third Generation Partnership Project

[0036] UE: User Equipment

[0037] RF: Radio Frequency

[0038] ·BS: Base Station

[0039] DL: Downlink

[0040] ·UL: Uplink

[0041] LTE: Long Term Evolution

[0042] NR: New Radio

[0043] •CBRS: Citizens' Broadband Radio Service

[0044] • DAS: Distributed Antenna System

[0045] ·5GS: 5G system

[0046] ·5GMM: 5GS Mobility Management

[0047] ·5GC / 5GCN: 5G Core Network

[0048] SIM: User Identity Recognition Module

[0049] eSIM: Embedded User Identity Module

[0050] ·IE: Information Elements

[0051] ·CE: Control element

[0052] MAC: Media Access Control

[0053] •SSB: Synchronization Signal Block

[0054] • CSI-RS: Channel State Information Reference Signal

[0055] • PDCCH: Physical Downlink Control Channel

[0056] • PDSCH: Physical Downlink Shared Channel

[0057] •RRC: Radio Resource Control

[0058] • RRM: Radio Resource Management

[0059] • CORESET: Control Resource Set

[0060] •TCI: Transport Configuration Indicator

[0061] • DCI: Downlink Control Indicator

[0062] the term

[0063] The following is a glossary of terms used in this disclosure:

[0064] Memory media—any device of any type of nontransitory memory device or storage device. The term "memory media" is intended to include mounting media such as CD-ROMs, floppy disks, or magnetic tape devices; computer system memory or random access memory such as DRAM, DDR RAM, SRAM, EDO RAM, Rambus RAM, etc.; non-volatile memory such as flash memory, magnetic media, e.g., hard disk drives or optical storage devices; registers or other similar types of memory elements, etc. Memory media may also include other types of nontransitory memory or combinations thereof. Furthermore, memory media may reside in a first computer system executing a program, or may reside in a different second computer system connected to the first computer system via a network such as the Internet. In the latter case, the second computer system may provide program instructions to the first computer for execution. The term "memory media" may include two or more memory media that may reside in different locations on different computer systems connected via a network, for example. Memory media may store program instructions (e.g., representing a computer program) that can be executed by one or more processors.

[0065] Carrier medium—the memory medium as described above, and physical transmission medium, such as buses, networks and / or other physical transmission media for transmitting signals (such as electrical signals, electromagnetic signals or digital signals).

[0066] Programmable hardware elements—including a variety of hardware devices comprising multiple programmable functional blocks connected via programmable interconnects. Examples include FPGAs (Field-Programmable Gate Arrays), PLDs (Programmable Logic Devices), FPOAs (Field-Programmable Object Arrays), and CPLDs (Complex PLDs). Programmable functional blocks can vary from fine-grained (combinatorial logic units or lookup tables) to coarse-grained (arithmetic logic units or processor cores). Programmable hardware elements may also be referred to as "configurable logic units."

[0067] Computer system (or computer) — any of the various types of computing or processing systems, including personal computer systems (PCs), mainframe computer systems, workstations, network appliances, internet-connected appliances, personal digital assistants (PDAs), television systems, grid computing systems, or other devices or combinations thereof. In general, the term "computer system" can be broadly defined to encompass any device (or combination of devices) having at least one processor that executes instructions from a memory medium.

[0068] User equipment (UE) (or “UE device”) — any of a variety of computer system devices that are mobile or portable and perform wireless communications. Examples of UE devices include mobile phones or smartphones (e.g., iPhone). TM Based on Android TM Telephones), portable gaming devices (e.g., Nintendo DS) TM PlayStation Portable TM Gameboy Advance TM iPhone TM Laptops, wearable devices (e.g., smartwatches, smart glasses), PDAs, portable internet devices, music players, data storage devices, other handheld devices, unmanned aerial vehicles (UAVs) (e.g., drones), UAV controllers (UACs), etc. Generally speaking, the term "UE" or "UE device" can be broadly defined as encompassing any electronic, computing, and / or telecommunications equipment (or combination of equipment) that is easily transportable by the user and capable of wireless communication.

[0069] Base station—The term “base station” has the full range of its common meaning and includes at least a wireless communication station that is installed in a fixed location and is used for communication as part of a wireless telephone system or radio system.

[0070] A processing element (or processor) is a component or combination of components capable of performing the functions of a device such as user equipment or cellular network equipment. A processing element may include, for example: a processor and associated memory, portions or circuitry of individual processor cores, an entire processor core, a processor array, circuitry such as an ASIC (Application-Specific Integrated Circuit), programmable hardware components such as a Field-Programmable Gate Array (FPGA), and any combination thereof.

[0071] A channel is a medium used to transmit information from a transmitter to a receiver. It should be noted that because the characteristics of the term "channel" can vary depending on different wireless protocols, the term "channel" as used herein can be considered to be used in a standard manner consistent with the type of device to which the term is referenced. In some standards, the channel width can be variable (e.g., depending on device capabilities, band conditions, etc.). For example, LTE can support scalable channel bandwidths from 1.4 MHz to 20 MHz. In contrast, WLAN channels can be 22 MHz wide, while Bluetooth channels can be 1 MHz wide. Other protocols and standards may include different definitions of channels. Furthermore, some standards may define and use multiple types of channels, such as different channels for uplink or downlink and / or different channels for different purposes such as data, control information, etc.

[0072] Frequency band—The term “frequency band” has the full range of its general meaning and includes at least a segment of spectrum (e.g., radio frequency spectrum) in which channels are used or reserved for the same purpose.

[0073] Wi-Fi—The term “Wi-Fi” (or WiFi) has the full range of its usual meaning and includes at least wireless communication networks or RATs that are provided by and through wireless LAN (WLAN) access points to provide connectivity to the Internet. Most modern Wi-Fi networks (or WLAN networks) are based on the IEEE 802.11 standard and are marketed under the name “Wi-Fi.” Wi-Fi (WLAN) networks are different from cellular networks.

[0074] 3GPP access refers to access technologies (e.g., radio access technologies) specified by 3GPP standards. These access technologies include, but are not limited to, GSM / GPRS, LTE, LTE-A, and / or 5G NR. Generally speaking, 3GPP access refers to various types of cellular access technologies.

[0075] Non-3GPP access refers to any access technology (e.g., radio access technologies) not specified by 3GPP standards. These accesses include, but are not limited to, WiMAX, CDMA2000, Wi-Fi, WLAN, and / or fixed networks. Non-3GPP access can be categorized into two types: "trusted" and "untrusted." Trusted non-3GPP access can interact directly with the Evolved Packet Core (EPC) and / or 5G Core (5GC), while untrusted non-3GPP access interoperates with the EPC / 5GC via network entities such as Evolved Packet Data Gateways and / or 5G NR Gateways. Generally speaking, non-3GPP access refers to various types of non-cellular access technologies.

[0076] Automatic—means an action or operation performed by a computer system (e.g., software executed by the computer system) or device (e.g., circuits, programmable hardware elements, ASICs, etc.) without requiring direct user input to specify or perform that action or operation. Therefore, the term "automatically" is the opposite of an operation performed or specified manually by a user, where the user provides input to directly perform the operation. An automatic process can be initiated by user-provided input, but the subsequent actions performed "automatically" are not specified by the user; that is, they are not performed "manually," where the user specifies each action to be performed. For example, a user filling out a form by selecting each field and providing input specifying information (e.g., by typing information, selecting a checkbox, radio selection, etc.) is considered manually filling out the form, even though the computer system must update the form in response to the user's actions. The form can be automatically filled out by a computer system (e.g., software executed on the computer system) which analyzes the fields of the form and fills it out without any user input specifying answers for the fields. As indicated above, the user can invoke the automatic filling of the form but does not participate in the actual filling of the form (e.g., the user does not manually specify answers for the fields, but they are completed automatically). This manual provides various examples of operations that are automatically performed in response to actions taken by the user.

[0077] Approximately—means a value close to the correct or precise value. For example, approximately can refer to a value within 1% to 10% of the precise (or expected) value. However, it should be noted that the actual threshold (or tolerance) can vary depending on the application. For example, in some implementations, “approximately” may mean within 0.1% of some specified or expected value, while in various other implementations, the threshold may be, for example, 2%, 3%, 5%, etc., depending on the expectations or requirements of the specific application.

[0078] Concurrency refers to the parallel execution or implementation of tasks, processes, or programs in a manner that at least partially overlaps. For example, concurrency can be achieved using “strong” or strict parallelism, where tasks are executed in parallel (at least partially) on corresponding computing elements; or using “weak parallelism,” where tasks are executed in an interleaved manner (e.g., by time multiplexing of execution threads).

[0079] Various components can be described as being "configured" to perform one or more tasks. In such contexts, "configured" is a broad expression generally meaning "having" a "structure" that performs one or more tasks during operation. Thus, a component can be configured to perform a task even when it is not currently performing one (e.g., a set of electrical conductors can be configured to electrically connect one module to another, even when the two modules are not connected). In some contexts, "configured" can also be a broad expression generally meaning a structure that "has" a "circuit" that performs one or more tasks during operation. Thus, a component can be configured to perform a task even when it is not currently switched on. Typically, the circuit forming the structure corresponding to "configured" can include hardware circuitry.

[0080] For ease of description, various components may be described as performing one or more tasks. Such descriptions should be interpreted as including the phrase "configured to". Statements describing a component as configured to perform one or more tasks are explicitly intended not to invoke the interpretation of 35 U.S.SC §112(f) for that component.

[0081] Figure 1A and 1B Communication system

[0082] Figure 1A A simplified exemplary wireless communication system according to some implementation schemes is shown. It should be noted that... Figure 1A The system described herein is merely one example of a possible system, and the features of this disclosure can be implemented in any of a variety of systems as needed.

[0083] As shown in the figure, the exemplary wireless communication system includes a base station 102A, which communicates with one or more user equipments 106A, 106B to 106N via a transmission medium. Each user equipment may be referred to herein as a "user equipment" (UE). Therefore, user equipment 106 is referred to as a UE or UE device.

[0084] Base station (BS) 102A may be a transceiver base station (BTS) or a cell site (“cellular base station”) and may include hardware that enables wireless communication with UE 106A to UE 106N.

[0085] The communication area (or coverage area) of a base station can be referred to as a "cell". Base station 102A and UE106 can be configured to communicate via a transmission medium using any of various Radio Access Technologies (RATs), also known as wireless communication technologies or telecommunications standards, such as GSM, UMTS (associated with air interfaces such as WCDMA or TD-SCDMA), LTE, LTE-A Advanced, 5G New Radio (5G NR), HSPA, 3GPP2 CDMA2000 (e.g., 1xRTT, 1xEV-DO, HRPD, eHRPD), etc. Note that if base station 102A is implemented in an LTE environment, its alternative location can be referred to as an "eNodeB" or "eNB". Note that if base station 102A is implemented in a 5G NR environment, its alternative location can be referred to as a "gNodeB" or "gNB".

[0086] As shown in the figure, base station 102A can also be configured to communicate with network 100 (e.g., in various possibilities, the core network of a cellular service provider, telecommunications networks such as the Public Switched Telephone Network (PSTN), and / or the Internet). Therefore, base station 102A can facilitate communication between user equipments and / or between user equipments and network 100. Specifically, cellular base station 102A can provide UE 106 with various communication capabilities such as voice, SMS, and / or data services.

[0087] Base station 102A and other similar base stations (such as base stations 102B...102N) operating according to the same or different cellular communication standards can therefore be provided as a network of cells that can provide continuous or nearly continuous overlapping services to UE 106A-N and similar devices over a geographical area via one or more cellular communication standards.

[0088] Therefore, although base station 102A can act as the "serving cell" for UEs 106A-N as shown in Figure 1, each UE 106 may also be able to receive signals (and possibly within its communication range) from one or more other cells (which may be provided by base stations 102B-N and / or any other base station), which may be referred to as "neighboring cells". Such cells may also facilitate communication between user equipments and / or between user equipments and network 100. Such cells may include "macro" cells, "micro" cells, "pecimen" cells, and / or any other cells of various other granularities providing service area size. For example, base stations 102A to 102B shown in Figure 1 may be macro cells, while base station 102N may be a pico cell. Other configurations are also possible.

[0089] In some implementations, base station 102A may be a next-generation base station, such as a 5G New Radio (5G NR) base station or a “gNB”. In some implementations, the gNB may be connected to a legacy evolved packet core (EPC) network and / or to an NR core (NRC) network. Furthermore, the gNB cell may include one or more transition and receive points (TRPs). Additionally, a UE capable of operating according to 5G NR may connect to one or more TRPs within one or more gNBs.

[0090] It should be noted that UE 106 can communicate using multiple wireless communication standards. For example, in addition to at least one cellular communication protocol (e.g., GSM, UMTS (associated with, for example, WCDMA or TD-SCDMA air interfaces), LTE, LTE-A, 5G NR, HSPA, 3GPP2CDMA2000 (e.g., 1xRTT, 1xEV-DO, HRPD, eHRPD, etc.), UE 106 can be configured to communicate using wireless networking (e.g., Wi-Fi) and / or peer-to-peer wireless communication protocols (e.g., Bluetooth, Wi-Fi peer-to-peer, etc.). If desired, UE 106 can also or alternatively be configured to communicate using one or more Global Navigation Satellite Systems (GNSS, such as GPS or GLONASS), one or more mobile television broadcasting standards (e.g., ATSC-M / H or DVB-H), and / or any other wireless communication protocol. Other combinations of wireless communication standards (including more than two wireless communication standards) are also possible.

[0091] Figure 1B User equipment 106 (e.g., one of devices 106A to 106N) communicating with base station 102 and access point 112 according to some embodiments is shown. UE 106 can be a device with cellular and non-cellular communication capabilities (e.g., Bluetooth, Wi-Fi, etc.), such as a mobile phone, handheld device, computer or tablet, or virtually any type of wireless device.

[0092] UE 106 may include a processor configured to execute program instructions stored in memory. UE 106 may execute any of the method embodiments of the present invention by executing such stored instructions. Alternatively or additionally, UE 106 may include programmable hardware elements, such as a field-programmable gate array (FPGA) configured to execute any of the method embodiments of the present invention or any portion thereof.

[0093] UE 106 may include one or more antennas for communicating using one or more wireless communication protocols or technologies. In some embodiments, UE 106 may be configured to communicate using, for example, CDMA2000 (1xRTT / 1xEV-DO / HRPD / eHRPD), LTE / Advanced LTE, or 5G NR and / or GSM, LTE, Advanced LTE, or 5G NR using a single shared radio component. The shared radio may be coupled to a single antenna or to multiple antennas (e.g., for MIMO) for performing wireless communication. Typically, the radio component may include any combination of baseband processor, analog radio frequency (RF) signal processing circuitry (e.g., including filters, mixers, oscillators, amplifiers, etc.) or digital processing circuitry (e.g., for digital modulation and other digital processing). Similarly, the radio component may use the aforementioned hardware to implement one or more receive chains and transmit chains. For example, UE 106 may share one or more portions of the receive chain and / or transmit chain among various wireless communication technologies such as those discussed above.

[0094] In some implementations, UE 106 may include separate transmit and / or receive chains (e.g., including separate antennas and other radio components) for each wireless communication protocol configured to communicate therewith. As another possibility, UE 106 may include one or more radio components shared among multiple wireless communication protocols, as well as one or more radio components uniquely used by a single wireless communication protocol. For example, UE 106 may include shared radio components for communication using either LTE or 5G NR (or LTE or 1xRTT, or LTE or GSM), and separate radio components for communication using each of Wi-Fi and Bluetooth. Other configurations are also possible.

[0095] Figure 2 Block diagram of a base station

[0096] Figure 2 An exemplary block diagram of a base station 102 according to some embodiments is shown. It should be noted that... Figure 3 The base station shown is merely one example of a possible base station. As illustrated, base station 102 may include a processor 204 capable of executing program instructions specific to base station 102. Processor 204 may also be coupled to memory management unit (MMU) 240 or other circuitry or devices, which may be configured to receive addresses from processor 204 and translate those addresses into locations in memory (e.g., memory 260 and read-only memory (ROM) 250).

[0097] Base station 102 may include at least one network port 270. Network port 270 may be configured to be coupled to a telephone network and provide access rights as described above in Figure 1 and... Figure 2 The telephone network as described herein includes multiple devices (such as UE device 106).

[0098] Network port 270 (or an additional network port) may also be configured, or alternatively configured, to be coupled to a cellular network, such as the core network of a cellular service provider. The core network may provide mobility-related services and / or other services to multiple devices, such as UE device 106. In some cases, network port 270 may be coupled to a telephone network via the core network, and / or the core network may provide a telephone network (e.g., in other UE devices served by the cellular service provider).

[0099] In some implementations, base station 102 may be a next-generation base station, such as a 5G New Radio (5G NR) base station, or a “gNB”. In such implementations, base station 102 may be connected to a legacy evolved packet core (EPC) network and / or to an NR core (NRC) network. Furthermore, base station 102 may be considered a 5G NR cell and may include one or more transition and receive points (TRPs). Additionally, UEs capable of operating according to 5G NR may connect to one or more TRPs within one or more gNBs.

[0100] Base station 102 may include at least one antenna 234 and possibly multiple antennas. The at least one antenna 234 may be configured to function as a wireless transceiver and may be further configured to communicate with UE device 106 via radio component 230. Antenna 234 communicates with radio component 230 via communication link 232. Communication link 232 may be a receive link, a transmit link, or both. Radio component 230 may be configured to communicate via various wireless communication standards, including but not limited to 5G NR, LTE, LTE-A, GSM, UMTS, CDMA2000, Wi-Fi, etc.

[0101] Base station 102 can be configured to perform wireless communication using multiple wireless communication standards. In some cases, base station 102 may include multiple radios that enable base station 102 to communicate according to multiple wireless communication technologies. For example, as one possibility, base station 102 may include an LTE radio component for performing communication according to LTE and a 5G NR radio component for performing communication according to 5G NR. In this case, base station 102 may be able to operate as both an LTE base station and a 5G NR base station. As another possibility, base station 102 may include a multimode radio component capable of performing communication according to any of multiple wireless communication technologies (e.g., 5G NR and Wi-Fi, LTE and Wi-Fi, LTE and UMTS, LTE and CDMA2000, UMTS and GSM, etc.).

[0102] As further described herein, base station 102 may include hardware and software components for implementing or supporting embodiments of the features described herein. The processor 204 of base station 102 may be configured to implement or support some or all of the methods described herein, for example, by executing program instructions stored on a memory medium (e.g., a non-transitory computer-readable memory medium). Alternatively, processor 204 may be configured as a programmable hardware element such as a FPGA (Field-Programmable Gate Array), or as an ASIC (Application-Specific Integrated Circuit), or a combination thereof. Alternatively (or in addition), in conjunction with one or more of other components 230, 232, 234, 240, 250, 260, 270, the processor 204 of base station 102 may be configured to implement or support some or all of the features described herein.

[0103] Furthermore, as described herein, processor 204 may comprise one or more processing elements. In other words, one or more processing elements may be included in processor 204. Therefore, processor 204 may include one or more integrated circuits (ICs) configured to perform the functions of processor 204. Additionally, each integrated circuit may include circuitry (e.g., a first circuit, a second circuit, etc.) configured to perform the functions of one or more processors 204.

[0104] Additionally, as described herein, the radio component 230 may comprise one or more processing elements. In other words, one or more processing elements may be included in the radio component 230. Therefore, the radio component 230 may include one or more integrated circuits (ICs) configured to perform the functions of the radio component 230. Furthermore, each integrated circuit may include circuitry (e.g., a first circuit, a second circuit, etc.) configured to perform the functions of the radio component 230.

[0105] Figure 3 Server block diagram

[0106] Figure 3 An exemplary block diagram of server 104 according to some implementation schemes is shown. It should be noted that... Figure 3 The server described is merely one example of a possible server. As shown, server 104 may include processor 344 capable of executing program instructions specific to server 104. Processor 344 may also be coupled to memory management unit (MMU) 374, which may be configured to receive addresses from processor 344 and translate those addresses into locations in memory (e.g., memory 364 and read-only memory (ROM) 354) or to other circuitry or devices.

[0107] Server 104 can be configured to provide network access functionality to multiple devices, such as base station 102, UE device 106, and / or UTM 108, for example, as further described herein.

[0108] In some implementations, server 104 may be part of a radio access network, such as a 5G New Radio (5G NR) access network. In some implementations, server 104 may be connected to a legacy evolved packet core (EPC) network and / or to an NR core (NRC) network.

[0109] As further described herein, server 104 may include hardware and software components for implementing or supporting the implementation of the features described herein. Processor 344 of server 104 may be configured, for example, to implement or support some or all of the methods described herein by executing program instructions stored on a storage medium (e.g., a non-transitory computer-readable storage medium). Alternatively, processor 344 may be configured as a programmable hardware element such as a FPGA (Field-Programmable Gate Array) or configured as an ASIC (Application-Specific Integrated Circuit) or a combination thereof. Alternatively (or in addition), in conjunction with one or more of other components 354, 364, and / or 374, processor 344 of server 104 may be configured to implement or support some or all of the features described herein.

[0110] Furthermore, as described herein, processor 344 may comprise one or more processing elements. In other words, one or more processing elements may be included in processor 344. Therefore, processor 344 may include one or more integrated circuits (ICs) configured to perform the functions of processor 344. Additionally, each integrated circuit may include circuitry (e.g., a first circuit, a second circuit, etc.) configured to perform the functions of processor 344.

[0111] Figure 4 : UE block diagram

[0112] Figure 4An exemplary simplified block diagram of a communication device 106 according to some embodiments is shown. It should be noted that... Figure 4 The block diagram of the communication device is merely one example of possible communication devices. According to the implementation, the communication device 106 may be a user equipment (UE) device, a mobile device or mobile station, a wireless device or wireless station, a desktop computer or computing device, a mobile computing device (e.g., a laptop, notebook, or portable computing device), a tablet computer, an unmanned aerial vehicle (UAV), a UAV controller (UAC), and / or a combination of devices, as well as other devices. As shown, the communication device 106 may include a set of components 400 configured to perform core functions. For example, this set of components may be implemented as a system-on-a-chip (SOC), which may include portions for various purposes. Alternatively, the set of components 400 may be implemented as individual components or groups of components for various purposes. This set of components 400 may be (e.g., communicatively; directly or indirectly) coupled to various other circuits of the communication device 106.

[0113] For example, communication device 106 may include various types of memory (e.g., including NAND flash memory 410), input / output interfaces such as connector I / F 420 (e.g., for connection to a computer system; docking station; charging station; input devices such as microphone, camera, keyboard; output devices such as speaker; etc.), a display 460 that may be integrated with or external to communication device 106, and cellular communication circuitry 430 such as for 5G NR, LTE, GSM, etc., and short- to medium-range wireless communication circuitry 429 (e.g., Bluetooth). TM (and WLAN circuitry). In some embodiments, the communication device 106 may include wired communication circuitry (not shown), such as, for example, a network interface card for Ethernet.

[0114] Cellular communication circuitry 430 may be coupled (e.g., communicatively grounded; directly or indirectly) to one or more antennas, such as antennas 435 and 436 shown. Short-to-medium-range wireless communication circuitry 429 may also be coupled (e.g., communicatively grounded; directly or indirectly) to one or more antennas, such as antennas 437 and 438 shown. Alternatively, short-to-medium-range wireless communication circuitry 429 may be coupled (e.g., communicatively grounded; directly or indirectly) to antennas 437 and 438, or as an alternative, to antennas 435 and 436. Short-to-medium-range wireless communication circuitry 429 and / or cellular communication circuitry 430 may include multiple receive chains and / or multiple transmit chains for receiving and / or transmitting multiple spatial streams, such as in a multiple-input multiple-output (MIMO) configuration.

[0115] In some embodiments, as further described below, the cellular communication circuit 430 may include dedicated receive chains for multiple RATs (including and / or coupled to (e.g., communication ground; directly or indirectly) dedicated processors and / or radio components) (e.g., a first receive chain for LTE and a second receive chain for 5G-NR). Furthermore, in some embodiments, the cellular communication circuit 430 may include a single transmit chain that can be switched between radio components dedicated to a particular RAT. For example, a first radio component may be dedicated to a first RAT, such as LTE, and can communicate with a dedicated receive chain and a transmit chain shared with additional radio components, such as a second radio component that may be dedicated to a second RAT (e.g., 5G NR) and can communicate with a dedicated receive chain and a shared transmit chain.

[0116] The communication device 106 may also include one or more user interface elements and / or be configured to be used with one or more user interface elements. User interface elements may include any of a variety of components such as a display 460 (which may be a touch screen display), a keyboard (which may be a separate keyboard or may be implemented as part of the touch screen display), a mouse, a microphone and / or a speaker, one or more cameras, one or more buttons, and / or any of a variety of other components capable of providing information to the user and / or receiving or interpreting user input.

[0117] The communication device 106 may also include one or more smart cards 445 with SIM (Subscriber Identity Module) functionality, such as one or more UICC cards (one or more general-purpose integrated circuit cards) 445. It should be noted that the term "SIM" or "SIM entity" is intended to include any of various types of SIM implementations or SIM functions, such as one or more UICC cards 445, one or more eUICCs, one or more eSIMs, removable or embedded, etc. In some embodiments, the UE 106 may include at least two SIMs. Each SIM may execute one or more SIM applications and / or otherwise implement SIM functionality. Thus, each SIM may be a single smart card that can be embedded, for example, soldered to a circuit board in the UE 106, or each SIM 410 may be implemented as a removable smart card. Thus, a SIM may be one or more removable smart cards (such as UICC cards, sometimes referred to as "SIM cards"), and / or SIM 410 may be one or more embedded cards (such as embedded UICCs (eUICCs), sometimes referred to as "eSIMs" or "eSIM cards"). In some implementations (such as when the SIM includes an eUICC), one or more SIMs within the SIM can implement embedded SIM (eSIM) functionality; in such implementations, a single SIM within the SIM can execute multiple SIM applications. Each SIM may include components such as a processor and / or memory; instructions for performing SIM / eSIM functionality may be stored in memory and executed by the processor. In some implementations, UE 106 may include, as needed, a combination of removable smart cards and fixed / non-removable smart cards (such as one or more eUICC cards implementing eSIM functionality). For example, UE 106 may include two embedded SIMs, two removable SIMs, or a combination of one embedded SIM and one removable SIM. Various other SIM configurations are also envisioned.

[0118] As described above, in some implementations, UE 106 may include two or more SIMs. Including two or more SIMs in UE 106 allows UE 106 to support two different phone numbers and allows UE 106 to communicate on two or more corresponding networks. For example, the first SIM may support a first RAT such as LTE, and the second SIM 106 may support a second RAT such as 5G NR. Other implementations and RATs are also possible. In some implementations, when UE 106 includes two SIMs, UE 106 may support Dual SIM Dual Standby (DSDA) functionality. DSDA functionality allows UE 106 to connect to two networks simultaneously (and use two different RATs), or allows two connections supported by two different SIMs using the same or different RATs to be maintained simultaneously on the same or different networks. DSDA functionality also allows UE 106 to receive voice calls or data traffic simultaneously on either phone number. In some implementations, voice calls may be packet-switched communications. In other words, voice calls can be received using LTE-based Voice (VoLTE) technology and / or NR-based Voice (VoNR) technology. In some implementations, UE 106 may support Dual SIM Dual Standby (DSDS) functionality. DSDS functionality allows either of the two SIMs in UE 106 to remain in standby while awaiting a voice call and / or data connection. In DSDS, when a call / data connection is established on one SIM, the other SIM is no longer active. In some implementations, DSDx functionality (DSDA or DSDS functionality) can be implemented using a single SIM (e.g., eUICC) that performs multiple SIM applications for different carriers and / or RATs.

[0119] As shown in the figure, the SOC 400 may include a processor 402 and a display circuit 404. The processor executes program instructions for the communication device 106, and the display circuit performs graphics processing and provides display signals to the display 460. The processor 402 may also be coupled to a memory management unit (MMU) 440 (which may be configured to receive addresses from the processor 402 and translate those addresses into locations in memory (e.g., memory 406, read-only memory (ROM) 450, NAND flash memory 410)) and / or coupled to other circuitry or devices (such as the display circuit 404, short-to-medium range wireless communication circuitry 429, cellular communication circuitry 430, connector I / F 420, and / or display 460). The MMU 440 may be configured to perform memory protection and page table translation or setup. In some embodiments, the MMU 440 may be included as part of the processor 402.

[0120] As described above, communication device 106 can be configured to communicate using wireless and / or wired communication circuits. Communication device 106 can be configured to perform methods for revoking and / or modifying user consent in the MEC, for example, in 5G NR systems and later, as further described herein. For example, communication device 106 can be configured to perform methods for CORESET#0 configuration, SSB / CORESET#0 multiplexing mode 1 of hybrid SCS, time-domain RO determination of 480kHz SCS / 960kHz SCS, and RA-RNTI determination of 480kHz SCS / 960kHz SCS.

[0121] As described herein, communication device 106 may include hardware and software components for implementing the features described above to transmit a scheduling profile for power saving to a network. For example, by executing program instructions stored on a memory medium (e.g., a non-transitory computer-readable storage medium), processor 402 of communication device 106 may be configured to implement some or all of the features described herein. Alternatively (or in addition), processor 402 may be configured as a programmable hardware element, such as an FPGA (Field-Programmable Gate Array) or an ASIC (Application-Specific Integrated Circuit). Alternatively (or in addition), in conjunction with one or more of other components 400, 404, 406, 410, 420, 429, 430, 440, 445, 450, 460, processor 402 of communication device 106 may be configured to implement some or all of the features described herein.

[0122] Furthermore, as described in this invention, processor 402 may include one or more processing elements. Therefore, processor 402 may include one or more integrated circuits (ICs) configured to perform the functions of processor 402. Additionally, each integrated circuit may include circuitry (e.g., a first circuit, a second circuit, etc.) configured to perform the functions of processor 402.

[0123] Furthermore, as described herein, the cellular communication circuit 430 and the short-to-medium-range wireless communication circuit 429 may each include one or more processing elements. In other words, one or more processing elements may be included in the cellular communication circuit 430, and similarly, one or more processing elements may be included in the short-to-medium-range wireless communication circuit 429. Therefore, the cellular communication circuit 430 may include one or more integrated circuits (ICs) configured to perform the functions of the cellular communication circuit 430. Furthermore, each integrated circuit may include circuitry (e.g., a first circuit, a second circuit, etc.) configured to perform the functions of the cellular communication circuit 430. Similarly, the short-to-medium-range wireless communication circuit 429 may include one or more ICs configured to perform the functions of the short-to-medium-range wireless communication circuit 429. Furthermore, each integrated circuit may include circuitry (e.g., a first circuit, a second circuit, etc.) configured to perform the functions of the short-to-medium-range wireless communication circuit 429.

[0124] Figure 5 Block diagram of cellular communication circuit

[0125] Figure 5 An exemplary simplified block diagram of a cellular communication circuit according to some embodiments is shown. It should be noted that... Figure 5 The block diagram of the cellular communication circuit is merely one example of a possible cellular communication circuit. According to the implementation, the cellular communication circuit 530 (which may be the cellular communication circuit 430) may be included in a communication device such as the communication device 106 described above. As mentioned above, among other devices, the communication device 106 may be a user equipment (UE) device, a mobile device or mobile station, a wireless device or wireless station, a desktop computer or computing device, a mobile computing device (e.g., a laptop, notebook, or portable computing device), a tablet computer, and / or a combination of these devices.

[0126] Cellular communication circuit 530 may (e.g., communicatively; directly or indirectly) be coupled to one or more antennas, such as ( Figure 4 Antennas 435a-435b and 436 are shown in the diagram. In some embodiments, the cellular communication circuitry 530 may include dedicated receive chains for multiple RATs (including and / or coupled to (e.g., communication ground; directly or indirectly) dedicated processors and / or radio components) (e.g., a first receive chain for LTE and a second receive chain for 5G-NR). For example, as... Figure 5 As shown, the cellular communication circuit 530 may include a modem 510 and a modem 520. The modem 510 may be configured for communication according to a first RAT, such as LTE or LTE-A, and the modem 520 may be configured for communication according to a second RAT, such as 5G NR.

[0127] As shown, modem 510 may include one or more processors 512 and memory 516 communicating with processors 512. Modem 510 may communicate with radio frequency (RF) front end 530. RF front end 530 may include circuitry for transmitting and receiving radio signals. For example, RF front end 530 may include receiver circuitry (RX) 532 and transmitter circuitry (TX) 534. In some embodiments, receiver circuitry 532 may communicate with downlink (DL) front end 550, which may include circuitry for receiving radio signals via antenna 335a.

[0128] Similarly, modem 520 may include one or more processors 522 and memory 526 communicating with processor 522. Modem 520 may communicate with RF front end 540. RF front end 540 may include circuitry for transmitting and receiving radio signals. For example, RF front end 540 may include receiving circuitry 542 and transmitting circuitry 544. In some embodiments, receiving circuitry 542 may communicate with DL front end 560, which may include circuitry for receiving radio signals via antenna 335b.

[0129] In some implementations, switch 570 may couple transmitting circuitry 534 to uplink (UL) front-end 572. Additionally, switch 570 may couple transmitting circuitry 544 to UL front-end 572. UL front-end 572 may include circuitry for transmitting radio signals via antenna 336. Therefore, when cellular communication circuitry 530 receives an instruction to transmit according to a first RAT (e.g., supported by modem 510), switch 570 may be switched to a first state allowing modem 510 to transmit signals according to the first RAT (e.g., via a transmission chain including transmitting circuitry 534 and UL front-end 572). Similarly, when cellular communication circuitry 530 receives an instruction to transmit according to a second RAT (e.g., supported by modem 520), switch 570 may be switched to a second state allowing modem 520 to transmit signals according to the second RAT (e.g., via a transmission chain including transmitting circuitry 544 and UL front-end 572).

[0130] In some implementations, cellular communication circuitry 530 may be configured to perform methods for downlink control resource set and RACH procedures during initial access in wireless communication, such as in 5G NR systems and later versions, as further described herein. For example, cellular communication circuitry 530 may be configured to perform methods for CORESET#0 configuration, SSB / CORESET#0 multiplexing mode 1 of hybrid SCS, time-domain RO determination of 480kHz SCS / 960kHz SCS, and RA-RNTI determination of 480kHz SCS / 960kHz SCS.

[0131] As described herein, modem 510 may include hardware and software components for implementing the features described above or for UL data used in time-division multiplexing NSA NR operation, as well as various other techniques described herein. For example, processor 512 may be configured to implement some or all of the features described herein by executing program instructions stored on a memory medium (e.g., a non-transitory computer-readable storage medium). Alternatively (or otherwise), processor 512 may be configured as a programmable hardware element such as a FPGA (Field-Programmable Gate Array) or as an ASIC (Application-Specific Integrated Circuit). Alternatively (or otherwise), processor 512 may be configured to implement some or all of the features described herein by combining with one or more of other components 530, 532, 534, 550, 570, 572, 335, and 336.

[0132] Furthermore, as described herein, processor 512 may include one or more processing elements. Therefore, processor 512 may include one or more integrated circuits (ICs) configured to perform the functions of processor 512. Additionally, each integrated circuit may include circuitry (e.g., a first circuit, a second circuit, etc.) configured to perform the functions of processor 512.

[0133] As described herein, modem 520 may include hardware and software components designed to implement the aforementioned features for transmitting power-saving scheduling profiles to the network, as well as various other technologies described herein. For example, processor 522 may be configured to implement some or all of the features described herein by executing program instructions stored on a memory medium (e.g., a non-transitory computer-readable storage medium). Alternatively (or otherwise), processor 522 may be configured as a programmable hardware element such as a FPGA (Field-Programmable Gate Array) or as an ASIC (Application-Specific Integrated Circuit). Alternatively (or additionally), processor 522 may be configured to implement some or all of the features described herein by combining one or more of other components 540, 542, 544, 550, 570, 572, 335, and 336.

[0134] Furthermore, as described herein, processor 522 may include one or more processing elements. Therefore, processor 522 may include one or more integrated circuits (ICs) configured to perform the functions of processor 522. Additionally, each integrated circuit may include circuitry (e.g., a first circuit, a second circuit, etc.) configured to perform the functions of processor 522.

[0135] Figure 6A , Figure 6B and Figure 7 5G Core Network Architecture—Interoperability with Wi-Fi

[0136] In some implementations, access to the 5G core network (CN) can be made via (or through) cellular connections / interfaces (e.g., via 3GPP communication architectures / protocols) and non-cellular connections / interfaces (e.g., non-3GPP access architectures / protocols such as Wi-Fi connections). Figure 6A An example of a 5G network architecture according to some implementation schemes is shown, which combines 3GPP (e.g., cellular) and non-3GPP (e.g., non-cellular) access to the 5G CN. As shown, a user equipment device (e.g., such as UE 106) can access the 5G CN via both a radio access network (RAN, such as gNB 604, which may be base station 102) and an access point (such as AP 612). AP 612 may include a connection to the Internet 600 and a connection to a non-3GPP Interoperability Function (N3IWF) 603 network entity. N3IWF may include a connection to the core access and mobility management function (AMF) 605 of the 5G CN. AMF 605 may include an instance of 5G mobility management (5G MM) functions associated with UE 106. In addition, the RAN (e.g., gNB 604) may also have a connection to AMF 605. Therefore, the 5G CN can support unified authentication on both connections and allow UE 106 to register for access simultaneously via gNB 604 and AP 612. As shown, AMF 605 may include one or more functional entities associated with the 5G CN (e.g., Network Slice Selection Function (NSSF) 620, Short Message Service Function (SMSF) 622, Application Function (AF) 624, Unified Data Management (UDM) 626, Policy Control Function (PCF) 628, and / or Authentication Server Function (AUSF) 630). It should be noted that these functional entities can also be supported via the 5G CN's Session Management Functions (SMF) 606a and SMF 606b. AMF 605 can connect to (or communicate with) SMF 606a. Furthermore, gNB 604 can communicate with (or connect to) User Plane Function (UPF) 608a, which can also communicate with SMF 606a. Similarly, the N3IWF 603 can communicate with the UPF 608b, which in turn can communicate with the SMF 606b. Both UPFs can communicate with data networks (e.g., DN 610a and 610b) and / or the Internet 600 and the Internet Protocol (IP) Multimedia Subsystem / IP Multimedia Core Network Subsystem (IMS) Core Network 610.

[0137] Figure 6BAn example of a 5G network architecture according to some implementation schemes is shown, which combines dual 3GPP (e.g., LTE and 5G NR) access to the 5G CN as well as non-3GPP access. As shown, a user equipment device (e.g., such as UE 106) can access the 5G CN via both a radio access network (RAN, such as gNB 604 or eNB 602, which may be base station 102) and an access point (such as AP 612). AP 612 may include a connection to the Internet 600 and a connection to the N3IWF 603 network entity. N3IWF may include a connection to the AMF 605 of the 5G CN. AMF 605 may include an instance of 5G MM functionality associated with UE 106. In addition, the RAN (e.g., gNB 604) may also have a connection to AMF 605. Therefore, the 5G CN can support unified authentication on both connections and allow UE 106 to register access simultaneously via gNB 604 and AP 612. Additionally, the 5G CN can support dual registration of the UE on both a legacy network (e.g., LTE via eNB 602) and a 5G network (e.g., via gNB 604). As shown, eNB 602 may have connections to both Mobility Management Entity (MME) 642 and Service Gateway (SGW) 644. MME 642 may have connections to both SGW 644 and AMF 605. Furthermore, SGW 644 may have connections to both SMF 606a and UPF 608a. As shown, AMF 605 may include one or more functional entities associated with the 5G CN (e.g., NSSF 620, SMSF 622, AF 624, UDM 626, PCF 628, and / or AUSF 630). Note that UDM 626 may also include Home Subscriber Server (HSS) functionality, and PCF may also include Policy and Charging Rules (PCRF) functionality. It should also be noted that these functional entities can also be supported by the 5G CN's SMF 606a and SMF 606b. The AMF 606 can connect to (or communicate with) the SMF 606a. Furthermore, the gNB 604 can communicate with (or connect to) the UPF 608a, which in turn can communicate with the SMF 606a. Similarly, the N3IWF 603 can communicate with the UPF 608b, which in turn can communicate with the SMF 606b. Both UPFs can communicate with data networks (e.g., DN 610a and 610b) and / or the Internet 600 and the IMS core network 610.

[0138] It should be noted that, in various implementations, one or more of the network entities described above may be configured to perform methods for improving security checks in 5G NR networks, including mechanisms used in wireless communications, such as during initial access in 5G NR systems and later versions, for downlink control resource sets and RACH procedures, as further described herein. For example, one or more of the network entities described above may be configured to perform methods for CORESET#0 configuration, SSB / CORESET#0 multiplexing mode 1 of hybrid SCS, time-domain RO determination of 480kHz SCS / 960kHz SCS, and RA-RNTI determination of 480kHz SCS / 960kHz SCS.

[0139] Figure 7 An example of a baseband processor architecture for a UE (e.g., such as UE 106) according to some implementation schemes is shown. Figure 7 The baseband processor architecture 700 described herein may be implemented on one or more radio components (e.g., radio components 429 and / or 430) or modems (e.g., modems 510 and / or 520) as described above. As shown, the non-access stratum (NAS) 710 may include a 5G NAS 720 and a traditional NAS 750. The traditional NAS 750 may include a communication connection with a traditional access stratum (AS) 770. The 5G NAS 720 may include communication connections with a 5G AS 740 and a non-3GPP AS 730, as well as a Wi-Fi AS 732. The 5G NAS 720 may include functional entities associated with both access strata. Therefore, the 5G NAS 720 may include multiple 5G MM entities 726 and 728 and 5G session management (SM) entities 722 and 724. The traditional NAS 750 may include functional entities such as Short Message Service (SMS) entity 752, Evolved Packet System (EPS) Session Management (ESM) entity 754, Session Management (SM) entity 756, EPS Mobility Management (EMM) entity 758, and Mobility Management (MM) / GPRS Mobility Management (GMM) entity 760. Furthermore, the traditional AS 770 may include functional entities such as LTE AS 772, UMTS AS 774, and / or GSM / GPRS AS 776.

[0140] Therefore, the baseband processor architecture 700 allows for a common 5G-NAS for both 5G cellular and non-cellular (e.g., non-3GPP access) networks. It's important to note that, as shown in the figure, the 5G MM can maintain separate connection management and registration management state machines for each connection. Furthermore, a device (e.g., UE 106) can register to a single PLMN (e.g., a 5G CN) using both 5G cellular and non-cellular access. Additionally, a device can be in a connected state in one access and an idle state in another, or vice versa. Finally, there may be common 5G-MM procedures (e.g., registration, deregistration, identification, authentication, etc.) for both accesses.

[0141] It should be noted that, in various implementations, one or more of the aforementioned functional entities of the 5G NAS and / or 5G AS may be configured to perform methods for downlink control resource set and RACH procedures during initial access in wireless communication, such as in 5G NR systems and later versions, for example, as further described herein. For example, one or more of the aforementioned functional entities may be configured to perform methods for CORESET#0 configuration, SSB / CORESET#0 multiplexing mode 1 of hybrid SCS, time-domain RO determination of 480kHz SCS / 960kHz SCS, and RA-RNTI determination of 480kHz SCS / 960kHz SCS.

[0142] Downlink Control Resource Set and RACH Procedure during Initial Access

[0143] In the current implementation, considering both licensed and unlicensed operation, cellular systems, such as 5G NR systems, can be configured to operate at higher frequency bands, such as frequencies up to 71 GHz. Additionally, the initial access channel (e.g., the synchronization signal block (SSB)) supports up to 64 SSB beams in the initial bandwidth portion (BWP) for both licensed and unlicensed operation, and a 120 kHz subcarrier spacing (SCS) for initial access-related signals / channels. Furthermore, relative to the physical random access channel (PRACH) configuration, and to accommodate operation at higher frequencies, SCS of 480 kHz and 960 kHz, and a minimum PRACH configuration period of 10 ms have been specified.

[0144] However, remaining issues regarding operation at higher frequencies and support for new SCS options include how to determine the bandwidth of CORESET#0, especially considering the associated coverage performance of System Information Block (SIB) 1 PDCCH and PDSCH transmissions. Another issue is how to support mixed digital schemes between SSBs, for example, between 120kHz SCS and 480kHz SCS Type 0-PDCCH / SIB1 transmissions, or for some operators' preferred multiplexing mode 1, such as (SSB, Type-1 PDCCH) = (120kHz SCS, 480kHz SCS / 960kHz SCS) with multiplexing mode 1. Yet another issue is how to determine the RACH timing (RO) for the 480kHz SCS and / or 960kHz SCS. Furthermore, increasing the SCS from frequencies greater than 52.6 GHz or higher to 480 kHz and / or 960 kHz can lead to a shortage of Random Access (RA) Radio Network Temporary Identifiers (RNTIs), for example, exceeding the 16-bit width of the RA-RNTI in current systems, which is a function of the time and frequency of the PRACH timing of the preamble according to equation [1].

[0145] RA-RNTI=1+s id +14(t id +80(f id +8ul_carrier id )) [1]

[0146] It should be noted that in equation [1], s id It is the index of the first orthogonal frequency division multiplexing (OFDM) symbol of the PRACH, t id It is the index of the first slot of the specified PRACH in the system frame, f id It is the index of the specified PRACH in the frequency domain, and ul_carrier id This is the uplink carrier used for Msg 1 transmission. Note that s id It is a value ranging from 0 to less than 14, t id It is a value ranging from 0 to less than 80, f id It is a value ranging from 0 to less than 8, and ul_carrier id The value is 0 for Normal Uplink (NUL) carriers and 1 for Supplemental Uplink (SUL) carriers.

[0147] The embodiments described herein provide systems, methods, and mechanisms to support downlink control resource sets and RACH procedures during initial access in wireless communications. For example, embodiments may include systems, methods, and mechanisms for CORESET#0 configuration, SSB / CORESET#0 multiplexing mode 1 for hybrid SCS, time-domain RO determination for 480kHz SCS / 960kHz SCS, and RA-RNTI determination for 480kHz SCS / 960kHz SCS. For example, the embodiments described herein allow the UE and network to address the aforementioned issues by implementing support for extended resource blocks for CORESET#0 and addressing for scheduling support for higher SCS (e.g., for 480kHz SCS / 960kHz SCS). Furthermore, the embodiments allow the UE to determine the bandwidth of CORESET#0 and allow the UE to support hybrid digital schemes between SSBs, for example, between 120kHz SCS and 480kHz SCSType0-PDCCH / SIB1 transmission or multiplexing mode 1. Furthermore, the implementation allows the UE to determine the ROs for the 480kHz SCS and / or 960kHz SCS and avoid RA-RNTI shortages. For example, for one or more of the 120kHz SCS, 480kHz SCS, and / or 960kHz SCS, the number of resource blocks (RBs) used for SIB-1 transmissions supported by CORESET#0 can be expanded from 24 physical RBs (PRBs) or 48 PRBs to 96 PRBs. It should be noted that in addition to the increase in supported PRBs, larger aggregation levels (e.g., such as AL-16) can also be supported for PDCCH transmissions to extend PDCCH coverage. Figure 8 As shown, when the {SS / PBCH block, PDCCH}SCS is defined as {120, 120} kHz, the existing table defining a set of RBs and slot symbols for the CORESET used for the Type 0-PDCCH search space set can be modified to include 96 PRBs with one or two symbols. Therefore, as... Figure 8 As shown, index 8 can correspond to SSB and CORESET multiplexing mode 1 with an offset of 96 PRBs, 1 symbol, and 38 RBs. Additionally, index 9 can correspond to SSB and CORESET multiplexing mode 1 with an offset of 96 PRBs, 2 symbols, and 38 RBs.

[0148] For example, a set of RB offset values ​​can be defined for the 120kHz SCS, 240kHz SCS, and 480kHz SCS based on a synchronization grating (e.g., a Global Synchronization Channel Number (GSCN)) and / or a component carrier (CC) grating (e.g., an Absolute Radio Frequency Channel Number (ARFCN)), such that the SSB is positioned closer to the edge of the CC, for example, as... Figure 9 As shown in the figure, the RB offset (e.g., N) can be defined based on the synchronization grating (e.g., GSCN). RB This allows for the allocation of RBs closer to the edge of the CC for SIB-1 transmissions. Furthermore, subcarrier alignment of SSB gratings and channel grating points can be achieved. It should be noted that this design maximizes the number of available resource elements (REs) for SIB-1, considering that SIB-1 can be scheduled using DCI format 1_0 with continuous resource allocation in the frequency domain. Additionally, a set of common RB offsets can be applied to all SSB SCSs, for example, to 120kHz, 240kHz, 480kHz, and / or 960kHz SCSs. Therefore, as... Figure 10 As shown, a set of resource blocks and the slot symbols of the CORESET used for the Type0-PDCCH search space set may include RB offsets of 0, 1, 2, or 4 RBs and / or subsets of these values, such as 0, 2, or 1, 4. Therefore, Figure 10 The index values ​​in the table shown can be used to indicate offsets.

[0149] As another example, time-domain multiplexing can be used to transmit CORESET#0 / RMSI with a larger SCS (e.g., 480kHz and / or 960kHz) in time slots not used for SSB transmissions with a smaller SCS (e.g., 120kHz). This multiplexing mode reduces the latency for acquiring the Remaining Minimum System Information (RMSI) by using a larger SCS and a relatively short time slot duration, making it possible to multiplex the RMSI into the gaps between SSB bursts. Additionally, this multiplexing mode allows operators to use a single, higher digital scheme (e.g., 960kHz) SCS for all channels (e.g., including CORESET#0, RMSI on PDSCH, CSI-RS, and / or CORESET on unicast PDCCH / PDSCH) besides the SSB. Figure 11 and Figure 12 This further illustrates this reuse pattern.

[0150] like Figure 11As shown, an SSB burst window (SSBW), such as SSBW 1110, may include a first M consecutive SSB slots, such as SSB slot 1120, where M equals 4, followed by a second N consecutive CORESET0 / RMSI slots, such as CORESET0 / RMSI slot 1130, where N equals 8. It should be noted that an SSB slot may have a first SCS, such as u1, and includes two SSB transmissions. It should also be noted that the CORESET0 / RMSI slot may be a second SCS, such as u2, and may be reserved for CORESET0 / RMSI transmissions that have a one-to-one association (or correspondence) with SSBs transmitted in SSB slots having the same SSBW. In some embodiments, it may be...<u1,u2> Different combinations specify<M,N> The correct value. For example, rereference. Figure 11 ,when<u1,u2> When the value is <3,5>,<M,N> It can be <4,8>. For example, when...<u1,u2> When the value is <3,6>,<M,N> It can be <4,16>.

[0151] In some implementations, the association between CORESET0 / RMSI and SSB within an SSBW can be defined at least in part based on the SSB's SCS. For example, for an SSB with a 120kHz SCS, the first symbol of a candidate synchronization signal (SS) / physical broadcast channel (PBCH) block may have an index {4,8,16,20}+28n, where n may be equal to 0, 1, 3, 5, 6, 7, 8, 10, 11, 12, 13, 15, 16, 17, 18, and n may be defined as having a 120kHz SCS. As another example, for a CORESET0 / RMSI with a 480kHz SCS and / or 960kHz SCS, the UE may monitor the PDCCH in the Type 0-PDCCH CSS set in slot n0 that can be associated with an SSB having an index i. In some implementations, n0 may be defined as... For u2 equal to 5, M can be equal to 1 / 2, and for u2 equal to 6, M can be equal to 1. Note that the slots of CORESET0 / RMSI using SCS u2 can be indexed starting from n0 = 0 for each SSBBW. Furthermore, if M = 1 / 2, the first symbolic index of the Type0-PDCCH CSS set for SSB index i is represented as k. i If i is even, then k i It can be 0, and if i is odd, then k i It can be 7. Additionally, if M = 1, then k i It can be 0.

[0152] Figure 12It shows when<u1,u2> Example of SSB and CORESET0 / RMSI multiplexing with different SCS when <3,6>. As shown in the figure, a CORESET0 / RMSI associated with an SSB transmitted in SSB slot 1220 with u1=3 in SSBW 1210 can be transmitted in CORESET#0 / RMSI slot 1230 using SCS u2=6. Therefore, as described above, the UE can monitor the PDCCH in the Type0-PDCCH CSS set associated with SSB#6 / #15 in CORESET0 / RMSI slot index #6 / #15 respectively.

[0153] In some implementations, the density of PRACH can be at least the same as that in FR2 (e.g., the number of PRACH slots per reference slot). Furthermore, a Δf value in the reference slot can be determined. RA The starting position of the RACH timing (Ro) ∈ {480, 960} kHz. In some implementations, a reference SCS of 60 kHz or 120 kHz can be used to define the reference slot. For example, the RO can be the slot distribution across each PRACH slot of the reference SCS. In this case, the UE can determine the valid PRACH slots with the reference SCS (e.g., 60 kHz SCS or 120 kHz SCS) based on the PRACH configuration index in Table 6.3.3.2-4 given by the higher-layer parameter prach-ConfigurationIndex. Then, the UE can determine the RACH slots with Δf RA A slot index ∈ {480, 960} kHz, where the effective PRACH slots have a reference SCS. In some cases, the number of slots with SCS u = 5 or 6 in PRACH slots with reference SCS u0 = 2 or 3 can be expressed as: For example, for u = 5 (480 kHz), and For example, for u = 6 (960kHz), and Furthermore, the number of time-domain ROs within the reference time slot can be represented as N. Then, when At this time, N ROs can be uniformly distributed across the last N time slots in the reference PRACH time slots, where each time slot has each RO and uses the same start symbol configured by the higher layers for each time slot. Furthermore, when At that time, RO can be uniformly distributed throughout the reference time slot. In terms of time slots. Furthermore, M1 can be defined as... K1 can be defined as K2 can be defined as Then, if M1 > 0, there can be M1 time slots with K1 ROs. Furthermore, the (M-M1) time slots within the reference time slot can include K2 for each time slot. In some implementations, the locations of the M1 consecutive time slots including K1 > 1 ROs for each time slot can be provided in various ways. For example, the time slot index can be specified by a standard; for instance, the time slot index can be the first or last M1 time slot within the reference PRACH time slot. Alternatively, a bitmap in SIB1 can be used to explicitly provide the time slot index, where there is a one-to-one mapping between bit fields and time slots in the reference time slot. Furthermore, the sign position l of K1 > 1 ROs in each of the M1 consecutive time slots can be determined, for example, by determining and numbering the candidate ROs within the time slot in an increasing order from 0 to Q-1 based on Table 6.3.3.2-4, where Q can be given by higher-level parameters such as prach-ConfigurationIndex. It should be noted that the first K1 > 1 even-numbered candidate ROs can also be considered valid ROs.

[0154] For example, RO can be configured by a higher layer and can be located in the last slot within the reference PRACH slot window.

[0155] Figure 13A and Figure 13B An example of time-domain RO determination according to some implementation schemes is shown. As shown, it is assumed that the reference SCS is a 120kHz SCS used for PRACH configuration. Additionally, the higher-layer parameter prach-ConfigurationIndex can have a value of 13, and the PRAHC format can be A1. Furthermore, there can be a total of N = 6 ROs within a PRACH time slot with a 60kHz SCS. Figure 13A As shown, for a 480kHz SCS, six ROs can be uniformly distributed across four (e.g., M) time slots. Therefore, for For example, if 6 > 4, the 6 ROs can be distributed across 4 time slots with ROs of <2, 2, 1, 1> each. Figure 13B As shown, for a 960kHz SCS, six ROs can be uniformly distributed across eight (e.g., M) time slots. Therefore, for For example, 6≤8, 6 ROs can be distributed in the last 6 of the 8 time slots in the PRACH time slot of the 120kHz SCS.

[0156] As another example, the PRACH transmission window can be divided into N slot subgroups, where each subgroup comprises M slots. The corresponding RO subgroup (or segment index) can be signaled by DCI format 1_0 of the scheduled RACH Response (RAR) transmission. In some implementations, N can be set to values ​​of 4 and 8 for 480 kHz and 960 kHz, respectively. In some cases, the segment index can be signaled by the DCI of the scheduled RAR transmission. For example, a field of the DCI can be added from reserved bits (e.g., 2 or 3 bits). Alternatively, the least significant bit (LSB) of the Sequence Frame Number (SFN) information element (ID) can be introduced for DCI format 1_0 with a CRC scrambled by RA-RNTI, for example, as... Figure 14A As shown. In some cases, the segment index can be divided into two parts, for example, part 1 and part 2. Part 1 may include a payload of DCI format 1_0 with a CRC scrambled by RA-RNTI. The scrambling sequence [w0, w1...w...] can be selected. 23 One of them scrambles the CRC bits of DCI format 1_0 to transmit part 2, such as Figure 14B As shown.

[0157] Alternatively, equation [1] can be modified to include a reference SCS u ref Additional weighting parameters for the reference time slot, and t id It is the index of the first slot of the PRACH timing with digital scheme u, for example:

[0158]

[0159]

[0160] Where u ref A value of 3 can be used for both the 480kHz and 960kHz SCS, and u can have a value of 5 for the 480kHz SCS and a value of 6 for the 960kHz SCS. Note that such weighting parameters can only be used when there is only one RO for both the 480kHz and 960kHz SCS within the reference time slot (e.g., 120kHz SCS). For example, as... Figure 15 As shown, the UE can calculate the RA-RNTI based on the index of time slot 1510. For RO 1520 associated with a 480kHz SCS and RO 1530 associated with a 960kHz SCS, this time slot can be a reference time slot with a 120kHz SCS. Thus, by mitigating any RA-RNTI overflow issues, this method ensures that the RA-RNTI is within the 16-bit range.

[0161] Figure 16 An example block diagram of a method for configuring initial access communication according to some implementation schemes is shown. Among other devices, Figure 16 The method shown can also be used with any of the systems, methods, or devices shown in the figures. In various embodiments, some of the method elements shown may be executed concurrently in a different order than that shown, or may be omitted. Additional method elements may also be executed as needed. As shown, the method operates as follows.

[0162] At 1602, a UE such as UE 106 can configure and / or receive: a control resource set (CORESET) configuration based on a Type 0 physical downlink control channel (PDCCH) search space set supporting at least 96 physical resource blocks (PRBs) of one or more of 120 kHz, 480 kHz, or 960 kHz subcarrier spacing (SCS), and resource block offsets based on one or more of synchronization gratings and component carrier gratings. The CORESET is configured by a data structure comprising one or more indices. Each of the one or more indices can specify the SSB and CORESET multiplexing mode, the number of PRBs in the CORESET, the number of symbols in the CORESET, and the offset between the minimum resource block (RB) index of the CORESET and the minimum RB of the corresponding SSB. Additionally, indices with values ​​of 8 and / or 9 can indicate a CORESET configuration comprising 96 PRBs. In some cases, resource block offsets can be applied to all SCSs or subsets of SCSs, such as subsets of 120kHz SCSs, 480kHz SCSs, and 960kHz SCSs. For example, resource block offsets can be specified as [0,1,2,4] and / or [0,2].

[0163] At 1604, the UE may receive one or more SSB transmissions in the Synchronization Signal Block (SSB) Burst Window (SSBBW) and at least one of the following: the Type 0 PDCCH search space set in CORESET#0 or the Residual Minimal System Information (RMSI) paired with the SSB transmission in the SSBBW.

[0164] In some implementations, the UE can monitor the Type 0 Physical Downlink Control Channel (PDCCH) search space set in at least one of the RMSI slots that are CORESET#0 or paired with the SSB index of one or more SSB transmissions within the SSBBW.

[0165] In some implementations, one or more SSB transmissions can be received in the SSB slots of the SSBBW with the first SCS. Additionally, the Type 0 PDCCH search space set for RMSI scheduling can be monitored in the CORESET0 / RMSI slots of the SSBBW with the second SCS. It should be noted that there can be a one-to-one association between the SSBs transmitted in the SSB slots of the SSBBW and the Type 0 PDCCH search space set monitored by the UE in the CORESET0 / RMSI slots of the SSBBW.

[0166] Furthermore, the SSB time slot may include the first M consecutive time slots of an SSBBW with a first SCS, and the CORESET0 / RMSI time slot may include the subsequent N consecutive time slots of an SSBBW with a second SCS. In some cases, various combinations of the first SCS and the second SCS can be specified.<M,N> The correct value. Note that the first SCS can be less than the second SCS.

[0167] In some implementations, the UE can determine the location of the Random Access Channel (RACH) Opportunity (RO) slot with the third SCS within the physical RACH (PRACH) slot of the reference subcarrier interval (SCS) based on a configuration index included in higher-layer parameters. Additionally, the UE can determine the distribution of ROs with the third SCS based on the total number of time-domain ROs within the PRACH slots of the reference SCS. The third SCS can be either a 480kHz SCS or a 960kHz SCS, which can be larger than the reference SCS of the PRACH slot. Furthermore, when the number of slots with the third SCS within the PRACH slots of the reference SCS is greater than or equal to the total number N of time-domain ROs within the reference slots, the time-domain ROs with the third SCS can be uniformly distributed across the last N slots of the third SCS within the reference slots of the reference SCS, where each slot of the third SCS has one RO. It should be noted that each time-domain RO can use the same start symbol within the slots of the third SCS. Furthermore, the start symbol can be configured for each slot of the third SCS via a higher layer. Additionally, when the number of time slots in the third SCS within the PRACH time slot of the reference SCS is less than the number N of time-domain ROs within the reference time slot, the time-domain ROs can be distributed across all time slots of the third SCS within the reference time slot. Note that each of the first M1 time slots can include K1 ROs, and each of the subsequent M2 time slots can include K2 ROs, where M1 = mod(N, Q). And M2 = N - M1, Q represents the number of time slots of the third SCS in the PRACH time slot of the reference SCS. In some implementations, when the number of time slots of the third SCS in the PRACH time slot of the reference SCS is less than the number N of time domain ROs in the reference time slot, the time domain ROs may be located in the last time slot of the third SCS in the reference time slot window.

[0168] In some implementations, the UE may receive a segment index of the corresponding RACH timing (RO) via a Downlink Control Indicator (DCI) format 1_0 transmitted in a Scheduled Random Access Channel (RACH) Response (RAR) transmission. This segment index may be based at least in part on the Subcarrier Spacing (SCS). Alternatively, the UE may determine the Random Access (RA) Radio Network Temporary Identifier (RNTI) based on the Physical Random Access Channel (PRACH) transmission window, which is divided into multiple time slot subgroups. Note that the number of time slot subgroups may be based on the SCS of the RO, and the segment index may be determined accordingly. In some cases, the segment index may be a field of the Scheduled RAR transmission in DCI format 1_0. In some cases, the segment index may be indicated via the least significant bit (LSB) of the Sequence Frame Number (SNF) Information Element (IE) of the Scheduled RAR transmission in DCI format 1_0. In some cases, the segment index may be indicated by a first part and a second part. The first part may be included in the payload of DCI format 1_0 with a CRC scrambled by the RA-RNTI. The second part can be transmitted by scrambling the CRC bits of DCI format 1_0 using a selected scrambling sequence. Additionally, the first part can indicate an index associated with the scrambling sequence. In some implementations, the RA-RNTI associated with RO can be determined based on a reference SCS greater than RO.

[0169] Figure 17 Another example of a block diagram illustrating a method for configuring initial access communication according to some implementation schemes is shown. Among other devices, Figure 16 The method shown can also be used with any of the systems, methods, or devices shown in the figures. In various embodiments, some of the method elements shown may be executed concurrently in a different order than that shown, or may be omitted. Additional method elements may also be executed as needed. As shown, the method operates as follows.

[0170] At 1702, a UE such as UE 106 may, for example, receive one or more SSB transmissions in a Synchronization Signal Block (SSB) burst window (SSBBW) based on configuration and resource block offset, and at least one of the following: the Type0PDCCH search space set in CORESET#0, or the Residual Minimum System Information (RMSI) paired with an SSB transmission in the same SSBBW.

[0171] At 1704, the UE can monitor the Type 0 Physical Downlink Control Channel (PDCCH) search space set in at least one of the RMSI slots that are paired with the SSB index of one or more SSB transmissions within the SSBBW, or CORESET#0.

[0172] In some implementations, one or more SSB transmissions can be received in the SSB slots of the SSBBW with the first SCS. Additionally, the Type 0 PDCCH search space set for RMSI scheduling can be monitored in the CORESET0 / RMSI slots of the SSBBW with the second SCS. It should be noted that there can be a one-to-one association between the SSBs transmitted in the SSB slots of the SSBBW and the Type 0 PDCCH search space set monitored by the UE in the CORESET0 / RMSI slots of the SSBBW.

[0173] Furthermore, the SSB time slot may include the first M consecutive time slots of an SSBBW with a first SCS, and the CORESET0 / RMSI time slot may include the subsequent N consecutive time slots of an SSBBW with a second SCS. In some cases, various combinations of the first SCS and the second SCS can be specified.<M,N> The correct value. Note that the first SCS can be less than the second SCS.

[0174] In some implementations, the UE can configure and / or receive: a control resource set (CORESET) configuration based on a Type 0 physical downlink control channel (PDCCH) search space set supporting at least 96 physical resource blocks (PRBs) of one or more of 120 kHz, 480 kHz, or 960 kHz subcarrier spacing (SCS), and resource block offsets based on one or more of synchronization gratings and component carrier gratings. The CORESET is configured by a data structure comprising one or more indices. Each of the one or more indices can specify the SSB and CORESET multiplexing mode, the number of PRBs in the CORESET, the number of symbols in the CORESET, and the offset between the minimum resource block (RB) index of the CORESET and the minimum RB of the corresponding SSB. Additionally, indices with values ​​of 8 and / or 9 can indicate a CORESET configuration comprising 96 PRBs. In some cases, resource block offsets can be applied to all SCSs or subsets of SCSs, such as subsets of 120 kHz SCS, 480 kHz SCS, and 960 kHz SCS. For example, the resource block offset can be specified as [0,1,2,4] and / or [0,2].

[0175] In some implementations, the UE can determine the location of the Random Access Channel (RACH) Opportunity (RO) slot with the third SCS within the physical RACH (PRACH) slot of the reference subcarrier interval (SCS) based on a configuration index included in higher-layer parameters. Additionally, the UE can determine the distribution of ROs with the third SCS based on the total number of time-domain ROs within the PRACH slots of the reference SCS. The third SCS can be either a 480kHz SCS or a 960kHz SCS, which can be larger than the reference SCS of the PRACH slot. Furthermore, when the number of slots with the third SCS within the PRACH slots of the reference SCS is greater than or equal to the total number N of time-domain ROs within the reference slots, the time-domain ROs with the third SCS can be uniformly distributed across the last N slots of the third SCS within the reference slots of the reference SCS, where each slot of the third SCS has one RO. It should be noted that each time-domain RO can use the same start symbol within the slots of the third SCS. Furthermore, the start symbol can be configured for each slot of the third SCS via a higher layer. Additionally, when the number of time slots in the third SCS within the PRACH time slot of the reference SCS is less than the number N of time-domain ROs within the reference time slot, the time-domain ROs can be distributed across all time slots of the third SCS within the reference time slot. Note that each of the first M1 time slots can include K1 ROs, and each of the subsequent M2 time slots can include K2 ROs, where M1 = mod(N, Q). And M2 = N - M1, Q represents the number of time slots of the third SCS in the PRACH time slot of the reference SCS. In some implementations, when the number of time slots of the third SCS in the PRACH time slot of the reference SCS is less than the number N of time domain ROs in the reference time slot, the time domain ROs may be located in the last time slot of the third SCS in the reference time slot window.

[0176] In some implementations, the UE may receive a segment index of the corresponding RACH timing (RO) via a Downlink Control Indicator (DCI) format 1_0 transmitted in a Scheduled Random Access Channel (RACH) Response (RAR) transmission. This segment index may be based at least in part on the Subcarrier Spacing (SCS). Alternatively, the UE may determine the Random Access (RA) Radio Network Temporary Identifier (RNTI) based on the Physical Random Access Channel (PRACH) transmission window, which is divided into multiple time slot subgroups. Note that the number of time slot subgroups may be based on the SCS of the RO, and the segment index may be determined accordingly. In some cases, the segment index may be a field of the Scheduled RAR transmission in DCI format 1_0. In some cases, the segment index may be indicated via the least significant bit (LSB) of the Sequence Frame Number (SNF) Information Element (IE) of the Scheduled RAR transmission in DCI format 1_0. In some cases, the segment index may be indicated by a first part and a second part. The first part may be included in the payload of DCI format 1_0 with a CRC scrambled by the RA-RNTI. The second part can be transmitted by scrambling the CRC bits of DCI format 1_0 using a selected scrambling sequence. Additionally, the first part can indicate an index associated with the scrambling sequence. In some implementations, the RA-RNTI associated with RO can be determined based on a reference SCS greater than RO.

[0177] Figure 18 Another example of a block diagram of a method for initial access communication according to some implementation schemes is shown. Among other devices, Figure 16 The method shown can also be used with any of the systems, methods, or devices shown in the figures. In various embodiments, some of the method elements shown may be executed concurrently in a different order than that shown, or may be omitted. Additional method elements may also be executed as needed. As shown, the method operates as follows.

[0178] At 1802, a UE such as UE 106 can determine the location of a random access channel (RACH) timing (RO) slot with a first SCS within a physical RACH (PRACH) slot of a reference subcarrier spacing (SCS) based on a configuration index included in the higher-layer parameters.

[0179] At 1804, the UE can determine the distribution of ROs with the first SCS based on the total number of time-domain ROs in the PRACH slots of the reference SCS. The first SCS can be either a 480kHz SCS or a 960kHz SCS, which can be larger than the reference SCS of the PRACH slot. Furthermore, when the number of slots of the first SCS in the PRACH slots of the reference SCS is greater than or equal to the total number N of time-domain ROs within the reference slots, the time-domain ROs with the first SCS can be uniformly distributed across the last N slots of the first SCS in the reference slots of the reference SCS, with one RO per slot of the first SCS. It should be noted that each time-domain RO can use the same start symbol in the slots of the first SCS. Additionally, the start symbol can be configured via a higher layer for each slot of the first SCS. Furthermore, when the number of slots of the first SCS in the PRACH slots of the reference SCS is less than the number N of time-domain ROs within the reference slots, the time-domain ROs can be distributed across all slots of the first SCS in the reference slots. It should be noted that each of the first M1 time slots may include K1 ROs, and each of the subsequent M2 time slots may include K2 ROs, where M1 = mod(N, Q). And M2 = N - M1, Q represents the number of time slots of the first SCS in the PRACH time slot of the reference SCS. In some implementations, when the number of time slots of the first SCS in the PRACH time slot of the reference SCS is less than the number N of time domain ROs in the reference time slot, the time domain ROs may be located in the last time slot of the first SCS in the reference time slot window.

[0180] In some implementations, the UE can configure and / or receive: a control resource set (CORESET) configuration based on a Type 0 physical downlink control channel (PDCCH) search space set supporting at least 96 physical resource blocks (PRBs) of one or more of 120 kHz, 480 kHz, or 960 kHz subcarrier spacing (SCS), and resource block offsets based on one or more of synchronization gratings and component carrier gratings. The CORESET is configured by a data structure comprising one or more indices. Each of the one or more indices can specify the SSB and CORESET multiplexing mode, the number of PRBs in the CORESET, the number of symbols in the CORESET, and the offset between the minimum resource block (RB) index of the CORESET and the minimum RB of the corresponding SSB. Additionally, indices with values ​​of 8 and / or 9 can indicate a CORESET configuration comprising 96 PRBs. In some cases, resource block offsets can be applied to all SCSs or subsets of SCSs, such as subsets of 120 kHz SCS, 480 kHz SCS, and 960 kHz SCS. For example, the resource block offset can be specified as [0,1,2,4] and / or [0,2].

[0181] In some implementations, the UE may, for example, receive one or more SSB transmissions within a Synchronization Signal Block (SSB) burst window (SSBBW) based on configuration and resource block offset, and at least one of the following: a Type 0 PDCCH search space set in CORESET#0, or a Residual Minimum System Information (RMSI) paired with an SSB transmission in the same SSBBW. Furthermore, the UE may monitor a Type 0 Physical Downlink Control Channel (PDCCH) search space set in at least one of the RMSI slots paired with the SSB indexes of one or more SSB transmissions within the SSBBW.

[0182] In some implementations, one or more SSB transmissions can be received in the SSB slots of the SSBBW with the first SCS. Additionally, the Type 0 PDCCH search space set for RMSI scheduling can be monitored in the CORESET0 / RMSI slots of the SSBBW with the second SCS. It should be noted that there can be a one-to-one association between the SSBs transmitted in the SSB slots of the SSBBW and the Type 0 PDCCH search space set monitored by the UE in the CORESET0 / RMSI slots of the SSBBW.

[0183] Furthermore, the SSB time slot may include the first M consecutive time slots of an SSBBW with a first SCS, and the CORESET0 / RMSI time slot may include the subsequent N consecutive time slots of an SSBBW with a second SCS. In some cases, various combinations of the first SCS and the second SCS can be specified.<M,N> The correct value. Note that the first SCS can be less than the second SCS.

[0184] In some implementations, the UE may receive a segment index of the corresponding RACH timing (RO) via a Downlink Control Indicator (DCI) format 1_0 transmitted in a Scheduled Random Access Channel (RACH) Response (RAR) transmission. This segment index may be based at least in part on the Subcarrier Spacing (SCS). Alternatively, the UE may determine the Random Access (RA) Radio Network Temporary Identifier (RNTI) based on the Physical Random Access Channel (PRACH) transmission window, which is divided into multiple time slot subgroups. Note that the number of time slot subgroups may be based on the SCS of the RO, and the segment index may be determined accordingly. In some cases, the segment index may be a field of the Scheduled RAR transmission in DCI format 1_0. In some cases, the segment index may be indicated via the least significant bit (LSB) of the Sequence Frame Number (SNF) Information Element (IE) of the Scheduled RAR transmission in DCI format 1_0. In some cases, the segment index may be indicated by a first part and a second part. The first part may be included in the payload of DCI format 1_0 with a CRC scrambled by the RA-RNTI. The second part can be transmitted by scrambling the CRC bits of DCI format 1_0 using a selected scrambling sequence. Additionally, the first part can indicate an index associated with the scrambling sequence. In some implementations, the RA-RNTI associated with RO can be determined based on a reference SCS greater than RO.

[0185] Figure 19 Another example of a block diagram of a method for initial access communication according to some implementation schemes is shown. Among other devices, Figure 16 The method shown can also be used with any of the systems, methods, or devices shown in the figures. In various embodiments, some of the method elements shown may be executed concurrently in a different order than that shown, or may be omitted. Additional method elements may also be executed as needed. As shown, the method operates as follows.

[0186] At 1902, a UE such as UE 106 can receive the segment index of the corresponding RACH timing (RO) via a downlink control indicator (DCI) format 1_0 transmitted in a Scheduled Random Access Channel (RACH) response (RAR). This segment index may be based at least in part on the subcarrier spacing (SCS).

[0187] At 1904, the UE can determine the Random Access (RA) Radio Network Temporary Identifier (RNTI) based on the Physical Random Access Channel (PRACH) transmission window, which is divided into multiple time slot subgroups. Note that the number of time slot subgroups can be based on the SCS of the RO, and the segment index can be determined. In some cases, the segment index can be a field of the DCI format 1_0 that schedules RAR transmissions. In some cases, the segment index can be indicated via the least significant bit (LSB) of the Sequence Frame Number (SNF) Information Element (IE) of the DCI format 1_0 that schedules RAR transmissions. In some cases, the segment index can be indicated by a first part and a second part. The first part can be included in the payload of the DCI format 1_0 with a CRC scrambled by the RA-RNTI. The second part can be transmitted by scrambling the CRC bits of the DCI format 1_0 using a selected scrambling sequence. Additionally, the first part can indicate an index associated with the scrambling sequence. In some implementations, the RA-RNTI associated with the RO can be determined based on a reference SCS greater than the RO's SCS.

[0188] In some implementations, the UE can configure and / or receive: a control resource set (CORESET) configuration based on a Type 0 physical downlink control channel (PDCCH) search space set supporting at least 96 physical resource blocks (PRBs) of one or more of 120 kHz, 480 kHz, or 960 kHz subcarrier spacing (SCS), and resource block offsets based on one or more of synchronization gratings and component carrier gratings. The CORESET is configured by a data structure comprising one or more indices. Each of the one or more indices can specify the SSB and CORESET multiplexing mode, the number of PRBs in the CORESET, the number of symbols in the CORESET, and the offset between the minimum resource block (RB) index of the CORESET and the minimum RB of the corresponding SSB. Additionally, indices with values ​​of 8 and / or 9 can indicate a CORESET configuration comprising 96 PRBs. In some cases, resource block offsets can be applied to all SCSs or subsets of SCSs, such as subsets of 120 kHz SCS, 480 kHz SCS, and 960 kHz SCS. For example, the resource block offset can be specified as [0,1,2,4] and / or [0,2].

[0189] In some implementations, the UE may, for example, receive one or more SSB transmissions within a Synchronization Signal Block (SSB) burst window (SSBBW) based on configuration and resource block offset, and at least one of the following: a Type 0 PDCCH search space set in CORESET#0, or a Residual Minimum System Information (RMSI) paired with an SSB transmission in the same SSBBW. Furthermore, the UE may monitor a Type 0 Physical Downlink Control Channel (PDCCH) search space set in at least one of the RMSI slots paired with the SSB indexes of one or more SSB transmissions within the SSBBW.

[0190] In some implementations, one or more SSB transmissions can be received in the SSB slots of the SSBBW with the first SCS. Additionally, the Type 0 PDCCH search space set for RMSI scheduling can be monitored in the CORESET0 / RMSI slots of the SSBBW with the second SCS. It should be noted that there can be a one-to-one association between the SSBs transmitted in the SSB slots of the SSBBW and the Type 0 PDCCH search space set monitored by the UE in the CORESET0 / RMSI slots of the SSBBW.

[0191] Furthermore, the SSB time slot may include the first M consecutive time slots of an SSBBW with a first SCS, and the CORESET0 / RMSI time slot may include the subsequent N consecutive time slots of an SSBBW with a second SCS. In some cases, various combinations of the first SCS and the second SCS can be specified.<M,N> The correct value. Note that the first SCS can be less than the second SCS.

[0192] In some implementations, the UE can determine the location of the Random Access Channel (RACH) Opportunity (RO) slot with the third SCS within the physical RACH (PRACH) slot of the reference subcarrier interval (SCS) based on a configuration index included in higher-layer parameters. Additionally, the UE can determine the distribution of ROs with the third SCS based on the total number of time-domain ROs within the PRACH slots of the reference SCS. The third SCS can be either a 480kHz SCS or a 960kHz SCS, which can be larger than the reference SCS of the PRACH slot. Furthermore, when the number of slots with the third SCS within the PRACH slots of the reference SCS is greater than or equal to the total number N of time-domain ROs within the reference slots, the time-domain ROs with the third SCS can be uniformly distributed across the last N slots of the third SCS within the reference slots of the reference SCS, where each slot of the third SCS has one RO. It should be noted that each time-domain RO can use the same start symbol within the slots of the third SCS. Furthermore, the start symbol can be configured for each slot of the third SCS via a higher layer. Additionally, when the number of time slots in the third SCS within the PRACH time slot of the reference SCS is less than the number N of time-domain ROs within the reference time slot, the time-domain ROs can be distributed across all time slots of the third SCS within the reference time slot. Note that each of the first M1 time slots can include K1 ROs, and each of the subsequent M2 time slots can include K2 ROs, where M1 = mod(N, Q). And M2 = N - M1, Q represents the number of time slots of the third SCS in the PRACH time slot of the reference SCS. In some implementations, when the number of time slots of the third SCS in the PRACH time slot of the reference SCS is less than the number N of time domain ROs in the reference time slot, the time domain ROs may be located in the last time slot of the third SCS in the reference time slot window.

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

[0194] Embodiments of this disclosure may be implemented in any of a variety of forms. For example, some embodiments may be implemented as computer-implemented methods, computer-readable storage media, or computer systems. Other embodiments may be implemented using one or more custom-designed hardware devices such as ASICs. Other embodiments may be implemented using one or more programmable hardware elements such as FPGAs.

[0195] In some embodiments, a non-transitory computer-readable storage medium may be configured to store program instructions and / or data, wherein if the program instructions are executed by a computer system, the computer system performs a method, such as any method embodiment of the method embodiments described herein, or any combination of the method embodiments described herein, or any subset or combination of any such subset of any method embodiments described herein.

[0196] In some implementations, the device (e.g., UE 106) may be configured to include a processor (or a set of processors) and a memory medium, wherein the memory medium stores program instructions, and the processor is configured to read from and execute the program instructions from the memory medium, wherein the program instructions are executable to implement any of the various method implementations described herein (or any combination of method implementations described herein, or any subset of any method implementations described herein, or any combination of such subsets). The device may be implemented in any of a variety of forms.

[0197] By interpreting each message / signal X received by the user equipment (UE) in the downlink as a message / signal X transmitted by the base station, and interpreting each message / signal Y transmitted by the UE in the uplink as a message / signal Y received by the base station, any method described herein for operating the UE can serve as the basis for a corresponding method for operating the base station.

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

Claims

1. A user equipment (UE), comprising: At least one antenna; At least one radio component, wherein the at least one radio component is configured to perform cellular communication using at least one radio access technology (RAT); One or more processors, said one or more processors being coupled to said at least one radio component, wherein said one or more processors and said at least one radio component are configured to perform communication; The one or more processors are configured such that the UE: Receive the configuration of the control resource set CORESET based on the Type 0 physical downlink control channel PDCCH search space set of at least 96 physical resource blocks PRBs supporting one or more of 120kHz, 480kHz or 960kHz subcarrier spacing SCS, and the resource block offset based on one or more of synchronization gratings and component carrier gratings. as well as Based on the configuration and the resource block offset, one or more SSB transmissions are received in the Synchronization Signal Block (SSB) burst window (SSBBW), along with at least one of the following: the Type 0 PDCCH search space set in CORESET #0, or the Remaining Minimum System Information (RMSI) paired with an SSB transmission in the same SSBBW; and Based on the configuration index included in the higher-layer parameters, the position of the RACH timing RO slot associated with the third SCS is determined within the reference physical random access channel RACH PRACH slot window associated with the reference SCS.

2. The UE according to claim 1, The configuration of CORESET is specified by a data structure comprising one or more indexes, each of which specifies the SSB and CORESET reuse mode, the number of PRBs of the CORESET, the number of symbols of the CORESET, and the offset between the minimum resource block (RB) index of the CORESET and the minimum RB of the corresponding SSB.

3. The UE according to claim 2, The indexes with values ​​8 and 9 indicate a CORESET configuration of 96 PRBs.

4. The UE according to claim 1, The resource block offset is applied to all SCSs or a subset of SCSs.

5. The UE according to claim 4, The resource block offset is specified as [0, 1, 2, 4].

6. The UE according to claim 1, The one or more processors are further configured such that the UE: Monitor the Type 0 Physical Downlink Control Channel (PDCCH) search space set in at least one of the RMSI slots that are paired with the SSB index of the one or more SSB transmissions within the SSBBW, or CORESET #0.

7. The UE according to claim 1, The one or more SSB transmissions are received in the SSB time slot of the SSBBW having the first SCS; and The Type 0 PDCCH search space set for RMSI scheduling is monitored in the CORESET0 / RMSI slot of the SSBBW with the second SCS.

8. The UE according to claim 7, There is a one-to-one association between the SSB transmitted in the SSB slot of the SSBBW and the Type 0 PDCCH search space set monitored by the UE in the CORESET0 / RMSI slot of the SSBBW.

9. The UE according to claim 7, The SSB time slot includes the preceding SSBBBW with a first SCS. M A series of consecutive time slots, and the CORESET0 / RMSI time slot includes the subsequent SSBBW with a second SCS. N A continuous time slot.

10. The UE according to claim 9, Where various combinations of the first SCS and the second SCS are specified M , N The value of the first SCS is less than the second SCS.

11. The UE according to claim 1, The one or more processors are further configured such that the UE: The distribution of ROs with the third SCS is determined based on the total number of time-domain ROs in the PRACH slot of the reference SCS, wherein the third SCS is one of a 480kHz SCS or a 960kHz SCS that is larger than the reference SCS of the PRACH slot.

12. The UE according to claim 11, in, When the number of time slots of the third SCS in the PRACH time slot of the reference SCS is greater than or equal to the total number of time domain ROs in the reference time slot. N At that time, the time-domain RO of the third SCS is uniformly distributed in the reference time slot of the reference SCS at the end of the third SCS. N In each time slot, the third SCS has one RO.

13. The UE according to claim 12, Each time-domain RO uses the same start symbol in the time slot of the third SCS.

14. The UE according to claim 13, The start symbol is configured for each time slot of the third SCS via a higher layer.

15. The UE according to claim 11, in, When the number of time slots of the third SCS in the PRACH time slot of the reference SCS is less than the number of time domain ROs in the reference time slot. N At that time, the time-domain RO is distributed across all time slots of the third SCS in the reference time slot, wherein the first Each time slot in the time slot includes One RO, and subsequent Each time slot in the time slot includes One RO, and among them , This indicates the number of time slots of the third SCS in the PRACH time slots of the reference SCS.

16. The UE according to claim 11, in, When the number of time slots of the third SCS in the PRACH time slot of the reference SCS is less than the number of time domain ROs in the reference time slot. N At that time, the time domain RO is located in the last time slot of the third SCS in the reference time slot window.

17. The UE according to claim 1, The one or more processors are further configured such that the UE: The segment index of the corresponding RACH timing RO is received via the downlink control indicator DCI format 1_0 transmitted in response to the RAR via the scheduled random access channel RACH, wherein the segment index is at least partially based on the subcarrier spacing SCS; and The Random Access RA Radio Network Temporary Identifier (RNTI) is determined based on the Physical Random Access Channel (PRACH) transmission window, which is divided into many time slot subgroups, wherein the number of time slot subgroups is based on the SCS of the RO and the segment index is determined.

18. The UE according to claim 17, The segment index is a field of the DCI format 1_0 used to schedule RAR transmissions.

19. The UE according to claim 17, The segment index is indicated by the least significant bit (LSB) of the sequence frame number (SNF) information element (IE) of the DCI format 1_0 transmitted via the scheduled RAR.

20. The UE according to claim 17, The segment index is indicated by a first part and a second part.

21. The UE according to claim 20, The first part is included in the payload of DCI format 1_0 with CRC scrambled by RA-RNTI.

22. The UE according to claim 21, The second part is transmitted by scrambling the CRC bits of DCI format 1_0 using a selected scrambling sequence.

23. The UE according to claim 22, The first part indicates an index associated with the scrambling sequence.

24. The UE of claim 17, wherein the RA-RNTI associated with the RO is determined based on a reference SCS value that is greater than the value of the SCS of the RO.

25. An apparatus comprising: Memory; as well as At least one processor, which communicates with the memory and is configured to: Receive one or more SSB transmissions and at least one of the following in the Synchronization Signal Block (SSB) Burst Window (SSBBW): Random Access Control Resource Set (CORESET) #0 or Residual Minimum System Information (RMSI); as well as Monitor the Type 0 Physical Downlink Control Channel (PDCCH) search space set in at least one of the RMSIs that are paired with the SSB index of the one or more SSB transmissions in the same SSBBW in CORESET #0; as well as Based on the configuration index included in the higher-layer parameters, the position of the RACH timing RO slot associated with the third SCS is determined within the reference physical random access channel RACH PRACH slot window associated with the reference SCS.

26. The apparatus according to claim 25, The one or more SSB transmissions are received in the SSB time slot of the SSBBW with the first SCS; and The Type 0 PDCCH search space set used for RMSI scheduling in the CORESET #0 is monitored in the CORESET0 / RMSI slot of the SSBBW with the second SCS.

27. The apparatus according to claim 26, There is a one-to-one association between the SSB transmitted in the SSB slot of the SSBBW and the Type 0 PDCCH search space set for UE monitoring in the CORESET0 / RMSI slot of the SSBBW.

28. The apparatus according to claim 26, The SSB time slot includes the preceding SSBBBW with a first SCS. M A series of consecutive time slots, and the CORESET0 / RMSI includes the subsequent SSBBW with a second SCS. N A continuous time slot.

29. The apparatus according to claim 28, Where various combinations of the first SCS and the second SCS are specified M , N The value of the first SCS is less than the value of the second SCS.

30. The apparatus according to claim 25, The at least one processor is configured to: The distribution of ROs with a third SCS is determined based on the total number of time-domain ROs in the PRACH slot of the reference SCS, wherein the third SCS is one of a 480 kHz SCS or a 960 kHz SCS that is larger than the reference SCS of the PRACH slot.

31. The apparatus according to claim 30, in, When the number of slots in the third SCS within the PRACH slot of the reference SCS is greater than or equal to the total number of time-domain ROs within the reference slot. N At that time, the time-domain ROs having the third SCS are uniformly distributed in the last of the reference time slots of the third SCS. N In each time slot, the third SCS has one RO.

32. The apparatus according to claim 31, Each time-domain RO uses the same start symbol in the time slot of the third SCS.

33. The apparatus according to claim 32, The start symbol is configured for each time slot of the third SCS via a higher layer.

34. The apparatus according to claim 30, in, When the number of slots in the third SCS within the PRACH slot of the reference SCS is less than the number of time-domain ROs within the reference slot. N At that time, the time-domain RO is distributed across all time slots of the third SCS in the reference time slot, wherein the first Each time slot in the time slot includes One RO, and subsequent Each time slot in the time slot includes One RO, and among them , as well as This indicates the number of time slots of the third SCS in the PRACH time slots of the reference SCS.

35. The apparatus according to claim 30, in, When the number of slots in the third SCS within the PRACH slot of the reference SCS is less than the number of time-domain ROs within the reference slot. N At that time, the time domain RO is located in the last time slot of the third SCS in the reference time slot window.

Images