ACTIVATION OF TWO OR MORE TCI STATES FOR ONE OR MORE CORESETs

Abstract

Systems and methods are disclosed herein for activation of two or more Transmission Configuration Indication (TCL) states for a Physical Downlink Control Channel (PDCCH) in one or more Control Resource Sets (CORESETs) in a cellular communications system. In one embodiment, a method performed by a wireless communication device for activation of multiple TCI states for a PDCCH in one or more CORESETs in a cellular communications system comprises receiving, from a network node, signaling that activates NTCI TCI states for one or more CORESETs, wherein NTCI>1. In this manner, activation of two or more TCI states for PDCCH in one or more CORESETs is enabled.

Claims

1-62. (canceled)

63. A method performed by a wireless communication device for activation of multiple Transmission Configuration Indication, TCI, states for a Physical Downlink Control Channel, PDCCH, in one or more Control Resource Sets, CORESETs, in a cellular communications system, the method comprising: receiving, from a network node, a medium access control, MAC, control element, CE, signaling that activates two TCI states for one CORESET wherein the MAC CE signaling comprises: a first octet that comprises a serving cell identity, ID, of a serving cell of the wireless communication device and a first part of a CORESET ID of the one CORESET; a second octet that comprises a second part of the CORESET ID of the one CORESET and a first TCI state ID of a first TCI state of the two TC states that are activated for the one CORESET; and a third octet that comprises a second TCI state ID of a second TCI state of the two TCI states that are activated for the one CORESET.

64. The method of claim 63, wherein the received PDCCHs comprise two copies of a same DCI received from two or more respective transmission points, and the two or more respective transmission points correspond to two or more respective TCI states from among the two TCI states that are activated for one or more CORESETs.

65. The method of claim 64, wherein the two copies of the same DCI are received from the two or more respective transmission points in a same CORESET.

66. The method of claim 63, wherein the one or more CORESETs consist of a single CORESET, and the two TCI states are activated for the single CORESET.

67. The method of claim 63, wherein receiving the MAC CE signaling that activates two TCI states for one CORESET comprises: receiving a configuration of M TCI state lists for the one CORESET, wherein each TC state list of the M TCI state lists comprises up to a predefined or preconfigured maximum number of TCI states and M>1; and receiving, from the network node, an indication of one of the M TCI state lists for the one CORESET, wherein TCI states in the one of the M TCI state lists are the two TCI states that are activated for the one CORESET.

68. The method of claim 67, wherein receiving the indication of the one of the NM TCI state lists for the CORESET comprises receiving a Medium Access Control, MAC, Control Element, CE, that comprises the indication of the one of the M TCI state lists for the CORESET.

69. The method of claim 67, wherein the wireless communication device interprets the TCI state ID as the indication of the one of the M TCI state lists for the CORESET.

70. The method of claim 67, wherein receiving the MAC CE signaling that activates two TCI states for one CORESET comprises: receiving, from the network node, a Medium Access Control, MAC, Control Element, CE, that comprises, for each CORESET of the one CORESET, information that indicates the two TCI states that are activated for the one CORESET.

71. The method of claim 63, wherein the first TCI state indicated by the first TCI state ID in the second octet of the MAC CE is a default TCI state for physical downlink shared channel, PDSCH.

72. The method of claim 63, wherein the MAC CE is a fixed size MAC CE.

73. The method of claim 63, wherein the third octet comprised in the MAC CE further comprises: a second part of the TCI state ID of the first TCI state of the two TCI states that are activated for the single CORESET.

74. The method of claim 63, wherein the one or more CORESETs comprise two or more CORESETs, and the MAC CE comprises, for each CORESET of the two or more CORESETs, for each TC state of the two TCL states that are activated for the CORESET, an indication of the TCI state.

75. A method performed by a network node for activation of multiple Transmission Configuration Indication, TCI, states for a Physical Downlink Control Channel, PDCCH, in one or more Control Resource Sets, CORESETs, in a cellular communications system, the method comprising: sending, to a wireless communication device, a medium access control, MAC, control element, CE, signaling that activates two TCI states for one CORESET, wherein the MAC CE signaling comprises: a first octet that comprises a serving cell identity, ID, of a serving cell of the wireless communication device and a first part of a CORESET ID of the one CORESET; a second octet that comprises a second part of the CORESET ID of the one CORESET and a first TCI state ID of a first TCI state of the two TCI states that are activated for the one CORESET; and a third octet that comprises a second TCI state ID of a second TCI state of the two TCI states that are activated for the one CORESET.

76. The method of claim 75, wherein the two TCI states are activated for the one CORESET.

77. The method of claim 75, wherein the MAC CE signaling comprises, for the one CORESET, information that indicates two TCI states activated for the one CORESET.

78. The method of claim 77, wherein the two TCI states are different for at least two of the two or more CORESETs.

79. The method of claim 77, wherein the two TCI states are the same for at least two of the two or more CORESETs.

80. The method of claim 75, wherein sending the MAC CE signaling that activates two TCI states for one CORESET comprises: sending, to the wireless communication device, a configuration of M TCI state lists for the one CORESET, wherein each TCI state list of the M TCI state lists comprises up to a predefined or preconfigured maximum number of TCI states and M>1; and sending, to the wireless communication device, an indication of one of the M TCI state lists for the one CORESET, wherein TCI states in the one of the M TCI state lists are the two TCI states that are activated for the one CORESET.

81. The method of claim 75, wherein the MAC CE is a fixed size MAC CE.

82. The method of claim 75, wherein the third octet of the MAC CE comprises a second part of the TCI state ID of the first TCI state of the two TCI states that are activated for the single CORESET.

83. The method of claim 63, further comprising determining one of the first and the second TCI states as a default TCI state for physical downlink shared channel, PDSCH, scheduled by a physical control channel, PDCCH, received in the one CORESET.

Description

BRIEF DESCRIPTION OF THE DRAWINGS

[0060] The accompanying drawing figures incorporated in and forming a part of this specification illustrate several aspects of the disclosure, and together with the description serve to explain the principles of the disclosure.

[0061] FIG. 1 illustrates a typical slot in Third Generation Partnership Project (3GPP) New Radio (NR);

[0062] FIG. 2 illustrates the basic NR time-frequency resource grid;

[0063] FIG. 3 is a reproduction of FIG. 6.1.3.15-1 of 3GPP Technical Specification (TS) 38.321;

[0064] FIG. 4 illustrates a Physical Downlink Control Channel (PDCCH) enhancement proposed in NR Release 17 with multiple Transmission/Reception Points (TRPs) where a PDCCH is repeated from different TRPs;

[0065] FIG. 5 illustrates one example of a cellular communications system in which embodiments of the present disclosure may be implemented;

[0066] FIG. 6 illustrates the operation of a base station and a User Equipment (UE) for activation of N.sub.TCI>1 TCI states for a Control Resource Set(s) (CORESET(s)) in accordance with embodiments of the present disclosure;

[0067] FIG. 7 illustrates step 600 of FIG. 6 in more detail for a first embodiment of the present disclosure;

[0068] FIGS. 8 through 12 illustrate examples of a Medium Access Control (MAC) Control Element (CE) for activation of multiple TCI states for one or more CORESETs in accordance with a second embodiment of the present disclosure;

[0069] FIG. 13 illustrates step 600 of FIG. 6 in more detail for the second embodiment of the present disclosure;

[0070] FIGS. 14, 15, and 16 are schematic block diagrams of example embodiments of a radio access node, or more generally a network node, in which embodiments of the present disclosure may be implemented;

[0071] FIGS. 17 and 18 are schematic block diagrams of example embodiments of a wireless communication device (e.g., a UE) in which embodiments of the present disclosure may be implemented;

[0072] FIG. 19 illustrates an example embodiment of a communication system in which embodiments of the present disclosure may be implemented;

[0073] FIG. 20 illustrates example embodiments of the host computer, base station, and UE of FIG. 19; and

[0074] FIGS. 21, 22, 23, and 24 are flow charts that illustrate example embodiments of methods implemented in a communication system such as that of FIG. 19.

DETAILED DESCRIPTION

[0075] The embodiments set forth below represent information to enable those skilled in the art to practice the embodiments and illustrate the best mode of practicing the embodiments. Upon reading the following description in light of the accompanying drawing figures, those skilled in the art will understand the concepts of the disclosure and will recognize applications of these concepts not particularly addressed herein. It should be understood that these concepts and applications fall within the scope of the disclosure.

[0076] Some of the embodiments contemplated herein will now be described more fully with reference to the accompanying drawings. Other embodiments, however, are contained within the scope of the subject matter disclosed herein, the disclosed subject matter should not be construed as limited to only the embodiments set forth herein; rather, these embodiments are provided by way of example to convey the scope of the subject matter to those skilled in the art.

[0077] 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.

[0078] Radio Node: As used herein, a “radio node” is either a radio access node or a wireless communication device.

[0079] Radio Access Node: As used herein, a “radio access node” or “radio network node” or “radio access network node” is any node in a Radio Access Network (RAN) of a cellular communications network that operates to wirelessly transmit and/or receive signals. Some examples of a radio access node include, but are not limited to, a base station (e.g., a New Radio (NR) base station (gNB) in a Third Generation Partnership Project (3GPP) Fifth Generation (5G) NR network or an enhanced or evolved Node B (eNB) in a 3GPP Long Term Evolution (LTE) network), a high-power or macro base station, a low-power base station (e.g., a micro base station, a pico base station, a home eNB, or the like), a relay node, a network node that implements part of the functionality of a base station (e.g., a network node that implements a gNB Central Unit (gNB-CU) or a network node that implements a gNB Distributed Unit (gNB-DU)) or a network node that implements part of the functionality of some other type of radio access node.

[0080] Core Network Node: As used herein, a “core network node” is any type of node in a core network or any node that implements a core network function. Some examples of a core network node include, e.g., a Mobility Management Entity (MME), a Packet Data Network Gateway (P-GW), a Service Capability Exposure Function (SCEF), a Home Subscriber Server (HSS), or the like. Some other examples of a core network node include a node implementing an Access and Mobility Management Function (AMF), a User Plane Function (UPF), a Session Management Function (SMF), an Authentication Server Function (AUSF), a Network Slice Selection Function (NSSF), a Network Exposure Function (NEF), a Network Function (NF) Repository Function (NRF), a Policy Control Function (PCF), a Unified Data Management (UDM), or the like.

[0081] Communication Device: As used herein, a “communication device” is any type of device that has access to an access network. Some examples of a communication device include, but are not limited to: mobile phone, smart phone, sensor device, meter, vehicle, household appliance, medical appliance, media player, camera, or any type of consumer electronic, for instance, but not limited to, a television, radio, lighting arrangement, tablet computer, laptop, or Personal Computer (PC). The communication device may be a portable, hand-held, computer-comprised, or vehicle-mounted mobile device, enabled to communicate voice and/or data via a wireless or wireline connection.

[0082] Wireless Communication Device: One type of communication device is a wireless communication device, which may be any type of wireless device that has access to (i.e., is served by) a wireless network (e.g., a cellular network). Some examples of a wireless communication device include, but are not limited to: a User Equipment device (UE) in a 3GPP network, a Machine Type Communication (MTC) device, and an Internet of Things (IoT) device. Such wireless communication devices may be, or may be integrated into, a mobile phone, smart phone, sensor device, meter, vehicle, household appliance, medical appliance, media player, camera, or any type of consumer electronic, for instance, but not limited to, a television, radio, lighting arrangement, tablet computer, laptop, or PC. The wireless communication device may be a portable, hand-held, computer-comprised, or vehicle-mounted mobile device, enabled to communicate voice and/or data via a wireless connection.

[0083] Network Node: As used herein, a “network node” is any node that is either part of the RAN or the core network of a cellular communications network/system.

[0084] Transmission/Reception Point (TRP): In some embodiments, a TRP may be either a network node, a radio head, a spatial relation, or a Transmission Configuration Indicator (TCI) state. A TRP may be represented by a spatial relation or a TCI state in some embodiments. In some embodiments, a TRP may be using multiple TCI states. In some embodiments, a TRP may be a part of the gNB transmitting and receiving radio signals to/from UE according to physical layer properties and parameters inherent to that element. In some embodiments, in Multiple TRP (multi-TRP) operation, a serving cell can schedule UE from two TRPs, providing better coverage, reliability and/or data rates for PDSCH and/or PDCCH. There are two different operation modes for scheduling PDSCH over multi-TRP: single Downlink Control Information (DCI) and multi-DCI. For both modes, control of uplink and downlink operation is done by both physical layer and Medium Access Control (MAC). In single-DCI mode, UE is scheduled by the same DCI for both TRPs and in multi-DCI mode, UE is scheduled by independent DCIs from each TRP.

[0085] In some embodiments, a set Transmission Points (TPs) is a set of geographically co-located transmit antennas (e.g., an antenna array (with one or more antenna elements)) for one cell, part of one cell or one Positioning Reference Signal (PRS)-only TP. TPs can include base station (eNB) antennas, Remote Radio Heads (RRHs), a remote antenna of a base station, an antenna of a PRS-only TP, etc. One cell can be formed by one or multiple TPs. For a homogeneous deployment, each TP may correspond to one cell.

[0086] In some embodiments, a set of TRPs is a set of geographically co-located antennas (e.g., an antenna array (with one or more antenna elements)) supporting TP and/or Reception Point (RP) functionality.

[0087] Note that the description given herein focuses on a 3GPP cellular communications system and, as such, 3GPP terminology or terminology similar to 3GPP terminology is oftentimes used. However, the concepts disclosed herein are not limited to a 3GPP system.

[0088] Note that, in the description herein, reference may be made to the term “cell”; however, particularly with respect to 5G NR concepts, beams may be used instead of cells and, as such, it is important to note that the concepts described herein are equally applicable to both cells and beams.

[0089] There currently exist certain challenge(s). There is no mechanism in NR to activate multiple Transmission Configuration Indicator (TCI) states for Physical Downlink Control Channel (PDCCH) in a Control Resource Set (CORESET). Currently, for each CORESET in NR, only one TCI state can be activated. The activation is typically done with a Medium Access Control (MAC) Control Element (CE). Thus, there is a need for systems and methods for activating multiple TCI states for a CORESET and the associated signaling details.

[0090] Certain aspects of the present disclosure and their embodiments may provide solutions to the aforementioned or other challenges. In this disclosure, different ways of signaling the activation of N.sub.TCI>1 TCI states for a CORESET(s) are disclosed. In one embodiment, the activation of N.sub.TCI>1 TCI states for a CORESET(s) is signaled in a way that reuses the existing MAC CE. Embodiments are also disclosed herein for signaling the activation of N.sub.TCI>1 TCI states for a CORESET(s) in a new way, e.g., using a new MAC CE.

[0091] Certain embodiments may provide one or more of the following technical advantage(s). Advantages of the solution depend on the particular embodiment. One advantage of the first embodiment, which proposes a way to reuse the existing MAC CE, is that no new MAC CE needs to be specified. In NR, many new MAC CEs have been defined to the extent that the Logical Channel Identity (LCID) space is running out. Even with a solution to the issue of the limited LCID space, adding more MAC CEs especially for similar functionality complicates the NR specification and interoperability between releases. In this embodiment, a number of lists may be needed. For example, assuming that a total of 64 TCI states are possible and that 2 TCI states are selected per the new list being introduced, then there are 2016 different ways of choosing 2 TCI states out of 64 possible TCI states. But since the TCI state identity (ID) field in the MAC CE only has 7 bits, there is a maximum of 128 lists.

[0092] One advantage of the second embodiment is that it enables more flexible activated TCI state selection than the first embodiment. In the first embodiment, the pair of TCI states is preconfigured (e.g., by Radio Resource Control (RRC) signaling), and enabling the same flexibility as in the second embodiment may not be possible due to the amount of permutations. Another advantage of the second embodiment as it relates to TCI state activation for two or more CORESETs using a single MAC CE is that it saves overhead compared to existing MAC CE signaling for CORESET TCI state activation. In the existing MAC CE for TCI state activation for a CORESET, one MAC CE needs to be sent for each CORESET. The solution proposed in the second embodiment enables a flexible number of TCI states (i.e., two or more TCI states) to be activated for multiple CORESETs, which saves signaling overhead.

[0093] FIG. 5 illustrates one example of a cellular communications system 500 in which embodiments of the present disclosure may be implemented. In the embodiments described herein, the cellular communications system 500 is a 5G system (5GS) including a Next Generation RAN (NG-RAN) and a 5G Core (5GC). In this example, the RAN includes radio access nodes 502-1 and 502-2, which in the 5GS include NR base stations (gNBs) and optionally next generation eNBs (ng-eNBs) (e.g., LTE RAN nodes connected to the 5GC), controlling corresponding (macro) cells 504-1 and 504-2. The base stations 502-1 and 502-2 are generally referred to herein collectively as base stations 502 and individually as base station 502. Likewise, the (macro) cells 504-1 and 504-2 are generally referred to herein collectively as (macro) cells 504 and individually as (macro) cell 504. Each base station 502 includes one or more Transmission Points (TRPs) (not shown). Also, in case of multi-TRP transmission, one of the TRPs may be another base station, e.g., data are transmitted from two base stations to a wireless communication device 512 (under control of one of the base stations through base station coordination).

[0094] The RAN may also include a number of low power nodes 506-1 through 506-4 controlling corresponding small cells 508-1 through 508-4. The low power nodes 506-1 through 506-4 can be small base stations (such as pico or femto base stations) or Remote Radio Heads (RRHs), or the like. Notably, while not illustrated, one or more of the small cells 508-1 through 508-4 may alternatively be provided by the base stations 502. The low power nodes 506-1 through 506-4 are generally referred to herein collectively as low power nodes 506 and individually as low power node 506. Likewise, the small cells 508-1 through 508-4 are generally referred to herein collectively as small cells 508 and individually as small cell 508. Each of the low power nodes 506 is or includes one (or more) TRP. Also, in case of multi-TRP transmission, one of the TRPs may be another low power node 506 (or a base station 502).

[0095] The cellular communications system 500 also includes a core network 510, which in the 5GS is the 5GC. The base stations 502 (and optionally the low power nodes 506) are connected to the core network 510.

[0096] The base stations 502 and the low power nodes 506 provide service to wireless communication devices 512-1 through 512-5 in the corresponding cells 504 and 508. The wireless communication devices 512-1 through 512-5 are generally referred to herein collectively as wireless communication devices 512 and individually as wireless communication device 512. In the following description, the wireless communication devices 512 are oftentimes UEs and as such sometimes referred to herein as UEs 512, but the present disclosure is not limited thereto.

[0097] FIG. 6 illustrates the operation of a base station 502 and a UE 512 for activation of N.sub.TCI>1 TCI states for a CORESET(s) in accordance with embodiments of the present disclosure. Optional steps are represented by dashed lines/boxes. As illustrated, the base station 502 signals activation of N.sub.TCI>1 TCI states for a CORESET(s) to the UE 512 (step 600). As discussed below, in some embodiments, the base station 502 signals activation of N.sub.TCI>1 TCI states for a single CORESET. In some other embodiments, the base station 502 signals activation of N.sub.TCI>1 TCI states for each of two (or more) CORESETs, where N.sub.TCI may be the same for all of these CORESETs or may be different for at least two of these CORESETs. As described below, some embodiments, the signaling of the activation of the N.sub.TCI>1 TCI states for the CORESET(s) uses an existing MAC CE (e.g., an existing PDCCH MAC CE). However, in some other embodiments, the signaling of the activation of the N.sub.TCI>1 TCI states for the CORESET(s) uses a new signaling structure such as, e.g., a new MAC CE (e.g., a new PDCCH MAC CE).

[0098] The UE 512 then receives PDCCHs (e.g., from two or more TRPs) in the CORESET(s) in accordance with the activated TCI states (step 602). For example, a particular PDCCH may be repeated from two or more TRPs (e.g., as shown in FIG. 4 described above). In one particular example, PDCCH in a CORESET is associated with multiple activated TCI states, and Resource Elements (REs) of a PDCCH candidate are divided into multiple subsets each associated with one of the activated TCI states. A PDCCH in each subset is then transmitted from a different TRP and received by the UE 512 in accordance with the respective (activated) TCI states.

[0099] The UE may then perform one or more actions based on the received PDCCHs (step 604). For example, if the received PDCCHs are repetitions of a same PDCCH, then that same PDCCH is decoded to obtain the respective DCI, and the UE 512 then operates in accordance with the DCI (e.g., receives a downlink transmission in accordance with a downlink assignment in the DCI or transmits an uplink transmission in accordance with an uplink grant in the DCI).

[0100] Now, details of embodiments of the signaling of the activation of the N.sub.TCI>1 TCI states for the CORESET(s), e.g., in step 600 of FIG. 6 are provided.

First Embodiment—Reuse of Existing MAC CE

[0101] In this embodiment, for each CORESET (i.e., ControlResourceSet), the UE 512 is configured (e.g., via RRC signaling) with multiple TCI state lists, each having up to a maximum number (e.g., predefined or preconfigured maximum number) of TCI states in each list. In some embodiments, the maximum number of TCI states in each list is given by a parameter (e.g., an RRC parameter referred to herein as maxNrofTCI-StatesPerPDCCH, which is set to an integer value (e.g., two). The TCI states in each of the multiple TCI state lists are the activated TCI states for the CORESET if the list is selected. The existing MAC CE (see FIG. 3) is reused to activate one of the lists by interpreting the “TCI state ID” field as an ID (e.g., tciListID in the example below) of the list of TCI states to be activated.

[0102] FIG. 7 illustrates step 600 of FIG. 6 in more detail for the first embodiment. As illustrated, in regarding to the signaling of step 600, the base station 502 configures (e.g., via RRC signaling) the UE 512 with two or more TCI state lists, each having up to the maximum number of TCI states (step 700). The base station 502 transmits a MAC CE (e.g., a PDCCH MAC CE) to the UE 512, where the MAC CE includes an ID of one of the two or more TCI state lists to be activated (step 702). In the first embodiment, the MAC CE uses the existing MAC CE format (see FIG. 3), where the “TCI state ID” field is interpreted as the ID (e.g., tciListID in the example below) of the list of TCI states to be activated.

[0103] In one example implementation, the first embodiment may be implemented by the following additions to 3GPP TS 38.311 and 3GPP TS 38 321. The parts emphasized with bolded and underlined text are new additions.

*****Start Changes to 3GPP TS 38.311 and TS 38.321*****

[0104]

TABLE-US-00001 Control ResourceSet ::= SEQUENCE {   controlResourceSetId    ControlResourceSetId,   frequencyDomainResources   BIT STRING (SIZE (45)),   duration           INTEGER (1..maxCoReSetDuration),   cce-REG-MappingType     CHOICE {     interleaved          SEQUENCE {       reg-BundleSize        ENUMERATED {n2, n3, n6},       interleaverSize        ENUMERATED {n2, n3, n6},       shiftIndex          INTEGER(0..maxNrofPhysicalResourceBlocks-1) OPTIONAL -- Need S     },     nonInterleaved        NULL   },   precoderGranularity       ENUMERATED {sameAsREG-bundle, allContiguousRBs},   tci-StatesPDCCH-ToAddList   SEQUENCE(SIZE (1..maxNrofTCI-StatesPDCCH)) OF TCI-StateId OPTIONAL, -- Cond NotSIBl-initialBWP   tci-StatesPDCCH-ToReleaseList  SEQUENCE(SIZE (1..maxNrofTCI-StatesPDCCH)) OF TCI-StateId OPTIONAL, -- Cond NotSIBl-initialBWP   tci-PresentlnDCI       ENUMERATED {enabled}  OPTIONAL, -- Need S   pdcch-DMRS-ScramblingID   INTEGER (0..65535)   OPTIONAL, -- Need S   ...,   [[   rb-Offset-r16         INTEGER (0..5)   OPTIONAL, -- Need N   tci-PresentInDCI-ForDCI-Formatl-2-r16  INTEGER (1..3)   OPTIONAL, -- Need S   coresetPoolIndex-r16      INTEGER (0..1)   OPTIONAL, -- Need R   controlResourceSetId-r16     ControlResourceSetId-r16  OPTIONAL -- Need S   ]],   [[   tci-StatesListPDCCH      SEQUENCE(SIZE (1..maxNrofTCI-StatesListsPDCCH)) OF TCIList OPTIONAL -- Cond NotSIBl-initialBWP   ]] } TCIList ::= SEQUENCE{   tciListID   INTEGER (1..maxNrofTCILists),   tciList    SEQUENCE (SIZE (1.. maxNrofTCI-StatesPerPDCCH)) OF   TCI-StateId } maxNrofTCI-StatesListsPDCCH INTEGER ::= 128 maxNrofTCI-StatesPerListPDCCH INTEGER ::= 2

TABLE-US-00002 ControlResourceSet field descriptions cce-REG-MappingType Mapping of Control Channel Elements (CCE) to Resource Element Groups (REG) (see TS 38.211 [16], clauses 7.3.2.2 and 7.4.1.3.2). controlResourceSetId Identifies the instance of the ControlResourceSet IE. Value 0 identifies the common CORESET configured in MIB and in ServingCellConfigCommon (controlResourceSetZero) and is hence not used here in the ControlResourceSet IE. Other values identify CORESETs configured by dedicated signalling or in SIB1. The controlResourceSetId is unique among the BWPs of a serving cell. If the field controlResourceSetId-r16 is present, the UE shall ignore the controlResourceSetId field (without suffix). coresetPoolIndex The index of the CORESET pool for this CORESET as specified in TS 38.213 [13] (clauses 9 and 10) and TS 38.214 [19] (clauses 5.1 and 6.1). If the field is absent, the UE applies the value 0. duration Contiguous time duration of the CORESET in number of symbols (see TS 38.211 [16], clause 7.3.2.2). frequencyDomainResources Frequency domain resources for the CORESET. Each bit corresponds a group of 6 RBs, with grouping starting from the first RB group (see TS 38.213 [13], clause 10.1) in the BWP. The first (left-most/most significant) bit corresponds to the first RB group in the BWP, and so on. A bit that is set to 1 indicates that this RB group belongs to the frequency domain resource of this CORESET. Bits corresponding to a group of RBs not fully contained in the bandwidth part within which the CORESET is configured are set to zero (see TS 38.211 [16], clause 7.3.2.2). interleaverSize Interleaver-size (see TS 38.211 [16], clause 7.3.2.2). pdcch-DMRS-ScramblingID PDCCH DMRS scrambling initialization (see TS 38.211 [16], clause 7.4.1.3.1). When the field is absent the UE applies the value of the physCellId configured for this serving cell. precoderGranularity Precoder granularity in frequency domain (see TS 38.211 [16], clauses 7.3.2.2 and 7.4.1.3.2). rb-Offset Indicates the RB level offset in units of RB from the first RB of the first 6RB group to the first RB of BWP (see 38.213 [13], clause 10.1). When the field is absent, the UE applies the value 0. reg-BundleSize Resource Element Groups (REGs) can be bundled to create REG bundles. This parameter defines the size of such bundles (see TS 38.211 [16], clause 7.3.2.2). shiftIndex When the field is absent the UE applies the value of the physCellIdconfigured for this serving cell (see TS 38.211 [16], clause 7.3.2.2). tci-PresentInDCI This field indicates if TCI field is present or absent in DCI format 1_1. When the field is absent the UE considers the TCI to be absent/disabled. In case of cross carrier scheduling, the network sets this field to enabled for the ControlResourceSet used for cross carrier scheduling in the scheduling cell (see TS 38.214 [19], clause 5.1.5). tci-PresentInDCI-ForDCI-Format1-2 Configures the number of bits for “Transmission configuration indicator” in DCI format 1_2. When the field is absent the UE applies the value of 0 bit for the “Transmission configuration indicator” in DCI format 1_2 (see TS 38.212, clause 7.3.1 and TS 38.214, clause 5.1.5). tci-StatesPDCCH-ToAddList A subset of the TCI states defined in pdsch-Config included in the BWP-DownlinkDedicated corresponding to the serving cell and to the DL BWP to which the ControlResourceSet belong to. They are used for providing QCL relationships between the DL RS(s) in one RS Set (TCI-State) and the PDCCH DMRS ports (see TS 38.213 [13], clause 6.). The network configures at most maxNrofTCI-StatesPDCCH entries. tci-StatesListPDCCH A list of TCI states that are a subset of the TCI states defined in pdsch-Config included in the BWP-DownlinkDedicated corresponding to the serving cell and to the DL BWP to which the ControlResourceSet belong to. They are used for providing OCL relationships between the DL RS(s) in one RS Set (TCI-State) and the PDCCH DMRS ports (see TS 38.213 [13]. clause 6.) The network configures at most maxNrofTCI-StatesPDCCH entries. UE ignores tci-StatesPDCCH-ToAddList if tci-StatesListPDCCH is configured
The TCI State Indication for UE-specific PDCCH MAC CE is identified by a MAC subheader with LCID as specified in Table 6.2.1-1. It has a fixed size of 16 bits with following fields: [0105] Serving Cell ID: This field indicates the identity of the Serving Cell for which the MAC CE applies. The length of the field is 5 bits. If the indicated Serving Cell is configured as part of a simultaneousTCI-UpdateList-r16 or simultaneousTCI-UpdateListSecond-r16 as specified in TS 38.331 [5], this MAC CE applies to all the Serving Cells in the set simultaneousTCI-UpdateList-r16 or simultaneousTCI-UpdateListSecond-r16, respectively; [0106] CORESET ID: This field indicates a Control Resource Set identified with ControlResourceSetId as specified in TS 38.331 [5], for which the TCI State is being indicated. In case the value of the field is 0, the field refers to the Control Resource Set configured by controlResourceSetZero as specified in TS 38.331 [5]. The length of the field is 4 bits; [0107] TCI State ID: This field indicates the TCI state identified by TCI-StateId or tciListID as specified in TS 38.331 [5] applicable to the Control Resource Set identified by CORESET ID field. If the field of CORESET ID is set to 0, this field indicates a TCI-StateId for a TCI state of the first 64 TCI-states configured by tci-States-ToAddModList and tci-States-ToReleaseList in the PDSCH-Confg in the active BWP. If the field of CORESET ID is set to the other value than 0 and UE is not configured with tci-StatesListPDCCH, this field indicates a TCI-StateIdconfigured by tci-StatesPDCCH-ToAddList and tci-StatesPDCCH-ToReleaseList in the controlResourceSet identified by the indicated CORESET ID. If the field of CORESET ID is set to the other value than 0 and UE is configured with tci-StatesListPDCCH, this field indicates a tciListID configured by tci-StatesListPDCCH in the controlResourceSet identified by the indicated CORESET ID. The length of the field is 7 bits.

Reproduced Herein as FIG. 3

FIG. 6.1.3.15-1: TCI State Indication for UE-Specific PDCCH MAC CE

*****End Changes to 3GPP TS 38.311 and TS 38.321*****

Second Embodiment—New MAC CE Options

[0108] In one embodiment, a new MAC CE is introduced to activate up to two TCI states to one CORESET ID as shown in FIG. 8. A “C” field is used to indicate which TCI state should be assumed by the UE 512 as default TCI state for PDSCH. If C=1 (or C=0), the default TCI state is the one in Octet 2; and, if C=0 (or C=1), the default TCI state is the one in Octet 3 which is the same octet where the C field is.

[0109] What is meant by default TCI state for PDSCH to be assumed by the UE 512 in this embodiment (and also in following embodiments) is the following. When the UE 512 assumes that the Demodulation Reference Signal (DMRS) ports of PDSCH of a serving cell are quasi co-located with the reference signal(s) (RS(s)) with respect to the QCL parameter(s) used for PDCCH quasi co-location indication in a CORESET, the default TCI state for PDSCH is the TCI state activated for PDCCH in the CORESET. For example, in NR Release 16 if none of the TCI codepoints in DCI for PDSCH scheduling are mapped to more than a single TCI state activated for PDSCH and the offset between the reception of a DL DCI and the corresponding PDSCH is less than a threshold timeDurationForQCL configured by higher layers, the UE may assume the default TCI state for receiving the PDSCH. The default TCI state in this case is the activated TCI state of the CORESET with the lowest CORESET-ID in the latest slot in which one or more CORESETs are monitored by the UE. In other word, the DMRS ports of the PDSCH are quasi co-located with RS(s) with respect to the QCL parameter(s) of the default TCI state in this case.

[0110] If the new MAC CE of the second embodiment is defined as fixed size MAC CE, by default the header does not include a length field. In this case, the MAC CE always activates two TCI states per CORESET. If this MAC CE is defined as flexible size MAC CE, the header will include a length field, and UE can interpret whether the MAC CE has one or two TCI states (two or three octets in the main body of the MAC CE) based on the length field.

[0111] In another embodiment, more than two TCI states can be mapped to one CORESET ID as shown in FIG. 9. In the example of FIG. 9, three TCI states are activated for one CORESET (i.e., the CORESET that corresponds to the given CORESET ID). One difference between this embodiment and that of FIG. 8 is that two or more bits are needed for the C field. The C field with 2 or more bits in this embodiment chooses which TCI states among the TCI states activated within the MAC CE should be used by the UE 512 as default TCI state for PDSCH.

[0112] In a further embodiment, the new MAC CE is as shown in FIG. 10, where up to N TCI states may be activated. If C.sub.k=1, then TCI state ID.sub.k is the default TCI state for PDSCH. Only one C.sub.k can be set to 1. If C.sub.k=0 for k=1, . . . , N−1, then TCI state ID.sub.0 is the default TCI state for PDSCH.

[0113] If this MAC CE is defined as fixed size MAC CE, by default the header does not include a length field. In this case, the MAC CE always activates two TCI states per CORESET. If this MAC CE is defined as flexible size MAC CE, the header will include a length field and UE can interpret whether the MAC CE has two TCI states or N TCI states (two or N octets in the main body of the MAC CE) based on the length field.

[0114] In some embodiments, only the first TCI state ID provided in the MAC CE is used as default TCI state for PDSCH. This means TCI state ID.sub.0 (7 bits) in FIG. 8, FIG. 9, and FIG. 10 is used as default TCI state of PDSCH. The additional TCI states activated for a CORESET in the examples of FIG. 8, FIG. 9, and FIG. 10 are only used for the purpose of subsets of REs of a PDCCH candidate. In this embodiment, the ‘C’ field(s) are no longer needed as the default TCI state for PDSCH is already predefined by the first activated TCI state with TCI state ID.sub.0. Hence, in this embodiment, the ‘C’ field(s) are replaced by reserved ‘R’ fields in FIG. 8, FIG. 9, and FIG. 10.

[0115] In some embodiments, the new MAC CE that provides more than one active TCI state per CORESET is only applicable to CORESETs other than CORESET 0 (i.e., a CORESET whose CORESET ID is set to a value other than 0).

[0116] In another embodiment, the number of CORESETs per serving cell is increased to larger than 16 (e.g., 20) which requires an additional bit to be included in the CORESET ID field. As shown in FIG. 11, CORESET ID is given by a 5-bit field where 3 bits are given in octet OCT1 and the remaining 2 bits are given in OCT2. For indicating the first activated TCI state for the CORESET, 6 out of 7 bits of TCI state ID.sub.0 are provided in octet OCT2 and the remaining 1 bit of TCI state ID.sub.0 is provided in octet OCT3. For indicating the second activated TCI state for the CORESET, the 7-bit TCI state ID.sub.1 is provided in octet OCT3.

[0117] The above embodiments can be extended to the case where TCI state activation for more than one CORESET may be included in one MAC CE where one or two TCI states can be activated for each MAC CE. In this regard, FIG. 12 shows an example where TCI state activation for two CORESETs within the same serving cell are provided in the same MAC CE. Further details of this MAC CE design are given below: [0118] The field CORESET ID.sub.r represents the CORESET ID of the r.sup.th CORESET for which TCI state(s) activation is provided in the MAC CE. [0119] The field TCI state ID.sub.r,i represents the i.sup.th activated TCI state for the CORESET associated with CORESET ID.sub.r. [0120] The field G.sub.r is an indicator that indicates if TCI state activation for an additional CORESET (i.e., CORESET corresponding to CORESET ID.sub.r+1) will be provided in the new MAC CE.

[0121] Note that, in one embodiment, in the above embodiments involving the introduction of a new MAC CE, each of the fields TCI state ID.sub.0, TCI state ID.sub.1, . . . indicate a TCI-StateIdconfigured by tci-StatesPDCCH-ToAddList and tci-StatesPDCCH-ToReleaseList in the controlResourceSet identified by the indicated CORESET ID.

[0122] FIG. 13 illustrates step 600 of FIG. 6 in more detail for the second embodiment. As illustrated, in regard to the signaling of step 600, the base station 502 may also configure (e.g., via RRC signaling) the UE 512 with a TCI state list having up to the maximum number of TCI states for each CORESET (step 1300). The base station 502 transmits a MAC CE (e.g., a PDCCH MAC CE) to the UE 512, where the MAC CE includes information that indicates the activated TCI states and, in some embodiments, the CORESET(s) for which the indicated TCI states are activated (step 1302). For example, the MAC CE may be the MAC CE of any one of FIGS. 8 to 12 described above. Note that the TCI state IDs included in the MAC CE may be indices of the TCI states in the TCI state list of the respective CORESET configured in step 1300.

Additional Details

[0123] FIG. 14 is a schematic block diagram of a radio access node 1400 according to some embodiments of the present disclosure. Optional features are represented by dashed boxes. The radio access node 1400 may be, for example, a base station 502, a low power node 506, a TRP (e.g., a TRP of a base station 502), or the like. As illustrated, the radio access node 1400 includes a control system 1402 that includes one or more processors 1404 (e.g., Central Processing Units (CPUs), Application Specific Integrated Circuits (ASICs), Field Programmable Gate Arrays (FPGAs), and/or the like), memory 1406, and a network interface 1408. The one or more processors 1404 are also referred to herein as processing circuitry. In addition, the radio access node 1400 may include one or more radio units 1410 that each includes one or more transmitters 1412 and one or more receivers 1414 coupled to one or more antennas 1416. The radio units 1410 may be referred to or be part of radio interface circuitry. In some embodiments, the radio unit(s) 1410 is external to the control system 1402 and connected to the control system 1402 via, e.g., a wired connection (e.g., an optical cable). However, in some other embodiments, the radio unit(s) 1410 and potentially the antenna(s) 1416 are integrated together with the control system 1402. The one or more processors 1404 operate to provide one or more functions of the radio access node 1400 as described herein (e.g., one or more functions of a base station 502, gNB, or TRP as described herein). In some embodiments, the function(s) are implemented in software that is stored, e.g., in the memory 1406 and executed by the one or more processors 1404.

[0124] FIG. 15 is a schematic block diagram that illustrates a virtualized embodiment of the radio access node 1400 according to some embodiments of the present disclosure. This discussion is equally applicable to other types of network nodes. Further, other types of network nodes may have similar virtualized architectures. Again, optional features are represented by dashed boxes.

[0125] As used herein, a “virtualized” radio access node is an implementation of the radio access node 1400 in which at least a portion of the functionality of the radio access node 1400 is implemented as a virtual component(s) (e.g., via a virtual machine(s) executing on a physical processing node(s) in a network(s)). As illustrated, in this example, the radio access node 1400 may include the control system 1402 and/or the one or more radio units 1410, as described above. The control system 1402 may be connected to the radio unit(s) 1410 via, for example, an optical cable or the like. The radio access node 1400 includes one or more processing nodes 1500 coupled to or included as part of a network(s) 1502. If present, the control system 1402 or the radio unit(s) are connected to the processing node(s) 1500 via the network 1502. Each processing node 1500 includes one or more processors 1504 (e.g., CPUs, ASICs, FPGAs, and/or the like), memory 1506, and a network interface 1508.

[0126] In this example, functions 1510 of the radio access node 1400 described herein (e.g., one or more functions of a base station 502, gNB, or TRP as described herein) are implemented at the one or more processing nodes 1500 or distributed across the one or more processing nodes 1500 and the control system 1402 and/or the radio unit(s) 1410 in any desired manner. In some particular embodiments, some or all of the functions 1510 of the radio access node 1400 described herein are implemented as virtual components executed by one or more virtual machines implemented in a virtual environment(s) hosted by the processing node(s) 1500. As will be appreciated by one of ordinary skill in the art, additional signaling or communication between the processing node(s) 1500 and the control system 1402 is used in order to carry out at least some of the desired functions 1510. Notably, in some embodiments, the control system 1402 may not be included, in which case the radio unit(s) 1410 communicate directly with the processing node(s) 1500 via an appropriate network interface(s).

[0127] In some embodiments, a computer program including instructions which, when executed by at least one processor, causes the at least one processor to carry out the functionality of the radio access node 1400 or a node (e.g., a processing node 1500) implementing one or more of the functions 1510 of the radio access node 1400 in a virtual environment according to any of the embodiments described herein is provided. In some embodiments, a carrier comprising the aforementioned computer program product is provided. The carrier is one of an electronic signal, an optical signal, a radio signal, or a computer readable storage medium (e.g., a non-transitory computer readable medium such as memory).

[0128] FIG. 16 is a schematic block diagram of the radio access node 1400 according to some other embodiments of the present disclosure. The radio access node 1400 includes one or more modules 1600, each of which is implemented in software. The module(s) 1600 provide the functionality of the radio access node 1400 described herein (e.g., one or more functions of a base station 502, gNB, or TRP as described herein). This discussion is equally applicable to the processing node 1500 of FIG. 15 where the modules 1600 may be implemented at one of the processing nodes 1500 or distributed across multiple processing nodes 1500 and/or distributed across the processing node(s) 1500 and the control system 1402.

[0129] FIG. 17 is a schematic block diagram of a wireless communication device 1700 according to some embodiments of the present disclosure. The wireless communication device 1700 may be, for example, the wireless communication device or UE 512 as described herein. As illustrated, the wireless communication device 1700 includes one or more processors 1702 (e.g., CPUs, ASICs, FPGAs, and/or the like), memory 1704, and one or more transceivers 1706 each including one or more transmitters 1708 and one or more receivers 1710 coupled to one or more antennas 1712. The transceiver(s) 1706 includes radio-front end circuitry connected to the antenna(s) 1712 that is configured to condition signals communicated between the antenna(s) 1712 and the processor(s) 1702, as will be appreciated by on of ordinary skill in the art. The processors 1702 are also referred to herein as processing circuitry. The transceivers 1706 are also referred to herein as radio circuitry. In some embodiments, the functionality of the wireless communication device 1700 described above (e.g., one or more functions of the wireless communication device 512 or UE 512 described above) may be fully or partially implemented in software that is, e.g., stored in the memory 1704 and executed by the processor(s) 1702. Note that the wireless communication device 1700 may include additional components not illustrated in FIG. 17 such as, e.g., one or more user interface components (e.g., an input/output interface including a display, buttons, a touch screen, a microphone, a speaker(s), and/or the like and/or any other components for allowing input of information into the wireless communication device 1700 and/or allowing output of information from the wireless communication device 1700), a power supply (e.g., a battery and associated power circuitry), etc.

[0130] In some embodiments, a computer program including instructions which, when executed by at least one processor, causes the at least one processor to carry out the functionality of the wireless communication device 1700 according to any of the embodiments described herein is provided. In some embodiments, a carrier comprising the aforementioned computer program product is provided. The carrier is one of an electronic signal, an optical signal, a radio signal, or a computer readable storage medium (e.g., a non-transitory computer readable medium such as memory).

[0131] FIG. 18 is a schematic block diagram of the wireless communication device 1700 according to some other embodiments of the present disclosure. The wireless communication device 1700 includes one or more modules 1800, each of which is implemented in software. The module(s) 1800 provide the functionality of the wireless communication device 1700 described herein (e.g., one or more functions of the wireless communication device 512 or UE 512 described above).

[0132] With reference to FIG. 19, in accordance with an embodiment, a communication system includes a telecommunication network 1900, such as a 3GPP-type cellular network, which comprises an access network 1902, such as a RAN, and a core network 1904. The access network 1902 comprises a plurality of base stations 1906A, 1906B, 1906C, such as Node Bs, eNBs, gNBs, or other types of wireless Access Points (APs), each defining a corresponding coverage area 1908A, 1908B, 1908C. Each base station 1906A, 1906B, 1906C is connectable to the core network 1904 over a wired or wireless connection 1910. A first UE 1912 located in coverage area 1908C is configured to wirelessly connect to, or be paged by, the corresponding base station 1906C. A second UE 1914 in coverage area 1908A is wirelessly connectable to the corresponding base station 1906A. While a plurality of UEs 1912, 1914 are illustrated in this example, the disclosed embodiments are equally applicable to a situation where a sole UE is in the coverage area or where a sole UE is connecting to the corresponding base station 1906.

[0133] The telecommunication network 1900 is itself connected to a host computer 1916, 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 1916 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. Connections 1918 and 1920 between the telecommunication network 1900 and the host computer 1916 may extend directly from the core network 1904 to the host computer 1916 or may go via an optional intermediate network 1922. The intermediate network 1922 may be one of, or a combination of more than one of, a public, private, or hosted network; the intermediate network 1922, if any, may be a backbone network or the Internet; in particular, the intermediate network 1922 may comprise two or more sub-networks (not shown).

[0134] The communication system of FIG. 19 as a whole enables connectivity between the connected UEs 1912, 1914 and the host computer 1916. The connectivity may be described as an Over-the-Top (OTT) connection 1924. The host computer 1916 and the connected UEs 1912, 1914 are configured to communicate data and/or signaling via the OTT connection 1924, using the access network 1902, the core network 1904, any intermediate network 1922, and possible further infrastructure (not shown) as intermediaries. The OTT connection 1924 may be transparent in the sense that the participating communication devices through which the OTT connection 1924 passes are unaware of routing of uplink and downlink communications. For example, the base station 1906 may not or need not be informed about the past routing of an incoming downlink communication with data originating from the host computer 1916 to be forwarded (e.g., handed over) to a connected UE 1912. Similarly, the base station 1906 need not be aware of the future routing of an outgoing uplink communication originating from the UE 1912 towards the host computer 1916.

[0135] Example implementations, in accordance with an embodiment, of the UE, base station, and host computer discussed in the preceding paragraphs will now be described with reference to FIG. 20. In a communication system 2000, a host computer 2002 comprises hardware 2004 including a communication interface 2006 configured to set up and maintain a wired or wireless connection with an interface of a different communication device of the communication system 2000. The host computer 2002 further comprises processing circuitry 2008, which may have storage and/or processing capabilities. In particular, the processing circuitry 2008 may comprise one or more programmable processors, ASICs, FPGAs, or combinations of these (not shown) adapted to execute instructions. The host computer 2002 further comprises software 2010, which is stored in or accessible by the host computer 2002 and executable by the processing circuitry 2008. The software 2010 includes a host application 2012. The host application 2012 may be operable to provide a service to a remote user, such as a UE 2014 connecting via an OTT connection 2016 terminating at the UE 2014 and the host computer 2002. In providing the service to the remote user, the host application 2012 may provide user data which is transmitted using the OTT connection 2016.

[0136] The communication system 2000 further includes a base station 2018 provided in a telecommunication system and comprising hardware 2020 enabling it to communicate with the host computer 2002 and with the UE 2014. The hardware 2020 may include a communication interface 2022 for setting up and maintaining a wired or wireless connection with an interface of a different communication device of the communication system 2000, as well as a radio interface 2024 for setting up and maintaining at least a wireless connection 2026 with the UE 2014 located in a coverage area (not shown in FIG. 20) served by the base station 2018. The communication interface 2022 may be configured to facilitate a connection 2028 to the host computer 2002. The connection 2028 may be direct or it may pass through a core network (not shown in FIG. 20) of the telecommunication system and/or through one or more intermediate networks outside the telecommunication system. In the embodiment shown, the hardware 2020 of the base station 2018 further includes processing circuitry 2030, which may comprise one or more programmable processors, ASICs, FPGAs, or combinations of these (not shown) adapted to execute instructions. The base station 2018 further has software 2032 stored internally or accessible via an external connection.

[0137] The communication system 2000 further includes the UE 2014 already referred to. The UE's 2014 hardware 2034 may include a radio interface 2036 configured to set up and maintain a wireless connection 2026 with a base station serving a coverage area in which the UE 2014 is currently located. The hardware 2034 of the UE 2014 further includes processing circuitry 2038, which may comprise one or more programmable processors, ASICs, FPGAs, or combinations of these (not shown) adapted to execute instructions. The UE 2014 further comprises software 2040, which is stored in or accessible by the UE 2014 and executable by the processing circuitry 2038. The software 2040 includes a client application 2042. The client application 2042 may be operable to provide a service to a human or non-human user via the UE 2014, with the support of the host computer 2002. In the host computer 2002, the executing host application 2012 may communicate with the executing client application 2042 via the OTT connection 2016 terminating at the UE 2014 and the host computer 2002. In providing the service to the user, the client application 2042 may receive request data from the host application 2012 and provide user data in response to the request data. The OTT connection 2016 may transfer both the request data and the user data. The client application 2042 may interact with the user to generate the user data that it provides.

[0138] It is noted that the host computer 2002, the base station 2018, and the UE 2014 illustrated in FIG. 20 may be similar or identical to the host computer 1916, one of the base stations 1906A, 1906B, 1906C, and one of the UEs 1912, 1914 of FIG. 19, respectively. This is to say, the inner workings of these entities may be as shown in FIG. 20 and independently, the surrounding network topology may be that of FIG. 19.

[0139] In FIG. 20, the OTT connection 2016 has been drawn abstractly to illustrate the communication between the host computer 2002 and the UE 2014 via the base station 2018 without explicit reference to any intermediary devices and the precise routing of messages via these devices. The network infrastructure may determine the routing, which may be configured to hide from the UE 2014 or from the service provider operating the host computer 2002, or both. While the OTT connection 2016 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).

[0140] The wireless connection 2026 between the UE 2014 and the base station 2018 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 UE 2014 using the OTT connection 2016, in which the wireless connection 2026 forms the last segment. More precisely, the teachings of these embodiments may improve, e.g., reliability and thereby provide benefits such as, e.g., improved performance.

[0141] 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 2016 between the host computer 2002 and the UE 2014, in response to variations in the measurement results. The measurement procedure and/or the network functionality for reconfiguring the OTT connection 2016 may be implemented in the software 2010 and the hardware 2004 of the host computer 2002 or in the software 2040 and the hardware 2034 of the UE 2014, or both. In some embodiments, sensors (not shown) may be deployed in or in association with communication devices through which the OTT connection 2016 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 the software 2010, 2040 may compute or estimate the monitored quantities. The reconfiguring of the OTT connection 2016 may include message format, retransmission settings, preferred routing, etc.; the reconfiguring need not affect the base station 2018, and it may be unknown or imperceptible to the base station 2018. Such procedures and functionalities may be known and practiced in the art. In certain embodiments, measurements may involve proprietary UE signaling facilitating the host computer 2002's measurements of throughput, propagation times, latency, and the like. The measurements may be implemented in that the software 2010 and 2040 causes messages to be transmitted, in particular empty or ‘dummy’ messages, using the OTT connection 2016 while it monitors propagation times, errors, etc.

[0142] FIG. 21 is a flowchart illustrating a method implemented in a communication system, in accordance with one embodiment. The communication system includes a host computer, a base station, and a UE which may be those described with reference to FIGS. 19 and 20. For simplicity of the present disclosure, only drawing references to FIG. 21 will be included in this section. In step 2100, the host computer provides user data. In sub-step 2102 (which may be optional) of step 2100, the host computer provides the user data by executing a host application. In step 2104, the host computer initiates a transmission carrying the user data to the UE. In step 2106 (which may be optional), the base station transmits to the UE the user data which was carried in the transmission that the host computer initiated, in accordance with the teachings of the embodiments described throughout this disclosure. In step 2108 (which may also be optional), the UE executes a client application associated with the host application executed by the host computer.

[0143] FIG. 22 is a flowchart illustrating a method implemented in a communication system, in accordance with one embodiment. The communication system includes a host computer, a base station, and a UE which may be those described with reference to FIGS. 19 and 20. For simplicity of the present disclosure, only drawing references to FIG. 22 will be included in this section. In step 2200 of the method, the host computer provides user data. In an optional sub-step (not shown) the host computer provides the user data by executing a host application. In step 2202, the host computer initiates a transmission carrying the user data to the UE. The transmission may pass via the base station, in accordance with the teachings of the embodiments described throughout this disclosure. In step 2204 (which may be optional), the UE receives the user data carried in the transmission.

[0144] FIG. 23 is a flowchart illustrating a method implemented in a communication system, in accordance with one embodiment. The communication system includes a host computer, a base station, and a UE which may be those described with reference to FIGS. 19 and 20. For simplicity of the present disclosure, only drawing references to FIG. 23 will be included in this section. In step 2300 (which may be optional), the UE receives input data provided by the host computer. Additionally or alternatively, in step 2302, the UE provides user data. In sub-step 2304 (which may be optional) of step 2300, the UE provides the user data by executing a client application. In sub-step 2306 (which may be optional) of step 2302, the UE executes a client application which provides the user data in reaction to the received input data provided by the host computer. In providing the user data, the executed client application may further consider user input received from the user. Regardless of the specific manner in which the user data was provided, the UE initiates, in sub-step 2308 (which may be optional), transmission of the user data to the host computer. In step 2310 of the method, the host computer receives the user data transmitted from the UE, in accordance with the teachings of the embodiments described throughout this disclosure.

[0145] FIG. 24 is a flowchart illustrating a method implemented in a communication system, in accordance with one embodiment. The communication system includes a host computer, a base station, and a UE which may be those described with reference to FIGS. 19 and 20. For simplicity of the present disclosure, only drawing references to FIG. 24 will be included in this section. In step 2400 (which may be optional), in accordance with the teachings of the embodiments described throughout this disclosure, the base station receives user data from the UE. In step 2402 (which may be optional), the base station initiates transmission of the received user data to the host computer. In step 2404 (which may be optional), the host computer receives the user data carried in the transmission initiated by the base station.

[0146] Any appropriate steps, methods, features, functions, or benefits disclosed herein may be performed through one or more functional units or modules of one or more virtual apparatuses. Each virtual apparatus may comprise a number of these functional units. These functional units may be implemented via processing circuitry, which may include one or more microprocessor or microcontrollers, as well as other digital hardware, which may include Digital Signal Processor (DSPs), special-purpose digital logic, and the like. The processing circuitry may be configured to execute program code stored in memory, which may include one or several types of memory such as Read Only Memory (ROM), Random Access Memory (RAM), cache memory, flash memory devices, optical storage devices, etc. Program code stored in memory includes program instructions for executing one or more telecommunications and/or data communications protocols as well as instructions for carrying out one or more of the techniques described herein. In some implementations, the processing circuitry may be used to cause the respective functional unit to perform corresponding functions according one or more embodiments of the present disclosure.

[0147] While processes in the figures may show a particular order of operations performed by certain embodiments of the present disclosure, it should be understood that such order is exemplary (e.g., alternative embodiments may perform the operations in a different order, combine certain operations, overlap certain operations, etc.).

[0148] Some example embodiments of the present disclosure are as follows:

Group A Embodiments

[0149] Embodiment 1: A method performed by a wireless communication device (512) for activation of multiple Transmission Configuration Indication, TCI, states for a Physical Downlink Control Channel, PDCCH, in one or more Control Resource Sets, CORESETs, in a cellular communications system (500), the method comprising: receiving (600), from a network node (502; 506; 1700), signaling that activates N.sub.TCI TCI states for one or more CORESETs, wherein N.sub.TCI>1.

[0150] Embodiment 2: The method of embodiment 1 further comprising receiving (602) PDCCHs in the one or more CORESETs in accordance with the N.sub.TCI TCI states that are activated for one or more CORESETs.

[0151] Embodiment 3: The method of embodiment 2 further comprising performing (604) one or more actions in accordance with downlink control information carried by the received PDCCHs.

[0152] Embodiment 4: The method of embodiment 2 or 3 wherein the received PDCCHs comprise two copies of a same DCI received from two or more respective transmission points, and the two or more respective transmission points correspond to two or more respective TCI states from among the N.sub.TCI TCI states that are activated for one or more CORESETs.

[0153] Embodiment 5: The method of embodiment 4 wherein the two copies of the same DCI are received from the two or more respective transmission points in a same CORESET.

[0154] Embodiment 6: The method of any one of embodiments 1 to 4 wherein the one or more CORESETs consist of a single CORESET, and the N.sub.TCI TCI states are activated for the single CORESET.

[0155] Embodiment 7: The method of any one of embodiments 1 to 4 wherein the one or more CORESETs comprise two or more CORESETs, and the signaling comprises, for each CORESET of the two or more CORESETs, information that indicates N.sub.TCI TCI states activated for the CORESET.

[0156] Embodiment 8: The method of embodiment 7 wherein N.sub.TCI is different for at least two of the two or more CORESETs.

[0157] Embodiment 9: The method of embodiment 7 wherein N.sub.TCI is the same for at least two of the two or more CORESETs.

[0158] Embodiment 10: The method of any one of embodiments 1 to 4 wherein receiving (600) the signaling that activates N.sub.TCI TCI states for one or more CORESETs comprises one or more of: receiving (700) a configuration of M TCI state lists for a CORESET, wherein each TCI state list of the M TCI state lists comprises up to a predefined or preconfigured maximum number of TCI states and M>1; and receiving (702), from the network node, an indication of one of the M TCI state lists for the CORESET, wherein TCI states in the one of the M TCI state lists are the N.sub.TCI TCI states that are activated for the CORESET.

[0159] Embodiment 11: The method of embodiment 10 wherein the predefined or preconfigured maximum number of TCI states is greater than or equal to 2.

[0160] Embodiment 12: The method of embodiment 10 or 11 wherein receiving (702) the indication of the one of the M TCI state lists for the CORESET comprises receiving a MAC CE that comprises the indication of the one of the M TCI state lists for the CORESET.

[0161] Embodiment 13: The method of embodiment 10 or 11 wherein receiving (702) the indication of the one of the M TCI state lists for the CORESET comprises receiving a MAC CE that comprises one or more of: a first octet that comprises a serving cell identity, ID, of a serving cell of the wireless communication device (512) and a first part of a CORESET ID of the CORESET; and a second octet that comprises a second part of the CORESET ID of the CORESET and a TCI state ID; wherein the wireless communication device (512) interprets the TCI state ID as the indication (e.g., index or ID) of the one of the M TCI state lists for the CORESET.

[0162] Embodiment 14: The method of any one of embodiments 10 to 13 wherein receiving (600) the signaling that activates N.sub.TCI TCI states for one or more CORESETs comprises: receiving (702), from the network node, a MAC CE that comprises, for each CORESET of the one or more CORESETs, information that indicates the N.sub.TCI TCI states that are activated for the CORESET.

[0163] Embodiment 15: The method of embodiment 14 wherein the one or more CORESETs consist of a single CORESET, and the MAC CE comprises, for each TCI state of the N.sub.TCI TCI states that are activated for the single CORESET, an indication (e.g., ID) of the TCI state.

[0164] Embodiment 16: The method of embodiment 15 wherein the MAC CE comprises one or more of: a first octet that comprises a serving cell identity, ID, of a serving cell of the wireless communication device (512) and a first part of a CORESET ID of the single CORESET; a second octet that comprises a second part of the CORESET ID of the single CORESET and a first TCI state ID of a first TCI state of the N.sub.TCI TCI states that are activated for the single CORESET; and a third octet that comprises a second TCI state ID of a second TCI state of the N.sub.TCI TCI states that are activated for the single CORESET.

[0165] Embodiment 17: The method of embodiment 16 wherein the MAC CE further comprises an indication of which of the N.sub.TCI TCI states that are activated for the single CORESET is a default TCI state for physical downlink shared channel, PDSCH.

[0166] Embodiment 18: The method of embodiment 16 wherein the first TCI state indicated by the first TCI state ID in the second octet of the MAC CE is a default TCI state for physical downlink shared channel, PDSCH.

[0167] Embodiment 19: The method of any of embodiments 15 to 18 wherein the MAC CE is a fixed size MAC CE.

[0168] Embodiment 20: The method of any of embodiments 15 to 18 wherein the MAC CE is a flexible size MAC CE, wherein a size of the MAC CE is indicated by a length field of an associated header and the wireless communication device (512) interprets a value of N.sub.TCI based on a value of the length field.

[0169] Embodiment 21: The method of embodiment 15 wherein the MAC CE comprises one or more of: a first octet that comprises a serving cell identity, ID, of a serving cell of the wireless communication device (512) and a first part of a CORESET ID of the single CORESET; a second octet that comprises a second part of the CORESET ID of the single CORESET and a first part of a TCI state ID of a first TCI state of the N.sub.TCI TCI states that are activated for the single CORESET; and a third octet that comprises a second part of the TCI state ID of the first TCI state of the N.sub.TCI TCI states that are activated for the single CORESET and a second TCI state ID of a second TCI state of the N.sub.TCI TCI states that are activated for the single CORESET.

[0170] Embodiment 22: The method of embodiment 15 wherein the MAC CE comprises one or more of: a first octet that comprises a serving cell identity, ID, of a serving cell of the wireless communication device (512) and a first part of a CORESET ID of the single CORESET; a second octet that comprises a second part of the CORESET ID of the single CORESET and a first TCI state ID of a first TCI state of the N.sub.TCI TCI states that are activated for the single CORESET; a third octet that comprises a second TCI state ID of a second TCI state of the N.sub.TCI TCI states that are activated for the single CORESET and a first part of a third TCI state ID of a third TCI state of the of the N.sub.TCI TCI states that are activated for the single CORESET; and a fourth octet that comprises a second part of the third TCI state ID of the third TCI state of the of the N.sub.TCI TCI states that are activated for the single CORESET.

[0171] Embodiment 23: The method of embodiment 22 wherein the MAC CE further comprises an indication of which of the N.sub.TCI TCI states that are activated for the single CORESET is a default TCI state for physical downlink shared channel, PDSCH.

[0172] Embodiment 24: The method of embodiment 22 wherein the first TCI state indicated by the first TCI state ID in the second octet of the MAC CE is a default TCI state for physical downlink shared channel, PDSCH.

[0173] Embodiment 25: The method of embodiment 15 wherein the MAC CE comprises one or more of: [0174] a first octet that comprises one or more of: [0175] a serving cell identity, ID, of a serving cell of the wireless communication device (512); and [0176] a first part of a CORESET ID of the single CORESET; [0177] a second octet that comprises one or more of: [0178] a second part of the CORESET ID of the single CORESET; and [0179] a first TCI state ID of a first TCI state of the N.sub.TCI TCI states that are activated for the single CORESET; and [0180] a third octet that comprises one or more of: [0181] an indication of whether a second TCI state of the N.sub.TCI TCI states that are activated for the single CORESET is a default TCI state for physical downlink shared channel, PDSCH; and [0182] a second TCI state ID of a second TCI state of the N.sub.TCI TCI states that are activated for the single CORESET.

[0183] Embodiment 26: The method of embodiment 25 wherein the MAC CE further comprises: [0184] a fourth octet that comprises one or more of: [0185] an indication of whether a third TCI state of the N.sub.TCI TCI states that are activated for the single CORESET is a default TCI state for physical downlink shared channel, PDSCH; and [0186] a third TCI state ID of the third TCI state of the of the N.sub.TCI TCI states that are activated for the single CORESET.

[0187] Embodiment 27: The method of embodiment 14 wherein the one or more CORESETs comprise two or more CORESETs, and the MAC CE comprises, for each CORESET of the two or more CORESETs, [0188] for each TCI state of the N.sub.TCI TCI states that are activated for the CORESET, an indication (e.g., ID) of the TCI state.

[0189] Embodiment 28: The method of embodiment 27 wherein the MAC CE comprises one or more of: [0190] a first octet that comprises one or more of: [0191] a serving cell identity, ID, of a serving cell of the wireless communication device (512); and [0192] a first part of a first CORESET ID of a first CORESET of the two or more CORESETs; [0193] a second octet that comprises one or more of: [0194] a second part of the first CORESET ID of the first CORESET; and [0195] a first TCI state ID of a first TCI state of the N.sub.TCI TCI states that are activated for the first CORESET; and [0196] a third octet that comprises one or more of: [0197] an indication of whether additional octets are present; and [0198] a second TCI state ID of a second TCI state of the N.sub.TCI TCI states that are activated for the first CORESET.

[0199] Embodiment 29: The method of embodiment 28 wherein the MAC CE further comprises one or more of: [0200] a first additional octet that comprises a second CORESET ID of a second CORESET of the two or more CORESETs; [0201] a second additional octet that comprises a first TCI state ID of a first TCI state of the N.sub.TCI TCI states that are activated for the second CORESET; and [0202] a third additional octet that comprises one or more of: [0203] an indication of whether additional octets are present; and [0204] a second TCI state ID of a second TCI state of the N.sub.TCI TCI states that are activated for the second CORESET.

[0205] Embodiment 30: A method performed by a wireless communication device (512) for activation of multiple Transmission Configuration Indication, TCI, states for a Physical Downlink Control Channel, PDCCH, in one or more Control Resource Sets, CORESETs, in a cellular communications system (500), the method comprising one or more of: [0206] receiving, from a network node (502; 506; 1700), a configuration of M TCI state lists, each comprising of two or more TCI states; and [0207] receiving an activation command carried by a MAC CE indicating one or more of: [0208] a TCI state list from the M TCI state lists if M>1; or [0209] a first and a second TCI states in the M TCI state lists if M=1 for PDCCH in the CORESET. (Note: For example, in the above disclosure, a case where a single list of TCI states is configured for a CORESET, a MAC CE is used to activate 2 or more TCI states from the list.)

[0210] Embodiment 31: The method of embodiment 30, wherein the MAC CE when M>1 is an existing MAC CE with its TCI state ID field being interpreted as an index or ID of a TCI state list.

[0211] Embodiment 32: The method of embodiment 30, wherein the MAC CE when M>1 consists of a first and a second TCI state IDs in a first and a second Octet for the first and the second TCI states, respectively.

[0212] Embodiment 33: The method of embodiment 30, wherein the MAC CE when M>1 further comprises a bit “C” field in a same Octet as the second TCI state ID to indicate one of the first and the second TCI states as a default TCI state for physical downlink shared channel, PDSCH.

[0213] Embodiment 34: The method of embodiment 30, wherein the method further comprises activating a third TCI state in the CORESET.

[0214] Embodiment 35: The method of embodiment 34, wherein the MAC CE when M>1 further comprises a third TCI state ID in a third octet for the third TCI state.

[0215] Embodiment 36: The method of embodiment 35, wherein the MAC CE when >1 further comprises of a “C” field in the third octet to indicate one of the first, the second, and the third TCI states as a default TCI state for physical downlink shared channel, PDSCH.

[0216] Embodiment 37: The methods of embodiment 35, wherein the MAC CE when M>1 further comprises a one bit “C” field in each of the second and the third octets to indicate one of the first, the second, and the third TCI states as a default TCI state for physical downlink shared channel, PDSCH.

[0217] Embodiment 38: The method of any of the previous embodiments, further comprising: providing user data; and forwarding the user data to a host computer via the transmission to the base station.

Group B Embodiments

[0218] Embodiment 39: A method performed by a network node (502) for activation of multiple Transmission Configuration Indication, TCI, states for a Physical Downlink Control Channel, PDCCH, in one or more Control Resource Sets, CORESETs, in a cellular communications system (500), the method comprising: sending (600), to a wireless communication device (512), signaling that activates N.sub.TCI TCI states for one or more CORESETs, wherein N.sub.TCI>1.

[0219] Embodiment 40: The method of embodiment 39 wherein the one or more CORESETs consist of a single CORESET, and the N.sub.TCI TCI states are activated for the single CORESET.

[0220] Embodiment 41: The method of embodiment 39 wherein the one or more CORESETs comprise two or more CORESETs, and the signaling comprises, for each CORESET of the two or more CORESETs, information that indicates N.sub.TCI TCI states activated for the CORESET.

[0221] Embodiment 42: The method of embodiment 41 wherein N.sub.TCI is different for at least two of the two or more CORESETs.

[0222] Embodiment 43: The method of embodiment 41 wherein N.sub.TCI is the same for at least two of the two or more CORESETs.

[0223] Embodiment 44: The method of embodiment 39 wherein sending (600) the signaling that activates N.sub.TCI TCI states for one or more CORESETs comprises one or more of: sending (700), to the wireless communication device (512), a configuration of M TCI state lists for a CORESET, wherein each TCI state list of the M TCI state lists comprises up to a predefined or preconfigured maximum number of TCI states and M>1; and sending (702), to the wireless communication device (512), an indication of one of the M TCI state lists for the CORESET, wherein TCI states in the one of the M TCI state lists are the N.sub.TCI TCI states that are activated for the CORESET.

[0224] Embodiment 45: The method of embodiment 44 wherein the predefined or preconfigured maximum number of TCI states is greater than or equal to 2.

[0225] Embodiment 46: The method of embodiment 44 or 45 wherein sending (702) the indication of the one of the M TCI state lists for the CORESET comprises sending a MAC CE that comprises the indication of the one of the M TCI state lists for the CORESET.

[0226] Embodiment 47: The method of embodiment 44 or 45 wherein sending (702) the indication of the one of the M TCI state lists for the CORESET comprises sending a MAC CE that comprises one or more of: a first octet that comprises a serving cell identity, ID, of a serving cell of the wireless communication device (512) and a first part of a CORESET ID of the CORESET; and a second octet that comprises a second part of the CORESET ID of the CORESET and a TCI state ID; wherein the TCI state ID is interpreted as the indication (e.g., index or ID) of the one of the M TCI state lists for the CORESET.

[0227] Embodiment 48: The method of embodiment 39 wherein sending (600) the signaling that activates N.sub.TCI TCI states for one or more CORESETs comprises: sending (702), to the wireless communication device (512), a MAC CE that comprises, for each CORESET of the one or more CORESETs, indicates of the N.sub.TCI TCI states that are activated for the CORESET.

[0228] Embodiment 49: The method of embodiment 48 wherein the one or more CORESETs consist of a single CORESET, and the MAC CE comprises, for each TCI state of the N.sub.TCI TCI states that are activated for the single CORESET, an indication (e.g., ID) of the TCI state.

[0229] Embodiment 50: The method of embodiment 49 wherein the MAC CE comprises one or more of: a first octet that comprises a serving cell identity, ID, of a serving cell of the wireless communication device (512) and a first part of a CORESET ID of the single CORESET; a second octet that comprises a second part of the CORESET ID of the single CORESET and a first TCI state ID of a first TCI state of the N.sub.TCI TCI states that are activated for the single CORESET; and a third octet that comprises a second TCI state ID of a second TCI state of the N.sub.TCI TCI states that are activated for the single CORESET.

[0230] Embodiment 51: The method of embodiment 50 wherein the MAC CE further comprises an indication of which of the N.sub.TCI TCI states that are activated for the single CORESET is a default TCI state for physical downlink shared channel, PDSCH.

[0231] Embodiment 52: The method of embodiment 50 wherein the first TCI state indicated by the first TCI state ID in the second octet of the MAC CE is a default TCI state for physical downlink shared channel, PDSCH.

[0232] Embodiment 53: The method of any of embodiments 49 to 52 wherein the MAC CE is a fixed size MAC CE.

[0233] Embodiment 54: The method of any of embodiments 49 to 52 wherein the MAC CE is a flexible size MAC CE, wherein a size of the MAC CE is indicated by a length field of an associated header and the wireless communication device (512) interprets a value of N.sub.TCI based on a value of the length field.

[0234] Embodiment 55: The method of embodiment 49 wherein the MAC CE comprises one or more of: a first octet that comprises a serving cell identity, ID, of a serving cell of the wireless communication device (512) and a first part of a CORESET ID of the single CORESET; a second octet that comprises a second part of the CORESET ID of the single CORESET and a first part of a TCI state ID of a first TCI state of the N.sub.TCI TCI states that are activated for the single CORESET; and a third octet that comprises a second part of the TCI state ID of the first TCI state of the N.sub.TCI TCI states that are activated for the single CORESET and a second TCI state ID of a second TCI state of the N.sub.TCI TCI states that are activated for the single CORESET.

[0235] Embodiment 56: The method of embodiment 49 wherein the MAC CE comprises one or more of: a first octet that comprises a serving cell identity, ID, of a serving cell of the wireless communication device (512) and a first part of a CORESET ID of the single CORESET; a second octet that comprises a second part of the CORESET ID of the single CORESET and a first TCI state ID of a first TCI state of the N.sub.TCI TCI states that are activated for the single CORESET; a third octet that comprises a second TCI state ID of a second TCI state of the N.sub.TCI TCI states that are activated for the single CORESET and a first part of a third TCI state ID of a third TCI state of the of the N.sub.TCI TCI states that are activated for the single CORESET; and a fourth octet that comprises a second part of the third TCI state ID of the third TCI state of the of the N.sub.TCI TCI states that are activated for the single CORESET.

[0236] Embodiment 57: The method of embodiment 56 wherein the MAC CE further comprises an indication of which of the N.sub.TCI TCI states that are activated for the single CORESET is a default TCI state for physical downlink shared channel, PDSCH.

[0237] Embodiment 58: The method of embodiment 56 wherein the first TCI state indicated by the first TCI state ID in the second octet of the MAC CE is a default TCI state for physical downlink shared channel, PDSCH.

[0238] Embodiment 59: The method of embodiment 49 wherein the MAC CE comprises one or more of: [0239] a first octet that comprises one or more of: [0240] a serving cell identity, ID, of a serving cell of the wireless communication device (512); and [0241] a first part of a CORESET ID of the single CORESET; [0242] a second octet that comprises one or more of: [0243] a second part of the CORESET ID of the single CORESET; and [0244] a first TCI state ID of a first TCI state of the N.sub.TCI TCI states that are activated for the single CORESET; and [0245] a third octet that comprises one or more of: [0246] an indication of whether a second TCI state of the N.sub.TCI TCI states that are activated for the single CORESET is a default TCI state for physical downlink shared channel, PDSCH; and [0247] a second TCI state ID of a second TCI state of the N.sub.TCI TCI states that are activated for the single CORESET.

[0248] Embodiment 60: The method of embodiment 59 wherein the MAC CE further comprises: [0249] a fourth octet that comprises one or more of: [0250] an indication of whether a third TCI state of the N.sub.TCI TCI states that are activated for the single CORESET is a default TCI state for physical downlink shared channel, PDSCH; and [0251] a third TCI state ID of the third TCI state of the of the N.sub.TCI TCI states that are activated for the single CORESET.

[0252] Embodiment 61: The method of embodiment 48 wherein the one or more CORESETs comprise two or more CORESETs, and the MAC CE comprises, for CORESET of the two or more CORESETs, [0253] for each TCI state of the N.sub.TCI TCI states that are activated for the CORESET, an indication (e.g., ID) of the TCI state.

[0254] Embodiment 62: The method of embodiment 61 wherein the MAC CE comprises one or more of: [0255] a first octet that comprises one or more of: [0256] a serving cell identity, ID, of a serving cell of the wireless communication device (512); and [0257] a first part of a first CORESET ID of a first CORESET of the two or more CORESETs; [0258] a second octet that comprises one or more of: [0259] a second part of the first CORESET ID of the first CORESET; and [0260] a first TCI state ID of a first TCI state of the N.sub.TCI TCI states that are activated for the first CORESET; and [0261] a third octet that comprises one or more of: [0262] an indication of whether additional octets are present; and [0263] a second TCI state ID of a second TCI state of the N.sub.TCI TCI states that are activated for the first CORESET.

[0264] Embodiment 63: The method of embodiment 62 wherein the MAC CE further comprises one or more of: [0265] a first additional octet that comprises a second CORESET ID of a second CORESET of the two or more CORESETs; [0266] a second additional octet that comprises a first TCI state ID of a first TCI state of the N.sub.TCI TCI states that are activated for the second CORESET; and [0267] a third octet that comprises one or more of: [0268] an indication of whether additional octets are present; and [0269] a second TCI state ID of a second TCI state of the N.sub.TCI TCI states that are activated for the second CORESET.

[0270] Embodiment 64: The method of any of the previous embodiments, further comprising: obtaining user data; and forwarding the user data to a host computer or a wireless communication device.

Group C Embodiments

[0271] Embodiment 65: A wireless communication device comprising: processing circuitry configured to perform any of the steps of any of the Group A embodiments; and power supply circuitry configured to supply power to the wireless communication device.

[0272] Embodiment 66: A base station comprising: processing circuitry configured to perform any of the steps of any of the Group B embodiments; and power supply circuitry configured to supply power to the base station.

[0273] Embodiment 67: A User Equipment, UE, comprising: an antenna configured to send and receive wireless signals; radio front-end circuitry connected to the antenna and to processing circuitry, and configured to condition signals communicated between the antenna and the processing circuitry; the processing circuitry being configured to perform any of the steps of any of the Group A embodiments; an input interface connected to the processing circuitry and configured to allow input of information into the UE to be processed by the processing circuitry; an output interface connected to the processing circuitry and configured to output information from the UE that has been processed by the processing circuitry; and a battery connected to the processing circuitry and configured to supply power to the UE.

[0274] Embodiment 68: A communication system including a host computer comprising: processing circuitry configured to provide user data; and a communication interface configured to forward the user data to a cellular network for transmission to a User Equipment, UE; wherein the cellular network comprises a base station having a radio interface and processing circuitry, the base station's processing circuitry configured to perform any of the steps of any of the Group B embodiments.

[0275] Embodiment 69: The communication system of the previous embodiment further including the base station.

[0276] Embodiment 70: The communication system of the previous 2 embodiments, further including the UE, wherein the UE is configured to communicate with the base station.

[0277] Embodiment 71: The communication system of the previous 3 embodiments, wherein: the processing circuitry of the host computer is configured to execute a host application, thereby providing the user data; and the UE comprises processing circuitry configured to execute a client application associated with the host application.

[0278] Embodiment 72: A method implemented in a communication system including a host computer, a base station, and a User Equipment, UE, the method comprising: at the host computer, providing user data; and at the host computer, initiating a transmission carrying the user data to the UE via a cellular network comprising the base station, wherein the base station performs any of the steps of any of the Group B embodiments.

[0279] Embodiment 73: The method of the previous embodiment, further comprising, at the base station, transmitting the user data.

[0280] Embodiment 74: The method of the previous 2 embodiments, wherein the user data is provided at the host computer by executing a host application, the method further comprising, at the UE, executing a client application associated with the host application.

[0281] Embodiment 75: A User Equipment, UE, configured to communicate with a base station, the UE comprising a radio interface and processing circuitry configured to perform the method of the previous 3 embodiments.

[0282] Embodiment 76: A communication system including a host computer comprising: processing circuitry configured to provide user data; and a communication interface configured to forward user data to a cellular network for transmission to a User Equipment, UE; wherein the UE comprises a radio interface and processing circuitry, the UE's components configured to perform any of the steps of any of the Group A embodiments.

[0283] Embodiment 77: The communication system of the previous embodiment, wherein the cellular network further includes a base station configured to communicate with the UE.

[0284] Embodiment 78: The communication system of the previous 2 embodiments, wherein: the processing circuitry of the host computer is configured to execute a host application, thereby providing the user data; and the UE's processing circuitry is configured to execute a client application associated with the host application.

[0285] Embodiment 79: A method implemented in a communication system including a host computer, a base station, and a User Equipment, UE, the method comprising: at the host computer, providing user data; and at the host computer, initiating a transmission carrying the user data to the UE via a cellular network comprising the base station, wherein the UE performs any of the steps of any of the Group A embodiments.

[0286] Embodiment 80: The method of the previous embodiment, further comprising at the UE, receiving the user data from the base station.

[0287] Embodiment 81: A communication system including a host computer comprising: communication interface configured to receive user data originating from a transmission from a User Equipment, UE, to a base station; wherein the UE comprises a radio interface and processing circuitry, the UE's processing circuitry configured to perform any of the steps of any of the Group A embodiments.

[0288] Embodiment 82: The communication system of the previous embodiment, further including the UE.

[0289] Embodiment 83: The communication system of the previous 2 embodiments, further including the base station, wherein the base station comprises a radio interface configured to communicate with the UE and a communication interface configured to forward to the host computer the user data carried by a transmission from the UE to the base station.

[0290] Embodiment 84: The communication system of the previous 3 embodiments, wherein: the processing circuitry of the host computer is configured to execute a host application; and the UE's processing circuitry is configured to execute a client application associated with the host application, thereby providing the user data.

[0291] Embodiment 85: The communication system of the previous 4 embodiments, wherein: the processing circuitry of the host computer is configured to execute a host application, thereby providing request data; and the UE's processing circuitry is configured to execute a client application associated with the host application, thereby providing the user data in response to the request data.

[0292] Embodiment 86: A method implemented in a communication system including a host computer, a base station, and a User Equipment, UE, the method comprising: at the host computer, receiving user data transmitted to the base station from the UE, wherein the UE performs any of the steps of any of the Group A embodiments.

[0293] Embodiment 87: The method of the previous embodiment, further comprising, at the UE, providing the user data to the base station.

[0294] Embodiment 88: The method of the previous 2 embodiments, further comprising: at the UE, executing a client application, thereby providing the user data to be transmitted; and at the host computer, executing a host application associated with the client application.

[0295] Embodiment 89: The method of the previous 3 embodiments, further comprising: at the UE, executing a client application; and at the UE, receiving input data to the client application, the input data being provided at the host computer by executing a host application associated with the client application; wherein the user data to be transmitted is provided by the client application in response to the input data.

[0296] Embodiment 90: A communication system including a host computer comprising a communication interface configured to receive user data originating from a transmission from a User Equipment, UE, to a base station, wherein the base station comprises a radio interface and processing circuitry, the base station's processing circuitry configured to perform any of the steps of any of the Group B embodiments.

[0297] Embodiment 91: The communication system of the previous embodiment further including the base station.

[0298] Embodiment 92: The communication system of the previous 2 embodiments, further including the UE, wherein the UE is configured to communicate with the base station.

[0299] Embodiment 93: The communication system of the previous 3 embodiments, wherein: the processing circuitry of the host computer is configured to execute a host application; and the UE is configured to execute a client application associated with the host application, thereby providing the user data to be received by the host computer.

[0300] Embodiment 94: A method implemented in a communication system including a host computer, a base station, and a User Equipment, UE, the method comprising: at the host computer, receiving, from the base station, user data originating from a transmission which the base station has received from the UE, wherein the UE performs any of the steps of any of the Group A embodiments.

[0301] Embodiment 95: The method of the previous embodiment, further comprising at the base station, receiving the user data from the UE.

[0302] Embodiment 96: The method of the previous 2 embodiments, further comprising at the base station, initiating a transmission of the received user data to the host computer.

[0303] Those skilled in the art will recognize improvements and modifications to the embodiments of the present disclosure. All such improvements and modifications are considered within the scope of the concepts disclosed herein.