CN112020842A

CN112020842A - Method for indicating time domain resource allocation for physical downlink shared channel before RRC connection

Info

Publication number: CN112020842A
Application number: CN201980028413.1A
Authority: CN
Inventors: 林志鹏; 李静雅; 张剑威
Original assignee: Telefonaktiebolaget LM Ericsson AB
Current assignee: Telefonaktiebolaget LM Ericsson AB
Priority date: 2018-02-28
Filing date: 2019-02-28
Publication date: 2020-12-01
Anticipated expiration: 2039-02-28
Also published as: EP3759858A1; US12047981B2; JP2021521664A; US10609713B2; BR112020017498A2; CL2020002209A1; JP7122385B2; RU2021124415A; CN117335938A; US20200252939A1; RU2754866C1; WO2019166991A1; PH12020500654A1; CN112020842B; US20190297629A1

Abstract

A method performed by a User Equipment (UE) (110, 500, 800) is disclosed. The method comprises the following steps: an indication of a time domain resource allocation table for one or more Physical Downlink Shared Channel (PDSCH) transmissions is received (401) at a UE (110, 500, 800). The method comprises the following steps: determining (402) a time domain resource allocation table for the one or more PDSCH transmissions based on the received indication.

Description

Method for indicating time domain resource allocation for physical downlink shared channel before RRC connection

Technical Field

The present disclosure relates generally to wireless communications, and more particularly, to a method for indicating time domain resource allocation for Physical Downlink Shared Channel (PDSCH) transmissions.

Background

In order to connect to a network, a wireless device (e.g., User Equipment (UE)) needs to acquire network synchronization and acquire necessary system information, including system information in a Master Information Block (MIB) and Remaining Minimum System Information (RMSI). The synchronization signal is used to adjust the frequency of the device relative to the network. The synchronization signal is also used to find the correct timing of the signal received from the network. In New Radios (NR), the synchronization and access procedures may involve several signals, including a Primary Synchronization Signal (PSS), a Secondary Synchronization Signal (SSS), a Physical Broadcast Channel (PBCH), and synchronization signals and PBCH blocks (SSB or SS/PBCH blocks).

PSS allows network detection in the presence of high initial frequency errors (up to tens of ppm). The SSS allows for more accurate frequency adjustment and channel estimation while providing basic network information (e.g., cell ID).

The PBCH provides a subset of minimum system information for random access and a configuration for taking the remaining minimum system information in the RMSI. The PBCH also provides timing information within the cell (e.g., to separate timing between beams transmitted from the cell). The amount of information that can be loaded in PBCH is very limited in order to reduce the size. In addition, demodulation reference signals (DMRS) are interleaved with PBCH resources to allow them to be properly received.

The SSB includes the above signals (i.e., PSS, SSS, and PBCH DMRS) and PBCH. Depending on the frequency range, the SSB may have different subcarrier spacing (SCS) (e.g., 15 kilohertz (kHz), 30kHz, 120kHz, or 240 kHz).

In NR, RMSI is carried in a Physical Downlink Control Channel (PDCCH) scheduled PDSCH in a control resource set (CORESET) configured by PBCH. The RMSI contains a remaining subset of the smallest system information (e.g., a bitmap of the SSB actually sent).

A plurality of (usually relatively close in time) SSBs form a set of SS bursts. The set of SS bursts is sent periodically. The periodicity is configured in the RMSI. For initial access, a set periodicity of 20 millisecond (ms) SS bursts is assumed. Fig. 1 and 2 below show SSB mapping within a slot and SS burst set mapping to a slot within 5ms, respectively.

Fig. 1 shows an example of SSB symbols in a slot. More specifically, fig. 1 shows SSB mapping for different SCS including 15kHz, 30kHz (pattern 1), 30kHz (pattern 2), 120kHz and 240 kHz. SSB mapping within two slots (slot n and slot n +1) is shown for 15kHz, 30kHz (pattern 1), 30kHz (pattern 2) and 120kHz SCS. As shown in fig. 1, each slot contains 14 Orthogonal Frequency Division Multiplexing (OFDM) symbols (represented as boxes numbered 0-13). For a 240kHz SCS, SSB mapping within 4 slots (slot n, slot n +1, slot n +2, and slot n +3) is shown. For the 240kHz SCS example, each slot contains 14 OFDM symbols (represented as boxes numbered 0-13).

In the example of fig. 1, the OFDM symbols in parentheses are mapped to candidate SSB locations. Each candidate SSB location includes 4 OFDM symbols. For example, for the example of 15kHz SCS, slot n includes two candidate SSB locations: a first one comprising OFDM symbols 2-5; and a second one comprising OFDM symbols 8-11. Slot n +1 also includes two candidate SSB locations: a first one comprising OFDM symbols 2-5; and a second one comprising OFDM symbols 8-11. The mapping for 30kHz (pattern 2) SCS is the same as for 15kHz SCS.

For the example of 30kHz (style 1) SCS, slot n includes two candidate SSB locations: including a first one of OFDM symbols 4-7; and a second one comprising OFDM symbols 8-11. Slot n +1 also includes two candidate SSB locations: a first one comprising OFDM symbols 2-5; and a second one comprising OFDM symbols 6-9. The mapping for 120kHz SCS is the same as for 30kHz (pattern 1) SCS.

For the example of 240kHz SCS, some of the candidate SSB locations extend across the slot. For example, slot n includes a first candidate SSB location, which includes OFDM symbols 8-11. The second candidate SSB location extends across slot n and slot n +1, including OFDM symbols 12-13 of slot n and OFDM symbols 0-1 of slot n + 1. The time slot n +1 further includes: a third candidate SSB location comprising OFDM symbols 2-5, and a fourth candidate SSB location comprising OFDM symbols 6-9. Similarly, slot n +2 includes: a first candidate SSB location comprising OFDM symbols 4-7, and a second candidate SSB location comprising OFDM symbols 8-11. The third candidate SSB location extends across slot n +2 and slot n +3, including OFDM symbols 12-13 of slot n +2 and OFDM symbols 0-1 of slot n + 3. Slot n +3 further includes: a fourth candidate SSB location comprising OFDM symbols 2-5 and a fifth candidate SSB location comprising OFDM symbols 6-9.

Fig. 2 shows an example of a set of SS bursts in a slot within 5 ms. More specifically, fig. 2 shows an example of a set of SS bursts in a radio field of 5 ms. In the example of fig. 2, each box is a time slot. As shown in fig. 2, the set of SS bursts is mapped to slots within a 5ms window in a compact manner using a mapping pattern, resulting in high network energy efficiency. The locations of possible SSB locations in the time slots are shown in fig. 1, and as described above, the locations of the possible SSB locations are SCS dependent. The mapping pattern of SSBs has a periodicity of 2 slots (for SSBs with SCS values of 15kHz, 30kHz, or 120 kHz) and a periodicity of 4 slots (for SSBs with SCS values of 240 kHz). With this periodicity of 2 or 4 slots, SSB mapping can continue by repeating the pattern until the maximum number of SSBs is fully mapped.

Prior to a Radio Resource Control (RRC) connection, there are access messages and system information that need to be sent on the PDSCH to the wireless device. These messages and information may be: e.g., RMSI, Other System Information (OSI), paging, Random Access Response (RAR) (message 2), and message 4, etc. Existing methods for time domain resource allocation for messages and system information that need to be sent on the PDSCH prior to RRC connection have certain drawbacks. For example, existing approaches may lack flexibility in terms of the time domain resource allocation tables that may be used. Therefore, there is a need for a time resource indication mechanism for transmitting and receiving PDSCH carrying information and/or messages prior to RRC connection.

Disclosure of Invention

To address the foregoing problems of existing solutions, a method performed by a UE is disclosed. The method comprises the following steps: an indication of a time domain resource allocation table for one or more PDSCH transmissions is received at a UE. The method comprises the following steps: based on the received indication, a time domain resource allocation table for one or more PDSCH transmissions is determined.

In some embodiments, the UE may not be in RRC connected mode.

In certain embodiments, the received indication may be included in a System Information Block (SIB). In certain embodiments, the SIB may be system information block type 1(SIB 1). In certain embodiments, the received indication may include a PDSCH time resource allocation parameter. In some embodiments, the received indication may comprise one or more bits.

In some embodiments, the received indication may include a CORESET configuration. In certain embodiments, a time domain resource allocation table for one or more PDSCH transmissions may be configured in the RMSI, and the method may further comprise: when the CORESET configuration is configured in the RMSI, the time domain resource allocation table configured in the RMSI is determined to be used. In certain embodiments, the time domain resource allocation table for one or more PDSCH transmissions may be a time domain resource allocation table for RMSI, and the method may further comprise: when the CORESET configuration is configured in PBCH, it is determined to use a time domain resource allocation table for RMSI.

In certain embodiments, the time domain resource allocation table for one or more PDSCH transmissions may be a default time domain resource allocation table defined for all PDSCH transmissions prior to the RRC connection.

In certain embodiments, the time domain resource allocation table for one or more PDSCH transmissions may be one of a plurality of time domain resource allocation tables. In some embodiments, the plurality of time domain resource allocation tables may include a plurality of different default time domain resource allocation tables defined for PDSCH transmission prior to the RRC connection. In certain embodiments, a first time domain resource allocation table of the plurality of time domain resource allocation tables may comprise a default time domain resource allocation table configured for a PDSCH carrying a RMSI, and a second time domain resource allocation table of the plurality of time domain resources may comprise a default time domain resource allocation table configured for a PDSCH carrying a different message than the RMSI.

In certain embodiments, the one or more PDSCH transmissions may include one or more of the following: RMSI; OSI; a paging message; random access message 2; and a random access message 4.

In some embodiments, the method may further comprise: determining a time resource allocation for one or more PDSCH transmissions using the determined time domain resource allocation table.

In certain embodiments, the time domain resource allocation table for one or more PDSCH transmissions may include one or more of: a row index; a DMRS location; a PDSCH mapping type; a slot level offset; a starting OFDM symbol in a slot; a number of allocated OFDM symbols for one or more PDSCH transmissions.

A UE is also disclosed. The UE includes a receiver, a transmitter, and processing circuitry coupled to the receiver and the transmitter. The processing circuitry is configured to: an indication of a time domain resource allocation table for one or more PDSCH transmissions is received at a UE. The processing circuitry is configured to: determining a time domain resource allocation table for one or more PDSCH transmissions based on the received indication.

A computer program comprising instructions configured to perform the above method in a UE is also disclosed.

Also disclosed is a computer program product comprising a non-transitory computer-readable storage medium comprising a computer program comprising computer-executable instructions that, when executed on a processor, are configured to perform the above-described method in a UE.

A method performed by a network node is also disclosed. The method comprises the following steps: a time domain resource allocation table for one or more PDSCH transmissions is determined. The method comprises the following steps: an indication of a time domain resource allocation table for one or more PDSCH transmissions is sent to the UE.

In some embodiments, the UE may not be in RRC connected mode.

In certain embodiments, the indication may be included in a SIB. In certain embodiments, the SIB may be SIB 1. In certain embodiments, the indication may include a PDSCH time resource allocation parameter. In some embodiments, the indication may comprise one or more bits.

In some embodiments, the indication may include a CORESET configuration. In certain embodiments, a time domain resource allocation table for one or more PDSCH transmissions may be configured in the RMSI, and when the CORESET configuration is configured in the RMSI, the indication may instruct the UE to use the time domain resource allocation table configured in the RMSI. In certain embodiments, the time domain resource allocation table for one or more PDSCH transmissions may be a time domain resource allocation table for RMSI, and the indication may indicate that the UE uses the time domain resource allocation table for RMSI when the CORESET configuration is configured in the PBCH.

In certain embodiments, the method may further include determining a time resource allocation for one or more PDSCH transmissions.

In certain embodiments, the time domain resource allocation table for one or more PDSCH transmissions may include one or more of: a row index; demodulating a reference signal position; a PDSCH mapping type; a slot level offset; a starting OFDM symbol in a slot; a number of allocated OFDM symbols for one or more PDSCH transmissions.

A network node is also disclosed. The network node comprises a receiver, a transmitter, and a processing circuit coupled to the receiver and the transmitter. The processing circuitry is configured to: a time domain resource allocation table for one or more PDSCH transmissions is determined. The processing circuitry is configured to: an indication of a time domain resource allocation table for one or more PDSCH transmissions is sent to the UE.

A computer program comprising instructions configured to perform the above method in a network node is also disclosed.

Also disclosed is a computer program product comprising a non-transitory computer-readable storage medium comprising a computer program comprising computer-executable instructions that, when executed on a processor, are configured to perform the above-mentioned method in a network node.

Certain embodiments of the present disclosure may provide one or more technical advantages. For example, certain embodiments enable indication of a time domain resource allocation table, e.g., for a PDSCH carrying a message prior to an RRC connection. This may advantageously allow for the definition of different time domain resource allocation tables, which may advantageously support flexibility and different configurations for PDSCH carrying different messages than RMSI, e.g., prior to RRC connection. Other advantages may be apparent to those of ordinary skill in the art. Certain embodiments may lack the advantages described, or may have some or all of the advantages described.

Drawings

For a more complete understanding of the disclosed embodiments and features and advantages thereof, reference is now made to the following descriptions taken in conjunction with the accompanying drawings, in which:

fig. 1 shows an example of SSB symbols in a slot;

fig. 2 shows an example of a set of SS bursts in a slot within 5 ms;

fig. 3 illustrates an example wireless communication network in accordance with certain embodiments;

fig. 4 is a flow chart of a method in a UE according to certain embodiments;

FIG. 5 is a schematic block diagram of a virtualization apparatus according to certain embodiments;

fig. 6 is a flow chart of a method in a network node according to some embodiments;

FIG. 7 is a schematic block diagram of a virtualization apparatus according to certain embodiments;

FIG. 8 illustrates one embodiment of a UE in accordance with certain embodiments; and

FIG. 9 is a schematic block diagram illustrating a virtualized environment in accordance with certain embodiments.

Detailed Description

Generally, all terms used herein are to be interpreted according to their ordinary meaning in the relevant art unless explicitly given and/or otherwise implied by the context. All references to "a/an/the element, device, component, means, step, etc" are to be interpreted openly as referring to at least one instance of the element, device, component, means, step, etc., unless explicitly stated otherwise. The steps of any method disclosed herein do not have to be performed in the exact order disclosed, unless one step must be explicitly described as being after or before another step and/or implicitly one step must be after or before another step. Any feature of any embodiment disclosed herein may be applied to any other embodiment, where appropriate. Likewise, any advantage of any embodiment may apply to any other embodiment, and vice versa. Other objects, features and advantages of the appended embodiments will become apparent from the description that follows.

Currently, the time domain allocation of PDSCH (and Physical Uplink Shared Channel (PUSCH)) in NR has not been done yet in RAN 1. However, some agreements have been reached. For example, the following consensus has been reached: for RRC connected mode, a time domain resource allocation table with 16 rows is signaled to the UE by RRC signaling in bandwidth part (BWP). Then, an index in the scheduling Downlink Control Information (DCI) will indicate the exact time resource allocation for the PDSCH.

The following consensus was also reached: for both slots and minislots, the scheduling DCI may provide an index to a UE-specific table that gives the OFDM symbols used for PDSCH (or PUSCH) transmission, including a starting OFDM symbol and an allocated length in OFDM symbols. A number of projects were identified that required further research, including: one or more tables; including slots used in the case of multi-slot/multi-micro-slot scheduling or slot indices for cross-slot scheduling; and Slot Format Indication (SFI) support for non-contiguous allocations. At least for RMSI scheduling, it has been agreed that at least one table entry needs to be fixed in the specification.

As described above, there are access messages and system information that need to be sent to the wireless device on PDSCH also before RRC connection. These messages and information may be: e.g., RMSI, OSI, paging, RAR (message 2), message 4, etc. Existing methods for time domain resource allocation for messages and system information that need to be sent on the PDSCH prior to RRC connection have certain drawbacks. For example, existing approaches may lack flexibility in terms of the time domain resource allocation tables that may be used. Therefore, there is a need for a time resource indication mechanism for transmitting and receiving PDSCH carrying information/messages, e.g., prior to RRC connection.

The present disclosure contemplates various embodiments that may address these and other deficiencies of existing approaches. In particular, the present disclosure contemplates various embodiments that may be applicable to time domain resource allocation for PDSCH carrying messages that need to be sent prior to RRC connection (such as those described above). In certain embodiments, a default time domain resource allocation table may be specified for at least the RMSI. For PDSCH carrying different messages than RMSI before RRC configuration, the corresponding time domain allocation table may be the same table as for RMSI or may be a different table.

In some embodiments, more than one time domain resource allocation table may be configured for PDSCH time domain resource allocation prior to the RRC connection. The present disclosure contemplates various embodiments by which a time domain resource allocation table for PDSCH transmission may be determined, e.g., according to one or more predefined rules and/or using an indication transmitted to a wireless device (e.g., UE), e.g., via RMSI/SIB1 or PBCH.

According to an example embodiment, a method in a UE is disclosed. The UE receives an indication of a time domain resource allocation table for one or more PDSCH transmissions. The UE determines a time domain resource allocation table for one or more PDSCH transmissions based on the received indication.

In some embodiments, the UE may not be in RRC connected mode when it receives the indication. In certain embodiments, the received indication may be included in a SIB. In certain embodiments, the SIB may be system information block type 1(SIB 1). In certain embodiments, the received indication may include a PDSCH time resource allocation parameter. In some embodiments, the received indication may comprise one or more bits.

According to another example embodiment, a method performed by a network node is disclosed. The network node determines a time domain resource allocation table for one or more PDSCH transmissions. The network node sends an indication of a time domain resource allocation table for one or more PDSCH transmissions to the UE.

In some embodiments, the UE may not be in RRC connected mode. In certain embodiments, the indication may be included in a SIB. In certain embodiments, the SIB may be SIB 1. In certain embodiments, the indication may include a PDSCH time resource allocation parameter. In some embodiments, the indication may comprise one or more bits.

Certain embodiments may provide one or more technical advantages. For example, certain embodiments enable a time domain resource allocation table for one or more PDSCH transmissions (e.g., for one or more PDSCH transmissions carrying messages prior to an RRC connection) to be indicated to a wireless device. This may advantageously allow for the definition of different time domain resource allocation tables, which may support flexibility and different configurations for PDSCH carrying different messages than RMSI prior to RRC connection. Other advantages may be apparent to those of ordinary skill in the art.

Some embodiments considered herein will now be described more fully with reference to the accompanying drawings. However, other embodiments are included within the scope of the subject matter disclosed herein, and the disclosed subject matter should not be construed as limited to only the embodiments set forth herein; rather, these embodiments are provided by way of example to convey the scope of the subject matter to those skilled in the art.

Fig. 3 illustrates an example wireless communication network in accordance with certain embodiments. Although the subject matter described herein may be implemented in any suitable type of system using any suitable components, the embodiments disclosed herein are described with respect to a wireless network (e.g., the example wireless network shown in fig. 3). For simplicity, the wireless network of fig. 3 depicts only network 106,

network nodes

160 and 160b, and

wireless devices

110, 110b, and 110 c. In practice, the wireless network may also include any additional elements adapted to support communication between wireless devices or between a wireless device and another communication device (e.g., a landline telephone, service provider, or any other network node or terminal device). Network node 160 and wireless device 110 are depicted with additional detail in the illustrated components. A wireless network may provide communication and other types of services to one or more wireless devices to facilitate the wireless devices in accessing and/or using the services provided by or via the wireless network.

The wireless network may include and/or interface with any type of communication, telecommunications, data, cellular, and/or radio network or other similar type of system. In some embodiments, the wireless network may be configured to operate according to certain standards or other types of predefined rules or procedures. Thus, particular embodiments of the wireless communication network may implement communication standards such as global system for mobile communications (GSM), Universal Mobile Telecommunications System (UMTS), Long Term Evolution (LTE), and/or other suitable 2G, 3G, 4G, or 5G standards; wireless Local Area Network (WLAN) standards such as the IEEE802.11 standard; and/or any other suitable wireless communication standard such as the worldwide interoperability for microwave access (WiMax), bluetooth, Z-Wave, and/or ZigBee standards.

Network 106 may include one or more backhaul networks, core networks, IP networks, Public Switched Telephone Networks (PSTN), packet data networks, optical networks, Wide Area Networks (WAN), Local Area Networks (LAN), Wireless Local Area Networks (WLAN), wireline networks, wireless networks, metropolitan area networks, and other networks to enable communication between devices.

Network node 160 and wireless device 110 include various components described in more detail below. These components work together to provide network node and/or wireless device functionality, such as providing wireless connectivity in a wireless network. In different embodiments, a wireless network may include any number of wired or wireless networks, network nodes, base stations, controllers, wireless devices, relay stations, and/or any other components or systems that may facilitate or participate in the communication of data and/or signals (whether via wired or wireless connections).

As used herein, a network node refers to a device that is capable, configured, arranged and/or operable to communicate directly or indirectly with a wireless device and/or with other network nodes or devices in a wireless network to enable and/or provide wireless access to the wireless device and/or to perform other functions (e.g., management) in the wireless network. Examples of network nodes include, but are not limited to, an Access Point (AP) (e.g., a radio access point), a Base Station (BS) (e.g., a radio base station, a node b (NodeB), an evolved NodeB (enb), and an NR NodeB (gNB)). Base stations may be classified based on the amount of coverage they provide (or in other words, based on their transmit power level), and thus they may also be referred to as femto base stations, pico base stations, micro base stations, or macro base stations. The base station may be a relay node or a relay host node that controls the relay. The network node may also include one or more (or all) parts of a distributed radio base station, such as a centralized digital unit and/or a Remote Radio Unit (RRU) (sometimes referred to as a Remote Radio Head (RRH)). Such a remote radio unit may or may not be integrated with an antenna as an antenna integrated radio. Parts of a distributed radio base station may also be referred to as nodes in a Distributed Antenna System (DAS). Still other examples of network nodes include multi-standard radio (MSR) devices (e.g., MSR BSs), network controllers (e.g., Radio Network Controllers (RNCs) or Base Station Controllers (BSCs)), Base Transceiver Stations (BTSs), transmission points, transmission nodes, multi-cell/Multicast Coordination Entities (MCEs), core network nodes (e.g., MSCs, MMEs), O & M nodes, OSS nodes, SON nodes, positioning nodes (e.g., E-SMLCs), and/or MDTs. As another example, the network node may be a virtual network node, as described in more detail below. More generally, however, a network node may represent any suitable device (or group of devices) as follows: the device (or group of devices) is capable, configured, arranged and/or operable to enable and/or provide wireless devices with access to a wireless network, or to provide some service to wireless devices that have access to a wireless network.

In fig. 3, network node 160 includes processing circuitry 170, device-readable medium 180, interface 190, auxiliary device 184, power supply 186, power supply circuitry 187, and antenna 162. Although network node 160 shown in the example wireless network of fig. 3 may represent a device that includes a combination of hardware components shown, other embodiments may include network nodes having different combinations of components. It should be understood that the network node comprises any suitable combination of hardware and/or software necessary to perform the tasks, features, functions and methods disclosed herein. Moreover, although the components of network node 160 are depicted as single blocks within larger blocks or nested within multiple blocks, in practice, the network node may include multiple different physical components making up a single illustrated component (e.g., device-readable medium 180 may include multiple separate hard disk drives and multiple RAM modules).

Similarly, the network node 160 may be composed of a plurality of physically separate components (e.g., a NodeB component and an RNC component, or a BTS component and a BSC component, etc.), each of which may have its respective corresponding component. In some scenarios where network node 160 includes multiple separate components (e.g., BTS and BSC components), one or more of these separate components may be shared among several network nodes. For example, a single RNC may control multiple nodebs. In such a scenario, each unique NodeB and RNC pair may be considered a single, separate network node in some instances. In some embodiments, the network node 160 may be configured to support multiple Radio Access Technologies (RATs). In such embodiments, some components may be duplicated (e.g., separate device-readable media 180 for different RATs) and some components may be reused (e.g., the same antenna 162 may be shared by the RATs). The network node 160 may also include various sets of illustrated components for different wireless technologies (e.g., GSM, WCDMA, LTE, NR, WiFi, or bluetooth wireless technologies) integrated into the network node 160. These wireless technologies may be integrated into the same or different chips or chipsets and other components within network node 160.

The processing circuit 170 is configured to perform any determination, calculation, or similar operations (e.g., certain obtaining operations) described herein as being provided by a network node. These operations performed by processing circuitry 170 may include processing information obtained by processing circuitry 170 by: for example, converting the obtained information into other information, comparing the obtained or converted information with information stored in the network node, and/or performing one or more operations based on the obtained or converted information, and making a determination based on the results of the processing.

The processing circuitry 170 may include a combination of one or more of the following: a microprocessor, controller, microcontroller, central processing unit, digital signal processor, application specific integrated circuit, field programmable gate array, or any other suitable computing device, resource, or combination of hardware, software, and/or encoded logic operable to provide network node 160 functionality, alone or in combination with other network node 160 components (e.g., device readable medium 180). For example, processing circuit 170 may execute instructions stored in device-readable medium 180 or in a memory within processing circuit 170. Such functionality may include providing any of the various wireless features, functions, or benefits discussed herein. In some embodiments, the processing circuit 170 may comprise a system on a chip (SOC).

In some embodiments, the processing circuitry 170 may include one or more of Radio Frequency (RF) transceiver circuitry 172 and baseband processing circuitry 174. In some embodiments, the Radio Frequency (RF) transceiver circuitry 172 and the baseband processing circuitry 174 may be located on separate chips (or chipsets), boards, or units (e.g., radio units and digital units). In alternative embodiments, some or all of the RF transceiver circuitry 172 and the baseband processing circuitry 174 may be on the same chip or chipset, board or unit.

In certain embodiments, some or all of the functionality described herein as being provided by a network node, base station, eNB, or other such network device may be performed by processing circuitry 170, the processing circuitry 170 executing instructions stored on device-readable medium 180 or memory within the processing circuitry 170. In alternative embodiments, some or all of the functionality may be provided by the processing circuitry 170, for example, in a hardwired fashion, without executing instructions stored on a separate or discrete device-readable medium. In any of these embodiments, the processing circuit 170 may be configured to perform the described functions, whether or not executing instructions stored on a device-readable storage medium. The benefits provided by such functionality are not limited to processing circuitry 170 or to other components of network node 160, but rather are enjoyed by network node 160 as a whole and/or by the end user and the wireless network as a whole.

Device-readable medium 180 may include any form of volatile or non-volatile computer-readable memory, including, but not limited to, permanent storage devices, solid-state memory, remote-mounted memory, magnetic media, optical media, random-access memory (RAM), read-only memory (ROM), mass storage media (e.g., a hard disk), removable storage media (e.g., a flash drive, a Compact Disc (CD), or a Digital Video Disc (DVD)), and/or any other volatile or non-volatile, non-transitory device-readable and/or computer-executable memory device that stores information, data, and/or instructions usable by processing circuit 170. Device-readable medium 180 may store any suitable instructions, data, or information, including computer programs, software, applications including one or more of logic, rules, code, tables, and/or the like, and/or other instructions capable of being executed by processing circuitry 170 and used by network node 160. Device-readable medium 180 may be used to store any calculations made by processing circuitry 170 and/or any data received via interface 190. In some embodiments, processing circuit 170 and device-readable medium 180 may be considered integrated.

Interface 190 is used for wired or wireless communication of signaling and/or data between network node 160, network 106, and/or wireless device 110. As shown, the interface 190 includes ports/terminals 194 for transmitting data to and receiving data from the network 106, such as through a wired connection. The interface 190 also includes radio front-end circuitry 192, which may be coupled to the antenna 162 or, in some embodiments, be part of the antenna 162. The radio front-end circuit 192 includes a filter 198 and an amplifier 196. The radio front-end circuitry 192 may be connected to the antenna 162 and the processing circuitry 170. The radio front-end circuitry may be configured to condition signals communicated between the antenna 162 and the processing circuitry 170. The radio front-end circuitry 192 may receive digital data that is to be transmitted out over a wireless connection to other network nodes or wireless devices. The radio front-end circuit 192 may use a combination of filters 198 and/or amplifiers 196 to convert the digital data to a radio signal having suitable channel and bandwidth parameters. The radio signal may then be transmitted through the antenna 162. Similarly, when receiving data, the antenna 162 may collect radio signals, which are then converted to digital data by the radio front-end circuitry 192. The digital data may be passed to processing circuitry 170. In other embodiments, the interface may include different components and/or different combinations of components.

In certain alternative embodiments, the network node 160 may not include separate radio front-end circuitry 192, instead the processing circuitry 170 may include radio front-end circuitry and may be connected to the antenna 162 without the separate radio front-end circuitry 192. Similarly, in some embodiments, all or some of the RF transceiver circuitry 172 may be considered part of the interface 190. In other embodiments, the interface 190 may include one or more ports or terminals 194, radio front-end circuitry 192, and RF transceiver circuitry 172 (as part of a radio unit (not shown)), and the interface 190 may communicate with the baseband processing circuitry 174 (which is part of a digital unit (not shown)).

The antenna 162 may include one or more antennas or antenna arrays configured to transmit and/or receive wireless signals. Antenna 162 may be coupled to radio front-end circuitry 190 and may be any type of antenna capable of wirelessly transmitting and receiving data and/or signals. In some embodiments, antenna 162 may include one or more omni-directional, sector, or patch antennas operable to transmit/receive radio signals between, for example, 2GHz and 66 GHz. An omni-directional antenna may be used to transmit/receive radio signals in any direction, a sector antenna may be used to transmit/receive radio signals to/from devices within a particular area, and a panel antenna may be a line-of-sight antenna used to transmit/receive radio signals in a relatively straight line. In some cases, using more than one antenna may be referred to as MIMO. In some embodiments, antenna 162 may be separate from network node 160 and may be connected to network node 160 through an interface or port.

The antenna 162, the interface 190, and/or the processing circuitry 170 may be configured to perform any receiving operations and/or certain obtaining operations described herein as being performed by a network node. Any information, data, and/or signals may be received from the wireless device, another network node, and/or any other network device. Similarly, the antenna 162, the interface 190, and/or the processing circuitry 170 may be configured to perform any of the transmit operations described herein as being performed by the network node. Any information, data, and/or signals may be transmitted to the wireless device, another network node, and/or any other network device.

The power circuitry 187 may include or be coupled to power management circuitry and configured to provide power to components of the network node 160 to perform the functions described herein. Power supply circuit 187 can receive power from power supply 186. Power supply 186 and/or power supply circuitry 187 can be configured to provide power to the various components of network node 160 in a form suitable for the respective components (e.g., at the voltage and current levels required by each respective component). The power supply 186 may be included in the power supply circuit 187 and/or the network node 160 or external to the power supply circuit 187 and/or the network node 160. For example, the network node 160 may be connected to an external power source (e.g., a power outlet) via an input circuit or interface such as a cable, whereby the external power source provides power to the power circuit 187. As another example, the power supply 186 may include a power source in the form of a battery or battery pack that is connected to or integrated within the power circuit 187. The battery may provide backup power if the external power source fails. Other types of power sources, such as photovoltaic devices, may also be used.

Alternative embodiments of network node 160 may include additional components beyond those shown in fig. 3 that may be responsible for providing certain aspects of the network node's functionality, including any of the functionality described herein and/or any functionality needed to support the subject matter described herein. For example, network node 160 may include user interface devices to allow information to be input into network node 160 and to allow information to be output from network node 160. This may allow a user to perform diagnostic, maintenance, repair, and other administrative functions for network node 160.

As used herein, a wireless device refers to a device capable, configured, arranged and/or operable to wirelessly communicate with a network node and/or other wireless devices. Unless otherwise specified, the term wireless device is used interchangeably herein with User Equipment (UE). Wireless transmission may include sending and/or receiving wireless signals using electromagnetic waves, radio waves, infrared waves, and/or other types of signals suitable for transmitting information over the air. In some embodiments, a wireless device may be configured to transmit and/or receive information without direct human interaction. For example, a wireless device may be designed to: when triggered by an internal or external event, or in response to a request from the network, information is sent to the network according to a predetermined schedule. Examples of wireless devices include, but are not limited to, smart phones, mobile phones, cellular phones, voice over IP (VoIP) phones, wireless local loop phones, desktop computers, Personal Digital Assistants (PDAs), wireless cameras, gaming consoles or devices, music storage devices, playback devices, wearable terminal devices, wireless endpoints, mobile stations, tablet computers, portable embedded devices (LEEs), portable installation equipment (LMEs), smart devices, wireless Customer Premises Equipment (CPE), in-vehicle wireless terminal devices, and so forth. The wireless devices may support device-to-device (D2D) communications, vehicle-to-vehicle (V2V) communications, vehicle-to-infrastructure (V2I) communications, vehicle-to-anything (V2X) communications, for example, by implementing the 3GPP standard for sidelink communications, and may be referred to as D2D communications devices in this case. As yet another particular example, in an internet of things (IoT) scenario, a wireless device may represent a machine or other device that performs monitoring and/or measurements and sends results of such monitoring and/or measurements to another wireless device and/or network node. In this case, the wireless device may be a machine-to-machine (M2M) device, which may be referred to as an MTC device in the 3GPP context. As one particular example, the wireless device may be a UE implementing a 3GPP narrowband internet of things (NB-IoT) standard. Specific examples of such machines or devices are sensors, metering devices (e.g., electricity meters), industrial machines, or household or personal devices (e.g., refrigerators, televisions, etc.), personal wearable devices (e.g., watches, fitness trackers, etc.). In other scenarios, the wireless device may represent a vehicle or other device capable of monitoring and/or reporting its operational status or other functionality associated with its operation. A wireless device as described above may represent an endpoint of a wireless connection, in which case the device may be referred to as a wireless terminal. Furthermore, a wireless device as described above may be mobile, in which case it may also be referred to as a mobile device or mobile terminal.

As shown, wireless device 110 includes an antenna 111, an interface 114, processing circuitry 120, a device readable medium 130, a user interface device 132, an auxiliary device 134, a power supply 136, and power supply circuitry 137. The wireless device 110 may include multiple sets of one or more of the illustrated components for different wireless technologies (e.g., GSM, WCDMA, LTE, NR, WiFi, WiMAX, or bluetooth wireless technologies, to name just a few) supported by the wireless device 110. These wireless technologies may be integrated into the same or different chips or chipsets as other components within wireless device 110.

The antenna 111 may include one or more antennas or antenna arrays configured to transmit and/or receive wireless signals and is connected to the interface 114. In certain alternative embodiments, antenna 111 may be separate from wireless device 110 and may be connected to wireless device 110 through an interface or port. The antenna 111, the interface 114, and/or the processing circuitry 120 may be configured to perform any of the receive or transmit operations described herein as being performed by a wireless device. Any information, data and/or signals may be received from the network node and/or another wireless device. In some embodiments, the radio front-end circuitry and/or the antenna 111 may be considered an interface.

As shown, the interface 114 includes radio front-end circuitry 112 and an antenna 111. The radio front-end circuitry 112 includes one or more filters 118 and an amplifier 116. The radio front-end circuit 114 is connected to the antenna 111 and the processing circuit 120, and is configured to condition signals communicated between the antenna 111 and the processing circuit 120. The radio front-end circuitry 112 may be coupled to the antenna 111 or be part of the antenna 111. In some embodiments, wireless device 110 may not include a separate radio front-end circuit 112; rather, the processing circuitry 120 may include radio front-end circuitry and may be connected to the antenna 111. Similarly, in some embodiments, some or all of the RF transceiver circuitry 122 may be considered part of the interface 114. The radio front-end circuitry 112 may receive digital data that is to be transmitted out over a wireless connection to other network nodes or wireless devices. The radio front-end circuitry 112 may use a combination of filters 118 and/or amplifiers 116 to convert digital data to a radio signal having suitable channel and bandwidth parameters. The radio signal may then be transmitted through the antenna 111. Similarly, when receiving data, the antenna 111 may collect a radio signal, which is then converted into digital data by the radio front-end circuit 112. The digital data may be passed to processing circuitry 120. In other embodiments, the interface may include different components and/or different combinations of components.

The processing circuit 120 may include a combination of one or more of the following: a microprocessor, controller, microcontroller, central processing unit, digital signal processor, application specific integrated circuit, field programmable gate array, or any other suitable computing device, resource, or combination of hardware, software, and/or encoded logic operable to provide wireless device 110 functionality alone or in combination with other wireless device 110 components (e.g., device readable medium 130). Such functionality may include providing any of the various wireless features or benefits discussed herein. For example, the processing circuit 120 may execute instructions stored in the device-readable medium 130 or in a memory within the processing circuit 120 to provide the functionality disclosed herein.

As shown, the processing circuitry 120 includes one or more of RF transceiver circuitry 122, baseband processing circuitry 124, and application processing circuitry 126. In other embodiments, the processing circuitry may include different components and/or different combinations of components. In some embodiments, processing circuitry 120 of wireless device 110 may include a SOC. In some embodiments, the RF transceiver circuitry 122, the baseband processing circuitry 124, and the application processing circuitry 126 may be on separate chips or chipsets. In alternative embodiments, some or all of the baseband processing circuitry 124 and the application processing circuitry 126 may be combined into one chip or chipset, and the RF transceiver circuitry 122 may be on a separate chip or chipset. In yet alternative embodiments, some or all of the RF transceiver circuitry 122 and the baseband processing circuitry 124 may be on the same chip or chipset, and the application processing circuitry 126 may be on a separate chip or chipset. In other alternative embodiments, some or all of the RF transceiver circuitry 122, the baseband processing circuitry 124, and the application processing circuitry 126 may be combined in the same chip or chipset. In some embodiments, the RF transceiver circuitry 122 may be part of the interface 114. RF transceiver circuitry 122 may condition the RF signals for processing circuitry 120.

In certain embodiments, some or all of the functions described herein as being performed by a wireless device may be provided by processing circuitry 120, processing circuitry 120 executing instructions stored on device-readable medium 130, in certain embodiments device-readable medium 130 may be a computer-readable storage medium. In alternative embodiments, some or all of the functionality may be provided by the processing circuit 120, for example, in a hardwired fashion, without executing instructions stored on a separate or discrete device-readable storage medium. In any of these particular embodiments, the processing circuit 120 may be configured to perform the described functions, whether or not executing instructions stored on a device-readable storage medium. The benefits provided by such functionality are not limited to the processing circuitry 120 or to other components of the wireless device 110, but rather are enjoyed by the wireless device 110 as a whole and/or by the end user and the wireless network as a whole.

The processing circuit 120 may be configured to perform any of the determination, calculation, or similar operations (e.g., certain obtaining operations) described herein as being performed by a wireless device. The operations performed by the processing circuit 120 may include processing information obtained by the processing circuit 120 by: for example, converting the obtained information to other information, comparing the obtained or converted information to information stored by wireless device 110, and/or performing one or more operations based on the obtained or converted information and making determinations based on the results of the processing.

The device-readable medium 130 may be operable to store computer programs, software, applications including one or more of logic, rules, code, tables, etc., and/or other instructions that are executable by the processing circuit 120. Device-readable medium 130 may include computer memory (e.g., Random Access Memory (RAM) or Read Only Memory (ROM)), a mass storage medium (e.g., a hard disk), a removable storage medium (e.g., a Compact Disc (CD) or a Digital Video Disc (DVD)), and/or any other volatile or non-volatile, non-transitory device-readable and/or computer-executable memory device that stores information, data, and/or instructions that may be used by processing circuit 120. In some embodiments, the processing circuit 120 and the device-readable medium 130 may be considered integrated.

The user interface device 132 may provide components that allow a human user to interact with the wireless device 110. Such interaction may take many forms, such as visual, audible, tactile, and the like. User interface device 132 is operable to generate output to a user and allow the user to provide input to wireless device 110. The type of interaction may vary depending on the type of user interface device 132 installed in the wireless device 110. For example, if wireless device 110 is a smartphone, the interaction may be via a touchscreen; if wireless device 110 is a smart meter, the interaction may be through a screen that provides usage (e.g., gallons used) or a speaker that provides an audible alert (e.g., if smoke is detected). The user interface device 132 may include input interfaces, devices, and circuits, and output interfaces, devices, and circuits. The user interface device 132 is configured to allow information to be input into the wireless device 110 and is connected to the processing circuitry 120 to allow the processing circuitry 120 to process the input information. The user interface device 132 may include, for example, a microphone, proximity or other sensor, keys/buttons, a touch display, one or more cameras, a USB port, or other input circuitry. The user interface device 132 is also configured to allow information to be output from the wireless device 110 and to allow the processing circuit 120 to output information from the wireless device 110. The user interface device 132 may include, for example, a speaker, a display, a vibration circuit, a USB port, a headphone interface, or other output circuitry. Wireless device 110 may communicate with an end user and/or a wireless network using one or more input and output interfaces, devices, and circuits of user interface device 132 and allow them to benefit from the functionality described herein.

The auxiliary device 134 may be operable to provide more specific functions that may not normally be performed by a wireless device. This may include dedicated sensors for making measurements for various purposes, interfaces for other types of communications such as wired communications, etc. The inclusion and type of components of the auxiliary device 134 may vary depending on the embodiment and/or the scenario.

In some embodiments, the power source 136 may be in the form of a battery or battery pack. Other types of power sources may also be used, such as external power sources (e.g., power outlets), photovoltaic devices, or battery cells. Wireless device 110 may also include power supply circuitry 137 for delivering power from power supply 136 to various portions of wireless device 110 that require power from power supply 136 to perform any of the functions described or indicated herein. In some embodiments, power supply circuit 137 may include a power management circuit. The power supply circuit 137 may additionally or alternatively be operable to receive power from an external power source; in this case, the wireless device 110 may be connected to an external power source (e.g., a power outlet) through an input circuit or an interface such as a power cable. In certain embodiments, power supply circuit 137 is also operable to deliver power from an external power source to power supply 136. This may be used, for example, for charging of the power supply 136. The power supply circuitry 137 may perform any formatting, conversion, or other modification to the power from the power supply 136 to adapt the power to the various components of the powered wireless device 110.

As described above, there are access messages and system information (e.g., RMSI, OSI, paging, RAR (message 2) and message 4, etc.) that need to be sent on the PDSCH before the RRC connection. Existing methods for time domain resource allocation for messages and system information that need to be sent on the PDSCH prior to RRC connection have certain drawbacks. For example, existing approaches may lack flexibility in terms of the time domain resource allocation tables that may be used.

The present disclosure contemplates various embodiments related to a time resource indication mechanism for transmitting and receiving a PDSCH carrying information and/or messages prior to an RRC connection. Although certain embodiments describe the definition and/or signaling of a time domain allocation table for a PDSCH carrying a message prior to an RRC connection, it should be understood that the disclosure is not limited to these example embodiments. For example, various embodiments described herein may also be applicable to scenarios in which wireless device 110 has established an RRC connection (e.g., when wireless device 110 is in an RRC connected mode).

In certain embodiments, the network node 160 may determine time domain resource allocations for one or more PDSCH transmissions (e.g., one or more PDSCH transmissions, such as access messages and system information, including one or more of RMSI, OSI, paging, RAR/MSG2, message 4, and any other suitable PDSCH transmissions). Further, the network node 160 may determine a time domain resource allocation table for one or more PDSCH transmissions.

In certain embodiments, the network node 160 sends an indication of the time domain resource allocation table for one or more PDSCH transmissions to the wireless device 110. The wireless device 110 receives an indication of a time domain resource allocation table for one or more PDSCH transmissions and determines the time domain resource allocation table for the one or more PDSCH transmissions based on the received indication. In some embodiments, wireless device 110 may not be in RRC connected mode. Thus, wireless device 110 may receive the indication before wireless device 110 has established an RRC connection.

In certain embodiments, the indication of the time domain resource allocation table for one or more PDSCH transmissions received by wireless device 110 may be included in a SIB, such as SIB 1. In some cases, the received indication may be a PDSCH time resource allocation parameter. For example, in certain embodiments, the PDSCH time resource allocation parameter may be introduced in the RMSI/SIB1 for the PDSCH message prior to the RRC connection. As an example, in some embodiments, the following parameters may be introduced in PDCCH-ConfigCommon of SIBs and during handover and primary secondary cell (PSCell)/secondary cell (SCell) addition: PDSCH-Allocation List-Common SEQUENCE of PDSCH-TimeDomainResourceAllocation (SIZE (1.. maxNrofDL-Allocations))

In such an implementation, the definition of PDSCH-timedomainresource allocation may be the same as or similar to the definition specified in PDCCH-Config (as described in 3GPP TS 38.331 V15.0.1). Note that the above example parameters are just one possible example of how PDSCH time resource allocation parameters may be introduced in the RMSI/SIB 1. Other implementations are possible. For example, in some embodiments, the parameter PDSCH-timedomainallclositionlist may be introduced in the PDSCH-ConfigCommon cell in SIB 1. In this scenario, the pdsch-timedomainallclositionslist field may be a list of time domain configurations for the timing of downlink allocations for downlink data. This configuration may be applicable to PDCCH scrambled for CORESET #0, 3GPP TS 38.214, the default values in table 5.1.2.1.1-1 apply to this CORESET # 0.

As described above, the various embodiments described herein are not limited to the pre-RRC connection scenario. For example, in certain embodiments, wireless device 110 may receive an indication of a time domain resource allocation table for one or more PDSCH transmissions while in RRC connected mode. In this scenario, the wireless device 110 may use this indication (e.g., the PDSCH time resource allocation parameter PDSCH-timedomainnalocationlist in SIB1) when the wireless device 110 has not received a particular PDSCH-timedomainnalocationlist in dedicated RRC signaling.

In some embodiments, a common default time domain resource allocation table may be defined for all PDSCHs prior to the RRC connection. Thus, in certain embodiments, the time domain resource allocation table for one or more PDSCH transmissions may be a default time domain resource allocation table defined for all PDSCH transmissions prior to the RRC connection.

In certain embodiments, the time domain resource allocation table for one or more PDSCH transmissions may be one of a plurality of time domain resource allocation tables. In some cases, the plurality of time domain resource allocation tables may include a plurality of different default time domain resource allocation tables defined for PDSCH transmission prior to the RRC connection. For example, in some embodiments, two different default time domain resource allocation tables (e.g., table a and table B) may be defined for the PDSCH prior to the RRC connection. One default time domain resource allocation table (e.g., table a) may be configured for PDSCH carrying RMSI, and another time domain resource allocation table (e.g., table B) may be defined for PDSCH carrying a different message than RMSI prior to RRC connection.

In some embodiments, the received indication may comprise one or more bits. For example, one bit may be introduced in the RMSI to indicate which time allocation table is used for the PDSCH carrying messages prior to the RRC connection. In one example implementation, when the bit is set to 0, it indicates that table a is used (i.e., the same table as RMSI is used); otherwise, table B is used.

As described above, in certain embodiments, a default time domain resource allocation table may be configured for the PDSCH carrying RMSI. In some embodiments, in addition to the default time domain resource allocation table for PDSCH carrying RMSI, one or more additional time domain resource allocation tables (e.g., tables B and C) may be defined for PDSCH carrying messages different from RMSI prior to RRC connection. In this scenario, more bits may be introduced in the RMSI to indicate which time domain resource allocation table to use for the PDSCH carrying the message prior to the RRC connection. In some cases, signaling in an RRC signaling overwrite (overwrite) RMSI may be used after an RRC connection.

In some embodiments, the indication received by wireless device 110 may be a CORESET configuration. Thus, in some embodiments, the time domain resource allocation table for non-RMSI PDSCH prior to RRC configuration may depend on the corresponding CORESET configuration. For example, if CORESET is configured in the RMSI, wireless device 110 may use the time domain resource allocation table configured/signaled in the RMSI. However, if CORESET is configured in PBCH, wireless device 110 may use the time domain resource allocation table for RMSI. Note that in some cases, multiple time domain resource allocation tables may be used. In such a scenario, some signaling may be added in the RMSI to provide an indication as to which of the multiple time domain resource allocation tables to use.

In certain embodiments, wireless device 110 may determine a time resource allocation for one or more PDSCH transmissions using the determined time domain resource allocation table. The time domain resource allocation table for one or more PDSCH transmissions may include any suitable information. For example, in certain embodiments, the time domain resource allocation table for one or more PDSCH transmissions may include one or more of: a row index; a DMRS location; a PDSCH mapping type; a slot level offset; a starting OFDM symbol in a slot; a number of allocated OFDM symbols for one or more PDSCH transmissions.

Table 1 below is an example of a time domain resource allocation table that may be used for one or more PDSCH transmissions. More specifically, table 1 is an example of a default PDSCH time domain resource allocation a for a normal Cyclic Prefix (CP). Table 1 below includes PDSCH mapping types. In the example of table 1, the type APDSCH mapping type is a normal slot allocation type, while the type B PDSCH mapping is a micro slot allocation type. The "DMRS-type a-Position" provides the OFDM symbol index of the first DMRS (used to demodulate the PDSCH) OFDM symbol. K₀Is the slot level offset associated with the slot in which CORESET is located. S is the starting OFDM symbol in the slot. L is allocated for PDSCHThe number of OFDM symbols.

TABLE 1

The various embodiments described above may advantageously enable indicating to a wireless device a time domain resource allocation table for a PDSCH carrying a message before or after an RRC connection. This may advantageously allow for the definition of different time domain resource allocation tables, which may advantageously support flexibility and different configurations for PDSCH carrying different messages than RMSI.

Fig. 4 is a flow chart of a method 400 in a wireless device (e.g., UE) according to some embodiments. The method 400 begins at step 401, where a wireless device receives an indication of a time domain resource allocation table for one or more PDSCH transmissions. In some embodiments, the wireless device may not be in RRC connected mode. In certain embodiments, an indication of a time domain resource allocation table for one or more PDSCH transmissions may be received prior to the wireless device establishing the RRC connection.

In certain embodiments, the received indication may be included in a SIB. In certain embodiments, the SIB may be SIB 1. In certain embodiments, the received indication may include a PDSCH time resource allocation parameter. In some embodiments, the received indication may comprise one or more bits.

In some embodiments, the received indication may include a CORESET configuration.

In step 402, the wireless device determines a time domain resource allocation table for one or more PDSCH transmissions based on the received indication. In certain embodiments, the method may further include determining a time resource allocation for one or more PDSCH transmissions using the determined time domain resource allocation table. In certain embodiments, the time domain resource allocation table for one or more PDSCH transmissions may include one or more of: a row index; a DMRS location; a PDSCH mapping type; a slot level offset; a starting OFDM symbol in a slot; a number of allocated OFDM symbols for one or more PDSCH transmissions.

In certain embodiments, a time domain resource allocation table for one or more PDSCH transmissions may be configured in the RMSI, and the method may further comprise: when the CORESET configuration is configured in the RMSI, the time domain resource allocation table configured in the RMSI is determined to be used. In certain embodiments, the time domain resource allocation table for one or more PDSCH transmissions may be a time domain resource allocation table for RMSI, and the method may further comprise: when the CORESET configuration is configured in PBCH, it is determined to use a time domain resource allocation table for RMSI.

In certain embodiments, the time domain resource allocation table for one or more PDSCH transmissions may be one of a plurality of time domain resource allocation tables. In some embodiments, the plurality of time domain resource allocation tables may include a plurality of different default time domain resource allocation tables defined for PDSCH transmission prior to the RRC connection. In certain embodiments, a first time domain resource allocation table of the plurality of time domain resource allocation tables may comprise a default time domain resource allocation table configured for a PDSCH carrying a RMSI, and a second time domain resource allocation table of the plurality of time domain resource allocation tables may comprise a default time domain resource allocation table configured for a PDSCH carrying a different message than the RMSI.

FIG. 5 is a schematic block diagram of a virtualization apparatus according to some embodiments. More specifically, fig. 5 shows a schematic block diagram of an apparatus 500 in a wireless network (e.g., the wireless network shown in fig. 3). The apparatus may be implemented in a wireless device (e.g., wireless device 110 shown in fig. 3). The apparatus 500 is operable to perform the example method described above with reference to fig. 4, as well as possibly any other process or method disclosed herein. It should also be understood that the method of fig. 4 need not be performed solely by the apparatus 500. At least some of the operations of the method may be performed by one or more other entities.

The virtual device 500 may include processing circuitry that may include one or more microprocessors or microcontrollers, as well as other digital hardware, which may include a Digital Signal Processor (DSP), dedicated digital logic, or the like. The processing circuitry may be configured to execute program code stored in memory, which may include one or several types of memory, such as Read Only Memory (ROM), random access memory, cache memory, flash memory devices, optical storage devices, and so forth. In several embodiments, the program code stored in the memory includes program instructions for performing one or more telecommunications and/or data communications protocols, as well as instructions for performing one or more of the techniques described herein. In some implementations, the processing circuitry may be used to cause the receiving unit 502, the determining unit 504 and the communicating unit 506, as well as any other suitable units of the apparatus 500, to perform corresponding functions in accordance with one or more embodiments of the present disclosure.

In certain embodiments, apparatus 500 may be a wireless device (e.g., a UE). As shown in fig. 5, the apparatus 500 includes a receiving unit 502, a determining unit 504, and a communicating unit 506. The receiving unit 502 may be configured to perform a receiving function of the apparatus 500. For example, the receiving unit 502 may be configured to receive an indication of a time domain resource allocation table for one or more PDSCH transmissions (e.g., one or more of RMSI, OSI, paging messages, random access message 2, and random access message 4 transmissions). In certain embodiments, the receiving unit 502 may be configured to receive an indication of a time domain resource allocation table for one or more PDSCH transmissions prior to establishing the RRC connection. In certain embodiments, the receiving unit 502 may be configured to receive an indication of a time domain resource allocation for one or more PDSCH transmissions in a SIB (e.g., SIB1) or configured as CORESET.

The receiving unit 502 may receive any suitable information (e.g., from a wireless device or another network node). The receiving unit 502 may include a receiver and/or a transceiver, such as the RF transceiver circuitry 122 described above with respect to fig. 3. The receiving unit 502 may include circuitry configured to receive messages and/or signals (wireless or wired). In particular embodiments, receiving unit 502 may communicate the received messages and/or signals to determining unit 504 or any other suitable unit of apparatus 500. In some embodiments, the functions of the receiving unit 502 may be performed in one or more different units.

The determination unit 504 may perform processing functions of the apparatus 500. For example, the determining unit 504 may be configured to determine a time domain resource allocation table for one or more PDSCH transmissions based on the received indication. For example, in certain embodiments, the determining unit 504 may be configured to identify a particular time domain allocation table for determining the time resource allocation based on the received information. As another example, in certain embodiments, determining unit 504 may be configured to determine a time resource allocation for one or more PDSCH transmissions using the determined time domain resource allocation table. As yet another example, in some embodiments, a time domain resource allocation table for one or more PDSCH transmissions may be configured in the RMSI, and the determining unit 504 may be configured to determine to use the time domain resource allocation table configured in the RMSI when the CORESET configuration is configured in the RMSI. As yet another example, in certain embodiments, the time domain resource allocation table for one or more PDSCH transmissions may be a time domain resource allocation table for RMSI, and determining unit 504 may be configured to determine to use the time domain resource allocation table for RMSI when the CORESET configuration is configured in PBCH.

The determining unit 402 may include one or more processors (e.g., the processing circuit 120 described above with respect to fig. 3) or may be included in one or more processors (e.g., the processing circuit 120 described above with respect to fig. 3). The determining unit 504 may comprise analog and/or digital circuitry configured to perform any of the functions of the determining unit 504 and/or the processing circuit 120 described above. In some embodiments, the functionality of the determining unit 504 may be performed in one or more different modules.

The communication unit 506 may be configured to perform the transmission functions of the apparatus 500. The communication unit 506 may send the message (e.g., to the wireless device and/or another network node). The communication unit 506 may include a transmitter and/or a transceiver, such as the RF transceiver circuitry 122 described above with respect to fig. 3. The communication unit 506 may include circuitry configured to transmit messages and/or signals (e.g., wirelessly or by wire). In particular embodiments, communication unit 506 may receive messages and/or signals for transmission from determination unit 504 or any other unit of apparatus 500. In some embodiments, the functionality of the communication unit 504 may be performed in one or more different units.

The term unit may have a conventional meaning in the field of electronics, electrical and/or electronic devices and may include, for example, electrical and/or electronic circuitry, devices, modules, processors, memory, logical solid state and/or discrete devices, computer programs or instructions for performing various tasks, processes, calculations, output and/or display functions and the like, such as those described herein.

Fig. 6 is a flow chart of a method 600 in a network node according to some embodiments. The method 600 begins at step 601, where the network node determines a time domain resource allocation table for one or more PDSCH transmissions. In certain embodiments, the one or more PDSCH transmissions may include one or more of the following: RMSI; OSI; a paging message; random access message 2; and a random access message 4.

In step 602, the network node sends to a wireless device (e.g., a UE) an indication of a time domain resource allocation table for one or more PDSCH transmissions. In some embodiments, the wireless device may not be in RRC connected mode. In certain embodiments, the indication of the time domain resource allocation table for one or more PDSCH transmissions may be sent prior to the wireless device establishing the RRC connection. In certain embodiments, the indication of the time domain resource allocation table for one or more PDSCH transmissions may enable the wireless device to determine and/or identify a particular time domain allocation table for determining a time resource allocation for the wireless device.

FIG. 7 is a schematic block diagram of a virtualization apparatus according to some embodiments. More specifically, fig. 7 shows a schematic block diagram of an apparatus 700 in a wireless network (e.g., the wireless network shown in fig. 3). The apparatus may be implemented in a network node (e.g., network node 160 shown in fig. 3). The apparatus 700 is operable to perform the example method described above with reference to fig. 6, as well as possibly any other process or method disclosed herein. It should also be understood that the method of fig. 6 need not be performed solely by the apparatus 700. At least some of the operations of the method may be performed by one or more other entities.

The virtual device 700 may include processing circuitry that may include one or more microprocessors or microcontrollers, as well as other digital hardware, which may include a Digital Signal Processor (DSP), dedicated digital logic, or the like. The processing circuitry may be configured to execute program code stored in memory, which may include one or several types of memory, such as Read Only Memory (ROM), random access memory, cache memory, flash memory devices, optical storage devices, and so forth. In several embodiments, the program code stored in the memory includes program instructions for performing one or more telecommunications and/or data communications protocols, as well as instructions for performing one or more of the techniques described herein. In some implementations, the processing circuitry may be used to cause the receiving unit 702, the determining unit 704 and the communicating unit 706, as well as any other suitable unit of the apparatus 700, to perform corresponding functions in accordance with one or more embodiments of the present disclosure.

In certain embodiments, apparatus 700 may be an eNB or a gNB. As shown in fig. 7, the apparatus 700 includes a receiving unit 702, a determining unit 704, and a communicating unit 706. The receiving unit 702 may be configured to perform receiving functions of the apparatus 700. The receiving unit 702 may receive any suitable information (e.g., from a wireless device or another network node). The receiving unit 702 may include a receiver and/or a transceiver, such as the RF transceiver circuitry 172 described above with respect to fig. 3. The receiving unit 702 may include circuitry configured to receive messages and/or signals (wireless or wired). In particular embodiments, receiving unit 702 may communicate the received messages and/or signals to determining unit 704 or any other suitable unit of apparatus 700. In some embodiments, the functions of the receiving unit 702 may be performed in one or more different units.

The determination unit 704 may perform processing functions of the apparatus 700. For example, the determining unit 704 may be configured to determine a time domain resource allocation table for one or more PDSCH transmissions (e.g., one or more of RMSI, OSI, paging messages, random access message 2, and random access message 4 transmissions). As another example, the determining unit 704 may be configured to determine a time resource allocation for one or more PDSCH transmissions.

The determination unit 704 may include one or more processors (e.g., the processing circuit 170 described above with respect to fig. 3) or may be included in one or more processors (e.g., the processing circuit 170 described above with respect to fig. 3). The determination unit 704 may include analog and/or digital circuitry configured to perform any of the functions of the determination unit 704 and/or the processing circuitry 170 described above. In some embodiments, the functions of the determination unit 704 may be performed in one or more different modules.

The communication unit 706 may be configured to perform transmission functions of the apparatus 700. For example, the communication unit 706 may be configured to transmit an indication of a time domain resource allocation table for one or more PDSCH transmissions to a wireless device (e.g., a UE). In some embodiments, the communication unit 706 may be configured to transmit an indication of a time domain resource allocation for one or more PSCH transmissions prior to the wireless device establishing the RRC connection. In certain embodiments, the communication unit 706 may be configured to transmit an indication of a time domain resource allocation table for one or more PDSCH transmissions in a SIB (e.g., SIB 1). In certain embodiments, the communication unit 706 may be configured to transmit an indication of a time domain resource allocation table for one or more PDSCH transmissions as a CORESET configuration.

As another example, the communication unit 706 may be configured to transmit one or more PDSCH transmissions (e.g., one or more of RMSI, OSI, paging messages, random access message 2, and random access message 4 transmissions).

The communication unit 706 may send the message (e.g., to the wireless device and/or another network node). Communication unit 1006 may include a transmitter and/or transceiver, such as RF transceiver circuitry 172 described above with respect to fig. 3. The communication unit 706 may include circuitry configured to transmit messages and/or signals (e.g., wirelessly or by wire). In particular embodiments, communication unit 706 may receive messages and/or signals for transmission from determination unit 704 or any other unit of apparatus 700. In some embodiments, the functions of the communication unit 704 may be performed in one or more different units.

Fig. 8 illustrates one embodiment of a UE in accordance with certain embodiments. As used herein, a "user device" or "UE" may not necessarily have a "user" in the sense of a human user who owns and/or operates the relevant device. Alternatively, the UE may represent a device (e.g., an intelligent water spray controller) that is intended for sale to or operated by a human user, but may not or may not initially be associated with a particular human user. Alternatively, the UE may represent a device (e.g., a smart meter) that is not intended for sale to or operation by the end user, but may be associated with or operate for the benefit of the user. The UE 800 may be any UE identified by the third generation partnership project (3GPP), including NB-IoT UEs, Machine Type Communication (MTC) UEs, and/or enhanced MTC (emtc) UEs. As shown in fig. 8, UE 800 is an example of a wireless device configured for communication in accordance with one or more communication standards promulgated by the third generation partnership project (3GPP), such as the GSM, UMTS, LTE, and/or 5G standards of 3 GPP. As previously mentioned, the terms wireless device and UE may be used interchangeably. Thus, although fig. 8 is a UE, the components discussed herein are equally applicable to a wireless device, and vice versa.

In fig. 8, the UE 800 includes processing circuitry 801 operatively coupled to an input/output interface 805, a Radio Frequency (RF) interface 809, a network connection interface 811, memory 815 including Random Access Memory (RAM)817, Read Only Memory (ROM)819, and storage medium 821, etc., a communication subsystem 831, a power supply 833, and/or any other component, or any combination thereof. Storage media 821 includes operating system 823, application programs 825, and data 827. In other embodiments, the storage medium 821 may include other similar types of information. Some UEs may use all of the components shown in fig. 8, or only a subset of these components. The level of integration between components may vary from one UE to another. Moreover, some UEs may contain multiple instances of a component, such as multiple processors, memories, transceivers, transmitters, receivers, and so forth.

In fig. 8, processing circuitry 801 may be configured to process computer instructions and data. The processing circuit 801 may be configured to implement any sequential state machine operable to execute machine instructions stored as a machine-readable computer program in memory, such as: one or more hardware-implemented state machines (e.g., implemented in discrete logic, FPGA, ASIC, etc.); programmable logic along with appropriate firmware; one or more stored programs, a general-purpose processor (e.g., a microprocessor or Digital Signal Processor (DSP)), along with suitable software; or any combination of the above. For example, the processing circuit 801 may include two Central Processing Units (CPUs). The data may be information in a form suitable for use by a computer.

In the depicted embodiment, the input/output interface 805 may be configured to provide a communication interface to an input device, an output device, or both. The UE 800 may be configured to use an output device via the input/output interface 805. The output device may use the same type of interface port as the input device. For example, USB ports may be used to provide input to UE 800 and output from UE 800. The output device may be a speaker, a sound card, a video card, a display, a monitor, a printer, an actuator, a transmitter, a smart card, another output device, or any combination thereof. The UE 800 may be configured to use an input device via the input/output interface 805 to allow a user to capture information into the UE 800. Input devices may include touch-sensitive or presence-sensitive displays, cameras (e.g., digital cameras, digital video cameras, web cameras, etc.), microphones, sensors, mice, trackballs, directional pads, touch pads, scroll wheels, smart cards, and so forth. Presence-sensitive displays may include capacitive or resistive touch sensors to sense input from a user. The sensor may be, for example, an accelerometer, a gyroscope, a tilt sensor, a force sensor, a magnetometer, an optical sensor, a proximity sensor, another similar sensor, or any combination thereof. For example, the input devices may be accelerometers, magnetometers, digital cameras, microphones, and optical sensors.

In fig. 8, RF interface 809 may be configured to provide a communication interface to RF components such as transmitters, receivers, and antennas. The network connection interface 811 can be configured to provide a communication interface to the network 843 a. The network 843a may include a wired and/or wireless network, such as a Local Area Network (LAN), a Wide Area Network (WAN), a computer network, a wireless network, a telecommunications network, another similar network, or any combination thereof. For example, the network 843a may include a Wi-Fi network. The network connection interface 811 may be configured to include a receiver and transmitter interface for communicating with one or more other devices over a communication network according to one or more communication protocols (e.g., ethernet, TCP/IP, SONET, ATM, etc.). The network connection interface 811 may implement receiver and transmitter functionality appropriate for a communication network link (e.g., optical, electrical, etc.). The transmitter and receiver functions may share circuit components, software or firmware, or alternatively may be implemented separately.

RAM 817 may be configured to interface with the processing circuitry 801 via the bus 802 to provide storage or caching of data or computer instructions during execution of software programs such as operating systems, application programs, and device drivers. The ROM 819 may be configured to provide computer instructions or data to the processing circuit 801. For example, the ROM 819 may be configured to store non-low level system code or data for basic system functions stored in non-volatile memory, such as basic input and output (I/O), boot-up, or receipt of keystrokes from a keyboard. The storage medium 821 may be configured to include memory, such as RAM, ROM, Programmable Read Only Memory (PROM), Erasable Programmable Read Only Memory (EPROM), Electrically Erasable Programmable Read Only Memory (EEPROM), a magnetic disk, an optical disk, a floppy disk, a hard disk, a removable cartridge, or a flash drive. In one example, the storage medium 821 may be configured to include an operating system 823, an application program 825 such as a web browser application, a widget or gadget engine or another application, and a data file 827. The storage medium 821 may store any one of, or a combination of, various operating systems for use by the UE 800.

The storage medium 821 may be configured to include a plurality of physical drive units, such as a Redundant Array of Independent Disks (RAID), a floppy disk drive, a flash memory, a USB flash drive, an external hard disk drive, a thumb disk drive, a pen drive, a key disk drive, a high-density digital versatile disk (HD-DVD) optical disk drive, an internal hard disk drive, a blu-ray disk drive, a Holographic Digital Data Storage (HDDS) optical disk drive, an external mini-dual in-line memory module (DIMM), Synchronous Dynamic Random Access Memory (SDRAM), an external micro DIMM SDRAM, a smart card memory such as a subscriber identity module or a removable subscriber identity (SIM/RUIM) module, other memory, or any combination thereof. The storage medium 821 may allow the UE 800 to access computer-executable instructions, applications, etc., stored on a transitory or non-transitory memory medium to offload data or upload data. An article of manufacture, such as one utilizing a communication system, may be tangibly embodied in storage medium 821, and storage medium 221 may comprise a device-readable medium.

In fig. 8, the processing circuit 801 may be configured to communicate with a network 843b using a communication subsystem 831. Network 843a and network 843b may be one or more of the same network or one or more different networks. The communication subsystem 831 may be configured to include one or more transceivers for communicating with the network 843 b. For example, the communication subsystem 831 may be configured to include one or more transceivers for communicating with one or more remote transceivers of a base station of another device (e.g., another wireless device, a UE) or a Radio Access Network (RAN) capable of wireless communication in accordance with one or more communication protocols (e.g., IEEE802.11, CDMA, WCDMA, GSM, LTE, UTRAN, WiMax, etc.). Each transceiver may include a transmitter 833 and/or a receiver 835 to implement transmitter or receiver functions (e.g., frequency allocation, etc.) appropriate for the RAN link, respectively. Further, the transmitter 833 and receiver 835 for each transceiver may share circuit components, software, or firmware, or alternatively may be implemented separately.

In the illustrated embodiment, the communication functions of the communication subsystem 831 may include data communication, voice communication, multimedia communication, short-range communication such as bluetooth, near field communication, location-based communication such as the use of the Global Positioning System (GPS) for determining location, another similar communication function, or any combination thereof. For example, the communication subsystem 831 may include cellular communication, Wi-Fi communication, Bluetooth communication, and GPS communication. The network 843b may include a wired and/or wireless network, such as a Local Area Network (LAN), a Wide Area Network (WAN), a computer network, a wireless network, a telecommunications network, another similar network, or any combination thereof. For example, the network 843b may be a cellular network, a Wi-Fi network, and/or a near-field network. The power supply 813 may be configured to provide Alternating Current (AC) or Direct Current (DC) power to the components of the UE 800.

The features, benefits, and/or functions described herein may be implemented in one of the components of the UE 800 or divided among multiple components of the UE 800. Furthermore, the features, benefits and/or functions described herein may be implemented in any combination of hardware, software or firmware. In one example, communication subsystem 831 may be configured to include any of the components described herein. Further, the processing circuit 801 may be configured to communicate with any such components over the bus 802. In another example, any such components may be represented by program instructions stored in memory that, when executed by the processing circuitry 801, perform the corresponding functions described herein. In another example, the functionality of any such components may be divided between the processing circuitry 801 and the communication subsystem 831. In another example, the non-compute intensive functionality of any such component may be implemented in software or firmware, and the compute intensive functionality may be implemented in hardware.

FIG. 9 is a schematic block diagram illustrating a virtualized environment in accordance with certain embodiments. More specifically, FIG. 9 is a schematic block diagram illustrating a virtualization environment 900 in which functions implemented by some embodiments may be virtualized. In this context, virtualization means creating a virtual version of an apparatus or device, which may include virtualizing hardware platforms, storage devices, and network resources. As used herein, virtualization may apply to a node (e.g., a virtualized base station or a virtualized radio access node) or a device (e.g., a UE, a wireless device, or any other type of communication device) or component thereof, and relates to an implementation in which at least a portion of functionality is implemented as one or more virtual components (e.g., by one or more applications, components, functions, virtual machines, or containers executing on one or more physical processing nodes in one or more networks).

In some embodiments, some or all of the functions described herein may be implemented as virtual components executed by one or more virtual machines implemented in one or more virtual environments 900 hosted by one or more hardware nodes 930. Furthermore, in embodiments where the virtual node is not a radio access node or does not require a radio connection (e.g. a core network node), the network node may be fully virtualized at this time.

These functions may be implemented by one or more applications 920 (which may alternatively be referred to as software instances, virtual devices, network functions, virtual nodes, virtual network functions, etc.), one or more applications 920 being operable to implement some features, functions, and/or benefits of some embodiments disclosed herein. Application 920 runs in virtualized environment 900, and virtualized environment 900 provides hardware 930 that includes processing circuitry 960 and memory 990. Memory 990 includes instructions 995 that are executable by processing circuit 960 whereby application 920 is operable to provide one or more of the features, benefits and/or functions disclosed herein.

Virtualization environment 900 includes a general or special purpose network hardware device 930 that includes a set of one or more processors or processing circuits 960, which may be commercial off-the-shelf (COTS) processors, Application Specific Integrated Circuits (ASICs), or any other type of processing circuit that includes digital or analog hardware components or special purpose processors. Each hardware device may include memory 990-1, which may be non-permanent memory for temporarily storing instructions 995 or software for execution by the processing circuit 960. Each hardware device may include one or more Network Interface Controllers (NICs) 970, also referred to as network interface cards, which include a physical network interface 980. Each hardware device may also include a non-transitory, non-transitory machine-readable storage medium 990-2 having stored therein software 995 and/or instructions executable by the processing circuit 960. Software 995 may include any type of software, including software for instantiating one or more virtualization layers 950 (also referred to as a hypervisor), software for executing virtual machine 940, and software that allows it to perform the functions, features, and/or benefits described in relation to some embodiments described herein.

Virtual machine 940 includes virtual processes, virtual memory, virtual networking or interfaces, and virtual storage, and may be run by a corresponding virtualization layer 950 or hypervisor. Different embodiments of instances of virtual device 920 can be implemented on one or more of virtual machines 940 and the implementation can be made in different ways.

During operation, the processing circuit 960 executes software 995 to instantiate a hypervisor or virtualization layer 950, which may sometimes be referred to as a Virtual Machine Monitor (VMM). Virtualization layer 950 may present a virtual operating platform that appears to virtual machine 940 as networking hardware.

As shown in fig. 9, hardware 930 may be a stand-alone network node with general or specific components. The hardware 930 may include an antenna 9225 and some functions may be implemented through virtualization. Alternatively, hardware 930 may be part of a larger hardware cluster (e.g., in a data center or Customer Premise Equipment (CPE)), where many hardware nodes work together and are managed through management and coordination (MANO)9100, MANO 9100 oversees lifecycle management of applications 920, and so on.

In some contexts, virtualization of hardware is referred to as Network Function Virtualization (NFV). NFV may be used to unify numerous network equipment types onto industry standard high capacity server hardware, physical switches, and physical storage that may be located in data centers and customer premises equipment.

In the context of NFV, virtual machines 940 may be software implementations of physical machines that run programs as if they were executing on physical, non-virtualized machines. Each virtual machine 940 and the portion of hardware 930 that executes the virtual machine (which may be hardware dedicated to the virtual machine and/or hardware shared by the virtual machine with other virtual machines in virtual machine 940) form a separate Virtual Network Element (VNE).

Still in the context of NFV, a Virtual Network Function (VNF) is responsible for handling specific network functions running in one or more virtual machines 940 above the hardware network infrastructure 930, and corresponds to the application 920 in fig. 9.

In some embodiments, one or more radio units 9200, each including one or more transmitters 9220 and one or more receivers 9210, may be coupled to one or more antennas 9225. The radio unit 9200 may communicate directly with the hardware node 930 via one or more suitable network interfaces, and may be used in conjunction with virtual components to provide a virtual node with radio capabilities, such as a radio access node or base station.

In some embodiments, some signaling may be implemented using control system 9230, and control system 9230 may instead be used for communication between hardware node 930 and radio 9200.

Any suitable steps, methods, features, functions or benefits disclosed herein may be performed by one or more functional units or modules of one or more virtual devices. Each virtual device may include a plurality of these functional units. These functional units may be implemented by processing circuitry that may include one or more microprocessors or microcontrollers, as well as other digital hardware, which may include Digital Signal Processors (DSPs), dedicated digital logic, and the like. The processing circuitry may be configured to execute program code stored in memory, which may include one or several types of memory, such as Read Only Memory (ROM), Random Access Memory (RAM), cache memory, flash memory devices, optical storage devices, and so forth. Program code stored in the memory includes program instructions for executing one or more telecommunications and/or data communications protocols, as well as instructions for performing one or more of the techniques described herein. In some implementations, the processing circuitry may be operative to cause the respective functional units to perform corresponding functions in accordance with one or more embodiments of the present disclosure.

Modifications, additions, or omissions may be made to the systems and devices described herein without departing from the scope of the disclosure. The components of the system and apparatus may be integrated and separated. Further, the operations of the systems and apparatus may be performed by more, fewer, or other components. Further, the operations of the systems and apparatus may be performed using any suitable logic comprising software, hardware, and/or other logic. As used herein, "each" refers to each member of a set or each member of a subset of a set.

Modifications, additions, or omissions may be made to the methods described herein without departing from the scope of the disclosure. The method may include more, fewer, or other steps. Further, the steps may be performed in any suitable order.

Although the present disclosure has been described with reference to particular embodiments, alterations and permutations of the embodiments will be apparent to those skilled in the art. Therefore, the above description of embodiments does not limit the present disclosure. Other changes, substitutions, and alterations are also possible without departing from the spirit and scope of this disclosure, as defined by the following claims.

At least some of the following abbreviations may be used in the present disclosure. If there is an inconsistency between abbreviations, it should be prioritized how it is used above. If listed multiple times below, the first listing should be prioritized over any subsequent listing.

1x RTT CDMA20001x radio transmission technology

3GPP third generation partnership project

5G fifth generation

ABS almost blank subframe

ARQ automatic repeat request

AWGN additive white Gaussian noise

BCCH broadcast control channel

BCH broadcast channel

CA carrier aggregation

CC carrier component

CCCH common control channel

CDMA code division multiple access

CGI cell global identifier

CIR channel impulse response

CORESET control resource set

CP Cyclic Prefix

CPICH common pilot channel

CPICH Ec/No received energy per chip CPICH divided by the power density in the band

CQI channel quality information

C-RNTI cell RNTI

CSI channel state information

Control channel special for DCCH

DCI downlink control information

DL downlink

DM demodulation

DMRS demodulation reference signals

DRX discontinuous reception

DTX discontinuous transmission

DTCH dedicated traffic channel

DUT device under test

E-CID enhanced cell ID (positioning method)

E-SMLC evolution service mobile location center

CGI for ECGI evolution

eNB E-UTRAN node B

EPDCCH enhanced physical downlink control channel

E-SMLC evolution service mobile location center

E-UTRA evolved UTRA

UTRAN for E-UTRAN evolution

FDD frequency division duplex

FDM frequency division multiplexing

FFS is to be further studied

GERN GSM EDGE radio access network

Base station in gNB NR

GNSS global navigation satellite system

The GSM global system for mobile communications system (GSM),

HARQ hybrid automatic repeat request

HO handover

HSPA high speed packet access

HRPD high rate packet data

LOS visual range

LPP LTE positioning protocol

LTE Long term evolution

MAC medium access control

MBMS multimedia broadcast multicast service

MBSFN multimedia broadcast multicast service single frequency network

MBSFN ABS MBSFN almost blank subframes

MDT drive test minimization

MIB Master information Block

MME mobility management entity

MSC mobile switching center

PDCCH narrowband physical downlink control channel

NR new radio

OCNG OFDMA channel noise generator

OFDM orthogonal frequency division multiplexing

OFDMA orthogonal frequency division multiple access

OS OFDM symbol

OSI other system information

OSS operation support system

OTDOA observed time difference of arrival

O & M operation and maintenance

PBCH physical broadcast channel

P-CCPCH primary common control physical channel

PCell primary cell

PCFICH physical control Format indicator channel

PDCCH physical downlink control channel

PDP distribution delay profile

PDSCH physical downlink shared channel

PGW packet gateway

PHICH physical hybrid ARQ indicator channel

PLMN public land mobile network

PMI precoder matrix indicator

Physical Random Access Channel (PRACH)

PRS positioning reference signal

PSCell main and auxiliary cell

PSS primary synchronization signal

PUCCH physical uplink control channel

PUSCH physical uplink shared channel

PACH random access channel

QAM quadrature amplitude modulation

RAN radio access network

RAR random access response

RAT radio access technology

RLM radio link management

RMSI minimum system information remaining

RNC radio network controller

RNTI radio network temporary identifier

RRC radio resource control

RRM radio resource management

RS reference signal

RSCP received signal code power

RSRP reference symbol received power or

Reference signal received power

RSRQ reference signal received quality or

Reference symbol reception quality

RSSI received signal strength indicator

RSTD reference signal time difference

RV redundancy version

SCH synchronous channel

Scell secondary cell

SCS subcarrier spacing

SDU service data unit

SFI slot format indication

SFN system frame number

SGW service gateway

SI system information

SIB system information block

SIBI system information block type 1

SNR signal-to-noise ratio

SON self-optimizing network

SS synchronization signal

SSB synchronization signal block or SS/PBCH block

SS/PBCH synchronization signal and PBCH (DMRS including PBCH)

SSS auxiliary synchronization signal

TDD time division duplex

TDOA time difference of arrival

TOA time of arrival

TSS three-level synchronization signal

TTI Transmission time Interval

UE user equipment

UL uplink

UMTS universal mobile telecommunications system

Universal Subscriber Identity Module (USIM)

UTDOA uplink time difference of arrival

UTRA universal terrestrial radio access

UTRAN Universal terrestrial radio access network

WCDMA Wide CDMA

WLAN wide local area networks.

Claims

1. A method performed by a user equipment, UE, (110, 500, 800) comprising:

receiving (401), at the UE (110, 500, 800), an indication of a time domain resource allocation table for one or more physical downlink shared channel, PDSCH, transmissions; and

determining (402) a time domain resource allocation table for the one or more PDSCH transmissions based on the received indication.

2. The method of claim 1, wherein the UE (110, 500, 800) is not in a radio resource control, RRC, connected mode.

3. The method according to any of claims 1 to 2, wherein the received indication is comprised in a system information block, SIB.

4. The method of claim 3, in which the SIB is a system information Block type 1 SIB 1.

5. The method of any of claims 1 to 4, wherein the received indication comprises a PDSCH time resource allocation parameter.

6. The method of any of claims 1-4, wherein the received indication comprises one or more bits.

7. The method of any of claims 1-2, wherein the received indication comprises a control resource set, CORESET, configuration.

8. The method of claim 7, wherein:

a time domain resource allocation table for the one or more PDSCH transmissions is configured in Remaining Minimum System Information (RMSI); and

the method further comprises the following steps: when the CORESET configuration is configured in the RMSI, determining to use a time domain resource allocation table configured in the RMSI.

9. The method of claim 7, wherein:

the time domain resource allocation table for the one or more PDSCH transmissions is a time domain resource allocation table for Remaining Minimum System Information (RMSI); and

the method further comprises the following steps: determining to use a time domain resource allocation table for RMSI when the CORESET configuration is configured in a physical broadcast channel PBCH.

10. The method of any of claims 1-9, wherein the time domain resource allocation table for the one or more PDSCH transmissions is a default time domain resource allocation table defined for all PDSCH transmissions prior to an RRC connection.

11. The method of any of claims 1-10, wherein the time domain resource allocation table for the one or more PDSCH transmissions is one of a plurality of time domain resource allocation tables.

12. The method of claim 11, wherein the plurality of time domain resource allocation tables comprises a plurality of different default time domain resource allocation tables defined for PDSCH transmission prior to an RRC connection.

13. The method of claim 12, wherein:

a first time domain resource allocation table of the plurality of time domain resource allocation tables comprises a default time domain resource allocation table configured for a PDSCH carrying Remaining Minimum System Information (RMSI); and

a second time domain resource allocation table of the plurality of time domain resource allocation tables comprises a default time domain resource allocation table configured for a PDSCH carrying a different message than the RMSI.

14. The method of any of claims 1-13, wherein the one or more PDSCH transmissions comprise one or more of:

remaining minimum system information RMSI;

other system information OSI;

a paging message;

random access message 2; and

random access message 4.

15. The method of any of claims 1 to 14, further comprising: determining a time resource allocation for the one or more PDSCH transmissions using the determined time domain resource allocation table.

16. The method of any of claims 1-15, wherein a time domain resource allocation table for the one or more PDSCH transmissions comprises one or more of:

a row index;

demodulating a reference signal position;

a PDSCH mapping type;

a slot level offset;

a starting orthogonal frequency division multiplexing, OFDM, symbol in a time slot; and

a number of OFDM symbols allocated for the one or more PDSCH transmissions.

17. A method performed by a network node (160, 700), comprising:

determining (601) a time domain resource allocation table for one or more physical downlink shared channel, PDSCH, transmissions; and

transmitting (602), to a user equipment, UE, (110, 500, 800) an indication of a time domain resource allocation table for the one or more PDSCH transmissions.

18. The method of claim 17, wherein the UE (110, 500, 800) is not in a radio resource control, RRC, connected mode.

19. The method of any of claims 17 to 18, wherein the indication is included in a system information block, SIB.

20. The method of claim 19, wherein the SIB is a system information block type 1 SIB 1.

21. The method of any of claims 17 to 20, wherein the indication comprises a PDSCH time resource allocation parameter.

22. The method of any of claims 17-20, wherein the indication comprises one or more bits.

23. The method of any of claims 17 to 18, wherein the indication comprises a control resource set, CORESET, configuration.

24. The method of claim 23, wherein:

when the CORESET configuration is configured in RMSI, the indication instructs the UE (110, 500, 800) to use a time domain resource allocation table configured in RMSI.

25. The method of claim 23, wherein:

the indication instructs the UE (110, 500, 800) to use a time domain resource allocation table for RMSI when the CORESET configuration is configured in a physical broadcast channel, PBCH.

26. The method of any of claims 17-25, wherein the time domain resource allocation table for the one or more PDSCH transmissions is a default time domain resource allocation table defined for all PDSCH transmissions prior to an RRC connection.

27. The method of any of claims 17-26, wherein the time domain resource allocation table for the one or more PDSCH transmissions is one of a plurality of time domain resource allocation tables.

28. The method of claim 27, wherein the plurality of time domain resource allocation tables comprises a plurality of different default time domain resource allocation tables defined for PDSCH transmission prior to an RRC connection.

29. The method of claim 28, wherein:

30. The method of any of claims 17-29, wherein the one or more PDSCH transmissions comprise one or more of:

remaining minimum system information RMSI;

other system information OSI;

a paging message;

random access message 2; and

random access message 4.

31. The method of any of claims 17 to 30, further comprising: determining a time resource allocation for the one or more PDSCH transmissions.

32. The method of any of claims 17-31, wherein a time domain resource allocation table for the one or more PDSCH transmissions comprises one or more of:

a row index;

demodulating a reference signal position;

a PDSCH mapping type;

a slot level offset;

a number of OFDM symbols allocated for the one or more PDSCH transmissions.

33. A user equipment, UE, (110, 500, 800), comprising:

a receiver (122);

a transmitter (122); and

a processing circuit (120) coupled to the receiver and the transmitter, the processing circuit configured to:

34. The UE of claim 33, wherein the UE (110, 500, 800) is not in a radio resource control, RRC, connected mode.

35. The UE of any of claims 33 to 34, wherein the indication is included in a system information block, SIB.

36. The UE of claim 35, wherein the SIB is a system information block type 1 SIB 1.

37. The UE of any of claims 33 to 36, wherein the indication comprises a PDSCH time resource allocation parameter.

38. The UE of any of claims 33 to 36, wherein the indication comprises one or more bits.

39. The UE of any of claims 33 to 34, wherein the indication comprises a control resource set, CORESET, configuration.

40. The UE of claim 39, wherein:

the processing circuit is further configured to: when the CORESET configuration is configured in the RMSI, determining to use a time domain resource allocation table configured in the RMSI.

41. The UE of claim 39, wherein:

the processing circuit is further configured to: determining to use a time domain resource allocation table for RMSI when the CORESET configuration is configured in a physical broadcast channel PBCH.

42. The UE of any of claims 33 to 41, wherein the time domain resource allocation table for the one or more PDSCH transmissions is a default time domain resource allocation table defined for all PDSCH transmissions prior to the RRC connection.

43. The UE of any of claims 33 to 42, wherein the time domain resource allocation table for the one or more PDSCH transmissions is one of a plurality of time domain resource allocation tables.

44. The UE of claim 43, wherein the plurality of time domain resource allocation tables comprises a plurality of different default time domain resource allocation tables defined for PDSCH transmissions prior to an RRC connection.

45. The UE of claim 44, wherein:

46. The UE of any of claims 33 to 45, wherein the one or more PDSCH transmissions comprise one or more of:

remaining minimum system information RMSI;

other system information OSI;

a paging message;

random access message 2; and

random access message 4.

47. The UE of any of claims 33 to 46, wherein the processing circuitry is further configured to: determining a time resource allocation for the one or more PDSCH transmissions using the determined time domain resource allocation table.

48. The UE of any of claims 33 to 47, wherein a time domain resource allocation table for the one or more PDSCH transmissions comprises one or more of:

a row index;

demodulating a reference signal position;

a PDSCH mapping type;

a slot level offset;

a number of OFDM symbols allocated for the one or more PDSCH transmissions.

49. A network node (160, 700) comprising:

a receiver (172);

a transmitter (172); and

processing circuitry (170) coupled to the receiver and the transmitter, the processing circuitry configured to:

50. The network node of claim 49, wherein the UE (110, 500, 800) is not in a radio resource control, RRC, connected mode.

51. The network node of any of claims 49-50, wherein the indication is included in a System Information Block (SIB).

52. The network node of claim 51, wherein the SIB is a system information block type 1 SIB 1.

53. The network node of any of claims 49-52, wherein the indication comprises a PDSCH time resource allocation parameter.

54. The network node of any of claims 49-52, wherein the indication comprises one or more bits.

55. The network node of any one of claims 49-50, wherein the indication comprises a control resource set (CORESET) configuration.

56. The network node of claim 55, wherein:

57. The network node of claim 55, wherein:

58. The network node of any of claims 49-57, wherein the time domain resource allocation table for the one or more PDSCH transmissions is a default time domain resource allocation table defined for all PDSCH transmissions prior to the RRC connection.

59. The network node of any of claims 49-58, wherein the time domain resource allocation table for the one or more PDSCH transmissions is one of a plurality of time domain resource allocation tables.

60. The network node of claim 59, wherein the plurality of time domain resource allocation tables comprises a plurality of different default time domain resource allocation tables defined for PDSCH transmissions prior to an RRC connection.

61. The network node of claim 60, wherein:

62. The network node of any of claims 49-61, wherein the one or more PDSCH transmissions comprise one or more of:

remaining minimum system information RMSI;

other system information OSI;

a paging message;

random access message 2; and

random access message 4.

63. The network node of any of claims 49-62, wherein the processing circuitry is further configured to determine a time resource allocation for the one or more PDSCH transmissions.

64. The network node of any of claims 49-63, wherein a time domain resource allocation table for the one or more PDSCH transmissions comprises one or more of:

a row index;

demodulating a reference signal position;

a PDSCH mapping type;

a slot level offset;

a number of OFDM symbols allocated for the one or more PDSCH transmissions.