U.S. patent application number 17/711838 was filed with the patent office on 2022-07-21 for signaling radio transmission mapping types.
The applicant listed for this patent is Telefonaktiebolaget LM Ericsson (publ). Invention is credited to Robert BALDEMAIR, Stefan PARKVALL.
Application Number | 20220232538 17/711838 |
Document ID | / |
Family ID | |
Filed Date | 2022-07-21 |
United States Patent
Application |
20220232538 |
Kind Code |
A1 |
PARKVALL; Stefan ; et
al. |
July 21, 2022 |
SIGNALING RADIO TRANSMISSION MAPPING TYPES
Abstract
According to some embodiments, a wireless device is configured
to receive resource allocation information from a network node. The
wireless device comprises a radio interface and processing
circuitry configured to receive radio resource allocation
information for a wireless transmission. The radio resource
allocation information comprises one or more time-domain resources
for the wireless transmission and a mapping type for the wireless
transmission. The mapping type refers to a reference signal
placement within the wireless transmission (e.g., demodulation
reference signal (DMRS) mapping Type A or Type B). The radio
interface and processing circuitry are further configured to
interpret the received radio resource allocation information to
determine a mapping type for the wireless transmission.
Inventors: |
PARKVALL; Stefan; (BROMMA,
SE) ; BALDEMAIR; Robert; (SOLNA, SE) |
|
Applicant: |
Name |
City |
State |
Country |
Type |
Telefonaktiebolaget LM Ericsson (publ) |
Stockholm |
|
SE |
|
|
Appl. No.: |
17/711838 |
Filed: |
April 1, 2022 |
Related U.S. Patent Documents
|
|
|
|
|
|
Application
Number |
Filing Date |
Patent Number |
|
|
16894151 |
Jun 5, 2020 |
11310788 |
|
|
17711838 |
|
|
|
|
16441216 |
Jun 14, 2019 |
10701682 |
|
|
16894151 |
|
|
|
|
16274531 |
Feb 13, 2019 |
|
|
|
16441216 |
|
|
|
|
PCT/SE2018/051208 |
Nov 23, 2018 |
|
|
|
16274531 |
|
|
|
|
62590466 |
Nov 24, 2017 |
|
|
|
International
Class: |
H04W 72/04 20060101
H04W072/04; H04L 5/00 20060101 H04L005/00 |
Claims
1. A network node configured to signal resource allocation
information to a wireless device, the network node comprising a
radio interface and processing circuitry configured to: assemble
radio resource allocation information for a wireless transmission,
the radio resource allocation information indicating one or more
time-domain resources for the wireless transmission and a mapping
type for the wireless transmission, wherein the mapping type refers
to a reference signal placement within the wireless transmission;
and transmit the radio resource allocation information to a
wireless device.
2. The network node of claim 1, wherein the mapping type comprises
one of mapping type A or mapping type B, wherein mapping type A
refers to a demodulation reference signal (DMRS) placed relative to
the beginning of a slot, and mapping type B refers to a DMRS placed
at the beginning of transmitted data within a slot.
3. The network node of claim 1, wherein the mapping type is
associated with a physical downlink shared channel (PDSCH).
4. The network node of a claim 1, wherein the mapping type is
associated with a physical uplink shared channel (PUSCH).
5. The network node of a claim 1, wherein the one or more
time-domain resources for the wireless transmission comprise at
least one of a starting orthogonal division frequency multiplexing
(OFDM) symbol for the wireless transmission and a duration of the
wireless transmission.
6. The network node of claim 5, wherein the duration of the
wireless transmission is specified by one of a number of OFDM
symbols for the wireless transmission or an ending OFDM symbol.
7. The network node of a claim 1, wherein the mapping type is
implicitly determined based on the one or more time-domain
resources for the wireless transmission.
8. The network node of claim 1, wherein the radio interface and
processing circuitry are configured to transmit the radio resource
allocation information to the wireless device by transmitting
downlink control information (DCI) to the wireless device, the DCI
comprising an index that identifies a particular radio resource
allocation information of a predefined set of radio resource
allocation information.
9. A method performed by a network node for signaling resource
allocation information to a wireless device, the method comprising:
assembling radio resource allocation information for a wireless
transmission, the radio resource allocation information indicating
one or more time-domain resources for the wireless transmission and
a mapping type for the wireless transmission, wherein the mapping
type refers to a reference signal placement within the wireless
transmission; and transmitting the radio resource allocation
information to a wireless device.
10. The method of claim 9, wherein the mapping type comprises one
of mapping type A or mapping type B, wherein mapping type A refers
to a demodulation reference signal (DMRS) placed relative to the
beginning of a slot, and mapping type B refers to a DMRS placed at
the beginning of transmitted data within a slot.
11. The method of claim 9, wherein the mapping type is associated
with a physical downlink shared channel (PDSCH).
12. The method of claim 9, wherein the mapping type is associated
with a physical uplink shared channel (PUSCH).
13. The method of claim 9, wherein the one or more time-domain
resources for the wireless transmission comprise at least one of a
starting orthogonal division frequency multiplexing (OFDM) symbol
for the wireless transmission and a duration of the wireless
transmission.
14. The method of claim 13, wherein the duration of the wireless
transmission is specified by one of a number of OFDM symbols for
the wireless transmission or an ending OFDM symbol.
15. The method of claim 9, wherein the mapping type is implicitly
determined based on the one or more time-domain resources for the
wireless transmission.
16. The method of claim 9, wherein transmitting the radio resource
allocation information to the wireless device comprises
transmitting downlink control information (DCI) to the wireless
device, the DCI comprising an index that identifies a particular
radio resource allocation information of a predefined set of radio
resource allocation information.
17. A wireless device configured to receive resource allocation
information from a network node, the wireless device comprising a
radio interface and processing circuitry configured to: receive
radio resource allocation information for a wireless transmission,
the radio resource allocation information indicating one or more
time-domain resources for the wireless transmission and a mapping
type for the wireless transmission, wherein the mapping type refers
to a reference signal placement within the wireless transmission;
and interpret the received radio resource allocation information to
determine a mapping type for the wireless transmission.
18. The wireless device of claim 1, wherein the mapping type
comprises one of mapping type A or mapping type B, wherein mapping
type A refers to a demodulation reference signal (DMRS) placed
relative to the beginning of a slot, and mapping type B refers to a
DMRS placed at the beginning of transmitted data within a slot.
19. The wireless device of claim 17, wherein the mapping type is
associated with a physical downlink shared channel (PDSCH).
20. The wireless device of claim 17, wherein the mapping type is
associated with a physical uplink shared channel (PUSCH).
21. The wireless device of claim 17, wherein the one or more
time-domain resources for the wireless transmission comprise at
least one of a starting orthogonal division frequency multiplexing
(OFDM) symbol for the wireless transmission and a duration of the
wireless transmission.
22. The wireless device of claim 21, wherein the duration of the
wireless transmission is specified by one of a number of OFDM
symbols for the wireless transmission or an ending OFDM symbol.
23. The wireless device claim 17, wherein the radio interface and
processing circuitry are configured to determine the mapping type
based on the one or more time-domain resources for the wireless
transmission.
24. The wireless device of claim 17, wherein the radio interface
and processing circuitry receive the radio resource allocation
information by receiving downlink control information (DCI) from
the network node, the DCI comprising an index that identifies a
particular radio resource allocation information of a predefined
set of radio resource allocation information, and wherein the radio
interface and processing circuitry are configured to interpret the
received radio resource allocation information by using the index
to determine the particular radio resource allocation information
and determine the mapping type using the particular radio resource
allocation information.
25. A method in a wireless device for receiving resource allocation
information from a network node, the method comprising: receiving
radio resource allocation information for a wireless transmission,
the radio resource allocation information indicating one or more
time-domain resources for the wireless transmission and a mapping
type for the wireless transmission, wherein the mapping type refers
to a reference signal placement within the wireless transmission;
and interpreting the received radio resource allocation information
to determine a mapping type for the wireless transmission.
26. The method of claim 25, wherein the mapping type comprises one
of mapping type A or mapping type B, wherein mapping type A refers
to a demodulation reference signal (DMRS) placed relative to the
beginning of a slot, and mapping type B refers to a DMRS placed at
the beginning of transmitted data within a slot.
27. The method of claim 25, wherein the mapping type is associated
with a physical downlink shared channel (PDSCH).
28. The method of claim 25, wherein the mapping type is associated
with a physical uplink shared channel (PUSCH).
29. The method of claim 25, wherein the one or more time-domain
resources for the wireless transmission comprise at least one of a
starting orthogonal division frequency multiplexing (OFDM) symbol
for the wireless transmission and a duration of the wireless
transmission.
30. The method of claim 29, wherein the duration of the wireless
transmission is specified by one of a number of OFDM symbols for
the wireless transmission or an ending OFDM symbol.
31.-34. (canceled)
Description
PRIORITY
[0001] This application is a continuation, under 35 U.S.C. .sctn.
120 of U.S. patent application Ser. No. 16/894,151 filed Jun. 5,
2020; which is a continuation, under 35 U.S.C. .sctn. 120 of U.S.
patent application Ser. No. 16/441,216 filed on Jun. 14, 2019, now
U.S. Pat. No. 10,701,682; which is a continuation, under 35 U.S.C.
.sctn. 120 of U.S. patent application Ser. No. 16/274,531 filed on
Feb. 13, 2019, now abandoned; which is a continuation, under 35
U.S.C. .sctn. 120 of International Patent Application Serial No.
PCT/SE2018/051208 filed Nov. 23, 2018 and entitled "SIGNALING RADIO
TRANSMISSION MAPPING TYPES" which claims priority to U.S.
Provisional Patent Application No. 62/590,466 filed Nov. 24, 2017
all of which are hereby incorporated by reference in their
entirety.
TECHNICAL FIELD
[0002] Embodiments of the present disclosure are directed to
wireless communications and, more particularly, to methods and
apparatus for signaling mapping type information, such as physical
downlink shared channel (PDSCH) mapping type A or type B.
BACKGROUND
[0003] 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, step, etc. are to be
interpreted openly as referring to at least one instance of the
element, apparatus, component, means, step, etc., unless explicitly
stated otherwise. The steps of any methods disclosed herein do not
have to be performed in the exact order disclosed, unless a step is
explicitly described as following or preceding another step and/or
where it is implicit that a step must follow or precede another
step. 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.
[0004] Third generation Partnership Project (3GPP) fifth generation
(5G) systems (e.g., new radio (NR)), may use one or more mapping
types for uplink and downlink radio transmissions. An example of
mapping type information is information indicating whether physical
downlink shared channel (PDSCH) is mapping type A or mapping type
B.
[0005] While certain embodiments are described with respect to
PDSCH mapping types A and B, particular embodiments may apply to
other mapping type information and other mapping types, such as
mapping types for uplink communication, such as physical uplink
shared channel (PUSCH).
[0006] Downlink data transmission in NR may start at the beginning
of a slot or may start at a later position within the slot.
Similarly, the data transmission may end before the end of the
slot. This is sometimes referred to (not necessarily in a very
careful manner) as "slot-based" and "mini-slot" or "non-slot-based"
transmission, respectively. NR specifications include two different
PDSCH mapping types, type A and type B. The difference between the
two is the placement of the downlink demodulation reference signal
(DM-RS).
[0007] In mapping type A, the DM-RS is placed at the beginning of
the slot, either at the third or fourth orthogonal frequency
division multiplexing (OFDM) symbol (signaled on the physical
broadcast channel (PBCH)). In mapping type B, the DM-RS is placed
at the beginning of the transmitted data. Thus, mapping type A is
suitable for slot-based transmission and mapping type B may be used
for non-slot-based transmission (although in principle it can be
used for any transmission length).
[0008] A user equipment (UE) needs to know whether PDSCH mapping
type A or B is used for a particular transmission. Current NR
specifications and agreements do not specify how to indicate to the
UE whether PDSCH mapping type A or B is used.
[0009] One possibility is semi-static configuration of the mapping
type. For this to work, a default mapping type is defined and used
for the initial configuration signaling form the network. Given NR
agreements that system information can be transmitted using
mini-slots, type B has to be the default.
[0010] Another possibility is to indicate in the downlink control
information (DCI) the mapping type used. This approach may provide
a large amount of flexibility at the cost of one DCI bit. As stated
above, downlink data transmissions have some flexibility in the
starting position in a slot, as well as the number of OFDM symbols
used for the transmission. It has been agreed to signal the start
and length through a table (i.e., the DCI contains an index which
selects one of a plurality of entries in a (configurable) table).
As an example, 3 bits may be used for the index giving 8 different
possibilities of starting position/length for downlink data
transmission.
[0011] Some proposals may include multiple time allocation tables,
for example, one for slot-based transmission and one for
non-slot-based transmission. In these proposals, the bit indicating
PDSCH mapping type A or B may be used to select the time allocation
table to use.
SUMMARY
[0012] As described above, separate signaling of type A/B and the
time allocation index may lead to inflexible system operation. If a
particular network deployment only uses one of the mapping types
(e.g., A), then there is a cost of n bits in the downlink control
information (DCI) but only n-1 of the bits is used to indicate the
time allocation, essentially wasting one bit of DCI
information.
[0013] According to some embodiments, a mapping type information
(e.g., indication of physical downlink shared channel (PDSCH)
mapping type A/B or other mapping type, such as for physical uplink
shared channel (PUSCH)) is included in resource allocation
information (or other system information) (e.g., a time allocation
table or a time-domain resource allocation table).
[0014] According to some embodiments, a network node is configured
to signal resource allocation information to a wireless device. The
network node comprises a radio interface and processing circuitry
configured to assemble radio resource allocation information for a
wireless transmission. The radio resource allocation information
comprises one or more time-domain resources for the wireless
transmission and a mapping type for the wireless transmission. The
mapping type refers to a reference signal placement within the
wireless transmission. The radio interface and processing circuitry
are further configured to transmit the radio resource allocation
information to a wireless device.
[0015] In particular embodiments, the radio interface and
processing circuitry are configured to transmit the radio resource
allocation information to the wireless device by transmitting DCI
to the wireless device. The DCI comprises an index that identifies
a particular radio resource allocation information of a predefined
set of radio resource allocation information.
[0016] According to some embodiments, a method performed by a
network node for signaling resource allocation information to a
wireless device comprises assembling radio resource allocation
information for a wireless transmission. The radio resource
allocation information comprises one or more time-domain resources
for the wireless transmission and a mapping type for the wireless
transmission. The mapping type refers to a reference signal
placement within the wireless transmission. The method further
comprises transmitting the radio resource allocation information to
a wireless device.
[0017] In particular embodiments, transmitting the radio resource
allocation information to the wireless device comprises
transmitting DCI to the wireless device. The DCI comprises an index
that identifies a particular radio resource allocation information
of a predefined set of radio resource allocation information.
[0018] According to some embodiments, a wireless device is
configured to receive resource allocation information from a
network node. The wireless device comprises a radio interface and
processing circuitry configured to receive radio resource
allocation information for a wireless transmission. The radio
resource allocation information comprises one or more time-domain
resources for the wireless transmission and a mapping type for the
wireless transmission. The mapping type refers to a reference
signal placement within the wireless transmission. The radio
interface and processing circuitry are further configured to
interpret the received radio resource allocation information to
determine a mapping type for the wireless transmission.
[0019] In particular embodiments, the radio interface and
processing circuitry are configured to determine the mapping type
based on the one or more time-domain resources for the wireless
transmission.
[0020] In particular embodiments, the radio interface and
processing circuitry receive the radio resource allocation
information by receiving DCI from the network node. The DCI
comprises an index that identifies a particular radio resource
allocation information of a predefined set of radio resource
allocation information. The radio interface and processing
circuitry are configured to interpret the received radio resource
allocation information by using the index to determine the
particular radio resource allocation information and determine the
mapping type using the particular radio resource allocation
information.
[0021] According to some embodiments, a method in a wireless device
for receiving resource allocation information from a network node
comprises receiving radio resource allocation information for a
wireless transmission. The radio resource allocation information
comprises one or more time-domain resources for the wireless
transmission and a mapping type for the wireless transmission. The
mapping type refers to a reference signal placement within the
wireless transmission. The method further comprises interpreting
the received radio resource allocation information to determine a
mapping type for the wireless transmission.
[0022] In particular embodiments, determining the mapping type is
based on the one or more time-domain resources for the wireless
transmission.
[0023] In particular embodiments, receiving the radio resource
allocation information comprises receiving DCI from the network
node. The DCI comprises an index that identifies a particular radio
resource allocation information of a predefined set of radio
resource allocation information. Interpreting the received radio
resource allocation information comprises using the index to
determine the particular radio resource allocation information and
determine the mapping type using the particular radio resource
allocation information.
[0024] In particular embodiments, the mapping type comprises one of
mapping type A or mapping type B. Mapping type A refers to a
demodulation reference signal (DMRS) placed relative to the
beginning of a slot, and mapping type B refers to a DMRS placed at
the beginning of transmitted data within a slot. The mapping type
may be associated with PDSCH or PUSCH.
[0025] In particular embodiments, the one or more time-domain
resources for the wireless transmission comprise at least one of a
starting orthogonal frequency division multiplexing (OFDM) symbol
for the wireless transmission and a duration of the wireless
transmission. The duration of the wireless transmission may be
specified by one of a number of OFDM symbols for the wireless
transmission or an ending OFDM symbol.
[0026] In particular embodiments, the mapping type is implicitly
determined based on the one or more time-domain resources for the
wireless transmission.
[0027] According to some embodiments, a network node is configured
to signal resource allocation information to a wireless device. The
network node comprises a resource allocation module and a radio
interface module. The resource allocation module is operable to
assemble radio resource allocation information for a wireless
transmission. The radio resource allocation information comprising
one or more time-domain resources for the wireless transmission and
a mapping type for the wireless transmission. The mapping type
refers to a reference signal placement within the wireless
transmission. The radio interface module is operable to transmit
the radio resource allocation information to a wireless device.
[0028] According to some embodiments, a wireless device is
configured to receive resource allocation information from a
network node. The wireless device comprises a radio interface
module and a resource interpreter module. The radio interface
module is operable to receive radio resource allocation information
for a wireless transmission. The radio resource allocation
information comprises one or more time-domain resources for the
wireless transmission and a mapping type for the wireless
transmission. The mapping type refers to a reference signal
placement within the wireless transmission. The resource
interpreter module is operable to interpret the received radio
resource allocation information to determine a mapping type for the
wireless transmission.
[0029] Also disclosed is a computer program product comprising a
non-transitory computer readable medium storing computer readable
program code, the computer readable program code operable, when
executed by processing circuitry to perform any of the methods
performed by the wireless device described above.
[0030] Another computer program product comprises a non-transitory
computer readable medium storing computer readable program code,
the computer readable program code operable, when executed by
processing circuitry to perform any of the methods performed by the
network node described above.
[0031] Certain embodiments may provide one or more of the following
technical advantage(s). Particular embodiments provide for
signaling mapping type information, such as for PDSCH, PUSCH or
other mapping type.
BRIEF DESCRIPTION OF THE DRAWINGS
[0032] For a more complete understanding of the disclosed
embodiments and their features and advantages, reference is now
made to the following description, taken in conjunction with the
accompanying drawings, in which:
[0033] FIG. 1 is a schematic diagram of an example network
architecture illustrating a telecommunication network connected via
an intermediate network to a host computer, according to some
embodiments;
[0034] FIG. 2 is a block diagram illustrating three examples of a
PDSCH start value relative to a PDCCH/CORESET;
[0035] FIG. 3 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;
[0036] FIG. 4 is a block diagram of an alternative embodiment of a
network node, according to some embodiments;
[0037] FIG. 5 is a block diagram of an alternative embodiment of a
wireless device, according to some embodiments;
[0038] FIG. 6 is a block diagram of an alternative embodiment of a
host computer, according to some embodiments;
[0039] FIGS. 7-10 are flow charts illustrating example methods
implemented in a communication system including a host computer, a
network node and a wireless device, according to some
embodiments;
[0040] FIG. 11 is a flowchart of an example process in a network
node for generating and signaling a resource allocation information
(or other system information) according to some embodiments;
and
[0041] FIG. 12 is a flowchart of an example process in a wireless
device for receiving and processing a resource allocation
information (or other system information) according to some
embodiments.
DETAILED DESCRIPTION
[0042] As described above, certain challenges currently exist with
signaling mapping type information in Third Generation Partnership
Project (3GPP) fifth generation (5G) new radio (NR). For example,
separate signaling of physical downlink shared channel (PDSCH) type
A/B and the time allocation index may lead to inflexible system
operation. If a particular network deployment uses only one of the
mapping types (e.g., A), then there is a cost of n bits in the
downlink control information (DCI) but only n-1 of the bits may be
used to indicate the time allocation, essentially wasting one bit
of DCI information.
[0043] According to some embodiments, a mapping type information
(e.g., indication PDSCH mapping type A/B or other mapping type,
such as for physical uplink shared channel (PUSCH)) is included in
resource allocation information (or other system information)
(e.g., a time allocation table or a time-domain resource allocation
table). Some embodiments include methods, wireless devices and
network nodes for signaling mapping type information together with
resource allocation information, rather than separately.
[0044] Before describing particular embodiments in detail,
generally the embodiments reside primarily in combinations of
apparatus components and processing steps related to methods and
apparatuses for signaling of a mapping type. Accordingly,
components are 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.
[0045] 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 describing particular embodiments
only and is not intended limit the concepts described herein.
[0046] 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. 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.
[0047] The joining 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 to achieve the electrical
and data communication.
[0048] In some embodiments described herein, the term "coupled,"
"connected," and the like, may be used to indicate a connection,
although not necessarily directly, and may include wired and/or a
wireless connection.
[0049] The term "network node" may be any kind of network node
comprised in a radio network which may further comprise any of base
station (BS), radio base station, base transceiver station (BTS),
base station controller (BSC), radio network controller (RNC), g
Node B (gNB), evolved Node B (eNB or eNodeB), Node B,
multi-standard radio (MSR) radio node such as MSR BS,
multi-cell/multicast coordination entity (MCE), relay node, 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.
[0050] 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. 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), USB
dongles, Customer Premises Equipment (CPE), an Internet of Things
(IoT) device, or a Narrowband IoT (NB-IOT) device, etc.
[0051] 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), relay node, access point, radio access point, Remote Radio
Unit (RRU) Remote Radio Head (RRH).
[0052] Although terminology from one particular wireless system,
such as, for example, 3GPP LTE, 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.
[0053] 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.
[0054] 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.
[0055] Certain embodiments provide methods, wireless devices and
network nodes for methods and apparatuses for signaling of mapping
type information, such as PDSCH mapping type. According to some
embodiments disclosed herein, indication of the PDSCH mapping type
A/B is included in the time allocation table or a time-domain
resource allocation table.
[0056] Returning 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, according to an
embodiment, including a communication system 10, such as a
3GPP-type cellular network, 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.
[0057] A first wireless device (WD) 22a located in coverage area
18a is configured to wirelessly connect to, or be paged by, the
corresponding network node 16c. A second WD 22b in coverage area
18b is wirelessly connectable to the corresponding network node
16a. While a plurality of WDs 22a, 22b (collectively referred to as
wireless devices 22) are illustrated in this example, the disclosed
embodiments are equally applicable to a situation where a sole WD
22 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.
[0058] 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).
[0059] The communication system of FIG. 1 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 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.
[0060] A network node 16 is configured to include a resource
allocation information (or other system information) generator 32,
which is configured to generate a resource allocation information
(or other system information), including mapping type information.
Alternatively (not shown), mapping type information may be included
in resource allocation information (or other system information)
not at the network node but elsewhere, and the combined system
information may be provided to the network node 16. A wireless
device 22 is configured to include a resource allocation
information (or other system information) interpreter 34, which is
configured to interpret resource allocation information (or other
system information) received from the network node 16.
[0061] 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.
3. 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 a traditional
processor and memory, the processing circuitry 44 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).
[0062] 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.
[0063] Thus, the host computer 24 may further comprise software
(SW) 48, which is stored in, for example, memory 46 at the host
computer 24, or stored in external memory (e.g., database)
accessible by 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. 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 be configured to enable the service provider to
observe functionality of and process data from the network node 16
and/or the wireless device 22.
[0064] The communication system 10 further includes a network node
16 provided in a telecommunication system 10 and comprising
hardware 54 enabling it to communicate with the host computer 24
and with the WD 22. The hardware 54 may include a communication
interface 56 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 58 for
setting up and maintaining at least a wireless connection 60 with a
WD 22 located in a coverage area 18 served by the network node 16.
The radio interface 58 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 56
may be configured to facilitate a connection 61 to the host
computer 24. The connection 61 may be direct or it may pass through
a core network 14 of the telecommunication system 10 and/or through
one or more intermediate networks 30 outside the telecommunication
system 10.
[0065] In the embodiment shown, the hardware 54 of the network node
16 further includes processing circuitry 62. The processing
circuitry 62 may include a processor 64 and a memory 66. In
particular, in addition to a traditional processor and memory, the
processing circuitry 62 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 64 may be configured to access
(e.g., write to and/or read from) the memory 66, 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).
[0066] Thus, the network node 16 further has software 94 stored
internally in, for example, memory 66 or stored in external memory
(e.g., database) accessible by the network node 16 via an external
connection. The software 68 may be executable by the processing
circuitry 62. The processing circuitry 62 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 64 corresponds to one or more processors
64 for performing network node 16 functions described herein. The
memory 68 is configured to store data, programmatic software code
and/or other information described herein. In some embodiments, the
software 68 may include instructions that, when executed by the
processor 64 and/or processing circuitry 62, causes the processor
64 and/or processing circuitry 62 to perform the processes
described herein with respect to network node 16. For example,
processing circuitry 62 of the network node 16 may include a port
index generator 32 to generate a port index indication.
[0067] The communication system 10 further includes the WD 22
already referred to. The WD 22 may have hardware 70 that may
include a radio interface 72 configured to set up and maintain a
wireless connection 60 with a network node 16 serving a coverage
area 18 in which the WD 22 is currently located. The radio
interface 72 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.
[0068] The hardware 70 of the WD 22 further includes processing
circuitry 74. The processing circuitry 74 may include a processor
76 and memory 78. In particular, in addition to a traditional
processor and memory, the processing circuitry 74 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 76 may be configured to access (e.g., write to and/or
read from) memory 78, 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).
[0069] Thus, the WD 22 further comprises software 80, which is
stored in, for example, memory 78 at the WD 22, or stored in
external memory (e.g., database) accessible by the WD 22. The
software 80 may be executable by the processing circuitry 74. The
software 80 includes a client application 82. The client
application 82 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 82 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 82 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 82 may interact with the user to generate the user data
that it provides.
[0070] Processing circuitry 74 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.
Processor 108 corresponds to one or more processors 76 for
performing WD 22 functions described herein. The WD 22 includes
memory 78 that is configured to store data, programmatic software
code and/or other information described herein. In some
embodiments, the software 80 and/or the client application 82 may
include instructions that, when executed by the processor 76 and/or
processing circuitry 74, causes the processor 76 and/or processing
circuitry 74 to perform the processes described herein with respect
to WD 22. For example, the processing circuitry 74 of the wireless
device 22 may be configured to implement a resource allocation
information (or other system information) interpreter 34 to
interpret (process) resource allocation information (or other
system information).
[0071] Embodiments discussed herein provide methods and apparatuses
that may allow for a system with improved efficiency. According to
some embodiments, the resource allocation information (or other
system information) may be a time allocation table or a time-domain
resource allocation table. According to some embodiments, the
resource allocation information (or other system information) may
be Downlink Control Information (DCI). The mapping type information
may comprise information indicating PDSCH mapping type A or B.
[0072] According to some embodiments, the PDSCH mapping type (A or
B) is part of a time allocation table. The table may be partially
or fully configurable, but at least one entry has a default
configuration for the system to be able to transmit configuration
information to a wireless device, such as WD 22. This is true in
general and not related to the mapping type only.
[0073] According to some embodiments, upon reception of a DCI, WD
22 interprets the information by using the time allocation field of
size n bits as a pointer into the table to get the time allocation
information, the mapping type, and possibly other information.
[0074] An example of such a table is shown below with the mapping
type in the last column. As an alternative to providing the
transmission length, the end position of the transmission may be
provided.
[0075] In one embodiment, the mapping type is explicitly configured
(or specified) in the table. In another embodiment, the mapping
type may be derived from the time allocation. For example, all time
allocations starting later than a certain OFDM symbol number would
correspond to mapping type B, while allocations starting earlier
that this OFDM symbol would use allocation type A. This would
reduce the amount of configuration information slightly at the cost
of reduced flexibility.
[0076] In some embodiments, depending on the PDSCH mapping type,
the start (and end field if present) field may be absolute or
relative. An absolute indication provides the starting symbol as
symbol number within a slot, while a relative indication is
relative to the scheduling PDCCH/CORESET. Absolute indication may
be more suitable for Type A while relative indication may be more
suitable for Type B. In principle, absolute and relative
indications may be configured individually for each table entry (or
linked to the A/B mapping). All entries may also be specified with
respect to same scheme, i.e. either absolute or relative.
[0077] In the example of Table 1 below, Index 0 and 1 refer to Type
A mapping (complete slot and almost complete slot with late start).
The last two rows refer to Type B mapping. All entries assume
absolute time indication.
TABLE-US-00001 TABLE 1 Starting OFDM Length in OFDM PDSCH mapping
Index symbol symbols type A or B 0 0 14 Type A 1 3 11 Type A 2 5 6
Type B 3 9 10 Type B . . .
[0078] Another example is shown in Table 2 below where the Type B
mapping assumes relative time indication. The starting OFDM symbol
is therefore relative to the PDCCH/COREST symbol.
TABLE-US-00002 TABLE 2 Starting OFDM Length in OFDM PDSCH mapping
Index symbol symbols type A or B 0 0 14 Type A 1 3 11 Type A 2 0 2
Type B 3 0 4 Type B . . .
[0079] For downlink, depending how PDCCH/CORSET and PDSCH overlap,
a relative start value can be interpreted differently. An NR
specification may define how to handle the overlap case. FIG. 2
illustrates some examples.
[0080] FIG. 2 is a block diagram illustrating three examples of a
PDSCH start value relative to a PDCCH/CORESET. Example (A) does not
include overlap. Starting symbol 0 means that the starting symbol
for PDSCH 4 is the same symbol as the starting symbol for PSCCH 2.
Example (B) includes overlap. Starting symbol 0 means that the
starting symbol for PDSCH 4 is the first symbol after PDCCH 2.
Example (C) also includes overlap. Starting symbol 0 means that the
starting symbol for PDSCH 4 is the same symbol as the starting
symbol for PSCCH 2, and PDSCH 4 is rate matched around PDCCH 2.
[0081] Particular embodiments may include mapping type information
in a resource allocation information (or other system information).
Some embodiments use mapping type information included in a
resource allocation information (or other system information). Some
embodiments facilitate improved radio system efficiency.
[0082] Although some embodiments of this disclosure have been
described from a downlink perspective (e.g., PDSCH), the same
approach can be applied to uplink transmissions (e.g., PUSCH) where
multiple mapping types also are present.
[0083] Although some embodiments of this disclosure describe
including mapping type information in a resource allocation
information (or other system information), mapping type information
may be transmitted together with resource allocation information
(e.g., time index in time allocation table) in alternate ways.
[0084] As will be appreciated by one of skill in the art, the
concepts described herein may be embodied as a method, data
processing system, and/or computer program product. 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." 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.
[0085] In some embodiments, the inner workings of the network node
16, WD 22, and host computer 24 may be as shown in FIG. 3 and
independently, the surrounding network topology may be that of FIG.
1.
[0086] In FIG. 3, 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).
[0087] The wireless connection 60 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
60 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.
[0088] In some embodiments, a measurement procedure may be provided
for 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 80 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, 80 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 22 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, 80 causes messages to
be transmitted, in particular empty or `dummy` messages, using the
OTT connection 52 while it monitors propagation times, errors
etc.
[0089] FIG. 4 is a block diagram of an alternative host computer
24, which may be implemented at least in part by software modules
containing software executable by a processor to perform the
functions described herein. The host computer 24 include a
communication interface module 41 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 memory
module 47 is configured to store data, programmatic software code
and/or other information described herein.
[0090] FIG. 5 is a block diagram of an alternative network node 16,
which may be implemented at least in part by software modules
containing software executable by a processor to perform the
functions described herein. The network node 16 includes a radio
interface module 59 configured for setting up and maintaining at
least a wireless connection 60 with a WD 22 located in a coverage
area 18 served by the network node 16. The network node 16 also
includes a communication interface module 57 configured for setting
up and maintaining a wired or wireless connection with an interface
of a different communication device of the communication system 10.
The communication interface module 57 may also be configured to
facilitate a connection 54 to the host computer 24. The memory
module 67 that is configured to store data, programmatic software
code and/or other information described herein. The resource
allocation information (or other system information) generation
module 33 is configured to generate a resource allocation
information (or other system information).
[0091] FIG. 6 is a block diagram of an alternative wireless device
22, which may be implemented at least in part by software modules
containing software executable by a processor to perform the
functions described herein. The WD 22 includes a radio interface
module 73 configured to set up and maintain a wireless connection
60 with a network node 16 serving a coverage area 18 in which the
WD 22 is currently located. The memory module 79 is configured to
store data, programmatic software code and/or other information
described herein. The resource allocation information (or other
system information) interpreter module 35 is configured to
interpret (process) resource allocation information (or other
system information). The interpretation may comprise interpreting
mapping information included in (or transmitted together with, by
the network node 16) the resource allocation information (or other
system information).
[0092] FIG. 7 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
FIG. 1.
[0093] In a first step of the method, the host computer 24 provides
user data (block S100). 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 74 (block
S102). In a second step, the host computer 24 initiates a
transmission carrying the user data to the WD 22 (block S104). 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 22 initiated, in accordance with the teachings of the
embodiments described throughout this disclosure (block S106). In
an optional fourth step, the WD 22 executes a client application,
such as, for example, the client application 114, associated with
the host application 74 executed by the host computer 24 (block
S108).
[0094] FIG. 8 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
FIG. 1.
[0095] In a first step of the method, the host computer 24 provides
user data (block S110). 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 74. In a second step,
the host computer 24 initiates a transmission carrying the user
data to the WD 22 (block S112). 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 S114).
[0096] FIG. 9 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
FIG. 1.
[0097] In an optional first step of the method, the WD 22 receives
input data provided by the host computer 24 (block S116).
Additionally or alternatively, in an optional second step, the WD
22 provides user data (block S120). In an optional substep of the
second step, the WD provides the user data by executing a client
application, such as, for example, client application 114 (block
S118). In a further optional substep of the first step, the WD 22
executes the client application 114, which provides the user data
in reaction to the received input data provided by the host
computer 24 (block S122). In providing the user data, the executed
client application 114 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).
[0098] FIG. 10 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
FIG. 1. 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 S128). 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).
[0099] FIG. 11 is a flowchart of an exemplary process in a network
node 16 for generating and signaling a port index indication
according to some embodiments of the present disclosure. The
process includes including, via the resource allocation information
(or other system information) generator 32, a mapping type
information in a resource allocation information (or other system
information) (block S134).
[0100] For example, network node 16 may assemble radio resource
allocation information for a wireless transmission. The radio
resource allocation information comprises one or more time-domain
resources for the wireless transmission and a mapping type for the
wireless transmission. The mapping type refers to a reference
signal placement within the wireless transmission.
[0101] The mapping type may comprise one of mapping type A or
mapping type B. Mapping type A refers to a DMRS placed at the
beginning of a slot, and mapping type B refers to a DMRS placed at
the beginning of transmitted data within a slot. The mapping type
may be associated with a PDSCH or PUSCH.
[0102] The one or more time-domain resources for the wireless
transmission may comprise one of a starting OFDM symbol for the
wireless transmission and a duration of the wireless transmission.
The duration of the wireless transmission may be specified by one
of a number of OFDM symbols for the wireless transmission or an
ending OFDM symbol.
[0103] The process also includes signaling, via the radio interface
58, the resource allocation information (or other system
information) to a wireless device (block S136). For example,
network node 16 may transmit the radio resource allocation
information to wireless device 22. In some embodiments, the network
node may transmit DCI to the wireless device. The DCI may comprise
an index that identifies a particular radio resource allocation
information of a predefined set radio resource allocation
information (e.g., Tables 1 and 2 described above).
[0104] Modifications, additions, or omissions may be made to the
method of FIG. 11. Additionally, one or more steps in the method of
FIG. 11 may be performed in parallel or in any suitable order.
[0105] FIG. 12 is a flowchart of an example process in a wireless
device 22 for receiving and processing (or interpreting) a resource
allocation information (or other system information) according to
some embodiments of the present disclosure. The process includes
receiving, via the radio interface 72, a resource allocation
information (or other system information) including mapping type
information from a network node 16 (block S144).
[0106] For example, wireless device 22 may receive radio resource
allocation information for a wireless transmission. The radio
resource allocation information comprises one or more time-domain
resources for the wireless transmission and a mapping type for the
wireless transmission. The mapping type refers to a reference
signal placement within the wireless transmission.
[0107] The mapping type may comprise one of mapping type A or
mapping type B. Mapping type A refers to a DMRS placed at the
beginning of a slot, and mapping type B refers to a DMRS placed at
the beginning of transmitted data within a slot. The mapping type
may be associated with a PDSCH or PUSCH.
[0108] The one or more time-domain resources for the wireless
transmission may comprise one of a starting OFDM symbol for the
wireless transmission and a duration of the wireless transmission.
The duration of the wireless transmission may be specified by one
of a number of OFDM symbols for the wireless transmission or an
ending OFDM symbol.
[0109] The process also includes interpreting, via the resource
allocation information (or other system information) interpreter
34, interpreting the resource allocation information (or other
system information) (block S146). The interpretation may comprise
interpreting mapping information included in (or transmitted
together) the resource allocation information (or other system
information).
[0110] For example, wireless device 22 may interpret the received
radio resource allocation information to determine a mapping type
for the wireless transmission. The wireless device may receive DCI
from the network node. The DCI may comprise an index that
identifies a particular radio resource allocation information of a
predefined set radio resource allocation information. The wireless
device may be configured to interpret the received radio resource
allocation information by using the index to determine the
particular radio resource allocation information and determine the
mapping type using the particular radio resource allocation
information.
[0111] Modifications, additions, or omissions may be made to the
method of FIG. 12. Additionally, one or more steps in the method of
FIG. 12 may be performed in parallel or in any suitable order.
[0112] 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, 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.
[0113] 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.
[0114] 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.
[0115] 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.
[0116] Computer program code for carrying out operations of the
concepts described herein may be written in an object-oriented
programming language such as Java.RTM. 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).
[0117] 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.
[0118] 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.
[0119] The term unit may have conventional meaning in the field of
electronics, electrical devices and/or electronic devices and may
include, for example, electrical and/or electronic circuitry,
devices, modules, processors, memories, logic solid state and/or
discrete devices, computer programs or instructions for carrying
out respective tasks, procedures, computations, outputs, and/or
displaying functions, and so on, as such as those that are
described herein.
[0120] 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, step, etc. are to be
interpreted openly as referring to at least one instance of the
element, apparatus, component, means, step, etc., unless explicitly
stated otherwise. The steps of any methods disclosed herein do not
have to be performed in the exact order disclosed, unless a step is
explicitly described as following or preceding another step and/or
where it is implicit that a step must follow or precede another
step. 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.
[0121] Modifications, additions, or omissions may be made to the
systems and apparatuses disclosed herein without departing from the
scope of the invention. The components of the systems and
apparatuses may be integrated or separated. Moreover, the
operations of the systems and apparatuses may be performed by more,
fewer, or other components. Additionally, operations of the systems
and apparatuses may be performed using any suitable logic
comprising software, hardware, and/or other logic. As used in this
document, "each" refers to each member of a set or each member of a
subset of a set.
[0122] Modifications, additions, or omissions may be made to the
methods disclosed herein without departing from the scope of the
invention. The methods may include more, fewer, or other steps.
Additionally, steps may be performed in any suitable order.
[0123] The foregoing description sets forth numerous specific
details. It is understood, however, that embodiments may be
practiced without these specific details. In other instances,
well-known circuits, structures and techniques have not been shown
in detail in order not to obscure the understanding of this
description. Those of ordinary skill in the art, with the included
descriptions, will be able to implement appropriate functionality
without undue experimentation.
[0124] References in the specification to "one embodiment," "an
embodiment," "an example embodiment," etc., indicate that the
embodiment described may include a particular feature, structure,
or characteristic, but every embodiment may not necessarily include
the particular feature, structure, or characteristic. Moreover,
such phrases are not necessarily referring to the same embodiment.
Further, when a particular feature, structure, or characteristic is
described in connection with an embodiment, it is submitted that it
is within the knowledge of one skilled in the art to implement such
feature, structure, or characteristic in connection with other
embodiments, whether or not explicitly described.
[0125] Although this disclosure has been described in terms of
certain embodiments, alterations and permutations of the
embodiments will be apparent to those skilled in the art.
Accordingly, the above description of the embodiments does not
constrain this disclosure. Other changes, substitutions, and
alterations are possible without departing from the spirit and
scope of this disclosure, as defined by the claims below.
[0126] At least some of the following abbreviations may be used in
this disclosure. If there is an inconsistency between
abbreviations, preference should be given to how it is used above.
If listed multiple times below, the first listing should be
preferred over any subsequent listing(s).
[0127] 1x RTT CDMA2000 1x Radio Transmission Technology
[0128] 3GPP 3rd Generation Partnership Project
[0129] 5G 5th Generation
[0130] ABS Almost Blank Subframe
[0131] ARQ Automatic Repeat Request
[0132] AWGN Additive White Gaussian Noise
[0133] BCCH Broadcast Control Channel
[0134] BCH Broadcast Channel
[0135] CA Carrier Aggregation
[0136] CC Carrier Component
[0137] CCCH SDU Common Control Channel SDU
[0138] CDMA Code Division Multiplexing Access
[0139] CGI Cell Global Identifier
[0140] CIR Channel Impulse Response
[0141] CN Core Network
[0142] CP Cyclic Prefix
[0143] CPICH Common Pilot Channel
[0144] CPICH Ec/No CPICH Received energy per chip divided by the
power density in the band
[0145] CQI Channel Quality information
[0146] CRC Cyclic Redundancy Check
[0147] C-RNTI Cell RNTI
[0148] CSI Channel State Information
[0149] DCCH Dedicated Control Channel
[0150] DCI Downlink Control Information
[0151] DL Downlink
[0152] DM Demodulation
[0153] DMRS Demodulation Reference Signal
[0154] DRX Discontinuous Reception
[0155] DTX Discontinuous Transmission
[0156] DTCH Dedicated Traffic Channel
[0157] DUT Device Under Test
[0158] E-CID Enhanced Cell-ID (positioning method)
[0159] E-SMLC Evolved-Serving Mobile Location Centre
[0160] ECGI Evolved CGI
[0161] eNB E-UTRAN NodeB
[0162] ePDCCH enhanced Physical Downlink Control Channel
[0163] E-SMLC evolved Serving Mobile Location Center
[0164] ETWS Earthquake and Tsunami Warning System
[0165] E-UTRA Evolved UTRA
[0166] E-UTRAN Evolved UTRAN
[0167] FDD Frequency Division Duplex
[0168] GERAN GSM EDGE Radio Access Network
[0169] gNB Base station in NR
[0170] GNSS Global Navigation Satellite System
[0171] GSM Global System for Mobile communication
[0172] HARQ Hybrid Automatic Repeat Request
[0173] HF High Frequency/High Frequencies
[0174] HO Handover
[0175] HSPA High Speed Packet Access
[0176] HRPD High Rate Packet Data
[0177] IMSI International Mobile Subscriber Identity
[0178] LOS Line of Sight
[0179] LPP LTE Positioning Protocol
[0180] LTE Long-Term Evolution
[0181] MAC Medium Access Control
[0182] MBMS Multimedia Broadcast Multicast Services
[0183] MBSFN Multimedia Broadcast multicast service Single
Frequency Network
[0184] MBSFN ABS MBSFN Almost Blank Subframe
[0185] MDT Minimization of Drive Tests
[0186] MIB Master Information Block
[0187] MME Mobility Management Entity
[0188] MSC Mobile Switching Center
[0189] NPDCCH Narrowband Physical Downlink Control Channel
[0190] NR New Radio
[0191] OCNG OFDMA Channel Noise Generator
[0192] OFDM Orthogonal Frequency Division Multiplexing
[0193] OFDMA Orthogonal Frequency Division Multiple Access
[0194] OSS Operations Support System
[0195] OTDOA Observed Time Difference of Arrival
[0196] O&M Operation and Maintenance
[0197] PBCH Physical Broadcast Channel
[0198] P-CCPCH Primary Common Control Physical Channel
[0199] PCell Primary Cell
[0200] PCFICH Physical Control Format Indicator Channel
[0201] PDCCH Physical Downlink Control Channel
[0202] PDP Profile Delay Profile
[0203] PDSCH Physical Downlink Shared Channel
[0204] PGW Packet Gateway
[0205] PHICH Physical Hybrid-ARQ Indicator Channel
[0206] PLMN Public Land Mobile Network
[0207] PMI Precoder Matrix Indicator
[0208] PI Paging Indicator
[0209] PO Paging Occasion
[0210] PRACH Physical Random Access Channel
[0211] P-RNTI Paging RNTI
[0212] PRS Positioning Reference Signal
[0213] PSS Primary Synchronization Signal
[0214] PUCCH Physical Uplink Control Channel
[0215] PUSCH Physical Uplink Shared Channel
[0216] RACH Random Access Channel
[0217] QAM Quadrature Amplitude Modulation
[0218] RAN Radio Access Network
[0219] RAR Random Access Response
[0220] RA-RNTI Random Access RNTI
[0221] RNA RAN Notification Area
[0222] RNTI Radio Network Temporary Identifier
[0223] RAT Radio Access Technology
[0224] RLM Radio Link Management
[0225] RNC Radio Network Controller
[0226] RNTI Radio Network Temporary Identifier
[0227] RRC Radio Resource Control
[0228] RRM Radio Resource Management
[0229] RS Reference Signal
[0230] RSCP Received Signal Code Power
[0231] RSRP Reference Symbol Received Power OR Reference Signal
Received Power
[0232] RSRQ Reference Signal Received Quality OR Reference Symbol
Received Quality
[0233] RSSI Received Signal Strength Indicator
[0234] RSTD Reference Signal Time Difference
[0235] SAE System Architecture Evolution
[0236] SCH Synchronization Channel
[0237] SCell Secondary Cell
[0238] SDU Service Data Unit
[0239] SFN System Frame Number or Single Frequency Network
[0240] SGW Serving Gateway
[0241] SI System Information
[0242] SIB System Information Block
[0243] SNR Signal to Noise Ratio
[0244] SON Self Optimized Network
[0245] SSSynchronization Signal
[0246] SSS Secondary Synchronization Signal
[0247] S-TMSI SAE-TMSI
[0248] TDD Time Division Duplex
[0249] TDOA Time Difference of Arrival
[0250] TMSI Temporary Mobile Subscriber Identity
[0251] TRP Transmission/Reception Point
[0252] TOA Time of Arrival
[0253] TSS Tertiary Synchronization Signal
[0254] TTI Transmission Time Interval
[0255] UE User Equipment
[0256] UL Uplink
[0257] UMTS Universal Mobile Telecommunication System
[0258] USIM Universal Subscriber Identity Module
[0259] UTDOA Uplink Time Difference of Arrival
[0260] UTRA Universal Terrestrial Radio Access
[0261] UTRAN Universal Terrestrial Radio Access Network
[0262] WCDMA Wide CDMA
[0263] WLAN Wide Local Area Network
* * * * *