NR V2X sidelink structure for PSCCH coverage enhancement

By designing new PSCCH and PSSCH structures in 5G NR V2X side link communication and adopting power enhancement technology, the problem of coexistence of unicast links and broadcast operations is solved, the system performance and data rate are improved, and the higher Channel reliability.

CN113678517BActive Publication Date: 2024-11-15APPLE INC
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202080026995.2
Authority / Receiving Office
CN · China
Patent Type
Patents(China)
Current Assignee / Owner
Priority Date
2019-04-08
Filing Date
2020-04-08
Publication Date
2024-11-15
Estimated Expiration
2040-04-08

AI Technical Summary

Technical Problem

In 5G NR V2X side link communication, the prior art is difficult to optimize the coexistence of unicast links and broadcast operations in the same spectrum, resulting in degradation of system performance and lack of effective resource selection methods to avoid conflicts, affecting data rates and reliability sex.

Method used

By designing a new physical side link control channel (PSCCH) and shared channel (PSSCH) structure, power enhancement technology is adopted, and PSSCH transmission is started immediately after PSCCH, avoiding transient periods, ensuring the coverage of PSCCH and PSSCH and Channel quality.

Benefits of technology

This improves the coverage of PSCCH, reduces the resource requirements for channel control information, avoids system performance degradation, and ensures efficient coexistence in mixed unicast and broadcast traffic scenarios.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN113678517B_ABST
    Figure CN113678517B_ABST
Patent Text Reader

Abstract

The present invention discloses a method, system or device, which can multiplex a physical sidelink control channel (PSCCH) and a physical sidelink shared channel (PSSCH). The system can apply power enhancement to the PSCCH. In addition, the method, system or device can perform power enhancement on a portion of the PSSCH corresponding to the frequency resources used by the PSSCH.
Need to check novelty before this filing date? Find Prior Art

Description

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS

[0002] This application claims the benefit of U.S. Provisional Application No. 62 / 831,086, filed April 8, 2019, which is hereby incorporated by reference in its entirety. Technical Field

[0003] The present patent application relates generally to wireless communication systems, and more particularly to sidelink communications. Background Art

[0004] Wireless mobile communication technology uses various standards and protocols to transmit data between base stations and wireless mobile devices. Wireless communication system standards and protocols may include the 3rd Generation Partnership Project (3GPP) Long Term Evolution (LTE) (e.g., 4G) or New Radio (NR) (e.g., 5G); the Institute of Electrical and Electronics Engineers (IEEE) 802.16 standard, which is generally referred to as Worldwide Interoperability for Microwave Access (WiMAX) by industry organizations; and the IEEE 802.11 standard for wireless local area networks (WLANs), which is generally referred to as Wi-Fi by industry organizations. In the 3GPP radio access network (RAN) in an LTE system, a base station may include a RAN node such as an Evolved Universal Terrestrial Radio Access Network (E-UTRAN) Node B (also commonly referred to as an evolved Node B, an enhanced Node B, an eNodeB, or an eNB) and / or a radio network controller (RNC) in the E-UTRAN, which communicates with a wireless communication device referred to as a user equipment (UE). In the fifth generation (5G) wireless RAN, the RAN nodes may include 5G nodes, NR nodes (also called next generation Node B or g NodeB (gNB)).

[0005] The RAN uses radio access technologies (RATs) to communicate between RAN nodes and UEs. The RAN may include a global system for mobile communications (GSM), an enhanced data rate for GSM evolution (EDGE) RAN (GERAN), a universal terrestrial radio access network (UTRAN), and / or an E-UTRAN, which provides access to communication services through a core network. Each RAN in the RAN operates according to a specific 3GPP RAT. For example, GERAN implements GSM and / or EDGE RAT, UTRAN implements Universal Mobile Telecommunications System (UMTS) RAT or other 3GPP RAT, E-UTRAN implements LTE RAT, and NG-RAN implements 5G RAT. In some deployments, E-UTRAN may also implement 5G RAT.

[0006] The frequency bands for 5G NR can be divided into two different frequency ranges. Frequency Range 1 (FR1) includes frequency bands below 6 GHz, some of which may be used by previous standards but can potentially be expanded to cover potential new spectrum products from 410 MHz to 7125 MHz. Frequency Range 2 (FR2) includes frequency bands from 24.25 GHz to 52.6 GHz. The frequency bands in the millimeter wave (mmWave) range of FR2 have a shorter range but higher available bandwidth than the frequency bands in FR1. The skilled person will recognize that these frequency ranges, which are provided by way of example, may vary from time to time or region to region. BRIEF DESCRIPTION OF THE DRAWINGS

[0007] To easily identify the discussion of any particular element or act, the most significant digit(s) in a reference number refers to the drawing number that first introduces the element.

[0008] Figure 1 A first example of resource allocation for PSCCH and associated PSSCH according to one embodiment is shown.

[0009] Figure 2 A second example of resource allocation for a physical sidelink control channel (PSCCH) and an associated PSSCH is shown according to one embodiment.

[0010] Figure 3 A method for power boosting and transmitting a PSCCH and an associated PSSCH according to one embodiment is shown.

[0011] Figure 4 A system according to one embodiment is shown.

[0012] Figure 5 Infrastructure equipment according to one embodiment is shown.

[0013] Figure 6 A platform according to one embodiment is shown.

[0014] Figure 7 An apparatus according to one embodiment is shown.

[0015] Figure 8 An exemplary interface according to one embodiment is shown.

[0016] Fig. 9 Components according to one embodiment are shown. DETAILED DESCRIPTION

[0017] New Radio (NR) vehicle-to-everything (V2X) communication systems will support a variety of use cases and deployment scenarios, including basic safety message exchanges, advanced driving applications, and extended sensor sharing. While basic safety applications can largely reuse LTE channel access designs based on sensing performed on the transmit (TX) side, more advanced applications may require channel access schemes based on a combination of TX-side and receive (RX)-side sensing to achieve higher data rates and reliability. For example, new use cases may primarily use multicast-type or unicast-type sidelink communications, where knowledge of the intended message recipients can help adapt TX and RX behavior to select the best resources in terms of system capacity and link performance.

[0018] In broadcast systems, there is no accurate representation of the intended receivers and the corresponding propagation channels, which limits the methods that can be used to avoid collisions. Transmitter-based channel sensing for resource selection is one such method to avoid collisions. However, transmitter-based channel sensing for resource selection cannot ensure RX channel quality due to multiple challenges such as hidden node interference, in-band emissions, and near-far problems.

[0019] In addition, some systems combine unicast links with broadcast operations. The introduction of unicast links combined with broadcast operations in the same spectrum requires consideration of seamless coexistence of the two communication types. More specifically, it is desirable that the introduction of unicast links coexisting with broadcast systems does not significantly degrade the performance of broadcast operations. Moreover, it is desirable that the performance of unicast systems does not degrade significantly in the case of mixed unicast and broadcast traffic compared to unicast-only scenarios. To ensure such coexistence, distributed communication modes can be designed to take into account different types of links, and unified channel sensing methods and control signaling designs can be employed.

[0020] In order to optimize the operation of the various services mentioned in the same spectrum, the control channel design for the sidelink may play a role.

[0021] Additionally, in the case of sensing-based resource selection, there is the possibility that multiple devices select the same resource for transmission. In order to reduce the amount of packet loss, it is useful to have the possibility to resolve these conflicts and even have the ability to decode all conflicting transmissions. So far, power boosting has not been considered when considering the NR physical sidelink control channel (PSCCH). In the LTE-V2X sidelink, only frequency division multiplexing (FDM) of PSCCH / PSSCH has been introduced. Therefore, it may be beneficial to introduce power boosting.

[0022] However, in order to enable power boost only for PSCCH in NR V2X sidelink but not PSSCH, PSCCH may require a transient period. This transient period may consume a lot of time resources, thus significantly degrading system performance. LTE solution can achieve power boost, but does not support flexible resource allocation for PSCCH / PSSCH for both FDM and TDM via multiplexing.

[0023] In the present disclosure, the design and process of PSCCH are described using the following components: a general PSCCH structure for handling independent and non-independent PSCCHs; and a structure and process for PSCCH carrying sidelink control information (SCI) scheduling for the corresponding physical sidelink shared channel (PSSCH).

[0024] In addition, the present disclosure describes an implementation scheme for introducing power boosting for frequency resources allocated to PSCCH without introducing a transient period before PSSCH. In other words, PSSCH can start immediately after PSCCH using the implementation scheme described herein, thereby significantly improving coverage. In order to prevent the need for transmission gaps due to transient periods, frequency resources that are power boosted in PSCCH should also be power boosted in the corresponding PSSCH. Power boosting not only improves the coverage of PSCCH, but also reduces the amount of resources required assuming a constant SCI size.

[0025] When a PSCCH carries at least the SCI required to decode a PSSCH, the corresponding PSSCH (also called associated PSSCH) is said to be "associated" or "corresponding" to the PSCCH.

[0026] The embodiments described herein may be used by a UE or a network node. Thus, the designs and processes for PSCCH and power boosting techniques may be used by a UE or a network node. In some embodiments, the UE may be a vehicle-to-everything (V2X) UE. In some embodiments, the network node may be an eNB or a gNB or a portion thereof.

[0027] Various operations will be described in turn as multiple discrete operations in a manner that helps to understand the present disclosure. However, the order of description should not be understood to imply that these operations are necessarily order-dependent. Specifically, these operations do not necessarily need to be performed in the order presented.

[0028] Additional details and examples are provided with reference to the following figures. The embodiments of the present disclosure may be understood with reference to the accompanying drawings, wherein like parts are represented by like numbers throughout. The components of the embodiments of the present disclosure as generally described and illustrated in the drawings herein may be arranged and designed in a variety of different configurations. Therefore, the following detailed description of the embodiments of the systems and methods of the present disclosure is not intended to limit the scope of the present disclosure protected by the claims, but merely represents possible embodiments.

[0029] Figure 1 A first example of a resource allocation 100 for a PSCCH and an associated PSSCH according to one embodiment is shown. The resource allocation 100 represents one possible multiplexing option in both frequency and time for the PSSCH (i.e., the combined PSSCH power boost portion 102 and the PSSCH non-power boost portion 104) and the associated PSCCH 106. As shown, a portion of the PSCCH 106 and a portion of the associated PSSCH are transmitted using overlapping time resources in non-overlapping frequency resources, but another portion of the associated PSSCH and / or another portion of the PSCCH 106 is transmitted using non-overlapping time resources.

[0030] In other words, PSCCH 106 and PSSCH are multiplexed such that PSCCH 106 and the first part 108 of PSSCH use overlapping time resources in non-overlapping frequency resources, and the second part 110 of PSSCH uses the frequency resources used by the first part 108 of PSSCH and the frequency resources used by PSSCH in non-overlapping time resources.

[0031] In order to improve the coverage of PSCCH 106, PSCCH 106 is power-enhanced. Power enhancement not only improves the coverage of PSCCH 106, but also reduces the amount of resources required assuming a constant SCI size. However, if PSCCH 106 and PSSCH do not use the same physical antenna and have the same power spectral density (PSD), a transient period between PSCCH 106 and PSSCH will be introduced. This transient period may take a lot of time resources, thereby significantly reducing system performance.

[0032] To prevent the use of transient periods, the same antenna and PSD used for PSCCH 106 can be used for PSSCH. However, if the entire PSSCH has the same amount of power boost as PSCCH 106, then PSCCH 106 will have similar coverage as PSSCH. However, in order to achieve proper system operation for demodulating PSCCH 106, the coverage of PSCCH 106 should be at least slightly larger than the coverage of the corresponding PSSCH. In addition, for other system functions such as independent resource selection via sensing, a larger coverage may be required.

[0033] In order to facilitate the beneficial effect of power boosting PSCCH 106 without introducing transient period, only a part of PSSCH is power boosted. PSSCH power boost part 102 is the part of PSSCH that is power boosted, while PSSCH non-power boost part 104 is not power boosted. As shown in the figure, PSSCH power boost part 102 uses the same frequency resource as PSCCH 106. The PSD of PSSCH power boost part 102 is consistent with the PSD of PSCCH 106. As shown in the figure, PSSCH and PSCCH106 are power boosted by the same amount in the entire transmission time of the frequency range used by PSCCH 106. Therefore, the transmission carried out using the frequency resources used by both PSSCH and PSCCH 106 is power boosted to the same level to achieve the same PSD for the transmission length, while other PSSCH transmissions carried out using the frequency resources not used by PSCCH 106 are not power boosted and have different PSDs.

[0034] PSCCH 106 and PSSCH power boost part 102 have the same PSD and can use the same antenna. Therefore, no transmission gap is introduced, and PSSCH power boost part 102 starts immediately after PSCCH 106. In addition, because PSSCH non-power boost part 104 is not power boosted, PSCCH 106 has a larger coverage than PSSCH.

[0035] Figure 2 A second example of a resource allocation 200 for a PSCCH and associated PSSCH according to one embodiment is shown. In the resource allocation 200, the PSCCH 202 is set to be transmitted at a time resource after the PSSCH has started. The PSCCH 202 is power boosted.

[0036] Use reference Figure 1 The same principles discussed above apply. That is, the PSSCH includes a PSSCH power boost portion 206 that uses the same frequency resources as the PSCCH 202. The PSSCH power boost portion 206 is power boosted at all transmission times and in the frequency range used by the PSCCH. The PSCCH 202 and the PSSCH power boost portion 206 are power boosted to the same level. The PSSCH non-power boost portion 204 is not power boosted.

[0037] PSCCH 202 and PSSCH power boost part 206 have the same PSD and can use the same antenna. Therefore, no transmission gap is introduced. As shown in the figure, there is no gap between PSSCH power boost part 206 and PSCCH 202. In addition, because PSSCH non-power boost part 204 is not power boosted, PSCCH 202 has a larger coverage than PSSCH.

[0038] Figure 3 A method 300 for power boosting and transmitting a PSCCH and an associated PSSCH according to one embodiment is shown. The method 300 may be performed by a UE or a network node.

[0039] In block 302, a UE or network node performing method 300 multiplexes PSCCH and PSSCH. For example, the UE or network node may multiplex PSCCH and PSSCH such that a first portion of PSSCH and PSCCH use overlapping time resources in non-overlapping frequency resources, and a second portion of PSSCH uses frequency resources used by the first portion of PSSCH and frequency resources used by PSSCH in non-overlapping time resources. Examples of such multiplexing are as follows: Figure 1 The resource allocation of 100 and Figure 2 The resource allocation 200 is shown.

[0040] In box 304, the UE or network node performing method 300 determines a power boost level for the PSCCH. The power boost level refers to the amount of power boost to be applied to the transmission. In order to determine the amount of power boost to be applied to the PSCCH, the UE or network node may base the power boost level on one or more of the following parameters: subchannel size, PSCCH allocation size, PSSCH allocation size, PSCCH resource amount, SCI size. For example, in some embodiments, the power boost amount for the PSCCH may be a function of one or more of the following parameters: subchannel size, PSCCH allocation size, PSSCH allocation size, PSCCH resource amount, SCI size. By using these parameters to determine the power boost, the UE or network node may be able to ensure that the PSCCH has sufficient coverage relative to the PSSCH with the lowest modulation and coding scheme.

[0041] In block 306, the UE or network node executing the method 300 power boosts the PSCCH by the determined power boost level.

[0042] In block 308, the UE or network node performing method 300 performs power boosting on a portion of the second portion of the PSSCH corresponding to the frequency resources used by the PSSCH. When the portion of the PSSCH using the same frequency band as the PSCCH is power boosted, the remaining portion of the PSSCH using a different frequency band is not power boosted. Therefore, only a portion of the PSSCH is power boosted. The power boosted portions of the PSSCH and PSCCH are power boosted to the same level at all transmission times and within the frequency range used by the PSCCH.

[0043] In block 310, the UE or network node performing method 300 selects a modulation and coding scheme for the PSSCH. Since different parts of the allocation of the PSSCCH now have different powers, the UE or network node ensures that the modulation and coding scheme selection takes this effect into account. In addition, the channel coding can be equipped to handle allocations with different powers. This can be ensured via different coding blocks (possibly even with different modulation and coding schemes), appropriate interleaving of power boost regions and non-power boost regions, and channel codes that can handle a larger spread in LLR values.

[0044] In some embodiments, the UE or network node may select a modulation and coding scheme for the PSSCH based on the size and power boost level of the PSCCH. In some embodiments, the UE or network node determines the modulation and coding scheme for transmission of the PSSCH based on at least one of a first PSD of a PSSCH in the same frequency band as the PSCCH and a second PSD of a PSSCH in a different frequency band than the PSCCH.

[0045] Channel estimation of the PSSCH may also process physical resource blocks (PRBs) at different powers. This may mean that PRB bundling applicable to the non-enhanced region is applied to the enhanced region in the same manner. In some embodiments, the method 300 also includes performing PSSCH channel estimation by dividing the PSSCH into a first region that is power-enhanced and a second region that is not power-enhanced. In some embodiments, the method 300 also includes performing PSSCH channel estimation by dividing the PSSCH into a first region that is power-enhanced and a second region that is not power-enhanced.

[0046] In block 312, the UE or network node performing method 300 transmits PSSCH and PSCCH using the selected modulation and coding scheme and the determined power boost level. More specifically, the UE or network node may transmit or cause transmission of PSSCH having the same power spectral density (PSD) as PSCCH in the same frequency band as PSCCH; and transmit or cause transmission of PSSCH having a different PSD than PSCCH in a different frequency band than PSCCH. The same antenna may be used for transmission.

[0047] Figure 4 An exemplary architecture of a system 400 of a network according to various embodiments is shown. The following description is provided for an example system 400 operating in conjunction with LTE system standards and 5G 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 802.16 protocols (e.g., WMAN, WiMAX, etc.), and the like.

[0048] like Figure 4 As shown, system 400 includes UE 402 and UE 404. In this example, UE 402 and UE 404 are shown as smart phones (e.g., handheld touch screen mobile computing devices that can connect to one or more cellular networks), but may also include any mobile or non-mobile computing devices, such as consumer electronic devices, mobile phones, smart phones, feature phones, tablet computers, wearable computer devices, personal digital assistants (PDAs), pagers, wireless handheld devices, desktop computers, laptop computers, in-vehicle infotainment (IVI), in-car entertainment (ICE) devices, instrument clusters (ICs), heads-up display (HUD) devices, on-board diagnostic (OBD) devices, dashtop mobile equipment (DME), mobile data terminals (MDTs), electronic engine management systems (EEMS), electronic / engine electronic control units (ECUs), electronic / engine electronic control modules (ECMs), embedded systems, microcontrollers, control modules, engine management systems (EMS), networked or "smart" appliances, MTC devices, M2M, IoT devices, etc.

[0049] In some embodiments, UE 402 and / or UE 404 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, ProSe or D2D 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-lived connections. The IoT UE may execute background applications (e.g., keep-alive messages, status updates, etc.) to facilitate connectivity to the IoT network.

[0050] UE 402 and UE 404 may be configured to be connected, e.g., communicatively coupled, to an access node or radio access node (shown as (R) AN 416). In an embodiment, (R) AN 416 may be an NG RAN or SG RAN, an E-UTRAN, or a traditional RAN, such as a UTRAN or GERAN. As used herein, the term "NG RAN" or the like may refer to an (R) AN 416 operating in an NR or SG system, and the term "E-UTRAN" or the like may refer to an (R) AN 416 operating in an LTE or 4G system. UE 402 and UE 404 utilize connections (or channels) (shown as connection 406 and connection 408, respectively), each connection comprising a physical communication interface or layer (discussed in further detail below).

[0051] In this example, connection 406 and connection 408 are air interfaces to achieve communication coupling, and may be consistent with a cellular communication protocol, such as a GSM protocol, a CDMA network protocol, a PTT protocol, a POC protocol, a UMTS protocol, a 3GPP LTE protocol, a SG protocol, a NR protocol, and / or any other communication protocol discussed herein. In an embodiment, UE 402 and UE 404 may also directly exchange communication data via a ProSe interface 410. ProSe interface 410 may alternatively be referred to as a side link (SL) interface 110, and may include one or more logical channels, including but not limited to PSCCH, PSSCH, PSDCH, and PSBCH.

[0052] UE 404 is shown as being configured to access AP 412 (also referred to as a "WLAN node," "WLAN," "WLAN terminal," "WT," etc.) via connection 414. Connection 414 may include a local wireless connection, such as a connection consistent with any IEEE 802.11 protocol, wherein AP 412 would include wireless fidelity. router. In this example, AP 412 may be connected to the Internet without being connected to the core network of the wireless system (described in further detail below). In various embodiments, UE 404, (R) AN 416, and AP 412 may be configured to utilize LWA operation and / or LWIP operation. LWA operation may involve UE 404 in RRC_CONNECTED configured by RAN node 418 or RAN node 420 to utilize radio resources of LTE and WLAN. LWIP operation may involve UE 404 using WLAN radio resources (e.g., connection 414) via an IPsec protocol tunnel to authenticate and encrypt packets (e.g., IP packets) sent over connection 414. IPsec tunneling may include encapsulating the entire original IP packet and adding a new packet header, thereby protecting the original header of the IP packet.

[0053] (R)AN 416 may include one or more AN nodes, such as RAN node 418 and RAN node 420, that implement connection 406 and connection 408. As used herein, the terms "access node," "access point," and the like may describe equipment that provides radio baseband functionality for data and / or voice connections between a network and one or more users. These access nodes may be referred to as BSs, gNBs, RAN nodes, eNBs, NodeBs, RSUs, TRxPs, or TRPs, 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 nodes," and the like may refer to RAN nodes (e.g., gNBs) operating in NR or SG systems, while the terms "E-UTRAN nodes," and the like may refer to RAN nodes (e.g., eNBs) operating in LTE or 4G systems 400. According to various embodiments, the RAN node 418 or the RAN node 420 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.

[0054] In some embodiments, all or part of RAN node 418 or RAN node 420 may be implemented as one or more software entities running on a server computer as part of a virtual network that may be referred to as a CRAN and / or a virtual baseband unit pool (vBBUP). In these embodiments, CRAN or vBBUP may implement RAN functional splits, such as PDCP splits, where the RRC and PDCP layers are operated by CRAN / vBBUP, while other L2 protocol entities are operated by individual RAN nodes (e.g., RAN node 418 or RAN node 420); MAC / PHY splits, where the RRC, PDCP, RLC, and MAC layers are operated by CRAN / vBBUP, and the PHY layer is operated by individual RAN nodes (e.g., RAN node 418 or RAN node 420); or "lower PHY" splits, where the RRC, PDCP, RLC, MAC layers, and upper portions of the PHY layers are operated by CRAN / vBBUP, and the lower portions of the PHY layers are operated by individual RAN nodes. This virtualization framework allows idle processor cores of RAN node 418 or RAN node 420 to execute other virtualized applications. In some specific implementations, each RAN node may represent a node via each F1 interface ( Figure 4In some implementations, the gNB-DUs may include one or more remote radio heads or RFEMs, and the gNB-CUs may be operated by a server (not shown) located in the (R)AN 416 or by a pool of servers in a manner similar to the CRAN / vBBUP. In addition or alternatively, the RAN node 418 or one or more of the RAN nodes 420 may be a next generation eNB (ng-eNB), which is a RAN node that provides E-UTRA user plane and control plane protocol terminals to the UE 402 and the UE 404 and is connected to the SGC via an NG interface (discussed below). In a V2X scenario, the RAN node 418 or one or more of the RAN nodes 420 may be an RSU or act as an RSU.

[0055] The term "roadside unit" or "RSU" may refer to any traffic infrastructure entity used for V2X communications. 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 roadside that provides connectivity support to passing vehicle UEs (vUEs). The RSU may also include internal data storage circuits 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, and the like. Additionally or alternatively, the RSU may operate on a cellular V2X band to provide the aforementioned low-latency communications as well as other cellular communications services. Additionally 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.

[0056] The RAN node 418 and / or the RAN node 420 may terminate the air interface protocol and may be the first point of contact for the UE 402 and the UE 404. In some embodiments, the RAN node 418 and / or the RAN node 420 may perform various logical functions of the (R)AN 416, 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.

[0057] In an embodiment, UE 402 and UE 404 may be configured to communicate with each other or with RAN node 418 and / or RAN node 420 over a multi-carrier communication channel using OFDM communication signals according to various communication techniques, such as, but not limited to, OFDMA communication techniques (e.g., for downlink communications) or SC-FDMA communication techniques (e.g., for uplink and ProSe or sidelink communications), although the scope of the embodiments is not limited in this respect. The OFDM signal may include multiple orthogonal subcarriers.

[0058] In some embodiments, a downlink resource grid may be used for downlink transmissions from RAN node 418 and / or RAN node 420 to UE 402 and UE 404, 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 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 set 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.

[0059] According to various embodiments, UE 402 and UE 404 and RAN node 418 and / or RAN node 420 communicate (e.g., transmit and receive) data through a licensed medium (also referred to as a "licensed spectrum" and / or a "licensed frequency band") and an unlicensed shared medium (also referred to as an "unlicensed spectrum" and / or an "unlicensed frequency 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 frequency band.

[0060] To operate in the unlicensed spectrum, UE 402 and UE 404 and RAN node 418 or RAN node 420 may operate using LAA, eLAA, and / or feLAA mechanisms. In these implementations, UE 402 and UE 404 and RAN node 418 or RAN node 420 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.

[0061] LBT is a mechanism for equipment (e.g., UE 402 and UE 404, RAN node 418 or RAN node 420, 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, which utilizes at least ED 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 energy over a period of time on an expected transmission band and comparing the sensed RF energy to a predefined or configured threshold.

[0062] Typically, existing systems in the 5 GHz band are WLANs based on IEEE 802.11 technology. WLANs use a contention-based channel access mechanism called CSMA / CA. Here, when a WLAN node (e.g., a mobile station (MS) such as UE 402, AP412, 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 conflicts. The backoff mechanism may be a counter randomly introduced within the CWS that increases exponentially when a conflict occurs and is reset to a minimum value when the transmission is successful. The LBT mechanism designed for LAA is somewhat similar to the CSMA / CA of WLAN. In some specific implementations, the LBT process for a DL or UL transmission burst (including PDSCH or PUSCH transmission) may have a LAA contention window of variable length between X and Y ECCA slots, where X and Y are the minimum and maximum values ​​of the CWS of LAA. In one example, the minimum CWS for LAA transmissions may be 9 microseconds (μs); however, the size of the CWS and MCOT (eg, transmission burst) may be based on government regulatory requirements.

[0063] The LAA mechanism is built on the CA technology of the LTE-Advanced system. In CA, each aggregated carrier is called a CC. A CC can have a bandwidth of 1.4, 3, 5, 10, 15, or 20 MHz, and up to five CCs can be aggregated, so the maximum aggregated bandwidth is 100 MHz. In an FDD system, the number of aggregated carriers can 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 system, the number of CCs and the bandwidth of each CC are typically the same for DL ​​and UL.

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

[0065] The PDSCH carries user data and higher layer signaling to the UE 402 and the UE 404. The PDCCH carries, among other information, information about the transport format and resource allocation related to the PDSCH channel. It may also inform the UE 402 and the UE 404 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 the UE 404 within the cell) may be performed at either the RAN node 418 or the RAN node 420 based on channel quality information fed back from either the UE 402 and the UE 404. Downlink resource allocation information may be sent on the PDCCH for (e.g., allocated to) each of the UE 402 and the UE 404.

[0066] PDCCH uses CCE 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. Four quadrature phase shift keying (QPSK) symbols can be mapped to each REG. Depending on the size of the DCI 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).

[0067] 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 that uses PDSCH resources for control information transmission. One or more ECCEs may be used to transmit EPDCCH. Similar to the above, each ECCE may correspond to nine sets of four physical resource elements, referred to as EREG. In some cases, ECCE may have other numbers of EREGs.

[0068] The RAN node 418 or the RAN node 420 may be configured to communicate with each other via an interface 422. In an embodiment where the system 400 is an LTE system (e.g., when the CN 430 is an EPC), the interface 422 may be an X2 interface. The X2 interface may be defined between two or more RAN nodes (e.g., two or more eNBs, etc.) connected to the EPC, and / or between two eNBs connected to the EPC. 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 to the SeNB; information about the successful delivery of PDCP PDUs from the SeNB to the UE 402 in sequence for user data; information about PDCP PDUs that are not delivered to the UE 402; information about the current minimum expected buffer size at the Se NB 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.

[0069] In an embodiment where the system 400 is a SG or NR system (e.g., when the CN 430 is an SGC), the interface 422 may be an Xn interface. The Xn interface is defined between two or more RAN nodes (e.g., two or more gNBs, etc.) connected to the SGC, between a RAN node 418 (e.g., a gNB) and an eNB connected to the SGC, and / or between two eNBs connected to a 5GC (e.g., CN 430). 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 UE402 in a connected mode (e.g., a CM connection) includes functions for managing UE mobility in a connected mode between one or more RAN nodes 418 or RAN nodes 420. The mobility support may include context transfer from the old (source) serving RAN node 418 to the new (target) serving RAN node 420; and control of the user plane tunnel between the old (source) serving RAN node 418 and the new (target) serving RAN node 420. The protocol stack of Xn-U may include a transport network layer built on an Internet Protocol (IP) transport layer, and a GTP-U layer on top of a UDP 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. 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.

[0070] (R)AN 416 is shown as being communicatively coupled to the core network - in this embodiment, communicatively coupled to CN 430. CN 430 may include one or more network elements 432 configured to provide various data and telecommunication services to customers / subscribers (e.g., users of UE 402 and UE 404) connected to CN 430 via (R)AN 416. The components of CN 430 may be implemented in one physical node or separate physical nodes, including 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 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 430 may be referred to as a network slice, and a logical instance of a portion of CN 430 may be referred to as a network sub-slice. The 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.

[0071] In general, the application server 434 may be an element that provides applications that use IP bearer resources with the core network (e.g., UMTS PS domain, LTE PS data services, etc.). The application server 434 may also be configured to support one or more communication services (e.g., VoIP sessions, PTT sessions, group communication sessions, social network services, etc.) for the UE 402 and UE 404 via the EPC. The application server 434 may communicate with the CN 430 via the IP communication interface 436.

[0072] In an embodiment, CN 430 may be an SGC, and (R)AN 116 may be connected to CN 430 via an NG interface 424. In an embodiment, NG interface 424 may be divided into two parts: an NG user plane (NG-U) interface 426, which carries traffic data between RAN node 418 or RAN node 420 and UPF; and an S1 control plane (NG-C) interface 428, which is a signaling interface between RAN node 418 or RAN node 420 and AMF.

[0073] In an embodiment, CN 430 may be an SG CN, while in other embodiments, CN 430 may be an EPC. In the case where CN 430 is an EPC, (R)AN 116 may be connected to CN 430 via an S1 interface 424. In an embodiment, S1 interface 424 may be divided into two parts: an S1 user plane (S1-U) interface 426, which carries traffic data between RAN node 418 or RAN node 420 and S-GW; and an S1-MME interface 428, which is a signaling interface between RAN node 418 or RAN node 420 and MME.

[0074] Figure 5 An example of infrastructure equipment 500 according to various embodiments is shown. The infrastructure equipment 500 can be implemented as a base station, a radio head, a RAN node, an AN, an application server, and / or any other element / device discussed herein. In other examples, the infrastructure equipment 500 can be implemented in or by a UE.

[0075] The infrastructure equipment 500 includes application circuits 502, baseband circuits 504, one or more radio front end modules 506 (RFEM), memory circuits 508, power management integrated circuits (shown as PMIC 510), power tee circuits 512, network controller circuits 514, network interface connectors 520, satellite positioning circuits 516, and user interface circuits 518. In some embodiments, the infrastructure equipment 500 may include additional elements such as memory / storage devices, displays, cameras, sensors, or input / output (I / O) interfaces. In other embodiments, these components may be included in more than one device. For example, the circuits may be separately included in more than one device for CRAN, vBBU, or other similar implementations. The application circuits 502 include, for example, but not limited to, one or more processors (or processor cores), cache memory, and one or more low dropout regulators (LDOs), interrupt controllers, serial interfaces such as SPI, I 2C 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 the application circuit 502 may be coupled to or may include a memory / storage element and may be configured to execute instructions stored in the memory / storage device to enable various applications or operating systems to run on the infrastructure equipment 500. In some specific implementations, 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.

[0076] The processor of the application circuit 502 may include, for example, one or more processor cores (CPUs), one or more application processors, one or more graphics processing units (GPUs), 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 (DSPs), one or more FPGAs, one or more PLDs, one or more ASICs, one or more microprocessors or controllers, or any suitable combination thereof. In some embodiments, the application circuit 502 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 502 may include one or more Intel FPGAs. or Processor: Advanced Micro Devices (AMD) Processor, Accelerated Processing Unit (APU) or Processor; 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, the infrastructure equipment 500 may not utilize the application circuit 502, and instead may include a dedicated processor / controller to process IP data received, for example, from the EPC or 5GC.

[0077] In some implementations, the application circuit 502 may include one or more hardware accelerators, which may be microprocessors, programmable processing devices, etc. 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), 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 implementations, the circuits of the application circuit 502 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, etc. of the various embodiments discussed herein. In such embodiments, the circuitry of the application circuit 502 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. The baseband circuit 504 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.

[0078] The user interface circuitry 518 may include one or more user interfaces designed to enable a user to interact with the infrastructure equipment 500 or a peripheral component interface designed to enable a peripheral component to interact with the infrastructure equipment 500. 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.

[0079] The radio front end module 506 may include a millimeter wave (mmWave) radio front end module (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 millimeter wave RFEM. The RFIC may include connections to one or more antennas or antenna arrays, and the RFEM may be connected to multiple antennas. In alternative implementations, both millimeter wave and sub-millimeter wave radio functions may be implemented in the same physical radio front end module 506 that combines both millimeter wave antennas and sub-millimeter waves.

[0080] The memory circuit 508 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); and 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 508 may be implemented as one or more of: a solder-in package integrated circuit, a socket memory module, and a plug-in memory card.

[0081] The PMIC 510 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 512 may provide power extracted from a network cable to provide both power and data connections for the infrastructure equipment 500 using a single cable.

[0082] The network controller circuit 514 may provide connectivity to the network using a standard network interface protocol such as Ethernet, Ethernet based on a GRE tunnel, Ethernet based on Multi-Protocol Label Switching (MPLS), or some other suitable protocol. Network connectivity may be provided to / from the infrastructure equipment 500 via the network interface connector 520 using a physical connection, which may be an electrical connection (commonly referred to as a "copper interconnect"), an optical connection, or a wireless connection. The network controller circuit 514 may include one or more dedicated processors and / or FPGAs for communicating using one or more of the aforementioned protocols. In some implementations, the network controller circuit 514 may include multiple controllers for providing connectivity to other networks using the same or different protocols.

[0083] The positioning circuit 516 includes a circuit for receiving and decoding signals transmitted / broadcasted by a positioning network of a global satellite navigation system (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 516 includes various hardware elements (e.g., including hardware devices such as switches, filters, amplifiers, antenna elements, etc. for facilitating OTA communications) to communicate with components of the positioning network such as navigation satellite constellation nodes. In some embodiments, the positioning circuit 516 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 516 may also be part of or interact with the baseband circuit 504 and / or the radio front end module 506 to communicate with nodes and components of the positioning network. The positioning circuit 516 may also provide location data and / or time data to the application circuit 502, which may use the data to synchronize operations with various infrastructures, etc. Figure 5 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.

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

[0085] Application circuit 602 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 C or general programmable serial interface module, RTC, timer-counter (including interval timer and watchdog timer), general IO, memory card controller (such as SDMMC or similar controller), USB interface, MIPI interface and JTAG test access port. The processor (or core) of the application circuit 602 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 platform 600. In some specific implementations, 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.

[0086] The processor of the application circuit 602 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 602 may include or may be a dedicated processor / controller for operating according to various embodiments herein.

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

[0088] Additionally or alternatively, the application circuit 602 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 602 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 602 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.

[0089] Baseband circuit 604 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.

[0090] The radio front end module 606 may include a millimeter wave (mmWave) radio front end module (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 millimeter wave RFEM. The RFIC may include connections to one or more antennas or antenna arrays, and the RFEM may be connected to multiple antennas. In alternative implementations, both millimeter wave and sub-millimeter wave radio functions may be implemented in the same physical radio front end module 606 that combines both millimeter wave antennas and sub-millimeter waves.

[0091] The memory circuit 608 may include any number and type of memory devices for providing a quantitative system memory. For example, the memory circuit 608 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 (NVM), 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 608 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 608 may be implemented as one or more of 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 608 may be an on-chip memory or register associated with the application circuit 602. In order to provide persistent storage of information such as data, applications, operating systems, etc., the memory circuit 608 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 600 may be combined with a memory device obtained from and Three-dimensional (3D) cross-point (XPOINT) memory.

[0092] Removable memory 614 may include devices, circuits, housings / casings, ports or receptacles, etc., for coupling portable data storage devices to platform 600. 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.

[0093] Platform 600 may also include interface circuitry (not shown) for connecting external devices to platform 600. External devices connected to platform 600 via the interface circuitry include sensors 610 and electromechanical components (shown as EMC 612), as well as removable memory devices coupled to removable memory 614.

[0094] Sensors 610 include devices, modules, or subsystems that are designed to detect events or changes in their environment and 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.

[0095] EMC 612 includes the equipment, module or subsystem that purpose is to enable platform 600 to change its state, position and / or orientation or move or control mechanism or (sub) system.In addition, EMC 612 can be configured to generate message / signaling and send message / signaling to other components of platform 600 to indicate the current state of EMC612.The example of EMC 612 includes one or more power switches, relays (including electromechanical relays (EMR) and / or solid-state relays (SSR)), actuators (e.g., valve actuators, etc.), audible sound generators, visual warning devices, motors (e.g., DC motors, stepper motors, etc.), wheels, thrusters, propellers, claws, clamps, hooks and / or other similar electromechanical components.In an embodiment, platform 600 is configured to operate one or more EMC 612 based on one or more capture events and / or instructions or control signals received from service providers and / or various clients.In some specific implementations, interface circuits can connect platform 600 with positioning circuit 622. The positioning circuit 622 includes a circuit for receiving and decoding signals transmitted / broadcasted by a positioning network of a GNSS. Examples of navigation satellite constellations (or GNSS) may include the United States' GPS, Russia's GLONASS, the European Union's Galileo system, China's Beidou navigation satellite system, regional navigation systems or GNSS augmentation systems (e.g., NAVIC, Japan's QZSS, France's DORIS, etc.), etc. The positioning circuit 622 includes various hardware elements (e.g., including hardware devices such as switches, filters, amplifiers, antenna elements, etc. for facilitating OTA communications) to communicate with components of the positioning network such as navigation satellite constellation nodes. In some embodiments, the positioning circuit 622 may include a micro PNT IC that uses a master timing clock to perform position tracking / estimation without GNSS assistance. The positioning circuit 622 may also be part of or interact with the baseband circuit 604 and / or the radio front-end module 606 to communicate with nodes and components of the positioning network. Positioning circuitry 622 may also provide position data and / or time data to application circuitry 602 , which may use the data to synchronize operations with various infrastructure (eg, radio base stations) for use in turn-by-turn navigation applications, and the like.

[0096] In some implementations, the interface circuit may connect the platform 600 to a near field communication circuit (shown as NFC circuit 620). The NFC circuit 620 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 620 and an NFC-enabled device (e.g., an "NFC touch point") external to the platform 600. The NFC circuit 620 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 620 by executing 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 620, or initiate data transfer between the NFC circuit 620 and another active NFC device (e.g., a smart phone or an NFC-enabled POS terminal) near the platform 600.

[0097] The driver circuit 624 may include software and hardware elements for controlling specific devices embedded in, attached to, or otherwise communicatively coupled to the platform 600. The driver circuit 624 may include various drivers to allow other components of the platform 600 to interact with or control various input / output (I / O) devices that may be present in or connected to the platform 600. For example, the driver circuit 624 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 600, a sensor driver for obtaining sensor readings of the sensor 610 and controlling and allowing access to the sensor 610, an EMC driver for obtaining actuator positions of the EMC 612 and / or controlling and allowing access to the EMC 612, 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.

[0098] A power management integrated circuit (shown as PMIC 616) (also referred to as a "power management circuit") can manage the power provided to various components of the platform 600. Specifically, the PMIC 616 can control power selection, voltage scaling, battery charging, or DC-DC conversion with respect to the baseband circuit 604. When the platform 600 is capable of being powered by a battery 618, for example, when the device is included in a UE, the PMIC 616 may generally be included.

[0099] In some embodiments, the PMIC 616 may control or otherwise be part of various power saving mechanisms of the platform 600. For example, if the platform 600 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 600 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 600 may transition to the RRC_Idle state, in which the device is disconnected from the network and no operations such as channel quality feedback, handover, etc. are performed. The platform 600 enters a very low power state and performs paging, in which the device wakes up periodically again to listen to the network and then powers off again. The platform 600 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.

[0100] The battery 618 can provide power to the platform 600, but in some examples, the platform 600 can be installed and deployed in a fixed location and can have a power source coupled to the power grid. The battery 618 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 specific implementations, such as in V2X applications, the battery 618 can be a typical lead-acid car battery.

[0101] In some implementations, the battery 618 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 600 to track the state of charge (SoCh) of the battery 618. The BMS may be used to monitor other parameters of the battery 618, such as the state of health (SoH) and state of function (SoF) of the battery 618 to provide fault prediction. The BMS may transmit information about the battery 618 to the application circuit 602 or other components of the platform 600. The BMS may also include an analog-to-digital (ADC) converter that allows the application circuit 602 to directly monitor the voltage of the battery 618 or the current from the battery 618. The battery parameters may be used to determine actions that the platform 600 may perform, such as transmission frequency, network operation, sensing frequency, etc.

[0102] A power block or other power source coupled to the grid can be coupled to the BMS to charge the battery 618. In some examples, the power block can be replaced with a wireless power receiver to obtain power wirelessly, for example, through a loop antenna in the computer platform 600. 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 618 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.

[0103] The user interface circuit 626 includes various input / output (I / O) devices present in or connected to the platform 600, and includes one or more user interfaces designed to implement user interaction with the platform 600 and / or a peripheral component interface designed to implement interaction with the peripheral components of the platform 600. The user interface circuit 626 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 circuit may include any number and / or combination of audio or visual displays, particularly including one or more simple visual outputs / indicators, such as binary state 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 the output of characters, graphics, multimedia objects, etc. is generated or produced by the operation of the platform 600. The output device circuit may also include a speaker or other audio emitting device, a printer, etc. In some embodiments, the sensor 610 may be used as an input device circuit (e.g., an image capture device, a motion capture device, etc.) and one or more EMCs may be used as an output device circuit (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 circuit including an NFC controller and a processing device coupled to an antenna element. The peripheral component interface may include, but is not limited to, a non-volatile memory port, a USB port, an audio jack, a power interface, etc.

[0104] Although not shown, the components of platform 600 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.

[0105] Figure 7 Example components of a device 700 according to some embodiments are shown. In some embodiments, the device 700 may include at least an application circuit 702, a baseband circuit 704, a radio frequency (RF) circuit (shown as RF circuit 720), a front-end module (FEM) circuit (shown as FEM circuit 730), one or more antennas 732, and a power management circuit (PMC) (shown as PMC 734) coupled together as shown. The components of the illustrated device 700 may be included in a UE or a RAN node. In some embodiments, the device 700 may include fewer elements (e.g., the RAN node cannot utilize the application circuit 702, but includes a processor / controller to process IP data received from the EPC). In some embodiments, the device 700 may include additional elements, such as a memory / storage device, a display, a camera, a sensor, or an input / output (I / O) interface. In other embodiments, the following components may be included in more than one device (e.g., the circuit may be included separately in more than one device for a cloud-RAN (C-RAN) specific implementation).

[0106] The application circuit 702 may include one or more application processors. For example, the application circuit 702 may include circuits such as, but not limited to, one or more single-core or multi-core processors. The one or more processors may include any combination of general-purpose processors and special-purpose processors (e.g., graphics processors, application processors, etc.). These processors may be coupled to or may include memory / storage devices, and may be configured to execute instructions stored in the memory / storage devices to enable various applications or operating systems to run on the device 700. In some embodiments, the processor of the application circuit 702 may process IP data packets received from the EPC.

[0107] The baseband circuit 704 may include circuits such as, but not limited to, one or more single-core or multi-core processors. The baseband circuit 704 may include one or more baseband processors or control logic components to process baseband signals received from the receive signal path of the RF circuit 720 and generate baseband signals for the transmit signal path of the RF circuit 720. The baseband circuit 704 may interact with the application circuit 702 to generate and process baseband signals and control the operation of the RF circuit 720. For example, in some embodiments, the baseband circuit 704 may include a third generation (3G) baseband processor (3G baseband processor 706), a fourth generation (4G) baseband processor (4G baseband processor 708), a fifth generation (5G) baseband processor (5G baseband processor 710), or other baseband processors 712 of other existing generations, generations under development or generations to be developed in the future (e.g., second generation (2G), sixth generation (6G), etc.). The baseband circuit 704 (e.g., one or more processors in the baseband processor) may handle various radio control functions that can communicate with one or more radio networks via the RF circuit 720. In other embodiments, some or all of the functions of the illustrated baseband processor may be included in a module stored in the memory 718 and executed via the central processing unit (CPU 714). 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 circuitry of the baseband circuitry 704 may include fast Fourier transform (FFT), precoding, or constellation mapping / demapping functions. In some embodiments, the encoding / decoding circuitry of the baseband circuitry 704 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.

[0108] In some embodiments, the baseband circuit 704 may include a digital signal processor (DSP), such as one or more audio DSPs 716. The audio DSP 716 may include elements for compression / decompression and echo cancellation, and may include other suitable processing elements in other embodiments. In some embodiments, the components of the baseband circuit may be appropriately combined in a single chip, a single chipset, or disposed on the same circuit board. In some embodiments, some or all of the components of the baseband circuit 704 and the application circuit 702 may be implemented together, such as on a system on a chip (SOC).

[0109] In some embodiments, the baseband circuit 704 may provide communications compatible with one or more radio technologies. For example, in some embodiments, the baseband circuit 704 may support communications with an Evolved Universal Terrestrial Radio Access Network (EUTRAN) or other wireless metropolitan area network (WMAN), wireless local area network (WLAN), wireless personal area network (WPAN). Embodiments in which the baseband circuit 704 is configured to support radio communications of more than one wireless protocol may be referred to as multi-mode baseband circuits.

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

[0111] In some embodiments, the receive signal path of the RF circuit 720 may include a mixer circuit 722, an amplifier circuit 724, and a filter circuit 726. In some embodiments, the transmit signal path of the RF circuit 720 may include a filter circuit 726 and a mixer circuit 722. The RF circuit 720 may also include a synthesizer circuit 728 for synthesizing frequencies used by the mixer circuit 722 of the receive signal path and / or the transmit signal path. In some embodiments, the mixer circuit 722 of the receive signal path may be configured to down-convert the RF signal received from the FEM circuit 730 based on the synthesized frequency provided by the synthesizer circuit 728. The amplifier circuit 724 may be configured to amplify the down-converted signal, and the filter circuit 726 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 the baseband circuit 704 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, mixer circuit 722 of the receive signal path may include a passive mixer, although the scope of the embodiments is not limited in this respect.

[0112] In some embodiments, the mixer circuit 722 of the transmit signal path can be configured to up-convert an input baseband signal based on a synthesized frequency provided by the synthesizer circuit 728 to generate an RF output signal for the FEM circuit 730. The baseband signal can be provided by the baseband circuit 704 and can be filtered by the filter circuit 726.

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

[0114] 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 720 may include an analog-to-digital converter (ADC) and a digital-to-analog converter (DAC) circuit, and the baseband circuit 704 may include a digital baseband interface to communicate with the RF circuit 720.

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

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

[0117] The synthesizer circuit 728 may be configured to synthesize an output frequency based on the frequency input and the divider control input for use by the mixer circuit 722 of the RF circuit 720. In some embodiments, the synthesizer circuit 728 may be a fractional-N / N+1 synthesizer.

[0118] 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 baseband circuitry 704 or application circuitry 702 (such as an application processor) 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 application circuitry 702.

[0119] The synthesizer circuit 728 of the RF circuit 720 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 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 D-type flip-flop set. 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.

[0120] In some embodiments, the synthesizer circuit 728 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 720 can include an IQ / polarity converter.

[0121] The FEM circuitry 730 may include a receive signal path that may include circuitry configured to operate on RF signals received from one or more antennas 732, amplify the receive signal, and provide an amplified version of the receive signal to the RF circuitry 720 for further processing. The FEM circuitry 730 may also include a transmit signal path that may include circuitry configured to amplify transmit signals provided by the RF circuitry 720 for transmission by one or more of the one or more antennas 732. In various embodiments, amplification by either the transmit signal path or the receive signal path may be accomplished only in the RF circuitry 720, only in the FEM circuitry 730, or in both the RF circuitry 720 and the FEM circuitry 730.

[0122] In some embodiments, the FEM circuit 730 may include a TX / RX switch to switch between transmit mode and receive mode operation. The FEM circuit 730 may include a receive signal path and a transmit signal path. The receive signal path of the FEM circuit 730 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 720). The transmit signal path of the FEM circuit 730 may include a power amplifier (PA) to amplify the input RF signal (e.g., provided by the RF circuit 720), and one or more filters to generate an RF signal for subsequent transmission (e.g., through one or more of the one or more antennas 732).

[0123] In some embodiments, the PMC 734 can manage the power provided to the baseband circuit 704. Specifically, the PMC 734 can control power selection, voltage scaling, battery charging, or DC-DC conversion. When the device 700 is capable of being powered by a battery, for example, when the device 700 is included in a UE, the PMC 734 can generally be included. The PMC 734 can improve power conversion efficiency while providing the desired specific implementation size and heat dissipation characteristics.

[0124] Figure 7 PMC 734 is shown coupled only to baseband circuitry 704. However, in other embodiments, PMC 734 may additionally or alternatively be coupled to other components (such as, but not limited to, application circuitry 702, RF circuitry 720, or FEM circuitry 730) and perform similar power management operations for these components.

[0125] In some embodiments, the PMC 734 may control or otherwise be part of various power saving mechanisms of the device 700. For example, if the device 700 is in the RRC_Connected state, where the device is still connected to the RAN node because it expects to receive traffic immediately, then after a period of inactivity, the device may enter a state known as discontinuous reception mode (DRX). During this state, the device 700 may be powered off for short time intervals, thereby saving power.

[0126] If there is no data traffic activity for an extended period of time, the device 700 may transition to the RRC_Idle state, in which the device is disconnected from the network and does not perform operations such as channel quality feedback, handover, etc. The device 700 enters a very low power state and performs paging, in which the device periodically wakes up again to listen to the network and then powers down again. The device 700 cannot receive data in this state, and in order to receive data, the device must transition back to the RRC_Connected state.

[0127] An additional power saving mode can keep a device from using the network for longer than the paging interval (which can range from a few seconds to several hours). During this time, the device is completely unable to connect to the network and can be completely powered down. Any data sent during this time will be significantly delayed, and it is assumed that the delay is acceptable.

[0128] The processor of the application circuit 702 and the processor of the baseband circuit 704 can be used to execute elements of one or more instances of the protocol stack. For example, the processor of the baseband circuit 704 can be used alone or in combination to perform layer 3, layer 2, or layer 1 functions, while the processor of the application circuit 702 can utilize data received from these layers (e.g., packet data) and further perform layer 4 functions (e.g., transport communication protocol (TCP) and user datagram protocol (UDP) layers). As mentioned herein, layer 3 may include a radio resource control (RRC) layer, which will be described in further detail below. As mentioned herein, layer 2 may include a medium access control (MAC) layer, a radio link control (RLC) layer, and a packet data convergence protocol (PDCP) layer, which will be described in further detail below. As mentioned herein, layer 1 may include a physical (PHY) layer of a UE / RAN node, which will be described in further detail below.

[0129] Figure 8 An exemplary interface 800 of a baseband circuit according to some embodiments is shown. As described above, Figure 7 The baseband circuit 704 may include a 3G baseband processor 706, a 4G baseband processor 708, a 5G baseband processor 710, other baseband processors 712, a CPU 714, and a memory 718 for use by the processors. As shown, each of the processors may include a corresponding memory interface 802 for sending / receiving data to / from the memory 718.

[0130] The baseband circuit 704 may also include one or more interfaces to communicatively couple to other circuits / devices, such as a memory interface 804 (e.g., an interface for sending / receiving data to / from a memory external to the baseband circuit 704), an application circuit interface 806 (e.g., an interface for sending / receiving data to / from a memory external to the baseband circuit 704), and an application circuit interface 807 (e.g., an interface for sending / receiving data to / from a memory external to the baseband circuit 704). Figure 7 The application circuit 702 sends / receives data), the RF circuit interface 808 (for example, for sending / receiving data to / from the application circuit 702), Figure 7 an interface for sending / receiving data to / from a RF circuit 720), a wireless hardware connection interface 810 (e.g., for sending / receiving data to / from a near field communication (NFC) component, Parts (e.g. Low power consumption), components and other communication components to send / receive data) and a power management interface 812 (for example, an interface for sending / receiving power or control signals to / from PMC 734).

[0131] Fig. 9 is a block diagram illustrating a component 900 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, Fig. 9 A schematic diagram of hardware resources 902 is shown, which includes one or more processors 912 (or processor cores), one or more memory / storage devices 918, and one or more communication resources 920, each of which may be communicatively coupled via a bus 922. For embodiments in which node virtualization (e.g., NFV) is utilized, a hypervisor 904 may be executed to provide an execution environment for one or more network slices / sub-slices to utilize the hardware resources 902.

[0132] Processor 912 (e.g., 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 digital signal processor (DSP) (such as a baseband processor), an application specific integrated circuit (ASIC), a radio frequency integrated circuit (RFIC), another processor, or any suitable combination thereof) may include, for example, processor 914 and processor 916.

[0133] The memory / storage device 918 may include main memory, disk storage, or any suitable combination thereof. The memory / storage device 918 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.

[0134] The communication resources 920 may include an interconnect or network interface component or other suitable device to communicate with one or more peripheral devices 906 or one or more databases 908 via the network 910. For example, the communication resources 920 may include a wired communication component (e.g., for coupling via a universal serial bus (USB)), a cellular communication component, an NFC component, Parts (e.g. Low power consumption), components and other communication components.

[0135] The instructions 924 may include software, programs, applications, applets, applications, or other executable code for causing at least any one of the processors 912 to perform any one or more of the methodologies discussed herein. The instructions 924 may reside completely or partially in at least one of the processors 912 (e.g., in a cache memory of the processor), the memory / storage device 918, or any suitable combination thereof. In addition, any portion of the instructions 924 may be transmitted to the hardware resources 902 from any combination of the peripheral devices 906 or the database 908. Thus, the memory of the processor 912, the memory / storage device 918, the peripheral devices 906, and the database 908 are examples of computer-readable and machine-readable media.

[0136] 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 examples 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 examples section below.

[0137] Examples

[0138] The following examples relate to additional embodiments.

[0139] Embodiment 1A may include multiplexing of PSCCH and PSSCH in both time and frequency, wherein both physical channels are power boosted to the same level at all transmission times and within the frequency range used by the PSCCH.

[0140] Embodiment 2A may include power boosting of PSCCH / PSSCH, wherein the power boosting is a function of one or more of the following parameters: subchannel size, PSCCH allocation size, PSSCH allocation size, PSCCH resource amount, SCI size.

[0141] Embodiment 3A may include MCS selection for the PSSCH that takes into account the size and power boost level of the PSCCH.

[0142] Embodiment 4A may include performing PSSCH channel estimation by dividing into a power boosted region and a non-power boosted region.

[0143] Embodiment 5A may include a method comprising: determining a power boost to be applied to a physical sidelink control channel (PSCCH); and transmitting or causing transmission of the PSCCH with the determined power boost.

[0144] Embodiment 6A may include a method according to embodiment 5A or another embodiment herein, wherein the method further comprises transmitting or causing transmission of a physical sidelink shared channel (PSSCH) having the same power spectral density (PSD) as the PSCCH in the same frequency band as the PSCCH.

[0145] Embodiment 7A may include a method according to embodiment 6A or another embodiment herein, wherein the PSSCH is transmitted immediately after the PSCCH in the time domain.

[0146] Embodiment 8A may include a method according to Embodiments 6A to 7A or another embodiment herein, the method further comprising transmitting or causing transmission of the PSSCH having a different PSD than the PSCCH in a different frequency band than the PSCCH.

[0147] Embodiment 9A may include a method according to Embodiment 6A to 8A or another embodiment herein, wherein the PSSCH and the PSCCH are transmitted using the same antenna.

[0148] Embodiment 10A may include a method according to embodiments 6A to 9A or another embodiment herein, the method further comprising determining a modulation and coding scheme for transmission of the PSSCH based on the PSD of the PSSCH in the same frequency band as the PSCCH and / or the PSD of the PSSCH in a different frequency band from the PSCCH.

[0149] Embodiment 11A may include a method according to embodiment 10A or another embodiment herein, wherein determining the MCS includes determining a first MCS to be applied to PSSCH resources in the same frequency band as the PSCCH and a second MCS to be applied to PSSCH resources in a different frequency band than the PSCCH.

[0150] Embodiment 12A may include a method according to embodiments 5A to 11A or another embodiment herein, wherein the power boost is determined based on one or more of: subchannel size; PSCCH allocation size; PSSCH allocation size; PSCCH resource amount; or sidelink control information (SCI) size.

[0151] Embodiment 13A may include a method according to Embodiment 5A to 12A or another embodiment herein, wherein the method is performed by a UE or a portion thereof.

[0152] Embodiment 14A may include a method according to embodiment 13A or another embodiment herein, wherein the UE is a vehicle-to-everything (V2X) UE.

[0153] Embodiment 15A may include a method according to Embodiments 5A to 12A or another embodiment herein, wherein the method is performed by an eNB or a gNB or a portion thereof.

[0154] Embodiment 1B A method for user equipment (UE), comprising: multiplexing PSCCH and PSSCH, so that: the first part of the PSSCH and the PSCCH use overlapping time resources in non-overlapping frequency resources, and the second part of the PSSCH uses the frequency resources used by the first part of the PSSCH and the frequency resources used by the PSSCH in non-overlapping time resources. The method also includes power boosting the PSCCH; and power boosting a portion of the second part of the PSSCH corresponding to the frequency resources used by the PSSCH.

[0155] Embodiment 2B is based on the method of embodiment 1B, wherein the PSSCH is power-boosted at all transmission times and within the frequency range used by the PSCCH.

[0156] Embodiment 3B is based on the method of embodiment 1B, wherein the PSSCH and the PSCCH are power boosted by the same amount.

[0157] Embodiment 4B is according to the method described in Embodiment 1B, and the method also includes determining the power enhancement amount of the PSCCH, wherein the power enhancement amount of the PSCCH and the PSSCH is a function of one or more of the following parameters: subchannel size, PSCCH allocation size, PSSCH allocation size, PSCCH resource amount, SCI size.

[0158] Embodiment 5B The method according to embodiment 1B further includes selecting a modulation and coding scheme for the PSSCH based on the size and power boost level of the PSCCH.

[0159] Embodiment 6B According to the method of Embodiment 1B, the method further includes performing PSSCH channel estimation by dividing the PSSCH into a first region with power boosting and a second region without power boosting.

[0160] Embodiment 7B is according to the method described in Embodiment 1B, and the method further includes: transmitting or causing transmission of the PSSCH having the same power spectral density (PSD) as the PSCCH in the same frequency band as the PSCCH; and transmitting or causing transmission of the PSSCH having a different PSD from the PSCCH in a frequency band different from the PSCCH.

[0161] Embodiment 8B is based on the method described in Embodiment 1B, wherein the PSSCH and the PSCCH are transmitted using the same antenna.

[0162] Embodiment 9B is according to the method described in Embodiment 1B, and the method also includes determining a modulation and coding scheme for transmission of the PSSCH based on at least one of a first PSD of the PSSCH in the same frequency band as the PSCCH and a second PSD of the PSSCH in a different frequency band from the PSCCH.

[0163] Embodiment 10B is according to the method described in Embodiment 9B, wherein the determining of the modulation and coding scheme comprises: determining a first modulation and coding scheme to be applied to PSSCH resources in the same frequency band as the PSCCH, and determining a second modulation and coding scheme to be applied to PSSCH resources in a different frequency band from the PSCCH.

[0164] Embodiment 11B A non-transitory computer-readable storage medium, the computer-readable storage medium comprising instructions, which when executed by a network node causes the network node to multiplex PSCCH and PSSCH, so that: the first part of the PSSCH and the PSCCH use overlapping time resources in non-overlapping frequency resources, and the second part of the PSSCH uses the frequency resources used by the first part of the PSSCH and the frequency resources used by the PSSCH in non-overlapping time resources. The instructions also cause the network node to: power-enhance the PSCCH; and power-enhance a portion of the second part of the PSSCH corresponding to the frequency resources used by the PSSCH.

[0165] Embodiment 12B The computer-readable storage medium of Embodiment 11B, wherein the PSSCH is power boosted at all transmission times and within the frequency range used by the PSCCH.

[0166] Embodiment 13B The computer-readable storage medium of Embodiment 11B, wherein the PSSCH and the PSCCH are power boosted by the same amount.

[0167] Embodiment 14B is a computer-readable storage medium according to embodiment 11B, wherein the instructions further configure the computer to determine a power enhancement amount of the PSCCH, wherein the power enhancement amount of the PSCCH and the PSSCH is a function of one or more of the following parameters: subchannel size, PSCCH allocation size, PSSCH allocation size, PSCCH resource amount, SCI size.

[0168] Embodiment 15B The computer-readable storage medium of Embodiment 11B, wherein the instructions further configure the computer to select a modulation and coding scheme for the PSSCH based on a size and a power boost level of the PSCCH.

[0169] Embodiment 16B The computer-readable storage medium of Embodiment 11B, wherein the instructions further configure the computer to perform PSSCH channel estimation by dividing the PSSCH into a first region that is power boosted and a second region that is not power boosted.

[0170] Embodiment 17B is a computer-readable storage medium according to Embodiment 11B, wherein the instructions further configure the computer to: transmit or cause transmission of the PSSCH having a PSD with the PSCCH in the same frequency band as the PSCCH; and transmit or cause transmission of the PSSCH having a PSD different from the PSCCH in a frequency band different from the PSCCH.

[0171] Embodiment 18B The computer-readable storage medium of Embodiment 11B, wherein the PSSCH and the PSCCH are transmitted using the same antenna.

[0172] Embodiment 19B is a computer-readable storage medium according to Embodiment 11B, wherein the instructions further configure the computer to determine a modulation and coding scheme for transmission of the PSSCH based on at least one of a first PSD of the PSSCH in the same frequency band as the PSCCH and a second PSD of the PSSCH in a different frequency band from the PSCCH.

[0173] Embodiment 20B is a computer-readable storage medium according to embodiment 19B, wherein determining the modulation and coding scheme comprises: determining a first modulation and coding scheme to be applied to PSSCH resources in the same frequency band as the PSCCH, and determining a second MCS to be applied to PSSCH resources in a different frequency band from the PSCCH.

[0174] Embodiment 21B A computing device, comprising: a baseband processing unit; and a memory storing instructions, wherein when the baseband processing unit executes the instructions, the device multiplexes PSCCH and PSSCH, so that: the first part of the PSSCH and the PSCCH use overlapping time resources in non-overlapping frequency resources, and the second part of the PSSCH uses the frequency resources used by the first part of the PSSCH and the frequency resources used by the PSSCH in non-overlapping time resources. The device is also used to: power-enhance the PSCCH; and power-enhance a portion of the second part of the PSSCH corresponding to the frequency resources used by the PSSCH.

[0175] Embodiment 22B is a computing device according to Embodiment 21B, wherein the PSSCH is power-boosted at all transmission times and within the frequency range used by the PSCCH, and wherein the PSSCH and the PSCCH are power-boosted by the same amount.

[0176] Embodiment 1C may include an apparatus comprising means for performing one or more elements of a method described in or related to any of the above embodiments or any other method or process described herein.

[0177] Embodiment 2C may include one or more non-transitory computer-readable media, which include instructions that, when executed by one or more processors of an electronic device, cause the electronic device to perform one or more elements of a method described in or related to any of the above embodiments or any other method or process described herein.

[0178] Embodiment 3C may include a device comprising logic components, modules, or circuits for performing one or more elements of the methods described in or related to any of the above embodiments or any other methods or processes described herein.

[0179] Embodiment 4C may include any of the methods, techniques or processes or parts or components thereof described in or related to the above embodiments.

[0180] Embodiment 5C may include a device comprising: one or more processors and one or more computer-readable media, wherein the one or more computer-readable media include instructions that, when executed by the one or more processors, cause the one or more processors to perform a method, technique, process, or portion thereof described in or related to any one of the above embodiments.

[0181] Embodiment 6C may include a signal or a portion or component thereof as described in or related to any of the above embodiments.

[0182] Embodiment 7C may include a datagram, packet, frame, segment, protocol data unit (PDU) or message or a portion or component thereof as described in or related to any of the above embodiments, or as otherwise described in the present disclosure.

[0183] Embodiment 8C may include a signal encoded with data or a portion or component thereof as described in any of the above embodiments or related thereto, or as otherwise described in this disclosure.

[0184] Embodiment 9C may include a signal or a portion or component thereof encoded with a datagram, packet, frame, segment, PDU or message as described in or related to any of the above embodiments, or described in other ways in the present disclosure.

[0185] Embodiment 10C may include an electromagnetic signal carrying computer-readable instructions, wherein execution of the computer-readable instructions by one or more processors will cause the one or more processors to perform a method, technique, or process, or a portion thereof, described in or related to any of the above embodiments.

[0186] Embodiment 11C may include a computer program comprising instructions, wherein execution of the program by a processing element causes the processing element to perform a method, technique, or process, or a portion thereof, described in or related to any one of the above embodiments.

[0187] Embodiment 12C may include signals in a wireless network as shown and described herein.

[0188] Embodiment 13C may include a method of communicating in a wireless network as shown and described herein.

[0189] Embodiment 14C may include a system for providing wireless communications as shown and described herein.

[0190] Embodiment 15C may include an apparatus for providing wireless communications as shown and described herein.

[0191] 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 embodiments to the precise form disclosed. Modifications and variations are possible in view of the above teachings or may be obtained from the practice of the various embodiments.

[0192] Embodiments and implementations of the systems and methods described herein may include various operations that may be embodied in machine executable instructions to be executed by a computer system. A computer system may include one or more general or special purpose computers (or other electronic devices). A computer system may include hardware components that include specific logic components for performing operations, or may include a combination of hardware, software, and / or firmware.

[0193] It should be appreciated that the systems described herein include descriptions of specific embodiments. These embodiments may be combined into a single system, partially incorporated into other systems, separated into multiple systems, or otherwise divided or combined. In addition, it is contemplated that parameters, attributes, aspects, etc. of one embodiment may be used in another embodiment. For clarity, these parameters, attributes, aspects, etc. are described only in one or more embodiments, and it should be appreciated that unless otherwise stated herein, these parameters, attributes, aspects, etc. may be combined with or substituted for parameters, attributes, aspects, etc. of another embodiment.

[0194] It is understood that the use of personally identifiable information should be subject to privacy policies and practices that are generally recognized to meet or exceed industry or government requirements for maintaining user privacy. Specifically, personally identifiable information data should be managed and processed to minimize the risk of unintentional or unauthorized access or use, and the nature of the authorized use should be clearly stated to users.

[0195] Although the foregoing has been described in considerable detail for the sake of clarity, it will be apparent that certain changes and modifications may be made without departing from the principles of the invention. It should be noted that there are many alternative ways to implement both the processes and the apparatus described herein. Therefore, the embodiments of the present invention are to be regarded as illustrative rather than restrictive, and the specification is not limited to the details given herein, but may be modified within the scope and equivalents of the appended claims.

Claims

1. A method for user equipment UE, the method comprising: The physical side link control channel PSCCH and the physical side link shared channel PSSCH are multiplexed so that: The first part of the PSSCH and the PSCCH use overlapping time resources in non-overlapping frequency resources, and The second part of the PSSCH uses the frequency resources used by the first part of the PSSCH and the frequency resources used by the PSCCH in non-overlapping time resources; Performing power boosting on the PSCCH; as well as A portion of the second portion of the PSSCH corresponding to the frequency resources used by the PSCCH is power-boosted, wherein the power-boosted portion of the PSSCH uses the same frequency resources as the PSCCH in non-overlapping time resources.

2. The method according to claim 1, wherein the PSSCH is power-boosted at all transmission times and in a frequency range used by the PSCCH.

3. The method of claim 1, wherein the PSSCH and the PSCCH are power boosted by the same amount.

4. The method of claim 1 , further comprising determining a power boost amount for the PSCCH, wherein the power boost amount for the PSCCH and the PSSCH is a function of one or more parameters, the one or more parameters comprising: Subchannel size, PSCCH allocation size, PSSCH allocation size, PSCCH resource amount, SCI size.

5. The method of claim 1, further comprising selecting a modulation and coding scheme for the PSSCH based on a size and a power boost level of the PSCCH. 6 . The method of claim 1 , further comprising performing PSSCH channel estimation by dividing the PSSCH into a first region that is power-boosted and a second region that is not power-boosted.

7. The method according to claim 1, further comprising: transmitting the PSSCH in the same frequency band as the PSCCH or causing transmission of the PSSCH having the same power spectral density PSD as the PSCCH; as well as The PSSCH is transmitted in a different frequency band than the PSCCH or caused to be transmitted with a different PSD than the PSCCH. The method according to claim 1 , wherein the PSSCH and the PSCCH are transmitted using the same antenna.

9. The method according to claim 1 further includes determining a modulation and coding scheme for transmission of the PSSCH based on at least one of a first power spectral density (PSD) of the PSSCH in the same frequency band as the PSCCH and a second PSD of the PSSCH in a different frequency band from the PSCCH.

10. The method of claim 9, wherein said determining said modulation and coding scheme comprises: determining a first modulation and coding scheme to be applied to a PSSCH resource in the same frequency band as the PSCCH, and A second modulation and coding scheme is determined to be applied to a PSSCH resource in a different frequency band than the PSCCH.

11. A non-transitory computer-readable storage medium comprising instructions that, when executed by a network node, cause the network node to: Multiplexing PSCCH and PSSCH makes: The first part of the PSSCH and the PSCCH use overlapping time resources in non-overlapping frequency resources, and The second part of the PSSCH uses the frequency resources used by the first part of the PSSCH and the frequency resources used by the PSCCH in non-overlapping time resources; Performing power boosting on the PSCCH; as well as A portion of the second portion of the PSSCH corresponding to the frequency resources used by the PSCCH is power-boosted, wherein the power-boosted portion of the PSSCH uses the same frequency resources as the PSCCH in non-overlapping time resources.

12. The computer-readable storage medium of claim 11, wherein the PSSCH is power boosted at all transmission times and within a frequency range used by the PSCCH.

13. The computer-readable storage medium of claim 11, wherein the PSSCH and the PSCCH are power boosted by the same amount.

14. The computer-readable storage medium of claim 11, wherein the instructions further configure the network node to determine a power boost amount for the PSCCH, wherein the The power boost amount of the PSCCH and the PSSCH is a function of one or more of the following parameters: subchannel size, PSCCH allocation size, PSSCH allocation size, PSCCH resource amount, SCI size.

15. The computer-readable storage medium of claim 11, wherein the instructions further configure the network node to select a modulation and coding scheme for the PSSCH based on a size and a power boost level of the PSCCH.

16. The computer-readable storage medium of claim 11, wherein the instructions further configure the network node to perform PSSCH channel estimation by dividing the PSSCH into a first region that is power boosted and a second region that is not power boosted.

17. The computer-readable storage medium of claim 11, wherein the instructions further configure the network node to: transmitting the PSSCH in the same frequency band as the PSCCH or causing transmission of the PSSCH having the same PSD as the PSCCH; and The PSSCH is transmitted in a different frequency band than the PSCCH or caused to be transmitted with a different PSD than the PSCCH.

18. The computer-readable storage medium of claim 11, wherein the PSSCH and the PSCCH are transmitted using the same antenna.

19. A computer-readable storage medium according to claim 11, wherein the instructions further configure the network node to determine a modulation and coding scheme for transmission of the PSSCH based on at least one of a first PSD of the PSSCH in the same frequency band as the PSCCH and a second PSD of the PSSCH in a different frequency band from the PSCCH.

20. The computer-readable storage medium of claim 19, wherein said determining the modulation and coding scheme comprises: determining a first modulation and coding scheme to be applied to a PSSCH resource in the same frequency band as the PSCCH, and A second MCS is determined to be applied to PSSCH resources in a different frequency band than the PSCCH.

21. A computing device, the computing device comprising: Baseband processing unit; and a memory storing instructions that, when executed by the baseband processing unit, cause the apparatus to: Multiplexing PSCCH and PSSCH makes: The first part of the PSSCH and the PSCCH use overlapping time resources in non-overlapping frequency resources, and The second part of the PSSCH uses the frequency resources used by the first part of the PSSCH and the frequency resources used by the PSCCH in non-overlapping time resources; Performing power boost on the PSCCH; as well as A portion of the second portion of the PSSCH corresponding to the frequency resources used by the PSCCH is power-boosted, wherein the power-boosted portion of the PSSCH uses the same frequency resources as the PSCCH in non-overlapping time resources.

22. The computing device of claim 21, wherein the PSSCH is power-boosted at all transmission times and within a frequency range used by the PSCCH, and wherein the PSSCH and the PSCCH are power-boosted by the same amount.