Additional DMRS for NR PDSCH considering LTE-NR DL sharing

Abstract

The present invention provides a mobile radio communication terminal device, which is operable to facilitate a physical downlink shared channel demodulation reference signal of a first mobile radio communication network communication connection during overlapping communications between the first mobile radio communication network and a second mobile radio communication network. The second mobile radio communication network is configured to transmit a cell-specific reference signal. The mobile radio communication terminal device includes one or more processors, the one or more processors being configured to generate a request for generating a demodulation reference signal to be transmitted from the first mobile radio communication network according to a modified schedule with respect to a scheduling shift of the cell-specific reference signal; and a memory, the memory storing the physical downlink shared channel demodulation reference signal of the first mobile radio communication network.

Description

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS

[0002] This application is based on and claims priority from provisional patent application 62 / 742,129 filed with the U.S. Patent and Trademark Office on October 5, 2018, the disclosure of which is incorporated herein by reference in its entirety. Technical Field

[0003] Various aspects relate generally to the field of wireless communications. Background Art

[0004] For the PDSCH (Physical Downlink Shared Channel) in NR (New Radio) systems, a number of DMRS (Demodulation Reference Signal) configurations are supported, catering for different use cases and link conditions / deployment scenarios etc. These range from single symbol "pre-only" DMRS (where the PDSCH DMRS occurs relatively early in the PDSCH duration) to multi-symbol DMRS with or without additional occurrences of DMRS within the scheduled PDSCH. It is also expected that NR systems may be deployed in LTE (Long Term Evolution) bands and may co-exist with LTE as a form of shared DL (downlink) resources between LTE and NR. In such scenarios using "DL sharing", it is expected that NR will be deployed with the same subcarrier spacing (SCS) as LTE DL, i.e. an SCS of 15kHz for DL ​​operations.

[0005] It has been identified that for some DMRS configurations for NR PDSCH, the additional DMRS location may coincide with LTE symbols carrying LTE cell-specific reference signals (CRS). One such example is the case when additional DMRS is configured for PDSCH of mapping type A with a length of 14 symbols and an additional single-symbol DMRS, which is currently designated as mapping to symbol #11 of the NR slot, which collides with the symbol carrying the LTE CRS. This impacts the ability to achieve DL resource sharing between NR and LTE in the same carrier in an efficient manner, as it implies restrictions on PDSCH scheduling (adversely affecting the achievable peak throughput performance) or configuration of additional DMRS (which may affect link performance in high mobility scenarios), etc.

[0006] To this end, it has been proposed that, for PDSCH mapping type A with a duration of 13 or 14 symbols (from the slot boundary to the last PDSCH symbol) and dmrs-AdditionalPosition = 'pos1', when the NR UE (user equipment) is configured to operate in 15kHz DL BWP (bandwidth part) and is configured to rate match the PDSCH around the LTE CRS as indicated by the higher-layer parameter Ite-CRS-ToMatchAround, for the case of unicast PDSCH transmission, the additional DMRS position is shifted to symbol #12 of the NR slot in order to avoid such conflicts between LTE CRS transmission and NR DMRS transmission.

[0007] However, such a shift of the last DMRS means that the UE may need to wait until the last DMRS symbol is received before performing channel estimation and demodulation for PDSCH reception, thereby reducing the effective available minimum PDSCH processing time (for the corresponding HARQ (Hybrid ARQ, Hybrid Automatic Repeat Request)-ACK (Acknowledgement) transmission) by one OFDM (Orthogonal Frequency Division Multiplexing) symbol in this case. BRIEF DESCRIPTION OF THE DRAWINGS

[0008] In the drawings, similar reference characters generally indicate the same parts throughout the different views. The drawings are not necessarily drawn to scale, but emphasis is generally placed on illustrating the principles of the invention. In the following description, various aspects of the invention are described with reference to the following drawings, in which:

[0009] Figure 1 An architecture of a system of networks according to various aspects is shown;

[0010] Figure 2 An exemplary architecture of a system according to various aspects is shown.

[0011] Figure 3 Examples of infrastructure equipment according to various aspects are shown.

[0012] Figure 4 Examples of platforms (or "devices") according to various aspects are shown.

[0013] Figure 5 Exemplary components of a baseband circuit and a radio front end module (RFEM) according to various aspects are shown.

[0014] Figure 6 is a block diagram illustrating components capable of reading instructions from a machine-readable or computer-readable medium and capable of performing any one or more of the methodologies discussed herein, according to some exemplary aspects.

[0015] FIG. 7A to FIG. 7D is a flow chart of a method according to various aspects. DETAILED DESCRIPTION

[0016] The following detailed description refers to the accompanying drawings that show, by way of illustration, specific details and aspects in which the invention may be practiced.

[0017] The word “exemplary” is used herein to mean “serving as an example, instance, or illustration.” Any aspect or design described herein as “exemplary” is not necessarily to be construed as preferred or advantageous over other aspects or designs.

[0018] The present disclosure provides a mechanism to address the above-mentioned impact on the UE minimum processing time. In addition, the present invention provides a method that can be used as an alternative to the option of shifting the last DMRS symbol according to the configuration of the higher layer parameter Ite-CRS-ToMatchAround.

[0019] Additional DMRS positions for PDSCH mapping type A

[0020] The UE assumes that the PDSCH DM-RS (demodulation reference signal) is mapped to the physical resource according to configuration type 1 or configuration type 2 given by the higher-level parameter dmrs-Type. The UE assumes that the sequence r(m) is determined by the factor Scaled to comply with the transmit power specified in 3GPP (3rd Generation Partnership Project) TS 38.214 V15.3.0 (2018-09) and mapped to resource elements (k, l) according to p,μ :

[0021]

[0022]

[0023] k′=0,1

[0024]

[0025] n=0,1,...

[0026] where w f (k'), w t (l') and Δ are given in Tables 7.4.1.1.2-1 and 7.4.1.1.2-2 and satisfy the following conditions:

[0027] - Resource element is within a common resource block allocated for PDSCH transmission

[0028] Reference point of k:

[0029] - subcarrier 0 of the lowest numbered resource block in CORESET (Control Resource Set) 0, if the corresponding PDCCH (Physical Downlink Control Channel) is associated with CORESET 0 and PDCCH type 0 common search space and is addressed to SI-RNTI (System Information - Radio Network Temporary Identifier);

[0030] - Otherwise, subcarrier 0 in common resource block 0

[0031] The reference point of l and the position of the first DM-RS symbol l0 depend on the mapping type:

[0032] -For PDSCH mapping type A:

[0033] -l is defined relative to the start of the time slot

[0034] - If the higher layer parameter dmrs-TypeA-Position is equal to 'pos3' and l0=2, then l0=3, otherwise

[0035] -For PDSCH mapping type B:

[0036] -l is defined relative to the starting point of the scheduled PDSCH resource

[0037] -l0=0

[0038] The position of the DM-RS symbol is determined by Given, and

[0039] - For PDSCH mapping type A, the duration is between the first OFDM symbol of a slot and the last OFDM symbol of a PDSCH resource scheduled in the slot

[0040] - For PDSCH mapping type B, the duration is the number of OFDM symbols of the scheduled PDSCH resources for signaling transmission

[0041] And according to Tables 7.4.1.1.2-3 and 7.4.1.1.2-4. The case where dmrs-AdditionalPosition is equal to 'pos3' is supported only when dmrs-TypeA-Position is equal to 'pos2'. For PDSCH mapping type A, the durations of 3 and 4 symbols in Tables 7.4.1.1.2-3 and 7.4.1.1.2-4, respectively, are applicable only when dmrs-TypeA-Position is equal to 'pos2'.

[0042] The PDSCH DMRS position of PDSCH mapping type A is shown in Table 7.4.1.1.2-3:

[0043] Table 7.4.1.1.2-1: Parameters for PDSCH DM-RS configuration type 1.

[0044]

[0045] Table 7.4.1.1.2-2: Parameters for PDSCH DM-RS configuration type 2.

[0046]

[0047]

[0048] Table 7 4.1.1.2-3: PDSCH DM-RS position for single-symbol DM-RS 1 .

[0049]

[0050] Table 7.4.1.1.2-4: PDSCH DM-RS positions for dual-symbol DM-RS

[0051]

[0052]

[0053] Note that in the table referenced above, the column "Symbol Duration" (D) indicates, for a particular PDSCH allocation with mapping type A, the number of symbols from the slot boundary (symbol #0) to the last PDSCH symbol.

[0054] As can be seen, there are multiple possible situations where NR PDSCH DMRS may conflict with LTE CRS transmissions in a symbol. While the ideas in this disclosure are not limited in their applicability to other situations, since other situations of shorter PDSCH allocations may be addressed via other scheduling alternatives, and "full slot" or "almost full slot" PDSCH allocations are significant in achieving achievable peak throughput performance, the situations involving "full slot" or "almost full slot" PDSCH allocations (marked in bold and underlined in the table above) are prioritized for exposure purposes.

[0055] In one aspect, the DMRS positions for single-symbol DMRS with D=13, 14 for PDSCH mapping type A are defined such that when the UE is configured with dmrs-AdditionalPosition='pos1' or dmrs-AdditionalPosition='pos2' or dmrs-AdditionalPosition='pos3', the last single-symbol DMRS in the PDSCH is in symbol #12 of the time slot.

[0056] Furthermore, in another aspect, the DMRS positions for single-symbol DMRS of D=13, 14 for PDSCH mapping type A are defined such that when the UE is configured with dmrs-AdditionalPosition='pos2', the first additional single-symbol DMRS position may be in symbol #8 of the slot.

[0057] In another example, any of the above aspects may apply regardless of whether the UE is configured with Ite-CRS-ToMatchAround via higher layers. In this case, the new DMRS position for additional DMRS symbols as in the above aspects may be applied to both unicast and broadcast PDSCHs.

[0058] Alternatively, mapping to symbol #12 or #8 (for the above two aspects, respectively) is applied only when the UE is configured with Ite-CRS-ToMatchAround via a higher layer. In this case, the above aspects can be applied only to unicast PDSCH, that is, PDSCH scheduled using PDCCH with CRC (cyclic redundancy check), which is scrambled using C-RNTI (cell radio network temporary identity (cell RNTI)), CS (circuit switching)-RNTI or MCS (modulation and coding scheme)-C-RNTI.

[0059] In addition or alternatively to the above-mentioned dependency on Ite-CRS-ToMatchAround via higher layers, in one aspect, the above-mentioned additional DMRS positions are defined when the PDSCH SCS is 15kHz. Alternatively, in addition or alternatively to the above-mentioned dependency on Ite-CRS-ToMatchAround via higher layers, in one aspect, the above-mentioned additional DMRS positions are defined for all SCSs (which in turn means PDSCH SCSs) in which the DL BWP of the PDSCH is scheduled.

[0060] The above two aspects are summarized in Table 1 below, where the values ​​that have changed compared to the existing specifications are marked in red.

[0061] Table 1: PDSCH DMRS for PDSCH mapping type A

[0062]

[0063] For the case of dual-symbol DMRS, in one aspect, when PDSCH is such that D=14, for dmrs-AdditionalPosition='pos1', the DMRS position is defined as (l0,12). For other cases of D values, the existing values ​​in Table 7.4.1.1.2-4 of TS38.211 v15.3.0 (2018-09) are used.

[0064] Adjustment of UE minimum processing time in case of additional DMRS position shift

[0065] In one aspect, in order to address the impact on the UE minimum processing time for PDSCH processing due to the shift of the last DMRS symbol within the PDSCH duration, when the UE is configured with dmrs-AdditionalPosition≠pos0 in DMRS-DownlinkConfig in any of dmrs-DownlinkForPDSCHMappingTypeA and dmrsDownlinkForPDSCH-MappingTypeB, or when this high-level parameter is not configured, when the last symbol DMRS position within the PDSCH is symbol #12 of the time slot of PDSCH mapping type A, the minimum UE processing time value (N1) (in OFDM symbols) is increased by one symbol.

[0066] Alternatively, in the case where the UE is configured with dmrs-AdditionalPosition=pos1 in DMRS-DownlinkConfig in dmrs-DownlinkForPDSCHMappingType A, when the second DMRS position is symbol #12 of the time slot of PDSCH mapping type A, the minimum UE processing time value (N1) (in OFDM symbols) is increased by one symbol.

[0067] In another example, when the SCS of the scheduled PDSCH is 15kHz, an additional one symbol margin may be applied. That is, when μ=0, an additional one symbol margin is applicable to determine the minimum PDSCH processing time, as shown in Table 5.3-1 of TS 38.214v15.3.0 (2018-09).

[0068] For the case of dual-symbol DMRS, in one aspect, when the UE is configured with dmrs-AdditionalPosition≠pos0 in DMRS-DownlinkConfig in either dmrs-DownlinkForPDSCHMappingTypeA or dmrsDownlinkForPDSCH-MappingTypeB, or when this higher-level parameter is not configured, when the last dual-symbol DMRS position within the PDSCH is symbol #12 of the time slot of PDSCH mapping type A, the minimum UE processing time value (N1) (in OFDM symbols) is increased by two symbols.

[0069] Alternatively, when the UE is configured with dmrs-AdditionalPosition=pos1 in DMRS-DownlinkConfig in dmrs-DownlinkForPDSCHMappingType A, when the last dual-symbol DMRS position within the PDSCH is symbol #12 of the time slot of PDSCH mapping type A, the minimum UE processing time value (N1) (in OFDM symbols) is increased by two symbols.

[0070] It should be noted that the above aspects are directly applicable to the case where PDSCH mapping type A is scheduled with D=8 or D=9, and for dmrs-AdditionalPosition='pos1', the corresponding DMRS position is defined as (l0,8), regardless of the configuration of the higher-level parameter Ite-CRS-ToMatchAround or when the higher-level parameter Ite-CRS-ToMatchAround is configured to the UE.

[0071] Figure 1 An exemplary architecture of a system 100 of a network according to various embodiments is shown. The following description is provided for an exemplary system 100 operating in conjunction with LTE system standards and 5G (fifth generation) or NR system standards provided by 3GPP technical specifications. However, the exemplary embodiments are not limited in this regard, and the embodiments may be applied to other networks that benefit from the principles described herein, such as future 3GPP systems (e.g., sixth generation (6G)) systems, IEEE (Institute of Electrical and Electronics Engineers) 802.16 protocols (e.g., WMAN, WiMAX (Worldwide Interoperability for Microwave Access), etc.), etc.

[0072] like Figure 1As shown, system 100 includes UE 101a and UE 101b (collectively referred to as "UE 101"). In this example, UE 101 is shown as a smart phone (e.g., a handheld touch screen mobile computing device that can connect to one or more cellular networks), but may also include any mobile or non-mobile computing device, such as a consumer electronic device, a cellular phone, a smart phone, a feature phone, a tablet computer, a wearable computer device, a personal digital assistant (PDA), a pager, a wireless handheld device, a desktop computer, a laptop computer, an in-vehicle infotainment (IVI), an in-vehicle entertainment (ICE) device, an instrument panel (IC), a head-up display (HUD) device, an on-board diagnostic (OBD) device, a dashtop mobile equipment (DME), a mobile data terminal (MDT), an electronic engine management system (EEMS), an electronic / engine electronic control unit (ECU), an electronic / engine electronic control module (ECM), an embedded system, a microcontroller, a control module, an engine management system (EMS), a networked or "smart" appliance, an MTC (machine type communication) device, an M2M (machine to machine), an IoT (Internet of Things) device, etc.

[0073] In some embodiments, any of the multiple UEs 101 may be an IoT UE, which may include a network access layer designed for low-power IoT applications that utilize short-term UE connections. The IoT UE may utilize technologies such as M2M or MTC to exchange data with an MTC server or device via PLMN (Public Land Mobile Network), ProSe (Proximity Service, based on proximity services) or D2D (Device to Device) communications, sensor networks, or IoT networks. M2M or MTC data exchanges may be machine-initiated data exchanges. The IoT network describes interconnected IoT UEs, which may include uniquely identifiable embedded computing devices (within the Internet infrastructure) with short-term connections. The IoT UE may execute background applications (e.g., keep active messages, status updates, etc.) to facilitate connectivity to the IoT network.

[0074] UE 101 may be configured to be communicatively coupled, for example, to an AN or RAN (Radio Access Network) 110. In an embodiment, RAN 110 may be an NG (Next Generation) RAN or 5G RAN, E-UTRAN (Evolved Universal Terrestrial Radio Access Network), or a traditional RAN, such as UTRAN or GERAN (GSM (Global System for Mobile Communications, Group Special Mobile) EDGE RAN, GSM EDGE Radio Access Network). As used herein, the term "NG RAN" or the like may refer to a RAN 110 operating in an NR or 5G system 100, while the term "E-UTRAN" or the like may refer to a RAN 110 operating in an LTE or 4G (Fourth Generation) system 100. Multiple UEs 101 utilize connections (or channels) 103 and 104, respectively, each connection including a physical communication interface or layer (discussed in further detail below).

[0075] In this example, connections 103 and 104 are shown as air interfaces to achieve communication coupling, and may be consistent with a cellular communication protocol, such as a GSM protocol, a CDMA (Code Division Multiple Access) network protocol, a PTT (Push to Talk) protocol, a POC (PTT on Cellular) protocol, a UMTS (Universal Mobile Telecommunications System) protocol, a 3GPP LTE protocol, a 5G protocol, a NR protocol, and / or any other communication protocol discussed herein. In an embodiment, the UE 101 may directly exchange communication data via the ProSe interface 105. The ProSe interface 105 may alternatively be referred to as the SL interface 105 and may include one or more logical channels, including but not limited to a PSCCH (Physical Side Link Control Channel), a PSSCH (Physical Side Link Shared Channel), a PSDCH (Physical Side Link Downlink Channel), and a PSBCH (Physical Side Link Broadcast Channel).

[0076] UE 101b is shown configured to access AP (application protocol, antenna interface, access point) 106 (also referred to as "WLAN (wireless local area network) node 106", "WLAN 106", "WLAN terminal 106" or "WT 106", etc.) via connection 107. Connection 107 may include a local wireless connection, such as a connection consistent with any IEEE 802.11 protocol, wherein AP 106 will include wireless fidelity router. In this example, AP 106 is shown connected to the Internet without being connected to the core network of the wireless system (described in further detail below). In various embodiments, UE 101b, RAN 110, and AP 106 may be configured to utilize LWA (LTE-WLAN aggregation) operation and / or to operate with LWIP (LTE / WLAN radio level integrated with IPsec tunnel). LWA operation may involve UE 101b in RRC_CONNECTED state configured by RAN nodes 111a-b to utilize radio resources of LTE and WLAN. LWIP operation may involve UE 101b using WLAN radio resources (e.g., connection 107) via an IPsec protocol tunnel to authenticate and encrypt packets (e.g., IP (Internet Protocol) packets) sent over connection 107. IPsec tunnel transmission may include encapsulating the entire original IP packet and adding a new packet header, thereby protecting the original header of the IP packet.

[0077] The RAN 110 may include one or more AN (access network) nodes or RAN nodes 111a and 111b (collectively referred to as "RAN nodes 111") that enable connections 103 and 104. As used herein, the terms "access node", "access point", etc. may describe equipment that provides radio baseband functions for data and / or voice connections between a network and one or more users. These access nodes may be referred to as BS (base station), gNB (next generation Node B), RAN node, eNB (evolved Node B, E-UTRAN Node B), NodeB, RSU (road side unit), TRxP or TRP (transmit receive point), etc., and may include ground stations (e.g., terrestrial access points) or satellite stations that provide coverage within a geographic area (e.g., a cell). As used herein, the terms "NG RAN node" and the like may refer to a RAN node 111 (e.g., a gNB) operating in an NR or 5G system 100, while the terms "E-UTRAN node" and the like may refer to a RAN node 111 (e.g., an eNB) operating in an LTE or 4G system 100. According to various embodiments, the RAN node 111 may be implemented as one or more of dedicated physical devices such as a macrocell base station and / or a low power (LP) base station for providing a femtocell, picocell or other similar cell with a smaller coverage area, smaller user capacity or higher bandwidth than a macrocell.

[0078] In some embodiments, all or part of the RAN node 111 may be implemented as one or more software entities running on a server computer as part of a virtual network, which may be referred to as a CRAN (Cloud Radio Access Network) and / or a vBBUP (Virtual Baseband Unit Pool). In these embodiments, the CRAN or vBBUP may implement RAN functional splits, such as PDCP (Packet Data Convergence Protocol) splits, where the RRC (Radio Resource Control, Radio Resource Control layer) and PDCP layers are operated by the CRAN / vBBUP, and other L2 (Layer 2 (Data Link Layer)) protocol entities are operated by individual RAN nodes 111; MAC / PHY (Physical Layer) splits, where the RRC, PDCP, RLC (Radio Link Control, Radio Link Control layer) and MAC layers are operated by the CRAN / vBBUP, and the PHY layer is operated by individual RAN nodes 111; or "Lower PHY" splits, where the RRC, PDCP, RLC, MAC (Medium Access Control (Protocol Hierarchy Context)) layers and upper portions of the PHY layers are operated by the CRAN / vBBUP, and the lower portions of the PHY layers are operated by individual RAN nodes 111. This virtualization framework allows idle processor cores of multiple RAN nodes 111 to execute other virtualized applications. In some implementations, a separate RAN node 111 may represent a single RAN node 111 connected via a separate F1 interface ( Figure 1 In some implementations, the gNB-DU may include one or more remote radio heads or RFEMs (see, e.g., Figure 3 ), and the gNB-CU may be operated by a server (not shown) located in the RAN 110 or by a server pool in a manner similar to CRAN / vBBUP. In addition or alternatively, one or more of the plurality of RAN nodes 111 may be a next generation eNB (ng-eNB), which is a RAN node that provides E-UTRA (Evolved UMTS Terrestrial Radio Access) user plane and control plane protocol terminals to the plurality of UEs 101 and is connected to the 5GC (5G Core Network) via an NG interface (discussed below).

[0079] In a V2X (vehicle-to-everything) scenario, one or more of the RAN nodes 111 may be an RSU or act as an RSU. The term "roadside unit" or "RSU" may refer to any traffic infrastructure entity used for V2X communication. The RSU may be implemented in or by a suitable RAN node or a stationary (or relatively stationary) UE, wherein an RSU implemented in or by a UE may be referred to as a "UE-type RSU", an RSU implemented in or by an eNB may be referred to as an "eNB-type RSU", an RSU implemented in or by a gNB may be referred to as a "gNB-type RSU", and so on. In one example, the RSU is a computing device coupled to a radio frequency circuit located on the road side that provides connectivity support to a passing vehicle UE 101 (vUE 101). The RSU may also include internal data storage circuitry for storing intersection map geometry, traffic statistics, media, and applications / software for sensing and controlling ongoing vehicle and pedestrian traffic. The RSU may operate on the 5.9 GHz Direct Short Range Communication (DSRC) band to provide extremely low latency communications required for high-speed events, such as collision avoidance, traffic warnings, etc. In addition or alternatively, the RSU may operate on the cellular V2X band to provide the aforementioned low latency communications as well as other cellular communication services. In addition or alternatively, the RSU may operate as a Wi-Fi hotspot (2.4 GHz band) and / or provide connectivity to one or more cellular networks to provide uplink and downlink communications. Some or all of the computing device and the RSU's RF circuitry may be packaged in a weather-resistant enclosure suitable for outdoor installation, and may include a network interface controller to provide a wired connection (e.g., Ethernet) to a traffic signal controller and / or backhaul network.

[0080] Any of the RAN nodes 111 may serve as a termination point for the air interface protocol and may be the first point of contact for the UE 101. In some embodiments, any of the RAN nodes 111 may perform various logical functions of the RAN 110, including but not limited to the functions of a radio network controller (RNC), such as radio bearer management, uplink and downlink dynamic radio resource management and data packet scheduling, and mobility management.

[0081] In an embodiment, UE 101 may be configured to communicate with each other or with any one of RAN nodes 111 using OFDM communication signals over a multi-carrier communication channel according to various communication techniques, such as, but not limited to, OFDMA (Orthogonal Frequency Division Multiple Access) communication techniques (e.g., for downlink communication) or SC-FDMA (Single Carrier Frequency Division Multiple Access) communication techniques (e.g., for uplink and ProSe or sidelink communication), although the scope of the embodiment is not limited in this respect. The OFDM signal may include multiple orthogonal subcarriers.

[0082] In some embodiments, a downlink resource grid may be used for downlink transmissions from any of the RAN nodes 111 to the UE 101, while uplink transmissions may utilize similar techniques. The grid may be a time-frequency grid, referred to as a resource grid or a time-frequency resource grid, which is a physical resource in the downlink in each time slot. For OFDM systems, such a time-frequency plane representation is a common practice, which makes wireless resource allocation intuitive. Each column and each row of the resource grid corresponds to an OFDM symbol and an OFDM subcarrier, respectively. The duration of the resource grid in the time domain corresponds to a time slot in a radio frame. The smallest time-frequency unit in the resource grid is represented as a resource element. Each resource grid includes a plurality of resource blocks, which describe the mapping of certain physical channels to resource elements. Each resource block includes a collection of resource elements. In the frequency domain, this may represent the minimum amount of resources that can currently be allocated. Such resource blocks are used to transmit several different physical downlink channels.

[0083] According to various embodiments, the UEs 101, 102 and the RAN nodes 111, 112 communicate (e.g., transmit and receive) data via a licensed medium (also referred to as a "licensed spectrum" and / or a "licensed band") and an unlicensed shared medium (also referred to as an "unlicensed spectrum" and / or an "unlicensed band"). The licensed spectrum may include channels operating in a frequency range of approximately 400 MHz to approximately 3.8 GHz, and the unlicensed spectrum may include a 5 GHz band.

[0084] To operate in the unlicensed spectrum, the UE 101, 102 and the RAN nodes 111, 112 may operate using LAA (licensed assisted access), eLAA (enhanced licensed assisted access, enhanced LAA) and / or feLAA (further enhanced licensed assisted access, further enhanced LAA) mechanisms. In these specific implementations, the UE 101, 102 and the RAN nodes 111, 112 may perform one or more known medium sensing operations and / or carrier sensing operations to determine whether one or more channels in the unlicensed spectrum are unavailable or otherwise occupied before transmitting in the unlicensed spectrum. The medium / carrier sensing operations may be performed according to a listen-before-talk (LBT) protocol.

[0085] LBT is a mechanism for equipment (e.g., UE 101, 102, RAN nodes 111, 112, etc.) to sense a medium (e.g., a channel or carrier frequency) and transmit when the medium is sensed to be idle (or when a particular channel in the medium is sensed to be unoccupied). The medium sensing operation may include CCA (clear channel assessment) which utilizes at least ED (energy detection) to determine whether other signals are present on the channel in order to determine whether the channel is occupied or idle. The LBT mechanism allows cellular / LAA networks to coexist with existing systems in unlicensed spectrum and with other LAA networks. ED may include sensing RF (radio frequency) energy over a period of time on an expected transmission band and comparing the sensed RF energy to a predefined or configured threshold.

[0086] Typically, existing systems in the 5 GHz band are WLANs based on IEEE 802.11 technology. WLAN adopts a contention-based channel access mechanism called CSMA (Carrier Sense Multiple Access) / CA (CSMA with Collision Avoidance). Here, when a WLAN node (e.g., a mobile station (MS) such as UE 101, 102, AP 106, etc.) intends to transmit, the WLAN node may first perform CCA before transmission. In addition, in the case where more than one WLAN node senses the channel as idle and transmits at the same time, a backoff mechanism is used to avoid collisions. The backoff mechanism may be a counter randomly introduced within the CWS (contention window size), which increases exponentially when a collision occurs and is reset to a minimum value when the transmission is successful. The LBT mechanism designed for LAA is somewhat similar to CSMA / CA for WLAN. In some implementations, the LBT process for a DL or UL (uplink) transmission burst (including a PDSCH or PUSCH (physical uplink shared channel) transmission) may have a variable length LAA contention window between X and Y ECCA (extended clear channel assessment, extended CCA) slots, where X and Y are the minimum and maximum values ​​of the CWS for LAA. In one example, the minimum CWS for LAA transmissions may be 9 microseconds (μs); however, the size of the CWS and MCOT (maximum channel occupancy time; e.g., transmission burst) may be based on government regulatory requirements.

[0087] The LAA mechanism is built on the CA (Carrier Aggregation, Authentication Authority) technology of the LTE-Advanced system. In CA, each aggregated carrier is called a CC (Component Carrier, Country Code, Cryptographic Checksum). A CC may have a bandwidth of 1.4, 3, 5, 10, 15, or 20 MHz, and up to five CCs may be aggregated, so the maximum aggregated bandwidth is 100 MHz. In an FDD (Frequency Division Duplex) system, the number of aggregated carriers may be different for DL ​​and UL, where the number of UL CCs is equal to or lower than the number of DL component carriers. In some cases, each CC may have a different bandwidth from other CCs. In a TDD (Time Division Duplex) system, the number of CCs and the bandwidth of each CC are typically the same for DL ​​and UL.

[0088] CA also includes individual service cells to provide individual CCs. The coverage of the service cells may be different, for example, because CCs on different frequency bands will experience different path losses. The primary service cell or PCell may provide a PCC (primary component carrier, primary CC) for both UL and DL, and may handle activities related to RRC and NAS (non-access stratum, non-access layer). Other service cells are called SCells, and each SCell may provide individual SCCs (secondary component carriers, secondary CCs) for both UL and DL. SCCs may be added and removed as needed, and changing PCCs may require UE 101, 102 to undergo switching. In LAA, eLAA, and feLAA, some or all of the SCells (secondary cells) may operate in an unlicensed spectrum (referred to as "LAA SCells"), and the LAA SCells are assisted by a PCell (primary cell) operating in a licensed spectrum. When a UE is configured with more than one LAA SCell, the UE may receive UL authorizations on the configured LAA SCells, indicating different PUSCH start positions within the same subframe.

[0089] The PDSCH carries user data and higher layer signaling to multiple UEs 101. The PDCCH carries, among other information, information about the transport format and resource allocation related to the PDSCH channel. It can also inform multiple UEs 101 about the transport format, resource allocation, and HARQ information related to the uplink shared channel. Typically, downlink scheduling (allocation of control and shared channel resource blocks to UEs 101b within a cell) can be performed at any one of the RAN nodes 111 based on channel quality information fed back from any one of the UEs 101. Downlink resource allocation information can be sent on the PDCCH for (e.g., allocated to) each of the UEs 101.

[0090] PDCCH uses CCE (control channel element) to transmit control information. Before being mapped to resource elements, the PDCCH complex-valued symbols can first be organized into quadruplets, which can then be arranged using a sub-block interleaver for rate matching. One or more of these CCEs can be used to transmit each PDCCH, where each CCE can correspond to nine sets of four physical resource elements, respectively, called REGs (resource element groups). Four orthogonal phase shift keying (QPSK) symbols can be mapped to each REG. Depending on the size of the DCI (downlink control information) and channel conditions, one or more CCEs can be used to transmit the PDCCH. There may be four or more different PDCCH formats defined in LTE with different numbers of CCEs (e.g., aggregation levels, L=1, 2, 4, or 8).

[0091] Some embodiments may use the concept of resource allocation for control channel information, which is an extension of the above concept. For example, some embodiments may utilize EPDCCH (enhanced PDCCH, enhanced physical downlink control channel) that uses PDSCH resources for control information transmission. One or more ECCEs (enhanced control channel elements, enhanced CCEs) may be used to transmit EPDCCH. Similar to the above, each ECCE may correspond to nine sets including four physical resource elements, referred to as EREGs (enhanced REGs, enhanced resource element groups). In some cases, ECCEs may have other numbers of EREGs.

[0092] RAN nodes 111 may be configured to communicate with each other via interface 112. In embodiments where system 100 is an LTE system (eg, when CN 120 is a Figure 2101 ), the interface 112 may be an X2 interface 112. The X2 interface may be defined between two or more RAN nodes 111 (e.g., two or more eNBs, etc.) connected to the EPC 120, and / or between two eNBs connected to the EPC 120. In some specific implementations, the X2 interface may include an X2 user plane interface (X2-U) and an X2 control plane interface (X2-C). The X2-U may provide a flow control mechanism for user packets transmitted over the X2 interface, and may be used to transmit information about the delivery of user data between eNBs. For example, the X2-U may provide specific sequence number information about user data transmitted from the MeNB (primary eNB) to the SeNB (secondary eNB); information about the successful in-sequence delivery of PDCP PDUs (protocol data units) from the SeNB to the UE 101 for user data; information about PDCP PDUs that are not delivered to the UE 101; information about the current minimum expected buffer size at the SeNB for transmitting user data to the UE; and the like. X2-C can provide intra-LTE access mobility functions, including context transfer from source eNB to target eNB, user plane transmission control, etc.; load management functions; and inter-cell interference coordination functions.

[0093] In an embodiment where the system 100 is a 5G or NR system (e.g., when the CN 120 is a 5GC), the interface 112 may be an Xn interface 112. The Xn interface is defined between two or more RAN nodes 111 (e.g., two or more gNBs, etc.) connected to the 5GC 120, between a RAN node 111 (e.g., a gNB) and an eNB connected to the 5GC 120, and / or between two eNBs connected to the 5GC 120. In some specific implementations, the Xn interface may include an Xn user plane (Xn-U) interface and an Xn control plane (Xn-C) interface. The Xn-U may provide non-guaranteed delivery of user plane PDUs and support / provide data forwarding and flow control functions. The Xn-C may provide management and error handling functions for managing the functions of the Xn-C interface; mobility support for UE 101 in a connected mode (e.g., CM (Connection Management, Conditional Enforcement)-CONNECTED) includes functions for managing UE mobility in a connected mode between one or more RAN nodes 111. The mobility support may include context transfer from the old (source) serving RAN node 111 to the new (target) serving RAN node 111; and control of the user plane tunnel between the old (source) serving RAN node 111 and the new (target) serving RAN node 111. The protocol stack of Xn-U may include a transport network layer built on an Internet Protocol (IP) transport layer, and a GTP-U (GPRS Tunneling Protocol for User Plane) layer on top of a UDP (User Datagram Protocol) and / or IP layer for carrying user plane PDUs. The Xn-C protocol stack may include an application layer signaling protocol (referred to as the Xn Application Protocol (Xn-AP)) and a transport network layer built on SCTP (Single Carrier Frequency Division Multiple Access). SCTP may be on top of the IP layer and may provide guaranteed delivery of application layer messages. In the transport IP layer, point-to-point transport is used to deliver signaling PDUs. In other specific implementations, the Xn-U protocol stack and / or the Xn-C protocol stack may be the same or similar to the user plane and / or control plane protocol stacks shown and described herein.

[0094] RAN 110 is shown as being communicatively coupled to a core network—in this embodiment, communicatively coupled to a core network (CN) 120. CN 120 may include a plurality of network elements 122 configured to provide various data and telecommunication services to customers / subscribers (e.g., users of a plurality of UEs 101) connected to CN 120 via RAN 110. The components of CN 120 may be implemented in one physical node or separate physical nodes, which include components for reading and executing instructions from a machine-readable or computer-readable medium (e.g., a non-transitory machine-readable storage medium). In some embodiments, NFV (network function virtualization) may be used to virtualize any or all of the above-mentioned network node functions via executable instructions stored in one or more computer-readable storage media (described in further detail below). A logical instance of CN 120 may be referred to as a network slice, and a logical instance of a portion of CN 120 may be referred to as a network sub-slice. NFV architecture and infrastructure may be used to virtualize one or more network functions onto physical resources comprising a combination of industry-standard server hardware, storage hardware, or switches (alternatively performed by proprietary hardware). In other words, the NFV system may be used to perform a virtual or reconfigurable implementation of one or more EPC components / functions.

[0095] In general, the application server 130 may be an element that provides applications that use IP bearer resources with the core network (e.g., UMTS PS (packet service) domain, LTE PS data service, etc.). The application server 130 may also be configured to support one or more communication services for the UE 101 via the EPC 120 (e.g., VoIP (Voice-over-IP, Voice over Internet Protocol) sessions, PTT sessions, group communication sessions, social networking services, etc.).

[0096] In an embodiment, CN 120 may be a 5GC (referred to as “5GC 120” or the like), and RAN 110 may be connected to CN 120 via an NG interface 113. In an embodiment, NG interface 113 may be divided into two parts: an NG user plane (NG-U) interface 114, which carries traffic data between RAN node 111 and UPF (User Plane Function); and an S1 control plane (NG-C) interface 115, which is a signaling interface between RAN node 111 and AMF (Access and Mobility Management Function).

[0097] In an embodiment, CN 120 may be a 5G CN (referred to as "5GC 120", etc.), while in other embodiments, CN 120 may be an EPC. In the case where CN 120 is an EPC (referred to as "EPC 120", etc.), RAN 110 may be connected to CN 120 via an S1 interface 113. In an embodiment, S1 interface 113 may be divided into two parts: an S1 user plane (S1-U) interface 114, which carries traffic data between RAN node 111 and S-GW (serving gateway); and an S1-MME (S1-Mobility Management Entity of the control plane) interface 115, which is a signaling interface between multiple RAN nodes 111 and multiple MMEs. Figure 2 An exemplary architecture in which CN 120 is EPC 120 is shown.

[0098] Figure 2 FIG. 2 shows an exemplary architecture of a system 200 including a first CN 220 according to various embodiments. In this example, the system 200 may implement the LTE standard, wherein the CN 220 is a Figure 1 In addition, UE 201 may communicate with EPC 220 of CN 120. Figure 1 The UE 101 is the same as or similar to the UE 101, and the E-UTRAN 210 may be Figure 1 The CN 220 may be a RAN that is the same as or similar to the RAN 110 of the mobile station, and may include the RAN node 111 discussed previously. The CN 220 may include an MME 221, an S-GW 222, a P-GW (PDN Gateway) 223, an HSS (Home Subscriber Server) 224, and an SGSN (Serving GPRS Support Node) 225.

[0099] MME 221 may be similar in function to the control plane of a traditional SGSN, and may implement MM functions to keep track of the current location of UE 201. MME 221 may perform various MM procedures to manage mobility aspects in access, such as gateway selection and tracking area list management. MM (also referred to as "EPS MM" or "EMM" in E-UTRAN systems) may refer to all applicable procedures, methods, data stores, etc. for maintaining knowledge of the current location of UE 201, providing user identity confidentiality to users / subscribers, and / or performing other similar services. Each UE 201 and MME 221 may include an MM or EMM sublayer, and when the attachment procedure is successfully completed, an MM context may be established in UE 201 and MME 221. An MM context may be a data structure or database object that stores MM-related information of UE 201. The MME 221 may be coupled to the HSS 224 via an S6a reference point, to the SGSN 225 via an S3 reference point, and to an S-GW (Serving Gateway) 222 via an S11 reference point.

[0100] SGSN 225 may be a node that serves UE 201 by tracking the location of individual UE 201 and performing security functions. In addition, SGSN 225 may perform inter-EPC node signaling for mobility between 2G / 3G and E-UTRAN 3GPP access networks; PDN (Packet Data Network, Public Data Network) and S-GW selection, as specified by MME 221; handling of UE 201 time zone functions, as specified by MME 221; and MME selection for handover to E-UTRAN 3GPP access network. The S3 reference point between MME 221 and SGSN 225 may enable user and bearer information exchange for inter-3GPP access network mobility in an idle state and / or an active state.

[0101] The HSS 224 may include a database for network users, which includes subscription-related information for supporting network entities in handling communication sessions. The EPC 220 may include one or several HSSs 224, depending on the number of mobile subscribers, the capacity of the devices, the organization of the network, etc. For example, the HSS 224 may provide support for routing / roaming, authentication, authorization, naming / addressing solutions, location dependencies, etc. The S6a reference point between the HSS 224 and the MME 221 may enable the transfer of subscription and authentication data for authenticating / authorizing users to access the EPC 220 between the HSS 224 and the MME 221.

[0102] The S-GW 222 may terminate the S1 interface 113 ( Figure 2 The S-GW 222 may be a local mobility anchor for inter-RAN node handovers and may also provide an anchor for inter-3GPP mobility. Other responsibilities may include lawful interception, charging, and enforcement of certain policies. The S11 reference point between the S-GW 222 and the MME 221 may provide a control plane between the MME 221 and the S-GW 222. The S-GW 222 may be coupled to the P-GW 223 via the S5 reference point.

[0103] The P-GW 223 may terminate the SGi interface toward the PDN 230. The P-GW 223 may communicate with the PDN 230 via the IP interface 125 (see, e.g., Figure 1 ) routes data packets between EPC 220 and external networks such as a network including application server 130 (alternatively referred to as "AF" (application function)). In an embodiment, P-GW 223 can communicate via IP communication interface 125 (see, e.g., Figure 1) is communicatively coupled to an application server ( Figure 1 Application server 130 or Figure 2 The S5 reference point between the P-GW 223 and the S-GW 222 may provide user plane tunneling and tunnel management between the P-GW 223 and the S-GW 222. The S5 reference point may also be used for S-GW 222 relocation due to the mobility of the UE 201 and whether the S-GW 222 needs to be connected to a non-colocated P-GW 223 for the required PDN connectivity. The P-GW 223 may also include a node for policy enforcement and charging data collection (e.g., a PCEF (Policy and Charging Enforcement Function (not shown)). In addition, the SGi reference point between the P-GW 223 and the packet data network (PDN) 230 may be an operator-external public, private PDN, or an internal operator packet data network, for example, for providing IMS (IP Multimedia Subsystem) services. The P-GW 223 may be coupled to a PCRF (Policy Control and Charging Rules Function) 226 via a Gx reference point.

[0104] PCRF 226 is a policy and charging control element of EPC 220. In a non-roaming scenario, there may be a single PCRF 226 in a domestic public land mobile network (HPLMN) associated with an Internet Protocol Connectivity Access Network (IP-CAN) session of UE 201. In a roaming scenario with local traffic breakout, there may be two PCRFs associated with the IP-CAN session of UE 201: a domestic PCRF (H-PCRF) in the HPLMN and a visited PCRF (V-PCRF) in a visited public land mobile network (VPLMN). PCRF 226 may be communicatively coupled to application server 230 via P-GW 223. Application server 230 may signal PCRF 226 to indicate a new service flow and select appropriate QoS (quality of service) and charging parameters. PCRF 226 may configure the rule to a PCEF (not shown) with the appropriate TFT and QCI, which function starts QoS and charging as specified by application server 230. The Gx reference point between PCRF 226 and P-GW 223 may allow QoS policies and charging rules to be transferred from PCRF 226 to PCEF in P-GW 223. The Rx (accept, receive, receiver) reference point may reside between PDN 230 (or "AF 230") and PCRF 226.

[0105] Figure 3An example of infrastructure equipment 300 according to various embodiments is shown. The infrastructure equipment 300 (or "system 300") can be implemented as a base station, a radio head, a RAN node (such as the RAN node 111 and / or AP 106 shown and described previously), an application server 130, and / or any other element / device discussed herein. In other examples, the system 300 can be implemented in or by a UE.

[0106] System 300 includes: application circuit 305, baseband circuit 310, one or more radio front end modules (RFEM) 315, memory circuit 320, power management integrated circuit (PMIC) 325, power tee circuit 330, network controller circuit 335, network interface connector 340, satellite positioning circuit 345 and user interface 350. In some embodiments, device 300 may include additional elements, such as, for example, memory / storage, display, camera, sensor or input / output (I / O) interface. In other embodiments, these components may be included in more than one device. For example, the circuit may be included separately in more than one device for CRAN, vBBU or other similar implementations.

[0107] The application circuit 305 includes the following circuits such as, but not limited to: one or more processors (processor cores), cache memory, and one or more of the following: a low dropout regulator (LDO), an interrupt controller, a serial interface such as SPI, 2 C or general programmable serial interface module, real-time clock (RTC), timer-counter including interval timer and watchdog timer, general input / output (I / O or IO), memory card controller such as secure digital (SD) multimedia card (MMC) or similar products, universal serial bus (USB) interface, mobile industry processor interface (MIPI) interface and joint test access group (JTAG) test access port. The processor (or core) of application circuit 305 can be coupled with memory / storage element or can include memory / storage element, and can be configured to execute instructions stored in memory / storage element to enable various applications or operating systems to run on system 300. In some embodiments, memory / storage element can be on-chip memory circuit, which can include any suitable volatile and / or non-volatile memory, such as DRAM, SRAM, EPROM, EEPROM, flash memory, solid-state memory and / or any other type of memory device technology, such as those discussed herein.

[0108] The processor of the application circuit 305 may include, for example, one or more processor cores (CPU (CSI (Channel State Information) processing unit, Central Processing Unit), one or more application processors, one or more Graphics Processing Units (GPU), one or more Reduced Instruction Set Computing (RISC) processors, one or more Acorn RISC Machine (ARM) processors, one or more Complex Instruction Set Computing (CISC) processors, one or more Digital Signal Processors (DSP), one or more FPGA (Field Programmable Gate Array), one or more PLD, one or more ASIC, one or more microprocessors or controllers, or any suitable combination thereof. In some embodiments, the application circuit 305 may include or may be a dedicated processor / controller for operating according to various embodiments herein. As an example, the processor of the application circuit 305 may include one or more Intel or Processor: Advanced Micro Devices (AMD) Processor, Accelerated Processing Unit (APU) or processors; ARM-based processors licensed by ARM Holdings, Ltd., such as the ARM Cortex-A series processors provided by Cavium(TM), Inc. and MIPS-based designs from MIPS Technologies, Inc., such as the MIPS Warrior P-class processor; etc. In some embodiments, system 300 may not utilize application circuit 305, and instead may include a dedicated processor / controller to process IP data received, for example, from an EPC or 5GC.

[0109] In some implementations, the application circuit 305 may include one or more hardware accelerators, which may be microprocessors, programmable processing devices, and the like. The one or more hardware accelerators may include, for example, computer vision (CV) and / or deep learning (DL) accelerators. For example, the programmable processing device may be one or more field programmable devices (FPDs), such as field programmable gate arrays (FPGAs), and the like; programmable logic devices (PLDs), such as complex PLDs (CPLDs), high capacity PLDs (HCPLDs), and the like; ASICs, such as structured ASICs, and the like; programmable SoCs (systems on a chip) (PSoCs); and the like. In such embodiments, the circuitry of the application circuit 305 may include logic blocks or logic architectures, as well as other interconnected resources that may be programmed to perform various functions, such as the processes, methods, functions, and the like of the various embodiments discussed herein. In such an embodiment, the circuitry of the application circuit 305 may include a memory unit (e.g., an erasable programmable read-only memory (EPROM), an electrically erasable programmable read-only memory (EEPROM), a flash memory, a static memory (e.g., a static random access memory (SRAM), an anti-fuse, etc.)) for storing logic blocks, logic architectures, data, etc. in a look-up table (LUT), etc.

[0110] The baseband circuit 310 may be implemented, for example, as a solder-in substrate including one or more integrated circuits, a single packaged integrated circuit soldered to a main circuit board, or a multi-chip module containing two or more integrated circuits. Figure 5 The various hardware electronic components of baseband circuit 310 are discussed.

[0111] The user interface circuit 350 may include one or more user interfaces designed to enable a user to interact with the system 300 or a peripheral component interface designed to enable a peripheral component to interact with the system 300. The user interface may include, but is not limited to, one or more physical or virtual buttons (e.g., a reset button), one or more indicators (e.g., light emitting diodes (LEDs)), a physical keyboard or keypad, a mouse, a touch pad, a touch screen, a speaker or other audio transmitting device, a microphone, a printer, a scanner, a headset, a display screen or display device, etc. The peripheral component interface may include, but is not limited to, a non-volatile memory port, a universal serial bus (USB) port, an audio jack, a power interface, etc.

[0112] The radio front end module (RFEM) 315 may include a millimeter wave (mmWave) RFEM and one or more sub-millimeter wave radio frequency integrated circuits (RFICs). In some implementations, the one or more sub-millimeter wave RFICs may be physically separated from the mmWave RFEM. The RFIC may include connections to one or more antennas or antenna arrays (see, e.g., below). Figure 5Antenna array 5111), and the RFEM can be connected to multiple antennas. In an alternative embodiment, both millimeter wave and sub-millimeter wave radio functions can be implemented in the same physical RFEM 315 combining both millimeter wave antennas and sub-millimeter waves.

[0113] The memory circuit 320 may include one or more of the following: a volatile memory including a dynamic random access memory (DRAM) and / or a synchronous dynamic random access memory (SDRAM), a non-volatile memory (NVM) including a high-speed electrically erasable memory (commonly referred to as a "flash memory"), a phase change random access memory (PRAM), a magnetoresistive random access memory (MRAM), etc., and may be combined with and The memory circuit 320 may be implemented as one or more of: a solder-in package integrated circuit, a socket memory module, and a plug-in memory card.

[0114] The PMIC 325 may include a voltage regulator, a surge protector, a power alarm detection circuit, and one or more backup power sources, such as a battery or capacitor. The power alarm detection circuit may detect one or more of a brownout (undervoltage) and a surge (overvoltage) condition. The power tee circuit 330 may provide power drawn from a network cable to provide both power and data connections for the infrastructure equipment 300 using a single cable.

[0115] The network controller circuit 335 may provide a connection to the network using a standard network interface protocol such as Ethernet, Ethernet based on a GRE tunnel, Ethernet based on a multi-protocol label switching (MPLS), or some other suitable protocol. A physical connection may be used to provide a network connection to / from the infrastructure equipment 300 via a network interface connector 340, which may be an electrical connection (commonly referred to as a "copper interconnect"), an optical connection, or a wireless connection. The network controller circuit 335 may include one or more dedicated processors and / or FPGAs for communicating using one or more of the aforementioned protocols. In some specific implementations, the network controller circuit 335 may include multiple controllers for providing connections to other networks using the same or different protocols.

[0116] The positioning circuit 345 includes circuits for receiving and decoding signals transmitted / broadcasted by a positioning network of a global satellite navigation system (or GNSS). Examples of navigation satellite constellations (or GNSS) include the United States' Global Positioning System (GPS), Russia's Global Navigation System (GLONASS), the European Union's Galileo system, China's Beidou Navigation Satellite System, regional navigation systems or GNSS augmentation systems (e.g., using the Indian constellation (NAVIC), Japan's Quasi-Zenith Satellite System (QZSS), France's Doppler Orbit Chart and Satellite Integrated Radio Positioning (DORIS), etc. for navigation), etc. The positioning circuit 345 may include various hardware elements (e.g., including hardware devices such as switches, filters, amplifiers, antenna elements, etc. for facilitating OTA (over-the-air) communications) to communicate with components of the positioning network such as navigation satellite constellation nodes. In some embodiments, the positioning circuit 345 may include a micro technology (micro PNT) IC for positioning, navigation, and timing that uses a master timing clock to perform position tracking / estimation without GNSS assistance. The positioning circuit 345 may also be part of or interact with the baseband circuit 310 and / or RFEM 315 to communicate with nodes and components of the positioning network. The positioning circuit 345 may also provide location data and / or time data to the application circuit 305, which may use the data to synchronize operations with various infrastructure (e.g., RAN node 111, etc.), etc.

[0117] Figure 3 The components shown may communicate with each other using interface circuitry that may include any number of bus and / or interconnect (IX) technologies, such as Industry Standard Architecture (ISA), Extended ISA (EISA), Peripheral Component Interconnect (PCI), Peripheral Component Interconnect Extended (PCIx), PCI express (PCIe), or any number of other technologies. The bus / IX may be a proprietary bus, such as used in SoC-based systems. Other bus / IX systems may be included, such as I 2 C interface, SPI interface, point-to-point interface and power bus, etc.

[0118] Figure 4 An example of a platform 400 (or "device 400") according to various embodiments is shown. In an embodiment, the computer platform 400 may be suitable for use as a UE 101, 102, 201, an application server 130, and / or any other element / device discussed herein. The platform 400 may include any combination of components shown in the example. The components of the platform 400 may be implemented as an integrated circuit (IC), a portion thereof, a discrete electronic device, or other modules, logic, hardware, software, firmware, or a combination thereof suitable for use in the computer platform 400, or as components otherwise incorporated within a chassis of a larger system. Figure 4The block diagram is intended to show a high-level view of the components of computer platform 400. 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 implementations.

[0119] Application circuit 405 includes circuits such as, but not limited to, one or more processors (or processor cores), cache memory, and LDO, interrupt controller, serial interface (such as SPI), I 2 The processor (or core) of the application circuit 405 may be coupled to or may include a memory / storage element and may be configured to execute instructions stored in the memory / storage element to enable various applications or operating systems to run on the system 400. In some embodiments, the memory / storage element may be an on-chip memory circuit that may include any suitable volatile and / or non-volatile memory, such as DRAM, SRAM, EPROM, EEPROM, flash memory, solid-state memory, and / or any other type of memory device technology, such as those discussed herein.

[0120] The processor of the application circuit 305 may include, for example, one or more processor cores, one or more application processors, one or more GPUs, one or more RISC processors, one or more ARM processors, one or more CISC processors, one or more DSPs, one or more FPGAs, one or more PLDs, one or more ASICs, one or more microprocessors or controllers, multi-threaded processors, ultra-low voltage processors, embedded processors, some other known processing elements, or any suitable combination thereof. In some embodiments, the application circuit 305 may include or may be a dedicated processor / controller for operating according to various embodiments herein.

[0121] As an example, the processor of the application circuit 405 may include a processor based on Architecture TM Processors such as Quark TM 、Atom TM , i3, i5, i7 or MCU class processors, or available from Santa Clara, CA The processor of application circuit 405 may also be one or more of the following: Advanced Micro Devices (AMD) Processor or Accelerated Processing Unit (APU); from Inc.'s A5-A9 processors, Snapdragon by Technologies, Inc. TM Processor, Texas Instruments, Open Multimedia Applications Platform(OMAP) TM processors; MIPS-based designs from MIPS Technologies, Inc., such as MIPS Warrior-class, Warrior I-class, and Warrior P-class processors; ARM-based designs licensed from ARM Holdings, Ltd., such as ARM Cortex-A, Cortex-R, and Cortex-M series processors; etc. In some implementations, the application circuit 405 can be part of a system on a chip (SoC), in which the application circuit 405 and other components are formed as a single integrated circuit or a single package, such as company( Edison Corporation TM or Galileo TM SoC board.

[0122] Additionally or alternatively, the application circuit 405 may include circuits such as, but not limited to, one or more field programmable devices (FPDs) such as FPGAs, etc.; programmable logic devices (PLDs) such as complex PLDs (CPLDs), high capacity PLDs (HCPLDs), etc.; ASICs such as structured ASICs, etc.; programmable SoCs (PSoCs); etc. In such embodiments, the circuits of the application circuit 405 may include logic blocks or logic structures, and other interconnected resources that may be programmed to perform various functions such as the processes, methods, functions, etc. of the various embodiments discussed herein. In such embodiments, the circuits of the application circuit 405 may include memory cells (e.g., erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), flash memory, static memory (e.g., static random access memory (SRAM), anti-fuse, etc.)) for storing logic blocks, logic structures, data, etc. in a lookup table (LUT), etc.

[0123] Baseband circuit 410 may be implemented, for example, as a solder-in substrate including one or more integrated circuits, a single packaged integrated circuit soldered to a main circuit board, or a multi-chip module containing two or more integrated circuits. Figure 5 The various hardware electronic components of baseband circuit 410 are discussed.

[0124] The RFEM 415 may include a millimeter wave (mm Wave) RFEM and one or more sub-millimeter wave radio frequency integrated circuits (RFICs). In some implementations, the one or more sub-millimeter wave RFICs may be physically separated from the mm Wave RFEM. The RFIC may include connections to one or more antennas or antenna arrays (see, e.g., below). Figure 5 Antenna array 5111), and RFEM can be connected to multiple antennas. In an alternative implementation, both millimeter wave and sub-millimeter wave radio functions can be implemented in the same physical RFEM 415 combining both millimeter wave antennas and sub-millimeter waves.

[0125] The memory circuit 420 may include any number and type of memory devices for providing a fixed amount of system memory. For example, the memory circuit 420 may include one or more of the following: volatile memory, including random access memory (RAM), dynamic RAM (DRAM) and / or synchronous dynamic RAM (SDRAM); and non-volatile memory, including high-speed electrically erasable memory (commonly referred to as flash memory), phase change random access memory (PRAM), magnetoresistive random access memory (MRAM), etc. The memory circuit 420 may be developed according to the Joint Electron Device Engineering Council (JEDEC) based low power double data rate (LPDDR) design such as LPDDR2, LPDDR3, LPDDR4, etc. The memory circuit 420 may be implemented as one or more of the following: a solder-in package integrated circuit, a single die package (SDP), a dual die package (DDP) or a quad die package (Q17P), a socketed memory module, a dual in-line memory module (DIMM) including a micro DIMM or a mini DIMM, and / or soldered to a motherboard via a ball grid array (BGA). In a low-power implementation, the memory circuit 420 may be an on-chip memory or register associated with the application circuit 405. To provide persistent storage of information such as data, applications, operating systems, etc., the memory circuit 420 may include one or more mass storage devices, which may include, among others, a solid-state disk drive (SSDD), a hard disk drive (HDD), a micro HDD, a resistive change memory, a phase change memory, a holographic memory, or a chemical memory. For example, the computer platform 400 may be combined with a memory device obtained from and Three-dimensional (3D) cross-point (XPOINT) memory.

[0126] Removable memory circuitry 423 may include devices, circuitry, housings / casings, ports or receptacles, etc., for coupling portable data storage devices to platform 400. These portable data storage devices may be used for mass storage, and may include, for example, flash memory cards (e.g., Secure Digital (SD) cards, micro SD cards, xD picture cards, etc.), as well as USB flash drives, optical disks, external HDDs, etc.

[0127] The platform 400 may further include an interface circuit (not shown) for connecting external devices to the platform 400. External devices connected to the platform 400 via the interface circuit include a sensor circuit 421 and an electromechanical component (EMC) 422, and a removable memory device coupled to a removable memory circuit 423.

[0128] Sensor circuitry 421 comprises a device, module, or subsystem that is intended to detect events or changes in its environment, and to send information about the detected events (sensor data) to some other device, module, subsystem, etc. Examples of such sensors include, among others: an inertial measurement unit (IMU) including an accelerometer, a gyroscope, and / or a magnetometer; a microelectromechanical system (MEMS) or a nanoelectromechanical system (NEMS) including a three-axis accelerometer, a three-axis gyroscope, and / or a magnetometer; a level sensor; a flow sensor; a temperature sensor (e.g., a thermistor); a pressure sensor; a barometric pressure sensor; a gravity meter; an altimeter; an image capture device (e.g., a camera or a lensless aperture); a light detection and ranging (LiDAR) sensor; a proximity sensor (e.g., an infrared radiation detector, etc.), a depth sensor, an ambient light sensor, an ultrasonic transceiver; a microphone or other similar audio capture device; etc.

[0129] The EMC 422 includes devices, modules or subsystems that are intended to enable the platform 400 to change its state, position and / or orientation or to move or control a mechanism or (sub) system. In addition, the EMC 422 may be configured to generate messages / signaling and send messages / signaling to other components of the platform 400 to indicate the current state of the EMC 422. The EMC 422 includes one or more power switches, relays (including electromechanical relays (EMRs) and / or solid-state relays (SSRs)), actuators (e.g., valve actuators, etc.), audible sound generators, visual warning devices, motors (e.g., DC (direct current) motors, stepper motors, etc.), wheels, thrusters, propellers, claws, clamps, hooks and / or other similar electromechanical components. In an embodiment, the platform 400 is configured to operate one or more EMCs 422 based on one or more capture events and / or instructions or control signals received from a service provider and / or various clients.

[0130] In some specific implementations, the interface circuit may connect the platform 400 to the positioning circuit 445. The positioning circuit 445 includes a circuit for receiving and decoding signals transmitted / broadcasted by the positioning network of the GNSS. Examples of navigation satellite constellations (or GNSS) may include the GPS of the United States, the GLONASS of Russia, the Galileo system of the European Union, the Beidou navigation satellite system of China, regional navigation systems or GNSS augmentation systems (e.g., NAVIC, QZSS of Japan, DORIS of France, etc.), etc. The positioning circuit 445 includes various hardware elements (e.g., including hardware devices such as switches, filters, amplifiers, antenna elements, etc. for facilitating OTA communication) to communicate with components of the positioning network such as navigation satellite constellation nodes. In some embodiments, the positioning circuit 445 may include a micro PNT IC that uses a master timing clock to perform position tracking / estimation without GNSS assistance. The positioning circuit 445 may also be part of the baseband circuit 310 and / or the RFEM 415 or interact with it to communicate with nodes and components of the positioning network. Positioning circuitry 445 may also provide position data and / or time data to application circuitry 405, which may use the data to synchronize operations with various infrastructure (e.g., radio base stations) for use in turn-by-turn navigation applications, etc.

[0131] In some implementations, the interface circuit may connect the platform 400 with a near field communication (NFC) circuit 440. The NFC circuit 440 is configured to provide contactless short-range communication based on the radio frequency identification (RFID) standard, wherein magnetic field induction is used to enable communication between the NFC circuit 440 and an NFC-enabled device (e.g., an "NFC touch point") external to the platform 400. The NFC circuit 440 includes an NFC controller coupled to an antenna element and a processor coupled to the NFC controller. The NFC controller may be a chip / IC that provides NFC functionality to the NFC circuit 440 by executing an NFC controller firmware and an NFC stack. The NFC stack may be executed by the processor to control the NFC controller, and the NFC controller firmware may be executed by the NFC controller to control the antenna element to transmit a short-range RF signal. The RF signal may power a passive NFC tag (e.g., a microchip embedded in a sticker or wristband) to transfer stored data to the NFC circuit 440, or initiate data transfer between the NFC circuit 440 and another active NFC device (e.g., a smartphone or an NFC-enabled POS terminal) proximate to the platform 400.

[0132] The driver circuit 446 may include software and hardware elements for controlling specific devices embedded in, attached to, or otherwise communicatively coupled to the platform 400. The driver circuit 446 may include various drivers to allow other components of the platform 400 to interact with or control various input / output (I / O) devices that may be present in or connected to the platform 400. For example, the driver circuit 446 may include: a display driver for controlling and allowing access to a display device, a touch screen driver for controlling and allowing access to a touch screen interface of the platform 400, a sensor driver for obtaining sensor readings of the sensor circuit 421 and controlling and allowing access to the sensor circuit 421, an EMC driver for obtaining an actuator position of the EMC 422 and / or controlling and allowing access to the EMC 422, 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.

[0133] A power management integrated circuit (PMIC) 425 (also referred to as “power management circuit 425”) may manage power provided to various components of the platform 400. Specifically, the PMIC 425 may control power selection, voltage scaling, battery charging, or DC-DC conversion with respect to the baseband circuit 410. When the platform 400 is capable of being powered by a battery 430, for example, when the device is included in a UE 101, 102, 201, a PMIC 425 may typically be included.

[0134] In some embodiments, the PMIC 425 may control or otherwise be part of various power saving mechanisms of the platform 400. For example, if the platform 400 is in the RRC_Connected state, in which the platform is still connected to the RAN node because it expects to receive traffic soon, then after a period of inactivity, the platform may enter a state known as discontinuous reception mode (DRX). During this state, the platform 400 may be powered off for short time intervals, thereby saving power. If there is no data traffic activity for an extended period of time, the platform 400 may transition to the RRC_Idle state, in which the platform is disconnected from the network and no operations such as channel quality feedback, handover, etc. are performed. The platform 400 enters an extremely low power state and performs paging, in which the platform wakes up periodically to listen to the network and then powers off again. The platform 400 may not receive data in this state; in order to receive data, the platform must transition back to the RRC_Connected state. Additional power saving modes may prevent the device from using the network for longer than the paging interval (ranging from a few seconds to a few hours). During this time, the device is completely unable to connect to the network and can be completely powered off. Any data sent during this time will be significantly delayed, and it is assumed that the delay is acceptable.

[0135] The battery 430 can power the platform 400, but in some examples, the platform 400 can be mounted in a fixed location and can have a power source coupled to a power grid. The battery 430 can 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 implementations, such as in V2X applications, the battery 430 can be a typical lead-acid car battery.

[0136] In some implementations, the battery 430 may be a "smart battery" that includes or is coupled to a battery management system (BMS) or a battery monitoring integrated circuit. The BMS may be included in the platform 400 to track the state of charge (SoCh) of the battery 430. The BMS may be used to monitor other parameters of the battery 430 to provide fault predictions, such as the state of health (SoH) and state of function (SoF) of the battery 430. The BMS may transmit information about the battery 430 to the application circuit 405 or other components of the platform 400. The BMS may also include an analog-to-digital (ADC) converter that allows the application circuit 405 to directly monitor the voltage of the battery 430 or the current from the battery 430. The battery parameters may be used to determine actions that the platform 400 may perform, such as transmission frequency, network operation, sensing frequency, etc.

[0137] A power block or other power source coupled to the grid can be coupled to the BMS to charge the battery 430. In some examples, the power block XS30 can be replaced with a wireless power receiver to obtain power wirelessly, for example, through a loop antenna in the computer platform 400. In these examples, a wireless battery charging circuit can be included in the BMS. The specific charging circuit selected can depend on the size of the battery 430 and therefore the current required. Charging can be performed using the aviation fuel standard published by the Aviation Fuel Alliance, the Qi wireless charging standard published by the Wireless Power Alliance, or the Rezence charging standard published by the Wireless Power Alliance.

[0138] The user interface circuit 450 includes various input / output (I / O) devices present in or connected to the platform 400, and includes one or more user interfaces designed to implement user interaction with the platform 400 and / or a peripheral component interface designed to implement interaction with the peripheral components of the platform 400. The user interface circuit 450 includes input device circuits and output device circuits. The input device circuit includes any physical or virtual means for accepting input, including, in particular, one or more physical or virtual buttons (e.g., a reset button), a physical keyboard, a keypad, a mouse, a touchpad, a touch screen, a microphone, a scanner, a headset, etc. The output device circuit includes any physical or virtual means for displaying information or otherwise conveying information (such as sensor readings, actuator positions, or other similar information). The output device circuitry may include any number and / or combination of audio or visual displays, including, among other things, one or more simple visual outputs / indicators (e.g., binary status indicators (e.g., light emitting diodes (LEDs)) and multi-character visual outputs, or more complex outputs such as display devices or touch screens (e.g., liquid crystal displays (LCDs), LED displays, quantum dot displays, projectors, etc.), where outputs of characters, graphics, multimedia objects, etc. are generated or produced by the operation of the platform 400. The output device circuitry may also include speakers or other audio emitting devices, printers, etc. In some embodiments, the sensor circuitry 421 may be used as an input device circuitry (e.g., an image capture device, a motion capture device, etc.) and one or more EMCs may be used as output device circuitry (e.g., an actuator for providing tactile feedback, etc.). In another example, an NFC circuit may be included to read an electronic tag and / or connect to another NFC-enabled device, the NFC circuitry including an NFC controller and a processing device coupled to an antenna element. The peripheral component interfaces may include, but are not limited to, non-volatile memory ports, USB ports, audio jacks, power interfaces, etc.

[0139] Although not shown, the components of platform 400 may communicate with each other using a suitable bus or interconnect (IX) technology, which may include any number of technologies, including ISA, EISA, PCI, PCIx, PCIe, a time-triggered protocol (TTP) system, a FlexRay system, or any number of other technologies. The bus / IX may be a proprietary bus / IX, such as used in SoC-based systems. Other bus / IX systems, such as I 2 C interface, SPI interface, point-to-point interface and power bus, etc.

[0140] Figure 5 Exemplary components of a baseband circuit 5110 and a radio front end module (RFEM) 5115 are illustrated according to various embodiments. The baseband circuit 5110 corresponds to Figure 3 and Figure 4 Baseband circuits 310 and 410. RFEM 5115 corresponds to Figure 3 and Figure 4 RFEM 315 and 415. As shown, RFEM 5115 may include radio frequency (RF) circuit 5106, front end module (FEM) circuit 5108, and antenna array 5111 coupled together at least as shown.

[0141] The baseband circuit 5110 includes circuits and / or control logic components that are configured to execute various radio / network protocols and radio control functions that enable communication with one or more radio networks via the RF circuit 5106. The radio control functions may include, but are not limited to, signal modulation / demodulation, encoding / decoding, radio frequency shifting, etc. In some embodiments, the modulation / demodulation circuit of the baseband circuit 5110 may include fast Fourier transform (FFT), precoding, or constellation mapping / demapping functions. In some embodiments, the encoding / decoding circuit of the baseband circuit 5110 may include convolution, tail-biting convolution, turbo, Viterbi, or low-density parity check (LDPC) encoder / decoder functions. The implementation of the modulation / demodulation and encoder / decoder functions is not limited to these examples, and may include other suitable functions in other embodiments. The baseband circuit 5110 is configured to process baseband signals received from the receive signal path of the RF circuit 5106 and generate baseband signals for the transmit signal path of the RF circuit 5106. The baseband circuit 5110 is configured to communicate with the application circuit 305 / 405 (see Figure 3 and Figure 4 ) to generate and process baseband signals and control the operation of RF circuit 5106. Baseband circuit 5110 can handle various radio control functions.

[0142] The aforementioned circuits and / or control logic components of the baseband circuit 5110 may include one or more single-core or multi-core processors. For example, the one or more processors may include a 3G baseband processor 5104A, a 4G / LTE baseband processor 5104B, a 5G / NR baseband processor 5104C, or some other baseband processors 5104D for other existing generations, generations under development, or generations to be developed in the future (e.g., the sixth generation (6G), etc.). In other embodiments, some or all of the functions of the baseband processors 5104A-D may be included in a module stored in the memory 5104G and may be executed via a central processing unit (CPU) 5104E. In other embodiments, some or all of the functions of the baseband processors 5104A-D may be provided as a hardware accelerator (e.g., FPGA, ASIC, etc.) loaded with an appropriate bitstream or logic block stored in a corresponding memory unit. In various embodiments, the memory 5104G may store program code of a real-time OS (RTOS), which, when executed by the CPU 5104E (or other baseband processor), will enable the CPU 5104E (or other baseband processor) to manage resources of the baseband circuit 5110, schedule tasks, etc. Examples of RTOS may include: Operating System Embedded (OSE) provided TM , by Mentor Nucleus RTOS provided TM , by Mentor Versatile Real-TimeExecutive (VRTX) provided by Express Provided by ThreadX TM ,Depend on FreeRTOS and REX OS provided by Open Kernel (OK) OKL4 provided, or any other suitable RTOS, such as those discussed herein. In addition, the baseband circuit 5110 includes one or more audio digital signal processors (DSPs) 5104F. The audio DSP 5104F includes elements for compression / decompression and echo cancellation, and may include other suitable processing elements in other embodiments.

[0143] In some embodiments, each of the processors 5104A-5104E includes a corresponding memory interface to send data to / receive data from the memory 5104G. The baseband circuit 5110 may also include one or more interfaces for communicatively coupling to other circuits / devices, such as an interface for sending data to / receiving data from a memory external to the baseband circuit 5110; an interface for sending data to / receiving data from a memory external to the baseband circuit 5110; Figures 3 to 5 An application circuit interface for sending data to / receiving data from the application circuit 305 / 405; Figure 5 RF circuit 5106 to send data / receive data from the RF circuit RF circuit interface; for receiving data from one or more wireless hardware elements (e.g., near field communication (NFC) components, Low power consumption components, components, etc.) to send data / receive data from these wireless hardware elements; and a power management interface for sending power or control signals to / receiving power or control signals from the PMIC 425.

[0144] In an alternative embodiment (which can be combined with the above embodiment), the baseband circuit 5110 includes one or more digital baseband systems, which are coupled to each other and to the CPU subsystem, audio subsystem and interface subsystem via an interconnect subsystem. The digital baseband subsystem can also be coupled to the digital baseband interface and the mixed signal baseband subsystem via another interconnect subsystem. Each of the interconnect subsystems may include a bus system, a point-to-point connector, a network on chip (NOC) structure and / or some other suitable bus or interconnect technology, such as those discussed herein. The audio subsystem may include a DSP circuit, a buffer memory, a program memory, a voice processing accelerator circuit, a data converter circuit such as an analog-to-digital converter circuit and a digital-to-analog converter circuit, an analog circuit including one or more of an amplifier and a filter, and / or other similar components. In one aspect of the present disclosure, the baseband circuit 5110 may include a protocol processing circuit with one or more control circuit instances (not shown) to provide control functions for the digital baseband circuit and / or the radio frequency circuit (e.g., the radio front end module 5115).

[0145] although Figure 5Not shown, but in some embodiments, the baseband circuit 5110 includes various processing devices (e.g., "multi-protocol baseband processor" or "protocol processing circuit") to operate one or more wireless communication protocols and various processing devices to implement PHY layer functions. In these embodiments, the PHY layer functions include the aforementioned radio control functions. In these embodiments, the protocol processing circuit operates or implements various protocol layers / entities of one or more wireless communication protocols. In a first example, when the baseband circuit 5110 and / or the RF circuit 5106 are part of a millimeter wave communication circuit or some other suitable cellular communication circuit, the protocol processing circuit may operate LTE protocol entities and / or 5G / NR protocol entities. In a first example, the protocol processing circuit will operate MAC, RLC, PDCP (packet data convergence protocol, packet data convergence protocol layer), SDAP (service data adaptation protocol, service data adaptation protocol layer), RRC and NAS functions. In a second example, when the baseband circuit 5110 and / or the RF circuit 5106 are part of a Wi-Fi communication system, the protocol processing circuit may operate one or more IEEE-based protocols. In a second example, the protocol processing circuit will operate the Wi-Fi MAC and logical link control (LLC) functions. The protocol processing circuit may include one or more memory structures (e.g., 5104G) for storing program code and data for operating protocol functions, and one or more processing cores for executing program code and performing various operations using data. The baseband circuit 5110 may also support radio communications for more than one wireless protocol.

[0146] The various hardware elements of the baseband circuit 5110 discussed herein may be implemented as, for example, a solder-in substrate, which includes one or more integrated circuits (ICs), a single packaged integrated circuit soldered to a main circuit board, or a multi-chip module containing two or more ICs. In one example, the components of the baseband circuit 5110 may be appropriately combined in a single chip or a single chipset, or arranged on the same circuit board. In another example, some or all of the components of the baseband circuit 5110 and the RF circuit 5106 may be implemented together, such as, for example, a system on a chip (SoC) or a system-level package (SiP). In another example, some or all of the components of the baseband circuit 5110 may be implemented as a separate SoC coupled to the RF circuit 5106 (or multiple instances of the RF circuit 5106) in communication. In yet another example, some or all of the components of the baseband circuit 5110 and the application circuit 305 / 405 may be implemented together as a separate SoC (e.g., a "multi-chip package") mounted to the same circuit board.

[0147] In some embodiments, the baseband circuit 5110 may provide communications compatible with one or more radio technologies. For example, in some embodiments, the baseband circuit 5110 may support communications with E-UTRAN or other WMANs (wireless metropolitan area networks), WLANs, WPANs (wireless personal area networks). Embodiments in which the baseband circuit 5110 is configured to support radio communications of more than one wireless protocol may be referred to as multi-mode baseband circuits.

[0148] The RF circuit 5106 may enable communication with a wireless network through a non-solid medium using modulated electromagnetic radiation. In various embodiments, the RF circuit 5106 may include switches, filters, amplifiers, etc. to facilitate communication with the wireless network. The RF circuit 5106 may include a receive signal path, which may include circuits for down-converting RF signals received from the FEM circuit 5108 and providing baseband signals to the baseband circuit 5110. The RF circuit 5106 may also include a transmit signal path, which may include circuits for up-converting baseband signals provided by the baseband circuit 5110 and providing RF output signals for transmission to the FEM circuit 5108.

[0149] In some embodiments, the receive signal path of the RF circuit 5106 may include a mixer circuit 5106a, an amplifier circuit 5106b, and a filter circuit 5106c. In some embodiments, the transmit signal path of the RF circuit 5106 may include a filter circuit 5106c and a mixer circuit 5106a. The RF circuit 5106 may also include a synthesizer circuit 5106d for synthesizing frequencies used by the mixer circuit 5106a for the receive signal path and the transmit signal path. In some embodiments, the mixer circuit 5106a of the receive signal path may be configured to down-convert the RF signal received from the FEM circuit 5108 based on the synthesized frequency provided by the synthesizer circuit 5106d. The amplifier circuit 5106b may be configured to amplify the down-converted signal, and the filter circuit 5106c may be a low pass filter (LPF) or a band pass filter (BPF) configured to remove unwanted signals from the down-converted signal to generate an output baseband signal. The output baseband signal may be provided to baseband circuit 5110 for further processing. In some embodiments, although this is not required, the output baseband signal may be a zero frequency baseband signal. In some embodiments, the mixer circuit 5106a of the receive signal path may include a passive mixer, but the scope of the embodiments is not limited in this regard.

[0150] In some embodiments, mixer circuit 5106a of the transmit signal path may be configured to upconvert an input baseband signal based on a synthesized frequency provided by synthesizer circuit 5106d to generate an RF output signal for FEM circuit 5108. The baseband signal may be provided by baseband circuit 5110 and may be filtered by filter circuit 5106c.

[0151] In some embodiments, the mixer circuit 5106a of the receive signal path and the mixer circuit 5106a of the transmit signal path may include two or more mixers and may be arranged for orthogonal down-conversion and up-conversion, respectively. In some embodiments, the mixer circuit 5106a of the receive signal path and the mixer circuit 5106a of the transmit signal path may include two or more mixers and may be arranged for image suppression (e.g., Hartley image suppression). In some embodiments, the mixer circuit 5106a of the receive signal path and the mixer circuit 5106a of the transmit signal path may be arranged for direct down-conversion and direct up-conversion, respectively. In some embodiments, the mixer circuit 5106a of the receive signal path and the mixer circuit 5106a of the transmit signal path may be configured for superheterodyne operation.

[0152] In some embodiments, the output baseband signal and the input baseband signal may be analog baseband signals, although the scope of the embodiments is not limited in this respect. In some alternative embodiments, the output baseband signal and the input baseband signal may be digital baseband signals. In these alternative embodiments, the RF circuit 5106 may include an analog-to-digital converter (ADC) and a digital-to-analog converter (DAC) circuit, and the baseband circuit 5110 may include a digital baseband interface to communicate with the RF circuit 5106.

[0153] In some dual-mode embodiments, separate radio IC circuits may be provided to process signals for each spectrum, although the scope of the embodiments is not limited in this respect.

[0154] In some embodiments, synthesizer circuit 5106d can be a fractional-N synthesizer or a fractional-N / N+1 synthesizer, but the scope of the embodiments is not limited in this respect, as other types of frequency synthesizers may also be suitable. For example, synthesizer circuit 5106d can be a delta-sigma synthesizer, a frequency multiplier, or a synthesizer including a phase-locked loop with a frequency divider.

[0155] Synthesizer circuit 5106d may be configured to synthesize an output frequency based on a frequency input and a divider control input for use by mixer circuit 5106a of RF circuit 5106. In some embodiments, synthesizer circuit 5106d may be a fractional-N / N+1 synthesizer.

[0156] In some embodiments, the frequency input may be provided by a voltage controlled oscillator (VCO), although this is not required. The divider control input may be provided by the baseband circuit 5110 or the application circuit 305 / 405 according to the desired output frequency. In some embodiments, the divider control input (e.g., N) may be determined from a lookup table based on the channel indicated by the application circuit 305 / 405.

[0157] The synthesizer circuit 5106d of the RF circuit 5106 may include a frequency divider, a delay locked loop (DLL), a multiplexer, and a phase accumulator. In some embodiments, the frequency divider may be a dual-mode frequency divider (DMD), and the phase accumulator may be a digital phase accumulator (DPA). In some embodiments, the DMD may be configured to divide the input signal by N or N+1 (e.g., based on a carry) to provide a fractional division ratio. In some example embodiments, the DLL may include a cascaded, tunable, delay element, a phase detector, a charge pump, and a set of D-type flip-flops. In these embodiments, the delay element may be configured to divide the VCO cycle into Nd equal phase groups, where Nd is the number of delay elements in the delay line. In this way, the DLL provides negative feedback to help ensure that the total delay through the delay line is one VCO cycle.

[0158] In some embodiments, the synthesizer circuit 5106d can be configured to generate a carrier frequency as an output frequency, while in other embodiments, the output frequency can be a multiple of the carrier frequency (e.g., twice the carrier frequency, four times the carrier frequency) and can be used with a quadrature generator and divider circuit to generate multiple signals with multiple different phases relative to each other at the carrier frequency. In some embodiments, the output frequency can be the LO frequency (fLO). In some embodiments, the RF circuit 5106 can include an IQ / polarity converter.

[0159] The FEM circuitry 5108 may include a receive signal path that may include circuitry configured to operate on RF signals received from the antenna array 5111, amplify the received signals, and provide an amplified version of the received signals to the RF circuitry 5106 for further processing. The FEM circuitry 5108 may also include a transmit signal path that may include circuitry configured to amplify transmit signals provided by the RF circuitry 5106 for transmission by one or more antenna elements in the antenna array 5111. In various embodiments, amplification by the transmit or receive signal path may be accomplished only in the RF circuitry 5106, only in the FEM circuitry 5108, or in both the RF circuitry 5106 and the FEM circuitry 5108.

[0160] In some embodiments, the FEM circuit 5108 may include a TX (transmit, transmit, transmitter) / RX switch to switch between transmit mode and receive mode operation. The FEM circuit 5108 may include a receive signal path and a transmit signal path. The receive signal path of the FEM circuit 5108 may include an LNA to amplify the received RF signal and provide the amplified received RF signal as an output (e.g., to the RF circuit 5106). The transmit signal path of the FEM circuit 5108 may include a power amplifier (PA) for amplifying the input RF signal (e.g., provided by the RF circuit 5106), and one or more filters for generating an RF signal for subsequent transmission by one or more antenna elements of the antenna array 5111.

[0161] The antenna array 5111 includes one or more antenna elements, each of which is configured to convert an electrical signal into a radio wave to travel through the air and convert the received radio wave into an electrical signal. For example, a digital baseband signal provided by the baseband circuit 5110 is converted into an analog RF signal (e.g., a modulated waveform), which is amplified and transmitted via the antenna elements of the antenna array 5111 including one or more antenna elements (not shown). The antenna elements may be omnidirectional, directional, or a combination thereof. The antenna elements may be formed into a variety of arrangements as known and / or discussed herein. The antenna array 5111 may include a microstrip antenna or a printed antenna fabricated on the surface of one or more printed circuit boards. The antenna array 5111 may be formed as a patch of metal foil of various shapes (e.g., a patch antenna) and may be coupled to the RF circuit 5106 and / or the FEM circuit 5108 using a metal transmission line or the like.

[0162] The processor of the application circuit 305 / 405 and the processor of the baseband circuit 5110 can be used to execute elements of one or more instances of the protocol stack. For example, the processor of the baseband circuit 5110 can be used alone or in combination to perform layer 3, layer 2, or layer 1 functions, while the processor of the application circuit 305 / 405 can utilize data received from these layers (e.g., packet data) and further perform layer 4 functions (e.g., TCP (Transport Communication Protocol) and UDP layers). As mentioned herein, layer 3 may include an RRC layer, which will be described in further detail below. As mentioned herein, layer 2 may include a MAC layer, an RLC layer, and a PDCP layer, which will be described in further detail below. As mentioned herein, layer 1 may include a PHY layer of a UE / RAN node, which will be described in further detail below.

[0163] Figure 6 is a block diagram illustrating components capable of reading instructions from a machine-readable or computer-readable medium (e.g., a non-transitory machine-readable storage medium) and capable of performing any one or more of the methods discussed herein, according to some exemplary embodiments. Specifically, Figure 6 A schematic diagram of hardware resources 600 is shown, including one or more processors (or processor cores) 610, one or more memory / storage devices 620, and one or more communication resources 630, each of which may be communicatively coupled via a bus 640. For embodiments in which node virtualization (e.g., NFV) is utilized, a hypervisor 602 may be executed to provide an execution environment for one or more network slices / sub-slices to utilize the hardware resources 600.

[0164] Processor 610 may include, for example, processor 612 and processor 614. Processor 610 may be, for example, a central processing unit (CPU), a reduced instruction set computing (RISC) processor, a complex instruction set computing (CISC) processor, a graphics processing unit (GPU), a DSP such as a baseband processor, an ASIC, an FPGA, a radio frequency integrated circuit (RFIC), another processor (including those discussed herein), or any suitable combination thereof.

[0165] The memory / storage device 620 may include main memory, disk storage, or any suitable combination thereof. The memory / storage device 620 may include, but is not limited to, any type of volatile or non-volatile memory, such as 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 storage, etc.

[0166] The communication resources 630 may include an interconnect or network interface component or other suitable device to communicate with one or more peripheral devices 604 or one or more databases 606 via the network 608. For example, the communication resources 630 may include a wired communication component (e.g., for coupling via USB), a cellular communication component, an NFC component, (or Low power consumption) components, components and other communication components.

[0167] The instructions 650 may include software, programs, applications, applet, applications, or other executable code for causing at least any one of the processors 610 to perform any one or more of the methods discussed herein. The instructions 650 may reside completely or partially in at least one of the processors 610 (e.g., in a cache memory of the processor), the memory / storage device 620, or any suitable combination thereof. In addition, any portion of the instructions 650 may be transmitted to the hardware resources 600 from any combination of the peripheral devices 604 or the database 606. Thus, the memory of the processor 610, the memory / storage device 620, the peripheral devices 604, and the database 606 are examples of computer-readable and machine-readable media.

[0168] FIG. 7A to FIG. 7D A flow chart of a method according to various aspects is shown. Fig. 7A A method for a mobile radio communication terminal device is shown, the method comprising: receiving 702, by at least one receiver of the mobile radio communication terminal device, a physical downlink shared channel and an associated physical downlink shared channel demodulation reference signal to be transmitted from the first mobile radio communication network according to a modified schedule, the modified schedule having at least one symbol shift of the physical downlink shared channel demodulation reference signal relative to a schedule of a cell-specific reference signal, wherein the second mobile radio communication network is configured to transmit the cell-specific reference signal, in a case where the mobile radio communication terminal device is operating during overlapping communications of a first mobile radio communication network and a second mobile radio communication network; storing 704, by a memory of the mobile radio communication terminal device, the physical downlink shared channel demodulation reference signal of the first mobile radio communication network; and processing 706, by one or more processors of the mobile radio communication terminal device, the received physical downlink shared channel using the physical downlink shared channel demodulation reference signal transmitted from the first mobile radio communication network so as to provide hybrid automatic repeat request confirmation feedback in response to the physical downlink shared channel in a case where a corresponding minimum mobile radio communication terminal device processing time for the physical downlink shared channel processing is met.

[0169] Figure 7BA method for a mobile radio communication device is shown, the method comprising: in a case where the mobile radio communication device is operating during overlapping communications between a first mobile radio communication network and a second mobile radio communication network, one or more processors of the mobile radio communication device generating 712 a physical downlink shared channel and an associated physical downlink shared channel demodulation reference signal according to a modified schedule, the modified schedule having at least one symbol shift of the physical downlink shared channel demodulation reference signal relative to a schedule of a cell-specific reference signal, wherein the second mobile radio communication network is configured to transmit the cell-specific reference signal; at least one transmitter of the mobile radio communication device transmitting 714 the physical downlink shared channel and the physical downlink shared channel demodulation reference signal according to the modified schedule; and one or more processors of the mobile radio communication device indicating 716 resources for hybrid automatic repeat request acknowledgment feedback corresponding to the transmitted physical downlink shared channel according to the modified schedule, the modified schedule being configured according to satisfying a corresponding minimum mobile radio communication terminal device processing time for physical downlink shared channel processing.

[0170] Figure 7C A method for a non-transitory computer-readable storage medium is shown, which stores program instructions that, when executed by one or more processors of a mobile radio communication terminal device, enable receiving 722 a physical downlink shared channel and an associated physical downlink shared channel demodulation reference signal from a first mobile radio communication network according to a modified schedule having at least one symbol shift of the physical downlink shared channel demodulation reference signal relative to a schedule of a cell-specific reference signal, wherein the second mobile radio communication network is configured to transmit the cell-specific reference signal; and store 724 the physical downlink shared channel demodulation reference signal of the first mobile radio communication network, when the mobile radio communication terminal device is operating during overlapping communications between the first mobile radio communication network and the second mobile radio communication network.

[0171] Fig.7DA method for a non-transitory computer-readable storage medium is shown, which stores program instructions that, when executed by one or more processors of a mobile radio communication device, cause the mobile radio communication device to generate 732 a physical downlink shared channel and an associated physical downlink shared channel demodulation reference signal according to a modified schedule having at least one symbol shift of the physical downlink shared channel demodulation reference signal relative to a schedule of a cell-specific reference signal, wherein the second mobile radio communication network is configured to transmit the cell-specific reference signal; and transmit 734 a physical downlink shared channel and an associated physical downlink shared channel demodulation reference signal of the first mobile radio communication network, while the mobile radio communication device is operating during overlapping communications between a first mobile radio communication network and a second mobile radio communication network.

[0172] 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 and / or methods described in the following example section. For example, the baseband circuit described above in conjunction with one or more of the foregoing figures may be configured to operate according to one or more of the following embodiments. For another example, the circuits 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 embodiments shown in the example section below.

[0173] For one or more aspects, 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 and / or methods described in the following embodiments. For example, the baseband circuit described above in conjunction with one or more of the foregoing figures may be configured to operate according to one or more of the following embodiments. For another example, the circuits 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 embodiments shown in the embodiments section below.

[0174] Example

[0175] Embodiment 1 is a mobile radio communication terminal device, which is operable to facilitate a physical downlink shared channel (e.g., PDSCH (Physical Downlink Shared Channel)) demodulation reference signal (e.g., PDSCH associated demodulation reference signal) of a first mobile radio communication network communication connection during overlapping communications between the first mobile radio communication network and a second mobile radio communication network. The second mobile radio communication network is configured to transmit a cell-specific reference signal. A mobile radio communication terminal device comprises one or more processors configured to receive a physical downlink shared channel (e.g., PDSCH) and an associated demodulation reference signal (e.g., PDSCH-associated demodulation reference signal) to be transmitted from a first mobile radio communication network according to a modified schedule having at least one symbol shift of the physical downlink shared channel demodulation reference signal relative to a schedule of a cell-specific reference signal; a memory storing the physical downlink shared channel of the first mobile radio communication network and the associated physical downlink shared channel demodulation reference signal; and one or more processors configured to process the received physical downlink shared channel using the physical downlink shared channel demodulation reference signal of the first mobile radio communication network transmitted according to the modified schedule so as to provide a hybrid automatic repeat request acknowledgment (e.g., HARQ-ACK) feedback in response to the physical downlink shared channel while satisfying a corresponding minimum mobile radio communication terminal device processing time for the physical downlink shared channel processing.

[0176] The modified scheduling of the demodulation reference signal may be to provide at least one demodulation reference signal provided in a symbol different from a cell-specific reference signal symbol of the second mobile communication network within a physical downlink shared channel of a duration of D symbols. Here, D is the number of symbols from a time slot boundary (symbol #0) to the last symbol of the physical downlink shared channel in a time slot of a frame of the first mobile communication network.

[0177] Embodiment 2 includes the mobile radio communication terminal device according to embodiment 1 and / or some other embodiments herein, wherein the mobile radio communication terminal device is a user equipment (UE).

[0178] Embodiment 3 includes a mobile radio communication terminal device according to any one of embodiments 1 or 2 and / or some other embodiments of this document, wherein the first mobile radio communication network is a 5G communication network, and the demodulation reference signal is a demodulation reference signal of the 5G communication network. The 5G communication network can also be represented as a new radio (NR) communication network. The physical downlink shared channel demodulation reference signal can be represented as a PDSCH DMRS.

[0179] Embodiment 4 includes a mobile radio communication terminal device according to any one of embodiments 1 to 3 and / or some other embodiments of this document, wherein the second mobile radio communication network is a long term evolution (LTE) communication network, and the cell-specific reference signal is a cell-specific reference signal of the LTE communication network. The cell-specific reference signal can be expressed as CRS.

[0180] Embodiment 5 comprises the mobile radio communication terminal device according to any one of embodiments 1 to 4 and / or some other embodiments herein, wherein the mobile radio communication terminal device comprises at least one receiver configured to receive a demodulation reference signal.

[0181] Embodiment 6 includes a mobile radio communication terminal device according to any one of Embodiments 1 to 5 and / or some other embodiments of the present invention, wherein when the mobile radio communication terminal device is configured with Ite-CRS-ToMatchAround via a high layer of an open system interconnection model, when the mobile radio communication terminal device is configured with dmrs-AdditionalPosition='pos1' or dmrs-AdditionalPosition='pos2' or dmrs-AdditionalPosition='pos3', the last single symbol of the demodulation reference signal in the physical downlink shared channel is in symbol #12 of the time slot.

[0182] Embodiment 7 includes a mobile radio communication terminal device according to any one of embodiments 1 to 6 and / or some other embodiments of the present invention, wherein the demodulation reference signal position of the single-symbol demodulation reference signal of D=13, 14 for the physical downlink shared channel mapping type A is defined so that when the mobile radio communication terminal device is configured with dmrs-AdditionalPosition='pos1' or dmrs-AdditionalPosition='pos2' or dmrs-AdditionalPosition='pos3', the last single-symbol demodulation reference signal in the physical downlink shared channel is in symbol #12 of the time slot.

[0183] Embodiment 8 includes a mobile radio communication terminal device according to any one of embodiments 1 to 7 and / or some other embodiments of the present invention, wherein the demodulation reference signal position of the single-symbol demodulation reference signal of D=13, 14 for physical downlink shared channel mapping type A is defined so that when the mobile radio communication terminal device is configured with dmrs-AdditionalPosition='pos2', the first additional single-symbol demodulation reference signal position is in symbol #8 of the time slot.

[0184] Embodiment 9 includes a mobile radio communication terminal device according to any one of Embodiments 1 to 8 and / or some other embodiments of the present invention, wherein when the mobile radio communication terminal device is configured with Ite-CRS-ToMatchAround via a higher layer, when the mobile radio communication terminal device is configured with dmrs-AdditionalPosition='pos2', the first additional single-symbol demodulation reference signal position is in symbol #8 of the time slot.

[0185] Embodiment 10 includes a mobile radio communication terminal device according to any one of embodiments 1 to 11 and / or some other embodiments of the present invention, wherein for the case of a dual-symbol demodulation reference signal, when the physical downlink shared channel is scheduled so that D=14, for dmrs-AdditionalPosition='pos1', the demodulation reference signal position is defined as (l0,12).

[0186] Embodiment 11 includes a mobile radio communication terminal device according to any one of embodiments 1 to 10 and / or some other embodiments of the present invention, wherein, regardless of whether the mobile radio communication terminal device is configured with Ite-CRS-ToMatchAround via a higher layer of an open system interconnection model, the demodulation reference signal position for additional demodulation reference signal symbols is applied to a unicast and / or broadcast physical downlink shared channel.

[0187] Embodiment 12 includes a mobile radio communication terminal device according to any one of embodiments 1 to 11 and / or some other embodiments herein, wherein the mapping of the additional demodulation reference signal to symbol #12 or #8 is applied to the unicast physical downlink shared channel only when the mobile radio communication terminal device is configured with Ite-CRS-ToMatchAround via a higher layer of the open system interconnection model,

[0188] Embodiment 13 includes a mobile radio communication terminal device according to any one of embodiments 1 to 12 and / or some other embodiments herein, wherein a physical downlink control channel (PDCCH) with a cyclic redundancy check (CRC) is used to schedule a unicast physical downlink shared channel, and the CRC is scrambled using a cell radio network temporary identifier (C-RNTI), a circuit switched radio network temporary identifier (CS-RNTI), or a modulation and coding scheme-radio network temporary identifier (MCS-C-RNTI).

[0189] Embodiment 14 includes a mobile radio communication terminal device according to any one of embodiments 1 to 13 and / or some other embodiments of the present invention, wherein when the mobile radio communication terminal device is configured with dmrs-AdditionalPosition≠pos0 in DMRS-DownlinkConfig in any one of dmrs-DownlinkForPDSCH-MappingTypeA and dmrs-DownlinkForPDSCH-MappingTypeB, or when this high-level parameter of the open system interconnection model is not configured, when the last single-symbol demodulation reference signal position within the physical downlink shared channel is symbol #12 of the time slot of the physical downlink shared channel mapping type A, the minimum mobile radio communication terminal device processing time value (N1) in the orthogonal frequency division multiplexing (OFDM) symbol is increased by one symbol.

[0190] Embodiment 15 includes a mobile radio communication terminal device according to any one of embodiments 1 to 14 and / or some other embodiments of the present invention, wherein, when the mobile radio communication terminal device is configured with dmrs-AdditionalPosition=pos1 in DMRS-DownlinkConfig in dmrs-DownlinkForPDSCH-MappingTypeA, when the second demodulation reference signal position is symbol #12 of the time slot of the physical downlink shared channel mapping type A, the minimum mobile radio communication terminal device processing time value (N1) (in OFDM symbol) is increased by one symbol.

[0191] Embodiment 16 includes a mobile radio communication terminal device according to any one of embodiments 1 to 15 and / or some other embodiments of the present invention, wherein in the case of a dual-symbol demodulation reference signal, when the mobile radio communication terminal device is configured with a demodulation reference signal in any of dmrs-Downlink of a physical downlink shared channel mapping type A and dmrsDownlink of a physical downlink shared channel mapping type B, dmrs-AdditionalPosition in DownlinkConfig≠pos0, or when this high-level parameter is not configured, when the last dual-symbol demodulation reference signal position within the physical downlink shared channel is symbol #12 of the time slot of the physical downlink shared channel mapping type A, the minimum mobile radio communication terminal device processing time value (N1) (in OFDM symbols) is increased by two symbols.

[0192] Embodiment 17 includes a mobile radio communication terminal device according to any one of embodiments 1 to 16 and / or some other embodiments of the present invention, wherein, when the mobile radio communication terminal device is configured with a demodulation reference signal in dmrs-Downlink of a physical downlink shared channel mapping type A and dmrs-AdditionalPosition=pos1 in DownlinkConfig, when the last two-symbol demodulation reference signal position within the physical downlink shared channel is symbol #12 of the time slot of the physical downlink shared channel mapping type A, the minimum mobile radio communication terminal device processing time value (N1) (in OFDM symbols) is increased by two symbols.

[0193] Embodiment 18 includes a mobile radio communication terminal device according to any one of embodiments 1 to 17 and / or some other embodiments of the present invention, wherein the physical downlink shared channel mapping type A is scheduled to have D=8 or D=9, and for dmrs-AdditionalPosition='pos1', the corresponding demodulation reference signal position is defined as (l0,8), regardless of the configuration of the higher-level parameter Ite-CRS-ToMatchAround or when the higher-level parameter Ite-CRS-ToMatchAround is configured to the mobile radio communication terminal device.

[0194] Embodiment 19 includes a mobile radio communication terminal device according to any one of embodiments 1 to 18 and / or some other embodiments herein, wherein a physical downlink shared channel subcarrier spacing (SCS) of a scheduled physical downlink shared channel is 15 kHz.

[0195] Embodiment 20 comprises a mobile radio communication terminal device according to any one of embodiments 1 to 19 and / or some other embodiments herein, wherein a demodulation reference signal position is defined for all SCSs of a downlink (DL) bandwidth part (BWP) in which a physical downlink shared channel is scheduled.

[0196] Embodiment 21 comprises the mobile radio communication terminal device according to any one of embodiments 1 to 20 and / or some other embodiments herein, wherein a last demodulation reference signal symbol within a physical downlink shared channel duration is delayed.

[0197] Embodiment 22 comprises a mobile radio communication terminal device according to any one of embodiments 1 to 21 and / or some other embodiments herein, wherein when μ=0, the symbol delay is applicable to determining the minimum physical downlink shared channel processing time as shown in Table 5.3-1 of TS38.214.

[0198] Embodiment 23 is a mobile radio communication device, which is operable to facilitate a physical downlink shared channel (PDSCH) and an associated PDSCH demodulation reference signal of a first mobile radio communication network communication connection during overlapping communications between the first mobile radio communication network and a second mobile radio communication network, wherein the second mobile radio communication network is configured to transmit a cell-specific reference signal, the mobile radio communication device comprising: one or more processors, the one or more processors configured to generate a demodulation reference signal to be received from the first mobile radio communication network according to a modified scheduling, the modified scheduling having at least one symbol shift of the PDSCH demodulation reference signal relative to the scheduling of the cell-specific reference signal; and generating a demodulation reference signal according to the modified scheduling; at least one transmitter, the at least one transmitter being used to transmit the PDSCH and the PDSCH demodulation reference signal according to the modified scheduling; and one or more processors, the one or more processors configured to indicate resources for HARQ-ACK feedback corresponding to the transmitted PDSCH according to the modified scheduling, so that the corresponding minimum mobile radio communication terminal device (e.g., UE) processing time for PDSCH processing is met.

[0199] Embodiment 24 comprises a mobile radio communication device according to embodiment 23 and / or some other embodiments herein, wherein the mobile radio communication device is a base station or a core network component.

[0200] Embodiment 25 includes a mobile radio communication device according to any one of embodiments 23 or 24 and / or some other embodiments herein, wherein the first mobile radio communication network is a 5G communication network, and the demodulation reference signal is a demodulation reference signal of the 5G communication network.

[0201] Embodiment 26 includes a mobile radio communication terminal device according to any one of embodiments 23 to 25 and / or some other embodiments of the present invention, wherein the second mobile radio communication network is a long term evolution (LTE) communication network, and the cell-specific reference signal is a cell-specific reference signal of the LTE communication network.

[0202] Embodiment 27 includes a mobile radio communication device according to any one of embodiments 23 to 26 and / or some other embodiments herein, wherein the mobile radio communication device includes at least one transmitter configured to transmit a physical downlink shared channel (PDSCH) and an associated PDSCH demodulation reference signal of a first mobile radio communication network communication connection according to a modified scheduling.

[0203] Embodiment 28 includes a mobile radio communication device according to any one of Embodiments 23 to 27 and / or some other embodiments of the present invention, wherein when the mobile radio communication terminal device is configured with Ite-CRS-ToMatchAround via a high layer of an open system interconnection model, when the mobile radio communication terminal device is configured with dmrs-AdditionalPosition='pos1' or dmrs-AdditionalPosition='pos2' or dmrs-AdditionalPosition='pos3', the last single symbol of the demodulation reference signal in the physical downlink shared channel is in symbol #12 of the time slot.

[0204] Embodiment 29 includes a mobile radio communication device according to any one of embodiments 23 to 28 and / or some other embodiments of the present invention, wherein the demodulation reference signal position of the single-symbol demodulation reference signal of D=13, 14 for the physical downlink shared channel mapping type A is defined so that when the mobile radio communication terminal device is configured with dmrs-AdditionalPosition='pos1' or dmrs-AdditionalPosition='pos2' or dmrs-AdditionalPosition='pos3', the last single-symbol demodulation reference signal in the physical downlink shared channel is in symbol #12 of the time slot.

[0205] Embodiment 30 includes a mobile radio communication device according to any one of embodiments 23 to 29 and / or some other embodiments of the present invention, wherein the demodulation reference signal position of the single-symbol demodulation reference signal of D=13, 14 for physical downlink shared channel mapping type A is defined so that when the mobile radio communication terminal device is configured with dmrs-AdditionalPosition='pos2', the first additional single-symbol demodulation reference signal position is in symbol #8 of the time slot.

[0206] Embodiment 31 includes a mobile radio communication device according to any one of Embodiments 23 to 30 and / or some other embodiments of the present invention, wherein when the mobile radio communication terminal device is configured with Ite-CRS-ToMatchAround via a higher layer, when the mobile radio communication terminal device is configured with dmrs-AdditionalPosition='pos2', the first additional single-symbol demodulation reference signal position is in symbol #8 of the time slot.

[0207] Embodiment 32 includes a mobile radio communication device according to any one of embodiments 23 to 31 and / or some other embodiments of the present invention, wherein for the case of a dual-symbol demodulation reference signal, when the physical downlink shared channel is scheduled so that D=14, for dmrs-AdditionalPosition='pos1', the demodulation reference signal position is defined as (l0,12).

[0208] Embodiment 33 includes a mobile radio communication device according to any one of embodiments 23 to 32 and / or some other embodiments of the present document, wherein, regardless of whether the mobile radio communication terminal device is configured with Ite-CRS-ToMatchAround via a higher layer of an open system interconnection model, the demodulation reference signal position for additional demodulation reference signal symbols is applied to a unicast and / or broadcast physical downlink shared channel.

[0209] Embodiment 34 includes a mobile radio communication device according to any one of embodiments 23 to 33 and / or some other embodiments herein, wherein mapping to symbol #12 or #8 is applied to the unicast physical downlink shared channel only when the mobile radio communication terminal device is configured with Ite-CRS-ToMatchAround via a higher layer of an open system interconnection model,

[0210] Embodiment 35 includes a mobile radio communication device according to any one of embodiments 23 to 34 and / or some other embodiments herein, wherein a physical downlink control channel (PDCCH) with a cyclic redundancy check (CRC) is used to schedule a unicast physical downlink shared channel, the CRC being scrambled using a cell radio network temporary identifier (C-RNTI), a circuit switched radio network temporary identifier (CS-RNTI), or a modulation and coding scheme-radio network temporary identifier (MCS-C-RNTI).

[0211] Embodiment 36 includes a mobile radio communication device according to any one of embodiments 23 to 35 and / or some other embodiments of the present invention, wherein when the mobile radio communication terminal device is configured with dmrs-Downlink of a physical downlink shared channel mapping type A, dmrs-AdditionalPosition in the demodulation reference signal-DownlinkConfig of any one of dmrs-Downlink of a physical downlink shared channel mapping type B, and dmrs-AdditionalPosition≠pos0, or when this high-level parameter of the open system interconnection model is not configured, when the last single-symbol demodulation reference signal position within the physical downlink shared channel is symbol #12 of the time slot of the physical downlink shared channel mapping type A, the minimum mobile radio communication terminal device processing time value (N1) in the orthogonal frequency division multiplexing (OFDM) symbol is increased by one symbol.

[0212] Embodiment 37 includes a mobile radio communication device according to any one of embodiments 23 to 36 and / or some other embodiments of the present invention, wherein, in a case where the mobile radio communication terminal device is configured with a demodulation reference signal in dmrs-Downlink of a physical downlink shared channel mapping type A and dmrs-AdditionalPosition in DownlinkConfig=pos1, when the second demodulation reference signal position is symbol #12 of the time slot of the physical downlink shared channel mapping type A, the minimum mobile radio communication terminal device processing time value (N1) (in OFDM symbols) is increased by one symbol.

[0213] Embodiment 38 includes a mobile radio communication device according to any one of embodiments 23 to 37 and / or some other embodiments of the present invention, wherein in the case of a dual-symbol demodulation reference signal, when the mobile radio communication terminal device is configured with a demodulation reference signal in any of dmrs-Downlink of physical downlink shared channel mapping type A, dmrsDownlink of physical downlink shared channel mapping type B, and dmrs-AdditionalPosition in DownlinkConfig≠pos0, or when this high-level parameter is not configured, when the last dual-symbol demodulation reference signal position within the physical downlink shared channel is symbol #12 of the time slot of the physical downlink shared channel mapping type A, the minimum mobile radio communication terminal device processing time value (N1) (in OFDM symbol) is increased by two symbols.

[0214] Embodiment 39 includes a mobile radio communication device according to any one of embodiments 23 to 38 and / or some other embodiments of the present invention, wherein, when the mobile radio communication terminal device is configured with a demodulation reference signal in dmrs-Downlink of a physical downlink shared channel mapping type A and dmrs-AdditionalPosition in DownlinkConfig=pos1, when the last two-symbol demodulation reference signal position within the physical downlink shared channel is symbol #12 of the time slot of the physical downlink shared channel mapping type A, the minimum mobile radio communication terminal device processing time value (N1) (in OFDM symbols) is increased by two symbols.

[0215] Embodiment 40 includes a mobile radio communication device according to any one of embodiments 23 to 39 and / or some other embodiments of the present invention, wherein the physical downlink shared channel mapping type A is scheduled to have D=8 or D=9, and for dmrs-AdditionalPosition='pos1', the corresponding demodulation reference signal position is defined as (l0,8), regardless of the configuration of the higher-level parameter Ite-CRS-ToMatchAround or when the higher-level parameter Ite-CRS-ToMatchAround is configured to the mobile radio communication terminal device.

[0216] Embodiment 41 includes a mobile radio communication device according to any one of embodiments 23 to 40 and / or some other embodiments herein, wherein a physical downlink shared channel subcarrier spacing (SCS) of a scheduled physical downlink shared channel is 15 kHz.

[0217] Embodiment 42 comprises a mobile radio communication device according to any one of embodiments 23 to 41 and / or some other embodiments herein, wherein a demodulation reference signal position is defined for all SCSs of a downlink (DL) bandwidth part (BWP) in which a physical downlink shared channel is scheduled.

[0218] Embodiment 43 includes the mobile radio communications device according to any one of embodiments 23 to 42 and / or some other embodiments herein, wherein a last demodulation reference signal symbol within a physical downlink shared channel duration is delayed.

[0219] Embodiment 44 includes a mobile radio communication device according to any one of embodiments 23 to 43 and / or some other embodiments herein, wherein when μ=0, the symbol delay is applicable to determine the minimum physical downlink shared channel processing time as shown in Table 5.3-1 of TS38.214.

[0220] Embodiment 45 is a method for facilitating a physical downlink shared channel (PDSCH) in a first mobile radio communication network connection between a mobile radio communication device and a mobile radio communication terminal device during overlapping communications of the first mobile radio communication network and a second mobile radio communication network, wherein the second mobile radio communication network is configured to transmit a cell-specific reference signal, the method comprising: receiving a PDSCH and an associated PDSCH demodulation reference signal according to a modified scheduling, the modified scheduling having at least one symbol shift of the PDSCH demodulation reference signal relative to the scheduling of the cell-specific reference signal; storing the physical downlink shared channel demodulation reference signal of the first mobile radio communication network; and processing the received PDSCH using the PDSCH demodulation reference signal of the first mobile radio communication network transmitted according to the modified scheduling so as to provide HARQ-ACK feedback in response to the PDSCH while satisfying the corresponding minimum mobile radio communication terminal device for PDSCH processing, such as processing time.

[0221] Embodiment 46 includes the method according to embodiment 45 and / or some other embodiments herein, wherein the mobile radio communication terminal device is a user equipment (UE).

[0222] Embodiment 47 includes a method according to any one of Embodiments 45 or 46 and / or some other embodiments herein, wherein the mobile radio communication device is a base station or a core network component.

[0223] Embodiment 48 includes a method according to any one of embodiments 45 to 47 and / or some other embodiments herein, wherein the first mobile radio communication network is a 5G communication network and the demodulation reference signal is a demodulation reference signal of the 5G communication network.

[0224] Embodiment 49 includes a method according to any one of embodiments 45 to 48 and / or some other embodiments herein, wherein the second mobile radio communication network is a Long Term Evolution (LTE) communication network, and the cell-specific reference signal is a cell-specific reference signal of the LTE communication network.

[0225] Embodiment 50 includes a method according to any one of embodiments 45 to 49 and / or some other embodiments herein, wherein the mobile radio communication device includes at least one transmitter configured to transmit a physical downlink shared channel demodulation reference signal of a first mobile radio communication network communication connection according to a modified scheduling, wherein the modified scheduling has at least one symbol shift of the PDSCH demodulation reference signal relative to the scheduling of the cell-specific reference signal.

[0226] Embodiment 51 comprises a method according to any one of embodiments 45 to 50 and / or some other embodiments herein, wherein the mobile radio communication terminal device comprises at least one receiver configured to receive a physical downlink shared channel demodulation reference signal of a first mobile radio communication network communication connection according to a modified scheduling, wherein the modified scheduling has at least one symbol shift of the PDSCH demodulation reference signal relative to the scheduling of the cell-specific reference signal.

[0227] Embodiment 52 includes a non-transitory computer-readable storage medium storing program instructions for facilitating a physical downlink shared channel (e.g., PDSCH) in a first mobile radio communication network connection between a mobile radio communication device and a mobile radio communication terminal device via a demodulation reference signal of the first mobile radio communication network during overlapping communications between the first mobile radio communication network and a second mobile radio communication network, wherein the second mobile radio communication network is configured to transmit a cell-specific reference signal, and when these program instructions are executed by one or more processors of the mobile radio communication terminal device, enable receiving the PDSCH and the associated PDSCH demodulation reference signal from the first mobile radio communication network according to a modified scheduling, wherein the modified scheduling has at least one symbol shift of the PDSCH demodulation reference signal relative to the scheduling of the cell-specific reference signal; and store the physical downlink shared channel demodulation reference signal of the first mobile radio communication network.

[0228] Embodiment 53 includes a non-transitory computer-readable storage medium storing program instructions for facilitating a physical downlink shared channel (e.g., PDSCH) in a first mobile radio communication network connection between a mobile radio communication device and a mobile radio communication terminal device via a demodulation reference signal of the first mobile radio communication network during overlapping communications between the first mobile radio communication network and a second mobile radio communication network, wherein the second mobile radio communication network is configured to transmit a cell-specific reference signal, and when these program instructions are executed by one or more processors of the mobile radio communication device, the device generates a PDSCH and an associated PDSCH demodulation reference signal according to a modified scheduling having at least one symbol shift of the PDSCH demodulation reference signal relative to the scheduling of the cell-specific reference signal; and transmits the PDSCH and the associated PDSCH demodulation reference signal of the first mobile radio communication network.

[0229] Embodiment 54 includes a non-transitory computer-readable storage medium according to any one of Embodiments 52 or 53 and / or some other embodiments herein, wherein the mobile radio communication terminal device is a user equipment (UE).

[0230] Embodiment 55 includes a non-transitory computer-readable storage medium according to any one of embodiments 52 to 54 and / or some other embodiments herein, wherein the mobile radio communication device is a base station or a core network component.

[0231] Embodiment 56 includes a non-transitory computer-readable storage medium according to any one of embodiments 52 to 55 and / or some other embodiments herein, wherein the first mobile radio communication network is a 5G communication network and the demodulation reference signal is a demodulation reference signal of the 5G communication network.

[0232] Embodiment 57 includes a non-transitory computer-readable storage medium according to any one of embodiments 52 to 58 and / or some other embodiments herein, wherein the second mobile radio communication network is a long term evolution (LTE) communication network, and the cell-specific reference signal is a cell-specific reference signal of the LTE communication network.

[0233] Embodiment 58 includes a non-transitory computer-readable storage medium according to any one of embodiments 52 to 57 and / or some other embodiments herein, wherein the mobile radio communication device includes at least one transmitter configured to transmit a physical downlink shared channel demodulation reference signal of a first mobile radio communication network communication connection according to a modified schedule.

[0234] Embodiment 59 includes a non-transitory computer-readable storage medium according to any one of embodiments 52 to 58 and / or some other embodiments of the present invention, wherein when the mobile radio communication terminal device is configured with Ite-CRS-ToMatchAround via a high layer of the open system interconnection model, when the mobile radio communication terminal device is configured with dmrs-AdditionalPosition='pos1' or dmrs-AdditionalPosition='pos2' or dmrs-AdditionalPosition='pos3', the last single symbol of the demodulation reference signal in the physical downlink shared channel is in symbol #12 of the time slot.

[0235] Embodiment 60 includes a non-transitory computer-readable storage medium according to any one of embodiments 52 to 59 and / or some other embodiments of the present invention, wherein the demodulation reference signal position of the single-symbol demodulation reference signal of D=13, 14 for the physical downlink shared channel mapping type A is defined so that when the mobile radio communication terminal device is configured with dmrs-AdditionalPosition='pos1' or dmrs-AdditionalPosition='pos2' or dmrs-AdditionalPosition='pos3', the last single-symbol demodulation reference signal in the physical downlink shared channel is in symbol #12 of the time slot.

[0236] Embodiment 61 includes a non-transitory computer-readable storage medium according to any one of embodiments 52 to 60 and / or some other embodiments of the present invention, wherein the demodulation reference signal position of the single-symbol demodulation reference signal of D=13, 14 for physical downlink shared channel mapping type A is defined so that when the mobile radio communication terminal device is configured with dmrs-AdditionalPosition='pos2', the first additional single-symbol demodulation reference signal position is in symbol #8 of the time slot.

[0237] Embodiment 62 includes a non-transitory computer-readable storage medium according to any one of embodiments 52 to 61 and / or some other embodiments of the present invention, wherein when the mobile radio communication terminal device is configured with Ite-CRS-ToMatchAround via a higher layer, when the mobile radio communication terminal device is configured with dmrs-AdditionalPosition='pos2', the first additional single-symbol demodulation reference signal position is in symbol #8 of the time slot.

[0238] Embodiment 63 includes a non-transitory computer-readable storage medium according to any one of embodiments 52 to 62 and / or some other embodiments of the present invention, wherein for the case of a dual-symbol demodulation reference signal, when the physical downlink shared channel is scheduled so that D=14, for dmrs-AdditionalPosition='pos1', the demodulation reference signal position is defined as (l0,12).

[0239] Embodiment 64 includes a non-transitory computer-readable storage medium according to any one of embodiments 52 to 63 and / or some other embodiments of the present document, wherein, regardless of whether the mobile radio communication terminal device is configured with Ite-CRS-ToMatchAround via a higher layer of an open system interconnection model, the demodulation reference signal position for additional demodulation reference signal symbols is applied to a unicast and / or broadcast physical downlink shared channel.

[0240] Embodiment 65 includes a non-transitory computer-readable storage medium according to any one of embodiments 52 to 64 and / or some other embodiments herein, wherein mapping to symbol #12 or #8 is applied to the unicast physical downlink shared channel only when the mobile radio communication terminal device is configured with Ite-CRS-ToMatchAround via a higher layer of the open system interconnection model,

[0241] Embodiment 66 includes a non-transitory computer-readable storage medium according to any one of embodiments 52 to 65 and / or some other embodiments herein, wherein a physical downlink control channel (PDCCH) with a cyclic redundancy check (CRC) is used to schedule a unicast physical downlink shared channel, the CRC being scrambled using a cell radio network temporary identifier (C-RNTI), a circuit switched radio network temporary identifier (CS-RNTI), or a modulation and coding scheme-radio network temporary identifier (MCS-C-RNTI).

[0242] Embodiment 67 includes a non-transitory computer-readable storage medium according to any one of embodiments 52 to 66 and / or some other embodiments of the present invention, wherein when the mobile radio communication terminal device is configured with dmrs-Downlink of physical downlink shared channel mapping type A, dmrs-AdditionalPosition in the demodulation reference signal-DownlinkConfig of any of dmrs-Downlink of physical downlink shared channel mapping type B, and when this high-level parameter of the open system interconnection model is not configured, when the last single-symbol demodulation reference signal position within the physical downlink shared channel is symbol #12 of the time slot of the physical downlink shared channel mapping type A, the minimum mobile radio communication terminal device processing time value (N1) in the orthogonal frequency division multiplexing (OFDM) symbol is increased by one symbol.

[0243] Embodiment 68 includes a non-transitory computer-readable storage medium according to any one of embodiments 52 to 67 and / or some other embodiments of the present invention, wherein, in a case where a mobile radio communication terminal device is configured with a demodulation reference signal in dmrs Downlink of a physical downlink shared channel mapping type A - dmrs-AdditionalPosition=pos1 in DownlinkConfig, when the second demodulation reference signal position is symbol #12 of the time slot of the physical downlink shared channel mapping type A, the minimum mobile radio communication terminal device processing time value (N1) (in OFDM symbols) is increased by one symbol.

[0244] Embodiment 69 includes a non-transitory computer-readable storage medium according to any one of embodiments 52 to 68 and / or some other embodiments of the present invention, wherein in the case of a dual-symbol demodulation reference signal, when the mobile radio communication terminal device is configured with a demodulation reference signal in any of dmrs-Downlink of physical downlink shared channel mapping type A and dmrsDownlink of physical downlink shared channel mapping type B, dmrs-AdditionalPosition in DownlinkConfig≠pos0, or when this high-level parameter is not configured, when the last dual-symbol demodulation reference signal position within the physical downlink shared channel is symbol #12 of the time slot of the physical downlink shared channel mapping type A, the minimum mobile radio communication terminal device processing time value (N1) (in OFDM symbol) is increased by two symbols.

[0245] Embodiment 70 includes a non-transitory computer-readable storage medium according to any one of embodiments 52 to 69 and / or some other embodiments of the present invention, wherein, in a case where a mobile radio communication terminal device is configured with a demodulation reference signal in dmrs-Downlink of a physical downlink shared channel mapping type A and dmrs-AdditionalPosition in DownlinkConfig = pos1, when the last two-symbol demodulation reference signal position within the physical downlink shared channel is symbol #12 of the time slot of the physical downlink shared channel mapping type A, the minimum mobile radio communication terminal device processing time value (N1) (in OFDM symbols) is increased by two symbols.

[0246] Embodiment 71 includes a non-transitory computer-readable storage medium according to any one of embodiments 52 to 70 and / or some other embodiments of the present invention, wherein the physical downlink shared channel mapping type A is scheduled to have D=8 or D=9, and for dmrs-AdditionalPosition='pos1', the corresponding demodulation reference signal position is defined as (l0,8), regardless of the configuration of the higher-level parameter Ite-CRS-ToMatchAround or when the higher-level parameter Ite-CRS-ToMatchAround is configured to the mobile radio communication terminal device.

[0247] Embodiment 72 comprises a non-transitory computer-readable storage medium according to any one of embodiments 52 to 71 and / or some other embodiments herein, wherein a physical downlink shared channel subcarrier spacing (SCS) of a scheduled physical downlink shared channel is 15 kHz.

[0248] Embodiment 73 comprises a non-transitory computer-readable storage medium according to any one of embodiments 52 to 72 and / or some other embodiments herein, wherein a demodulation reference signal position is defined for all SCSs of a downlink (DL) bandwidth part (BWP) in which a physical downlink shared channel is scheduled.

[0249] Embodiment 74 includes a non-transitory computer-readable storage medium according to any one of embodiments 52 to 73 and / or some other embodiments herein, wherein a last demodulation reference signal symbol within a physical downlink shared channel duration is delayed.

[0250] Embodiment 75 comprises a non-transitory computer-readable storage medium according to any one of embodiments 52 to 74 and / or some other embodiments herein, wherein when μ=0, the symbol delay is applicable to determining the minimum physical downlink shared channel processing time as shown in Table 5.3-1 of TS38.214.

[0251] In embodiment 76, in addition to any one of embodiments 1 to 75, the demodulation reference signal to be transmitted is shifted by a single symbol to avoid transmission to the mobile radio communication terminal device on a symbol containing a cell-specific reference signal of LTE as indicated by the first mobile radio communication network.

[0252] Unless explicitly stated otherwise, any of the above embodiments may be combined with any other embodiment (or combination of embodiments). The foregoing description of one or more specific implementations provides illustration and description, but is not intended to be exhaustive or to limit the scope of the various aspects to the precise form disclosed. In view of the above teachings, modifications and variations are possible or can be obtained from the practice of various aspects.

[0253] In this disclosure, “SMTC” refers to the SSB-based measurement timing configuration configured by SSB-MeasurementTimingConfiguration;

[0254] "SSB" refers to SS / PBCH block; "field" may refer to the individual contents of an information element;

[0255] "Information Element" means a structural element containing single or multiple fields;

[0256] "Primary cell" refers to an MCG (primary cell group) cell operating on the primary frequency, in which the UE either performs an initial connection establishment procedure or initiates a connection re-establishment procedure;

[0257] “Primary SCG cell” refers to the SCG cell in which the UE performs random access when performing reconfiguration using the synchronization procedure for DC (dual connectivity) operation;

[0258] "Secondary cell" refers to a cell that provides additional radio resources on top of a special cell for a UE configured with CA;

[0259] “Secondary cell group” refers to a subset of serving cells including a PSCell (primary SCell) and zero or more secondary cells for a UE configured with DC;

[0260] "Serving cell" means a primary cell for a UE in RRC_CONNECTED without CA / DC configured, where there is only one serving cell including the primary cell;

[0261] "Serving cell" refers to the cell group including special cells and all secondary cells for UEs configured with CA / DC and in RRC_CONNECTED; and

[0262] “Special cell” refers to the PCell of an MCG or the PSCell of an SCG for DC operation; otherwise, the term “special cell” refers to the PCell.

[0263] Although the present invention has been shown and described with reference to certain aspects, it will be understood by those skilled in the art that various changes in form and details may be made therein without departing from the spirit and scope of the present invention as defined by the appended claims. The scope of the present invention is therefore indicated by the appended claims, and all changes coming within the meaning and range of equivalents of the claims are therefore intended to be embraced.

Claims

1. A mobile radio communication terminal device, comprising: at least one receiver configured to, in case the mobile radio communication terminal device is operating during overlapping communications of the first mobile radio communication network and the second mobile radio communication network, receive a physical downlink shared channel and an associated physical downlink shared channel demodulation reference signal to be transmitted from the first mobile radio communication network according to a modified schedule having at least one symbol shift of the physical downlink shared channel demodulation reference signal relative to a schedule of a cell-specific reference signal, wherein the second mobile radio communication network is configured to transmit the cell-specific reference signal and wherein the position of the demodulation reference signal is defined for all subcarrier spacings of the downlink bandwidth portion in which the physical downlink shared channel is scheduled; a memory storing the physical downlink shared channel demodulation reference signal of the first mobile radio communications network; and one or more processors for processing a received physical downlink shared channel using the physical downlink shared channel demodulation reference signal transmitted from the first mobile radio communications network to provide hybrid automatic repeat request acknowledgement feedback in response to the physical downlink shared channel while meeting a corresponding minimum mobile radio communications terminal equipment processing time for physical downlink shared channel processing, wherein the physical downlink shared channel demodulation reference signal position of at least one additional demodulation reference signal symbol is shifted by a single symbol to avoid transmission on a symbol containing a cell-specific reference signal of the second mobile radio communications network as indicated by the first mobile radio communications network, and Wherein the minimum second mobile radio communication network processing time for physical downlink shared channel processing is increased by one symbol compared to a case where the additional demodulation reference signal symbol of the physical downlink shared channel is not shifted.

2. The mobile radio communication terminal device according to claim 1, The mobile radio communication terminal is a user equipment (UE).

3. The mobile radio communication terminal device according to claim 1, Wherein the first mobile radio communication network is a 5G communication network, and the physical downlink shared channel demodulation reference signal is a physical downlink shared channel demodulation reference signal of the 5G communication network.

4. The mobile radio communication terminal device according to claim 1 or 2, in, The second mobile radio communication network is a Long Term Evolution LTE communication network and the cell-specific reference signal is a Cell-Specific Reference Signal (CRS) of the LTE communication network.

5. A mobile radio communication device comprising: one or more processors for, in a case where the mobile radio communications device is operating during overlapping communications in a first mobile radio communications network and a second mobile radio communications network, generating a physical downlink shared channel and an associated physical downlink shared channel demodulation reference signal according to a modified schedule having at least one symbol shift of the physical downlink shared channel demodulation reference signal relative to a schedule of a cell-specific reference signal, wherein the second mobile radio communications network is configured to transmit the cell-specific reference signal and wherein the positions of the demodulation reference signal are defined for all subcarrier spacings of a downlink bandwidth portion in which the physical downlink shared channel is scheduled; at least one transmitter configured to transmit the physical downlink shared channel and the physical downlink shared channel demodulation reference signal according to the modified schedule; and one or more processors configured to indicate resources for hybrid automatic repeat request acknowledgment feedback corresponding to the transmitted physical downlink shared channel according to the modified schedule to meet a corresponding minimum mobile radio communication terminal equipment processing time for physical downlink shared channel processing, wherein in the physical downlink shared channel, the physical downlink shared channel demodulation reference signal to be transmitted is shifted by a single symbol to avoid transmission on symbols containing a cell-specific reference signal of the second mobile radio communications network as indicated by the first mobile radio communications network, and Therein, the minimum mobile radio communication terminal equipment processing time for physical downlink shared channel processing is increased by one symbol compared to a case where the additional demodulation reference signal symbol of the physical downlink shared channel is not shifted.

6. The mobile radio communication device according to claim 5, The mobile radio communication device is a base station or a core network component.

7. The mobile radio communication device according to any one of claims 5 or 6, wherein the first mobile radio communication network is a 5G communication network, and the physical downlink shared channel demodulation reference signal is a demodulation reference signal of a 5G NR communication network.

8. The mobile radio communication device according to any one of claims 5 or 6, wherein the second mobile radio communication network is a Long Term Evolution (LTE) communication network, and the cell-specific reference signal is a cell-specific reference signal (CRS) of the LTE communication network.

9. A non-transitory computer-readable storage medium storing program instructions which, when executed by one or more processors of a mobile radio communication terminal device, enable the mobile radio communication terminal device to: receiving, in case the mobile radio communication terminal device is operating during overlapping communications of a first mobile radio communication network and a second mobile radio communication network, a physical downlink shared channel and an associated physical downlink shared channel demodulation reference signal from the first mobile radio communication network according to a modified schedule having at least one symbol shift of the physical downlink shared channel demodulation reference signal relative to a schedule of a cell-specific reference signal, wherein the second mobile radio communication network is configured to transmit the cell-specific reference signal and wherein the position of the demodulation reference signal is defined for all subcarrier spacings of a downlink bandwidth portion in which the physical downlink shared channel is scheduled; and storing the physical downlink shared channel demodulation reference signal of the first mobile radio communications network, wherein the physical downlink shared channel demodulation reference signal position of at least one additional demodulation reference signal symbol is shifted by a single symbol to avoid transmission on a symbol containing a cell-specific reference signal of the second mobile radio communications network as indicated by the first mobile radio communications network, and The minimum second mobile radio communication network processing time for physical downlink shared channel processing is increased by one symbol compared to the case where the additional demodulation reference signal symbol of the physical downlink shared channel is not shifted. 10 . The non-transitory computer-readable storage medium according to claim 9 , wherein the mobile radio communication terminal device is a user equipment (UE).

11. The non-transitory computer readable storage medium according to any one of claims 9 or 10, Wherein the first mobile radio communication network is a 5G communication network, and the physical downlink shared channel demodulation reference signal is a physical downlink shared channel demodulation reference signal of the 5G communication network.

12. The non-transitory computer readable storage medium according to any one of claims 9 or 10, Wherein the second mobile radio communication network is a Long Term Evolution (LTE) communication network, and the cell-specific reference signal is a cell-specific reference signal (CRS) of the LTE communication network.

13. A non-transitory computer readable storage medium storing program instructions which, when executed by one or more processors of a mobile radio communication device, cause the mobile radio communication device to: generating a physical downlink shared channel and an associated physical downlink shared channel demodulation reference signal according to a modified schedule having at least one symbol shift of the physical downlink shared channel demodulation reference signal relative to a schedule of a cell-specific reference signal, wherein the second mobile radio communications network is configured to transmit the cell-specific reference signal and wherein the position of the demodulation reference signal is defined for all subcarrier spacings of a downlink bandwidth portion in which the physical downlink shared channel is scheduled, in a case where the mobile radio communications device is operating during overlapping communications of a first mobile radio communications network and a second mobile radio communications network, and transmitting said physical downlink shared channel and an associated physical downlink shared channel demodulation reference signal of said first mobile radio communications network, wherein in the physical downlink shared channel, the physical downlink shared channel demodulation reference signal to be transmitted is shifted by a single symbol to avoid transmission on symbols containing a cell-specific reference signal of the second mobile radio communications network as indicated by the first mobile radio communications network, and Therein, the minimum mobile radio communication terminal equipment processing time for physical downlink shared channel processing is increased by one symbol compared to a case where the additional demodulation reference signal symbol of the physical downlink shared channel is not shifted.

14. The non-transitory computer-readable storage medium of claim 13, wherein the mobile radio communication device is a base station or a core network component.

15. The non-transitory computer readable storage medium according to any one of claims 13 or 14, The first mobile radio communication network is a 5G communication network, and the physical downlink shared channel demodulation reference signal is a demodulation reference signal of a 5G NR communication network.

16. The non-transitory computer readable storage medium according to any one of claims 13 or 14, Wherein the second mobile radio communication network is a Long Term Evolution (LTE) communication network, and the cell-specific reference signal is a cell-specific reference signal (CRS) of the LTE communication network.

Images