Control channel and reference signal transmission in wireless networks

Abstract

The present disclosure relates to control channel and reference signal transmissions in wireless networks. The present application relates to devices and components, including apparatuses, systems, and methods for control signaling and reference signal transmissions in wireless networks.

Description

[0001] This application is a divisional application of Chinese invention patent application filed on April 5, 2021, with national application number 202180005756.3 and invention title "Control Channel and Reference Signal Transmission in Wireless Network". Technical Field

[0002] This disclosure relates to the field of wireless communications. Background Technology

[0003] The 3GPP Technical Specifications (TS) define the standards for wireless networks. These TSs describe aspects related to control channels and reference signals that can be transmitted in a wireless network. Summary of the Invention

[0004] According to one aspect of this disclosure, a method of operating a base station is provided, the method comprising: generating an information element to include an indication of whether frequency domain (FD)-code division multiplexing (CDM) is enabled for a user equipment (UE); transmitting the information element to the UE; mapping one or more reference signals to one or more resource elements based on whether FD-CDM is enabled; and transmitting the one or more reference signals.

[0005] According to another aspect of this disclosure, a base station is provided, the base station comprising: processing circuitry configured to: generate information elements including an indication of whether frequency domain (FD)-code division multiplexing (CDM) is enabled for a user equipment (UE); map one or more demodulation reference signals (DMRS) to one or more resource elements based on whether FD-CDM is enabled; and interface circuitry coupled to the processing circuitry to transmit the information elements over the one or more DMRS.

[0006] According to another aspect of this disclosure, one or more non-transitory computer-readable media are provided, the one or more non-transitory computer-readable media having instructions that, when executed, cause a first user equipment (UE) to perform the following operations: receive from a base station an information element indicating whether frequency domain (FD)-code division multiplexing (CDM) is enabled for the first UE; receive a first reference signal for a first antenna port, the first reference signal being associated with a first downlink transmission of the first UE; and, based on whether FD-CDM is enabled, determine whether to schedule a second downlink transmission for a second UE, the second downlink transmission being associated with a second reference signal for a second antenna port, the second antenna port being in a CDM group with the first antenna port. Attached Figure Description

[0007] Figure 1 A network environment according to some implementation schemes is shown.

[0008] Figure 2 Transmission resources according to some implementation schemes are shown.

[0009] Figure 3 Transmission resources according to some implementation schemes are shown.

[0010] Figure 4 Transmission resources according to some implementation schemes are shown.

[0011] Figure 5 Transmission resources according to some implementation schemes are shown.

[0012] Figure 6 Transmission resources according to some implementation schemes are shown.

[0013] Figure 7 Transmission resources according to some implementation schemes are shown.

[0014] Figure 8 Transmission resources according to some implementation schemes are shown.

[0015] Figure 9 Transmission resources according to some implementation schemes are shown.

[0016] Figure 10 Transmission resources according to some implementation schemes are shown.

[0017] Figure 11 Transmission resources according to some implementation schemes are shown.

[0018] Figure 12 Transmission resources according to some implementation schemes are shown.

[0019] Figure 13 Transmission resources according to some implementation schemes are shown.

[0020] Figure 14 Control elements according to some implementation schemes are shown.

[0021] Figure 15 The downlink control information is shown according to some implementation schemes.

[0022] Figure 16 Transmission resources according to some implementation schemes are shown.

[0023] Figure 17 Transmission resources according to some implementation schemes are shown.

[0024] Figure 18 Transmission resources according to some implementation schemes are shown.

[0025] Figure 19The operational flow / algorithm structure according to some implementation schemes is shown.

[0026] Figure 20 Another operational flow / algorithm structure according to some implementation schemes is shown.

[0027] Figure 21 Another operational flow / algorithm structure according to some implementation schemes is shown.

[0028] Figure 22 User equipment according to some implementation schemes is shown.

[0029] Figure 23 A base station according to some implementation schemes is shown. Detailed Implementation

[0030] The following detailed description relates to the accompanying drawings. The same reference numerals may be used in different drawings to identify the same or similar elements. In the following description, specific details, such as particular structures, architectures, interfaces, technologies, etc., are set forth for illustrative and non-limiting purposes to provide a thorough understanding of various aspects of the various embodiments. However, it will be apparent to those skilled in the art that various aspects of the various embodiments may be practiced in other examples departing from these specific details. In some cases, descriptions of well-known devices, circuits, and methods have been omitted so as not to obscure the description of the various embodiments with unnecessary detail. For the purposes of this document, the phrase "A or B" means (A), (B), or (A and B).

[0031] The following is a glossary of terms that may be used in this disclosure.

[0032] As used herein, the term "circuit" refers to, is part of, or includes the following: hardware components such as electronic circuits, logic circuits, processors (shared, dedicated, or grouped) or memories (shared, dedicated, or grouped), application-specific integrated circuits (ASICs), field-programmable devices (FPDs) (e.g., field-programmable gate arrays (FPGAs), programmable logic devices (PLDs), complex PLDs (CPLDs), high-capacity PLDs (HCPLDs), structured ASICs, or programmable system-on-a-chip (SoCs)), digital signal processors (DSPs), etc. In some embodiments, a circuit may execute one or more software or firmware programs to provide at least some of the said functions. The term "circuit" may also refer to a combination of one or more hardware elements and program code for performing the functions (or a combination of circuits used in an electrical or electronic system). In these embodiments, the combination of hardware elements and program code may be referred to as a particular type of circuit.

[0033] As used herein, the term "processor circuit" means, is part of, or includes the following: a circuit capable of sequentially and automatically performing a series of arithmetic or logical operations or recording, storing, or transmitting digital data. The term "processor circuit" may also refer to an application processor, baseband processor, central processing unit (CPU), graphics processing unit, single-core processor, dual-core processor, triple-core processor, quad-core processor, or any other device capable of executing or otherwise operating computer-executable instructions (such as program code, software modules, and / or functional procedures).

[0034] As used herein, the term "interface circuit" refers to, is part of, or includes a circuit that enables the exchange of information between two or more components or devices. The term "interface circuit" can refer to one or more hardware interfaces, such as buses, I / O interfaces, peripheral component interfaces, network interface cards, etc.

[0035] As used herein, the term "user equipment" or "UE" refers to equipment of a remote user that has radio communication capabilities and can describe network resources in a communication network. Furthermore, the term "user equipment" or "UE" can be considered synonymous and can be referred to as a client, mobile phone, mobile device, mobile terminal, user terminal, mobile unit, mobile station, mobile user, subscriber, user, remote station, access agent, user agent, receiver, radio equipment, reconfigurable radio equipment, reconfigurable mobile device, etc. Additionally, the term "user equipment" or "UE" can include any type of wireless / wired equipment or any computing device that includes a wireless communication interface.

[0036] As used herein, the term "computer system" means any type of interconnected electronic device, computer device, or component thereof. Additionally, the term "computer system" or "system" may refer to the various components of a computer that are communicatively coupled to each other. Furthermore, the term "computer system" or "system" may refer to multiple computer devices or multiple computing systems that are communicatively coupled to each other and configured to share computing resources or network resources.

[0037] As used herein, the term "resource" refers to physical or virtual devices, physical or virtual components within a computing environment, or physical or virtual components within a specific device, such as computer equipment, mechanical equipment, memory space, processor / CPU time, processor / CPU utilization, processor and accelerator load, hardware time or utilization, power supply, input / output operations, port or network sockets, channel / link allocation, throughput, memory utilization, storage, network, databases and applications, units of workload, etc. "Hardware resource" can refer to computing, storage, or networking resources provided by physical hardware components. "Virtualized resource" can refer to computing, storage, or networking resources provided by virtualization infrastructure to applications, devices, systems, etc. The terms "network resource" or "communication resource" can refer to resources that computer equipment / systems can access via a communication network. The term "system resource" can refer to any kind of shared entity providing services and can include computing or network resources. System resources can be considered as a coherent set of functions, network data objects, or services accessible through a server, wherein such system resources reside on a single host or multiple hosts and are clearly identifiable.

[0038] As used herein, the term "channel" refers to any tangible or intangible transmission medium used for transmitting data or data streams. The term "channel" may be synonymous or equivalent with "communication channel," "data communication channel," "transmission channel," "data transmission channel," "access channel," "data access channel," "link," "data link," "carrier," "radio frequency carrier," or any other similar term indicating a path or medium through which data is transmitted. Additionally, as used herein, the term "link" refers to a connection between two devices used for transmitting and receiving information.

[0039] As used in this article, the terms "instantiate" and "instantiate" refer to the creation of an instance. "Instance" also refers to the concrete occurrence of an object, which may occur, for example, during the execution of program code.

[0040] The term "connection" can mean that two or more elements at a common communication protocol layer have an established signaling relationship with each other through a communication channel, link, interface, or reference point.

[0041] As used herein, the term "network element" refers to physical or virtualized equipment or infrastructure used to provide wired or wireless communication network services. The term "network element" may be considered synonymous with or referred to as networked computers, network hardware, network equipment, network nodes, virtualized network functions, etc.

[0042] The term "information element" refers to a structural element that contains one or more fields. The term "field" refers to the individual content of an information element, or the data element that contains that content. An information element may include one or more additional information elements.

[0043] Figure 1 A network environment 100 according to some implementation schemes is illustrated. Network environment 100 may include a UE 104 communicatively coupled to one or more base stations (e.g., base station 108 and base station 112). UE 104 and base stations 108 / 112 may communicate via air interfaces compatible with those 3GPP TS that define Long Term Evolution (LTE) and Fifth Generation (5G) New Radio (NR) system standards. Base stations 108 / 112 may be evolved Node Bs (eNBs) providing one or more Evolved Long Term Evolution (LTE) Evolution Universal Terrestrial Radio Access (E-UTRA) cells to provide E-UTRA user plane and control plane protocol termination to UE 104; or next-generation Node Bs (gNBs) providing one or more 5G New Radio (NR) cells to provide NR user plane and control plane protocol termination to UE 104.

[0044] Each of base stations 108 / 112 may use carrier aggregation (CA) deployment to provide one or more cells. In carrier aggregation, a base station may provide: a primary serving cell (PCell) for providing some or all of the control signaling via signaling radio bearers (SRB); and one or more secondary serving cells (SCells) for providing one or more data radio bearers (DRB) to increase the system's throughput capacity. PCells may be configured on primary component carriers (PCC) and SCells may be configured on secondary component carriers (SCC).

[0045] In some implementations, network environment 100 may support dual connectivity (DC) operation, where UE 104 may be configured to utilize radio resources provided by different schedulers located in different base stations 108 / 112. One of the base stations may be configured as a primary node (MN) to provide control plane connectivity to core network 116. The MN may be associated with a serving cell group referred to as a primary cell group (MCG), which includes PCells deployed in CA and optionally one or more SCells. Other base stations may be configured as secondary nodes (SNs), which may not have control plane connectivity to core network 116. The SN may be used to provide additional resources to UE 104. The SN may be associated with a serving cell group referred to as a secondary cell group (SCG), which includes primary cells (PSCells) deployed in CA and one or more SCells. The primary cells of the DC network (e.g., PCells and PSCells) may be referred to as special cells (SpCells).

[0046] NR networks can utilize Dynamic Spectrum Sharing (DSS), which allows LTE and NR to share the same carrier. The DSS framework allows NR cells to rate match around an LTE reference signal that would otherwise cause strong interference and impair spectral efficiency. Enhancements to the Physical Downlink Control Channel (PDCCH) used for cross-carrier scheduling can be considered to improve DSS operation. The PDCCH of an SCell can be used to schedule the PDSCH or PUSCH on a PCell or PSCell. When this is configured, the SCell can be referred to as a scheduled SCell (sScell). Further research may be needed to determine whether to specify the PDCCH of a PCell / PSCell / SCell for scheduling PDSCH on multiple cells using a single Downlink Control Information (DCI). In some scenarios, the number of cells that can be scheduled at one time may be limited to two. Minimizing the increase in the size of the DCI used to schedule PDSCH on multiple cells may be desirable.

[0047] In some cases, it can be assumed that UE 104 can monitor only the type 0 / 0A / 1 / 2 common search space (CSS) set on PCell / PSCell but not on sSCell (for the DCI format associated with those CSS sets). When cross-carrier scheduling from sSCell to PCell / PSCell is configured, UE 104 can be configured to monitor DCI format 0_1 / 1_1 / 0_2 / 1_2, which schedules PDSCH / PUSCH on PCell / PSCell, on the PCell / PSCell UE-specific search space (USS) set, or on the sSCell USS set.

[0048] Some implementations describe how to configure the USS set on PCell / PSCell and sSCell for cross-carrier scheduling on PCell / PSCell; whether and how to switch the configured search space set on PCell / PSCell and sSCell for PDCCH monitoring; and how to define PDCCH overrun when PDCCH candidates can be located on two component carriers.

[0049] The implementation describes various methods for configuring the sSCell and the USS search space set on the PCell / PSCell for the PCell / PSCell. Different types of search space sets for the PCell / PSCell can be defined depending on the component carriers it is configured to transmit on. For PCells / PSCells with self-scheduling operation, Type 1 USS can be configured on the PCell / PSCell. For PCells / PSCells with cross-carrier scheduling (CCS) operation, Type 2 USS can be configured on the sSCell.

[0050] Figure 2 Transmission resource 200 according to some embodiments is shown. Transmission resource 200 may include PCell (or PSCell) and sSCell.

[0051] PCell can include CSS204 and Type 1 USS. CSS204 can be used for broadcast messages or group-specific DCIs. For example, CSS204 can be used for paging messages, system information, random access responses, etc. Type 1 USS can be used to schedule PDSCH / PUSCH in PCell.

[0052] sSCell can include type 2 USS212 and USS216 for self-scheduling. Type 2 USS212 can be used to schedule PDSCH / PUSCH in PCell. USS 216 for self-scheduling can be used to schedule PDSCH / PUSCH in sSCell.

[0053] In some implementations, if all configurable parameters of a search space have the same Search Space Set (SSS) identifier (ID), they can be identical or duplicated between Type 1 USS and Type 2 USS. For example, if Type 1 USS 208 and Type 2 USS 212 have a common SSS-ID, they can be paired with each other and have the same configurable parameters. Configurable parameters that can be identical between paired SSSs may include, for example, the Control Resource Set (CORESET) index, duration, PDCCH blind decoding (BD) candidate number, DCI format used for monitoring, PDCCH monitoring periodicity and offset, and PDCCH monitoring span within a time slot. In some implementations, the BD number may be different for Type 1 USS and Type 2 USS associated with a common SSSID.

[0054] Providing Type 1 / Type 2 USS with publicly configurable parameters facilitates the detection / decoding of PDCCHs transmitted in these search spaces. For example, as... Figure 2 As shown, Type 1 USS 208 and Type 2 USS 212 can be configured with the same symbols. This makes the detection / decoding of PDCCH transmitted in the search space more efficient.

[0055] Providing Type 1 / Type 2 USS with common configurable parameters also facilitates the configuration of these search spaces. For example, it may be necessary to use Radio Resource Control (RRC) messages to explicitly configure only one of the Type 1 or Type 2 USS. The explicitly configured USS can be a Type 1 USS on a PCell / PSCell or a Type 2 USS on an sSCell. It may not be necessary to explicitly configure associated USS, as it can be configured through association. In some implementations, a one-bit tagging information element (IE) may be added to either the Type 1 or Type 2 USS to indicate the presence of associated USS of other types.

[0056] An exemplary abstract syntax representation (ANS.1) for configuring the search space by indicating the presence of associated USS can be shown below.

[0057]

[0058] This IE can exist in the PCell / PSCell configuration. The Type2-USS-Presence field can be used to indicate whether a Type 2 USS exists (true) or does not exist (false) on the SCell, thereby indicating the authorization or assignment for this PCell or PSCell.

[0059] In some implementations, the search space configuration may include only the PCell / PSCell field. This field may exist in the USS of the PCell / PSCell. If the USS is not a PCell / PSCell, it may not exist.

[0060] The search space configuration described above can be used to initially configure Type 1 USS on the PCell / PSCell and to indicate the presence of the associated Type 2 USS on the sSCell by setting the 1-bit flag Type2-USS-Presence to "true". Type 2 USS can then be configured based on the configuration parameters of Type 1 USS. In other implementations, the search space configuration can be used to first configure Type 2 USS and indicate the presence of Type 1 USS, which can then be configured via association.

[0061] Figure 3 Transmission resource 300 according to some embodiments is shown. In this embodiment, PCell may include a first set of parameters, while sSCell includes a second set of parameters. For example, PCell may include a 15kHz subcarrier spacing (SCS), while sSCell includes a 30kHz SCS. Therefore, the time slot of sSCell may be half the length of the time slot of PCell.

[0062] PCell can include CSS 304 and type 1 USS 308, and sSCell can include type 2 USS 312 and USS 316 for self-scheduling, similar to the above regarding... Figure 2 Those described. However, in order to maintain alignment between Type 1 USS and Type 2 USS, PCell may include an additional Type 1 USS 320 associated with Type 2 USS 324 in the second time slot of sSCell.

[0063] In some implementations, Type 1 USS and Type 2 USS for a given SSS-ID can be configured separately for PCell / PSCell. Figure 4 Transmission resources 400, configured separately as type 1 USS and type 2 USS according to some implementation schemes, are shown.

[0064] PCell can include CSS 404 and type 1 USS 408, and sSCell can include type 2 USS 412 and USS 416 for self-scheduling, similar to the above regarding... Figure 2 Those described. However, in this embodiment, Type 1 USS 408 and Type 2 USS 412, which can be associated with the same SSS-ID, can be configured separately, for example, by separate RRC signals. For example, separate configurations could include different time-domain configurations. Therefore, with Figure 2 Compared to the / 3 configuration Figure 4 Type 1 USS and Type 2 USS are not time-aligned.

[0065] The implementation plan provides different technologies for switching between Type 1 USS and Type 2 USS monitoring for PCell / PSCell.

[0066] In one implementation, either a Type 1 USS or a Type 2 USS may be hard-coded or explicitly configured by RRC signaling as the default USS for PDCCH monitoring. Under certain conditions, UE 104 may conditionally switch to monitor the other non-default USS. For example, UE 104 may only monitor the non-default USS when the symbol set is in a slot where the default USS is configured for uplink. In some implementations, the uplink slot may be provided in a tdd-UL-DL-ConfigurationCommon configuration or a tdd-UL-DL-ConfigurationDedicated configuration; or it may be provided by DCI format 2_0.

[0067] Figure 5Transmission resource 500, according to some embodiments, is illustrated for describing the switching between Type 1 USS and Type 2 USS monitoring. Transmission resource 500 includes six time slots, time slots 0-5. Time slots 0, 1, 4, and 5 of the sSCell can be configured for downlink, while time slots 2 and 3 of the sSCell can be configured for uplink. The sSCell can be configured with Type 2 USS and the PCell can be configured with Type 1 USS. In this embodiment, Type 2 USS can be the default USS. Therefore, UE 104 can monitor Type 2 USS in time slots 0, 1, 4, and 5. However, in time slots 2 and 3, UE 104 can switch to monitor a non-default USS (e.g., Type 1 USS).

[0068] In some implementations, the tag can be used to switch monitoring from a first USS type to a second USS type. The tag can be transmitted via DCI, as described below.

[0069] Figure 6 A transport resource 600 is illustrated according to some embodiments for describing a DCI-based handover between type 1 USS and type 2 USS monitoring. Transport resource 600 comprises six time slots, time slots 0-5. A sSCell may be configured with a type 2 USS and a PCell may be configured with a type 1 USS. In this embodiment, the type 2 USS may be the default USS (or an actively monitored USS). Therefore, UE 104 may begin monitoring the type 2 USS in time slots 0, 1, 4, and 5. In time slot 1, the DCI in the type 2 USS 604 may include an asserted handover flag. After detecting the asserted handover flag, UE 104 may switch from monitoring the type 2 USS to monitoring the type 1 USS in the PCell. In some embodiments, UE 104 may begin monitoring the USS being switched to in a first time slot, which is at least P_switch symbols after the last symbol of the PDCCH with a scheduling DCI (e.g., a DCI including a handover flag). Figure 6 As shown, UE 104 can receive the flag in slot 1 and begin switching to the USS in slot 2 for monitoring, but in other implementations, the switching may be delayed for other values.

[0070] In some implementations, UE 104 may continue to monitor the PDCCH on type 1 USS on PCell until it receives a handover flag of another assertion to switch back to monitoring type 2 USS on SCell.

[0071] In some implementations, the handover flag may be a new flag field added to the scheduling DCI format monitored in Type 1 / Type 2 USS. For example, if the flag field is set to "1" in the scheduling DCI format in the first USS type (e.g., Type 1 USS or Type 2 USS), then UE 104 may detect the handover flag as asserted and switch to monitoring the second USS type (e.g., Type 2 USS or Type 1 USS).

[0072] In some implementations, a timer may be introduced to facilitate the handover of USS monitoring. The timer can be used to provide an indication of when UE 104 will perform the initial handover. For example, UE 104 may start the timer when a handover flag is detected in a first USS type. The UE stops monitoring the PDCCH on the first USS type and begins monitoring the PDCCH on the second USS type in a first time slot, which is at least P_switch symbols after the timer expires.

[0073] In some implementations, a timer can be used to determine the duration for which the UE will monitor the USS type upon switching. For example, UE 104 may receive a handover flag in a first USS type. After switching to a second USS type, UE 104 may start a timer and monitor the second USS type while the timer is running. When the timer expires, UE 104 may switch back to monitoring the first USS type.

[0074] In some implementations, the switching flag may be indicated by a scrambling sequence [w_0, w_1, ..., w_23] used to scramble the cyclic redundancy check (CRC) bits of the scheduling DCI. Table 1 below shows the scrambling sequences that can be used to indicate the switching flag.

[0075] Codec-state [w_0,w_1,w_2,…,w_n-1] 0 [0,0,0,…,0] 1 [1,1,1,…,1]

[0076] Table 1

[0077] For example, if the CRC is scrambled by [0,0,0,…,0], the switching flag can be considered to be set to "0", for example, unassertified; and if the CRC is scrambled by [1,1,1,…,1], the switching flag can be considered to be set to "1", for example, asserted.

[0078] In some implementations, a new DCI format with a Private Radio Network Temporary Identifier (RNTI) value in the common search space of the PCell / PSCell can be used to indicate the selected USS type for PCell / PSCell scheduling via the following fields: USS type number 1, USS type number 2, ..., USS type number M. In some examples, a value "0" can be used to indicate type 1 USS and a value "1" can be used to indicate type 2 USS. The payload size of the new DCI format can be equal to the payload size of DCI format 1_0, including any padding bits attached to this new DCI format. UE 104 can be configured by a higher layer with field indexes to determine the index to the USS type for a given UE. In some designs, DCI format 2_6, typically used to notify power-saving information beyond the discontinuous reception (DRX) activity period, can be used during DRX activity time to indicate the selected USS type for PCell / PSCell scheduling.

[0079] Some implementations describe PDCCH monitoring operations relative to Type 1 USS and Type 2 USS, as follows.

[0080] In the first step, UE 104 can determine the maximum number of PDCCH BD candidates for PCell / PSCell and sSCell. And the non-overlapping control channel element (CCE) for each time slot. In some respects, PCell and sSCell can be counted as a single “virtual CC” to determine the CC BD and non-overlapping CCE budget.

[0081] If different SCS configurations are used for PCell / PSCell and sSCell, the minimum SES can be used to determine and The limit per CC.

[0082] In some aspects, scaling factors (e.g., α_1, α_2) can be introduced to be based on Determine each limit BD and CCE of PCell, where α1+α2≤1.

[0083] In the second step, UE 104 can determine the PDCCH monitoring for Type 1 USS and Type 2 USS. Consider M_CSS as the number of PDCCH BDs configured for CSS; M_type1 as the number of PDCCH BDs configured for Type 1 USS; M_type2 as the number of PDCCH BDs configured for Type 2 USS; and M_USS as the number of BDs available for both Type 1 USS and Type 2 USS without exceeding the limit, where...

[0084] In some implementations, PDCCH overruns may be disallowed for the following: PDCCH monitoring for SCell scheduling; or CSS on PCell / PSCell.

[0085] In one option, PDCCH overruns may not be allowed for Type 1 USS and Type 2 USS. Using this option, the configuration for Type 1 USS and Type 2 USS should meet the following conditions: M Type2 ≤M USS And M Type1 ≤(M USS -M Type1 ).

[0086] In the second option, PDCCH overruns are permitted for Type 1 USS and Type 2 USS. UE 104 may assume a PDCCH overrun has occurred if the following conditions are met relative to one or more of the following four options.

[0087] In the first option, if: M Type2 ≤M USS (Guaranteed by gNB via RRC configuration without exceeding limits) and M Type1 +M Type2 >M USS If this option is enabled, then PDCCH overruns can occur. This option typically disallows type 2 overruns, but allows total type 1 / type 2 overruns.

[0088] In the second option, if: M Type1 +r*M Type2 >M USS or r*M Type1 +M Type2 >M USS If r is a scaling factor greater than one, then PDCCH overrun can occur, and this can be predefined by 3GPP TS or reported as part of UE capability signaling.

[0089] In the third option, if r*(M) Type1 +M Type2 )>M USS If r is a scaling factor greater than one, then PDCCH overrun can occur, and this can be predefined by 3GPP TS or reported as part of UE capability signaling.

[0090] In the fourth option, if r*Max(M) Type1 M Type2 )>M USSIf this occurs, a PDCCH overrun may occur. In some implementations, the value R can be set to one. A fourth option can be used in implementations where UE 104 monitors only one type of USS (e.g., Type 1 USS or Type 2 USS) for a given time slot instead of both.

[0091] If an overlimit occurs, UE 104 can proceed to the third step.

[0092] In the third step, UE 104 may use one or more of the following three methods to determine the priority order for allocating PDCCH candidates to monitor up to the per CC BS limit for Type 1 / Type 2 USS. Non-overlapping CCE

[0093] In the first method, the priority order can be configured by RRC signaling as part of a Type 1 / Type 2 USS configuration.

[0094] In the second approach, the priority order can be predefined in the 3GPP TS. For example, if UE 104 is required to monitor both Type 2 and Type 1 USS, Type 2 can always be prioritized.

[0095] For both the first and second methods, the search space set with the lowest index can be prioritized over other search space sets within the USS type.

[0096] In the third method, the USS type between the actively monitored Type 1 USS and Type 2 USS is prioritized.

[0097] Figures 7 to 12 The determination of PDCCH candidates according to some implementation schemes is illustrated. In these implementation schemes, the following values ​​may be assumed: M CSS =8, as well as

[0098] Figure 7 Transmission resource 700 is shown, wherein CSS 704, Type 1 USS 708, and Type 1 USS 712 are in PCell, and Type 2 USS 716, Type 2 USS 720, and self-scheduled USS 724 are in sSCell. PDCCH candidates in virtual CC 728 can be counted against the BD / non-overlapping CCE budget of the PCell. In this embodiment, M CSS =8 from CSS 704, M Type1 =8 from Type 1 USS 708 and Type 1 USS 712, M Type2 =24 from type 2USS 716 and type 2USS 720.

[0099] The configuration of transport resources 700 for USS and CSS on PCell and sSCell can occur where PDCCH overruns are not allowed for CSS, Type 1 USS, and Type 2 USS. For example, in option 1, overruns only occur on M Type1 +M Type2 >M USS This only occurs at certain times. Regarding the above values, 8+24 is no greater than 32, and therefore no limit was exceeded. All BD candidates can be monitored by UE 104.

[0100] Figure 8 Transmission resource 800 is shown, where CSS 804, Type 1 USS 808, and Type 1 USS 812 are in PCell, and Type 2 USS 816, Type 2 USS 820, and self-scheduled USS 824 are in sSCell. PDCCH candidates in virtual CC 828 can be counted against the BD / non-overlapping CCE budget of the PCell. Compared to the previous diagram, the candidates on Type 1 USS 808 and Type 1 USS 812 are each increased to eight to improve scheduling flexibility. In this embodiment, M CSS =8 from CSS 804, M Type1 =16 from Type 1 USS 808 and Type 1 USS 812, M Type2 =24 from type 2USS 816 and type 2USS 820.

[0101] The configuration of transport resources 800 for USS and CSS on PCell and sSCell can occur if PDCCH overruns are allowed for Type 1 / Type 2 USS. For example, in Option 1, overruns occur in M... Type1 +M Type2 >M USS This occurs at certain times. Regarding the values ​​mentioned above, 16+24 is greater than 32, and therefore an overshoot does occur. If Type 2 USS has a higher priority than Type 1 USS, then UE 104 is allowed to discard Type 1 USS 812 and the UE can monitor the remaining BD candidates.

[0102] Figure 9 Transmission resource 900 is shown, where CSS 904, Type 1 USS 908, and Type 1 USS 912 are in PCell, and Type 2 USS 916, Type 2 USS 920, and self-scheduled USS 924 are in sSCell. PDCCH candidates in virtual CC 928 can be counted against the BD / non-overlapping CCE budget of the PCell. Compared to the previous diagram, the candidates on Type 1 USS 908 and Type 1 USS 912 are each reduced to two. In this embodiment, MCSS =8 from CSS 904, M Type1 =4 from type 1 USS 908 and type 1 USS 912, and M Type2 =24 from type 2USS 916 and type 2USS 920.

[0103] Considering the second clause of option 2 above and r=2 to determine PDCCH overlimit, then when r*M Type1 +M Type2 >M USS When this happens, an overlimit occurs. Regarding the above values, 2*4+24 is not greater than 32, and therefore an overlimit will not occur. All BD candidates can be monitored by UE 104.

[0104] Figure 10 Transmission resource 1000 is shown, where CSS 1004, Type 1 USS 1008, and Type 1 USS 1012 are in PCell, and Type 2 USS 1016, Type 2 USS 1020, and Self-Scheduled USS 1024 are in sSCell. PDCCH candidates in virtual CC 1028 can be counted against the BD / non-overlapping CCE budget of the PCell. Compared to the previous diagram, the candidates on Type 1 USS 1008 and Type 1 USS 1012 are each increased to four. In this embodiment, M... CSS =8 from CSS 1004, M Type1 =8 comes from type 1 USS 1008 and type 1 USS 1012, and M Type2 =24 from type 2USS 1016 and type 2USS 1020.

[0105] Reconsidering the second clause based on option 2 above and determining PDCCH overlimit with r=2, then when r*M Type1 +M Type2 >M USS When this happens, an over-limit occurs. Regarding the above values, 2*8+24 is greater than 32, and therefore an over-limit does indeed occur. If Type 2 USS has a higher priority than Type 1 USS, then UE 104 is allowed to discard Type 1 USS 1012 and the UE can monitor the remaining BD candidates.

[0106] Figure 11Transmission resource 1100 is shown, where CSS 1104, Type 1 USS 1108, and Type 1 USS 1112 are in PCell, and Type 2 USS 1116, Type 2 USS 1120, and self-scheduled USS 1124 are in sSCell. PDCCH candidates in virtual CC 1128 can be counted against the BD / non-overlapping CCE budget of the PCell. Compared to the previous diagram, the candidates on Type 2 USS 1116 and Type 2 USS 1120 are reduced to four and eight, respectively. In this embodiment, M CSS =8 from CSS1104, M Type1 =8 comes from type 1 USS 1108 and type 1 USS 1112, and M Type2 =12 from type 2USS 1116 and type 2USS 1120.

[0107] Considering the third option above and r=2 to determine PDCCH overlimit, then when r*(M Type1 +M Type2 )>M USS When this happens, an over-limit occurs. Regarding the values ​​above, 2*(8+12) is greater than 32, and therefore an over-limit does indeed occur. If Type 2 USS has a higher priority than Type 1 USS, UE 104 is allowed to discard Type 1 USS 1112 and the UE can monitor the remaining BD candidates. After discarding Type 1 USS 1112, over-limits will no longer occur, for example, 2*(4+12) will not be greater than 32.

[0108] Figure 12 Transmission resource 1200 is shown, where CSS 1204, Type 1 USS 1208, and Type 1 USS 1212 are in PCell, and Type 2 USS 1216, Type 2 USS 1220, and self-scheduled USS 1224 are in sSCell. PDCCH candidates in virtual CC 1228 can be counted against the BD / non-overlapping CCE budget of the PCell. Compared to the previous diagram, the candidates on Type 1 USS 1208 and Type 1 USS 1212 are increased to eight, the candidates on Type 2 USS 1216 are increased to 16, and the candidates on Type 2 USS 1220 are increased to eight. In this embodiment, M CSS =8 from CSS 1204, M Type1 =16 comes from type 1 USS 1208 and type 1 USS 1212, and M Type2 =24 from type 2USS 1216 and type 2USS 1220.

[0109] Considering the fourth option above and r=1 to determine PDCCH overlimit, then when r*Max(M Type1 M Type2 )>M USS When this happens, an over-limit occurs. Regarding the values ​​mentioned above, 1*max(16,24) is no greater than 32, and therefore an over-limit will not occur. All BD candidates can be monitored by UE 104. As can be seen, compared to other options, this option allows for a larger BD / CCE at the base station, but can also be a more stringent burden at the UE.

[0110] The implementation plan also describes the transmission of reference signals in wireless communication.

[0111] When NR operation is extended to higher frequencies (e.g., up to 71 GHz) and includes higher frequency SCS (e.g., 480 kHz SCS and 960 kHz SCS), reference signal enhancement may be required.

[0112] Figure 13 Transmission resource 1300 is illustrated, wherein comb-based resource element (RE) mapping is used for demodulation reference signals (DMRS) associated with different antenna ports of configuration 1. In addition to further reducing DMRS overhead, this allows code division multiplexing (CDM) of the antenna ports in both the frequency domain (e.g., frequency domain (FD)-CDM) and the time domain (e.g., TD-CDM), such as... Figure 13 As shown.

[0113] For example, FD-CDM group 1 can map two DMRS sequences on two REs. The first two REs of FD-CDM group 1 can include DMRS sequences associated with two antenna ports AP0 and AP1. A first orthogonal coverage code (OCC) (e.g., <1,1>) can be applied to the DMRS sequence for AP0, and a second OCC (e.g., <1,-1>) can be applied to the DMRS sequence for AP1. The first two REs of FD-CDM group 2 can include DMRS sequences associated with two additional antenna ports AP2 and AP3. A first OCC can be applied to the DMRS sequence for AP2, and a second OCC can be applied to the DMRS sequence for AP3. The first / second OCC can be reused given the interval between the first and second REs in the frequency domain.

[0114] Above 52.6 GHz, channels with significant temporal dispersion (e.g., large delay spread) can stand out in frequency selectivity and lead to orthogonality loss between FD OCCs used at different layers, such as in rank-2 transmissions. Poor interpolation and orthogonality loss between the two ports of the FD-CDM can degrade the performance of practical channel estimation.

[0115] The implementation scheme describes enhancements to the DMRS mode to improve channel estimation and avoid unnecessary UE complexity. Some implementation schemes describe maintaining the same maximum number of layers to improve resource spectral efficiency. This is particularly beneficial for system designs above 52.6 GHz.

[0116] Several approaches can be considered for DMRS resource mapping associated with PDSCH / PUSCH or CSI-RS transmissions to mitigate performance loss caused by orthogonality loss between FD OCCs used for different ports.

[0117] In the first option, FD-CDM can be disabled for a predefined subcarrier spacing configuration set. This predefined subcarrier spacing configuration set can be defined in the 3GPP TS. For example, in some implementations, the subcarrier spacing configuration set for which FD-CDM is disabled may include configurations with a 480kHz SCS or a 960kHz SCS.

[0118] In the second option, FD-CDM for a given SCS (e.g., 480kHz SCS) can be controlled and semi-statically disabled by using a new IE in system information (e.g., System Information Block 1 (SIB-1)) or dedicated RRC signaling for a given UE. This allows the base station to enable / disable FD-CDM for DMRS based on UE-specific channel characteristics (e.g., delay spread curve).

[0119] In the third option, a new MAC CE can be introduced to disable / enable FD-CDM corresponding to a given SCS group on a per-UE basis. The MAC CE can be identified by a MAC sub-header with a dedicated logical channel ID (LCID).

[0120] Figure 14 A MAC CE 1400, which can be used to disable / enable FD-CDM according to some embodiments, is illustrated. The MAC CE 1400 may include an S_i field indicating whether FD-CDM is enabled or disabled for a DMRS / CSI-RS with parameter set index i. The S_i field can be set to "1" to indicate that FD-CDM is enabled for a DMRS / CSI-RS with the corresponding SCS i. The S_i field can be set to "0" to indicate that FD-CDM is disabled for a DMRS / CSI-RS with the corresponding SCS i. In one embodiment, the 480 kHz SCS can be configured as SCS 0, and the 960 kHz SCS can be configured as SCS 1. Reserved bits (R) of the MAC CE 1500 can be set to "0".

[0121] In the fourth option, FD-CDM can be enabled or disabled for DMRS RE mapping using the scheduled DCI format. This allows the base station to enable / disable FD-CDM for DMRS based on the actual modulation and coding scheme (MCS) of the scheduled PDSCH. As an example, for higher MCS levels, FD-CDM can be disabled to avoid performance loss. For lower MCS levels, FD-CDM can be enabled to improve system spectral efficiency.

[0122] Figure 15 Two exemplary DCIs, according to some implementation schemes, are shown that can be used to indicate whether FD-CDM is enabled or disabled.

[0123] DCI 1504 may include a new field, namely FD-CDM indicator 1508, which is added to the existing DCI fields 1512 and CRC 1516. FD-CDM indicator 1508 can be used to dynamically enable / disable FD-CDM for DMRS mapping. FD-CDM indicator 1508 may include a single bit. In some implementations, this value may be set to "1" to indicate that FD-CDM is disabled, which may also imply that other UEs are not co-scheduled in the same CDM group.

[0124] DCI 1520 may include the existing DCI field 1524 and CRC 1528, but may not include the FD-CDM indicator field. Instead, DCI 1520 can provide an FD-CDM indicator by selecting a scrambling sequence [w_0, w_1, w_2, ... w_23] for scrambling bits in CRC 1528. In some embodiments, the selection of the scrambling sequence may convey 1-bit enable / disable information, as shown in Table 2.

[0125] 1-bit FD-CDM indicator [w_0,w_1,w_2,…w_23] 0 [0,0,0,…,0] 1 [1,1,1,…,1]

[0126] Table 2

[0127] To accommodate the dynamic enabling / disabling of FD-CDM, some implementations provide enhancements to the DMRS AP signaling. For example, new AP tables can be defined for the “Antenna Port” field in DCI formats 1_1 and 1_2 to reduce signaling overhead when FD-CDM is disabled on the DMRS port for PDSCH / PUSCH. Specifically, Tables 3 and 4 have been developed to more effectively signal the DMRS AP when FD-CDM is disabled.

[0128] Table 3 shows a two-bit table (e.g., two bits for providing one of four values) for antenna ports with DMRS type 1 (1000+ DMRS ports) and a maximum length of one (e.g., DMRS sequence transmitted by one symbol).

[0129]

[0130] Table 3

[0131] Table 4 shows a four-bit table (e.g., four bits for providing one of 12 values, where four values ​​are reserved) for antenna ports with DMRS type 1 (1000+ DMRS ports) and maximum length two (e.g., DRMS ​​sequences are transmitted by two symbols).

[0132]

[0133] Table 4

[0134] When developing Tables 3 and 4, the lowest DMRS port within a DMRS group is defined as the front port. Within a CDM group, ports other than the front port can be used when the front port is used. For example, port 0 can be the front port of CDM group 0. Correspondingly, the indication "port 1" is not supported in the rank-1 length 1 DMRS mode, as shown in Table 3.

[0135] If UE 104 receives a DCI for rank 1 length 1 DMRS mode with an AP field value set to 2 (e.g.,

[10] bit value), it can refer to Table 3 to determine that the base station will use DMRS port 2 to schedule data.

[0136] Disabling FD-CDM within the same CDM group for larger SCSs can degrade peak data rate performance because up to two layers are supported for single-symbol DMRS and up to four layers for dual-symbol DMRS. To address this, the following options can be considered.

[0137] In the first option, a new DMRS mode for configuring type 1 DMRS can be used, such that the DMRS sequence associated with a single DMRS port is mapped to consecutive REs in the frequency domain (k,l)_p,u according to the following equation:

[0138] k = 4n + k' + Δ, where k' = 0, 1; n = 0, 1, ...; and Δ = 0, 1.

[0139] In the second option, the DMRS sequence can be mapped to the resource element (k,l)_p,u across paired DMRS timings, which can be represented as shown in the figure. Figure 16 The transmission resource 1600 is indexed according to some implementation schemes and by i = 0, 1 according to the following equation:

[0140] k = (4n + k' + Δ) mod 12, where

[0141]

[0142] n = 0, 1, ..., and

[0143]

[0144] Table 5 shows the OCC(ω) t (l′)) can be applied to different antenna ports (p) and CDM groups.

[0145]

[0146]

[0147] Table 5

[0148] As described in the second option, mapping DMRS sequences to REs can support data transmission up to eight layers.

[0149] R represents the layer number of PDSCH / PUSCH, and the position of the double-symbol DMRS timing in the DMRS timing pair can be determined based on one of the following three options.

[0150] In the first option, only when the data duration is l for PDSCH mapping type A. d >9 and for PDSCH mapping type A, data duration l d PDSCH / PUSCH with R>4 is allowed only when R>7, as shown in Table 6 below.

[0151] <![CDATA[Symbol l d > PDSCH mapping type A PDSCH mapping type B 8 - <![CDATA[l0,5]]> 9 - <![CDATA[l0,5]]> 10 <![CDATA[l0,8]]> <![CDATA[l0,7]]> 11 <![CDATA[l0,8]]> <![CDATA[l0,7]]> 12 <![CDATA[l0,8]]> <![CDATA[l0,8]]> 13 <![CDATA[l0,10]]> <![CDATA[l0,8]]> 14 <![CDATA[l0,10]]> -

[0152] Table 6

[0153] When targeting PDSCH mapping type A, data duration l d >9 or for PDSCH mapping type A, data duration l d When >7 occurs, UE 104 may assume that the DMRS timing pair is used for PDSCH / PUSCH. (By...) The first DMRS symbol representing DMRS timing i is provided in Table 6 for PDSCH mapping types A / B. The value of .

[0154] Figure 17 A transmission resource 1700 with a DMRS pair 1704 is shown according to some embodiments. Specifically, transmission resource 1700 is shown for a pair with l d DMRS position of PDSCH mapping type B = 8 Using this design, the timing of the paired dual-symbol DMRS is synchronized with the first symbol. Transmit together. Figure 16 The patterns in the data can be used for DMRS pairs.

[0155] A second option for determining the position of a double-symbol DMRS timing in a DMRS timing pair is as follows. When R>4 is detected in the DCI format, UE 104 may assume that DMRS timings entering consecutive PDSCHs or PUSCH timings scheduled by a single DCI format are aggregated together to form a DMRS timing pair.

[0156] Figure 18 Transport resources 1800 with DMRS pairings that aggregate across consecutive PDSCH timings to support high-rank PDSCH transport are illustrated according to some embodiments. In this embodiment, the DCI can schedule two consecutive PDSCHs, namely PDSCH 1804 and PDSCH 1808.

[0157] Transport resource 1800 provides support for an R>4 example for multi-PDSCH scheduling by utilizing a double-symbol preload DMRS in two consecutive PDSCH transports 1804 and 1808. Note that in some implementations, Figure 16 The frequency-shift DMRS mode described herein can be used in DMRS pairs in PDSCH 1804 and 1808.

[0158] For example, when there are additional DMRS timings in a single PDSCH transmission within multiple PDSCHs, the DMRS timing pair can be determined as described above relative to... Figure 18 The DMRS timing is formed within a single PDSCH transmission as described.

[0159] A third option for determining the location of the two-symbol DMRS timing in a DMRS timing pair can increase the number of preceding DMRS. For example, the number of preceding DMRS can be increased to B symbols, where B>2, to enable R>4 transmission. In some implementations, for a 480kHz SCS and a 960kHz SCS, B=4 instead of 2, as described above relative to... Figure 18 As shown.

[0160] Figure 19 An operational flow / algorithm structure 1900 according to some embodiments is shown. The operational flow / algorithm structure 1900 may be executed or implemented by a base station (e.g., base station 108, 112 or 2300); or by a component thereof such as a baseband processor 2304A.

[0161] Operation flow / algorithm structure 1900 may include, at 1904, configuring a first type USS on the PCell / PSCell. The first type USS may be a type 1 USS, which can be used to transmit and schedule the PUSCH or PDSCH PDCCH on the PCell / PSCell.

[0162] The operation flow / algorithm structure 1900 may also include, at 1908, configuring a second type USS on the sSCell. The second type USS may be a type 2 USS, which can be used to transmit the PDCCH of the PUSCH or PDSCH on the PCell / PSCell. The base station can configure a first type USS and a second type USS sharing the same SSS-ID with the same configuration parameters. These same parameters may include the CORESET index, duration, PDCCH BD candidate, DCI format used for monitoring, PDCCH monitoring periodicity and offset, or PDCCH monitoring span within a time slot. In some implementations, configuring the same parameters for the first type USS and the second type USS allows the USS to be perfectly aligned in the time domain.

[0163] In some implementations, the base station can configure the first type USS and the second type USS by explicitly configuring the first in the first / second type USS and by associating the second in the first / second type USS. For example, in configuring the first in the first / second type USS, the base station can provide an indication of associating the first with the second in the first / second type USS. This can be accomplished by including an appropriate type of USS presence marker in the configuration signaling.

[0164] Figure 20 An operational flow / algorithm structure 2000 according to some embodiments is shown. The operational flow / algorithm structure 2000 may be executed or implemented by a UE (e.g., UE 104 or 2200); or by components thereof such as baseband processor circuitry 2204A.

[0165] The operation flow / algorithm structure 2000 may include, at 2004, determining the maximum number of BD candidates for PCell or PScell. This value can be given as... As discussed above.

[0166] The operation procedure / algorithm structure 2000 may also include, at point 2008, determining the number of BD candidates to be monitored for Type 1 USS and Type 2 USS. The number of BD candidates to be monitored for Type 1 USS and Type 2 USS can be considered as the number of BD candidates to be monitored for virtual carrier components, which include a portion of the primary component carrier where Type 1 USS is located and a portion of the secondary component carrier where Type 2 USS is located.

[0167] The operation flow / algorithm structure 2000 may further include: at 2012, determining whether an over-limit has occurred. The UE may determine whether an over-limit has occurred based on the maximum number of BD candidates for the PCell / PSCell and the number of PDCCH BD candidates to be monitored for both Type 1 USS and Type 2 USS. In some implementations, the UE may first determine the maximum number of BD candidates that can be monitored for the USS on the virtual component carrier. This may be the maximum number of BD candidates for the PCell / PSCell minus the number of BD candidates to be monitored for the CSS. Then, the UE may compare the number of BD candidates to be monitored for both Type 1 USS and Type 2 USS with the maximum number of BD candidates that can be monitored for the USS. In some implementations, such as those described above with respect to the second, third, and fourth options for determining whether a PDCCH over-limit has occurred, a scaling factor may be applied to the maximum of the number of BD candidates to be monitored for Type 1 USS; the number of BD candidates to be monitored for Type 2 USS; the number of BD candidates to be monitored for both Type 1 USS and Type 2 USS; or the maximum of the number of BD candidates for either Type 1 USS or Type 2 USS.

[0168] In some implementations, the maximum number of BD candidates that can be monitored for a USS on a virtual component carrier can be determined based on a value derived from the sum of the maximum number of BD candidates for the PCell / PSCell multiplied by a first scaling factor and the maximum number of BD candidates for the SCell multiplied by a second scaling factor, wherein the sum of the first and second scaling factors is less than or equal to one. For example, the maximum number of BD candidates that can be monitored for a Type 1 / Type 2 USS can then be equal to that value minus the number of BD candidates to be monitored for a CSS on the PCell / PSCell.

[0169] If an overlimit is detected at 2012, the operation flow / algorithm structure 2000 can proceed to 2016 to select PDCCH BD candidates from a subset of Type 1 and Type 2 USSs for monitoring based on priority rules. Priority rules can be configured by RRC signaling as part of the search space configuration, or they can be predefined in the 3GPP TS. In some implementations, the USS being actively monitored can be a prioritized USS. Within a specific USS type, the search space set can be prioritized based on its index, where lower indices are associated with higher priorities. When an overlimit occurs, the UE can exclude BD candidates from the many lowest-priority USS required to prevent the overlimit situation.

[0170] If it is determined at 2012 that no limit is exceeded, the operation process / algorithm structure 2000 can proceed to 2020 to select PDCCH BD candidates from all types 1 USS and type 2 USS for monitoring.

[0171] After 2016 or 2020, the operational process / algorithm structure can be advanced to monitor the selected PDCCH BD candidate.

[0172] Figure 21 An operational flow / algorithm structure 2100 according to some embodiments is shown. The operational flow / algorithm structure 2100 may be executed or implemented by a base station (e.g., base station 108, 112 or 2300); or by components thereof such as baseband processor 2304A.

[0173] The operation flow / algorithm structure 2100 may include, at 2104, identifying the SCS used for reference signal transmission. The SCS may be a 120kHz SCS, a 480kHz SCS, a 960kHz SCS, or some other SCS.

[0174] The operation procedure / algorithm structure 2100 may also include, at 2108, determining whether to enable FD-CDM for the identified SCS. FD-CDM can be disabled for higher SCS configurations (e.g., 480kHz SCS or 960kHz CS or based on channel conditions).

[0175] The operation flow / algorithm structure 2100 may also include, at 2112, mapping the reference signal to the resource element based on whether FD-CDM is enabled for the identified SCS. The mapping from the reference signal to the resource element can be similar to the above description relative to... Figures 16 to 19 The mapping described.

[0176] The operation process / algorithm structure 2100 may also include: at 2116, transmitting a reference signal.

[0177] In some implementations, the base station may provide the UE with an indication of whether FD-CDM is enabled for the SCS. This can be done through scheduling (or some other) DCI, system information, RRC signaling, MAC CE, or some combination thereof.

[0178] Figure 22 A UE 2200 according to some implementation schemes is shown. The UE 2200 may be similar to... Figure 1 The UE 104 is essentially interchangeable with it.

[0179] The UE 2200 can be any mobile or non-mobile computing device, such as mobile phones, computers, tablets, industrial wireless sensors (e.g., microphones, carbon dioxide sensors, pressure sensors, humidity sensors, thermometers, motion sensors, accelerometers, laser scanners, fluid level sensors, stock sensors, voltmeters / ammeters, actuators, etc.), video surveillance / monitoring devices (e.g., cameras, camcorders, etc.), wearable devices (e.g., smartwatches), and Internet of Things (IoT) devices.

[0180] UE 2200 may include a processor 2204, RF interface circuitry 2208, memory / storage device 2212, user interface 2216, sensor 2220, drive circuitry 2222, power management integrated circuit (PMIC) 2224, antenna 2226, and battery 2228. Components of UE 2200 may be implemented as integrated circuits (ICs), portions of integrated circuits, discrete electronic devices or other modules, logic components, hardware, software, firmware, or combinations thereof. Figure 22 The block diagram is intended to show a high-level view of some of the components of the UE 2200. However, some of the components shown may be omitted, additional components may be present, and different arrangements of the components shown may occur in other specific implementations.

[0181] The components of UE 2200 can be coupled to various other components via one or more interconnects 2232, which can represent any type of interface, input / output, bus (local, system, or extension), transmission line, trace, optical connector, etc., allowing various circuit components (on common or different chips or chipsets) to interact with each other.

[0182] Processor 2204 may include processor circuitry such as baseband processor circuitry (BB) 2204A, central processing unit circuitry (CPU) 2204B, and graphics processing unit circuitry (GPU) 2204C. Processor 2204 may include any type of circuitry or processor circuitry that executes or otherwise operates computer-executable instructions (such as program code, software modules, or functional processes from memory / storage device 2212) to cause UE 2200 to perform the operations described herein.

[0183] In some implementations, the baseband processor circuit 2204A can access the communication protocol stack 2236 in the memory / storage device 2212 to communicate over a 3GPP-compliant network. Generally, the baseband processor circuit 2204A can access the communication protocol stack to perform the following operations: user plane functions at the PHY, MAC, RLC, PDCP, SDAP, and PDU layers; and control plane functions at the PHY, MAC, RLC, PDCP, RRC, and non-access layers. In some implementations, PHY layer operations may additionally / optionally be performed by components of the RF interface circuit 2208.

[0184] The baseband processor circuit 2204A can generate or process baseband signals or waveforms carrying information in a 3GPP-compliant network. In some implementations, the waveforms used for NR can be based on cyclic prefix OFDM (CP-OFDM) in the uplink or downlink, and Discrete Fourier Transform Extended OFDM (DFT-S-OFDM) in the uplink.

[0185] Memory / storage device 2212 may include one or more non-transitory computer-readable media, including instructions (e.g., communication protocol stack 2236) that can be executed by one or more processors in processor 2204 to cause UE 2200 to perform the various operations described herein. Memory / storage device 2212 includes any type of volatile or non-volatile memory that can be distributed throughout UE 2200. In some embodiments, some memory / storage devices in memory / storage device 2212 may be located on processor 2204 itself (e.g., L1 cache and L2 cache), while other memory / storage devices 2212 may be located external to processor 2204 but accessible via a memory interface. Memory / storage device 2212 may include any suitable volatile or non-volatile memory, such as, but not limited to, dynamic random access memory (DRAM), static random access memory (SRAM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), flash memory, solid-state memory, or any other type of memory device technology.

[0186] RF interface circuitry 2208 may include transceiver circuitry and a radio frequency front-end module (RFEM), which allows UE 2200 to communicate with other devices via a radio access network. RF interface circuitry 2208 may include various components arranged in the transmit or receive path. These components may include, for example, switches, mixers, amplifiers, filters, synthesizer circuitry, control circuitry, etc.

[0187] In the receiving path, the RFEM can receive the radiated signal from the air interface via antenna 2226 and continue to filter and amplify the signal (using a low-noise amplifier). This signal can be provided to the receiver of the transceiver, which downconverts the RF signal into a baseband signal that is provided to the baseband processor of processor 2204.

[0188] In the transmission path, the transceiver's transmitter upconverts the baseband signal received from the baseband processor and provides the RF signal to the RFEM. The RFEM amplifies the RF signal using a power amplifier before it is radiated across the air interface via antenna 2226.

[0189] In various implementations, the RF interface circuit 2208 can be configured to transmit / receive signals in a manner compatible with NR access technology.

[0190] Antenna 2226 may include antenna elements to convert electrical signals into radio waves for propagation through the air and to convert received radio waves back into electrical signals. These antenna elements may be arranged in one or more antenna panels. Antenna 2226 may have omnidirectional, directional, or combinations thereof antenna panels to enable beamforming and multiple-input / multiple-output communication. Antenna 2226 may include microstrip antennas, printed antennas fabricated on the surface of one or more printed circuit boards, patch antennas, phased array antennas, etc. Antenna 2226 may have one or more panels designed for a specific frequency band included in FR1 or FR2.

[0191] User interface 2216 includes various input / output (I / O) devices designed to enable users to interact with UE 2200. User interface 2216 includes input device circuitry and output device circuitry. Input device circuitry includes any physical or virtual means for accepting input, particularly including one or more physical or virtual buttons (e.g., a reset button), a physical keyboard, a keypad, a mouse, a touchpad, a touchscreen, a microphone, a scanner, a headset, etc. Output device circuitry includes any physical or virtual means for displaying information or otherwise conveying information (such as sensor readings, actuator positions, or other similar information). Output device circuitry may include any number or combination of audio or visual displays, particularly including one or more simple visual outputs / indicators (e.g., binary status indicators such as LEDs and multi-character visual outputs), or more complex outputs such as display devices or touchscreens (e.g., liquid crystal displays (LCDs), LED displays, quantum dot displays, projectors, etc.), wherein the output of characters, graphics, multimedia objects, etc., is generated or produced by the operation of UE 2200.

[0192] Sensor 2220 may include devices, modules, or subsystems designed to detect events or changes in their environment and transmit information about the detected events (sensor data) to other devices, modules, subsystems, etc. Examples of such sensors include, in particular: inertial measurement units including accelerometers, gyroscopes, or magnetometers; microelectromechanical systems (MEMS) or nanoelectromechanical systems (NEMS) including triaxial accelerometers, triaxial gyroscopes, or magnetometers; level sensors; flow sensors; temperature sensors (e.g., thermistors); pressure sensors; barometric pressure sensors; gravimeters; altimeters; image capture devices (e.g., cameras or lensless aperture sensors); light detection and ranging sensors; proximity sensors (e.g., infrared radiation detectors, etc.); depth sensors; ambient light sensors; ultrasonic transceivers; microphones or other similar audio capture devices; etc.

[0193] The driving circuitry 2222 may include software and hardware elements for controlling specific devices embedded in, attached to, or otherwise communicatively coupled to the UE 2200. The driving circuitry 2222 may include various drivers that allow other components to interact with or control various input / output (I / O) devices that may exist within or be connected to the UE 2200. For example, the driving circuitry 2222 may include: a display driver for controlling and allowing access to a display device; a touchscreen driver for controlling and allowing access to a touchscreen interface; a sensor driver for acquiring sensor readings of the sensor 2220 and controlling and allowing access to the sensor 2220; a driver for acquiring actuator positions of electromechanical components or controlling and allowing access to electromechanical components; a camera driver for controlling and allowing access to an embedded image capture device; and an audio driver for controlling and allowing access to one or more audio devices.

[0194] The PMIC 2224 manages the power supplied to various components of the UE 2200. Specifically, relative to the processor 2204, the PMIC 2224 controls power selection, voltage scaling, battery charging, or DC-DC conversion.

[0195] In some implementations, the PMIC 2224 may control or otherwise become part of various power-saving mechanisms of the UE 2200, including DRX, as discussed herein.

[0196] Battery 2228 can power UE 2200, but in some examples, UE 2200 may be mounted in a fixed location and may have a power source coupled to the mains. Battery 2228 may be a lithium-ion battery, a metal-air battery such as a zinc-air battery, an aluminum-air battery, a lithium-air battery, etc. In some specific implementations, such as in vehicle-based applications, battery 2228 may be a typical lead-acid automotive battery.

[0197] Figure 23 Base station 2300 according to some embodiments is shown. Base station 2300 may be similar to Figure 1 The base stations are 108 or 112, and are basically interchangeable with them.

[0198] Base station 2300 may include processor 2304, RF interface circuit 2308, core network (CN) interface circuit 2312, memory / storage device circuit 2316 and antenna structure 2326.

[0199] The components of base station 2300 can be coupled to various other components via one or more interconnects 2328.

[0200] The processor 2304, RF interface circuit 2308, memory / storage device circuit 2316 (including communication protocol stack 2310), antenna structure 2326, and interconnect 2328 can be similar to those in the reference. Figure 10 Similar named elements are shown and described.

[0201] The CN interface circuit 2312 can provide connectivity to a core network (e.g., a 5th generation core network (5GC) using a 5GC-compatible network interface protocol (such as Carrier Ethernet) or some other suitable protocol). Network connectivity can be provided to / from base station 2300 via fiber optic or wireless backhaul. The CN interface circuit 2312 may include one or more dedicated processors or FPGAs for communicating using one or more of the aforementioned protocols. In some implementations, the CN interface circuit 2312 may include multiple controllers for providing connectivity to other networks using the same or different protocols.

[0202] In some implementations, base station 2300 may be coupled to transmit-receive point (TRP) using antenna structure 2326, CN interface circuit, or other interface circuit.

[0203] As is widely recognized, the use of personally identifiable information should comply with privacy policies and practices that are generally accepted to meet or exceed industry or governmental requirements for protecting user privacy. Specifically, personally identifiable information data should be managed and processed to minimize the risk of unintentional or unauthorized access or use, and the nature of authorized use should be clearly explained to users.

[0204] For one or more embodiments, at least one of the components shown in one or more of the foregoing figures may be configured to perform one or more operations, techniques, processes, or methods as described in the Examples section below. For example, the baseband circuitry described above in conjunction with one or more of the foregoing figures may be configured to operate according to one or more of the examples below. Similarly, circuitry associated with the UE, base station, network element, etc., described above in conjunction with one or more of the foregoing figures may be configured to operate according to one or more of the examples shown in the Examples section below.

[0205] Example

[0206] Further exemplary implementations are provided in the following sections.

[0207] Example 1 includes a method for operating a base station, the method comprising: configuring a first type of User Equipment (UE) Specific Search Space (USS) on a primary serving cell (PCell) or a primary secondary cell (PSCell) for scheduling data in the PCell or PSCell; and configuring a second type of USS on a scheduling secondary cell (sSCell) for scheduling data in the PCell or PSCell, wherein the first type of USS and the second type of USS are configured with the same Search Space Set (SSS) identifier (ID) and the same configuration parameters.

[0208] Example 2 includes the method according to Example 1 or some other example herein, wherein the same configuration parameters include physical downlink control channel (PDCCH) monitoring periodicity and offset or PDCCH monitoring span within a time slot.

[0209] Example 3 includes the method according to Example 1 or some other embodiment herein, wherein the same configuration parameters make the timing of monitoring for the first type of USS and the second type of USS perfectly aligned in the time domain.

[0210] Example 4 includes the method according to Example 1 or some other embodiment herein, wherein configuring the first type USS and the second type USS includes: transmitting a radio resource control (RRC) signal to a user equipment (UE) to configure the first of the first type USS or the second type USS, wherein the RRC signal includes a marker for indicating the presence of a second associated with the first of the first type USS or the second type USS.

[0211] Example 5 includes a method for operating a user equipment (UE), the method comprising: receiving configuration information to configure a first UE-specific search space (USS), the first USS being a first of the following: a first type USS configured on a primary serving cell (PCell) or a primary secondary cell (PSCell) for scheduling data in the PCell or PSCell; or a second type USS configured on a secondary cell (sSCell) for scheduling data in the PCell or PSCell; and determining, based on the configuration information, the configuration of a second USS being a second of the first type USS or the second type USS.

[0212] Example 6 includes the method according to Example 5 or some other embodiment herein, wherein the configuration information includes a marker for indicating the presence of the second USS.

[0213] Example 7 includes the method according to Example 5 or some other embodiment herein, wherein the first USS is a default USS and the second USS is a non-default USS, and the method further includes: determining whether a triggering condition exists; if the triggering condition does not exist, monitoring the default USS for downlink control information; and if the triggering condition exists, monitoring the non-default USS for downlink control information.

[0214] Example 8 includes the method according to Example 7 or some other embodiment of this document, and further includes: determining that the triggering condition exists when the default USS is in an uplink time slot.

[0215] Example 9 includes the method according to Example 7 or some other embodiment herein, further comprising: detecting a Physical Downlink Control Channel (PDCCH) transmission in the default USS of the first time slot, the PDCCH transmission including a marker; and determining, based on the marker, that one or more symbols following the last symbol of the PDCCH transmission exist, the triggering condition.

[0216] Example 10 includes the method according to Example 9 or some other embodiment herein, wherein the PDCCH transmission includes downlink control information (DCI), and the marker is: a sequence for scrambling cyclic redundancy check (CRC) bits of the DCI; or one or more bits in a field of the DCI.

[0217] Example 11 includes the method according to Example 7 or some other embodiment of this document, further comprising: determining that the triggering condition exists; setting a timer based on the determination that the triggering condition exists; and determining that the triggering condition no longer exists when the timer expires.

[0218] Example 12 includes the method according to Example 7 or some other embodiment herein, further comprising: detecting downlink control information (DCI) in a public search space, the DCI including a tag; and determining, based on the tag, that the triggering condition exists.

[0219] Example 13 includes the method according to Example 12 or some other embodiment herein, further comprising: receiving an indication of a field index via Radio Resource Control (RRC) or Medium Access Control (MAC) signaling; and detecting the tag in the DCI based on the field index.

[0220] Example 14 includes the method according to Example 12 or some other embodiment herein, wherein the DCI includes DCI format 2_6 received during discontinuous reception (DRX) activity time.

[0221] Example 15 includes a method for operating a user equipment (UE), the method comprising: determining a maximum number of blind decoding (BD) candidates for a primary serving cell (PCell) or a primary / secondary serving cell (PSCell); determining a number of physical downlink control channel (PDCCH) BD candidates to be monitored for a type 1 UE-specific search space (USS) and a type 2 USS, wherein the type 1 USS is configured on a scheduling secondary cell (sSCell) for scheduling data in the PCell or PSCell, and the type 2 USS is configured on the PCell or PSCell for scheduling data in the PCell or PSCell; and determining whether an over-limit has occurred based on the maximum number of BD candidates and the number of PDCCH BD candidates to be monitored for the type 1 USS and the type 2 USS.

[0222] Example 16 includes the method according to Example 15 or some other embodiment herein, wherein the PCell or the PSCell is configured with a first subcarrier spacing (SCS), the sSCell is configured with a second subcarrier spacing (SCS), and the method further includes: determining the maximum number of BD candidates based on the lower of the first SCS and the second SCS.

[0223] Example 17 includes the method according to Example 15 or some other embodiment herein, wherein the maximum number is a first maximum number and the method further includes: determining a second maximum number of BD candidates for the sSCell; and determining a third maximum number of BD candidates for the virtual component carrier based on the sum of the first maximum number multiplied by a first scaling factor and the second maximum number multiplied by a second scaling factor, wherein the first scaling factor plus the second scaling factor is less than or equal to one.

[0224] Example 18 includes the user equipment described in Example 15 or some other embodiment herein, and further includes: determining that PDCCH monitoring for the sSCell does not allow PDCCH overruns; determining that PDCCH overruns are not allowed for the common search space on the PCell or PSCell; or determining that PDCCH overruns are not allowed for Type 1 USS or Type 2 USS.

[0225] Example 19 includes the method according to Example 15 or some other embodiment herein, wherein the method further includes: determining the number of PDCCH candidates available for Type 1 USS and Type 2 USS without exceeding the limit by subtracting the number of PDCCH BD candidates to be monitored for the common search space (CSS) from the maximum number of BD candidates for the PCell or the PSCell.

[0226] Example 20 includes the method according to Example 19 or some other embodiment herein, wherein determining whether an overlimit has occurred includes: determining that an overlimit has occurred based on determining a first value greater than the number of PDCCH candidates available for Type 1 USS and Type 2 USS without overlimit, wherein the first value includes: the number of PDCCH BD candidates to be monitored for Type 1 CSS and Type 2 CSS; the number of PDCCH BD candidates to be monitored for Type 1 CSS plus the number of PDCCH BD candidates to be monitored for Type 2 CSS multiplied by a scaling factor; the number of PDCCH BD candidates to be monitored for Type 2 CSS plus the number of PDCCH BD candidates to be monitored for Type 1 CSS multiplied by a scaling factor; the scaling factor multiplied by the number of PDCCH BD candidates to be monitored for Type 1 CSS and Type 2 CSS; or a selection from the maximum of the number of PDCCH BD candidates to be monitored for Type 1 CSS and the number of PDCCH BD candidates to be monitored for Type 2 CSS.

[0227] Example 21 includes the method according to Example 15 or some other embodiment herein, further comprising: determining that an overlimit has occurred; and selecting one or more PDCCH BD candidates that will not be monitored based on a priority rule based on the determination that an overlimit has occurred.

[0228] Example 22 includes the method according to Example 21 or some other embodiment herein, wherein the priority rule is configured or predefined by radio resource control signaling.

[0229] Example 23 includes the method according to Example 21 or some other embodiment herein, wherein the priority rule prioritizes PDCCH BD candidates to be monitored for Type 2 USS over PDCCH BD candidates to be monitored for Type 1 USS; and prioritizes PDCCH BD candidates to be monitored for either Type 1 USS or Type 2 USS that the UE actively monitors over PDCCH BD candidates that the UE does not actively monitor.

[0230] Example 24 includes the method according to Example 21 or some other embodiment herein, wherein the priority rule prioritizes PDCCHD candidates of a first type of USS with a relatively low index over PDCCHD candidates of the first type of USS with a relatively high index, wherein the first type is a type 1 USS or a type 2 USS.

[0231] Example 25 includes a method of operating a base station, the method comprising: identifying a subcarrier spacing (SCS) for reference signal transmission; determining whether frequency domain (FD)-code division multiplexing (CDM) is enabled for the SCS; mapping the reference signal to resource elements based on whether FD-CDM is enabled; and transmitting the reference signal.

[0232] Example 26 includes the method according to Example 25 or some other embodiment herein, wherein the reference signal is a demodulation reference signal or a channel state information reference signal.

[0233] Example 27 includes the method according to Example 25 or some other embodiment herein, further comprising: accessing predefined SCS configuration information; and determining, based on the predefined SCS configuration information, whether to enable FD-CDM for the SCS.

[0234] Example 28 includes the method according to Example 27 or some other embodiment herein, wherein the SCS configuration information is used to instruct the disabling of FD-CDM for an SCS configuration set including SCS configurations having a 480 kHz or 960 kHz SCS.

[0235] Example 29 includes the method according to Example 25 or some other embodiment herein, further comprising: transmitting SCS configuration information in a system information message or radio resource control (RRC) signaling, the SCS configuration information being used to indicate whether FD-CDM is enabled for the SCS.

[0236] Example 30 includes the method according to Example 25 or some other embodiment herein, further comprising: transmitting SCS configuration information in a bitmap of a Media Access Control (MAC) Control Element (CE), the bitmap including values ​​corresponding to the SCS and indicating whether FD-CDM is enabled for the SCS.

[0237] Example 31 includes the method according to Example 25 or some other embodiment herein, further comprising: transmitting downlink control information (DCI) having an indication of whether FD-CDM is enabled for the SCS, wherein the indication is a sequence for scrambling cyclic redundancy check (CRC) bits of the DCI or one or more bits of a field of the DCI.

[0238] Example 32 includes the method according to Example 25 or some other embodiment herein, further comprising: transmitting downlink control information (DCI) including a demodulation reference signal (DMRS) antenna port indication, the DMRS antenna port indication referring to a first table if FD-CDM is enabled or referring to a second table if FD-CDM is not enabled, wherein the first table is larger than the second table.

[0239] Example 33 includes the method according to Example 32 or some other embodiment herein, wherein the second table includes only the front antenna port.

[0240] Example 34 includes a method of operating a user equipment (UE), the method comprising: mapping a demodulation reference signal (DMRS) sequence associated with a single DMRS port to consecutive resource elements in the frequency domain; and transmitting the DMRS sequence.

[0241] Example 35 includes the method according to Example 34 or some other embodiment herein, further comprising: transmitting the DMRS sequence via frequency domain code division multiplexing (FD-CDM).

[0242] Example 36 includes the method according to Example 34 or some other embodiment herein, further comprising: mapping DMRS sequences associated with different DMRS ports to consecutive resource elements in the time domain using orthogonal overlay codes; and transmitting the DMRS sequences.

[0243] Example 37 includes the method according to Example 34 or some other embodiment herein, further comprising: transmitting four data layers associated with the DMRS sequence.

[0244] Example 38 includes a method of operating user equipment (UE), the method comprising: mapping a demodulation reference signal (DMRS) sequence to resource elements across paired DMRS timings; and transmitting the DMRS sequence.

[0245] Example 39 includes the method according to Example 38 or some other embodiment herein, wherein the mapping of the DMRS sequence includes: mapping the DMRS sequence associated with the first and second antenna ports to a first resource element in a first DMRS timing of the paired DMRS timing and a second resource element in a second DMRS timing of the paired DMRS timing, wherein the first resource element is adjacent in the time domain, the second resource element is adjacent in the time domain, and the second resource element is offset from the first resource element in the frequency domain.

[0246] Example 40 includes the method according to Example 39 or some other embodiment herein, wherein the second resource element is offset by two subcarriers.

[0247] Example 41 includes the method according to Example 39 or some other embodiment herein, further comprising: encoding the DMRS sequence mapped to the first resource element and the DMRS sequence mapped to the second resource element using a first pair of orthogonal overlay codes.

[0248] Example 42 includes the method according to Example 39 or some other embodiment herein, further comprising: determining the length of the data duration in the symbol; determining the Physical Data Sharing Channel (PDSCH) mapping type; and determining the time domain separation between the first DMRS timing and the second DMRS timing based on the length and the PDSCH mapping type.

[0249] Example 43 includes the method according to Example 39 or some other embodiment herein, further comprising: detecting downlink control information (DCI) to schedule a first physical downlink shared channel (PDSCH) and a second PDSCH, wherein the second PDSCH is contiguous with the first PDSCH in the time domain, and the first resource element is in the first two symbols of the first PDSCH, and the second resource element is in the first two symbols of the second PDSCH.

[0250] Example 44 may include an apparatus comprising means for performing one or more elements of the method described or associated with any of Examples 1 to 43 or any other method or process described herein.

[0251] Example 45 may include one or more non-transitory computer-readable media, the one or more non-transitory computer-readable media including instructions that, when executed by one or more processors of an electronic device, cause the electronic device to perform one or more elements of the method or any other method or process described herein according to any one of Examples 1 to 43.

[0252] Example 46 may include an apparatus comprising one or more elements of a logic component, module, or circuit for performing a method or process described or associated with any of Examples 1 to 43 or any other method or process described herein.

[0253] Example 47 may include a method, technique, or process, or a part or component thereof, as described or associated with any of Examples 1 to 43.

[0254] Example 48 may include an apparatus comprising one or more processors and one or more computer-readable media, the one or more computer-readable media including instructions that, when executed by the one or more processors, cause the one or more processors to perform the methods, techniques, or processes or portions thereof described or associated with any of Examples 1 to 43.

[0255] Example 49 may include a signal, or a portion thereof, as described or associated with any of Examples 1 to 43.

[0256] Example 50 may include a datagram, information element, packet, frame, segment, PDU or message, or a portion or component thereof, as described or associated with any of Examples 1 to 43 or otherwise described in this disclosure.

[0257] Example 51 may include a signal, or a portion thereof, encoded with data according to any one of Examples 1 to 43 or otherwise described in this disclosure.

[0258] Example 52 may include a signal, or a portion thereof, encoded as a datagram, IE, packet, frame, segment, PDU, or message, as described or associated with any of Examples 1 to 43 or otherwise described in this disclosure.

[0259] Example 53 may include an electromagnetic signal carrying computer-readable instructions, wherein execution of the computer-readable instructions by one or more processors will cause the one or more processors to perform any of the methods, techniques or processes described or associated with any of Examples 1 to 43, or a portion thereof.

[0260] Example 54 may include a computer program comprising instructions, wherein execution of the program by a processing element will cause the processing element to perform a method, technique, or process, or a portion thereof, as described or associated with any of Examples 1 to 43.

[0261] Example 55 may include signals in a wireless network as shown and described herein.

[0262] Example 56 may include methods for communicating in a wireless network as shown and described herein.

[0263] Example 57 may include a system for providing wireless communication as shown and described herein.

[0264] Example 58 may include a device for providing wireless communication as shown and described herein.

[0265] Unless otherwise expressly stated, any of the examples above may be combined with any other example (or combination of examples). The foregoing description of one or more specific embodiments provides illustration and description, but is not intended to be exhaustive or to limit the scope of the embodiments to the precise form disclosed. In light of the teachings above, modifications and variations are possible, or modifications and variations may be derived from practice of various embodiments.

[0266] Although the above embodiments have been described in considerable detail, many variations and modifications will become apparent to those skilled in the art once the disclosure is fully understood. This disclosure is intended to render the following claims as encompassing all such variations and modifications.

Claims

1. A method for operating a base station, the method comprising: Generate information elements to include an indication of whether frequency domain (FD)-code division multiplexing (CDM) is enabled for the user equipment (UE); The information element is transmitted to the UE; Map one or more reference signals to one or more resource elements based on whether FD-CDM is enabled; as well as Transmitting the one or more reference signals, wherein the one or more reference signals include a first demodulation reference signal (DMRS) and a second DMRS, wherein the first DMRS is transmitted using a first antenna port, and wherein the first antenna port and the second antenna port are within a CDM group, the indication in the information element is used to indicate FD-CDM enabled for the UE, and the method further includes: Based on enabling the FD-CDM, a transmission to another UE is scheduled using the second antenna port, wherein the transmission is associated with a second DMRS to be transmitted using the second antenna port.

2. The method according to claim 1, further comprising: The Physical Downlink Shared Channel (PDSCH) transmission is associated with the DMRS.

3. The method of claim 1, wherein the first antenna port and the second antenna port are within a CDM group, the indication in the information element is used to indicate that FD-CDM is not enabled for the UE, and the method further comprises: Based on the fact that the FD-CDM is not enabled, the scheduling of transmissions to another UE using the second antenna port is suppressed.

4. The method according to claim 1, further comprising: The first DMRS with a first orthogonal coverage code (OCC) is transmitted; as well as The second DMRS with a second OCC is transmitted.

5. The method according to claim 1, wherein the FD-CDM is an FD-Orthogonal Cover Code (OCC).

6. The method according to claim 1, further comprising: The information element is transmitted in a Radio Resource Control (RRC) message.

7. A base station, the base station comprising: Processing circuit, the processing circuit being used for: Generate information elements to include an indication of whether frequency domain (FD)-code division multiplexing (CDM) is enabled for the user equipment (UE); Based on whether FD-CDM is enabled, one or more demodulation reference signals (DMRS) are mapped to one or more resource elements; This enables the first DMRS of the one or more DMRSs to transmit to the UE using the first antenna port; and An interface circuit coupled to the processing circuitry to transmit the information element on one or more DMRSs, wherein the first antenna port and the second antenna port are within a CDM group, the indication in the information element is used to indicate FD-CDM activation for the UE, and the processing circuitry is further configured to: Based on enabling the FD-CDM, a transmission to another UE is scheduled using the second antenna port, wherein the transmission is associated with a second DMRS to be transmitted using the second antenna port.

8. The base station of claim 7, wherein the first antenna port and the second antenna port are within a CDM group, the indication in the information element is used to indicate that FD-CDM is not enabled for the UE, and the processing circuitry is further configured to: Based on the fact that the FD-CDM is not enabled, the scheduling of transmissions to another UE using the second antenna port is suppressed.

9. One or more non-transitory computer-readable media, the one or more non-transitory computer-readable media having instructions that, when executed, cause a first user equipment (UE) to perform the following operations: Receive information elements from the base station indicating whether frequency domain (FD)-code division multiplexing (CDM) is enabled for the first UE; Receive a first reference signal from the first antenna port, the first reference signal being associated with a first downlink transmission of the first UE; as well as Based on whether FD-CDM is enabled, it is determined whether to schedule a second downlink transmission for the second UE. The second downlink transmission is associated with a second reference signal of the second antenna port, and the second antenna port and the first antenna port are within the CDM group. The instruction in the information element is used to instruct FD-CDM to be enabled for the UE, and when the instruction is executed, it also causes the UE to perform the following operations: Determine to schedule the second downlink transmission for the second UE.

10. One or more non-transitory computer-readable media according to claim 9, wherein the first reference signal includes a demodulation reference signal (DMRS).

11. The one or more non-transitory computer-readable media of claim 10, wherein the instructions, when executed, further cause the first UE to perform the following operations: Receive the first downlink transmission, wherein the first downlink transmission is a Physical Downlink Shared Channel (PDSCH) transmission.

12. The one or more non-transitory computer-readable media of claim 9, wherein the indication in the information element is for indicating that FD-CDM is not enabled for the UE, and the instruction, when executed, also causes the first UE to perform the following operations: It was determined that the second downlink transmission was not scheduled for the second UE.

13. The one or more non-transitory computer-readable media according to claim 9, further comprising: The first reference signal is processed using orthogonal cover code (OCC).

14. One or more non-transitory computer-readable media according to claim 9, wherein the FD-CDM is an FD-orthogonal overlay code (OCC).

Images