Downlink control channel signaling for UL coexistence of multiple service types

Abstract

Various embodiments herein describe uplink (UL) multiplexing of transmissions with different reliability and / or latency requirements. Specifically, one or more indications of affected resources may be communicated to one or more user equipments so that ongoing or upcoming UL transmissions can be adjusted to avoid adversely affecting other UL transmissions that may occur on shared resources. Other embodiments may be described and claimed.

Description

[0001] Cross-references to Related Patent Applications

[0002] This application claims priority to U.S. Provisional Patent Application No. 62 / 760,339, filed on November 13, 2018. Technical Field

[0003] Embodiments of the present invention generally relate to the field of wireless communication technology. Background Art

[0004] New Radio (NR) systems will support the coexistence of various services and traffic communications in a common carrier. However, the transmission of packets of different service types may affect each other. BRIEF DESCRIPTION OF THE DRAWINGS

[0005] Embodiment will be more readily understood by the following detailed description in conjunction with the accompanying drawings. In order to facilitate this description, similar reference numerals represent similar structural elements. In each figure of the accompanying drawings, embodiment is shown by way of example and not limitation.

[0006] Figure 1 An operational flow / algorithm structure according to some embodiments is shown.

[0007] Figure 2 Another operational flow / algorithm structure according to some embodiments is shown.

[0008] Figure 3 Another operational flow / algorithm structure according to some embodiments is shown.

[0009] Figure 4 An exemplary architecture of a network system according to various embodiments is shown.

[0010] Figure 5 Examples of infrastructure equipment according to various embodiments are shown.

[0011] Figure 6 Depicted are exemplary components of a computer platform or device according to various embodiments.

[0012] Figure 7 Depicted are exemplary components of baseband circuitry and RF-side modules according to various embodiments.

[0013] Figure 8 is a block diagram illustrating components capable of reading instructions from a machine-readable medium or computer-readable medium (e.g., a non-transitory machine-readable storage medium) and performing any one or more of the methodologies discussed herein, according to some exemplary embodiments. DETAILED DESCRIPTION

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

[0015] Various embodiments herein describe uplink (UL) multiplexing of transmissions with different reliability and / or delay requirements. Specifically, how one or more indications of affected resources can be transmitted to one or more user equipments (UEs, e.g., Figure 4 In the example embodiment, UE 401a and / or UE 401b in the shared resource may be configured to adjust ongoing or upcoming UL transmissions to avoid adversely affecting other UL transmissions that may occur in the shared resource. Transmissions of one service type may be more urgent than another service type and may take precedence over other ongoing transmissions.

[0016] For example, various embodiments herein relate to scenarios where, for a given service type, the indication of affected resources may not be directed to a UE, but rather any UE may be configured to receive it. NR UEs may support communications of various traffic types and, over time, may have critical (e.g., stringent reliability and / or latency requirements) and non-critical communications, and when receiving an indication of affected resources, the UE's behavior upon receiving the indication may be different.

[0017] A group-common indication of affected resources where two or more UL transmissions may collide / overlap may be sent to a group of UEs, where the UE behavior upon receipt of the indication may be preconfigured via higher layer signaling or via dynamic signaling. For example, UEs belonging to the group may adopt one or more of the following behaviors upon receiving the indication:

[0018] ● Cancel any transfers that overlap with the affected resource

[0019] ● Increase the power of transmissions that overlap with the affected resources

[0020] ● Reduce the power of transmissions that overlap with the affected resources

[0021] A shared resource indication sent to a group of UEs in a service-agnostic manner may facilitate more flexible UL coexistence, eg, different UEs in the group may have different behaviors adapted to their transmission requirements.

[0022] In the present disclosure, a UL multiplexing scenario is described in which one or more UL transmissions of one or more service types (such as enhanced mobile broadband (eMBB), ultra-reliable low latency communication (URLLC), massive machine type communication (mMTC), etc.) may receive overlapping resource allocations from the network on a carrier. To ensure performance requirements for critical communications (such as those requiring very high reliability and / or low latency), the network may indicate, through some dynamic signaling, the resources where overlap or collision will occur, and the UE receiving the indication may take one or more appropriate actions. In some embodiments, a first UE and a second UE belonging to the group receiving the indication may have different behaviors. For example, the first UE may cancel or reduce the signal power of its transmissions that overlap with the affected resources, while the second UE may increase the signal power of its transmissions. One or more UL transmissions of the UE may be modified. The UE's UL data transmission may be based on UL scheduling downlink control information (DCI) or based on a UL configured grant, such as type 1 and / or 2. Other UL transmissions of the UE that may be modified include sounding reference signal (SRS) transmissions, physical uplink control channel (PUCCH) transmissions, and / or physical random access channel (PRACH) transmissions. It is also possible that the UE's UL transmissions that may be modified based on the indication may include multiple of data transmission, PUCCH, PRACH, and / or SRS.

[0023] Unless otherwise mentioned, the duration referred to herein may be one or more time slots, one or more symbols, or a combination thereof. UL coexistence may occur in licensed and / or unlicensed bands below or above 6 GHz, in frequency division duplex (FDD) and time division duplex (TDD) systems, and / or in any bandwidth portion of given parameters, such as 15 kHz, 30 kHz, 60 kHz, 120 kHz, etc. Note that the UL transmission cancellation indication may alternatively be referred to as a UL transmission interruption indication or a UL transmission preemption indication. A control resource set (CORESET) refers to a downlink (DL) control resource set, which may include a set of contiguous and / or non-contiguous physical resource blocks (PRBs) and a set of symbols. A CORESET may include one or more search spaces in which DL control channel signaling (such as a UL transmission cancellation indication or a UL grant) may be monitored / detected.

[0024] As discussed above, in some embodiments, a group-common DCI indication containing information about UL time-frequency resources is sent to a group of UEs. One or more UEs belonging to the group (e.g., all UEs in the group or a subset of UEs in the group) may have one or more of the following behaviors upon receiving the indication:

[0025] • If it overlaps with the indicated resource, cancel its transmission.

[0026] o The UE may cancel only the portion of its transmission that overlaps with the indicated resources.

[0027] o The UE may cancel its remaining transmissions starting (in time and / or frequency) from the indicated resources. In some implementations, the UE may cancel its entire transmission if the indication is received before its transmission.

[0028] ● Modify / adjust the UL transmission power of its UL transmissions.

[0029] o The UE may modify / adjust the transmit power only for the portion where its transmission overlaps with the indicated resources.

[0030] o The UE may modify / adjust the transmit power of its remaining transmissions starting from the indicated resources (in time and / or frequency).In some embodiments, the UE may adjust / modify the transmit power of its entire UL transmission if the indication is received before its transmission.

[0031] • The UE may cancel its transmission for the portion overlapping with the indicated resources and adjust / modify the transmission power for the remaining portion of the UL transmission.

[0032] In some embodiments, the UE may be configured with higher layer signaling, such as RRC signaling, regarding the behavior of its UL transmission assumptions upon receiving an indication. Note that all UEs belonging to a group monitoring an indication may or may not have the same behavior.

[0033] Alternatively or in addition, there may be one or more flags / bit fields comprising one or more bits present in the indication and the resource indication that may dynamically indicate to one or more UEs monitoring the indication the behavior to be performed with respect to their UL transmissions. In some embodiments, the flag may be specific to one or more UEs in the group to indicate behavior for those one or more UEs that is different from the behavior of one or more other UEs. For example, in some embodiments, an indication may include multiple flags for different groups of one or more UEs to indicate the behavior to be performed by those respective UEs.

[0034] In one embodiment, if the UE is configured to adjust / modify / increase transmission power, the UE may perform one or more of the following:

[0035] • Applying an offset to an existing or most recent UL power control parameter, such as a closed loop power control command, eg, an adjustment value δ.

[0036] o The offset may be for one of, for example, +1 dB, +2 dB, +3 dB, +4 dB, +5 dB, +6 dB, +7 dB, +8 dB, +9 dB, +10 dB. Negative values (e.g., one of -1 dB to -10 dB) are also possible.

[0037] o The offset may be applied only for cases where the UL transmission is modified / affected by the indication.

[0038] o The offset may be configured for the UE as part of higher layer configuration, for example using UE-specific RRC signaling.

[0039] • Apply a pre-configured value of the adjustment value δ.

[0040] o The value may be for, for example, one of +1 dB, +2 dB, +3 dB, +4 dB, +5 dB, +6 dB, +7 dB, +8 dB, +9, +10 dB. Negative values (e.g., one of -1 dB to -10 dB) are also possible.

[0041] o Adjustments can be applied as absolute values for just one instance of a transfer or cumulatively on top of previous parameters.

[0042] • Apply pre-configured values for the open-loop parameters P0 and α.

[0043] • Apply a closed loop power control procedure different from the last instructed procedure.

[0044] o A pre-configured adjustment value d can be applied to another closed-loop process.

[0045] In one example, the resource indication may include one or more of the following:

[0046] A field containing a bitmap of M×N bits (M and N may be equal to or greater than 1), where each bit indicates the status of a time-frequency partition. The status may be, for example, no preemption / collision / overlap or expected preemption / collision / overlap. There may be M=>1 time partitions and N=>1 frequency partitions configured within the indicated or configured time-frequency reference region.

[0047] • A field indicating the granularity of the resource indication in time and / or frequency, eg an indication of the value of M and / or N.

[0048] • A field indicating the reference time-frequency region, for example, the starting position of the region, the duration / range in time and / or the duration / range in frequency.

[0049] In one example, if the reference region is configured, the UE may obtain the configuration through higher layer signaling. For example, the frequency domain span of the reference region may be x% of the entire UL effective BWP or BWP. The value x may be, for example, 50%, 25%, etc. In one example, the time domain region addressed by the indication may start after an offset from the location of the reception indication of the CORESET. The time domain region may be a symbol group or a time slot or a time slot group for a given parameter. For example, M may be one of 1, 2, 4, 7, 14. N may be one of 1, 2, 3, 4, etc. In one example, the bitmap may have a total of 14 bits. Therefore, a combination of M and N values may be used such that the product of M×N is equal to 14 (e.g., M=1 and N=14, M=2 and N=7, M=7 and N=2, M=14 and N=1). In some embodiments, M may be greater than N (e.g., in the time-frequency region, there are more time partitions than frequency partitions). In other embodiments, N may be greater than M (eg, in the time-frequency domain, there are more frequency partitions than time partitions).

[0050] In one example, for a given parameter, the UE may monitor for an indication every N=>1 symbol.For example, the UE may monitor for an indication of any UL transmission in a periodic manner and / or after resource allocation.

[0051] In one example, the UE is configured to monitor for an indication via high-layer signaling. The UE may be configured with an RNTI associated with the indication, which may be transmitted in a PDCCH. The PDCCH may provide indications via one or more carriers. A UE with UL transmissions on different carriers may have the same or different behaviors in multiple carriers. The PDCCH may have a carrier-specific field or subfield containing resource indications and / or other UE behavior-related indications. In another example, different RNTIs may be configured for the UE for the purpose of indicating associated behaviors, for example, different RNTIs may be configured and used to scramble a cyclic redundancy check (CRC) of a group-common DCI to indicate one of the following: UL transmission cancellation, or UL transmission with modified transmission power (for example, including possible different indications of using different RNTIs to indicate UL power increase (for example, applying a positive power offset, etc.), or UL transmission with reduced power (for example, applying a negative power offset, etc.)).

[0052] In one example, the RNTI associated with the PDCCH may imply one or more of the UE behaviors identified above.

[0053] The PDCCH may be received in a UE-specific search space or a common search space.

[0054] According to various embodiments, other examples of configurations for monitoring indications (eg, behavior and / or range of monitoring indications in time / frequency) may be used by one or more UEs.

[0055] Figure 1 An operational flow / algorithm structure 100 according to some embodiments is shown. The operational flow / algorithm structure 100 may be partially or completely performed by a UE (e.g., UE 401a and / or UE 401b, discussed below) or a component thereof. For example, in some embodiments, the operational flow / algorithm structure 100 may be performed by baseband circuitry implemented in the UE.

[0056] At 104, the operational flow / algorithm structure 100 may include receiving a time-frequency resource allocation for an uplink transmission in a cell. The uplink transmission may be, for example, an uplink data transmission, a sounding reference signal (SRS) transmission, and / or another suitable uplink transmission.

[0057] At 108, the operational flow / algorithm structure 100 may further include configuration information of a time-frequency region in a receiving cell, wherein the time-frequency region includes a plurality of configured partitions. In some embodiments, the configuration information may be received via RRC signaling. The configured partitions may include a first number (e.g., M) of partitions in the time domain and a second number (e.g., N) of partitions in the frequency domain. In some embodiments, the configuration information may indicate the number of partitions included in the time-frequency region (e.g., the number of partitions in the time domain and / or the number of partitions in the frequency domain). In addition or alternatively, the configuration information may further include an indication of the start position, end position, duration, and / or frequency range of the time-frequency region.

[0058] At 112, the operational flow / algorithm structure 100 may also include receiving a downlink control information (DCI) message including an indication of the priority of one or more partitions within the second resource. In some embodiments, the indication may include a bitmap, wherein individual bits of the bitmap indicate whether the priority status is indicated for the time-frequency partition associated with the corresponding individual bit. In some embodiments, the indication may also include a field for indicating the granularity of the time-frequency partition of the bitmap. In addition or alternatively, the indication may also include an indication of the start position, end position, duration, and / or frequency range of the time-frequency region associated with the indication.

[0059] At 116 , the operational flow / algorithm structure 100 may further include determining that the time-frequency resource allocation overlaps with at least one partition of the time-frequency region for which the priority indication was received.

[0060] At 120, the operational flow / algorithm structure 100 may further include canceling a remaining portion of the uplink transmission that remains after the determination based on the determination. In some embodiments, the remaining portion is the entire uplink transmission (e.g., if the DCI is processed in time before the uplink transmission begins). In other embodiments, the remaining portion may be only a portion of the uplink transmission (e.g., if the processing of the DCI is not completed before the uplink transmission begins).

[0061] In other embodiments, the UE may perform different modifications of its uplink transmissions based on the indication, such as increasing or decreasing the transmit power of the uplink transmissions, as further described herein.

[0062] Figure 2 Another operational flow / algorithm structure 200 is shown, according to some embodiments. The operational flow / algorithm structure 200 may be performed in part or in whole by a next-generation base station (gNB, e.g., RAN nodes 411a and / or 411b, discussed below) or components thereof. For example, in some embodiments, the operational flow / algorithm structure 200 may be performed by baseband circuitry implemented in the gNB. One or more aspects of the operational flow / algorithm structure 200 may additionally or alternatively be performed by one or more other network elements of the wireless cellular network (e.g., network element 422, discussed below).

[0063] At 204, the operational flow / algorithm structure 200 may include encoding a message indicating a first resource allocation for an uplink transmission from a first UE to a gNB in a wireless cellular network for transmission to the UE. The uplink transmission may be, for example, an uplink data transmission, a sounding reference signal (SRS) transmission, and / or another suitable uplink transmission.

[0064] At 208, the operational flow / algorithm structure 200 may also include determining that a second resource allocation for the second UE overlaps with one or more time-frequency resources of the first resource allocation. In one example, the first resource allocation may be for enhanced mobile broadband (eMBB) or massive machine type communication (mMTC), and the second resource allocation may be for ultra-reliable and low-latency communication (URLLC).

[0065] At 212, the operational flow / algorithm structure 200 may also include encoding an indication of one or more time-frequency resources for transmission to the UE, the indication of the one or more time-frequency resources instructing the UE to cancel the remaining portion of the uplink transmission remaining after processing the indication. In some embodiments, the indication may include a bitmap, wherein individual bits of the bitmap indicate whether an overlapping state is indicated for the time-frequency partition associated with the corresponding individual bit. In some embodiments, the indication may also include a field for indicating the granularity of the time-frequency partition of the bitmap. In addition or alternatively, the indication may also include an indication of the start position, end position, duration, and / or frequency range of the frequency region associated with the indication.

[0066] In some embodiments, the remainder is the entire uplink transmission (e.g., if the DCI is processed in time before the uplink transmission begins). In other embodiments, the remainder may be only a portion of the uplink transmission (e.g., if processing of the DCI is not complete before the uplink transmission begins).

[0067] In other embodiments, the indication may instruct the UE to perform different modifications of its uplink transmissions based on the indication, such as increasing or decreasing the transmission power of the uplink transmissions, as further described herein.

[0068] Figure 3 An operational flow / algorithm structure 300 according to some embodiments is illustrated. The operational flow / algorithm structure 300 may be partially or completely performed by a UE (e.g., UE 401a and / or UE 401b, discussed below) or a component thereof. For example, in some embodiments, the operational flow / algorithm structure 300 may be performed by baseband circuitry implemented in the UE.

[0069] At 304, the operational flow / algorithm structure 300 may include receiving a first resource allocation for an uplink transmission in a wireless cellular network.

[0070] At 308, the operational flow / algorithm structure 300 may further include receiving, in a downlink control information (DCI) message provided to a plurality of UEs including the first UE and the second UE, an indication of one or more time-frequency resources that overlap with the first resource allocation for the second UE.

[0071] At 312, the operational flow / algorithm structure 300 may also include modifying the uplink transmission based on the indication, wherein the modification is different from the modification to be performed by the second UE based on the indication. For example, the first UE may reduce the transmission power of its uplink transmission or cancel all or part of its uplink transmission, while the second UE may increase the transmission power of its uplink transmission. Alternatively, the first UE may increase the transmission power of its uplink transmission, while the second UE may reduce the transmission power of its uplink transmission or cancel all or part of its uplink transmission. In some embodiments, the first UE may receive configuration information to indicate the modification to be performed by the first UE based on the indication.

[0072] System and implementation

[0073] 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 exemplary 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 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.

[0074] like Figure 4 As shown, system 400 includes UE 401a and UE 401b (collectively referred to as "UE 401"). UE 401a and / or UE 401b may correspond to the UEs described above. For example, UE 401 may receive an indication of overlap on one or more time-frequency resources allocated to UE 401a and / or 401b for uplink transmission, as described herein.

[0075] In this example, UE 401 is shown as a smart phone (e.g., a handheld touchscreen mobile computing device that can connect to one or more cellular networks), but may also include any mobile or non-mobile computing device, such as a consumer electronic device, a mobile phone, a smart phone, a feature phone, a tablet computer, a wearable computer device, a personal digital assistant (PDA), a pager, a wireless handheld device, a desktop computer, a laptop computer, an in-vehicle infotainment (IVI), an in-car entertainment (ICE) device, an instrument cluster (IC), a head-up display (HUD) device, an on-board diagnostic (OBD) device, a dashtop mobile equipment (DME), a mobile data terminal (MDT), an electronic engine management system (EEMS), an electronic / engine electronic control unit (ECU), an electronic / engine electronic control module (ECM), an embedded system, a microcontroller, a control module, an engine management system (EMS), a connected or "smart" appliance, an MTC device, an M2M device, an IoT device, etc.

[0076] In some embodiments, any of the UEs 401 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 a PLMN, ProSe or D2D communications, a sensor network, or an IoT network. M2M or MTC data exchanges may be machine-initiated data exchanges. The IoT network describes interconnected IoT UEs, which may include uniquely identifiable embedded computing devices (within the Internet infrastructure) with short-term connections. The IoT UE may execute background applications (e.g., keep-alive messages, status updates, etc.) to facilitate connectivity to the IoT network.

[0077] UE 401 may be configured to connect, e.g., be communicatively coupled, to RAN 410. In an embodiment, RAN 410 may be an NG RAN or 5G RAN, E-UTRAN, or a legacy RAN, such as UTRAN or GERAN. As used herein, the term "NG RAN," etc., may refer to RAN 410 operating in NR or 5G systems 400, while the term "E-UTRAN," etc., may refer to RAN 410 operating in LTE or 4G systems 400. UE 401 utilizes connections (or channels) 403 and 404, respectively, each of which includes a physical communication interface or layer (discussed in further detail below).

[0078] In this example, connections 403 and 404 are shown as air interfaces to achieve communication coupling and may be consistent with a cellular communication protocol, such as a GSM protocol, a CDMA network protocol, a PTT protocol, a POC protocol, a UMTS protocol, a 3GPP LTE protocol, a 5G protocol, a NR protocol, and / or any other communication protocol discussed herein. In an embodiment, the UE 401 may directly exchange communication data via a ProSe interface 405. The ProSe interface 405 may alternatively be referred to as an SL interface 405 and may include one or more logical channels, including but not limited to a PSCCH, a PSSCH, a PSDCH, and a PSBCH.

[0079] UE 401b is shown as being configured to access AP 406 (also referred to as "WLAN node 406," "WLAN 406," "WLAN terminal 406," "WT 406," etc.) via connection 407. Connection 407 may comprise a local wireless connection, such as a connection consistent with any IEEE 802.11 protocol, wherein AP 406 would include Wireless Fidelity. router. In this example, AP 406 is shown connected to the Internet without being connected to the core network of the wireless system (described in further detail below). In various embodiments, UE 401b, RAN 410, and AP 406 can be configured to utilize LWA operation and / or LWIP operation. LWA operation can involve UE 401b in RRC CONNECTED being configured by RAN nodes 411a-b to utilize radio resources of LTE and WLAN. LWIP operation can involve UE 401b using WLAN radio resources (e.g., connection 407) via an IPsec protocol tunnel to authenticate and encrypt packets (e.g., IP packets) sent over connection 407. IPsec tunneling can include encapsulating the entire original IP packet and adding a new packet header, thereby protecting the original header of the IP packet.

[0080] RAN 410 includes one or more AN nodes or RAN nodes 411a and 411b (collectively referred to as "RAN nodes 411") that enable connections 403 and 404. 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 411 (e.g., gNBs) operating in NR or 5G systems 400, while the terms "E-UTRAN nodes" and the like may refer to RAN nodes 411 (e.g., eNBs) operating in LTE or 4G systems 400. According to various embodiments, the RAN node 411 may be implemented as one or more 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.

[0081] In some embodiments, all or part of the RAN node 411 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, the CRAN or vBBUP may implement a RAN functional split, such as a PDCP split, where the RRC and PDCP layers are operated by the CRAN / vBBUP, while other L2 protocol entities are operated by individual RAN nodes 411; a MAC / PHY split, where the RRC, PDCP, RLC, and MAC layers are operated by the CRAN / vBBUP, and the PHY layer is operated by individual RAN nodes 411; or a "lower PHY" split, where the RRC, PDCP, RLC, MAC layers, and upper portions of the PHY layers are operated by the CRAN / vBBUP, and the lower portions of the PHY layers are operated by individual RAN nodes 411. This virtualization framework allows idle processor cores of the RAN node 411 to execute other virtualized applications. In some implementations, individual RAN nodes 411 may represent a plurality of virtualized applications via individual FI interfaces ( Figure 4 In these implementations, the gNB-DU may include one or more remote radio heads or RFEMs (see, e.g., Figure 5), and the gNB-CU may be operated by a server (not shown) located in the RAN 410 or by a server pool in a manner similar to CRAN / vBBUP. In addition or alternatively, one or more of the RAN nodes 411 may be a next-generation eNB (ng-eNB), which is a RAN node that provides E-UTRA user plane and control plane protocol terminations to the UE 401 and is connected to the 5G Core (5GC) via an NG interface.

[0082] In a V2X scenario, one or more of the RAN nodes 411 may be or function as an RSU. The term "roadside unit" or "RSU" may refer to any traffic infrastructure entity used for V2X communication. The RSU may be implemented in or by a suitable RAN node or a stationary (or relatively stationary) UE, where 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 RF circuitry located on the roadside that provides connectivity support to passing vehicle UEs 401 (vUEs 401). The RSU may also include internal data storage circuitry for storing intersection map geometry, traffic statistics, media, and applications / software for sensing and controlling ongoing vehicular 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 the cellular V2X band to provide the aforementioned low latency communications as well as other cellular communication 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 weatherproof 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.

[0083] Any of the RAN nodes 411 may terminate the air interface protocol and may be the first point of contact for the UE 401. In some embodiments, any of the RAN nodes 411 may perform various logical functions of the RAN 410, including but not limited to 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.

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

[0085] In some embodiments, a downlink resource grid can be used for downlink transmissions from any of the RAN nodes 411 to the UE 401, while similar techniques can be used for uplink transmissions. The grid can be a time-frequency grid, called a resource grid or time-frequency resource grid, which represents the physical resources in the downlink in each time slot. This type of time-frequency plane representation is common for OFDM systems, making radio resource allocation intuitive. Each column and 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 multiple resource blocks, which describe the mapping of certain physical channels to resource elements. Each resource block includes a collection of resource elements; in the frequency domain, this can represent the minimum amount of resources that can currently be allocated. Such resource blocks are used to transmit several different physical downlink channels.

[0086] According to various embodiments, UEs 401, 402 and RAN nodes 411, 412 communicate (e.g., transmit and receive) data over a licensed medium (also referred to as "licensed spectrum" and / or "licensed band") and an unlicensed shared medium (also referred to as "unlicensed spectrum" and / or "unlicensed band"). The licensed spectrum may include channels operating in a frequency range of approximately 400 MHz to approximately 3.8 GHz, while the unlicensed spectrum may include a 5 GHz band.

[0087] To operate in the unlicensed spectrum, the UEs 401, 402 and the RAN nodes 411, 412 may operate using LAA, eLAA, and / or feLAA mechanisms. In these implementations, the UEs 401, 402 and the RAN nodes 411, 412 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 in accordance with a listen-before-talk (LBT) protocol.

[0088] LBT is a mechanism for equipment (e.g., UE 401, 402, RAN nodes 411, 412, etc.) to sense the 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 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 intended transmission band and comparing the sensed RF energy to a predefined or configured threshold.

[0089] Typically, existing systems in the 5 GHz band are WLANs based on IEEE 802.11 technology. WLANs employ a contention-based channel access mechanism known as CSMA / CA. Here, when a WLAN node (e.g., a mobile station (MS) such as UE 401 or 402, AP 406, etc.) intends to transmit, the WLAN node may first perform CCA before transmitting. In addition, in the event that more than one WLAN node senses the channel as idle and transmits simultaneously, a backoff mechanism is used to avoid collisions. The backoff mechanism may be a counter randomly introduced within the CWS that increases exponentially when a collision occurs and is reset to a minimum value when the transmission is successful. The LBT mechanism designed for LAA is somewhat similar to CSMA / CA for WLAN. In some implementations, the LBT process for a DL or UL transmission burst (including PDSCH or PUSCH transmission) may have an 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 for 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.

[0090] The LAA mechanism is built on the Carrier Adaptation (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, resulting in a maximum aggregate bandwidth of 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 can have a different bandwidth than other CCs. In a TDD system, the number of CCs and the bandwidth of each CC are generally the same for DL and UL.

[0091] 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. The other serving cells are called SCells, and each SCell may provide individual SCCs for both UL and DL. SCCs may be added and removed as needed, and changing the PCC may require the UE 401, 402 to undergo a handover. In LAA, eLAA, and feLAA, some or all of the SCells may operate in 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 starting positions within the same subframe.

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

[0093] PDCCH uses control channel elements (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 six resource element groups (REGs). Each REG includes a resource block in one OFDM symbol. Depending on the size of the downlink control information (DCI) and the channel conditions, one or more CCEs can be used to transmit the PDCCH. Different numbers of CCEs (e.g., aggregation levels, L=1, 2, 4, 8, or 16) can be used for the transmission of PDCCH.

[0094] 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 a set of nine physical resource elements, called EREGs, including four physical resource elements. In some cases, an ECCE may have other numbers of EREGs.

[0095] RAN nodes 411 may be configured to communicate with each other via interface 412. In an embodiment where system 400 is an LTE system (e.g., when CN 420 is an EPC), interface 412 may be an X2 interface 412. The X2 interface may be defined between two or more RAN nodes 411 (e.g., two or more eNBs, etc.) connected to the EPC 420, and / or between two eNBs connected to the EPC 420. In some 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 convey information regarding the delivery of user data between eNBs. For example, the X2-U may provide specific sequence number information regarding user data transmitted from the MeNB to the SeNB; information regarding successful in-sequence delivery of PDCP PDUs for user data from the SeNB to the UE 401; information regarding PDCP PDUs that were not delivered to the UE 401; information regarding the current minimum expected buffer size at the SeNB for transmitting user data to the UE; and the like. X2-C provides intra-LTE access mobility functions, including context transfer from the source eNB to the target eNB, user plane transmission control, load management functions, and inter-cell interference coordination functions.

[0096] In embodiments where system 400 is a 5G or NR system (e.g., when CN 420 is a 5GC), interface 412 may be an Xn interface 412. The Xn interface is defined between two or more RAN nodes 411 (e.g., two or more gNBs, etc.) connected to 5GC 420, between a RAN node 411 (e.g., a gNB) and an eNB connected to 5GC 420, and / or between two eNBs connected to 5GC 420. In some implementations, the Xn interface may include an Xn user plane (Xn-U) interface and an Xn control plane (Xn-C) interface. Xn-U may provide non-guaranteed delivery of user plane PDUs and support / provide data forwarding and flow control functions. Xn-C may provide management and error handling functions for managing the functionality of the Xn-C interface; mobility support for UE 401 in connected mode (e.g., CM connection) includes functions for managing connected mode UE mobility between one or more RAN nodes 411. This mobility support may include context transfer from the old (source) serving RAN node 411 to the new (target) serving RAN node 411; and control of the user plane tunnel between the old (source) serving RAN node 411 and the new (target) serving RAN node 411. The Xn-U protocol stack may include a transport network layer built on the Internet Protocol (IP) transport layer, and a GTP-U layer built on top of the UDP and / or IP layers 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 built on top of the IP layer and may provide guaranteed delivery of application layer messages. In the transport IP layer, signaling PDUs are delivered using point-to-point transport. In other embodiments, the Xn-U protocol stack and / or the Xn-C protocol stack may be the same as or similar to the user plane and / or control plane protocol stacks shown and described herein.

[0097] RAN 410 is shown as being communicatively coupled to a core network—in this embodiment, to a core network (CN) 420. CN 420 may include multiple network elements 422 configured to provide various data and telecommunication services to customers / subscribers (e.g., users of UE 401) connected to CN 420 via RAN 410. Components of CN 420 may be implemented in a single physical node or separate physical nodes, including components for reading and executing instructions from machine-readable or computer-readable media (e.g., non-transitory machine-readable storage media). In some embodiments, NFV may be used to virtualize any or all of the aforementioned network node functions (described in further detail below) via executable instructions stored on one or more computer-readable storage media. A logical instance of CN 420 may be referred to as a network slice, and a logical instance of a portion of CN 420 may be referred to as a network sub-slice. NFV architecture and infrastructure may be used to virtualize one or more network functions onto physical resources comprising a combination of industry-standard server hardware, storage hardware, or switches (alternatively, performed by proprietary hardware). In other words, the NFV system can be used to perform virtual or reconfigurable implementations of one or more EPC components / functions.

[0098] Generally speaking, the application server 430 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 430 may also be configured to support one or more communication services (e.g., VoIP sessions, PTT sessions, group communication sessions, social networking services, etc.) for the UE 401 via the EPC 420.

[0099] In an embodiment, CN 420 may be a 5GC (referred to as "5GC 420" or the like), and RAN 410 may be connected to CN 420 via an NG interface 413. In an embodiment, NG interface 413 may be divided into two parts: an NG user plane (NG-U) interface 414, which carries traffic data between RAN node 411 and UPF; and an S1 control plane (NG-C) interface 415, which is a signaling interface between RAN node 411 and AMF.

[0100] In an embodiment, CN 420 may be a 5G CN (referred to as "5GC 420," etc.), while in other embodiments, CN 420 may be an EPC. In the case where CN 420 is an EPC (referred to as "EPC 420," etc.), RAN 410 may be connected to CN 420 via an S1 interface 413. In an embodiment, S1 interface 413 may be divided into two parts: an S1 user plane (S1-U) interface 414, which carries traffic data between RAN node 411 and S-GW; and an S1-MME interface 415, which is a signaling interface between RAN node 411 and MME.

[0101] Figure 5 An example of infrastructure equipment 500 according to various embodiments is shown. Infrastructure equipment 500 (or "system 500") can be implemented as a base station, a radio head, a RAN node (such as the RAN node 411 and / or AP 406 shown and described previously), an application server 430, and / or any other element / device discussed herein. In other examples, system 500 can be implemented in or by a UE.

[0102] System 500 includes application circuitry 505, baseband circuitry 510, one or more radio front-end modules (RFEMs) 515, memory circuitry 520, a power management integrated circuit (PMIC) 525, power tee circuitry 530, network controller circuitry 535, a network interface connector 540, satellite positioning circuitry 545, and a user interface 550. In some embodiments, device 500 may include additional components such as, for example, memory / storage, a display, a camera, sensors, or input / output (I / O) interfaces. In other embodiments, these components may be included in more than one device. For example, the circuitry may be separately included in more than one device for a CRAN, vBBU, or other similar implementation.

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

[0104] The processor of the application circuit 505 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 505 may include or may be a dedicated processor / controller for operating in accordance with various embodiments herein. As an example, the processor of the application circuit 505 may include one or more Intel or Processor: Advanced Micro Devices (AMD) Processor, Accelerated Processing Unit (APU), or processors; ARM-based processors licensed by ARM Holdings, Ltd., such as the ARM Cortex-A series processors and MIPS-based designs from MIPS Technologies, Inc., such as the MIPS Warrior P-class processor; etc. In some embodiments, system 500 may not utilize application circuitry 505 and instead may include a dedicated processor / controller to process IP data received, for example, from an EPC or 5GC.

[0105] In some implementations, the application circuit 505 may include one or more hardware accelerators, which may be microprocessors, programmable processing devices, and the like. The one or more hardware accelerators may include, for example, computer vision (CV) and / or deep learning (DL) accelerators. For example, the programmable processing device may be one or more field programmable devices (FPDs), such as field programmable gate arrays (FPGAs); programmable logic devices (PLDs), such as complex PLDs (CPLDs) and high-capacity PLDs (HCPLDs); ASICs, such as structured ASICs; programmable SoCs (PSoCs); and the like. In such embodiments, the circuitry of the application circuit 505 may include logic blocks or logic structures, as well as other interconnected resources that can be programmed to perform various functions, such as the processes, methods, functions, and the like of the various embodiments discussed herein. In such embodiments, the circuitry of the application circuit 505 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), antifuse), and the like) for storing the logic blocks, logic structures, data, and the like in a lookup table (LUT) or the like.

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

[0107] The user interface circuitry 550 may include one or more user interfaces designed to enable a user to interact with the system 500 or a peripheral component interface designed to enable a peripheral component to interact with the system 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 touchpad, a touch screen, a speaker or other audio emitting 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 port, etc.

[0108] The radio front end module (RFEM) 515 may include a millimeter wave (mmWave) RFEM and one or more sub-millimeter wave radio frequency integrated circuits (RFICs). In some implementations, the one or more sub-millimeter wave RFICs may be physically separate from the mmWave RFEM. The RFIC may include connections to one or more antennas or antenna arrays (see, for example, below). Figure 7The antenna array 711 is configured such that the RFEM can be connected to multiple antennas. In an alternative embodiment, both millimeter-wave and sub-millimeter-wave radio functions can be implemented in the same physical RFEM 515, which combines both millimeter-wave antennas and sub-millimeter-wave antennas.

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

[0110] The PMIC 525 may include a voltage regulator, a surge protector, a power alarm detection circuit, and one or more backup power sources, such as batteries or capacitors. The power alarm detection circuit may detect one or more of a brownout (undervoltage) and a surge (overvoltage) condition. The power tee circuit 530 may provide power drawn from the network cable to provide both power and data connectivity for the infrastructure equipment 500 using a single cable.

[0111] The network controller circuit 535 can 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 can be provided to / from the infrastructure equipment 500 via the network interface connector 540 using a physical connection, which can be an electrical connection (commonly referred to as a "copper interconnect"), an optical connection, or a wireless connection. The network controller circuit 535 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 535 may include multiple controllers for providing connectivity to other networks using the same or different protocols.

[0112] The positioning circuit 545 includes circuits for receiving and decoding signals transmitted / broadcasted by the positioning network of the 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., navigation using the Indian constellation (NAVIC), Japan's Quasi-Zenith Satellite System (QZSS), France's Doppler Orbit Chart and Satellite Integrated Radio Positioning (DORIS), etc.). The positioning circuit 545 includes various hardware elements (e.g., including hardware devices such as switches, filters, amplifiers, antenna elements, etc. for facilitating OTA communication) to communicate with components of the positioning network such as navigation satellite constellation nodes. In some embodiments, the positioning circuit 545 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 545 may also be part of or interact with the baseband circuit 510 and / or RFEM 515 to communicate with nodes and components of the positioning network. The positioning circuit 545 may also provide location data and / or time data to the application circuit 505, which may use the data to synchronize operations with various infrastructure (e.g., RAN node 411, etc.).

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

[0114] Figure 6 An example of a platform 600 (or "device 600") according to various embodiments is shown. In an embodiment, computer platform 600 may be suitable for use as UE 401, application server 430, and / or any other element / device discussed herein. Platform 600 may include any combination of the components shown in the example. The components of platform 600 may be implemented as integrated circuits (ICs), portions of ICs, discrete electronic devices, or other modules, logic, hardware, software, firmware, or combinations thereof adapted within computer platform 600, or as components otherwise incorporated within the chassis of a larger system. Figure 6The 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.

[0115] Application circuit 605 includes circuits such as, but not limited to, one or more processors (or processor cores), cache memory, and LDO, interrupt controller, serial interface (such as SPI), I 2 The application circuit 605 may include one or more of a C or general programmable serial interface module, an RTC, a timer (including an interval timer and a watchdog timer), general I / O, a memory card controller (such as an SD MMC or similar controller), a USB interface, a MIPI interface, and a JTAG test access port. The processor (or core) of the application circuit 605 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 system 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.

[0116] The processor of the application circuit 505 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, a multi-threaded processor, an ultra-low voltage processor, an embedded processor, some other known processing element, or any suitable combination thereof. In some embodiments, the application circuit 505 may include or may be a dedicated processor / controller for operating according to various embodiments herein.

[0117] As an example, the processor of the application circuit 605 may include a processor based on Architecture TM Processors such as Quark TM 、Atom TM , i3, i5, i7 or MCU class processors, or available from Santa Clara, CA The processor of application circuit 605 may also be one or more of the following: Advanced Micro Devices (AMD) Processor or Accelerated Processing Unit (APU); from Inc.'s A5-A9 processors, Snapdragon by Technologies, Inc. TM processors, 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 605 can be part of a system on a chip (SoC), in which the application circuit 605 and other components are formed as a single integrated circuit or a single package, such as company( Edison Corporation TM or Galileo TM SoC board.

[0118] Additionally or alternatively, the application circuit 605 may include circuitry such as, but not limited to, one or more field programmable devices (FPDs) such as FPGAs; programmable logic devices (PLDs) such as complex PLDs (CPLDs), high-capacity PLDs (HCPLDs); ASICs such as structured ASICs; programmable SoCs (PSoCs); and the like. In such embodiments, the circuitry of the application circuit 605 may include logic blocks or logic fabrics, as well as other interconnected resources that can be programmed to perform various functions, such as the processes, methods, functions, and the like of the various embodiments discussed herein. In such embodiments, the circuitry of the application circuit 605 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), antifuse), and the like) for storing logic blocks, logic fabrics, data, and the like in lookup tables (LUTs) and the like.

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

[0120] The RFEM 615 may include a millimeter wave (mmWave) RFEM and one or more sub-millimeter wave radio frequency integrated circuits (RFICs). In some implementations, the one or more sub-millimeter wave RFICs may be physically separate from the mmWave RFEM. The RFIC may include connections to one or more antennas or antenna arrays (see, for example, below). Figure 7 The antenna array 711 is configured such that the RFEM can be connected to multiple antennas. In an alternative embodiment, both millimeter-wave and sub-millimeter-wave radio functions can be implemented in the same physical RFEM 615, which combines both millimeter-wave antennas and sub-millimeter-wave antennas.

[0121] The memory circuit 620 may include any number and type of memory devices for providing a fixed amount of system memory. For example, the memory circuit 620 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 620 may be developed according to a Joint Electron Device Engineering Council (JEDEC) low-power double data rate (LPDDR)-based design, such as LPDDR2, LPDDR3, LPDDR4, etc. The memory circuit 620 may be implemented as one or more of the following: a solder-in package integrated circuit, a single die package (SDP), a dual die package (DDP), or a quad die package (Q17P), a socketed memory module, a dual in-line memory module (DIMM) including a micro DIMM or a mini DIMM, and / or soldered to a motherboard via a ball grid array (BGA). In a low-power implementation, the memory circuit 620 may be an on-chip memory or register associated with the application circuit 605. To provide persistent storage of information such as data, applications, operating systems, etc., the memory circuit 620 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.

[0122] Removable storage circuitry 623 may include devices, circuitry, 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.

[0123] Platform 600 may also include an interface circuit (not shown) for connecting external devices to platform 600. External devices connected to platform 600 via the interface circuit include sensor circuit 621 and electromechanical components (EMC) 622, as well as a removable memory device coupled to removable memory circuit 623.

[0124] Sensor circuitry 621 comprises a device, module, or subsystem whose purpose is to detect events or changes in its environment and to send information about the detected events (sensor data) to some other device, module, subsystem, etc. Examples of such sensors include, among others: an inertial measurement unit (IMU) including an accelerometer, a gyroscope, and / or a magnetometer; a microelectromechanical system (MEMS) or nanoelectromechanical system (NEMS) including a three-axis accelerometer, a three-axis gyroscope, and / or a magnetometer; a fluid 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.

[0125] The EMC 622 includes devices, modules, or subsystems designed to enable the platform 600 to change its state, position, and / or orientation, or to move or control mechanisms or (sub)systems. Additionally, the EMC 622 can be configured to generate and send messages / signaling to other components of the platform 600 to indicate the current state of the EMC 622. The EMC 622 includes one or more power switches, relays (including electromechanical relays (EMRs) and / or solid-state relays (SSRs)), actuators (e.g., valve actuators, etc.), audible sound generators, visual warning devices, motors (e.g., DC motors, stepper motors, etc.), wheels, thrusters, propellers, claws, clamps, hooks, and / or other similar electromechanical components. In an embodiment, the platform 600 is configured to operate one or more EMCs 622 based on one or more capture events and / or instructions or control signals received from service providers and / or various clients.

[0126] In some implementations, the interface circuitry may connect the platform 600 to the positioning circuitry 645. The positioning circuitry 645 includes circuitry for receiving and decoding signals transmitted / broadcasted by a GNSS positioning network. 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.). The positioning circuitry 645 includes various hardware components (e.g., including hardware devices for facilitating over-the-air (OTA) communications, such as switches, filters, amplifiers, antenna elements, etc.) to communicate with components of the positioning network, such as nodes of the navigation satellite constellation. In some embodiments, the positioning circuitry 645 may include a micro PNT IC that uses a master timing clock to perform position tracking / estimation without GNSS assistance. The positioning circuitry 645 may also be part of or interact with the baseband circuitry 510 and / or RFEM 615 to communicate with nodes and components of the positioning network. Positioning circuitry 645 may also provide location data and / or time data to application circuitry 605 , which may use the data to synchronize operations with various infrastructure (eg, radio base stations) for turn-by-turn navigation applications, and the like.

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

[0128] Driver circuitry 646 may include software and hardware components for controlling specific devices embedded in, attached to, or otherwise communicatively coupled to platform 600. Driver circuitry 646 may include various drivers to allow other components of platform 600 to interact with or control various input / output (I / O) devices that may be present within or connected to platform 600. For example, driver circuitry 646 may include a display driver for controlling and enabling access to a display device, a touch screen driver for controlling and enabling access to a touch screen interface of platform 600, a sensor driver for acquiring sensor readings from sensor circuitry 621 and controlling and enabling access to sensor circuitry 621, an EMC driver for acquiring actuator positions of EMC 622 and / or controlling and enabling access to EMC 622, a camera driver for controlling and enabling access to an embedded image capture device, and an audio driver for controlling and enabling access to one or more audio devices.

[0129] A power management integrated circuit (PMIC) 625 (also referred to as "power management circuit 625") can manage the power provided to various components of platform 600. Specifically, PMIC 625 can control power source selection, voltage scaling, battery charging, or DC-DC conversion with respect to baseband circuit 610. PMIC 625 is typically included when platform 600 is capable of being powered by battery 630, such as when the device is included in UE 401.

[0130] In some embodiments, the PMIC 625 can 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, where it remains connected to the RAN node as it expects to receive traffic soon, after a period of inactivity, it can enter a state known as discontinuous reception mode (DRX). During this state, the platform 600 can be powered down for short intervals, thereby saving power. If there is no data traffic activity for an extended period of time, the platform 600 can transition to the RRC Idle state, where the device is disconnected from the network and does not perform operations such as channel quality feedback or handovers. The platform 600 enters a very low-power state and performs paging, where the device periodically wakes up to listen to the network before being powered down again. The platform 600 cannot receive data in this state; to receive data, it must transition back to the RRC Connected state. Additional power-saving modes can prevent the device from using the network for periods exceeding the paging interval (ranging from a few seconds to several hours). During this period, the device is completely unable to connect to the network and can be completely powered down. Any data sent during this time will cause significant delay, and it is assumed that the delay is acceptable.

[0131] Battery 630 can power platform 600, but in some examples, platform 600 can be installed in a fixed location and can have a power source coupled to the power grid. Battery 630 can be a lithium-ion battery, a metal-air battery such as a zinc-air battery, an aluminum-air battery, a lithium-air battery, etc. In some implementations, such as in V2X applications, battery 630 can be a typical lead-acid car battery.

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

[0133] A power block or other power source coupled to the grid can be coupled to the BMS to charge the battery 630. In some examples, the power block can be replaced with a wireless power receiver to wirelessly obtain power, for example, via a loop antenna in the computer platform 600. In these examples, wireless battery charging circuitry can be included in the BMS. The specific charging circuit selected can depend on the size of the battery 630 and, therefore, the required current. 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 Consortium, or the Rezence charging standard published by the Wireless Power Consortium.

[0134] The user interface circuit 650 includes various input / output (I / O) devices present within or connected to the platform 600, and includes one or more user interfaces designed to implement user interaction with the platform 600 and / or peripheral component interfaces designed to implement interaction with peripheral components of the platform 600. The user interface circuit 650 includes input device circuits and output device circuits. The input device circuit includes any physical or virtual device 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 trackpad, a touch screen, a microphone, a scanner, a headset, etc. The output device circuit includes any physical or virtual device for displaying information or otherwise conveying information (such as sensor readings, actuator positions, or other similar information). The output device circuitry may include any number and / or combination of audio or visual displays, including, among other things, one or more simple visual outputs / indicators (e.g., binary state indicators (e.g., light emitting diodes (LEDs)) and multi-character visual outputs, or more complex outputs such as a display device or touch screen (e.g., a liquid crystal display (LCD), an LED display, a quantum dot display, a projector, etc.), wherein output of characters, graphics, multimedia objects, etc., is generated or produced by the operation of the platform 600. The output device circuitry may also include a speaker or other audio emitting device, a printer, etc. In some embodiments, the sensor circuitry 621 may function as an input device circuitry (e.g., an image capture device, a motion capture device, etc.) and one or more EMCs may function as output device circuitry (e.g., an actuator for providing tactile feedback, etc.). In another example, an NFC circuit may be included to read an electronic tag and / or connect to another NFC-enabled device, the NFC circuitry including an NFC controller and a processing device coupled to an antenna element. Peripheral component interfaces may include, but are not limited to, a non-volatile memory port, a USB port, an audio jack, a power port, etc.

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

[0136] Figure 7 Exemplary components of a baseband circuit 710 and a radio front end module (RFEM) 715 are shown according to various embodiments. The baseband circuit 710 corresponds to Figure 5 The baseband circuit 510 and Figure 6 Baseband circuit 610. RFEM 715 corresponds to Figure 5 RFEM 515 and Figure 6 RFEM 615. As shown, RFEM 715 may include radio frequency (RF) circuitry 706, front end module (FEM) circuitry 708, and at least an antenna array 711 coupled together as shown.

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

[0138] The aforementioned circuits and / or control logic components of the baseband circuitry 710 may include one or more single-core or multi-core processors. For example, the one or more processors may include a 3G baseband processor 704A, a 4G / LTE baseband processor 704B, a 5G / NR baseband processor 704C, or some other baseband processor 704D for other existing, developing, or future generations (e.g., the sixth generation (6G), etc.). In other embodiments, some or all of the functionality of the baseband processors 704A-704D may be included in modules stored in the memory 704G and executed via the central processing unit (CPU) 704E. In other embodiments, some or all of the functionality of the baseband processors 704A-D may be provided as hardware accelerators (e.g., FPGAs, ASICs, etc.) loaded with appropriate bitstreams or logic blocks stored in corresponding memory units. In various embodiments, the memory 704G may store program code for a real-time OS (RTOS) that, when executed by the CPU 704E (or other baseband processor), enables the CPU 704E (or other baseband processor) to manage resources of the baseband circuit 710, schedule tasks, etc. Examples of RTOS may include: Operating System Embedded (OSE) TM , by Mentor Nucleus RTOS provided TM , by Mentor Versatile Real-Time Executive (VRTX) provided by Express ThreadX TM ,Depend on FreeRTOS and REX OS provided by OpenKernel (OK) The baseband circuit 710 may include one or more audio digital signal processors (DSPs) 704F. The audio DSPs 704F may include elements for compression / decompression and echo cancellation, and may include other suitable processing elements in other embodiments.

[0139] In some embodiments, each of processors 704A-704E includes a corresponding memory interface to send data to / receive data from memory 704G. Baseband circuit 710 may also include one or more interfaces for communicatively coupling to other circuits / devices, such as an interface for sending data to / receiving data from a memory external to baseband circuit 710; an interface for sending data to / receiving data from a memory external to baseband circuit 710; Figures 5 to 7Application circuit interface for sending data to / receiving data from the application circuit 505 / 605; Figure 7 RF circuit 706 to send data / receive data from the RF circuit RF circuit interface; for receiving data from one or more wireless hardware elements (e.g., near field communication (NFC) components, Low power consumption components, components, etc.) to send data / receive data from these wireless hardware elements; and a power management interface for sending power or control signals to / from the PMIC 625.

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

[0141] although Figure 7Although not shown, in some embodiments, the baseband circuitry 710 includes various processing devices (e.g., a "multi-protocol baseband processor" or "protocol processing circuitry") for operating one or more wireless communication protocols and various processing devices for implementing PHY layer functions. In these embodiments, the PHY layer functions include the aforementioned radio control functions. In these embodiments, the protocol processing circuitry operates or implements various protocol layers / entities of one or more wireless communication protocols. In a first example, when the baseband circuitry 710 and / or the RF circuitry 706 are part of millimeter wave communication circuitry or some other suitable cellular communication circuitry, the protocol processing circuitry may operate LTE protocol entities and / or 5G / NR protocol entities. In the first example, the protocol processing circuitry will operate MAC, RLC, PDCP, SDAP, RRC, and NAS functions. In a second example, when the baseband circuitry 710 and / or the RF circuitry 706 are part of a Wi-Fi communication system, the protocol processing circuitry may operate one or more IEEE-based protocols. In the second example, the protocol processing circuitry will operate Wi-Fi MAC and Logical Link Control (LLC) functions. The protocol processing circuitry may include one or more memory structures (e.g., 704G) for storing program code and data for operating protocol functions, and one or more processing cores for executing program code and performing various operations using data. The baseband circuitry 710 may also support radio communications for more than one wireless protocol.

[0142] The various hardware elements of the baseband circuit 710 discussed herein may be implemented as, for example, a solder-in substrate comprising one or more integrated circuits (ICs), a single packaged integrated circuit soldered to a main circuit board, or a multi-chip module comprising two or more ICs. In one example, the components of the baseband circuit 710 may be appropriately combined in a single chip or a single chipset, or provided on the same circuit board. In another example, some or all of the components of the baseband circuit 710 and the RF circuit 706 may be implemented together, such as, for example, a system on a chip (SOC) or a system in a package (SiP). In another example, some or all of the components of the baseband circuit 710 may be implemented as a separate SoC communicatively coupled to the RF circuit 706 (or multiple instances of the RF circuit 706). In yet another example, some or all of the components of the baseband circuit 710 and the application circuit 505 / 605 may be implemented together as a separate SoC mounted to the same circuit board (e.g., a "multi-chip package").

[0143] In some embodiments, the baseband circuit 710 can provide communications compatible with one or more radio technologies. For example, in some embodiments, the baseband circuit 710 can support communications with E-UTRAN or other WMANs, WLANs, or WPANs. Embodiments in which the baseband circuit 710 is configured to support radio communications using more than one wireless protocol may be referred to as multi-mode baseband circuitry.

[0144] The RF circuitry 706 can communicate with a wireless network using modulated electromagnetic radiation through a non-solid medium. In various embodiments, the RF circuitry 706 can include switches, filters, amplifiers, etc. to facilitate communication with the wireless network. The RF circuitry 706 can include a receive signal path that can include circuitry for down-converting RF signals received from the FEM circuitry 708 and providing baseband signals to the baseband circuitry 710. The RF circuitry 706 can also include a transmit signal path that can include circuitry for up-converting baseband signals provided by the baseband circuitry 710 and providing an RF output signal to the FEM circuitry 708 for transmission.

[0145] In some embodiments, the receive signal path of RF circuitry 706 may include mixer circuitry 706a, amplifier circuitry 706b, and filter circuitry 706c. In some embodiments, the transmit signal path of RF circuitry 706 may include filter circuitry 706c and mixer circuitry 706a. RF circuitry 706 may also include synthesizer circuitry 706d for synthesizing frequencies used by mixer circuitry 706a in the receive and transmit signal paths. In some embodiments, mixer circuitry 706a in the receive signal path may be configured to downconvert the RF signal received from FEM circuitry 708 based on the synthesized frequency provided by synthesizer circuitry 706d. Amplifier circuitry 706b may be configured to amplify the downconverted signal, and filter circuitry 706c may be a low-pass filter (LPF) or a band-pass filter (BPF) configured to remove unwanted signals from the downconverted signal to generate an output baseband signal. The output baseband signal may be provided to baseband circuitry 710 for further processing. In some embodiments, the output baseband signal can be a zero-frequency baseband signal, although this is not required.In some embodiments, the mixer circuit 706a of the receive signal path can include a passive mixer, although the scope of the embodiments is not limited in this respect.

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

[0147] In some embodiments, the mixer circuit 706a of the receive signal path and the mixer circuit 706a 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 706a of the receive signal path and the mixer circuit 706a 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 706a of the receive signal path and the mixer circuit 706a of the transmit signal path may be arranged for direct down-conversion and direct up-conversion, respectively. In some embodiments, the mixer circuit 706a of the receive signal path and the mixer circuit 706a of the transmit signal path may be configured for superheterodyne operation.

[0148] 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, RF circuitry 706 may include analog-to-digital converter (ADC) and digital-to-analog converter (DAC) circuitry, and baseband circuitry 710 may include a digital baseband interface to communicate with RF circuitry 706.

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

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

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

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

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

[0154] In some embodiments, the synthesizer circuit 706d can be configured to generate a carrier frequency as the 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 at the carrier frequency with multiple different phases relative to each other. In some embodiments, the output frequency can be the LO frequency (fLO). In some embodiments, the RF circuit 706 can include an IQ / polarity converter.

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

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

[0157] Antenna array 711 includes one or more antenna elements, each configured to convert electrical signals into radio waves for travel through the air and to convert received radio waves into electrical signals. For example, a digital baseband signal provided by baseband circuitry 710 is converted into an analog RF signal (e.g., a modulated waveform), which is amplified and transmitted via the antenna elements of antenna array 711, which includes one or more antenna elements (not shown). The antenna elements can be omnidirectional, directional, or a combination thereof. The antenna elements can be formed into various arrangements as known and / or discussed herein. Antenna array 711 can include microstrip antennas or printed antennas fabricated on the surface of one or more printed circuit boards. Antenna array 711 can be formed as patches of metal foil of various shapes (e.g., patch antennas) and can be coupled to RF circuitry 706 and / or FEM circuitry 708 using metal transmission lines, etc.

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

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

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

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

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

[0163] The instructions 850 may include software, a program, an application, an applet, an application, or other executable code for causing at least one of the processors 810 to perform any one or more of the methods discussed herein. The instructions 850 may reside entirely or partially within at least one of the processors 810 (e.g., within a cache memory of the processor), the memory / storage device 820, or any suitable combination thereof. In addition, any portion of the instructions 850 may be transferred to the hardware resources 800 from any combination of the peripheral devices 804 or the database 806. Thus, the memory of the processor 810, the memory / storage device 820, the peripheral devices 804, and the database 806 are examples of computer-readable media and machine-readable media.

[0164] In some embodiments, Figures 4 to 8 The electronic devices, networks, systems, chips or components or portions thereof or specific implementations in some other figures herein may be configured to perform one or more processes, techniques or methods described herein or portions thereof.

[0165] 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 Examples section below. For example, the baseband circuitry described above in conjunction with one or more of the foregoing figures may be configured to operate according to one or more of the embodiments described below. For another example, circuitry associated with the UE, base station, network element, etc. described above in conjunction with one or more of the foregoing figures may be configured to operate according to one or more of the embodiments described below in the Examples section.

[0166] Some non-limiting examples of various embodiments are provided below.

[0167] Embodiment 1 is one or more computer-readable media (CRM) having stored thereon instructions that, when executed by one or more processors, cause a user equipment (UE) to perform the following operations: receive a time-frequency resource allocation for an uplink transmission in a cell; receive configuration information of a time-frequency region in the cell, wherein the time-frequency region includes a plurality of configured partitions; receive a downlink control information (DCI) message including an indication of the priority of one or more partitions within the second resource; determine that the time-frequency resource allocation overlaps with at least one partition of the time-frequency region for which a priority indication is received; and cancel, based on the determination, a remaining portion of the uplink transmission remaining after the determination.

[0168] Embodiment 2 is the one or more CRMs according to embodiment 1, wherein the remainder is the entire uplink transmission.

[0169] Embodiment 3 is the one or more CRMs of embodiment 1, wherein the remaining portion is only a portion of the uplink transmission.

[0170] Embodiment 4 is one or more CRMs according to embodiment 1, wherein the configuration information is received via radio resource control (RRC) signaling, and wherein the configuration information includes the number of the plurality of partitions in the time-frequency region.

[0171] Embodiment 5 is one or more CRMs according to embodiment 1, wherein the plurality of partitions comprises a first number of partitions in the time domain and a second number of partitions in the frequency domain.

[0172] Embodiment 6 is one or more CRMs according to embodiment 1, wherein the indication comprises a bitmap, wherein individual bits of the bitmap indicate whether a status of priority is indicated for the partition associated with the corresponding individual bit.

[0173] Embodiment 7 is one or more CRMs according to embodiment 6, wherein the indication further comprises a field for indicating the granularity of the partition of the bitmap.

[0174] Embodiment 8 is one or more CRMs according to embodiment 1, wherein the configuration information indicates a radio network temporary identifier (RNTI) associated with the indication, wherein the indication includes the RNTI.

[0175] Embodiment 9 is one or more CRMs according to embodiment 1, wherein the indication includes a plurality of fields for indicating priorities of different corresponding carrier frequencies.

[0176] Embodiment 10 is one or more computer-readable media (CRMs) having stored thereon instructions that, when executed by one or more processors, cause a next-generation node B (gNB) to: encode a message for transmission to a first user equipment (UE) in a wireless cellular network for a first resource allocation for an uplink transmission to the gNB; determine that a second resource allocation for a second UE overlaps with one or more time-frequency resources of the first resource allocation; and encode, for transmission to the UE, an indication of the one or more time-frequency resources, the indication of the one or more time-frequency resources commanding the UE to cancel a remaining portion of the uplink transmission that remains after processing the indication.

[0177] Embodiment 11 is one or more CRMs according to embodiment 10, wherein the remainder is the entire uplink transmission.

[0178] Embodiment 12 is one or more CRMs according to embodiment 10, wherein the remaining portion is only a portion of the uplink transmission.

[0179] Embodiment 13 is one or more CRMs according to embodiment 10, wherein the indication comprises a bitmap, wherein individual bits of the bitmap indicate whether an overlapping status is indicated for the time-frequency partition associated with the respective individual bits.

[0180] Embodiment 14 is one or more CRMs according to embodiment 13, wherein the indication further comprises a field for indicating the granularity of the time-frequency partitioning of the bitmap.

[0181] Embodiment 15 is one or more CRMs according to embodiment 13, wherein the indication further includes an indication of a start position, an end position, a duration, or a frequency range of a frequency region associated with the indication.

[0182] Embodiment 16 is one or more CRMs according to embodiment 10, further comprising: determining a group of UEs including the first UE and excluding the second UE, wherein the group of UEs is subject to cancellation of uplink transmission due to overlap; and configuring a radio network temporary identifier (RNTI) for the group of UEs; wherein the indication is transmitted to the group of UEs associated with the RNTI.

[0183] Embodiment 17 is one or more CRMs according to any one of embodiments 10 to 16, wherein the first resource allocation is for enhanced mobile broadband (eMBB) or massive machine type communication (mMTC), and the second resource allocation is for ultra-reliable and low-latency communication (URLLC).

[0184] Embodiment 18 is one or more computer-readable media having stored thereon instructions that, when executed by one or more processors, cause a first user equipment (UE) to perform the following operations: receive a first resource allocation for an uplink transmission in a wireless cellular network; receive, in a downlink control information (DCI) message provided to a plurality of UEs including the first UE and the second UE, an indication of one or more time-frequency resources that overlap with the first resource allocation for a second resource allocation of the second UE; and modify the uplink transmission based on the indication, wherein the modification is different from a modification to be performed by the second UE based on the indication.

[0185] Embodiment 19 is one or more CRMs according to embodiment 18, wherein the instructions, when executed, further cause the first UE to receive configuration information to indicate the modification to be performed by the first UE based on the indication.

[0186] Embodiment 20 is one or more CRMs according to embodiment 18, wherein to modify the uplink transmission, the first UE cancels the uplink transmission on the indicated time-frequency resources.

[0187] Embodiment 21 is one or more CRMs according to embodiment 18, wherein the uplink transmission is a first uplink transmission, and wherein: in order to modify the first uplink transmission, the first UE will reduce the first transmission power of the first uplink transmission on the indicated time-frequency resources; and the second UE will increase the second transmission power of the second uplink transmission of the second UE on the indicated time-frequency resources in response to the indication.

[0188] Embodiment 22 is one or more CRMs according to embodiment 18, wherein the uplink transmission is a first uplink transmission, and wherein: in order to modify the first uplink transmission, the first UE will increase the first transmission power of the first uplink transmission on the indicated time-frequency resources; and the second UE will reduce the second transmission power of the second uplink transmission of the second UE on the indicated time-frequency resources in response to the indication.

[0189] Embodiment 23 is one or more CRMs according to any one of embodiments 18 to 22, wherein the indication comprises: a bitmap, and wherein individual bits of the bitmap indicate whether an overlapping state is indicated for the corresponding time-frequency partition; and a field for indicating the granularity of the resource indication of the bitmap.

[0190] Embodiment 24 is one or more CRMs according to embodiment 23, wherein the indication further includes an indication of a start position, an end position, a duration, or a frequency range of a frequency region associated with the indication.

[0191] Embodiment 25 is one or more CRMs according to any one of embodiments 18 to 24, wherein: the first resource allocation is used for one of enhanced mobile broadband (eMBB), massive machine type communication (mMTC), or ultra-reliable and low-latency communication (URLLC); and the second resource allocation is used for a different one of eMBB, URLLC, or mMTC.

[0192] Unless expressly 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 forms disclosed. Modifications and variations are possible in light of the above teachings or may be acquired from practice of the various embodiments.

Claims

1. A computer-readable medium (CRM) having stored thereon instructions that, when executed by one or more processors, cause a first user equipment (UE) to perform the following operations: receiving a time-frequency resource allocation for uplink transmission in a cell; receiving configuration information of a time-frequency region in the cell, wherein the time-frequency region includes a plurality of configured partitions; receiving a downlink control information (DCI) message for a plurality of UEs including the first UE, the message including an indication of a priority of one or more partitions within a second resource, wherein: The first UE is configured with a radio network temporary identifier (RNTI) to indicate associated behavior of the first UE; determining that the time-frequency resource allocation overlaps with at least one partition of the time-frequency region for which a priority indication is received; as well as Transmission of the overlapping portion of the uplink transmission is canceled based on the determination and the RNTI, and transmission power of the remaining portion of the uplink transmission is modified. 2 . The CRM according to claim 1 , wherein the configuration information is received via Radio Resource Control (RRC) signaling, and wherein the configuration information includes the number of partitions in the time-frequency region. 3 . The CRM of claim 1 , wherein the plurality of configured partitions comprises a first number of partitions in the time domain and a second number of partitions in the frequency domain. 4 . The CRM of claim 1 , wherein the indication of priority comprises a bitmap, wherein individual bits of the bitmap indicate a status of whether priority is indicated for the partition associated with the corresponding individual bits.

5. The CRM of claim 4, wherein the indication of priority further comprises a field for indicating a granularity of the partition of the bitmap.

6. The CRM of claim 1, wherein the configuration information indicates an RNTI associated with the indication of priority, wherein the indication of priority comprises the RNTI associated with the indication of priority.

7. The CRM of claim 1, wherein the indication of the priority comprises a plurality of fields for indicating the priorities of different corresponding carrier frequencies.

8. A computer readable medium (CRM) having stored thereon instructions that, when executed by one or more processors, cause a base station to: A message for indicating first resource allocation for uplink transmission from a first user equipment UE in a wireless cellular network to the base station is encoded for transmission to the first UE, wherein: The first UE is configured with a radio network temporary identifier (RNTI) to indicate associated behavior of the first UE, and wherein the RNTI is configured and used to scramble a cyclic redundancy check of a group-common DCI to indicate uplink transmission cancellation; determining that a second resource allocation for a second UE overlaps with one or more time-frequency resources of the first resource allocation; and An indication of the one or more time-frequency resources is encoded for transmission to the first UE, and the indication of the one or more time-frequency resources commands the first UE to cancel a remaining portion of the uplink transmission remaining after processing the indication of the one or more time-frequency resources.

9. The CRM of claim 8, wherein the indication of the one or more time-frequency resources comprises a bitmap, wherein individual bits of the bitmap indicate a status of whether overlap is indicated for the time-frequency partition associated with the corresponding individual bit.

10. The CRM of claim 9, wherein the indication of the one or more time-frequency resources further comprises a field for indicating a granularity of the time-frequency partitioning of the bitmap.

11. The CRM of claim 9, wherein the indication of the one or more time-frequency resources further comprises an indication of a start position, an end position, a duration or a frequency range of a frequency region associated with the indication of the one or more time-frequency resources.

12. The CRM of claim 8, wherein: The instructions, when executed by the one or more processors, further cause the base station to: determining a group of UEs including the first UE and excluding the second UE, the group of UEs being subject to cancellation of uplink transmission due to overlap; as well as Configuring an RNTI for the group of UEs; The indication of the one or more time-frequency resources is transmitted to the group of UEs associated with the RNTI configured for the group of UEs.

13. The CRM according to any one of claims 8 to 12, wherein the first resource allocation is for enhanced mobile broadband (eMBB) or massive machine type communication (mMTC), and the second resource allocation is for ultra-reliable and low-latency communication (URLLC).

14. A computer readable medium (CRM) having stored thereon instructions which, when executed by one or more processors, cause a first user equipment (UE) to perform the following operations: receiving a first resource allocation for an uplink transmission in a wireless cellular network; In a downlink control information (DCI) message provided to a plurality of UEs including the first UE and a second UE, an indication of one or more time-frequency resources on which a second resource allocation of the second UE overlaps with the first resource allocation is received, wherein: The first UE is configured with a radio network temporary identifier (RNTI) to indicate associated behavior of the first UE, and wherein the RNTI is configured and used to scramble a cyclic redundancy check of a group-common DCI to indicate uplink transmission with modified transmission power; and The uplink transmission is modified based on the indication of the one or more time-frequency resources, wherein the modification is different from a modification to be performed by the second UE based on the indication of the one or more time-frequency resources.

15. The CRM of claim 14, wherein the uplink transmission is a first uplink transmission, and wherein: To modify the first uplink transmission, the first UE is to reduce a first transmission power of the first uplink transmission on the indicated time-frequency resources; and The second UE will increase a second transmission power of a second uplink transmission of the second UE on the indicated time-frequency resources in response to the indication of the one or more time-frequency resources.

16. The CRM of claim 14, wherein the uplink transmission is a first uplink transmission, and wherein: To modify the first uplink transmission, the first UE is to increase a first transmission power of the first uplink transmission on the indicated time-frequency resources; and The second UE will reduce a second transmission power of a second uplink transmission of the second UE on the indicated time-frequency resources in response to the indication of the one or more time-frequency resources.

17. The CRM according to any one of claims 14 to 16, wherein the indication of the one or more time-frequency resources comprises: a bitmap, and wherein individual bits of the bitmap indicate a status of whether overlap is indicated for a corresponding time-frequency partition; and A field is used to indicate the granularity of the resource indication of the bitmap.

18. The CRM of claim 17, wherein the indication of the one or more time-frequency resources further comprises an indication of a start position, an end position, a duration or a frequency range of a frequency region associated with the indication of the one or more time-frequency resources.

19. A CRM according to any one of claims 14 to 16, wherein: The first resource allocation is for one of enhanced mobile broadband (eMBB), massive machine type communication (mMTC), or ultra-reliable and low-latency communication (URLLC); and The second resource allocation is used for a different one of eMBB, URLLC, or mMTC.

Images