WO2020005133A1

WO2020005133A1 - Method of generating ss-ocng in a radio node

Info

Publication number: WO2020005133A1
Application number: PCT/SE2019/050490
Authority: WO
Inventors: Muhammad Kazmi; Joakim Axmon; Kazuyoshi Uesaka; Christopher Callender
Original assignee: Telefonaktiebolaget Lm Ericsson (Publ)
Priority date: 2018-06-25
Filing date: 2019-05-27
Publication date: 2020-01-02

Abstract

Embodiments include methods for generating signals usable for testing operation of a user equipment (UE) within a cell of a wireless communication network. Embodiments include determining a first set of time-frequency resources usable for transmitting a common signal directed to all UEs operating in the cell and, based on the first set, determining a third set of time-frequency resources usable for transmitting a third set of signals directed to the UE. Embodiments also include, based on the first and the third sets, determining a second set of time-frequency resources usable for transmitting a second set of signals (e.g., OFDM channel noise) directed to virtual UE(s). The first, second, and third sets are within the frequency bandwidth of the cell. Embodiments also include transmitting the common signal, the second set of signals, and the third set of signals using the determined first, second, and third sets of time-frequency resources.

Description

METHOD OF GENERATING SS-OCNG IN A RADIO NODE

TECHNICAL FIELD

The present application relates generally to the field of wireless communication devices and networks, and more specifically to techniques for controlled testing of device functionality based on generating conditions typically found in networks loaded with many devices.

BACKGROUND

Generally, all terms used herein are to be interpreted according to their ordinary meaning in the relevant technical field, unless a different meaning is clearly given and/or is implied from the context in which it is used. All references to a/an/the element, apparatus, component, means, operation, etc. are to be interpreted openly as referring to at least one instance of the element, apparatus, component, means, operation, etc., unless explicitly stated otherwise. The operations of any methods disclosed herein do not have to be performed in the exact order disclosed, unless an operation is explicitly described as following or preceding another operation and/or where it is implicit that a operation must follow or precede another operation. Any feature of any of the embodiments disclosed herein may be applied to any other embodiment, wherever appropriate. Likewise, any advantage of any of the embodiments may apply to any other embodiments, and vice versa. Other objectives, features, and advantages of the enclosed embodiments will be apparent from the following description.

Mobile data traffic is growing exponentially due to the enormous success of smart phones, tablets and other data traffic appliances. The traditional way for increasing the data rate had been to increase the transmission bandwidth. However, the spectrum has become scarce due to the increase in wireless access systems and hence the main challenge for the future wireless access systems is to find alternative solutions to meet high demands on the data rate. One way of handling the increased wireless data traffic is to deploy more base stations (BS) and densify the cellular network. This would however increase interference and deployment cost. Another option for increasing the system capacity is to introduce large antenna arrays ( e.g ., arrays of antenna elements) at the BS. Using these arrays, the BS can create multiple coverage beams - sometimes referred to as“beamforming” - with each beam targeted to a particular user or subset of users within the BS’s entire coverage area. In this manner, the BS can spatially multiplex more users within a given frequency bandwidth in the coverage area, thereby increasing system capacity. This technique is often referred to as very large (VL) multi-user (MU) multiple-input-multiple-output (MIMO), and is abbreviated by VL-MIMO hereinafter.

Such beamforming and spatial multiplexing techniques can be utilized in Long-Term Evolution (LTE) cellular networks. LTE is an umbrella term for so-called fourth- generation (4G) radio access technologies developed within the Third- Generation Partnership Project (3GPP) and initially standardized in Releases 8 and 9, also known as Evolved UTRAN (E- UTRAN). LTE is targeted at various licensed frequency bands and is accompanied by improvements to non-radio aspects commonly referred to as System Architecture Evolution (SAE), which includes Evolved Packet Core (EPC) network. LTE continues to evolve through subsequent releases that are developed according to standards-setting processes with 3GPP and its working groups (WGs), including the Radio Access Network (RAN) WG, and sub-working groups (e.g., RAN1, RAN2, etc.).

LTE Release 10 (Rel-lO) supports bandwidths larger than 20 MHz. One important requirement on Rel-lO is to assure backward compatibility with LTE Release-8. This should also include spectrum compatibility. As such, a wideband LTE Rel-lO carrier (e.g., wider than 20 MHz) should appear as a number of carriers to an LTE Rel-8 (“legacy”) terminal. Each such carrier can be referred to as a Component Carrier (CC). For an efficient use of a wide carrier also for legacy terminals, legacy terminals can be scheduled in all parts of the wideband LTE Rel-lO carrier. One exemplary way to achieve this is by means of Carrier Aggregation (CA), whereby a Rel-lO terminal can receive multiple CCs, each preferably having the same structure as a Rel-8 carrier. Similarly, one of the enhancements in LTE Rel-l 1 is an enhanced Physical Downlink Control Channel (ePDCCH), which has the goals of increasing capacity and improving spatial reuse of control channel resources, improving inter-cell interference coordination (ICIC), and supporting antenna beamforming and/or transmit diversity for control channel.

An overall exemplary architecture of a network comprising LTE and SAE is shown in Figure 1. E-UTRAN 100 comprises one or more evolved Node B’s (network node), such as network nodes 105, 110, and 115, and one or more user equipment (UE), such as UE 120. As used within the 3GPP standards,“user equipment” or“UE” means any wireless communication device (e.g., smartphone or computing device) that is capable of communicating with 3GPP- standard-compliant network equipment, including E-UTRAN as well as UTRAN and/or GERAN, as the third- (“3G”) and second-generation (“2G”) 3GPP radio access networks are commonly known.

As specified by 3GPP, E-UTRAN 100 is responsible for all radio-related functions in the network, including radio bearer control, radio admission control, radio mobility control, scheduling, and dynamic allocation of resources to UEs in uplink and downlink, as well as security of the communications with the UE. These functions reside in the network nodes, such as network nodes 105, 110, and 115. The network nodes in the E-UTRAN communicate with each other via the XI interface, as shown in Figure 1. The network nodes also are responsible for the E-UTRAN interface to the EPC, specifically the S l interface to the Mobility Management Entity (MME) and the Serving Gateway (SGW), shown collectively as MME/S- GWs 134 and 138 in Figure 1. Generally speaking, the MME/S-GW handles both the overall control of the UE and data flow between the UE and the rest of the EPC. More specifically, the MME processes the signaling protocols between the UE and the EPC, which are known as the Non-Access Stratum (NAS) protocols. The S-GW handles all Internet Procotol (IP) data packets between the UE and the EPC, and serves as the local mobility anchor for the data bearers when the UE moves between network nodes, such as network nodes 105, 110, and 115.

Figure 2 A shows a high-level block diagram of an exemplary LTE architecture in terms of its constituent entities - UE, E-UTRAN, and EPC - and high-level functional division into the Access Stratum (AS) and the Non-Access Stratum (NAS). Figure 1 also illustrates two particular interface points, namely Uu (UE/E-UTRAN Radio Interface) and S l (E- UTRAN/EPC interface), each using a specific set of protocols, i.e., Radio Protocols and S l Protocols. Each of the two protocols can be further segmented into user plane (or“U-plane”) and control plane (or“C-plane”) protocol functionality. On the Uu interface, the U-plane carries user information (e.g., data packets) while the C-plane is carries control information between UE and E-UTRAN.

Figure 2B illustrates a block diagram of an exemplary C-plane protocol stack on the Uu interface comprising Physical (PHY), Medium Access Control (MAC), Radio Link Control (RLC), Packet Data Convergence Protocol (PDCP), and Radio Resource Control (RRC) layers. The PHY layer is concerned with how and what characteristics are used to transfer data over transport channels on the LTE radio interface. The MAC layer provides data transfer services on logical channels, maps logical channels to PHY transport channels, and reallocates PHY resources to support these services. The RLC layer provides error detection and/or correction, concatenation, segmentation, and reassembly, reordering of data transferred to or from the upper layers. The PHY, MAC, and RLC layers perform identical functions for both the U- plane and the C-plane. The PDCP layer provides ciphering/deciphering and integrity protection for both U-plane and C-plane, as well as other functions for the U-plane such as header compression.

Figure 2C shows a block diagram of an exemplary LTE radio interface protocol architecture from the perspective of the PHY. The interfaces between the various layers are provided by Service Access Points (SAPs), indicated by the ovals in Figure 2C. The PHY layer interfaces with the MAC and RRC protocol layers described above. The MAC provides different logical channels to the RLC protocol layer (also described above), characterized by the type of information transferred, whereas the PHY provides a transport channel to the MAC, characterized by how the information is transferred over the radio interface. In providing this transport service, the PHY performs various functions including error detection and correction; rate-matching and mapping of the coded transport channel onto physical channels; power weighting, modulation; and demodulation of physical channels; transmit diversity, beamforming multiple input multiple output (MIMO) antenna processing; and providing radio measurements to higher layers, such as RRC.

The multiple access scheme for the LTE physical layer (PHY) is based on Orthogonal Frequency Division Multiplexing (OFDM) with a cyclic prefix (CP) in the downlink, and on Single-Carrier Frequency Division Multiple Access (SC-FDMA) with a cyclic prefix in the uplink. To support transmission in paired and unpaired spectrum, the LTE PHY supports both Frequency Division Duplexing (FDD) (including both full- and half-duplex operation) and Time Division Duplexing (TDD). Figure 3 shows an exemplary radio frame structure (“type 1”) used for LTE FDD downlink (DL) operation. The DL radio frame has a fixed duration of 10 ms and consists of 20 slots, labeled 0 through 19, each with a fixed duration of 0.5 ms. A l-ms subframe comprises two consecutive slots where subframe i consists of slots 2 i and 2/ + 1 . Each exemplary FDD DL slot consists of N^DL _Symb OFDM symbols, each of which is comprised of N_Sc OFDM subcarriers. Exemplary values of N^DL _Symb can be 7 (with a normal CP) or 6 (with an extended-length CP) for subcarrier bandwidth of 15 kHz. The value of N_sc is configurable based upon the available channel bandwidth. Since persons of ordinary skill in the art are familiar with the principles of OFDM, further details are omitted in this description.

As shown in Figure 3, a combination of a particular subcarrier in a particular symbol is known as a resource element (RE). Each RE is used to transmit a particular number of bits, depending on the type of modulation and/or bit-mapping constellation used for that RE. For example, some REs may carry two bits using QPSK modulation, while other REs may carry four or six bits using 16- or 64-QAM, respectively. The radio resources of the LTE PHY are also defined in terms of physical resource blocks (PRBs). A PRB spans N^RB _SC sub-carriers over the duration of a slot ( i.e ., N^DL _sym_b symbols), where N^RB _SC is typically either 12 (with a 15 -kHz sub-carrier bandwidth) or 24 (7.5-kHz bandwidth). A PRB spanning the same N^RB _SC subcarriers during an entire subframe {i.e., 2N^DL _sym_b symbols) is known as a PRB pair. Accordingly, the resources available in a subframe of the LTE PHY DL comprise N^DLRB PRB pairs, each of which comprises 2N^DL _symb· N^RB _scREs. For a normal CP and l5-kHz sub-carrier spacing (SCS), a PRB pair comprises 168 REs.

One exemplary characteristic of PRBs is that consecutively numbered PRBs ( e.g ., PRBi and PRBi_+i) comprise consecutive blocks of subcarriers. For example, with a normal CP and l5-kHz SCS, PRBo comprises sub-carrier 0 through 11 while PRBi comprises sub-carriers 12 through 23. The LTE PHY resource also can be defined in terms of virtual resource blocks (VRBs), which are the same size as PRBs but may be of either a localized or a distributed type. Localized VRBs can be mapped directly to PRBs such that VRB «_VRB corresponds to PRB ^WPRB = «vRi_! · On the other hand, distributed VRBs may be mapped to non-consecutive PRBs according to various rules, as described in 3GPP Technical Specification (TS) 36.213 or otherwise known to persons of ordinary skill in the art. However, the term“PRB” shall be used in this disclosure to refer to both physical and virtual resource blocks. Moreover, the term “PRB” will be used henceforth to refer to a resource block for the duration of a subframe, i.e., a PRB pair, unless otherwise specified.

Downlink (i.e., eNB to UE) physical channels carried by the LTE PHY include Physical Downlink Shared Channel (PDSCH), Physical Multicast Channel (PMCH), Physical Downlink Control Channel (PDCCH), Relay Physical Downlink Control Channel (R-PDCCH), Physical Broadcast Channel (PBCH), Physical Control Format Indicator Channel (PCFICH), and Physical Hybrid ARQ Indicator Channel (PHICH). In addition, the LTE PHY downlink includes various reference signals, synchronization signals, and discovery signals.

Exemplary LTE FDD uplink (ETL) radio frames can configured in a similar manner as the exemplary FDD DL radio frame shown in Figure 3. For example, using terminology consistent with the above DL description, each UL slot consists of N^UL _Symb OFDM symbols, each of which includes N_sc OFDM subcarriers.

Uplink ( i.e ., UE to eNB) physical channels carried by the LTE PHY include Physical Uplink Shared Channel (PUSCH), Physical Uplink Control Channel (PUCCH), and Physical Random-Access Channel (PRACH). In addition, the LTE PHY uplink includes various reference signals including demodulation reference signals (DM-RS), which are transmitted to aid the eNB in the reception of an associated PUCCH or PUSCH; and sounding reference signals (SRS), which are not associated with any uplink channel.

Both PDCCH and PUCCH can be transmitted on aggregations of one or several consecutive control channel elements (CCEs), and a CCE is mapped to the physical resource based on resource element groups (REGs), each of which is comprised of a plurality of REs. For example, a CCE can comprise nine (9) REGs, each of which can comprise four (4) REs.

As discussed above, the LTE PHY maps the various DL and UL physical channels to the PHY resources. For example, the PHICH carries HARQ feedback (e.g., ACK/NAK) for UL transmissions by the UEs. Similarly, PDCCH carries scheduling assignments, channel quality feedback (e.g., CSI) for the UL channel, and other control information. Likewise, a PUCCH carries uplink control information such as scheduling requests, CSI for the downlink channel, HARQ feedback for network node DL transmissions, and other control information. Both PDCCH and PUCCH can be transmitted on aggregations of one or several consecutive control channel elements (CCEs), and a CCE is mapped to the physical resource based on resource element groups (REGs), each of which is comprised of a plurality of REs. For example, a CCE can comprise nine (9) REGs, each of which can comprise four (4) REs.

To support mobility (e.g., handover or reselection) between cells and/or beams, a UE can perform periodic cell search and measurements of signal power and quality (e.g., reference signal received power, RSRP, and Reference signal received quality, RSRQ) in both Connected and Idle modes. The UE is responsible for detecting new neighbor cells, and for tracking and monitoring already detected cells. The detected cells and the associated measurement values are reported to the network. An LTE UE can perform such measurements on various downlink reference signals (RS) including, e.g., cell-specific Reference Signal (CRS), MBSFN reference signals, UE-specific Reference Signal (DM-RS) associated with PDSCH, Demodulation Reference Signal (DM-RS) associated with EPDCCH or MPDCCH, Positioning Reference Signal (PRS), and CSI Reference Signal (CSI-RS).

While LTE was primarily designed for user-to-user communications, 5G (also referred to as“New Radio” or“NR”) cellular networks are envisioned to support both high single-user data rates (e.g., 1 Gb/s) and large-scale, machine-to -machine communication involving short, bursty transmissions from many different devices that share the frequency bandwidth. The 5G radio standards are currently targeting a wide range of data services including eMBB (enhanced Mobile Broad Band) and URLLC (Ultra-Reliable Low Latency Communication). These services can have different requirements and objectives. For example, URLLC is intended to provide a data service with extremely strict error and latency requirements, e.g., error probabilities as low as 10^-5 or lower and 1 ms end-to-end latency or lower. For eMBB, the requirements on latency and error probability can be less stringent whereas the required supported peak rate and/or spectral efficiency can be higher.

Another important goal of NR is to provide more capacity for operators to serve ever increasing traffic demands and variety of applications. Because of this, NR will be able to operate on frequencies over 6 GHz up to 60 or even 100 GHz. In comparison to the current frequency bands allocated to LTE, some of the new bands will have much more challenging propagation properties such as lower diffraction and higher outdoor/indoor penetration losses. As a consequence, signals will have less ability to propagate around comers and penetrate walls. In addition, in high frequency bands atmospheric/rain attenuation and higher body losses render the coverage of NR signals even more spotty. Fortunately, the operation in higher frequencies also makes it possible to use smaller antenna elements, which enables antenna arrays with many antenna elements. As such, beamforming may play an even greater role in NR than in LTE.

Different types of UE requirements are specified in 3GPP standards. The objective of UE requirement verification is to verify that UE fulfils the desired requirements in a given scenario, conditions, and/or channel environment. Other UE requirements can be specified and/or requested by an operator deploying the network. These UE requirements are categorized into several different types. Non-limiting examples of UE requirements are: • UE RF receiver requirements e.g., receiver sensitivity

• UE RF transmitter requirements e.g., UE transmit power accuracy, UE radio emission mask, UE maximum power reduction etc.

• UE demodulation requirements e.g., achievable throughput

• UE CSI reporting requirements e.g., CQI reporting accuracy

• Radio resource management (RRM) related requirements e.g., cell identification delay, handover delay, measurement accuracy (e.g., SS-RSRP accuracy, etc.).

In order to ensure that UE meets these requirements, appropriate and relevant test cases are also specified. The testing and/or verification of UE requirements can be broadly categorized into lab verification and verification in an actual (e.g., real or live) network. In lab verification, each base station involved in the test is emulated by test equipment, which is often referred to as system (or network) simulator, test system, or testing node. As such, all downlink transmission in a cell for the UE under test is done by the test equipment. During a test all common control channels and other necessary UE-specific control channels (e.g., PDCCH) are transmitted by the test equipment. In addition, a data channel (e.g., PDSCH) is also needed to send necessary data and configure the UE.

Furthermore, typically only a single UE is tested at any given time, such that, in most typical test cases, the entire available downlink resources are not used by the UE. However, to make testing approximate actual conditions, the remaining downlink resources should also be transmitted to one or multiple virtual UEs. This transmission should take place according to some well-defined pattern, which may be different in different types of tests. In E-UTRAN, this type of resource allocation to generate load in OFDMA is referred to as OFDM channel noise generation (OCNG) or generating OFDM channel noise (OCN).

As mentioned above, the OCNG is sent to a plurality of virtual UEs for loading the cell during the test. In general, the term“virtual UE” refers to a UE other than the UE under test, as specified in 3GPP TS 36.133. Such virtual UEs are generally intended to represent actual UEs that could be operating in a cell of a live network, thereby facilitating testing under approximated actual conditions while minimizing the number of actual UEs required.

As discussed above, in an OFDMA system, the transmission resources of a cell are portions of a time-frequency grid, along with a particular transmit power level. Additionally, the same resources can be reused by the cell when transmitting in a different spatial direction, e.g., using a different spatial beam.

Other tests to verify certain UE requirements are performed in a real network, e.g., before launching a new feature and/or verifying a particular UE device. These tests may involve single or multiple UEs. When tests are being performed before network roll-out or in an early phase of deployment, the traffic load can be very low. This may also be the case under certain conditions in legacy networks. As such, resources not allocated to the UEs under test should be allocated to the virtual UEs according to some well-defined pattern in order to emulate load in the cell. Thus, either all or large part of available resources should be used in the tests. This requires a base station to implement the ability to generate load in a controlled manner, thereby facilitating verification of the UE requirements in a real network under load before rolling out any new feature (e.g., new frequency band, MIMO with larger number of antennas, multicarrier with larger number of carriers, etc.). OCNG can also be beneficial since only a small number of test UEs (e.g., as low as one) are necessary to perform the test.

In addition, a real base station must be able to emulate a high-traffic, commercial- service for regulatory compliance testing (e.g., FCC emissions compliance). This inspection verifies base station transmitter characteristics such as transmission power or emission level. Since these measurements must be performed under the fully loaded condition, the base station must generate OCN.

In LTE, the mechanism to generate OCN can be implemented in an actual base station.

Due to various differences between LTE and NR, however, the mechanism used to generate OCN in LTE cannot be applied in NR.

SUMMARY

Exemplary embodiments disclosed herein address these problems, issues, and/or drawbacks of existing solutions by providing a flexible but efficient approach for configuring an NR radio node to transmit signals in a controlled and adaptive manner in a cell with SSB transmission in the downlink. These exemplary embodiments provide improvements to the operation of UEs in a cellular (e.g., 5G/NR) network, particularly in relation to facilitating network testing of NR UEs in realistic and timely manner. Furthermore, exemplary embodiments include methods that can be implemented not only in an NR radio node but also in test equipment, thereby facilitating testing of UEs in a laboratory environment.

Exemplary embodiments of the present disclosure include methods and/or procedures for generating signals usable for testing operation of a user equipment (UE) ( i.e ., a UE under test) within a cell of a wireless communication system. The exemplary methods and/or procedures can be implemented, for example, in a radio network node ( e.g ., base station, eNB, gNB, etc. or component thereof) and/or a radio network simulator. The exemplary methods and/or procedures can include determining a first set of time-frequency resources, within the frequency bandwidth of the cell, usable for transmitting a common signal directed to all UEs operating in the cell. In some embodiments, the common signal can include a synchronization signal and physical broadcast channel block (SSB).

The exemplary methods and/or procedures can also include, based on the first set of time-frequency resources, determining a third set of time-frequency resources, within the frequency bandwidth of the cell, usable for transmitting a third set of signals directed to the UE. In some embodiments, the third set of signals are usable by the UE under test to perform one or more measurements. In some embodiments, the third set of signals can include one or more of the following: reference measurement channel (RMC), physical downlink shared channel (PDSCH), and physical downlink control channel (PDCCH). The third set of time-frequency resources can be determined in various ways according to various embodiments.

The exemplary methods and/or procedures can also include, based on the first and the third sets of time-frequency resources, determining a second set of time-frequency resources, within the frequency bandwidth of the cell, usable for transmitting a second set of signals directed to one or more virtual UEs. In some embodiments, determining the second set of time- frequency resources can be further based on one or more particular tests to be conducted for the UE. In various embodiments, the second set of signals can include one or more of the following: load generating signals; noise generating signals; virtual UE signals; and synchronization signal OFDM channel noise (SS-OCN). The second set of time-frequency resources can be determined in various ways according to various embodiments

The exemplary methods and/or procedures can also include transmitting the common signal, the second set of signals, and the third set of signals using the determined first, second, and third sets of time-frequency resources. Such transmitted signals can be received by the UE ( i.e ., the UE under test).

Other exemplary embodiments include radio network nodes ( e.g ., base station, eNB, gNB, etc. or component thereof) and radio network simulators configured to perform operations corresponding to the exemplary methods and/or procedures described herein. Other exemplary embodiments include non-transitory, computer-readable media storing program instructions that, when executed by at least one processor, configure such radio network nodes or radio network simulators to perform operations corresponding to the exemplary methods and/or procedures described herein.

These and other objects, features, and advantages of the present disclosure will become apparent upon reading the following detailed description in view of the drawings briefly described below.

BRIEF DESCRIPTION OF THE DRAWINGS

Figure 1 is a high-level block diagram of an exemplary architecture of the Long-Term Evolution (LTE) Evolved UTRAN (E-UTRAN) and Evolved Packet Core (EPC) network, as standardized by 3GPP.

Figure 2A is a high-level block diagram of an exemplary E-UTRAN architecture in terms of its constituent components, protocols, and interfaces.

Figure 2B is a block diagram of exemplary protocol layers of the control-plane portion of the radio (Uu) interface between a user equipment (UE) and the E-UTRAN.

Figure 2C is a block diagram of an exemplary LTE radio interface protocol architecture from the perspective of the PHY layer.

Figure 3 is an exemplary resource grid diagram illustrating arrangement of time- frequency resources in the LTE downlink radio interfaces used for frequency-division duplex (FDD) operation;

Figure 4 shows an exemplary time-frequency resource grid for an NR slot.

Figures 5A-B shows various exemplary NR slot configurations.

Figures 6A-C show various exemplary time-frequency configurations of NR SS/PBCH blocks (SSBs) usable with one or more exemplary embodiments of the present disclosure. Figures 7A-B, 8A-B, and 9-12 illustrate various exemplary allocations of time- frequency resources for signals S 1-S3 that comprise a composite SS-OCNG transmission to a UE under test, according to various exemplary embodiments of the present disclosure.

Figure 13 is a flow diagram illustrating exemplary methods and/or procedures performed by a radio network node ( e.g ., base station in an NR network) or radio network simulator system according to various exemplary embodiments of the present disclosure.

Figure 14 illustrates an exemplary embodiment of a wireless network, in accordance with various aspects described herein.

Figure 15 illustrates an exemplary embodiment of a UE, in accordance with various aspects described herein.

Figure 16 is a block diagram illustrating an exemplary virtualization environment usable for implementation of various embodiments of network nodes described herein.

Figure 17 is a block diagram of an exemplary communication system and/or network, in accordance with various aspects described herein.

Figure 18 is a block diagram of an exemplary radio network simulator, according to various exemplary embodiments of the present disclosure.

DETAILED DESCRIPTION

Some of the embodiments contemplated herein will now be described more fully with reference to the accompanying drawings. Other embodiments, however, are contained within the scope of the subject matter disclosed herein, 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. Furthermore, the following terms are used throughout the description given below:

• Radio Node: As used herein, a“radio node” can be either a“radio access node” or a “wireless device.”

• Radio Access Node: As used herein, a“radio access node” (or“radio network node”) can be any node in a radio access network (RAN) of a cellular communications network that operates to wirelessly transmit and/or receive signals. Some examples of a radio access node include, but are not limited to, a base station (e.g., a New Radio (NR) base station (gNB) in a 3 GPP Fifth Generation (5G) NR network or an enhanced or evolved Node B (network node) in a 3GPP LTE network), a high-power or macro base station, a low-power base station ( e.g ., a micro base station, a pico base station, a home network node, or the like), and a relay node.

• Core Network Node: As used herein, a“core network node” is any type of node in a core network. Some examples of a core network node include, e.g., a Mobility Management Entity (MME), a Packet Data Network Gateway (P-GW), a Service Capability Exposure Function (SCEF), or the like.

• Wireless Device: As used herein, a“wireless device” is any type of device that has access to ( i.e ., is served by) a cellular communications network by communicating wirelessly with network nodes or other wireless devices. Communicating wirelessly can involve transmitting and/or receiving wireless signals using electromagnetic waves, radio waves, infrared waves, and/or other types of signals suitable for conveying information through air. Unless otherwise noted, the term“wireless device” is used interchangeably herein with“user equipment” (or“UE” for short). Some exemplary wireless devices include, but are not limited to, a UE in a 3GPP network and a Machine Type Communication (MTC) device. Further examples of wireless devices include a radio communication device, target device, device to device (D2D) UE, a UE- equipped sensor, tablet, mobile terminal, smart phone, laptop-embedded equipped (LEE), laptop-mounted equipment (LME), USB device, customer premises equipment (CPE), etc. The term“UE under test” or“device under test” (DUT) may refer to any type of UE.

• Network Node: As used herein, a“network node” is any node that is either part of the radio access network or the core network of a cellular communications network/system. Functionally, a network node can be equipment capable, configured, arranged, and/or operable to communicate directly or indirectly with a wireless device and/or with other network nodes or equipment in the cellular communications network, to enable and/or provide wireless access to the wireless device, and/or to perform other functions (e.g., administration) in the cellular communications network.

• Radio measurement: As used herein, a“radio measurement” can refer to any measurement performed on radio signals. Radio measurements can be absolute or relative. Radio measurement can be signal level, signal quality, and/or signal strength. Radio measurements can be intra-frequency, inter-frequency, CA, etc. A radio measurement can be performed on one or more cells operating on a frequency layer ( e.g ., cell specific measurement) and/or on a carrier frequency (e.g., carrier specific measurement) that may be common for more than one cells on that carrier. Radio measurements can be unidirectional (e.g., DL or UL) or bidirectional (e.g., RTT, Rx- Tx, etc.). Some examples of radio measurements include timing measurements (e.g., TOA, timing advance, RTT, RSTD, Rx-Tx, propagation delay, SSTD. SFTD etc.); angle measurements (e.g., angle of arrival); power-based measurements (e.g., received signal power, RSRP, received signal quality, RSRQ, SINR, SNR, interference power, total interference plus noise, RSSI, noise power, etc.); cell detection or cell identification; radio link monitoring (RLM); system information (SI) reading; etc.

• UE requirement: As used herein,“UE requirement” may refer to any criteria or metric which characterizes the performance of any procedure performed by a UE. Examples of procedures are measurement, reception of signals, transmission of signals, cell change (e.g., handover, cell reselection, RRC connection re-establishment etc), activation/deactivation of serving cell, UE transmit power control etc. The term UE requirement can be used interchangeably with performance requirements, radio requirements, measurement requirement, measurement performance requirements, etc. For example, a UE may have to meet one or more UE requirements related to a performed procedure. Examples of UE requirements include measurement time, number of cells to be measured with the measurement time, measurement reporting delay, measurement accuracy, measurement accuracy with respect to a reference value (e.g., ideal measurement result), etc. Examples of measurement time include measurement period, cell identification period, evaluation period, etc. Other examples of UE radio requirements include receiver sensitivity, UE maximum output power tolerance, UE maximum power reduction, UE maximum allowed radio emission in an adjacent carrier, etc.

Note that the description herein focuses on a 3GPP cellular communications system and, as such, 3GPP terminology or terminology similar to 3GPP terminology is oftentimes used. However, the concepts disclosed herein are not limited to a 3GPP system. Furthermore, although the term“cell” is used herein, it should be understood that (particularly with respect to 5G NR concepts) beams may be used instead of cells and, as such, concepts described herein apply equally to both cells and beams.

Likewise, the disclosed principles and/or embodiments are applicable for any OFDM- or OFDMA-based system in which signals are generated based on OFDM and/or OFDMA technology. The general OFDM and/or OFDMA based technology herein may comprise different variants. Specific examples of OFDM and/or OFDMA based technology are single carrier, frequency-division multiple access (SC-FDMA), Discrete Fourier Transform-spread- OFDM (DFT-s-OFDM), etc.

As briefly mentioned above, due to various fundamental differences between LTE and NR, the mechanism used in LTE to generate OCNG cannot be applied in NR. Some of these fundamental differences are explained below.

Similar to LTE, NR uses CP-OFDM (Cyclic Prefix Orthogonal Frequency Division Multiplexing) in the downlink and both CP-OFDM and DFT-spread OFDM (DFT-S-OFDM) in the uplink. In the time domain, NR downlink and uplink physical resources are organized into equally-sized subframes of lms each. A subframe is further divided into multiple slots of equal duration, with each slot including multiple OFDM-based symbols.

In Rel-l5 NR, a UE can be configured with up to four carrier bandwidth parts (BWPs) in the downlink with a single downlink carrier BWP being active at a given time. A UE can be configured with up to four carrier BWPs in the uplink with a single uplink carrier BWP being active at a given time. If a UE is configured with a supplementary uplink, the UE can be configured with up to four additional carrier BWPs in the supplementary uplink, with a single supplementary uplink carrier BWP being active at a given time.

Figure 4 shows an exemplary time-frequency resource grid for an NR slot. As illustrated in Figure 4, a resource block (RB) consists of a group of 12 contiguous OFDM subcarriers for a duration of a l4-symbol slot. Like in LTE, a resource element (RE) consists of one subcarrier in one slot. Common RBs (CRBs) are numbered from 0 to the end of the system bandwidth. Each BWP configured for a UE has a common reference of CRB 0, such that a particular configured BWP may start at a CRB greater than zero. In this manner, a UE can be configured with a narrow BWP (e.g., 10 MHz) and a wide BWP (e.g., 100 MHz), each starting at a particular CRB, but only one BWP can be active for the UE at any given time. Within a BWP, RBs are defined and numbered in the frequency domain from 0 to

i is the index of the particular BWP for the carrier. Similar to LTE, each

NR resource element (RE) corresponds to one OFDM subcarrier during one OFDM symbol interval. Various SCS values (referred to as numerologies) are supported in NR and are given by D/ = (15 X 2^a ) kHz where a e (0,1, 2, 3, 4) . D/ = 15 kHz is the basic (or reference) subcarrier spacing that is also used in LTE. The slot length is inversely related to subcarrier spacing or numerology according to l/2^a ms. For example, there is one (l-ms) slot per subframe for Af = 15 kHz, two 0.5-ms slots per subframe for Af = 30 kHz, etc. In addition, the RB bandwidth is directly related to numerology according to 2^a * 180 kHz.

Table 1 below summarizes the supported NR transmission numerologies and associated parameters. Different DL and UL numerologies can be configured by the network.

Table 1.

An NR slot can include 14 OFDM symbols for normal cyclic prefix and 12 OFDM symbols for extended cyclic prefix. Figure 5A shows an exemplary NR slot configuration comprising 14 symbols, where the slot and symbols durations are denoted T_s and T_symb, respectively. In addition, NR includes a Type-B scheduling, also known as“mini-slots.” These are shorter than slots, typically ranging from one symbol up to one less than the number of symbols in a slot ( e.g ., 6 or 13), and can start at any symbol of a slot. Mini-slots can be used if the transmission duration of a slot is too long and/or the occurrence of the next slot start (slot alignment) is too late. Applications of mini-slots include unlicensed spectrum and latency- critical transmission (e.g., URLLC). Even so, mini-slots are not service- specific and can be used for eMBB, etc.

Similar to LTE, NR data scheduling is done on a per-slot basis. In each slot, the base station (e.g., gNB) transmits downlink control information (DCI) over PDCCH that indicates which UE is scheduled to receive data in that slot, which RBs will carry that data. A UE first detects and decodes DCI and, if successful, then decodes the corresponding PDSCH based on the decoded DCI. Likewise, DCI can include UL grants that indicate which UE is scheduled to transmit data in that slot, which RBs will carry that data. A UE first detects and decodes an uplink grant from PDCCH and, if successful, then transmits the corresponding PUSCH on the resources indicated by the grant. DCI formats 0_0 and 0_l are used to convey UL grants for PUSCH, while DCI formats l_0 and l_l are used to convey PDSCH scheduling. Other DCI formats (2_0, 2_l, 2_2 and 2_3) are used for other purposes including transmission of slot format information, reserved resource, transmit power control information, etc. In addition to grants or assignments, DCI can also carry an indication of modulation and coding scheme (MCS) to be used for DL or UL transmissions.

Figure 5B shows an exemplary NR slot structure with l5-kHz subcarrier spacing (e.g., m = 0 in Table 1). Within an NR slot, the PDCCH channels are confined to a particular number of symbols and a particular number of subcarriers, where this region is referred to as the control resource set (CORESET). In the exemplary structure shown in Figure 5B, the first two symbols contain PDCCH and each of the remaining 12 symbols contains physical data channels (PDCH), i.e., either PDSCH or PUSCH. Depending on the particular CORESET configuration, however, the first two slots can also carry PDSCH or other information, as required.

A CORESET is made up of multiple RBs (i.e., multiples of 12 REs) in the frequency domain and either one, two, or three OFDM symbols in the time domain, as further defined in 3GPP TS 38.211 § 7.3.2.2. A CORESET is functionally similar to the control region in LTE subframe. Like in LTE, the CORESET time domain size can be indicated by PCFICH. However, each NR REG includes all 12 REs of one OFDM symbol in a RB, whereas an LTE REG includes only four REs, as discussed above. Moreover, the frequency bandwidth of the LTE control region is fixed (i.e., to total system bandwidth), while the frequency bandwidth of the NR CORESET is variable. CORESET resources can be indicated to a UE by RRC signaling.

The smallest unit used for defining CORESET is the REG, which spans one PRB in frequency and one OFDM symbol in time. In addition to PDCCH, each REG contains demodulation reference signals (DM-RS) to aid in the estimation of the radio channel over which that REG was transmitted. When transmitting the PDCCH, a precoder can be used to apply weights at the transmit antennas based on some knowledge of the radio channel prior to transmission. It is possible to improve channel estimation performance at the UE by estimating the channel over multiple REGs that are proximate in time and frequency, so long as the same precoder used for the REGs by the transmitter. To assist the UE with channel estimation, the multiple REGs can be grouped together to form a REG bundle, and the REG bundle size for a CORESET can be indicated to the UE. The UE can assume that any precoder used for the transmission of the PDCCH is the same for all the REGs in the REG bundle. A REG bundle may consist of 2, 3, or 6 REGs.

An NR control channel element (CCE) consists of six REGs. These REGs may either be contiguous or distributed in frequency. When the REGs are distributed in frequency, the CORESET is said to use interleaved mapping of REGs to a CCE, while if the REGs are contiguous in frequency, a non-interleaved mapping is said to be used. Interleaving can provide frequency diversity. On the other hand, not using interleaving can be beneficial when available knowledge of the channel facilitates the use of a precoder in a particular part of the spectrum, thereby improving the SINR at the receiver.

In NR, downlink signals available for UE measurement can occur much more sparsely, or over a longer time period, than in LTE. An exemplary configuration for an NR synchronization signal and PBCH block (SSB) is illustrated in Figure 6A. The NR SSB comprises a Primary Synchronization Signal (PSS), a Secondary Synchronization Signal (SSS), a Physical Broadcast Channel (PBCH), and Demodulation Reference Symbols (DM-RS). As also shown in Figure 6A, an individual SSB spans four adjacent OFDM symbols within a PRB. Multiple SSBs comprise an SSB burst, which is transmitted within a half-frame ( e.g ., 5 ms). Moreover, within the half-frame, multiple SSBs for different cells or different beams may be transmitted, as illustrated with SSB indices 0-7 in Figure 6B. The number of SSB locations in a burst depends on the frequency range (e.g., 0-3 or 0-6 GHz as shown in Figure 6B), as well as on the particular NR radio interface configuration. The SSB burst (hence the individual SSBs) is transmitted according to an SSB measurement timing configuration (SMTC) cycle, as illustrated in Figure 6C. The SMTC cycle can be 5, 10, 20, 40, 80 or 160 ms.

During each SMTC cycle or SMTC period, one or more SSBs are transmitted during a time window referred to as the SMTC window. The maximum SMTC window duration is 5 ms, but the actual window depends on several factors including subcarrier spacing (SCS) of SSB, number of SSBs (corresponding to number of beams) within the SMTC window, etc. As such, the SMTC window duration can be an integer number of milliseconds from one (1) to five (5), i.e., 1 ms to 5 ms.

The SSB signals are used by the UE for performing various operations. Examples of such operations are time and/or frequency synchronization, radio link monitoring (e.g., out-of- sync evaluation, in-sync evaluation, etc.), cell search, measurements (e.g., SS-RSRP, SS- RSRQ, SS-SINR, etc.), channel estimation etc.

In LTE, the common signals for a cell have fixed, well-defined location in time and frequency. For example, the LTE PSS/SSS are pre-defined to be transmitted in subframes 0 and 5. Similarly the PBCH is pre-defined to be transmitted in subframe 0. In the frequency domain, the signals are transmitted on the central six (6) RBs of the carrier transmission bandwidth. On the other hand, as illustrated and explained above in relation to Figure 6, the NR SSB transmission in a cell is quite flexible both in time and frequency.

Another exemplary difference is that the NR SSB can be transmitted using different subcarrier spacings (SCS) of 15 kHz, 30 kHz, 120 kHz, 240 kHz, etc., while the SCS of LTE PSS/SSS is fixed at 15 kHz. Moreover, an NR EGE can receive and/or transmit signals (e.g., PDSCH, PDCCH, etc.) with different SCS such as 15 kHz, 30 kHz, 60 kHz, 120 kHz, etc.

Another exemplary difference is that in NR, the UE can apply receiver beam sweeping for receiving SSB signals. For example, the UE can search for neighbour cells or perform neighbour cell measurements in a different spatial direction than the serving cell. As such, during SSB reception using beam sweeping, the UE cannot receive other signals (e.g., PDSCH, PDCCH, etc.).

Due to these and other differences between LTE and NR, the NR OCNG generation needed to verify NR UE requirements cannot be based on the same or similar approach as used in LTE. If such LTE principles were applied during testing, an otherwise-compliant NR UE may be incorrectly identified as failing one or more tests and/or not meeting one or more requirements. As such, this can result in delays to UE and/or network deployment. Exemplary embodiments of the present disclosure address these and other drawbacks by configuring an NR radio node to transmit signals in a controlled and adaptive manner in a cell with SSB transmission in the downlink, thereby facilitating performance of tests on NR UEs in realistic and timely manner. Furthermore, exemplary embodiments include methods that can be implemented not only in an NR radio node, but also in test equipment, etc. According to high-level principles, exemplary embodiments node to adaptively transmit signals to a device under test (e.g., a UE) and also signals to one or more virtual UEs during a test when verifying UE requirements or system performance in NR system. The adaptation of the transmission of the signals to DUT and virtual UEs in the NR cell can be based on the location (e.g., within the time-frequency grid) of resources used for the transmission of the common signals (e.g., the SSB). The time-frequency location of the common signals can be adaptive according to the NR cell bandwidth. In the case of SSB, for example, frequency resources, SMTC periodicity, and SMTC window are adaptive.

Some exemplary embodiments include methods and/or procedures in which a radio node (e.g., an NR radio node, base station, and/or test equipment) determines a location of at least one common signal within a bandwidth of a cell. The common signal can comprise a first set of signals (also referred to as Sl), which can be an SSB. The location can comprise a first set of time-frequency resources (also referred to as Rl), e.g., within a time-frequency grid. In some embodiments, Rl can be an SMTC window for transmitting the SSB.

The exemplary methods and/or procedures can also include the radio node using the determined location to adapt transmission of various signals using various resources. In some embodiments, the radio node can use the determined location to select a second set of time- frequency resources (also referred to as R2) for transmitting a second set of signals (also referred to as S2) to one or more virtual UEs in the cell. In some embodiments, the radio node can use the determined location to select a third set of time-frequency resources (also referred to as R3) for transmitting a third set of signals (also referred to as S3) to a UE under test in the cell. For example, the third set of signals (S3) can include PDSCH, PDCCH, etc. Collectively, Sl, S2, and S3 are referred to herein as an SS-OCNG pattern.

In some embodiments, the second set of signals (S2) can be load generating signals, noise generating signals, virtual UE signals, and/or synchronization signal OFDM channel noise (SS-OCN). In some embodiments, the third set of signals (S3) can be one or more reference measurement channels (RMCs) transmitted by the radio node to the UE under test during the test, e.g., to configure the UE by one or more procedures and/or schedule the UE with respect to other signals. Examples of RMCs include PDSCH, PDCCH, etc.

In some embodiments, the time resources can be selected such that Rl, R2, and R3 don’t overlap with each other. For example, R2 and R3 can be allocated in resource blocks that are different than the resource blocks used for Rl. In another exemplary embodiment, the radio node can adapt, determine, and/or select resources R3 such that R3 doesn’t overlap with Rl in at least the time domain. For example, R3 can be allocated in time resources occurring outside the SMTC window, in which the SSB is transmitted. In yet another example, R3 can be allocated in time resources that occur outside the SMTC window (in time) but also which occur in different frequency resources than used by Rl.

The exemplary methods and/or procedures can also include the radio node transmitting S2 and/or S3 using time-frequency resources R2 and/or R3.

Exemplary embodiments of the present disclosure provide various advantages and/or address various drawbacks discussed above. For example, embodiments facilitate a radio network node ( e.g ., an NR base station) to verify performance requirements of a UE operating in NR cell of an actual NR network. Similarly, embodiments facilitate test equipment (e.g., system simulator) to more accurately verify performance requirements of a UE in a lab environment.

As another example, embodiments facilitate a radio network node (e.g., an NR base station) to generate traffic load for a test scenario in an adaptive manner regardless of the numerology (e.g., SCS) of signals and/or the location of common signals (e.g., SSB) within a carrier bandwidth. As such, embodiments facilitate consistent outcomes of the tests performed in different types of radio nodes.

As another example, embodiments facilitate various entities (e.g., network operator, equipment vendor, etc.) to simulate various load conditions that occur in actual cells and to obtain feedback and/or results that can be useful for tuning network parameters. Such tunable network parameters include parameters sent to UEs as network configuration, such as thresholds that trigger a UE action or a UE report to the radio node, etc. Such feedback can also be useful for further development of functionality in the UE, the radio node, and/or other network node.

In various embodiments, when the radio node is required to generate signals S2 and S3, the radio node initially determines the first set of resources, Rl, used for transmitting common signal Sl. For example, this can be done by one or more of the following mechanisms:

• by retrieving stored configuration information about currently used SSB in the cell; • by monitoring characteristic of signals transmitted in different time-frequency resources;

• based on historical data or statistics (e.g., Sl configuration used in past);

• based on relations between S 1 configuration and type of tests e.g. , specific S 1 location is used in certain types of tests. For example, the lowest part of cell BW can be used for S l for verifying UE radio requirements.

• based on transmission characteristics of the cell, such as channel bandwidth, numerology (e.g., SCS) used in the cell for Sl and/or for other signals, etc.

Based on the determined time-frequency location of Rl for Sl, the radio node can determine the location of R2 and R3 used for transmission of other signals. The location of R2 and R3 can further depend on the type of UE requirements to be verified. Some specific examples include:

• R3 can be selected in time-frequency location that does not overlap with the Rl time- frequency resources used for S 1.

• R3 can be determined in time resources which occur outside the SMTC window (in time) and also in frequency resources which are not part of Rl. For example, this type of allocation can be used for verifying radio resource management (RRM) requirements such as, e.g., cell search delay, RSRP accuracy, etc.

• Time resources of R3 can be selected to overlap with time resources of Rl (e.g., same symbols used for SSB), but in frequency resources different than allocated for Rl . For example, if Rl comprises symbols 2-5 in resource blocks 0- 19, then R3 can be selected in one or more symbols 2-5 but in resource blocks 20-39 (e.g., 24 RBs).

• SCS of R3 can be different than the SCS of Rl. For example, this type of allocation can be used to verify that a UE is capable of receiving signals with different numerologies at the same time (e.g., SSB with SCS of 15 kHz, RMC containing PDSCH with SCS of 30 kHz).

Based on the determination of Rl and R3, the radio node can determine the location of R2 within the frequency bandwidth of the cell. The resources comprising R2 can be used for transmitting one or more signals (e.g., a second set of signals) to one or more“virtual UEs” associated with the cell. This determination of R2 can be done in various ways, including the examples given below: • All unused radio resources (not used for S 1 or S3) can be allocated for S2

• Only a subset of the unused radio resources (not used for S 1 and S3) can be allocated for S2. In this case, the remaining unallocated resources can be reserved for some other potential transmissions, e.g., paging messages, system information, random access response (RAR) within the RAR transmission window, reference symbols used for CSI estimation or time tracking, etc.

• The amount of resources allocated for virtual UEs can depend on one or more factors such as the number of virtual UEs, the number of RBs per virtual UE, base station antenna transmission mode, transmission characteristics of S2 (e.g., modulation type, transport block size, modulation and coding scheme, etc.). For example, S2 may comprise a group of one or more RBs per virtual UE, and/or be modulated with a specific modulation such as QPSK, 16-QAM, PE2-BPSK, 64-QAM etc.

Various other examples are described below with reference to the appended figures. Figure 7, which includes Figures 7A and 7B, illustrates an exemplary allocation of time- frequency resources for signals S 1-S3 that comprise a composite SS-OCNG transmission to a UE under test, according to various exemplary embodiments of the present disclosure. In this example, S l (e.g., SSB) is allocated RB 0-19 (SSB size = 20 RBs) within a 10 MHz channel bandwidth (e.g., 52 RBs). SMTC duration is 5 ms. The signal S3 (e.g., RMC comprising PDSCH) is allocated outside the SMTC window using 24 RBs within the cell bandwidth. Signal S2 is allocated the remaining resources within the cell’s frequency bandwidth. All the signals in this example are transmitted using the same SCS of 15 kHz. Figures 7A and 7B illustrate configurations for FDD and TDD, respectively, wherein TDD signals are transmitted only in DL slots.

Figure 8, which includes Figures 8 A and 8B, illustrates another exemplary allocation of time-frequency resources for signals S 1-S3 that comprise a composite SS-OCNG transmission to a UE under test, according to various other exemplary embodiments of the present disclosure. These examples are similar to the ones illustrated by Figure 7, except that they also include a second channel (e.g., PDCCH type 0) for certain operations like paging, etc. This could be part of S3 (e.g., second RMC) or independent of any RMC. Figures 8A and 8B illustrate configurations for FDD and TDD, respectively, wherein TDD signals are transmitted only in DF slots. Figure 9 illustrates another exemplary allocation of time-frequency resources for signals S1-S3 that comprise a composite SS-OCNG transmission to a UE under test, according to various other exemplary embodiments of the present disclosure. In this TDD- only example, resources R1-R3 are allocated within a cell bandwidth of 20 MHz for SCS = 30 kHz (51 RBs). In this case, S3 RMC ( e.g ., PDSCH) is allocated over 24 RBs outside the SMTC window. This scenario is applicable for TDD in frequency bands between 3-6 GHz, since these bands support SCS of 30 kHz but don’t support SCS of 15 kHz.

Figure 10 illustrates another exemplary allocation of time-frequency resources for signals S1-S3 that comprise a composite SS-OCNG transmission to a UE under test, according to various other exemplary embodiments of the present disclosure. This example is similar to the one illustrated by Figure 9, except that in this case there are also resource blocks allocated for PDCCH-type 0 (e.g., 20 PRBs over two slots).

Figure 11 illustrates another exemplary allocation of time-frequency resources for signals S1-S3 that comprise a composite SS-OCNG transmission to a UE under test, according to various other exemplary embodiments of the present disclosure. In this TDD- only example, resources R1-R3 are allocated within a cell bandwidth of 100 MHz for SCS = 120 kHz (66 RBs). In this case, S3 RMC (e.g., PDSCH) is allocated over 24 RBs outside the SMTC window. This scenario is applicable for TDD in frequency bands above 6 GHz, since these bands support SCS of 120 kHz but don’t support SCS of 15 or 30 kHz.

Figure 12 illustrates another exemplary allocation of time-frequency resources for signals S1-S3 that comprise a composite SS-OCNG transmission to a UE under test, according to various other exemplary embodiments of the present disclosure. This example is similar to the one illustrated by Figure 11, except that in this case there are also resource blocks allocated for PDCCH-type 0 (e.g., 20 PRBs over two slots).

In the examples discussed above in relation to Figures 7-12, the SSB is configured in RB 0-19 within the frequency bandwidth of the cell and, accordingly the RMC and SS-OCNG transmissions are adapted in the remaining resources of the cell bandwidth. However, the embodiments are applicable for any location of the SSB within the cell BW, according to the radio node’s ability to adaptively transmit the SS-OCNG and RMC in the resources available after the SSB location is determined. For example, if the SSB is configured in RB 32-51 then RMC can be configured in RB 0-23, and remaining RBs can be configured with SS-OCNG. The number of RBs for SS-OCNG, and RMC location/number of RBs can also depend on the SCS of the PDSCH carrying SS-OCNG and the SCS of the PDCCH/PDSCH of the RMC. For example, the number of RBs for RMCs can be decreased from 24 RBs to 10 RBs if 30 kkHz SCS is used for SSB and 15 kkHz SCS is used for RMC (e.g., PDCCH/PDSCH).

Various examples of SS-OCNG pattern for generating signals Sl, S2, and S3 for a cell by a radio node are shown in Tables 2-5 below and described as follows. In the following examples, the parameter g _PRB is used for setting the relative power level of SS-OCNG signals. For example, SS-OCNG relative power level of the i-th virtual UE is defined as:

g_RKB ,i = (EPRE ratio of PDSCHi to PDSCHi DMRS) /

(EPRE ratio of OCNG to OCNG DMRS),

where EPRE = Energy Per Resource Element. Typically, g _PRB = 0 dB, i.e., PDSCH for SS-

OCNG and PDSCH for RMC have the same power level.

As one example, Table 2 illustrates SS-OCNG Pattern # 2 for FDD in FR1 (SOP.2 FDD FR1) for a 10-MHz FDD cell with SCS of 15 kHz. The four (4) SSBs are transmitted in symbols 2-5 and 8-11, in each of slots 0 and 1, using RBs 0-19 within the cell’s frequency bandwidth. The SMTC window is 2 ms. The PDSCH for RMC is transmitted over RBs 28- 51 outside the SMTC window. The PDSCH for SS-OCNG is transmitted to virtual UEs in all other time-frequency resources.

Table 2.

_

As another example, Table 3 illustrates SS-OCNG Pattern # 1 for TDD in FR1 (SOP.l TDD FR1) for a 10 MHz TDD cell with SCS = 15 kHz. The four (4) SSBs are also transmitted in symbols 2-5 and 8-11, in each of slots 0-1, using RBs 0-19 within the frequency bandwidth of the cell. The SMTC window is 2 ms. The PDSCH for RMC is also transmitted over RBs 28-51 outside the SMTC window, and only in DL slots or DL symbols in slots with guard period. The PDSCH for SS-OCNG is transmitted to virtual UEs in all other DL time- frequency resources. Table 3.

_

As another example, Table 4 illustrates SS-OCNG Pattern # 3 for TDD in FR1 (SOP.3 TDD FR1) used for a 20 MHz TDD cell with SCS = 30 kHz. There are four (4) SSBs transmitted in symbols 2-5, and 8-11, in each of slots 0-1, in RBs 0-19 within the frequency bandwidth of the cell. The SMTC window is 1 ms. PDSCH for RMC is transmitted over RBs 27-50 outside the SMTC window, and only in DL slots or DL symbols in slots with guard period. The PDSCH for SS-OCNG is transmitted to virtual UEs in all other DL time- frequency resources. Table 4.

As another example, Table 5 illustrates SS-OCNG Pattern # 2 for TDD in FR2 (SOP.2 TDD FR2) used for a 100 MHz TDD cell with SCS = 120 kHz. There are 16 SSBs transmitted in total over RBs 0 to 19 within the frequency bandwidth of the cell. Out of these SSBs, eight are transmitted in symbols 4-11, in each of slots 0, 2, 4, and 8. The other eight SSBs are transmitted in symbols 2-9, in each of slots 1, 3, 5, and 7. The SMTC window is 1 ms. The PDSCH for RMC is transmitted over RBs 42-65 outside the SMTC window, and only in DL slots or DL symbols in slots with guard period. The PDSCH for SS-OCNG is transmitted to virtual UEs in all other DL time-frequency resources. Table 5.

Figure 13 is a flow diagram illustrating an exemplary method and/or procedure for generating signals usable for testing operation of a user equipment (UE) within a cell of a wireless communication system, according to various exemplary embodiments of the present disclosure. The exemplary method and/or procedure shown in Figure 13 can be implemented, for example, in radio network node ( e.g ., base station, eNB, eNB, etc. or component thereof) and/or radio network simulator shown in, or described in relation to, other figures herein. Nevertheless, for the sake of brevity, the term“node” used in the following description refers to both types of devices. Although Figure 13 shows blocks in a particular order, this order is exemplary and the operations of the exemplary method and/or procedure can be performed in a different order than shown, and can be combined and/or divided into blocks having different functionality than shown. Optional operations are represented by dashed lines. The exemplary method and/or procedure illustrated can include the operations of block 1310, in which the node can determine a first set of time-frequency resources, within the frequency bandwidth of the cell, usable for transmitting a common signal directed to all UEs operating in the cell. In some embodiments, the common signal can comprise a synchronization signal and physical broadcast channel block (SSB).

In some embodiments, the operations of block 1310 can include the operations of sub block 1312, where the node can select the first set of time-frequency resources based on a synchronization signal and physical broadcast channel block measurement timing configuration (SMTC) window. For example, the SMTC window can represent a configuration of the common signal.

In some embodiments, the operations of block 1310 can include the operations of sub block 1314, where the node can select the first set of time-frequency resources based on one or more of the following characteristics of the cell: frequency bandwidth, starting frequency, center frequency, ending frequency, numerology, and predetermined set of locations for placement of the common signal.

In other embodiments, determining the first set of time-frequency resources can involve retrieving stored configuration information about the common signal currently transmitted in the cell, and/or monitoring characteristic of signals transmitted in time-frequency resources comprising the frequency bandwidth of the cell.

The exemplary method and/or procedure can also include the operations of block 1320, in which the node can, based on the first set of time-frequency resources, determine a third set of time-frequency resources, within the frequency bandwidth of the cell, usable for transmitting a third set of signals directed to the UE ( i.e ., the UE under test). In some embodiments, the third set of signals are usable by the UE under test to perform one or more measurements. In some embodiments, the third set of signals are usable by the UE to perform one or more measurements. In some embodiments, the third set of signals can include one or more of the following: reference measurement channel (RMC), physical downlink shared channel (PDSCH), and physical downlink control channel (PDCCH).

In some embodiments, the operations of block 1320 can include the operations of sub block 1321, where the node can select time-frequency resources that do not overlap with the first set of time-frequency resources. In embodiments where the first set is determined based on an SMTC window ( e.g ., in block 1312), the operations of block 1320 can include the operations of sub-block 1323, where the node can select time-frequency resources that occur outside of the SMTC window.

In some embodiments, the operations of block 1320 can include the operations of sub block 1325, where the node can select time resources that overlap with the time resources of the first set in at least one symbol. Such embodiments can also include the operations of sub block 1327, where the node can select frequency resources that do not overlap with the frequency resources of the first set.

In some embodiments, the operations of block 1320 can include the operations of sub block 1329, where the node can select frequency resources that have a different OFDM sub carrier spacing than the frequency resources of the first set.

The exemplary method and/or procedure can also include the operations of block 1330, in which the node can, based on the first and the third sets of time-frequency resources, determine a second set of time-frequency resources, within the frequency bandwidth of the cell, usable for transmitting a second set of signals directed to one or more virtual UEs. In some embodiments, determining the second set of time-frequency resources can be further based on one or more particular tests to be conducted for the UE. In various embodiments, the second set of signals can include one or more of the following: load generating signals; noise generating signals; virtual UE signals; and synchronization signal OFDM channel noise (SS-OCN).

In some embodiments, the operations of block 1330 can include the operations of sub block 1332, where the node can select at least a subset of all time-frequency resources, within the frequency bandwidth of the cell, that do not include at least one of the first set of time- frequency resources and the third set of time-frequency resources. In some embodiments, selecting at least a subset can be further based on one or more of the following: number of virtual UEs, number of resource blocks (RBs) per virtual UE, antenna transmission mode, and one or more transmission parameters of the second set of signals.

The exemplary method and/or procedure can also include the operations of block 1340, in which the node can transmit the common signal, the second set of signals, and the third set of signals using the determined first, second, and third sets of time-frequency resources. Such transmitted signals can be received by the UE ( i.e ., the UE under test). Although the subject matter described herein can be implemented in any appropriate type of system using any suitable components, the embodiments disclosed herein are described in relation to a wireless network, such as the example wireless network illustrated in Figure 14. For simplicity, the wireless network of Figure 14 only depicts network 1406, network nodes 1460 and l460b, and WDs 1410, l4l0b, and l4l0c. In practice, a wireless network can further include any additional elements suitable to support communication between wireless devices or between a wireless device and another communication device, such as a landline telephone, a service provider, or any other network node or end device. Of the illustrated components, network node 1460 and wireless device (WD) 1410 are depicted with additional detail. The wireless network can provide communication and other types of services to one or more wireless devices to facilitate the wireless devices’ access to and/or use of the services provided by, or via, the wireless network.

The wireless network can comprise and/or interface with any type of communication, telecommunication, data, cellular, and/or radio network or other similar type of system. In some embodiments, the wireless network can be configured to operate according to specific standards or other types of predefined rules or procedures. Thus, particular embodiments of the wireless network can 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 IEEE 802.11 standards; and/or any other appropriate wireless communication standard, such as the Worldwide Interoperability for Microwave Access (WiMax), Bluetooth, Z-Wave and/or ZigBee standards.

Network 1406 can comprise one or more backhaul networks, core networks, IP networks, public switched telephone networks (PSTNs), packet data networks, optical networks, wide-area networks (WANs), local area networks (LANs), wireless local area networks (WLANs), wired networks, wireless networks, metropolitan area networks, and other networks to enable communication between devices.

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

Examples of network nodes include, but are not limited to, access points (APs) ( e.g ., radio access points), base stations (BSs) (e.g., radio base stations, Node Bs, evolved Node Bs (eNBs) and NR NodeBs (gNBs)). Base stations can be categorized based on the amount of coverage they provide (or, stated differently, their transmit power level) and can then also be referred to as femto base stations, pico base stations, micro base stations, or macro base stations. A base station can be a relay node or a relay donor node controlling a relay. A network node can also include one or more (or all) parts of a distributed radio base station such as centralized digital units and/or remote radio units (RRUs), sometimes referred to as Remote Radio Heads (RRHs). Such remote radio units may or may not be integrated with an antenna as an antenna integrated radio. Parts of a distributed radio base station can also be referred to as nodes in a distributed antenna system (DAS).

Further examples of network nodes include multi-standard radio (MSR) equipment such as MSR BSs, network controllers such as 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, a network node can be a virtual network node as described in more detail below.

In Figure 14, network node 1460 includes processing circuitry 1470, device readable medium 1480, interface 1490, auxiliary equipment 1484, power source 1486, power circuitry 1487, and antenna 1462. Although network node 1460 illustrated in the example wireless network of Figure 14 can represent a device that includes the illustrated combination of hardware components, other embodiments can comprise network nodes with different combinations of components. It is to be understood that a network node comprises any suitable combination of hardware and/or software needed to perform the tasks, features, functions and methods and/or procedures disclosed herein. Moreover, while the components of network node 1460 are depicted as single boxes located within a larger box, or nested within multiple boxes, in practice, a network node can comprise multiple different physical components that make up a single illustrated component ( e.g ., device readable medium 1480 can comprise multiple separate hard drives as well as multiple RAM modules).

Similarly, network node 1460 can be composed of multiple physically separate components (e.g., a NodeB component and a RNC component, or a BTS component and a BSC component, etc.), which can each have their own respective components. In certain scenarios in which network node 1460 comprises multiple separate components (e.g., BTS and BSC components), one or more of the separate components can be shared among several network nodes. For example, a single RNC can control multiple NodeB’s. In such a scenario, each unique NodeB and RNC pair, can in some instances be considered a single separate network node. In some embodiments, network node 1460 can be configured to support multiple radio access technologies (RATs). In such embodiments, some components can be duplicated (e.g., separate device readable medium 1480 for the different RATs) and some components can be reused (e.g., the same antenna 1462 can be shared by the RATs). Network node 1460 can also include multiple sets of the various illustrated components for different wireless technologies integrated into network node 1460, such as, for example, GSM, WCDMA, LTE, NR, WiFi, or Bluetooth wireless technologies. These wireless technologies can be integrated into the same or different chip or set of chips and other components within network node 1460.

Processing circuitry 1470 can be configured to perform any determining, calculating, or similar operations (e.g., certain obtaining operations) described herein as being provided by a network node. These operations performed by processing circuitry 1470 can include processing information obtained by processing circuitry 1470 by, for example, converting the obtained information into other information, comparing the obtained information or converted information to information stored in the network node, and/or performing one or more operations based on the obtained information or converted information, and as a result of said processing making a determination.

Processing circuitry 1470 can comprise a combination of one or more of 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, either alone or in conjunction with other network node 1460 components, such as device readable medium 1480, network node 1460 functionality. For example, processing circuitry 1470 can execute instructions stored in device readable medium 1480 or in memory within processing circuitry 1470. Such functionality can include providing any of the various wireless features, functions, or benefits discussed herein. In some embodiments, processing circuitry 1470 can include a system on a chip (SOC).

In some embodiments, processing circuitry 1470 can include one or more of radio frequency (RF) transceiver circuitry 1472 and baseband processing circuitry 1474. In some embodiments, radio frequency (RF) transceiver circuitry 1472 and baseband processing circuitry 1474 can be on separate chips (or sets of chips), boards, or units, such as radio units and digital units. In alternative embodiments, part or all of RF transceiver circuitry 1472 and baseband processing circuitry 1474 can be on the same chip or set of chips, boards, or units

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 can be performed by processing circuitry 1470 executing instructions stored on device readable medium 1480 or memory within processing circuitry 1470. In alternative embodiments, some or all of the functionality can be provided by processing circuitry 1470 without executing instructions stored on a separate or discrete device readable medium, such as in a hard-wired manner. In any of those embodiments, whether executing instructions stored on a device readable storage medium or not, processing circuitry 1470 can be configured to perform the described functionality. The benefits provided by such functionality are not limited to processing circuitry 1470 alone or to other components of network node 1460, but are enjoyed by network node 1460 as a whole, and/or by end users and the wireless network generally.

Device readable medium 1480 can comprise any form of volatile or non-volatile computer readable memory including, without limitation, persistent storage, solid-state memory, remotely mounted memory, magnetic media, optical media, random access memory (RAM), read-only memory (ROM), mass storage media (for example, a hard disk), removable storage media (for example, a flash drive, a Compact Disk (CD) or a Digital Video Disk (DVD)), and/or any other volatile or non-volatile, non-transitory device readable and/or computer-executable memory devices that store information, data, and/or instructions that can be used by processing circuitry 1470. Device readable medium 1480 can store any suitable instructions, data or information, including a computer program, software, an application including one or more of logic, rules, code, tables, etc. and/or other instructions capable of being executed by processing circuitry 1470 and, utilized by network node 1460. Device readable medium 1480 can be used to store any calculations made by processing circuitry 1470 and/or any data received via interface 1490. In some embodiments, processing circuitry 1470 and device readable medium 1480 can be considered to be integrated.

Interface 1490 is used in the wired or wireless communication of signalling and/or data between network node 1460, network 1406, and/or WDs 1410. As illustrated, interface 1490 comprises port(s)/terminal(s) 1494 to send and receive data, for example to and from network 1406 over a wired connection. Interface 1490 also includes radio front end circuitry 1492 that can be coupled to, or in certain embodiments a part of, antenna 1462. Radio front end circuitry 1492 comprises filters 1498 and amplifiers 1496. Radio front end circuitry 1492 can be connected to antenna 1462 and processing circuitry 1470. Radio front end circuitry can be configured to condition signals communicated between antenna 1462 and processing circuitry 1470. Radio front end circuitry 1492 can receive digital data that is to be sent out to other network nodes or WDs via a wireless connection. Radio front end circuitry 1492 can convert the digital data into a radio signal having the appropriate channel and bandwidth parameters using a combination of filters 1498 and/or amplifiers 1496. The radio signal can then be transmitted via antenna 1462. Similarly, when receiving data, antenna 1462 can collect radio signals which are then converted into digital data by radio front end circuitry 1492. The digital data can be passed to processing circuitry 1470. In other embodiments, the interface can comprise different components and/or different combinations of components.

In certain alternative embodiments, network node 1460 may not include separate radio front end circuitry 1492, instead, processing circuitry 1470 can comprise radio front end circuitry and can be connected to antenna 1462 without separate radio front end circuitry 1492. Similarly, in some embodiments, all or some of RF transceiver circuitry 1472 can be considered a part of interface 1490. In still other embodiments, interface 1490 can include one or more ports or terminals 1494, radio front end circuitry 1492, and RF transceiver circuitry 1472, as part of a radio unit (not shown), and interface 1490 can communicate with baseband processing circuitry 1474, which is part of a digital unit (not shown).

Antenna 1462 can include one or more antennas, or antenna arrays, configured to send and/or receive wireless signals. Antenna 1462 can be coupled to radio front end circuitry 1490 and can be any type of antenna capable of transmitting and receiving data and/or signals wirelessly. In some embodiments, antenna 1462 can comprise one or more omni-directional, sector or panel antennas operable to transmit/receive radio signals between, for example, 2 GHz and 66 GHz. An omni-directional antenna can be used to transmit/receive radio signals in any direction, a sector antenna can be used to transmit/receive radio signals from devices within a particular area, and a panel antenna can be a line of sight antenna used to transmit/receive radio signals in a relatively straight line. In some instances, the use of more than one antenna can be referred to as MIMO. In certain embodiments, antenna 1462 can be separate from network node 1460 and can be connectable to network node 1460 through an interface or port.

Antenna 1462, interface 1490, and/or processing circuitry 1470 can 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 can be received from a wireless device, another network node and/or any other network equipment. Similarly, antenna 1462, interface 1490, and/or processing circuitry 1470 can be configured to perform any transmitting operations described herein as being performed by a network node. Any information, data and/or signals can be transmitted to a wireless device, another network node and/or any other network equipment.

Power circuitry 1487 can comprise, or be coupled to, power management circuitry and can be configured to supply the components of network node 1460 with power for performing the functionality described herein. Power circuitry 1487 can receive power from power source 1486. Power source 1486 and/or power circuitry 1487 can be configured to provide power to the various components of network node 1460 in a form suitable for the respective components ( e.g ., at a voltage and current level needed for each respective component). Power source 1486 can either be included in, or external to, power circuitry 1487 and/or network node 1460. For example, network node 1460 can be connectable to an external power source (e.g., an electricity outlet) via an input circuitry or interface such as an electrical cable, whereby the external power source supplies power to power circuitry 1487. As a further example, power source 1486 can comprise a source of power in the form of a battery or battery pack which is connected to, or integrated in, power circuitry 1487. The battery can provide backup power should the external power source fail. Other types of power sources, such as photovoltaic devices, can also be used.

Alternative embodiments of network node 1460 can include additional components beyond those shown in Figure 14 that can be responsible for providing certain aspects of the network node’s functionality, including any of the functionality described herein and/or any functionality necessary to support the subject matter described herein. For example, network node 1460 can include user interface equipment to allow and/or facilitate input of information into network node 1460 and to allow and/or facilitate output of information from network node 1460. This can allow and/or facilitate a user to perform diagnostic, maintenance, repair, and other administrative functions for network node 1460.

In some embodiments, a wireless device (WD, e.g., WD 1410) can be configured to transmit and/or receive information without direct human interaction. For instance, a WD can be designed to transmit information to a network on a predetermined schedule, when triggered by an internal or external event, or in response to requests from the network. Examples of a WD include, but are not limited to, a smart phone, a mobile phone, a cell phone, a voice over IP (VoIP) phone, a wireless local loop phone, a desktop computer, a personal digital assistant (PDA), a wireless cameras, a gaming console or device, a music storage device, a playback appliance, a wearable terminal device, a wireless endpoint, a mobile station, a tablet, a laptop, a laptop-embedded equipment (LEE), a laptop-mounted equipment (LME), a smart device, a wireless customer-premise equipment (CPE) a vehicle-mounted wireless terminal device, etc.

A WD can support device-to-device (D2D) communication, for example by implementing a 3GPP standard for sidelink communication, vehicle-to-vehicle (V2V), vehicle- to-infrastructure (V2I), vehicle-to-everything (V2X) and can in this case be referred to as a D2D communication device. As yet another specific example, in an Internet of Things (IoT) scenario, a WD can represent a machine or other device that performs monitoring and/or measurements, and transmits the results of such monitoring and/or measurements to another WD and/or a network node. The WD can in this case be a machine-to-machine (M2M) device, which can in a 3GPP context be referred to as an MTC device. As one particular example, the WD can be a UE implementing the 3GPP narrow band internet of things (NB-IoT) standard. Particular examples of such machines or devices are sensors, metering devices such as power meters, industrial machinery, or home or personal appliances (e.g., refrigerators, televisions, etc.) personal wearables (e.g., watches, fitness trackers, etc.). In other scenarios, a WD can represent a vehicle or other equipment that is capable of monitoring and/or reporting on its operational status or other functions associated with its operation. A WD as described above can represent the endpoint of a wireless connection, in which case the device can be referred to as a wireless terminal. Furthermore, a WD as described above can be mobile, in which case it can also be referred to as a mobile device or a mobile terminal.

As illustrated, wireless device 1410 includes antenna 1411, interface 1414, processing circuitry 1420, device readable medium 1430, user interface equipment 1432, auxiliary equipment 1434, power source 1436 and power circuitry 1437. WD 1410 can include multiple sets of one or more of the illustrated components for different wireless technologies supported by WD 1410, such as, for example, GSM, WCDMA, LTE, NR, WiFi, WiMAX, or Bluetooth wireless technologies, just to mention a few. These wireless technologies can be integrated into the same or different chips or set of chips as other components within WD 1410.

Antenna 1411 can include one or more antennas or antenna arrays, configured to send and/or receive wireless signals, and is connected to interface 1414. In certain alternative embodiments, antenna 1411 can be separate from WD 1410 and be connectable to WD 1410 through an interface or port. Antenna 1411, interface 1414, and/or processing circuitry 1420 can be configured to perform any receiving or transmitting operations described herein as being performed by a WD. Any information, data and/or signals can be received from a network node and/or another WD. In some embodiments, radio front end circuitry and/or antenna 1411 can be considered an interface.

As illustrated, interface 1414 comprises radio front end circuitry 1412 and antenna 1411. Radio front end circuitry 1412 comprise one or more filters 1418 and amplifiers 1416. Radio front end circuitry 1414 is connected to antenna 1411 and processing circuitry 1420, and can be configured to condition signals communicated between antenna 1411 and processing circuitry 1420. Radio front end circuitry 1412 can be coupled to or a part of antenna 1411. In some embodiments, WD 1410 may not include separate radio front end circuitry 1412; rather, processing circuitry 1420 can comprise radio front end circuitry and can be connected to antenna 1411. Similarly, in some embodiments, some or all of RF transceiver circuitry 1422 can be considered a part of interface 1414. Radio front end circuitry 1412 can receive digital data that is to be sent out to other network nodes or WDs via a wireless connection. Radio front end circuitry 1412 can convert the digital data into a radio signal having the appropriate channel and bandwidth parameters using a combination of filters 1418 and/or amplifiers 1416. The radio signal can then be transmitted via antenna 1411. Similarly, when receiving data, antenna 1411 can collect radio signals which are then converted into digital data by radio front end circuitry 1412. The digital data can be passed to processing circuitry 1420. In other embodiments, the interface can comprise different components and/or different combinations of components.

Processing circuitry 1420 can comprise a combination of one or more of 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, either alone or in conjunction with other WD 1410 components, such as device readable medium 1430, WD 1410 functionality. Such functionality can include providing any of the various wireless features or benefits discussed herein. For example, processing circuitry 1420 can execute instructions stored in device readable medium 1430 or in memory within processing circuitry 1420 to provide the functionality disclosed herein.

As illustrated, processing circuitry 1420 includes one or more of RF transceiver circuitry 1422, baseband processing circuitry 1424, and application processing circuitry 1426. In other embodiments, the processing circuitry can comprise different components and/or different combinations of components. In certain embodiments processing circuitry 1420 of WD 1410 can comprise a SOC. In some embodiments, RF transceiver circuitry 1422, baseband processing circuitry 1424, and application processing circuitry 1426 can be on separate chips or sets of chips. In alternative embodiments, part or all of baseband processing circuitry 1424 and application processing circuitry 1426 can be combined into one chip or set of chips, and RF transceiver circuitry 1422 can be on a separate chip or set of chips. In still alternative embodiments, part or all of RF transceiver circuitry 1422 and baseband processing circuitry 1424 can be on the same chip or set of chips, and application processing circuitry 1426 can be on a separate chip or set of chips. In yet other alternative embodiments, part or all of RF transceiver circuitry 1422, baseband processing circuitry 1424, and application processing circuitry 1426 can be combined in the same chip or set of chips. In some embodiments, RF transceiver circuitry 1422 can be a part of interface 1414. RF transceiver circuitry 1422 can condition RF signals for processing circuitry 1420.

In certain embodiments, some or all of the functionality described herein as being performed by a WD can be provided by processing circuitry 1420 executing instructions stored on device readable medium 1430, which in certain embodiments can be a computer-readable storage medium. In alternative embodiments, some or all of the functionality can be provided by processing circuitry 1420 without executing instructions stored on a separate or discrete device readable storage medium, such as in a hard-wired manner. In any of those particular embodiments, whether executing instructions stored on a device readable storage medium or not, processing circuitry 1420 can be configured to perform the described functionality. The benefits provided by such functionality are not limited to processing circuitry 1420 alone or to other components of WD 1410, but are enjoyed by WD 1410 as a whole, and/or by end users and the wireless network generally.

Processing circuitry 1420 can be configured to perform any determining, calculating, or similar operations ( e.g ., certain obtaining operations) described herein as being performed by a WD. These operations, as performed by processing circuitry 1420, can include processing information obtained by processing circuitry 1420 by, for example, converting the obtained information into other information, comparing the obtained information or converted information to information stored by WD 1410, and/or performing one or more operations based on the obtained information or converted information, and as a result of said processing making a determination.

Device readable medium 1430 can be operable to store a computer program, software, an application including one or more of logic, rules, code, tables, etc. and/or other instructions capable of being executed by processing circuitry 1420. Device readable medium 1430 can include computer memory (e.g., Random Access Memory (RAM) or Read Only Memory (ROM)), mass storage media (e.g., a hard disk), removable storage media (e.g., a Compact Disk (CD) or a Digital Video Disk (DVD)), and/or any other volatile or non-volatile, non-transitory device readable and/or computer executable memory devices that store information, data, and/or instructions that can be used by processing circuitry 1420. In some embodiments, processing circuitry 1420 and device readable medium 1430 can be considered to be integrated.

User interface equipment 1432 can include components that allow and/or facilitate a human user to interact with WD 1410. Such interaction can be of many forms, such as visual, audial, tactile, etc. User interface equipment 1432 can be operable to produce output to the user and to allow and/or facilitate the user to provide input to WD 1410. The type of interaction can vary depending on the type of user interface equipment 1432 installed in WD 1410. For example, if WD 1410 is a smart phone, the interaction can be via a touch screen; if WD 1410 is a smart meter, the interaction can be through a screen that provides usage ( e.g ., the number of gallons used) or a speaker that provides an audible alert (e.g., if smoke is detected). User interface equipment 1432 can include input interfaces, devices and circuits, and output interfaces, devices and circuits. User interface equipment 1432 can be configured to allow and/or facilitate input of information into WD 1410, and is connected to processing circuitry 1420 to allow and/or facilitate processing circuitry 1420 to process the input information. User interface equipment 1432 can include, for example, a microphone, a proximity or other sensor, keys/buttons, a touch display, one or more cameras, a USB port, or other input circuitry. User interface equipment 1432 is also configured to allow and/or facilitate output of information from WD 1410, and to allow and/or facilitate processing circuitry 1420 to output information from WD 1410. User interface equipment 1432 can include, for example, a speaker, a display, vibrating circuitry, a USB port, a headphone interface, or other output circuitry. Using one or more input and output interfaces, devices, and circuits, of user interface equipment 1432, WD 1410 can communicate with end users and/or the wireless network, and allow and/or facilitate them to benefit from the functionality described herein.

Auxiliary equipment 1434 is operable to provide more specific functionality which may not be generally performed by WDs. This can comprise specialized sensors for doing measurements for various purposes, interfaces for additional types of communication such as wired communications etc. The inclusion and type of components of auxiliary equipment 1434 can vary depending on the embodiment and/or scenario.

Power source 1436 can, in some embodiments, be in the form of a battery or battery pack. Other types of power sources, such as an external power source (e.g., an electricity outlet), photovoltaic devices or power cells, can also be used. WD 1410 can further comprise power circuitry 1437 for delivering power from power source 1436 to the various parts of WD 1410 which need power from power source 1436 to carry out any functionality described or indicated herein. Power circuitry 1437 can in certain embodiments comprise power management circuitry. Power circuitry 1437 can additionally or alternatively be operable to receive power from an external power source; in which case WD 1410 can be connectable to the external power source (such as an electricity outlet) via input circuitry or an interface such as an electrical power cable. Power circuitry 1437 can also in certain embodiments be operable to deliver power from an external power source to power source 1436. This can be, for example, for the charging of power source 1436. Power circuitry 1437 can perform any converting or other modification to the power from power source 1436 to make it suitable for supply to the respective components of WD 1410.

Figure 15 illustrates one embodiment of a UE in accordance with various aspects described herein. As used herein, a user equipment or UE may not necessarily have a user in the sense of a human user who owns and/or operates the relevant device. Instead, a UE can represent a device that is intended for sale to, or operation by, a human user but which may not, or which may not initially, be associated with a specific human user ( e.g ., a smart sprinkler controller). Alternatively, a UE can represent a device that is not intended for sale to, or operation by, an end user but which can be associated with or operated for the benefit of a user (e.g., a smart power meter). UE 15200 can be any UE identified by the 3^rd Generation Partnership Project (3GPP), including a NB-IoT UE, a machine type communication (MTC) UE, and/or an enhanced MTC (eMTC) UE. UE 1500, as illustrated in Figure 15, is one example of a WD configured for communication in accordance with one or more communication standards promulgated by the 3^rd Generation Partnership Project (3GPP), such as 3GPP’s GSM, UMTS, LTE, and/or 5G standards. As mentioned previously, the term WD and UE can be used interchangeable. Accordingly, although Figure 15 is a UE, the components discussed herein are equally applicable to a WD, and vice-versa.

In Figure 15, UE 1500 includes processing circuitry 1501 that is operatively coupled to input/output interface 1505, radio frequency (RF) interface 1509, network connection interface 1511, memory 1515 including random access memory (RAM) 1517, read-only memory (ROM) 1519, and storage medium 1521 or the like, communication subsystem 1531, power source 1533, and/or any other component, or any combination thereof. Storage medium 1521 includes operating system 1523, application program 1525, and data 1527. In other embodiments, storage medium 1521 can include other similar types of information. Certain UEs can utilize all of the components shown in Figure 15, or only a subset of the components. The level of integration between the components can vary from one UE to another UE. Further, certain UEs can contain multiple instances of a component, such as multiple processors, memories, transceivers, transmitters, receivers, etc.

In Figure 15, processing circuitry 1501 can be configured to process computer instructions and data. Processing circuitry 1501 can be configured to implement any sequential state machine operative to execute machine instructions stored as machine-readable computer programs in the memory, such as one or more hardware-implemented state machines ( e.g ., in discrete logic, FPGA, ASIC, etc.); programmable logic together with appropriate firmware; one or more stored program, general-purpose processors, such as a microprocessor or Digital Signal Processor (DSP), together with appropriate software; or any combination of the above. For example, the processing circuitry 1501 can include two central processing units (CPUs). Data can be information in a form suitable for use by a computer.

In the depicted embodiment, input/output interface 1505 can be configured to provide a communication interface to an input device, output device, or input and output device. UE 1500 can be configured to use an output device via input/output interface 1505. An output device can use the same type of interface port as an input device. For example, a USB port can be used to provide input to and output from UE 1500. The output device can be a speaker, a sound card, a video card, a display, a monitor, a printer, an actuator, an emitter, a smartcard, another output device, or any combination thereof. UE 1500 can be configured to use an input device via input/output interface 1505 to allow and/or facilitate a user to capture information into UE 1500. The input device can include a touch-sensitive or presence- sensitive display, a camera (e.g., a digital camera, a digital video camera, a web camera, etc.), a microphone, a sensor, a mouse, a trackball, a directional pad, a trackpad, a scroll wheel, a smartcard, and the like. The presence- sensitive display can include a capacitive or resistive touch sensor to sense input from a user. A sensor can be, for instance, an accelerometer, a gyroscope, a tilt sensor, a force sensor, a magnetometer, an optical sensor, a proximity sensor, another like sensor, or any combination thereof. For example, the input device can be an accelerometer, a magnetometer, a digital camera, a microphone, and an optical sensor.

In Figure 15, RF interface 1509 can be configured to provide a communication interface to RF components such as a transmitter, a receiver, and an antenna. Network connection interface 1511 can be configured to provide a communication interface to network l543a. Network l543a can encompass wired and/or wireless networks such as a local-area network (LAN), a wide-area network (WAN), a computer network, a wireless network, a telecommunications network, another like network or any combination thereof. For example, network l543a can comprise a Wi-Fi network. Network connection interface 1511 can be configured to include a receiver and a transmitter interface used to communicate with one or more other devices over a communication network according to one or more communication protocols, such as Ethernet, TCP/IP, SONET, ATM, or the like. Network connection interface 1511 can implement receiver and transmitter functionality appropriate to the communication network links ( e.g ., optical, electrical, and the like). The transmitter and receiver functions can share circuit components, software or firmware, or alternatively can be implemented separately.

RAM 1517 can be configured to interface via bus 1502 to processing circuitry 1501 to provide storage or caching of data or computer instructions during the execution of software programs such as the operating system, application programs, and device drivers. ROM 1519 can be configured to provide computer instructions or data to processing circuitry 1501. For example, ROM 1519 can be configured to store invariant low-level system code or data for basic system functions such as basic input and output (I/O), startup, or reception of keystrokes from a keyboard that are stored in a non-volatile memory. Storage medium 1521 can 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), magnetic disks, optical disks, floppy disks, hard disks, removable cartridges, or flash drives. In one example, storage medium 1521 can be configured to include operating system 1523, application program 1525 such as a web browser application, a widget or gadget engine or another application, and data file 1527. Storage medium 1521 can store, for use by UE 1500, any of a variety of various operating systems or combinations of operating systems.

Storage medium 1521 can be configured to include a number of physical drive units, such as redundant array of independent disks (RAID), floppy disk drive, flash memory, USB flash drive, external hard disk drive, thumb drive, pen drive, key drive, high-density digital versatile disc (HD-DVD) optical disc drive, internal hard disk drive, Blu-Ray optical disc drive, holographic digital data storage (HDDS) optical disc drive, external mini-dual in-line memory module (DIMM), synchronous dynamic random access memory (SDRAM), external micro- DIMM SDRAM, smartcard memory such as a subscriber identity module or a removable user identity (SIM/RUIM) module, other memory, or any combination thereof. Storage medium 1521 can allow and/or facilitate UE 1500 to access computer-executable instructions, application programs or the like, stored on transitory or non-transitory memory media, to off load data, or to upload data. An article of manufacture, such as one utilizing a communication system can be tangibly embodied in storage medium 1521, which can comprise a device readable medium.

In Figure 15, processing circuitry 1501 can be configured to communicate with network l543b using communication subsystem 1531. Network l543a and network l543b can be the same network or networks or different network or networks. Communication subsystem 1531 can be configured to include one or more transceivers used to communicate with network l543b. For example, communication subsystem 1531 can be configured to include one or more transceivers used to communicate with one or more remote transceivers of another device capable of wireless communication such as another WD, UE, or base station of a radio access network (RAN) according to one or more communication protocols, such as IEEE 802.15, CDMA, WCDMA, GSM, LTE, UTRAN, WiMax, or the like. Each transceiver can include transmitter 1533 and/or receiver 1535 to implement transmitter or receiver functionality, respectively, appropriate to the RAN links ( e.g ., frequency allocations and the like). Further, transmitter 1533 and receiver 1535 of each transceiver can share circuit components, software or firmware, or alternatively can be implemented separately.

In the illustrated embodiment, the communication functions of communication subsystem 1531 can include data communication, voice communication, multimedia communication, short-range communications such as Bluetooth, near-field communication, location-based communication such as the use of the global positioning system (GPS) to determine a location, another like communication function, or any combination thereof. For example, communication subsystem 1531 can include cellular communication, Wi-Fi communication, Bluetooth communication, and GPS communication. Network l543b can encompass wired and/or wireless networks such as a local-area network (LAN), a wide-area network (WAN), a computer network, a wireless network, a telecommunications network, another like network or any combination thereof. For example, network l543b can be a cellular network, a Wi-Fi network, and/or a near-field network. Power source 1513 can be configured to provide alternating current (AC) or direct current (DC) power to components of UE 1500.

The features, benefits and/or functions described herein can be implemented in one of the components of UE 1500 or partitioned across multiple components of UE 1500. Further, the features, benefits, and/or functions described herein can be implemented in any combination of hardware, software or firmware. In one example, communication subsystem 1531 can be configured to include any of the components described herein. Further, processing circuitry 1501 can be configured to communicate with any of such components over bus 1502. In another example, any of such components can be represented by program instructions stored in memory that when executed by processing circuitry 1501 perform the corresponding functions described herein. In another example, the functionality of any of such components can be partitioned between processing circuitry 1501 and communication subsystem 1531. In another example, the non-computationally intensive functions of any of such components can be implemented in software or firmware and the computationally intensive functions can be implemented in hardware.

Figure 16 is a schematic block diagram illustrating a virtualization environment 1600 in which functions implemented by some embodiments can be virtualized. In the present context, virtualizing means creating virtual versions of apparatuses or devices which can include virtualizing hardware platforms, storage devices and networking resources. As used herein, virtualization can be applied to a node (e.g., a virtualized base station or a virtualized radio access node) or to a device (e.g., a UE, a wireless device or any other type of communication device) or components thereof and relates to an implementation in which at least a portion of the functionality is implemented as one or more virtual components (e.g., via 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 can be implemented as virtual components executed by one or more virtual machines implemented in one or more virtual environments 1600 hosted by one or more of hardware nodes 1630. Further, in embodiments in which the virtual node is not a radio access node or does not require radio connectivity (e.g., a core network node), then the network node can be entirely virtualized.

The functions can be implemented by one or more applications 1620 (which can alternatively be called software instances, virtual appliances, network functions, virtual nodes, virtual network functions, etc.) operative to implement some of the features, functions, and/or benefits of some of the embodiments disclosed herein. Applications 1620 are run in virtualization environment 1600 which provides hardware 1630 comprising processing circuitry 1660 and memory 1690. Memory 1690 contains instructions 1695 executable by processing circuitry 1660 whereby application 1620 is operative to provide one or more of the features, benefits, and/or functions disclosed herein.

Virtualization environment 1600, comprises general-purpose or special-purpose network hardware devices 1630 comprising a set of one or more processors or processing circuitry 1660, which can be commercial off-the-shelf (COTS) processors, dedicated Application Specific Integrated Circuits (ASICs), or any other type of processing circuitry including digital or analog hardware components or special purpose processors. Each hardware device can comprise memory 1690-1 which can be non-persistent memory for temporarily storing instructions 1695 or software executed by processing circuitry 1660. Each hardware device can comprise one or more network interface controllers (NICs) 1670, also known as network interface cards, which include physical network interface 1680. Each hardware device can also include non-transitory, persistent, machine-readable storage media 1690-2 having stored therein software 1695 and/or instructions executable by processing circuitry 1660. Software 1695 can include any type of software including software for instantiating one or more virtualization layers 1650 (also referred to as hypervisors), software to execute virtual machines 1640 as well as software allowing it to execute functions, features and/or benefits described in relation with some embodiments described herein.

Virtual machines 1640, comprise virtual processing, virtual memory, virtual networking or interface and virtual storage, and can be run by a corresponding virtualization layer 1650 or hypervisor. Different embodiments of the instance of virtual appliance 1620 can be implemented on one or more of virtual machines 1640, and the implementations can be made in different ways.

During operation, processing circuitry 1660 executes software 1695 to instantiate the hypervisor or virtualization layer 1650, which can sometimes be referred to as a virtual machine monitor (VMM). Virtualization layer 1650 can present a virtual operating platform that appears like networking hardware to virtual machine 1640.

As shown in Figure 16, hardware 1630 can be a standalone network node with generic or specific components. Hardware 1630 can comprise antenna 16225 and can implement some functions via virtualization. Alternatively, hardware 1630 can be part of a larger cluster of hardware (<?.#., such as in a data center or customer premise equipment (CPE)) where many hardware nodes work together and are managed via management and orchestration (MANO) 16100, which, among others, oversees lifecycle management of applications 1620.

Virtualization of the hardware is in some contexts referred to as network function virtualization (NFV). NFV can be used to consolidate many network equipment types onto industry standard high volume server hardware, physical switches, and physical storage, which can be located in data centers, and customer premise equipment.

In the context of NFV, virtual machine 1640 can be a software implementation of a physical machine that runs programs as if they were executing on a physical, non- virtualized machine. Each of virtual machines 1640, and that part of hardware 1630 that executes that virtual machine, be it hardware dedicated to that virtual machine and/or hardware shared by that virtual machine with others of the virtual machines 1640, forms a separate virtual network elements (VNE).

Still in the context of NFV, Virtual Network Function (VNF) is responsible for handling specific network functions that run in one or more virtual machines 1640 on top of hardware networking infrastructure 1630 and corresponds to application 1620 in Figure 16.

In some embodiments, one or more radio units 16200 that each include one or more transmitters 16220 and one or more receivers 16210 can be coupled to one or more antennas 16225. Radio units 16200 can communicate directly with hardware nodes 1630 via one or more appropriate network interfaces and can be used in combination with the virtual components to provide a virtual node with radio capabilities, such as a radio access node or a base station.

In some embodiments, some signalling can be effected with the use of control system 16230 which can alternatively be used for communication between the hardware nodes 1630 and radio units 16200.

With reference to Figure 17, in accordance with an embodiment, a communication system includes telecommunication network 1710, such as a 3GPP-type cellular network, which comprises access network 1711, such as a radio access network, and core network 1714. Access network 1711 comprises a plurality of base stations l7l2a, l7l2b, l7l2c, such as NBs, eNBs, gNBs or other types of wireless access points, each defining a corresponding coverage area l7l3a, l7l3b, l7l3c. Each base station l7l2a, l7l2b, l7l2c is connectable to core network 1714 over a wired or wireless connection 1715. A first UE 1791 located in coverage area !7l3c can be configured to wirelessly connect to, or be paged by, the corresponding base station l7l2c. A second UE 1792 in coverage area l7l3a is wirelessly connectable to the corresponding base station l7l2a. While a plurality of UEs 1791, 1792 are illustrated in this example, the disclosed embodiments are equally applicable to a situation where a sole UE is in the coverage area or where a sole UE is connecting to the

Telecommunication network 1710 is itself connected to host computer 1730, which can be embodied in the hardware and/or software of a standalone server, a cloud-implemented server, a distributed server or as processing resources in a server farm. Host computer 1730 can be under the ownership or control of a service provider, or can be operated by the service provider or on behalf of the service provider. Connections 1721 and 1722 between telecommunication network 1710 and host computer 1730 can extend directly from core network 1714 to host computer 1730 or can go via an optional intermediate network 1720. Intermediate network 1720 can be one of, or a combination of more than one of, a public, private or hosted network; intermediate network 1720, if any, can be a backbone network or the Internet; in particular, intermediate network 1720 can comprise two or more sub-networks (not shown).

The communication system of Figure 17 as a whole enables connectivity between the connected UEs 1791, 1792 and host computer 1730. The connectivity can be described as an over-the-top (OTT) connection 1750. Host computer 1730 and the connected UEs 1791, 1792 are configured to communicate data and/or signaling via OTT connection 1750, using access network 1711, core network 1714, any intermediate network 1720 and possible further infrastructure (not shown) as intermediaries. OTT connection 1750 can be transparent in the sense that the participating communication devices through which OTT connection 1750 passes are unaware of routing of uplink and downlink communications. For example, base station 1712 may not or need not be informed about the past routing of an incoming downlink communication with data originating from host computer 1730 to be forwarded ( e.g ., handed over) to a connected UE 1791. Similarly, base station 1712 need not be aware of the future routing of an outgoing uplink communication originating from the UE 1791 towards the host computer 1730.

Figure 18 is a block diagram of an exemplary radio network simulator, according to various exemplary embodiments of the present disclosure. Radio network simulator 1860 includes processing circuitry 1870, device readable medium 1880, communication interface 1890, auxiliary equipment 1884, power source 1886, power circuitry 1887, and external connector 1862. Although radio network simulator 1860 illustrated in Figure 18 can represent a device that includes the illustrated combination of hardware components, other embodiments can comprise simulators with different combinations of components. It is to be understood that a radio network simulator comprises any suitable combination of hardware and/or software needed to perform the tasks, features, functions and methods and/or procedures disclosed herein. Moreover, while the components of radio network simulator 1860 are depicted as single boxes located within a larger box, or nested within multiple boxes, a radio network simulator can comprise multiple different physical components that make up a single illustrated component ( e.g ., device readable medium 1880 can comprise multiple separate hard drives as well as multiple RAM modules). Similarly, radio network simulator 1860 can be composed of multiple physically separate components (e.g., radio component, processing component, etc.), each of which can each have their own respective components.

Given that radio network simulator 1860 is intended to simulate the operation of a radio network, its functionality needed to achieve this goal can be comparable to functionality found in an actual radio network node. As such, the individual components shown in Figure 18 can have functionality similar to comparable components of exemplary network node 1460 shown in Figure 14. As such, the above detailed description of the functionality of the components of exemplary network node 1460 applies equally to the functionality of the components of exemplary radio network simulator 1860 shown in Figure 18. One exception, however, is that antenna 1462 can be replaced by external connector 1862, by which radio network simulator 1860 can connect to a UE under test, such as UE 1810. However, it should be understood that this connection to the UE can also be indirect, such as by attaching an appropriate antenna to external connector 1862.

Any appropriate operations, methods, features, functions, or benefits disclosed herein may be performed through one or more functional units or modules of one or more virtual apparatuses. Each virtual apparatus may comprise a number of these functional units. These functional units may be implemented via processing circuitry, which may include one or more microprocessor or microcontrollers, as well as other digital hardware, which may include Digital Signal Processor (DSPs), special-purpose 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, etc. Program code stored in memory includes program instructions for executing one or more telecommunications and/or data communications protocols as well as instructions for carrying out one or more of the techniques described herein. In some implementations, the processing circuitry may be used to cause the respective functional unit to perform corresponding functions according one or more embodiments of the present disclosure.

Example embodiments of the techniques and apparatus described herein include, but are not limited to, the following enumerated examples:

1. A method for generating signals usable for testing operation of a user equipment (UE) within a cell of a wireless communication system, the method comprising:

determining a first set of time-frequency resources, within the frequency bandwidth of the cell, used for transmitting a common signal directed to all UEs operating in the cell;

based on the first set of time-frequency resources, determining a third set of time- frequency resources, within the frequency bandwidth of the cell, that are usable for transmitting a third set of signals directed to a UE under test; based on the first and the third sets of time-frequency resources, determining a second set of time-frequency resources, within the frequency bandwidth of the cell, that are usable for transmitting a second set of signals directed to one or more virtual UEs; and

transmitting, to the UE under test, a combined signal comprising the common signal, the second set of signals, and the third set of signals.

2. The method of embodiment 1, wherein determining the third set of time-frequency resources comprises selecting time-frequency resources that do not overlap with the first set of time-frequency resources.

3. The method of any of embodiments 1-2, wherein: the common signal comprises a synchronization signal and physical broadcast channel block (SSB);

the first set of time-frequency resources comprises an SSB measurement timing

configuration (SMTC) window; and

determining the third set of time-frequency resources comprises selecting time- frequency resources that occur outside of the SMTC window.

4. The method of embodiment 1, wherein the third set of time-frequency resources are determined such that:

time resources comprising the third set and time resources comprising the first set overlap in at least one symbol; and

frequency resources comprising the third set and frequency resources comprising the first set do no overlap.

5. The method of any of embodiments 1-2, wherein the third set of time-frequency resources are determined such that frequency resources comprising the third set and frequency resources comprising the first set have different OFDM sub-carrier spacing.

6. The method of any of embodiments 1-5, wherein determining the first set of time- frequency resources comprises selecting the first set of time-frequency resources based on one or more of the following with respect to the frequency bandwidth of the cell: frequency bandwidth, starting frequency, center frequency, ending frequency, and predetermined set of locations for placement of the common signal.

7. The method of any of embodiments 1-5, wherein determining the first set of time- frequency resources comprises selecting the duration of the time resource comprising the first set based on at least one of the periodicity of the common signal and the duration of the common signal.

8. The method of any of embodiments 1-5, wherein determining the first set of time- frequency resources used for transmitting the common signal comprises selecting the first set of time-frequency resources based on a relation between the common signal and one or more particular tests to be conducted for the UE under test.

9. The method of any of embodiments 1-5, wherein determining the first set of time- frequency resources comprises one or more of:

retrieving stored configuration information about the common signal currently

transmitted in the cell; and

monitoring characteristic of signals transmitted in time-frequency resources

comprising the frequency bandwidth of the cell.

10. The method of any of embodiment 1-9, wherein determining the second set of time- frequency resources comprises selecting at least a subset of all time-frequency resources, within the frequency bandwidth of the cell, that do not comprise at least one of the first set of time-frequency resources and the third set of time-frequency resources.

11. The method of embodiment 10, wherein selecting at least a subset is further based on one or more of: number of virtual UEs, number of resource blocks (RBs) per virtual UE, antenna transmission mode, and one or more transmission parameters of the second set of signals.

12. The method of any of embodiments 1-9, wherein determining the second set of time- frequency resources is further based on one or more particular tests to be conducted for the UE under test.

13. The method of any of embodiments 1-12, wherein the third set of signals are usable by the UE under test to perform one or more measurements.

14. A radio network node configurable for generating signals usable for testing operation of a user equipment (UE) within a cell of a wireless communication system, the radio network node comprising:

an antenna configured to send and receive wireless signals; radio transceiver circuitry operably coupled to the antenna;

processing circuitry operably coupled to the radio transceiver circuitry and configured to perform any of the operations of any of embodiments 1-13;

15. A radio network simulator system configurable for generating signals usable for testing operation of a user equipment (UE) within a cell of a wireless communication system, the radio network node comprising:

an external connector;

radio transceiver circuitry operably coupled to, and configurable to send and/or

receive radio signals via, the external connector; and

16. A communication system including a host computer comprising:

processing circuitry configured to provide user data; and

a communication interface configured to forward the user data to a cellular network for transmission to a user equipment (UE), wherein the cellular network comprises a base station having a radio interface and processing circuitry, the base station’s processing circuitry configured to perform any of the operations comprising embodiments 1-13.

17. The communication system of the previous embodiment further including the UE, wherein the UE is configured to communicate with the base station.

19. The communication system of the previous two embodiments, wherein:

the processing circuitry of the host computer is configured to execute a host application, thereby providing the user data; and

the UE comprises processing circuitry configured to execute a client application associated with the host application.

20. A method implemented in a communication system including a host computer, a base station, and a User Equipment (UE), the method comprising: at the host computer, providing user data; and

at the host computer, initiating a transmission carrying the user data to the UE via a cellular network comprising the base station, wherein the base station performs any of the operations comprising any of embodiments 1-13.

21. The method of the previous embodiment, further comprising, at the base station, transmitting the user data.

22. The method of the previous two embodiments, wherein the user data is provided at the host computer by executing a host application, the method further comprising, at the UE, executing a client application associated with the host application.

23. A communication system including a host computer comprising a communication interface configured to receive user data originating from a transmission from a User equipment (UE) to a base station, wherein the base station comprises a radio interface and processing circuitry, the base station’s processing circuitry is configured to perform operations of any of embodiments 1-13.

24. The communication system of the previous embodiment further including the base station.

25. The communication system of the previous two embodiments, further including the UE, wherein the UE is configured to communicate with the base station.

26. The communication system of the previous three embodiments, wherein:

the processing circuitry of the host computer is configured to execute a host application; and

the UE is configured to execute a client application associated with the host application, thereby providing the user data to be received by the host computer.

Claims

1. A method for generating signals usable for testing operation of a user equipment, UE, within a cell of a wireless communication network, the method comprising:

determining (1310) a first set of time-frequency resources, within the frequency

bandwidth of the cell, usable for transmitting a common signal directed to all UEs operating in the cell;

based on the first set of time-frequency resources, determining (1320) a third set of time-frequency resources, within the frequency bandwidth of the cell, usable for transmitting a third set of signals directed to the UE;

based on the first and the third sets of time-frequency resources, determining (1330) a second set of time-frequency resources, within the frequency bandwidth of the cell, usable for transmitting a second set of signals directed to one or more virtual UEs; and

transmitting (1340) the common signal, the second set of signals, and the third set of signals using the determined first, second, and third sets of time-frequency resources.

2. The method of claim 1, wherein the common signal comprises a synchronization signal and physical broadcast channel block, SSB.

3. The method of any of claims 1-2, wherein determining (1320) the third set of time- frequency resources comprises selecting (1321) time-frequency resources that do not overlap with the first set of time-frequency resources.

4. The method of any of claims 1-3, wherein:

determining (1310) the first set of time-frequency resources comprises selecting

(1312) the first set of time-frequency resources based on a synchronization signal and physical broadcast channel block measurement timing configuration, SMTC, window; and determining (1320) the third set of time-frequency resources comprises selecting (1323) time-frequency resources that occur outside of the SMTC window.

5. The method of any of claims 1-3, wherein determining (1320) the third set of time- frequency resources comprises:

selecting (1325) time resources that overlap with the time resources of the first set in at least one symbol; and

selecting (1327) frequency resources that do not overlap with the frequency resources of the first set.

6. The method of any of claims 1-3, wherein determining (1320) the third set of time- frequency resources comprises selecting (1329) frequency resources that have a different OFDM sub-carrier spacing than the frequency resources of the first set.

7. The method of any of claims 1-6, wherein determining (1310) the first set of time- frequency resources comprises selecting (1314) the first set of time-frequency resources based on one or more of the following characteristics of the cell: frequency bandwidth, starting frequency, center frequency, ending frequency, numerology, and predetermined set of locations for placement of the common signal.

8. The method of any of claims 1-6, wherein determining (1310) the first set of time- frequency resources used for transmitting the common signal comprises selecting (1314) the first set of time-frequency resources based on a relation between the common signal and one or more particular tests to be conducted for the UE.

9. The method of any of claim 1-8, wherein determining (1330) the second set of time- frequency resources comprises selecting (1332) at least a subset of all time-frequency resources, within the frequency bandwidth of the cell, that do not include at least one of the first set of time-frequency resources and the third set of time-frequency resources.

10. The method of claim 9, wherein selecting (1332) at least a subset is further based on one or more of: number of virtual UEs, number of resource blocks (RBs) per virtual UE, antenna transmission mode, and one or more transmission parameters of the second set of signals.

11. The method of any of claims 1-10, wherein determining (1330) the second set of time- frequency resources is further based on one or more particular tests to be conducted for the UE.

12. The method of any of claims 1-11, wherein the third set of signals are usable by the UE to perform one or more measurements.

13. The method of any of claims 1-12, wherein the third set of signals includes one or more of the following:

reference measurement channel, RMC;

physical downlink shared channel, PDSCH; and

physical downlink control channel, PDCCH.

14. The method of any of claims 1-13, wherein the second set of signals includes one or more of the following:

load generating signals;

noise generating signals;

virtual UE signals; and

synchronization signal OFDM channel noise, SS-OCN.

15. A radio network node (1460, 1630) configured to generate signals usable for testing operation of a user equipment, UE, within a cell of a wireless communication network, the radio network node comprising:

one or more antennas (1482, 16225) configured to send and receive wireless signals; communication interface circuitry (1490, 1670) operably coupled to, and configured to send and/or receive radio signals via, the antennas (1482, 16225); processing circuitry (1470, 1660) operably coupled to the communication interface circuitry (1490, 1670) and configured to perform operations corresponding to any of the methods of claims 1-14. 16. A radio network simulator (1860) configured to generate signals usable for testing operation of a user equipment, UE, the radio network simulator comprising:

an external connector (1862);

communication interface circuitry (1890) operably coupled to, and configured to send and/or receive radio signals via, the external connector (1862); and processing circuitry (1870) operably coupled to the communication interface circuitry

(1890) and configured to perform operations corresponding to any of the methods of claims 1-14.

17. A non-transitory, computer-readable medium (1480, 1690, 1880) storing program instructions (1695) that, when executed by processing circuitry (1470, 1660, 1870) of a radio network node (1460, 1630) or a radio network simulator (1860), configure the radio network node or the radio network simulator to perform operations corresponding to any of the methods of claims 1-14. 18. A computer program product comprising program instructions (1695) that, when executed by processing circuitry (1470, 1660, 1870) of a radio network node (1460, 1630) or a radio network simulator (1860), configure the radio network node or the radio network simulator to perform operations corresponding to any of the methods of claims 1-14.