TECHNICAL FIELD

The present disclosure relates to wireless communications, and in particular, to a network node, a method and a wireless device for rate matching around reference signals such as a cell-specific reference signal (CRS).

BACKGROUND

The Third Generation Partnership Project (3 GPP) has developed and is developing standards for Fourth Generation (4G) (also referred to as Long Term Evolution (LTE)) and Fifth Generation (5G) (also referred to as New Radio (NR)) wireless communication systems. Such systems provide, among other features, broadband communication between network nodes, such as base stations, and mobile wireless devices (WD), as well as communication between network nodes and between WDs.

With Dynamic Spectrum Sharing (DSS) it is possible to let a NR wireless device rate match the physical downlink shared channel (PDSCH) around the LTE cell-specific reference signals (CRS) using the CRS Rate Matching definition as defined 3GPP specification(s) such as in, for example, 3GPP Technical Specification (TS) 38.331, a portion of which is described below.

RateMatchPatternLTE-CRS :: = SEQUENCE { carrierFreqDL INTEGER (0..16383), carrierBandwidthDL ENUMERATED {n6, nl5, n25, n50, n75, nlOO, spare2, spare 1}, mbsfn-SubframeConflgList EUTRA-MBSFN-SubframeConflgList OPTIONAL, — NeedM nrofCRS-Ports ENUMERATED {nl, n2, n4}, v-Shift ENUMERATED {n0, nl, n2, n3, n4, n5}

}

LTE-CRS-PatternList-r 16 :: = SEQUENCE (SIZE (L.maxLTE-CRS-

P after ns -rl 6) ) OF RateMatchPatternLTE-CRS

From the definition above, a static pattern is always on, except in the multimedia broadcast multicast service single network (MBSFN) subframes. In addition to the definition above, it has been discussed to use up to three CRS rate matching patterns, one of which can be selected using the scheduling information in the NR downlink control information (DCI).

It may be possible to mute the LTE CRS. In 3GPP contributions, this muting technique is referred to as “CRS muting” or “CRS mitigation,” hereinafter referred to as CRS muting. This CRS muting was discussed 3GPP Release 15 such as summarized in 3GPP Technical Report (TR) 21.915 V15.0.0 in clause 7.3.4 (for LTE-M) and 13.3 (for LTE).

In one existing system, the CRS is muted when it is not necessary for the wireless devices, similar to what was discussed in 3GPP Release 15. In particular, the existing system predicts the need for CRS and only enables it when necessary.

Cat-Mi (e.g., category Ml) devices may be a lower power wide area (LPWAN) cellular technology device where the Cat-Mi device is limited to a 1.4 MHz bandwidth. This can be utilized, so it may not be necessary to transmit CRS in, parts of, the frequency band that no Cat-Mi device will listen too. That is, in one example, it may not be necessary to transmit CRS in the frequency band outside of this 1.4 MHz bandwidth that the Cat-Mi device uses.

In 3GPP TS 38.331, it is possible to define up to three (maxLTE-CRS- Patterns-rl6) CRS static rate matching patterns. For example, as described in 3GPP TS 38.331:

RateMatchPatternL TE-CRS

The IE RateMatchPatternLTE-CRS is used to configure a pattern to rate match around LTE CRS. See 3GPP TS 38.214 , clause 5.1.4.2. RateMatchPatternLTE-CRS information element

RateMatchPatternLTE-CRS : : = SEQUENCE { carrierFreqDL INTEGER (0..16383), carrierBandwidthDL ENUMERATED {n6, nl5, n25, n50, n75, nlOO, spare2, spare 1}, mbsfn-SubframeConflgList EUTRA-MBSFN-SubframeConflgList OPTIONAL, - NeedM nrofCRS-Ports ENUMERATED {nl, n2, n4}, v-Shift ENUMERATED {n0, nl, n2, n3, n4, n5} }

LTE-CRS-PatternList-r 16 :: = SEQUENCE (SIZE (L.maxLTE-CRS- P after ns-rl 6) ) OF RateMatchPatternLTE-CRS

The intention may be to allow multiple LTE carriers overlapping one NR carrier.

It may not be possible to define the static patterns needed for:

SIB1-BR - because it is not perfectly but it can be close

SI - because the SI periodicity is too large to work and there can be multiple

SI periods

Paging - because the paging periodicity does not match the MBSFN periodicity.

It is also possible to define two different set of CRS patterns and alternate between the two CRS patterns by using two different coresets with two different coreset poolindexes, as described in 3GPP specifications such as in, for example, 3GPP TS 38.214, clause 5.1.4.2, a portion of which is described below: lte-CRS-PattemListl-r!6 SetupRelease { LTE-CRS-PattemList-rl6 }

OPTIONAL, - Need M lte-CRS-PattemList2-r!6 SetupRelease { LTE-CRS-PattemList-rl6 }

OPTIONAL, - Need M

It is also possible to let Cat-Mi devices use a 1.4 or 3 MHz carrier. The problems with this approach are the following:

Reduced coverage due to limited SIB1-BR repetitions

SIB1-BR, SI and paging transmissions reduce the cell throughput since these transmissions share the same physical resources as normal data transmissions. In high load scenarios it may not be possible to increase the enhanced Machine Type Communication (eMTC) cell capacity since the carrier size is fixed.

Hence, existing LTE based CRS patterns may not work efficiently in with new technologies such as, for example, Cat-Mi devices.

SUMMARY

Some embodiments herein advantageously provide methods and apparatuses for rate matching around reference signals such as a cell-specific reference signal (CRS).

According to a first aspect there is presented a network node for rate matching around reference signals. The network node is configured to communicate with a wireless device (WD). The network node comprises a processing circuitry configured to provide an indication to the wireless device, whether at least one time and frequency resource for transmitting cell-specific reference signal (CRS) is applicable for rate matching. The at least one time and frequency resource for transmitting CRS corresponds to a subset of the at least one time and frequency resource in a static CRS resource pattern.

According to a second aspect there is presented a method for rate matching around reference signals implemented in a network node that is configured to communicate with a wireless device. The method comprises providing an indication, to the wireless device, whether at least one time and frequency resource for transmitting CRS is applicable for rate matching, The at least one time and frequency resource for transmitting CRS corresponds to a subset of the at least one time and frequency resource in a static CRS resource pattern. According to a third aspect there is presented a wireless device (WD) for rate matching around reference signals. The wireless device is configured to communicate with a network node. The WD comprises a radio interface and a processing circuitry. The WD is configured to receive an indication whether at least one time and frequency resource for receiving CRS is applicable for rate matching, The WD receives the CRS and performs rate matching based on the indication and the received CRS. The received CRS corresponds to a CRS static resource pattern, and the at least one time and frequency resource for received CRS corresponds to a subset of at least one frequency and time resource in the static CRS resource pattern.

In one or more embodiments, a method (e.g., standardized method) is provided to define CRS rate matching pattern suitable for one or more of system information block type 1 specific for bandwidth reduced devices (SIB1-BR), system information (SI), Paging (MTC physical downlink control channel (MPDCCH)) and the center frequencies used for primary synchronization signal (PSS), secondary synchronization signal (SSS) and physical broadcast channel (PBCH). Examples of bandwidth reduced devices may be Cat-Mi devices. This method can be used both for regular/legacy LTE devices (allowing different CRS patterns depending on the situation) and Cat-Mi and Cat-M2 devices (e.g., non-legacy devices, NR based devices, etc.). One or more embodiments described herein may be used not only for DSS between NR and LTE-M but also between NR and legacy LTE.

Those CRS patterns may always be rate matched around, except for symbol 2+ in the MBSFN subframes. The pattern may make it possible to rate match around the 1 subframe “preheating” before the intended CRS pattern start.

In addition, it may be possible to define patterns that can then be selected in the NR PDCCH DCI, for example:

Nothing

LTE whole bandwidth

Cat-Mi random access narrowband

Cat-Mi narrowbands used for data transmission

For example, each category above may correspond to a respective CRS pattern. Advantageously, these aspects and embodiments described herein provides more advanced CRS rate matching pattern definitions to make it possible to reduce the static overhead due to CRS to a minimum while still allowing high capacity for Cat-Mi in high load scenarios.

Other objectives, features and advantages of the enclosed embodiments will be apparent from the following detailed disclosure, from the attached dependent claims as well as from the drawings.

Generally, all terms used in the claims are to be interpreted according to their ordinary meaning in the technical field, unless explicitly defined otherwise herein. All references to "a/an/the element, apparatus, component, means, module, step, etc." are to be interpreted openly as referring to at least one instance of the element, apparatus, component, means, module, step, etc., unless explicitly stated otherwise. The steps of any method disclosed herein do not have to be performed in the exact order disclosed, unless explicitly stated.

BRIEF DESCRIPTION OF THE DRAWINGS

A more complete understanding of the present embodiments, and the attendant advantages and features thereof, will be more readily understood by reference to the following detailed description when considered in conjunction with the accompanying drawings wherein:

FIG. 1 is a schematic diagram of an example network architecture illustrating a communication system connected via an intermediate network to a host computer according to the principles in the present disclosure;

FIG. 2 is a block diagram of a host computer communicating via a network node with a wireless device over an at least partially wireless connection according to some embodiments of the present disclosure;

FIG. 3 is a flowchart illustrating example methods implemented in a communication system including a host computer, a network node and a wireless device for executing a client application at a wireless device according to some embodiments of the present disclosure; FIG. 4 is a flowchart illustrating example methods implemented in a communication system including a host computer, a network node and a wireless device for receiving user data at a wireless device according to some embodiments of the present disclosure;

FIG. 5 is a flowchart illustrating example methods implemented in a communication system including a host computer, a network node and a wireless device for receiving user data from the wireless device at a host computer according to some embodiments of the present disclosure;

FIG. 6 is a flowchart illustrating example methods implemented in a communication system including a host computer, a network node and a wireless device for receiving user data at a host computer according to some embodiments of the present disclosure;

FIG. 7 is a flowchart of an example process in a network node according to some embodiments of the present disclosure; and

FIG. 8 is a flowchart of an example process in a wireless device according to some embodiments of the present disclosure.

DETAILED DESCRIPTION

As described above, existing prior art CRS patterns may not provide adequate performance for new technologies (e.g., RATs, RATs for certain device types) such as, for example, Cat-Mi. One or more embodiments described herein solve at least part of the problem with existing systems by providing more/new CRS rate matching pattern definitions to make it possible to reduce the static overhead due to CRS to a minimum while still allowing high capacity for Cat-Mi in high load scenarios.

Before describing in detail exemplary embodiments, it is noted that the embodiments reside primarily in combinations of apparatus components and processing steps related to rate matching around reference signals such as a cellspecific reference signal (CRS). Accordingly, components have been represented where appropriate by conventional symbols in the drawings, showing only those specific details that are pertinent to understanding the embodiments so as not to obscure the disclosure with details that will be readily apparent to those of ordinary skill in the art having the benefit of the description herein. Like numbers refer to like elements throughout the description.

As used herein, relational terms, such as “first” and “second,” “top” and “bottom,” and the like, may be used solely to distinguish one entity or element from another entity or element without necessarily requiring or implying any physical or logical relationship or order between such entities or elements. The terminology used herein is for the purpose of describing particular embodiments only and is not intended to be limiting of the concepts described herein. As used herein, the singular forms “a”, “an” and “the” are intended to include the plural forms as well, unless the context clearly indicates otherwise. It will be further understood that the terms “comprises,” “comprising,” “includes” and/or “including” when used herein, specify the presence of stated features, integers, steps, operations, elements, and/or components, but do not preclude the presence or addition of one or more other features, integers, steps, operations, elements, components, and/or groups thereof.

In embodiments described herein, the j oining term, “in communication with” and the like, may be used to indicate electrical or data communication, which may be accomplished by physical contact, induction, electromagnetic radiation, radio signaling, infrared signaling or optical signaling, for example. One having ordinary skill in the art will appreciate that multiple components may interoperate and modifications and variations are possible of achieving the electrical and data communication.

In some embodiments described herein, the term “coupled,” “connected,” and the like, may be used herein to indicate a connection, although not necessarily directly, and may include wired and/or wireless connections.

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

In some embodiments, the non-limiting terms wireless device (WD) or a user equipment (UE) are used interchangeably. The WD herein can be any type of wireless device capable of communicating with a network node or another WD over radio signals, such as wireless device (WD). The WD may also be a radio communication device, target device, device to device (D2D) WD, machine type WD or WD capable of machine to machine communication (M2M), low-cost and/or low-complexity WD, a sensor equipped with WD, Tablet, mobile terminals, smart phone, laptop embedded equipped (LEE), laptop mounted equipment (LME), Cat-Mi device, Cat-M device, Cat-M2 device, USB dongles, Customer Premises Equipment (CPE), an Internet of Things (loT) device, or a Narrowband loT (NB-IOT) device, etc.

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

Note that although terminology from one particular wireless system, such as, for example, 3GPP LTE and/or New Radio (NR), may be used in this disclosure, this should not be seen as limiting the scope of the disclosure to only the aforementioned system. Other wireless systems, including without limitation Wide Band Code Division Multiple Access (WCDMA), Worldwide Interoperability for Microwave Access (WiMax), Ultra Mobile Broadband (UMB) and Global System for Mobile Communications (GSM), may also benefit from exploiting the ideas covered within this disclosure. Note further, that functions described herein as being performed by a wireless device or a network node may be distributed over a plurality of wireless devices and/or network nodes. In other words, it is contemplated that the functions of the network node and wireless device described herein are not limited to performance by a single physical device and, in fact, can be distributed among several physical devices.

Unless otherwise defined, all terms (including technical and scientific terms) used herein have the same meaning as commonly understood by one of ordinary skill in the art to which this disclosure belongs. It will be further understood that terms used herein should be interpreted as having a meaning that is consistent with their meaning in the context of this specification and the relevant art and will not be interpreted in an idealized or overly formal sense unless expressly so defined herein.

Some embodiments provide rate matching around reference signals such as a cell-specific reference signal (CRS).

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

Also, it is contemplated that a WD 22 can be in simultaneous communication and/or configured to separately communicate with more than one network node 16 and more than one type of network node 16. For example, a WD 22 can have dual connectivity with a network node 16 that supports LTE and the same or a different network node 16 that supports NR. As an example, WD 22 can be in communication with an eNB for LTE/E-UTRAN and a gNB for NR/NG-RAN.

The communication system 10 may itself be connected to a host computer 24, which may 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. The host computer 24 may be under the ownership or control of a service provider, or may be operated by the service provider or on behalf of the service provider. The connections 26, 28 between the communication system 10 and the host computer 24 may extend directly from the core network 14 to the host computer 24 or may extend via an optional intermediate network 30. The intermediate network 30 may be one of, or a combination of more than one of, a public, private or hosted network. The intermediate network 30, if any, may be a backbone network or the Internet. In some embodiments, the intermediate network 30 may comprise two or more sub-networks (not shown).

The communication system of FIG. 1 as a whole enables connectivity between one of the connected WDs 22a, 22b and the host computer 24. The connectivity may be described as an over-the-top (OTT) connection. The host computer 24 and the connected WDs 22a, 22b are configured to communicate data and/or signaling via the OTT connection, using the access network 12, the core network 14, any intermediate network 30 and possible further infrastructure (not shown) as intermediaries. The OTT connection may be transparent in the sense that at least some of the participating communication devices through which the OTT connection passes are unaware of routing of uplink and downlink communications. For example, a network node 16 may not or need not be informed about the past routing of an incoming downlink communication with data originating from a host computer 24 to be forwarded (e.g., handed over) to a connected WD 22a. Similarly, the network node 16 need not be aware of the future routing of an outgoing uplink communication originating from the WD 22a towards the host computer 24.

A network node 16 is configured to include an indication unit 32 which is configured to perform one or more network node 16 functions as described herein such as with respect to rate matching around CRS. A wireless device 22 is configured to include a rate matching unit 34 which is configured to one or more wireless device 22 functions such as with respect to rate matching around CRS.

Example implementations, in accordance with an embodiment, of the WD 22, network node 16 and host computer 24 discussed in the preceding paragraphs will now be described with reference to FIG. 2. In a communication system 10, a host computer 24 comprises hardware (HW) 38 including a communication interface 40 configured to set up and maintain a wired or wireless connection with an interface of a different communication device of the communication system 10. The host computer 24 further comprises processing circuitry 42, which may have storage and/or processing capabilities. The processing circuitry 42 may include a processor 44 and memory 46. In particular, in addition to or instead of a processor, such as a central processing unit, and memory, the processing circuitry 42 may comprise integrated circuitry for processing and/or control, e.g., one or more processors and/or processor cores and/or FPGAs (Field Programmable Gate Array) and/or ASICs (Application Specific Integrated Circuitry) adapted to execute instructions. The processor 44 may be configured to access (e.g., write to and/or read from) memory 46, which may comprise any kind of volatile and/or nonvolatile memory, e.g., cache and/or buffer memory and/or RAM (Random Access Memory) and/or ROM (Read- Only Memory) and/or optical memory and/or EPROM (Erasable Programmable Read-Only Memory).

Processing circuitry 42 may be configured to control any of the methods and/or processes described herein and/or to cause such methods, and/or processes to be performed, e.g., by host computer 24. Processor 44 corresponds to one or more processors 44 for performing host computer 24 functions described herein. The host computer 24 includes memory 46 that is configured to store data, programmatic software code and/or other information described herein. In some embodiments, the software 48 and/or the host application 50 may include instructions that, when executed by the processor 44 and/or processing circuitry 42, causes the processor 44 and/or processing circuitry 42 to perform the processes described herein with respect to host computer 24. The instructions may be software associated with the host computer 24.

The software 48 may be executable by the processing circuitry 42. The software 48 includes a host application 50. The host application 50 may be operable to provide a service to a remote user, such as a WD 22 connecting via an OTT connection 52 terminating at the WD 22 and the host computer 24. In providing the service to the remote user, the host application 50 may provide user data which is transmitted using the OTT connection 52. The “user data” may be data and information described herein as implementing the described functionality. In one embodiment, the host computer 24 may be configured for providing control and functionality to a service provider and may be operated by the service provider or on behalf of the service provider. The processing circuitry 42 of the host computer 24 may enable the host computer 24 to observe, monitor, control, transmit to and/or receive from the network node 16 and or the wireless device 22. The processing circuitry 42 of the host computer 24 may include an information unit 54 configured to enable the service provider to determine, provide, relay, forward, transmit, receive, analyze, store, etc., information related to rate matching around CRS such as the CRS based information described herein.

The communication system 10 further includes a network node 16 provided in a communication system 10 and including hardware 58 enabling it to communicate with the host computer 24 and with the WD 22. The hardware 58 may include a communication interface 60 for setting up and maintaining a wired or wireless connection with an interface of a different communication device of the communication system 10, as well as a radio interface 62 for setting up and maintaining at least a wireless connection 64 with a WD 22 located in a coverage area 18 served by the network node 16. The radio interface 62 may be formed as or may include, for example, one or more RF transmitters, one or more RF receivers, and/or one or more RF transceivers. The communication interface 60 may be configured to facilitate a connection 66 to the host computer 24. The connection 66 may be direct or it may pass through a core network 14 of the communication system 10 and/or through one or more intermediate networks 30 outside the communication system 10.

In the embodiment shown, the hardware 58 of the network node 16 further includes processing circuitry 68. The processing circuitry 68 may include a processor 70 and a memory 72. In particular, in addition to or instead of a processor, such as a central processing unit, and memory, the processing circuitry 68 may comprise integrated circuitry for processing and/or control, e.g., one or more processors and/or processor cores and/or FPGAs (Field Programmable Gate Array) and/or ASICs (Application Specific Integrated Circuitry) adapted to execute instructions. The processor 70 may be configured to access (e.g., write to and/or read from) the memory 72, which may comprise any kind of volatile and/or nonvolatile memory, e.g., cache and/or buffer memory and/or RAM (Random Access Memory) and/or ROM (Read-Only Memory) and/or optical memory and/or EPROM (Erasable Programmable Read-Only Memory).

Thus, the network node 16 further has software 74 stored internally in, for example, memory 72, or stored in external memory (e.g., database, storage array, network storage device, etc.) accessible by the network node 16 via an external connection. The software 74 may be executable by the processing circuitry 68. The processing circuitry 68 may be configured to control any of the methods and/or processes described herein and/or to cause such methods, and/or processes to be performed, e.g., by network node 16. Processor 70 corresponds to one or more processors 70 for performing network node 16 functions described herein. The memory 72 is configured to store data, programmatic software code and/or other information described herein. In some embodiments, the software 74 may include instructions that, when executed by the processor 70 and/or processing circuitry 68, causes the processor 70 and/or processing circuitry 68 to perform the processes described herein with respect to network node 16. For example, processing circuitry 68 of the network node 16 may include indication unit 32 configured to perform one or more network node 16 functions as described herein such as with respect to rate matching around CRS.

The communication system 10 further includes the WD 22 already referred to. The WD 22 may have hardware 80 that may include a radio interface 82 configured to set up and maintain a wireless connection 64 with a network node 16 serving a coverage area 18 in which the WD 22 is currently located. The radio interface 82 may be formed as or may include, for example, one or more RF transmitters, one or more RF receivers, and/or one or more RF transceivers.

The hardware 80 of the WD 22 further includes processing circuitry 84. The processing circuitry 84 may include a processor 86 and memory 88. In particular, in addition to or instead of a processor, such as a central processing unit, and memory, the processing circuitry 84 may comprise integrated circuitry for processing and/or control, e.g., one or more processors and/or processor cores and/or FPGAs (Field Programmable Gate Array) and/or ASICs (Application Specific Integrated Circuitry) adapted to execute instructions. The processor 86 may be configured to access (e.g., write to and/or read from) memory 88, which may comprise any kind of volatile and/or nonvolatile memory, e.g., cache and/or buffer memory and/or RAM (Random Access Memory) and/or ROM (Read-Only Memory) and/or optical memory and/or EPROM (Erasable Programmable Read-Only Memory).

Thus, the WD 22 may further comprise software 90, which is stored in, for example, memory 88 at the WD 22, or stored in external memory (e.g., database, storage array, network storage device, etc.) accessible by the WD 22. The software 90 may be executable by the processing circuitry 84. The software 90 may include a client application 92. The client application 92 may be operable to provide a service to a human or non-human user via the WD 22, with the support of the host computer 24. In the host computer 24, an executing host application 50 may communicate with the executing client application 92 via the OTT connection 52 terminating at the WD 22 and the host computer 24. In providing the service to the user, the client application 92 may receive request data from the host application 50 and provide user data in response to the request data. The OTT connection 52 may transfer both the request data and the user data. The client application 92 may interact with the user to generate the user data that it provides.

The processing circuitry 84 may be configured to control any of the methods and/or processes described herein and/or to cause such methods, and/or processes to be performed, e.g., by WD 22. The processor 86 corresponds to one or more processors 86 for performing WD 22 functions described herein. The WD 22 includes memory 88 that is configured to store data, programmatic software code and/or other information described herein. In some embodiments, the software 90 and/or the client application 92 may include instructions that, when executed by the processor 86 and/or processing circuitry 84, causes the processor 86 and/or processing circuitry 84 to perform the processes described herein with respect to WD 22. For example, the processing circuitry 84 of the wireless device 22 may include a rate matching unit 34 configured to perform one or more wireless device 22 functions as described herein such as with respect to rate matching around CRS.

In some embodiments, the inner workings of the network node 16, WD 22, and host computer 24 may be as shown in FIG. 2 and independently, the surrounding network topology may be that of FIG. 1.

In FIG. 2, the OTT connection 52 has been drawn abstractly to illustrate the communication between the host computer 24 and the wireless device 22 via the network node 16, without explicit reference to any intermediary devices and the precise routing of messages via these devices. Network infrastructure may determine the routing, which it may be configured to hide from the WD 22 or from the service provider operating the host computer 24, or both. While the OTT connection 52 is active, the network infrastructure may further take decisions by which it dynamically changes the routing (e.g., on the basis of load balancing consideration or reconfiguration of the network).

The wireless connection 64 between the WD 22 and the network node 16 is in accordance with the teachings of the embodiments described throughout this disclosure. One or more of the various embodiments improve the performance of OTT services provided to the WD 22 using the OTT connection 52, in which the wireless connection 64 may form the last segment. More precisely, the teachings of some of these embodiments may improve the data rate, latency, and/or power consumption and thereby provide benefits such as reduced user waiting time, relaxed restriction on file size, better responsiveness, extended battery lifetime, etc.

In some embodiments, a measurement procedure may be provided for the purpose of monitoring data rate, latency and other factors on which the one or more embodiments improve. There may further be an optional network functionality for reconfiguring the OTT connection 52 between the host computer 24 and WD 22, in response to variations in the measurement results. The measurement procedure and/or the network functionality for reconfiguring the OTT connection 52 may be implemented in the software 48 of the host computer 24 or in the software 90 of the WD 22, or both. In embodiments, sensors (not shown) may be deployed in or in association with communication devices through which the OTT connection 52 passes; the sensors may participate in the measurement procedure by supplying values of the monitored quantities exemplified above, or supplying values of other physical quantities from which software 48, 90 may compute or estimate the monitored quantities. The reconfiguring of the OTT connection 52 may include message format, retransmission settings, preferred routing etc.; the reconfiguring need not affect the network node 16, and it may be unknown or imperceptible to the network node 16. Some such procedures and functionalities may be known and practiced in the art. In certain embodiments, measurements may involve proprietary WD signaling facilitating the host computer’s 24 measurements of throughput, propagation times, latency and the like. In some embodiments, the measurements may be implemented in that the software 48, 90 causes messages to be transmitted, in particular empty or ‘dummy’ messages, using the OTT connection 52 while it monitors propagation times, errors, etc.

Thus, in some embodiments, the host computer 24 includes processing circuitry 42 configured to provide user data and a communication interface 40 that is configured to forward the user data to a cellular network for transmission to the WD 22. In some embodiments, the cellular network also includes the network node 16 with a radio interface 62. In some embodiments, the network node 16 is configured to, and/or the network node’s 16 processing circuitry 68 is configured to perform the functions and/or methods described herein for preparing/initiating/maintaining/supporting/ending a transmission to the WD 22, and/or preparing/terminating/maintaining/supporting/ending in receipt of a transmission from the WD 22.

In some embodiments, the host computer 24 includes processing circuitry 42 and a communication interface 40 that is configured to a communication interface 40 configured to receive user data originating from a transmission from a WD 22 to a network node 16. In some embodiments, the WD 22 is configured to, and/or comprises a radio interface 82 and/or processing circuitry 84 configured to perform the functions and/or methods described herein for preparing/initiating/maintaining/supporting/ending a transmission to the network node 16, and/or preparing/terminating/maintaining/supporting/ending in receipt of a transmission from the network node 16.

Although FIGS. 1 and 2 show various “units” such as indication unit 32, and rate matching unit 34 as being within a respective processor, it is contemplated that these units may be implemented such that a portion of the unit is stored in a corresponding memory within the processing circuitry. In other words, the units may be implemented in hardware or in a combination of hardware and software within the processing circuitry.

FIG. 3 is a flowchart illustrating an example method implemented in a communication system, such as, for example, the communication system of FIGS. 1 and 2, in accordance with one embodiment. The communication system may include a host computer 24, a network node 16 and a WD 22, which may be those described with reference to FIG. 2. In a first step of the method, the host computer 24 provides user data (Block SI 00). In an optional substep of the first step, the host computer 24 provides the user data by executing a host application, such as, for example, the host application 50 (Block SI 02). In a second step, the host computer 24 initiates a transmission carrying the user data to the WD 22 (Block SI 04). In an optional third step, the network node 16 transmits to the WD 22 the user data which was carried in the transmission that the host computer 24 initiated, in accordance with the teachings of the embodiments described throughout this disclosure (Block SI 06). In an optional fourth step, the WD 22 executes a client application, such as, for example, the client application 92, associated with the host application 50 executed by the host computer 24 (Block SI 08).

FIG. 4 is a flowchart illustrating an example method implemented in a communication system, such as, for example, the communication system of FIG. 1, in accordance with one embodiment. The communication system may include a host computer 24, a network node 16 and a WD 22, which may be those described with reference to FIGS. 1 and 2. In a first step of the method, the host computer 24 provides user data (Block SI 10). In an optional substep (not shown) the host computer 24 provides the user data by executing a host application, such as, for example, the host application 50. In a second step, the host computer 24 initiates a transmission carrying the user data to the WD 22 (Block SI 12). The transmission may pass via the network node 16, in accordance with the teachings of the embodiments described throughout this disclosure. In an optional third step, the WD 22 receives the user data carried in the transmission (Block SI 14).

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

FIG. 6 is a flowchart illustrating an example method implemented in a communication system, such as, for example, the communication system of FIG. 1, in accordance with one embodiment. The communication system may include a host computer 24, a network node 16 and a WD 22, which may be those described with reference to FIGS. 1 and 2. In an optional first step of the method, in accordance with the teachings of the embodiments described throughout this disclosure, the network node 16 receives user data from the WD 22 (Block SI 28). In an optional second step, the network node 16 initiates transmission of the received user data to the host computer 24 (Block S130). In a third step, the host computer 24 receives the user data carried in the transmission initiated by the network node 16 (Block S132).

FIG. 7 is a flowchart of an example process in a network node 16 according to one or more embodiments of the present disclosure. One or more blocks described herein may be performed by one or more elements of network node 16 such as by one or more of processing circuitry 68 (including the indication unit 32), processor 70, radio interface 62 and/or communication interface 60. Network node 16 is configured to indicate (Block S134), to the wireless device 22, whether at least one time and frequency resource for transmitting cell-specific reference signal, CRS, is applicable for rate matching, as described herein. The time and frequency resource may be suitable for one or more of system information block type 1 -bandwidth reduced device (SIBl)-BR, system information (SI), Paging (MTC physical downlink control channel (MPDCCH)) and center frequencies used for primary synchronization signal (PSS), secondary synchronization signal (SSS) and physical broadcast channel (PBCH). The term “CRS signaling” used herein may also mean CRS transmission and may interchangeably be used in the text. According to one or more embodiments, the at least one time and frequency resource for transmitting the CRS corresponds to a subset of at least one time and frequency resource in a static CRS resource pattern. The term “corresponds” when used herein e.g. means to match something such that for example the transmitted CRS may be matched on a part of the CRS resource pattern. According to one or more embodiments, the applicability comprises that the indication of the subset of at least one time and frequency resource in the static CRS resource pattern comprises the indication on what time and frequency resource the CRS is transmitted or on what time and frequency resource the CRS is not transmitted. According to one or more embodiments, the at least one time and frequency resource is selected based on device type. According to one or more embodiments, the transmission of CRS is on a first radio access technology, RAT, CRS and the wireless device is a second RAT wireless device, the first RAT being different from the second RAT. According to one or more embodiments, the CRS is transmitted on a first RAT and the wireless device is on a second RAT. According to one or more embodiments, the indication is provided in one of downlink control information, DCI, signaling and radio resource control, RRC, signaling. FIG. 8 is a flowchart of an example process in a wireless device 22 according to some embodiments of the present disclosure. One or more blocks described herein may be performed by one or more elements of wireless device 22 such as by one or more of processing circuitry 84 (including the rate matching unit 34), processor 86, radio interface 82 and/or communication interface 60. Wireless device 22 is configured to receive (Block SI 36) an indication whether at least one time and frequency resource for CRS signaling is applicable for rate matching, as described herein. Wireless device 22 is configured to receive (Block SI 38) the CRS, as described herein. Wireless device 22 is configured to perform (Block SI 40) rate matching based on the indication and the received CRS, as described herein.

According to one or more embodiments, the received CRS corresponds to a static CRS resource pattern wherein the at least one time and frequency resource for the received CRS corresponds to a subset of the at least one time and frequency resource in the static CRS resource pattern. E.g. the received CRS matches to a part of the resources in the CRS resource pattern, so it may be received on a part of what is rate matched. According to one or more embodiments, the applicability comprises that the indication of the subset of at least one time and frequency resource in the static CRS resource pattern comprises the indication on what time and frequency resource the CRS is received or on what time and frequency resource the CRS is not received. According to one or more embodiments, the at least one time and frequency resource is selected based on device type. According to one or more embodiments, the CRS is received on a first radio access technology, RAT, and the wireless device is a second RAT wireless device, the first RAT being different from the second RAT. According to one or more embodiments, the indication is received in one of downlink control information, DCI, signaling and radio resource control, RRC, signaling.

Having described the general process flow of arrangements of the disclosure and having provided examples of hardware and software arrangements for implementing the processes and functions of the disclosure, the sections below provide details and examples of arrangements for rate matching around CRS.

Some embodiments provide rate matching around CRS.

One or more embodiments specify on what resource in time and frequency the CRS is transmitted. In other words, one or more embodiments specify when in time and frequency the LTE CRS (e.g., first radio access technology (RAT) CRS) is applicable, and therefore the NR device (e.g., second RAT wireless device 22) rate matches around the LTE CRS. In some existing systems, there may be a MBSFN list indicating that CRS is not applicable in such MFSFN subframes. However, one or more embodiments specify when in time and frequency the CRS is applicable among the non-MBSFN subframes. For example, in existing systems, the CRS (e.g., LTE CRS or LTE CRS pattern) is static such that the static overhead in resources is high. One or more embodiments of the instant disclosure allows network node 16 to indicate at least one time and frequency resource carrying the static CRS pattern that are applicable to wireless device 22. This may reduce the static overhead in resources as the wireless device 22 may only rate match around a subset of CRS resources from the static CRS pattern or may rate match around the new CRS pattern associated with the indication. The CRS pattern used for rate matching in one or more embodiments is referred to as the CRS rate matching pattern. In one or more embodiments, the CRS may not be applicable in the MBSFN subframes, similar to existing systems.

In one or more embodiments, the CRS rate match pattern is performed through radio resource control (RRC) signaling as an extension (or add-on) to CRS rate match information defined in existing standards. For example, the indication of at least one time and frequency resource carrying the static CRS pattern that is/are applicable to wireless device 22 may be provided in the extension or add-on information in the RRC signaling.

In one or more embodiments, there are two CRS types: static and dynamic. Three embodiments may be possible: 1) when only static is applicable, 2) only dynamic is applicable and 3) both static and dynamic are applicable. The text below assumes that both static and dynamic is included in the 3GPP TS 38.331 specification document, but the teaching described herein are applicable to when one of them is excluded.

The static CRS type means that the CRS is always applicable. The dynamic CRS type means that the CRS is transmitted when the DCI indicates so. There are two embodiments for the DCI encoding. In one embodiment one dynamic CRS rate matching pattern ID (identity) can be indicated (the number of bits needed is 21og(maxid)), on the other embodiment multiple identities can be indicated in the DCI with one bit for each ID.

The RRC attribute names below are merely suggestions. Other names may be used in possible future standardization work, but the functionality of what these field or information elements or bits indicate may be the same. RateMatchPattemLTE-CRS-vXXX ::= SEQUENCE { carrierFreqDL INTEGER (0..16383), carrierBandwidthDL ENUMERATED {n6, n!5, n25, n50, n75, nlOO, spare2, sparel}, mbsfn-SubframeConfigList EUTRA-MBSFN-SubframeConfigList OPTIONAL, - - Need M nrofCRS-Ports ENUMERATED {nl, n2, n4}, v-Shift ENUMERATED {n0, nl, n2, n3, n4, n5}, staticCrsRateMatchApplicableList-vXXX SEQUENCE (SIZE

(1..maxNrofStaticCrsRateMatchApplicableLists)) OF StaticCrsRateMatchApplicablePeriod OPTIONAL, dynamicCrsRateMatchApplicableltem-vXXX SEQUENCE (SIZE

(1..maxNrofDynamicCrsRateMatchApplicableltems)) OF DynamicCrsRateMatchApplicableltem OPTIONAL,

The static parameter can be defined in several ways. In the below example there are several embodiments described. The pattern size M, N, K and maxNrof* (above) can vary and the number of alternatives between them (when lines has been removed or omitted for ease of reading).

RateMatchResourceBlocks ::= CHOICE { resourceBlocks BIT STRING (SIZE (carrierBandwidthDL)), narrowbands BIT STRING (SIZE (carrierBandwidthDL/6)),

StaticCrsRateMatchingApplicablePeriod ::= SEQUENCE { rateMatchResourceBlocks RateMatchResourceBlocks, periodicity AndPattem CHOICE { bitmaps { nM BIT STRING (SIZE (M)),

... [[One or more possibilities omitted for ease reading]] ... nN BIT STRING (SIZE (N)), startAndLength { startOffset INTEGER (0... N-l), periodicity INTEGER (M... N), length INTEGER (0... K),

The startOffset, periodicity and length are in LTE subframes.

The dynamic parameter is less complex to define since only the frequency needs to be considered. There are however multiple embodiments depending on the number of such items.

DynamicCrsRateMatchApplicableltem ::= SEQUENCE { dynamicCrsRateMatchApplicableld DynamicCrsRateMatchApplictyld, rateMatchResourceBlocks RateMatchResourceBlocks

DynamicCrsRateMatchApplicableld ::= INTEGER

(0..maxNrofDynamicCrsRateMatchApplicableltems- 1 )

In one or more embodiments, the wireless device takes the union of all static and dynamic parameters (when indicated in the DCI) as the CRS blocks to rate match around are in non-MBSFN subframes. In MBSFN subframes, the CRS is assumed to not be transmitted and this behavior remains the same or similar as defined in existing 3GPP specification(s).

In one or more embodiments, the start and length can be applied also to the RateMatchPattem information element (IE) to allow rate matching around the actual transmission of SIB1-BR and SI since they are completely static.

Hence, one or more embodiments described herein provides one or more of the following advantages: In a cell with low Cat-Mi load, the CRS overhead can be reduced to (approximately) the same level as the CRS overhead for 1.4 or 3 MHz LTE. o This is possible also when the total Cat-Mi carrier bandwidth is 5, 10, 15 or 20 MHz, thereby allowing the Cat-Mi technology capacity to scale in case of high load.

One or more embodiments described herein may not require any update of Cat-Mi or LTE devices. It is the NR device that performs the rate-matching and this is also backwards compatible because older NR devices can be configured to rate match around the whole bandwidth. So, while these older (e.g., older 3GPP version) NR devices may not get the benefit from using the CRS rate matching pattern described herein, these older NR devices will still work as before.

As will be appreciated by one of skill in the art, the concepts described herein may be embodied as a method, data processing system, computer program product and/or computer storage media storing an executable computer program. Accordingly, the concepts described herein may take the form of an entirely hardware embodiment, an entirely software embodiment or an embodiment combining software and hardware aspects all generally referred to herein as a “circuit” or “module.” Any process, step, action and/or functionality described herein may be performed by, and/or associated to, a corresponding module, which may be implemented in software and/or firmware and/or hardware. Furthermore, the disclosure may take the form of a computer program product on a tangible computer usable storage medium having computer program code embodied in the medium that can be executed by a computer. Any suitable tangible computer readable medium may be utilized including hard disks, CD-ROMs, electronic storage devices, optical storage devices, or magnetic storage devices.

Some embodiments are described herein with reference to flowchart illustrations and/or block diagrams of methods, systems and computer program products. It will be understood that each block of the flowchart illustrations and/or block diagrams, and combinations of blocks in the flowchart illustrations and/or block diagrams, can be implemented by computer program instructions. These computer program instructions may be provided to a processor of a general purpose computer (to thereby create a special purpose computer), special purpose computer, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions/acts specified in the flowchart and/or block diagram block or blocks.

These computer program instructions may also be stored in a computer readable memory or storage medium that can direct a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer readable memory produce an article of manufacture including instruction means which implement the function/act specified in the flowchart and/or block diagram block or blocks.

The computer program instructions may also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer implemented process such that the instructions which execute on the computer or other programmable apparatus provide steps for implementing the functions/acts specified in the flowchart and/or block diagram block or blocks.

It is to be understood that the functions/acts noted in the blocks may occur out of the order noted in the operational illustrations. For example, two blocks shown in succession may in fact be executed substantially concurrently or the blocks may sometimes be executed in the reverse order, depending upon the functionality/acts involved. Although some of the diagrams include arrows on communication paths to show a primary direction of communication, it is to be understood that communication may occur in the opposite direction to the depicted arrows.

Computer program code for carrying out operations of the concepts described herein may be written in an object oriented programming language such as Python, Java® or C++. However, the computer program code for carrying out operations of the disclosure may also be written in conventional procedural programming languages, such as the "C" programming language. The program code may execute entirely on the user's computer, partly on the user's computer, as a stand-alone software package, partly on the user's computer and partly on a remote computer or entirely on the remote computer. In the latter scenario, the remote computer may be connected to the user's computer through a local area network (LAN) or a wide area network (WAN), or the connection may be made to an external computer (for example, through the Internet using an Internet Service Provider).

Many different embodiments have been disclosed herein, in connection with the above description and the drawings. It will be understood that it would be unduly repetitious and obfuscating to literally describe and illustrate every combination and subcombination of these embodiments. Accordingly, all embodiments can be combined in any way and/or combination, and the present specification, including the drawings, shall be construed to constitute a complete written description of all combinations and subcombinations of the embodiments described herein, and of the manner and process of making and using them, and shall support claims to any such combination or subcombination.

Abbreviations that may be used in the preceding description include: [include a list of abbreviations provided in the IVD if any, or delete if abbreviations are not listed in the IVD]

It will be appreciated by persons skilled in the art that the embodiments described herein are not limited to what has been particularly shown and described herein above. In addition, unless mention was made above to the contrary, it should be noted that all of the accompanying drawings are not to scale. A variety of modifications and variations are possible in light of the above teachings.

Embodiments:

Embodiment Al . A network node configured to communicate with a wireless device (WD), the network node configured to, and/or comprising a radio interface and/or comprising processing circuitry configured to: indicate, to the wireless device, whether at least one time and frequency resource for cell-specific reference signal, CRS, signaling is applicable for rate matching.

Embodiment A2. The network node of Embodiment Al, wherein the at least one time and frequency resource for CRS signaling corresponds to a subset of at least one resource in a static CRS resource pattern.

Embodiment A3. The network node of any one of Embodiments A1-A2, wherein the at least one time and frequency resource is selected based on device type.

Embodiment A4. The network node of any one of Embodiments A1-A3, wherein the CRS signaling is a first radio access technology, RAT, CRS and the wireless device is a second RAT wireless device, the first RAT being different from the second RAT.

Embodiment A5. The network node of any one of Embodiments A1-A4, wherein the indication is provided in one of downlink control information, DCI, signaling and radio resource control, RRC, signaling.

Embodiment Bl. A method implemented in a network node that is configured to communicate with a wireless device, the method comprising: indicating, to the wireless device, whether at least one time and frequency resource for cell-specific reference signal, CRS, signaling is applicable for rate matching. Embodiment B2. The method of Embodiment Bl, wherein the at least one time and frequency resource for CRS signaling corresponds to a subset of at least one resource in a static CRS resource pattern.

Embodiment B3. The method of any one of Embodiments B1-B2, wherein the at least one time and frequency resource is selected based on device type.

Embodiment B4. The method of any one of Embodiments B1-B3, wherein the CRS signaling is a first radio access technology, RAT, CRS and the wireless device is a second RAT wireless device, the first RAT being different from the second RAT.

Embodiment B5. The method of any one of Embodiments B1-B4, wherein the indication is provided in one of downlink control information, DCI, signaling and radio resource control, RRC, signaling.

Embodiment Cl . A wireless device configured to communicate with a network node, the WD configured to, and/or comprising a radio interface and/or processing circuitry configured to: receive an indication whether at least one time and frequency resource for CRS signaling is applicable for rate matching; receive the CRS signaling; and perform rate matching based on the indication and the received CRS.

Embodiment C2. The wireless device of Embodiment Cl, wherein the CRS signaling corresponds to a static CRS resource pattern; and the at least one time and frequency resource for CRS signaling corresponds to a subset of at least one resource in the static CRS resource pattern. Embodiment C3. The wireless device of any one of Embodiments C1-C2, wherein the at least one time and frequency resource is selected based on device type.

Embodiment C4. The wireless device of any one of Embodiments C1-C3, wherein the CRS signaling is a first radio access technology, RAT, CRS and the wireless device is a second RAT wireless device, the first RAT being different from the second RAT.

Embodiment C5. The wireless device of any one of Embodiments C1-C4, wherein the indication is received in one of downlink control information, DCI, signaling and radio resource control, RRC, signaling.

Embodiment DI . A method implemented in a wireless device that is configured to communicate with a network node, the method comprising: receiving an indication whether at least one time and frequency resource for CRS signaling is applicable for rate matching; receiving the CRS signaling; and performing rate matching based on the indication and the received CRS signaling.

Embodiment D2. The method of Embodiment DI, wherein the CRS signaling corresponds to a static CRS resource pattern; and the at least one time and frequency resource for CRS signaling corresponds to a subset of at least one resource in the static CRS resource pattern.

Embodiment D3. The method of any one of Embodiments D1-D2, wherein the at least one time and frequency resource is selected based on device type. Embodiment D4. The method of any one of Embodiments D1-D3, wherein the CRS signaling is a first radio access technology, RAT, CRS and the wireless device is a second RAT wireless device, the first RAT being different from the second RAT.

Embodiment D5. The method of any one of Embodiments D1-D4, wherein the indication is received in one of downlink control information, DCI, signaling and radio resource control, RRC, signaling.