WO2022031743A1

WO2022031743A1 - Prach configuration and rnti determination for above 52.6ghz

Info

Publication number: WO2022031743A1
Application number: PCT/US2021/044398
Authority: WO
Inventors: Gang Xiong; Yingyang Li; Daewon Lee; Salvatore TALARICO
Original assignee: Intel Corp
Current assignee: Intel Corp
Priority date: 2020-08-06
Filing date: 2021-08-03
Publication date: 2022-02-10
Anticipated expiration: 2023-02-06

Abstract

In a fifth-generation (5G) new radio (NR) system (5GS), for operating above a 52.6 GHz carrier frequency when a physical random-access channel (PRACH) subcarrier spacing (SCS) is used for transmission of a PRACH preamble, a user equipment (UE) may identify a reference PRACH slot based on a reference SCS and may identify one or more PRACH slots within the reference PRACH slot based on a PRACH configuration index for transmission of the PRACH preamble. The one or more PRACH slots may be based on the PRACH SCS and the PRACH SCS may be larger than the reference SCS. The UE may encode the PRACH preamble for transmission to a generation Node B (gNB) in a PRACH occasion corresponding to the one or more PRACH slots to perform a random-access channel (RACH) procedure.

Description

PRACH CONFIGURATION AND RNTI DETERMINATION FOR ABOVE

52.6GHZ

PRIORITY CLAIM

[0001] This application claims priority to United States Provisional Patent Application Serial No, 63/062,015, filed August 06, 2020 [reference number AD1629-Z] which is incorporated herein by reference in its entirety.

TECHNICAL FIELD

[0002] Some embodiments relate to wireless networks including 3 GPP (Third Generation Partnership Project) and fifth-generation (5G) networks including 5G new radio (NR) (or 5G-NR) networks. Some embodiments pertain to physical random-access channel (PRACH) configuration for operations above a 52.6 GHz carrier frequency.

BACKGROUND

[0003] Mobile communications have evolved significantly from early voice systems to today’s highly sophisticated integrated communication platform. With the increase in different types of devices communicating with various network devices, usage of 3GPP 5G NR systems has increased. The penetration of mobile devices (user equipment or UEs) in modern society has continued to drive demand for a wade variety of networked devices in many disparate environments. 5G NR wireless systems are forthcoming and are expected to enable even greater speed, connectivity, and usability, and are expected to increase throughput, coverage, and robustness and reduce latency and operational and capital expenditures. 5G-NR networks will continue to evolve based on 3 GPP LTE- Advanced with additional potential new radio access technologies (RATs) to enrich people’s lives with seamless wireless connectivity solutions delivering fast, rich content and services. As current cellular network frequency is saturated, higher frequencies, such as millimeter wave (mmWave) frequency, can be beneficial due to their high bandwidth.

[0004] One issue with operations above a 52.6 GHz carrier frequency is phase noise. A greater subcarrier spacings (SCS) may be used to help combat phase noise and thus a PRACH configuration is needed for greater subcarrier spacings.

BRIEF DESCRIPTION OF THE DRAWINGS

[0005] FIG. 1 A illustrates an architecture of a network, in accordance with some embodiments.

[0006] FIG. 1B and FIG. 1C illustrate a non-roaming 5G system architecture in accordance with some embodiments.

[0007] FIG. 2A illustrates a 4-step RACH procedure in accordance with some embodiments.

[0008] FIG. 2B illustrates a 2-step RACH procedure in accordance with some embodiments.

[0009] FIG. 2C illustrates a table for PRACH configuration index 88 in accordance with some embodiments.

[0010] FIG. 2D illustrates a table for PRACH configuration index 255 in accordance with some embodiments.

[0011] FIG. 3 illustrates PRACH slots for PRACH configuration index 88, in accordance with some embodiments.

[0012] FIG. 4 illustrates PRACH slots for PRACH configuration index 255, in accordance with some embodiments.

[0013] FIG. 5 illustrates PRACH slots for PRACH configuration index 88, in accordance with some other embodiments.

[0014] FIG. 6 illustrates PRACH slots for PRACH configuration index 88, in accordance with some other embodiments.

[0015] FIG. 7 illustrates PRACH slots identified to align with slots based on a 120 kHz subcarrier spacing, in accordance with some other embodiments.

[0016] FIG. 8 is a functional block diagram of a wireless communication device in accordance with some embodiments. DETAILED DESCRIPTION

[0017] The following description and the drawings sufficiently illustrate specific embodiments to enable those skilled in the art to practice them. Other embodiments may incorporate structural, logical, electrical, process, and other changes. Portions and features of some embodiments may be included in, or substituted for, those of other embodiments. Embodiments set forth in the claims encompass all available equivalents of those claims.

[0018] Some embodiments are directed to a user equipment (UE) configured for operation in a fifth-generation (5G) new radio (NR) system (5GS). In these embodiments, for operating above a 52.6 GHz carrier frequency when a physical random-access channel (PRACH) subcarrier spacing (SCS ) is used for transmission of a PRACH preamble, the UE may be configured to identify a reference PRACH slot based on a reference SCS. The UE may identify one or more PRACH slots within the reference PRACH slot based on a PRACH configuration index for transmission of the PRACH preamble. In these embodiments, the one or more PRACH slots may be based on the PRACH SCS and the PRACH SCS may be larger than the reference SCS. In these embodiments, the UE may encode the PRACH preamble for transmission to a generation Node B (gNB) (e.g., Msgl (see FIG. 2A) or MsgA (see FIG. 2B ) ) in a PRACH occasion corresponding to the one or more PRACH slots to perform a random-access channel (RACH) procedure.

[0019] In these embodiments, the reference PRACH slot may be based on the reference SCS and comprises a plurality of smaller slots which may be based on the PRACH SCS. In these embodiments, one or two PRACH slots for transmission of the PRACH preamble, for example, may be included in a reference PRACH slot. The one or two PRACH slots may be determined by the UE based on the PRACH configuration index.

[0020] In some embodiments, when the PRACH SCS comprises one of a 480 kHz SCS or a 960 kHz SCS, and when the reference SCS is a 60 kHz SCS, the UE may use the 60 kHz SCS to determine a location of the PRACH slots for transmission of the PRACH preamble, the PRACH slots based on the PRACH SCS. In these embodiments, when the PRACH SCS comprises one of the 480 kHz SCS or the 960 kHz SCS, and when the reference SCS is a 120 kHz SCS, the UE may use the 120 kHz SCS to determine the location of the PRACH slots for transmission of the PRACH preamble. In these embodiments, the PRACH slots may be based on the PRACH SCS. In these embodiments, the same set of PRACH configuration index tables may be used for different SCSs as the PRACH configuration index is independent from the SCS.

[0021] In some embodiments, when the reference SCS is the 60 kHz SCS and when the PRACH SCS is either the 480 kHz SCS or 960 kHz SCS, the reference PRACH slot (i.e., based on the 60 kHz SCS) comprises two 120 kHz SCS slots that are based on the 120 kHz SCS. In some embodiments, when two PRACH slots are indicated (e.g., allocated) by the PRACH configuration index within the reference PRACH slot (e.g., by PRACH config, index 88 (see FIG. 2C)), either a first or a last slot within each 120 kHz SCS slot may be identified by the UE as the PRACH slots for transmission of the PRACH preamble. In these embodiments, the PRACH slots identified by the UE may be based on the PRACH SCS. An example of these embodiments is illustrated in FIG. 7, described in more detail below.

[0022] In some embodiments, when the reference SCS is the 60 kHz SCS and when the PRACH SCS is either the 480 kHz SCS or 960 kHz SCS, the reference PRACH slot (i.e., based on the 60 kHz SCS) may comprise the two 120 kHz SCS slots that are based on the 120 kHz SCS. In some embodiments, when one PRACH slot is indicated (e.g., allocated) by the PRACH configuration index within the reference PRACH slot (e.g., by PRACH config, index 255 (see FIG. 2D)), either a first or a last slot within one of the two 120 kHz SCS slots (either the first or the second 120 kHz SCS slot) may be identified by the UE as the PRACH slot for transmission of the PRACH preamble. In these embodiments, the PRACH slot identified by the UE may be based on the PRACH SCS.

[0023] In some embodiments, when the reference SCS is the 60 kHz SCS and when the PRACH SCS is either the 480 kHz SCS or 960 kHz SCS, the reference PRACH slot (i.e., based on the 60 kHz SCS) may comprise two 120 kHz SCS slots that are based on the 120 kHz SCS. When two PRACH slots are indicated (e.g., allocated) by the PRACH configuration index within the reference PRACH slot (e.g,, by PRACH config, index 88), a slot, within each 120 kHz SCS slot may be identified by the UE as the PRACH slots for transmission of the PRACH preamble. In these embodiments, the PRACH slots identified by the UE may be based on the PRACH SCS. In these embodiments, when only one PRACH slot is indicated (e.g., allocated) by the PRACH configuration index within the reference PRACH slot (e.g., by PRACH config, index 255), a slot within either the first or the second 120 kHz SCS slot may be identified by the UE as the PRACH slot for transmission of the PRACH preamble, the PRACH slot identified by the UE being based on the PRACH SCS. In these embodiments, the slot within each 120 kHz SCS slot or the slot within either the first or the second 120 kHz SCS slot are identified by the UE based on predefined slot index. In these embodiments, the PRACH slots identified by the UE for transmission of the PRACH preamble are aligned with slots based on the 120 kHz SCS.

[0024] In some embodiments, when the PRACH SCS comprises the 960 kHz SCS, and when the reference SCS is the 480 kHz SCS, the UE may use the 480 kHz SCS to determine a location of the PRACH slots for transmission of the PRACH preamble, the PRACH slots based on the 960 kHz SCS. (see FIG. 6). In the example illustrated in FIG. 6, the PRACH configuration index 255 identifies slots 1 ,3,5,7. . . ,37,39 as the reference PRACH slots for reference SCS of 480 kHz. Therefore, slots 3, 7, etc. are identified as the PRACH shots 960 kHz SCS for transmission of the PRACH preamble.

[0025] In some embodiments, for a 4-step RACH procedure, the UE may be configured to calculate a Random-Access Radio Network Temporary Identifier (RA-RNTI) and monitor a physical downlink control channel (PDCCH) with Cyclic Redundancy Check (CRC) scrambled by the RA-RNTI for a random-access response (RAR) (e.g., Msg2) from the gNB. In these embodiments, the RA-RNTI may be calculated using a modulo or floor operation (e.g., to limit the size of the RA-RNTI). In these embodiments, both the gNB and the UE are able to determine the RA-RNTI for use in the 4-step RACH procedure (see FIG. 2A). In some embodiments, a MsgB-RNTI is determined for a 2-step RACH procedure (see FIG. 2B).

[0026] In some embodiments, for a 2-step RACH procedure, the UE may encode the PRACH preamble for transmission along with a physical uplink shard channel (PUSCH) payload (e.g., Msg A), determine a MsgB-RNTI; and monitor the PDCCH with a CRC scrambled by the MsgB-RNTI for the RAR (e.g., MsgB) from the gNB. In these embodiments, the UE may determine the MsgB-RNTI using a modulo or floor operation n (e.g., to limit the size of the MsgB-RNTI). In some embodiments, the PRACH SCS may be an integer multiple of the reference SCS allowing the slots of the PRACH SCS to be aligned with slots of the reference SCS. In these embodiments, the PRACH SCS may be greater than the reference SCS and thus time slots based on the PRACH SCS are smaller in time than time slots based on the reference subcarrier spacing.

[0027] In some embodiments, the UE may also be configured to decode a system information block (SIB1) received from the gNB. The SIB1 may include a PRACH configuration that includes the PRACH configuration index (see table 1 (see FIG. 2C) or table 2 (see FIG. 2D)) (e.g., a prach-Configindex information element (IE)). In these embodiments, based on the PRACH configuration index, the UE determines the PRACH occasion (RO) index in time and frequency. A PRACH configuration index of 88 and a PRACH configuration index 255 are some non-limiting examples illustrated in table 1 (see FIG. 2C) and table 2 (FIG. 2D), respectively.

[0028] Some embodiments are directed to a non-transitory computer- readable storage medium that stores instructions for execution by processing circuitry of a user equipment (UE) configured for operation in a fifth-generation (5G) new radio (NR) system (5GS) for operating above a 52.6 GHz carrier frequency when a physical random-access channel (PRACH) subcarrier spacing (SCS) is used for transmission of a PRACH preamble.

[0029] Some embodiments are directed to a generation Node B (gNB) configured for operation in a fifth-generation (5G) new radio (NR) system (5GS). For operating above a 52.6 GHz carrier frequency when a physical random-access channel (PRACH) subcarrier spacing (SCS) is used for transmission of a PRACH preamble by a user equipment (UE), the gNB may be configured to identify a reference PRACH slot based on a reference SCS and identify one or more PRACH slots within the reference PRACH slot based on a PRACH configuration index. The one or more PRACH slots may be based on the PRACH SCS and the PRACH SCS may be larger than the reference SCS. In these embodiments, the gNB may be configured to decode the PRACH preamble received from the UE (e.g., Msgl or MsgA) in a PRACH occasion corresponding to the one or more PRACH slots to perform a random-access channel (RACK) procedure.

[0030] FIG. 1 A illustrates an architecture of a network in accordance with some embodiments. The network 140 A is shown to include user equipment (UE) 101 and UE 102. The UEs 101 and 102 are illustrated as smartphones (e.g., handheld touchscreen mobile computing devices connectable to one or more cellular networks) but may also include any mobile or non-mobile computing device, such as Personal Data Assistants (PDAs), pagers, laptop computers, desktop computers, wireless handsets, drones, or any other computing device including a wired and/or wireless communications interface. The UEs 101 and 102 can be collectively referred to herein as UE 101, and UE 101 can be used to perform one or more of the techniques disclosed herein.

[0031] Any of the radio links described herein (e.g., as used in the network 140A or any other illustrated network) may operate according to any exemplary radio communication technology and/or standard.

[0032] LTE and LTE-Advanced are standards for wireless communications of high-speed data for UE such as mobile telephones. In LTE- Advanced and various wireless systems, carrier aggregation is a technology according to which multiple carrier signals operating on different frequencies may be used to carry communications for a single UE, thus increasing the bandwidth available to a single device. In some embodiments, carrier aggregation may be used where one or more component carriers operate on unlicensed frequencies.

[0033] Embodiments described herein can be used in the context of any spectrum management scheme including, for example, dedicated licensed spectrum, unlicensed spectrum, (licensed) shared spectrum (such as Licensed Shared Access (LSA) in 2.3-2.4 GHz, 3, 4-3, 6 GHz, 3.6-3.8 GHz, and further frequencies and Spectrum Access System (SAS) in 3.55-3.7 GHz and further frequencies).

[0034] Embodiments described herein can also be applied to different Single Carrier or OFDM flavors (CP-OFDM, SC-FDMA, SC-OFDM, filter bank-based multicarrier (FBMC), OFDMA, etc.) and in particular 3GPP NR (New Radio) by allocating the OFDM earner data bit vectors to the corresponding symbol resources.

[0035] In some embodiments, any of the UEs 101 and 102 can comprise an Internet-of-Things (loT) UE or a Cellular loT (CIoT) UE, which can comprise a network access layer designed for low-power loT applications utilizing short-lived UE connections. In some embodiments, any of the UEs 101 and 102 can include a narrowband (NB) loT UE (e.g., such as an enhanced NB- loT (eNB-IoT) UE and Further Enhanced (FeNB-IoT) UE). An loT UE can utilize technologies such as machine-to-machine (M2M) or machine-type communications (MTC) for exchanging data with an MTC server or device via a public land mobile network (PLMN), Proximity -Based Serving (ProSe) or device-to-device (D2D) communication, sensor networks, or loT networks. The M2M or MTC exchange of data may be a machine-initiated exchange of data. An loT network includes interconnecting loT UEs, which may include uniquely identifiable embedded computing devices (within the Internet infrastructure), with short-lived connections. The loT UEs may execute background applications (e.g., keep-alive messages, status updates, etc.) to facilitate the connections of the loT network.

[0036] In some embodiments, any of the UEs 101 and 102 can include enhanced MTC (eMTC) UEs or further enhanced MTC (FeMTC) UEs.

[0037] The UEs 101 and 102 may be configured to connect, e.g., communicatively couple, with a radio access network (RAN) 110. The RAN 110 may be, for example, an Evolved Universal Mobile Telecommunications System (UMTS) Terrestrial Radio Access Network (E-UTRAN), a NextGen RAN (NG RAN), or some other type of RAN. The UEs 101 and 102 utilize connections 103 and 104, respectively, each of which comprises a physical communications interface or layer (discussed in further detail below); in this example, the connections 103 and 104 are illustrated as an air interface to enable communicative coupling and can be consistent with cellular communications protocols, such as a Global System for Mobile Communications (GSM) protocol, a code-division multiple access (CDM A) network protocol, a. Push-to- Talk (PTT) protocol, a PTT over Cellular (POC) protocol, a Universal Mobile Telecommunications System (UMTS) protocol, a 3 GPP Long Term Evolution (LTE) protocol, a fifth-generation (5G) protocol, a New Radio (NR) protocol, and the like.

[0038] In an aspect, the UEs 101 and 102 may further directly exchange communication data via a ProSe interface 105. The ProSe interface 105 may alternatively be referred to as a sidelink interface comprising one or more logical channels, including but not limited to a Physical Sidelink Control Channel (PSCCH), a Physical Sidelink Shared Channel (PSSCH), a Physical Sidelink Discovery Channel (PSDCH), and a Physical Sidelink Broadcast Channel (PSBCH).

[0039] The UE 102 is shown to be configured to access an access point (AP) 106 via connection 107. The connection 107 can comprise a local wireless connection, such as, for example, a connection consistent with any IEEE 802. 11 protocol, according to which the AP 106 can comprise a wireless fidelity (WiFi®) router. In this example, the AP 106 is shown to be connected to the Internet without connecting to the core network of the wireless system (described in further detail below).

[0040] The RAN 110 can include one or more access nodes that enable the connections 103 and 104. These access nodes (ANs) can be referred to as base stations (BSs), NodeBs, evolved NodeBs (eNBs), Next Generation NodeBs (gNBs), RAN nodes, and the like, and can comprise ground stations (e.g., terrestrial access points) or satellite stations providing coverage within a geographic area (e.g., a cell). In some embodiments, the communication nodes 111 and 112 can be transmission/reception points (TRPs). In instances when the communication nodes 11 1 and 112 are NodeBs (e.g., eNBs or gNBs), one or more TRPs can function within the communication cell of the NodeBs. The RAN 110 may include one or more RAN nodes for providing macrocells, e.g,, macro RAN node 111, and one or more RAN nodes for providing femtocells or picocells (e.g., cells having smaller coverage areas, smaller user capacity, or higher bandwidth compared to macrocells), e.g., low power (LP) RAN node 112.

[0041] Any of the RAN nodes 111 and 112 can terminate the air interface protocol and can be the first point of contact for the UEs 101 and 102. In some embodiments, any of the RAN nodes 111 and 112 can fulfill various logical functions for the RAN 110 including, but not limited to, radio network controller (RNC) functions such as radio bearer management, uplink and downlink dynamic radio resource management and data packet scheduling, and mobility management. In an example, any of the nodes 111 and/or 1 12 can be a new generation Node-B (gNB), an evolved node-B (eNB), or another type of RAN node.

[0042] The RAN 110 is shown to be communicatively coupled to a core network (CN) 120 via an SI interface 113. In embodiments, the CN 120 may be an evolved packet core (EPC) network, a NextGen Packet Core (NPC) network, or some other type of CN (e.g., as illustrated in reference to FIGS. 1B-1C). In this aspect, the SI interface 113 is split into two parts: the Sl-U interface 114, which carries traffic data between the RAN nodes 111 and 112 and the serving gateway (S-GW) 122, and the S1 -mobility management entity (MME) interface 115, which is a signaling interface between the RAN nodes 111 and 112 and MMEs 121.

[0043] In this aspect, the CN 120 comprises the MMEs 121, the S-GW 122, the Packet Data Network (PDN) Gateway (P-GW) 123, and a home subscriber server (HSS) 124. The MMEs 121 may be similar in function to the control plane of legacy Serving General Packet Radio Serving (GPRS) Support Nodes (SGSN). The MMEs 121 may manage mobility embodiments in access such as gateway selection and tracking area list management. The HSS 124 may comprise a database for network users, including subscription-related information to support the network entities' handling of communication sessions. The CN 120 may comprise one or several HSSs 124, depending on the number of mobile subscribers, on the capacity of the equipment, on the organization of the network, etc. For example, the HSS 124 can provide support for routing/roaming, authentication, authorization, naming/addressing resolution, location dependencies, etc.

[0044] The S-GW 122 may terminate the SI interface 113 towards the RAN 110, and routes data packets between the RAN 110 and the CN 120. In addition, the S-GW 122 may be a local mobility anchor point for inter-RAN node handovers and also may provide an anchor for inter-3GPP mobility. Other responsibilities of the S-GW 122 may include a lawful intercept, charging, and some policy enforcement. [0045] The P-GW 123 may terminate an SGi interface toward a PDN. The P-GW 123 may route data packets between the EPC network 120 and external networks such as a network including the application server 184 (alternatively referred to as application function (AF)) via an Internet Protocol (IP) interface 125. The P-GW 123 can also communicate data to other external networks 131A, which can include the Internet, IP multimedia subsystem (IPS) network, and other networks. Generally, the application server 184 may be an element offering applications that use IP bearer resources with the core network (e.g., UMTS Packet Services (PS) domain, LTE PS data services, etc.). In this aspect, the P-GW 123 is shown to be communicatively coupled to an application server 184 via an IP interface 125. The application server 184 can also be configured to support one or more communication services (e.g., Voice-over- Internet Protocol (VoIP) sessions, PTT sessions, group communication sessions, social networking services, etc.) for the UEs 101 and 102 via the CN 120.

[0046] The P-GW 123 may further be a node for policy enforcement and charging data collection. Policy and Charging Rules Function (PCRF) 126 is the policy and charging control element of the CN 120. In a non-roaming scenario, in some embodiments, there may be a single PCRF in the Home Public Land Mobile Network (HPLMN) associated with a UE's Internet Protocol Connectivity Access Network (IP-CAN) session. In a roaming scenario with a local breakout of traffic, there may be two PCRFs associated with a UE's IP- CAN session: a Home PCRF (H-PCRF) within an HPLMN and a Visited PCRF (V-PCRF) within a Visited Public Land Mobile Network (VPLMN). The PCRF 126 may be communicatively coupled to the application server 184 via the P- GW 123.

[0047] In some embodiments, the communication network 140 A can be an loT network or a 5G network, including 5G new radio network using communications in the licensed (5G NR) and the unlicensed (5G NR-U) spectrum. One of the current enablers of loT is the narrowband-IoT (NB-IoT). [0048] An NG system architecture can include the RAN 110 and a 5G network core (5GC) 120. The NG- RAN 110 can include a plurality of nodes, such as gNBs and NG-eNBs. The core network 120 (e.g.. a 5G core network or 5GC) can include an access and mobility function ( AMF) and/or a user plane function (UPF). The AMF and the UPF can be communicatively coupled to the gNBs and the NG-eNBs via NG interfaces. More specifically, in some embodiments, the gNBs and the NG-eNBs can be connected to the AMF by NG- C interfaces, and to the UPF by NG-U interfaces. The gNBs and the NG-eNBs can be coupled to each other via Xn interfaces.

[0049] In some embodiments, the NG system architecture can use reference points between various nodes as provided by 3GPP Technical Specification (TS) 23,501 (e.g,, V15.4.0, 2018-12). In some embodiments, each of the gNBs and the NG-eNBs can be implemented as a base station, a mobile edge server, a small cell, a home eNB, and so forth. In some embodiments, a gNB can be a master node (MN) and NG-eNB can be a secondary node (SN) in a 5G architecture.

[0050] FIG. 1 B illustrates a non-roaming 5G system architecture in accordance with some embodiments. Referring to FIG. IB, there is illustrated a 5G system architecture MOB in a reference point representation. More specifically, UE 102 can be in communication with RAN 110 as well as one or more other 5G core (5GC) network entities. The 5G system architecture MOB includes a plurality of network functions (NT’s), such as access and mobility management function (AMF) 132, session management function (SMF) 136, policy control function (PCF) 148, application function (AF) 150, user plane function (UPF) 134, network slice selection function (NSSF) 142, authentication server function (AUSF) 144, and unified data management (UDM)/home subscriber server (HSS) 146. The UPF 134 can provide a connection to a data network (DN) 152, which can include, for example, operator services, Internet access, or third-party services. The AMF 132 can be used to manage access control and mobility and can also include network slice selection functionality. The SMF 136 can be configured to set up and manage various sessions according to network policy. The UPF 134 can be deployed in one or more configurations according to the desired service type. The PCF 148 can be configured to provide a policy framework using network slicing, mobility management, and roaming (similar to PCRF in a 4G communication system). The UDM can be configured to store subscriber profiles and data (similar to an HSS in a 4G communication system). [0051] In some embodiments, the 5G system architecture 140B includes an IP multimedia subsystem (IMS) 168B as well as a plurality of IP multimedia core network subsystem entities, such as call session control functions (CSCFs). More specifically, the IMS 168B includes a CSCF, which can act as a proxy CSCF (P-CSCF) 162BE, a serving CSCF (S-CSCF) 164B, an emergency CSCF (E-CSCF) (not illustrated in FIG. IB), or interrogating CSCF (I-CSCF) 166B. The P-CSCF 162B can be configured to be the first contact point for the UE 102 within the IM: subsystem (IMS) 168B. The S-CSCF 164B can be configured to handle the session states in the network, and the E-CSCF can be configured to handle certain embodiments of emergency sessions such as routing an emergency request to the correct emergency center or PSAP. The I-CSCF 166B can be configured to function as the contact point within an operator's network for all IMS connections destined to a subscriber of that network operator, or a roaming subscriber currently located within that network operator's service area. In some embodiments, the I-CSCF 166B can be connected to another IP multimedia network 170E, e.g. an IMS operated by a different network operator.

[0052] In some embodiments, the UDM/HSS 146 can be coupled to an application server 160E, which can include a telephony application server (TAS) or another application server (AS). The AS 160B can be coupled to the IMS 168B via the S-CSCF 164B or the I-CSCF 166B.

[0053] A reference point representation shows that interaction can exist between corresponding NF services. For example, FIG. 1 B illustrates the following reference points: N1 (between the UE 102 and the AMF 132), N2 (between the RAN 110 and the AMF 132), N3 (between the RAN 110 and the UPF 134), N4 (between the SMF 136 and the UPF 134), N5 (between the PCF 148 and the AF 150, not shown), N6 (between the UPF 134 and the DN 152), N7 (between the SMF 136 and the PCF 148, not shown), N8 (between the UDM 146 and the AMF 132, not shown), N9 (between two UPFs 134, not shown), N10 (between the UDM 146 and the SMF 136, not shown), N11 (between the AMF 132 and the SMF 136, not shown), N12 (between the AUSF 144 and the AMF 132, not shown), N13 (between the AUSF 144 and the UDM 146, not shown), N14 (between two AMFs 132, not shown), N15 (between the PCF 148 and the AMF 132 in case of a non-roaming scenario, or between the PCF 148 and a visited network and AMF 132 in case of a roaming scenario, not shown), N16 (between two SMFs, not shown), and N22 (between AMF 132 and NSSF 142, not shown). Other reference point representations not shown in FIG. IB can also be used.

[0054] FIG. 1C illustrates a 5G system architecture 140C and a sendee- based representation. In addition to the network entities illustrated in FIG. IB, system architecture 140C can also include a network exposure function (NEF) 154 and a network repository function (NRF) 156. In some embodiments, 5G system architectures can be service-based and interaction between network functions can be represented by corresponding point-to-point reference points Ni or as service-based interfaces.

[0055] In some embodiments, as illustrated in FIG. 1C, sendee-based representations can be used to represent network functions within the control plane that enable other authorized network functions to access their services. In this regard, 5G system architecture 140C can include the following sendee-based interfaces: Namf 158H (a service-based interface exhibited by the AMF 132), Nsmf 1581 (a sendee-based interface exhibited by the SMF 136), Nnef 158B (a service-based interface exhibited by the NEF 154), Npcf I 58D (a service-based interface exhibited by the PCF 148), a Nudm 158E (a sendee-based interface exhibited by the UDM 146), Naf 158F (a service-based interface exhibited by the AF 150), Nnrf 158C (a senice-based interface exhibited by the NRF 156), Nnssf 158A (a service-based interface exhibited by the NSSF 142), Nausf 158G (a senice-based interface exhibited by the AUSF 144). Other service-based interfaces (e.g., Nudr, N5g-eir, and Nudsf) not shown in FIG. 1C can also be used.

[0056] In some embodiments, any of the UEs or base stations described in connection with FIGS. 1 A-l C can be configured to perform the functionalities described herein.

[0057] Mobile communication has evolved significantly from early voice systems to today’s highly sophisticated integrated communication platform. The next generation wireless communication system, 5G, or new radio (NR) will provide access to information and sharing of data any where, anytime by various users and applications. NR is expected to be a unified net work/sy stem that targets to meet vastly different and sometimes conflicting performance dimensions and services. Such diverse multi-dirnensional requirements are driven by different services and applications. In general, NR will evolve based on 3GPP LTE-Advanced with additional potential new Radio Access Technologies (RATs) to enrich people's lives with better, simple, and seamless wireless connectivity solutions. NR will enable everything connected by wireless and deliver fast, rich content and services.

[0058] Rel-15 NR systems are designed to operate on the licensed spectrum . The NR-tmlicensed (NR-U), a short-hand notation of the NR -based access to unlicensed spectrum, is a technology that enables the operation of NR systems on the unlicensed spectrum.

[0059] In Rel-15 NR, 4-step random-access (RACH) procedure was defined. As illustrated in FIG. 2A, in the first step, UE transmits physical random-access channel (PRACH) in the uplink by selecting one preamble signature. Subsequently, in the second step, gNB feedbacks the random-access response (RAR) which carries timing advanced (TA) command information and uplink grant for the uplink transmission. Further, in the third step, UE transmits Msg3 physical uplink shared channel (PUSCH) which may carry contention resolution ID. In the fourth step, gNB sends the contention resolution message in physical downlink shared channel (PDSCH).

[0060] Further, in Rel-16 NR, 2-step RACH procedure was defined, with the motivation to allow fast access and low latency uplink transmission. As illustrated in FIG. 2B, in the first step, UE transmits a PRACH preamble and associated MsgA PUSCH on a configured time and frequency resource, where MsgA PUSCH may carry at least equivalent contents of Msg3 in 4-step RACH. In the second step, after successful detection of PRACH preamble and decoding of MsgA PUSCH, gNB transmits MsgB which may carry equivalent contents of Msg2 and Msg4 in 4-step RACH.

[0061] As defined in 4-step RACH, UE monitors physical downlink control channel (PDCCH) with Cyclic Redundancy Error (CRC) scrambled by a Random-access - Radio Network Temporary Identifier (RA-RNTI) in the second step for RAR reception. Note that the determination of RA-RNTI is described in Section 5.1.3 in TS38.321.

[0062] The RA-RNTI associated with the PRACH occasion in which the Random-access Preamble is transmitted, is computed as: [0063] RA-RNTI - 1 + s_id + 14 x t_id + 14 x 80 x f_id + 14 x 80 x 8 x ul_carrier_id

[0064] where s id is the index of the first OFDM symbol of the PRACH occasion (0 ≤ s_id < 14), t_id is the index of the first slot of the PRACH occasion in a system frame (0 ≤ t_id < 80), where the subcarrier spacing to determine t_id is based on the value of u specified in clause 5.3.2 in TS 38.211 , f_id is the index of the PRACH occasion in the frequency domain (0 ≤ f_id < 8), and ul_carrier_id is the UL carrier used for Random-access Preamble transmission (0 for NUL carrier, and 1 for SUL carrier).

[0065] For system operating above 52,6GHz carrier frequency, it. is envisioned that a larger subcarrier spacing is needed to combat severe phase noise. For instance, 480kHz or 960kHz or even larger subcarrier spacing may be employed for above 52.6GHz carrier frequency. Note that when large subcarrier spacing is used, the number of slots within 10ms frame boundary can be relatively large. In one example, when 960kHz subcarrier spacing is used, the number of slots within 10ms frame boundary is 640. In this case, if the existing RA-RNTI determination mechanism is reused, the maximum value of RA-RNTI is 143360, which is greater than 16-bit RNTI range. To address this issue, certain mechanism may need to be considered for the determination of RA-RNTI for system operating above 52.6GHz carrier frequency.

[0066] This disclosure describes mechanisms on determination of RA- RNTI and MsgB-RNTI for system operating above 52.6GHz earner frequency. For example, embodiments include:

[0067] PRACH configuration with large subcarrier spacing [0068] Determination of RA-RNTI and MsgB-RNTI

[0069] In NR Rel-15, as defined in 4-step RACH, UE monitors physical downlink control channel (PDCCH) with Cyclic Redundancy Error (CRC) scrambled by a Random-access - Radio Network Temporary Identifier (RA- RNTI) in the second step for RAR reception. Note that the determination of RA- RNTI is described in Section 5.1.3 in TS38.321.

[0070] The RA-RNTI associated with the PRACH occasion in which the Random-access Preamble is transmitted, is computed as: [0071] RA-RNTI - 1 + s_id + 14 x t_id + 14 x 80 x f id + 14 x 80 x 8 x ul_carrier_id

[0072] where s id is the index of the first OFDM symbol of the PRACH occasion (0 ≤ s_id < 14 ), t_id is the index of the first slot of the PRACH occasion in a system frame (0 ≤ t_id < 80), where the subcarrier spacing to determine t_id is based on the value of u specified in clause 5.3.2 in TS 38.211 , f_id is the index of the PRACH occasion in the frequency domain (0 ≤ f_id < 8), and ul_carrier_id is the UL carrier used for Random-access Preamble transmission (0 for NUL carrier, and 1 for SUL carrier).

[0073] Further, in Rel-16, for 2-step RACK. UE monitors PDCCH with CRC scrambled by a MsgB-RNTI in the second step. Note that the determination of MsgB-RNTI is described in Section 5.1 ,3a in TS38.321 .

[0074] The MSGB-RNTI associated with the PRACH occasion in which the Random-access Preamble is transmitted, is computed as:

[0075] MSGB-RNTI == 1 + s_id + 14 x t_id + 14 x 80 x f_id + 14 x 80 x 8 x ul_carrier_id + 14 x 80 x 8 x 2

[0076] where s_id is the index of the first OFDM symbol of the PRACH occasion (0 ≤ s id < 14), t_id is the index of the first slot of the PRACH occasion in a system frame (0 ≤ t_id < 80), where the subcarrier spacing to determine t_id is based on the value of p specified in clause 5.3.2 in TS 38.211 , f_id is the index of the PRACH occasion in the frequency domain (0 ≤ f_id < 8), and ul_carrier_id is the UL carrier used for Random-access Preamble transmission (0 for NUL carrier, and 1 for SUL carrier). The RA-RNTI is calculated as specified in clause 5.1.3.

[0077] PRACH configuration with large subcarrier spacing [0078] When large subcarrier spacing is employed for PRACH transmission, existing PRACH configuration may not be applied given that the number of slots in a frame is increased substantially. To minimize the specification impact, certain mechanisms may need to be defined for PRACH configuration with large subcarrier spacing.

[0079] Embodiments of PRACH configuration with large subcarrier spacing are provided as follows: [0080] In one embodiment of the disclosure, when large subcamer spacing, e.g., or subcarrier spacing is larger than 120kHz, is used for

transmission of PRACH preamble, 60kHz subcarrier spacing is used to determine the PRACH slot number, where P- is the index for subcarrier spacing. In other words, 0.25ms which is derived based on 60kHz subcarrier spacing is used for PRACH reference slot duration. This indicates that within PRACH reference slot, there are

PRACH slots when subcarrier spacing with

is used for PRACH transmission. For instance, for 960kHz subcarrier spacing, In this case, there are 16 slots within PRACH reference slots.

[0081] In one option, existing PRACH configuration table can be reused for system operating above 52.6GHz carrier frequency. Further, in the PRACH configuration, when 2 slots are allocated for PRACH reference slot, first or last slot within both PRACH slots based on 120kHz subcarrier spacing is used for PRACH transmission. Similarly, when 1 slot is allocated for PRACH reference slot, first or last slot within second PRACH slot based on 120kHz subcarrier spacing is used for PRACH transmission.

[0082] FIG. 3 illustrates one example of PRACH configuration when 960kHz subcarrier spacing is used for PRACH transmission. In this example, 60kHz subcarrier spacing is used to determine reference PRACH slot and PRACH configuration index of 88 in Table 1 (see FIG. 2C). Based on this PRACH configuration index, considering the first slot in the reference slot is used for PRACH transmission. In this case, slot index of {8, 24, 40, . . ., 632} is used for PRACH transmission with 960kHz subcarrier spacing.

[0083] FIG. 4 illustrates another example of PRACH configuration when 960kHz subcarrier spacing is used for PRACH transmission. In this example, 60kHz subcarrier spacing is used to determine reference PRACH slot and PRACH configuration index of 255 in Table 2 (see FIG. 2D). Based on this PRACH configuration index, considering the last slot in the reference PRACH slot is used for PRACH transmission. In this case, slot index of {31, 63, 95, . . ., 639} is used for PRACH transmission with 960kHz subcarrier spacing.

[0084] In another option, an existing PRACH configuration table can be reused for system operating above 52.6GHz carrier frequency. Further, in the PRACH configuration, when 2 slots are allocated for PRACH reference slot, first and second slot within reference PRACH slot is used for PRACH transmission. Similarly, when I slot is allocated for PRACH reference slot, first or second slot within reference PRACH slot is used for PRACH transmission. [0085] FIG. 5 illustrates one example of PRACH configuration when 960kHz subcarrier spacing is used for PRACH transmission. In this example, 60kHz subcarrier spacing is used to determine reference PRACH slot and PRACH configuration index of 88 in Table 1 (see FIG. 2C). Based on this PRACH configuration index, as 1 slot is allocated in the reference PRACH slot, slot index of { 1 , 17, . . . , 625 } is used for PRACH transmission with 960kHz subcarrier spacing.

[0086] In another embodiment of the disclosure, when large subcarrier spacing, e.g., is used for transmission of PRACH preamble, subcarrier

spacing with

is used to determine the PRACH slot number. In this case, two PRACH slots are allocated within the PRACH reference slot based on subcarrier spacing with

A For instance, when 960kHz subcarrier spacing is used for PRACH preamble, 480kHz subcarrier spacing is used to determine PRACH slot, number.

[0087] Note that the existing PRACH configuration table can be reused for system operating above 52.6GHz carrier frequency. Further, in the PRACH configuration, when 2 PRACH slots are allocated in the reference PRACH slot, both slots are used for PRACH transmission. When 1 PRACH slot is allocated in the reference PRACH slot, only second slot within the PRACH reference slot is used for PRACH transmission.

[0088] FIG. 6 illustrates one example of PRACH configuration when 960kHz subcarrier spacing is used for PRACH transmission. In this example, 480kHz subcarrier spacing is used to determine reference PRACH slot and PRACH configuration index of 255 in Table 2 (see FIG. 2D). Based on this PRACH configuration index, slot index of {3, 7, 11, . . ., 79} is used for PRACH transmission with 960kHz subcarrier spacing.

[0089] In another embodiment of the disclosure, when large subcarrier spacing, e.g.,

is used for transmission of PRACH preamble, subcarrier spacing with

is used to determine the PRACH slot number, where is

the minimum value of in a frequency range. In this case, one or two PRACH slots are allocated within the PRACH reference slot based on subcarrier spacing with For instance, when 240kHz subcarrier spacing is the minimum supported subcarrier spacing in the frequency range and 960kHz subcarrier spacing is used for PRACH preamble, 240kHz subcarrier spacing is used to determine PRACH slot number.

[0090] In another embodiment of the disclosure, when large subcarrier spacing, e.g.,

is used for transmission of PRACH preamble, a number of consecutive ROs can be allocated with or without gap starting from a symbol in a slot. The consecutive ROs may be mapped to the time resource in multiple consecutive slots. For instance, the number of ROs, the slot index and the symbol index in the slot can be determined by a row of a table for PRACH configuration. For larger subcarrier spacing, the number of symbols of a PRACH preamble may need to be increased, otherwise, the supported coverage of the preamble is too short. Further, for larger subcarrier spacing, if the adjacent RO corresponds to different RX beam at gNB side, gNB may need one or more symbols for RX beam switching for the detection of PRACH preamble.

[0091] Determination of RA-RNTI and MsgB-RNTI

[0092] As mentioned above, for system operating above 52.6GHz carrier frequency, it is envisioned that a larger subcarrier spacing is needed to combat severe phase noise. For instance, 480kHz or 960kHz or even larger subcarrier spacing may be employed for above 52.6GHz carrier frequency. Note that when large subcarrier spacing is used, the number of slots within 10ms frame boundary can be relatively large. In one example, when 960kHz subcarrier spacing is used, the number of slots within 10ms frame boundary is 640. In this case, if the existing RA-RNTI determination mechanism is reused, the maximum value of RA-RNTI is 143360, which is greater than 16-bit RNTI range. To address this issue, certain mechanism may need to be considered for the determination of RA-RNTI for system operating above 52.6GHz carrier frequency. In general, the RA-RNTI and MsgB-RNTI could be determined as

[0093]

[0094] are predefined functions. S, T, F are predefined

values in the specification or can be configured by high layer signaling. [0095] Embodiment of determination of RA-RNTI and MsgB-RNTI tor 4-step RACH and 2-step RACH, respectively, are provided as follows:

[0096] In one embodiment of the disclosure, when large subcarrier spacing, e.g.,

is used for transmission of PRACH preamble, symbol index and/or slot index in RA-RNTI and MsgB-RNTI determination can be replaced by taking modulo or floor operation. In particular, s id in the equation may be replaced by mod(s_id, 2) or mod( Further, t_id may be replaced by

o_{r mo}d(t_id, 80) or where mod is

modulo operation and J is floor operation.

[0097] For RA-RNTI determination, in one example, for PRACH transmission with 960kHz subcarrier spacing, the following text in Section 5.1.3 in TS38.321 can be updated.

[0098] The RA-RNTI associated with the PRACH occasion in which the Random-access Preamble is transmitted, is computed as:

[0099] RA-RNTI = 1 + s_ id + 14 x

+ 14 x 80 x f_id + 14 x 80 x 8 x ul carrier id

[00100] where s__id is the index of the first OFDM symbol of the PRACH occasion (0 ≤ s id < 14), t_id is the index of the first slot of the PRACH occasion in a system frame (0 ≤ t_id < 640), where the subcarrier spacing to determine t_id is based on the value of

specified in clause 5.3.2 in TS 38.211 , f_id is the index of the PRACH occasion in the frequency domain (0 ≤ f_id < 8), and ul carrier id is the UL carrier used for Random-access Preamble transmission (0 for NUL carrier, and 1 for SUL carrier).

[00101] In another example, for PRACH transmission with 960kHz subcarrier spacing, the following text in Section 5.1.3 in TS38.321 can be updated.

[00102] The RA-RNTI associated with the PRACH occasion in which the Random-access Preamble is transmitted, is computed as:

[00103] RA-RNTI - 1 + _s id + 14 x mod(t_id, 80) + 14 x 80 x f jd + 14 x 80 x 8 x ul_carrier_id

[00104] where s id is the index of the first OFDM symbol of the PRACH occasion (0 ≤ s__id < 14), t__id is the index of the first slot of the PRACH occasion in a system frame (0 ≤ t_id < 640), where the subcarrier spacing to determine t_id is based on the value of specified m clause 5.3.2 in TS 38.211 , f_id is the index of the PRACH occasion in the frequency domain (0 ≤ f_id < 8), and ul carrier id is the UL carrier used for Random-access Preamble transmission (0 for NUL carrier, and 1 for SUL carrier).

[00105] In another example, for PRACH transmission with 960kHz subcarrier spacing, the following text in Section 5.1.3 in TS38.321 can be updated.

[00106] The RA-RNTI associated with the PRACH occasion in which the Random-access Preamble is transmitted, is computed as:

[00107] RA-RNTI - 1 + s_id + 14 x ₊ 14 _x 80

x f_id + 14 x 80 x 8 x ul_carrier_id

[00108] where s id is the index of the first OFDM symbol of the PRACH occasion (0 ≤ s_id < 14), t__id is the index of the first slot of the PRACH occasion in a system frame (0 ≤ t_id < 640), where the subcarrier spacing to determine t_id is based on the value of p specified in clause 5.3.2 in TS 38.211 , f_id is the index of the PRACH occasion in the frequency domain (0 ≤ f_id < 8), and ul_carrier_id is the UL carrier used for Random-access Preamble transmission (0 for NUL carrier, and 1 for SUL carrier).

[00109] In another example, for PRACH transmission with 960kHz subcarrier spacing, the following text in Section 5.1.3 in TS38.321 can be updated.

[00110] The RA-RNTI associated with the PRACH occasion in which the Random-access Preamble is transmitted, is computed as:

[00111] RA-RNTI - 1 + s_id + 14 x + 14

x 80 x f_id + 14 x 80 x 8 x ul_carrier_id

[00112] where s id is the index of the first OFDM symbol of the PRACH occasion (0 ≤ s_id < 14), t_id is the index of the first slot of the PRACH occasion in a system frame (0 ≤ t_id < 640), where the subcarrier spacing to determine t_id is based on the value of u specified in clause 5.3.2 in TS 38.211 , f_id is the index of the PRACH occasion in the frequency domain (0 ≤ f_id < 8), and ul_carrier_id is the UL carrier used for Random-access Preamble transmission (0 for NUL carrier, and 1 for SUL carrier). [00113] For MsgB-RNTI determination, in one example, for PRACH transmission with 960kHz subcarrier spacing, the following text in Section 5.1.3a in TS38.321 can be updated.

[00114] The MSGB-RNTI associated with the PRACH occasion in which the Random-access Preamble is transmitted, is computed as:

[00115] MSGB-RNTI - 1 + s id + 14 *

_{+ 34 x} 80 * f_id + 14 x 80 x 8 x ul_carrier_id + 14 x 80 x 8 + 2

[00116] where s id is the index of the first OFDM symbol of the PRACH occasion (0 ≤ s id < 14), t_id is the index of the first slot of the PRACH occasion in a system frame (0 ≤ t_id < 640), where the subcarrier spacing to determine t__id is based on the value of

specified in clause 5.3.2 in TS 38.211 , f_id is the index of the PRACH occasion in the frequency domain (0 ≤ f_id < 8), and ul_carrier_id is the UL carrier used for Random-access Preamble transmission (0 for NUL carrier, and 1 for SUL carrier). The RA-RNTI is calculated as specified in clause 5.1.3.

[00117] In another example, for PRACH transmission with 960kHz subcarrier spacing, the following text in Section 5.1.3 in TS38.321 can be updated.

[00118] The MSGB-RNTI associated with the PRACH occasion in which the Random-access Preamble is transmitted, is computed as:

[00119] MSGB-RNTI - 1 + s id + 14 x mod(t_id, 80) + 14 x 80 x f_id + 14 x 80 x 8 x ul_carrier_id + 14 x 80 x 8 x 2

[00120] where s id is the index of the first OFDM symbol of the PRACH occasion (0 ≤ s_id < 14), t_id is the index of the first slot of the PRACH occasion in a system frame (0 ≤ t_id < 640), where the subcarrier spacing to determine t_id is based on the value of specified in clause 5.3.2 in TS 38.211 ,

f_id is the index of the PRACH occasion in the frequency domain (0 ≤ f_id < 8), and ul_carrier_id is the UL carrier used for Random-access Preamble transmission (0 for NUL carrier, and 1 for SUL carrier). The RA-RNTI is calculated as specified in clause 5.1.3.

[00121] In another example, for PRACH transmission with 960kHz subcarrier spacing, the following text in Section 5.1.3 in TS38.321 can be updated. [00122] The MSGB-RNTI associated with the PRACH occasion m which the Random-access Preamble is transmitted, is computed as:

[00123] MSGB-RNTI = 1 + s id + 14 x _{+ 14}

x 80 x f_id + 14 x 80 x 8 x ul_carrier_id + 14 x 80 x 8 x 2

[00124] where s__id is the index of the first OFDM symbol of the PRACH occasion (0 ≤ s id < 14), t. id is the index of the first slot of the PRACH occasion in a system frame (0 ≤ t_id < 640), where the subcarrier spacing to determine t_id is based on the value of u specified in clause 5.3.2 in TS 38.211 , f_id is the index of the PRACH occasion in the frequency domain (0 ≤ f_id < 8), and ul carrier id is the UL carrier used for Random-access Preamble transmission (0 for NUL carrier, and 1 for SUL carrier). The RA-RNTI is calculated as specified in clause 5.1.3.

[00125] In another embodiment of the disclosure, when large subcarrier spacing, e.g.,

, is used for transmission of PRACH preamble, considering only a limited number of PRACH occasions may be configured within a channel bandwidth, the range of f_id may be reduced accordingly.

[00126] In one example, only one RO is configured within a channel bandwidth. In this case, For RA-RNTI determination, and for PRACH transmission with 960kHz subcarrier spacing, the following text in Section 5.1.3 in TS38.321 can be updated.

[00127] The RA-RNTI associated with the PRACH occasion in which the Random-access Preamble is transmitted, is computed as:

[00128] RA-RNTI = 1 + s id + 14 x t_id + 14 x 80 x ul_carrier _id

[00129] where s __id is the index of the first OFDM symbol of the PRACH occasion (0 ≤ s id < 14), t_id is the index of the first slot of the PRACH occasion in a system frame (0 ≤ t_id < 640), where the subcarrier spacing to determine t__id is based on the value of p specified in clause 5.3.2 in TS 38.211 , f_id is the index of the PRACH occasion in the frequency domain (0 ≤ f_id < 8), and ul_carrier_id is the UL carrier used for Random-access Preamble transmission (0 for NUL carrier, and 1 for SUL carrier).

[00130] For MsgB-RNTI determination, in one example, for PRACH transmission with 960kHz subcarrier spacing, the following text in Section 5.1.3a in TS38.321 can be updated. [00131] The MSGB-RNTI associated with the PRACH occasion in which the Random-access Preamble is transmitted, is computed as:

[00132] MSGB-RNTI :::: 1 + s id + 14 x t_id + 14 x 80 x ul_carrier_id + 14 x 80 x 2

[00133] where s id is the index of the first OFDM symbol of the PRACH occasion (0 ≤ s __id < 14), t__id is the index of the first slot of the PRACH occasion in a system frame (0 ≤ t_id < 640), where the subcarrier spacing to determine t_id is based on the value of p specified in clause 5.3.2 in TS 38.21 1 , f_id is the index of the PRACH occasion in the frequency domain (0 ≤ f_id < 8), and ul_carrier_id is the UL carrier used for Random-access Preamble transmission (0 for NUL carrier, and 1 for SUL carrier). The RA-RNTI is calculated as specified in clause 5.1.3.

[00134] In another embodiment of the disclosure, when large subcarrier spacing, e.g.,

is used for PRACH preamble, in order to ensure the RA- RNTI and MsgB-RNTI within 16-bit RNTI range, a modulo operation can be applied on the existing RA-RNTI and MsgB-RNTI determination.

[00135] In particular, RA-RNTI can be determined as

[00136] RA-RNTI = mod(l + s__id + 14 x t__id + 14 x 80 x f_id + 14 x 80 x 8 x ul_carrier_id, N),

[00137] where N can be predefined in the specification or can be configured by high layer signaling. For instance, N = 66519, or 17920

or 35840, or N =^;: 14 x 80 x 8 x ul_carrier_id M-- I .

[00138] Similarly, MsgB-RNTI can be determined as

[00139] M:SGB-RNTI - modi ’ + s id + 14 x t_id + 14 x 80 x f_id + 14 x 80 x 8 x ul_carrier_id + 14 x 80 x 8 x 2, N)

[00140] where N can be predefined in the specification or can be configured by high layer signaling. For instance, N = 66519, or 17920

or 35840, or N = 14 x 80 x 8 x ul_carrier_id M - 1.

[00141] In another embodiment of the disclosure, the above options can be combined for the determination of RA-RNTI and MsgB-RNTI, when large subcarrier spacing, e.g.,

is used for transmission of PRACH preamble. For instance, t_id may be replaced by

and f_id is removed from the

RA-RNTI and Msg-RNTI determination. [00142] FIG. 7 illustrates PRACH slots identified to align with slots based on a 120 kHz subcarrier spacing, in accordance with some other embodiments. In these embodiments, the PRACH slots identified by the UE for transmission of the PRACH preamble are aligned with slots based on the 120 kHz SCS.

[00143] FIG. 8 illustrates a functional block diagram of a wireless communication device, in accordance with some embodiments. Wireless communication device 800 may be suitable for use as a UE in some embodiments. Wireless communication device 800 may also be suitable for use as a gNB or other network node, in some embodiments. The communication device 800 may also be suitable for use as a handheld device, a mobile device, a cellular telephone, a smartphone, a tablet, a netbook, a wireless terminal, a laptop computer, a wearable computer device, a femtocell, a high data rate (HDR) subscriber device, an access point, an access terminal, or other personal communication system (PCS) device.

[00144] The communication device 800 may include communications circuitry’ 802 and a transceiver 810 for transmitting and receiving signals to and from other communication devices using one or more antennas 801. The communications circuitry 802 may include circuitry' that can operate the physical layer (PHY) communications and/or medium access control (MAC) communications for controlling access to the wireless medium, and/or any other communications layers for transmitting and receiving signals. The communication device 800 may also include processing circuitry 806 and memory 808 arranged to perform the operations described herein. In some embodiments, the communications circuitry 802 and the processing circuitry 806 may be configured to perform operations detailed in the above figures, diagrams, and flow's.

[00145] In accordance with some embodiments, the communications circuitry 802 may be arranged to contend for a wireless medium and configure frames or packets for communicating over the wireless medium. The communications circuitry' 802 may be arranged to transmit and receive signals. The communications circuitry/ 802 may also include circuitry' for m odul ation/dem odul ation, upconversi on/downconversi on, filtering, amplification, etc. In some embodiments, the processing circuitry/ 806 of the communication device 800 may include one or more processors. In other embodiments, two or more antennas 801 may be coupled to the communications circuitry 802 arranged for sending and receiving signals. The memory 808 may store information for configuring the processing circuitry 806 to perform operations for configuring and transmitting message frames and performing the various operations described herein. The memory 808 may include any type of memory, including non-transitory memory, for storing information in a form readable by a machine (e.g., a computer). For example, the memory 808 may include a computer-readable storage device, read-only memory (ROM), random- access memory (RAM), magnetic disk storage media, optical storage media, flash-memory devices and other storage devices and media.

[00146] In some embodiments, the communication device 800 may be part of a portable wireless communication device, such as a personal digital assistant (PDA), a laptop or portable computer with wireless communication capability, a web tablet, a wireless telephone, a smartphone, a wireless headset, a pager, an instant messaging device, a digital camera, an access point, a television, a medical device (e.g., a heart rate monitor, a blood pressure monitor, etc.), a wearable computer device, or another device that may receive and/or transmit information wirelessly.

[00147] In some embodiments, the communication device 800 may include one or more antennas 801. The antennas 801 may include one or more directional or omnidirectional antennas, including, for example, dipole antennas, monopole antennas, patch antennas, loop antennas, microstrip antennas, or other types of antennas suitable for transmission of RF signals. In some embodiments, instead of two or more antennas, a single antenna with multiple apertures may be used. In these embodiments, each aperture may be considered a separate antenna. In some multiple-input multiple-output (MIMO) embodiments, the antennas may be effectively separated for spatial diversity and the different channel characteristics that may result between each of the antennas and the antennas of a transmitting device.

[00148] In some embodiments, the communication device 800 may include one or more of a keyboard, a display, a non-volatile memory port, multiple antennas, a graphics processor, an application processor, speakers, and other mobile device elements. The display may be an LCD screen including a touch screen . [00149] Although the communication device 800 is illustrated as having several separate functional elements, two or more of the functional elements may be combined and may be implemented by combinations of software-configured elements, such as processing elements including digital signal processors (DSPs), and/or other hardware elements. For example, some elements may include one or more microprocessors, DSPs, field-programmable gate arrays (FPGAs), application specific integrated circuits (ASICs), radio-frequency integrated circuits (RFICs) and combinations of various hardware and logic circuitry for performing at least the functions described herein. In some embodiments, the functional elements of the communication device 800 may refer to one or more processes operating on one or more processing elements.

[00150] Examples:

[00151] Example 1 may include a method of wireless communication for a fifth generation (5G) or new radio (NR) system, the method comprising: [00152] Configuring, by gNodeB (gNB), a physical random-access channel (PRACH) configuration index when large subcarrier spacing is used for PRACH preamble;

[00153] Transmitting, by UE, a PRACH preamble in accordance with the PRACH configuration index.

[00154] Example 2 may include the method of example 1 or some other example herein, wherein when large subcarrier spacing, e.g., or subcarrier

spacing is larger than 120kHz, is used for transmission of PRACH preamble, 60kHz subcarrier spacing is used to determine the PRACH slot number, where is the index for subcarrier spacing.

[00155] Example 3 may include the method of example 2 or some other example herein, wherein in the PRACH configuration, when 2 slots are allocated for PRACH reference slot, first or last slot within both PRACH slots based on 120kHz subcarrier spacing is used for PRACH transmission; wherein when 1 slot is allocated for PRACH reference slot, first or last slot within second PRACH slot based on 120kHz subcarrier spacing is used for PRACH transmission.

[00156] Example 4 may include the method of example 2 or some other example herein, wherein existing PRACH configuration table can be reused for system operating above 52,6GHz carrier frequency. Further, m the PRACH configuration, when 2 slots are allocated for PRACH reference slot, first and second slot within reference PRACH slot is used for PRACH transmission; wherein when 1 slot is allocated for PRACH reference slot, first or second slot within reference PRACH slot is used for PRACH transmission.

[00157] Example 5 may include the method of example 1 or some other example herein, wherein when large subcarrier spacing, e.g.,

, is used for transmission of PRACH preamble, subcarrier spacing with

is used to determine the PRACH slot number.

[00158] Example 6 may include the method of example 5 or some other example herein, wherein in the PRACH configuration, when 2 PRACH slots are allocated in the reference PRACH slot, both slots are used for PRACH transmission; wherein when 1 PRACH slot is allocated in the reference PRACH slot, only second slot within the PRACH reference slot is used for PRACH transmission.

[00159] Example 7 may include the method of example 1 or some other example herein, wherein when large subcarrier spacing, e.g.,

is used for transmission of PRACH preamble, subcarrier spacing with

is used to determine the PRACH slot number, where is the minimum value of in a

frequency range.

[00160] Example 8 may include the method of example 1 or some other example herein, wherein when large subcarrier spacing, e.g.,

is used for transmission of PRACH preamble, a number of consecutive ROs can be allocated with or without gap starting from a symbol in a slot

[00161] Example 9 may include the method of example 1 or some other example herein, wherein when large subcarrier spacing, e.g.,

is used for transmission of PRACH preamble, symbol index and/or slot index in RA-RNTI and MsgB-RNTI determination can be replaced by taking modulo or floor operation.

[00162] Example 10 may include the method of example 9 or some other example herein, wherein s id in the equation may be replaced by mod(s_id, 2). Further, t_id may be replaced by floor(t_id, ) or mod(t_id, 80). [00163] Example 1 1 may include the method of example 1 or some other example herein, wherein when large subcarrier spacing, e.g.,

is used for transmission of PRACH preamble, considering only a limited number of PRACH occasions may be configured within a channel bandwidth, the range of f_id may be reduced accordingly.

[00164] Example 12 may include the method of example 1 or some other example herein, wherein when large subcarrier spacing, e.g., is used for

PRACH preamble, in order to ensure the RA-RNTI and MsgB-RNTI within 16- bit RNTI range, a modulo operation can be applied on the existing RA-RNTI and MsgB-RNTI determination.

[00165] Example 13 may include a method comprising:

[00166] receiving a physical random-access channel (PRACH) configuration index; and

[00167] encoding a PRACH preamble for transmission based on the PRACH configuration index.

[00168] Example 14 may include the method of example 13 or some other example herein, wherein the PRACH preamble is based on the PRACH configuration index if a subcarrier spacing is greater than a threshold.

[00169] Example 15 may include the method of example 13-14 or some other example herein, further comprising determining a slot number of the PRACH preamble based on the PRACH configuration index.

[00170] Example 16 may include the method of example 13-15 or some other example herein, wherein the PRACH configuration index is received from a gNB.

[00171] Example 17 may include the method of example 13-16 or some other example herein, wherein the method is performed by a UE or a portion thereof.

[00172] The Abstract is provided to comply with 37 C.F.R. Section

1.72(b) requiring an abstract that will allow the reader to ascertain the nature and gist of the technical disclosure. It is submitted with the understanding that it will not be used to limit or interpret the scope or meaning of the claims. The following claims are hereby incorporated into the detailed description, with each claim standing on its own as a separate embodiment.

Claims

CLAIMS What is claimed is:

1. An apparatus of a user equipment (UE) configured for operation in a fifth -generation (5G) new radio (NR) system (5GS), the apparatus comprising: processing circuitry; and memory, wherein for operating above a 52.6 GHz carrier frequency when a physical random-access channel (PRACH) subcarrier spacing (SCS) is used for transmission of a PRACH preamble, the processing circuitry is configured to: identify a reference PRACH slot based on a reference SCS; identify one or more PRACH slots within the reference PRACH slot based on a PRACH configuration index, for transmission of the PRACH preamble, the one or more PRACH slots based on the PRACH SCS, the PRACH SCS being larger than the reference SCS; and encode the PRACH preamble for transmission to a generation Node B (gNB) in a PRACH occasion corresponding to the one or more PRACH slots to perform a random-access channel (RACH) procedure.

2. The apparatus of claim 1, wherein when the PRACH SCS comprises one of a 480 kHz SCS or a 960 kHz SCS, and when the reference SCS is a 60 kHz SCS, the processing circuitry is configured to use the 60 kHz SCS to determine a location of the PRACH slots for transmission of the PRACH preamble, the PRACH slots based on the PRACH SCS, and wherein when the PRACH SCS comprises one of the 480 kHz SCS or the 960 kHz SCS, and when the reference SCS is a 120 kHz SCS, the processing circuity is configured to use the 120 kHz SCS to determine the location of the PRACH slots for transmission of the PRACH preamble, the PRACH slots based on the PRACH SCS.

3. The apparatus of claim 2, wherein when the reference SCS is the 60 kHz SCS and when the PRACH SCS is either the 480 kHz SCS or 960 kHz SCS, the reference PRACH slot comprises two 120 kHz SCS slots that are based on the 120 kHz SCS; and when two PRACH slots are indicated by the PRACH configuration index within the reference PRACH slot, either a first or a last slot within each 120 kHz SCS slot are identified by the UE as the PRACH slots for transmission of the PRACH preamble, the PRACH slots identified by the UE being based on the PRACH SCS.

4. The apparatus of claim 3, wherein when the reference SCS is the 60 kHz SCS and when the PRACH SCS is either the 480 kHz SCS or 960 kHz SCS, the reference PRACH slot comprises the two 120 kHz SCS slots that are based on the 120 kHz SCS; and wherein when one PRACH slot is indicated by the PRACH configuration index within the reference PRACH slot, either a first or a last slot within one of the two 120 kHz SCS slots is identified by the UE as the PRACH slot for transmission of the PRACH preamble, the PRACH slot identified by the UE being based on the PRACH SCS.

5. The apparatus of claim 2, wherein when the reference SCS is the 60 kHz SCS and when the PRACH SCS is either the 480 kHz SCS or 960 kHz SCS, the reference PRACH slot comprises two 120 kHz SCS slots that are based on the 120 kHz SCS, when two PRACH slots are indicated by the PRACH configuration index within the reference PRACH slot, a slot within each 120 kHz SCS slot is identified by the UE as the PRACH slots for transmission of the PRACH preamble, the PRACH slots identified by the UE being based on the PRACH SCS, wherein when only one PRACH slot is indicated by the PRACH configuration index within the reference PRACH slot, a slot within either the first or the second 120 kHz SCS slot is identified by the UE as the PRACH slot for transmission of the PRACH preamble, the PRACH slot identified by the UE being based on the PRACH SCS, and wherein the slot within each 120 kHz SCS slot or the slot within either the first or the second 120 kHz SCS slot are identified by the UE based on predefined slot index.

6. The apparatus of claim 2, wherein when the PRACH SCS comprises the 960 kHz SCS, and when the reference SCS is the 480 kHz SCS, the processing circuitry is configured to use the 480 kHz SCS to determine a location of the PRACH slots for transmission of the PRACH preamble, the PRACH slots based on the 960 kHz SCS.

7. The apparatus of claim 2, wherein for a 4-step RACH procedure, the processing circuitry is further configured to: calculate a Random-Access Radio Network Temporary Identifier (RA- RNTI); and configure the UE to monitor a physical downlink control channel (PDCCH) with Cyclic Redundancy Check (CRC) scrambled by the RA-RNTI for a random-access response (RAR) from the gNB, wherein the RA-RNTI is calculated using a modulo or floor operation.

8. The apparatus of claim 7, wherein for a 2-step RACH procedure, the processing circuitry is configured to: encode the PRACH preamble for transmission along with a physical uplink shard channel (PUSCH) payload, determine a MsgB-RNTI; and configure the UE to monitor the PDCCH with a CRC scrambled by the MsgB-RNTI from the gNB, wherein the processing circuitry is configured to determine the MsgB- RNTI using a modulo or floor operation.

9. The apparatus of claim 8, wherein the processing circuitry is further configured to: decode a system information block (SIB1) received from the gNB, the SIB 1 including a PRACH configuration that includes the PRACH configuration index.

10. The apparatus of claim 1, wherein the processing circuitry comprises a baseband processor, and wherein the memory is configured to store the PRACH configuration index.

11. A non-transitory computer-readable storage medium that stores instructions for execution by processing circuitry of a user equipment (LIE) configured for operation in a fifth-generation (5G) new radio (NR) system (5GS), wherein for operating above a 52.6 GHz carrier frequency when a physical random-access channel (PRACH) subcarrier spacing (SCS) is used for transmission of a PRACH preamble, the processing circuitry' is configured to: identify a reference PRACH slot based on a reference SCS; identify one or more PRACH slots within the reference PRACH slot based on a PRACH configuration index, for transmission of the PRACH preamble, the one or more PRACH slots based on the PRACH SCS, the PRACH SCS being larger than the reference SCS; and encode the PRACH preamble for transmission to a generation Node B (gNB) in a PRACH occasion corresponding to the one or more PRACH slots to perform a random-access channel (RACH) procedure.

12. The non-transitory computer-readable storage medium of claim 11, wherein when the PRACH SCS comprises one of a 480 kHz SCS or a 960 kHz SCS, and when the reference SCS is a 60 kHz SCS, the processing circuitry is configured to use the 60 kHz SCS to determine a location of the PRACH slots for transmission of the PRACH preamble, the PRACH slots based on the PRACH SCS, and wherein when the PRACH SCS comprises one of the 480 kHz SCS or the 960 kHz SCS, and when the reference SCS is a 120 kHz SCS, the processing circuity is configured to use the 120 kHz SCS to determine the location of the PRACH slots for transmission of the PRACH preamble, the PRACH slots based on the PRACH SCS.

13. The non-transitory computer-readable storage medium of claim 12, wherein when the reference SCS is the 60 kHz SCS and when the PRACH SCS is either the 480 kHz SCS or 960 kHz SCS, the reference PRACH slot comprises two 120 kHz SCS slots that are based on the 120 kHz SCS; and when two PRACH slots are indicated by the PRACH configuration index within the reference PRACH slot, either a first or a last slot within each 120 kHz SCS slot are identified by the UE as the PRACH slots for transmission of the PRACH preamble, the PRACH slots identified by the UE being based on the PRACH SCS.

14. The non-transitory computer-readable storage medium of claim 13, wherein when the reference SCS is the 60 kHz SCS and when the PRACH SCS is either the 480 kHz SCS or 960 kHz SCS, the reference PRACH slot comprises the two 120 kHz SCS slots that are based on the 120 kHz SCS; and wherein when one PRACH slot is indicated by the PRACH configuration index within the reference PRACH slot, either a first or a last slot within one of the two 120 kHz SCS slots is identified by the UE as the PRACH slot for transmission of the PRACH preamble, the PRACH slot identified by the UE being based on the PRACH SCS.

15. The non-transitory computer-readable storage medium of claim 12, wherein when the reference SCS is the 60 kHz SCS and when the PRACH SCS is either the 480 kHz. SCS or 960 kHz SCS, the reference PRACH slot comprises two 120 kHz SCS slots that are based on the 120 kHz SCS, when two PRACH slots are indicated by the PRACH configuration index within the reference PRACH slot, a slot within each 120 kHz SCS slot is identified by the UE as the PRACH slots for transmission of the PRACH preamble, the PRACH slots identified by the UE being based on the PRACH SCS, wherein when only one PRACH slot is indicated by the PRACH configuration index within the reference PRACH slot, a slot within either the first or the second 120 kHz SCS slot is identified by the UE as the PRACH slot for transmission of the PRACH preamble, the PRACH slot identified by the UE being based on the PRACH SCS, and wherein the slot within each 120 kHz SCS slot or the slot within either the first or the second 120 kHz SCS slot are identified by the UE based on predefined slot index.

16. The non-transitory computer-readable storage medium of claim 12, wherein when the PRACH SCS comprises the 960 kHz SC’S, and when the reference SCS is the 480 kHz SCS, the processing circuitry is configured to use the 480 kHz SCS to determine a location of the PRACH slots for transmission of the PRACH preamble, the PRACH slots based on the 960 kHz SCS.

17. The non-transitory computer-readable storage medium of claim 12, wherein for a 4-step RACH procedure, the processing circuitry is further configured to: calculate a Random-Access Radio Network Temporary Identifier (RA- RNTI); and configure the UE to monitor a physical downlink control channel (PDCCH) with Cyclic Redundancy Check (CRC) scrambled by the RA-RNTI for a random-access response (RAR) from the gNB, wherein the RA-RNTI is calculated using a modulo or floor operation.

18. The non-transitory computer-readable storage medium of claim 17, wherein for a 2-step RACH procedure, the processing circuitry/ is configured to: encode the PRACH preamble for transmission along with a physical uplink shard channel (PUSCH) payload; determine a MsgB-RNTI; and configure the UE to monitor the PDCCH with a CRC scrambled by the MsgB-RNTI from the gNB, wherein the processing circuitry is configured to determine the MsgB- RNTI using a modulo or floor operation.

19. An apparatus of a generation Node B (gNB) configured for operation in a fifth-generation (5G) new radio (NR) system (5GS), the apparatus comprising: processing circuitry/; and memory, wherein for operating above a 52.6 GHz carrier frequency when a phy sical random-access channel (PRACH) subcarrier spacing (SCS) is used for transmission of a PRACH preamble by a user equipment (UE), the processing circuitry is configured to: identify a reference PRACH slot based on a reference SCS; identify one or more PRACH slots within the reference PRACH slot based on a PRACH configuration index, the one or more PRACH slots based on the PRACH SCS, the PRACH SCS being larger than the reference SCS; and decode the PRACH preamble received from the UE in a PRACH occasion corresponding to the one or more PRACH slots to perform a random- access channel (RACH) procedure.

20. The apparatus of claim 19, wherein when the PRACH SCS comprises one of a 480 kHz SCS or a 960 kHz SCS, and when the reference SCS is a 60 kHz SCS, the processing circuitry is configured to use the 60 kHz SCS to determine a location of the PRACH slots for reception of the PRACH preamble from the UE, the PRACH slots based on the PRACH SCS, and wherein when the PRACH SCS comprises one of the 480 kHz SCS or the 960 kHz SCS, and when the reference SCS is a 120 kHz SCS, the processing circuity is configured to use the 120 kHz SCS to determine the location of the PRACH slots for reception of the PRACH preamble from the UE, the PRACH slots based on the PRACH SCS.