Patent Description:
A random access (RA) procedure is a function in a cellular system. In Long Term Evolution (LTE), a wireless device (WD) that would like to access the network initiates the RA procedure by transmitting a preamble (MSG1) in the uplink, i.e., from the WD to the base station, on the Physical Random Access Channel (PRACH). An eNB or gNB (next generation Node B, or transmission/reception point (TRP), i.e. a base station, access node, etc.) receiving the preamble and detecting the random-access attempt will respond in the downlink, i.e., from the base station to the WD, by transmitting a RA response (RAR, MSG2). The RAR carries an uplink scheduling grant for the WD to continue the procedure by transmitting a following subsequent message in the uplink (MSG3) for terminal identification. A similar procedure is envisioned for New Radio (NR) (also known as "<NUM>") as shown in <FIG>.

Before transmission of the PRACH preamble, the WD receives both a set of synchronization signals and configuration parameters on a broadcast channel in a synchronization signal (SS)-block (i.e., NR-Primary SS (NR-PSS), NR Secondary SS (NR-SSS), NR-physical broadcast channel (NR-PBCH)), possibly complemented with configuration parameters received on yet another channel.

MSG3 is transmitted by using a physical uplink shared channel (PUSCH). Besides MSG3 payload, demodulation reference signals (DMRS) are also transmitted to assist the data decoding at the base station (eNB/gNB). In both LTE and NR, for a <NUM>-step random access procedure, the initial transmission of MSG3 is scheduled by the uplink (UL) grant contained in the random access response (RAR). The retransmission of MSG3 is scheduled by UL grant over the physical downlink control channel (PDCCH). In LTE, MSG3 repetition can be configured by the UL grant contained in RAR for coverage enhancements for bandwidth reduced low complexity (BL)/ coverage enhancement (CE) wireless devices.

As part of the RA procedure, after receiving Random Access Request in MSG1, base station provides the required information in MSG2 - Random Access Response (RAR) message - for the WD to send the MSG3 (RRC Connection Request). This is referred to as the RAR Grant in the physical layer. In LTE, the RAR Grant is a <NUM>-bit message with contents from most significant bit (MSB) to least significant bit (LSB) as follows:.

For narrow band Internet of Things (NB-IoT) WDs, the size of an UL grant field may be <NUM> bits, and for BL WDs and WDs in enhanced coverage level <NUM> or <NUM>, the size of the UL grant field may be <NUM> bits. The contents of the UL grant may be those listed in 3GPP Table <NUM>-<NUM> TS <NUM> for BL/CE WD.

Random access procedures in LTE or NR are also discussed in <CIT>, in <CIT>, and in 3GPP contribution "Corrections on PRACH procedure", document R1-<NUM>, TSG RAN WG1 Meeting AH <NUM>, Vancouver, Canada, January 22nd - 26th, <NUM>.

In LTE, MSG3 transmission has a fixed transmission duration of one subframe (i.e., <NUM>). In NR, both slot and non-slot based MSG3 transmission are supported. This means that MSG3 transmission can be scheduled with different transmission durations (e.g., <NUM>, <NUM>, <NUM>, or <NUM> orthogonal frequency division multiplexed (OFDM) symbols). Further, NR supports bandwidth part (BWP) sizes that are much larger than maximum LTE carrier bandwidth. Therefore, the approach currently used in LTE for determining the resource block assignment with fixed size signaling in RAR grant for MSG3 transmission cannot be reused for NR.

With fixed size <NUM>-bit RAR grant and the number of bits used by the above fields, the number of bits left for fixed size resource block assignment is not more than <NUM>. Assuming a ~<NUM>-byte MSG3, <NUM> RBs are needed for MCS=<NUM> and slot based PUSCH transmission with <NUM>+<NUM>+<NUM> DMRS configuration. Table <NUM> shows the maximum number of RBs that can be allocated with NR resource allocation type <NUM> (equivalently, LTE PUSCH resource allocation type <NUM>) under some example BWP sizes. Clearly, the existing LTE method of fixed size resource block assignment cannot be reused for NR considering (<NUM>) BWP size in NR can be much larger than the maximum LTE bandwidth and (<NUM>) non-slot based MSG3 transmission (<NUM>, <NUM>, <NUM> symbols) is supported.

For NR random access, new fixed size resource block assignment methods are used in RAR grant scheduling MSG3 including scalable resource block (RB) granularity and/or restricted resource block assignment span in a BWP.

The present disclosure provides a method according to claim <NUM>, a method according to claim <NUM>, a network node according to claim <NUM>, and a wireless device according to claim <NUM>. The dependent claims define further embodiments.

The fixed size resource block assignment methods described herein can cope with large BWPs in NR and flexible MSG3 transmission that can be slot based or non-slot based (<NUM>, <NUM>, or <NUM> OFDM symbols).

Before describing in detail exemplary embodiments, it is noted that the embodiments reside primarily in combinations of apparatus components and processing steps related to resource block assignment for MSG3 transmission. Accordingly, components have been represented where appropriate by conventional symbols in the drawings, showing only those specific details that are pertinent to understanding the embodiments so as not to obscure the disclosure with details that will be readily apparent to those of ordinary skill in the art having the benefit of the description herein.

The term "network node" used herein can be any kind of network node comprised in a radio network which may further comprise any of base station (BS), radio base station, base transceiver station (BTS), base station controller (BSC), radio network controller (RNC), g Node B (gNB), evolved Node B (eNB or eNodeB), Node B, multi-standard radio (MSR) radio node such as MSR BS, multi-cell/multicast coordination entity (MCE), relay node, integrated access and backhaul (IAB) node, donor node controlling relay, radio access point (AP), transmission points, transmission nodes, Remote Radio Unit (RRU) Remote Radio Head (RRH), a core network node (e.g., mobile management entity (MME), self-organizing network (SON) node, a coordinating node, positioning node, MDT node, etc.), an external node (e.g., 3rd party node, a node external to the current network), nodes in distributed antenna system (DAS), a spectrum access system (SAS) node, an element management system (EMS), etc. The network node may also comprise test equipment. The term "radio node" used herein may be used to also denote a wireless device (WD) such as a wireless device (WD) or a radio network node.

In some embodiments, the non-limiting terms wireless device (WD) or a user equipment (WD) are used interchangeably.

It can be any kind of a radio network node which may comprise any of base station, radio base station, base transceiver station, base station controller, network controller, RNC, evolved Node B (eNB), Node B, gNB, IAB, Multi-cell/multicast Coordination Entity (MCE), relay node, access point, radio access point, Remote Radio Unit (RRU) Remote Radio Head (RRH).

It should be understood that, in some embodiments, signaling may generally comprise one or more symbols and/or signals and/or messages. A signal may comprise or represent one or more bits. An indication may represent signaling, and/or be implemented as a signal, or as a plurality of signals. One or more signals may be included in and/or represented by a message. Signaling, in particular control signaling, may comprise a plurality of signals and/or messages, which may be transmitted on different carriers and/or be associated to different signaling processes, e.g. representing and/or pertaining to one or more such processes and/or corresponding information. An indication may comprise signaling, and/or a plurality of signals and/or messages and/or may be comprised therein, which may be transmitted on different carriers and/or be associated to different acknowledgment signaling processes, e.g. representing and/or pertaining to one or more such processes. Signaling associated to a channel may be transmitted such that it represents signaling and/or information for that channel, and/or that the signaling is interpreted by the transmitter and/or receiver to belong to that channel. Such signaling may generally comply with transmission parameters and/or format/s for the channel.

An indication generally may explicitly and/or implicitly indicate the information it represents and/or indicates. Implicit indication may for example be based on position and/or resource used for transmission. Explicit indication may for example be based on a parametrization with one or more parameters, and/or one or more index or indices, and/or one or more bit patterns representing the information. It may in particular be considered that the RRC signaling as described herein may indicate what subframes or signals to use for one or more of the measurements described herein and under what conditions and/or operational modes.

Configuring a radio node, in particular a terminal or user equipment or the WD <NUM>, may refer to the radio node being adapted or caused or set and/or instructed to operate according to the configuration. Configuring may be done by another device, e.g., a network node <NUM> (for example, a radio node of the network like a base station or eNodeB) or network, in which case it may comprise transmitting configuration data to the radio node to be configured. Such configuration data may represent the configuration to be configured and/or comprise one or more instruction pertaining to a configuration, e.g. a configuration for transmitting and/or receiving on allocated resources, in particular frequency resources, or e.g., configuration for performing certain measurements on certain subframes or radio resources. A radio node may configure itself, e.g., based on configuration data received from a network or network node <NUM>. A network node <NUM> may use, and/or be adapted to use, its circuitry/ies for configuring. Allocation information may be considered a form of configuration data. Configuration data may comprise and/or be represented by configuration information, and/or one or more corresponding indications and/or message/s.

Generally, configuring may include determining configuration data representing the configuration and providing, e.g. transmitting, it to one or more other nodes (parallel and/or sequentially), which may transmit it further to the radio node (or another node, which may be repeated until it reaches the wireless device <NUM>). Alternatively, or additionally, configuring a radio node, e.g., by a network node <NUM> or other device, may include receiving configuration data and/or data pertaining to configuration data, e.g., from another node like a network node <NUM>, which may be a higher-level node of the network, and/or transmitting received configuration data to the radio node. Accordingly, determining a configuration and transmitting the configuration data to the radio node may be performed by different network nodes or entities, which may be able to communicate via a suitable interface, e.g., an X2 interface in the case of LTE or a corresponding interface for NR. Configuring a terminal (e.g. WD <NUM>) may comprise scheduling downlink and/or uplink transmissions for the terminal, e.g. downlink data and/or downlink control signaling and/or DCI and/or uplink control or data or communication signaling, in particular acknowledgement signaling, and/or configuring resources and/or a resource pool therefor. In particular, configuring a terminal (e.g. WD <NUM>) may comprise configuring the WD <NUM> to perform certain measurements on certain subframes or radio resources and reporting such measurements according to embodiments of the present disclosure.

Some embodiments provide for determining a fixed size resource block assignment in random access response, RAR, scheduling of MSG3 transmission based at least in part on at least one of bandwidth part size, slot/non-slot transmission and resource allocation type, are disclosed. Some embodiments reduce a number of bits needed to indicate resource block size to be allocated by the WD for MSG3 message transmission.

For an RAR grant in NR, note that the RAN2 technical standards entity already has decided on <NUM> bits for UL grant in RAR, which has the same size as the RAR grant in LTE. It may be natural to use a similar RAR grant structure for NR, but certain NR specific design factors need to be considered. These factors include the following:.

Returning to the drawing figures, in which like elements are referred to by like reference numerals, there is shown in <FIG> a schematic diagram of a communication system <NUM>, according to an embodiment, such as a 3GPP-type cellular network that may support standards such as LTE and/or NR (<NUM>), which comprises an access network <NUM>, such as a radio access network, and a core network <NUM>. The access network <NUM> comprises a plurality of network nodes 16a, 16b, 16c (referred to collectively as network nodes <NUM>), such as NBs, eNBs, gNBs or other types of wireless access points, each defining a corresponding coverage area 18a, 18b, 18c (referred to collectively as coverage areas <NUM>). Each network node 16a, 16b, 16c is connectable to the core network <NUM> over a wired or wireless connection <NUM>. A first wireless device (WD) 22a located in coverage area 18a is configured to wirelessly connect to, or be paged by, the corresponding network node 16c. A second WD 22b in coverage area 18b is wirelessly connectable to the corresponding network node 16a. While a plurality of WDs 22a, 22b (collectively referred to as wireless devices <NUM>) are illustrated in this example, the disclosed embodiments are equally applicable to a situation where a sole WD is in the coverage area or where a sole WD is connecting to the corresponding network node <NUM>. Note that although only two WDs <NUM> and three network nodes <NUM> are shown for convenience, the communication system may include many more WDs <NUM> and network nodes <NUM>.

As an example, WS <NUM> can be in communication with an eNB for LTE/E-UTRAN and a gNB for NR/NG-RAN.

A network node <NUM> is configured to include an assignment unit <NUM> which is configured to determine a fixed size resource block, RB, assignment in random access response, RAR, scheduling of MSG3 transmission based at least in part on at least one of bandwidth part size, whether transmission is one of slot and non-slot transmission and resource allocation type. A wireless device <NUM> is configured to include an allocation unit <NUM> which is configured to allocate RBs to the MSG3 transmission according to the assignment.

The host application <NUM> may be operable to provide a service to a remote user, such as a WD <NUM> connecting via an OTT connection <NUM> terminating at the WD <NUM> and the host computer <NUM>. The "user data" may be data and information described herein as implementing the described functionality. In one embodiment, the host computer <NUM> may be configured for providing control and functionality to a service provider and may be operated by the service provider or on behalf of the service provider. The processing circuitry <NUM> of the host computer <NUM> may enable the host computer <NUM> to observe, monitor, control, transmit to and/or receive from the network node <NUM> and or the wireless device <NUM>.

The communication system <NUM> further includes a network node <NUM> provided in a communication system <NUM> and comprising hardware <NUM> enabling it to communicate with the host computer <NUM> and with the WD <NUM>.

Thus, the network node <NUM> further has software <NUM> stored internally in, for example, memory <NUM>, or stored in external memory (e.g., database, storage array, network storage device, etc.) accessible by the network node <NUM> via an external connection. The processing circuitry <NUM> may be configured to control any of the methods and/or processes described herein and/or to cause such methods, and/or processes to be performed, e.g., by network node <NUM>. Processor <NUM> corresponds to one or more processors <NUM> for performing network node <NUM> functions described herein. The memory <NUM> is configured to store data, programmatic software code and/or other information described herein. In some embodiments, the software <NUM> may include instructions that, when executed by the processor <NUM> and/or processing circuitry <NUM>, causes the processor <NUM> and/or processing circuitry <NUM> to perform the processes described herein with respect to network node <NUM>. For example, processing circuitry <NUM> of the network node <NUM> may include assignment unit <NUM> configured to determine a fixed size resource block, RB, assignment in random access response, RAR, scheduling of MSG3 transmission based at least in part on at least one of bandwidth part size, whether transmission is one of slot and non-slot transmission and resource allocation type.

The processing circuitry <NUM> may be configured to control any of the methods and/or processes described herein and/or to cause such methods, and/or processes to be performed, e.g., by WD <NUM>. The processor <NUM> corresponds to one or more processors <NUM> for performing WD <NUM> functions described herein. The WD <NUM> includes memory <NUM> that is configured to store data, programmatic software code and/or other information described herein. In some embodiments, the software <NUM> and/or the client application <NUM> may include instructions that, when executed by the processor <NUM> and/or processing circuitry <NUM>, causes the processor <NUM> and/or processing circuitry <NUM> to perform the processes described herein with respect to WD <NUM>. For example, the processing circuitry <NUM> of the wireless device <NUM> may include an allocation unit <NUM> configured to allocate RBs to the MSG3 transmission according to an assignment received from a network node.

Although <FIG> and <FIG> show various "units" such as assignment unit <NUM>, and allocation unit <NUM> as being within a respective processor, it is contemplated that these units may be implemented such that a portion of the unit is stored in a corresponding memory within the processing circuitry. In other words, the units may be implemented in hardware or in a combination of hardware and software within the processing circuitry.

<FIG> is a block diagram of an alternative host computer <NUM>, which may be implemented at least in part by software modules containing software executable by a processor to perform the functions described herein. The host computer <NUM> include a communication interface module <NUM> configured to set up and maintain a wired or wireless connection with an interface of a different communication device of the communication system <NUM>. The memory module <NUM> is configured to store data, programmatic software code and/or other information described herein.

<FIG> is a block diagram of an alternative network node <NUM>, which may be implemented at least in part by software modules containing software executable by a processor to perform the functions described herein. The network node <NUM> includes a radio interface module <NUM> configured for setting up and maintaining at least a wireless connection <NUM> with a WD <NUM> located in a coverage area <NUM> served by the network node <NUM>. The network node <NUM> also includes a communication interface module <NUM> configured for setting up and maintaining a wired or wireless connection with an interface of a different communication device of the communication system <NUM>. The communication interface module <NUM> may also be configured to facilitate a connection <NUM> to the host computer <NUM>. The memory module <NUM> that is configured to store data, programmatic software code and/or other information described herein. The assignment module <NUM> is configured to determine a fixed size resource block, RB, assignment in random access response, RAR, scheduling of MSG3 transmission based at least in part on at least one of bandwidth part size, whether transmission is one of slot and non-slot transmission and resource allocation type.

<FIG> is a block diagram of an alternative wireless device <NUM>, which may be implemented at least in part by software modules containing software executable by a processor to perform the functions described herein. The WD <NUM> includes a radio interface module <NUM> configured to set up and maintain a wireless connection <NUM> with a network node <NUM> serving a coverage area <NUM> in which the WD <NUM> is currently located. The memory module <NUM> is configured to store data, programmatic software code and/or other information described herein. The allocation module <NUM> is configured to allocate RBs to the MSG3 transmission according to an assignment received from a network node.

<FIG> is a flowchart illustrating an exemplary method implemented in a communication system, such as, for example, the communication system of <FIG> and <FIG>, in accordance with one embodiment. The communication system may include a host computer <NUM>, a network node <NUM> and a WD <NUM>, which may be those described with reference to <FIG>. In a first step of the method, the host computer <NUM> provides user data (block S100). In an optional substep of the first step, the host computer <NUM> provides the user data by executing a host application, such as, for example, the host application <NUM> (block S102). In a second step, the host computer <NUM> initiates a transmission carrying the user data to the WD <NUM> (block S104). In an optional third step, the network node <NUM> transmits to the WD <NUM> the user data which was carried in the transmission that the host computer <NUM> initiated, in accordance with the teachings of the embodiments described throughout this disclosure (block S106). In an optional fourth step, the WD <NUM> executes a client application, such as, for example, the client application <NUM>, associated with the host application <NUM> executed by the host computer <NUM> (block S108).

<FIG> is a flowchart illustrating an exemplary method implemented in a communication system, such as, for example, the communication system of <FIG>, in accordance with one embodiment. The communication system may include a host computer <NUM>, a network node <NUM> and a WD <NUM>, which may be those described with reference to <FIG> and <FIG>. In a first step of the method, the host computer <NUM> provides user data (block S110). In an optional substep (not shown) the host computer <NUM> provides the user data by executing a host application, such as, for example, the host application <NUM>. In a second step, the host computer <NUM> initiates a transmission carrying the user data to the WD <NUM> (block S112). In an optional third step, the WD <NUM> receives the user data carried in the transmission (block S114).

<FIG> is a flowchart illustrating an exemplary method implemented in a communication system, such as, for example, the communication system of <FIG>, in accordance with one embodiment. The communication system may include a host computer <NUM>, a network node <NUM> and a WD <NUM>, which may be those described with reference to <FIG> and <FIG>. In an optional first step of the method, the WD <NUM> receives input data provided by the host computer <NUM> (block S116). In an optional substep of the first step, the WD <NUM> executes the client application <NUM>, which provides the user data in reaction to the received input data provided by the host computer <NUM> (block S118). Additionally or alternatively, in an optional second step, the WD <NUM> provides user data (block S120). In an optional substep of the second step, the WD provides the user data by executing a client application, such as, for example, client application <NUM> (block S122). In providing the user data, the executed client application <NUM> may further consider user input received from the user. Regardless of the specific manner in which the user data was provided, the WD <NUM> may initiate, in an optional third substep, transmission of the user data to the host computer <NUM> (block S124). In a fourth step of the method, the host computer <NUM> receives the user data transmitted from the WD <NUM>, in accordance with the teachings of the embodiments described throughout this disclosure (block S126).

<FIG> is a flowchart illustrating an exemplary method implemented in a communication system, such as, for example, the communication system of <FIG>, in accordance with one embodiment. The communication system may include a host computer <NUM>, a network node <NUM> and a WD <NUM>, which may be those described with reference to <FIG> and <FIG>. In an optional first step of the method, in accordance with the teachings of the embodiments described throughout this disclosure, the network node <NUM> receives user data from the WD <NUM> (block S128). In an optional second step, the network node <NUM> initiates transmission of the received user data to the host computer <NUM> (block S130). In a third step, the host computer <NUM> receives the user data carried in the transmission initiated by the network node <NUM> (block S132).

<FIG> is a flowchart of an exemplary process in a network node <NUM> for RB assignment according to the principles set forth herein. The process includes determining, via the assignment unit <NUM>, a fixed size resource block, RB, assignment in random access response, RAR, scheduling of MSG3 transmission based at least in part on at least one of bandwidth part size, whether transmission is one of slot and non-slot transmission and resource allocation type (block S134).

<FIG> is a flowchart of another exemplary process in a network node <NUM> for RB assignment according to the principles set forth herein. One or more Blocks and/or functions performed by network node <NUM> may be performed by one or more elements of network node <NUM> such as by assignment unit <NUM> in processing circuitry <NUM>, processor <NUM>, communication interface <NUM>, radio interface <NUM>, etc. In one or more embodiments, network node <NUM> such as via one or more of processing circuitry <NUM>, processor <NUM>, radio interface <NUM> and communication interface <NUM> is configured to determine (block <NUM>) a fixed size resource block, RB, assignment for random access response, RAR, scheduling of an uplink transmission based at least in part on at least one of: whether the uplink transmission is one of slot and non-slot transmission, resource allocation type, as described herein. In one or more embodiments, network node <NUM> such as via one or more of processing circuitry <NUM>, processor <NUM>, radio interface <NUM> and communication interface <NUM> is configured to optionally indicate (block S138) the fixed sized RB assignment to the wireless device <NUM>, as described herein.

According to one or more embodiments of this aspect, the fixed size RB assignment indicates a RB granularity where the RB granularity is based at least in part on one of a bandwidth part size and transmission duration. According to one or more embodiments of this aspect, the RB granularity indicates a RB start position and quantity of RBs for the uplink transmission. According to one or more embodiments of this aspect, the uplink transmission corresponds to a message <NUM>, MSG3, transmission. According to one or more embodiments of this aspect, the fixed sized RB assignment is indicated in a message <NUM>, MSG2, transmission.

According to one or more embodiments of this aspect, the fixed sized RB assignment is based at least in part on a bandwidth part size. According to one or more embodiments of this aspect, the uplink transmission is the non-slot transmission having a time duration less than a slot. According to one or more embodiments of this aspect, the fixed size RB assignment corresponds to a subset of RBs in a bandwidth part size based at least in part on a threshold. According to one or more embodiments of this aspect, the threshold is based at least in part on a transmission duration. According to one or more embodiments of this aspect, the fixed size RB assignment assigns RBs corresponding to one of: lowest RB values of a group of RBs, highest RB values of the group of RBs, and middle RB values of the group of RBs.

<FIG> is a flowchart of an exemplary process in a wireless device <NUM> according to some embodiments of the present disclosure. The process includes receiving, via a radio interface <NUM>, from the network node <NUM> a fixed size resource block, RB, assignment in random access response, RAR, scheduling of MSG3 transmission based at least in part on at least one of bandwidth part size, whether transmission is one of slot and non-slot transmission and resource allocation type (block S140). The process further allocates, via the allocation unit <NUM>, RBs to the MSG3 transmission according to the assignment (block S142).

<FIG> is a flowchart of an exemplary process in a wireless device <NUM> according to some embodiments of the present disclosure. One or more Blocks and/or functions performed by wireless device <NUM> may be performed by one or more elements of wireless device <NUM> such as by allocation unit <NUM> in processing circuitry <NUM>, processor <NUM>, radio interface <NUM>, etc. In one or more embodiments, wireless device <NUM> such as via one or more of processing circuitry <NUM>, processor <NUM> and radio interface <NUM> is configured to cause (block S144) transmission of an uplink transmission where the uplink transmission is based at least in part on a fixed size resource block, RB, assignment for RAR scheduling of the uplink transmission and where the fixed size RB assignment is based at least in part on at least one of: whether the uplink transmission is one of slot and non-slot transmission and resource allocation type, as described herein.

The fixed size resource block assignment in RAR grant scheduling MSG3 transmission in NR can consider the BWP size, slot vs. non-slot based transmission, and resource allocation type.

Embodiment <NUM>: In some embodiments, the fixed size resource block assignment in RAR grant indicating start RB position and RB length uses x-RB granularity, where x>=<NUM> and takes into account at least the BWP size, slot vs. non-slot based transmission, and resource allocation type.

In this embodiment, unlike the fixed size resource block assignment in LTE RAR grant where start RB position and RB length are fixed at the granularity of <NUM> RB, the assignment granularity is a function of BWP size and/or transmission duration.

Example <NUM>: The x-RB granularity values are fixed in the spec. Table <NUM> provides an example of how the x-RB granularity may vary depending on BWP size and/or transmission duration.

Example <NUM>: The x-RB granularity can be configured in system information (e.g., remaining minimum system information (RMSI)) and/or radio resource control (RRC). For example, a set of RB granularity values {<NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>} may be chosen as the set of configurable parameters, and RMSI can configure the used RB granularity values for different BWP sizes and/or transmission durations, and optionally RRC may reconfigure the used RB granularity values.

Embodiment <NUM>: The fixed size resource block assignment in the RAR grant indicating start RB position and RB length uses x-RB granularity and is applicable to a subset of RBs in a BWP if the BWP size is larger than a threshold, i.e., based at least in part on a threshold.

In this embodiment, the range of RBs that may be assigned to MSG3 transmission is limited to a subset of all the RBs in a BWP if the BWP is larger than a threshold. The threshold values may be different depending on transmission durations. The threshold values may be fixed in the spec or configured in system information (e.g. RMSI) and/or RRC.

Example <NUM>: For slot based transmission, if a BWP size is larger than N_th (e.g., N_th = <NUM> RBs), the fixed size resource block assignment indicating start RB position and RB length with <NUM>-RB granularity is used to assign the RBs from the lowest N_th RBs in the BWP or from the highest N_th RBs in the BWP or from the center N_th RBs in the BWP.

Embodiment <NUM>: The fixed size resource block assignment in RAR grant uses a fixed size bitmap of RB groups (RBGs) to indicate RBs assigned to MSG3 transmission.

In this embodiment, a fixed size bitmap of RBGs is used to indicate RBs assigned to MSG3 transmission. Assume the length of the bitmap is x (e.g., if the field of fixed size resource bock assignment has <NUM> bits, x = <NUM> without frequency hopping, or x = <NUM> if <NUM> bits are excluded and used for frequency hopping indication). Assume the BWP has a size of N_RB. If floor (N_RB/x) >=<NUM>, each bit indicates if the corresponding floor(N_RB/x) RBs are assigned to MSG3 transmission. If floor(N_RB/x) <<NUM>, i.e., N_RB < x, then each bit of N_RB bits out of x bits is used to indicate if the corresponding RB is assigned and the rest of x - N_RB bits are reserved.

Example <NUM>: For a BWP with <NUM> RBs and <NUM>-bit bitmap, the i-th bit, i=<NUM>,. ,<NUM>, indicates if the set of <NUM> RBs from <NUM>*i, <NUM>*i+<NUM>,. , to <NUM>*i+<NUM> is assigned for MSG3 transmission.

Example <NUM>: For a BWP with <NUM> RBs and <NUM>-bit bitmap, each bit of the <NUM> bits out of <NUM> bits is used to indicate if the corresponding RB is assigned and the rest of <NUM> bits are reserved.

This embodiment <NUM> may not be efficient when BWP size is large. In particular, MSG3 is small payload of usually less than <NUM> bytes. For example, in Example <NUM>, the RB assignment granularity is <NUM>, which may be too large for MSG3. With limited number (<=<NUM>) of bits for fixed size resource block assignment, we can limit RAR grant within a subset of large BWP to get finer RB assignment granularity, which motives the following embodiment.

Embodiment <NUM>: The fixed size resource block assignment in the RAR grant uses a fixed size bitmap of RBGs to indicate RBs within a subset of RBs in a BWP if the BWP size is larger than a threshold.

Example <NUM>: For slot based transmission, if a BWP size is larger than N_th (e.g., N_th = <NUM> RBs) and a fixed size of <NUM>-bit bitmap is used, the fixed size resource block assignment using the bitmap is used to assign the RBs from the lowest N_th RBs in the BWP or from the highest N_th RBs in the BWP or from the center N_th RBs in the BWP or from a part of N_th-RBs configured by RSMI or RRC. The i-th bit, i=<NUM>,. ,<NUM>, indicates if the set of <NUM> RBs, <NUM>*i, <NUM>*i+<NUM>, in the N_th RBs are assigned for MSG3 transmission.

Embodiment <NUM>: The fixed size resource block assignment in the RAR grant uses a fixed size bitmap of RBGs and a RBG size to indicate assigned RBs in a BWP or within a subset of RBs in a BWP if the BWP size is larger than a threshold that may depend on RBG size.

In this embodiment, a RBG size can be configured by the network that may depend on BWP sizes and/or transmission durations, or RBG sizes corresponding to different BWP sizes and/or transmission durations can be fixed in the spec. Then each bit in the fixed size bitmap indicates if the RBs in the corresponding RBG are assigned. Assume the length of the bitmap is x, the RBG size is y, and the BWP has N_RB RBs. If x*y >= N_RB, then each bit of the ceil(N_RB/y) bits out of the x bits is used to indicate if the corresponding RBG is assigned and the rest of x - ceil(N_RB/y) bits are reserved. If x*y < N_RB, then a subset of x*y RBs out of the BWP can be assigned and each bit of the x bits is used to indicate if the corresponding RBG is assigned. The subset of x*y RBs can be the lowest x*y RBs in the BWP or the highest x*y RBs in the BWP or the center x*y RBs in the BWP. This can be either fixed or configured.

Below are two examples to illustrate this embodiment.

Example <NUM>: Assume the length of the bitmap is x=<NUM>, the RBG size is y=<NUM>, and the BWP has N_RB=<NUM> RBs. This may be used for non-slot based MSG3 transmission. Since x*y=<NUM>>N_RB=<NUM>, each bit of the ceil(<NUM>/<NUM>)=<NUM> bits out of the <NUM> bits is used to indicate if the corresponding RBG is assigned and the rest of <NUM>-<NUM>=<NUM> bits are reserved.

Example <NUM>: Assume the length of the bitmap is x=<NUM>, the RBG size is y=<NUM>, and the BWP has N_RB=<NUM> RBs. This may be used for slot based MSG3 transmission. Since x*y=<NUM><N_RB=<NUM>, the bitmap can only indicate a subset of x*y=<NUM> RBs out of the <NUM>-RB BWP and each bit of the x=<NUM> bits is used to indicate if the corresponding RBG is assigned. The <NUM> RBs that can be assigned can be the lowest <NUM> RBs in the BWP or the highest <NUM> RBs in the BWP or the center <NUM> RBs in the BWP, depending on the fixed rule or configuration.

Embodiment <NUM>: The fixed size resource assignment in the RAR grant indicates jointly the time domain allocation and frequency domain allocation. The granularities in frequency and time take into account at least the BWP size, slot vs. non-slot based transmission, and resource allocation type.

In the previous embodiments, time domain allocation and frequency domain allocation may be considered separately. It can be observed that, in some cases, the number of bits necessary for frequency domain allocation may be less than assigned, which leaves some bits unused in the RAR grant.

In this embodiment, the granularities in frequency and time domains can be jointly considered in order to maximize the utility of bits in the RAR grant. If there are fewer time domain allocation candidates, then more bits are assigned for frequency domain resource allocation by adopting a smaller frequency domain granularity. If there are more time domain allocation candidates, then fewer bits are assigned for frequency domain resource allocation by adopting a larger frequency domain granularity. A general encoding of the joint time and frequency domain resource assignment has the following form is shown in <FIG>.

Within the fixed number of resource allocation bits, the first part of the bits indicates the time domain allocation and the second part indicates the frequency domain allocation. The encoding of the time domain resource allocation should provide non-ambiguous indication of the time domain scheduling type. One nonlimiting example of such time domain resource allocation is to enforce a prefix structure. Nonlimiting examples are explained in the following.

Consider a BWP of N_RB=<NUM> RBs in size and frequency domain granularities as shown in Table <NUM>. It can be calculated that the numbers of bits needed for frequency domain allocation are as follows for the different time domain scheduled transmission durations:.

If a total of <NUM> bits are assigned for joint time and frequency domain resource allocation, there will be.

If the first bit is '<NUM>', then a slot based scheduling is signaled as shown in <FIG>. If the first bit is '<NUM>', then a non-slot scheduling is signaled. If the first two bits are '<NUM>', then a <NUM>-symbol non-slot based scheduling is signaled and the two candidates are indicated using the first <NUM> bits as follows as shown in <FIG>. If the first three bits are '<NUM>', then a <NUM>-symbol non-slot based scheduling is signaled and the four candidates are indicated using the first <NUM> bits as shown in <FIG>. If the first three bits are '<NUM>', then a <NUM>-symbol non-slot based scheduling is signaled and the fourteen candidates are indicated using the first <NUM> bits as shown in <FIG>. If it is decided that more <NUM>-symbol non-slot based scheduling candidates are needed, then embodiments teach that the frequency domain granularity should be reduced to allow more bits for encoding the time domain candidates. For instance, if the frequency domain granularity is changed to <NUM> RBs for <NUM>-symbol non-slot based scheduling, then the frequency domain resource allocation only needs <NUM> bits. This leaves <NUM> bits to encode the following nine time domain allocation candidates, as shown in <FIG>.

The sections below provide non-limiting examples of how certain aspects of the proposed solutions could be implemented within the framework of a specific communication standard. In particular, the below sections provide non-limiting examples of how the proposed solutions could be implemented within the framework of a 3GPP TSG RAN standard. The changes described by sections below are merely intended to illustrate how certain aspects of the proposed solutions could be implemented in a particular standard. However, the proposed solutions could also be implemented in other suitable manners, both in the 3GPP Specification and in other specifications or standards.

In this contribution, we discuss the remaining DCI issues including RAR grant and PDCCH ordered RA that are needed to stabilize the basic and essential NR functionalities within the scope of the drop approved during RAN#<NUM>.

As part of the random access procedure, after receiving Random Access Request in MSG1, gNB will provide the required information in MSG2 - Random Access Response (RAR) message - for UE to send the MSG3 (RRC Connection Request). This is referred to the RAR Grant in the physical layer. In LTE, RAR Grant is a <NUM>-bit message with contents from MSB to LSB as [<NUM>].

For RAR grant in NR, note that RAN2 already has decided on <NUM> bits for UL grant in RAR, which has the same size as the RAR grant in LTE. It is natural to use a similar RAR grant structure for NR, but certain NR specific design factors need to be considered. We elaborate these aspects in the following.

The use of NR resource allocation type <NUM> - bitmap of RBGs - is less suitable for RAR grant. This is because MSG3 is small payload of usually less than <NUM> bytes. For large BWP, the RBG size may be <NUM> or <NUM>, which would be too large for MSG3. With limited number (<=<NUM>) of bits for fixed size resource block assignment, we have to limit RAR grant within a subset of large BWP and smaller RBG size is used for RAR grant. This may require a new set of special rules of handling RAR grant, including (<NUM>) which subset of BWP is used and (<NUM>) the RBG size (which may further depend on time domain assignment with <NUM>, <NUM>, <NUM> OSs or slot-based transmission). The rules may be fixed in the spec (e.g., the bitmap in RAR grant is considered as the MSB or LSB or central bits in the full bitmap for the whole BWP), and/or signaled in system information, and/or RRC configured. Due to these complications, we prefer to use NR resource allocation type <NUM> for RAR grant.

Proposal <NUM> The <NUM>-bit RAR grant in NR has contents from MSB to LSB as.

In the LS [<NUM>] sent by RAN2 to RAN1, it says that.

In this section, we present our views on PDCCH ordered random access for NR.

Proposal <NUM> For PDCCH ordered random access, reinterpret some of the existing fields in format 1_0 or 0_0 and set the other fields as follows.

In this contribution, we discuss the remaining DCI issues needed to stabilize the basic and essential NR functionalities within the scope of the drop approved during RAN#<NUM>.

Accordingly, all embodiments can be combined in any way and/or combination, and the present specification, including the drawings, shall be construed to constitute a complete written description of all combinations and subcombinations of the embodiments described herein, and of the manner and process of making and using them, and shall support any such combination or subcombination.

Claim 1:
A method performed by a network node (<NUM>) configured to communicate with a wireless device (<NUM>), the method comprising:
determining (S136) a fixed size resource block, RB, assignment for an uplink transmission by the wireless device (<NUM>), the uplink transmission corresponding to a message <NUM>, MSG3, transmission of a New Radio, NR, random access procedure and being scheduled by a random access response, RAR, corresponding to a message <NUM>, MSG2, transmission of the NR random access procedure in which the fixed size RB assignment is indicated to the wireless device (<NUM>),
wherein the fixed size RB assignment is based at least in part on:
whether the uplink transmission is a slot transmission having a time duration of a slot or a non-slot transmission having a time duration less than a slot; and/or
resource allocation type used in the RAR.