Method, apparatus, and machine-readable medium for communication

Abstract

The present invention discloses an apparatus, a method, and a machine-readable medium for implementing the method of a New Radio (NR) evolved Node B (gNodeB). The method includes: processing a first signal sent by the NR evolved Node B (gNodeB) regarding a primary Physical Random Access Channel (PRACH) configuration to be used for encoding a first communication for transmission to the gNodeB; processing a second signal sent by the gNodeB regarding a secondary PRACH configuration different from the primary PRACH configuration and to be used for encoding a second communication for transmission to the gNodeB; determining the primary PRACH configuration from the first signal and determining the secondary PRACH from the second signal; switching from the primary PRACH configuration to the secondary PRACH configuration, and encoding the second communication based on the secondary PRACH configuration for transmission to the gNodeB.

Description

[0001] Cross - reference to related applications

[0002] This application claims the benefit and priority of U.S. Provisional Patent Application No. 62 / 754,503, filed on Nov. 1, 2018, entitled "Secondary PRACH configuration for contention based random access in 5G NR Release-16", the entire disclosure of which is incorporated herein by reference. Technical Field

[0003] The various embodiments generally relate to the field of cellular communications, and more particularly to the use of a Physical Random Access Channel (PRACH) in a cellular network. Background Art

[0004] The current 3rd Generation Partnership Project (3GPP) New Radio (NR) specification (or 5G specification) does not explicitly address issues related to the use of PRACH in an Integrated Access and Backhaul (IAB) scenario or in a scenario involving remote interference. Brief Description of the Drawings

[0005] Figure 1 An exemplary IAB network is shown;

[0006] Figure 2A A Time Division Duplex (TDD) Downlink (DL) / Uplink (UL) radio frame is shown;

[0007] Figure 2B A Time Division Duplex (TDD) Downlink (DL) / Uplink (UL) radio frame implementing a secondary PRACH according to one embodiment is shown;

[0008] Figure 2C A Time Division Duplex (TDD) Downlink (DL) / Uplink (UL) radio frame implementing a secondary PRACH according to another embodiment is shown;

[0009] Figure 3 A cellular network according to one embodiment is shown, where a Secondary Random Access Radio Network Temporary Identifier (SRA-RNTI) is based on its corresponding uplink reception beam;

[0010] Figure 4 A Medium Access Control (MAC) Control Element (CE) according to one embodiment is shown;

[0011] Figure 5 is a process according to one embodiment;

[0012] Figure 6 illustrates an exemplary architecture of a network system according to various embodiments; and

[0013] Figure 7 illustrates exemplary components of a baseband circuit and a radio front-end module (RFEM) according to various embodiments. DETAILED DESCRIPTION

[0014] The following detailed description refers to the accompanying drawings. The same reference numerals may be used in different drawings to identify the same or similar elements. In the following description, for purposes of illustration and not limitation, specific details are set forth, such as particular structures, architectures, interfaces, techniques, etc., in order to provide a thorough understanding of various aspects of the embodiments. However, it will be apparent to those skilled in the art who have benefited from the present disclosure that various aspects of the embodiments may be practiced in other examples that depart from these specific details. In some instances, descriptions of well-known devices, circuits, and methods are omitted so as not to obscure the description of the various embodiments with unnecessary detail. For the purposes of this document, the phrase "A or B" means (A), (B), or (A and B).

[0015] NR may include enhancements to the physical random access channel (PRACH). Embodiments include enhancing contention-based random access using a secondary PRACH configuration. The enhancements can be used in a variety of scenarios.

[0016] One of the use cases associated with the embodiments is for an integrated access and backhaul (IAB) network. Figure 1 Illustrated is a portion of a cellular communication network 100 that includes an IAB node 102, a parent IAB node 104, a UE 106, and a child IAB node 108. The IAB node is configured to act as an access node for the sub-UE 106 for downlink (DL) and uplink (UL) communication. The IAB node may at some point attach both the child IAB node (the IAB node using the IAB node for backhaul) and the UE to the IAB node for access. The IAB node 102 is configured to communicate with the parent node 104 and the child node 108 for downlink (DL) and uplink (UL) communication for backhaul, and communicate with the UE 106 for access. It is desirable to configure orthogonal PRACH resources at the IAB for the child IAB node (such as the child node 108) and the UE (such as the UE 106) such that conflicts between the backhaul and the access link in contention-based random access are reduced.

[0017] If the child IAB node and the UE share the same Synchronization Signal Block (SSB) from the IAB node, the IAB node may configure its UE to use the existing (primary) PRACH resource and configure its child IAB node to use the secondary PRACH resource. If the two PRACH resources (primary PRACH resource and secondary PRACH resource) are orthogonal, there is no conflict between the backhaul and access random accesses.

[0018] Another use case for the secondary PRACH configuration is for Remote Interference Management (RIM). When Remote Interference (RI) occurs due to the atmospheric duct effect, the closer the UL symbol is to the DL / UL Switching Guard Period (GP), the greater the chance of being interfered with in the interfered cell. Therefore, when RI occurs, it is desirable to use the PRACH resource that is close in time to the end of the semi-static DL / UL cycle. Embodiments herein include a secondary PRACH configured as a fallback PRACH configuration for the UE in the interfered cell. According to this embodiment, the UE may first use the primary PRACH resource for random access and switch to the secondary PRACH resource configuration due to active signaling from the network or due to RI occurring because there have been too many failed random access attempts using the primary PRACH.

[0019] Some embodiments present Random Access Channel (RACH) configuration extensions and related signaling to enable a secondary PRACH configuration for contention-based random access.

[0020] Some embodiments present a secondary PRACH configuration for a node (IAB node or UE). PRACH enhancements can be used in the NRIAB network to reduce the conflict between the access link and the sub-backhaul link in random access scenarios (e.g., one PRACH configuration for the access link and another PRACH configuration for the sub-backhaul link), and it can also be used in NR RIM to improve random access performance when RI occurs (e.g., by allowing the use of the secondary PRACH configuration when the primary PRACH configuration suffers from a high failure rate due to RI).

[0021] RACH configuration extension with secondary PRACH configuration

[0022] According to one embodiment, the cell-specific PRACH resource configuration for random access in the primary cell (PCell) can be signaled in the remaining minimum system information block type 1 (RSH) (SIB1). For other serving cells, the cell-specific PRACH configuration can be signaled to the UE via dedicated radio resource control (RRC) signaling. In another embodiment, an additional RRC field rach-ConfigCommon2 can be defined in BWP-UplinkCommon as part of the RMSI (SIB1) for signaling the secondary PRACH configuration for the initial bandwidth part (BWP) of the PCell. According to the latter embodiment, the BWP-UplinkCommon signal can be configured as follows:

[0023]

[0024] The descriptions of the relevant fields are as follows:

[0025]

[0026] The additional RRC information element (IE) RACH-ConfigCommonSecondary as shown above can be used to specify the cell-specific random access parameters for the secondary PRACH configuration. The RRC IE can also be carried in BWP-UplinkCommon in the cell-specific uplink configuration for one or more other serving cells.

[0027] According to one embodiment, if the secondary PRACH is used for an IAB sub-node, in order to reduce the conflict between the access link and the sub-backhaul link, as suggested above, for example, in the context of the scenario of Figure 1 it is desirable to configure orthogonal resources for RACH-ConfigCommon and RACH-ConfigCommon2. For example, the following PRACH configurations can be used with indices 41 and 42, which are orthogonal in frequency range 2 (FR2) (millimeter wave range) time division duplex (TDD) operation:

[0028]

[0029]

[0030] According to another embodiment, the orthogonality between the two PRACH configurations pointed out by way of example above can be achieved using node-specific PRACH configurations. For example, in the following table, configuration x is based on configuration 41 with a one-slot offset, as shown in the "slot number" column. Then configuration 41 can be used for the primary PRACH and configuration x can be used for the secondary PRACH:

[0031]

[0032] According to one embodiment, if the secondary PRACH is used as a RIM fallback option, to provide a backup PRACH configuration to resist remote interference, the secondary PRACH resources can be configured in subframes / symbols within a given semi-static DL / UL period.

[0033] Now refer to Figures 2A to 2C , which respectively show TDD DL / UL radio frames 200a, 200b, and 200c, each radio frame occurring in a 10 ms period with a semi-static DL / UL configuration. The radio frames 200a / 200b / 200c include DL subframes (D), uplink subframes (U), and switching subframes (F), where the switching frame includes a downlink time region and an uplink time region separated by a guard period (GP) for downlink to uplink switching. As Figure 2B shown, for the FR1 TDD radio frame 200b, the PRACH configuration index 157 is available as the main configuration, where the subframe number 4 is also as Figure 2B shown by the arrow in Figure 2C shown, showing the secondary PRACH configuration that has been used for the UL subframe. As Figure 2C shown, the PRACH configuration index 158 is available as the secondary PRACH configuration, where the subframe number 4 is also as

[0034]

[0035]

[0036] Configurable uses of secondary PRACH configuration

[0037] In one embodiment, compared with the existing RACH-ConfigCommon IE, the secondary PRACH configuration IE can have two additional optional fields: ue-CapabilityRAT-ContainerList and secondaryPRACH-ActiveConfig, as follows:

[0038]

[0039]

[0040] The descriptions of the relevant fields are as follows:

[0041]

[0042] According to one embodiment, the uses of the secondary PRACH configuration, such as those described above in Figure 2B andFigure 2C As shown in the example of, it can be configured via the additional RRC field UE-CapabilityRAT-ContainerList. The latter field can specify the UE category configured to use the secondary PRACH resource. As previously discussed, one use of the secondary PRACH is to distinguish between the backhaul and access PRACHs in the IAB network. Therefore, the UE category can be configured as IAB node mobile termination (MT), and only the MT of the IAB node can use the secondary PRACH configuration for contention-based random access. According to another / alternative embodiment, the secondary PRACH can be used as a fallback option when RI occurs.

[0043] According to one embodiment, the optional RRC IE SecondaryPRACH-ActiveConfig can specify a trigger condition for the UE to switch to the secondary PRACH configuration. In one embodiment, the trigger condition can be defined as:

[0044]

[0045] The field description is as follows:

[0046]

[0047] According to one embodiment, the UE can use the primary PRACH configuration for random access and can switch to the secondary PRACH configuration after attempts using the primary configuration have experienced a specified number of failures. After a specified timer expires, the UE can switch back to the primary configuration.

[0048] However, if SecondaryPRACH-ActiveConfig is configured by the network, the UE can expect the network to signal the switching timing to / from the secondary PRACH configuration in an explicit manner, as discussed in the following section.

[0049] Explicit signaling from the network to notify the node to switch between two PRACH configurations .

[0050] The conditions for switching between the two PRACH configurations can be specified in the RRC, as discussed in the previous section. Alternatively, according to one embodiment, the network can also signal to the UE in an explicit manner to indicate which PRACH configuration the UE should use.

[0051] SIB message

[0052] In one embodiment, the switching signal can be transmitted in the system information (SI), SIB10, as described below, where the indication from the network can be specific to each serving cell, as described below:

[0053]

[0054] The field descriptions are as follows:

[0055]

[0056] Group common PDCCH

[0057] In one embodiment, the handover signal may be transmitted in the group common PDCCH (GC-PDCCH). In the current NR specification, 4 types of GC-PDCCH are specified, including downlink control information (DCI) format 2_0 for dynamic slot format indication (SFI), DCI format 2_1 for preemption, DCI formats 2_2 and 2_3 for uplink power control. According to one embodiment, DCI format 2_4 may be defined to notify the UE to switch to or from a secondary PRACH configuration. Multiple PRACH resource configuration indicators may be transmitted by DCI format 2_4, such as PRACH indicator 1, PRACH indicator 2... PRACH indicator N, and the cyclic redundancy check (CRC) may be scrambled by a radio network temporary identifier (RNTI) such as a secondary random access (SRA)-RNTI. According to one embodiment, the UE may obtain the SRA-RNTI from a higher layer. Each PRACH indicator indicates the number of resource blocks allocated to the PRACH data for the cell.

[0058] According to one embodiment, as Figure 3 shown in the example of, a network such as network 300 may allocate the SRA-RNTI based on its uplink reception beam. In Figure 3 , two base stations 302 and 304 are part of the cellular network 300. If a transmit / receive (Tx / Rx) point (TRP) (such as base station 304) can receive the uplink transmissions of two UEs using the same beam (such as a beam with a strong rank indicator (RI) 306), the same SRA-RNTI, SRA-RNTI 1 may be allocated to the two UEs. If TRP 304 cannot receive the uplink of the two UEs using the same beam due to a weak RI, such as weak RI 308, different SRA-RNTIs, SRA-RNTI 2 and SRA-RNTI 3 may be allocated to each of those UEs respectively. When an RI occurs, the interfered cell TRP may experience different levels of RI on various reception beams. According to one embodiment, the interfered cell may use the SRA-RNTI to notify a subset of its associated UEs to switch to a secondary PRACH resource configuration using the GC-PDCCH, the uplink of which suffers from a high RI, such as the RI caused by an atmospheric duct at 310.

[0059] According to one embodiment, the size of DCI format 2_4 can be configured by higher layers, and each PRACH indicator within DCI format 2_4 can inform the corresponding UE whether to use the primary PRACH configuration or the secondary PRACH configuration on a specific serving cell. The mapping between the PRACH indicator and the serving cell can be provided by higher layers in the RRC serving cell configuration. In one embodiment, the RRC IE for PRACH indication and serving cell mapping can be defined as follows:

[0060]

[0061] UE - specific RRC signaling

[0062] In one embodiment, the handover signal can be transmitted in a UE-specific RRC message, such as a downlink-downlink control channel message (DL-DCCH message). Within the latter RRC message, the RRC IE can be defined as follows:

[0063]

[0064] Field descriptions are as follows:

[0065]

[0066]

[0067] MAC CE

[0068] In one embodiment, 10110 can be used as the logical channel identifier (LCID) of the downlink shared channel (DL-SCH) to transmit the handover signal in the medium access control element (MAC CE). The DL-SCH is typically used to transmit system information blocks (SIBs), RRC signaling, and application data. As Figure 4 shown, the MAC CE can contain multiple octets, such as 2 octets in the case of the shown MAC CE 400, Oct 1 and Oct 2, where each C field corresponds to a serving cell. C0 represents the PCell, and each of the other C i s in i has its ServCellIndex. If the serving cell C i (where Ci≠0) is not configured or deactivated, then Ci is ignored by the IAB node or the UE. If C i = 0, then the UE shall use the primary PRACH configuration in that serving cell. Otherwise, if C i = 1, then the UE shall use the secondary PRACH configuration.

[0069] UE - specific DCI format / field

[0070] In one embodiment, the handover signal may be transmitted in a field of DCI format 1_1 or another DCI format. The physical downlink control channel (PDCCH carrier) of the DCI may be scrambled by a cell RNTI (C-RNTI). An N-bit field, the PRACH configuration indicator field (PCIF), may be used to indicate the PRACH configuration in the serving cell. According to one embodiment, cross-carrier (serving cell) indication is possible, and each bit in the PCIF may correspond to a cell ID configured by RRC. If the bit is 0, the UE uses the primary PRACH configuration in the serving cell. Otherwise, if the bit is 1, the UE uses the secondary PRACH configuration. In one embodiment, the RRC IE used for PRACH indication and serving cell mapping in the PCIF is defined as follows:

[0071]

[0072]

[0073] Secondary system information RNTI for IAB - specific remaining minimum SI (System Information Block Type 1) (SI - RNTI)

[0074] According to one embodiment, the PDCCH for scheduling the physical downlink shared channel (PDSCH) for RMSI may be scrambled by the SI-RNTI. The current NR Release-15 has a single fixed SI-RNTI value 0xFFFF as shown in Table 7.1-1 of 3GPP TS 38.321 V15.2.0. In one embodiment, a second SI-RNTI value is defined as shown in Table 5-1 below, and this second SI-RNTI value may be used to scramble the PDCCH for scheduling the RMSI that is only intended for IAB nodes.

[0075] Table 5 - 1 SI - RNTI values for IAB nodes

[0076]

[0077]

[0078] Figure 5Illustrates a process 500 according to one embodiment. The process 500 includes, at operation 502, processing a first signal regarding a primary physical random access channel (PRACH) configuration to be used for encoding a first communication for transmission to a gNodeB sent by a NR evolved NodeB (gNodeB); at operation 504, processing a second signal regarding a secondary PRACH configuration different from the primary PRACH configuration and to be used for encoding a second communication for transmission to the gNodeB sent by the gNodeB; at operation 506, determining the primary PRACH configuration from the first signal and the secondary PRACH from the second signal; and at operation 508, switching from the primary PRACH configuration to the secondary PRACH configuration and encoding the second communication based on the secondary PRACH configuration for transmission to the gNodeB.

[0079] Figure 6 Illustrates an exemplary architecture of a network system 600 according to various embodiments. The following description is provided for an example system 600 operating in conjunction with LTE system standards and 5G or NR system standards provided in 3GPP technical specifications. However, the exemplary embodiments are not limited in this regard, and the embodiments may be applied to other networks that benefit from the principles described herein, such as future 3GPP systems (e.g., sixth generation (6G)) systems, IEEE 802.16 protocols (e.g., WMAN, WiMAX, etc.), and the like.

[0080] As Figure 6 shown, the system 600 includes UE 601a and UE 601b (collectively referred to as "UE 601"). In this example, UE 601 is shown as a smart phone, but may also include any mobile or non-mobile computing device.

[0081] Multiple UEs 601 may be configured to be communicatively coupled to, for example, a RAN 610. In an embodiment, the RAN 610 may be a NG RAN or 5G RAN, an E-UTRAN, or a legacy RAN, such as a UTRAN or GERAN. As used herein, terms such as "NG RAN" may refer to the RAN 610 operating in a NR or 5G system 600, while terms such as "E-UTRAN" may refer to the RAN 610 operating in an LTE or 4G system 600. The multiple UEs 601 respectively utilize connections (or channels) 603 and 604, each connection including a physical communication interface or layer (discussed in further detail below).

[0082] In this example, the connections 603 and 604 are shown as air interfaces to enable communication coupling, and may be consistent with cellular communication protocols, such as GSM protocol, CDMA network protocol, PTT protocol, POC protocol, UMTS protocol, 3GPP LTE protocol, 5G protocol, NR protocol, and / or any other communication protocol discussed herein. In an embodiment, the UE 601 may directly exchange communication data via the ProSe interface 605. The ProSe interface 605 may alternatively be referred to as the SL interface 605, and may include one or more logical channels, including but not limited to PSCCH, PSSCH, PSDCH, and PSBCH.

[0083] UE 601b is shown as being configured to access the AP 606 (also referred to as "WLAN node 606", "WLAN 606", "WLAN terminal 606", "WT 606", etc.) via the connection 607. The connection 607 may include a local wireless connection, such as a connection consistent with any IEEE802.11 protocol, where the AP 606 will include a Wi-Fi router. In this example, the AP 606 is shown connected to the Internet without being connected to the core network of the wireless system (described in further detail below).

[0084] The RAN 610 includes one or more AN nodes or RAN nodes 611a and 611b (collectively referred to as "RAN nodes 611") that enable the connections 603 and 604. As used herein, the terms "access node", "access point", etc. may describe equipment that provides radio baseband functionality for data and / or voice connections between a network and one or more users. These access nodes may be referred to as BS, NR evolved NodeB (gNodeB), RAN nodes, eNB, NodeB, RSU, TRxP, or TRP, etc. As used herein, the term "NG RAN node", etc. may refer to the RAN node 611 (e.g., gNB) operating in the NR or 5G system 600, while the term "E-UTRAN node", etc. may refer to the RAN node 611 (e.g., eNB) operating in the LTE or 4G system 600. According to various embodiments, the RAN node 611 may be implemented as one or more of a dedicated physical device such as a macrocell base station and / or a low-power (LP) base station for providing a femtocell, picocell, or other similar cell with a smaller coverage area, smaller user capacity, or higher bandwidth compared to a macrocell.

[0085] In an embodiment, a plurality of UEs 601 may be configured to communicate with each other or with any one of a plurality of RAN nodes 611 over a multi-carrier communication channel using OFDM communication signals according to various communication technologies, such as but not limited to OFDMA communication technology (e.g., for downlink communication) or SC-FDMA communication technology (e.g., for uplink and ProSe or sidelink communication), although the scope of the embodiment is not limited in this regard. The OFDM signal may include a plurality of orthogonal sub-carriers.

[0086] In some embodiments, a downlink resource grid may be used for downlink transmission from any one of the RAN nodes 611 to the UE 601, and uplink transmission may utilize a similar technique. The grid may be a time-frequency grid, referred to as a resource grid or a time-frequency resource grid, which is the physical resources in the downlink in each time slot. For an OFDM system, such a time-frequency plane representation is a common practice, which makes wireless resource allocation intuitive. Each column and each row of the resource grid correspond to an OFDM symbol and an OFDM sub-carrier, respectively. The duration of the resource grid in the time domain corresponds to one time slot in the radio frame. The smallest time-frequency unit in the resource grid is represented as a resource element. Each resource grid includes a plurality of resource blocks, which describe the mapping of certain physical channels to resource elements. Each resource block includes a set of resource elements; in the frequency domain, this may represent the smallest amount of resources that can be currently allocated. Such resource blocks are used to transmit several different physical downlink channels.

[0087] According to various embodiments, the UEs 601 and the RAN nodes 611, 612 transmit (e.g., send and receive) data over an authorized medium (also referred to as "authorized spectrum" and / or "authorized band") and an unlicensed shared medium (also referred to as "unlicensed spectrum" and / or "unlicensed band"). The licensed spectrum may include channels operating in a frequency range of approximately 400 MHz to approximately 3.8 GHz, while the unlicensed spectrum may include the 5 GHz band.

[0088] The RAN nodes 611 may be configured to communicate with each other via an interface 612. In an embodiment where the system 600 is a 5G or NR system, the interface 612 may be an Xn interface 612. The Xn interface is defined between two or more RAN nodes 611 (e.g., two or more gNodeBs or gNBs, etc.) connected to the 5GC 620, between a RAN node 611 (e.g., gNB) connected to the 5GC 620 and an eNB, and / or between two eNBs connected to the 5GC 620.

[0089] The RAN 610 is shown as communicatively coupled to a core network - in this embodiment, communicatively coupled to a core network (CN) 620. The CN 620 may include a plurality of network elements 622, which are configured to provide various data and telecommunications services to customers / users (e.g., users of the UE 601) connected to the CN 620 via the RAN 610. The components of the CN 620 may be implemented in one physical node or separate physical nodes, including components for reading and executing instructions from a machine-readable or computer-readable medium (e.g., a non-transitory machine-readable storage medium).

[0090] Generally, the application server 630 may be an element that provides an application that uses IP bearer resources together with the core network (e.g., UMTS PS domain, LTE PS data services, etc.). The application server 630 may also be configured to support one or more communication services (e.g., VoIP sessions, PTT sessions, group communication sessions, social network services, etc.) for a plurality of UEs 601 via the EPC 620.

[0091] In an embodiment, the CN 620 may be a 5GC (referred to as "5GC 620", etc.), and the RAN 610 may be connected to the CN 620 via an NG interface 613. In an embodiment, the NG interface 613 may be divided into two parts: an NG user plane (NG-U) interface 614, which carries traffic data between the RAN node 611 and the UPF; and an S1 control plane (NG-C) interface 615, which is a signaling interface between the RAN node 611 and the AMF.

[0092] In an embodiment, the CN 620 may be a 5G CN (referred to as "5GC 620", etc.), while in other embodiments, the CN 620 may be an EPC. In the case where the CN 620 is an EPC (referred to as "EPC 620", etc.), the RAN 610 may be connected to the CN 620 via an S1 interface 613. In an embodiment, the S1 interface 613 may be divided into two parts: an S1 user plane (S1-U) interface 614, which carries traffic data between the RAN node 611 and the S-GW; and an S1-MME interface 615, which is a signaling interface between the RAN node 611 and the MME.

[0093] Figure 7 Exemplary components of a baseband circuit 710 and a radio front-end module (RFEM) 715 according to various embodiments are illustrated. The baseband circuit 710 includes an RF interface 718 that connects it to the RFEM. As shown, the RFEM 715 may include at least a radio frequency (RF) circuit 706, a front-end module (FEM) circuit 708, and an antenna array 711 coupled together as shown.

[0094] The baseband circuit 710 includes circuitry and / or control logic configured to perform various radio / network protocols and radio control functions enabling communication with one or more radio networks via the RF circuit 706. The radio control functions may include, but are not limited to, signal modulation / demodulation, encoding / decoding, radio frequency shifting, etc. In some embodiments, the modulation / demodulation circuitry of the baseband circuit 710 may include fast Fourier transform (FFT), precoding, or constellation mapping / demapping functions. In some embodiments, the encoding / decoding circuitry of the baseband circuit 710 may include convolutional, tail-biting convolutional, turbo, Viterbi, or low density parity check (LDPC) encoder / decoder functions. Embodiments of the modulation / demodulation and encoder / decoder functions are not limited to these examples and may include other suitable functions in other embodiments. The baseband circuit 710 is configured to process baseband signals received from the receive signal path of the RF circuit 706 and generate baseband signals for the transmit signal path of the RF circuit 706. The baseband circuit 710 is configured to interact with the application circuitry to generate and process baseband signals and control the operation of the RF circuit 706. The baseband circuit 710 may process various radio control functions.

[0095] The foregoing circuitry and / or control logic of the baseband circuit 710 may include one or more single-core or multi-core processors. For example, the one or more processors may include a 3G baseband processor 704A, a 4G / LTE baseband processor 704B, a 5G / NR baseband processor 704C, or some other baseband processor 704D for other existing, under development, or future generations (e.g., sixth generation (6G), etc.). In other embodiments, some or all of the functions of the baseband processors 704A-D may be included in modules stored in the memory 704G and executed via the central processing unit (CPU) 704E. In other embodiments, some or all of the functions of the baseband processors 704A-D may be provided as hardware accelerators (e.g., FPGA, ASIC, etc.) loaded with appropriate bitstreams or logic blocks stored in corresponding memory units. In various embodiments, the memory 704G may store program code of a real-time OS (RTOS) which, when executed by the CPU 704E (or other baseband processor), will cause the CPU 704E (or other baseband processor) to manage the resources of the baseband circuit 710, schedule tasks, etc. Additionally, the baseband circuit 710 includes one or more audio digital signal processors (DSPs) 704F. The audio DSP 704F includes elements for compression / decompression and echo cancellation and may include other suitable processing elements in other embodiments.

[0096] In some embodiments, each of processors 704A - 704E includes a respective memory interface for sending data to / receiving data from memory 704G. Baseband circuitry 710 may also include one or more interfaces for communicatively coupling to other circuits / devices.

[0097] RF circuitry 706 may enable communication with a wireless network using modulated electromagnetic radiation through a non - solid medium.

[0098] In some embodiments, the receive signal path of RF circuitry 706 may include mixer circuitry 706a, amplifier circuitry 706b, and filter circuitry 706c. In some embodiments, the transmit signal path of RF circuitry 706 may include filter circuitry 706c and mixer circuitry 706a. RF circuitry 706 may also include synthesizer circuitry 706d for synthesizing the frequencies used by mixer circuitry 706a of the receive and transmit signal paths. In some embodiments, mixer circuitry 706a of the receive signal path may be configured to down - convert an RF signal received from FEM circuitry 708 based on the synthesized frequency provided by synthesizer circuitry 706d. Amplifier circuitry 706b may be configured to amplify the down - converted signal, and filter circuitry 706c may be a low - pass filter (LPF) or a band - pass filter (BPF) configured to remove unwanted signals from the down - converted signal to generate an output baseband signal. The output baseband signal may be provided to baseband circuitry 710 for further processing. In some embodiments, although not required, the output baseband signal may be a zero - frequency baseband signal. In some embodiments, mixer circuitry 706a of the receive signal path may include a passive mixer, but the scope of the embodiments is not limited in this regard.

[0099] FEM circuitry 708 may include a receive signal path that may include circuitry configured to operate on an RF signal received from antenna array 711, amplify the received signal, and provide an amplified version of the received signal to RF circuitry 706 for further processing. FEM circuitry 708 may also include a transmit signal path that may include circuitry configured to amplify a transmit signal provided by RF circuitry 706 for transmission by one or more antenna elements in antenna array 711. In various embodiments, amplification through the transmit or receive signal path may be accomplished only in RF circuitry 706, only in FEM circuitry 708, or in both RF circuitry 706 and FEM circuitry 708.

[0100] The antenna array 711 includes one or more antenna elements, each antenna element being configured to convert an electrical signal into a radio wave to travel through the air and convert the received radio wave into an electrical signal. For example, the digital baseband signal provided by the baseband circuit 710 is converted into an analog RF signal (e.g., a modulated waveform), which will be amplified and transmitted via the antenna elements in the antenna array 711 including one or more antenna elements (not shown). The antenna elements can be omnidirectional, directional, or a combination thereof. The antenna elements can form various arrangements as known and / or discussed herein. The antenna array 711 can include microstrip antennas or printed antennas fabricated on the surface of one or more printed circuit boards. The antenna array 711 can be formed as patches of metal foil in various shapes (e.g., patch antennas), and can be coupled to the RF circuit 706 and / or the FEM circuit 708 using metal transmission lines and the like.

[0101] Figure 6 and / or Figure 7 One or more components of can be used in any of the embodiments described herein.

[0102] For one or more embodiments, at least one of the components shown in one or more of the foregoing figures can be configured to perform one or more of the operations, techniques, processes, and / or methods described in the example section below. For example, the baseband circuit described above in connection with one or more of the foregoing figures can be configured to operate in accordance with one or more of the following embodiments. As another example, the circuits associated with the UE, base station, network element, etc. described above in connection with one or more of the foregoing figures can be configured to operate in accordance with one or more of the embodiments shown in the embodiments section below.

[0103] Figure 6 and / or Figure 7 Components such as the baseband processing circuit including a processor, RF interface as shown can be used in any of the embodiments described herein, such as for use in a gNodeB or a UE.

[0104] In some embodiments, Figure 6 , Figure 7 or an electronic device, network, system, chip, or component or a part or a specific implementation thereof in some other figure herein can be configured to perform one or more of the processes, techniques, or methods described herein or a part thereof. One such process is shown in Figure 5 in.

[0105] For one or more embodiments, at least one of the components shown in one or more of the foregoing figures may be configured to perform one or more of the operations, techniques, processes, and / or methods described in the example section below. For example, the baseband circuitry described above in connection with one or more of the foregoing figures may be configured to operate in accordance with one or more of the following embodiments. As another example, the circuitry associated with the UE, base station, network element, etc. described above in connection with one or more of the foregoing figures may be configured to operate in accordance with one or more of the embodiments shown in the embodiments section below.

[0106] In some embodiments, Figure 6 and Figure 7 or an electronic device, network, system, chip, or component or a portion or a specific implementation thereof in some other figure herein may be configured to perform one or more of the processes, techniques, or methods described herein or a portion thereof. For example, the process may include receiving an indication of a secondary physical random access channel (PRACH) configuration via a signaling mechanism; and identifying the secondary PRACH configuration.

[0107] In some embodiments, Figure 6 and Figure 7 an electronic device may be configured to perform one or more of the processes, techniques, and / or methods described herein, or a portion thereof. For example, the process may include: determining an indication of a secondary physical random access channel (PRACH) configuration; and transmitting an indication of the secondary PRACH configuration via a signaling mechanism.

[0108] Embodiment

[0109] Embodiment 1 includes an apparatus for a wireless device, the apparatus including a radio frequency (RF) interface and processing circuitry coupled to the RF interface, the processing circuitry for: processing a first signal transmitted by a NR evolved Node B (gNodeB) regarding a primary physical random access channel (PRACH) configuration to be used for encoding a first communication for transmission to the gNodeB; processing a second signal transmitted by the gNodeB regarding a secondary PRACH configuration different from the primary PRACH configuration and to be used for encoding a second communication for transmission to the gNodeB; determining the primary PRACH configuration from the first signal and determining the secondary PRACH from the second signal; switching from the primary PRACH configuration to the secondary PRACH configuration, and encoding the second communication based on the secondary PRACH configuration for transmission to the gNodeB.

[0110] Embodiment 2 includes the subject matter of Embodiment 1, and optionally, wherein the gNodeB is an integrated access and backhaul (IAB) parent node, and wherein the wireless device is one of a NR user equipment (UE) or an IAB child node.

[0111] Embodiment 3 includes the subject matter of Embodiment 1, and optionally, wherein the second signal is part of one of a radio resource control (RRC) signal, a system information (SI) signal, or a group common physical downlink control channel (GC-PDCCH) signal.

[0112] Embodiment 4 includes the subject matter of Embodiment 1, and optionally, wherein the processing circuit switches in response to at least one of the following: meeting a trigger condition for the handover; or explicit signaling from the gNodeB.

[0113] Embodiment 5 includes the subject matter of Embodiment 4, and optionally, wherein the trigger condition includes determining whether a predetermined number of failed attempts to transmit a first communication from the wireless device to the gNodeB using the primary PRACH configuration have occurred.

[0114] Embodiment 6 includes the subject matter of Embodiment 4, and optionally, wherein the explicit signaling is based on remote interference management (RIM) performed by the gNodeB.

[0115] Embodiment 7 includes the subject matter of Embodiment 4, and optionally, wherein the explicit signaling is part of one of the following: a system information (SI) radio resource control (RRC) message from the gNodeB; a group common physical downlink control channel (PDCCH) including downlink control information (DCI) format 2_4; a user equipment specific (UE specific) RRC message including a downlink control channel message (DL-DCCH message); a media access control control element (MAC CE); or a UE specific DCI format.

[0116] Example 8 includes the subject matter of Example 7, and optionally, wherein: in the case where the explicit signaling is part of an SI RRC message, the SI RRC message includes a cell-specific indication for selecting between a primary PRACH configuration and a secondary PRACH configuration; wherein the explicit signaling is part of DCI format 2_4, and DCI format 2_4 includes an indication for selecting between a primary PRACH configuration and a secondary PRACH configuration for one user equipment (UE) or for a group of UEs from one or more serving cells; wherein the explicit signaling is part of the DL-DCCH message, and the DL-DCCH message includes an RRC information element (IE) that indicates a cell-specific selection between the primary PRACH configuration and the secondary PRACH configuration; in the case where the explicit signaling is part of a MAC CE, the MAC CE includes a 1-bit field to indicate the selection between the primary PRACH configuration and the secondary PRACH configuration; and in the case where the explicit signaling is part of a UE-specific DCI format, the UE-specific DCI format includes a selection between a primary PRACH configuration and a secondary PRACH configuration for multiple serving cells.

[0117] Example 9 includes the subject matter of Example 8, and optionally, wherein, in the case where the explicit signaling is part of DCI format 2_4, the processing circuitry is configured to decode a cyclic redundancy check (CRC) based on a secondary random access (SRA) radio network temporary identifier (RNTI) (SRA-RNTI).

[0118] Example 10 includes the subject matter of Example 9, and optionally, wherein the processing circuitry is configured to determine the SRA-RNTI from higher layer signaling by a gNodeB.

[0119] Example 11 includes the subject matter of Example 1, and optionally, wherein both the first signal and the second signal are part of cell-specific uplink configuration signaling.

[0120] Example 12 includes the subject matter of Example 11, and optionally, wherein: for random access of a wireless device in a primary cell (PCell), the second signal is part of an extended remaining minimum system information (RFIFO) block (SIB1) sent by a gNodeB; for random access of a wireless device in a serving cell outside the PCell, the second signal is part of dedicated radio resource control (RRC) signaling sent by a gNodeB; and the processing circuitry is configured to perform a handover based on the second signal.

[0121] Embodiment 13 includes the subject matter of Embodiment 11, and optionally, wherein the second signal includes information about a triggering condition for triggering a handover between a primary PRACH configuration and a secondary PRACH configuration, and the processing circuitry performs the handover based on the triggering condition.

[0122] Embodiment 14 includes the subject matter of Embodiment 1, and optionally, wherein the processing circuitry uses the secondary PRACH configuration to encode uplink (UL) time slots within a semi-static downlink / uplink (DL / UL) period to avoid interference from a remote cell.

[0123] Embodiment 15 includes the subject matter of any one of Embodiments 1-14, and optionally, further includes a front-end module coupled to the processing circuitry.

[0124] Embodiment 16 includes the subject matter according to Embodiment 15, and optionally, further includes one or more antennas, the one or more antennas being coupled to the front-end module to transmit signals to and receive signals from a gNodeB.

[0125] Embodiment 17 includes a method to be implemented at a device of a wireless device, the device including a radio frequency (RF) interface and a processing circuitry coupled to the RF interface, the method including: processing a first signal transmitted by a New Radio evolved Node B (gNodeB) regarding a primary physical random access channel (PRACH) configuration to be used for encoding a first communication for transmission to the gNodeB; processing a second signal transmitted by the gNodeB regarding a secondary PRACH configuration different from the primary PRACH configuration and to be used for encoding a second communication for transmission to the gNodeB; determining the primary PRACH configuration from the first signal and determining the secondary PRACH from the second signal; switching from the primary PRACH configuration to the secondary PRACH configuration, and encoding the second communication based on the secondary PRACH configuration for transmission to the gNodeB.

[0126] Embodiment 18 includes the subject matter of Embodiment 17, and optionally, wherein the gNodeB is an integrated access and backhaul (IAB) parent node, and wherein the wireless device is one of a New Radio user equipment (UE) or an IAB child node.

[0127] Embodiment 19 includes the subject matter of Embodiment 17, and optionally, wherein the second signal is part of one of a radio resource control (RRC) signal, a system information (SI) signal, or a group common physical downlink control channel (GC-PDCCH) signal.

[0128] Example 20 includes the subject matter of Example 17, and optionally, wherein the handover includes handover in response to at least one of: a triggering condition for the handover being met; or explicit signaling from the gNodeB.

[0129] Example 21 includes the subject matter of Example 20, and optionally, wherein the triggering condition includes determining whether a predetermined number of failed attempts to transmit a first communication from the wireless device to the gNodeB using the primary PRACH configuration have occurred.

[0130] Example 22 includes the subject matter of Example 20, and optionally, wherein the explicit signaling is based on remote interference management (RIM) performed by the gNodeB.

[0131] Example 23 includes the subject matter of Example 20, and optionally, wherein the explicit signaling is part of one of: a system information (SI) radio resource control (RRC) message from the gNodeB; a group common physical downlink control channel (PDCCH) including a downlink control information (DCI) format 2_4; a user equipment specific (UE specific) RRC message including a downlink control channel message (DL-DCCH message); a medium access control control element (MAC CE); or a UE specific DCI format.

[0132] Example 24 includes the subject matter of Example 23, and optionally, wherein: in the case where the explicit signaling is part of an SI RRC message, the SI RRC message includes a cell specific indication for selecting between a primary PRACH configuration and a secondary PRACH configuration; where the explicit signaling is part of DCI format 2_4, the DCI format 2_4 includes an indication for selecting between a primary PRACH configuration and a secondary PRACH configuration for one user equipment (UE) or for a group of UEs from one or more serving cells; where the explicit signaling is part of the DL-DCCH message, the DL-DCCH message includes an RRC information element (IE) that indicates a cell specific selection between the primary PRACH configuration and the secondary PRACH configuration; in the case where the explicit signaling is part of a MAC CE, the MAC CE includes a 1-bit field to indicate a selection between a primary PRACH configuration and a secondary PRACH configuration; and in the case where the explicit signaling is part of a UE specific DCI format, the UE specific DCI format includes a selection between a primary PRACH configuration and a secondary PRACH configuration for multiple serving cells.

[0133] Example 25 includes the subject matter of Example 24 and optionally further includes, in the case where explicit signaling is part of DCI format 2_4, decoding a cyclic redundancy check (CRC) based on a secondary random access (SRA) radio network temporary identifier (RNTI) (SRA-RNTI).

[0134] Example 26 includes the subject matter of Example 25 and optionally further includes determining the SRA-RNTI by the gNodeB from higher layer signaling.

[0135] Example 27 includes the subject matter of Example 17 and optionally, where both the first signal and the second signal are part of cell-specific uplink configuration communication.

[0136] Example 28 includes the subject matter of Example 27 and optionally, where: for random access of the wireless device in the primary cell (PCell), the second signal is part of an extended remaining minimum system information (RFIFO) block (SIB1) sent by the gNodeB; for random access of the wireless device in a serving cell outside the PCell, the second signal is part of dedicated radio resource control (RRC) signaling sent by the gNodeB; and the handover is based on the second signal.

[0137] Example 29 includes the subject matter of Example 27 and optionally, where the second signal includes information about a triggering condition for triggering a handover between a primary PRACH configuration and a secondary PRACH configuration, and the handover is based on the triggering condition.

[0138] Example 30 includes the subject matter of Example 17 and optionally further includes using a secondary PRACH configuration to encode uplink (UL) time slots within a semi-static downlink / uplink (DL / UL) period to avoid interference from a remote cell.

[0139] Example 31 includes an apparatus of a wireless device, the apparatus including: means for processing a first signal sent by a NR evolved Node B (gNodeB) regarding a primary physical random access channel (PRACH) configuration to be used for encoding a first communication for transmission to the gNodeB; means for processing a second signal sent by the gNodeB regarding a secondary PRACH configuration different from the primary PRACH configuration and to be used for encoding a second communication for transmission to the gNodeB; means for determining the primary PRACH configuration from the first signal and determining the secondary PRACH from the second signal; and means for switching from the primary PRACH configuration to the secondary PRACH configuration and encoding the second communication based on the secondary PRACH configuration for transmission to the gNodeB.

[0140] Embodiment 32 includes the subject matter of Embodiment 31, and optionally, wherein the gNodeB is an integrated access and backhaul (IAB) parent node, and wherein the wireless device is one of a New Radio (NR) user equipment (UE) or an IAB child node.

[0141] Embodiment 33 includes the subject matter of Embodiment 31, and optionally, wherein the second signal is part of one of a Radio Resource Control (RRC) signal, a System Information (SI) signal, or a Group Common Physical Downlink Control Channel (GC-PDCCH) signal.

[0142] Embodiment 34 includes the subject matter of Embodiment 31, and optionally, wherein the means for handover includes means for performing a handover in response to at least one of: a handover trigger condition being met; or explicit signaling from the gNodeB.

[0143] Embodiment 35 includes the subject matter of Embodiment 34, and optionally, wherein the trigger condition includes determining whether a predetermined number of failed attempts have occurred to transmit a first communication from the wireless device to the gNodeB using the primary PRACH configuration.

[0144] Embodiment 36 includes the subject matter of Embodiment 34, and optionally, wherein the explicit signaling is part of one of: a System Information (SI) Radio Resource Control (RRC) message from the gNodeB; a Group Common Physical Downlink Control Channel (PDCCH) including Downlink Control Information (DCI) format 2_4; a User Equipment specific (UE specific) RRC message including a Downlink Control Channel Message (DL-DCCH message); a Medium Access Control Control Element (MAC CE); or a UE specific DCI format.

[0145] Embodiment 37 includes an apparatus of a New Radio (NR) evolved Node B (gNodeB), the apparatus including a radio frequency (RF) interface and processing circuitry coupled to the RF interface, the processing circuitry for: encoding a first signal for transmission to a wireless device, the first signal regarding a primary Physical Random Access Channel (PRACH) configuration to be used by the wireless device to encode a first communication for transmission to the gNodeB; encoding a second signal for transmission to the wireless device, the second signal regarding a secondary PRACH configuration different from the primary PRACH configuration and to be used by the wireless device to encode a second communication for transmission to the gNodeB; and causing the wireless device to switch from the primary PRACH configuration to the secondary PRACH configuration and encode the second communication for transmission to the gNodeB based on the secondary PRACH configuration.

[0146] Example 38 includes the subject matter of Example 37, and optionally, wherein a second communication based on a secondary PRACH configuration is orthogonal to another communication from another wireless device to a gNodeB, the another communication at least partially overlapping with the second communication in time.

[0147] Example 39 includes the subject matter of Example 37, and optionally, wherein the gNodeB is an integrated access and backhaul (IAB) parent node, and wherein the wireless device is one of a New Radio (NR) user equipment (UE) or an IAB child node.

[0148] Example 40 includes the subject matter of Example 37, and optionally, wherein the second signal is part of one of a radio resource control (RRC) signal, a system information (SI) signal, or a group common physical downlink control channel (GC-PDCCH) signal.

[0149] Example 41 includes the subject matter of Example 37, and optionally, wherein the processing circuitry is configured to encode at least one of: information regarding a triggering condition for causing the wireless device to switch from a primary PRACH to a secondary PRACH; or explicit signaling for causing the wireless device to switch from a primary PRACH to a secondary PRACH for transmission to the wireless device.

[0150] Example 42 includes the subject matter of Example 41, and optionally, wherein the triggering condition includes information regarding a predetermined number of failed attempts to transmit a first communication from the wireless device to the gNodeB using a primary PRACH configuration.

[0151] Example 43 includes the subject matter of Example 41, and optionally, wherein the explicit signaling is based on remote interference management (RIM) performed by the gNodeB.

[0152] Example 44 includes the subject matter of Example 41, and optionally, wherein the explicit signaling is part of one of: a system information (SI) radio resource control (RRC) message; a group common physical downlink control channel (PDCCH) including a downlink control information (DCI) format 2_4; a user equipment specific (UE specific) RRC message including a downlink control channel message (DL-DCCH message); a media access control control element (MAC CE); or a UE specific DCI format.

[0153] Example 45 includes the subject matter of Example 44, and optionally, wherein: in the case where the explicit signaling is part of an SI RRC message, the SI RRC message includes a cell-specific indication for selecting between a primary PRACH configuration and a secondary PRACH configuration; wherein the explicit signaling is part of DCI format 2_4, and DCI format 2_4 includes an indication for selecting between a primary PRACH configuration and a secondary PRACH configuration for one user equipment (UE) or for a group of UEs from one or more serving cells; wherein the explicit signaling is part of the DL-DCCH message, and the DL-DCCH message includes an RRC information element (IE) that indicates a cell-specific selection between the primary PRACH configuration and the secondary PRACH configuration; in the case where the explicit signaling is part of a MAC CE, the MAC CE includes a 1-bit field to indicate the selection between the primary PRACH configuration and the secondary PRACH configuration; and in the case where the explicit signaling is part of a UE-specific DCI format, the UE-specific DCI format includes a selection between a primary PRACH configuration and a secondary PRACH configuration for multiple serving cells.

[0154] Example 46 includes the subject matter of Example 45, and optionally, wherein, in the case where the explicit signaling is part of DCI format 2_4, DCI format 2_4 includes a cyclic redundancy check (CRC) based on a secondary random access (SRA) radio network temporary identifier (RNTI) (SRA-RNTI).

[0155] Example 47 includes the subject matter of Example 46, and optionally, wherein the processing circuitry is used to encode the SRA-RNTI based on higher layer signaling for transmission to the wireless device.

[0156] Example 48 includes the subject matter of Example 37, and optionally, wherein the processing circuitry is used to encode cell-specific uplink configuration communication to the wireless device, and both the first signal and the second signal are part of the cell-specific uplink configuration communication.

[0157] Example 49 includes the subject matter of Example 48, and optionally, wherein the processing circuitry is used to encode the following for transmission to the wireless device to cause the wireless device to perform a handover based on the second signal: for random access of the wireless device in the primary cell (PCell), it is an extended remaining minimum system information (RFIFO) block (SIB1) including the second signal; and for random access of the wireless device in a serving cell outside the PCell, it is dedicated radio resource control (RRC) signaling including the second signal.

[0158] Example 50 includes the subject matter of Example 48, and optionally, wherein the second signal includes information about a triggering condition for triggering a handover between a primary PRACH configuration and a secondary PRACH configuration by a wireless device.

[0159] Example 51 includes the subject matter of Example 37, and optionally, wherein the processing circuitry is configured to cause the wireless device to encode an uplink (UL) time slot within a semi-static downlink / uplink (DL / UL) period using the secondary PRACH configuration to avoid interference from a remote cell.

[0160] Example 52 includes the subject matter of any one of Examples 37 - 51, and optionally, further includes a front-end module coupled to the processing circuitry.

[0161] Example 53 includes the subject matter according to Example 52, and optionally, further includes one or more antennas coupled to the front-end module to transmit signals to and receive signals from the wireless device.

[0162] Example 54 includes a method used at a device of a new radio (NR) evolved Node B (gNodeB), the method including: encoding a first signal for transmission to a wireless device, the first signal regarding a primary physical random access channel (PRACH) configuration to be used by the wireless device to encode a first communication for transmission to the gNodeB; encoding a second signal for transmission to the wireless device, the second signal regarding a secondary PRACH configuration different from the primary PRACH configuration and to be used by the wireless device to encode a second communication for transmission to the gNodeB; and causing the wireless device to switch from the primary PRACH configuration to the secondary PRACH configuration and encode the second communication based on the secondary PRACH configuration for transmission to the gNodeB.

[0163] Example 55 includes the subject matter of Example 54, and optionally, wherein the second communication based on the secondary PRACH configuration is orthogonal to another communication from another wireless device to the gNodeB, the another communication at least partially overlapping with the second communication in time.

[0164] Example 56 includes the subject matter of Example 54, and optionally, wherein the gNodeB is an integrated access and backhaul (IAB) parent node, and wherein the wireless device is one of an NR user equipment (UE) or an IAB child node.

[0165] Example 57 includes the subject matter of Example 54, and optionally, wherein the second signal is part of one of a radio resource control (RRC) signal, a system information (SI) signal, or a group common physical downlink control channel (GC-PDCCH) signal.

[0166] Example 58 includes the subject matter of Example 54, and optionally, further includes encoding at least one of the following for transmission to a wireless device: information about a trigger condition for causing the wireless device to switch from a primary PRACH to a secondary PRACH; or explicit signaling for causing the wireless device to switch from a primary PRACH to a secondary PRACH.

[0167] Example 59 includes the subject matter of Example 58, and optionally, wherein the trigger condition includes information about a predetermined number of failed attempts to transmit a first communication from the wireless device to the gNodeB using a primary PRACH configuration.

[0168] Example 60 includes the subject matter of Example 58, and optionally, wherein the explicit signaling is based on remote interference management (RIM) performed by the gNodeB.

[0169] Example 61 includes the subject matter of Example 58, and optionally, wherein the explicit signaling is part of one of the following: a system information (SI) radio resource control (RRC) message; a group common physical downlink control channel (PDCCH) including a downlink control information (DCI) format 2_4; a user equipment specific (UE specific) RRC message including a downlink control channel message (DL-DCCH message); a media access control control channel (MAC CE); or a UE specific DCI format.

[0170] Example 62 includes the subject matter of Example 61 and, optionally, wherein: in the case where the explicit signaling is part of an SI RRC message, the SI RRC message includes a cell-specific indication for selecting between a primary PRACH configuration and a secondary PRACH configuration; wherein the explicit signaling is part of DCI format 2_4, and DCI format 2_4 includes an indication for selecting between a primary PRACH configuration and a secondary PRACH configuration for one user equipment (UE) or for a group of UEs from one or more serving cells; wherein the explicit signaling is part of the DL-DCCH message, and the DL-DCCH message includes an RRC information element (IE) that indicates a cell-specific selection between the primary PRACH configuration and the secondary PRACH configuration; in the case where the explicit signaling is part of a MAC CE, the MAC CE includes a 1-bit field to indicate the selection between the primary PRACH configuration and the secondary PRACH configuration; and in the case where the explicit signaling is part of a UE-specific DCI format, the UE-specific DCI format includes a selection between a primary PRACH configuration and a secondary PRACH configuration for multiple serving cells.

[0171] Example 63 includes the subject matter of Example 62 and, optionally, wherein, in the case where the explicit signaling is part of DCI format 2_4, DCI format 2_4 includes a cyclic redundancy check (CRC) based on a secondary random access (SRA) radio network temporary identifier (RNTI) (SRA-RNTI).

[0172] Example 64 includes the subject matter of Example 63 and, optionally, further includes encoding the SRA-RNTI based on higher layer signaling for transmission to a wireless device.

[0173] Example 65 includes the subject matter of Example 54 and, optionally, further includes encoding cell-specific uplink configuration communication to a wireless device, both the first signal and the second signal being part of the cell-specific uplink configuration communication.

[0174] Example 66 includes the subject matter of Example 65 and, optionally, further includes encoding for transmission to a wireless device to cause the wireless device to perform a handover based on the second signal: for random access of the wireless device in a primary cell (PCell), an extended remaining minimum system information (RFIFO) block (SIB1) that includes the second signal; and for random access of the wireless device in a serving cell outside the PCell, dedicated radio resource control (RRC) signaling that includes the second signal.

[0175] Example 67 includes the subject matter of Example 65, and optionally, wherein the second signal includes information about a triggering condition for triggering a switch between a primary PRACH configuration and a secondary PRACH configuration by a wireless device.

[0176] Example 68 includes the subject matter of Example 54, and optionally, further includes causing a wireless device to encode an uplink (UL) time slot within a semi-static downlink / uplink (DL / UL) period using a secondary PRACH configuration to avoid interference from a remote cell.

[0177] Example 69 includes an apparatus of a new radio (NR) evolved Node B (gNodeB), the apparatus including: means for encoding a first signal for transmission to a wireless device, the first signal regarding a primary physical random access channel (PRACH) configuration to be used by the wireless device for encoding a first communication for transmission to the gNodeB; means for encoding a second signal for transmission to the wireless device, the second signal regarding a secondary PRACH configuration different from the primary PRACH configuration and to be used by the wireless device for encoding a second communication for transmission to the gNodeB; and means for causing the wireless device to switch from the primary PRACH configuration to the secondary PRACH configuration and encode the second communication based on the secondary PRACH configuration for transmission to the gNodeB.

[0178] Example 70 includes the subject matter of Example 69, and optionally, wherein the second communication based on the secondary PRACH configuration is orthogonal to another communication from another wireless device to the gNodeB, the another communication at least partially overlapping with the second communication in time.

[0179] Example 71 includes the subject matter of Example 69, and optionally, wherein the gNodeB is an integrated access and backhaul (IAB) parent node, and wherein the wireless device is one of an NR user equipment (UE) or an IAB child node.

[0180] Example 72 includes a machine-readable medium including code that, when executed, will cause a machine to perform the method according to any one of Examples 17 - 30 and 54 - 68.

[0181] Example 73 includes a product including one or more tangible computer-readable non-transitory storage media, the one or more tangible computer-readable non-transitory storage media including computer-executable instructions that, when executed by at least one computer processor, enable the at least one computer processor to perform the method according to any one of Examples 17 - 30 and 54 - 68.

[0182] Embodiment 74 includes an apparatus that includes means for causing a wireless communication device to perform the method of any one of Embodiments 17 - 30 and 54 - 68.

[0183] Embodiment 75 includes a signal as described in or associated with any of the above embodiments, or a part or component thereof.

[0184] Embodiment 76 includes a signal in a wireless network as shown and described herein.

[0185] Embodiment 77 includes a method of communicating in a wireless network as shown and described herein.

[0186] Embodiment 78 includes a system for providing wireless communication as shown and described herein.

[0187] Unless otherwise explicitly stated, any one of the above embodiments may be combined with any other embodiment (or combination of embodiments). The foregoing description of one or more specific embodiments provides illustration and description, but is not intended to be exhaustive or to limit the scope of the embodiments to the precise forms disclosed.

Claims

1. A user equipment (UE), the user equipment comprising a radio frequency (RF) interface and a baseband processor coupled to the RF interface, the baseband processor being configured to: Receive information indicating a first physical random access channel (PRACH) configuration, a second PRACH configuration, a failure attempt threshold, and an expiration timer value from a base station, the first PRACH configuration being different from the second PRACH configuration; Transmit a first communication via the RF interface based on the first PRACH configuration; And In response to the number of failed attempts to transmit the first communication to the base station using the first PRACH configuration being equal to the failure attempt threshold, set a timer to the expiration timer value and switch from the first PRACH configuration to the second PRACH configuration; Transmit a second communication via the RF interface based on the second PRACH configuration; In response to expiration of the timer, switch from the second PRACH configuration to the first PRACH configuration; And Transmit a third communication via the RF interface based on the first PRACH configuration.

2. The UE according to claim 1, wherein the base station is an integrated access and backhaul (IAB) parent node, and wherein the UE is one of a New Radio (NR) UE or an IAB child node.

3. The UE according to claim 1, wherein the information is received from the base station in a radio resource control (RRC) signal.

4. The UE according to claim 1, wherein both the first PRACH configuration and the second PRACH configuration are contention-based PRACH configurations.

5. The UE according to claim 1, wherein the baseband processor is configured to encode an uplink (UL) time slot within a semi-static downlink / uplink (DL / UL) period using the second PRACH configuration to avoid interference from a remote cell.

6. A method implemented at a device of a wireless apparatus, the device comprising a radio frequency (RF) interface and processing circuitry coupled to the RF interface, the method comprising: Receive information indicating a first physical random access channel (PRACH) configuration, a second PRACH configuration, a failure attempt threshold, and an expiration timer value from a base station, the first PRACH configuration being different from the second PRACH configuration; Transmit a first communication based on the first PRACH configuration; And In response to the number of failed attempts to transmit the first communication to the base station using the first PRACH configuration being equal to the failure attempt threshold, set a timer to the expiration timer value and switch from the first PRACH configuration to the second PRACH configuration; Transmit a second communication based on the second PRACH configuration; In response to expiration of the timer, switch from the second PRACH configuration to the first PRACH configuration; And Transmit a third communication via the RF interface based on the first PRACH configuration.

7. The method according to claim 6, wherein both the first PRACH configuration and the second PRACH configuration are contention-based PRACH configurations.

8. An apparatus of a wireless device, the apparatus comprising: means for receiving, from a base station, information indicating a first physical random access channel (PRACH) configuration, a second PRACH configuration, a failure attempt threshold, and an expiration timer value, the first PRACH configuration being different from the second PRACH configuration; means for transmitting a first communication based on the first PRACH configuration; and means for setting a timer to the expiration timer value and switching from the first PRACH configuration to the second PRACH configuration in response to the number of failed attempts to transmit the first communication to the base station using the first PRACH configuration being equal to the failure attempt threshold; means for transmitting a second communication based on the second PRACH configuration; means for switching from the second PRACH configuration to the first PRACH configuration in response to the expiration of the timer; and means for transmitting a third communication based on the first PRACH configuration.

9. The apparatus according to claim 8, wherein the base station is an integrated access and backhaul (IAB) parent node, and wherein the wireless device is associated with one of a New Radio (NR) user equipment (UE) or an IAB child node.

10. The apparatus according to claim 8, wherein both the first PRACH configuration and the second PRACH configuration are contention-based PRACH configurations.

11. A machine-readable medium comprising code that, when executed, causes a machine to perform the method according to any one of claims 6-7.

Images